Slide 1

OSC Half Rate with SAIC MS Reference: MML (ZEEL)ZEEL;

LOADING PROGRAM VERSION 23.59-0

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

BSC NETWORK INFORMATION:

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

COMMAND EXECUTED

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC Half Rate with SAIC MS Reference: MML (ZEEI)EEI:BTS=301;

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

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

COMMAND EXECUTED# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC Half Rate with SAIC MS Reference: MML (ZERO) ADM.STATE OP.STATE --------------------------------------BCF-0087 UNLOCKED WO SEG-0174 ALISSIDAU BTS-0174 ALISSIDAU UNLOCKED WO TRX-009 EDGE UNLOCKED WO BCSU-2

GTRX Y (EDGE) HRS Y PREF N

FREQ 1020 TSC 2 FRT 0 (REGULAR) LEV N (NOT USED)

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

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

D-CH TELECOM LINK SET 800 T0879

RTSL PCM-TSL SUB_TSL TYPE I.LEV ADM.STATE OP.STATE CH.STATUS------------------------------------------------------------------------------ 0 575- 15 0 TCHD 1 UNLOCKED WO HR HR 1 575- 15 1 TCHD 0 UNLOCKED WO HR HR HR 2 575- 15 2 TCHD 0 UNLOCKED WO FR 3 575- 15 3 TCHD 0 UNLOCKED WO HR HR 4 575- 16 0 TCHD 0 UNLOCKED WO HR HR 5 575- 16 1 TCHD 0 UNLOCKED WO HR HR HR 6 575- 16 2 TCHD 1 UNLOCKED WO HR HR 7 575- 16 3 TCHD 0 UNLOCKED WO HR HR

TRANSCEIVER HAS NO INTERFERING CELLS# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelBSS21309, BSS30385IntroductionFeature detailsConfiguration managementPilot resultsDimensioning aspectsImplementation aspectsPM countersFeature impact analysis/feature performance monitoringContents# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channel

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

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

OSC feature increases hardware efficiencyIncreased TRX voice capacityincreased capacity for PS services (by saving resources occupied by CS)improved energy efficiencyIntroduction# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channel

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 timeslotDouble Full Rate (DFR) RG20EP1 feature OSC Full Rate with SAIC MS up to two AMR FR connections may be allocated on one radio timeslotIntroduction

OSC-related enhancements on the roadmapDFCA Support for OSC in RG20EP1OSC Support for VAMOS mobiles in RG30AQPSK for VAMOS II in RG30OSC over EDAP in RG30OSC Capability test in RG30

OSC FR feature provides the same capacity as AMR HR but by utilizing full rate codecs allows improving speech quality in terms of MOSHRFRDFRDHRPacking / Un-packingOSC Mux-ing / Demux-ing# Nokia Siemens Networks Presentation / Author / DateFor internal use

Feature details# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelFeature detailsOrthogonal Sub-Channel (OSC) is a voice capacity feature that allows assigning two AMR connections on the same TCH half rate channel either TCHD or TCHH and further referred to as TCH/Hup to four AMR HR connections may be served by one radio timeslot

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

OSC requires Single Antenna Interference Cancelation (SAIC) receiver in mobile stationsBSC applies OSC only for MSs which indicate their SAIC supportOverview# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelFeature detailsMain aspectsTCH/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 CodesOSC-0 sub-channel is assigned a legacy TSC and uses legacy Abis transport resourcesOSC-1 sub-channel is assigned a pair-wise TSC and uses additional Abis transport resourcesadditional Abis transport capacity is provided with CSDAP or Packet AbisOSC-0 and OSC-1 sub-channels have independent RR signaling# Nokia Siemens Networks Presentation / Author / DateFor internal useCall Control algorithm sends ASSIGNMENT COMMAND message to MS otherwise normally but indicatingTable 1 Optimized TSC pairs for OSC

Orthogonal Sub-channelFeature detailsOSC concept in DL direction is based on QPSK modulation orthogonal transmission

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

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

TSC for OSC-0TSC for OSC-10217203443566571

# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelFeature detailsOrthogonal sub-channel concept in UL direction is based on traditional GMSK modulation and MU-MIMO (Multi User Multiple Input Multiple Output) techniqueTwo users are differentiated by TSC (same as DL) and propagation pathsBTS separates users with Rx Diversity and interference cancellation techniquesSuccessive Interference Cancellation (SIC) receiver is usedRx Diversity is a prerequisite for OSCwithout Rx Diversity DHR performance in UL would be very poorRx level balance between two connections occupying paired OSC-0 and OSC-1 sub-channels is needed to provide sufficient quality

# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelOSC Half Rate with SAIC MSDHR multiplexing mode is triggered based on the load criterionLoad criterion is checked upon receiving a report from HO&PC algorithmIf the percentage of free FR TCHs decreases below Limit for Triggering OSC DHR Multiplexing, the BTS enters DHR multiplexing mode -> searching for the best pair to be multiplexed into DHR mode (only one pair is multiplexed at a time per BCSU)

When evaluating free FR TCHs, the PS territory resources are interpreted according to setting of CS TCH allocation calculation (CTC) parameter: 0 = Only CSW used RTSLs are used (default) 1 = CSW and PSW used RTSLs are used. PSW is seen as occupied (optimize PS) 2 = CSW used and PSW used RTSLs are used. PSW is seen as idle resourceSearch for the 1st candidate (target channel) DHR multiplexing HO of 2nd candidate to the target channelLoad criterionfulfilled? YesNoSearch for the 2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode # Nokia Siemens Networks Presentation / Author / DateFor internal useMultiplexing is realized by handing over AMR HR/FR connection to the target channel with ongoing AMR HR call

Algorithm searches for the best pair of calls to be multiplexed to ensure optimal quality in DHR modefirst, the best target channel is searched (1st candidate)Only AMR HR SAIC connection is considerednext, the best connection to be handed over to target channel is searched for (2nd candidate)both half rate and full rate AMR SAIC connections consideredOrthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HO of 2nd candidate to the target channelLoad criterionfulfilled? YesNoSearch for the 2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode # Nokia Siemens Networks Presentation / Author / DateFor internal useSearching for the best target channel (the 1st candidate)target channel candidates are searched:only TCH/H with ongoing SAIC AMR call may become a target channel for DHR multiplexingUL Rx Level criterion:-47dBm > UL RxLev Multiplexing UL Rx Level ThresholdUL & DL Rx Quality criterion: UL(DL) RxQual Multiplexing Rx Quality Threshold the list of channels fulfilling above criteria is sorted in descending order according to UL path-loss criterion (UL RxLev + current power reduction)the 1st channel in the list (with the lowest path-loss) is selected as the best target channel (1st candidate)Orthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HOLoad criterionfulfilled? YesNoSearch for the2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode

# Nokia Siemens Networks Presentation / Author / DateFor internal use

MS1MS2MS3ULRxLevMS1 UL RxLevMS2 - Multiplexing UL RxLev WindowULRxLevMS4 + Power Reduction < UL RxLev MS2+ Multiplexing UL RxLev Window + max power reductionMS4

MS1MS2MS3

MS4ULRxLevMS1 + Power Reduction < UL RxLevMS2 - Multiplexing UL RxLev WindowRxLevMS2 + Window + Max Power ReductionMS4 Multiplexing Window for MS4

MS1

MS4RxLevMS2 + Window + Max Power ReductionMS3 RxLevMS2 - WindowRxLevMS2 RxLev

MS2

MS3Multiplexing Window for MS3# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HOLoad criterionfulfilled? YesNoSearch for the2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode Among all the connections meeting DHR multiplexing HO criteria the best 2nd candidate is searchedThe best 2nd candidate is determined based on:UL Rx Level Difference criterionULRXLEV= (UL RxLev1st+ CurrentPowerReduction1st)-(UL RxLev2nd + CurrentPowerReduction2nd) UL Rx Level Change Rate criterionUL RXLEV CHANGE RATE =ULRxLevChangeRate1st-ULRxLevChangeRate2nd whereULRxLevChangeRate = (ULRxLev+CurrentPowerReduction)new - (ULRxLev+CurrentPowerReduction)oldwherenew refers to the values of the latest report from HO&PC algorithmold refers to the values of the latest but one report from HO&PC algorithm# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HOLoad criterionfulfilled? YesNoSearch for the2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode

MS1MS2MS3

MS41st candidate: MS2list of 2nd candidates (fulfilling also RxQual criterion): MS3, MS4|ULRXLEVMS3-MS2|+ |ULRxLev Change RateMS3-MS2| < |ULRXLEVMS4-MS2|+ |ULRxLev Change RateMS4-MS2|the best 2nd candidate: MS3Connection with the minimum value of(|ULRXLEV| + |UL RXLEV CHANGE RATE|)is selected as the best 2nd candidate

If UL RXLEV CHANGE RATE is greater than the change rate threshold (UTPFIL parameter: UL RX CHANGE RATE) the multiplexing is rejectedif a suitable multiplexing pair for the best 1st candidate cannot be found, the algorithm continues with multiplexing attempt for the next best 1st candidate and so on until suitable pair is found or there is no more 1st candidates to be checked# Nokia Siemens Networks Presentation / Author / DateFor internal useThe best 2nd candidate is handed over to the target channelMultiplexing HO may be done to:OSC-1 sub-channel if AMR HR connection occupying target channel is regarded as OSC-0OSC-0 sub-channel if AMR HR connection occupying target channel is regarded as OSC-1Orthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HOLoad criterionfulfilled? YesNoSearch for the2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode TRX:0TRX:1TS7DHR multiplexing HOconnection to be handed overtarget channelTS6TS5MS3TS3TS2TS1TS0TS7MS2TS5TS3TS2TS1TS0TS4HR multiplexingOSC multiplexingMS3free OSC-0MS2 OSC-0free OSC-1free OSC-1HR multiplexingOSC multiplexingMS3free OSC-0MS2 OSC-1free OSC-1free OSC-0# Nokia Siemens Networks Presentation / Author / DateFor internal useDuring DHR multiplexing procedure BTS switches from GMSK modulation to QPSK modulation in DL on the target TCH/H

During DHR multiplexing HO theTraining Sequence Code is selected based on the TSC value used for OSC-0 connections according to table 1 (Optimized TSC pairs)If legacy Abis is used, CSDAP resource is needed for the new radio sub-channelIf there is Packet Abis, a separate dynamic Abis pool is not neededif there are no free CSDAP resources for OSC-1 sub-channel available, Radio Channel Allocation algorithm changes priorities in multiplexing algorithm to prefer (for the next attempts the number defined by UTPFIL parameter CSDAP PENALTY COUNT) a pair of AMR connections for which CSDAP resource is not neededOrthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HOLoad criterionfulfilled? YesNoSearch for the2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode # Nokia Siemens Networks Presentation / Author / DateFor internal useUL power optimization during DHR multiplexing HO is needed to minimize the difference between UL Rx Levels of paired DHR connectionsUL Tx power level of the 1st candidate is not changed during DHR multiplexing HOUL Tx power level of the 2nd candidate is adjusted so that the UL Rx Levels of two paired calls are the same

max possible power reduction is defined by the following formula:

UL Rx Level of the 2nd candidate may be allowed to be higher/lower than of the 1st candidate by the value of UTPFIL parameter (UL RX LEVEL DIFF)Orthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HOLoad criterionfulfilled? YesNoSearch for the2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode

# Nokia Siemens Networks Presentation / Author / DateFor internal useDL power optimization during DHR multiplexing HO is needed to avoid an unnecessary power increase on target channel

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

optimized DL Tx power level is determined by calculating new Power Reduction defined as the minimum of two values:max(0, Old_Power_Red_DL1st 3dB) andmax(0,RxLev_DL2nd + Old_Power_Red_DL2nd RxLev_DL1st 3dB) The value of 3dB may be adjusted with the UTPFIL parameter: OSC MODULATION LOSS Orthogonal Sub-channelOSC Half Rate with SAIC MSSearch for the 1st candidate (target channel) DHR multiplexing HOLoad criterionfulfilled? YesNoSearch for the2nd candidateReport fromHO&PCreadysuitable targetchannel found? Yessuitable 2nd candidate found? endNoNoendYesendEnter DHR multiplexing mode # Nokia Siemens Networks Presentation / Author / DateFor internal usePC algorithm for DHR mode is similar to the one used for non-DHR connectionslegacy Rx Level thresholds are re-usednew DHR-specific Rx Quality thresholds allow differentiating from AMR HRPC Lower Threshold DL Rx Qual DHRPC Upper Threshold DL Rx Qual DHRPC Lower Threshold UL Rx Qual DHRPC Upper Threshold UL Rx Qual DHROrthogonal Sub-channel OSC Half Rate with SAIC MS

PC control has lower priority than demultiplexing HODL 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 # Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channel OSC Half Rate with SAIC MS

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 Windowif power decrease results in reaching or exceeding OSC Multiplexing UL Rx Level Window, PC action is abandonedpower increase step size determination algorithm has not been changed and works as in current PC implementation # Nokia Siemens Networks Presentation / Author / DateFor internal useDemultiplexing# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal useDHR 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 DHRDLRxLev ThresholdLevelDownlinkRxLevelULRxLev ThresholdLevelDownlinkRxLevel Orthogonal Sub-channel OSC Half Rate with SAIC MS

# Nokia Siemens Networks Presentation / Author / DateFor internal useDHR demultiplexing HO (intra-cell HO from DHR to non-DHR mode) can be triggered by:Rx Quality criterionDemultiplexing is performed if UL or DL Rx Quality of DHR connection is greater than or equal to Demultiplexing Rx Quality ThresholdUL 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 modeRx Level criterion if Improved AMR Packing and Unpacking (BSS21483) is enableddemultiplexing 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)Orthogonal Sub-channelOSC Half Rate with SAIC MS

# Nokia Siemens Networks Presentation / Author / DateFor internal useQuality based OSC DHR connection demultiplexing has the same priority as AMR HR unpacking handover has among other existing handover criteria

DHR demultiplexing HO may be performed to either AMR HR or AMR FRif demultiplexing is triggered by Rx Quality degradation and AMR Unpacking Optimization (BSS21120) is enabled, the DHR connection is demultiplexed to:AMR HR as the first option (AMR FR is allowed as the secondary option) - 1AMR FR as the first option (AMR HR is allowed as the secondary option) - 2DHR demultiplexing HO is prevented - 3If UL or DL Rx Quality is equal to or higher than Intra HO Lower Rx Quality Limit AMR, DHR demultiplexing HO triggered by RxQual degradation is prevented - 4

Orthogonal Sub-channelOSC Half Rate with SAIC MS1234# Nokia Siemens Networks Presentation / Author / DateFor internal useAMR HR is a prerequisite for DHRtarget channels for DHR multiplexing are searched only among channels already allocated to AMR HR connectionsSupport for Single Antenna Interference Cancellation is a prerequisite for DHRBSC must be able to recognize SAIC capable MSRx Diversity is a prerequisite for DHRwithout Rx Diversity UL Quality in DHR mode may be very poorAMR FR is a prerequisite for DHR (until RG20EP1)AMR HR packingDHR multiplexing is supplementary functionality in addition to the traditional AMR HR packing allowing for achieving higher capacityCSDAP and Packet Abisone of these features is required to provide additional Abis capacity needed for DHR modeSoft Channel Capacitythis feature is not mandatory for DHR but it may be used to enable the full TRX configuration with Double Half RateOrthogonal Sub-channelOSC Half Rate with SAIC MS# Nokia Siemens Networks Presentation / Author / DateFor internal useBaseband Frequency HoppingTo apply DHR multiplexing in BB hopping scenario, all TRXs of the hopping group must be OSC configuredAntenna HoppingTo apply DHR multiplexing in antenna hopping scenario, all TRXs of the BTS must be OSC configuredDouble Power TRX and Intelligent Downlink DiversityDHR multiplexing is not performed in either DPTRXs or IDD TRXsEnhanced Coverage by Frequency Hopping, Intelligent Underlay-Overlay, Handover Support for Coverage EnhancementsOSC is not supported in super reuse layers of a BTSExtended Cell RangeOSC is not supported in TRXs of the extended or super extended coverage area4-way UL DiversityDHR multiplexing is not performed in TRXs with 4UD feature in use

Orthogonal Sub-channelOSC Half Rate with SAIC MS# Nokia Siemens Networks Presentation / Author / DateFor internal useAMR Unpacking Optimization Lower Rx Level and Lower Rx Quality thresholds are re-used to prevent DHR demultiplexing HO in poor radio conditionsUpper Rx Level threshold is used to determine the target channel mode (AMR FR or AMR HR) for DHR connections being demultiplexedImproved AMR Packing and UnpackingRx Level threshold triggering unpacking is re-used to trigger DHR demultiplexing HOTandem-free Operationnormal rules of TFO are applied during DHR multiplexing and demultiplexing HOsTRAU Bicasting in AMR FR/HR HandoverTRAU Bicasting is applied to OSC multiplexing and OSC demultiplexing when the channel mode is changed from AMR FR to DHR or from DHR to AMR FR and conditions for TRAU Bicasting in AMR FR/HR Handover are fulfilledWideband AMRDHR multiplexing of WB-AMR FR connection is not supportedDHR multiplexing is not applied to Dual Transfer Mode callsOrthogonal Sub-channelOSC Half Rate with SAIC MS# Nokia Siemens Networks Presentation / Author / DateFor internal useDiscontinuous Transmissionin both UL and DL direction DTX is applied to each of two paired connections independentlyin DL during DTX periods GMSK is used for active channel instead of QPSK

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

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

Orthogonal Sub-channelOSC Half Rate with SAIC MS# Nokia Siemens Networks Presentation / Author / DateFor internal useEpsilon 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 upBSC sets OSC starting mode for a Flexi EDGE TRX only if:OSC has been enabled in the BTS andDual TRX usage (dualTRXusage) parameter of the TRX is set to value disabled andneither of the two TRXs of the Dual TRX unit is an EGPRS TRXTRXs is regarded as EGPRS TRX if:EGPRS enabled (EGENA) is set to value different than disabled andGPRS enabled TRX (GTRX) is set to value Y

Odessa TRX (EXxB) does support EGPRS in the DTRXOrthogonal Sub-channelOSC Half Rate with SAIC MS# Nokia Siemens Networks Presentation / Author / DateFor internal useIf 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 TRXif 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 modeif 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

Orthogonal Sub-channelOSC Half Rate with SAIC MS

TRX starting modeAntenna hopping# Nokia Siemens Networks Presentation / Author / DateFor internal useCSDAP# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelCircuit Switched Dynamic Abis PoolAdditional Abis resources are needed for OSC-1 channelsthis additional capacity can be taken from a new dedicated pool of Abis resources available for each TRX within the BTS sitethis new pool of Abis resources is hereafter referred to as CSDAP(Circuit Switched Dynamic Abis Pool) Main characteristics of CSDAP:CSDAPs are created per BCF (BTS site) basisup to 4 CSDAPs pools are possible per BCF up to 1000 CSDAPs is possible per BSC CSDAP must be created in consecutive PCM TSLsCSDAP size ranges from 1-31 TSL for E1 (1-24 for T1) with granularity of 1 PCM TSL (i.e. 64 kbps channels)CSDAP can be created on any PCM line, in particular it can be on different PCM than that used by associated TCH and TRXSIG

# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelCircuit Switched Dynamic Abis PoolMS1FRFor OSC DHR mode more Abis transmission is needed for radio timeslot because two calls are multiplexed in one HR channelMS1HRfreeHRHR (time) multiplexingMS1HRMS2HRHR (time) multiplexingfreeFRHR (time) multiplexingfree OSC-0MS2 OSC-1OSC multiplexingfree OSC-1MS1 OSC-0HR (time) multiplexingMS3 OSC-0MS2 OSC-1OSC multiplexingMS4 OSC-1MS1 OSC-0

a single RTSL carrying FR call is mapped to a single Abis sub-TSLa single RTSL carrying HR (1 or 2 calls) is mapped to a single Abis sub-TSLas the entire channel is used by HR call in every second time slotin 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 whileOSC-1 channels always use PCM resources reserved in CSDAP2+2+264kbit trxsig# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelCircuit Switched Dynamic Abis PoolResource allocation from CSDAPCSDAP resource is allocated to OSC-1 call activated in the cell controlled by BCF which the CSDAP is attached toReleasing of CSDAP resourcesThe following events trigger releasing of CSDAP resources:OSC-1 call completionOSC-1 demultiplexing (intra-cell HO)inter-cell HO for OSC-1 callOSC multiplexing failureOSC-1 call activation failureOnly 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 BTSEither allocation or release of OSC-0 call does not affect CSDAP resource allocation# Nokia Siemens Networks Presentation / Author / DateFor internal useDimensioning# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal useDimensioning stepsDimensioning for OSC consists of a few stepsAir interface dimensioningAccess transmission dimensioningBSC / BCSU dimensioningOSC licenses Planning stepsBSS/TSC planningBCSU planning

# Nokia Siemens Networks Presentation / Author / DateFor internal useAir interface dimensioning

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

OSC strategy possibilitiesDecrease number of frequenciesBy implementing OSC-HR traffic can be served by less TRXs (assuming traffic remains the same) and frequencies can be freed for refarmingIncrease voice capacityBy implementing OSC-HR more traffic is potentially servedIncrease PS capacity By Implementing OSC-HR more voice calls can be packed more efficiently and radio resources are freed for PS territory The strategy is important to know for the dimensioning and planning of OSC# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC traffic estimation OSC traffic calculation inputSAIC traffic usage

HR utilizationOSC calls start from AMR HR (trf_122a)

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

Traffic (trf_202a) / trf_1d

Cell rangeLimited cell area where OSC calls can be supportedDe-multiplexingMultiplexing# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC traffic estimationOSC percentage calculation

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

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

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

# Nokia Siemens Networks Presentation / Author / DateFor internal useCSDAP size depends on site configuration and OSC penetration

site configuration#BCCH/CCCH/CDED per cellcodec distribution% FR = % HR = % OSC = #RTSL available for CS# Abis trunks for FR# Abis trunks for HR# Abis trunks for OSCSee next slide!!

Erl / site (and codec)FR/HR trunks actually do not needto be computed because their resourcesare anyway available on Abis permanentlyDynamic Abis CSDAP size (1) Orthogonal Sub-channel Abis dimensioning aspects# Nokia Siemens Networks Presentation / Author / DateFor internal useCSDAP calculator To be able to calculate the CSDAP a tool has been developedLink of tool

# Nokia Siemens Networks Presentation / Author / DateFor internal useto avoid OSC de-multiplexing it is recommended to round up the results related to OSC trunksexample:

3 PCM TSLs are recommended to be usedDynamic Abis CSDAP size - exampleOrthogonal Sub-channel Abis dimensioning aspects

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

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

20.15 Erl/cell60.45 Erl/site30.23 FR Erl15.12 HR Erl15.12 OSC ErlNot needed to be computed

**** Source from NE# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC increase voice capacity in GERAN by doubling the number of connections that can run on the same TCH/H RTSLTherefore the whole transmission path in access network (from BTS to MSC) is affectedthus introduction of OSC requires to check available capacity in the whole access networkBTS Enabling of OSC allows to increase capacity per TRX. Several scenarios possible, each of them have potential impact on number of resources in access network:TRX configuration is kept, CS traffic kept, more RTSL available for PS traffic => higher PS traffic/throughputs possible TRX configuration is kept, PS territory is kept, more CS traffic can be served TRX configuration decreased but CS traffic is kept because of huge OSC penetration BSC

TCSMMSCAbisAterAAbis interface=> Dynamic Abis: TRX site configuration is crucial for estimation of required PCM lines, CSDAP computed based on OSC penetration, modification of PS territory affects EDAP size, TRXSIG capacity must be chosen appropriately (depending on load and codec type)=> Packet Abis: required bandwidth depends on amount of CS and PS traffic as well as codec distributionBSCTraffic to be handled determines bandwidth required in transport (Abis, Ater) regardless on used technology => this must be reflected in number of Exchange Terminals (ET16, ETS2, ETIP, ETP)Number of users served have impact on signaling capacity and processor load (AS7, BCSU, MCMU).PS traffic modification have impact on PCU HW and Gb links capacity.Other aspects to be evaluated: LAC planning, Soft channel capacityTCSMAdditional CS traffic must reflected in the number of transcoders as well as Exchange Terminals (towards BSC and MSC).Ater / A interfaceCS traffic increase caused by OSC introduction has also impact on transport resources towards Core. The need for additional resources must be checked regardless on used transport technology (TDM-based or IP-based). Orthogonal Sub-channel Access network dimensioning aspectsGeneral overview# Nokia Siemens Networks Presentation / Author / DateFor internal usesystem performance and capacityDHR 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 BCSUsEach 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.# Nokia Siemens Networks Presentation / Author / DateFor internal usePresented example calculations which give overview on potential capacity bottlenecks in access network after introduction of OSCPlease note that these calculations are example as the final results always depend onload situation in network before introduction of OSC (BSC type and capacity, interface load, processors load, )OSC penetration rate and introduction strategyThis 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 networkBSC

TCSMMSCAbisAterAOrthogonal Sub-channel Access network dimensioning aspectsExample calculations (1)# Nokia Siemens Networks Presentation / Author / DateFor internal useExample scenario:150 sites, 3+3+3 (per cell: 3 sign RTSL + 1 CDED+ 3 CDEF), 50% FR / 50% HR, TRXSIG = 32kFlexiBSC, PCU2E (incl. asymmetrical PCU conf.), TDM-based transport Initial calculations (i.e. for case without OSC): 18.38 Erl/cell, 5 MB/BH/cellper site: 1 E1 line (18 TCH, 5 TSL for TRXSIG+OMUSIG, 6 EDAP)Abis channels for PS: 3*(1+3) + 4*6 = 36 sub-channelsper BSC: 1350 TRX, 150 E1 lines on Abis, 8271 Erl, 5400 Abis sub-channels for PS3 BCSU, 8 PCU (70% utilization), 4 E1 lines on Gb (15 TSL/PCU) signaling: 1350+150 LAPD on Abis, 71 LAPD on Ater, 16 SS7@64 (2 BCSU needed due to signaling)TCSM configuration (standalone TCSM): 8430 Ater channels (0.1% blocking) => 71 E1 lines on AterGbBSC

TCSMMSCAbisAterAPS core3+3+3 (9 TRX)55.14 Erl15 MB/BH1 E1 line:18 TSL/TCH 5 TSL/sign 6 TSL/EDAP (~40 kbps/user)150 E1 / BSC71 E1 / BSC4 E1 / BSC15 ET16 (225 E1)3 BCSU, 8 PCU1 TCSM rack5 TC2C (9 TR3E, 5 ET16)20 ET16 (towards MSC)284 E1 / TCSMOrthogonal Sub-channel Access network dimensioning aspectsExample calculations (2)# Nokia Siemens Networks Presentation / Author / DateFor internal useSS7 is included in #Ater lines, i.e. (8430/4+16) / 30 = 71 E1OSC introduction scenario 1:OSC on every site, huge penetration OSC, codec distribution of 40% FR / 10% HR, 50% OSCCS traffic increase, PS traffic kept the same Calculations: 25.53 Erl/cell, 5 MB/BH/cellper site: 1 E1 line with compressed mapping (18 TCH, 5 TSL for TRXSIG+OMUSIG, 6 EDAP, 4 CSDAP); without compressed mapping: 2 E1 lines / site => impact on ET16 in BSCAbis channels for PS: 3*(1+3) + 4*6 = 36 sub-channelsper BSC: 1350 TRX, 150 E1 lines on Abis, 11488 Erl, 5400 Abis sub-channels for PS3 BCSU, 8 PCU (70% utilization), 4 E1 lines on Gb (15 TSL/PCU) signaling: 1350+150 LAPD on Abis, 98 LAPD on Ater, 22 SS7@64 i.e. 2 BSC would be needed!!! => 11 SS7@128 (3 BCSU due to signaling) or SIGTRANTCSM configuration (standalone TCSM): 11666 Ater channels (0.1% blocking) => 98 E1 lines on AterGbBSC

TCSMMSCAbisAterAPS core3+3+3 (9 TRX)76.59 Erl15 MB/BH1 E1 line withcompressedmapping18 TSL/TCH 5 TSL/sign 6 TSL/EDAP (~40 kbps/user)4 TSL/CSDAP150 E1 / BSC98 E1 / BSC4 E1 / BSC16 ET16 (252 E1)3 BCSU, 8 PCU7 TC2C (13 TR3E, 7 ET16)28 ET16 (towards MSC)=> 2nd TCSM cabinet needed392 E1 / TCSMNote! In this case there are much more users. Therefore dynamic capacity must be double-checked too.In particular BCSU/MCMU load as well as LAC planning.Orthogonal Sub-channel Access network dimensioning aspectsExample calculations (3)# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC introduction scenario 2:OSC on every site, moderate penetration OSC with distribution of 40% FR / 40% HR / 20% OSCadditional capacity used to relax number of RTSL used by voice to increase PS traffic and throughput (*)i.e. site configuration can be changed to 3+3+3 (per cell: 3 sign RTSL + 3 CDED+ 3 CDEF) Calculations: 19.26 Erl/cell, 10 MB/BH/cellper site: 1 E1 line with compressed mapping (18 TCH, 5 TSL for TRXSIG+OMUSIG, 8 EDAP, 2 CSDAP) => cf. slide 19; without compressed mapping: 2 E1 lines / site => impact on ET16 in BSCAbis channels for PS: 3*(3+3) + 4*8 = 48 sub-channelsper BSC: 1350 TRX, 150 E1 lines on Abis, 8667 Erl, 7200 Abis sub-channels for PS3 BCSU, 11 PCU (70% utilization), 8 E1 lines on Gb (20 TSL/PCU) signaling: 1350+150 LAPD on Abis, 74 LAPD on Ater, 17 SS7@64 i.e. 2 BSC would be needed!!! => 9 SS7@128 (3 BCSU due to signaling) or SIGTRANTCSM configuration (standalone TCSM): 8829 Ater channels (0.1% blocking) => 74 E1 lines on AterGbBSC

TCSMMSCAbisAterAPS core3+3+3 (9 TRX)57.78 Erl30 MB/BH1 E1 line withcompressedmapping18 TSL/TCH 5 TSL/sign 8 TSL/EDAP (~70 kbps/user)2 TSL/CSDAP150 E1 / BSC74 E1 / BSC8 E1 / BSC15 ET16 (232 E1)3 BCSU, 11 PCU1 TCSM rack5 TC2C (10 TR3E, 5 ET16)20 ET16 (towards MSC)296 E1 / TCSMOrthogonal Sub-channel Access network dimensioning aspectsExample calculations (4)# Nokia Siemens Networks Presentation / Author / DateFor internal use(*) in this scenario main bottleneck for PS traffic was on radio (high CS load and only 1 dedicated PDCH). Thus additional radio resources were at least as helpful as EDAP enlargement. Eventually, combination of both allowed to double PS traffic volume and (almost) double perceivable throughput rate per use at the same time.These planning activities can be done using existing methods and toolsintroduction of OSC does not modify access dimensioning methodologyCapacity 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 OSCAnyway 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 extensionto indicate HW elements or interfaces where capacity extension is needed in given scenario and access network configurationMain 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 gainsOrthogonal Sub-channel Access network dimensioning aspectsOSC impact summary# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC licenses In the BSC is the OSC licenseThe license works based on Number of simultaneous OSC pairs100 calls per licenseNumber of OSC TRXs activated in the BSC do not have an impact

There are two ways in looking at the licensesPer implementation via the CSDAP calculations OSC traffic is estimated. Estimations could be done via(avg / peak = burstiness, mux HO / Erlang = number of simultanious callsAfter implementationThe counter 1267 (DHR_MPLX_FAIL_DUE_OTHER) is triggered when there are abnormal OSC HO failures, but also when the licenses are not enough# Nokia Siemens Networks Presentation / Author / DateFor internal usePlanning# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal usePlanning for OSC When all is dimensioned and verified the planning phase (optimizing for performance) should start and should consist of the following aspectsBCC / TSC planning / verificationMS differentiation is done by using different TSC some TSC combinations provide less good performanceBCSU planningOSC will start independently per TRX of a BTS per BCSUHandover planningOSC is starting slow and delaying the handovers will enhance the performanceParameter planningDepending on the strategy the OSC parameters should be chosen# Nokia Siemens Networks Presentation / Author / DateFor internal useBCC / TSC planning / verification

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

TSC for OSC-0TSC for OSC-10217203443566571TSC for the second connection is selected based on the value used for the first connection in the TCH according to the table on the rightvalues in the table are still subject to optimization and may change# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channel Implementation aspectsTSC planning aspects (2)In case of OSC networks (especially in 1x1 reuse) the TSC planning issue becomes more problematic and may need special attentionthe probability of accidental synchronization is the same as in non-OSCTSC for OSC-0TSC for OSC-10217203443566571Optimized TSC pairs for OSC

activation of OSC in a network with optimal (according to legacy planning rules) TSC plan may result in collisions between main TSCs of one cell and paired TSCs of other cellssuch collisions between TSCs characterized by poor mutual cross-correlation properties may lead to significant quality degradationexample: main TSCs determined by legacy non-OSC aware algorithm; paired TSC derived from predefined tablecell B

main TSC = 0main TSC = 2paired TSC = 0cell Apaired TSC = 2collision between main TSC of cell A (B) and paired TSC of cell B (A)collision between paired TSC of cell A (B) and main TSC of cell B (A)# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channel Implementation aspectsTSC planning aspects (3)If after OSC activation some cells suffer from relatively higher speech quality degradation than others, the TSC plan should be reviewedspeech quality may be monitored with e.g. OSC RX Quality Measurements (counters: 122000-122079) and/or FER Measurement (counter 77002)if any TSC collision is detected the TSC re-planning should be considered taking into account:interference relations between neighboring cellsprobability of paired TSC utilization dependent on OSC penetrationfact that QPSK interference is more harmful for GMSK victim than GMSK interferencethere is significant performance deterioration of OSC DL transmission due to TSC collision between OSC paired users and external interferer (see next slide)cross-correlation properties between:main TSC in cell A and main TSC in cell B (as in non-OSC case)main TSC in cell A and paired-TSC in cell B and vice versa (main TSC in cell B and paired-TSC in cell A)paired-TSC in cell A and paired-TSC in cell B

cell B

main TSC = 0main TSC = 2paired TSC = 0cell Apaired TSC = 2cell B

main TSC = 0main TSC = 3paired TSC = 4cell Apaired TSC = 2# Nokia Siemens Networks Presentation / Author / DateFor internal useBCSU planning

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

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

Keep in mind the load distribution over the BCSUs

# Nokia Siemens Networks Presentation / Author / DateFor internal useHandover planning

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

Meaning that is a mobile is not the 1st in line in the ranking it means that it will take at least a few OSC reporting rounds before the call will go to OSCTherefore it is crucial to keep the MSs as much as possible on the cell to provide the opportunity to go to OSCThe degree of the maintaining the call depends on many things, likeCall durationHandover / call (trf_13f)Quality distribution in cellBlocking in the cell and surrounding# Nokia Siemens Networks Presentation / Author / DateFor internal useParameter planning

With the OSC parameters you define the working of OSC OSC works on top of AMR-HR/FRMeaning that some of the AMR parameters still applyThese parameters areIHRH, IHRFCodec settings parametersAMR-HR load seetings (FRL, FRU, AFRL, AFRU)# Nokia Siemens Networks Presentation / Author / DateFor internal useOSCDHRMultiplexingRXQualityThr(ODMQT)OSCMultiplexingULRXLevelWindow(OMLW)MultiplexingOSCMultiplexingULRXLevelThr(OMLT)trxOSCCapability(ERO)General TRXtrxStartingMode(-)pcLowerThresholdDLRXQualDhr(LDDHR)POWER CONTROLpcLowerThresholdULRXQualDHR(LUDHR)pcUpperThresholdDLRxQualDhr(UDDHR)pcUpperThresholdULRxQualDhr(UUDHR)DHRLIM (BTS))LOADOSC Parameters (RG20)- OverviewDemultiplexingOSCDemultiplexingULRxLevMargin(ODMRG)OSCDhrDemultiplexingRXQualityThr(ODDQT)UL RX Change rate(0x38)UTPFILUL Rx Level Diff(0x39)OSC Modulation loss(0x3A)CSDAP Penalty count(0x3B)Fast AVE of DHR UL()AMR FR DHR MUX()AMR FR DHR MUXL()CSDAP IDCSDAP)circuitGroupNumberpcmCircuit_IDfirstTSLLastTSLPoolSizebcfAbisIFbcfTslShiftcsDapID# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementlimForTriggeringOscDhrMultiplexingLimit for Triggering OSC DHR Multiplexingobject:BTSunit:%range: 0..100step:1default: 0MML command: EQM, EQOMML abbr. name: DHRLIMIt determines the load threshold for triggering DHR multiplexing: if the percentage of free FR TCH decreases below the value of this parameter, DHR multiplexing procedure is attempted. Default value of the parameter disables DHR multiplexing in a BTS.To enable the DHR multiplexing the parameter must be set to value different than zero. Activation of the OSC feature is possible only if:- BCF site type is Flexi EDGE (version EX4.0)- Rx diversity is in use in the BTS (parameter RDIV = Y)- AMR Half Rate (BSS30060) is in use in the BTS: valid license is active- AMR HR Packing is in use: parameter amrConfHrCodecModeSet >0 and load limits parameters: FRL & FRU or HRL & HRU (if Load Based AMR Packing BSS21154 is not active) or AFRL & AFRU or AHRL & AHRU (if Load Based AMR Packing BSS21154 is active) are appropriately set- Extra Abis resources are available with Packet Abis or Circuit Switched Dynamic Abis Pool featureSetting 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)HRLRule: the higher the value of this attribute, the lower traffic load at which DHR multiplexing is triggered# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementoscMultiplexingUlRxLevelThrOSC Multiplexing UL Rx Level Thresholdobject:HOCunit:dBmrange:-110..-47step:1default: -85MML command: EHC, EHS, EHOMML abbr. name: OMLTThis parameter determines the UL Rx Level criterion for searching DHR multiplexing candidates (both 1st and 2nd candidate must fulfill this criterion).Only calls with UL Rx level greater than or equal to this threshold (and lower than -47dBm), can be regarded as DHR multiplexing candidates.oscDhrMultiplexingRxQualityThrOSC DHR Multiplexing Rx Quality Thresholdobject:HOCunit:-range: 0..7step:1default: 0MML command: EHC, EHQ, EHOMML abbr. name: ODMQTThis parameter determines the UL and DL Rx Quality criterion for searching the 1st DHR multiplexing candidate (target channel).Only AMR HR calls with UL and DL Rx quality lower than or equal to this threshold, can be regarded as the 1st DHR multiplexing candidate (target channel).

# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementoscMultiplexingUlRxLevelWindowOSC Multiplexing UL Rx Level Windowobject:HOCunit:dBrange: 0..20step:1default: 10MML command:EHC, EHS, EHOMML abbr. name: OMLWThis parameter determines the UL Rx Level Difference criterion for searching the 2nd DHR multiplexing candidate (connection to be handed over to the target channel).Only AMR FR/HR connections having UL RxLev within the window defined based on this parameter and UL RxLev of the 1st candidate may be regarded as 2nd DHR multiplexing candidates.Multiplexing Window for 2nd candidateUL RxLev1st RxLevRxLev1st - WindowRxLev1st + Window + Max Power Reduction2nd # Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementoscDemultiplexingUlRxLevMarginOSC Demultiplexing UL Rx Level Marginobject:HOCunit:dBrange: 0..63step:1default: 14MML command: EHC, EHS, EHOMML abbr. name: ODMRGThis parameter determines the UL Rx Level Difference criterion for DHR demultiplexing HO.If difference between UL Rx Levels of DHR paired connections exceeds the value of this parameter, the connection with higher RxLev is handed over to non-DHR mode.This parameter should always be set to higher values than OSC Multiplexing UL Rx Level Window.oscDhrDemultiplexingRxQualityThrOSC DHR Demultiplexing Rx Quality Thresholdobject:HOCunit:-range: 0..7step:1default: 3MML command: EHQ, EHOMML abbr. name: ODDQTThis parameter determines the UL and DL Rx Quality thresholds for DHR demultiplexing HO.If UL or DL Rx quality of DHR connection reaches or exceeds this threshold, demultiplexing HO to non-DHR mode is attempted (DHR demultiplexing HO may be prevented if AMR Unpacking Optimization feature is enabled and RxQual or RxLev degrades too much).Setting of this parameter must be consistent with setting of OSC Multiplexing Rx Quality Threshold.# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementthrDlRxQualDhrThreshold DL RxQual DHRobject:HOCunit:-range: 0..7step:1default: 4MML command: EHC, EHQ, EHOMML abbr. name: TDRQDThis parameter determines DL Rx Quality threshold for inter-cell HO for DHR connections.If DL RxQual reaches or exceeds this threshold, DHR connection is handed over to a new cell to non-DHR mode (AMR HR or FR).Rule: This parameter should always be set to higher value than OSC Demultiplexing Rx Quality Threshold.thrUlRxQualDhrThreshold UL RxQual DHRobject:HOCunit:-range: 0..7step:1default: 4MML command: EHC, EHQ, EHOMML abbr. name: TURQDThis parameter determines UL Rx Quality threshold for inter-cell HO for DHR connections.If UL RxQual reaches or exceeds this threshold, DHR connection is handed over to a new cell to non-DHR mode (AMR HR or FR).Rule: This parameter should always be set to higher value than OSC Demultiplexing Rx Quality Threshold.# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementpcLowerThresholdDlRxQualDhrPC Lower Threshold DL RxQual DHRobject:POCunit:-range: 0..7step:1default: 3MML command: EUC, EUO, EUQ MML abbr. name: LDDHRThis parameter determines DL Rx Quality threshold for BTS power increase for DHR connections.Rule: setting of this parameter should be consistent with setting of OSC Demultiplexing Rx Quality Threshold, Threshold DL RxQual DHR and PC Upper Threshold DL RxQual DHR.Recommendation: it is recommended to set this parameter to value lower than OSC Demultiplexing Rx Quality Threshold to trigger power control action before attempting the demultiplexing HO.pcLowerThresholdUlRxQualDhrPC Lower Threshold UL RxQual DHRobject:POCunit:-range: 0..7step:1default: 3MML command: EUC, EUO, EUQMML abbr. name: LUDHRThis parameter determines UL Rx Quality threshold for BTS power increase for DHR connections.Rule: setting of this parameter should be consistent with setting of OSC Demultiplexing Rx Quality Threshold, Threshold UL RxQual DHR and PC Upper Threshold UL RxQual DHR.Recommendation: it is recommended to set this parameter to value lower than OSC Demultiplexing Rx Quality Threshold to trigger power control action before attempting the demultiplexing HO.# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementpcUpperThresholdDlRxQualDhrPC Upper Threshold DL RxQual DHRobject:POCunit:-range: 0..7step:1default: 0MML command: EUC, EUO, EUQMML abbr. name: UDDHRThis parameter determines DL Rx Quality threshold for BTS power decrease for DHR connections.Rule: setting of this parameter should be consistent with setting of OSC Demultiplexing Rx Quality Threshold, Threshold DL RxQual DHR and PC Lower Threshold DL RxQual DHR.pcUpperThresholdUlRxQualDhrPC Upper Threshold UL RxQual DHRobject:POCunit:-range: 0..7step:1default: 0MML command: EUC, EUO, EUQMML abbr. name: UUDHRThis parameter determines UL Rx Quality threshold for BTS power decrease for DHR connections.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.

# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementtrxOSCCapabilityTRX OSC Capabilityobject:TRXunit:-range: 0..4step:1default: 0MML command:EROThis parameter indicates whether TRX supports OSC feature. This is read-only parameter. Its value is set by the system. Rule:0 - TRX is not OSC capable1 - TRX is OSC capable2 - TRX OSC capability is temporarily lost3 - TRX is capable of OSC without EGPRS4 - TRX OSC capability without EGPRS is temporarily losttrxStartingModeTRX Staring Moodeobject:TRXunit:-range: 0, 1step:1default: -This parameter indicates the mode (EGPRS or OSC) in which the BSC has started the Flexi EDGE TRX. It is used with Flexi EDGE BTS only. This is read-only parameter. Its value is set by the BSC.Rule:0 - EGPRS starting mode, in this mode 1st generation Flexi EDGE TRX does not support OSC;1 - OSC starting mode, in this mode 1st generation Flexi EDGE TRX does not support EGPRS# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementUL RX CHANGE RATEobject:UTPFILunit:-range: 0..63step:1default: 10number/id:0x38This parameter determines the maximum allowed difference between UL RxLev Change Rates of DHR multiplexing candidates. BSC rejects DHR multiplexing if UL RxLev Change Rates difference is greater than the value of this parameter.Rule: the lower the value of this parameter the more stringent criterion for DHR multiplexing and lower OSC usage. Setting this parameter to higher values may result in higher number of DHR multiplexing HO but may also lead to increase of the DHR demultiplexing HO due to UL RxLev Unbalance.UL RX LEVEL DIFFobject:UTPFILunit:dBrange: 0..63step:1default: 0number/id:0x39This parameter allows for adjusting the algorithm for MS Power Optimization in 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 the 1st DHR multiplexing candidate.# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementOSC MODULATION LOSSobject:UTPFILunit:dBrange: 0..63step:1default: 3number/id:0x3AThis parameter allows for adjusting the algorithm for BTS Power Optimization in DHR Multiplexing HO it allows to tune the value of extra power increase applied in DL during DHR multiplexing HO to compensate the loss resulting from DHR multiplexing.CSDAP PENALTY COUNTobject:UTPFILunit:-range: 0..255step:1default: 5number/id:0x3BAmount of multiplexing attempts when CSDAP allocation is avoided after unsuccessful CSDAP allocation the pairs with the 1st candidate having already been assigned CSDAP resource (OSC-1 sub-channel) are preferred.# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementFAST AVE OF DHR ULobject:UTPFILunit:-range: 0 (fast averaging disabled)1 (fast averaging enabled)default: 1number/id:tbdThis parameter determines whether fast averaging is used in UL power control and handover evaluation of DHR connections.Since DHR multiplexing may result in significant changes of Rx quality it is recommended to enable fast averaging for DHR connections.AMR FR DHR MUXobject:UTPFILunit:-range: 0 (AMR FR->DHR forbidden)1 (AMR FR->DHR allowed)default: 1number/id:tbdThis parameter allows for preventing AMR FR-to-DHR multiplexing HO. Direct switching from AMR FR to DHR mode may result in too high degradation of user perceived quality. Disabling this type of transition allow avoiding this potential degradation. On the other hand, preventing AMR FR-to-DHR multiplexing HO limits the list of multiplexing candidates what may result in lower DHR utilization.# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementAMR FR DHR MUXobject:UTPFILunit:-range: 0 (AMR FR->DHR forbidden)1 (AMR FR->DHR allowed)default: 1number/id:tbdThis parameter allows for preventing AMR FR-to-DHR multiplexing HO. Direct switching from AMR FR to DHR mode may result in too high degradation of user perceived quality. Disabling this type of transition allow avoiding this potential degradation. On the other hand, preventing AMR FR-to-DHR multiplexing HO limits the list of multiplexing candidates what may result in lower DHR utilization.# Nokia Siemens Networks Presentation / Author / DateFor internal useParameter nameDescriptionPC Lower Thresholds Lev UL/DL Rx LevelDetermines Rx level threshold for a uplink/downlink power increase. This also applies to DHR connections.PC Upper Thresholds Lev UL/DL Rx LevelDetermines Rx level threshold for a uplink/downlink power decrease. This also applies to DHR connections.Threshold Level Uplink/Downlink Rx LevelDetermines uplink/downlink Rx level threshold for triggering the inter-cell handover due to Rx level. This also applies to DHR connections.Intra HO Threshold Rx Qual AMR FRDetermines downlink and uplink Rx quality threshold for the packing HO (AMR FR to AMR HR). This is also used as a threshold for 2nd DHR multiplexing candidate selection.There are no new Nx & Px parameters dedicated to DHR mode and the existing ones related to particular HO and PC procedures are re-used.Orthogonal Sub-channelConfiguration Management# Nokia Siemens Networks Presentation / Author / DateFor internal usehoTQUlNxhoTQUlPxHOThreshold Level Downlink Nx Threshold Level Uplink Nx Threshold Level Downlink Px Threshold Level Uplink PxThreshold Qual Downlink Nx Threshold Qual Uplink Nx Threshold Qual Downlink Px Threshold Qual Uplink Px

Power ControlPC Upper Thresholds Lev DL Nx PC Lower Thresholds Lev DL Nx PC Upper Thresholds Lev DL Px PC Lower Thresholds Lev DL Px PC Upper Thresholds Lev UL Nx PC Lower Thresholds Lev UL Nx PC Upper Thresholds Lev UL Px PC Lower Thresholds Lev UL Px

PC Upper Thresholds Qual DL Nx PC Lower Thresholds Qual DL Nx PC Upper Thresholds Qual DL Px PC Lower Thresholds Qual DL Px PC Upper Thresholds Qual UL Nx PC Lower Thresholds Qual UL Nx PC Upper Thresholds Qual UL Px PC Lower Thresholds Qual UL Px Parameter nameDescriptionIntra HO Lower Rx Quality Limit AMR(AMR Unpacking Optimization BSS21120)Determines the limit of the uplink and downlink Rx quality for quality based intra-cell HOs. If averaged uplink or downlink Rx quality is higher than this parameter, the quality based intra-cell HOs are not allowed. This also prevents DHR demultiplexing HO in poor Rx quality conditions. Intra HO Lower Rx Level Limit AMR HR(AMR Unpacking Optimization BSS21120)Determines the lower limit for uplink and downlink Rx level for quality based intra-cell HOs for AMR HR mode. If averaged uplink or downlink Rx level is lower than this parameter, the quality based intra-cell HOs for AMR HR calls are not allowed. This also prevents DHR demultiplexing HO in poor Rx level conditions. Intra HO Upper Rx Level Limit AMR HR(AMR Unpacking Optimization BSS21120)Determines the upper limit for uplink and downlink Rx level for quality based intra-cell HOs for AMR HR mode. If averaged uplink or downlink Rx level is higher than this parameter, the quality based intra-cell HOs for AMR HR calls are not allowed. This is also used to determine the target channel mode (AMR FR or AMR HR) in DHR demultiplexing HO triggered by Rx quality criterion if Rx level is higher than this threshold DHR call is demultiplexed to AMR HR, otherwise to AMR FR. Rx Level AMR HR Unpacking Threshold (UTPFIL parameter)(Improved AMR Packing and Unpacking BSS21483)Determines the Rx level threshold for triggering the unpacking HO - if uplink or downlink Rx level is lower than the value of this parameter the intra-cell HO from AMR HR to AMR FR is attempted. This is re-used to trigger also DHR demultiplexing HO. Setting of this parameter should be aligned with oscMultiplexUlRxLevThr and oscDemultiplexUlRxLevMarg.Orthogonal Sub-channelConfiguration Management# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementidCSDAP IDobject: CSDAPrange: 1..1000step: 1MML commands: ESE, ESV, ESM, ESIMML abbreviated name: IDCSDAP ID allows to identify the dynamic Abis pool in the BSC. The identification number must be unique within the BSC. circuitGroupNumberCircuit group numberobject:CSDAPrange: 0..65535MML commands: MML abbreviated name:

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

NOTE: 2048..3391 is reserved for T1 (OC-3) administration areaPCM circuit ID indicates the number of Abis interface line (ET-PCM) where CSDAP is created. PCM circuit ID is part of hidden circuit (CRCT) parameter which allows to indicate the number of PCM line where CSDAP is created as well as the amount of PCM timeslots from the ET_PCM reserved for the CSDAP. The size of DAP is defined either by indication of firstTSL and lastTSL or by indication of firstTSL and size of the Abis pool. Thus circuit can have the following structure:circuit = pcmCircuit_ID firstTSL lastTSL orcircuit = pcmCircuit_ID firstTSL size # Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementlastTSLLast Timeslotobject:CSDAPrange: 1..31 (E1) 1..24 (T1)MML commands: ESE, ESM, ESIMML abbreviated name: CRCTLast timeslot indicates the position on Abis interface line (defined by means of pcmCircuit_ID) of the last timeslot of the CSDAP. The parameter is optional as the size of CSDAP can be also defined explicitly by using parameter pool size (in addition to first timeslot). Last timeslot can be modified by entering a new value using parameter newLastTimeSlot (NLT). By entering a number bigger than the last timeslot the pool is extended (by adding some timeslots on at the end of the pool), by entering a number smaller than the last timeslot the pool is got shrunk (by removal some timeslots at the end of the pool).firstTSLFirst Timeslotobject:CSDAPrange: 1..31 (E1) 1..24 (T1)MML commands: ESE, ESM, ESIMML abbreviated name: CRCTFirst timeslot indicates the position on Abis interface line (defined by means of pcmCircuit_ID) of the first timeslot of the CSDAP. This parameter can be modified by entering a new value using parameter newFirstTimeSlot (NFT). By entering a number smaller than the first timeslot the pool is extended (by adding some timeslots on to the beginning of the pool), by entering a number bigger than the first timeslot the pool is got shrunk (by removal some timeslots from the beginning of the pool).poolSizePool sizeobject:CSDAPrange: 1..31 (E1) 1..24 (T1)MML commands: ESE, ESIMML abbreviated name: CRCTPool size defines the size of the CSDAP. The parameter is optional as it can be replaced with the parameter last timeslot.# Nokia Siemens Networks Presentation / Author / DateFor internal useOrthogonal Sub-channelConfiguration ManagementbcfAbisIFBCF Abis IFobject:CSDAPrange: 1..16MML commands: ESE, ESM, ESIMML abbreviated name: BAIFBCF Abis interface allows to define at BCF side the number of Abis interface line where the CSDAP is created. bcfTslShiftBCF Timeslot Shiftobject:CSDAPrange: -30..30default:0Step:1MML commands: ESE, ESM, ESIMML abbreviated name: SHIFTBCF timeslot shift allows to define the offset between ET-PCM timeslots in BSC side and Abis IF timeslots in BCF sidecsDapId1..4Attached CSDAP1..4object:BCFrange: 1..1000MML command: EFC, EFO, EFMMML abbreviated name: CSDAP1..4Attached CSDAP1..4 indicates the number of CSDAP attached to the given BCF. Up to 4 CSDAPs can be attached to BCF (but a single CSDAP can be connected to only one BCF).# Nokia Siemens Networks Presentation / Author / DateFor internal useGood values to start a pilot During different projects it has been seen that the following parameter sets is working well and could be used as starting point

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC in MML# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC Half Rate with SAIC MS operationHow to monitornumber of busy DHR connections / DHR call pairs on different object levels are seen with ZEEI, ZEEL and ZERO commandsOSC DHR multiplexing can be verified with the performance measurement counters of the featureparticularly the counters in Traffic Measurement, Resource Availability Measurement and Handover Measurement Alarms related to the feature give indications of problems in running of the feature

# Nokia Siemens Networks Presentation / Author / DateFor internal useOptimization# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal useModule description This module will discuss:High level DHR process with the countersNew counters for DHRNew KPIs for DHROptimization of DHR

# Nokia Siemens Networks Presentation / Author / DateFor internal useProcess high levelFree TCH DHR Limit For FR TCH ResourcesSearch candidatesCandidatesFound?Legacy Abis?Search CSDAPStart multiplexingHO to chosen TCHLegacy Abis?Activate CSDAPOSC call conversion done011263011264011265004235510135101401126601126701126601126700423751216DHR_MULTIPLEXING_ATTEMPTSDHR_MPLX_FAIL_DUE_TCH_RESCSDAP_RES_ALLOC_ATT_FOR_DHRHO_ATTEMPT_FROM_AMR_HR_TO_DHRHO_FROM_AMR_HR_TO_DHR_SUCCINTRA_HO_FROM_AMR_HR_TO_DHR011266yesyesnono# Nokia Siemens Networks Presentation / Author / DateFor internal use95connectionIn defined Window?Call conversion to OSC Legacy AbisFree TCH DHR Limit For FR TCH ResourcesCall in AMR-HR?ULlevel aUL&DLquality byesyes2nd Call in AMR (FR-HR)?UL&DL lev aUL&DL qual IHRFyesyesCSDAP Found?Start ofmultiplexingChannel activationSuccess?HO commandTo moving call HO successful?Activate CSDAP 2 waysCSDAP activationsuccessful?4237/51216A = OSC Multiplexing UL Rx Level Threshold B = OSC DHR Multiplexing Rx Quality ThresholdWindow = multiplexing window (c) = Rxlev1-window < rxlev2 < rxlev1 +window+ max pwr redSearching for OSC-0Candidate foundnononoyesSearching for OSC-1Pair found004235yesyesno004239Intra-cell HOcounters011266no011263Activate CSDAP 1wayOSC startedyesyes011266011267Balance the Call to same RXLevel011265011264* Find resourcesFrom USC connectionWith CSDAP011267Send over air interfaceCounterLegacy Abis processes51013510141266endBalance systemPower commandsyes*nono# Nokia Siemens Networks Presentation / Author / DateFor internal use96 BSS21309: Orthogonal subchannel with SAIC MSOSC_AMR_HR_475_UL_RXQUAL_0 122000 OSC_AMR_HR_475_DL_RXQUAL_0 122001 OSC_AMR_HR_475_UL_RXQUAL_7 122014OSC_AMR_HR_475_DL_RXQUAL_7 122015OSC_AMR_HR_515_UL_RXQUAL_0 122016OSC_AMR_HR_515_DL_RXQUAL_0 122017OSC_AMR_HR_515_UL_RXQUAL_7 122030OSC_AMR_HR_515_DL_RXQUAL_7 122031OSC_AMR_HR_590_UL_RXQUAL_0 122032OSC_AMR_HR_590_DL_RXQUAL_0 122033OSC_AMR_HR_590_UL_RXQUAL_7 122046OSC_AMR_HR_590_DL_RXQUAL_7 122047OSC_AMR_HR_670_UL_RXQUAL_0 122048OSC_AMR_HR_670_DL_RXQUAL_0 122049OSC_AMR_HR_670_UL_RXQUAL_7 122062OSC_AMR_HR_670_DL_RXQUAL_7 122063OSC_AMR_HR_740_UL_RXQUAL_0 122064OSC_AMR_HR_740_DL_RXQUAL_0 122065OSC_AMR_HR_740_UL_RXQUAL_7 122078OSC_AMR_HR_740_DL_RXQUAL_7 122079

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

2 Resource Availability MeasurementAVE_BUSY_DHR_TCH 002094AVE_BUSY_DHR_TCH_DENOM 002095PEAK_BUSY_DHR_TCH 002096

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

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

KPI s:Average DHR TrafficDHR Usage # Nokia Siemens Networks Presentation / Author / DateFor internal useKPIs for Orthogonal Sub-channel

KPIFormulaMeaningAverage DHR TrafficAVE_BUSY_DHR_TCH/AVE_BUSY_DHR_TCH_DENOMIndicates number of Erlangs served by DHR TCHDHR Usage Average DHR Traffic/ trf_1Indicates the portion of traffic served on DHR TCHTotal DHR Multiplexing Failure Rate SUM_OF_DHR_MULTIPLEXING_FAILURES/DHR_MULTIPLEXING_ATTEMPTSwhere SUM_OF_DHR_MULTIPLEXING_FAILURES=(DHR_MPLX_FAIL_DUE_TCH_RES+ DHR_MPLX_FAIL_DUE_CSDAP_RES+ DHR_MPLX_FAIL_DUE_OTHER)Gives failure rate of multiplexing AMR calls to DHR as the ratio between failed multiplexing HOs and number of multiplexing attemptsDHR Multiplexing Failure Rate due to Lack of Suitable PairDHR_MPLX_FAIL_DUE_RES (1264)/ DHR_MULTIPLEXING_ATTEMPTS (1263)Gives failure rate of multiplexing AMR calls to DHR caused by lack of suitable pair (pair of connections fulfilling DHR multiplexing criteria)DHR Multiplexing Failure Rate due to lack of CSDAP DHR_MPLX_FAIL_DUE_CSDAP_RES (1266)/DHR_MULTIPLEXING_ATTEMPTS (1263)

Gives failure rate of multiplexing AMR calls to DHR caused by lack of CSDAPDHR Multiplexing Failure Rate due to Other Reasons DHR_MPLX_FAIL_DUE_OTHER (1267)/ DHR_MULTIPLEXING_ATTEMPTS (1263)Gives failure rate of multiplexing AMR calls to DHR caused by unsuitable state of the call (e.g. OSC HO is started by RRM that is not aware of the call phase and might end up to situation where OSC HO is interrupted.# Nokia Siemens Networks Presentation / Author / DateFor internal useKPIs for Orthogonal Sub-channel

KPIFormulaMeaningCSDAP Allocation Failure RateDHR_MPLX_FAIL_DUE_CSDAP_RES/CSDAP_RES_ALLOC_ATT_FOR_DHRGives the CSDAP Allocation Failure ratio due to lack of CSDAP for OSC-1 subchannelAMR HR-to-DHR HO Success Rate HO_FROM_AMR_HR_TO_DHR_SUCC/HO_ATTEMPT_FROM_AMR_HR_TO_DHRGives success rate of multiplexing AMR HR calls to DHR as the ratio between succesful multiplexing HOs from AMR HR to DHR and number of multiplexing attemptsAMR HR-to-DHR HO RateHO_ATTEMPT_FROM_AMR_HR_TO_DHR/(HO_ATTEMPT_FROM_AMR_HR_TO_DHR+ HO_ATTEMPT_FROM_AMR_FR_TO_DHR)Gives the percentage of AMR HR-to-DHR HO Attempts AMR FR-to-DHR HO Success Rate (HO_FROM_AMR_FR_TO_DHR_SUCC/HO_ATTEMPT_FROM_AMR_FR_TO_DHRGives success rate of multiplexing AMR FR calls to DHR as the ratio between succesful multiplexing HOs from AMR FR to DHR and number of multiplexing attemptsAMR FR-to-DHR HO Rate

HO_ATTEMPT_FROM_AMR_FR_TO_DHR/(HO_ATTEMPT_FROM_AMR_HR_TO_DHR+ HO_ATTEMPT_FROM_AMR_FR_TO_DHR)Gives the percentage of AMR FR-to-DHR HO Attempts# Nokia Siemens Networks Presentation / Author / DateFor internal useKPIs for Orthogonal Sub-channel

KPIFormulaMeaningRxQual DHR Demultiplexing HO Success Rate HO_FROM_DHR_DUE_RX_QUAL_SUCC/HO_ATT_FROM_DHR_DUE_RX_QUALGives success rate of demultiplexing DHR calls to AMR HR or FR due to RxQual as the ratio between succesful demultiplexing HOs due to quality and number of demultiplexing attempts with the same causeUL RxLev Difference DHR Demultiplexing HO Success Rate HO_FROM_DHR_DUE_RXLEV_SUCC/HO_ATT_FROM_DHR_DUE_RXLEV_DIFFGives success rate of demultiplexing DHR calls to AMR HR or FR due to UL RxLev difference as the ratio between succesful demultiplexing HOs due to UL RxLev and number of demultiplexing attempts with the same causeRxLev DHR Demultiplexing HO Success Rate HO_FROM_DHR_DUE_RX_LEV_SUCC/HO_ATT_FROM_DHR_DUE_RX_LEVGives success rate of demultiplexing DHR calls to AMR HR or FR due to UL RxLev difference as the ratio between succesful demultiplexing HOs due to UL RxLev and number of demultiplexing attempts with the same causeDHR Demultiplexing HO Success Rate (HO_FROM_DHR_DUE_RX_QUAL_SUCC+ HO_FROM_DHR_DUE_RXLEV_SUCC + HO_FROM_DHR_DUE_RX_LEV_SUCC)/( HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_ATT_FROM_DHR_DUE_RX_LEV)Gives success rate of demultiplexing DHR calls to AMR HR or FR as the ratio between succesful demultiplexing HOs and number of demultiplexing attempts# Nokia Siemens Networks Presentation / Author / DateFor internal useKPIs for Orthogonal Sub-channel

KPIFormulaMeaningDHR Demultiplexing HO type (due to RxQual) Distribution HO_ATTEMPT_FROM_DHR_DUE_TO_RXQUAL / (HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_ATT_FROM_DHR_DUE_RX_LEV)

Gives the ratio of demultiplexing HO attempts due to RxQual in the all causes of demultiplexingDHR Demultiplexing HO type (due to UL RxLev difference) Distribution HO_ATT_FROM_DHR_DUE_RXLEV_DIFF / (HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_ATT_FROM_DHR_DUE_RX_LEV )

Gives the ratio of demultiplexing HO attempts due to UL RxLev difference in the all causes of demultiplexingDHR Demultiplexing HO type (due to RxLev) DistributionHO_ATT_FROM_DHR_DUE_RX_LEV / (HO_ATT_FROM_DHR_DUE_RX_QUAL+HO_ATT_FROM_DHR_DUE_RXLEV_DIFF+HO_ATT_FROM_DHR_DUE_RX_LEV)Gives the ratio of demultiplexing HO attempts triggered by Rx Level criterion (when Improved AMR Packing and Unpacking (BSS21483) is active) in the all causes of demultiplexing

Average CSDAP 8kbit/s subTSL Usage AVERAGE_CSDAP_SUBTSL_USAGE/AVERAGE_CSDAP_SUBTSL_USAGE_DENGives the average usage of CSDAP 8kbit/s subTSLPeak CSDAP utilization PEAK_CSDAP_8_KBIT/S_SUBTSL_USAGE / TOTAL_PCM_8_KBIT/S_SUBTSL_IN_CSDAPGives the peak utilization of CSDAP resources# Nokia Siemens Networks Presentation / Author / DateFor internal useKPIs for Orthogonal Sub-channel

KPIFormulaMeaningUL RxQual distributionE.g. [(OSC_AMR_HR_475_UL_RXQUAL_6+OSC_AMR_HR_515_UL_RXQUAL_6+OSC_AMR_HR_590_UL_RXQUAL_6+OSC_AMR_HR_670_UL_RXQUAL_6+OSC_AMR_HR_740_UL_RXQUAL_6)+(OSC_AMR_HR_475_UL_RXQUAL_7+OSC_AMR_HR_515_UL_RXQUAL_7+OSC_AMR_HR_590_UL_RXQUAL_7+OSC_AMR_HR_670_UL_RXQUAL_7+OSC_AMR_HR_740_UL_RXQUAL_7)] / [(OSC_AMR_HR_475_UL_RXQUAL_0+OSC_AMR_HR_515_UL_RXQUAL_0+OSC_AMR_HR_590_UL_RXQUAL_0+OSC_AMR_HR_670_UL_RXQUAL_0+OSC_AMR_HR_740_UL_RXQUAL_0)+ +(OSC_AMR_HR_475_UL_RXQUAL_7+OSC_AMR_HR_515_UL_RXQUAL_7+OSC_AMR_HR_590_UL_RXQUAL_7+OSC_AMR_HR_670_UL_RXQUAL_7+OSC_AMR_HR_740_UL_RXQUAL_7)]Gives the ratio of samples with given RxQual value to all samples in UL, e.g. UL Rxqual 6&7 Rate All AMR codecs are included in the formula not only the active ones# Nokia Siemens Networks Presentation / Author / DateFor internal useKPIs for Orthogonal Sub-channel

KPIFormulaMeaningDL RxQual distribution

E.g.:[(OSC_AMR_HR_475_DL_RXQUAL_6+OSC_AMR_HR_515_DL_RXQUAL_6+OSC_AMR_HR_590_DL_RXQUAL_6+OSC_AMR_HR_670_DL_RXQUAL_6+OSC_AMR_HR_740_DL_RXQUAL_6)+(OSC_AMR_HR_475_DL_RXQUAL_7+OSC_AMR_HR_515_DL_RXQUAL_7+OSC_AMR_HR_590_DL_RXQUAL_7+OSC_AMR_HR_670_DL_RXQUAL_7+OSC_AMR_HR_740_DL_RXQUAL_7)] / [(OSC_AMR_HR_475_DL_RXQUAL_0+OSC_AMR_HR_515_DL_RXQUAL_0+OSC_AMR_HR_590_DL_RXQUAL_0+OSC_AMR_HR_670_DL_RXQUAL_0+OSC_AMR_HR_740_DL_RXQUAL_0)+ +(OSC_AMR_HR_475_DL_RXQUAL_7+OSC_AMR_HR_515_DL_RXQUAL_7+OSC_AMR_HR_590_DL_RXQUAL_7+OSC_AMR_HR_670_DL_RXQUAL_7+OSC_AMR_HR_740_DL_RXQUAL_7)]Gives the ratio of samples with given RxQual value to all samples in DL, e.g. DL Rxqual 6&7 Rate

All AMR codecs are included in the formula not only the active ones# Nokia Siemens Networks Presentation / Author / DateFor internal useMain drivers for getting OSC traffic

#BCSU/BTS

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC optimization - DHRLIMDHRLIM is the load threshold that defines when the OSC mechanism should startThe DHRLIM should be smaller or equal to (A)FRL or (A)HRLIn the graph the DHRLIM has been changed from 10 to 50

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC optimization - Multiplexing attempts

Multiplexing attemptsMultiplexing attempts are showing how many possible candidates are available for OSC

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC optimization - OMLTThe OMLT defines the maximum level that the OSC mechanism is searching for a candidate (both pairs)In the bellow figure the OMLT has been changed from -85dBm to -95dBm

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC optimization - ODMQTOMDQT controls the quality for the OSC calls to be multiplexed together with the IHRF (Intra HO threshold RXQuality AMR FR). Default value is 1 and is good value to start with. ODMQT should be at least same or smaller value than the IHRF

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC optimization - ODMRGWith ODMRG the demultiplexing level difference is changed. Meaning how far are we letting the mobiles drift before disconnecting them. The default value is 14dB. This parameter should be especially looked at if the quality is good and the demultiplexing reason is more than 30% due to window difference.

# Nokia Siemens Networks Presentation / Author / DateFor internal useOSC optimization other parametersODDQTThis is the demultiplexing based on qualitydefault value is 3. In the pilot / projects it has been set to 5 without any problemsSetting it to higher value will keep the calls longer in OSC untilThey pass the quality thresholdMake an external handoverDisconnect / dropTDRQT / TURQTInter cell HO for DL / UL has been set to 6 and was not providing problems. Default value is 4.

# Nokia Siemens Networks Presentation / Author / DateFor internal useRxquality changes Quality distributionThe quality of the DHR will or will not be seen in the KPIsThis depends on the DHR share out of total AMR-HRIn general there are two possibilities, which one is more common?

# Nokia Siemens Networks Presentation / Author / DateFor internal useRxquality changes Quality is most likely to improve if looking at the UL quality distribution of the AMR and OSC in relation to AMRAMR degrades slightly due to the OSC calls (from AMR-HR) are the best in the cell and are not longer updateing the AMR distributionDue to OSC there is more room on the cells and the MSs are staying in the dominance area rather than going to non optimal cell due to congestion

# Nokia Siemens Networks Presentation / Author / DateFor internal useRxquality changes BH Rxquality distibution in BH cluster level

# Nokia Siemens Networks Presentation / Author / DateFor internal useKPIs to follow during OSC projectSAIC Penetrationc1263 DHR MULTIPLEXING ATTEMPTSSAIC Traffic share (1 hour meas time)Successful OSC multiplexing HOstrf_202/ Average CS Traffic (Erl)hfr_1000/ Total DHR Multiplexing Failure Rateblck_8i/ TCH call blockinghfr_1001/ DHR Multiplexing Failure Rate due to Lack of Suitable Pairdcr_8i/ TCH drop call ratio, after TCH assignment, without REhfr_1002/ DHR Multiplexing Failure Rate due to CSDAPblck_5b/ SDCCH blocking on, before FCShfr_1003/ DHR Multiplexing Failure Rate due to Other Reasonstrf_122a/ TCH traffic share of HR AMR callsho_1000/ AMR HR-to-DHR HO Ratetrf_197/ TCH capacity usage by CS traffic (%)hsr_1000/ AMR HR-to-DHR HO Success Ratetrf_81/TCH free marginho_1001/ AMR FR-to-DHR HO Ratedlq_2a/ Bad DL cumulative quality ratio % in classes 5,6,7hsr_1001/ AMR FR-to-DHR HO Success Ratedlq_1000/ Bad DL cumulative quality ratio for OSC % in classes 5,6,7DHR demultiplexing attemptsulq_2a/ Bad UL cumulative quality % in class 5,6,7Successful OSC demultiplexing HOsulq_1000/ Bad UL cumulative quality ratio for OSC % in classes 5,6,7hsr_1005/ DHR Demultiplexing HO Success RateDL RX-LEVEL distributionOSC mux HOs per demux HOsUL RX-LEVEL distributionhsr_1002/ RxQual DHR Demultiplexing HO Success Ratepwr_1/MS Average power (dbm)ho_1002/ RxQual DHR Demultiplexing HO sharetrf_2d/ Average call length (sec)hsr_1003/ UL RxLev Difference DHR Demultiplexing HO Success Rateho_24/ Intra-cell HO attemptsho_1003/ UL RxLev Difference DHR Demultiplexing HO shareIntra cell HO per traffichsr_1004/ RxLev DHR Demultiplexing HO Success Ratehsr_9a/ Intra-cell TCH-TCH HO success ratioho_1004/ RxLev DHR Demultiplexing HO sharec4142 HO ATT FOR AMR TO HRhfr_1004/ CSDAP Allocation Failure Ratec4143 HO ATT FOR AMR TO FRCSDAP Sizeava_44/ Average available area level PS territory size for nTRXsAverage CSDAP 8kbit/s subTSL Usageblck_30/ Territory upgrade rejection due to CSWPeak CSDAP 8kbit/s subTSL Usagetbf_38d/ Average number of DL TBFs per timeslotPeak CSDAP Utilizationtrf_473/ DHR Usageho_11/ Outgoing inter-cell HO attemptstrf_472/ Average DHR trafficho_13h/ HO attempts, outgoing and intracellPeak Busy DHR TCHho_65/ Total HO success ratio, ISHO excludedhsr_6a/ BSC controlled outgoing TCH-TCH HO success ratiohsr_28/ Total HO Success Rate, ISHO included# Nokia Siemens Networks Presentation / Author / DateFor internal useAlarms With OSC a few new and changed alarms have been defined and should be followed. 3536 CIRCUIT SWITCHED DYNAMIC ABIS POOL FAILURECSDAP 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 FAILURESeveral 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 THRESHOLDThe 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 THRESHOLDMean 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.

# Nokia Siemens Networks Presentation / Author / DateFor internal useTest cases# Nokia Siemens Networks Presentation / Author / DateFor internal use# Nokia Siemens Networks Presentation / Author / DateFor internal useProject setup The following competences are need for the trial1 x (Technical) project manager1-2 x Radio engineer (depending on the size of project and if SDC is used or not)1 x Access transmission engineer (optional initially 100%, later maybe 10% (please evaluate)1 x BSC engineerSDC for post processing PM and CM datatools are in-house tool for post processing datadrive test team + analysis (optional)

# Nokia Siemens Networks Presentation / Author / DateFor internal useProject duration0th weekSite selection (customer of own team) and test preparation together with the data (initial parameters for OSC & CSDAP or PacketAbis)1st week Initial baseline perf