OSC FEATURE IN NOKIA BSS

OSC – Orthogonal Sub ChannelDHR – Double Half Rate

1 © Nokia Siemens Networks 2013For internal use

Orthogonal Sub ChannelDouble Half Rate

Agenda

• Introduction• Feature Details• Interworking and Compatibility Issues• Configuration Management• Performance Measurements

2 © Nokia Siemens Networks RSO-Opti./OSC

For internal use only

and Compatibility Issues

Measurements

OSC- Introduction

3 © Nokia Siemens NetworksFor internal use only

OSC- Introduction

Orthogonal Sub -Channel

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

• In RG20 the OSC feature was introduced.• OSC adds new channel mode: Double Half Rate (DHR)• With DHR mode up to 4 AMR HR connections may be allocated on one radio TSL.



• With DHR mode up to 4 AMR HR connections may be allocated on one radio TSL.• DHR mode applies only to AMR connections for SAIC

indicating its SAIC capability to the NW.

• OSC –DHR feature increases hardware efficiency � Increased TRX voice capacity (up to double in optimal radio condition)� Increased capacity for PS traffic (by saving RTSL occupied by CS traffic)� Lower site density to provide same coverage and capacity� Improved energy efficiency

Up to RG10 two channel modes were supported: AMR speech codecs)AMR speech codecs)

OSC adds new channel mode: Double Half Rate (DHR)With DHR mode up to 4 AMR HR connections may be allocated on one radio TSL.With DHR mode up to 4 AMR HR connections may be allocated on one radio TSL.DHR mode applies only to AMR connections for SAIC-capable mobile stations

DHR feature increases hardware efficiency Increased TRX voice capacity (up to double in optimal radio condition)Increased capacity for PS traffic (by saving RTSL occupied by CS traffic)Lower site density to provide same coverage and capacity

Feature Details


Feature Details

Overview (1)

• OSC is a voice capacity feature that allows assigning 2 AMR HR connections on the same TCH HR channel (defined as either TCHD or TCHH)

• OSC comprises the following features:� OSC Half Rate with SAIC MS (BSS21309)� CSDAP- Circuit Switched Dynamic Abis

� It is required incase of legacy Abis



� It is required incase of legacy Abisfor second OSC connection.

� Not required if Packet Abis is in use.

• OSC requires Single Antenna Interference Cancelation (SAIC) receiver in MSs.� BSC applies OSC only to those MSs which indicate their SAIC support.

OSC is a voice capacity feature that allows assigning 2 AMR HR connections on the same TCH HR channel (defined as either TCHD or

OSC comprises the following features:OSC Half Rate with SAIC MS (BSS21309)

Abis Pool (BSS30385)Abis to provide the additional Abis capacity Abis to provide the additional Abis capacity

is in use.

OSC requires Single Antenna Interference Cancelation (SAIC) receiver in

BSC applies OSC only to those MSs which indicate their SAIC support.

Overview (2)

• Two AMR HR connections being allocated on the same TCH/H channel are regarded as DHR calls.

• TCH/H channel to be allocated to DHR calls is split into 2 (orthogonal) sub channels (OSC-0 & OSC-1)

• The separation between OSC-0 & OSCSequence Codes

• OSC-0 sub-channel is assigned a ‘legacy’ TSC and uses ‘legacy’



• OSC-0 sub-channel is assigned a ‘legacy’ TSC and uses ‘legacy’ transport resources.

• OSC-1 sub-channel is assigned a ‘pairAbis transport resources (provided by either CSDAP or packet

Two AMR HR connections being allocated on the same TCH/H channel

TCH/H channel to be allocated to DHR calls is split into 2 (orthogonal) sub

0 & OSC-1 is achieved by using Training

channel is assigned a ‘legacy’ TSC and uses ‘legacy’ Abischannel is assigned a ‘legacy’ TSC and uses ‘legacy’ Abis

channel is assigned a ‘pair-wise’ TSC and uses ‘additional’ transport resources (provided by either CSDAP or packet Abis)

Overview (3)

• OSC uses QPSK modulation in DL • QPSK modulation carries 2 OSC channels

which can be received by legacy SAIC MS like normal GMSK

• Separate reception of 2 sub-channels is possible by orthogonality achieved with appropriately selected TSCs.

• BTS uses dynamically GMSK or QPSK



• BTS uses dynamically GMSK or QPSK • If there is only one AMR HR connection

in a TCH/H, the channel performs as traditional AMR HR TCH

QPSK modulation carries 2 OSC channels which can be received by legacy SAIC MS

TSC for OSC-0 TSC for OSC-1

0 2

1 7

If there is only one AMR HR connection in a TCH/H, the channel performs as

1 7

2 0

3 4

4 3

5 6

6 5

7 1

Optimized TSC pairs for OSC

Overview (4)

• OSC concept in UL is based on traditional GMSK modulation and MUUser MIMO) technique

• In UL, two users are differentiated by TSC (same TSC pair as in DL is used)• BTS separates users with Rx Diversity and interference cancellation techniques• Rx level balance between 2 connections occupying paired OSC

channels is needed to provide sufficient quality.



is based on traditional GMSK modulation and MU-MIMO (Multi

In UL, two users are differentiated by TSC (same TSC pair as in DL is used)BTS separates users with Rx Diversity and interference cancellation techniquesRx level balance between 2 connections occupying paired OSC-0 & OSC-1 sub-channels is needed to provide sufficient quality.

OSC- RRMDHR Multiplexing (1)• DHR multiplexing is triggered based on the load criterion.• Load criteria is checked upon receiving a report from HO &

PC algorithm with updated values of Rx Quality & Rx Level.• If the % of free FR TCH resources decreases below

Triggering OSC DHR Multiplexing, the BTS enters DHR multiplexing mode & starts searching for the best pair to be multiplexed into DHR mode.

• Only one pair is multiplexed at a time



•• DHR multiplexing is realized by handing over AMR FR/HR

connection to the target channel with ongoing AMR HR call having sufficient quality and UL Rx Level

• First the best target channel is searched for (the 1candidate)• Only TCH/H allocated to SAIC MS for AMR call may be

regarded as a target channel for DHR multiplexing

• Next, the best connection to be handed over to target channel is searched for (the 2nd candidate)

DHR multiplexing is triggered based on the load criterion.Load criteria is checked upon receiving a report from HO & PC algorithm with updated values of Rx Quality & Rx Level.If the % of free FR TCH resources decreases below Limit for

the BTS enters DHR multiplexing mode & starts searching for the best pair to be

Yes

Yes

DHR multiplexing is realized by handing over AMR FR/HR connection to the target channel with ongoing AMR HR call

First the best target channel is searched for (the 1st

Only TCH/H allocated to SAIC MS for AMR call may be regarded as a target channel for DHR multiplexing

Next, the best connection to be handed over to target

OSC- RRMDHR Multiplexing (2)Searching for the best target channel

• Only TCH/H with ongoing SAIC AMR call may become a target channel for DHR multiplexing

• UL Rx Level criterion: -47dBm > UL RxLev > Multiplexing UL Rx Level Threshold

• UL & DL Quality criterion:

UL(DL) RxQual < Multiplexing Rx Quality Threshold



UL(DL) RxQual < Multiplexing Rx Quality Threshold

• The list of channels fulfilling above conditions is sorted in descending order according to UL path-loss criterion (ULRxLev + current power reduction)

• The 1st channel in the list is selected as the best target channel (1st candidate)

Only TCH/H with ongoing SAIC AMR call may become a

Multiplexing UL Rx Level Threshold

< Multiplexing Rx Quality Threshold< Multiplexing Rx Quality Threshold

The list of channels fulfilling above conditions is sorted in loss criterion

channel in the list is selected as the best target

OSC- RRMDHR Multiplexing (3)Searching for the 2nd candidate

• Searching for the best 2nd candidate is done among SAIC connections (AMR FR & HR)

• The list of 2nd candidates is created based on the UL Rx Level Window criterion

• Candidates for DHR multiplexing HO must fulfill the following criteria:UL & DL RxQual ≤ Intra HO Threshold Rx Qual

and

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



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

candidate is done among SAIC connections (AMR FR & HR)

candidates is created based on the UL Rx Level Window criterion

Candidates for DHR multiplexing HO must fulfill the following criteria:Qual AMR FR

Multiplexing UL Rx Level Threshold Multiplexing UL Rx Level Threshold

OSC- RRMPower Control• Power control algorithm for DHR is similar to the one used for non

• Legacy RX Level thresholds are re-used• New DHR specific Rx Quality thresholds are introduced

� 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

•



• DL PC is performed for both paired DHR connections separately (based on Rx Level & Quality criteria), but used TX power is determined by the weaker connection.• Individual Tx power levels are commanded to BTS• BTS selects the higher DL power level (among 2 commanded ones) and applies it for

both paired DHR connections• 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

Power control algorithm for DHR is similar to the one used for non-DHR connections

New DHR specific Rx Quality thresholds are introduced

DL PC is performed for both paired DHR connections separately (based on Rx Level & but used TX power is determined by the weaker connection.

power levels are commanded to BTSBTS selects the higher DL power level (among 2 commanded ones) and applies it for

UL PC is performed for both paired DHR connections independently (based on Rx Level and

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

OSC- RRMInter-cell DHR Handovers• 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 (

Rx Qual DHR and Threshold Ul Rx Qual DHR) and legacy Rx Level thresholds (Downlink Rx Level and Threshold Level Uplink Rx Level

DHR Demultiplexing HO• DHR demultiplexing HO (intra-cell HO from DHR to non



• DHR demultiplexing HO (intra-cell HO from DHR to non• Rx Quality criterion - Demultiplexing Rx Quality Threshold

• UL Rx Level balance criterion - OSC Demultiplexing UL

DHR connection may be handed over to the other cell but only to AMR HR/FR channel mode

cell handovers are not possiblecell HO for DHR connections are controlled with new Rx Quality thresholds (Threshold Dl

and legacy Rx Level thresholds (Threshold Level Threshold Level Uplink Rx Level are re-used)

cell HO from DHR to non-DHR mode) can be triggered by:cell HO from DHR to non-DHR mode) can be triggered by:Demultiplexing Rx Quality Threshold

OSC Demultiplexing UL RxLevel Margin

OSC- CSDAPCircuit Switched Dynamic Abis Pool (1)• For OSC DHR mode more Abis transmission is needed for radio timeslot because two calls

are multiplexed in one HR channel

MS1FR

freeFR

A single RTSL carrying FR call



A single RTSL carrying FR callis mapped to a single Abis sub-TSL

MS1HR

freeHR

HR (time) multiplexing

MS1HR

MS2HR


A single RTSL carrying HR (1 or 2 calls) is mapped to a single Abis sub-TSL

Pool (1)transmission is needed for radio timeslot because two calls


OS

C

mul

tiple

xing

MS2 OSC-0

MS1 OSC-0

free OSC-1

free OSC-1


free OSC-0

MS1 OSC-0

MS2 OSC-1

free OSC-1 O

SC

m

ultip

lexi

ng

Examples of “unpaired” OSC calls where MS2 mapped to- OSC-0 uses TCH area (no CSDAP resources will be used)- OSC-1 uses CSDAP

In OSC mode 2 DHR calls are transmitted in the same ti me OSC-0 channels always use PCM resources reserved fo r TCH while OSC-1 channels always use PCM resources reserved in CSDAP


MS3 OSC-0

MS2 OSC-1 O

SC

m

ultip

lexi

ng

MS4 OSC-1

MS1 OSC-0

OSC- CSDAPCircuit Switched Dynamic Abis Pool (2)Main characteristics of CSDAP

• CSDAPs are created per BCF basis

• Up to 4 CSDAPs can be created per BCF

• Up to 1000 CSDAPs can be created per BSC

• CSDAP is shared by all TRXs hosted by given BCF

•



• CSDAP must be created in consecutive PCM TSLs.

• CSDAP size ranges from 1-31 TSL for E1 (1PCM TSL (64 kbps)

Pool (2)

Up to 4 CSDAPs can be created per BCF

Up to 1000 CSDAPs can be created per BSC

CSDAP is shared by all TRXs hosted by given BCF

CSDAP must be created in consecutive PCM TSLs.

31 TSL for E1 (1-24 for T1) with granularity of 1

OSC- CSDAPCircuit Switched Dynamic Abis Pool (3)CSDAP Dimensioning Calculation – Example

• Consider a Site (4+4+4) with following assumptions

• Total traffic carried by site : 90 Erl

• OSC Traffic : 15 Erl

• Half of the OSC traffic will occupy legacy Abis



• Half of the OSC traffic will occupy legacy Abis

• Trunks required for 7.5 Erl traffic as per eralng

• i.e., CSDAP required = 14/2 = 7 Abis Sub Tsl

• CSDAP required per BCF = 2 Abis TSL

Pool (3)Example

) with following assumptions

Abis resources.Abis resources.

eralng-B table is 14

Tsl (as 2 OSC-DHR call will use 1 Abis Sub-TSL)

Feature Dependencies & Compatibilities


Feature Dependencies & CompatibilitiesFeature Dependencies & CompatibilitiesFeature Dependencies & Compatibilities

OSCFeature Dependencies

BSS BSC*BTS

TalkFamilyBTS

MetroSite

Release RG20 S15.1 Not supported Not supported

* Supported by BSCi, BSC2i, BSC3i and FlexiBSC

BTSFlexi EDGE

BTSUltraSite

BTSFlexi Multiradio

19 © Nokia Siemens Networks RSO-Opti./OSCFor internal use only

Release SW: EX4.1 CX8.1 EX4.1

DX200Platform

MS SGSN

Release No dependency

SAIC indicating its capability

No dependency dependency

BTSBTSplus

Not supported

Multiradio

MCS RAN NetAct

No dependency

No dependency OSS5.3 CD set 2

OSC

OSC specific License requirement:

• 1531: OSC Half rate with SAIC MS (Includes 100 simultaneous OSC call pairs)

• 1968: OSC HR Capacity (Additional OSC capacity, per 100 OSC calls)

• 1671: Circuit Switched Dynamic Abis Pool (per TRX)


1531: OSC Half rate with SAIC MS (Includes 100 simultaneous OSC call pairs)

1968: OSC HR Capacity (Additional OSC capacity, per 100 OSC calls)

Pool (per TRX)

OSCFeature Interdependencies (1)• AMR HR is a prerequisite for Double Half Rate

• Support for SAIC is mandatory

• AMR HR packing must be in use

• CSDAP or Packet-Abis required for additional

• Rx diversity must be enabled

• Baseband Hopping



• Baseband Hopping• To apply DHR multiplexing in BB scenario, all the TRXs of BTS must be OSC configured

• Antenna Hopping• DHR multiplexing cannot be enabled on select TRXs, if Antenna Hopping is in use

• To apply DHR multiplexing in AH scenario, all the TRXs of BTS must be OSC configured

AMR HR is a prerequisite for Double Half Rate

required for additional Abis capacity

To apply DHR multiplexing in BB scenario, all the TRXs of BTS must be OSC configured

DHR multiplexing cannot be enabled on select TRXs, if Antenna Hopping is in use

To apply DHR multiplexing in AH scenario, all the TRXs of BTS must be OSC configured

OSCFeature Interdependencies (2)• Double Power TRX & Intelligent Downlink Diversity

• DHR multiplexing can not be enabled in either DPTRXs or IDD TRXs

• DHR multiplexing is not performed in TRXs with 4UD (4feature in use

• OSC can not be enabled if ‘Extended Cell Range’ is in use

• DHR multiplexing is not applied to Emergency calls



Double Power TRX & Intelligent Downlink DiversityDHR multiplexing can not be enabled in either DPTRXs or IDD TRXs

DHR multiplexing is not performed in TRXs with 4UD (4-Way Uplink Diversity)

OSC can not be enabled if ‘Extended Cell Range’ is in use

DHR multiplexing is not applied to Emergency calls

OSCFlexi EDGE TRX capability • Epsilon TRX 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 of Epsilon DTRX then OSC can not be applied in the other TRX of the DTRX.

• In case of Odessa TRX this limitation does not apply.• How to verify TRX HW variants (Odessa or Epsilon)



• How to verify TRX HW variants (Odessa or Epsilon)• Different module description codes:

• Epsilon : EXxA (EXTA-GSM800,EXGA• Odessa : EXxB

• This information may be retrieved via BTS Manager session direct to a BTS site.

Epsilon TRX does not support the concurrent use of EGPRS and OSC within a Dual

This limitation refers to EGPRS only and not to GPRSIf EGPRS is applied in one of Epsilon DTRX then OSC can not be applied in the

In case of Odessa TRX this limitation does not apply.How to verify TRX HW variants (Odessa or Epsilon)How to verify TRX HW variants (Odessa or Epsilon)

GSM800,EXGA-GSM900,etc)

This information may be retrieved via BTS Manager session direct to a BTS site.

Configuration Management



DHR parameters (1)DHR parameters (1)

OSC - Configuration Management

limForTriggeringOscDhrMultiplexing Limit for Triggering OSC DHR Multiplexing

object: BTSunit: %range: 0..100default: 0MML command: EQM, EQOMML abbr. name: DHRLIM

This parameter controls the status of the OSC DHR w ith SAIC MS feature in a BTS. 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. To enable the DHR multiplexing the parameter must b e set to value different than zero


oscMultiplexingUlRxLevelThr OSC Multiplexing UL Rx Level Threshold

object: HOCunit: dBmrange: -110..-47default: -85MML command: EHC, EHS, EHOMML abbr. name: OMLT

This parameter determines the UL Rx Level criterion for searching DHR multiplexing candidates (both 1st and 2Only calls with UL Rx level greater than or equal to this threshold, can be regarded as DHR multiplexing candidates.


Limit for Triggering OSC DHR Multiplexing

This parameter controls the status of the OSC DHR w ith SAIC MS feature in a BTS. It determines the load threshold for triggering DHR multiplexing: if the percentage of free FR TCH decreases below the value of this parameter, DHR multiplexing procedure is attempted. To enable the DHR multiplexing the parameter must b e set to value different than zero .

OSC Multiplexing UL Rx Level Threshold

determines the UL Rx Level criterion for searching DHR multiplexing and 2nd candidate must fulfill this criterion).

Only calls with UL Rx level greater than or equal to this threshold, can be regarded as DHR multiplexing candidates.

DHR parameters DHR parameters (2)(2)


oscDhrMultiplexingRxQualityThr OSC DHR Multiplexing object: HOCdefault: 0MML command: EHC, EHQ, EHOMML abbr. name: ODMQT

This parameter the DHR multiplexing candidate

oscMultiplexingUlRxLevelWindow OSC Multiplexing UL Rx Level Windowobject: HOC This parameter


object: HOCunit: dBrange: 0..20default: 10MML command: EHC, EHS, EHOMML abbr. name: OMLW

This parameter the 2nd DHR multiplexing candidate (connection to be handed over to the target channel).

oscDemultiplexingUlRxLevMargin OSC Demultiplexing UL Rx Level Marginobject: HOCunit: dBrange: 0..63default: 14MML command: EHC, EHS, EHOMML abbr. name: ODMRG

This parameter determines the UL Rx Level Difference criterion for DHR demultiplexing HO.


OSC DHR Multiplexing Rx Quality ThresholdThis parameter determines the UL and DL Rx Quality criterion for searching the DHR multiplexing candidate

OSC Multiplexing UL Rx Level WindowThis parameter determines the UL Rx Level Difference criterion for searching This parameter determines the UL Rx Level Difference criterion for searching

DHR multiplexing candidate (connection to be handed over to the target channel).

OSC Demultiplexing UL Rx Level MarginThis parameter determines the UL Rx Level Difference criterion for DHR demultiplexing HO.



oscDhrDemultiplexingRxQualityThr OSC DHR Demultiplexing object: HOCrange: 0..7default: 3MML command: EHQ, EHOMML abbr. name: ODDQT

This parameter determines the UL and DL Rx Quality thresholds for DHR demultiplexing HO.If UL or DL Rx quality of DHR connection reaches or exceeds this threshold, demultiplexing HO to non

thrDl/ULRxQualDhr Threshold DL/UL object: HOC This parameter determines DL/UL Rx Quality threshold for inter


object: HOCrange: 0..7default: 4MML command: EHC, EHQ, EHOMML abbr. name: TD/URQD

This parameter determines DL/UL Rx Quality threshold for interconnections.If DL/UL RxQualover to a new cell to non

pcLower/UpperThresholdDl/ULRxQualDhr PC Lower/Upper Threshold DL/UL

object: POCrange: 0..7default: 3MML command: EUC, EUO, EUQ MML abbr. name: L/UD/UDHR

This parameter determines DL/UL Rx Quality threshold for BTS power increase for DHR connections.


OSC DHR Demultiplexing Rx Quality Thresholddetermines 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

Threshold DL/UL RxQual DHRdetermines DL/UL Rx Quality threshold for inter-cell HO for DHR determines DL/UL Rx Quality threshold for inter-cell HO for DHR

reaches or exceeds this threshold, DHR connection is handed over to a new cell to non-DHR mode (AMR HR or FR).

PC Lower/Upper Threshold DL/UL RxQual DHR

determines DL/UL Rx Quality threshold for BTS power increase for DHR connections.



trxOSCCapability TRX OSC Capabilityobject: TRXrange: 0..4step: 1default: 0MML command: ERO

This parameter indicates whether TRX supports OSC feature. This is read-only parameter. Its value is set by the system. 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 lost



TRX OSC CapabilityThis parameter indicates whether TRX supports OSC feature.

only parameter. Its value is set by the system. TRX is not OSC capableTRX is OSC capableTRX OSC capability is temporarily lostTRX is capable of OSC without EGPRSTRX OSC capability without EGPRS is temporarily lost

Performance Management


Performance Management

New Counters (1)New Counters (1)

OSC - Performance Measurements

Counter name Description

DHR_MULTIPLEXING_ATTEMPTS (001263)(Traffic Measurement)

This counter provides the number of DHR multiplexing procedures triggered by load criterion.

DHR_MPLX_FAIL_DUE_TCH_RES (001264)(Traffic Measurement)

This counter provides the number of DHR multiplexing failures due to lack of suitable DHR multiplexing candidates.

DHR_MPLX_FAIL_DUE_CSDAP_RES This counter provides the number of CSDAP resources allocation


DHR_MPLX_FAIL_DUE_CSDAP_RES (001266)(Traffic Measurement)`

This counter provides the number of CSDAP resources allocation failures for DHR, due to lack of CSDAP resources.

DHR_MPLX_FAIL_DUE_OTHER (001267)(Traffic Measurement)

This counter provides the number of DHR multiplexing failures due to unsuitable state of the call.

CSDAP_RES_ALLOC_ATT_FOR_DHR (001265)(Traffic Measurement)

This counter provides the number of CSDAP resources allocation attempts for

Performance Measurements

DescriptionThis counter provides the number of DHR multiplexing procedures triggered by load criterion.

This counter provides the number of DHR multiplexing failures due to lack of suitable DHR multiplexing candidates.

This counter provides the number of CSDAP resources allocation This counter provides the number of CSDAP resources allocation failures for DHR, due to lack of CSDAP resources.

This counter provides the number of DHR multiplexing failures due to unsuitable state of the call.

This counter provides the number of CSDAP resources allocation attempts for DHR.




AVE_BUSY_DHR_TCH (002094)(Resource Availability Measurement)

This counter provides the sum of the number of busy DHR TCHsNote: two DHR connections paired in one TCH/H chann el are counted as one DHR TCH. Hence to obtain real number of DHR calls t he value provided with this this counter must be multiplied by 2.

AVE_BUSY_DHR_TCH_DENOM (002095)(Resource Availability Measurement)

This counter provides the number of measurement samples for busy DHR TCHs


(Resource Availability Measurement)

PEAK_BUSY_DHR_TCH (002096)(Resource Availability Measurement)

This counter provides the peak number of busy DHR TCHs within an observation period.


HO_ATTEMPT_FROM_AMR_HR_TO_DHR (004235)(Handover Measurement)

This counter provides the number of DHR multiplexing handover attempts for an AMR HR connections.

HO_FROM_AMR_HR_TO_DHR_SUCC (004237)(Handover Measurement)

This counter provides the number of successful AMR HRhandovers.


This counter provides the sum of the number of busy DHR TCHsNote: two DHR connections paired in one TCH/H chann el are counted as one DHR TCH. Hence to obtain real number of DHR calls t he value provided with this this counter must be multiplied by 2.

This counter provides the number of measurement samples for busy DHR TCHs

This counter provides the peak number of busy DHR TCHs within an observation

This counter provides the number of DHR multiplexing handover attempts for an AMR HR connections.

This counter provides the number of successful AMR HR-to-DHR multiplexing




HO_ATTEMPT_FROM_AMR_FR_TO_DHR (004236)(Handover Measurement)

This counter provides the number of DHR multiplexing handover attempts from an AMR FR connections.

HO_FROM_AMR_FR_TO_DHR_SUCC (004238)(Handover Measurement)

This counter provides the number of successful AMR FRmultiplexing handovers.



UNSUCC_HO_TO_DHR_DUE_MISMATCH (004239)(Handover Measurement)

This counter provides the number of failed DHR multiplexing handovers due to CSDAP conflict between BSC and BTS.


DescriptionThis counter provides the number of DHR multiplexing handover attempts from an AMR FR connections.

This counter provides the number of successful AMR FR-to-DHR multiplexing handovers.

DescriptionThis counter provides the number of failed DHR multiplexing handovers due to CSDAP conflict between BSC and BTS.




HO_ATT_FROM DHR DUE_RX_QUAL (004240)(Handover Measurement)

This counter provides the number of DHR demultiplexing HO attempts triggered by Rx Quality criterion.

HO_FROM_DHR_DUE_RX_QUAL_SUCC (004242)(Handover Measurement)

This counter provides the number of successful DHR demultiplexing HO triggered by Rx Quality criterion.



HO_ATT_FROM_DHR_DUE_RXLEV_DIFF (004241)(Handover Measurement)

This counter provides the number of DHR demultiplexing HO attempts triggered by UL Rx Level Difference (Unbalance) criterion.

HO_FROM_DHR_DUE_RXLEV_SUCC (004243)(Handover Measurement)

This counter provides the number of successful DHR demultiplexing HO triggered by UL Rx Level Difference criterion.


This counter provides the number of DHR demultiplexing HO attempts triggered by Rx

This counter provides the number of successful DHR demultiplexing HO triggered by

This counter provides the number of DHR demultiplexing HO attempts triggered by UL Rx Level Difference (Unbalance) criterion.

This counter provides the number of successful DHR demultiplexing HO triggered by UL Rx Level Difference criterion.




HO_ATT_FROM_DHR DUE_RX_LEV (004251)(Handover Measurement)

This counter provides the number of DHR demultiplexing HO attempts triggered by Rx Level criterion

HO_FROM_DHR_DUE_RX_LEV_SUCC (004252)(Handover Measurement)

This counter provides the number of successful DHR demultiplexing HO triggered by Rx Level criterion



AVERAGE_CSDAP_SUBTSL_USAGE (121001)(CSDAP Measurement)

This counter provides the sum of the number of busy 8kbit/s

AVERAGE_CSDAP_SUBTSL_USAGE_DEN (121002)(CSDAP Measurement)

This counter provides the number of measurement samples for busy 8kbit/s CSDAP

PEAK_CSDAP_SUBTSL_USAGE (121003)(CSDAP Measurement)

This counter provides the peak usage of 8kbit/s


This counter provides the number of DHR demultiplexing HO attempts triggered by Rx

This counter provides the number of successful DHR demultiplexing HO triggered by

This counter provides the sum of the number of busy 8kbit/s subTSL in CSDAP

This counter provides the number of measurement samples for busy 8kbit/s subTSL in

This counter provides the peak usage of 8kbit/s subTSL in CSDAP.



Measurements Description

OSC RX Quality Measurementscounters: 122000-122079

This group of counters collects UL and DL Rx Quality statistics for DHR mode.There are separate counters (each comprising 8 AMR HR codec.



This group of counters collects UL and DL Rx Quality statistics for DHR mode.There are separate counters (each comprising 8 RxQual bins) for each TRX and each

Possible Feature Impact ExamplesPossible Feature Impact Examples

OSC – Feature Impact Analysis

Feature impact How to measure

Lower TCH blocking KPIs:� TCH Call Blocknig

Higher TCH Traffic Carried and/or Lower TSL Utilization by CS Traffic

KPIs:�

• The feature impact highly depends on the DHR mode usage (determined by SAIC MS penetration, network scenario and OSC


TSL Utilization by CS Traffic � Average CS Traffic� Normal TCH Usage Ratio for CS

Feature impact How to measure

Larger PS Territory KPIs:� Average Available PS Territory Size

Lower TBF Multiplexing KPIs:� Average DL TBF per TSL

Lower Multislot Allocation Soft Blocking KPIs:� DL Multislot

How to measure

TCH Call Blocknig (blck_8i)

The feature impact highly depends on the DHR mode usage (determined by SAIC MS penetration, network scenario and OSC-related parameters setting).

Average CS Traffic (trf_202a)Normal TCH Usage Ratio for CS (trf_197a)

How to measure

Average Available PS Territory Size (ava_44)

Average DL TBF per TSL (tbf_38c)

Multislot Soft Blocking (blck_33c)

Thank You..!

37 © Nokia Siemens Networks 2013For internal use

Documents

OSC FEATURE IN NOKIA BSS