Nortel Edge Deployment

411-9001-801
Wireless Service Provider Solutions

EDGE
Deployment Guide
BSS V15 Standard 01.04 November 2004
What’s inside...
E-GPRS Deployment Roadmap
BSS Datafill
New Counters and Troubleshooting
Engineering Methods: Interfaces
Support Material
test
EDGE
Deployment Guide
Document number: 411-9001-801

Product release: BSS V15
Document version: Standard 01.04
Date: November 2004
Copyright Country of printing Confidentiality Legal statements Trademarks
Copyright © 2004 Nortel Networks, All Rights Reserved

Originated in Canada
NORTEL NETWORKS CONFIDENTIAL
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks. CDMA2000
is a trademark of the Telecommunications Industry Association (TIA). CDMA2000 1X is a trademark of the CDMA Development
Group. Microsoft Windows and Win2000 are trademarks of Microsoft Corporation. UNIX is a trademark of X/Open Company
Limited.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
iv
Nortel Networks Confidential Copyright © 2004 Nortel Networks
411-9001-801 Standard 01.04 November 2004

v
Publication history
November 2004
01.03-01.04, Standard release. Minor fixes.
July 2004
01.02, Standard release. Updated the upgrade paths and support statement
concerning E4002.
May 2004
01.01, Initial release.
Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

vi Publication history

vii
Contents
About this document xiii

Audience for this document -xiii
Organization of this document -xiii
Indication of hypertext links -xiv
Related documents -xiv
E-GPRS Deployment Roadmap 1-1

Upgrade and Compatibility for V15.0 1-2
Nortel NSS Compatibility 1-2
Nortel GPRS Packet Core Compatibility 1-2
Norel SMLC Compatibility 1-2
CT Compatibility 1-2
BSS Release Upgrade Path POR 1-3
Supported WPS Configurations 1-3
Prerequisites 1-4
BTS 1-4
BSC 1-8
PCUSN 1-8
OMC-R 1-9
Tools 1-12
CT/CPT Hardware and Software 1-12
CT2000 Hardware and Software 1-13
CT7100 CT/CPT Hardware and Software 1-13
TIL & TML 1-13
NIMS - PrOptimaTM 1-14
SW License 1-14
BSS Datafill 2-17

Backhaul Enhancement 2-17
REL'99 Activation: Radio 2-17
E-GPRS Activation 2-18
REL'99 Interaction 2-19
Edge Configuration 2-19
OMC-R MMI Parameters 2-19
PCUSN OAM Parameters 2-25
Unused GPRS Parameters 2-26
EDGE Configuration Tool 2-28

viii Contents
Tool Description 2-28

EDGE Cell Configuration Input 2-30
EDGE TDMA and Backhaul Input 2-33
Tool File Input 2-35
EDGE BTS Configuration 2-37
EDGE TDMA and Backhaul 2-38
EDGE Backhaul Algorithm 2-41
Radio Site Mask Algorithm 2-42
Checks Performed by the Tool 2-45
NRP 2-45
Tool Options 2-46
Tool Output 2-47
Command Files Generated 2-47
LOG File 2-48
NSS Core Datafill 2-48
GPRS Core Datafill 2-48
New Counters and Troubleshooting 3-51

EDGE Radio Quality 3-52
EDGE Link Adaptation Tables Fine-Tuning 3-54
GPRS/EDGE Agprs 3-56
EDGE Abis 3-58
Lack of EDGE Radio Resource 3-59
EDGE Traffic Profile and Throughput 3-60
GPRS Monitoring Improvement 3-62
Engineering Methods: Interfaces 4-65

Methodology 4-65
First Step: Radio interface 4-66
Second Step: DS0 joker on Abis 4-67
Third step: BTS hardware compatibility: 4-68
Fourth Step: Abis backhaul dimensioning 4-68
Fifth step: Agprs dimensioning. 4-68
Sixth step: BSC/PCU dimensioning. 4-68
Example 4-69
Radio Interface 4-73
EDGE Deployment in an existing network 4-74
Data throughput calculation 4-74
Radio Conditions (C/I and Eb/No) on the Cell 4-76
Mean Throughput per TS Calculation 4-81
Link Adaptation 4-85
Mean Throughput / TS 4-86
EDGE Performance Estimation 4-88
EDGE TS Allocation Strategy 4-104
Conclusion 4-109
Traffic Sharing Between TDMA 4-110
BTS 4-112
Capability Management 4-112
Site and Joker Management 4-114
TRX Capability 4-114

Contents ix
TDMA Mapping Over Available TRX 4-115

EPA - HEPA 4-116
Operation Information 4-120
Recommendations 4-120
Abis Interface 4-121
Joker Dimensioning 4-121
PCM Allocation 4-125
TDMA Rules 4-125
PCM Dimensioning 4-125
Defense Mechanisms 4-126
Backhaul Configuration Algorithm 4-127
4-130
RSM Rule 4-130
Impact On EDGE Performance 4-133
BSC3 4-133
BSC3 Rule 4-133
Defense Mechanisms 4-134
Recommendation 4-135
Agprs Interface 4-135
GPRS Principles 4-135
EDGE Principles 4-135
Guideline for Agprs Initial Dimensioning 4-137
PCUSN Dimensioning 4-142
Support Material 5-143

MEAN_BEP and CV_BEP Mapping for DL 5-143
MEAN_BEP and CV_BEP Mapping for UL 5-147
Recommended Link Adaptation Tables 5-147
Link Adaptation Tables Usage Examples 5-149
DL 8-PSK & GMSK Tables Usage (no output limitation) 5-149
DL 8-PSK & GMSK With GMSK Only Tables Usage 5-151
Type of LA-Tables 5-152
ePA 900/1800 and eDRX 900 Introduction 5-153
Details 5-154
Phase In/Phase Out Plan 5-154
Market Models And Market Packages 5-156
Network Identification and Automatic SW Downloading of BTS Equipment 5-
160
EFT Management 5-160
Spare Management 5-161
R and R Management 5-161
List of figures
Figure 1-1 E-GPRS network 1-2
Figure 2-1 EDGE Tool Configuration Plug-In Interface Window 2-29
Figure 2-2 EDGE Backhaul Algorithm 2-41
Figure 2-3 EDGE Radio Site Mask Algorithm 2-42
Figure 4-1 EDGE GPRS deployment methodology 4-66
Figure 4-2 Data throughput calculation methodology 4-76
Figure 4-3 Cell Partitioning 4-77

x Contents
Figure 4-4 C/I cdf depending on frequency re-use pattern 4-80

Figure 4-5 BLER=f(Eb/No) in TU50, no FH, no IR, no Diversity at 1800 MHz 4-
82
Figure 4-6 BLER=f(C/I) in TU50, no FH, no IR, no Diversity at 1800 MHz 4-83
Figure 4-7 MCS distribution 4-86
Figure 4-8 Mean data throughput integration 4-87
Figure 4-9 BLER versus sensitivity for speech in TU3 without frequency hopping
4-96
Figure 4-10 BLER versus sensitivity for speech in TU3 with frequency hopping 4-
97
Figure 4-11 Abis Main and Joker TS relation 4-121
Figure 4-12 PCM example 4-126
Figure 4-13 PCM fail example 4-127
Figure 4-14 Backhaul Configuration Methodology 4-128
Figure 4-15 RSM with EDGE TDMA priority 4-130
Figure 4-16 RSM with voice TDMA priority 4-132
Figure 4-17 PCU Request 4-135
Figure 4-18 Agprs EDGE principle 4-136
Figure 5-1 8-PSK and GMSK table usage 1 5-150
Figure 5-2 8-PSK and GMSK table usage 2 5-151
List of tables
Table i Document Organization -xiii
Table 1-1 Release Upgrade Path 1-3
Table 1-2 Supported WPS Configurations 1-3
Table 1-3 S8000 PEC Codes (BCF) 1-5
Table 1-4 S8000 PEC codes (CBCF) 1-5
Table 1-5 S12000 PEC Codes 1-6
Table 1-6 eCell EDGE Features 1-6
Table 1-7 850 MHz S8000 PEC Codes 1-7
Table 1-8 850 MHz S12000 PEC Codes 1-7
Table 1-9 DS512 Fiber Cable PEC codes 1-8
Table 1-10 PCUSN PEC Codes 1-9
Table 1-11 Single Server Configuration 1-10
Table 1-12 Integrated Server Configuration 1-10
Table 1-13 Dual Server Configuration 1-10
Table 1-14 Disk Array 1-11
Table 1-15 Server Disk Array Compatibility 1-11
Table 1-16 PCU OAM Server 1-12
Table 1-17 Workstation 1-12
Table 1-18 SDO Workstation 1-12
Table 1-19 Software Licenses 1-14
Table 1-20 V15.0 Optional Software Licenses 1-15
Table 1-21 CT2000 Optional Software Licenses 1-15
Table 1-22 CT7100 CT/CPT Optional Software Licenses 1-16
Table 2-1 GPRS Cell Options 2-18
Table 2-2 BSC 2-19
Table 2-3 BTS 2-19
Table 2-4 Powercontrol (BTS Associated Object) 2-22
Table 2-5 Transceiver 2-23

Contents xi
Table 2-6 Channel (Transceiver Associated Object 2-24

Table 2-7 PCU 2-24
Table 2-8 PCUSN OAM 2-25
Table 2-9 Unused OMC-R MMI Parameters: BTS 2-26
Table 2-10 Unused OMC-R MMI Parameters: Transceiver 2-27
Table 2-11 Unused PCUSN OAM Parameters 2-28
Table 2-12 EDGE BTS Configuration Parameters 2-37
Table 2-13 EDGE TDMA and Backhaul Configuration Parameters 2-39
Table 2-14 BDE Parameters 2-39
Table 3-1 New counters for V15.0 3-51
Table 3-2 EDGE Radio Quality Counters 3-52
Table 3-3 EDGE Link Adaptation Tables Fine-Tuning Counters 3-55
Table 3-4 GPRS/EDGE Agprs Counters 3-57
Table 3-5 EDGE Abis Counters 3-58
Table 3-6 Lack of EDGE Radio Resource Counters 3-59
Table 3-7 EDGE Traffic Profile and Throughput Counters 3-60
Table 3-8 GPRS Monitoring Improvement Counters 3-63
Table 4-1 DSO Jokers on Abis 4-67
Table 4-2 Example: MCS Distribution 4-69
Table 4-3 Example: Joker Requirement 4-70
Table 4-4 Example: Abis Dimensioning 4-71
Table 4-5 Example: Abis Increase 4-71
Table 4-6 MaxThroughput/MCS 4-85
Table 4-7 User Equipment Performance 4-88
Table 4-8 Base Station Performance 4-89
Table 4-9 Coupler losses 4-89
Table 4-10 Link Budget margins 4-89
Table 4-11 Selected environment correction 4-90
Table 4-12 C/I and C/N hypothesis for EDGE in different environments 4-90
Table 4-13 Data throughput, TU3 1800/1900 4-91
Table 4-14 Data throughput, TU50 1800/1900 4-91
Table 4-15 MCS usage distribution and throughput (TU3 1800, no FR with IR) 4-
92
Table 4-16 MCS usage distribution (TU3 1800 no FH with IR) 4-93
Table 4-17 MCS usage distribution and throughput (TU50 1800, no FR with IR)
4-93
Table 4-18 MCS usage distribution (TU50 1800 no FH with IR) 4-94
Table 4-19 Frequency hopping impact on EDGE MCS 4-98
Table 4-20 Frequency Load for MCS 4-99
Table 4-21 Mean Data Throughput / TS depending on FL (5 MHz) 4-100
Table 4-22 Mean Data Throughput / TS depending on FL (7.5 MHz) 4-100
Table 4-23 Mean Data Throughput / TS depending on FL (10 MHz) 4-101
Table 4-24 MCS usage distribution in TU3 (1800/1900, IR, mean BLER/MCS) 4-
103
Table 4-25 MCS usage distribution in RU130 (1800/1900, no IR, mean BLER/
MCS) 4-103
Table 4-26 Base Station capacity: 5 MHz 4-105
Table 4-27 Base Station capacity: 7.5 MHz 4-106
Table 4-28 Base Station capacity: 10MHz 4-108
Table 4-29 Site Capabilities 4-112
Table 4-30 TRX Capability 4-114

xii Contents
Table 4-31 MCS Joker requirements 4-122

Table 4-32 Example: DL, cell radius = 580 m, 1800/1900 MHz with IR, TU3 4-
122
Table 4-33 Example: DL, cell radius = 1.77 km, 1800/1900 MHz with IR, TU50
4-123
Table 4-34 Example: DL, cell radius = 580 m, 1800/1900 MHz with IR, TU3 4-
124
Table 4-35 Example: DL, cell radius = 1.77 km, 1800/1900 MHz with IR, TU50
4-124
Table 4-36 Joker DSO 4-133
Table 4-37 E1 with Four Joker DSO per Cell 4-140
Table 4-38 E1 with Three Joker DSO per Cell 4-140
Table 4-39 T1 with Four Joker DSO per Cell 4-141
Table 4-40 T1 with Three Joker DSO per Cell 4-141
Table 5-1 MEAN_BEP Values for 8-PSK 5-143
Table 5-2 MEAN_BEP Values for GMSK 5-145
Table 5-3 CV_BEP Values for GMSK and 8-PSK 5-146
Table 5-4 DL for 8-PSK Measurements Without Option Limitation (8-PSK
allowed) 5-147
Table 5-5 UL for 8-PSK Measurements Without Option Limitation (8-PSK
allowed) 5-148
Table 5-6 DL for GMSK/8-PSK Measurements with only GMSK in output, GMSK
Measurement without limitations 5-148
Table 5-7 Other UL table 5-149
Table 5-8 Hardware Replacement Scheme 5-154
Table 5-9 1800 MHz Phase In 5-155
Table 5-10 900 MHz Phase In 5-155
Table 5-11 900 MHz 5-157
Table 5-12 1800 MHz 5-159

xiii
About this document A

This document contains information on the deployment of a typical EDGE
GPRS network.
The deployment of an EDGE GPRS network is complex in the sense that no

two networks will be alike. Differences in philosophy of redundancy,
capacity, customer demands, and RF coverage will lead to many network
configurations of an EDGE GPRS network.
This guide will allow a reader to look at the different nodes of an EDGE
GPRS network. Upon reviewing the information relating to each node, the
reader will have an understanding as to what hardware, software, and datafill
should be in place to allow for a successful deployment of the EDGE GPRS
network.
Audience for this document 0

This guide is intended for individuals responsible for planning the
deployment of a EDGE GPRS network.
The reader should have a base understanding of data networks and general
telecommunications practices.
Organization of this document 0

This guide is organized into chapters as follows:
Table i
Document Organization
To learn more about See
An overview of the E-GPRS deployment Chapter 1, “E-GPRS Deployment Roadmap”

including upgrades, compatibilities, and
prerequisites
Datafill details for the new features in V15.0 Chapter 2, “BSS Datafill”
—sheet 1 of 2—

xiv Deployment Guide
Table i
Document Organization (continued)
To learn more about See
New counters for V15.0 and troubleshooting Chapter 3, “New Counters and Troubleshooting”
tips
Detailed Engineering methodologies for Chapter 4, “Engineering Methods: Interfaces”

EDGE deployments
Background information on EDGE parameters Chapter 5, “Support Material”

and settings
—sheet 2 of 2—
Indication of hypertext links 0

Hypertext links in this document are indicated in blue. If viewing a PDF
version of this document, click on the blue text to jump to the associated
section or page.
Related documents 0
• Wireless Services Provider Solutions Observation Counter Dictionary,
411-9001-125. Reference guide describing all GSM BSS network
observation counters managed through the OMC-R.
• DRX 900 MHz EFT Strategies Procedure for EFT Management in 900
MHz, PE/COM/INF/008263. Addresses the introduction of the EFT
specific to the DRX 900 ND3 and the implementation procedure of that
EFT into a network that contains DRX ND3.
• EDGE Engineering Guideline, PE/IRC/APP/008966. Provides
information to Engineering team and customers in order to help them
implement their Network with the introduction of EDGE in V15.
• 20231: SV1346.0 - EDGE Features, PE/DAS/DD/0006. Describes
features of EDGE networks.
• 19174: Data Backhaul Evolution, PE/DAS/DD/0008. Describes the data
backhaul evolution plan for EDGE networks.
• EDGE Configuration and Backhaul, DS/BSS/APP/5231. Describes the
operations performed on an in-service BSS network to configure the
EDGE feature.
• What’s New in the V15 BSS NTP Suite, 411-9001-088. Explains key
information for operators regarding the BSS NTP Suite.
• 20219 - SV1346.3 - EDGE Link Adaptation, PE/DAS/DD/0014.
Describes EDGE link adaptation function.

Deployment Guide xv
• DMS-MSC/Call Server Software Delta, 411-2231-199. Provides readers

with information changed by software release GSM15 / UMTS02.
• DMS-HLR Software Delta, 411-2831-199. Contains deltas that show the
software additions, deletions, and changes between individual software
releases.
• SGSN Components Reference Manual, 411-5221-060. Describes the
Passport components used to provision, modify, and monitor the 15000-
VSS Passport* platform functioning as a Serving General Packet Radio
Service (GPRS) Support Node (SGSN).
• Shasta GGSN Procedures Reference Manual, 411-5221-927. Explains the
main Operations, Administration & Maintenance (OA&M) procedures
for the Nortel Networks Shasta GGSN. It reflects the functionality present
in the GGSNS 3.1 software version.
• V15 Access Network Parameters User Guide, PE/IRC/APP/0119.
Describes the Nortel GPRS / EDGE Access network algorithms and
parameters from an engineering point of view.
• V15.0 Release Reference Book, PE/SYS/DPL/006555. Describes the
Release Reference Book (RRB) of the V15.0 version.

xvi Deployment Guide

1-1
E-GPRS Deployment Roadmap 1

This chapter provides an overview of what must be configured and a flow to
which nodes should be brought into service. Nodes can be brought up
independently of each other and then there will be a sequence to allow the
nodes to communicate.
V15.0 is a commercial release fully compatible with BSS V14.3 networks,

whose main features are EDGE and WPS. Information about WPS and GPRS
are provided to support EDGE deployment. V15.0 is dedicated to all
customers, and is available for NA, EMEA, ASPAC, CALA.
EDGE is an enhancement of the GPRS data communications protocols and

introduces new modulation and coding schemes. In addition to the GMSK
modulation used for GSM voice and GPRS, EDGE introduces 8-PSK
modulation. There are also new coding schemes introduced in EDGE that
allow data communications up to 59.2 kbit/s. Other sub-features of EDGE are
Link Adaptation and Incremental Redundancy that work to provide robust
communications in non-ideal RF conditions. EDGE is primarily an Access
(BSS) feature. When introducing EDGE there is a modification to the Abis
and Agprs backhaul links to accommodate the higher data rates. See Chapter
4, “Engineering Methods: Interfaces” for details on provisioning backhaul
resources for V15.0.
For the most part the Core (NSS and GPRS) are not impacted by the
introduction of EDGE. The release is optimized to work with the most recent
version of Core working at R99.
For more details on new features in V15.0 see What’s New in the V15 BSS
NTP Suite, 411-9001-088.
An example of an EDGE GPRS network is displayed in Figure 1-1.

1-2 Deployment Guide
Figure 1-1
E-GPRS network
Upgrade and Compatibility for V15.0 1

For further information please refer to V15.0 Release Reference Book, PE/
SYS/DPL/006555.
Nortel NSS Compatibility

The V15.0 is compatible with NSS15, NSS16, and NSS17. See Supported
WPS Configurations on page 1-3.
Nortel GPRS Packet Core Compatibility

The V15.0 is compatible with the GPRS5.0.
Norel SMLC Compatibility

The V15.0 is compatible with the SMLC3.0.
CT Compatibility
CT/CPT - CT7100
The Nortel Call Path Trace/Call Trace Module is kept in V8.0 version, but the
other CT7100 modules (NSS, BSS) will not be supported in V15.0. In V15.0
NIMS-PrOptimaTM will replace the CT7100 BSS and NSS modules.
CT2000
The V15.0 release is compatible with the CT2000 V3.

NIMS-PrOptimaTM
OAM content is driven by the first step of OAM convergence with the
introduction of NIMS-PrOptimaTM for GSM access.
BSS Release Upgrade Path POR

Table 1-1
Release Upgrade Path
From To V15.0 ChR
V14.2 Not Supported
V14.3 Not Supported
V14.3.0 (ML0) Supported
V14.3.1(ML1) Supported
V15.0 CuR Supported
Supported WPS Configurations

Table 1-2
Supported WPS Configurations
NSS HLR BSS
WPS IOC Phase 1 NSS15 patches GSM15 BSS V13.2
GSM16 BSS V14.3
WPS IOC Phase 2 NSS17 GSM16 BSS V15.0
GSM17 BSS V15.0
WPS FOC NSS17 GSM17 BSS V15.0
Note 1: All new functionality for WPS IOC Phase 2 is in the NSS15
patches. Existing functionality in the HLR and BSS.
Note 2: All new functionality for WPS IOC Phase 2 is in BSS V15.0. The
NSS15 patches are sourced in NSS17 and existing functionality is utilized
in the HLR.
Note 3: All new functionality for WPS FOC is in NSS17 for both the
HLR and MSC. Existing functionality in BSS V15.0.

Prerequisites 1
The following sections give the prerequisites for E-GPRS.
BTS
BTS EDGE hardware compatibility has been introduced in V12.4 for 1900
and in V13.2 in 850 (eDRX and ePA).
Even if the BTS 1900 and 850 MHz EDGE capabilities have been introduced
with BSS V14.3, it will be the first time their EDGE features will be enabled:
they are mandatory for V15.0 EDGE. S8000 configurations with cavities are
not supported in V15.0.
The BTS hardware and software considerations as baseline for V15 are:
• S8000 1900 MHz Indoor and Outdoor equipped with BCF and GTW
PROM.
• S8000 1900 MHz and 850 MHz Indoor and Outdoor equipped with
CBCF (Dual Band included).
• S8000 1800 MHz Indoor and Outdoor equipped with BCF and GTW
PROM.
• S8000 900 MHz Indoor and Outdoor equipped with BCFand GTW
PROM.
• eCell phase 2.
Note 1: EDGE requires the Dynamic Agprs feature (introduced in BSS

V14.2).
Note 2: V15.0 is required prior to E-GPRS activation.
1900 MHz: S8000 equipped with BCF (Indoor and Outdoor)

• BCF + GTW board (NTQA06AA) equipped with a new PROM upgrade
kit (NTQA06KA) is required, the upgrade being done on site. After
upgrade the PEC code of the board evolves to NTQA06AB.
• eDRX 1900 and ePA 1900 (BCF).

Table 1-3
S8000 PEC Codes (BCF)
Code DRX
NTQA88PA eDRX 1900 MHz
NTQA50GA ePA 1900 MHz
NTQA87TA Outdoor extension EDGE kit 1900
NTQA87UA Indoor extension EDGE kit 1900
1900 MHz: S8000 equipped with CBCF (Indoor and Outdoor)

• No restriction, all versions of CBCF (Equipped either with CMCF board
Ph1 or Ph2, or a mix of both) fully support the V15.0 EDGE features.
• eDRX 1900 and ePA 1900.
Table 1-4
S8000 PEC codes (CBCF)
Code DRX
NTQA87TA Outdoor extension Edge kit 1900
NTQA87UA Indoor extension Edge kit 1900
NTQA50RA HePA
1900 MHz: S12000 (Indoor and Outdoor)

• All the versions equipped with CBCF, S12000 fully support V15.0 EDGE
features.
Note: S12000 does not support CMCF Phase 1 (NTQA66CA).

Table 1-5
S12000 PEC Codes
Code DRX
NTQA87TA Outdoor extension Edge kit 1900
NTU497DA Cables for DRX kit; Outdoor
NTQA87UA Indoor extension Edge kit 1900
NTU497CA Cables for DRX kit; Indoor
NTQA50RA HePA
eCell (Indoor and Outdoor)

eCell Phase 2 fully supports V15.0 EDGE features.
Table 1-6
eCell EDGE Features
Code Description
NT0110DA Radio cabinet T1
NTDS03LA Market models Outdoor
NTDS03QB
NTDS03PB Market models Indoor
NTDS03KA
850 MHz: S8000 equipped with CBCF (Indoor and Outdoor)

Note: All versions of the 850 MHz S8000 support EDGE.
• No restriction, all versions of CBCF (Equipped either with CMCF board

phase 1 or phase 2, or a mix of both) fully support the V15.0 EDGE
features.

Table 1-7
850 MHz S8000 PEC Codes
Code DRX
NTQA88HA eDRX 850 MHz
NTQA37AA ePA 850 MHz
NTQA87XA Outdoor extension EDGE kit 850
NTQA87WA Indoor extension EDGE kit 850
850 MHz: S12000 (Indoor and Outdoor)

Note: All versions of the 850 MHz S12000 support EDGE.
• All the versions equipped with CBCF, S12000 fully support V15.0 EDGE
features.
Note: S12000 does not support the CMCF Phase 1 (NTQA66CA).
Table 1-8
850 MHz S12000 PEC Codes
Code DRX
NTQA88HA eDRX 850 MHz
NTQA37AA ePA 850 MHz
NTQA87XA Outdoor extension Edge kit 850
NTU497DA Cables for DRX kit; Outdoor
NTQA87WA Indoor extension Edge kit 850
NTU497CA Cables for DRX kit; Indoor
900 MHz & 1800MHz

See ePA 900/1800 and eDRX 900 Introduction on page 5-153 for
introdutionary information.

BSC
BSC2G
The BSC2G is not supported with V15.0.
BSCe3
The BSCe3 introduced in the BSS release V14.3 has been updated with an
improvement to throughput capacity. This improvement will enable the BSC
to reach the same level of capacity achieved in V14.3 when EDGE is
introduced.
This is achieved through the implementation of the DS512 Fiber cables. This
upgrade is highly recommended but is not mandatory. An Engineering
analysis is needed to determine if the DS512 cables are required (see
Engineering Methods: Interfaces on page 4-65).
The order code for the DS512 fiber cables are listed in Table 1-9.
Table 1-9
DS512 Fiber Cable PEC codes
Code Title
NTQE43BA Optical cable kit for BSCe3 (DS512)
NTQE0785 Individual Fiber Cables for BSCe3
The operating mode for BSCe3 upgrade is as follows:

• Upgrade to V15.0.
• Installation of the optical fiber.
• Enable the feature “switching capacity increase” at the OMC-R.
The complete installation procedure is contained in IM# 65-9218.
Note: The BSCe3 will not work properly at V14.3 with these cables
installed. These cables must be removed if it is necessary to fall back to
V14.3 from V15.0.
PCUSN
The PCUSN hardware and software considerations from BSS V14.3 are:
• PCUSN equipped with old TDM board.
• PCUSN equipped with new TDM board.

Note: V15.0 is required prior to E-GPRS activation.
No hardware changes are needed to the PCUSN when upgrading from V14.3
to V15.0 release. While a new TDM board is introduced with V15.0 it is not a
prerequisite for V15.0 release.
If during operation it becomes necessary to replace the existing TDM board it

is recommended to implement the new design. PEC codes for the new TDM
boards are listed in Table 1-10.
Table 1-10
PCUSN PEC Codes
Code DRX
NTFN93AB TDM Board with 2 ports DS3
NT0464AB TDM Board with 32 ports E1
OMC-R
The OCM-R hardware and software considerations are:
• SF880 with T3 disk array.
• E4500 (400 MHz) with T3 Disk array.
• E4500 (400 MHz) with A5200 Disk array.
Note: V15.0 is required prior to E-GPRS activation.
The only upgrade paths allowed to go to V15.0 are the following

• BSS Upgrade from V14.3 to V15.0.
The only OMC-R HW server supported during upgrade are:

• Upgrade SF880 with T3 in V14.3 to SF880 with T3 (V15.0).
• Upgrade E4500/400 MHz/T3 in V14.3 to E4500/400 MHz/T3 (V15.0).
• Upgrade E4500/400 MHz/A5200 V14.3 to E4500/400 MHz/A5200
(V15.0).
To keep the duration of an upgrade within an acceptable maintenance window,
the Centralized Installation and Upgrade Server (CIUS) functionality requires
a speed of 100 Mbit/s on the LAN between:
• CIUS and OMCR Servers.
• CIUS and Local Workstation.
• CIUS and SDO and PCU-OAM Workstation.

If a remote or local workstation (except SDO and PCU-OAM) is connected at

a lesser rate, apply procedure DS/OMC/APP/003.
The important thing to note is that NO HW Upgrade will be allowed during

upgrade and within V15.0 (apply for OMC-R server and disk array). All the
OMC-R HW upgrade should have been done in V14.3.
Table 1-11
Single Server Configuration
Equipment Description Disk Array V15
HC SUN UltraServer 4002 Supported

30 BSC / 2400 cells 400 MHz – 1024 Mbyte RAM
SUN UltraServer 450x A5200 or T3 Supported

400MHz – 1024Mbyte RAM
VHC SUN UltraServer 4002 Supported

SUN UltraServer 450x T3 only Supported

400 MHz – 1024 Mbyte RAM
For details on disk array size see Table 1-14.

Table 1-12
Integrated Server Configuration
30 BSC / 2400 cells SUN Fire V880 900 MHz – 8 GB RAM T3 only Supported
40 BSC / 3200 cells SUN Fire V880 900 MHz – 8 GB RAM T3 only Supported
Table 1-13
Dual Server Configuration
HC SUN UltraServer 4002 Supported

SUN UltraServer E450x A5200 or T3 Supported

—sheet 1 of 2—

Table 1-13
Dual Server Configuration (continued)
VHC SUN UltraServer 4002 Supported

SUN UltraServer E450x T3 Supported

—sheet 2 of 2—
Table 1-14
Disk Array
Equipment Description Disk Array
A5200 81 Gbyte (2) x (9 x 9) Gbyte Not supported
153 Gbyte (2) x (9 x 9 Gbyte + 1 x 73) Gbyte Supporteda
162 Gbyte 2 x (9 x 18) Gbyte Supported
T3 230 Gbyte 4 / 5 x 8 x 36 + hot spare (1x 36) Not supported
460 Gbyte 4 / 5 x 8 x 73 + hot spare (1x 73) Supported
a. A5200 153 Gbyte configuration is only provided as an upgrade kit for A5200 81GB and is not available
within V15.0. Upgrade needs to be done prior to upgrade in V15.0.
Table 1-15
Server Disk Array Compatibility
A5200 A5200 T3 460

153 Gbyte 162 Gbyte Gbyte
SUN UltraServer E450x Compatible Compatible Compatible

SUN Fire V880 Not Not Compatible

900 MHz – 8 GB RAM compatible compatible

Table 1-16
PCU OAM Server
Equipment Description V15
PCU OAM SUN Ultra 5 360 MHz – 256 Mbyte RAM Multi-pack 27 GB Supported
SUN Ultra 5 360 MHz – 256 Mbyte RAM Multi-pack 36 GB Supported
SUN Ultra 5 400 MHz – 256 Mbyte RAM Multi-pack 36 GB Supported
SUN Blade 150 650 MHz – 512 Mbyte RAM Multi-pack 36 GBa Supported
a. In the case of SF V880, PCU OAM and SDO functions are integrated within the server.
Table 1-17
Workstation
Workstations SUN ULTRA 5 360 MHz – 128 Mbyte of RAM Supported
SUN ULTRA 5 400 MHz – 128 Mbyte of RAM Supported
SUN Blade 150 650 MHz – 512 Mbyte RAM Nominal
Table 1-18
SDO Workstation
SDO SUN ULTRA 5 360 MHz – 128 Mbyte of RAM 27/36 Gbyte diska b Supported
SUN ULTRA 5 400 MHz – 128 Mbyte of RAM 27/36 Gbyte diska b Supported
SUN Blade 150 650 MHz – 512 Mbyte RAM Multi-pack 36 Gbytea b c Supported
a. Disk extension might be required according to counter nuMbyteer increase.

b. Multi-pack 27GB supports a maximum of 2400 cells. Multi-pack 36GB configuration supports 3200
cells on V13.2, V14.2 and V14.3. A confirmation is expected for V15.
c. In case of SF V880, PCU OAM and SDO functions are integrated within the server.
Tools 1
This section covers the tools required for the deployment of E-GRPS.
CT/CPT Hardware and Software

The PC for CT/CPT is not provided by Nortel Networks.

CT2000 Hardware and Software

The PC for CT2000 is not provided by Nortel Networks.
The minimum recommended hardware is as follows:

• Pentium IV 2.5 GHz or higher, 1 Gbyte or higher RAM, 10 Gbyte Hard
Disk at 7200 rpm (SW + Database).
• Graphical Device: 21 inches.
• Floppy disk + CD ROM drive.
Mandatory software (not provided by Nortel):

• OS: Microsoft Windows 2000 Service Pack 4 until V15.0 included (not
provided by Nortel).
• SW: Access 2000, Microsoft Office Pro 2000, Internet Explorer 6.0
The Workstation for CT2000 Plugins

• Ultra 5 or SB150, 400 MHz, 512 Mbyte RAM.
• Great than 1 Gbyte available for swap space.
CT7100 CT/CPT Hardware and Software

The PC for CT7100 is not provided by Nortel Networks.

• Pentium III 500 MHz, 512 Mbyte RAM, 10 Gbyte Hard Disk.

• OS: Microsoft Windows 2000 and XP.
• Internet Explorer 5.0 and Microsoft Office Pro 2000.
TIL & TML
The PC is not sold by Nortel Networks.

• Pentium III 500 MHz, 512 Mbyte RAM, 10 Gbyte Hard Disk.

• OS: Microsoft Windows 2000 or XP.

Note: Moving to Windows XP requires a PCMCIA Board change as the

old PCMCIA board does not have drivers for XP.
• Internet Explorer 5.0 and Microsoft Office Pro 2000.
NIMS - PrOptimaTM
NIMS-PrOptima™ Standalone Configuration (BSS only releases):
• Server: Fire V880 4x900 MHz, 8 Gbyte RAM, 12x73 Gbyte Hard Drive.
• Client: operating system Windows 2000 or XP.
NIMS-PrOptima™ PWI configuration (all Nortel domains):
• Server: PWI performance server.
• Client: PWI clients.
SW License 1
V15.0 BSS & OMC-R Base Software is shown in Table 1-19.
Table 1-19
Software Licenses
PEC Code Package Description
NTM502AAVA BSS V15.0 Base SW RTU BSS V15.0 Basic Package
NTM502AAYA BSS V14.3-V15.0 BASE SW UPG RTU BSS Upgrade v14.3 to v15.0
NTM503AGRA OMC-R Base TRIAL OMC-R SW: BSS SW module
NTM503AGSA OMC-R Base 1K DRX RTU
NTM503AGTA OMC-R Base 2.5K DRX RTU
NTM503AGUA OMC-R Base 5K DRX RTU
NTM503AGVA OMC-R Base 10K DRX RTU
NTM503AGWA OMC-R Base +2.5K DRX RTU

V15.0 Optional Software is shown in Table 1-20.

Table 1-20
V15.0 Optional Software Licenses
PEC Code Package Feature Title
NTM503ANHA DIRECTED RETRY W/O QUEUING SW RTU WPS IOC Phase 1 Directed
Retry without queuing on
BSCe3
NTM503ANEA GOLD PRIORITY SERVICE SW RTU WPS feature (on BSCe3)
NTM503ANFA BSS EDGE SW RTU EDGE Feature (20231, 24386,

20320, 20189, 19174? 24879,
20224,20219)
NTM503ADMA GPRS Base SW UG RTU GPRS Upgrade
NTM503ADJA PCUSN AGPRS Base SW RTU PCUSN AGPRS interface

software
NTM503ADHA PCUSN GB Interface Base SW RTU PCUSN Gb Interface software
NTM503ADKA QoS PCUSN QoS software RTU
CT2000 Optional Software is shown in Table 1-21.

Table 1-21
CT2000 Optional Software Licenses
NTM503AFQA CT2000 Base SW RTU - TRIAL CT2000 SW: BSS SW module
NTM503AFRA CT2000 Base SW RTU - 1000 DRX
NTM503AFSA CT2000 Base SW RTU - 2500 DRX
NTM503AFTA CT2000 Base SW RTU - 5000 DRX
NTM503AFUA CT2000 Base SW RTU - 10000 DRX
NTM503AKBA CT2000 Base SW RTU-+2500 DRX

CT7100 CT/CPT Optional Software is shown in Table 1-22.

Table 1-22
CT7100 CT/CPT Optional Software Licenses
NTM503AGCA CT/CT TRACE MOD. SW-TRIAL CT7100 CP/CPT SW module
NTM503AGDA CT/CT TRACE MOD. SW-1000 DRX
NTM503AGEA CT/CT TRACE MOD. SW-2500 DRX
NTM503AGFA CT/CT TRACE MOD. SW-5000 DRX
NTM503AGGA CT/CT TRACE MOD. SW-10000 DRX
NTM503AKAA CT/CT TRACE MOD. SW-+2500 DRX

2-17
BSS Datafill 2
This chapter includes information on the BSS datafill that is required to
deploy an EDGE GPRS network.
General GSM network engineering information is available in the GSM

training course NE2.
Backhaul Enhancement 2
In previous versions, the radio throughput per radio TS is limited to CS2, so
each radio resource is connected to one 16 kbit/s Abis and Agprs TS. In this
version new data coding schemes are introduced in order to increase the user
throughput. Because of radio improvements the backhaul has to be enhanced
to support higher data rates.
This evolution is described in 19174: Data Backhaul Evolution, PE/DAS/

DD/0008.
Note: The backhaul evolution on the Abis is not required to activate

EDGE, the throughput is then limited to MCS-2 for such a TDMA. On
that TDMA, the InitialMCS-UL and InitialMCS-DL are ignored and the
Link Adaptation function is de-activated, MS allocated on that TDMA are
only using MCS-2.
For more information, see 20231: SV1346.0 - EDGE Features, PE/DAS/DD/

0006.
REL'99 Activation: Radio

The MS does not need to be aware of the SGSN release to request an EDGE
TBF (only the EDGE activation presented in E-GPRS Activation is needed).
The BSS broadcasts to the MS the release supported by SGSN through the
“SGSNR” bit in the SI13.
Details are provided in the 20231: SV1346.0 - EDGE Features, PE/DAS/DD/

0006 (section 5.2.1).
It is recommended to keep the default value (“rel'98 or older”) for “First

EDGE Version.”

E-GPRS Activation
Prior to EDGE Activation, all MS are allocated in GPRS mode. The
“EGPRS-Services” parameter is used to activate EDGE in a given cell. No
hardware verification is done to control the activation in the target cell. If no
DRX is EDGE capable in the cell, the PCU will allocate all the EDGE MS in
GPRS mode. Detailed behavior is described in 20231: SV1346.0 - EDGE
Features, PE/DAS/DD/0006 (section 4.2.1).
When the parameter “EGPRS-Services” is activated, the BSC includes the

two fields “EGPRS_PACKET_CHANNEL_REQUEST” and
“BEP_PERIOD” in the “GPRS Cell Options.” For more information see
20231: SV1346.0 - EDGE Features, PE/DAS/DD/0006 (section 5.1.1).
This field “GPRS Cell Options” is present in the SI13. Table 2-1 presents the
correspondence between the Cell parameters on the OMC-R and the content
of the SI13 on the radio.
Table 2-1
GPRS Cell Options
Cell Parameters SI13 Format
EGPRS-Services (Class 3) 0|1 - ECPRS supported by the cell if the choice

bit is set to ‘1’
EGPRS_PACKET_CHANNEL_REQUEST (No <EGPRS_PACKET_CHANNEL_REQUEST :

parameter) bit> = ‘1’
BEP_PERIOD (Class 3) <BEP_PERIOD : bit(4)>
The BEP-PERIOD is used by the Link Adaptation functionality. For more

information see 20219 - SV1346.3 - EDGE Link Adaptation, PE/DAS/DD/
0014.
When the SI13 is modified, the PCU_BROADCAST_INFO_MODIFY is

sent to PCU with the updated information.
When EDGE is activated, the PCU uses the “Radio Access Capability”
parameter provided by SGSN or by MS to determine whether the MS should
be allocated in GPRS or EDGE Mode. For more information see 20231:
SV1346.0 - EDGE Features, PE/DAS/DD/0006 (TDMA section).
E-GPRS De-activation
When the EGPRS-Services flag is disabled, the BSC modifies the SI13
accordingly, but also removes all the jokers allocated to the PCU in that cell
(see 19174: Data Backhaul Evolution, PE/DAS/DD/0008 for details). All the

BSS Datafill 2-19
MS engaged into an EDGE TBF are released by PCU (note that those MS are
still allowed to establish a TBF in GPRS mode, only the EDGE service is de-
activated).
REL'99 Interaction
As described previously, the SGSN can be kept in rel'97 to introduce EDGE
on the BSS. The Gb interface is not changed for the first EDGE version, only
the radio interface evolves.
A full set of optional features have been introduced in rel'99 of the GPRS
specification. On the Radio the BSS provides indication of optional support in
the SI13:
• PFC_FEATURE_MODE
• DTM_SUPPORT
• BSS_PAGING_COORDINATION
The BSC always broadcasts the value '0' in the SI13 for those three fields.
Edge Configuration 2
The tables presented below summarize the parameters settable at OMC-R
MMI and PCUSN OAM in the GPRS V15.0 release.
OMC-R MMI Parameters

See V15 Access Network Parameters User Guide, PE/IRC/APP/0119.
Table 2-2
BSC
V12.4 V14.2 V15.0
Parameter Cls a b c default
bscGprsActivation 3 X X X X X disabled
Table 2-3
BTS
V12.4 V14.2 V15.0
agprsFilterCoefficient 3 X X 0
bEPPeriod 3 X 0
—sheet 1 of 4—

Table 2-3
BTS (continued)
V12.4 V14.2 V15.0
bsCvMax 3 X X X X X 1
btsSensitivity 3 X X X X X 0
dlGMSKMCS2UpperThreshold 3 X 0
dlGMSKMCS3UpperThreshold 3 X 0
dlMCS2UpperThreshold 3 X 0
edgeMixity 3 X 100
egprsServices 3 X disabled
gprsAvgParam
nAvgT 3 X X X X X 0
nAvgW 3 X X X X X 0
gprsBtsExtendedConf
gprsPreemption 3 X X X X yes
gprsPreemptionProtection 3 X X X X 10
minNbGprsTs 3 X X X X 0
N3103 3 X X X X X 5
btsSensitivityInnerZone 3 X X X 0
maxBsTransmitPowerInnerZone 3 X X X 2
CCCHGprsAtBtsLevel 3 X X disabled
—sheet 2 of 4—

BSS Datafill 2-21
Table 2-3
BTS (continued)
V12.4 V14.2 V15.0
targetThroughputStep 3 X X 0
minTargetThroughput 3 X X 0
RLCPollingTuning 3 X 0
gprsBtsLockExtendedConf
radioAllocator 2 X X X X X voice+dat
aCircuit
gprsCellActivation 3 X X X X X disabled
gprsPermittedAccess 3 X X X X X 0
jokerperMainTarget 3 X 0
onePhaseAccess 2 X disabled
onePhaseDnMsCapability 3 X 1
pan
panDec 3 X X X X X 0
panInc 3 X X X X X 0
panMax 3 X X X X X 0
routingArea 2 X X X X X 0
sGSNRelease 3 X 0
T3168 3 X X 0
T3192 3 X X 0 (500
ms)
ulGMSKMCS2UpperThreshold 3 X 0
ulGMSKMCS3UpperThreshold 3 X 0
ulMCS2UpperThreshold 3 X 0
—sheet 3 of 4—

Table 2-3
BTS (continued)
V12.4 V14.2 V15.0
—sheet 4 of 4—
Table 2-4
Powercontrol (BTS Associated Object)
V12.4 V14.2 V15.0
gprsQoS
admissionCtrlBronze 3 X X 0
admissionCtrlGold 3 X X 0
admissionCtrlSilver 3 X X 0
dwQoSCriterion 3 X X 0
minThroughputBronze 3 X X 0
minThroughputGold 3 X X 0
minThroughputSilver 3 X X 0
peakThroughputLimitation 3 X X 0
preemptionRatioGold 3 X X 0
preemptionRatioSilver 3 X X 0
upQoSCriterion 3 X X 0
voicePreemptionBronze 3 X X 0
voicePreemptionGold 3 X X 0
—sheet 1 of 2—

BSS Datafill 2-23
Table 2-4
Powercontrol (BTS Associated Object) (continued)
V12.4 V14.2 V15.0
voicePreemptionSilver 3 X X 0
—sheet 2 of 2—
Table 2-5
Transceiver
V12.4 V14.2 V15.0
codingScheme 2 X X X X X CS1
edgeDataServiceType 2 X capabilit
yNotRe
quested
edgeFavor 3 X 1
gprsTranscvLockExtendedConf
gprsPriority 2 X X X X 0
maxNbrPUDWithoutVChange 2 X X X X X 10
N3105Max 2 X X X X X 4
initialMCSDL 3 X MCS-2
initialMCSUL 3 X MCS-2
numberOfJokerDS0 2 X 0
packetAckTime
dwAckTime 3 X X X 1
upAckTime 3 X X X 1
ulBepPeriod 2 X 0

Table 2-6
Channel (Transceiver Associated Object
V12.4 V14.2 V15.0
channelType 2 X X X X X none
Table 2-7
PCU
V12.4 V14.2 V15.0
gprsPcuLockExtendedConf
agprsTsSharingProtection 2 X X 0 (10)
dynamicAgprsAllowed 2 X X disabled

BSS Datafill 2-25
PCUSN OAM Parameters

Table 2-8
PCUSN OAM
V12.4 V14.2 V15.0
Parameter Crtl a b c default
frAtmDlciSpProv
accounting (ac) No X X X X X off
committedBurstSize (bc) No X X X X X 64000
committedInformationRate (cir) No X X X X X 64000
excessBurstSize (be) No X X X X X 64000
maximumFrameSize (n203) No X X X X X 2100
measurementInterval (t) No X X X X X 0
rateEnforcement (re) No X X X X X off
gprsNsProv
nsAliveRetries No X X X X X 10
nsAliveTimer No X X X X X 3
nsBlockRetries No X X X X X 3
nsBlockTimer No X X X X X 3
nsResetRetries No X X X X X 5
nsResetTimer No X X X X X 3
nsTestTimer No X X X X X 30
nsUnblockRetries No X X X X X 3
gprsPcBssgpProv
bvcBlockRetries No X X X X X 3
bvcBlockUnblockTimer No X X X X X 15
bvcResetReqRetries No X X X X X 3
bvcResetReqTimer No X X X X X 60
—sheet 1 of 2—

Table 2-8
PCUSN OAM (continued)
V12.4 V14.2 V15.0
Parameter Crtl a b c default
bvcUnblockRetries No X X X X X 3
flowControlMaxDelay No X X 300
flowControlMaxRate No X X X X X 2000
msFlowCntlBucketSize No X X X X X 90
msLeakRate No X X X X X 0
suspendRetries No X X X X X 3
suspendTimer No X X X X X 5
tsFlowCntlBucketSize (tsBmax) No X X X X X 720
tsLeakRate No X X X X X 100
—sheet 2 of 2—
Unused GPRS Parameters

The tables below summarize the GPRS parameters still “reserved for future
use” in the GPRS V15.0 release.
Note: These parameters must be set to their default values at OMC-R

MMI and PCUSN OAM.
Table 2-9
Unused OMC-R MMI Parameters: BTS
Parameter Class Default
agprsHysteresis 3 0
agprsThreshold 3 0
drxTimerMax 3 0
gprsTimerWaitPUAM 3 500 ms
gprsTimerWaitRLC 3 500 ms
longTbfLossThroughput 3 0
—sheet 1 of 2—

BSS Datafill 2-27
Table 2-9
Unused OMC-R MMI Parameters: BTS (continued)
longTbfSizeThreshold 3 100
maxDnTbfP1P2Threshold 3 16
maxDnTbfPerTs 3 8
maxDwAssign 3 8
maxUpTbfP1P2Threshold 3 16
maxUpTbfPerTs 3 8
msCapWeightActive 2 yes
nAvgl 3 0
nbrFreeTchBeforeAnticipation 3 0
nbrFreeTchToEndAnticipation 3 0
speechOnHoppingTs 3 false
T3172 3 20
typeOfGprsAllocator 3 0
—sheet 2 of 2—
Table 2-10
Unused OMC-R MMI Parameters: Transceiver
allocBitmap
blockErrorRate 3 0
maxSize 3 0
dLPwrValue 3 0
maxNbrPDAAssig 2 5
maxNbrRLCEmptyBlock 2 10

Table 2-11
Unused PCUSN OAM Parameters
GprsPcBssgpProv
resumeTimer N.A. 5
resumeRetries N.A. 3
raCapabilityUpTimer N.A. 15
raCapabilityUpRetries
N.A. 3
EDGE Configuration Tool 2

This section defines the specification for the EDGE configuration tool.
It describes the operations performed on an in-service BSS network to

configure the EDGE feature and EDGE Backhaul.
Prerequisites
• The OMC-R must be already configured.
• The BSC must have e3 architecture.
Scope
• This document is applicable to V15.0.
• The EDGE configuration procedure applies to a V15.0 OMC-R with
operational V14.4 BSS entities.
For more information on the EDGE configuration procedure, see EDGE

Configuration and Backhaul, DS/BSS/APP/5231.
Tool Description
The configuration of the EDGE feature on BSS is based on a UNIX program
referred as “Tool” in the present document and installed on the OMC-R as a
plug in.
The Tool allows the application of these parameters on the BSS of an

OMC-R.
The purpose of the Tool is to configure EDGE parameters and/or EDGE

backhaul by execution of the MMI command files on the OMC-R. This

BSS Datafill 2-29
avoids manual operation and the configuration errors caused by the number
of affected parameters.
Figure 2-1
EDGE Tool Configuration Plug-In Interface Window
The principles of the Tool are listed below:

1. EDGE Cell Configuration:
The tool asks for the impacted BTS and EDGE setting values, it builds an
input file related to them. There is the possibility to load predefined
EDGE setting values from predefined configuration files.
EDGE Cell Input file for
Operator
configuration EDGE execution:
Inputs
action ds_EDGE.cfg
2. EDGE TDMA with pDTCH and Backhaul configuration:

The tool asks for the impacted TDMA and EDGE backhaul values, it

builds an input file related to them. There is the possibility to load

predefined EDGE setting values from predefined configuration file.
EDGE Input file for
Operator
backhaul EDGE execution:
Inputs
action ds_EDGE.cfg
3. Command Execution:
The tool generates output command files to activate the new EDGE
configuration or backhaul parameters
EDGE
Operator
execution
Input file
action
Edge TDMA and

Edge Cell Configuration Backhaul Configuration
bsc_all.cmd
bsc_bscNumber.cmd
btsSM_bscNumber_btsSMNumber.cmd
bts_bscNumber_btsSMNumber_btsNumber.cmd
bsc_all_Rev.cmd
bsc_bscNumber_Rev.cmd
btsSM_bscNumber_btsSMNumber_Rev.cmd
bts_bscNumber_btsSMNumber_btsNumber_Rev.cmd
tdma_bsc_all.cmd
tdma_bsc_bscNumber.cmd
tdma_btsSM_bscNumber_btsSMNumber.cmd
tdma_bts_bscNumber_btsSMNumber_btsNumber.cmd
tdma_bsc_all_Rev.cmd
tdma_bsc_bscNumber_Rev.cmd
tdma_btsSM_bscNumber_btsSMNumber_Rev.cmd
tdma_bts_bscNumber_btsSMNumber_btsNumber_Rev
EDGE Cell Configuration Input

The following section describes EDGE Tool cell configuration input.
EDGE Target Window

To identify all the concerned BTS, the operator has first to give the information
of (BSC, BTSSM, BTS ).
• The value for BSC may be bscId or all.

BSS Datafill 2-31
• The value for BTSSM may be btsSMId or all.

• The value for BTS may be btsId or all.
• The value for Setting is any predefined EDGE values or the Nortel default
one.
The operator clicks on the:

• “Setting” button to set a new EDGE values setting. Then the EDGE
setting window appears.
• “Add” button to add all the BTS related to the (BscId, BtsSmId, BtsId)
criterion with the EDGE values previously defined from EDGE setting
window. There is a check to ensure that a same BTS does not appear twice
with two different settings.
• “Remove” button to remove all the BTS related to the (BscId, BtsSmId,
BtsId) criterion.
• “Remove all” button to remove ALL the BTS. It means to reset the input
configuration file.
• “Done” button when the selection of BTS is done. It makes disappear the
EDGE setting window and the EDGE target window then saves the input
file.
• “Cancel” button to cancel all actions since the opening of “EDGE target”
window.

Bad Target Window

If in the loaded input files, any non valid settings and/or targets previously
defined in it are found because of OMC-R re-configuration, a Bad Target
window appears.
On this window, the “x” word means all possible values or setting definitions.
Example:
1. “x x x setting_3”: means that the setting_3 definition in the
input file has a syntax errors or does not exist. All BSS targets with this
setting are not possible. The “x” word means all possible values.
2. “4 2 0 x”: means that the BTS target with btsId=0 is not enabled
for the EDGE feature or does not exist. Targets with bscId=4, btsSMId=2
and btsId=0 are not valid with all definition setting.
3. “4 44 x x”: means that the btsSM target with btsSMId=44 is not
enabled for the EDGE feature or does not exist. Targets with bscId=4 and
btsSMId=44 are not valid with all BTS and all definition setting.
4. “3 x x x”: means that the BSC target with bscId=3 has not an e3
architecture or does not exist. Targets with bscId=3 are not valid with all
btsSM, all BTS and all definition setting.
5. “all x x x”: means that the all BSC targets can not be chosen
because one or more btsSM or BTS have not the EDGE feature enabled.

BSS Datafill 2-33
EDGE BTS Parameters Setting Window

To set the EDGE parameters, the operator has to give the information
described in the window hereafter.
Note: For EGPRS-Services : 0 = Disabled and 1 = Enabled

For InitialMCS-DL/UL: 1 = MCS1, 2 = MCS2,…, 9 = MCS9.
The operator clicks on the :

• “Save” button to save this EDGE setting. Before saving, checks are done
with the values.
• “Remove” button to remove the “Current EDGE Setting”
• “Quit” button to close the window
• “NO UPDATE” radio button to update or not the concerned parameter.
EDGE TDMA and Backhaul Input

The following section describes EDGE Tool TDMA and Backhaul
configuration input.

EDGE TDMA and Backhaul Target Window

• “Setting” button to set a new EDGE backhaul values setting. Then the
EDGE Backhaul setting window appears.
• “Add” button to add all the TDMA related to the (BscId, BtsSmId, BtsId)
criterion with the EDGE values previously defined from EDGE Backhaul
setting window. There is a check to ensure that a same TDMA does not
appear twice with two different settings.
• “Remove” button to remove all the TDMA related to the (BscId,
BtsSmId, BtsId) criterion.
• “Remove all” button to remove ALL the TDMA. It means to reset the
input configuration file.
• “Done” button when the selection of TDMA is done. It makes disappear
the EDGE Backhaul setting window and the EDGE Backhaul target
window then saves the input file.
• “Cancel” button to cancel all actions since the opening of “EDGE
Backhaul target” window.
The “CURRENT TDMA SETTING” window displays all information of the

TDMA corresponding to the selected bscId, btsSMId and btsId.
The operator clicks on the TDMA targets to select or deselect them regarding
to their parameters:
• “bsc” column gives the ID of an existing BSC equipment in the Data Base
for current OMC-R.
• “btsSM” column gives the ID of an existing btsSM in the Data Base for
the bscId.
• “bts” column gives the ID of an existing BTS equipment in the Data Base
for the btsSMId and bscId.

BSS Datafill 2-35
• “tdma” column gives the ID of an existing TDMA in the Data Base for
the bscId, btsSMId and btsId.
• “JokerSDO” column gives the numberOfJokerDS0 existing in the Data
Base for the TDMA ID.
• “ServiceType” column gives the edgeDataServiceType existing in the
Data Base for the TDMA ID.
EDGE TDMA and Backhaul Setting Window

• “Save” button to save this EDGE setting. Before saving, checks are done
with the values.
• “Remove” button to remove the “Current EDGE Setting”
• “Quit” button to close the window.
• “NO UPDATE” radio button to update or not the concerned parameter.
Tool File Input

The following code snippet shows an example of an EDGE Tool input file.
##############################################################
#
# Input file for EDGE parameters setting and targets
##############################################################
#
# Fichier d'entree pour l'outil de configuration : EDGE
##############################################################
#
# Target:bscId:btsSmId:btsId:policy
# Setting:policy:EGPRS-Services:BEP-PERIOD:
# DL_MCS2UpperThreshold:DL_MCS3UpperThreshold:

# DL_GMSK_MCS2UpperThreshold:DL_GMSK_MCS3UpperThreshold:
# UL_MCS2UpperThreshold:UL_MCS3UpperThreshold:
# UL_GMSK_MCS2UpperThreshold:UL_GMSK_MCS3UpperThreshold:
# SGSNRelease:EdgeMixity
#
# Backhaul:policy:edgeDataServiceType:EDGEFavor:
# UL-BEP_PERIOD:InitalMCS-DL:InitialMCS-UL:
# JokerperMainTarget:numberOfJokerDS0
# Tdma:bscId:btsSmId:btsId:default:tdmaId_list
#
##############################################################
#
# Example/Exemple :
# Setting:classical:Enabled:x:31:0:72:x:182:0:31:0:31:0:x:
# 136:182:0:31:0:rel'98:1
# Target:99:all:all:classical
#
# Backhaul:classical:fullCapabilityRequested:2.00:10:x:x:0:1
# Tdma:14:11:0:classical:1
##############################################################
#
# EDGE BACKHAUL DEFINITION :
Backhaul:default:fullCapabilityRequested:1.00:10:MCS2:MCS2:0:4
Backhaul:1:fullCapabilityRequested:1.00:10:MCS2:MCS2:0:1
# EDGE BACKHAUL TARGETS :
Tdma:14:6:0:1:0
Tdma:14:6:1:1:0
Tdma:14:6:2:1:0
Tdma:25:1:0:default:0
# EDGE BACKHAUL SITE TARGETS FOR RSM UPDATE :
RSM:14:15:11111111111111111111111111000000
RSM:25:1:11111111111111000000000000000000
RSM:25:16:00000000000000111111111111000000
# EDGE CONFIGURATION DEFINITION :
Setting:default:Enabled:10:31:0:72:136:182:199:31:0:31:0:72:13
6:182:199:31:0:
rel'98:1
# EDGE CONFIGURATION TARGETS :
Target:14:2:all:default
Target:30:all:all:default
Target:24:all:all:default
~
############################################################

BSS Datafill 2-37
Note: There must be no space, no tabulations in this lines that are not in
commentary. Anyway this file must not be modifying by a user. It is built
in the “EDGE Configuration” step with a Graphical tool. The file is used
to generate the command files.
EDGE BTS Configuration

The EDGE Tool file is “/CMN/data/plugins/inputFiles/EDGEPlugin/
ds_EDGE.cfg”
The file input is built by the previous operator input actions of “Add” and
“Remove.”
In this file, each lines is built like:
Target:BscId,BtsSMId,BtsId,Policy
Setting:Policy1:EDGEparam1,EDGEparam2, …. ,EDGEparam9
Where EDGEparam1 … EDGEparam25 are the 25 values as shown in Table

2-12. For more information see EDGE Configuration and Backhaul, DS/
BSS/APP/5231.
Table 2-12
EDGE BTS Configuration Parameters
MMI Label MMI Attribute Name BDE Attribute Object Default Range
Name Name Value
EGPRS-Services eGPRSServices eGPRSServices bts 1 01
SGSNRelease SGSNRelease SGSNRelease bts 0 01
EdgeMixity EdgeMixity eDGEMixity bts 1 0…100
BEP-PERIOD bEPPeriod bEPPeriod bts 10 0…15
DL_MCS2UpperThre DL_MCS2UpperThre dlMCS2UpperThresh bts 31 0…255

shold shold old

shold shold old

shold shold old

shold shold old

shold shold old
—sheet 1 of 2—

Table 2-12
EDGE BTS Configuration Parameters (continued)
MMI Label MMI Attribute Name BDE Attribute Object Default Range
Name Name Value

shold shold old
DL_GMSK_MCS2Up DL_GMSK_MCS2Up dlGMSKMCS2Upper bts 31 0…255

perThreshold perThreshold Threshold
DL_GMSK_MCS3Up DL_GMSK_MCS3Up dlGMSKMCS3Upper bts 0 0…255

UL_MCS2UpperThre UL_ ulMCS2UpperThresh bts 31 0…255

shold MCS2UpperThreshol old
d

d

d

d

d

d
UL_GMSK_MCS2Up UL_GMSK_MCS2Up ulGMSKMCS2Upper bts 31 0…255

UL_GMSK_MCS3Up UL_GMSK_MCS3Up ulGMSKMCS3Upper bts 0 0…255

—sheet 2 of 2—
EDGE TDMA and Backhaul

File is “/CMN/data/plugins/inputFiles/EDGEPlugin/ds_EDGE.cfg”
The file input is built by the previous operator input actions of “Add” and
“Remove” actions.

BSS Datafill 2-39
In this file, each lines is built like :
Tdma:BscId:BtsSMId:BtsId:Policy:tdma1:…:tdmaN
Backhaul:Policy:BkHparam1, BkHaulParam2
Where BkHparam1 and BkHaulParam2 are the 2 values as shown in Table 2-

13:
Table 2-13
EDGE TDMA and Backhaul Configuration Parameters
MMI Label MMI Attribute BDE Attribute Object Default Range

Name Name Name Value
edgeDataServiceT edgeDataServiceT edgeDataServiceT transcv capability CapabilityN

ype ype ype NotReque otRequeste
sted d/
fullCapabilit
yRequested
EDGEFavor EDGEFavor eDGEFavor transcv 1 1:0,04:…5
InitalMCS-DL InitialMCS-DL initialMCSDL transcv 2 0235678

9
UL-BEP_PERIOD UL-BEP_PERIOD ulBepPeriod transcv 10 0…15
InitialMCS-UL InitialMCS-UL initialMCSUL transcv 2 0235678

9
JokerperMainTarg JokerperMainTarg jokerperMainTarg transcv 4 0…4

et et et
numberOfJokerD numberOfJokerD numberOfJokerD transcv 4 0…4

S0 S0 S0
Before applying the EDGE Backhaul configuration, some parameters of the

Data Base (BDE) are checked as in Table 2-14:
Table 2-14
BDE Parameters

radioSMask radioSMask radioSMask btsSM
—sheet 1 of 2—

Table 2-14
BDE Parameters (continued)

edgeDataServiceTy edgeDataServiceTy edgeDataServiceTy transcv capabili Capabili

pe pe pe tyNotRe tyNotRe
quested quested
/
fullCap
abilityR
equeste
d
numberOfJokerDS0 numberOfJokerDS0 numberOfJokerDS0 transcv 4 0…4
codingSheme codingSheme codingSheme transcv 2 1…4
transcvId transcvId transcvId transcv
priority priority priority transcv
pcmCircuit pcmCId pcmCId pcmC 0…

167/129
pcmCType pcmCType pcmCType pcmC e1/t1
—sheet 2 of 2—

BSS Datafill 2-41
EDGE Backhaul Algorithm

See Figure 2-2 for a task-flow for the EDGE Backhaul configuration.
Figure 2-2
EDGE Backhaul Algorithm
BSS Check
Select bsc, btsSM, bts, and TDMA
Select parameters to modify
No Do parameters
change?
Yes
No
Does DS0
number Reselect
increase? number of
Jokers
Yes
Stop and
Is Abis No exit
Decision
capability ok?
Yes
Calculate
New RSM
Generate MMI command file
Stop tool execution No

Generate log file Auto-exection?
Exit with error code
Yes
Generate log
Execute MMI command file file and exit

Radio Site Mask Algorithm

The calculation of the Radio Site Mask (RSM) is implemented in
coordination with CT2000, BSC, and Engineering teams. This is done only if
the increase of Abis capacity request needs an update of the RSM.
See Figure 2-3 for the configuration logic.
Figure 2-3
EDGE Radio Site Mask Algorithm
Abis increase requested
Can request fit Yes

into exisiting
resource?
No Configure EDGE backhaul

parameters including default
codingScheme parameter
Abis capacity Abis or RSM is RSM capacity

not enough not enough? not enough
Create a new PCM Accept the new RadioSiteMask

or calculated by the tool
Modify previous entries of or
TDMA numberOfJokerDS0 Modify previous entries of
TDMA numberOfJokerDS0
Ensure that new Abis capacity request fits into existing resource
This check consists in testing if the new joker DS0 demand can fit into
existing Abis.
Consider:
1. TDMAs are indexed with parameter TDMANb; total number of TDMAs
is named NmaxTDMA.
TDMAs are ordered as a function of their priority parameter, from the
highest (0) to the smallest. For same value of priority, they are ordered
function of their number, from the smallest to the highest. TDMAList is
the list of thus ordered TDMA.
Among TDMAs, there are:

BSS Datafill 2-43
— The Edge TDMAs with numberOfJokerDS0 > 0, requiring (2 +

numberOfJokerDS0(TDMANb)) DS0.
— The normal TDMAs with numberOfJokerDS0 = 0, requiring 2 DS0.
— Total number of Jokers DS0 is noted NmaxJokerDS0.
2. The existing PCMs connected to the site:
— The total number of PCM is named NmaxPCM.
— One PCM is indexed with parameter PCMNb.
3. The maximum number of DS0 available for traffic and Lapd signalization
is noted NmaxRSM:
— NmaxRSM = 31 in case of E1 PCM type.
— NmaxRSM = 24 in case of T1 PCM type.
The minimum number of time-slots equal to 1 needed in site RadioSiteMask

is RSMmin. It can be incremented while running algorithm.
RSMmin = Trunc[2 * NmaxTDMA / (NmaxPCM - {1 if redundant PCM})]1
+ Round [NmaxJokerDS0 / (NmaxPCM - {1 if redundant PCM})]2
+ (number of Secondary LAPDLink)
The maximum number of time-slots equal to 1 we can fit in site RadioSiteMask

RSMmax depends of the reserved ones:
• Tei correspondent number depending of the PCM type (E1 or T1). All
time-slots less or equal to Tei number are reserved.
• Pcm number if different from Tei number in case of a cross connect
configuration.
• RSM offset. The number of reserved time-slots is equal to RSM offset.
• Other Tei and Pcm time-slots numbers corresponding to other sites in case
of a cross connect configuration
RSMmax = NmaxRSM - reservedTimeSlots
We will note RSMneed(PCMNb) the number of time-slots equal to 1 required

in RadioSiteMask of PCM indexed PCMNb to satisfy all TDMA demands. It
is incremented while running algorithm.
The check is obtained applying:
1Trunc: integer value part of number (+1 if odd number)

2Round : integer value part of number part

WHILE (RSMmin <= RSMmax) and (at least one TDMA with joker not
mapped)
RSMneed(PCMNb) = 0, for all PCMs
WHILE (RSMmin <= RSMmax)
Rest = RSMmin - RSMneed(PCMNb)
numberbDS0(TDMANb) = 2 + numberOfJokerDS0(TDMANb)
IF (Rest >= numberbDS0(TDMANb))
RSMneed(PCMNb) = RSMneed(PCMNb) + numberbDS0(TDMANb)
Increment TDMANb (look for next TDMA)
ELSE
Increment PCMNb (look for next PCM)
END IF
END WHILE
IF (at least one TDMA with joker not mapped)
Increment RSMmin
END IF
END WHILE
IF (at least one TDMA is not mapped)
The check is FALSE
ELSE
The check is OK
New RadioSiteMask is calculated for impacted sites
END IF

BSS Datafill 2-45
Checks Performed by the Tool

Checks are performed when the operator saves the EDGE Setting and BTS
targets or generate MMI command files from input file.
If one of these conditions is met, an ERROR or WARNING message will be

displayed on the screen (and) on the log file if necessary:
1. The tool cannot connect to the OMC-R data base (BDE).
2. No compatible target. Only compatible targets are treated:
— OMC-R : must be already configured.
— BSC : must have an e3 architecture.
— SITE : must be one of S8000, S12000, e-Cell.
— Tdma : must have a PDTCH
3. The target to process (identified by bscId, btsSMId, btsId) is duplicated.
4. The value of the input parameters is not compliant with the range of
values allowed by the MMI configuration. Further details are provided in
NRP.
5. No parameter setting definition name given.
6. No EDGE parameter to update.
7. New Abis capacity request can not fit into existing resource.
8. New Radio Site Mask must be calculated or number of Jokers
redefinition.
NRP
An NRP is needed to configure the EDGE function. No control is done on the
activation of the backhaul nor on the activation of CCCH@BTS feature.
The NRP allows the configuration of all the parameters available on the
OMC-R MMI and relative to the different EDGE Features described in this
document such as:
On bts object:
• SGSNRelease
• EGPRS-Services
• BEP-PERIOD
• DL_MCS2UpperThreshold

• UL_MCS2UpperThreshold
• DL_GMSK_MCS2UpperThreshold
• DL_GMSK_MCS3UpperThreshold
• UL_GMSK_MCS2UpperThreshold
• UL_GMSK_MCS3UpperThreshold
• EdgeMixity
On transceiver object:
• InitialMCS-UL
• InitialMCS-DL
• EDGEFavor
• JokerperMainTarget
Tool Options
The tool is delivered as a plug-in.
• log log_file: To print all output in the log_file. The default log file is:
/var/local/oam/ds_ EDGE.log
• file conf_file: To take as input the configuration file conf_file.
The default configuration file is:
/CMN/data/plugins/inputFiles/EDGEPlugin/ds_EDGE.cfg
• action type: To configure EDGE parameters type = configure.
To configure EDGE backhaul type = backhaul.
• mode type: To execute EDGE command files manually type = manual.
To execute EDGE command files automatically type = automatic.
Two different modes of tool execution are available:
Automatic Mode:
• If only a small number of BTS objects are involved in the operation and if
the confidence level is high, the operator may choose to execute directly
all the command files generated.

BSS Datafill 2-47
— Use option -mode automatic
Manual Mode:
• This is the default mode. All the command files will be generated but not
executed.
— Use option -mode manual
Tool Output
For each line in the configuration file, the tool generates command files
containing OMC-R commands that will be executed automatically by way of
the MmiExecuteOneCommand.x available on the OMC-R, or manually by
the operator.
All command files are located in or under the directory:
/OMC/cmdFile/root/oam/EDGE/
There are 3 classes for command files generated:

1. One top command file.This file is unique for each execution of the tool. It
calls all other command files generated by the tool.
2. One command file for each BSC
3. One command file for each BTSSM of a BSC
In order to restore the BSS to its original state, the tool also generates a set of
command files for fallback that can be executed manually by the operator in
case of problems during EDGE configuration. The names of these files have
the key word “REV.”
Command Files Generated

The tool generates four types of OMC-R command files are created in the
directory /OMC/cmdFile/root/oam/EDGEPlugin/.
Note: Command files are generated only if there are no errors found in
the configuration file.
EDGE BTS Configuration Command Files

Top command file and its fallback file:
config_bsc_all.cmd
config_bsc_all_Rev.cmd
One command file for each BSC and its fallback file:
config_bsc_bscNumber.cmd
config_bsc_bscNumber_Rev.cmd

One command file for each BtsSM of a BSC and its fallback file:
config_btsSM_bscNumber_btsSMNumber.cmd
config_btsSM_bscNumber_btsSMNumber_Rev.cmd
One command file for each BTS of a btsSM and its fallback file:
config_bts_bscNumber_btsSMNumber_btsNumber.cmd
config_bts_bscNumber_btsSMNumber_btsNumber_Rev.cmd
EDGE TDMA and Backhaul Command Files

Top command file and its fallback file:
backhaul_bsc_all.cmd
backhaul_bsc_all_Rev.cmd
One command file for each BSC and its fallback file:
backhaul_bsc_bscNumber.cmd
backhaul_bsc_bscNumber_Rev.cmd
One command file for each btsSM of a BSC and its fallback file:
backhaul_btsSM_bscNumber_btsSMNumber.cmd
backhaul_btsSM_bscNumber_btsSMNumber_Rev.cmd
One command file for each BTS of a btsSM and its fallback file:
backhaul_bts_bscNumber_btsSMNumber_btsNumber.cmd
backhaul_bts_bscNumber_btsSMNumber_btsNumber_Rev.cmd
For EDGE BACKHAUL, the tool automatically sets the “codingScheme”

parameter to its default value: “cs2.”
LOG File
The tool logs all relevant information and messages in a log file. If not
specified when executing the tool, the default log file is:
/var/local/oam/ds_EDGE.log
NSS Core Datafill 2

There are no changes to the NSS Core Datafill for introduction of V15.0
EDGE. For the MSC refer to DMS-MSC/Call Server Software Delta,
411-2231-199 for parameter settings and for the HLR refer to DMS-HLR
Software Delta, 411-2831-199.
GPRS Core Datafill 2

There are no changes to the GPRS Core (SGSN or GGSN) Datafill for
introduction of V15.0 EDGE. Refer to SGSN Components Reference Manual,

BSS Datafill 2-49
411-5221-060 and Shasta GGSN Procedures Reference Manual,

411-5221-927 for parameter settings.


3-51
New Counters and Troubleshooting 3

This section deals with new counters that have been introduced into the BSS
software in V15.0 that could be used to troubleshoot EDGE networks.
Existing GPRS counters are useful when deploying EDGE. To troubleshoot
an EDGE network, use standard GSM troubleshooting principles as provided
in GSM training courses (OM1, OM9, and NE2).
For more information on E-GPRS counters see Wireless Services Provider

Solutions Observation Counter Dictionary, 411-9001-125. For more
information on GSM troubleshooting principles contact Nortel Networks to
arrange for a training course.
Table 3-1 shows the new counters introduced in V15.0.

Table 3-1
New counters for V15.0
Counter Type: Number of Counters
EDGE Radio Quality 9 counters
EDGE Link Adaptation Tables Fine-Tuning 42 counters
GPRS/EDGE Agprs 13 counters
EDGE Abis 3 counters
Lack of EDGE Radio Resource 4 counters
EDGE Traffic Profile and Throughput 9 counters
GPRS Monitoring Improvement 7 counters
TOTAL 87 counters

EDGE Radio Quality 3

To characterize the UL/DL radio quality for EDGE:
• UL MEAN_BEP.
• DL GMSK MEAN_BEP.
• DL 8-PSK MEAN_BEP.
Table 3-2
EDGE Radio Quality Counters
Counter Range ID/ Type Class/ Src Feature

SubID Object
pcuEdgeDnCum8PskMeanBep 0 to 15102/0 CUM TDMA PCU GPRS

4294967296 TBF
improve
ment
pcuEdgeDnNbs8PskMeanBep 15102/0 NBS TDMA
pcuEdgeDnCumGmskMeanBep 0 to 15103/0 CUM TDMA PCU GPRS

4294967296 TBF
improve
ment
pcuEdgeDnNbsGmskMeanBep 15103/0 NBS TDMA
pcuEdgeUpCumMeanBep 0 to 15104/0 CUM TDMA PCU GPRS

4294967296
pcuEdgeUpNbsMeanBep 15104/0 NBS TDMA
pcuEdgeDnAvg8PskMeanBep 15102/0 AVG TDMA
pcuEdgeDnAvgGmskMeanBep 15103/0 AVG TDMA
pcuEdgeUpAvgMeanBep 0 to 15104/0 AVG TDMA/ PCU GPRS

4294967296 cell TBF
improve
ment
Details:
• pcuEdgeDnCum8PskMeanBep
— Function: Number of iteration samples for
pcuDyAgprsNbTimeslotsCumCumulative value of the 8PSK_BEP
derived from the 8PSK_MEAN_BEP received from a MS in this

TDMA in the EGPRS BEP Link Quality Measurements

(8PSK_MEAN_BEP).
— Event: Reception of an EGPRS Packet Downlink Ack/Nack by an
EGPRS DL TBF on this TDMA, containing an 8PSK_MEAN_BEP
value set in the EGPRS BEP link quality measurements.
Note 1: MEAN_BEP is calculated and filtered in a linear scale but

mapped to a logarithmic scale for reporting as defined in 3GPP 05.08, so
for the processing of the average value, the log10(actual BEP) is used
(value between 0.60 and 3.60 as defined in 3GPP05.08 chapter 8.2.5).
Note 2: MEAN_BEP is used to derive the actual BEP reported in the

counter. For more information see Wireless Services Provider Solutions
Observation Counter Dictionary, 411-9001-125 Annex A.
• pcuEdgeDnNbs8PskMeanBep
• pcuEdgeDnCumGmskMeanBep
pcuDyAgprsNbTimeslotsCumCumulative value of the GMSK_BEP
derived from the GMSK_MEAN_BEP received from a MS in this
TDMA in the EGPRS BEP Link Quality Measurements
(GMSK_MEAN_BEP).
— Event: Reception of an EGPRS Packet Downlink Ack/Nack by an
EGPRS DL TBF on this TDMA, containing a GSMK_MEAN_BEP
value set in the EGPRS BEP link quality measurements.

mapped to a logarithmic scale for reporting as defined in 3GPP 05.08, so
for the processing of the average value, the log10(actual BEP) is used
(value between 0.60 and 3.60 as defined in 3GPP05.08 chapter 8.2.5).
Note 2: MEAN_BEP is used to derive the actual BEP reported in the

• pcuEdgeDnNbsGmskMeanBep
• pcuEdgeUpCumMeanBep
pcuDyAgprsNbTimeslotsCumCumulated value of the assumed BEP
received by the PCU in each EGPRS RLC data block on this TDMA.
— Event: Receipt of a TRAU frame without BFI by an EDGE TBF on
this TDMA. Upon receipt of an EGPRS RLC/MAC block by a

EGPRS TBF on this TDMA, the MEAN_BEP is used to derived the

assumed BER. This assumed BEP is cumulated in the
pcuEdgeUpCumMeanBep counter.
Note 1: All frames received in an EGPRS TBF are taken into account
except the one with BFI. In the special case where the MS started the UL
TBF on another TDMA, the MEAN_BEP for this TBF are ignored until
the PACKET CONTROL ACK is received on the initial TDMA.

mapped to a logarithmic scale for reporting as defined in TRAU Frame I/
F, so for the processing of the average value, the log10(actual BEP) is
used (value between 0.60 and 3.60)
Note 3: The MEAN_BEP is used to derive the actual BEP reported in the
• pcuEdgeUpNbsMeanBep
• pcuEdgeDnAvg8PskMeanBep
• pcuEdgeDnAvgGmskMeanBep
• pcuEdgeUpAvgMeanBep
pcuDyAgprsNbTimeslotsCumTBD.
— Event: TBD.
EDGE Link Adaptation Tables Fine-Tuning 3

To characterize:
• UL/DL radio BLER per MCS.
• UL/DL effective throughput per MCS.
• UL/DL MCS downgraded due to non-Radio limitations (backhaul or
GPRS/EDGE multiplexing).

Table 3-3
EDGE Link Adaptation Tables Fine-Tuning Counters

SubID Object
pcuEdgeMcsXRequestRetransDat 0 to 1514X/0 CUM TDMA PCU EDGE

aBlockDn X=2,3,5 tp 9 4294967295 link
adapt
pcuEdgeLADnTargetedTransmitte 0 to 1515X/0 CUM TDMA PCU EDGE

dMcsX X=2,3,5 tp 9 4294967295 link
adapt
pcuEdgeMcsXRequestRetransDat 1517X/0 CUM TDMA

aBlockUp X=2,3,5 tp 9
pcuEdgeLAUpTargetedTransmitte 0 to 1518X/0 CUM TDMA PCU EDGE

dMcsX X=2,3,5 tp 9 4294967295 link
adapt
pcuEdgeDnTransmittedMcsX 0 to 1513X/0 CUM TDMA PCU GPRS

X=2,3,5 tp 9 4294967296 TBF
improve
ment
pcuEdgeUpTransmittedMcsX 0 to 15162/0 CUM TDMA PCU GPRS

X=2,3,5 tp 9 4294967296 TBF
improve
ment
Considerations:
• pcuEdgeMcsXRequestRetransDataBlockDn\Up= All Dn\Up blocks sent
in MCSX and nacked
• pcuEdgeLADn\UpTargetedTransmittedMcsX= All Dn\Up blocks LA-
commanded in MCSX and sent in MCSX
• pcuEdgeDn\UpTransmittedMcsX= All Dn\Up blocks sent in MCSX
Details:
• pcuEdgeMcsXRequestRetransDataBlockDn X=2,3,5 tp 9
pcuDyAgprsNbTimeslotsCumCumulative number of EDGE RLC
Data Blocks transmitted in MCSX by PCU in the DL direction.

— Event: An EDGE DL radio data block targeted by LA in MCSX and

sent in MCSX (for the first time (i.e. fresh block) or retransmitted) is
NACK by MS in PDAN.
• pcuEdgeLADnTargetedTransmittedMcsX X=2,3,5 tp 9
— Event: An EDGE DL radio data block targeted by LA in MCS5 ad
sent in MCSX (for the first time (i.e. fresh block) or retransmitted).
• pcuEdgeMcsXRequestRetransDataBlockUp X=2,3,5 tp 9
• pcuEdgeLAUpTargetedTransmittedMcsX X=2,3,5 tp 9
Data Blocks transmitted in MCSX by MS in the UL direction.
— Event: Transmission by the MS of a data block inMCS2 whenMCS2
is the coding scheme commanded by the LA.
• pcuEdgeDnTransmittedMcsX X=2,3,5 tp 9
— Event: An EDGE DL radio data block sent by PCU in MCS2 (for the
first time (i.e. fresh block) or retransmitted).
• pcuEdgeUpTransmittedMcsX X=2,3,5 tp 9
Data Blocks that are transmitted in MCSX by MS in the UL direction.
— Event: Reception of an EDGE UL radio data block in MCS2 (with
frame validity bit set to 0 or 1).
GPRS/EDGE Agprs 3
To characterize:
• The number of Agprs Joker TS allocated to the cell by the BSC.
• The UL/DL AGPRS PCM resource occupancy.
• The cell load and the number of allocated Agprs TS for the dynamic
Agprs.

Table 3-4
GPRS/EDGE Agprs Counters
Counter Range ID/ Type Class/ Src

SubID Object
pcuEdgeAgprsMainNbofBlocksDn 15110/0 CUM CELL
pcuEdgeDynAgprsJokerCumNbTimeslot 15118/0 CUM CELL
pcuEdgeDynAgprsJokerNbsNbTimeslot 15118/0 NBS CELL
pcuEdgeDynAgprsJokerAvgNbTimeslot 15118/0 AVG CELL
pcuEdgeDynAgprsJokerMinNbTimeslot 15118/0 MIN CELL
pcuEdgeDynAgprsJokerMaxNbTimeslot 15118/0 MAX CELL
pcuEdgeAgprsJokerNbofBlocksDn 15119/0 CUM CELL
pcuEdgeAgprsMainNbofBlocksUp 15127/0 CUM CELL
pcuEdgeAgprsJokerNbofBlocksUp 15128/0 CUM CELL
pcuDyAgprsNbTimeslotsCum 0 to 15075/1 CUM CELL/ PCU

4294967295 bts
pcuDyAgprsNbTimeslotsNbs 0 to 15075/1 NBS CELL/ PCU

4294967295 bts
pcuDyAgprsLoadCriterionCum 15076/0 CUM CELL
pcuDyAgprsLoadCriterionNbs 15076/0 NBS CELL
Details:
• pcuEdgeAgprsMainNbofBlocksDn
• pcuEdgeDynAgprsJokerCumNbTimeslot
• pcuEdgeDynAgprsJokerNbsNbTimeslot
• pcuEdgeDynAgprsJokerAvgNbTimeslot
• pcuEdgeDynAgprsJokerMinNbTimeslot
• pcuEdgeDynAgprsJokerMaxNbTimeslot
• pcuEdgeAgprsJokerNbofBlocksDn
• pcuEdgeAgprsMainNbofBlocksUp
• pcuEdgeAgprsJokerNbofBlocksUp

• pcuDyAgprsNbTimeslotsCum
pcuDyAgprsNbTimeslotsCumCumulative number of Agprs timeslots
allocated in the cell by the BSC. This correspond to the formula: sum
(dyAgprsNbTs<i>). The value dyAgprsNbTs<i> is the number of
AgprsTS allocated in the cell at the <i>th sample.
— Event: Updated after every cell load calculation.
Note 1: This counter is based on 16kbps TS on the Agprs (this means

both joker and main channels).
Note 2: When the cell is set as the most or less loaded cell several times
in a row, the load criterion is not computed, thus the counter is not
incremented.
• pcuDyAgprsNbTimeslotsNbs
pcuDyAgprsNbTimeslotsCum.
— Event: Updated after every cell load calculation.
Note 1: This counter is based on 16kbps TS on the Agprs (this means

both joker and main channels).
Note 2: When the cell is set as the most or less loaded cell several times
in a row, the load criterion is not computed, thus the counter is not
incremented.
• pcuDyAgprsLoadCriterionCum
• pcuDyAgprsLoadCriterionNbs
EDGE Abis 3
To detect a lack of EDGE Abis PCM jocker TS.
Table 3-5
EDGE Abis Counters
Counter ID/SubID Type Class
pcuEdgeLackAbisJokerTSCum 15129/0 CUM TDMA
pcuEdgeLackAbisJokerTSNbs 15129/0 NBS TDMA
—sheet 1 of 2—

Table 3-5
EDGE Abis Counters (continued)
Counter ID/SubID Type Class
pcuEdgeLackAbisJokerTSAvg 15129/0 AVG TDMA
—sheet 2 of 2—
Details:
• pcuEdgeLackAbisJokerTSCum
• pcuEdgeLackAbisJokerTSNbs
• pcuEdgeLackAbisJokerTSAvg
Lack of EDGE Radio Resource 3

To detect a lack of EDGE resource configured in the cell.
Table 3-6
Lack of EDGE Radio Resource Counters

SubID Object
pcuEdgeDowngradedTbf 15111/0 CUM CELL
pcuEdgeTbfEstReq 0 to 4294967296 15122/0 CUM CELL/ PCU GPRS

bts TBF
improvem
ent
pcuEdgeDowngradedTbfNbs 0 to 4294967296 15111/0 NBS CELL PCU GPRS

TBF
improvem
ent
pcuEdgeDowngradedTbfAvg 15111/0 AVG CELL
Details:
• pcuEdgeDowngradedTbf
• pcuEdgeTbfEstReq
pcuDyAgprsNbTimeslotsCumCumulative number of EGPRS TBF
establishment requests.
— Event: In the UL direction, when a Packet Resource Request
including an EDGE request is received by PCU.

Note: V15 Counter.
• pcuEdgeDowngradedTbfNbs
pcuDyAgprsNbTimeslotsCumTBD.
— Event: In the UL direction, when a Packet Resource Request
including an EDGE request is received by PCU.
• pcuEdgeDowngradedTbfAvg
EDGE Traffic Profile and Throughput 3

To characterize:
• The UL/DL EDGE effective RLC/MAC throughput in the cell without
BLER impact.
• The EDGE to GPRS data traffic ratio.
• The UL/DL EDGE to GPRS data transfer duration ratio.
• The average UL/DL TBF duration.
Table 3-7
EDGE Traffic Profile and Throughput Counters

SubID Object
pcuEdgeDataBlocksReceivedUp 0 to 15101/0 CUM TDMA PCU GPRS

4294967296
pcuEdgeUpCumUsefulDataPerCell 15112/0 CUM CELL
pcuEdgeDnCumUsefulDataPerCell 15113/0 CUM CELL
pcuEdgeUpUsefulDataDurationPer 0 to 15123/0 CUM CELL PCU GPRS

Cell 4294967296 TBF
improve
ment
pcuEdgeDnUsefulDataDurationPer 0 to 15124/0 CUM CELL PCU GPRS

Cell 4294967296 TBF
improve
ment
—sheet 1 of 2—

Table 3-7
EDGE Traffic Profile and Throughput Counters (continued)

SubID Object
pcuEdgeUpNbsUsefulDataPerCell 0 to 15112/0 NBS CELL PCU GPRS

4294967296 TBF
improve
ment
pcuEdgeUpAvgUsefulDataPerCell 15112/0 AVG CELL
pcuEdgeDnNbsUsefulDataPerCell 0 to 15113/0 NBS CELL PCU GPRS

4294967296 TBF
improve
ment
pcuEdgeDnAvgUsefulDataPerCell 15113/0 AVG CELL
—sheet 2 of 2—
Details:
• pcuEdgeDataBlocksReceivedUp
pcuDyAgprsNbTimeslotsCumCumulative number of EGPRS RLC
data blocks received by the PCU on this TDMA.
— Event: Receipt for a TBF in progress of a TRAU frame without BFI,
containing a RLC/MAC block including:
– a valid RLC data block in sequence received for the first time
– a valid RLC data block in sequence already received
– a valid RLC data block out of sequence
– an invalid RLC data block
Note 1: In case of receipt of a EGPRS Header Stealing Frame or a TRAU

data frame with all Frame Validity set to’0’, this counter is NOT
incremented.
Note 2: In case of receipt of a MCS2 or MCS3 re--segmented data block,

this counter is incremented by 1 unit.
Note 3: In case of receipt of a semi--frame or a TRAU data frameMCS7,

8 or 9 where 1 of the 2 validity frame is set to’0’, this counter is
incremented by 2 units.

Note 4: In case of receipt of MCS7, 8, 9 where 2 RLC data blocks are

sent this counter is incremented by 4 units.
• pcuEdgeUpCumUsefulDataPerCell
• pcuEdgeDnCumUsefulDataPerCell
• pcuEdgeUpUsefulDataDurationPerCell
pcuDyAgprsNbTimeslotsCumCumulative number of times in
multiples of 20ms where the pipes for UL EGPRS TBF are in
“verbose” state.
— Event: This counter is incremented if EDGE is activated in the cell.
• pcuEdgeDnUsefulDataDurationPerCell
pcuDyAgprsNbTimeslotsCumAccumulative times in multiples of 20
ms where the pipes for DL EGPRS TBF are in “verbose” state.
— Event: This counter is incremented if EDGE is activated in the cell.
• pcuEdgeUpNbsUsefulDataPerCell
pcuDyAgprsNbTimeslotsCumAccumulative size in octets of all the
RLC EDGE data blocks received for the first time on a pipe.
— Event: An RLC EDGE data block is received for the first time (i.e.
fresh block) on a pipe by a EGPRS UL TBF.
• pcuEdgeUpAvgUsefulDataPerCell
• pcuEdgeDnNbsUsefulDataPerCell
pcuDyAgprsNbTimeslotsCumAccumulated size in octets of all the
RLC EDGE data blocks sent for the first time on a pipe.
— Event: AnRLCEDGEdata block is sent for the first time (i.e. fresh
block) on a pipe by a EGPRS DL TBF.
• pcuEdgeDnAvgUsefulDataPerCell
GPRS Monitoring Improvement 3

To characterize:
• The UL/DL GPRS effective RLC/MAC throughput in the cell without
BLER impact.
• The number of GPRS UL pipes greater than 22 kbit/s.
• The number of DL TBF pre-established with LLC frames transmitted.

Table 3-8
GPRS Monitoring Improvement Counters

SubID Object
pcuDlThroughputCum 0 to 15007/1 CUM CELL/ PCU GPRS TBF

4294967295 bts improvement
pcuDlThroughputNbs 15007/1 NBS CELL/ PCU GPRS

bts
pcuUpThroughputCum 15193/0 CUM CELL
pcuUpThroughputNbs 15193/0 NBS CELL
pcuUpThroughputAvg 15193/0 AVG CELL
pcuUpPipeGreater22kbps 15194/0 CUM CELL
pcuDnPreEstWithLLCFrame 15195/0 CUM CELL

Transmitted
Details:
• pcuDlThroughputCum
pcuDyAgprsNbTimeslotsCumCumulated size in bytes of all the
GPRS RLC data blocks sent for the first time (i.e. fresh block) on a
pipe.
— Event: AGPRSRLCdata block is sent for the first time (i.e. fresh
block) on a pipe by a GPRS DL TBF.
• pcuDlThroughputNbs
pcuDyAgprsNbTimeslotsCumCumulated time in multiple of 20ms
where the MS is in GPRS DL data transfer.
– TO = Time of the first block sent in downlink for that mobile
– T1 = Time of the last FRESH or NACKED block
– T2 = Time of the PDAN which acknowledged all the downlink
blocks
– The counter is equal to T1--T0+1=T2-- T0--(RTD + RRBP)+1.
— Event: T2 which increment the counter with the result of T1 - T0+1=
T2 - T0-(RTD + RRBP)+1

Note 1: When only one block is sent (i.e. T1=T0) the counter is
incremented by 1.
Note 2: As an implementation choice, T1 can be used as the trigger

instead of T2. RTD = 9 blocks in synchronous TRAU and 5 blocks in
asynchronous TRAU. RRBP is equal to 3 blocks.
• pcuUpThroughputCum
• pcuUpThroughputNbs
• pcuUpThroughputAvg
• pcuUpPipeGreater22kbps
• pcuDnPreEstWithLLCFrameTransmitted

4-65
Engineering Methods: Interfaces 4

This chapter described E-GPRS interfaces and how to plan and design them
for the EDGE network.
Methodology 4
Figure 4-1 shows the suggested steps to follow when deploying an EDGE
GPRS network in an existing GPRS network and highlights nodes that must
be upgraded.
See EDGE Engineering Guideline, PE/IRC/APP/008966 for more

information.

Figure 4-1
EDGE GPRS deployment methodology
Radio
Radio Interface
Interface analysis:
analysis:
Throughput,
Throughput,TDMATDMA
configuration
configuration
Joker on
on Abis
Abis dimensioning:
dimensioning:
Number
Number ofof jokers
jokersto
tobe
be
configured
configured
BTS hardware
hardware provisioning:
provisioning:
Possible
Possible Upgrades
Upgrades
Abis
Abis Interface
Interface dimensioning:
dimensioning:
PCM#
PCM# Radio
Radio Site
SiteMask
Mask
Agprs
Agprs Interface
Interface dimensioning:
dimensioning:
PCM#
PCM#
BSC/PCU
BSC/PCU engineering:
engineering:
Possible
Possible Upgrades,
Upgrades,
dimensioning
dimensioning
First Step: Radio interface

Based on radio condition and network design (cell radius, C/I,…) it is
possible to compute the expected radio Time Slot (TS) throughput. Radio
Interface on page 4-73 presents the detailed of the calculations and proposed
results in typical environments. The outputs of the analysis are the expected
TS throughput, the MCS distribution and the average BLER values.
Moreover this section proposes an analysis on the most adapted strategy for
radio, TS configuration (see EDGE TS Allocation Strategy on page 4-104):
• EDGE TS configured on BCCCH TDMA
• EDGE TS configured on another non-hopping TDMA
• EDGE TS configured on a hopping TDMA
Best strategy depends on available spectrum and data demand. To introduce

EDGE in a network, a simple recommendation is to enable EDGE in the
TDMA supporting the GPRS TS, (typically on the BCCH frequency in many
operator cases).

GPRS and EDGE multiplexing on the same TS is supported and provides

better user throughput on average than GPRS/EDGE segregation on different
TDMA. Traffic Sharing Between TDMA on page 4-110 details the algorithm
and parameters used by the allocator when multiplexing or segregating
EDGE/GPRS users.
Second Step: DS0 joker on Abis

The second step consists in determining the required number of joker DS0 to
be configured on Abis to support the higher throughput per TS. The number
of DS0 can be computed based on the expected MCS distribution. Indeed
from the MCS distribution the requirement per EDGE TS can be deduced as
is show in Table 4-1:
Table 4-1
DSO Jokers on Abis
MSC Percent Joker required

Users
MSC-1 0.0 0
MSC-2 0.0 0
MSC-3 0.0 1
MSC-4 0.0 1
MSC-5 0.0 1
MSC-6 4.9 2
MSC-7 49.5 3
MSC-8 27.5 4
MSC-9 18.1 4
Mean Joker per EDGE TS = 3.41
The number of joker DS0 on Abis can then be computed as follow:
• joker TS dimensioning: Nb_of_Joker_per_EDGE_TS*Nb_of_EDGE_TS
• joker DS0: round_up(Nb_of_16k_Joker/4)

As an alternative to this method, marketing objectives may indicate a minimum

number of DS0 to be configured per cell:
• If MCS-9 is the objective on all TS, then 1 joker DS0 per TS must be
configured
• If MCS-7 is the objective on all TS, then 0.75 joker DS0 per TS must be
configured
See Joker Dimensioning on page 4-121 for further details and examples.
Third step: BTS hardware compatibility:

The BTS/DRX constrains the ability to enable EDGE on one cell/site, and
limits can be set for the maximum number of joker DS0 that can be
configured per TDMA.
TDMA mapping rules for DRX/PA take into account the hardware
capabilities. In the case of defense, a new mapping is performed, and
operators must decide if EDGE service requires hardware redundancy (two
eDRX / ePA per cell) or not (only one eDRX / ePA per cell). In the case of
required redundancy only one set of DS0 Jokers must be provisioned on Abis
(Joker DS0 are managed on a TDMA basis, and TDMA is then mapped on
the most suitable board).
See BTS on page 4-112 for further details.
Fourth Step: Abis backhaul dimensioning

Additional DS0 Jokers must be taken into account, and the radio site mask
must be modified accordingly: additional Abis PCM must be provisioned if
needed.
In the case of PCM defense (Abis PCM failure), the operator can either favor
EDGE TDMA or voice TDMA, and this choice may influence the Radio Site
Mask (RSM) calculation.
Abis Interface on page 4-121 provides the details on the impact of EDGE
Abis dimensioning and (RSM) calculation.
Fifth step: Agprs dimensioning.

Agprs interface should be re-dimensioned to add capacity for Joker TS. A
simple methodology is proposed in Agprs Interface on page 4-135.
Sixth step: BSC/PCU dimensioning.

BSCe3 switching capability will likely require an upgrade because of the
increased number of DS0 that must be switched at BSC level.

Because of the increased number of PCMs (Abis and Agprs), the BSC may
also require additional LSA boards to support more connectivity, and because
of the increase of the Agprs PCM, BSC mapping on PCU may be modified.
Note: EDGE does not impact engineering rules for Gb and Core Packet
network.
See BSC3 on page 4-133 for BSC engineering impact and PCUSN
Dimensioning on page 4-142 for corresponding PCUSN rules.
Example
Consider one 51 sites T1 BSC with the following characteristics in urban
area. With the following TRX distribution: 20 S222, 10 S333, 10 S444, 10
S888, 1 S121212 (153 cells, 606TRX). The BSC is dimensioned to carry
2000 Erlang.
Four PDTCH per cell are configured on the EDGE TDMA. In order to
minimize the impact on the network configuration the BCCH TDMA hosting
the PDTCH is EDGE enabled. GPRS and EDGE users are multiplexed over
the same radio resources.
First step: Radio Analysis

For those sites an average of 580 m cell radius is assumed. Based on a TU3
typical environment the following MCS distribution is obtained (C/I= 12 dB),
the average DL TS throughput in EDGE is 32 kbit/s and the expected MCS
distribution is shown in Table 4-2.
Table 4-2
Example: MCS Distribution
Percent Users Cumulative Percent Mean BLER when

Users used
MCS-1 0.0 100.0 0.0
MCS-2 0.0 100.0 0.0
MCS-3 0.0 100.0 0.0
MCS-4 0.0 100.0 0.0
MCS-5 0.0 100.0 0.0
MCS-6 4.9 100.0 46.3
MCS-7 49.5 95.1 47.6
MCS-8 27.5 45.6 31.0
—sheet 1 of 2—

Table 4-2
Example: MCS Distribution (continued)
Percent Users Cumulative Percent Mean BLER when

Users used
MCS-9 18.1 18.1 7.4
Mean BLER 35.7
—sheet 2 of 2—
Second Step: Joker Requirement on Abis

Based on this distribution the number of DS0 joker can be computed using the
formula:
• joker TS dimensioning: Nb_of_Joker_per_EDGE_TS*Nb_of_EDGE_TS
• joker DS0: round_up(Nb_of_16k_Joker/4)
See Table 4-3.

Table 4-3
Example: Joker Requirement
Percent Users Joker Requirement
MCS-1 0.0 0
MCS-2 0.0 0
MCS-3 0.0 1
MCS-4 0.0 1
MCS-5 0.0 1
MCS-6 4.9 2
MCS-7 49.5 3
MCS-8 27.5 4
MCS-9 18.1 4
Mean joker per EDGE 3.41

TS:
Then 4 DS0 joker should be provisioned per cell (actually per EDGE TDMA)
to benefit from the full EDGE throughput enhancement.

Third Step: BTS Hardware Upgrade

The hardware BTS should be checked on a site basis to ensure the hardware
compatibility with the EDGE activation. Particularly if EDGE service
requires redundancy, i.e. in case of eDRX / ePA failure, then 2 pairs of eDRX
/ ePA should be available on every cell.
Fourth Step: Abis Dimensioning

For every site the Abis PCM number and the Radio Site Mask should be re-
calculated to take into consideration the DS0 joker, see Table 4-4.
Table 4-4
Example: Abis Dimensioning
Configuration TRX Lapd PCM w/o RSM w/o Joker T1 PCM RSM
Total EDGE EDGE DSO with Size
EDGE with
EDGE
S222 6 1 1 12 12 2 12
S333 9 3 1 20 12 2 17
S444 12 3 2 14 12 2 20
S888 24 3 3 18 12 3 22
S121212 36 6 4 23 12 5 23
S121212 36 6 5 21 12 6 19
Note: A S121212 site with 12 joker DS0 (4 per cell) can fit on 5 T1 PCM
only if the full PCM are available. If one DS0 is reserved for other
purpose, then 6 PCM should be provisioned.
Therefore in the considered network, the PCM number on Abis increases

from 94 to 115 T1 PCM, see Table 4-5.
Table 4-5
Example: Abis Increase
Configuration T1 PCM T1 PCM Site

w/o with Number
EDGE EDGE
S222 1 2 20
S333 1 2 10
—sheet 1 of 2—

Table 4-5
Example: Abis Increase (continued)
Configuration T1 PCM T1 PCM Site

w/o with Number
EDGE EDGE
S444 2 2 10
S888 3 3 10
S121212 4 5 1
S121212 5 6 0
Total BSC 94 115
—sheet 2 of 2—
Fifth Step: Agprs Dimensioning

Assuming an average of 10% usage for the PDTCH, 10 cells should be
configured per Agprs PCM (54% compression rate). The considered network
has 153 cells which then requires 15 Agprs PCM.
Note: Before Dynamic Agprs activation with GPRS only services, 7

Agprs PCM were required (23 cells per PCM).
Sixth Step: BSC Upgrade

EDGE introduction has only an impact on the connectivity requirement (more
T1 PCM on Abis and Agprs) and on the switching matrix (more DS0 to be
switched).
• TMU: no evolution. 11 TMU are still required
• LSA: PCM connectivity
— Without EDGE: 94 Abis PCM + 7 Agprs PCM + 28 Ater PCM (2000
erlang) = 129 T1 PCM => 5 LSA
— With EDGE: 115 Abis PCM + 15 Agprs + 28 Ater PCM (200 erlang)
= 158 T1 PCM => 6LSA
• Switching matrix:
— Without EDGE: Abis: 2* nbOfTRX = 1212 DS0; Agprs: 23 DS0 * 7
PCM = 161 DS0; Ater: 623 DS0 (2492 CIC)
— So the total number of DS0 switched in the 8k-RM was 1212 + 161 +
623 = 1996 DS0 which is below the engineering limit 2268 DS0.
— With EDGE activation: Abis: 2* nbOfTRX (1212) + nbOfJokers
(606) = 1818 DS0; Agprs: 23 DS0 * 15 PCM = 345 DS0; Ater: 623
DS0 (2492 CIC)

— So the total number of DS0 switched in the 8k-RM is 2786 DS0 which
is above the engineering limit 2268 DS0.Therefore the upgrade with
the DS512 kit is required.
Conclusions
On this BSC, one LSA board and the kit DS512 must be installed prior to
EDGE activation.
PCUSN: As the number of Agprs PCM increase from 7 to 15, BSC mapping
over PCU may need to be review if no 8 Agprs slot are available. Eventually
the PCU can be upgraded to PCUSN24.
No impact on Gb interface.
Radio Interface 4
E-GPRS achieves higher data throughput (when compared to GPRS) with
new modulation usage: GSM and GPRS use Gaussian Minimum Shift
Keying (GMSK) modulation, while EDGE uses both GMSK and Eight Phase
Shift Keying (8-PSK). 8-PSK communicates three bits of information per
radio symbol while GMSK encodes only one bit per symbol.
Higher Modulation and Coding Schemes (MCS) have higher user data rates
(these data rates are at RLC/MAC level), and lower protection and less
puncturing. Since higher MCSs do less puncturing and send fewer protection
bits, they are used only when good radio conditions exist, and lower MCSs
are used when poor radio conditions exist.
EDGE also benefits from the following other complementary (to radio
modulation) improvements:
• Link Adaptation
– Adapts the coding schemes to the radio channel conditions
dynamically and optimizes communication performances and
throughput. Done through radio measurements, the network
chooses the best MCS and adapts it, estimating the best MCS used
in each position of the cell. All values presented in this document
assumes ideal link adaptation algorithm.
• Incremental Redundancy (exclusive to EDGE)
— Re-transmits data block using a different puncturing method and also
recombines received data block with received erroneous packets so
that the probability of correctly decoding received block is increased.
• Advanced RLC/MAC Protocol (significantly improved in EDGE)
— Handsets that support multiple TS in EDGE are not limited by the
GPRS acknowledge window restriction (GPRS RLC window size is
64, so that the transmitter cannot transmit block N+64 if block N was

not correctly acknowledged by the receiver). In EDGE, window size

have been extended to 1024 blocks and incorrect blocks will not be
lost because of poor radio conditions.
EDGE Deployment in an existing network

This chapter focuses on the performances of an EDGE networks deployed
over an existing GSM network, characterized by a C/(I+N) distribution. User
throughput is distributed in the cell according to the existent network air-
interface quality level. The GSM network’s typical values of coverage and
frequency plan are considered.
There are three significant performance parameters for EDGE network design,
listed below.
• Mean data throughput per TS overall cell
— See Data throughput at cell edge.
• Data throughput at cell edge
— The first two throughput metrics depend on the number of erroneous
blocks that need to be re-transmitted on air interface. BLock Error
Rate (BLER) distribution, which varies with MCS, depends on
several parameters listed below:
– BTS type (macro, micro cell);
– MS performances;
– frequency band;
– environment and mobiles’ speed (TU3, TU50);
– features of signal processing (diversity, frequency hopping,
incremental redundancy); and
– radio condition of the cell, which is related to cell planning and the
frequency plan.
• MCS usage distribution
— Determines which and where each MCS is used. This distribution
drives backhaul dimensioning.
Data throughput calculation

Mean data throughput offered by EDGE on a given cell depends on BLER
distribution on the cell. BLER distribution depends on radio conditions.
Estimations between BLER and radio conditions have been obtained through
software signal processing simulators at the air-interference layer, where
transmitter, receiver, interference, and multipath channel are modelled.

The following global methodology is implemented to calculate EDGE mean

throughput offered per TS for a given scenario:
• Implemented frequency plan on network determines C/I at cell edge. C/I
distribution on cell is obtained applying typical propagation model.
• Cell size, once the environment is characterized, determines Eb/No at cell
edge. Eb/No distribution on cell is obtained with typical propagation
model.
• Thermal noise and interference are independent but with combined
effects, thus C/(N+I) is considered. BLER distributions on cell is deduced
for each MCS from BLER=f[C/(I+N)].
• Throughput distribution on cell is deduced from BLER distributions for
each MCS. User throughput at RLC/MAC layer is estimated by the
following simplified formula:
EffectiveThroughput = MaxThroughput_MCS * (1 - BLER)
• Finally, throughput is estimated integrating data throughput over coverage
area.
Calculations at cell edge determine data throughput with certain reliability

since worst radio conditions are found.
BLER distribution over cell defines MCS distribution usage if perfect link
adaptation is considered, i.e. best data throughput is considered at each
position over all MCS available. Figure 4-2 gives an overview of the
methodology.

Figure 4-2
Data throughput calculation methodology
Voice cell range Frequency Plan
Eb/No distribution on the cell C/I distribution on the cell
C/(N+I) distribution on the cell
R&D simulations:
BLER = f(C/(N+I))
BLER distributions on the cell

for each MCS
Throughput distributions on the

cell for each MCS
Mean throughput / TS on the

cell
This methodology is applicable to either DL or UL. The following steps are

detailed in the next sections:
• Calculations of C/I and Eb/No distributions on cell
• Calculations of throughput distributions on cell
• Calculations of mean throughput per TS on cell
Radio Conditions (C/I and Eb/No) on the Cell

Assume a cell range of R. Cell is divided in concentric cells of radius r i , so
that 0 ≤ r i ≤ R , in order to determine E b ⁄ N o and C ⁄ I distributions on this
cell, Figure 4-3.

Figure 4-3
Cell Partitioning
r1 r2 r3 r4 r6 r8 r10
r10 = R
C/N Distribution
The C/N distribution on the cell depends on voice pathloss. From this
pathloss, C/N at cell edge can be deduced and then E b ⁄ N o distribution can
be calculated.
C/N at cell edge
The cell radius R corresponds to a given voice pathloss. MS and BS

sensitivities are deduced from this pathloss using the following formulas:
MS sensitivity calculation:
PathLoss_Voice = BS_TxPower – DL_Losses – MS_Sensitivity

BS sensitivity calculation:
PathLoss_Voice = MS_TxPower – UL_Losses – BS_Sensitivity
DL_Losses and UL_Losses correspond to all losses introduced in the

transmission and reception chain. In particular: cable losses, BS antenna gain,
slant losses, and penetration factor.
Note: Body losses are not included since, for data transmission, the
handset is assumed to be separated enough from the body to make body
loss insignificant.
MS and BS Eb/No at cell edge can be calculated using the following formula:
C- + NF
Sensitivity(dBm) = – 119.7 + ---
N
Where:
• NF is the noise factor: NF is 3 dB for BS and 8 dB for MS
• C is the carrier received power at MS computed from the transmitter
EIRP and path loss
Which leads to:
C- – 10 × log ( M )
E b ⁄ N o = ---
N
Where:
• M = number of bits per symbol
— M = 1 for GMSK modulated signals (MCS-1 to MCS-4)
— M = 3 for 8-PSK modulated signals (MCS-5 to MCS-9)
As M is different according to the modulation, Eb/No at cell edge is also

different. Three bits per symbol are transmitted in 8-PSK while one bit per
symbol is transmitted in GMSK modulation. In other words, there are two Eb/

No distributions: One for GMSK MCS and another for 8-PSK MCS. The
difference between the two distributions is 10*log(3) factor.
C/N Distribution Estimation
A simplified propagation model is used to calculate C/N distribution over the

cell depending on each ri, i.e. UE cell position:
C-
--- C
( r ) ( dB ) = ---- ( R ) ( dB ) – 10 × α × log ( r ⁄ R )
N N
Where:
• α is the propagation coefficient:
— α = 3.522 in dense-urban, urban, and suburban environments
— α = 3.441 in rural environments
• R is cell radius
• r is expressed in km
C/I Distribution
C/I distribution on the cell depends on implemented frequency plan. From
this frequency plan, C/I at cell edge can be deduced and then C/I distribution.
C/I at cell edge
C/I at cell edge depends on frequency plan implemented on the network.

Nortel Networks experience and simulations have shown that 4*12 for non-
hopping frequency plan allow ensuring a minimum C/I of 12dB with 95% of
reliability. So, the C/I at cell edge is assumed equal to 12 dB.
Note: If the frequency reuse pattern is higher, the C/I at cell edge is
greater. See Figure 4-4 for information on C/I cdf depending on frequency
plan.

Figure 4-4
C/I cdf depending on frequency re-use pattern
100
100
90
90
80
80
70
70 Plan opérationnel
60 Motif 1-1
% P(C/I >= X)
Plan opérationnel
60 Motif 1-3
Motif 1-1
% P(C/I >= X)
50 Motif 2-6
Motif 1-3
Motif 3-9
50 Motif 2-6
40 Motif 4-12
Motif 3-9
Motif 7-21
40 Motif 4-12
30 Motif 7-21
30
20
20
10
10
0
0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30
0
0 2 4 6 8 10 X12
: Seuil de
14 C/I (dB)
16 18 20 22 24 26 28 30
Note: The same C/I distributions are considered for Uplink and
Downlink
C/I Distribution
Following formula is used to calculate C/I distribution over the cell

depending on UE position, for example, r i :
C
---- ( r ) ( dB ) = C
---- ( R ) ( dB ) – 10 × α × log ( r ⁄ R )
I I
Where:
• α is the propagation coefficient:
— α = 3.522 in dense-urban, urban, and suburban environments
— α = 3.441 in rural environments
• R is cell radius
• r is expressed in km

Mean Throughput per TS Calculation

BLER Distributions on the Cell
BLER distributions is deduced using the BLER = f(C/I) curves. These curves
are actually the results of simulations, giving performances for each MCS in
term of BLER uplink versus C/I or Eb/No according to:
• Environment
• Frequency
• Activated features, such as diversity, frequency reuse, incremental
redundancy
Following are two simulations of BLER versus Eb/No (Figure 4-5) and C/I
(Figure 4-6): TU50 propagation profile; 1800 MHz; no FH, no diversity and
no incremental redundancy.

Figure 4-5
BLER=f(Eb/No) in TU50, no FH, no IR, no Diversity at 1800 MHz
20
BLER
10
1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Eb/No
MCS-1
MCS-2
MCS-3
MCS-4
MCS-5
MCS-6
MCS-7
MCS-8
MCS-9

Figure 4-6
BLER=f(C/I) in TU50, no FH, no IR, no Diversity at 1800 MHz
20
BLER
10
1
0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30
C/I
MCS-1
MCS-2
MCS-3
MCS-4
MCS-5
MCS-6
MCS-7
MCS-8
MCS-9
These curves show clearly that BLER performances for a given radio
condition (C/I or C/N) are not the same according to MCS considered. BLER
distribution needs to be calculated for each MCS.
Thermal noise and interference noise effects are combined, so both are added
to calculate C/(N+I). Curves are done either for C/I or Eb/No.
The methodology to calculate BLER distribution on the cell for one MCS is
the following: Consider each couple {C/I; C/N}i calculated previously for
each ri

C/(I+N) is estimated using the following equation:
–1
C ⁄ ( I + N ) = ⎛ ---I- + N
----⎞
⎝ C C⎠
Deduce from the curves (BLER versus C/(I+N) in C/I curves and BLER
versus C/(I+N) in Eb/No curves for each considered MCS) two BLER values
{BLERC/I; BLEREb/No}i associated to C/(N+I)i.
In order to estimate BLER depending on C(I+N) and to take into account

noise characterization (either coverage or interference limited environment)
{BLERC/I; BLEREb/No}i are weighted following a baricenter weighting:
BLER C ⁄ ( I + N ) = α ⋅ BLER C ⁄ N + ( 1 – α ) ⋅ BLER C ⁄ I
C⁄N -
α = ------------------------
C ⁄ (I + N)
Throughput Distributions on the Cell

With BLER distributions on the cell for each MCS (BLER value for each ri
between 0 and R) throughput distributions can be easily determined. The
following formula is used to calculate effective throughput per TS according
to the BLER:
Effective_Throughput i = MaxThroughput × ( 1 – BLER i )

The value of MaxThroughput can be determined using the MCS and Table 4-
6.
Table 4-6
MaxThroughput/MCS
MCS MaxThroughput (kbit/s)
MCS-1a 8.8
MCS-2 11.2
MCS-3 14.8
MCS-4a 17.6
MCS-5 22.4
MCS-6 29.6
MCS-7 44.8
MCS-8 54.4
MCS-9 59.2
a. Not implemented in V15.0.
Note: These values are at RLC/MAC level.
Link Adaptation
To maximize data throughput, the EDGE network chooses the best
throughput value offered by the MCS for each point of the cell. This is done
with an algorithm called Link Adaptation.
Assuming an ideal link adaptation, only one throughput value (throughputi) is

kept for each r i of the cell ( 0 ≤ r i ≤ R ): this throughput value is the best one
among 9 throughputs offered by the different MCS. This means that only one
throughput distribution results from link adaptation. MCS usage on the cell is
deduced from the throughput distribution in Figure 4-7).

Figure 4-7
MCS distribution
MCS-9
MCS-8
MCS-7
MCS-6
MCS-5
MCS-4
MCS-3
MCS-2
MCS-1
Note: MCS-1 and MCS-4 are not available in V15.0.
Mean Throughput / TS
Having throughput value per TS for each ri of the cell, mean throughput per
TS is estimated by integration on coverage area (see Figure 4-7).
Following formula is used:
ΣThroughput i × S i
MeanThroughput = --------------------------------------------
SurfaceTotale
where:
2
• SurfaceTotale is coverage area, for example: SurfaceTotale = πR
• S i is surface area of the crown of range δ , centered on r i (actually
δ = ri )
2 2
S i = π ⎛ r i + δ---⎞ – ⎛ r i – δ---⎞
⎝ 2⎠ ⎝ 2⎠

S o and S R have different expressions since their range is δ ⁄ 2 :
δ 2
S o = π ⎛ ---⎞
⎝ 2⎠
and:
2
S R = π R – ⎛ R – --δ-⎞
2
⎝ 2⎠
Figure 4-8
Mean data throughput integration
SSRR
SS11
δ/2
δ/2
δδ δ/2
δ/2
SS00 r1r1 r2r2 r3r3 r4r4 r5r5 r6r6 r7r7 r8r8==RR

EDGE Performance Estimation

In this section, EDGE performance capacities are estimated. Impact on
capacity of incremental redundancy, and frequency reuse are studied.
EDGE performance estimation depends critically on hypothesis and input

parameters, so estimation performance value has no sense if hypothesis
associated are not clearly specified. In this section, EDGE performance
values are given in order to give an idea of capacity performances, but case-
by-case capacity study should be done for each network separately.
Maximum cell ranges are considered, so performances improve critically if
inter-site distance is reduced.
The following network characteristics are assumed for performance estimations

calculated in this section (excepting examples):
• 4x12 frequency plan is considered by default estimating 12 dB C/I at cell
edge.
• A cell size of 510 meters at 1800 MHz in TU3 and 1.56 km in TU50 is
considered using a default link budget considering a maximum S444 BS
configuration available. Table 4-7 to Table 4-12 detail link budget default
parameters:
Table 4-7
User Equipment Performance
Parameter Value
Maximum UE Tx power (dBm)/Mean 30a
UE Tx antenna gain (dBi) 0.0
UE Rx noise figure (dB) 8.0
UE Rx sensitivity (dBm) -102.0
a. 3 classes of MS are defined in recommendations for EDGE capable handhelds:

E1 MS transmits same power in GMSK and 8-PSK
E2 MS transmits 6 dB (resp 4 dB) less power in 8-PSK than in GMSG in 850/900
MHz frequency band (resp in frequency 1800/1900 MHz band)
E3 MS transmits 10 dB (resp 8 dB) less power in 8-PSK than in GMSG in 850/900
MHz frequency band (resp in frequency 1800/1900 MHz band)

Table 4-8
Base Station Performance
Parameter Value
Maximum BS Tx power (dBm)/Mean 44.8
BS Tx antenna gain (dBi) 18.0
BS Rx noise figure (dB) 3.0
BS Rx sensitivity (dBm) -114.0
Slant losses 1.5
BS Rx cable & connector losses (dB) 3.3
Site antenna height (m) 30
Table 4-9
Coupler losses
Configuration Coupler loss (dB)
S222 1.4
S444 4.7
S888 7.8
Table 4-10
Link Budget margins
Parameter Value
Area reliability desired 90%
Shadowing margin (dB) 10.7
Building penetration factor (dB) 15.0
Body loss (dB) 3.0

Table 4-11
Selected environment correction
Environment Selected Environment Correction Factor (dB)
TU3 0
TU50 -12
RA120/RA230 -22
Taking into account all these input values, 7.6 dB C/N is found in UL at cell
edge for GMSK MCS and 12.7 dB C/N in DL.
Table 4-12
C/I and C/N hypothesis for EDGE in different environments
Environment C/I at cell edge (dB) DL C/No at cell edge (dB)
TU3 (Urban) 12 12.7
TU50 (Suburban) 12 12.7
Mean data throughput has been maximized independent of transmission

impact. There is a trade-off between data throughput and backhaul
dimensioning. Backhaul dimensioning has an important impact on average
throughput because operator may want to sacrifice a little bit of radio
throughput to get significant gains on backhaul and equipment.
Incremental Redundancy
The TU3 and TU50 environments are analyzed and compared, and the impact
of IR is underlined in downlink. No frequency reuse is considered.

Table 4-13 and Table 4-13 show the mean data throughput per time-slot
estimations and the maximum data throughput per time-slot at cell edge.
Incremental redundancy gain is also deduced.
Table 4-13
Data throughput, TU3 1800/1900
TU3 1800/1900 MHz Mean Data Max Data Throughput at cell edge
no FH Throughput
DL no IR 27.1 kbit/s 11.5 kbit/s
DL IR 30.4 kbit/s 14.0 kbit/s
Gain IR 12.2 % 21.7 %
Table 4-14
Data throughput, TU50 1800/1900
TU50 1800/1900 MHz Mean Data Max Data Throughput at cell edge
no FH Throughput
DL no IR 24.2 kbit/s 9.5 kbit/s
DL IR 28.5 kbit/s 15.0 kbit/s
Gain IR 17.7 % 57.9 %
Main conclusions on mean data throughput per TS for a non-frequency hopping

network are:
• Around 28-30 kbit/s per TS are possible in DL.
• As shown in table Table 4-13 IR brings a gain around 15% in the mean
data throughput. IR is interesting in challenging conditions such as cell
edge and in downlink where more retransmissions and recombinations are
needed. Up to 60 % increase of capacity at cell edge is obtained thanks to
incremental redundancy.
• Higher user physical speed degrades throughput performance. Higher
MCS are affected the most, so performance of mean data throughput is
decreased. Around 8% loss is found between a user moving at 3 km/h and
a 50 km/h with the same radio conditions.
MCS Usage Distribution

Table 4-15 to Table 4-18 show MCS used depending on UE-BS distance and
maximum data throughput at this cell position. Mean data throughput and

data throughput at cell edge are also shown for UL TU3 1800 no FH with IR
and DL TU50 1800 no FH without IR respectively.
Table 4-15
MCS usage distribution and throughput (TU3 1800, no FR with IR)
Distance (km) Throughput / MCS usage (%) Mean

TS (kbit/s) Throughput / TS
0.00 59.200 MCS-9 0.037
0.03 59.200 0.296
0.06 59.200 0.592
0.09 59.200 0.888
0.12 59.052 1.181
0.15 57.804 1.445
0.17 55.674 1.670
0.20 52.640 1.842
0.23 48.769 1.951
0.26 44.769 MCS-8 2.015
0.29 41.398 2.070
0.32 37.932 2.086
0.35 34.760 2.086
0.38 31.699 2.060
0.41 29.062 MCS-7 2.034
0.44 26.915 2.019
0.47 24.832 1.987
0.50 22.965 1.952
0.52 21.226 1.910
0.55 18.175 1.727
0.58 15.898 MCS-6 0.785
Mean Throughput / TS (kbit/s) 32.633

Table 4-16
MCS usage distribution (TU3 1800 no FH with IR)
MCS % Users % Users Cumulative
MCS-1 0.0 100.0
MCS-2 0.0 100.0
MCS-3 0.0 100.0
MCS-4 0.0 100.0
MCS-5 0.0 100.0
MCS-6 4.9 100.0
MCS-7 49.5 95.1
MCS-8 27.5 45.6
MCS-9 18.1 18.1
Table 4-17
MCS usage distribution and throughput (TU50 1800, no FR with IR)

0.00 59.200 MCS-9 0.037
0.09 59.200 0.296
0.18 59.200 0.592
0.27 58.342 0.875
0.35 55.736 1.115
0.44 52.766 1.319
0.53 49.287 MCS-8 1.479
0.62 46.203 1.617
0.71 42.570 1.703
—sheet 1 of 2—

Table 4-17
MCS usage distribution and throughput (TU50 1800, no FR with IR) (continued)

0.80 40.205 MCS-7 1.809
0.89 37.868 1.893
0.97 35.199 1.936
1.06 32.508 1.950
1.15 29.763 1.935
1.24 27.237 1.907
1.33 24.915 1.869
1.42 23.379 MCS-6 1.870
1.51 21.883 1.860
1.59 20.332 1.830
1.68 18.776 1.784
1.77 17.330 0.856
Mean Throughput / TS (kbit/s) 30.531
—sheet 2 of 2—
Table 4-18
MCS usage distribution (TU50 1800 no FH with IR)
MCS-1 0.0 100.0
MCS-2 0.0 100.0
MCS-3 0.0 100.0
MCS-4 0.0 100.0
MCS-5 0.0 100.0
MCS-6 39.9 100.0
—sheet 1 of 2—

Table 4-18
MCS usage distribution (TU50 1800 no FH with IR) (continued)
MCS-7 42.0 40.1
MCS-8 10.5 18.1
MCS-9 7.6 7.6
—sheet 2 of 2—
The main conclusions of MCS usage distribution in non-hopping frequency

reuse patterns can be stated as follows:
• MCS-9is used in a small cell coverage area near the BS.
• MCS-5, MCS-6 and MCS-7 are mainly used over the cell.
• MCS-1 and MCS-4 are never used because of the trade-off of BLER-
radio link QoS (also the reason they are not implemented in V15.0).
• MCS usage distribution shows 8-PSK MCS are mainly used all over the
cell but GMSK MCS are necessary to prevent worst punctual cases at cell
edge, mainly in downlink.
Frequency reuse degrades MCS data performances and it critically modifies

MCS usage distribution as detailed in the next section.
Frequency Reuse
Frequency hopping brings frequency and interferer diversity into the process
of reception; since changing the RF carrier while hopping averages the effects
of strong fades and spreads interferences across the network.
Frequency hopping is particularly efficient for slow moving mobiles and for a
sufficient number of hopping frequencies. It reduces the number of
frequencies per TRX, and the capacity increases since more TRXs can be
deployed in the same frequency band.
Frequency load (the ratio between the number of hopping TRXs hopping
frequencies in a cell) is a crucial parameter in a network with frequency
hopping. It represents the amount of time a given frequency is used in the
network.
In order to determine impact of frequency hopping in EDGE MCS, frequency

hopping gain of each MCS is compared with speech gain.
Figure 4-9 shows sensitivity versus BLER performances for TU3, 900 MHz,
no diversity no frequency hopping. In order to guarantee 10% BLER, -107.3
dB sensitivity is found. Four dB sensitivity gain is attributable to frequency

hopping as it is shown in Figure 4-9, where –111.3 dB is found to achieve

10% BLER.
Figure 4-9
BLER versus sensitivity for speech in TU3 without frequency hopping
RXQUAL
7 4 3 2 1 0
FER, BLER
FS
CS1
CS2
CS3
CS4
-117 -116 -115 -114 -113 -112 -111 -110 -109 -108 -107 -106 -105 -104 -103 -102 -101 -100 -99 -98 -97
dBm (S8000)

Figure 4-10
BLER versus sensitivity for speech in TU3 with frequency hopping
RXQUAL
7 6 5 4 3 2 1 0
BLER
FER, BLER
FS
FER,
CS1
CS2
CS3
CS4
-117
-117 -116
-116 -115
-115 -114
-114 -113
-113 -112
-112 -111
-111 -110
-110 -109
-109 -108
-108 -107
-107 -106
-106 -105
-105 -104
-104 -103
-103 -102
-102 -101
-101 -100
-100 -99
-99 -98
-98 -97
-97
dBm (S8000)
Frequency hopping does not provide the same benefits for data as for voice. If
BLER gains (for data) versus FER gains (for speech) are considered, it can be
seen that spreading the errors does not provide any improvement, as packets
have to be received error free (error correction algorithms must be able to
correct all errors). In fact, FH introduces errors in the bit stream that are
difficult to correct if the signal correction process is poor. The more
demanding the protocol is on radio quality, the smaller the benefit of
frequency hopping.

Hence, the impact of frequency hopping for each MCS has to be calculated.
Table 4-19 shows impact for TU3, 900 MHz, no diversity for different MCS.
Table 4-19
Frequency hopping impact on EDGE MCS
Eb/No 10% BLER
MCS TU3 IFH (dB) TU3 (dB) Gain (dB)
MCS-1 6.2 9.4 3.2
MCS-2 8.8 10.7 1.9
MCS-3 12.6 12.5 -0.1
MCS-4 17.1 15.0 -2.1
MCS-5 8.2 12.0 3.8
MCS-6 10.8 14.0 3.2
MCS-7 15.8 17.2 1.4
MCS-8 20.3 19.6 -0.7
MCS-9 22.0 20.8 -1.2
It has been shown in field tests that a 16% frequency load results in the same
quality for speech, with DTX and power control inactivate, as a non-hopping
frequency plan. Therefore, depending on frequency load deployed in the
network, different performances are found. Assuming that 4 dB gain brings
the same quality as for 16% frequency load for speech, and knowing the
impact of frequency hopping on each MCS, the frequency load required to
achieve the same performances as 4*12 frequency plan can be calculated for
each MCS using a linear approximation.
16%
FL(%) = ------------------------------------------------------------------------------------------------------
-
( FH_Gain_Speech – FH_Gain_MCSi ) ⁄ 10

A different frequency load for each MCS is required to achieve the same
performances as non-hopping frequency plans. This is shown in Table 4-20.
Table 4-20
Frequency Load for MCS
MCS Frequency Load (%)
MCS-1 13.30
MCS-2 9.90
MCS-3 6.20
MCS-4 3.90
MCS-5 15.30
MCS-6 13.30
MCS-7 8.80
MCS-8 5.40
MCS-9 4.80
Note: A value of 10% BLER is a good approximation for all MCS.
If the frequency load of a network corresponds to values in Table 4-20, then

MCS performance of this MCS is the same as for a network without
frequency hopping. If FL is lower, frequency hopping results in a gain in the
performance of the MCS but if it is higher then degradation has to be
considered. The next equation estimates the gain or degradation depending on
frequency load implemented and MCS studied.
FL_degradation_Factor(dB) = 10 × log 10 ( FL(%) ⁄ FL_MCS i )
Degradation values are applied to C/(I+N). The same values are applied
independently.
Table 4-21 to Table 4-23 show the capacity increase attributable to frequency
reuse. A dense urban, TU3, 1800 MHz, no IR, downlink with diversity, 510
meter cell size study has been analyses. It compares capacity available for
different frequency bands (5 MHz, 7.5 MHz, and 10 MHz) considering same
QoS in each scenario for users, i.e. same data throughput. Capacity is then

calculated as mean data throughput times the number of TS available divided

by the number of TS required to obtain the same QoS as non-hopping
frequency reuse pattern network.
Downlink cases are the focus of this section since asymmetrical traffic
expectations create downlink limited systems.
Table 4-21
Mean Data Throughput / TS depending on FL (5 MHz)
TU3 1800 Mean Frequencies FL Config TS / TS/ Capacity Capacity

MHz DL no data / / TRx (%) sector User per Gain (%)
IR TS for 30.4 sector
kbit/s (kbit/s)
No FH 27.1 12 S222 14 1 338.2
FH 28.4 12 8.3 S222 14 1.07 371.4 9.8
FH 27.0 10 10.0 S322 16.33 1.13 391.6 15.8
FH 23.7 6 16.0 S333 21 1.28 388.0 14.7
FH 22.1 5 20.0 S433 23.67 1.38 380.2 12.4
Table 4-22
Mean Data Throughput / TS depending on FL (7.5 MHz)

kbit/s (kbit/s)
No FH 27.1 12 S333 21 1 507.3
FH 28.4 12 8.3 S333 21 1.07 557.1 9.8
FH 27.0 10 10.0 S433 23.6 1.13 567.5 11.8
FH 23.7 6 16.6 S555 36 1.28 665.1 31.1
FH 22.1 5 20.0 S666 44 1.38 706.9 39.3

Table 4-23
Mean Data Throughput / TS depending on FL (10 MHz)

kbit/s (kbit/s)
No FH 27.1 12 S444 29 1 700.5
FH 28.4 12 8.3 S444 29 1.07 769.4 9.82
FH 27.0 10 10.0 S554 33.67 1.13 807.3 15.24
FH 23.7 6 16.0 S777 52 1.28 960.7 37.14
FH 22.1 5 20.0 S988 61.33 1.38 985.3 40.65
Frequency hopping degrades mean data throughput per time-slot, but

frequency hopping used with a fractional reuse pattern allows the number of
time-slots per site to increase. The typical 16% frequency load allows an
increase of 37% capacity with regard to non-frequency hopping dimensioning
if 10 MHz is available. Capacity gain depends on the frequency band
available and frequency load deployed in the network as it is shown in Table
4-21 to Table 4-23.
Important Hypothesis and Assumptions

• 3 dB UE noise figure and 8 dB BS noise figure are considered.
• Engineering margins are left to adapt BS eDRX performances to UE
performance estimations.
• To simplify analysis, no call profile is considered and number of EDGE or
speech TS is fixed.
• Voice and data busy-hours are considered the same (worst case).
• Perfect link adaptation is considered independent of BLER estimated: no
stability problem is considered in the backhaul even if BLER figure
grows to more than 50% BLER.
• Results are for radio capacity only: delay on protocols; connection times;
and release times are not considered.
• For mean data throughput calculations users request maximum available
data throughput.
• Real distribution of BCCH and SDCCH are considered depending on
base station configuration.
• Uniform user distribution is considered.

• Maximum inter-site distance is considered following Nortel Networks

default link budgets.
• Frequency reuse plans are always considered to be 1:1 with 16%
frequency load independently from EDGE TS load.
• 70% channel occupancy is considered for both speech and EDGE data
TS.
• Reference value of FL of 16% is estimated without extra GSM features:
power control and DTX are not activated [R4]. The same conditions for
data are considered.
• 4*12 BCCH frequency plan is always considered. This corresponds to 12
dB C/I with 95% reliability, which is found considering full power TX by
the BS (worst case). There will be more interferences because of data but
C/I should not be lower than 12 dB.
• Cell tiering gain is greater closer to the cell edge: gain is neglected when
the user is outside the cell tiering ‘region’ (closer the base station).
• ePA usage with same output power for GMSK and 8-PSK modulation.
• Cell tiering does not exist on PDTCH
BLER Study
For all examples in this document, no BLER limitations have been taken into
account. To calculate different MCS data throughput the following formula is
used:
EffectiveThroughput = MaxThroughput_MCS × ( 1 – BLER )
Link adaptation choose MCS, which optimizes maximum data throughput

independent of BLER estimated for each MCS. RLC/MAC layer
improvement from GPRS result in maximum EDGE BLER values that could
be higher than 10% BLER (the GPRS limiting point).
High BLER values are considered for 8-PSK modulations. 8-PSK data
throughput performance makes 8-PSK MCS more suitable for the chosen
ideal link adaptation algorithm when compared with GMSK. As an example,
MCS-5 at 50% BLER effective data throughput equals 11.2 kbit/s is more
suitable for ideal link adaptation than MCS-2 working at 2% BLER which
represents 10.976 kbit/s effective data throughput.

Table 4-24 shows mean BLER for an environment TU3, DL, 1800/1900
MHz, IR where 8-PSK modulation is recommended to maximize data
throughput
Table 4-24
MCS usage distribution in TU3 (1800/1900, IR, mean BLER/MCS)
MCS % Users % Users Cumulative Mean BLER

when used
MCS-1 0.0 100.0 0.0
MCS-2 0.0 100.0 0.0
MCS-3 0.0 100.0 0.0
MCS-4 0.0 100.0 0.0
MCS-5 0.0 100.0 0.0
MCS-6 4.9 100.0 46.3
MCS-7 49.5 95.1 47.6
MCS-8 27.5 45.6 31.0
MCS-9 18.1 18.1 7.4
Mean BLER 35.7
For example, MCS-7 is used for 49.5% of the cell area with a mean BLER of
47.6%. Over the whole cell, meaning BLER of chosen MCS to maximize data
throughput is 35.7% BLER.
Table 4-25
MCS usage distribution in RU130 (1800/1900, no IR, mean BLER/MCS)

when used
MCS-1 0.0 100.0 0.0
MCS-2 0.0 100.0 0.0
MCS-3 0.0 100.0 0.0
MCS-4 0.0 100.0 0.0
MCS-5 39.9 100.0 34.0
—sheet 1 of 2—

Table 4-25
MCS usage distribution in RU130 (1800/1900, no IR, mean BLER/MCS)

when used
MCS-6 37.5 60.1 17.8
MCS-7 22.6 22.6 18.5
MCS-8 0.0 0.0 0.0
MCS-9 0.0 0.0 0.0
Mean BLER 24.4
—sheet 2 of 2—
BLER study conclusions:

• Ideal link adaptation chooses MCS independent of associated BLER to
optimize data throughput.
• Incremental redundancy reduces BLER at cell edge. BLER from MCS-2
does not overcome 20% BLER without frequency hopping in any
environment.
• Frequency hopping degrades BLER performance. The validity of all
results presented in this document depends on stability because of high
BLERs.
For performance estimation examples, see EDGE Engineering Guideline, PE/

IRC/APP/008966.
EDGE TS Allocation Strategy

This section gives fundamentals of the EDGE TS allocation strategy for
typical cases depending on frequency band, available features, and EDGE
demand.
Two different frequency plans are considered:

• Non-hopping environment where 4*12 frequency reuse pattern is
assumed.
• Frequency hopping with 16% frequency load.
Depending on frequency band and hopping TS, cell tiering ratio and then
frequency load are determined.

Different notations are used in the following tables:

• NO FH: No frequency hopping is available, so the same results are
obtained whether the EDGE TS are allocated in BCCH TDMA or in an
other one.
• Speech Only: No EDGE TS is allocated.
• EDGE on BCCH: EDGE TS are allocated in BCCH TDMA only.
• Non-dedicated TRX: speech and EDGE share all TRX. TS preemption is
considered available.
• CT (27%) non-dedicated 1 TRX non hopping non dedicated. A second
TRX non-hopping, besides BCCH, is deployed. This TRX is not
dedicated, i.e. can be used by speech and EDGE. Other hopping TRX are
also used by both services.
Two indications are given in the same cell because EDGE and speech have
different frequency plans:
CT (28%) Speech only + EDGE Dedicated non-hopping: Automatic Cell

Tiering is only activated in TRX where speech is allocated. EDGE TS are
allocated in dedicated TRX only for EDGE with their own non-hopping
resources, (12 frequencies per TRX).
CT (28%) Speech only + EDGE Dedicated hop (16% FL): Automatic Cell
Tiering is only activated in TRX where speech is allocated. EDGE TS are
allocated in dedicated TRX only for EDGE with their own hopping frequency
with a Frequency load of 16% (6 frequencies required per TRX).
It is assumed that voice QoS is not affected by data TS introduction.

Table 4-26
Base Station capacity: 5 MHz
EDGE Frequency Plan Confg Speech Mean Data Total

demand Max Capacity Data Capacity Capacity
(kbit/s) Thrput/ (kbit/s) (kbit/s)
TS
(kbit/s)
0 TS No FH S222 512.4 N/A N/A 512.4
FH (16%) speech only S333 768.6 N/A N/A 768.6
CT (27%) speech only S544 1146.8 N/A N/A 1146.8
—sheet 1 of 2—

Table 4-26
Base Station capacity: 5 MHz

TS
(kbit/s)
4 TS No FH S222 366.0 30.3 363.6 729.6
FH (16%) EDGE on BCCH S333 622.2 30.3 363.3 985.8
FH (16%) non-dedicated TRX S333 622.2 25.3 303.6 925.8
CT (20%) EDGE on BCCH S433 719.8 30.3 363.3 1083.4
CT (27%) non-dedicated TRX S544 1000.4 21.5 258.0 1258.4
8 TS No FH S222 219.6 30.3 727.2 946.8
FH (16%) EDGE on BCCH S333 475.8 30.3 727.2 1203.0
16 TS No FH S222 0.0 30.3 1272.6 1272.6
—sheet 2 of 2—
Table 4-27
Base Station capacity: 7.5 MHz

TS
(kbit/s)
0 TS No FH S333 768.4 N/A N/A 768.4
—sheet 1 of 2—

Table 4-27
Base Station capacity: 7.5 MHz

TS
(kbit/s)
8 TS No FH S333 475.8 30.3 727.2 1203.0
FH (16%) EDGE on BCCH S555 1024.8 30.3 727.2 1752.0
CT (28%) speech only EDGE S655 1122.4 30.3 727.2 1849.6

dedicated non-hopping

dedicated hop (16% FL)
16 TS No FH S333 183.0 30.3 1454.4 1637.4
Speech dedicated hop (16% S555 732.0 25.3 1214.4 1926.4

FL) EDGE dedicated hop
(16% FL)

CT (27%) non-dedicated 1 S655 829.6 21.8 1046.4 1876.0

TRX non-hopping non-
dedicated
—sheet 2 of 2—

Table 4-28
Base Station capacity: 10MHz

TS
(kbit/s)
0 TS No FH S444 1061.4 N/A N/A 1061.4
8 TS No FH S444 768.6 30.3 727.2 1495.8
FH (16%) EDGE on BCCH S777 1610.4 30.3 727.2 2337.6

dedicated non-hopping

16 TS No FH S444 475.8 30.3 1454.4 1930.2
Speech dedicated hop (16% S777 1317.6 25.3 1214.4 2532.0

FL) EDGE dedicated hop
(16% FL)

CT (23%) non-dedicated 1 S999 1830.0 22.7 1089.6 2919.6

TRX non-hopping non-
dedicated
EDGE TS allocation strategy conclusions:

• Increased frequency load supports a higher number of TRX with reduced
EDGE performance.

• For small frequency band and low EDGE demand, allocating EDGE TS
on BCCH TS is the best strategy.
• From 5 to 10 MHz the best strategy is to put EDGE TS in non-dedicated
hopping TRX shared with speech. For low data traffic demand deploying
EDGE on dedicated frequency hopping plan is something to consider.
• For higher than 10 MHz band, more combinations and strategies are
available, dedicated non-hopping or dedicated data TRX could be
considered. The trade-off between capacity gain and frequency plan ease
must be analyzed.
Conclusion
The following conclusions are found for EDGE only traffic networks:
• Incremental redundancy provides a 15% mean data throughput/TS
increase, with the main advantage reached in worst case conditions (on
cell edge where data throughput is increased up to more than 50%).
• Frequency hopping increases capacity by more than 30% depending on
frequency band available and frequency load deployed.
Performance depends on the scenario, frequency band available, EDGE

penetration, EDGE TS allocation strategy, and reference taken for
comparison, and estimated performance is given only for the sake of giving
examples of a typical environment, but case-by-case study should be
considered using actual customer network characteristics. Performance
calculation inaccuracy apply to the results, but should not influence the
tendencies observed.
The following are EDGE TS allocation strategies:

• For small frequency band and low EDGE demand, allocating EDGE TS
on BCCH TS is the best strategy.
• From 5 to 10 MHz, the best strategy is to allocate EDGE TS with non-
dedicated hopping TRX sharing with speech or EDGE with dedicated
hopping.
• For a higher than 10 MHz band, more combinations and strategies are
available, and non-dedicated non-hopping or dedicated data TRX should
be considered. The trade-off between capacity gain and the ease of
frequency planning must be analyzed.
Finally, GPRS versus EDGE offered traffic load is compared to show the
advantage on traffic load when greater data throughput per TS is available.
Data throughput not only improves the transmission time but increases the
number of user that can be processed in the network when compared with
GPRS at the same QoS.

Traffic Sharing Between TDMA

This section covers traffic sharing between TDMA for PCU, BSC, and GPRS
multiplexing.
PCU
Once an EDGE MS comes into the network, the PCU allocates it on a TDMA.
A TDMA can be either
• No EDGE, or
• Full EDGE.
All the TDMAs of the same GPRS priority get equal consideration for
allocation and only the TDMA number is used. In order to get the highest
EDGE throughput, the EDGE MS is allocated first on the EDGE capable
TDMAs, and a specific parameter is introduced per TDMA called
“EdgeFavor.”
“EdgeFavor” is assigns an equal or higher offer to EDGE TS for EDGE MS.

It is configured on a per TDMA basis and reflects the relative throughput that
can be obtained with EDGE on that TDMA.
TDMA selection depends on:

• The type of the TDMA.
• The value of “EdgeFavor” (EDGE TDMA).
• The GPRS and EDGE load in the TDMA.
TS selection allocation principles do not change in the “first EDGE version.”
Note: If there are two equal offer TDMAs, the PCU will first select an
EDGE capable TDMA for an EDGE capable MS; If there are two equal
offer TDMAs, the PCU will first select a GPRS only TDMA for a GPRS
capable MS.
In most cells EDGE provides three times more throughput than GPRS, so it is
recommended to set EdgeFavor to ‘3.’
BSC
Shared radio TS are allocated using the following criteria from a BSC point of
view (the PCU uses the reverse):
• TDMA priority linked to the requested service,
• The TDMA number, and
• TS number.
This algorithm is not changed for GPRS only TDMA.

In order to avoid pre-emption of EDGE TS, the EDGE TDMA are assigned a
“Super High” priority by the BSC (assigned in first priority to PCU). The
TDMA is selected as “EDGE” through parameter “EdgeDataServiceType.”
In “First EDGE Version,” allocation follows this order:

1. An EDGE TDMA according to the GPRS priority,
2. A GPRS TDMA according to the GPRS priority,
3. The TDMA number,
4. TS number.
The pre-emption follows the reverse order.
GPRS Multiplexing
E-GPRS / GPRS multiplexing on the same time-slot permits the control and
data traffic for E-GPRS and GPRS mobiles to be multiplexed on the same
physical PDCH.
It may occur on more than one PDCH depending on the multi-slot capabilities
of the mobiles multiplexed and on the PDCH assignments.
The downlink throughput for an E-GPRS mobile is reduced when

• An E-GPRS mobile is multiplexed with a GPRS mobile in uplink on the
same time-slot, and
• Modulation for E-GPRS MS is 8-PSK.
In this case, the USF block must be detected by both GPRS and E-GPRS MS
so modulation is GMSK.
The TDMA configuration for E-GPRS:

• No Edge Capacity: all mobiles are allocated as GPRS, even the E-GPRS
ones if one of the multi-slot class capabilities of such mobiles allows it,
• Full Edge Capacity: both GMSK and 8-PSK modulation are used for E-
GPRS mobiles (TDMA requires a TRX type with eDRX and ePA).
Although multiplexing should offer good average throughput for all mobiles,
a parameter is introduced in the GPRS / EDGE radio resources allocator
algorithm to allow time slots segregation (limitation or interdiction of the GPRS
/ EDGE multiplexing), this parameter is called ‘eDGEMixity,’ and it reduces
the offered bandwidth of GPRS mobiles on ‘Full Edge Capacity’ TDMA.
A mobile is allocated on the combination TDMA / Time Slots that offers the
maximum available bandwidth.

In the algorithm, for every Time Slot of a ‘Full Edge Capacity’ TDMA the
offered bandwidth is:
• TimeSlot_Available_Bandwidth, for an EDGE mobile,
• TimeSlot_Available_Bandwidth * eDGEMixity, for a GPRS mobile.
The parameter eDGEMixity has a value between 0 and 100 (percent). 0%

corresponds to no multiplexing, or no GPRS mobiles on EDGE TDMA, and
100% corresponds to no multiplexing constraints. The recommended value
for eDGEMixity is 100%.
Principles:
1. GPRS MS are first allocated on ‘No Edge Capacity’ TDMA, and E-GPRS
MS are first allocated on ‘Full Edge Capacity’ TDMA, as long as the
throughput offer is not greater on the other kind of TDMA (Allocation of
GPRS MS can be limited on ‘Full Edge Capacity’ TDMA with the use of
the ‘eDGEMixity’ parameter), when multiplexing occurs GPRS uplink
TBF is sent with granularity 1.
2. GPRS mobile can always switch between ‘No Edge Capacity’ TDMA
and ‘Full Edge’ TDMA for bandwidth optimization during a TBF.
3. An E-GPRS MS in E-GPRS mode does not switch to ‘No Edge TDMA’.
4. An E-GPRS mobile in GPRS mode can switch to ‘Full Edge’ TDMA (but
still in GPRS mode) for bandwidth optimization, and it can also switch
back to a ‘No Edge Capacity’ TDMA.
BTS 4
This section covers BTS deployment.
Capability Management
Each type of site is able to connect a given number of DS0s to one TRX. The
following table give the capability of each type of site.
Table 4-29
Site Capabilities
Type of Site DSO Maximum (Joker and Main) per

TRX
CSW DCU4 2
S2000 H/L 2
BCF old GTW PROM 2
BCF new GTW PROM 6
—sheet 1 of 2—

Table 4-29
Site Capabilities (continued)
Type of Site DSO Maximum (Joker and Main) per

TRX
CBCF CMCF phase I 6
CBCF CMCF phase II 8a
eCell 8a
—sheet 2 of 2—
a. The maximum number of DSOs that can be configured on a TDMA is restricted to
6 in V15.0 for both CMCF phase II and eCell.
For example, the BSC can configure one TDMA with 6 DS0s only if the site is:
• A BCF equipped with new GTW PROM.
• A CBCF equipped with CMCF phase I.
• A CBCF equipped with CMCF phase II.
• A CBCF equipped with 2 CMCF phase I and II.
• An e-cell.
In other cases, the TDMA is not configured.
One BTS requirement is to have in the same level of site hardware (BCF,
CSWM, and so on) for both chains. If this requirement is met, then a site
switchover is completely transparent on circuit and packet-data services, but
if this requirement is not met, some restrictions exist on the BTS capacity and
upgrade.
These restrictions exist because CMCF Phase I has lower performance in

term of EDGE capability than new CMCF phase II. Consequently, sites with
different cards for duplex have the following restrictions:
• If site is duplex, offered capacity will be the one of CMCF phase I

• If site is simplex with EDGE already configured, the upgrade for duplex
functionality will be restricted if inserted card for duplex is a CMCF
phase I and present card is CMCF phase II.
Finally, sites having old GTW PROM card do not support any EDGE TDMA
configuration.

Site and Joker Management

As the maximum number of joker TS per TDMA is directly linked to the type
of site, the following rule is mandatory: both chains of the site must have the
same level of hardware.
If this rule is not verified one of the following restrictions will apply:
• EDGE TDMA cannot be configured.
• Maximum DS0 capability cannot be used and some EDGE TDMA will
not be configured.
• Duplex functionality will be restricted.
Inconsistency between joker requested by operator and BTS capability will

lead to a TDMA non-configuration with the cause “Maximum number of
joker TS.” To avoid this, it is recommended to first explore site capability
when performing a site EDGE data configuration. This gives the maximum
number of joker TS supported by the BCF/CBCF and TRXs.
It is strongly recommended to have enough spares of each BTS type in order

to avoid any risk of site inconsistency.
TRX Capability
Table 4-30 gives TRX capability according to TRX type.
Table 4-30
TRX Capability
TRX Optimum Data Capability
DCU2 None
DCU4 GPRS
DRX GPRS
DRX-ND3 GPRS
eDRX + legacy PA GPRS + EDGE (up to MCS4a)
eDRX + (H)ePA GPRS + EDGE
eCell GPRS + EDGE
a. In V15.0 only, GPRS capability in this case.
During the Status phase of the start up procedure the TRX sends its capability
using a new “EDGE TRX capability” information element.

TDMA Mapping Over Available TRX

The objective of the TDMA configuration is to map the TDMA on a
hardware resource.
The following mapping is recommended:

• Normal TDMA on normal TRX.
• EDGE TDMA on EDGE TRX with ePA or HePA with sufficient EDGE
capabilities.
While the previous configurations are recommended, they are not mandatory.
The following non-optimum configuration are allowed and are configured in
degraded mode:
• Normal TDMA on EDGE TRX.
• EDGE TDMA on Normal TRX.
• EDGE TDMA on EDGE TRX with insufficient EDGE capabilities
(insufficient DS0 capability compared to TDMA number of DS0).
When an EDGE TDMA is configured in degraded mode, a notification

(Warning 1063) with appropriate cause of degradation is sent to the OMC-R
to inform the operator.
A normal TDMA configured in degraded mode does not induce specific

processing. When a normal TDMA is configured in degraded mode, there is
no specific cause to be displayed since mapping of normal TDMA on eDRX
is current.
An EDGE TDMA configured in degraded mode is considered GPRS TDMA

by the system:
• For the PCU, the TDMA will carry GPRS. Its coding scheme capabilities
are inherited from the default coding scheme allowed for the TDMA.
• For TMG, TDMA will not continue to be EDGE (EDGE features and
counters will not be supported for this TDMA).
An EDGE TDMA configured in degraded mode is consequently configured in

PCU with the following attributes in message PCU TDMA TS status.
• EDGE capability:
— TDMA new EDGE capability is inherited from the EDGE capability
of the TRX on which it is mapped
— In V15.0, if TDMA EDGE capability returned by BSC after TDMA
configuration is 0,1, or 3 then the PCU interprets it as 0 “no Edge
capacity.”
• In joker TS information IEI, current number of joker TS = 0.

Warning 1063 is used to notify the mapping TDMA TRX that degraded mode
is used and the cause of it. A field is added to specify configuration as
nominal or degraded.
Cause of the configuration in degraded mode can be:

1. “Site not supporting Edge” when Site Edge capability <> 2.
2. “Site insufficient number of DS0” when site is not able to respond to the
DS0 request.
3. “TRX insufficient Edge capability” when TRX is not able to respond to
TDMA DS0 request.
If there is a redundant eDRX for one EDGE TDMA, it is not necessary to

have the Joker DSO twice. If an eDRX failed, the EDGE TDMA is
automatically mapped on the available eDRX with the same DS0 Joker.
EPA - HEPA
Dimensioning:
• ePA: Amplifies the GMSK / 8-PSK signal from the eDRX. It is available
in GSM850/1800/1900, and provides 30 Watts output power in both
cases.
• HePA: The HePA (High Power Edge PA) amplifies GMSK/8-PSK signal
from the eDRX. It is available in GSM 1900 only, and provides 60 Watts
output power for GMSK and 45 Watts output power for 8-PSK.
As the HePA consumes more power than the (e)PA and because of its thermal
characteristics, the S8000 cannot support as many HePA as (e)PA.
For these thermal and power supply reasons, the maximum supported
configurations.
S8000 Indoor and Outdoor (S8000 CBCF: 8 HePA900), the following rule
applies for S8000 in V15.0:
• If there are 8 HePA, then there is 0 (e)PA.
• If there are x HePA, then there can be y (e)PA possible, according to the
two following rules x+y<7 and x<5 with x <> 0.
S12000 Indoor and Outdoor (S12000: 8 HePA or 6 HePA + 3 (e)PA versus 12

(e)PA), the following rule applies for S12000 in V15.0:
• If there are 8 HePA, then there is 0 (e)PA.
• If there are x HePA, then there can be y (e)PA possible, according to the
two following rules: x+y<10 and x<7 with x <> 0.
So 1 HePA can go up to 8 (e)PA, 2HePA + 6 (e)PA and so on.

If the maximum configuration is exceeded, the TRX(s) whose (h)(e)PA

connection has caused the overrun, can not be configured: it is declared
unavailable in the enable TRX acknowledge message and a new specific “PA
configuration exceeded” event, mapped on the TRX object, is sent to the
OMC-R.
This event is also sent on the TRX of a S8000 CSWM connected to HePA: the
TRX is declared unavailable.
In the same way, if a HePA has been connected to a DRX, this DRX cannot be
configured and is declared unavailable in the enable TRX acknowledge
message and a new specific “HePA not supported” event, mapped on the
TRX object, is sent to the OMC-R.
HEPA Characteristics
The following are HEPA characteristics:
• EDGE compatible, the non-EDGE TDMA (GMSK) can be transmitted at
up to 60 W; EDGE TDMA (8PSK) can be transmitted with an average
power of 45 W.
• Not compatible with DRX.
• Can be used mixed with PA or ePA thanks to the standard concentric cells
features. The inner zone contains the PA and the outer zone contains
HePA (and only HePA).
• Differentiated at the OMC-R from PA and ePA in the same way the ePA is
differentiated from the PA.
• Same size as the standard PA, so it can be plugged in as S8000 rack at the
same places that the legacy PA (as long as the supported configuration
and the (e)DRX compatibility are respected).
• No impact on the cabling rules and the DLU (no new DLU needed to
support configurations with HePA).
The range of value of the OMC-R parameter “bsTxPwrMax” (that sets the
power of the TRX) already permits configuration of power up to 60 Watts.
Main HEPA usage scenarios:

• Coverage extension for rural site (DLNA recommended).
• Deeper coverage in dense urban sites using stepped power/coupling.
• Capacity growth for urban sites w/o RF coverage reduction where
additional feeders and/or antennas are not permitted (compensate
combining losses).
• Better EDGE coverage / throughput.
• Match 850TDMA coverage footprint when migrating to GSM1900.

Benefits: QoS (coverage) and new service (EDGE).
Interworking with EDGE Feature characteristics

The power output of the 8-PSK modulation (EDGE) is limited to 45 W
instead of 60 W for the GMSK modulation (non-EDGE).
If the BCCH is configured on a TDMA that has also been configured to

support EDGE, its power output may fluctuate 1.25 dB according to the
TDMA supporting or not 8-PSK modulation.
This 1.25 dB fluctuation of the power output of the BCCH TDMA may skew
the power measurement made by the mobile, and this may modify the HO
rules. See HePA Network Engineering Issues to see HO rule.
HePA Network Engineering Issues

The supported coupling configuration with HePA are: duplexer, TxFilter,
H2D (a new H2D version is needed to support HePA), and H4D.
Because of the attenuation induced by the coupling, the maximum power values
that can be configured at OM-R are as follows:
• Duplexer 46.5 dBm
• TxFilter 46.5 dBm
• H2D (new version) 43.5 dBm
• H4D 39.5 dBM
As a consequence interworking with the EDGE feature, it is recommended to

configure the BCCH on a TDMA that is configured as an EDGE TDMA too
or on a non-EDGE TDMA, depending on the network configuration.
EDGE traffic on BCCH carrier:

• Advantages:
— Because of the special reuse of BCCH the higher load on traffic has no
impact as the packet data traffic is mainly downlink. This seems
especially useful for cells with a small number of DRXs.
• Drawbacks:
— Because of peculiarities of 8-PSK modulation, EDGE downlink
transmission in 8- PSK will result in a transmitted mean power
slightly less than the power used on other time-slots of the BCCH
carrier. This power reduction will result in the reduction of power
measurements performed by the MS on this BCCH carrier (that is
supposed to be at constant power).

This reduction on BCCH power measurements could lead to consequences

for cell selection, cell re-selection, and hand-over.
EDGE traffic not on BCCH carrier:

• Advantages:
— No impact on transmitted power on BCCH carrier, therefore no
impact on cell selection, re-selection, or hand-over.
• Drawbacks:
— The EDGE traffic shall be dealt with like the GPRS data traffic: either
using the same radio resources as circuit voice or separate resources.
Not applicable in cell equipped with only one DRX.
BCF Impact:
• The PA type (legacy PA, ePA, or HePA) is sent by the PA/TRX to the BCF
during the TRX-BCF connection stage. The BCF uses this information
and deduces the power limits of the PA. These power limits are not read in
DLU anymore.
• There are two reasons no new DLU is needed to support the HePA:
— The power information given in the DLU is not used by the BCF (the
power information remains in the DLU but it is not used, so the DLU
does not have to be modified and re-delivered).
— As the size of the HePA is the same that the size of the PA, there are
no cabling rule modifications.
Power:
• To avoid power supply problems that could cause a power shut down or
thermal problems that could damage some BTS equipment, the BTS must
have a supported configurations and there cannot be too many HePAs or
(e)PAs in the cabinet.
• Every time a TRX connects to the BCF, the BCF checks its PA type and
verifies that the configuration is supported according to the PA type of the
TRX that are already connected. If the PA type is not supported, an event
on the corresponding TRX with a new specific cause is sent to the BSC at
the reception of the enable TRX message and the TRX cannot be
configured (the TRX is declared unavailable in the enable TRX
acknowledge message).
CSWM:
• The S8000 CSWM doesn’t support HePA (the maximum HePA
configuration supported by the CSWM is equal to 0). If a HePA is

connected to a (e)DRX in a S8000 CSWM BTS, this new specific event is

sent at the reception of the enable TRX message of each (e)DRX.
DRX:
• As the HePA is not able to work with a DRX, the BTS has to check that
the PA type and TRX type of the TRX are compatible.
• Every time a TRX connects itself to the BCF, the BCF checks its PA type
and verifies it is compatible with its TRX type. If not, an event on the
corresponding TRX with a new specific cause is sent to the BSC at the
reception of the enable TRX message and the TRX cannot be configured
(the TRX is declared unavailable in the enable TRX acknowledge
message).
• To permit the configuration of a mixed HePA/(e)PA cell, the BCF doesn’t
check that the cell power given during the cell configuration or cell
modification procedure is supported by all the TRX/PA of the cell. This
verification is done during the cell modify procedure (applies to a cell that
has already been configured) and during power modify procedure (applies
to one TRX only).
• If the power configured at the OMC is not supported by a TRX ((e)PA
configured in the outer zone of a mixed (e)PA / HePA cell, bad power
value configured for a normal cell, with or without HePA), the cell
configuration message is accepted by the BCF but the TRX will not be
configured.
Operation Information
To help the operator manage its network, following mechanisms are improved:
• For BTS data display (only on a centralized OAM BTS): the following
information elements are added:
— Maximum number of DS0 associated to each TRX by the active
chain.
— Maximum number of DS0 associated to each TRX by the passive
chain.
— EDGE capacity (TRX + PA) of each TRX.
Recommendations
Some generic recommendations can be given for BTS dimensioning rules.
• S8000 and S12000 sites with more than 4 EDGE PDTCH and where high
performance coding schemes (MCS-7 and above) are used, the
recommendation is to check the type of CMCF/BCF boards (active and
passive) in order to ensure only CMCF phase 2 are used.
• S8000 and S12000 sites where lower performance coding schemes
(MCS-6 and below) are used and/or where there is a limited number of

EDGE radio time-slots (less than 6), CMCF phase 1 boards or BCF may
be used without end-user impact.
• To ensure consistent CMCF distribution over all the EDGE sites before
the CMCF board may restrict the required EDGE capacity, the
recommendation is to perform an audit of the BTS site while installing the
e-DRX kit. A new feature will be supported from BSS V15.0 in order to
audit remotely from the OMC-R.
• Differentiate both types of CMCF phase 1 and 2 when managing the spare
parts with PEC codes (to avoid any new mixity case when replacing
CMCF boards).
Abis Interface 4
This section covers Abis deployment.
Joker Dimensioning
Every radio TS (voice or GPRS mapped statically on one 16 kbit/s bearer or
1/4 of DS0) on the Abis interface. Since V15.0, new EDGE coding schemes
are managed up to MCS-9 (59.2 kbit/s). So the current Abis and Agprs
interfaces, based on 16 kbit/s TS, have to be enhanced in order to manage
new throughput.
Nortel has implemented a dynamic solution based on “main+joker TS,” which

allow the operator to define:
• The classical set of Abis TS (called main TS) used in order to manage
circuit switch calls and a part of the packet data bandwidth.
• The number of Abis TS used by all radio TS of one TRX, called joker TS.
Figure 4-11
Abis Main and Joker TS relation
4
4 TRAU
TRAU blocks
blocks conveyed
conveyed
by
Main
Main joker
joker 1
1 joker
joker 2
2 joker
joker 3
3
by 4 Abis TS
4 Abis TS
1
1 MCS-7
MCS-7 Radio
Radio Block
Block
conveyed
conveyed by
by 1
1 radio
radio TS
TS
one
one MCS-7
MCS-7 radio
radio block
block =
=44 TRAU
TRAU blocks
blocks

The MCS requirements in terms of jokers is given in Table 4-31:

Table 4-31
MCS Joker requirements
MCS Joker 1/4 DSO Requirement
MCS-1 0
MCS-2 0
MCS-3 1
MCS-4 1
MCS-5 1
MCS-6 2
MCS-7 3
MCS-8 4
MCS-9 4
The jokers are dynamically shared on a TDMA basis. Every 20 ms, the
allocator adjusts the bandwidth on Abis to the MS requirements. A number of
joker DS0 must be provisioned for every EDGE TDMA between 0 to 6.
As a first approach the number of DS0 joker can be computed from the MCS
distribution provided by the radio analysis (see Radio Interface on
page 4-73).
The following formulas provide the statistical number of joker required as a

function of the EDGE number of TS and the number of joker required per TS
• joker TS dimensioning =
Nb_of_Joker_per_EDGE_TS*Nb_of_EDGE_TS
• joker DS0 = round_up(Nb_of_16k_Joker/4)
Table 4-32
Example: DL, cell radius = 580 m, 1800/1900 MHz with IR, TU3
MCS % Users Jokers Required
MCS-1 0.0 0
—sheet 1 of 2—

Table 4-32
Example: DL, cell radius = 580 m, 1800/1900 MHz with IR, TU3 (continued)
MCS-2 0.0 0
MCS-3 0.0 1
MCS-4 0.0 1
MCS-5 0.0 1
MCS-6 39.9 2
MCS-7 49.5 3
MCS-8 27.5 4
MCS-9 18.1 4
Mean Jokers per EDGE TS = 3.41
—sheet 2 of 2—
A TDMA with 4 PDTCH would require 4 DS0 joker to benefit from the
available radio throughput.
Table 4-33
Example: DL, cell radius = 1.77 km, 1800/1900 MHz with IR, TU50
MCS-1 0.0 0
MCS-2 0.0 0
MCS-3 0.0 1
MCS-4 0.0 1
MCS-5 0.0 1
MCS-6 39.9 2
MCS-7 42.0 3
MCS-8 10.5 4
MCS-9 7.6 4
Mean Jokers per EDGE TS = 2.78

A TDMA with 4 PDTCH would require 3 DS0 joker to benefit from the
available radio throughput [= roundup (2.78 * 4 TS / 4 16k_TS_per_DS0)].
This formula provides the average required number of DS0s per joker;
however, one user close to the site may require MCS-9 on all PDTCH: the
allocator allocates all available Abis resources and downgrades MCS until
sufficient jokers are available. In the second example with only 3 DS0s, a 4+1
MS could use 3 TS with MCS-9 and one TS with MCS-2. The average TS
throughput is then decreased.
The following examples provides some insight of the TS throughput

degradation due to Abis backhaul bandwidth.
Table 4-34
Example: DL, cell radius = 580 m, 1800/1900 MHz with IR, TU3
DS0 Joker TS Throughput Degradation

(kbit/s) (%)
4 DSO 32.6 N/A
3 DSO 28.9 -11
2 DSO 23.1 -29
1 DSO 17.3 -47
0 DSO 11.2 -66
Table 4-35
Example: DL, cell radius = 1.77 km, 1800/1900 MHz with IR, TU50
DS0 Joker TS Throughput Degradation

(kbit/s) (%)
4 DSO 30.5 N/A
3 DSO 28.8 -6
2 DSO 24.4 -20
1 DSO 17.9 -41
0 DSO 10.9 -64
It can be seen that without jokers the GPRS typical throughput provided in
this case by MCS-2 is computed.

When the radio conditions are poor, providing 3 DS0s instead of 4 per TDMA
only slightly decreases the mean TS throughput.
PCM Allocation
Principles of Abis PCM allocation are as follows:
• TDMA are mapped on Abis “traffic PCM allocation priority” parameter.
• PCM are selected with regard to their number.
• For each TDMA, from the highest priority to the lowest one, the TDMA
is mapped on the first available PCM with sufficient free time-slots
defined in RadioSiteMask.
TDMA Rules
The following list details the TDMA requirement:
• The Abis DS0 of TDMA (main and Joker) may be non-consecutive on

one PCM, but must belong to the same PCM.
• If a TDMA can not be associated to a set of Abis TS because of a lack of
resources, the BSC sends a major hardware anomaly to the OMC-R to
inform the operator.
• Plan only BCCH TDMA with priority 0. If TDMA other than the BCCH
one are planned with priority 0, the probability of not configuring BCCH
TDMA because of hardware constraints is increased (caused by change in
TDMA TRX mapping algorithm).
• A new action “btsSiteManagerPcmConfig” is created on the
objectbtsSiteManager allowing the display of PCM configuration for a
site with explicit mapping of each TDMA on the Abis interface.
PCM Dimensioning
The introduction of joker TS impacts BTS dimensioning:
• Without joker TS, one TDMA uses 2 DS0, both of which are configured
on one PCM, so the maximum number of TDMA per PCM is:
— E1 PCM (30 DS0): 15 TDMA.
— T1 PCM (23 DS0): 11 TDMA.
• With 6 joker TDMA, one TDMA uses 8 DS0s, all of which are configured
on one PCM, so the maximum number of TDMA per PCM is:
— E1 PCM (30 DS0): 3 TDMA, which use 3*8=24 DS0, so 6 DS0 can
be allocated to small TDMA (for example 3 TDMA without joker TS
or 2 TDMA with 1 joker TS).
— T1 PCM (23 DS0): 2 TDMA, which use 2*8=16 DS0, so 7 DS0 can
be allocated to small TDMA (for example 3 TDMA without joker TS
or 2 TDMA with 1 joker TS).

• As the maximum number of PCM per site is 6, joker TS causes some

limitations in terms of the number of TDMAs per site.
Defense Mechanisms
Defense mechanisms presented below correspond to immediate mode of Abis
re-configuration specified with parameter abisReconfiguration.
If Abis capacity is lost and recovered, the BSC reallocates TDMA to TRX
according to principles described above. In order to decrease the re-
configuration period, the BSC performs these procedures immediately, even
if some calls are dropped.
These principles are illustrated in the following list:

• One cell with 5 TDMA:
— TDMA 0: BCCH TDMA, 2 main TS, 0 joker TS, priority 0.
— TDMA 1: EDGE TDMA, 2 main TS, 2 joker TS, priority 1.
• Two PCM with nine DS0s dedicated to this cell (1 for the Lapd channel, 8
for traffic).
The initial configuration is as in Figure 4-12.
Figure 4-12
PCM example
L
a
PCM 0 TDMA 0 TDMA 3 TDMA 4
p
d
L
a
PCM 1 TDMA 1 TDMA 2
p
d
If one PCM fails, the BSC re-configures as in Figure 4-13.

Figure 4-13
PCM fail example
L
a
PCM 0 TDMA 0 TDMA 1
p
d
L
a
PCM 1 FAIL
p
d
In the fail condition TDMA 2, 3, and 4 are immediately de-configured. If

PCM 1 restarts, then TDMA 2, 3, and 4 are re-configured in order to restore
the initial configuration (full capacity).
Backhaul Configuration Algorithm

Backhaul configuration is proposed to the operator on a site-by-site basis.
Only sites belonging to a BSC e3 can be selected.

On a selected site, all existing TDMAs are displayed with their cell ID and
current EDGE parameters. See Figure 4-14 for the backhaul configuration
methodology.
Figure 4-14
Backhaul Configuration Methodology
Select one or more
TDMAs
Enter EDGE parameters with associated controls:

numberOfJokerDSO
Modify TDMA parameters:
range = 0 to 4 (V15.0)
numberOfJokerDSO and/or
range = 0 to 8 (V15.1, BTS H/W dependent) edgeDataServiceType
edgeDataServiceType
range = capabilityNotRequested/fullCapabilityRequested
Has one or more TDMA

changed with regard to
previous parameters?
Yes
Has a new TDMA been set with

edgeDataServiceType = fullCapabilityRequested
or
Has an already EDGE TDMA been set with an
increase of numberOfJokerDS0?
Yes
Extend Abis capacity:
Read in database site existing
Create PCM, request new
RadioSiteMask and Abis PCM configuration.
RadioSiteMask.
Can new Abis capacity

No Do one of the
request fit into existing
following.
resources?
Yes
Configure missing parameter

codingScheme,
Propose to generate command files.
Check that new Abis capacity request can fit into existing resources using the
list below (this check consists of testing if the new joker DS0 demand can fit
into existing Abis).

• TDMAs are indexed with parameter TDMANb, total number of TDMAs

parameter is named NmaxTDMA.
• TDMAs are ordered as a function of their priority parameter, from the
highest priority (0) to the lowest priority. For same value of priority, they
are ordered as a function of their number, from the smallest to the highest.
• Among TDMAs, there are:
— The EDGE TDMAs with numberOfJokerDS0 > 0, requiring (2 +
numberOfJokerDS0(TDMANb)) DS0s.
— The normal TDMAs with numberOfJokerDS0 = 0, requiring 2 DS0s.
— The existing PCMs connected to the site:
– The total number of PCM is named NmaxPCM.
– One PCM is indexed with parameter PCMNb.
– Site RadioSiteMask gives the number of time-slots allowed for
traffic for each PCM (signalling time-slots removed) given the
following rule: nth row of RadioSiteMask characterizes PCM
number n.
– Note RSM(PCMNb) the number of time-slots equal to 1 in
RadioSiteMask of PCM indexed PCMNb.
– Note RSMneed(PCMNb) the number of time-slots equal to 1
required in RadioSiteMask of PCM indexed PCMNb to satisfy all
TDMA demands. It is incremented while algorithm runs.
The check is obtained by applying:

• RSMneed(PCMNb) = 0.
• For (TDMANb = 1 to NmaxTDMA).
— For (PCMNb = 0 to NmaxPCM).
– Calculate non reserved time-slots:
Rest(PCMNb) = RSM(PCMNb) - RSMneed(PCMNb).
– Try to reserve time-slots on PCM index PCMNb for the EDGE
TDMA index TDMANb using the following logic:
— IF (Rest(PCMNb) =>2+ numberOfJokerDS0(TDMANb))
– RSMneed(PCMNb) = RSMneed(PCMNb) + 2+
numberOfJokerDS0(TDMANb)
– look for next TDMA
— ELSE (PCM index PCMNb is full):
– Increment PCM number
• IF there is at least one TDMA not mapped, the check is FALSE.

RSM Rule
The TDMAs are taken into account by the BSC according to their priority and
after their number (ID).
During the activation of EDGE, the operator can choose the TDMA that will
be EDGE by assigning a quantity of TS joker. The operator can choose the
number of the TDMA and modifies its priority if necessary.
To give a high priority to EDGE, choose a low TDMA number and a high
priority (TDMA = 1 and priority = 1)
Figure 4-15
RSM with EDGE TDMA priority
E1
Compute RSM size
Site configuration S444 PCM type : E1 1 T1 E1
TRX Site configuration 12 S444 Compute RSM size
PCM type : E1 1 T1
Cell1TRX 4 Joker 12Priority PCM_map Cell2 4 Joker Prio rity PCM_ma p Cell3 4 Joker Prio rity PCM_ma p
TDMA1Cell1 1 4 0 Joker 0 Priority PCM_map
1 TDMA1
Cell2 1 4 0 Joker 0 Prio rity PCM_ma
1 TDMA1
p Cell3 1 4 0 Joker 0 Prio rity PCM_ma
1 p
TDMA2TDMA1 1 1 4 0 1 0 1 1 TDMA2
TDMA1 1 1 4 0 1 0 2 1 TDMA2TDMA1 1 1 4 0 1 0 3 1
TDMA3TDMA2 1 1 1 4 1 1 2 1 TDMA3
TDMA2 1 1 1 4 1 1 2 2 TDMA3TDMA2 1 1 1 4 1 1 3 3
TDMA4TDMA3 1 1 0 1 3 1 1 2 TDMA4
TDMA3 1 1 0 1 3 1 2 2 TDMA4TDMA3 1 1 0 1 3 1 3 3
TDMA5TDMA4 0 1 0 3 1 TDMA5
TDMA4 0 1 0 3 2 TDMA5TDMA4 0 1 0 3 3
TDMA6TDMA5 0 0 TDMA6
TDMA5 0 0 TDMA6TDMA5 0 0
TDMA10
TDMA9 0 0 TDMA10
TDMA9 0 0 TDMA10
TDMA9 0 0
TDMA11
TDMA10 0 0 TDMA11
TDMA10 0 0 TDMA11
TDMA10 0 0
TDMA12
TDMA11 0 0 TDMA12
TDMA11 0 0 TDMA12
TDMA11 0 0
TDMA12 0 TDMA12 0 TDMA12 0
Nb of DS0 for maping 39 for traffic + 2 for secondary LAPD
Nb of Nb
PCM of DS0 for maping 3
39 for traffic + 2 for secondary LAPD
Min NbNbofofDS0
PCMfor RSM 133- > may be no reachable because of TDMA granularity)
min. RSM
Min Nbsize
of DS0 for RSM 14
13 - >+may be2no reachable
for traffic for secondary
becauseLAPDof TDMA granularity)
min. RSM size 14 for traffic + 2 for secondary LAPD
PCM1 PCM2 PCM3 PCM4 PCM5 PCM6
Abis TS 16 PCM1 16 PCM2 13 PCM3 0 PCM4 0 PCM5 0 PCM6 inc. Secondary LAPD
0 Abis TS 16 16 Synchro for
13 E1 PCM 0 0 0 inc. Secondary LAPD
1 0 Primary LAPD (assuming
Synchro for E1TEIPCM= 0)
2 1 Primary LAPD (assuming TEI = 0)
3 2
4 3
5 4
6 5
7 6
8 7
9 8
10 9
11 10
12 11
13 12
14 13
15 14
16 15
17 16
18 17
19 18
20 19
21 20
22 21
23 22
24 23
25 24
26 25
27 26
28 27
29 28
30 29
31 30
31
In this example the operator chose to give a high priority on the EDGE
TDMA.

The operator chooses the quantity of the PCM (3 E1 in this case).
In the first PCM there are the TDMAs with BCCH as a result of priority (0),
and then in the first cell the EDGE TDMA have a priority of 1 and there is
enough space on the first PCM, so this EDGE TDMA is put on it.
This continues with the priority and the dedicated places on the PCM.
That is the RSM site.
If this is not the case or, there are PCM losses, and the operator wants to keep
TDMA voice, choose a high number (ID) and a low priority for EDGE
TDMA (TDMA = 6 and priority = 2). In this case the RSM size may be larger
because the last TDMA mapped on the PCM requires a larger number of
DS0s.

Figure 4-16
RSM with voice TDMA priority
E1
Compute RSM size
Site config uratio n S444 PCM typ e : E1 1 T1 E1
TRXSite config uratio n 12S444 Compute RSM size
PCM typ e : E1 1 T1
CellTRX
1 4 Joker12 Priority PCM_map Cell2 4 Joker Prio rity PCM_map Cell3 4 Joker Priority PCM_ma p
TDMA1
Cell 1 1 4 0Joker 0 1
Priority PCM_map TDMA1
Cell2 1 4 0Joker 0 1 TDMA1
Prio rity PCM_map Cell3 1 4 0Joker 0 1
Priority PCM_ma
TDMA2
TDMA1 1 1 0 0 1 0 1 1 TDMA2TDMA1 1 1 0 0 1 0 1 1 TDMA2TDMA1 1 1 0 0 1 0 1 1
TDMA3
TDMA4
TDMA5
TDMA4 0 1 4 3 2 TDMA5
TDMA4 0 1 4 3 3 TDMA5
TDMA4 0 1 4 3 3
TDMA6
TDMA5 0 0 TDMA6
TDMA5 0 0 TDMA6
TDMA5 0 0
TDMA7
TDMA6 0 0 TDMA7
TDMA6 0 0 TDMA7
TDMA6 0 0
TDMA8
TDMA7 0 0 TDMA8
TDMA7 0 0 TDMA8
TDMA7 0 0
TDMA9
TDMA8 0 0 TDMA9
TDMA8 0 0 TDMA9
TDMA8 0 0
TDMA10
TDMA9 0 0 TDMA10
TDMA9 0 0 TDMA10
TDMA9 0 0
TDMA11
TDMA10 0 0 TDMA11
TDMA10 0 0 TDMA11
TDMA10 0 0
TDMA12
TDMA11 0 0 TDMA12
TDMA11 0 0 TDMA12
TDMA11 0 0
TDMA12 0 TDMA12 0 TDMA12 0
Nb of DS0 for maping 39 for traffic + 2 for secondary LAPD
Nb of
NbPCM
of DS0 for maping 3 39 for traffic + 2 for secondary LAPD
Min Nb
Nb ofofPCM
DS0 for RSM 13 3 - > may be no reachable because of TDMA granularity)
min.Min
RSMNb size
of DS0 for RSM 15 13 for traffic
- > may+ be no 2 reachable
for secondary
because LAPD
of TDMA granularity)
min. RSM size 15 for traffic + 2 for secondary LAPD
PCM1 PCM2 PCM3 PCM4 PCM5 PCM6
Abis TS 17PCM1 14PCM2 14PCM3 0PCM4 0PCM5 0PCM6inc. Secondary LAPD
0Abis TS 17 14 Synchro14for E1 PCM0 0 0 inc. Secondary LAPD
1 0 Primary LAPD (assuming
Synchro TEI = 0)
for E1 PCM
2 1 Primary LAPD (assuming TEI = 0)
3 2
4 3
5 4
6 5
7 6
8 7
9 8
10 9
11 10
12 11
13 12
14 13
15 14
16 15
17 16
18 17
19 18
20 19
21 20
22 21
23 22
24 23
25 24
26 25
27 26
28 27
29 28
30 29
31 30
31
In this second example the operator chose to keep voice TDMA in case of
PCM failure and gave a low priority on the EDGE TDMA.
All the EDGE TDMAs are located at the end of the PCM 2 and all of PCM 3.
The number of time-slots set to 1 in the radio site mask needs to include
jokers following the rule: “main and joker time-slots are not necessarily
consecutive but must belong to the same PCM for one given TDMA.”
Specificities of PCM allocation mechanisms in BSC must be taken into

account to ensure that RSM definitions are coherent with final allocation.
Note: Abis defence actions performed by BSC cause a sub-optimization

of Abis resources.

Extension policy needs to be reviewed to take into consideration the

introduction of jokers.
Impact On EDGE Performance

With EDGE the Abis interface needs to be resized to convey the high
performance coding schemes (MCS-3, MCS-4, MCS-5, MCS-6, MCS-7,
MCS-8, and MCS-9).
In V15.0 all EDGE BTS can support up to four additional DS0s (TS joker)
dedicated to an EDGE TDMA on Abis interface.
In V15.1 when calculating the number of DS0 for each TDMA, consider the
following capabilities.
The number of additional DS0 on Abis limits the average coding scheme to
be used on the air interface. Each radio time-slot requires some ¼ DS0s
depending on the coding scheme actually used for this TS, see Table 4-36.
Table 4-36
Joker DSO
Actual Coding Scheme Number of Additional 1/4 DSO for One Radio TS
MCS-1 0
MCS-2 0
MCS-3 1
MCS-4 1
MCS-5 1
MCS-6 2
MCS-7 3
MCS-8 4
MCS-9 4
BSC3 4
This section describes BSC deployment, and focuses on the BSC3 rule.
BSC3 Rule
BSCe3 dimensioning rules are the same as for V14.3 except that 24 Agprs
PCMs can be configured with a PCUSN24 (instead of 12). Moreover, the
DS512 option increases the switching capacity of the BSCe3.

The two following rules are required:

• The number of timeswitches that a 8k-RM can handled is 2268 DS0s
without DS512 option and 4060 with the option (additional fiber cabling
between CEM and 8k-RM board in BSCe3 face panel).
• Without the DS512, DS0s joker are added as in the following formula
(new rule in V15):
Number of TRXs < [ 2268 – ( x ⁄ 4 ) – Y – Z ] ⁄ 2
Where:
• x = number of CIC (on the A interface <= 3112)
• Y = number of DS0 used on Agprs interface (excluding LAPD DS0)
• Z = sum of joker DS0 configured on Abis interface
Note: Ignoring this rule can result in additional “SWM blocking rate”
conditions caused by the lack of resource in the 8k-RM module.
With the DS512 option, no check is to performed because the switching matrix
limit can not be reached (in E1 case 126 PCM * 31 DS0 < 4060 DS0 or in T1
case 168 PCM * 24 DS0 < 4060 DS0).
Defense Mechanisms
In case of TRX loss, it becomes disabled.
On a normal TDMA of priority P lost, the BSC tries to reallocate it on an

available normal TRX. If there aren’t any available normal TRXs, the BSC
tries to reallocate lost TDMAs on normal TRXs with a priority below P or on
EDGE TRX in degraded mode with a priority below P or on EDGE TRX with
a priority below P.
On an EDGE TDMA of priority P, the BSC tries to reallocate it on an

available EDGE TRX with sufficient EDGE capabilities. If there aren’t any
available EDGE TRXs, the BSC tries to reallocate the lost TDMA by first
clearing non optimized allocations.
In case of TRX restart, it becomes enabled.
On a normal TRX, the BSC tries to allocate non-configured TDMA, from the
highest to lowest priority of the non-configured TDMA.
On an EDGE TRX, the BSC tries to optimize first the existing allocation,
then eventually allocate non configured TDMA.

The reconfiguration is similar to a simple configuration of TDMA. It consists

for the BSC of sending to the PCU a message PCU TDMA TS Status with
attributes depending on the mode of configuration of the TDMA (degraded or
not).
Recommendation
Until the BTS is upgraded beyond V15, EDGE TRX and site capabilities are
not reported to the BSC, so the BSC cannot configure a EDGE TDMA on an
adapted TRX.
Agprs Interface 4
This section describes the Agprs interface, and its deployment.
GPRS Principles
The goal of this feature in GPRS is to optimize Agprs PCM use, according to
GPRS traffic sharing among cells.
The benefits are:

• Minimization of the number of Agprs links.
or
• Improvement of the available cell bandwidth.
Note: It is assumed that traffic has a heterogeneous distribution (when

combined with Time Slot Sharing).
This is made on demand, on an Agprs PCM basis. The PCU computes the
Agprs load of each cell and triggers re-configuration procedures in order to
exchange one Agprs TS from the least to the most loaded cell. The BSC
performs the re-configuration according to PCU requests.
Figure 4-17
PCU Request
Cell A Cell B
Agprs PCM
EDGE Principles
The principle is the same as in GPRS only mode: the aim is to give more
bandwidth to the most loaded cells (taking bandwidth from the least loaded
cells).
If:
• No Joker is connected in Cells A & B
• No EDGE TBF is on-going in Cells A & B

then the same algorithm runs: 1 main TS is exchanged between cell A & Cell
B.
• In the other cases, the following principles are used to select the type of
TS added or removed. In most loaded cells:
— If one MS is active in EDGE mode, joker TS can be added in the
EDGE TDMA. The number of jokers is controlled by the parameter
“JokerPerMainTarget” . If it is “x”, and there is already n PDCH and
n*x jokers connected, 1 main TS is selected instead of joker TS.
— If no MS is active in EDGE mode, a main TS is selected.
Engineering rule: “JokerPerMainTarget parameter value should be equal or

less than the number of provisioned Abis DS0 joker.”
If at least one EDGE user has an active TBF, the least loaded cell is the one
where there is no EDGE MS in transfer and with the maximum number of
Jokers connected. If a main is required the least loaded cell is evaluated as in
V14.
In the other cases, 1 Main is selected.
Figure 4-18
Agprs EDGE principle
Cell
Cell A
A with
with 11 EDGE
EDGE TDMA
TDMA
JokerperMainTarget=1
JokerperMainTarget=1 Cell
Cell B
B with
with 1GPRS
1GPRS TDMA
TDMA
11 MS
MS allocated
allocated
in
in Cell
Cell B:
B:becomes
becomes
the
the most
most loaded
loaded one
one
EDGE
EDGE MS MS
allocated
allocated in
in
Cell
Cell AA
MS
MS leaves
leaves
the
the Cell
Cell
JokerperMainTarget
JokerperMainTarget is is reached,
reached,
11 main
main is
is requested
requested
Main
Main in
in Cell
Cell AA
Main
Main in
in Cell
Cell BB
Joker
Joker in
in Cell
Cell AA

Guideline for Agprs Initial Dimensioning

A simple methodology provides a target compression rate according to the
PDTCH usage metric. Network monitoring will allow tuning the Agprs
bandwidth with specific call profile. Moreover network monitoring will allow
increasing the Agprs trunk according to gprs/edge traffic needs.
The idea is to compute the average TS occupancy in the BSC area from the
following cell level metrics:
pcuAgprsMainNbofBlocksDn ( 15110 ⁄ 0 )
DL_CONFIGURED_PDTCH_OCCUPANCY_BKH_EVOLUTION = ----------------------------------------------------------------------------------------------------------------------------
T × 50 × totalNumberOfPacketTs 〈 C1813.1.avg〉
Where T is the observation period (in second).
Note: In V14 release, the PDTCH occupancy can be anticipated by

checking the equivalent V14 metric and assuming a low EDGE
penetration. This is a pessimistic assumption since the spectrum
efficiency improvement with high MCS is not included.
dataBlocksDn ( 15046 ⁄ 1 ) + controlBlocksDn ( 15047 ⁄ 1 )

DL_CONFIGURED_PDTCH_OCCUPANCY = ---------------------------------------------------------------------------------------------------------------------------------------
T × TotalNumberofPacketTSMoy ( C1813.1,avg ) × 50
In the following section µpdtch is the average PDTCH usage on Air interface
(or the average load of the main TS on Abis). Let µjok be the average joker
load on Abis interface. The load of the Abis joker depends on EDGE
penetration and can be approximated as follow:
µjok = µpdtch * edgeRatio
Where edgeRatio is the percentage of data traffic involving a EDGE capable

MS.
The average load of Abis resource is then given by the following formula:
( n pdtch µ pdtch + n jok µ jok )

µ Abis = --------------------------------------------------------
-
( n pdtch + µ jok )
Compression rate calculation

On radio interface:

One set of timeslot is statically associated to the cell and another set can be
dynamically disconnected due to voice preemption or dynamic Agprs
reconfiguration procedures. If the number of dedicated TS is 0 (all shared
with voice), at least one TS is connected on Agprs side. With npdtch TS per
cell, let nf be the static number of TS and nc be the number of reconfigurable
TS.
nf = MAX(1, nminTS)
nf + nc = npdtch
Where nminTS is the number of dedicated PDTCH per cell.
On Abis interface njok joker 16k timeslot are defined per cell. The joker to
main ratio is then: JtoMratio = njok/npdtch It is assumed that the parameter
jokerPerMainTarget is set to this value, i.e. if the number of Abis joker is 4
(resp. 3) for 4 PDTCH the parameter value is 4 (resp. 3).
When considering a given number of cells, NbCell, the sum of their Abis
associated resource is then:
Nabis = NbCell*npdtch*(1+JtoMratio)
On Agprs each cell has a minimum number of TS connected:
nf = MAX(1, nminTS)*(1+JtoMratio)
The remaining resource on Agprs PCM, Nc, can be dynamically reallocated

from one cell to an other.
For E1: 120 = NbCell*nf + Nc
For T1: 92 = NbCell*nf + Nc
Where NbCell is the number of cells mapped on one PCM To ensure that the
Dynamic Agprs algorithm has sufficient resource and do not impact
significantly the customer transfer time it is recommended that the usage of
Agprs TS from Nc pool keeps below 15% at Agprs PCM level.
The following condition must then be checked:
N Abis
µ NC ≤ µ Abis ------------- ≤ 15%
NC

The following formulas provide the maximum number of cells per Agprs
PCM:
E1 case:
1 15% × 120
NbCell ≤ ----------------------------------- --------------------------------------------------------------------------------------
1 + JtoMration µ Abis n pdtch + 15% × max ( n minTS ,1 )
T1 case:
1 15% × 92
NbCell ≤ ----------------------------------- --------------------------------------------------------------------------------------
1 + JtoMration µ Abis n pdtch + 15% × max ( n minTS ,1 )
The compression rate is defined as the ratio of PDTCH not connected at one
time on Agprs (not used by PCU allocator):
For E1case:
120
x = 1 – ----------------------------------------------------------------------------
-
NbCell ⋅ n pdtch ⋅ ( 1 + JtoMratio )
For T1case:
92
x = 1 – ----------------------------------------------------------------------------
-
NbCell ⋅ n pdtch ⋅ ( 1 + JtoMratio )
Where NbCell is the average number of cells per Agprs PCM.
Examples:

Consider 4 PDTCH cell, one of them being dedicated (nf = 1, npdtch = 4).
10% EDGE penetration is assumed. The Dynamic Agprs compression rate
can then be deduced. See tables.
Table 4-37
E1 with Four Joker DSO per Cell
µ PDTCH µ abis Max number of cells Compression rate
5.0% 1.4% 17 65%
7.5% 2.1% 15 60%
10.0% 2.8% 13 54%
15.0% 4.2% 11 45%
20.0% 5.6% 9 33%
25.0% 7.0% 8 25%
30.0% 8.4% 7 14%
40.0% 11.2% 6 0%
Table 4-38
E1 with Three Joker DSO per Cell
5.0% 1.6% 20 63%
7.5% 2.4% 18 58%
10.0% 3.3% 16 53%
15.0% 4.9% 13 42%
20.0% 6.5% 10 25%
25.0% 8.1% 9 17%
30.0% 9.8% 8 6%
40.0% 13.0% 7 0%

Table 4-39
T1 with Four Joker DSO per Cell
5.0% 1.4% 13 65%
7.5% 2.1% 11 58%
10.0% 2.8% 10 54%
15.0% 4.2% 8 43%
20.0% 5.6% 7 34%
25.0% 7.0% 6 23%
30.0% 8.4% 5 8%
40.0% 11.2% 4 0%
Table 4-40
T1 with Three Joker DSO per Cell
5.0% 1.6% 16 64%
7.5% 2.4% 13 56%
10.0% 3.3% 12 52%
15.0% 4.9% 10 43%
20.0% 6.5% 8 28%
25.0% 8.1% 7 18%
30.0% 9.8% 6 4%
40.0% 13.0% 5 0%
Note: High compression rate could reduce the throughput at the

beginning of the transfer for EDGE users. Indeed several reconfigurations
are required to satisfy a 4+1 EDGE MS which can then take a few
seconds.

PCUSN Dimensioning 4
The PCUSN dimensioning rules in V15.0 are identical to the previous
release. The same hardware configurations are supported, and, from an
engineering point of view, the Gb interface is not impacted by EDGE
introduction.
Note 1: Asynchronous TRAU management is an improvement in V15.0.

In the previous release, the maximum round trip delay between the PCU
and the BTS introduced by the transmission network was required to be
below 20 ms (for delay above 20 ms the GPRS service could not be
guaranteed). For V15.0 maximum delay is not enforced, but the PCU can
monitor the delay and adapt the transmission. In order to maximize the
user transfer performance, a delay shorter than 20 ms is recommended.
Note 2: As a result of the joker on Agprs, an increase in the number of

Agprs PCMs may required to upgrade from PCUSN12 to PCUSN24 or to
introduce new PCUSN elements in the network.

5-143
Support Material 5
This chapter contains information that may prove useful but is not essential to
the deployment of an E-GPRS network.
MEAN_BEP and CV_BEP Mapping for DL 5

MEAN_BEP and CV_BEP are calculated for each RLC block (4 bursts),
namely:
• MEAN_BEP is mapped from mean(BEP); BEP= Mean Bit Error
Probability of an RLC block
• CV_BEP is mapped from std(BEP)/mean(BEP). CV_BEP = Coefficient
of variation of the Bit Error Probability of an RLC block
Mean(BEP) and std(BEP) are the mean and the standard deviation
respectively of the measured BEP values of the four bursts in the RLC block,
calculated in a linear scale. In calculating MEAN_BEP and CV_BEP,
measurements made during previous RLC blocks are discarded. In the case of
a multi-slot configuration MEAN_BEP and CV_BEP are calculated over all
slots [GSM 5.08].
There will be a MEAN_BEP value for GSMK modulation and a

corresponding MEAN_BEP for 8-PSK. The parameter is mapped as in Table
5-1.
Table 5-1
MEAN_BEP Values for 8-PSK
Mean Channel Quality for 8-PSK
MEAN_BEP 0 log10(mean(BEP)) >-0.6
MEAN_BEP 1 -0.6 > log10(mean(BEP)) > -0.64
—sheet 1 of 3—

Table 5-1
MEAN_BEP Values for 8-PSK (continued)
—sheet 2 of 3—

Table 5-1
MEAN_BEP Values for 8-PSK (continued)
MEAN_BEP 31 -3.60 > log10(mean(BEP))
—sheet 3 of 3—
Table 5-2 shows values of MEAN_BEP for GMSK modulation [GSM 4.60].
Table 5-2
MEAN_BEP Values for GMSK
Mean Channel Quality for GMSK
MEAN_BEP 0 log10(mean(BEP)) >-0.6
—sheet 1 of 2—

Table 5-2
MEAN_BEP Values for GMSK (continued)
Mean Channel Quality for GMSK
MEAN_BEP 31 -3.60 > log10(mean(BEP))
—sheet 2 of 2—
Note: MEAN_BEP is calculated and filtered in a linear scale but reported

in a logarithmic scale (log10(mean(BEP))).
Concerning CV_BEP, there will be only one mapping for GMSK and 8-PSK
as in Table 5-3.
Table 5-3
CV_BEP Values for GMSK and 8-PSK
Coefficient of variation of the channel quality (8-PSK and GMSK)
CV_BEP 0 2.00 > std(BEP)/mean(BEP) > 1.75
—sheet 1 of 2—

Table 5-3
CV_BEP Values for GMSK and 8-PSK (continued)
Coefficient of variation of the channel quality (8-PSK and GMSK)
—sheet 2 of 2—
MEAN_BEP and CV_BEP Mapping for UL 5

In UL, GMSK measures are shifted at BTS level to match 8-PSK
measurements. As a result, only one table is used for MEAN_BEP mapping.
It is identical to 8-PSK. mapping table in DL.
UL CV_BEP table is identical to the DL table.
Recommended Link Adaptation Tables 5

This section presents the recommended values for Link Adaptation tables.
These values are issued by Nortel Simulations and are subject to change up
the CuR based on platform tuning.
Table 5-4
DL for 8-PSK Measurements Without Option Limitation (8-PSK allowed)
DL 8-PSK Table Recommended Values
TU RA HT
dlMCS2UpperThreshold 31 32 40
—sheet 1 of 2—

Table 5-4
DL for 8-PSK Measurements Without Option Limitation (8-PSK allowed) (continued)
DL 8-PSK Table Recommended Values
TU RA HT
—sheet 2 of 2—
Table 5-5
UL for 8-PSK Measurements Without Option Limitation (8-PSK allowed)
UL 8-PSK Table Recommended Values With Recommended Values

Diversity Without Diversity
TU RA HT TU RA HT
ulMCS2UpperThreshold 40 38 40 31 32 40
Table 5-6
DL for GMSK/8-PSK Measurements with only GMSK in output, GMSK Measurement without
limitations
Other DL Table Recommended Values
TU RA HT
dlGMSKMCS2UpperThreshold 55 60 64
dlGMSKMCS3UpperThreshold 0 0 0

Table 5-7
Other UL table
UL 8-PSK with GMSK only Recommended Values With Recommended Values

Output Table Diversity Without Diversity
TU RA HT TU RA HT
ulGMSKMCS2UpperThreshold 40 38 40 55 60 64
ulGMSKMCS3UpperThreshold 0 80 0 0 0 0
Link Adaptation Tables Usage Examples 5

This section presents examples explaining which table is used in different
situations.
DL 8-PSK & GMSK Tables Usage (no output limitation)

Reference Figure 5-1 for the following examples.

Figure 5-1
8-PSK and GMSK table usage 1
MS BTS PCU
DL TBF Established Using MCS-2
DL Data Block (MCS-2)

(MEAN-BEP; CV-BEP)GMSK

DL Data Block (MCS-2, RRBP, ES/P)
E-GPRS PDAN (LQM: GMSK)
A
(MEAN-BEP; CV-BEP)8-PSK
(MEAN-BEP; CV-BEP)8-PSK DL Data Block (MCS-5, RRBP, ES/P)
E-GPRS PDAN (LQM: 8-PSK & GMSK)

B

E-GPRS PDAN (LQM: 8-PSK) C
Time A:
The MS previously received GMSK blocks only. The MS only reports a
GMSK LQM to PCU. The PCU uses in that case the Table 5-6 to select the
target MCS for Link Adaptation: MCS5 in the example.
Between A & B:
After the MS sent the PDAN with GMSK LQM, and before it is received by
PCU, the MS continues receiving GMSK blocks. When the PCU receives the
E-PDAN, it switches to MCS5, and then the MS only receives 8-PSK blocks.
Between the 2 E-PDAN, the MS received both GMSK & 8-PSK
measurements, then it shall include both measurements in the next E-PDAN.
Time B:
The PCU will look in both Table 5-6 and Table 5-4 using the two
measurements from the MS. If the resulting MCS is unique, it is chosen as the
new MCS for Link Adaptation (here MCS5 in the example). If two MCS

values are provided, the special rule described in section Type of LA-Tables
applies.
Between B & C:
The MS previously received 8-PSK blocks only. The MS shall only report an
8-PSK LQM to PCU in the next E-PDAN.
Time C:
The PCU uses in that case the Table 5-4 to select the target MCS for Link
Adaptation; MCS-5 in the example.
DL 8-PSK & GMSK With GMSK Only Tables Usage

Reference Figure 5-2 for the following examples.
Figure 5-2
8-PSK and GMSK table usage 2
MS BTS PCU
DL TBF Established Using MCS-2

E-GPRS PDAN (LQM: GMSK)

A
USFGPRS-DL Data Block (MCS-2)

E-GPRS PDAN (LQM: 8-PSK & GMSK)
B
USFGPRS-DL Data Block (MCS-2)

Time A:
The MS previously received GMSK blocks only. The MS shall only report a
GMSK LQM to PCU. The PCU uses in that case the Table 5-6 to select the
target MCS for Link Adaptation. For the blocks that need to be sent in GMSK
because the USF is for a GPRS MS, the PCU uses the Table 5-6.

Between A & B:
After the MS sent the PDAN with GMSK LQM, and before it is received by
PCU, the MS continues receiving GMSK blocks. When the PCU receives the
E-PDAN, it switches to MCS-5, and then the MS only receives 8-PSK blocks.
Between the two E-PDAN, the MS received both GMSK & 8-PSK
measurements, then it shall include both measurements in the next E-PDAN.
Time B:
The PCU will look in both Table 5-6 and Table 5-4 using the 2 measurements
from the MS. If the resulting MCS is unique, it is chosen as the new MCS for
Link Adaptation (here MCS5 in the example). If two MCS are provided, the
special rule described in Type of LA-Tables applies.
For the blocks that need to be sent in GMSK because the USF is for a GPRS
MS, the PCU uses both table Table 5-6. If the resulting MCS is unique, it is
chosen as the new MCS for Link Adaptation. If two MCS values are
provided, the special rule described in Type of LA-Tables applies.
Type of LA-Tables
The choice of the LA-Table is made according to :
• the kind of measurement: GMSK BEP / 8-PSK BEP.
• the modulation limitations: GMSK + 8-PSK / GMSK-only.
The kind of measurement only impacts DL LA-Tables.
The modulation limitations may be the result of multiplexing with GPRS MS

(USF decoding or synchronization constraints) or MS not being able to use 8-
PSK in UL (8-PSK support optional in UL for MS)
Notation example:
The table concerning DL, 8-PSK BEP and a resulting modulation limited to
GMSK will be noted: DL_8PSK_BEP_GMSK_ONLY table.
Particular case:
As depicted in [GSM 5.08], the MS shall report MEAN_BEP and CV_BEP
for the modulations, GMSK and/or 8-PSK for which it has received blocks
since it last sent a measurement report to the network. (i.e.
GMSK_MEAN_BEP, GMSK_CV_BEP; and/or 8PSK_MEAN_BEP,
8PSK_CV_BEP).
In the DL direction, the modulation usage can differ from 1 block to another,
thus the PCU can face 4 different LQM contents:
1. No MEAN_BEP neither CV_BEP, no modification of the LA-DL-
CommandedMCS.

2. MEAN_BEP & CV_BEP included only for GMSK, the table concerning
GMSK is used to derive the LA-DL-CommandedMCS.
3. MEAN_BEP & CV_BEP included only for 8-PSK, the table concerning
8-PSK is used to derive the LA-DL-CommandedMCS.
4. Both measurements are included, both tables are used and 2 LA-DL-
CommandedMCS are derived.
In that specific case, the PCU needs to decide on a unique LA-DL-

CommandedMCS. In a case where both modulations were equally used, it is
expected that both Commanded MCS are equivalent.
If the reported values are different, and belongs to different modulations, the
one belonging to the same modulation as currently used is chosen.
If the reported values are different, and belong to same modulation, the
highest MCS from the 2 values is selected, except when GMSK-MEAN-BEP
is equal to 31, in that case, the commanded MCS is the one resulting from the
8-PSK table.
ePA 900/1800 and eDRX 900 Introduction 5

The eDRX and ePA are introduced to follow Nortel strategy of being
completely EDGE hardware ready, and non EDGE DRX and PAs will be
phased so the focus can be put on a single production line.
The eDRX 900 introduction depends on V14.3 software, so operators must

upgrade their networks as early as possible if they want to start deploying
EDGE hardware. The V14.3 software upgrade is a mandatory path to V15,
which is the minimum required release to benefit from EDGE functionality.
Note: GSM-R DRX and PA strategies are not addressed in this

document.
To be completely EDGE hardware ready in GSM 1800, the eDRX 1800 is

also required.
Affected BTS Products:

• BTSs using the P-GSM and E-GSM in 900 MHz and the DCS 1800 MHz.
• S8000 indoor and outdoor.
• S12000 indoor and outdoor.
• S8006 and S8003.
S8002 is not affected as it is a GSM-R BTS and is supplied with a GSM-R

specific DRX/PA.

Details
The EDGE ready PA 900/1800 are software independent and can be used for
non EDGE applications in a transparent way for the operator compared with
the other PA versions. ePA and standard PA can be mixed into the same
cabinet. The ePA is also compatible with both the DRX and eDRX.
The EDGE ready DRX 900 can run on V14.3 and greater software loads. It
can be used for non EDGE applications in a transparent way for the operator
compared with the other DRX versions. eDRX and standard DRX can be
mixed into the same cabinet. The eDRX is also compatible with both the PA
and ePA.
With the introduction of this new ePA and eDRX the former PA and DRX
ND3 will be placed in a manufacture discontinued (MD) status according to
the time frame of introduction of the eDRX, see Phase In/Phase Out Plan on
page 5-154.
For the eDRX and the ePA, a different PEC code is being introduced to reflect
the EDGE Hardware readiness functionality.
Table 5-8
Hardware Replacement Scheme
GSM Frequency Reason for Introduction New Hardware Replacing
GSM 1800 EDGE ready ePA PA
GSM 900 EDGE ready ePA PA
GSM 900 EDGE ready eDRX 900 DRX ND3
Phase In/Phase Out Plan

eDRX 900
The eDRX 900 MHz requires V14.3 or greater software load, so the eDRX
can be introduced when the network is upgraded to V14.3 or greater software.
When all operators are software compatible, the DRX ND3 will be declared
manufacture discontinued (MD) and Nortel will subsequently deliver all
DRX.
ePA 900
The Nortel strategy is to be fully EDGE ready as soon as possible, so the PA
900 MHz will be MD once all PA 900 units are consumed. Since all power
amplifiers should be ePA before eDRX (SW dependency), there will be a
transition period during which Nortel will ship ePA 900 and DRX ND3 900.

ePA 1800
Since the first quarter of 2004, the ePA 1800 became the standard
configuration and the PA 1800 will be placed in MD status. The PA 1800 can
be ordered as long as there is inventory.
PA 900 and 1800 Last Order Date

This is not applicable because the ePA use instead of PA has no impact on
network performance: the ePA is software independent and has the same non
EDGE capability as the PA.
Table 5-9
1800 MHz Phase In
Code DRX/PA 1800 MHz CuR ChR Phase MD

In
NTQA50FA ePA 1800 MHz 03W34 03W40 1Q04
NTQA50HB PA 1800 MHz 04W15
NTU483JB S12 In extension eDRX+ePA 1800 03W34 03W40 1Q04
NTU483DB S12 Out extension eDRX+ePA 1800
NTQA87BC S8 In extension eDRX+ePA 1800
NTQA87PC S8 Out extension eDRX+ePA 1800
NTU483JA S12 In extension eDRX+PA 1800 04W15
NTU483DA S12 Out extension eDRX+PA 1800
NTQA87BB S8 In extension eDRX+PA 1800
NTQA87PB S8 Out extension eDRX+PA 1800
Table 5-10
900 MHz Phase In
Code DRX/PA 1800 MHz CuR ChR Phase In MD
NTQA50EA ePA 900 MHz 04W05 04W13 04W14
NTQA88JA eDRX 900 MHz 04W05 04W13 with v14.3

SW
—sheet 1 of 2—

Table 5-10
900 MHz Phase In (continued)
Code DRX/PA 1800 MHz CuR ChR Phase In MD
NTQA50PC PA 900 MHz After all

PA are
consume
d
NTQA89GA DRX ND3 900 MHz After

V14.3
introducti
on
NTU483GC S12 In extension eDRX+ePA 900 04W05 04W13 With

v14.3 SW
NTU483BC S12 Out extension eDRX+ePA 900
NTQA87AD S8 In extension eDRX+ePA 900
NTQA87ND S8 Out extension eDRX+ePA 900
NTU483GB S12 In extension DRX ND3+ePA 900 04W05 04W13 After After
04W14 v14.3 SW
NTU483BB S12 Out extension DRX ND3+ePA and introducti
900 before on
v14.3 SW
NTQA87AC S8 In extension DRX ND3+ePA 900 introducti
on
NTQA87NC S8 Out extension DRX ND3+ePA 900
NTU483GA S12 In extension DRX ND3+PA 900 After all

PA 900
NTU483BA S12 Out extension DRX ND3+PA 900 are
consume
NTQA87AB S8 In extension DRX ND3+PA 900 d
NTQA87NB S8 Out extension DRX ND3+PA 900
—sheet 2 of 2—
Market Models And Market Packages

The following market models have been updated to reflect the different steps
of the EDGE Hardware introduction between the PA and the DRX:
1800MHz: DRX + PA -> eDRX + PA -> eDRX + ePA
900MHz: DRX ND3+PA -> DRX ND3 + ePA -> eDRX + ePA

The Phase In of these new Packages should occur simultaneously with the
new ePA/eDRX.
Table 5-11
900 MHz
Description Order Code Comments
DRX ND3 DRX ND3 EDGE DRX

and PA and ePA and ePA
S8O 09 1O1E NTDS14BN NTDS14BS NTDS14BT S8000 outdoor 900Mhz O1 H2D ext
H2D 120 16AL O4, 120 Ohms, PS-F redundancy, 1
CPCMI, 2 CMCF, AC main
monophased, max rectifiers, internal
battery BU, 16 alarm prot 1,5m, no
VSWR, no user Ico, no other option.
S8O 09 1O1E NTDS14C NTDS14CE NTDS14CF MM S800 outdoor 900 O1 H2D ext
H2DM 120 8AL C O8, 120 Ohms, EDGE functionality,
PS-F red, lightning prot on RF/Io
cables, 2 CPCMI, 2 CMCF, AC main
monophased, max Phillips rectifiers,
internal battery BU, 8 alarm prot
1,5m, no VSWR, no user Ico, no
other option.
S8O 09 1O1E NTDS14BC NTDS14BE NTDS14BF MM S8000 outdoor 900 O1 H2D ext
H2DPR 120 8AL O4, 120 Ohms, EDGE functionality,
PS-F red, lightning prot on RF/Io
cables, 1 CPCMI, 2 CMCF, AC main
monophased, max Phillips rectifiers,
internal battery BU, 8 alarm prot
1,5m, no VSWR, no user Ico, no
other option.
S8O 09 1S11E NTDS05PC NTDS05PF NTDS05P

H2D 120 G
S8O 09 1S111E NTDS02N NTDS02NE NTDS02NF

H2D 120 C
S8O 09 1S222E NTDS02PC NTDS02PE NTDS02PF

H2D 120
S8O E9 1O1E NTDS15AB NTDS15AD NTDS15AE

H2DM 120
S8O E9 1S111E NTDS15BB NTDS15BD NTDS15BE

H2D 120
—sheet 1 of 2—

Table 5-11
900 MHz (continued)

S8O E9 1S11E NTDS15CB NTDS15C NTDS15CE

H2D 120 D
S8O E9 1O1E NTDS15DB NTDS15D NTDS15DE

H2D 120 D
S8I 09 1O1E NTDS14AB NTDS14AC NTDS14AD MM S800 INDOOR 900 O1 H2D ext
H2D 120 O4, 120 Ohms, EDGE functionality,
PS-F red, 1 CPCMI, 2 CMCF, no
VSWR, no red fan, no alarm prot, no
ETC, no ancillaries.
S8I 09 1S111E NTDS02AB NTDS02AC NTDS02AD

DV 120
S8I 09 1S11E D NTDS16DA NTDS16DB NTDS16D

120 8AL C
S8I 09 1S111E NTDS02BB NTDS02BC NTDS02BD

H2D 120
S8I E9 1S111E NTDS15EB NTDS15EC NTDS15ED

H2D 120
S8I & S8O 09 NTDS31BB NTDS31BC NTDS31BD This DRX kit is common for Indoor &
TRX EDGE Outdoor 900Mhz S8000 BTS. It is
30W made of 1 DRX,1 PA,13 cables. Used
for site expansion (e.g. upgrade S111
to S132->3 TDS31BA required). This
kit completes the list of existing DRX
kits (NTQA87xx)., EDGE
functionality.
S83 09 TRX NTE687AB NTE687AC NTE687AD

EDGE 30W
—sheet 2 of 2—

Table 5-12
1800 MHz

S8000 Outdoor
S8O 18 1S111E NTDS02UA NTDS02UC NTDS02UE

H2D 120
S8000 Indoor
S8I 18 1S111E NTDS16AA NTDS16AA NTDS16AB

D 120 8AL
S8I 18 1S222E NTDS16BA NTDS16BA NTDS16BV

D 120 8AL
S8I 18 1S111E NTDS16CA NTDS16CA NTDS16CB

H2D 120 8AL
S8006
OG6 18 75 NTSB59AA NTSB59AB NTSB59AB S8006 configuration type S222 1800

1S222E DF HD/ MHz hybrid duplexes with VSWR
T 11A 1CPCMI 1CMCF 48V plug grey.
OU6 18 75 NTSB99AA NTSB99AB NTSB99AB Configuration type S222 120 Ohms

1S222E DF HD/ 1800 MHz grey.
T 11A
OG6 18 120 NTSB59BA NTSB59BB NTSB59BB S8006 configuration type S222 1800
1S111E HD/T MHz hybrid duplexes with VSWR
22A 1CPCMI 1CMCF 48V plug green.
S8000 Indoor and Outdoor
S8I & S8O 18 NTDS31CA NTDS31CB NTDS31CC This DRX kit is common for Indoor &
TRX EDGE Outdoor 1800 MHz S8000 BTS. It is
30W made of 1 DRX,1 PA,13 cables.
Used for site expansion. This kit
completes the list of existing DRX
kits (NTQA87xx).

Network Identification and Automatic SW Downloading of BTS

Equipment
From V14.3 the feature SV1374, Network Level Identification of eDRX and
ePA Presence (ID: 12108) is released so that the OMC-R can identify which
types of DRX and PA are in the BTS so that technicians bring the correct
equipment to the site in the event of a failure.
The feature can be used when adding new equipment in the BTS POD of the
products:
• eDRX type: 0xC0 (versus DRX type: 0x90)
• ePA type: 0xC1 (versus PA type: 0x68)
The differentiation function is also necessary for EDGE customers since

EDGE equipment must be differentiated from non EDGE equipment, and
eDRX must be replaced by an eDRX and an ePA must be replaced by an ePA.
To replace a DRX by an eDRX or DRX ND3 or a PA by an ePA, a Lock/

Unlock or a reset TRX must be made to ensure the coherence of the
notifications sent to OMC-R.
From V15.1 the feature DRX Edge Automatic Downloading (ID: 13752) will
be introduced so that the EFT is found automatically on the OMC-R and
downloaded on the other DRX after the DRX type is manually downloaded
once. This procedure searches among the available EFT present in the
OMC-R database, which software (EFT, catalog file and a hardware
reference) should be attached to the DRX and will automatically perform the
change. This feature is designed to help the operator to introduce new
software attached to a new DRX platform.
Also, during upgrades to V15.1, if a DRX ND3 is downloaded with an EFT

EDGxxx, the upgrade tool will download the EDGxxx EFT. Then after DRX
ND3 restarts with the V15.1 software, there will a notification of
downloading failure. If the feature DRX Edge Automatic Downloading is
activated at the OMC-R, no manual action will be required; except a manual
change for the first EFT, that may have to be performed.
EFT Management
Another way to differentiate the DRX type at the OMC-R level is by using the
DRX EFT. Following is a summary of the different DRX EFT naming
conventions for V12.4d.3 and higher software versions:
• CDRxxxx EFT delivery for DRX, DRX ND and DRX ND2.
• DRXxxxx EFT delivery for DRX ND3.
• EDGxxxx EFT delivery for eDRX.

Even though using the same EFT to manage eDRX and ND3 (EDGxxx) is
possible until V15.0 (only the label seen at the OMC differs, because both
DRX have the same logical board), Nortel strongly recommends using DRX
ND3 with the DRXxxx EFT as soon as possible (from V12.4d.3 software
load) to avoid the issue of not managing the EDGE hardware in V15.
For more details on the subject and the EFT upgrade procedure, please refer
to the Customer Advisory Bulletin number 141 and DRX 900 MHz EFT
Strategies Procedure for EFT Management in 900 MHz, PE/COM/INF/
008263 describing the impact of the ND3 DRX and eDRX introduction on
the EFT naming.
Spare Management
Spare ordering on the PA 900/1800 MHz and the DRX 900 is no longer
possible as the product is in the MD status, so it is important to observe the
last order date. All orders will automatically reflect the DRX/PA change and
the new ePA 900/1800 and eDRX 900 will be delivered in lieu of the PA 900/
1800 and the DRX ND3.
R and R Management
Non EDGE PA and DRX equipment will continue to be supported from a
repair and return standpoint. Depending on the PA and DRX repair-ability
and stock availability, Nortel Networks may send ePA and eDRX modules as
replacement for defective PA and DRX modules. This strategy has no
incompatibility impact on the network as PA are software independent, and
all customers should have a software versions compatible with the eDRX.


Family Product Manual Contacts Copyright Confidentiality Legal

EDGE
Deployment Guide
To order documentation from Nortel Networks Global Wireless Knowledge Services, call
(1) (877) 662-5669
To report a problem in this document, call

(1) (877) 662-5669
or send e-mail from the Nortel Networks Customer Training & Documentation World Wide Web site at
http://www.nortelnetworks.com/td
Copyright © 2004 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its
employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the
same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks.
CDMA2000 is a trademark of the Telecommunications Industry Association (TIA). CDMA2000 1X is a trademark of the CDMA
Development Group. Microsoft Windows and Win2000 are trademarks of Microsoft Corporation. UNIX is a trademark of X/Open
Company Limited.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
411-9001-801
BSS V15
Standard 01.04
November 2004
Originated in Canada

Nortel Edge Deployment

Uploaded by

Copyright:

Available Formats

You might also like

Nortel Edge Deployment

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nortel Edge Deployment

Uploaded by

Copyright:

Available Formats

411-9001-801

Wireless Service Provider Solutions

Document number: 411-9001-801

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright © 2004 Nortel Networks, All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL

411-9001-801 Standard 01.04 November 2004

Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

411-9001-801 Standard 01.04 November 2004

About this document xiii

E-GPRS Deployment Roadmap 1-1

BSS Datafill 2-17

Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

Tool Description 2-28

New Counters and Troubleshooting 3-51

Engineering Methods: Interfaces 4-65

411-9001-801 Standard 01.04 November 2004

TDMA Mapping Over Available TRX 4-115

Support Material 5-143

Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

Figure 4-4 C/I cdf depending on frequency re-use pattern 4-80

411-9001-801 Standard 01.04 November 2004

Table 2-6 Channel (Transceiver Associated Object 2-24

Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

Table 4-31 MCS Joker requirements 4-122

411-9001-801 Standard 01.04 November 2004

About this document A

The deployment of an EDGE GPRS network is complex in the sense that no

Audience for this document 0

Organization of this document 0

To learn more about See

An overview of the E-GPRS deployment Chapter 1, “E-GPRS Deployment Roadmap”

Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

To learn more about See

Detailed Engineering methodologies for Chapter 4, “Engineering Methods: Interfaces”

Background information on EDGE parameters Chapter 5, “Support Material”

Indication of hypertext links 0

411-9001-801 Standard 01.04 November 2004

• DMS-MSC/Call Server Software Delta, 411-2231-199. Provides readers

Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

411-9001-801 Standard 01.04 November 2004

E-GPRS Deployment Roadmap 1

V15.0 is a commercial release fully compatible with BSS V14.3 networks,

EDGE is an enhancement of the GPRS data communications protocols and

An example of an EDGE GPRS network is displayed in Figure 1-1.

Wireless Service Provider Solutions EDGE Deployment Guide BSS V15

Upgrade and Compatibility for V15.0 1

Nortel NSS Compatibility

Nortel GPRS Packet Core Compatibility

Norel SMLC Compatibility

411-9001-801 Standard 01.04 November 2004

BSS Release Upgrade Path POR

From To V15.0 ChR

V14.2 Not Supported

V14.3 Not Supported

V14.3.0 (ML0) Supported

V15.0 CuR Supported

Supported WPS Configurations

NSS HLR BSS