GSM/EDGE BSS, Rel.
RG30(BSS), Operating
Documentation, Issue 05
BSC/TCSM description
Multicontroller BSC and
Multicontroller Transcoder
Product Description
DN0947925
Issue 02B
Approval Date 2014-01-31
Confidential
Multicontroller BSC and Multicontroller Transcoder
Product Description
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 Solutions and 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 Solutions and
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 Solutions
and 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 Solutions and Networks and the customer.
However, Nokia Solutions and 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 Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks,
explain issues which may not be covered by the document.
Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN
NO EVENT WILL Nokia Solutions and 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.
NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia
Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright © 2014 Nokia Solutions and Networks. 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.
Nokia Solutions and 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 Solutions and Networks for any additional information.
2
Id:0900d80580a56487
Confidential
DN0947925 Issue 02B
Multicontroller BSC and Multicontroller Transcoder
Product Description
Table of Contents
This document has 60 pages.
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
DN0947925
1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.2
2.2.1
Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Functionality of the mcBSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
General functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Data and messaging services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Operability, capacity, quality, and value added services . . . . . . . . . . . . 14
Support for smart device friendly GSM networks. . . . . . . . . . . . . . . . . . 18
Functionality of the mcTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Advanced functionality of the mcTC . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3
3.1
3.2
3.2.1
3.3
3.4
3.5
3.6
3.7
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
A over IP (AoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Packet Abis over IP/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Packet Abis / TDM – Packet Abis Network media conversion. . . . . . . . 26
Packet Ater over IP/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Gb over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Lb over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
O&M over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
CBC interface (BSC - CBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.2
4.3
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
4.4.7
4.4.8
mcBSC and mcTC architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Functional architecture of the mcBSC . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Multicontroller BSC signaling unit (BCXU). . . . . . . . . . . . . . . . . . . . . . . 29
Packet control unit for Multicontroller (PCUM). . . . . . . . . . . . . . . . . . . . 29
Ethernet transmission processing for Multicontroller (ETM) . . . . . . . . . 29
Marker and cellular management unit (MCMU) . . . . . . . . . . . . . . . . . . . 30
Operation and maintenance unit (OMU) . . . . . . . . . . . . . . . . . . . . . . . . 30
Functional architecture of the mcTC . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
mcBSC and mcTC hardware architecture . . . . . . . . . . . . . . . . . . . . . . . 31
External physical interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Gigabit Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
LAN/Ethernet for O&M interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
SW download and SW debugging interfaces. . . . . . . . . . . . . . . . . . . . . 34
Serial Port interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
External Alarm interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
External Telecom Synchronization interface . . . . . . . . . . . . . . . . . . . . . 34
External HD cross connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
External Packet Synchronization Interfaces . . . . . . . . . . . . . . . . . . . . . 34
5
mcBSC and mcTC software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6
6.1
6.2
Connectivity and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
mcBSC connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
mcTC connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Id:0900d80580a56487
Confidential
3
Multicontroller BSC and Multicontroller Transcoder
Product Description
4
6.3
Traffic handling capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7
7.1
7.2
7.2.1
7.2.2
7.2.3
7.2.4
7.3
7.3.1
7.4
Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
mcBSC and mcTC module types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
mcBSC basic modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
mcBSC TRX extension module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
mcBSC PS data extension module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
mcTC basic module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
mcBSC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Standalone mcBSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
mcTC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8
8.1
8.2
8.3
8.4
8.5
8.6
Mechanical design and power supply system. . . . . . . . . . . . . . . . . . . . . 45
Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Cabinet installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Cooling of the modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Cooling in rack installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Electrical specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
9
9.1
9.2
9.3
Reliability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Overload protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Redundancy principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
10
10.1
10.2
10.3
Operational environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Standards for environmental requirements . . . . . . . . . . . . . . . . . . . . . . . 54
Conditions during operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Conditions during transportation and storage . . . . . . . . . . . . . . . . . . . . . 60
Id:0900d80580a56487
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
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
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Figure 19
Figure 20
Figure 21
Figure 22
Figure 23
DN0947925
Multicontroller BSC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
mcBSC interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
AoIP with transcoder located in BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
AoIP with transcoder located in core network . . . . . . . . . . . . . . . . . . . . 25
Packet Abis over IP/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Packet Ater over IP/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Functional architecture of the mcBSC . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Functional architecture of the mcTC . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Physical interfaces of controller module . . . . . . . . . . . . . . . . . . . . . . . . 32
The mcBSC and the mcTC software platform . . . . . . . . . . . . . . . . . . . . 35
mcTC connectivity steps with BCN-A hardware . . . . . . . . . . . . . . . . . . 38
Compact Multicontroller BSC module used to build mcBSC configurations
40
mcBSC basic modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
mcBSC TRX extension module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
mcBSC PS data extension module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
mcTC basic module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Standalone Multicontroller BSC capacity steps with BCN-B hardware . 43
Standalone mcBSC network configuration . . . . . . . . . . . . . . . . . . . . . . 44
Front view of the module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Rear view of the module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
CAB216-A cabinet (empty and fully equipped with eight BCN modules and
two PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Controller module, rear side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Rear view of AC and DC power supply modules . . . . . . . . . . . . . . . . . . 48
Id:0900d80580a56487
Confidential
5
Multicontroller BSC and Multicontroller Transcoder
Product Description
List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 9
Table 10
Table 11
Table 12
Table 13
Table 14
Table 15
Table 16
Table 17
Table 18
Table 19
6
Interface specifications for network connections and element
management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Interface specifications for connections to be used either for module interconnects or network connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
mcBSC capacity steps with BCN-A hardware . . . . . . . . . . . . . . . . . . . . 36
mcBSC capacity steps with BCN-B hardware . . . . . . . . . . . . . . . . . . . . 37
CS processing capacity of the mcBSC with nominal call mix . . . . . . . . 39
CAB216-A cabinet technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
AC power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
DC power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Redundancy princples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
The predicted availability, mean down time (MDT) and mean operating
time between system failures (MTBFNE) for the complete system . . . . . 52
The predicted availability, mean down time (MDT) and mean operating
time between system failures (MTBFNE) for the complete system . . . . . 52
The predicted availability, mean down time (MDT) and mean operating
time between system failures (MTBFNE) for the complete system . . . . . 53
ETSI standards defining the environmental requirements for the network
elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
IEC standards defining the environmental requirements for the network
elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Limits for temperature and humidity during operation . . . . . . . . . . . . . . 56
Chemically active substances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Mechanical conditions allowed during operation . . . . . . . . . . . . . . . . . . 59
Temperature limits during transportation . . . . . . . . . . . . . . . . . . . . . . . . 60
Mechanical stress allowed during transportation . . . . . . . . . . . . . . . . . . 60
Id:0900d80580a56487
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Summary of Changes
Summary of Changes
Changes between issues 02B(2014/01/22, RG30(BSS)) and 02A(2012/07/24,
RG30(BSS))
Overview (1)
•
The chapter has been updated due to introduction of Multicontroller module HW
variant BCN-B and related functionalities.
Functionality of the mcBSC (2.1)
•
The Smart Resource Adaptation (SRA), Precise Paging, and Enhanced packet
scheduling features have been added to the 2.1.4 Support for smart device friendly
GSM networks chapter.
mcBSC and mcTC architecture (4)
•
The chapter 4.4 External physical interfaces has been updated due to introduction
of Multicontroller module HW variant BCN-B and related functionalities.
mcBSC connectivity (6.1)
•
The chapter has been updated due to introduction of Multicontroller module HW
variant BCN-B and related functionalities.
mcTC connectivity (6.2)
•
The chapter has been updated due to introduction of Multicontroller module HW
variant BCN-B and related functionalities.
Traffic handling capacity (6.3)
•
The chapter has been updated due to introduction of Multicontroller module HW
variant BCN-B and related functionalities.
Configurations (7)
•
The chapter has been updated due to introduction of Multicontroller module HW
variant BCN-B and related functionalities.
Mechanical design and power supply system (8)
•
The chapter has been updated due to introduction of Multicontroller module HW
variant BCN-B and related functionalities.
Reliability (9)
•
The chapter has been updated due to introduction of Multicontroller module HW
variant BCN-B and related functionalities.
Changes between issues 02A(2012/07/24, RG30(BSS)) and 02(2012/06/04,
RG30(BSS))
Functionality of the mcBSC (2.1)
•
The information regarding Dynamic PCU2 Pooling has been added updated in the
section PCU2 pooling.
mcBSC and mcTC architecture (4)
•
DN0947925
Name of the units in figure 7 has been corrected. The section on Element Management 1GigE Interface has been removed.
Id:0900d80580a56438
Confidential
7
Summary of Changes
Multicontroller BSC and Multicontroller Transcoder
Product Description
Changes between issues 02(2012/06/04, RG30(BSS)) and 01B(2011/03/08,
RG20(BSS))
Functionality of the mcBSC (2.1)
•
The information regarding Dynamic PCU2 Pooling has been added updated in thesection PCU2 pooling.
Changes made between issues 01B and 01A
8
Id:0900d80580a56438
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Overview
1 Overview
The huge growth of traffic in the recent years and even more rapid growth expected in
the coming years with needed future-proof network evolution capabilities towards new
technologies has brought new challenges to the radio networks elements. To satisfy
current and future needs, NSN has developed a novel, compact and highly scalable Multicontroller Platform, which enables operators to provide the needed capacity in an unrivaled footprint.
The Multicontroller BSC (mcBSC) application on top of new platform design is aimed to
increase the flexibility and versatility protecting operator’s investments. mcBSC also
includes transcoder implementation, the Multicontroller Transcoder (mcTC), as a functional part of the mcBSC. The mcBSC and mcTC hardware is based on the latest component technology which enabled extremely high packing density. As a result of the
modular and revolutionary processor architecture, the capacity, connectivity and functionality can be efficiently scaled to match the network and end-user needs in a flexible,
fast and cost efficient way.
The mcBSC provides highly scalable connectivity for voice and data applications. It
provides market leading capacity with 4400 TRXs and 26400 Erlangs. It is fully optimized to most modern and efficient IP transmission solutions.
Figure 1
Multicontroller BSC module
This document provides a general overview of the mcBSC and mcTC. The overview
describes briefly the mcBSC and the mcTC functionality and architecture. In addition,
some basic information of hardware configuration, network interfaces, performance and
operating environmental topics are provided.
DN0947925
Id:0900d80580a5643a
Confidential
9
Functionality
Multicontroller BSC and Multicontroller Transcoder
Product Description
2 Functionality
2.1
Functionality of the mcBSC
The mcBSC manages a variety of tasks ranging from channel administration to short
messaging service. The most important basic and optional functionalities are explained
briefly below. Activation of optional functionalities requires a valid license in mcBSC. For
more details, see BSS feature descriptions.
2.1.1
General functionalities
Call control
Basic Call provides speech and data services to the mobile subscriber by offering the
means for establishing speech calls with half or full rate or data calls with full rate radio
channels.
Management of radio channels
•
•
•
•
•
Management of common signaling of traffic channel configurations
Management of traffic channels (TCH) and standalone dedicated control channels
(SDCCH):
• Resource management
• Channel allocation
• Link supervision
• Channel release
• Power control
Management of broadcast control channels (BCCH) and common control channels
(CCCH):
• Random access
• Access grant
• Paging
• System information broadcast
Management of frequency hopping which enables effective use of radio resources
and enhanced voice quality for GSM subscriber
Handovers
Existing handover types are:
• Intra-BSC, intra-cell (both intra-TRX and inter-TRX), which means that the
handover takes place within the area controlled by the BSC and the mobile stays
in the same cell
• Intra-BSC, inter-cell, which means that the mobile stays in the area of the BSC
but moves from one cell to another
• Inter-BSC, both outgoing and incoming, which means that the mobile moves into
the area of another BSC
The handover threshold comparison includes the evaluation of uplink/downlink level,
quality and interference, MS-BTS distance evaluation, the evaluation of a rapid field
drop, the detection of a fast/ slow-moving mobile station (MS), the detection of a turnaround-corner MS, power budget evaluation, and umbrella handover evaluation. If two
10
Id:0900d80580a5643d
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Functionality
or more criteria for a handover are present simultaneously, the handover is done according to the priority order.
GPRS/EDGE packet data handling
•
•
•
•
•
•
•
Connection establishment and management
Resource allocation
Scheduling
Data transfer
MS uplink power control
Gb load sharing (uplink)
Flow control (downlink)
Maintenance
The mcBSC offers the possibility for the following maintenance procedures:
•
•
•
•
Fault localization for the mcBSC
Reconfiguration of the mcBSC
Reconfiguration support to the BTS
Updating of the software in the mcBSC, Multicontroller TC (mcTC), and BTS
Operation
During normal operation, the mcBSC offers various possibilities for the operator:
•
•
•
•
Modification of the parameters of the mcBSC and the BTS
Modification of the radio network parameters
Configuration of the mcBSC hardware
Administration of the mcBSC equipment
Measurements and observations
To run the network effectively, that is, to minimize costs and maximize service quality to
the subscriber, the information on the performance and service level of the mcBSC and
the radio network is needed. It is useful to know how much traffic different cells carry,
whether there is congestion on the SDCCH or TCH channels, and how many handovers
are successful and how many fail. Traffic measurements provide this information.
The mcBSC measures traffic, observes signaling events, and traces a specific call. It
then forwards these results to NetAct for further processing. It allows to select measurements, needed at a particular time. mcBSC measurements are independent of one
another even though they are handled through the same user interface.
For more information on the measurements and observations of the mcBSC see the
Counters/performance indicators section of the BSC documentation set.
2.1.2
Data and messaging services
General packet radio service (GPRS)
GPRS gives customers the benefits of instant IP connectivity on-the-move and of being
continuously connected. GPRS provides the possibility of being charged only for transferred data in addition to more efficient use of limited air interface resources.
GPRS provides packet radio access for a GSM/GPRS mobile. The benefit of GPRS is
that it can use the same resources as circuit-switched connections by sharing the
DN0947925
Id:0900d80580a5643d
Confidential
11
Functionality
Multicontroller BSC and Multicontroller Transcoder
Product Description
overhead capacity. This means that one mobile uses the resources only for a short
period of time, that is, when there is data to be sent or received. Resource sharing
together with a very fast method of reserving radio channels makes the air interface
usage even more efficient. GPRS coding schemes CS1-CS4 are supported.
Enhanced Data rates for GSM Evolution (EDGE)
EDGE, introduced in GSM/GPRS standard Release 99, boosts GSM/GPRS network
capacity and data rates to meet the demands of wireless multimedia applications and
mass market deployment. NSN EDGE Solution includes GPRS/EDGE for packet
switched data.
EDGE uses 200 kHz radio channels, which are the same as the current GSM channel
widths. From a technical perspective, EDGE BSS allows the GSM and GPRS core
network to offer a set of new radio access bearers. EDGE is designed to improve
spectral efficiency through efficient link utilization with GMSK and 8-PSK modulation
schemes, which can be alternated on the same radio slot according to radio channel
conditions. With new modulation, EDGE increases the radio interface data throughput
threefold on average compared to GPRS.
Available EDGE Modulation and Coding Schemes MCS1-MCS9 provide optimal performance in all radio conditions.
Multipoint Gb interface
Multipoint Gb interface enables one packet control unit (PCU) or PCU pool to be connected to several SGSNs. This enhances the resilience of the system and provides the
possibility of distributing the traffic load between the SGSNs. Different users in the same
PCU can be connected to different SGSNs according to their load conditions.
A PS pool area defines a group of PCUs, where an MS roams without the need to
change the serving SGSN node. This reduces the need for signaling when, for example,
an MS moves between the city centre and suburban areas within a single pool area.
Multipoint Gb interface improves scalability and fault protection in the core network and
thus leads to savings in capital expenditure. In case of failures in the GPRS core, the
network remains operational with reduced SGSN capacity. Multipoint Gb interface also
facilitates easy core network element upgrades and helps the operator to maintain
revenue and increase end-user service quality.
Extended cell for GPRS/ EDGE
Extended cell for GPRS/EDGE enables the use of GPRS/EDGE traffic in the extended
radio coverage area of an extended cell. Traffic for a mobile station is supported so that
the mobile station can move between coverage areas of the cell without breaking data
connections. Depending on the configuration of the cell, packet services can be
provided up to 70 km from the BTS site. Super extended cell for GPRS/EDGE further
enhances the cell radius up to 105 km.
Circuit Switched Data services
The mcBSC with mcTC supports the following bearer services, including both transparent and nontransparent data services, defined in GSM Specification ETS 300 904 with
applicable ETSI/3GPP specifications:
•
•
•
12
Data Circuit Duplex (300-14400 bit/s) transparent/non-transparent
High Speed Circuit Switched Data
14.4 kbits/s Data Traffic Channel
Id:0900d80580a5643d
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
•
•
Functionality
Telefax Automatic Group 3, Transparent
Short Message Service Functionality
High Speed Circuit Switched Data (HSCSD)
HSCSD application software provides accelerated data rates for end-user applications.
HSCSD supports both transparent and non-transparent data services. A multiple set of
basic resources is reserved for one HSCSD call, and up to four time slots can be used
for an HSCSD call. HSCSD can be combined with 14.4 kbit/s data service for higher
data speed rates.
Multimedia message service (MMS) and short message service (SMS)
The mcBSC forwards mobile originating and mobile terminating messages transparently.
Cell broadcast messages (CB)
CB provides the mcBSC with the short message service cell broadcast (SMSCB) capabilities defined by GSM recommendations. The SMSCB is a basic teleservice that is
used for broadcasting short messages to mobile stations in a specified area within the
PLMN. The input is MMI, local, or remote. Optionally CBC can be used as the input for
CB messages.
Inter-System Network-controlled cell re-selection (IS-NCCR)
Cell re-selection is a basic cellular radio network operation, where the MS's contact point
to the network is changed during MS network connection. Cell re-selection is performed
by the MS. The target cell of the cell reselection can be selected by the network or autonomously by the MS.
Inter-System Network-Controlled Cell Re-selection (IS-NCCR) gives the network the
possibility to order a cell re-selection from a GSM cell to a WCDMA RAN cell instead of
the autonomous selection done by the MS itself. With this feature, the network decides
when the MS changes cell and which is the target cell.
IS-NCCR introduces the possibility for the network to control timing and target cell selection in cell re-selection. The cell reselection criteria is as follows:
•
•
Service-based IS-NCCR selects 3G network according to SGSN Service UTRAN
CCO BSSGP procedure even if the serving cell signal level is good.
Coverage-based IS-NCCR selects 3G network as soon as it is available or when
GSM coverage ends, depending on operator choice.
Inter-BSC Network-assisted cell change (IB-NACC)
The Inter-BSC Network-Assisted Cell Change (IB-NACC) feature is an extension of
NACC feature that provides assistance to the MS, when it moves from one cell to
another cell inside the BSC. IB-NACC extends the functionality to provide the cell
change assistance when the MS moves between different BSCs. When IB-NACC is in
use, the network assists the MS changing cell by sending a set of system information
messages of the target neighboring cell to the MS, while it is still camping on the source
cell. The system information messages are exchanged between two BSCs using the
RAN Information Management (RIM) protocol. The RIM protocol is an enhancement to
BSSGP protocol and is used for a reliable BSC-to-BSC information exchange.
DN0947925
Id:0900d80580a5643d
Confidential
13
Functionality
Multicontroller BSC and Multicontroller Transcoder
Product Description
Inter-System Network-assisted cell change (IS-NACC)
The Inter-System Network-Assisted Cell Change (IS-NACC) feature is an extension of
the IB-NACC feature that provides assistance to the MS, when it moves from one cell to
another cell of a different BSC. The IS-NACC feature extends the functionality by providing the GSM system information to the WCDMA system. The WCDMA system may
use this set of system information messages in cell change assistance, when the MS
moves from a WCDMA cell to a GSM cell. The system information is transferred by BSC
to RNC using the RIM protocol. The RIM protocol is an enhancement to BSSGP protocol
and is used for a reliable BSC-to-RNC information exchange.
Inter-System Network-assisted cell change for LTE (IS-NACC for LTE)
The Inter-System Network-Assisted Cell Change for LTE (IS-NACC for LTE) feature is
an extension of IB-NACC feature that provides assistance to the MS when it moves from
one cell to another cell of a different BSC. The IS-NACC for LTE feature extends the
functionality by providing the GSM system information to the LTE system. The LTE
system may use this set of system information messages in cell change assistance,
when the MS moves from an LTE cell to a GSM cell. The system information is transferred by the BSC to eNodeB using the RIM protocol. The RIM protocol is an enhancement to BSSGP protocol and is used for a reliable BSC-to-LTE information exchange.
2.1.3
Operability, capacity, quality, and value added services
GSM-UTRAN interworking
To provide seamless coverage in the areas where WCDMA is not available, for example
in rural areas, inter-system handovers provide a method of extending the radio network
coverage area by making a handover from the WCDMA network to the GSM network.
Additionally, in cases where the WCDMA network and GSM network overlap, an intersystem handover from GSM to WCDMA can be made to relieve the traffic load in the
GSM system. Inter-system network controlled cell re-selection is also supported.
Inter-system handovers provide seamless coverage extension for 3G with the existing
GSM network (or vice versa) as well as capacity extension for GSM with a load sharing
between 3G and GSM.
GSM-LTE interworking
LTE system information functionality enables GSM/EDGE–LTE interworking. Using this
functionality the neighbouring LTE cell and parameter information can be introduced to
the BSS. By doing this, the autonomous cell reselection from the GSM/EDGE cell to the
LTE cell is possible. Interworking capability with LTE results in continuous coverage and
improved end user experience.
MS location services (LCS)
LCS allows a GSM subscriber and/or valid mobile equipment to be positioned. Positioning might be initiated by the subscriber, the network, or an external party utilizing the
Mobile Positioning Function. Positioning is subject to various restrictions based on, for
example, capability, security, and service profiles. LCS allows the location of a GSM MS
to be determined at any time while the MS is within the radio coverage area of the GSM
HPLMN or VPLMN. Different MS location methods have different benefits and drawbacks. No single method is suitable for all applications. The BSS provides support for
Cell ID with timing advance (CI+TA) method for legacy phones. It means that in addition
to CI data also additional information are to be used to improve a legacy MS location
14
Id:0900d80580a5643d
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Functionality
accuracy. The method includes location calculation using air interface measurements.
The Lb+ interface support for Standalone SMLC also enables the use of the assisted
GPS location method.
Adaptive multi-rate codec (AMR)
mcBSC supports full rate (FR), half rate (HR) and enhanced full rate (EFR) speech
codecs. AMR introduces a set of codecs and an adaptive algorithm for codec changes
which together can provide significantly improved speech quality and more capacity on
the air interface. With AMR it is possible to achieve very good speech quality in FR mode
even in low C/I conditions; or increase the speech capacity through using the HR mode
while still maintaining the quality level of calls.
The AMR consists of a family of codecs (source and channel codecs with different tradeoff bit-rates) operating in the GSM FR and HR channels. The idea behind the AMR
codec concept is that it is capable of adapting its operation optimally according to the
prevailing channel conditions.
Enhanced operation with power control and handover algorithms together with improved
quality measurements (FER Measurement) provide extended benefits and interworking
with the NSN advanced capacity software solutions, including Intelligent Frequency
Hopping (IFH). Power control for AMR is enhanced through AMR progressive power
control and robust AMR signaling provides reliable operation of the control channels
(FACCH/SACCH) in poor radio conditions.
Wideband adaptive multi-rate codec
Wideband AMR is a family of speech codecs designed to achieve improvements in
speech quality by extending the speech bandwidth. The sampling rate used by
Wideband AMR is twice the rate of current voice services in mobile and fixed line telephony. The higher sampling rate, combined with improved transcoding algorithms,
enhances the audio frequency band to 50 Hz - 7000 Hz, which is a significant increased
compared to the 300 Hz - 3400 Hz frequency band for existing voice services.
The Wideband AMR codec set supported by the BSS consists of 12.65, 8.85 and 6.60
kbps codec modes, which are currently the same as in WCDMA RAN.
Like in AMR, the codec mode can be chosen based on the radio conditions, yielding to
optimal audio performance through rate adaptation. The codec mode can be changed
every 40 ms in GSM. The codec also includes a source controlled rate adaptation mechanism, which allows it to encode speech at a lower average rate by taking speech inactivity into account.
Wideband AMR requires support for end-to-end tandem-free operation, because downsampling in transcoding would invalidate the improved properties of sound.
A5/3 ciphering
A5/3 is a more secure 3GPP-standardized ciphering method that is based on the same
core algorithm used in WCDMA. While the actual ciphering is performed by the BTS, the
mcBSC selects the ciphering algorithm based on the information received from the MSC
and the information on the allowed and supported algorithms in the BSS and MS.
Enhanced A5/1 ciphering
The mcBSC supports also an option for additional security enhancement for the generally employed A5/1 ciphering mechanism. This feature provides enhanced security for
the communication done with legacy GSM mobile terminals with intra-cell SDCCH
handover mechanism.
DN0947925
Id:0900d80580a5643d
Confidential
15
Functionality
Multicontroller BSC and Multicontroller Transcoder
Product Description
Dual-band GSM operation
The mcBSC supports the dual band network. The dual band operation supports dual
band mobiles able to perform handovers between the GSM 900 and GSM 1800 bands,
between 800 and 1900 bands as well as GSM/EDGE 800/1800 during a call.
Extended GSM 900 band
The extended (E)GSM 900 band (tri band) supports the use of the ETSI specified GSM
900 frequency band extension, the area of 880-890 MHz uplink and 925-935 MHz
downlink where available. This means that a total of 50 radio frequency channels are
included in this E-GSM 900 band. For a GSM operator, the E-GSM 900 extension band
can represent the most cost-effective way of adding capacity to his system if the primary
GSM spectrum is used.
Common BCCH
There is an option that allows GSM 900 and GSM 1800 TRXs to share the same BCCH
in the same cell. This functionality can be considered a progression from the integrated
dual band BTS and EGSM 900 frequency band support (Tri Band). Common BCCH is
also supported for GSM/EDGE 800/1900 frequency bands.
Intelligent underlay-overlay (IUO)
The IUO allows the operator to reuse frequencies more intensively and hence achieve
a higher radio network capacity. In IUO the operating spectrum of a network is divided
into regular frequencies and super-reuse frequencies. The overlay network uses regular
frequencies and offers a continuous coverage area. The underlay network uses the
super-reuse frequencies which are reused very intensively to provide the extended
capacity.
Intelligent frequency hopping (IFH)
The IFH provides the benefits of IUO and frequency hopping at the same time: the
operator can enjoy powerful radio spectrum efficiency and the quality benefits of frequency hopping, avoiding frequency-dependent fading in the radio path.
Advanced multilayer handling (AMH)
The AMH concept is used to redistribute traffic to the appropriate layer or frequency
band according to the prevailing load of the network. AMH provides the network operator
with the tools to relieve the load of the congested cells and smooth out the load over the
network. In other words, it provides the operator with both improved quality and capacity.
Extended cell
Extended cell enables the use of two cells, that is, inner and outer cells with different
timing advance ranges. An inner cell has a regular coverage area and an outer cell has
an extended radius of the coverage area. Based on the timing advance, the mcBSC
triggers a handover when the mobile station is approaching the inner cell while still being
served by the outer cell. Depending on the configuration of the cell, services can be
provided up to 70 km from the BTS site. Super extended cell further enhances the cell
radius up to 105 km.
Multipoint A interface
Multipoint A interface enables one mcBSC to be connected to several core network
elements (MSCs or MSC Servers). Even if one of the core network elements or connections fails, it is still possible that the network remains operational (but with a reduced
16
Id:0900d80580a5643d
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Functionality
capacity). Multipoint A interface improves network performance in terms of scalability
and makes capacity upgrades smoother. Network load can be distributed among the
serving entities.
SIGTRAN
SIGTRAN is a standardized way to carry SS7 signaling over an Internet protocol (IP)
backbone. The same IP backbone can be used for all kinds of traffic (management,
user, and control plane).
Multi-operator BSS
Multi-operator base station subsystem (MOBSS) enables two or more network operators to share a BSS. This BSS sharing would typically occur in a network roll-out phase
in order to derive CAPEX / OPEX advantages or in a phase where the 2G network is
being scaled down due to 3G networks.
Operators can share one or more physical BSCs and BTSs between themselves. They
can have both shared BSS as well as their own dedicated BSS networks, and either own
or shared BTSs within the shared BSS area.
Energy saving mode for BCCH TRXs and Flexi EDGE dual TRX automatic power
down
Energy saving mode for BCCH TRXs introduces a new configurable power saving mode
for BCCH TRXs in Flexi EDGE BTSs, which can reduce energy consumption throughout
the day. Flexi EDGE Dual TRX Automatic Power Down enables the operator to shut
down a dual TRX during periods of low traffic, thus reducing energy consumption during
the night-time, for example.
File-based plan provisioning
File-based plan provisioning enables the operator to download radio network configuration plans by using the file transfer protocol (FTP).
File-based plan provisioning improves the performance of the configuration change procedure. The performance improvement is needed because of increased network
element capacity, increased number of radio network objects, and growing network
sizes.
PCU2 Pooling and Dynamic PCU2 Pooling
A group of PCU units forms a packet service entity (PSE), that is, one PSE can contain
several PCU units in a BSC. A PSE is a logical concept that hides the physical PCU units
from the logical network configuration. From the serving GPRS support node (SGSN),
a PSE looks like a single PCU. With PCU pooling segments are attached to a PSE
instead of a single PCU. When a new PCU is added to a PSE, the Gb interface is configured automatically for the new PCU. The system also allocates segments to the new
PCU, based on the measured peak GPRS/EDGE load of each cell. For more information, see “Packet Control Unit (PCU2) Pooling“
Dynamic PCU2 pooling feature is an extension of the Packet Control Unit (PCU2)
Pooling feature. It enables automatic allocation of the segments between PCUs within
a PCU pool. User needs to define when PCU pool reallocation start and how often it is
done. For more information, see ”Dynamic PCU Pooling”
DN0947925
Id:0900d80580a5643d
Confidential
17
Functionality
Multicontroller BSC and Multicontroller Transcoder
Product Description
2.1.4
Support for smart device friendly GSM networks
Increased paging capacity
Extended CCCH (E-CCCH)
The E-CCCH feature increases the CCCH channel capacity in the cell. It may be used
for alleviating CCCH paging and access grant capacity problems if these appear in the
network. With this feature, the operator can define one, two, or three extended CCCH
channels in the BCCH TRX. The non-combined channel structure of a CCCH is meant
for bigger cells. This feature aims to introduce more non-combined CCCHs, thus
extending the range of non-combined configurations that a cell can assume in compliance with GSM specifications.
Intelligent Selective Paging
Intelligent Selective Paging feature decreases signaling load generated by paging
messages considerably in Air and Abis interfaces by sending the paging message only
to the last known cell and its adjacent cells. In basic paging procedure, the MS is paged
either only the cells identified in paging message, or all the cells in BSC's control. In this
basic solution, every cell in the location area is paged, even if the MS is located in one
cell only. The more the traffic, the more pages are generated for each cell.
When Intelligent Selective Paging is activated and MS is paged, MSC identifies the last
known cell of the MS in the paging message and sends the BSC a paging message containing the location area code (LAC) + CI of the cell. Message is sent only to the BSC in
which the cell is configured. When BSC receives the message, it conducts paging in the
cell identified in the paging message and its adjacent cells.
If there is no response from the MS, the MSC re-pages the MS with paging message
containing only LAC; if there are more than one BSC belonging to the same location
area (LA), the message is usually sent to all of them. The MSC may have settings which
affect to this. When BSC receives the paging message containing LAC identification
only, the paging is done in all the cells belonging to the identified LAC.
If more than one cell is identified in the paging message, the paging is conducted only
in the identified cells.
Precise Paging
Precise Paging feature enhances the signalling capacity of the CCCH channel through
initially sending paging messages only towards the cell (and its neighbors) from which
a Handset had performed the most recent connection to the BSC - instead of the whole
Location Area (LA) or Routing Area (RA). If the Handset does not respond within a given
period of time, the paging message is then extended towards the other cells of the LA
or RA.
Voice and Data Traffic coordination
Paging Coordination
The Paging coordination in BSC feature enables the GSM/GPRS network to send a CS
paging request message to a GPRS-attached MS on the PACCH, when the mobile is in
packet transfer mode. In addition to Paging Coordination in BSC, BSC also provides
paging coordination in network operation mode I (NOM I) with Gs interface between the
MSC and the SGSN. With the introduction of this feature, the BSC performs CS paging
coordination internally when in the network operation mode II (NOM II). The BSC
forwards the paging messages internally to the appropriate PCUs, which in turn send
the paging messages on the PACCH, if the MS is in packet transfer mode.
18
Id:0900d80580a5643d
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Functionality
Dual transfer mode (DTM)
DTM provides mobile users simultaneous circuit switched (CS) voice and packet
switched (PS) data services. This means that users can, for example, share a video call
or send and receive email during an ongoing phone call.
GSM data perfromance improvements
High Multislot Classes (HMC)
HMC increases the EDGE peak throughput value from 236.8 kbit/s to 296 kbit/s, as well
as the combined downlink and uplink transmission throughput. Together with DTM it
makes symmetrical (equal number of downlink and uplink timeslots (TSLs)) allocation
possible, enabling good quality video transmission. One TSL is used for a CS voice and
two downlink and uplink TSLs are used for a PS video transmission.
Extended Dynamic Allocation (EDA)
Extended Dynamic Allocation (EDA) allows an MS to use more than two timeslots in the
uplink direction. With EDA the number of uplink timeslots per uplink temporary block flow
(TBF) is up to four, which enables the following maximum uplink bit rates:
•
•
•
GPRS with CS1/CS2, up to 48 kbit/s
GPRS with CS3/CS4, up to 80 kbit/s
EDGE, up to 236 kbit/s
Downlink dual carrier (DLDC)
The Downlink dual carrier (DLDC) feature offers a possibility to enhance the data rates
of DLDC-capable MSs by increasing the number of radio timeslots that can be allocated
for the downlink TBFs of such mobiles. This is achieved by assigning the resources of
an EGPRS downlink Temporary Block Flow (TBF) on two TRXs. One of these channels
can be, for example, on a BCCH carrier, and the other on a TCH with frequency hopping.
The MS receives both radio frequency channels, thus doubling downlink throughput. An
uplink TBF, on the other hand, is assigned on one TRX only. However, the uplink TBF
can be dynamically reallocated between the two TRXs to maximize utilization of uplink
resources. This feature doubles downlink peak throughput, bringing rates of up to 592
kbit/s. The average throughput can exceed 300 kbit/s for example, the streaming of high
quality video.
The HMC feature in mcBSC must be enabled in order to utilize the extended multi slot
capabilities of MSs with multi slot classes 30-45 for DLDC.
Network-assisted cell change (NACC)
NACC reduces service outage time to less than one second when a GPRS/EDGE
mobile moves between GPRS/EDGE cells. It improves both autonomous and networkcontrolled cell change.
Outage time is reduced because the network is allowed to assist MSs before and during
the cell change. The network sends neighbor cell system information to the mobile
through the source cell on packet associated control channel (PACCH) while it is still
camping on the serving cell. Neighbor cell system information messages sent to the MS
contain a set of system information messages needed to perform packet access in the
new cell.
When all required messages are sent to the mobile, the MS can perform packet access
and use PACKET SI STATUS procedures for the acquisition of the rest of the system
information messages.
Network-controlled cell re-selection (NCCR)
DN0947925
Id:0900d80580a5643d
Confidential
19
Functionality
Multicontroller BSC and Multicontroller Transcoder
Product Description
NCCR introduces the possibility for the network to order a cell re-selection instead of the
autonomous selection done by the MS itself. With NCCR, the network triggers the cell
change and selects the target cell.
Cell re-selection is a basic cellular radio network operation, where an MS moves from
one cell to another. Cell re-selection is performed by the MS.
NCCR includes the following criteria:
•
•
Power budget pushes GPRS/EDGE-capable mobiles to operator defined data layer
or cells preferred for data usage.
In gradual EDGE network deployment power budget algorithm can be used to direct
EDGE capable MSs to EDGE cells and non-EDGE capable MSs to GPRS cells.
With power budget NCCR, the operator can reduce the number of unnecessary cell
re-selections, especially ping-pong cell re-selections at the cell borders.
Quality control triggers NCCR when the quality of the serving cell transmission
drops, even if the serving cell signal level is good.
Enhanced packet scheduling
Enhanced packet scheduling provides service differentiation for the users having different QoS attributes (Traffic Class, THP and ARP) by supporting R99 QoS parameters on
the level of radio resource scheduling. With the help of adjustable scheduling weights it
is possible to determine how PCU shares the radio resources among the users with different QoS attributes. Therefore the right level of service that is needed for the specific
application in the network can be provided and usage of available resources can be efficiently improved.
Smart Resource Adaptation (SRA)
Smart Resource Adaptation (SRA) enables improved capability to handle more smart
phones by efficiently adapting radio resources for packet transfer based on real demand
from the very beginning instead of the max throughput capabilities of MS and network.
With Smart Resource Adaptation resource blocking due to smart phones can be
reduced.
Voice capacity solutions
Orthogonal subchannel
OSC greatly reduces operational costs by using the channel allocation in an efficient
manner. It enhances the channel capacity by allowing four users to share the same time
slot for a double half rate channel. This functionality makes use of orthogonal subchannels to increase the channel capacity.
In the downlink, a BTS uses quadrature phase shift keying (QPSK) modulation, which
is composed from orthogonal subchannels. As the subchannels are orthogonal, they
can be received separately. It uses different training sequences to identify the subchannels in the uplink, while the transmission is done in normal Gaussian minimum shift
keying (GMSK) modulation. By using an AMR Full Rate and an AMR Half Rate together
with the new AMR Double Half Rate, the network capacity can be increased without
compromising the voice quality.
Dynamic frequency and channel allocation (DFCA)
DFCA is a new channel assignment scheme, which uses interference estimations
derived from mobile downlink measurement reports to dynamically assign a timeslot and
frequency in the establishment of a new call or incoming handover.
20
Id:0900d80580a5643d
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Functionality
The purpose of this channel selection is to provide satisfactory quality, so that each connection meets its quality of service requirements, and to minimize the interference to
other connections. These lead to a significant capacity gain as the usage of valuable frequency resources is dynamically optimized.
DFCA is a completely automated functionality, and it removes the need to make a frequency plan for the non-BCCH TRXs configured for the functionality.
DN0947925
Id:0900d80580a5643d
Confidential
21
Multicontroller BSC and Multicontroller Transcoder
Product Description
2.2
Functionality of the mcTC
The mcTC is used on the 3GPP A over IP (AoIP) interface between the mcBSC and the
MSS/MGW. The mcTC provides capabilities to perform transcoding functions also in the
BSS and provides a Packet Ater interface towards the mcBSC. The processing
resources of the mcTC can be shared by several mcBSCs using several small logical
TC units. Transcoding and Rate Adaptation Unit (TRAU) is implemented with services
provided by the mcTC.
The telecommunication functions of the mcTC are:
•
•
•
2.2.1
Transcoding (converting the G.711 64 kbit/s PCM speech traffic carried over AoIP
to Packet Ater/Abis FR, HR, EFR, AMR-NB or AMR-WB coded format and vice
versa)
Rate adaptation of CS data traffic carried over AoIP to Packet Ater/Abis format and
vice versa
Termination of AoIP and Packet Ater transmission and setting the required IP and
port addresses call by call basis
Advanced functionality of the mcTC
Beyond the general functionality, the mcTC offers advanced network efficiency and
speech quality solutions for enhanced user experience and efficient network operation.
Automatic Level Control (ALC)
The speech quality enhancing ALC automatically adjusts the level of a speech signal
towards a predefined target level, either amplifying or attenuating the signal. This is
done to compensate the varying signal levels in the network which results from various
circumstances such as different user equipment, communication conditions or different
speaker.
In addition to linear PCM gain adjustment, ALC can also be applied straight to coded
speech parameters. This is called Coded Domain ALC (CD-ALC). The benefit of the CDALC is that TFO can be used simultaneously with ALC.
Text Telephony (TTY)
The Text Telephone signal can be adapted for use over the radio interface by a combination of a Text Telephone detector and CTM (Cellular Text telephone Modem) transmitter at one end and a corresponding CTM receiver and Text Telephone regenerator
at the other end. The combination of a Text Telephone detector/regenerator and a CTM
receiver/transmitter is called a CTM adaptor.
The Text Telephone detector converts the audio signals received from a PSTN Text
Telephone device into characters. The CTM transmitter transforms the text telephone
characters into a signal that can be transmitted robustly via the speech codec and the
radio transmission path of cellular phone systems. The corresponding CTM receiver
decodes the signal back into Text Telephone characters. The Text Telephone regenerator transforms the characters back to audio signals that can be sent to a PSTN Text
Telephone.
Acoustic Echo Cancellation (AEC)
Acoustic echo is generated in the uplink direction due to the acoustic coupling from the
ear-piece to the microphone of the user equipment (UE). Acoustic echo is removed by
a built-in acoustic echo control device of the UE/MS (mobile station). Sometimes this is
22
Id:0900d80580a5643c
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
not sufficient, and therefore an AEC functionality is provided on the network side by
mcTC.
In addition to linear PCM acoustic echo control, AEC can also be applied straight to
coded speech parameters. This is called coded domain AEC (CD-AEC). The benefit of
the CD-AEC is that TFO can be used simultaneously with AEC.
Noise Suppression (NS)
The majority of mobile phones are used in the urban environments. This makes background noise an important factor in the final voice quality perceived by the end-user. A
high background noise level and low signal-to-noise ratio (SNR) can degrade voice
quality so much that the listener becomes annoyed or concentrates on background
sounds rather than speech. In very low SNR conditions, even the intelligibility of the conversation might suffer.
Therefore, one way to improve customer satisfaction and to reduce churn is to improve
the SNR of calls. By using Noise Suppression (NS) implemented in the mcTC, the SNR
is effectively increased by lowering the noise level without attenuation of the speech
channel.
In addition to linear PCM noise suppression, NS can also be applied straight to coded
speech parameters. This is called coded domain NS (CD-NS). The benefit of the CDNS is that TFO can be used simultaneously with NS.
Tandem Free Operation (TFO)
TFO is a procedure which can be used to enhance speech quality in mobile-to-mobile
(MS-MS) calls. TFO efficiently improves the speech quality in mobile-to-mobile calls by
avoiding double transcoding.
Discontinuous Transmission (DTX)
DTX is a mechanism which allows the radio transmitter to be switched off during speech
pauses. The purpose is to reduce the power consumption of the transmitter, which is
important for mobile phones, and to reduce the overall interference level on the radio
channels, which affects the capacity of the network.
Data transmission
Rate adaptation of CS data traffic up to 14.4 kbit/s FR data rates as well as high speed
circuit switched data (HSCSD) transmission at the rates of maximum 4 x FR data (HS4).
DN0947925
Id:0900d80580a5643c
Confidential
23
Interfaces
Multicontroller BSC and Multicontroller Transcoder
Product Description
3 Interfaces
The mcBSC provides interfaces for the MSS/MGW, NetAct, the base transceiver
stations (BTSs), the serving GPRS support node (SGSN), the cell broadcast centre
(CBC), the mcTC and towards other BSCs. There is also the Lb interface to stand-alone
Serving Mobile Location Centre (SMLC).
Figure 2
mcBSC interfaces
The mcBSC and the mcTC enables efficient IP/Ethernet connections on all interfaces:
•
•
•
•
•
A over IP (AoIP)
SS7 over IP (SIGTRAN)
Packet Abis over Ethernet or Packet Abis / TDM with Packet Abis Network Media
Conversion functionality
Packet Ater over Ethernet
Gb over IP
Additionally all other interfaces like O&M, Lb etc. are based on IP/Ethernet.
3.1
A over IP (AoIP)
The AoIP interface between the MSS/MGW and the mcBSC (or mcTC depending on
network scenario) is implemented according to the 3GPP standards. Together with the
signaling over IP (SIGTRAN), it offers an all IP transport towards the core network.
The 3GPP has standardized AoIP for Rel-8, including two basic alternatives:
•
24
Transcoder located in the base station system (BSS) network ( PCM coded speech
(G7.11) is sent over IP stack) allowing optimized transcoder resource allocation
within the BSS network
Id:0900d80580a56463
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Interfaces
BSS
Packet
Abis
Packet
Ater
Eth
Eth
Eth
Eth
mcTC
Figure 3
•
CN
AoIP
(TC in BSS)
AoIP with transcoder located in BSS
Transcoder located in core network (BSS is sending coded frames, for example
GSM codecs like AMR, over A interface using IP stack)
BSS
Packet
Abis
Figure 4
Eth
CN
Eth
AoIP
(TC in CN)
AoIP with transcoder located in core network
SIGTRAN
Signaling transport over IP (SIGTRAN) is a standardized way to carry SS7 signaling
over an Internet Protocol (IP) backbone.
SIGTRAN can be configured with a resilience functionality like SCTP multihoming
together with heartbeat mechanism. Usage of redundant routes and duplicated
backbone elements provide resilience for QoSaware IP network. Signaling is assigned
to high priority class for IP routers and sufficient amount of transmission capacity must
be ensured for this high priority class in IP backbone.
Multipoint A interface
Multipoint A Interface enables one BSC to be connected to several core network elements.
Multipoint A Interface introduces the concept of a pool area. A pool area corresponds
roughly to an MSS service area in that it is a collection of one or more BSC service
areas. However, a pool area is served simultaneously by multiple MSSs which share the
traffic in the area. In addition, two or more pool areas may overlap whereas service
areas do not.
Service availability is increased as other core network elements can provide service in
case one MSS in a pool area fails. The amount of signaling required by roaming mobile
stations is reduced, because the pool area is larger than the service area of one MSS.
3.2
Packet Abis over IP/Ethernet
The Packet Abis over IP/Ethernet enables a bandwidth optimized connectivity to packet
switched networks. Bandwidth savings are achieved thanks to Abis optimization through
the removal of silence and idle frames, multiplexing and bandwidth sharing for circuit
and packet switched user, control and management planes. When no data is to be sent,
no capacity is occupied.
The Packet Abis user plane is transported over UDP/IP and the control plane and management plane is transported over SCTP/IP. The physical interface supported is Ethernet.
DN0947925
Id:0900d80580a56463
Confidential
25
Interfaces
Multicontroller BSC and Multicontroller Transcoder
Product Description
Packet Abis
Eth
Packet Switched
Network
Eth
BTS
mcBSC
Figure 5
3.2.1
Packet Abis over IP/Ethernet
Packet Abis / TDM – Packet Abis Network media conversion
The Packet abis media conversion feature allows the mixing of Packet Abis over
Ethernet and Packet Abis over TDM interface media between BTS and mcBSC. This
feature decouples the interface types between the BTS and mcBSC. External conversion device is performing Packet Abis over TDM to Packet Abis over Ethernet conversion and vice versa, positioned at the mcBSC site or at an aggregation site location of
the transport network. By using this feature, mcBSC connectivity for BTSs with Packet
Abis over TDM is enabled with Ethernet interfaces natively supported by the mcBSC.
The used external conversion device needs to:
•
•
•
3.3
Terminate Packet Abis over TDM
Aggregate and schedule Packet Abis Traffic at IP layer meeting the QoS
Terminate Packet Abis over Ethernet
Packet Ater over IP/Ethernet
The Packet Ater interface is an IP based BSS internal interface between the mcBSC and
the mcTC.
Packet
Ater
Eth
Figure 6
Packet Switched
Network
Eth
mcTC
Packet Ater over IP/Ethernet
The physical interface used is Ethernet.
3.4
Gb over IP
The Gb over IP interface offers UDP/IP stack as a transport method in the transmission
network. It complies with the 3GPP 48.016 and 48.018 standards. The Gb over IP interface's subnetwork is constructed with a UDP/IP stack. When the Gb interface is based
on IP, an NS-VC is a pair of UDP/IP addresses: one UDP/IP address in the BSS and
one UDP/IP address in the SGSN. That is, an NS-VC is composed of IP endpoint
addresses, one IP endpoint address in BSS and the other IP endpoint address in the
SGSN.
Multipoint Gb Interface
With Multipoint Gb interface one packet control unit (PCU) or PCU pool can be connected to several SGSNs. Multipoint Gb Interface provides the system with enhanced
resilience and with the possibility to equalize traffic load of the different SGSNs.
26
Id:0900d80580a56463
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Interfaces
For more information see BSS10103: Gb over IP feature description.
3.5
Lb over IP
The Lb over IP interface is used to connect the mcBSC to a stand-alone SMLC. The
interface contains a controlling functionality for the allocation of location requests
between location services in BSC and the external stand-alone SMLC.
For more information see Location Services in BSC and BSC-SMLC Interface Specification.
3.6
O&M over IP
The O&M interface (Q3 interface) is the interface between NetAct and the mcBSC. The
implementation of this interface is based on the O&M framework of the ITU-T and the
International Standards Organization (ISO).
The physical interface used is Ethernet.
3.7
CBC interface (BSC - CBC)
The BSC Cell Broadcast Centre interface provides an interconnection between the BSC
and the Cell Broadcast Centre (CBC). The implementation is according to GSM Specification 03.41 and permits open interconnection between the BSC and the CBC.
The physical interface used is Ethernet.
DN0947925
Id:0900d80580a56463
Confidential
27
mcBSC and mcTC architecture
Multicontroller BSC and Multicontroller Transcoder
Product Description
4 mcBSC and mcTC architecture
The major architectural change with the mcBSC and the mcTC is the move from multisubrack blade system to a few rack mount modules. Depending on the capacity needs,
one mcBSC can consist of two up to several modules. A multicontroller module is tightly
integrated and has only a few field-replaceable parts.
The new Multicontroller HW platform allows new, optimized placement of the BSC and
transcoder functionalities in the system.
4.1
Functional architecture of the mcBSC
Figure 7 shows the general functional architecture of the mcBSC. The functions are distributed in entities of hardware and software. The 1G and 10G interfaces are available
for external connections towards site routers. The main functional units of the mcBSC
are:
•
•
•
•
•
Multicontroller BSC signaling unit (BCXU)
Marker and cellular management unit (MCMU)
Operation and maintenance unit (OMU)
Packet control unit for Multicontroller (PCUM)
Ethernet transmission processing for Multicontroller (ETM)
OMU
1G and 10G interfaces
are available for external
connections towards
site routers
MCMU
Ethernet
switching
for
external
traffic
BCXU
Ethernet
switching
for
internal
traffic
PCUM
ETM
DN0952838
10GE
1GE
OMU
MCMU
BCXU
PCUM
ETM
Figure 7
Operation and maintenance unit
Marker and cellular management unit
Multicontroller BSC signaling unit
Packet control unit
Ethernet transmission processing for Multicontroller
Functional architecture of the mcBSC
g The general ETM functionality contains ETME and ETMA functionalities.
28
Id:0900d80580a56467
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
mcBSC and mcTC architecture
The distributed processing architecture of the mcBSC is implemented by a multiprocessor system, where the data processing capacity is divided among several processors.
Based on the application needs general purpose processing units can be assigned to
different tasks.
Internal communications (internal messaging) between the functional units of the
system is based on Ethernet.
The mcBSC functional units are briefly described below:
4.1.1
Multicontroller BSC signaling unit (BCXU)
The Multicontroller BSC signaling unit (BCXU) is a TRX-capacity unit of the mcBSC. It
performs those BSC functions that are highly dependent on the volume of traffic. The
BCXU consists of two parts, which correspond to the A over IP (AoIP) and Packet Abis
interfaces.
The AoIP interface part of the BCXU is responsible for the following tasks:
•
•
Performing the functions of SIGTRAN based SS7 signaling
Performing all message handling and processing functions of the signaling channels
connected to it
The Packet Abis interface part of the BCXU controls the air interface channels associated with transceivers and Abis signaling channels. The handover and power control
algorithms reside in this functional unit.
4.1.2
Packet control unit for Multicontroller (PCUM)
The PCUM unit is an independent processing unit logically connected to the BCXU. The
PCUM unit performs all the data processing tasks related to GPRS/EDGE traffic. It
implements packet switched traffic oriented Gb and Packet Abis interfaces in the
mcBSC.
The PCUM controls GPRS/EDGE radio resources and acts as the key unit in the following procedures:
•
•
•
•
•
4.1.3
GPRS/EDGE radio resource allocation and management
GPRS/EDGE radio connection establishment and management
Data transfer
Coding scheme selection
PCUM statistics
Ethernet transmission processing for Multicontroller (ETM)
In the mcBSC, A and Abis interfaces are connected to an IP network. The ETM functionality terminates all external management, user and control plane IP traffic, handling the
Ethernet transmission processing which is related to AoIP and Packet Abis interfaces in
the mcBSC. The general ETM functionality contains ETME and ETMA functionalities.
With the mcTC implementation, when transcoder is located in the BSS, ETM functionality handles the needed Ethernet transmission processing related to used Packet Ater
interface between the mcBSC and the mcTC.
DN0947925
Id:0900d80580a56467
Confidential
29
mcBSC and mcTC architecture
4.1.4
Multicontroller BSC and Multicontroller Transcoder
Product Description
Marker and cellular management unit (MCMU)
The MCMU has centralized cellular management functions for controlling cells and radio
channels for the mcBSC. The MCMU reserves and keeps track of the radio resources
requested by the MSC and the handover procedures of the mcBSC. The MCMU also
manages the configuration of the cellular network.
4.1.5
Operation and maintenance unit (OMU)
The Operation and Maintenance Unit (OMU) is an interface between the mcBSC and a
higher-level network management system and/or the user. The mcBSC can provide fullscale traffic capacity even when O&M interface towards NetAct is disconnected.
The OMU can also be used for local operations and maintenance. The OMU receives
fault indications from the mcBSC. It can produce local alarm printouts to the user or send
the fault indications to NetAct.
In the event of a fault, the OMU automatically activates appropriate recovery and diagnostics procedures within the mcBSC. Recovery can also be activated by the MCMU if
the OMU is lost. The tasks of the OMU can be divided into four groups:
•
•
•
•
4.2
Traffic control functions
Maintenance functions
System configuration administration functions
System management functions
Functional architecture of the mcTC
The general functional architecture of the mcTC is shown in Figure 8.
30
Id:0900d80580a56467
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
mcBSC and mcTC architecture
TCU
1G and 10G interfaces
are available for external
connections towards
site routers
Ethernet
switching
for
external
traffic
ETP
Ethernet
switching
for
internal
traffic
MCU
10GE
1GE
TCU Transcoding unit
ETP Ethernet transmission processing
MCU Management and control unit
Figure 8
Functional architecture of the mcTC
The functions are distributed in entities of hardware and software. The main functional
units of the mcTC are:
•
•
•
4.3
ETP, which is responsible for terminating all external management, user and control
plane IP traffic.
Transcoding unit (TCU), which implements transcoding and rate adaptation and
other media processing functions for the mcTC.
Management and control unit (MCU), which implements transcoder control, management and centralized O&M tasks in the mcTC module.
mcBSC and mcTC hardware architecture
The mcBSC and the mcTC are based on the Multicontroller HW platform in which motherboard provides the following main functions:
•
•
•
•
Slots for add-in cards
Ethernet switch
AMC expansion slots
Power supply and cooling
Add-in cards provides the processing functionality. The mcBSC and the mcTC products
efficiently utilize general purpose processing units with SW configurable functionality for
control, O&M and user plane as well as for Ethernet transmission processing and
transcoding purposes.
DN0947925
Id:0900d80580a56467
Confidential
31
mcBSC and mcTC architecture
4.4
Multicontroller BSC and Multicontroller Transcoder
Product Description
External physical interfaces
Network interfaces provide external interfaces and the means to execute physical layer
and transport layer functions.
Any interface can be configured to be used as an Abis, A, Gb or Ater interface.
External physical interfaces towards site routers can be either GbE or 10GB with
relevant SFP modules.
In addition to the network interfaces, local area network (LAN) interfaces as well as
debugging and maintenance interfaces are provided in front of the module.
The controller module front panel is shown in Figure 9.
Figure 9
Physical interfaces of controller module
The BCN module front panel contains the following interfaces and functions:
1.
2.
3.
4.
USB 2.0 slave port for software debugging purposes.
AMC bay slots for hard disk and synchronization modules.
SAS connector for cross connecting hard disks between BCN modules.
RS232 interface to the Local Management Processor (LMP) for debugging and
remote O&M purposes.
5. BCN-A : Six 1/10GE (SFP/SFP+) interfaces for inter-node cabling and external connections. BCN-B : Seven 1/10GE (SFP/SFP+) interfaces for inter-node cabling and
one GbE SFP for Trace.
6. BCN-A : Sixteen GbE (SFP) interfaces for external connections. BCN-B : Ten GbE
(SFP) interfaces for external connections and two 10GE (SFP+) interfaces for
external connections.
32
Id:0900d80580a56467
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
mcBSC and mcTC architecture
7. Two GbE (SFP) interfaces provide access to add-in card slots 1 and 8. Not used in
mcBSC and mcTC.
8. Two USB 2.0 interfaces for software upgrade of BCN platform (used typically during
commissioning).
9. GbE(1000Base-T) interface to LMP for and debugging and remote O&M purposes.
10. Two RJ 45 connectors for eight external voltage-sensitive alarm inputs (with 1 mA
pull-up load).
11. Two RJ45 interfaces for external synchronization input (2.048 MHz / 1.544 MHz).
12. Status led indicators.
13. Reset button.
4.4.1
Gigabit Ethernet interfaces
IP over Ethernet network interfaces with protection possibility are provided in the front
panel of the module.
All these interfaces use standard SFP and SFP+ (for 10GE) connectors.
Interface Type
Gigabit Ethernet
Standard
IEEE 802.3-2005
Physical layer
1000Base-SX
1000Base-LX
1000Base-T
Connections
SFP/LC
SFP/LC
SFP/RJ-45
Number of interfaces
on BCN-A
16 pcs
Number of interfaces
on BCN-B
10 + 1 pcs
Table 1
Interface Type
1 and 10 Gbps Ethernet
Standard
IEEE 802.3-2005
Physical layer
1000Base-SX
1000Base-LX
1000Base-T
Connections
SFP/LC
SFP/LC
SFP/RJ-45
Physical layer
10GBase-SR
10Base-LR
10GDirect Attach
Connections
SFP+/LC
SFP+/LC
SFP+/copper
Number of interfaces
on BCN-A
6 pcs in the node
Number of interfaces
on BCN-B
7pcs for 1GE/10GE and
2pcs for 10GE only
Table 2
DN0947925
Interface specifications for network connections and element
management
Interface specifications for connections to be used either for module interconnects or network connections
Id:0900d80580a56467
Confidential
33
mcBSC and mcTC architecture
4.4.2
Multicontroller BSC and Multicontroller Transcoder
Product Description
LAN/Ethernet for O&M interfaces
The local area network interface functions at the rate of 10/100/1000 Mbps using an
RJ45 connector located in the front panel.
4.4.3
SW download and SW debugging interfaces
One USB type B interface for debugging and two USB type A interfaces for SW
download are provided on the front panel.
4.4.4
Serial Port interface
Standard RS-232 interface with a RJ-45 connector, used for connection to the Local
Management Processor.
4.4.5
External Alarm interface
Standard RJ-45 connector, used for collecting external alarm inputs for monitoring
purpose.
4.4.6
External Telecom Synchronization interface
Two standard RJ-45 connectors, used for external E1, T1, J1, 2.048 MHz, and 1.544
MHz input and output reference. mcBSC synchronization connectors are used for
maximum two external inputs (multi module or single module) and remaining connectors
are used for chaining module synchronization.
4.4.7
External HD cross connection
Standard SAS connector, used for cross connecting hard disks between two controller
modules.
4.4.8
External Packet Synchronization Interfaces
Optional Multicontroller Packet Timing Unit (PTUM) is used for mcBSC packet synchronization. This unit implements Ethernet Packet synchronization IEEE1588v2 PTP
protocol and Synchronous Ethernet (SyncE) for physical layer synchronization. It can be
used in slave mode.
Packet Synchronization interfaces are available with BSAC-A AMC card.
Two Standard SFP connectors, used for external 100M/1GE Ethernet providing IEEE
1588 or Synchronous Ethernet timing.
Two Standard RJ-45 connectors, used for external E1, T1, J1, 2.048 MHz input (and
output) reference or GPS input.
34
Id:0900d80580a56467
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
mcBSC and mcTC software
5 mcBSC and mcTC software
The mcBSC and the mcTC system software implemented for the general purpose processing units provides a standard, easy-to-use operating environment for the platform
and application software of a functional unit. The uniform operating environment facilitates the development and maintenance of the platform and application software and
helps the user understand the operation of the software.
Software architecture of the mcBSC and the mcTC is shown in Figure 10.
Application SW
Platform SW
System SW
mcBSC and mcTC general purpose processing units
Figure 10
DN0947925
The mcBSC and the mcTC software platform
Id:0900d80580a56473
Confidential
35
Connectivity and capacity
Multicontroller BSC and Multicontroller Transcoder
Product Description
6 Connectivity and capacity
6.1
mcBSC connectivity
mcBSC configurations are built with compact Multicontroller BSC hardware modules
according required TRX and PS data connectivity. With modular hardware architecture
and scalable software design, mcBSC connectivity can also be easily extended by just
adding additional mcBSC modules.
The following tables define the TRX and PS extension capacity steps for a standalone
mcBSC.
Table 3
36
mcBSC capacity steps with BCN-A hardware
Id:0900d80580a56478
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Table 4
DN0947925
Connectivity and capacity
mcBSC capacity steps with BCN-B hardware
Id:0900d80580a56478
Confidential
37
Multicontroller BSC and Multicontroller Transcoder
Product Description
6.2
mcTC connectivity
mcTC configurations are built with compact Multicontroller TC modules enabling
transcoder capacity scaling according the needed capacity for voice transcoding, CS
data rate adaptation and mcBSC connectivity. Required transcoder capacity is flexibly
implemented by including needed amount of mcTC modules into complete BSS system
installation.
Figure 11
38
mcTC connectivity steps with BCN-A hardware
Id:0900d80580a56476
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
6.3
Traffic handling capacity
With reference to the nominal model shown in Table 5, the maximum processing
capacity of the mcBSC (BCN-A and BCN-B hardware) is 26 400 Erl, giving full support
to 4 400 full rate TRXs with module configuration providing maximum TRX connectivity.
The BHCA value varies heavily depending on the call mix. With the nominal model
shown in Table 5, the call processing capacity is 780 000 BHCA and correspondingly
with call mixes having considerably shorter call lengths - a level of over 5 000 000 BHCA
can be reached.
BHCA and Erlangs figures are related to Voice Service Call mix shown in Table 5.
Property
Value
Mean holding time (MHT)
120 s
Proportion of MS originating calls
70%
Proportion of MS terminating calls
30%
Proportion of handovers
1.5 per call
Proportion of location updates
2 per call
Proportion of IMSI detaches
0.1 per call
For terminating call attempts, the noanswer call attempts to paging
requests
63%
SMS call rate
1 req./subs./1 hour
Table 5
CS processing capacity of the mcBSC with nominal call mix
The above mentioned traffic handling capacity of mcBSC can be achieved with module
configuration providing maximum TRX connectivity. Some new functionalities and
network characteristics might, have an influence on the capacity of the mcBSC. The
maximum traffic handling capacity (26 400 Erl) of mcBSC supports 4400 full rate TRXs
or 2200 half rate TRXs. Connectivity for 4400 AMR HR TRXs is available as an optional
Soft Channel Capacity functionality.
DN0947925
Id:0900d80580a56477
Confidential
39
Configurations
Multicontroller BSC and Multicontroller Transcoder
Product Description
7 Configurations
7.1
General
The mcBSC and the mcTC configurations are based on easily installable, standardsized, compact modules.
The modular and compact design allows flexible scalability in configurations and efficient utilization of the available site space.
The multicontroller module is extremely easy to install, operate and maintain.
The smallest operational size of the mcBSC is two modules. The maximum supported
Configuration with BCN-B hardware is 8 modules. With BCN-A hardware the maximum
supported configuration is 7 modules. The capacity is delivered under capacity licenses
or, if exceeding the capacity limit of the existing mcBSC HW configuration, adding additional capacity extension modules into the network element configuration.
High scalability is also evident with mcTC implementation, needed capacity and mcBSC
connectivity is reached by adding modules starting from one module basic implementation. Additional modules easily enable capacity extension according to traffic needs.
Figure 12
7.2
Compact Multicontroller BSC module used to build mcBSC configurations
mcBSC and mcTC module types
The mcBSC and mcTC configurations are flexibly built with compact Multicontroller BSC
HW modules. Only two types of general purpose processing units inside a module with
SW configurable functionality support are used to equip three types of modules used to
build a complete mcBSC configuration and correspondingly only two types of general
purpose processing units inside a module with SW configurable functionality support are
used to equip one module type used in all mcTC configurations.
7.2.1
40
mcBSC basic modules
Id:0900d80580a5647f
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Figure 13
7.2.2
mcBSC TRX extension module
mcBSC PS data extension module
Figure 15
DN0947925
mcBSC basic modules
mcBSC TRX extension module
Figure 14
7.2.3
Configurations
mcBSC PS data extension module
Id:0900d80580a5647f
Confidential
41
Configurations
Multicontroller BSC and Multicontroller Transcoder
Product Description
7.2.4
mcTC basic module
Figure 16
7.3
mcTC basic module
mcBSC configurations
Combining the compact and scalable HW platform to the modular and flexible SW in the
mcBSC and the mcTC creates a network element, where the configuration can easily
be optimized to meet the operator requirements.
The smallest mcBSC configuration consists of two Multicontroller BSC HW modules.
High scalability is reached in the process of adding additional modules into the two
module basic configuration. According to traffic and connectivity needs, additional
extension modules are added to the basic configuration enabling TRX and PS data
capacity extension.
Several network topology scenarios are possible, from a highly centralized one with a
high capacity mcBSC located at switch site, to a distributed mcBSC located close to
small, remote BTS areas.
7.3.1
Standalone mcBSC
About Standalone mcBSC
Major architectural change is moving from multisubrack type of blade system to a few
identical rack or desktop mount modules. Depending on the capacity needs, one
mcBSC consists of two to several modules.
Seven reference capacity steps are used in mcBSC. They differ in the number of Multicontroller Platform modules used.
Basic standalone mcBSC configuration consists of two modules (mcBSC basic modules).
Additional capacity steps are available by steps of one mcBSC TRX extension module
to increase TRX and PS data connectivity. Maximum TRX connectivity can be reached
with capacity step 4 containing 5 modules and on top of that, even higher PS data connectivity can be reached with additional mcBSC PS data extension modules. Maximum
configuration with BCN-B hardware consists of 8 modules.
The standalone mcBSC network element is an independent BSC network element for
all IP configurations built with flexible module configuration enabling high mcBSC scalability according to TRX and PS data connectivity needs.
42
Id:0900d80580a5647f
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Configurations
For more information on maximum connectivity of each mcBSC configuration step see
section mcBSC connectivity.
Figure 17
Standalone Multicontroller BSC capacity steps with BCN-B hardware
Inter processor communication between modules goes through 10G intermodule
cabling.
Network topology
The standalone mcBSC network scenario with 2 module basic configuration is shown in
Figure 18.
DN0947925
Id:0900d80580a5647f
Confidential
43
Configurations
Multicontroller BSC and Multicontroller Transcoder
Product Description
Figure 18
7.4
Standalone mcBSC network configuration
mcTC configuration
The mcTC configurations are built with compact Multicontroller TC modules enabling
transcoder channel capacity scaling according to needed BSC connectivity, traffic and
customer needs. Required transcoder channel capacity is flexibly implemented by
including needed amount of mcTC modules into complete BSS system installation. Typically one mcBSC is connected to several mcTC modules providing a network level
transcoding redundancy for the mcBSC, utilizing transcoding functionality provided by
mcTC modules.
44
Id:0900d80580a5647f
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Mechanical design and power supply system
8 Mechanical design and power supply system
8.1
Module
The mcBSC and the mcTC hardware is installed in a rack-mount enclosure with dimensions of 444 mm (width), 450 mm (depth) and 176 mm (height).
Figure 19
Front view of the module
The module is provided with three, field replaceable dual fans, that are capable of
keeping the temperature of all motherboard components at an acceptable level. Two
field-replaceable power supply units can be installed in the module. 230 VAC mains
power option as well as -48VDC/-60VDC battery feed are supported.
Figure 20
Rear view of the module
Two bays for standard AMC cards are provided in each module. The controller module
hot swappable hard disc, HDDs, and 1588 sync units are installed in the AMC bays.
All the external interfaces are located and easily accessible from the front of the module.
In case of the configuration consisting of several modules, they are connected together
with external cables from the front. The access to field replaceable fans and power
supply units is from rear side.
For repair and maintenance purposes, the module is easy to remove from the entire
installation.
DN0947925
Id:0900d80580a56484
Confidential
45
Mechanical design and power supply system
8.2
Multicontroller BSC and Multicontroller Transcoder
Product Description
Cabinet installation
Controller module does not have any dedicated rack or cabinet. Installation is possible
in a standard 19’’ rack according to NSN rack installation requirements.
Figure 21
CAB216-A cabinet (empty and fully equipped with eight BCN modules and
two PDUs)
The cabinet has 16 side supporting brackets and 8 rear supporting brackets for BCN
modules, and vertical front and rear cabling conduits on both sides. There are also
cabling openings at the roof and bottom of the cabinet.
The cabinet includes wheels. The cabinet can be installed:
•
•
•
on feet
on a pedestal bolted to concrete floor or to a raised floor
directly onto concrete floor or raised floor
Cabinet installation alternatives and detailed installation instructions are provided in the
document Installing BCN Hardware to CAB216-A Cabinet.
46
Id:0900d80580a56484
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Dimensions (H x
W x D)
Mechanical design and power supply system
With doors, lifting eyes, top fixing brackets, feet:
2254 x 598 x 680 mm
Without doors, lifting eyes, top fixing brackets, feet:
2130 x 598 x 600 mm
Foot adjustment +50/-0 mm
Weight
Cabinet frame with two doors: approx. 137 Kg
without anti-toppling system and? approx. 151 Kg
with anti-toppling kit.
Maximum total weight, with fully-equipped modules,
PDUs, lifting eyes, supporting brackets, feet and
cables: approx. 470 kg
Table 6
8.3
CAB216-A cabinet technical data
Cooling of the modules
The cooling is made by three redundant fan modules with two fans each, supervised and
controlled by the HW management system. The field replaceable fan modules are in the
rear side of the box.
Figure 22
Controller module, rear side
The cooling system is designed to work in single fan failure case up to ambient temperature of 40°C. The system has a specific cooling algorithm which controls the fan speed.
It is based on measured values of exhaust air temperature in the air inlet. Cooling algorithm monitors also critical component temperatures and adjust fan rotation speed
accordingly.
Cooling system tolerates up to three simultaneous fan failures if the faulty fans are in
different fan modules. In case of fan failure, the failure event notification is given to the
HW management system and the other fan speed is increased to maximum.
As an option there is an easily changeable air filter in the front panel.
8.4
Cooling in rack installation
The mcBSC modules can be installed in standard 19” rack according to NSN rack installation requirements. Several modules can be installed on top of each other. The air ven-
DN0947925
Id:0900d80580a56484
Confidential
47
Mechanical design and power supply system
Multicontroller BSC and Multicontroller Transcoder
Product Description
tilation goes from the front to the rear side, which is to be taken into account in site
cooling planning.
The ambient temperature in the equipment room must be within the limits of the shown
in Table 11. It is recommended to keep temperature in the range between +10 and +35
°C.
8.5
Power supply system
The power feed forms a hierarchical system with function and overload protection on
every level. Redundancy is implemented by duplicating power feed equipment from the
battery feed or mains supply to the module internal functional entities.
Basic concept of power supply system are two field replaceable, hot swappable power
units. Either AC or DC units can be used according to the power feed requirements.
Figure 23
Rear view of AC and DC power supply modules
In DC power installations the battery voltage is fed to the modules through duplicated
DC front-ends. The battery voltage is -48VDC/-60VDC nominal.
In AC power installations the same mcBSC/mcTC module is equipped with duplicated
230 VAC front-ends.
With both AC and DC power feed options, optional power distribution units (PDU) can
be used in rack installations to fed the power to module AC or DC front-ends.
8.6
Electrical specification
Table 8 and Table 9 provide AC and DC power requirements of the mcBSC and the
mcTC modules.
AC power requirements
Nominal input voltage
Table 7
48
230 VAC
AC power requirements
Id:0900d80580a56484
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Mechanical design and power supply system
AC power requirements
Operating voltage range
180 VAC – 264 VAC
Frequency range
47 Hz - 63 Hz
Hold-up time
20 ms (230 VAC 50 Hz)
Power factor
>0.95 at 90% of full load
Safety
IEC60950-1
Table 7
AC power requirements (Cont.)
DC power requirements
Nominal input voltage
-48 VDC - -60 VDC
Operating voltage range
-40 VDC - -72 VDC
Table 8
DN0947925
DC power requirements
Id:0900d80580a56484
Confidential
49
Reliability
Multicontroller BSC and Multicontroller Transcoder
Product Description
9 Reliability
By compact design the mcBSC and the mcTC are made extremely fault-tolerant. Great
attention is paid to the reliability of operation. At least 99.999% availability on network
element level is targeted as global average. All centralized functions of the network
element are protected in order to guarantee high availability of the system. Hardware
and software of the system are constantly supervised with back-up components ready
for use in the event of failure. When a defect is detected in an active functional entity, a
spare entity is activated by an automatic recovery function.
Simplicity and speed of maintenance procedures offer extremely high availability. The
maintenance is improved and made easy by simplified modularity of the equipment,
automatic fault detection procedures and elimination of downtime by using a hot standby
unit in the event of a failure.
9.1
Fault management
The mcBSC system is a loosely coupled, fault-tolerant distributed system with some
centralized functions. The mcBSC system maintenance functions conform to the idea of
loose coupling of autonomous control computers. This means, for example, that state
control mechanisms do not depend on any centralized hardware, control computers
control their own software and are able to restart on their own by asking for the appropriate loading services, and an individual program block failure or an individual hardware
failure has a minor effect on the overall operation of the whole system. The fault situation
is hardly ever so bad or complex that the whole system has to be restarted.
In most cases, a restart in a program block, preprocessor, or a single control computer
is enough. The control computer states are controlled from a centralized point which can
be dynamically reallocated from the OMU to a pair of control computers when, for
example, an OMU with no redundancy fails. This means that this centralised function
has 3N redundancy. Only the control computers are autonomous as described above.
The preprocessors run under the control of a master computer.
9.2
Overload protection
The mcBSC overload protection handles excessive traffic or signalling load by limiting
the load level of the mcBSC's main CPUs and preprocessors, and also provides information of excessive load, so that preventive actions can be taken. The main cause of
this kind of load might be related to special end-user behaviour and is mainly related to
radio network planning and dimensioning according to the required level.
For more information on BSS overload protection, see BSS overload protection in BSS
(BSC) Traffic Handling Capacity, Network Planning and Overload Protection.
9.3
Redundancy principles
The following redundancy schemes are applied for various units:
Duplication (2N)
If the spare unit is designated for only one active unit, the software in the spare unit is
kept synchronized. The spare unit can be said to be in hot standby. This redundancy
principle is called duplication, abbreviated "2N".
50
Id:0900d80580a56485
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Reliability
Replacement (N+M)
One or M spare units is (are) allocated for a larger group of active units (M is greater or
equal 1). The spare unit(s) is (are) kept in cold standby, which means that synchronization of the spare unit is performed during the switchover procedure. Several spare units
can be available.
Load sharing (SN+)
If the unit group acts as a resource pool, it is allocated with or without spare units. The
number of units in the pool is selected, so that there is a certain amount of extra capacity.
If a few units of the pool are disabled because of faults, the whole group can still perform
its designated functions. This redundancy principle is called load sharing, abbreviated
"SN+"
None
Some functional units have no redundancy at all. This is because a failure in them does
not prevent the function or cause any drop in the capacity.
Redundancy model
Redundancy of the mcBSC and the mcTC
The mcBSC and mcTC are highly available systems. The smallest field replaceable unit
(FRU) is one module. The HW architecture supports isolation of the effect of the certain
HW fault to as small part of the module as possible. If the nature of a failure is a SW
fault, recovery is usually possible. The redundancy concept is based on redundancy of
the services that different logical functional units (FU) provide. If one of the logical FU
fails, another FU of the same type takes care of the services. Redundancy principle of
each logical FU of the mcBSC and the mcTC is shown in Table 6.
Functional unit
Redundancy principle
MCMU
2N
OMU
None
BCXU
N+1
PCUM
N+M
ETM
N+M, SN+
PTU
1+1
mcTC
SN+ (Module redundancy on network
level)
Table 9
Redundancy princples
case of OMU failure, traffic handling capability and recovery related system mainteg Innance
functions of OMU are taken over by MCMU functional unit.
Redundancy of the power distribution system
The power feed is protected by duplicated power supply from mains power, rectifiers or
batteries. Failure of one power supply unit does not affect availability of the controller
module, because the remaining power supply is capable to provide sufficient power
required by it.
DN0947925
Id:0900d80580a56485
Confidential
51
Reliability
Multicontroller BSC and Multicontroller Transcoder
Product Description
Redundancy of the cooling system
Each module is provided with three pairs of fans, each with 1:1 redundancy. In the event
of a fan failure, an alarm is raised and operational fans are controlled to full rotation
speed, maintaining sufficient cooling capacity in specified environmental conditions.
Redundancy of the controller module hard disks
Redundancy principle of the mcBSC module hard disks is 1:1. There are 2 AMC slots in
each controller module, in which hard disk is installed. It is sufficient to have 2 hard disks
installed in one network element, regardless the amount of controller modules belonging
to the configuration.
System availability
The mcBSC and the mcTC are designed to meet the availability requirements of the
ITU-T. The following design objectives have been adopted to ensure that the unavailability of the mcBSC and the mcTC is very low.
HW Intrinsic availability performance
[MRT = 1.0 h]
mcBSC system configuration with BCN-A
hardware
Availability
MDT
MTBFNE
Minimum configuration
0.999 99992
0.05 min/ year
12 900 000 h
Medium configuration
0.999 99992
0.05 min/ year
13 000 000 h
Maximum configuration 0.999 99992
0.05 min/ year
13 100 000 h
Table 10
The predicted availability, mean down time (MDT) and mean operating
time between system failures (MTBFNE) for the complete system
HW Intrinsic availability performance
[MRT = 1.0 h]
mcBSC system configuration with BCN-B
hardware
Availability
MDT
MTBFNE
Minimum configuration
0.999 999934
0.035 min/year
15 100 000 h
Medium configuration
0.999 999932
0.0355 min/year
14 800 000 h
Maximum configuration 0.999 999935
0.0344 min/year
15 300 000 h
Table 11
52
The predicted availability, mean down time (MDT) and mean operating
time between system failures (MTBFNE) for the complete system
Id:0900d80580a56485
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Reliability
HW Intrinsic availability performance
[MRT = 1.0 h]
mcTC system configuration with BCN-A
hardware
Availability
MDT
MTBFNE
Minimum configuration
0.999 95515
23.6 min/ year
22 300 h
Medium configuration
0.999 99994
0.03 min/ year
17 600 000 h
Maximum configuration 0.999 99994
0.03 min/ year
18 000 000 h
Table 12
The predicted availability, mean down time (MDT) and mean operating
time between system failures (MTBFNE) for the complete system
Note that the values above are predictions and cannot be used as guaranteed values in
contracts. Simplicity and speed of the maintenance procedures are the prerequisites for
the availability of the mcBSC and the mcTC. The maintenance is improved by the
modular structure of the equipment, automatic fault detection procedures, and elimination of downtime by using a hot standby unit in the event of a failure. The mean active
repair time of the mcBSC is estimated at one hour.
For more detailed information see Multicontroller BSC Availability Performance Prediction.
Planned downtime
The mcBSC computing platform makes it possible to minimize the downtime caused by,
for example, software upgrades. The mcBSC software can be downloaded without any
disturbance to user data traffic, but the activation of new software requires computer unit
restarts. Thanks to the trial configuration, the possible downtime can be minimized. The
trial configuration means that first the new software is loaded into spare units, then a unit
switchover is performed, that is, the spare units are switched into active state and vice
versa, and finally the new software is loaded into the primary units.
DN0947925
Id:0900d80580a56485
Confidential
53
Operational environment
Multicontroller BSC and Multicontroller Transcoder
Product Description
10 Operational environment
10.1
Standards for environmental requirements
ETSI and IEC standards
The network elements comply with the ETSI standards ETSI EN 300 019-1-1, ETSI EN
300 019-1-2 and ETSI EN 300 019-1-3, as specified in the following tables.
Conditions
Normal operation
Standard
Class
Mechanical conditions
ETS 300 019-1-3
3.2
Other conditions 1)
ETS 300 019-1-3
3.1 E
ETS 300 019-1-2
2.3
Chemically active substances,
mechanically active substances and
mechanical conditions
ETS 300 019-1-1
1.2
Other conditions
ETS 300 019-1-1
1.2
Transportation
Storage
Table 13
ETSI standards defining the environmental requirements for the network
elements
1) Contrary to ETSI EN 300 019-1-3, Class 3.1E, power-up not allowed below 0°C.
The ETSI standards defining the environmental conditions are based on corresponding
IEC standards, which are listed in the following table.
Conditions
Normal Operation
Transportation
Table 14
54
Standard
Class
Climatic conditions 1)
IEC 60721-3-3
K3
Special climatic conditions
IEC 60721-3-3
Z2, Z4
Lightning Protection Zone
IEC 61312-1
Z2
Overvoltage Category
IEC 60664-1
I, II
Biological conditions
IEC 60721-3-3
B1
Chemically active substances
IEC 60721-3-3
C2 (C1)
Mechanically active substances
IEC 60721-3-3
S2
Mechanical conditions
IEC 60721-3-3
M1
Earthquake resistance
IEC 60721-2-6
-
Climatic conditions
IEC 60721-3-2
K4
Biological conditions
IEC 60721-3-2
B2
Chemically active substances
IEC 60721-3-2
C2
Mechanically active substances
IEC 60721-3-2
S2
Mechanical conditions
IEC 60721-3-2
M2
IEC standards defining the environmental requirements for the network
elements
Id:0900d80580a564d5
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
Conditions
Storage
Table 14
Operational environment
Standard
Class
Climatic conditions
IEC 60721-3-1
K4
Special climatic conditions
IEC 60721-3-1
Z2, Z3, Z5
Biological conditions
IEC 60721-3-1
B2
Chemically active substances
IEC 60721-3-1
C2
Mechanically active substances
IEC 60721-3-1
S3
Mechanical conditions
IEC 60721-3-1
M2
IEC standards defining the environmental requirements for the network
elements (Cont.)
1) Contrary to IEC 60721-3-3K3, power-up not allowed below 0°C.
NEBS standards
The Network Equipment Building System (NEBS) is a set of Telcordia (former Bellcore)
standards, the purpose of which is to unify hardware requirements and help operators
to evaluate the suitability of products for use in their networks. Compliance with NEBS
is usually required by Regional Bell Operator Companies (RBOC).
The network element hardware is NEBS Level 3 compliant as specified in SR-3580,
covering GR-63-CORE and GR-1089-CORE standards in Central Office or equivalent
premises, as applicable for Type 2 equipment specified in appendix B of GR-1089CORE.
DN0947925
Id:0900d80580a564d5
Confidential
55
Multicontroller BSC and Multicontroller Transcoder
Product Description
10.2
Conditions during operation
Climatic conditions
The network elements are designed to operate in temperature-controlled, weather-protected conditions. The limits for climatic conditions during operation are shown in the following table.
Exceptional 1)
Normal
Recommended
2)
Temperature range
–5°C to +50°C
+5°C to +40°C (nominal
+23°C)
+20°C to +30°C
Change rate of temperature
0.5°C/min
<0.5°C/min (nominal
0.1°C/min)
-
Relative humidity
5% to 93%
nominal 50%
Less than 50% 3)
Table 15
Limits for temperature and humidity during operation
1) Exceptional conditions may occur following the failure of the temperature controlling
system. The network elements can operate under the exceptional conditions in short
term (refers to not more than 96 consecutive hours and a total of not more than 15 days
in one year). During the site normal operation the climatic conditions should be within
the normal ranges.
2) The climatic conditions which are recommended to be maintained at the facility level
to ensure the long-term reliable operation of the equipment.
3) When measured in operating temperature of +23°C.
g Do not power up the equipment in temperatures below 0°C/32°F.
Temperature and humidity
Normal operating temperature range for the network elements is between +5°C and
+40°C. However, it is recommended that temperature is set such that air intake for the
network element is between +20°C and +30°C. This helps to save energy compared to
lower temperatures. To keep the temperature in the equipment rooms suitable for the
equipment and personnel, heat (thermal energy) must be removed from the premises.
It is recommended that relative humidity is less than 50% when measured in operating
temperature of +23°C. Relative humidity is temperature and pressure dependent.
Therefore, to maintain the same absolute humidity (i.e. same water vapour content in a
given volume of air), the targeted relative humidity valued must be lowered when operating temperature is higher than +23°C. Humidity control helps to reduce the effects of
corrosive gases that might be contained in the air.
Altitude
The maximum ambient temperature of +50°C is allowed to an elevation of between 61m
to 1829 m above sea level. With a temperature of +40°C the maximum intended operational altitude is 1829m to 3960 m above sea level.
Dust
The equipment has been designed for use in an urban industrial area where the
maximum annual average of dust concentration is 200 µg/m3 (total suspended particles). The equipment is protected against the known harmful effects of dust. However,
56
Id:0900d80580a564d3
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
the physical and chemical properties of dust in the environment vary and may cause
problems which are not always perceptible. Therefore, the equipment rooms must be
kept clean and appropriate instructions must be followed to ensure operational reliability
and maximum life span of the equipment.
If the environment contains large amounts of active dust particles, the use of air filters
in the site ventilation system is recommended. Adequate filtering in the equipment
rooms is generally achieved with filters that trap 40 to 70% of the dust particles or whose
weight separating capacity is ≥90%. The use of electrical or oil filters is not allowed. The
filters must be replaced every six months.
Chemical impurities
The network elements are designed to withstand impurities in quantities found in the air
in a normal urban industrial area. Indoor particulate levels are a function of the degree
of filtration of the outdoor air and the recirculated air.
Acceptable levels of chemically active substances are according to ETSI EN 300 0191-3 and according to GR-63-CORE (indoor levels). Lower value of each substance is
recommended. To be able to withstand air impurities, the humidity of site should be controlled (relative humidity less than 50%). The values are shown in the following table.
Environmental parameter
Unit 1)
Concentration
ETSI
Telcordia
EN 300 019-1-3
GR-63-CORE
Class 3.1
Mean value
Mean value 2)
No 3)
No
ppb 4)
110
50
mg/m 3
0.3
cm3/m3
0.11
ppb
71
mg/m 3
0.1
cm3/m3
0.071
ppb
34
mg/m 3
0.1
cm3/m3
0.034
ppb
66
mg/m 3
0.1
cm3/m3
0.066
ppb
12
mg/m 3
0.01
cm3/m3
0.012
ppb
1400
a) Salt mist: sea and road salt
b) Sulphur dioxide (SO2)
c) Hydrogen sulphide (H2S)
d) Chlorine (Cl2)
e) Hydrochloric acid(HCI)
f) Hydrofluoric acid(HF)
g) Ammonia(NH 3)
Table 16
DN0947925
40
5 (HCl+Cl2)
5 (HCl+Cl2)
N/S
500
Chemically active substances
Id:0900d80580a564d3
Confidential
57
Multicontroller BSC and Multicontroller Transcoder
Product Description
Environmental parameter
Unit 1)
Concentration
ETSI
Telcordia
EN 300 019-1-3
GR-63-CORE
Class 3.1
Mean value
Mean value 2)
h) Ozone(O3)
i) Nitrogen oxides (NOx) 5)
Volatile organic compounds
(boiling point > 30 °C)
Table 16
mg/m 3
1.0
cm3/m3
1.4
ppb
25
mg/m 3
0.05
cm3/m3
0.025
ppb
260
mg/m 3
0.5
cm3/m3
0.26
ppb
N/S
125
200
1200
mg/m 3
5
cm3/m3
1.2
Chemically active substances (Cont.)
1) The values given in cm 3/m3 have been calculated from the values given in mg/m3 and
refer to 20°C. The table uses rounded values.
2) Mean values are the average values (long-term values) to be expected.
3)Salt mist may be present at sheltered locations of coastal areas and offshore sites.
4) Gas concentration X(ppm) = 24 x Y(mg/m 3)/Mw when the temperature is 20°C and the
air pressure is 760 mm Hg; Mw is the molecular weight in g; ppm = parts per million = 1
x 10-6 = cm3/m3 = 1000 ppb (parts per billion).
5) Expressed as the equivalent values of nitrogen dioxide.
Air quality measurement
If the environment is suspected or found to be corrosive, air quality measurements
should be performed.
The level of corrosion should be tested with copper and silver coupons ("reactivity monitoring") using the specification ISA-71.04-1985 as reference. The silver coupons should
be used in addition to copper even though they are not required by the ISA specification.
The levels of specific substances in the air can be also directly measured by using
suitable test equipment. Measured gas concentrations should be compared against the
acceptable levels of chemically active substances stated by ETSI EN 300 019-1-3.
Nokia Siemens Networks equipment is able to withstand ISA G2 (Moderate) corrosive
environment based on gas concentrations specified for that class, except if there is
ammonia in the air that exceed the specified limits of 1400 ppb.
Maximum conditions: ISA G2 (Moderately corrosive environment):
•
•
58
Relative humidity RH less than 50%
Copper reactivity rate of less than 1000 Å/month
Id:0900d80580a564d3
Confidential
DN0947925
Multicontroller BSC and Multicontroller Transcoder
Product Description
•
Silver reactivity rate of less than 1000 Å/month
Acoustic noise
Attended Telecommunication Equipment Room Class 3.1 in the ETSI 300 753 calls for
a sound power noise emission limit of 7.2 bels [LWAd].
Telcordia GR-63-CORE (Issue 4, April 2012) acoustic noise criteria for attended room
call for acoustic noise not exceeding 78 dB [LWAd] at ambient temperature of 27°C.
BCN hardware is compliant with the above-mentioned requirements.
Mechanical conditions
The mechanical conditions allowed during operation are shown in the following table.
Vibration
Amplitude
1.5 mm, f = 2 to 9 Hz
Acceleration
5 m/s2, f = 9 to 200 Hz
Shocks
Table 17
40 m/s2, 22 ms
Mechanical conditions allowed during operation
Earthquake
The network elements are earthquake durable, compliant to GR–63–CORE (NEBS
zone 4) requirements. For more information, see the Installation documentation.
DN0947925
Id:0900d80580a564d3
Confidential
59
Multicontroller BSC and Multicontroller Transcoder
Product Description
10.3
Conditions during transportation and storage
w NOTICE: Risk of equipment damage.
•
•
Keep the equipment in its original package during storage and transportation. This
reduces the risk of mechanical damage, protects units against electrostatic discharge (ESD), and maintains traceability.
Keep the equipment in its original package during transportation. Minimum air
pressure during transportation is 70 kPa (which corresponds to an altitude of 3000
m) to guarantee the integrity of the humidity seal.
Climatic conditions
Some temperature recommendations are given in the following table.
Temperature
min.
max.
Transportation
–40°C
+70°C
Short-term storage1
–25°C
+55°C
Long-term storage
–5°C
+50°C
Table 18
Temperature limits during transportation
1 Max. 60 consecutive days
Relative humidity during transportation and storage may vary between 5% and 95%.
During long-term storage, humidity between 20% and 75% is recommended.
Mechanical conditions
The permitted mechanical conditions during transportation are shown in the following
table.
Vibration
Amplitude
3.5 mm, f = 2 to 9 Hz
Acceleration
10 m/s2 , f = 9 to 200 Hz
15 m/s2 , f = 200 to 500 Hz
Random vibration
Acceleration
spectral density
300 m/s2 , 6 ms
Shocks
Table 19
60
1 m2 /s3 , f = 10 to 200 Hz
Mechanical stress allowed during transportation
Id:0900d80580a564d4
Confidential
DN0947925