Download - Egprs on Bcch Trx Trial Report Tao

7/29/2019 Egprs on Bcch Trx Trial Report Tao

1/44

REPORT on EGPRS PERFORMANCE ON BCCH-TRX TRIAL

04 Mar 15, 2005 Results and Summary P. SkonN. Surachet,

L. Penrat

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

ED 04 EGPRS PERFORMANCE ON BCCH-TRX TRIAL Released

MND EGPRS Performance on BCCH-TRXPage1/44

Uo


2/44

DDOOCCUUMMEENNTTHHIISSTTOORRYY

EDITION DATE ORIGINATOR OBJECT

01 J an 16, 2005 N. Surachet Creation

02 Feb 08, 2005 L. Penrat Adding testing part IV

03 Feb 21, 2005 L. Penrat Feature Description modification

04 Mar 15, 2005 N. Surachet Results and Summary




3/44

TTAABBLLEE OOFF CCOONNTTEENNTTSS

1 INTRODUCTION....................................................................................5

2 FEATURE DESCRIPTION.........................................................................6

2.1 TRX configuration and priority .......................................................................6

2.1.1 DR (Dual Rate) TRE selection 62.1.2 TRX-TRE mapping 62.1.3 Ordering of the TRX for the PS traffic 72.1.4 Association of a TRX transmission pool to each TRX 7

2.2 EGPRS TBF on the BCCH Carrier.....................................................................7

3 TEST DESCRIPTION................................................................................9

3.1 Test Cell Selection...........................................................................................9

Part I: EGPRS Performance in BCCH-Recovery mechanism 9PART II: EGPRS performance on BCCH-TRX with different TRE types 9Part III: EGPRS performance on BCCH-TRX and non-BCCH-TRX assessment9Part IV: Packet & Circuit resource sharing 10

3.2 Test Equipments............................................................................................10

3.3 Test Schedule................................................................................................11

4 TEST PROCEDURE & RESULTS...............................................................13

4.1 EGPRS performance in BCCH-Recovery mechanism...............................13

4.1.1 Objectives 134.1.2 Test Diagram 134.1.3 Parameters Setting 134.1.4 Test Result 14

4.2 EGPRS performance on BCCH-TRX with different TRE types...................... 184.2.1 Objective 184.2.2 Test Diagram 184.2.3 Parameters Setting 194.2.4 Test Result 19

Step1: TRAD Card (G4) on BCCH-TRX..........................................................20Step2: TRADE Card (G4 Plus) on BCCH-TRX.................................................22

4.3 EGPRS Performance on BCCH-TRX & non-BCCH-TRX Assessment...........24

4.3.1 Objectives 24

4.3.2 Test Diagram 24



4.3.3 Parameters Setting 25


4/44

4.3.4 Test Result 25Step1: EGPRS performance on BCCH-TRX ..................................................25Step2: EGPRS Performance on non-BCCH-TRX...........................................29

4.4 Packet & Circuit resource sharing...............................................................33

4.4.1 Objectives 334.1.2 Test Diagram 334.4.3 Parameters Setting 344.1.4 Test Result 34

Step1: Resource sharing between EGPRS traffic & C ircuit traffic ............34Step2: Resource sharing between EGPRS traffic & GPRS traffic ..............36

5 SUMMARY AND CONCLUSION.........................................................42

6 ANNEX: TEST PARAMETERS DESCRIPTION.........................................43

6.1 GPRS/EGPRS Configuration..........................................................................43

6.2 EGPRS activation / TBF handling..................................................................43



`


5/44

1 INTRODUCTION

This document is created to present EGPRS Performance on BCCH-TRX Proposal,which will be performed in the BTS-Test at Arena site. The purpose of this test is notonly to assess the EGPRS performance comparing between BCCH-TRX and non-BCCH-TRX, but it also assesses the EGPRS performance in BCCH-Recoverymechanism, and the EGPRS performance on BCCH-TRX with different TRE types.

This trial is comprised of 4 main parts:

1. EGPRS performance in BCCH-Recovery mechanismThe purpose of this part is to observe EGPRS performance relating to BCCH-Recovery mechanism, in term of service interruption, recovery function timing

and TBF allocating behavior. See details in Section4.1.1.

2. EGPRS performance on BCCH-TRX with different TRE typesThe purpose of this part is to observe EGPRS performance in term of CodingScheme usage (MCS Modulation Coding Scheme) at either 8PSK modulationor GMSK modulation of EGPRS TBF, this part is considering an impact from twodifferent types of TRE card mapped on BCCH-TRX: TRADE card (MP-TRE as G4with EDGE plus) and TRAD card (MP-TRE as G4). See details in Section4.1.2.

3. EGPRS performance on BCCH-TRX and non-BCCH-TRX assessment.The purpose of this part is to compare EGPRS performance between EGPRS

allocated on BCCH-TRX and non-BCCH-TRX, in term of data throughput andtransfer time. See details in Section4.1.3.

4. Packet & Circuit resource sharing.The purpose of this part is to verify resource-sharing behavior for both circuit -packet traffic and EGPRS - GPRS traffic, and observe coding scheme usage ofRLC blocks for each test case. See detail in Sec tion4.1.4.

Remark: For the 2nd part, it is brought to prove with 3GPP 05.08 standard, relating tothe constraint of EGPRS on BCCH-TRX in term of output power for GMSK and 8PSKmodulation. See more details in Section2.2.




6/44

2 FEATURE DESCRIPTION

2.1 TRX configuration and priority

The BSC is in charge of the TRX configuration and the TRX priority definition for the CSand PS traffics.

In B8 release, the B7 parameter GPRS_PREF_MARK is removed and the radioresources management process only uses the TRX_PREF_MARK parameter. A TRX witha TRX_PREF_MARK parameter different from 0 (that is > 0) is reserved for the CS traffic.As in previous releases, the highest the TRX_PREF_MARK parameter is, the highest thepriority for the C S traffic is. A TRX with a TRX_PREF_MARK parameter equal to 0 is usedfor CS and PS traffics and has the lowest priority for CS traffic.

2.1.1 DR (Dual Rate) TRE selection

The first step of the algorithm is the choice of the DR TRE. The following list of orderedcriteria is used by the BSC:

- Non EDGE TRE (that is G3 TRE)

- Then Medium power EDGE TRE

- Then High power EDGE TRE

2.1.2 TRX-TRE mapping

After having selected the DR TRE, the second step of the algorithm is the TRE-TRXmapping using the same algorithm than in B7.2 release. But afterwards anadjustment is performed for PS capable TRX (that is TRX with a TRX_PREF_MARKparameter equal to 0). PS capable TRX are mapped preferentially (from the highestto the lowest priority) on the following TRE:

- Full rate, High power, EGPRS capable TRE

- Dual rate, High power, EGPRS capable TRE

- Full rate, Medium power, EGPRS capable TRE

- Dual rate, Medium power, EGPRS capable TRE

- Full rate, non EGPRS capable TRE

- Dual rate, non EGPRS capable TRE

IfPS_Pref_BCCH_TRX = true, then the BCCH TRX is mapped on the TRE with the highestpriority.




7/44

2.1.3 Ordering of the TRX for the PS traffic

The PS capable TRX (that is with TRX_PREF_MARK = 0) are ordered as follows for the PS

traffic (from the highest to the lowest priority):- BCCH TRX ifPS_Pref_BCCH_TRX = true

- Then HW TRX capability: EGPRS High power, then EGPRS Medium power, thennon EGPRS

- Then DR capability: Full rate then Dual rate

- Then size of the PDCH group: rank first the TRX having the maximum number ofconsecutive SPDCH per TRX (this is a static information given by the O&Mconfiguration of the TRX)

- Finally TRX identity: among the remaining TRX, select first the TRX having the

lowest TRX idThis ordering algorithm is obviously in line with the TRX-TRE mapping algorithm.

Finally it is important to notice that the PS capable TRX are ordered in the same wayfor the CS traffic but this time from the lowest to the highest priority to avoid as muchas possible collisions between the CS and PS traffics.

2.1.4 Association of a TRX transmission pool to each TRX

Some definitions: the term "basic Abis timeslot" refers to the Abis (64k) timeslot

carrying the CS traffic of the considered TRX. Similarly, the term "basic Abis nibble"refers to the Abis (16k) nibble carrying the CS traffic of the considered radio timeslot.

The terms "extra Abis timeslot" or "extra Abis nibble" refer to the additional Abis (64k)timeslot or Abis (16k) nibble used to carry PS traffic when the TRX is of type 2, 3, 4, or 5.

This is the last step of the configuration performed by the BSC. The TRX transmissionpool is the set of extra Abis nibbles associated to the TRX.

The biggest TRX transmission pool is assoc iated to the TRX with the highest PS priority.

2.2 EGPRS TBF on the BCCH Carrier

If the difference between the maximum output power for the 8-PSK and the GMSKmodulation on the BCCH carrier is higher than 4dB (that is 8-SPK APD > 4dB), theBCCH carrier cannot handle EDGE TBF (05.08 GSM recommendations: 8-PSKmodulated timeslots on the BCCH carrier, with the exception of TN7, may use amean power which is at most 4dB lower than the power used for GMSK modulatedtimeslots). This is due to the necessity to transmit the BCCH frequency at a constantpower level.




8/44



Moreover, the 05.08 GSM recommendations also indicates the following possibleproblem for some fast moving MS linked to the use of frequency hopping on theBCCH carrier by EDGE TBF: In the case that 8-PSK modulation is allowed on theBCCH carrier and frequency hopping including BCCH carrier is used, the reception

quality in connected mode for some fast moving MS (meaning MS experiencingDoppler frequencies of 100Hz or more) may be degraded. This may be seen as abackwards compatibility problem for some existing MS, most likely occurring if theused APD is larger than 2dB.


9/44

3 TEST DESCRIPTION

3.1 Test Cell Selection

A test cell for this trial is used BTS-Test at Arena site with 3-TRX configurations. The testarea selec tion for this trial presents as below.

Part I: EGPRS Performance in BCCH-Recovery mechanism

Objectives:

Observe EGPRS performance relating to BCCH-Recovery mechanism, in term of

service interruption, recovery function timing and TBF allocating behavior of on-going TBF before/after BCCH recovery process.

Test cell criteria:

Create cell in BTS-Test at Arena site at 3-TRX configurations with Baseband-Hopping frequenc ies (BBH).

Plug 2 TRAD cards and 1 TRDM card. Allow PS service on all TRX by set TRX_PREF_MARK = 0.

PART II: EGPRS performance on BCCH-TRX with different TRE types

Objective:

Observe the appropriate coding scheme (MCS: Modulation Coding Scheme) forEGPRS service on BCCH-TRX for each TRE type.

Test Cell Criteria:

Create cell in BTS-Test at Arena site at 3-TRX configurations with Baseband-Hopping frequenc ies (BBH).

Prepare 1 TRE for TRADE type (MP TRE as G4 EDGE plus), 2 TREs for TRAD type(MP TRE as G4), and 1 TRDM (MP TRE as G3) for the test in this part.

Allow PS and CS service on all TRX by set TRX_PREF_MARK = 0.

Part III:EGPRS performance on BCCH-TRX and non-BCCH-TRX assessment

Objectives:



Assess EDGE performance in term of data throughput and transfer time, when EDGETBF is allocated on BCCH and non-BCCH TRX.


10/44

Test cell criteria:

Create cell in BTS-Test at Arena site at 3-TRX configurations with Baseband-

Hopping frequencies. Set 1TRX to support EGPRS service as well as GPRS service, and set all TRXs to

support ordinary GSM service.

Part IV: Packet & Circuit resource sharing

Objectives:

Verify the resource sharing behavior for both circuit-packet traffic and EGPRS-GPRS traffic

Observe coding scheme usage for RLC blocks (GMSK or 8-PSK modulation)sharing on the same time slot (PDCH)

Test cell criteria:

Create cell in BTS test at 2 TRX configurations with Base band Hoppingfrequencies.

Plug 2 TRAD cards on BTS test.

3.2 Test Equipments

Test BTS and TREsTRADE card (for Part II) 1 Ea.TRAD card 2 Ea.TRDM card 1 Ea.

Radio measurement toolTEMS Investigation, EDGE capable (version5.1) 1 setTEMS Investigation, GPRS capable 1 set

MS Terminal

EDGE mobile (NOKIA6230) 1 setGPRS mobile (Sony Ericsson T610) 1 setGSM mobile 2 set



OMC-R for changing parameters and monitoring: USD-Cell overview andmonitoring TRE-TRX mapping


11/44

3.3 Test Schedule

Table below is the trial schedule for EGPRS on BCCH-TRX Performance Trial, details

as following:

09

Week 503-507 Week 508 Week 509 Week 510

17 ... 13... 14 1615 17 1918 20 21 2322 24 2625 27 28 0201 03 0504 06

Proposal Perform

TestingConclusion

&

Report

Figure1: Trial schedule for EGPRS on BCCH-TRX Performance Trial

Remark: This trial time frame is flexibly changed; it depends on the B8 migrationschedule.

The following table shows detail of each test.




12/44

Da

te

Service

Mode

Test DescriptionItera

tion

TRE

TypeTRXClass

PS_

PREF

_BCCH_

MA

RK

Numberof

TBF/PDCH

Remark

PART I

EGPRS FTP: Download 1000 KB - TRAD 4 1 1Observe BCCHrecovery behavior

01/3

EGPRS FTP: Upload 500 KB - TRAD 4 1 1Observe BCCHrecovery behavior

PART II

EGPRS FTP: Download 1000 KB 10 TRAD 4 1 1Observe throughput

per PDCH02/3

EGPRS FTP: Download 1000 KB 10 TRADE 4 1 1Observe throughputper PDCH

PART III

EGPRS FTP: Download 1000 KB 10 TRAD 4 0 1Observe throughputon BCCH-TRX

EGPRS FTP: Upload 500 KB 10 TRAD 4 0 1Observe throughputon BCCH-TRX

EGPRS FTP: Download 1000 KB 10 TRAD 4 0 1Observe throughputon non-BCCH-TRX

03/3

EGPRS FTP: Upload 500 KB 10 TRAD 4 0 1 Observe throughputon non-BCCH-TRX

PART IV

GPRS/GSM

EGPRS: FTP download 1000KBGSM: Dedicate mode

- TRAD 4 0 1Observe allocatedPDCH and TCH

EGPRS/GPRS

EGPRS: FTP download 1000KBGPRS: FTP upload 500 KB

- TRAD 4 0 2Observe throughputof eac h TBF04/3

EGPRS/GPRS

EGPRS: FTP download 1000KBGPRS: FTP download 500 KB

- TRAD 4 0 2Observe throughputof eac h TBF



Table1: Detail of each test schedule for EGPRS on BCCH-TRX Performance Proposal


13/44

4 TEST PROCEDURE & RESULTS

4.1 EGPRS performance in BCCH-Recovery mechanism4.1.1 Objectives

Observe EGPRS performance relating to BCCH-Recovery mechanism, in term ofservice interruption, recovery function timing and TBF allocating behavior of on-going TBF before/after BCCH recovery process.

4.1.2 Test Diagram

This test is to observe the behaviours during BCCH-Recovery mechanism. The figurebelow shows test-BTS configuration. PS and CS service are allowed on all TRXs, bysetting TRX_Pref_Mark = 0

BCCH

SDCCH

TRX1: TRX_PREF_MARK = 0



Figure2: Test-BTS configuration for EGPRS performance in BCCH-Recovery mechanism

The 3 TRXs on test-BTS are mapped on 3 TRE cards, 2 TRAD and 1 TRDM. Download(Downlink bias) and upload (Uplink bias) data from external FTP server is used asfollowing diagram.

PS_PREF_BCCH_TRX = 1

FTP download 1000 KBytes

FTP upload 500 KBytes

TRX Class 4(MAX_EGPRS) = MCS8)

Figure3: Test diagram for EGPRS performance in BCCH-Recovery mechanism

4.1.3 Parameters Setting



This sub-section presents the relating parameters for EGPRS performance in BCCH-Recovery mechanism part.


14/44

Parameter Setting value Description

EN_EGPRS Enable Enables/Disables EGPRS traffic in the cell.

MAX_EGPRS_MCS MCS8Maximum Modulation and Coding Schemeused for EGPRS traffic in the cell.

TBF_DL_INIT_MCS MC S8

Value of the downlink modulation and codingscheme when the link adaptation a lgorithm isdisabled or initial value of the modulation andcoding scheme otherwise.

TBF_UL_INIT_MCS MC S4

Value of the uplink modulation and codingscheme when the link adaptation a lgorithm isdisabled or initial value of the modulation and

coding scheme otherwise.

TRX_PREF_MARK 0 Preference mark assigned to a given TRX.

PS_PREF_BCCH_TRX 1Indicates whether or not the PS requests shallbe preferentially served with PDCH(s) of theBCCH TRX

MAX_PDCH 4Maximum number of slave and master PDCHsthat can be established in the cell.

Table2: Parameters setting for EGPRS performance in BCCH-Recovery mechanism

4.1.4 Test Result

This following indicators are taken into account and considered during the test forthis part:

- TRE-TRX mapping relation before and after BCCH-Recovery action- Location of allocated PDCH of EGPRS TBF before and after BCCH-

Recovery action- BCCH-Recovery period

- EGPRS TBF behavior thru BCCH-Recovery mechanism

TRE-TRX Mapping Relation

This presents the results in term of TRE-TRX mapping relation, which were performed 3iterations for 1.5Mbytes download (downlink bias) by external FTP server (www.air-price.com)

Result



In the test cell, the BCCH-TRX was automatically recovered successfully when this TRX

was disabled by unplugging the Rx-Cable at the BTS test. See details as below:
http://www.air-price.com/http://www.air-price.com/http://www.air-price.com/http://www.air-price.com/


15/44

1st time:

Figure4: TRE-TRX mapping relation result for the 1st time

2nd time:

Figure5: TRE-TRX mapping relation result for the 2nd timeFigure5: TRE-TRX mapping relation result for the 2nd time

3rd time:3rd time:

Figure6: TRE-TRX mapping relation result for the 3rd timeFigure6: TRE-TRX mapping relation result for the 3rd time

Location of allocated PDCH of EGPRS TBF Location of allocated PDCH of EGPRS TBF

This presents the results in term of location of allocated PDCH of EGPRS TBF by celloverview from OMC-R point of view thru BCCH-Recovery action.

This presents the results in term of location of allocated PDCH of EGPRS TBF by celloverview from OMC-R point of view thru BCCH-Recovery action.

ResultResult

Locations of PDCHs were allocated on the supported TRE card G4, TRAD card, forboth before and after BCCH-Recovery action. See details as below:Locations of PDCHs were allocated on the supported TRE card G4, TRAD card, forboth before and after BCCH-Recovery action. See details as below:



TRX1 TRE2 TRAD7 TRX1 TRE1 TRAD10 TRX1 TRE1 TRAD10

TRX2 TRE3 TRDM4 TRX2 TRE3 TRDM4 TRX2 TRE3 TRDM4

TRX3 TRE1 TRAD10 TRX3 TRX3 TRE2 TRAD7

Before BCCH-Recovery After BCCH-Recovery Plug Disable TRE Back

DISABLE

Unplug Rx-cableon TRAD7 card

Plug Rx-cable onTRAD7 card



TRX3 TRE2 TRAD7 TRX3 TRX3 TRE1 TRAD10


DISABLE

Unplug Rx-Cableon TRAD10 card

Plug Rx-Cable onTRAD10 card



TRX3 TRE2 TRAD7 TRX3 TRX3 TRE1 TRAD10DISABLE


Plug Rx-cable onTRAD10 card

Unplug Rx-Cableon TRAD10 card


16/44

1st step: No EGPRS traffic (Idle mode)

Figure7: Location of allocated PDCH of EGPRS TBF at the 1st step

2nd step: Location of allocated PDCH with EGPRS traffic, before BCCH-Recoveryaction

Figuree8: Location of a llocated PDCH of EGPRS TBF at the 2nd step

3rd step: Location of allocated PDCH during BCCH-Recovery mechanism (by disableRx-Cable at the BTS test)

Figure9: Location of allocated PDCH of EGPRS TBF at the 3rd step

4th step: Location of allocated PDCH with EGPRS traffic, after BCCH-Recovery actionwas successful




17/44

Figure10: Location of allocated PDCH of EGPRS TBF at the 4th step

BCCH-Recovery Period

This presents the result in term of period for BCCH-Recovery mechanism bystopwatch measuring (manually).

Result

In the BCCH-Recovery mechanism, the BTS test takes 5 minutes approximately inBCCH-Recovery mechanism since BCCH-TRX was disabled (by unplugging Rx-Cable)until this TRX was recovered successfully (already on-service).

Table3: BCCH-Recovery period measurement

EGPRS TBF behavior thru BCCH-Recovery mechanism

When EGPRS traffic was established, 4PDCHs were allocated at TS1-TS4 on BCCH-TRX.In the meantime, the on-going active EGPRS TBF was interrupted and then suddenlydropped after the BCCH-TRX was disabled. During the BCCH-Recovery mechanismthat takes 5 minutes approximately, the packet service (or even circuit service)

requests were rejected. However, the EGPRS TBF can be established and workingproperly again after the BCCH was successfully recovered to another active TREs inthe cell.



No. BCCH-Recovery Period (min)

1 5.04

2 5

3 4.58


18/44

4.2 EGPRS performance on BCCH-TRX with different TRE types

4.2.1 Objective

Observe the appropriate coding scheme (MCS: Modulation Coding Scheme) forEGPRS service on BCCH-TRX for each TRE type.

Remark:

According to 3GPP 8-PSK modulated timeslots on the BCCH carrier, with theexception of TN7, may use a mean power which is at most 4 dB lower than thepower used for GMSK modulated timeslots.

If the difference between the maximum output power for the 8-PSK and the GMSK

modulations on the BCCH carrier is higher than 4 dB (that is 8-PSK APD > 4 dB), theBCCH carrier cannot handle EDGE TBF. The table below shows power back offbetween 2 TRE Type during 8-PSK modulation used.

DCS 1800 Medium PowerTRAD

DCS 1800 Medium PowerTRADE EDGE Plus

TX output power, GMSK35 W 0.5/+1 dB

(45.44 dBm)35 W 0.5/+1 dB

(45.44 dBm)

TX output power, 8-PSK12 W (40.79 dBm)

(4.65 dB back off)

30 W (44.77 dBm)

(0.67 dB back off)

Table4: Output power specification for TRAD and TRADE card

4.2.2 Test Diagram

This test is to observe the performance on BCCH-TRX with two kinds of TRE type:TRADE (MP-TRE as G4 EDGE Plus) and TRAD (MP-TRE as G4). In addition, downloadwith external FTP server is taken into account for this test.

The figure below shows test-BTS configuration. PS and CS service are allowed on a llTRXs by setting TRX_Pref_Mark = 0

BCCH

SDCCH




Figure11: Test-BTS configuration for EGPRS performance on BCCH-TRX with different TRE types




19/44



STEP 1, 3TRXs map on:2 TRAD1 TRDM

STEP 2, 3TRXs map on:1 TRADE1 TRAD1 TRDM

Figure12: Test diagram for EGPRS performance on BCCH-TRX with different TRE types


This sub-section presents the relating parameters for EGPRS performance on BCCH-

TRX with different TRE types part.







Value of the uplink modulation and codingscheme when the link adaptation a lgorithm isdisabled or initial value of the modulation andcoding scheme otherwise.




Table5: Parameters setting for EGPRS performance on BCCH-TRX with different TRE types

4.2.4 Test Result



This following indicators are taken into account and considered during the test in thispart:


20/44

- Data throughput (kbps per TS) and transfer time between TRAD card (G4)and TRADE (G4 Plus)

- Location of allocated PDCH of EGPRS TBF- TRE-TRX mapping relation

Step1: TRAD Card (G4) on BCCH-TRX

This presents the results of each indicator above when TRAD card was set as BCCH-TRX and 6 iterations for 1.5Mbytes download (downlink bias) by external FTP server,shown the result as below:

Data throughput (kbps per TS) and Transfer time

This presents the result in term of transfer time (seconds) and data throughput (kbps

per TS) at both average application throughput (kbps) and RLC throughput (kbps) interm of MCS distribution usage.

Result

Transfer time (sec) and data throughput in term of application throughput (kbps) areshown in the table below:

Table6: Data throughput and transfer time result

Remark: The maximum and minimum values from the test were excluded in theaverage values calculation

RLC throughput (kbps) in term of MCS usage distribution is shown as the followinggraph:



No. Data Throughput (kbps per TS) Transfer Time (Sec)

1 40.8 294.22

2 42.72 281

3 32.16 372.85

4 39.28 305.67

5 32.72 367.05

6 45.44 264.2

Average 38.88 311.99


21/44

Figure13: MCS usage distribution RLC throughput (kbps)

Additionally, BEP (Mean) value distribution usage is shown as the following graph:

Figure14: BEP (Mean) value distribution usage

From all results above, EGPRS performance, when allocated on BCCH-TRX by TRADcard, has an average data throughput equals to 38.88kbps per TS and transfer time311.99 seconds. Most of EGPRS TBFs were used at MCS-8 coding scheme and haveBEP (Mean) value at the best condition, 31-value.

Location of allocated PDCH of EGPRS TBF

This presents the result in term of the location of allocated PDCHs for EGPRS TBF

Result

All of iterations were providing the same result of a llocated PDCHs location, shown asfollowing figure:



Distributi on of MCS

0

5000

10000

15000

20000

25000

3000035000

40000

45000

50000

MCS-1 MCS-2 MCS-3 MCS-3

(pad)


(pad)

MCS-7 MCS-8

MCS

Nb

Number

BEP (Mean) Value Distr ibutio n

0

5000

10000

15000

20000

25000

30000

35000

1 4 7 10 13 16 19 22 25 28 31

BEP (Mean)

Number

Number


22/44

Figure15: Location of allocated PDCHs of active EGPRS TBF


This presents the result in term of TRE-TRX mapping relation

Result

All of iterations were providing the same result of TRE-TRX mapping relation becauseof no recovery action on BCCH-TRX, shown as following figure:

Figure16: TRE-TRX mapping relation

Step2: TRADE Card (G4 Plus) on BCCH-TRX

This presents the results of each indicator above when TRADE card was set as BCCH-TRX and 6 iterations for 1.5Mbytes download (downlink bias) by external FTP server,shown the result as below:

Data throughput (kbps per TS) and Transfer time

This presents the result in term of transfer time (seconds) and data throughput (kbpsper TS) for application throughput (kbps)

Result

In the test of this section, there was an irregular measurement found, presents asfollowing.

- Data throughput: 19.2kbps per TS approximately

- Transfer time: 625.75 seconds



TRX1 TRE2 TRAD7

TRX2 TRE3 TRDM4

TRX3 TRE1 TRAD10


23/44

- Very low BEP (Mean) value: 19-21 approximately- Very low of C/I value: 10-12 approximately- MCS coding scheme usage was roughly stable at MCS-7

From all results above, EGPRS performance has an irregular value, too low value fordata throughput, BEP and C/I. This might be caused from hardware degradation at

TRADE card (G4 Plus).

Summary from Section4.2

The results from this part, we can notice that EGPRS performance in term of datathroughput, and transfer time and BEP (Mean) value from TRAD card (G4) was good,but the value from TRADE card (G4 Plus) was irregular, this might be impacted fromhardware degradation (TRADE card). Therefore, for this part, it cannot be comparedor conc luded EGPRS performance result on different TRE types.




24/44

4.3 EGPRS Performance on BCCH-TRX & non-BCCH-TRX Assessment

4.3.1 Objectives

Assess EDGE performance in term of data throughput and transfer time, when EDGETBF is allocated on BCCH and non-BCCH TRX.

4.3.2 Test Diagram

This EGPRS test is to assess the performance when allocating TBF on BCCH-TRX andnon-BCCH-TRX:

STEP 1:

TRX_PREF_MARK = 0 on BCCH-TRX

STEP 2:TRX_PREF_MARK = 0 on non-BCCH-TRX


FTP upload 500 KBytes


Figure17: Test diagram for EGPRS performance on BCCH-TRX and non-BCCH-TRX assessment

This following sub-section describes TRX_PREF_MARK setting for each step:

Step1: Design 3TRXs mapping to 2 TRAD cards and 1 TRDM card with

PS_PREF_BCCH_TRX = 0, and observe the EGPRS performance on BCCH-TRX.

BCCH

SDCCH




Figure18: Test-BTS configuration for EGPRS performance on BCCH-TRX section

Step2: Design 3TRXs mapping to 2 TRAD cards and 1 TRDM card with

PS_PREF_BCCH_TRX = 0, and observe the EGPRS performance on non-BCCH-TRX.

BCCH

SDCCH




Figure19: Test-BTS configuration for EGPRS performance on non-BCCH-TRX sec tion




25/44








Value of the uplink modulation and coding

scheme when the link adaptation a lgorithm isdisabled or initial value of the modulation andcoding scheme otherwise.

TRX_PREF_MARK 0,1 Preference mark assigned to a given TRX.



Table7: Parameters setting for EGPRS performance on BCCH-TRX and non-BCCH-TRX

4.3.4 Test Result

The following indicators are taken into account and considered during the test in thispart:

- Data throughput (kbps per TS) and transfer time between TRAD card (G4)and TRADE (G4 Plus)

-Location of allocated PDCH of EGPRS TBF- TRE-TRX mapping relation

Step1: EGPRS performance on BCCH-TRX

This presents the results of each indicator above on BCCH-TRX, which was pluggedby TRAD card (G4). This section performed 10 and 5 iterations for 1.5Mbytesdownload and upload by external FTP server respectively, shown the result as below:




26/44

Data throughput (kbps) and Transfer time

This presents the result in term of transfer time (seconds) and data throughput (kbpsper TS) at both average application throughput (kbps) and RLC throughput (kbps)in

term of MCS distribution usage.

Result



Remark: the maximum value from the test was excluded in the average valuescalculation.

RLC throughput (kbps) in term of MC S usage distribution for both download andupload are shown as the following graph:

Figure20: MC S usage distribution RLC throughput (kbps) at download direction



Data Throughput (kbps per TS) Transfer t ime (second) Data Throughput (kbps per TS) Transfer t ime (second)

1 36.19 110.61 13.84 433.53

2 39.2 102.12 15.88 377.7

3 36.08 110.88 15.72 381.64

4 39.17 102.16 15.72 382.03

5 37.28 107.31 15.8 379.56

6 36.91 108.42 - -

7 39.25 101.93 - -

8 36.08 110.9 - -

9 38.37 104.28 - -

10 36.37 110.04 - -

Average 37.45 106.98 15.78 380.23

Download UploadNo.

Downlin k - MCS Usage Distribution

0

2000

4000

6000

800010000

12000

14000

16000

18000


(pad)


(pad)

MCS--7 MCS-8

MCS

Numb

er

Number


27/44

Figure21: MCS usage distribution RLC throughput (kbps) at upload direc tion


Figure22: BEP (Mean) value distribution usage at download direc tion

Figure23: BEP (Mean) value distribution usage at upload direction

From all results above, EGPRS performance at download direction, when allocatedon BCCH-TRX by TRAD card, has an average data throughput equals to 37.45kbpsper TS and transfer time 106.98 seconds. Most of EGPRS TBFs were used at MCS-8coding scheme and have BEP (Mean) value at the best condition, 31-value.



Uplink - MCS Usage Distribution

0

5000

10000

15000

20000

25000


(pad)


(pad)

MCS--7 MCS-8

MCS

Number

Number

Downlink - BEP (Mean) Value Distribution

0

5000

10000

15000

20000

25000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31BEP (Me an)

Number

Number

Uplink - BEP (Mean) Value Distribution

0

5000

10000

15000

20000

25000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31BEP (Me an)

Number

Number


28/44

In addition, EGPRS performance at upload direction, when allocated on BCCH-TRXby TRAD card, has an average data throughput equals to 15.78kbps per TS andtransfer time 380.23seconds. Most of EGPRS TBFs were used at MCS-4 coding schemeand have BEP (Mean) value at the best value condition, 31-value.


This presents the result in term of the location of allocated PDCHs for EGPRS TBF.

Result

All of iterations were providing the same result of allocated PDCHs location at bothdownload and upload direction, shown as following figure:

Figure24: Location of a llocated PDCHs of EGPRS TBF at download direction

Figure25: Location of a llocated PDCHs of EGPRS TBF at upload direction


This presents the result in term of TRE-TRX mapping relation

Result





29/44


Step2: EGPRS Performance on non-BCCH-TRX

This presents the results of each indicator above on non-BCCH-TRX, which wasplugged by TRAD card (G4). This section performed 10 and 5 iterations for 1.5Mbytesdownload and upload by external FTP server respectively, shown the results as

below:


This presents the result in term of transfer time (seconds) and data throughput (kbpsper TS) at both average application throughput (kbps) and RLC throughput (kbps) interm of MCS distribution usage.

Result



Remark: The minimum value from the test was excluded in the average valuescalculation.



TRX1 TRE2 TRAD7

TRX2 TRE1 TRAD10

TRX3 TRE3 TRDM4


1 38.29 104.52 15.4 389.25

2 39.28 101.89 16.04 374.58

3 38.83 103.08 15.48 388.2

4 38.45 105.36 16.12 372.49

5 39.15 102.25 15.92 377.29

6 39.28 101.89 - -

7 39.57 101.1 - -

8 38.77 103.18 - -

9 39.04 102.48 - -

10 40.19 99.55 - -

Average 39.03 102.55 15.89 378.14

No.Download Upload


30/44

RLC throughput (kbps) in term of MC S usage distribution for both download andupload are shown as the following graph:

Figure27: MC S usage distribution RLC throughput (kbps) at download direction

Figure28: MCS usage distribution RLC throughput (kbps) at upload direc tion


Figure29: BEP (Mean) value distribution usage at download direc tion



Downlink - MCS Usage Distribution

0

2000

4000

6000

8000

10000

12000

14000

16000

18000


(pad)


(pad)

MCS-7 MCS-8

MCS

Number

Number

Uplink - MCS Usage Distribution

0

5000

10000

15000

20000

25000

30000

35000

40000


(pad)


(pad)

MCS-7 MCS-8

MCS

Number

Number

Downlin k - BEP (Mean) Value Distribution

0

5000

10000

15000

20000

25000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31BEP (Me an)

Number

Number


31/44

Figure30: BEP (Mean) value distribution usage at uplink direc tion

From all results above, EGPRS performance at download direction, when allocated

on non-BCCH-TRX by TRAD card, has an average data throughput equals to39.03kbps per TS and transfer time 102.55 seconds. Most of EGPRS TBFs were used atMCS-8 coding scheme and have BEP (Mean) value at the best condition, 31-value.

In addition, EGPRS performance at upload direction, when allocated on non-BCCH-TRX by TRAD card, has an average data throughput equals to 15.89kbps per TS andtransfer time 378.14 seconds. Most of EGPRS TBFs were used at MCS-4 coding schemeand have BEP (Mean) value at the best value condition, 31-value.


This presents the result in term of the location of allocated PDCHs for EGPRS TBF.

Result

All of iterations were providing the same result of allocated PDCHs location at bothdownload and upload direction, shown as following figure.

Figure31: Location of a llocated PDCHs of EGPRS TBF at download direction



Uplink - BEP (Mean) Value Distribution

0

5000

10000

15000

20000

2500030000

35000

40000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31BEP (Mean)

Number

Number


32/44

Figure32: Location of a llocated PDCHs of EGPRS TBF at upload direction


This presents the result in term of TRE-TRX mapping relation.

Result



Summary from Section4.3

The results from this part, we can notice that EGPRS performance in term of datathroughput and transfer time from TRAD card on non-BCCH-TRX are slightly betterthan TRAD card on BCCH-TRX around 4.11% and 3.74% for download and uploadrespectively.

Actually, the data throughput on BCCH-TRX and non-BCCH-TRX should be similarity (Itis under the same frequencies BBH, the same TRE card, the same a llocated PDCHs& the same packet size), however, this might be impacted from the external FTPserver (at www.air-price.com) that was selected to perform download and uploaddata for this trial. It is the uncontrollable factor. This might be the reason why thedata throughput on non-BCCH-TRX was better than the result on BCCH-TRX.



TRX1 TRE2 TRAD7

TRX2 TRE1 TRAD10

TRX3 TRE3 TRDM4
http://www.air-price.com/http://www.air-price.com/


33/44

4.4 Packet & Circuit resource sharing

4.4.1 Objectives

Verify the resource sharing behavior for both circuit-packet traffic and EGPRS-GPRS traffic

Observe coding scheme usage for RLC blocks (GMSK or 8-PSK modulation)sharing on the same time slot (PDCH)

4.1.2 Test Diagram

Step1: Design 2TRXs mapping to 2 TRAD cards with PS_PREF_BCCH_TRX = 0, andlock TRX 2. Observe the PS and CS traffic sharing on same TRX.

LOCKEDTRX2: TRX_PREF_MARK = 0

BCCH

SDCCH



MAX_PDCH 4Maximum number of slave and master PDCHs

that can be established in the cell.

Figure34: Test-BTS configuration for packet-c ircuit resource sharing

Step2: Design 2TRXs mapping to 2 TRAD cards with PS_PREF_BCCH_TRX = 0, observethe coding scheme of G PRS TBF and EGPRS TBF, which sharing on same PDCH.Set parameter MAX_PDCH = 1 for forcing PS traffic sharing on same PDC H.


BCCH

SDCCH




Figure35: Test-BTS configuration for packet-c ircuit resource sharing




34/44








Value of the uplink modulation and codingscheme when the link adaptation a lgorithm isdisabled or initial value of the modulation andcoding scheme otherwise.



Table10: Parameters setting for packet-circuit resource sharing

4.1.4 Test Result

Step1: Resource sharing between EGPRS traffic & C ircuit traffic


- Resource sharing between circuit traffic (GSM call) and packet traffic(EGPRS) on the same TRX

- Signal strength (RxLev dBm) on BCCH-TRX observation

Resource sharing between C ircuit traffic (GSM call) and Packet traffic (EGPRS)

This presents the result in term of the location of allocated time slots that were sharedfor circuit traffic (GSM call) and packet traffic (EGPRS).

Figure36: Time slot in idle mode




35/44

Figure37: Location of allocated time-slot for circuit traffic and EGPRS traffic

Figure38: Location of allocated time slot for circuit traffic without EGPRS traffic

Summary:

From the above results, both ciruit traffic (GSM call) and packet traffic (EGPRS traffic)can be well shared on the same TRX.

In addition, from the figure47 above, EGPRS traffic by MS calss10 can share theresource at only 3 time slots with circuit traffic on the same TRX due to oneparameter setting: High_Traffic_Load_GPRS = 80%, this leads to limit the availabletime slot for any traffic at 4 time slots, so when circuit traffic consumed 1 time slot,then EGPRS traffic can allocate only 3 time slots as the result above.

Signal Strength on BCCH-TRX

This presents the result in term of RxLev (dBm unit) distribution on a BCCH-TRX by TRADcard between before and after established EGPRS traffic that performed 5 iterationson this TRX.

Figure39: RxLev (dBm) on BCCH-TRX without EGPRS traffic (only GMSK measurement)



RxLev Distribution

0

500

1000

1500

2000

2500

3000

-55 -56 -57 -58 -59 -60 -61 -62 -63 -64 -65 -66 -67 -68 -69 -70 -71 -72 -73 -74 -75

RxLev (dBm)

Number

Number


36/44

Figure40: RxLev (dBm) on BCCH-TRX with EGPRS traffic (both GMSK & 8-PSK measurement)

Summary:

From the above results, RxLev on BCCH-TRX without EGPRS traffic can be measuredat the range of 59 to 61dBm, and RxLev on BCCH-TRX with EGPRS traffic can bemeasured at the range of 60 to 62dBm. This presents that the level of signal isfluctuating 2-3dBm comparing between with and without EGPRS traffic on theBCCH-TRX time slot.

Step2: Resource sharing between EGPRS traffic & GPRS traffic

A. EGPRS Download Traffic & GPRS Download Traffic


- Resource sharing behavior between EGPRS traffic at download directionand GPRS traffic at download direction

- Data throughput (kbps per TS), transfer time and MCS-CS coding schemeusage distribution for both EGPRS and GPRS traffic

Resource sharing between EGPRS and GPRS traffic

This presents the result in term of the location of allocated time slots that were sharedfor EGPRS traffic in download direction and GPRS traffic in download direction.

Figure41: Location of allocated time slots for both EGPRS and GPRS traffic



RxLev Distribution

0

500

1000

1500

2000

2500

3000

3500

-55 -56 -57 -58 -59 -60 -61 -62 -63 -64 -65 -66 -67 -68 -69 -70 -71 -72 -73 -74 -75

RxLev (dBm )

Number

Number


37/44

Summary:

From the above result, EGPRS traffic and GPRS traffic can be well shared on thedame TRX at the same time slot (PDCH)


This presents the result in term of data throughput in term of application throughput(kbps per TS), transfer time (sec) and coding scheme usage distribution for bothEGPRS traffic in download and GPRS traffic in download.

Result



Coding scheme usage distribution for both EGPRS and GPRS traffic in download

direction are shown as the following graph:

Figure42: MCS usage distribution (RLC throughput) for EGPRS traffic at download direc tion



Data Throughput (kbps per TS) Transfer time (second) Data Throughput (kbps per TS) Transfer time (second)

1 18 667.93 11.6 1033.73

2 17.6 681.46 11.76 1021.89

3 14.88 807.51 10.08 1192.32

Average 15.88 770.05 10.88 1109.41

No.EGPRS Traffic - Download GPRS Traffic - Download


0

5000

10000

15000

20000

25000

30000

35000


(pad)


(pad)

MCS-7 MCS-8

MCS

Number

Number


38/44

Figure43: CS usage distribution (RLC throughput) for GPRS traffic at downlink direc tion

Summary:

From the above results, EGPRS performance in this part has an average datathroughput at 15.88kbps, transfer time at 770 seconds approximately, and the mostpenetrating of MCS usage distribution (or RLC throughput) was at MC S-4 and MCS-8.

These changes of MCS coding scheme were mainly impacted from sharing resource(one PDCH) with GPRS traffic.

In addition, GPRS performance in this part has an average data throughput at10.88kbps, transfer time at 1109 seconds approximately, and the most penetrating ofCS usage distribution (or RLC throughput_ was at CS-4.

B. EGPRS Download Traffic & GPRS Upload Traffic


- Resource sharing between EGPRS traffic at download direction and GPRStraffic at upload direction

- Data throughput (kbps per TS), transfer time and MCS-CS coding scheme

usage distribution for both EGPRS and GPRS traffic

Resource sharing between EGPRS and GPRS traffic

This presents the result in term of the location of allocated time slots that were sharedfor EGPRS traffic in download direction and GPRS traffic in upload direction.



Downli nk - CS Usage Distributi on

0

10000

20000

30000

40000

50000

60000

70000

80000

90000

CS-1 CS-2 CS-3 CS-4MCS

Number

Number


39/44

Figure44: Location of allocated time slot for both EGPRS and GPRS traffic

Summary:

From the above result, both EGPRS traffic and GPRS traffic can be well shared on thesame TRX at the same time slot (PDCH).


This presents the result in term of data throughput in term of application throughput(kbps per TS), transfer time (sec) and coding scheme usage distribution for bothEGPRS traffic in download and GPRS traffic in upload direction.

Result



Coding scheme usage distribution for EGPRS traffic in download direction and GPRStraffic in upload direction are shown as the following graph:




1 14.08 852.83 13.04 919.7

2 14.72 815.41 13.12 914.59

3 14.64 818.41 13.2 907.63

Average 14.48 828.88 13.12 913.97

No.EGPRS Traffic - Download GPRS Traffic - Upload


40/44

Figure45: MCS usage distribution (RLC throughput) for EGPRS traffic at download direc tion

Figure46: CS usage distribution (RLC throughput) for GPRS traffic at upload direction

Summary:

From the above results, EGPRS performance in this part has an average datathroughput at 14.48kbps, transfer time at 828 seconds approximately, and the mostpenetrating of MCS usage distribution (or RLC throughput) was at MCS-4. This is thelimitation of coding scheme usage for EGPRS when it is allocating on the same timeslot (PDCH) with GPRS in upload direction. When GPRS traffic needs to upload data,MS has to notice the USF information at each RLC block to prepare sending thedata. This situation impacts to any time slot (PDCH), which will be used for GPRSupload, to support in GMSK modulation for GPRS behavior. Therefore, this is indirectlyimpacted to EGPRS TBF, which is allocated in the same time slot (PDCH) with GPRSupload, has to use in GMSK modulation at MCS-4 maximum coding scheme fordownload any data.




0

10000

20000

30000

40000

50000

60000

70000

80000


(pad)


(pad)

MCS-7 MCS-8

MCS

Number

Number

Uplink - CS Usage Distribution

0

10000

20000

30000

40000

50000

60000

70000

CS-1 CS-2 CS-3 CS-4

CS

Number

Number


41/44

However, this problematic situation for EGPRS TBF especially for download can berelieved by enabling parameter reallocation triggered T4, which will handle theallocated PDCH for GPRS upload (the same PDCH for EGPRS TBF) to reallocate toanother available time slot (PDCH), in order to gain MCS or throughput for EGPRS TBF

allocated on that PDCH.



In addition, GPRS performance in this part has an average data throughput at13.12kbps, transfer time at 913.97 seconds, and the most penetrating of CS usagedistribution (or RLC throughput) was at CS-4.


42/44

5 SUMMARY AND CONCLUSION

This trial focused on four main areas:

- BCCH recovery mechanism & EGPRS performance- EGPRS performance on BCCH with different TRE types- EGPRS performance on BCCH & non-BCCH assessment- Resource sharing of EGPRS

The trial presented that BCCH recovery mechanism on BCCH-TRX was successfulwhen BCCH-TRX was disabled. This mechanism took 5 minutes approximately. ForEGPRS service point of view, the on-going EGPRS service on BCCH was suddenlydropped when this TRX was disabled, however, EGPRS service then was achieved

again when BCCH was recovered successfully to another active TREs in the test cell.

EGPRS performance on BCCH by TRAD card has 38.88kbps per TS for average datathroughput, 311.99 seconds for transfer time, as well as most of TBFs were used atMCS-8 coding scheme and 31 value for BEP mean value. In addition, EGPRSperformance on BCCH by TRADE card has 19.2 kbps per TS for data throughput,625.75 seconds for transfer time, as well as most of TBFs were used at MCS-7 and 19-21 value for BEP mean value. As above results, values from TRADE card were irregular,this might be caused from hardware degradation (TRADE card). Therefore, for thispart, it cannot be compared or concluded EGPRS performance result on different

TRE types.

EGPRS performance in term of data throughput and transfer time (by TRAD card) onnon-BCCH (TCH) were slightly better than on BCCH around 4.11% and 3.74% approxfor download and upload respectively.

PDCHs resource were well shared between EGPRS call and GSM call on the sametimeslot, as well as between EGPRS call and download GPRS call. Except EGPRS calland upload GPRS call case, EGPRS call can adapt to maximum coding scheme atMCS-4, however, this situation can be relieved by enabling parameter reallocationtriggered T4.

From all results above, EGPRS can be implemented on either BCCH or non-BCCH(TCH), this depends on the objec tive and strategy. If EGPRS is deployed on BCCH, itwill imply that clean frequencies are guaranteed and EGPRS service is ensured byBCCH recovery mechanism whenever BCCH got faulty. However, if EGPRS isdeployed on TCH, it will benefit high utilization of capacity resource and avoid thelimitation of EGPRS TBF handle on BCCH when the difference of maximum outputpower for 8-PSK and GMSK modulation is higher than 4dB (referred to 05.08 GSMrecommendation).




43/44

6 ANNEX: TEST PARAMETERS DESCRIPTION

6.1 GPRS/EGPRS Configuration

Logical name Definition Type Range Instance

TRX_PREF_MARKPreference mark assigned to a TRXto favour or disfavour CS radioresource allocations on a TRX.

Number 0 to 7 TRX

0: PS/CS TRX: This TRX can carry PS and C S traffic and has the lowest preference in the TCH sub-channel selectionprocess used to serve a CS call.1: CS TRX with preference mark 1: This TRX can carry only CS traffic and has the preference mark 1 in the TCH sub-channel selec tion process used to serve a C S call.

6.2 EGPRS activation / TBF handling

Logical name Definition Type Range Instance

EN_EGPRSEnables/Disables EGPRS traffic in thecell.

FlagTrue-False

Cell

MAX_EGPRS_MCSMaximum Modulation and CodingScheme used for EGPRS traffic in thecell.

NumberMCS1

toMCS9

Cell

PS_PREF_BCCH_TRXIndicates whether or not the PSrequests shall be preferentiallyserved with PDCH(s) of the BCCH TRX

Flag 0 or 1 Cell

TBF_DL_INIT_MC S

Value of the downlink-codingscheme when the link adaptationalgorithm is disabled or initial valueof the coding scheme otherwise.

NumberMCS1

toMCS9

Cell

TBF_UL_INIT_MCS

Value of the uplink-coding schemewhen the link adaptation

algorith111111111m is disabled orinitial value of the coding schemeotherwise.

Number

MCS1

toMCS4

Cell




44/44

END OFDOCUMENT