Anda di halaman 1dari 83

GSM/EDGE BSS, Rel.

RG20(BSS), Operating
Documentation, Issue 08

Feature description

BSS21469: BS2xx@Flexi BSC product


family
DN0933257
Issue 01D
Approval Date 2011-08-10
Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of
its products and services. We would like to encourage you as our customers and users to join
us in working towards a cleaner, safer environment. Please recycle product packaging and
follow the recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental
services we offer, please contact us at Nokia Siemens Networks for any additional information.

BSS21469: BS2xx@Flexi BSC product family

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2011. All rights reserved

Important Notice on Product Safety


This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit


Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.

Id:0900d805808a4e53
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Table of contents
This document has 83 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

DN0933257

1
1.1
1.2
1.3

Introduction . . . . . . . . . . . .
Network elements . . . . . . .
Terminology . . . . . . . . . . . .
Benefits for the operator . .

.......
.......
.......
.......

2
2.1
2.2
2.3
2.4

Network architecture . . . . . . . . . . . . . . . . . .
BS-240XL II / BS-240XL II B . . . . . . . . . . . .
BS-240 II / 240 II B / 241 II / 241 II B . . . . . .
BS-288 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BS-82 II . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3
3.1

Operation and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


Remote configuration of BTSplus hardware objects . . . . . . . . . . . . . . . 18

4
4.1
4.2

Info model mediation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20


Handling of segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Migrating TRXs from BTSM to BCF. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5
5.1
5.1.1
5.1.2
5.1.2.1
5.1.2.2
5.1.2.3
5.1.3
5.1.3.1
5.2
5.2.1
5.2.1.1
5.2.1.2
5.2.2
5.2.3

Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abis interface transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1/T1 configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Star configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multidrop configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross-connect configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functional overview/details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abis interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPD multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPD logical link configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPD redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EDAP handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example PCM allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21
21
21
22
23
24
25
25
25
27
27
29
29
30
30

6
6.1
6.2
6.2.1
6.2.2
6.3
6.3.1

Migration of complex cells . . . . . . . . . . . . . . . . . . . . . . . . . . .


Dual band cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Concentric cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dual band operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration of concentric cells to the Flexi BSC . . . . . . . . . . . .
Extended cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring extended cells . . . . . . . . . . . . . . . . . . . . . . . . . .

........
........
........
........
........
........
........

33
33
33
34
34
35
36

7
7.1
7.1.1
7.1.2

Handover and power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classification of handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mapping of handover causes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

38
38
38
42

Id:0900d805808a4e53
Confidential

............................ 9
............................ 9
. . . . . . . . . . . . . . . . . . . . . . . . . . . 10
. . . . . . . . . . . . . . . . . . . . . . . . . . . 10
.......
.......
.......
.......
.......

......
......
......
......
......

.......
.......
.......
.......
.......

.
.
.
.
.

11
13
14
15
16

BSS21469: BS2xx@Flexi BSC product family

7.1.3
7.1.4
7.2
7.2.1

TCH and SDCCH handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43


Congestion control for dual area cell . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Derived handover power management. . . . . . . . . . . . . . . . . . . . . . . . . . 44

8
8.1
8.2
8.2.1
8.3
8.4
8.4.1
8.4.1.1
8.4.1.2
8.4.1.3
8.5
8.6
8.7
8.7.1
8.7.2
8.7.3
8.7.4
8.7.5
8.8
8.8.1
8.8.2
8.8.3
8.8.4
8.9
8.10
8.11
8.12

Supported functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Features in BTSplus with the Flexi BSC . . . . . . . . . . . . . . . . . . . . . . . . . 45
GSM frequency bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Multiband operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Antenna diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Frequency hopping management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Exporter Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Specific behavior in case of BB frequency hopping . . . . . . . . . . . . . . . . 73
Hopping configuration provided via control file . . . . . . . . . . . . . . . . . . . . 74
Dual carrier in downlink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A5 ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Control channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4 SDCCH/8 on BCCH carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
BCCH recovery in case of TRX failure . . . . . . . . . . . . . . . . . . . . . . . . . . 74
No support for 2nd CCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Repeated FACCH/SACCH and temporary overpower . . . . . . . . . . . . . . 75
Extended BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Packet-switched data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Dual transfer mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Multislot classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Extended uplink TBF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
HSCSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Power save mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Hierarchical paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Real-time road traffic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Tandem free operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

9
9.1
9.1.1
9.1.2
9.2
9.2.1
9.2.2
9.2.2.1
9.2.2.2
9.3
9.3.1
9.3.2
9.4
9.4.1

Quality standards / specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78


Industrial requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Product safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Power supply interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Quality requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Storage and transportation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Electromagnetic compatibility (EMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Emission requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Immunity requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Environmental requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Stationary use indoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Stationary use outdoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
List of norms and standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Antenna signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Id:0900d805808a4e53
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

List of figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12

DN0933257

Network architecture for managing BTSplus . . . . . . . . . . . . . . . . . . . . .


OAM network architecture for administering the BTSplus . . . . . . . . . . .
Configurations of the Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Object relationship in an Abis star connection . . . . . . . . . . . . . . . . . . . .
Functional overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abis LAPD configuration for the Flexi EDGE BTS . . . . . . . . . . . . . . . . .
Abis LAPD multiplexing for the BTSplus . . . . . . . . . . . . . . . . . . . . . . . .
Example of an optimized PCM line allocation . . . . . . . . . . . . . . . . . . . .
Concentric cell areas in a BR RAN . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extended cell configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Id:0900d805808a4e53
Confidential

11
17
23
24
26
28
28
32
34
36
39
41

BSS21469: BS2xx@Flexi BSC product family

List of tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 9

Types of handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Intra-cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Inter-cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Features in BTSplus with Flexi BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Product safety requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Power supply interface requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Storage and transportation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Environmental requirements for stationary use indoor . . . . . . . . . . . . . 81
Environmental requirements for stationary use outdoor . . . . . . . . . . . . 82

Id:0900d805808a4e53
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Summary of changes

Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Issue
number

Date

Summary

01

10/2009

First issue for RG10(BSS)

01A

12/2009

Second issue for RG10(BSS)

01B

08/2010

Third issue for RG10(BSS)

01C

12/2010

New chapters added

01D

08/2011

New chapter added

Issue 01D for release RG10(BSS)

Supported functionality (8)

DN0933257

New chapter: Features in BTSplus with the Flexi BSC

Id:0900d805808a8cc7
Confidential

Summary of changes

BSS21469: BS2xx@Flexi BSC product family

Id:0900d805808a8cc7
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Introduction

1 Introduction
The BS2xx@Flexi BSC product family (BSS21469) feature describes a network
solution in which BTSplus base stations are managed by BSCs of the Flexi BSC product
family. This solution therefore represents a merging of the Nokia Siemens Networks
GSM/EDGE BR and BSS product lines.
In such a scenario, NetAct is the OAM system used to manage the BTSplus connected
to the Flexi BSC product family. The overall OAM functionality is then provided both
directly by NetAct, as well as via the BR LMT (LMT Evolution) integrated in NetAct. The
LMT Evolution is used to configure and maintain the BTSplus hardware objects, which
are not supported by NetAct.The strict local maintenance connection to the BTSplus is
also supported by the LMT Evolution.
The mediation function between the BSS Abis interface implementation and the
BTSplus is implemented on the BTSplus itself. No hardware changes are required to the
BTSplus for it to support the BSS Abis implementation.
The Flexi BSC product family has been adapted, allowing it to manage the BTSplus as
a new BSS BTS type, in addition to the base station types of the BSS product line:
UltraSite EDGE BTS
MetroSite EDGE BTS
Talk-family BTS
Flexi EDGE BTS
The TRAU/eTRAU is not supported in this network configuration. Instead, the TCSM3i
has to be used.

1.1

Network elements
BTSplus, LMT Evolution and TRAU/eTRAU are products of the Nokia Siemens
Networks GSM/EDGE BR line.
The BTSplus product range can be divided into three type groupings:
BTSplus mainline:
BS-240 / BS-241
BS-240 II / 240 II B, 241 II / 241 II B
BS-240XL
BS-240XL II / BS-240XL II B
BS-40 II
BS-40/41
BS-82 II
BTSplus eMicro:
BS-82
BTSplus basic:
BS-240XS
BS-288
For more information on the individual network element types in the BR line, refer to the
individual product descriptions:
BS-240/241 product description
BS-240XS product description
BS-240 II / 240 II B / 241 II / 241 II B product description

DN0933257

Id:0900d8058063e948
Confidential

Introduction

BSS21469: BS2xx@Flexi BSC product family

BS-240XL product description


BS-240XL II / 240XL II B product description
BS-288 product description
BS-40 II product description
BS-40/41 product description
BS-82 product description
BS-82 II product description

Flexi BSC product family, UltraSite EDGE BTS, MetroSite BTS, Talk-family BTS, Flexi
EDGE BTS, NetAct and TCSM3i are products of the Nokia Siemens Networks
GSM/EDGE BSS line.
The Flexi BSC product family consists of:
BSC3i 660
BSC3i 1000
BSC3i 2000
Flexi BSC
For more information on the individual network element types in the BSS line, refer to
the individual product descriptions:
Flexi EDGE BTS product description
Product description of Nokia BSC3i high capacity base station controller
Product description of Flexi BSC
Product description of Nokia TCSM3i High Capacity Transcoder Submultiplexer

1.2

Terminology
In this feature description, the term operator is used to refer to the GSM/EDGE network
operator, while the operators customers are referred to as end customers or subscribers.
Throughout the document, reference is made to the different GSM/EDGE network
element implementations in the Nokia Siemens Networks GSM/EDGE BR and BSS
product lines. These are referred to in short as BR and BSS respectively.
Thus, for example, the Abis interface implementation used in the BR product line to
connect the BTSplus with the eBSC/BSC1 is referred to as the BR Abis implementation,
while the Abis interface implementation used in the BSS product line to connect the Flexi
EDGE BTS with the Flexi BSC is referred to as the BSS Abis implementation.
Throughout this feature description, the term Flexi BSC will be used to refer to all BSCs
of the Flexi BSC product family, namely the BSC3i 660, 1000 and 2000, as well as the
Flexi BSC.

1.3

Benefits for the operator


This network solution allows for both BSS base station types (e.g. Flexi EDGE BTS) and
BR BTSplus base stations to be operated by the same Flexi BSC within the same BSS
architecture. This means that the BTSplus is actually connected to the Flexi BSC via an
adaptation of the BSS Abis interface.

10

Id:0900d8058063e948
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Network architecture

2 Network architecture
The network architecture shown in Figure 1 illustrates the possible configurations for
managing BTSplus base stations with either the eBSC/BSC1 or the Flexi BSC product
family.

BTSplus
Modified BSS Abis

BSS BTS

BTSplus
BTSplus
BSS BTS
BTSplus

BR LMT
BR Abis

BSS Abis

eBSC/
BSC1

Flexi
BSC

Q3

O-link

NetAct

RC
BR LMT

Figure 1

Network architecture for managing BTSplus

When operating BTSplus in a BR RAN, the BTSplus base stations are managed by the
eBSC/BSC1. The BTSplus is connected to the eBSC/BSC1 using the BR implementation of the Abis interface. The corresponding OAM system is based on the RC, which
uses the O-link interface to connect the RC to the eBSC/BSC1.
BTSplus base stations operating in a mixed BR/BSS environment are managed by
BSCs of the Flexi BSC product family. In this case, the BTSplus is connected to the
Flexi BSC using a modified version of the BSS Abis interface. The OAM system is now
based on NetAct. An LMT Evolution in BR look and feel is integrated in the NetActbased OAM system and used to manage the BTSplus hardware-related objects, as

DN0933257

Id:0900d8058064b439
Confidential

11

Network architecture

BSS21469: BS2xx@Flexi BSC product family

these are not currently supported by NetAct. The LMT Evolution is also used to configure Abis transport parameters on location at the BTSplus site.
BTSplus base stations are managed by the Flexi BSC in almost the same way as that
used to manage the other BTS types (e.g. Flexi EDGE BTS). The most significant difference is in the way handover and power control issues are handled. Refer to Handover and power control for more information.
Additionally, the BSS Abis implementation used to manage BTSplus has adopted the
BR mechanism for assigning TRX signaling channels to LAPD links on the Abis interface, whereby the LAPD signaling data related to several TRXs is multiplexed onto a
single LAPD link. Refer to LAPD multiplexing for more information.
Refer to Operating guidelines: LMT Evolution for more information on using the BR
LMT.

12

Id:0900d8058064b439
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

2.1

Network architecture

BS-240XL II / BS-240XL II B
The BS-240XL II / BS-240XL II B represents the high end in the mainline of Nokia
Siemens Networks BTSplus base stations.
The architecture of the BS-240XL II and BS-240XL II B provides maximum performance to develop ultra high capacity BTSs with minimum footprint for rural and urban
applications.
Software-driven redundancy for core, power supply and broadcast channel modules
offer highest reliability and enable hot swapping, rack extension and TRX substitution
without service interruption.
The modular architecture and the flexible internal structure enable the BS-240XL II /
BS-240XL II B to provide new GSM features such as enhanced data rates for GSM evolution (EDGE). This platform ensures that network evolution is as smooth as possible.
The provision of a full spectrum of combining equipment allows high power and minimized number of antennas. High receiver sensitivity is also guaranteed.
Overview of the functionality - main features of BS-240XL II / BS-240XL II B

Casing variants: indoor version only

Maximum configuration:
2 racks with an entire quantity of 48 carriers
5 service racks housing power supply modules, battery backup and line equipment

Cell configurations:
Up to 6 cells per rack
Up to 12 cells per BS-240XL II / BS-240XL II B
Concentric omnicell: one cell with inner and complete supply area
Concentric multicells: multicell with several sectors plus inner supply area

Frequency configurations:
Single band
Dual band
Mixed cell configuration to enlarge GSM 900 cells with GSM 1800 frequencies,
or GSM 850 cells with GSM 1900 frequencies
Single cell
Multi cell

Combining options:
Antenna combining for the TX and RX path with duplexers
Antenna combining for the TX path with filter combiners
Antenna combining for the RX path with amplifying multicouplers
Duplexing of RX and TX path with high power duplexer
Mixed configurations of cells/sectors

For a detailed technical description please refer to BS-240XL II / BS-240XL II B product


description.

DN0933257

Id:0900d8058064b439
Confidential

13

Network architecture

2.2

BSS21469: BS2xx@Flexi BSC product family

BS-240 II / 240 II B / 241 II / 241 II B


The BS-240 II / 240 II B / 241 II / 241 II B represents the mainline of Nokia Siemens
Networks base stations (BR line).
The architecture of the BS-240 II / 240 II B / 241 II / 241 II B provides maximum flexibility
to develop ultra high capacity BTSs for rural and urban applications. With indoor and
outdoor cabinets, AC or DC power supply and a scalability from 1 to 7 cabinets, these
powerful dual-band base stations meet rising demand for higher capacity.
Software-driven redundancy for core, power supply and broadcast channel modules
offer highest reliability and enable hot swapping, rack extension and TRX substitution
without service interruption.
The provision of a full spectrum of combining equipment allows high power and minimized number of antennas. High receiver sensitivity is also guaranteed.
Overview of the functionality - main features of BS-240 II / 240 II B / 241 II / 241 II B

Casing variants:
Indoor version: BS-240 II / BS-240 II B
Outdoor version: BS-241 II / 241 II B

Maximum configuration:
3 cabinets with an entire quantity of 48 carriers
4 service cabinets housing power supply modules, battery backup and line
equipment

Cell configurations:
Up to 6 cells per rack
Up to 12 cells per BS-240 II / 240 II B / 241 II / 241 II B
Concentric omnicell: one cell with inner and complete supply area
Concentric multicells: multicell with several sectors plus inner supply area

Frequency configurations:
Single band
Dual band
Mixed cell configuration to enlarge GSM 900 cells with GSM 1800 frequencies,
or GSM 850 cells with GSM 1900 frequencies
Single cell
Multi cell

Combining options:
Antenna combining for the TX and RX path with duplexers
Antenna combining for the TX path with filter combiners
Antenna combining for the RX path with amplifying multicouplers
Duplexing of RX and TX path with high power duplexer
Mixed configurations of cells/sectors

For a detailed technical description please refer to BS-240/241 II/241 II B product


description.

14

Id:0900d8058064b439
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

2.3

Network architecture

BS-288
The BS-288 is ideally suited for micro cell or urban hot spot applications with a small
footprint and reduced requirements for cell configuration.
Overview of the functionality - main features of BS-288

Casing:
Indoor version only

Maximum configuration:
One rack with 12 carriers

Cell configurations:
Up to 6 cells
Single cell
Multiple cell

Frequency configurations:
Single band
Single cell
Multi cell

Combining options:
Duplex combining of RX and TX path with low noise amplifier for RX path

For a detailed technical description please refer to BS-288 product description.

DN0933257

Id:0900d8058064b439
Confidential

15

Network architecture

2.4

BSS21469: BS2xx@Flexi BSC product family

BS-82 II
Designed for microcellular coverage and far beyond, the remarkably powerful
Enhanced Micro BTS BS-82 II delivers impressive performance and high RF output. Its
coverage and range is comparable to the BTSplus lines flagship product. Rugged, versatile, powerful and compact, BS-82 II is an indoor/outdoor solution catering to all types
of micro cellular applications.
Overview of the functionality - main features of BS-82 II

Casing:
Indoor and outdoor configurations with one universal type of shelter
wall mounting or pole mounting option

Maximum configuration:
3 cabinets with an entire quantity of 12 carriers

Cell configurations per shelter:


Up to 2 cells per cabinet
Up to 6 cells per BS-82 II
Single cell
Multi cell

Frequency configurations:
Single band
Dual band with at least 2 cabinets
Single cell
Multi cell

Combining options:
Antenna combining for the TX and RX path with duplexers
Antenna combining for the RX path with amplifying multicouplers
Mixed configurations of cells/sectors

For a detailed technical description please refer to BS-82 II product description.

16

Id:0900d8058064b439
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Operation and maintenance

3 Operation and maintenance


Figure 2 shows the network configuration for OAM procedures on the BTSplus when
managed by the Flexi BSC product family.

BTSplus
T-interface

LMT Evolution
(remote)

BTSplus

LMT Evolution
(local)
T-int. over
Q1 over Abis

T-int. over Q1
over TCP/IP
(using GCS protocol)

NetAct

T-int. over X.25/LAN


(using GCS protocol)

Figure 2

Flexi
BSC

Flexi
BSC

OAM network architecture for administering the BTSplus

NetAct is the main OAM system for managing meshed networks consisting of the Flexi
BSC, BTSplus and other BTS site types (e.g. Flexi EDGE BTS). In order to provide a
common platform for managing base stations of all types with NetAct and the Flexi BSC,
the BTSplus maps BR info model objects, related to network and transport configuration
and management, to equivalent objects in the BSS info model. Objects related to
hardware management of the BTSplus are however not mapped, and therefore need to
be configured and managed remotely via the BR LMT (LMT Evolution). For this reason,
LMT Evolution has been integrated into NetAct. The NetAct server can support several
instances of LMT Evolution in parallel, allowing for OAM activities related to several
BTSplus base stations.
LMT Evolution can also be connected to the BTSplus locally. The OAM interface used
is the T-interface, which is the proprietary interface for connecting LMT Evolution with
the BTSplus in the Nokia Siemens Networks GSM/EDGE BR product line. When using
LMT Evolution to manage BTSplus remotely or locally, you can only perform GET
actions on functional management objects in the BR info model, with the exception of
the BTSM managed object. Full remote OAM configurability is supported for hardwarerelated management objects, as well as for the BTSM managed object.

g
DN0933257

Either a local or a single remote LMT connection to a BTSplus is possible at one time.

Id:0900d8058068db3c
Confidential

17

Operation and maintenance

BSS21469: BS2xx@Flexi BSC product family

In case of a remote LMT connection via NetAct and the Flexi BSC, LMT Evolution and
the BSS Element Manager can be installed and run in parallel on the same system (for
example an OAM laptop). This allows for remote management of both BSS and BR
network elements using the same system. In case of a local LMT connection, either LMT
Evolution or the BSS Element Manager can be run at one time, even if both are installed
on the same system.
State and status management
State and status management notifications are presented by BTSplus to LMT Evolution
according to BR state and status management rules. This is done on the LMT GUI in BR
look and feel, and irrespective of whether BTSplus is being managed locally or remotely.
The Abis mediation function receives the necessary triggers from the BTSplus internal
subystems and maps these to BSS states and statuses accordingly. These are then
visible to the BSS OAM system.
Alarms
Alarms are presented by the BTSplus to LMT Evolution according to BR fault management rules. This is done on the LMT GUI in BR look and feel, and irrespective of whether
BTSplus is being managed locally or remotely.
Alarms raised by BTSplus are also mapped to BSS alarms and presented to the Flexi
BSC and NetAct according to BSS fault management rules. They are displayed on the
NetAct GUI with BSS look and feel.
External alarms related to the BTSplus are configured using LMT Evolution.

3.1

Remote configuration of BTSplus hardware objects


Remote LMT management of BTSplus hardware objects is done using Remote Node
Manager (Q1) sessions based on the GCS protocol and the NetAct Node Manager
Server tool. Commands and responses related to the T-interface are encapsulated in
Q1 data packets and relayed from/to the remote LMT and the BTSplus, via the Flexi
BSC.
In such a scenario:
LMT Evolution uses the service provided by GCS to open a connection towards the
BTSplus and to send commands to it. The commands are transmitted as T-interface
commands, just like those used in case of a local connection. A polling mechanism
on the LMT at application level allows for management, handling and termination of
remote sessions, as well as for the notification of events from the BTSplus to the
LMT.
LMT Evolution is installed as a node manager on NetAct GUIS. In addition to other
BSS Node Managers, LMT Evolution is also hosted on the Windows 2003-based
Node Manager Server, configured on NetAct GUIS.
GCS provides support for OSI connections using the OSI service of the NetAct Connectivity Server, in order to transfer Q1 commands to the BSC on top of the OSI
transport protocol. The OSI transport protocol is carried between NetAct and the
Flexi BSC using either X.25 or TCP/IP over LAN.
The Flexi BSC, when receiving a Q1 command from LMT Evolution via NetAct,
encapsulates this command using the Q1 Transmission Equipment Protocol and
directs it towards the respective BTSplus over the Abis interface. The reverse

18

Id:0900d8058068db3c
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Operation and maintenance

applies for when a Q1 data packet is sent from BTSplus to the LMT. Between NetAct
and the LMT, Q1 messages are carried over TCP/IP.
BTSplus establishes the Q1 Transmission Equipment Protocol with the Flexi BSC.
When BTSplus receives a Q1 Transmission Equipment Protocol message, it
extracts and process the LMT T-interface command. BTSplus is allowed to transmit
spontaneous notifications to LMT Evolution as a response to the polling messages
on the LMT-BTSplus interface.

Refer to the GCS user manual for more information on remote node management and
the GCS protocol.

DN0933257

Id:0900d8058068db3c
Confidential

19

Info model mediation

BSS21469: BS2xx@Flexi BSC product family

4 Info model mediation


The Abis interface mediation function between the BTSplus and the Flexi BSC product
family is responsible for the mapping of objects and parameters of the BR info model
related to the administration and management of the BTSplus, to the corresponding
objects and parameters in the BSS hierarchy, and vice versa. This mediation function is
implemented in the BTSplus software layer.
For a detailed implementation of this BR-BSS mediation function, refer to Abis mediation of BTSplus parameters/attributes towards the Flexi BSC product family.
For the BR info model parameters that cannot be mapped onto existing BSS parameters, new parameters are added to the BSS Abis interface and the Flexi BSC RNW
parameter database.

4.1

Handling of segments
In the BR product line info model, every GSM sector as seen by an MS is described
through a single BTS object. Every BTS object contains different TRX objects. For
example, a dual band cell is associated to one BTS object where multiple TRXs are
defined: some working on the 900 MHz band, others on the 1800 MHz band.
In the Flexi BSC, more than one BTS object are required to configure a dual band cell.
All the BTS objects that make up a GSM sector are collected under a unique SEG
(segment) object. Therefore, in the Flexi BSC, the dual band cell is described by a single
SEG object, two BTS objects (one for the 900 MHz frequency band and one for the 1800
MHz band) and several TRX objects. In this case, however, all TRXs of a BTS object
have to use the same frequency band.
The Abis mediation function implemented between the BTSplus and the Flexi BSC does
not mediate the BTS object structure. Therefore, when the Flexi BSC managed object
tree has two BTS objects (one for the GSM band and one for the DCS band), the
BTSplus tree is changed to now also contain two BTS objects. In comparison, before
migration of the BTSplus, when it was still administered by the eBSC/BSC1, the same
configuration was represented by one BTS object. A new segmentId attribute is used
in the BTS object on the BTSplus to identify the BTS objects as belonging to the same
segment.
A consequence of this mediation function is that the BTSplus BTS object may now not
have a BCCH. Indeed, in a dual band cell configuration, only the BTS object operating
in the GSM frequency band has a BCCH, while the second BTS object in the same
segment only has traffic channels.

4.2

Migrating TRXs from BTSM to BCF


The BTSM object in the BR product line info model provides services to control the
functionality of one or more BTSplus base stations located at the same site. It performs
all the operation and maintenance functions common to all TRXs.
The equivalent managed object on the Flexi BSC is the BCF object. However, while
the BTSM object can support up to 48 TRXs, the BCF object can only recognize 32
TRXs. Even if you can have up to 48 hardware antennae installed in a BTSplus site,
when the BTSplus is administered by the Flexi BSC, you will only see the first 32. Therefore, you need to select which TRXs you want to migrate.

20

Id:0900d8058068bbfd
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Abis interface

5 Abis interface
The BSS Abis interface is used to connect one or more BTSplus base stations with the
Flexi BSC product family. It replaces the BR Abis interface used to connect the BTSplus
base stations with the eBSC/BSC1 in the Nokia Siemens Networks BR product line.
The Abis interface used to connect BTSplus base stations is therefore almost the same
as that used to connect other BSS BTS types (e.g. Flexi EDGE BTS) with the Flexi BSC
product family. One important difference is in the way TRX signaling channels are
assigned to LAPD links on the Abis interface. In case of the BTSplus, the BSS Abis
interface has been modified to adopt the BR mechanism, whereby the LAPD signaling
data related to several TRXs is multiplexed onto a single LAPD link. Refer to LAPD multiplexing for more information.
Abis interface transport descibes the physical characteristics and transport configurations of the Abis interface. The differences between the BSS Abis interface when used
for the BTSplus and for a BSS BTS, and how they affect configuration procedures, are
described in Abis interface configuration.
Refer to the Abis EDGE dimensioning for BTSplus at the Flexi BSC product family for
more information on planning and dimensioning the Abis interface between the BTSplus
and the Flexi BSC.

The LMT Evolution is used to configure Abis transport parameters at the BTS.

5.1

Abis interface transport


The Abis interface is based on E1/T1 transmission lines. The physical characteristics of
the E1 and T1 interfaces are described in detail in Physical layer.
The possible transport configurations are described in detail in E1/T1 configurations.
If the Abis transport medium cannot provide the needed frequency stability and precision, it is possible to synchronize the BTSplus with an external 1 pps signal. Refer to
External synchronization for more information.
The Abis interface can be carried either over terrestrial or satellite links.

5.1.1

Physical layer
The BTS and BSC link interfaces are carried by standard E1/T1 transmission lines. The
recovered E1/T1 transmission clock can be used by the BTS to synchronize itself to the
BSC. If this clock is not reliable enough, the BTS can be synchronized with an external
clock source (see External synchronization).
If one E1/T1 line is not enough to serve all the TRXs of a BTSplus, up to 8 E1/T1 lines
per BTSplus can be configured. Possible applications include:
Serving large-capacity sites
Providing redundancy by distributing TRXs of a cell/sector over two lines
Characteristics of E1 lines
E1 tranmission lines are defined by the ITU-T G.703, G.704 and G.706 recommendations. Their characteristics include:

DN0933257

Transfer rates of up to 2 Mbit/s

Id:0900d805807f73a1
Confidential

21

Abis interface

BSS21469: BS2xx@Flexi BSC product family

120 Ohm balanced lines (symmetrical pair) or 75 Ohm unbalanced lines (coaxial
cables).
HDB3 line code
Frame formats:
Doubleframe
CRC4 Multiframe, including CRC4 checks to supervise the line
Remote alarm indication using the A-bit
Frame alignment loss and recovery conforming to the G.732 recommendations
Fault condition management conforming to the G.732 recommendations

Characteristics of T1 lines
T1 transmission lines are defined by the ANSI T1.403 standards. Their characteristics
include:
Transfer rates of up to 1.544 Mbit/s
100 Ohm balanced interfaces
B8ZS line code
Frame formats:
Superframe format (SF)
Extended superframe format (ESF), including CRC6 checks
Remote (yellow) alarm indication using framing bit 12 (SF format) or periodical
pattern (ESF)
Short haul interfaces of type DSX-1, with line length of 0 to 133 ft.
The E1/T1 transmission interface signal connected to the BTS on the Abis interface has
the following characteristics:
Long-term line clock frequency stability, better than 1 x 10 exp-8
Jitter and wander tolerance conforming to the ITU-T G.823 recommendations
The line clock should be synchronized to the BSC clock to avoid data slips; clocktransparent transmission links are required between the BSC and the connected
BTS.
In addition, the following devices can be installed on the BTS cabinets:
Microwave equipment
Network terminations for optical fibers (NTPM-GF)
Network terminations for copper lines (NTPM-KU)

5.1.2

E1/T1 configurations
This section gives an overview of the E1/T1 configurations that are possible when connecting several BTS Plus base stations to the Flexi BSC product family. For more details
on the individual configurations, refer to the Abis EDGE dimensioning for BTSplus at
the Flexi BSC product family.
Figure 3 describes the possible transport configurations on the Abis interface connecting one or more BTSplus base stations with the Flexi BSC product family. Configurations
including base stations of both the BTSplus and other BSS BTS types (e.g. Flexi EDGE
BTS) are also supported.

22

Id:0900d805807f73a1
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Abis interface

E1/T1
P1

P2

P3

P6
P7

E1/T1
P0

P1

P0

...

Flexi
BSC

E1/T1
P0

BTS
Plus 1

E1/T1

P4

BTS
Plus 2

BTS
Plus 3

E1/T1
LIF 1

P0

Flexi
BTS 1

Figure 3

BTS
Plus 4

Configurations of the Abis interface

In Figure 3, P0/P1, P2/P3 .. P6/P7 represent BTSplus E1/T1 PCM port pairs. These
are short connected by relays in case of a BTS reset. LIF 1 is the line interface to the
Flexi EDGE BTS.
The figure illustrates the following transport configurations:
Star configuration, used to connect:
BTSplus 3 on P0
BTSplus 4 on P0
Flexi EDGE BTS 1 on LIF 1
Multidrop configuration in BTSplus 1:
over P0/P1 towards BTSplus 2
over P2/P3 towards Flexi EDGE BTS 1
Multidrop configuration in BTSplus 2:
over P0/P1 towards BTSplus 3
Cross-connect configuration over P4 in BTSplus 2 towards BTSplus 4.
The BTSplus supports several PCM ports, represented by the BPORT managed object
as seen by the LMT Evolution. The total number of configurable BPORT instances
depends on the corresponding COBA and COSA board configurations. Refer to the repsective BTSplus product descriptions for more information.

5.1.2.1

Star configuration
A star connection is a point-to-point connection between the BSC and one BTS site. A
star transport configuration is composed of one or more E1/T1 lines, where each line
connects one BTS site. The line is terminated at the BTS. In the downlink direction, the

DN0933257

Id:0900d805807f73a1
Confidential

23

Abis interface

BSS21469: BS2xx@Flexi BSC product family

BTS extracts data from its assigned PCM timeslots. It fills the relevant PCM timeslots
for uplink transmission, and timeslots that are not assigned are filled with an idle pattern.
Figure 4 shows the relevant managed objects and hardware units involved in
managing the star connection on the Abis interface between the BTSplus and the Flexi
BSC.

Flexi BSC

BTS Plus
PCM time slot carrying LAPD OAM
and TRX signaling: LAPDLE object
in BTS Plus

BCSU/ET

LAPD
object

Figure 4

...

... 31

COBA/COSA

BPORT
object

Object relationship in an Abis star connection

One BPORT object instance in the BTSplus (BR) info model holds the configuration data
of one line interface port. The instance number of the object is related to the port number
of the corresponding line plug. For example, instance 0 is related to port 1, which allows
the connection to line 1.
The BTSplus BPORT object instance is mapped onto a Flexi BSC PCM, identified by
the corresponding PCM port ID parameter.

5.1.2.2

Multidrop configuration
A multidrop configuration allows an E1/T1 line to be shared between two or more BTS
sites. Each BTS on the multidrop chain extracts or fills its assigned PCM timeslots, and
routes the other timeslots to the following BTS on the other port in the same port pair.
The unused timeslots are forwarded without being changed. Timeslots that are
extracted are filled with an idle pattern before being forwarded.
In order to establish such a drop/insert connection, both ports of the BTS involved are
configured as supporting the multidrop configuration. This is done using the LCONF
attribute of the BPORT object via the LMT Evolution.
It is possible to create mixed BTSplus and Flexi EDGE BTS multidrop configurations. A
Flexi EDGE BTS reset affects all following sites in the chain, while a BTSplus reset does
not.

24

Id:0900d805807f73a1
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

5.1.2.3

Abis interface

Cross-connect configuration
Star or multidrop configurations alone do not allow for hub and spoke configurations.
Such configurations can only be realized by means of cross-connecting equipment with
drop/insert functionality. Such cross-connect functionality is integrated in the BTSplus
by means of the XCONNECT and BPORT managed objects.
In a cross-connected configuration, individual 64 kbit/s PCM timeslots can be extracted
from E1/T1 lines in a star or multidrop configuration. These extracted timeslots are
inserted into another E1/T1 line starting at the cross-connected BTSplus. Cross-connected configurations including both the BTSplus and the Flexi EDGE BTS are allowed.
In case of a BTS reset, all cross connections are interrupted.
Each XCONNECT managed object instance in a BTSplus is related to a primary BPORT
instance. The MPTSL[xx] attribute of the XCONNECT object defines a target BPORT
and target timeslot for every timeslot [xx] arriving on the primary port (or port pair in case
of a multidrop circuit).
By using cross-connect configurations, the BTSplus can be used as a merging station
for several low-capacity sites using the same Abis link towards the BSC. It can also be
used to convert a PCM 30 link into a PCM 24 link.

5.1.3

External synchronization
If the Abis transport medium is unable to provide the needed frequency stability and precision (as defined by 3GPP standards for the air interface), the BTS can be synchronized to an external 1pps signal. This can happen, for example, in cases where the Abis
interface is implemented on:

E1/T1 via a fixed network with poor clock quality


Satellite links

The external 1pps signal interface is provided on all types of BTSplus base station,
except for the BS-82.
If the external 1pps input fails, the BTS does not use the Abis line as a secondary synchronization source but falls back directly to the internal holdover mode.

5.1.3.1

Functional overview/details
The External 1pps interface support for BTS feature offers a 1pps input interface for
an external clock source.

DN0933257

Id:0900d805807f73a1
Confidential

25

Abis interface

BSS21469: BS2xx@Flexi BSC product family

1pps
sync input

Abis I/F
sync input

OC-VCXO

COBA

BTS

Internal
clock output

CU

CU

CU

Um I/F

Figure 5

Functional overview

As shown in Figure 5, the BTS can synchronize either to an Abis line or to an external
clock source. This can be configured by network operators by setting the corresponding
attribute value of an MMI parameter. Such an external clock source will be in most cases
a 3rd party GPS receiver; but in general any other device fulfilling the requirements of
the interface specification can be connected.
The External 1pps interface support for BTS feature offers a balanced 1pps RS-422
based clock interface. The 1pps signal in balanced mode provides an excellent
immunity against electromagnetic disturbance and ground potential interface.
Once enabled by network operators, the BTS synchronizes to the incoming 1pps signal
of the external device (using the rising edge of the 1pps signal on the line). The BTS
continously monitors the accuracy of the synchronization source and changes automatically to the internal hold mode if the external source fails or is not available.

The primary evaluation of the 1pps accuracy has to be done by the external source itself;
if the accuracy of the external source is not sufficient the output of the 1pps clock must
not be enabled by the external source.
An automatic fallback to the synchronization via Abis line makes no sense because in
this use case there is no required clock precision from the Abis transport medium.
If the external clock is a GPS receiver and is started simultaneously with the BTS, the
systems startup time is increased due to the fact that the GPS receiver needs time to
reach the required precision.
If no 1pps clock source is available at the startup of the BTS, call processing starts using
the internal holdover mode.
Whenever switching to the internal holdover mode, an alarm will be generated.

26

Id:0900d805807f73a1
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

5.2

Abis interface

Abis interface configuration


PCM lines are created on the Abis interface between the BTSplus and the Flexi BSC
product family, to carry traffic channel and signaling data in both directions. PCM 30 is
carried on E1 transmission lines with a throughput of 2 Mbit/s. PCM 24 is carried on T1
transmission lines with a throughput of 1.5 Mbit/s.
A PCM line is divided into timeslots of 8 bits, each having a throughput of 64 kbit/s. A
PCM frame is a grouping of 32 such timeslots for PCM 30, or 24 such timeslots for PCM
24.
From a configuration point of view, transmission bits on a PCM line can be assigned
using a 16 kbit/s granularity, i.e. in groupings of 2 bits. This corresponds to the throughput of a full-rate traffic channel on the radio interface.
PCM channels can therefore be allocated to the following:
Signaling data for the LAPD protocol on the Abis interface. LAPD links can be
created by allocating timeslots of 16 kbit/s (2 PCM bits), 32 kbit/s (4 PCM bits) or 64
kbit/s (8 PCM bits) for the LAPD signaling data. Refer to LAPD multiplexing for
more information.
Transportation of TRAU/PCU frames of a single traffic channel or TRX timeslot. The
assignment of traffic channels to PCM 16kbit/s timeslots is static. It applies to:
CS services for speech: HR, FR, EFR, WMR, WB-AMR (codecs fitting in GMSK
coding schemes)
CS data rates of 2.4, 4.8, 9.6 and 14.4 kbit/s
PCU frames for GPRS restricted to CS1 and CS2
Master PCU frames for use in GPRS and EGPRS
EDAP resources for the transportation of EGPRS/EDGE packet data timeslots that
require more than 16 kbit/s.
The relevant configuration information is obtained from the management plane alignment with the BSC. An example PCM configuration for the Abis interface connecting a
BTSplus to a Flexi BSC is given in Example PCM allocation.

5.2.1

LAPD multiplexing
Figure 6 shows an LAPD link configuration for the Abis interface, when used to connect
a BSS BTS (e.g. Flexi EDGE BTS) with a Flexi BSC. In this configuration, a dedicated
physical LAPD link is provided for each TRX. A physical LAPD link is associated with
an LAPD signaling channel assigned to a PCM timeslot, and can have a throughput of
16, 32 or 64 kbit/s.

DN0933257

Id:0900d805807f73a1
Confidential

27

Abis interface

TRX3
TEI3

BSS21469: BS2xx@Flexi BSC product family

TRX1
TRX2 TEI1
TEI2

LAPD 1

Flexi
BTS

Figure 6

LAPD 2
LAPD 3

Dynamic Abis

Flexi
BSC

Abis LAPD configuration for the Flexi EDGE BTS

Figure 7 shows how the LAPD configuration is done on the Abis interface connecting
a BTSplus base station with the Flexi BSC. In this case, the LAPD signaling data related
to several TRXs is multiplexed onto one physical LAPD link, defined by a 16, 32 or 64
kbit/s PCM timeslot.

TRX3
TEI3

TRX1
TRX2 TEI1
TEI2

LAPD

BTS
Plus

Figure 7

Dynamic Abis

Flexi
BSC

Abis LAPD multiplexing for the BTSplus

A PCM line can carry more than one physical LAPD link, but a physical link cannot be
shared between several PCM lines.
The maximum number of physical LAPD channels that can be configured per BTSplus
is 11. This maximum number is a result of hardware constraints: there are 11 HDLC controllers available for LAPD links on the COBA module in the BTSplus. However, the Flexi
BSC can manage up to 32 TRXs per BTSplus (i.e. per BCF object). Therefore, several
TRXs belonging to a BTSplus base station can be configured on a common physical
LAPD link. For this purpose, up to 16 simultaneous signaling data link connections, or
logical LAPD links, can be multiplexed onto one physical LAPD link. This method
allows for optimized use of the available LAPD channels, and therefore reduces the signaling bandwidth required.

28

Id:0900d805807f73a1
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Abis interface

Each logical LAPD link inside a physical LAPD link is identified by the value of the (TEI,
SAPI) pair in the layer 2 header. Each TEI value uniquely identifies the radio signaling
channel of one TRX (TRXSIG). TEI value 1 is allocated for OAM signaling (OMUSIG),
and TEI value 127 is used for broadcasting. The SAPI value identifies the type of layer
2 service for which the LAPD channel is used:
SAPI value 0 is used for TRXSIG
SAPI value 62 is used for OMUSIG
SAPI value 63 is used for layer 2 management

5.2.1.1

LAPD logical link configuration


The TRX to LAPD association is set up in two phases:
1. During network element installation, you need to configure the physical LAPD
channels required, and distribute the TRXSIG logical links across these channels on
the BSC side. This is the static configuration phase. In this phase, the TEI value
1 is allocated to OMUSIG. This value is fixed and cannot be configured.
The LAPD physical links are configured on the BTSplus via the LMT Evolution. The
corresponding object is the LAPDLE object. This configuration must match the BSC
PCM configurations (2 Mbit/s or 1.5 Mbit/s), meaning that the same timeslots must
be configured on the Flexi BSC side. However, LAPD link configuration in the
BTSplus and the Flexi BSC can be done independently and at different times.
The bandwidth of the LAPD physical link can be 16, 32 or 64 kbit/s. Each LAPD
physical link can have a different bandwidth.
2. In the second, dynamic configuration phase, the Flexi BSC notifies the BTSplus
of the associations between the logical LAPDs for each TRX (the TRXSIGs) and the
physical LAPD timeslots. This is done after the establishment of an active logical
LAPD link for OMUSIG. In this phase, the BTSplus also associates TEI values with
TRXSIG logical LAPD links. A new TEI is assigned by re-using the object identity of
the corresponding TRX. The range for these TEI values is 1..63.
The new multiplexed logical LAPD signaling link can only be used when connecting
base stations of type BTSplus. When you create BCF and TRX objects, the Flexi BSC
only allows you to use this multiplexed D-channel type if you are configuring a BTSplus
site. The BTSplus releases TRXSIG LAPD links when the corresponding TRX is
deleted.

g
5.2.1.2

TRXSIG and OMUSIG channels that share the same timeslot (physical LAPD link) must
be configured to the same BCSU unit and to the same signaling terminal (AS7).

LAPD redundancy
LAPD redundancy helps to prevent BTSplus site loss in case of a physical LAPD link
failure. The following mechanism is implemented:
If a physical LAPD link fails containing TRXSIG related to a BCCH TRX, the BSC
moves the BCCH to another TRX in the same BTS object for which the TRXSIG link
is operational.
If a physical LAPD link containing OMUSIG fails, the BSC raises an alarm but no
recovery actions are triggered. There would be no impact on the working calls and
new calls can be initiated on the TRX, if corresponding TRXSIG is established. In

DN0933257

Id:0900d805807f73a1
Confidential

29

Abis interface

BSS21469: BS2xx@Flexi BSC product family

case of TRXSIG interruption RF transmission on corresponding TRXs will be


stopped.
Radio network configuration changes are not possible while the OMUSIG link is
down.
If a physical LAPD link fails containing TRXSIG related to a non-BCCH TRX, no
recovery actions are triggered.

In BR OMUSIG redundancy is supported. If the OMU get down at runtime then OMU
sig will be configured on an other working LAPD link and there is no impact on the
working TRXs of another ET link.
However in the BSS OMU sig redundancy is not supported. So in Gemini OMU sig
behavior is adopted in the same way as the BSS one . In Gemini if the OMU sig is down
longer than 1 minute then the LAPD link of working TRXs will be blocked.
Reason behind this different behavior from Flexi Edge is due to the handover parameter
which is updated by the BSC to BTS every minute on OMU sig at runtime. So in this case
if OMU sig is down all TRXs signaling link working on other ET are marked blocked. In
Flexi BTS handover information is maintained by BSC itself and OMU sig is not being
used to maintain the working calls functionality so there is no impact on the other TRXs
LAPD link configured on different ET.

5.2.2

EDAP handling
EDAP handling is not supported on the CU/GCU hardware units, meaning that these
units only support GPRS CS1 and CS2 using standard PCU frames. CS3 and CS4 are
not supported. The ECU and FlexCU hardware units support all EGPRS coding
schemes. The Flexi BSC is able to distinguish between the different capabilities of the
various CUs of the BTSplus.
The number of EDAPs that can be configured and shared among more than one TRX
is limited, and depends on the hardware variant of the COBA module.

5.2.3

Example PCM allocation


Figure 8 shows an example allocation of transmission bits on a 2 Mbit/s PCM line. This
example represents an optimized allocation where 12 TRXs have been fitted onto the
PCM line. A maximum of 12 TRXs can normally be fitted onto a 2Mbit/s PCM line, and
up to 10 TRXs onto a 1.5 Mbit/s PCM line. The TCH resources are assigned statically.
The signaling channels for these 12 TRXs and for OAM has been fitted into 3 physical
LAPD channels, with a total bandwidth of 128 kbit/s.
The Compressed Abis time slot allocation feature makes it possible for unused or
redundant TCH capacity on the PCM line to be re-allocated to signaling channels
(logical LAPD links). With this solution, the assignment of PCM bits can be used more
efficiently to fit up to 15 TRXs on a 2 Mbit/s PCM line. In the example shown in Figure
8, the PCM bits corresponding to the BCCH and SDCCH are used to carry 32 kbit/s
physical LAPD channels.
Refer to Compressed Abis time slot allocation for more information.
The remaining 64 kbit/s timeslots on the PCM line are used for the dynamic assignment
of EDAP resources. Dynamic allocation of PCM subslots in this section is done for slave
frames used for:
GPRS PCU frames CS2-CS4

30

Id:0900d805807f73a1
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Abis interface

EGPRS PCU frames MCS2-MCS9

If additional transport capacity is needed for (E)GPRS rates that are higher than 16
kbit/s, this is dynamically assigned on a per-PCU frame basis from an EDAP pool of this
PCM line. In the PCU master frame of a connection, the uplink and downlink allocations
are described by the indication of PCM timeslot, subslot and the number of subchannels.

DN0933257

Id:0900d805807f73a1
Confidential

31

Abis interface

BSS21469: BS2xx@Flexi BSC product family

Bits
1

E1/T1
timeslot

synchronization and link management

LAPD1 64kbit/s

LAPD2 32 kbit/s

TCH2

TCH3

TCH4

TCH5

TCH6

TCH7

TCH0

TCH1

TCH2

TCH3

TCH4

TCH5

TCH6

TCH7

TCH0

TCH1

TCH2

TCH3

TCH4

TCH5

TCH6

TCH7

TCH0

TCH1

TCH2

TCH3

TCH4

TCH5

TCH6

TCH7

TCH2

TCH3

10

LAPD3 32 kbit/s

11

TCH4

TCH5

TCH6

TCH7

12

TCH0

TCH1

TCH2

TCH3

13

TCH4

TCH5

TCH6

TCH7

14

TCH0

TCH1

TCH2

TCH3

15

TCH4

TCH5

TCH6

TCH7

16

TCH0

TCH1

TCH2

TCH3

17

TCH4

TCH5

TCH6

TCH7

18

BCCH

SDCCH

TCH2

TCH3

19

TCH4

TCH5

TCH6

TCH7

20

TCH0

TCH1

TCH2

TCH3

21

TCH4

TCH5

TCH6

TCH7

22

TCH0

TCH1

TCH2

TCH3

23

TCH4

TCH5

TCH6

TCH7

24

TCH0

TCH1

TCH2

TCH3

25

TCH4

TCH5

TCH6

TCH7

26

EDAP1

27

EDAP2

28

EDAP3

29

EDAP4

30

EDAP5

31

unused

Figure 8

32

TRX1

TRX2

TRX3

TRX4

TRX5

TRX6

TRX7

TRX8

TRX9

TRX10

TRX11

TRX12

Example of an optimized PCM line allocation

Id:0900d805807f73a1
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Migration of complex cells

6 Migration of complex cells


The standard GSM cell is represented in the BTSplus by the BTS object with CELLTYPE=STDCELL. The maximum cell radius for GSM900/GSM850 is of 35 km. For
DCS1800/PCS1900, this value is smaller due to the more adverse radio propagation
characteristics of higher frequencies. Standard cells do not distinguish between various
coverage areas.
When administering the BTSplus with the Flexi BSC product family, the Abis mediation
function maps the BTS object to the BTS object in the BSS info model. A new BTSplus
parameter, SEGMENTID, is defined to facilitate segment configuration in the same
way as done for other base stations connected to the Flexi BSC (refer to Multi BCF
control for more information).
A standard BTSplus cell configured using the eBSC/BSC1 is automatically migrated to
the Flexi BSC using the exporter migration tool. The new BTS number, as well as the
segment ID and name are given by the operater to the migration tool using the control
file input. Refer to Migration of BR complex cells for more information.
When migrating the following more complex overlay cell structure types to the Flexi
BSC, special considerations have to be taken into account:
Dual band cells
Concentric cells
Extended cells

6.1

Dual band cells


Dual band standard cells in the BTSplus provide two frequency bands within the area of
a standard cell. The cells radius is assumed to be the same for the two frequency
bands, i.e. both bands have well-matching cell borders. The frequency band combinations GSM850/PCS1900, GSM900/DCS1800 and GSM850/DCS1800 MHz are supported. Dual band standard cells are also called mixed cells, and are used to increase
the capacity of a cell.
In a BR RAN, a dual band standard cell is managed by a single BTS object with CELLTYPE=DBSTDCELL. One common BCCH is set up for both frequency bands to save
radio capacity and avoid additional BCCH planning activities. The BCCH frequency can
be chosen from both frequency bands.
When migrating such a dual band cell to the Flexi BSC, the BR BTS object is split by the
exporter migration tool into two BSS BTS objects in a pair. The pair is identified by
means of the segment ID and name. This information, together with the numbers of the
new BTS objects, are given by the operater to the migration tool using the control file
input.
The first BTS object in the new pair corresponds to the BCCH TRX band. The HOC and
PWRC (POC) objects are then only associated to this BTS object.
Refer to Migration of BR complex cells for more information.

6.2

Concentric cells
In a BR RAN, controlled by the eBSC/BSC1, a concentric cell is defined as a cell in
which different TRXs have different ranges, as defined by the maximum power output
of the particular TRX. A selection of TRXs in the cell are designated to operate with a

DN0933257

Id:0900d8058062e149
Confidential

33

Migration of complex cells

BSS21469: BS2xx@Flexi BSC product family

lower maximum power output, and therefore with a smaller range. These TRXs serve
the inner area, while TRXs with the higher output power serve the complete area (see
Figure 9).

Concentric cell

Inner
area

Figure 9

complete
area

Concentric cell areas in a BR RAN

The TRXs in the inner area allow tighter reuse of frequencies, thereby increasing their
capacity but at the same time making them more vulnerable to interference. All the
control channels of the concentric cell (BCCH, CCCH, SDCCH, CBCH) are carried on
the TRXs of the complete area.
The corresponding feature in the Flexi BSC product family is (non-BCCH) frequency
super-reuse (see Technical description of intelligent underlay-overlay). The superreuse frequencies correspond to the TRXs of the inner area. Whether a frequency is
super-reused or not is configured by the trxFrequencyType parameter of the TRX object
in the Flexi BSC.
The different link budgets of regular and super-reuse frequencies have to be taken into
account in assignment procedures and handover evaluation.

6.2.1

Dual band operation


In the BR RAN, different frequency bands can be assigned to the inner and complete
areas of a concentric cell. Such concentric cells are also called mixed cells. One
common BCCH is used for both areas. The different TRX coverage areas for dual band
concentric cells are determined by the different TRX output powers of the TRX hardware, and the different propagation attenuations of the different frequency bands used.
Considering the frequency propagation characteristics and the band-specific maximum
cell radius, the most useful configuration is to use GSM900 or GSM850 frequencies for
the complete area (and therefore for the BCCH and SDCCHs), and to assign DCS1800
or PCS1900 frequencies to the inner area. However, the opposite configuration is also
technically possible.

6.2.2

Migration of concentric cells to the Flexi BSC


When using the Flexi BSC product family to administer the BTSplus, the concentric cell
configurations are managed as standard BTS objects if they are not dual band. The trx-

34

Id:0900d8058062e149
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Migration of complex cells

FrequencyType parameter of the TRX object is used to define a group of TRXs as


super-reuse frequencies (corresponding to the inner area) and the rest as regular frequencies (corresponding to the complete area).
Dual-band concentric cells are managed by the Flexi BSC as two separate BTS objects
created in the same segment. Each BTS object operates in a separate frequency band.
The (non-BCCH) BTS object corresponding to the frequency band of the inner area in
the BR concentric cell has all its TRXs configured as super-reuse frequencies. Refer to
Dual band cells for more information on migrating dual band BR cells to the Flexi BSC.

6.3

Extended cells
When rehosting a BTSplus from an eBSC/BSC1 to the Flexi BSC product family, configuration information concerning extended cells is not migrated automatically by the
exporter tool. Therefore, extended cells must be reconfigured as necessary, according to the Flexi BSC product family configuration rules.
The Flexi BSC product family solution for extended cells is applied to both the CS and
PS domains. The E-TRX type parameter of the TRX managed object in the Flexi BSC
is used to determine the coverage area in which a TRX is operating. Up to three areas
are defined:
Near area (N-TRX) for TRXs covering 0-35 km
Extended area (E-TRX) for TRXs covering a 35 km range, where the maximum
distance can be within the range 36-70 km
Super extended area (S-TRX) for TRXs covering a 35 km range, where the
maximum distance can be within the range 71-105 km
In the near area, the standard implementation is to delay the uplink by 3 timeslots with
respect to the downlink. The distance between the mobile station and the BTSplus is
represented by the TA, which can have a value of 0 to 63, representing a maximum of
35 km. The TA value is communicated by the BTSplus to the mobile station via the
SACCH during a call, or using the continuous TA estimation procedure in a PS call.
For the extended and super extended areas, the uplink TRX is further delayed by 116.3
s and 232.6 s respectively, allowing the same approach to be used to calculate the
TA on TRXs in the extended areas.

To configure three coverage areas, you need 3 TRX types. Additional hardware needs
to be installed if there are less than 3 TRXs per sector.
In order to support extended cells, a new channel type ERACH is defined and supported
by the BTSplus. The ERACH receives the uplink access burst when the mobile station
is in the extended and super extended coverage areas. Two ERACH channels are
needed, one on the TRX that is handling the extended cell, and the other one on the
TRX that is handling the super extended cell. Both channels are located on timeslot 0 of
the respective TRX and on the BCCH frequency, in analogy to the standard RACH.
Since all the timeslots 0 on the 3 TRXs have to use the BCCH frequency, the use of
extended cells also has an impact on the frequency hopping scheme to be used.
The Flexi BSC solution for extended cells differs from the solution implemented by the
eBSC/BSC1, which is based on the use of a double timeslot for TRXs working in
extended mode. For this reason, when the BTSplus is connected to the Flexi BSC
product family, the Timing offset IE used with the eBSC/BSC1 is now redundant. In

DN0933257

Id:0900d8058062e149
Confidential

35

Migration of complex cells

BSS21469: BS2xx@Flexi BSC product family

addition, the Access delay IE is extended to up to 189 TA values, in compliance with


the BSS Long reach timeslot feature.

6.3.1

Configuring extended cells


Overlapping coverage areas may exist between the three areas, in which a mobile
station may be served by either of 2 TRXs. These are illustrated by the darker areas in
Figure 10. The three coverage areas are defined using the radius extension (EXT)
and super radius extension (SEXT) parameters of the BTS managed object in the Flexi
BSC.

super extended area

SMAX
MIN
SMIN

MAX

near area
35 km

35 km

EXT

XT
SE

extended area
35 km

Figure 10

Extended cell configuration

When planning the real coverage of the extended areas, it is recommended that you
plan an overlapping coverage area that is large enough to allow a mobile station to move
from one area to the next without disruption to traffic. The long reach time slots (LRTCH)
and extended cell GPRS/EDGE channels (EGTCH) also need to be dimensioned properly.
The MIN and MAX parameters of the HOC managed object in the Flexi BSC are used
to determine at what point the mobile station is reallocated from the extended area to
the normal area of an extended cell, and vice versa. The corresponding ranges of these
two parameters lie in the overlapping area between the near and extended areas. The
corresponding parameters in the overlapping area between the extended and super
extended areas are SMIN and SMAX respectively.
Thus, if a call is ongoing in an extended area, and the reported TA >= SMAX, the
BTSplus sends a HANDOVER CONDITION INDICATION message to the Flexi BSC, in
order to trigger an internal intra-cell handover to the super extended area. Likewise, if a
call is ongoing in a super extended area, and the reported TA <= SMIN, the BTSplus
sends a HANDOVER CONDITION INDICATION message to the Flexi BSC to trigger an
internal intra-cell handover to the extended area. Refer to Handover and power control
for more information on types of handover.

36

Id:0900d8058062e149
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Migration of complex cells

Refer to the Extended cell for GPRS/EDGE (BSS20094) and 105 km extended cell
(BSS21277) features for more information.

DN0933257

Id:0900d8058062e149
Confidential

37

Handover and power control

BSS21469: BS2xx@Flexi BSC product family

7 Handover and power control


The algorithms for handover decision and power control are handled by the BTSplus.
This contrasts with other BSS BTS types (e.g. Flexi EDGE BTS), where the respective
algorithms are handled by the Flexi BSC.

7.1

Handover
The handover process maintains a call in progress while the mobile subscriber is moving
through the network. In particular, service is not interrupted when the mobile subscriber
moves from cell of the network to another.
The following criteria are used to evaluate whether or not a handover is triggered:
To maintain link quality: the quality and level with which downlink signals are
received at the MS, as well as the quality and level with which uplink signals are
received at the TRX
To minimize interference (co-channel and adjacent channel interference): the
absolute MS-BTS distance and the transmission power of the MS
To optimize traffic distribution: the congestion state of the current cell and of the
adjacent cells
When operating the BTSplus with the Flexi BSC product family, the above criteria are
evaluated by the BTSplus itself. The respective algorithm used for a handover decision
is the same as that applied to handover situations in the BR RAN. On the other hand,
the evaluation and selection of the given target cells is handled by the BSC. The Flexi
BSC can only request the BTSplus to start a handover if this is necessary, for example
in case of congestion. The decision to activate AMR compression or decompression is
also taken in the BTSplus.
The parameters required for the BTSplus handover evaluation are provided by the BSC
and are forwarded to the BTSplus via the BTS OAM mediation software. The parameters concerned are related to the ADCE, ADJW and HOC managed objects in the BSS
info model.

7.1.1

Classification of handovers
Handover categories
Different handover categories can be identified with respect to a cell, a BSS (BSC-controlled) area and an MSC area. These categories are illustrated in Figure 11.

38

Id:0900d8058068be5c
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Handover and power control

-3#"

"3#"

(/(ANDOVER

)NTER -3#(/
)NTRA CELL(/

)NTRA -3#(/

)NTRA "33(/

"3#!
"3#!

-3#!

Figure 11

Handover categories

An inter-cell handover from a serving cell to an adjacent cell usually occurs either when
the handover measurements indicate low RXLEV (received signal strength) or RXQUAL
(received quality) values in the serving cell and a better RXLEV value in a surrounding
cell, or when a surrounding cell allows for communication with a lower transmit power
level. This typically indicates that the mobile station is located on the cell border area.
Inter-cell handover between cells using different frequency bands is allowed for a multiband mobile station.
An intra-cell handover from one channel/timeslot in the serving cell, to another channel/timeslot in the same cell, usually occurs if the handover measurements indicate a
low RXQUAL value but a high RXLEV value in the serving cell. This implies a degradation of quality caused by interference, even though the mobile station is located within
the serving cell. The intra-cell handover provides a channel with a lower level of interference, which can be a different timeslot on the same carrier or a timeslot on a new carrier.
If an inter-cell handover is indicated, the BTSplus generates a list of target cells by comparing the receive levels of the current cell and adjacent cells and by evaluating the
power budget criteria. This list is used for the final handover decision to be made in the
BSC (for an intra-BSS handover) or in the MSC (for an intra-MSC or inter-MSC han-

DN0933257

Id:0900d8058068be5c
Confidential

39

Handover and power control

BSS21469: BS2xx@Flexi BSC product family

dover). Intra-MSC and inter-MSC handovers are also called external handovers.
Internal intra-BSS handovers are performed by the BSC without the need for initiation
by the MSC. The MSC is only informed after successful execution. The same applies to
intra-cell handovers.
Types of handover
Table 1 shows the types of handover possible. The communication between the
mobile station and the BTSplus is handled via the FACCH within the TCH, for all these
handover types except for the forced handover, which is handled via the SDCCH.
Handover type

Handover category

extended cell handover

intra-cell

concentric cell handover

intra-cell

quality handover

inter-cell or intra-cell

RXLEV handover

inter-cell

fast uplink handover

inter-cell

distance handover

inter-cell

power budget handover

inter-cell

speed-sensitive power budget handover

inter-cell

traffic handover

inter-cell

forced handover

inter-cell

compression/decompression handover

intra-cell

Table 1

Types of handover

The first 6 handovers are imperative handovers, meaning that they must be performed
if the related handover conditions (based on RXLEV and RXQUAL measurements) are
fulfilled. In case of one of the other handover types, indication that a handover is advantageous does not necessarily lead to a handover actually taking place.
Forced handover
A forced handover is triggered in the following cases:
directed retry, or handover from an SDCCH in one cell to a TCH in another cell
during call setup
pre-emption
OAM-triggered handover
PS territory upgrade
In particular, a forced handover is not determined by the evaluation of radio network
criteria in the BTSplus. It is initiated by the Flexi BSC, which sends the FORCED
HANDOVER REQUEST message to the handover algorithm on the BTSplus. The
BTSplus processes this handover type as if an inter-cell handover condition had been
detected.
If the FORCED HANDOVER REQUEST message is received before the neighbor cell
measurements are available from the mobile station, the handover indication is stored
internally until two neighbor cell measurements can be evaluated by the mobile station,

40

Id:0900d8058068be5c
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Handover and power control

or more than seven measurement reports have been received from the mobile station
since call establishment.
Traffic handover
A traffic handover moves a call from a cell with a high number of busy channels to an
adjacent cell with a lot of free radio channels. Such handovers allow for the setting up
of new connections in order to maximize the number of users.

High Traffic Cell

Low Traffic Cell

Handover from BTS A to BTS B

BTS B

BTS A

BSC

Figure 12

Traffic handover

A traffic handover can only be performed between cells belonging to the same BSC, as
the serving BSC cannot control the channel occupance of an adjacent cell belonging to
another BSC. It also has the lowest priority amongst all the causes for a handover.
Concentric cell handover
Intra-cell handovers are possible between the inner and complete areas of a concentric
cell. When administrating the BTSplus by the Flexi BSC product family, the inner and
complete areas of concentric cells are represented by super-reuse and regular frequencies respectively. Refer to Concentric cells for more information.
Extended cell handover
An extended cell handover is the handover between one of the areas of an extended
cell and another. Refer to Extended cells for more information.
Compression/decompression handover
Compression handover is the intra-cell handover from a full rate traffic channel to a half
rate traffic channel. Correspondingly, decompression handover is the intra-cell
handover from a half rate traffic channel to a full rate traffic channel.
Compression handover is used to increase cell capacity when radio conditions are
good. Decompression handover can be used to improve the quality of transmitted
speech data, thus avoiding call drops due to low transmission quality, and also allows
higher transmission rates.

DN0933257

Id:0900d8058068be5c
Confidential

41

Handover and power control

BSS21469: BS2xx@Flexi BSC product family

When administering the BTSplus with the Flexi BSC product family, compression/decompression handover is only available for AMR calls.
In case wideband AMR is applied, compression/decompression handovers between
wideband AMR calls on full rate traffic channels and narrowband AMR calls on half rate
traffic channels are also possible.
Compression/decompression handovers for AMR calls can also be done if the link adaptation phase is completely exhausted. Generally, if wideband AMR is used for the
encoding of speech data for a TCH, operation with wideband AMR codecs is held until
the TCH is released. In a few cases, transitions between wideband AMR on full rate
TCHs and narrowband AMR on half rate TCHs may be useful, for example for traffic load
reasons, so these transitions are supported and can be configured.
Power budget handover
A power budget or better cell handover is a non-imperative handover type performed
to change to a cell with a better power budget. In general, the power budget is determined by taking the ratio of maximum uplink transmit power possible (or allowed) to
downlink receive strength, and converting this to dB. A better cell has a lower power
budget, which allows for minimizing transmitter power level and interference.
Speed-sensitive power budget handover
A speed-sensitive power budget handover is a special kind of power budget handover
that avoids multiple handovers when a mobile station quickly moves between a macrocell and an embedded microcell. In a mixed-cell environment with large, small and
micro-sized cells, fast moving mobile stations allocated in microcells would cause too
many handovers. In addition, the residence time in a microcell would be too short for
handover to be successful. Therefore, the speed of the mobile station is estimated and
used to influence the handover process, such that the probability of a smaller cell being
chosen as a potential target cell is lower when the mobile station is moving at high
speed.

7.1.2

Mapping of handover causes


The reasons for which the BTSplus can start an intra-cell or inter-cell handover are
mapped to existing handover causes in the Flexi BSC. These are listed in Table 2 and
Table 3.
BTSplus cause
uplink quality

ul_interf_c

downlink quality

dl_interf_c

inner area to complete area

bad_ci_ratio_c

complete area to inner area

ok_ci_ratio_c

distance near to far

distance_c

distance far to near

low_distance_c

AMR to HR handover

ho_to_amr_hr_c

AMR to FR handover

ho_to_amr_fr_c

Table 2

42

Flexi BSC cause

Intra-cell handover

Id:0900d8058068be5c
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Handover and power control

BTSplus cause
uplink quality

ul_rxqual_c

downlink quality

dl_rxqual_c

uplink strength

ul_rxlev_c

downlink strength

dl_rxlev_c

distance

distance_c

better cell

pbgt_ho_c

forced

forced_ho_c

fast uplink handover

rap_fld_drop_c

traffic handover

bsc_trho_c

UMTS sufficient

isho_c

Table 3

7.1.3

Flexi BSC cause

Inter-cell handover

TCH and SDCCH handovers


Usually a handover situation occurs while a traffic channel between a mobile station and
the BTSplus is established. Consequently, the handover conditions are evaluated on the
FACCH within the TCHs.
In case no TCH is established, but an SDCCH is allocated for the communication
between the mobile station and the BTSplus, an SDCCH handover is not necessary if
the SDCCH is only allocated for a short time, as is normally the case. However,
handover from one SDCCH to another is provided for in case of longer SDCCH connections. Moreover, an SDCCH handover from one cell to another could be advantageous
during the call establishment procedure, as a means for successfully establishing a call
when no TCH resource is available on the current serving cell.
The evaluation of handover conditions for SDCCH handovers refer to the radio conditions (signal strength, quality and power budget) affecting the related handover types.
Extended cell handovers are not possible for SDCCHs, since SDCCHs are always
assigned to the double timeslot configuration. Concentric cell handovers are also impossible for SDCCHs, since SDCCHs are always assigned to the complete area.
SDCCH to SDCCH handovers are usually inter-cell handovers. A quality intra-cell
handover between SDCCHs is possible if the new SDCCH is allocated on a different
timeslot or a different TRX.
A handover from an SDCCH in one cell to a TCH in a neighboring cell is provided by
means of the forced handover, which is triggered by the Directed retry feature.

7.1.4

Congestion control for dual area cell


The Flexi BSC supports congestion control for dual area cells, as well as the activation
of AMR compression or decompression according to traffic load of the cell.
The BTSplus handover algorithm for dual area cells needs to know the congestion
status of the complementary area in order to avoid floods of unserved handover condi-

DN0933257

Id:0900d8058068be5c
Confidential

43

Handover and power control

BSS21469: BS2xx@Flexi BSC product family

tion indications. The Flexi BSC therefore sends the following information to the BTSplus
via Abis attributes:
Whether or not the cell or area is congested highly loaded, so that the BTSplus can
avoid unnecessary handover indications
Indication to start AMR compression, when the cell is highly loaded
Indication that AMR decompression may be started, when the cell is not highly
loaded

7.2

Power control
Power control is the mechanism with which the MS (for the uplink) or TRX (for the downlink) transmit power is increased or reduced during an ongoing radio link between the
MS and the BTS, in order to react to the current radio conditions. Power control is
employed in order to minimize the transmit power to a level that just about ensures
adequate speech or data quality over the radio path. By doing so, it reduces the cochannel interference caused by other cells re-using the same frequencies, as well as the
adjacent channel interference caused by other call connections in the same cell, and the
average power consumption of the transmitter.
When operating the BTSplus with the Flexi BSC product family, the power control algorithm is also executed on the BTSplus. For this case, therefore, the power control algorithm running on the Flexi BSC needs to be disabled for calls made via the BTSplus. The
Flexi BSC sends the parameters related to the POC managed object to the BTSplus via
the BTS OAM mediation software.
The algorithm is enabled on the Flexi BSC for calls involving other BSS base station
types (e.g. the Flexi EDGE BTS). The BTS site type is identified by the BCF managed
object.
When the power control mechanism is unable to guarantee the minimum call quality, the
call must be handed over to a different cell.

7.2.1

Derived handover power management


The Flexi BSC supports the optional Derived handover power feature in the BTSplus.
This feature allows the target BTS in a handover operation to calculate the optimal uplink
and downlink transmit power for the situation just after the handover. This optimal power
calculation has, as a target value, the received downlink signal strength value in the
serving BTS, which it sends to the target BTS via the BSC whenever handover conditions are detected.
The optimal transmit power values are sent to the BSC as part of the CHANNEL ACTIVATION ACKNOWLEDGE message, inside the MS power IE. If the required MS
power value matches the MS power class, this value is sent to the MS as part of the
HANDOVER COMMAND message. If the mobile station is unable to send with the calculated transmission power, this value has to be reduced accordingly. The mobile
station power class is indicated in the MS RF POWER CAP IND message sent by the
Flexi BSC to the BTSplus.
This feature helps to reduce the interference level in a cell. It governs power control for
the first few seconds after the MS call is switched to the target cell, after which the
standard power control algorithm takes over.

44

Id:0900d8058068be5c
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Supported functionality

8 Supported functionality
This section describes just some aspects of the supported GSM/EDGE functionality that
are specific to using the BTSplus with the Flexi BSC product family. Refer to the
standard documentation of the Nokia Siemens Networks GSM/EDGE BSS product line
for a comprehensive description of GSM/EDGE functionality using all the BTS types in
this product line.

8.1

Features in BTSplus with the Flexi BSC


RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

RG(BSS)
feature name

SF010001

Star Connection
(BSC/MSC)

SF010016

Rx Antenna Diversity

BSS01073

Receiver Diversity in BTS Configuration


Package

SF010027

Star Connection
(BTS/BSC)

BSS00128

Abis Trunk
Transmission
Allocation

SF010028

Loop Connection
(BTS/BSC)

RG601668

BS2xx Loop Protection with Flexi


BSC

SF010032,
SF010232

Multidrop Connection, Integrated


Drop/Insert 16
Kbit/s Channels

BSS00128

Abis Trunk
Transmission
Allocation

SF010036

Speed Sensitive
Handover

SF010039

BTS Emergency
Operation for
Extended Battery
Backup Time

BSS20151

Adjustable Intelligent Shutdown ,


FlexiEDGE BTS
/ UltraSite/MetroSIte BTS

SF010043

A - Interface:
Overload Control

not applicable

BSC HW Basic
SW functionality

SF010045

BSC Overload
Regulation

not applicable

BSC HW Basic
SW functionality

SF010046

CCS#7 Overload
Handling

not applicable

BSC HW Basic
SW functionality

Table 4

DN0933257

Corresponding
RG(BSS)
feature
number

BSC HW Basic
SW functionality

Features in BTSplus with Flexi BSC)

Id:0900d805808a406d
Confidential

45

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

RG(BSS)
feature name

SF010047

Radio Interface
Overload Regulation

BSC HW Basic
SW functionality

SF010049

A - Interface: 2
MBit/s, Coax.
Cable/Sym. Pair

not applicable

BSC HW Basic
SW functionality

SF010054

Abis Interface:
2MBit/s. Coax.
Cable/Sym. Pair

BSS00128

Abis Trunk
Transmission
Allocation

SF010063

Abis-Interface Sub- y
multiplexing:
4TCH/F into 1x64
kBit/s

BSS00128

Abis Trunk
Transmission
Allocation

SF010065

Flexible Lapd
Links: 1*16, 1*64
kBit/s

BSS01605

Abis Trunk Signalling

SF010075

Asub Interface:
2MBit/s, Coax.
Cable/Sym. Pair

not applicable

BSC HW Basic
SW functionality

SF010080

Asub Interface:
Submultiplexing of
4 TCH/F into 1*64
kBit/s

not applicable

BSC HW Basic
SW functionality

SF010083

Synchronization
Aspects

BSC HW Basic
SW functionality

SF010085

Interface to Cell
Broadcast Center

SF010086

Local Maintenance
Terminal Interface,
General

BSC HW Basic
SW functionality

SF010087

BSC-OMC Interface (X.25):


General

BSC HW Basic
SW functionality

SF010090

BSC-OMC Interface (X.25): via


PSPDN

Table 4

46

Corresponding
RG(BSS)
feature
number

BSS07002

Cell Broadcast
(CB) IF in BSC to
CB Centre

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

RG(BSS)
feature name

SF010091

BSC-OMC Interface (X.25): via


NUC

BSC HW Basic
SW functionality

SF010096

Basic Functionality: y
MTP, SCCP,
BSSAP

BSC HW Basic
SW functionality

SF010101

Priority Access
Classes
(Enhanced Set)

BSS03910

Queuing and
Priority

SF010102

VAD and DTX (Full


Rate)

BSS11610

Discontinuous
Transmission DL
and UL (DTX)
included to
Spectral & Efficiency Package

SF010107

VAD and DTX (Half


Rate)

BSS11610

Discontinuous
Transmission DL
and UL (DTX)
included to
Spectral & Efficiency Package

SF010109

Speech (Upgrade
from Full Rate to
Full and Half Rate)

BSS05010

GSM Half Rate

SF010116

Simultaneous Use
of Basic Services
with SMS

BSS01003

SMS Point-toPoint in GSM


Voice & Extension Package

SF010117

Dataservices: Incall Modification

SF010121

Discontinuous
y
Reception (Paging:
Sleep Mode)

SF010122

On Line Administration of Paging


Groups in Service

Table 4

DN0933257

Corresponding
RG(BSS)
feature
number

BSS01005

BSC HW Basic
SW functionality
BSS02213

Discontinuos
Reception (DTX)
in Common
Control Channel
Package
Manual operation, BSC HW
Basic SW functionality

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

47

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

Corresponding
RG(BSS)
feature
number

RG(BSS)
feature name

SF010128

BCCH Redundancy in BTS:


Reconfiguration
Mode (Manual)

not applicable

SF010129

Data Traffic Channels: TCH/F9.

BSS01019

Circuit Switched
Data up to 9.6
kbps

SF010130

Data Traffic Channels: TCH/F4.8

BSS01017

Circuit Switched
Data up to 9.6
kbps

SF010131

Data Traffic Channels: TCH/F2.4

BSS01015

Circuit Switched
Data up to 9.6
kbps

SF010134

Control Channels

BSS21538

Extended CCCH

SF010135

Ciphering with
Algorithm A5: A5/1
(MOU), Incl. A5/0
(No Ciphering)

BSS01029

BSC Ciphering
Algorithm A5/1 or
BSC Ciphering
Algorithm A5/0

BSC HW Basic
SW functionality

BSS02501
BSS01082
BSS2509
BSS03011

SF010136

Ciphering with
n
Algorithm A5: A5/2,
Incl. A5/0 (No
Ciphering)

SF010137

Ciphering: Mandatory Functionality

BSC Ciphering
Algorithm A5/2

BSS01029
BSS02501
BSS01082

BSC Ciphering
Algorithm A5/1 or
BSC Ciphering
Algorithm A5/0

BSS2509
BSS03011
SF010140

Table 4

48

Frequency
Hopping (Baseband)

BSS02013

Frequency
Hopping (FH)
(BB) included to
Spectral & Efficiency Package

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

Corresponding
RG(BSS)
feature
number

RG(BSS)
feature name

SF010141

Frequency
Hopping (Synthesized)

BSS03050

Frequency
Hopping (FH)
(Synth) included
to Spectral & Efficiency Package

SF010144

Intracell-HO

BSS02801

GSM Voice &


Extension
Package

BSS5070
BSS07075
BSS06114
SF010145

Intra-BSC-HO
(Inter-Cell)

BSS02801
BSS5070
BSS07075

GSM Voice &


Extension
Package

BSS06114
SF010146

Intra-MSC-HO
(Inter-BSC)

BSS02801
BSS5070
BSS07075

GSM Voice &


Extension
Package

BSS06114
SF010147

Inter- MSC-HO

BSS02801
BSS5070
BSS07075

GSM Voice &


Extension
Package

BSS06114
SF010150

HO Decision due to
Basic Parameters

BSS02801
BSS5070
BSS07075

GSM Voice &


Extension
Package

BSS06114
SF010153

SF010161

HO Decision due to
O&M Criteria
(Maintenance
Caused HO)

Data Services (Full


Rate)

BSS00191
BSS07709

BSS01436
BSS01019,
BSS01013,

Forced Handover
for O&M Reason
included to
Spectral & Efficiency Package
Circuit Switched
Data up to 9.6
kbps

BSS01011
Table 4

DN0933257

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

49

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

Corresponding
RG(BSS)
feature
number

feature name

SF010162

Supplementary
services

SF010165

12 Emergency Call y

BSS30330

GSM Voice &


Extension
Package

SF010166

21 Short Message
MT/PP, excl.
GMSC/IWMSC

BSS01003,

GSM Voice &


Extension
Package

22 Short Message
MO/PP, excl.
GMSC/IWMSC

SF010172

Priority Access
Classes (Basic
Set)

BSC HW Basic
SW functionality

SF010174

Radio Interface:
Automatic Barring
of Access Classes

BSC HW Basic
SW functionality

SF010192

Frequency Band
Characteristics,
DCS

BSS05050

Dual band GSM


900/1800, ETSI

SF010194

TCH RF Power
Control

BSS09021

Spectral & Efficiency Package /


GSM Voice &
Extension
Package

SF010167

RG(BSS)

BSC HW Basic
SW functionality

BSS01005
BSS01003,
BSS01005

BSS02703
BSS02707
BSS02715

SF010195

TCH Handover

BSS02801
BSS5070
BSS07075
BSS06114

GSM Voice &


Extension
Package

Spectral & Efficiency Package /


GSM Voice &
Extension
Package

BSS00251
BSS05230
SF010208

Reduced Number
of Antennas:
Duplexers within
the BTS Rack,
GSM

BSS40040
BSS40050

BSC HW Basic
SW functionality

BSS09030
BSS05820
BSS07399
BSS09007

Table 4

50

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010222

Multiband Operation

Corresponding
RG(BSS)
feature
number
BSS05050
BSS06144

RG(BSS)
feature name

Dual band GSM


900/1800, ETSI

BSS07210
BSS07015
SF010232

BTS Multidrop-Star
Cross Connect

BSC HW Basic
SW functionality

SF010234

Infrastructure
Sharing: GSM and
DCS BTSEs Connected to the Same
BSC

SF010239

BCCH Redundancy in BTS:


Reconfiguration
Mode (Automatic)

BSC HW Basic
SW functionality

SF010242

Improved Equaliser y
for Increase of
Speed Limit

BSC HW Basic
SW functionality

SF010243

Tower Mounted
not applicable
Receiver Preamplifier as a Configuration Option, GSM

SF010244

Tower Mounted
not applicable
Receiver Preamplifier as a Configuration Option, DCS

SF010245

Direct Assignment
on TCH

BSS05290

FACCH Call
Setup due to
SDCCH Congestion, included to
Spectral & Efficiency Package

SF010248

Reduced Number
of Antennas:
Duplexers within
the BTS Rack,
DCS

BSS40040

BSC HW Basic
SW functionality

BSS05050

BSS40050

Dual band GSM


900/1800, ETSI

BSS09030
BSS05820
BSS07399
BSS09007

Table 4

DN0933257

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

51

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

Corresponding
RG(BSS)
feature
number

RG(BSS)
feature name

SF010250

TRAU Volume
Control

BSS05022

Adaptive Gain
Control/Downlink in GSM Voice
& Extension
Package

SF010255,
SF010406

Directed Retry
(SDCCH to TCH
Handover)

BSS02307

Directed Retry
(DR)

BSS07071
BSS00231
BSS06114

SF010260

Frequency
Hopping (Baseband) Enhancement: Autonomous
Frequency Redefinition

SF010262

Ciphering with
partially supAlgorithm A5: A5/1, ported
A5/2, Incl. A5/0:
Enhancements

BSS02013

Frequency
Hopping (FH)
(BB) included to
Spectral & Efficiency Package

BSS01029

BSC Ciphering
Algorithm A5/1 or
BSC Ciphering
Algorithm A5/0

BSS02501
BSS01082
BSS2509
BSS03011

SF010265

BSC Overload
Regulation
(Enhancements)

BSC HW Basic
SW functionality

SF010272

Radio Interface
Overload Regulation (Enhancements 1)

BSC HW Basic
SW functionality

SF010279

Abis Interface:
Survival of Short
Layer 2 Breakdown

BSC HW Basic
SW functionality

SF010280

Enhanced Availnot applicable


ability: BSC
Redundancy
(MPPC Hot Redundancy Preliminary)

Table 4

52

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010281

Enhanced Availnot applicable


ability: BSC
Redundancy
(MPCC Hot Redundancy)

SF010282

Enhanced Availability: TRAU


Redundancy
(MSCI, BSCI Cold
Redundancy)

not applicable

SF010283

Enhanced Availability: TRAU


Redundancy
(MSCI, BSCI Hot
Redundancy)

not applicable

SF010284

Loop Connection
(BTS/BSC) with
Active Routing
from Two Sides

SF010285

Expansion of BTSs
with Additional
TRXs without
Service Impact

partially supported

SF010286

Activation of
Exchanged Boards
without Service
Impact

Enhanced Full
Rate

SF010328

4 SDCCH/8 on
BCCH Carrier

SF010330

Hierarchical Cell
Structure

SF010327

Corresponding
RG(BSS)
feature
number

RG(BSS)
feature name

BSC HW Basic
SW functionality

BSS06071
BSS05360

BSS06071
BSS05360

Enhanced Full
Rate (EFR), ETSI

Enhanced Full
Rate (EFR), ETSI
BSC HW Basic
SW functionality

BSS04016
BSS05310
BSS07066

Child Cell Bar,


Intelligent
Underlay Overlay
(IUO)

BSS07210
Table 4

DN0933257

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

53

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010331

Concentric Cells

Corresponding
RG(BSS)
feature
number
BSS04016
BSS05310
BSS07066

RG(BSS)
feature name

Child Cell Bar,


Intelligent
Underlay Overlay
(IUO)

BSS07210
SF010332,
SF010963

Extended cell (distance)

partially supported

SF010333

Call release for


excessive distance

BSC.260

Included to HO
features and optimisation
packages

SF010351

SF HighSpeedCircuiSwitchedData

BSS07003

High Speed
Circuit Switched
Data (HSCSD)

SF010352

Pooling for TRAU


circuit allocation on
A-Interface

BSC HW Basic
SW functionality

SF010401

BTS Rack Extension: 24 TRX/Site,


12 TRX/Cell

partially supported

BSC HW Basic
SW functionality

SF010402

BSC Capacity
Enhancements:
250 TRX, 150
Cells, 2000 Erlang

not applicable

SF010403

ASCI: Voice Group


Call Service
(VGCS)

SF010404

ASCI: Voice Broad- n


cast Service (VBS)

SF010404,
SF010424

ASCI: Voice Broad- n


cast Service (VBS)
(VGCS)

SF010405

14,4 Kbit/s Data


Service on a single
timeslot

Table 4

54

partially supported

BSC HW Basic
SW functionality

BSS07037

14.4 kbps Circuit


Switched Data

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010406

Queueing, Preemption and


Directed retry for
TCH

Corresponding
RG(BSS)
feature
number
BSS02301
BSS02302
BSS02337
BSS03910

RG(BSS)
feature name

Queuing and
Priority - features
in Spectral &
Efficiency
Package

BSS20869
SF010407

SDCCH to SDCCH
Handover

Handover
Strategies

Included to HO
features and optimisation
packages

SF010408

Tandem Free
Operation of
Speech Codecs
(TFO)

BSS09004

Tandem Free
Operation (TFO)

SF010410

NUC (Nailed Up
Connection) within
TRAU

BSC HW Basic
SW functionality

SF010411

NUC (Nailed Up
Connection) within
BSC

BSC HW Basic
SW functionality

SF010412

BTS connected
with 2 PCM Lines

BSC HW Basic
SW functionality

SF010413,
SF010414,
SF010415,
SF010489

Support of Satellite
Link on A-Interface

SF010414

Support of Satellite y
Link on Asub-Interface

SF010415

SF010416

Table 4

DN0933257

BSS04040,
BSS04041,

Satellite
Abis/Ater/A

BSS05850

Support of Satellite
Link on Abis-Interface

SMSCB Enhance- y
ment: 2200
Messages per BSC

BSS04040,
BSS04041,

Satellite
Abis/Ater/A

BSS05850
BSS04040,
BSS04041,

Satellite
Abis/Ater/A

BSS05850
BSS01006
BSS06084

Common Control
Channel
Package

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

55

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

Corresponding
RG(BSS)
feature
number

RG(BSS)
feature name

SF010417

Dualband
900/1900MHz:
BSC Infrast.
Sharing, HO,
Roam

BSS30040

Dual band GSM


800/1900, ANSI

SF010420

General Paket
Radio Services
(GPRS)

BSS09006

GPRS and
related features

BSS20929
BSS30240
BSS11088
BSS30245
BSS30165
BSS30170
BSS30175
BSS30065
BSS30180
BSS30185
BSS30190
BSS30070
BSS10074
BSS30205
BSS30195
BSS30210
BSS30215
BSS30220

SF010421

High Speed Circuit


Switched Data
Enhancement

partially supported

BSS07003

High Speed
Circuit Switched
Data (HSCSD)

SF010423

Adaptive Multi Rate partially supSpeech Codec


ported
(AMR)

BSS10004

AMR HR, AMR


FR

BSS30055
BSS30060
BSS20249
BSS21120
BSS21483

Table 4

56

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010423

RG(BSS)
feature name

Adaptive Multirate
Speech Codec FR

partially supported

BSS30055

SF010423

Adaptive Multirate
Speech Codec HR

partially supported

BSS30060

AMR Capacity
(HR)

SF010424

ASCI Step 2

SF010425

Smooth Channel
Modification

BSS07036

Dynamic SDCCH
Allocation Increased
Dynamic SDCCH
capacity

SET Command for


Changes of
Channel Combination

SF010427

24 TRXs per Cell


and Handling of
GSM900/1800
Cells

SF010428,
SF010961

Common BCCH for


GSM900/1800
Dual Band Operation

BSS10016

Tri-Band
GSM/EDGE
Common BCCH,
ETSI

SF010429

Cell Load Depeny


dent Activation of
Half Rate Channels
in One Cell

BSS30025

Traffic Channel
Allocation Traffic Channel
Allocation, Load
of BTS

SF010426

BSS10004

BSS21113

BSS07036
BSS21113

SF010430

Enhanced Pairing
for Half Rate
Channels

SF010432

Service Dependent y
Channel Allocation
Strategy Step 1

Table 4

DN0933257

Corresponding
RG(BSS)
feature
number

BSS30030

AMR Quality &


Coverage (FR)

Dynamic SDCCH
Allocation Increased
Dynamic SDCCH
capacity

BSS11136

Enhanced TRX
Priorisation in
TCH Allocation
included in
Spectral & Efficiency Package

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

57

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

Corresponding
RG(BSS)
feature
number

feature name

SF010435

Cell Allocation
Number Increase

BSS03050

Frequency
Hopping (FH)
(Synth) included
to Spectral & Efficiency Package

SF010436

Handover Decision
Due to BSS
ReSource ManAgement Criteria

BSS08123

Advanced Multilayer Handling


(AMH)GSM
Voice & Extension Package

Fast Uplink
Handover

Introduction of
"Level Handover
Margin" Parameter

SF010437

SF010438

BSS00251
BSS05230

BSS04013
BSS07031

BSS02801
BSS5070
BSS07075
BSS06114

Chained Cells in
Rapid Field Drop
in BSS Microcellular Features
Functionality
included into
Spectral & Efficiency Package /
Queuing and
Priority

SF010439

Single Command
for non-BCCH and
BSIC`s

not applicable

SF010440

Load Sharing and


LAPD Fault
Recovery

BSC HW Basic
SW functionality

SF010441

BTSplus Core
Redundancy

BSC HW Basic
SW functionality

SF010442

Extended Number
of TRXs in BSC
Area

not applicable

SF010443

GPRS: Automatic
y
"Horizontal" Allocation

BSS30170

Functionality
included into
GPRS

SF010444

Packet Transfer on
Non-BCCH TRXs
w/o DL PC

BSS20929

Functionality
included into
GPRS

Table 4

58

RG(BSS)

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010445

EDGE: Speeding
up into a Packet
Data World

Corresponding
RG(BSS)
feature
number
BSS10091
BSS30250
BSS30255

RG(BSS)
feature name

EDGE - One
Phase Access for
EDGE

BSS11156
BSS30165
BSS30170
BSS30180
BSS30190
BSS10074
BSS30205
SF010445,
SF010446

EDGE: Speeding
up into a Packet
Data World

BSS10091
BSS30250
BSS30255

EDGE - One
Phase Access for
EDGE

BSS11156
BSS30165
BSS30170
BSS30180
BSS30190
BSS10074
BSS30205
SF010446

SF010447

SF010448
Table 4

DN0933257

Multiplexing of
GPRS and EGPRS
Users on the Same
Timeslot

Dynamic Abis
Resource Allocation

BSS20929,
BSS10091

MS/Gb flow control y

BSS10045,
BSS09006,
BSS10091
BSS11110

Included into
GPRS / EDGE
feature +
Spectral & Efficiency Package
+PS Data
Package
Included into
GPRS / EDGE
feature
Gb Over IP

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

59

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010449

Link Adaptation

Corresponding
RG(BSS)
feature
number
BSS30245
BSS30260

SF010451

Improved Power
Control

SF010452

Service Dependent n
Power Control and
Handover Thresholds

SF010453

Extension of
External Alarms

SF010454

Support of CS3
and CS4

SF010455

feature name

Included to
GRPS / EDGE
features +
Spectral & Efficiency Package
+ PS Data
Package

BSS09021

Variable DL
Power Control
included to
Spectral & Efficiency Package

partially supported

BSS11088

GPRS Coding
Schemes CS3
and CS4 (UL,
DL)

GPRS and EGPRS


Quality of Service

BSS10084

Priority Class
Based Quality of
Service in PS
Data Package

SF010456

Network Controlled
Cell Reselection

BSS11112

Network Controlled Cell Reselection (NCCR)

SF010459

Transmission
Diversity

BSS11134

Antenna Hopping

SF010460

ASCI: Use of the


Uplink in the Group
Call Channel

SF010461

Handover from
GSM to UMTS

partially supported

BSS10101

Inter-System
Handover GSM-WCDMA,
Controlled
WCDMA Access

BSS30135
BSS30160
BSS11107

Table 4

60

RG(BSS)

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010465

SF010467

Adaptive MultiRate Speech


Codec HR2

Handover from
UMTS to GSM for
Circuit Switched
Services

Corresponding
RG(BSS)
feature
number
BSS10004
BSS30055

RG(BSS)
feature name

AMR Quality and


Coverage (FR)

BSS30060
BSS10101
BSS30140
BSS30160
BSS11107

Inter-System
Handover GSM-WCDMA,
Controlled
WCDMA Access

SF010468

Transmission
Diversity Time
Delay

BSS10104

Smart Radio
Concept (SRC)

SF010469

Performance Measurement based on


Enhanced Measurement Report

BSS11086

Enhanced Measurement Report


(EMR)

SF010472

IP based O-Link
Interface

BSS30340

BSC Q3 interface
for NetAct

SF010473

Flexible Carrier
Unit - Four Path
Receive Diversity

BSS10104

Smart Radio
Concept (SRC)

SF010478

Common Codec
Pool for TRAU

SF010479

Performance Measurements for


GPRS

SF010482

Counters for Clear


Requests and
Clear Commands

SF010483

Intersystem Cell
Reselection
between GSM /
GPRS and UMTS

BSC HW Basic
SW functionality
BSS20929
BSS21026

BSS10101
BSS30155
BSS30145
BSS30150

Included to
GRPS / EDGE
features +
Spectral & Efficiency Package
+ PS Data
Package

Inter-System
Handover GSM-WCDMA,
Controlled
WCDMA Access

BSS11107
Table 4

DN0933257

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

61

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010487

Processing
Booster for HC
BSC step 1

not applicable

SF010488

Processing
Booster for HC
BSC step 2

not applicable

SF010489

(E-)GPRS over
Abis over Satellite

Corresponding
RG(BSS)
feature
number

BSS04040,
BSS04041,

RG(BSS)
feature name

Satellite
Abis/Ater/A

BSS05850
SF010493

Cell Name Broadcast

BSS01006
BSS06084

Cell Broadcast
(CB)

BSS02129
SF010501

Uplink Incremental
Redundancy

BSS10091

EDGE Incremental Redundancy


(UL, DL)

SF010503

Flexible Gb

BSS20086

Multipoint GbInterface

SF010504

Derived Handover
Power

SF010505

Ciphering A5/3 for


GSM

BSS20093 /
L50026-BB75

A5/3 ciphering /
Release SW
RG10 BTS+ A5/3
emedia

SF010506

Allocation Retention Priority

partially supported

SF010507

Central Network
Sevice Layer

SF010508

External Network
Assisted Cell
Change (NACC)

BSS20083

Inter-BSC NACC

SF010509

Support of MS
classes 30-33

BSS20084

High Multislot
Classes

SF010510,
SF010511

U-TDOA AMR
Enhancements for
Lb-Interface

BSS30125

in U-TDOA LCS
features

Table 4

62

BSS30130

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010511

RG(BSS)
feature name

U-TDOA Lb-Interface Enhancements

SF010512

GB Streaming
Enhancements

SF010513

ASCI: Group Call


Broadcast Point in
BSS

SF010515

BSC Interface
Enhancements for
US LCS Requirements

SF010516

Delayed Power
Control for E911
Emergency Calls

BSS21041

Maximum MS TX
Power During
E911 location

SF010517

QoS Improvey
ments: Multiplexing
of RT and/or EDA
TBFs

BSS20089

Extended
Dynamic Allocation

SF010518

RAN Information
y
Management (RIM)

BSS20083

Inter-BSC NACC

SF010520

Improved Uplink
Receiver Sensitivity by Averaging
over Multiple
Bursts

SF010521

Improved UIC
(Uplink Interference Cancellation)

SF010522

SW Support of the
eBSC

not applicable

SF010523

ASCI: Ciphering for


Voice Group Call
Services

Table 4

DN0933257

Corresponding
RG(BSS)
feature
number
BSS30125
BSS30130

BSS30125
BSS30130

in U-TDOA LCS
features

in U-TDOA LCS
features

BSC HW Basic
SW functionality

BSS40090,
BSS40100

Maximum Ratio
Combining
(MRC), Interference Rejection
Combining (IRC)

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

63

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010524

Fine Tuning for


Quality Thresholds

partially supported

Corresponding
RG(BSS)
feature
number
BSS03701
BSS21120
BSS21483

feature name

Included to HO
features and optimisation
packages

SF010525

R-FACCH and
TOP on
FACCH/SACCH
for reduced call
drop rate

BSS20872

Robust AMR
Signalling
(FACCH /
SACCH)

SF010526

Reduced Muting
Gap during IntraBSC Handover

BSS20588

TRAU Bicasting
in AMR FR/HR
Handover

SF010527

Simultaneous
Power Activation of
many TRX in Test
Mode

SF010528

SW Support of the
eTRAU

not applicable

SF010529

Multiple OPC

BSS30020

High Capacity
Signalling Links
on A interface

SF010530

SS7 High Speed


Link

BSS30020

High Capacity
Signalling Links
on A interface

SF010531

Virtual (Multiple
TRAUs in one)
eTRAU

not applicable

SF010532

UPM Capacity
Booster

not applicable

SF010533

A5/1 Ciphering
Security Enhancements - SDCCH
HO

BSS21389

A5/1 Ciphering
Security
Enhancements SDCCH HO

SF010550

Different Level
Thresholds for
RACH Access and
HO Access

BSS02801

Functionality
included into
Spectral & Efficiency Package /
Queuing and
Priority

BSS5070
BSS07075
BSS06114

Table 4

64

RG(BSS)

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010551

Link Adaptation
partially supEnhancements for ported
GRPS and EGPRS

SF010553

ASCI: Reactivation
of VGCS/VBS
Channels After
Service Unavailability

SF010556

Flexible A-Interface y

Corresponding
RG(BSS)
feature
number
BSS10091
BSS20485
BSS20929

AMR Wideband
TCH/WFS

feature name

Link Adaptation
features (GPRS,
EDGE) +
Separate UL&DL
AMR Link
Adaption Thresholds

BSS20092
BSS21217

SF010557

RG(BSS)

partially supported

BSS20960
BSS21218

Multipoint Ainterface, Multipoint A Load Balancing


Wideband AMR features

BSS21118
SF010558

Repeated SACCH
and Modified
Scheduling

SF010559

Enhancement of
PCU Capacity

not applicable

SF010560

Internal Ethernet /
IP Interfaces for
BSS

BSS21443

SF010562

GERAN Evolution:
Dual Carrier in
Downlink

BSS21228

SF010563

Modified PCU Load n


Balancing

SF010564

External 1pps
Interface Support
for BTS

SF010565

IP Interface
support for LMT

Table 4

DN0933257

BSS20872

Robust AMR
Signalling
(FACCH /
SACCH)
BSC HW Basic
SW functionality

Downlink Dual
Carrier
BSC HW Basic
SW functionality

Release SW
RG10 LMT
emedia

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

65

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

RG(BSS)
feature name

SF010567

ASCI: Cell Resen


lection - Introduction of new SI10bis

SF010568

Advanced Packet
Resource Allocation

SF010570

ASCI: CS Data
Transmission
During Active
VGCS

SF010571

Multi-operator BSS y

BSS21213

Multi-operator
BSS (MOBSS)

SF010572

Support of Real
Time Road Traffic
Information

BSS21333

Real-Time Road
Traffic Information

SF010573

Management of
Standby TRX for
BTS

SF010600

Tandem Free
Operation for Narrowband AMR

BSS21118

Tandem Free
Operation (TFO)
for AMR

SF010601

Orthogonal Sub
Channel with SAIC
MS

BSS21309

Orthogonal Sub
Channel with
SAIC MS

SF010602

Prevention of Back
Handover

SF010603

Load Based
Handover

BSS10101

Load based
UTRAN
Handover
support for
BTSplus

SF010604

IMSI Based
Handover

BSS12158

IMSI Based HO

SF010605

GSM/EDGE - LTE
Interworking

BSS21353

LTE System
Information

SIGTRAN: Signaling over IP Interface

SF010606

Table 4

66

Corresponding
RG(BSS)
feature
number

BSS21355
BSS20852

SIGTRAN over A
Interface

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

RG(BSS)
feature name

SF010607

A over IP

BSC99321

A over IP

SF010608

IPSec on O-Link

BSS30340

OSI over TCP/IP

SF010609

BCCH TRX Energy y


Saving Mode:
Dummy Burst Management

BSS20958

Energy Saving
Mode for BCCH
TRX

SF010610

BCCH TRX Energy


Saving Mode:
Power Reduction

BSS20958

Energy Saving
Mode for BCCH
TRX

SF010611

Load Dependent
Activation/Deactivation of BTS
Carrier Units

BSS20984

2G TRX Automatic Power


Down

SF010612

Time Based Activa- y


tion/Deactivation of
BTS Carrier Units

BSS21261

SF010613

Conference Bridge
on eTRAU

SF010614

VQE Upgrade

not applicable

SF010615

Security Enhancements for eBSC


and eTRAU

not applicable

SF010616

PCM Synchronization for Ethernet


Based BTS

SF010618

Remote Access to
Network Element

SF010619

Software Support
for Integrated IP
Interface Card in
eBSC and eTRAU

SF010803

Board identification
via Serial EPROM
for BTSE Boards
(ESN)

SF010937

Lb Interface:
Location Services

Table 4

DN0933257

Corresponding
RG(BSS)
feature
number

BSS21157

Integrated IP
card for BSC3i
and TCSM3i

BSS11114

Lb interface in
BSC

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

67

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

SF010938

U-TDOA Positioning: Location


Services

Corresponding
RG(BSS)
feature
number
BSS30125
BSS30130

feature name

Functionality
included in LCS
U-TDOA features

SF010950

Quality of Service: n
Streaming
Services for
EGPRS and GPRS

SF010951

Extended Dynamic
Allocation

BSS20089

Extended
Dynamic Allocation (EDA)

SF010952

Network Assisted
Cell Change

BSS11506

Network Assisted
Cell Change
(NACC)

SF010953

Dual Transfer
Mode

BSS20088

"Dual Transfer
Mode - Dual
Transfer Mode
2G/3GPaging
Coordination"

BSS30100
BSS20738

SF010954

Intersystems
Network Controlled
Cell Reselection
from GSM GPRS
to UMTS due to
Sufficient UMTS
Coverage

BSS20394

Inter System
NCCR (ISNCCR)

SF010955

Uplink Interference
Cancellation

BSS40090

BSC HW Basic
SW functionality

SF010956

Network Synchronization

SF010957

Dynamic MAIO
Allocation and
Admission Control

SF010958

Integrated Acoustic y
Echo Control

SF010959

Table 4

68

RG(BSS)

Integrated
Advanced Noise
Reduction

BSS40100

BSS06142
BSS07068
BSS09069
BSS30090

Acoustic Echo
Cancellation
(AEC)
Noise Suppression (NS)

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

Supported functionality

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC
yes/no

Corresponding
RG(BSS)
feature
number

feature name

SF010960

Integrated Autoy
matic Level Control

BSS05022

Adaptive Gain
Control/Downlink in GSM Voice
& Extension
Package

SF010961

Common BCCH
y
Dual Band Cells Standard and Concentric Cell Structures

BSS10087

Dual band GSM


900/1800, ETSI Dual band GSM
800/1900, ANSI Dual Band GSM
800/1800, ETSI GSM/EDGE
Common BCCH,
ANSI

SF010962

Multi Service Layer


Support

SF010963

Extended Cells for


Circuit and Packet
Services

partially supported

BSS30040
BSS30050
BSS30045

BSS20882
BSS20094
BSS21277
BSS21270

SF010964

Extended Uplink
TBF

SF010965

High Speed Gb

SF010966

none

Table 4

DN0933257

RG(BSS)

BSS11151

Extended Cell
Range for Flexi
EDGE BTS Extended Cell for
GPRS/EDGE 105km Extended
Cell for CS 105km Extended
Cell for
GPRS/EDGE

BSS20966

"Extended Uplink
TBF Mode
(EUTM) in PS
Data Package"

BSS11110

Gb Over IP

Integrated Cellular
Text Telephony
Modem

BSS10112

Text Telephony
(TTY)

"Lb CI+TA Positioning Method for


BSC Capacity - 5
Location requests /
minute"

BSS21076
BSS30115

"Lb CI+TA Positioning Method


for BSC Capacity
- 5 Location
requests /
minute"

Features in BTSplus with Flexi BSC) (Cont.)

Id:0900d805808a406d
Confidential

69

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

RG(BR)
feature
number

RG(BR)
feature name

Support in
BS2xx@Flexi
BSC

Corresponding
RG(BSS)
feature
number

yes/no

feature name

none

"Lb U-TDOA Positioning Method for


BSC Capacity - 5
Location requests /
minute"

BSS30130

"Lb U-TDOA
Positioning
Method for BSC
Capacity - 5
Location
requests /
minute"

none

"Lb A-GPS Positioning Method for


BSC Capacity - 5
Location requests /
minute"

BSS30120

"Lb A-GPS Positioning Method


for BSC Capacity
- 5 Location
requests /
minute"

Table 4

8.2

RG(BSS)

Features in BTSplus with Flexi BSC) (Cont.)

GSM frequency bands


The BTSplus supports the following frequency bands:

GSM
GSM
GSM
GSM
GSM

850 MHz
900 MHz (primary GSM)
900 MHz extended (extended GSM)
1800 MHz (DCS)
1900 MHz (PCS)

When operating the BTSplus with the Flexi BSC product family, the GSM-R frequency
band is not used.

8.2.1

Multiband operation
If you have licenses in more than one of the frequency bands specified by GSM, multiband operation enables you to support the use of multi-band mobile stations. Refer to
Overview of dual band network operation for more information.

8.3

Antenna diversity
The two-branch antenna diversity in the receive path of the BTSplus is employed in
order to improve the receiver performance and thus the uplink quality under conditions
of fading. In order to implement antenna diversity, two spatially separated receiving
antennas are installed at the BTS site, each of which is connected to a separate receive
path of the TRX. Diversity combining of the two receive signals is performed within the
CU/TPU unit of the TRX. In order to achieve the highest diversity gain possible, the
maximum ratio combining technique is applied in the adaptive equalizer of the TRX.

70

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Supported functionality

The BTSplus at the Flexi BSC product family also supports transmission diversity on the
downlink. Refer to the Antenna hopping (BSS11134) and Nokia smart radio concept
for EDGE (BSS10104) features for more information.

8.4

Frequency hopping
Frequency hopping is used in GSM to counteract the negative effects of multipath
channel fading. It involves transmitting subsequent TDMA frames at different frequencies, introducing frequency diversity to the communication link between the BTS and the
MS, and thereby improving the quality of this link. In particular, frequency hopping
improves the average CIR ratio for slow-moving mobile subscribers in urban areas.
Because the rate of frequency hops is much lower than the transmission bitrate, this
method is known as slow frequency hopping (SFH).
BTSplus at the Flexi BSC product family supports both baseband frequency hopping,
with autonomous frequency redefinition, and synthesized frequency hopping (or radio
frequency hopping).
In baseband frequency hopping, the TRXs operate at fixed frequencies and the information stream of one traffic channel is switched to the different TRXs, frame by frame
according to the frequency hopping sequence.
Synthesized or radio frequency hopping is supported only by wideband TRXs, in which
the transmission frequency can be changed arbitrarily. The information stream of one
traffic channel is transmitted on one TRX that switches its frequency frame by frame,
according to the frequency hopping sequence.
When operating BTSplus with the Flexi BSC product family, you have to configure the
frequency hopping laws according to the guidelines described for other BTS types in the
Nokia Siemens Networks GSM/EDGE BSS product line. Refer to BSS7005: Frequency
hopping for more information.

8.4.1

Frequency hopping management


This feature is necessary in order to avoid manual reconfiguration of the BTSs with the
suitable hopping laws, at least in those cases where it is feasible to port the BR configuration to BSS.
The migration of BTS configurated with frequency hopping depends on the BTS HW
configuration, i.e. on the type of Carrier Units equipped on each BTSplus and on the
GPRS/EDGE configuration.
Considering the following BTSplus configuration cases:

BTSplus has a mixed CUs configuration (CU and ECU/FCU) or homogeneous CUs
and EDGE is disabled on all TRXs (only GPRS is used)
EDGE is configured on one or more TRXs and BTSplus is equipped with homogeneous CUs (ECU/FCU).
BTSplus has a mixed CUs configuration (CU and ECU/FCU) and EDGE is enabled
on one or more TRXs.

The migration of BB frequency hopping from BR to BSS is possible only in the case 1)
and 2).
In BSS the configuration 3) is not compatible with BB frequency hopping.

DN0933257

Id:0900d805808a406d
Confidential

71

Supported functionality

BSS21469: BS2xx@Flexi BSC product family

The RF frequency hopping can be migrated under the same conditions of BB hopping
plus the case 3) with some restrictions.
The configuration 3) above is supported with RF hopping, the following restriction:

BCCH TRX has to be configured on ECU/FCU and GTRX = no for all TRXs associated to CU

The Exporter Tool has to know which CUs are equipped for each BTS: the operator shall
provide the input to the tool via control file.
A new option cuconf is provided: by the new option cuconf the operator generates
the Control File template with info related to CU types associated to each TRX.
The Control File template will be generated with a default configuration and the operator
is allowed to adapt it to real one.
The control file is enhanced indicating if:

all migrated BTSs are equipped with homogeneous carrier units or not (ECU/FCU
or CU). The control file template will be generated considering an homogeneous
TRX carrier unit configuration with ECU/FCU type..

In case of mixed configuration the operator can specify for each TRX the type of the
equipped CUs (CU or ECU/FCU), modifying the control file.

g
8.4.1.1

the control file could be generated automatically starting from HW inventory files and/or
backup files.

Exporter Tool
For each BTS with frequency hopping enabled, the tool has to:

72

check the type of frequency hopping (BB or RF)


verify if the BTS configuration matches with cases1, or 2 or 3 (case 3 has to be
checked only for RF hopping and considering the restriction described above)
check if frequency hopping is configured on all TRXs or if there are one or more
TRXs with no hopping configured.
In case there are one or more TRXs with no hopping configured the tool does
not perform the migration and it shall notify it in the log file
The previous behavior doesn't apply to the BCCH TRX in case of RF hopping:
in this case it is valid for both BR and BSS configuration to have no hopping for
the TRX carrying the BCCH.
check if it is a DUALBAND or no DUALBAND BTS
In case of DUALBAND BTS: split the BTS in 2 BTSs belonging to the same
segment and associate the hopping laws to each BTS (TRXs on different frequency bands should be associated to different hopping laws).
Apply the BB/RF hopping parameters migration to the BTSs related to TRXs with
hopping enabled.

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

Supported functionality

Check if there is only 1 hopping law for each migrated BTS (2 hopping laws for
BCCH BTS in case of BB hopping).
In BR it is possible to configure more than one hopping law for the same BTS:
in this case the hopping configuration is not migrated and the tool generates a
warning.
In case of DUALBAND cell, the cell is migrated as two different BTSs and each
BTS hopping configuration is migrated independently on the configuration of the
other BTS.
Check if the MAIO settings in the starting configuration are aligned to the BSS
MAIO offset and MAIO step rules.

In BSS MAIO step and MAIO offset are used at BTS level:

MAIO offset indicates the first frequency used by the first TRX in the cell
MAIO step indicates MAIO difference between 2 consecutive TRX of the same cell

In BR the MAIO is defined at TRX and CHAN level.


The tool has to verify if the MAIO settings in BR is equivalent to BSS setting for MAIO
offset and MAIO step, by the following steps:

set MAIO offset as the min value of the MAIOs of the all TRXs in the cell
set MAIO step as the min value of the MAIO difference between first and the second
TRX; in case there is only one TRX hopping, the MAIO step has to be set to the
default value 1.

In case this condition is not satisfied, the hopping configuration is not migrated and the
tool generates a warning.
The tool has to check also if the MOBALLOC in BR configuration has been configured
with a number of frequencies too high. The BSS limits are 47 frequencies if EGPRS is
supported and 52 frequencies when EGPRS is not supported.
In case a higher number of frequencies are configured, the hopping configuration is not
migrated for that BTS and the tool generates a warning.

8.4.1.2

Specific behavior in case of BB frequency hopping


In BR BB hopping uses two hopping systems (FHSYs) with different HSN, MAIO, MOBALLOC: one FHSY is used for TSL0 to exclude TSL0 of BCCH and the other FHSY is
used for TSL1-7.In BSS with BB hopping one BTS is created and two HSNs are used:
HSN1 for TSL0 and HSN2 for TSL1-7. This is the mapping rule specific for BB hopping
(HOPP = 1, HOPMODE = BBHOP):

HSN1 equal to HSN of FHSY used on CHANNEL0 of TRX1 (or anyway of the first
no BCCH TRX)
HSN2 equal to HSN of FHSY used on CHANNEL1 of TRX1 (the first no BCCH TRX)

The previous mapping rules can be applied only if in the BR configuration:

all CHANNEL0 (except the BCCH TRX CHANNEL0) are configured with the same
hopping law
all channels (except the CHANNEL0) of all TRXs in the BTS are configured with the
same hopping law

If the previous conditions are not satisfied, the BB hopping is not migrated and the tool
generates a warning (the operator has to configure manually the hopping in this case).

DN0933257

Id:0900d805808a406d
Confidential

73

Supported functionality

8.4.1.3

BSS21469: BS2xx@Flexi BSC product family

Hopping configuration provided via control file


The user shall be able to provide the inputs for BTS hopping configuration via the control
file.The control file contains the following data (filled manually by the user):

BTS hoppingMode
BTS hoppingSequenceNumber1
BTS hoppingSequenceNumber2 (only for BB hopping)
BTS maioStep and maioOffset
MAL id and frequency list (for RF hopping only)

The usedMobileAllocation parameter is assigned automatically by the tool, depending


on the hopping mode and the MAL id.
The tool provides one additional option '-owrhopping' for switching from the normal
migration (where the hopping configuration is taken only from the BR BSC database file)
to the migration using the hopping configuration provided via the control file. When this
new option is used, the BSC database file and the info on the carrier type are ignored
by the tool because the hopping parameters are inserted directly in the control file by the
user.
The user can use this new hopping option when it detects the BR hopping rules cannot
be migrated due to not compatible BR hopping rules or due to a mixed hopping/no
hopping TRX configurations.

8.5

Dual carrier in downlink


The BTSplus at the Flexi BSC product family supports the Downlink dual carrier
(BSS21228) feature.

8.6

A5 ciphering
The BTSplus at the Flexi BSC product family supports the A5/0 and A5/1 stream ciphering algorithms. It optionally also supports the GSM A5/3 block ciphering algorithm for
privacy over the air interface. The Flexi BSC applies the A5/3 algorithm with the same
rules as those used with the Flexi EDGE BTS.

8.7
8.7.1

Control channels
4 SDCCH/8 on BCCH carrier
Up to 4 timeslots on the BCCH carrier can be configured as SDCCH/8 channels. To configure a radio timeslot as an SDCCH/8 channel, use the RTSL type parameter.

8.7.2

BCCH recovery in case of TRX failure


If the CU that serves as the BCCH carrier fails or is locked by the user, the BTSplus
autonomously starts a reconfiguration procedure in order to have another CU operating
as the BCCH carrier. The preferred BCCH TRX parameter is used to determine which
TRX is preferred for the reconfiguration of the BCCH carrier. Refer to Errors in functional blocks of the BTS site for more information.

74

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

8.7.3

Supported functionality

No support for 2nd CCCH


The BTSplus at the Flexi BSC product family does not support a BCCH + CCCH channel
combination on a timeslot other than timeslot 0. Therefore, radio timeslots for which the
CHTYPE attribute is set to CCCH are not migrated by the exporter tool. Refer to
Create TRX for more information.

8.7.4

Repeated FACCH/SACCH and temporary overpower


The features: repeated SACCH; and repeated FACCH and temporary overpower on
FACCH/SACCH for reduced call drop rate, are supported by the BTSplus at the Flexi
BSC product family. Refer to Robust AMR signaling (BSS20872) for more information.

8.7.5

Extended BCCH
Too long SI (system information) need more individual SI messages and the UE needs
more time to read them; it means more time for HO and Update. To reduce the time of
reading SI in GSM side, Extended BCCH is provided, that will bring more space for SI.
The extended BCCH feature reduces time of handovers and update by reducing amount
of individual SI 2 quater messages.As a result, less time is needed at the UE side for
HO and update.
With the Extended BCCH feature the operator can define the new BCCH channel to
the time slot 0. This new BCCH channel type consists of the BCCH block, the extended
BCCH block and 8 uncombined CCCH blocks.
The extended BCCH sub channels are used to broadcast information that is not as timecritical (for the operation of the mobile stations) as the information in the normal BCCH
channel.

The feature enhances interworking KPI between GSM and TD-SCDMA.


Extended BCCH will decrease CCCH capacity by 11%.
One additional block (=CCCH 0) is used for BCCH to carry SI 2 quarter messages.

The extended BCCH is enabled in the cell/sector with the parameter Extended BCCH
Enabled 'EBENA' .
BTS:
EBENA is added to enable Ext-BCCH for the BTS at the BSC
Abis:
SI 3 Rest Octets in "System information 3" having SI2quater information with
SI2quater_POSITION as '1' denoting that the SI2quater is to be transmitted on ExtBCCH.

8.8

Packet-switched data
The BTSplus at the Flexi BSC product family supports both GPRS and EDGE technology for packet-switched data services. Refer to GPRS and EDGE for more information on the respective solutions in the Nokia Siemens Networks GSM/EDGE BSS
product line.

DN0933257

Id:0900d805808a406d
Confidential

75

Supported functionality

8.8.1

BSS21469: BS2xx@Flexi BSC product family

Dual transfer mode


The BTSplus at the Flexi BSC product family supports DTM to provide mobile users with
simultaneous circuit-switched voice and packet-switched data services. Refer to Dual
transfer mode for more information.
Paging coordination between DTM and packet-switched paging procedures is however
not supported by this feature.
Since, when operating the BTSplus with the Flexi BSC product family, the power control
algorithms are executed on the BTSplus, the BTSplus needs to made aware of the
establishment of a DTM call and of the possible variations affecting handover and power
control functions. This is done by means of the DTM data IE in the CHANNEL ACTIVATION message.

8.8.2

Multislot classes
The BTSplus at the Flexi BSC product family supports multislot classes 1 - 45 for.multiple timeslots on TDMA frames. The multislot class of a mobile station defines the
maximum number of multiple time slots supported by the mobile station.
For more information on the maximum number of slots on the downlink and uplink for
the different multislot classes, refer to Maximum configurations.

8.8.3

Extended uplink TBF


A temporary block flow (TBF) temporarily relates a PDCH, or a set of PDCHs, to the
transfer of packet data to or from a mobile station. The Extended uplink TBF feature
allows uplink TBF resources to be kept even in the case of a short period of inactivity on
the uplink. This reduces the number of new TBF establishment procedures needed, thus
avoiding delays.

8.8.4

HSCSD
The BTSplus at the Flexi BSC product family supports HSCSD at data rates of 9.6 kbit/s
and 14.4 kbit/s, for both transparent and non-transparent data services. HSCSD
combines multiple radio timeslots to provide higher data rates for end-user applications.
Up to four radio timeslots are supported simultaneously to provide a total maximum data
rate of 57.6 kbit/s.
Upgrade or downgrade data handover procedures are not supported for transparent
services.
For more information, refer to HSCSD and 14 kbit/s data services.

8.9

Power save mode


If the Flexi EDGE dual TRX automatic power down feature is enabled in the Flexi BSC,
then the BSC analyzes traffic load on the TRXs and decides whether to power TRXs on
or off. Using the OAM mediation layer, the BTSplus TRXs are handled by the Flexi BSC
in the same way as the dual TRX units in other BSS BTS types (e.g. Flexi EDGE BTS).

76

Id:0900d805808a406d
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

8.10

Supported functionality

Hierarchical paging
Hearchical paging uses the BTSplus site manager (BTSM) managed object as a broadcasting element for paging messages. If paging messages need to be delivered to
several cells within a site belonging to the same location area, only one specific paging
command is sent to the respective BTSM object. The BTSM then distributes this
command to the respective cells. Hierarchical paging therefore reduces the required signaling capacity on the Abis interface. It is required in order to support sites bigger than
3 sectors with 24 TRXs or 6 sectors with 13 TRXs.
The Flexi BSC sends the paging command to the master BCF managed object, which
is then mapped by the OAM mediation layer to the BTSM object. Hierarchical paging
requires no additional configuration measures by the operator.

8.11

Real-time road traffic information


The BTSplus supports the Real-time road traffic information (BSS21333) feature.

8.12

Tandem free operation


The BTSplus at the Flexi BSC product family supports TFO functionality for both NBAMR and WB-AMR calls. Refer to BSS20960 Wideband AMR and BSS21118 TFO for
AMR for more information.

DN0933257

Id:0900d805808a406d
Confidential

77

Quality standards / specifications

BSS21469: BS2xx@Flexi BSC product family

9 Quality standards / specifications


9.1
9.1.1

Industrial requirements
Product safety
The BTSplus network elements comply with the safety requirements of the standards
listed in Table 5.
Europe / world
Safety of information technology equipment

IEC 60950-1

UL 60950-1

Radio transmitting equipment

IEC 60215

Safety of laser products

IEC 60825-1
IEC 60825-2

UL 60950

Fire resistance

IEC 60950
(4.4, Annex A)

UL 60950
UL 94

Degrees of protection
provided by enclosures

IEC 60529
Outdoor equipment: IP 55

NEMA Standards
Publication 250
Outdoor equipment: Type 3
R

Table 5

78

North America

Product safety requirements

Id:0900d805806498f8
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

9.1.2

Quality standards / specifications

Power supply interface

Test criteria

Steady state voltage tolerance requirements


-48 V DC

Normal operation:
Within this voltage range no
damage or deterioration of functional performance shall occur
during and after the test. Performance of Base Station equipment
shall meet the following requirements of the relevant Air Interface
standards:
- TX Modulation accuracy
- TX output power (only GSM)
- RX Reference sensitivity.
Table 6

9.2

9.2.1

230 V / 50 HZ
AC

120 V / 60 HZ
AC

Line to
neutral:
207 to 253 V

Line to
neutral:
90 to 132 V

47-53 Hz

Line to line:
180 to 264 V
57 - 63 Hz

ETS 300 1322:


- 40,5 to - 57,0
V

Power supply interface requirements

Quality requirements

Storage and transportation


The criteria in this section apply to the equipment in its normal shipping container. The
packaged equipment shall not be affected in its functional performances after it has
been exposed to the environment described in Table 7:
Environment

Transport

Climatic conditions

ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3
EN 300 019-2-1 Test T 1.2 EN 300 019-2-2 Test T 2.3

Biological conditions

ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3

Chemically active substances

ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3

Mechanically active substances

ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3

Mechanical conditions

ETS 300 019-1-1 class 1.2 ETS 300 019-1-2 class 2.3
EN 300 019-2-1 Test T 1.2 EN 300 019-2-2 Test T 2.3

Table 7

DN0933257

Storage

Storage and transportation

Id:0900d805806498f8
Confidential

79

Quality standards / specifications

9.2.2
9.2.2.1

BSS21469: BS2xx@Flexi BSC product family

Electromagnetic compatibility (EMC)


Emission requirements
BTSplus:

EN 301 502
EN 301 489-1
EN 301 489-8
EN 55022 class B
FCC part 15.107 class B
FCC part 15.109 class B
FCC part 15.111
FCC part 2.1053

g
9.2.2.2

FCC part 2.1057


The BTSplus complies with R&TTE directive 1999/5/EC.

Immunity requirements
BTSplus:

EN 301 489-1
EN 301 489-8
EN 55024
EN 61000-6-2
EN 300 386
TBR 12; TBR 13

80

Id:0900d805806498f8
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

9.3
9.3.1

Quality standards / specifications

Environmental requirements
Stationary use indoor
The indoor equipment shall not be affected by the environmental conditions specified in
ETS 300019-1-3 recommendation, class 3.1. The environmental requirements together
with the relevant test specifications are defined in Table 8.
Environmental requirements

Test specification

Climatic conditions for base station equip- EN 300019-2-3


ment
Test specification T3.1E
- 5C... + 45C
Chemically and mechanically active substances

No test required (The characteristic severities of class 3.1 should be considered


when designing the equipment and when
choosing components and materials)

Mechanical conditions

EN 300019-2-3
Test specification T3.2

Acoustic noise emission

ETS 300753 (6), class 3.1


Measurement method: ISO 7779

Earthquake

EN 300 019-2-3 chapter 4.2


(IEC 60721-2-6: Zone 4)

Table 8

DN0933257

Environmental requirements for stationary use indoor

Id:0900d805806498f8
Confidential

81

Quality standards / specifications

9.3.2

BSS21469: BS2xx@Flexi BSC product family

Stationary use outdoor


Outdoor base station equipment shall not be affected by the environmental conditions
specified in the ETS 300019-1-4 recommendation, class 4.1. The environmental
requirements together with the relevant test specifications are defined in Table 9
Environmental requirements

Test specification
Climatic conditions
EN 300019-2-4Test specification
T4.1,except for high air temperature test
severity:
1) Equipment with temperature control
system (note 1): - 33C to + 45C: all performance specifications are met
+ 45C to + 50C: operation without
damage and without fault alarms
possible2) other equipment than above:45C to + 55C

Chemically and mechanically active substances

not applicable

Mechanical conditions

EN 300019-2-4,
test specification T4.1
IEC 60721-3-4 class 4M5
Acoustic noise emission
ETS 300753 class 4.1E, rural area
day time<6.7 Bel
night time<6.1 Bel

Earthquake

Table 9

82

EN 300 019-2-4 chapter 4.2


(IEC 60721-2-6: zone 4)
Environmental requirements for stationary use outdoor

The temperature control system controls the temperature inside the enclosure with the
support of fans, heat exchanger, active cooling, active heating.

Id:0900d805806498f8
Confidential

DN0933257

BSS21469: BS2xx@Flexi BSC product family

9.4

Quality standards / specifications

List of norms and standards


The general configuration and the main features of the BTSplus are based on the specifications described in the phase 2" series of recommendations under the responsibility
of the GSM technical committee of the European telecommunication standards Institute
ETSI and the technical sub-committee T1P1 of the American national standards institute
ANSI, which are valid for the GSM 850, GSM 900, GSM 1800 and GSM 1900 systems.
In addition, the BSS fulfils the special requirements laid down in national specifications
of several worldwide network operators or by the manufacturer himself.
It is also worth noting that the GSM 1900 application for the American market refers to
the relevant specifications of the US standardization bodies; and, more specifically, to:
J-STD-007

issued by

T1P1

for the radio interface

J-STD-024

issued by

T1P1

for the A interface

It is well known that the above two documents are broadly based on the European ETSI
SMG phase 2 specification and that a full and formal alignment between the two specifications is issued by T1P1.
Finally, the following specifications for the DS-1 interface, relevant for T1 terrestrial
circuits (PCM lines at 1554 kb/s timeslots and A law or law speech encoding) are also
applicable:

9.4.1

ANSI T1 403-1989

issued by ANSI

for PCM T1 (DS-1) interface

AT&T publ. 54016 and 62411

issued by AT&T

for PCM T1 (DS-1) interface

FCC part 68 req.

issued by FCC

for PCM T1 (DS-1) interface

Antenna signaling
The signalling for remote tilt and tower mounted amplifier is compatible with 3GPP standards TS 25.460, TS 25.461, TS 25.462, TS 25.463.

DN0933257

Id:0900d805806498f8
Confidential

83