04 Rn20114en16gla0 Osc+csdap

Nokia Academy
Orthogonal Sub-Channel (OSC) &

CSDAP
BSS Parameter Planning 2 [GSM 16]
RN2011-16A-GSM
RN20114EN16GLA0 © Nokia Solutions and Networks 2015

Copyright and confidentiality
The contents of this document are proprietary and Feedback may be used in Nokia Solutions and any kind, either express or implied, including, but not
confidential property of Nokia Solutions and Networks. Networks products and related specifications or other limited to, the implied warranties of merchantability and
This document is provided subject to confidentiality documentation. Accordingly, if the user of this fitness for a particular purpose, are made in relation to
obligations of the applicable agreement(s). document gives Nokia Solutions and Networks the accuracy, reliability or contents of this document.
feedback on the contents of this document, Nokia NOKIA SOLUTIONS AND NETWORKS SHALL NOT
Solutions and Networks may freely use, disclose, BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN
This document is intended for use of Nokia Solutions
reproduce, license, distribute and otherwise THIS DOCUMENT or for any loss of data or income or
and Networks customers and collaborators only for the
commercialize the feedback in any Nokia Solutions and any special, incidental, consequential, indirect or direct
purpose for which this document is submitted by Nokia
Networks product, technology, service, specification or damages howsoever caused, that might arise from the
Solutions and Networks. No part of this document may
other documentation. use of this document or any contents of this document.
be reproduced or made available to the public or to any
third party in any form or means without the prior
written permission of Nokia Solutions and Networks. Nokia Solutions and Networks operates a policy of This document and the product(s) it describes are
This document is to be used by properly trained ongoing development. Nokia Solutions and Networks protected by copyright according to the applicable laws.
professional personnel. Any use of the contents in this reserves the right to make changes and improvements
document is limited strictly to the use(s) specifically to any of the products and/or services described in this
Nokia is a registered trademark of Nokia Corporation.
created in the applicable agreement(s) under which the document or withdraw this document at any time
Other product and company names mentioned herein
document is submitted. The user of this document may without prior notice.
may be trademarks or trade names of their
voluntarily provide suggestions, comments or other
respective owners.
feedback to Nokia Solutions and Networks in respect of
The contents of this document are provided "as is".
the contents of this document ("Feedback"). Such
Except as required by applicable law, no warranties of
© Nokia Solutions and Networks 2015
2 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

Module Objectives
• After completing the module, the student will be able to:

- Describe the main functionality of Orthogonal Sub-Carrier (OSC)
- Explain how the call is transferred from AMR to Dual Half (DH) AMR
- Describe the DH power control principles
- Explain how the existing HO algorithms are applied in DH AMR handovers
- Explain the parameters related to OSC
- Describe the main functionality and parameters of CS Dynamic Abis Pool
(CSDAP)
- Explain the OSC Support for AMR-FR, OSC support for VAMOS handsets
and AQPSK support with VAMOS-2 handsets features

Module Contents
• Orthogonal Sub-Carrier (OSC) Feature Details

• Call setup from AMR to DHR AMR
• Power control
• Handover Control
• Configuration management
• CSDAP
• OSC Support for AMR-FR (RG20)
• OSC support for VAMOS handsets and AQPSK support with
VAMOS-2 handsets (RG30)

Module Contents

• Power control
• CSDAP

Orthogonal Sub-channel
Introduction
 Orthogonal Sub-Channel (OSC) is a voice capacity feature that allows assigning two AMR HR
connections on the same TCH/H channel (Double Half Rate mode)
• up to four AMR HR connections may be served by one radio timeslot
 OSC comprises the following features:
• OSC Double Half Rate with SAIC MS (BSS21309)
• Circuit Switched Dynamic Abis Pool (BSS30385)
- provisioning of the ‘additional’ Abis capacity required by the second OSC sub-channel (two
AMR connections paired in DHR mode on the same TCH/H requires two 16kbps Abis sub-
channels)
- either CSDAP or Packet Abis over IP/Eth (BSS21454) or Packet Abis over TDM BSS21440)
is a prerequisite for OSC Double Half Rate with SAIC MS feature
 OSC requires Single Antenna Interference Cancelation (SAIC) receiver in mobile stations
• BSC applies OSC only for MSs which indicate their SAIC support

Feature details
• Two AMR HR connections being allocated on the same TCH/H channel are regarded as Double Half
Rate calls
• 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
• sub-channel specific TSCs are optimized in TSC pairs for the lowest cross-correlation
• OSC-0 sub-channel is assigned a ‘legacy’ TSC and uses ‘legacy’ Abis transport resources
• OSC-1 sub-channel is assigned ‘pair-wise’ TSC and uses ‘additional’ Abis transport resources
• additional Abis transport capacity may be provided with CSDAP or Packet Abis
• OSC-0 and OSC-1 sub-channels have independent RR signaling
• A decision whether connection should be regarded as standard AMR HR call or DHR one is based
on the new OSC Neighboring Sub Channel Measurements IE being part of in Uplink Measurements
IE sent in existing Measurement Result message

Feature details
• Orthogonal Sub-channel concept in DL direction is based on

the adoption of the QPSK modulation
• 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 their
orthogonality achieved with appropriately selected TSCs
• BTS uses dynamically GMSK or QPSK modulation Table 1 Optimized TSC pairs for OSC
• if there is only one AMR HR connection in a TCH/H, the TSC for OSC-0 TSC for OSC-1
channel performs as a traditional AMR HR TCH 0 2
1 7
• if one of paired DHR connections is in DTX mode, 2 0
GMSK is used by the other one 3

4
4
3
5 6
6 5
7 1

Prerequisites
OSC Half Rate requires:

• Either UltraSite, Flexi EDGE, Flexi Multiradio, Flexi Multiradio 10 or Flexi Compact base
stations. In the UltraSite base station OSC Half Rate requires the use of UltraSite EDGE
TRX HW.
• MS must be SAIC (DARP or VAMOS) and AMR capable.
• AMR codec feature, because only AMR calls can be multiplexed into OSC.
• Packet Abis or CSDAP feature in case of Legacy Abis interface.

Module Contents

• Power control
• CSDAP

Orthogonal Sub-channel Report from
HO&PC
DHR multiplexing (1)
Load criterion No
• DHR multiplexing mode is triggered based on the load criterion fulfilled?
Yes end
• load criterion is checked with updated values of Rx Quality, Enter DHR multiplexing
Rx Level and power reduction mode
• interval is defined with UTPFIL parameter: DHR Search for the 1st
CANDIDATE LISTING INTERVAL candidate (target
channel)
• if the percentage of free FR TCHs decreases below DHR
Yes suitable target No
Limit For FR TCH Resources, the BTS enters DHR channel found?
multiplexing mode end
Search for the 2nd candidate
Yes suitable 2nd No

candidate
found?
end
DHR multiplexing HO of 2nd
candidate to the target channel
ready

HO&PC
Load criterion No
• Searching for the best target channel (the 1 st candidate) fulfilled?
Yes end
Enter DHR multiplexing
mode
Search for the 1st

candidate (target
channel)

channel found?
end
Yes suitable 2nd No

candidate
• the list of channels fulfilling above criteria is sorted in descending found?
order according to UL path-loss criterion (UL RxLev +
current power reduction) end
• the 1st channel in the list (with the lowest path-loss) is selected candidate to the target channel
as the best target channel (1st candidate)
ready

HO&PC
Load criterion No
• Searching for the best candidate to be handed over (the fulfilled?
Yes end
2nd candidate) to the target channel is done among calls Enter DHR multiplexing
included in the latest report from HO&PC algorithm mode
• both AMR HR and FR calls are considered Search for the 1st
candidate (target
• unless AMR FR to DHR HO is blocked with UTPFIL parameter channel)
(AMR FR DHR MUX)
• Candidates for DHR multiplexing HO must fulfill the following
channel found?
criteria:
end
• UL & DL RxQual ≤ Intra HO Threshold Rx Qual AMR FR Search for the 2nd candidate
and suitable 2nd

Yes No
candidate
• UL RxLev ≥ Multiplexing UL Rx Level Threshold found?
end
ready

• 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)
Multiplexing Window for 2nd

candidate
RxLev
RxLev1st - Window UL RxLev1st RxLev1st + Window + Max Power Reduction 2nd

HO&PC
Load criterion No
• Among all the connections meeting DHR multiplexing fulfilled?
Yes end
HO criteria the best 2nd candidate is searched. Enter DHR multiplexing
mode
• The best 2 candidate is determined based on:
nd
Search for the 1st

candidate (target
channel)

channel found?
end
Yes suitable 2nd No

candidate
found?
end
ready

HO&PC
Load criterion No
• The best 2 candidate is handed over to the target
nd fulfilled?
Yes end
channel Enter DHR multiplexing
• Multiplexing HO may be done to: mode
• OSC-1 sub-channel if AMR HR connection occupying target channel
is regarded as OSC-0 Search for the 1st
candidate (target
• OSC-0 sub-channel if AMR HR connection occupying target channel channel)
is regarded as OSC-1
connection to be handed over Yes suitable target No
channel found?
TRX:0 TS0 TS1 TS3 MS3 TS5 TS6 TS7
end
DHR multiplexing HO Search for the 2nd candidate
target channel
TRX:1 TS0 TS1 TS3 TS4 TS5 TS6 TS7
Yes suitable 2nd No
candidate
found?
MS2 free MS3 free free
OSC-0 OSC-0 OSC OSC-0 OSC-0 OSC end
MS3 free free multiplexing MS2 free multiplexing DHR multiplexing HO of 2nd
OSC-1 OSC-1 OSC-1 OSC-1 candidate to the target channel
HR multiplexing HR multiplexing
ready

Module Contents

• Power control
• CSDAP

Power Control (1)
• 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
• individual (DHR-connection-specific) Tx power levels are commanded to BTS
• BTS selects the higher DL power level (among two commanded ones) and applies it for both
paired DHR connections

Power Control (2)
• 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

Power Control (3)
• In case UL Rx Level difference increases to or above Multiplexing UL Rx Level Window

the auxiliary power increase action is triggered for the connection with lower UL Rx
Level:
• if (ULRxLevPAIRED_DHR_call – ULRxLevDHR_CALL) ≥ Multiplexing Ul Rx Level Window

• and ULRxLevDHR_CALL + PowerIncreaseStepSize < PcUpperThresholdsLevUL,
• then DHR_CALL power is increased by PowerIncreaseStepSize
• Fast averaging of UL RxLev and UL RxQual for PC (and HO) procedures in DHR mode
may be enabled with the UTPFIL parameter FAST AVE OF DHR UL
• the existing RxLev and RxQual specific Px and Nx parameters are used

Module Contents

• Power control
• CSDAP

Inter-cell DHR handovers – basic functionality
- 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 are re-used)
- inter-cell HO is triggered if the following conditions are met:
DLRxQual ≥ Threshold DL Rx Qual DHR or ULRxQual ≥ Threshold UL Rx Qual DHR
or
DLRxLev ≤ ThresholdLevelDownlinkRxLevel or ULRxLev ≤ ThresholdLevelDownlinkRxLevel

DHR demultiplexing HO (1)
• DHR demultiplexing HO (intra-cell HO from DHR to non-DHR mode) can be triggered by:
• Rx Quality criterion
• demultiplexing HO to non-DHR mode 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)

DHR demultiplexing HO (2)
• 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 FR if:
• Intra HO Lower Rx Level Limit AMR HR ≤ UL RxLev ≤ Intra HO Upper Rx Level Limit AMR HR
• and
• Intra HO Lower Rx Level Limit AMR HR ≤ DL RxLev ≤ Intra HO Upper Rx Level Limit AMR HR
AMR HR if:
• UL RxLev>Intra HO Upper Rx Level Limit AMR HR
• and
• DL RxLev>Intra HO Upper Rx Level Limit AMR HR
• if UL RxLev or DL RxLev is lower than

Intra HO Lower Rx Level Limit AMR HR,
DHR demultiplexing HO is prevented
• 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.

Module Contents

• Power control
• CSDAP

DHR parameters (1)
dhrLimForFRTCHRes DHR Limit For FR TCH Resources
object: BTS This parameter controls the status of the OSC DHR with SAIC MS feature in a BTS. It
unit: % determines the load threshold for triggering DHR multiplexing: if the percentage of free FR TCH
range: 0..100 decreases below the value of this parameter, DHR multiplexing procedure is attempted.
step: 1 Default value of the parameter disables DHR multiplexing in a BTS.
default: 0 To enable the DHR multiplexing the parameter must be set to value different than zero.
MML command: EQM, Activation of the OSC feature is possible only if:
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”)
Category: Advanced - 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
- Support for SAIC (BSS20082) feature is enabled – valid license is active
- Extra Abis resources are available with ‘Packet Abis’ or ‘Circuit Switched Dynamic Abis Pool’
feature
Setting of DHR Limit For FR TCH Resources must be aligned with setting of lower load limit for
AMR HR packing:
DHR Limit For FR TCH Resources ≤ (A)FRL or (A)HRL
Rule: the higher the value of this attribute, the lower traffic load at which DHR multiplexing is
triggered

DHR parameters (2)
oscMultiplexUlRxLevThr OSC Multiplexing UL Rx Level Threshold
object: HOC This parameter determines the UL Rx Level criterion for searching DHR multiplexing
unit: dBm 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, can be regarded as DHR
multiplexing candidates.
step: 1
Rule: the higher the value of this parameter the more stringent Rx Level criterion for DHR
default: -85 multiplexing candidates selection and consequently lower OSC usage. Setting this threshold
MML command: EHC, EHS, EHO to lower values may result in higher OSC usage but may lead to quality degradation and/or
MML abbr. name: OMLT increase of the number of DHR demultiplexing HOs.
Category: Advanced

DHR parameters (3)
oscDhrMultiplexRxQualThr OSC DHR Multiplexing Rx Quality Threshold

object: HOC This parameter determines the UL and DL Rx Quality criterion for searching the 1 st DHR
unit: - 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 candidate (target channel).
step: 1
Rule: the lower the value of this parameter the more stringent Rx quality criterion for DHR
default: 0 multiplexing candidates selection and consequently lower OSC usage. Setting of this
MML command: EHC, EHQ, parameter must be consistent with setting of OSC Demultiplexing Rx Quality Threshold.
EHO
MML abbr. name: ODMQT
Category: Advanced

DHR parameters (4)
oscMultiplexUlRxLevWin OSC Multiplexing UL Rx Level Window

object: HOC This parameter determines the UL Rx Level Difference criterion for searching the 2 nd DHR
unit: dB multiplexing candidate (connection to be handed over to the target channel).
range: 0..20 Only AMR FR/HR connections having UL RxLev within the window defined based on this
parameter and UL RxLev of the 1st candidate may be regarded as 2nd DHR multiplexing
step: 1 candidates.
default: 10 Rule: the lower the value of this parameter the more stringent UL Rx Level difference
MML command: EHC, EHS, criterion for 2nd candidate selection and consequently lower OSC usage. Setting this
EHO threshold to higher values may result in higher OSC usage but may lead to UL quality
MML abbr. name: OMLW degradation.
Category: Advanced This parameter shall always be set to lower values than OSC Demultiplexing UL Rx Level
Margin.
Setting of this parameter impacts UL Power Control algorithm in DHR mode.

DHR parameters (5)
oscDemultiplexUlRxLevMarg OSC Demultiplexing UL Rx Level Margin

object: HOC This parameter determines the UL Rx Level Difference criterion for DHR demultiplexing
unit: dB HO.
range: 0..63 If difference between UL Rx Levels of DHR paired connections exceeds the value of this
parameter, the connection with higher RxLev is handed over to non-DHR mode (DHR
step: 1 demultiplexing HO may be prevented if AMR Unpacking Optimization feature is enabled
default: 14 and RxQual or RxLev degrades too much)
MML command: EHC, EHS, Rule: the lower the value of this parameter the more stringent UL Rx Level difference
EHO criterion for keeping connections in DHR mode and consequently lower OSC usage.
MML abbr. name: ODMRG Setting this threshold to higher values may result in higher OSC usage but may lead to UL
Category: Advanced quality degradation.
This parameter should always be set to higher values than OSC Multiplexing UL Rx Level
Window.

DHR parameters (6)
oscDemultiplexRxQualThr OSC Demultiplexing Rx Quality Threshold

object: HOC This parameter determines the UL and DL Rx Quality thresholds for DHR demultiplexing
unit: - 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 attempted (DHR demultiplexing HO may be prevented if AMR
step: 1 Unpacking Optimization feature is enabled and RxQual or RxLev degrades too much).
default: 3 Rule: the lower the value of this parameter the more stringent Rx quality criterion for DHR
MML command: EHQ, EHO demultiplexing and consequently lower OSC usage. Setting this threshold to higher values
MML abbr. name: ODDQT may result in higher OSC usage but may lead to speech quality degradation. Setting of this
Category: Advanced parameter must be consistent with setting of OSC Multiplexing Rx Quality Threshold.

DHR parameters (7)
thrDIRxQualDHR Threshold DL RxQual DHR

object: HOC This parameter determines DL Rx Quality threshold for inter-cell HO for DHR
range: 0..7 connections.
step: 1 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).
default: 4
Rule: This parameter should always be set to higher value than OSC Demultiplexing Rx
MML command: EHC, EHQ, EHO Quality Threshold.
MML abbr. name: TDRQD
Category: Advanced
thrUlRxQualDHR Threshold UL RxQual DHR

object: HOC This parameter determines UL Rx Quality threshold for inter-cell HO for DHR
step: 1 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).
default: 4
Rule: This parameter should always be set to higher value than OSC Demultiplexing Rx
MML command: EHC, EHQ, EHO Quality Threshold.
MML abbr. name: TURQD
Category: Advanced

DHR parameters (8)
pcLTDlRxQualDHR PC Lower Threshold DL RxQual DHR

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

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

DHR parameters (9)
pcUTDlRxQualDHR PC Upper Threshold DL RxQual DHR

object: POC This parameter determines DL Rx Quality threshold for BTS power decrease for DHR
step: 1 Rule: setting of this parameter should be consistent with setting of OSC Demultiplexing Rx
Quality Threshold, Threshold DL RxQual DHR and PC Lower Threshold DL RxQual DHR.
default: 0
MML command: EUC, EUO, EUQ
MML abbr. name: UDDHR
Category: Advanced
pcUTUlRxQualDHR PC Upper Threshold UL RxQual DHR

object: POC This parameter determines UL Rx Quality threshold for BTS power decrease for DHR
step: 1 Rule: setting of this parameter should be consistent with setting of OSC Demultiplexing Rx
Quality Threshold, Threshold UL RxQual DHR and PC Upper Threshold UL RxQual DHR.
default: 0
MML command: EUC, EUO, EUQ
MML abbr. name: UUDHR
Category: Advanced

DHR parameters (10)
ciTargetOscDHR C/I Target OSC DHR
object: BSC This parameter determines target carrier-to-interference ratio for DHR connections
unit: dB which is used in the DFCA C/I estimation and channel selection procedure.
range: 0..63
step: 1
default: 16
MML command: EEH,
EEO
MML abbr. name:
CIDHR
Category: Advanced
softBlockingCiOscDHR Soft Blocking C/I DHR
object: BSC This parameter determines soft-blocking carrier-to-interference ratio for DHR
unit: dB connections which is used in the DFCA channel selection procedure. This is the
minimum acceptable C/I value for DHR mode.
range: -20..43
Rule: the higher the value of this parameter the higher DHR multiplexing HO blocking
step: 1 rate and consequently lower OSC usage
default: -20 Recommendation: setting of this parameter should be adjusted to minimum CIR
MML command: EEH, requirements for DHR mode - according to link level simulation it should not be set to
EEO lower values than 10 dB
MML abbr. name:
SBDHR
Category: Advanced

DHR parameters (11)
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 (N)
1 (Y)
step: 1
default: 0
MML command: ERO
Category: Advanced

Related parameters (1)
Parameter name Description

Determines Rx level threshold for a uplink/downlink power increase. This also
PC Lower Threshold Lev UL/DL RxLevel
applies to DHR connections.
Determines Rx level threshold for a uplink/downlink power decrease. This also

PC Upper Threshold Lev UL/DL RxLevel
applies to DHR connections.
Threshold Level Uplink/Downlink Rx Determines uplink/downlink Rx level threshold for triggering the inter-cell handover
Level due to Rx level. This also applies to DHR connections.
Determines downlink and uplink Rx quality threshold for the packing HO (AMR FR to
Intra HO Threshold Rx Qual AMR FR AMR HR). This is also used as a threshold for 2 nd DHR multiplexing candidate
selection.
There are no new Nx & Px parameters dedicated to DHR mode and the existing ones related to particular HO and PC
procedures are re-used.

Related parameters (2)
Parameter name Description
Intra HO Lower Rx Quality Limit AMR Determines the limit of the uplink and downlink Rx quality for quality based intra-cell
(AMR Unpacking Optimization HOs. If averaged uplink or downlink Rx quality is higher than this parameter, the
BSSBSS21120) quality based intra-cell HOs are not allowed. This also prevents DHR demultiplexing
HO in poor Rx quality conditions.
Intra HO Lower Rx Level Limit AMR HR Determines the lower limit for uplink and downlink Rx level for quality based intra-cell
(AMR Unpacking Optimization HOs for AMR HR mode. If averaged uplink or downlink Rx level is lower than this
BSSBSS21120) parameter, the quality based intra-cell HOs for AMR HR calls are not allowed. This
also prevents DHR demultiplexing HO in poor Rx level conditions.
Determines the upper limit for uplink and downlink Rx level for quality based intra-cell
Intra HO Upper Rx Level Limit AMR HR HOs for AMR HR mode. If averaged uplink or downlink Rx level is higher than this
(AMR Unpacking Optimization parameter, the quality based intra-cell HOs for AMR HR calls are not allowed. This is
BSSBSS21120) also used to determine the target channel mode (AMR FR or AMR HR) in DHR
demultiplexing HO triggered by Rx quality criterion – if Rx level is higher than this
threshold DHR call is demultiplexed to AMR HR, otherwise to AMR FR.
Determines the Rx level threshold for triggering the unpacking HO - if uplink or

Rx Level AMR HR Unpacking Threshold downlink Rx level is lower than the value of this parameter the intra-cell HO from
(Improved AMR Packing and Unpacking AMR HR to AMR FR is attempted. This is re-used to trigger also DHR demultiplexing
BSS21483) HO. Setting of this parameter should be aligned with oscMultiplexUlRxLevThr and
oscDemultiplexUlRxLevMarg.

Module Contents

• Power control
• CSDAP

Circuit Switched Dynamic Abis Pool
General aspects (1)
 In legacy Abis interface there is allocated 16 kbit/s fixed transmission capacity for
each radio timeslot from Abis ETPCM.
 When OSC is taken to use then more Abis transmission is needed for radio timeslot
because two calls are multiplexed to one HR (or FR) TCH.
 There is no sense to allocate double fixed transmission capacity for each RTSL
because extra transmission is needed only when there is high load situation in the
cell.
 There are two possibilities to offer transmission for OSC DHR calls:
• Circuit Switched Dynamic Abis Pool (CSDAP)
• Packet Abis

General aspects (2)
 CSDAP feature offers possibility to create common transmission pool(s) for circuit
switched traffic to BCF cabinet
 Maximum 4 CSDAPs in BCF
 Maximum 1000 CSDAPs in BSC
 CSDAP is continuous block 64 kbit/s physical timeslots
 CSDAP size can be 1 … 31 timeslots (ANSI 1…24 timeslots)
 CSDAP can situate in the same or different Abis ETPCM as TRXs using it.

General aspects (3)
• 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
in OSC mode 2 DHR calls are transmitted in the same time
(i.e. time slot as these calls are distinguished by different TSC):
OSC-0 channels always use PCM resources reserved for TCH
a single RTSL carrying FR call while
is mapped to a single Abis sub-TSL OSC-1 channels always use PCM resources reserved in CSDAP
a single RTSL carrying HR (1 or 2 calls)

is mapped to a single Abis sub-TSL
MS1 MS3 MS1 free
multiplex
multiplex
as the entire channel is used by HR call
OSC-0 OSC-0 OSC-0 OSC-0
OSC
OSC
ing
ing
in every second time slot
MS2 MS4 MS2 free
OSC-1 OSC-1 OSC-1 OSC-1
MS1 MS2 HR (time) HR (time)
HR HR multiplexing multiplexing
HR (time) multiplexing

General aspects (4)
Main characteristics of CSDAP:

 CSDAPs are created per BCF (BTS site) basis
 up to 4 CSDAPs is possible per BCF
 up to 1000 CSDAPs is possible per BSC
 CSDAP is shared by all TRXs hosted by given BCF (BTS site)
 CSDAP must not be shared among different BCF
 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)

Circuit Switched Dynamic Abis Pool Example: 4/4/4 with EDGE
General aspects (5) PS territories on
TRX1 and TRX2
• CSDAP configuration on PCM line(s) is

less complex in comparison to EDAP
• EDAP
• TCH, TRXSIG and EDAP related to
particular TRX must be on the same PCM line
• this is necessary because synchronization is
required between master and slave PCU frames
• the configuration rule is crucial
when more than 1 PCM line is needed per site
• example on the right with TRX grouped
“by functions”: EGPRS capable TRXs from each cell
are grouped on the “first” PCM line and thus EDAP
must be also created therein
• CSDAP
• DAP configuration rules are relaxed for CSDAP in comparison to EDAP:
• CSDAP can be created on any PCM line, in particular it can be on different PCM than that used by associated TCH, TRXSIG and
EDAP
• CS calls are independent thus synchronization is not needed between TRAU frames associated to OSC-0 and OSC-1 calls
• CSDAPs related to the given site can be freely distributed among available PCM lines

Handling of OSC calls by CSDAP
• 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
• release order of CSDAP resources and radio resources is needed to prevent from attempts to allocate CSDAP
resource for a new radio channel even though the old one is not yet released
• Either allocation or release of OSC-0 call does not affect CSDAP resource allocation

CSDAP parameters (1)
Range BSC - MML

MO Abbreviated Default
And Description Name
Class Name value
Step (Category)
CSDAP id 1..1000, CSDAP ID allows to identify the dynamic Abis pool in the BSC. The - ID
step 1 identification number must be unique within the BSC. (ADV)
CSDAP circuitGroupNumber 0..65535, Circuit group number identifies the circuit group associated to the CSDAP. - -
step 1 Circuit group (CGR) represents resources available on A interface as well as (-)
corresponding block of memory which BSC SW can recognize and address. Note: This is
During DAP creation BSC automatically reserves a free circuit group for each hidden
CSDAP, the assignment cannot be modified and BSC SW understands these parameter.
circuit group numbers rather than CSDAP IDs. This is read-only parameter as
the value is automatically selected during CSDAP creation.
CSDAP pcmCircuit_ID 0..3391, PCM circuit ID indicates the number of Abis interface line (ET-PCM) where - CRCT
step 1 CSDAP is created. (-)
PCM circuit ID is part of hidden circuit (CRCT) parameter which allows to
indicate the number of PCM line where CSDAP is created as well as the
amount of PCM timeslots from the ET_PCM reserved for the CSDAP. The size
of DAP is defined either by indication of firstTSL and lastTSL or by indication
of firstTSL and size of the Abis pool. Thus circuit can have the following
structure:
circuit = pcmCircuit_ID – firstTSL – lastTSL or
circuit = pcmCircuit_ID – firstTSL – size

BSC - MML
MO Abbreviated Range And Default
Description Name
Class Name Step value
(Category)
CSDAP firstTSL 1..31 (E1) First timeslot indicates the position on Abis interface line (defined by means - CRCT
1..24 (T1) of pcmCircuit_ID) of the first timeslot of the CSDAP. (-)
This parameter can be modified by entering a new value using parameter
newFirstTimeSlot (NFT).
CSDAP lastTSL 1..31 (E1) Last timeslot indicates the position on Abis interface line (defined by means of - CRCT
1..24 (T1) pcmCircuit_ID) of the last timeslot of the CSDAP. The parameter is optional as (-)
the size of CSDAP can be also defined explicitly by using parameter pool size
(in addition to first timeslot).
Last timeslot can be modified by entering a new value using parameter
newLastTimeSlot (NLT).
CSDAP poolSize 1..31 (E1) Pool size defines the size of the CSDAP. The parameter is optional as it can - CRCT
1..24 (T1) be replaced with the parameter last timeslot. (-)

Range BSC - MML

MO Abbreviated Default
And Description Name
Class Name value
Step (Category)
CSDAP bcfAbisIF 1..16 BCF Abis interface allows to define at BCF side the number of Abis interface line - BAIF
where the CSDAP is created. (ADV)
CSDAP bcfTslShift -30...30, Last timeslot indicates the position on Abis interface line (defined by means of 0 SHIFT
step 1 pcmCircuit_ID) of the last timeslot of the CSDAP. The parameter is optional as the (ADV)
size of CSDAP can be also defined explicitly by using parameter pool size (in
addition to first timeslot).
Last timeslot can be modified by entering a new value using parameter
newLastTimeSlot (NLT).
BCF csDapId1..4 1..1000 Attached CSDAP1..4 indicates the number of CSDAP attached to the given BCF. - CSDAP1..4
Up to 4 CSDAPs can be attached to BCF (but a single CSDAP can be connected (ADV)
to only one BCF).
When more than 1 pool is attached to the BCF then fault situation in CSDAP (e.g.
due to Abis line outage) does not totally prevent OSC capability in the BCF.
Besides, CSDAP capacity can be increased in the BCF by extension transmission
capacity of the BCF and creation of another CSDAP on the newly connected Abis
line.

Module Contents

• Power control
• CSDAP

OSC Support for AMR-FR
Introduction (1)
• Up to RG10 (BSS) two channel modes were supported, i.e. full-rate (FR) and half-rate (HR) for both
AMR and non-AMR speech codec modes
• In RG20 (BSS) the orthogonal sub-channel (OSC) feature introduced a new channel mode, i.e. the
double half-rate (DHR) mode:
– The DHR mode applies to AMR connections only of SAIC capable mobile stations
indicating their SAIC capability to a network
– With the DHR mode up to four AMR HR connections may be allocated to a single
radio timeslot
• In RG20EP1 the orthogonal sub-channel feature is extended to include a new channel mode, i.e. the
double full-rate (DFR) mode:
– In contrary to the DHR mode, the DFR mode applies strictly to AMR FR
connections only (AMR HR calls are unaffected by the new mode) and, as a
consequence, with the DFR mode two AMR FR connections are allocated to a
single radio timeslot

OSC Support for AMR-FR 0.2 difference in MOS scale
(7.4 kbps vs. 12.2 kbps)
Introduction (2)
• The DFR (OSC for AMR-FR) mode is an alternative to
the AMR HR mode with two calls as well allocated to a
single timeslot
• Compared to AMR-HR the objective of the feature is to
improve subjective speech quality in networks with
reasonable penetration of SAIC capable MSs
• => the DFR mode by using AMR codec modes up to
12.2 kbps offers improved subjective speech quality in
terms of MOS compared to the AMR HR mode: Reference: 3GPP TR26.975 v.10.0.0
– AMR HR mode allows using codec modes up to 7.4 kbps
only The DFR mode can be regarded as a
• Moreover, the DFR mode can provide an operator with remedy for networks limited by MOS
an intermediate grade of freedom to smoothly extend performance => the MOS degradation
cell capacity, e.g. depending on load and quality caused by extensive usage of AMR-HR can
conditions AMR FR calls can be switched at first to the be diminished by applying the DFR mode
DFR mode, then to the AMR HR mode and finally to the instead without the risk of the MOS
DHR (OSC for AMR-HR) mode
degradation

Introduction (3)
• The OSC Support for AMR-FR (BSS21327) is strictly related to the following
features:
– Circuit Switched Dynamic Abis Pool (BSS30385):
▪ Mandatory for the legacy Abis implementation to provide ‘additional’ Abis capacity for the 2nd OSC sub-channel,
i.e. two AMR-FR connections paired to the DFR mode on the same TCH/F or TCH/D requires two 16 kbps Abis
sub-channels
▪ Not needed with the Packet Abis over IP/Eth (BSS21454) or Packet Abis over TDM (BSS21440) implementation
▪ Not mandatory when the optional feature 8k TRAU for AMR-FR feature is activated
– 8k TRAU for AMR-FR (BSS21325):

▪ Both OSC sub-channels can share a common 16 kbps fixed Abis sub-channel with the restriction both AMR-FR
calls run on codec modes up to 7.4 kbps to fit the 2·8 kbps = 16 kbps transmission pattern
– OSC Support for UltraSite (BSS21546) and OSC Support for FlexiMultiradio
(BSS21534)

Introduction (4)
• Two AMR-FR calls allocated to the same TCH/F channel are regarded as the double full
rate (DFR) calls
• TCH/F channel occupied by the DFR calls is split into two (orthogonal) sub-channels, i.e.
OSC-0 and OSC-1
• The separation between OSC-0 and OSC-1 sub-channels is achieved by using training
sequence codes (TSCs):
– The sub-channel specific TSCs are optimized TSC pairs to reach the best performance in the DFR mode
– The OSC-0 sub-channel is assigned with a ‘legacy’ TSC whereas the OSC-1 sub-channel is assigned with a ‘pair-wise’ TSC
• The OSC-0 and OSC-1 sub-channels have independent RR signaling

• A decision whether a connection should be regarded as a standard AMR FR call or a
DFR one is based on the new OSC Neighboring Sub Channel Measurements IE being
part of in Uplink Measurements IE sent in existing Measurement Result message

Introduction (5)
• The orthogonal sub-channel concept in the DL direction is
based on the adoption of the QPSK modulation:
– The QPSK modulation carries two orthogonal sub-channels which can be received
by a legacy SAIC MS like a normal GMSK signal
– Whether particular sub-channels are mapped to MSB or LSB is BTS
implementation dependent
– Separate reception of two sub-channels is enabled by their orthogonality achieved
with appropriately selected TSCs
• BTS uses dynamically GMSK or QPSK modulation
– If there is only one AMR-FR connection in a TCH/F the channel operates in a
traditional AMR-FR mode TSC for OSC-0 TSC for OSC-1
0 2
– If one of paired DFR connections is in the DTX mode the GMSK modulation is 1 7
applied to another one 2 0
• Double FACCH stealing is used for FACCH transmissions, 3 4
4 3
i.e. TCH bursts are stolen from both sub-channels when 5 6
FACCH is to be transmitted 6 5
7 1
Optimized TSC pairs for OSC

Introduction (6)
• The orthogonal sub-channel concept in the UL direction is based on a traditional GMSK modulation and MU-MIMO
(Multi User Multiple Input Multiple Output) technique
– Two users are differentiated by a TSC and propagation paths
▪ The same TSC pair as in DL is used
– 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 OSC performance in UL would be very poor (UL without Rx Diversity is worse than DL without SAIC)
– RX level balance between two connections occupying paired OSC-0 and OSC-1 sub-channels
is needed to provide sufficient quality

OSC Support for AMR-FR MUX-HO
MUX-HO: Multiplexing Handover
Feature Details (1) New Call

(1AFR + 1 AFR)
AFR call on the Target Radio TS
DMUX-HO: De-Multiplexing Handover
PACK-HO: Packing Handover
AFR call moved by UPAC-HO: Unpacking Handover
FR Multiplexing Handover DFR
• RRM allocation schemes and transition

DMUX-HO
BSS21534
states are not supported:

– Direct channel mode transition PACK-HO UPAC-HO
between the DFR and DHR mode DMUX-HO
– Direct FR multiplexing to DHR DMUX-HO
HR DHR
New Call MUX-HO BSS21309

(1AHR + 1 AHR)
AHR call on the Target Radio TS

AHR call moved by Multiplexing Handover
< RG20 < RG20 RG20 RG20 RG20EP1

Allocation scheme non-OSC non-OSC OSC OSC OSC
sub-channel N/A N/A 0 1 0 1 0 1
OSC-0/timeslot HR HR HR HR FR
FR
OSC-1/timeslot HR HR HR HR FR
channel mode allocation FR HR DHR DHR DFR
speech mode FR/AMR HR/AMR AMR AMR AMR

OSC Support for AMR-FR Report from
HO&PC
Feature Details (2)
Load criterion No
RRM: DFR Multiplexing (1/9) fulfilled?
• DFR multiplexing is triggered by the load criterion: Yes end

– The load criterion is checked each time a report from HO&PC Enter DFR multiplexing
mode
algorithm is received with updated values of Rx quality, Rx level and
power reduction Search for the 1st
– If the percentage of the free FR TCHs decreases below the Limit for candidate (target
channel)
Triggering OSC DFR Multiplexing the BTS enters the DFR
mulitplexing mode, i.e. it starts searching for the best pair of AMR-FR Yes suitable target No
calls to be multiplexed to the DFR mode channel found?
– Only a single pair can be multiplexed at a time end
100 Percentage of free

FR channels suitable 2nd
Yes No
candidate
found?
Limit for Triggering
OSC DFR Multiplexing end
time DFR multiplexing HO of 2nd
0
Enter mux mode Exit mux mode
ready

HO&PC
Feature Details (3)
Load criterion No
• DFR multiplexing is realized by handing over an AMR-FR call Yes end
to a target channel with another on-going AMR-FR call both Enter DFR multiplexing
mode
having sufficient quality and UL Rx level:
– Algorithm searches for the best pair of calls to be Search for the 1st
candidate (target
multiplexed to ensure optimal quality in the DFR mode channel)
– At first, the best target channel is searched (the 1st
candidate)
channel found?
– Then, the best connection to be handed over (the 2nd end
candidate) to the target channel is searched Search for the 2nd candidate
– Only TCH/F allocated to SAIC MS with the AMR-FR call suitable 2nd
Yes No
may be regarded as the 1st or the 2nd candidate for candidate
found?
DFR multiplexing
end
DFR multiplexing HO of 2nd
ready

Feature Details (4)
RRM: DFR Multiplexing (3/9)
• Target channel candidates are searched in TRXs included in the latest report from the HO&PC
algorithm:
– Only a TCH channel with an ongoing AMR FR call may become the target channel
• At first, the AMR FR calls satisfying the following criteria are selected:
– UL Rx level criterion: -47 dBm > UL RxLev ≥ OSC DFR Multiplexing UL Rx Level Threshold
– UL & DL Rx quality criterion: UL(DL) RxQual ≤ OSC DFR Multiplexing Rx Quality Threshold
• Then, the list of channels fulfilling above criteria is sorted in descending order according to the UL
pathloss criterion, i.e. UL RxLev + MS Power Reduction
• Finally, the 1st channel on the list, i.e. the one with the highest potential Rx level is selected as
the best target channel (the 1st candidate)
RXQUAL
0
too low RxLev target channel
candidates
OSC DFR Multiplexing Rx
Quality Threshold UL and DL
too low RxLev &
too poor RxQual
too poor RxQual RXLEV
7
0 OSC DFR Multiplexing UL 63
Rx Level Threshold

Feature Details (5)
• 2nd candidates are searched among TRXs included in the latest report from the HO&PC
algorithm:
– Only a TCH channel with an ongoing AMR FR call may become the 2nd candidate
• 2nd candidates for the DFR multiplexing must fulfil the following criteria:
– UL Rx level criterion: -47 dBm > UL RxLev ≥ OSC DFR Multiplexing UL Rx Level Threshold
– UL & DL Rx quality criterion: UL(DL) RxQual ≤ Intra HO Threshold Rx Qual AMR FR2DFR
RXQUAL
0
too low RxLev 2nd candidates
Intra HO Threshold
Rx Qual AMR FR2DFR too low RxLev &
too poor RxQual
too poor RxQual
RXLEV
7
0 OSC DFR Multiplexing UL 63
Rx Level Threshold

Feature Details (6)
• The list of 2nd candidates is updated according to the UL Rx level window criterion:
ULRxLev2nd+ CurrentPowerReduction2nd ≥ ULRxLev1st –OSC DFR Multiplexing UL Rx Level Window

AND
ULRxLev2nd+ CurrentPowerReduction2nd ≤ ULRxLev1st + OSC DFR Multiplexing UL Rx Level Window +
MaxPowerReduction2nd
where:
• MaxPowerReduction2nd – maximum possible uplink power reduction of the 2nd candidate
• MaxPowerReduction2nd = min(MsTxPwrMax - MSTxPwrMin, RxLevReductionMax)
• RxLevReductionMax = max(0, RXLEV_UL – PCLowerThresholdLevUL - SafetyMargin)
• SafetyMargin – the UTPFIL parameter to prevent excessive power reduction

Feature Details (7)
• Finally, among all the connections meeting the DFR multiplexing the best 2nd candidate is
selected according to the following criteria:
– UL Rx Levels Difference criterion:
ΔRxLev = (UL RxLev1st + CurrentPowerReduction1st) - (UL RxLev2nd + CurrentPowerReduction2nd)
– Pathloss Change Rate Difference criterion:
ΔPathlossChangeRate = PathlossChangeRate1st - PathlossChangeRate2nd
– The 2nd connection with the minimum value of |ΔRxLev| + |ΔPathloss Change Rate| is selected
as the best 2nd candidate
where:
PathlossChangeRate = (ULRxLev+CurrentPowerReduction)new - (ULRxLev+CurrentPowerReduction)old
‘new’ refers to the values of the latest report from HO&PC algorithm
‘old’ refers to the values of the last but one report from HO&PC algorithm

HO&PC
Feature Details (8)
Load criterion No
Yes end
• If ΔUL RXLEV CHANGE RATE is greater than a Enter DFR multiplexing
certain threshold (UTPFIL parameter: mode
UL RX CHANGE RATE) the multiplexing attempt is Search for the 1st

rejected: candidate (target
channel)
– If a suitable 2nd candidate cannot be found for the
best 1st candidate the algorithm tries multiplexing Yes suitable target No
with the next best 1st candidate and so on until a channel found?
suitable 2nd candidate is found or the list with the 1st end
candidates is exhausted
Yes suitable 2nd No
candidate
found?
end
ready

Feature Details (9)
• The best 2nd candidate is handed over to the target
channel
• Multiplexing may be done to:
– The OSC-1 sub-channel if an AMR FR connection
occupying the target channel is regarded as OSC-0: …
▪ A timeslot in the past never in the DFR mode Yes suitable target No
▪ A timeslot in the FR mode, but previously in the DFR mode channel found?
and demultiplexing HO executed on the OSC-1 sub-channel end
handed over to another timeslot or call terminated while in the Search for the 2nd candidate
DFR mode while on OSC-1
– The OSC-0 sub-channel if AMR FR connection occupying Yes suitable 2nd
candidate
No
target channel is regarded as OSC-1 found?
▪ A timeslot in the FR mode, but previously in the DFR mode
and demultiplexing HO executed on the OSC-0 sub-channel end
handed over to another timeslot or call terminated in the DFR candidate to the target channel
mode while on OSC-0
ready

Feature Details (10)
• With the legacy Abis implementation the OSC-0 sub-channel is always allocated to fixed Abis
resources whereas a new OSC-1 sub-channel is allocated to:
– 16 kbps Abis sub-slot from the CSDAP pool if the optional 8k TRAU for OSC AMR-FR feature is off (trau8kEnabledForDfr
= 0) or CSDAP is preferred over the 8k TRAU mode (trau8kEnabledForDfr = 1) and there is still room in the CSDAP pool
– Fixed Abis resources in the 8k TRAU mode if there is no room in CSDAP pool even if it is preferred (trau8kEnabledForDfr
= 1) or 8k TRAU mode is preferred over CSDAP (trau8kEnabledForDfr = 2)
– If there are not free CSDAP resources for the OSC-1 sub-channel and the 8k TRAU for OSC AMR-FR feature is off the
radio channel allocation algorithm changes priorities in the multiplexing algorithm to prefer (for the next 5 attempts) a pair
of AMR connections for which CSDAP pool is not needed, i.e. they are to be regarded as the OSC-0 sub-channel after
multiplexing => the target channel is regarded as OSC-1 sub-channel and it already has its resources allocated from the
CSDAP pool
• If both OSC sub-channels are in the 8k TRAU mode they must not use codec modes of source bit
rates greater than 7.4 kbps
• With the packet Abis implementation both OSC sub-channels are handled identically and in the
same way as other (unpaired) speech calls

RRM: Power Control (1/3)
• PC algorithm for the DFR mode works in the same
way as with the DHR mode
• The only difference is the DFR specific PC
thresholds are defined to control the algorithm
independently of the DHR mode (and non-OSC DFR
modes as well):
– legacy Rx level thresholds are re-used
– There are new DFR-specific Rx quality thresholds to DFR
distinguish them from AMR-FR and DHR quality
thresholds:
▪ PC Lower Threshold DL Rx Qual DFR
▪ PC Upper Threshold DL Rx Qual DFR
▪ PC Lower Threshold UL Rx Qual DFR
▪ PC Upper Threshold UL Rx Qual DFR
• The DFR specific multiplexing margin to control Rx level balance of OSC paired connections
in UL, i.e. the OSC DFR Multiplexing UL Rx Level Window parameter

• In case UL Rx Level difference increases to or above the Multiplexing UL Rx Level
Window the auxiliary power increase action is triggered for the connection with lower UL
Rx Level:
– if (ULRxLevPAIRED_DFR_CALL – ULRxLevDFR_CALL) ≥ Multiplexing Ul Rx Level Window
AND
– ULRxLevDFR_CALL + PowerIncreaseStepSize < PcUpperThresholdsLevUL then the DFR_CALL power is
increased by PowerIncreaseStepSize
• Fast averaging of UL RxLev and UL RxQual for PC (and HO) procedures in the DFR
mode may be enabled with the UTPFIL parameter FAST AVE OF DFR UL
– the existing RxLev and RxQual specific Px and Nx parameters are used

DFR
• Example of the PC algorithm in UL
for two DFR paired connections in a
single timeslot DFR
UL RXLEV User B
63
PC Upper Threshold
Lev UL Rx Level (UUR) OSC DFR Multiplexing
UL Rx Level Window
User A OSC DFR Multiplexing
UL Rx Level Window
6 dB safety margin
PC Lower Threshold
Lev UL Rx Level (LUR)
BSC decreases User’s B
power because Rx level
is above UUR
0 time
BSC increases User’s B power BSC applies auxiliary power increase to User A because
because Rx level is below LUR User’s B power is outside Rx Lev Window

RRM: Inter-cell Handover
• Similarly to the DHR mode, a DFR connection may be handed over to another cell, but
only to the AMR HR/FR mode (DFR-to-DFR inter-cell handovers are not possible)
• Inter-cell HOs for the DFR connections are controlled with new Rx quality thresholds:
Threshold Dl Rx Qual DFR and Threshold Ul Rx Qual DFR and the legacy Rx level
thresholds: Threshold Level Downlink Rx Level and Threshold Level Uplink Rx Level
• Inter-cell HO is triggered if the following conditions are met:
– DLRxQual ≥ Threshold DL Rx Qual DFR or UL Rx Qual ≥ Threshold UL Rx Qual DFR or
DLRxLev ≤ Threshold Level Downlink Rx Level or ULRxLev ≤ Threshold Level Downlink Rx
Level
RXQUAL
0
other procedures, e.g.: DFR
Inter-cell
Threshold DL(UL) Rx demultiplexing

HO
Qual DFR
Inter-cell HO
RXLEV
7
0 Threshold level DL(UL) Rx 63
Level

RRM: DFR Demultiplexing (1/3)
• DFR demultiplexing (an intra-cell HO from the DFR to AMR-FR mode) is triggered if one of the
following criteria is satisfied:
– Rx Quality criterion: UL(DL) Rx Qual ≥ OSC DFR Demultiplexing Rx Qual Threshold
– UL Rx Level Balance criterion: ∆ UL Rx Level ≥ OSC DFR Demultiplexing UL Rx Level Margin => the connection with
higher UL Rx level is demultiplexed to the AMR-FR mode
• The UL Rx level balance criterion has lower priority than the Rx quality criterion
• The OSC DFR Demultiplexing UL Rx Level Margin must have higher value than the OSC DFR
Multiplexing Ul Rx Level Window
UL RX Level User A is
• The DFR call can be optionally 63 demultiplexed
here
demultiplexed to the AMR-HR call
(due to UL Rx level imbalance User A OSC Demux Ul Rx Lev Margin
only!) if the AMR-FR channel is not
available
User B
OSC Demux Ul Rx Lev Margin
0
Time
• The DFR demultiplexing is also triggered by:
– Rx level criterion: if the Improved AMR Packing and Unpacking (BSS21483) feature is
enabled demultiplexing to AMR FR is triggered if UL Rx level or DL Rx level of a DFR
connection is equal to or lower than the Unpacking RX Level Threshold AMR HR threshold
DOWNLINK / UPLINK UPLINK
Inter-cell handover to AMR-FR if ULRxLev ≤ DFR demultiplexing if Improved AMR
if Improved AMR Packing Threshold Level Uplink RxLevel Packing and Unpacking is enabled and UL
and Unpacking is enabled Rx Level < AMR HR Unpacking Threshold
RXQUAL
0 RXQUAL 0
DFR no action no action or... DFR
OSC DFR demultiplexing OSC DFR demultiplexing
Inter-cell HO
Demultiplexing Rx Demultiplexing
Qual Threshold Rx Qual
DFR demultiplexing Threshold
DFR demultiplexing
Threshold DL(UL) Threshold UL
Rx Qual DFR Rx Qual DFR
Inter-cell HO RXLEV Inter-cell HO
7 7
0 Threshold level RxLev AMR HR 63 0 ∆ UL Rx Level
Downlink (Uplink) Rx Unpacking OSC DFR
Level Threshold Demultiplexing UL
Rx Level Margin

• DFR demultiplexing is prevented if the AMR Unpacking Optimization (BSS21120) feature is
activated and one of the following criteria is met:
– Averaged UL(DL) Rx quality criterion: UL(DL) RxQual ≥ Intra HO Lower Rx Quality Limit AMR HR
– Averaged UL(DL) Rx level criterion: UL(DL) RxLev < Intra HO Lower Rx Level Limit AMR HR
• DFR demultiplexing due to the UL Rx level balance criterion cannot be prevented by the AMR
unpacking optimization feature if Improved AMR Packing
and Unpacking is enabled
DOWNLINK / UPLINK
RXQUAL
0 DFR
demultiple
due to low
prevented
demultip
xing HO
RxLev
lexing no action
DFR
Inter-cell HO
OSC DFR Demultiplexing Rx Qual
Threshold DFR demultiplexing
Intra HO Lower Rx Quality Limit AMR
DFR demultiplexing HO prevented due to poor
RxQual
Threshold DL(UL) Rx Qual DFR
Inter-cell HO RXLEV
7
0 63
Threshold level Intra HO Lower
Rx Level Limit RxLev AMR HR
DL(UL) Rx Level AMR HR Unpacking Threshold
Module Contents

• Power control
• CSDAP

BSS 21313, BSS21537
Introduction (1)
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) – RG25 feature OSC Full Rate
with SAIC MS – up to two AMR FR connections may be
allocated on one radio timeslot
DHR
• OSC-related enhancements on the roadmap M
ux
• DFCA Support for OSC in RG25 -in OSC
• g
OSC Support for VAMOS mobiles in RG30 Pa /D DFR
• AQPSK for VAMOS II in RG30 ck HR em
in ux
• OSC over EDAP in RG30 g
/U -in
• OSC Capability test in RG30 n- g
pa FR
ck
• OSC feature increases hardware efficiency in
g
• increased (up to doubled in optimal radio conditions) TRX voice capacity
• increased capacity for PS services (by saving resources occupied by CS)
• improved energy efficiency

BSS 21313, BSS21537 Hi, ... …
Introduction (2)
Mobile station types naming convention Non-SAIC Hi, I’m SAIC…
 SAIC is a generic term for the algorithm that suppresses interference in MS
a single antenna receiver (Single Antenna Interference Cancellation)
 SAIC was standardized originally in 3GPP Rel.6 and terminals having
SAIC algorithm on board and signaling their SAIC-capability to the Hi, I wish I could
network were officially named DARP phase1 (Downlink Advanced DARP tell you that I’m
Receiver Performance) MS SAIC, but…
 currently MS SAIC-capability is 3GPP release independent feature
 in 3GPP terminology, DARP phase1 MS signals its capability to the
network, while MS referred to as SAIC does not have to indicate its
capability SAIC-capable
MS Hi, I’m VAMOS I … ...
 VAMOS I MS supports new training sequences that have been optimized I’m better than SAIC
for simultaneous use in OSC mode and hence provides link gains over since I can use new
legacy TSCs TSCs 
 VAMOS II MS supports new training sequences and utilizes advanced
receiver providing further link gains over VAMOS I or SAIC. It supports VAMOS I
also Shifted SACCH functionality. MS Hi, I’m VAMOS II … …
I’m even better than
 Note: in most of NSN materials the term “SAIC MS” refers to a mobile
VAMOS I 
that have SAIC capability and indicates it to the network
VAMOS II
MS
BSS 21313, BSS21537
Features details
• Features provides support for new types of handsets: VAMOS-1 and VAMOS-2.
• New Training Sequence Codes were defined and standardized in 3GPP for VAMOS
mobiles in order to improve their link level performance when paired in OSC mode.
VAMOS-2 additionally utilizes joint detection method/successive interference cancellation
to retrieve the desired signal out of composite channel.
• New TSCs were introduced in such a way that for each legacy TSC there is a new TSC
and the cross-correlation properties of such pair is optimized to assure its orthogonal
properties
• Features work on top of RG20/25 features DHR/DFR with limited number of changes
in RRM mechanism in comparison with pre-RG30 OSC implementation

OSC support for VAMOS handsets
Feature details
- OSC support for VAMOS handsets – major changes in RRM:

- once at least one VAMOS mobile is paired in OSC mode, new TSC has to be assigned for one
of the mobile in this pair; the second mobile will use legacy TSC
- the TSC pairs are fixed in such a way that for one legacy TSC (from so called TSC set 1) there is only
one counterpart new TSC (from new TSC set 2) to be used for the paired mobile – this TSC has the
same number as the counterpart legacy one
- VAMOS pairs (i.e. OSC pairs where at least one of the mobile is VAMOS capable) could be
prioritized over non-VAMOS pairs (i.e. where neither of the mobiles is VAMOS capable) in order
to boost the penetration of new TSCs and hence increase the link performance of such pairs and
consequently reduce the overall interference level in the network
- DFCA algorithm is updated and made aware of new TSC set
- TSC pairing rule for VAMOS case has to be respected by DFCA algorithm
- new C/I target and soft blocking values for VAMOS DHR and VAMOS DFR are introduced

AQPSK support with VAMOS-2 handsets
Feature details
• AQPSK support with VAMOS-2 handsets – major changes in RRM:

• non-SAIC mobiles are allowed to be paired with another mobiles (in both DHR and DFR
mode) – if the second mobile in this pair is VAMOS-2 capable
• Without this feature non-SAIC mobiles are excluded from any DHR/DFR pairing actions
• in case of VAMOS-2/non-SAIC pairing asymmetrical AQPSK modulation is applied in DL
direction in such a way that sub-channel with higher power is assigned to non-SAIC
mobile and sub-channel with lower power is assigned to VAMOS-2 mobile
• AQPSK modulation loss for both candidates has to be taken into account in the power
budget calculation prior to the actual pairing to assure that both MSs will survive more
severe radio conditions after the pairing (caused by interferences from the other sub-
channel and sub-channel power imbalance)
• Modulation loss is also taken into account in the DFCA algorithm

04 Rn20114en16gla0 Osc+csdap

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

04 Rn20114en16gla0 Osc+csdap

Uploaded by

Copyright:

Available Formats

Nokia Academy

Orthogonal Sub-Channel (OSC) &

RN20114EN16GLA0 © Nokia Solutions and Networks 2015

2 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• After completing the module, the student will be able to:

4 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• Orthogonal Sub-Carrier (OSC) Feature Details

5 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• Orthogonal Sub-Carrier (OSC) Feature Details

6 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

7 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

8 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• Orthogonal Sub-channel concept in DL direction is based on

GMSK is used by the other one 3

9 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

OSC Half Rate requires:

10 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• Orthogonal Sub-Carrier (OSC) Feature Details

11 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

Yes suitable 2nd No

12 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

Search for the 1st

Yes suitable target No

Yes suitable 2nd No

13 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

and suitable 2nd

14 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

Multiplexing Window for 2nd

15 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

Search for the 1st

Yes suitable target No

Yes suitable 2nd No

16 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

17 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• Orthogonal Sub-Carrier (OSC) Feature Details

18 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

19 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• UL PC is performed for both paired DHR

20 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• In case UL Rx Level difference increases to or above Multiplexing UL Rx Level Window

• if (ULRxLevPAIRED_DHR_call – ULRxLevDHR_CALL) ≥ Multiplexing Ul Rx Level Window

21 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• Orthogonal Sub-Carrier (OSC) Feature Details

22 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

23 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

24 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• if UL RxLev or DL RxLev is lower than

25 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

• Orthogonal Sub-Carrier (OSC) Feature Details

26 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

27 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

28 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

oscDhrMultiplexRxQualThr OSC DHR Multiplexing Rx Quality Threshold

29 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

oscMultiplexUlRxLevWin OSC Multiplexing UL Rx Level Window

30 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

oscDemultiplexUlRxLevMarg OSC Demultiplexing UL Rx Level Margin

31 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

oscDemultiplexRxQualThr OSC Demultiplexing Rx Quality Threshold

32 RN20114EN16GLA0 © Nokia Solutions and Networks 2015

thrDIRxQualDHR Threshold DL RxQual DHR

thrUlRxQualDHR Threshold UL RxQual DHR