当前位置:首页 >> 信息与通信 >>

EGPRS implementation guide


2002545 Nokia GSM/EDGE BSS10.5 System Documentation Set

EGPRS implementation guide for GSM/EDGE BSS

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietar

y and Confidential

1 (32)

EGPRS implementation guide for GSM/EDGE BSS

2 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

Contents

Contents
Contents 3 1 1.1 1.2 1.3 1.4 1.5 2 2.1 2.2 2.3 3 4 4.1 4.2 4.3 4.4 4.5 4.6 5 5.1 5.2 5.3 6 EDGE features 5 8-ary Phase Shift Keying 5 EGPRS Modulation and Coding Schemes Incremental Redundancy 7 Link Adaptation for EGPRS 10 Dynamic Abis 11 EGPRS user interface 15 EDGE-related parameters 15 EDGE-related MMI 17 EDGE-related counters 18 Planning and managing EGPRS implementation 21 Integrating a new EDGE BSS to the radio network 23 Creating Gb interface 23 Creating routing area and handling links 23 Creating Dynamic Abis pool and radio network objects 24 Activating BCF software 25 Commissioning UltraSite EDGE Base Station 25 Unlocking radio network objects 26 Implementing EDGE in an integrated GPRS BSS 27 Activating BCF software 27 Activating EDGE in UltraSite BTS already integrated in the network Enabling EGPRS in BSC 28 Runtime EDAP modification 31

6

27

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

3 (32)

EGPRS implementation guide for GSM/EDGE BSS

4 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EDGE features

1
1.1

EDGE features
8-ary Phase Shift Keying
Introducing 8-ary Phase Shift Keying (8PSK), a linear, higher-order modulation, in addition to Gaussian Minimum Shift Keying (GMSK) allows the data transmission rates to be tripled. An 8PSK signal carries three bits per modulated symbol over the radio path, compared to a GMSK signal, which carries only one bit per symbol. Nokia uses standardized 3pi/8 offset rotation to reduce amplitude variations with 8PSK modulation, as shown in the figure 8PSK modulation scheme. The standard GSM carrier symbol rate (270.833 ksps) is the same as with 8PSK. The burst lengths are the same as the existing GMSK Time Division Multiple Access (TDMA) structure, and the same 200 kHz nominal frequency spacing between carriers is used. While GSM uses GMSK, EDGE uses both 8PSK and GMSK.

(d(3k),d(3k+1),d(3k+2))= (0,0,0) (0,0,1)

(0,1,0) (0,1,1) (1,1,1)

(1,0,1) (1,0,0)

(1,1,0)

Figure 1.

8PSK modulation scheme

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

5 (32)

EGPRS implementation guide for GSM/EDGE BSS

Table 1.

8PSK and GMSK comparison 8PSK GMSK
GMSK, 1 bit/sym 270.833 ksps 116 bits 23.2 kbit/s

Modulation Symbol rate Payload/burst Gross rate/time slot

8PSK, 3 bit/sym 270.833 ksps 346 bits 69.6 kbit/s

Related topics

Overview of Nokia EDGE

1.2

EGPRS Modulation and Coding Schemes
Enhanced General Packet Radio Service (EGPRS) supports high-rate packet data services across varying channel conditions. The table Peak data rates for single slot EGPRS shows the peak data rates for a single slot EGPRS. As shown, EGPRS supports higher data rates compared to basic GPRS, using several Modulation and Coding Schemes (MCSs) varying from 8.8 kbit/s to 59.2 kbit/s in the radio interface.

Table 2. MCS
1 2 3 4 5 6 7

Peak data rates for single slot EGPRS Modulation
GMSK GMSK GMSK GMSK 8PSK 8PSK 8PSK

Code Rate
.53 .66 .80 1 .37 .49 .76

Family
C B A C B A B

User Rate
8.8 kbit/s 11.2 kbit/s 14.8 kbit/s 17.6 kbit/s 22.4 kbit/s 29.6 kbit/s 44.8 kbit/s

6 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EDGE features

Table 2. MCS
8 9

Peak data rates for single slot EGPRS (cont.) Modulation
8PSK 8PSK

Code Rate
.92 1

Family
A A

User Rate
54.4 kbit/s 59.2 kbit/s

The information contained in the table is further defined as follows:

MCS1 through MCS4 - GMSK modulated, robust against challenging radio channel conditions. MCS5 through MCS9 - 8PSK modulated to provide higher data rates. Code Rate - higher coding scheme identifiers indicate higher coding and peak throughput rates, but are less tolerant to noise and interference. Family - MCSs are organised in families to allow re-segmentation of data blocks in case of retransmissions. They can be accomplished on lower coding schemes, that is if transmission failed with the original, higher coding scheme, the same data can be re-transmitted with a lower codec within the same family.

Note
GPRS is not a subset of EGPRS. The GPRS coding schemes, CS-1 to CS-4, are different than the EGPRS GMSK coding schemes, MCS-1 to MCS-4.

Related topics

Overview of Nokia EDGE

1.3

Incremental Redundancy
Incremental Redundancy (IR) is an efficient combination of two techniques, Automatic Repeat reQuest (ARQ) and Forward Error Correction (FEC). In the ARQ method, when the receiver detects the presence of errors in a received RLC block, it requests and receives a re-transmission of the same RLC block from the

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

7 (32)

EGPRS implementation guide for GSM/EDGE BSS

transmitter. The process continues until an uncorrupted copy reaches the destination. The Forward Error Correction (FEC) method adds redundant information to the user information at the transmitter, and the receiver uses the information to correct errors caused by disturbances in the radio channel. In the IR scheme (also known as Type II Hybrid ARQ scheme), all the redundancy is not sent right away. Rather, only a small amount is sent first, which yields a high user throughput if the decoding is successful. However, if decoding fails, a re-transmission takes place according to the ARQ method. Using IR, the transmitter transmits a different set of FEC information from the same RLC block. These sets are called puncturing schemes, and there are two (P1 and P2) or three (P1, P2 and P3) of them in each of the nine MCSs of EGPRS. Supporting IR, the receiver is able to combine the necessary amount of error correcting information. This mechanism is illustrated in the figure Incremental Redundancy scheme. Since the combination includes more information than any individual transmission, the probability of correct reception is increased. IR co-operates with link adaptation which selects the amount of redundancy information transmitted in each transmission. The benefits of IR are increased throughput due to better and automatic adaptation to different and varying channel conditions, and reduced sensitivity to link quality measurements.

8 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EDGE features

Data Block

P1

One MCS P2

P3

Transmitter

P1

P2

P3

1st transmission P1 Protection Level 1

1st re-transmission upon reception failure

2nd re-transmission upon reception failure

No data recovered

P1 Stored Combination: Protection Level x 2

P2 No data recovered

Receiver

P1 Stored Combination: Protection Level x 3

P2 Stored

P3

Figure 2.

Incremental Redundancy scheme

Note
If after P3 the data still cannot be recovered, P1 is sent again and combined with the stored P1, P2, and P3 (which reaches a protection level of about four times P1), and so on, until the data is recovered.

Related topics

Overview of Nokia EDGE

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

9 (32)

EGPRS implementation guide for GSM/EDGE BSS

1.4

Link Adaptation for EGPRS
EDGE not only increases efficiency and speed, but also improves data protection through link quality control. The system uses various measurements of the past link to predict up coming channel quality. This prediction determines the relevant protection of the information to be sent. The Link Adaptation (LA) mechanism works to provide the highest throughput and lowest delay available by adapting the protection of the information to be sent, according to the link quality. Enabling LA requires accurate link quality measurements and a set of modulation and coding schemes (MCSs) with different degrees of protection.
Accurate link quality measurements

The use of new, efficient EGPRS measurement provides accurate prediction of up coming link quality in several propagation channels that have various speeds (for example, typical urban and rural areas and hilly terrain). The link quality measurements are Bit Error Probability estimates (BEP). Nokia uses a link adaptation algorithm to work in cooperation with IR. While IR improves throughput by automatically adapting the total amount of transmitted redundancy to the radio channel conditions, LA selects the amount of redundancy for each individual transmission. This helps reduce the number of re-transmissions, and thus keeps the transfer delay reasonably low. Protection decreases
Data rates and protection levels

Nine Modulation and Coding Schemes (MCSs) are designed for EGPRS. When an RLC data block is sent, the information is encoded using one of the MCSs to resist channel degradation and modulated before transmission over the airinterface. Since the resources are limited, the higher the level of protection for information, the less information is sent. MCS-1 to MCS-9 ranges from a high protection/low bit rate, to a no protection/high bit rate, as summarised in the figure Data Rates and Protection Levels for Modulation and Coding Schemes.

10 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EDGE features

Scheme
MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9

Modulation

Data Rate (kbps)
8.8
Protection decreases

Code Rate
.53 .66 .80 1 .37 .49 .76 .92 1

Family
C B A C B A B A A

11.2 GMSK 14.8 17.6 22.4 29.6 8PSK 44.8 54.4 59.2

Figure 3.

Data Rates and Protection Levels for Modulation and Coding Schemes

In EGPRS, it is possible to switch between any of the MCSs, from one data block to another, as it is in GPRS. The GPRS re-transmission would take place with exactly the same protection as for its initial transmission. In EGPRS, however, it is possible to change the MCS. This is useful since the level of protection needed in a re-transmission may be different due to varying channel conditions and the existing protection from earlier incremental redundancy transmissions.
Related topics

Overview of Nokia EDGE

1.5

Dynamic Abis
With enhanced data rates per radio time slot varying between 8.8 and 59.2 kbit/s, traditional static Abis allocation does not use transmission resources efficiently. The Dynamic Abis feature is introduced to optimise loading, by splitting Pulse Code Modulations (PCMs) into permanent time slots for signalling and voice, and by providing a dynamic pool for data. The pool is shared by a number of

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

11 (32)

EGPRS implementation guide for GSM/EDGE BSS

TRXs. The Dynamic Abis transmission feature saves up to 60 percent of the Abis transmission expansion cost, since it allows Abis dimensioning to be performed closer to the average data rates instead of at peak rates. This saving also applies to the reduced number of 2M BSC interfaces needed. Abis channel mapping is arranged so that the standard GSM TRXs are connected to the BSC in a conventional fashion, such as 16 or 64 kbit/s. These bits are reserved permanently for signalling (TRXSIG) for each TCH, and 16 kbit/s are reserved permanently for each TCH. The same applies to GSM/EDGE TRXs, but when MCS-2 or higher is used, the BSC allocates Abis capacity for data calls from the EGPRS dynamic pool (EDAP). Normal GPRS (non-EGPRS) calls using CS-2 also use EDAP resources when allocated into EGPRS territory (GSM/EDGE TRXs). The Dynamic Abis pool is usually shared between multiple GSM/EDGE TRXs. EGPRS and Dynamic Abis use a new type of PCU frame to connect with the Abis L1 interface. GSM/EDGE TRXs use the PCU Master data and PCU Slave data frames to transfer both GPRS and EGPRS data. The required EDAP resources for MCSs are allocated with 16 kbp/s slave channel resolution according to the table below. In addition to the table, CS-2 also requires one slave channel in and EDGE-enabled BTS.

Table 3.
MCS-1 noSlaves 1 Slave 2 Slaves 3 Slaves 4 Slaves X MCS-2

Usage of slave channels.
MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9

X

X

X

X X

X

X

X

The figure Dynamic Abis pooling shows an example of Dynamic Abis pooling.

12 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EDGE features

Example: Data call from TRX 2 (MCS<=2) Example: Data call from TRX 6 (MCS<=2) A

Abis PCM with 6 EDGE TRXs 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
BCCH TCH 4 TRX 1 TCH 0 TCH 4 BCCH TCH 4 TRX 3 TCH 0 TCH 4 TRX 4 BCCH TCH 4 TCH 0 TCH 4 TRX 6 TCH 1 TCH 2 TCH 3 TCH 5 TCH 6 TCH 7 OMU 1 TXR 2 OMU 2 TCH 2 TCH 3 TCH 5 TCH 6 TCH 7 TCH 1 TCH 2 TCH 3 TCH 5 TCH 6 TCH 7 OMU 3 TCH 1 TCH 2 TCH 3 TCH 5 TCH 6 TCH 7 OMU 4 TXR 5 OMU 5 TCH 1 TCH 2 TCH 3 TCH 5 TCH 6 TCH 7 TCH 1 TCH 3 TCH 5 TCH 6 TCH 7 OMU 6

EDGE TRX 1 EDGE TRX 2 EDGE TRX 3

Abis B BTS BSC

EDGE TRX 4 EDGE TRX 5 EDGE TRX 6

BTS

EGPRS Dynamic Abis pool

Figure 4.

Dynamic Abis pooling

Related topics

Overview of Nokia EDGE

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

13 (32)

EGPRS implementation guide for GSM/EDGE BSS

14 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EGPRS user interface

2
2.1

EGPRS user interface
EDGE-related parameters
For a detailed description on the parameters, see BSS Radio Network Parameter Dictionary in BSC documentation set.
BSC parameters

" "

maximum number of UL TBF (MNUL) maximum number of DL TBF (MNDL)

BTS-specific BTS parameter

"

EGPRS enabled (EGENA)

SEG-specific BTS parameters

" " " " " " "

EGPRS Link Adaptation Enabled (ELA) initial MCS for acknowledged mode (MCA) initial MCS for unacknowledged mode (MCU) mean BEP offset GMSK (MBG) mean BEP offset 8PSK (MBP) maximum BLER in acknowledged mode (BLA) maximum BLER in unacknowledged mode (BLU)

Power control (POC) parameter

"

bit error probability filter averaging period (BEP) This parameter is related to EGPRS link adaptation. It is not used for power control.

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

15 (32)

EGPRS implementation guide for GSM/EDGE BSS

Transceiver (TRX) parameters

" "

dynamic Abis pool ID (DAP) GPRS enabled TRX (GTRX)

Dynamic Abis Pool (DAP) (DYN_ABIS_IN_USE) (EGPRS_USAGE) parameters

" " " "

pool id (ID) BCSU number (BCSU) PCU index (PCU) circuit (CRCT)

PRFILE parameters

Detailed parameter descriptions can be found in BSC documentation, PRFILE and FIFILE Parameter List.

Parameter class 046 PCU_TELECOM_PARAMETERS:
" " " " " " " " " " " " " MEMORY_OUT_FLAG_SUM EGPRS_UPLINK_PENALTY EGPRS_UPLINK_THRESHOLD EGPRS_DOWNLINK_PENALTY EGPRS_DWNLINK_THRESHOLD UPLNK_RX_LEV_FRG_FACTOR GPRS_TBF_REALLC_THRSHLD TERRIT_BALANCE_THRSHLD TERRIT_UPD_GTIME_GPRS TBF_LOAD_GUARD_THRSHLD EGPRS_RE_SEGMENTATION PRE_EMPTIVE_TRANSMISSIO BCCH_BAND_TBF_THRSHLD

Parameter class 049 GB_INTERFACE:

16 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EGPRS user interface

" " " "

FC_MS_R_DEF_EGPRS (MS-specific leak rate default value for EGPRS) FC_MS_B_MAX_DEF_EGPRS (MS-specific buffering capacity default value for EGPRS) FC_R_TSL_EGPRS (EGPRS timeslot transmission capacity) FC_B_MAX_TSL_EGPRS (EGPRS timeslot buffering capacity)

PAFILE parameters

Parameter description can be found in BSC documentation, PAFILE Timer and Parameter List. " BS_CV_MAX The default value of this parameter is 6. For EGPRS it is recommended that a higher value is used.

2.2

EDGE-related MMI
"

BSC: The following MML commands are related to EDGE:
EQV, EQO. For more information, see Base Transceiver Station Handling in BSC in BSC documentation set. EUC, EUM, EUO. For more information, see Power Control Parameter Handling in BSC documentation set. ERC, ERO, ERM. For more information, see Transceiver Handling in BSC documentation set. Commands of EE command group. With EEI command you can check the TRX hardware support for EDGE. Note that this can be checked after the object has been unlocked for the first time and it has reached working state with EDGE-capable software. After that the information remains in BSC regardless of the object's operational state. For more information, see Base Station Controller Parameter Handling in BSC documentation set. Commands of WO command group. For more information, see Parameter Handling in BSC documentation set. Commands of EG command group. For more information, see GSM Timer and BSC Parameter Handling in BSC documentation set.

-

"

BTS: the feature cannot be managed with BTS MMI.

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

17 (32)

EGPRS implementation guide for GSM/EDGE BSS

EDGE-related features and MMI

"

Nokia Smart Radio Concept for EDGE (Nokia SRC):
-

BSC: the feature cannot be managed with BSC MMI. BTS:: the feature is managed with BTS MMI.

"

Support of PCCCH/PBCCH
-

BSC: the feature is managed with BSC MMI. BTS: the feature cannot be managed with BTS MMI.

"

Priority Class based Quality of Service
-

BSC: the feature is managed with BSC MMI. BTS: the feature cannot be managed with BTS MMI.

"

Dynamic Abis Allocation
-

"

BSC: the following MML commands are used to manage Dynamic Abis allocation feature: ESE, ESM, ESG. For more information, see Abis Interface Configuration and Dynamic Abis Pool Handling in BSC documentation set. BTS: the feature is managed with BTS MMI.

System Level Trace
-

BSC: the feature cannot be managed with BSC MMI. BTS: the feature cannot be managed with BTS MMI.

" "

Common BCCH: see System impact for Common BCCH. Multi BCF: see Multi BCF Control.

2.3

EDGE-related counters
New measurements in EGPRS

New counters or measurements that are introduced with EGPRS include: " " "

Dynamic Abis measurement: includes for example counters for average and peak EDAP usage uplink and downlink. Coding Scheme Measurement: differ from GPRS counters because 8-PSK is introduced with EGPRS.
New counters, for example for EGPRS TBFs, are added in Packet Control Unit Measurement.

18 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

EGPRS user interface

The other counters remain the same as in GPRS.
GPRS-specific measurements

For GPRS statistics there are several measurements in the BSC. Some of these provide information about the basic functionality of GPRS and some are related to some specific GPRS feature. " " " " " " " "

Packet Control Unit Measurement Frame Relay Measurement RLC Blocks per TRX Measurement Dynamic Abis Measurement Coding Scheme Measurement Quality of Service Measurement PBCCH Availability Measurement
TBF Observation for GPRS Trace

GPRS-related counters in other measurements

In addition to GPRS-specific measurements, there are GPRS-related counters in other measurements: " " " "

Traffic Measurement: the GPRS counters in Traffic Measurement are related to the GPRS territory method. Resource Availability Measurement: gives information about the paging load both on the Gb interface and on the radio interface. Handover Measurement: counter for intra cell handover attempts due to GPRS (HO ATT DUE TO GPRS). BSC Clear Code (PM) Measurement:counter for intra cell handovers due to GPRS (INTRA GPRS HO).

For more information, see BSC documentation set: " "

GPRS in BSC BSC counters

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

19 (32)

EGPRS implementation guide for GSM/EDGE BSS

20 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

Planning and managing EGPRS implementation

3

Planning and managing EGPRS implementation
This is a summary of the tasks needed to implement EGPRS. The tasks depend on whether you are integrating a new EDGE BSS to the radio network, or implementing EDGE in an already integrated GPRS BSS. You can activate EDGE in the network using NetAct. For more information, see NetAct documentation: Building and Extending EDGE Coverage in OSS.
Prerequisites

Node Managers (Remote BTS manager, UltraSite Hub Manager) must be integrated to NetAct. For more information, see NetAct documentation. OSS3.1ED2 software is the prerequisite for the RNW Planning tools such as Plan Manager. For Node Manager server concept, ED1 is sufficient. TRXs should have EDGE specific HW. Take into account the following: " When the TRX has been created with EDAP defined at BSC and EGPRS feature is enabled, the TRX must be attached to EDAP on the BTS side as well. Otherwise the configuration of BCF will fail. EDAP in BSC must be inside the TSL boundaries defined in the BTS side. This requirement has to be taken into account also when modifying EDAP size or changing the first and/or the last timeslot. The timeslot indexes in the BSC and BTS also have to match, regardless of how the timeslots are routed through the transmission network. In other words, the index of the first timeslot of the EDAP in the BTS has to be the same or smaller than in the BSC for this DAP. The index of the last timeslot in the BTS has to be the same or greater than in the BSC for this DAP.

"

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

21 (32)

EGPRS implementation guide for GSM/EDGE BSS

"

Creating, modifying or deleting of EDAP in the BSC will cause a territory downgrade/upgrade procedure to all territories served by the PCU in question. This will make ongoing EGPRS/GPRS connections to pause and resume immediately. The maximum EDAP size is 12 timeslots. EDAP must be located on the same ET-PCM line as TRX signaling and traffic channels. There are no specific commissioning tests concerning EDAP. EDAP must be located on the same BCSU as Gb interface.

" " " "

Integrating a new EDGE BSS to the radio network

1. 2. 3. 4. 5. 6.

Creating Gb interface Creating Routing area and handling links Creating Dynamic Abis pool and radio network objects Activating BCF software Commissioning UltraSite EDGE Base Station Unlocking radio network objects

Implementing EDGE in an integrated GPRS BSS

1. 2. 3.

Activating BCF software Activating EDGE in UltraSite BTS already integrated in the network Enabling EGPRS in BSC

22 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

Integrating a new EDGE BSS to the radio network

4
4.1

Integrating a new EDGE BSS to the radio network
Creating Gb interface
Steps

1. 2.

Create Gb interface (FUC, FNS, FWC, FWS) Check that Gb interface creation was successful (FWO)

Example 1. Example printout.
LOADING PROGRAM VERSION 6.18-0 DX 200 DX220-LAB 2002-11-05 11:10:15

NETWORK SERVICE VIRTUAL CONNECTION PARAMETERS: NSEI-01000 BCSU-00 PCU-04 NS-VC ID NAME ----------------01000 LAURA_NS ADM OP STATE STATE -----------U WO-EX OP STATE ----------016 AV-EX DLCI CIR ---0576 BEARER CHANNEL ID NAME ---------------0000 LAURA

COMMAND EXECUTED

4.2

Creating routing area and handling links
Steps

1.

Create the Routing Area (EBF)

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

23 (32)

EGPRS implementation guide for GSM/EDGE BSS

2. 3. 4.

Check that the creation was successful (EBP) Create OMU link and TRX link (DSE) Change links states to WO (DTC)

4.3

Creating Dynamic Abis pool and radio network objects
Steps

1.

Create the Dynamic Abis pool (ESE)

Note
The Dynamic Abis pool must be created on the PCU where the NSEI (that is used for the BTS) is defined. The Dynamic Abis pool must also be created on the same ETPCM where the TRX signaling is located. See also the prerequisites in Planning and managing EGPRS implementation.

2. 3. 4. 5. 6. 7. 8. 9.

Create a BCF (EFC) Create a BTS (EQC) Create handover and power control parameters (EHC, EUC) Attach BTS to RAC (EQV) Enable EGPRS by giving value Y to EGENA parameter (EQV) Define GPRS and EGPRS parameters (EQV) Enable GPRS by giving value Y to GENA parameter Create a TRX with DAP connection (ERC)

24 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

Integrating a new EDGE BSS to the radio network

4.4

Activating BCF software
Steps

1. 2. 3.

Create BCF software that supports EDGE (EWC) Attach BCF software (EWA) Activate BCF software (EWV)

4.5

Commissioning UltraSite EDGE Base Station
Before you start

Check that the BTS has EDGE-capable software or load it with the BTS Manager. For more information, see Nokia UltraSite EDGE Base Station User Manual, Commissioning.
Steps

1.

Commission FXC Transmission Configuration with UltraSite BTS Hub Manager The recommended way to commission FXC transmission unit is to use SCF file that contains all parameters including EDAPs. In addition to TCHs, TRXSIGs and OMUSIG, EDAP abis allocation must be defined in Traffic Manager dialog.

Note
When creating EDAP, the index of the first timeslot of the EDAP in the BTS has to be the same or smaller than in the BSC for this DAP. The index of the last timeslot in the BTS has to be the same or greater than in the BSC for this DAP.

Attach EDGE TRXs to EDAP that are going to use EGPRS. Traffic Manager does all needed cross connections between Abis and d1-buses.

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

25 (32)

EGPRS implementation guide for GSM/EDGE BSS

EGPRS configuration does not affect Line Interface, Radio Configuration, Synchronization nor Q1 Management settings. They are the same as currently. 2. Implement HW Configuration with Configuration Wizard in BTS HW Configurator Finish commissioning with Commissioning Wizard in BTS Manager There are no changes to the procedure related to EGPRS.

3.

4.6

Unlocking radio network objects
Steps

1. 2. 3.

Unlock the TRX (ERS) Unlock the BTS (EQS) Unlock the BCF (EFS)

26 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

Implementing EDGE in an integrated GPRS BSS

5
5.1

Implementing EDGE in an integrated GPRS BSS
Activating BCF software
Steps

1. 2. 3.

Create BCF software that supports EDGE (EWC) Attach BCF software (EWA) Activate BCF software (EWV)

5.2

Activating EDGE in UltraSite BTS already integrated in the network
Steps

1.

Configure FXC Transmission Configuration with UltraSite BTS Hub Manager Keep the existing Abis allocation and add EDAP Abis allocation in Traffic Manager dialog.

Note
When creating EDAP, the index of the first timeslot of the EDAP in the BTS has to be the same or smaller than in the BSC for this DAP. The index of the last timeslot in the BTS has to be the same or greater than in the BSC for this DAP.

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

27 (32)

EGPRS implementation guide for GSM/EDGE BSS

Attach EDGE TRXs to EDAP that are going to use EGPRS. The Traffic Manager does all the needed cross connections between Abis and d1buses. 2. Update Abis allocation to BTS Select Tools | Update Abis Allocation from BTS manager pulldown menu. When updating Abis Allocation in the BTS, ongoing CS or GPRS connections are not affected. Ongoing EGPRS connections are not allowed.

5.3

Enabling EGPRS in BSC
In order to enable EGPRS in a cell you first have to create the dynamic Abis pool and then create a TRX which uses the pool. When the TRX using the dynamic Abis pool is created, GPRS must be disabled in the cell. GPRS must be enabled in the cell (parameter GENA set to Y) and EGPRS enabled in the BTS (parameter EGENA set to Y) in order to enable EGPRS traffic in the BTS. If GENA is set to N then EGPRS traffic is also disabled.

Note
To get BCCH recovery to work correctly, it is recommended that you take the following conditions into account, when unlocked non-EDGE-capable and EDGE-capable TRXs exist in same BTS: If the BTS has EGPRS enabled (EGENA=Y) and the BCCH TRX is EDGEcapable and has the parameter GTRX set to Y, then all EDGE-capable unlocked TRXs which have GTRX set to Y should be marked as Preferred BCCH TRXs. If the BTS has EGPRS enabled (EGENA=Y) and the BCCH TRX is non-edgecapable and has the parameter GTRX set to N, then all non-EDGE-capable unlocked TRXs which have GTRX set to N, should be marked as Preferred BCCH TRXs.

Note
Deleting TRXs and taking them into use for enabling EGPRS in BSC has to be done during low traffic hours. All the calls will be dropped when this procedure is being carried out.

28 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

Implementing EDGE in an integrated GPRS BSS

Steps

1.

Create the dynamic Abis pool a. b. Check whether you have a suitable dynamic Abis pool created (ESI) If not, create the dynamic Abis pool (ESE)

Note
See the prerequisites in Planning and managing EGPRS implementation.

2. 3. 4. 5. 6.

Disable the GPRS in the cell (EQV) Lock the BTS (EQS) Lock the TRX (ERS) Delete the TRX to be connected to Dynamic Abis pool (ERD) Create a TRX which uses the dynamic Abis pool (ERC) All the TRXs that will be using EGPRS in the BTS must be attached to a dynamic Abis pool.

7. 8.

Unlock the TRX (ERS) Enable EGPRS in the BTS by giving value Y to parameter EGENA (EQV) Enable GPRS in the cell by giving value Y to parameter GENA (EQV) Unlock the BTS (EQS)

9. 10.

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

29 (32)

EGPRS implementation guide for GSM/EDGE BSS

30 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en

Runtime EDAP modification

6

Runtime EDAP modification
Before you start

" "

Check that EGPRS has already been activated in BCF. When modifying EDAP, the index of the first timeslot of the EDAP in the BTS has to be the same or smaller than in the BSC for this DAP. The index of the last timeslot in the BTS has to be the same or greater than in the BSC for this DAP. This means that when removing timeslots from EDAP/DAP, it has to be done first at the BSC side. When adding timeslots to EDAP/ DAP it has to be done first at the BTS side. Creating, modifying or deleting of EDAP in the BSC will cause a territory downgrade/upgrade procedure to all territories served by the PCU in question. This will make ongoing EGPRS/GPRS connections to pause and resume immediately. When updating Abis Allocation in the BTS, ongoing CS or GPRS connections are not affected. Ongoing EGPRS connections are not allowed. EGPRS calls cannot be ongoing during EDAP modification because cross connection between Abis and BTS internal D1-buses changes. TRXs stay in WO state all the time, voice calls are enabled during EDAP modification procedure. All modifications must be done during the maintenance window. For more information, see EGPRS Dynamic Abis pool connections.

"

"

" " "
Steps

1.

Add/remove timeslots to/from EDAP a. Modify EDAP by means of Traffic Manager Open EDAP properties dialog by clicking the right button of the mouse on top of incoming EDAP, or doubleclick EDAP, and select EDAP properties. Modify EDAP end timeslot and after that click OK.

dn03300436 Issue 1 en

? Nokia Corporation Nokia Proprietary and Confidential

31 (32)

EGPRS implementation guide for GSM/EDGE BSS

b. c.

Update Abis allocation to BTS by selecting Tools | Update Abis Allocation from BTS manager pulldown menu. Do the same modifications at BSC side (ESM) TRXs stay in WO state all the time and CS calls are enabled.

2.

Remove EDAP from the BTS a. b. c. d. Disable EGPRS for TRXs that are attached to EDAP being deleted (EQV) Delete TRX with EDAP connection Re-create TRX without EDAP connection Check if EDAP still has TRX connections

Example 2. ESI:ID=1:TRXS:; e. Delete EDAP after all the TRXs have been disconnected from it Example 3. ESG:ID=1:; f. Remove EDAP by means of Traffic Manager Delete EDAP by clicking the right button of the mouse on top of incoming EDAP and select delete signal. g. In case of FXC transmission configuration, update Abis allocation to BTS by selecting Tools | Update Abis Allocation from BTS manager pulldown menu.

Note
To remove EDAP from the BSC, no TRXs can be attached to EDAP. This means that TRXs must be deleted and recreated without EDAP defined at the BSC.

32 (32)

? Nokia Corporation Nokia Proprietary and Confidential

dn03300436 Issue 1 en


相关文章:
ApndxA_操作指南
? Microsoft SQL Server 2008 R2 SP1 2 Appendix A: Implementation Guide for a Server 安装互联网信息服务 (IIS) 在服务器上安装 IIS,可以使用下面的指令来...
...Server 2003 Security Guide Implementation Vision...
Windows Server 2003 Security Guide Implementation Vision Scope Windows_Server_2003_Security_GuideWindows_Server_2003_Security_Guide隐藏>> Windows Server 2003 Sec...
...Server 2003 Security Guide Implementation Functi...
Windows_Server_2003_Security_GuideWindows_Server_2003_Security_Guide隐藏>> Windows Server 2003 Security Guide Implementation Functional Specification <Company Name...
A Guide to the Implementation of ES standards-20100...
A Guide to the Implementation of ES standards-20100921_生活休闲。关于沃尔玛验厂的指导A Guide to the Implementation of the Wal-mart ES Standards 沃尔玛社会...
更多相关标签:
egprs | egprs edge | gprs egprs | gsm w egprs | implementation | implementation plan | open implementation | implementation 翻译 |