Enhanced Support of EGPRS in UL Ed3

7/28/2019 Enhanced Support of EGPRS in UL Ed3

1/30

All rights reserved 2005, Alcatel

ENHANCED SUPPORT OF EGPRS IN UPLINK

August2005


2/30

All rights reserved 2005, AlcatelEnhanced support of EGPRS in Uplink / July2005

Page 2

ENHANCED SUPPORT of EGPRS IN UPLINKIntroduction

This feature is part of EGPRS package. It is divided intotwo sub features:

Support of 8-PSK in Uplink

The "8-PSK in UL" feature proposes to introduce the 8-PSK modulation in

UL, which permits to use the MCS-5 to MCS-9 coding schemes in the BSS(in B8 only the MCS-1 to MCS-4 are supported in UL).

Support of Incremental Redundancy in Uplink

The "Incremental Redundancy in UL" feature proposes to introduce theincremental redundancy in UL which permits to improve the decodingperformances of the BTS with EGPRS. This is particularly useful when

mobiles are at the border of the cells where a gain up to 15 % ofthroughput can be expected according to simulations.


3/30


Page 3


ENHANCED SUPPORT of EGPRS IN UPLINKContent



4/30


Page 4

ENHANCED SUPPORT of EGPRS IN UPLINK8-PSK in Uplink feature

The feature introduces 8-PSK modulation supported in UL.

Maximum data rate for difference coding scheme

The 8-PSK is a modulation technique that compare to GMSK allows up to3 times more data to be transmitted over the GSM air interface. The 8-

PSK supports MCS-5 to MCS-9 coding schemes, which permit to achievehigher throughput when the radio conditions are good enough.

Modulation Coding Scheme Throughput (kbits/sec)GMSK MCS-1 8.4GMSK MCS-2 11.2GMSK MCS-3 14.8GMSK MCS-4 17.68-PSK MCS-5 22.48-PSK MCS-6 29.68-PSK MCS-7 44.88-PSK MCS-8 54.48-PSK MCS-9 59.2


5/30


Page 5


Alternative training sequences decoding

If an EGPRS mobile station wants to initiate the UL EGPRS TBFestablishment and if the mobile supports the 8PSK in uplink, then it shallsend an EGPRS Packet Channel Request using TS1 alternative trainingsequences to request the resources in EGPRS mode.

The EGPRS capability is indicated using alternative training sequences(see 3GPP TS 45.002).

Training sequence Packet Channel Access

TS1 EGPRS with 8PSK capability in uplink

TS2 EGPRS without 8PSK capability in uplink


6/30


Page 6


The MCS-5 to MCS-9 coding schemes will be used in RLCacknowledged and unacknowledged mode.Support 8-PSK in RLC acknowledged & unacknowledged mode

The link adaptation mechanism in uplink is based on measurements(MEAN_BEP, CV_BEP) done by the BTS on the radio blocks received

from the mobile. To take into account MCS-5 to MCS-9 in uplink, the BSS algorithm for link

adaptation needs new link adaptation MEAN_BEP/CV_BEP tables, whichare the same as the ones already used for downlink.

The MCS selected by the BSS is indicated in the "EGPRS modulation andcoding" IE included in the PACKET UPLINK ACK/NACK message.

The TRX shall transmit the MEAN_BEP and CV_BEP of the RLC datablock which is received with a correctly decoded RLC/MAC header,whether the payload is correctly decoded or not. The TRX will discard theRLC/MAC blocks when the header has not been successfully decoded.


7/30All rights reserved 2005, AlcatelEnhanced support of EGPRS in Uplink / July2005

Page 7


MCS selected forretransmission block The retransmission of the RLC data blocks

that have not been correctly decoded, theBSS has the possibility to request theretransmission of these RLC data blocks

with or without re-segmentation. The"RESEGMENT" bit in the PACKETUPLINK ACK/NACK, PACKET UPLINKASSIGNMENT and PACKET TIMESLOTRECONFIGURE messages indicates if re-segmentation should be used or not.

When the type I ARQ is used, the"RESEGMENT" bit shall be set to "1". Forretransmission the mobile shall use an

MCS within the same family as the initialtransmission and the payload may be split.

The table indicates the MCS that shouldbe selected for retransmission accordingto the MCS, used for initial transmission.

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

MCS-9 MCS-9 MCS-6 MCS-6 MCS-6 MCS-3 MCS-3 MCS-3 MCS-3 MCS-3

MCS-8 MCS-8 MCS-8MCS-6 MCS-6 MCS-3 MCS-3 MCS-3 MCS-3 MCS-3








MCS commandedInitial

MCS

MFSTRXMS

RLC/MAC block B0 (PS1, MCS-6)

RLC/MAC block decoding.B0 payload not decoded, but

header of B0 correctly decoded.

Un-correct payload is sent to the

MFS with a Bad Frame indicator


RLC/MAC block decoding.B0 decoded

EGCH frame with B0 decoded(meanBEP, CV_BEP)

LA algorithmPACKET UL ACK/NACK

(MCS-4, RB=1, Ack/Nack bitmap: B0 not decoded)


8/30All rights reserved 2005, AlcatelEnhanced support of EGPRS in Uplink / July2005

Page 8


The LA tables considered depend on:

The APD (Average Power Decrease) of the mobile station

The APD of a mobile station is the difference between the maximum output powerin GMSK and the maximum output power in 8-PSK.

The maximum output powers are known by "GMSK Power Class" and "8-PSKPower Class" fields of the MS Radio Access capability IE.

Examples of APD in case of GSM 900 and GSM 850:

The IR is activated or not (EN_IR_UL flag).

8-PSK: Power Class E1

Max. output power = 33 dBm8-PSK: Power Class E2

Max. output power = 27 dBm8-PSK: Power Class E3

Max. output power = 23 dBmGMSK: Power Class 2

Max. output power = 39 dBm APD = 6 APD = 10 APD = 10GMSK: Power Class 3



Max. output power = 29 dBm APD = 0 APD = 2 APD = 6


9/30


Page 9


ENHANCED SUPPORT of EGPRS IN UPLINKContent



10/30


Page 10

ENHANCED SUPPORT of EGPRS IN UPLINKIncremental Redundancy in Uplink feature

The incremental redundancy (type II hybrid ARQ) is usedwith EGPRS data blocks sent on RLC acknowledgedmode using MCS-1 to MCS-9.


The incremental redundancy is based on reception of RLC data blockscoded with different puncturing schemes, so that the BTS may enhancethe decoding of the RLC data block with soft combining. By taking intoaccount the erroneous RLC data blocks and combining them with theretransmitted RLC data blocks, the BTS receiver increases the probabilityof decoding them correctly and reduces the number of times it uses aslower coding scheme compared to the situation where incremental

redundancy is not used and therefore the average throughput isincreased.

Interaction with re-segmentation on UL

As for DL, incremental redundancy cannot be applied when the RLCdatablocks are re-segmented with a different number of payloads.


11/30


Page 11


Puncturing scheme used for RLC data blocks retransmitted in newMCS.

When a RLC data block shall be retransmitted using another MCS of thesame family, the first puncturing scheme to be used by the mobile after theMCS switch is given by the following table.

MCS Switched PS of last transmissionbefore MCS switched PS of first transmissionafter MCS switchedFrom To

MCS9 MCS6 PS1 or PS3 PS1PS2 PS2

MCS6

MCS9 PS1 PS3

PS2 PS2MCS7 MCS5 any PS1MCS5 MCS7 any PS2

All other combinations any PS1


12/30


Page 12


IR is configured in the MFS by parameter EN_IR_UL.

When EN_IR_UL = Enable, the MFS shall:

Use incremental redundancy with all MSs.

Give the [TFI, RTS] combinations, used by TBF, to the TRX.

Remark: The Incremental Redundancy for the uplink TBF feature issupported only on G4 BTSs.

When EN_RESEGMENTATION_UL = Enable, the MFS shall:

Set 1 (re-segmentation) to RESEGMENT bit in the PACKET UPLINKACK/NACK, PACKET UPLINK ASSIGNMENT and PACKET TIMESLOTRECONFIGURE messages.


13/30


Page 13


To implement the IR with EGPRS, the TRX shall be able to retrievethe RLC data blocks pertaining to the same TBF, received on one orseveral PDCHs.

The TRX needs to decode the RLC/MAC header of all UL RLC/MAC datablocks received on each PDCHs to know which TBF the RLC data block(s)

pertain. The TFI in the RLC/MAC header and the time slot number permit to

identify the TBF.

The BSN in the RLC/MAC header permits to identify a specific RLC datablock.

For each TBF, the maximum number of different RLC data blocks stored,

is equal to the window size which depends on the maximum number ofRTS used in uplink (512 for 4 TS).


14/30


Page 14


Data organization in the TRX

3 Data structures are defined to describe the management of the RLCdata block with incremental redundancy:

1. TBF list

Indexed by TFI (maximum number of possible TFI is 32) and RTS

(maximum number of possible radio time slot is 8).2. BSN list

A TRX has 56 BSNs list, one list per TBF. 56 UL TBFs can be allocatedsimultaneously on one TRX.

3. SB buffer

The buffer can store the soft bits up to 4000 RLC data blocks.


15/30


Page 15


TBF list0 < TFI < 31 RTS Address of the context

0 0 0 0 0 0 0 0 @BSN list for TBF indexed by (TFI0, RTS0) or NULL0 0 0 0 0 0 0 1 @BSN list for TBF indexed by (TFI0, RTS1) or NULL0 0 0 0 0 0 1 0 @BSN list for TBF indexed by (TFI0, RTS2) or NULL0 0 0 0 0 0 1 1 @BSN list for TBF indexed by (TFI0, RTS3) or NULL0 0 0 0 0 1 0 0 @BSN list for TBF indexed by (TFI0, RTS4) or NULL0 0 0 0 0 1 0 1 @BSN list for TBF indexed by (TFI0, RTS5) or NULL0 0 0 0 0 1 1 0 @BSN list for TBF indexed by (TFI

0

, RTS6

) or NULL0 0 0 0 0 1 1 1 @BSN list for TBF indexed by (TFI0, RTS7) or NULL0 0 0 0 0 0 0 0 @BSN list for TBF indexed by (TFI1, RTS0) or NULL

1 1 1 1 1 1 1 0 @BSN list for TBF indexed by (TFI31, RTS6) or NULL1 1 1 1 1 1 1 1 @BSN list for TBF indexed by (TFI31, RTS7) or NULL

BSN list for TBF n (0 < n < 55) BSN PS1 PS2 PS3

0 @RLC data block orNULL MCS number @RLC data block orNULL MCS number @RLC data block orNULL MCS number

1 @RLC data block orNULL MCS number @RLC data block orNULL MCS number @RLC data block orNULL MCS number

511 @RLC data block or

NULL MCS number @RLC data block orNULL MCS number @RLC data block orNULL MCS number

SB buffer(Soft bits buffer)Soft bits of not decoded RLC data blocks

0 Soft bits of RLC data block (TBFx0, BSNy0)1 Soft bits of RLC data block (TBFx1, BSNy1)

3999 Soft bits of RLC data block (TBFx3999, BSNy3999)4000 Soft bits of RLC data block (TBFx4000, BSNy4000)

This table permits to retrieve

the TBF context associated to[TFI, RTS]

Each time a RLC data block is

not decoded, the soft bits are

stored in the current position andthe pointer is incremented.


16/30


Page 16


TBF list

A TBF listis a two dimension [TFI, RTS] table indexed by TFI and RTS. The TFIindex size is the number of the possible TFIs, 32. The RTS index size is the numberof the possible radio time slots, 8. A [TFI, RTS] index contains a pointer, point to theBSN listused by the TBF. A [TFI, RTS] index, which is not used, is marked as "NOTUSED", NULL.

BSN listA BSN listis a two dimension [BSN, PS] table indexed by BSN and PS. The BSNindex size is the number of the possible BSNs, 512. The PS index size is themaximum number puncturing schemes, 3.

A [BSN, PS] index contains information concerning the soft bits of RLC data block,received with the values of BSN and PS if RLC data block has not been correctlydecoded. A [BSN, PS] index contains a pointer, point to the buffer where the softbits of the corresponding RLC data block are stored. A [BSN, PS] index which is not

used is marked as "NOT USED", NULL. SB buffer

The SB buffercontains the soft bits of the RLC data blocks which have not beencorrectly decoded. This buffer has the capacity to store the soft bits of up to 4000RLC data blocks.


17/30


Page 17


Storage of RLC data blocks in the SB buffer

Each time a RLC data block is received by a TRX, and the payload cannotbe decoded (but the header has been correctly decoded to get the TFI andthe BSN), the soft bits of this RLC data block shall be stored in the SBbuffer in the position indicated by the pointer and the pointer is

incremented.At the same time the [BSN, PS] list is updated to indicate the address

where the soft bits of the RLC data block are stored in the SB buffer.


18/30


Page 18


Management of incremental redundancy in UL at the TRX

When the TFI, the BSN and the CPS (gives the PS value) fields, included in theheader of a RLC data block received on a given RTS, have been decoded but thepayload of the RLC data block cannot be decoded. The TRX will check:

ifone or more RLC data blocks are stored for the three possible [BSN, PSx]combinations in the BSN list.

Then the soft bits of the received RLC data blocks are combined with the soft bitsof the stored RLC data blocks. Ifafter the combination, the CRC of the payload of the RLC data block is valid,

then the RLC data block is sent to the MFS and the pointers in the [BSN, PSx]combinations in the BSN list are set to NULL.

Ifafter the combination, the CRC of the payload of the RLC data block is stillinvalid, then:

1. The soft bits of the RLC data block are stored in the circular buffer

2. The pointer in the [BSN, PS] combination in the BSN list is updated, point to

the address where the soft bits of the RLC data block are stored.3. If the soft bits of another instance of the same RLC data block received with

the same puncturing scheme was already present in the BSN list, only the lastinstance is taken into account.


19/30


Page 19


Management of incremental redundancy in UL at the MFS

The MFS is in charge of opening and closing the UL TBFs contexts in the TRX.The active TBFs context on a TRX are numbered from 0 to 55.

The MFS have a TBF table with 56 entries. The index of the table is associatedwith the TBF number. The index which are not used are marked as FREE and theindex which are used for a TBF contains the parameters [TFI, RTSs] of the TBF.

When a UL TBF is allocated, the MFS selects an index marked as FREE in theTBF table. The value of the index is the TBF number that should be provided tothe TRX.

When a UL TBF is de-allocated the MFS marks the corresponding index of theTBF table as FREE.

TBF table0 [TFI, RTSs] or FREE1 [TFI, RTSs] or FREE 54 [TFI, RTSs] or FREE55 [TFI, RTSs] or FREE


20/30


Page 20


Opening an UL TBF context in a TRX

MFS shall open TBF context in a TRX for every TBFs managed by the TRX.

MFS send TBF_OPEN_REQUEST message to the TRX, containing TBF number, TFI, list ofRTS number, IR used (or not), cause of TBF opening (configuration or re-configuration), RLCmode (ACK/NACK), TBF priority (needed for QoS feature).

The TRX fills the TBF list, [TFI, RTS] indexes with the address of BSN list associated to TBF.

TRX acknowledge TBF_OPEN_REQUEST message with TBF_OPEN_CONFIRM message toMFS.

At that time, the MFSmay schedule USF

If the TBF_OPEN_CONFIRM message is not

received when the timer T_CONFIG_TBF elapses,

the MFS shall repeat sending the

TBF_OPEN_REQUEST message. Timer

T_CONFIG_TBF shall be stopped when theTBF_OPEN_CONFIRM message is received.

MFSTRXMS

TBF_OPEN_CONFIRM

(TBF nb, report)

TBF_OPEN_REQUEST

(TBF nb, TFI, TS bitmap, config, )

PACKET_UPLINK_ASSIGNMENT

The TRX links the [TFI, TSs]used by the concerned TBF

T_CONFIG_TBF


21/30


Page 21


Closing an UL TBF context in a TRX

To close a TBF context, MFS sends a TBF_ CLOSE_REQUEST message containing the TBFnumber.

TRX fills the TBF list, concerned [TFI, RTS] index with a NULL pointer.

The TRX shall acknowledge the TBF_CLOSE_REQUEST message received byTBF_CLOSE_CONFIRM message.

At that time, the MFS may

release the resources it uses

for the TBF

MFSTRXMS

TBF_CLOSE_CONFIRM

(TBF nb, report)

TBF_CLOSE_REQUEST

(TBF nb)

The TRX links the [TFI, TSs]used by the concerned TBF

MFS release the UL TBF


22/30


Page 22


The MS sends a RLC/MAC block B1with puncturing scheme PS1.

The TRX cannot decode the RLC/MACblock B1. The TRX stores B1 soft bits.

The TRX sends the RLC data block B1that has been wrongly decoded in anM-EGCH frame.

The MFS sends a PACKET UPLINKACK/NACK message containing theMCS to be used by the MS (MCS 3),the ACK/NACK bitmap and theRESEGMENT bit set to "0".

The MS sends a RLC/MAC block B1,coded with MCS-6 (not 2 RLC/MACblock coded with MCS-3) withpuncturing scheme PS2.

The TRX decodes the RLC/MAC blockB1, using the soft bits of B1 previouslystored.

The TRX sends the RLC data block B1that has been correctly decoded.

MFSTRXMS


RLC/MAC block decoding.B0 decoded.

EGCH frame with B0 decoded(meanBEP, CV_BEP)


RLC/MAC block decoding.B1 not decoded, but

header of B1 decoded.Storage of B1 soft bits

EGCH frame with B1 not decoded(meanBEP, CV_BEP)

LA algorithm


PACKET UL ACK/NACK(MCS-3, RB=0, Ack/Nack bitmap: B1 not decoded)

RLC/MAC block decoding.B1 header decoded. Softcombining with previous

transmission

EGCH frame with B1(meanBEP, CV_BEP)

Retransmission of a RLC/MAC block with the same MCS


23/30


Page 23


TRX cannot decode the RLC/MACblock containing the two RLC datablocks B0 and B1. The TRX stores thecorresponding soft bits, then sends thetwo RLC data blocks B0 and B1,wrongly decoded in an M-EGCH frame

The MFS sends a PACKET UPLINK

ACK/NACK message containing theMCS to be used by the MS (MCS-8),the ACK/NACK bitmap and theRESEGMENT bit set to "0".

MS retransmits the RLC/MAC blockcontaining the RLC data blocks B0 withthe MCS-6 and PS1.

TRX decoding, and sends the RLC datablock B0 correctly decoded in an M-

EGCH frame. The MS retransmits the RLC/MAC

block containing the RLC data blocksB1 with the MCS-6 and PS1. TRXdecoding, and sends the RLC datablock B1 correctly decoded in an M-EGCH frame.

Retransmission of a RLC/MAC block with the MCS of the same family

MFSTRXMS

RLC/MAC block B0&B1(PS1, MCS-9)

RLC/MAC header decoded. Payload not decoded.Storage of B0&B1 soft bits

EGCH frame with B0&B1 not decoded(meanBEP, CV_BEP)

LA algorithm


PACKET UL ACK/NACK (MCS-8, RB=0, Ack/Nack bitmap)

RLC/MAC header decoded. Payload not decoded.Soft combining with previous transmission

EGCH frame with B0

(meanBEP, CV_BEP)


RLC/MAC header decoded. Payload not decoded.Soft combining with previous transmission

EGCH frame with B1(meanBEP, CV_BEP)


24/30


Page 24

ENHANCED SUPPORT of EGPRS IN UPLINKOMC-R parameters

HMI name Definition Sub-system

Instance

OMC-Raccess

Type Defvalue

Range Unit

EN_IR_UL Enables/DisablesIncrementalredundancy for theuplink TBF in the BSS.

MFS BSS Changeable Flag 0 [0,1] None

EN_RESEGMENTATION_UL Enables/Disables there-segmentation forthe uplink TBF in theBSS

MFS BSS Changeable Flag 0 [0,1] None

TBF_UL_INIT_MCS Value of the uplinkmodulation and codingscheme when the linkadaptation algorithm isdisabled or initial valueof the modulation and

coding schemeotherwise.

MFS Cell Changeable Number 3 [1,9] None

T_CONFIG_TBF Supervision timer forTBF contextconfiguration in a TRX

MFS MFS None (DLS) Timer 280 [200,400]

ms


25/30


Page 25

ENHANCED SUPPORT of EGPRS IN UPLINKMFS counters

Counternumber Name Definition

P21e NB_UL_RLC_BYTES_PDTCH_RETRANS_MCS In acknowledged mode, number of UL RLC data bytes received on PDTCHencoded in MCS-x (with x = 1 to 9) retransmitted due to un-acknowledgement of the MFS.

P57e NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1 Number of useful UL RLC blocks received in RLC acknowledged mode onPDTCH encoded in MCS-1.

P57f NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2 Number of useful UL RLC blocks received in RLC acknowledged mode onPDTCH encoded in MCS-2.

P57g NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS3 Number of useful UL RLC blocks received in RLC acknowledged mode onPDTCH encoded in MCS-3.

P57h NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4 Number of useful UL RLC blocks received in RLC acknowledged mode onPDTCH encoded in MCS-4.

P57i NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS5 Number of useful UL RLC blocks received in RLC acknowledged mode onPDTCH encoded in MCS-5.

P57j NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6 Number of useful UL RLC blocks received in RLC acknowledged mode onPDTCH encoded in MCS-6.

P57k NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS7 Number of useful UL RLC blocks received in RLC acknowledged mode on

PDTCH encoded in MCS-7.P57l NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8 Number of useful UL RLC blocks received in RLC acknowledged mode on

PDTCH encoded in MCS-8.

P57m NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS9 Number of useful UL RLC blocks received in RLC acknowledged mode onPDTCH encoded in MCS-9.

P73d NB_UL_RLC_BYTES_PDTCH_LOST_MCS In unacknowledged mode, number of UL RLC data bytes on PDTCHencoded in MCS-x (with x = 1 to 9) lost.


26/30


Page 26

ENHANCED SUPPORT of EGPRS IN UPLINKNPA indicators (1/2)

Ref. name Name Formula Unit TableName

TRPDUM5N USEFUL_THROUGHPUT_UL_MCS5_NUMBER

P57i number GPTRLA


P57j number GPTRLA

TRPDUM7N USEFUL_THROUGHPUT_UL_MCS7_N

UMBER

P57k number GPTRLA


P57l number GPTRLA


P57m number GPTRLA

TRPDUC8N USEFUL_THROUGHPUT_UL_8PSK_NUMBER

P57i + P57j + P57k + P57l +P57m

number GPTRLA

TRPDUUSN USEFUL_THROUGHPUT_UL_NUMBER P57a + P57b + P57c + P57d +rnz (P57i + P57j + P57k +

P57l +P57m,1)

number GPTRLA


27/30


Page 27

ENHANCED SUPPORT of EGPRS IN UPLINKNPA indicators (2/2)

Ref. name Name Formula Unit TableName

TRPDUBYN UL_RLC_BYTES_transmitted_NUMBER

P57a*20+P57b*30+P57c*36+P57d*50+P57e*22+P57f*28+P57g*37+P57h*44+P57i*56+P57j*74+P57k*56+P57l *68+ P57m*74

number GPTRLA

TRPDUTBA USEFUL_THROUGHPUT_PER_TBF_UL_RADIO_AVERAGE

tdiv(P57a*160+P57b*240+(P57c*288)+(P57d*400)+(P57e*176+P57f*224+P57g*296+P57h*352)+RNZ(P

57i*448+P57j*592+P57k*448+P57l*544+P57m*592,0),((RNZ(P129c,1)+RNZ(p129a,1)))*1000,0,1)

kbps GPTRLA

ARUTBACEAT TIME_UL_TBF_ACTIVE_CONNECT_EGPRS_ACK_OCCUPANCY

P129c seconds GPTRLA

ARUTBACENT TIME_UL_TBF_ACTIVE_CONNECT_EGPRS_NACK_OCCUPANCY

P129d seconds GPTRLA

ARUTBACGAT TIME_UL_TBF_ACTIVE_CONNECT_GPRS_ACK_OCCUPANCY

P129a seconds GPTRLA

ARUTBACGNT TIME_UL_TBF_ACTIVE_CONNECT_GPRS_NACK_OCCUPANCY

P129b seconds GPTRLA

QRPDULMN UL_RLC_BYTES_PDTCH_MCS_LOST_NUMBER

P73d number GPQOS1

QRPDURMN UL_RLC_BYTES_PDTCH_MCS_RETRANS_NUMBER

P21e number GPQOS1


28/30


Page 28

ENHANCED SUPPORT of EGPRS IN UPLINKRNO indicators (1/2)

Ref. name Name Formula Unit

TRPDUM5N GPRS_UL_useful_throughput_MCS5_ack P57i Number

TRPDUM5O GPRS_UL_useful_throughput_MCS5_ack_ratio Ref. to 8PSK ratio %

TRPDUM6N GPRS_UL_useful_throughput_MCS6_ack P57j Number


TRPDUM7N GPRS_UL_useful_throughput_MCS7_ack P57k Number

TRPDUM7O GPRS_UL_useful_throughput_MCS7_ack_ratio Ref. to 8PSK ratio %TRPDUM8N GPRS_UL_useful_throughput_MCS8_ack P57l Number


TRPDUM9N GPRS_UL_useful_throughput_MCS9_ack P57m Number


TRPDUC8N GPRS_UL_useful_throughput_MCSx_8PSK_ack

P57i + P57j + P57k + P57l +P57m

Number

TRPDUC8O GPRS_UL_useful_throughput_MCSx_8PSK_ack_ratio GPRS_UL_useful_throughput_MCSx_8PSK_ack /GPRS_UL_useful_throughput_M

CSx_ack

%

TRPDUUSN

TRPDUMN

GPRS_UL_useful_throughput_ack

GPRS_UL_useful_throughput_MCSx_ack

UPDATED with :

+P57i+P57j+P57k+P57l+P57m

Number

ENHANCED SUPPORT f EGPRS IN UPLINK


29/30


Page 29

ENHANCED SUPPORT of EGPRS IN UPLINKRNO indicators (2/2)

Ref. name Name Formula Unit

TRPDUBYN

TRPDUBIN

GPRS_UL_useful_throughput_bytes_ack

GPRS_UL_useful_throughput_bits_ack

..+P57i*56+P57j*74+P57k*56+P57l *68+ P57m*74

..+P57i*448+P57j*592+P57k*448+P57l *544+P57m*592

number

TRPDUTBA GPRS_UL_useful_throughput_radio_TBF_avg

GPRS_UL_useful_throughput_bits_ack /((GPRS_UL_active_connection_GPRS_ack_time +GPRS_UL_active_connection_EGPRS_ack_time)*100

0)

kbps

TRPDUTBEGA

GPRS_UL_useful_throughput_radio_EGPRS_TBF_avg

GPRS_UL_useful_throughput_MCSx_bits_ack /(GPRS_UL_active_connection_EGPRS_ack_time*1000)

kbps

TRPDUTBGPA

GPRS_UL_useful_throughput_radio_GPRS_TBF_avg

GPRS_UL_useful_throughput_CSx_bits_ack / (GPRS_UL_active_connection_GPRS_ack_time*1000)

kbps

TRPDUPDA GPRS_UL_useful_throughput_radio_PDCH_avg

GPRS_UL_useful_throughput_bits_ack /(GPRS_PDCH_UL_traffic_time * 1000)

kbps

TRPDUCLA GPRS_UL_useful_throughput_radio_cell_avg

( GPRS_UL_useful_throughput_bits_ack) /(GPRS_obs_period * 1000)

kbps

QRPDURMN

GPRS_UL_RLC_bytes_PDTCH_MCSx_retransmissing_ack

P21e number

QRPDURMO

GPRS_UL_RLC_bytes_PDTCH_MCSx_retrans_ack_ratio

GPRS_UL_RLC_bytes_PDTCH_MCSx_retransmissing_ac

k /

(GPRS_UL_RLC_bytes_PDTCH_MCSx_retransmissing

_ack+GPRS_UL_useful_throughput_MCSx_bytes_ack

%

Date post:	03-Apr-2018
Category:	Documents
Upload:	phuong-le
View:	219 times
Download:	0 times

Enhanced Support of EGPRS in UL Ed3

Documents