Module 1 - OSC

1 Nokia Siemens Networks Presentation / Author / Date
For internal use

RG20 (BSS)

Orthogonal Sub-channel
BSS21309, BSS30385
For internal use
Dependency table
BSS BSC*
BTS
TalkFamily
BTS
MetroSite
BTS
BTSplus
Release RG20 S15 Not supported Not supported Not supported**
BSS21309, BSS30385
DX200
Platform
MS SGSN MCS RAN NetAct
Release
No
dependency
SAIC indicating
its capability
No
dependency
No
dependency
No
dependency
OSS5.2 CD set 3
* supported by BSCi, BSC2i, BSC3i and FlexiBSC
** Supported via RG301397 (Cositing with BS2xx)
BTS
Flexi EDGE
BTS
UltraSite
BTS
Flexi Multiradio
Release SW: EX4.0 Not supported*** Not supported***
*** Supported starting from RG25(BSS)
For internal use
BSS21309, BSS30385
RG feature
Handset compatibility
in OSC allocation
Comments
OSC Half Rate with SAIC MS
(BSS21309); RG20
DARP (SAIC)
VAMOS I
VAMOS II
OSC Half Rate with SAIC MS is the NSN proprietary
feature which also motivated 3GPP to start VAMOS
standardization activities.
OSC Full Rate with SAIC MS (BSS
21534); RG25
DARP (SAIC)
VAMOS I
VAMOS II
OSC Full Rate with SAIC MS is the NSN proprietary
feature extending the concept of BSS21309
Orthogonal Sub-channels to full rate mode.
OSC support for VAMOS mobiles
(BSS 21313); RG30
DARP (SAIC)
VAMOS I
VAMOS II
Feature adds signaling support for new training
sequences supported by VAMOS handsets. New
training sequences are optimized for simultaneous
use.
VAMOS II handset utilizes advanced receiver
providing further link gains over VAMOS I or SAIC.
AQPSK for VAMOS II (BSS
21537); RG30
Rel 99
DARP (SAIC)
VAMOS I
VAMOS II
Introduces sub channel power control in DL allowing
also non-SAIC mobiles to be paired in OSC mode
with VAMOS II handsets.
RG(BSS) features with reference to 3GPP VAMOS
For internal use
BSS21309, BSS30385
Introduction
Feature details
Configuration management
Pilot results
Dimensioning aspects
Implementation aspects
PM counters
Feature impact analysis/feature performance monitoring
Contents
For internal use
Introduction
For internal use

Up to RG10(BSS) two channel modes were supported: Full Rate and Half Rate
(for both AMR and non-AMR speech codecs)

In RG20(BSS) the Orthogonal Sub-channel (OSC) feature introduces the new
channel mode: Double Half Rate (DHR)
DHR mode applies only to AMR connections for SAIC-capable mobile stations indicating
its SAIC capability to the network
with DHR mode up to four AMR HR connections may be allocated on one radio timeslot

OSC feature increases hardware efficiency
Increased TRX voice capacity
increased capacity for PS services (by saving resources occupied by CS)
improved energy efficiency
Introduction
For internal use

Orthogonal Sub-channel introduces two
new channels modes:
Double Half Rate (DHR) RG20 feature
OSC Half Rate with SAIC MS up to four
AMR HR connections may be allocated on
one radio timeslot
Double Full Rate (DFR) RG20EP1 feature
OSC Full Rate with SAIC MS up to two
AMR FR connections may be allocated on
one radio timeslot
Introduction
OSC-related enhancements on the roadmap
DFCA Support for OSC in RG20EP1
OSC Support for VAMOS mobiles in RG30
AQPSK for VAMOS II in RG30
OSC over EDAP in RG30
OSC Capability test in RG30

OSC FR feature provides the same capacity as AMR HR but by
utilizing full rate codecs allows improving speech quality in terms
of MOS
HR
FR
DFR
DHR
OSC
For internal use
Feature details
For internal use
Feature details
Orthogonal Sub-Channel (OSC) is a voice capacity feature that allows assigning
two AMR connections on the same TCH half rate channel
either TCHD or TCHH and further referred to as TCH/H
up to four AMR HR connections may be served by one radio timeslot

OSC exists of the following features:
OSC Half Rate with SAIC MS (BSS21309)
Circuit Switched Dynamic Abis Pool (BSS30385)
required in case of legacy
not needed in case of Packet Abis over IP/Eth (BSS21454) or Packet Abis over TDM
BSS21440)

OSC requires Single Antenna Interference Cancelation (SAIC) receiver in mobile
stations
BSC applies OSC only for MSs which indicate their SAIC support
Overview
For internal use
Feature details
Main aspects
TCH/H channel to be allocated to DHR connections is split into two (orthogonal)
sub-channels (OSC-0 and OSC-1)
The separation between OSC-0 and OSC-1 sub-channels is achieved by the use
of Training Sequence Codes
OSC-0 sub-channel is assigned a legacy TSC and uses legacy Abis transport
resources
OSC-1 sub-channel is assigned a pair-wise TSC and uses additional Abis
transport resources
additional Abis transport capacity is provided with CSDAP or Packet Abis
OSC-0 and OSC-1 sub-channels have independent RR signaling
For internal use
Table 1 Optimized TSC pairs for OSC

Feature details
OSC concept in DL direction is based on QPSK
modulation
orthogonal transmission

QPSK modulation carries two orthogonal sub-
channels which can be received by legacy SAIC MS
like normal GMSK

Separate reception of two sub-channels is enabled
by different TSCs send to MSs

TSC for OSC-0 TSC for OSC-1
0 2
1 7
2 0
3 4
4 3
5 6
6 5
7 1
For internal use
Feature details
Orthogonal sub-channel concept in UL direction is based on traditional GMSK
modulation and MU-MIMO (Multi User Multiple Input Multiple Output) technique
Two users are differentiated by TSC (same as DL) and propagation paths
BTS separates users with Rx Diversity and interference cancellation techniques
Successive Interference Cancellation (SIC) receiver is used
Rx Diversity is a prerequisite for OSC
without Rx Diversity DHR performance in UL would be very poor
Rx level balance between two connections occupying paired OSC-0 and OSC-1 sub-
channels is needed to provide sufficient quality
For internal use
DHR multiplexing mode is triggered based on the
load criterion
Load criterion is checked upon receiving a report
from HO&PC algorithm
If the percentage of free FR TCHs decreases below
Limit for Triggering OSC DHR Multiplexing,
the BTS enters DHR multiplexing mode ->
searching for the best pair to be multiplexed into
DHR mode (only one pair is multiplexed at a time
per BCSU)

When evaluating free FR TCHs, the PS territory
resources are interpreted according to setting of CS
TCH allocation calculation (CTC) parameter:
0 = Only CSW used RTSLs are used (default)
1 = CSW and PSW used RTSLs are used.
PSW is seen as occupied (optimize PS)
2 = CSW used and PSW used RTSLs are used.
PSW is seen as idle resource
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO of 2
nd

candidate to the target
channel
Load criterion
fulfilled?
Yes
No
Search for the 2
nd

candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
For internal use
Multiplexing is realized by handing over AMR HR/FR
connection to the target channel with ongoing AMR
HR call

Algorithm searches for the best pair of calls to be
multiplexed to ensure optimal quality in DHR mode
first, the best target channel is searched (1
st
candidate)
Only AMR HR SAIC connection is considered
next, the best connection to be handed over to target
channel is searched for (2
nd
candidate)
both half rate and full rate AMR SAIC connections
considered
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO of 2
nd

candidate to the target
channel
Load criterion
fulfilled?
Yes
No
Search for the 2
nd

candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
For internal use
Searching for the best target channel (the 1
st
candidate)
target channel candidates are searched:
only TCH/H with ongoing SAIC AMR call may become a target
channel for DHR multiplexing
UL Rx Level criterion:
-47dBm > UL RxLev Multiplexing UL Rx Level Threshold
UL & DL Rx Quality criterion:
UL(DL) RxQual Multiplexing Rx Quality Threshold
the list of channels fulfilling above criteria is sorted in descending
order according to UL path-loss criterion (UL RxLev + current
power reduction)
the 1
st
channel in the list (with the lowest path-loss) is selected
as the best target channel (1
st
candidate)
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
For internal use
MS1
MS2
MS3
ULRxLev
MS1
<Muxltiplexing UL RxLev Threshold
ULRxQual
MS1
=Multiplexing RxQual Threshold
DLRxQual
MS1
<Multiplexing RxQual Threshold
ULRxLev
MS3
>Multiplexing UL RxLev Threshold
ULRxQual
MS3
DLRxQual
MS3

ULRxLev
MS2
=Multiplexing UL RxLev Threshold
ULRxQual
MS2
=Multiplexing RxQual Threshold
DLRxQual
MS2
the best target channel:
TCH/H occupied by MS2
target channel candidate list:
1. TCH/H occupied by MS2
sorted target channel candidate list:
ULRxLev
MS2
+Power reduction
MS2
>
ULRxLev
MS3
+Power reduction
MS3
DHR multiplexing example
For internal use
Searching for the best candidate to be handed over (the 2
nd

candidate) to the target
both AMR HR and FR calls are considered
unless AMR FR to DHR HO is blocked with UTPFIL parameter
(AMR FR DHR MUX)
Candidates for DHR multiplexing HO must fulfill the following
criteria:
UL & DL RxQual Intra HO Threshold Rx Qual AMR FR
and
-47dBm > UL RxLev Multiplexing UL Rx Level Threshold

Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
For internal use
The list of 2
nd
candidates is created based on the UL Rx Level Window criterion:
(UL RxLev
2nd
+Current Power Reduction
2nd
)(UL RxLev
1st
-Multiplexing UL RxLev Window)
and
(UL RxLev
2nd
+Current Power Reduction
2nd
)(UL RxLev
1st
+Multiplexing UL RxLev Window +
Max Power Reduction
2nd
)
where
Max Power Reduction
2nd
is the maximum possible uplink power reduction of the 2
nd
candidate
(concerning MS power capability and the PCLowerThresholdLevUL+6dB margin):
MaxPowerReduction = min [min(MsTxPwrMax. MSPowerClass)-MSTxPwrMin, RxLevReductionMax]
where
RxLevReductionMax = max(0, RXLEVmax_UL-PCLowerThresholdLevUL-SafetyMargin)
SafetyMargin - to prevent excessive power reduction (UTPFIL ID= 05AC006A: 1C) in Common BCCH
scenario
MsTxPwrMax = MsTxPwrMaxGSM or MsTxPwrMaxGSM1x00 depending on the frequency band
MsPowerClass - the max power defined by the MS power class
Multiplexing Window for 2nd
candidate
UL RxLev
1st

RxLev
RxLev
1st
- Window
RxLev
1st
+ Window + Max Power Reduction
2nd

For internal use
Searching for the DHR multiplexing 2
nd
candidate according to UL Rx Level Window criterion
(UL RxLev
2nd
+ Current Power Reduction
2nd
) (UL RxLev
1st
- Multiplexing UL RxLev Window)
and
(UL RxLev
2nd
+ Current Power Reduction
2nd
) (UL RxLev
1st
+ Multiplexing UL RxLev Window + Max
Power Reduction
2nd
)
MS2 has been chosen as the 1
st
candidate
ULRxLev
MS3
+Power Reduction >UL RxLev
MS2
- Multiplexing UL RxLev Window
ULRxLev
MS3
+Power Reduction <UL RxLev
MS2
+Multiplexing UL RxLev Window +max power reduction
MS3
ULRxLev
MS4
+Power Reduction >UL RxLev
MS2
ULRxLev
MS4
MS2
+Multiplexing UL RxLev Window +max power reduction
MS4
MS1
MS2
MS3
MS4
ULRxLev
MS1
MS2
RxLev
MS2
MS4

Multiplexing Window for MS4
MS1
MS4
RxLev
MS2
+ Window +
Max Power Reduction
MS3

RxLev
MS2
- Window RxLev
MS2

RxLev
MS2
MS3
Multiplexing Window for MS3
For internal use
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
Among all the connections meeting DHR
multiplexing HO criteria the best 2
nd
candidate
is searched
The best 2
nd
candidate is determined based on:
UL Rx Level Difference criterion

ULRXLEV
=(UL RxLev
1st
+CurrentPowerReduction
1st
)-(UL RxLev
2nd
+
CurrentPowerReduction
2nd
)
UL Rx Level Change Rate criterion

UL RXLEV CHANGE RATE
=ULRxLevChangeRate
1st
-ULRxLevChangeRate
2nd

where
ULRxLevChangeRate =(ULRxLev+CurrentPowerReduction)
new
-
(ULRxLev+CurrentPowerReduction)
old
where
new refers to the values of the latest report from HO&PC algorithm
old refers to the values of the latest but one report from HO&PC algorithm
For internal use
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
MS1
MS2
MS3
MS4
1
st
candidate: MS2
list of 2
nd
candidates (fulfilling also RxQual criterion): MS3, MS4
|ULRXLEV
MS3-MS2
|+|ULRxLev Change Rate
MS3-MS2
| <
|ULRXLEV
MS4-MS2
|+|ULRxLev Change Rate
MS4-MS2
|
the best 2
nd
candidate: MS3
Connection with the minimum value of
(|
ULRXLEV
|

+ |
|)
is selected as the best 2
nd
candidate

If
is greater than the change rate
threshold (UTPFIL parameter: UL RX CHANGE RATE) the
multiplexing is rejected
if a suitable multiplexing pair for the best 1
st
candidate cannot be
found, the algorithm continues with multiplexing attempt for the
next best 1
st
candidate and so on until suitable pair is found or
there is no more 1
st
candidates to be checked
For internal use
The best 2
nd
candidate is handed over to the target channel
Multiplexing HO may be done to:
OSC-1 sub-channel if AMR HR connection occupying target channel
is regarded as OSC-0
OSC-0 sub-channel if AMR HR connection occupying target channel
is regarded as OSC-1
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
TRX:0
TRX:1
TS7
DHR multiplexing HO
connection to be handed over
target channel
TS6 TS5 MS3 TS3 TS2 TS1 TS0
TS7 MS2 TS5 TS3 TS2 TS1 TS0 TS4
HR multiplexing
OSC
multiplexing
MS3
free
OSC-0
MS2
OSC-0
free
OSC-1
free
OSC-1
HR multiplexing
OSC
multiplexing
MS3
free
OSC-0
MS2
OSC-1
free
OSC-1
free
OSC-0
For internal use
During DHR multiplexing procedure BTS switches from GMSK
modulation to QPSK modulation in DL on the target TCH/H

During DHR multiplexing HO the
Training Sequence Code is selected based on the TSC value
used for OSC-0 connections according to table 1 (Optimized
TSC pairs)
If legacy Abis is used, CSDAP resource is needed for the new
radio sub-channel
If there is Packet Abis, a separate dynamic Abis pool is not needed
if there are no free CSDAP resources for OSC-1 sub-channel
available,
Radio Channel Allocation algorithm changes priorities in
multiplexing algorithm to prefer (for the next attempts the
number defined by UTPFIL parameter CSDAP PENALTY
COUNT) a pair of AMR connections for which CSDAP
resource is not needed
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
For internal use
UL power optimization during DHR multiplexing HO is needed to
minimize the difference between UL Rx Levels of paired DHR
connections
UL Tx power level of the 1
st
candidate is not changed during DHR
multiplexing HO
UL Tx power level of the 2
nd
candidate is adjusted so that the UL Rx
Levels of two paired calls are the same

max possible power reduction is defined by the following formula:

UL Rx Level of the 2nd candidate may be allowed to be
higher/lower than of the 1st candidate by the value of UTPFIL
parameter (UL RX LEVEL DIFF)
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
tionMax] RxLevReduc , MSTxPwrMin
- ss) MSPowerCla TxPwrMax. min[min(Ms duction MaxPowerRe
class power MS by the defined power max the - ss MsPowerCla
band frequency on the depending GSM1x00 MsTxPwrMax or GSM MsTxPwrMax MsTxPwrMax
in) SafetyMarg - L esholdLevU PCLowerThr - L RXLEVmax_U max(0, tionMax RxLevReduc

For internal use
DL power optimization during DHR multiplexing HO is needed to
avoid an unnecessary power increase on target channel

an extra power increase is applied to balance ~3dB performance
degradation (OSC with QPSK has worse performance than AMR with
GMSK) and provide sufficient DL quality in DHR mode

optimized DL Tx power level is determined by calculating new Power
Reduction defined as the minimum of two values:
max(0, Old_Power_Red_DL
1st
3dB) and
max(0,RxLev_DL
2nd
+ Old_Power_Red_DL
2nd
RxLev_DL
1st
3dB)
The value of 3dB may be adjusted with the UTPFIL parameter:
OSC MODULATION LOSS
Search for the 1
st

candidate (target
channel)
DHR multiplexing HO
Load criterion
fulfilled?
Yes
No
Search for the
2
nd
candidate
Report from
HO&PC
ready
suitable target
channel found?
Yes
suitable 2
nd
candidate
found?
end
No
No
end
Yes
end
Enter DHR
multiplexing mode
For internal use
PC algorithm for DHR mode is similar to the one used for non-DHR connections
legacy Rx Level thresholds are re-used
new DHR-specific Rx Quality thresholds allow differentiating from AMR HR
PC Lower Threshold DL Rx Qual DHR
PC Upper Threshold DL Rx Qual DHR
PC Lower Threshold UL Rx Qual DHR
PC Upper Threshold UL Rx Qual DHR
PC control has lower priority than
demultiplexing HO
DL PC is performed for both paired DHR
connections independently (based on Rx Level
and Rx Quality criteria) but used Tx power is
determined by the weaker connection
For internal use
UL PC is performed for both paired DHR
connections independently (based on Rx
Level and Rx Quality criteria)
power decrease step size is adjusted in a
way that the difference between UL Rx
Levels of paired calls does not reach or
exceed the value of OSC Multiplexing UL
Rx Level Window
if power decrease results in reaching
or exceeding OSC Multiplexing UL
Rx Level Window, PC action is
abandoned
power increase step size determination
algorithm has not been changed and
works as in current PC implementation
For internal use
Demultiplexing
For internal use
DHR connection may be handed over to the other cell but only to AMR HR/FR channel mode
(DHR to DHR inter-cell handovers are not possible)
Inter-cell HO for DHR connections are controlled with new Rx Quality thresholds (Threshold
Dl Rx Qual DHR and Threshold Ul Rx Qual DHR) and legacy Rx Level thresholds (Threshold
Level Downlink Rx Level and Threshold Level Uplink Rx Level)
inter-cell HO is triggered if one of the following conditions are met:
DLRxQual Threshold DL Rx Qual DHR
ULRxQual Threshold UL Rx Qual DHR
DLRxLev ThresholdLevelDownlinkRxLevel
ULRxLev ThresholdLevelDownlinkRxLevel
For internal use
DHR demultiplexing HO (intra-cell HO from DHR to non-DHR mode) can be
triggered by:
Rx Quality criterion
Demultiplexing is performed if UL or DL Rx Quality of DHR connection is greater than or equal to
Demultiplexing Rx Quality Threshold
UL Rx Level Balance criterion (has lower priority than Rx Quality demultiplexing HO)
if UL Rx Level Difference (between paired DHR calls) is greater than or equal to OSC
Demultiplexing UL RxLevel Margin, the connection with higher UL RxLev is demultiplexed to non-
DHR mode
Rx Level criterion if Improved AMR Packing and Unpacking (BSS21483) is enabled
demultiplexing HO to AMR FR is performed if UL or DL Rx Level of DHR connection drops below the
threshold triggering AMR HR unpacking HO (introduced with BSS21483)
For internal use
DHR demultiplexing HO may be performed to either AMR HR or AMR FR
if demultiplexing is triggered by Rx Quality degradation and AMR Unpacking Optimization
(BSS21120) is enabled, the DHR connection is demultiplexed to:
AMR HR as the first option (AMR FR is allowed as the secondary option) - 1
AMR FR as the first option (AMR HR is allowed as the secondary option) - 2
DHR demultiplexing HO is prevented - 3
If UL or DL Rx Quality is equal to or higher than Intra HO Lower Rx Quality Limit AMR, DHR
demultiplexing HO triggered by RxQual degradation is prevented - 4

1 2
3
4
For internal use
AMR HR is a prerequisite for DHR
target channels for DHR multiplexing are searched only among channels already allocated
to AMR HR connections
Support for Single Antenna Interference Cancellation is a prerequisite for DHR
BSC must be able to recognize SAIC capable MS
Rx Diversity is a prerequisite for DHR
without Rx Diversity UL Quality in DHR mode may be very poor
AMR FR is a prerequisite for DHR (until RG20EP1)
AMR HR packing
DHR multiplexing is supplementary functionality in addition to the traditional AMR HR
packing allowing for achieving higher capacity
CSDAP and Packet Abis
one of these features is required to provide additional Abis capacity needed for DHR mode
Soft Channel Capacity
this feature is not mandatory for DHR but it may be used to enable the full TRX
configuration with Double Half Rate
For internal use
Baseband Frequency Hopping
To apply DHR multiplexing in BB hopping scenario, all TRXs of the hopping group must
be OSC configured
Antenna Hopping
To apply DHR multiplexing in antenna hopping scenario, all TRXs of the BTS must be
OSC configured
Double Power TRX and Intelligent Downlink Diversity
DHR multiplexing is not performed in either DPTRXs or IDD TRXs
Enhanced Coverage by Frequency Hopping, Intelligent Underlay-Overlay,
Handover Support for Coverage Enhancements
OSC is not supported in super reuse layers of a BTS
Extended Cell Range
OSC is not supported in TRXs of the extended or super extended coverage area
4-way UL Diversity
DHR multiplexing is not performed in TRXs with 4UD feature in use

For internal use
AMR Unpacking Optimization
Lower Rx Level and Lower Rx Quality thresholds are re-used to prevent DHR
demultiplexing HO in poor radio conditions
Upper Rx Level threshold is used to determine the target channel mode (AMR FR or AMR
HR) for DHR connections being demultiplexed
Improved AMR Packing and Unpacking
Rx Level threshold triggering unpacking is re-used to trigger DHR demultiplexing HO
Tandem-free Operation
normal rules of TFO are applied during DHR multiplexing and demultiplexing HOs
TRAU Bicasting in AMR FR/HR Handover
TRAU Bicasting is applied to OSC multiplexing and OSC demultiplexing when the
channel mode is changed from AMR FR to DHR or from DHR to AMR FR and conditions
for TRAU Bicasting in AMR FR/HR Handover are fulfilled
Wideband AMR
DHR multiplexing of WB-AMR FR connection is not supported
DHR multiplexing is not applied to Dual Transfer Mode calls
For internal use
Discontinuous Transmission
in both UL and DL direction DTX is applied to each of two paired connections
independently
in DL during DTX periods GMSK is used for active channel instead of QPSK

Pre-emption (forced HO and forced call release)
forced actions may be applied to paired DHR calls in a congestion scenario to find a
TCH/H for a new call with higher priority (than both DHR connections in question)
non-OSC connections are preferred as the target for the forced actions if they are
regarded as equal candidates by other criteria of the pre-emption algorithm

UL interference level update procedure
UL interference level update procedure is not impacted by the DHR feature
UL interference level information is not utilized in DHR multiplexing algorithm

For internal use
Epsilon TRX (EXxA) does not support the concurrent use of EGPRS and OSC within
a Dual TRX unit (this limitation refers to EGPRS only and not to GPRS)
if EGPRS is applied in one TRX of an Epsilon Dual TRX then OSC cannot be applied in the
other TRX of the Dual TRX

Selection between EGPRS and OSC is made when the first TRX of an Epsilon Dual
TRX is started up
BSC sets OSC starting mode for a Flexi EDGE TRX only if:
OSC has been enabled in the BTS and
Dual TRX usage (dualTRXusage) parameter of the TRX is set to value disabled and
neither of the two TRXs of the Dual TRX unit is an EGPRS TRX
TRXs is regarded as EGPRS TRX if:
EGPRS enabled (EGENA) is set to value different than disabled and
GPRS enabled TRX (GTRX) is set to value Y

Odessa TRX (EXxB) does support EGPRS in the DTRX
For internal use
If Baseband Hopping or Antenna Hopping is in use in a BTS and at least one TRX
needs to be started in EGPRS mode, the BSC regards all the TRXs in the BTS
object as EGPRS TRXs and starts them in EGPRS mode

The rules of TRX starting mode determination apply also to Odessa TRX. However,
for Odessa TRX the starting mode set by BSC is critical only in the case of common
BB/AH hopping with Epsilon TRX
if neither BB hopping nor AH hopping is used in a BTS, the OSC can be applied in the
Odessa TRX even though the BSC has started it in EGPRS mode
if all the TRXs in the BB/AH hopping group are of Odessa HW variant, OSC can be
applied without any limitations even though the BSC has not started any of the TRXs in
OSC mode

TRX type GTRX EGENA OSC
Epsilon Dual TRX Yes Yes Not possible
Epsilon Dual TRX Yes No Possible
Epsilon Dual TRX No No Possible
Odessa Dual TRX* Yes Yes Possible
Odessa Dual TRX* Yes No Possible
Odessa Dual TRX* No No Possible
TRX types in BTS GENA EGENA OSC in BTS
Epsilon Dual TRXs only Yes Yes Not possible
Mix of Epsilon and Odessa Dual TRXs Yes Yes Not possible
Odessa Dual TRXs only Yes Yes Possible

TRX starting mode
Antenna hopping
For internal use
CSDAP
For internal use
Circuit Switched Dynamic Abis Pool
Additional Abis resources are needed for OSC-1 channels
this additional capacity can be taken from a new dedicated pool of
Abis resources available for each TRX within the BTS site
this new pool of Abis resources is hereafter referred to as CSDAP
(Circuit Switched Dynamic Abis Pool)
Main characteristics of CSDAP:
CSDAPs are created per BCF (BTS site) basis
up to 4 CSDAPs pools are possible per BCF
up to 1000 CSDAPs is possible per BSC
CSDAP must be created in consecutive PCM TSLs
CSDAP size ranges from 1-31 TSL for E1 (1-24 for T1)
with granularity of 1 PCM TSL (i.e. 64 kbps channels)
CSDAP can be created on any PCM line, in particular it can
be on different PCM than that used by associated TCH and TRXSIG

For internal use
MS1
FR
For OSC DHR mode more Abis transmission is needed for radio timeslot because
two calls are multiplexed in one HR channel
MS1
HR
free
HR
HR (time)
multiplexing
MS1
HR
MS2
HR
HR (time)
multiplexing
free
FR
HR (time)
multiplexing
free
OSC-0
MS2
OSC-1
O
S
C

m
u
l
t
i
p
l
e
x
i
n
g

free
OSC-1
MS1
OSC-0
HR (time)
multiplexing
MS3
OSC-0
MS2
OSC-1
O
S
C

m
u
l
t
i
p
l
e
x
i
n
g

MS4
OSC-1
MS1
OSC-0
a single RTSL carrying FR call
is mapped to a single Abis sub-TSL
a single RTSL carrying HR (1 or 2 calls)
is mapped to a single Abis sub-TSL
as the entire channel is used by HR call
in every second time slot
in OSC mode 2 DHR calls are transmitted in the same time
(i.e. time slot as these calls are distinguished by different TSC):
OSC-0 channels always use PCM resources reserved for TCH
while
OSC-1 channels always use PCM resources reserved in CSDAP
2+2+2
64kbit trxsig
For internal use
Resource allocation from CSDAP
CSDAP resource is allocated to OSC-1 call activated in the cell controlled by BCF which
the CSDAP is attached to
Releasing of CSDAP resources
The following events trigger releasing of CSDAP resources:
OSC-1 call completion
OSC-1 demultiplexing (intra-cell HO)
inter-cell HO for OSC-1 call
OSC multiplexing failure
OSC-1 call activation failure
Only channel activation failure (for OSC-1 call) effects with immediate CSDAP release, in
case of the remaining above-mentioned events (e.g. OSC-1 call completion) BSC waits
until radio channel is successfully released from BTS
Either allocation or release of OSC-0 call does not affect CSDAP resource
allocation
For internal use
Dimensioning
For internal use
Dimensioning steps
Dimensioning for OSC consists of a few steps
Air interface dimensioning
Access transmission dimensioning
BSC / BCSU dimensioning
OSC licenses
Planning steps
BSS/TSC planning
BCSU planning

For internal use
Air interface dimensioning

The aim for air interface dimensioning is to calculate the
amount of OSC traffic (gain) that can be achieved

OSC strategy possibilities
Decrease number of frequencies
By implementing OSC-HR traffic can be served by less TRXs (assuming
traffic remains the same) and frequencies can be freed for refarming
Increase voice capacity
By implementing OSC-HR more traffic is potentially served
Increase PS capacity
By Implementing OSC-HR more voice calls can be packed more efficiently
and radio resources are freed for PS territory
The strategy is important to know for the dimensioning and
planning of OSC
For internal use
OSC traffic estimation
OSC traffic calculation input
SAIC traffic usage

HR utilization
OSC calls start from AMR HR (trf_122a)

Rxlevel / RxQuality distribution
OSC has a working range upto
RXLevel : -90dBm (maximum is -95dBm)
RXQuality : 4 (maximum is 6, but not recommended to use)

Traffic (trf_202a) / trf_1d
) 014017 .. (014010 samples RXquality DL all
) 014157 .. (01415 samples RXQuality DL SAIC
usage SAIC

Cell
range
Limited cell
area where
OSC calls
can be
supported
De-
multiplexing
Multiplexing
For internal use
OSC traffic estimation
OSC percentage calculation

Example
SAIC penetration is 45%
45-60% is typical for SAIC penetration
HR usage is 80%
Rxquality
(0-4)
, Rxlevel
(-47 to -90)
is 90%

Example : 45%/2 * 80% * 90% = 16.2% OSC-HR traffic

For OSC-HR traffic in Erlang multiply the share with the traffic (trf_202a for
instance)
The outcome of the OSC-HR share is going to be used in the CSDAP
dimensioning
The CSDAP size is defining the upper limits for OSC-HR traffic

s ity_sample all_RXqual
) RXLevel , ty DL(RXquali
* HR% * )
2
usage SAIC
( percentage OSC
85dBm - to 47dBm - 4 0-

For internal use

CSDAP size depends on site configuration and OSC penetration

site configuration
#BCCH/CCCH/CDED per cell
codec distribution
% FR =
% HR =
% OSC =
#RTSL available for CS
# Abis trunks for FR
# Abis trunks for HR
# Abis trunks for OSC
Erl / site (and codec)
FR/HR trunks actually do not need
to be computed because their resources
are anyway available on Abis permanently
Dynamic Abis CSDAP size (1)
Abis dimensioning aspects
For internal use
CSDAP calculator
To be able to calculate the CSDAP a tool has been developed
Link of tool
CSDAP Calculator v0.1.0
INPUTS
BTS HW Configuration cell1 cell2 cell 3
no of TRXs: 3 3 3
no of BCCH/SDCCH: 3 3 3
no of fixed PDCHs (CDED): 1 1 1
no of TCHs: 20 20 20
Traffic load cell1 cell2 cell 3 percentage
voice FR [Erl] 11,03 11,03 11,03 60 % mode: utilization
voice HR [Erl] 3,68 3,68 3,68 20 %
voice OSC [Erl] 3,68 3,68 3,68 20 %
CS blocking 2,00 % 2,00 % 2,00 %
OUTPUTS
PCM TSLs needed: 2
message:
2009 Network Engineering Wroclaw
OK
3 3 3
utilization
For internal use
to avoid OSC de-multiplexing it is recommended to round up the results related to OSC trunks
example:

3 PCM TSLs are recommended to be used
Dynamic Abis CSDAP size - example

33 OSC Abis trunks => 9 subchannels => 3 TSL
Site configuration: 3 TRX/cell, 3 BCCH+SDCCH/cell, 1 CDED/cell => 20 RTSLs available for CS/cell (N
cs
)
codec penetration: 50% FR, 25% HR, 25% OSC

Calculations:
#FR trunks/cell = 14
#HR trunks/cell = 7
#OSC trunks/cell = 7
28 trunks@2%

20.15 Erl/cell
60.45 Erl/site
30.23 FR Erl
15.12 HR Erl
15.12 OSC Erl
Not needed to be computed
25 . 0 * 25 . 0 * 75 . 0
*
_

n penetratio n penetratio
cs n penetratio
HR trunks
HR FR
N HR
N
25 . 0 * 25 . 0 * 75 . 0
*
_

n penetratio n penetratio
cs pentration
DHR trunks
HR FR
N DHR
N
4 2
_ _
_
DHR Trunks HR Trunks
cs FR Trunks
N N
N N
7
25 . 0 25 * 25 . 0 50 * 75 . 0
20 * 25 . 0

HRTrunks
*
*
*
* Source from NE
For internal use
OSC increase voice capacity in GERAN by doubling the number of connections that can run
on the same TCH/H RTSL
Therefore the whole transmission path in access network (from BTS to MSC) is affected
thus introduction of OSC requires to check available capacity in the whole access
network
BTS
Enabling of OSC allows to increase capacity per TRX. Several
scenarios possible, each of them have potential impact on
number of resources in access network:
-TRX configuration is kept, CS traffic kept, more RTSL available for
PS traffic => higher PS traffic/throughputs possible
- TRX configuration is kept, PS territory is kept, more CS traffic can
be served
- TRX configuration decreased but CS traffic is kept because of huge
OSC penetration
-
BSC
TCSM
MSC
Abis
Ater
A
Abis interface
=> Dynamic Abis: TRX site configuration is crucial for estimation of
required PCM lines, CSDAP computed based on OSC penetration,
modification of PS territory affects EDAP size, TRXSIG capacity must
be chosen appropriately (depending on load and codec type)
=> Packet Abis: required bandwidth depends on amount of CS and PS
traffic as well as codec distribution
BSC
Traffic to be handled determines bandwidth required in transport (Abis,
Ater) regardless on used technology => this must be reflected in
number of Exchange Terminals (ET16, ETS2, ETIP, ETP)
Number of users served have impact on signaling capacity and
processor load (AS7, BCSU, MCMU).
PS traffic modification have impact on PCU HW and Gb links capacity.
Other aspects to be evaluated: LAC planning, Soft channel capacity
TCSM
Additional CS traffic must reflected in the number of transcoders as
well as Exchange Terminals (towards BSC and MSC).
Ater / A interface
CS traffic increase caused by OSC introduction has also impact on
transport resources towards Core. The need for additional resources
must be checked regardless on used transport technology (TDM-based
or IP-based).
Access network dimensioning aspects
General overview
For internal use
system performance and capacity
DHR increases the radio channel capacity of TRXs. This limits the number of
TRXs that can be configured in the BSC.

BSC calculates a half rate capable TSL in an OSC capable TRX as corresponding
to 3 TCHs on the BCSUs
Each OSC TRX will be counted as 3 BCSU TCHs

When the DHR capacity exceeds the actual traffic handling capacity of the BSC,
the BSC makes sure that, in each created TRX, it is possible to activate as many
calls as there are TCH TSLs in the TRX.
For internal use
BCSU capacity, example
Allowed Full Rate configuration
6 TRXs * 8 TCHs = 48 TCHs
Allowed Half Rate configuration
3 TRXs * 2*8 TCHs = 48 TCHs
Allowed OSC Half Rate config.
2 TRXs * 3*8 TCHs = 48 TCHs
BSC telecom makes sure that BCSU capacity is not exceeded with OSC Half Rate.
Soft Channel Capacity feature is needed for full TRX configuration with OSC Half Rate.
For internal use
Presented example calculations which give overview on potential capacity bottlenecks in
access network after introduction of OSC
Please note that these calculations are example as the final results always depend on
load situation in network before introduction of OSC (BSC type and capacity, interface
load, processors load, )
OSC penetration rate and introduction strategy
This means that calculated results must not be treated as unavoidable consequences
of OSC introduction because they are only examples to illustrate possible impacts of
OSC on access network in different scenarios (e.g. for different OSC penetration, BSC load,
)
Please note that existing dimensioning rules were used to calculate the examples on the
next slides => introduction of OSC does not modify existing BSC dimensioning
methodology, it only leads to greater consumption of resources in access network
BSC
TCSM
MSC
Abis
Ater
A
Example calculations (1)
For internal use
Example scenario:
150 sites, 3+3+3 (per cell: 3 sign RTSL + 1 CDED+ 3 CDEF), 50% FR / 50% HR,
TRXSIG = 32k
FlexiBSC, PCU2E (incl. asymmetrical PCU conf.), TDM-based transport
Initial calculations (i.e. for case without OSC): 18.38 Erl/cell, 5 MB/BH/cell
per site: 1 E1 line (18 TCH, 5 TSL for TRXSIG+OMUSIG, 6 EDAP)
Abis channels for PS: 3*(1+3) + 4*6 = 36 sub-channels
per BSC: 1350 TRX, 150 E1 lines on Abis, 8271 Erl, 5400 Abis sub-channels for PS
3 BCSU, 8 PCU (70% utilization), 4 E1 lines on Gb (15 TSL/PCU)
signaling: 1350+150 LAPD on Abis, 71 LAPD on Ater, 16 SS7@64 (2 BCSU needed
due to signaling)
TCSM configuration (standalone TCSM): 8430 Ater channels (0.1% blocking) => 71 E1
lines on Ater
Gb
BSC
TCSM
MSC
Abis
Ater
A
PS core
3+3+3 (9 TRX)
55.14 Erl
15 MB/BH
1 E1 line:
18 TSL/TCH
5 TSL/sign
6 TSL/EDAP (~40 kbps/user)
150 E1 / BSC 71 E1 / BSC
4 E1 / BSC
15 ET16 (225 E1)
3 BCSU, 8 PCU
1 TCSM rack
5 TC2C (9 TR3E, 5 ET16)
20 ET16 (towards MSC)
284 E1 / TCSM
For internal use
OSC introduction scenario 1:
OSC on every site, huge penetration OSC, codec distribution of 40% FR / 10% HR, 50% OSC
CS traffic increase, PS traffic kept the same
Calculations: 25.53 Erl/cell, 5 MB/BH/cell
per site: 1 E1 line with compressed mapping (18 TCH, 5 TSL for TRXSIG+OMUSIG, 6 EDAP,
4 CSDAP); without compressed mapping: 2 E1 lines / site => impact on ET16 in BSC
signaling: 1350+150 LAPD on Abis, 98 LAPD on Ater, 22 SS7@64 i.e. 2 BSC would be needed!!!
=> 11 SS7@128 (3 BCSU due to signaling) or SIGTRAN
TCSM configuration (standalone TCSM): 11666 Ater channels (0.1% blocking) => 98 E1 lines on
Ater
Gb
BSC
TCSM
MSC
Abis
Ater
A
PS core
3+3+3 (9 TRX)
76.59 Erl
15 MB/BH
1 E1 line with
compressed
mapping
18 TSL/TCH
5 TSL/sign
4 TSL/CSDAP
150 E1 / BSC 98 E1 / BSC
4 E1 / BSC
16 ET16 (252 E1)
3 BCSU, 8 PCU
7 TC2C (13 TR3E, 7 ET16)
=> 2nd TCSM cabinet needed
392 E1 / TCSM
Note! In this case there are much more users. Therefore dynamic capacity must be double-checked too.
In particular BCSU/MCMU load as well as LAC planning.
For internal use
OSC introduction scenario 2:
OSC on every site, moderate penetration OSC with distribution of 40% FR / 40% HR / 20% OSC
additional capacity used to relax number of RTSL used by voice to increase PS traffic and throughput (*)
i.e. site configuration can be changed to 3+3+3 (per cell: 3 sign RTSL + 3 CDED+ 3 CDEF)
Calculations: 19.26 Erl/cell, 10 MB/BH/cell
per site: 1 E1 line with compressed mapping (18 TCH, 5 TSL for TRXSIG+OMUSIG, 8
EDAP,
2 CSDAP) => cf. slide 19; without compressed mapping: 2 E1 lines / site => impact on ET16 in BSC
signaling: 1350+150 LAPD on Abis, 74 LAPD on Ater, 17 SS7@64 i.e. 2 BSC would be needed!!!
=> 9 SS7@128 (3 BCSU due to signaling) or SIGTRAN
TCSM configuration (standalone TCSM): 8829 Ater channels (0.1% blocking) => 74 E1 lines on Ater
Gb
BSC
TCSM
MSC
Abis
Ater
A
PS core
3+3+3 (9 TRX)
57.78 Erl
30 MB/BH
1 E1 line with
compressed
mapping
18 TSL/TCH
5 TSL/sign
2 TSL/CSDAP
150 E1 / BSC 74 E1 / BSC
8 E1 / BSC
15 ET16 (232 E1)
3 BCSU, 11 PCU
1 TCSM rack
5 TC2C (10 TR3E, 5 ET16)
296 E1 / TCSM
For internal use

These planning activities can be done using existing methods and tools
introduction of OSC does not modify access dimensioning methodology
Capacity enhancements may be not necessarily needed in access network as a
result of OSC introduction; whether they are required or not it depends on:
OSC introduction strategy (e.g. if OSC is introduced to decrease BTS site configuration)
OSC penetration
Load situation in access network before introduction of OSC
Anyway audit of access network is necessary as a part of OSC planning
activities in order:
to definitely rule out or to confirm the need for access network capacity extension
to indicate HW elements or interfaces where capacity extension is needed in given
scenario and access network configuration
Main message:
capacity available in the whole transmission path in access network must be checked
during OSC introduction and as a result some re-planning may be needed otherwise
different capacity bottlenecks may prevent from achieving expected OSC capacity gains
OSC impact summary
For internal use
OSC licenses
In the BSC is the OSC license
The license works based on
Number of simultaneous OSC pairs
100 calls per license
Number of OSC TRXs activated in the BSC do not have an impact

There are two ways in looking at the licenses
Per implementation via the CSDAP calculations OSC traffic is
estimated. Estimations could be done via
(avg / peak = burstiness, mux HO / Erlang = number of simultanious calls
After implementation
The counter 1267 (DHR_MPLX_FAIL_DUE_OTHER) is triggered when
there are abnormal OSC HO failures, but also when the licenses are not
enough
For internal use
Planning
For internal use
Planning for OSC
When all is dimensioned and verified the planning phase
(optimizing for performance) should start and should consist of
the following aspects
BCC / TSC planning / verification
MS differentiation is done by using different TSC
some TSC combinations provide less good performance
BCSU planning
OSC will start independently per TRX of a BTS per BCSU
Handover planning
OSC is starting slow and delaying the handovers will enhance the
performance
Parameter planning
Depending on the strategy the OSC parameters should be chosen
For internal use
BCC / TSC planning / verification

The separation between the simultaneous connections in a TCH is
enabled by the use of separate training sequences
Subchannel specific Training Sequence Codes (TSC) are optimised in
pairs for the lowest cross-correlation

0 2
1 7
2 0
3 4
4 3
5 6
6 5
7 1
TSC for the second connection is selected
based on the value used for the first
connection in the TCH according to the table
on the right
values in the table are still subject to
optimization and may change
For internal use
TSC planning aspects (2)
In case of OSC networks (especially in 1x1 reuse) the TSC planning issue becomes more
problematic and may need special attention
the probability of accidental synchronization is the same as in non-OSC
0 2
1 7
2 0
3 4
4 3
5 6
6 5
7 1
Optimized TSC pairs for OSC

activation of OSC in a network with optimal (according to
legacy planning rules) TSC plan may result in collisions
between main TSCs of one cell and paired TSCs of other
cells
such collisions between TSCs characterized by poor mutual
cross-correlation properties may lead to significant quality
degradation
example: main TSCs determined by legacy non-OSC aware
algorithm; paired TSC derived from predefined table
cell B
main TSC = 0 main TSC = 2
paired TSC = 0
cell A
paired TSC = 2
collision between main TSC of cell A (B)
and paired TSC of cell B (A)
collision between paired TSC of cell A (B)
and main TSC of cell B (A)
For internal use
TSC planning aspects (3)
If after OSC activation some cells suffer from relatively higher speech quality degradation
than others, the TSC plan should be reviewed
speech quality may be monitored with e.g. OSC RX Quality Measurements (counters:
122000-122079) and/or FER Measurement (counter 77002)
if any TSC collision is detected the TSC re-planning should be considered taking into
account:
interference relations between neighboring cells
probability of paired TSC utilization dependent on OSC penetration
fact that QPSK interference is more harmful for GMSK victim than GMSK interference
there is significant performance deterioration of OSC DL transmission due to TSC
collision between OSC paired users and external interferer (see next slide)
cross-correlation properties between:
main TSC in cell A and main TSC in cell B (as in non-OSC case)
main TSC in cell A and paired-TSC in cell B and vice versa (main TSC in cell B and paired-TSC
in cell A)
paired-TSC in cell A and paired-TSC in cell B

cell B
paired TSC = 0
cell A
paired TSC = 2
cell B
paired TSC = 4
cell A
paired TSC = 2
For internal use
BCSU planning

Per each OSC reporting period a number of OSC calls can start
Starting of an OSC call is done per BCSU
More BCSUs attached means more simultanious call staring

When allocating the BCSUs to the OSC TRXs it is best to have as many
as possible to enhance the amount of OSC simultaneous multiplexing

Keep in mind the load distribution over the BCSUs

For internal use
Handover planning

OSC multiplexing starts every reporting period
OSC ranks the MSs according to quality and level (per BCSU) and
searches for the optimal candidate
When a suitable pair is found the pair are multiplexed
If no suitable pair is found the process stops for this BCSU until the next OSC reporting
period

Meaning that is a mobile is not the 1st in line in the ranking it means that it
will take at least a few OSC reporting rounds before the call will go to OSC
Therefore it is crucial to keep the MSs as much as possible on the cell to
provide the opportunity to go to OSC
The degree of the maintaining the call depends on many things, like
Call duration
Handover / call (trf_13f)
Quality distribution in cell
Blocking in the cell and surrounding
For internal use
Parameter planning

With the OSC parameters you define the working of OSC
OSC works on top of AMR-HR/FR
Meaning that some of the AMR parameters still apply
These parameters are
IHRH, IHRF
Codec settings parameters
AMR-HR load seetings (FRL, FRU, AFRL, AFRU)
For internal use
OSCDHRMultiplexing
RXQualityThr
(ODMQT)
OSCMultiplexingUL
RXLevelWindow
(OMLW)
Multiplexing
OSCMultiplexingUL
RXLevelThr
(OMLT)
trxOSCCapability
(ERO)
General TRX
trxStartingMode
(-)
pcLowerThresholdDL
RXQualDhr
(LDDHR)
POWER CONTROL
pcLowerThresholdUL
RXQualDHR
(LUDHR)
pcUpperThresholdDL
RxQualDhr
(UDDHR)
pcUpperThresholdUL
RxQualDhr
(UUDHR)
DHRLIM (BTS))
LOAD
OSC Parameters (RG20)- Overview
Demultiplexing
OSCDemultiplexingUL
RxLevMargin
(ODMRG)
OSCDhrDemultiplexing
RXQualityThr
(ODDQT)
UL RX Change rate
(0x38)
UTPFIL
UL Rx Level Diff
(0x39)
OSC Modulation loss
(0x3A)
CSDAP Penalty count
(0x3B)
Fast AVE of DHR UL
()
AMR FR DHR MUX
()
AMR FR DHR MUXL
()
CSDAP ID
CSDAP)
circuitGroupNumber
pcmCircuit_ID
firstTSL
LastTSL
PoolSize
bcfAbisIF
bcfTslShift
csDapID
For internal use
Configuration Management
limForTriggeringOscDhr
Multiplexing
Limit for Triggering OSC DHR Multiplexing
object: BTS
unit: %
range: 0..100
step: 1
default: 0
MML command: EQM, EQO
MML abbr. name: DHRLIM
It determines the load threshold for triggering DHR multiplexing: if the
percentage of free FR TCH decreases below the value of this parameter,
DHR multiplexing procedure is attempted.
Default value of the parameter disables DHR multiplexing in a BTS.
To enable the DHR multiplexing the parameter must be set to value
different than zero. Activation of the OSC feature is possible only if:
- BCF site type is Flexi EDGE (version EX4.0)
- Rx diversity is in use in the BTS (parameter RDIV = Y)
- AMR Half Rate (BSS30060) is in use in the BTS: valid license is active
- AMR HR Packing is in use: parameter amrConfHrCodecModeSet >0 and
load limits parameters: FRL & FRU or HRL & HRU (if Load Based AMR
Packing BSS21154 is not active) or AFRL & AFRU or AHRL & AHRU (if Load
Based AMR Packing BSS21154 is active) are appropriately set
- Extra Abis resources are available with Packet Abis or Circuit Switched
Dynamic Abis Pool feature
Setting of Limit for Triggering OSC DHR Multiplexing must be aligned with
setting of lower load limit for AMR HR packing:
Limit for Triggering OSC DHR Multiplexing (A)FRL or (A)HRL
Rule: the higher the value of this attribute, the lower traffic load at which DHR
multiplexing is triggered
For internal use
oscMultiplexingUlRxLevelThr OSC Multiplexing UL Rx Level Threshold
object: HOC
unit: dBm
range: -110..-47
step: 1
default: -85
MML command: EHC, EHS, EHO
MML abbr. name: OMLT
This parameter determines the UL Rx Level criterion for searching
DHR multiplexing candidates (both 1
st
and 2
nd
candidate must fulfill
this criterion).
Only calls with UL Rx level greater than or equal to this threshold
(and lower than -47dBm), can be regarded as DHR multiplexing
candidates.
oscDhrMultiplexingRxQualityThr OSC DHR Multiplexing Rx Quality Threshold
object: HOC
unit: -
range: 0..7
step: 1
default: 0
MML command: EHC, EHQ, EHO
MML abbr. name: ODMQT
This parameter determines the UL and DL Rx Quality criterion for
searching the 1
st
DHR multiplexing candidate (target channel).
Only AMR HR calls with UL and DL Rx quality lower than or equal
to this threshold, can be regarded as the 1
st
DHR multiplexing
candidate (target channel).
For internal use
oscMultiplexingUlRxLevelWindow OSC Multiplexing UL Rx Level Window
object: HOC
unit: dB
range: 0..20
step: 1
default: 10
MML abbr. name: OMLW
This parameter determines the UL Rx Level Difference criterion
for searching the 2
nd
DHR multiplexing candidate (connection to
be handed over to the target channel).
Only AMR FR/HR connections having UL RxLev within the
window defined based on this parameter and UL RxLev of the 1
st

candidate may be regarded as 2
nd
DHR multiplexing candidates.
Multiplexing Window for 2nd
candidate
UL RxLev
1st

RxLev
RxLev
1st
- Window
RxLev
1st
2nd

For internal use
oscDemultiplexingUlRxLevMargin OSC Demultiplexing UL Rx Level Margin
object: HOC
unit: dB
range: 0..63
step: 1
default: 14
MML abbr. name: ODMRG
This parameter determines the UL Rx Level Difference
criterion for DHR demultiplexing HO.
If difference between UL Rx Levels of DHR paired connections
exceeds the value of this parameter, the connection with
higher RxLev is handed over to non-DHR mode.
This parameter should always be set to higher values than
OSC Multiplexing UL Rx Level Window.
oscDhrDemultiplexingRxQualityThr OSC DHR Demultiplexing Rx Quality Threshold
object: HOC
unit: -
range: 0..7
step: 1
default: 3
MML command: EHQ, EHO
MML abbr. name: ODDQT
This parameter determines the UL and DL Rx Quality
thresholds for DHR demultiplexing HO.
If UL or DL Rx quality of DHR connection reaches or exceeds
this threshold, demultiplexing HO to non-DHR mode is
attempted (DHR demultiplexing HO may be prevented if AMR
Unpacking Optimization feature is enabled and RxQual or
RxLev degrades too much).
Setting of this parameter must be consistent with setting of
OSC Multiplexing Rx Quality Threshold.
For internal use
thrDlRxQualDhr Threshold DL RxQual DHR
object: HOC
unit: -
range: 0..7
step: 1
default: 4
MML abbr. name: TDRQD
This parameter determines DL Rx Quality threshold for inter-cell HO
for DHR connections.
If DL RxQual reaches or exceeds this threshold, DHR connection is
handed over to a new cell to non-DHR mode (AMR HR or FR).
Rule: This parameter should always be set to higher value than OSC
Demultiplexing Rx Quality Threshold.
thrUlRxQualDhr Threshold UL RxQual DHR
object: HOC
unit: -
range: 0..7
step: 1
default: 4
MML abbr. name: TURQD
This parameter determines UL Rx Quality threshold for inter-cell HO
for DHR connections.
If UL RxQual reaches or exceeds this threshold, DHR connection is
handed over to a new cell to non-DHR mode (AMR HR or FR).
Rule: This parameter should always be set to higher value than OSC
Demultiplexing Rx Quality Threshold.
For internal use
pcLowerThresholdDlRxQualDhr PC Lower Threshold DL RxQual DHR
object: POC
unit: -
range: 0..7
step: 1
default: 3
MML command: EUC, EUO, EUQ
MML abbr. name: LDDHR
This parameter determines DL Rx Quality threshold for BTS power
increase for DHR connections.
Rule: setting of this parameter should be consistent with setting of
OSC Demultiplexing Rx Quality Threshold, Threshold DL RxQual
DHR and PC Upper Threshold DL RxQual DHR.
Recommendation: it is recommended to set this parameter to
value lower than OSC Demultiplexing Rx Quality Threshold to
trigger power control action before attempting the demultiplexing
HO.
pcLowerThresholdUlRxQualDhr PC Lower Threshold UL RxQual DHR
object: POC
unit: -
range: 0..7
step: 1
default: 3
MML abbr. name: LUDHR
This parameter determines UL Rx Quality threshold for BTS power
increase for DHR connections.
OSC Demultiplexing Rx Quality Threshold, Threshold UL RxQual
DHR and PC Upper Threshold UL RxQual DHR.
Recommendation: it is recommended to set this parameter to
value lower than OSC Demultiplexing Rx Quality Threshold to
trigger power control action before attempting the demultiplexing
HO.
For internal use
pcUpperThresholdDlRxQualDhr PC Upper Threshold DL RxQual DHR
object: POC
unit: -
range: 0..7
step: 1
default: 0
MML abbr. name: UDDHR
This parameter determines DL Rx Quality threshold for BTS power
decrease for DHR connections.
OSC Demultiplexing Rx Quality Threshold, Threshold DL RxQual
DHR and PC Lower Threshold DL RxQual DHR.
pcUpperThresholdUlRxQualDhr PC Upper Threshold UL RxQual DHR
object: POC
unit: -
range: 0..7
step: 1
default: 0
MML abbr. name: UUDHR
This parameter determines UL Rx Quality threshold for BTS power
decrease for DHR connections.
OSC Demultiplexing Rx Quality Threshold, Threshold UL RxQual
DHR and PC Upper Threshold UL RxQual DHR.

For internal use
trxOSCCapability TRX OSC Capability
object: TRX
unit: -
range: 0..4
step: 1
default: 0
MML command: ERO
This parameter indicates whether TRX supports OSC feature.
This is read-only parameter. Its value is set by the system.
Rule:
0 - TRX is not OSC capable
1 - TRX is OSC capable
2 - TRX OSC capability is temporarily lost
3 - TRX is capable of OSC without EGPRS
4 - TRX OSC capability without EGPRS is temporarily lost
trxStartingMode TRX Staring Moode
object: TRX
unit: -
range: 0, 1
step: 1
default: -
This parameter indicates the mode (EGPRS or OSC) in which the
BSC has started the Flexi EDGE TRX. It is used with Flexi EDGE
BTS only. This is read-only parameter. Its value is set by the BSC.
Rule:
0 - EGPRS starting mode, in this mode 1st generation Flexi EDGE
TRX does not support OSC;
1 - OSC starting mode, in this mode 1st generation Flexi EDGE TRX
does not support EGPRS
For internal use
UL RX CHANGE RATE
object: UTPFIL
unit: -
range: 0..63
step: 1
default: 10
number/id: 0x38
This parameter determines the maximum allowed difference between UL RxLev
Change Rates of DHR multiplexing candidates. BSC rejects DHR multiplexing if
UL RxLev Change Rates difference is greater than the value of this parameter.
Rule: the lower the value of this parameter the more stringent criterion for DHR
multiplexing and lower OSC usage. Setting this parameter to higher values may
result in higher number of DHR multiplexing HO but may also lead to increase
of the DHR demultiplexing HO due to UL RxLev Unbalance.
UL RX LEVEL DIFF
object: UTPFIL
unit: dB
range: 0..63
step: 1
default: 0
number/id: 0x39
This parameter allows for adjusting the algorithm for MS Power Optimization in
DHR Multiplexing HO it determines how much initial UL Rx Level of the 2
nd

DHR multiplexing candidate may differ (be higher or lower) from UL RxLev of
the 1
st
DHR multiplexing candidate.
For internal use
OSC MODULATION LOSS
object: UTPFIL
unit: dB
range: 0..63
step: 1
default: 3
number/id: 0x3A
This parameter allows for adjusting the algorithm for BTS Power
Optimization in DHR Multiplexing HO it allows to tune the value of extra
power increase applied in DL during DHR multiplexing HO to compensate
the loss resulting from DHR multiplexing.
CSDAP PENALTY COUNT
object: UTPFIL
unit: -
range: 0..255
step: 1
default: 5
number/id: 0x3B
Amount of multiplexing attempts when CSDAP allocation is avoided after
unsuccessful CSDAP allocation the pairs with the 1
st
candidate having
already been assigned CSDAP resource (OSC-1 sub-channel) are
preferred.
For internal use
FAST AVE OF DHR UL
object: UTPFIL
unit: -
range: 0 (fast averaging disabled)
1 (fast averaging enabled)
default: 1
number/id: tbd
This parameter determines whether fast averaging is used in
UL power control and handover evaluation of DHR
connections.
Since DHR multiplexing may result in significant changes of
Rx quality it is recommended to enable fast averaging for
DHR connections.
AMR FR DHR MUX
object: UTPFIL
unit: -
range: 0 (AMR FR->DHR forbidden)
1 (AMR FR->DHR allowed)
default: 1
number/id: tbd
This parameter allows for preventing AMR FR-to-DHR
multiplexing HO. Direct switching from AMR FR to DHR
mode may result in too high degradation of user perceived
quality. Disabling this type of transition allow avoiding this
potential degradation. On the other hand, preventing AMR
FR-to-DHR multiplexing HO limits the list of multiplexing
candidates what may result in lower DHR utilization.
For internal use
AMR FR DHR MUX
object: UTPFIL
unit: -
range: 0 (AMR FR->DHR forbidden)
1 (AMR FR->DHR allowed)
default: 1
number/id: tbd
This parameter allows for preventing AMR FR-to-DHR
multiplexing HO. Direct switching from AMR FR to DHR
mode may result in too high degradation of user perceived
quality. Disabling this type of transition allow avoiding this
potential degradation. On the other hand, preventing AMR
FR-to-DHR multiplexing HO limits the list of multiplexing
candidates what may result in lower DHR utilization.
For internal use
Parameter name Description
PC Lower Thresholds Lev UL/DL
Rx Level
Determines Rx level threshold for a uplink/downlink power
increase. This also applies to DHR connections.
PC Upper Thresholds Lev UL/DL
Rx Level
Determines Rx level threshold for a uplink/downlink power
decrease. This also applies to DHR connections.
Threshold Level
Uplink/Downlink Rx Level
Determines uplink/downlink Rx level threshold for triggering the
inter-cell handover due to Rx level. This also applies to DHR
connections.
Intra HO Threshold Rx Qual
AMR FR
Determines downlink and uplink Rx quality threshold for the
packing HO (AMR FR to AMR HR). This is also used as a threshold
for 2
nd
DHR multiplexing candidate selection.
There are no new Nx & Px parameters dedicated to DHR mode and the existing ones
related to particular HO and PC procedures are re-used.
For internal use
Parameter name Description
Intra HO Lower Rx Quality Limit
AMR
(AMR Unpacking Optimization
BSS21120)
Determines the limit of the uplink and downlink Rx quality for
quality based intra-cell HOs. If averaged uplink or downlink Rx
quality is higher than this parameter, the quality based intra-cell
HOs are not allowed. This also prevents DHR demultiplexing HO
in poor Rx quality conditions.
Intra HO Lower Rx Level Limit
AMR HR
BSS21120)
Determines the lower limit for uplink and downlink Rx level for
quality based intra-cell HOs for AMR HR mode. If averaged uplink
or downlink Rx level is lower than this parameter, the quality
based intra-cell HOs for AMR HR calls are not allowed. This also
prevents DHR demultiplexing HO in poor Rx level conditions.
Intra HO Upper Rx Level Limit
AMR HR
BSS21120)
Determines the upper limit for uplink and downlink Rx level for
quality based intra-cell HOs for AMR HR mode. If averaged uplink
or downlink Rx level is higher than this parameter, the quality
based intra-cell HOs for AMR HR calls are not allowed. This is
also used to determine the target channel mode (AMR FR or AMR
HR) in DHR demultiplexing HO triggered by Rx quality criterion
if Rx level is higher than this threshold DHR call is demultiplexed
to AMR HR, otherwise to AMR FR.
Rx Level AMR HR Unpacking
Threshold (UTPFIL parameter)
(Improved AMR Packing and
Unpacking BSS21483)
Determines the Rx level threshold for triggering the unpacking HO
- if uplink or downlink Rx level is lower than the value of this
parameter the intra-cell HO from AMR HR to AMR FR is attempted.
This is re-used to trigger also DHR demultiplexing HO. Setting of
this parameter should be aligned with oscMultiplexUlRxLevThr
and oscDemultiplexUlRxLevMarg.
For internal use
id CSDAP ID
object: CSDAP
range: 1..1000
step: 1
MML commands: ESE, ESV, ESM, ESI
MML abbreviated name: ID
CSDAP ID allows to identify the dynamic Abis pool in the BSC. The identification
number must be unique within the BSC.
circuitGroupNumber Circuit group number
object: CSDAP
range: 0..65535
MML commands:
MML abbreviated name:

Note: This is hidden parameter.
Circuit group number identifies the circuit group associated to the CSDAP. Circuit
group (CGR) represents resources available on A interface as well as corresponding
block of memory which BSC SW can recognize and address. During DAP creation
BSC automatically reserves a free circuit group for each CSDAP, the assignment
cannot be modified and BSC SW understands these circuit group numbers rather than
CSDAP IDs. This is read-only parameter as the value is automatically selected during
CSDAP creation.
pcmCircuit_ID PCM Circuit ID
object: CSDAP
range: 0..3391
MML commands: ESE, ESM, ESI, WUP
MML abbreviated name: CRCT

NOTE:
2048..3391 is reserved for T1 (OC-3)
administration area
PCM circuit ID indicates the number of Abis interface line (ET-PCM) where CSDAP is
created.
PCM circuit ID is part of hidden circuit (CRCT) parameter which allows to indicate the
number of PCM line where CSDAP is created as well as the amount of PCM timeslots
from the ET_PCM reserved for the CSDAP. The size of DAP is defined either by
indication of firstTSL and lastTSL or by indication of firstTSL and size of the Abis pool.
Thus circuit can have the following structure:
circuit = pcmCircuit_ID firstTSL lastTSL or
circuit = pcmCircuit_ID firstTSL size
For internal use
lastTSL Last Timeslot
object: CSDAP
range: 1..31 (E1)
1..24 (T1)
MML commands: ESE, ESM, ESI
Last timeslot indicates the position on Abis interface line (defined by means of
pcmCircuit_ID) of the last timeslot of the CSDAP. The parameter is optional as the
size of CSDAP can be also defined explicitly by using parameter pool size (in addition
to first timeslot).
Last timeslot can be modified by entering a new value using parameter
newLastTimeSlot (NLT). By entering a number bigger than the last timeslot the pool
is extended (by adding some timeslots on at the end of the pool), by entering a
number smaller than the last timeslot the pool is got shrunk (by removal some
timeslots at the end of the pool).
firstTSL First Timeslot
object: CSDAP
range: 1..31 (E1)
1..24 (T1)
First timeslot indicates the position on Abis interface line (defined by means of
pcmCircuit_ID) of the first timeslot of the CSDAP.
This parameter can be modified by entering a new value using parameter
newFirstTimeSlot (NFT). By entering a number smaller than the first timeslot the pool
is extended (by adding some timeslots on to the beginning of the pool), by entering a
number bigger than the first timeslot the pool is got shrunk (by removal some timeslots
from the beginning of the pool).
poolSize Pool size
object: CSDAP
range: 1..31 (E1)
1..24 (T1)
MML commands: ESE, ESI
Pool size defines the size of the CSDAP. The parameter is optional as it can be
replaced with the parameter last timeslot.
For internal use
bcfAbisIF BCF Abis IF
object: CSDAP
range: 1..16
MML abbreviated name: BAIF
BCF Abis interface allows to define at BCF side the number of Abis interface line
where the CSDAP is created.
bcfTslShift BCF Timeslot Shift
object: CSDAP
range: -30..30
default: 0
Step: 1
MML abbreviated name: SHIFT
BCF timeslot shift allows to define the offset between ET-PCM timeslots in BSC side
and Abis IF timeslots in BCF side
csDapId1..4 Attached CSDAP1..4
object: BCF
range: 1..1000
MML command: EFC, EFO, EFM
MML abbreviated name: CSDAP1..4
Attached CSDAP1..4 indicates the number of CSDAP attached to the given BCF.
Up to 4 CSDAPs can be attached to BCF (but a single CSDAP can be connected to
only one BCF).
For internal use
Good values to start a pilot
During different projects it has been seen that the following
parameter sets is working well and could be used as starting
point
parameter
name
value
DHRLIM 10
OMLT -85 dBm
ODMQT 1
OMLW 10 dB
ODMRG 14 dB
ODDQT 5
TDRQD 6
TURQD 6
LDDHR 3
LUHDR 3
UDDHR 1
UUDHR 1

For internal use
OSC in MML
For internal use
OSC support for Epsilon TRX of Flexi EDGE BTS
New TRX radio network object parameters

ZERO:BTS=1;

BSC DEBORAH 2010-11-09 17:25:58

TRANSCEIVER DATA

ADM.STATE OP.STATE
--------------------------------------
BCF-0001 UNLOCKED WO
SEG-0001
BTS-0001 UNLOCKED WO
TRX-001 EDGE UNLOCKED WO
BCSU-0

GTRX N
ETRX N HRS Y PREF N
DFCA N DTRX DISABLED

FREQ 693 TSC 0 FRT 0 (REGULAR) LEV N (NOT USED)

DAL N (NOT USED) DAP N (NOT USED) LEVD N (NOT USED)
DDU INDEPENDENT SDG -

OSC 3 (SUPPORTED, NO EGPRS) TRX STARTING MODE 0 ( EGPRS)
SIGN 0 RFHA Y

D-CH TELECOM LINK SET 10 D35T1

RTSL PCM-TSL SUB_TSL TYPE I.LEV ADM.STATE OP.STATE CH.STATUS
------------------------------------------------------------------------------
0 35 - MBCCHC - UNLOCKED WO
1 35- 1 1 TCHD 0 UNLOCKED WO ID ID

TRANSCEIVER HAS NO INTERFERING CELLS
For internal use
OSC support for Epsilon TRX of Flexi EDGE BTS
New TRX radio network object parameters
ERO:BTS=301,TRX=1:;

BSC3i BSC24 2011-05-10 13:37:45

TRANSCEIVER DATA

ADM.STATE OP.STATE
--------------------------------------
SEG-0301 ESATERI241
BTS-0301 ESATERI241 UNLOCKED WO
BCSU-0

GTRX Y (EDGE CS3 & CS4)
ETRX N HRS Y PREF P
DFCA N


DAL N (NOT USED) DAP 300 LEVD N (NOT USED)

OSC 1 (SUPPORTED) TRX STARTING MODE 0 ( EGPRS)
SIGN 0 RFHA Y

D-CH TELECOM LINK SET 15 T3001

------------------------------------------------------------------------------
0 515 - MBCCH - UNLOCKED WO
1 515 - SDCCH - UNLOCKED WO

For internal use
operation
How to monitor
number of busy DHR connections / DHR call pairs on different object
levels are seen with ZEEI, ZEEL and ZERO commands
OSC DHR multiplexing can be verified with the performance
measurement counters of the feature
particularly the counters in Traffic Measurement, Resource Availability
Measurement and Handover Measurement
Alarms related to the feature give indications of problems in running of
the feature

For internal use
Reference: MML (ZEEL)

ZEEL;

LOADING PROGRAM VERSION 23.59-0

BSC3i BSC24 2011-05-11 09:52:33

BSC NETWORK INFORMATION:

BUSY FULL RATE .............. 1
BUSY HALF RATE .............. 0
BUSY DOUBLE HALF RATE ....... 0
BUSY SDCCH .................. 0
IDLE FULL RATE .............. 187
IDLE HALF RATE .............. 296
IDLE SDCCH .................. 208
BLOCKED RADIO TIME SLOTS .... 203
GPRS TIME SLOTS ............. 24
BUSY DTM FULL RATE .......... 0
BUSY DTM HALF RATE .......... 0
IDLE DTM HALF RATE .......... 0

COMMAND EXECUTED

For internal use
Reference: MML (ZEEI)

EEI:BTS=301;

BSC3i BSC24 2011-05-11 09:56:46
RADIO NETWORK CONFIGURATION IN BSC:
E P B
F T R C D-CHANNEL BUSY
AD OP R ET- BCCH/CBCH/ R E S O&M LINK HR FR
LAC CI HOP ST STATE FREQ T PCM ERACH X F U NAME ST DHR /GP
===================== == ====== ==== == ==== =========== = = == ===== == === ===

BCF-0300 FLEXI EDGE U WO 0 BC300 WO
00024 24301 BTS-0301 U WO 0 0
ESATERI241 RF/- 0 1
TRX-001 U WO 638 0 515 MBCCH P 0
TRX-002 U WO 874 0 515 0
TRX-003 U WO 878 0 515 0
TRX-004 U WO 881 0 515 0

COMMAND EXECUTED
For internal use
Reference: MML (ZERO)

ADM.STATE OP.STATE
--------------------------------------
SEG-0174 ALISSIDAU
BTS-0174 ALISSIDAU UNLOCKED WO
BCSU-2

GTRX Y (EDGE)
HRS Y PREF N


DAL N (NOT USED) DAP 1 LEVD N (NOT USED)

OSC 1 (SUPPORTED) TRX STARTING MODE 0 ( EGPRS)
SIGN 0

D-CH TELECOM LINK SET 800 T0879

------------------------------------------------------------------------------
0 575- 15 0 TCHD 1 UNLOCKED WO HR HR
1 575- 15 1 TCHD 0 UNLOCKED WO HR HR HR
2 575- 15 2 TCHD 0 UNLOCKED WO FR
5 575- 16 1 TCHD 0 UNLOCKED WO HR HR HR

For internal use
Optimization
For internal use
Module description
This module will discuss:
High level DHR process with the counters
New counters for DHR
New KPIs for DHR
Optimization of DHR

For internal use
Process high level
Free TCH
DHR Limit For
FR TCH
Resources
Search
candidates
Candidates
Found?
Legacy
Abis?
Search
CSDAP
Start
multiplexing
HO to chosen
TCH
Legacy
Abis?
Activate
CSDAP
OSC call
conversion
done
011263
011264
011265
004235
51013
51014
011266
011267
011266 011267
004237
51216
DHR_MULTIPLEXING_
ATTEMPTS
DHR_MPLX_FAIL_DUE_
TCH_RES
CSDAP_RES_ALLOC_ATT_FOR_DHR
HO_ATTEMPT_FROM_AMR_
HR_TO_DHR
HO_FROM_AMR_HR_TO_DHR_SUCC
INTRA_HO_FROM_AMR_HR_TO_DHR
011266
yes
yes
no
no
For internal use
connection
In defined
Window?
Call conversion to OSC Legacy Abis
F
r
e
e

T
C
H

D
H
R

L
i
m
i
t

F
o
r

F
R

T
C
H

R
e
s
o
u
r
c
e
s

Call in
AMR-HR?
UL
level a
UL&DL
quality b
yes yes
2nd Call in
AMR
(FR-HR)?
UL&DL
lev a
UL&DL
qual
IHRF
yes yes
CSDAP
Found?
S
t
a
r
t

o
f

m
u
l
t
i
p
l
e
x
i
n
g

Channel
activation
Success?
H
O

c
o
m
m
a
n
d

T
o

m
o
v
i
n
g

c
a
l
l

HO
successful?
A
c
t
i
v
a
t
e

C
S
D
A
P

2

w
a
y
s

CSDAP
activation
successful?
4
2
3
7
/
5
1
2
1
6

A = OSC Multiplexing UL Rx Level Threshold
B = OSC DHR Multiplexing Rx Quality Threshold
Window = multiplexing window (c) =
Rxlev1-window < rxlev2 < rxlev1 +window+ max pwr red
Searching for OSC-0
C
a
n
d
i
d
a
t
e

f
o
u
n
d

no no no
yes
Searching for OSC-1
Pair found
004235
yes
yes
no
004239
Intra-cell HO
counters
011266
no
011263
A
c
t
i
v
a
t
e

C
S
D
A
P

1
w
a
y

O
S
C

s
t
a
r
t
e
d

yes
yes
011266 011267
Balance the
Call to same
RXLevel
011265
011264
* Find resources
From USC connection
With CSDAP
011267
Send over air interface
Counter
Legacy Abis processes
51013
51014
1266
end
Balance system
Power commands
yes
*
no
no
For internal use
BSS21309: Orthogonal subchannel with SAIC MS
OSC_AMR_HR_475_UL_RXQUAL_0 122000
OSC_AMR_HR_475_DL_RXQUAL_0 122001






122 OSC RX Quality measurement collects statistics of
received signal quality both in uplink and downlink directions
for each AMR HR bit rate for double half rate calls. The
information is collected from each transceiver (TRX)
separately.
The Bit Error Ratio (BER) based signal quality counters
correspond to the eight RX Quality bands. The counters are
updated by the RX Quality values as measured by the MS
(downlink) and BTS (uplink) and reported in the radio link
measurement messages. The RX Quality reports are
collected on the traffic channels (TCHs).
KPIs:
OSC DL/UL
Rx Quality
Distribution
1 Traffic Measurement
DHR_MULTIPLEXING_ATTEMPTS 001263
DHR_MULTIPLX_FAIL_DUE_TCH_RES 001264
CSDAP_RES_ALLOC_ATT_FOR_DHR 001265
DHR_MPLX_FAIL_DUE_CSDAP_RES 001266
DHR_MPLX_FAIL_DUE_OTHER 001267

2 Resource Availability Measurement
AVE_BUSY_DHR_TCH 002094
AVE_BUSY_DHR_TCH_DENOM 002095
PEAK_BUSY_DHR_TCH 002096

4 Handover Measurement
HO_ATTEMPT_FROM_AMR_HR_TO_DHR 004235
HO_ATTEMPT_FROM_AMR_FR_TO_DHR 004236
HO_FROM_AMR_HR_TO_DHR_SUCC 004237
HO_FROM_AMR_FR_TO_DHR_SUCC 004238
UNSUCC_HO_TO_DHR_DUE_MISMATCH 004239
HO_ATT_FROM_DHR_DUE_RX_QUAL 004240
HO_ATT_FROM_DHR_DUE_RXLEV_DIF 004241
HO_FROM_DHR_DUE_RX_QUAL_SUCC 004242
HO_FROM_DHR_DUE_RXLEV_SUCC 004243
HO_ATT_FROM_DHR_DUE_RX_LEV 004251
HO_FROM_DHR_DUE_RX_LEV_SUCC 004252

BSS21309: Orthogonal subchannel with SAIC MS introduce a set of counters in 1
Traffic Measurement 2 Resource Availability Measurement and 4 Handover
Measurement for feature performance monitoring.
KPIs:
Total DHR Multiplexing Failure Rate
DHR Multiplexing Failure Rate due to Lack of Suitable Pair
DHR Multiplexing Failure Rate due to CSDAP
DHR Multiplexing Failure Rate due to Other Reasons
CSDAP Allocation Failure Rate
KPIs:
AMR HR-to-DHR HO Success Rate
AMR HR-to-DHR HO Rate
AMR FR-to-DHR HO Success Rate
AMR FR-to-DHR HO Rate
RxQual DHR Demultiplexing HO
Success Rate
UL RxLev Difference DHR
Demultiplexing HO Success Rate
RxLev DHR Demultiplexing HO Success
Rate
DHR Demultiplexing HO Success Rate
DHR Demultiplexing HO type (due to
RxQual) Distribution
DHR Demultiplexing HO type (due to UL
RxLev difference) Distribution
DHR Demultiplexing HO type (due to
RxLev) Distribution

KPI s:
Average DHR Traffic
DHR Usage
For internal use
KPIs for Orthogonal Sub-channel

KPI Formula Meaning
Average DHR Traffic
AVE_BUSY_DHR_TCH/AVE_BUSY_DHR
_TCH_DENOM
Indicates number of Erlangs
served by DHR TCH
DHR Usage
Average DHR Traffic/ trf_1 Indicates the portion of traffic
served on DHR TCH
Total DHR
Multiplexing Failure
Rate
SUM_OF_DHR_MULTIPLEXING_FAILUR
ES/DHR_MULTIPLEXING_ATTEMPTS
where
SUM_OF_DHR_MULTIPLEXING_FAILUR
ES=(DHR_MPLX_FAIL_DUE_TCH_RES+
DHR_MPLX_FAIL_DUE_CSDAP_RES+
DHR_MPLX_FAIL_DUE_OTHER)
Gives failure rate of multiplexing
AMR calls to DHR as the ratio
between failed multiplexing HOs
and number of multiplexing
attempts
DHR Multiplexing
Failure Rate due to
Lack of Suitable Pair
DHR_MPLX_FAIL_DUE_RES (1264)/
DHR_MULTIPLEXING_ATTEMPTS (1263)
AMR calls to DHR caused by lack
of suitable pair (pair of
connections fulfilling DHR
multiplexing criteria)
DHR Multiplexing
Failure Rate due to
lack of CSDAP
DHR_MPLX_FAIL_DUE_CSDAP_RES
(1266)/DHR_MULTIPLEXING_ATTEMPTS
(1263)

AMR calls to DHR caused by lack
of CSDAP
DHR Multiplexing
Failure Rate due to
Other Reasons
DHR_MPLX_FAIL_DUE_OTHER (1267)/
DHR_MULTIPLEXING_ATTEMPTS (1263)
AMR calls to DHR caused by
unsuitable state of the call (e.g.
OSC HO is started by RRM that is
not aware of the call phase and
might end up to situation where
OSC HO is interrupted.
For internal use

KPI Formula Meaning
CSDAP
Allocation
Failure Rate
DHR_MPLX_FAIL_DUE_CSDAP_RES/CSDAP
_RES_ALLOC_ATT_FOR_DHR
Gives the CSDAP Allocation
Failure ratio due to lack of CSDAP
for OSC-1 subchannel
AMR HR-to-DHR
HO Success
Rate
HO_FROM_AMR_HR_TO_DHR_SUCC/HO_A
TTEMPT_FROM_AMR_HR_TO_DHR
Gives success rate of multiplexing
AMR HR calls to DHR as the ratio
between succesful multiplexing
HOs from AMR HR to DHR and
number of multiplexing attempts
AMR HR-to-DHR
HO Rate
HO_ATTEMPT_FROM_AMR_HR_TO_DHR/(H
O_ATTEMPT_FROM_AMR_HR_TO_DHR+
HO_ATTEMPT_FROM_AMR_FR_TO_DHR)
Gives the percentage of AMR HR-
to-DHR HO Attempts
AMR FR-to-DHR
HO Success
Rate
(HO_FROM_AMR_FR_TO_DHR_SUCC/HO_A
TTEMPT_FROM_AMR_FR_TO_DHR
Gives success rate of multiplexing
AMR FR calls to DHR as the ratio
between succesful multiplexing
HOs from AMR FR to DHR and
number of multiplexing attempts
AMR FR-to-DHR
HO Rate

HO_ATTEMPT_FROM_AMR_FR_TO_DHR/(H
O_ATTEMPT_FROM_AMR_HR_TO_DHR+
HO_ATTEMPT_FROM_AMR_FR_TO_DHR)
Gives the percentage of AMR FR-
to-DHR HO Attempts
For internal use

KPI Formula Meaning
RxQual DHR
Demultiplexing
HO Success
Rate
HO_FROM_DHR_DUE_RX_QUAL_SUCC/HO
_ATT_FROM_DHR_DUE_RX_QUAL
Gives success rate of
demultiplexing DHR calls to AMR
HR or FR due to RxQual as the
ratio between succesful
demultiplexing HOs due to quality
and number of demultiplexing
attempts with the same cause
UL RxLev
Difference DHR
Demultiplexing
HO Success
Rate
HO_FROM_DHR_DUE_RXLEV_SUCC/HO_A
TT_FROM_DHR_DUE_RXLEV_DIFF
HR or FR due to UL RxLev
difference as the ratio between
succesful demultiplexing HOs due
to UL RxLev and number of
demultiplexing attempts with the
same cause
RxLev DHR
Demultiplexing
HO Success
Rate
HO_FROM_DHR_DUE_RX_LEV_SUCC/HO_
ATT_FROM_DHR_DUE_RX_LEV
HR or FR due to UL RxLev
difference as the ratio between
succesful demultiplexing HOs due
to UL RxLev and number of
demultiplexing attempts with the
same cause
DHR
Demultiplexing
HO Success
Rate
(HO_FROM_DHR_DUE_RX_QUAL_SUCC+
HO_FROM_DHR_DUE_RXLEV_SUCC +
HO_FROM_DHR_DUE_RX_LEV_SUCC)/(
HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_
ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_A
TT_FROM_DHR_DUE_RX_LEV)
HR or FR as the ratio between
succesful demultiplexing HOs and
number of demultiplexing
attempts
For internal use

KPI Formula Meaning
DHR
Demultiplexing
HO type (due to
RxQual)
Distribution
HO_ATTEMPT_FROM_DHR_DUE_TO_RXQU
AL /
(HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_
ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_AT
T_FROM_DHR_DUE_RX_LEV)

Gives the ratio of demultiplexing
HO attempts due to RxQual in the
all causes of demultiplexing
DHR
Demultiplexing
HO type (due to
UL RxLev
difference)
Distribution
HO_ATT_FROM_DHR_DUE_RXLEV_DIFF /
T_FROM_DHR_DUE_RX_LEV )

HO attempts due to UL RxLev
difference in the all causes of
demultiplexing
DHR
Demultiplexing
HO type (due to
RxLev)
Distribution
HO_ATT_FROM_DHR_DUE_RX_LEV /
T_FROM_DHR_DUE_RX_LEV)
HO attempts triggered by Rx
Level criterion (when Improved
AMR Packing and Unpacking
(BSS21483) is active) in the all
causes of demultiplexing

Average CSDAP
8kbit/s subTSL
Usage
AVERAGE_CSDAP_SUBTSL_USAGE/AVERA
GE_CSDAP_SUBTSL_USAGE_DEN
Gives the average usage of
CSDAP 8kbit/s subTSL
Peak CSDAP
utilization
PEAK_CSDAP_8_KBIT/S_SUBTSL_USAGE /
TOTAL_PCM_8_KBIT/S_SUBTSL_IN_CSDAP
Gives the peak utilization of
CSDAP resources
For internal use

KPI Formula Meaning
UL RxQual
distribution
E.g.
[(OSC_AMR_HR_475_UL_RXQUAL_6+OSC_
AMR_HR_515_UL_RXQUAL_6+OSC_AMR_H
R_590_UL_RXQUAL_6+OSC_AMR_HR_670_
UL_RXQUAL_6+OSC_AMR_HR_740_UL_RX
QUAL_6)+(OSC_AMR_HR_475_UL_RXQUAL
_7+OSC_AMR_HR_515_UL_RXQUAL_7+OS
C_AMR_HR_590_UL_RXQUAL_7+OSC_AMR
_HR_670_UL_RXQUAL_7+OSC_AMR_HR_74
0_UL_RXQUAL_7)] /
[(OSC_AMR_HR_475_UL_RXQUAL_0+OSC_
QUAL_0)+
+(OSC_AMR_HR_475_UL_RXQUAL_7+OSC_
QUAL_7)]
Gives the ratio of samples with
given RxQual value to all samples
in UL, e.g. UL Rxqual 6&7 Rate
All AMR codecs are included in the formula not only the active ones
For internal use

KPI Formula Meaning
DL RxQual
distribution

E.g.:
[(OSC_AMR_HR_475_DL_RXQUAL_6+OSC_A
MR_HR_515_DL_RXQUAL_6+OSC_AMR_HR
_590_DL_RXQUAL_6+OSC_AMR_HR_670_D
L_RXQUAL_6+OSC_AMR_HR_740_DL_RXQ
UAL_6)+(OSC_AMR_HR_475_DL_RXQUAL_7
+OSC_AMR_HR_515_DL_RXQUAL_7+OSC_
AMR_HR_590_DL_RXQUAL_7+OSC_AMR_H
R_670_DL_RXQUAL_7+OSC_AMR_HR_740_
DL_RXQUAL_7)] /
[(OSC_AMR_HR_475_DL_RXQUAL_0+OSC_
DL_RXQUAL_0+OSC_AMR_HR_740_DL_RX
QUAL_0)+
+(OSC_AMR_HR_475_DL_RXQUAL_7+OSC_
DL_RXQUAL_7+OSC_AMR_HR_740_DL_RX
QUAL_7)]
Gives the ratio of samples with
given RxQual value to all samples
in DL, e.g. DL Rxqual 6&7 Rate

All AMR codecs are included in the formula not only the active ones
For internal use
Main drivers for getting OSC traffic
#BCSU/BTS
For internal use
OSC optimization - DHRLIM
DHRLIM is the load threshold that defines when the OSC mechanism
should start
The DHRLIM should be smaller or equal to (A)FRL or (A)HRL
In the graph the DHRLIM has been changed from 10 to 50
For internal use
OSC optimization - Multiplexing attempts

Multiplexing attempts
Multiplexing attempts are showing how many possible candidates are
available for OSC
For internal use
OSC optimization - OMLT
The OMLT defines the maximum level that the OSC
mechanism is searching for a candidate (both pairs)
In the bellow figure the OMLT has been changed from -85dBm
to -95dBm
For internal use
OSC optimization - ODMQT
OMDQT controls the quality for the OSC calls to be
multiplexed together with the IHRF (Intra HO threshold
RXQuality AMR FR).
Default value is 1 and is good value to start with. ODMQT
should be at least same or smaller value than the IHRF
UL0 UL1 UL2 UL3 UL4 UL5 UL6 UL7
sum 85,9 3,0 2,6 1,9 1,1 0,5 0,3 0,1
For internal use
OSC optimization - ODMRG
With ODMRG the demultiplexing level difference is changed.
Meaning how far are we letting the mobiles drift before disconnecting
them.
The default value is 14dB.
This parameter should be especially looked at if the quality is
good and the demultiplexing reason is more than 30% due to
window difference.

For internal use
OSC optimization other parameters
ODDQT
This is the demultiplexing based on quality
default value is 3. In the pilot / projects it has been set to 5 without any
problems
Setting it to higher value will keep the calls longer in OSC until
They pass the quality threshold
Make an external handover
Disconnect / drop
TDRQT / TURQT
Inter cell HO for DL / UL has been set to 6 and was not providing
problems.
Default value is 4.

For internal use
Rxquality changes
Quality distribution
The quality of the DHR will or will not be seen in the KPIs
This depends on the DHR share out of total AMR-HR
In general there are two possibilities, which one is more common?

For internal use
Rxquality changes
Quality is most likely to improve if looking at the UL quality
distribution of the AMR and OSC in relation to AMR
AMR degrades slightly due to the OSC calls (from AMR-HR) are the
best in the cell and are not longer updateing the AMR distribution
Due to OSC there is more room on the cells and the MSs are staying
in the dominance area rather than going to non optimal cell due to
congestion
For internal use
Rxquality changes BH
Rxquality distibution in BH cluster level
For internal use
KPIs to follow during OSC project
SAIC Penetration c1263 DHR MULTIPLEXING ATTEMPTS
SAIC Traffic share (1 hour meas time) Successful OSC multiplexing HOs
trf_202/ Average CS Traffic (Erl) hfr_1000/ Total DHR Multiplexing Failure Rate
blck_8i/ TCH call blocking hfr_1001/ DHR Multiplexing Failure Rate due to Lack of Suitable Pair
dcr_8i/ TCH drop call ratio, after TCH assignment, without RE hfr_1002/ DHR Multiplexing Failure Rate due to CSDAP
blck_5b/ SDCCH blocking on, before FCS hfr_1003/ DHR Multiplexing Failure Rate due to Other Reasons
trf_122a/ TCH traffic share of HR AMR calls ho_1000/ AMR HR-to-DHR HO Rate
trf_197/ TCH capacity usage by CS traffic (%) hsr_1000/ AMR HR-to-DHR HO Success Rate
trf_81/TCH free margin ho_1001/ AMR FR-to-DHR HO Rate
dlq_2a/ Bad DL cumulative quality ratio % in classes 5,6,7 hsr_1001/ AMR FR-to-DHR HO Success Rate
dlq_1000/ Bad DL cumulative quality ratio for OSC % in classes 5,6,7 DHR demultiplexing attempts
ulq_2a/ Bad UL cumulative quality % in class 5,6,7 Successful OSC demultiplexing HOs
ulq_1000/ Bad UL cumulative quality ratio for OSC % in classes 5,6,7 hsr_1005/ DHR Demultiplexing HO Success Rate
DL RX-LEVEL distribution OSC mux HOs per demux HOs
UL RX-LEVEL distribution hsr_1002/ RxQual DHR Demultiplexing HO Success Rate
pwr_1/MS Average power (dbm) ho_1002/ RxQual DHR Demultiplexing HO share
trf_2d/ Average call length (sec) hsr_1003/ UL RxLev Difference DHR Demultiplexing HO Success Rate
ho_24/ Intra-cell HO attempts ho_1003/ UL RxLev Difference DHR Demultiplexing HO share
Intra cell HO per traffic hsr_1004/ RxLev DHR Demultiplexing HO Success Rate
hsr_9a/ Intra-cell TCH-TCH HO success ratio ho_1004/ RxLev DHR Demultiplexing HO share
c4142 HO ATT FOR AMR TO HR hfr_1004/ CSDAP Allocation Failure Rate
c4143 HO ATT FOR AMR TO FR CSDAP Size
ava_44/ Average available area level PS territory size for nTRXs Average CSDAP 8kbit/s subTSL Usage
blck_30/ Territory upgrade rejection due to CSW Peak CSDAP 8kbit/s subTSL Usage
tbf_38d/ Average number of DL TBFs per timeslot Peak CSDAP Utilization
trf_473/ DHR Usage ho_11/ Outgoing inter-cell HO attempts
trf_472/ Average DHR traffic ho_13h/ HO attempts, outgoing and intracell
Peak Busy DHR TCH ho_65/ Total HO success ratio, ISHO excluded
hsr_6a/ BSC controlled outgoing TCH-TCH HO success ratio hsr_28/ Total HO Success Rate, ISHO included
For internal use
Alarms
With OSC a few new and changed alarms have been defined and should be
followed.
3536 CIRCUIT SWITCHED DYNAMIC ABIS POOL FAILURE
CSDAP has encountered a malfunction and it has been taken out of use for a
penalty period. BSC sets penalty for a certain CSDAP in case of consecutive
remote transcoder failures and hunting error(s).
7793 ORTHOGONAL SUB CHANNEL ACTIVATION FAILURE
Several consecutive OSC multiplexing attempts have failed due to channel
activation failure in a TCH. The BSC has interrupted OSC multiplexing activity in the
TRX. Failures due to CSDAP problems excluded.
7741 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD
The mean holding time on the channel specified exceeds the operator-defined
threshold during the measurement period. The alarm is used to supervise the
functioning of the traffic and signaling channels. It reveals unreleased calls.
7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD
Mean holding time on a channel is below the operator-defined minimum during the
measurement period. The alarm is used to supervise the functioning of traffic
channels and to detect the possible faulty channels.

For internal use
Test cases
For internal use
Project setup
The following competences are need for the trial
1 x (Technical) project manager
1-2 x Radio engineer (depending on the size of project and if SDC is
used or not)
1 x Access transmission engineer (optional initially 100%, later
maybe 10% (please evaluate)
1 x BSC engineer
SDC for post processing PM and CM data
tools are in-house tool for post processing data
drive test team + analysis (optional)

For internal use
Project duration
0
th
week
Site selection (customer of own team) and test preparation together with the data (initial parameters for OSC & CSDAP or
PacketAbis)
1
st
week
Initial baseline performance verification
Resources: 1 Radio engineer, FM team, SDC for performance data (OSS + FM) analysis and reporting (if not done locally)
Tools: BSS RS, FM logging tools (no special requirements, NEMO + optionally MOS capability if required), FM post-
processing tool (comes along with SDC supporting the post-processing)
2
nd
week
Activation of OSC
Post-implementation functionality and performance verification
Resources: 1 Radio engineer, FM team, SDC for performance data (OSS + FM) analysis and reporting (if not done locally),
+ 1 Access TRS engineer (optionally in case of issues with Abis, etc.)
3
rd
6
th
week
Tuning and performance verification
Reporting
Resources: 1 Radio engineer, FM team, SDC for performance data (OSS + FM) analysis and reporting (if not done locally)

For internal use
Test cases
BTSs can be grouped in accordance to the strategy. It is good to follow the BTSs
individually and tune the parameters (described later) in order to reach the strategy
General test cases
OSC activation with CSDAP / PacketAbis
CSDAP verification
TRXSIG verification
PacketAbis activation (optional)
Blocking cells (TCH blocking) optimizing by changing the parameters
Low blocking (< 10%)
High blocking (> 10%) if applicable, requires also checking of the environment in
order to get the blocking down. there is a chance that OSC will not be able to drop
the blocking completely if the HOs are not working properly
increase PS performance (restriction on territory upgrade) optimizing by changing
the parameters
With blocking
Without blocking
Shutdown TRX(s) optimizing by changing the parameters

For internal use
OSC feature test cases
OSCP1: Potential OSC utilization estimation
OSCP2: Baseline KPI collection with RG20(BSS)
OSCP3: Baseline drive test with RG20(BSS) during busy hour
OSCP4: OSC activation with CSDAP
OSCP5: OSC drive test during busy hour
OSCP6a: OSC performance in cell with blocking (capacity increase gain)
OSCP6b: OSC performance with optimized parameters in cell with blocking
OSCP7a: OSC impact on used radio tsls (reduce configuration gain)
OSCP7b: OSC impact on used radio tsls with optimized parameters
OSCP7c: OSC performance with reduced capacity with optimized parameters
OSCP8a: OSC impact on PS performance (increased PS performance gain)
OSCP8b: OSC impact on PS performance with optimized parameters
OSCP9: CSDAP dimensioning verification

For internal use
References
Planning and optimization guideline :
https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D430224871
OSC parameter settings:
OSC activation trial report Bali
GC Zain :
OSC pilot report India

For internal use
OSC related items
For internal use
Compressed Abis mapping)
usage of compressed Abis mapping also has some undesired effects therefore
should be used only when necessary
it reduces radio capacity of the cell (for non-BCCH TRX, for details
please refer to https://sharenet-
ims.inside.nokiasiemensnetworks.com/Open/409812699) but this
should be overcompensated by OSC calls (depends on CSDAP size
and radio conditions)
it requires more operational effort than standard mapping
Dynamic Abis Compresses Abis
For internal use
Usage of Packet Abis simplifies OSC configuration to the far extent since no
specific planning or configuration on Abis is necessary (neither to user traffic
nor to signaling traffic)
this is because with Packet Abis no resources need to be reserved for any type of
traffic and available bandwidth is shared dynamically between U-, C- and M-planes
based on the actual demand
therefore Abis planning activities related to implementation of OSC in Packet
Abis are also simplified in comparison to Dynamic Abis and only consist in Abis
bandwidth estimation (for U- and C-planes) with properly chosen set of
codecs:
Abis bandwidth estimation is normal business for Packet Abis regardless on whether OSC
is enabled or not
OSC codecs penetration rates must be taken into account
impact of OSC is already included in Packet Abis dimensioning methodology and relevant
tools (see next slide)
for description of Packet Abis dimensioning methodology please refer to: https://sharenet-
ims.inside.nokiasiemensnetworks.com/Open/D417347304

Packet Abis - overview
For internal use
The screenshots below show the set of inputs in Packet Abis calculator which are directly
related to OSC

Apart from these Packet Abis calculator has other sections to define the remaining aspects
related to Packet Abis dimensioning (e.g. physical realization of Packet Abis)
Note: explanations of these additional parameters is part of description of Packet Abis
dimensioning methodology
This section allows to define
BTS HW configuration, i.e.
#TRX per cell as well as
#RTSL dedicated for signaling
and PS
In this section it is possible to
define the actual cell load or
to compute the maximum.
e.g. here it is possible to define
OSC load or penetration
(depending on whats given)
This section allows to define
codec distribution
Note: contributions of standard
HR codecs as well as OSC-HR
are to ne entered in column HR
Packet Abis - calculator
For internal use
Bandwidth required by Packet Abis for given traffic profile also depends on used protocol
stack (i.e. physical realization of Packet Abis) however the trends are similar for both
implementations: examples below are on the basis of Packet Abis over TDM
Examples
CS/PS traffic maintained after introduction of OSC:

CS traffic increase due to higher OSC penetration:
site configuration: 3 TRX/cell, 3 BCCH+SDCCH/cell, 1 CDED/cell, 20 MB/BH/cell
codec penetration: 60% FR / 40% HR (wo. OSC) => 16.37 Erl/cell

Calculations:
Dynamic Abis: 18 TSL (TCH), 5 TSL (sign; 9 TRXSIG@32+OMUSIG@32), 6 TSL (EDAP)
=> 1 E1 line (29 TSL)
Packet Abis: 1.31 Mbps
60% FR / 20% HR / 20% OSC (with OSC) => 16.37 Erl/cell

Dynamic Abis: 2 TSL (CSDAP) + 29 TSL (TCH+sign+EDAP)
=> still 1 E1 (31 TSL) but fully loaded E1 (!!!)

=> still 1 E1 (31 TSL) but fully loaded E1 (!!!)

=> 2 E1 (35 TSL) already needed (!!!)
=> compressed mapping to be checked
Packet Abis: 1.51 Mbps (still a lot of space for more traffic)
Packet Abis example calculations
Please note that Packet Abis bandwidth values below are only examples given to illustrate
quantitatively the possible impact of OSC on backhaul bandwidth. These values are early estimations
and must be currently interpreted as a design target rather than the binding indication!!! Therefore the
figures related to Packet Abis must not be used for contractual commitment or customer presentations.
Please refer to NEI Packet Abis for further details concerning Packet Abis bandwidth estimations (incl.
the most up-to-dated results of bandwidth estimation).
For internal use
Traffic increase caused by introduction of OSC is reflected in greater
consumption of Packet Abis bandwidth
Packet Abis bandwidth must be re-evaluated taken into account expected
OSC penetration and related traffic increase
bandwidth related to both U-plane and C-plane will be affected due to
introduction of OSC
Packet Abis planning procedure is the same regardless on whether OSC is
enabled or not
for Packet Abis result of planning procedure is the same with and without OSC
(i.e. bandwidth)
for Dynamic Abis there is specific DAP which is only needed when OSC is
enabled
Packet Abis summary
For internal use
For internal use
Prerequisites (1)
Features being prerequisites for OSC Half Rate with SAIC MS (BSS21309)
activation
AMR Half Rate (BSS30060); valid license is active and
parameter amrConfHrCodecModeSet (HRC) 0 and
0 <amrSegLoadDepTchRateLower(AFRL)
amrSegLoadDepTchRateUpper(AFRU) or
0 <amrLoadDepTchRateLower(AHRL) amrLoadDepTchRateUpper(AHRU) (if
segment level control is deactivated)
other AMR HR related parameters like e.g. PC and HO thresholds, must be
configured appropriately
Rx Diversity (BSS01073); parameter diversityUsed(RDIV) = Y
CSDAP (BSS30385) or Packet Abis (BSS21454 or BSS21440)
CSDAP is license-controlled feature and is in use if there is attached CSDAP in
the BCF
Packet Abis is license-controlled feature and is in use if BCF parameter Abis
Interface Connection Type Legacy
OSC HR with SAIC MS is license-controlled feature, so to activate it appropriate license
capacity is required
In RG20(BSS) OSC DHR with SAIC MS feature is supported only by Flexi EDGE BTS
(version EX4.0);

For internal use
Prerequisites (2)
Since OSC cannot be applied in Epsilon TRX belonging to a Dual TRX unit of which at
least one TRX has been started in EGPRS mode the following should be considered
(this limitation refers to EGPRS only and not to GPRS):
in case of BTSs equipped with Epsilon TRXs only, there must be at least one Dual
TRX unit of which neither of TRXs is started in EGPRS mode
this means that in order to enable OSC in a BTS having EGPRS enabled (parameter
EGENA=Y), two TRXs belonging to the same Dual TRX unit must have the parameter GPRS
enabled TRX (GTRX) set to value N different than default setting
to allow for as high as possible OSC penetration, the number of EGPRS enabled TRXs should
be kept to the necessary minimum
in case of BTS equipped with only one Dual TRX this means that either EGPRS or OSC may
be supported unless the sharing of Dual TRXs between sectors of the same site is applied
(see next slide)
in case of BTSs equipped with both Epsilon and Odessa TRXs it is recommended to
enable EGPRS on Odessa TRXs first (EGPRS and OSC can be supported
simultaneously) and only in case of lack of PS capacity on Epsilon TRXs
How to check TRX HW variant (Epsilon or Odessa)
different module description codes
Epsilon: EXxA
Odessa: EXxB
this information may be retrieved via BTS Manager session direct to a BTS site or NetAct
Inventory Manager reports (after HW inventory has been uploaded from each BTS site via
BSC to NetAct database)
For internal use
Since OSC cannot be applied in Epsilon TRX belonging to a Dual TRX unit of which at
least one TRX has been started in EGPRS mode, to allow concurrent support of
EGPRS and OSC in case of 2+2+2 BTS configuration, sharing of Dual TRXs between
sectors of the same site should be considered
this solution however allows to enable both EGPRS and OSC simultaneously in
two out of three BTSs of a given site
Upgrade Cable Kit (EUCA) with extra long RF cables has to be used to provide
RX paths

Sector 1
Sector 2
Sector 3
Dual TRX1 with
EGPRS supported
Dual TRX2 with OSC
supported
Dual TRX3 with OSC or
EGPRS supported
Dual TRX module
Dual duplexer module
Prerequisites (3)
For internal use
Recommended features (1)
Features recommended to be considered when introducing OSC Half Rate with SAIC
MS (BSS21309):
Soft Channel Capacity (BSS30080) allows for TRX configurations exceeding
maximum TCH handling capacity of BCSU
AMR Unpacking Optimization (BSS21120) allows improving the performance in
terms of call drop rate in both non-DHR and DHR mode and allows controlling the
target channel mode in DHR demultiplexing HOs
AMR HO Signaling Optimization (BSS20916) allows improving the performance
in terms of call drop rate and MOS statistics (less FACCH blocks needed during
HO procedure; especially beneficial in case of Double FACCH Stealing in DHR
mode)
Robust AMR Signaling (BSS20872) comprising FACCH & SACCH Repetition and
FACCH Power Increment allows improving the performance in terms of call
drop rate may be beneficial also in DHR mode
Improved AMR Packing and Unpacking (BSS21483) allows improving the
performance of AMR HR and DHR calls by providing means to trigger unpacking
and demultiplexing HO due to low Rx level (without waiting for Rx quality
degradation)
Discontinuous Transmission (BSS11610) less interference in the network and
better performance of DHR mode (mandatory)
For internal use
Recommended features (2)
Features recommended to be considered when introducing OSC Half Rate with SAIC
MS (BSS21309):
Dynamic SDCCH Allocation (BSS07036) higher network capacity resulting from
OSC introduction may require higher SDCCH channel capacity to keep GoS at
satisfactory level; instead of creating additional permanent SDCCH channel
(needed only during busy hour) Dynamic SDCCH Allocation may be applied
Increase Dynamic SDCCH Capacity (BSS21113) in some scenarios standard
SDCCH capacity (16 channels on BCCH TRX and 24 channels on non-BCCH TRX)
may be not sufficient
Extended CCCH (BSS21538) and Intelligent Selective Paging (BSS21324) higher
network capacity achieved with OSC may result in higher paging load and hence
a feature improving paging performance may be needed
Variable DL Power Control (BSS09021) fast TX power adjustment to optimum
level may be especially beneficial in case of DHR demultiplexing HO towards AMR
FR (after demultiplexing from DHR to AMR FR, Rx Quality may improve
significantly as an effect of Rx Quality disproportion between these two channel
modes and hence quicker power reduction may be helpful to avoid ping-pong
AMR FR -> AMR HR packing HO)
For internal use
Performance Measurements
For internal use
New counters (1)
Counter name Description
DHR_MULTIPLEXING_
ATTEMPTS (001263)
(Traffic Measurement)
This counter provides the number of DHR multiplexing procedures triggered by
load criterion (threshold Limit for Triggering OSC DHR Multiplexing).
Trigger event: checking the load criterion (upon receiving the report form
HO&PC algorithm) results in starting of DHR multiplexing procedure.
Use case:
- Total DHR Multiplexing Failure Rate (Sum of DHR Multiplexing
Failures/DHR_MULTIPLEXING_ATTEMPTS): hfr_1000
- DHR Multiplexing Failure Rate per Reason: hfr_1001, hfr_1002, hfr_1003
- DHR seizers (DHR_MULTIPLEXING_ATTEMPTS - Sum of DHR Multiplexing
Failures)
DHR_MPLX_FAIL_DUE
_TCH_RES (001264)
This counter provides the number of DHR multiplexing failures due to lack of
suitable DHR multiplexing candidates.
Trigger event: attempted DHR multiplexing procedure fails due to lack of pair
of connections fulfilling DHR multiplexing criteria.
Use case: calculation of DHR Multiplexing Failure Rate due to Lack of Suitable
Pair: hrf_1001 = (DHR_MPLX_FAIL_DUE_TCH_RES
/DHR_MULTIPLEXING_ATTEMPTS)
Note: in some scenarios this counter (and consequently DHR Multiplexing
Failure Rate due to Lack of Suitable Pair ) may provide quite high values
despite the fact that DHR multiplexing algorithm is correctly configured and
sufficient DHR utilization is achieved. The reason of this is that multiplexing
procedure may be attempted every 5 sec (default settings) if load criterion is
met and it may happen that all SAIC capable MS are already in DHR mode and
therefore no even 1
st
multiplexing candidate can be found.
For internal use
New counters (2)
DHR_MPLX_FAIL_DUE_C
SDAP_RES (001266)
This counter provides the number of CSDAP resources allocation failures
for DHR.
Trigger event: DHR multiplexing is rejected due to lack of CSDAP
resources
Use case: calculations of DHR Multiplexing Failure Rate due to lack of
CSDAP: hfr_1002 =
(DHR_MPLX_FAIL_DUE_CSDAP_RES/DHR_MULTIPLEXING_ATTEMP
TS)
DHR_MPLX_FAIL_DUE_O
THER (001267)
This counter provides the number of DHR multiplexing failures due to
unsuitable state of the call.
Trigger event: initiated DHR multiplexing HO is rejected due to
unsuitable state of the call.
Use case: calculations of the DHR Multiplexing Failure Rate due to Other
Reasons: hfr_1003 = (DHR_MPLX_FAIL_DUE_OTHER/
DHR_MULTIPLEXING_ATTEMPTS)
CSDAP_RES_ALLOC_AT
T_FOR_DHR (001265)
This counter provides the number of CSDAP resources allocation
attempts for DHR.
Trigger event: CSDAP resources are requested by RRM for OSC-1 sub-
channel.
Use case: calculations of the CSDAP Allocation Failure Rate: hfr_1004 =
(DHR_MPLX_FAIL_DUE_CSDAP_RES/CSDAP_RES_ALLOC_ATT_FO
R_DHR)
For internal use
New counters (3)
AVE_BUSY_DHR_TCH
(002094)
(Resource Availability
Measurement)
This counter provides the sum of the number of busy DHR TCHs
(aggregated for the whole observation time over 20-second periods).
Note: two DHR connections paired in one TCH/H channel are
counted as one DHR TCH. Hence to obtain real number of DHR calls
the value provided with this this counter must be multiplied by 2.
Trigger event: seizure or release of DHR TCH. The number of busy DHR
TCH is sampled every 20 seconds.
Use case: calculations of the Average DHR Traffic: trf_472 =
(2*AVE_BUSY_DHR_TCH/AVE_BUSY_DHR_TCH_DENOM) and DHR
Usage (trf_473 = Average DHR Traffic/Total Carried Traffic); together with
counters AVE_TCH_BUSY_FULL and AVE_TCH_BUSY_HALF allows to
estimate FR, HR and DHR traffic distribution.
AVE_BUSY_DHR_TCH_D
ENOM (002095)
Measurement)

This counter provides the number of measurement samples for busy DHR
TCHs (the number of 20-second periods comprised in observation period)
Trigger event: every 20 seconds when sample of the number of busy
DHR TCH is taken.
Use case: calculations of Average DHR Traffic: trf_472 =
(2*AVE_BUSY_DHR_TCH/AVE_BUSY_DHR_TCH_DENOM)
PEAK_BUSY_DHR_TCH
(002096)
Measurement)
This counter provides the peak number of busy DHR TCHs within an
observation period. See note for AVE_BUSY_DHR_TCH.
Trigger event: when the latest measured number of busy DHR TCHs
exceeds the previous peak value.
Use case: monitoring of the peak DHR traffic and the highest DHR usage
For internal use
New counters (4)
DHR_PAIR_AVERAGE_
LIFETIME (002101)
Measurement)
This counter provides the sum of the OSC DHR pair lifetimes.
Trigger event: updated every time an OSC DHR connection is released
successfully and another connection still remains in the TCH/F. The counter
is updated by the time the two OSC DHR connections have spent
concurrently in a TCH/H.
Use case: calculations of the Average DHR Call Length =
(DHR_PAIR_AVERAGE_LIFETIME/DHR_PAIR_AVE_LIFETIME_DENOM)
Note: this counter is available starting from in RG20 EP1 release.
DHR_PAIR_AVE_LIFETI
ME_DENOM (002102)
Measurement)
This counter provides the denominator for the average OSC DHR pair
lifetime calculation.
Trigger event: is increased by one when an OSC DHR connection is
released successfully and another connection still remains in the TCH/H.
Use case: calculations of the Average DHR Call Length =
(DHR_PAIR_AVERAGE_LIFETIME/DHR_PAIR_AVE_LIFETIME_DENOM)
Note: this counter is available starting from in RG20 EP1 release.
For internal use
New counters (5)
HO_ATTEMPT_FROM_A
MR_HR_TO_DHR
(004235)
(Handover Measurement)
This counter provides the number of DHR multiplexing handover attempts
for an AMR HR connections.
Trigger event: DHR multiplexing HO is attempted for connection being in
AMR HR mode (appropriate 2
nd
candidate has already been found)
Use case:
- AMR HR-to-DHR HO Success Rate: hsr_1000 =
(HO_FROM_AMR_HR_TO_DHR_SUCC/HO_ATTEMPT_FROM_AMR_H
R_TO_DHR)
- Percentage of AMR HR-to-DHR HO Attempts: ho_1000 =
(HO_ATTEMPT_FROM_AMR_HR_TO_DHR/(HO_ATTEMPT_FROM_AM
R_HR_TO_DHR+ HO_ATTEMPT_FROM_AMR_FR_TO_DHR))
HO_FROM_AMR_HR_TO
_DHR_SUCC (004237)
This counter provides the number of successful AMR HR-to-DHR
multiplexing handovers.
Trigger event: completion of AMR HR-to-DHR multiplexing HO
Use case:
- AMR HR-to-DHR HO Success Rate hsr_1000 =
(HO_FROM_AMR_HR_TO_DHR_SUCC/HO_ATTEMPT_FROM_AMR_H
R_TO_DHR)
For internal use
New counters (6)
HO_ATTEMPT_FROM_A
MR_FR_TO_DHR
(004236)
This counter provides the number of DHR multiplexing handover attempts
from an AMR FR connections.
Trigger event: DHR multiplexing HO is attempted for connection being in
AMR FR mode (appropriate 2
nd
candidate has already been found)
Use case:
- AMR FR-to-DHR HO Success Rate: hsr_1001 =
(HO_FROM_AMR_FR_TO_DHR_SUCC/HO_ATTEMPT_FROM_AMR_F
R_TO_DHR)
- Percentage of AMR FR-to-DHR HO Attempts: ho_1001 =
(HO_ATTEMPT_FROM_AMR_FR_TO_DHR/(HO_ATTEMPT_FROM_AM
R_HR_TO_DHR+ HO_ATTEMPT_FROM_AMR_FR_TO_DHR))
HO_FROM_AMR_FR_TO_
DHR_SUCC (004238)
This counter provides the number of successful AMR FR-to-DHR
multiplexing handovers.
Trigger event: completion of AMR FR-to-DHR multiplexing HO
Use case:
- AMR FR-to-DHR HO Success Rate: hsr_1001 =
(HO_FROM_AMR_FR_TO_DHR_SUCC/HO_ATTEMPT_FROM_AMR_F
R_TO_DHR)
For internal use
New counters (7)
UNSUCC_HO_TO_DHR_D
UE_MISMATCH (004239)
This counter provides the number of failed DHR multiplexing handovers
due to CSDAP conflict between BSC and BTS.
Trigger event: when target channel activation fails during DHR
multiplexing HO with cause code CSDAP error
Use case: monitoring of DHR multiplexing HO Failure Rate due to
CSDAP conflict
For internal use
New counters (8)
HO_ATT_FROM DHR
DUE_RX_QUAL (004240)
This counter provides the number of DHR demultiplexing HO attempts
triggered by Rx Quality criterion.
Trigger event: Rx quality criterion triggers DHR demultiplexing HO.
Use case:
- RxQual DHR Demultiplexing HO Success Rate: hsr_1002 =
(HO_FROM_DHR_DUE_RX_QUAL_SUCC/HO_ATT_FROM_DHR_DUE
_RX_QUAL)
- DHR Demultiplexing HO Type Distribution, e.g.: ho_1002 =
(HO_ATT_FROM_DHR_DUE_RX_QUAL/Total number of DHR
Demultiplexing HO Attempts)
- DHR Demultiplexing HO Success Rate: hsr_1005 = (Total number of
Successful DHR Demultiplexing HO/Total number of DHR demultiplexing
HO Attempts)
HO_FROM_DHR_DUE_R
X_QUAL_SUCC (004242)
This counter provides the number of successful DHR demultiplexing HO
triggered by Rx Quality criterion.
Trigger event: completion of DHR demultiplexing HO triggered by Rx
Quality criterion.
Use case:
- RxQual DHR Demultiplexing HO Success Rate: hsr_1002
- DHR Demultiplexing HO Success Rate: hsr_1005
For internal use
New counters (9)
HO_ATT_FROM_DHR_DU
E_RXLEV_DIFF (004241)
triggered by UL Rx Level Difference (Unbalance) criterion.
Trigger event: UL Rx Level Difference criterion triggers DHR
demultiplexing HO.
Use case:
- UL RxLev Difference DHR Demultiplexing HO Success Rate:hsr_1003=
(HO_FROM_DHR_DUE_RXLEV_SUCC/HO_ATT_FROM_DHR_DUE_R
XLEV_DIFF)
(HO_ATT_FROM_DHR_DUE_RXLEV_DIFF/Total number of DHR
HO Attempts)
HO_FROM_DHR_DUE_R
XLEV_SUCC (004243)
triggered by UL Rx Level Difference criterion.
Trigger event: completion of DHR demultiplexing HO triggered by UL Rx
Level Difference criterion.
Use case:
- UL RxLev Difference DHR Demultiplexing HO Success Rate: hsr_1003
For internal use
New counters (10)
HO_ATT_FROM_DHR
DUE_RX_LEV (004251)
triggered by Rx Level criterion (when Improved AMR Packing and
Unpacking (BSS21483) is active).
Trigger event: Rx Level criterion triggers DHR demultiplexing HO
Use case:
- RxLev DHR Demultiplexing HO Success Rate: hsr_1004 =
(HO_FROM_DHR_DUE_RX_LEV_SUCC/HO_ATT_FROM_DHR_DUE_
RX_LEV)
(HO_ATT_FROM_DHR_DUE_RX_LEV/Total number of DHR
HO Attempts)
HO_FROM_DHR_DUE_R
X_LEV_SUCC (004252)
triggered by Rx Level criterion (when Improved AMR Packing and
Unpacking (BSS21483) is active).
Trigger event: completion of DHR demultiplexing HO triggered by Rx
Level criterion.
Use case:
- RxLev DHR Demultiplexing HO Success Rate: hsr_1004
For internal use
New counters (11)
INTRA_HO_FROM_AMR_H
R_TO_DHR (051216)
(BSC Level Clear Code
Measurement)
This counter provides the number of successful intra-cell AMR HR-to-DHR multiplexing HOs.
Trigger event: HANDOVER PERFORMED message is sent to the MSC.
Use case: monitoring of the number of AMR HR-to-DHR multiplexing HOs (analogous to the
counter HO_FROM_AMR_HR_TO_DHR_SUCC from Handover Measurements)
INTRA_HO_FROM_AMR_F
R_TO_DHR (051217)
Measurement)
This counter provides the number of successful intra-cell AMR FR-to-DHR multiplexing HOs.
counter HO_FROM_AMR_FR_DHR_SUCC from Handover Measurements)
INTRA_HO_FROM_DHR_D
UE_RX_QUAL (051218)
Measurement)
This counter provides the number of successful intra-cell DHR demultiplexing HO triggered
by Rx Quality criterion.
counter HO_FROM_DHR_DUE_RX_QUALITY_SUCC from Handover Measurements)
INTRA_HO_FROM_DHR_D
UE_LEV_DIFF (051219)
Measurement)
by UL Rx Level Difference criterion.
counter HO_FROM_DHR_DUE_RXLEV_SUCC from Handover Measurements)
INTRA_HO_FROM_DHR_D
UE_RX_LEV (051221)
Measurement)
by Rx Level criterion (when Improved AMR Packing and Unpacking (BSS21483) is active).
counter HO_FROM_DHR_DUE_RX_LEV_SUCC from Handover Measurements)
For internal use
New counters (12)
TOTAL_PCM_SUBTSLS
_IN_CSDAP (121000)
(CSDAP Measurement)
This counter provides the total number of 8 kbps PCM subTSL in CSDAP.
Trigger event: The counter is updated by the size of the CSDAP once in a
measurement period
Use case: monitoring of the usage of CSDAP
AVERAGE_CSDAP_SUB
TSL_USAGE (121001)
(CSDAP Measurement)
This counter provides the sum of the number of busy 8kbit/s subTSL in
CSDAP (aggregated for the whole observation time over 20-second periods)
Trigger event: seizure or release of 8kbit/s subTSL. The number of busy
8kbit/s subTSL is sampled every 20 seconds.
Use case: calculations of the Average CSDAP 8kbit/s subTSL Usage:
trf_1000 =
(AVERAGE_CSDAP_SUBTSL_USAGE/AVERAGE_CSDAP_SUBTSL_USAG
E_DEN)
AVERAGE_CSDAP_SUB
TSL_USAGE_DEN
(121002)
(CSDAP Measurement)

This counter provides the number of measurement samples for busy 8kbit/s
subTSL in CSDAP (the number of 20-second periods comprised in
observation period)
Trigger event: every 20 seconds when sample of the number of busy 8kbit/s
subTSL in CSDAP is taken.
Use case: calculations of Average 8kbit/s subTSL in CSDAP Usage: trf_1000
PEAK_CSDAP_SUBTSL
_USAGE (121003)
(CSDAP Measurement)
This counter provides the peak usage of 8kbit/s subTSL in CSDAP.
Trigger event: when the latest measured number of busy 8kbit/s subTSL
exceeds the previous peak value.
Use case: monitoring of the peak usage of 8kbit/s subTSL in CSDAP.
For internal use
New counters (13)
Measurements Description
OSC RX Quality
Measurements
counters: 122000-122079
This group of counters collects UL and DL Rx Quality statistics for DHR
mode.
There are separate counters (each comprising 8 RxQual bins) for each
TRX and each AMR HR codec.
Trigger event: appropriate counter is updated upon receiving
measurement report for DHR connection.
Use case: monitoring of Rx Quality for DHR mode, e.g.:
(dlq_1007+dlq_1008), (ulq_1007+ulq_1008)
For internal use
Modified counters
Measurements Description
FER Measurement Identification of the used codec type. Five new counters
was added to distinguish DHR channel/codec mode
(DHR4.75..DHR7.4); counters CODEC_TYPE (77002)
Drop Call Break Down Observation Modified to distinguish DHR channel/codec mode;
counters: DL_LAST_USED_BITRATE (029014) and
DL_LAST_USED_BITRATE (029015)
Radio Measurement Report Modified to distinguish DHR channel/codec modes used in
UL and DL;
Resource Availability Measurements Meaning of counters for congestion remains the same as
without OSC feature:
- Counter HALF RATE RADIO TCH CONGESTION TIME
(002045) is started when there is at least one call in each
TCH/H.
- Counter TOTAL CHANNEL BUSY TIME (002026) is started
when there is at least one call in each TCH of the BTS.
DHR calls are included in the counters collecting the
average and peak numbers of occupied TCHs (counters
002027 AVE BUSY TCH and 002029 PEAK BUSY TCH) and
in the counter collecting the average holding time of all
TCHs (counter 002036 AVE TCH HOLD TIME)
For internal use
Feature Impact Analysis/Feature
Performance Monitoring
For internal use
Feature Impact Analysis
Feature impact How to measure
Lower TCH blocking
KPIs:
TCH Call Blocknig (blck_8i)
Higher TCH Traffic Carried and/or
Lower TSL Utilization by CS Traffic
Note: depending on the amount of CS traffic
offered to the network
KPIs:
Average CS Traffic (trf_202a)
Normal TCH Usage Ratio for CS (trf_197a)
The feature impact highly depends on the DHR mode usage (determined by SAIC MS penetration,
network scenario and OSC-related parameters setting).
Impact of the OSC feature on overall network performance depends on the
operators deployment strategy, whether it is e.g.:
capacity extension without network reconfiguration
reduction of the number of TRXs
reduction of site density, etc.
Presented feature impact analysis has been done for capacity extension
scenario without any network reconfiguration
For internal use
Larger PS Territory
Note: resulting from lower TSL utilization by
CS traffic -> less TSL occupied by CS traffic
means that there is more space for PS
territory; appropriate DHR utilization may
allow avoiding situation in which the default
or additional PS territory is limited by CS
traffic and its actual size is lower than could
be according to CDEF and/or CMAX
parameters settings
KPIs:
Average Available PS Territory Size (ava_44)
Lower TBF Multiplexing
Note: resulting from larger PS Territory
KPIs:
Average DL TBF per TSL (tbf_38c)
Lower Multislot Allocation Soft
Blocking
Note: the lower probability that an MS will be
assigned less TSLs than it could be
according to its multislot class results from
larger PS Territory
KPIs:
DL Multislot Soft Blocking (blck_33c) a ratio of un-
served TSL requests to all requests in DL
PS performance is analyzed only in DL direction since in UL PS traffic amount is relatively low and radio
resources are not regarded as a bottleneck.
For internal use
Higher Number of PDCHs per TBF
KPIs:
Distribution of DL x TSL Allocations (msl_4c)
Average Number of Allocated TSL in DL (msl_12c)
Higher DLDC Allocation Success Ratio
KPIs:
DLDC Allocation Success Ratio (dldc_3)
Higher LLC Data Throughput
Note: resulting from lower Multislot Blocking
and lower TBF Multiplexing and assuming the
same radio conditions
KPIs:
Volume Weighted LLC Throughput (llc_3a)
Weighted LLC Throughput for DLDC MS (dldc_4)
PS performance is analyzed only in DL direction since in UL PS traffic amount is relatively low and radio
resources are not regarded as a bottleneck.
For internal use
Increased BER and FER
Note: QPSK modulation and MU-MIMO concepts
used in DL and UL respectively, may result in
performance degradation of voice calls in DHR
mode.
It may, however, happen that with high DHR usage
resulting in lower TSL occupation (if served traffic
does not increase) the overall interference level in
the network gets lower and quality statistics get
better (decrease of interference level is higher than
degradation resulting from DHR mode itself).
KPIs:
DL Cumulative Level Ratio in Class X (dlq_2a)
UL Cumulative Level Ratio in Class X (ulq_2a)
DL and UL BER Distribution based on counters 014016..014148
and new OSC RX Quality Measurements (122000-122079)
UL FER Distribution and UL Bad FER Ratio based on counters
077015..077022
DL FER Distribution and DL Bad FER Ratio based on counters
077023..077030 and 077032..077039
No or slight degradation in MOS KPIs:
Drive tests needed
No or slightly increased Drop Call Ratio
Note: resulting from poorer SACCH and FACCH
performance in DHR mode and phenomena
described in note above
KPIs:
TCH Drop Call Ratio (dcr_8i)
Increased number of intra-cell HOs
Note: resulting from the fact that switching between
non-DHR and DHR mode is realized via DHR
multiplexing/demultiplexing HOs
KPIs:
CELL_TCH_TCH _AT (004076)/Total Carried Traffic(trf_1)
For internal use
Feature Performance Monitoring
Performance indicator How to measure
DHR Traffic
Characteristics
KPIs:
Average DHR Traffic: trf_472 =
2*AVE_BUSY_DHR_TCH/AVE_BUSY_DHR_TCH_DENOM
Peak Busy DHR TCH =2*PEAK_BUSY_DHR_TCH
REMARK: See note for counter AVE_BUSY_DHR_TCH.
DHR Traffic Share: trf_473 = Average DHR Traffic(trf_472) /Total Carried
Traffic(trf_1)
Average DHR Call Length
=(DHR_PAIR_AVERAGE_LIFETIME/DHR_PAIR_AVE_LIFETIME_DENOM)
SDCCH Blocking = blck_5b
DHR Multiplexing
Failure Rate

KPIs:
Total DHR Multiplexing Failure Rate = hfr_1000 =
SUM_OF_DHR_MULTIPLEXING_FAILURES/DHR_MULTIPLEXING_ATTE
MPTS
DHR Multiplexing Failure Rate due to Lack of Suitable Pair = hfr_1001 =
DHR_MPLX_FAIL_DUE_TCH_RES / DHR_MULTIPLEXING_ATTEMPTS
REMARK: See note for counter DHR_MPLX_FAIL_DUE_TCH_RES.
DHR Multiplexing Failure Rate due to CSDAP = hfr_1002 =
DHR_MPLX_FAIL_DUE_CSDAP_RES/DHR_MULTIPLEXING_ATTEMPTS
DHR Multiplexing Failure Rate due to Other Reasons = hfr_1003 =
DHR_MPLX_FAIL_DUE_OTHER/ DHR_MULTIPLEXING_ATTEMPTS
Description of particular counters used in above KPI definitions may be found in the section dedicated
to Performance Measurements
For internal use
DHR Multiplexing HO Success Rate
KPIs:
AMR HR-to-DHR HO Success Rate = hsr_1000 =
HO_FROM_AMR_HR_TO_DHR_SUCC/HO_ATTEMPT_FROM
_AMR_HR_TO_DHR
AMR FR-to-DHR HO Success Rate = hsr_1001 =
HO_FROM_AMR_FR_TO_DHR_SUCC/HO_ATTEMPT_FROM
_AMR_FR_TO_DHR
DHR Demultiplexing HO Success
Rate
KPIs:
RxQual DHR Demultiplexing HO Success Rate = hsr_1002 =
HO_FROM_DHR_DUE_RX_QUAL_SUCC/HO_ATT_FROM_D
HR_DUE_RX_QUAL
UL RxLev Difference DHR Demultiplexing HO Success Rate
= hsr_1003 = HO_FROM_DHR_DUE_RXLEV_SUCC /
HO_ATT_FROM_DHR_DUE_RXLEV_DIFF
RxLev DHR Demultiplexing HO Success Rate = hsr_1004 =
HO_FROM_DHR_DUE_RX_LEV_SUCC/HO_ATT_FROM_DH
R_DUE_RX_LEV
DHR Demultiplexing HO Success Rate = hsr_1005 =
(HO_FROM_DHR_DUE_RX_QUAL_SUCC+
HO_FROM_DHR_DUE_RXLEV_SUCC +
HO_FROM_DHR_DUE_RX_LEV_SUCC)/(
HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DH
R_DUE_RXLEV_DIFF+HO_ATT_FROM_DHR_DUE_RX_LEV)
For internal use
DHR Demultiplexing HO Type
Distribution
KPIs
DHR Demultiplexing HO Type (due to RxQual) Distribution =
ho_1002 = HO_ATTEMPT_FROM_DHR_DUE_TO_RXQUAL /
(HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DHR
_DUE_RXLEV_DIFF+HO_ATT_FROM_DHR_DUE_RX_LEV)
DHR Demultiplexing HO Type (due to UL RxLev difference)
Distribution = ho_1003 =
HO_ATT_FROM_DHR_DUE_RXLEV_DIFF
/(HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DHR
DHR Demultiplexing HO Type (due to RxLev) Distribution =
ho_1004 = HO_ATT_FROM_DHR_DUE_RX_LEV
/(HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DHR
DHR Quality
KPIs:
Rx Quality distribution, e.g.
- OSC DL RxQual 6_7 distribution=dlq_1007+dlq_1008
- OSC UL RxQual 6_7 distribution=ulq_1007+ulq_1008
FER based on USED_CODEC_TYPE (77002)
For internal use
CSDAP Size
KPIs:
CSDAP Size = TOTAL_PCM_8_KBIT/S_SUBTSL_IN_CSDAP
CSDAP Allocation Failure Rate
KPIs:
CSDAP Allocation Failure Rate = hfr_1004 =
DHR_MPLX_FAIL_DUE_CSDAP_RES/CSDAP_RES_ALLOC_ATT_
FOR_DHR
CSDAP Usage
KPIs:
Average CSDAP 8kbit/s subTSL Usage = trf_1000 =
AVERAGE_CSDAP_8KBPS_SUBTSL_USAGE/AVERAGE_CSDAP
_8KBPS_SUBTSL_USAGE_DENOMINATOR
Peak CSDAP 8kbit/s subTSL Usage =
PEAK_CSDAP_8_KBIT/S_SUBTSL_USAGE
Peak CSDAP Utilization = trf_1001 =
(PEAK_CSDAP_8_KBIT/S_SUBTSL_USAGE)/
(TOTAL_PCM_8_KBIT/S_SUBTSL_IN_CSDAP)
For internal use
Thank you
for your attention!
For internal use
Backup slides

Module 1 - OSC

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Module 1 - OSC

Diunggah oleh

Hak Cipta:

Format Tersedia

1 Nokia Siemens Networks Presentation / Author / Date

For internal use

47 Nokia Siemens Networks Presentation / Author / Date

Anda mungkin juga menyukai