CE - TMO18090 BSS B10-B11 Telecom Evolution PDF

Base Station Subsystem
BSS B10-B11 Telecom Evolutions

TMO18090 Issue 1.0
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent @@YEAR
All rights reserved Alcatel-Lucent @@YEAR

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

BSS B10-B11 Telecom Evolutions - Page 1
Empty page
Switch to notes view!
2
This page is left blank intentionally

Terms of Use and Legal Notices

1. Safetyto
Warning
Switch
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3written consent of Alcatel-Lucent.

4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.

Blank Page
4

Course Outline
1. BSS
B10-B11
Telecom Evolutions
About
This
Course
Course outline
1. Support of Paging Coordination
Technical
2.support
Repeated ACCH
Course objectives
3. NACC for Inter BSS and Inter RAT
4. Topic/Section is Positioned Here

4. Tandem
Free Operation
1. Topic/Section
is Positioned
Herewith AMR-NB
Xxx
Xxx
Xxx
5. Support of A5.3 Ciphering
6. Synchronized Radio Network
7. TRX Dynamic Power Saving

8. Abbreviations



Course Outline [cont.]

6

Course Objectives
Welcome to BSS B10-B11 Telecom Evolutions
Upon completion of this course, you should be able to:

By the end of the course, participants will be able to describe the new telecom B11
features and their telecom impacts.


Course Objectives [cont.]

8

About this Student Guide
Conventions
used
in this guide
Switch
to notes
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Where you can get further information

If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]
10

Self-assessment of Objectives
Contract number :
At the end of each

Course title :
Please, return this
Client (Company, Center) :
Language
:
Switch
section you will be asked to fill this questionnaire

sheet to the trainer at the end of the training
to notes view!
Number of trainees :
Dates from :
to :
Location :
Surname, First name :

Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Instructional objectives
1
Yes (or
globally
yes)
No (or
globally
no)
To be able to XXX
2
11


Comments
Self-assessment of Objectives [cont.]

Instructional objectives
12
Yes (or
Globally
yes)
No (or
globally
no)
Comments

Other comments
Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:
Section 1
Module 1
Support of Paging Coordination
3JK11693AAAAWBZZA Issue 1.0

TMO18090 Issue 1.0

Section 1 Module 1 Page 1
Blank Page
112
BSS B10-B11 Telecom Evolutions Support of Paging Coordination

Base Station Subsystem BSS B10-B11 Telecom Evolutions
Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Module Objectives
Upon completion of this module, you should be able to:
Describe the purpose of the "Support of Paging Coordination in the BSS"
feature and its Telecom and O&M impacts
113


Module Objectives [cont.]
114


Table of Contents
Page

1 What Is the Purpose of this Feature?
1.1 Paging Coordination Principle in B10
2 How Does It Work?
2.1 Overall Description
3 What Are the Telecom Impacts?
3.1 CS Paging Requests Processing
4 What Are the O&M Impacts?
4.1 Feature Activation
4.2 Performance Management
115


7
8
11
12
13
17
18
20
21
22
Table of Contents [cont.]

116


117


Do you remember the CS paging coordination in B10?

Select the correct statements.
In NMO-II or NMO-III, the MS cannot receive CS paging while in Packet

Transfer Mode
The Gs interface is a pre-requisite to fully support the DTM feature
If the network operates in NMO-I, there is no Gs interface between the MSC
and the SGSN
In case of NMO-I, the paging coordination is done by the core network
(between the MSC and the SGSN)
Paging coordination is an Alcatel-Lucent specific feature
118


1.1 Paging Coordination Principle in B10 [cont.]
Without paging coordination, CS Paging messages are always broadcast

through the CCCH/PCH channel, even if the MS is in PTM mode.
PCH
BSC
CS
paging
CS
paging
MSC
Without
Gs interface
PDCHs
MFS
Serving cell
PACCH
119
CS
paging


SGSN
1.1 Paging Coordination Principle in B10 [cont.]
With paging coordination in the SGSN, CS paging messages for GPRSattached MS are conveyed from the MSC to the SGSN through the Gs
interface. It corresponds to the Network Mode of Operation I (NMO-I).
Dedicated
mode
BSC
TCH
MSC
Paging coordination
in the SGSN using
the Gs interface
CS
paging
Serving cell
1 1 10
PACCH
MFS
CS
paging


CS
paging
CS
paging
Gs
SGSN
The support of paging coordination improves CS paging performance, as

it allows to send CS paging messages through the PACCH.
In B11, this procedure can be fully performed in the BSS.
TCH
Paging coordination
in the BSS
BSC
Dedicated
mode
CS
paging
CS
paging
CS
paging
CS
paging
PCH
GSL
CS
paging
Serving cell
1 1 11
PACCH
MFS
MSC
Without
Gs interface
SGSN
CS
paging

There are two ways to support paging coordination:

Prior to B11, paging coordination is performed in the SGSN. In such a case, CS paging messages for GPRSattached MS are conveyed from the MSC to the SGSN through the Gs interface, which allows the SGSN to
perform the paging coordination. This corresponds to the Network Mode of Operation I.
In B11, paging coordination is performed in the BSS. If no Gs interface is available then CS paging
coordination has to be fully performed in the BSS.

2 How Does It Work?
1 1 12


2 How Does It Work?
2.1 Overall Description
With CS paging coordination in the BSS, the BSC has to forward to the
MFS CS Paging requests received from the MSC.
Knowing that the BSC is aware of neither the MS location nor the MS
mode (PTM or not), and the fact that we have to be very careful with
the GSL load, can you guess which kind of information shall be sent to
the MFS?
Select the correct answer.
Indication about the Paging Area
The cell the MS camps on
List of all cells managed by the BSC
MS Location Area
MS IMSI
PTM/non-PTM mode
Nothing
1 1 13


2 How Does It Work?
2.1 Overall Description [cont.]
The BSC forwards to the MFS CS Paging requests received from the MSC in order
to allow the MFS to send the paging requests on the PACCH channel.
The BSC also broadcasts all CS paging requests to the MS through the PCH
channel.
Paging coordination in the BSS
BSC
PCH
CS
paging
CS
paging
CS
paging
CS
paging
IMSI
GSL
MFS
MSC
Without
Gs interface
SGSN
Serving cell
MS in PIM
MFS discards the Paging Request
1 1 14

CS paging coordination in the BSS is performed in 3 steps:

1. CS paging requests are received from the MSC.
2. The BSC forwards CS paging requests to the MFS via the GSL (using BSCGP) after filtering. In any case the
BSC also broadcasts all CS paging requests to the MS through the PCH channel (for all cells corresponding to
the Paging Area and managed by the BSC).
3. On receipt of the CS paging requests sent by the BSC and when applicable (i.e. for MS in PTM mode), the
MFS sends these CS paging requests to the MS through the PACCH channel (for the cell the MS camps on).
Management of the IMSI by the MFS

When CS paging coordination is performed in the BSS, no Paging Area is provided within CS Paging Requests
forwarded by the BSC but only the IMSI. Therefore the MFS has to build and maintain a set of IMSI vs MS
Context relationships for all MS in PTM mode.

2 How Does It Work?
The BSC forwards to the MFS CS Paging requests received from the MSC in order
to allow the MFS to send the paging requests on the PACCH channel.
The BSC also broadcasts all CS paging requests to the MS through the PCH
channel.
TCH
Dedicated
mode
Paging coordination
in the BSS
BSC
CS
paging
CS
paging
CS
paging
CS
paging
CS
paging
PCH
PACCH
GSL
MFS
MSC
Without
Gs interface
SGSN
CS
paging
Serving cell
MS in PTM mode
will be paged faster on the PACCH
than on the PCH
1 1 15

CS paging coordination in the BSS is performed in 3 steps:

1. CS paging requests are received from the MSC.
2. The BSC forwards CS paging requests to the MFS via the GSL (using BSCGP) after filtering. In any case the
BSC also broadcasts all CS paging requests to the MS through the PCH channel (for all cells corresponding to
the Paging Area and managed by the BSC).
3. On receipt of the CS paging requests sent by the BSC and when applicable (i.e. for MS in PTM mode), the
MFS sends these CS paging requests to the MS through the PACCH channel (for the cell the MS camps on).
Management of the IMSI by the MFS

When CS paging coordination is performed in the BSS, no Paging Area is provided within CS Paging Requests
forwarded by the BSC but only the IMSI. Therefore the MFS has to build and maintain a set of IMSI vs MS
Context relationships for all MS in PTM mode.

2 How Does It Work?
Are the following statements about the CS Paging coodination in the

BSS true or false?
Match the correct answers.
The MFS is responsible for checking if the MS is in PTM mode

and if so, to find the cell the MS camps on which is clearly
something new for the MFS
CS paging requests for non-GPRS attached MS or MS not in
PTM mode are also conveyed on the GSL
True
The two ways to perform Paging Coordination (in BSS / in

SGSN) can be handled simultaneously for a given BSS
False
Paging Coordination functions were defined first in Release 1999,

as part of the DTM feature
The feature cannot be useful independently from the DTM feature
1 1 16


1 1 17


3.1 CS Paging Requests Processing
A new message PAGING_COORDINATION_REQ is introduced in the

BSCGP to forward CS paging to the MFS.
Fill in the blank boxes on the left with the appropriate number to re-build the
scenario in the right order.
BTS
BSC
MFS
MULTIPLE PAGING
COMMAND (MSn, pgrk)
PAGING (MS5)
PAGING
COORDINATION
_REQUEST
(IMSI1,IMSI2, )
PAGING (MS1)
1 1 18
Start T3113 for MS1
Start T3113 for MS5
T_SEND_MULTIPLE_PAGING_COMMAND
PACKET PAGING
REQUEST (IMSI) on
PACCH
MSC
NB_MAX_MULTIPLE_PAGING_COMMAND PAGING
commands buffered
(or T_SEND_MULTIPLE_PAGING_COMMAND timer elapses)
For each IMSI check the availability of the MS Context

IF PTM mode IMSI found
Multiple paging
command scenario

PAGING_COORDINATION_REQ:
A new message is introduced in the BSCGP to forward CS paging to the MFS. The same new message is used
for both Paging command and Multiple Paging command scenarios.

3.1 CS Paging Requests Processing [cont.]
The MFS has to maintain a set of "IMSI vs MS Context" relationships:
For an MS which leaves the PTM mode, the corresponding "IMSI vs MS

Context" relationship has to be removed from the set.
For an MS which enters the PTM mode, its IMSI has to be retrieved.
In your opinion, how must the IMSI be retrieved?

Select the correct answers.
For a DL TBF, pick the IMSI from a DL LLC PDU

The IMSI is retrieved only during GPRS Attach
For a UL TBF, perform an RA Capacity Update procedure
For a UL TBF, perform the two-phase access procedure
1 1 19


1 1 20


New Parameter
The "Support of Paging Coordination in the BSS" feature is optional. It
shall be activated at BSS level, via the OMC-R:
BSS_PAGING_COORDINATION
1 1 21

BSS_PAGING_COORDINATION:
Enables CS Paging Coordination to be managed in the BSS for MS in Packet Transfer Mode.
The default value is "Disabled".
Recommended rules:
If BSS_PAGING_COORDINATION (BSC)/(MFS) is set to "Enabled", it is highly recommended to set
EN_RA_CAP_UPDATE to "Enabled" for all cells of the corresponding BSS.
If DTM is Enabled for at least one cell within a given BSS, it is highly recommended to activate CS Paging
Coordination for this BSS, either through the Gs Interface (network_operation_mode = "NMO I") or by setting
BSS_PAGING_COORDINATION (BSC)/(MFS) to "Enabled" (network_operation_mode <> "NMO I").
Note
The activation of DTM is NOT a prerequisite to activate the "Support of paging coordination in the BSS"
feature. This feature can be used to simply improve CS paging performance for MS in PTM mode without
having mandatorily DTM in mind.
As Network_Operation_Mode is defined on a per BSS basis, the two ways to perform Paging Coordination
cannot be handled simultaneously for a given BSS. On the other hand, nothing prevents to use both at
Network level.

PM Counters
No new PM counters are needed, as the extra GSL load brought by the
feature can be monitored using 2 PM counters:
NB_PAGING_COMMANDS_RECEIVED_ABIS
NB_PS_PAGING_REQ_GPU
1 1 22

NB_PAGING_COMMANDS_RECEIVED_ABIS (MC925g):
This counter accumulated by the BTS and reported by the BSC counts on a per cell basis the CS + PS
PAGING commands sent on Abis and broadcast on PCH (in case of Multiple Paging, all embedded commands
are counted).
NB_PS_PAGING_REQ_GPU (P391a):
This counter is managed by the MFS and counts on a per GPU basis the PS Paging Requests received through
the Gb interface.

Module Summary
If no Gs interface is available then CS paging coordination has to be

fully performed in the BSS.
With paging coordination in the BSS, the BSC sends all received
paging requests from the MSC both to the PCH and to the MFS.
Paging coordination is mandatory to fully support the DTM feature.
This new feature can be useful independently from the DTM.
The two ways to perform paging coordination cannot be handled

simultaneously for a given BSS.
The feature activation is configured from the OMC-R via the

BSS_PAGING_COORDINATION parameter.
1 1 23


Self-assessment on the Objectives
Please be reminded to fill in the form

Self-Assessment on the Objectives
for this module
The form can be found in the first part
of this course documentation
1 1 24


End of Module
Support of Paging Coordination
1 1 25


Section 1
Module 2
Repeated ACCH

TMO18090 Issue 1.0

Blank Page
122
BSS B10-B11 Telecom Evolutions Repeated ACCH

Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Module Objectives
Describe the purpose of the "Repeated DL FACCH and Repeated UL & DL
SACCH" features and their Telecom and O&M impacts
123


124

Table of Contents
Page

1.1 FACCH and SACCH
1.2 Voice and Signaling Coverage without AMR in B10
1.3 Improved Voice Coverage with AMR in B10
1.4 Improved Coverage in B11
2 How Does It Work?
2.1 Repeated DL FACCH
2.2 Dynamic Activation of RDFACCH
2.3 Repeated DL SACCH
2.4 Repeated UL SACCH
2.5 Dynamic Activation of RSACCH
3.1 RUSACCH and RLS
4.1 RDFACCH Enabling
4.2 RSACCH Enabling
125


7
8
9
10
11
12
13
15
17
19
21
24
25
27
28
29
30

126

127


1.1 FACCH and SACCH
Do you remember FACCH and SACCH?

Select the corresponding signaling channel.
The
FACCH
SACCH is associated with a TCH, and is required to support the high-speed signaling needed during
call establishment and HO management.
The occurrence of the
Insted, the
FACCH
FACCH
SACCH is not fixed in the multiframe, as it is for the
SACCH occurs on a TDMA frame that is reserved for a TCH.
FACCH
SACCH..
An FR TCH uses one TS per TDMA frame, for each frame of the multiframe, except for the frames 12 and 25. The TDMA
frame 12 is used to carry the
FACCH
SACCH and the TDMA frame 25 is an idle frame.
The
FACCH
SACCH multiframe/block is composed of four
FACCH
SACCH period is equal to 480ms.
FACCH
SACCH frames/bursts; thus the
The
FACCH
SACCH is used mainly for the transmission of the radio measurement data.
FACCH
SACCH is also used for SMS transfer during a call.
The multiplexing of TCH and

FACCH
SACCH is possible by means of the frame stealing. This means that a speech
frame carried over a TCH can be replaced by an
FACCH
SACCH frame.
The BTS sends cell-specific information (periodically SYS_INFO 5, 5bis, 5ter, 6) to the MS using
128


FACCH
SACCH.
1.2 Voice and Signaling Coverage without AMR in B10
When AMR speech codecs were introduced, the same Associated Control
Channels (ACCHs) as those used for traditional TCH/FR and TCH/EFR
were re-used. The consequence is that, in poor radio conditions, the
more protected AMR speech codecs have now better performance (in
terms of error rate) than the associated control channels. This results
in an imbalance between voice and signaling.
Call Drop
Voice and
signaling coverage
without AMR
Z
Z
129


BTS
1.3 Improved Voice Coverage with AMR in B10
When AMR speech codecs were introduced, the same Associated Control
Channels (ACCHs) as those used for traditional TCH/FR and TCH/EFR
were re-used. The consequence is that, in poor radio conditions, the
more protected AMR speech codecs have now better performance (in
terms of error rate) than the associated control channels. This results
in an imbalance between voice and signaling.
Improved voice coverage
with AMR
Signaling channels
designed at the
beginning of GSM
less robust than
AMR codec
Call Drop
Z
Z
1 2 10
Risk of call drop

while voice quality
is still OK
at cell border
BTS

AMR codecs are more resistant than the signaling channel (SACCH).
AMR calls can be stopped because of RLT expiry due to persistent bad SACCH quality (while AMR codec still
performing well), in particular in FR usage.
In B10, a shorter-term solution to fix this issue was the Differentiated Radio Link Timeout for AMR calls
feature. It is desirable to use higher RLT values for AMR calls than for Legacy Codecs.
A long-term solution is to strengthen SACCH. This is introduced in B11 with the new Repeated DL FACCH
and Repeated UL & DL SACCH feature.

1.4 Improved Coverage in B11
In B11, the Repeated DL FACCH and Repeated UL & DL SACCH

features improve the robustness of signaling.
Repeated UL & DL SACCH (RSACCH): Extended Coverage & reduction of call
drops.
Repeated DL FACCH (RDFACCH): Improves handover reliability of AMR calls.
Improved coverage with RSACCH and RDFACCH
BTS
1 2 11


2 How Does It Work?
1 2 12


2 How Does It Work?
2.1 Repeated DL FACCH
H fr
ame
When the RDFACCH feature is activated for a given MS, each DL FACCH frame
is sent twice with exactly the same contents. The MS shall, when receiving a
DL FACCH block, always attempt to decode it without combining with any
previously received FACCH block. If the current FACCH block is unsuccessfully
decoded and there was an unsuccessfully decoded FACCH block, a new
decoding using these 2 FACCH blocks shall be performed (soft combining).
RDFACCH is mandatory for Rel-6 mobile stations.
BTS
TCH
fram
e
TCH frame
FACCH n+2,1
TCH frame
TCH frame
FACCH n+1,2
TCH frame
FACCH n+1,1
TCH frame
TCH frame
TCH frame
FACCH n,2
TCH frame
FACCH n,1
TCH frame
LAPDm
FACCH n+2,2
Rel-6
MS
Downlink
AMR
Call
Outcome of
the decoding
process
1 2 13
Soft combining

Without the RDFACCH, the FACCH blocks are decoded without taking into account the history of the
previously sent FACCH blocks.
The main goal of the repeated downlink FACCH feature is to increase the transmission success rate of the
single-block handover commands.
If the current FACCH block is successfully decoded and an identical FACCH block was previously received
(successfully decoded and spaced in time from the current FACCH block), the MS shall not send the LAPDm
frame of the current FACCH block to the LAPDm entity.
If the current FACCH block is successfully decoded and there was no such previously received identical
FACCH block, the LAPDm frame of the current FACCH block is sent to the LAPDm entity.
If the current FACCH block is unsuccessfully decoded and there was an unsuccessfully decoded FACCH
block spaced in time from the current FACCH block, a new decoding using the information from both these
FACCH blocks shall be performed. If this decoding is successful, the LAPDm frame produced by the new
decoding is sent to the LAPDm entity.

2 How Does It Work?
2.1 Repeated DL FACCH [cont.]
Have you understood the RDFACCH mechanism?

Prior to B11, FACCH blocks are decoded without taking into account the history of the
previously sent FACCH blocks
The MS shall, when receiving a DL FACCH block, always attempt to decode it using the soft
combining procedure
The MS performs soft combining only when the two received FACCH blocks are unsuccessfully
decoded
In case of TCH/FR, the transmission of the repeated FACCH is done by leaving one TCH frame
between the two LAPDm frames
The RDFACCH can also be used in case of TCH/HR
The operations of RDFACCH is not transparent to upper layers
Even if RDFACCH could have brought a gain for non-AMR calls, it applies only to AMR calls
1 2 14


2 How Does It Work?
2.2 Dynamic Activation of RDFACCH
AMR Codec-Based Activation

RDFACCH is decided dynamically in the BTS if the DL codec requested
(CMR value) is inferior or equal to a given codec threshold (e.g.
5.9kbps). The codec threshold is an OMC-R parameter for this cell.
BTS
d
te
ea
p
Re
H
CC
FA
TCH
Codec threshold
5.15
RDFACCH
active
5.9
Dynamic activation
as long as the CMR value
is inferior or equal to the codec threshold
1 2 15
H
CC
FA


7.95
10.2
2 How Does It Work?
2.2 Dynamic Activation of RDFACCH [cont.]
Have you understood the dynamic activation of RDFACCH?

Click on each button in the right order to display the steps of this scenario.
MS Rel-6
BTS
FACCH frame n
If new codec inferior to
codec threshold
RDFACCH frame n
TCH frame
CMR (new codec)
C/I evaluation & threshold

comparison
RDFACCH Activation
6
7
1 2 16


2 How Does It Work?
2.3 Repeated DL SACCH

The RDSACCH mechanism means that the BSS may send a DL SACCH frame twice with exactly the
same contents to improve the DL SACCH performance thanks to combining in the MS. When receiving a
DL SACCH block, the MS shall first attempt to decode it without combining. If this decoding fails, then
soft combining using the previous SACCH block shall be performed. RDSACCH and RUSACCH are
mandatory for Rel-6 mobile stations.
CCH
n+3
LAPDm
480ms
1 2 17
480ms
SACCH n+2,2
TCHs
TCHs
480ms
SACCH
SRR=1
SACCH n+2,1
TCHs
TCHs
Soft
combining
SACCH
SRR=1
SACCH n+1,2
TCHs
TCHs
480ms
SACCH
SACCH n+1,1
Soft
combining
SACCH
SRR=1
TCHs
TCHs
SACCH n,1
SACCH
TCHs
TCHs
Soft
combining
BTS
SAC
CH
n+4
Downlink
AMR
Call
Rel-6 MS
Outcome of
the decoding
process
Uplink
480ms

SACCH Repetition Request (SRR)

If a DL SACCH block is incorrectly decoded (prior to combining with any previously received SACCH
block), and the next UL SACCH block is not a repetition as per the Repeated SACCH procedure, then the MS
shall set the SRR in the next UL SACCH block to "Repeated SACCH required" (see 3GPP TS 44.004).
If a DL SACCH block is correctly decoded (prior to combining with any previously received SACCH block),
and the next UL SACCH block is not a repetition as per the Repeated SACCH procedure, the MS shall set the
SRR in the next UL SACCH block to "Repeated SACCH not required".
On BSS side, if a transmitted downlink SACCH block contains a SAPI 0 frame and is not already a repetition,
then it is a repetition candidate.

2 How Does It Work?
2.3 Repeated DL SACCH [cont.]
Have you understood the RDSACCH mechanism?

When the MS cannot decode correctly (before combining) a DL SACCH, it requests for repetition
by setting the SRR bit.
On BTS/LAPDm side, any DL SACCH block can be repeated.
RDSACCH involves only 2 layers: the LAPDm in the BTS on the one hand and the physical layer in
the MS on the other hand.
When the RDSACCH feature is activated, any DL SACCH frame is sent twice.
If the last DL SACCH frame can not be decoded, the MS tries to soft combine it with the previous
frame.
RSACCH is mandatory for Rel-6 MSs, furthermore it cannot be applied to legacy MSs, contrary to
RDFACCH.
1 2 18


2 How Does It Work?
2.4 Repeated UL SACCH
The RUSACCH mechanism means that an MS shall send upon BSS order a UL SACCH frame
twice with exactly the same contents to improve the UL SACCH performance thanks to
combining in the BTS.
SACCH n+4,2
SR0=1
SACCH m+4,2
SACCH n+4,1
SR0=1
TCHs
TCHs
TCHs
480ms
SAC
Soft
combining
SACCH m+4,1
480ms
SACCH m+3,2
TCHs
TCHs
480ms
Soft
combining
SACCH m+3,1
480ms
SACCH m+2,1
TCHs
Soft
combining
TCHs
SACCH n+3,2
TCHs
SACCH n+3,1
SR0=1
TCHs
SACCH n+2,1
TCHs
LAPDm
480ms
Rel-6 MS
1 2 19
CH
n+
BTS
4
Downlink
Outcome of
the decoding
process
Uplink
AMR
Call

SACCH Repetition Order (SRO)

On MS side:
If a transmitted uplink SACCH block contains a SAPI 0 frame and is not already a repetition, then it is a
repetition candidate.
If an SACCH block is a repetition candidate and if the last correctly received SACCH Repetition Order
was set to SRO, then the MS shall repeat this SACCH block at the next SACCH block period.
On BSS side:
When receiving a UL SACCH block, the BSS may first attempt to decode it without combining with any
previously received SACCH block. If this decoding fails, then a new decoding using the information from
this SACCH block and from the SACCH block received at the previous SACCH block period, may be
performed.

2 How Does It Work?
2.4 Repeated UL SACCH [cont.]
Have you understood the RUSACCH mechanism?

A UL SACCH block containing a SAPI 0 frame, which is not already repeated, is a repetition candidate.
A UL SACCH block containing an SMS, if it is not already a repetition, then it is also a repetition
candidate.
The SRO bit shall be set in the SACCH DL frames in order to tell the MS to repeat the UL SACCH frames.
When the RUSACCH feature is activated, same mechanism as for the RDFACCH, each UL SACCH frame is
sent twice systematically.
When the SACCH block n has to be repeated, its repetition is performed at SACCH block period n+1.
The BTS does not know if a UL SACCH frame is a repetition or not.
The BTS should always try to perform combining between successive SACCH blocks, even if RUSACCH is
not currently activated.
1 2 20


2 How Does It Work?
2.5 Dynamic Activation of RSACCH
The RDSACCH is activated if at least 3 SRR bits set to 1 have been

received in a window whose size is equal to 10 successive UL SACCH
periods. Inversely, the RDSACCH is deactivated if less than 3 SRR bits
set to 1 have been received in the decision window. A similar algorithm
is used for the RUSACCH. The state of RSACCH activation shall be
updated in every SACCH period.
In the example below, is the RDSACCH activated or not?
Select the correct answer for each SACCH period.
SACCH Period
10
11
12
13
14
15
16
17
SRR Value
SRR Sum
0/1
1/2
2/3
3/4
4/5
5/6
5/7
5/8
6/9
6/10
6/10
5/10
4/10
3/10
2/10
2/10
3/10
RDSACCH
activated?
Yes
No
1 2 21

Activation of RDSACCH
The RDSACCH is activated if at least REP_DL_SACCH_THRES SRR bits set to 1 have been received in a
window whose size is equal to REP_DL_SACCH_WS successive UL SACCH periods. Inversely, the RDSACCH is
deactivated if less than 3 SRR bits set to 1 have been received in the decision window.
Activation of RUSACCH
The RUSACCH is activated if at least REP_UL_SACCH_THRES UL SACCH messages have not been correctly
received before combining in a window whose size is equal to REP_UL_SACCH_WS successive UL SACCH
periods. Inversely, the RUSACCH is deactivated if less than REP_UL_SACCH_THRES UL legacy SACCH
messages have not been correctly received before combining in the window. This means the BTS shall
always try to first decode the SACCH before any combining.
Note
REP_DL_SACCH_THRES and REP_DL_SACCH_WS are constants in the DLS defined at BSC level. They are
respectively set by default to 3 and 10.
REP_UL_SACCH_THRES and REP_UL_SACCH_WS are constants in the DLS defined at BSC level. They are
respectively set by default to 3 and 10.

2 How Does It Work?
2.5 Dynamic Activation of RSACCH [cont.]
The RDSACCH is also triggered when the UL RLT counter is inferior or

equal to the value of RADIOLINK_REP_DL_SACCH. This avoids blocking
scenarios and enables to react in case of rapid UL field drops (i.e. in
case the SRR is not received anymore due to bad UL quality).
RLS Counter
RADIOLINK_TIMEOUT_BS
RADIOLINK_RECOVERY_THRES
BTS
10
Rel-6 MS
RDSACCH
activation
1 2 22
09
RADIOLINK_REP_DL_SACCH
Bad
UL SACCH

RADIOLINK_REP_DL_SACCH is set by default to 10 (i.e. equal to RADIOLINK_RECOVERY_THRES (=

N_BSTXPWR_M) - 3) to give time to the BSS to set the power output of the BTS and of the MS to its
maximum value (recovery mechanism).

Exercise
Have you understood the RUSACCH, RDFACCH and RDSACCH
mechanisms?
Match each item on the left with the corresponding features.
AMR Codec-based dynamic activation

Dynamically activated using SRR or RLT procedures
Mandatory for Rel-6 MS
RUSACCH
It can be applied to legacy (pre-Rel-6) MS
RDSACCH
Each frame is sent twice
RDFACCH
A frame may be sent twice

New SACCH Repetition Order (SRO) field
1 2 23


1 2 24


3.1 RUSACCH and RLS
The introduction of RUSACCH has an impact on the receiving principle

of SACCH blocks and on the Radio Link Supervision (RLS).
Outcome of
the first decoding
RLS Counter
+
Outcome of
the second decoding
Soft combining
Rel-6
MS
BTS
1 2 25
18
17
16
15
14
13
12
11
10
09
Bad
UL SACCH

SACCH Block Receiving Procedure and Radio Link Supervision

In B11, with the possibility of a repeated UL SACCH, the following principle shall be used:
When an SACCH block is received, there's a first decoding attempt without combining:
If the decoding is performed, then the RLT counter is incremented by 2.
If the decoding is not performed, then a second decoding is attempted by combining with the previous
SACCH block:
If the second decoding is successful, then the RLT counter is incremented by 2.
If the second decoding failed, then the RLT counter is decremented by 1.

3.1 RUSACCH and RLS [cont.]
The introduction of RUSACCH has an impact on the receiving principle

of SACCH blocks and on the Radio Link Supervision (RLS).
Outcome of
the first decoding
RLS Counter
+
Outcome of
the second decoding
Soft combining
Rel-6
MS
BTS
1 2 26
17
16
15
14
13
12
11
10
09
Bad
UL SACCH

SACCH Block Receiving Procedure and Radio Link Supervision

In B11, with the possibility of a repeated UL SACCH, the following principle shall be used:
When an SACCH block is received, there's a first decoding attempt without combining:
If the decoding is performed, then the RLT counter is incremented by 2.
If the decoding is not performed, then a second decoding is attempted by combining with the previous
SACCH block:
If the second decoding is successful, then the RLT counter is incremented by 2.
If the second decoding failed, then the RLT counter is decremented by 1.

1 2 27


4.1 RDFACCH Enabling
New Parameters
The RDFACCH feature is optional. It can be enabled at cell level.
EN_REP_DL_FACCH
REP_DL_FACCH_LEGACY_SUPPORT
REP_DL_FACCH_THRES_AMR_FR
REP_DL_FACCH_THRES_AMR_HR
REP_DL_FACCH_THRES_AMR_WB
1 2 28

EN_REP_DL_FACCH
Definition: Enables repeated downlink FACCH for AMR calls.
Instance: cell, changeable.
Range/default value: Three levels: 0: Repeated DL FACCH not enabled (default), 1: Repeated DL FACCH enabled for LAPDm
command frames,2: Repeated DL FACCH enabled for LAPDm command frames, and also for LAPDm response frames (valid only for
the MS having indicated the support of the feature by Repeated ACCH Capability bit=1).
REP_DL_FACCH_LEGACY_SUPPORT
Definition: Legacy support for Repeated Downlink FACCH for AMR calls.
Remarks: This parameter is relevant only if Repeated Downlink FACCH is enabled (EN_REP_DL_FACCH parameter). This parameter
concerns only the LAPDm command frames.
Instance: cell , changeable.
Range/default value: 0: Repeated DL FACCH enabled only for the AMR MSs having indicated the support of the feature by
Repeated ACCH Capability bit=1 (default), 1: Repeated DL FACCH enabled for all AMR MSs.
REP_DL_FACCH_THRES_AMR_FR
Definition: Repeated DL FACCH activation threshold for AMR FR. Dynamic activation is done as long as CMR is inferior or equal to the
threshold value.
Instance: cell, changeable
Range/default: 0=off, 1=4.75kbps, 2=5.15kbps, 3=5.9kbps (default), 4=6.7kbps, 5=7.4kbps, 6=7.95kbps, 7=10.2kbps, 8=12.2kbps
REP_DL_FACCH_THRES_AMR_HR
Definition: Repeated DL FACCH activation threshold for AMR HR. Dynamic activation is done as long as CMR is inferior or equal to the
threshold value.
Range/default: 0=off, 1=4.75kbps, 2=5.15kbps, 3=5.9kbps (default), 4=6.7kbps, 5=7.4kbps
REP_DL_FACCH_THRES_AMR_WB
Definition: Repeated DL FACCH activation threshold for AMR WB. Dynamic activation is done as long as CMR is inferior or equal to the
threshold value.
Range/default: 0=off, 1=6.60kbps (default), 2=8.85kbps, 3=12.65kbps

4.2 RSACCH Enabling
New Parameters
The RSACCH feature is optional. It can be enabled at cell level.
EN_REP_SACCH
L_RXQUAL_UL_P_AMR_RXACCH
L_RXQUAL_DL_P_AMR_RXACCH
1 2 29

EN_REP_SACCH
Definition: Enables repeated SACCH for SAPI 0 frames in case of AMR calls (for MSs having indicated the
support of the feature).
Range/default value: Flag 0: Repeated SACCH not enabled (default), 1: Repeated SACCH enabled.
Definition: Counter threshold of UL RTL counter to activate Repeated DL SACCH.
Range: 1 to 128 (default: 10)
L_RXQUAL_UL_P_AMR_RXACCH
Definition: Lower uplink quality threshold for power control for AMR calls with activated Repeated DL
FACCH and Repeated SACCH.
Range: 0 to 7 (default: 3) - (use the value of L_RXQUAL_UL_P for migration).
L_RXQUAL_DL_P_AMR_RXACCH
Definition: Lower downlink quality threshold for power control for AMR calls with activated Repeated DL
FACCH and Repeated SACCH.
Range: 0 to 7 (default: 3) - (use the value of L_RXQUAL_DL_P for migration).

New Counters
NB_MS_REPEATED_ACCH_CAPABLE
NB_CALLS_RFACCH_ACTIVATED
NB_CALLS_RSACCH_ACTIVATED
NB_AMR_TCH_DROP_RLF_TRX
NB_AMR_TCH_DROP_RLF_TRX_RSACCH
1 2 30

NB_MS_REPEATED_ACCH_CAPABLE (MC990)
Definition:
Number of calls for which the mobile stations support the repeated ACCH capability.
Trigger
condition: Each time the BSC gets for a call the indication of the corresponding MS Repeated ACCH Capability in the classmark
3 IE at the time of Channel Activation or Mode modify messages sending, this counter is incremented by one.
NB_CALLS_RFACCH_ACTIVATED (MC991)
Definition:
Number of calls for which repeated DL FACCH is allowed by the BSC.
Trigger condition: Each time the BSC sends a Channel Activation or a Mode Modify to a BTS indicating that RDFACCH is activated for
LAPDm command frames and/or LAPDm response frames, then this counter is incremented by 1. For Mode Modify trigger, only the
cases where RDFACCH was not activated in the Channel Activation message previously sent by the BSC are counted.
NB_CALLS_RSACCH_ACTIVATED (MC992)
Definition:
Number of calls for which repeated SACCH (DL or UL) is allowed by the BSC.
Trigger
condition: Each time the BSC sends a Channel Activation or a Mode Modify to a BTS indicating that RSACCH (UL and/or DL) is
activated, then this counter is incremented by 1. For Mode Modify trigger, only the cases where RSACCH was not activated in the
Channel Activation message previously sent by the BSC are counted.
NB_AMR_TCH_DROP_RLF_TRX (MC993)
Number of AMR TCHs (NB or WB AMR) for which Repeated SACCH is not activated, dropped in TCH established phase due to radio link
failure (radio link timeout or Lapdm timer expiry), per TRX. For TCH using AMR codecs (NB or WB) but for which the feature Repeated
SACCH is not activated by the BSC:
1)Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio link failure" is received on Abis interface
for a TCH channel (after successful seizure).
2) Whenever a 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of call.
NB_AMR_TCH_DROP_RLF_TRX_RSACCH (MC994)
Number of AMR TCHq (NB or WB AMR) for which Repeated SACCH is activated, dropped in TCH established phase due to radio link
failure (radio link timeout or Lapdm timer expiry), per TRX. This counter takes into account TCH in traffic. For TCH using AMR codecs
(NB or WB) but for which the feature Repeated SACCH is activated by the BSC:
1)Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio link failure" is received on Abis interface
for a TCH channel (after successful seizure).
2)Whenever a 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of call.

Module Summary
The Repeated DL FACCH (RDFACCH) and Repeated UL & DL SACCH

(RSACCH) features improve the robustness of signaling.
The RDFACCH mechanism means that each DL FACCH frame is sent

twice.
The RUSACCH mechanism means that an MS shall send upon BSS order
a UL SACCH frame twice.
The RDSACCH mechanism means that the BSS may send a DL SACCH
frame twice.
The dynamic activation of RDFACCH is AMR Codec based.
1 2 31


Module Summary [cont.]
RSACCH is also dynamically activated using a specific algorithm (SRR or

RLT).
The RSACCH and RDACCH are not linked.
RDFACCH and RSACCH can be activated only for calls using AMR-NB or
AMR-WB.
Both features can be enabled at cell level.
Both features have been introduced in Rel-6 specifications and are

mandatory for Rel-6 MSs.
1 2 32



for this module
1 2 33


End of Module
Repeated ACCH
1 2 34


Section 1
Module 3
NACC for Inter BSS and Inter RAT

TMO18090 Issue 1.0

Blank Page
132
BSS B10-B11 Telecom Evolutions NACC for Inter BSS and Inter RAT
Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Module Objectives
Describe the purpose of the "Inter-BSS/RAT NACC" feature and its Telecom
and O&M impacts
133

134

Table of Contents
Page

1.1 NACC in B10
1.2 Principle of NACC in B10
2 How Does It Work?
2.1 Inter-BSS/RAT NACC Principles in B11
2.2 Inter-BSS/RAT Principles
2.3 Cell Reselection: 2G-to-2G Inter-BSS Cell Reselection
2.4 Cell Reselection: 3G-to-2G Cell Reselection
3.1 Inter-BSS/RAT NACC Principles
4.1 Configuration Management
135

7
8
9
11
12
13
15
16
17
18
19
20
21
22

136

137

1.1 NACC in B10
Do you remember NACC?

With NACC, the network can send SI1, SI3 and SI13 of target cell after PS cell reselection
The NACC is mandatory for Release 4 MSs supporting the GERAN feature Package 1
It has been introduced in ALU BSS B10 release
In B10, the NACC could occur only for a source and target cells mapped on the same GPU
In B10, the NACC could occur for a source and target cells mapped on 2 GPUs belonging
to the same MFS
In B10, the NACC could occur for a source and target cells mapped on 2 GPUs belonging
to different MFSs
SI1 and SI3 are provided by the BSC to the MFS, SI13 is built by the serving MFS
138

The NACC feature has been

introduced in B9. This
feature allows to decrease
the
GPRS service outage
during intra-BSS PS cell
reselection, by providing the
MS with a set of System
Information (SI) messages,
required to access the new
cell, before the MS leaves
the old cell.
SGSN
BTS
A
BSS1
BTS
B
Cell A
Throughput
(Kbit/s)
Intra-BSS
BSS1
Cell B
Reduced service
outage
Average
throughput
t0
139
t1 t2
t3
Time
(s)
The feature reduced the service outage time for an MS in packet transfer mode from a couple of seconds
down to 300-700 ms by giving the network a possibility to assist the MS before and during the cell change.
The assistance is given as sending of neighbouring cell system information.

1.2 Principle of NACC in B10 [cont.]
The NACC feature has been

introduced in B9. This
feature allows to decrease
the
GPRS service outage
during intra-BSS PS cell
reselection, by providing the
MS with a set of System
Information (SI) messages,
required to access the new
cell, before the MS leaves
the old cell.
Before B11,
inter-BSS NACC
not supported
SGSN
BTS A
BSS1
BTS B
Cell A
Throughput
(Kbit/s)
Service outage
Average
throughput
4s
t0
1 3 10
BSS2
Cell B
t1
t2
t3
Time
(s)

In B11, the benefits of NACC are

extended to the inter-BSS and
3G-to-2G
Cell
Reselection
Cases. The NACC feature is
based on RAN Information
Management (RIM), a generic
mechanism for the exchange of
information between two RAN
nodes (GERAN or UTRAN). With
the introduction of RIM-NACC,
the GPRS service outage during
inter-BSS or inter-ratting PS cell
reselection
can
also
be
improved. In B11, the inter-BSS
NACC can occur between 2 MFSs.
SGSN
BTS A
BSS1
BTS B
Cell A
Throughput
(Kbit/s)
BSS2
Cell B
Reduced service
outage
Average
throughput
Inter-BSS
PS cell reselection
is improved
t0
1 3 11
t1 t2
t3
Time
(s)

2 How Does It Work?
1 3 12

2 How Does It Work?
2.1 Inter-BSS/RAT NACC Principles in B11
What Is RIM?
The RAN Information Management (RIM) procedures provide a generic
mechanism for the exchange of arbitrary information between two RAN
nodes, located either in a GERAN or in a UTRAN access network.
Current BSS
or RNC
RANINFORMATIONACK
RANINFORMATIONREQUEST/
Multiple
Report
RANINFORMATION/
Multiple Report
(ACK)
Target BSS
SGSN(s)
SI Request
RANINFORMATION/
Initial
Multiple Report
1 3 13
The SGSNs
simply perform a relay
of the messages
SI Change
The RAN Information Management (RIM) procedures allow to send information between BSCs/RNCs via one
or more SGSNs. The SGSNs simply perform a relay of the messages (possibly inter-SGSN). Any relation
between messages is transparent for the SGSN.
Two main procedures are defined:
RAN Information Request procedure: initiated by a Controlling BSS/RNC when it requires information (in
NACC case: SI) from another Serving BSS/RNC, or when it requires stop of event driven reports from another
Serving BSS/RNC.
RAN Information Send procedure: initiated by a Serving BSS when it has information to be sent to
another Controlling BSS/RNC. The procedure may be event-triggered (e.g. SI change) or scheduled (e.g. by
a request procedure). Sending BSS may request acknowledgement of the information.
Routing and addressing of the messages are done through:
cell identifiers for the BSS.
A BSS is addressed by the Routing Area Identity (RAI) + Cell Identity (CI) of one of its cells.
RNC identifiers for RNC.
An RNC is addressed by the Routing Area Identity + RNC-Id.

2 How Does It Work?
2.1 Inter-BSS/RAT NACC Principles in B11 [cont.]
What Is RIM?
The RAN Information Management (RIM) procedures provide a generic
mechanism for the exchange of arbitrary information between two RAN
nodes, located either in a GERAN or in a UTRAN access network.
Current BSS
or RNC
RANINFORMATION/
Multiple Report
(ACK)
RANINFORMATIONACK
Target BSS
SGSN(s)
The SGSNs
simply perform
a relay of the messages
SI Request
1 3 14
SI Change
The RAN Information Management (RIM) procedures allow to send information between BSCs/RNCs via one
between messages is transparent for the SGSN.
Two main procedures are defined:
RAN Information Request procedure: initiated by a Controlling BSS/RNC when it requires information (in
NACC case: SI) from another Serving BSS/RNC, or when it requires stop of event driven reports from another
Serving BSS/RNC.
RAN Information Send procedure: initiated by a Serving BSS when it has information to be sent to
another Controlling BSS/RNC. The procedure may be event-triggered (e.g. SI change) or scheduled (e.g. by
a request procedure). Sending BSS may request acknowledgement of the information.
Routing and addressing of the messages are done through:
cell identifiers for the BSS.
A BSS is addressed by the Routing Area Identity (RAI) + Cell Identity (CI) of one of its cells.
RNC identifiers for RNC.
An RNC is addressed by the Routing Area Identity + RNC-Id.

2 How Does It Work?
2.2 Inter-BSS/RAT Principles
Have you understood the RIM procedure?

The RAN Information Management is an Alcatel-Lucent specific feature

The RIM procedure allows to send information between BSCs/RNCs via one or more SGSNs
This information may not be transparent for the SGSN
The RAN Information Send procedure is an event-triggered mechanism. It is used only when the
set of NACC-related SI is changed
This procedure may be event triggered or scheduled
A BSS is addressed by the RAI + Cell Identity (CI) of one of its cells
An RNC is addressed by the RAI + RNC-Id+Cell Identity (CI) of one of its cells
1 3 15

2 How Does It Work?
2.3 Cell Reselection: 2G-to-2G Inter-BSS Cell Reselection
Inter-BSS NACC Procedure

In order to provide the MS with SI of external adjacent cells, the
current BSS/RNC shall obtain them from another target BSS, via the
SGSN. The RAN Information Management (RIM) procedure allows to send
information between BSCs/RNCs via one or more SGSNs. The RIM allows
a BSS to get System Information of 2G cells located in another BSS.
SGSN 1
SGSN 2
2G-to-2G
PS Cell Reselection
Serving cell
Target cell
BSS 1
BSS 2
1 3 16
RIM-NACC
procedure
In the inter-BSS case, the exchanges with the MS are the same as in Release 4 NACC.
In order to provide the MS with SI of external adjacent cells, the Controlling BSS shall obtain them from
another Serving BSS, via the SGSN.
The RAN Information Management (RIM) procedure allows to send information between BSCs/RNCs via one
between messages is transparent for the SGSN, i.e. a request/response exchange between RIM applications,
is routed and relayed as two independent messages by the SGSN.
The support of RIM by the BSS and the SGSN is negotiated thanks to the Bitmap Mechanism of BSSGP
Interface feature.
Routing and addressing of the messages is done through cell identifiers for the BSS and through RNC
identifiers for RNC.
SIs are requested for a given 2G cell. The sets of SIs to be sent to the MS are SI1, SI3 (both provided by the
BSC to the MFS) and SI13 (built by the serving MFS).
In B11, the inter-BSS NACC can occur between 2 MFSs or also between 2 GPUs belonging to the same MFS
but supporting different BSSs. In this last case, no inter-GPU signaling is used. The usual procedure via the
SGSN is also used between 2 GPUs in the same MFS.

2 How Does It Work?
2.4 Cell Reselection: 3G-to-2G Cell Reselection
Inter-RAT NACC Procedure

In order to provide the MS with SI of external adjacent cells, the
current BSS/RNC shall obtain them from another target BSS, via the
SGSN. The RAN Information Management (RIM) procedure allows to send
information between BSCs/RNCs via one or more SGSNs. The RIM allows
a UTRAN to get SI of a target 2G cell.
SGSN 1
SGSN 2
3G-to-2G
PS Cell Reselection
Serving cell
Target cell
UTRAN
BSS 2
1 3 17
RIM-NACC
procedure
In the inter-BSS case, the exchanges with the MS are the same as in Release 4 NACC.
In order to provide the MS with SI of external adjacent cells, the Controlling BSS shall obtain them from
another Serving BSS, via the SGSN.
The RAN Information Management (RIM) procedure allows to send information between BSCs/RNCs via one
between messages is transparent for the SGSN, i.e. a request/response exchange between RIM applications,
is routed and relayed as two independent messages by the SGSN.
The support of RIM by the BSS and the SGSN is negotiated thanks to the Bitmap Mechanism of BSSGP
Interface feature.
Routing and addressing of the messages is done through cell identifiers for the BSS and through RNC
identifiers for RNC.
SIs are requested for a given 2G cell. The sets of SIs to be sent to the MS are SI1, SI3 (both provided by the
BSC to the MFS) and SI13 (built by the serving MFS).
In B11, the inter-BSS NACC can occur between 2 MFSs or also between 2 GPUs belonging to the same MFS
but supporting different BSSs. In this last case, no inter-GPU signaling is used. The usual procedure via the
SGSN is also used between 2 GPUs in the same MFS.

1 3 18

3.1 Inter-BSS/RAT NACC Principles
Have you understood the Inter-BSS/RAT NACC procedure?

Click on each button in the right order to display the steps of this scenario.
Current MFS/
RNC
MS
Data block
Packet Cell Change Continue
Target
MFS
2
3
Packet Cell Change Notification
Packet Neighbour Cell Data
Packet Neighbour Cell Data
RAN- Information
RAN- Information Request
Polling
1 3 19
PAGING_COORDINATION_REQ:
A new message is introduced in the BSCGP to forward CS paging to the MFS. The same new message is used
for both Paging command and Multiple Paging command scenarios.

1 3 20

New Parameters
The Inter-BSS/Inter-RAT NACC feature is optional. It can be activated at
BSS level.
EN_RIM_NACC
T_RIR
T_RI
T_MULTIPLE_REPORT
N_RIM_RETRIES
1 3 21
EN_RIM_NACC:
This parameter enables inter-BSS and inter-RAT NACC.
It can take the following values:
0: RIM NACC feature disabled
1: Inter_BSS_NACC only enabled
2: Inter_RAT_NACC only enabled
3: Inter_BSS_NACC and Inter_RAT NACC enabled
T_RIR:
The timer supervising the reception of RAN Information.
Changeable: 1 255 sec/ 10
T_RI
The timer supervising the reception of RAN information ACK.
Changeable: 1 255 sec/10
T_MULTIPLE_REPORT:
The timer supervising the reception of the following RAN information with multiple report MFS.
Changeable: 15 360 mn/60
N_RIM_RETRIES:
The number of times a RAN procedure is sent before giving up (in case of no answer).
Changeable: 1 255 /2
New Counters
NB_SERVING_INTER_BSS_NACC
NB_SERVING_INTER_RAT_NACC
NB_CONTROLLING_INTER_BSS_NAC
TIME_SPENT_RIM_NACC_PROCEDURE
TIME_SOURCE_RIM_NACC_CELL_RESEL
MAX_SOURCE_RIM_NACC_CELL_RESEL_TIME
MIN_SOURCE_RIM_NACC_CELL_RESEL_TIME
1 3 22
NB_SERVING_INTER_BSS_NACC:
The number of received RAN-Information-Request from a controlling BSS. Within the granularity period, the MFS counts the number of
RAN-INFORMATION-REQUEST received from a BSS (both single and multiple reports).
Measured object: Target Cell
NB_SERVING_INTER_RAT_NACC:
The number of received RAN-Information-Request from a controlling RNC. Within the granularity period, the MFS counts the number of
RAN-INFORMATION-REQUEST received from a RNC (both single and multiple reports).
NB_CONTROLLING_INTER_BSS_NACC:
The number of successful RAN-Information-Request sent to another BSS. Within the granularity period, the MFS counts the number of
RAN-INFORMATION-REQUEST sent to another BSS (both single and multiple reports).
TIME_SPENT_RIM_NACC_PROCEDURE:
The cumulated time needed to require the SI of the target cell via the RIM procedure. This will allow to estimate the time during
which a RAN-Information-Request PDU is sent and a RAN-Information PDU is received.
TIME_SOURCE_RIM_NACC_CELL_RESEL:
The cumulated time of the successful Network Assisted cell reselection duration in NC0 mode in case of Inter-BSS serving cell. Within
the granularity period, the MFS cumulates the duration of each successful outgoing RIM_NACC cell reselections triggered by the BSS in
the source cell.
MAX_SOURCE_RIM_NACC_CELL_RESEL_TIME:
The
maximum
Network-Assisted
TIME_SOURCE_RIM_NACC_CELL_RESEL.
cell
reselection
duration
in
NC0
mode
maximum
value
of
counter
The
minimum
Network-Assisted
cell
reselection
duration
in
NC0
mode
TIME_SOURCE_RIM_NACC_CELL_RESEL.
minimum
value
of
counter
MIN_SOURCE_RIM_NACC_CELL_RESEL_TIME:
Module Summary
In B11, the benefits of NACC are extended to the inter-BSS and 3G-to2G Cell Reselection cases.
The GPRS service outage during inter-BSS or inter-RAT PS cell

reselection is improved.
RAN Information Management (RIM) is generic mechanism for the
exchange of information between two RAN nodes (GERAN or UTRAN).
For 2G-to-2G Inter-BSS Cell Reselections, the RIM allows a BSS to get
System Information of 2G cells located in another BSS.
For 3G-to-2G Cell Reselections, the RIM allows a UTRAN to get SI of a

targer 2G cell.
The Inter-BSS/Inter-RAT NACC feature is optional. It can be activated

at BSS level.
1 3 23


for this module
1 3 24

End of Module
NACC for Inter BSS and Inter RAT
1 3 25

Section 1
Module 4
Tandem Free Operation with AMR-NB

TMO18090 Issue 1.0

Blank Page
142
BSS B10-B11 Telecom Evolutions Tandem Free Operation with AMR-NB

Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Module Objectives
Describe the purpose of the "Tandem Free Operation (TFO) for AMR-NB"
feature and its Telecom and O&M impacts
143


144


Table of Contents
Page

1.1 TFO Implementation Prior to B11
1.2 Prior to B11
1.3 Principle in B11
2 How Does It Work?
2.1 Do You Remember AMR-NB?
2.2 TFO Negotiation and Decision Algorithm
2.3 AMR Codec Adaptation with TFO
2.3.1 UL Downgrading
2.3.2 DL Downgrading
2.3.3 UL Upgrading
2.3.4 DL Upgrading
2.4 TFO AMR-NB vs TFO Rel.99
3.1 TFO Interoperability with TrFO
3.1.1 2G-2G Interoperability
3.2 TFO Interoperability with UMTS
145


7
8
9
10
11
12
14
16
17
18
19
20
21
22
23
24
28
29
30
31
32

146


147


1.1 TFO Implementation Prior to B11
Do you remember the TFO implementation before B11?

In B10, the AMR-NB and TFO are not supported together by the Alcatel-Lucent BSS
Alcatel-Lucent provides TFO since B7 for legacy Codecs and since B10 for AMR-WB
Calls established with AMR-NB will either stay in AMR with tandeming or use TFO
TFO implementation in B7 is aligned with 3GPP Rel.99 version of TFO. The MS should
be R99
TFO is a prerequisite for AMR-WB. AMR-WB does not make sense without TFO
148


1.2 Prior to B11
Before B11, the AMR-NB and TFO features were not supported
together by the Alcatel-Lucent BSS. Only TFO for legacy codecs (EFR,
FR & HR) is supported since release B7 and since B10 for AMR-WB.
Therefore, in case of AMR-NB, TFO cannot be used, hence a degraded
voice quality (3 transcoding stages). The issue is tandeming in NGN:
G711oIP requires high bandwidth.
MSC
server
Degraded
Speech Quality
due to 3 transcoding
stages
MSC
server
BSS 1
BSS 2
MS 1
MS 2
IP
AMR-NB
AMR-NB
TC
1
G711
MG
No
TFO
149
G711 over IP
MG
G711oIP
requires
high
bandwidth
G711
TC AMR-NB
2
AMR-NB
No
TFO

TFO Implemented in B7
TFO implementation in B7 is aligned with 3GPP Rel.99 version of TFO.
There is no impact on the MS.
TFO is possible with FR, EFR, HR.
TFO is NOT possible with AMR-NB.

Force_TFO_vs_AMR option: Depending on the preference given by the operator, calls established with
AMR-NB will:
either stay in AMR, with tandeming.
or go to TFO, with FR, EFR or HR.
A simple algorithm is used with TFO for codec negotiation:
If both sides support EFR, use EFR, else
If both sides support FR, use FR, else
Use HR.

1.3 Principle in B11
In release B11, the TFO feature can be used together with AMR-NB.
TFO provides a better voice quality by avoiding unnecessary
successive coding and decoding operations in the case of mobile-tomobile calls. Furthermore, with the introduction of the NGN, TFO for
all GSM codecs gets an important application that is related to the
bandwidth saving aspects at the CN level.
MSC
server
High transmission
savings in NGN
MSC
server
Better
Speech Quality
BSS 1
BSS 2
MS 1
MS 2
IP
AMR-NB
AMR-NB
TC
1
AMR-NB MG
TFO
AMR-NB
MG AMR-NB
TrFO
AMR over IP
TC AMR-NB
2
AMR-NB
TFO
Transcoding Functions
Bypassed
1 4 10

Transcoder Free Operation (TrFO) is a Core Network protocol, applicable to the NGN architecture.
TrFO allows to transport speech in the Core Network using GERAN/UTRAN codecs over IP, rather than
G.711. Advantages:
Gain in transmission bandwidth.
Gain in speech quality if the same codec is used over the complete path.
Contrarily to TFO, TrFO is out-of-band, i.e. negotiation is not done in the User Plane (embedded in speech
frames), but in the Control Plane, on a specific interface.
The AMR +TFO feature improves the speech quality of mobile-to-mobile calls and TFO-TrFO interaction in
the NGN core network.
AMR-WB without TFO does not make sense.

2 How Does It Work?
1 4 11


2 How Does It Work?
2.1 Do You Remember AMR-NB?
Do you remember the Codec Mode Adaptation Mechanism?

The BTS adapts the codec to the radio link condition among a subset of codecs
The TC adapts the codec to the radio link condition among a subset of codecs
With AMR-NB, maximum 4 codec modes are used for a given call
The same codec subset is used for both the Uplink and the Downlink
The codecs used in UL and used in DL can be different: the adaptation is
independent in each direction
1 4 12


2 How Does It Work?
2.1 Do You Remember AMR-NB? [cont.]
Do you know the AMR-related vocabulary?

Match each term from the list on the left to its correct definition from the list on
the right.
The maximum number of codec modes
supported for the ongoing call
Active Codec Set (ACS)
The codec mode to use in DL and UL at TCH

activation
Supported Codec Set (SCS)
The list of all codec modes supported by the

BSS for a given AMR codec
Maximum Active Codec

Set (MACS)
The list of codec modes usable for the ongoing

call
Initial Codec Mode (ICM)

Common Active Codec Set
(CACS)
ACS used for TFO, based on ACS on both sides
Common Supported Codec

Set (CSCS)
Intersection of SCS on both sides
1 4 13

Rule for implicit ICM:
If ACS contains 1 mode, then this shall be the Initial Codec Mode.
If ACS contains 2 or 3 modes, then the Initial Codec Mode shall be the most robust mode of the set (with
the lowest bit rate).
If ACS contains 4 modes, then the Initial Codec Mode shall be the second most robust mode of the set
(with the second lowest bit rate).

2 How Does It Work?
2.2 TFO Negotiation and Decision Algorithm
The establishment of a TFO

call begins with a negotiation
phase. Each TFO partner
exchanges by means of TFO
messages (TFO_REQ,
TFO_ACK) the local used
codec type, the Active Codec
modes Set (ACS) and the
Supported Codec modes Set
(SCS). Each partner runs in
the TC a decision algorithm to
decide if TFO can be
established and on what
codec type and set of codec
modes.
Both radio legs

use or offer AMR-NB
LACS == DACS
Yes
Immediate
TFO Establishment
No
FR HR
Matching?
Yes
Immediate
TFO Establishment
FR HR
Optimization
No
Calculate
OACS and IACS
OACS
No
Codec Mismatch
Resolution
Yes
IACS == OACS?
Yes
No
Yes
IACS
sub-set of
OACS?
No
Change ACS to
OACS (if supported)
Immediate
TFO Establishment
Codec Mode
Optimization
TFO Establishment
on OACS
1 4 14

The decision algorithm is standardized by 3GPP:

LACS == DACS: Establishes immediate TFO if the local and distant ACS are identical. Example: Enable
immediate TFO establishment within one operator's homogeneous network. The operator's choice is always
acceptable and needs no optimization.
FR HR Matching: The goal is to enable immediate TFO between 3G channels and 2G FR and 2G HR
channels.
A Common ACS (CACS) is acceptable for immediate TFO establishment without consideration of the OACS if
all of the following conditions are fulfilled:
one radio leg uses FR_AMR or UMTS_AMR_2, the other uses HR_AMR [for AMR TFO].
the CACS is contiguous.
the CACS fulfills the acceptability rule.
FR HR Optimization: Takes place after immediate TFO establishment in the case of FR HR
Matching. The FR_AMR-side adopts the ACS of the HR_AMR-side, if this ACS is supported and the
optimization mode allows an ACS change.
Codec Mismatch Resolution: A TFO connection with the currently used AMR codec types will not be
possible, but the remaining codec types have to be investigated.
Codec Type Optimization and Codec Mismatch resolution:
These procedures already exist up to B10 for the GSM EFR, FR and HR codec types. The principle
remains the same but with the specificities linked to AMR-NB. The codec mismatch resolution and
codec type optimization remain delegated to the BSC.
These procedures are optional and driven with the TFO_OPT and TFO_MATCH options. These options
control the overall TFO behavior. They are independent from the codec types or codec modes
involved in the TFO call.
It is not foreseen to support the AMR configuration with optimization allowed, so an ACS change cannot
occur.
2 How Does It Work?
2.2 TFO Negotiation and Decision Algorithm [cont.]

The FR-HR matching allows to establish TFO immediately in case one side uses
FR_AMR and the other HR_AMR. Here is an example of FR-HR matching: One side
uses FR_AMR with a Maximum of Active Codec mode Set of 4 (MACS), the other
side HR_AMR uses a MACS of 3 codec modes. It is possible to establish Immediate
TFO on IACS and on FR-HR matching. But no further optimization is done.
Select the codec modes used within CSCS, OACS and IACS.
Codec
mode
12.20
SCS
ACS
IACS
OACS
CSCS
ACS
SCS
10.20
7.95
7.40
6.70
5.90
5.15
4.75
1 4 15

The decision algorithm is standardized by 3GPP:

LACS == DACS: Establishes immediate TFO if the local and distant ACS are identical. Example: Enable
immediate TFO establishment within one operator's homogeneous network. The operator's choice is always
acceptable and needs no optimization.
FR HR Matching: The goal is to enable immediate TFO between 3G channels and 2G FR and 2G HR
channels.
A Common ACS (CACS) is acceptable for immediate TFO establishment without consideration of the OACS if
all of the following conditions are fulfilled:
one radio leg uses FR_AMR or UMTS_AMR_2, the other uses HR_AMR [for AMR TFO].
the CACS is contiguous.
the CACS fulfills the acceptability rule.
FR HR Optimization: Takes place after immediate TFO establishment in the case of FR HR
Matching. The FR_AMR-side adopts the ACS of the HR_AMR-side, if this ACS is supported and the
optimization mode allows an ACS change.
Codec Mismatch Resolution: A TFO connection with the currently used AMR codec types will not be
possible, but the remaining codec types have to be investigated.
Codec Type Optimization and Codec Mismatch resolution:
These procedures already exist up to B10 for the GSM EFR, FR and HR codec types. The principle
remains the same but with the specificities linked to AMR-NB. The codec mismatch resolution and
codec type optimization remain delegated to the BSC.
These procedures are optional and driven with the TFO_OPT and TFO_MATCH options. These options
control the overall TFO behavior. They are independent from the codec types or codec modes
involved in the TFO call.
It is not foreseen to support the AMR configuration with optimization allowed, so an ACS change cannot
occur.
2 How Does It Work?
The Codec mode adaptation is performed independently on each

direction. But for one direction, the same codec mode is used
from one MS to the other MS.
Codec mode adaptation is always performed for the side having

the worst radio conditions.
1 4 16

The codec mode used in one direction may be different from the one used in the other direction. But
for one direction, the same codec mode is used from one MS to the other MS.
The same codec mode is used for each leg.
Example:
From MS1 in UL to MS2 in DL, AMR-NB 12.2 kbit/s
The codec mode adaptation is performed independently on each direction. But in one direction, the
codec mode adaptation is triggered by both radio interfaces.
Codec mode adaptation is always done for the side having the worst radio conditions.
The principle for codec mode adaptation in ongoing TFO is that the BTS controlling the MS always takes
the final decision to upgrade or downgrade its local uplink direction. This BTS sends the Codec Mode
Command downlink.
The Codec Mode Request for the local uplink direction is taken directly into account and the effective
delay is not higher than in normal connections.
The Codec Mode Request from the remote side in the remote downlink direction is also taken into
account, but it becomes active with a reaction time increased by the round trip delay between both
BTSs.
Upgrading is possible only if both radio links in one direction (first uplink then downlink) are good
enough.
Downgrading is necessary if one (or both) radio link(s) is(are) not good enough.
2.3.1 UL Downgrading
MS1
BTS1
TRAU1
TRAU2
BTS2
MS2
TFO establishment with original codec

The BTS detects
a bad uplink quality
CMC: new codec
(lower rate)
The MS1 uses
immediately
the new codec
CMI: new codec
CMI:
new codec
CMI:
new codec
CMI:
new codec
CMI:
new codec
TFO establishment with new codec
1 4 17

Example:
Command downlink.
BTSs.
enough.
2.3.2 DL Downgrading
MS1
BTS1
TRAU1
TRAU2
BTS2
MS2

The MS
detects a bad
downlink quality
CMR:
new codec
(lower rate)
CMI:
new codec
The BTS
decides to adapt
downlink codec
CMR: new codec
CMI:
new codec
CMR:
new codec
CMI:
new codec
CMR:
new codec
CMI:
new codec
CMC: new codec

The MS2 uses
immediately
the new codec
CMI:
new codec
1 4 18

Example:
Command downlink.
BTSs.
enough.
2.3.3 UL Upgrading
MS1
BTS1
TRAU1
TRAU2
BTS2
MS2

The MS
detects good
downlink quality
BTS1 has measured

good uplink quality,
waits for a CMR from BTS2
BTS1 orders
MS1 to upgrade
the uplink codec
CMR:
new codec
CMR:
new codec
CMR:
new codec
CMR: new codec
CMC: new codec

The MS1 uses
immediately
the new codec
CMI: new codec
CMI:
new codec
CMI:
new codec
CMI:
new codec
1 4 19
CMI:
new codec

Example:
Command downlink.
BTSs.
enough.
2.3.4 DL Upgrading
MS1
BTS1
TRAU1
TRAU2
BTS2
MS2

The MS
detects good
downlink quality
CMR:
new codec
The BTS
decides to adapt
downlink codec
CMR:
new codec
CMR:
new codec
CMR:
new codec
BTS2 has
measured good
uplink quality
CMC: new codec
CMI:
new codec
CMI:
new codec
CMI:
new codec
CMI:
new codec
The MS2 uses

immediately
the new codec
CMI: new codec
1 4 20

Example:
Command downlink.
BTSs.
enough.
2 How Does It Work?
2.4 TFO AMR-NB vs TFO Rel.99
What mainly differences TFO for AMR-NB with respect to TFO

implemented in B7 (TFO Rel.99)?
Select the correct answers.
More complex algorithm for common configuration choice

Change to the common configuration
Codec Mode adaptation while in TFO
TFO messages exchanged between TCs via in-band signaling
Handling of handovers while in TFO
Interoperability between 2G and 3G
Codec mismatch resolution
For AMR codec type, TFO allows FR-HR matching
1 4 21


1 4 22


3.1 TFO Interoperability with TrFO
TrFO is a Core Network protocol, applicable to the NGN architecture.

TrFO allows to transport speech in the Core Network using
GERAN/UTRAN codecs over IP, rather than G.711. The advantages are
gain in transmission bandwidth and in speech quality if the same codec
is used over the complete path.
Contrarily to TFO, TrFO is out-of-band, i.e. negotiation is not done in

the User Plane (embedded in speech frames), but in the Control Plane,
on a specific interface.
1 4 23


3.1 TFO Interoparability with TrTFO
No TFO No TrFO
Transmission
saving
MSC
server
Speech quality
MSC
server
BSS 1
BSS 2
MS 1
MS 2
2G
No
TFO
TC
1
MG
No
TrFO
MG
G711 W/O TFO
AMR-NB
1 4 24
2G
No
TFO
IP


TC
2
AMR-NB
3.1.1 2G-2G Interoperability [cont.]
TFO supported for the current codec, no TrFO available
Transmission
saving
MSC
server
Speech quality
MSC
server
BSS 1
BSS 2
MS 1
MS 2
2G
IP
TFO
TC
1
MG
No
TrFO
MG
TFO + AMR-NB
AMR-NB
1 4 25
2G
TFO


TC
2
AMR-NB
TFO not supported for the current codec
Transmission
saving
MSC
server
Speech quality
MSC
server
BSS 1
BSS 2
MS 1
MS 2
2G
No
TFO
TC
1
AMR-NB
MG
G711
W/O TFO
1 4 26
TrFO
2G
No
TFO
IP
TC
2
MG
AMR 12.2
G711
W/O TFO


AMR-NB
TFO and TrFO supported for the current codec
Transmission
saving
MSC
server
Speech quality
MSC
server
BSS 1
BSS 2
MS 1
MS 2
2G
IP
TFO
TC
1
AMR-NB
MG
TFO+AMR-NB
1 4 27
TrFO
2G
TFO
MG
AMR-NB
TC
2
TFO+AMR-NB


AMR-NB
TFO and TrFO supported for the current codec
Transmission
saving
MSC
server
Speech quality
MSC
server
BSS 1
MSC
3G
MS 1
2G
AMR-NB
MG
TFO+AMR-NB
1 4 28
MS 2
3G
IP
TFO
TC
1
UTRAN
TrFO
MG
AMR-NB


TC
2
AMR-NB
3.2 TFO Interoperability with UMTS
AMR-NB (UMTS AMR2 codec shall be used in 3G) and AMR-WB are
common to GSM and UMTS and are therefore a pre-requisite for TFO
between 2G and 3G. In TFO messages, the parameter SysID allows to
determine from which system a TFO message has been received (e.g.
GSM, UMTS).
UMTS
Transmission
saving
Speech quality
GERAN
MSC
2G
MSC
3G
UTRAN
MS 1
MS 2
Core
Network
TC
1
TFO AMR-NB
AMR-NB
1 4 29
TC
2
UMTS AMR-NB

In UMTS, the TC is located in the Core Network. This TC shall support the TFO protocol to allow 2G-3G TFO.

1 4 30


The TFO for AMR-NB is optional. It can be activated at cell level.
New parameter: EN_TFO_AMR_NB
Parameter modified: EN_TFO
1 4 31

EN_TFO_AMR_NB:
A flag to enable, disable the use of TFO in case of AMR NarrowBand:
Instance: Cell
Type: Flag
Range:Enable, Disable
Default: Disable
EN_TFO:
A flag to enable, disable the use of TFO in case of GSM EFR, FR and HR codec type (definition changed):
Instance: Cell
Type Flag
Range: Enable, Disable
Default: Disable

Module Summary
In B11, The AMR +TFO feature improves the speech quality of mobileto-mobile calls.
This feature allows TFO-TrFO interaction in the NGN core network.
The establishment of a TFO call begins by a negotiation phase.
Each partner runs in the TC a decision algorithm to decide if TFO can
be established and on what codec type and set of codec modes.
The codec mode adaptation is performed independently on each
direction.
In one direction, the codec mode adaptation is triggered by both
radio interfaces.
TFO shall be supported for 2G-3G mobile calls.
There is a flag to enable, disable the use of TFO in case of AMR
NarrowBand.
The feature activation is done at cell level.
1 4 32



for this module
1 4 33


End of Module
Tandem Free Operation with AMR-NB
1 4 34


Section 1
Module 5
Support of A5.3 Ciphering

TMO18090 Issue 1.0

Blank Page
152
BSS B10-B11 Telecom Evolutions Support of A5.3 Ciphering

Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Module Objectives
Describe the purpose of the "Support of A5/3 Ciphering Algorithm" feature
and its Telecom impacts
153


154

Table of Contents
Page

1.1 Ciphering Usage Prior to B11
1.2 A5/3 Supported in B11
2 How Does It Work?
2.1 A5/3 Usage
155


7
8
10
11
12
15
16
17

156

157


Section
Module
Page 7
This page
is 1left
blank 5intentionally
1.1 Ciphering Usage Prior to B11
Do you remember the ciphering usage before B11?

The MSC is responsible for initiating
Ciphering
Parameter BSS_CIPH_LIST: list of cipher

algorithms according to their priority
For a certain call segment (e.g. between

handovers), the BSC chooses the encryption
algorithm matching the MSC ciphering
requirements
A5/1 initial GSM ciphering used in Europe and

in the United States
For a certain call segment (e.g. between

handovers), the BSC chooses the encryption
algorithm matching the MS & BTS ciphering
capabilities and takes into account the
priorities given in BSS_CIPH_LIST
158
A5/2 was developed in 1989 for export outside

Europe
Ciphering algorithm A5/0 is not supported
Today every TRE is able to do A5/1
All TREs of a BTS have the same ciphering
capabilities


1.1 Ciphering Usage Prior to B11 [cont.]
Before the introduction of the A5/3 algorithm, the BSS supported up

to 2 encryption algorithms (A5/1 and alternatively A5/2 until 2007).
The cracked A5/2 was removed from the field in July 2007. This could
be used as an intermediate step for cracking of A5/1.
A5/2: Cracked
and removed
from the field
in July 2007
MSC
BSS
Necessity to deploy a more solid ciphering algorithm: A5/3

159

A5/1 is the initial GSM ciphering used in Europe and in the United States.
A5/2 is considered as the weaker algorithm for certain export regions.
A5/2 cracked and could be used as an intermediate step for cracking of A5/1.
Decision to remove A5/2 from handsets and networks occurred mid 2007: Due to fact that A5/2
ciphering algorithm has been broken, the GSM Association requested all operators didn't use A5/2 anymore
from July 2007 onwards. As a complement to this request, the MS does not support A5/2 ciphering
algorithm starting with 3GPP Release 6 onwards.
All Operators were then allowed to use A5/1.
A5/1 is endangered: hackers have been claiming for several months that they would be able to crack
A5/1 with relatively limited means.
Vodafone undergo high pressure to include 3GPP modifications to improve the resistance to cracking of
A5/1.

1.2 A5/3 Supported in B11
A5/3 is a new ciphering algorithm specified first for UMTS, and then
for GSM (3GPP R4). A5/3 is used within Alcatel-lucent for circuitswitched channels (TCH and SDCCH). Thus, in B11, Alcatel-Lucent BSS
supports A5/0, A5/1 and A5/3 (A5/2 is no longer supported). It is not
supported by all MSs in the field and by all TRE generations.
Rel-4 MSC
BSS
Rel-6 MS
A5/3 ciphering is seen as being as stronger as A5/1
1 5 10

The MSs supporting Rel-6 or latter versions of the 3GPP protocol support A5/0, A5/1 and A5/3. These MSs
are also capable of turning ciphering off or starting or changing encryption during a channel change
procedure.
Restrictions
The A5/3 ciphering algorithm only concerns the Circuit-Switched domain.
For a DTM-capable MS whose Ciphering Mode Setting Capability bit is set to 0, A5/1 shall always be used
in cells where DTM is enabled.
A5/3 cannot be used on G4 TRE in IP mode (performance limitation).
As the A5/3 algorithm is not supported by all MSs in the network and by all TRX generations, the BSS will
have to support 2 encryption algorithms simultaneously. The choice of the algorithm to be used will be
performed on a per call basis: the ciphering algorithm is decided at call setup, and can be changed after a
handover in case the new TRX has different ciphering capabilities.

2 How Does It Work?
1 5 11


2 How Does It Work?
2.1 A5/3 Usage
The introduction of the A5/3 ciphering algorithm into the AlcatelLucent BSS requires the new encryption itself (in the BTS) and the
selection among the different A5 algorithms (in the BSC). Activation of
A5/3 is done on a per call segment basis (CS only). A BSS and a TRX
must be able to handle no ciphering, A5/1 and A5/3 in parallel (on
different calls). When should A5/3 be used?
For a call segment, A5/3 is used if:
The MS supports A5/3. This is indicated in classmark 2.
The TRX supports A5/3 in the intended service and current
Abis mode (TDM or IP).
The operator has enabled A5/3 support for the cell.
The NSS allows the use of A5/3.
DTM is not enabled in the cell or DTM is enabled and the
Ciphering Mode Setting Capability of the MS bit is set.
1 5 12

The selection among the A5 algorithms is done in the BSC (the MSC gives in a bit field a set of permitted
algorithms on a per call basis, e.g. in the CIPHER MODE COMMAND message).
Rules
The BSC will always give A5/3 priority over A5/1. This means that the matching set of algorithms between
MS, NSS, OMC-R and TRX capabilities has to be calculated. If the result is more than one algorithm, the one
with the highest A5 number will be used (i.e. A5/3 has the highest priority).
If no CIPHER MODE COMMAND message has been sent by the MSC, the algorithms allowed by the NSS
should be considered as A5/0 only.
In case of competition with A5/1, A5/3 is preferred.
For a DTM-capable MS whose Ciphering Mode Setting Capability bit is set to 0, A5/1 shall always be used
in cells where DTM is enabled.

2 How Does It Work?
2.1 A5/3 Usage [cont.]

Are the statements related to the ciphering procedure in B11 true or
false?

TRX rather than BTS ciphering capabilities have to be
considered in the BSC
Operator settings have to be considered
A5/1 is not supported in B11, but A5/3 will be supported
True
Support of A5/3 ciphering capabilities in classmark 2
False
Support new bit (Ciphering Mode Setting Capability) in classmark

3
-
For a DTM-capable MS whose Ciphering Mode Setting Capability

bit is set to 1, A5/1 shall always be used in cells where DTM is
enabled
-
1 5 13


2 How Does It Work?
2.1 A5/3 Usage [cont.]
On the A interface, in which messages are the encryption IE and the

chosen encryption algorithm contained?
Cipher Mode Complete

Assignment Request
Handover Performed
Encryption Information
IE
Handover Request
Chosen Encryption
Algorithm
Assignment Complete
Cipher Mode Command
Handover Request Ack
1 5 14


1 5 15


New Parameters
The operator can configure the list of supported A5/x algorithms in
each cell.
CELL_CIPH_SET
TRE_CIPH_CAP
1 5 16

CELL_CIPH_SET:
Definition: Indicates in an 8-bit field the ciphering algorithms allowed by the operator (each bit represents
an A5 algorithm). The values can be A5/0 or A5/0 + A5/1 or A5/0 + A5/1 +A5/3.
The A5/0 is always set. The setting of only A5/0 + A5/3 should be refused, because today not all mobiles
support A5/3.
Instance: Cell
Default value: A5/0 (no ciphering)
TRE_CIPH_CAP:
Definition: Indicates the ciphering algorithms supported by the TRE.
The values can be A5/0 + A5/1 or A5/0 + A5/1 +A5/3.
The parameter consists of two bytes: one for TDM the other for IP. The OMC shall display the capabilities
per TRE of the current and the alternative Abis mode to the operator.
Default value: A5/0 (no ciphering) + A5/1 are always set.
Parameters BSS_CIPH_LIST and BTS_CIPH_CAP are removed.

New Counters
NB_TCH_A5_3_REQ
NB_CIPHER_CMD_A5_3
NB_SUCC_CIPHER_CMD_A5_3
NB_TCH_A5_3_ASS
NB_TCH_A5_3_ASS_NO_TRX
1 5 17

NB_TCH_A5_3_REQ (MC951)
The number of TCH normal assignment requests for A5/3-capable mobiles.
Trigger condition: Receipt of 48.008 ASSIGNMENT REQUEST from the MSC.
NB_CIPHER_CMD_A5_3 (MC952)
The number of Cipher Mode Command messages received from the MSC, allowing A5/3 for an MS supporting A5/3 in a
cell where A5/3 is enabled.
Trigger condition: Receipt of 48.008 CIPHER MODE COMMAND from the MSC with encryption information indicating that
A5/3 usage is allowed for an A5/3-capable MS, in a cell where A5/3 is enabled.
NB_SUCC_CIPHER_CMD_A5_3 (MC953)
The number of successful Cipher Mode Command messages for usage of A5/3.
Trigger condition: Receipt of 44.018 CIPHERING MODE COMPLETE from the MS, subsequently to a 44.018 CIPHERING
MODE COMMAND with cipher mode setting indicating usage of A5/3.
NB_TCH_A5_3_ASS (MC954)
The number of 44.018 ASSIGNMENT COMMAND or HANDOVER COMMAND sent to an MS requiring the usage of A5/3
ciphering algorithm.
Trigger condition:
if the cell is a serving cell, incremented by 1 each time the BSC sends a 44.018 ASSIGNMENT COMMAND message with
the target ciphering algorithm to be used by the MS for this call set to A5/3 (whatever the ciphering algorithm used
before).
if the cell is the target cell of an intra-cell handover, or inter-cell handover, or external handover or
internal/external directed retry, incremented by 1 each time the BSC sends a 44.018 HANDOVER COMMAND message via
the serving cell with the target ciphering algorithm to be used by the MS for this call in the target cell set to A5/3
(whatever the ciphering algorithm used before).
NB_TCH_A5_3_ASS_NO_TRX (MC955)
The number of unsuccessful A5/3 cipher mode command due to non A5/3 support on the TRX used for the MS
allocation.
Trigger condition: Incremented by 1 each time a CIPHER MODE REJECT message is sent with cause "Ciphering algorithm
not supported" in response to a CIPHER MODE COMMAND indicating A5/3 as permitted algorithm but the TRX on which
the MS is allocated does not support A5/3.
Module Summary
The A5/3 ciphering algorithm is supported in B11.
In B11, the Alcatel-Lucent BSS does not support A5/2 anymore.
A5/3 compatible handsets are required.
A5/3 is not supported on TRE G3.
A5/3 shall not be used in a certain case of DTM.
There is a new parameter: CELL_CIPH_SET on the BSC, managed

from the OMC-R.
Parameters BSS_CIPH_LIST and BTS_CIPH_CAP are removed.
1 5 18



for this module
1 5 19


End of Module
Support of A5.3 Ciphering
1 5 20


Section 1
Module 6
Synchronized Radio Network

TMO18090 Issue 1.0

Blank Page
162
BSS B10-B11 Telecom Evolutions Synchronized Radio Network

Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Module Objectives
Describe the purpose of the "Synchronized Radio Network" feature and its
Telecom impacts
163


164

Table of Contents
Page

1.1 Without Synchronization of Radio Timeslots
1.2 With Synchronization of Radio Timeslots
1.3 Clock Synchronization Mode
2 How Does It Work?
2.1 GPS Synchronization
2.2 Frame Number Synchronization
165


7
8
9
10
11
12
13
14
15

166

167


Section
Module
Page 7
This page
is 1left
1.1 Without Synchronization of Radio Timeslots
Without synchronization of radio timeslots, MS1 transmitting on TS 3 of

BTS1 interferes with TS1 and TS2 (i.e. MS2) of BTS2, if the same
frequency is used. And inversely, MS2 transmitting on TS 2 of BTS2
interferes with TS3 (i.e. MS1) and TS4 of BTS 1.
BTS 1
MS1
MS1
on TS 3
FN=10
FN=11
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
BTS 2
MS2
MS2
on TS 2
168
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
FN=25


FN=26
1.2 With Synchronization of Radio Timeslots
This new feature aims at significantly improving the spectral efficiency, in order to
increase the network capacity. The principle is that all the BTSs of an area (and not
only the cells of a BTS) use the same starting time for the radio timeslots. This results in
fewer collisions between signals and interferences, then in an improved distribution of
C/I, which explains the capacity gains. Up to 10% capacity gains can be expected with
the great advantage of no MS dependency.
MS1 transmitting on TS3 of BTS1 interferes with TS1 and TS2 (i.e. MS2) of BTS 2, if the
same frequency is used. And inversely, MS2 transmitting on TS2 of BTS2 interferes with
TS3.
BTS 1
MS1
MS1
on TS 3
FN=10
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
Each slot interferes with maximum
1 other slot per interfering carrier
BTS 2
MS2
MS2
on TS 2
169
FN=11
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
FN=25
FN=26

Rationale of the Feature

Some Mobile Operators get only a limited frequency range, although having to face a continuous increase
in the number of subscribers.
Those Operators are then very interested by any feature allowing to significantly improve the spectral
efficiency (boosting the maximum equipment usage).
, in order to increase the network capacity while avoiding huge impact on network dimensioning and
planning, when all the other existing solutions have been applied (AMR-HR, full usage of synthesized
frequency hopping).
Among them, the so-called "Synchronized Network" feature is promising, as up to 10% capacity gains can
be expected with the great advantage of no mobile station dependency.
The principle is that all the BTSs of an area (and not only the cells of a BTS) use the same starting time
for the radio timeslots.
This results in fewer collisions between signals and interferences, then in an improved distribution of C/I,
which explains the capacity gains.

1.3 Clock Synchronization Mode
Do you know in which synchronization modes the Alcatel-Lucent BTS is

able to operate?
The PCM synchronized mode (the BTS uses the PCM clock to synchronize the radio).
The free running (the BTS uses an internal clock).
Because IP was originally planned in B10, clock synchronization by NTP has been
introduced. NTP synchronization cannot be activated in B10. The NTP is a protocol for
synchronizing the clocks of computer systems over PS data networks.
The Precision Time Protocol (PTP) is a time-transfer protocol defined in the IEEE 15882002 standard. PTP allows precise synchronization of networks (e.g., Ethernet). It is not
supported yet.
1 6 10


2 How Does It Work?
1 6 11


2 How Does It Work?
2.1 GPS Synchronization
The feature requires the installation of a GPS receiver in the BTS. The
site has also to be equipped with a GPS antenna, typically with free
sight to the satellites.
GPS
BTS 1
BTS n
GPS
Receiver
1 6 12
GPS
Receiver

The GPS receiver in the BTS can serve 2 purposes:

Frequency synchronization: in countries where no stable PCM clock is available, operators have to make
annual checks/alignments of the OCXO on all BTS sites in the networks.
Time synchronization: the time synchronization of frames limits interferences and is a means to improve
handover quality.
In a configuration with master/slaves BTS, the GPS receiver is mandatory only in the master BTS.
GPS receiver acquisition is done only when SUMX is powered up. SUMX reset/restart does not imply a GPS
receiver acquisition.

2 How Does It Work?
2.2 Frame Number Synchronization
If the emissions of the BTSs are synchronized in time and in frame

number, this can however have some negative effects.
For the BSIC decoding: 1 idle slot can be used out of 10 such as idle slots for an MS with
an FR TCH. This could increase the time required to identify neighbor cells.
SACCH collision: For the mobiles with a TCH, all the SACCH frames are transmitted
simultaneously.
Synchronized Radio Networks without a proper frequency plan and/or frequency hopping
parameters may turn sporadic interference between cells in a typical GSM radio network
into constant interference in the Synchronized Radio Network.
Use an offset of
the TDMA frame number
between each cell
to reduce the impacts
1 6 13


1 6 14


In B11, the OMC-R access of the parameters below is changed:

GPS_Synchronised
EN_OFFSET_TIME_SYNCHRO
There is no new PM counter foreseen to monitor this

feature.
1 6 15

GPS-Synchronised
Definition: This parameter is used to allow the BTS to be externally synchronised on a GPS server.
Instance: BTS
OMC-R access: changeable
Type: Flag
Range / default value: [True,False]/False
FN_OFFSET_TIME_SYNCHRO
Definition This parameter is used to allow the GPS-synchronized BTS to have different frame numbers.
This parameter is used only if the BTS is a master BTS and is GPS synchronized.
Instance: BTS
OMC-R access: changeable
Type: Number
Range / default value: [0..103]/ 0

Module Summary
With the Synchronized Radio Network feature, all GSM cells take
their timing/clock from a single source: the GPS system.
Each slot interferes with maximum 1 other slot per interfering carrier.
Fewer collisions between signals and interferences, improved

distribution of C/I.
Improved spectrum efficiency & capacity.
No Mobile Station dependency.
The OMC-R parameter GPS-Synchronised is used to allow the BTS to

be externally synchronized on a GPS server.
1 6 16



for this module
1 6 17


End of Module
Synchronized Radio Network
1 6 18


Section 1
Module 7
TRX Dynamic Power Saving

TMO18090 Issue 1.0

Blank Page
172
BSS B10-B11 Telecom Evolutions TRX Dynamic Power Saving

Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Module Objectives
Describe the purpose of the "TRX Dynamic Power Saving" feature and its
Telecom impacts
173


174

Table of Contents
Page

1.1 Reducing BTS Power Consumption
2 How Does It Work?
2.1 BTS Algorithms to Switch on / off the PA Bias
2.2 BTS Behavior while the PA Bias Is Off
175


7
8
9
10
12
13
14
15

176

177


Section
Module
Page 7
This page
is 1left
1.1 Reducing BTS Power Consumption
The TRX Dynamic Power Saving feature aims at reducing BTS power
consumption. It consists in switching off the Power Amplifier (PA) bias
of a TRX as soon as several consecutive timeslots are not used in DL on
this TRX, which should allow a significant reduction of power
consumption.
Power saving
when there is nothing to transmit
over the air
PA On
0
PA Off
5
PA Off
5
Time
G5
or G4
TRE
5 x 60W
2 x 20W
Active TS
Idle TS
178

Thanks to this feature, the power consumption per TRX is reduced by ~25W when there is no traffic to be
transmitted.
At BTS level, the association of Dynamic Power Saving, Power Control and Discontinuous Transmission in
Downlink brings around 25% saving on the global energy bill.
This feature should allow to reduce the total cost of ownership of the operators in a significant way.
The feature does not bring any negative impact on the quality of the network. Indeed, thanks to the very
fast reaction of the system, even in case of sudden variation of traffic, no call will be blocked.

2 How Does It Work?
179


2 How Does It Work?
2.1 BTS Algorithms to Switch on / off the PA Bias
The algorithm to switch on / off the PA bias of a TRX is a pure on the

fly algorithm: it is based on the Radio Time Slots (1 RTS 0.577 ms)
which are busy in DL in the TDMA frames of the TRX. The BTS
permanently monitors whether data has to be transmitted over the air
in the next two RTSs. DependingGPS
on the result of the monitoring, it may
switch on or switch off the PA bias. The time required for switch-off
or switch-on is below one RTS.
0
TWIN TRE
TWIN module
Power
Consumption (W)
The power consumption per TRX

is reduced by ~25W
With Dynamic
Power Saving
250
200
150
100
50
180
180
155
155
180
90
180
155
90
Without
Dynamic
Power Saving
155
Watts saved
Assumption: no power control

40
1 7 10
40
Time

Power saving as soon as 2 consecutive TSs are idle:
"On the flight" procedure: the BTS detects whether data has to be transmitted over the air in the
next 2 radio timeslots or not
Immediate reaction
No impact on quality: zero call blocked
Power saving during the day or night period
Power saving for all BTS configurations
When the PA bias is switched off, the power consumption of the corresponding TRX is reduced by ~25W.
In B11, the reduction of power consumption of G4 TREs (which represent more than 90% of the TREs
currently present on the field) and of G5 TREs (for the future) is particularly important.
In B10, to simplify, the feature is only supported on G5 TREs (but not on G3 and G4 TREs).
The procedure is independent from the type of traffic: it is valid for voice, packet or signaling. Therefore it
applies for all types of channels (TCH, SDCCH, PDCH). The radio timeslot may be allocated for a service. If
nothing has to be transmitted on the downlink path, the PA bias is switched off.

2 How Does It Work?
2.1 BTS Algorithms to Switch on / off the PA Bias [cont.]
When Is a TS Considered to Be Busy in DL?

When a DL transmission is needed on that TS, it can be related to the
following cases:
A TCH was allocated by the BSC on the associated RTS of the TRX.
A dynamic SDCCH/8 sub-channel was allocated by the BSC on the associated RTS of the
TRX.
A DL TBF was allocated by the MFS on the associated RTS of the TRX (and for which a
data/control radio block or a dummy block shall be transmitted in DL).
A Packet-UL-Assignment message has to be sent by the MFS on the associated RTS of
the TRX during a UL two-phase access procedure.
A logical channel was configured on the associated RTS of the TRX: BCH (FCCH, SCH,
BCCH) or CCCH (PCH, RACH, AGCH, CBCH), or a static SDCCH that was configured on
the associated RTS of the TRX.
The TS belongs to an idle TDMA frame (frames 25 and 51 in each multiframe) on a
BCCH carrier.
The TS belongs to a PTCCH TDMA frame (frames 12 and 38 in each multiframe) on
which there is something to transmit.
1 7 11

A TCH was allocated by the BSC on the associated RTS of the TRX. But during the silence periods in DL, the
TS will not be considered as busy. Thus, DTX will induce some power gains.
On BCCH carriers, dummy bursts have to be transmitted to allow power monitoring by MSs at any time.
This rule is not applicable to non-BCCH carriers where there is no transmission within idle frames.
In case of base band hopping, a DL transmission is necessary on the associated RTS, given the frequency
hopping law between the 4 TRXs of the cell. For example, the PA bias of the current TRX may need to be
switched on due to an MS which has been allocated resources (PS or CS) on the same RTS on another of the
4 TRXs.

2 How Does It Work?
2.2 BTS Behavior while the PA Bias Is Off
What is the BTS behavior while the PA bias of a TRX is off?
DL transmissions are not possible (with a proper signal quality and whatever the
logical channels) on the considered TS(s)
UL reception is not cut.
The air interface messages received in UL on the considered TS(s) are handled
normally by the BTS
The interactions with the rest of the BSS are unchanged.
The reception of messages from / the sending of messages to the BSC/TC/MFS are
unchanged.
1 7 12

The feature is supported on all TRX generations, i.e.:
TRE (no n-EDGE capable),
TRA (EDGE capable),
EDGE+,
TWIN TRX.
The feature is also supported on micro-BTS.

1 7 13


The feature can be activated/deactivated at OMC-R level via the

following parameter: EN_POWER_SAVING
1 7 14

EN_POWER_SAVING
Definition: Enables power saving on all TRXs in the cell
Instance: Cell
Changeable
Type: flag
Range / default value:
0: disabled (default value)
1: enabled

Two PM counters are used to monitor the efficiency of the feature:

TIME_TS_BUSY
TIME_PA_BIAS_ON
1 7 15

TIME_TS_BUSY (MC957)
Definition: The cumulated time during which TSs are "busy in DL" on the TRXs of the cell (i.e. a DL
transmission is needed on that TS, whatever the nature of the DL transmission: useful or dummy bursts).
Trigger condition: The sum of all TSs (1 TS is about 0.577 ms) which are "busy in DL" on the TRXs of the
cell, among all the successive TDMA frames associated to those TRXs.
TIME_PA_BIAS_ON (MC958)
Definition: The cumulated time during which the PA bias is "on" (or partially "on") on the TRXs of the cell.
Trigger condition: The sum of all periods during which the PA bias is "on" on the TRXs of the cell. For
each TRX of the cell, the counter shall be incremented.

Module Summary
The TRX Dynamic Power Saving feature consists in switching off the
Power Amplifier (PA) bias when there is nothing to transmit over
the air.
Power saving is performed as soon as 2 consecutive TSs are idle.
Power saving is brought with NO detriment of the quality of service:

there is no call blocking, no reduction of packet data throughput.
Power saving is performed during the day or night period.
Power saving applies to all BTS configurations.
The feature is very simple to use, as it requires no specific parameter

tuning (only one flag to activate it).
1 7 16



for this module
1 7 17


End of Module
TRX Dynamic Power Saving
1 7 18


Section 1
Module 8
Abbreviations

TMO18090 Issue 1.0

Blank Page
182
BSS B10-B11 Telecom Evolutions Abbreviations

Document History
Edition
Date
Author
Remarks
01
2009-03-30
Eljaafari, Mohamed
First edition

Abbreviations and Acronyms

#
2G
3G
3GPP
Second Generation
Switch
to notes view!
Third Generation
Third Generation Partnership Project
A
ACCH
ACS
AGCH
AMR
AMR-HR
AMR-NB
AMR-WB
Associated Control Channel

Active Codec Set
Access Grant CHannel
Adaptive Multi-Rate
AMR-Half Rate
AMR NarrowBand
AMR WideBand
B
BCCH
BSC
BSCGP
BSIC
BSS
BTS
Broadcast Common Control CHAnnel

Base Station Controller
Base Station Controller GPRS Protocol
Base transceiver Station Identity Code
Base Transceiver Station
C
C/I
Carrier over Interference Ratio
CACS
Common Active Codec Set
CBCH1 8 3Cell Broadcast CHannel
BSS B10-B11
Telecom Evolutions
Abbreviations
CCCHBase
Common
Control
CHAnnel
Station Subsystem BSS B10-B11 Telecom Evolutions
CI
Cell Identity
CMR
Codec Mode Request
CN
Core Network
CS
Circuit Switching
CSCS
Common Supported Codec Set
H
HO
HR
I
IACS
Immediate Active Codec Set
ICM
Initial Codec Mode
IEEE
Institute of Electrical and Electronics
Engineers
IMSI
International Mobile Subscriber Identity
L
LACS
LAPD
LLC
Local Active Codec Set

Link Access Protocol Digital
Logical Link Control
M
MACS
MFS
MGW
MS
MSC
Maximum Active Codec Set

Multi-BSS Fast Packet Server
Media GateWay
Mobile Station
Mobile services Switching Center
N
NACC
NC
NGN
NMO
NGN
NTP
D
DACS
DL
DLS
DTM
Distant Active Codec Set

DownLink
Data Load Segment
Dual Transfer Mode
E
EDGE
EFR
Enhanced Data rates for GSM Evolution

Enhanced Full Rate
F
FACCH
FCCH
FN
FR
Fast Associated Control CHannel

Frequency Correction Channel
Frame Number
Full Rate
Handover
High Rate
O
O&M
OACS
OMC-R
Radio
P
PA
PACCH
PCM
PDCH
PDU
PIM
PM
PS
PTCCH
PTM
PTP
Network Assisted Cell Reselection

Network Control
Next Generation Network
Network Mode of Operation
Next Generation Network
Network Time Protocol
Operation and Maintenance
Optimized Active Codec Set
Operation and Maintenance Center-
Power Amplifier
Packet Associated Control Channel
Pulse Code Modulation
Packet Data Channel
Packet Data Unit
Packet Idle Mode
Performance Management
Packet Switching
Packet Timing advance Control Channel
Packet Transfer Mode
Precision Time Protocol
G
Gb
BSS-SGSN interface
GERAN
GSM EDGE Radio Access Network
GPRS
General Packet Radio Service
GPS
Global Positioning System
GPU
GPRS Packet Unit
Gs
MSC-SGSN interface
GSL
GPRS Signaling Link
GSM
Global System for Mobile
communications
Abbreviations and Acronyms

R
RA
Routing Area
RACH
Random Access Channel
RAI
Routing Area Identity
RAN
Radio Access Network
RAT
Radio Access Technology
RDFACCH Repeated DL FACCH
RDSACCH Repeated DL SACCH
Rel-6
Release 6
RIM
RAN Information Management
RLS
Radio Link Supervision
RLT
Radio Link Timeout
RNC
Radio Network Controller
RSACCH Repeated UL & DL SACCH
RTS
Radio Time Slot
RUSACCH Repeated UL SACCH
S
SACCH
Slow Associated Control Channel
SAPI
Service Access Point Identifier
SCH
Synchronization Channel
SDCCH
Standalone Dedicated Control Channel
SGSN
Serving GPRS Support Node
SI
System Information
SMS
Short Message Service
SRO 1 8 4SACCH Repetition Order
SRR Base Station
SACCH
Subsystem Repetition
BSS B10-B11 Telecom Request
Evolutions
T
TBF
TCH
TDMA
TFO
TRA
TRAU
TRE
TrFO
TS
TS
Temporary Block Flow

Traffic Channel
Time-Division Multiple Access
Tandem Free Operation
TRE with 8-PSK capacity
Transcoding Unit
TRansceiver Equipment
Transcoder Free Operation
Time Slot
Technical Specification
U
UL
UpLink
UMTS
Universal Mobile Telecommunications
System
UTRAN
Universal Terrestrial Radio Access
Network

End of Module
Abbreviations
185


Last But One Page

1
@@PRODUCT
@@COURSENAME

@@COURSENAME - Page 1

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

CE - TMO18090 BSS B10-B11 Telecom Evolution PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CE - TMO18090 BSS B10-B11 Telecom Evolution PDF

Загружено:

Авторское право:

Доступные форматы

Base Station Subsystem

BSS B10-B11 Telecom Evolutions

All Rights Reserved Alcatel-Lucent @@YEAR

All rights reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

Terms of Use and Legal Notices

Base Station Subsystem

All rights reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

3. NACC for Inter BSS and Inter RAT

4. Topic/Section is Positioned Here

5. Support of A5.3 Ciphering

6. Synchronized Radio Network

7. Topic/Section is Positioned Here

7. TRX Dynamic Power Saving

2. Topic/Section is Positioned Here

All Rights Reserved Alcatel-Lucent @@YEAR

Base Station Subsystem

All Rights Reserved Alcatel-Lucent @@YEAR

Course Outline [cont.]

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

Welcome to BSS B10-B11 Telecom Evolutions

Upon completion of this course, you should be able to:

features and their telecom impacts.

All Rights Reserved Alcatel-Lucent @@YEAR

Base Station Subsystem

All Rights Reserved Alcatel-Lucent @@YEAR

Course Objectives [cont.]

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

About this Student Guide

All Rights Reserved Alcatel-Lucent @@YEAR

Where you can get further information

Base Station Subsystem

If you want further information you can refer to the following:

All Rights Reserved Alcatel-Lucent @@YEAR

About this Student Guide [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

At the end of each

section you will be asked to fill this questionnaire

Surname, First name :

All Rights Reserved Alcatel-Lucent @@YEAR

Base Station Subsystem

All Rights Reserved Alcatel-Lucent @@YEAR

Self-assessment of Objectives [cont.]

All Rights Reserved Alcatel-Lucent @@YEAR

Base Station Subsystem

Thank you for your answers to this questionnaire

All Rights Reserved Alcatel-Lucent @@YEAR

Do not delete this graphic elements in here: