Multicontroller BSC, Product Overview with Q&A

Multipurpose, Scalable, Compact

Version 25 – April 2016

April 2016 - 1 / 37 © Nokia Solutions and Networks 2016

Confidential
This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia Solutions and Networks. All rights are reserved. Copying, including
reproducing, storing, adapting or translating, any or all of this material requires the prior written
consent of Nokia Solutions and Networks. This material also contains confidential information,
which may not be disclosed to others without the prior written consent of Nokia Solutions and
Networks.

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is not an official
customer document and Nokia Solutions and Networks does not take responsibility for any
errors or omissions in this document. This document is intended for the use of Nokia Solutions
and Networks customers only for the purposes of the agreement under which the document is
submitted.

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.

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 might
arise from the use of this document or the information in it.

THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY
APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, ARE MADE IN RELATION TO THE
ACCURACY, RELIABILITY OR CONTENTS OF THIS DOCUMENT. NOKIA SOLUTIONS AND NETWORKS
RESERVES THE RIGHT TO REVISE THIS DOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR
NOTICE.

April 2016 - 2 / 37 © Nokia Solutions and Networks 2016

Confidential
Contents
1 Overview ................................................................................................................................ 5

2 Multicontroller BSC in Nokia Single RAN (SRAN) ............................................................... 5

3 Introducing Multicontroller BSC ......................................................................................... 6

3.1 Multicontroller BSC is an evolution for existing Flexi BSC installations ....................... 8
3.2 Multicontroller BSC value points ........................................................................................ 9
3.3 Configurations and capacity ............................................................................................... 11
3.4 Multicontroller BSC – efficient All-IP transport inbuilt .................................................... 13
3.4.1 Multicontroller BSC VRRP / HSRP site IP solution ............................................................ 15
3.4.2 Multicontroller BSC OSPF site IP solution ......................................................................... 16
3.5 External Interfaces ............................................................................................................... 16
3.6 Multicontroller BSC evolution towards Multicontroller RNC .......................................... 17
4 Software and functionality.................................................................................................. 21

4.1 Advanced functionalities with Multicontroller BSC.......................................................... 22

4.1.1 Network Resiliency for mcBSC ............................................................................................ 22
4.1.2 Integrated CS Data Support in mcBSC.............................................................................. 24
5 Positioning against competition ........................................................................................ 25

5.1 Huawei BSC6910 .................................................................................................................. 25

5.2 Ericsson Evo Controller 8000 ............................................................................................. 26
5.3 Differentiating space efficiency with unique modularity ............................................... 26
6 Availability .............................................................................................................................. 27

7 Q&A ........................................................................................................................................ 28

7.1 General ................................................................................................................................... 28

7.2 Multicontroller Platform ...................................................................................................... 30
7.3 Multicontroller BSC implementation ................................................................................. 32
7.4 Transcoding ........................................................................................................................... 35
7.5 Functionality .......................................................................................................................... 35

April 2016 - 3 / 37 © Nokia Solutions and Networks 2016

Confidential
7.6 Transport ............................................................................................................................... 36

April 2016 - 4 / 37 © Nokia Solutions and Networks 2016

Confidential
1 Overview
Ever increasing traffic with much needed future-proof network evolution towards new technologies ahead
of us, paves the road for the Multicontroller Platform, being a new concept enabling operators to provide
the needed capacity in an unrivaled footprint and scalability.

Voice is still key service especially in GSM and even there unique new innovations like Orthogonal Sub-
Channel (OSC) boost the capacity and usage. Multicontroller BSC and Multicontroller RNC are the
applications of the common platform evolution aimed to increase the flexibility and versatility protecting
operator’s investment. The hardware is based on the latest component technology and research efforts
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 platform is designed to be modular and adaptive supporting flexible GSM TRX and PS data capacity as
well as WCDMA throughput and cell connectivity in various network topologies. The revolutionary concept
fits networks from highly centralized, with high capacity BSC or RNC located at the switch site, to a
distributed BSCs or RNCs located close to remote and small BTS areas. The combination of highly flexible
hardware and distributed software makes the capacity expansions and functionality upgrades easy to
optimize according to requirements set by network and end-user advanced services.

The small footprint widens the installation options allowing, for the first time in the industry, saving
opportunities in real estate investment. Cost efficiency made a quantum leap in the spare parts
management since plug-in units have been highly reduced in types and overall numbers.

Combining the compact and scalable hardware platform to the modular and flexible software creates a
new way of thinking of network controllers, where the capacity can easily be optimized to meet the
operator’s capacity and network topology requirements. The Multicontroller BSC configurations can be
optimized according TRX coverage or PS data capacity needs. As a clear benefit of this platform on top of
high maximum capacity is also the downward scalability with very small initial configurations to address all
different needs.

2 Multicontroller BSC in Nokia Single RAN (SRAN)

The concept behind the Single Radio Access Network (Single RAN, SRAN) is to operate different radio
technologies on multi-purpose hardware platforms: Multiradio Controller Platform and Single RAN BTS
(SBTS). Both Multicontroller BSC and Multicontroller RNC are based on Multiradio Controller Platform,
SBTS is based on Flexi Multiradio 10 BTS.

Single RAN offers the best performance through enabling simultaneous coordination and operation of a
variety of different radio access technologies (RATs). SRAN concept includes also Common Operability and
Common Transport solutions for all RATs in a single SBTS logical node.
April 2016 - 5 / 37 © Nokia Solutions and Networks 2016
Confidential
Nokia solution enables a fully flexible evolution to Single RAN. With re-farming, sharing, modernization and
evolution. Single RAN enables operators to simplify their networks, reduce costs, grow their business, and
balance investments more efficiently. On top of Multiradio Platform controllers (Multicontroller BSC and
Multicontroller RNC) a new BTS type, SBTS, is introduced with its three key functionalities: Common
Transport, Common Operability, and System Module sharing with shared RF fibers. SRAN BTS as well as
Multicontroller BSC or Multicontroller RNC can coexist in the same network with dedicated RAT BTSs.

In Single RAN all radio technologies are provided at the same BTS site more cost efficiently than in
previous solutions. Single RAN introduces Common OAM functionality, all network elements related to the
Single RAN site are integrated into the same NetAct.

Figure 1: Single RAN network architecture

3 Introducing Multicontroller BSC

Nokia has a track record of high performing BSC portfolio. Final development step in the legacy BSC era
was Flexi BSC, introduced with RG10 SW release at 2009. Latest development in Nokia’s high performing
BSC portfolio is Multicontroller BSC, introduced at 2012.

Multipurpose, compact and scalable Multicontroller BSC, built on top of the unique Multiradio Controller
Platform responds to the new challenges being there for the controller design.

April 2016 - 6 / 37 © Nokia Solutions and Networks 2016

Confidential
Figure 2: Technology and service evolution sets new challenges for controller design

Multicontroller BSC is a completely new network controller concept for providing the needed capacity and
connectivity:

- One platform, several technologies : High capacity and future-proof GSM and WCDMA controllers
for IP-based radio networks on the same hardware platform

- Modular architecture : Scale up capacity and functionality flexibly, rapidly and cost effectively

- Built in reliability : Extreme fault tolerance with maximum reliability – all centralized functions in
the network element are protected

- Reduced operational costs : Simple and extremely compact modular architecture – easy
installation with minimum site space

- Highly cost effective spare part management – very low number of hardware parts

- Most scalable BSC based on modular Multicontroller Platform ranging from very compact 2
module BSC up to the highest capacity configurations supporting 4400 TRX, 4400 BTS sectors
and 4400 BTS sites with over 26 000 Erlangs
- Supports Flexi EDGE BTSs, Flexi Multiradio BTSs, SBTS and further BTS evolution according GSM
Release roadmap
- Supports advanced IP transmission features by design i.e. Packet Abis, Gb/IP and AoIP. TDM
interfaces for BTS connections with Packet Abis/TDM are supported with Packet Abis Network
Media Conversion feature (BSS101414), where Ethernet / TDM media conversion (MLPPP) is done
within transport path with external equipment (e.g. with Multicontroller BSC site router).
- GSM voice transcoding efficiently with MGW (AoIP, TC in MGW)
- Further improved footprint and energy efficiency

April 2016 - 7 / 37 © Nokia Solutions and Networks 2016

Confidential
 - Implementation efficiency from feature parity and common SW release with Nokia’s legacy BSC
portfolio (excluding features not applicable with All-IP Multicontroller HW Platform)

3.1 Multicontroller BSC is an evolution for existing Flexi BSC installations

Existing Flexi BSC installations and new Multicontroller BSCs can complement each other and offer
together flexible future-proofness for operators.

- Compact Multicontroller BSC can be co-sited with existing Flexi BSCs (or other legacy BCSs) for a
future-proof SRAN evolution path within existing networks.
- With co-siting the latest evolution options are introduced to the installed base simply by
introducing a compact Multicontroller BSC into existing BSC site. With IP based interfaces of
Multicontroller BSC, co-siting provides a smooth and future-proof evolution for new BTS site
installations as well as for BTS modernisations with Packet Abis
- On top of IP interfaces provided by Multicontroller BSC for radio network with Packet Abis, existing
Flexi BSC (or other legacy BSC) continues to offer traditional E1/STM-1 Dynamic Abis connections
for the existing legacy radio network according its lifecycle

Existing Flexi BSC with co-sited Multicontroller BSC creates a powerful BSC site providing support for the
existing installed legacy radio network along with capabilities to evolve for the latest technology, SRAN,
IP/Ethernet transport and further towards HW reuse for RNC implementations.

Existing Flexi BSC can continue to serve existing legacy RNW with Dynamic Abis according its lifecycle
without any mandatory HW investments. When legacy RNW is being gradually modernized – e.g. due to LTE
introduction to the same existing BTS site, bringing in efficient IP transport, BSC capacity for the
modernized and Packet Abis capable RNW is provided with new co-sited Multicontroller BSC.

Figure 3: Compact Multicontroller BSC co-sited with legacy BSC – gradual evolution towards SRAN

April 2016 - 8 / 37 © Nokia Solutions and Networks 2016

Confidential
3.2 Multicontroller BSC value points

Simplified and extremely small modular structure makes installation fast and easy. Additionally less HW
parts with common modules contributes automatically to clearly lower spare part costs.

Figure 4: Multicontroller BSC – Higher capacity with higher energy and space efficiency

Multicontroller BSC key value points:

High capacity and efficiency

- Support for 4400 TRXs and over 26 000 Erlangs minimises the number of network elements
- High integrated packet data capacity for EDGE evolution (up to 87 040 Packet Abis channels)
- Excellent capacity per footprint ratio
- Excellent power consumption per capacity ratio
- Future path for Single RAN evolution with module reuse in Multicontroller RNC configurations
- Efficient voice transcoding in MGW with AoIP, TC in MGW
- Simple capacity extensions with modular Multicontroller Platform

April 2016 - 9 / 37 © Nokia Solutions and Networks 2016

Confidential
Figure 5: Multicontroller BSC – modular Multicontroller Platform, simple capacity extensions

Completely integrated IP transmission solutions:

- Optimised for integrated IP in all interfaces
- Native IP for efficient Packet Abis / Ethernet, Packet Abis / TDM (MLPPP) and AoIP solutions

Figure 6: Multicontroller BSC – integrated IP transport

April 2016 - 10 / 37 © Nokia Solutions and Networks 2016

Confidential
3.3 Configurations and capacity

High scalability is reached by just adding modules starting from the two module fully HW redundant
minimum configuration. Additional module extensions enable TRX or PS data capacity extensions
according traffic and connectivity needs. Maximum configuration of Multicontroller BSC contains eight
modules.

Figure 7: Multicontroller BSC – modular building blocks

Connectivity and traffic handling capacity of Multicontroller BSC is:

− Up to 4 400 TRXs
− Up to 26 400 Erlangs
− Up to 87 040 Packet Abis channels for PS data

April 2016 - 11 / 37 © Nokia Solutions and Networks 2016

Confidential
Figure 8: Multicontroller BSC configurations and capacity steps

Examples of Multicontroller BSC configurations, modular Multicontroller HW Platform enables various

configuration options within the same site installation by default.

Figure 9: Examples of Multicontroller BSC configurations

April 2016 - 12 / 37 © Nokia Solutions and Networks 2016

Confidential
Figure 10: Examples Multicontroller BSC/RNC configurations

3.4 Multicontroller BSC – efficient All-IP transport inbuilt

Multicontroller BSC is equipped with efficient All-IP transport by design and supports different interfaces
as below :

- Packet Abis / Ethernet

- Packet Abis / TDM (MLPPP with TDM Ethernet media conversion in site equipment or within
transport path and with Packet Abis Network Media Conversion – feature BSS101414)
- Gb over IP
- A over IP (voice transcoding in MGW : AoIP, TC in MGW)
- SS7 over IP (SIGTRAN)
- O&M over IP
- Lb over IP

April 2016 - 13 / 37 © Nokia Solutions and Networks 2016

Confidential
Figure 11: Multicontroller BSC external interfaces

Actual Multicontroller BSC site implementation requires mandatory site equipment. Multicontroller BSC
implementation provides support for two site connectivity options.

April 2016 - 14 / 37 © Nokia Solutions and Networks 2016

Confidential
3.4.1 Multicontroller BSC VRRP / HSRP site IP solution
Traffic between Multicontroller BSC and Site Equipment is Ethernet (L2) switched

– L2 Ethernet switching between Multicontroller BSC modules and site equipment

– VLANs that needs to be switched or routed outside the Multicontroller BSC are allowed on links
towards site equipment

– Virtual Gateway protocol functionality HSRP/VRRP implemented on site equipment

– Loop prevention at site equipment – L3 interface between the site equipment pair (breaks the
broadcast domain for Multicontroller BSC VLANs visible to the site equipment)

Figure 12: Multicontroller BSC L2 VRRP/HSRP site IP solution

April 2016 - 15 / 37 © Nokia Solutions and Networks 2016

Confidential
3.4.2 Multicontroller BSC OSPF site IP solution
Traffic between Multicontroller BSC and Site Equipment is IP (L3) routed

– L3 IP routing between Multicontroller BSC modules and site equipment

– OSPF or static routing

– OSPF with Fast Hello applied

– L3 functionality is activated in Ethernet switches of the two basic modules in Multicontroller BSC
configuration (Feature BSS101431 – L3 connectivity for Multicontroller BSC is required)

– VRRP applied internally for network connectivity redundancy

Figure 13: Multicontroller BSC L3 OSPF site IP solution

3.5 External Interfaces

Network interfaces in Multicontroller BSC are used for external connectivity as well as for interconnections
between modules within the Multicontroller BSC network element. Network interfaces are located in the

April 2016 - 16 / 37 © Nokia Solutions and Networks 2016

Confidential
front panel of each module. One Multicontroller BSC module contains 10 pcs of 1G Ethernet interfaces
and 9 pcs of 10G Ethernet interfaces.

Figure 14: Multicontroller BSC network interfaces for external traffic (Packet Abis, AoIP, GboIP, O&M,
SIGTRAN) from mcBSC basic modules

In addition to network interfaces, additional external connections for external alarms and synchronization
are provided from the module.

For external connections to mandatory site routers Multicontroller BSC provides options to connect either
with 1G or with 10G interfaces through relevant SFP modules. Redundant site router connections are
configured through two basic modules in Multicontroller BSC configuration.

3.6 Multicontroller BSC evolution towards Multicontroller RNC

Modular Multicontroller Platform enables smooth evolution between GSM and WCDMA with simple basic
concepts:

- Module HW used in BSC can be reused in RNC configurations

- Product configurations can be flexibly changed by moving HW modules from BSC configuration to
RNC configuration
- Concurrent operation of BSC and RNC in the same HW module is not supported. One module is
always either in BSC or in RNC network element configuration

April 2016 - 17 / 37 © Nokia Solutions and Networks 2016

Confidential
Module HW reuse capability between BSC and RNC fully supports future network evolution from GSM to
WCDMA.

Figure 15: Two technologies – One Multicontroller Platform

Future network evolution with downward trend in GSM capacity requirements highly benefits from the
modular Multicontroller BSC implementation – according WCDMA capacity needs controller HW capacity
previously used for GSM can be transferred module by module into RNC use in order to provide higher
RNC capacity for increasing WCDMA traffic.

Figure 16: Transferring HW modules between GSM and WCDMA according traffic development

Multiradio Controller Platform implementation supports this network and technology evolution with
common HW platform componens, there are only two different types of HW processing units used for
GSM and WCDMA:

April 2016 - 18 / 37 © Nokia Solutions and Networks 2016

Confidential
 1. BJC-A HW processing unit used for GSM Control Plane processing
2. BMPP2-B HW processing unit used for GSM User Plane or WCDMA User Plane / Control Plane
processing

Figure 17: HW processing units in Multicontroller BSC HW module implementation

According the network element implementation BJC-A and BMPP2-B HW processing units are equipped in
Multicontroller Platform modules. Whether BJC-A HW units for GSM Control Plane processing are included
or not depends if the particular module is providing GSM Control Plane processing capacity – i.e. TRX
connectivity. Following table summarizes the processing units used in Multicontroller Platform HW
modules.

Figure 18: Summary of Multicontroller Platform module HW configurations and equipping of HW

processing units inside the modules

April 2016 - 19 / 37 © Nokia Solutions and Networks 2016

Confidential
With capability to transfer HW modules between GSM and WCDMA, modular Multicontroller BSC enables
excellent growth path and investment protection between these technologies.

Figure 19: Multicontroller BSC evolution towards Multicontroller RNC

Typical scenario when Multicontroller BSC modules are reused in Multicontroller RNC configuration can be
according the following:

1. Customer is seeing a downward need for PS data capacity in GSM => Multicontroller BSC PS data
capacity can be lowered by moving Multicontroller BSC PS data extension modules into
Multicontroller RNC configuration => customer will experience a higher capacity Multicontroller
RNC and a Multicontroller BSC with lower PS data capacity. Multicontroller BSC PS data extension
module does not contain any HW specific for GSM Control Plane processing.

In this scenario TRX connectivity and radio network coverage of Multicontroller BSC is maintained
and GSM is continued to be used to provide the existing TRX capacity and site coverage optimized
for voice.

2. Evolution can go further in a more dramatic way => amount of sites for GSM is physically reduced
=> coverage of GSM is reduced => resulting a lower required TRX capacity for Multicontroller BSC
=> Multicontroller BSC TRX extension modules can be moved to Multicontroller RNC configuration
to extend the RNC capacity => customer will experience a higher capacity Multicontroller RNC and
a GSM radio network with smaller coverage and lower number of sites.

Multicontroller BSC TRX extension module contains partly HW resources used specifically for GSM
Control Plane (BJC-A HW processing units) – before Multicontroller BSC TRX extension module is
moved to Multicontroller RNC configuration GSM specific Control Plane processing units are

April 2016 - 20 / 37 © Nokia Solutions and Networks 2016

Confidential
 removed and replaced with the WCDMA User Plane / Control Plane processing units (BMPP2-B HW
processing units)

3. The last step would be to move the remaining Multicontroller BSC basic modules into
Multicontroller RNC configuration => when this happens all the GSM sites are removed (or
transferred to another Multicontroller BSC) and there is no need for any GSM coverage =>
Multicontroller BSC disappears.

Multicontroller BSC basic modules contains partly HW resources used specifically for GSM Control
Plane – before Multicontroller BSC basic modules are moved to Multicontroller RNC configuration
GSM specific Control Plane processing units are removed and replaced with the WCDMA User
Plane / Control Plane processing units (BMPP2-B HW processing units)

Above described scenario is achieved with the modular Multicontroller BSC/RNC architecture – HW
modules are building blocks for the needed element configuration. High modularity enables vast amount
of different configuration options to follow the customer needs.

4 Software and functionality

Scalable functional architecture of Multicontroller BSC is enhanced from the field proven functional
architecture of Flexi BSC. This enables to reuse Flexi BSC software and therefore also provides similar
functionality. This means that the same BSC SW release is used within the GSM controller portfolio - with
Flexi BSC as well as with Multicontroller BSC. Similarly also learning curve in operations is smooth when
existing Flexi BSC experience can be fully utilized with Multicontroller BSC.

Figure 20: Scalable functional architecture of Multicontroller BSC

April 2016 - 21 / 37 © Nokia Solutions and Networks 2016

Confidential
In complete feature support there are differences between Flexi BSC and Multicontroller BSC – this relates
to All-IP Multicontroller HW Platform, which excludes BSC integrated TDM transport specific features from
the feature set of Multicontroller BSC.

4.1 Advanced functionalities with Multicontroller BSC

4.1.1 Network Resiliency for mcBSC

Network Resiliency for mcBSC improves the GSM network availability by protecting controllers against
exceptional incidents. During a single mcBSC outage or in exceptional and complete mcBSC site outage
scenarios, backup mcBSC can take over the responsibility and recover the radio network operation.

Figure 21: Network level redundancy for a radio network served by Multicontroller BSCs

Benefits for the Customer: mcBSC based GSM radio network resiliency and availability is improved against
single mcBSC outages or exceptional and complete mcBSC site outage scenarios - GSM service can be
recovered quickly after the failure scenario. Capability to protect several active mcBSCs with just one
backup mcBSC reduces the amount of additional equipment when building a GSM radio network with
network level controller redundancy.

Functional Description: Network Resiliency for mcBSC improves the GSM network availability by protecting
controllers against exceptional incidents. During a single mcBSC outage or in exceptional and complete
mcBSC site outage scenarios, backup mcBSC can take over the responsibility and recover the GSM radio
network operation within acceptable time interval.

With Network Resiliency for mcBSC feature it is possible to define a pair of mcBSCs where one is protected
mcBSC and the other one is backup mcBSC. One backup mcBSC can belong to several pairs and can
protect in maximum 16 other mcBSCs. This N+1 redundancy model with Network

April 2016 - 22 / 37 © Nokia Solutions and Networks 2016

Confidential
Resiliency for mcBSC feature enables backup mcBSC to serve one protected mcBSC at a time. During
normal network operation backup mcBSC is idle and does not carry any traffic. HW capacity step in backup
mcBSC needs to be equal or larger than in any protected mcBSC.

During normal network operation mcBSC configuration is being synchronized from protected mcBSCs to
the backup mcBSC through a specific BSC cluster O&M interface.

Figure 22: Protection against mcBSC failures or BSC site level disaster scenarios

In case of a failure in the protected mcBSC or because of maintenance activities, the backup mcBSC can
take over the GSM radio network operation after the operator has given the specific mcBSC switchover
MML command. After triggered mcBSC switchover, backup mcBSC is activated to use the BSC SW load of
protected mcBSC and dual homed BTSs are switched over from the protected mcBSC to the backup
mcBSC. After protected mcBSC has been recovered, operator triggers switchback from backup mcBSC by
a MML command.

April 2016 - 23 / 37 © Nokia Solutions and Networks 2016

Confidential
Figure 23: Dual homed BTS sites are switched over to the backup mcBSC

Prerequisites for the Network Resiliency for mcBSC feature:

- HW Rel2 is required in both backup mcBSC and in all protected mcBSCs. HW capacity step in
backup mcBSC must be equal or larger than in any protected mcBSC
- Feature BSS101413 “L3 connectivity for mcBSC” is required
- Licence Key for RG302362, “GSM 16 Release Upgrade License” must be installed
- Dual Homing capability is supported with BTS Flexi Multiradio 10. Packet Abis / Ethernet is
required for Dual Homed BTSs. Packet Abis / TDM can be optionally used for Single Homed BTS
sites.

4.1.2 Integrated CS Data Support in mcBSC

Integrated CS Data Support (mcBSC) enables CS Data Rate Adaptation functionalities in mcBSC ETMA
functional unit with AoIP, transcoding in MGW configuration. This SW based solution enables opportunities
to optimise the existing network architecture supporting the functionality with HW based mcTC
implementation.

April 2016 - 24 / 37 © Nokia Solutions and Networks 2016

Confidential
Figure 24: CS Data support for Multicontroller BSC with a SW functionality

Following CS Data service types are supported: FR CS Data 9.6 and 4.8 kbit/s (single slot in air interface),
Automatic Facsimile group 3. Connection types can be Transparent with fixed data rates, where rate
changes are not allowed. Also Non-transparent connections, where rate changes are allowed and either
Synchronous or Asynchronous modes are supported. Half Rate CS Data; CS Data for EDGE; and
additionally the optional data redundancy for the A-interface over IP are not supported.

Benefits for the Operator: mcBSC integrated support for different service types in AoIP, transcoding in
MGW configurations is extended to support now also CS Data and Fax services. Feature is license
controlled with migration option for deployments where HW based mcTC implementation for CS Data
Rate Adaptation is configured. When feature license is enabled then mcTC implementation for CS Data
Rate Adaptation will not be used, even if it is configured – here mcBSC connects CS Data calls to MGW via
ETMA functional unit. Similarly when feature license is disabled and when mcTC implementation is
configured then mcBSC connects CS Data calls to MGW via mcTC.

5 Positioning against competition

5.1 Huawei BSC6910

Huawei’s combined BSC/RNC product:

- They started with pure mechanical integration by putting independent BSC and RNC parts to the
same cabinet, but during development moved to use also partly same HW units with new
BSC6900 HW platform with “SW upgradeability”
- Huawei platform includes three types of plug-in units i.e. BSC specific, RNC specific and Common
- Due to traditional cabinet approach their combined product is always clearly weaker from capacity
perspective than using separate independent products – as an example Huawei BSC only
implementation has shown unpractically high TRX capacities (24 000 TRXs, Full IP, AoIP, 3
subracks) but clearly lower when combined RNC / BSC operation is implemented within the
cabinet (7 200 TRXs, Full IP, AoIP, 1 subrack)

For these reasons Nokia counter claim against such “combined controller” is stressing that given
combined controller spec. was not really providing strong benefits over independent BSC and RNC

April 2016 - 25 / 37 © Nokia Solutions and Networks 2016

Confidential
implementation in real networks, rather just being a compromise for both of them (waste of capacity and
resources). Such combined product is seen “as strong as the weakest half” easily leading to solution which
is optimal from capacity and configuration flexibility point of view only in a specific point of time when the
GSM/WCDMA traffic balance is same as capacity split between BSC and RNC. This also means that other
mutual benefits such as radio resource sharing is achievable already with GSM/WCDMA Inter-Working
functionalities and any claimed operability benefit comes already from existing common network
management system (NetAct).

Our counter argumentation should focus to highlight the strengths of Nokia approach over competition
by justifying the required flexibility which can be provided only by HW module based Multicontroller
Platform – e.g. it is easy to plan and implement innovative and site space saving installations where several
high capacity Multicontroller configurations (being e.g. Multicontroller BSCs, Multicontroller RNCs or mix of
Multicontroller BSC and Multicontroller RNC) are combined in to one physical installation. Nokia
Multicontroller Platform offers totally different type of approach over competition.

5.2 Ericsson Evo Controller 8000

Ericsson’s Evo Controller 8000 is a completely new solution. First it would offer capacity on par with
Ericsson’s legacy High Density BSC with the potential for RNC functionalities (Evo Controller 8100 BSC
relies on HD BSC boards), next evolution step would support RNC capabilities and 20 Gbps of throughput
(Evo Controller 8200 introduces “Evo Processing boards”, common with BSC and RNC) – also growth of
BSC capacity to over 12 000 TRX level has been seen.

Site evolution path between GSM, WCDMA and LTE is highlighted on BTS side, but the new Evo Controller
8000 seems to bring discontinuity to existing controller offering. If we compare Ericsson BSC upgrade
path to Flexi BSC product family (from BSC3i 660 onwards) we can clearly see discontinuities on their side.
And most importantly compact Nokia Multicontroller BSC solution allows also a clear evolution path for
legacy BSC installations.

Evo Controller 8000 seems to have similar limitations than Huawei has. Configuration limitations and GSM
or WCDMA specific individual parts are bound to be there to make the solution less flexible than Nokia’s
Multicontroller approach.

5.3 Differentiating space efficiency with unique modularity

Competition, e.g. Huawei BSC6910 in GSM only Full-IP configuration is showing unpractically high BSC TRX
connectivity figures – in here plain comparison of these basic BSC TRX connectivity or Erlang capacity
figures does not consider benefits coming from modular Nokia Multicontroller Platform.

Difference in site space efficiency with extremely compact and modular Multicontroller BSC is clearly
visible when compared to competitor offering. Nokia modular Multicontroller Platform allows innovative
installation options first time in the industry for really optimizing the needed site space – you can easily

April 2016 - 26 / 37 © Nokia Solutions and Networks 2016

Confidential
create innovative site installation by combining several Multicontroller configurations (being
Multicontroller BSC, Multicontroller RNC or mixture of Multicontroller BSC and Multicontroller RNC) into
one single site installation.

With Multicontroller BSC :

- Highest space efficiency : Optimal GSM controller implementation for distributed and centralised
BSC sites
- Unrestricted data connectivity and high data capacity efficiency : Maximum service availability for
end users with capability for data connectivity for all RTSLs in all TRXs
- Common HW for GSM and WCDMA : Future proof Nokia Multicontroller Platform, transforms to
Multicontroller RNC according network evolution

Figure 25: Multicontroller BSC - competitor landscape

6 Availability
Multicontroller BSC has been commercially available since 2012 and is in use in several customer
networks.

April 2016 - 27 / 37 © Nokia Solutions and Networks 2016

Confidential
7 Q&A
7.1 General

Q: What benefits Multicontroller BSC provides for operators?

A: In essence new modular HW architecture of Multicontroller BSC complements the successful Flexi BTS
approach also within controllers. The modular architecture enables very high scalability in capacity and
connectivity.

Extremely small size will reduce the site costs whereas modularity ensures easier implementation to the
various sites where cabinet based approach has not even been considered to be possible at all.

This will ease network topology planning with design that opens new possibilities outside the traditional
cabinet based implementations. All this is backed by high reliability for securing the availability of operator
services in the network.

Q: How Multicontroller BSC fits into Nokia Single RAN concept?

A: Nokia Single RAN is based on common platform concept. Nokia has introduced innovative Single RAN
platforms with Flexi Multiradio BTS and Multicontroller Platform addressing operator’s demand on
flexibility and efficiency following network evolution within GSM and between GSM and WCDMA.

Q: What is the main differentiator between Nokia Multiradio Controller Platform and competitor’s
Single RAN platforms?

A: Nokia Multicontroller Platform is unique controller platform which is very focused on All-IP. This reflects
to ongoing accelerated transition of the whole telecom world towards All-IP and Single RAN. The
architecture allows the allocation of HW resources to various functionalities, enabling high versatility for
different applications.

If you take a look at the product, it is obvious that it represents a completely novel approach in controller
HW. No conventional plug-in unit concept exists any more (less spare parts, easier installation, no
restrictive cabinet boundaries).

Comparing to our competitors corresponding products, an astonishing integration level has been
achieved. This translates to the market’s highest capacity/volume ratio.

Savings in installation time, spare parts cost and upgrade costs are obvious just by observing the physical
presentation of the product. In terms of capacity, the product can break the traditional cabinet
restrictions and flexibly grow from moderate to very high allowing many different approaches in terms of
network topology (from distributed to highly concentrated).

April 2016 - 28 / 37 © Nokia Solutions and Networks 2016

Confidential
Q: How does Multicontroller BSC relate to existing Flexi BSC?

A: The basic features and functionality of the Multicontroller BSC are the same as in the Flexi BSC. The
main difference in addition to increased capacity is that Multicontroller BSC is based on a novel and
generic Multicontroller Platform, based solely on Ethernet switching and all-IP transport.

Q: How does the Flexi BSC continue after Multicontroller BSC is introduced?

A: Flexi BSC will continue in customer networks - all new BSC deliveries will be Multicontroller BSCs.
Multicontroller BSC design is based on common application SW for both existing Flexi BSC and
Multicontroller BSC for securing the synchronization of the further SW development in both.

Q: Is Multicontroller BSC adaptable beyond GSM radio technology?

A: The Multicontroller BSC is based on an adaptive Multicontroller Platform which is not limited to the GSM
use only but may be transferred to WCDMA use according operator needs.

Multicontroller Platform HW architecture is so generic, that it is easily adaptable to various network

technologies. This means that both the new platform hardware and platform software are designed to
fully support favorable technology evolution. Furthermore Nokia’s intelligent network management
system - NetAct – always ensures smooth operation together with existing networks.

Q: When is Multicontroller BSC available?

A: Multicontroller BSC has been commercially available since 2012.

Q: How is Multicontroller BSC priced?

A: Multicontroller BSC price information is available through Nokia configurator (IPC) tool. Additionally also
a separate Excel based dimensioning and pricing tool is available in Nokia pricing database (access rights
by global pricing team).

Q: Is there cost difference between Multicontroller BSC and Flexi BSC?

A: Actual cost of configuration is always dependant on product configuration – generally HW costs of

simplified Multicontroller BSC are lower when compared to similar cabinet based Flexi BSC. When costs are
compared, the All-IP nature of Multicontroller BSC needs to be taken into account when compared Flexi
BSC configuration is selected. Cost data is available through pricing managers.

April 2016 - 29 / 37 © Nokia Solutions and Networks 2016

Confidential
Q: Is there price difference between Multicontroller BSC and Flexi BSC?

A: Generally IRP price / TRX is on a same level as with Flexi BSC. Common SW licenses are also used with
Multicontroller BSC and Flexi BSC.

Q: Is there any global delivery restrictions related to Multicontroller BSC?

A: Yes - Multicontroller BSC cannot be delivered to US Embargo countries – e.g. Iran, Sudan, Syria, North-
Korea and Cuba. In case of planning mcBSC introduction for these US Embargo countries, please contact
Controller Product Management for further details.

7.2 Multicontroller Platform

Q: What are the names of products utilising Multicontroller Platform?

A: Novel, unique and modular multicontroller HW platform :

Nokia Multiradio Controller Platform

BSC and RNC network elements by combining modules of Multiradio Controller Platform:

Nokia Multicontroller BSC

Nokia Multicontroller RNC

Q: What are the physical dimensions of Multicontroller BSC?

A: Physical dimensions are dependent on the amount of modules in Multicontroller BSC configuration. One
module is 444 mm wide and 176 mm high. Modules can be installed e.g. into a standard 19” rack meeting
Nokia’s installation asite requirements with a specific installation kit. Maximum Multicontroller BSC
network element configuration contains 8 modules.

Q: Is the Multicontroller Platform based on commercially available server based platform?

A: Multicontroller Platform is not directly and commercially available platform, but fully designed for Nokia.
All the technology inside is based on standard high capacity component technology.

April 2016 - 30 / 37 © Nokia Solutions and Networks 2016

Confidential
Q: Is the Multicontroller Platform based on ATCA HW?

A: Nokia, like many other vendors, has decided not to follow the ATCA-standard building practice with
Radio Controller products, as it does not appear to offer any benefits for our customers in terms of cost,
functionality and reliability.

Q: How does the Multicontroller Platform support both RNC and BSC network elements?

A: Modular Multicontroller Platform enables flexibly creation of different BSC, RNC and BSC/RNC
configurations by combining modules into a common site installation. In Multicontroller BSC/RNC
configuration containing several modules, different technologies are served by different modules, BSC
and RNC do not operate in concurrent mode within a single module. According to capacity needs modules
can be transferred from one network element to another.

Q: How many HW processing units there are in Multicontroller BSC?

A: Multicontroller BSC is build with only two different HW processing units. HW resources of these
processing units are SW configured for 1.) GSM Control Plane functional units (BJC-A HW processing unit)
and 2.) GSM User Plane functional units (BMPP2-B HW processing unit).

Q: Can a Multicontroller BSC be changed to Multicontroller RNC?

A: Yes, modular Multicontroller platform fully supports network and technology evolution. According
traffic development between GSM and WCDMA, BSC HW modules can be transferred into Multicontroller
RNC configuration module by module.

Q: Can a Multicontroller RNC be changed to Multicontroller BSC?

A: Yes, modular Multicontroller platform fully supports network and technology evolution. According
traffic development between GSM and WCDMA, RNC HW modules can be transferred into existing
Multicontroller BSC configuration module by module. Transferred RNC modules are used as a PS data
extension modules in existing Multicontroller BSC configuration.

Q: What is the procedure when module is transferred between technologies?

A: Modules are simply removed from existing RNC or BSC configuration by disconnecting the related inter-
module cables and similarly added into existing RNC on BSC configuration by connecting the related inter-
module cables. Module is activated in a new configuration with related RNC or BSC SW. When modules
containing GSM specific Control Plane processing units (Multicontroller BSC TRX extension module and
Multicontroller BSC basic modules) are moved to RNC configuration HW upgrade to replace GSM specific
Control Plane processing units is required.
April 2016 - 31 / 37 © Nokia Solutions and Networks 2016
Confidential
Q: How is the faulty HW replacement performed in modular configuration without affecting the service
level?

A: Multicontroller BSC provides module level redundancy enabling smooth traffic transition of working
modules in case of a failure. One module within the configuration can be replaced by still keeping the
whole Multicontroller BSC configuration operational.

Q: Can you compare installation times between Multicontroller BSC and Flexi BSC?

A: As being highly compact and modular, Multicontroller BSC installation is vastly simpler than installation
of a cabinet based Flexi BSC. Savings in installation time are expected in actual equipment site installation
and in commissioning phase.

Q: Is it possible to use Multicontroller BSC capacity or PS Data Extension module next to

Multicontroller RNC? Question is including the control of the BSC area functions to exist in
Multicontroller RNC modules and then just use the extension modules of Multicontroller BSC

A: Modular architecture allows to physically place the Multicontroller BSC modules next to Multicontroller
RNC modules. In all cases modules are either in Multicontroller BSC or in Multicontroller RNC configuration.
If there is an existing Multicontroller RNC configuration present you can add Multicontroller BSC modules
(first step would be the two Multicontroller BSC basic modules + additional ones for TRX and PS data
capacity) into the same physical location and with these additional modules you can create a
Multicontroller BSC configuration. Combination of Multicontroller BSC and Multicontroller RNC modules
can then share the same site router for external connections. Multicontroller RNC modules are not
controlling Multicontroller BSC modules.

7.3 Multicontroller BSC implementation

Q: Can Multicontroller BSC be upgraded to Multicontroller RNC?

A: Yes. Multicontroller BSC modules can be transferred into RNC configuration module by module and
taken into use with uploading the corresponding RNC SW. When modules containing GSM specific Control
Plane processing units (Multicontroller BSC TRX extension module and Multicontroller BSC basic modules)
are moved to RNC configuration HW upgrade to replace GSM specific Control Plane processing units is
required.

April 2016 - 32 / 37 © Nokia Solutions and Networks 2016

Confidential
Q: What SW release supports Multicontroller BSC?

A: Multicontroller BSC has been commercially available since 2012 on top of RG20 and its SW support has
been there according to GSM release roadmap. Latest available Release SW for Multicontroller BSC is GSM
16.

Q: What are the capacity figures of Multicontroller BSC?

A: Multicontroller BSC configurations are built by combining modules according capacity needs. In
maximum TRX capacity configuration with five modules Multicontroller BSC will offer TRX capacity up to
4400 TRXs with traffic handling capacity up to 26400 Erlangs. According needs additional PS data capacity
can be added with additional modules. Maximum Multicontroller BSC configuration contains eight
modules.

Q: What are the key differences between Flexi BSC and Multicontroller BSC?

A: Multicontroller BSC supports solely All-IP interfaces as Flexi BSC supports on top of IP interfaces also
traditional E1/T1 and STM-1/OC-3 interfaces. Despite of not having native TDM interfaces, Multicontroller
BSC BTS connectivity with Packet Abis/TDM can be achieved with TDM/Ethernet media conversion
functionality (MLPPP) – here TDM/Ethernet media conversion is done in transport path, e.g. in
Multicontroller BSC site equipment. Additionally Flexi BSC has cabinet based mechanics as Multicontroller
BSC is based on modules without traditional cabinet restrictions.

Q: How does the modular Multicontroller BSC provide telecom level reliability?

A: Availability and redundancy principles are implemented in similar manner as with existing Flexi BSC to
offer full telecom level reliability. Multicontroller BSC implements full redundancy on module and unit
level.

Q: Can I buy Multicontroller RNC HW and run it as Multicontroller BSC?

A: Yes, combined Multicontroller BSC/RNC site installation is supported and flexible HW architecture makes
it easy to use HW modules either in BSC or in RNC configuration.

If existing Multicontroller BSC configuration is not present when RNC HW modules are to be transferred
into Multicontroller BSC configuration additional modules containing BSC specific Control Plane HW
resources are needed. On the other hand already existing Multicontroller BSC configuration can be
extended with RNC modules.

Q: What should we offer as BSC solution to our customers and when?

Multicontroller BSC is the BSC offering for all customer cases.

April 2016 - 33 / 37 © Nokia Solutions and Networks 2016
Confidential
Q: What are the installation options for Multicontroller BSC modules?

A: Multicontroller BSC implementation as such does not limit the actual installation options. E.g. standard
19” rack installation according Nokia’s site installation requirements can be used.

Q: What is the lowest capacity of Multicontroller BSC? How many modules will be needed for the lowest
capacity configuration?

A: Absolutely minimum configuration is two modules for Multicontroller BSC.

Q: Is Combined BSC/TCSM is also applicable with Multicontroller BSC similarly as with Flexi
BSC/TCSM3i?

A: Multicontroller BSC network element is built by combining modules to reach the needed TRX and PS
data capacity. Transcoder functionality will be located in MGW, combined BSC/TCSM configuration is not
relevant with Multicontroller BSC.

Q: Can I connect Multicontroller BSC to TCSM3i?

A: No, with Multicontroller BSC transcoding is done in MGW (AoIP, TC in MGW). Transcoders in BSS are not
used with Multicontroller BSC.

Q: Are there significant differences in MML interface between Flexi BSC and Multicontroller BSC?

A: Multicontroller BSC is based on field proven Flexi BSC architecture sharing also the structure of MML
interface. Learning curve for persons familiar with Flexi BSC MML interface will be fast when Multicontroller
BSC is introduced into network.

Q: Can you fully describe in detail the redundancy principles and relative planning and dimensioning
needed to be done for both HW and module redundancy?

A: Redundancy is automatically built into all Multicontroller BSC configurations. There is no need for any
additional redundancy related planning or dimensioning. All Multicontroller BSC configurations provide
redundancy against a failure of a complete module or against a failure of a add-in card inside the module.
Functional units utilising HW resources from add-in cards have specific redundancy principles to ensure
the operation in case of a failure.

April 2016 - 34 / 37 © Nokia Solutions and Networks 2016

Confidential
Q: Is it guaranteed that the capacities included in a complete Multicontroller BSC element are
achievable? Is there a limitation achieving the maximum capacities?

Capacities defined for Multicontroller BSC configurations are including all the spare units required for
redundancy - there is no need for any additional capacity considerations due to redundancy

Q: How about external peripheral equipment – like alarm lamp panes – are these supported by
Multicontroller BSC?
A: Multicontroller BSC is all IP-based product, traditional peripheral equipment, like with Flexi BSC, are not
supported. Further development for peripheral equipment support with Multicontroller BSC is decided
separately according customer requests – please contact controller Product Management in case if having
related customer requests.

7.4 Transcoding

Q: When going for the Multicontroller Platform do I still need a transcoder in GSM?

A: No – when core networks with Multicontroller BSC are evolving to IP (3GPP Rel 8 AoIP) also voice
transcoding moves to MGW. With Multicontroller BSC AoIP, TC in MGW is always used – transcoding in BSS
is not supported nor required.

Q: Can I use the Multicontroller BSC to modernize existing transcoder implementation?

A: No – when Multicontroller BSC is implemented, voice transcoding moves to MGW (AoIP, TC in MGW).
Transcoding in BSS, i.e. separate transcoder network elements are not required anymore.

7.5 Functionality

Q: Does Multicontroller BSC support also SS7 signaling?

A: Signaling is part of the Control Plane functionality in Multicontroller BSC. SIGTRAN (SS7 over IP) is used
with Multicontroller BSC.

Q: Does Multicontroller also support BS2xx via BSS Abis – similarly as with Flexi BSC?

A: No – Multicontroller BSC requires Packet Abis implementation and Packet Abis capable BTSs.

Q: Does Multicontroller also support Horizon BTS via BSS Abis – similarly as with Flexi BSC?

A: No – Multicontroller BSC requires Packet Abis implementation and Packet Abis capable BTSs.

April 2016 - 35 / 37 © Nokia Solutions and Networks 2016

Confidential
Q: How can existing BTS sites be maintained and still evolve towards Multicontroller BSC
implementation?

A: Co-siting with legacy BSCs provides an evolution path towards Multicontroller BSC. Compact
Multicontroller BSC is installed into existing BSC site and existing BTS sites with legacy Dynamic Abis
remain to be served by the existing legacy BSC according their lifecycle. New Multiradio BTSs with Packet
Abis are then served with Multicontroller BSC. This co-siting with legacy BSCs creates a powerful
combination supporting both legacy BTSs and an evolution towards IP/Ethernet transport with new
Multiradio BTS sites.

7.6 Transport

Q: The Multicontroller provides only All-IP interfaces. What can we do, if there are also other
transmission lines used for GSM like E1/SDH ?

A: All-IP support of Multicontroller BSC is requested by customers in their “2G to Single RAN
modernization plans” with strong desire to utilize common IP/Ethernet transmission resources in
combined Single RAN implementation. From interfaces point of view this means that Multicontroller BSC
supports Packet Abis over Ethernet connection towards BTSs, Gb/IP interface for packet data/SGSNs, AoIP
towards Circuit core/MGWs and SIGTRAN signaling (SS7 over IP) for A -interface/MSS.

Despite that Multicontroller BSC as such is designed for All-IP implementation, Packet Abis Network Media
Conversion feature (BSS101414) enables BTS sites with Packet Abis/TDM to be connected to
Multicontroller BSC by doing a TDM / Ethernet media conversion (MLPPP) within the transport path with
external equipment (e.g. with Multicontroller BSC site equipment).

Q: Is it possible to have the option of E1 as external connectivity towards Multicontroller BSC? Is there
any solution for E1/STM1 external connectivity towards Multicontroller BSC?

A: Multicontroller BSC is IP only by design. This defines the requirements for external transport. On the
Abis side Packet Abis is always required and correspondingly on core network interfaces Gb/IP and AoIP.
Legacy E1/STM1 and TDM transport (Dynamic Abis) is not available with Multicontroller BSC. In addition to
Packet Abis / Ethernet, Packet Abis Network Media Conversion feature (BSS101414) enables BTS sites with
Packet Abis/TDM to be connected to Multicontroller BSC by doing a TDM / Ethernet media conversion
within the transport path with external equipment.

April 2016 - 36 / 37 © Nokia Solutions and Networks 2016

Confidential
Q: Is it possible to have Packet Abis / TDM as external connectivity option for Multicontroller BSC?

A: Yes - Packet Abis / TDM connectivity is available with Packet Abis Network Media Conversion feature
(BSS101414). BTS sites with Packet Abis/TDM can be connected to Multicontroller BSC by doing a TDM /
Ethernet media conversion within the transport path with external equipment.

April 2016 - 37 / 37 © Nokia Solutions and Networks 2016

Confidential