Sie sind auf Seite 1von 9

Filter >> High PDCH Cong >> Continuous >> TBF Sharing

AFP > A FLP ??

OSRTHRESH

3.4   Handling of Packet Data Traffic

3.4.1   General

When resources are needed for PS connections, PDCHs are reserved for those TBFs. PDCHs
are reserved in accordance with the MS type (GPRS/EGPRS/EGPRS2-A), MS feature
capability (for example Reduced Latency) and the multislot class. If the feature Multiband
cell is used also the frequency band capabilities of the MS may be considered. See
Reference [10]. If the frequency band capabilities is not known then the reservation will
follow the parameter MBCRAC.Only one PDCH will be reserved for pure GMM/SM signaling
use.

Each PDCH can carry traffic for more than one connection at a time, both uplink and
downlink. The following limits are applicable:

 32 TFIs per PSET and direction (UL/DL),


 7 USFs per PDCH on uplink.

The optional feature Expanded PDCH Address Space (EPAS) doubles this capacity using
two different Training Sequence Codes (TSC). Thus the maximum number of
simultaneous users can be doubled.

A PDCH may be used as essential channel for a maximum of 16 TBFs. This limit is however
not valid when the optional feature Expanded PDCH Address Space (EPAS) is activated. The
TBF limits described in Section 3.4.9 do not limit the number of allowed TBFs per PDCH
further.

3.7.3.4   EPAS

When Expanded PDCH Address Space (EPAS) is activated in a cell, Automatic FLP and
Automatic IRC tuning adapts the TSC plan for all CHGRs in that cell. A specific TSC plan is
needed for EPAS because two different TSCs are used in a EPAS pair.

Expanded PDCH Address Space


The feature Expanded PDCH Address Space (EPAS) allows to use two Training Sequence
Codes (TSC) in a channel group thus doubling the capacity of the available PDCHs in the
congested cell.
The feature can be activated in a certain cell but it is triggered when the PS traffic in the cell
is very high, with other words when all TFIs and/or USFs for the primary TSC are allocated
or blocked. Then new requests will be reserved on the same PDCH but with the secondary
TSC. If the feature is not activated in the cell, the STS counters PREJTFI, LDISTFI,
PREJPDCH and LDISPDCH will be incremented (see Section 2.18). The feature does not
increase the GPH CPU load unreasonably: carrying more PS traffic will naturally result in a
higher CPU load.

3.4   Handling of Packet Data Traffic

3.4.1   General

When resources are needed for PS connections, PDCHs are reserved for those TBFs. PDCHs
are reserved in accordance with the MS type (GPRS/EGPRS/EGPRS2-A), MS feature
capability (for example Reduced Latency) and the multislot class. If the feature Multiband
cell is used also the frequency band capabilities of the MS may be considered. See
Reference [10]. If the frequency band capabilities is not known then the reservation will
follow the parameter MBCRAC. Only one PDCH will be reserved for pure GMM/SM signaling
use.

Each PDCH can carry traffic for more than one connection at a time, both uplink and
downlink. The following limits are applicable:

 32 TFIs per PSET and direction (UL/DL),


 7 USFs per PDCH on uplink.

The optional feature Expanded PDCH Address Space (EPAS) doubles this capacity using two
different Training Sequence Codes (TSC). Thus the maximum number of simultaneous users
can be doubled.

A PDCH may be used as essential channel for a maximum of 16 TBFs. This limit is however
not valid when the optional feature Expanded PDCH Address Space (EPAS) is activated. The
TBF limits described in Section 3.4.9 do not limit the number of allowed TBFs per PDCH
further.

At channel request for a PS user, channels in one PSET are selected where the TBF
reservation will be made . If the MS already has PDCHs reserved for a TBF in the opposite
direction, the new reservation is made on the same PSET in accordance with the MS
multislot class (which does not always mean that channels are reserved on the maximum
number of PDCHs according to the multislot class). Also the QoS requirements (if QoS is
activated) and the level of priority EGPRS and EGPRS2-A shall have over GPRS (if EGPRS
Prioritized Over GPRS is activated) are taken into consideration.

If the optional feature Packet Data Efficiency is activated in the cell and cell parameter
OSRTHRESH is set to a positive value, the MS will get reserved on a single PDCH until the
downlink or uplink RLC buffer level in the PCU exceeds the value of OSRTHRESH. When the
threshold is exceeded the MS will be eligible for TBF reservation based on its full multislot
class and available PDCHs.
The TBF reservations are then continuously supervised and any TBF may be upgraded
(added PDCHs without removing the existing ones) or re-reserved (moved to other PDCHs
in the cell) in order to fulfil the QoS requirements and/or the MS multislot class. When a TBF
is re-reserved the concurrent TBF (in the opposite direction), if any, will also be moved.
Furthermore it is continuously checked whether the balance for DL and UL TBFs should be
changed for MSs with TBFs in both directions. A TBF can also be re-reserved to even out the
PDCH load in a cell. The procedures used to perform these changes are described in
Reference [6].

The TTI configuration, BTTI or RTTI, for MSs capable of 3GPP release 7 feature Reduced
Latency (if parameter RTTI is set and the TBF is reserved on RI-PDCHs or E2A-PDCHs) can
be changed to suit the current packet transfer situation.

Note that the TBF reservation only decides which PDCHs that are possible to use for the
transfer. If a PDCH is shared between different MSs then it is the scheduling functionality
that decides how much of the PDCH capacity that may be used for each MS, see Reference
[6] and Reference [7].

[6] User Description, GPRS/EGPRS Connection Control and Transfer, (User


Description)
[7] User Description, GPRS/EGPRS Quality of Service, (User Description)

If it is not possible to reserve any PDCH for the new uplink TBF on the PDCHs where the downlink TBF is
placed and the Expanded PDCH Address Space (EPAS) feature is active, a simultaneous re-reservation of
the existing downlink TBF and set up of the uplink TBF can be performed. The scheduling is then
temporarily stopped for the downlink TBF. The 44.060 PACKET TIMESLOT RECONFIGURE message is sent
to the MS on PACCH. The scheduling is then resumed for the downlink TBF and started for the uplink
TBF. The first RLC Data Block is sent to the MS with a request for a 44.060 PACKET DOWNLINK
ACK/NACK message. If the 44.060 PACKET DOWNLINK ACK/NACK message is received, the TBFs are
considered to be established. If the 44.060 PACKET DOWNLINK ACK/NACK message is not received,
another two attempts to send the 44.060 PACKET TIMESLOT RECONFIGURE message are performed
before the procedure is considered unsuccessful and both TBFs are terminated.

3.2.8   TBF Setup on Additional TSC

With the optional feature Expanded PDCH Address Space (EPAS) activated two Training
Sequence Codes (TSCs) can be used on a PDCH, the default one and an additional one.

As soon as the amount of available USFs, UL TFIs and/or DL TFIs in the PSET becomes too
low, two separate TSCs are then used in the PSET. Each TBF that is set up is assigned a
TSC. When using two separate TSCs in the PSET, another TBF can then be assigned the
same TFI and/or USF value on the same PDCH, but with the other TSC. The amount of
possible TBFs to be reserved on a PDCH is thus doubled.
When sufficient USFs, UL TFIs and DL TFIs are available in the PSET again, all new TBF
reservations will be done using just one TSC, the default one. DTM TBFs are always
assigned the default TSC, which is the same as is used for the CS part.

EPASSTATE

4.3.8.3   Expanded PDCH Address Space

The feature Expanded PDCH Address Space (EPAS) allows more TBFs to be allocated on the
same PDCHs by increasing the number of available TFIs and USFs. The network then
schedules two MSs on the same PDCH using the same TFI and/or USF, separating them by
using different Training Sequence Code (TSC). When a downlink block is sent to an MS the
TSC, which was assigned to it during the assignment procedure, is used. Only the MSs that
are assigned that specific TSC can then decode the block. An MS with the same TFI and/or
USF but another TSC is not able to decode the block.

4.3.12   Timing Advance Handling

The Continuous Timing Advance (CTA) procedure is used for update of timing advance
values. The MS then gets updates of its timing advance values via the Packet Timing
Advance Control Channel (PTCCH). If the Expanded PDCH Address Space (EPAS) feature is
activated, the Continuous Timing Advance procedure is not used. The PTCCH is then
deactivated and updated timing advance values are instead sent to the MS in 44.060
PACKET POWER CONTROL/TIMING ADVANCE messages.
5.6   Expanded PDCH Address Space

Table 13     Impact and dependency quick chart


Impacts Implementation Operations Characteristics Interface Compatibility
    X X X  
 
Dependencies BSC BTS STN OSS Other Network Elements Other
Dependencies
  X X   X X  

5.6.1   Description

This new feature makes it possible to double the amount of simultaneous data flows for
Packet Services in GSM RAN. Prior upgrade to GSM RAN G15B the system limits were:

 Maximum 32 Temporary Flow Identities (TFIs) per PDCH Set (PSET) and
direction
 Maximum 7 Uplink State Flags (USFs) per PDCH on uplink

Previously only one Training Sequence Code (TSC) have been used but in GSM RAN G15B
one additional TSC per channel group has been added. By this two Temporary Block Flows
(TBFs) can share the same PDCH and use the same TFI and USF as long as they use
different TSCs. When sending downlink data to an MS it is sent using its specific TSC. This
way only the intended MS is able to decode the data. The MS with the same TFI and USF
but another TSC cannot decode the data.

5.6.2   Operations

5.6.2.1   Commands and Printouts

Commands:

 RLEPI: Radio Control Cell, Expanded PDCH Address Space, Initiate


RLEPE: Radio Control Cell, Expanded PCDH Address Space, End
RLEPP: Radio Control Cell, Expanded PDCH Address Space, Print
New commands introduced by this feature. They are used to activate (RLEPI)
and deactivate (RLEPP) support for EPAS in a cell. RLEPP prints EPAS data for
specified internal cells.

Printouts:

 CELL EXPANDED PDCH ADDRESS SPACE DATA (Command RLEPP)

5.6.2.2   STS Counters

The following new counters have been added for Expanded PDCH Address Space:
 Six new counters in the new Object Type CLGPRSTSC

More information can be found in Section 7.1 .

5.6.3   Characteristics

This feature doubles the maximum number of simultaneous PS users per channel. Expanded
PDCH Address Space also improves PS accessibility KPI since there will be fewer TFI
rejections in the network.

Small changes in the GPH throughput and load may occur depending on the traffic mix and
the configuration of the packet channels in the cells.

If the optional feature Packet Data Efficiency is activated in the cell and cell parameter OSRTHRESH is set
to a positive value, the MS will get reserved on a single PDCH until the downlink or uplink RLC buffer
level in the PCU exceeds the value of OSRTHRESH. When the threshold is exceeded the MS will be
eligible for TBF reservation based on its full multislot class and available PDCHs.

Object type: CLGPRSTSC.

Title: GPRS/EGPRS Traffic Load TSC specific counters for the downlink per cell.

MSESTDLTBFTSC2 The counter MSESTDLTBFTSC2 counts the number of successfully


established DL TBFs that use secondary Training Sequence Code
(TSC), where at least one data block has been sent and
 
acknowledged.

The counter MSESDLTBFTSC2 is a subset of the counter MSESTDLTBF.

6.7   Need for Expanded PDCH Address Spaces

This chapter describes STS counters based statistics that can be improved by activating
EPAS feature.

6.7.1   Introduction

EPAS introduces two ways to increase number of simultaneous PS users and number of
successfully established TBFs:

 Additional training sequence allowing to double of possible number of established


TBFs at once
 Re-reservation of existing TBFs to another PDCH when an opposite direction TBF
cannot be set up due to lack of USFs
Activation of the feature shall thus decrease number of Packet Access rejections that are
caused by lack of PDCH or PSET.

6.7.2   Suggested Formulas

The following rejection rate formulas, that are expected to be improved (increased) by
activating the EPAS feature, are proposed:

Equation 91   IP Transfer Interrupts UL due to Lack of Resources, excluding Lack of PDCHs

Equation 92   IP Transfer Interrupts DL due to Lack of Resources, excluding Lack of PDCHs

PDCH Congestion Cells:


AVG
Cell Name das
KC2154B 14
KV2170C 14
MC2129C 14
RC2178C 14
MC2122A 13
RC2191A 12
MC2121C 10
GV2010C 8
MC2127C 7
RC2182B 5
GC2001B 4
GC2001C 4
GC2110A 4
BH
Cell Name dsa
KC2154B 10
RC2178C 9
KV2170C 8
KC2190B 6
KC2155C 6
RC2191A 5
RA2153A 3

Cell Name dsa


MC2129C 14
MC2123D 9
MC2127C 9
GV2010C 8
GC2110C 8
MC2122A 8
GC2001D 7
GC2110A 7
MC2123C 7
MC2131A 5
GV2010B 5
GC2001B 4
MC2121C 4

Vendor Componente Fórmula Componente


Ericsson TBF_SUC_DL_ANATEL_N MSESTDLTBF
Ericsson TBF_SUC_DL_ANATEL_D MSESTDLTBF|LDISEST
Ericsson TBF_SUC_UL_ANATEL_N MSESTULTBF
Ericsson TBF_SUC_UL_ANATEL_D MSESTULTBF|PREJTFI|PREJOTH|PREJABISCONG

TBF ?? Double ?? Counter ??

BSC CELL epasstate


BSC06 GC2001D ACTIVE
BSC06 GC2110A ACTIVE
BSC06 GC2110C ACTIVE
BSC06 GV2010B ACTIVE
BSC06 GV2010C ACTIVE
EBSC05 KC2154B ACTIVE
EBSC05 KC2155C ACTIVE
EBSC05 KC2190B ACTIVE
EBSC05 KV2170C ACTIVE
EBSC05 RA2153A ACTIVE
EBSC05 RC2178C ACTIVE
EBSC05 RC2191A ACTIVE

Das könnte Ihnen auch gefallen