UMT SYS DD 018824 V03.06 en - AMR CS Speech Service Support - UMTS Access Standard

AMR CS speech service support - UMTS Access
Document number: UMT/SYS/DD/018824

Document issue: 03.06 / EN
Document status: Standard
Date: 19/May/2008
External document
Copyright
2007 Alcatel-Lucent, All Rights Reserved

Printed in France
ALCATEL-LUCENT CONFIDENTIAL
The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in
writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the
information only to its employees with a need to know, and shall protect the information from disclosure and
dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted
no rights to use the information contained herein. If you have received this document in error, please notify the
sender and destroy it immediately
without notice. Nortel Networks assumes no responsibility for errors that might appear in t.All other brand and
Alcatel-Lucent confidential
UMT/SYS/DD/018824 03.06 / EN Standard 19/May/2008 Page 2/129

PUBLICATION HISTORY
19/May/2008
Issue 03.06 / EN, Standard
Update after review

05/May/2008
Descoping of 32687 functionality (no iRM table checks at call admission, no
AMR rate control for multi-service calls when PS is mapped to R99 DCH)
Remove support of SRB#5

25/Apr/2008
Update according review comments

04/Apr/2008
Issue 03.03 / EN, Preliminary
Market Information added

16/Feb/2008
Update after review

28/Jan/2008
Creation based on issue 02.05
Feature 34216 added for UA6.0

05/Dec/2007
Update after review

26/Nov/2007
POR update


19/Sep/2007

13/Sep/2007

31/Aug/2007
Updated after review

16/Jul/2007
Issue 02.00 / EN, Draft
Creation based on 01.05 document
Updated for UA06.0 (features #27804, #32647 & #32687)


CONTENTS
1 INTRODUCTION............................................................................................................................7
1.1 OBJECT....................................................................................................................................7
1.2 FRS ........................................................................................................................................7
1.3 SCOPE OF THIS DOCUMENT .......................................................................................................7
1.4 AUDIENCE FOR THIS DOCUMENT ................................................................................................8
1.5 DEFINITIONS & EDITORIAL CONVENTIONS...................................................................................8
2 RELATED DOCUMENTS............................................................................................................10
2.1 APPLICABLE DOCUMENTS........................................................................................................10
2.2 REFERENCE DOCUMENTS........................................................................................................10
3 FUNCTION OVERVIEW..............................................................................................................12
4 BENEFITS....................................................................................................................................16
4.1 CUSTOMER/SERVICE PROVIDER BENEFITS................................................................................16
4.2 END-USER/SUBSCRIBER BENEFITS........................................................................................17
5 FUNCTIONAL DESCRIPTION....................................................................................................18
5.1 PRINCIPLE..............................................................................................................................18
5.1.1 AMR support with Iu UP V1 (features 30229 & 18717 not activated)...........................18
5.1.2 AMR multi-mode support with Iu UP V2 (18717, 30229, 33863)..................................21
5.1.3 Wideband AMR (27803)................................................................................................28
5.1.4 AMR mode change during call (32687) ........................................................................33
5.1.5 AMR support with Iu UP V1 (featurE 34216 activated).................................................40
5.2 INTER SUB-SYSTEM FUNCTIONAL DISTRIBUTION ........................................................................41
5.2.1 RNC...............................................................................................................................41
5.2.2 Node B ..........................................................................................................................41
5.2.3 OMC..............................................................................................................................41
5.3 USE CASES.............................................................................................................................42
5.3.1 AMR support with Iu UP V1 ..........................................................................................42
5.3.2 AMR-NB multi-mode support with Iu UP V2 (18717, 30229)........................................42
5.3.3 Wideband AMR (27803)................................................................................................44
5.3.4 AMR mode change during call (32687) ........................................................................45
5.3.5 34216 AMR IMprovements ........................................................................................46
5.4 RNS INTER-RELEASE COMPATIBILITY USE CASES ....................................................................47
5.4.1 Features 30229, 18717.................................................................................................47
5.4.2 Feature 27803...............................................................................................................48
5.4.3 Feature 32687...............................................................................................................49
5.4.4 Feature 34216...............................................................................................................49
5.5 FEATURE INTERWORKING........................................................................................................50
5.5.1 Dependencies ...............................................................................................................50
5.5.2 Interaction......................................................................................................................51
5.6 PERFORMANCE IMPACTS. ........................................................................................................55

5.6.1 System performances ...................................................................................................55
5.6.2 Dimensioning ................................................................................................................55
5.6.3 Capacity ........................................................................................................................56
5.6.4 Dependability ................................................................................................................56
5.6.5 End User Performances................................................................................................56
5.7 SECURITY...............................................................................................................................56
6 INTERFACES ..............................................................................................................................56
6.1 UMTS INTERFACES ................................................................................................................57
6.1.1 UU interface...................................................................................................................57
6.1.2 IU interface ....................................................................................................................75
6.1.3 IUR interface ..................................................................................................................76
6.1.4 IUB interface ..................................................................................................................77
6.1.5 IUPC Interface (RNC/SAS).............................................................................................78
6.1.6 IUBC Interface (RNC/CBC) ............................................................................................78
6.2 OAM INTERFACES ..................................................................................................................79
6.2.1 3GPP OAM interfaces...................................................................................................79
6.2.2 External ALCATEL-LUCENT OAM interfaces ..............................................................79
6.3 TRANSMISSION NETWORK INTERFACES ....................................................................................79
6.3.1 Physical layer ................................................................................................................79
6.3.2 Ethernet.........................................................................................................................80
6.3.3 ATM...............................................................................................................................80
6.3.4 IP...................................................................................................................................80
7 OAM MODEL DESCRIPTION.....................................................................................................81
7.1 CONFIGURATION MANAGEMENT...............................................................................................81
7.1.1 RAN Managed Objects .................................................................................................81
7.1.2 RAN Customer Parameters ..........................................................................................90
7.1.3 CDL ............................................................................................................................ 106
7.1.4 CDL: New/Modified/removed COMPONENTS.......................................................... 106
7.1.5 Control rules............................................................................................................... 106
7.2 FAULT MANAGEMENT........................................................................................................... 108
7.2.1 RNC CNode, BTS and OAM Alarm Notifications....................................................... 108
7.2.2 RNC INode Alarm Notifications.................................................................................. 108
7.2.3 State Changes ........................................................................................................... 108
7.3 PERFORMANCE MANAGEMENT .............................................................................................. 108
7.3.1 Counters..................................................................................................................... 108
7.3.2 Metrics........................................................................................................................ 119
7.3.3 Traces ........................................................................................................................ 119
7.4 MISCELLANEOUS ................................................................................................................. 121
7.4.1 Static Data.................................................................................................................. 121
7.4.2 Inventory..................................................................................................................... 121
7.4.3 Action ......................................................................................................................... 121
8 OAM PROCEDURES ............................................................................................................... 122
8.1 UPGRADES.......................................................................................................................... 122
8.1.1 OAM platform Upgrade .............................................................................................. 122
8.1.2 RNC & BTS Upgrade ................................................................................................. 122
8.2 INSTALLATION & COMMISSIONING PROCEDURES.................................................................... 126
8.3 MAINTENANCE..................................................................................................................... 126
8.4 OPERATION......................................................................................................................... 126

8.5 EXTENSION ......................................................................................................................... 126
8.6 TECHNICAL ASSISTANCE SUPPORT....................................................................................... 127
8.7 STABILITY DATA ANALYSER .................................................................................................. 127
9 FIELD INTRODUCTION........................................................................................................... 127
9.1 HARDWARE CONSTRAINTS.................................................................................................... 127
9.2 SPARE PART CONSTRAINTS.................................................................................................. 127
9.3 INTER RNS VERSION INTERWORKING ................................................................................... 128
9.3.1 Features 30229, 18717.............................................................................................. 128
9.3.2 Feature 27803............................................................................................................ 128
9.3.3 Feature 32687............................................................................................................ 128
9.4 CORE NETWORK INTERWORKING........................................................................................... 128
9.5 UE INTERWORKING.............................................................................................................. 128
9.6 GERAN INTERWORKING ...................................................................................................... 128
10 TOOLS IMPACTS..................................................................................................................... 129
11 RESTRICTION TABLE..................................................... ERROR! BOOKMARK NOT DEFINED.
12 ABBREVIATIONS AND DEFINITIONS.................................................................................... 130
12.1 ABBREVIATIONS................................................................................................................... 130
12.2 DEFINITIONS........................................................................................................................ 131
12.2.1 ALCATEL-LUCENT specific definitions ..................................................................... 131
12.2.2 AMR specific definitions............................................................................................. 132
12.2.3 Other 3GPP definitions .............................................................................................. 133
13 ANNEX A. ................................................................................................................................. 134


1 INTRODUCTION
1.1 OBJECT
This document describes the AMR speech service capability supported by the Alcatel-
Lucent UTRAN.
1.2 FRS

The UA05.0 applicable FRS(s) are:
FRS #30229 Iu UP SMpSDU V2
FRS #18717 AMR-NB multi-mode support (for Iu UP V2)

The UA05.0.3 applicable FRS(s) are:
FRS #33863 Initialisation of AMR DL Rate from OMC

In UA05.1 applicable FRS(s):
FRS #27803 Adaptive Multi Rate - Wide Band

FRS #32687 AMR mode change during call - evolution
o 32687-1 AMR rate control based on radio criteria
o 32687-2 AMR rate control based on Iub load criteria

FRS #34216 AMR improvements

1.3 SCOPE OF THIS DOCUMENT
The scope of this document is UTRAN. According to 3GPP this includes the following
nodes: Node B, RNC and OMC.
This document applies respectively to:
The UMTS06.0 solution version i.e. UA06.0 and OAM06.0 releases

1.4 AUDIENCE FOR THIS DOCUMENT
This document is provided for the following manufacturer and customer departments:
validation, engineering and installation.

This document is used for Alcatel-Lucent internal purposes as well (e.g. system
validation and engineering).

1.5 DEFINITIONS & EDITORIAL CONVENTIONS
The following definitions are used:
Within this document the following definition convention is used:
o AMR mode It refers to any AMR rate delivered by an AMR codec
with the exclusion of rates related to the silent mode (SID rate and No
Data rate)
o AMR rate It refers to any AMR rate including the silent mode
rates
Iu UP Iu User Plane
SMpSDU Support Mode for predefined SDU size
For other definitions used throughout this document, please refer to section
12.

The following editorial conventions are used:
Cross out (strikethrough): when used in tabular: means not supported or not
used.
Change bar: indicates additions or deletions

1.6 DEFINITIONS AND SPECIFICATION PRINCIPLES
The present document addresses several markets with potentially different behaviours
in those markets. The definition of Global Market and USA Market are:
Global Market: customers other than those part of the following market.
USA Market: customers with UTRAN where Alcatel-Lucent 939X Node B (former
Lucent Flexent Node B) is deployed.

For the purpose of the present document, the following notations apply:
[Global Market] This tagging of a word indicates that the word preceding the tag
"[Global Market]" applies only to the Global Market. This tagging
of a heading indicates that the heading preceding the tag
"[Global Market]" and the section following the heading applies
only to the Global Market.
This tagging shall, in particular, be used under the parameter
name of parameters specific to the Global Market.
[USA Market] This tagging of a word indicates that the word preceding the tag
"[USA Market]" applies only to the USA Market. This tagging of
a heading indicates that the heading preceding the tag "[USA
Market]" and the section following the heading applies only to
the USA Market.
This tagging shall, in particular, be used under the parameter
name of parameters specific to the USA Market.

[Global Market - ] This tagging indicates that the enclosed text following the
"[Global Market - " applies only to the Global Market. Multiple
sequential paragraphs applying only to Global Market are
enclosed separately to enable insertion of USA Market specific
(or common) paragraphs between the Global Market specific
paragraphs.
[USA Market - ] This tagging indicates that the enclosed text following the "[USA
Market - " applies only to the USA Market. Multiple sequential
paragraphs applying only to USA Market are enclosed
separately to enable insertion of Global Market specific (or
common) paragraphs between the USA Market specific
paragraphs.
Text that is not identified via one of the hereabove tags is common to all markets.


2 RELATED DOCUMENTS
2.1 APPLICABLE DOCUMENTS

Ref. # Document Identifier Document Title
[A0] UMT/SYS/DD/018826 Call Admission Control
[A1] UMT/SYS/DD/000111 Alcatel-Lucent RNS V6.0 Compliance to 3GPP-TS25.415- UTRAN Iu
Interface User Plane Protocols

2.2 REFERENCE DOCUMENTS
The.3GPP baseline for UA06.0 is described in the FRS 33817 3GPP baseline &
additional CRs for UA06.

3GPP documents
[R1] TS 25.331 Radio Resource Control (RRC); Protocol Specification
[R2] TS 25.413 UTRAN Iu interface RANAP signalling
[R3] TS 25.423 UTRAN Iur interface RNSAP signalling
[R4] TS 25.433 UTRAN Iub interface NBAP signalling
[R5] TS 32.104 3G Performance Management (PM)
[R6] TS 25.415 UTRAN Iu interface user plane protocols
[R7] TS 26.102 AMR speech codec; Interface to Iu, Uu and Nb
[R8] TS 26.202 AMR wideband speech codec; Interface to Iu, Uu and Nb
[R9] TS 34.108 Common Test Environments for User Equipment (UE); Conformance
Testing
[R10] TR 25.993 Typical examples of RABs and RBs supported by UTRA; R6
[R11] TS 23.153 Out of band transcoder control
[R12] TS 28.062 Inband Tandem Free Operation (TFO) of speech codecs
[R13] TS 26.103 Speech codec list for GSM and UMTS

Alcatel-Lucent documents
[R20] UMT/SYS/DD/0054 UMTS radio mobility
[R21] UMT/SYS/DD/0128 Intelligent RAB mapping (iRM)
[R22] UMT/SYS/DD/0034 PS call management
[R23] UMT/SYS/DD/18470 SRNS Relocation - UE not involved

[R25] UMT/SYS/DD/0086 UTRAN power management
[R26] UMT/SYS/DD/08326 Radio Bearer configuration parameters

Other standard documents
[R30] M3100 Maintenance Telecommunications Management Network: Generic
Network Information Model
[R31] X721 OSI Systems management: Definition of Management Information
[R32] X730 OSI Systems management: Object Management
[R33] X731 OSI Systems management: State management
[R34] X733 OSI Systems management: Alarm reporting
[R35] GR-1929-Core Telcordia Technologies: Reliability and Quality Measurements for
Telecommunications Systems (RQMS Wireless)
[R36] GR-815-Core Telcordia Technologies: Generic Requirements for Network
Security/Network System (NE/NS) Security


3 FUNCTION OVERVIEW

Up to release UA04.2 the bearer service support for AMR was restricted to mono-
mode AMR, i.e. bearer service support for AMR 12.2 and support of silent mode (aka
SCR (VAD/DTX)) with use of version 1 of Iu UP.

The following set of features provides the bearer service support for additional AMR
codecs:
[Global Market]The UA05.0 features 18717 AMR-NB multi-mode support and
30229 Iu UP SMpSDU V2 provide the bearer service support with use of
version 2 of Iu UP for a number of narrowband AMR speech service and the
support of a number of functions to allow core network Transcoder/Tandem
Free mode of Operation (TrFO/TFO) speech calls.

R
b
S
e
t
C
o
n
f

#

B

R
b
S
e
t
C
o
n
f

#

A

12.2 12.2
7.95
5.9
4.75
SID
[No]
SID
[No]
10.2
6.7
5.9
4.75
SID
[No]
5.9
4.75
SID
[No]
4.75
SID
[No]
DL SF 128 (CS speech service only) DL SF 256
Multi-service possible with DL SF 128 Only Mono-service
Only with Version 2 of Iu UP Version 1 or 2 of Iu UP
All AMR-NB configurations are with 3 AMR sub-flows over Iub/Iur and radio interfaces
All RABs
are with
VAD/DTX
Only with Version 2 of Iu UP

[Global Market]The UA05.0.3 feature 33863 Initialisation of AMR DL Rate
from OMC allows the operator to control the max allowed AMR DL rate for
the OMC

[Global Market]The UA05.1 feature 27803 AMR-WB provides the support by
the RAN of the necessary means to provide the CS WB telephony built on the
multi-mode AMR WB speech codec. This consists in providing the required
RAB as well as the means for changing UL and DL Rates. This feature works
only with Iu UP v2.

R
b
S
e
t
o
n
f

#

C

12,65
8,85
6,6
SID
[No]
DL SF 128 (CS speech service only)
Multi-service possible with DL SF 128
All AMR-WB configurations are with 3 AMR sub-flows over Iub/Iur & Radio
interfaces
All RABs
are with
VAD/DTX
Only with Version 2 of Iu UP
R
b
S
e
t
C
o
n
f

#

C

The following set of UA06.0 features provides some optimizations in order to support
more speech calls per cell:

[Global Market]DL AMR mode adaptation during the call (feature 32687)
No AMR Radio Bearer allocation change is performed during the call, only the rate
is controlled.
- This applies only to CS speech AMR calls with any controllable rate(s) (as per
3GPP 25.415 spec definitions)*.
- The RNC may unilaterally decide to change the set of allowed the UL rate(s):
Whenever the Cell -RTWP- becomes highly (respectively lowly)
loaded
- The RNC may unilaterally decide to change the DL rate:
Whenever the Cell -DL Total Transmitted power- becomes highly
(respectively lowly) loaded
Whenever the DL Transmitted power is above is pre-defined max
power threshold during at least an OAM configurable amount of time,
the RNC will request the Core Network to reduce the DL AMR rate in
order to avoid excessive power consumption in the cell by a single
call.
Whenever the DL transmitted power is under a pre-defined min power
threshold during at least an OAM configurable amount of time, the
RNC will no more restrict the upper rates provided that there is no
restriction from Iub resource perspective.
The Max permitted DL Tx power for a individual AMR call depends on
the Cell, the physical channel configuration (AsConf) and the OLS
The assigned DL Target BLER depends on the DCH configuration -
DCH carrying the Class A bits- and the OLS
- The RNC decides on the set of allowed rates based on the Iub resource load
The Iub DS iRM table determines the max allowed rate. If the current
rate excesses the max allowed rate, the RNC will request the Core
Network to prohibit some of the upper DL AMR rates and the UE to
prohibit some of the upper UL AMR rates (TFCS reduction).

The max allowed rate as output of the Iub iRM table is used to
determine the Equivalent Bit Rate (EBR) over Iub instance related to
the added link.
- The RNC may unilaterally decide to restrict the UL and the DL rates of several
individual calls if an Iub instance becomes loaded:
Whenever the Iub resource becomes loaded, the RNC will restrict the
rate of some of the individual AMR call using this Iub and having any
rate above a pre-defined max rate threshold being above GBR.
This typically copes with cases where in some cells there would be
many stationary UEs.
Before re-enabling a previously disabled AMR rate the RNC needs to check
whether this AMR rate is inline with the bandwidth of the currently established
transport bearers.

Note: The load colors of all cells in the UEs active set is taken into account when
selecting the appropriate AMR rate. The most loaded cell defines the load color.
This applies to DL power load, UL cell load and Iub DS DL load. Whenever there
is a change in the active set, the load colors are recalculated.

Rate Control based on allocated RB
between RB MBR and GBR
(indication of the max allowed rate)
Trigger for rate control UL & DL
- AS Iub resource color change

Trigger for rate control in DL:
- Power consumption based
Rate 4

Rate 3

Rate 2

Rate 1
Allocated RB several rates
above SID rate

Rate-4 is the granted Max Bit
Rate, with
MBR Rate-4 < GBR
Non-controllable rates, in order to satisfy
to GBR (case GBR = Rate-2)

- The feature 32687 does not apply to the following particular cases::
The RAB parameters (list of SDU size) correspond to an AMR WB
codec set.
The RAB parameters (list of SDU size) correspond to an AMR mono-
mode codec.
The requested DL GBR equates to the requested DL MBR, i.e. there
is no RNC rate controllable rate.
The UE has a concurrent PS RAB which is mapped onto a R99 DCH
in DL.

[USA Market]The UA06.0 feature 34216 AMR Improvements introduces a method to
select AMR12.2 or AMR5.9 in monorate mode to increase the voice capacity relative
to a AMR12.2 only scenario. The codec selection is done at RAB Assignment and
dependent on
DL power load
UL cell load
Iub DL DS load.
The feature only applies to calls using Iu UP V1. AMR5.9 which is only selected when
there is no simultaneous PS RAB, is supported with SF128 and SF256. SF256 is

selected, if the number of spreading codes in the cell is running short. Otherwise
SF128 is selected, because this configuration requires less Tx power.

The UTRAN nodes being impacted by these features are the RNC, the Node B and
the OMC:

UE

Node B
MSC

Uu

Iub
UTRAN Core Network
IuCs
UMTS NETWORK
OMC

Itf-N Itf-xDRF
Itf-B Itf-R
UTRAN impacted interfaces by AMR CS speech Service
Shaded area: scope of this document
UTRAN Node impacted by AMR CS speech Service
RNC

Iur

Figure: UMTS Network Architecture / scope of the document

The following table indicates if a node is impacted by a given feature
Feature Node B RNC OMC
30229 X X
18717 X* X X
33863 X X**
27803 X* X X
32687 X X X
34216 X X

(*) Only test and capacity impacts
(**) Only from UA05.1

The following table indicates which features are commercially supported by iBTS and
OneBTS:
Feature iBTS OneBTS
AMR12.2 X X
30229 X
18717 X
33863 X
27803 X

32687 X
34216 X

4 BENEFITS

4.1 CUSTOMER/SERVICE PROVIDER BENEFITS
[Global Market]Customer/service provider benefits related to the following features:
30229 Iu UP SMpSDU V2
18717 AMR-NB multi-mode support (with Iu UP V2)
33863 Initialisation of AMR DL Rate from OMC
27803 AMR-WB

benefit loss
Cost ownership (day to day operation, fault management, upgrade,
preventive/curative maintenance....)

Capacity
Dimensioning (Connectivity, storage capacity..)
Engineering (coverage, C/I..) X
Traffic management (load sharing, compliance with recommendations ..)
Robustness (restart/recovery enhancement..)

32687 AMR mode change during the call - Evolution

benefit loss

Capacity X

[USA Market]Customer/service provider benefits related to feature 34216 (AMR
Improvements):
benefit loss

Capacity X


4.2 END-USER/SUBSCRIBER BENEFITS
30229 Iu UP SMpSDU V2
18717 AMR-NB multi-mode support
33863 Initialisation of AMR DL Rate from OMC
27803 AMR-WB

Benefit benefit loss
Voice quality (HO, call handling enhancement ) X
Quality Of Service (call drop, availability..) X
New services X

32687 AMR mode change during the call - Evolution

Voice quality (HO, call handling enhancement )
New services

[USA Market]End-User/Subscriber benefits related to feature 34216 (AMR
Improvements):
Voice quality (HO, call handling enhancement )
New services


5 FUNCTIONAL DESCRIPTION
5.1 PRINCIPLE
5.1.1 AMR SUPPORT WITH IU UP V1 (FEATURES 30229 & 18717
NOT ACTIVATED)
The AMR 12.2 mode with VAD/DTX is supported (AMR 12.2 without VAD/DTX
support has been removed from release UA05.0).

5.1.1.1 DESCRIPTION
5.1.1.1.1 RAB MATCHING (RNC)
The RAB matching function allows the matching based on the requested RAB
parameters with a provisioned user service configuration and to retrieve and/or
compute the parameters necessary to setup or reconfigure the call.

5.1.1.1.1.1 RANAP PARAMETERS CONTROL
The CS Speech service is identified by the triplet (CN domain = CS, Traffic Class =
Conversational, Source Statistics Descriptor = Speech)

The RAB parameters being taken into account as input of the RAB matching algorithm
are: UP Mode Versions (i.e. versions proposed by CN: version 1 and/or version 2),
Maximum Bit Rate (MBR), Guaranteed Bit Rate (GBR), Maximum SDU Size, SDU
format information Parameter (SDU sizes per sub-flow and AMR rate).

The requested RAB parameters are considered as consistent if the following rule is
fulfilled:
Max AMR rate (calculated from Max (Compound SDU size) = Max SDU size) = MBR
GBR > SID rate (calculated from Min (Compound SDU size) > 0)

In case of failure, the RNC rejects the RAB Assignment Request with RANAP cause
Requested Maximum Bit Rate not Available.

5.1.1.1.1.2 RBSETCONF MATCHING
The RNC identifies the RbSetConf, which satisfies to one of the requested compound
SDU sizes corresponding to a rate greater or equal to the requested GBR for case of
the Iu UP V1 protocol.

Case 1: Version 1 of Iu UP is requested by the CN
The RNC selects the RbSetConf, which supports the AMR 12.2 rate provided
that the 12.2 rate is part of the Core Network requested rate.

The RAB Assignment Request is rejected

Case 3: the CN allows both Versions of Iu UP
The RNC behaves as only Version 1 of Iu UP (same behavior as for Case 1
applies)

5.1.1.1.1.3 ASCONF MATCHING
AsConf matching proceeds as usual.

5.1.1.1.1.4 PARAMETERS COMPUTATION
Following successful RbSet and AsConf matching, the actual UL and DL AMR TFS(s)
are derived from the provisioned TFS(s) by removing TF(s) corresponding to non
selected rates.
The UL and DL TFCS(s) are derived from the provisioned TFCS(s) by:
o removing TFC(s) corresponding to non selected AMR rates
o recalculating CTFC(s) as per 25.331
o checking consistency of gain factors (only applicable to UL): in case
computed gain factors have been provisioned and a reference TFC is
missing (i.e. was removed at 1st step) the RAB matching is failed and
the failure is handled as for a AsConf matching failure

5.1.1.1.2 CALL CONTROL (RNC)
The role of the Call Control function is to setup, reconfigure or release the call.

5.1.1.1.2.1 RAB ASSIGNMENT
Only version 1 of Iu UP is allowed within the scope of this feature:
RAB Assignment Request / UP Mode Versions = v1
v2 v2 or v1 v1
Failure RbSetConf matching as
in 5.1.1.1.1.2
RbSetConf matching
as in 5.1.1.1.1.2

If the RAB matching fails due to RbSetConf matching failure, the RAB assignment
procedure is failed with RANAP cause RNC unable to establish all RFC(s).
If the RAB matching fails due to AsConf matching failure, the RAB assignment

5.1.1.1.2.2 [GLOBAL MARKET]RAB RECONFIGURATION
Some CS AMR-NB speech RAB reconfiguration are supported. If AMR-WB is
enabled, the reconfiguration between NB and WB is supported.

Recall of the possible transitions triggered by the Rab CS Modification

Target Configuration

12.2 mono-mode (IuUp
V1)

AMR-NB
(IuUp
V2)

AMR-LR
(IuUp V2)

AMR-WB
(IuUp V2)

12.2 mono-mode (IuUp
V1)

Partial success
(**)
Success
AMR-NB (IuUp V2)

Failure (*)
Partial success
(**)
Success
AMR-LR (IuUp V2)

Success Success Failure (*) Success
Source
Configuration
AMR-WB (IuUp V2)

Success Success Partial success
(**)
Failure
(*)

(*) only modification with change of UL/DL AsConf is supported
(**) multi-service restrictions : AMR-LR is mono-service

5.1.1.1.2.3 RAB RELEASE
Release proceeds as usual.

5.1.1.1.2.4 INCOMING UE INVOLVED RELOCATION
The target RNC performs the RAB matching for all RABs requested to relocate.
The target RNC performs the following as for the call setup (evaluation of the RAB
attributes):
The version of the Iu UP*
The RbSetConf matching, including the AMR rate selection*
The AsConf matching, including the parameters computation
(*) The AMR rates and version of Iu UP may therefore be different before and after
relocation (e.g. if the source RNC is non Alcatel-Lucent).

Relocation failure cases:
If the RbSetConf matching fails for some of the RABs requested to relocate (the RNC
does not attempt partial relocation) or if the AsConf matching failed, the Relocation
Resource Allocation procedure is failed (and thus the relocation) with RANAP cause
Unable to Establish during Relocation.

5.1.1.1.3 HANDLING WITHIN THE DRIFT RNC
The RbSetConf / AsConf matching on drift role allow AMR configurations other than
these supported in serving role, e.g. including other rates. This is to prevent Iur any
inter-working issues when facing RNC from other manufacturer or Alcatel-Lucent RNC
in a future release.
However the two sub-flows based AMR configurations are not supported in drift role.
Also multi-service combinations other than those supported in serving role may not be
supported in drift role. In such cases RL setup or reconfiguration are failed with
RNSAP cause Requested Configuration not Supported.

5.1.1.1.4 IU UP
Iu UP V1 Time Alignment procedure is fully supported.

5.1.2 AMR MULTI-MODE SUPPORT WITH IU UP V2 (18717, 30229,
33863) [GLOBAL MARKET]
These features extend the UTRAN capability to support the following AMR
configurations with the version 2 of Iu User Plane:
AMR (12.2, 7.95, 5.9, 4.75), AMR (10.2, 6.7, 5.9, 4.75) and AMR 12.2 speech
service along with possible PS data services
AMR (5.9, 4.75) and AMR 4.75 standalone speech service: use of DL SF 256
based physical channel
The following principles apply:
As per 3GPP specification, the call setup in version 2 of Iu UP requires the
initialization of all the requested rates.
Mobility: Support of any mobility case as for AMR 12.2
DL rate control:
o The initial max allowed DL rate is set to the max rate supported by the
selected configuration if feature #33863 is not activated otherwise the
initial max allowed DL rate is the min between the max rate supported
by the configuration and the max allowed rate by configuration .
o No rate control is initiated by the RNC during the call
UL rate control:
o No rate control is initiated by the RNC during the call

o Any valid incoming rate control command (originated by the core
network) is forwarded by means of an RRC TFC control command
over the SRB#2.
Note that SRB#5 shall not be enabled in UA06.
5.1.2.1 DESCRIPTION
5.1.2.1.1 RAB MATCHING (RNC)
5.1.2.1.1.1 RANAP PARAMETERS CONTROL
Refer to the section 5.1.1.1.1.1

5.1.2.1.1.2 RBSETCONF MATCHING
The RNC identifies the RbSetConf, which satisfies to the list of requested compound
SDU sizes (N+1 compound SDU) for case of the Iu UP V2 protocol or to one of the
requested compound SDU sizes corresponding to a rate greater or equal to the
requested GBR for case of the Iu UP V1 protocol

Where N+1 = number of AMR rates + SID rate + No_Data rate*
* Optionally provided by the CN.

Same behavior as described in section 5.1.1.1.1.2 / case 1

The RNC establishes the list of RbSetConf candidates based on the following
criteria:
The RbSetConf shall satisfy to the set of N+1 compound SDU sizes (all
requested rates shall be supported)

The RNC will first try with Version 2 of Iu UP (same behavior as for Case 2)
Should the RAB matching with version 2 of Iu UP fail, the RNC will behave as
in case 1

5.1.2.1.1.3 ASCONF MATCHING

5.1.2.1.1.4 PARAMETERS COMPUTATION
Same behavior as this described in section 5.1.1.1.1.4.

5.1.2.1.2 CALL CONTROL (RNC)
The role of the Call Control function is to setup, reconfigure or release the call.


5.1.2.1.2.1 RAB ASSIGNMENT
The determination of the allowed version(s) of Iu UP is based on a set of provisioned
parameters (Cf. section 7.1.2):
If (allowedIuUpVersion == v1 Or isAmrMultiModeAllowed == disabled) {
AllowedIuUpVersionAtSetup = v1
}
Otherwise {
If ((isAmrMultiModeAllowed == completelyEnabled) OR
(isAmrMultiModeAllowed == enabledPerCell &&
FddCell/isAmrMultiModeSetupAllowed == completelyEnabled)) {
AllowedIuUpVersionAtSetup = v2 or v1
}
Otherwise {
AllowedIuUpVersionAtSetup = v1
}
}
AllowedIuUpVersion RAB Assignment Request / UP Mode Versions
v2 v2 or v1 v1
v1 Failure RbSetConf matching as in
5.1.1.1.1.2
RbSetConf matching as
in 5.1.1.1.1.2
v2 or v1 RbSetConf matching as in
5.1.2.1.1.2 / case 2
RbSetConf matching as in
5.1.2.1.1.2 / case 3
RbSetConf matching as
in 5.1.1.1.1.2

If the RAB matching fails due to RbSetConf matching failure, the RAB assignment
If the RAB matching fails due to AsConf matching failure, the RAB assignment

5.1.2.1.2.2 RAB RECONFIGURATION

Some CS AMR-NB speech RAB reconfigurations are supported. If AMR-WB is
enabled, the reconfiguration between NB and WB is supported.

Recall of the possible transitions triggered by the Rab CS Modification


12.2 mono-mode
(IuUp V1)
AMR-NB
(IuUp
AMR-LR
(IuUp V2)
AMR-WB
(IuUp

V2)

V2)

12.2 mono-mode
(IuUp V1)

Partial success
(**)
Success
AMR-NB (IuUp V2)

Failure (*)
Partial success
(**)
Success
AMR-LR (IuUp V2)

Success Success Failure (*) Success
Source
Configuration
AMR-WB (IuUp V2)

(**)
Failure
(*)

(*) only modification with change of UL/DL AsConf is supported
(**) multi-service restrictions: AMR-LR is mono-service

5.1.2.1.2.3 RAB RELEASE
The RAB release proceeds as usual.

5.1.2.1.2.4 INCOMING UE INVOLVED RELOCATION
5.1.2.1.2.4.1 3G to 3G handover

The target RNC performs the RAB matching as described in section 5.1.1.1.2.4. It is
assumed that SRB#5 support is not required in SRNS Relocations.
The received TFC subset IE is included in the UL Transport channel information
common for all transport channels IE at the RB reconfiguration, so that the rate
control information is preserved within the UE.

A rate control is, in addition, initiated by the target RNC.

5.1.2.1.2.4.2 2G to 3G handover

The RNC performs RAB matching identical to the incoming 3G to 3G case (except
that it is mono RAB).


5.1.2.1.2.5 MULTI-SERVICE SUPPORT
Multi-service is supported along with the high rate AMR configuration.
Multi-service is not supported along with low rate AMR configuration :
o If there is any ongoing PS data, any CS speech call for AMR 4.75 or AMR
(5.9, 4.75) is rejected (AsConf failure).
o If there is any ongoing CS speech call with low rate AMR configuration, any
PS data call request is rejected (AsConf failure).

5.1.2.1.3 RATE CONTROL HANDLING (RNC)
5.1.2.1.3.1 HANDLING OF OUTGOING IU RATE CONTROLS
The RNC does not send any Rate Control toward the CN as part of feature 18717,
except in relocation scenarios when the target RNC receives the relocation trigger
(mandatory per 25.415). The indicated maximum rate for the downlink is again the
highest initialised rate. According to the maximum rate for the uplink included in the
Rate Control acknowledgement, the RNC triggers an RRC TFC Control procedure.
If the feature #33863 is enabled the following applies at call setup or after relocation
scenarios, 2G to 3G handover scenario:
The initial maximum DL rate is evaluated as following:
maxFromOam = lowest value of maxDlAmrRateFromOam across all cells of
active set
Note: If no value was provisioned for a cell, or if a cell is controlled by another
RNC, this cell does not contribute, i.e. 12.2 is assumed allowed.
If there is at least one selected rate above or equal to GBR and below or equal to
maxFromOam then the highest rate is selected
Otherwise the lowest selected rate above GBR is selected
The initial maximum DL rate is transmitted to the CN embedded in the Iu UP
initialisation frame.

If the feature #33863 is enabled the following applies for Soft-handover scenarios:
Whenever the active set is updated the applicable maximum DL rate is re-evaluated
the same way as it is evaluated for call setup i.e. if and only if the applicable maximum
DL rate is modified or changed, a rate control toward the Core Network is issued.
Example:
Set of initialised rates: {10.2, 6.7, 5.9, 4.75}, GBR=4.75
Cell A: maxDlAmrRateFromOam=12.2, cell B: maxDlAmrRateFromOam=7.95
Active set update {A} {A, B}: a rate control is sent with maximum rate allowed 6.7
Active set update {A, B} {A}: a rate control is triggered with maximum rate allowed
10.2


5.1.2.1.3.2 HANDLING OF INCOMING IU RATE CONTROLS
Any incoming rate controls (Iu UP FP RC) are accepted if the OAM parameter
isCnInitiatedRateControlAllowed is set to True, the Iu UP is in version 2 and the
frame is correctly formatted, otherwise they are ignored. For case the RNC accepts
the rate control request, the RNC acknowledges it with indication of the current
maximum rate in the downlink (within the scope of this feature this is always the
highest initialised rate).
Then the RNC triggers an RRC TFC Control procedure indicating the new maximum
rate in the uplink. The RNC ignores any attempt to disallow the lowest AMR rate or
SID or NO_DATA.
The RNC does not check on the User Plane that the UE actually complies with the
TFC control. In case the UE continues to use a rate that is no longer allowed, the RNC
continues to handle normally the frames. This may occur e.g. because the TFC
Control was lost over the radio. The assumption is that the originator of the rate
control will repeat if needed.

5.1.2.1.3.3 HANDLING OF RRC TFC CONTROL
The RRC rate control mechanism is based on the Information Element:
- TFC subset
This IE is present in UL Transport channel information common for all
transport channels optional IE of various RRC messages such as RB SETUP,
RB RECONFIGURATION, RB RELEASE and also SRNS RELOCATION
INFORMATION (included in Source RNC To Target RNC Transparent
Container IE used at relocation). TFC subset is mandatory for TFC
CONTROL over SRB#2 (called DPCH/PUSCH TFCS in uplink).
TFC subset represents a subset of the UL TFCS. It allows to restrict the use
of the UL TFCS by the UE and therefore to control the uplink rate.

The TFC Control procedure is performed regardless the current state of rate control,
i.e. the currently allowed rates.
The TFC Control procedure is performed over SRB#2.
The SRB#2 provides a reliable transfer service (RLC-AM).
The RNC selects the format of the TFC subset IE to be used in TFC CONTROL
message as following:
- Non-allowed transport format combination list for single AMR call
- Restricted TrCH information for multi RAB call
In case the TFC Control procedure cannot be performed because of RRC connection
unavailability, the rate control is not memorized but dropped.
In case the RNC receives TFC CONTROL FAILURE (case the TFC CONTROL was
sent over SRB#2 and the UE found that the TFC subset were inconsistent with the
configured TFCS), no action is taken (the message is traceable. Cf. 7.3.3.2.1.1).

5.1.2.1.4 HANDLING WITHIN THE DRIFT RNC
The behaviour and associated restrictions described in 5.1.1.1.3 applies. It is assumed
that support of SRB#5 is not required for softhandover over Iur.

5.1.2.1.5 HANDLING WITHIN THE NODEB
The CEM-alpha capability is aligned with iCEM capabilities for the TFCS size (CEM-
alpha Software modification in order to support Maximum number of TFC per
Physical Channel in DL extension from 64 to 128) one in order to support the new
multi-service configurations with multi-mode AMR.

5.1.2.1.6 IU UP
5.1.2.1.6.1 INITIALISATION OF IU UP BY RNC
The RNC initializes the Iu UP upon the following events:
RAB assignment (setup)
Incoming relocation
RAB assignment (modification) provided that feature 27803 is supported
The version of Iu UP is determined as described in 5.1.2.1.2.
The rates to initialize result from the RAB matching phase (cf. 5.1.2.1.1.)
The RNC allocates the RFCI(s) in the order of compound SDU sizes, starting with
value 0 for the smallest compound SDU size.
The RFCI corresponding to highest rate first (initial rate control) is signaled first in list.

5.1.2.1.6.2 INITIALISATION OF IU UP BY CN
The CN may re-initialize the Iu UP connection in order to solve any RFCI mismatch in
a TrFO scenario.
If the RNC initiated the Iu UP connection in version 1, any incoming initialisation
request is ignored.
If the RNC initiated the Iu UP connection in version 2, any incoming initialization
request is taken into account, provided that the same set of rates are requested,
otherwise a negative acknowledgement is sent.
The first RFCI in the list of RFCIs received in the initialization request determines the
highest permitted UL rate (embedded rate control). The RNC forwards this rate control
by means of an RRC TFC Control procedure.

5.1.2.1.6.3 HANDLING OF TIME ALIGNMENT
Handling of incoming TA: A negative acknowledgement (TS 25.415) is sent upon
reception of any Time Alignment frame.
RNC initiated Time Alignment procedure is supported.

5.1.3 WIDEBAND AMR (27803) [GLOBAL MARKET]
This feature extends the UTRAN capability to support the following AMR-WB
configurations with the version 2 of Iu User Plane:

AMR (12.65, 8,85, 6,6) speech service along with possible PS data services
Same principles apply as for AMR-NB multi-mode (see section 5.1.2)
5.1.3.1.1 CALL SETUP
RAB matching corresponds to Step1 up to Step2.

Step1
The RNC checks the RANAP parameters consistency
Max AMR rate (calculated from Max (Compound SDU size) = Max SDU size) MBR
GBR > SID rate (calculated from Min (Compound SDU size) > 0)
If there is any inconsistency then the RNC rejects the call.
Note: the presence of SDU sizes for NO-DATA rate is not checked (SDU sizes for NO-
DATA rate optionally provided by the MSC)

No modification compared to AMR-NB multi-mode,

AMR-WB RAB may be requested either with 3 Iu sub-flows, the 3
rd
sub-flow being
possibly locked to 0 kbps rate (no AMR-WB class C bits) or with 2 Iu sub-flows. In
both cases only 3 sub-flow is configured over radio/Iub/Iur.

Step2
The RNC identifies the RbSetConf, which satisfies to the list of requested compound
SDU sizes (N+1 compound SDU).
Where N+1 = number of AMR rates + SID rate + No_Data rate*
* Optionally provided by the CN.
The AMR-WB is identified by its rate. It must be > 12.2 kbps and <= 12.65 kbps.
The flag isAmrWbAllowed is checked.
The flags isAmrMultiModeAllowed and isAmrMultiModeSetupAllowed are not used.
The RNC rejects the call

The RNC establishes the list of RbSetConf candidates, which satisfy to the
subset of N+1 SDU sizes above or equal to GBR and which supports MBR.
There should be only one in the list (MBR = GBR and all configurations are
with SID,).

The RNC will first try with Version 2 of Iu UP (same behavior as for Case 2)
Should the RAB matching fail, the RNC would reject the call

Step3

Step4
CAC proceeds as usual

Step5
Initialization:
RFCI allocation (number of RFCI = number of Compound SDU sizes). Allocation
scheme should be from lowest rate to the highest rate (0*, SID, etc) in order to avoid
as much as possible RFCI mismatch for TFO/TrFO operation. RFCI for 0 rate only
initiated if SDU sizes for No-DATA rate were provided.
The mapping table (TFCI / RFCI) is initialised
Iu UP Initialization provides all RFCIs (i.e. all CN requested rates)
The max rate of allocated RB is the first RFCI in the list (embedded Rate Control)

RB Setup
The RNC configures the UE & NodeB on the allocated RB basis

Interaction with multi-service
If there is any PS I/B or PS STR RAB being established, the RAB matching algorithm
(iRM table) for the PS part is played as well. This is already the case in the current
implementation.

5.1.3.1.2 CALL MODIFICATION
Assumptions taken in order to ease / speed up transitions between AMR-WB & AMR-
NB:
The modification may lead to a change in the number of Iu sub-flows
between 2 and 3. The number of sub-flows configured of the radio/Iub/Iur
is not changed and equals 3.
The same set of RAB combinations is supported with Full rate AMR-NB (cf.
feature 18717) and AMR-WB

The following transitions between AMR-NB & AMR-WB are not supported:
AMR-NB with 3 sub-flows and AMR-WB with 2 sub-flows over radio/Iub/Iur.

RAB matching corresponds to Step1 up to Step2.

Step1
The RNC checks the RANAP parameters consistency as Call setup

If there is any inconsistency then the RNC rejects the call.

Step2
Idem step 2 of Call setup.

Step3
AsConf matching proceeds as in section Call setup / step 3 but with the following
difference:

Step4
CAC proceeds as usual

Step5
Idem step 5 of Call establishment but with the following differences:
Previously allocated RFCIs are replaced with the new RFCIs by the IuUP/Init
procedure.
The Iub transport bearer is replaced. For Iur transport there is no modification nor TB
replacement.
Iu CS transport bearer is either kept or replaced as requested by the CN (the
presence of the TLI IE in the RAB Assignment Request triggers the transport bearer
replacement on Iu).

Interaction with multi-service
If there is any PS I/B or PS STR RAB being established, the RAB matching algorithm
(iRM table) for the PS part is played as well. Similar policy applied as for the setup
case.

5.1.3.1.3 SRB#5 MANAGEMENT

SRB#5 is no longer supported in UA06.

5.1.3.1.4 RFCI MANAGEMENT
RFCI allocation
The system shall support RFCI allocation scheme for AMR (12.65, 8.85, 6.6)
+ SID

Solution choice: The RFCI(s) values are allocated in order of increasing SDU
sizes.

RFCI #

(example)
4 AMR-WB 12.65
3 AMR-WB 8.85
2 AMR-WB 6.6
1 AMR-WB SID
0* NO-DATA
(**) If SDUs for NO-DATA rate provided in RANAP RAB Assignment
Request message

Mapping between RFI & TFI and RFCI and TFCI

RFCS

RFCI RF 1 RF 2
RF 3 (if
configured
)
Total
(bit)
Source rate
(kbps)
4** 72 181 0 253 12.65
3** 64 113 0 177 8.85
2** 54 78 0 132
6.6
1* 40 0 0 40 SID
RFCS
0*** 0 0 0 0 NO-DATA
RF RAB sub-flow
RFCI RAB sub-flow Combination Indicator
RFCS RAB sub-flow Combination Set
(*) Always part of RFCS assuming that VAD/DTX is now supported by any UE /
RAN
(**) Assuming that the RFCI are allocated by increasing rates
The allocation scheme should be based according to the most probable rule in order to
avoid any RFCI mismatch solving (CN originated Iu UP Init (RFCI list) procedure)
(***) Optionally part of RFCS

TFCS UL/DL
TFCS (RF#1, RF#2, RF#3, DCCH)=

(TF0,TF0,TF0, TFj) NO-DATA, TFC # (0 + 5j)
(TF1,TF0,TF0, TFj) SID+0+0, TFC # (1 + 5*j)
(TF2,TF1,TF0, TFj) 42+53+0, 6.6 rate TFC # (2 + 5*j)
(TF3,TF2,TF0, TFj) 55+63+0, 8.85 rate TFC # (3 + 5*j)
(TF4,TF3,TF0, TFj) 75+84+0, 12.65 rate TFC # (4+ 5*j)

With j = 0, 1

RFCI TFCI mapping

RFCI TFCI TFI list
Source rate
(kbps)
4 4 or 9
TF4,TF3,TF0,
TF0/TF1
12.65
3 3 or 8
TF3,TF2,TF0,
TF0/TF1
8.85
2 2 or 7
TF2,TF1,TF0,
TF0/TF1
6.6
1 1 or 6
TF1,TF0,TF0,
TF0/TF1
SID
0 0 or 5
TF0,TF0,TF0,
TF0/TF1
NO-DATA

RFCI modification

Case of RFCI mismatch (TrFO/TFO scenario support)
Case of RAB modification

RFCI release
Case of RFCI mismatch (TrFO/TFO scenario support)
Case of RAB modification
Case of RAB release

5.1.3.1.5 RATE CONTROL DURING THE CALL
Idem as AMR-NB multi-mode provided that the feature 33863 is not activated. Feature
33863 cannot be applied on an AMR-WB call (i.e. no outgoing Iu Rate Control)


5.1.4 AMR MODE CHANGE DURING CALL (32687) [GLOBAL
MARKET]
The feature activation flag is the parameter isAmrRateControlDuringTheCallAllowed
Several concurrent criteria are taken into account by the RNC to trigger any AMR rate
control:
o The possible criteria to control the AMR rate are the DL Tx CP, the DL power
load*, the UL cell load* and the Iub DS load**
o DL Tx CP NBAP measurement report events A & B are used
o The AMR rate control only applies with version 2 of Iu UP protocol

(*) Use of these criteria are respectively controllable via the parameters
isAmrRateControlOnDlPowerLoadAllowed, isAmrRateControlOnULCellLoadAllowed

(**) Use of this criterion is controllable via the parameter isAmrRateControlOnIubDsLoadAllowed

5.1.4.1 DESCRIPTION
AMR rate modification during the call may be initiated by the RNC provided that the
feature 32687 is activated.

During the call, there is no AMR RB reconfiguration based on e.g. the cell load (power,
code) or Iu DS load. During the call, the RNC only controls the AMR rate.

During the call, the RNC will control
the DL AMR rate based on the observed amount of DL power consumption
provided that the following condition is fulfilled:
DL Requested MBR rate > DL Requested GBR

the UL/DL AMR rate based on the observed Iub DS load provided that, in
addition of the above condition, the following one is fulfilled:
UL Requested MBR rate > UL Requested GBR

Control of the AMR DL Rate based on DL power consumption criteria

In case of a mono-service call, the RNC continuously control the DL AMR rate
provided that there is any configured AMR rate above GBR.
In case of a multi-service call where the PS data part is carried over DL dedicated
channel(s), no DL AMR Rate Control is performed for power reason.
In case of a multi-service call where the PS data part is carried over HS-DSCH
channel(s), the RNC behaves as for a mono-service speech call case.


5.1.4.1.1 DL AMR RATE CONTROL BASED ON DL TX CP
At establishment of a speech bearer eligible* to rate control, the RNC configures
NBAP dedicated measurement Reporting on the primary cell in order to track the DL
Transmitted Code Power.
Thus, the RNC can detect when the DL transmitted power rises above a given
threshold, which indicates that radio conditions become worst enough to require a rate
decrease.
(*) AMR rate control is allowed if there are any rate controllable AMR modes, i.e. AMR
rates above the Requested Guaranteed Bit Rate. In case of multiple RAB
combinations, eligibility to AMR rate adaptation requires that some additional
conditions are met. Refer to section Multi-service Handling.
1. Dedicated measurements configuration
In order to detect a rate decrease / increase condition, the RNC configures dedicated
measurement reporting with the following characteristics:
- measurement quantity = transmitted code power (Radio Link)
- reporting mode = event triggered
- event = A / B
- threshold1 = RateDecTh
- threshold2 = RateIncTh
- time to trigger = RateDecTTT / RateIncTTT. This time to trigger indicates the time
during which the threshold condition should be fulfilled before the UE sends the
event to the RNC.

2. Dedicated measurements initiation
The dedicated measurement is initiated on the primary cell at call establishment time
or whenever there is a change of the primary cell (the dedicated measurement on the
old primary cell is terminated), provided that the following conditions are met:
There is any DL AMR rate(s), which is/are controllable by the RNC (rate(s) above
GBR)
Speech only user traffic or Speech + PS data over high speed shared channel
The dedicated measurements are managed over both Iub and Iur.

3. NBAP dedicated measurements processing
On reception of an event A / B, and provided that rate decrease / increase is allowed /
possible, the RNC issues an Iu UP Rate Control to the Core Network indicating that
the max current DL rate* is now prohibited / allowed.
(*) In case of TFO/TrFO the DL rate may change. Despite the fact that the
measurement report trigger may relate to an AMR rate below the current max rate,
only the current max allowed rate is prohibited.

Illustration of the process of DL AMR rate control based on DL TxCP


Time
Measured entity (DL TxCP)
maxDlTxPower
RateDecTh
RateIncTh
minDlTxPower
NBAP
Event A
NBAP
Event B
RateDecTTT
RateIncTTT
ReportPeriodicity
t1 t2

The thresholds are determined as following:
maxDlTxPower = maxDlTxPowerPerOls[CurrentOls].maxDlTxPower
RateDecThreshold = pcpichPower + maxDlTxPower dlAmrRateDecreaseTxcpTrigger.thresholdDelta
RateIncThreshold = pcpichPower + maxDlTxPower dlAmrRateIncreaseTxcpTrigger.thresholdDelta

Where
dlAmrRateDecreaseTxcpTrigger.thresholdDelta <= dlAmrRateIncreaseTxcpTrigger.ThresholdDelta

The time to trigger values are determined as following:
RateDecTTT = dlAmrRateDecreaseTxcpTrigger.timeToTrigger
RateIncTTT = dlAmrRateIncreaseTxcpTrigger.timeToTrigger

Actions taken at different instants (tx)
t1: the NodeB informs the RNC that there is a high consumption of DL power. The RNC decides
to prohibit the current highest permitted AMR rate via an Iu UP Rate Control frame provided that
the current highest permitted rate is above GBR.
t2: the NodeB informs the RNC that there is a low consumption of DL power. The RNC decides
to allow a higher AMR rate just after the current one via an Iu UP Rate Control frame provided
that the current rate is below the max rate supported by the allocated RB and allowed by the
reserved downlink power load.
Example with AMR (12.2, 7.95, 5.9, 4.75) with initial max rate at 12.2 kbps:
t1: The RNC issues a DL AMR Rate Control in order to prohibit 12.2 rate (DL rates up to 7.95
are allowed)
t2: The RNC issues a DL AMR Rate Control in order to allow 12.2 rate (DL rates up to 12.2 are
allowed)


5.1.4.1.2 CONTROL OF THE AMR UL/DL RATE BASED ON IUB DS LOAD
CRITERIA
The Iub DS load criteria is taken into account if the parameter
isAmrRateControlDuringTheCallAllowed and isAmrRatecontrolOnIubDsLoadAllowed
are set to True.

A specific iRM table is introduced to determine the max allowed AMR rate based on
the OLS and the Iub DS DL load color of the Active Set. This table is played
After any mobility event, to help determine the new max UL/DL rate*
During stable state, determine possible UL/DL rate change by checking the
Active Set Iub DS DL load color every configurable period
In order to avoid any ping pong effects due to the application of different
criteria, the downlink rate upgrade is not triggered based on Iub DS load
colour change. Any ping-pong effect would due to e.g. downgrade by TxCP
measurement report, then upgrade by table DlIrmTableIubDsLoadConfClass,
then downgrade by TxCP measurement report, etc. Only the trigger of TxCP
measurement report is used to upgrade the rate of an AMR call.

Procedures:
DL Rate control: Iu UP Rate Control frame sent to core network
UL rate control: RRC TFC control message sent to UE

Whenever applicable, the rate is decreased step by step, this means that several Iu
UP rate control / TFC control messages may be successively sent. The Iu UP rate
control / TFC control messages will be issued with a configurable frequency (i.e. 1 /
delayBetweenAmrRateControls).

Multi-service:
The RNC initiated AMR rate control for Iub DS load reason does not apply when
the UE has a simultaneous PS RAB.

Iub DS iRM table:
o It defines the maximum AMR rate based on the OLS and the Iub DS load
o To a given value of the pair (Iub DS color, OLS) corresponds the Operators
provisioned max allowed rate.
o There is only one instance of the table per RNC
o The table applies for both UL & DL.
o The Iub DS load is only calculated for the DL assuming that in most of the cases
the traffic over Iub DS is rather symmetric (CS domain calls are mostly symmetric
services: speech or Video Telephony calls, Symmetric CS streaming) or
asymmetric services with higher rate in the DL

Iub transport Color OLS Max AMR rate
Gold e.g. 12.2
GREEN Silver e.g. 12.2
Bronze e.g. 7.95
Gold e.g. 12.2
YELLOW Silver e.g. 7.95
Bronze e.g. 5.9
Gold e.g. 5.9
RED Silver e.g. 4.75
Bronze e.g. 4.75


Remark: The Max AMR rate as output of the iRM table does not influence the process
of selection of the RB configuration (RbSetConf).

The table is played during the call for rate control purpose:
For stationary UE / Stable AS: the color of the AS Iub* may change because
one Iub instance part of the AS becomes loaded / unloaded
Mobility cases
o Intra RNC inter-frequency HO: the Iub instance color related to the
target cell is different from AS Iub of the source AS cell
o Soft handover: the color of AS Iub* changes due to the addition /
deletion of an Iub instance, which supports the added / deleted radio
link

(*) AS Iub: Iub related to the NodeBs supporting the Active Set Cell

5.1.4.1.3 CONTROL OF THE AMR UL RATE BASED ON UL CELL LOAD
CRITERIA
The UA05.0 UL Cell Load feature introduces the support of the NBAP common
measurement on Received Total Wideband Power (RTWP) and determination of the
UL cell load colors based on it.

A specific UL iRM table is introduced to determine the max allowed AMR rate based
on the OLS and the UL cell load color of the cells of the active set. This table is played
At admission to help determine the max initial UL rate based on the UL cell
load color of the cells of the Active Set
After every primary cell update, to help determine the new max UL rate based
on the UL cell load color of the cells of the Active Set
During stable state, determine possible UL rate change by checking the UL
cell load color of the Active Set every configurable period (Cf. parameter
delayBetweenAmrRateControls)

Procedures:
UL rate control: RRC TFC control message sent to UE

Multi-service:
The RNC initiated AMR rate control based on radio criteria (UL Cell Load) does
not apply

UL cell load iRM table:
o It defines the maximum AMR rate based on the OLS and the UL cell load
o To a given value of the pair (UE AS UL cell color, OLS) corresponds the
Operators provisioned max allowed rate

UL cell load Color OLS Max AMR rate
Gold e.g. 12.2
Bronze e.g. 7.95
Gold e.g. 12.2
Bronze e.g. 5.9
Gold e.g. 5.9
Bronze e.g. 4.75


5.1.4.1.4 CONTROL OF THE AMR DL RATE BASED ON DL POWER LOAD
CRITERIA
A specific DL iRM table is introduced to determine the max allowed AMR rate based
on the OLS and the DL power load color of the cells of the active set. This table is
played per individual call:
After every primary cell update, to help determine the new max DL rate based
on the DL power load color of the cells of the active set
During stable state, determine possible DL rate change by checking the DL
power load color of the Active Set every configurable period (Cf. parameter
delayBetweenAmrRateControls)
In order to avoid any ping pong effects due to the application of different
criteria, the downlink rate upgrade is not triggered based on DL power load
colour change. Any ping-pong effect would due to e.g. downgrade by TxCP
measurement report, then upgrade by table DlIrmTablePowerLoadConfClass,
then downgrade by TxCP measurement report, etc. Only the trigger of TxCP
measurement report is used to upgrade the rate of an AMR call.

Procedures:
DL Rate control: Iu UP Rate Control frame sent to core network

Multi-service:
The RNC initiated AMR rate control based on radio criteria (Total DL Tx Power
load) does not apply if PS RAB(s) mapped on DCH (whereas it applies if PS
RAB(s) mapped on HSDPA)

DL cell power load iRM table:
o It defines the maximum AMR rate based on the OLS and the DL cell power load
o To a given value of the pair (UE AS Total DL Tx Power color, OLS) corresponds
the Operators provisioned max allowed rate.

Total DL Tx Power
load Color
OLS Max AMR rate
Gold e.g. 12.2
Bronze e.g. 7.95
Gold e.g. 12.2
Bronze e.g. 5.9
Gold e.g. 5.9
Bronze e.g. 4.75

5.1.4.1.5 RATE CONTROL HANDLING (RNC)
Rate control Applicability:
DL is rate controllable by the RNC if DL MBR > DL GBR
UL is rate controllable by the RNC if UL MBR > UL GBR

Rate initialization cases:
RAB establishment
Mobility cases involving relocation procedure (idem RAB establishment case)


Rate control cases during call:
Rate control shall be performed in a way to ensure the following behavior:
Rate increase shall only be performed step per step, e.g. for case AMR (12.2,
7.95, 5.9, 4.75) is initialized and current rate is 4.75 then the target rate will be 5.9.
Rate decrease shall only be performed step per step, e.g. for case AMR (12.2,
7.95, 5.9, 4.75) is initialized and current rate is 12.2 then the target rate will be
7.95.

Rate control failure handling:
Case the rate is outside the set of permitted rates:
As per 3GPP TS 25.415 [R6] section 6.5.3.2, if the RNC / Iu UP detects that the
RATE CONTROL frame has not been correctly interpreted or received, the Iu UP
shall retrigger an Iu Rate Control procedure. If after NRC repetitions the rate still
not conforms than the RNC should drop the call .

For other failure cases, refer to TS 25.415 [R6]

5.1.4.1.5.1 RATE CONTROL OVER IU
Only version 2 of Iu UP is applicable

Iu UP version 2

CN RNC UE NodeB
Iu UP/ Rate Control (RFCIs, )
Iu UP/ Rate Control Ack (RFCIs, )
The RNC informs the CN that the DL rate should be
reduced (resp. that it accepts increase of the DL
rate)
If the RNC detects that the RATE CONTROL has not been correctly interpreted or
received (e.g.
the observed rate is outside the set of permitted rates in the reverse direction
of the RATE CONTROL control frame,
or a RATE CONTROL NEGATIVE ACKNOWLEDGEMENT control frame
has been received,
or no RATE CONTROL POSITIVE ACKNOWLEDGEMENT control frame
was received before the supervision timer TRC expires),
the Iu UP shall retrigger a Iu Rate Control procedure. If after N RC repetitions, the
error situation persists, the Iu UP protocol layers (sending and receiving) take the
appropriate local actions.
TRC
Iu UP/ Data frame
May be repeated if the procedure
fails. Up to NRC repetitions allowed

Notes:

In this version of the document, the OAM parameter tInit is used to set both
25.415 T
RC
and T
INIT
and, the OAM parameter nInit is used to set both
25.415 N
RC
and N
INIT
.
The IuUP Rate Control Ack message contains rate control information
relevant for UL operation. If the maximum AMR rate provided by this
message is lower than the currently used AMR rate, then the RNC needs to
rate control the UL by sending a Transport Format Combination Control
message to the UE.

5.1.4.1.6 HANDLING WITHIN THE NODEB
The Node B performs the DL Tx Code Power measurements with events A & B (cf.
3GPP spec 25.433).
There is some capacity limitation (number of simultaneous DL Tx CP measurements
supported). Refer to section 5.6.3 for details.
5.1.5 AMR SUPPORT WITH IU UP V1 (FEATURE 34216 ACTIVATED)
[USA MARKET]
With feature 34216 enabled, the RNC supports the following AMR configuration:
AMR12.2
AMR5.9 with SF128
AMR5.9 with SF256
5.1.5.1 AMR CODEC SELECTION AT CALL SETUP
Feature 34216 is applicable when the MSC offers at least the AMR5.9 and AMR12.2
in the RAB Parameters IE of the RAB Assignment Request or intra-system Relocation
Request of type UE involved in relocation of SRNS requesting Iu UP V1. In this
scenario the RNC checks the current
DL power load color
UL cell load color
Iub DS DL load color
to determine the suitable AMR codec rate.
The initially selected AMR codec rate is not changed during the call when the load
conditions change. However the AMR codec is reconfigured to AMR12.2, when a PS
RAB is established in addition to the voice bearer.
5.1.5.1.1 DL POWER LOAD CRITERIA
The RNC supports an iRM table to determine the maximum allowed AMR rate based
on the OLS and the DL power load color. The table is played at call admission. The
power load from all cells in the active set which are managed by the SRNC is taken
into account. The DL power load color is derived from DL Tx power measurements
provided by the NodeBs.

5.1.5.1.2 UL CELL LOAD CRITERIA
on the OLS and the UL cell load color. The table is played at call admission. The UL
cell load from all cells in the active set which are managed by the SRNC is taken into
account. The UL cell load color is derived from RTWP measurements from the NodeB.
5.1.5.1.3 IUB DS DL LOAD CRITERIA
on the OLS and the Iub DS DL load color. The table is played at call admission. The
Iub DS DL load from all cells in the active set which are managed by the SRNC is
taken into account.
5.1.5.1.4 SPREADING FACTOR SELECTION FOR AMR5.9
The RNC supports an iRM table to determine the spreading factor for AMR5.9 rate
based on the OLS and OVSF code tree load color. The table is played at selection of
AMR5.9. The DL OVSF code load from all cells in the active set which are managed
by the SRNC is taken into account.
5.1.5.2 AMR CODEC RECONFIGURATION FROM AMR5.9 TO AMR12.2
AMR5.9 is not supported in combination with any PS RAB. To avoid that a PS RAB
needs to be rejected when the UE has an active voice call using AMR5.9, the RNC
reconfigures the voice call to AMR12.2 when establishing the PS radio bearers.
To prepare the Iu UP for the reconfiguration the RNC establishes a RFCI also for
AMR12.2 at call setup. Thus the RNC only needs to send an Iu UP rate control frame
to the MGW in order to request a modification of the DL AMR codec rate. No RANAP
interworking is required for this modification. On the interface towards the NodeB(s)
and the UE a synchronized radio link reconfiguration procedure is used.
No AMR codec reconfiguration is triggered when CAC fails for the PS RAB.
5.2 INTER SUB-SYSTEM FUNCTIONAL DISTRIBUTION
5.2.1 RNC
Iu UP handling, RAB matching, call control and rate control functions as described in
section 5.1
5.2.2 NODE B
[Global Market] bearer and measurement support as described in section 5.1
5.2.3 OMC
Support for new parameters, counters and traces. Refer to section 7

5.3 USE CASES

5.3.1 AMR SUPPORT WITH IU UP V1

Case the operator allows only version 1 of Iu UP (allowedIuUpVersion set to V1)
Sub-cases
CN proposes only V1*: nominal case
CN proposes only V2*: failure case
CN proposes V1 and V2*: nominal case

Note (*) UP Mode Versions IE of the RANAP RAB Assignment Request or the Relocation Request
message

5.3.2 AMR-NB MULTI-MODE SUPPORT WITH IU UP V2 (18717,
30229) [GLOBAL MARKET]
Case the operator allows version 1 and 2 of Iu UP (allowedIuUpVersion set to
V1&V2)
Sub-cases
CN proposes only V1*
CN proposes only V2*
CN proposes V1 and V2*

Note (*) UP Mode Versions IE of the RANAP RAB Assignment Request or the Relocation Request
message

Cases:
SINGLE AMR CALL SETUP
Sub-cases:
- All supported AMR RAB(s)
-
PS TO PS+AMR
AMR TO AMR+PS
SINGLE AMR CALL RELEASE
AMR+PS TO AMR
AMR+PS TO PS

AMR+PS, PS RECONFIGURATION
AMR CALL SETUP WITH UP INIT BY CN
In this scenario the CN re-initializes Iu UP after call setup in order to resolve
RFCI mismatch during TrFO establishment. Obviously this cannot occur with
two identical RNC(s).
UPLINK RATE CHANGE
The UE changes the UL rate e.g. because it reached its maximum transmit
power. To do so it needs to switch the rate of the speech encoder and then
select the appropriate TFC on the radio interface.
DOWNLINK RATE CHANGE
The distant UE changed its UL rate in a TFO/TrFO configuration.
RATE CONTROL RECEIVED FROM CN
This case is applicable in a TFO/TrFO configuration:
1. In a UMTS to GSM call the MS requested rate change
2. Or in a UMTS to UMTS call the distant RNC requested rate change

Refer to section 5.1.2.1.3.2 for additional information.

RATE CONTROL SENT TOWARD THE CN
Refer to section 5.1.2.1.3 for the description of the case.

UE INVOLVED RELOCATION
SUCCESSFUL UE INVOLVED RELOCATION, ALCATEL-LUCENT END TO
END
Case the source and target RNS are Alcatel-Lucent with same release &
same configuration.
Variants:
- All supported AMR RABs
SUCCESSFUL UE INVOLVED RELOCATION, IOT
Case the source RNC is from a 3
rd
party vendor.
FAILED UE INVOLVED RELOCATION
Examples:
- The AMR RAB to relocate is not supported
- The AMR RAB to relocate is supported but the multi RAB combination
is not supported

UE NOT INVOLVED RELOCATION
1. SUCCESSFUL UE NOT INVOLVED RELOCATION, ALCATEL-LUCENT TO
ALCATEL-LUCENT
same configuration.

Variants:
- all supported AMR RABs

2. SUCCESSFUL UE NOT INVOLVED RELOCATION, IOT
In this scenario the source RNC is from other vendor or simulated.
3. FAILED UE NOT INVOLVED RELOCATION
Examples:
- The AMR RAB to relocate is not supported
- The AMR RAB to relocate is supported but the multi RAB combination is not
supported

SOFT HANDOVER OVER IUR, ALCATEL-LUCENT TO ALCATEL-LUCENT
Case the serving and drift RNS are Alcatel-Lucent with same release &
same configuration.
Variants:
- All supported AMR RABs

SOFT HANDOVER OVER IUR, OTHER VENDOR TO ALCATEL-LUCENT
In this case the serving RNC is a 3
rd
party vendor and uses an AMR configuration
being not supported by Alcatel-Lucent RNC in serving role, e.g.
- Unsupported rates

RAB MODIFICATION
Example: the CN request a modification of an established AMR RAB from AMR
(12.2, 7.95, 5.9, 4.75) to AMR (12.2)
This case is not supported.

MODIFICATION OF AMR DCH(S) IN DRIFT ROLE
Example: the CN attempts to modification of an established AMR RAB from AMR
(12.2, 7.95, 5.9, 4.75) to AMR (12.2) with a serving RNC supporting this
procedure.
This case is not supported.

5.3.3 WIDEBAND AMR (27803) [GLOBAL MARKET]
Use cases described for AMR-NB multi-mode are applicable taking into account the
specific codec modes of AMR-WB.
Use case introduced by AMR-WB is the RAB modification procedure used to support
any transition between AMR-WB multi-rate codec & AMR-NB multi-rate codec.
The mobility use cases assume that the core network is responsible for Codec change
in case that the target RNC/RAT does not support AMR-WB, there is no specific
management required at originating RNC side.

5.3.4 AMR MODE CHANGE DURING CALL (32687) [GLOBAL
MARKET]
Cases:
AMR CALL SETUP / No ongoing PS session
Variants:
- Version 1 of Iu UP is proposed or not
- Multiple rates are proposed or not

AMR CALL SETUP / Ongoing PS session
Sub-cases:
- Speech service is established and PS session is removed
- Speech service is established and PS session(s) is maintained
- Variants:
With or without HSDPA

SINGLE AMR CALL RELEASE
AMR+PS TO AMR
AMR+PS TO PS
AMR+PS, PS RECONFIGURATION
RATE CONTROL SENT TOWARD THE CN
Criteria:
- Cell power load
- DL Transmitted Code Power
- Iub DS load

TFC CONTROL SENT TOWARD THE UE
Criteria:
- UL Cell load
- Iub DS load

UE INVOLVED RELOCATION
The initial max rate is determined as for AMR call setup.

UE NOT INVOLVED RELOCATION
1. SUCCESSFUL UE NOT INVOLVED RELOCATION, Alcatel-Lucent TO
Alcatel-Lucent

same configuration.
- No rate control assuming that radio resources are let unchanged
and Iur transport load are not taken into account
2. SUCCESSFUL UE NOT INVOLVED RELOCATION, IOT
In this scenario the source RNC is from other vendor or simulated.
- Any possible rate control issued assuming that Iub DS load
criteria may apply

SOFT HANDOVER within RNS
NBAP Dedicated measurement initiation request (Event A & B) upon change
of primary cell

SOFT HANDOVER OVER IUR, ALCATEL-LUCENT TO ALCATEL-LUCENT
Case the serving and drift RNS are Alcatel-Lucent with same release &
same configuration.
- RNSAP Dedicated measurement initiation request (Event A & B)
upon change of primary cell under the drift RNC

SOFT HANDOVER OVER IUR, OTHER VENDOR TO ALCATEL-LUCENT
In this case the serving RNC is a 3
rd
party vendor and may not support
RNSAP Dedicated measurement initiation request (Event A & B)
5.3.5 34216 AMR IMPROVEMENTS [USA MARKET]
Cases:
AMR12.2 selection if the UE has a simultaneous PS RAB
12.2 selection independent of cell load colors

AMR5.9 selection based on
DL power load
UL cell load
Iub DS DL load

Spreading factor selection for AMR5.9

Soft handover with and without Iur

SRNS Relocation type UE involved in Relocation of SRNS

SRNS Relocation type UE not involved in Relocation of SRNS


Reconfiguration 5.9 to 12.2
Iub only
Reconfiguration with Iur involvement
Reconfiguration with Iur involvement towards an other-vendor RNC
Reconfiguration with Iur involvement triggered by an other-vendor RNC

Reconfiguration Failures
NodeB rejects NBAP radio link reconfiguration preparation
NBAP radio link reconfiguration preparation times out in RNC
IuUP Rate Control fails
Radio Bearer Reconfiguration Failure
Radio Bearer Reconfiguration timeout

5.4 RNS INTER-RELEASE COMPATIBILITY USE CASES

5.4.1 FEATURES 30229, 18717 [GLOBAL MARKET]
Once the RNC is upgraded to the new release it is assumed that the features are not
activated before all the controlled NodeB(s) are upgraded.
The feature may be activated prior the upgrade or the features activation on the
neighbouring RNC(s). In this case, since the neighbouring RNS acting as drift will not
support all or part of the new AMR configuration, this may cause inter-RNC soft
handover failure and consequently may result in a call drop whenever the UE moves
into the neighbouring RNS area.
In order to mitigate this issue, the following depicted mechanism allows a partial
activation of the feature. This mechanism is based on the principle that any call setup
with use of the new AMR configuration may be limited to some cells in the centre of
the area covered by the RNS, allowing soft handover in the whole RNS with a rather
low probability of moving out of the RNS.
The activation mechanism is based on the following OAM parameters (cf. section
7.1.2) is provided:
- allowedIuUpVersion (per CS CN instance)
- isAmrMultiModeAllowed (per RNC)
- isAmrMultiModeSetupAllowed (per FddCell)
In a serving role, the feature 18717 is activated as soon as isAmrMultiModeAllowed is
set to completelyEnabled or enabledPerCell and allowedIuUpVersion is set to v2
or v1 or v2 for the current CN CS instance.
If the parameter isAmrMultiModeAllowed is set to enabledPerCell and the parameter
isAmrMultiModeSetupAllowed associated to the primary cell is set to false (assuming
the CN allows v1), the RNC fallbacks to AMR 12.2 configuration with Iu UP V1 at call
setup or at incoming UE involved relocation.
In RNS drift role the feature 18717is implicitly activated after upgrade (i.e. Vn+1). Any
activation parameters is ignored, e.g. isAmrMultiModeAllowed.

The Inter-RNS version compatibility is summarized in the table below:
Neighboring

Feature
activation on
RNS Vn RNS Vn+1
Feature
not
activated
RNS Vn+1
Feature
activated
in all cells
RNS Vn+1
Feature
only
activated
in some
cells
RNC Vn+1
Node Bs
Vn+1 Node
Bs < Vn+1
Other
vendor
RNS
SRNS Vn+1 Partial
support *
Partial
support
Full support Partial
support
Partial
support
Full support
DRNS Vn+1 Full support Full support Full support Full support Full support Full
support

Note (*): The AMR configurations introduced by the feature 18717 are supported by a DRNS Vn except
when the additional DCH for SRB#5 is present.

5.4.2 FEATURE 27803 [GLOBAL MARKET]
Once the RNC is upgraded to the new release it is assumed that the feature is not
activated before all the controlled Node Bs are upgraded.
The feature may be activated before all the neighbouring RNCs are upgraded, or have
the feature activated. In such situations it may happen that a neighbouring RNS does
not support some new AMR WB configuration in drift role, depending on the RB
configuration and depending on the release. This will cause inter RNC soft handover
failure and will eventually lead to call drop when the UE moves into the neighbouring
RNC area.
No mechanism similar to AMR multi mode soft activation (activation per cell, see
5.4.1) is provided to mitigate this issue. The reason is that for AMR WB unlike for AMR
multi mode, there is no possible fallback at call setup.
In drift role the feature cannot be desactivated.

Neighbour
_____________
Feature activation
on:
RNS Vn RNS Vn+1 without the feature (the feature
cannot be desactivated on DRNC)
RNC Vn+1
Node Bs Vn+1
Node Bs < Vn+1
Other
vendor RNS
SRNS Vn+1 Partial Full support Partial support
(2)
Full support
DRNS Vn+1 Full support Full support Full support Full support


(2)
The success of AMR-WB setup or RAB modification depends on (NodeBs < Vn+1)
behavior.

5.4.3 FEATURE 32687 [GLOBAL MARKET]
This feature impacts both the RNC and the Node B. In addition, it impacts the Iub and
the Iur interfaces

It is recommended that a whole RNS (RNC + all NodeB(s)) be upgraded prior the
activation of the feature.

Neighbouring RNS is
RNS Vn RNS Vn+1 but
feature not
activated
RNS not fully
upgraded to
Vn+1 (NodeB(s))
3
rd
party RNS
Feature support
on SRNS Vn+1
Partial support Partial support Partial support Full support

5.4.4 FEATURE 34216 [USA MARKET]
This feature impacts the RNC. In addition it impacts the Iu and Iur interfaces.
It is recommended that all RNCs are upgraded prior to the feature activation.
Neighbouring RNS is
RNS Vn RNS Vn+1 but
feature not
activated
RNS not fully
upgraded to
Vn+1 (NodeB(s))
3
rd
party RNS
Feature support
on SRNS Vn+1
Partial support Partial support Full support Full support

This feature can also be deployed when inter-connected to an ex-Lucent R5.X RNC.
Soft handover between the two RNC is fully supported at Iur.
For the reconfiguration from AMR5.9 to AMR12.2 the following aspects need to be
mentioned:
The ex-Lucent RNC when acting as a SRNC reconfigures the voice bearer
first and adds the PS radio bearer in a second step. So there are two
separate synchronized radio bearer configurations.
The ex-Lucent RNC rejects synchronized radio link reconfigurations for
AMR5.9 to AMR12.2 reconfigurations using a single radio link
reconfiguration when the PS radio bearer is mapped to HS-DSCH. When
mapped to R99 DCH, the same reconfiguration procedure is accepted.


5.5 FEATURE INTERWORKING
5.5.1 DEPENDENCIES
5.5.1.1 FEATURE 30229 [GLOBAL MARKET]
This feature is only usable whenever the RNC is connected to a Circuit Core
supporting the version 2 of Iu UP.

This feature is dependant from the following features:
30229 Iu UP V2
30897 UTRAN functional simplifications

This feature is dependant from UE implementation:
Multi-mode AMR speech coder capable UE
Supported RAB combinations

This feature is dependant from the following features:
30229 Iu UP V2
18717 AMR multi-mode

Same as 18717

The feature 32687 is dependant from feature 18717.
This feature relies on iRM Iub DS color calculation (cf. document [R21])
Differentiation between users based on OLS is only possible if the circuit core is able
to properly set the RANAP ARP-PL based on the user subscription.

5.5.1.6 FEATURE 34216 [USA MARKET]
This feature relies on the load color calculation and the iRM framework for DL Power,
UL Load and Iub DL DS load which are introduced by other features.

This feature relies on the ALCAP bearer handling as introduced with feature 28018
'3GPP compliant Iub: Alcap'.
The RAB matching algorithm for feature 34216 requires that feature 32687 is
deactivated by the attribute RadioAccessService\
isAmrRateControlDuringTheCallAllowed.

5.5.2 INTERACTION
No interaction with other features
5.5.2.2.1 FEATURE 29417 IU-FLEX
There might be several instances of Iu-CS interfaces. At call setup time, the RNC shall
retrieve the OAM parameters from the appropriate instance of CsCoreNetworkAccess
(Cf. section 7.1.2).
5.5.2.2.2 MULTI-SERVICE
Whenever the RNC updates the UL TFCS, typically when adding/releasing a service
or when reconfiguring the PS service, it includes the current TFC subset at the RB
reconfiguration. If the actual value was not included, then the default value would be
used, meaning TFC subset = full UL TFCS. As a result the rate control would be reset
in the UE.
Not all supported AMR RABs are supported in multi-service, e.g. these one related to
AMR 4.75 and AMR (5.9, 4.75).
The exact list of supported multi-service configurations including AMR, with the
corresponding AMR rates, is specified in the document [R26].

The features 28333 Speech + PS Streaming up to 256kbit/s (+PS I/B 8kbit/s) and
30598 CS Speech UL:12.2 DL:12.2+PS I/B up to 384 introduce the support of new
RAB combinations, which requires large TFCS size. When combined with multi-mode
AMR the required TFCS size may exceed the capacity of the system (memory).
Example: the following combinations exceed the capacity of the system.
UL
PS Streaming UL 32 or 128 kbps + PS I/B 8/8 + CS speech (4
modes) (Cf. section 7.1.1.2 UlUserService #39 and #40)
PS I/B UL 384 kbps + CS speech (4 modes)

In multi-service, some static restrictions (configuration) apply on the PS configuration
compared to the PS mono-service configuration:

Some TFCS and/or TFS restriction is applied for the following UL User
Services (Static restriction):
o UlUserService #39: TFCS restriction is applied
The simultaneous transmission of SRB blocks and of PS I/B
blocks is forbidden

o UlUserService #40: Combined TFCS & TFS restriction is applied.
The simultaneous transmission of SRB blocks and of PS I/B
blocks is forbidden
The set of allowed rates is restricted to 0, 64, 128 kbps (32
kbps rate in restriction)

The TFS size of the RB(s) for UL & DL PS I/B 384 (simple & multiplexed) is
restricted to 5 TF (64 kbps rate in restriction):
o DL: UlUserService #22 and #35. Cf. section 7.1.1.2.
o UL: UlUserService #30. Cf. section 7.1.1.2.

On attempt to upsize PS RB in presence of AMR call (iRM scheduling, Always-on, RB
rate adaptation based on traffic): the upsize is not performed if the size of the new DL
TFCS would exceed 128.

5.5.2.2.2.1 FEATURE 33320 NEW RAB AND COMBINATIONS FOR UA06
This feature introduces from UA06.0 other multi-service configurations with AMR. TFS
and/or TFCS reduction may apply to some of these multi-service service
combinations. Details are available in document [R26].

5.5.2.2.3 FEATURE 27083 AAL2 CAC PER VCC
Both features 18717 and 27083 require the modification cacAal2Info part of the OAM
model. The feature 27803 requires that the AAL2 CAC parameters be available per
Iux interfaces (Iub, Iur, Iu-CS), i.e. qaal2EquivalentBitRate,
qaal2EquivalentSSSARSDULength plus a new qaal2MaxBitRate parameters related
to DlRbSetConf and UlRbSetConf.

5.5.2.2.4 POWER CONTROL
The OAM parameters ulRbSetConf / blerTarget and dlRbSetConf / dlBlerQuality are
split per priority level (Cf. section 7.1.2).
The additional DCH for SRB#5 shall not be set as reference transport channel for
Outer Loop Power Control (OLPC). This is enforced by the OMC-R: A check on
parameter ulOuterLoopPowerCtrl / ulRbSetConfId is performed at OMC level in
order to forbid the operator to put the transport channel for support of SRB#5 as
reference for the UL OLPC.

5.5.2.2.5 FEATURE 18880 SRNS RELOCATION UE NOT
INVOLVED
5.5.2.2.5.1 INCOMING UE NOT INVOLVED RELOCATION
RAB matching is performed similarly as for UE involved relocation (Cf. section
5.1.2.1.2.4). Partial relocation is not applicable.

The RAB matching determines the version of the Iu UP (the Iu UP version may be
different before and after the relocation) and AMR rates to initialize (the set of rates
shall remain the same in order to avoid any radio reconfiguration).
The RNC checks that the selected rates match exactly the rates already established
according to the received UL and DL TFCS(s). If not then the RNC fails the incoming
relocation with RANAP cause RNC unable to establish all RFC(s). Note that this may
occur only if Iu UP v1 is allowed (because with v1 allowed two RNC(s) may decide to
initialize two different sets of rates for the same RAB).
If the TFC subset list IE received from the source RNC is not compliant with the
format described in Error! Reference source not found., a post SRNS relocation
SRLR (Cf. document [R23]) is triggered, including a new TFC subset list generated as
described in Error! Reference source not found.. In the meantime any incoming Iu
rate control is discarded and the rate control included in the acknowledgement of the
mandatory Rate Control following relocation (Cf. section 5.1.2.1.3.1) is ignored as
well.
If the feature #33863 is enabled, the applicable maximum DL rate is re-evaluated and
transmitted same as for call setup.

5.5.2.2.5.2 OUTGOING UE NOT INVOLVED RELOCATION
The RNC includes the current TFC subset into the TFC subset IE of the RRC
container.

5.5.2.2.6 FEATURE 33322 PRE-EMPTION PROCESS FOR
DCH AND HSDPA/HSUPA
The AMR-NB RAB is selected prior resource allocation is attempted. In case of any CAC
failure the pre-emption function may be triggered.
This feature is only applicable to AMR-NB. It is only relevant for case the RNC selects
several rates among these requested by the MSC prior application of the feature
33863.
5.5.2.4 FEATURE 27803 WIDEBAND AMR [GLOBAL MARKET]
The interactions described for the feature 18717 are applicable except 30289-1.
The features 33863 and 32687 are not applicable to AMR wideband.

5.5.2.5 FEATURE 27803 CS RAB MODIFICATION [GLOBAL MARKET]
The following CS speech RAB modifications upon reception of a RAB Assignment
Request are supported: AMR-NB (18717 RbSetConf) to AMR-NB (18717
RbSetConf)*, AMR-NB (18717 RbSetConf) to/from AMR-WB (27803 RbSetConf).
(*) Assuming that the target RbSetConf is different as the initial one the rule applies
regardless of the initial versus target version of the Iu UP protocol


AMR-NB
Iu UP V2

AMR-NB
Iu UP V1
AMR-LR
Iu UP V2

AMR-WB
Iu UP V2

AMR-NB
Iu UP V2

Failure Failure Partial success
(**)
Success
AMR-NB
Iu UP V1

Failure Failure Partial success
(**)
Success
AMR-LR
Iu UP V2

Success Success Failure Success

Initial
Configuration
AMR-WB
Iu UP V2

(**)
Failure

(**) some other restrictions apply (Cf. details in section 5.1.3.1.2)

5.5.2.5.1 FEATURE 33322 PRE-EMPTION PROCESS FOR
DCH AND HSDPA/HSUPA
The pre-emption is never triggered after a CAC failure during a CS speech RAB
modification,

This feature is only applicable to AMR-NB.

5.5.2.6.1 FEATURE 27803
The transitions either from AMR-WB to NB or AMR-NB to WB will cause the initiation
or termination of the activation of the feature 32687, respectively.


5.5.2.6.2 FEATURE 29416
The transitions either from Video-telephony to AMR-NB or Video-telephony to AMR-
NB will cause the initiation or termination of the activation of the feature 32687,
respectively.
5.5.2.7.1 FEATURE 30091 - TRANSPORT BEARER
REPLACEMENT ON SRNC
When reconfiguring the radio bearer from AMR5.9 to AMR12.2, the RNC uses a
transport bearer replacement at Iub and Iur as specified in feature 30091 (Transport
Bearer Replacement on SRNC).
5.5.2.7.2 FEATURE 34230 - IRAT ENHANCEMENTS
When the RNC receives a Relocation Request related to 2G-3G handover and the
usage of default configurations is enabled, then the RNC selects monorate AMR12.2
whenever possible to allow usage of default configuration in the Handover To UTRAN
Command. If the usage of default configurations is disabled, the RNC selects the radio
bearer for 2G-3G handovers as defined for other type of relocations.

5.6 PERFORMANCE IMPACTS.
5.6.1 SYSTEM PERFORMANCES

The KPI related to AMR multi-mode shall not be degraded compared to the KPI end-
to-end one-way delay (UE to UE) [CS RAB: CONVERSATIONAL / SPEECH
12.2/12.2] *

Note (*) This KPI quantifies the delay of a speech sample from the UE to MSC and back to UE (i.e. round
trip delay). The measurement is performed with Iu-CS Time Alignment enabled.

5.6.2 DIMENSIONING

System limitations
(per user service)
CEM-Alpha
(Capabilities for
UA05.0)
iCEM xCEM RNC
Max Nb TCH 6 8 8 /
Max TFCS size UL 64 64 64 64
Max TFCS size DL 128 128 256 128


5.6.3 CAPACITY
If the multi-service configuration is supported (aligned to TFCS size), same capacity is
provided with multi-rate AMR and 12.2 kbps.

iCEM: max number of simultaneous measurements is 72
xCEM: there is no specific constraint on the number of simultaneous measurements

5.6.4 DEPENDABILITY
Not applicable

5.6.5 END USER PERFORMANCES

5.7 SECURITY
Not applicable

6 INTERFACES

6.1 UMTS INTERFACES
6.1.1 UU INTERFACE
6.1.1.1 FEATURE30229 [GLOBAL MARKET]
No impact
6.1.1.2.1 RADIO BEARER SETUP

Signalling RB information to setup IE

Information Element/Group
name
Need Multi Type and
reference
Semantics description
RB identity

MD 10.3.4.16
CHOICE RLC info type MP
>RLC info 10.3.4.23
>Same as RB RB identity
10.3.4.16
Identity of RB with exactly the
same RLC info IE values
RB mapping info MP 10.3.4.21

25.331 10.3.4.21 RB mapping info
name
Need Multi Type and
reference
Information for each multiplexing
option
MP 1 to
<maxRBM
uxOptions>

>Downlink RLC logical channel
info
CV-DL-
RLC info

>>Number of downlink RLC
logical channels
MD 1 to
MaxLoCHp
erRLC

Enumerated(
DCH,FACH,
DSCH,DCH+
DSCH
>>>Downlink transport channel
type
MP
, HS-DSCH,
DCH + HS-
DSCH)

>>>DL DCH Transport channel
identity
CV-DL-
DCH
10.3.5.18
>>>Logical channel identity OP Integer(1..15
)
16 is reserved

25.331 10.3.4.23 RLC info
name
Need Multi Type and
reference
Semantics description Values
CHOICE Downlink RLC
mode
OP Indicates if Acknowledged,
Unacknowledged or
Transparent mode RLC shall
be used

>TM RLC
>>Segmentation indication MP Boolean TRUE indicates that
segmentation is performed.

One sided RLC re-
establishment
MP Boolean TRUE indicates that only one
side of the AM RLC entity is
re-established.
FALSE
Alternative E-bit
interpretation
MD Enumerated
(true)
Default: "normal E-bit
interpretation".

UL Transport channel information common for all transport channels
name
Need Multi Type and
reference
Semantics description Values
CHOICE mode OP
>FDD

>>TFC subset MD 10.3.5.22 Default value is the complete
existing set of transport
format combinations

>>UL DCH TFCS MP 10.3.5.20
TFC subset list OP 1 to
<max
TFCs
ub>
The maximum number of
elements in the TFC subset
list is 8.

>CHOICE mode MP
>>FDD (no data)
>TFC subset MD 10.3.5.22

Added or Reconfigured DL TrCH information
name
Need Multi Type and
reference
Semantics
description
Values
Enumerated(DC
H,DSCH
Note 2 DCH Downlink transport channel type MP
,HS-DSCH) Note 1
MP 10.3.5.18 DL Transport channel identity
CV-not
HS-DSCH

CHOICE DL parameters
>Explicit
>>TFS MP 10.3.5.23
DCH quality target OP 10.3.5.10

6.1.1.2.2 TRANSPORT FORMAT COMBINATION CONTROL
(SRB#2)

name
Need Multi Type and
reference
Semantics
description
values
Message Type MP Message Type
UE information elements
RRC transaction identifier MP 10.3.3.36
Integrity check info CH 10.3.3.16
TrCH information elements
CHOICE mode MP
>FDD (no data)
>TDD
DPCH/PUSCH TFCS in uplink MP Transport Format
Combination subset
10.3.5.22

Activation time for TFC subset MD Activation time
10.3.3.1
Default value is
"now"
Default
TFC Control duration OP TFC Control
duration 10.3.6.80

Transport Format Combination subset IE:

name
Need Multi Type and
reference
Semantics
description
Usage
CHOICE Subset representation MP
>Minimum allowed Transport
format combination index
10.3.5.19 TFC not used except
received at
SRNS relocation
>Allowed transport format
combination list
1 to
<maxTFC>
not used except
received at
SRNS relocation
>>Allowed transport format
combination
MP 10.3.5.19 TFC
>Non-allowed transport format
combination list
1 to
<maxTFC>

>>Non-allowed transport format
combination
MP 10.3.5.19 TFC
>Restricted TrCH information 1 to
<maxTrCH>

>>Uplink transport channel type MP Enumerated(
DCH, USCH)
DCH
>>Restricted UL TrCH identity MP 10.3.5.18
>>Allowed TFIs OP 1 to
<maxTF>

>>>Allowed TFI MP Integer(0..31
)

>Full transport format
combination set
(No data)

FAILURE
Signaling over SRB #2 (RLC-AM). When received, the RNC ignores this message.
(SRB#5)
Three bit size encoded value (range 0 up to 7). SRB#5 is no longer supported in UA06

Same as 18717 and additionally
6.1.1.3.2 RB RECONFIGURATION

name
Need Multi Type and
reference
Semantics
description
Version
Message Type MP Message
Type

UE Information elements
RRC transaction identifier MP RRC
transaction
identifier
10.3.3.36


name
Need Multi Type and
reference
Semantics
description
Version
Integrity check info CH Integrity
check info
10.3.3.16

Integrity protection mode info OP Integrity
protection
mode info
10.3.3.19
The UTRAN
should not include
this IE unless it is
performing an
SRNS relocation
or a handover
from GERAN Iu
mode

Ciphering mode info OP Ciphering
mode info
10.3.3.5
The UTRAN
should not include
this IE unless it is
performing either
an SRNS
relocation or a
handover from
GERAN Iu mode
and a change in
ciphering
algorithm

Activation time MD Activation
time 10.3.3.1
Default value is
"now"

Delay restriction flag OP Enumerate
d (TRUE)
This IE is always
set to TRUE and
included if the
activation time is
restricted
according to
subclause 8.6.3.1
REL-6
New U-RNTI OP U-RNTI
10.3.3.47

New C-RNTI OP C-RNTI
10.3.3.8

New DSCH-RNTI OP DSCH-
RNTI
10.3.3.9a
Should not be set
in FDD. If
received The UE
should ignore it

New H-RNTI OP H-RNTI
10.3.3.14a
REL-5
New Primary E-RNTI OP E-RNTI
10.3.3.10a
REL-6
New Secondary E-RNTI OP E-RNTI
10.3.3.10a
REL-6
RRC State Indicator MP RRC State
Indicator
10.3.3.35a

UTRAN DRX cycle length
coefficient
OP UTRAN
DRX cycle
length
coefficient
10.3.3.49

CN information elements
CN Information info OP CN
Information
info 10.3.1.3


name
Need Multi Type and
reference
Semantics
description
Version
UTRAN mobility information
elements

URA identity OP URA
identity
10.3.2.6

CHOICE specification mode MP REL-5
>Complete specification
RB information elements
>>RAB information to
reconfigure list
OP 1 to <
maxRABs
etup >

>>>RAB information to
reconfigure
MP RAB
information
to
reconfigure
10.3.4.11

4>>>>RAB identity MP RAB
Identity
10.3.1.14

4>>>>CN domain identity MP CN domain
identity
10.3.1.1

4>>>>NAS synchronization
indicator
MP NAS
Synchronizat
ion info
10.3.4.12

MP 1to
<maxRB>
Although this IE
is not always
required, need is
MP to align with
ASN.1
>>RB information to
reconfigure list
OP REL-4
>>>RB information to
reconfigure
MP RB
information
to
reconfigure
10.3.4.18

4>>>> RB identity MP RB identity
10.3.4.16

4>>>> PDCP info OP PDCP info
10.3.4.2

4>>>> PDCP SN info OP PDCP SN
info
10.3.4.3
PDCP sequence
number info from
the network.
Present only in
case of lossless
SRNS relocation.

4>>>> RLC info OP RLC info
10.3.4.23

5>>>>>CHOICE Uplink RLC
mode
OP Indicates if
Acknowledged,
Unacknowledged
or Transparent
mode RLC shall
be used.

6>>>>>>AM RLC

name
Need Multi Type and
reference
Semantics
description
Version
6>>>>>>UM RLC
6>>>>>>TM RLC
7>>>>>>>Transmission RLC
discard
OP Transmissio
n RLC
discard
10.3.4.25

7>>>>>>>Segmentation
indication
MP Boolean TRUE indicates
that segmentation
is performed.

5>>>>>CHOICE Downlink RLC
mode
OP Indicates if
Acknowledged,
Unacknowledged
or Transparent
mode RLC shall
be used

6>>>>>>AM RLC
6>>>>>>UM RLC
6>>>>>>TM RLC
7>>>>>>>Segmentation
indication
that segmentation
is performed.

5>>>>>One sided RLC re-
establishment
that only one side
of the AM RLC
entity is re-
established.
REL-5
5>>>>>Alternative E-bit
interpretation
CV-Not-
SIB16md
Enumerated
(true)
Default: "normal
E-bit
interpretation".
REL-6
4>>>> RB mapping info OP RB mapping
info
10.3.4.21

5>>>>>Information for each
multiplexing option
MP 1 to
<maxRBM
uxOptions>

6>>>>>>RLC logical channel
mapping indicator
CV-UL-
RLCLogica
lChannels

If "Number
of uplink
RLC
logical
channels"
in IE "RB
mapping
info" is 2,
then this IE
is
mandatory
present.
Otherwise
this IE is
not
needed.
Boolean TRUE indicates
that the first
logical channel
shall be used for
data PDUs and
the second logical
channel shall be
used for control
PDUs.
FALSE indicates
that control and
data PDUs can be
sent on either of
the two logical
channels.
This parameter is
not used in this
release and shall
be set to TRUE.

6>>>>>>Number of uplink RLC
logical channels
CV-UL-
RLC info
1 to
MaxLoCHp
erRLC
1 or 2 logical
channels per RLC
entity or radio
bearer
RLC [16]

7>>>>>>>CHOICE Uplink
transport channel type
REL-6

name
Need Multi Type and
reference
Semantics
description
Version
8>>>>>>>>DCH, RACH, USCH REL-6
8>>>>>>>>>Uplink transport
channel type
MP Enumerated(
DCH,RACH,
USCH
USCH is TDD only
9>>>>>>>>>ULTransport
channel identity
CV-UL-
DCH/USC
H
Transport
channel
identity
10.3.5.18
This is the ID of a
DCH or USCH
(TDD only) that
this RB could be
mapped onto.

9>>>>>>>>>Logical channel
identity
OP Integer(1..15
)
This parameter is
used to distinguish
logical channels
multiplexed by
MAC on a
transport channel.

9>>>>>>>>>CHOICE RLC size
list
MP The RLC sizes
that are allowed
for this logical
channel.

10>>>>>>>>>>All Null All RLC sizes
listed in the
Transport Format
Set. 10.3.5.23

10>>>>>>>>>>Configured Null The RLC sizes
configured for this
logical channel in
the Transport
Format Set.
10.3.5.23 if
present in this
message or in the
previously stored
configuration
otherwise

10>>>>>>>>>>Explicit List 1 to
<maxTF>
Lists the RLC
sizes that are valid
for the logical
channel.

11>>>>>>>>>>>RLC size index MP Integer(1..m
axTF)
The integer
number is a
reference to the
RLC size which
arrived at that
position in the
Transport Format
Set 10.3.5.23

8>>>>>>>>E-DCH Note 4 REL-6
7>>>>>>>MAC logical channel
priority
MP Integer(1..8) This is priority
between a user's
different RBs (or
logical channels).
[15]

6>>>>>>Downlink RLC logical
channel info
CV-DL-
RLC info

6>>>>>>>Number of downlink
RLC logical channels
MD 1 to
MaxLoCHp
erRLC
1 or 2 logical
channels per RLC
entity or radio
bearer
RLC [16]
Default value is
that parameter
values for DL are


name
Need Multi Type and
reference
Semantics
description
Version
exactly the same
as for
corresponding UL
logical channel. In
case two
multiplexing
options are
specified for the
UL, the first
options shall be
used as default for
the DL. As
regards to the IE
"Channel type",
rule is specified in
8.6.4.8.
Enumerated(
DCH,FACH,
DSCH,DCH+
DSCH
Note 3 8>>>>>>>>Downlink transport
channel type
MP
, HS-DSCH,
DCH + HS-
DSCH)
Note 4 REL-5
8>>>>>>>>DL DCH Transport
channel identity
CV-DL-
DCH
Transport
channel
identity
10.3.5.18

8>>>>>>>>DL DSCH Transport
channel identity
CV-DL-
DSCH
Transport
channel
identity
10.3.5.18

8>>>>>>>>DL HS-DSCH MAC-
d flow identity
CV-DL-HS-
DSCH
MAC-d flow
identity
10.3.5.7c
REL-5
8>>>>>>>>Logical channel
identity
OP Integer(1..15
)
16 is reserved
4>>>> RB stop/continue OP Enumerated(
stop,
continue)

>>RB information to be
affected list
OP 1 to
<maxRB>

>>>RB information to be
affected
MP RB
information
to be
affected
10.3.4.17

>>RB with PDCP context
relocation info list
OP 1 to
<maxRBal
lRABs>
This IE is needed
for each RB
having PDCP and
performing PDCP
context relocation
REL-5
>>>PDCP context relocation
info
MP PDCP
context
relocation
info
10.3.4.1a
REL-5
PDCP ROHC target mode OP PDCP
ROHC
target mode
REL-5

name
Need Multi Type and
reference
Semantics
description
Version
10.3.4.2a
TrCH Information Elements
Uplink transport channels
>>UL Transport channel
information common for all
transport channels
OP UL
Transport
channel
information
common for
all
transport
channels
10.3.5.24

3>>>PRACH TFCS OP Transport
format
combination
set 10.3.5.20
This IE should not
be included in this
version of the
protocol.

3>>>CHOICE mode OP
4>>>>FDD
5>>>>>TFC subset MD Transport
Format
Combination
Subset
10.3.5.22

See table
below
Default value is
the complete
existing set of
transport format
combinations

5>>>>>UL DCH TFCS MP Transport
format
combination
set 10.3.5.20

See table
below

4>>>>TDD
3>>>TFC subset list OP 1 to
<maxTFCs
ub>
The maximum
number of
elements in the
TFC subset list is
8.
REL-4
4>>>>CHOICE mode MP REL-4
5>>>>>FDD (no data) REL-4
5>>>>>TDD REL-4
3>>>>>TFC subset MD Transport
Format
Combination
Subset
10.3.5.22

See table
below
Default value is
the complete
existing set of
transport format
combinations
REL-4
>>Deleted TrCH information
list
OP

1 to
<maxTrC
H>

>>>Deleted UL TrCH
information
MP Deleted UL
TrCH
information
10.3.5.5

>>Added or Reconfigured
TrCH
OP

1 to
<maxTrC


name
Need Multi Type and
reference
Semantics
description
Version
information list H>
>>>Added or Reconfigured UL
TrCH information
MP Added or
Reconfigure
d UL TrCH
information
10.3.5.2

4>>>>Uplink transport channel
type
MP Enumerated(
DCH,USCH
USCH is TDD only
,E-DCH) Note 1 REL-6
MP Transport
channel
identity
10.3.5.18
4>>>>UL Transport channel
identity
CV-NotE-
DCH
REL-6
4>>>>CHOICE UL parameters REL-6
5>>>>>DCH,USCH REL-6
6>>>>>>TFS MP Transport
Format Set
10.3.5.23

See table
below

5>>>>>E-DCH REL-6
6>>>>>>E-DCH Transmission
Time Interval
MP Integer(2,10) Unit is ms. REL-6
6>>>>>>HARQ info for E-DCH OP 10.3.5.7d REL-6
6>>>>>>Added or reconfigured
E-DCH MAC-d flow
OP 10.3.5.1b REL-6
Downlink transport channels
>>DL Transport channel
information common for all
transport channels
OP DL
Transport
channel
information
common for
all
transport
channels
10.3.5.6

3>>>SCCPCH TFCS OP Transport
Format
Combination
Set
10.3.5.20
This IE should not
be included in this
version of the
protocol.

MP Although this IE is
not always
required, need is
MP to align with
ASN.1
3>>>CHOICE mode
OP REL-4
4>>>>FDD
5>>>>>CHOICE DL parameters OP
6>>>>>>Explicit

name
Need Multi Type and
reference
Semantics
description
Version
MP Transport
Format
Combination
Set
10.3.5.20

See table
below
Although this IE is
not always
required, need is
MP to align with
ASN.1
7>>>>>>>DL DCH TFCS
OP REL-4
6>>>>>>SameAsUL (no data)
>TDD
>>Deleted TrCH information
list
OP

1 to
<maxTrC
H>

>>>Deleted DL TrCH
information
MP Deleted DL
TrCH
information
10.3.5.4

>>Added or Reconfigured
TrCH
information list
OP

1 to
<maxTrC
H>

>>>Added or Reconfigured
DL TrCH information
MP Added or
Reconfigure
d DL TrCH
information
10.3.5.1

Enumerated(
DCH,DSCH
Note 2 4>>>>Downlink transport
channel type
MP
,HS-DSCH) Note 1 REL-5
MP Transport
channel
identity
10.3.5.18
4>>>>DL Transport channel
identity
CV-not
HS-DSCH
REL-5
4>>>>CHOICE DL parameters
5>>>>>Explicit
6>>>>>>TFS MP Transport
Format Set
10.3.5.23

5>>>>>SameAsUL
6>>>>>>Uplink transport
channel type
MP Enumerated(
DCH,USCH)
USCH is TDD
only

6>>>>>>UL TrCH identity MP Transport
channel
identity
10.3.5.18
Same TFS applies
as specified for
indicated UL TrCH

5>>>>>HS-DSCH Note 1 REL-5
4>>>>DCH quality target OP Quality
target
10.3.5.10

Real(-6.3
..0 by step of
0.1)

>Preconfiguration REL-5
>>CHOICE Preconfiguration
mode
MP This value only
applies in case the
message is sent


name
Need Multi Type and
reference
Semantics
description
Version
through GERAN
Iu mode
>>>Predefined configuration
identity
MP Predefined
configuratio
n identity
10.3.4.5

>>>Default configuration
>>>>Default configuration
mode
MP Enumerated
(FDD, TDD)
Indicates whether
the FDD or TDD
version of the
default
configuration
shall be used

>>>>Default configuration
identity
MP Default
configuratio
n identity
10.3.4.0

PhyCH information elements
Frequency info OP Frequency
info
10.3.6.36

Uplink radio resources
Maximum allowed UL TX
power
MD Maximum
allowed UL
TX power
10.3.6.39

Integer(-
50..33)
Default value is
the existing
maximum UL TX
power

Uplink DPCH info OP Uplink
DPCH info
10.3.6.88

E-DCH Info OP E-DCH Info
10.3.6.97
REL-6
Downlink radio resources
Downlink HS-PDSCH
Information
OP Downlink
HS-PDSCH
Information
10.3.6.23a
REL-5
Downlink information common
for all radio links
OP Downlink
information
common for
all radio
links
10.3.6.24

MP

1 to
<maxRL>
Although this IE
is not always
required, need is
MP to align with
ASN.1
Downlink information per radio
link list
OP REL-4
>Downlink information for each
radio link
MP Downlink
information
for each
radio link
10.3.6.27


name
Need Multi Type and
reference
Semantics
description
Version
MBMS PL Service Restriction
Information
OP Enumerated
(TRUE)
Absence means
that on the
MBMS Preferred
Layer (PL) no
restrictions apply
concerning the
use of non-
MBMS services
i.e. the PL is not
congested
REL-6

Transport Format Combination Subset 10.3.5.22
name
Need Multi Type and
reference
CHOICE Subset representation MP
>Minimum allowed Transport
format combination index
Transport
format
combination
10.3.5.19

Integer (0..
1023)

>Allowed transport format
combination list
1 to
<maxTFC>

>>Allowed transport format
combination
MP Transport
format
combination
10.3.5.19

Integer (0..
1023)

>Non-allowed transport format
combination list
1 to
<maxTFC>

>>Non-allowed transport format
combination
MP Transport
format
combination
10.3.5.19

Integer (0..
1023)

>Restricted TrCH information 1 to
<maxTrCH
>

>>Uplink transport channel type MP Enumerated(
DCH, USCH)
USCH is TDD only
>>Restricted UL TrCH identity MP Transport
channel
identity
10.3.5.18

>>Allowed TFIs OP 1 to
<maxTF>

>>>Allowed TFI MP Integer(0..31
)

>Full transport format
combination set
(No data)

Transport format combination set 10.3.5.20

name
Need Multi IE type and
reference
TFCI Field 1 Information MP TFCS
explicit
Configuratio
n 10.3.5.13

1>CHOICE TFCS
representation
MP
2>>Complete reconfiguration
3>>>TFCS complete
reconfiguration information
MP TFCS
Reconfigurat
ion/Addition
information
10.3.5.15

4>>>>CHOICE CTFC Size MP
5>>>>>2 bit CTFC
6>>>>>>CTFC information MP 1 to
<maxTFC>

7>>>>>>>2bit CTFC MP Integer(0..3)
7>>>>>>>Power offset
Information
OP Power Offset
Information
10.3.5.8
Needed only for uplink
physical channels.
5>>>>>4 bit CTFC
<maxTFC>

7>>>>>>>4bit CTFC MP Integer(0..15
)

Information
OP Power Offset
Information
10.3.5.8
physical channels.
5>>>>>6 bit CTFC
<maxTFC>

7>>>>>>>6 bit CTFC MP Integer(0..63
)

Information
OP Power Offset
Information
10.3.5.8
physical channels.
5>>>>>8 bit CTFC
<MaxTFC>

5)

Information
OP Power Offset
Information
10.3.5.8
physical channels.
5>>>>>12 bit CTFC
<maxTFC>

95)

Information
OP Power Offset
Information
10.3.5.8
physical channels.
5>>>>>16 bit CTFC
<maxTFC>

535)

Information
OP Power Offset
Information
10.3.5.8
physical channels.
5>>>>>24 bit CTFC

Transport format combination set 10.3.5.20
name
Need Multi IE type and
reference
<MaxTFC>

777215)

Information
OP Power Offset
Information
10.3.5.8
physical channels.
2>>Addition
3>>>TFCS addition information MP TFCS
Reconfigurat
ion/Addition
information
10.3.5.15

2>>Removal
3>>>TFCS removal information MP TFCS
Removal
Information
10.3.5.16

2>>Replace
3>>>TFCS removal information MP TFCS
Removal
Information
10.3.5.16

3>>>TFCS addition information MP TFCS
Reconfigurat
ion/Addition
information
10.3.5.15

Transport Format Set 10.3.5.23
name
Need Multi Type and
reference
Semantics description Version
CHOICE Transport channel type MP
>Dedicated transport
channels
The transport channel that is
configured with this TFS is of
type DCH

>>Dynamic Transport Format
Information
MP 1 to
<maxTF>

>>>RLC Size MP Integer(16..5
000 by step
of 8)

Unit is bits
>>>Number of TBs and TTI List MP 1 to
<maxTF>
Present for every valid number
of TB's (and TTI) for this RLC
Size.

>>>>Transmission Time Interval CV-
dynamicTT
I
Integer(10,2
0,40,80)
Unit is ms.
>>>>Number of Transport
blocks
MP Integer(0..51
2)

>>>CHOICE Logical Channel
List
MP The logical channels that are
allowed to use this RLC Size

>>>>ALL Null All logical channels mapped to
this transport channel.

>>>>Configured Null The logical channels
configured to use this RLC


name
Need Multi Type and
reference
size in the RB mapping info.
10.3.4.21 if present in this
message or in the previously
stored configuration otherwise
>>>>Explicit List 1 to 15 Lists the logical channels that
are allowed to use this RLC
size.

>>>>>RB Identity MP RB identity
10.3.4.16

>>>>>LogicalChannel CH-UL-
RLCLogica
lChannels
Integer(0..1) Indicates the relevant UL
logical channel for this RB. "0"
corresponds to the first, "1"
corresponds to the second UL
logical channel configured for
this RB in the IE "RB mapping
info".

>>Semi-static Transport Format
Information
MP Semi-static
Transport
Format
Information
10.3.5.11

Integer(10,
20, 40, 80,
dynamic
In ms. The value dynamic is
only used in TDD mode. For
FDD DCH, the value 80 is
applicable only when SF=512.
3>>>Transmission time interval MP
5) 5 is only applicable for the
RACH in 1.28 Mcps TDD
REL-4
3>>>Type of channel coding MP Enumerated(
No coding,
Convolutiona
l, Turbo)
The option "No coding" is only
valid for TDD.

3>>>Coding Rate CV-Coding Enumerated(
1/2, 1/3)

3>>>Rate matching attribute MP Integer(1..hi
RM)

3>>>CRC size MP Integer(0, 8,
12, 16, 24)
in bits
>Common transport channels The transport channel that is
configured with this TFS is of a
type not equal to DCH

>>Dynamic Transport Format
Information
MP 1 to
<maxTF>
Note
>>>RLC Size MP Integer(16..5
000 by step
of 8)

Unit is bits
>>>Number of TBs and TTI List MP 1 to
<maxTF>
Present for every valid number
of TB's (and TTI) for this RLC
Size.

>>>>Number of Transport
blocks
MP Integer(0..51
2)

>>>>CHOICE mode MP
>>>>>FDD (no data)
>>>>>TDD
>>>CHOICE Logical Channel
List
MP The logical channels that are
allowed to use this RLC Size.

>>>>ALL Null All logical channels mapped to
this transport channel.

>>>>Configured Null The logical channels
configured to use this RLC
size in the RB mapping info.


name
Need Multi Type and
reference
10.3.4.21 if present in this
message or in the previously
stored configuration otherwise
>>>>Explicit List 1 to 15 Lists the logical channels that
are allowed to use this RLC
size.

>>>>>RB Identity MP RB identity
10.3.4.16

>>>>>LogicalChannel CV-UL-
RLCLogica
lChannels
Integer(0..1) Indicates the relevant UL
logical channel for this RB. "0"
corresponds to the first, "1"
corresponds to the second UL
logical channel configured for
this RB in the IE "RB mapping
info".

>>Semi-static Transport Format
Information
MP Semi-static
Transport
Format
Information
10.3.5.11

Integer(10,
20, 40, 80,
dynamic
In ms. The value dynamic is
only used in TDD mode. For
FDD DCH, the value 80 is
applicable only when SF=512.
3>>>Transmission time interval MP
5) 5 is only applicable for the
RACH in 1.28 Mcps TDD
REL-4
3>>>Type of channel coding MP Enumerated(
No coding,
Convolutiona
l, Turbo)
The option "No coding" is only
valid for TDD.

3>>>Coding Rate CV-Coding Enumerated(
1/2, 1/3)

3>>>Rate matching attribute MP Integer(1..hi
RM)

3>>>CRC size MP Integer(0, 8,
12, 16, 24)
in bits

6.1.1.4 FEATURES 32687 [GLOBAL MARKET]
No impact.
Same as 18717
6.1.1.5.2 RADIO BEARER RECONFIGURATION
The radio bearer reconfiguration from AMR5.9 to AMR12.2 is done in parallel to a PS
RAB establishment. Thus the Radio Bearer Reconfiguration message is used to
modify the existing transport channel of the voice bearer and to establish the transport
channel for the PS bearer.


6.1.2 IU INTERFACE
The support of the following procedures is added:
Iu UP initialization / Iu UP initialization Ack
o Incoming in addition to outgoing
Iu UP Rate control / Iu UP Rate Control Ack
o Incoming / outgoing
Iu UP time alignment / Iu UP time alignment nack
o Incoming in addition to outgoing

TS 25.415 procedure Iu UP version 1 Iu UP version 2
6.6.2.3.4.1 Initialisation Number of subflows per RFCI (N)
List (1.. M) {RFCI, Length of subflow 1, ; Length of subflow N}
[Timing information (TI, IPTI of n
th
RFCI fields)]
Iu UP Mode Versions supported
DATA PDU type to be used for transferring user data (UL & DL)

6.6.2.3.4.2 Rate Control Number of RFCI indicators
List of {RFCI indicators*}

6.6.2.3.4.2.2 Rate Control positive
acknowledgement
N/A Number of RFCI indicators
List of {RFCI indicators*}

* RFCI n Indicator indicates if the RFCI with value n is allowed or barred.

6.1.2.2.1 RAB ASSIGNMENT REQUEST / RELOCATION
REQUEST
Additional values of the TS 25.413 UP Mode Versions IE to be taken into account.

6.1.2.3.1 RAB ASSIGNMENT REQUEST / RELOCATION
REQUEST
Same as 18717

6.1.2.3.2 RELOCATION REQUIRED / RELOCATION REQUEST
Same as 18717RAB ASSIGNMENT REQUEST (MODIFY)
Same as Initial RAB ASSIGNMENT REQUEST but for an already established RAB Id

No impact.

6.1.2.5.1 RAB ASSIGNMENT REQUEST/RELOCATION
REQUEST
AMR5.9 selection is only possible, when the MSC has included AMR5.9 related SDU
formats and RAB Parameters IE.
6.1.2.5.2 RAB ASSIGNMENT RESPONSE/RELCOCATION
REQUESTACKNOWLEDGE
With Feature 34216 the RNC populates the Assigned RAB Parameter Values IE in the
RAB Assignment Response and Relocation Request Acknowledge messages. If
AMR5.9 has been selected, then the RNC sets Assigned Guaranteed Bit Rate to
5900. If AMR12.2 has been selected, then the RNC sets Assigned Guaranteed Bit
Rate to 12200. The Assigned Maximum Bit Rate IE is set to 12200 independent of the
selected AMR codec rate.
6.1.2.5.3 ALCAP
The transport bearer at Iu is always established with AMR12.2 in order to be prepared
for a reconfiguration from AMR5.9 to AMR12.2.
6.1.2.5.4 IU UP
This feature is supported with Iu UP V1 only. At initialization of AMR5.9 the RNC
always establishes a RFCI also for 12.2. This RFCI is disabled at initialization and is
enabled only when reconfiguring the voice call from AMR5.9 to AMR12.2 by sending
an Iu UP Rate Control command to the MGW.

6.1.3 IUR INTERFACE
No impact
RNSAP
The impact on RNSAP is similar as for NBAP.

User Plane
Similar impacts on Iur UP as for Iub UP

Same impact as 18717

The impact on RNSAP is similar as for NBAP.
Same impact as for Iub.

6.1.4 IUB INTERFACE
No impact
No impact
Same impact as 18717

The following messages are used. They are already supported in previous release for
iRM scheduling feature
25.433 9.1.52 DEDICATED MEASUREMENT INITIATION REQUEST

25.433 9.1.53 DEDICATED MEASUREMENT INITIATION RESPONSE

25.433 9.1.54 DEDICATED MEASUREMENT INITIATION FAILURE

25.433 9.1.55 DEDICATED MEASUREMENT REPORT

25.433 9.1.56 DEDICATED MEASUREMENT TERMINATION REQUEST

25.433 9.1.57 DEDICATED MEASUREMENT FAILURE INDICATION

No new impact on NBAP.
When establishing a voice call using AMR5.9 the ALCAP bearer is established with a
equivalent bit rate for AMR5.9. When reconfiguring the AMR5.9 call to AMR12.2, this

transport bearer is replaced by a transport bearer with a equivalent bit rate for
AMR12.2.

6.1.5 IUPC INTERFACE (RNC/SAS)
Not applicable.
6.1.6 IUBC INTERFACE (RNC/CBC)
Not applicable.


6.2 OAM INTERFACES
6.2.1 3GPP OAM INTERFACES

No applicable

6.2.2 EXTERNAL ALCATEL-LUCENT OAM INTERFACES
6.2.2.1 WIPS INTERFACE (OPTIONAL)

6.2.2.2 OAM USER INTERFACE

No modification

6.3 TRANSMISSION NETWORK INTERFACES
6.3.1 PHYSICAL LAYER
No impact

6.3.2 ETHERNET
Not applicable
6.3.3 ATM
No impact
6.3.4 IP
Not applicable


7 OAM MODEL DESCRIPTION
Warning: The customer documentation is the reference for the names and values
regarding the OAM items: the name and values of these OAM items can change until
the CuR.
7.1 CONFIGURATION MANAGEMENT
7.1.1 RAN MANAGED OBJECTS
7.1.1.1 IU UP PROTOCOL (FEATURE 30229)
No modification
7.1.1.2 FEATURE 18717
New and modified RABs
The DlUserService, UlUserService, UlRbSetConf & DlRbSetConf instances previously
used for AMR 12.2 are now used for support of AMR 12.2, AMR (12.2, 7.95, 5.9, 4.75)
and AMR (10.2, 6.7, 5.9, 4.75).
The DlUserService, UlUserService, UlRbSetConf & DlRbSetConf instances previously
used for AMR 12.2 without VAD/DTX are now used for support of AMR 4.75 and AMR
(5.9, 4.75).

RNC/RadioAccessService/UlRbSetConf
UA04.2 UA05.0 RdnId
CSDTCH12_2K Not used 2
CSDTCH12_2KDTX CS_AMR_NB 5
CS_AMR_LR 16

RNC/RadioAccessService/UlUserService

UA04.2 UA05.0 rdnId
CSDTCH12_2Kx4SRBDCCH3_4K Not used 1
CSDTCH12_2KDTXx4SRBDCCH3_4K CS_AMR_NBxSRB_3_4K 5
CSDTCH12_2KDTXxPSDTCH64Kx4SRBDCCH3_4K CS_AMR_NBxPS_64K_IBxSRB_3_4K 8
CSDTCH12_2KxPSDTCH8Kx4SRBDCCH3_4K Not used 13
CSDTCH12_2KDTXx2PSDTCH64Kx4SRBDCCH3_4K CS_AMR_NBxPS_64K_IB_MUXxSRB_3_4K 21
CS_AMR_LRxSRB_3_4K 25
CS_AMR_NBxPS_64K_IB_MUXxSRB_3_4K 26
CS_AMR_NBxPS_32K_IBxSRB_3_4K 28
CS_AMR_NBxPS_16K_STRxSRB_3_4K 35

CS_AMR_NBxPS_16K_STRxPS_8K_IBxSRB_3_4K 38

Note. In UA06.0, additional user service combinations are supported in the scope of
the feature 33320 (cf. section 5.5.2.2.2.1)

RNC/RadioAccessService/DlRbSetConf
UA04.2 UA05.0 RdnId
CSDTCH12_2K Not used 2
CSDTCH12_2KDTX CS_AMR_NB 5
CS_AMR_LR 19
SRB_0_15K 27

RNC/RadioAccessService/DlUserService

UA04.2 UA05.0 rdnId
CSDTCH12_2Kx4SRBDCCH3_4K Not used 1
CSDTCH12_2KDTXx4SRBDCCH3_4K CS_AMR_NBxSRB_3_4K 5
CSDTCH12_2KDTXx2PSDTCH64Kx4SRBDCCH3_4K CS_AMR_NBxPS_64K_IB_MUXxSRB_3_4K 26
CS_AMR_LRxSRB_3_4K 31
CS_AMR_NBxPS_HSDSCHxSRB_3_4K 65
CS_AMR_NBxPS_16K_STRxPS_HSDSCHxSRB_3_4K 70


New components
ulTransportFormatCombinationSets
Characteristics property comments

Path RadioAccessService / UlUserService /
UlTransportFormatCombinationSets

Children ComputedGainFactors
SignalledGainFactors

Link(s) none
Identifier(s) primary
Cardinality 1..8 In UA05.0 a maximum of
6 instances is configurable
Create (off-line) Yes
Create on-line Yes
Delete on-line Yes
MO presence Required
Object to lock no

BlerQualityList
Path RadioAccessService / UlRbSetConf /
DynamicParameterPerDch / BlerQualityList

Children none
Link(s) none
Cardinality 1..3 1 or 3
Create on-line Yes
Delete on-line Yes
Object to lock no

dlBlerQualityList
Path RadioAccessService / DlRbSetConf /
dlDynamicParameterPerDch / dlBlerQualityList

Children none
Link(s) none
Cardinality 1..3 1 or 3
Create on-line Yes
Delete on-line Yes
Object to lock no

CacAal2InfoList
Paths RadioAccessService / UlRbSetConf /
CacAal2InfoList

RadioAccessService / DlRbSetConf /
CacAal2InfoList

Children none
Link(s) none
Cardinality 1..8 In UA05.0 a maximum of
2 instances of
CacAaal2InfoList is

configurable, i.e.
for UlRbSetConf 5 /
DlRbSetConf 5 instance 0
is for AMR12.2 & instance
1 is for AMR10.2
for UlRbSetConf 16 /
DlRbSetConf 19 instance
0 is for AMR 5.9 &
instance 1 is for AMR4.75

For all other RbSetConf
(non AMR related) only
instance 0 is created
Create on-line Yes
Delete on-line Yes
Object to lock no

Modified components

UlTransportFormatCombinationSets /
ComputedGainFactors
Path is modified
Children none
Link(s) none
Cardinality 1..128 Cardinality is modified
Create on-line Allowed with parent
Delete on-line Allowed with parent
MO presence Optional
Object to lock no

UlTransportFormatCombinationSets /
SignalledGainFactors
Path is modified
Children none
Link(s) none
Cardinality 1..128 Cardinality is modified
Create on-line Allowed with parent
Delete on-line Allowed with parent
MO presence Optional
Object to lock no

7.1.1.3 FEATURE 27803
New and modified RABs
The DlUserService, UlUserService, UlRbSetConf & DlRbSetConf instances to be used
for AMR-WB (codec rates 12.65, 8.85, 6.60)RNC/RadioAccessService/UlRbSetConf
UA05.0 UA05.1 RdnId
Not used Not used 2

CS_AMR_NB CS_AMR_NB 5
CS_AMR_LR CS_AMR_LR 16
CS AMR WB 7

RNC/RadioAccessService/UlUserService

UA05.0 UA05.1 rdnId
Not used Not used 1
CS_AMR_NBxSRB_3_4K CS_AMR_NBxSRB_3_4K 5
CS_AMR_NBxPS_64K_IBxSRB_3_4K CS_AMR_NBxPS_64K_IBxSRB_3_4K 8
Not used Not used 13
CS_AMR_NBxPS_64K_IB_MUXxSRB_3_4K CS_AMR_NBxPS_64K_IB_MUXxSRB_3_4K 21
CS_AMR_LRxSRB_3_4K CS_AMR_LRxSRB_3_4K 25
CS_AMR_NBxPS_16K_STRxSRB_3_4K CS_AMR_NBxPS_16K_STRxSRB_3_4K 35
CS_AMR_NBxPS_16K_STRxPS_8K_IBxSRB_3_4K CS_AMR_NBxPS_16K_STRxPS_8K_IBxSRB_3_4K 38
CS_AMR_WBxSRB_3_4K 57
CS_AMR_WBxPS_64K_IBxSRB_3_4K 58
CS_AMR_WBxPS_64K_IB_MUXxSRB_3_4K 63
CS_AMR_WBxPS_16K_STRxSRB_3_4K 65
CS_AMR_WBxPS_16K_STRxPS_8K_IBxSRB_3_4K 68
CS_AMR_WBxPS_E-DCH_IBxSRB_3_4K 71

CS_AMR_WBxPS_16K_STRxPS_E-
DCH_IBxSRB_3_4K
72

DCH_IBxSRB_3_4K
73

DCH_IBxSRB_3_4K
74


RNC/RadioAccessService/DlRbSetConf
UA05.0 UA05.1 RdnId
Not used Not used 2
CS_AMR_NB CS_AMR_NB 5
CS_AMR_LR CS_AMR_LR 19
SRB_0_15K SRB_0_15K 27
CS AMR WB 31


RNC/RadioAccessService/DlUserService

UA05.0 UA05.1 rdnId
Not used Not used 1
CS_AMR_NBxSRB_3_4K CS_AMR_NBxSRB_3_4K 5
Not used Not used 9
CS_AMR_LRxSRB_3_4K CS_AMR_LRxSRB_3_4K 31
CS_AMR_NBxPS_HSDSCHxSRB_3_4K CS_AMR_NBxPS_HSDSCHxSRB_3_4K 65
CS_AMR_NBxPS_16K_STRxPS_HSDSCHxSRB_3_4K CS_AMR_NBxPS_16K_STRxPS_HSDSCHxSRB_3_4K 57
CS_AMR_WBxSRB_3_4K 66
CS_AMR_WBxPS_HSDSCHxPS_HSDSCHx SRB_3_4K 83



7.1.1.4 FEATURE 32687-1
New paths
RNC / RadioAccessService / DlIrmTablePowerLoadConfClass / IrmAmrRateList
IrmAmrRatePerOls
RNC / RadioAccessService / UlIrmTableCellLoadConfClass / IrmAmrRateList
IrmAmrRatePerOls

New components
UlIrmTableCellLoadConfClass
Path RadioAccessService /
UlIrmTableCellLoadConfClass

Children IrmAmrRateList
Link(s) none
Cardinality 1..1
Create on-line No
Delete on-line No
Object to lock no

IrmAmrRateList
UlIrmTableCellLoadConfClass / IrmAmrRateList

Children IrmAmrRatePerOls
Link(s) none
Cardinality 1..3
Create on-line No
Delete on-line No
Object to lock no

IrmAmrRatePerOls
UlIrmTableCellLoadConfClass / IrmAmrRateList
/ IrmAmrRatePerOls

Children none
Link(s) none
Cardinality 1..3
Create on-line No
Delete on-line No
Object to lock no


DlIrmTablePowerLoadConfClass
DlIrmTablePowerLoadConfClass

Link(s) none
Cardinality 1..1
Create on-line No
Delete on-line No
Object to lock no

IrmAmrRateList
DlIrmTablePowerLoadConfClass /
IrmAmrRateList

Children IrmAmrRatePerOls
Link(s) none
Cardinality 1..3
Create on-line No
Delete on-line No
Object to lock no

IrmAmrRatePerOls
DlIrmTablePowerLoadConfClass /
IrmAmrRateList / IrmAmrRatePerOls

Children none
Link(s) none
Cardinality 1..3
Create on-line No
Delete on-line No
Object to lock no

7.1.1.5 FEATURE 32687-2
New path
RNC / RadioAccessService / DlIrmTableIubDsLoadConfClass / IrmAmrRateList
IrmAmrRatePerOls

New components
DlIrmTableIubDsLoadConfClass

DlIrmTableIubDsLoadConfClass

Link(s) none
Cardinality 1..1
Create on-line No
Delete on-line No
Object to lock no

IrmAmrRateList
DlIrmTableIubDsLoadConfClass /
IrmAmrRateList

Children none
Link(s) none
Cardinality 1..6
Create on-line No
Delete on-line No
Object to lock no

IrmAmrRatePerOls
DlIrmTableIubDsLoadConfClass /
IrmAmrRateList / IrmAmrRatePerOls

Children none
Link(s) none
Cardinality 1..3
Create on-line No
Delete on-line No
Object to lock no

New components
DLCodeiRMTable
Path RadioAccessService / DLCodeiRMTable
Children irmAmrConfList
Link(s) none
Cardinality 1..1
Create on-line No

Delete on-line No
Object to lock no

7.1.2 RAN CUSTOMER PARAMETERS
7.1.2.1 IU UP PROTOCOL (FEATURE 30229)

Source Creation
Object name RadioAccessService
parameter name allowedIuUpVersion
Category standard
Class 3-A2
Associated Event next DCH allocation
Domain RNC
definition 3GPP based parameter (TS 25.413 UP Mode Versions)
To allow OA&M controllable selection of allowed version of the Iu UP frame protocol
proposed by the Core Network via the RANAP RAB Assignment Request or the
Relocation Request message.

If V1 is selected then only the Iu UP FP procedures as supported in UA04 are
allowed. If the UP Mode Versions IE of the RANAP RAB Assignment Request or the
Relocation Request message indicates that version 1 is not supported by the Core
Network, then the RNC, as per 3GPP TS 25.413, cannot initialize the requested UP
mode and the RAB assignment will fail.
The feature 30229 is allowed by selection of V2orv1
If V2andv1 is selected then the RNC will select the version of the Iu UP frame
protocol according to the UP Mode Versions IE of any RAB Assignment Request. If
UP Mode Versions IE indicates that both versions are supported by the CN, then the
RNC will preferably try with version 2 of the protocol.

Optional No
Range Enum { V1 (0), V2orv1 (1), }

Unit N/A
Initial values V1 (0)
Recommended values V2orv1 (1)
Upgrade rule No
Control rule No

Source Creation
parameter name isAmrMultiModeAllowed
Category standard
Class 3-A2
Domain RNC
definition To allow OA&M controllable activation / deactivation of the feature 18717
Optional No
Range Enum {Disabled (0) , completelyEnabled (1), enabledPerCell (2) }
Unit N/A

Initial values Disabled (0)
Recommended values completelyEnabled (1)
Upgrade rule No
Control rule No
Source Creation
parameter name IsSrb5Allowed
Category standard
Class 3-A2
Domain RNC
definition Allows to enable/disable use of SRB 5 when the RNC takes the serving role (i.e. this
parameter is not applicable whenever the RNC takes the drift role)
Optional No
Range Enum {False (0), True (1) }
Unit N/A
Initial values False (0)
Recommended values True (1)
Upgrade rule No
Control rule No
Source Creation
parameter name minUeRelForSrb5Amr
Category standard
Class 3-A2
Domain RNC
definition This parameter provides the min 3GPP UE release required to setup an SRB#5
Optional No
Range Enum {Rel4 (0), Rel5 (1), Rel6 (2)}
Unit N/A
Initial values Rel6 (2)
Recommended values Rel6 (2)
Upgrade rule No
Control rule No
Source Creation
Object name csCoreNetworkAccess
parameter name IsCnInitiatedRateControlAllowed
Category standard
Class 3-A2
Domain RNC
definition This parameter is applicable only for case the call is established with version 2 of Iu
User Plane.
If the parameter is set to True subsequent incoming Iu UP FP Rate Control are
accepted. In addition, an SRB#5 is setup provided that other conditions are met as
well, i.e. the UE 3GPP release is of minUeRelForSrb5Amr or later, IsSrb5Allowed is
set to True, the UE Transport Capability allows it.
Otherwise subsequent incoming Rate Control frames are rejected.

Optional No
Unit N/A
Recommended values True (1) // for case the Core Network may put the call in TrFO or TFO
Upgrade rule No
Control rule No
Source Creation
Object name FddCell
parameter name isAmrMultiModeSetupAllowed
Category standard
Class 3-A2
Associated Event next DCH
Domain RNC
definition Allows to enable/disable multi-mode AMR per cell
Optional No

Unit N/A
Recommended values True (1)
Upgrade rule No
Control rule No
UlRbSetConf
The following Customer Class 3 parameters are made available per AMR mode (up to
8 modes), per AMR Max bit rate (2 in this version of the product: depending on
selected UlRbsetConf AMR max rate is 12.2 or 10.2 / 5.9 or 4.75) or per OLS (3
subscriber classes) creation / modification are indicated in shaded
text:cacAal2InfoList[1.. MAX_NB_REF_AMR_BIT_RATE (8)] related parameters
DynamicParameterPerDch[0..MAX_NB_DCH_PER_RBSET_CONF(3)] / BlerQualityList
[1 or 3] / blerTarget
DynamicParameterPerDch[0..MAX_NB_DCH_PER_RBSET_CONF(3)] / BlerQualityList
[1 or 3] / priorityLevel
DynamicParameterPerDch[0..MAX_NB_DCH_PER_RBSET_CONF(3)]
/ulRateMatchingAttributeList[1.. MAX_NB_REF_AMR_BIT_RATE (8)]
Source Creation
Object name UlRbSetConf / DynamicParameterPerDch / BlerQualityList
parameter name blerTarget
Category standard
Class 3-A2
Domain RNC
definition Defines the target radio interface Transport Block Error Rate of the transport channel
Optional No
Range
Unit N/A
Initial values N/A
Recommended values
Upgrade rule Yes. Refer to section 8.1.2 RNC & BTS Upgrade
Control rule No
Source Creation
Object name UlRbSetConf / DynamicParameterPerDch / BlerQualityList
parameter name priorityLevel
Category standard
Class 3-A2
Domain RNC
definition Allows to identify the UL BLER Target value to be used for the 3GPP TS 25.413
Priority Level
Optional No
Range 1..15
Unit N/A
Initial values
Recommended values
Upgrade rule No
Control rule No
Source Creation
Object name UlRbSetConf / DynamicParameterPerDch /
parameter name ulRateMatchingAttributeList
Category standard
Class 3-A2
Domain RNC
definition List (1 to 8) of Rate matching attributes
In UA05.0, a maximum of 2 instances is configurable
Optional No
Range 1..256
Unit N/A
Initial values N/A
Recommended values
Control rule No

DlRbSetConf

The following Customer Class 3 parameters are made available per AMR mode (up to
8 modes), per AMR Max bit rate (2 in this version of the product: depending on
selected DlRbsetConf AMR max rate is 12.2 or 10.2 / 5.9 or 4.75) or per OLS (3
subscriber classes) creation / modification are indicated in shaded
text:cacAal2InfoList[1.. MAX_NB_REF_AMR_BIT_RATE (8)] related parameters
dlDynamicParameterPerDch [1.. MAX_NB_DCH_PER_RBSET_CONF(3)] /
dlBlerQualityList[1 or 3] / blerTarget *
dlBlerQualityList[1 or 3] / priorityLevel
dlRateMatchingAttribute [1.. MAX_NB_REF_AMR_BIT_RATE (8)]

(*) As per 3GPP spec, the SIR target shall be set per Transport Channel. Clarification text -CR 2607 on TS
25.331 [R1]: the SIR target shall be set on a Transport Channel level, and not for each Transport Format.
This means that the UE is not to compensate for the fact that the required Ec/No to achieve a target BLER
for a particular transport format is different from the required Ec/No to achieve the target BLER for another
transport format.
Source Creation
Object name DlRbSetConf / DlDynamicParameterPerDch / dlBlerQualityList
parameter name blerTarget
Category standard
Class 3-A2
Domain RNC
definition Defines the target radio interface Transport Block Error Rate of the transport channel
Optional No
Range
Unit N/A
Initial values N/A
Recommended values
Control rule No
Source Creation
Object name DlRbSetConf / DlDynamicParameterPerDch / dlBlerQualityList
parameter name priorityLevel
Category standard
Class 3-A2
Domain RNC
definition Allows to identify the DL BLER Target value to be used for the 3GPP TS 25.413
Priority Level
Optional No
Range 1..15
Unit N/A
Initial values N/A
Recommended values
Upgrade rule No
Control rule No
Source Creation
Object name DlRbSetConf / dlDynamicParameterPerDch /
parameter name dlRateMatchingAttributeList
Category standard
Class 3-A2
Domain RNC
definition List (1 to 8) of Rate matching attributes
In UA05.0, a maximum of 2 instances is configurable
Optional No
Range 1..256
Unit N/A
Initial values N/A
Recommended values

Control rule No

UlUserService

The following Customer Class 3 parameters are made available per AMR mode (up
to 8 modes)
computedGainFactors / refTfcId
signalledGainFactors / betaC
signalledGainFactors / betaD
signalledGainFactors / refTfcId
Cf. ulTransportFormatCombinationSets component description in section 7.1.1.2.


Source Creation
parameter name isAmrWbAllowed
Category standard
Class 3-A2
Domain RNC
Optional No
Range Boolean
Unit N/A
Initial values False
Recommended values True
Upgrade rule No
Control rule No

Source Creation
parameter name isCsRabModificationForSpeechAllowed
Category standard
Class 3-A2
Associated Event next RanapRabAssignment for CS Rab Modifiy
Domain RNC
definition Indicates if the CS Rab modification is allowed
Optional No
Range Bolean
Unit N/A
Recommended values True (1) // to enable WB-AMR to/from NB-AMR reconfiguration
Upgrade rule No
Control rule No
Source Creation
Object name UlRbSetConf
parameter name IuUpInitEndTimeBeforeCfn
Category standard
Class 3-A2
Domain RNC
definition Target time for Iu-UP Initialization procedure to be completed before radio
CFN reach in case of CS Rab Modify
Optional No
Range u16 [0 .. 65535]
Unit ms
Initial values TBC

Recommended values TBC
Control rule No


Modified parameters (applicable prior UA05.1)
Source Creation
parameter name isDynamicMacdPduSizeManagementAllowed
Category standard
Class 3-A2
Associated Event RAB matching or Active Set Update
Domain RNC
(Use of a spare parameter)
Optional No
Range Enum {False (0), True(1)}
Unit N/A
Upgrade rule No
Control rule No

Source Creation
Object name FddCell
parameter name maxDlAmrRateConfigured
Category standard
Class 3-A2
Domain RNC
definition This parameter sets a maximum downlink rate for AMR calls in the cell
(Use of a spare parameter)
Optional No
Range Enum {12.2 (10), 10.2 (16), 7.95 (32), 7.4 (48), 6.7 (64), 5.9 (80), 5.15 (96), 4.75
(112)}
Unit kbps
Initial values 10
Recommended values 10
Upgrade rule No
Control rule No

Parameters applicable from UA05.1
Source Creation
parameter name isMaxDlAmrRateConfiguredAllowed
Category standard
Class 3-A2
Domain RNC
Optional No
Unit N/A
Upgrade rule No

Control rule No

Source Creation
Object name FddCell
parameter name maxDlAmrRateConfigured
Category standard
Class 3-A2
Domain RNC
definition This parameter sets a maximum downlink rate for AMR calls in the cell
Optional No
Range 12.2, 10.2, 7.95, 7.4, 6.7, 5.9, 5.15, 4.75
Unit kbps
Initial values 12.2
Recommended values 12.2
Upgrade rule No
Control rule No

7.1.2.5 FEATURES 32687-1 [GLOBAL MARKET]

Source Creation
parameter name IsAmrRateControlDuringTheCallAllowed
Category standard
Class 3-A2
Associated Event Event reception (next verification of AMR rate control eligibility)
Domain RNC
definition To allow OA&M controllable activation/deactivation of the feature 32687-1, i.e. AMR
rate control during the call based on DL power load and UL cell load criteria.
Optional No
Unit N/A
Upgrade rule No
Control rule No

Source Creation
parameter name isAmrRateControlOnULCellLoadAllowed
Category standard
Class 3-A2
Domain RNC
definition To allow OA&M controllable activation/deactivation of AMR rate control based on
uplink cell load changes
Optional No
Unit N/A
Upgrade rule No
Control rule No

Source Creation
parameter name isAmrRateControlOnDlPowerLoadAllowed
Category standard
Class 3-A2

Domain RNC
downlink power load changes
Optional No
Unit N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / UlIrmTableCellLoadConfClass / irmAmrRateList /
irmAmrRatePerOls
RadioAccessService / DlIrmTablePowerLoadConfClass / irmAmrRateList /
irmAmrRatePerOls
parameter name irmAmrRate
Category standard
Class 3-a2
Associated Event Taken into account on next iRM table evaluation
Domain RNC
definition Defines the maximum AMR rates based on the OLS and the UL cell load color.
Optional No
Range Enum { 4.75k (0), 5.15k (1), 5.9k (2), 6.7k (3), 7.4k (4), 7.95k (5), 10.2k (6), 12.2k (7) }
Unit N/A
Initial values 12.2k (7)
Recommended values N/A
Upgrade rule No
Control rule No

Source Creation
parameter name delayBetweenAmrRateControls
Category standard
Class 3-A2
Domain RNC
definition This controls delay between two AMR rate control assessments.
Optional No
Range Integer [500..60000] Step 10
Unit ms
Initial values 5000
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DlUserService
parameter name isAmrRateControlOnULCellLoadAllowed
Category standard
Class 3-A2
Associated Event Event reception (next DlUserService change)
Domain RNC
uplink cell load changes
Optional No

Unit N/A
Initial values True
Upgrade rule No
Control rule No

Source Creation
parameter name isAmrRateControlOnDlPowerLoadAllowed
Category standard
Class 3-A2
Associated Event Event reception (next DlUserService change)
Domain RNC
downlink power load changes
Optional No
Unit N/A
Upgrade rule No
Control rule No

Source Creation
parameter name dlAmrRateDecreaseAbsoluteTxcpTrigger
Category standard
Class 3-A2
Domain RNC
definition Used to configure an event A NBAP dedicated measurement for Transmitted Code
Power over Iur.
Optional No
Range N/A
Unit N/A
Initial values N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DlUserService / dlAmrRateDecreaseAbsoluteTxcpTrigger
parameter name threshold
Category standard
Class 3-A2
Domain RNC
definition Defines the absolute requested threshold.
Optional No
Range [-10.0..46.0] step:0.5
Unit dBm
Initial values 46.0
Recommended values
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DlUserService / dlAmrRateDecreaseAbsoluteTxcpTrigger
parameter name timeToTrigger

Category standard
Class 3-A2
Domain RNC
definition This TS 25.433 parameter defines the value of the hysteresis time required to
configure an Event A NBAP dedicated measurement.

Optional No
Range 10..60000] step:10
Unit ms
Initial values 5000
Recommended values
Upgrade rule No
Control rule No

Source Creation
parameter name dlAmrRateIncreaseAbsoluteTxcpTrigger
Category standard
Class 3-A2
Domain RNC
definition Used to configure an event B NBAP dedicated measurement for Transmitted Code
Power over Iur.
Optional No
Range N/A
Unit N/A
Initial values N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DlUserService / dlAmrRateIncreaseAbsoluteTxcpTrigger
parameter name threshold
Category standard
Class 3-A2
Domain RNC
definition Defines the absolute requested threshold.
Optional No
Range [-10.0..46.0] step:0.5
Unit dBm
Initial values -10.0
Recommended values
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DlUserService / dlAmrRateIncreaseAbsoluteTxcpTrigger
Category standard
Class 3-A2
Domain RNC
configure an Event B NBAP dedicated measurement.

Optional No
Range [10..60000] step:10
Unit ms

Initial values 5000
Recommended values
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / dedicatedConf / PowerConfClass / DlUsPowerConf
parameter name dlAmrRateDecreaseTxcpTrigger
Category standard
Class 3-A2
Domain RNC
definition Used to configure an event A NBAP dedicated measurement for Transmitted Code
Power.
Optional No
Range N/A
Unit N/A
Initial values N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / dedicatedConf / PowerConfClass / DlUsPowerConf /
dlAmrRateDecreaseTxcpTrigger
parameter name thresholdDelta
Category standard
Class 3-A2
Domain RNC
definition Delta value of the requested threshold of Transmitted code power to configure an
Event A NBAP dedicated measurement.
Helps to define the requested threshold:
Threshold = pcpichPower + maxDlTxPowerPerOls[].maxDlTxPower thresholdDelta
Optional No
Range Decimal [0.0..56.5] Step 0.5
Unit dB
Initial values 0
Recommended values
Upgrade rule No
Control rule No

Source Creation
dlAmrRateDecreaseTxcpTrigger
Category standard
Class 3-A2
Domain RNC
configure an Event A NBAP dedicated measurement.

Optional No
Unit ms
Initial values 5000
Recommended values
Upgrade rule No

Control rule No

Source Creation
parameter name dlAmrRateIncreaseTxcpTrigger
Category standard
Class 3-A2
Domain RNC
definition Used to configure an event B NBAP dedicated measurement for Transmitted Code
Power over Iur.
Optional No
Range N/A
Unit N/A
Initial values N/A
Upgrade rule No
Control rule No

Source Creation
dlAmrRateIncreaseTxcpTrigger
parameter name thresholdDelta
Category standard
Class 3-A2
Domain RNC
definition Helps to define the requested threshold:
Threshold = pcpichPower + maxDlTxPowerPerOls[].maxDlTxPower thresholdDelta
Optional No
Range Decimal [0.0..56.5] Step 0.5
Unit dB
Initial values 0
Recommended values
Upgrade rule No
Control rule No

Source Creation
dlAmrRateIncreaseTxcpTrigger
Category standard
Class 3-A2
Domain RNC
configure an Event B NBAP dedicated measurement.

Optional No
Unit ms
Initial values 5000
Recommended values
Upgrade rule No
Control rule No


Source Modification
Object name RadioAccessService / dedicatedConf / PowerConfClass / DlUsPowerConf
parameter name maxDlTxPowerPerOls
Category standard
Class 3-A2
Associated Event Event reception (RL setup, add, reconf)
Domain RNC
definition The TS 25.433 Maximum DL power the Node B can allocate to the call. It represents
a power level relative to the P-CPICH power. For the first foreseen algorithm, which
allows RNC to reserve MaxDlTxPower-Delta for a call establishment, some
considerations must be taken into account. It must be adapted (fitted) as much as
possible to service and to Eb/N0 requirement in order to avoid wasting power and to
be received by the UE wherever it is located in the coverage area. This power must
be delivered by taking account of the power available for traffic admission for the
required type of service (speech, data) by referring to the TrafficClassRatio.
Optional No
Range Decimal [1..3] [-35.0..15.0] Step 0.1
Unit dB
Initial values
Recommended values
Upgrade rule No
Control rule No

7.1.2.6 FEATURES 32687-2 [GLOBAL MARKET]

Source Creation
parameter name isAmrRateControlOnIubDsLoadAllowed
Category standard
Class 3-A2
Domain RNC
definition To allow OA&M controllable activation/deactivation of AMR rate control based on Iub
DS load changes
Optional No
Unit N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DlIrmTableIubDsLoadConfClass / irmAmrRateList /
irmAmrRatePerOls
parameter name irmAmrRate
Category standard
Class 3-a2
Domain RNC
definition Defines the maximum AMR rates based on the OLS and the Iub DS load color.
Optional No
Range Enum { 4.75k (0), 5.15k (1), 5.9k (2), 6.7k (3), 7.4k (4), 7.95k (5), 10.2k (6), 12.2k (7) }
Unit N/A
Upgrade rule No

Control rule No

Source Creation
parameter name isMultipleAmrMonoModewithIuUpV1Allowed
Category standard
Class 3-B
Associated Event N/A
Domain RNC
definition This parameter is used to enable the selection AMR subrate configurations in AMR
monorate mode , e,g, AMR5.9, when the RNC receives a RAB Assignment Request
or Relocation Request which offers multiple AMR codecs and IuUP Mode Version 1.
Optional No
Unit N/A
Upgrade rule No
Control rule No

Source Creation
parameter name DLCodeiRMTable
Category standard
Class 3-a2
Domain RNC
definition DL Code iRM table used for AMR RB selection for IU UP V1
Optional No
Range N/A
Unit N/A
Initial values N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DLCodeiRMTable
parameter name irmAmrConfList[MAX_CELL_COLORS][MAX_OLYMPIC_SERVICE_LEVEL]
Category standard
Class 3-a2
Domain RNC
definition Specifies RB type for AMR multirate mode and the spreading factor to be used for
AMR5.9 monorate operation dependent on the DL code load color and the user AR
priority level.
Optional
Range The max number of elements in this list is MAX_CELL_COLORS (3) X
MAX_OLYMPIC_SERVICE_LEVEL (3)
Unit N/A
Initial values N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DLCodeiRMTable / irmAmrConfList [][]
parameter name amr5p9MonoRateConfig
Category standard
Class 3-a2

Domain RNC
definition Specifies the spreading factor to be used for AMR5.9 monorate operation dependent
on the DL code load color and the user AR priority level.
Optional No
Range Enum { SF128(0), SF256(1)}
Unit N/A
Initial values 0
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DLCodeiRMTable / irmAmrConfList [][]
parameter name amrRateConfig
Category standard
Class 3-a2
Domain RNC
definition Specifies the RB to be chosen when AMR narrowband RB selection function is
applied, according to user ARP priority level and DL Code load color.
Optional No
Range Enum { AmbNbHighRate (0), AmrNbLowRate (1) }
Unit N/A
Initial values 0
Upgrade rule No
Control rule No

Source Creation
Object name CsCoreNetworkAccess
parameter name MinTimePerfIURateCtrl
Category standard
Class 3-a2
Associated Event next reconfiguration from AMR5.9 to AMR12.2
Domain RNC
definition The minimum time prior to the activation/commit time that the Iu rate control
procedure is performed during a transport channel reconfiguration as part of an AMR
codec rate change.
Optional No
Range [0..255]
Unit 10 msec
Initial values 10
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / DlIrmTableIubDsLoadConfClass
parameter name irmAmrMonoRate
Category Standard
Class 3-a2
Domain RNC
definition Specified the AMR monorate codec to be applied based on the current DL power load
color and the user AR priority level.
Optional No
Range Enum { 5.9k (0), 12.2k (1) }
Unit N/A
Upgrade rule No
Control rule No


Source Creation
Object name RadioAccessService / DlIrmTablePowerLoadConfClass
Category standard
Class 3-a2
Domain RNC
definition Specified the AMR monorate codec to be applied based on the current DL power load
Optional No
Range Enum { 5.9k (0), 12.2k (1) }
Unit N/A
Upgrade rule No
Control rule No

Source Creation
Object name RadioAccessService / UlIrmTableCellLoadConfClass
Category standard
Class 3-a2
Domain RNC
definition Specifies the AMR monorate codec to be applied based on the current UL cell load
Optional No
Range Enum { 5.9k (0), 12.2k (1) }
Unit N/A
Upgrade rule No
Control rule No

7.1.3 CDL

7.1.4 CDL: NEW/MODIFIED/REMOVED COMPONENTS
No modification.
7.1.5 CONTROL RULES
No modification.

7.2 FAULT MANAGEMENT
7.2.1 RNC CNODE, BTS AND OAM ALARM NOTIFICATIONS

No impact

7.2.2 RNC INODE ALARM NOTIFICATIONS
No impact.

7.2.3 STATE CHANGES
No impact.

7.3 PERFORMANCE MANAGEMENT
7.3.1 COUNTERS

7.3.1.1 FEATURE 30229
Counters to used to provide Statistics on the number of Rate Control coming
from the CN
Measurement Name NT_Iu_received_AMR_rate control (1516)
3GPP name (itf-N) VS.IuRcvdAmrRtCtrl
Description Number of received Iu rate control in AMR-NB CS speech calls
Collection Method CC GAUGE DER SI
X
Condition Reception of Iu rate control during AMR-NB CS speech call
Measurement Result
Measurement Type
Measurement Object
Instance
FddCell (reference cell)
Switching Technology Circuit Switched
3GPP compliance
Comments
Observation type GPO: RNC
objectives QoS reporting
Temporal aggregation rule Rtotal as defined in [R24]


7.3.1.2 FEATURE 18717
All PM counters, which are per UL/DL RbSetConf or UL/DL AsConf including the AMR
speech service are impacted. For this set of PM counters, please refer to the customer
document.

Modified counters

Counters used to provide Statistics on the UL BLER per Mode

Measurement Name NT_Dedicated_uplink_AMR_A_bits_good_frames (1506)
3GPP name (itf-N) VS.DdUlAmrABtGoodFrm
Description Number of AMR frames with Class A bits Transport Block received with CRC
indicator (3GPP TS 25.415 CRCi) = 0
X
Condition Reception on the uplink direction of an AMR frame Class A bits Transport
Block, with CRCi = 0
Measurement Result
Measurement Type Screening per AMR-NB mode:
AMR_12.2 (0): 12.2,
AMR_10.2 (1): 10.2,
AMR_7.95 (2): 7.95,
AMR_7.4(3): 7.4,
AMR_6.7 (4): 6.7,
AMR_5.9 (5): 5.9,
AMR_5.15 (6): 5.15 (not pegged in UA06),
AMR_4.75 (7): 4.75

Measurement Object
Instance
3GPP compliance
Comments

Measurement Name NT_Dedicated_uplink_AMR_A_bits_bad_frames (1507)
3GPP name (itf-N) VS.DdUlAmrABtBadFrm
Description Number of AMR frames with Class A bits Transport Block received with CRC
indicator (3GPP TS 25.415 CRCi) = 1
X
Condition Reception on the uplink direction of an AMR frame Class A bits Transport
Block, with CRCi = 1
Measurement Result
AMR_12.2 (0): 12.2,
AMR_10.2 (1): 10.2,
AMR_7.95 (2): 7.95,
AMR_7.4(3): 7.4,
AMR_6.7 (4): 6.7,
AMR_5.9 (5): 5.9,
AMR_4.75 (7): 4.75

Measurement Object
Instance
3GPP compliance

Comments

New counters

Counters used to provide Statistics on the UL/DL Mode used

Measurement Name NT_UL_AMR_frame_by_rate (1514)
3GPP name (itf-N) VS.UlAmrFrmRt
Description Number of AMR calls by rate in the UL direction
X
Condition Reception of an AMR frame in the UL direction
Measurement Result
AMR_12.2 (0): 12.2,
AMR_10.2 (1): 10.2,
AMR_7.95 (2): 7.95,
AMR_7.4(3): 7.4,
AMR_6.7 (4): 6.7,
AMR_5.9 (5): 5.9,
AMR_4.75 (7): 4.75
AMR_SID (8): 1.8

Measurement Object
Instance
3GPP compliance
Comments
objectives Call profile reporting

Measurement Name NT_DL_AMR_frame_by_rate (1513)
3GPP name (itf-N) VS.DlAmrFrmRt
Description Number of AMR calls by rate in the DL direction
X
Condition Reception of an AMR frame in the DL direction
Measurement Result
AMR_12.2 (0): 12.2,
AMR_10.2 (1): 10.2,
AMR_7.95 (2): 7.95,
AMR_7.4(3): 7.4,
AMR_6.7 (4): 6.7,
AMR_5.9 (5): 5.9,
AMR_4.75 (7): 4.75
AMR_SID (8): 1.8

Measurement Object
Instance
3GPP compliance
Comments


Counters used to provide Statistics on the Frame Quality of the DL frames

Measurement Name NT_Iu_DL_AMR_frames_by_fqc (1505)
3GPP name (itf-N) VS.IuDlAmrFrmFqc
Description Number of AMR frames received on Iu by Frame Quality Classification (FQC)

3GPP TS 25.415. Frame Quality Classification is used to classify the Iu UP
frames depending on whether errors have occurred in the frame or not.
X
Condition Reception of an Iu UP PDU including an AMR frame
Measurement Result
Measurement Type Screening per Frame Quality Classification (FQC):
FrameGood (0): Frame Good,
FrameBad (1): Frame Bad,
FrameBadDueToRadio (2): Frame bad due to radio

Measurement Object
Instance
3GPP compliance
Comments

Counters used to provide Statistics on the number of Rate Changes coming
from the CN

Measurement Name NT_DL_AMR_rate_change (1515)
3GPP name (itf-N) VS.DlAmrRtChg
Description Change of AMR mode in the DL direction.
The silence mode is not taken into account (SID frames & NO-DATA)
X
Condition Reception of an Iu UP PDU including an AMR frame
Measurement Result
Measurement Type
Measurement Object
Instance
3GPP compliance
Comments


AMR WB Counter 1
Nb: Id: NT_Dedicated_uplink_AMR_WB_A_bits_good_frames
3GPP: No 3GPP_Name: -
Location: FDDCELL (REFERENCE_CELL) Unit:
EVENT
Range:
31Bits
Screened:
YES
Type: CUM
Meaning: Number of AMR WB frames with Class A bits Transport Block received with CRCi = 0

Triggering event: Reception of AMR WB frame with Class A bits TB on uplink, where CRCi = 0
Screening criteria: AMR WB rate
Screening: 0 12.65
Screening: 1 8.85
Screening: 2 6.60

AMR WB Counter 2
Nb: Id: NT_Dedicated_uplink_AMR_WB_A_bits_bad_frames
EVENT
Range:
31Bits
Screened:
YES
Type: CUM
Meaning: Number of AMR WB frames with Class A bits Transport Block received with CRCi = 1
Triggering event: Reception of AMR WB frame with Class A bits TB on uplink, where CRCi = 1
Screening: 0 12.65
Screening: 1 8.85
Screening: 2 6.60

AMR WB Counter 3
Nb: Id: NT_Iu_received_AMR_WB_rate control
EVENT
Range:
31Bits
Screened:
NO
Type: CUM
Meaning: Number of received Iu rate control in AMR WB calls
Triggering event: Reception of Iu rate control during AMR WB call

AMR WB Counter 4
Nb: Id: NT_DL_AMR_WB_frames_by_rate
EVENT
Range:
31Bits
Screened:
YES
Type: CUM
Meaning: Number of DL AMR WB frames by rate
Triggering event: Reception of DL AMR WB frame
Screening: 0 12.65
Screening: 1 8.85
Screening: 2 6.60

Screening: 3 AMR WB SID

AMR WB Counter 5
Nb: Id: NT_UL_AMR_WB_frames_by_rate
EVENT
Range:
31Bits
Screened:
YES
Type: CUM
Meaning: Number of UL AMR WB frames by rate
Triggering event: Reception of UL AMR WB frame
Screening criteria: AMR rate
Screening: 0 12.65
Screening: 1 8.85
Screening: 2 6.60
Screening: 3 AMR WB SID

AMR WB Counter 6
Nb: Id: NT_DL_AMR_WB_rate_change
EVENT
Range:
31Bits
Screened:
NO
Type: CUM
Meaning: Number of DL rate change in AMR WB calls
Triggering event: Change of DL rate in AMR WB (silence not taken into account)

AMR WB Counter 7
Nb: Id: NT_Iu_DL_AMR_WB_frames_by_fqc
EVENT
Range:
31Bits
Screened:
YES
Type: CUM
Meaning: Number of AMR WB frames received on Iu by FQC
Triggering event: Reception of AMR WB frame on Iu UP
Screening criteria: Frame Quality Classification
Screening: 0 frame good
Screening: 1 frame bad
Screening: 2 frame bad due to radio

AMR WB Counter 8
Nb: Id: NT_AMR_RAB_modification_success

Location: RNC Unit:
EVENT
Range:
31Bits
Screened:
NO
Type: CUM
Meaning: Number of successful AMR RAB modification
Triggering event: RANAP RAB ASSIGNMENT RESPONSE message, success

AMR WB Counter 9
Nb: Id: NT_AMR_RAB_modification_unsuccess
Location: RNC Unit:
EVENT
Range:
31Bits
Screened:
NO
Type: CUM
Meaning: Number of unsuccessful AMR RAB modification
Triggering event: RANAP RAB ASSIGNMENT RESPONSE message, failure

AMR WB Counter 10
Nb: Id: NT_AMR_WB_RAB_modification_success
Location: RNC Unit:
EVENT
Range:
31Bits
Screened:
NO
Type: CUM
Meaning: Number of successful AMR WB RAB modification
Triggering event: RANAP RAB ASSIGNMENT RESPONSE message, success

In UA05 the only supported modification of AMR WB RAB is AMR WB to AMR.

AMR WB Counter 11
Nb: Id: NT_AMR_WB_RAB_modification_unsuccess
Location: RNC Unit:
EVENT
Range:
31Bits
Screened:
NO
Type: CUM
Meaning: Number of unsuccessful AMR WB RAB modification
Triggering event: RANAP RAB ASSIGNMENT RESPONSE message, failure

7.3.1.4 FEATURE 33863
No specific counters


Counters used to provide Statistics on the reason for AMR rate changes

Measurement Name NT_Rnc_Initiated_Amr_Nb_DL_Rate_Control (1535)
3GPP name (itf-N) VS.RncInitiatedAmrNbDlRateCtrl
Description Number of time an AMR-NB DL rate has changed due to due to UTRAN
specific criteria (DL Tx power consumption or Iub DS transport load)
X
Condition
Triggering events for Rate control:
DL power color change
DL Tx code power consumption criteria:
NBAP event A: the rate needs to be decreased because of
too much DL power consumption
NBAP event B: the rate may be increased

Iub load criteria
AS Iub color change because one Iub instance part of the
AS becomes loaded
Intra RNC inter-frequency HO: the Iub instance color
related to the target cell is different from AS Iub of the
source AS cell
Soft handover: AS Iub color change due to the addition /
deletion of an Iub instance, which supports the added /
deleted radio link

Measurement Result
Measurement Type Screening per reason:
DlPowerLoad (0): AMR rate control based on total DL Tx power consumption
DlTxCodePower (1): AMR rate control based on DL Tx code power
consumption
IubDsLoad (2): AMR rate control for Iub DS transport load reason

Measurement Object
Instance
3GPP compliance
Comments
objectives
Temporal aggregation rule see Performance Management Access Network Observation Counters -
Volume 1 : CNode Counters customer documentation
GQM metric Identifier of the related GQM metric

Measurement Name NT_Rnc_Initiated_Amr_Nb_UL_Rate_Control (1536)
3GPP name (itf-N) VS.RncInitiatedAmrNbUlRateCtrl
Description Number of time an AMR-NB UL rate has changed due to UTRAN specific
criteria (i.e. UL Cell load color change or Iub DS transport load state change)
X
Condition Triggering events for Rate control:
UL Cell load color change
Iub load criteria :
AS Iub color change because one Iub instance part of the

AS becomes loaded
Intra RNC inter-frequency HO: the Iub instance color
related to the target cell is different from AS Iub of the
source AS cell
Soft handover: AS Iub color change due to the addition /
deletion of an Iub instance, which supports the added /
deleted radio link
Measurement Result
UlCellLoad (0): AMR rate control based on UL Cell Load

Measurement Object
Instance
3GPP compliance
Comments
objectives

Measurement Name NT_Cn_Initiated_Amr_Nb_UL_Rate_Control (1537)
3GPP name (itf-N) VS.CnInitiatedAmrNbUlRateCtrl
Description Number of CN initiated rate controls
X
Condition
Measurement Result
UlCellLoad (0): AMR rate control based on UL Cell Load

Measurement Object
Instance
3GPP compliance
Comments
objectives

Measurement Name NT_Amr_Nb_Initial_Max_Rate (1680)
3GPP name (itf-N) VS.AmrNbInitialMaxRate
Description Number of time an AMRNB rate is selected as the max allowed rate at call
setup time. This counter heps to provide some statistics on the initial AMR-NB
max rate selected at admission time
X
Condition Max AMR rate indicated in the Iu UP Initialization message
Measurement Result
AMR_12.2 (0): 12.2,
AMR_10.2 (1): 10.2,
AMR_7.95 (2): 7.95,
AMR_7.4(3): 7.4,
AMR_6.7 (4): 6.7,
AMR_5.9 (5): 5.9,
AMR_4.75 (7): 4.75

Measurement Object FddCell (reference cell)

Instance
3GPP compliance
Comments
objectives


Measurement Name VS_AmrRateReconfig_5p9_Att (2682)
3GPP name (itf-N) VS.AmrRateReconfig5p9.Att
Description Number of voice RB Reconfiguration attempts from AMR5.9 to AMR12.2 due
to PS RAB addition
X
Condition PS RAB Assignment Request message received for an UE which has an
active voice call with a AMR configuration without appropriate multi-service
support. Pegged on the FDDcell MO representing the reference cell on the
serving RNC.
Measurement Result
Measurement Type
Measurement Object
Instance
3GPP compliance
Comments
objectives

Measurement Name VS_AmrRateReconfig_5p9_Att_NeighbRnc (2683)
3GPP name (itf-N) VS.AmrRateReconfig5p9.Att.NeighbRnc
Description Number of voice RB Reconfiguration attempts from AMR5.9 to AMR12.2 due
to PS RAB addition
X
Condition PS RAB Assignment Request message received for an UE which has an
active voice call with a AMR configuration without appropriate multi-service
support. Pegged on the Neighbouring RNC MO the reference cell is on in case
the reference cell is on the drift RNC.
Measurement Result
Measurement Type
Measurement Object
Instance
Neighbouring RNC
3GPP compliance
Comments
objectives

Measurement Name VS_AmrRateReconfig_5p9_Succ (2684)
3GPP name (itf-N) VS.AmrRateReconfig5p9.Succ
Description Number of successful voice RB Reconfigurations from AMR5.9 to AMR12.2

due to PS RAB addition
X
Condition Reception of a Radio Bearer Reconfiguration Complete in the context of an
AMR monorate reconfiguration to AMR12.2. Pegged on the FDDcell MO
representing the reference cell on the serving RNC.
Measurement Result
Measurement Type
Measurement Object
Instance
3GPP compliance
Comments
objectives

Measurement Name VS_AmrRateReconfig_5p9_Succ_NeighbRnc (2685)
3GPP name (itf-N) VS.AmrRateReconfig5p9.Succ.NeigbRnc
Description Number of successful voice RB Reconfigurations from AMR5.9 to AMR12.2
due to PS RAB addition
X
Condition Reception of a Radio Bearer Reconfiguration Complete in the context of an
AMR monorate reconfiguration to AMR12.2. Pegged on the NeighbouringRnc
MO the reference cell is on in case the reference cell is on the drift RNC.
Measurement Result
Measurement Type
Measurement Object
Instance
Neigbouring RNC
3GPP compliance
Comments
objectives

Measurement Name VS_RAB_Drop_CS_CodecChange (2686)
3GPP name (itf-N) VS.RAB.Drop.CS.CodecChange
Description Dropped CS RAB connections during AMR codec change due to unsuccessful
termination of the Iu Rate Control procedure.
X
Condition Pegged for each dropped CS RAB, when the SRNC invokes RANAP Iu
Release Request procedure due to Nrc (refer to 3GPP 25.415) times
unsuccessful termination of the Iu Rate control procedure.
Measurement Result
Measurement Type
Measurement Object
Instance
3GPP compliance
Comments
objectives


Measurement Name VS_RAB_Drop_CS_CodecChange_NeighbRnc (2687)
3GPP name (itf-N) VS.RAB.Drop.CS.CodecChange.NeighbRnc
Description Dropped CS RAB connections during AMR codec change due to unsuccessful
termination of the Iu Rate Control procedure.
X
Condition Pegged for each dropped CS RAB, when the SRNC invokes RANAP Iu
Release Request procedure due to Nrc (refer to 3GPP 25.415) times
unsuccessful termination of the Iu Rate control procedure.
Pegged on the NeighbouringRnc MO the reference cell is on in case the
reference cell is on the drift RNC.
Measurement Result
Measurement Type
Measurement Object
Instance
Neighbouring RNC
3GPP compliance
Comments
objectives

7.3.2 METRICS

7.3.3 TRACES

7.3.3.1 FEATURE 30229
No impact.

7.3.3.2 FEATURE 18717
7.3.3.2.1 FUNCTION RRC
7.3.3.2.1.1 SUBFUNCTION RRC DEDICATED TRAFFIC
The following additional messages are traceable:
TRANSPORT FORMAT COMBINATION CONTROL
This message is traceable only when send over SRB#2.
TRANSPORT FORMAT COMBINATION CONTROL FAILURE
Only the ASN.1 trace mode is available, no additional data is provided.


7.3.3.2.2 NEW FUNCTION RRC USER PLANE
7.3.3.2.2.1 SUBFUNCTION RRC_TFC_CONTROL
Traceability
The following table shows which trace session type can trace this sub-function.
Call Trace Session Available
Call Trace - CTa_trace_invoke no
Call Trace - CTa_emergency_call no
Call Trace - CTa_call_failure no
Call Trace - CTb yes
Call Trace - CTg yes
Object Trace - Cell no
Object Trace - Iu CS no
Object Trace - Iu PS no
Object Trace - Iur no
Object Trace - RNC no

Context-Full Trace Data
The data types traced are as follows:
Data type Description Event name
RRC_TFC_Control

see below
Indicates which transport format
combinations in the already
defined UL Transport Format
Combination Set are currently
allowed.
TRACE_EVENT_TFC_Control

TFC_Control
The TFC_Control data block definition is the following:
Data XDR type Description Value range
TFC_Subset u_int Identity of the currently used
Transport Format
Combination Subset
0-7

7.3.3.3 FEATURE 27803
No additional traces required.

7.3.3.4 FEATURE 33863

7.3.3.5 FEATURE 32687

7.3.3.6 FEATURE 34216

7.4 MISCELLANEOUS
7.4.1 STATIC DATA
Not applicable

7.4.2 INVENTORY

Not applicable

7.4.3 ACTION

Not applicable

8 OAM PROCEDURES
8.1 UPGRADES

8.1.1 OAM PLATFORM UPGRADE

8.1.2 RNC & BTS UPGRADE
8.1.2.1 RNC & BTS UPGRADE TO UA05.0 [GLOBAL MARKET]

RbSetConf
At upgrade, the configuration related to UlRbSet #5, DlRbSet #5, UlRbSet #16 and
DlRbSet #19 shall always be provisioned.

UlRbSet #5 & DlRbSet #5 shall take the same values, which were provisioned for DL
CS speech 12.2 (VBR).

DlBlerQualityList
For each existing DlDynamicParameterPerDch of each existing DlRbSetConf:
Create a single instance of DlBlerQualityList
Set DlBlerQualityList / blerTarget to UA04.2 value of DlRbSetConf / dlBlerQuality.
Set DlBlerQualityList / priorityLevel to 1

BlerQualityList
For each existing DynamicParameterPerDch of each existing UlRbSetConf:
Create a single instance of BlerQualityList
Set BlerQualityList / blerTarget to UA04.2 value of UlRbSetConf / ulBlerTarget.
Set BlerQualityList / priorityLevel to 1

CacAal2InfoList
UlRbSetConf #5, DlRbSetConf #5: Instances 0 and 1 of CacAal2InfoList shall both be
created for AMR 12.2.
UlRbSetConf #16: Instance 0 of CacAal2InfoList shall be created for AMR 5.9.
UlRbSetConf #19: Instance 1 of CacAal2InfoList shall be created for AMR 4.75.
For all other UlRbSet and DlRbSet, only the instance 0 of cacAal2InfoList is created
Copy the values of qaal2EquivalentBitRate & qaal2EquivalentSSSARSDULength
parameters into the new corresponding parameters for Iu, Iub and Iur.
Set Qaal2maxBitRate to its default value.

ulRateMatchingAttributeList
For each existing DynamicParameterPerDch of each existing UlRbSetConf
Set ulRateMatchingAttributeList to UA04.2 value of UlRbSetConf /
ulRateMatchingAttribute
For modified ulRbsetConf #5, ulRateMatchingAttributeList contains 2 elements
Set to default value
For new UlRbSetConf

dlRateMatchingAttributeList
For each existing DynamicParameterPerDch of each existing DlRbSetConf
Set dlRateMatchingAttributeList to UA04.2 value of DlRbSetConf /
dlRateMatchingAttribute
For modified dlRbsetConf #5, dlRateMatchingAttributeList contains 2 elements

For new DlRbSetConf

UlTransportFormatCombinationSets
A single instance is created for all UlUserService excepted for NB AMR UlUserService
where 6 instances are created (0..5) and NB-LR AMR UlUserService where 2
instances are created (0..1).
All existing UlUserServices remain configured with signalledGainFactors.
All new or changed UlUserService are configured with ComputedGainFactor.

8.1.2.2 RNC & BTS UPGRADE FROM UA05.0 TO UA05.1 [GLOBAL
MARKET]

Below is the specification for upgrade for UA05.0 to UA05.1.
For the upgrade from UA04.2 to UA05.1: The rules must be executed
sequentially.UA04.2 to UA05.0, then UA05.0 to UA05.1.

General rules for AMR-WB: As there is only one MaxBitRate for AMR-WB, Model
aspects which are duplicated for the 2 MaxBitrates in AMR-NB and AMR-LR, are not
duplicated for AMR-WB. (CacAal2InfoList; UlTransportFormatCombinationSets;
ul/dl/RateMatchingAttributeList)
RbSetConf
At upgrade, the configuration related to UlRbSet #21, DlRbSet #31, shall always be
provisioned.

For DlRbSet #31, introduced for AMR-WB create the DlRbSet and
3 instances of DlDynamicParameterPerDch, with 3 instances each of
BlerQualityList set to default value
1 instances of CacAal2InfoList
IuCsTimingAlignement
Do not create DlRbRaTrafficMonitoring

For UlRbSet #27, introduced for AMR-WB create the UlRbSet and
3 instances of DynamicParameterPerDch, with 3 instances each of
BlerQualityList set to default value
1 instances of CacAal2InfoList
Do not create UlRbRaTrafficMonitoring

UserServices
At upgrade, the configuration related to all new Uplink and Downlink UserServices
shall always be provisioned.

For each new UlUserService create it and
o 1 ulOuterLoopPowerCtrl, and set all params to default values

o UlTransportFormatCombinationSets:
For all UlUserServices associated to AMR WB, create 2 instances
For each new instance, configure it in ComputedGainFactor Mode using
default values
* All configuration is given in excel sheet, and is on the principle of the
usage of Computed GainFactor.
* The reference TFC used is the maximum TFC defined for the
corresponding UlUserService.
* its RefTfcId is set to 0
* All other TFCs have their RefTfcId set to 0.
o Create 1 new UlUsPowerConf and set all params to default values

For each new DlUserService create it and
o Create IntraFreqTargetCellParams set all params to default values
o Create IrmSchedulingDowngradeTranscodePower/LowRbA set all params
to default values
o Create IrmSchedulingUpgrade for new instances listed below and set all
parameters to default values:
o 69 SRB 3.4 CS WB AMR PS I/B 128
o 73 SRB 3.4 CS WB AMR PS I/B 128 Mux
o 77 SRB 3.4 CS WB AMR PS STR 128
o 81 SRB 3.4 CS WB AMR PS STR 128 PS I/B 8
o 86 SRB 3.4 CS WB AMR PS STR 128 PS HS DSCH

Create 1 new DlUsPowerConf
Create dlIrmSchedDowngradeTxcp and DlIrmSchedulingUpgrade for new
instances of DlUsPowerConf listed below and set all parameters
to default values.


o Create 1 new UsHoConf
For the full subtree, for each attributes, same default value for all instances
Create Fast AlarmHardHoConf
Create SoftHoConf

Create FullEventHoConfHhoMgt
Create Create FullEventHoConfHhoMgt2D
Create Create FullEventHoConfHhoMgt2F
Create FullEventHoConfShoMgt

8.1.2.3 RNC & BTS UPGRADE FROM UA05.1 TO UA06.0 [GLOBAL
MARKET]
For the upgrade from UA05.0 to UA06.0: The rules must be executed sequentially.
UA05.0 to UA05.1, then UA05.1 to UA06.0

The feature 32687 requires a full RNS upgrade in order to support the AMR rate
control based on DL Tx CP.

Below is the specification for upgrade for UA05.1 to UA06.0
Create 1 UlIrmTableCellLoadConfClass and associated chidren *
Create 1 DlIrmTablePowerLoadConfClass and associated chidren *
Create 1 DlIrmTableIubDsLoadConfClass and associated chidren *

(*) For each attribute of the tree the default value applies

For the Upgrade to UA06.0 the MO DLCodeiRMTable and all associated Children
needs to be created.

8.2 INSTALLATION & COMMISSIONING PROCEDURES
Not applicable

8.3 MAINTENANCE
Not applicable

8.4 OPERATION
Not applicable

8.5 EXTENSION
Not applicable


8.6 TECHNICAL ASSISTANCE SUPPORT
Not applicable

8.7 STABILITY DATA ANALYSER
Not applicable

9 FIELD INTRODUCTION
9.1 HARDWARE CONSTRAINTS
No specific constraints.

9.2 SPARE PART CONSTRAINTS
No specific constraints.


9.3 INTER RNS VERSION INTERWORKING
9.3.1 FEATURES 30229, 18717
Refer to section 5.4.1.
9.3.2 FEATURE 27803
Refer to section 5.4.2.

9.3.3 FEATURE 32687
Refer to section 5.4.3

9.4 CORE NETWORK INTERWORKING
The ALCATEL-LUCENT RNC is able to inter-work with a CN based on 3GPP R6 or
earlier specs.

Refer to section 5.3.1 for other cases.

9.5 UE INTERWORKING

Some UEs (e.g. 3GPP R99 based UEs) do no support the SRB#5
The SRB#5 setup is controllable via the OAM parameter minUeRelForSrb5Amr
(cf. section 7.1.1.2).
Note: SRB#5 is no longer supported in UA06.

9.6 GERAN INTERWORKING
Not applicable


10 TOOLS IMPACTS

Impact y/n Comments (tool identifier, )
Maintenance tools N
Engineering tools N
Validation tools N

11 RESTRICTIONS
The support of the SRB#5 is in restriction (not tested)


12 ABBREVIATIONS AND DEFINITIONS
12.1 ABBREVIATIONS

ACS Active Codec Set
ATM Asynchronous Transfer Mode
CAS Component Administration System
CC Cumulative Counter [R5]
CCTrCH Coded Composite Transport Channel
CCCH Common Control Channel
CDL Component Definition Language used in Passport
ChR Channel Readiness
CM Configuration Management
CM XML Configuration Management XML
CN Core Network
CuR Customer Readiness
DER Discrete Event Registration [R5]
DRNC Drift RNC
DRNS Drift RNS
DRX Discontinuous Reception
DS Delay Sensitive
DS1 Digital Signal level 1 (1.544 Mbit/s)
E1 Standard European PCM link (2.048 Mbit/s)
EBR Equivalent Bit Rate
FRS Feature Requirements Specification
GPO General Permanent Observation
IP Internet Protocol
Itf-R OMC-RNC Interface
KPI Key Performance Indicator
NBAP Node B Application Part
NDS Non Delay Sensitive
NB Narrowband
NE Network Element (RNC or BTS)
NRP Network Reconfiguration Procedure
OAM Operation, Administration and Maintenance
OC3 Optical carrier-3 (155.52 Mbit/s)
OCAN Offline Configuration of Access Networks
PDH Plesiochronous Digital Hierarchy
PWI Preside for Wireless Internet
RAN Radio Access Network
RANAP Radio Access Network Application Part
RNC Radio Network Controller
RNS Radio network subsystem
RNSAP Radio network subsystem Application part
RQMS Reliability and Quality Measurements for Telecommunications Systems
RRC Radio Resource Control
RTO Real Time Observation
RB Radio Bearer
RDN Relative Distinguish Name
RDNID Relative Distinguish Name Identifier
RNC Radio Resource Control
RNS Radio network subsystem

SAS Standalone SMLC
SDH Synchronous Digital Hierarchy
SI Status Inspection
SONET Synchronous Optical Network
SRNC Serving RNC
SRNS Serving RNS
STM1 Synchronous Transport Module-1 (155.52 Mbit/s)
SRB Signaling Radio Bearer
TB Transport Block
TBS Transport Block Set
TCTF Target Channel Type Field (MAC header field)
TF Transport Format
TFC Transport Format Combination
TFS Transport Format Set
TFCS Transport Format Combination Set
TIL Terminal d'Installation Locale (Local I&C terminal)
TML Terminal de maintenance Locale (Local Maintenance Terminal)
TR Technical Report
TrCH Transport Channel
TS Technical Specification [R5]
TTI Transmission Timing Interval
UE User Equipment
UTRAN Universal Terrestrial Radio Access Network
VS Vendor Specific
WB Wideband
W-NMS Wireless Network Management System (aka PWI)
XML eXtended Markup Language

12.2 DEFINITIONS

12.2.1 ALCATEL-LUCENT SPECIFIC DEFINITIONS
12.2.1.1 OAM PARAMETERS
Class 0: the parameter cannot be modified and a new object instance must be
created or recreated with the requested value thanks to build process or on line
creation command.
Class 2: the object instance (or the parent object instance) must be locked to modify
the parameter and the modification will be taken into account after the object instance
(or the parent object instance) has been unlocked.
Class 3: the parameter can be changed on-line without impact on the service. The
new value is taken into account either immediately or for new calls only.
Class 3-A1 new value immediately taken into account.
Class 3-A2 new value taken into account upon event reception (service
establishment, SRLR, for instance...).
Class 3-B new value taken into account for next calls.

Operator: the parameter is configurable from the OMC and seen by the operator
Manufacturer: the parameter is configurable from the OMC and only seen by Alcatel-
Lucent engineering teams

Default value: This value is used
- Either when a System release upgrade occurs and the value of a new parameter is
["false"] or ["null"] or [x] in order to ensure the same performance before upgrades
- Or when a customer wants to deactivate a function.

Recommended value: This value is recommended by Alcatel-Lucent Network for new
networks roll out before the optimization. The recommended values take benefit of the
performance of Alcatel-Lucent Network UTRAN feature.
For installed networks, the value to set depends on the chosen options or rules
defined by the customer.

12.2.1.2 CALL TRACE
Trace session: Call Trace activity in the UTRAN may only exist during and within the
frame of trace sessions. At a given time, an existing trace session may be active or
not. An active trace session corresponds to the activity of Call Trace processes both in
the OMC and in the involved Network Elements (NEs): generation of trace records
and log in trace files (NE activity), upload of trace files (NE & OMC activity). The type
of Call Trace, the nature of data traced, the involved NEs are specified in the Call
Trace creation command. Types of Call trace session:
Cta session (Core Network invoked Call trace): It allows tracing, one or
several UE calls. Invocation is controlled via RANAP signaling.
Ctb session (Access invoked Call trace): It allows only one UE to be traced at
a time. Invocation is controlled via the OMC-R.
Ctg session (Geographical Call trace): It allows tracing UEs, which have
established a call within a geographical area specified in the Trace Session
creation command.
Object tracing session: It may be invoked for a variety of tracing targets (e.g.
cell, Iu, Iur, RNC). Invocation is controlled via the OMC-R.
Trace modes: Records provided by the NE(s) may be presented according three
different Trace modes:
Mode 1 or Event only, providing a mere header including in particular: the
traced sub-function, a record name, a time-stamp, the related cell Id (if
relevant), the related RNC Id.
Mode 2 or ASN.1, providing the header plus the rest of the record
information, coded in ASN.1; mode 2 applies only to UTRAN protocols PDUs.
Mode 3 or ctx_full, providing the header plus a complete specific structure
build by the Call processing application for Call Trace needs.

12.2.2 AMR SPECIFIC DEFINITIONS
Narrowband AMR codec

The narrowband AMR speech codec is a multi-rate speech codec with eight source
rates from 4.75 kbps to 12.2 kbps and the capability to switch rate every 20 ms (in
UMTS), plus a low rate background noise encoding mode designed to take advantage
of speech inactivity. The last mechanism is specified as Source Controlled Rate and
also known as VAD/DTX.
Refer to 3GPP TS 26.103 [R13] for more information.

Wideband AMR codec
The wideband AMR speech codec is a multi-rate speech codec with up to 4 source
rates from 6.60 kbps to 23.85 kbps and the capability to switch rate every 20 ms, plus
a low rate background noise encoding mode designed to take advantage of speech
inactivity. The last mechanism is specified as Source Controlled Rate and also known
as VAD/DTX.

Transcoder Free Operation (TrFO)
TrFO relies on Out of Band Transcoder Control which is a capability of R4 Bearer-
independent circuit-switched core network (BICN) architecture. At call setup the
involved MSC(s) perform codec negotiation in order to insert a pair of transcoders only
when necessary. The MSCs may also insert/remove the transcoders during the call
e.g. at relocation.
The negotiation results in a codec type selected (e.g. AMR) and a set of codec modes
(rates) called Active Codec Set (ACS). The ACS is the same for uplink and downlink.
TrFO is a UMTS specific feature i.e. it is not applicable to a UMTS to GSM call.
From RAN perspective, in case of TrFO, Iu UP appears to be terminated in the peer
RAN since the CN is transparent to the Iu UP control messages such as rate control

Tandem Free Operation (TFO)
TFO is based on inband signalling between transcoders after call setup. Transcoders
supporting TFO are able to compare codec types and modes at both ends, and to
switch off the transcoding function. When the codecs are not compatible, the network
may have the capability to change the codec(s) in order to resolve the mismatch. This
would result in a RAB modification.
TFO is applicable to UMTS to UMTS calls and to UMTS to GSM calls as well.
From RNC perspective, in case of TFO, Iu UP appears to be terminated in the peer
RNC (UMTS to UMTS) or TRAU (UMTS to GSM).

12.2.3 OTHER 3GPP DEFINITIONS


13 ANNEX A.
This annex is optional for additional information.
END OF DOCUMENT

UMT SYS DD 018824 V03.06 en - AMR CS Speech Service Support - UMTS Access Standard

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

UMT SYS DD 018824 V03.06 en - AMR CS Speech Service Support - UMTS Access Standard

Transféré par

Droits d'auteur :

Formats disponibles

AMR CS speech service support - UMTS Access

Document number: UMT/SYS/DD/018824

2007 Alcatel-Lucent, All Rights Reserved

Vous aimerez peut-être aussi