Packet Abis and A Over IP: Soc Classification Level 1 © Nokia Siemens Networks Presentation / Author / Date

Packet Abis and A over IP
Overview
Soc Classification level

1 © Nokia Siemens Networks Presentation / Author / Date
All IP/ Ethernet in NSN 2G Radio Access elements
Entire NSN GSM interfaces supporting IP/ ETH
Before BSS13 RG10 RG20

(CESoPSN) (CESoPSN) Packet Abis
A over IP

Dynamic Abis today
TDM offers less flexibility
• Each voice channel is allocated to a dedicated air interface channel
• Each timeslot is allocated for dedicated traffic
• PWE maps timeslot transparently on Ethernet  no bandwidth optimization
• Fix allocation of bandwidth – pooling is done for PS data only
• Less flexibility to react on data peaks
Legacy TDM PWE CESoPSN

Packet Abis pools all traffic types
• TDM: All timeslots/E1 are pooled  single “bit-pipe”

– Similar to Ethernet media
– CS, PS, signaling and management traffic shares the same bandwidth
• No dedicated bandwidth reserved
• No empty packets are sent (Unused, silence …)

Packet Abis and AoIP Features
• BSS15/RG20 Features
– BSS21440 Packet Abis over TDM (MLPPP)
– BSS21454 Packet Abis over IP/Ethernet
– BSS21444 Packet Abis Security
– BSS21438 Packet Abis over Satellite
– BSS21439 Packet Abis Synchronization ToP IEEE 1588v2
– BSS30450 Packet Abis Synchronous Ethernet
– BSS21443 Packet TRS for UltraSite / BTSplus (requires ETIP and PW)
– BSS21445 Packet Abis Congestion Reaction
– BSS21341 A over IP
– BSS30395 Packet Abis Delay Measurement

BSC3i Block Diagram (S15)
Abis Ater
ET or A
STMU ET TCSM3i or
Abis over IP TCSM2
(PWE) ETIP
Ater (PWE) A
Bit ETIP
Packet Abis based TCSM3i
over TDM STMU ETP TDM
Packet Abis switch
over Ethernet ETP ET or Ater in MGW
STMU Gb over FR
LAN
switch for ETP-A A over IP
ETPLAN (transcoding in MGW)
CLS
Gb
over IP PCU
LAN
switch for Q3, CBC (X.25)
PCULAN BCSU MCMU OMU
…
EMB LAN switch HD MO drive
Ethernet
TDM
LAN switch for CPULAN

Lb, BSC-BSC, A (SIGTRAN)
6 © Nokia Siemens Networks Presentation / Author / Date Q3, CBC (LAN)
Packet Abis and AoIP, combined scenarios
ETPA Eth AoIP (FI) U-plane
Compressed codecs
MGW
PAbis oEth BSC Nb
Eth ETPE TCSM
ETPC Eth AoIP (PI) U-plane
G G.711/CS Data
PAbis oTDM Ater
S
TDM ETPT TDM TDM
W
B
TDM AoTDM (PT)
Legacy Abis G.711/CS
TDM
Data
Mc
AoIP C-plane MSS
• Plug-in units
– ETP Exchange Terminal for Packet Transport
– ETP-A Exchange Terminal for Packet Transport over A-interface
• Functional units
– ETPT, Exchange Terminal for Packet over TDM
– ETPE, Exchange Terminal for Packet over Ethernet
– ETPA, Exchange Terminal for Packet A-interface
– ETPC, Exchange Terminal for Packet A-interface in Transcoder

Network SLA considerations for Abis PSN
The SLA parameters have the following recommended and maximum

values
– Recommended means the performance is almost the same as traditional
TDM
– Maximum means the system is operational but gives the KPIs that are
normally not acceptable

RG20
Packet Abis Synchronization Options for BTS -
overview
•Synchronization to
– T1/E1 Interface
– GPS clock source (NSN LMUB)
– 2MHz source
– Adaptive Clock Recovery
– ToP IEEE1588-2008 (FIQB, FIYB only)
GPS
– Synchronous Ethernet (FIQB, FIYB only)
GPS
1588
Server
FlexiEDGE
CESoPSN PW
BSC
Eth Packet Switched Network Eth
T1/E1/2 MHz

Dynamic Abis BSC
TCSM2i,
BTS ET TDMAter
ET TCSM3i
or MGW
Sn+pair Sn+pair
GSWB
ETP Sn+pair
E1 SET A over IP
/T Packet Abis ETPT
IP-BTS over TDM SB ETP-A TC in BSS
ETS2
1
(STM-1/OC-3) Sn+pair MUX ETPC GigE
MGW
SET
ETP
STMU ETPT
TR3s
Packet Abis
over Ethernet
TCSM3i
Sn+pair
GigE ETP
IP-BTS Packet- TDM A over IP
Packet- Sn+pair
switched ETPE
switched Ater TC in BSS
network
network ET ETP-A
MGW
ETPC GigE
*) PCU2-E uses PCU2-D TCSM3i

internal LAN for ETP
connectivity.
PCU2-E *)
Sn+pair
A over IP
BCSUs
ETP-A TC in MGW
m/c plane ESB24s
ETPA
MGW
to ETPs GigE

ETP/ETP-A Connectivity with Different BSC/TCSM
Configurations
General
• ETP is available for Flexi BSC and BSC3i 1000/2000
• Packet Abis over IP/Ethernet
• Packet Abis over TDM (requires additionally new version of ETS2 E4A)
• ETP-A is available for TCSM3i, Flexi BSC and BSC3i 1000/2000
BSC
• BSC3i 1000 (one cabinet), upgraded BSC3i 1000 (to Flexi BSC, one cabinet) and upgraded BSC3i 660 (to
BSC3i 1000 or Flexi BSC, one cabinet) maximum number of cards/connections:
• 2+2 ETP, 2 ETP-A
– This is equivalent to 16,000 Erlangs (2 x 8000 ch Packet Abis and A over IP)
– If ETP-A in TCSM3i, no A over IP limitation
• BSC3i 2000 (two cabinets) and upgraded BSC3i 660 (to BSC3i 2000 with two cabinets or Flexi BSC with
two cabinets) and Flexi BSC maximum number of cards/connections:
• 6+6 ETP, 4 ETP-A
– This is equivalent to max. 32,000 Erlangs (4 x 8000 ch A over IP, Packet Abis non limiting, Flexi BSC capacity
25,200 Erl)
– If ETP-A in TCSM3i, no A over IP limitation
Transcoder
• TCSM3i (RG20) maximum number of cards/connections per cabinet:
• 5+5 ETP-A
– This is equivalent to max. 19200 Erlangs (5 x 3840 ch A over IP)
• TCSM3i (RG10 or older) maximum number of cards/connections per cabinet:
• 3+3 ETP-A
– This is equivalent to max. 11520 Erlangs (3 x 3840 ch A over IP)

New delivery FlexiBSC, maximum ETPT, ETPE and
ETPA amounts 1 . Pack e t Abis o ve r T DM & ET P- Af o r A ( 6+ 6 ET PT ,4 ETP- A & 3 +3 ET S2a s ma te of ETPTs )
2000 x 900 x 600 cabinet

GTI C 0 o r G T IC 1 ET C0o r ET C2 ET C1 o r ETC3
S B1 -0 SB1 -0 S B1- 0 S B1 -0 SB 1-0 S B1 -0 S B1 -0 SB 1- 0 B1

S S B2 S B2 SB 2 SB2 SB 2 SB2
SB2
SB1
SB 2
SB1 SB
1 SB1 SB1 SB1 SB1
S B1 -0 S B 1-0 SB 1- 0
1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1
S B1 -1 SB1 -1 S B1- 1 S B1 -1 SB 1- S B1 -1 S B1 -1 SB 1- 1 S B1 -1 S B 1- SB 1- 1
0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
S B2 -0 SB2 -0 S B2- 0 S B2 -0 SB 2-0 S B2 -0 S B2 -0 SB 2- 0 S B2 -0 S B 2-0 SB 2- 0
2 1
SW256B 0
SW256B 1
SW256B 2
SW256B 3
SW256B 4
SW256B 5
SW256B 6
SW256B 7
2 1 2 1 2 1 2 1 2 1 2 1 2 1
S B2 -1 SB2 -1 S B2- 1 S B2 -1 SB 2-1 S B2 -1 S B2 -1 SB 2- 1 S B2 -1 S B 2-1 SB 2- 1
I 4T
SHI M 4 T
SHI M 4 T
SH IM 4 T
SH IM 4T
SH IM 4T
1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
SH M
O PR
O PR OP R O PR OPR OP R O PR O PR OP R O PR O PR ETH SB3 ETH S B3 ETH S B3 ETH S B3 ETH SB 3 ETH SB3 ETH S B3 E T
E T H
H SB3
SHI
T x/R x T x/R T x/R x
F AIL F AIL F AIL
S B3 -0 SB3 -0 S B3- 0 S B3 -0 SB 3-0 S B3 -0 S B3 -0 SB 3- 0 ST -1M /OCT -3x S TM- 1/O C-3 S TM -1/ OC -3
Tx T x
0M 0M 0M R U N R U N RU N R U N RU N R U N RU N RU N
R x Rx R x
ST M-1 /OC -3 S TM- 1/O -3C S TM -1/ CO -3
T x Tx T x
C L 3 TG
S B3 -1 SB3 -1 S B3- 1 S B3 -1 SB 3-1 S B3 -1 S B3 -1 SB 3- 1 0 0 0
R R R
R x Rx R x
ST M-1 OC/ -3
T x S TM- 1/O C-3Tx S TM -1/ OCT -3x
S B4 -0 SB4 -0 S B4- 0 S B4 -0 SB 4-0 S B4 -0 S B4 -0 SB 4- 0
1M 1M 1M
R x Rx R x
ST M-1 OC/ -3 S TM- 1/O -3C S TM -1/ CO -3
S B4 -1 SB4 -1 S B4- 1 S B4 -1 SB 4-1 S B4 -1 S B4 -1 SB 4- 1 1T x Tx1 1T x
R R R S E R1 S ER 1 SE R 1 SE R 1 SE R 1 SE R 1 SE R 1 SE R 1
R x Rx R x
E TPT E TPT ET PT ET PT E TPT ET PT E T P- A ET P- A

ET S2 E TS2 ET S2
17
PDFU 0 PDFU 1
PDFU-B PDFU-B
CLS 0
GSW2KB GTIC ETC ETC
0 0 0 1
SGC1C-A
GSW2KB GTIC ETC ETC

CLS 1
1 1 2 3
SGC1C-A
FTRB 2 FTRB 3
1 .Packe t Ab is o ver ET H an d E TP- Afo r A plus Dy namicA bis /Ate r
GT IC0 or GTIC 1 ETC 0o r ETC2 ET C1 or ET C3
SB1 -0 S B1- 0 S B1 -0 S B1- 0 S B1 -0 SB 1- 0 S B1 -0 SB1 -0 SB1 SB 2 SB 2 SB2 SB 2 SB 2 SB 2

S B2
SB1
SB 2
SB1 SB1 SB1 SB1 SB1 SB1
S B 1-0 SB 1 -0 SB 1 -0 S B 1-0
1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1
SB1 -1 S B1- 1 S B1 -1 S B1- 1 S B1 -1 SB 1- 1 S B1 -1 SB1 -1
S B 1- SB 1 -1 SB 1 -1 S B 1-
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
SB2 -0 S B2- 0 S B2 -0 S B2- 0 S B2 -0 SB 2- 0 S B2 -0 SB2 -0 S B 2-0 SB 2 -0 SB 2 -0 S B 2-0

B0
B1
B2
B3
B4
B5
B7
2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1
B
SW25 6
SW25 6
SW25 6
SW25 6
SW25 6
SW25 6
SW25 6
SW25 6
S B 2-1 SB 2 -1 SB 2 -1 S B 2-1
SB2 -1 S B2- 1 S B2 -1 S B2- 1 S B2 -1 SB 2- 1 S B2 -1 SB2 -1
SHI M 4 T
S HI M 4 T
SHI M 4 T
SHI M 4 T
SHI M 4 T
1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
OPR O PR O PR OP R ETH S B3 ETH S B3 ETH SB 3 ETH SB 3 E H

T SB3 T
E H S B3 ETH SB 3 E T
E T H
H SB 3
OPR O PR OP R O PR O PR O PR O PR OP R
Tx/R x T x/R x T x/R x Tx/ Rx
FAI L F AIL F AI L FA IL
S TM- /O1 -3C S TM 1/- CO -3 ST -1M O/ C-3 ST M- /O1 -3C
SB3 -0 S B3- 0 S B3 -0 S B3- 0 S B3 -0 SB 3- 0 S B3 -0 SB3 -0 Tx0 0T x 0T x Tx0 RU N
M M M M RU N RU N R U N RU N R UN R U N R UN
Rx R x R x Rx
S TM- 1/O -3C S TM -1/ CO -3 ST M-1 O/ C-3 ST M- 1/O -3C
CL 3 T G
SB3 -1 S B3- 1 S B3 -1 S B3- 1 S B3 -1 SB 3- 1 S B3 -1 SB3 -1 Tx T x T x Tx

0R 0R 0R 0R
Rx
R x R x Rx
S TM- 1/O -3C S TM -1/ CO -3 ST M-1 O/ C-3 ST M- 1/O -3C
SB4 -0 S B4- 0 S B4 -0 S B4- 0 S B4 -0 SB 4- 0 S B4 -0 SB4 -0 Tx T x T x Tx
1 1 1 1
MRx MR x MR x MRx
S TM- 1/O C-3Tx S TM -1/ CO -3 ST M-1 O/ C-3 ST M- 1/O -3C
SB4 -1 S B4- 1 S B4 -1 S B4- 1 S B4 -1 SB 4- 1 S B4 -1 SB4 -1 T x T x Tx
1R 1R 1R 1R S ER 1 SE R 1 SE R 1 SE R 1 S E R1 S E R1 S ER 1 S E R1
Rx R x R x Rx
ET PE E TP E E TP E ET PE E TP E E TPE ETP -A E T P- A
E TS 2 ETS 2 ETS 2 ETS 2
17
MCMU 0
MCMU 1
BCSU 0 OMU
CC3C-A
CC3C-B DC3C-B
LANU 0
BCSU 1 BCSU 2 BCSU 3
BC1C-A
FTRB 0 FTRB 1
LANU 1
BCSU 4 BCSU 5 BCSU 6
BC1C-A
6+6 ETPs, 4 ETP-As

BSC3i 1000/2000, maximum ETPT, ETPE and ETPA
amounts
Cabling
BSC3i base cabinet option Extension cabinet
GSW2KB
GSW2KB
CLOC
CLAC
ETC
ETC
MCMU
OMU ETC ETC ETC ETC
MCMU
Fan tray Fan tray Fan tray Fan tray

LANU
LANU
BCSU BCSU BCSU BCSU BCSU
BCSU BCSU BCSU BCSU BCSU BCSU

Fan tray Fan tray Fan tray Fan tray
CLAC
LANU
LANU
GTIC
GTIC
2000 x 900 x 600 (300) 2000 x 900 x 600

6+6 ETPs, 4 ETP-As
S15 BSC LAN topology
L3 IP Connectivity
L3
L3
L3 0 1 0 1 L3
ETP ETP
SWU-0 SWU-1 0 1 0 1 SWU-2 SWU-3
SWU-6 SWU-7 SWU-4 SWU-5
0 1 0 1 0 1
0 1 0 1
OMU BCSU MCMU
ETPLAN PCU PCU
ESB24-D
CPULAN PCULAN
ESB24-D, ESB26 ESB24-D, ESB26

Packet Abis and AoIP – Logical Interfaces
EEP link
ETPA AoIP TC in
Packet Abis MGW
over TDM
ETPT ETPSIG-m
ML PPP bundles AoIP TC
ETP
(Abis HDLC GW C
in BSS
ETPSIG-m
links) BCSUs
Abis ETPSIG-c ETPSIG-c AoIP TC
ETPs all ETP
ETPSIG-c in BSS
C
BCSUs
Packet Abis
over Ethernet PEP HDLC link
ETPE PCU2-D
PEP Eth link

PCU2-E TCSM3 TCSM3i
BSC i standalon
combi e
• ETPSIG-m: O&M / management plane interface between a GW BCSU and an ETPx

• ETPSIG-c: Telecom / control plane interface between all BCSUs and an ETPx
• PEP link: data link between a PCU plug-in unit and an ETPE/T
• EEP link: ETPA – ETPE/T interface for CS user plane in AoIP TC in MGW case
IP Interfaces of ETP, ETP-A
• EL0 – External Link 0: Abis CS/PS u-planes, e2e measurement packets

and SynchE, Telnet, ssh.
– Carrier sense interface
• IL0/1 – Internal Link 0/1: ETPSIG-c, ETPSIG-m, PEP Link, EEP link,
DHCP, FTP (SW upgrade).
• BOND0 – Internal links IL0 and IL1 are connected into one BOND
interface
– Both interfaces are active providing also redundancy
• IN0 – Internal Octeon - DSP interface.
• IM0 – Internal direct link between Sn+ load sharing pair.

ETPSIG-m - Management plane interface between
GW BCSU and ETP
• DMX messaging using logical
ETPT-0-0 ETPT-0-1
addresses
Idle Active
• DX platform delivers
messages via a BCSU that acts ETPSIGs
as a Gateway (GW role IUA
nominated via D2 -MML UDP

IP
commands and has to be the
same for protecting unit) Ethernet
• alarms, supervision,
diagnostics, recovery, IP
configuration OMU, MCMU,
GW BCSU-1
• configuration BCSU
• Unreliable protocol ->
application must take care of Message Bus
reliability BSC
• ETPSIGs use only limited IUA
protocol (IUA Data
Request/Indication messages)
ETPSIG-m establishment in startup of ETPE/T/A
• ETP unit sends DHCPDISCOVER message in startup of ETP

unit
– BSC internal DHCP server in OMU identifies the ETPE/T/A units based
on information (CARIDx, CABIDx and ADDMODxx) ETP adds to a
DHCPDISCOVER.
• BSC internal DHCP server in OMU provides ETPSIG-m
addresses in DHCPOFFER
– ETP’s own IP address and GW BCSU IP address
 Defined with QR and D2 –MMLs
• No DHCP service for ETPC
– IP addresses configured locally with ST and stored into flash of ETPC
 Must match with the configuration of master BSC
• ETPSIG-m connectivity is established by ETP. After this DMX
messaging based configuration can be started

ETPSIG-c - Telecom / control plane interface between
all BCSUs and ETP
• For telecom ETPT-0-0 ETPT-0-1 ETPE-n-0 ETPE-n-1

messaging inside the Idle Active Active Idle
BSC, each BCSU has
direct interface to
each ETP unit
ETPSIGs
IUA
UDP
IP
Ethernet
BCSU-0 BCSU-n
Message Bus
BSC

ETPSIG in case of AoIP (TC in BSS)
MSS/MGW
BCSUs
IP/Ethernet
BSC-1 connectivity
ETPC-0-0
ETPSIGs
IUA ETPC-1-0
BCSUs UDP
IP
ETPC-2-0
Ethernet
BSC-n
(max 8 per ETPC)
ETPC-3-0
TCSM3i cabinet
• One of the BSCs sharing the ETPC sees the ETPC as a functional unit and terminates the
ETPSIG-m
• In combined BSC3i/TCSM3i installation the BSC that terminates the ETPSIG-m is the master
BSC
• The other BSCs see the ETPC as a resource to be used with a certain TCSM functional unit
• There are ETPSIG-c connections between ETPC and each BSC using the resources

Dynamic Abis BSC
BTS ET TDMAter TCSM2i
ET ,
Sn+pair Sn+pair TCSM3i
GSWB or
ETP Sn+pair
E1 SET A over IP MGW
/T Packet Abis ETPT
ETS2
1
(STM-1/OC-3) Sn+pair MUX ETP GigE
MG
SET
ETP C W
STMU ETPT
TR3s
Packet Abis
over Ethernet
TCSM3i
Sn+pair
GigE ETP
IP-BTS Packet- TDM A over IP
Packet- Sn+pair
switched ETPE
network
network ET ETP-A
MG
GigE
ETP W
C
*) PCU2-E uses PCU2-D TCSM3i
internal LAN for ETP
connectivity.
PCU2-E *)
Sn+grou
A over IP
BCSUs p
ETP-A TC in MGW
m/c plane ESB24s
ETPA
MG
to ETPs GigE W

OMUSIG & TRXSIG
OMUSIG/TRX
SIG
IUA
SCTP
Ethernet IP
connectivity
Packet Abis over

Ethernet
SWU-0 SWU-1 SWU-n SWU-n+1

OMUSIG/TRX
SIG
IUA
SCTP
CPU ETPT IP
Packet Abis over

BCSU
TDM
BSC

Packet Abis C/M-planes – TRXSIG/OMUSIG
• IUA/SCTP protocol
• Terminated in BCSU
– Ethernet port of the CPU, no AS7
• Packet Abis over TDM: connected via ETPT
• TRXSIG and OMUSIG are carried over different SCTP associations
– OMUSIG SCTP association carries only one stream per direction
– TRXSIG SCTP association shall carry two streams per direction – one is for
Measurement Report messages
• SCTP multihoming is not used
• SCTP chunk bundling (multiplexing) is used by default
• SCTP fragmentation and reassembly is supported
• Three parameter sets:
– AFAST for normal Abis
– ASATEL for satellite Abis
– AMEDI between normal and satellite Abis

Example: Sigtran, TRXSIG and ETPSIG-c in
Normal TCH setup
• Figure 1
- PAoTDM/Eth
- AoIP (TC in MGW)

Packet Abis over TDM – U-plane
conversion/forwarding in ETPT
ETPT
Abis CS u-plane <-> Ater TRAU Frames

Abis CS u-plane <-> ETPA
Abis PS u-plane <-> PCUs
RTP Payload Payload type+PCU frame
Compr. RTP header AoIP packets PEP id Payload type+PCU frame

voice codec
Mux Header DSP protocol
in TRAU Frames
Compressed UDP Modified UDP
IP/UDP PEP id
IP Modified IP
ML/MC-PPP
HDLC TDM Ethernet Ethernet TDM/HDLC like
TDM (Hotlink)
Ater EEP PCU2-E PCU2-D

Packet Abis over TDM

Packet Abis over TDM – C/M-plane forwarding in
ETPT
ETPT
OMUSIG TRXSIG OMUSIG TRXSIG

IUA IUA
SCTP SCTP
IP IP
ML/MC-PPP BSC internal Ethernet
HDLC
TDM (Hotlink)
BCSUs

Packet Abis over Ethernet – U-plane
conversion/forwarding in ETPE
ETPE
Abis CS u-plane <-> Ater TRAU Frames

Abis CS u-plane <-> ETPA
Abis PS u-plane <-> PCUs
RTP Payload Payload type+PCU frame
Compr. RTP header AoIP packets PEP id Payload type+PCU frame

voice codec
Mux header DSP protocol
in TRAU Frames
UDP UDP Modified UDP
PEP id
IP IP Modified IP
Ethernet
TDM Ethernet Ethernet TDM/HDLC like
Packet Abis over Ethernet Ater EEP PCU2-E PCU2-D

A over IP (TC in MGW) – U-plane forwarding in
ETPA
ETPA
CS u-plane
bi-casting
voice codec voice codec
RTP RTP
UDP UDP
IP IP
Ethernet Ethernet
EEP-interface AoIP TC in MGW

A over IP (TC in BSS) – U-plane conversion in
ETPC
TCSM
3i
TR3 ETPC
conversion to TDM
G.711
G.711 in RTP
64kb/s channel
UDP
IP
TDM
Ethernet
A/TDM
AoIP TC in BSS

ETPE/ETPT/ETPC Equipment Protection
• Redundancy principle: Load sharing pair

• Normally both units are in WO-EX state, one unit is active and the other is
protecting (idle)
– Only the active unit is processing Abis/AoIP traffic
• Switchover: Protecting unit takes the active role
– Virtual address mapping is changed at switchover (Gratuitous ARP)
• Forced switchover
– Initiated by forced state change or restart of the active unit
– Forced state change can be caused by a fault (e.g. alarm hw_block_failure_in_piu (2794))
or user command
– Calls are cleared
• Controlled switchover
– Initiated when the user changes the active unit to BL state (forced parameter not used)
– Ongoing calls are maintained, information of ongoing calls is warmed to the redundant
unit during switchover
 Disturbance Spare Unit Warmup Failure (1684) if warming fails

ETS2 Equipment Redundancy with ETPT
STM1/OC3
interfaces SET-0
Hotlink
SET-1 interfaces
working SET-2
Not used SET-3

ETPT-0-0
STMU-0 active GSWB-
active 0
MPS1+1 GigE c ok
pair s
SET-4
ETPT-0-
SET-5 1
idle
protecting SET-6 GSWB-
1
Not used SET-7
STMU-1
idle BSC

ETPA Equipment Protection
• Redundancy principle: Load sharing group

• Normally all units are in WO-EX state and are able to carry
traffic
• Forced state change
– Forced state change can be caused by a fault (to TE) or user command
(to BL)
– Calls are cleared
• Controlled shutdown
– Initiated when the user changes the unit to BL state (forced parameter
not used)
– Ongoing calls are maintained (until time-out), new calls are not allowed

Interface Redundancy
• ETP or ETP-A connects to the transport network via two

different interfaces, one interface is active and the other is
passive
– Carrier sense Ethernet
– ‘ETP Ethernet interface failure’ (3515) alarm
• ETPT is a special case: interface redundancy is implemented
in the ETS2. There’s a control channel between the ETPT and
ETS2 for interface redundancy purposes.
– Unit state bit in the hotlink.

ETS2 Interface Redundancy with ETPT
Hotlink
interfaces
STM1/OC3 SET-0
interfaces
SET-1
GSWB-
working SET-2 ETPT-0-0 0
MPS1+1 active
pair protecting SET-3
STMU-0
active
GSWB-
1
BSC

Supported Call Paths - Packet Abis and Legacy A-
interface
Intra-
BSC HO
Dynamic
Abis BSC
BTS ET TDMAter TCSM2,
ET TCSM3
2n 2n or MGW
GSWB
E1/ SET ETP 2n A over IP
Packet
Abis
IP-BTS
T1 ETPT SB ETP-A GigE TC in BSS
over TDM
(STM
-1/OC
-3)
ETS2
2n MUX ETPC MGW Legacy Abis
SET ETP and Packet
STMU ETPT TR3s Abis are
TCSM3 possible with
TDM
TCSM3A over IP legacy A-if
Ater TC in BSS
ET ETP
-A GigE MGW
PCU2-D
ESB24s PCU2-E Pool

A over IP
ETP-A TC in MGW
BCSUs MGW
m/cplane ETPA GigE
to ETPs
Note: BSS Internal HO is a new HO type

specified because of AoIP.

Supported Call Paths - Packet Abis and AoIP (TC in
BSS)
Dynamic
Abis BSC
BTS ET TDMAter TCSM2,
ET TCSM3
2n 2n or MGW
ETP
GSWB
E1/ SET 2n A over IP
Packet
Abis
IP-BTS
T1
over TDM ETS2
ETPT SB ETP-A GigE TC in BSS
(STM
-1/OC
-3) 2n MUX ETPC MGW
SET ETP
STMU ETPT TR3s
TCSM3
Intra- TDM Legacy Abis
TCSM3A over IP
BSC HO Ater TC in BSS and Packet
ET ETP
-A GigE MGW Abis are
PCU2-D possible with
AoIP (TC in
ESB24s PCU2-E Pool
A over IP BSS)
ETP-A TC in MGW
BCSUs MGW
m/cplane ETPA GigE
to ETPs
Also in case
of remote
TCSM3i

Supported Call Paths - Packet Abis and AoIP (TC in
MGW, Full IP)
MSS
Intra-BSC HO controlled
only within BSS Internal
Packet Abis HO between
Dynamic
Abis BSC
BTS ET TDMAter TCSM2, A-if types
ET TCSM3
2n 2n or MGW
GSWB
E1/ SET ETP 2n A over IP
Packet
Abis
IP-BTS
T1
over TDM ETS2
ETPT SB ETP-A GigE TC in BSS
(STM
-1/OC
-3) 2n MUX ETPC MGW
SET ETP
STMU ETPT TR3s
TCSM3
TDM
Ater
TCSM3A over IP
TC in BSS
ET ETP
-A GigE MGW
PCU2-D
ESB24s PCU2-E Pool

A over IP
ETP-A TC in MGW
BCSUs MGW
Legacy Abis is m/cplane ETPA GigE
not possible with to ETPs
AoIP (TC in
MGW) in S15


CS user plane

ETP and ETP-A plug-in units in BSC and TCSM
Dynamic Abis BSC

BTS ET TDMAter TCSM2i,
ET TCSM3i
Sn+pair Sn+pair or MGW
GSWB
ETP Sn+pair
E1/ SET A over IP
T1 Packet Abis ETPT
ETS2
MGW
SET
ETP
STMU ETPT
TR3s
Packet Abis
over Ethernet
TCSM3i
Sn+pair
GigE ETP
IP-BTS Packet- TDM
Packet- Sn+pair A over IP
switched ETPE
network
network ET ETP-A
MGW
ETPC GigE
*) PCU2-E uses internal PCU2-D TCSM3i

LAN for ETP
connectivity.
PCU2-E *)
Sn+group
BCSUs A over IP
ETP-A TC in MGW
m/c plane
ESB24s MGW
to ETPs ETPA
GigE

Downlink CS traffic handling in ETPT
•ETPT receives Ater/TRAU frames from GSWB (in case TC is

in BSS) or RTP packets from ETPA (in case TC is in MGW) for
the given CS call
•If ETPT receives Ater/TRAU packets from GSWB
– ETPT converts Ater/TRAU packets to RTP packets
– ETPT performs silence removal
• ETPT multiplexes the RTP packets to Packet Abis packets.
• If header compression is enabled for UDP/IP, ETPT performs
UDP/IP header compression for the Packet Abis packets.
• ETPT sends the Packet Abis packets to the BTS sites using
ML/MC-PPP links. If header compression is enabled for ML-
PPP, ETPT performs header compression for the ML-PPP
headers
•
Uplink CS traffic handling in ETPT
•ETPT receives Packet Abis packets from the BTS sites via
ML/MC-PPP link.
•ETPT decompress the packet headers if needed.
•ETPT demultiplexes the RTP packets, if needed.
•In a case where Transcoder is located in BSS (it is either in
BSC or it is standalone Transcoder) ETPT converts the RTP
packets to Ater/TRAU frames and sends them to GSWB.
•ETPT adds buffer delay to ensure that variation (jitter) in packet
arrival time does not normally cause missing frames on the Ater
interface.
•In a case where Transcoder is located in MGW, ETPT sends
the RTP packets to the correct ETPA which sends them further
to MGW.
Downlink CS traffic handling in ETPE
•ETPE receives Ater/TRAU frames from GSWB (in case TC is

in BSS) or RTP packets from ETPA (in a case TC is in MGW)
for the given CS call.
•If ETPE receives Ater/TRAU packets from GSWB
– ETPE converts Ater/TRAU packets to RTP packets
– ETPE performs silence removal
• ETPE multiplexes the RTP packets to Packet Abis packets.
• ETPE sends the Packet Abis packets to the BTS sites using
the Ethernet interface

Uplink CS traffic handling in ETPE
•ETPE receives Packet Abis packets from the BTS sites via
Ethernet link
•ETPE demultiplexes the RTP packets, if needed.
•In a case where Transcoder is located in BSS (it is either in
BSC or it is standalone Transcoder) ETPE converts the RTP
packets to Ater/TRAU frames and sends them to GSWB.
•ETPE adds buffer delay to ensure that variation (jitter) in
packet arrival time does not normally cause missing frames on
the Ater interface.
•In a case, where Transcoder is located to MGW ETPE sends
the RTP packets to the correct ETPA which sends them further
to MGW.

Downlink CS traffic handling in ETPA
•ETPA receives DL CS U-plane RTP packets from Media

Gateway via A over IP interface. The RTP packets may carry
speech frames (or CS data, not possible at the moment)
•ETPA identifies the CS connection based on the UDP port
number where the DL CS-U-plane RTP packets are received
•ETPA sends the received RTP packets to the correct ETPT (in
case of Packet Abis over TDM) or ETPE (in case of Packet Abis
over Ethernet) within UDP/IP packets.
– The destination IP address shall be the BCF’s U-plane IP address
– The source IP address shall be the ETPA’s IP address that is used on
the EEP interface
– The destination UDP port number shall be the ETPT/ETPE’s UDP port
number that has been provided to ETPA at the CS call setup.
– The source UDP port number shall be the ETPA’s UDP port number
that ETPA has allocated towards the ETPT/ETPE at the CS call setup.

Uplink CS traffic handling in ETPA
•ETPA receives UL CS U-plane RTP packets either from ETPT

(in case of Packet Abis over TDM) or from ETPE (in case of
Packet Abis over Ethernet) via the EEP interface.
•ETPA identifies the CS connection based on the UDP port
number where the UL CS-U-plane RTP packets are received
(there is a separate UDP port number for each CS connection).
•ETPA sends the received RTP packets to the correct Media
Gateway via the A over IP interface within UDP/IP packets
– The destination IP address shall be the MGW’s IP address
– The source IP address shall be the ETPA’s IP address that is used on
the AoIP interface
– The destination UDP port number shall be the MGW’s UDP port
number that has been provided to ETPA at the CS call setup
– The source UDP port number shall be the ETPA’s UDP port number
that ETPA has allocated towards the MGW at the CS call setup

Downlink CS traffic handling in ETPC
•ETPC receives DL CS U-plane RTP packets from Media

Gateway via A over IP interface. The RTP packets may carry
speech frames or Clearmode data
•ETPC identifies the CS connection based on the UDP port
number where the DL CS-U-plane RTP packets are received
•ETPC performs jitter buffering for the RTP packets
•ETPC converts the RTP packets to G.711 coded 64k speech
samples (PCMU or PCMA encoded speech) or to CS data
samples (CS-data/fax/HSCSD data)
•ETPC transmits the speech/data samples to TR3 plug in unit
with fixed frequency (50 packets/s)

Uplink CS traffic handling in ETPC
•ETPC receives 64k G.711 speech samples or CS data (CS-

data/fax/HSCSD-data) samples from TR3 plug-in-unit with fixed
frequency (50 packets/s)
•ETPC identifies the CS connection based on the ETP-PCM
connection (PCM ID and TSL). Once the CS connection is
identified, ETPC is able to resolve the correct destination
address
•ETPC converts the 64k G.711 speech samples or CS data
samples to RTP packets
•ETPC sends the RTP packets to Media Gateway via A over IP
interface

Bicasting in ETPA
•ETPA supports bicasting functionality for the CS call when intra-BSC

handover is performed so that there is no change in the A interface
connection.
•Bi-casting in BSS is possible only if codec type and channel mode
are not changed during Intra-BSC handovers, but here are following
exceptions:
– Bi-casting in GSWB: FR_AMR <-> HR_AMR is possible using Dual rate TRAU-
feature.
– Bi-casting in ETPA: FR_AMR <-> HR_AMR is possible, if compatible codec
types and codec configuration are used in source and target side.
• If codec is not compatible in AoIP TC in MGW, then BSS Internal
Handover is used and bi-casting is done by MGW and there are
two streams from MGW to BTS and back.
• Bi-casting is done by MGW during Inter-BSC handovers and in
BSS Internal Handovers.

Multiplexing of CS U-plane packet
•In DL direction ETPT/ETPE shall pack several CS U-plane

RTP packets, that are addressed to the same BCF, to one
Packet Abis packet in such a way that:
– The length of the Packet Abis packet does not exceed the ‘Maximum
Multiplexing packet size’ parameter value
– The wait time for any CS U-plane RTP packet does not exceed the
‘Maximum Multiplexing wait time on ETP’ parameter value
– Number of Frames per packet is maximized, within the above
constraints
• In UL direction ETPT/ETPE shall demultiplex the CS U-plane
RTP packets that are received from the BCF within one
Packet Abis packet

Silence deletion in CS U-plane for AMR DL in ETPT
and ETPE
•In case TC is in BSS, ETPT/ETPE shall support silence
deletion in CS U-plane for AMR DL frames in the following
manner:
– ETPT/ETPE shall not send AMR “NoData” frames to the downlink
direction, unless the AMR “NoData” frames carry PAC/TFO signalling in
which case the AMR “NoData” frames shall be sent. In other words,
ETPT/ETPE shall delete the DL AMR “NoData” frames that do not carry
PAC/TFO signalling.
– The next AMR frame, that is sent to DL direction after some DL AMR
“NoData” frames have been deleted, shall have the next unused RTP
sequence number and a timestamp which ETPT/ETPE has
incremented by the correct number of 20 mSec periods.

Silence Deletion in CS U-plane for FR/EFR/HR DL
in ETPT and ETPE
•In case TC is in BSS, ETPT/ETPE shall support silence
deletion in CS U-plane for FR/EFR/HR DL frames in the
following manner:
– For FR/EFR/HR codec SID frames on the Downlink which are received
every 20 mSec ETPT/ETPE shall send the first SID frame following the
latest speech frame (i.e. the first frame with SP=0 shall be sent) and
after that ETPT/ETPE shall send every 8th SID frame. ETPT/ETPE
shall not send the other SID frames (i.e. the other DL SID frames are
deleted)
– The next frame, that is sent to DL direction after some DL SID frames
have been deleted, shall have the next unused RTP sequence number
and a timestamp which ETPT/ETPE has incremented by the correct
number of 20 mSec periods.

TRAU frame conversion
•In CS U-plane, when TC is in BSS, ETPT/ETPE converts the

RTP packets to TRAU frames in the UL direction and TRAU
frames to RTP packets in the DL direction. The conversion
depends on the type of CODEC being used for the CS call
S. RTP_Payload_Type Codec Name Format

No.
1. 3 GSM-FR 16 kbps TRAU frame format
2. 110 GSM-EFR 16 kbps TRAU frame format
3. 112 AMR-NB 16 kbps TRAU frame format
4. 113 AMR-WB 16 kbps TRAU frame format
5. 95 Data codec 16 kbps TRAU frame format
6. 111 HR 8 kbps TRAU frame format
Supported codecs

Forwarding and addressing of OMUSIG and
TRXSIG signalling in ETPT
•ETPT forwards OMUSIG and TRXSIG signalling between the
BCSUs and up to 256 BTS sites (BCFs).
•When ETPT receives a DL C-plane or M-plane IP packet from
BCSU, ETPT forwards it to the correct BCF via the correct
HDLC bundle based on the IP packet’s destination IP address
(= BCF’s M-plane IP address).
•When ETPT receives an UL C-plane or M-plane IP packet from
BCF, ETPT forwards it to BCSU based on the IP packet’s
destination IP address (≠ ETPT’s own IP address) and based
on the IP packet’s Protocol field (= SCTP).

PS user plane

ETP and ETP-A plug-in units in BSC and TCSM
Dynamic Abis BSC

BTS ET TDMAter TCSM2i,
ET TCSM3i
Sn+pair Sn+pair or MGW
GSWB
ETP Sn+pair
E1/ SET A over IP
T1 Packet Abis ETPT
ETS2
MGW
SET
ETP
STMU ETPT
TR3s
Packet Abis
over Ethernet
TCSM3i
Sn+pair
GigE ETP
IP-BTS Packet-
Packet- TDM
switched Sn+pair A over IP
switched ETPE TCin BSS
network Ater
network ET ETP-A
MGW
ETPC GigE
*) PCU2-E uses internal PCU2-D TCSM3i

LAN for ETP
connectivity.
PCU2-E *)
Sn+group
BCSUs A over IP
ETP-A TCin MGW
m/c plane
ESB24s MGW
to ETPs ETPA
GigE

DL PS Traffic handling in ETPT
•ETPT receives a Packet Abis PCU Frame from PCU2-D or

PCU2-E within a HDLC Data frame or within a UDP/IP packet.
•ETPT updates its look-up tables based on the addressing
information that is received along the Packet Abis PCU Frame.
The old association, if there is one, is overwritten.
•ETPT constructs a PS U-plane IP packet for DL transmission.
•ETPT applies the UDP/IP header compression to the
constructed IP packet if the header compression for UDP/IP has
been enabled
•ETPT sends the constructed IP packet to the correct BCF over
the correct MC/ML-PPP link. If header compression is enabled
for ML-PPP, ETPT performs header compression for the ML-
PPP headers.

UL PS Traffic handling in ETPT
•ETPT receives a PS U-plane IP packet from BCF via some

MC/ML-PPP link. Destination UDP port number is PS_UDP-
MUX-Port.
•ETPT makes the de-compression for the UDP/IP header, if
needed.
•ETPT takes the RTP payload (i.e. the Packet Abis PCU Frame)
out of the received PS U-plane IP packet
•By using its look-up tables ETPT retrieves the PEP ID
association for the packet
•ETPT sends the received Packet Abis PCU Frame to PCU2-
D/E with the necessary address information via the correct
HDLC link or via the correct Ethernet link.

DL PS Traffic handling in ETPE
•ETPE receives a Packet Abis PCU Frame from PCU2-D or

PCU2-E within a HDLC Data frame or within a UDP/IP packet.
•ETPE updates its look-up tables based on the addressing
information that is received along the Packet Abis PCU Frame.
The old association, if there is one, is overwritten.
•ETPE constructs a PS U-plane IP packet for DL transmission.
•ETPE sends the constructed IP packet to the correct BCF via
the Ethernet interface.

UL PS Traffic handling in ETPE
•ETPE receives a PS U-plane IP packet from BCF via the

Ethernet interface.
•ETPE takes the RTP payload (i.e. the Packet Abis PCU
Frame) out of the received PS U-plane IP packet.
•By using its look-up tables ETPE retrieves the PEP ID
association for the packet
•ETPE sends the received Packet Abis PCU Frame to PCU2-
D/E with the necessary address information via the correct
HDLC link or via the correct Ethernet link.

Buffering of UL PS traffic in ETPT and ETPE
•ETPT and ETPE buffers the UL User Plane data traffic towards
the PCU2-Ds to prevent data loss in possible congestion
situation in PCU2-D – ETPT/ETPE interface.
•The buffer size per HDLC link shall be about 3 kbytes (that
amount of data can be transmitted via the HDLC link within 50
ms). If the buffer overflows, then the incoming packets can be
discarded.

Configuring

Configuring the Packet interfaces
1. Increasing BCSU memory to 1GB (optional, needed for BSC1000/2000)

 S15 Firmware and memory upgrade procedure
2. IP Address planning
 Guidelines from NED: BSC IP Connectivity guidelines
3. Configuring LAN topology changes (topology, L3, optional)
 L3 BSC IP Site Connectivity upgrade
4. Configuring Packet Abis
5. Configuring BCF
6. Configuring Packet A

Configuring LAN topology changes (optional)
1. Configuring LAN topology change T3-T6

2. Configuring L3

Configuring the Packet Abis BSC - Steps
1. Configuring LAN Devices (ETPLAN)

2. Creating ETPE/T
3. Configuring PCU2 for Packet Abis
4. Configuring ETS2 for Packet Abis over TDM (optional)
5. Configuring ETPE/T network interfaces
6. Configuring ETPE/T IP addresses
7. Configuring ETPSIG interfaces
8. Configuring EEP
9. Configuring PEP
10. Configuring BCSU network interfaces for OMUSIG and TRXSIG
11. Configuring BCSU IP addresses for OMUSIG and TRXSIG
12. IP Routing Data Handling
 EEP-if (BTS)
 TRXSIG and OMUSIG (ETPT)

Packet Abis new BTS installation
– Outline of Activation and operation
Steps to create BCF to use Packet Abis
1. Create SCTP associations for OMUSIG & TRXSIG(ZOY)
2. Create D-channels for OMUSIG & TRXSIG (ZDW)
3. Create Abis HDLC links (only in case of Packet Abis over
TDM)
4. Create BCF
5. Create BTS/HOC/POC – no changes to these
6. Create TRXs
7. Open abis HDLC links (only in case of Packet Abis over
TDM)
8. Unlock/activate created objects

Configuring the Packet A with ETPA in BSC - Steps
1. Creating ETPA
2. Configuring ETPA network interfaces
3. Configuring ETPA IP addresses
5. Configuring EEP
 EEP-if (BTS)
 MGW

Configuring the Packet A with ETPC in TCSM-
Steps
1. ETPC local configuration
2. Creating ETPC
3. Configuring ETPC network interfaces
4. Configuring ETPC IP addresses
 ETPSIG
 MGW

PA over Ethernet BSC internal host port VLANs
TRXSIG
Optional CS U-plane
BCF group level Optional
VLAN BCF group level
VLAN
OMUSIG
Optional
BCF group level PS U-plane
VLAN Optional
BCF group level
VLAN
ETPSIG-c
No VLAN
ETPSIG-m
No VLAN
ETPE ETPAs
EEP link
BSC internal
CS u-plane VLAN
PEP link
BSC internal PCU2-Es
PS u-plane VLAN
DHCP
no VLAN
BCSU BCSU BCSU BCSU BCSU BCSU BCSU OMU
0 1 2 3 4 5 6

PA over TDM BSC internal host port VLANs
EEP link
CS U-plane
BSC internal
over TDM
CS u-plane VLAN
PS U-plane STMU
over TDM
TRXSIG OMUSIG/TRXSIG is routed through ETPT i.e.

ETPT is serving as next-hop gateway towards
VLAN BTS from BCSU.
OMUSIG
ETPT ETPAs
VLAN
ETPSIG-c
No VLAN
ETPSIG-m PCU2-Es
No VLAN
PEP link
BSC internal
PS u-plane VLAN BCSU BCSU BCSU BCSU BCSU BCSU BCSU OMU
0 1 2 3 4 5 6
DHCP
no VLAN
ETPSIG-m/c addresses and connectivity
ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T ETPE/T
0-0 0-1 1-0 1-1 2-0 2-1 3-0 3-1 4-0 4-1 5-0 5-1
active idle active idle active idle active idle active idle active idle
ETPSIG-c
No VLAN
ETPSIG-m
No VLAN
= one IPv4 address
BCSU BCSU BCSU

BCSU BCSU BCSU BCSU
6
0 1 2 3 4 5
SP-EX

Troubleshooting

IP connectivity troubleshooting tips
– Physical connection verification

 Cabling, port settings (state, duplex, speed, VLAN),
– Logical connection verification
 VLAN, subnets, GW, spanning tree (loops)
– Ping, tracert
– Wireshark (or any other Ethernet monitoring tool)
 Monitoring connection in SWUs (or site switch)

Useful commands in ETP
– Connectivity
 ping [ip_address]
• basic connectivity tests, ping from ETPE EL0 to BCF and from ETPA to MGW
NPGE has to work
• it is normal behavior that ping from ETPT EL0 to BCF does not work
 arp -a or dafdb
• displays ARP entries of unit. If entry for GW address is <incomplete> then there is a
problem in connectivity

– Configuration
 dbcfinfo
• displays all BCFs configured to unit
 dbcfinfo [bcf_id]
• displays IP configuration related to BCF
 etpsig_m_info
• displays ETPSIG-M information
 etpsig_c_info
• displays ETPSIG-C information
 detpps
• displays to which PCU PEP link is created (can be used with ETPE/ETPT only)
 dhdlcinfo [index]
• displays status of HDLC link between ETPT and BCF. LCP-STATE has to be 9 for
BCF OMUSIG to work. There is separate HDLC link for each BCF. Link index of a
BCF is visible in ZEFO MML output (EBID parameter).

– Configuration
 route or drfdb
• displays IP routing information
 ifconfig or dinterface
• displays interface information
 dbscp
• displays QoS and overload parameters

– Traffic
 detpcs all
• displays number of active CS calls handled by unit
 dudul
• displays number of UL IP packets routed by unit
 duddl
• displays number of DL IP packets routed by unit
 dpdul
• displays number of UL IP packets dropped by unit
 dpddl
• displays number of DL IP packets dropped by unit
 netstat -a
• displays TCP/UDP ports used by unit
 dscfp
• displays number of SCTP packets passed by ETPT

Q&A

Some answers to earlier asked questions
– Why PEP interface is created only into IFETH0 in PCU2E and

interface is created as BOND ( of interfaces IL0 and IL0) in ETP
 PEP interface is created in PCU only to IFEHT0. PCU2 internally binds
IFETH1 into BOND interface.
– Does call change to Full IP after HO from legacy Abis to PAbis
 When HO is made from legacy Abis BTS into PAbis BTS, A-if type is not
changed, i.e. call remains using legacy A-if.
– Does all the TRXs of one BTS (BCF) be under the same BCSU as
only one BCSU IP address is given to BCF during commissioning.
 TRXs can use different BCSUs (lapd) in one BTS as they do also in legacy
abis configuration
 IP address given during commissioning is only the IP address of OMUSIG
BCSU. Other IP addresses are configured by BSC during BCF startup.

RG20 Pilot Lessons Learnt,
Technical Findings & Tips
RG20 Pilot Team
Ver 5.0

Introduction
• This document summaries technical findings and tips learnt in

RG20 pilots
• This document aims to help new RG20 projects to let them
avoid and overcome some of the issues faced in piloting
phase

ETPE/T/A units general
Entity Area Finding & Tip
While upgrade of ETP it must be ensured that both flashes are working fine (this can be
checked by ZWDM MML command for active and stand by flash or ssv 1 and ssv 2
output on ETP service terminal). Also ensure to upgrade the SW in both the flashes
ETP/
BSC while downloading new SW into ETP. Avoid restarting the ETP with C=TOT option as
ETP-A
this results in flash switchover and incase the back up flash is not fine the card gets
stuck. The recovery for this is to physically jack out and jack in the card since physical
jack out and jack in brings the card from the active flash.
ETP/ While configuring etpsig-m for active and redundant ETPE/T/A ensure that the GW
BSC
ETP-A BCSU is the same. This is to avoid problems during switchovers and restarts.
The electrical SFP type of the EL0 interface shall be the FCLF-8520-3. The FCLF-8520-
3 uses the SFP’s RX_LOS pin for link indication. The link indication is needed for
ETP/ interface and equipment redundancy i.e. to trigger switchover if there’s a failure in the
BSC Ethernet interface.
ETP-A
The FCLF-8521-3 does not have a link indication feature (RX_LOS is internally
grounded).
If electrical (copper) EL0 cabling is in use the Autoneg setting in the other peer (external
ETP/ switch port) shall be ON (dublex auto, speed auto).
BSC
ETP-A If optical (fibre) EL0 cabling is in use the Autoneg setting in the other peer (external
switch port) shall be OFF.

ETPE/T/A units and Packet Abis general
With equipment protection normally the both ETPE/T/C units of a pair are in WO-EX
state. The other is active and the other is idle. The controlled way to make a switch
ETP/
BSC over is to change the active unit to BL. Then the active unit goes to BL-EX and after the
ETP-A
calls are transferred to the pair the unit goes to BL-ID and the other unit of the pair
takes the WO-EX active role.
PAoETH Differing from the default BTS SCF values for the OMUSIG SCTP signaling protocol,
BTS the Selective Acknowledgement period has to be configured to 110ms (same as in
PAoTDM
BSC).
PAoETH As default SCTP bundling is in use for OMUSIG and TRXSIGs. Because of bundling
BSC delay the BTS level parameter SLO (number of timeslots to spread retransmissions)
PAoTDM
must be changed from 10 to SLO=32.
If mirroring is configured to take Wireshark logs from ports of a BSC internal LAN switch
e.g
mirror enable
mirror add 1/1/3-1/1/20
mirror monitor 1/1/24
SWUs
BSC (ESB24 when ending the monotoring It’s not enough to
-D) mirror disable
no mirror monitor
remember also to remove ports that were mirrored
mirror del 1/1/3-1/1/20
otherwise there may be disturbances in the switching.

A over IP
BSC does not supervise the e-2-e user plane of AoIP (both TC in MGW and TC in
AoIP BSS) is not supervised. If NSN MGW is in use turn the RTCP u-plane supervision
BSC
u-plane OFF. When integrating the ETPA/C unit remember to ping the other peer (i.e. MGW
u-plane address).
Set the NSN MSS/MGW parameter AOIP TRANSPORT TYPE PERCENTAGE to

BSC AoIP 100. Then the AoIP is used for all the call set-ups when using of AoIP is possible.
RG20 release has a restriction that AoIP TC in MGW can be used only with Packet
Abis BTS sites. Because of this the system makes an BSS internal HO with MSS
support if:
the MS makes an intraBSC HO from Packet Abis cell to a legacy Abis cell (the call has been set
BSC AoIP up with AoIP).
the MS makes an interBSC HO (or interSystem HO) to a legacy Abis cell and MSS first tries to
use AoIP for the call. The call is re-attempted with an AoTDM circuit.
This BSS internal HO with MSS support is needed to change the A-if type used for
the call.
A-if If with NSN MSS a log writing MCMU log: TWO WAY RELEASE TO SWICOP;double
signalling reserve is seen in the MCMU the BSSAP par nbr. 61 "MODIFIED RE-
BSC ESTABLISHMENT RELEASE SEQUENCE“ shall be changed to Yes in the MSS.
(also
legacy A)

Packet Abis over IP/Ethernet
D-channel creation: Instead of modifying the existing D-channels it is better to create
new D-channels for Packet Abis sites using different naming convention: e.g. P011A
BSC NPO instead of T011A (for BCF 011 TRX 10). This simplifies the switchover as new D-
channels can be created beforehand. Also fallback is easier if needed. After “stability
period” the old D-channels shall be deleted. Applicable also for PAoTDM.
SIGTRAN subnets are advertised towards core network but TRXSIG and OMUSIG not.
To support separate global and local routing tables in multilayer site switch (MLS) it is
advisable to create separate VLANs in L3 interface between SWU and MLS for
BSC NPO SIGTRAN and OMU/TRXSIG.
See pilot plans in NPO IMS: Cosmote RG20 Pilot (Packet Abis and AoIP)
material https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/426741732 Microsoft
and NPO pilot learning's. PowerPoint Presentation

Traffic scheduling activation assumes valid value for DLCIR parameter even the
BSC/BTS NPO given parameter is relevant only for Ethernet and not for ML-PPP. As a workaround
apply: DLCIR = ML-PPP capacity.
In S15 you cannot have Header Compression ON in one direction. So, there is
nothing like HC enabled in UL only or HC enabled in DL only. It has to be enabled
BSC/BTS HC
in both sides ( from BSC and BCF) and then BCF and HDLC link lock unlock to be
performed.
In case the associations for certain PAoTDM sites go down. The work around for
BSC HDLC this is to lock and unlock the HDLC links followed ETPT switchover.
A Packet Abis over TDM feature specific PRFILE shall be installed to change the
ML PPP value of PRFILE parameter PCM_MAINT_ANNOUNCE_TL (parameter ID Class
BSC
bundle 10, id 4) from ten to five seconds. This makes the ETPT to react faster if a single
E1/T1 link of a MLL PPP bundle fails.

OSC
BSC/BTS OSC BTS SW has to be attached to BCFs before OSC can be activated
Null circuit has to be created to make CSDAP working, example:

BSC OSC ZRCC:TYPE=SPE,NCGR=BB_ZERO,CGR=99:FORMAT=0,HUNTED=N,:
ZRCA:NCGR=BB_ZERO:CRCT=0-0&-1:


Packet Abis and A Over IP: Soc Classification Level 1 © Nokia Siemens Networks Presentation / Author / Date

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

Packet Abis and A Over IP: Soc Classification Level 1 © Nokia Siemens Networks Presentation / Author / Date

Uploaded by

Copyright:

Available Formats

Packet Abis and A over IP

Soc Classification level

Before BSS13 RG10 RG20

Soc Classification level

Legacy TDM PWE CESoPSN

• TDM: All timeslots/E1 are pooled  single “bit-pipe”

Soc Classification level

Soc Classification level

Soc Classification level

AoIP C-plane MSS

Soc Classification level

The SLA parameters have the following recommended and maximum

Soc Classification level

Soc Classification level

*) PCU2-E uses PCU2-D TCSM3i

Soc Classification level

Soc Classification level

2000 x 900 x 600 cabinet

S B1 -0 SB1 -0 S B1- 0 S B1 -0 SB 1-0 S B1 -0 S B1 -0 SB 1- 0 B1

S B2 -1 SB2 -1 S B2- 1 S B2 -1 SB 2-1 S B2 -1 S B2 -1 SB 2- 1 S B2 -1 S B 2-1 SB 2- 1

E TPT E TPT ET PT ET PT E TPT ET PT E T P- A ET P- A

GSW2KB GTIC ETC ETC

GT IC0 or GTIC 1 ETC 0o r ETC2 ET C1 or ET C3

SB1 -0 S B1- 0 S B1 -0 S B1- 0 S B1 -0 SB 1- 0 S B1 -0 SB1 -0 SB1 SB 2 SB 2 SB2 SB 2 SB 2 SB 2

SB2 -0 S B2- 0 S B2 -0 S B2- 0 S B2 -0 SB 2- 0 S B2 -0 SB2 -0 S B 2-0 SB 2 -0 SB 2 -0 S B 2-0

OPR O PR O PR OP R ETH S B3 ETH S B3 ETH SB 3 ETH SB 3 E H

SB3 -1 S B3- 1 S B3 -1 S B3- 1 S B3 -1 SB 3- 1 S B3 -1 SB3 -1 Tx T x T x Tx

BCSU 1 BCSU 2 BCSU 3

BCSU 4 BCSU 5 BCSU 6

6+6 ETPs, 4 ETP-As

Fan tray Fan tray Fan tray Fan tray

BCSU BCSU BCSU BCSU BCSU

BCSU BCSU BCSU BCSU BCSU BCSU

2000 x 900 x 600 (300) 2000 x 900 x 600

SWU-0 SWU-1 0 1 0 1 SWU-2 SWU-3

SWU-6 SWU-7 SWU-4 SWU-5

Soc Classification level

PEP Eth link

• ETPSIG-m: O&M / management plane interface between a GW BCSU and an ETPx

• EL0 – External Link 0: Abis CS/PS u-planes, e2e measurement packets

Soc Classification level

as a Gateway (GW role IUA

nominated via D2 -MML UDP

• ETP unit sends DHCPDISCOVER message in startup of ETP

Soc Classification level

• For telecom ETPT-0-0 ETPT-0-1 ETPE-n-0 ETPE-n-1

Soc Classification level

Soc Classification level

Soc Classification level

Packet Abis over

SWU-0 SWU-1 SWU-n SWU-n+1

Packet Abis over

Soc Classification level

Soc Classification level

Soc Classification level

Abis CS u-plane <-> Ater TRAU Frames

RTP Payload Payload type+PCU frame

Compr. RTP header AoIP packets PEP id Payload type+PCU frame

Ater EEP PCU2-E PCU2-D

Soc Classification level

OMUSIG TRXSIG OMUSIG TRXSIG

Packet Abis over TDM

Soc Classification level