01 Rn30084en10gla0 r99 Features

RU10 Features for R99

1 © Nokia Siemens Networks RU10 for Network Planners 2008 / 03.04.2008

RU10 for Network Planners Training2008




RU10 R99 Features

• Mobility features– Soft HO based on Detected Set Reporting– Inter-frequency HO over Iur– Inter-system HO Cancellation– Cell Selection Parameter Set– UTRAN-GAN Interworking

•Performance features– Load based AMR Codec Mode Selection– RRC Re-establishment for Real Time Services– PS UE States: URA_PCH– PS RAB Reconfiguration– Extension of SIB11 (SIB11bis)

• Changes in existing functionality



Mobility features



SHO based on Detected Set Reporting: FunctionalityRAN1266 (ASW)• The feature increases the maximum number of intra-frequency neighbour

cells in CELL_DCH state from 31 to 63 neighbour cells per WCDMA cell.• The total max number of intra-frequency neighbour cells increases further

during soft handover, up to 126 or 189 cells, as the RNC integrates the intra-frequency neighbour cell definitions of the active set cells.

• The feature is based on the 3GPP feature that allows the UE to measure and report any intra-frequency cell (in addition to active and monitored set cells) which is outside the intra-frequency cell list of the UE. This capability removes the limitation on the length of the intra-frequency cell

list (32 cells) since the UE can include any detected intra-frequency cell in the event evaluation and reporting.

• The RNC adds the detected cell into the active set if the detected cell is defined as the intra-frequency neighbour cell of the active set cell.

When the feature is enabled, it is possible to define max 32 additional intra-frequency neighbour cells (new object ADJD) in addition to the max 31 intra-frequency neighbourcells (object ADJS) of the WCDMA cell.

Additional intra-frequency neighbour cell definitions are used only for the identification of the detected cells.

Additional intra-frequency neighbour cell may be located in any UMTS Radio Access Network (UTRAN) of any Public Land Mobile Network (PLMN).

The neighbour cell parameters are defined by attaching specified HOPS parameter sets (RT, NRT, HSDPA and HSPA) to the additional intra-frequency neighbour cell.



SHO based on Detected Set Reporting: FunctionalityRAN1266 (ASW)

RNCUE

Activate DSR

UE measures AS, neighbor list

and other cellsReporting event on other cell

Check other cell against missing

neighbors and ADJDs

Update AS with ADJD cell

Update neighbor list

Missing neighbors can occur in SHO if combined neighbor list is less than all neighbors of all AS cells (as a result of neighbor list combination)



Soft HO Based on Detected Set Reporting: Functionality RAN1266• Handover control includes/excludes detected set cells in/from

the handover decision process according to the value of the parameter FMCS – DSRepBasedSHO :– Handover control includes only active and monitored set cells in the

handover decision process when the value is 0 (DSR is not allowed) or 1 (DSR is enabled but SHO to detected cell is not allowed).

– Handover control includes those detected set cells in the handover decision process (in addition to the active and monitored set cells) which are defined in the ADJS (but are left out from the full combined intra-frequency cell list) and ADJD database objects of the active setcells when the value of the parameter FMCS - DSRepBasedSHO is 2 (DSR based SHO is enabled).



Soft HO Based on Detected Set Reporting: : BenefitRAN1266 (ASW)

Improved call completion

Improved throughput per user and on system level

Improved possibilities for optimisation

Improved call completion

Improved throughput per user and on system level

Improved possibilities for optimisation



Soft HO Based on Detected Set Reporting: : PreconditionsRAN1266 (ASW)

Requires RAN1191 Detected set reporting and MeasurementsRequires RAN1191 Detected set reporting and Measurements



• License requirements

• Activation per cell required• New measurement M1028, new counters as below• No alarms• Updated KPIs on SHO success• New KPIs on amount of detected cell, EcNo and RSCP

Soft HO Based on Detected Set Reporting: Operational aspectsRAN1266

Licence description Licence typeLicence control in

network elementRNC LK

Licence control attributes

Long-term capacity licence (# of BTS)



Soft Handover Based on Detected Set Reporting –Management data 1/3• New parameters related to this feature

– FMCS – DSRepBasedSHO (Detected Set Reporting Based SHO)– ADJD – ADJDChangeOrigin (Change Origin)– ADJD – ADJDId (Identifier of Additional Intra-frequency Adjacency)– ADJD – AdjdCI (Cell Identifier)– ADJD – AdjdCPICHTxPwr (Primary CPICH Power)– ADJD – AdjdDERR (Disable Effect on Reporting Range)– ADJD – AdjdLAC (Location Area Code)– ADJD – AdjdMCC (Mobile Country Code)– ADJD – AdjdMNC (Mobile Network Code)– ADJD – AdjdMNCLength (Mobile Network Code Length)– ADJD – AdjdRAC (Routing Area Code)– ADJD – AdjdRNCId (RNC Identifier)



Soft Handover Based on Detected Set Reporting –Management data 2/3• New parameters related to this feature (cont.):

– ADJD – AdjdScrCode (Primary Scrambling Code)– ADJD – AdjdTxDiv (Tx Diversity Indicator)– ADJD – AdjdHSDPAHopsId (HSDPA HOPS Identifier)– ADJD – AdjdNRTHopsId (NRT HOPS Identifier)– ADJD – AdjdRTWithHSDPAHopsId (HSDPA HOPS Identifier for AMR)– ADJD – AdjdRTHopsId (RT HOPS Identifier)

• Modified parameters related to this feature:– RNC – RncOptionList – RncOptions (RNC Options)



Soft Handover Based on Detected Set Reporting –Management data 3/3• Counters

– Detected set reporting based SHO updates existing counters in:▪ Soft handover measurement (M1007)▪ Intra-system hard handover measurement (M1008)▪ Autodef SHO measurement (1013)▪ Autodef SHO DSR (1028)



Inter Frequency Handover over Iur: FunctionalityRAN1824 (ASW)

SRNC DRNC

NodeB NodeB

D-Cell2f2

CN

S-Cell2f2

S-Cell1f1

•Inter-RNC inter-frequency handover can be carried out over the Iur if the DRNC or CN does not support SRNS relocation

•Inter-frequency handover over the Iur is required when there are isolated cells, e.g. indoor cells, in some carrier under the DRNS or if some carrier has a dedicated RNC

•If the DRNC or CN does not support the SRNS relocation procedure, the SRNC continues as a controlling node (anchoring point) for the RRC connection when the UE moves under the DRNS

•The user plane traffic between the DRNC and CN is transferred via Iur and the SRNC

•If the intra-frequency coverage under the DRNS is not continuous, the inter-RNC inter-frequency handover will be carried out over the Iur

•The DRNC sends information to the SRNC on the inter-frequency neigbour cells (in addition to the intra-frequency neighbour cells) that have been defined for the active set cell(s) controlled by the DRNC

•The SRNC takes into account the inter-RNC inter-frequency neighbour cell information in the inter-frequency measurement and handover decision procedures

•The SRNC has specific BTS and cell level handover control parameters, that are used during anchoring for the active set cells controlled by the DRNC and for the neighbouring cells defined on the DRNC side

•The SRNC and DRNC support compressed mode during the inter-frequency measurements



Inter Frequency Handover over Iur: FunctionalityRAN1824 (ASW) The SRNC and DRNC support the following inter-frequency handover signalling procedures over Iur:• Inter-frequency handover within DRNS when all radio links in the active set

are controlled by the target DRNC• Inter-frequency handover from the SRNS to the DRNS when one (or more)

radio link in the active set is controlled by the target DRNC• Inter-frequency handover from the SRNS to the DRNS when no radio link in

the active set is controlled by the target DRNC• Inter-frequency handover from the DRNS back to the SRNS• Inter-frequency handover between two DRNSs when no radio link in the

active set is controlled by the target DRNC



Inter Frequency Handover over Iur: Benefit RAN1824 (ASW)

This feature enables full connected mode mobility during anchoring with the support for both intra- and inter-frequency handovers over Iur

Relocation support in DRNC and CN is not required anymore (but still recommended)

This feature enables full connected mode mobility during anchoring with the support for both intra- and inter-frequency handovers over Iur

Relocation support in DRNC and CN is not required anymore (but still recommended)




• Activation required• Follow up by measurement M1014• New KPIs on IFHO under DRNC• No alarms

Inter Frequency Handover over Iur : Operational aspectsRAN1824




Long-term capacity licence



ISHO Cancellation: FunctionalityRAN1275 (OSW)

RNCUE

Activate CM and measurements

UE measures GSMbut also Intra-

frequency Reporting event relevant for cancellation: 1A,1C,1E, 6B

UE or RAN triggerstarts ISHO

.. or RAN internalevent allowcancellation

Cancel CM and measurements



ISHO Cancellation: FunctionalityRAN1275 (OSW)• Inter-System measurements may be started in the UE due to

– uplink DCH quality

– UE TX power

– downlink DPCH power

– CPICH RSCP

– CPICH Ec/No)

• The inter-system measurement phase takes a few seconds and during that time the conditions in the WCDMA layer may change => Cancellation

• AS Update can also cancel ISHO

Inter-System measurements may be started in the UE due to the radio coverage and

connection quality (uplink DCH quality, UE TX power, downlink DPCH power, CPICH RSCP

or CPICH Ec/No) reasons .

When the inter-system measurements are completed, the target cell selection takes place.

The inter-system measurement phase takes a few seconds and during that time the

conditions in the WCDMA layer may change.

During the inter-system measurements the UE measures also intra-frequency WCDMA

neighbors.

If the intra-frequency measurements indicate that the conditions have improved in the

WCDMA layer so that defined cancellation thresholds are exceeded, the RNC stops the

handover and compressed mode measurements.

Also, if the UE Internal Measurements or the RL Quality measurements indicate that the radio

conditions have improved, the ongoing inter-system Handover is interrupted or cancelled.

Active set update due to cell addition/replacement during the measurements also causes the

inter-system handover cancellation.

With this feature unnecessary Inter-System Handovers can be cancelled in the UE thus

retaining the call in current WCDMA network.



ISHO Cancellation: FunctionalityRAN1275 (OSW)

• No cancellation once measurement phase is completed

• No cancellation if the UE has had already RNC:MaxNumISHOClPerAS

cancellations in the current active set (1…5,step 1, def. 1)

• Extension of RAS06 feature RAN1726, covering only RSCP



Example signaling flow• Event 1E triggered measurement report received for CPICH EcNo

SRNC -HCSRNC -AC/PSBTSUE

CM Required

NBAP/RNSAP: RL Reconfiguration Commit

RRC: Ph/ Tr Channel Reconfiguration

RRC: Measurement Control (Inter-System Meas)

RRC: Measurement Report (Event 1E for CPICH EcNo)

RRC: Measurement Report (RSSI Meas)

Stop CM

NBAP/RNSAP: RL Reconfiguration procedure or CM Command

RRC: Ph/Tr Channel Reconfiguration (Optional)

NBAP/RNSAP: RL Reconfiguration Prepare

NBAP/RNSAP: RL Reconfiguration Ready

DRNC

RRC: Ph/ Tr Channel Reconfiguration Complete

Load and start CM Ack

Stop CM Ack

Me

a

s

u

r

e me

n

t

p

h

a

s

e

Inter-system measurement cancellation decision

RRC Measurement Control

RRC Measurement Report (Event 1F for CPICH EcNo)



ISHO Cancellation: BenefitRAN1275 (OSW)

Unnecessary WCDMA to GSM/GPRS handovers can be avoided, thus improving end-user service quality .Reduces the additional load in the 2G layer caused by unnecessary Inter-System Handover from the 3G to 2G.Typically about one-fourth of the inter-system handovers can be interrupted by enabling this featureThus the impact of CM on system capacity and coverage will be reducedWithout this feature RAN1726 provides cancellation only for RSCPtrigger

Unnecessary WCDMA to GSM/GPRS handovers can be avoided, thus improving end-user service quality .Reduces the additional load in the 2G layer caused by unnecessary Inter-System Handover from the 3G to 2G.Typically about one-fourth of the inter-system handovers can be interrupted by enabling this featureThus the impact of CM on system capacity and coverage will be reducedWithout this feature RAN1726 provides cancellation only for RSCPtrigger



• No license requirements• Activation per RNC required: ISHOCancellation• By default enabled in FMCG object per trigger reasons

ISHOClcauseXXX• DLDPCHTxPwrClOffset allows to influence cancellation

triggered by DL power• New counters M1010C203-C214 per RT/NRT and trigger reasons• No alarms

ISHO Cancellation: Operational aspectsRAN1275



Cell Selection Parameter Set: FunctionalityRAN1138 (OSW)

System information block 4

UE

High mobility UE parameters

Quality measure hysteresis

Non-HCS_TCRmax

Non-HCS_NCR

Non-HCSmaxHyst

Speed-dependent scaling factor

QHyst1 used with RSCP

QHyst2 used with Ec/N0

Treselection timers for:Cell_FACH state

Cell_PCH/URA_PCH state

Non-HCS_TCRmax > Non-HCS_NCR

Cell reselection for inter-RAT

Inter-RAT scaling factor



Cell Selection Parameter Set: FunctionalityRAN1138 (OSW)• System information block type 4 (SIB4) scheduling on BCCH (so far SIB3

data were used in DCH)– Support different parameters for cell selection and reselection in idle

mode (SIB3) and in connected mode (SIB4)• CPICH RSCP can be used as intra- and inter-system cell reselection

criterion – RSCP trigger is alternative to CPICH Ec/N0

• Separate Treselection values for Cell_FACH state and for Cell_PCH/URA_PCH state and Inter-RAT Scaling Factor for Treselectionparameter are included in SIB4

• Speed Dependent Scaling Factor for Treselection parameter for high mobility UEs is supported

• Separate QHyst1 and QHyst2 values for Cell_FACH state and for Cell_PCH/URA_PCH state are included in SIB4



Cell Selection Parameter Set: BenefitRAN1138 (OSW)

Better end user experience due to optimised cell reselection in connected modeAvoid unnecessary IF and IS reselections

Better end user experience due to optimised cell reselection in connected modeAvoid unnecessary IF and IS reselections



• No license requirements• Activation per WCEL required• No alarms, no counters• New/related parameters as below

Cell Selection Parameter Set: Operational aspectsRAN1138 (OSW) :



Cell Selection Parameter Set - RAN1138 WCEL Parameters

• SintrasearchConn - The parameter defines the threshold for intra-frequency measurements, and for the HCS measurement rules.UE will start the neighbour measurements when CPICH EcNo < qualmin+SintrasearchConn (default: EcNo < -8 dB). The parameter is used for cell selection and re-selection in connected mode.Note: If no threshold is given, MS performs measurements

• SintersearchConn - The parameter defines the threshold for inter-frequency measurements, and for the HCS measurement rules. The parameter should be between the SintrasearchConn and SsearchRATConn, but high enough to manage cell reselection. The parameter is used for cell selection and re-selection in connected mode.Note: If no threshold is given, UE performs measurements

• SsearchHCSConn - The parameter defines the threshold for intra- and interfrequency measurement rules in HCS. Below this limit in the serving cell, the UE initiates measurements of all intra and inter-frequency neighbouring cells of the serving cell. The parameter is used for cell selection and re-selection in connected mode



Cell Selection Parameter SetRAN1138

• Ssearch_RATConn - The parameter defines the RAT-specific threshold for inter-RAT measurement rules. GSM measurements will happen when it is not possible to maintain a call with good quality:

CPICH EcNo < Ssearch_RATConn + Qqualmin (default: EcNo < -14 dB). • The parameter is used for cell selection and re-selection in connected mode.

Note: If no threshold is given, UE performs measurements• SHCS_RATConn - The parameter defines the RAT specific threshold for inter-RAT

measurement rules. Needed only if HCS is used. The parameter is used for cell selection and re-selection in connected mode

• Slimit_SearchRAT - The parameter defines the threshold for skipping inter-RAT measurement rules in HCS. Above this RAT specific threshold in the serving UTRA cell, the UE does not need to perform any inter-RATm measurements. Needed only if HCS is used. The parameter is used for cell selection and re-selection in idle mode

• Qhyst1FACH and Qhyst1PCH - The parameter is used for cell selection and re-selection in PCH. Qhyst1PCH is used for TDD and GSM cells, and for FDD cells when cell selection and re-selection quality measure is set to CPICH RSCP



Cell Selection Parameter SetRAN1138

• Qhyst2FACH and Qhyst2PCH - The parameter is used for FDD cells when cell selection and re-selection quality measure is set to CPICH Ec/No. The parameter is used for cell selection and re-selection in FACH. 2dB hysteresis between WCDMA cells can be used in urban environment to avoid ping-pong. 0dB hysteresis can be used in areas of high mobility like highways

• Treselection - The parameter defines when the UE triggers the reselection of a new cell if the cell reselection criteria are fulfilled during the time interval Treselection. 2s reselection time may avoid too many cell reselections between cells and hence LA/RA updates when crossing LA/RA border. Thus there are less signalling and less call failures at LA/RA border due to LA/RA update. 0s can be used in areas of high mobility like highways

• SIB4_Priority - The priority of System Information Block 4, which is used by the scheduling algorithm in the RNC to give precedence to the SIB.1 = highest priority4 = lowest priority

RNC Parameters• UseOfHCS - Indicates whether the serving cell belongs to a Hierarchical

Cell Structure (HCS), or not



UTRAN-GAN Interworking: FunctionalityRAN1183 (ASW)

• GAN, Generic Access Network also known as UMA (Unlicensed Mobile Access), is a radio network with combined GSM and WLAN access

• UTRAN-GAN Interworking enables handovers for ongoing voice calls between UTRAN and GAN networks

• RNC sets up the measurement event 3a to UEs supporting handover to GAN

• RNC includes neighbouring GAN cell(s) in Inter-RAT Measurement Objects list



UTRAN-GAN Interworking: FunctionalityRAN1183 (ASW)

• GAN-enabled UEs must have dual receivers=> no CM needed

• Two UE modes:– GAN-preferred => 3a is sent immediately after GAN

registration– GAN-not-preferred => 3a is sent only after GAN registration

and quality threshold is passed• From UTRAN perspective GAN-HO procedure is like GSM-

HO• Each WCEL can have only one GAN-specific ADJG neighbor



UTRAN-GAN Interworking : BenefitRAN1183 (ASW)

Service continuity between RAN and WLANPossibility to offload 3GBetter utilisation of WLAN network

Service continuity between RAN and WLANPossibility to offload 3GBetter utilisation of WLAN network




• License activation with ZW7, feature code 1309• RNC and WCEL configuration is required• New counter M1001C643 on RRC release due to GAN-HO• New counters M1010C219-C222 on attempted, successful and

unsuccessful GAN-HO • No alarms, new and related parameters as below

UTRAN-GAN Interworking : Operational aspectsRAN1183(ASW)




Long-term on-off



UTRAN-GAN Interworking: ParametersRAN1183 (ASW)

RNC parametersGANetwARFCN, GANetwNCC, GANetwBCC

to specify the GA network



UTRAN-GAN Interworking: ParametersRAN1183 (ASW)

WCEL parametersADJGId: identification of inter-system adjacency between WCDMA and GAN

neighbour cell.BSIC (AdjgBCC + AdjgNCC): give these ADJG parameters the same values that have

been configured for the GANetwNCC and GANetwBCC RNC parameters in a previous step.

BCCH frequency (AdjgBCCH): give this ADJG parameter the same value that has been configured for the GANetwARFCN RNC parameter in a previous step.

AdjgBandIndicator: indicates whether the BCCH ARFCN of the GAN neighbour cell belongs to the GSM 1900 band.

AdjgCI: cell identifier of the GAN neighbour cell.AdjgLAC: defines Location Area Code of the GAN neighbour cell.AdjgMCC: defines Mobile Country Code of the GAN neighbour cell.AdjgMNC: defines Mobile Network Code of the GAN neighbour cell.AdjgMNCLength: defines whether the Mobile Network Code has 2 or 3 digits in GAN.AdjgSIB: the GAN neighbour cell is not included in System Information Block 11, 11bis,

12 or 18. Allowed parameter value is “No” for the GAN neighbour cell.

In case the WCEL has inter-system adjacency (ADJG) to the GAN cell, but no inter-system adjacency to the GSM cell, the following WCEL parameters are not used and do not need to be configured:

HSDPAFmcgIdentifier

NrtFmcgIdentifier

RtWithHSDPAFmcgIdentifier

RtFmcgIdentifier

In case the inter-system adjacency is a GAN specific ADJG, the following ADJG parameters are not used and do not need to be configured:

AdjgTxPwrMaxRACH

AdjgTxPwrMaxTCH

NrtHopgIdentifier

RtHopgIdentifier



Performance features



Load based AMR Codec Mode Selection: FunctionalityRAN580 (ASW)

Transmitted power in the cellTransmitted power in the cell

Load of DL spreading codesLoad of DL spreading codes

Traffic load at Iub interfaceTraffic load at Iub interface

AMR codec mode selection based on:

TX power of RT trafficTX power of RT traffic

Total TX powerTotal TX power

Non-HSPA TX powerNon-HSPA TX power

{12.2, 7.95, 5.90, 4.75}{12.2, 7.95, 5.90, 4.75}

{5.90, 4.75}{5.90, 4.75}

Choose this AMR codec modeset when there is low load

Choose this AMR codec modeset when there is high load

Where load is measured in these capacity areas:

OR

OR

Choice influences priorities

between AMR and NRT

TX power of RT traffic: NRT traffic is downgraded first

Total TX power: AMR traffic is downgraded first, then NRT and HSPA

Non-HSPA TX power: AMR traffic is downgraded, if R99 NRT load is high



Load based AMR Codec Mode Selection: FunctionalityRAN580

Load

Maximum load

Overload threshold

Target threshold

Underload threshold

If at least one load indicator exceeds itsown overload threshold, then the AMR codec mode set {12.2, 7.95, 5.9, 4.75} is downgraded to the mode set {5.9, 4.75}

If at least one load indicator exceeds itsown overload threshold, then the AMR codec mode set {12.2, 7.95, 5.9, 4.75} is downgraded to the mode set {5.9, 4.75}

If no load indicator exceeds the underloadthreshold, then the AMR codec mode set {5.9, 4.75} is upgraded to the mode set {12.2, 7.95, 5.9, 4.75}

If no load indicator exceeds the underloadthreshold, then the AMR codec mode set {5.9, 4.75} is upgraded to the mode set {12.2, 7.95, 5.9, 4.75}

New calls use low codec modesNew calls use low codec modes

New calls use high codec modesNew calls use high codec modes



Load based AMR Codec Mode Selection: FunctionalitySF Selection for low codec set

Ptx< Target

Yes

NoSC < Target?

Target<Ptx<Overload

Incoming: Select SF128 ifInitial code power>Ptxmax+ AMRSF

Downgrading: Select SF128 ifCurrent code power>Ptxmax+ AMRSF

SF256

Yes

NoSC < Target?

Overload<Ptx

SF256 SF128 SF256

SC:= Load in Spreading code domain

•For the ongoing calls, the AMR codec mode change is applied gradually to avoid sudden signalling peaks caused by the Radio Link Reconfiguration procedures

•The AMR codec mode set {5.90, 4.75} with a 3.4 kbit/s signalling radio bearer bit rate allows the usage of SF256 in downlink instead of SF128

At the radio interface, a somewhat higher energy per bit is required for the AMR 5.9 kbps than for AMR 12.2 kbps due to difference in SF

The AMR codec mode 5.9 on SF256 consumes more transmission powerthan AMR 5.9 on SF128. Therefore, if radio link transmitted power exceeds a predefined threshold and if a spreading code on SF128 is available, SF128 is used.



Downgrade victim selection

• RNC first selects downgrade victim by Allocation Retention Priority (highest ARP value first)

• Second selection is based on allocation time (shortest time is downgraded first)



Load Based AMR Codec Mode Selection: Benefit

With lower codec mode set:• Higher radio capacity (~60%)• More voice users with the same Iub and Iur transport resources (~120%) • Larger spreading code space with SF256

Voice capacity increase with AMR 5.9 kbps

64

95105

210

0

50

100

150

200

250

Air interface [per cell] Iub [1xE1, 2VCCs]

Use

rs

AMR12.2

AMR5.9

+60%

+120%



Load Based AMR Codec Mode Selection : PrerequisitesRAN1183 (ASW)

RAN830 AMR Codes Sets is requiredBoth code sets need to be enabled in WCELRAN830 AMR Codes Sets is requiredBoth code sets need to be enabled in WCEL



Message flow in the case when an AMR codec mode is upgraded to ahigher bitrate

Load based AMR Codec Mode SelectionRAN580




• RNC and WCEL configuration is required• Update of existing KPIs 0014, 0015 on allocated AMR capacity• New counters M1000288-C299 to follow up load situation• New counters M1002C219-C222 on (re-)allocations and failures • No alarms, new and related parameters as below

Load based AMR Codec Mode Selection : Operational aspectsRAN580(ASW)


network elementFIFILE


-



AMROverXYZ : Overload threshold for capacity area XYZAMRTargetXYZ : Target load for capacity area XYZAMRUnderXYZ : Underload threshold for capacity area XYZ

For power these relate the threshold to Ptxtarget

Indicator for downlink radio power load : Selects power quantity AMRSF : Influences the choice between SF128 and 256Usage of Load based AMR codec mode selection : Enabling param.

Load based AMR Codec Mode Selection : Operational aspectsParameters



RRC Re-Establishment for RT Services: FunctionalityRAN1730 (OSW)

Related to:conversational and streaming class CS and PS RABs

T314 Timer

UE

RNC

BTS

No coverage

Radio link failure

UE looses coverage:• BTS sends radio link failure• RNC starts T314 timer• UE goes to Cell_FACH state

UE regains coverage:• UE sends Cell Update• RNC sends Cell Update Confirm,

UE in Cell_DCH• RNC sends RB reconfiguration• UE sends RB reconf. confirm

RRC connection for AMR speech, CS data and PS streaming services is re-established after a temporary loss of RF coverage e.g. in tunnel areas

The feature improves call completion ratio and thus enhances the end user experience

This feature extends the support of RRC connection re-establishment procedure to CS and PS RABs of streaming or conversational classes

If a UE loses the radio connection in Cell_DCH state due to loss of coverage, it moves to Cell_FACH state

When the radio coverage is recovered, the UE sends a cell update message to the RNC with cause radio link failure

The RNC starts the operator configurable timer T314 when it receives the radio link failure message from the BTS(s).

Radio Link Failure is sent 2 seconds (not modifiable!) after WBTS has received 8 out-of-synch indications from UL L1

If the cell update message is received from the UE before T314 has expired, the RNC moves the UE back to Cell_DCH state with cell update confirm message

If T314 expires all RABs and Iu are released by RNC



RRC Re-Establishment for RT Services: BenefitRAN1730 (OSW)

Improved call completion ratio. Allowable time in coverage hole is roughly duplicated (2s -> 4s by default)Improved user experienceWithout this feature the call is dropped immediately after RNC receives RL failure from WBTS

Improved call completion ratio. Allowable time in coverage hole is roughly duplicated (2s -> 4s by default)Improved user experienceWithout this feature the call is dropped immediately after RNC receives RL failure from WBTS



• No license requirements, no activation• New counters M1006C186-C188 on re-establishment success

and failure for RT• No alarms• RNC:T314 is broadcasted on SIB1, default 2s• Deactivate by setting T314 to 0s

RRC Re-Establishment for RT Services: Operational aspectsRAN1730

WCEL:T315 governing the same functionality for NRT is 180 s by default.



PS UE States: URA_PCHRAN833 (OSW)• UE is ordered to transfer to URA_PCH state if number of cell updates received in a

predefined time window is exceeded– Typically for fast moving UEs

• Reduces URA update signaling betweenthe UE and RNC

– On the other hand paging load increases• UTRAN registration areas may be overlapping

– Up to 8 URA identifiers can be broadcasted in one cell

• UE in URA_PCH state has always onevalid URA– The first URA ID in the URA-list of the cell

is the primary URA, which is assigned tothe UE in this cell

– The rest of the URA IDs in the URA-list aresecondary URAs

– UE does not initiate URA update procedure in the cells where the assigned URA is included in the URA-list

– UE is paged in the cells where the assigned URA is in the URA-list



PS UE States - URA_PCH: FunctionalityRAN833

UTRAN connected mode

Cell_FACHCell_DCH

URA_PCH Cell_PCH

RRC states for packet switched services

Idle Mode

Cell_PCH to Cell_DCH transiotion is also new in RU10:

The cell update confirm (CUC) procedure can be used for direct state transition from Cell_PCH to Cell_DCH and for RRC connection re-establishment procedure. In 3GPP Rel5 Cell update message contains a new information (e.g. traffic volume measurement indication), which can be used for immediately allocate the Cell_DCH state resources to the UE.



PS UE States - URA_PCH : BenefitRAN833 (OSW)

For high-speed, low-activity users:•Less signaling, longer battery life than Cell_PCH•Faster service reaction than Idle

For high-speed, low-activity users:•Less signaling, longer battery life than Cell_PCH•Faster service reaction than Idle



PS UE States - URA_PCH : PreconditionsRAN833 (OSW)

• Requires good URA planning, considering e.g. mobility patterns

• Paging load increases

• Requires good URA planning, considering e.g. mobility patterns

• Paging load increases



• Activate URA_PCH feature– No Licencing needed– Value of the management parameter MaxCellReselections set greater

than zero.• Deactivate URA_PCH feature

– MaxCellReselections is set to zero (0), indicating that URA_PCH state is not supported in RNC.

• No alarms• New counters M1001C593-C594 on RAB Active Failures in PCH • New counters in M1006 to count various events in PCH• New counter M802C22 to count average # of users in PCH

PS UE States - URA_PCH: Operational aspectsRAN833



• Parametersation related to Common Channel mobility (Cell_FACH, Cell_PCH, URA_PCH) ▪ Value of the MaxCellReselections represents the maximum number

of cell reselections executed in Cell_FACH and Cell_PCH states within time-window defined by a management parameter CellReselectionObservingTime

• If the number of cell reselections exceeds the value MaxCellReselections, the UE will be interpreted as ‘Fast-moving’ and it is switched to URA_PCH instead of Cell_PCH

• Default values for MaxCellReselections and CellReselectionObservingTime has been chosen by assuming that the average cell-radius in the RNC-area is e.g. 2.5km, and thus the values MaxCellReselections=3 and "CellReselextionObservingTime"=4minute will give 112 km/h as an average speed for the "Fast-moving UE"

• Values of MaxCellReselections and CellReselectionObservingTime need to be fine-tuned if there is a different (average) cell-radius used in the RNC and/or different distribution/level of mobility in the UE-population

• In general, all low-mobility users (at least stationary and pedestrian) should remain in Cell_PCH state to avoid unnecessary increase of the paging load

PS UE States - URA_PCH: Operational aspects RAN833



• Parametersation related to handover control (Cell_DCH state mobility) – FastUEPeriod (Fast UE evaluation period; how many times the active set

cells have changed completely during the specified evaluation period)– FastUETreshold (Fast UE Threshold; If the number of complete active set

changes equals or exceeds the threshold FastUEThreshold, information about ‘fast moving UE’ is given)

– FastUECancel (Fast UE Cancellation; If the number of complete active set changes equals or exceeds the threshold FastUECancel, information about ‘slow moving UE’ is given)

• Value of the MSActivitySupervision (Time supervision of user inactivity; The MSActivitySupervision timer is used in the RRC states CELL_PCH and URA_PCH for supervising the inactivity of NRT RAB(s)

– Both PCH states can be activated /deactivated by setting MSActivitySupervision to non zero/zero, indicating that Cell_PCH/URA_PCH states are used/not used

PS UE States - URA_PCH: Operational aspects RAN833



PS RAB Reconfiguration: FunctionalityASW, RAN930

• Core Network driven feature• Enables reconfiguration of RAB (attributes)• This is required for service differentiation with a single Access Point Name• Related CN features:

– “Service based QoS” in QoS aware GGSN/ISN recognises service by performing IP packet look-ups

– “Peer-to-peer control” in service aware ISN recognises set of peer-to-peer applications (including Skype)

"Service based QoS" in the NSN GGSN/ISN

The feature recognises service by performing IP packet look-ups, and applies operator configurable QoS policy (service => QoS) accordingly by "GGSN initiated PDP context modification procedure" (Rel99 TS 23.060)

"peer-to-peer control" in the NSN ISN

The feature recognises set of peer-to-peer applications (incl. Skype) by various methods, i.e. protocol signatures and pattern recognition. The feature applies operator configurable QoS policy (service => QoS) accordingly by "GGSN initiated PDP context modification procedure" (Rel99 TS 23.060)

Operators wish to use a single APN for all services but still use service differentiation

Currently operators can perform service differentiation by using different APNs for different services (in this case different HLR QoS profiles are defined for each APN)

This requires complex configurations and is difficult from charging point-of-view

•The reconfiguration is triggered by the CN with a RAB Setup message requesting reconfiguration of the existing RAB

•The following RAB parameters can be changed for the interactive and background traffic class RABs:

Traffic class interactive <-> background

Maximum bit rate (UL/DL)

Change of Traffic Handling Priority (THP) of an interactive RAB

Change of Allocation and Retention Priority (ARP)




Parameter changes become effective depending on– UE RRC state– Direction of Parameter change: UL or DL– Transport Channel: HSPA or DCH

If UE is in URA_PCH or CELL_PCH state, RABAssignmentRequest message does not trigger paging procedure for UE – RNC stores the data to be applied in next active phaseIn CELL_FACH state the new parameters are taken into use on next state transition to CELL_DCHIf UE has DCH service, the handling depends on requested parameter change:• THP, ARP and Traffic Class are taken into use immediately• Maximum bitrate increase on next RRM resource allocation



• Furthermore the resources are taken into use immediately if– UE has HSPA service and upgrade/downgrade of maximum bitrate

or other RAB parameters is requested– The UE has a DCH service and the downgrade of the maximum bit

rate and/or the modification of other RAB parameters is requested.• If RAB reconfiguration is executed in RNC, all UTRAN

capacity areas are reconfigured as well:– Air Interface– WBTS Channel Elements– IuB Transport

• If applicable, new SPI and MBR values are sent from the RNC to the NodeB and new DSCP value is taken into use in the RNC.




PS RAB Reconfiguration : BenefitRAN930 (ASW)

RAN supports CN features useful for simplified service differentiation or QoS adaptionAll resources fit to QoS requirements

RAN supports CN features useful for simplified service differentiation or QoS adaptionAll resources fit to QoS requirements



PS RAB Reconfiguration : PreconditionsRAN930 (ASW)

Related CN features are neededRelated CN features are needed



PS RAB Reconfiguration: Operational aspectsASW, RAN930• License requirements

• Activation is required, via enabling parameter NodeBRABReconfigSupport

• Further details TBD• New KPIs on RAB reconfiguration success rate• New counter M1001C197 on attempts• New counters M1003C9,12,20,24-C222 on requests, successes and

failures • No alarms

Licence description Licence typeLicence control in network

elementRNC LK

Licence control attributes Long-term ON/OFF licence



Extension of SIB11 (SIB11bis):FunctionalityRAN1323 (OSW)

Shortcomings of SIB11:

SIB11bis is introduced in 3GPP Release 6

• Information of about 47 neighbouring cells only • Suboptimal reselection decision

Cells Neighbouring cell type

32 Inter-frequency

32 Intra-frequency

32 Inter-system

SIB11bis provides the capacity for defining:

System Information Block type 11bis (SIB11bis) provides extension segments for SIB11 and solves an inconsistency problem in 3GPP TS 25.331, which has prevented the usage of complete neighbouring cell lists for idle mode UEs

System Information Block type 11/11bis: contains measurement control information to be used in the cell. This SIB is read by MSs in idle mode and in CELL_FACH, CELL_PCH and URA_PCH state. It is used also in CELL_DCH state

Complete neighbouring cell lists can be provided to guarantee optimal cell re-selection and end-user QoS

Allows the definition of 32 intra-frequency, 32 inter-frequency and 32 inter-system neighbouring cells for idle mode UEs

All these neighbours were originally intended to be included in SIB11, but in the specifications the physical size of SIB11 data has capacity only for 47 cells

•In demanding environments, the existing size of SIB11 may not be enough because the intra-frequency neighbours are typically given the highest priority and as a result the inter-frequency and inter-system neighbour cell lists may remain incomplete

•When relevant neighbours are missing from the SIB11, the UE cannot make optimal cell selection, which may lower the performance in call success rates

•SIB11bis is a backward compatible solution to correct the problem in SIB11

•Pre-R6 UEs can not read SIB11bis, and their capability is indicated to the RAN

•The RNC may update the missing neighbours to legacy UEs in the Cell_DCH state.



• No license, no activation needed• Use AdjsSIB, AdjiSIB, AdjgSIB parameters to configure what

adjacency should go into SIB11 or SIB11bis• No counters• Alarm 7771 still exists in cases when too many adjacencies are

configured to SIB11

Extension of SIB11 (SIB11bis): Operational aspectsRAN1323



Changes in existing functionality



R99 Capacity Request Queuing and Overload Control

• These functions are now steered by QoSPriorityMappingparameter structure, defining SPI per TC, ARP and THP

• CrHandlingPolicy is not used anymore• The Capacity Request Queue is ordered based on1. SPI of the request2. Arrival time

• The selection of the radio bearers, whose bit rates have to be decreased, is done based on

1. QoS priority value (lowest priority)2. Connection allocation time (longest allocation time)3. Bit rate (highest bit rate)

SPI = Scheduling Priority Indicator 0…15

TC = Traffic Class (Conversational, Streaming, Interactive, Background)

ARP = Allocation and Retention Priority from CN

THP = Traffic Handling Priority from CN



BTS measurement handling in AC

• Since WBTS sends UL and DL load indications 400ms(WBTS) –800ms (NB/RSxxx) there is need to correctly estimate the cell UL and DL load during these intervals until new load indication arrives from WBTS.

• This happens continuously and is sampled every WBTS:SchedulingPeriod

• Once load indication arrives, cell load estimation is recalibrated with new cell load information



Immediate packet scheduling

• If the scheduling queue in RNC is empty, when a new CR arrives, the CR will be scheduled immediately, i.e. without waiting for the end of the scheduling period



WRAB Parameters for BLER target and Planned EbNo

• New WRAB object collects quality parameters for AC and PC and allows their modification– Planned EbNo– BLER target– Initial SIR target– CM quality parameters– Orthogonality



Thank You !

01 Rn30084en10gla0 r99 Features

Documents

Transcript of 01 Rn30084en10gla0 r99 Features