OSC

RG20 (BSS)
Orthogonal Sub-channel
BSS21309, BSS30385
For internal use

1 © Nokia Siemens Networks Presentation / Author / Date
BSS21309, BSS30385
Dependency table
BTS BTS BTS

BSS BSC*
TalkFamily MetroSite BTSplus
Release RG20 S15 Not supported Not supported Not supported**
* supported by BSCi, BSC2i, BSC3i and FlexiBSC
** Supported via RG301397 (Cositing with BS2xx)
BTS BTS BTS

Flexi EDGE UltraSite Flexi Multiradio
Release SW: EX4.0 Not supported*** Not supported***

*** Supported starting from RG25(BSS)
DX200
MS SGSN MCS RAN NetAct
Platform
Release No SAIC indicating No No No OSS5.2 CD set 3

dependency its capability dependency dependency dependency
For internal use

BSS21309, BSS30385
RG(BSS) features with reference to 3GPP VAMOS
Handset compatibility
RG feature Comments
in OSC allocation
DARP (SAIC) OSC Half Rate with SAIC MS is the NSN proprietary
OSC Half Rate with SAIC MS
VAMOS I feature which also motivated 3GPP to start VAMOS
(BSS21309); RG20
VAMOS II standardization activities.
DARP (SAIC) OSC Full Rate with SAIC MS is the NSN proprietary
OSC Full Rate with SAIC MS (BSS
VAMOS I feature extending the concept of BSS21309
21534); RG25
VAMOS II Orthogonal Sub-channels to full rate mode.
Feature adds signaling support for new training

DARP (SAIC) sequences supported by VAMOS handsets. New
OSC support for VAMOS mobiles training sequences are optimized for simultaneous
VAMOS I use.
(BSS 21313); RG30
VAMOS II VAMOS II handset utilizes advanced receiver
providing further link gains over VAMOS I or SAIC.
Rel 99
DARP (SAIC) Introduces sub channel power control in DL allowing
AQPSK for VAMOS II (BSS
also non-SAIC mobiles to be paired in OSC mode
21537); RG30 VAMOS I with VAMOS II handsets.
VAMOS II
For internal use

BSS21309, BSS30385
Contents
 Introduction
 Feature details
 Configuration management
 Pilot results
 Dimensioning aspects
 Implementation aspects
 PM counters
 Feature impact analysis/feature performance monitoring
For internal use

Introduction
For internal use

Introduction
 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
For internal use

Introduction
 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 DHR
one radio timeslot
OSC
 OSC-related enhancements on the roadmap DFR
HR
 DFCA Support for OSC in RG20EP1
 OSC Support for VAMOS mobiles in RG30
 AQPSK for VAMOS II in RG30 FR
 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 MOSFor internal7use © Nokia Siemens Networks Presentation / Author / Date
Feature details
For internal use

Feature details
Overview
 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
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

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
Table 1 Optimized TSC pairs for OSC
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

OSC Half Rate with SAIC MS Report from
HO&PC
 DHR multiplexing mode is triggered based on the Yes

load criterion Load criterion No
fulfilled?
 Load criterion is checked upon receiving a report end
from HO&PC algorithm
Enter DHR
 If the percentage of free FR TCHs decreases below multiplexing mode
Limit for Triggering OSC DHR Multiplexing,
 the BTS enters DHR multiplexing mode -> Search for the 1st
candidate (target
searching for the best pair to be multiplexed into channel)
DHR mode (only one pair is multiplexed at a time
per BCSU) Yes suitable target No
channel found?
 When evaluating free FR TCHs, the PS territory end
resources are interpreted according to setting of CS Search for the 2nd
TCH allocation calculation (CTC) parameter: candidate
• 0 = Only CSW used RTSLs are used (default)

Yes suitable 2nd
• 1 = CSW and PSW used RTSLs are used. candidate
No
found?
• PSW is seen as occupied (optimize PS) end
• 2 = CSW used and PSW used RTSLs are used. DHR multiplexing HO of 2nd
candidate to the target
• PSW is seen as idle resource channel
For internal use

13 © Nokia Siemens Networks Presentation / Author / Date ready
Report from
HO&PC
 Multiplexing is realized by handing over AMR HR/FR Yes

connection to the target channel with ongoing AMR Load criterion No
HR call fulfilled?
end
Enter DHR
 Algorithm searches for the best pair of calls to be multiplexing mode
multiplexed to ensure optimal quality in DHR mode
 first, the best target channel is searched (1st candidate) Search for the 1st
candidate (target
 Only AMR HR SAIC connection is considered channel)
 next, the best connection to be handed over to target
channel is searched for (2nd candidate) Yes suitable target No
 both half rate and full rate AMR SAIC connections channel found?
considered
end
Search for the 2nd
candidate
Yes suitable 2nd No

candidate
found?
end
DHR multiplexing HO of 2nd
candidate to the target
channel
For internal use

14 © Nokia Siemens Networks Presentation / Author / Date ready
Report from
HO&PC
Orthogonal Sub-channel Yes No

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

DHR multiplexing example
ULRxLevMS1<Muxltiplexing UL RxLev Threshold
MS1 ULRxQualMS1=Multiplexing RxQual Threshold
DLRxQualMS1<Multiplexing RxQual Threshold
ULRxLevMS2=Multiplexing UL RxLev Threshold

MS2
ULRxQualMS2=Multiplexing RxQual Threshold
MS3
ULRxLevMS3>Multiplexing UL RxLev Threshold
ULRxQualMS3<Multiplexing RxQual Threshold
target channel candidate list:

1. TCH/H occupied by MS2
ULRxLevMS2+Power reductionMS2>
ULRxLevMS3+Power reductionMS3
sorted target channel candidate list:

the best target channel:

TCH/H occupied by MS2
For internal use

Report from
HO&PC
Orthogonal Sub-channel Yes Load criterion No

fulfilled?
OSC Half Rate with SAIC MS end
Enter DHR
multiplexing mode
 Searching for the best candidate to be handed over (the 2nd Search for the 1st
candidate (target
candidate) to the target channel)
 both AMR HR and FR calls are considered Yes suitable target No
 unless AMR FR to DHR HO is blocked with UTPFIL parameter

channel found?
(AMR FR DHR MUX) Search for the

end
 Candidates for DHR multiplexing HO must fulfill the following 2nd candidate
criteria:
Yes suitable 2nd No
candidate
UL & DL RxQual ≤ Intra HO Threshold Rx Qual AMR FR found?
end
and DHR multiplexing HO
-47dBm > UL RxLev ≥ Multiplexing UL Rx Level Threshold ready
For internal use

 The list of 2nd candidates is created based on the UL Rx Level Window criterion:
(UL RxLev2nd+Current Power Reduction2nd)≥(UL RxLev1st -Multiplexing UL RxLev Window)
and
(UL RxLev2nd+Current Power Reduction2nd)≤(UL RxLev1st +Multiplexing UL RxLev Window +

Max Power Reduction2nd)
where
Max Power Reduction2nd is the maximum possible uplink power reduction of the 2nd 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
RxLev
For internal use
18RxLev 1st - Siemens
© Nokia Window Networks UL RxLev
Presentation
1st RxLev
/ Author 1st + Window + Max Power Reduction2nd
/ Date
 Searching for the DHR multiplexing 2nd candidate according to UL Rx Level Window criterion
(UL RxLev2nd + Current Power Reduction2nd) ≥ (UL RxLev1st - Multiplexing UL RxLev Window)
and
(UL RxLev2nd + Current Power Reduction2nd) ≤ (UL RxLev1st + Multiplexing UL RxLev Window + Max
Power Reduction2nd)
MS1 MS2 has been chosen as the 1st candidate

ULRxLevMS1 + Power Reduction < UL RxLevMS2 - Multiplexing UL RxLev Window
ULRxLevMS3 + Power Reduction > UL RxLevMS2 - Multiplexing UL RxLev Window
MS2
ULRxLevMS3 + Power Reduction < UL RxLevMS2 + Multiplexing UL RxLev Window + max power reductionMS3
ULRxLevMS4 + Power Reduction > UL RxLevMS2 - Multiplexing UL RxLev Window
ULRxLevMS4 + Power Reduction < UL RxLev MS2+ Multiplexing UL RxLev Window + max power reductionMS4
MS3
MS4
Multiplexing Window for MS4
Multiplexing Window for MS3 MS4

MS1
MS3 MS2
RxLevMS2 + Window +
Max Power ReductionMS3
RxLev
RxLevMS2 - Window RxLevMS2 RxLevMS2 + Window + Max Power ReductionMS4

For internal use
Report from
HO&PC
Orthogonal Sub-channel Yes Load criterion

fulfilled?
No

Enter DHR
multiplexing mode
Search for the 1st

candidate (target
 Among all the connections meeting DHR channel)
multiplexing HO criteria the best 2nd candidate Yes suitable target No

is searched channel found?
end
 The best 2nd candidate is determined based on: Search for the
2nd candidate
 UL Rx Level Difference criterion

Yes suitable 2nd No
ΔULRXLEV= (UL RxLev1st+ CurrentPowerReduction1st)-(UL RxLev2nd + candidate
found?
CurrentPowerReduction2nd) end
 UL Rx Level Change Rate criterion DHR multiplexing HO
ΔUL RXLEV CHANGE RATE =ULRxLevChangeRate1st-ULRxLevChangeRate2nd ready

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

Report from
HO&PC

fulfilled?
No

Enter DHR
multiplexing mode
Search for the 1st

 Connection with the minimum value of candidate (target
channel)
(|ΔULRXLEV| + |ΔUL RXLEV CHANGE RATE|) Yes suitable target No

channel found?
is selected as the best 2nd candidate
end
Search for the
2nd candidate
 If ΔUL RXLEV CHANGE RATE is greater than the change rate

threshold (UTPFIL parameter: UL RX CHANGE RATE) the Yes suitable 2nd
candidate
No
multiplexing is rejected found?
 if a suitable multiplexing pair for the best 1st candidate cannot be

end
DHR multiplexing HO
found, the algorithm continues with multiplexing attempt for the
next best 1st candidate and so on until suitable pair is found or ready
there is no more 1st candidates to be checked
MS1 1st candidate: MS2

list of 2nd candidates (fulfilling also RxQual criterion): MS3, MS4
MS2
|ΔULRXLEVMS3-MS2|+ |ΔULRxLev Change RateMS3-MS2| <
|ΔULRXLEVMS4-MS2|+ |ΔULRxLev Change RateMS4-MS2|
MS3 MS4 the best 2nd candidate: MS3
For internal use

Report from
HO&PC

fulfilled?
No

Enter DHR
multiplexing mode
 The best 2nd candidate is handed over to the target channel Search for the 1st
candidate (target
channel)
 Multiplexing HO may be done to:
 OSC-1 sub-channel if AMR HR connection occupying target channel Yes suitable target
channel found?
No
is regarded as OSC-0
 OSC-0 sub-channel if AMR HR connection occupying target channel Search for the
end
is regarded as OSC-1 2nd candidate
Yes suitable 2nd No

candidate
found?
connection to be handed over
end
TRX:0 TS0 TS1 TS2 TS3 MS3 TS5 TS6 TS7 DHR multiplexing HO
DHR multiplexing HO ready

target channel
TRX:1 TS0 TS1 TS2 TS3 TS4 TS5 MS2 TS7
MS2 free MS3 free free

OSC-0 OSC-0 OSC-0 OSC-0 OSC
OSC
multiplexing multiplexing
MS3 free free MS2 free
OSC-1 OSC-1 OSC-1 OSC-1
HR multiplexing HR multiplexing
For internal use

Report from
HO&PC
OSC Half Rate with SAIC MS Yes
Load criterion
fulfilled?
No
end
 During DHR multiplexing procedure BTS switches from GMSK Enter DHR
multiplexing mode
modulation to QPSK modulation in DL on the target TCH/H
Search for the 1st
 During DHR multiplexing HO the

candidate (target
channel)
 Training Sequence Code is selected based on the TSC value

used for OSC-0 connections according to table 1 (Optimized Yes
suitable target
No
TSC pairs) channel found?
 If legacy Abis is used, CSDAP resource is needed for the new end
radio sub-channel Search for the
 If there is Packet Abis, a separate dynamic Abis pool is not needed 2nd candidate
 if there are no free CSDAP resources for OSC-1 sub-channel

available, Yes No
suitable 2nd
 Radio Channel Allocation algorithm changes priorities in candidate
found?
multiplexing algorithm to prefer (for the next attempts – the
number defined by UTPFIL parameter CSDAP PENALTY end
COUNT) a pair of AMR connections for which CSDAP DHR multiplexing HO
resource is not needed
ready
For internal use

Report from
HO&PC

fulfilled?
No

Enter DHR
multiplexing mode
 UL power optimization during DHR multiplexing HO is needed to Search for the 1st
candidate (target
minimize the difference between UL Rx Levels of paired DHR channel)
connections
Yes suitable target No
 UL Tx power level of the 1st candidate is not changed during DHR channel found?
multiplexing HO end
 UL Tx power level of the 2nd candidate is adjusted so that the UL Rx Search for the
2nd candidate
Levels of two paired calls are the same
Yes suitable 2nd No
 max possible power reduction is defined by the following formula:

candidate
found?
end
MaxPowerRe duction  min[min(Ms TxPwrMax. MSPowerCla ss) - DHR multiplexing HO
MSTxPwrMin , RxLevReduc tionMax] ready
RxLevReduc tionMax  max(0, RXLEVmax_U L - PCLowerThr esholdLevU L - SafetyMarg in)

MsTxPwrMax  MsTxPwrMax GSM or MsTxPwrMax GSM1x00 depending on the frequency band
MsPowerCla ss - the max power defined by the MS power class
• 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)
For internal use

Report from
HO&PC

fulfilled?
No

Enter DHR
multiplexing mode
Search for the 1st

candidate (target
channel)
 DL power optimization during DHR multiplexing HO is needed to
avoid an unnecessary power increase on target channel Yes suitable target No
channel found?
end
 an extra power increase is applied to balance ~3dB performance Search for the
2nd candidate
degradation (OSC with QPSK has worse performance than AMR with
GMSK) and provide sufficient DL quality in DHR mode
Yes suitable 2nd No
candidate
found?
 optimized DL Tx power level is determined by calculating new Power end
Reduction defined as the minimum of two values: DHR multiplexing HO
max(0, Old_Power_Red_DL1st – 3dB) and ready
max(0,RxLev_DL2nd + Old_Power_Red_DL2nd – RxLev_DL1st – 3dB)

• The value of 3dB may be adjusted with the UTPFIL parameter:
OSC MODULATION LOSS
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
3 2 1
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 TRX types in BTS GENA EGENA OSC in BTS
Epsilon Dual TRX Yes Yes Not possible Epsilon Dual TRXs only Yes Yes Not possible
Mix of Epsilon and Odessa Dual TRXs Yes Yes Not possible
Epsilon Dual TRX Yes No Possible
Odessa Dual TRXs only Yes Yes Possible
Epsilon Dual TRX No No Possible
Odessa Dual TRX* Yes Yes Possible Antenna hopping
Odessa Dual TRX* Yes No Possible
Odessa Dual TRX* No No Possible
TRX starting mode
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

 For OSC DHR mode more Abis transmission is needed for radio timeslot because
two calls are multiplexed in one HR channel
MS1 free
FR FR 2+2+2
64kbit trxsig
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 in OSC mode 2 DHR calls are transmitted in the same time
as the entire channel is used by HR call (i.e. time slot as these calls are distinguished by different TSC):
in every second time slot OSC-0 channels always use PCM resources reserved for TCH
while
OSC-1 channels always use PCM resources reserved in CSDAP
MS1 MS2 MS1 free

HR HR HR HR
multiplexing
multiplexing
MS1 MS3 MS1 free
OSC-0 OSC-0 OSC-0 OSC-0
OSC
OSC
HR (time) HR (time) MS2 MS4 MS2 free
multiplexing multiplexing OSC-1 OSC-1 OSC-1 OSC-1
For internal use HR (time) HR (time)

40 © Nokia Siemens Networks Presentation / Author / Date multiplexing multiplexing
 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
SAIC DL RXQuality samples (01415  ..  014157)
SAIC usage 
all DLRXquality samples (014010  ..  014017)
• HR utilization
De-
multiplexing
• OSC calls start from AMR HR (trf_122a) Limited cell

area where
OSC calls
Cell
can be
• Rxlevel / RxQuality distribution supported
range
• OSC has a working range upto Multiplexing
• RXLevel : -90dBm (maximum is -95dBm)

• RXQuality : 4 (maximum is 6, but not recommended to use)
• Traffic (trf_202a) / trf_1d
For internal use

OSC traffic estimation
• OSC percentage calculation

SAIC usage DL(RXquali ty 0-4 , RXLevel -47dBm to -85dBm )
OSC percentage  ( ) * HR% *
2 all_RXqual ity_sample s
• 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
For internal use

Abis dimensioning aspects
Dynamic Abis – CSDAP size (1)
 CSDAP size depends on site configuration and OSC penetration

FR/HR trunks actually do not need
site configuration to be computed because their resources
are anyway available on Abis permanently
#BCCH/CCCH/CDED per cell
#RTSL available for CS # Abis trunks for FR

Erl / site (and codec) # Abis trunks for HR
codec distribution
# Abis trunks for OSC
% FR = …
% HR = …
% OSC = …
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: 33 33 33
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

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: OK
© 2009 Network Engineering Wroclaw
For internal use

Dynamic Abis – CSDAP size - example
 to avoid OSC de-multiplexing it is recommended to round up the results related to OSC trunks
example:
Site configuration: 3 TRX/cell, 3 BCCH+SDCCH/cell, 1 CDED/cell => 20 RTSLs available for CS/cell (Ncs)
codec penetration: 50% FR, 25% HR, 25% OSC
Not needed to be computed
Calculations:
#FR trunks/cell = 14 28 trunks@2% 30.23 FR Erl
#HR trunks/cell = 7 60.45 Erl/site 15.12 HR Erl
#OSC trunks/cell = 7 20.15 Erl/cell 15.12 OSC Erl 33 OSC Abis trunks => 9 subchannels => 3 TSL
 3 PCM TSLs are recommended to be used
HR penetration * N cs * 0.25 * 20
N trunks_ HR  HRTrunks  7
0.75 * FR penetration  0.25 * HR penetration  0.25
0.75 * 50  0.25 * 25  0.25
DHR pentration * N cs *
N trunks_ DHR 
0.75 * FR penetration  0.25 * HR penetration  0.25
NTrunks _ FR  N cs 
NTrunks _ HR

NTrunks _ DHR *
2 4
* Source from NE
For internal use

Access network dimensioning aspects
General overview
 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 BSC
Enabling of OSC allows to increase capacity per TRX. Several Traffic to be handled determines bandwidth required in transport (Abis,
scenarios possible, each of them have potential impact on Ater) regardless on used technology => this must be reflected in
number of resources in access network: number of Exchange Terminals (ET16, ETS2, ETIP, ETP)
-TRX configuration is kept, CS traffic kept, more RTSL available for Number of users served have impact on signaling capacity and
PS traffic => higher PS traffic/throughputs possible processor load (AS7, BCSU, MCMU).
- TRX configuration is kept, PS territory is kept, more CS traffic can PS traffic modification have impact on PCU HW and Gb links capacity.
be served Other aspects to be evaluated: LAC planning, Soft channel capacity
- TRX configuration decreased but CS traffic is kept because of huge TCSM
OSC penetration Additional CS traffic must reflected in the number of transcoders as
-… well as Exchange Terminals (towards BSC and MSC).
TCSM
Abis A
Ater
BSC MSC
Abis interface Ater / A interface
=> Dynamic Abis: TRX site configuration is crucial for estimation of CS traffic increase caused by OSC introduction has also impact on
required PCM lines, CSDAP computed based on OSC penetration, transport resources towards Core. The need for additional resources
modification of PS territory affects EDAP size, TRXSIG capacity must must be checked regardless on used transport technology (TDM-based
be chosen appropriately (depending on load and codec type) or IP-based).
For internal use
=> Packet Abis: required bandwidth depends on amount of CS and PS
traffic as well as codec distribution
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 Allowed Half Rate configuration
6 TRXs * 8 TCHs = 48 TCHs 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
Example calculations (1)
 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
TCSM
Abis A
Ater
BSC MSC
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
15 ET16 (225 E1)
150 E1 / BSC
3 BCSU, 8 PCU
71 E1 / BSC
TCSM 284 E1 / TCSM
Abis A
1 E1 line: Ater
18 TSL/TCH
3+3+3 (9 TRX)
5 TSL/sign BSC 1 TCSM rack MSC
55.14 Erl 5 TC2C (9 TR3E, 5 ET16)
6 TSL/EDAP (~40 kbps/user)
15 MB/BH 20 ET16 (towards MSC)
4 E1 / BSC
PS core
Gb
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
16 ET16 (252 E1)
150 E1 / BSC
3 BCSU, 8 PCU
98 E1 / BSC
TCSM 392 E1 / TCSM
Abis A
1 E1 line with Ater
compressed
3+3+3 (9 TRX)
mapping BSC 7 TC2C (13 TR3E, 7 ET16) MSC
76.59 Erl 28 ET16 (towards MSC)
18 TSL/TCH
15 MB/BH => 2nd TCSM cabinet needed
5 TSL/sign 4 E1 / BSC
6 TSL/EDAP (~40 kbps/user) PS core
4 TSL/CSDAP
Gb
Note! In this case there
For internal use are much more users. Therefore dynamic capacity must be double-checked too.
In particular BCSU/MCMU ©load
55 as well
Nokia Siemens as LAC planning.
Networks Presentation / Author / Date
 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
15 ET16 (232 E1)
150 E1 / BSC
3 BCSU, 11 PCU
74 E1 / BSC
TCSM 296 E1 / TCSM
Abis A
1 E1 line with Ater
compressed
3+3+3 (9 TRX)
mapping BSC 1 TCSM rack MSC
57.78 Erl 5 TC2C (10 TR3E, 5 ET16)
18 TSL/TCH
30 MB/BH 20 ET16 (towards MSC)
5 TSL/sign 8 E1 / BSC
8 TSL/EDAP (~70 kbps/user)
For internal use 2 TSL/CSDAP
PS core
56 © Nokia Siemens Networks Gb
Presentation / Author / Date
OSC impact summary
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
 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
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
• TSC for the second connection is selected TSC for OSC-0 TSC for OSC-1
based on the value used for the first 0 2
connection in the TCH according to the table 1 7
on the right
2 0
– values in the table are still subject to
3 4
optimization and may change
4 3
5 6
6 5
7 1
For internal use

Implementation aspects
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
 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 TSC for OSC-0 TSC for OSC-1
cells 0 2
 such collisions between TSCs characterized by poor mutual 1 7
cross-correlation properties may lead to significant quality 2 0
degradation 3 4
 example: main TSCs determined by legacy non-OSC aware 4
5
3
6
algorithm; paired TSC derived from predefined table
6 5
7 1
Optimized TSC pairs for OSC
main TSC = 0 main TSC = 2 collision between main TSC of cell A (B)
and paired TSC of cell B (A)
cell A cell B collision between paired TSC of cell A (B)

and main TSC of cell B (A)
paired TSC = 2 paired TSC = 0
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
main TSC = 0 main TSC = 2 main TSC = 0 main TSC = 3
cell A cell B cell A cell B
For internal use

paired TSC = 2 63 paired
© Nokia Siemens TSC
Networks =0 Presentation / Authorpaired
/ Date TSC = 2 paired TSC = 4
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

OSC Parameters (RG20)- Overview
Multiplexing CSDAP) LOAD
DHRLIM (BTS))
OSCMultiplexingUL CSDAP ID firstTSL
RXLevelThr
(OMLT)
POWER CONTROL UTPFIL
circuitGroupNumber LastTSL UL RX Change rate
pcLowerThresholdDL
RXQualDhr (0x38)
OSCDHRMultiplexing (LDDHR)
pcmCircuit_ID PoolSize
RXQualityThr
(ODMQT)
pcLowerThresholdUL UL Rx Level Diff
RXQualDHR (0x39)
bcfAbisIF bcfTslShift (LUDHR)
OSCMultiplexingUL pcUpperThresholdDL OSC Modulation loss

RXLevelWindow RxQualDhr
csDapID (0x3A)
(OMLW) (UDDHR)
CSDAP Penalty count

pcUpperThresholdUL
(0x3B)
RxQualDhr
Demultiplexing (UUDHR)
General TRX
OSCDemultiplexingUL trxOSCCapability Fast AVE of DHR UL

trxStartingMode ()
RxLevMargin (ERO) (-)
(ODMRG)
AMR FR DHR MUX
()
OSCDhrDemultiplexing
RXQualityThr AMR FR DHR MUXL
(ODDQT) ()
For internal use

Configuration Management
limForTriggeringOscDhr
Limit for Triggering OSC DHR Multiplexing
Multiplexing
object: BTS It determines the load threshold for triggering DHR multiplexing: if the
unit: % percentage of free FR TCH decreases below the value of this parameter,
DHR multiplexing procedure is attempted.
range: 0..100
Default value of the parameter disables DHR multiplexing in a BTS.
step: 1
To enable the DHR multiplexing the parameter must be set to value
default: 0 different than zero. Activation of the OSC feature is possible only if:
MML command: EQM, EQO - BCF site type is Flexi EDGE (version EX4.0)
MML abbr. name: DHRLIM - 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 This parameter determines the UL Rx Level criterion for searching
unit: dBm DHR multiplexing candidates (both 1st and 2nd candidate must fulfill
this criterion).
range: -110..-47
Only calls with UL Rx level greater than or equal to this threshold
step: 1 (and lower than -47dBm), can be regarded as DHR multiplexing
default: -85 candidates.
MML command: EHC, EHS, EHO
MML abbr. name: OMLT
oscDhrMultiplexingRxQualityThr OSC DHR Multiplexing Rx Quality Threshold

object: HOC This parameter determines the UL and DL Rx Quality criterion for
unit: - searching the 1st DHR multiplexing candidate (target channel).
range: 0..7 Only AMR HR calls with UL and DL Rx quality lower than or equal
to this threshold, can be regarded as the 1st DHR multiplexing
step: 1 candidate (target channel).
default: 0
MML command: EHC, EHQ, EHO
MML abbr. name: ODMQT
For internal use

oscMultiplexingUlRxLevelWindow OSC Multiplexing UL Rx Level Window

object: HOC This parameter determines the UL Rx Level Difference criterion
unit: dB for searching the 2nd DHR multiplexing candidate (connection to
be handed over to the target channel).
range: 0..20
Only AMR FR/HR connections having UL RxLev within the
step: 1 window defined based on this parameter and UL RxLev of the 1st
default: 10 candidate may be regarded as 2nd DHR multiplexing candidates.
MML command: EHC, EHS, EHO
MML abbr. name: OMLW
Multiplexing Window for 2nd

candidate
RxLev
RxLev1st - Window UL RxLev1st RxLev1st + Window + Max Power Reduction2nd
For internal use

oscDemultiplexingUlRxLevMargin OSC Demultiplexing UL Rx Level Margin

object: HOC This parameter determines the UL Rx Level Difference
unit: dB criterion for DHR demultiplexing HO.
range: 0..63 If difference between UL Rx Levels of DHR paired connections
exceeds the value of this parameter, the connection with
step: 1 higher RxLev is handed over to non-DHR mode.
default: 14 This parameter should always be set to higher values than
MML command: EHC, EHS, EHO OSC Multiplexing UL Rx Level Window.
MML abbr. name: ODMRG
oscDhrDemultiplexingRxQualityThr OSC DHR Demultiplexing Rx Quality Threshold

object: HOC This parameter determines the UL and DL Rx Quality
unit: - thresholds for DHR demultiplexing HO.
range: 0..7 If UL or DL Rx quality of DHR connection reaches or exceeds
this threshold, demultiplexing HO to non-DHR mode is
step: 1 attempted (DHR demultiplexing HO may be prevented if AMR
default: 3 Unpacking Optimization feature is enabled and RxQual or
MML command: EHQ, EHO RxLev degrades too much).
MML abbr. name: ODDQT 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 This parameter determines DL Rx Quality threshold for inter-cell HO
unit: - for DHR connections.
range: 0..7 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).
step: 1
Rule: This parameter should always be set to higher value than OSC
default: 4 Demultiplexing Rx Quality Threshold.
MML abbr. name: TDRQD
thrUlRxQualDhr Threshold UL RxQual DHR

object: HOC This parameter determines UL Rx Quality threshold for inter-cell HO
unit: - for DHR connections.
range: 0..7 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).
step: 1
Rule: This parameter should always be set to higher value than OSC
default: 4 Demultiplexing Rx Quality Threshold.
MML abbr. name: TURQD
For internal use

pcLowerThresholdDlRxQualDhr PC Lower Threshold DL RxQual DHR

object: POC This parameter determines DL Rx Quality threshold for BTS power
unit: - increase for DHR connections.
range: 0..7 Rule: setting of this parameter should be consistent with setting of
OSC Demultiplexing Rx Quality Threshold, Threshold DL RxQual
step: 1 DHR and PC Upper Threshold DL RxQual DHR.
default: 3 Recommendation: it is recommended to set this parameter to
MML command: EUC, EUO, EUQ value lower than OSC Demultiplexing Rx Quality Threshold to
MML abbr. name: LDDHR trigger power control action before attempting the demultiplexing
HO.
pcLowerThresholdUlRxQualDhr PC Lower Threshold UL RxQual DHR

object: POC This parameter determines UL Rx Quality threshold for BTS power
unit: - increase for DHR connections.
OSC Demultiplexing Rx Quality Threshold, Threshold UL RxQual
step: 1 DHR and PC Upper Threshold UL RxQual DHR.
default: 3 Recommendation: it is recommended to set this parameter to
MML command: EUC, EUO, EUQ value lower than OSC Demultiplexing Rx Quality Threshold to
MML abbr. name: LUDHR trigger power control action before attempting the demultiplexing
HO.
For internal use
pcUpperThresholdDlRxQualDhr PC Upper Threshold DL RxQual DHR

object: POC This parameter determines DL Rx Quality threshold for BTS power
unit: - decrease for DHR connections.
OSC Demultiplexing Rx Quality Threshold, Threshold DL RxQual
step: 1 DHR and PC Lower Threshold DL RxQual DHR.
default: 0
MML command: EUC, EUO, EUQ
MML abbr. name: UDDHR
pcUpperThresholdUlRxQualDhr PC Upper Threshold UL RxQual DHR

object: POC This parameter determines UL Rx Quality threshold for BTS power
unit: - decrease for DHR connections.
OSC Demultiplexing Rx Quality Threshold, Threshold UL RxQual
step: 1 DHR and PC Upper Threshold UL RxQual DHR.
default: 0
MML command: EUC, EUO, EUQ
MML abbr. name: UUDHR
For internal use

trxOSCCapability TRX OSC Capability

object: TRX This parameter indicates whether TRX supports OSC feature.
unit: - This is read-only parameter. Its value is set by the system.
range: 0..4 Rule:
step: 1 0 - TRX is not OSC capable
default: 0 1 - TRX is OSC capable
MML command: ERO 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 This parameter indicates the mode (EGPRS or OSC) in which the
unit: - 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.
range: 0, 1
Rule:
step: 1
0 - EGPRS starting mode, in this mode 1st generation Flexi EDGE
default: - 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 This parameter determines the maximum allowed difference between UL RxLev
unit: - Change Rates of DHR multiplexing candidates. BSC rejects DHR multiplexing if
UL RxLev Change Rates difference is greater than the value of this parameter.
range: 0..63
Rule: the lower the value of this parameter the more stringent criterion for DHR
step: 1 multiplexing and lower OSC usage. Setting this parameter to higher values may
default: 10 result in higher number of DHR multiplexing HO but may also lead to increase
number/id: 0x38 of the DHR demultiplexing HO due to UL RxLev Unbalance.
UL RX LEVEL DIFF
object: UTPFIL This parameter allows for adjusting the algorithm for MS Power Optimization in
unit: dB DHR Multiplexing HO – it determines how much initial UL Rx Level of the 2nd
DHR multiplexing candidate may differ (be higher or lower) from UL RxLev of
range: 0..63 the 1st DHR multiplexing candidate.
step: 1
default: 0
number/id: 0x39
For internal use

OSC MODULATION LOSS

object: UTPFIL This parameter allows for adjusting the algorithm for BTS Power
unit: dB Optimization in DHR Multiplexing HO – it allows to tune the value of extra
power increase applied in DL during DHR multiplexing HO to compensate
range: 0..63 the loss resulting from DHR multiplexing.
step: 1
default: 3
number/id: 0x3A
CSDAP PENALTY COUNT

object: UTPFIL Amount of multiplexing attempts when CSDAP allocation is avoided after
unit: - unsuccessful CSDAP allocation – the pairs with the 1st candidate having
already been assigned CSDAP resource (OSC-1 sub-channel) are
range: 0..255 preferred.
step: 1
default: 5
number/id: 0x3B
For internal use

FAST AVE OF DHR UL

object: UTPFIL This parameter determines whether fast averaging is used in
unit: - UL power control and handover evaluation of DHR
connections.
range: 0 (fast averaging disabled)
Since DHR multiplexing may result in significant changes of
1 (fast averaging enabled) Rx quality it is recommended to enable fast averaging for
default: 1 DHR connections.
number/id: tbd
AMR FR DHR MUX

object: UTPFIL This parameter allows for preventing AMR FR-to-DHR
unit: - multiplexing HO. Direct switching from AMR FR to DHR
mode may result in “too high” degradation of user perceived
range: 0 (AMR FR->DHR forbidden) quality. Disabling this type of transition allow avoiding this
1 (AMR FR->DHR allowed) potential degradation. On the other hand, preventing AMR
default: 1 FR-to-DHR multiplexing HO limits the list of multiplexing
candidates what may result in lower DHR utilization.
number/id: tbd
For internal use

AMR FR DHR MUX

object: UTPFIL This parameter allows for preventing AMR FR-to-DHR
unit: - multiplexing HO. Direct switching from AMR FR to DHR
mode may result in “too high” degradation of user perceived
range: 0 (AMR FR->DHR forbidden) quality. Disabling this type of transition allow avoiding this
1 (AMR FR->DHR allowed) potential degradation. On the other hand, preventing AMR
default: 1 FR-to-DHR multiplexing HO limits the list of multiplexing
candidates what may result in lower DHR utilization.
number/id: tbd
For internal use

Parameter name Description

PC Lower Thresholds Lev UL/DL Determines Rx level threshold for a uplink/downlink power
Rx Level increase. This also applies to DHR connections.
PC Upper Thresholds Lev UL/DL Determines Rx level threshold for a uplink/downlink power
Rx Level decrease. This also applies to DHR connections.
Threshold Level Determines uplink/downlink Rx level threshold for triggering the
Uplink/Downlink Rx Level inter-cell handover due to Rx level. This also applies to DHR
connections.
Intra HO Threshold Rx Qual Determines downlink and uplink Rx quality threshold for the
AMR FR packing HO (AMR FR to AMR HR). This is also used as a threshold
for 2nd 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 Determines the limit of the uplink and downlink Rx quality for
AMR quality based intra-cell HOs. If averaged uplink or downlink Rx
quality is higher than this parameter, the quality based intra-cell
(AMR Unpacking Optimization HOs are not allowed. This also prevents DHR demultiplexing HO
BSS21120) in poor Rx quality conditions.
Intra HO Lower Rx Level Limit Determines the lower limit for uplink and downlink Rx level for
AMR HR quality based intra-cell HOs for AMR HR mode. If averaged uplink
or downlink Rx level is lower than this parameter, the quality
(AMR Unpacking Optimization based intra-cell HOs for AMR HR calls are not allowed. This also
BSS21120) prevents DHR demultiplexing HO in poor Rx level conditions.
Determines the upper limit for uplink and downlink Rx level for
quality based intra-cell HOs for AMR HR mode. If averaged uplink
Intra HO Upper Rx Level Limit or downlink Rx level is higher than this parameter, the quality
AMR HR based intra-cell HOs for AMR HR calls are not allowed. This is
(AMR Unpacking Optimization also used to determine the target channel mode (AMR FR or AMR
BSS21120) 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.
Determines the Rx level threshold for triggering the unpacking HO
Rx Level AMR HR Unpacking - if uplink or downlink Rx level is lower than the value of this
Threshold (UTPFIL parameter) parameter the intra-cell HO from AMR HR to AMR FR is attempted.
(Improved AMR Packing and This is re-used to trigger also DHR demultiplexing HO. Setting of
Unpacking BSS21483) this parameter should be aligned with oscMultiplexUlRxLevThr
and oscDemultiplexUlRxLevMarg.
For internal use

id CSDAP ID
object: CSDAP CSDAP ID allows to identify the dynamic Abis pool in the BSC. The identification
range: 1..1000 number must be unique within the BSC.
step: 1
MML commands: ESE, ESV, ESM, ESI
MML abbreviated name: ID
circuitGroupNumber Circuit group number

object: CSDAP Circuit group number identifies the circuit group associated to the CSDAP. Circuit
range: 0..65535 group (CGR) represents resources available on A interface as well as corresponding
MML commands: – 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
MML abbreviated name: – 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
Note: This is hidden parameter. CSDAP creation.
pcmCircuit_ID PCM Circuit ID

object: CSDAP PCM circuit ID indicates the number of Abis interface line (ET-PCM) where CSDAP is
range: 0..3391 created.
MML commands: ESE, ESM, ESI, WUP PCM circuit ID is part of hidden circuit (CRCT) parameter which allows to indicate the
MML abbreviated name: CRCT 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.
NOTE:
2048..3391 is reserved for T1 (OC-3) Thus circuit can have the following structure:
administration area circuit = pcmCircuit_ID – firstTSL – lastTSL or
For internal use circuit = pcmCircuit_ID – firstTSL – size
firstTSL First Timeslot

object: CSDAP First timeslot indicates the position on Abis interface line (defined by means of
range: 1..31 (E1) pcmCircuit_ID) of the first timeslot of the CSDAP.
1..24 (T1) This parameter can be modified by entering a new value using parameter
MML commands: ESE, ESM, ESI newFirstTimeSlot (NFT). By entering a number smaller than the first timeslot the pool
MML abbreviated name: CRCT 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).
lastTSL Last Timeslot

object: CSDAP Last timeslot indicates the position on Abis interface line (defined by means of
range: 1..31 (E1) pcmCircuit_ID) of the last timeslot of the CSDAP. The parameter is optional as the
1..24 (T1) size of CSDAP can be also defined explicitly by using parameter pool size (in addition
MML commands: ESE, ESM, ESI to first timeslot).
MML abbreviated name: CRCT 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).
poolSize Pool size

object: CSDAP Pool size defines the size of the CSDAP. The parameter is optional as it can be
range: 1..31 (E1) replaced with the parameter last timeslot.
1..24 (T1)
MML commands: ESE, ESI
MML abbreviated name: CRCT
For internal use
bcfAbisIF BCF Abis IF

object: CSDAP BCF Abis interface allows to define at BCF side the number of Abis interface line
range: 1..16 where the CSDAP is created.
MML commands: ESE, ESM, ESI
MML abbreviated name: BAIF
bcfTslShift BCF Timeslot Shift

object: CSDAP BCF timeslot shift allows to define the offset between ET-PCM timeslots in BSC side
range: -30..30 and Abis IF timeslots in BCF side
default: 0
Step: 1
MML commands: ESE, ESM, ESI
MML abbreviated name: SHIFT
csDapId1..4 Attached CSDAP1..4

object: BCF Attached CSDAP1..4 indicates the number of CSDAP attached to the given BCF.
range: 1..1000 Up to 4 CSDAPs can be attached to BCF (but a single CSDAP can be connected to
MML command: EFC, EFO, EFM only one BCF).
MML abbreviated name: CSDAP1..4
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 value
name
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 CSDAP_RES_ALLOC_ATT_FOR_DHR
Search
011265
CSDAP
yes
011266
Free TCH ≤
Search Candidates Legacy no
DHR Limit For Start
FR TCH candidates Found? Abis?
multiplexing
Resources
004235
HO_ATTEMPT_FROM_AMR_
011264
011263 HR_TO_DHR
DHR_MPLX_FAIL_DUE_
DHR_MULTIPLEXING_
TCH_RES
ATTEMPTS
011267
51014
HO to chosen
TCH
51013 011266
HO_FROM_AMR_HR_TO_DHR_SUCC
INTRA_HO_FROM_AMR_HR_TO_DHR
OSC call no
004237 Legacy
conversion
51216 Abis?
done
011266 011267
yes
Activate
CSDAP
For internal use

Call conversion to OSC – Legacy Abis
Searching for OSC-0 Searching for OSC-1
Candidate found
DHR Limit For FR
TCH Resources
011263
Free TCH ≤
yes yes
2nd Call in yes yes yes
UL&DL
Call in UL UL&DL AMR UL&DL
qual ≤
AMR-HR? level ≥ a quality ≤ b (FR-HR)? lev ≥ a
IHRF
no no no connection
011264 In defined
Window?
Intra-cell HO
counters
4237/51216
011266 011267 004239

011266 011267 Pair found
end 004235
no no
Activate CSDAP 1way

51013
Activate CSDAP 2 ways
no 011265
To moving call
HO command
multiplexing
Channel yes
OSC started
Balance the CSDAP yes HO yes CSDAP
Start of
yes
activation
Call to same activation successful? Found?
Success?
RXLevel successful?
51014
yes
*
Balance system
* Find resources
no
From USC connection
With CSDAP
Send over air interface
1266
Power commands
Counter
A = OSC Multiplexing UL Rx Level Threshold
Legacy Abis processes
B = OSC DHR Multiplexing Rx Quality Threshold
Window = multiplexing window (c) =
For internal use Rxlev1-window < rxlev2 < rxlev1 +window+ max pwr red
BSS21309: Orthogonal subchannel with SAIC MS
‘122 OSC RX Quality measurement’ collects statistics of BSS21309: Orthogonal subchannel with SAIC MS’ introduce a set of counters in ‘1
received signal quality both in uplink and downlink directions Traffic Measurement’ ‘2 Resource Availability Measurement’ and ‘4 Handover
for each AMR HR bit rate for double half rate calls. The Measurement’ for feature performance monitoring.
information is collected from each transceiver (TRX) KPIs:
separately. Total DHR Multiplexing Failure Rate
The Bit Error Ratio (BER) based signal quality counters ‘1 Traffic Measurement’ DHR Multiplexing Failure Rate due to Lack of Suitable Pair
correspond to the eight RX Quality bands. The counters are DHR_MULTIPLEXING_ATTEMPTS 001263 DHR Multiplexing Failure Rate due to CSDAP
updated by the RX Quality values as measured by the MS DHR_MULTIPLX_FAIL_DUE_TCH_RES 001264 DHR Multiplexing Failure Rate due to Other Reasons
(downlink) and BTS (uplink) and reported in the radio link CSDAP_RES_ALLOC_ATT_FOR_DHR 001265 CSDAP Allocation Failure Rate
measurement messages. The RX Quality reports are DHR_MPLX_FAIL_DUE_CSDAP_RES 001266
collected on the traffic channels (TCHs). DHR_MPLX_FAIL_DUE_OTHER 001267
OSC_AMR_HR_475_UL_RXQUAL_0 122000 KPI s:
OSC_AMR_HR_475_DL_RXQUAL_0 122001 Average DHR Traffic
‘2 Resource Availability Measurement’
… DHR Usage
AVE_BUSY_DHR_TCH 002094
OSC_AMR_HR_475_UL_RXQUAL_7 122014 AVE_BUSY_DHR_TCH_DENOM 002095
OSC_AMR_HR_475_DL_RXQUAL_7 122015 PEAK_BUSY_DHR_TCH 002096 KPIs:
OSC_AMR_HR_515_UL_RXQUAL_0 122016 AMR HR-to-DHR HO Success Rate
OSC_AMR_HR_515_DL_RXQUAL_0 122017
AMR HR-to-DHR HO Rate
…
AMR FR-to-DHR HO Success Rate
OSC_AMR_HR_515_UL_RXQUAL_7 122030
AMR FR-to-DHR HO Rate
OSC_AMR_HR_515_DL_RXQUAL_7 122031 ‘4 Handover Measurement’
OSC_AMR_HR_590_UL_RXQUAL_0 122032 RxQual DHR Demultiplexing HO
KPIs: HO_ATTEMPT_FROM_AMR_HR_TO_DHR 004235
Success Rate
OSC_AMR_HR_590_DL_RXQUAL_0 122033 OSC DL/UL HO_ATTEMPT_FROM_AMR_FR_TO_DHR 004236
… UL RxLev Difference DHR
Rx Quality HO_FROM_AMR_HR_TO_DHR_SUCC 004237
Demultiplexing HO Success Rate
OSC_AMR_HR_590_UL_RXQUAL_7 122046 Distribution HO_FROM_AMR_FR_TO_DHR_SUCC 004238
OSC_AMR_HR_590_DL_RXQUAL_7 122047 RxLev DHR Demultiplexing HO Success
UNSUCC_HO_TO_DHR_DUE_MISMATCH 004239
Rate
OSC_AMR_HR_670_UL_RXQUAL_0 122048 HO_ATT_FROM_DHR_DUE_RX_QUAL 004240
OSC_AMR_HR_670_DL_RXQUAL_0 122049 DHR Demultiplexing HO Success Rate
HO_ATT_FROM_DHR_DUE_RXLEV_DIF 004241
… DHR Demultiplexing HO type (due to
HO_FROM_DHR_DUE_RX_QUAL_SUCC 004242
RxQual) Distribution
HO_FROM_DHR_DUE_RXLEV_SUCC 004243
OSC_AMR_HR_670_DL_RXQUAL_7 122063 DHR Demultiplexing HO type (due to UL
HO_ATT_FROM_DHR_DUE_RX_LEV 004251
RxLev difference) Distribution
HO_FROM_DHR_DUE_RX_LEV_SUCC 004252
OSC_AMR_HR_740_DL_RXQUAL_0 122065 DHR Demultiplexing HO type (due to
…
RxLev) Distribution
OSC_AMR_HR_740_DL_RXQUAL_7 122079
For internal use

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

Failure Rate due to DHR_MULTIPLEXING_ATTEMPTS (1263) AMR calls to DHR caused by
Other Reasons unsuitable state of the call (e.g.
OSC HO is started by RRM that is
For internal use
not aware of the call phase and
98 © Nokia Siemens Networks Presentation / Author / Date might end up to situation where
KPI Formula Meaning
CSDAP  DHR_MPLX_FAIL_DUE_CSDAP_RES/CSDAP  Gives the CSDAP Allocation
Allocation _RES_ALLOC_ATT_FOR_DHR Failure ratio due to lack of CSDAP
Failure Rate for OSC-1 subchannel
AMR HR-to-DHR  HO_FROM_AMR_HR_TO_DHR_SUCC/HO_A  Gives success rate of multiplexing

HO Success TTEMPT_FROM_AMR_HR_TO_DHR AMR HR calls to DHR as the ratio
Rate between succesful multiplexing
HOs from AMR HR to DHR and
number of multiplexing attempts
AMR HR-to-DHR  HO_ATTEMPT_FROM_AMR_HR_TO_DHR/(H  Gives the percentage of AMR HR-
HO Rate O_ATTEMPT_FROM_AMR_HR_TO_DHR+ to-DHR HO Attempts
HO_ATTEMPT_FROM_AMR_FR_TO_DHR)
AMR FR-to-DHR  (HO_FROM_AMR_FR_TO_DHR_SUCC/HO_A  Gives success rate of multiplexing
HO Success TTEMPT_FROM_AMR_FR_TO_DHR AMR FR calls to DHR as the ratio
Rate between succesful multiplexing
HOs from AMR FR to DHR and
number of multiplexing attempts
AMR FR-to-DHR  HO_ATTEMPT_FROM_AMR_FR_TO_DHR/(H  Gives the percentage of AMR FR-
HO Rate O_ATTEMPT_FROM_AMR_HR_TO_DHR+ to-DHR HO Attempts
HO_ATTEMPT_FROM_AMR_FR_TO_DHR)
For internal use

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

Demultiplexing (HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ HO attempts due to UL RxLev
HO type (due to ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_AT difference in the all causes of
T_FROM_DHR_DUE_RX_LEV ) demultiplexing
UL RxLev
difference)
Distribution
DHR  HO_ATT_FROM_DHR_DUE_RX_LEV /  Gives the ratio of demultiplexing
Demultiplexing (HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ HO attempts triggered by Rx
HO type (due to ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_AT Level criterion (when Improved
T_FROM_DHR_DUE_RX_LEV) AMR Packing and Unpacking
RxLev) (BSS21483) is active) in the all
Distribution causes of demultiplexing
Average CSDAP  AVERAGE_CSDAP_SUBTSL_USAGE/AVERA  Gives the average usage of

8kbit/s subTSL GE_CSDAP_SUBTSL_USAGE_DEN CSDAP 8kbit/s subTSL
Usage
Peak CSDAP  PEAK_CSDAP_8_KBIT/S_SUBTSL_USAGE /  Gives the peak utilization of
utilization TOTAL_PCM_8_KBIT/S_SUBTSL_IN_CSDAP CSDAP resources
For internal use
KPI Formula Meaning
UL RxQual  E.g.  Gives the ratio of samples with
distribution [(OSC_AMR_HR_475_UL_RXQUAL_6+OSC_ given RxQual value to all samples
AMR_HR_515_UL_RXQUAL_6+OSC_AMR_H in UL, e.g. UL Rxqual 6&7 Rate
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_
AMR_HR_515_UL_RXQUAL_0+OSC_AMR_H
QUAL_0)+ …
+(OSC_AMR_HR_475_UL_RXQUAL_7+OSC_
AMR_HR_515_UL_RXQUAL_7+OSC_AMR_H
QUAL_7)]
All AMR codecs are included in the formula – not only the active ones
For internal use

KPI Formula Meaning
DL RxQual  E.g.:  Gives the ratio of samples with
distribution [(OSC_AMR_HR_475_DL_RXQUAL_6+OSC_A given RxQual value to all samples
MR_HR_515_DL_RXQUAL_6+OSC_AMR_HR in DL, e.g. DL Rxqual 6&7 Rate
_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)]
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
0th week
• Site selection (customer of own team) and test preparation together with the data (initial parameters for OSC & CSDAP or
PacketAbis)
1st 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)
nd
2 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.)
3rd – 6th 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

Dynamic Abis – Compresses Abis
 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
For internal use

Packet Abis - overview
 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
For internal use

Packet Abis - calculator
 The screenshots below show the set of inputs in Packet Abis calculator which are directly
related to OSC
This section allows to define

This section allows to define codec distribution
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 what’s given)
Note: contributions of standard
HR codecs as well as OSC-HR
are to ne entered in column “HR”
 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
For internal use

Packet Abis – example calculations
 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:
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 60% FR / 20% HR / 20% OSC (with OSC) => 16.37 Erl/cell
Calculations:
Dynamic Abis: 18 TSL (TCH), 5 TSL (sign; 9 TRXSIG@32+OMUSIG@32), 6 TSL (EDAP) Dynamic Abis: 2 TSL (CSDAP) + 29 TSL (TCH+sign+EDAP)
=> 1 E1 line (29 TSL) => still 1 E1 (31 TSL) but fully loaded E1 (!!!)
Packet Abis: 1.31 Mbps Packet Abis: 1.31 Mbps
 CS traffic increase due to higher OSC penetration:

60% FR / 20% HR / 20% OSC (with OSC) => 18.38 Erl/cell 40% FR / 20% HR / 40% OSC (with OSC) => 24.63 Erl/cell
Dynamic Abis: 2 TSL (CSDAP) + 29 TSL (TCH+sign+EDAP) Dynamic Abis: 4 TSL (CSDAP) + 31 TSL (TCH+sign+EDAP)
=> still 1 E1 (31 TSL) but fully loaded E1 (!!!) => 2 E1 (35 TSL) already needed (!!!)
Packet Abis: 1.36 Mbps => compressed mapping to be checked
Packet Abis: 1.51 Mbps (still a lot of space for more traffic)
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 toForNEI Packet
internal use Abis for further details concerning Packet Abis bandwidth estimations (incl.
the most up-to-dated results of bandwidth estimation).
Packet Abis – summary
 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
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
For internalManager
use reports (after HW inventory has been uploaded from each BTS site via
BSC to NetAct 130 database)
© Nokia Siemens Networks Presentation / Author / Date
Prerequisites (3)
 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
Dual duplexer module
• Dual TRX1 with

Sector 1 EGPRS supported
Dual TRX module
Sector 2 • Dual TRX2 with OSC

supported
Sector 3 • Dual TRX3 with OSC or

EGPRS supported
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_ This counter provides the number of DHR multiplexing procedures triggered by
ATTEMPTS (001263) load criterion (threshold Limit for Triggering OSC DHR Multiplexing).
(Traffic Measurement) 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 This counter provides the number of DHR multiplexing failures due to lack of
_TCH_RES (001264) suitable DHR multiplexing candidates.
(Traffic Measurement) 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
For internal use met and it may happen that all SAIC capable MS are already in DHR mode and
135 © Nokia Siemens Networks
therefore no even 1Presentation / Author / Date
st multiplexing candidate can be found.
New counters (2)
DHR_MPLX_FAIL_DUE_C This counter provides the number of CSDAP resources allocation failures
SDAP_RES (001266) for DHR.
(Traffic Measurement) 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 This counter provides the number of DHR multiplexing failures due to
THER (001267) unsuitable state of the call.
(Traffic Measurement) 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 This counter provides the number of CSDAP resources allocation
T_FOR_DHR (001265) attempts for DHR.
(Traffic Measurement) 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
For internal use R_DHR)
New counters (3)
AVE_BUSY_DHR_TCH This counter provides the sum of the number of busy DHR TCHs
(002094) (aggregated for the whole observation time over 20-second periods).
(Resource Availability Note: two DHR connections paired in one TCH/H channel are
Measurement) 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 This counter provides the number of measurement samples for busy DHR
ENOM (002095) TCHs (the number of 20-second periods comprised in observation period)
(Resource Availability Trigger event: every 20 seconds when sample of the number of busy
Measurement) 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 This counter provides the peak number of busy DHR TCHs within an
(002096) observation period. See note for AVE_BUSY_DHR_TCH.
(Resource Availability Trigger event: when the latest measured number of busy DHR TCHs
Measurement) For internal use exceeds the previous peak value.
137 Use case:
© Nokia Siemens Networks monitoring of the
Presentation peak
/ Author / Date DHR traffic and the highest DHR usage
New counters (4)

DHR_PAIR_AVERAGE_ This counter provides the sum of the OSC DHR pair lifetimes.
LIFETIME (002101) Trigger event: updated every time an OSC DHR connection is released
(Resource Availability successfully and another connection still remains in the TCH/F. The counter
Measurement) 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 This counter provides the denominator for the average OSC DHR pair
ME_DENOM (002102) lifetime calculation.
(Resource Availability Trigger event: is increased by one when an OSC DHR connection is
Measurement) 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 This counter provides the number of DHR multiplexing handover attempts
MR_HR_TO_DHR for an AMR HR connections.
(004235) Trigger event: DHR multiplexing HO is attempted for connection being in
AMR HR mode (appropriate 2nd candidate has already been found)
(Handover Measurement)
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 This counter provides the number of successful AMR HR-to-DHR
_DHR_SUCC (004237) multiplexing handovers.
(Handover Measurement) 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 This counter provides the number of DHR multiplexing handover attempts
MR_FR_TO_DHR from an AMR FR connections.
(004236) Trigger event: DHR multiplexing HO is attempted for connection being in
AMR FR mode (appropriate 2nd 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_ This counter provides the number of successful AMR FR-to-DHR
DHR_SUCC (004238) multiplexing handovers.
(Handover Measurement) 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 This counter provides the number of failed DHR multiplexing handovers
UE_MISMATCH (004239) due to CSDAP conflict between BSC and BTS.
(Handover Measurement) 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 This counter provides the number of DHR demultiplexing HO attempts
DUE_RX_QUAL (004240) triggered by Rx Quality criterion.
(Handover Measurement) 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 This counter provides the number of successful DHR demultiplexing HO
X_QUAL_SUCC (004242) triggered by Rx Quality criterion.
(Handover Measurement) 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 This counter provides the number of DHR demultiplexing HO attempts
E_RXLEV_DIFF (004241) triggered by UL Rx Level Difference (Unbalance) criterion.
(Handover Measurement) 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)
XLEV_SUCC (004243) triggered by UL Rx Level Difference criterion.
(Handover Measurement) 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
- DHR Demultiplexing HO Success Rate: hsr_1005
For internal use
New counters (10)
HO_ATT_FROM_DHR This counter provides the number of DHR demultiplexing HO attempts
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)
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 - DHR Demultiplexing HO Success Rate: hsr_1005
New counters (11)
INTRA_HO_FROM_AMR_H This counter provides the number of successful intra-cell AMR HR-to-DHR multiplexing HOs.
R_TO_DHR (051216) Trigger event: HANDOVER PERFORMED message is sent to the MSC.
(BSC Level Clear Code Use case: monitoring of the number of AMR HR-to-DHR multiplexing HOs (analogous to the
Measurement) counter HO_FROM_AMR_HR_TO_DHR_SUCC from Handover Measurements)
INTRA_HO_FROM_AMR_F This counter provides the number of successful intra-cell AMR FR-to-DHR multiplexing HOs.
R_TO_DHR (051217) Trigger event: HANDOVER PERFORMED message is sent to the MSC.
(BSC Level Clear Code Use case: monitoring of the number of AMR HR-to-DHR multiplexing HOs (analogous to the
Measurement) counter HO_FROM_AMR_FR_DHR_SUCC from Handover Measurements)
INTRA_HO_FROM_DHR_D This counter provides the number of successful intra-cell DHR demultiplexing HO triggered
UE_RX_QUAL (051218) by Rx Quality criterion.
(BSC Level Clear Code Trigger event: HANDOVER PERFORMED message is sent to the MSC.
Measurement) Use case: monitoring of the number of AMR HR-to-DHR multiplexing HOs (analogous to the
counter HO_FROM_DHR_DUE_RX_QUALITY_SUCC from Handover Measurements)
UE_LEV_DIFF (051219) by UL Rx Level Difference criterion.
counter HO_FROM_DHR_DUE_RXLEV_SUCC from Handover Measurements)
UE_RX_LEV (051221) by Rx Level criterion (when Improved AMR Packing and Unpacking (BSS21483) is active).
For internal use counter HO_FROM_DHR_DUE_RX_LEV_SUCC from Handover Measurements)
New counters (12)
TOTAL_PCM_SUBTSLS This counter provides the total number of 8 kbps PCM subTSL in CSDAP.
_IN_CSDAP (121000) Trigger event: The counter is updated by the size of the CSDAP once in a
(CSDAP Measurement) measurement period
Use case: monitoring of the usage of CSDAP
AVERAGE_CSDAP_SUB This counter provides the sum of the number of busy 8kbit/s subTSL in
TSL_USAGE (121001) CSDAP (aggregated for the whole observation time over 20-second periods)
(CSDAP Measurement) 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 This counter provides the number of measurement samples for busy 8kbit/s
TSL_USAGE_DEN subTSL in CSDAP (the number of 20-second periods comprised in
(121002) observation period)
Trigger event: every 20 seconds when sample of the number of busy 8kbit/s
(CSDAP Measurement)
subTSL in CSDAP is taken.
Use case: calculations of Average 8kbit/s subTSL in CSDAP Usage: trf_1000
PEAK_CSDAP_SUBTSL This counter provides the peak usage of 8kbit/s subTSL in CSDAP.
_USAGE (121003) Trigger event: when the latest measured number of busy 8kbit/s subTSL
(CSDAP Measurement) exceeds the previous peak value.
For internal use
146 UseNetworks
© Nokia Siemens case: monitoring of/ Author
Presentation the peak
/ Date usage of 8kbit/s subTSL in CSDAP.
New counters (13)
Measurements Description
OSC RX Quality This group of counters collects UL and DL Rx Quality statistics for DHR
Measurements mode.
There are separate counters (each comprising 8 RxQual bins) for each
counters: 122000-122079 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
 Impact of the OSC feature on overall network performance depends on the

operator’s 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
Feature impact How to measure

Lower TCH blocking KPIs:
 TCH Call Blocknig (blck_8i)
Higher TCH Traffic Carried and/or KPIs:

Lower TSL Utilization by CS Traffic  Average CS Traffic (trf_202a)
Note: depending on the amount of CS traffic  Normal TCH Usage Ratio for CS (trf_197a)
offered to the network
The feature impact highly depends on the DHR mode usage (determined by SAIC MS penetration,
network scenario and OSC-related parameters setting).
For internal use

Larger PS Territory KPIs:
Note: resulting from lower TSL utilization by  Average Available PS Territory Size (ava_44)
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
Lower TBF Multiplexing KPIs:

Note: resulting from larger PS Territory  Average DL TBF per TSL (tbf_38c)
Lower Multislot Allocation Soft KPIs:

Blocking  DL Multislot Soft Blocking (blck_33c) – a ratio of un-
Note: the lower probability that an MS will be served TSL requests to all requests in DL
assigned less TSLs than it could be
according to its multislot class results from
larger PS Territory
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:
Note: resulting from larger PS Territory  Distribution of DL x TSL Allocations (msl_4c)
 Average Number of Allocated TSL in DL (msl_12c)
Higher DLDC Allocation Success Ratio KPIs:
Note: resulting from larger PS Territory  DLDC Allocation Success Ratio (dldc_3)
Higher LLC Data Throughput KPIs:

Note: resulting from lower Multislot Blocking  Volume Weighted LLC Throughput (llc_3a)
and lower TBF Multiplexing and assuming the  Weighted LLC Throughput for DLDC MS (dldc_4)
same radio conditions
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 KPIs:
Note: QPSK modulation and MU-MIMO concepts  DL Cumulative Level Ratio in Class X (dlq_2a)
used in DL and UL respectively, may result in  UL Cumulative Level Ratio in Class X (ulq_2a)
performance degradation of voice calls in DHR
mode.  DL and UL BER Distribution based on counters 014016..014148
and new OSC RX Quality Measurements (122000-122079)
It may, however, happen that with high DHR usage
resulting in lower TSL occupation (if served traffic  UL FER Distribution and UL Bad FER Ratio based on counters
does not increase) the overall interference level in 077015..077022
the network gets lower and quality statistics get  DL FER Distribution and DL Bad FER Ratio based on counters
better (decrease of interference level is higher than 077023..077030 and 077032..077039
degradation resulting from DHR mode itself).
No or slight degradation in MOS KPIs:

Drive tests needed
No or slightly increased Drop Call Ratio KPIs:

Note: resulting from poorer SACCH and FACCH  TCH Drop Call Ratio (dcr_8i)
performance in DHR mode and phenomena
described in note above
Increased number of intra-cell HOs KPIs:
Note: resulting from the fact that switching between  CELL_TCH_TCH _AT (004076)/Total Carried Traffic(trf_1)
non-DHR and DHR mode is realized via DHR
multiplexing/demultiplexing HOs
For internal use

Feature Performance Monitoring
Performance indicator How to measure
DHR Traffic KPIs:
Characteristics  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 KPIs:
Failure Rate  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
For internal use
to Performance Measurements
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 KPIs:
Rate  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 KPIs
Distribution  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
For internal use


OSC

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

OSC

Загружено:

Авторское право:

Доступные форматы

RG20 (BSS)

For internal use

BTS BTS BTS

BTS BTS BTS

Release SW: EX4.0 Not supported*** Not supported***

Release No SAIC indicating No No No OSS5.2 CD set 3

For internal use

Feature adds signaling support for new training

For internal use

For internal use

For internal use

 In RG20(BSS) the Orthogonal Sub-channel (OSC) feature introduces the new

 OSC feature increases hardware efficiency

For internal use

 OSC FR feature provides the same capacity as AMR HR but by

For internal use

 OSC exists of the following features:

 OSC requires Single Antenna Interference Cancelation (SAIC) receiver in mobile

For internal use

For internal use

 OSC concept in DL direction is based on QPSK

 QPSK modulation carries two orthogonal sub-

 Separate reception of two sub-channels is enabled

 Orthogonal sub-channel concept in UL direction is based on traditional GMSK

For internal use

 DHR multiplexing mode is triggered based on the Yes

• 0 = Only CSW used RTSLs are used (default)

For internal use

 Multiplexing is realized by handing over AMR HR/FR Yes

Yes suitable 2nd No

For internal use

Orthogonal Sub-channel Yes No

For internal use

ULRxLevMS2=Multiplexing UL RxLev Threshold

target channel candidate list:

sorted target channel candidate list:

the best target channel:

For internal use

Orthogonal Sub-channel Yes Load criterion No

 both AMR HR and FR calls are considered Yes suitable target No

 unless AMR FR to DHR HO is blocked with UTPFIL parameter

(AMR FR DHR MUX) Search for the

and DHR multiplexing HO

-47dBm > UL RxLev ≥ Multiplexing UL Rx Level Threshold ready

For internal use

(UL RxLev2nd+Current Power Reduction2nd)≤(UL RxLev1st +Multiplexing UL RxLev Window +

Multiplexing Window for 2nd

MS1 MS2 has been chosen as the 1st candidate

Multiplexing Window for MS3 MS4

RxLevMS2 - Window RxLevMS2 RxLevMS2 + Window + Max Power ReductionMS4

Orthogonal Sub-channel Yes Load criterion

OSC Half Rate with SAIC MS end

Search for the 1st

 Among all the connections meeting DHR channel)

multiplexing HO criteria the best 2nd candidate Yes suitable target No

 UL Rx Level Difference criterion

 UL Rx Level Change Rate criterion DHR multiplexing HO

ΔUL RXLEV CHANGE RATE =ULRxLevChangeRate1st-ULRxLevChangeRate2nd ready

For internal use

Orthogonal Sub-channel Yes Load criterion

OSC Half Rate with SAIC MS end

Search for the 1st

(|ΔULRXLEV| + |ΔUL RXLEV CHANGE RATE|) Yes suitable target No

Release SW: EX4.0 Not supported* Not supported*