Académique Documents
Professionnel Documents
Culture Documents
Un o
04 ED ED MND
DOCUMENT HISTORY
EDITION 01 02 03 04
DATE Jan 16, 2005 Feb 08, 2005 Feb 21, 2005 Mar 15, 2005
OBJECT Creation Adding testing part IV Feature Description modification Results and Summary
ED MND
04
TABLE OF CONTENTS
1 INTRODUCTION ....................................................................................5 2 FEATURE DESCRIPTION .........................................................................6
2.1 TRX configuration and priority ....................................................................... 6 2.1.1 DR (Dual Rate) TRE selection 6 2.1.2 TRX-TRE mapping 6 2.1.3 Ordering of the TRX for the PS traffic 7 2.1.4 Association of a TRX transmission pool to each TRX 7 2.2 EGPRS TBF on the BCCH Carrier ..................................................................... 7
24 24 25
Released Page 3/44
4.3.4 Test Result 25 Step1: EGPRS performance on BCCH-TRX .................................................. 25 Step2: EGPRS Performance on non-BCCH-TRX........................................... 29 4.4 Packet & Circuit resource sharing............................................................... 33 4.4.1 Objectives 33 4.1.2 Test Diagram 33 4.4.3 Parameters Setting 34 4.1.4 Test Result 34 Step1: Resource sharing between EGPRS traffic & Circuit traffic............ 34 Step2: Resource sharing between EGPRS traffic & GPRS traffic.............. 36
ED MND
04
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 not only to assess the EGPRS performance comparing between BCCH-TRX and nonBCCH-TRX, but it also assesses the EGPRS performance in BCCH-Recovery mechanism, 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 mechanism The purpose of this part is to observe EGPRS performance relating to BCCHRecovery 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 types The purpose of this part is to observe EGPRS performance in term of Coding Scheme usage (MCS Modulation Coding Scheme) at either 8PSK modulation or GMSK modulation of EGPRS TBF, this part is considering an impact from two different types of TRE card mapped on BCCH-TRX: TRADE card (MP-TRE as G4 with 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 and transfer 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 of RLC blocks for each test case. See detail in Section4.1.4. Remark: For the 2nd part, it is brought to prove with 3GPP 05.08 standard, relating to the constraint of EGPRS on BCCH-TRX in term of output power for GMSK and 8PSK modulation. See more details in Section2.2.
ED MND
04
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 CS and PS traffics. In B8 release, the B7 parameter GPRS_PREF_MARK is removed and the radio resources management process only uses the TRX_PREF_MARK parameter. A TRX with a 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 the priority for the CS traffic is. A TRX with a TRX_PREF_MARK parameter equal to 0 is used for CS and PS traffics and has the lowest priority for CS traffic.
- 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-TRX mapping using the same algorithm than in B7.2 release. But afterwards an adjustment is performed for PS capable TRX (that is TRX with a TRX_PREF_MARK parameter equal to 0). PS capable TRX are mapped preferentially (from the highest to 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
If PS_Pref_BCCH_TRX = true, then the BCCH TRX is mapped on the TRE with the highest priority.
ED MND
04
- BCCH TRX if PS_Pref_BCCH_TRX = true - Then HW TRX capability: EGPRS High power, then EGPRS Medium power, then non EGPRS
-
- Then size of the PDCH group: rank first the TRX having the maximum number of consecutive SPDCH per TRX (this is a static information given by the O&M configuration of the TRX) - Finally TRX identity: among the remaining TRX, select first the TRX having the lowest TRX id
This 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 way for the CS traffic but this time from the lowest to the highest priority to avoid as much as possible collisions between the CS and PS traffics.
ED MND
04
Moreover, the 05.08 GSM recommendations also indicates the following possible problem for some fast moving MS linked to the use of frequency hopping on the BCCH carrier by EDGE TBF: In the case that 8-PSK modulation is allowed on the BCCH carrier and frequency hopping including BCCH carrier is used, the reception quality in connected mode for some fast moving MS (meaning MS experiencing Doppler frequencies of 100Hz or more) may be degraded. This may be seen as a backwards compatibility problem for some existing MS, most likely occurring if the used APD is larger than 2dB.
ED MND
04
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 test area selection for this trial presents as below.
ED MND
04
Test cell criteria: Create cell in BTS-Test at Arena site at 3-TRX configurations with BasebandHopping frequencies. Set 1TRX to support EGPRS service as well as GPRS service, and set all TRXs to support ordinary GSM service.
OMC-R for changing parameters and monitoring: USD-Cell overview and monitoring TRE-TRX mapping
ED MND
04
Week 508
16 17 18 19 20 21 22
Week 509
23 24 25 26 27 28 01
Week 510
02 03 04 05 06
Proposa l
Perform Testing
Remark: This trial time frame is flexibly changed; it depends on the B8 migration schedule. The following table shows detail of each test.
ED MND
04
Test Description
TRE Type
Service Mode
TRX Class
Iteration
Date
Remark
PART I EGPRS 01/3 EGPRS PART II EGPRS 02/3 EGPRS PART III EGPRS EGPRS 03/3 EGPRS EGPRS PART IV GPRS/ GSM EGPRS /GPRS EGPRS /GPRS EGPRS: FTP download 1000 KB GSM: Dedicate mode EGPRS: FTP download 1000 KB GPRS: FTP upload 500 KB EGPRS: FTP download 1000 KB GPRS: FTP download 500 KB TRAD 4 0 1 Observe allocated PDCH and TCH Observe throughput of each TBF Observe throughput of each TBF FTP: Download 1000 KB FTP: Upload 500 KB 10 10 TRAD TRAD 4 4 0 0 1 1 FTP: Download 1000 KB FTP: Upload 500 KB 10 10 TRAD TRAD 4 4 0 0 1 1 Observe throughput on BCCH-TRX Observe throughput on BCCH-TRX Observe throughput on non-BCCH-TRX Observe throughput on non-BCCH-TRX FTP: Download 1000 KB 10 TRADE 4 1 1 FTP: Download 1000 KB 10 TRAD 4 1 1 Observe throughput per PDCH Observe throughput per PDCH FTP: Upload 500 KB TRAD 4 1 1 FTP: Download 1000 KB TRAD 4 1 1 Observe BCCH recovery behavior Observe BCCH recovery behavior
04/3
TRAD
TRAD
Table1: Detail of each test schedule for EGPRS on BCCH-TRX Performance Proposal
ED MND
04
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 as following diagram.
FTP download 1000 KBytes TRX Class 4 (MAX_EGPRS) = MCS8) FTP upload 500 KBytes PS_PREF_BCCH_TRX = 1
ED MND
04
Description Enables/Disables EGPRS traffic in the cell. Maximum Modulation and Coding Scheme used for EGPRS traffic in the cell. Value of the downlink modulation and coding scheme when the link adaptation algorithm is disabled or initial value of the modulation and coding scheme otherwise. Value of the uplink modulation and coding scheme when the link adaptation algorithm is disabled or initial value of the modulation and coding scheme otherwise. Preference mark assigned to a given TRX. Indicates whether or not the PS requests shall be preferentially served with PDCH(s) of the BCCH TRX Maximum number of slave and master PDCHs that can be established in the cell.
TBF_DL_INIT_MCS
MCS8
TBF_UL_INIT_MCS
MCS4
TRX_PREF_MARK PS_PREF_BCCH_TRX
0 1
MAX_PDCH
TRE-TRX Mapping Relation This presents the results in term of TRE-TRX mapping relation, which were performed 3 iterations for 1.5Mbytes download (downlink bias) by external FTP server (www.airprice.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:
ED MND 04 EGPRS PERFORMANCE ON BCCH-TRX TRIAL Released Page 14/44
1st time:
Before BCCH-Recovery TRX1 TRX2 TRX3 TRE1 TRE3 TRE2 TRAD10 TRDM4 TRAD7 After BCCH-Recovery TRX1 TRX2 TRX3 TRE2 TRE3 TRAD7 TRDM4 Plug Disable TRE Back TRX1 TRX2 TRX3 TRE2 TRE3 TRE1 TRAD7 TRDM4 TRAD10
DISABLE
2nd time:
Before BCCH-Recovery TRX1 TRX2 TRX3 TRE2 TRE3 TRE1 TRAD7 TRDM4 TRAD10 After BCCH-Recovery TRX1 TRX2 TRX3 TRE1 TRE3 TRAD10 TRDM4 Plug Disable TRE Back TRX1 TRX2 TRX3 TRE1 TRE3 TRE2 TRAD10 TRDM4 TRAD7
DISABLE
3rd time:
Before BCCH-Recovery TRX1 TRX2 TRX3 TRE1 TRE3 TRE2 TRAD10 TRDM4 TRAD7 After BCCH-Recovery TRX1 TRX2 TRX3 TRE2 TRE3 TRAD7 TRDM4 Plug Disable TRE Back TRX1 TRX2 TRX3 TRE2 TRE3 TRE1 TRAD7 TRDM4 TRAD10
DISABLE
Location of allocated PDCH of EGPRS TBF This presents the results in term of location of allocated PDCH of EGPRS TBF by cell overview from OMC-R point of view thru BCCH-Recovery action. Result Locations of PDCHs were allocated on the supported TRE card G4, TRAD card, for both before and after BCCH-Recovery action. See details as below:
ED MND
04
2nd step: Location of allocated PDCH with EGPRS traffic, before BCCH-Recovery action
3rd step: Location of allocated PDCH during BCCH-Recovery mechanism (by disable Rx-Cable at the BTS test)
4th step: Location of allocated PDCH with EGPRS traffic, after BCCH-Recovery action was successful
ED MND
04
BCCH-Recovery Period This presents the result in term of period for BCCH-Recovery mechanism by stopwatch measuring (manually). Result In the BCCH-Recovery mechanism, the BTS test takes 5 minutes approximately in BCCH-Recovery mechanism since BCCH-TRX was disabled (by unplugging Rx-Cable) until this TRX was recovered successfully (already on-service).
No. 1 2 3 BCCH-Recovery Period (min) 5.04 5 4.58
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 suddenly dropped after the BCCH-TRX was disabled. During the BCCH-Recovery mechanism that takes 5 minutes approximately, the packet service (or even circuit service) requests were rejected. However, the EGPRS TBF can be established and working properly again after the BCCH was successfully recovered to another active TREs in the cell.
ED MND
04
Figure11: Test-BTS configuration for EGPRS performance on BCCH-TRX with different TRE types
ED MND
04
STEP 1, 3TRXs map on: 2 TRAD 1 TRDM TRX Class 4 (MAX_EGPRS) = MCS8) FTP download 1000 KBytes STEP 2, 3TRXs map on: 1 TRADE 1 TRAD 1 TRDM
Figure12: Test diagram for EGPRS performance on BCCH-TRX with different TRE types
TBF_DL_INIT_MCS
MCS8
TBF_UL_INIT_MCS
MCS4
TRX_PREF_MARK PS_PREF_BCCH_TRX
0 1
MAX_PDCH
Table5: Parameters setting for EGPRS performance on BCCH-TRX with different TRE types
ED MND
04
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
Remark: The maximum and minimum values from the test were excluded in the average values calculation RLC throughput (kbps) in term of MCS usage distribution is shown as the following graph:
ED MND
04
Distribution of MCS
50000 45000 40000 35000 30000 25000 20000 15000 10000 5000 0 MCS-1 MCS-2 MCS-3 MCS-3 (pad) MCS-4 MCS-5 MCS-6 MCS-6 (pad) MCS-7 MCS-8
Number
Nb
MCS
Additionally, BEP (Mean) value distribution usage is shown as the following graph:
BEP (Mean) Value Distribution
35000 30000 25000
Number
BEP (Mean)
From all results above, EGPRS performance, when allocated on BCCH-TRX by TRAD card, has an average data throughput equals to 38.88kbps per TS and transfer time 311.99 seconds. Most of EGPRS TBFs were used at MCS-8 coding scheme and have BEP (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 allocated PDCHs location, shown as following figure:
ED MND
04
TRE-TRX Mapping Relation 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 because of no recovery action on BCCH-TRX, shown as following figure:
ED MND
04
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 for data 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 data throughput, 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 from hardware degradation (TRADE card). Therefore, for this part, it cannot be compared or concluded EGPRS performance result on different TRE types.
ED MND
04
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.
BCC H SDC CH TRX1: TRX_PREF_MARK = 0 TRX2: TRX_PREF_MARK = 1 TRX3: TRX_PREF_MARK = 1
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.
BCC H SDC CH TRX1: TRX_PREF_MARK = 1 TRX2: TRX_PREF_MARK = 0 TRX3: TRX_PREF_MARK = 1
ED MND
04
TBF_DL_INIT_MCS
MCS8
TBF_UL_INIT_MCS
MCS4
TRX_PREF_MARK PS_PREF_BCCH_TRX
0,1 0
MAX_PDCH
ED MND
04
Data throughput (kbps) 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)in term of MCS distribution usage. Result Transfer time (sec) and data throughput in term of application throughput (kbps) are shown in the table below:
Download No. Data Throughput (kbps per TS) 1 2 3 4 5 6 7 8 9 10 Average 36.19 39.2 36.08 39.17 37.28 36.91 39.25 36.08 38.37 36.37 37.45 Transfer time (second) 110.61 102.12 110.88 102.16 107.31 108.42 101.93 110.9 104.28 110.04 106.98 Data Throughput (kbps per TS) 13.84 15.88 15.72 15.72 15.8 15.78 Transfer time (second) 433.53 377.7 381.64 382.03 379.56 380.23 Upload
Remark: the maximum value from the test was excluded in the average values calculation. RLC throughput (kbps) in term of MCS usage distribution for both download and upload are shown as the following graph:
Downlink - MCS Usage Distribution
18000 16000 14000
Number
12000 10000 8000 6000 4000 2000 0 MCS-1 MCS-2 MCS-3 MCS-3 MCS-4 MCS-5 MCS-6 MCS-6 MCS--7 MCS-8 (pad) (pad) MCS Number
ED MND
04
15000 10000 5000 0 MCS-1 MCS-2 MCS-3 MCS-3 MCS-4 MCS-5 MCS-6 (pad) MCS MCS-6 MCS--7 MCS-8 (pad) Number
Additionally, BEP (Mean) value distribution usage is shown as the following graph:
Downlink - BEP (Mean) Value Distribution
25000 20000
Number
From all results above, EGPRS performance at download direction, when allocated on BCCH-TRX by TRAD card, has an average data throughput equals to 37.45kbps per TS and transfer time 106.98 seconds. Most of EGPRS TBFs were used at MCS-8 coding scheme and have BEP (Mean) value at the best condition, 31-value.
ED MND
04
In addition, EGPRS performance at upload direction, when allocated on BCCH-TRX by TRAD card, has an average data throughput equals to 15.78kbps per TS and transfer time 380.23seconds. Most of EGPRS TBFs were used at MCS-4 coding scheme and have BEP (Mean) value at the best value 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 allocated PDCHs location at both download and upload direction, shown as following figure:
TRE-TRX Mapping Relation 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 because of no recovery action on BCCH-TRX, shown as following figure:
ED MND
04
Remark: The minimum value from the test was excluded in the average values calculation.
ED MND
04
RLC throughput (kbps) in term of MCS usage distribution for both download and upload are shown as the following graph:
Downlink - MCS Usage Distribution
18000 16000 14000
Number
12000 10000 8000 6000 4000 2000 0 MCS-1 MCS-2 MCS-3 MCS-3 MCS-4 MCS-5 MCS-6 MCS-6 MCS-7 MCS-8 (pad) (pad) MCS Number
25000 20000 15000 10000 5000 0 MCS-1 MCS-2 MCS-3 MCS-3 MCS-4 MCS-5 MCS-6 (pad) MCS MCS-6 MCS-7 MCS-8 (pad) Number
Additionally, BEP (Mean) value distribution usage is shown as the following graph:
Downlink - BEP (Mean) Value Distribution
25000 20000
Number
ED MND
04
From all results above, EGPRS performance at download direction, when allocated on non-BCCH-TRX by TRAD card, has an average data throughput equals to 39.03kbps per TS and transfer time 102.55 seconds. Most of EGPRS TBFs were used at MCS-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-BCCHTRX by TRAD card, has an average data throughput equals to 15.89kbps per TS and transfer time 378.14 seconds. Most of EGPRS TBFs were used at MCS-4 coding scheme and have BEP (Mean) value at the best value 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 allocated PDCHs location at both download and upload direction, shown as following figure.
ED MND
04
TRE-TRX Mapping Relation 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 because of no recovery action on BCCH-TRX, shown as following figure:
TRX1 TRX2 TRX3 TRE2 TRE1 TRE3
Figure33: TRE-TRX mapping relation
Summary from Section4.3 The results from this part, we can notice that EGPRS performance in term of data throughput and transfer time from TRAD card on non-BCCH-TRX are slightly better than TRAD card on BCCH-TRX around 4.11% and 3.74% for download and upload respectively. Actually, the data throughput on BCCH-TRX and non-BCCH-TRX should be similarity (It is under the same frequencies BBH, the same TRE card, the same allocated PDCHs & the same packet size), however, this might be impacted from the external FTP server (at www.air-price.com) that was selected to perform download and upload data for this trial. It is the uncontrollable factor. This might be the reason why the data throughput on non-BCCH-TRX was better than the result on BCCH-TRX.
ED MND
04
Parameter MAX_PDCH
Setting value 4
Description Maximum number of slave and master PDCHs that can be established in the cell.
Step2: Design 2TRXs mapping to 2 TRAD cards with PS_PREF_BCCH_TRX = 0, observe the coding scheme of GPRS TBF and EGPRS TBF, which sharing on same PDCH. Set parameter MAX_PDCH = 1 for forcing PS traffic sharing on same PDCH.
BCC H
SDC CH
TRX1: TRX_PREF_MARK = 1
TRX2: TRX_PREF_MARK = 0
Parameter MAX_PDCH
Setting value 1
Description Maximum number of slave and master PDCHs that can be established in the cell.
ED MND
04
TBF_DL_INIT_MCS
MCS8
TBF_UL_INIT_MCS
MCS4
TRX_PREF_MARK PS_PREF_BCCH_TRX
0 0
4.1.4 Test Result Step1: Resource sharing between EGPRS traffic & Circuit traffic
The following indicators are taken into account and considered during the test in this part: 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 Circuit traffic (GSM call) and Packet traffic (EGPRS) This presents the result in term of the location of allocated time slots that were shared for circuit traffic (GSM call) and packet traffic (EGPRS).
ED MND
04
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 the resource at only 3 time slots with circuit traffic on the same TRX due to one parameter setting: High_Traffic_Load_GPRS = 80%, this leads to limit the available time 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 TRAD card between before and after established EGPRS traffic that performed 5 iterations on this TRX.
RxLev Distribution
3000 2500 2000
Number
1500 1000 500 0 -55 -56 -57 -58 -59 -60 -61 -62 -63 -64 -65 -66 -67 -68 -69 -70 -71 -72 -73 -74 -75 RxLev (dBm ) Number
Figure39: RxLev (dBm) on BCCH-TRX without EGPRS traffic (only GMSK measurement)
ED MND
04
RxLev Distribution
3500 3000 2500
Number
2000 1500 1000 500 0 -55 -56 -57 -58 -59 -60 -61 -62 -63 -64 -65 -66 -67 -68 -69 -70 -71 -72 -73 -74 -75 RxLev (dBm ) Number
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 measured at the range of 59 to 61dBm, and RxLev on BCCH-TRX with EGPRS traffic can be measured at the range of 60 to 62dBm. This presents that the level of signal is fluctuating 2-3dBm comparing between with and without EGPRS traffic on the BCCH-TRX time slot.
Resource sharing between EGPRS and GPRS traffic This presents the result in term of the location of allocated time slots that were shared for EGPRS traffic in download direction and GPRS traffic in download direction.
Figure41: Location of allocated time slots for both EGPRS and GPRS traffic ED MND 04 EGPRS PERFORMANCE ON BCCH-TRX TRIAL Released Page 36/44
Summary: From the above result, EGPRS traffic and GPRS traffic can be well shared on the dame TRX at the same time slot (PDCH) Data throughput (kbps) and Transfer time 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 both EGPRS traffic in download and GPRS traffic in download. Result Transfer time (sec) and data throughput in term of application throughput (kbps) are shown in the table below:
EGPRS Traffic - Download No. Data Throughput (kbps per TS) 1 2 3 Average 18 17.6 14.88 15.88 Transfer time (second) 667.93 681.46 807.51 770.05 Data Throughput (kbps per TS) 11.6 11.76 10.08 10.88 Transfer time (second) 1033.73 1021.89 1192.32 1109.41 GPRS Traffic - Download
Coding scheme usage distribution for both EGPRS and GPRS traffic in download direction are shown as the following graph:
Downlink - MCS Usage Distribution
35000 30000 25000
Number
20000 15000 10000 5000 0 MCS-1 MCS-2 MCS-3 MCS-3 (pad) MCS-4 MCS-5 MCS-6 MCS-6 (pad) MCS-7 MCS-8
Number
MCS
Figure42: MCS usage distribution (RLC throughput) for EGPRS traffic at download direction
ED MND
04
50000 40000 30000 20000 10000 0 CS-1 CS-2 MCS CS-3 CS-4
Figure43: CS usage distribution (RLC throughput) for GPRS traffic at downlink direction
Summary: From the above results, EGPRS performance in this part has an average data throughput at 15.88kbps, transfer time at 770 seconds approximately, and the most penetrating of MCS usage distribution (or RLC throughput) was at MCS-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 at 10.88kbps, transfer time at 1109 seconds approximately, and the most penetrating of CS usage distribution (or RLC throughput_ was at CS-4. B. EGPRS Download Traffic & GPRS Upload Traffic The following indicators are taken into account and considered during the test in this part: Resource sharing between EGPRS traffic at download direction and GPRS traffic 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 shared for EGPRS traffic in download direction and GPRS traffic in upload direction.
ED MND
04
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 the same TRX at the same time slot (PDCH). Data throughput (kbps) and Transfer time 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 both EGPRS traffic in download and GPRS traffic in upload direction. Result Transfer time (sec) and data throughput in term of application throughput (kbps) are shown in the table below:
EGPRS Traffic - Download No. Data Throughput (kbps per TS) 1 2 3 Average 14.08 14.72 14.64 14.48 Transfer time (second) 852.83 815.41 818.41 828.88 Data Throughput (kbps per TS) 13.04 13.12 13.2 13.12 Transfer time (second) 919.7 914.59 907.63 913.97 GPRS Traffic - Upload
Coding scheme usage distribution for EGPRS traffic in download direction and GPRS traffic in upload direction are shown as the following graph:
ED MND
04
50000 40000 30000 20000 10000 0 MCS-1 MCS-2 MCS-3 MCS-3 (pad) MCS-4 MCS-5 MCS-6 MCS-6 (pad) MCS-7 MCS-8
Number
MCS
Figure45: MCS usage distribution (RLC throughput) for EGPRS traffic at download direction
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 data throughput at 14.48kbps, transfer time at 828 seconds approximately, and the most penetrating of MCS usage distribution (or RLC throughput) was at MCS-4. This is the limitation of coding scheme usage for EGPRS when it is allocating on the same time slot (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 the data. This situation impacts to any time slot (PDCH), which will be used for GPRS upload, to support in GMSK modulation for GPRS behavior. Therefore, this is indirectly impacted to EGPRS TBF, which is allocated in the same time slot (PDCH) with GPRS upload, has to use in GMSK modulation at MCS-4 maximum coding scheme for download any data.
ED MND
04
However, this problematic situation for EGPRS TBF especially for download can be relieved by enabling parameter reallocation triggered T4, which will handle the allocated PDCH for GPRS upload (the same PDCH for EGPRS TBF) to reallocate to another 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 at 13.12kbps, transfer time at 913.97 seconds, and the most penetrating of CS usage distribution (or RLC throughput) was at CS-4.
ED MND
04
The trial presented that BCCH recovery mechanism on BCCH-TRX was successful when BCCH-TRX was disabled. This mechanism took 5 minutes approximately. For EGPRS service point of view, the on-going EGPRS service on BCCH was suddenly dropped 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 data throughput, 311.99 seconds for transfer time, as well as most of TBFs were used at MCS-8 coding scheme and 31 value for BEP mean value. In addition, EGPRS performance 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 1921 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 this part, 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) on non-BCCH (TCH) were slightly better than on BCCH around 4.11% and 3.74% approx for download and upload respectively. PDCHs resource were well shared between EGPRS call and GSM call on the same timeslot, as well as between EGPRS call and download GPRS call. Except EGPRS call and upload GPRS call case, EGPRS call can adapt to maximum coding scheme at MCS-4, however, this situation can be relieved by enabling parameter reallocation triggered T4. From all results above, EGPRS can be implemented on either BCCH or non-BCCH (TCH), this depends on the objective and strategy. If EGPRS is deployed on BCCH, it will imply that clean frequencies are guaranteed and EGPRS service is ensured by BCCH recovery mechanism whenever BCCH got faulty. However, if EGPRS is deployed on TCH, it will benefit high utilization of capacity resource and avoid the limitation of EGPRS TBF handle on BCCH when the difference of maximum output power for 8-PSK and GMSK modulation is higher than 4dB (referred to 05.08 GSM recommendation).
ED MND
04
0: PS/CS TRX: This TRX can carry PS and CS traffic and has the lowest preference in the TCH sub-channel selection process 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 subchannel selection process used to serve a CS call.
MAX_EGPRS_MCS
Number
Cell
PS_PREF_BCCH_TRX
Flag
Cell
TBF_DL_INIT_MCS
Number
MCS1 to MCS9
Cell
TBF_UL_INIT_MCS
Number
MCS1 to MCS4
Cell
ED MND
04
END OF DOCUMENT
ED MND
04