Horizon at Flexibsc dn0983164 01A en

GSM/EDGE BSS, Rel.
RG10(BSS), Operating
Documentation, Issue 08, Doc.
Change Delivery 1
Horizon BTS at Flexi BSC Product Family

DN0983164
Issue 01A
Approval Date 2011-06-14
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 DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, 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
f 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:
f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-
satzes.
2 Id:0900d8058086869f DN0983164
Issue 01A
Table of contents
This document has 81 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1 Software requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1 Network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.1 Horizon BTS product family overview . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.2 Horizonmacro Indoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.3 Horizonmacro Outdoor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.4 Horizonmacro 12 Carrier Outdoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.5 Horizon II macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.6 Horizon II macro Outdoor Lite enclosure . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.7 Horizon II macro DC Outdoor enclosure . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.8 Horizon II mini (Outdoor enclosure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.9 Horizon II micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.10 Horizon 2G-nx BBU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2 BSS Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2.1 Abis interface transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2.2 Abis interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3 Operation and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5 System impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1 Relation to other features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2 Impact on external interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.1 New parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.1.1 horizon TRX type (HTYPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.1.2 horizon associated TRX ID (HASSO) . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.1.3 horizon edge service type (ETYPE). . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.1.1.4 horizon power finetune (HPOFT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.1.2 Modified parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.1.2.1 site type (TYPE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.1.2.2 BCCH TRX TX pwr reduction (TPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1.2.3 transceiver identification (TRX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.1.2.4 PCM port ID 0 (PORT0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.1.2.5 PCM port ID 1 (PORT1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.1.2.6 PCM port ID 2 (PORT2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DN0983164 Id:0900d8058086869f 3
Issue 01A
6.1.2.7 PCM port ID 3 (PORT3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6.1.2.8 PCM port ID 4 (PORT4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1.2.9 PCM port ID 5 (PORT5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1.2.10 PCM port ID 6 (PORT6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.2.11 PCM port ID 7 (PORT7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1.2.12 bb Unit Supports Edge (BB_UNIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1.2.13 2G TRX power down threshold (PWDT) . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.1.2.14 2G TRX power up threshold (PWUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.1.2.15 TRX DDU association (DDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1.2.16 Server TRX Id (-). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.2 MML commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.2.1 EE MML commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.2.1.1 EEI - OUTPUT RADIO NETWORK CONFIGURATION . . . . . . . . . . . . . 54
6.2.2 EF MML commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.2.2.1 EFC - CREATE BASE CONTROL FUNCTION . . . . . . . . . . . . . . . . . . . 54
6.2.2.2 EFM - MODIFY BASE CONTROL FUNCTION PARAMETERS. . . . . . . 55
6.2.2.3 EFO - OUTPUT BASE CONTROL FUNCTION PARAMETERS . . . . . . 56
6.2.3 EW MML commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.2.3.1 EWL - SET LIST EXISTING BCF SOFTWARE BUILDS . . . . . . . . . . . . 57
6.2.3.2 EWO - LIST SOFTWARE CONFIGURATION OF BCF . . . . . . . . . . . . . 57
6.2.3.3 EWP - MML LIST BCF SOFTWARE BUILD CONTENTS . . . . . . . . . . . 57
6.2.3.4 EWS - SET OR REMOVE INITIAL SOFTWARE BUILD . . . . . . . . . . . . 59
6.2.4 ER MML commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.2.4.1 ERC - CREATE TRANSCEIVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.2.4.2 ERM - MODIFY TRANSCEIVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.2.4.3 ERO - OUTPUT TRANSCEIVER PARAMETERS . . . . . . . . . . . . . . . . . 61
6.3 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.4 Measurements and counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7 Activating and configuring the feature. . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.1 LAPD multiplexed configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.2 BCF creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.3 BTS creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.4 TRX creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7.4.1 TRX: EDGE - ASYMMETRIC mode creation . . . . . . . . . . . . . . . . . . . . . 76
7.5 RNW configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4 Id:0900d8058086869f DN0983164
Issue 01A
List of figures
Figure 1 Network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
DN0983164 Id:0900d8058086869f 5
Issue 01A
List of tables
Table 1 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 2 Horizon BTS product family overview . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 3 Supported code rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 4 horizonTrxType (Horizon TRX Type) . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 5 horizonAssociatedTrxId (Horizon Associated TRX ID) . . . . . . . . . . . . . 27
Table 6 horizonEdgeServiceType (Horizon EDGE Service Type) . . . . . . . . . . . 28
Table 7 horizonPowerFinetune (Horizon Power Finetune) . . . . . . . . . . . . . . . . . 30
Table 8 bcfType (Site Type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 9 transmitPowerReduction (BCCH TRX TX Pwr Reduction) . . . . . . . . . . 35
Table 10 id (TRX ID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 11 pcmPortId0 (PCM Port ID 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 19 bbUnitSupportsEdge (BB Unit Supports EDGE) . . . . . . . . . . . . . . . . . . 46
Table 20 dtrxPowerDownThreshold (2G TRX Power Down Threshold) . . . . . . . . 48
Table 21 dtrxPowerUpThreshold (2G TRX Power Up Threshold) . . . . . . . . . . . . 49
Table 22 trxDDUAssociation (TRX DDU Association) . . . . . . . . . . . . . . . . . . . . . 51
Table 23 serverTRXId (Server TRX Id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6 Id:0900d8058086869f DN0983164
Issue 01A
Horizon BTS at 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.
Changes between issues 01 (2011-01-24) and 01A (2011-06-14)
Introduction (1)
• GSR and RSR terms have been explained in the terminology section.
• Requirements for the Flexi BSC and BSC3i have been added to the introduction.
Benefits (2)
• The benefits section has been rephrased.
Requirements (3)
• Table 1 Software requirements has been updated.
Network architecture (4.1)

• Mixed configurations for the Horizonmacro and Horizon II family has been added.
• BSC connectivity options - HDSL has been removed from Table 2 Horizon BTS
product family overview.
• BSS Abis has been removed form the Network elements list.
• Packet Abis has been removed form Figure 1 Network architecture.
BSS Abis interface (4.2)

• Chapter has been updated to improve technical correctness.
• Support for the CTU radio has been added to the 4.2.2 Abis interface configuration
chapter.
Operation and maintenance (4.3)

• Element Manager high level functionalities have been added and the list of the func-
tionalities has been removed.
• NetAct functionalities have been removed form the chapter because of no visibility
to the Horizon BTS.
• RSR has been removed form the chapter.
System impacts (5)

• 5.1 Relation to other features descriptions have been improved. the following
descriptions have been changed: BSS6035: RF-hopping, BSS09006: GPRS,
BSS10091: EDGE, BSS10045: Dynamic Abis, BSS20760: BTS ID shown in BTS
Manager, BSS20151: Adjustable Intelligent Shutdown, BSS20249: AMR FR and
BSS20588: TRAU Bicasting in AMR FR/HR handover.
Parameters (6.1)
• The parameters have been updated.
MML commands (6.2)

• The following printouts of MML commands have been updated: EFO, EEI, EWP, EWS,
ERC, and ERO.
DN0983164 Id:0900d8058086f0a4 7
Issue 01A
Summary of changes Horizon BTS at Flexi BSC Product Family
Activating and configuring the feature (7)

• The command in 7.4.1 TRX: EDGE - ASYMMETRIC mode creation has been cor-
rected.
• The printouts have been changed and configuration settings have been added to the
sub-chapters.
Abbreviations (8)
• GSR and RSR abbreviations have been added.
8 Id:0900d8058086f0a4 DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family Introduction
1 Introduction
The Horizon BTS at Flexi BSC Product Family feature provides a network solution in
which Horizon base stations are managed by BSCs of the Flexi BSC product family. This
solution therefore represents merging of the GSM/EDGE BSS and GSR product lines.
The BSS controlled by RG10 Flexi BSC or BSC3i might consists of Horizon, BTSplus,
Flexi EDGE, UltraSite and Flexi Multiradio BTSs. Any of such mixed configurations is
supported by BSC and NetAct. The BSC3i should have PCU2 to support Horizon BTS.
Horizon BTSs is connected to FlexiBSC/BSC3i via Abis. Abis is the BSS Abis with a few
modifications and restrictions which are mandatory because of Horizon BTS HW restric-
tions (especially with older HW versions). There are some functionalities which are
changed or limited in the Abis and BSC3i.
1.1 Terminology
In this feature description, the term operator is used to refer to the GSM/EDGE network
operator, while the operator‘s customers are referred to as end customers or sub-
scribers.
Throughout this feature description, the term Flexi BSC is 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.
The BSS Abis interface implementation used in the product line to connect the Horizon
BTS with the BSC is referred to as the BSS Abis. It is also the Abis interface implemen-
tation used in the BSS product line to connect the Flexi EDGE BTS with the Flexi BSC.
There are two kinds of software releases paired with the BSC Horizon BTS, GSM
Software Release (GSR) and RAN Software Release (RSR). The RSR software release
is used when a BSC is provided by a third party company.
1.2 Network elements

Horizon BTS product family range:
• Horizonmacro Indoor
• Horizonmacro Outdoor
• Horizonmacro 12 Carrier Outdoor
• Horizon II macro
• Horizon II macro Outdoor Lite enclosure
• Horizon II macro DC Outdoor enclosure
• Horizon II mini (Outdoor enclosure)
• Horizon II micro
• Horizon 2G-nx BBU
For more information on the individual network element types in the GSR line, refer to
the individual product descriptions.
Flexi BSC product family, UltraSite EDGE BTS, MetroSite BTS, Flexi EDGE BTS,
NetAct and TCSM3i are products of the GSM/EDGE BSS line.
The Flexi BSC product family consists of:
• BSC3i 660
DN0983164 Id:0900d80580888220 9
Issue 01A
Introduction Horizon BTS at Flexi BSC Product Family
• BSC3i 1000
• BSC3i 2000
• Flexi BSC
For more information on the individual network element types, refer to the individual
product descriptions in Nokia Siemens Networks GSM/EDGE BSS, rel. RG10(BSS),
operating documentation.
10 Id:0900d80580888220 DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family Benefits
2 Benefits
The BSS Abis provides meshed network with both BSS Flexi BTS and Horizon BTS
cooperating in the same BSS architecture and managed by a single NetAct. It means
the Horizon BTS is actually connected to BSC3i via the BSS Abis interface. This solution
then allows GSR customers to participate to the evolution of BSS portfolio. Several addi-
tional BSS features work immediately after Horizon BTS migration.
DN0983164 Id:0900d8058089060f 11
Issue 01A
Requirements Horizon BTS at Flexi BSC Product Family
3 Requirements
The software and hardware requirements for this feature are:
3.1 Software requirements

Table 1 Software requirements lists the software requirements for Horizon BTS at Flexi
BSC Product Family.
Network element Required software release

BSC S14 EP8.1
NetAct OSS5.2 MP2
Horizon BTS HR 1
Table 1 Software requirements
3.2 Hardware requirements

This feature requires the following hardware:
• Flexi BSC/BSC3i
• Horizon BTS
• PCU2
12 Id:0900d80580888222 DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family Functional description
4 Functional description
4.1 Network architecture

The network architecture illustrates the possible configurations for managing Horizon
BTS with the Flexi BSC product family.
Network elements:
• Horizon BTS family products,
• Flexi BTS family products,
• Flexi BSC/BSC3i,
• NetAct,
• Element Manager.
Figure 1 Network architecture

After the migration of the Horizon BTSs family products to the Flexi BSC the Horizon
BTSs are connected to Flexi BSC/BSC3i via BSS Abis. The Horizon BTSs are managed
by NetAct and Element Manager.
The Horizon BTS family hardware supports (E)GSM900 and GSM1800 bands.
4.1.1 Horizon BTS product family overview

The Horizon BTS at Flexi BSC Product Family feature supports migration of Horizon
base transceiver stations (BTSs). The Horizon BTS family is divided into:
• Horizonmacro,
DN0983164 Id:0900d805808686a1 13
Issue 01A
Functional description Horizon BTS at Flexi BSC Product Family
• Horizon II family (Horizon II macro, Horizon II mini and Horizon II micro),

• Horizon 2G-nx BB.
Mix of cabinet types and radios at a Horizon BTS site is also supported. There is possi-
bility to have Horizonmacro site that consists of the Horizonmacro master with Horizon
II family slaves, similarly the Horizon II macro site with a Horizon II macro master with
Horizonmacro slaves. Both such configurations support all radio types.
The radio unit types used by Horizon BTSs are CTU, CTU2 and CTU2D in Horizon-
macro and CTU2, CTU2D and CTU8m used in the Horizon II family.
Horizon BTS Unit type Working Supported Number BSC con-

environ- bands of nectivity
ment carriers options
Horizonmacro Base Trans- Indoor (E)GSM900, 6 - 12 E1
Indoor ceiver Station GSM1800
(BTS)
Horizonmacro Base Trans- Outdoor (E)GSM900, 6 - 12 E1
Outdoor ceiver Station GSM1800
(BTS)
Horizonmacro Base Trans- Outdoor (E)GSM900, 12 - 24 E1
12 Carrier ceiver Station GSM1800
Outdoor (BTS)
Horizon II macro Base Trans- Indoor (E)GSM900, 12 - 48 E1
ceiver Station GSM1800
(BTS)
Horizon II macro Base Trans- Outdoor (E)GSM900, 12 - 48 E1
Outdoor Lite ceiver Station GSM1800
enclosure (BTS)
Horizon II macro Base Trans- Outdoor (E)GSM900, 12 - 48 E1
DC Outdoor ceiver Station GSM1800
enclosure (BTS)
Horizon II mini Base Trans- Indoor, (E)GSM900, 4 - 16 E1
ceiver Station Outdoor GSM1800
(BTS)
Horizon II micro Base Trans- Indoor, (E)GSM900, 2 E1
ceiver Station Outdoor GSM1800
(BTS)
Horizon 2G-nx Base Trans- Indoor - 48 E1
BBU ceiver Station
(BTS)
Table 2 Horizon BTS product family overview
4.1.2 Horizonmacro Indoor

The Horizonmacro indoor is a base transceiver station (BTS) cabinet with variants that
operate in the following frequency bands are GSM/EGSM900, GSM1800.
14 Id:0900d805808686a1 DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family Functional description
Up to six Compact Transceiver Units (CTUs) can be fitted, providing up to six carriers.
If the later double density CTU2s or CTU2Ds (developed for Horizon II macro) are
installed, up to12 carriers are supported. Indoor cabinets operate from either-48/60V
DC(positive earth), +27V DC (negative earth), or wide input, nominal 120/240V. An
optional battery backup system is available for use with the -48/60V DC BTS.
The Horizonmacro supports baseband frequency hopping (BBH) and synthesizer fre-
quency hopping (SFH).
4.1.3 Horizonmacro Outdoor

The Horizonmacro outdoor is a six to twelve carrier Base Transceiver Station (BTS). The
enclosure contains one Horizonmacro indoor BTS cabinet with variants that can operate
in the following frequency bands - GSM/EGSM900, GSM1800.
The enclosure operates from nominal 110 V single phase or nominal 230 V, single or
three phase, ac supply. The Thermal Management System (TMS) located in the bottom
of the unit provides the cabinet temperature control.
The Horizonmacro supports baseband frequency hopping (BBH) and synthesizer fre-
quency hopping (SFH).
4.1.4 Horizonmacro 12 Carrier Outdoor

The Horizonmacro 12 carrier outdoor is a six to 24 carrier Base Transceiver Station
(BTS). The enclosure can contain either one or two Horizonmacro indoor BTS cabinets
that can operate in the following frequency bands - GSM/EGSM900, GSM1800.
The enclosure operates from a nominal 230 V, single phase or three phase ac supply.
Temperature control within the enclosure is provided by two heat management systems
(HMS), one located on the inside of each enclosure door.
4.1.5 Horizon II macro

The Horizon II macro is a 12 to 48 carrier Base Transceiver Station (BTS) cabinet, with
variants that operate in the GSM/EGSM900 and GSM1800 frequency bands.
The BTS cabinets are designed for indoor use. They can operate from either -48 V to 60
V DC (positive earth) or +27 V DC (negative earth) or wide input, Nominal 120 V to 240
V AC single phase supplies.
4.1.6 Horizon II macro Outdoor Lite enclosure

The Horizon II macro is a 12 carrier BTS, with variants that operate in the
GSM/EGSM900 and GSM1800 frequency bands.
The Outdoor Lite enclosure operates from a nominal 230 V, single phase or three phase
AC supply.
The function of the Outdoor Lite enclosure is to provide a platform for a Horizon II macro
indoor BTS cabinet allowing it to operate in an outdoor environment.
Temperature within the enclosure is controlled by a Heat Management System (HMS),
mounted on the door and controlled from a control card (HMSCC) mounted in the Power
Distribution Unit (PDU).
DN0983164 Id:0900d805808686a1 15
Issue 01A
Functional description Horizon BTS at Flexi BSC Product Family
4.1.7 Horizon II macro DC Outdoor enclosure

The Horizon II macro is a 12 to 48 carrier BTS, with variants that operate in the
GSM/EGSM900 and GSM1800 frequency bands.
The DC Outdoor enclosure operates from a nominal –48 V supply.
The function of the DC Outdoor enclosure is to provide a platform for a Horizon II macro
indoor BTS cabinet allowing it to operate in an outdoor environment.
Temperature within the enclosure is controlled by a Thermal Management System
(TMS) mounted on the door, and controlled by a controller mounted on the enclosure
framework below the indoor cabinet shelf.
4.1.8 Horizon II mini (Outdoor enclosure)

The Horizon II mini is a 4 to 16 carrier base station capable of filling either the macro or
micro BTS role. The Horizon II mini has variants that operate in the GSM/EGSM900 and
GSM1800 frequency bands.
The BTS cabinets can be installed indoors or in an outdoor enclosure. The indoor
cabinet can operate from – 48 V to 60 V DC (positive earth), + 27 V DC (negative earth)
or wide input nominal 120 V to 240 V AC single phase supplies. Both AC and DC
variants are available for the Horizon II outdoor mini. A Horizon II mini DC outdoor
variant can operate from - 48 V DC (positive earth).
4.1.9 Horizon II micro

The Horizon II micro is a 2 carrier compact BTS, that might be pole or wall mounted
offering a wide range of deployment locations. It can be quickly deployed and is suitable
for both indoor and outdoor applications; no separate enclosure is required for outdoor
applications.
The Horizon II micro is available in both GSM 900 and GSM 1800 frequencies and
provides up to two transceiver capacity in a single enclosure allowing it to support in
Omni-2 configurations. In order to achieve sectored configurations, up to four Horizon II
micro enclosures can be deployed in a logical site.
The Horizon II micro is an AC cabinet operating from a wide input nominal 120 V to 240
V AC single phase supply.
4.1.10 Horizon 2G-nx BBU

The Horizon 2G-nx BBU is an indoor unit designed to be fitted into a standard 19-inch
rack which is customer supplied. This is a 48 carrier base band unit primarily intended
for use with RCTU8m supporting EGSM 900 and GSM1800 frequencies. It can also be
used as a master controller to any type of the cabinets.
The Horizon 2G-nx BBU operates from –48 V DC (positive earth) and accommodates
two –48 V power supply modules.
16 Id:0900d805808686a1 DN0983164
Issue 01A
4.2 BSS Abis interface

The BSS Abis interface enables connection of BTSs to the Flexi BSC.
4.2.1 Abis interface transport

The only transport option supported with Horizon BTS is E1. Max number of E1 lines per
BTS site is 6. In Horizon BTS E1 lines are identified as ports which are numbered from
0 to 7.
Abis transport topologies

Topologies supported by Horizon BTS are daisy chain and star topology. However BSC
is not aware of daisy chain or star configuration, it only understands Abis mapping in the
outgoing E1 lines. Appropriate cross-connections configuration for hops in a daisy chain
has to be set. Dasy chain requires Element Manager (EM) or Site Configuration File
(SCF) configuration for each downstream hop.
Abis timeslot allocation

Abis timeslot allocation principles are similar to the BSS Abis. However, there are further
restrictions on configurations and options. BSC determines how traffic channels and
logical channels are distributed among available timeslots.
Horizon BTS supports only 64 kbps allocation for LAPD channels and the LAPD multi-
plexing functionality is used.
Allocation for traffic channels (TCH) is similar to the BSS Abis implementation. Two con-
secutive 64 kbps timeslots are allocated for each transceiver. One 64 kbps timeslot is
allocated for operation and maintenance unit signalling (OMUSIG). There is one opera-
tion and maintenance unit signalling timeslot for each base control function (BCF).
Logical transceiver channels (TRXSIG) can be multiplexed in the same timeslot with
OMUSIG. One or more 64 kbps timeslots can be allocated for transceiver channels.
Transceiver channels are multiplexed. Maximum of four logical transceiver channels
use the same 64 kbps timeslot.
4.2.2 Abis interface configuration

EDAP handling
Horizon BTS can only support Radio Level EDAP for CTU/CTU2/CTU2D radios. While
using LAPD multiplexing the TRXs associated with the same hardware have to be mul-
tiplexed together. The BTS for CTU8m supports more flexible allocation spanning
multiple radios but cannot exceed more than four logical TRX per EDAP. Configurations
other than these are rejected by Horizon BTS.
LAPD protocol
LAPD establishment procedure is the same as in the current Abis. BSC sends the set
asynchronous balanced mode repeatedly and a BTS answers.
Horizon BTS gets LAPD parameters from SCF. BSC uses LAPD parameter sets. The
operator can select a parameter set but cannot modify individual parameters. The
parameter set includes separate parameter values for operation and maintenance unit
signaling and transceiver channel. The LAPD protocol can only be used in the multi-
plexed scenario.
LAPD multiplexing
DN0983164 Id:0900d805808908c8 17
Issue 01A
The LAPD signaling data related to several TRXs is multiplexed onto one physical LAPD
link defined by 64 kbps. Several TRXs belonging to a Horizon BTS can be configured
on a common physical LAPD link. Simultaneous signaling data link connections, or
logical LAPD links, can be multiplexed onto one physical LAPD link.
This method allows the optimized use of the available LAPD channels, and therefore
reduces the signaling bandwidth required.
18 Id:0900d805808908c8 DN0983164
Issue 01A
4.3 Operation and maintenance

Network Management
NetAct is the network management system with comprehensive set of tools to support
planning, monitoring, CM, PM, FM, software management.
NetAct parameter database is the master storage for radio network parameters. The
radio network plans and mapped GSR data, enter NetAct and are populated into the
radio network (BSCs). Parameter changes made locally by the BSC MML are reported
immediately into NetAct for database storage.
The NetAct entity is replacement for the GSR OMC entitie. The Horizon BTS has con-
formed the NetAct functionalities.
Element Manager
The management of entities within the GSR and BSS BSC is fundamentally different.
The main difference is that the NetAct entity does not manage any hardware devices.
The management of hardware entities is performed by an Element Manager which
provides remote access control to the hardware configuration at the BTS. The Element
Manager provides cross connections for daisy chaining, logical TRX allocation to
physical radio hardware, LAPD and OMUsig configuration and also allows access to
BTS level parameters and configuration items.
DN0983164 Id:0900d805808908cc 19
Issue 01A
System impacts Horizon BTS at Flexi BSC Product Family
5 System impacts
This chapter describes the inter-working relation of the Horizon BTS at Flexi BSC
Product Family feature with the other features, and the impact of this feature on the
external interfaces.
This chapter is divided into the following sections:
• Relation to other features
• Impact on external interfaces
5.1 Relation to other features

This section discusses the inter-working relation of the Horizon BTS at Flexi BSC
Product Family feature with the following listed features:
• BSS7020: Intelligent shutdown with timer control
• BSS6035: RF-hopping
• BSS4040: Satellite Abis
• BSS20540: Remote MMI
• BSS09006: GPRS
• BSS10091: EDGE
• BSS10045: Dynamic Abis
• BSS07078: Local object blocking
• BSS20817: End to End Downlink Abis Performance Monitor
• BSS20760: BTS ID shown in BTS Manager
• BSS20151: Adjustable Intelligent Shutdown
• BSS20984: 2G TRX Automatic Power Down
• BSS21261: 2G TRX Manual Power Down
• BSS20093: A5/3 Ciphering
• BSS7003: High Speed Circuit Switched Data
• BSS7037: 14.4 kbit/s GSM data services
• BSS07036: Dynamic SDCCH Allocation
• BSS30060: AMR HR
• BSS20249: AMR FR
• BSS5010: Half Rate
• BSS20916: AMR HO Signalling Optimization
• BSS20588: TRAU Bicasting in AMR FR/HR handover
• BSS20958: Energy saving mode for BCCH TRX
• BSS101411: Extended BCCH
• BSS21538: Extended CCCH
BSS7020: Intelligent shutdown with timer control

The BSC and BCF level parameters are visible and modifiable in case the Horizon BTS
option is on.
BSS6035: RF-hopping
The RF Hopping feature is handled like in Flexi EDGE.
20 Id:0900d805808908ce DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family System impacts
The local hopping from SCF before hopping from BSC is allowed for the operator.
BSS4040: Satellite Abis

The Satellite Abis feature is handled like in Flexi EDGE.
BSS20540: Remote MMI

The Remote MMI feature is handled like in Flexi EDGE.
BSS09006: GPRS
The GPRS feature is handled like in Flexi EDGE with few key differences:
• Horizon BTS supports mix of hardware and because of that it supports mix of service
capabilities; it is possible to configure EDGE and nonEDGE capable radios in the
same site
• EDAP restrictions
BSS10091: EDGE
The different Horizon BTS radio unit types have different EDGE capabilities and their
operational mode can be controlled with the Horizon EDGE Service Type parameter.
The Horizon Edge Service Type parameter modification is handled from MML point of
view. The baseband hopping is not allowed with EDGE.CTU-1 is not EDGE capable.
CTU2/CTU2D is fully EDGE capable in single density configuration CTU2 in double
density configuration operates in EDGE POWER mode.CTU2D in double density con-
figuration can operate in three modes: EDGE-POWER mode, EDGE-CAPACITY mode
or EDGE-ASYMMETRIC mode.
CTU8m TRXs are fully EDGE capable.
Differences between Flexi EDGE and the Horizon BTS:
• mix of hardware capabilities
• EDAP
• POWER restrictions reducing capacity
• CAPACITY restrictions on TRX associations
• ASYM restrictions on TRX associations end EDGE capability
Parameter values for the EDGE support:
• EDGE-POWER mode - the TRXs of CTU2/CTU2D have different EDGE capabili-
ties: Carrier A is fully EDGE capable whereas Carrier B is not GPRS/EGPRS
capable. When there is a TSL on Carrier A configured to EGPRS, then the respec-
tive TSL on Carrier B is blanked (by system). The blanked TSL cannot be used for
any traffic (not even for CS calls).
• EDGE-CAPACITY mode - the TRXs of CTU2/CTU2D have different EDGE capabil-
ities Carrier A is fully EDGE capable whereas Carrier B is GPRS capable (EDGE is
not supported on Carrier B). Note that there can be EGPRS territory on Carrier A
and GPRS territory on Carrier B only if the TRXs (Carrier A and Carrier B) belong to
different BTS objects.
• EDGE mode
DN0983164 Id:0900d805808908ce 21
Issue 01A
• EDGE-ASYMMETRIC mode - the TRXs of CTU2/CTU2D have different EDGE

capabilities: Carrier A is fully EDGE capable whereas Carrier B has asymmetric
EDGE capability (all coding schemes MCS1-MCS9 are supported in DL direction but
in UL direction only GMSK modulation (MCS1-MCS4) is supported).
BSS10045: Dynamic Abis

The feature is handled like in Flexi EDGE, but there is restriction that DAP cannot be
shared across the CTUs, even in the case of CTU8m the max count of TRXs in the DAP
is 4. The dynamic Abis feature is also not possible for single CTU2/2D radio.
BSS07078: Local object blocking

The Local object blocking is handled like in Flexi EDGE.
BSS20817: End to End Downlink Abis Performance Monitor

The feature is supported also for the Horizon BTS. The feature usage control is not site
type specific.
BSS20760: BTS ID shown in BTS Manager

The real BTS ID is sent from the base station data to Horizon as for Flexi EDGE.
Element Manager allows the BTS ID to be shown in the User Interface.
BSS20151: Adjustable Intelligent Shutdown

The Flexi EDGE license is reused by Horizon BTS. The BSC, BCFand TRX level param-
eters are visible and modifiable for Horizon BTS in case Intelligent Shutdown for Flexi
EDGE BTS license state is ON or CONF.
The parameter modification is allowed for Horizon BTS. The feature usage for Horizon
BTS is possible as for existing Flexi EDGE feature license. Otherwise the existing error
code is returned to the user.
BSS20984: 2G TRX Automatic Power Down

The feature is handled like in Flexi EDGE except that the TRXs are shutted down one
by one instead of Dual TRX unit in the case of Flexi EDGE.
Flexi EDGE Dual TRX Automatic Power Down feature related parameters are allowed
also in case of Horizon BTS. Horizon BTS indicates whether a radio is capable to shut
down or not.
BSS21261: 2G TRX Manual Power Down

The MML command allow power up and power down for Horizon BTS. The feature
usage is controlled with the existing feature license also for Horizon BTS.
BSS20093: A5/3 Ciphering

The A5/3 ciphering is not allowed for CTU.
22 Id:0900d805808908ce DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family System impacts
BSS7003: High Speed Circuit Switched Data

The feature is not supported.
The only supported data rates are 9.6 kbps and below.
BSS7037: 14.4 kbit/s GSM data services

The feature is not supported.
The only supported data rates are 9.6 kbps and below.
BSS07036: Dynamic SDCCH Allocation

The number of dynamic SDCCHs is limited according to multiplexing.
In order to have current limits valid also for Horizon BTS, multiplexing is taken into
account when limiting number of dynamic SDCCHs.
BSS30060: AMR HR
The same AMR HR codec mode set rules are used for Horizon BTS as for FlexiEDGE.
BSS20249: AMR FR
The CTU do not support all code rates. Code rates supported by CTU are in Table
3 Supported code rates.
CS1 CTU CTU2 CTU2D CTU8m

TCH AFS12.2 mandatory supported supported supported supported
TCH AFS10.2 supported supported supported supported
TCH AFS7.95 - - - -
TCH AFS7.4 mandatory supported supported supported supported
TCH AFS5.9 mandatory - supported supported supported
TCH AFS4.75 mandatory - supported supported supported
TCH AHS7.95 supported supported supported supported
TCH AHS7.4 mandatory supported supported supported supported
TCH AHS5.9 mandatory supported supported supported supported
TCH AHS4.75 mandatory - supported supported supported
Table 3 Supported code rates
DN0983164 Id:0900d805808908ce 23
Issue 01A
BSS5010: Half Rate

The feature is handled like in Flexi EDGE.
BSS20916: AMR HO Signalling Optimization

BSS20588: TRAU Bicasting in AMR FR/HR handover

The TRAU Bicasting in AMR FR/HR handover is allowed for Horizon BTS.
Bicasting is not supported for the CTU radio.
BSS20958: Energy saving mode for BCCH TRX

The Energy saving mode for BCCH TRX feature is allowed for Horizon BTS with existing
Flexi EDGE feature license. The power reduction is also supported for Horizon BTS.
BSS101411: Extended BCCH

BSS21538: Extended CCCH

5.2 Impact on external interfaces

This section describes the impact of the Horizon BTS at Flexi BSC Product Family
feature on the external interface: BSC-NMS (NetAct).
New parameters are supported by BSC-NMS (NetAct) in connection to Horizon BTS
migration to Flexi BSC.
24 Id:0900d805808908ce DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family User interface
6 User interface
6.1 Parameters
6.1.1 New parameters

This chapter lists the new parameters introduced with the Horizon BTS at Flexi BSC
Product Family feature.
6.1.1.1 horizon TRX type (HTYPE)
Parameter name Horizon TRX Type

Abbreviated name horizonTrxType
3GPP name -
Managed Object TRX
Multiplicity 1
Description The Horizon TRX Type together with the Horizon
EDGE Service Type parameter defines the EDGE
capabilities of the TRX HW.
Value Single (0) is used for CTU and when CTU2 or
CTU2D is used in single density configuration.
Normal EDGE capabilities is available for CTU2
and CTU2D when Horizon TRX type is Single
(0).The EDAP relation is 1 TRX - 1 EDAP, i.e. the
EDAP configured for the TRX cannot be shared
with any other TRX.
Values Carrier A and Carrier B are used when
CTU2 or CTU2D is used in double density configu-
ration. Limited EDGE capabilities is available for
Horizon TRX within the pair Carrier A and Carrier B.
Carrier A and Carrier B can share the same EDAP
in EDGE-CAPACITY mode, in EDGE-ASYMMET-
RIC mode and in non-EDGE configurations.
Value Multi is used when CTU type is CTU8m.
Normal EDGE capabilities is available when
Horizon TRX type is Multi. It is possible to share
one EDAP with up to four (Horizon TRX Type =
Multi) TRXs configured on a single or across
multiple CTU8m radios.
Parameter is valid only for Horizon BTS.
Additional information -
Range Single (0), Carrier A (1), Carrier B (2), Multi (3)
Table 4 horizonTrxType (Horizon TRX Type)
DN0983164 Id:0900d805808686a3 25
Issue 01A
User interface Horizon BTS at Flexi BSC Product Family
Step -
Units -
Formula for getting gui ==> internal
internal value Single ==> 0
Carrier A ==> 1
Carrier B ==> 2
Multi ==> 3
Default value Single (0)
Default value notes Both Carrier A and Carrier B TRX of the paired
TRXs shall be in locked state.
Required on creation optional
Modification Requires object locking
Modified -
Related parameters horizonAssociatedTrxId of TRX - When the Horizon
TRX Type is Carrier A, the Horizon Associated
Carrier B must be defined.
horizonEdgeServiceType of TRX - When the
Horizon TRX Type is Carrier A, the values NON-
EDGE, EDGE-POWER, EDGE-CAPACITY and
EDGE are possible. When the Horizon TRX Type is
Carrier B, the Horizon EDGE Service Type value
depends on the corresponding Carrier A Horizon
EDGE Service Type value.
Parameter relationships -
Related options -
Feature dependencies • Support for Horizon BTS Family in Flexi BSC
Interfaces • RACApp <-> RAC
• RAC <-> BSC
References -
File based provisioning true
supported
MML Abbreviated Name HTYPE
MML Commands ERC, ERM, ERO
MML Full Name horizon TRX type
Segment Level Parame- -
ter
Table 4 horizonTrxType (Horizon TRX Type) (Cont.)
26 Id:0900d805808686a3 DN0983164
Issue 01A
6.1.1.2 horizon associated TRX ID (HASSO)
Parameter name Horizon Associated TRX ID

Abbreviated name horizonAssociatedTrxId
3GPP name -
Managed Object TRX
Multiplicity 1
Description Horizon Associated TRX ID indicates the TRX ID of
Carrier B when two TRXs are paired, that is, when
CTU2 or CTU2D is used in double density configu-
ration.
The Horizon Associated TRX ID is used when the
Horizon TRX type is Carrier A.
The Horizon Associated TRX ID must be 0 (not
used), if Horizon TRX type is Single, Carrier B or
Multi.
Parameter is valid only for Horizon BTS
Range 1...36
Step 1
Units -
Formula for getting internal_value = gui_value
internal value
Default value 0
Default value notes Not used
Special value Not used (0)
Modified Both Carrier A and Carrier B TRX of the paired
Related parameters horizonTrxType of TRX - When the TRX parameter
Horizon TRX Type is Single, Carrier B or Multi, the
Horizon Associated TRX ID value must be Not used
(0).
horizonEdgeServiceType of TRX - When the
Horizon TRX Type is Carrier A, the values NON-
EDGE, EDGE-POWER, EDGE-CAPACITY and
EDGE are possible.
Related options -
Table 5 horizonAssociatedTrxId (Horizon Associated TRX ID)
DN0983164 Id:0900d805808686a3 27
Issue 01A

• RAC <-> BSC
References -
supported
MML Abbreviated Name HASSO
MML Full Name horizon associated TRX ID
ter
Table 5 horizonAssociatedTrxId (Horizon Associated TRX ID) (Cont.)
6.1.1.3 horizon edge service type (ETYPE)
Parameter name Horizon EDGE Service Type

Abbreviated name horizonEdgeServiceType
3GPP name -
Managed Object TRX
Multiplicity 1
Table 6 horizonEdgeServiceType (Horizon EDGE Service Type)
28 Id:0900d805808686a3 DN0983164
Issue 01A
Description The Horizon EDGE Service Type together with the

Horizon TRX Type parameter defines the EDGE
capabilities of the TRX HW.
Value NON-EDGE is used when the TRX is not
EDGE capable (CTU type is CTU) or when EDGE
is not configured.
Value EDGE is used when EDGE is configured for
a TRX having normal EDGE capabilities (CTU2 or
CTU2D in single density configuration or CTU8m).
In EDGE POWER mode (CTU2 or CTU2D can
operate in this mode in double density configura-
tion) Carrier A is having the Horizon EDGE Service
Type value EDGE-POWER and Carrier B is not
GPRS/EDGE capable (Horizon EDGE Service
Type = NON-EDGE).
In EDGE CAPACITY mode (CTU2D can operate in
this mode in double density configuration) Carrier A
is having Horizon EDGE Service Type value
EDGE-CAPACITY and Carrier B is not EDGE
capable (Horizon EDGE Service Type = NON-
EDGE). In this case it is possible to have GPRS
(CS-3/4) on Carrier B if Carrier A and Carrier B
belong to different BTS objects.
In EDGE ASYMMETRIC mode (CTU2D can
operate in this mode in double density configura-
tion) Carrier A is having the Horizon EDGE Service
Type value EDGE and Carrier B is having the
Horizon EDGE Service Type value EDGE-ASYM-
METRIC.
In NON-EDGE configurations GPRS (CS-3/4) can
be supported on both carriers of CTU2(D).
Range non-EDGE (0), EDGE (1), EDGE-POWER (2),
EDGE-CAPACITY (3), EDGE-ASYMMETRIC (4)
Step -
Units -
internal value non-EDGE ==> 0
EDGE ==> 1
EDGE-POWER ==> 2
EDGE-CAPACITY ==> 3
EDGE-ASYMMETRIC ==> 4
Default value non-EDGE (0)
Table 6 horizonEdgeServiceType (Horizon EDGE Service Type) (Cont.)
DN0983164 Id:0900d805808686a3 29
Issue 01A
Default value notes -

Modified Both Carrier A and Carrier B TRX of the paired
Related parameters horizonTrxType of TRX - 1)
When the Horizon TRX Type is Single or Multi, the
values non-EDGE and EDGE are possible.
Related options -
• RAC <-> BSC
References -
supported
MML Abbreviated Name ETYPE
MML Full Name horizon edge service type
ter
Table 6 horizonEdgeServiceType (Horizon EDGE Service Type) (Cont.)
6.1.1.4 horizon power finetune (HPOFT)
Parameter name Horizon Power Finetune

Abbreviated name horizonPowerFinetune
3GPP name -
Managed Object TRX
Multiplicity 1
Table 7 horizonPowerFinetune (Horizon Power Finetune)
30 Id:0900d805808686a3 DN0983164
Issue 01A
Description With this parameter together with BS Tx Pwr Max or

BS TX Pwr Max1x00 parameters user can identify
the maximum transmission power of the TRX as an
attenuation from the peak power of the TRX.
This parameter is used for frequency bands GSM
900 and GSM1800. The total attenuation for GSM
900 band TRXs is BS Tx Pwr Max (PMAX1) +
Horizon Power Finetune. The total attenuation for
GSM 1800 band TRXs is BS TX Pwr Max1x00
(PMAX2) + Horizon Power Finetune.
This parameter is valid only for Horizon BTS.
Range 0...10
Step 0.2
Units dB
Formula for getting internal_value = gui_value * 5
internal value
Default value 0
Default value notes Not used
Modification On-Line
Modified -
Related parameters bsTxPwrMax of POC - The total attenuation for
GSM 900 band TRXs is BS Tx Pwr Max (PMAX1) +
Horizon Power Finetune.
bsTxPwrMax1x00 of POC - The total attenuation
for GSM 1800 band TRXs is BS TX Pwr Max1x00
(PMAX2) + Horizon Power Finetune.
Related options -
• RAC <-> BSC
References -
supported
MML Abbreviated Name HPOFT
MML Full Name horizon power finetune
Table 7 horizonPowerFinetune (Horizon Power Finetune) (Cont.)
DN0983164 Id:0900d805808686a3 31
Issue 01A

ter
Table 7 horizonPowerFinetune (Horizon Power Finetune) (Cont.)
6.1.2 Modified parameters

This chapter lists the modified parameters introduced with the Horizon BTS at Flexi BSC
Product Family feature.
6.1.2.1 site type (TYPE)
Parameter name Site Type

Abbreviated name bcfType
3GPP name -
Managed Object BCF
Multiplicity 1
Table 8 bcfType (Site Type)
32 Id:0900d805808686a3 DN0983164
Issue 01A
Description With this parameter you identify the type of the BTS
site.
NOTE:
Modification of the BTS site type is possible only
between the 2nd generation and Talk-family site
types and from the 2nd generation or Talk-family
site types to UltraSite site and Talk-family or Ultra-
Site site types to Flexi EDGE type. The modification
from the UltraSite or Flexi EDGE back to the 2nd
generation or Talk-family site types is not possible.
Modification between BTSplus and other site types
is not possible.
Modification from UltraSite or Flexi EDGE site type
to Flexi Multiradio BTS site type is possible but not
vice versa.
It is not allowed to modify the BTS site type of
Horizon BTS to any other or any other BTS site type
to Horizon BTS.
Site type modification is not possible with File
Based Plan Provisioning.
MML NOTE:
B (2nd Generation),
D (Talk-family),
F (PrimeSite),
C (MetroSite),
I (InSite),
P (UltraSite),
E (Flexi EDGE <option>),
X (BTSplus),
M (Flexi Multiradio <option>)
H (Horizon)
NOTE:
Flexi EDGE is available only when the Flexi EDGE
licence state is ON or CONFIG. Flexi Multiradio is
available only when the Flexi Multiradio licence
state is ON or CONFIG.
Range 2nd Generation (0), Talk-family (1), PrimeSite (2),
MetroSite (3), InSite (4), UltraSite (5), Flexi EDGE
(6), BTSplus (7), Flexi Multiradio (8), Horizon (9)
Step -
Table 8 bcfType (Site Type) (Cont.)
DN0983164 Id:0900d805808686a3 33
Issue 01A
Units -
internal value 2nd Generation ==> 0
Talk-family ==> 1
PrimeSite ==> 2
MetroSite ==> 3
InSite ==> 4
UltraSite ==> 5
Flexi EDGE ==> 6
BTSplus ==> 7
Flexi Multiradio ==> 8
Horizon ==> 9
Default value -
Required on creation mandatory
Modified When BCF is locked. The OMU link of the BCF
cannot be in working state when the BTS site type
is modified to UltraSite.
Related parameters -
Related options -
Feature dependencies • BSS21469 BS2xx@Flexi BSC product family
• BSS21403 Flexi Multiradio TRX HW Activation
• Planner <-> RAC
• RAC <-> Optimizer
• RAC <-> BSC
References NSN reference: BSS21403 Flexi Multiradio TRX
HW ActivationNSN reference: Support for Horizon
BTS Family in Flexi BSC Implementation Specifica-
tion
supported
MML Abbreviated Name TYPE
MML Commands EFC, EFM, EFO, EEI
MML Full Name site type
34 Id:0900d805808686a3 DN0983164
Issue 01A

ter
6.1.2.2 BCCH TRX TX pwr reduction (TPR)
Parameter name BCCH TRX TX Pwr Reduction

Abbreviated name transmitPowerReduction
3GPP name -
Managed Object POC
Multiplicity 1
Description With this parameter you can define the amount of
BCCH TRX transmit power reduction.
Valid only when BCCH TRX is UltraSite, Flexi
EDGE, BTSplus, Flexi Multiradio or Horizon BTS.
Range 0...2
Step 2
Units dB
Formula for getting internal_value = gui_value / 2
internal value
Default value 0
Modified -
Related options • Energy saving mode for BCCH TRX (139)
Feature dependencies • BSS20958 Energy saving mode for BCCH TRX
• RAC <-> BSC
HW Activation
supported
MML Abbreviated Name TPR
Table 9 transmitPowerReduction (BCCH TRX TX Pwr Reduction)
DN0983164 Id:0900d805808686a3 35
Issue 01A
MML Commands EUG, EUO, EUC

MML Full Name BCCH TRX TX pwr reduction
ter
Table 9 transmitPowerReduction (BCCH TRX TX Pwr Reduction) (Cont.)
6.1.2.3 transceiver identification (TRX)
Parameter name TRX ID

Abbreviated name id
3GPP name -
Managed Object TRX
Multiplicity 1
Description With this parameter you identify the transceiver.
The value you enter for this parameter must be
unique for each transceiver within one BCF.
NOTE:
The TRX id range for Flexi Multiradio and Horizon
BTS is from 1 to 36, and for BTSplus is from 1 to 32,
and for Flexi EDGE is from 1 to 24 and for other site
types the id range is 1 to 16.
Range 1...36
Step 1
Units -
internal value
Default value -
Modification Not modifiable
Modified -
Related options -
Table 10 id (TRX ID)
36 Id:0900d805808686a3 DN0983164
Issue 01A
Feature dependencies • BSS20744 24 TRX per BCF for Flexi EDGE

BTS
• BSS21469 BS2xx@Flexi BSC product family
• BSS21403 Flexi Multiradio TRX HW Activation
• Planner <-> RAC
• RAC <-> Optimizer
• RAC <-> BSC
HW Activation
supported
MML Abbreviated Name TRX
MML Commands ERC, ERD, ERO
MML Full Name transceiver identification
ter
Table 10 id (TRX ID) (Cont.)
6.1.2.4 PCM port ID 0 (PORT0)
Parameter name PCM Port ID 0

Abbreviated name pcmPortId0
3GPP name -
Managed Object -
Multiplicity 1
Description With this parameter you identify the BSC PCM used
in BTS Abis Port 0 in BTSplus side and Horizon
BTS. PCM of TRX is defined in TRX creation.
Parameter is valid only for BTSplus and Horizon
BTS.
NOTE: At least one of PCM port ID parameters
must be given for BTSplus and Horizon BTS.
Range 0...3391
Step 1
Units -
internal value
Table 11 pcmPortId0 (PCM Port ID 0)
DN0983164 Id:0900d805808686a3 37
Issue 01A
Default value -
Special value PCM port is not used (65535)
Modified When BCF is locked
Related options -
Interfaces • BSC <-> RAC
• RAC <-> RACApp
References -
supported
MML Abbreviated Name PORT0
MML Commands EFC, EFM, EFO
MML Full Name PCM port ID 0
ter
Table 11 pcmPortId0 (PCM Port ID 0) (Cont.)

3GPP name -
Managed Object -
Multiplicity 1
BTS.
38 Id:0900d805808686a3 DN0983164
Issue 01A
Range 0...3391
Step 1
Units -
internal value
Default value -
Related options -
• RAC <-> RACApp
References -
supported
ter

3GPP name -
Managed Object -
Multiplicity 1
DN0983164 Id:0900d805808686a3 39
Issue 01A
BTS.
Range 0...3391
Step 1
Units -
internal value
Default value -
Related options -
• RAC <-> RACApp
References NSN reference: Support for Horizon BTS Family in
Flexi BSC Implementation Specification
supported
ter
40 Id:0900d805808686a3 DN0983164
Issue 01A

3GPP name -
Managed Object -
Multiplicity 1
BTS.
Range 0...3391
Step 1
Units -
internal value
Default value -
Related options -
• RAC <-> RACApp
supported
DN0983164 Id:0900d805808686a3 41
Issue 01A

ter

3GPP name -
Managed Object -
Multiplicity 1
BTS.
Range 0...3391
Step 1
Units -
internal value
Default value -
Related options -
• RAC <-> RACApp
42 Id:0900d805808686a3 DN0983164
Issue 01A

supported
ter

3GPP name -
Managed Object -
Multiplicity 1
BTS.
Range 0...3391
Step 1
Units -
internal value
Default value -
DN0983164 Id:0900d805808686a3 43
Issue 01A
Related options -
• RAC <-> RACApp
References -
supported
ter

3GPP name -
Managed Object -
Multiplicity 1
BTS.
Range 0...3391
Step 1
Units -
internal value
Default value -
44 Id:0900d805808686a3 DN0983164
Issue 01A

Related options -
• RAC <-> RACApp
References -
supported
ter

3GPP name -
Managed Object -
Multiplicity 1
BTS.
Range 0...3391
Step 1
DN0983164 Id:0900d805808686a3 45
Issue 01A
Units -
internal value
Default value -
Related options -
• RAC <-> RACApp
References -
supported
ter
6.1.2.12 bb Unit Supports Edge (BB_UNIT)
Parameter name BB Unit Supports EDGE

Abbreviated name bbUnitSupportsEdge
3GPP name -
Managed Object TRX
Multiplicity 1
Table 19 bbUnitSupportsEdge (BB Unit Supports EDGE)
46 Id:0900d805808686a3 DN0983164
Issue 01A
Description This parameter indicates whether baseband unit

controlling of TRX is capable of supporting EDGE
When defined as non-EDGE the following restric-
tions apply for Horizon BTS:
- TRX does not support A5/3
- No EPCR support if TRX is BCCH TRX
- No AMR-FR support in the associated BTS if the
ACS contains either of TCH-AFS5.9 or TCH-
AFS4.75 rates.
The parameter is only shown in outputs.
Parameter is visible only if the TRX is in a Met-
roSite, UltraSite, Flexi Multiradio or Horizon BTS.
Range Non-EDGE (0), EDGE (1), Unknown (255)
Step -
Units -
internal value Non-EDGE ==> 0
EDGE ==> 1
Unknown ==> 255
Default value Unknown (255)
Required on creation Value set by the system
Modified -
Related options -
Feature dependencies • BSS20872 Robust AMR Signalling
Interfaces • BSC -> RAC
HW Activation
File based provisioning false
supported
MML Abbreviated Name BB_UNIT
MML Commands ERO
MML Full Name bb Unit Supports Edge
Table 19 bbUnitSupportsEdge (BB Unit Supports EDGE) (Cont.)
DN0983164 Id:0900d805808686a3 47
Issue 01A

ter
Table 19 bbUnitSupportsEdge (BB Unit Supports EDGE) (Cont.)
6.1.2.13 2G TRX power down threshold (PWDT)
Parameter name 2G TRX Power Down Threshold

Abbreviated name dtrxPowerDownThreshold
3GPP name -
Managed Object BTS
Multiplicity 1
Description With this parameter user can activate the 2G TRX
Automatic Power Down feature by setting the load
threshold parameter in a value greater than zero.
The threshold parameter indicates the amount of
traffic channels that has to remain idle after TRXs
are powered down.
The actual TRX power down is started if the load in
the segment remains low enough for a period of
time defined by the 2G TRX Power Down Supervi-
sion Period parameter. 2G TRX Power down
threshold must be higher than 2G TRX Power up
threshold if 2G TRX Power down threshold differs
from 0.
This parameter is valid only for Flexi EDGE,
BTSplus, Multiradio BTS and Horizon BTS.
Range 0...255
Step 1
Units -
internal value
Default value 0
Default value notes This feature is not in use as a default.
Modified -
Table 20 dtrxPowerDownThreshold (2G TRX Power Down Threshold)
48 Id:0900d805808686a3 DN0983164
Issue 01A
Related parameters dtrxPowerDownSupervisionPeriod of BSC - TRX

power down is started if the load remains lower than
defined by 2G TRX Power Down Threshold param-
eter for the whole 2G TRX Power Down Supervi-
sion Period.
dtrxPowerUpThreshold of BTS - 2G TRX Power
down threshold must be higher than 2G TRX Power
up threshold
Related options • 2G TRX Automatic Power Down (140)
Feature dependencies • BSS20984 2G TRX Automatic Power Down
• RAC <-> BSC
References -
supported
MML Abbreviated Name PWDT
MML Commands EQM, EQO
MML Full Name 2G TRX power down threshold
Segment Level Parame- true
ter
Table 20 dtrxPowerDownThreshold (2G TRX Power Down Threshold) (Cont.)
6.1.2.14 2G TRX power up threshold (PWUT)
Parameter name 2G TRX Power Up Threshold

Abbreviated name dtrxPowerUpThreshold
3GPP name -
Managed Object BTS
Multiplicity 1
Table 21 dtrxPowerUpThreshold (2G TRX Power Up Threshold)
DN0983164 Id:0900d805808686a3 49
Issue 01A
Description With this parameter user can define the amount of

traffic channels which has to remain free in the
segment when TRXs have been powered down by
the 2G TRX Automatic Power Down feature. When
the number of free traffic channels decreases
below this threshold value then TRXs are powered
up.
2G TRX Power down threshold must be higher than
2G TRX Power up threshold if 2G TRX Power down
threshold differs from 0.
This parameter is valid only for Flexi EDGE,
BTSplus, Multiradio BTS and Horizon BTS.
Range 0...254
Step 1
Units -
internal value
Default value 4
Default value notes 4 traffic channels
Modified -
Related parameters dtrxPowerDownThreshold of BTS
- 2G TRX Power down threshold must be higher
than 2G TRX Power up threshold.
• RAC <-> BSC
References -
supported
MML Abbreviated Name PWUT
MML Commands EQM, EQO
MML Full Name 2G TRX power up threshold
Segment Level Parame- true
ter
Table 21 dtrxPowerUpThreshold (2G TRX Power Up Threshold) (Cont.)
50 Id:0900d805808686a3 DN0983164
Issue 01A
6.1.2.15 TRX DDU association (DDU)
Parameter name TRX DDU Association

Abbreviated name trxDDUAssociation
3GPP name -
Managed Object TRX
Multiplicity 1
Description Output parameter which defines DDU association
of Flexi EDGE, BTSplus, Flexi Multiradio and
Horizon TRX. TRX can be server, slaver, indepen-
dent or not applicable.
MML NOTE: The parameter is only shown in
outputs.
Additional information This parameter is valid only for Flexi EDGE,
BTSplus, Flexi Multiradio and Horizon BTSs.
Range server (0), slave (1), independent (2), not applica-
ble (255)
Step -
Units -
internal value server ==> 0
slave ==> 1
independent ==> 2
not applicable ==> 255
Default value not applicable (255)
Default value notes not applicable
Modified -
HW Activation
supported
Table 22 trxDDUAssociation (TRX DDU Association)
DN0983164 Id:0900d805808686a3 51
Issue 01A
MML Abbreviated Name DDU

MML Commands ERO
MML Full Name TRX DDU association
ter
Table 22 trxDDUAssociation (TRX DDU Association) (Cont.)
6.1.2.16 Server TRX Id (-)
Parameter name Server TRX Id

Abbreviated name serverTRXId
3GPP name -
Managed Object TRX
Multiplicity 1
Description Output parameter which defines which Flexi EDGE,
BTSplus, Flexi Multiradio and horizon TRX is server
of this TRX in DDU association. Only slave TRXs
have this information.
MML NOTE: The parameter is only shown in
outputs.
Additional information This parameter is valid only for Flexi EDGE,
BTSplus, Flexi Multiradio and Horizon BTSs.
Range 1...36
Step 1
Units -
internal value
Default value 255
Default value notes Only slave TRXs have this information.
Special value Other TRXs than slaves uses this value. (255)
Modified -
Related parameters trxDDUAssociation of TRX - TRX DDU Association,
Only slave has this information.
Table 23 serverTRXId (Server TRX Id)
52 Id:0900d805808686a3 DN0983164
Issue 01A

HW Activation
supported
MML Abbreviated Name -
MML Commands ERO
MML Full Name Server TRX Id
ter
Table 23 serverTRXId (Server TRX Id) (Cont.)
DN0983164 Id:0900d805808686a3 53
Issue 01A
6.2 MML commands

The Horizon BTS implementation to the BSC affects some of the mml commands.
Results of the command entering are different in order to include Horizon BTS to the
system.
6.2.1 EE MML commands
6.2.1.1 EEI - OUTPUT RADIO NETWORK CONFIGURATION

New parameter value of site type from BCF object is outputted in case of Horizon
BTS site type in execution of MML command EEI printout.
Example:
6.2.2 EF MML commands
6.2.2.1 EFC - CREATE BASE CONTROL FUNCTION

New parameter value of site type is allowed in case of Horizon BTS site type cre-
ation.
Example:
BASE CONTROL FUNCTION BCF-0020 CREATED
SITE TYPE ............................ H - HORIZON
ADMINISTRATIVE STATE ................. LOCKED
OPERATIONAL STATE .................... BL-USR
54 Id:0900d80580890729 DN0983164
Issue 01A
D-CHANNEL LINK SET 100 ............. OM50 -

OUTPUT 1 ....................... OFF TEXT ID -
INPUT 1 ..............ROUTE: NOT REPORT

POLARITY: OPEN SEVERITY: * TEXT ID -
.
.
.
.INPUT 24 ..............ROUTE: NOT REPORT
POLARITY: OPEN SEVERITY: * TEXT ID -
RX DIFFERENCE LIMIT ..........(RXDL).. 10 dB

BTS BATTERY BACKUP PROCEDURE .(BBU)... ALL
TRX SHUTDOWN TIMER ...........(NTIM).. 0 min
TRX SHUTDOWN TIMER2 ..........(NTIM2). 0 min
BCCH TRX SHUTDOWN TIMER ......(BTIM).. 0 min
MASTER CLOCK BCF .............(MCBCF). --
CLOCK SOURCE .................(CS).... --
SYNCHRONIZATION ENABLED ......(SENA).. F
SYNCHRONIZATION MODE .........(SM).... UNSYNCH
AUTOMATIC UNLOCK ALLOWED .....(AU).... T
FACCH LAPDM T200 .............(T200F). 0 (BCF PREDEFINED VALUES)
SDCCH LAPDM T200 .............(T200S). 0 (BCF PREDEFINED VALUES)
ABIS OVER IP ETHERNET USAGE ..(TRS1).. 0 (NOT IN USE)
ADDITIONAL 2 E1/T1 USAGE .....(TRS2).. 0 (NOT IN USE)
TRS ABIS GROOMING USAGE ......(TRS3).. 0 (NOT IN USE)
TRS LOOP PROTECTION USAGE ....(TRS4).. 0 (NOT IN USE)
6.2.2.2 EFM - MODIFY BASE CONTROL FUNCTION PARAMETERS

New parameter value of site type is allowed in case of Horizon BTS site type modi-
fication in execution printout of MML command EFM.
g Note
The printout is similar to the ZEFC command.
DN0983164 Id:0900d80580890729 55
Issue 01A
6.2.2.3 EFO - OUTPUT BASE CONTROL FUNCTION PARAMETERS

New parameter value of site type is outputted in execution printout of MML command
EFO.
Example:
EFO:1;
BSC DX220-LAB 2011-06-02 04:02:13
BASE CONTROL FUNCTION BCF-0001 DATA

SITE TYPE ............................ H - HORIZON
ADMINISTRATIVE STATE ................. LOCKED
OPERATIONAL STATE .................... BL-USR
D-CHANNEL LINK SET 200 ............. OM100 WO-EX
RX DIFFERENCE LIMIT ..........(RXDL).. 10 dB
BTS BATTERY BACKUP PROCEDURE .(BBU)... ALL
TRX SHUTDOWN TIMER ...........(NTIM).. 0 min
BCCH TRX SHUTDOWN TIMER ......(BTIM).. 0 min
FACCH LAPDM T200 .............(T200F). 0 (BCF PREDEFINED VALUES)
SDCCH LAPDM T200 .............(T200S). 0 (BCF PREDEFINED VALUES)
PCM PORT ID 0 ................(PORT0). 5
PCM PORT ID 1 ................(PORT1). ND (NOT DEFINED)
BTS UNDER THIS BCF ARE:
SEG-0001
BTS-0001 SECTOR-001 ..... LOCKED
SEG-0005
COMMAND EXECUTED
56 Id:0900d80580890729 DN0983164
Issue 01A
6.2.3 EW MML commands
6.2.3.1 EWL - SET LIST EXISTING BCF SOFTWARE BUILDS

when list of existing SW build is outputted with MML command EWL.
Example:
6.2.3.2 EWO - LIST SOFTWARE CONFIGURATION OF BCF

No BTS site type specific information.
6.2.3.3 EWP - MML LIST BCF SOFTWARE BUILD CONTENTS

New parameter value of site type is used in build id and build type in case of Horizon
when list of SW build content is outputted with MML command EWP.
Example:
EWP:ID=1,:;
EXECUTION STARTED
BSC3i ESPOO6 2011-06-09 15:11:32
SOFTWARE BUILD CONTENTS
BUILD ID ................................ 1
BUILD TYPE .............................. H
RELEASE VERSION ......................... 0.14-4
DN0983164 Id:0900d80580890729 57
Issue 01A
MASTER FILE NAME ........................ BTS_000E.040

MASTER FILE VERSION ..................... 0.14-4
BUILD SUBDIRECTORY ...................... /PACK_4
FILE NAME VERSION DATE TYPE UNIT
---------------------------------------------------------------
BTS_000E.040 0.14-4 23/03/11 MF BTS
BOOT1 .MOT 0.14-4 22/03/11 BO
BOOT2 .MOT 0.14-4 22/03/11 BO
OOBJ .MOT 0.0-0 17/12/10 DA
BBU-SW .MOT 0.14-4 23/03/11 RU
SC2-FM .MOT 0.14-4 23/03/11 RU
BBUBTROM.MOT 1.0-7 27/10/09 BO
SC2-OAM .MOT 0.14-4 23/03/11 RU
BBU-BOOT.MOT 0.14-2 09/03/11 BO
CTU-RSS .MOT 0.14-4 23/03/11 RU
CTU2-RSS.MOT 0.14-4 23/03/11 RU
FM .MOT 0.14-4 23/03/11 RU
OAM .MOT 0.14-4 23/03/11 RU
CTU-FW .MOT 0.14-4 23/03/11 FW
CTU2-FW .MOT 0.14-4 23/03/11 FW
SC2-BOOT.MOT 0.14-4 22/03/11 BO
CTU-ENC1.MOT 0.0-0 22/06/04 FW
CTU-ENC2.MOT 0.0-0 22/06/04 FW
CTU-ENC3.MOT 1.0-12 23/04/10 FW
NIU1 .MOT 1.0-5 20/08/09 FW
NIU2 .MOT 0.0-13 09/02/11 FW
CTU41 .MOT 0.0-3 11/11/10 FW
CTU2ENC1.MOT 6.0-3 15/04/04 FW
CTU2ENC2.MOT 1.0-8 25/11/09 FW
CTU42 .MOT 0.0-3 11/11/10 FW
BBU-FW2 .MOT 1.0-4 10/07/09 FW
SC2BTROM.MOT 1.0-7 27/10/09 BO
SC2-FW1 .MOT 1.0-12 26/04/10 FW
SC2-FW2 .MOT 1.0-5 20/08/09 FW
NIU3 .MOT 1.0-10 15/01/10 FW
CTU4ENC1.MOT 0.0-4 17/03/09 FW
CTU4ENC2.MOT 0.0-4 17/03/09 FW
BBU-FW1 .MOT 1.0-12 21/04/10 FW
BBU-FW3 .MOT 0.14-4 22/03/11 FW
58 Id:0900d80580890729 DN0983164
Issue 01A
CTU2ENC3.MOT 1.0-8 25/11/09 FW

CTU4ENC3.MOT 1.0-2 02/06/09 FW
LIST1 .MOT 0.14-4 23/03/11 RU
LIST2 .MOT 0.14-4 23/03/11 RU
LIST3 .MOT 0.14-4 23/03/11 RU
COMMAND EXECUTED
6.2.3.4 EWS - SET OR REMOVE INITIAL SOFTWARE BUILD

BTS. BTS site type in printout when setting or removing initial SW build in MML
command EWS.
Example
EWS:H:1:;
EXECUTION STARTED
INITIAL SOFTWARE BUILD SET
SITE TYPE .................................... HORIZON

BUILD ID ..................................... 1
COMMAND EXECUTED
6.2.4 ER MML commands
6.2.4.1 ERC - CREATE TRANSCEIVER

New parameters are taken into account when creating TRX.
DN0983164 Id:0900d80580890729 59
Issue 01A
Example:
6.2.4.2 ERM - MODIFY TRANSCEIVER

New parameters are taken into account while modifying TRX.
Example:
Syntax ERM:
( BTS = <BTS identification> |
NAME = <BTS name> ),
TRX = <transceiver identification> :
60 Id:0900d80580890729 DN0983164
Issue 01A
[[ PREF = <preferred BCCH TRX> | def=N ]

...
...
[[ DTRX = <dual TRX usage> <option> | def = 0 ]
[ SDG = <TRX shutdown group> <option> ]]:
[[ HTYPE = <Horizon TRX Type> | def = 0],
[ HASSO = <Horizon Associated TRX Id> | def = 0],
[ ETYPE = <Horizon EDGE Service Type> | def = 0],
[ HPOFT = <Horizon Power Finetune> | def = 0]]... ;
6.2.4.3 ERO - OUTPUT TRANSCEIVER PARAMETERS

New parameters service type, associated TRX id and Carrier TRX are taken into
account when printing TRX parameters.
Example:
Single TRX association
DN0983164 Id:0900d80580890729 61
Issue 01A
Carrier A association
62 Id:0900d80580890729 DN0983164
Issue 01A
Carrier B association
DN0983164 Id:0900d80580890729 63
Issue 01A
Multi association
64 Id:0900d80580890729 DN0983164
Issue 01A
6.3 Alarms
The range of BTS external alarms is expanded due to Horizon BTS migration to the
BSC.
The range of supported alarms can be found in the Alarm Handling and BSS Field Trou-
bleshooting document.
DN0983164 Id:0900d80580890727 65
Issue 01A
6.4 Measurements and counters

There are no measurements or counters related to this feature.
66 Id:0900d80580898582 DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family Activating and configuring the feature
7 Activating and configuring the feature

The detailed instructions for configuring the Horizon BTS at Flexi BSC Product Family
feature can be found in the Radio Network Administration document in the Nokia
Siemens Networks GSM/EDGE BSS, rel. RG10(BSS), operating documentation.
This chapter shows changes in current configuring procedure due to adding Horizon
BTSs to the Flexi BSC.
The example configuration of the following network elements is shown in the sub-chap-
ters:
• LAPD multiplexed configuration,
• BCF creation,
• BTS creation,
• TRX creation,
• RNW configuration.
7.1 LAPD multiplexed configuration
7.2 BCF creation

Creating BCF with:
• identification number: 1
• D-channel link set name: LNKO
• PCM Port ID 0: 511
DN0983164 Id:0900d8058086921a 67
Issue 01A
Activating and configuring the feature Horizon BTS at Flexi BSC Product Family
• site type: Horizon BTS
68 Id:0900d8058086921a DN0983164
Issue 01A
Example
The parameter settings for BFC creation:
DN0983164 Id:0900d8058086921a 69
Issue 01A
70 Id:0900d8058086921a DN0983164
Issue 01A
7.3 BTS creation

Creating BTS-1 into the BSDATA. Default values are used for other BTS parameters.
DN0983164 Id:0900d8058086921a 71
Issue 01A
Example
The BTS GPRS parameter settings:
72 Id:0900d8058086921a DN0983164
Issue 01A
7.4 TRX creation

Creating a TRX-1 under BTS-1 with the following parameter values:
• dynamic Abis pool id: 2
• frequency: 60,
• training sequence code: 0
• PCM-TSL: 511-1
• D-channel telecom link set name: LNK1
DN0983164 Id:0900d8058086921a 73
Issue 01A
• CH0: MBCCHC.
74 Id:0900d8058086921a DN0983164
Issue 01A
Example
The TRX parameter settings:
DN0983164 Id:0900d8058086921a 75
Issue 01A
7.4.1 TRX: EDGE - ASYMMETRIC mode creation

Creating a TRX-2 under BTS-1 with the following parameter values:
• GTRX: N
• frequency: 64
• training sequence code: 0
• PCM-TSL: 511-3
• D-channel telecom link set name: LINK2
76 Id:0900d8058086921a DN0983164
Issue 01A
• horizon TRX type:2

• horizon associated TRX ID: 0
• horizon edge service type: 4
DN0983164 Id:0900d8058086921a 77
Issue 01A
Example:
78 Id:0900d8058086921a DN0983164
Issue 01A
DN0983164 Id:0900d8058086921a 79
Issue 01A
7.5 RNW configuration

Output of the network under BTS-1:
80 Id:0900d8058086921a DN0983164
Issue 01A
Horizon BTS at Flexi BSC Product Family Abbreviations
8 Abbreviations
0–Z
BCF Base Control Function

BTS Base Transceiver Station
Carrier A The another ('master') TRX of coupled TRXs in the case of
CTU2/2D.
Carrier B The another ('slave') TRX of coupled TRXs in the case of
CTU2/2D.
CCCH Common Control Channel
CTU Old radio unit type in Horizon BTS
CTUx Common term for all CTU types
CTU2/2D Radio unit type with 2 logical TRXs at maximum
CTU8m Radio unit type with up to 8 logical TRXs
EGPRS Enhanced GPRS
EPCR EGPRS Packet Channel Request
GPRS General Packet Radio Service
GSR GSM Software Release
Horizon BTS Product family name for all GSR BTS variants which are
supported by Flexi BSC product.
LAPD Link Access Procedure D channel
PCCH Packet control channel
PCU Packet Control Unit
PCU2 Second generation Packet Control Unit
POC Power Control
RSR RAN Software Release
TRAU Transcoder and Rate Adaptation Unit
DN0983164 Id:0900d8058089054c 81
Issue 01A

Horizon at Flexibsc dn0983164 01A en

Uploaded by

Copyright:

Available Formats

You might also like

Horizon at Flexibsc dn0983164 01A en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Horizon at Flexibsc dn0983164 01A en

Uploaded by

Copyright:

Available Formats

GSM/EDGE BSS, Rel.

Horizon BTS at Flexi BSC Product Family

f Important Notice on Product Safety

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

6.1.2.7 PCM port ID 3 (PORT3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7 Activating and configuring the feature. . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Network architecture (4.1)

BSS Abis interface (4.2)

Operation and maintenance (4.3)

System impacts (5)

MML commands (6.2)

Activating and configuring the feature (7)

1.2 Network elements

3.1 Software requirements

Network element Required software release

Table 1 Software requirements

3.2 Hardware requirements

4.1 Network architecture

Figure 1 Network architecture

4.1.1 Horizon BTS product family overview

• Horizon II family (Horizon II macro, Horizon II mini and Horizon II micro),

Horizon BTS Unit type Working Supported Number BSC con-

Table 2 Horizon BTS product family overview

4.1.2 Horizonmacro Indoor

4.1.3 Horizonmacro Outdoor

4.1.4 Horizonmacro 12 Carrier Outdoor

4.1.5 Horizon II macro

4.1.6 Horizon II macro Outdoor Lite enclosure

4.1.7 Horizon II macro DC Outdoor enclosure

4.1.8 Horizon II mini (Outdoor enclosure)

4.1.9 Horizon II micro

4.1.10 Horizon 2G-nx BBU

4.2 BSS Abis interface

4.2.1 Abis interface transport

Abis transport topologies

Abis timeslot allocation

4.2.2 Abis interface configuration

4.3 Operation and maintenance

5.1 Relation to other features

BSS7020: Intelligent shutdown with timer control

BSS4040: Satellite Abis

BSS20540: Remote MMI

• EDGE-ASYMMETRIC mode - the TRXs of CTU2/CTU2D have different EDGE

BSS10045: Dynamic Abis

BSS07078: Local object blocking

BSS20817: End to End Downlink Abis Performance Monitor

BSS20760: BTS ID shown in BTS Manager

BSS20151: Adjustable Intelligent Shutdown

BSS20984: 2G TRX Automatic Power Down

BSS21261: 2G TRX Manual Power Down

BSS20093: A5/3 Ciphering

BSS7003: High Speed Circuit Switched Data

BSS7037: 14.4 kbit/s GSM data services

BSS07036: Dynamic SDCCH Allocation

CS1 CTU CTU2 CTU2D CTU8m

Table 3 Supported code rates

BSS5010: Half Rate