Documente Academic
Documente Profesional
Documente Cultură
Orthogonal Sub-channel
BSS21309, BSS30385
Dependency table
DX200
MS SGSN MCS RAN NetAct
Platform
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.
Contents
Introduction
Feature details
Configuration management
Pilot results
Dimensioning aspects
Implementation aspects
PM counters
Feature impact analysis/feature performance monitoring
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
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
Searching for the best candidate to be handed over (the 2nd Search for the 1st
candidate (target
candidate) to the target channel)
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
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
RxLev
For internal use
18RxLev 1st - Siemens
© Nokia Window Networks UL RxLev
Presentation
1st RxLev
/ Author 1st + Window + Max Power Reduction2nd
/ Date
Orthogonal Sub-channel
OSC Half Rate with SAIC MS
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)
end
The best 2nd candidate is determined based on: Search for the
2nd candidate
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
HR multiplexing HR multiplexing
Orthogonal Sub-channel
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
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
ready
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
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?
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
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
3 2 1
4
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
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”
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 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
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
• HR utilization
De-
multiplexing
• 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%
• 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
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
OUTPUTS
message: OK
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
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
50 © Nokia Siemens Networks Presentation / Author / Date
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.
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
52 © Nokia Siemens Networks Presentation / Author / Date
Orthogonal Sub-channel
Access network dimensioning aspects
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
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
5 6
6 5
7 1
main TSC = 0 main TSC = 2 collision between main TSC of cell A (B)
and paired TSC of cell B (A)
• 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
• 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
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)
OSCDhrDemultiplexing
RXQualityThr AMR FR DHR MUXL
(ODDQT) ()
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
68 © Nokia Siemens Networks Presentation / Author / Date
Orthogonal Sub-channel
Configuration Management
RxLev
RxLev1st - Window UL RxLev1st RxLev1st + Window + Max Power Reduction2nd
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
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
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
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
TRANSCEIVER DATA
ADM.STATE OP.STATE
--------------------------------------
BCF-0300 UNLOCKED WO
SEG-0301 ESATERI241
BTS-0301 ESATERI241 UNLOCKED WO
TRX-001 EDGE UNLOCKED WO
BCSU-0
COMMAND EXECUTED
EEI:BTS=301;
COMMAND EXECUTED
GTRX Y (EDGE)
HRS Y PREF N
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
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
no 011265
To moving call
HO command
multiplexing
Channel yes
OSC started
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
96 © Nokia Siemens Networks Presentation / Author / Date
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
OSC_AMR_HR_670_UL_RXQUAL_7 122062
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
OSC_AMR_HR_740_UL_RXQUAL_0 122064
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_UL_RXQUAL_7 122078
OSC_AMR_HR_740_DL_RXQUAL_7 122079
All AMR codecs are included in the formula – not only the active ones
All AMR codecs are included in the formula – not only the active ones
#BCSU/BTS
•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
•Multiplexing attempts
• Multiplexing attempts are showing how many possible candidates are
available for OSC
•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.
• 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?
• 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.
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.)
• 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)
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)
• 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)
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
119 © Nokia Siemens Networks Presentation / Author / Date
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
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
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
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.
126 © Nokia Siemens Networks Presentation / Author / Date
the most up-to-dated results of bandwidth estimation).
Orthogonal Sub-channel
Abis dimensioning aspects
Packet Abis – summary
INTRA_HO_FROM_DHR_D This counter provides the number of successful intra-cell DHR demultiplexing HO triggered
UE_LEV_DIFF (051219) by UL Rx Level Difference 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_RXLEV_SUCC from Handover Measurements)
INTRA_HO_FROM_DHR_D This counter provides the number of successful intra-cell DHR demultiplexing HO triggered
UE_RX_LEV (051221) by Rx Level criterion (when Improved AMR Packing and Unpacking (BSS21483) is active).
(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
For internal use counter HO_FROM_DHR_DUE_RX_LEV_SUCC from Handover Measurements)
145 © Nokia Siemens Networks Presentation / Author / Date
Orthogonal Sub-channel
Performance Measurements
New counters (12)
Counter name Description
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.
Orthogonal Sub-channel
Performance Measurements
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)