Flexi BSC Product Overview.pdf

Company Confidential 29

th April 2011

1 / 31

Nokia Siemens Networks Flexi Base Station Controller (Flexi BSC)

Flexi BSC Product Overview

For Internal Use


th April 2011

2 / 31

Contents

Purpose of the Document ................................................................. 4

Flexi BSC.......................................................................................... 4

High Capacity Network ................................................................................................... 5 Circuit Traffic handling capacity ...................................................................................... 6 Evolution framework ....................................................................................................... 7 Availability ...................................................................................................................... 7 Product naming .............................................................................................................. 8 Pricing of Flexi BSC ....................................................................................................... 8

Flexi BSC - customer benefits .......................................................... 9

Value Based model - calculations ................................................... 10

Competitors' BSCs ......................................................................... 13

Upgrades ..................................................................................................................... 16 Flexi BSC new deliveries .............................................................................................. 17 Radio Network Configurations supported by S15 ......................................................... 18

Positioning Flexi BSC against Multicontroller BSC .......................... 20

Questions & Answer ....................................................................... 21

Characteristics of the product ....................................................................................... 21 Compatibility ................................................................................................................ 25 Availability .................................................................................................................... 26 Replacement strategy .................................................................................................. 26 Pricing .......................................................................................................................... 27 Competition .................................................................................................................. 27 Multicontroller BSC ...................................................................................................... 27


th April 2011

3 / 31

Summary of changes

V0.1 First draft 18.08.2008 V0.11 Second draft 24.08.2008 V0.12 Thrid draft 27.08.2008 V1.0 First updated version 01.10.2008 V1.1 RG update 24.10.2008 V1.2 Piloting & mcBSC update 31.03.2009 V2 RG20 update 30.04.2010 V2.1 RG20 version revised 15.11.2010 V2.2 RG20 P8/C5 version with Motorola 29.04.2011


th April 2011

4 / 31

Purpose of the Document This document is aimed to be internal training material, i.e. initial information to support the Nokia Siemens Networks customer teams presenting Flexi BSC to customers. It is to be used internally as back-up and training material. The document also clarifies the Flexi BSC as a part of the GSM/EDGE Evolution solution.

This document is part of Flexi BSC marketing material. See Flexi BSC intranet page for more details. Document is maintained by BSC and Transcoder Product Management team in RA GSM/EDGE Product Management.

Flexi BSC

Peerless capacity, scalability, and efficiency in a single cabinet

GSM is booming with steadily growing subscriber numbers, networks, and data traffic. Aiming to capitalizing on this business opportunity, operators are looking for the best GSM investment. One network provider rises to the challenge with innovative solutions, advanced features, and enhanced capabilities – Nokia Siemens Networks. Our cautioners chart a smooth evolutionary course to protect operators’ installed base and future-proof their investments. And they develop new products geared to drive revenues up and costs down. Witness our Flexi BSC: Engineered to provide remarkable capacity, it leaves a small footprint and consumes little power.

Bigger capacity, smaller package

The latest Nokia Siemens Networks Base Station Controller, the Flexi BSC offers vastly improved capacity in a compact package the size of a single cabinet. If you are seeking to boost capacity and improve your network with the latest technology, look no further than the Flexi BSC. It delivers plenty of capacity to meet even the most demanding requirements. Featuring the latest Intel processors, it rivals any other BSC for CS traffic capacity and outperforms them all in terms of PS traffic handling capacity.

All but unlimited traffic handling

The Flexi BSC scales to suit just about any size demand, so its PS traffic handling capacity is practically unlimited. No need to buy new BSCs when this one grows in step with your business. Aiming to capitalizing on this business opportunity, operators are looking for the best GSM investment and and the new Flexi BSC product configuration is designed to offer enhanced radio access service in optimal and compact package. Best parts of latest DX200 multi-processing platform have been used to enable packing of more traffic handling capacity to only one cabinet design. This product is well-suited for equipment rooms, where additional space is scarce. Flexi BSC product enables high capacity up to 4200 TRX together with evolution to integrated IP/Ethernet connectivity in all external interfaces.

https://inside.nokiasiemensnetworks.com/global/Work/Products/RadioAccess/RA_products/GSM/Flexi+BSC.htm?languagecode=en

https://inside.nokiasiemensnetworks.com/global/Work/Products/RadioAccess/RA_products/GSM/Flexi+BSC.htm?languagecode=en


th April 2011

5 / 31

Full scale IP/Ethernet on top of legacy transmission solutions

Equipped with an LAN switch and IP interface units, the Flexi BSC offers flexible connectivity options, brings IP capability to all external interfaces, and enables high capacity SIGTRAN (SS7 over IP) links to maximize traffic usage. The Flexi BSC comes complete with built-in SDH/Sonet capability as well as conventional PCM interfaces. With the benefit of this optical interface, you need fewer connections, which translate to less installation effort, faster rollout, and lower maintenance costs. External transmission equipment is unnecessary, so there are far fewer network elements to support

High Capacity Network

The very first aim for the operator is to build coverage within the network. Many of today's operators have passed this phase and are concentrating on capacity. That is mandatory because the amount of mobile subscribers and traffic increases all the time and the subscribers will use many new services and mobile data applications. All that usage will require capacity, efficiency and power from the network elements.

Networks will become increasingly complex and challenging to implement and operate. Moreover, it will be more and more important to possess the competence necessary to integrate high capacity solutions into the existing network without compromising end-user quality or cost efficiency.


th April 2011

6 / 31

Circuit Traffic handling capacity

There are different ways to communicate the traffic handling capacity of the BSC. To give the most reliable and real picture of the capacity, it should be communicated in terms of Erlangs, which is increasingly important in more mature networks. The maximum connectivity with the number of TRXs, BCFs and BTSs are not alone necessarily that adequate measurement to highlight the potential of the BSC.

Flexi BSC is designed to handle high traffic volumes and in all various configurations. The average traffic can be around 6 Erl/TRX with the nominal reference call mix to ascertain enough processing power to handle even the most challenging hot spot traffic situations. This is seen as adequate even in the most challenging situations and is generally above the figures other products in the marketplace can achieve.

Based on the nominal call mix below, the maximum traffic processing capacity of the Flexi BSC is 25 200 Erl giving full support to 4200 TRXs. Processing capacity of one HW capacity step (BCSU) is 700TRX and 4200 Erl.

Reference model of call traffic (call mix and parameters):

mean holding time 120 s

proportion of MS originated calls 70%

proportion of MS terminated calls 30%

proportion of handovers (HOs ) 1.5 HOs per call

proportion of location updates (LUs) 2 LUs per call

proportion of IMSI detaches 0.1 detaches / call

for terminating call attempts, the proportion of no-answer call 63% attempts to paging requests

SMS call rate 1 req./subs./1 hour

BHCA (busy hour call attempt) depends on reference call mix and therefore figures are not comparable directly between different vendors. The BHCA (busy hour call attempt) value varies heavily depending on the call mix. With the nominal call mix the call processing capacity is 531 000 BHCA with Flexi BSC (RG10) and with a call mix having a very short call mean holding time and other supporting characteristics 3.4M BHCA with Flexi BSC (RG10) can be reached (we have reached even ~3.7 M BHCA in laboratory environment). BHCA (busy hour call attempt) depends on reference call mix and therefore figures are not comparable directly between different vendors.


th April 2011

7 / 31

Packet Traffic handling capacity

Mobile networks have grown rapidly in line with subscriber amount. As packet data is gaining its momentum, more flexibility is given to PCU configurations; each BCSU units can be equipped individually with 0-5 PCU (PCU2-E) plug-in units giving possibility to scale data throughput nearly linearly depending on traffic requirements.

In Flexi BSC packet switched (PS) GPRS and EDGE traffic is supported with Packet Control Units (PCU). The maximum packet handling capacity for Flexi BSC is handled by up to 30 720 Abis (16kbit/s) channels, which provides in practise unlimited traffic handling capacity.

Packet handling capacity and connectivity per each PCU2-E HW unit is 384 BTSs, 1024 TRXs, and 1024 traffic channels (16 kbit/s, Abis) for GPRS/EDGE use.

Maximum capacity of Flexi BSC with full configuration (30 x PCU2-E units) is 1024 x 30 = 30 720 traffic channels (16 kbit/s) per Flexi BSC for GPRS/EDGE use

Asymmetrical HW configuration support enables adding PCU2 cards one by one

Capacity steps are controlled by SW licence keys in 256 ch steps (max. 4 per card)

Evolution framework

We strongly feel, that the evolution of legacy GSM networks with EDGE and further GSM/EDGE evolution items will keep the existing networks competitive and provide the operator very strong cash flow by creating new services and by boosting usage up.

The Flexi BSC is the BSC made for this kind of environment: more capacity in compact size and with state-of-the-art reliability.

Availability

Flexi BSC (RG10) and (RG20) are commercially available for deliveries together with corresponding RG10 SW and RG20 SW releases.

Flexi BSC is the BSC to be offered to BSS, BR and Motorola customers. Flexi BSC product family (Flexi BSC, BSC3i 1000/2000 and BSC3i 660) will support connectivity to Horizon base stations will be available same way as connectivity to BS2xxx base stations (with E1/T1) with SW functionality has been available with RG10ED.


th April 2011

8 / 31

Product naming

The official name of Flexi BSC is “Nokia Siemens Networks Flexi Base Station Controller” and the abbreviation is “Flexi BSC”.

Configuration: Description:

Flexi BSC One cabinet configuration (RG10) with maximum 3000 TRXs

One cabinet configuration (RG20) with maximum 4200 TRXs

From BSS14 SW release onwards also earlier delivered BSC3i configurations are all considered to be part of Flexi BSC product family as presented in following table:

Family name: Abbreviation: Description:

Flexi BSC BSC3i 660 660 TRX one-cabinet configuration, Product upgradeable to Flexi BSC family

BSC3i 1000/2000 1000 TRX one-cabinet or 2000-TRX two cabinet configuration, upgradeable to Flexi BSC

Flexi BSC 3000 TRX one-cabinet configuration

4200 TRX one-cabinet configuration

Upgrade path for all earlier delivered BSC3i configurations is thus available to Flexi BSC. BSC3i 660 and 1000/2000 product configurations can, therefore, be upgraded to 3000 TRX product configuration.

Pricing of Flexi BSC

The pricing of the Flexi BSC is based on hardware and basic software. The Flexi BSC new delivery pricing structure consists of hardware in steps of BCSU i.e. 700 TRXs in Flexi BSC. Basic SW is available with 1 TRX steps. HW for PS traffic capacity is available in one plug-in unit steps i.e. PCU2-E. Basic SW for PCUs is available in 256 channel (Abis 16kbit/s) steps (four needed per card for full channel capacity).

In pricing, the total value for customer should be is emphasized and the OPEX savings should be pointed out apart from the CAPEX, i.e. the cost of ownership should be noted.

The pricing information is available in configurator (IPC) in CSP system and from NSN Pricing Database.

https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=356430312&objAction=Browse&viewType=1


th April 2011

9 / 31

Flexi BSC - customer benefits

Here are quite a few points worth considering usage of Flexi BSC. There are several areas, where the higher capacity BSC brings benefits to the operator. Also latest HW will provide additional benefits in many areas.

The main value based marketing message can be derived from the cost per capacity, which is optimised with Nokia Siemens Networks solutions. This can be derived from the following:

Cuts OPEX through less equipment

o Less equipment needed for CS and PS traffic

o Reduces site space costs thanks to decreased demands on site space

o Reduction in power consumption per TRX and per capacity unit

o Cuts transmission costs

o Integrated IP/Ethernet and SDH/Sonet support most cost-efficient transmission media

o No need for external transmission elements

Cuts IMPEX through fast installation

o Compact size

o Less equipment needed

o More scalable configuration steps

o Integrated high capacity transmission minimizes cabling related work

Adds revenue through better radio network quality and reduces churn

o Fewer lower success rate inter-BSC handovers

o Fewer inter-PCU and inter-BSC PCU cell reselections

The unique traffic handling capacity with distributed processing, modular structure, fault tolerance, upgradeable processors, good on-line operability and user-friendly MML interfaces gives competitive advantage over the competition.

See Flexi BSC Product slides and Internal Guidelines sets for further information.


th April 2011

10 / 31

Value Based model - calculations With techno-economic modelling we are able to prove the value of the investment for the operator.

The key initial driver in Flexi BSC case is the OPEX saving related to need for lower amount of BSCs in the network. In later phase, when data traffic grows, higher data handling capacity starts to play a role also.

Presented here is a customer case, a GSM operator to extend a network with new or old BSCs.

Figure 1: Network extension rollout in this example.

To rollout the same capacity with ~2000 TRX BSCs, the operator needs them basically double amount compared to Flexi BSCs.

As Flexi BSC offers market leading traffic handling capacity for one cabinet design the site space needs remain low even when traffic growths. Additionally very low power consumption especially against offered capacity minimises the cost of electricity both for the equipment and also for site equipment such as air conditioning.


th April 2011

11 / 31

Figure 2: Amount of new BSCs in the network per year.

By having less BSCs, the operator savings are mostly site costs, installation costs and operational costs such like power consumption. The quality related costs are harder to quantify, but can be crucial for the subscriber point of view.

Figure 3: Annual BSC TCO (x1000EUR) Flexi BSC compared to 2000TRX BSCs


th April 2011

12 / 31

The real difference between the solutions becomes visible with the cumulative cost of ownership curve below: in five years ~60 million EUR. This means approximately 40% difference in cumulative cash flows.

This business case shows clearly the monetary benefit of the Flexi BSC: cost per Erlang and TRX should be pointed out with low data traffic penetration and exceptional cost per Mbit if high data penetration. Also the lifetime cost is considered in the NSN solution.

Figure 4: Cumulative Cost of ownership between Flexi BSC 4200 and 2000 TRX legacy BSC solutions (MEUR).

Value Based modelling tool for highlighting Flexi BSC benefits over competition of for supporting modernisation argumentation is developed by RA SSM Value Based Argumentation team. Main contact for Flexi BSC modelling is Tom Höglund.


th April 2011

13 / 31

Competitors' BSCs All major GSM/EDGE vendors are strongly investing to GSM/EDGE development. This is visible in BSC product offering, where from previous 2000 TRX capacity milestone most of the vendors are moving forward to higher capacity levels

Ericsson has been minimising the HW and number of cabinets (currently 2 cabinets) and has enhanced the capacity to 4095 TRXs (release 08B 2009)

o Additional capacity requires additional cabinet(s), Erlang capacity remains at 18k

Huawei has also been minimising the HW and offering is moving from current 3072 TRXs to 4096 TRXs (GBSS13.0, 2Q 2011)

o The 4096 TRX capacity comes from “6900” HW, additional cabinet needed for TC and traditional transmission

Motorola has been offering Huawei BSC/BSS (at least the BSC6000 2048 TRX version)

Alcatel-Lucent has enhanced the capacity to 2800 TRXs, but second cabinet is needed for PCU support

ZTE is offering 3072 TRXs from multicabinet product

Nortel has enhanced the capacity from 1000 TRXs to 1500 from one cabinet

Flexi BSC has major advantages over competition:

Supporting market leading 4200 TRXs from one cabinet

o Ericsson’s 4095 TRXs come from multiple cabinets

o Huawei’s 4096 TRXs global availability earliest 2Q 2011

Highest voice (Erlang) capacity compared to any GSM BSC

Very high PS data capacity (only ZTE on higher level)

High transmission capacity supporting all medias including integrated IP in all interfaces (in par with Huawei and Ericsson)

Very high BTS site and sector connectivity

Very good footprint efficiency e.q. high traffic capacity per site space -ratio

Low power consumption especially when compared to traffic handling performance

Constant capacity evolution path guaranteed with Intel processor evolution, advanced SW development and Multicontroller evolution path


th April 2011

14 / 31

Competitor BSC highlights

• Competitors have smaller cabinets; 2 small cabinets might be a bit smaller than our single cabinet

• Ericsson and Huawei offer fully integrated transcoders as we need separate cabinet

• High BHCA figures with Ericsson, Huawei and ZTE

• Huawei started with Single RAN story, Ericsson has followed this lately, ZTE has also shown on roadmap Server based common controller concept


th April 2011

15 / 31

Flexi BSC - technical description Product features for Flexi BSC are following:

• A maximum 4200 TRX capacity with compact one cabinet configuration with 700 TRX HW capacity steps (BCSU)

• Circuit Switched Capacity of 25 200 Erl with 4200 Erl HW capacity steps (BCSU)

• Packet Switched Capacity of 30 720 16 kbit/s Abis channels from 30 x PCU2-E cards with S14 SW release – each capable to connect 4 x 256 x 16 kbit/s Abis traffic channels

• Compact product configuration in one rack configuration, simplified product structure to minimise installation and delivery times

• Flexi BSC (RG20) deliveries offers higher transmission connectivity Table 1: Interface option of the Flexi BSC (RG20)

• The STM-1/OC-3 connectivity will increase from 16 + 16 to 18 + 18 with RG20 • The IP connectivity with CESoPSN has been increased from 8 + 8 to 9 + 9

with RG20. This enhancement will also be available for installed base of Flexi

BSCs (delivered with RG10 before June 2011) in form of cabling kit (one kit per Flexi BSC enables both connectivity enhancements)

This enhancement will be available as standard also for Flexi BSC RG10 deliveries starting from June 2011

• The IP connectivity with “old” native Ethernet interfaces 3 + 3 from internal LAN switches are coming from:

2 + 2 GE connections on top of the cabinet for Gb over IP 1 + 1 GE connections on top of the cabinet for CPU LAN for O&M

and BSC-BSC interfaces • Packet Abis and A over IP application SW products are enabled with ETP and

ETP-A plug-in units 6 + 6 ETP plug-in units enable full Packet Abis connectivity 3 + 1 ETP-A plug-in unit enable full A over IP connectivity Both options are supported with special cabling kit with LAN switch

pair (one kit per Flexi BSC enables both connectivity enhancements)


th April 2011

16 / 31

• PDH connectivity up to 800 E1/T1 interfaces • Power consumption of the Flexi BSC (4200TRX) is only 0.7 – 1.0 W per TRX

depending on packet switched capacity and provided amount of external interfaces

Upgrades

All existing BSC3i 660/1000/2000 and Flexi BSC (RG10) configurations can be optionally upgraded to Flexi BSC (RG20) configuration. This HW upgrade path from BSC3i to Flexi BSC is rather time consuming and requires experienced BSC engineer skills. Such HW upgrades are also typically done without life traffic operations with the help of network management tools such as BSS rehoming tool (former BSS split).

NetAct 2G Rehosting is a new powerful tool for BTS re-allocation to BSCs (replacing BSS Split). It provides several key benefits:

One tool for planning, executing and following up the whole re-hosting operation

Support for automated, operator specific processes

Tailoring possibility for re-hosting process and parameter view

Scripts can be integrated, e.g. to update in-house tools, other vendor data

Higher performance compared to old BSS Split

Supports File based plan provisioning


th April 2011

17 / 31

Flexi BSC new deliveries

The configuration of Flexi BSC new deliveries is illustrated in following figure.

Figure 5: Flexi BSC new deliveries with maximum capacity of 4200 TRXs


th April 2011

18 / 31

Radio Network Configurations supported by S15

A number of different configurations are likely to exist in operators' networks currently. To assist in establishing which BSC configurations can be supported the table 6 in previous page shows the BSC configurations vs. capability.

* Dependant on total signalling capacity usage: TRXSIG / TRX, OMUSIG / BCF, SS7 links and control channels for interface / transmission units.

BSC Configurations (S12) A

BSCi

B

BSC2i

C

BSC3i 660

D

BSC3i 1000

E

BSC3i 2000

F

Flexi BSC

S14

F

Flexi BSC

S15

Maximum Radio network configuration

248 BCF

512 BTS

512 TRX

248 BCF

512 BTS

512 TRX

248/504 BCF

660 BTS

660 TRX

1000 BCF

1000 BTS

1000 TRX

2000 BCF

2000 BTS

2000 TRX

3000 BCF

3000 BTS

3000 TRX

3000* BCF

4200 BTS

4200 TRX

Allowed CPU Type in OMU CP6LX /

CP6MX

CP6LX /

CP6MX

CP710 CP816 CP816 CP816 CP1D-A

Allowed CPU Type in MCMU CP6LX /

CP6MX

CP6LX /

CP6MX


Allowed CPU Type in BCSU CP6LX /

CP6MX

CP6LX /

CP6MX


Allowed Group Switch type / Maximum number of internal PCMs

GSWB/ 128 GSWB/ 192

GSWB/ 128 GSWB/ 192 GSWB/ 256

GSWB/ 256 (S10.5/S10.5ED/ S11)

GSW1KB/ 512 (S11.5/S12)

GSW2KB/ 2048

GSW2KB/ 2048

GSW2KB/ 2048

GSW2KB/ 2048

Number of AS7 cards in BCSUs

(Variant letter + amount of units)

V 3 U 0-1

V 2-3

B 3 (S10.5/S10.5ED)

C 1 (S11/S11.5)

C 2 C 2 D 2 D 1 - 2

Maximum Number of external PCMs (E1/T1)

56/88 80/112/ 144

124 / 256 (ET2s) (ET4s)

384 800 800 800

Maximum Number of STM-1 / OC-3 interfaces

- - - 16 16 16 18

Maximum Number of IP/PWE interfaces

- - - 8 8 8 9

Type of LapD and Q1 terminal in OMU

AS7-V AS7-V / -VA / -X

AS7-B (S10.5/S10.5ED)

AS7-C (S11/S11.5)

AS7-C

AS7-D P05/2011 onwards

AS7-C

AS7-D P05/2011 onwards

AS7-D

AS7-D

Minimum number of WO-EX BCSUs 1-8 1-8 1-6 1-5 1-10 1-6 1-6

Number of BCFSIG LapD links per BCSU

32 32 84 200 200 500 700

Number of TRXSIG LapD links per BCSU

64 64 110 200 200 500 700

Maximum number of LapD links per BCSU

(BCFSIG + TRXSIG + ISDN+ET-LAPD)

117 124 170 (AS7-B)

206 (AS7-C)

448 448 1024 1024

Maximum number of TCHs per BCSU

512 512 880 1600 1600 4000 5600


th April 2011

19 / 31


th April 2011

20 / 31

Positioning Flexi BSC against Multicontroller BSC

NSN has track record of high performing BSC portfolio. As its latest evolution supporting new deliveries the Flexi BSC comes in RG20 and introduces common NSN BSC with vastly improved capacity and reduced operator costs. Additionally “Horizon@Flexi BSC family” SW functionality on top of RG10 will connect installed base of ex-Motorola base stations to the Flexi BSC product family same way as ex-Siemens base stations can be connected with “BS2xx@Flexi BSC family” SW functionality.

NSN has also announced plan to develop multiradio controller platform as the next step in controller platform evolution - RNC is the first one to adapt. Flexi BSC and Multicontroller BSC complement each other and offer flexible future proofness to operators. Multicontroller BSC will be developed to take full advantage of Flexi BSC platform.

It is very important to note that there is no plan whatsoever to discontinue Flexi BSC; it is the base for NSN BSC needs and supports whole installed base.

Let’s keep in mind that today is today and tomorrow is tomorrow. We have excellent market leading Flexi BSC just coming available and we must concentrate on the sales of it. To put this in simple words “sell today Flexi BSC”.

On the contrary Multicontroller BSC is a solution for tomorrow. It is best suited as such for revolutionary new all IP network implementations. In the beginning this is most probably only a segment in the future markets. On top of the revolutionary all IP implementations Multicontroller BSC can be used as evolution path for Flexi BSC in existing networks. With combined site installation all the newest possibilities can be introduced to installed base without the need to swap products. This is excellent path to ascertain our footprint in customer networks and work against competitor initiated swap risks.

Flexi BSC and RNC2600 are leading controllers and will be introduced and rolled out and further developed as planned. No changes due to Multicontroller.

The overall plan is following the logic that both Multicontroller BSC and Multicontroller RNC will be offered as complementary products. There is no forced need to go to Multicontroller due to EOL of any other product.

This means that 2G Flexi BSC and Multicontroller BSC are complementing each other and offer a flexible and future proof network evolution in the same way as RNC2600 and Multicontroller RNC do.

E.g., the introduction of Multicontroller BSC can be done so that capacity can be flexibly extended also for the installed Flexi BSC base using the new HW module implementation of the Multicontroller. This way Multicontroller BSC will provide evolution path to installed Flexi BSC product family base as well as totally new BSC option for new installations.


th April 2011

21 / 31

Questions & Answer

Characteristics of the product

Q: Why new GSM BSC product?

A: Flexi BSC development was originated to provide innovative and advanced BSC product offering to the rapidly evolving GSM/EDGE markets. Market requirement for new Flexi BSC with higher traffic handling capacity and IP evolution was clearly seen. See Flexi BSC slide set for further information.

Q: Why the name Flexi BSC?

A: As name suggests the product has inbuilt flexibility in almost all aspects. It supports not only 4200 TRXs but also 4200 sectors and 3000 BTS sites (BCFs) making the radio network connectivity practically unlimited. Furthermore its capacity can be scaled flexibly with basic SW licences in terms of TRXs (1 TRX steps) or in terms of packet data connections (in 256 16kbit/s Abis ch steps). Furthermore flexibility with external interface configurations is supported towards all interfaces. Naturally the name reflects also to its capabilities to provide full support to Flexi BTS product family.

Q: Is the software still same as in earlier BSCs such as BSC2i or BSC3i?

A: Yes the software release is really same, but different SW build is needed for the Flexi BSC.

Q: What is the software release supporting Flexi BSC?

A: RG10 SW release supports Flexi BSC with 3000TRX. RG20 SW release supports Flexi BSC with 4200TRXs and of course older 3000TRX version. In old terms we are talking about S14 and S15 product releases.

Q: What is RG20 then?

A: RG20 is NSN GSM RA SW release available after RG10. See latest roadmaps for further information.

Q: Will Flexi BSC support Motorola Horizon base stations?

A: Whole Flexi BSC product family (includes BSC3i 660 and BSC3i 1000/2000) will support Horizon I/II base stations when a specific RG10ED releases the SW functionality. See special intranet pages for further information.

Q: Will Flexi BSC support Siemens BS2xx base stations?

A: Whole Flexi BSC product family (includes BSC3i 660 and BSC3i 1000/2000) will support BS2xx base stations when a specific RG10ED releases the SW functionality. See latest roadmaps for further information.

https://inside.nokiasiemensnetworks.com/GLOBAL/WORK/SALES/SALES_MATERIALS/NWSSALESPORTAL/MBBSALESPORTAL/GSMSALESPORTAL/Pages/MotorolaAbis.aspx


th April 2011

22 / 31

Q: What is the footprint compared to earlier BSCs?

A: Maximum configuration (4200 TRX) in standard one rack version has footprint of 900x600 mm, whereas BSC3i 2000 has 1800x600 mm footprint in maximum 2000 TRX configuration.

Q: Will there in future be SW products only functional in Flexi BSC?

A: Not foreseen yet, but new complex features might require the processing power and other enhancements available only in Flexi BSC. New SW products may require more processing power, IP interface support etc, which are not be available in all BSC variants.

Q: You mentioned IP based interfaces – what are they?

A: Flexi BSC has lots of redundant external IP/Ethernet interfaces. 4 of them are native IP based used for O&M, Gb/IP, Lb, BSC-BSC (DFCA) and Sigtran (SS7 over IP) interfaces. For those there is inbuilt L3 switching functionality available in integrated IP Switch connections. On top of these “old” IP connections there are introduced with RG10 redundant IP/Ethernet connections (9+9 with RG20, 8+8 with RG10) dedicated for PWE/CESoPSN based connections in Abis and Ater interfaces. New Native IP interfaces 6+6 for Packet Abis over Ethernet and 3+1 for A over IP are introduced with RG20.

Q: What is the difference in supporting IP based interfaces between Flexi BSC and earlier product variants?

A: Flexi BSC introduces IP connectivity for all interfaces including also Abis and Ater interfaces with its new integrated units (ETP and ETP-A) for Native Packet Abis and A over IP and CESoPSN units (ETIP1-A).

Q: What are the basic HW configuration steps in Flexi BSC?

A: There are six HW steps each supporting up to 700 TRX/BTS and 4200 Erlangs. Packet Control Units (PCU2-E) HW can be now scaled in terms of 1 unit granularity each supporting up to 1024 channels (16 kbit/s Abis). This is possible with the support of new “asymmetrical PCU configuration” support.

Q: So is the new Flexi BSC less modular? Can you still start small and grow, or do you have to invest in max size from the start?

A: The Flexi BSC is actually more modular than the earlier BSCs. An operator can start with a so-called basic configuration with one working BCSU HW and activate TRX capacity flexibly in 1 TRX basic SW license steps. Similarly PS data capacity is available in 256 channels (Abis 16 kbit/s) steps. Thus 4 x 256 channels steps enable full capacity of one PCU2-E unit providing full flexibility there.


th April 2011

23 / 31

Q: What are the main improvements when comparing to existing products?

A: Flexi BSC offers more CS and PS capacity in compact size, smaller power consumption per offered capacity, as well as new technology towards IP based transmission for offering most cost-optimal BSC solution.

Q: How the Flexi BSC can provide so much more capacity?

A: There are new pre-processors such as Packet Control and signalling units and SW is optimized for better performance.

Q: How far can the new Flexi BSC stretch, any proven figures?

A: The maximum capacity is 4200 TRXs. The Erlang capacity is 25200 Erlangs with the reference call mix described in the Flexi BSC Product Description.

Q: What should be stated about the Flexi BSC BHCA figures?

A: The BHCA figure is call mix dependant. Exact BHCA figure will be confirmed after thorough performance testing as development program proceeds.

Q: How many BTS sites/sectors can be connected to one Flexi BSC with 4200 TRX capacity?

A: The Flexi BSC has huge flexibility with BTS topologies as it is capable of handling in maximum of 4200 TRXs, 4200 BTS objects and 3000 Base Control Function (BCF) objects per BSC. Number TRXs and BCFs depend on the number of active BCSU units.

Q: How are the BTS/BCF amounts compared to the HW/SW configuration?

A: Maximum amount of BCF objects in BSC depends on the amount of active BCSUs (BCSUs in WO-EX state). Amount of BCF objects is 500 under one BCSU with help of two AS7-D units. Similarly amount of BTS objects is always same as amount of TRXs i.e. 700 per BCSU.

Q: There will definitely be more signalling, how can it be handled?

A: Flexi BSC supports high capacity 64/128/256/512/1024/2048 kbit/s traditional SS7 signalling links and additionally SIGTRAN signalling over IP.

Q: How many E1/T1 links are provided?

A: The maximum configuration of 800 external PCMs E1/T1 is available with Flexi BSC.

Q: How many SDH/Sonet links are provided?

A: The maximum configuration of 18 external STM-1/OC-3 links can be provided. Plug-in units called ETS2 can provide two redundant STM-1/OC-3 interfaces. 9 ETS2 units can provide maximum amount 18 interfaces.


th April 2011

24 / 31

Q: Can SDH/Sonet and PCM links be used in same time?

A: Up to the certain extent both external interface types can be also used simultaneously.

Q: When the optional cabling cabinet is needed?

A: Optional cabling cabinet is used only for PCM connections. STM-1/OC-3 connections do not need cabling cabinet. Thus cabling cabinet is needed normally when more than 48 external PCMs is needed.

Q: How can you prove the promised capacity?

A: NSN will run thorough performance tests for the product.

Q: Have you had capacity problems or doubts with the old BSCs?

A: No we have not. All existing BSC variants perform the capacity guaranteed.

Q: Can you provide some Flexi BSC dimensioning examples – e.g. how much CS/PS traffic can be handled, and how many external PCM are needed?

A: As an example 2400 TRX in BSC for BTSs (typical 80 % BSC TRX fill-up ratio in one rack configuration).

2400 TRX with 4 pcs of HW capacity steps

1200 TRX, in CS use: 6TRX per PCM line (Average rule of thumb) : 200 Abis PCM needed.

1200 TRX, in PS use: (EDGE dimensioned 341kbit/s per TRX with Dynamic Abis) : 200 Abis PCM needed 6 TRX/PCM

Ater interface: 7200 Erlangs (29% of 25 200 Erl, one rack maximum) : 72 PCM needed

Gb interface: one duplicated 1 Gbit connection with Gb/IP connection.

Total PCM needed: 472 PCM (30 ET16 or 4+4 ETS2/ETIP1-A units)

Q: What is the benefit to use fewer larger BSCs instead of larger quantity of smaller ones?

A: The main benefits come from less operating costs and more economical capacity building capabilities providing savings in site costs, installation costs as well as overall benefits achieved in the radio network performance.

Q: Is there any difference in ANSI models compared to the ETSI models?

A: There is no difference in HW unit configurations in Flexi BSC configurations. Optionally external PCM cabling connections for ETSI market can be implemented using coaxial PCM cabling panels (separate optional sales items).


th April 2011

25 / 31

Compatibility

Q: Should other network element types be taken into account in planning Flexi BSC implementation?

A: Yes – the compatibility of RG20 SW release including Flexi BSC is tested thoroughly. See the RG20 FUD about planned compatibilities and latest release dependencies.

Q: Can the existing BSC3is be upgraded to the Flexi BSC model?

A: Yes.

Q: Is it mandatory to upgrade BSC3i to the Flexi BSC configuration?

A: No.

Q: Can the new Flexi BSC exist in the same network as the current models, i.e. are they fully compatible with each other?

A: Yes, they are. Introduction of the Flexi BSC into the network does not require any changes to the current network elements since all the interfaces are the same.

Also, the same SW functionality is used for both Flexi BSC and the earlier network elements, so the same features work throughout the network. Therefore the SW does not affect network functionality from the end-users’ point of view, even if both mechanics are in use. The SW package build, however, is different and therefore different SW files are used.

Q: Are all old BSC elements (BSCi, BSC2i, and BSC3i) compatible with this new Flexi BSC model with S15 SW?

A: Earlier BSCi, BSC2i, and BSC3i are compatible with new Flexi BSC configuration. The new Flexi BSC is based on DX 200 platform having all the same interfaces and functionalities as before, so there will not be any problems integrating Flexi BSC-models to an already existing network.

Q: Is there same software release for both old BSCs and Flexi BSC.

A: yes

Q: Which are the common parts in BSC3i 660/1000/2000 and Flexi BSC models? What about spare parts?

A: The architecture is basically the same, but Flexi BSC has latest HW plug-in unit versions for the areas requiring enhanced processing power and for improved interface connections. Detailed plug in unit list is available in internal guidelines slides.


th April 2011

26 / 31

Availability

Q: When is the Flexi BSC-model available?

A: Flexi BSC product configuration with 3000 TRX has been commercially available for deliveries with RG10 SW release starting from the beginning of 3Q09. Flexi BSC product configuration with 4200 TRX is available from 2Q/2011 (in line with RG20 SW release).

Replacement strategy

Q: How to position the existing BSC3i and the new Flexi BSC?

A: They have different maximum capacities: existing BSC3i: 660 TRXs and 1000/2000 TRXs, the new Flexi BSC 4200/3000 TRX.

Q: How do you recommend an operator to use the Flexi BSC? Should we start replacing all existing BSCs with the Flexi BSC?

A: Every operator should consider their network structure and the capacity needs in different parts of the network, and then make the decision whether it is reasonable to upgrade or replace the existing BSCs with Flexi BSCs. However, every effort should be made to ensure offering Flexi BSC always as the preferred BSC product. For example Flexi BSC could easily replace old BSCi/2i to gain benefits of network modernisation.

Q: What kind of network topology do you recommend?

A: The network topology always varies from network to network, so it should always be considered separately. One important thing that needs to be taken into consideration when defining the network topology is of course the transmission arrangements operator has, i.e. whether it is using own or leased lines.

Q: If we would like to replace an old BSC, how are we going to do that in practice without cutting service?

A: The new Flexi BSC will be installed usually in the night time when the traffic is low. All the preliminary tasks will be done in advance. When the old and new BSCs are both operational, the traffic can be transferred from old BSC to the new BSC via NetAct rehoming tool (BSS split).


th April 2011

27 / 31

Pricing

Q: Will the price of the Flexi BSC be less compared to the existing BSC3is?

A: Due to improved design we can cut the cost per Erlang, especially when you count the implementation and operational costs.

Q: What will this new BSC then cost?

A: The cost per Erlang tends to go down over time. The exact cost of a BSC, however, depends on the configuration and will be quoted on customer request.

Competition

Q: How does Flexi BSC model compare to competition?

A: Our target is that the Flexi BSC offers the highest traffic handling capacity (Erlangs) available in such a little space. Capacity, power and efficiency are provided within the same product with superior features.

Q: What makes the network cost-optimised?

A: First, Flexi BSC enables the smooth capacity evolution. Capacity and equipment can be added when needed. Second, the grooming of traffic minimises transmission costs with fewer transmission connections required. Third, the site costs are minimised. Fourth, the integration in bigger units means also fewer maintenance need.

Multicontroller BSC

Q: Will Multicontroller BSC replace Flexi BSC?

A: No, Multicontroller BSC will come as complementary module to ascertain future proof evolution path for Flexi BSC and also as new installation option on its own.

Q: What is the future of Flexi BSC?

A: Flexi BSC is key product for GSM/EDGE BSC needs for years to come and it will be developed further. It will offer connectivity to NSN’s whole installed base of BTSs and will benefit from Multicontroller BSC modules as capacity extensions in the future. The SW package will be the same.


th April 2011

28 / 31

Q: Will Multicontroller BSC is upgradeable to RNC?

A: Yes. In BSC application the control and user planes are divided between different HW computing entities, where the user plane is same as in RNC application. Multicontroller BSC can be easily transferred into RNC use module by module. Depending on module HW configuration in BSC use achievable RNC capacity varies. For example in Huawei solution there are only 6 out of 17 same cards between BSC and RNC and the actual upgrade from BSC to RNC is anything but smooth SW update.

Q: What SW release supports Multicontroller BSC?

A: Current tentative plan is to support volume deliveries in RG30. Piloting option is tentatively planned for 1H2011 and even earlier schedule option is under study.

Q: Will Flexi BSC SW release support end?

A: No, the SW will be common with Multicontroller BSC for securing the synchronisation of the functional development in both products. So the current product will continue in the networks for a long time and it’s functionality be developed further.

Q: What are the capacity figures of Multicontroller BSC?

A: This is very configuration dependant issue as the balance between control plane (TRXs) and user plane (packet data, transcoded voice channels) varies according to customer needs. Current estimate for TRX capacity is 4400 and for packet data channels 26400. The capacity per footprint will be very competitive and more than doubles against Flexi BSC.

Q: Can Flexi BSC benefit from Multicontroller BSC?

A: Yes! Multicontroller BSC modules can be used as capacity additions for Flexi BSCs.

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

A: Multicontroller BSC supports IP interfaces as Flexi BSC supports on top of IP traditional E1/T1 and STM-1/OC-3 interfaces. Flexi BSC has cabinet based “fixed” mechanics as Multicontroller BSC is based on modules, which can just be compiled on top of each other providing additional flexibility in site installations and capacity building like Flexi BTS has proved during last 2 years.

Q: What platform is this? Does it offer real telecom reliability?

A: The Multicontroller BSC is based on an adaptive platform which is not limited to the BSC only but may be extended to a new range of applications in the near future. Multicontroller Platform HW architecture is made so generic, that it is easily adaptable to various network technologies in the future. This means that both the new hardware and software platforms are designed to fully support


th April 2011

29 / 31

favourable technological evolution. Availability and redundancy principles are planned in similar manner as with existing products to offer full telecom level reliability

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

A: Yes, combined BSC/RNC installations are supported and flexible HW architecture makes it easy and SW defines the functional mode of HW module being either BSC or RNC at the time. Please note, that there are some differences in HW modules between BSC and RNC. RNC cannot be transferred into BSC as such without adding additional modules containing BSC specific control plane computing platform. Amount of additional modules depends on needed BSC TRX capacity.

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

A: We are currently selling BSC3i 1000/2000 and making offers for Flexi BSC. It is very important to get customers to move their ordering to Flexi BSC, when it becomes available with RG10 with volume deliveries starting in 3Q 2009. As Flexi BSC is future proof product and can be extended with Multicontroller BSC modules, there is no need to start waiting for Multicontroller BSC as such.

Overall plan is following the logic that both Multicontroller BSC and Multicontroller RNC will come as complementary offering to ascertain future proof evolution path for earlier launched Flexi BSC and RNC2600 products. This means that in case of 2G Flexi BSC and Multicontroller BSC are complementing each other and offer flexible future proofness to operators. This means in real life plan to introduce Multicontroller BSC so that capacity can be flexibly extended also for the installed Flexi BSC base using new HW module implementation.

Q: What will happen to Flexi BSC being launched, how are we going to align roadmaps for Flexi BSC & Multi-controller

A: Overall plan is following the logic that both Multicontroller BSC and Multicontroller RNC will come as complementary offering to ascertain future proof evolution path for earlier launched Flexi BSC and RNC2600 products. This means that in case of 2G Flexi BSC and Multicontroller BSC are complementing each other and offer flexible future proofness to operators. This means in real life plan to introduce Multicontroller BSC so that capacity can be flexibly extended also for the installed Flexi BSC base using new HW module implementation.

Q: Does it mean that IP story for legacy BSCs will not be supported? - eBSC/BSC3i/FlexiBSC.

A: First step in implementing IP interfaces in to all connections of legacy BSCs is introduced in RG10 release where integrated IP/Ethernet interfaces are provided for Abis / Ater also supporting in real life IP/Ethernet connectivity for any BSC interfaces with BSC3i 1000/2000, Flexi BSC (and TCSM3i). Next steps are planned evolution in RG20 release where new IP interfaces (Packet Abis, AoIP) have been feature candidates. Whether all different IP i/f combinations


th April 2011

30 / 31

needs to be supported in RG20 is to reviewed during 1H09 when RG20 proceeds to C3 milestone freezing the feature content and implementation plans for this GSM release.

Q: When going for the Multicontroller - Do I still need a transcoder in 2G?

A: The Multicontroller BSC plan includes also transcoder implementation as a functional part of the BSC. Therefore the Multicontroller can be connected via the standardized A-Interface also to any other vendors MSC, without having the need for add transcoding cabinets.

Q: Can I use the Multicontroller to get rid of the transcoder cabinets in existing network installations?

A: Transcoding is always needed for voice calls in the mobile network. In 2G implementation optimized transcoding functionality is part of planned Multicontroller BSC functionality and therefore it can be used to modernize installed base of older Transcoders.

Q: What about signaling. Does the Multicontroller support also SS7 Signaling and SS7 on HSL?

A: Signaling is part of control plane functionality in Multicontroller BSC. Current assumption is to provide SIGTRAN (SS7 over IP) with Multicontroller BSC and therefore traditional SS7 links will be available by co-location with Flexi BSC.

Q: Does the Multicontroller also support BS2xx via BSS Abis – same like the Flexi BSC?

A: Yes, the SW is same as with Flexi BSC and provides therefore similar functionality. But we must keep in mind, that the issue here is actually the supported transmission media; BS2xx BTSs are not planned to support Native IP/Ethernet Interfaces requiring Packet Abis over Ethernet functionality.

Q: Is a BSC3i or Flexi BSC, which is expanded with a Multicontroller for GSM, seen as one network entity, meaning does it have only one SS7 DPC?

A: It is too early to provide detailed level of information like this at this phase of development. The level of integration in collocating Flexi BSC with Multicontroller BSC modules is most probably not 100%.

Q: Considering the requirement for a BSC now with Village Connection release 2.0, will the new Multicontroller also offer GSM only?

A: Yes, the Multicontroller platform is planned to support both GSM only (BSC) and WCDMA only (RNC) implementations. Village Connection release 2.0 is planned to be implemented on top of existing GSM products. Thus there are no specific requirements for Multicontroller implementation in VC 2.0 planned


th April 2011

31 / 31

Q: Is the same scalability I_BTS, distributed RAN and centralized RAN planned for GSM? - we need a common solution for locally switching GSM as well as 3G.

A: The plan in GSM is to allow flexible use of multicontroller BSC in both centralized implementations (typically few large BSC sites having high capacity configurations) as well as in distributed topology (small size multicontrollers located close to BTS) where Multicontroller BSC is providing major transmission savings by collecting the traffic and with local switching by supporting local call routing. In GSM there are no plans to integrate controlling functionality to the BTS itself (I-HSPA like).

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

A: The idea with Multicontroller is to support native IP/Ethernet interfaces as requested by customers in their “2G to Single RAN modernization plans” with strong desire to utilize common IP/Ethernet transmission resources in combined 2G/3G implementation.

From interfaces point of view this means Multicontroller support for Packet Abis over Ethernet connection towards BTSs, Gb/IP interface for packet data/SGSNs, AoIP towards Circuit core/MGWs and SIGTRAN signalling (SS7 over IP) for A -interface/MSS.“”.

When using Multicontroller in existing networks together with legacy BSCs and BTSs the idea is to give support for traditional transmission connections (E1/SDH) by Flexi BSC and co-locating the Multicontroller BSC modules for capacity extensions. Thus Multicontroller BSC alone is thus optimized for pure IP /Ethernet implementation.

Documents

Flexi BSC Product Overview.pdf