Packet Abis Over IP Integration - Idea

Packet Abis over IP/Ethernet
1 © Nokia Siemens Networks RN2822AEN30GLA0

Overview
• This fully integrated feature enables the transport of Abis information using native IP
over Packet Switched Networks (via Ethernet) which removes the traditional TDM
Abis structure.
• Further, Abis Optimization through the removal of silence and idle frames, multiplexing
and bandwidth sharing for the CS-Userplane; PS-Userplane; Control-Plane and
Management-Plane achieves significant bandwidth savings.
• The Packet Abis U-Plane is transported over UDP/IP and the C-Plane/M-Plane is
transported over SCTP/IP.
• OPEX savings due to the more cost effective physical media (Ethernet) and the
simplified operation and maintenance of the network that can then be derived
Abis*
p-RTP/UDP/IP BSC
Eth Ethernet PSN Eth
E TP
Ref. SFS Packet Abis overview, S. Krafft / L. Marnoni,

BSS21231, version 1.0.1, December 2008

Packet Abis over IP/Ethernet/TDM
Functional Description - Inter working scenarios
Packet Abis with legacy Abis and legacy Ater
• The BSC is capable of terminating all kinds of Abis interfaces at the same time. In case of legacy
Ater interface, the A interface can be either the legacy A interface or A over IP with the
Transcoder(TC) in the base station subsystem (BSS).
• This type of connectivity is used for Abis optimization.

Functional Description - Inter working scenarios
Packet Abis with AoIP with the TC in Media Gateway (MGW)
• Packet Abis works with the transcoder that is located in multi media gateway through the A
over IP interface. The A over IP interface facilitates the packet transport from the BSS
towards MSS.
• The ETP unit is the termination point for the A over IP interface towards the BSC.

Functional Description - BSC3i Architecture for Packet Abis, ETP (1/6)
• A new interface unit, Exchange Terminal for Packet Transport

(ETP), terminates Packet Abis U-plane in the BSC.
• There are two HW variants of the ETP:
– ETP terminates Packet Abis, and A over IP where the TC is in the MGW
– ETP-A (Exchange Terminal for Packet Transport over A-interface)
terminates A over IP where the TC is in the BSS
▪ The ETP-A is located either in the TCSM3i or BSC (depending on the A over IP
scenario).

Functional Description
There are four new functional units, which will include ETP or ETP-A plug-in unit:
• ETPE : Exchange Terminal for Packet Abis over Ethernet (PAoEth).
The Ethernet links from the Packet Abis BTS are terminated on ETP-E interface unit.
• ETPT : Exchange Terminal for Packet Abis over TDM (PAoTDM).
The TDM links from Packet Abis BTS are terminated on the ETP-T through a ETS2
unit.
• ETPA: Exchange Terminal for A over IP with TC in MGW (AoIP (TC in MGW)).
Ethernet links from MGW are terminated on the ETPA when TC is located in MGW.
• ETPC: Exchange Terminal for A over IP with TC in BSS (AoIP (TC in BSS)).
Ethernet links from MGW are terminated on ETPC when the TC is located in the BSS.
The TC can be co-located in the BSC or remotely located in the Transcoder
Submultiplexer (TCSM) unit.

• The same ETP

hardware variant is
used both in Packet
Abis over Ethernet
and Packet Abis over
TDM.
• One ETP card
converts up to 8192
CS channels from
Ater/TRAU to Packet
Abis packets and
vice versa.

User Interface - MML commands
The following MML commands are used to handle the feature “Packet Abis over
IP/Ethernet ”:
• The EEY command for modifying the packet transport parameters
• The ESK and ESH commands for handling the ETP-PCU connections:
• The ESL command to display the Packet Abis configuration.
• The ESJ command to modify the ETP parameters.
• The following MML commands are modified to handle the feature:
• The EFC, EFM, and EFO commands for handling the BCF parameters.
• The EEO command for displaying the BSC parameters.
• The TPM, TPS, TPE and TPI commands for handling the measurement
characteristics.
• The EQV, EQO, and EQC commands for handling the BTS parameters.

Interrogation / Creation of Packet Abis over IP/Ethernet
INTERROGATION / CREATION
Packet Abis over

TDM
TDM
BTS
Packet Abis over
TDM ETPT
Ethernet
PSN ETH ETPE

ETH
BTS TDM
BSC
Legacy
Abis
TDM
BTS

Activation and Configuring (1/15)
Prerequisites
• To operate the feature, the license for the feature BSS21454: “Packet Abis
over Ethernet” must be installed
• The new ETP plug-in unit is available and commissioned.
• The PCU is available and configured to use Packet Abis.
• The ETP-PCU connection is available.
• Flexi EDGE BTS with SW EX 4.0 or Flexi Multiradio BTS with SW EX4.1.
• Configure ESB24-D LAN devices(using commands ZWT, ZUS, ZW6,
ZYF). Three new LAN topologies, T8, T9, T10 defined
• FIYA/ FIQA/ FIYB/ FIQB module required by the BTS are available.
* RG20 Operating Documentation: BSC Site Connectivity Guidelines

Packet Abis over IP/Ethernet – GPRS

GPRS Configuration
• Check PCU configuration.

• PCU2-D or PCU2-E must be created to the PCUPAB function.
• For PCU2_E PEP interface create PEP Eth link (VLAN).
• PCU configuration can be checked with following command:
• ZWTI:BCSU,<unit_index>;
• If PCU configurations need to change use
• S15 BSCPCU HW implementation for PS traffic

GPRS Configuration
ETP- PCU connection.

ZESK:ETPE,<pair number>:BCSU,<index>:PCU,<index>:;
Note :This is required for both PCU2_E and PCU2_D cards
E B
T C
P ZESK
P S
C
E U U


BCF Creation Steps for Packet Abis over Ethernet

Start
Check/Active the required licenses Create static routes
Create the ETP network interfaces IL0&IL1 & Activate ETPE to WO-EX Create HOC / POC for BTSs
bond them
Create SCTP associations for OMUSIG & TRXSIG Create TRXs for BTSs
Assign IP addresses to the bond
Set IP addresses to the associations Unlock TRXs

Configure the ETPSIG interface
Create D-channels for OMUSIG & TRXSIG Unlock BTSs

Configure the ETP-PCU connection (PEP)
Activate associations Unlock BCF

Configure IP for EEP links
Create the BCF object End

Configure IP for PEP links
Attach SW to BCF
Create network interfaces (EL0) in BCSU
Activate the BCF SW build
Create IP addresses for network interfaces
(EL0)
Create BTSs

Licenses

ETP Network Interfaces and IP’s

>ZQRI:ETPE;
BSC3i BSC24 2010-11-22 15:18:55
INTERROGATING NETWORK INTERFACE DATA
UNIT ADMIN ADDR

INTERFACE STATE MTU ATTR IP ADDRESS
------------ ----- ----- -------- ---------------------------------------------
ETPE-1-0
BOND0 UP 1500 PVIDM (10.0.1.11/26)
->IL0 IL1 LVC (10.0.1.26/26)
EL0 UP 1500 L (10.16.155.101/28)

IL0 UP 1500
IL1 UP 1500
IN0 UP 1500 L (10.0.3.26/24)
VLAN21 UP 1500 LVI (10.0.1.66/26)
EEP
->BOND0 21 0/0
VLAN22 UP 1500 LVI (10.0.2.2/24)
PEP
->BOND0 22 0/0
COMMAND EXECUTED

ETPSIG interfaces – Management and Control
< D2I:::ETPE,;
LOADING PROGRAM VERSION 1.10-0
BSC3i BSC24 2010-11-22 17:29:02
INTERROGATE IUA MESSAGING CONFIGURATION
Management
ETP UNIT CONN-TYPE SIG-TYPE GW UNIT D-CHN
--------- --------- -------- -------- -----
ETPE-1-0 NORMAL ETPSIG-M BCSU-0 64
BCSU-0 IP ADDR: 10.0.1.2
ETPE-1-0 IP ADDR: 10.0.1.11 Control
ETPE-1-0 NORMAL ETPSIG-C BCSU-0 65
ETPE-1-0 IP ADDR: 10.0.1.26 Control
ETPE-1-0 IP ADDR: 10.0.1.26
COMMAND EXECUTED

ETPSIG interfaces – Management and Control

< D2I;
BSC3i BSC24 2010-11-22 15:17:25
INTERROGATE IUA MESSAGING CONFIGURATION
ETP UNIT CONN-TYPE SIG-TYPE GW UNIT D-CHN

--------- --------- -------- -------- -----
ETPE-1-0 NORMAL ETPSIG-M BCSU-0 64
ETPE-1-0 IP ADDR: 10.0.1.11
ETPE-1-0 IP ADDR: 10.0.1.26
ETPE-1-0 IP ADDR: 10.0.1.26
ETPA-0 NORMAL ETPSIG-M BCSU-0 67
ETPA-0 IP ADDR: 10.0.1.21
ETPA-0 NORMAL ETPSIG-C BCSU-0 68
ETPA-0 IP ADDR: 10.0.1.31
COMMAND EXECUTED

ETP Network Interfaces and IP’s

QRN:ETPE,1,0::
/* IDENTIFY NETWORK INTERFACE NAME: QRN:ETPE,1,0::BOND0:"10.0.1.11",26,
BONDING: BOND0 /* SPECIFY IP ADDRESS TYPE

ETHERNET: EL0
ETHERNET: IL0 IL1 L ... LOGICAL IP ADDRESS
ETHERNET: IN0 P ... PHYSICAL IP ADDRESS
VLAN: VLAN21-VLAN22
DEFAULT IS LOGICAL IP ADDRESS */
*/
QRN:ETPE,1,0::BOND0 QRN:ETPE,1,0::BOND0:"10.0.1.11",26,P
/* SPECIFY THE IP ADDRESS:

/* SPECIFY IP ADDRESS ATTRIBUTE(S):
IPV4: #.#.#.# IN QUOTATION MARKS.
IPV6: #:#:#:#:#:#:#:# IN QUOTATION MARKS. V ... VIRTUAL IP ADDRESS
I ... INTERNAL IP ADDRESS
*/ D ... DYNAMIC IP ADDRESS FOR DHCP CLIENT
M ... ETPSIG-M IP ADDRESS
QRN:ETPE,1,0::BOND0:"10.0.1.11" C ... ETPSIG-C IP ADDRESS
/* SPECIFY NETMASK LENGTH: DEFAULT IS ATTRIBUTE NOT DEFINED */
DECIMAL 4 ... 32 QRN:ETPE,1,0::BOND0:"10.0.1.11",26,P,IDM
DEFAULT IS 8 */

Example from: BSC3i1000
QRI:;
BSC3i BSC24 2010-11-23
(1) BSC
10:04:48
Network Interfaces
INTERROGATING NETWORK INTERFACE DATA
andEL0 IP’s UP
BCSU-0
1500 LIMC 10.0.1.2/26
EL1 UP 1500 LIMC (10.0.1.2/26)

UNIT ADMIN ADDR
INTERFACE STATE MTU ATTR IP ADDRESS VLAN30 UP 1500 L 10.16.155.21/28
------------ ----- ----- --------
----------------------- ->EL0 30 0/0
OMU
EL0 UP 1500 PIM 10.0.1.8/26 VLAN31 UP 1500 L 10.16.155.37/28
EL1 UP 1500 PIM (10.0.1.8/26) ->EL1 31 0/0
VLAN1000 UP 1500 P 10.16.155.4/28 VLAN410 UP 1500 L 10.16.155.69/28
->EL0 10 0/0 ->EL0 41 0/0
VLAN1001 UP 1500 P (10.16.155.4/28) VLAN411 UP 1500 L (10.16.155.69/28)
->EL1 10 0/0 ->EL1 41 0/0
MCMU-0
EL0 UP 1500 LI (10.0.0.1/28)
LI (10.0.0.17/28)
EL1 UP 1500 LI (10.0.0.1/28)
LI (10.0.0.33/28)
EMB0 UP 1500 LI (10.0.0.49/28)
EMB1 UP 1500 LI (10.0.0.65/28)
MCMU-1
EL0 UP 1500 LI 10.0.0.1/28 RG20 Operating Documentation: BSC Site Connectivity Guidelines
LI 10.0.0.17/28
EL1 UP 1500 LI (10.0.0.1/28)

Packet Abis over IP/Ethernet BCSU-1
EL0 UP 1500
EL1 UP 1500
BCSU-0 -PCU2D-3
IFETH0 UP 1500 L 10.16.155.136/25 VLAN30 UP 1500
(2) BSC
IFETH1 Network
UP 1500 L Interfaces and IP’s
(10.16.155.136/25) ->EL0 30 0/0
VLAN31 UP 1500
BCSU-0 -PCU2D-4
IFETH0 UP 1500 L 10.16.155.137/25 ->EL1 31 0/0
IFETH1 UP 1500 L (10.16.155.137/25) VLAN410 UP 1500
->EL0 41 0/0
BCSU-0 -PCU2D-5
IFETH0 UP 1500 L 10.16.155.138/25 VLAN411 UP 1500
IFETH1 UP 1500 L (10.16.155.138/25) ->EL1 41 0/0
BCSU-0 -PCU2D-6 BCSU-1 -PCU2D-3

IFETH0 UP 1500 L 10.16.155.139/25 IFETH0 UP 1500
IFETH1 UP 1500 L (10.16.155.139/25) IFETH1 UP 1500
BCSU-0 -PCU2E-12 BCSU-1 -PCU2D-4

IFETH0 UP 1500 L 10.16.155.144/25 IFETH0 UP 1500
IFETH1 UP 1500 L (10.16.155.144/25) IFETH1 UP 1500
VLAN22 UP 1500 LI 10.0.2.16/24

BCSU-1 -PCU2D-5
PEP IFETH0 UP 1500
->IFETH0 22 0/0 IFETH1 UP 1500
BCSU-1 -PCU2D-6
IFETH0 UP 1500
IFETH1 UP 1500
RG20 Operating Documentation: BSC Site Connectivity Guidelines BCSU-1 -PCU2E-12

IFETH0 UP 1500
BCSU-2
EL0 UP 1500 LIMC 10.0.1.3/26
EL1 UP 1500 LIMC (10.0.1.3/26) ETPA-0
BOND0 UP 1500 LDM (10.0.1.21/26)
VLAN30 UP 1500 L 10.16.155.22/28
->IL0 IL1 LC (10.0.1.31/26)
(3)
->EL0BSC30 Network
0/0 Interfaces and IP’s
VLAN31 UP 1500 L 10.16.155.38/28
EL0 UP 1500 L (10.16.155.105/28)
->EL1 31 0/0
IL0 UP 1500
VLAN410 UP 1500 L 10.16.155.70/28
IL1 UP 1500
->EL0 41 0/0
VLAN21 UP 1500 LVI (10.0.1.71/26)
VLAN411 UP 1500 L (10.16.155.70/28)
EEP
->EL1 41 0/0
->BOND0 21 0/0
BCSU-2 -PCU2D-3
IFETH0 UP 1500 L 10.16.155.140/25 ETPE-1-0
BOND0 UP 1500 PVIDM (10.0.1.11/26)
IFETH1 UP 1500 L (10.16.155.140/25)
->IL0 IL1 LVC (10.0.1.26/26)
BCSU-2 -PCU2D-4
IFETH0 UP 1500 L 10.16.155.141/25
EL0 UP 1500 L (10.16.155.101/28)
IFETH1 UP 1500 L (10.16.155.141/25)
IL0 UP 1500
IL1 UP 1500
BCSU-2 -PCU2D-5
IFETH0 UP 1500 L 10.16.155.142/25 IN0 UP 1500 L (10.0.3.26/24)
IFETH1 UP 1500 L (10.16.155.142/25) VLAN21 UP 1500 LVI (10.0.1.66/26)
EEP
BCSU-2 -PCU2D-6
IFETH0 UP 1500 L 10.16.155.143/25 ->BOND0 21 0/0
IFETH1 UP 1500 L (10.16.155.143/25) VLAN22 UP Operating
RG20 1500 Documentation:
LVI (10.0.2.2/24)
BSC Site Connectivity Guidelines
PEP
BCSU-2 -PCU2E-12
IFETH0 UP 1500 L 10.16.155.145/25 ->BOND0 22 0/0
IFETH1 UP 1500 L (10.16.155.145/25)
SCTP Associations
• SCTP Associations created to enable OMUSIG & TRXSIG

connectivity between the BCSU and BCF
Steps:
1. Create the association with ZOYX
2. Allocate IP addresses and port numbers to each association using
ZOYP
3. Create D-channels for each OMUSIG & TRXSIG using ZDWP
4. Activate the associations using ZOYS
4.
1.
B0001 (d.e.f.10)
(a.b.c.69) 3. OMUSIG BCF
BCSU
2.
SCTP Associations

D- Channels for OMUSIG and TRXSIG

< ZDW?
LOADING PROGRAM VERSION 1.12-0
BSC3i BSC24 2010-11-23 15:24:16
D-CHANNEL DATA HANDLING COMMANDS
? ..... DISPLAY MENU

C: ..... CREATE D-CHANNEL
D: ..... DELETE D-CHANNEL
I: ..... INTERROGATE D-CHANNEL DATA
E: ..... MODIFY D-CHANNEL WORKING STATE
P: ..... CREATE ABIS D-CHANNEL
Q: ..... INTERROGATE ABIS D-CHANNEL DATA
Z; ..... RETURN TO MAIN LEVEL
D-CHANNEL DATA HANDLING COMMAND <DW_>

<

D- Channels for OMUSIG and TRXSIG

TRXs with Packet Abis over IP/Ethernet

ERO:BTS=1200,;
ADM.STATE OP.STATE
--------------------------------------
BCF-1200 UNLOCKED WO
SEG-1200 SYVELAB1
BSC3i BSC24 2010-11-23 11:55:05 BTS-1200 SYVELAB1 UNLOCKED WO
TRX-002 EDGE UNLOCKED WO
TRANSCEIVER DATA BCSU-0
ADM.STATE OP.STATE GTRX Y (GPRS)
-------------------------------------- ETRX N HRS Y PREF N
BCF-1200 UNLOCKED WO DFCA N
SEG-1200 SYVELAB1
BTS-1200 SYVELAB1 UNLOCKED WO FREQ 873 TSC 3 FRT 0 (REGULAR) LEV N (NOT
TRX-001 EDGE UNLOCKED WO USED)
BCSU-0
DAL N (NOT USED) LEVD N (NOT
GTRX Y (GPRS) USED)
ETRX N HRS Y PREF P
DFCA N
OSC 3 (SUPPORTED, NO EGPRS) TRX STARTING MODE 0 ( EGPRS)
FREQ 630 TSC 3 FRT 0 (REGULAR) LEV N (NOT RFHA Y
USED)
D-CH TELECOM LINK SET 30 T1202
DAL N (NOT USED) LEVD N (NOT
USED) RTSL PCM-TSL SUB_TSL TYPE I.LEV ADM.STATE OP.STATE CH.STATUS
---------------------------------------------------------------------------
---
OSC 3 (SUPPORTED, NO EGPRS) TRX STARTING MODE 0 ( EGPRS) 0 - - TCHF 0 UNLOCKED WO ID
RFHA Y
1 - - TCHF 0 UNLOCKED WO ID
D-CH TELECOM LINK SET 29 T1201
RTSL PCM-TSL SUB_TSL TYPE I.LEV ADM.STATE OP.STATE CH.STATUS
--------------------------------------------------------------------------- 3 - - TCHF 0 UNLOCKED WO ID
---
0 - - MBCCHC - UNLOCKED WO 4 - - TCHF 0 UNLOCKED WO ID
1 - - TCHF 0 UNLOCKED WO ID 5 - - TCHF 0 UNLOCKED WO ID
TRANSCEIVER HAS NO INTERFERING CELLS
COMMAND EXECUTED
TRANSCEIVER DATA HANDLING COMMAND <ER_>
7 - - TCHF 0 UNLOCKED WO GP
28 © Nokia
TRANSCEIVER HAS NOSiemens Networks CELLS
INTERFERING RN2822AEN30GLA0
RNW Configuration with Packet Abis over IP/Ethernet
< EEI:BCF=1200:;
BSC3i BSC24 2010-11-23 11:59:46

RADIO NETWORK CONFIGURATION IN BSC:
E P B
F T R C D-CHANNEL BUSY
AD OP R ET- BCCH/CBCH/ R E S O&M LINK HR FR
LAC CI HOP ST STATE FREQ T PCM ERACH X F U NAME ST DHR /GP
===================== == ====== ==== == ==== =========== = = == ===== == === ===
BCF-1200 FLEXI EDGE U WO 0 O1201 WO

00024 24121 BTS-1200 U WO 0 0
SYVELAB1 -/- 0 1
TRX-001 U WO 630 0 - MBCCHC P 0
TRX-002 U WO 873 0 - 0
COMMAND EXECUTED

BCF Creation Steps for Packet Abis over Ethernet

Start
Check/Active the required licenses Create static routes Create HOC / POC for BTSs
Create the ETP network interfaces IL0&IL1 & Activate ETPE to WO-EX Create TRXs for BTSs
bond them
Create SCTP associations for OMUSIG & TRXSIG Unlock TRXs
Assign IP addresses to the bond
Set IP addresses to the associations Unlock BTSs
Configure the ETPSIG interface
Create D-channels for OMUSIG & TRXSIG Unlock BCF

Activate associations End
Configure IP for EEP links
Create the BCF object
Configure IP for PEP links
Attach SW to BCF
Create network interfaces (EL0) in BCSU
Create IP addresses for network

interfaces(EL0) Create BTSs

Activation and Configuring
1. Check the license state of the features with the command W7I
ZW7I:FEA,FULL:FEA=1533;
2. If the license is not active, enter the following command to activate the license
ZE7M:FEA=<featurecode>:ON;
3. Create the ETP network interfaces (IL0 and IL1) and BOND them with command ZQRA
ZQRA:ETPE,0,0::IL0::UP;
ZQRA:ETPE,0,0::IL1::UP;
ZQRA:ETPE,0,0::BOND0,IL0,IL1,::UP:;
4. Assign IP addresses to the BOND created using command ZQRN
ZQRN:ETPE,0,0::BOND0:"10.0.1.14",26,P,IDM:;
ZQRN:ETPE,0,0::BOND0:"10.0.1.30",26,L,ICV::;
5. Configure the ETPSIG interface with command ZD2C (ETPSIGc creation for all BCSUs)
ZD2C:C,NOR::BCSU,0:ETPE,0,0::;
6. Create ETP-PCU connection (PEP) link with command ZESK
ZESK:ETPE,4:BCSU,2:PCU,3;

7. Configure IP for EEP link using ZQRA,ZQRN and ZQRP commands
ZQRA:ETPE,0,0::VLAN21,21,BOND0,;
ZQRN:ETPE,0,0::VLAN21,:"10.0.1.65",26,L,I::;
ZQRP:ETPE,0,0::VLAN21:"10.0.1.65":TAG,"EEP":;
8. Configure IP for PEP link using ZQRA,ZQRN and ZQRP commands
ZQRA:ETPE,0,0::VLAN22,22,BOND0,;
ZQRN:ETPE,0,0::VLAN22,:"10.0.2.1",24,L,I::;
ZQRP:ETPE,0,0::VLAN22:"10.0.2.1":TAG,"PEP":;
9. Create the network interfaces (EL0) to BCSU with ZQRA command
ZQRA:UNIT IDENTIFICATION:PIU IDENTIFICATION:INTERFACE NAME:MAXIMUM
TRANSMISSION UNIT:INTERFACE ADMINISTRATIVE STATE:;
10.Create the IP addresses to network interfaces EL0 with command ZQRN
ZQRN: UNIT IDENTIFICATION:PIU IDENTIFICATION: NETWORK INTERFACE
IDENTIFICATION: IP ADDRESS IDENTIFICATION:DESTINATION IP ADDRESS;
11.Create static route using the command ZQKC
ZQKC:UNIT IDENTIFICATION:PIU IDENTIFICATION:DESTINATION IPADDRESS,
NETMASK:GATEWAY IP ADDRESS:ROUTE TYPE;
12.Bring up ETPE to working state using the following commands
ZUSC:ETPE,0,0:SE;
ZUSC:ETPE,0,0:TE;
ZUSC:ETPE,0,0:WO;

13.Create SCTP associations with OYX command for OMUSIG & TRXSIG
ZOYX:TEST:IUA:S:BCSU,0:Packet Abis Fast;
14.Set IP address to the association
ZOYP:IUA:KUDO:"10.125.113.99",,49180:"10.125.117.21",24,,,49180:;
The source IP address is the same as was given to the BCSU unit interface with
QRN command. Destination address and port are the BTS M-plane address (for OMUSIG),
C/U-plane address (for TRX sig). Source and destination ports should be the same.
This command has to be repeated for each OMUSIG and TRXSIG.
15.Created SCTP association can be checked
ZOYV:IUA:NAME=KUDO:A:;
16.Create D-channels with DWP command for OMUSIG & TRXSIG
ZDWP:KUDO:BCSU,1:62,1:KUDO,0:;
17.Association activation
ZOYS:<Association name>;
D-channel activation is not needed, once the association is activated the D-channel
becomes active
18.Create BCF
ZEFC:311,E,,2:DNAME=O311,:::::ETPGID=0,BCUIP=10.125.113.32,SMCUP=24,BMIP=
10.15.113.32,SMMP=24,::;
New Packet Abis parameters are shown to user if Packet Abis over TDM or Packet
Abis over Ethernet license is in ON or CONF state

19. Attach software package to BCF

ZEWA:311:NW:EX4_BL063:;
20. Activate the BCF with the software build
ZEWV:311:NW:;
21. Output the BCF Software Attached
ZEWO:311:;
22. Create BTS
ZEQC:BCF=20,BTS=1,SEGNAME=BIGCENTRUM020,NAME=CENTRUM1:CI=12,BAND
=900,CHW=0:NCC=2,BCC=4:MCC=111,MNC=22,LAC=34567:HOP=RF,UHOP=N,HSN1=
3,HSN2=1:GENA=Y,PSEI=13;
23. Create HO
ZEHC:BTS=311,:;
24. Create POC
ZEUC:BTS=311,:;
25. Create TRXs
ZERC:BTS=1,TRX=1::FREQ=99,TSC=4,PCMTSL=21-
5:DNBR=23:CH0=MBCCHC,CH1=NOTUSED,CH2=CCCHE;
The parameters AC,DAP, PCMTSL, SIGN, BR, CL can not be given if packet abis is
in use
26. Unlock all created objects (TRX, BTS, BCF)
ZERS:<BCF identification>,<transceiver identification>:U;
ZEQS:<BTS identification>:U;
ZEFS:<BCF identification>:U;

Packet Abis over TDM

Overview
• This fully integrated feature enables the transport of Abis information using native IP
over Time Division Multiplexed (TDM) Networks, which removes the traditional TDM
Abis structure, where the static relationship between the Air and the Abis Interfaces is
eliminated.
• The Packet Abis over TDM is realized by transporting:
• U-Plane over UDP/IP/MLPPP
• C-Plane/M-Plane over SCTP/IP/MLPPP.
• Benefits of this feature is operators can utilize the existing installed TDM
Infrastructure, easing the introduction of the Packet Abis solution
Abis*
p-RTP/UDP/IP
ML-PPP/HDLC BSC
TDM TDM TDM SDH
ETP
Ref. SFS Packet Abis overview, S. Krafft / L. Marnoni,

BSS21231, version 1.0.1, December 2008

Overview
• The Packet Abis over TDM solution removes the traditional TDM Abis structure, where
the static relationship between the Air and the Abis Interfaces is eliminated.
• Further, Abis Optimization is achieved by not sending empty packets (unused, silence),
multiplexing and bandwidth sharing.
• The Packet Abis U-Plane is transported over UDP/IP/Multi Class PPP(MC-PPP)/Multi
Link PPP (ML-PPP) and the C-Plane/M-Plane is transported over SCTP/IP/MC-PPP/ML-
PPP.
• In Packet Abis over TDM the transport technology solution is still based on the TDM, but
Abis is packet based with the adoption of IP layer on top of ML/MC- PPP and HDLC
over TDM(E1/T1).
• At BSC side the E1/T1 Abis link is accomplished via channelized STM1/OC3 interface.

Benefits
• The Packet Abis solution removes the traditional TDM Abis structure, where the
static relationship between the Air and the Abis Interfaces is eliminated
• The operator is able to employ Packet Switched Networks in order to provide the
transport backhaul for the Abis traffic, by utilizing the existing installed TDM infrastructure,
easing the introduction of the Packet Abis solution.
• The benefits of Packet Abis solution can be made use of without introducing “Ethernet”.
• The savings achieved are much higher than the overhead by protocol headers introduced
by Packet Abis.
• Other benefits introduced by this features are :
 Cost reduction due to simplified operation.
▪ Very minimal configuration changes in Abis interface in case the Air interface is changed, for example
when a BTS is upgraded by adding new TRXs.
▪ All traffic share the same bandwidth and there is no EDAP configuration required.
▪ Easier expansion of the BTS to support OSC.
 Support for already identified transport enhancements, like A interface over IP, OSC, and paving
the way for future transport and telecom GSM/EDGE features such as EGPRS2.

Functional Description – Interworking Scenarios
Packet Abis over TDM and legacy Abis with legacy Ater
• The BSC is capable of terminating all kinds of Abis interfaces at the same time.
• In case of legacy Ater interface, the A interface can be either the legacy A interface or A
over IP with the Transcoder (TC) in the Base Station Subsystem (BSS).
• This type of connectivity is used for Abis optimization, especially in TDM networks.
• New TRXs could be rolled out without increasing the number of required TDM links.
• Also, within a single STM1/OC3 interface at BSC, Packet Abis over TDM and Legacy Abis
cannot be mixed. In this case, an SDH/OC3 add/drop multiplexer (ADM) is needed to
separate the traffic to different physical interfaces.

Functional Description – Interworking Scenarios
Packet Abis over TDM with AoIP with the TC in Media Gateway (MGW)
• The scenario shown here is the conversion of legacy Abis to AoIP (TC in MGW).
• In this scenario, the GSM codec is sent over the A-interface without transcoding.
Transcoder function resides completely on MGW.
• Legacy Abis traffic will only be possible to go to Ater interface in RG20.
• Packet Abis might either go to Ater or AoIP (TC in MGW) depending on the need and
configuration.
• Interworking between legacy Abis and A over IP (TC in MGW) is not supported in S15.

BSC • There are four new functional
ET units, which will include ETP
call or ETP-A plug-in unit:
Sn+pair Sn+pair specific • ETP Plug in unit:
GSWB CS – ETPE: Exchange
ETP
SET connection
ETP Terminal for Packet Abis
(STM-1/OC-3) ETS2
T
Sn+pair over Ethernet (PAoEth).
SET
ETP TD – ETPT: Exchange
ET M Terminal for Packet Abis
STMU ETPT
Ater over TDM (PAoTDM).
PS HotLink •
Sn+pair ETP-A Plug in unit:
only if
GigE – ETPA: Exchange
ETP PCU2-D is
in use Terminal for A over IP
ETP
with TC in MGW (AoIP
E
(TC in MGW)).
Semipermanent – ETPC: Exchange
PCU2-D PEP links Terminal for A over IP
with TC in BSS (AoIP
(TC in BSS)).
PCU2-E
Sn+group
BCSUs
ETP GigE
etpsig-m/c SWUs
ETPA A over IP
to ETPs
TC in
41 © Nokia Siemens Networks RN2822AEN30GLA0 MGW
Interrogation / Activation
Packet Abis over

TDM
TDM
BTS
Packet Abis over
TDM ETPT
Ethernet
PSN
ETH ETH ETPE
BTS TDM
BSC
Legacy
Abis
TDM
BTS

BCF modification from Legacy Abis to Packet Abis
Pre requisites
• License state of the feature PAoTDM or PAoETH should be ON or CONF.
• If default value is not suitable, then all BSC level packet abis parameters should be
modified.
• ETP should exist and is configured with the appropriate functional type to use.
• PCU exists and it must be empty (this is when ETP-PCU connection is not
available)
• PCU SW must support packet abis and PCU is configured to use Packet Abis.
• Number of PCUs connected to ETP should not exceed the maximum value.
• Flexi EDGFE BTS with SW EX 4.0 or Flexi Multiradio BTS with SW EX4.1.
• TheFIYA/ FIQA/ FIYB/ FIQB module required by BTS is available.

Licenses
W7I:FEA,:FEA=1380&1533&1673&1535&1555&1522&1753&899,:;
FlexiBSC BSC15 222917 2010-11-23 19:34:28
FEATURE INFORMATION:
FEATURE CODE FEATURE NAME

----------------------------------------
1533 Packet Abis over IP/Ethernet
1673 Packet Abis Sync. ToP IEEE1588v2
1535 Packet Abis over TDM
1555 Packet Abis Delay Measurement
1522 A over IP
1753 A over IP, Transcoder in MGW
899 L-NWP -- IUA
COMMAND EXECUTED

BCF Creation Steps for Packet Abis over TDM

Start
Check/Active the required licenses Create static routes Create BTSs
Create the ETP network interfaces IL0&IL1 & Activate ETPT to WO-EX
bond them Create HOC / POC for BTSs
Create SCTP associations for OMUSIG & TRXSIG

Assign IP addresses to the bond Create TRXs for BTSs
Set IP addresses to the associations
Configure the ETPSIG interface Open Abis HDLC links
Create D-channels for OMUSIG & TRXSIG
Unlock TRXs
Activate associations
Configure IP for EEP links Unlock BTSs
Create Abis HDLC links
Configure IP for PEP links Unlock BCF
Create the BCF object

Create network interfaces (EL0) in BCSU End
Attach SW to BCF
Create IP addresses for interfaces(EL0)


BCF Modification

1 If GPRS is enabled, it must be disabled

ZEQV:<BTS identification>:<GPRS enabled>;
Example
ZEQV:BTS=21:GENA=N;
2 If the connection between ETP and PCU does not exist, establish it
ZESK:<ETP type>,<ETP group id>:<Unit>,<Unit Index>:Plugin
Unit>,<Plugin Unit Index>;
Example
ZESK:ETPE,4:BCSU,2:PCU,3;
3 Download SCF file for the BTS using EEE command
ZEEE:<Configuration identification>,<operation type>:<Activation
method>,<Connection type>:;
Example
ZEEE:22,ACT:10,FTP:;

4 Create the OMUSIG and TRXSIG

Create the OMUSIG and TRXSIG
Activating and Configuring the Packet Abis”
5 Lock the BCF
ZEFS:<BCF identification>:L;
Example
ZEFS:128:L;
6 Modify BCF to use Packet Abis over TDM
ZEFM:<BCF identification>:<Abis Interface Connection
Type>:<ETPGID>;
Example
ZEFM:128:AICT=2:ETPGID=12;
7 Lock the TRXs
ZERS:<BTS identification>,<transceiver identification>:L;
Example
ZEFS:BTS=40,TRX=2:L;

8 Create TRXs to use Packet Abis TRX links

ZERC:BTS=1,TRX=1::FREQ=99,TSC=4:DNBR=23:CH0=MBCCHC,
CH1=NOTUSED, CH2=CCCHE;
 The parameters AC,DAP, PCMTSL, SIGN, BR, CL can not be given if packet abis is in
use
9 Unlock all created objects
ZERS:<BTS identification>,<transceiver identification>:U;
ZEFS:<BTS identification>,<transceiver identification>:U;
End

OMUSIG/TRXSIG Configuration
OMUSIG/TRXSIG:
• Uses VLAN 20 (ETPSIG-I)
• Untagged output from BCSU
• Route from BCSU to ETPE BOND0 (ETPSIG-c address)
ETPT
VLAN20 BOND0
(U)
SWU0 SWU6
(T) Route
I BCSU-ETPT
BCSU L
0/1 (U)
Activating the Packet Abis synchronization and Security
Pre requisites
• The licenses for the features BSS21454: “Packet Abis over Ethernet” , BSS21439: “
Packet Abis Sync. ToP IEEE1588v2”, BSS30450: “Packet Abis Synchronous
Ethernet” should be installed.
• ETP unit exists and is configured to support Packet Abis.
• PCU exists and ETP-PCU connection is established.
• An external security gateway exists for the BSC.
• Flexi EDGFE BTS with SW EX 4.0 or Flexi Multiradio BTS with SW EX4.1.
• The FIYB/ FIQB module required by BTS is available.

Activating the Packet Abis synchronization
1 Check the license status of the features
For Packet Abis over Ethernet:

For Packet Abis Synchronous Ethernet:


Activating the Packet Abis synchronization
2 Activate the licenses if needed

ZE7M:FEA=<feature code>:ON;
3 Lock the BCF using EFS command
ZEFS:<BCF identification>:L;
4 Enable SyncE feature
ZESJ:<ETP type>,<ETP group id>,<SyncE Mode>;
Example
ZESJ:ETPE,1,MAS;
5 Unlock the BCF
ZEFS:<BCF identification>:U;
7 Enable SSM functionality in the BSC
ZEEY:SSME=Y;
* Please consult and get detailed document from radio expert before implementing this feature in any
Live Network.

Packet Abis Over IP Integration - Idea

Uploaded by

Document Information

Original Description:

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 Over IP Integration - Idea

Uploaded by

Copyright:

Available Formats

Packet Abis over IP/Ethernet

1 © Nokia Siemens Networks RN2822AEN30GLA0

Ref. SFS Packet Abis overview, S. Krafft / L. Marnoni,

2 © Nokia Siemens Networks RN2822AEN30GLA0

3 © Nokia Siemens Networks RN2822AEN30GLA0

4 © Nokia Siemens Networks RN2822AEN30GLA0

• A new interface unit, Exchange Terminal for Packet Transport

5 © Nokia Siemens Networks RN2822AEN30GLA0

6 © Nokia Siemens Networks RN2822AEN30GLA0

• The same ETP

7 © Nokia Siemens Networks RN2822AEN30GLA0

8 © Nokia Siemens Networks RN2822AEN30GLA0

Packet Abis over

PSN ETH ETPE

9 © Nokia Siemens Networks RN2822AEN30GLA0

* RG20 Operating Documentation: BSC Site Connectivity Guidelines

10 © Nokia Siemens Networks RN2822AEN30GLA0

11 © Nokia Siemens Networks RN2822AEN30GLA0

• Check PCU configuration.

12 © Nokia Siemens Networks RN2822AEN30GLA0

ETP- PCU connection.

13 © Nokia Siemens Networks RN2822AEN30GLA0

14 © Nokia Siemens Networks RN2822AEN30GLA0

BCF Creation Steps for Packet Abis over Ethernet

Check/Active the required licenses Create static routes

Set IP addresses to the associations Unlock TRXs

Create D-channels for OMUSIG & TRXSIG Unlock BTSs

Activate associations Unlock BCF

Create the BCF object End

15 © Nokia Siemens Networks RN2822AEN30GLA0

16 © Nokia Siemens Networks RN2822AEN30GLA0

ETP Network Interfaces and IP’s

BSC3i BSC24 2010-11-22 15:18:55

INTERROGATING NETWORK INTERFACE DATA

UNIT ADMIN ADDR

EL0 UP 1500 L (10.16.155.101/28)

17 © Nokia Siemens Networks RN2822AEN30GLA0

ETPSIG interfaces – Management and Control

LOADING PROGRAM VERSION 1.10-0

BSC3i BSC24 2010-11-22 17:29:02

INTERROGATE IUA MESSAGING CONFIGURATION

18 © Nokia Siemens Networks RN2822AEN30GLA0

ETPSIG interfaces – Management and Control

BSC3i BSC24 2010-11-22 15:17:25

INTERROGATE IUA MESSAGING CONFIGURATION

ETP UNIT CONN-TYPE SIG-TYPE GW UNIT D-CHN

19 © Nokia Siemens Networks RN2822AEN30GLA0

ETP Network Interfaces and IP’s

/* IDENTIFY NETWORK INTERFACE NAME: QRN:ETPE,1,0::BOND0:"10.0.1.11",26,

BONDING: BOND0 /* SPECIFY IP ADDRESS TYPE

/* SPECIFY THE IP ADDRESS:

/* SPECIFY NETMASK LENGTH: DEFAULT IS ATTRIBUTE NOT DEFINED */

DECIMAL 4 ... 32 QRN:ETPE,1,0::BOND0:"10.0.1.11",26,P,IDM

20 © Nokia Siemens Networks RN2822AEN30GLA0

BSC3i BSC24 2010-11-23

EL1 UP 1500 LIMC (10.0.1.2/26)

EL1 UP 1500 LI (10.0.0.1/28)

EMB0 UP 1500 LI (10.0.0.49/28)

EMB1 UP 1500 LI (10.0.0.65/28)

EL1 UP 1500 LI (10.0.0.1/28)

IFETH1 UP 1500 L (10.16.155.137/25) VLAN410 UP 1500

IFETH1 UP 1500 L (10.16.155.138/25) ->EL1 41 0/0