You are on page 1of 69

mcBSC/mcTC Architecture

Training
Specialist training
Igor Dziuba

1
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID

Objectives

BCN
Embedded SW
SW Loading Mechanism
Switches
Synchronization
BCN Level Configuration
HiGig
Site Connectivity

2
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID

Objectives

mcBSC

3
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID

BCN
Terminology:

BCN: Box Controller Node,


mcBSC and mcRNC HW
platform
mcETP: generic mcBSC or mcTC
ETP unit (ETME, ETMA,
mcETPc)
ETP: Used here as generic ETP
type (S15 ETP or mcETP)
mcPCU: PCUM, PCU unit in
mcBSC HW
Octeon card: Common name
for BOC-A and BMPP2-B units
Intel card: Common name for
BJC-A units
4
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

AMC: Advanced Mezzanine


Card, ATCA extension card
VCMC: Virtual Carrier
Management
Controller
MMC: Module Management
Controller
IPMI: Intelligent Platform
Management Interface
LMP: Local Management
Processor, Control processor
on the motherboard

BCN

BCXU Base Station Controller Signalling Unit

BJC-A OMU

BOC-A ETP

BOC-A ETP

BOC-A PCU

BOC-A PCU

BJC-A BCXU

BJC-A BCXU

BJC-A MCMU

HD

PTU BSAC-A

Basic HW structure:

MCMUMarker and Cellular Management Unit

PCU Packet Control Unit

PTU Packet Timing Unit

OMU Operation and Maintenance Unit

HDU Hard Disk Unit

ETP Exchange Terminal for Packet


5
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

HDD AMC SYNCAMC

Octeon Intel

BCN
Basic HW structure

6
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
Add-in Cards
Up to eight processor add-in cards provide the main processing power of the BCN.
The interfacing to the motherboard is independent of the type of add-in card used.
Depending on the add-in card type, an add-in card provides networking, TCP
acceleration, QoS, compression or digital signal processing features. The processor is
able to boot from a dual flash memory located on the add-in card. Two copies of the boot
code are stored in the flash memory for increased reliability.
Each add-in card provides four insertion slots for standard 30 mm high dual in-line
memory modules (DIMMs) containing synchronous dynamic random access memory
(SDRAM).

7
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
AMC

Each BCN module


contains two
Advanced Mezzanine
Card (AMC) bays into
which midsize singlewidth AMCs can be
inserted.

8
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
Basic HW structure

The main functional units of the mcBSC are:


Multicontroller BSC signaling unit (BCXU)
Marker and cellular management unit (MCMU)
Operation and maintenance unit (OMU)
Packet control unit for Multicontroller (PCUM)
Ethernet transmission processing for Multicontroller (ETM)
Internal communications (internal messaging) between the
functional units of the system is based on Ethernet

9
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
HW Management
The central hardware
management entity within a BCN
module is the node manager.
The node manager consists of
the virtual carrier management
controller (VCMC) and software
running on the local
management processor (LMP).
The interfacing from the VCMC
towards the various hardware
entities in the BCN module
conforms with the Intelligent
Platform Management Interface
(IPMI) specifications.

10
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
BCXU
The Multicontroller BSC signaling unit (BCXU) is a TRX-capacity unit of the
mcBSC. It performs those BSC functions that are highly dependent on the
volume of traffic. The BCXU consists of two parts, which correspond to the A
over IP (AoIP) and Packet Abis interfaces.
The AoIP interface part of the BCXU is responsible for the following tasks:

Performing the functions of SIGTRAN based SS7 signaling


Performing all message handling and processing functions of the signaling
channels connected to it

The Packet Abis interface part of the BCXU controls the air interface channels
associated with transceivers and Abis signaling channels. The handover and
power control algorithms reside in this functional unit.

11
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
Packet control unit for Multicontroller (PCUM)
The PCUM unit is an independent processing unit logically connected to the
BCXU. The PCUM unit performs all the data processing tasks related to
GPRS/EDGE traffic. It implements packet switched traffic oriented Gb and
Packet Abis interfaces in the mcBSC.
The PCUM controls GPRS/EDGE radio resources and acts as the key unit in the
following procedures:

GPRS/EDGE radio resource allocation and management

GPRS/EDGE radio connection establishment and management

Data transfer

Coding scheme selection

PCUM statistics

12
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

mcBSC basics
Ethernet transmission processing for Multicontroller (ETM)
ETMA

In the mcBSC A and Abis interfaces are connected to an IP network. The ETM
functionality terminates all external management, user and control plane IP
traffic, handling the Ethernet transmission processing which is related to AoIP
and Packet Abis interfaces in the mcBSC. The general ETM functionality
contains ETME and ETMA functionalities.
ETMA = ETPA in BCN-A Hardware (BOC-A Add-in card)
BMPP2-B add-in card implements ETME and ETMA functionalities with BCN-B
hardware
- Application SW is based on ETPA
- Same Processor Family (Octeon) and OS (Linux) as in ETP
- Redundancy Concept is SN+ (Load Sharing)
- No switchovers
13
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

mcBSC basics
Ethernet transmission processing for Multicontroller (ETM)
ETME
ETME = ETPE in BCN Hardware (BOC-A Add-in card)
- Application SW is based on ETPE
- Same Processor Family (Octeon) and OS (Linux) as in ETP
- Calls can be kept only in controlled switchover

14
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
MCMU
The MCMU has centralized cellular management functions for controlling cells
and radio channels for the mcBSC. The MCMU reserves and keeps track of the
radio resources requested by the MSC and the handover procedures of the
mcBSC. The MCMU also manages the configuration of the cellular network.

15
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
OMU
The Operation and Maintenance Unit (OMU) is an interface between the
mcBSC and a higher-level network management system and/or the user. The
mcBSC can provide full-scale traffic capacity even when O&M interface
towards NetAct is disconnected.
The OMU can also be used for local operations and maintenance. The OMU
receives fault indications from the mcBSC. It can produce local alarm printouts
to the user or send the fault indications to NetAct.
The tasks of the OMU can be divided into four groups:

Traffic control functions

Maintenance functions

System configuration administration functions

System management functions

16
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
Redundancy
Different redundancy schemes applied to different functional units:

BCXUs are N+2 redundant:

2 spare BCXUs enough to replace the BCXUs of one failed BCN


PCUMs are N+M redundant:
Enough spare PCUMs to replace all PCUMs in one failed BCN.
ETMEs are N+M redundant:
Enough spare ETMEs to replace all ETMEs in one failed BCN.
ETMAs are SN+ redundant:
All ETMAs are active: the traffic of a failed unit distributed between the remaining active units.
MCMUs are 2N redundant:
A dedicated spare stands by ready to take over the tasks of the failed unit.
OMU not backed up
BCN module level redundancy:
- There is always sufficient spare unit capacity to replace the units in any single failing BCN module

17
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

mcBSC basics
Connectivity & Capacity (BCN-A)

18
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

1 ETM can handle 1100 BCFs


11 logical PCUMs can be connected to one ETM

mcBSC basics
Connectivity & Capacity (BCN-B/BMPP2-B)
Intermediate capacity steps are not supported with 2nd generation HW BCN-B and BMPP2-B

19
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
Basic Module 1

20
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
Basic Module 2

21
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
TRX Extension Module

22
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
PS Extension Module

23
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
mcBSC SW architecture

BSC control plane


& O&M applications

PCU applications

ETP applications

CDX SW platform

PCU SW platform

ETP SW platform

Linux

Linux

DMX SMP

Multi-core Intel hardware

24
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

SE

Multi-core Octeon hardware

SE

BCN
mcBSC SW architecture
BSC control plane & O&M applications
provides the BSC application functionality, like:
CS call handling
A-interface and Abis signalling
System level resource management
Radio network configuration management
O&M and statistics interfaces

DMX SMP - Proprietary operating system for DX


platform:
Supports symmetric multiporcessing (SMP) on
multicore processors
PCU applications:
Provides the (E)GPRS control- and user plane
functionalities

CDX SW platform
Provides the computing and switching platform
services for the application:
Functional unit state management, supervision and
recovery
Signalling protocol stacks
System configuration management

25
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
mcBSC SW architecture
ETP applications provides the user plane handling
on:
Voice and CS data calls on Packet Abis
(E)GPRS traffic on Packet Abis
Voice and CS data calls on A over IP interface
PCU SW platform & ETP SW platform provides
the unit level platform services to application and
integration to CDX SW platform:
Communication with other units
Unit state management and supervision

26
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Linux provides unit level operating system services for


management and control functions:
Resource management
HW integration
SE (Cavium Simple Executive):
provides lightweight OS or HW abstraction services
for user plane data handling

BCN
BCN-A connections & LEDs

27
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
BCN- A Interfaces
Six 10 GigE (SFP+ or SFP) interfaces for external cabling and intermodule cabling
Sixteen 1 GigE (SFP) interfaces for external cabling
Two additional 1 GigE (SFP) interfaces provide access to add-in card
slots 1 and 8 for network element management purposes
One 1 GigE (1000Base-T) interface for local hardware management and
debugging purposes
Two USB 2.0 interfaces for software downloading (typically during
commissioning)
Direct RS232 interface to the local management processor (LMP) for
debugging purposes
USB 2.0 slave port for software debugging purposes
SAS connector for hard disk cross-connecting between two BCN modules
two RJ 45 connectors for eight external voltage-sensitive alarm inputs
two external synchronization interfaces (E1, T1, JT1, 1.544 MHz, 2.048
MHz)

28
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
BCN-B connections & LEDs

29
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

BCN
BCN- B Interfaces

seven 10 GigE (SFP+) interfaces for external cabling and inter-module


cabling
two 10 GigE (SFP+) and ten 1 GigE (SFP) interfaces for external cabling
two additional 1 GigE (SFP) interfaces provide access to add-in card slots
1 and 8 for network element management purposes
one 1 GigE (1000Base-T) interface for local hardware management and
debugging purposes
two USB 2.0 interfaces for software downloading (typically during
commissioning)
direct RS232 interface to the local management processor (LMP) for
debugging purposes
USB 2.0 slave port for software debugging purposes
SAS connector for hard disk cross-connecting between two BCN modules
two RJ 45 connectors for eight external voltage-sensitive alarm inputs
(with 1 mA pull-up load)
two external synchronization interfaces (E1, T1, JT1, 1.544 MHz, 2.048
MHz)

30
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

a special 1 GE interface, the trace


port, is used for providing a
connection to an external traffic tracing
server. The trace port is also used for
port mirroring, which allows mirroring
of any port connecting to the HiGig
virtual backplane to the trace port.

BCN
BCN-A Internal Switch Domain

BCN-A module has


three separate
switch units.
Only Main and
Extension switches are
accessible.

Network interfaces 1GigE


Fiber or Copper SFP

31
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Network interfaces 1GigE


Fiber or Copper SFP
Used for BCN interconnection.

BCN

Add-in Card

Embedded SW architecture
VCMC

Node Manager
Ethernet switch
Management

(LVL 7 + BCM SDK)

MCH
(RMCP for SYM
)

Wind River Linux


HW
Diag
and util

Device Driver

MMC

IPMI OEM
Commands

IPMI
Commands

MCMC FW

PigeonPoint
AMC Module
FW

NXP
LPC2368

Serial

Node Manager
SW running on
PowerPC
One in each
Node

32
12/8/16
Confidential

IPMI OEM
Commands

IPMI
Commands

Boot Loader(uboot)

PowerPC8545 (LMP)

application
CDX or ETP/PCU
Platform

IPMB-L
100Base-T

Virtual
Carrier
Management
Controller
One in each
Node

IPMI Utility
WRLinux
or DMX
Device Driver
Boot Loader
(uboot)

Atmel
ATmega
128

Octeon56xx

Module
Management
Controller
One on each
Add-in Card

Main board
VCMC (Flash & FRU data) LMP
(Flash banks 0 & 1)
CPLDs

Octeon Add-in card (BOC-A


or BMPP2-B, from S16.1
step3 onwards)
MMC (Flash & FRU data)
Boot flash (banks 0 &1)

Serial

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

HW
Diag
and util

Theres eSW/Firmware on

Octeon Plus SW
Or Intel SW
One in each
Add.in Card

Intel Add-in card (BJCA)


MMC (Flash & FRU data)
BIOS
Boot flash (DMX OS loader)
DMX FPGA

Embedded SW
BCN
The eSW of a BCN-A/BCNMB-B module is needed to initialize the hardware and perform an initial loading of
the system software build during the unit startup.
The eSW images are programmed into the unit's FLASH memory and are managed as plug-in unit typespecific entities.
The BCN-A module eSW file names are formatted as BNCxxyZZ.IMG, where 'xx' is MB for BCN-A module,
and 'y' is K for the KERNEL file, B for the loader (UBOOT) file, and F for the file system (ROOTFS). For
example, BNCMBKZZ.IMG is a file name for BCN-A kernel file.
The BCNMB-B module eSW file names are formatted as BNCxxyBZ.IMG, where 'xx' is MB for BCNMB-B
module, and 'y' is K for the KERNEL file, B for the loader (UBOOT) file, and F for the file system (ROOTFS).
For example, BNCMBKBZ.IMG is a filename for BCNMB-B kernel file.

33
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Ebbedded SW
BJC-A
The BJC-A add-in card is a computer plug-in unit.
The eSW images are programmed into the unit's flash memory.
The BOOT, FPGA, BIOS/BACKUPBIOS and BIOSBB/BACKUPBIOSBB eSW can be updated in the BJC-A
add-in card.
The BIOS for BIOS/BACKUPBIOS options is upgraded without the boot block while
BIOSBB/BACKUPBIOSBB upgrade is done including the boot block.

34
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Embedded SW
BOC-A
The eSW of a BOC-A card is needed to initialize the hardware and perform an initial loading of the system
software build during the unit startup.
The eSW images are programmed into the unit's FLASH memory and are managed as plug-in unit typespecific entities.
The BOC-A add-in card eSW file name is BNCOCBZZ.IMG for the loader (UBOOT) file.

35
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Embedded SW
BSAC-A AMC
The eSW of a BSAC-A Advanced Mezzanine Card (AMC) is needed to initialize the hardware and perform an
initial loading of the system software build during the unit startup.
The eSW images are programmed into the unit's FLASH memory and are managed as plug-in unit type-specific
entities.
The BSAC-A AMC eSW file name is BNCSAUZZ.IMG for the UCSW file.

36
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

SW Loading Mechanism
Octeon
- Same SW Loading mechanism is used for all Octeon
based add-in-cards, i.e. PCUM, ETMA and ETME use
the same mechanism
- In the BOC-A, the flash does not contain any
application SW, thus the application SW must be
loaded on every restart
PCUM: BCXU will act as the loading source
ETMA and ETME: BCXU will act as the loading source
During actual loading, only pure IP-protocols like DHCP
and TFTP are used. During SW loading, no DMXmessaging (including IUA-messaging) happens
between the loading BOC-A and the rest of the system.

37
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

SW Loading Mechanism
BCN Startup Phases

Power ON
3.3V Standby Power

EthernetSwitch
Switch
Management
configures Ethernet
Switch Domain
according to Initial
Switch Configuration

VCMC Boots up
Power ON
12V Payload Power

VCMC normal opr.

Node Manager
configures Add-in
Cards and
Motherboard
according to BCN
Configuration file

LMP Reset
LMP Boots up
Node Manager is
running

Node Manager
loads Node
Configuration
Script from
Working SMS

Load Node Config.

Octeon Boot

NMg. Normal operation

Add-in Card receives


and sets pre boot
strapping
Octeon Boot source
selection

Boot Scripts
resides in
Octeon Flash
Memory

Failsafe starts

Failsafe Boot

Auto Script is
loaded from
Working SMS
Hard Disk to
Octeon
memory

38
12/8/16
Confidential

U-Boot reads
Boot Script
Number from
MMC

Boot script 1

Boot script n

Load Auto Script and


start it

Load Auto Script and


start it

Auto script #a

Auto script #b

Auto script #a

Auto script #b

Run Auto Script

Run Auto Script

Run Auto Script

Run Auto Script

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

-Octeon starts U-Boot


-Booot
-Reads Boots Script
number and start the
script

PCIe Boot

SW Loading Mechanism
Octeon
Inside the mcBSC modules LMP acts as the Shelf
Manager. Thus LMP controls the start order of the
add-in-cards, and decides how they are started
(where from they are supposed to load the SW)
Further, LMP also acts as the control computer for
the modules LAN-switch, and thus LMP does the
initial configuration of the modules LAN-switch
When BOC-A starts and enters the u-boot phase, it
does not yet know whether it will function as PCUM,
ETMA or ETME; the function will depend on the
loaded application SW
When BOC-A starts and enters the u-boot phase, it
does not have an IP-address

39
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

SW Loading Mechanism
Octeon
In order to start actual SW loading, starting BOC-A Note: In order SW Loading to work correctly, equipment
must get an IP-address and tell the platform about info in HW configuration database and add-in-card info
itself
in the modules FRU data (part of LMPs flash content)
This is achieved by DHCP. To be more specific, the must match
DHCPDISCOVER message not only requests an IP- For example, first module equipped as 1A1 =>
CLI> SetNodeNumber 1
address, but also contains NSN specific location
CLI> SetRackNumber 65
info.
The
starting BOC-A should receive a DHCPOFFER
65 decimal corresponds to ASCII A
message with an IP-address and path to a file to be
loaded

40
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

SW Loading Mechanism
Octeon
OMU

There are two different kind of DHCP servers in the


system:
TFDHCP: serves LMP, MCMUs, BCXUs
ORZDHC: serves PCUM, ETME/A
For the actual file loading, D2TFTP server is used.
It exists in MCMU, OMU, BCXU
Each BCXU can serve as loading source. Thus each
BCXU is including a TFTP server.
Images are first loaded from OMUs disk into RAM disk
to the computer selected as loading source.
After loading, files will be left on the RAM disk, thus not
requiring a re-load from OMUs disk for the next usage

TFD

LMP

D2T

BCXU

MCMU

D2T

D2T

PCUM

ORZ

ETME/A

DHCP clients of TFD:BJC-A, LMP


DHCP clients of ORZ: PCUM, ETME/A

41
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

DHCP

TFTP

SW Loading Mechanism
Octeon
DHCP server contacts SLVMAN program block in order to
get an IP-address, function of the specific BOC-A and thus
name of the boot image
- IP-address is got from IM1MAN
- function is queried from HWILIB, based on the received
location info
- name of the boot image is hard coded into SLVMAN
Actual load consists of four files, the first one (SCRA.IMG,
which actually is a boot script mentioned before) specifying
the actual images for:
- Linux kernel (KRN.IMG)
- Linux application (.GB.IMG)
- Simple Executive application (SES.IMG)
All these files are part of application SW build and not part
of DX 200 platform SW build

42
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Switches
A Multicontroller BCN unit comprises three Broadcom Ethernet switch processors integrated on the
Motherboard: BCM56820 (main switch), BCM56512 (extension switch BCN-A), BCM56514 (extension
switch BCN-B) and BCM53212 (management switch). The Multicontroller platform runs under the
WindRiver Linux OS and provides Layer 2 switching functions using a FASTPATH PCI bus through the
Main and Extension switches. The management switch is used for providing a connection between LMP
and Main switch and it is not controlled through Fastpath command line interface. Add-in card slots has
a Fast Ethernet connection to Management switch but those connections are not used by mcBSC
Two 10 Gigabit Ethernet XAUI interface implements the interconnection between Main and Extension
switch.
Main purpose of the Ethernet Switches in the Multicontroller platform is to perform functions like traffic
aggregation, VLAN tagging / untagging and providing loop free topologies utilizing Multiple Spanning
Tree and HiGig protocols. Broadcoms FASTPATH software is used to support these functionalities.

43
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Switches
Configuration files of BCN-A switches

44
12/8/16
Confidential

Main Switch directories and files

Extension Switch directories and files

1.
2.
3.
4.
5.
6.
7.

/mnt/fastpath/config.bcm
/mnt/fastpath/module/init.soc
/mnt/fastpath/startup-config
/mnt/fastpath/module/post.soc
/opt/cluster/m<module_id>/u0/phy<port_id>up.soc
/opt/cluster/m<module_id>/u0/phy<port_id>down.soc
/opt/cluster/m<module_id>/ext/node<nbr>port4up.soc

/mnt/fastpath2/config.bcm
/mnt/fastpath2/module/init.soc
/mnt/fastpath2/startup-config
/mnt/fastpath2/module/post.soc
/opt/cluster/m<module_id>/u1/phy<port_id>up.soc
/opt/cluster/m<module_id>/u1/phy<port_id>down.soc

8.

/opt/cluster/m<module_id>/ext/node<nbr>port4down.soc

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Switches
Configuration files of BCN switches
1. BCN switch related settings.
2. init.soc: Can be used to execute SDK commands before standard FASTPATH configuration is
loaded. HiGig commands and interface specific initializations are given in this file.
3. startup-config: The Default FASTPATH startup configuration file. It has a binary header, not a pure
text based file.
4. post.soc: Can be used to execute SDK commands after the FASTPATH has finished the normal
startup sequence. HiGig related post-command are given here.
5. phy<port_id>up.soc: When the related <port_id> link goes up, FASTPATH will run the SDK command
defined in this file. HiGig configuring is done by using these files in the Main switch.
6. phy<port_id>down.soc: When the related <port_id> link goes down, FASTPATH will run the SDK
command defined in this file. HiGig configuring is done by using these files in the Main switch.
7. node<nbr>port4up.soc: The content of the file is executed when the module receives corresponding
control message from the neighbor module.
8. node<nbr>port4down.soc: The content of the file is executed when the module receives
corresponding control message from the neighbor module.

45
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Switches
Flashbanks
Box Controller Node (BCN) is designed to have a two physically separated flash inside, which
contains the running embedded software (eSW) and the necessary configuration files (e.g.: Main
and Extension Switch configuration) to ensure if some unrecoverable problem happens with one
of the flashbanks then the other is still able to boot up the whole box by switchovering the
flashbanks.
Current implementation requires both flashbanks to be separately configured.
Refer to TS-BSC-SW-0910 for further details.

46
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Synchronization
Synchronization source of mcBSC can be either ToP synchronization using PTUM cards or PCM based.
The master reference clock for mcBSC synchronization has to be the same which is providing
synchronization
to the base stations connected to the mcBSC.
PCM based synchronization
When PCM line (E1/T1/J1) is used as external clock
reference (synchronization source), it can be
connected directly to SYNC port on mcBSC module
front panel. PTUM units are not needed in this
configuration. It is strongly recommended to use two
PCMs to reach the required reliability.
The first PCM line is connected to SYNC 2 port in
the first module.
The second PCM line is connected to SYNC 1 port
in the last module.

47
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Synchronization
PTUM unit on BSAC-A pug-in-unit (AMC card) is used to get the
clock reference from external ToP (IEEE 1588v2) master clock or
from synchronous Ethernet clock. PTUM unit supports the following
synchronization sources:
2.048 / 1.544 MHz according to G703
PCM (E1 / T1)
Ethernet according to IEEE 1588v2
Synchronous Ethernet for optical connections
Following external input interface connections are supported by
PTUM:
2 x RJ-45 for E1/T1/JT1 (framed/plain) clock based
synchronization.
2 x SFP (Optical and Copper) for Timing over Packet and
Synchronous Ethernet based synchronization.

48
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

HiGig

HiGig is the Broadcom proprietary interconnecting technology used in


mcBSC
for connecting modules.
It refers primarily to the formatting of a packet for
transmission between switches integrated into modules. The basic transmission
method utilizes Ethernet packets which are modified to include a HiGig
Module header. HiGig also provides fast link failure detection mechanism with
less than 50 ms recovery time for links used for interconnecting Multicontroller
modules.
HiGig scripts used with Multicontroller platform are produced by NSN. The
scripts are copied into LMP during the commission phase and are activated
when switches are starting up.
The scripts are also totally invisible for end-users and usually no modifications
to content are needed.

49
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

HiGig

In standalone a full-mesh
cabling is applied.
Full-mesh = each unit in a
group is directly connected
to every other unit in the
same group

The precise cabling topology


varies depending on the
number of BCNs in the stack.
Correct cabling is always
explained in readme files
located in /opt/backplane0.3.9/

Cabling complies with the


HiGig configuration applied.

50
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Site Equipment Connectivity (BCN-A)

1GE
With 1GE connections
Totally 10 cables needed.
5 from M1 and 5 from M2.
One connection is reserved for
applications which have low capacity
requirements. For Packet Abis,Packet
Ater/ AoIP two LAGs with two GbE
connections each are configured
.

51
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Site Equipment Connectivity (BCN-B)


10GE
With 10GE connections
Totally 2 cables needed.
1 from M1 and 1 from M2

52
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Site Equipment Connectivity


Ethernet
Ethernet

MLS-0

IP
i
MLS-1

Site equipment.

LAG

T10 T44
T32 T45

T46
T47

T33 T48
T35
T36
T49

LAG

34

LAG

34

ToP Master

mcBSC modules

T10 T44
T32 T45
T33 T48
T35
T36
T49

T46
T47

LAG

LAG

T10
T32
T33
34
T35
T36
T44
T45
T46
T47
T48
T49

53
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

O&M [3]
SIGTRAN-1
SIGTRAN-2
Sync
ETPSIG-M
ETPSIG-C
OMUSIG
TRXSIG
AoIP
Packet Ater
PAbis
Gb

mcBSC basics
External LAN architecture

Traffic between mcBSC and Site equipment


Ethernet (L2) connected
Several mcBSC VLANs are visible to Site
Equipment
VLAN IDs used in each mcBSC and every other

network element with L2 interface to Site


equipment must be unique for each such
element.
The same base VLAN IDs used in all mcBSCs.
VLAN differentiation done on the basis of
mcBSC-specific prefixs: e.g. an mcBSC uses
prefix 11 VLAN PEP (22) identified as 1122
and VLAN sigtran-1 (32) as 1132.

Loop prevention at Site Equipment

HiGig is not extended over the mcBSC & Site


Equipment interface.
The risk of Ethernet loop creation and traffic
storms.
Recommended method for L2 loop prevention:
disrupt the loop between the Site Equipment
pair by alternatively configuring an L3 interface
between the Site Equipment pair.
If an L2 interface between the Site Equipment is

required for other purposes, it must be configured to


reject mcBSC VLANs.

Routing done at Site Equipment (preferably)


Routing at Site equipment recommended for

configuration simplicity.
Routing point may be further down in the
network, but this leads to complex network
cumbersome
NW- Creator - DocID
54
12/8/16 configuration
Nokia 2014and
- File
Name - Version
management
Confidential

Dept. / Author / Date

L3 interface

Objectives

mcTC

55
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID

mcTC Basic Module

MCU
MCU

The
Themanagement
managementand
andcontrol
controlunit
unit(MCU)
(MCU)
implements
implementstranscoder
transcodercontrol,
control,
management
managementand
andcentralized
centralizedO&M
O&Mtasks
tasks
ininthe
themcTC
mcTCmodule.
module.

56
12/8/16
Confidential

TCU
TCU

The
Thetranscoding
transcodingunit
unit(TCU)
(TCU)implements
implements
transcoding,
transcoding,rate
rateadaptation
adaptationand
andadditional
additional
media
mediaprocessing
processingfunctions
functionsfor
forthe
themcTC.
mcTC.

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

ETP
ETP

The
TheEthernet
Ethernettransmission
transmissionprocessing
processingunit
unit
(ETP)
(ETP)terminates
terminatesthe
theuser
userplane
planeIP
IPtraffic
traffic
over
the
Ater
and
A
interfaces.
over the Ater and A interfaces.

mcTC Functional Architecture

57
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

mcTC internal functional units


MCU = mcTC NE controller unit
- Flexi Platform node controller
TCU = mcTC Transcoding unit
- Actual DSP resources (TCSUs)
mcETPC = ETPC on mcTC
- Physically terminates ETPSIG-C/M interfaces
- A-interface U-plane (like ETPC)
- Packet Ater U-plane

These units are not visible in mcBSC!

58
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

mcTC HW Configuration
mcTC HW components are:

One BCN box with PEM and FAN units

One HDU unit (AMC)


One ETP unit (Add-in card)
6 TCU units (Add-in cards)
One MCU unit (Add-in card)
6* SFP (1GE) or 2*SFP+ (10GE) for user, control and O&M plane connections
2-6 Ethernet cables
Reference clock RJ45 input cable (e.g. E1) or
Optional PTU unit (AMC) + at least one SFP (1GE) and one 1GE cable for
synchronization input (and possibly RJ45 cables for connecting reference timing to other
mcTC units)

59
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Power Supply

mcTC HW Configuration

1-8 Add-in Cards

AMC Slot

60
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Motherboard

mcTC SW architecture

Transcoding applications
dSPEED (DSP mgmt &
Flexi platform)

dSPEED
(DSP platform)

Linux

OSEck

Unit computer
hardware

DSP
hardware

ETP applications

MCU applications

ETP SW platform

Flexi platform

Linux

SE

Multi-core Octeon
hardware

Multicontroller TC software architecture

61
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

Linux
Multi-core Octeon
hardware

mcTC Connectivity (External Interfaces)


Gigabit Ethernet interfaces
IP over Ethernet network interfaces with protection
possibility are provided in the front panel of the module.
One module may contain up to 16 Gigabit Ethernet
interfaces and up to 6 interfaces, that can be used
either in 1 Gbps or 10Gbps speed.
In addition to these connections there are two 1GE
interfaces directly connected Add-in card slots 1 and 8.
All these interfaces use standard SFP and SFP+ (for
10GE) connectors.
Only 10GE capable interfaces (in 1GE or in 10GE
mode) are being used in the mcTC configuration.

62
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

LAN/Ethernet for O&M connections


The local area network interface functions at the rate of
10/100/1000 Mbps using an RJ45 connector located in
the front panel.
SW download and SW debugging interfaces
In the front panel there is one USB type B interface for
debugging and two USB type A interfaces for SW
download (not used during normal operation).
Serial Port Interface
Standard RS-232 interface with a RJ-45 connector,
used for connection to the Local Management
Processor on the motherboard.
External Alarm interface
Two standard RJ-45 connectors, used for collecting
external alarm inputs for monitoring purposes.

mcTC Connectivity (External Interfaces)


External Telecom Synchronization Interface
Two standard RJ-45 connectors, used for external
2/1.5 MHz input and output reference.
External Packet Synchronization Interfaces in
BSAC-A AMC
Standard SFP connector used for external 100M/1GE
Ethernet providing IEEE 1588 or Synchronous Ethernet
timing.
Standard RJ45 connector, used for external
1.544/2,048 MHz input (and 2.048 MHz output)
reference.

63
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

mcTC/mcBSC Control Plane

ETP
Master
BSC

ETPSIG-m

Client
BSC

ETPSIG-c

Client
BSC

ETPSIG-c

MCU
TCUSIG-m

TCUSIG-c

64
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID

TCU

MOM

TCM
TCC

LINX

mcTC/mcBSC User Plane

mcBSC 1
Packet Abis
over Ethernet

ETMA
ETME

IP BTS

S
W
I
T
C
H

Packet Ater

AoIP
mcTC

mcBSC 2

S
W
I
T
C
H

Packet Abis
over Ethernet
IP BTS

ETME
ETMA

65
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID

Packet Ater
Support for multiple BSC

MGW

mcTC Connectivity (Object Relations)

66
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

What remains the same as in FlexiBSC/BSC3i


In mcBSC MCTC is managed with MML
Like ETPC management
Resource management remains on BSC
Static TCSU resources for BSC call control
NetAct interface through master BSC
FM, alarm handling
PM, statistics
NOTE!
mcTC is Flexi platform based NE
Local management is through SCLI on MCU

67
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

mcTC capacity
Maximum channel connectivity of one mcTC is 5040 (in case of multislot
HSCSD number of calls is 5040/4=1260).
1 TCSU can handle 84 channels.
10 TCSUs per one TCU PIU.
6 TCU PIUs per one mcTC

68
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID


Dept. / Author / Date

69
12/8/16
Confidential

Nokia 2014 - File Name - Version - Creator - DocID