Evob200 BSC: Ran Modernization Project

EVOb200 BSC
RAN MODERNIZATION Project
Ghana Ericsson
EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 1
1
EVO8200 BSC
Technical
overview

AGENDA
• EVO8200 Introduction, comparison with the current GSM controllers
• Hardware overview
• EVO8200 BSC Capacity
• NWI-E
• SCXB
• CMXB
• EPB1
• EPB Blade Concept
• CTH Concept
• Virtual RPs, CTH Load Balancing, Redistribution
• EVO ET Board
• Packet Abis over TDM
• Hardware Activation Codes (HWAC)
• Dimensioning
• Integration Experiences
• Roadmap

ERICSSON BSC FOOTPRINT EVOLUTION
SUPPORTING 2048TRXs
BYB 202
BYB501/AXE10
GS10/12 High Capacity
GDM (Mega BSC) High Density
APZ 212 30 EvoC 8200
GS890 GS890
IOG20 No GS
GEM and GDM EGEM
ET155-7 EGEM2
APZ 212 33C APZ 212 55
TRA R5 APZ 212
APG40C APG43
RPG2 & RPP/4 60F
ET155-1 ET155-1/2
APG43/3
TRA R6 TRA R7
EvoET
RPG3 & RPP/5/6/7 GARP-2
No TRA
(TRHB, GPHB,
EPB1
PGW, AGW)
BYB501 BYB501 BYB501 BYB501

GDM GEM EGEM EGEM2
BYB202
1991 1995 2000 2008 2012

BSC HW Configurations
HD BSC
• SIGTRAN only on RP, GARP-2 boards, EGEM magazines

• For G10A and earlier HD is the only alternative
• Supported a long time
Evo Controller 8100

TDM+IP
• Using same boards as HD BSC, EGEM2 cabinets introduced
• A BSC, which is RNC-ready for future WCDMA expansion
• Supported a long time, from BSC release G10B and onwards
Evo Controller 8200

TDM+IP
• Built on EPB, EVO ET

very high capacity and small footprint
• Supporting IP and packet Abis over TDM

Hardware overview
HD BSC Evo 8100 Evo 8200 Evo 8200
CP APZ 212 55 APZ 212 60C APZ 212 60C APZ 212 60F
AP APG43 & 43/2 APG 43/2 APG 43/2 APG 43/3 Linux
Magazine EGEM EGEM2 EGEM2 EGEM2
Magazine
SCB-RP/4 SCXB SCXB SCXB
switch
BSC LAN Switch
LAN Switch NWI-E NWI-E NWI-E
/NWI-E
RP GARP-2 GARP-2 EPB, EVO ET EPB, EVO ET
Group Switch GS 890 GS 890 No No
Packet Abis over
GS and ET155-1 (all GS and ET155-1 (all Packet Abis over TDM (EVO ET)
TDM support
interfaces) interfaces) TDM (EVO ET)
Sigtran on RP (GARP- Sigtran on RP (GARP-2) or

SS7 1) or SS7 on STEB SS7 on STEB
Sigtran on CP Sigtran on CP

Evo Controller 8000
• Evo Controller 8100 • Evo Controller 8200
(Intro. of EGEM2)
(EGEM2 + EPB)
–TDM & IP – High Capacity RNC & BSC
– IP and some TDM
› Cabinet
› Subrack (EGEM2) EPB EPB & EvoET
› 28 slots
› Dual Fabric Dual Star
› 1 Gbps Ethernet
› 10 Gbps Ethernet
› 40 Gbps forward compatible backplane EPB Ethernet switches
› Power & fan module
(SCXB and CMXB)
Active Patch Panel

(APP)
Support from G10B Support from W11B & G12B

EVO8200/BSC GS less

EVO8200 BSC
Hardware overview

EVO8200 BSC
› Capacity
› Evo Controller 8200 – 256-4096 TRX

› 4096 TRX in 1-2 Subracks (min 4 EPB1*)
› HW prepared for 8192 TRX on
G14B
› Up to 12283 TRX in 1 cabinet, 3
logical BSCs
› Size
– 600x400x1800 [mm] WxDxH per
cabinet
› External interfaces
– NWI-E: IP connectivity
– TDM option with 8 ports STM-1
*Traffic model has big impact, with BAS3 and 4 EPB1 4095 TRX,
11200 Erlang and 36 Mbps data is supported

COMMON HW - PFM
› Power and Fan Module (PFM) BFD 140 13/1
• Two Power and Fan Modules (PFMs) are

included in the lower part of each subrack,
providing power feeding to the backplane
and cooling air throughout the cabinet.
– There is redundancy in the PFMs. If one of
the two PFMs stops working, the other
PFM has enough cooling capacity for the
subrack.
– The PFM also has speed regulation
reducing the speed (based on ambient
temperature requirements).
Power Feeding is also redundant

EVO8200 Power interfaces
• Power cables are attached to the power connectors in
the PFMs and the APP units (in the further releases)
Unit Max power No. of power Circuit breaker PDU type

consumption branches size per branch
[W]
Subrack with 2400 3+3 30A HOD
two PFMs
2+2 40A LOD
APP 30 1 5-15A HOD/LOD
Node size (No. of Max. Power [W] Typical [W]

configurable EPB1
boards)
10 1590 1280
20 2460 1960
32 3880 3010
44 4860 3830
56 6220 4880
68 7260 5700
EGEM2-40 Backplane

EVO8200 BSC Main Subrack
The BSC Main Subrack always includes the APZ and has 10 slots
that can be equipped with EPB1 boards.
If the optional EVOET is Required. Its can be installed in slot 14
and 50.

Optional EVO-et board

BSC Main Subrack

EVO8200 BSC Capacity
• Capacity
– 4096 TRX in 1-2 subracks (planned 8192 from G14B)
– 10 Gb in one subrack
• Power Consumption
– 1.5 kW for a typical 4096 TRX
• Size
– 600x400x1800mm WxDxH cabinet
• External links
– NWI-E: IP connectivity
– 8x 1 ports
– 8 ports STM-1

EVO 8200 BSC Capacity on G14B

APZ 212 60F HW Architecture

APG43 Linux

AXE IO Evolution
IOG20
– based on Motorola M68060 with APN167 OS
APG40C/2
– based on INTEL Pentium III with Windows Server 2003 OS
APG40C/4
– based on INTEL Pentium M with Windows Server 2003 OS
APG43 and APG43/2

– based on GEP1 (SC) with Windows Server 2003 OS
– based on GEP2 (QC) with Windows Server 2003 OS
APG43 on Linux (APG43/3)

– evolution of APG43 based on CBA (LOTC, CMW, COM)
Componenet Based Application

APG43 on Linux
FEATURE IN SHORT
• The current Windows 2003 operating system on APG is
approaching End of Support
• Therefore the operating system is upgraded to Linux on APG43,
which will also result in OPEX reductions
(Note: APG40 will stay on Windows until end of life)
CUSTOMER BENEFITS
› OPEX Reduction
- Improved SW update time ~ 45 min
(3 times faster than Windows)
- Centralized user management reduces administration
- Less security packages

APG43L Benefits
• Linux reduces the APG43 update time to ~ 45 min
(instead of > 2 hours with Windows, 2-3 times faster)
• Centralized User Management
User A User A
User B User B
…
X N 1 X …
OSS BSC User X OSS BSC
User X
• Improved usability, security and robustness

(model based O&M, Linux not exposed to APG users,
less security packages)

APG43L Key Characteristic (BSC)
› AP SW Update ~4 times faster
› 25-50 min
200
150 ONLY APPLICATION

CORRECTIONS
100
50 APPLICATION &
OPERATING SYSTEM
0
› AP Backup ~10 times faster CORRECTIONS
APG43 on LINUX APG43 Windows
› 3 min
SW Update (min)
› AP Restore ~7 times faster
› 9 min 35 70
30 60
25 50
20 40
› Max number of STS counters
15 30
› APG43/2: increased from 5 to 10 million counters
› APG43: kept 3.5 million counters 10 20
5 10
0 0
APG43 on Linux APG43 Windows APG43 on Linux APG43 Windows
Backup time (min) Restore time (min)

CBA-Componenet Based
O
A
Application Architecture
M Middleware
Overall structure
OS
Key interfaces
Virtualization
Generic requirements
HW
Framework Architecture
Component Based Architecture Model
ME F
SF E
T
COM Applications
Realization of framework Java

Environment
Erlang
Environment
vDicos
Environment
architecture Signaling
License
Manager
Component
X
Component
Y
Core Middleware
Linux
Specification of behavior and Virtualization
design rules HW System

APG43L New Operational mode for (ordinary)
AP Session
› Configuration of APG43L is based on MOM (Managed Object Model)
› Managed Object (MO) classes are organized in a tree hierarchy
› An MO represents an physical/logical resource

› It contains attributes and actions which enable user read and change operations
ManagedElement
SystemFunctions
E///
SwM BrM FileM SecM SwIM SysM AXE Functions
AXE
CertM
› Unified E/// O&M.

Significant reduction ~75% (200 -> 50) of APG commands
From command to model based
O&M
• Windows OS exposed to AP • Linux OS hidden to AP users
users – Less complex
– Too easy to misconfigure – Less possibilities to make
faults
• O&M through APG • Model based O&M
commands – Navigation through object
– More than 200 proprietary AP models
cmds – Uniform /// CLI style
– Help on line / autocompletion

APG43L File System Management
› File system can be accessed via (S)FTP and AP sessions via File Management
model (FILEM)
› Only a portion of data disk is exposed and made accessible
System Disk
Data Disk

OSS LDAP Server
• Roles
– Defined for each user, roles are used to determine access rights of the user.
Stored in LDAP as attributes, used only by the node.
• Targets
– Defined for each user, targets are used to determine which nodes a user can
access. Stored in LDAP as attributes, used only by the node.
– A target could represents the single node or group of nodes or all nodes,
where the role or alias is defined.

APG43L User Roles
Non-security Security Non-security Security MML
Roles Authority MOM MOM folders folders Session
AP cmd
SystemAdministrator Full access No Access Full access No access No Almost all
Read-only
SystemSecurityAdministrator No access Full access Full access No Few of them
access
Read-only Read-only Only listing

SystemReadOnly No access No access No
access access ones
EricssonSupport No access No access Only /tools No access No Only gmlog
Read-only to
CpRole0-CpRole15 No Access No access No access Yes Only alogfind
3 Top MOC

Background- facts

How to connect to APG43L Locally.
1.Serial console connection
Open a client for serial connection.
Connect TSR 491 637(RS232 -D-SUB9-RJ45) cable to Port eht-2 On the APG43/3
- Connection Type: Serial
- Serial line: COM<n>, where <n> corresponds to the used COM port
- Speed (baud rate): 115 200
- Keyboard: VT100+ (In order for function keys to work)
- Data Bits: 8 (default)
- Stop Bits: 1 (default)
- Parity: None (default)
Flow Control: XON/XOFF (default)
2.Serial console connection

Connect TSR 491 603 cable (D-RJ45) to Port eht-2 On the APG43/3.
On Win foil setup property
-192.168.200.1 Node A IP
On Local PC
-192.168.200.3
- 255.255.255.0 (Subnet mask)
- N/A Gateway IP (Default Gateway)
**Ensure to disable Symantec Endpoint Protect on your PC by changing to out of ericsson

Types of Login Sessions & Access.
• root
Remote login for “root” user is disabled. “root” can’t login to the node neither using port 22 nor using port 4422. For “root” the
access to the node is allowed only through console, serial connection.
• TS Session
TS session is opened using protocol SSH over port 4422. Only the troubleshooting administrator (tsadmin) and troubleshooting
users can login using this session.
1). Troubleshooting administrator (tsadmin)
2). Troubleshooting User (ts_user).
It is denoted with the prompt below;
# or $
• AP Session
An AP session is used to perform OaM operations on APG. An AP session is opened when an OaM user establishes a SSH
connection with the cluster IP address of APG on port 22.
AP session can be established only towards active AP node since COM, (Common Operation and Maintenance SW component)
runs only on active AP node. In case AP session is attempted towards passive AP node, the SSH connection is unsuccessful.
It is denoted with the prompt below;
>

Nwi -e

Cabling of EVO8200/BSC cabinets
CMX B
NWI E
SCX B
SCX B
CMX B
NWI E
SCX B
CMX B
SCX B
EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 36 CMX B
NWI-E
› NWI- E board ROJ 208 465/1
• NWI-E is a Layer2/Layer3 Ethernet switching plug

in unit for the Ericsson GSM/BSC
• Enables IP on the BSC external interfaces
• The front panel interfaces include

– 11 x 10/100/1000 Base-T Ethernet
– 2 x SFP supporting both electrical and optical GBIC
for Ethernet
– 1 x RS-232 serial management interface, used for
initial installation and for troubleshooting
– 1 x 10/100/1000 Base-T Local Ethernet
management interface used for troubleshooting

Front panel
The front panel interfaces include
– 11 x 10/100/1000 Base-T Ethernet
– 2 x SFP supporting both electrical and optical GBIC for

Ethernet
– 1 x RS-232 serial management interface, used for

initial installation and for troubleshooting
– 1 x 10/100/1000 Base-T Local Ethernet management

interface used for troubleshooting

Port Group Member ports
Internal 1-8
Crosslink 9,10
External 11-13
VLAN Name Member port groups

-SR_Gb, SR_A_Userplane, External (and Crosslink)
SR_SS7_A/B, SR_OM
-Intercon Crosslink
-LH_A,LH_B Internal
-BSC_Inner Internal

VLAN Member Port Groups
VLAN Name Member Port Groups Comments
SR_Gb, SR_Abis, External (and port group Crosslink is optional
SR_SS7, SR_OM CrossLink) depending on external network
configuration
Intercon CrossLink all ports in port group Crosslink
LH_A, LH_B Internal all ports in port group Internal
BSC_Inner Internal and CrossLink all ports in port group Internal &
Crosslink

Supported configurations

How to connect to NWI-E
• From OSS via winfoil
ssh admin@10.29.10.5 (side A - ip 10.29.10.5/ Side –B ip -10.29.10.6)
Password= password
From other Terminals remotely using telnet protocol.

• O&M IP – 10.29.10.5 or 10.29.19.6
• User – admin
• Password –password
Direct connection on site.

Connect serial RS-232 console with TSR 491 616 cable to the serial management port on NWI-E and Laptop. Use below serial port
settings on your secure CRT or hyper-terminal :
Baud rate: 9600
Data bits: 8
Stop bit: 1
Parity: None
Flow Control: xon/xoff
• User – admin
• Password –password

Use full command on NWI-E
Show configuration
Show vrrp
Show vlan
Show switch
Show ports
Show port info
Show version
Show configuration rtmgr

Evo8200 building
elements

New Boards in EVO8200

New HW units for
Evo Controller 8200
HW Task Redundancy Subrack Node type
EPB The Evo Processing Board is a generic processor N+1 and 1+1 Main and Mandatory for
board used for all processing tasks. Each EPB1 Extension both BSC and
board is equipped with two multi-core processors RNC
with 8 cores per processor.
CMXB Ethernet switching infrastructure with a 200 Gbps 1+1 Main and Mandatory for
Ethernet switch. 10 Gbps Ethernet ports for Extension RNC.
external connections and interfaces for Inter- Mandatory for
Subrack Links for user plane.
all node types
from mid
2013.
SCXB Ethernet switching infrastructure. Manages also 1+1 Main and Mandatory for
system clock distribution, power filtering and Extension all node
distribution, and interfaces for Inter-Subrack Links types.
for control plane.

Exchange Terminal Boards, active patch panel and
cabinet switch
HW Interface Ports Function Node type

CMXB 10 Gbps electrical 8 External connection for 1-4 ports via APP. Mandatory
or reconfigurable Electrical to optical conversion is made in the APP.
to 1 Gbps. HW
prepared for 40
Gbps.
NWI-E Enables IP on the 1 NWI-E is a Layer2/Layer3 Ethernet switching plug in Mandatory for BSC.
BSC external unit for the BSC.
interfaces
EvoET 155 Mbps. 8 The EvoET board is an optional board to handle TDM Optional both for
STM-1/VC4 and transport for A-bis in case of BSC operation or ATM BSC and RNC.
STM-1/VC12 transport for Iub, Iur and Iu-CS in case of RNC
operation.

System Control Switch Board
(SCXB)
• Ethernet Switching and Magazine

controlling
• Connects one EGEM2 with further EGEM2
• Replaces SCB-RP/4 (EGEM)
• NTP Client

SCXB3 Description
• System Control Switch Boards (SCXB3) ROJ 208 395/1
– SCXB is used to carry node internal control signaling and manages system clock
distribution, and connections between EGEM2 subracks for control traffic.
– There are two SCXBs in every subrack belonging to two physically separated LANs.
• Each subrack contains a redundant SCXB pair, in slots 1 and 27
• All device boards and switch boards in a subrack are connected to both SCXBs
through a 1Gbps backplane connection. .
– The MS SCXBs are connected to the ES SCXBs by 10Gbps front panel Control Inter Switch
Links (CISLs) - (slot 1 to slot 1 and slot 27 to slot 27).

SCXB3 and (EPB) LED Indicators

EPB
EPB
EPB
SCXB
SCXB
1G 1G
10G 10G
EPB
EPB
SCXB
EPB
SCXB
1G 1G
10G 10G
EPB
EPB
SCXB
EPB
SCXB
1G 1G

SCXB3 ports
Port Name Function
A-D 10GE
E-G 1GE
H RP bus
I Serial Control P.
J Sync1
K GPS
L RS232/Alarm
M Ethernet/Debug
N Sync2 (coax)

SCXB3 Functions
-Ethernet Bridging
-Shelf Management
-Log Management
-Synchronization
-Performance monitoring
-Port Mirroring
-Rate limiting
-Warm Restart
-Delayed restart
-Link Aggregation
-Ethernet O&M
-NTP Server, Client

Ethernet Bridging
• Layer 1 Switch
• Layer 2 Switch (MAC)
• VLAN
– Protocol based
– Subnet based
• Class of Service
– 0-6 serviced with Weighted Fair Queuing
– 7 queue with Strict Priority (L2 packets)
• Switch Buffer Management
• Ethernet LAN supervision
• Ethernet O&M

Shelf Management
• Shelf management
– Reset and power management
– HW which implemented into magazine
– Fan control
– Fault detection
– Store HW information (Product number etc.)
– Temperature supervision

How to Connect to SCXB
• ssh advanced@192.168.169.56
• Password: ett,30
• su root
• Password = ericsson1
sss66
• ssh advanced@192.168.169.57
• Password: ett,30
• su root
• Password = ericsson1

Network Syncronization
• Synchronization
– clock on all outgoing Ethernet links
– Frequency reference or GPS connection on the front port
• Loss of synchronization source leads to that the clock

(in SCXB3) enters a holdover mode and frequency synchronization towards the
RBSs is affected.
• This may lead to an unsynchronized network with handover problems, if

synchronization source is not restored.
• Synchronization source needs to be restored within ~20 hours, otherwise traffic

will be stopped.

EVO8200 BSC Synchronization
TDM
transmission
RBS
(GPS or
MSC/MGW Symmetricon S 200/300)
RBS
BSC Abis
SDH-net
IP transmission RBS
G.813
SCXB
3
Primary RBS
Synchronization
Source
SDH-MUX
G.813
Component Main Switching Board
(CMXB)
• CMXB: ROJ 208 392/1, Data switch
• Introduced on G13B
• Originally developed for EVO8200/RNC
• Used for connecting EPB and EVO ET
- 960 Gbps Ethernet Switching
- Switching 10Gbit/s Ethernet LAN
- 24 x 10/40G
- Layer 2
- Layer 3 (IP routing)
- Load balancing
- 15 mm
- 1+1 redundancy
- It will replace NWI-E in a later SW revision

CMXB3 build up
• Carries user plane data and node external traffic.
• Each subrack contains a redundant CMXB pair. All CMXB boards are
interconnected in a double star topology with Ethernet Subrack Links (ESL)
• The board has 10 Gbps backplane which reach all (non switch) device boards
within the same subrack
• Also has 8 front panel (1 , 10 or 40 Gbps) ports that can be used to connect
to other CMXBs inside the node or as external ports for outgoing traffic

CMXB-EVO ET Connections

EPB1 board &
Cth concept

EVO Processor Board (EPB1)
• ROJ 208394/1
• Replaces GARP-2
– Used for
• Combined Traffic Handler (CTH)
• GPRS Packet Handler (GPH)
• General Service Handler (GSH)
• Multicore processor – 7 Configurable RPs
– Each RP can be restarted independently
• 1 Gbit/s Ethernet interfaces – backward compatibility
• 10 Gbit/s Ethernet interfaces – future proof
• No Group Switch Interface

EPB1 HW Architecture
CS traffic
LEDs
EPB1 Front connector
Eth – 1G
FLASH
(Boot)
PCIe – 5G
Freescale Eth – 1G Freescale

Disc P4080 P4080
Eth – 1G
PIU-processor Device-processor
8 GB
for EGEM2
DDR3 8GB
Eth -1G
Eth -1G
Eth -1G
(16 bit) DDR3
IP payload (16 bit)
PCIe
PCIe
FPGA
IPMI
XAUI XAUI
2 x 1G Ethernet
2 x 10 G Ethernet
Blade Concept in the EVO8200/
RNC
 Primary processor (PiU)
– Contains four mMP (run MC : Module Controller)
– Contains one CC device (terminating the Iub common channels) and two DC devices
(terminating the Iub, Iu-CS and Iur user planes for dedicated channels).
 Secondary processor (PiuDevice)
– Contains one PDR device (terminating the Iu-PS user plane) and six DC devices
(terminating the Iub, Iu-CS and Iur user planes for dedicated channels).
PiU
Core#0 Core#1 Core#2 Core#3 Core#4 Core#5 Core#6 Core#7
IP
mMP stack ccSP mMP mMP mMP dcSP dcSP
PiuDevice
Core#0 Core#1 Core#2 Core#3 Core#4 Core#5 Core#6 Core#7
IP
pdrSP stack dcSP dcSP dcSP dcSP dcSP dcSP
Blade Concept at EPB1 in gsm
›1 x CTH and GPH blade contains as below:

– 1 x AXE core
– 4 x CTH device
– 3 x GPH device
– Not used
The secondary processor does not work.
EPB1
PP SP
PP = Primary Processor
SP = Secondary processor

EVO8200/BSC EPB (CTH) concept
(from G13B)
• AGW+TRH+PGW => CTH
• Simpler configuration and updates A
Gb
• Improved hardware utilization Lb
• Ethernet infrastructure can be offloaded IP Abis
O&M
BSC
LAN LAN
Switch
Switch
(NWI-E)
Ethernet Ethernet
Ethernet
Ethernet
Switch
Switch
Switch
(SCX)
AGW
AGW TRH
TRH
GPH CTH
APZ APG
APG
Sigtran
APZ (CP) IPN

BSC Regional processors
Evo Controller
HD BSCs 8200/BSC
GARP2 EPB1
CPU CPU
Core Core #1 Core #2
Core #3 Core #4
Core #5 Core #6
Core #7 System
• Each processing board has a one core CPU 7 cores, called Virtual RPs (VRPs), are available per
processing board
• Single application
› Multiple applications

EPB Core concept on G13B
G12B G13B
Static core configuration Static core configuration Dynamic core configuration
The TRH/PGW/AGW EPB1 The GPH EPB1 The EPB1

Core Core Core
TRH GPH CTH

TRH GPH CTH
TRH GPH CTH
PGW GPH CTH
PGW GPH GPH
PGW GPH GPH
AGW GPH GPH
› Each processing board has a one core CPU

› G12B: The cores will have fixed allocated function: GPH, TRH, AGW or PGW.
› G12B: Two EPB1 boards are included in base configuration & shall be used for user traffic
› G13B: CTH is introduced and can dynamically take on TRH, PGW & AGW functionality, GPH on separate cores, but both CTH and GPH cores can share same EPB1

RP Applications Distribution status in example
<raasp;
RP APPLICATION DISTRIBUTION STATUS
DSTATUS (Distribution status)

OPTIMAL
MAXGPH MAXCTH MAXGSH (Maximum number of instances on a PIU)

4 2 0
NOPIU NOPIA NOPIL NOPIE EXCSTAT

7 41 0 8 NO
MAGNO SLOTNO BOARDNAME CFGNO

1 14 EPB1 1
PI APPL RPADDR
1 CTH 1
2 CTH 8
3 GPH 102
4 GPH 109
5 GPH 116
6 GPH 123
7 E
NOPIU: Total number of PIUs (Plug In Unit)

NOPIA: Total number of PIs with BSC applications
NOPIL: Total number of BSC and non-BSC applications in locked PIs
NOPIE: Total number of PIs that are empty
EXCSTAT: Exceed Status

RP SW overview
› 13B: More dynamic way of utilizing the resources.
– CTH
– Auto RP redistribution
GARP2 GARP2 EPB EPB

GPH AGW CTH CTH
CTH GPH
GPH GPH
GS LAN CTH GPH
GARP2 GARP2 LAN

TRH PGW
BSC HD/EvoC8100 Evo Controller 13B

EPB1 Capacity
› In G13B cores can dynamically be allocated in the EPB1, all functionality can be mixed in
same EPB1.
› From G13B CTH will be introduced for PGW/TRH/AGW functionality per processing core:
› In G13B following EPB capacities shall be used in the dimensioning:
EPB1 core Max core Capacity Comment
CTH 256 TRX and 700 Erlang CTH includes PGW, TRH and
AGW functionality
GPH 512 (E)PDCH and 20 Mbps

CTH IP Addressing for standby
CTH RP
• Standby CTH
– One or more CTH RP can be standby. No IP address allocated to these RPs
– In the case of failure of any of the active CTH RPs the IP address and traffic is
moved to a standby RP which becomes active.
– The number of standby CTH RPs are set by RALSC command.
– The number of IP addresses for Abis traffic shall be equal to the number of
CTH RPs minus the number of Standby CTH RPs. If there are more, some IP
addresses will not be used. If there are less, some CTH-RPs will not handle
Packet Abis over IP traffic.

Initial CTH Load balancing
• At TG configuration the Superchannel
groups (SCGRs) are distributed evenly CTH 1
over the CTH-RPs Standby
• When putting TRX in service the Sign
signaling links (DLIs) are placed on the
CTH 2
same CTH-RP as their TG
• When call is set up the RTP session is Sign
set up primarily on the CTH-RP which CTH 3
handles the signaling and Abis parts of
the call
Sign
• As second priority it is set up on CTH-
RP which have the most RTP sessions CTH 4
with the same M-MGW IP endpoint

CTH Load Balancing,
overload handling
• Periodic CTH Load Balancing can be set up to distribute SCGRs at low traffic hours
if high load has occurred on some CTH-RPs at busy hour
– Command: RALBI;
• Move of SCGR is performed with minimal traffic impact
• The corresponding signaling resources are moved with the SCGR
• CTH Load Balancing can also be performed immediate using MML command
– Command: RALII;
• At the same time we can easily check the traffic on the CTHs.
– As there is no more transcoder pool, the solution is RALDP:RP=ALL;
• At overload of one CTH-RP, set up of new RTP sessions are stopped on the CTH-RP
• If CPU load continues to increase, SCGRs are immediately moved to lower loaded
CTH-RP
• As last resort, SCGR are blocked until CPU load is low

Automatic RP Application Distribution and
Redistribution (ADA)
• The feature Automatic RP Application Distribution and Redistribution (ADA)
function enables the application to control where a Virtual Regional Processor (VRP)
shall execute. It means automatically distribute VRPs on cores of EPB1. VRP address
have no relationship with physical PIU.
• Three type of applications: Combined Traffic Handler (CTH), GPRS Packet Handler
(GPH) and General Service Handler (GSH) can be used by the ADA mechanism.
– GSH is introduced on G13B for the feature BTS Soft Sync and it is used for CP off load
• ADA performs distribution and redistribution of RP instances each time an RP is

configured and deblocked for the first time, when new PIUs are added to the
system and when a PIU is taken out of service.

• Redistribution can be performed immediate
– using command RAAII;
or it can be set to be performed at low traffic hours in order to minimize traffic
impact.
-using command RAAPI;
• The ADA user can order that an RP is moved from one RP location to a free RP
location or that the locations of two RPs are swapped.
• The RPS may ask the ADA user at unblocking of RP in which RP location the RP
shall execute.
Deblock Distribution
Deblock distribution is performed the first time an RP instance is configured. Compared
to PIUs with one RP instance per board the operator does not need to specify which RP
hardware the RP instance shall be placed. For PIUs with several RP instances per board
this is handled by ADA function. At unblock ADA will find a suitable PIU and PI
automatically.

VRP Redistribution
A redistribution of RP instances is performed as a series of swaps and/or moves. Each
swap will block two RP instances of different application and on different PIUs for
about 30 seconds. A move is when a configured RP instance is moved to a empty PI.
Each move will block one RP instance for about 30 seconds.
When each move or swap is finished the affected RP instances will be taken into
service automatically and start handling traffic again. The RP instances will keep the
configured RP addresses and software units, only now running on another PIUs.

EVO ET Board &
Packet abis over TDM

EVO ET Board
• ROJ 208 467/1
• Available on G13B
• Replaces ET155-1
• Used for Packet Abis over TDM
• Provides 8 STM-1/OC-3 ports
• No Group Switch interface
– Uses 10 Gbit/s Ethernet for
communication with CTH
• 1+1 redundancy
- 1- 8 port could be activated per board (HWAC)
Note: Evo Controller 8200/BSC only support IP transport
to core network
=> TRC will not be included in Evo Controller 8200

EVO ET Concept
A
Gb
Lb
Abis Abis
IP
O&M
TDM network
BSC
LAN LAN
Switch
Switch
(NWI-E)
Ethernet Ethernet
Ethernet
Ethernet
Switch
Switch
Switch
TRH (SCX)
TRH
TRH TRH
EvoET TRH
EPB TRH
10 Gbit/s
Eth Swich
(CMX)
APZ APG
APG
Sigtran
APZ (CP)

EVO ET Technical Background
• EvoBSC 8200 only supports IP interfaces in G12B release.
However for Abis the migration to IP may be seen as too costly, or planned for a
later point in time and hence the Evo 8200/BSC cannot be used.
• Each EvoET provides 8 STM-1

– old ET-155-1 board supports one STM-1 port
– operator gets a whole board, but maybe the whole capacity is not required,
therefore HWAC are needed to activate required no of ports.
• Support of only “Packet Abis over TDM” requires a new EvoET board in EvoC
8200.
The EvoET board terminates TDM towards Abis but use Ethernet internally
towards PGW (EPB1) boards.
• The Hardware Activation Codes define capacity limits (ports) and depend on the
commercial agreements.
• Communication EvoET – PGW requires 10Gbit/s Ethernet Communication which is
supported by CMX boards (CMXB3).
EVO ET HW Layout Limitations
According to the latest HW Configuration Data for EVO8200 BSC, the subrack can not
hold more than six EVO ETs, because of the heating problems
EvoET boards are only allowed to be placed in certain slots of the EGEM2 magazine.
For Main subrack , EvoET boards may be placed in slot 3 for active board and slot 15 for
protection board. Slots 14 to 17 may be used by an optional external media. Then no
EvoET boards must be installed in Main subrack.
It is recommended to run always with both active and protection EvoET boards.
For Extension subrack, EvoET boards may be placed in slots 9 and 7 for active boards
and slots 21 and 19 for protection boards, respectively in pairs slot 9 with slot 21 and
slot 7 with slot 19.
A separate license control is required. A license for the first STM-1/OC-3 port is
included in the HW, but new licenses are required for each additional port (FAK 101
0016).

Packet Abis over TDM
Packet Abis over TDM for EvoC 8200/BSC is based on the old
feature Abis Optimization.
Super Channels are used.
ET-155 board has been replaced by EvoET board.
No GS is required.
Hardware activation code is introduced.

– HWAC are granted via electronic license keys
– Existing Capacity Lock framework in BSC reused
– Alarm raised if HWAC lower than number of used ports
Number of ports are checked at command TPCOI

– At SDIP connection a check towards available number of HWACs is performed.
– Each connected port requires one HWAC, ports on both working and
protecting EvoET board are counted.

Abis Optimization in a Legacy
BSC
AGW
ET155
GPH PGW FPGA GS AUG
ET155
DL34
TRH
Interface
STM-1/OC-3
155 Mbit

New Solution (Packet Abis over TDM) in
EVO8200 BSC E
t
h
e
r
n
e
t Evo-ET
GPH
C AUG
CTH
o
m
m
u
n Evo-ET
i
c
a
t STM-1/OC-3
i 155 Mbit
o
CTH = Combined Traffic Handler n
AGW+TRH+PGW
Abis Optimization

Packet Abis over TDM technical
details
Packet Abis over TDM a feature to achieve bandwidth savings on the Abis interface.
Bandwidth savings are achieved by removal of redundant information and packing of
frames in both uplink and downlink.
Bandwidth savings are also accomplished by introducing the super channel concept. A
super channel is one E1 or one T1 link, or a fraction of one E1 or one T1, where 64
Kbit/s consecutive Abis timeslots can be used as a wideband connection for sending
signaling and payload as LAPD frames between BSC and BTS. As all traffic and signaling
share the same wideband connection, statistical multiplexing gains are achieved.
The bandwidth usage optimization is achieved by, for example, removal of TRAU
frames during silence speech periods and removal of spare bits in CS and PS frames.

It is possible to have from one to up to four E1 links between the BTS and the BSC.
Each E1 link is a super channel, and as mentioned all super channels from one TG are
named as a Super Channel Group (SCGR) There is up to four Super Channel can be
gathered together as one Super Channel Group.
•The BSS solution for Packet Abis over TDM based on that traffic and signaling on the
Abis interface are sent as LAPD frames on super channels instead of using dedicated
timeslots. As normal E1/T1 links are used, synchronization of the radio base stations is
kept.

•In the uplink direction, the TRX handles removal of redundant information in order to
save bandwidth. Each "compressed" traffic frame is sent as one LAPD frame to the
DXU every 20 ms. The DXU is configured so that a number of TRXs are dedicated to a
specific Abis link or part of an Abis link (super channel). In the downlink direction, jitter
buffers exists in each TRX due to that frames sent from the BSC are sent in series and
can arrive in the TRX at different times depending on the load on the super channel

Abis Load Regulations -
• Functionality to reduce the Abis load
– The PGW measures the Abis load per super channel. When the transmission
load to a super channel has increased above one of three operator specified
thresholds, the following high load measures are applied:
• Allocate half rate speech calls by triggering the feature “Abis triggered HR
Allocation”.
• Move full rate speech calls to half rate by triggering the feature “Abis
triggered HR Allocation”.
• Trigger the feature “Fullrate AMR on 8 kbps Abis“. This feature allocates
full rate AMR calls with codecs restricted to a maximum of 7.4 kbps.

Packet Abis over TDM rules
• Traffic Priorities
– Signaling will be prioritized at Abis overload
– Speech will be prioritized over GPRS/EGPRS
– PS-scheduling is gradually decreased during overload scenarios to reduce the

super channel load.
– At continuous overload, new connections will be rejected for the specific TG

to maintain speech quality

Super Channel (SC)
The Abis interface has always had a number of features to reduce its traffic load. With
the adventure of the Packet Abis over TDM feature, the concept of 64 kbps time slots
in the E1 links is not valid anymore. Both PGW and BTS see the E1 link as a wide band
connection of 2 Mbps where the LAPD is sent in compressed LAPD packets. These
nodes only transfer bit that really contain information, so redundant bits are no longer
inserted. Other bits used to maintain the constant bit rate on the PDH channel are no
longer inserted as well.
One Super Channel is 1-31 consecutive time slots

Abis Traffic on Super Channel
LAPD header and footer P-GSL
TFP Header (E)GPRS
Circuit switched traffic Signalling
E1
ts0 n*64 kbps packet bandwidth to

frame several TRXs
sync
if req.
Super Channel Dimensioning (1)
• If one E1 link is enough for today’s traffic using classic TDM it will also be sufficient
now due to bandwidth savings when using super channels.
• Define super Channel as 31 TS.
• Unused bandwidth can be used for growing EDGE traffic without reconfiguring the
SCs.
– Extend number of EGPRS channels
– Extend number of TRXs
• Special considerations must be taken if an E1 is shared between different TGs.

Super Channel Dimensioning (2)
• One RBS with 12 TRX’s, configured as one TG
• 3 sector site with 4 TRXs in each sector
• 4 Erlang/TRX and 10 kbps PS per Erlang CS
– Approx 23 TS required
4 TRX
One super channel
4 TRX 4 TRX
One E1 is enough, grooming in transport

network gives additional benefit for E1

• If there is a 3x4 configuration (TRX-0-3=cellA ,TRX-4-7=cellB ,TRX-8-11=cellC) and
the allocation is TRX-0-11 to SC=0 then all traffic for all cells (signaling and user
data) will go via a single E1 (SC0).
•
• Or there is 3x4 (TRX-0-3=cellA ,TRX-4-7=cellB ,TRX-8-11=cellC) configuration and
allocate let`s say:
• TRX-0-2 to SC0
• TRX-3-5 to SC1
• TRX-6-8 to SC2
• TRX-9-11 to SC3
• then 4E1 link is needed and every E1 will handle the corresponding TRXs signaling
and user data also. Meaning:
• TRX-0-3=cellA ==> carried by SC0 and SC1
• TRX-4-7=cellB ==> carried by SC1 and SC2
• TRX-8-11=cellC ==> carried by SC2 and SC3
•
• In case of a big site/cell, let`s say 1 cell with 12 TRX, you could also use 4E1s ==>
means 4E1 and then 3-3-3-3TRXes will be handled by 1-1-1-1E1/SC.

Packet Abis over TDM configuration rules
• A TG can be configured in transmission mode:
– TDM, Abis interface is structured into 64 kbps circuits. Each LAPD link and
speech/data channel uses a single 64 kbps circuit or subrate physical channel for
transferring data. (GS is used).
– SCM, several LAPD links and speech/data channels share an SC for transferring data.
• Transmission mode SCM

– Two concepts are used:
• SC: Super Channel
• SCGR: Super Channel Group.
– SC is a set of contiguous 64 kbps timeslots (1-31) that are used as one wideband
channel.
– A set of one up to four SCs constitutes an SCGR.
Both “Packet Abis over TDM” and “Packet Abis over IP” can coexist in the same Evo
Controller 8200/BSC node.

Define SCGR for Abis interface
–Use command RRSGI.
–MODE = SCM
Define SC within the SCGR
–Use command RRSCI.
–DEV1 = ETM4-xx
–NUMDEV = 1 - 31
Define the TG MO and its subordinate MOs
–Use command RXMOI.
–TG Transmission mode is set to SCM.
–SCGR is connected to TG.
–Each subordinate TRXC MO should be connected to the specific SC
Change Abis Path Thresholds Values - TG in SCM Mode

–Use command RXATC.
•Connect and Deblock Digital Path to DP MO

–Use command DTDII/DTBLE.
•Bring the TG MO and its subordinate MOs into service.

–Use command RXESI.

Hardware activition
Codes (hwac)

Hardware Activation codes
(HWAC)
› GSM unique
BSC Data Capacity › HWAC specified in steps of 1 EDGE
channel or 2*GPRS channels
› GSM unique
BSC TRX Capacity › HWAC specified in steps of one TRX
EvoET BSC port › Sold in steps of 1

› HWAC specified in steps of one EvoET port

HWAC Operator values
REMOTE
• No site visit. Remote activation.
Ai76xYj8i7R2
d2ka8w2klq8
9KY8KA82W0 • Activated via HW Activation Codes
 OPEX savings for operator
FLEXIBLE Pay as You Grow, instead of investing in

Capacity Capacity unused capacity
• Invest only when capacity is really needed
Flexible
Unused upgrades
capacity
Demand Demand •  CAPEX savings for operator
Time Time
INSTANT  Instant Capacitiy ExpansionCAP

Reduce lead time , no downtime during the
expansion
Reduce time to market
– BSC Capacity Lock framework in used
– Move of HW activation codes is not possible between BSCs. However it is

possible within the same BSC. Move of licenses is possible but requires a
manual process
– BSC Capacity Lock Exceeded - this alarm is raised due to two possible reasons:
– Attempt to use capacity lock resources above provided limit.
– Provided capacity lock maximum volume has been changed and current use
of capacity lock resources exceeds the new provided capacity lock limit.
– The alarm is ceased automatically when the current use of capacity lock
resources decreases below or equal to the provided capacity limit. Manual
ceasing is required when alarm is raised due to the attempt to use capacity
lock resources above provided limit.

Hardware Activation Codes (HWAC) for
EVO ET Board
• HW activation code for number of EvoET ports in BSC
– HWAC are granted via electronic license keys
– Existing Capacity Lock framework in BSC reused
– Alarm raised if HWAC lower than number of used ports
• Number of ports are checked at command TPCOI

– At SDIP connection a check towards available number of HWACs is performed.
– Each connected port requires one HWAC, ports on both working and
protecting EvoET board are counted.

Hardware Activation Codes in the
BSCs at G13B

EVO8200 BSC
Dimensioning

Miscellaneous BSC information
• A BSC needs to run the following applications:
– TRH
– PGW
– AGW
– GPH
– ET boards are added as TDM transmission interfaces
• Evo 8200 BSC uses EPB1 (EVO Processing Board v1) for the applications and EVO-ET boards
for TDM
• In an Evo 8200/BSC, 7 processing cores on EPB1 can be utilized
• Each core can run one or more applications and has a same capacity of a legacy GARP2 board
• In G12B
– The same applications as in HD BSC will be used, i.e. AGW, PGW, TRH, and GPH in a fixed
configuration (“331”), see next slide. (TRA n/a)
– NOTE! In 12B & 13A, two EPB1 is included in base configuration by default.
• In G13B
– CTH core is introduced, this means that one core can take on the functionality of TRH,
PGW & AGW at the same time dynamically.
EPB1, CTH versus the “old”
331 model
Generic view In 12B & 13A In 13B
EPB “Blade” “331” fixed config.
2nd processor not used 2nd processor not used 2nd processor not used
Core
Primary processor Core
Primary processor Core
Primary processor
CPP Core CPP Core CPP Core
Core Core TRH Core CTH Core
Core Core PGW Core CTH Core
Core Core PGW Core CTH Core
Core Core PGW Core GPH Core
Core AGW GPH
Remember:
In 12B & 13A the cores will have fixed allocated function: GPH, TRH, AGW or PGW.
In 12B & 13A two EPB1 configurations, “331” with 3 x TRH, 3 x PGW & 1 x AGW or all 7 cores as GPH
In 12B & 13A two EPB1 boards is included in base configuration & shall be used for user traffic
In 13B CTH is introduced and can dynamically take on TRH, PGW & AGW functionality, GPH on separate cores.

Dimensioning limit in G13B
• There are only two different RPs available for the Evo8200 BSC and those are
CTHs and GPHs. Each core in the EPB1 board can be statically configured as CTH or
GPH
• The amount of total cores per EPB is 7, any combination of CTH and GPH are
applicable in the EPB
• The CTH is a combination of AGW, TRH and PGW into one unit.

Dimensioning
• 2 different methods to perform dimensioning:
– Using CMEX tool
• detailed dimensioning which takes into account all details around
processor load for all processors
• Requires high amount of information to be retrieved form the network
– Basic dimensioning
• takes into account system limits and verified system capacity in live
networks
• HW capacity is reduced to cater for processor load on GPH
• additional checks are performed to evaluate if processor load on GPH could
still be a limiting factor, in this case CMEX should be used instead

Evo BSC 8200 – initial
Dimensioning
Results Scenario 1 Scenario 2

Number of BSC 3 2
Hardware Needed per BSC
Number of EPB's (N+1 redundancy) 10 11
Number of EVO-ET's (1+1 redundancy) 6 6
Data Capacity HWAC 10104 10208
TRX Capacity HWAC 3772 4095
No. of extension sub racks needed 1 1
No. of Gb TS 1941 2912
No. of SCC needed 4797 7150
Assumes Min SW G13B

More EBPs required on G12B
CTH Capacity on G13B
• Each CTH core can simultaneously handle:
– Up to 1200 Erlangs
– Up to 256 TRX
– Processor load is evaluated separately and amount of cores due to processor
load is also estimated
• The limiting requirement will define the number of required CTH cores

GPH Capacity on G13B
• Each GPH core can simultaneously handle:
– Up to theoretically 20 Mbps (UL + DL peak throughput), recommended values
to be used for dimensioning in order to cater for processor load are:
• 8 Mbps in FTP traffic
• 4 Mbps in BAS3 model (mixed smartphone and MBB)
• 3.5 Mbps in smartphone centric networks to cater for processor load
– Max 512 PDCH or 384 EPDCH (with packet A-bis over TDM/IP)
• 384 EPDCH to be considered to cater for processor load on GPH
• The limiting requirement will define the number of required GPH cores
• Additional processor load check:

– if the average throughput (during BH) per PDCH is higher than 9-10 kbps then extra GPH
might be required (recommended to dimension with CMEX)

Information received from customer
• Number of cells
• Number of TRX
– considering a safe margin of 5% increase
• Number of PDCH
– Considering a safe margin of 10% increase
• Number of EPDCH
– Considering a safe margin increase of 10%, an increase due to the modernization
and a reduction due to the introduction of the feature packet data efficiency (-20%)
• Gb Throughput
– peak throughput possible given amount of PDCH and EPDCH
• Erlangs

EVO8200 BSC
Integration
Experiences

EVO8200 BSC Configuration Experiences
• Check if Evo 8200/BSC

– RRGCP;
RADIO TRANSMISSION GS CONNECTION DATA
GSCONN APPL
NOTALLOWED AGW
TRH
PGW
GPH
• Each of the 7 RPs on EPB1 are configured in the same way as legacy RPs
…but much simpler…
– No Group Switch
• This means no:
– GMHWI, GMHWP, GDCOI, GDTEI, GDBLE, …

Configuration Experiences (cont.)
– No Switching Network Terminals (SNTs)

• This means no:
– NTCOI, NTCOP, NTTEI, NTIDP, NTIDC, NTBLE, NTSIP…
–No Devices
• This means no:
– EXDUI, EXDUP, EXDAI, BLODE, …
–and no TRA, ET155-1, Signaling Terminal…
–No changes compared to legacy BSC when configuring RBSs, TRXs, cells, PDCHs,
radio network functionality, core network connections, etc…
–OSS-RC support is the same as for legacy BSC

Integrating onto the OSS
•OSS O14.1
– EvoC 8200/BSC can be modeled ad BSC or BSC/TRC
– GS Connection Mode is displayed in OSS Explorer and BSM
– Classic Abis TGs are prohibited by BSM Wizard
– CTH support is introduced in ICS
•Sigtran on CP
– Configuration changes compared to Sigtran on RP (different set of commands)
– No front cables
•SCXB and EPB1
– Hardware is configured using APG commands
– SCXB software and EPB1 firmware are loaded from APG
– The EPB1 RPs are configured in the same way as the legacy RPs

SIGTRAN, Syncing
• Sigtran does not require RP hardware in Evo8200
– Same Sigtran implementations as in MSC is used
– No front cables needed
– Sigtran on CP is supported on Evo8200
– Only small changes in configuration compared to Sigtran on RP
• Synching of BSC clock with NTP does not require RP hardware in Evo8200
– In Evo8200 the NTP client is placed on SCX and the current time is fetched by
the CP using a SNTP (Simple NTP) protocol
Let we see a specific example:

• Create a Virtual Interface (IHVFI):
• IHIFP:VIF=ALL;
• VIRTUAL ETHERNET INTERFACE DATA
• VIF DID STATE MTU HWADDRESS

• ETHA-51 2 UP 1500 3C-19-7D-0F-91-70
IP NETMASK ARP
• 192.168.88.242 255.255.255.240 YES
• VIF DID STATE MTU HWADDRESS

• ETHB-51 3 UP 1500 3C-19-7D-0F-91-71
IP NETMASK ARP
• 192.168.88.250 255.255.255.240 YES
• Create the C7 Signaling points for every connecting MSC- Servers (C7SPI):
•
• C7SPP:SP=ALL;
• CCITT7 SIGNALLING POINT DATA
• SP SPID NET PREF MODE

• 2-11493 OWNSP BSC184
• 2-11336 BUE1K IP NOACT
• 2-11478 CRR3K IP NOACT
• 2-11550 SMPC IP NOACT

Create SCTP Association Points for every routes, to every MSC Servers, and associate
them to the virtual interface, created above (M3RSI):
IHCLP:EPID=BSC184,SAID=ALL;
SCTP ASSOCIATION CONNECTION LIST DATA
EPID LPN USER MODE

BSC184 2905 M3UA CLIENT
LIP
192.168.88.242
192.168.88.250
SAID SASTATE RPN OS

CRR3K_1 ASSOCESTABL 2905 17
RIP
138.188.87.250
138.188.62.250
SAID SASTATE RPN OS

CRR3K_2 ASSOCESTABL 2905 17
RIP
138.188.87.251
138.188.62.251
SAID SASTATE RPN OS

BUE1K ASSOCESTABL 2905 17
RIP
138.188.87.220
138.188.62.220

Activate the SCTP Associations (M3ASC, and M3RAI). Only applicable, after it is done at the
MSC S side. The co operation with the Core team, as well as the customer’s IP backbone
team is mandatory, during the SIGTRAN integration phase.
M3RSP:DEST=ALL;
M3UA ROUTING DATA
DEST SPID DST LSHM
2-11336 BUE1K AVA PP
SAID PRIO RST CW CWU

BUE1K 1 EN-ACT-AVA
2-11478 CRR3K AVA PP
SAID PRIO RST CW CWU

CRR3K_1 1 EN-ACT-AVA
CRR3K_2 2 EN-ACT-AVA
C7NCP:SSN=ALL,SP=ALL;
CCITT7 SCCP NETWORK CONFIGURATION DATA
SP SPID SPSTATE BROADCASTSTATUS SCCPSTATE
2-11336 BUE1K ALLOWED NCON ALLOWED
SSN SUBSYSTEMSTATE SST
254 ALLOWED YES
SP SPID SPSTATE BROADCASTSTATUS SCCPSTATE

2-11478 CRR3K ALLOWED NCON ALLOWED
SSN SUBSYSTEMSTATE SST
254 ALLOWED YES

Network Sync settings on BSC184
•
• ncdap;
• NETWORK CLOCK-REFERENCE DATA
•
• CLKREF PRI REFGRP FDL ACL STATE FCODE
• EXT-2 1 1 1000 A2 WO/EX
• EXT-3 2 1 1000 A2 WO
•
• DYNAMIC DATA
•
• SCX CLKMODE CURFCV AVGFCV
• SCX-A LOCKED 33727 33727
• SCX-B LOCKRTL 33789 33789
•
• CLKREF DFREQ ERATE RFD INFO
• EXT-2 2048 0 0
• EXT-3 2048 0 0
• END


Evob200 BSC: Ran Modernization Project

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Evob200 BSC: Ran Modernization Project

Uploaded by

Copyright:

Available Formats

EVOb200 BSC

RAN MODERNIZATION Project

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 2

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 3

BYB501 BYB501 BYB501 BYB501

1991 1995 2000 2008 2012

• SIGTRAN only on RP, GARP-2 boards, EGEM magazines

Evo Controller 8100

Evo Controller 8200

• Built on EPB, EVO ET

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 6

Sigtran on RP (GARP- Sigtran on RP (GARP-2) or

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 7

Active Patch Panel

Support from G10B Support from W11B & G12B

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 9

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 10

› Evo Controller 8200 – 256-4096 TRX

11200 Erlang and 36 Mbps data is supported

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 11

• Two Power and Fan Modules (PFMs) are

Power Feeding is also redundant

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 12

Unit Max power No. of power Circuit breaker PDU type

Node size (No. of Max. Power [W] Typical [W]

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 14

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 15

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 16

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 17

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 18

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 19

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 20

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 21

APG43 and APG43/2

APG43 on Linux (APG43/3)

Componenet Based Application

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 23

• Centralized User Management

• Improved usability, security and robustness

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 24

150 ONLY APPLICATION

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 25

Realization of framework Java

Specification of behavior and Virtualization

design rules HW System

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 26

› Managed Object (MO) classes are organized in a tree hierarchy

› An MO represents an physical/logical resource

› Unified E/// O&M.

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 28

› Only a portion of data disk is exposed and made accessible

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 29

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 30

SystemAdministrator Full access No Access Full access No access No Almost all

Read-only Read-only Only listing

EricssonSupport No access No access Only /tools No access No Only gmlog

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 31

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 32

2.Serial console connection

**Ensure to disable Symantec Endpoint Protect on your PC by changing to out of ericsson

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 33

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 34

EVO8200 BSC | Commercial in confidence | © Ericsson AB 2015 | 2015-06-29 | Page 35