AMR Full Rate Vs Half Rate

GSM
Reference : Version : Date : PE/SYS/DD/000343 01.11 / EN 12/05/04
SV713 : AMR FULL RATE; SV885 AMR HALF RATE
This confidential document is the property of NORTEL MATRA CELLULAR and may not be copied or circulated without permission Ce document confidentiel est la proprit de NORTEL MATRA CELLULAR et ne peut tre reproduit ou communiqu sans autorisation
TABLE OF CONTENTS
0. 1. SUMMARY .................................................................................................................................................................. 6 INTRODUCTION........................................................................................................................................................ 6 1.1 1.2 2. 2.1 2.2 3. 3.1 3.2 4. OBJECT................................................................................................................................................................ 6 SCOPE.................................................................................................................................................................. 7 APPLICABLE DOCUMENTS ...................................................................................................................................... 8 REFERENCE DOCUMENTS ....................................................................................................................................... 8 ABBREVIATIONS............................................................................................................................................... 9 DEFINITIONS ................................................................................................................................................... 10
RELATED DOCUMENTS.......................................................................................................................................... 8
ABBREVIATIONS AND DEFINITIONS ................................................................................................................. 9
BENEFITS .................................................................................................................................................................. 12 4.1 CUSTOMER/SERVICE PROVIDER BENEFITS ............................................................................................................ 12 4.1.1 AMR FR ......................................................................................................................................................... 12 4.1.2 AMR HR ......................................................................................................................................................... 13 4.1.3 BSS capacity................................................................................................................................................... 14
4.1.3.1 4.1.3.2 4.1.3.3 Abis PCM...............................................................................................................................................................14 BSC e3 capacity.....................................................................................................................................................14 TCU e3 capacity ....................................................................................................................................................14
4.2 5.
END-USER/SUBSCRIBER BENEFITS .................................................................................................................... 15
FUNCTIONAL DESCRIPTION .............................................................................................................................. 17 5.1 PRINCIPLE ............................................................................................................................................................ 17 5.1.1 Basics and specific terminology..................................................................................................................... 17 5.1.2 AMR mechanisms........................................................................................................................................... 20
5.1.2.1 5.1.2.1.1 5.1.2.1.2 5.1.2.2 5.1.2.2.1 5.1.2.2.2 5.1.2.2.3 5.1.2.2.4 5.1.2.2.5 5.1.2.3 5.1.2.4 5.1.2.5 AMR codec sets .....................................................................................................................................................20 FR AMR ...........................................................................................................................................................21 HR AMR...........................................................................................................................................................22 Codec mode adaptation ..........................................................................................................................................22 Principle............................................................................................................................................................22 Downlink requested codec mode ......................................................................................................................23 Uplink requested codec mode ...........................................................................................................................23 Downlink codec mode modification according to uplink path .........................................................................24 Parameters ........................................................................................................................................................24 RATSCCH management ........................................................................................................................................25 CMI/CMR inversion ..............................................................................................................................................26 Pre-handover ..........................................................................................................................................................26 Channel allocation .................................................................................................................................................27 General .............................................................................................................................................................27 Flag management..............................................................................................................................................28 Channel type management................................................................................................................................29 Radio allocator..................................................................................................................................................33 Channel Release.....................................................................................................................................................34 Abis and switching matrix management ................................................................................................................34 Ater management ...................................................................................................................................................36 Assignment or incoming inter-BSC Handover .................................................................................................36 Intra-BSC Handover .........................................................................................................................................36 Mode Modify ....................................................................................................................................................37
5.1.3
TMG mechanisms........................................................................................................................................... 27
5.1.3.1 5.1.3.1.1 5.1.3.1.2 5.1.3.1.3 5.1.3.1.4 5.1.3.2 5.1.3.3 5.1.3.4 5.1.3.4.1 5.1.3.4.2 5.1.3.4.3
5.1.4
L1m ................................................................................................................................................................ 37
SV713 : AMR Full Rate; SV885 AMR Half Rate PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 2/110
5.1.4.1 12.2 and 7.4 codec mode false activation...............................................................................................................38 5.1.4.2 Power control .........................................................................................................................................................39 5.1.4.2.1 Uplink Power control........................................................................................................................................40 5.1.4.2.2 Downlink Power control ...................................................................................................................................40 5.1.4.3 Handover mechanisms ...........................................................................................................................................42 5.1.4.3.1 Principle............................................................................................................................................................42 5.1.4.3.2 Alarm inter-cell handover................................................................................................................................43 5.1.4.3.3 Intra-cell handover............................................................................................................................................44 5.1.4.3.4 Handover AMR FR -> AMR HR......................................................................................................................45 5.1.4.3.5 Handover HR -> FR..........................................................................................................................................45 5.1.4.3.6 Direct half rate TCH allocation ........................................................................................................................46 5.1.4.3.7 Inter-zone handover ..........................................................................................................................................47 5.1.4.3.8 Handover priority..............................................................................................................................................47 5.1.4.3.9 AMR L1m deactivation ....................................................................................................................................47 5.1.4.3.10 Summary...........................................................................................................................................................49
HO decision.................................................................................................................................................................. 49 Direct HR TCH allocation ........................................................................................................................................... 49 5.2 FEATURE INTERWORKING .................................................................................................................................... 52 5.2.1 Radio allocator from V7 ................................................................................................................................ 52 5.2.2 VAD / DTX ..................................................................................................................................................... 52 5.2.3 Queuing / priority 0 ....................................................................................................................................... 52 5.2.4 Handover for traffic reason and dynamic access class baring...................................................................... 53 5.2.5 Circuit switch data channel ........................................................................................................................... 53 5.2.6 TCH Signaling ............................................................................................................................................... 53 5.2.7 Automatic Cell tiering.................................................................................................................................... 54 5.2.8 General protection against HO ping pong .................................................................................................... 54 5.2.9 CM1170 HW/SW compatibility ...................................................................................................................... 54 5.2.10 Handover EFR/FR AMR ...................................................................................................................... 55 5.2.11 GSM/GPRS TS sharing ............................................................................................................................. 55 5.2.12 ASCI features ............................................................................................................................................ 55 5.2.13 Get Channel State ..................................................................................................................................... 56 5.3 OPERATION .......................................................................................................................................................... 56 5.4 PERFORMANCES................................................................................................................................................... 56 5.4.1 HR AMR capacity .......................................................................................................................................... 56 5.4.2 BSC e3 capacity ............................................................................................................................................. 58
5.4.2.1 5.4.2.2 5.4.2.3 HR AMR................................................................................................................................................................58 CPU........................................................................................................................................................................58 BSC Memory and OMC-R BSC link ..................................................................................................................59
5.4.3 5.4.4 5.4.5 5.4.6 5.4.7 6.
OMC-R capacity ............................................................................................................................................ 59 TDMA configuration ...................................................................................................................................... 59 Lapd capacity................................................................................................................................................. 60 AMR HR FR interworking........................................................................................................................... 61 Call setup time ............................................................................................................................................... 61
INTERFACES ............................................................................................................................................................ 62 6.1 GSM INTERFACES................................................................................................................................................ 62 6.1.1 AIR interface .................................................................................................................................................. 62

6.1.1.1 6.1.1.2 Messages for Radio Resources management .........................................................................................................62 Messages for RATSCCH management ..................................................................................................................63
6.1.2 6.1.3
A interface...................................................................................................................................................... 63 Abis interface ................................................................................................................................................. 65
6.1.3.1 ABIS OML messages.............................................................................................................................................65 6.1.3.2 ABIS RSL messages ..............................................................................................................................................66 6.1.3.2.1 Modified messages ...........................................................................................................................................66 6.1.3.2.2 New messages...................................................................................................................................................73
6.1.4
Ater interface ................................................................................................................................................. 77

Ater OML messages...............................................................................................................................................77
6.1.4.1
Page 3/110
6.1.4.2 6.1.4.3
Ater RSL messages ................................................................................................................................................78 TRAU frames format .............................................................................................................................................78 Agprs RSL messages..............................................................................................................................................79 Agprs GSL messages .............................................................................................................................................79 Agprs OML messages ............................................................................................................................................79
6.1.5
AGPRS Interface ............................................................................................................................................ 79
6.1.5.1 6.1.5.2 6.1.5.3
6.1.6 Gb Interface ................................................................................................................................................... 80 6.2 O&M INTERFACES ............................................................................................................................................... 81 6.2.1 External Manager (Q3 interface)................................................................................................................... 81
6.2.1.1 6.2.1.2 6.2.1.3 6.2.1.4 6.2.1.5 6.2.1.6 6.2.1.7 Data Model ............................................................................................................................................................81 Alarms & notifications...........................................................................................................................................84 Counters .................................................................................................................................................................84 TMG counters ........................................................................................................................................................85 L1m counters .........................................................................................................................................................88 AMR counters........................................................................................................................................................90 Existing counters....................................................................................................................................................91 Data Model ............................................................................................................................................................95 Alarms & notifications...........................................................................................................................................98 Counters .................................................................................................................................................................98 Miscellaneous ........................................................................................................................................................98
6.2.2
Local Manager (man Machine Interface) ...................................................................................................... 95
6.2.2.1 6.2.2.2 6.2.2.3 6.2.2.4
6.2.3 SDO................................................................................................................................................................ 99 6.3 TRANSMISSION NETWORK INTERFACES ................................................................................................................ 99 6.3.1 PCM ............................................................................................................................................................... 99 6.3.2 Ethernet.......................................................................................................................................................... 99 6.3.3 X25 ................................................................................................................................................................. 99 7. O&M PROCEDURES ............................................................................................................................................. 100 7.1 7.1.1 7.1.2 7.2 7.3 7.4 7.4.1 7.5 7.6 8. 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.7.1 8.7.2 8.7.3 8.7.4 8.7.5 8.7.6 9. 9.1 9.2 UPGRADES ......................................................................................................................................................... 100 OMC-R Upgrade.......................................................................................................................................... 100 BSC, TCU & BTS upgrade........................................................................................................................... 100 INSTALLATION AND COMMISSIONING ................................................................................................................ 100 MAINTENANCE .................................................................................................................................................. 101 OPERATION ........................................................................................................................................................ 101 NRP .............................................................................................................................................................. 101 EXTENSION ........................................................................................................................................................ 101 TECHNICAL ASSISTANCE SUPPORT .................................................................................................................... 101 HARDWARE CONSTRAINTS ................................................................................................................................. 102 SPARES CONSTRAINTS........................................................................................................................................ 102 BSS VERSION INTERWORKING ........................................................................................................................... 102 NSS INTERWORKING.......................................................................................................................................... 102 SGSN INTERWORKING ....................................................................................................................................... 102 FUNCTION INTERWORKING ................................................................................................................................ 102 ENGINEERING RULES ......................................................................................................................................... 103 Power Control Algorithm............................................................................................................................. 103 DIRECT HR TCH Allocation....................................................................................................................... 103 HANDOVERs............................................................................................................................................... 104 TDMA Priority ............................................................................................................................................. 107 LAPD DIMENSIONNING............................................................................................................................ 107 SDCCH DIMENSIONNING ........................................................................................................................ 107 OMC-R ............................................................................................................................................................. 108 BSC 12000 ......................................................................................................................................................... 108
FIELD INTRODUCTION....................................................................................................................................... 102
SUB SYSTEMS IMPACTS ..................................................................................................................................... 108
Page 4/110
9.3 9.4 9.5 9.6 9.7 9.8
BSC E3 .............................................................................................................................................................. 108 BTS .................................................................................................................................................................... 109 TCU 2G .............................................................................................................................................................. 109 TCU E3 ............................................................................................................................................................... 109 PCUSN ............................................................................................................................................................. 109 TOOLS ................................................................................................................................................................ 110
Page 5/110
0. SUMMARY
Nortel BSS has evolved to introduce sophisticated traffic management features dealing with call quality management and capacity improvements. This feature manages AMR services, which allow high gains and good trade-off between these 2 objectives.
1. INTRODUCTION
1.1 OBJECT
The aim of this feature is to introduce AMR management in the Nortel BSS, in order to : increase voice quality in degraded radio conditions, due to the adaptation of the pair {source, channel} to the radio channel quality. increase radio capacity due to robustness of FR AMR and introduction half rate channels. AMR introduction induces creations or modifications of following algorithms in the BSS : AMR management : AMR vocoders, dedicated VAD/DTX, link adaptation mechanisms, RATSCCH channel and TRAU frames, L1m mechanisms : adaptation of current mechanisms (power control and handover) to the intrinsic quality of AMR channel, TMG mechanisms : allocation and management of AMR channels and specially half rate channels.
Page 6/110
1.2
SCOPE
This feature will be implemented in V14 release. The feature is applicable to the following sub-systems: Sub systems BSC 12000 BSC 6000 BSC e3 PCUSN TCU-TCB1 TCU-TCB2 TCU e3 S4000/S2000E-DCU2 S4000/S2000E -DCU4 S4000/S2000E-DCU2/DCU4 S8000-BCF S8000-CBCF S2000L/H e-cell iBTS OMC-R
Y/N/I N* N Y I N N Y N Y N Y Y Y Y N Y
* This feature is not implemented on BSC12000, but has some impacts on it (see section 9.2 for more details).
Page 7/110
2. RELATED DOCUMENTS
2.1 APPLICABLE DOCUMENTS
[A1] [A2] [A3] [A4] [A5] [A6] [A7] [A8] [A9] PE/SYS/DD/0303 PE/SYS/DD/0304 PE/SYS/DD/0321 PE/SYS/DD/0279 PE/BTS/DD/1514 PE/SYS/DD/0291 PE/SYS/DD/0272 PE/SYS/DD/0330 PE/SYS/DD/0331 TF1121 : GSM/GPRS TSs Dynamic sharing HO Priority Management enhancement :TF1141 CM1170 : HW/SW compatibility TF995 : Automatic Cell tiering SFS of layer 1 management TF821 : General protection against HO ping pong TF875 : Dual band cell 1 BCCH TF1216 : Automatic handover adaptation TF1217 : Protection against intra-cell HO Ping-pong
2.2
REFERENCE DOCUMENTS
[R1] [R2] [R3] [R4] [R5] [R6] [R7] [R8] [R9] [R10] [R11] [R12] [R13] [R14] 04.08 Mobile radio interface layer 3 specification 05.09 Link Adaptation 06.71 Adaptive Multi-Rate (AMR) speech processing functions; General description 06.73 Adaptive Multi Rate (AMR) Speech; ANSI-C code for the AMR speech codec 06.90 Adaptive Multi-Rate (AMR) speech transcoding 06.91 Substituting and muting of lost frames for Adaptive Multi-Rate (AMR) speech traffic channels 06.92 Comfort noise aspects for Adaptive Multi-Rate (AMR) speech traffic channels 06.93 Discontinuous Transmission (DTX) for Adaptive Multi-Rate (AMR) speech traffic channels 06.94 Voice Activity Detector (VAD) for Adaptive Multi-Rate (AMR) speech traffic channels; General description 08.08 BSS - MSC interface Layer 3 specification 08.58 Base Station Controller - Base Transceiver Station (BSC - BTS) interface 08.60 Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels 08.61 In-band control of remote transcoders and rate adaptors for half rate traffic channels 04.06 Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification
Page 8/110
3. ABBREVIATIONS AND DEFINITIONS

3.1 ABBREVIATIONS
ACS AMR BFI BFI KO C/I CMC CMI CMR DCU2 EFR Erl FER FR FR AMR HR HR AMR ICM L1m PWCI RATSCCH RFU SNR TCB TRAU TMG VAD VAF Adaptive multirate Codec mode Set Adaptative Multi-Rate Bad Frame Indicator Bad Frame Indicator KO Carrier over Interferer Codec Mode Command Codec Mode Indication Codec Mode Request Data Channel Unit 2 Enhanced Full Rate vocoder Erlang Frame Erasure rate Full Rate Full Rate AMR Half Rate Half Rate AMR Initial Codec Mode Layer one Management Potential Worst C/I Robust AMR Traffic Synchronized Control Channel Reserved for Future Used Signal to Noise ratio TransCoder Board Transcoding and Rate Adaptor Unit Traffic ManaGement Voice Activity Detection Voice Activity Factor
Page 9/110
3.2
DEFINITIONS
Multizone cell : used in order to refer following kinds of cell : concentric cell, heterogeneous coupling cell, dual-band cell. based on same following principles : radio resources are divided in two classes (i.e. zone) : inner and outer zone, allocation in each zone is done according radio criteria, L1m mechanisms are defined in order to allow handover between each zone.
outer zone inner zone
Codec mode : in following sections, codec mode is used to designate one of the 8 AMR vocoder and identified using its rate (12.2, 10.2, 7.95, 7.4, 6.7, 5.9, 5.15, 4.75) give in kbps. Speech frame : corresponds to 20 ms of speech on the radio interface and the TRAU interface. Frequency load1 : defines the load of a frequency hopping pattern and is evaluated as below : fl = Nb of hopping TRX in the cell / Nb of frequencies in the hopping law. 1*1 frequency hopping patterns1 : this frequency pattern is used in case of frequency hopping. Each hopping TRX of 1*1 cell, uses all frequencies of the frequency law :
f1,f2,f3,f4,f5
f1,f2,f3,f4,f5
f1,f2,f3,f4,f5
1 For more details, see [A4]
Page 10/110
1*3 frequency hopping patterns : this frequency pattern is used in case of frequency hopping. Each hopping TRX of 1*3 cell, uses 1/3 frequencies of the frequency law :
f1,f2
f3,f4
f5,f6
SV713 : AMR Full Rate; SV885 AMR Half Rate
Page 11/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
4. BENEFITS
4.1 CUSTOMER/SERVICE PROVIDER BENEFITS
benefit loss
Cost ownership (day to day operation, fault management, upgrade, preventive/curative maintenance....) Circuit Capacity (Erlang) Packet Capacity (GPRS) Dimensioning (Connectivity, storage capacity..) Engineering (coverage, C/I..) Traffic management (load sharing, compliance with recommendations ..) Robustness (restart/recovery enhancement..)
N Y N Y Y Y N
N Y N Y N N N
With the introduction of the data in the wireless, the increasing number of customers and the constant growth of the networks, capacity remains as one of the major concern of operators. To respond to this tremendous demand, Nortel has focused on capacity by evolving its equipment continuously. The example of BSC with the improvement from the BSC 1G to the BSC e3 illustrates perfectly this equipment evolution. In addition to this equipment evolution, some features have allowed to maximize network performances such as fractional reuse patterns (1*1, 1*3). AMR is the new feature that will provide a way to extend network capacity by : increasing the spectrum efficiency, tanks to FR AMR, increasing the TRX, thanks to HR AMR.
4.1.1 AMR FR
Regarding the EFR applied to the 1*1 fractional reuse pattern, the maximal frequency load is 20% (see [A4] for more details). AMR-FR is more robust than EFR because of the channel coding that allows to adapt and to obtain a better protection in bad propagation conditions and then to go down to inferior C/I at equivalent auditive quality. This results in a higher frequency load for AMR-FR which is equivalent to a higher number of Erl/km2/frequency. The estimation with AMR is a maximal frequency load of 28%, with the same level of voice quality. The following table gives the number of hopping TRX, according to the allocated spectrum and the type of vocoder :
Page 12/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Spectrum MHz 1*1 EFR (20%) 1*1 AMR (28%)
3 3 4
6 6 8
9 9 12
12 12 16
15 15 21
This means that speech quality is improved thanks to better robustness in AMR FR in comparison to EFR. And the capacity is increased by operating a tighter frequency reuse pattern.
4.1.2 AMR HR
AMR HR offers the possibility to have a capacity increase in term of Erlang with the quality of a FR speech. According to simulation results, following figures give the number of carried Erlang versus the percent of half rate TCH allocation, according to the number of TRX in the cell (On : one cell equipped with n TRX) :
Erlang vs HR
50.0
40.0 O1 O2 O3 O4
30.0
Erlang
20.0
10.0
0.0 0 20 40 60 % of HR allocation 80 100
Page 13/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Erlang vs HR allocation
110.0 100.0 90.0 80.0 Erlang 70.0 60.0 50.0 40.0 30.0 20.0 0 20 40 60 % of HR allocation 80 100 O5 O6 O7 O8
4.1.3 BSS CAPACITY
4.1.3.1
Abis PCM AMR Half Rate allows to double the number of calls that could be carried on a Abis PCM.
4.1.3.2
BSC e3 capacity The introduction of AMR services on BSC induces : handovers between half rate and full rate TCH, in order to adapt the radio link to radio conditions, more complex algorithm (see section Principles/ TMG mechanisms/ Channel allocation), thus the BSC load of an AMR call is greater than the load induced by a non AMR call.
4.1.3.3
TCU e3 capacity AMR services induce more complexity on TCU, so the capacity of the TCU is reduced: Codec TRM capacity EFR and FR 216 calls AMR 180 calls EFR with TTY 144 calls
Page 14/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
4.2
END-USER/SUBSCRIBER BENEFITS
Benefit Voice quality (HO, call handling enhancement ) Quality Of Service (call drop, availability..) New services
benefit loss
Y Y
A better voice quality is a strong contributor to the end user perception and a competitive differentiator for operators. This importance of voice quality is verified as long as voice represents and will represent the most important part of the traffic for some years. Nortel has constantly focused on this quality aspect to improve the service and tend to offer a wireline quality whatever the conditions are. Some existing features such as -115 dBm BTS sensivity campaign, interference cancellation algorithm feature, enhancement full rate (EFR) and others, have demonstrated excellent results. AMR offers at the same time the possibility to improve service availability at business hours by freeing channels with AMR HR, to strengthen the call by adapting the channel coding and to enhance voice quality in normal and bad radio propagation conditions. The 2 following schemes describe the quality of AMR FR and AMR HR that is evaluated on a scale from 0 to 5 in MOS (mean opinion score) depending on the radio conditions in C/I.
AMR FR performances :
MOS
5
10K2 10K2, 6K7, 10k2, 6k70, 5k90, EFR

16 13 10 7 4
C/I
Page 15/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
AMR HR performances :
MOS
5
6K7, 5K9 6K7, 5K9, 4K75 EFR
19
16
13
10
C/I
Quickly summarized, the gain of AMR in term of voice quality is : to provide up to 6 dB improvement compared to EFR in Clean Speech in Full Rate Mode to provide a wireline Quality Half Rate mode (Equivalent to EFR) down to 16 dB C/I, always significantly better than the GSM FR and GSM HR, to provide a significant improvement compared to EFR in Background Noise, to provide excellent performances in Half Rate in background Noise down to 16-13 dB C/I, equivalent to GSM FR otherwise, to provide particularly significant benefits in dynamic conditions when the Codec Adaptation is turned on: 1-2 MOS points.
Page 16/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
5. FUNCTIONAL DESCRIPTION
5.1 PRINCIPLE
In GSM, speech is transmitted on a radio channel which has a fixed raw bit rate. On this channel, speech is transmitted using a speech coder (also called source coder), which reduces the required bit rate, compared to the standard 64 Kb/s coding used in the PSTN. The coder delivers speech frames every 20 ms. From that standpoint, speech quality tends to improve when the source coder bit rate is increased, at least for a given complexity of the coder itself. On the radio segment, the speech frames as elaborated by the coder should be protected by some redundancy, which is called channel coding. The choice is then to use a high coder rate with little redundancy, or a low coder rate with more redundancy. In the first case, the speech quality will be very good in excellent radio conditions, as long as speech frames can be decoded properly. But in bad radio conditions, a high proportion of speech frames will not be decoded, in which case some interpolation will be done by the decoder, and speech quality actually drops. In the second case, speech quality will be medium or low, but will resist very well to radio channel impairments, due to the high level of redundancy. Consequently, present techniques like FR or EFR are the result of compromises between the source coder rate, and the channel coding, within the boundaries of the raw bit rate of a GSM channel. AMR techniques is Adaptive, and multirate. It means that it allows to adapt the compromise between source coder rate and channel coding/redundancy to actual radio conditions. AMR may operate in full rate channels, or half rate channels. This is called the channel type The channel type to use (TCH/FR or TCH/HR) is controlled by the network. Uplink and downlink always apply the same channel type. Basis of AMR is that within the channel (FR or HR), there is a set of voice coders, along with associated channel coding, among which the best combination can be selected to maximize speech quality according to conditions met on the radio link. This is codec mode adaptation.
5.1.1 BASICS AND SPECIFIC TERMINOLOGY
Page 17/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
For codec mode adaptation the receiving side performs link quality measurements of the incoming link. The measurements are processed yielding a Quality Indicator. For uplink adaptation, the Quality Indicator, as measured in the BTS is compared to certain thresholds and generates, also considering possible constraints from network control, a Codec Mode Command (CMC) indicating the codec mode to be used on the uplink. The Codec Mode Command is then transmitted inband to the mobile side where the incoming speech signal is encoded in the corresponding codec mode. For downlink adaptation, the DL Mode Request Generator within the mobile compares the DL Quality indicator with certain thresholds and generates a Codec Mode Request (CMR) indicating the preferred codec mode for the downlink. The Codec Mode Request is transmitted inband to the network side where it is used by the BTS, which generally grants the requested mode. However, considering possible constraints from network control, it may also override the request. The resulting codec mode is then applied for encoding of the incoming speech signal in downlink direction. Both for uplink and downlink, the presently applied codec mode is transmitted inband as Codec Mode Indication (CMI) together with the coded speech data. At the decoder, the Codec Mode Indication is decoded and applied for decoding of the received speech data. The following figure provides the AMR data flow from a "CMR, CMC and CMI" point of view and explains the CMI, CMC and CMR period.
MS CMI
20ms 40ms
BTS
CMI CMR CMC CMI CMI CMR CMC

20ms 40ms
Page 18/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
It has to be noticed, that the minimum time between 2 codec modifications is 40 ms.
TRAU
Speech encoder
speech data
BTS
channel encoder
UL Mode Command
MS
channel decoder speech decoder
DL codec mode (received)
DL codec mode
DLMode Ctrl
ULMode Ctrl
UL Quality Indicator
DLMeas.
UL Mode Command (received)
network control
DL Mode Request ( received) UL codec mode (received)
DL Quality Indicator
ULMeas.
DLReq.Gen
DL Mode Request
speech decoder
speech data
channel decoder
channel encoder
Speech encoder
AMR is introduced to choose in real time the repartition between rate of the source vocoder and channel protection :
Half Rate
Full Rate
Source coding Channel coding
Global throughput = 11.4 kbits/s
Global throughput = 22.8 kbits/s
when the transmission is good, a high rate vocoder is chosen and the number of bits dedicated to the channel protection is low, in case of degraded radio conditions, the vocoder rate is decreased, in order to provide a better channel protection and allow a better voice quality. thus the BSS provides all parameters and mechanisms, in order to manage the main aspect of this feature.
Page 19/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Linked to the AMR vocoders management, following points have to be detailed : TMG : some dedicated mechanisms have to be designed in the BSS in order to manage AMR channel, specially : allocation of a HR or a FR radio TS at the call setup, allocation of a HR or a FR radio TS for an handover, handover for (to) FR radio TS to (from) HR radio TS in order to increase the capacity or the voice quality. L1m : due to the specific quality of each AMR channel types, some dedicated L1m mechanisms are designed in order to take advantage of all possibilities of this new feature.
5.1.2 AMR MECHANISMS
5.1.2.1
AMR codec sets In the recommendations, the following coding modes are defined (in kbits/s) : AMR FR AMR HR 12.2 10.2 7.95 7.95 7.4 7.4 6.7 6.7 5.9 5.9 5.15 5.15 4.75 4.75 but due to : hardware capacity : all TRX types have to have the same AMR capacities, intrinsic quality of each codec mode in term of voice quality and functioning range, rec. limitation to 4 active codec mode at the same time, only the following coding modes are loaded in the BSS : AMR FR AMR HR 10.2 6.7 6.7 5.9 5.9 4.75 4.75
Page 20/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
The following figures show for each mode the voice quality according to C/I :
FR AMR
12k2
10k2
7k95 6k70 5k90 4k75
6dB
5dB 4dB
3dB
12dB
10dB
8dB
7dB
HR AMR
7k95 7k40 6k70 5k90 4k75
16dB
15dB
11dB
10dB
It can be noticed that this choice ensures : a good overlapping between each codec mode, an optimal voice quality, a good trade-off between stability and codec mode adaptation, NB : the functional range of one codec mode is of course not limited by one high C/I (i.e. in French : "qui peut le plus, peut le moins"). 5.1.2.1.1 FR AMR Initial codec mode : at the TCH allocation, the initial codec (ICM) mode used by the MS and the BTS is the 5.9 kbits/s.
Page 21/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
5.1.2.1.2
HR AMR Initial codec mode : at the TCH allocation, the initial codec mode (ICM) used by the MS and the BTS is the 5.9 kbits/s.
5.1.2.2 5.1.2.2.1
Codec mode adaptation Principle The purpose of AMR codec mode adaptation is to provide the "best" compromise between data rate of codec mode and channel protection, according to the link quality. This adaptation is done for uplink and downlink and there is no interdependence between the 2 links, but both sets of codec have to be identical. This adaptation is done using information exchange every 20ms, in both paths : applied codec mode : each 40ms, each entity indicates which codec mode is applied during the 2 next frames, downlink path : each 40ms, the BTS indicates which codec mode the MS has to use, uplink path: each 40ms, the MS gives a requested codec mode for the next period and the BTS internally evaluates a requested codec mode for the uplink path.
MS CMI
20ms 40ms
BTS
CMI CMR CMC CMI CMI CMR CMC

20ms 40ms
Each 40ms, according to the requested codec mode and the applied codec mode, the BTS : increases by one step the rate of the codec mode, if the requested codec mode (CMR) is greater than the applied codec mode, decreases by one step the rate of the codec mode, if the requested codec mode (CMR) is lower than the applied codec mode, keeps the same codec mode, if the requested codec mode (CMR) is equal to the applied codec mode.
Page 22/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Thus the MS gives some indications to BTS in term of requested codec mode, but the final decision is within BTS's province. A switch from one codec mode to another one, does not introduce any voice perturbation. Downlink requested codec mode For the downlink path, as described in [R2], the requested codec mode is fixed using an estimation of C/I and a set of thresholds and hysteresis :
codec mode Irate CODEC_MODE_4 THR_3 + HYST_3 = THR_MX_Up(3) THR_3 CODEC_MODE_3 THR_2 + HYST_2 = THR_MX_Up(2) THR_2 CODEC_MODE_2 THR_1 + HYST_1 = THR_MX_Up(1) CODEC_MODE_1 THR_1 = THR_MX_Dn(2) = THR_MX_Dn(3) = THR_MX_Dn(4) C/I
5.1.2.2.2
but the only recommendation requirement is to satisfy some mobile tests, thus the way to estimate the C/I criteria (specially the filter used to smooth the measurement) and the use of network parameters is mobile dependant. 5.1.2.2.3 Uplink requested codec mode In order to evaluate the requested codec mode for the uplink path, the BTS calculates for each burst, the SNR criterion which provides a good approximation of C/I. In order to have a smooth variation of this criterion, the BTS applies the following filter : (SNR )F (k ) = * (SNR)(k ) + (1 ) * (SNR )F (k 1) where is equal to : 0.05 in case of FR no frequency hopping channel and slow moving mobile, 0.1 in others cases of FR channels, 0.1 in case of HR no frequency hopping channel and slow moving mobile, 0.2 in others cases of HR channels. In case of DTX, the BTS cannot evaluate the SNR criteria, thus during the DTX period the last value of (SNR)k is taken into account and at the end of the DTX period a time exponential filter is used in order to increase the weight of the new measures and keep the same period of filtering.
Page 23/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
This filtered SNR is compared to a set of thresholds and allows determining the requested codec mode. 5.1.2.2.4 Downlink codec mode modification according to uplink path If no uplink correct frames (i.e. BFI KO and DTX not active) is received, the BTS has no way to evaluate the quality of the downlink path, thus after 10 invalid uplink frames and if the uplink CMC is equal to the minimum, the BTS decreases the applied downlink codec mode of one step each 40ms, as a precautionary action. This procedure is repeated until an uplink frame is correctly received or the 4.75 codec mode is selected for the downlink path. 5.1.2.2.5 Parameters For each mobile, the following set of parameters has to be defined : one threshold per codec mode and per link (8 in FR and 6 in HR channel), one hysteresis (the same value is used for each codec mode, but one for FR and another one for HR channel). But these parameters are linked to a set of factors, some of them being determined by the BTS (frequency hopping, MS speed), others being network dependent (environment profile). The following table is implemented in the BSS for the uplink path : <------------------Uplink BSS choice ----------------------> downlink parameters SFH 900 TU3 O&M Slow MS Fast MS - FH with < 8 FH with 8 param no FH no FH freq freq => set 11 set 12 set 13 set 14 set 15 set 21 set 22 set 23 set 24 set 25 set 31 set 32 set 33 set 34 set 35 set 41 set 42 set 43 set 44 set 45 The operator using one parameter (AMRAdaptationSet on bts object) selects the appropriate line according to the network configuration. The BSS using the TS configuration and the MS speed applies the appropriate column for the uplink path and the appropriate cell for the downlink. Thus the AMRAdaptationSet parameter takes value 0 to 3: value: 0: nominal set. This set has to be used in all nominal cases. Value 1: optimistic set. This set has to be used if the AMR FER is too low in some specific configurations. Value 2: pessimistic set. This set has to be used if the AMR FER is too high in some specific configurations. Note : due to a late change request, it is assumed now that the set of parameters provided to the MS is TU3iFH-900MHz and the MS has to adapt provided parameters according to TS configuration, MS speed. But in the
Page 24/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
previous table, for each line one set of downlink parameters is added in order to allow optimization of the downlink path. All parameters of this table are defined in the data base of the BSC, but the line 4 is settable using the "BSC data config" feature. At the channel initialization, the BSC provides the multirate configuration (the line of parameters as defined above), according to TS configuration (number of frequencies in the hopping law) : in the Channel Activation and Mode Modify messages (see [R11]) on the Abis interface to the BTS, for the uplink path, in the Assignment Command, Channel Mode Modify and Handover Command on the Air interface (see [R1]), to the MS for the downlink path. At the channel initialization, the MS speed is unknown. In case of non hopping channel, the MS is by default considered as a slow mobile. In case of non hopping channel and at each 480ms period, the BTS can modify the local set of parameters used in use, according to the MS speed. From internal studies and simulation, a mobile can be considered as a fast mobile, if the standard deviation in dB of the RxLev during one period of measurement (i.e. 104 bursts, thus 480ms) is less than 1.4. This standard deviation represents approximately : 20 km/h in GSM900, 10km/h in GSM1800 and GSM1900, and is sufficient to have a good average of the Rayleigh fading. 5.1.2.3 RATSCCH management This new channel is described in [R2] and is used in order to change the set of codec modes (see "L1m" section), and has the following main characteristics : frame stealing (1 speech frame for a FR channel, 2 speech frames for a HR channel), priority of RATSCCH frames is lower than FACCH priority, a RATSCCH message has to be acknowledged in the next 3 frames by the MS, the content of RATSCCH message is applicable 12 frames after this message, in case of failure (reception of an ACK_ERR message), a RATSCCH procedure is repeated 100 times.
Page 25/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
This procedure is used by the L1m to modify the set of codec modes (see "L1m" section for more details), for a FR channel and in case of handover failure with return on the old FR channel, in order to avoid inconsistency between the BTS and the MS (receipt of a Start Measurement Request, with a cause reestablishment). In these cases, the BTS sends the AMR_CONFIG_REQ message using the following format :
Bit Value 3432 0 0 1 31 DLF (1) 30 ULF (1) 29 28 ICM 27 20 ACS 19 18 HYSTc 17 12 THRESH3 11 6 THRESH2 50 THRESH1
In case of non-acknowledgement, the BTS repeats this message twice. If the procedure completely fails, the MS and the BTS use the previous set of codec modes. Due to a late change request, the set of codec modes has to be identical for both paths. If the RATSCCH procedure fails (no response from the MS after 2 repetitions or negative response received from the MS), the BTS increments the C1988 counter. 5.1.2.4 CMI/CMR inversion For TCH/FR, the default transmission phase shall be such that Codec Mode Indications are sent aligned with TDMA frame 0 in the uplink and with TDMA frame 4 in the downlink. For TCH/HR, the default transmission phase shall be such that Mode Indications are sent aligned with TDMA frame 0 or 1 depending on the subchannel in the uplink and with TDMA frame 4 or 5 depending on the subchannel, in the downlink. If at call setup or after a handover, the Codec Mode Indication is not aligned, an Ater procedure is engaged in order to change the default phase in downlink direction. This procedure has to be taken into account in 8 TRAU frames (thus 8*20ms) by the TCU. In case of failure, this procedure is repeated 15 times. In case of failure after 15 repetitions, the BTS stops the AMR adaptation and a counter is incremented. 5.1.2.5 Pre-handover In case of intra-cell or inter-cell handover, the adaptation mechanism has to be frozen to the ICM. For this result, the BTS has to intercept : the Assignment Command in case of intra-cell, the Handover Command in case of inter-cell handover,
Page 26/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
and to perform up to 2 codec mode adaptations, in order to activate the initial codec mode (5.9 kbits in all cases) and to stop the adaptative mechanism. This induces : an increase of around 150ms on the handover duration from the BSS point of view, a delay of around 150ms on the handover starting time from a MS point of view, but no impact for the end-user in term of voice quality (i.e. same speech gap). In case of handover failure when the MS returns on the old channel, the adaptation mechanism is restarted by the BTS at reception of the Start Measurement message.
5.1.3 TMG MECHANISMS
5.1.3.1 5.1.3.1.1
Channel allocation General TCH channel allocation is triggered by the reception of an Assignment request or a Handover request message from the MSC, or in case of an intra-BSC handover. The BSC should determine whether AMR is to be used, and select between FR or HR. This mechanism is based on proprietary algorithms, which provide to the operator a full control of the allocation. These decisions are made based on several criteria : OAM flags which indicate if the BSC, the TCU, and the cell support AMR, and strategy selected Cell load, in order to allocate a half rate channel only if the cell load is sufficient, MS capability, which is reported by the MSC in Assignment request or Handover request messages2, radio context, for instance as evaluated during the SDCCH phase.
2 This information is the result of a negotiation between the MS and the MSC during the Setup procedure (for more details see [R1] : MS MSC
--------------------------------------Setup[Bearer Cap] -------------------------- > < -----------------------------Call Proceeding [Bearer Cap] ------------------+ Assignment procedure
Page 27/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
In order to guarantee the highest capacity, if all previous conditions are fulfilled, then the BSC always tries to allocate a half rate channel. The following picture illustrates these principles:
A interface Request
If not AMR TCU / BSC / Cell capacity If AMR Cell load Cell not loaded Cell loaded Radio conditions TCH FR Bad TCH FR Good TCH HR Classic allocation
The BSC also has to control the BSS version : an AMR channel is activated only if all nodes managing the call are at least in V14. Note : in V14, if the MSC requires only AMR on half rate channel in the Channel type element, then the BSC always allocates a EFR or FR (mandatory for a standard point of view) vocoder. 5.1.3.1.2 Flag management Using following parameters : signallingPoint object : speechMode (halfRateAMR, fullRateAMR, fullrate, enhancedfullrate) attribute, This attribute enumerates speech modes allowed in the BSC. Transcoder object : coderPoolConfiguration (AMR, fullrate, enhancedfullrate) attribute, This attribute indicates enumerated speech coding algorithms supported by the TCU. Note that TCU2G does not support AMR. bts object : speechMode attribute (halfRateAMR, fullRateAMR, fullrate, enhancedfullrate) attribute, This attribute indicates enumerated speech coding algorithms supported by the cell.
Page 28/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
at reception of an Assignment Request or a Handover Request message, the BSC checks the types of channel and vocoder, which can be activated on these objects (for the G3Transcoder, a dedicated procedure is used, see "Ater management" for more details). This information is used by default, in the below algorithms. The bts speechMode attribute is a class 3 attribute and can be modified during an AMR call. In this case, the new value is taken into account at the next channel allocation. 5.1.3.1.3 Channel type management In order to select the channel type associated to the connection, the BSC uses the channel rate and type and permitted speech version information, in order to know the MS capability in term of : FR/HR management, Speech codec. But the chosen channel type is fixed according to radio criteria and some O&M parameters, and the BSS has the possibility to modify the channel type during the connection, in all cases. So at reception of the Assignment Request or Handover Request, the following mediation is done on the Channel Type octet 4 :
octet 4 value 0000 1000 0000 1001 0000 1010 Signification Full Rate TCH channel Bm. Preference between the permitted speech versions for full rate TCH as indicated in octet 5 and extensions of octet 5. Half Rate TCH channel Lm. Preference between the permitted speech versions for half rate TCH as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Full rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Half rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Full rate preferred, changes between full rate and half rate NOT allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Half rate preferred, changes between full rate and half rate NOT allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Preference between the permitted speech versions as indicated in octet 5 and extensions of octet 5, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Full or half rate TCH channel, Preference between the permitted speech versions as indicated in octet 5 and extensions of octet 5, changes between full new value 0000 1000 Request Rejected 0000 1111
0000 1011
0000 1111
0001 1010
0000 1111
0000 1011
0000 1111
0000 1111
0000 1111
0001 1111
0000 1111
Page 29/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
rate and half rate NOT allowed after first channel allocation as a result of the request.
In following sections, when the target TCH is equal to : FR TCH, the BSC always allocates a FR TCH, HR TCH, the BSC allocates a HR TCH, if AMR HR is allowed in the cell, else the BSC allocates a FR TCH. As for interworking with some old MSC releases, some mobiles does not set AMR codec at the top of the codec list, the BSC has to sort the codec list according to the following order: AMR, EFR, FR.
5.1.3.1.3.1 Cell load state
In following sections, the cell load state is used in order to choose between a FR or a HR channel. The cell load state is defined using following parameters : HRCellLoadStart on the cell object, value : 0..100. HRCellLoadEnd on the cell object, value : 0..100. In this version, this parameter has the following meaning : if HRCellLoadStart is equal to 0, then a FR radio channel is always allocated to the MS, if HRCellLoadStart is greater than 0, then a HR radio channel is allocated to the MS, according to its radio conditions. the HRCellLoadEnd is reserved for future use. For one call, the cell load state is evaluated at the first TCH allocation in the cell, thus in case of intra-cell handover, the cell load state is not reevaluated.
5.1.3.1.3.2 Assignment
In case of assignment, according to : the speechMode parameter value of the target cell (signallingPoint + TranscoderBaord+bts parameters), the cell load of the target cell, the radio conditions of the MS, the BSC selects the target Channel Type.
Page 30/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
To know the radio conditions, the BSC sends to the BTS a Connection State Request (type = current cell additional infos) and in the Connection State Ack the BTS gives the following bit map : Current cell add information element 8 7 6 5 4 3 2 1 Element identifier = 6Bh spare bits HR HR small small large zone where : "small zone" bit indicates if the small zone of the serving is eligible in case of multi-zone cell (for a normal cell, this bit is always set to 0), "HR large" bit indicates if the MS has sufficient radio conditions to manage a HR channel in the large zone of a multi-zone cell or in the whole cell of a normal cell, "HR small" bit indicates if the MS has sufficient radio conditions to manage a HR channel in the small zone of a multi-zone cell (for a normal cell, this bit is always set to 0). NB: If no measurement is available at the reception of the Connect State Request, the BTS shall wait for the first valid measurement in order to send the Connection State Ack message. Using these bits and the following priority order between channel type and zone : Priority + HR small zone HR large zone FR small zone - FR large zone the BSC selects the channel type and the zone for the MS. The way to datafill this bit map is detailed in "L1m" section.
5.1.3.1.3.3 Inter-BSC handover
In case of inter-BSC handover, according to : the speechMode parameter value of the target cell (signallingPoint + TtranscoderBaord+bts parameters), the cell load of the target cell, the Current Channel element (see [R10] for more details), the Cause element (see [R10] for more details),
Page 31/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
the BSC selects the target Channel Type : if one out of these last 2 optional A interface elements is not set in the Handover Request message, the chosen channel type is FR, if these 2 elements are present and the half rate is allowed in the target cell, then the following table is applied : Current Channel type 1 HR FR Cause uplink quality FR FR uplink strength FR FR downlink quality FR FR downlink strength FR FR Distance FR FR O&M intervention FR FR Better cell HR FR Directed retry FR FR Traffic HR FR in all other cases, a FR channel is allocated.
5.1.3.1.3.4 Intra-BSC inter-cell handover
In case of intra-BSC handover, following transitions are defined in order to determine the target channel type :
Initial Channel type Handover cause AMR quality RxLev DISTANCE PBGT TRAFFIC Forced HO Capture Directed retry HR AMR FR AMR
FR AMR FR AMR FR AMR HR AMR HR AMR FR AMR FR AMR FR AMR
FR AMR FR AMR FR AMR FR AMR FR AMR FR AMR FR AMR FR AMR
The speechMode parameter value of the target cell and the cell load are also checked in order to verify that the half rate is allowed in the cell.
5.1.3.1.3.5 Intra-cell handover
In this section intra-cell handover is used in order to refer to all kind of intra-cell handovers : normal intra-cell handover : triggered if the quality is low and the level is high, cell tiering handover : used in order to select an appropriate frequency pattern according to the PWCI criteria (see [A4] for more details),
Page 32/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
inter-zone handover : triggered in order to perform a handover from one zone to the other, in case of concentric cell, dual-band cell or heterogeneous coupling cell. In order to select the channel type, the BSC applies the following table : Handover cause original channel type target channel type normal intra-cell FR FR FR or HR FR smalllarge zone large to small FR FR or HR according zone to radio conditions* large to small HR HR** zone FR FR tiering FH no FH HR FR tiering FH no FH FR FR tiering no FH FH HR HR tiering no FH FH FR HR AMR FR HR HR FR AMR HR FR *The radio conditions are given by the BTS to the BSC using the Current Cell Add information element in the Handover Indication message. **If radio conditions are not sufficient in the small zone to manage this HR MS, the MS remains in the large one, due to the HR priority. 5.1.3.1.4 Radio allocator The radio allocator designed from V12 and activated if the radio_allocator parameter is set to " voice+data circuit + packet data" (see [A1] for more details), is improved in order to manage AMR calls. Due to intrinsic quality of FR AMR and HR AMR, 2 new parameters are created on the transceiver object, in order to give an AMR priority to each TDMA : FRAMRPriority, range : 0..2, HRAMRPriority, range : 0..2. where : priority 0 is given to a high priority TDMA, priority 1 is given to a low priority TDMA, priority 2 disables this service on the TDMA.
Page 33/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Thus according to [A1] and these new parameters, the BSC chooses the radio TS using the following order : 1. Interference level, 2. TDMA priority, 3. TDMA number (from the smallest to the biggest : 0 => n), 4. TS number (from the biggest to the smallest : TS7 => TS0). The following figure gives an example of allocation order according to :
TDMA number 0 FRAMRPriority
3 1 2 4
For more details, on the TS allocation, see [A1]. In case of HR request, the BSC applies the following rules : always fill the holes in term of free half TS (between 2 holes, the BSC uses priority rules previously defined), if there is no hole, then the BSC allocates the highest priority TS using the rules previously defined. In case of intra-cell handover, the radio allocator applies the supplementary rules: FR intracell handover: only TS belonging to the best TCH pool can be selected. FR to HR handover: all radio TS can be selected, even if the interference level is high, HR to FR handover: all radio TS can be selected, even if the interference level is high. 5.1.3.2 Channel Release In case of AMR channel release, the BTS sends in the Stop Measurement Ack, some information allowing the BSC to calculate observation counters(see "Interface/Abis interface/modified messages" section for more details). 5.1.3.3 Abis and switching matrix management On the Abis interface, half rate channels induce 8 kbps TS, instead of 16 kbps for FR channel.
Page 34/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
As the same radio TS can be used as a FR or HR channel, the associated 16 kbps Abis TS is used as one 16 kbps TS in case of FR channel and two 8 kbps TS in case of HR channel, using following rules : FR : 16 kbps, HR with T= 0 : 8 kbps (the most significant bit of the 16 kbps TS), HR with T= 1 : 8 kbps (the less significant bit of the 16 kbps TS), where T indicated the subchannel number of the Air interface (see [A1] for more details). In case of FR channel, the 16 kbps Abis TS is naturally connected to the associated 16 kbps Ater TS. In case of HR channel, the 8 kbps Abis channel is connected to the most significant bit of the 16 kbps Ater TS. The less significant bit of the 16 kbps Ater TS is not used and padded using silent pattern by the BSC, in the uplink path. For the downlink path of the Ater interface, the TCU uses always both 8 kbps whatever the channel type FR or HR (see Ater TRAU frame definition, for more details), but the BSC ignores the less significant bit and sends to the BTS the most significant one. Uplink path examples : Half rate channel T = 0 :
Ater MSB silent
BSC MSB
Abis LSB
16 kbps
16 kbps
Half rate channel T = 1 :
Ater MSB silent
BSC
Abis MSB LSB
16 kbps
16 kbps
Page 35/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
5.1.3.4 5.1.3.4.1
Ater management Assignment or incoming inter-BSC Handover At reception of an Assignment Request or a Handover Request message from the MSC, for an AMR connection and if the CIC is managed by a TCU e3, then the BSC sends a EST REQ message to the TCU containing the speech mode list and the A interface TS, in order to get an Ater TS and to know the chosen speech mode : TCU BSC < ------------ EST REQ (CIC + speech mode list) --------------------------- EST ACK (Ater TS + vocoder) -------------- > According to its capabilities, the TCU allocates the highest priority speech mode, which is used in radio TS allocation (if the speech mode is not equal to AMR, then only a FR channel can be allocated). In case of nack by the TCU due to no resource available, the connection is rejected using an Assignment Failure or Handover Failure message (cause : Requested terrestrial resource unavailable).
5.1.3.4.2
Intra-BSC Handover In case of intra-BSC handover, from (or to) a FR AMR channel to (or from) a HR AMR channel, in order to maintain the downlink voice quality, the following "Y connection" is done : the codec mode during the handover is 5.9, on the Ater interface, a 16 kbits/s TS is used, on the Abis interface a 8 or 16 kbits/s TS is used according to the channel type (HR or FR), the first 8 kbits/s of the Ater interface is used to manage 8K frame defined in [R13],
Page 36/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
the second 8 kbits/s of the Ater interface is used to manage proprietary frame, in order to ensure a "16 kbits quality" for the FR channel.
BSC Rec HR 5.9 Supp info Rec HR 5.9 FR source BTS HR target BTS
TCU Rec HR 5.9 Supp info
In case of intra-BSC handover, from (or to) an AMR cell to (or from) a non AMR cell, in order to avoid complex procedure between TCU and BSC, a standard Handover Required message is sent to the MSC, in order to execute this procedure via the A interface : MSC BSC BTS < ------------------- HO Indication----------<--------- HO Required---------------------------HO Request ---------------- > . <-------HO Request Ack --------------------------HO CMD ------------------ > <------------ HO CMP -------------------
5.1.3.4.3
Mode Modify The modification from (to) an AMR channel to (from) a non AMR channel, using a Channel Mode Modify is allowed, thus at reception of an Assignment Request message, the BSC sends a Mode Modify procedure The modification from (to) an AMR channel to (from) a data circuit channel is allowed and managed using a classic Channel Mode Modify procedure (no Ater modification is required in this case).
5.1.4 L1M
Up to V14, L1m algorithms are common for all types of dedicated channel, but due to performances of AMR channels : a FR AMR channel, specially with low codec mode, is more resistant than the normal FR channel, a HR AMR channel is more sensitive to interference than the normal FR channel. some new mechanisms dedicated for AMR channels are designed.
Page 37/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
These mechanisms are mainly based on "requested codec mode" in uplink and downlink paths, which is the best representation of the quality in this case. For this reason, RxQual criterion is not used in L1m algorithm, dealing with AMR channel. Note : in V14, only the L1m V2 introduced in V12 is available for DCU4 and DRX, in V14, only the L1m V1 is available for DCU2.. But in order to allow a smooth AMR introduction, this new AMR L1m can be deactivated, thanks a dedicated parameter. 5.1.4.1 12.2 and 7.4 codec mode false activation As seen before following codec mode sets are implemented in the BTS : AMR FR AMR HR 10.2 6.7 6.7 5.9 5.9 4.75 4.75 In AMR L1m mechanisms, the main criterion for L1m is the requested codec mode provided by the MS or the BTS. With this set of codec modes, it is impossible to detect if the quality is good or very good (in both cases the MS and the BTS provide the 10.2 or 6.7 codec mode according to the channel type). This information is needed for power control and FR->HR handover mechanisms. In order to solve this problem, for an half rate channel, a fourth codec mode (7.4) is added to the list allowing to distinguished between good and very good radio conditions. Thus the half rate codec mode set becomes : AMR HR 7.4 6.7 5.9 4.75 For a full rate channel : if the radio conditions are good for uplink and downlink, then the 12.2 kbits codec mode is configured and the 4.75 discarded allowing to distinguish between good and very good radio conditions, if the radio conditions are bad for uplink or downlink, then the 12.2 kbits codec mode is removed and the 4.75 is set back.
Page 38/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Thus the codec mode set becomes : AMR FR AMR FR downlink and downlink or uplink good uplink bad 12.2 10.2 10.2 6.7 6.7 5.9 5.9 4.75 In order to change the codec mode set, a RATSCCH message is sent to the MS (see "RATSCCH management" for more details). The following algorithm details the way of changing the codec mode set, for both paths : initial state : the active codec mode set is {12.2, 10.2, 6.7, 5.9}, if the active code mode set is {12.2, 10.2, 6.7, 5.9} and during the last 480ms period, at least one 4.75 code mode or 3 * 5.9 codec mode are requested for uplink or downlink paths, then the active codec mode set is change to {10.2, 6.7, 5.9, 4.75}, if the active code mode set is {10.2, 6.7, 5.9, 4.75} and during the last 2*480ms period, no 5.9 nor 4.75 code mode is requested for uplink and downlink paths, then the active codec mode set is change to {12.2, 10.2, 6.7, 5.9}. NB: in case of {10.2, 6.7, 5.9, 4.75} to {12.2, 10.2, 6.7, 5.9} transition, this algorithm is frozen during the 2 next measurement in order to avoid ping-pong effects, observed with some mobiles. In any case, when the BTS or the MS require the false upper codec mode (12.2 for FR and 7.4 for HR), adaptation mechanisms provide the upper codec mode (10.2 for FR and 6.7 for HR). In order to solve potential inconsistencies between MS and BTS after an intracell or inter-cell handover failure, the initial set of codec modes is resent at the MS reestablishment using a RATSCCH procedure (the BTS uses the allocation cause of the Start Measurement message to trigger the procedure). 5.1.4.2 Power control Power control algorithms are redesigned for AMR calls, in order to take into account the requested codec mode. Using the 2 following parameters (powerControl object), the operator defines the target codec mode of each channel type : HRPowerControlTargetMode : 7.4, 6.7, 5.9, 4.75, FRPowerControlTargetMode : 12.2, 10.2, 6.7, 5.9, 4.75.
Page 39/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
For the uplink path, SNR and CMR criteria are available, but the SNR is more accurate than the CMR. For the downlink path only the CMR is available. Thus the AMR power control does not apply same principles for both paths. This new power control mechanism is also controlled by the 2 classical power control parameters : bs PowerControl for the downlink path, UplinkPowerControl for the uplink path. 5.1.4.2.1 Uplink Power control For the uplink path, the criterion is the SNR, averaged on 2 measurement periods. As this mechanism shall guarantee a voice quality, the target SNR is the upper threshold of the adaptation mechanism:
SNR 12.2 target 12.2 10.2 target + hysteresis 10.2 target 10.2 6.7 target 6.7 5.9 target 5.9 4.75 target 4.75
NB: for the 12.2 (or 7.4) value, the BTS takes into account the 10.2 (or 6.7) value plus the FR (or HR) hysteresis. At each measurement period, the BTS calculates the new MS power using the following formula:
if (Filtered_SNR Target _SNR) > 0 MS_txpwr(N) = MS_txpwr(N-1) 0.7*( Filtered_SNR Target _SNR) else MS_txpwr(N) = MS_txpwr(N-1) + (Target _SNR -Filtered_SNR) + max ( 2dBm; 0,4*(Target _SNR -Filtered_SNR))
In order to protect the call against shadowing effect, the attenuation is limited by the following formula:
MS_txpwr(N) = msTxPwrMaxCnx RxLevULweight - lRxLevULPC) min(msTxPwrMaxCnx MS_txpwr(N),
5.1.4.2.2
Downlink Power control The power control principle is to :
Page 40/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
decrease the power level of one step, if the last requested codec mode of the 480ms is greater than the target codec mode, increase the power level of one step, if the last requested codec mode of the 480ms is less than the target codec mode,. The decrementation step is fixed to 2 dB. The incrementation step is fixed to 2 dB, except if the last CMR is equal to 4.75. Example with the FRPowerControlTargetMode is equal to 10.2 :
C/I 12.2 10.2 6.7 5.9 4.75
= + + +
No average is done in this case, due to the filter applied by the BTS or the MS, which gives an estimate quality for the next period. If the target codec mode is the virtual one (12.2 or 7.4), then the BTS decreases the power if the last CMR is equal to the target and increase the power in the other case. In order to protect the call against shadowing effect, the attenuation is limited by the following formula:
BS_txpwr(N) = bsTxPwrMaxCnx RxLevDLweight - lRxLevDLPC) min(bsTxPwrMaxCnx BS_txpwr(N),
If no downlink CMR is received during the measurement period (on the uplink path), the CMR is arbitrarily fixed to 4.75, in order to decrease the downlink power control attenuation and solve potential dropped calls issues.
Page 41/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
5.1.4.3
Handover mechanisms The following table describes which handover mechanisms are impacted by the AMR introduction : Handover type modified uplink and downlink quality yes uplink and downlink strength yes distance no power budget no uplink and downlink intra-cell handover yes capture no inter-zone yes directed retry no Traffic no Principle In following sections, these handovers are defined : alarm inter-cell handover, intra-cell handover for FR AMR calls, FR => HR capacity handover, HR => FR alarm handover. These 4 handovers are based on "(n,p) voting" principle, using the requested codec mode : If in the last p requested codec modes, at least n are strictly less than a target codec mode, then the condition is fulfilled. Example : if p is set to 2 SACCH periods (2*12), n is set to 10, the target codec mode is the green one, then a handover is triggered in the following example :
5.1.4.3.1
Handover decision
t
This principle applies in uplink and downlink direction independently. This mechanism is managed by the L1m and triggered at the end of each period of measurement, thus p has to be a multiple of the number of requested codec mode in one measurement period (i.e. 480 / 40 = 12). The following parameters are defined in the handOverControl object and used by these 4 handovers :
Page 42/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
pRequestedCodec : 12..192 (i.e. from 1 measurement period up to 16), nHRRequestedCodec : 1..196, used in case of HR AMR call, nFRRequestedCodec : 1..196, used in case of FR AMR call. If the n parameter is set to a value greater than the p parameter, then all associated features are deactivated. If the target codec mode is the smallest, then the associated feature is deactivated. Missing measurement management : in case of non reception of a uplink frame by the BTS due to a very low C/I, the BTS used normally the uplink measurement calculated by the BTS and the requested codec mode is replaced by : the last received one, the applied codec mode if the BTS has started to decrease the downlink codec mode as a precaution (see section " Downlink codec mode modification according to uplink path" for more details). in case of uplink DTX, a rule of three is applied on the number of received measurement, in order to reach p measurements. In the Channel Activate and Mode Modify messages, the BSC gives to the BTS, the channel type capability of the connection, using the following conditions : FRCapability = FR capability from the Channel type, HRCapability = And (cellLoadState; HR capability from the channel type). The BTS uses these capabilities, in order to filter useless Handover Indication. 5.1.4.3.2 Alarm inter-cell handover Following criteria are not used for AMR calls : uplink and downlink RxQual, and replaced by an algorithm based on "(n,p) voting" principle, using the requested codec mode. Following parameters are introduced in order to specified the target requested codec mode for FR and HR AMR channel : AMRHRIntercellCodecModeThreshold: 7.4, 6.7, 5.9, 4.75, AMRFRIntercellCodecModeThreshold : 12.2, 10.2, 6.7, 5.9, 4.75. In order to manage the eligible cell list, a new handover margin is introduced in the adjacentCellHandOver object : hoMarginAMR : -63..+63 dB. this parameter is used in order to calculate the Exp2 (this expression is used to evaluate the PBGT criteria for each cell and to classify eligible cells, see [A4] for more details).
Page 43/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Four new cause values are created in the Handover Indication message : alarm inter-cell handover for uplink criteria in case of FR channel : 13, alarm inter-cell handover for downlink criteria in case of FR channel : 14, alarm inter-cell handover for uplink criteria in case of HR channel : 15, alarm inter-cell handover for downlink criteria in case of HR channel : 16. 5.1.4.3.3 Intra-cell handover Intra-cell handover principle is to give to the mobile a better resource in term of interference, if its C/I is low, with a high C value. This principle is only applicable to FR AMR mobiles, due to interaction with HR->FR handover : in these radio conditions, it is really more efficient to allocate a FR radio TS to a HR AMR mobile, than to perform a handover from an HR TS to a HR TS. This intra-cell handover is triggered only if the intra-cell parameter of handovercontrol object is set to enabled. The following parameter is introduced on the handoverControl object, in order to specify the target requested codec mode for FR AMR channel : AMRFRIntracellCodecModeThreshold : 12.2, 10.2, 6.7, 5.9, 4.75. The minimum level to perform an AMR intra-cell handover is defined by following parameters on the handoverControl object : AMRiRxLevDLH : -110 .. 47 dB, AMRiRxLevULH : -110 .. 47 dB. Thus an intra-cell handover is triggered if : "(n,p) voting" is fulfilled for the uplink direction, and RxLevULweight > AMRiRxLevULH or "(n,p) voting" is fulfilled for the downlink direction, and RxLevDLweight > AMRiRxLevDLH.
Page 44/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Two new cause values are created in the Handover Indication message : alarm intra-cell handover for uplink criteria in case of FR channel : 17, alarm intra-cell handover for downlink criteria in case of FR channel : 18. 5.1.4.3.4 Handover AMR FR -> AMR HR This handover is used to change the channel type of a mobile from FR to HR if the quality is sufficient. Due to the high C/I requirement for HR channel, the requested codec mode of "(n,p) voting" mechanism is fixed by default to 12.2 kbits/s and a dedicated "n" parameter (handoverControl object) allows to fixed the trade-off between quality and capacity : nCapacityFRRequestedCodec : 1..196. The handover is triggered if the "(n,p) voting" principle is fulfilled in both directions, but in this case the (n,p) voting is: If in the last p downlink requested codec modes, at least n requested codec modes are equal to 12.2 kbits/s. and If in the last p uplink requested codec modes, at least n requested codec modes are equal to 12.2 kbits/s, then the condition is fulfilled. One new cause value is created in the Handover Indication message : capacity handover for uplink and downlink criteria in case of FR channel : 21. Note :

5.1.4.3.5
this mechanism is not linked to the intra-cell parameter of handovercontrol object. this mechanism is deactivated if nCapacityFRRequestedCodec is greater than pRequestedCodec.
Handover HR -> FR This handover is used to change the channel type of a mobile from HR to FR if the quality is not sufficient. The handover is triggered if the "(n,p) voting" principle is fulfilled in one direction. The following parameter is introduced on the handoverControl object, in order to specify the target requested codec mode for this handover: AMRHRToFRIntracellCodecModeThreshold : 7.4, 6.7, 5.9, 4.75. Two new cause values are created in the Handover Indication message :
Page 45/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
HR=>FR handover for uplink criteria in case of HR channel : 19, HR=>FR handover for downlink criteria in case of HR channel : 20. Note :

5.1.4.3.6
this mechanism is not linked to the intra-cell parameter of handovercontrol object, this mechanism is deactivated if AMRHRToFRIntracellCodecModeThreshold is set to 4.75.
Direct half rate TCH allocation In order to avoid some unnecessary handover from FR to HR channel, it is mandatory to evaluate the radio conditions at following stages : primo allocation : SDCCH => TCH in a normal cell, primo allocation : SDCCH => large zone TCH in a multi-zones cell, primo allocation : SDCCH => small zone TCH in a multi-zones cell, inter-zone handover from large to small in a multi-zones cell. and allocate immediately a HR channel if radio conditions are sufficient. The principle of this mechanism is to compare the RxLev uplink and downlink to dedicate thresholds, in order to estimate the MS HR capability. Following parameters are introduced on the handoverControl object, in order to specified RxLev thresholds for this handover : AMRDirectAllocRxLevUL : -110..-47, AMRDirectAllocRxLevDL : -110..-47, AMRDirectAllocIntRxLevUL : -110..-47, AMRDirectAllocIntRxLevDL : -110..-47. The BTS uses following expressions in order to determine if the MS has sufficient radio conditions to manage HR channel in each zone : normal cell or large zone : (RxLevDLweight* > AMRDirectAllocRxLevDL) and (RxLevULweight* > AMRDirectAllocRxLevUL) small zone : (RxLevDLweight* > AMRDirectAllocIntRxLevDL) and (RxLevULweight* > AMRDirectAllocIntRxLevUL) * measurements taking into account are all available measurements, with a maximum equals to the normal averaging in case of inter-zone handover. This information is sent in the Handover Indication or Connection State Ack message, using the following bit map :
Current cell additional information element 8 7 6 5 4 3 2 1 Element identifier = 6Bh
Page 46/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
spare bits
HR HR small small large zone
If no measurement is received at this stage, the BTS shall wait for the first measurement before sending the Connect State Ack. 5.1.4.3.7 Inter-zone handover Inter-zone handover mechanisms are not modified due to AMR services introduction, except for quality handover from inner-zone to outer-zone : for non AMR calls : if the inter-cell RxQual criterion is verified and no neighboring cell is eligible, then an inner to large zone handover is triggered . for AMR calls : if the inter-cell AMR quality criterion is verified and no neighboring cell is eligible, then a inner to large zone handover is triggered and the target channel is always a FR channel. 5.1.4.3.8 Handover priority From V12, the handover priority is the following (see [A2]) : HO Capture, RXQUAL - signal quality, uplink then downlink, RXLEV - signal strength, uplink then downlink, DISTANCE - if required for this cell, PBGT - if required for this cell, TRAFFIC - if required for this cell, INTRACELL - uplink then downlink, INTERZONE - downlink, TIERING - if required for this cell, and is not modified for normal mobiles, but for AMR mobiles, it becomes the following order : HO Capture, AMR quality - AMR quality, uplink then downlink, RXLEV - signal strength, uplink then downlink, DISTANCE - if required for this cell, PBGT - if required for this cell, TRAFFIC - if required for this cell, INTER-MODE (HR FR) - if required for this cell, INTRACELL - uplink then downlink, INTERZONE - downlink, TIERING - if required for this cell. 5.1.4.3.9 AMR L1m deactivation In order to allow a smooth introduction of AMR services, it is possible to deactivate following AMR L1m algorithms: AMR FR Intra-cell handover and AMR quality inter-cell handover, AMR power control mechanism.
Page 47/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
If one of these mechanisms is deactivated, then the legacy algorithm is activated: AMR FR intra-cell handover is replaced by intra-cell handover based on RxQual criteria, AMR quality inter-cell handover is replaced by the inter-cell handover based on RxQual criteria, AMR power control is replaced by the legacy power control based on RxQual & RxLev criteria. These deactivations are done using the amrReserved2 parameter, according to the following setting: Value 0 (default value): AMR L1m algorithms are used. Value 1: AMR FR intra-cell handover and AMR quality inter cell handover are deactivated, but the AMR power control is activated. Value 2: AMR FR intra-cell handover and AMR quality inter cell handover are activated, and the AMR power control is deactivated. Value 3: AMR FR intra-cell handover, AMR quality inter cell handover and the AMR power control are deactivated. This parameters is available at the OMC-R level, managed by all NRP, except the AMR activation NRP and this parameter is not managed by the CT2000 and the SDO. If AMR handovers are deactivated, then the handover priority table from V12 is used (see [A2]) and following counters are triggered : 1138/2: uplink quality, 1138/3: downlink quality, 1138/8: intracell uplink, 1138/9: intracell downlink, 1839/2 Uplink Quality, 1839/3 Downlink Quality, 1840/2 Uplink Quality, 1840/3 Downlink Quality. If AMR handovers are deactivated, then the following tables is applied in order to choose the target channel type:
Page 48/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Initial Channel type Handover cause RxQual RxLev DISTANCE PBGT TRAFFIC Forced HO Capture Directed retry
HR AMR
FR AMR
FR AMR FR AMR FR AMR HR AMR HR AMR FR AMR FR AMR FR AMR
FR AMR FR AMR FR AMR FR AMR FR AMR FR AMR FR AMR FR AMR
If AMR power control is deactivated, counters associated to AMR power control are still incremented.
5.1.4.3.10
Summary The following table presents a summary of all new L1m decisions :
HO decision
quality UL / DL intercell
channel type
TCH FR TCH HR
p value for (n,p) voting

pRequestedCodec pRequestedCodec
n value for (n,p) voting

nFRRequestedCodec nHRRequestedCodec
target codec
AMRFRIntercellCod ecModeThreshold AMRHRTargetCode cModeQualH AMRFRIntracellCod ecModeThreshold AMRHRIntracellCod ecModeThreshold fixed to FR codec 12.2
quality intracell UL / DL FR => FR HR => FR capacity intracell FR => HR
TCH FR TCH HR TCH FR
pRequestedCodec pRequestedCodec pRequestedCodec
nFRRequestedCodec nHRRequestedCodec nCapacityFRRequeste dCodec
Direct HR TCH allocation

outer zone
channel type
SDCCH
averaging window
1..rxLevHreqt* rxLevHreqave
Thresholds
AMRDirectAllocRxL evUL AMRDirectAllocRxL evDL AMRDirectAllocIntR xLevUL AMRDirectAllocIntR xLevDL
inner zone
SDCCH TCH FR TCH HR
1..rxLevHreqt* rxLevHreqave
* in this case, all available measures, up to rxLevHreqt are taken into account.0
Page 49/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Following figures illustrate all possible transitions for an AMR call, in a multizones cell environment :
Internal cell Handover :
tiering BCCH=>FH FR tiering BCCH=>FH HR tiering FH=>BCCH FR tiering FH=>BCCH HR FR
FR HR FR
Intra-cell FR or HR
Intra-cell FR or HR Inter-zone FR FR or HR Inter-zone HR HR Capacity FR FR Capacity Capacity FR HR HR FR
FR Inter-zone FR or HR HR HR FR HR FR
FR
Direct TCH allocation
Page 50/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
Inter-cell Handover :
HR
HR FR
Target Cell
FR
FR
FR
PBGT
PBGT Traffic
FR HR FR HR
Alarm Capture
HR FR
Source Cell
HR FR FR FR
Directed retry
Page 51/110 12/05/04
PE/SYS/DD/0343
01.11 / EN
5.2
FEATURE INTERWORKING
This radio allocator is the one designed from V7 and activated if the radio_allocator parameter is set to "voice+data circuit".
5.2.1 RADIO ALLOCATOR FROM V7
This radio allocator is not improved in order to manage AMR calls, thus if an AMR request occurs and this radio allocator is selected, then : an other vocoder (EFR or FR) is selected using priority order given in the channel type element , the allocated channel type is always a full rate TCH. 5.2.2 VAD / DTX
For the uplink path, It is possible to activate VAD/DTX separately for FR and HR cases, thus the current parameter (dtxMode) is extended uplink FR DTX Uplink HR DTX value (bit 6 and 5) of value (bit 8, 6 and 5) DTX mode element of DTX mode (see [A1]) in System element (see [A1]) in Info Type 3 System Info Type 6 FRmsmayuseDTX HRmsshallnotuseDTX 00 000 FRmsshalluseDTX HRmsshallnotuseDTX 01 001 FRmsshallnotuseDTX HRmsshallnotuseDTX 10 010 FRmsmayuseDTX HRmsmayuseDTX 00 100 FRmsshalluseDTX HRmsshalluseDTX 01 101 FRmsshallnotuseDTX HRmsshalluseDTX 10 110 Due to interworking with phase 1 MS, following values are not settable at the OMC-R : uplink FR DTX Uplink HR DTX value (bit 8, 6 and 5) of DTX mode element (see [A1]) FRmsshalluseDTX HRmsmayuseDTX 011 FRmsmayuseDTX HRmsshalluseDTX 111 For AMR channels, two VAD are specified (see [R9] for more details), in this BSS version, both are coded and the choice of the active VAD is done using one "BSC data config" parameter. Note : in this version, only VAD option 2 is fully tested.
5.2.3 QUEUING / PRIORITY 0

In this version : queuing is not possible for an HR only request, for a FR or HR request in queue, only a FR TCH can be allocated.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 52/110
The number of priority 0 TS takes into account only radio TS which are completely free (i.e. a free half rate TS is count for 0).
5.2.4 HANDOVER FOR TRAFFIC REASON AND DYNAMIC ACCESS CLASS BARING
These 2 mechanisms use the number of free radio TS. As above a free half rate TS counts for 0 and a free full rate TS counts for 1.
5.2.5 CIRCUIT SWITCH DATA CHANNEL

In V14, circuit switch data calls are managed only by FR TCH. If a data Assignment Request is received, then the BSC uses the following table to manage the request :
octet 3 of Channel Type 0000 1000 0000 1001 0000 1010 0000 1011 0001 1010 0001 1011 Signification Full rate TCH channel Bm Half rate TCH channel Lm Full or Half rate TCH channel, Full rate preferred, changes allowed also after first channel allocation as a result of the request. Full or Half rate TCH channel, Half rate preferred, changes allowed also after first channel allocation as a result of the request. Full or Half rate TCH channel, Full rate preferred, changes not allowed after first channel allocation as a result of the request. Full or Half rate TCH channel. Half rate preferred, changes not allowed after first channel allocation as a result of the request. new value 0000 1000 Request Rejected 0000 1000 0000 1000 0000 1000 0000 1000
5.2.6 TCH SIGNALING

A signaling half rate TCH can not be activate at reception of Channel Required. If a signaling Assignment Request (channel type : speech/ data indicator field is set to 0011), for a mobile using an half rate TCH, an assignment procedure is triggered to a SDCCH channel and the associated CIC is released3. If a signaling Assignment Request (channel type : speech/ data indicator field is set to 0011), for a mobile using an full rate TCH, a channel mode modify procedure is triggered to a signaling TCH channel and the associated CIC is released4. If an AMR HR or FR Assignment Request is received for a mobile using a signaling FR TCH, the BSC modifies the current signaling FR TCH to a AMR
3 This case occurs at the end of a speech call, if a SMS procedure is started and not finished. 4 This case occurs at the end of a speech call, if a SMS procedure is started and not finished.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 53/110
FR TCH and later, if radio conditions are sufficient, then a handover from AMR FR to AMR HR will be triggered by the BTS (see section Principles/ L1m/Handover mechanisms/ handover HR->FR).
5.2.7 AUTOMATIC CELL TIERING

Automatic cell tiering is a feature developed by Nortel, in order to improve spectrum efficiency (for more details, see [A4]). In V12.4, according to PWCI distribution and hopping TCH percentage, the BTS is able to automatically set the used threshold in order to trigger tiering handover. In V14, this mechanism has to be enhanced as show below, in order to take into account AMR HR calls : in V12.4 : P% is evaluated as : (number of TCH borne by a non SFH TDMA - NbLargeReuseDataChannels) . P% = (total number of TCH in the)cell - NbLargeReuseDataChannels in V14 : P% is evaluated as : (number of TCH borne by a non SFH TDMA - NbLargeReuseDataChannels) * (1+ Non _ FH_HR%) . P%= ((total number of TCH in the)cell - NbLargeReuseDataChannels) * (1+ HR%) where :
FH_HR% is the percent of HR calls managed by the hopping pattern in the cell, HR% is the percent of HR calls managed in the cell.
These 2 percentages are calculated by the BTS.
5.2.8 GENERAL PROTECTION AGAINST HO PING PONG

This feature defines the minimum duration between 2 kinds of handovers (see [A6] for more details). Due to AMR L1m introduction, a new cause value is added in hoCombination : AMRquality. This value is used in case of AMR handover triggered for alarm purpose. In case of inter-BSC handover, in order to distinguish between RxQual handover and AMR quality handover, the BSC uses following rules: If the handover cause = RxQual and the speech version <> AMR then the Handover cause = RxQual. If the handover cause = RxQual and the speech version = AMR then the Handover cause = AMR quality.
5.2.9 CM1170 HW/SW COMPATIBILITY

The "CM1170 HW/SW COMPATIBILITY" feature (see [A3] for more details) is completed, in order to ban the AMR activation on a DCU2 TRX and the

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 54/110
associated codano (1074) is extended (see "External Manager interface)/Alarms & Notifications" section).
(Q3
The BSC uses the AMR capability of the first TRX available in the cell, in order to determine if AMR services have to be configured for this cell : the first TRX is a DCU4 or a DRX, AMR services are activated, the first TRX is a DCU2, AMR services are not activated. If all DCU2 TRX of one cell are replaced by DCU4 TRX, the operator has to lock and unlock the cell, in order to reactivate AMR services in the cells. If AMR services are activated in a mixed DCU2/DCU4 cell5, some Channel Activation Nack for AMR calls can occurs, in some specific cases. This Nack message induces the abnormal end of the procedure (Assignment Failure, Handover Request Nack) and increment some counters (for example : C1056 and C1057 screening 1; C1062 and C1063 screening 2).
5.2.10 HANDOVER EFR/FR
AMR
A handover EFR/FR AMR can occur during an inter-cell intra-BSC handover from (to) a non AMR cell to (from) an AMR cell. For handover from AMR area to non-AMR area, as described in section Principle/ TMG mechanisms/ Ater management, the handover is performed via the A interface using external handover mechanism, in order to allow the fallback to EFR or FR channel (according to Assignment Request order). For handover from non-AMR area to AMR area, in order to decrease the MSC load, the call is not upgraded to AMR and a normal EFR handover occurs.
5.2.11 GSM/GPRS TS SHARING

The GSM/GPRS TS sharing is used in order to allow the BSC to preempt some GPRS radio resources, in case of lack of circuit radio resources (see [A1] for more details). In case of AMR FR request, there is no special mechanism and all algorithms detailed in [A1] are applied. In case of AMR HR request, if a preemption has to be done, then the allocated channel is an AMR FR one.
5.2.12 ASCI FEATURES

VBS and VGCS features can not be managed by an AMR channel. An AMR channel can be allocated after a preemption procedure.
5 This mixed configuration does not support AMR services.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 55/110
5.2.13 GET CHANNEL STATE

The get channel state mechanism is enhanced in order to manage HR channel and the result of a get channel state of a channel object is coded as one FR channel or two HR channels. In both case, the BSC indicates the state of each channel (free, busy).
5.3
OPERATION
Due to : the number of parameters linked to this feature and specially some class 2 parameters, a dedicated L1m for AMR calls, it is strongly recommended to use the dedicated NRP (see "O&M procedures/Operation/NRP" for more details), at the AMR activation.
5.4
PERFORMANCES
This section presents some simulation results, linked to HR and FR allocation interworking. Targets of these simulations are to : evaluate the number of carried Erlang managed by each kind of channel and associated blocking rates, evaluate the allocator efficiency in term of HR FR interworking and specially the impact of holes created by HR TS on FR blocking rate. Inputs of these simulations are : HR allocation duration : Poisson law, average = 25 seconds*, FR allocation duration : Poisson law, average = 35 seconds*, blocking rate : 2%. * : without HR channel, the normal allocation duration is around 40 seconds, but due to HR FR handover, this duration is reduced. During these simulations, the number of SDCCH TS in cell is not modified.
5.4.1 HR AMR CAPACITY

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 56/110
Carried Erlangs according to HR allocation penetration :

O1 O2 O3 O4 O5 O6 O7 O8 O9 O10 O11 O12 O13 O14 O15 O16 TCH number 6 14 21 29 36 44 51 59 65 73 80 88 95 103 110 118 0% 2.2 7.9 14 20 26 33 40 47 53 61 67 75 81 89 95 10 3 10% 2.2 8.2 14 21 27 34 41 49 55 63 70 78 84 92 99 107 20% 2.3 8.5 15 22 28 36 43 51 57 65 72 80 87 96 103 111 30% 2.5 9.0 16 23 30 38 45 54 60 69 77 85 92 101 108 118 40% 2.7 9.7 17 25 32 40 48 57 64 73 80 90 97 106 114 124 50% 2.9 10.7 18 27 35 44 52 62 69 78 87 96 105 115 123 133 60% 3.2 11.6 20 29 38 47 56 66 74 84 94 104 113 124 133 143 70% 3.7 12.8 22 32 41 52 62 73 81 92 102 113 124 134 144 155 80% 4.3 14.3 24 36 46 58 69 81 90 102 112 125 136 148 158 171 90% 5.0 16.3 27 39 51 65 76 89 99 113 125 138 150 163 176 190 100% 6.4 19.5 32 46 60 75 88 103 114 130 144 159 173 189 202 218
Erlang according to HR allocation (O4)

50.000 45.000 40.000 35.000 Erlang 30.000 25.000 20.000 15.000 10.000 5.000 0.000 0.00 20.00 40.00 60.00 80.00 100.00 Erlang Erlang FR Erlang HR
% of HR allocation
The hole management : the following table gives some results for a O2 cell, where : blocking rate blocking rate is the global blocking rate of the cell, HR blocking rate is the blocking rate of HR requests, FR blocking rate is the blocking rate of FR requests, blocking rate with garbage collector I the global blocking rate of the cell, if an ideal garbage collector is implemented to solve the hole problem, FR blocking rate with garbage collector, the same but for full rate request,

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 57/110
a hole exists as soon as 2 HR TS are free, on 2 different radio TS in cell.

0% 2.01 2.01 2.01 2.01 10% 2.01 0.92 2.13 1.98 2.09 15.6 20% 2.01 0.83 2.29 1.98 2.21 12.3 30% 2.00 0.80 2.51 1.87 2.25 9.4 40% 2.01 0.68 2.89 1.82 2.40 8.0 50% 2.00 0.83 3.16 1.85 2.56 6.7 60% 2.01 0.96 3.63 1.87 2.68 5.9 70% 1.99 1.04 4.28 1.83 2.98 5.1 80% 2.00 1.30 4.87 1.93 3.23 4.5 90% 2.01 1.50 6.47 1.99 4.08 3.9 100% 1.99 1.99 1.99 -
Percent of HR allocation blocking rate HR blocking rate FR blocking rate blocking rate with garbage collector FR blocking rate with garbage collector hole duration
We can notice that : the FR blocking rate increases logically with HR penetration, but remains normal up to a reasonable percent, the hole duration is short and the gain given by an ideal garbage collector is very low at the cell level (maximum : 0.18%), by comparison with the cost of an intra-cell procedure used to move a MS from a HR TS to another, in term of : o voice quality : every handover induce a small voice perturbation, o drop call : even if a handover is performed in good radio condition, there is a drop call probability, o BSC load : each handover has a direct handover on the BSC load.
5.4.2 BSC E3 CAPACITY

5.4.2.1 HR AMR According to : call profile, BSC type (mainly the number of TMU), BSC configuration (number of cells, number of TRX by cell), each BSC has a maximum capacity in term of traffic, given in Erlang. Due to introduction of HR AMR service, following data are modified : call profile : introduction of HR FR handover, number of Erlangs by cell, thus according to HR AMR penetration, following points have to be studied : BSC capacity (see below), BSC configuration : number of cells by BSC, number of TRX by BSC, LAC size 5.4.2.2 CPU Due to : sophisticated allocation mechanisms,

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 58/110
intra-cell handovers from (to) HR channel to (from) FR channel, AMR services induce an increase of the load on the BSC.
5.4.2.3 BSC Memory and OMC-R BSC link AMR services induces a high number of new counters, thus an increase of the BSC memory use and of the OMC-R BSC link, but in this version these 2 factors are not limiting.
5.4.3 OMC-R CAPACITY

AMR services induces a high number of new counters, thus an increase of the OMC-R resources use in term of memory, disk space, Ethernet bandwidth, but in this version these factors are not limiting.
5.4.4 TDMA CONFIGURATION

Due to the half rate channel introduction and to limit the number of contexts in the BSC, the number of SDCCH per TDMA is limited as following : normal cell : o Maximum number of SDCCH per TDMA : 2, o only one SDCCH TS managed by odd TS per TDMA, o only one SDCCH TS managed by even TS per TDMA. extended cell : o Maximum number of SDCCH per TDMA : 1. One OMC-R check is implemented in order to control these limits.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 59/110
5.4.5 LAPD CAPACITY

Following figures give the number of Lapd messages and the Lapd bandwidth according to the number of Erlang by Lapd, the call profile (GSM and GPRS) and the GPRS activation :
90 80 70 60 50 40 30 20 10 0 Downlink bandwidth
Ko / s
Standard Short 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 call high mobility
Erlang
600 500
msg / s
Messages
400 300 200 100 0 Standard Short call 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 high mobility
Erlang
70 60 50 Ko / s 40 30 20 10 0
Uplink bandwidth
Standard Short 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 call high mobility
Erlang

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 60/110
Limits indicated on these figures are : in term of messages : the engineering limit for the BCF, for the CBCF, there is no capacity problem, in term of bandwidth : the engineering limit for the use of a Lapd link in one path.
5.4.6
AMR HR FR INTERWORKING
In case of deactivation of AMR FR service, following points have to be highlighted : direct HR TCH allocation is available, even if AMR FR is not configured in the cell, handovers from FR radio TS to AMR HR are triggered on requested codec mode criterion, but this criterion is available only for AMR calls, thus this kind of handover is not possible from a FR or EFR channel and decreases the AMR HR efficiency, handovers from (or to) an AMR HR channel to (or from) EFR channel are performed using an external handover procedure and thus induce : more load on the MSC, more perturbations on the voice quality, thus it is mandatory to activate AMR FR service, in case of AMR HR activation and a control is done at the OMC-R.
5.4.7 CALL SETUP TIME

AMR services induces an increase of the length of some messages and particularly : Assignment Command, Setup, This increase can induce in some cases (frequency hopping with a high number of frequencies in the law for RR messages, high size of the Called Party BCD number element) a segmentation of these messages on the Air interface. Each supplementary segmentation induces an increases of 235ms of the call setup time.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 61/110
6. INTERFACES
6.1 GSM INTERFACES
6.1.1 AIR INTERFACE
6.1.1.1 Messages for Radio Resources management The complete description of messages and information elements is given in [A1], the following table described which messages and information elements are modified or created in this BSS release, due to AMR service introduction : Channel Mode Channel Desc Multi-rate Configuration 10.5.2.6** 10.5.2.5* 10.5.2.21aa*** Assignment modified modified new Command Handover modified modified new Command Channel modified new Mode Modify Channel modified Mode Modify ACK * : in this information element, a mode is added due to half rate channel introduction : 0 0 0 1 T : for TCH/H + ACCHs ** : in this information element, a Channel Description is added due to AMR introduction : 0 1 0 0 0 0 0 1: for speech full rate or half rate version 3. *** for this element, the following format is used : 8 7 6 5 4 3 2 1 Multi-rate speech Configuration IEI octet 1 length octet 2 MR version spare ICMI spare Start mode octet 3 ACS octet 4 spare Threshold 1 octet 5 Hysteresis 1 Threshold 2 octet 6 Threshold 2 Hysteresis 2 Threshold 3 octet 7 Threshold 3 Hysteresis 3 octet 8 with :
MR (Multi Rate) version = 0 0 1, ICMI (Initial Codec Mode Indicator) = 1 (The initial codec mode is defined by the Start Mode field), Start Mode = 0 0 (i.e. 5.9 for FR TCH) and 0 1 (i.e.5.9 for HR TCH),

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 62/110
ACS = 1 1 0 0 1 1 0 0(i.e. 12.2, 10.2, 6.7, 5.9) for FR TCH, ACS = 0 0 0 1 1 1 0 1(i.e. 7.4, 6.7, 5.9, 4.75) for HR TCH. System Information type 3 and 6 uses the following table, in order to set the cell options element : dtxMode value (bit 6 and 5) of value (bit 8, 6 and 5) DTX mode element of DTX mode (see [A1]) in System element (see [A1]) in Info Type 3 System Info Type 6 FRmsmayuseDTX/HRmsshallnotuseDTX 00 000 FRmsshalluseDTX/HRmsshallnotuseDTX 01 001 FRmsshallnotuseDTX/HRmsshallnotuseDTX 10 010 FRmsmayuseDTX/HRmsmayuseDTX 00 100 FRmsshalluseDTX/HRmsshalluseDTX 01 101 FRmsshallnotuseDTX/HRmsshalluseDTX 10 110
6.1.1.2 Messages for RATSCCH management See section " RATSCCH management" for all details.
6.1.2 A INTERFACE
The complete description of messages and information elements is given in [A10], the following table described which messages and information elements are modified in this BSS release, due to AMR service introduction : Channel Speech Chosen Current type version Channel Channel Type 1 3.2.2.11 3.2.2.51 3.2.2.33 3.2.2.49 Assignment Request X Assignment Complete X X Handover Performed X X Handover Required X X Handover Request X X X Handover Request Ack X X Channel type : Management of new values for : Channel rate and type : half rate channel, permitted speech version : GSM speech full or half rate version 3. If an Assignment Request or a Handover Request is received with the channel type capability sets to half rate only (i.e. a TCH/FR is not allowed for this connection), then this request is rejected (cause element sets to xxx).

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 63/110
Speech Version : Management of new value for : Speech version identifier : GSM speech full or half rate version 3. Chosen Channel : Management of new value for : Channel : 1001 1 Half rate TCH Current Channel type 1 : Management of new value for : Channel : 1001 1 Half rate TCH The mapping between Abis and A interface for new handover types is the following : Abis cause A cause alarm inter-cell handover for uplink criteria in case of FR uplink quality channel alarm inter-cell handover for downlink criteria in case of FR downlink quality channel alarm inter-cell handover for uplink criteria in case of HR uplink quality channel alarm inter-cell handover for downlink criteria in case of HR downlink quality channel alarm intra-cell handover for uplink criteria in case of FR uplink quality channel alarm intra-cell handover for downlink criteria in case of FR downlink quality channel HR=>FR handover for uplink criteria in case of HR channel uplink quality HR=>FR handover for downlink criteria in case of HR downlink quality channel capacity handover for uplink and downlink criteria in case of Traffic FR channel

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 64/110
6.1.3 ABIS INTERFACE

6.1.3.1 ABIS OML messages The DRX catalog file is modified in order to take into account AMR services : DRX catalog file: The 257-byte table at the end of this file has been redefined as follows:
byte index [0] [1..4] [5..8] [37..40] [41..245] [246] [247] [255] [256] Significance 02 hw1 mask hw2 mask hw10 mask 00 (not used) hw1 reference hw2 reference hw10 reference checksum
The fist byte ([0]) gives the version of the 256 bytes table: o 0 : feature not implemented o 1 : ABIS message implementation table o 2 : hardware/software/feature compatibility The "hw masks" ([1..40]) gives the list of features available for each DRX hardware supported by the catalog file. An "hw mask" bits are defined as follows: o Bit 0 : 0 : Cell Tiering not possible 1 : Cell Tiering possible o Bit 1 : 0 : New L1M not possible 1 : New L1M possible o Bit 2 : 0 : GPRS not possible 1 : GPRS possible o Bit 3 : 0 : AMR not possible 1 : AMR possible

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 65/110
6.1.3.2 6.1.3.2.1
6.1.3.2.1.1
ABIS RSL messages Modified messages

Current Cell Parameter
MS-BS Power Control element :

8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 Element Identifier = 56h Length = 05h PowerIncStepSizeUL PowerRedStepSizeUL pwr_type_algo PowerIncStepSizeDL PowerRedStepSizeDL
6.1.3.2.1.2
(Extended) Neighbouring Cells Parameters message
The ho_margin_amr information is added in the neigh. cells parameters element (byte 28).
6.1.3.2.1.3 Connection State Ack
Current cell add infos element Note : in previous version this element was called "Multizone Information". 8 7 6 5 4 3 2 1 Element identifier = 6Bh spare bits HR HR small small large zone Connection Context element :
8 Early Early 7 5 4 3 2 Element identifier Length Lev_ul_pmax_short_ave Lev_ul_pmax_ave Lev_ul_pmax_super_ave Lev_dl_pmax_short_ave Lev_dl_pmax_ave Lev_dl_pmax_super_ave Ber_ul_short_ave (most significant octet) Ber_ul_short_ave (less significant octet) Ber_ul_super_ave (most significant octet) Ber_ul_super_ave (less significant octet) Ber_dl_short_ave (most significant octet) Ber_dl_short_ave (less significant octet) 6 1 Octet octet 1 octet 2 octet 3 octet 4 octet 5 octet 6 octet 7 octet 8 octet 9 octet 10 octet 11 octet 12 octet 13 octet 14

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 66/110
Ber_dl_super_ave (most significant octet) Ber_dl_super_ave (less significant octet) Dist_super_ave PWCI HoMargin_adapt_offset_s HoMargin_adapt_offset_n Nb_nc Ncell averages[0] ... Ncell averages[Nb_nc - 1] communication type uplink Codec_mode_cumul_P[4.75] (CMR(4)) uplink Codec_mode_cumul_P[5.15] (useless) uplink Codec_mode_cumul_P[5.9] uplink Codec_mode_cumul_P[6.7] uplink Codec_mode_cumul_P[7.4] (useless) uplink Codec_mode_cumul_P[7.955] (useless) uplink Codec_mode_cumul_P[10.2] uplink Codec_mode_cumul_P[12.2] downlink Codec_mode_cumul_P[4.75] (CMR(4)) downlink Codec_mode_cumul_P[5.15] (useless) downlink Codec_mode_cumul_P[5.9] downlink Codec_mode_cumul_P[6.7] downlink Codec_mode_cumul_P[7.4] (useless) downlink Codec_mode_cumul_P[7.955] (useless) downlink Codec_mode_cumul_P[10.2] downlink Codec_mode_cumul_P[12.2]
octet 15 octet 16 octet 17 octet 18 octet 19 octet 20 octet 21 octet 22 to octet 25 octet 22 +4 x Nb_nc 4 to octet 22 +4 x Nb_nc 1 octet 22 +4 x Nb_nc octet 23 +4 x Nb_nc octet 24 +4 x Nb_nc octet 25 +4 x Nb_nc octet 26 +4 x Nb_nc octet 27 +4 x Nb_nc octet 28 +4 x Nb_nc octet 29 +4 x Nb_nc octet 30 +4 x Nb_nc octet 31 +4 x Nb_nc octet 32 +4 x Nb_nc octet 33 +4 x Nb_nc octet 34 +4 x Nb_nc octet 35 +4 x Nb_nc octet 36 +4 x Nb_nc octet 37 +4 x Nb_nc octet 38 +4 x Nb_nc
6.1.3.2.1.4
Handover Indication
Current cell add infos element : 8 7 6 5 4 3 2 1 Element identifier = 6Bh spare bits HR HR small small large zone where : HR small bit is set to 1, if the MS has sufficient radio condition in order to manage half rate channel in the small zone, HR large bit is set to 1, if the MS has sufficient radio condition in order to manage half rate channel in the large zone, small zone bit is set to 1, if the MS has sufficient radio condition in order to manage half rate or full rate channel in the small zone,

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 67/110
Handover Cause element : Following new causes are added : 13 alarm inter-cell handover for uplink criteria in case of FR channel 14 alarm inter-cell handover for downlink criteria in case of FR channel 15 alarm inter-cell handover for uplink criteria in case of HR channel 16 alarm inter-cell handover for downlink criteria in case of HR channel 17 alarm intra-cell handover for uplink criteria in case of FR channel 18 alarm intra-cell handover for downlink criteria in case of FR channel 19 HR=>FR handover for uplink criteria in case of HR channel 20 HR=>FR handover for downlink criteria in case of HR channel 21 capacity handover for uplink and downlink criteria in case of FR channel Connection Context element : see Connection State Ack message.
6.1.3.2.1.5 Call Clearing Indication
Connection Context element : see Connection State Ack message.

6.1.3.2.1.6 Stop Measurement Ack
Observation Context and Reduced Observation Context : following counters are added : 16 number of 40 ms periods during which codec FR 4.75 has been applied on the uplink 17 number of 40 ms periods during which codec FR 4.75 has been applied on the downlink 18 number of 40 ms periods during which codec FR 5.9 has been applied on the uplink 19 number of 40 ms periods during which codec FR 5.9 has been applied on the downlink 20 number of 40 ms periods during which codec FR 6.7 has been applied on the uplink 21 number of 40 ms periods during which codec FR 6.7 has been applied on the downlink 22 number of 40 ms periods during which codec FR 10.2 has been applied on the uplink 23 number of 40 ms periods during which codec FR 10.2 has been applied on the downlink 24 number of 40 ms periods during which codec HR 4.75 has been applied on the uplink 25 number of 40 ms periods during which codec HR 4.75 has been applied on the downlink 26 number of 40 ms periods during which codec HR 5.9 has been applied on the uplink 27 number of 40 ms periods during which codec HR 5.9 has been applied on the downlink 28 number of 40 ms periods during which codec HR 6.7 has been applied

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 68/110
on the uplink 29 number of 40 ms periods during which codec HR 6.7 has been applied on the downlink 30 number of SPEECH BAD FRAMES received on the uplink with codec FR 4.75 31 number of valid frames received on the uplink with codec FR 4.75 32 number of SPEECH BAD FRAMES received on the uplink with codec FR 5.9 33 number of valid frames received on the uplink with codec FR 5.9 34 number of SPEECH BAD FRAMES received on the uplink with codec FR 6.7 35 number of valid frames received on the uplink with codec FR 6.7 36 number of SPEECH BAD FRAMES received on the uplink with codec FR 10.2 37 number of valid frames received on the uplink with codec FR 10.2 38 number of SPEECH BAD FRAMES received on the uplink with codec HR 4.75 39 number of valid frames received on the uplink with codec HR 4.75 40 number of SPEECH BAD FRAMES received on the uplink with codec HR 5.9 41 number of valid frames received on the uplink with codec HR 5.9 42 number of SPEECH BAD FRAMES received on the uplink with codec HR 6.7 43 number of valid frames received on the uplink with codec HR 6.7 44 number of uplink NO DATA frames 45 number of downlink NO DATA frames 46 number of RATSCCH procedure failure 47 number of codec modification : FR uplink increment 48 number of codec modification : FR uplink decrement 49 number of codec modification : FR downlink increment 50 number of codec modification : FR downlink decrement 51 number of codec modification : HR uplink increment 52 number of codec modification : HR uplink decrement 53 number of codec modification : HR downlink increment 54 number of codec modification : HR downlink decrement 59 C/I_UL sum (1/2 dB)

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 69/110
6.1.3.2.1.7
Measurement Result
In case of AMR connection, this message is extended in order to provide AMR measurements, using the optional supplementary information element :
8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 ... byte N Element Identifier = 19h Length = (N - 2) RFU
DTXd
RXLEV-FULL-up RXLEV-SUB-up RXQUAL-FULL-up Supplementary Measurement Information (optional) RXQUAL-SUB-up
Reserved Reserved
In case of non-AMR call, this element is changed as follow :

8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 SFH byte 8 Element Identifier = 19h Length = 6 RFU
DTXd
RXLEV-FULL-up RXLEV-SUB-up RXQUAL-FULL-up RXQUAL-SUB-up
Reserved Reserved
UL supplementary measurement IEI = 79h Length = 1 var_drxlev_ul

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 70/110
But in case of HR AMR call, the following encoding is used :

8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 SFH byte 8 byte 9 byte 10 byte 11
Element Identifier = 19h Length = 16 RFU

DTXd
RXLEV-FULL-up RXLEV-SUB-up RXQUAL-FULL-up RXQUAL-SUB-up
Reserved Reserved
AMR Supplementary Measurement Info. IEI = 77h Length = 8 Uplink codec mode ... Uplink codec mode Downlink codec mode ... Downlink codec mode number of requests number of requests number of requests number of requests
byte 14 byte 15
byte 18

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 71/110
But in case of FR AMR call, the following encoding is used : :

8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 SFH byte 8 byte 9 byte 10 byte 11
Element Identifier = 19h Length = 18 RFU DTX d Reserved Reserved RXLEV-SUB-up RXQUAL-FULL-up RXQUAL-SUB-up RXLEV-FULL-up
AMR Supplementary Measurement Info. IEI = 77h Length = 10 Uplink codec mode ... Uplink codec mode Downlink codec mode ... Downlink codec mode number of requests number of requests number of requests number of requests
byte 15 byte 16
byte 20
Each codec mode is coded as below (see " New messages / Extended Current Cell Parameters / group AMR Adaptation Parameters "). The number of request represents the number of periods, for which the associated codec mode was required during the period.
6.1.3.2.1.8 Channel Activate and Mode Modify Request
Using the following element, the BSC gives to the BTS : the Connection capability in term of FR and HR management : 8 7 6 5 4 3 2 1 Element identifier = 7B spare bits FR HR where : FR bit is set to 1, if the MS has the AMR FR capability, HR bit is set to 1, if the MS has the AMR HR capability. the Channel Mode : 0010 0001 : AMR FR, 0010 0101 : AMR HR, the Channel Number : 00001 TCH full rate, 0001T TCH half rate (the T bit indicate the sub channel number)

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 72/110
the Multi rate configuration : 8 7 6 5 4 3 2 1 Multi-rate Configuration IEI length = 7 MR version 0 ICMI 0 Start mode 12.2 10.2 7.95 7.40 6.70 5.90 5.15 4.75 0 0 Threshold 1 Hysteresis 1 Threshold 2 Threshold 2 Hysteresis 2 Threshold 3 Threshold 3 Hysteresis 3
6.1.3.2.1.9 Start Measurement
octet 1 octet 2 octet 3 octet 4 octet 5 octet 6 octet 7 octet 8
In the Start Measurement, the Allocation cause has been enhanced, for RATSCCH management purpose:
8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 Element Identifier = 78h Length = 1 Allocation cause
with the following values : 0: initial assignment, 1: capacity intra-cell HO, 2: quality intra-cell HO, 3: inter-cell HO, 4: reestablishment, other values: inhibit the protection for the communication. 6.1.3.2.2
6.1.3.2.2.1
New messages
Extended Current Cell Parameters
This new message is sent from the BSC to the BTS, in order to provide all AMR L1m and codec mode adaptation information, using the following structure :
Information Element Message Discriminator Message Type AMR Adaptation Parameters Reference 0 0 1 0 1 0 0 0 0 1 0 0 0 1 Type 0 M 1 M Length 1d 1d 104d 4d 18d
group AMR Adaptation O Parameters AMR Power Control Parameters group AMR Power Control O Parameters group AMR Handover MO AMR Handover Parameters Parameters

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 73/110
group AMR Adaptation Parameters :

8 7 5 4 3 2 1 Element Identifier = 74h Length = 102d number of profiles = 5d elementary length (of a profile) = 20d Spare bits profile identifier number of codecs = 9 6 byte 1 byte 2 byte 3 byte 4 byte 5 + (n profil x 20) byte 6 + (n profil x 20) byte 7 + (n profil x 20) + n codec x2 byte 8 + (n profil x 20) + n codec x2 x nb of codec s
elementary length (of a codec) = 2 hysteresis
x nb of profile s
codec identifier
threshold
where : nb of codec : 0..8 nn of profiles : 0...3 "profile identifier" element : 4 3 2 1 description 0 0 0 0 uplink no SFH, slow MS 0 0 0 1 uplink no SFH, fast MS 0 0 1 0 uplink SFH with less than 8 freq. 0 0 1 1 uplink SFH with more than 7 freq. 1 0 0 0 Downlink SFH 900 TU3 X X X X RFU

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 74/110
"codec identifier" element : 4 3 2 1 codec rate FR 4.75 0 0 0 0 FR 5.9 0 0 1 0 0 1 1 FR 6.7 0 FR 10.2 0 1 1 0 0 1 1 1 FR 12.2 (*) HR 4.75 1 0 0 0 0 1 0 HR 5.9 1 HR 6.7 1 0 1 1 1 1 0 0 HR 7.4 (*) * : these codec modes are used for L1m purpose only. In the following sections code modes are coded as above. hysteresis : 0..7.5 dB (step : 0.5 dB), threshold : 0..31.5 dB (step 0.5 dB), but in the BTS for implementation reasons, the following control is done : (threshold + hysteresis 31.5dB). The 0xFF value is used in case of not significant threshold. One threshold specifies the transition codec identifier -> coder identifier +1, example : Code identifier : 4.75 Threshold : 5.9 ->4.75
group AMR POWER CONTROL PARAMETERS :

8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 byte 4
Element Identifier = 75h Length = 02h

FRPowerControlTargetMode HRPowerControlTargetMode

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 75/110
group AMR HANDOVER PARAMETERS :

8 7 6 5 4 3 2 1 byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 byte 8 byte 9 byte 10 byte 11 byte 12 byte 13 byte 14 byte 15 byte 16 byte 17 byte 18 Element Identifier = 76h Length = 16d pRequestedCodec nCapacityFRRequestedCodec nFRRequestedCodec nHRRequestedCodec
AMRFRIntercellCodecModeThreshold AMRHRIntercellCodecModeThreshold AMRFRIntracellCodecModeThreshold AMRHRToFRIntracellCodecModeThreshold
AMRDirectAllocRxLevUL AMRDirectAllocRxLevDL AMRDirectAllocIntRxLevUL AMRDirectAllocIntRxLevDL AMRiRxLevULH AMRiRxLevDLH spare1 amrReserved2
6.1.3.2.2.2
Extended Current Cell Parameters ACK
This new message is sent from the BTS to the BSC, in order to acknowledge the Extended Current Cell Parameters message, using the following structure :
Information Element Message Discriminator Message Type Reference 0 0 1 0 1 0 0 0 0 1 0 1 0 0 0 0 Type M M Length 1d 1d
6.1.3.2.2.3
Extended Current Cell Parameters NACK
This new message is sent from the BTS to the BSC, in order to nack the Extended Current Cell Parameters message, using the following structure :
Information Element Message Discriminator Message Type RMP cause Nack Info Reference 0 0 1 0 1 0 0 0 0 1 0 1 0 0 0 1 Type M M M O Length 1d 1d 2d V
cause value

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 76/110
6.1.4 ATER INTERFACE

6.1.4.1 Ater OML messages In CONFIG CALLP REQ, GET CALLP DATA ACK, SET CALLP DATA REQ messages, a new value id added in the Callp config data element :
Size u8 u8 u8 u8[5] u8[5] Hex 0x 0x05 Value IEI_CALLP_CONFIG_DATA Number of CODECS configured in this IEI. This value ranges from 1 to 8. Size in bytes of a set of Callp Parameters. Set of CallP parameters for the first listed CODEC. (1) ... Set of CallP parameters for the last listed codec. (1)
(1) The following table details a set of CallP parameters :

Size u8 u16 u8 u8 Value Codec number (1=FR, 3=EFR, 5=AMR). Any value between 1 and 15 included are available. Guaranted minimum number of calls. Maximum calls threshold (in percent) Minimum calls threshold (in percent)
In CONFIG TCU REQ, GET TCU DATA ACK, SET TCU DATA REQ message, a new value id added in the Logic TRM codec data element :
Size u8 u8 u8 u8[14] u8[14] Hex 0x 0x0e Value IEI_LOGTRM_CODEC_DATA Number of CODECS configured in this IEI. This value ranges from 1 to 8. Size in bytes of a set of codec Parameters. Set of parameters for the first listed CODEC. (1) ... Set of parameters for the last listed codec. ((1)
(1) The following table details a set of codec parameters :

Size u8 u8 s8 s8 u8 u8 u32 u32 Value Codec number (1=FR, 3=EFR, 5=AMR). Any value between 1 and 15 included are available. Hang over delay. Uplink amplification gain. Downlink amplification gain. A interface parameters. Ater interface parameters. Electric echo canceller parameters (e_ecan_cfg). Acoustic echo canceller parameters (a_ecan_cfg).

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 77/110
The following table details the Ater interface parameters element : bit Name meaning 0 tty_on 1 = ttty_on 1 tty_baudrate 0=45.45 BAUDS (US) 1=50 BAUDS 2 Vad / dtx on 1=VAD/DTX on 3 Vad algo 0=VAD2 AMR 1=VAD1 AMR 4-7 unused 6.1.4.2 Ater RSL messages In the following messages : Established Request, Established Ack, Modif Request, Modif Ack, the Channel Coding element can take the new value : 8 7 6 5 4 3 2 1 0 0 0 0 0 1 1 0 AMR 6.1.4.3 TRAU frames format For AMR services, new TRAU frames are defined in recommendations, but for voice quality optimization in following cases : 6.7 kbits/s for FR channel, 5.9 kbits/s for FR channel, 4.75 kbits/s for FR channel, proprietary TRAU frames are used. For all others cases, the recommendation TRAU frame format is used (see [R12] and [R13]). In the proprietary cases, the following principle is used : the 16K frame is divided into 2 "8K frames" : one is used in order to manage 8K frames defined in [R13] for 4.75 up to 6.7 kbits/s rate (MSB), one is used to manage proprietary frames containing TFO, CRC information (LSB). So in case of half rate channel (i.e. 8 K frame on the Abis interface), the BSC has to switch the MSB frame from the TCU to the BTS. The LSB frame is ignored by the BSC in this case.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 78/110
Definition of the LSB TRAU frame :

Bit number Octet # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 1 H1 C1 C9 2 3 4 5 H5 C5 6 H6 C6 7 H7 C7 8 H8 C8 H2 H3 H4 C2 C3 C4 C10 C11 C12
X0
X1
X2 Pattern M Y0 Reserved (TFO, ) CRC
Y1
Y2 Z0 Z1 Z2
with : Pattern : M M 1000101 Control bits : Uplink Downlink Description Header Version 1 00000000 10011001 (H1 .. H8) C1..C3 Time Alignment Command C4..C9 Phase Alignment Bit C10 TFOE C11 DTXd C12 DFE UFE CRC : these CRC are used in order to have the same level of error detection than the 16 K frame format.
6.1.5 AGPRS INTERFACE

6.1.5.1 6.1.5.2 6.1.5.3 Agprs RSL messages Not applicable. Agprs GSL messages Not applicable. Agprs OML messages Not applicable.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 79/110
6.1.6 Gb INTERFACE
Not applicable.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 80/110
6.2
O&M INTERFACES
6.2.1 EXTERNAL MANAGER (Q3 INTERFACE)

6.2.1.1 Data Model Range Default values
New/modifie d
object transcoder coderPoolConfiguration This attribute indicates enumerated speech coding algorithms supported by the TCU. Note that TCU2G does not support AMR.
object :signallingPoint speechMode This attribute enumerates speech modes allowed in the BSC object :bts AMRAdapatationSet This attribute defines the lines of parameter used for the adaptation mechanism speechMode This attribute indicates enumerated speech coding algorithms supported by the cell HRCellLoadStart This attribute is used to trigger the beginning of AMR HR allocation in the cell. HRCellLoadEnd This attribute is used to trigger the end of AMR HR allocation in the cell. dtxMode This attribute specifies if the
list of [algoid, MinimumCalls, powerUplink , powerDownlink] where : algo id : full rate, enhanced full rate, AMR_FR_HR powerUplink : -15, +15 powerDownlink : -15, +15 Range Default values
modified
New/modifie d
[full rate, enhanced full modified list of [algoid] rate] where : algo id : full rate, enhanced full rate, AMR full rate, AMR half rate New/modifie Range Default values
d
0..3
new
[full rate, enhanced full list of [algoid] rate] where : algo id : full rate, enhanced full rate, AMR full rate, AMR half rate 0..100 100
modified
new
0..100
new
FRmsmayuseDTX/HRmsshallno FRmsmayuseDTX/Hrmsmay tuseDTX useDTX FRmsshalluseDTX/HRmsshalln
modified

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 81/110
uplink DTX is active or not
otuseDTX FRmsshallnotuseDTX/HRmssha llnotuseDTX FRmsmayuseDTX/HRmsmayDT X FRmsshalluseDTX/Hrmsshallus eDTX FRmsshallnotuseDTX/HRmssha lluseDTX
object :handoverControl
pRequestedCodec P parameter in the "(n,p) voting" mechanism nCapacityFRRequestedCodec n parameter in the full rate "(n,p) voting" mechanism nFRRequestedCodec n parameter in the full rate "(n,p) voting" mechanism nHRRequestedCodec n parameter in the half rate "(n,p) voting" mechanism AMRFRIntercellCodecModeThre shold specifies the target codec mode in case of FR intercell handover AMRHRIntercellCodecModeThre shold specifies the target codec mode in case of HR intercell handover AMRFRIntracellCodecModeThre shold specifies the target codec mode in case of FR intercell handover AMRHRToFRIntracellCodecMod eThreshold specifies the target codec mode in case of FR to HR handover AMRDirectAllocRxLevUL uplink RxLev threshold for direct TCH allocation AMRDirectAllocRxLevDL downlinkev threshold for direct TCH allocation AMRDirectAllocIntRxLevUL uplink RxLev threshold for direct TCH allocation in the
Range 12..192 (step : 12) 0..196 0..196 0..196 12.2, 10.2, 6.7, 5.9, 4.75
Default values 48 44 24 34 6.7
New/modifie d
new new new new new
7.4, 6.7, 5.9, 4.75
5.9
new
12.2, 10.2, 6.7, 5.9, 4.75
4.75
new
7.4, 6.7, 5.9, 4.75
6.7
new
-110..-47
-80
new
-110..-47
-80
new
-110..-47
-80
new

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 82/110
inner zone AMRDirectAllocIntRxLevDL down RxLev threshold for direct TCH allocation in the inner zone AMRiRxLevULH uplink RxLev threshold in case of AMR FR intracell handover AMRiRxLevDLH down RxLev threshold in case of AMR FR intracell handover AMRreserved1 AMRreserved2
-110..-47
-80
new
-110..-47
-75
new
-110..-47
-75
new
object :powerControl
PowerIncStepSizeUL** Increment step size for uplink power control PowerRedStepSizeUL** Decrement step size for uplink power control PowerIncStepSizeDL Increment step size for downlink power control PowerRedStepSizeDL
0 0 0..3 0 0 (default value): AMR L1m algorithms are used. 1: AMR FR intra-cell handover and AMR quality inter cell handover are deactivated, but the AMR power control is activated. 2: AMR FR intra-cell handover and AMR quality inter cell handover are activated, and the AMR power control is deactivated. 3: AMR FR intra-cell handover, AMR quality inter cell handover and the AMR power control are deactivated. Range Default values 2..30dB 4
new new
New/modifie d
new
2..30dB
new
2..30dB
new
2..8dB
new

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 83/110
Decrement step size for downlink power control FRPowerControlTargetMode Target codec mode for AMR FR power control HRPowerControlTargetMode Target codec mode for AMR HR power control
12.2, 10.2, 6.7, 5.9, 4.75
12.2
new
7.4, 6.7, 5.9, 4.75
7.4
new
object :adjacentCellHandover hoMarginAMR Handover margin linked to AMR quality handover hoCombination List of couples of causes indicating the causes of pingpong handovers in the overlapping areas object :transceiver
Range -63..+63 (HOInitialCause, HONonEssentialCause)*
Default values -2
New/modifie d
new modified
Range
Default values
New/modifie d
FRAMRPriority 0..2 0 AMR FR priority of the TDMA HRAMRPriority 0..2 0 AMR HR priority of the TDMA * in these 2 fields, a new value is added : AMRQuality ** for DCU2, these 2 fields replace previous powerIncrStepSize and powerRedStepSize. 6.2.1.2 Alarms & notifications
new new following parameters
For the 1074 codano ("Indication of non activated features on specific instances", see [A3] for more details), the following feature identifier is added : AMR services : (3). 6.2.1.3 Counters From V12, the list of activated observation counters in the BSS is defined using a dedicated tool, at the OMC-R level. Link to AMR services, a high number of counters is defined, thus in order to avoid useless load on the BSS, it is recommended to deactivate AMR FR or HR counter if these features are not used. The following counter list has been implemented in previous version and of course inherited for AMR HR counters :
counter title TCH_HR_ALLOCATED number of half rate TCH allocations. Type CUM counter id. 1610 location TDMA CLASS ORT ODIAG OFS X OGS

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 84/110
TCH_HR_ALLOCATED_NSC number of half rate TCH allocations. TCH_HR_AVERAGED_USED average and maximum number of half rate TCH allocations. TCH_HR_AVERAGED_USED_NSC average and maximum number of half rate TCH allocations. TCH_HR_RESOURCE_FAILURE number of failures caused by the lack of half rate TCH in the cell and a lack of free entries in the queue.
CUM Load Load CUM
1745 1612 1747 1614
TDMA CLASS TDMA CLASS TDMA CLASS TDMA CLASS
X X X X
Of course in this case, HR means AMR HR because no other codec is implemented for HR channel. In brackets, the associated observation context (OC) or handover cause (HC) is given (see section Interface \ GSM interfaces \ Abis interface \ Abis RSL messages \ Stop Measurement Ack). 6.2.1.4 TMG counters This section defines all counters link to AMR services and Traffic ManaGement, which allows to evaluate : the number of AMR calls, the number of AMR handovers, the drop call ratio of AMR calls. In this section a "classic" channel means a non AMR channel (EFR or FR).
counter title AMR_FR_TCH_ALLOCATED number of AMR full rate TCH allocations. AMR_FR_ TCH_STD_AVERAGED_USED average and maximum number of AMR full rate TCH allocations. AMR_TCH_Connection_Duration duration of the TCH connections. This counter starts at the beginning of transmission of SACCH blocks on TCH, and stops at the end of SACCH blocks transmission. Screening 0 : AMR_FR_TCH Screening 1 : AMR_HR_TCH CHANNEL_ACTIVATE_SPEECH number of channel activation for speech. S0 full rate algorithm S1 Enhanced full rate algorithm S2 AMR half rate algorithm S3 AMR FR algorithm AMR_ TCH_successfully_Assigned number of successful AMR TCH assignations for any kind of mobile. Screening 0 : AMR_FR_TCH Screening 1 : AMR_HR_TCH AMR_ TCH_ ASSIGN_FAILURE number of failure of the dedicated channel assignment procedure for AMR TCH. Screening 0 : AMR_FR_TCH Screening 1 : AMR_HR_TCH SPEECH_ALGO_FALL_BACK* Number of handover and assignment which the initial request in EFR or AMR speech algorithm is degraded into FR or EFR speech algorithm Screening 0 : EFR -> FR Screening 1 : AMR-> classic FR_AMR_HO_REQUIRED_TCH number of FR AMR required handovers in the cell. These Type Cum
Load Val
counter id. 1900

1901 1902
location TDMA CLASS TDMA CLASS TDMA CLASS
ORT
ODIAG
OFS X
X X
OGS
cum
1197
cell
Cum
1903
Cell
Cum
1904
Cell
Cum
1206
bsc
Cum
1950
cell

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 85/110
counters are incremented upon receipt of a Handover Indication message, if the handover indication message is taken into account. Screening 0 : Intracell AMR FR Up (HC17) Screening 1 : Intracell AMR FR down (HC18) Screening 2 : AMR Quality FR UP (HC13) Screening 3 : AMR Quality FR down (HC14) Screening 4 : Capacity FR-> HR (HC21) HR_AMR_HO_REQUIRED_TCH number of HR AMR required handovers in the cell. These counters are incremented upon receipt of a Handover Indication message, if the handover indication message is taken into account. Screening 0 : Alarm HR->FR up (HC19) Screening 1 : Alarm HR->FR down (HC20) Screening 2 : AMR Quality HR UP (HC15) Screening 3 : AMR Qualtity HR down (HC16) HO_Request_OUTGOING_TCH number of outgoing handovers (intra/inter_bss) requests by an AMR MS Screening 0 : AMR FR Screening 1 : AMR HR HO_Success_OUTGOING_TCH number of successful outgoing handovers (intra/inter_bss) by an AMR MS Screening 0 : classic Screening 1 : AMR FR Screening 1 : AMR HR AMR_HO_REQUEST_INTRA_CELL_TCH number of Intracell handover requests for the cell, by an AMR mobile. The counter is incremented at the end of the handover (success, selection failure, execution failure or end of call). Screening 0 : AMR FR Screening 1 : AMR FR -> AMR HR Screening 2 : AMR HR -> AMR FR AMR_HO_Execution_INTRA_CELL_TCH number of Intracell handover executions for the cell, for an AMR mobile. The counter is incremented at the end of the handover (success, execution failure or end of call). Screening 0 : AMR FR Screening 1 : AMR FR -> AMR HR Screening 2 : AMR HR -> AMR FR AMR_HO_Success_INTRA_CELL_TCH number of successful Intracell handovers for the cell, for an AMR mobile. Screening 0 : AMR FR Screening 1 : AMR FR -> AMR HR Screening 2 : AMR HR -> AMR FR HO_NCELLS_EXECUTION_TCH_AMRHR number of attempts of HR AMR handovers from a central cell to a neighboring one. HO_NCELLS_EXECUTION_TCH_AMRFR number of attempts of FR AMR handovers from a central cell to a neighboring one. HO_NCELLS_UNSUCCESS_TCH_AMRHR Screening 0 : mobile returns to the old channel. triggered on receipt of HANDOVER FAILURE message before T3103 timer expiration Screening 1 : expiration of T3103 timer. triggered on expiration of T3103 timer. significant for intra BSS and inter BSS handovers. Screening 2 : other cases. triggered on receipt of a CLEAR COMMAND message with a cause set to another value than "handover successful" or "call control". significant for inter BSS handovers. HO_NCELLS_UNSUCCESS_TCH_AMRFR Screening 0 : mobile returns to the old channel. triggered on receipt of HANDOVER FAILURE message before T3103 timer expiration
Cum
1951
cell
Cum
1952
cell
Cum
1780
cell
Cum
1953
cell
Cum
1954
cell
Cum
1955
cell
Cum Cum Cum
1956 1957 1958
neigh. neigh neigh
X X X
Cum
1959
neigh

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 86/110
Screening 1 : expiration of T3103 timer. triggered on expiration of T3103 timer. significant for intra BSS and inter BSS handovers. Screening 2 : other cases. triggered on receipt of a CLEAR COMMAND message with a cause set to another value than "handover successful" or "call control". significant for inter BSS handovers. HO_NCELLS_REQUEST_OUTGOING_AMRHR of outgoing intra BSS or inter BSS handovers attempts from a central cell to a neighboring one for AMR HR call. HO_NCELLS_REQUEST_OUTGOING_AMRFR number of outgoing intra BSS or inter BSS handovers success from a central cell to a neighboring one for an AMR FR call traffic_release_AMR_FR** number of release for FR AMR mobile Screening 0: Lapdm cause Screening 1 : radio cause Screening 2 : others causes traffic_release_AMR_HR** number of release for HR AMR mobile Screening 0: Lapdm cause Screening 1 : radio cause Screening 2 : others causes
Cum
1963 1964
neigh. neigh. Cell
X X X
Cum
1960
Cum
1961
Cell
* this counter has to be implemented on BSC 12000. The management of this counter is modified in V14 as follow : the BSC checks the difference between the channel type received from the MSC and the modified channel type after BSS filtering of not allowed vocoders (speechMode attributes of signallingPoint and bts object + coderPoolConfiguration of transcoder object; see section "TMG MECHANISMS/Channel allocation /Flag management"). this check is done just before the channel allocation. So this counter evaluates the number of potential fallbacks. ** these counters are a summary of counter "1164 traffic release" screened by mobile type : Screening 0 Lapdm cause : this screening is the sum of following 1164 screenings: Screening: 16 Receipt of a RELEASE INDICATION message from the BTS. Screening: 17 Receipt of an ERROR INDICATION message: expiration of (N200 + 1) times of T200 timer. Screening: 18 Receipt of an ERROR_INDICATION message: DM frame received in established multi-frame state. Screening: 19 Receipt of an ERROR_INDICATION message: sequence error. Screening 1 radio cause : this screening is the sum of following 1164 screenings : Screening: 6 Expiration of T3107 timer before receipt of ESTABLISHMENT INDICATION message, during an Dedicated Channel Assignment procedure or a handover Intracell on SDCCH procedure. Screening: 12 Receipt of a CALL CLEARING request from the L1M following a call clearing distance threshold comparison.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 87/110
Screening: 13 Receipt of a CONNEXION FAILURE INDICATION message with Abis cause set to radio interface failure. Screening: 14 Receipt of a CONNEXION FAILURE INDICATION message with Abis cause set to radio link failure. Screening: 23 Two expirations of TmodMs timer (CHANNEL MODE MODIFY procedure). Screening: 24 Expiration of T3103 timer (handover procedure). Screening: 25 Expiration of T8 timer (inter-BSC handover procedure). Screening 2 others causes : this screening is the sum of following 1164 screenings: Screening: 0 Receipt of a SCCP DISCONNECTION INDICATION message from the MSC. Screening: 1 Receipt of a RESET message from the MSC. Screening: 2 Receipt of a RESET CIRCUIT DOWNLINK message from the MSC. Screening: 3 Receipt of a SCCP DATA REFUSAL message from the MSC. Screening: 7 TS removal due to an O&M operation (associated cell put out of service...) Screening: 8 TS removal due to an equipment failure (PCM KO...) Screening: 9 CIC removal due to an O&M operation (terrestrial circuit put out of service...) Screening: 10 CIC removal due to an equipment failure (PCM KO...). Screening: 11 Associated radio channel blocked due to an O&M action. Screening: 28 Others. Screening: 31 SYS INFO procedure failure after a switchover. Screening: 32 Receipt of a CONNEXION FAILURE INDICATION message with Abis cause set to re-mote transcoder failure.
6.2.1.5
L1m counters This section defines all counters link to AMR services and L1m, which allows to evaluate the quality of AMR calls compared to non AMR calls in term of RxLev, RxQual All previous L1m counters do not take into account AMR calls, which are managed only by the following counters.
counter title C/I_UPLINK_FR* Sum of uplink C/I received from the L1m, for non AMR channel (i.e. classic TCH and SDCCH). (OC55) DOWNLINK_POWER_CTRL_MAX_TCH_AMRFR time downlink power control was running at maximum level for the busy FR AMR TCHs. UPLINK_POWER_CTRL_MAX._TCH_AMRFR time uplink power control was running at maximum level for the busy FR AMR TCHs. RXLEV_DOWNLINK_AMRFR number of downlink RXLEV received from the L1m for FR AMR TCH.
Type Cum
Val Val Cum
counter id. 1905

1906 1907 1908
location TDMA CLASS

Cell Cell TDMA CLASS
ORT
ODIAG
OFS X
X X X
OGS

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 88/110
RXLEV_UPLINK_AMRFR number of uplink RXLEV received from the L1m for FR AMR TCH. RXQUAL_DOWNLINK_AMRFR number of downlink RXQual received from the L1m for FR AMR TCH. RXQUAL_UPLINK_AMRFR number of uplink RXQual received from the L1m for FR AMR TCH. MS_POWER_INC_CONTROL_AMRFR number of MS increment power control ordered by the L1m for FR AMR TCH. MS_POWER_DEC_CONTROL_AMRFR number of MS decrement power control ordered by the L1m for FR AMR TCH BS_POWER_INC_CONTROL_AMRFR number of BS increment power control ordered by the L1m for FR AMR TCH. BS_POWER_DEC_CONTROL_AMRFR number of BS decrement power control ordered by the L1m for FR AMR TCH. C/I_UPLINK_AMRFR* Sum of uplink C/I received from the L1m, for FR AMR calls(OC55) TIMING_ADVANCE_AMRFR average and maximum timing advance values FR AMR calls in the cell. MS_LOST_MEASUREMENTS_AMRFR number of MS measurement messages not received by the BTS for an AMR FR call DOWNLINK_POWER_CTRL_MAX_TCH_AMRHR time downlink power control was running at maximum level for the busy HR AMR TCHs. UPLINK_POWER_CTRL_MAX_TCH_AMRHR time uplink power control was running at maximum level for the busy FR AMR TCHs. RXLEV_DOWNLINK_AMRHR number of downlink RXLEV received from the L1m for HR AMR TCH. RXLEV_UPLINK_AMRHR number of uplink RXLEV received from the L1m for HR AMR TCH. RXQUAL_DOWNLINK_AMRHR number of downlink RXQual received from the L1m for HR AMR TCH. RXQUAL_UPLINK_AMRHR number of uplink RXQual received from the L1m for HR AMR TCH. MS_POWER_INC_CONTROL_AMRHR number of MS increment power control ordered by the L1m for HR AMR TCH MS_POWER_DEC_CONTROL_AMRHR number of MS decrement power control ordered by the L1m for HR AMR TCH BS_POWER_INC_CONTROL_AMRHR number of BS increment power control ordered by the L1m for HR AMR TCH. BS_POWER_DEC_CONTROL_AMRHR number of BS decrement power control ordered by the L1m for HR AMR TCH. C/I_UPLINK_AMRHR* Sum of uplink C/I received from the L1m, for HR AMR calls(OC55) TIMING_ADVANCE_AMRHR average and maximum timing advance values HR AMR calls in the cell. MS_LOST_MEASUREMENTS_AMRHR number of MS measurement messages not received by the BTS for an AMR HR call
Cum Cum Cum Cum Cum Cum Cum Cum Cum cum Val Val Cum Cum Cum Cum Cum Cum Cum Cum Cum Cum cum
1909 1910 1911 1912 1913 1914 1915 1916 1917 1930 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1931
TDMA CLASS TDMA CLASS TDMA CLASS Cell Cell Cell Cell TDMA CLASS Cell TDMA CLASS Cell Cell TDMA CLASS TDMA CLASS TDMA CLASS TDMA CLASS Cell Cell Cell Cell TDMA CLASS Cell TDMA CLASS
X X X X X X X X X X X X X X X X X X X X X X X
* this counter is given in dB.


PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 89/110
6.2.1.6
AMR counters This section defines all counters link to AMR mechanisms, which allows to evaluate the accuracy of AMR adaptation mechanism in term of distribution of AMR codec mode, number of bad frames received, stability of AMR mechanism. The use of these is counters is to : demonstrate AMR adaptation mechanism accuracy during AMR deployment, monitor on a day basis, AMR adaptation mechanisms, thus except during AMR validation, it is recommended to configure these counters in the OGS list.
counter title codec Uplink use AMR FR Number of uplink CMC for AMR FR Screening 0 : codec 4.75 (OC 16) Screening 1 : codec 5.9 (OC 18) Screening 2 : codec 6.7 (OC 20) Screening 3 : codec 10.2 (OC 22) codec Uplink use AMR HR Number of uplink CMC for AMR HR Screening 0 : codec 4.75 (OC 24) Screening 1 : codec 5.9 (OC 26) Screening 2 : codec 6.7 (OC 28) codec Downlink use AMR FR Number of downlink CMC for AMR FR Screening 0 : codec 4.75 (OC 17) Screening 1 : codec 5.9 (OC 19) Screening 2 : codec 6.7 (OC 21) Screening 3 : codec 10.2 (OC 23) codec Downlink use AMR HR Number of downlink CMC for AMR HR Screening 0 : codec 4.75 (OC 25) Screening 1 : codec 5.9 (OC 27) Screening 2 : codec 6.7 (OC 29) Speech bad frames AMR FR Number of bad speech frames (BFI KO) received at the BTS for each AMR FR coded mode Screening 0 : codec 4.75 (OC 30) Screening 1 : codec 5.9 (OC 32) Screening 2 : codec 6.7 (OC 34) Screening 3 : codec 10.2 (OC 36) Received speech frames AMR FR Number of correct and bad speech frames received at the level for each AMR FR coded mode Screening 0 : codec 4.75 (OC 31) Screening 1 : codec 5.9 (OC 33) Screening 2 : codec 6.7 (OC 35) Screening 3 : codec 10.2 (OC 37) Speech bad frames AMR HR Number of bad speech frames (BFI KO) received at the BTS for each AMR HR coded mode Screening 0 : codec 4.75 (OC 38) Screening 1 : codec 5.9 (OC 40) Screening 2 : codec 6.7 (OC 42) Received speech frames AMR HR Number of correct and bad speech frames received at the level for each AMR HR coded mode
Type Cum
counter id. 1975
location TDMA CLASS
ORT
ODIAG
OFS
OGS X
Cum
1976
TDMA CLASS
Cum
1977
TDMA CLASS
Cum
1978
TDMA CLASS
Cum level
1979
TDMA CLASS
Cum BTS
1980
TDMA CLASS
Cum level
1981
TDMA CLASS
Cum BTS
1982
TDMA CLASS

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 90/110
Screening 0 : codec 4.75 (OC 39) Screening 1 : codec 5.9 (OC 41) Screening 2 : codec 6.7 (OC 43) number of no data frames Number of no data frames received or sent on the Abis interface for AMR (FR and HR) calls Screening 0 : uplink (OC 44) Screening 1 : downlink (OC 45) number of modifications AMR FR up Screening 0 : inc (OC 47) Screening 1 : dec (OC 48) number of modifications AMR FR down Screening 0 : inc (OC 49) Screening 1 : dec (OC 50) number of modifications AMR HR up Screening 0 : inc (OC 51) Screening 1 : dec (OC 52) number of modifications AMR HR down Screening 0 : inc (OC 53) Screening 1 : dec (OC 54) Number of RASTCCH procedure failure number of RASTCHH procedure failure for AMR calls (FR and HR) (see "RATSCCH management " section for more details) (OC 46)
Cum
1983
Cell
Cum Cum Cum Cum Cum
1984 1985 1986 1987 1988
TDMA CLASS TDMA CLASS TDMA CLASS TDMA CLASS Cell
X X X X X
Using these counters, following information can be evaluated : Frame Erasure rate (FER) for each code mode : Speech bad frames AMR FER = Received speech frames Voice Activity Factor (VAF) for each path : Numberofnodataframes VAF = totalnumberofframes 6.2.1.7 Existing counters
The following table lists all existing counters related to TCH management, in previous versions and specifies if these counters are incremented in case of AMR FR or AMR HR call. If the screening of one counter is not detailed, then it follows the rule establishes for the counter.
AMR FR 1609 S0 S1 S2 1744 1810 1611 S0 S1 S2 TCH_FR_ALLOCATED allocation of a TCH channel. allocation in primo-allocation (call re-establishment). allocation for a SDCCH on overflowing (lack of SDCCH resources). TCH_FR_ALLOCATED_NSC TCH_FR_AVERAGE_CONFIGURATED TCH_FR_AVERAGED_USED allocation of a TCH channel. allocation in primo-allocation (call re-establishment). allocation for a SDCCH on overflowing (lack of SDCCH resources).
AMR HR
N N N N N N N N
Y N N Y N Y N N

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 91/110
1746 TCH_FR_AVERAGED_USED_NSC 1613 TCH_FR_RESOURCE_FAILURE 1700 TCH_FR_AVERAGE_AVAILABLE 1057 ALL_TCH_FR_ALLOCATED_TIME 1616 TCH_AVERAGE_QUEUE_LENGTH 1617 TCH_QUEUING_EXPIRATION 1618 TCH_QUEUEING_DURATION 1049 ATTEMPTED_TCH_FR_SEIZURES 1715 ATTEMPTED_TCH_FR_SEIZURES_MS_DUALB 1050 SUCCESSFUL_TCH_FR_SEIZURES 1716 SUCCESSFUL_TCH_FR_SEIZURES_MS_DUALB 1055 ASSIGN_FAILURE 1799 ASSIG_TO_OTHER_BAND_OR_ZONE 1841 ASSIGN_REQUEST 1842 ASSIGN_FAILURE_AINT 1620 DIRECTED_RETRY_UNSUCCESS_NO_CELL 1138 HO_REQUIRED_TCH S0 Uplink Strength S1 Downlink Strength S2 Uplink Quality S3 Downlink Quality S4 Distance S5 Power Budget S6 Capture S7 Intra_cell_O&M (TRX HS) S8 Intracell Uplink S9 IntraCell Down S10 Directed retry (only for HO_REQUIRED_TCH) S11 TDMA_class_0: intra-cell handover into a class 0 TDMA for downlink power level or distance, for a multi-class cell (concentric cell...) (only for HO_REQUIRED_TCH) S12 TDMA_class_1: intra-cell handover into a class 1 TDMA for downlink power level and distance, for a multi-class cell (concentric cell...) (only for HO_REQUIRED_TCH) S13 inter_cell_O&M (forced handover) S14 traffic. S15 tiering handover from large pattern to small pattern S16 small to large 1776 HO_REQUIRED_TCH_NSC 1165 HO_INDICATION_NOT_TREATED_TCHOKE 1782 HO_CELL_REJECTED 1208 HO_REQUEST_OUTGOING_MBAND_EBAND_MS_DUALB 1783 HO_REQUEST_OUTGOING_MBAND_MBAND_MS_DUALB 1784 HO_REQUEST_OUTGOING_EBAND_EBAND_MS_DUALB 1785 HO_REQUEST_OUTGOING_EBAND_MBAND_MS_DUALB 1789 HO_EXECUTION_OUTGOING_MBAND_EBAND_MS_DUALB 1790 HO_EXECUTION_OUTGOING_MBAND_MBAND_MS_DUALB 1791 HO_EXECUTION_OUTGOING_EBAND_EBAND_MS_DUALB 1792 HO_EXECUTION_OUTGOING_EBAND_MBAND_MS_DUALB 1209 HO_SUCCESS_OUTGOING_MBAND_EBAND_MS_DUALB 1786 HO_SUCCESS_OUTGOING_MBAND_MBAND_MS_DUALB 1787 HO_SUCCESS_OUTGOING_EBAND_EBAND_MS_DUALB 1788 HO_SUCCESS_OUTGOING_EBAND_MBAND_MS_DUALB 1780 HO_SUCCESS_OUTGOING_TCH 1781 HO_SUCCESS_INCOMING_TCH
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y N N Y Y Y Y Y Y
N N N N Y Y Y N N N N N N Y Y Y Y Y N N Y Y Y Y N N N Y Y Y Y Y
Y
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Y
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 92/110
1081 HO_REQUEST_INTRA_CELL_TCH 1796 HO_REQUEST_INTRA_CELL_MS_DUALB 1082 HO_EXECUTION_INTRA_CELL_TCH 1797 HO_EXECUTION_INTRA_CELL_MS_DUALB 1083 HO_SUCCESS_INTRA_CELL_TCH 1798 HO_SUCCESS_INTRA_CELL_MS_DUALB 1134 HO_UNSUCCESS_REEST_INTRA_CELL_TCH 1756 HO_FAILURE_INTRA_CELL_TCH 1802 HO_SUCCESS_TIERING_TCH 1801 HO_FAILURE_TIERING_TCH_NORR 1075 HO_REQUEST_OUTGOING_INTRA_BSS_TCH 1065 HO_EXECUTION_OUTGOING_INTRA_BSS_TCH 1067 HO_SUCCESS_OUTGOING_INTRA_BSS_TCH 1077 HO_SUCCESS_OUTGOING_FIRST_INTRA_TCH 1135 HO_UNSUCCESS_REEST_OUTGOING_INTRA_BSS_TCH 1167 HO_UNSUCCESS_OUTGOING_INTRA_BSS_N_ATTEMPT_TCH 1762 HO_FAILURE_OUTGOING_INTRA_BSS_TCH 1768 HO_UNSUCCESS_OUTGOING_INTRA_BSS_TCH 1069 HO_REQUEST_INCOMING_INTRA_BSS_TCH 1793 HO_REQUEST_INCOMING_INTRA_BSS_MS_DUALB 1071 HO_EXECUTION_INCOMING_INTRA_BSS_TCH 1794 HO_EXECUTION_INCOMING_INTRA_BSS_MS_DUALB 1073 HO_SUCCESS_INCOMING_INTRA_BSS_TCH 1795 HO_SUCCESS_INCOMING_INTRA_BSS_MS_DUALB 1137 HO_UNSUCCESS_REEST_INCOMING_INTRA_BSS_TCH 1758 HO_FAILURE_INCOMING_INTRA_BSS_TCH 1772 HO_UNSUCCESS_INCOMING_INTRA_BSS_TCH 1076 HO_REQUEST_OUTGOING_INTER_BSS_TCH 1066 HO_EXECUTION_OUTGOING_INTER_BSS_TCH 1068 HO_SUCCESS_OUTGOING_INTER_BSS_TCH 1078 HO_SUCCESS_OUTGOING_FIRST_INTER_TCH 1136 HO_UNSUCCESS_REEST_OUTGOING_INTER_BSS_TCH 1169 HO_UNSUCCESS_OUTGOING_INTER_BSS_N_ATTEMPT_TCH 1764 HO_FAILURE_OUTGOING_INTER_BSS_TCH 1770 HO_UNSUCCESS_OUTGOING_INTER_BSS_TCH 1070 HO_REQUEST_INCOMING_INTER_BSS_TCH 1072 HO_EXECUTION_INCOMING_INTER_BSS_TCH 1074 HO_SUCCESS_INCOMING_INTER_BSS_TCH 1760 HO_FAILURE_INCOMING_INTER_BSS_TCH 1774 HO_UNSUCCESS_INCOMING_INTER_BSS_TCH 1200 HO_NCELLS_EXECUTION_TCH 1204 HO_NCELLS_UNSUCCESS_TCH 1839 HO_NCELLS_REQUEST_OUTGOING S0 Uplink Strength S1 Downlink Strength S2 Uplink Quality S3 Downlink Quality S4 Distance S5 Power Budget S6 Directed retry S7 inter_cell_O&M (forced handover) S8 traffic. S9 other.
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y Y Y
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y Y Y

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 93/110
1840 S0 S1 S2 S3 S4 S5 S6 S7 S8 S9 1164 1754 1779 1621 1198 1199 1600 1601 1602 1603 1622 1623 1624 1625 1626 1805 1806 1807 1808 1809 1816 1717 1718 1719 1720 1721
HO_NCELLS_SUCCESS_OUTGOING Uplink Strength Downlink Strength Uplink Quality Downlink Quality Distance Power Budget Directed retry inter_cell_O&M (forced handover) traffic. other. TRAFFIC_RELEASE TRAFFIC_RELEASE_NSC TRAFFIC_ABNORMAL_RELEASE SAPI_3_SESSION_ESTABLISHMENT DOWNLINK_POWER_CTRL_MAX_TCH UPLINK_POWER_CTRL_MAX_TCH CONNECTION_DURATION_TCH DOWNLINK_POWER_CTRL_MAX_SDCCH UPLINK_POWER_CTRL_MAX_SDCCH CONNECTION_DURATION_SDCCH MS_LOST_MEASUREMENTS RXLEV_DOWNLINK RXLEV_UPLINK RXQUAL_DOWNLINK RXQUAL_UPLINK MS_POWER_INC_CONTROL MS_POWER_DEC_CONTROL BS_POWER_INC_CONTROL BS_POWER_DEC_CONTROL TIMING_ADVANCE PATH_BALANCE ABIS_TRAU_FRAME_DL_RECEIVED ABIS_TRAU_FRAME_DL_CORRECTED ABIS_TRAU_FRAME_DL_MUTED RADIO_FRAME_UL_RECEIVED ECU_ACTIVATION
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N N N N N N N N N N Y N N N N N
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N N N N N N N N N N Y N N N N N

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 94/110
6.2.2 LOCAL MANAGER (MAN MACHINE INTERFACE)

6.2.2.1 Data Model
mandatory
New/modified class param range 2 list of [algoid, modified MinimumCalls, powerUplink , powerDownlink] where : algo id : full rate, enhanced full rate, AMR_FR_HR powerUplink : -15, +15 powerDownlink : -15, +15 New/modified class param object :signallingPoint range modified 3 speechMode list of [algoid] This attribute enumerates where : speech modes allowed in the algo id : full rate, BSC enhanced full rate, AMR full rate, AMR half rate New/modified class param object :bts range AMRAdapatationSet 0..3 new 3 This attribute defines the line of parameter used for the adaptation mechanism modified 3 speechMode list of [algoid] This attribute indicates where : enumerated speech coding algo id : full rate, algorithms supported by the enhanced full rate, AMR cell full rate, AMR half rate HRCellLoadStart 0..100 new 3 This attribute is used to trigger the beginning of AMR HR allocation in the cell. HRCellLoadEnd 0..100 new 3 This attribute is used to trigger the end of AMR HR allocation in the cell. (not used in this version) FRmsmayuseDTX/HRmsshal dtxMode modified 3 This attribute specifies if the lnotuseDTX FRmsshalluseDTX/HRmssha uplink DTX is active or not llnotuseDTX
object transcoder coderPoolConfiguration This attribute indicates enumerated speech coding algorithms supported by the TCU. Note that TCU2G does not support AMR.
mandatory
mandatory
mandatory
mandatory
mandatory
mandatory
mandatory
mandatory
mandatory

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 95/110
FRmsshallnotuseDTX/HRms shallnotuseDTX FRmsmayuseDTX/HRmsma yDTX FRmsshalluseDTX/Hrmsshall useDTX FRmsshallnotuseDTX/HRms shalluseDTX
object :handoverControl
pRequestedCodec P parameter in the "(n,p) voting" mechanism nCapacityFRRequestedCodec n parameter in the full rate "(n,p) voting" mechanism nFRRequestedCodec n parameter in the full rate "(n,p) voting" mechanism nHRRequestedCodec n parameter in the half rate "(n,p) voting" mechanism AMRFRIntercellCodecModeThre shold specifies the target codec mode in case of FR intercell handover AMRHRIntercellCodecModeThre shold specifies the target codec mode in case of HR intercell handover AMRFRIntracellCodecModeThre shold specifies the target codec mode in case of FR intercell handover AMRHRToFRIntracellCodecMod eThreshold specifies the target codec mode in case of FR to HR handover AMRDirectAllocRxLevUL uplink RxLev threshold for direct TCH allocation AMRDirectAllocRxLevDL downlinkev threshold for direct TCH allocation AMRDirectAllocIntRxLevUL uplink RxLev threshold for direct TCH allocation in the inner zone
range 12..192 (step : 12) 0..192 0..192 0..192 12.2, 10.2, 6.7, 5.9, 4.75
New/modified class param
mandatory
new new new new new
3 3 3 3 3
mandatory mandatory mandatory mandatory mandatory
7.4, 6.7, 5.9, 4.75
new
mandatory
12.2, 10.2, 6.7, 5.9, 4.75
new
mandatory
7.4, 6.7, 5.9, 4.75
new
mandatory
-110..-47
new
mandatory
-110..-47
new
mandatory
-110..-47
new
mandatory

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 96/110
AMRDirectAllocIntRxLevDL down RxLev threshold for direct TCH allocation in the inner zone AMRiRxLevULH uplink RxLev threshold in case of AMR FR intracell handover AMRiRxLevDLH down RxLev threshold in case of AMR FR intracell handover AMRreserved1 AMRreserved2
-110..-47
new
mandatory
-110..-47
new
mandatory
-110..-47
new
mandatory
object :powerControl
PowerIncStepSizeUL Increment step size for uplink power control PowerRedStepSizeUL Decrement step size for uplink power control PowerIncStepSizeDL Increment step size for downlink power control
0 0..3 range 2..30dB
new new new
3 3 3
Optional optional
mandatory
mandatory
2..30dB
new
mandatory
2..30dB
new
mandatory
2..8dB PowerRedStepSizeDL Decrement step size for downlink power control

FRPowerControlTargetMode Target codec mode for AMR FR power control HRPowerControlTargetMode Target codec mode for AMR HR power control
new
mandatory
12.2, 10.2, 6.7, 5.9, 4.75
new
mandatory
7.4, 6.7, 5.9, 4.75
new
mandatory
object :adjacentCellHandover hoMarginAMR Handover margin linked to AMR quality handover hoCombination List of couples of causes indicating the causes of pingpong handovers in the overlapping areas object :transceiver FRAMRPriority
range -63..+63 *
mandatory
new modified
3 3
mandatory mandatory
range 0..2
mandatory
new
mandatory Page 97/110

PE/SYS/DD/0343 01.11 / EN 12/05/04
AMR FR priority of the TDMA HRAMRPriority 0..2 new 2 AMR HR priority of the TDMA * the following value is added in this parameter : AMRQuality. 6.2.2.2 6.2.2.3 6.2.2.4 Alarms & notifications See Q3 interface. Counters See Q3 interface. Miscellaneous
mandatory
Following parameters are settable using the "BSC data config" feature : DtxDownlinkHR : enable /disable downlink DTX for AMR HR calls (default value : enabled), DtxDownlinkFR : enable /disable downlink DTX for FR specch calls (default value : enabled), DtxDownlinkdata : enable /disable downlink DTX for data circuit calls (default value : enabled), downlink VAD used : default value VAD 2, Codec mode adaptation parameters : following sets of parameters are : Uplink Downlink Slow MS - no Fast MS - no FH with < 8 FH with 8 SFH 900 TU3 FH FH freq freq set 41 set 42 set 43 set 44 set 45 each set contains : one FR hysteresis, one HR hysteresis, 4 FR thresholds, 3 HR thresholds. channelTypeManagement : this flag is used to configure the A interface management : BSS management : see section Principles/TMG mechanisms A interface : in this case, the BSC applies all requirements given in the Channel Type element, in term of : channel type preference, change of channel type after the initial assignment, in case of handover. This mode is designed in order to satisfy all certification agreements and no radio criteria are taken into account in this case. In fact this mode uses same principles as the previous mode, but at reception of the Assignment Request or Handover Request, the

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 98/110
octet 4 of the channel type is accepted/modified or rejected as follow :

octet 4 value 0000 1000 0000 1001 0000 1010 Signification Full Rate TCH channel Bm. Preference between the permitted speech versions for full rate TCH as indicated in octet 5 and extensions of octet 5. Half Rate TCH channel Lm. Preference between the permitted speech versions for half rate TCH as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Full rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Half rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Full rate preferred, changes between full rate and half rate NOT allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Full or half rate TCH channel, Half rate preferred, changes between full rate and half rate NOT allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rate as indicated in octet 5 and extensions of octet 5. Management Request accepted Request refused Request accepted Request accepted Request changed (HR refused) 0000 1000 Request changed (HR refused) 0000 1000
0000 1011
0001 1010
0001 1011
The first mode is the normal one. The second one is only used in specific cases like compliance tests.
6.2.3 SDO
See Q3 interface.
6.3
TRANSMISSION NETWORK INTERFACES

Not applicable.
6.3.1 PCM 6.3.2 ETHERNET

Not applicable.
6.3.3 X25
Not applicable.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 99/110
7. O&M PROCEDURES
7.1 UPGRADES
Before the upgrade, a dedicated tool has to check if all TDMA verify new OMCR controls described in sections "Sub systems impacts / OMC-R". If it is not the case, the operator has to reconfigure all impacted cells.
7.1.1 OMC-R UPGRADE
7.1.2 BSC, TCU & BTS UPGRADE

During the upgrade, all new parameters are set to the default value and modified parameters are managed using the following table : object: TranscoderBoard coderPoolConfiguration object: signallingPoint speechMode object: bts speechMode dtxMode object: powerControl
PowerIncStepSizeUL PowerRedStepSizeUL PowerIncStepSizeDL PowerRedStepSizeDL
object: adjacentCellHandover
hoCombination
default value same value than previous version. range same value than previous version. range same value than previous version. see following table range powerIncrStepSize powerRedStepSize powerIncrStepSize powerRedStepSize range same value than previous version.
in in in
in
All AMR counters are added at the default list of counters. VAD/DTX : dtxMode : old value dtxMode : new value
msmayuseDTX msshalluseDTX msshallnotuseDTX FRmsmayuseDTX/HrmsmayuseDTX FRmsshalluseDTX/HrmsshalluseDTX FRmsshallnotuseDTX/HRmsshallnotuseDTX
7.2
INSTALLATION AND COMMISSIONING

Not applicable.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 100/110
7.3 7.4
MAINTENANCE
Not applicable.
OPERATION
Due to the number of AMR parameters, a dedicated NRP is created, in order to control AMR activation easily. All parameters of section "Interfaces. O&M Interfaces" are managed by this NRP. This NRP can induces if necessary : a TCU reset in order to add AMR capabilities, a cell reset in order to specify AMR priority of each TRX. This NRP works in two modes : mode command advised in case of small number of impacted cells, mode reset-build advised in case of high number of impacted cells.
7.4.1 NRP
7.5 7.6
EXTENSION
Not applicable.
TECHNICAL ASSISTANCE SUPPORT

Not applicable.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 101/110
8. FIELD INTRODUCTION
8.1 HARDWARE CONSTRAINTS
AMR services are not supported on following hardware : BSC 12000 and 12000HC, TCU 1G and 2G, BTS S4000 DCU2, BTS S4000 DCU2&DCU4 (in this case, it is strongly recommended to deactivate AMR services at the OMC-R using the speechMode parameter on the bts object).
8.2 8.3
SPARES CONSTRAINTS
Not applicable.
BSS VERSION INTERWORKING

All nodes of the BSS have to be in V14 (this is controlled by the BSC), if this shouldn't be the case the BSC deactivate the AMR feature.
8.4
NSS INTERWORKING
The NSS has to manage all element information link to AMR (see "A interface" section).
8.5 8.6
SGSN INTERWORKING
Not applicable.
FUNCTION INTERWORKING
Not applicable.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 102/110
8.7
ENGINEERING RULES
In following sections, a set of recommended values is proposed, of which target is guaranteed a good voice quality, even if the capacity gain is not maximum. Of course each operators can / have to adapt this proposal, to its "quality/capacity" strategy.
8.7.1 POWER CONTROL ALGORITHM

Recommended Value Parameter bsPowerControl UplinkPowerControl AMRFRPowerControlTargetMode AMRHRPowerControlTargetMode (2) PowerIncrStepSizeDL PowerIncrStepSizeUL (2) PowerRedStepSizeDL (2) (2) PowerRedStepSizeUL Enabled (1) (1) Enabled 12.2 7.4 4 dB 4 dB 2 dB 2 dB Deactivation Value Disabled Disabled N/A N/A N/A N/A N/A N/A
Power control has to be triggered when the call quality is very good. So we take the highest possible values (12.2 for FR and 7.4 for HR). Used the lowest values induces some risks of dropped calls, as there is no way to increase the MS or BTS power, thus the 4.75 value is strongly not recommended.
(1)
Enabling the parameter bsPowerControl and/or uplinkPowerControl activates both the power control for AMR calls and the power control (Step by step or One shot according to the value of the powerControlAlgorithm parameter) for standard calls (FR or EFR) Those steps are applicable to standard calls with step by step power control algorithm.
(2)
8.7.2 DIRECT HR TCH ALLOCATION

Parameter AMRDirectAllocRxLevDL AMRDirectAllocRxLevUL AMRDirectAllocIntRxLevDL AMRDirectAllocIntRxLevUL Recommended Value See Engineering rule 1 below See Engineering rule 1 below See Engineering rule 1 & 2 below See Engineering rule 1 & 2 below Deactivation Value -47 -47 -47 -47
Engineering rules: 1. To define the value of those parameters it is necessary to study the distribution of RxLev for the codec mode defined as the target for the HR to FR intra cell HO to avoid a immediate come back on a FR channel after a

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 103/110
direct HR allocation. The uplink parameter may be set considering a threshold corresponding to 90% of C/I values higher than 16 dB (proposed value, depends on the network quality). The downlink value will be deduced from the link balance. 2. The threshold to make a direct HR allocation in the small zone of a bizone cell has to be more restrictive than the threshold to go back to the large zone. AMRDirecAllocIntRxLevDL concentAlgoIntRxLev
Remark: The direct HR TCH allocation can be done at call establishment , or during an interzone handover. 8.7.3 HANDOVERS
There are different types of intracell handovers: capacity handover: FR to HR, quality handover: HR to FR, normal intracell: FR to FR, interzone handover. All these handovers, except interzone handover, are based on (n,p) voting decision: p is common for all of them (except for interzone handover), there are 3 different values of n: o 1 for capacity handover, o 1 for HR calls in intracell and intercell handovers (except for capacity), o 1 for FR calls in intracell and intercell handovers (except for capacity). The following graph shows the handover order philosophy : Good C/I IntraCell FR HR IntraCell FR FR IntraCell HR FR InterCell FR or HR Bad C/I

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 104/110
Parameter PrequestedCodec NCapacityFRRequestedCodec
Recommended Value 48 See Engineering 1 rule below 43 Set a value corresponding to 90% of pRequestedCodec See Engineering rule 2 below 6.7 33 Set a value corresponding to 70% of pRequestedCodec See Engineering rule 3 below 4.75 See Engineering rule 4 below 24 Set a value corresponding to 50% of pRequestedCodec See Engineering rule 3 below -75 See engineering rule 5 below -75 See engineering rule 5 below 5.9 See engineering rule 4 below 6.7 See engineering rule 4 below -2 dB (all, PBGT)
Deactivation Value N/A NCapacityFR RequestedCodec > PrequestedCodec 4.75 N/A
AMRHRIntraCellCodecMode Threshold nHRRequestedCodec
AMRFRIntraCellCodecMode Threshold NFRRequested Codec AMRRxLevULIH AMRRxLevDLIH AMRHRInterCellCodecModeThreshold AMRFRInterCellCodecModeThreshold AMRHOMargin HOPingPongCombination
4.75 N/A
N/A N/A 4.75 4.75 63 N/A
Target codecs for intercell handovers have to be smaller than the target codecs for power control. As a matter of fact the aim of the power control algorithm is to improve the communications conditions (increasing the power) instead of making a handover that would load the BSC and impact the voice quality. As the recommended value for Power Control algorithm is 10.2 for FR calls and 6.7 for HR, the recommended value for intercell HO has to be smaller (cf. table here under) To have coherent parameters it is necessary to trigger a intracell HO before intercell HO: the parameters have to be more restrictive for intercell HO. Otherwise, because of HO priorities, it will be never possible to make an intracell HO before an intercell HO. As the n values taken into account for intracell and intercell HO are the same, the difference will be done on the threshold values: If AMR Intracell handover is activated: o AMRFRIntraCellCodecModeThreshold > AMRFRInterCellCodecModeThreshold

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 105/110
o AMRHRToFRIntracellCodecModeThreshold > AMRHRInterCellCodecModeThreshold. So different sets of parameters are possible as shown in the following table. The set in bold is the recommended set. This one enables to maintain a good voice quality . HO intracell FR to HO intracell FR to FR FRactive non active 10.2 6.7 4.75 6.7 5.9 4.75 10.2 6.7 5.9 4.75 6.7 5.9 4.75 6.7 5.9 4.75 5.9 4.75 6.7 5.9 4.75 12.2 (hardcoded) 12.2 (hardcoded)
HO intracell FR to FR HO intercell FR HO intracell HR to FR HO intercell HR to FR HO intracell FR to HR
AMR handovers need to have a negative handover margin value (parameter HOMarginAMR) since it is a handover trigger for quality reason.
Engineering rules:
1. To have a similar reactivity between AMR calls and standard calls the value of p in the (n,p) voting has to correspond to the same reactivity of decision as for the standard calls: pRequestedCodecMode = (rxQualHreqt x rXQualHreqave) x12 since there are 12 codec mode requested for one measurement report received. Remark: this value has to be a multiple of 12 2. This value depends on the operator strategy. To make a capacity in real good condition we recommand to set this value to 90% of the p value: nCapacityFRRequestedCodec = pRequestedCodec x 90% 3. As we use the same target codec for FR to FR and HR to FR handovers (intracell and intercell handovers), the priority between those 2 handovers is given by the n value (p beeing the same). The conditions to make a handover FR to FR have to be more difficult, because the communication quality would be more increased in the same radio conditions, going from a HR to FR channel, than from a FR to FR channel (this is due to a better resistance to interference for the same codec value in FR than in HR). nFRRequestedCodecMode > nHRRequestedCodecMode 4. The target codec mode for intercell handover has to be more restrictive, than the one for intracell handover otherwise intracell handover will never be possible (see explanation above). 5. As AMR coding is better than standard coding, the threshold for intracell AMR handover must be more restrictive, than the one for standard calls: AMRRxLevXXIH > rxLevXXIH (with XX = UL or DL)
Remarks:

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 106/110
For AMR interzone handovers, the parameters used are the same as for standard handovers. For handover on PBGT and HO on traffic, if the initial channel was a HR channel the new channel in the neighboring cell will be also an HR channel if AMR activated in the neighboring cell is activated and the radio conditions verified.
Recommended Value See Engineering Rule See Engineering Rule Deactivation Value N/A N/A
8.7.4 TDMA PRIORITY

Parameter FRAMRPriority HRAMRPriority
Reminder: Priority 0 is given to a high priority TDMA Priority 1 is given to a low priority TDMA Priority 2 disables this service on the TDMA Engineering rule: It is highly recommended to reserve a FR TDMA on which HR allocation is set to priority 2 to favors an easier come back on FR when HR is activated. This backup TDMA has to be carried by the TDMA of highest value. See 5.1.3.1.4 8.7.5 LAPD DIMENSIONNING
Considering the actual proportion of AMR mobiles in a network, one LAPD for 8 TRX ( classical dimensioning) might be sufficient.
8.7.6 SDCCH DIMENSIONNING

It will be probably necessary to re-estimate the number of SDCCH channels (TBC after capacity studies). The number of SDCCH channels need to be periodically reestimated regarding HR penetration.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 107/110
9. SUB SYSTEMS IMPACTS

9.1 OMC-R
See "Functional description" chapter for main impacts. Due to Measurement Result format modification, call path and call path trace features have to be improved (see section "Interfaces/ Abis interface / Abis RSL messages/ Modified messages /Measurement Result"), in order to decode and present all new information at the MMI and SDO level. Following semantic checks have to be listed : if the bscArchitecture is equal to bsc6000 or bsc12000, then the speechMode attribute on the signalingPoint can not contain the following value : AMR full rate, AMR half rate, if the AMR HR is activated, then the AMR FR shall be configured (bts and signaling point objects). following expressions have to be verified : AMRDirectAllocIntRxLevDL concentAlgoIntRxLev, HRCellLoadEnd HRCellLoadStart, IRxLevDLP'+'powerIncrStepSizeDL <= 'uRxLevDLP, IRxLevULP'+'powerIncrStepSizeUL' <= 'uRxLevULP. TDMA configuration : normal cell : o Maximum number of SDCCH per TDMA : 2, o only one SDCCH TS managed by odd TS per TDMA, o only one SDCCH TS managed by even TS per TDMA. extended cell : o Maximum number of SDCCH per TDMA : 1.
9.2
BSC 12000
AMR services are not supported on BSC 12000, but following points have to be highlighted : a Speech version (AMR,EFR,FR) is accepted and an EFR or FR is activated, a Channel Type (HR,FR) is accepted and a FR TCH is allocated, some counters are implemented and allow the operator to evaluate the number of AMR mobiles managed by the BSC.
9.3
BSC E3
See "Functional description" chapter for main impacts.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 108/110
9.4
BTS
See "Functional description" chapter for main impacts. Due to the introduction of half rate channel, according to [R14], following timer and parameter have to be modified for this kind of channel : N200 is set to 29, 34 T200 44.
9.5 9.6 9.7
TCU 2G
Not applicable.
TCU E3
See "Functional description" chapter for main impacts.
PCUSN
Not applicable.

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 109/110
9.8
TOOLS
Y/N
Impact Maintenance tools TML platform TML BSC2G application TML TCU2G application TIL RTC application TIL COAM application TML BSC e3 application TML TCU e3 application ROT
Engineering tools CT2000 Network Configuration Tool iPlanner RF / Cell Optimization Tool CT5100 Network Planning Tool CT7100 Performance Monitoring Tool
Comments
(HW, SW, installation procedure)
Y Y Y Y
Management of all AMR parameters. Management of FR and HR AMR services. Management of HR channels. Management of : AMR counters, AMR parameters, metrics modification, new format of Measurement Result (call path trace and call trace features) Lapd load estimation.
Validation tools Simulators SPY
Y Y
End of DOCUMENT

PE/SYS/DD/0343 01.11 / EN 12/05/04
Page 110/110

AMR Full Rate Vs Half Rate

Uploaded by

Copyright:

Available Formats

AMR Full Rate Vs Half Rate

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AMR Full Rate Vs Half Rate

Uploaded by

Copyright:

Available Formats

GSM

Reference : Version : Date : PE/SYS/DD/000343 01.11 / EN 12/05/04

SV713 : AMR FULL RATE; SV885 AMR HALF RATE

ABBREVIATIONS AND DEFINITIONS ................................................................................................................. 9

END-USER/SUBSCRIBER BENEFITS .................................................................................................................... 15

5.4.3 5.4.4 5.4.5 5.4.6 5.4.7 6.

Ater interface ................................................................................................................................................. 77

AGPRS Interface ............................................................................................................................................ 79

6.1.5.1 6.1.5.2 6.1.5.3

Local Manager (man Machine Interface) ...................................................................................................... 95

6.2.2.1 6.2.2.2 6.2.2.3 6.2.2.4

FIELD INTRODUCTION....................................................................................................................................... 102

SUB SYSTEMS IMPACTS ..................................................................................................................................... 108

9.3 9.4 9.5 9.6 9.7 9.8

3. ABBREVIATIONS AND DEFINITIONS

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 11/110 12/05/04

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 12/110 12/05/04

Spectrum MHz 1*1 EFR (20%) 1*1 AMR (28%)

0.0 0 20 40 60 % of HR allocation 80 100

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 13/110 12/05/04

4.1.3 BSS CAPACITY

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 14/110 12/05/04

10K2 10K2, 6K7, 10k2, 6k70, 5k90, EFR

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 15/110 12/05/04

6K7, 5K9 6K7, 5K9, 4K75 EFR

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 16/110 12/05/04

5.1.1 BASICS AND SPECIFIC TERMINOLOGY

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 17/110 12/05/04

CMI CMR CMC CMI CMI CMR CMC

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 18/110 12/05/04

UL Mode Command (received)

Global throughput = 11.4 kbits/s

Global throughput = 22.8 kbits/s

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 19/110 12/05/04

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 20/110 12/05/04

7k95 6k70 5k90 4k75

7k95 7k40 6k70 5k90 4k75

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 21/110 12/05/04

CMI CMR CMC CMI CMI CMR CMC

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 22/110 12/05/04

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 23/110 12/05/04

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 24/110 12/05/04

SV713 : AMR Full Rate; SV885 AMR Half Rate

Page 25/110 12/05/04

SV713 : AMR Full Rate; SV885 AMR Half Rate

Spectrum MHz 11 EFR (20%) 11 AMR (28%)