Packet Abis BSC NE Configurations. ETPE_T IP Interfaces, Configuring BSC

5/20/2018 Packet Abis BSC NE Configurations. ETPE_T IP Interfaces, Configuring BSC

1/37

Soc Classification level

1 Nokia Siemens Networks Presentation / Author / 14.01.2010

BSS21231 Packet AbisBSS21440 Packet Abis over TDM

BSS21454 Packet Abis over IP/Ethernet

1.Packet Abis BSC NE configuration

2. ETPE/T IP interfaces3. Configuring the Packet Abis BSC

BSC S15 Feature Training

Trainer: Juha Toivonen


2/37



1. Packet Abis BSC NE configuration-Module Objective

After this module the reader: has an idea about the Packet Abis related BSC Network Element

configurations


3/37



PCU2-D

Overview of ETPE/T/A units in BSC

BSC

(STM-1/OC-3)

GSWB

A over IP

TC in MG

ETTDM

Ater

SWUs

ET

Dynamic Abis

PCU2-E

SET

SET

BCSUs

etpsig-m/c

to ETPs

Sn+pair

Sn+group

ETP

T

ETP

E

ETP

ETP

A

ETP-A

ETS2

STMU

ETP

ETP

T

ETP

GigE

GigE

Sn+pair

Sn+pair

Sn+pair

Plug-in units ETP Exchange Terminal for Packet

Transport

ETP-A Exchange Terminal for PacketTransport over A-interface

Functional units ETPT, Exchange Terminal for Packet

over TDM

ETPE, Exchange Terminal for Packetover Ethernet

ETPA, Exchange Terminal for PacketA-interface

Optical interface(s):

1000 Base-LX: Long haul, up to 5000 m SMF fiber

1000 Base-SX: Short haul, up to 550 m MMF fiber

Electrical interface(s):

1000 Base-T:

GigaBit Ethernet over two pairs Category 5 (orbetter) twisted-pair cable.

Small Form-factor Pluggables(SFP)

PS HotLinkonly if

PCU2-D is inuse

Packet Abis

Packet Abis

Semipermanent

PEP links

call specificCS

connection

Transmissionor equipment

protection


4/37


5/37



BSC3i 1000/2000, maximum ETPT, ETPE and ETPAamounts (DRAFT)

GTIC

ETC

ETC

ETC

ETC

ETC

ETC

GTIC

MCMU

MCMU OMU

BCSU

BCSU BCSU

BCSU

BCSU

LANU

LANU

CLAC

GSW2KB

GSW2KB

CLOC

BCSU

Fan tray Fan tray

BCSU BCSU

CLAC

Fan tray Fan tray

LANU

LANU

BCSU

BCSU

BCSU

Fan tray Fan tray Fan tray Fan tray

Cablingoption

BSC3i base cabinet Extension cabinet

2000 x 900 x 600 2000 x 900 x 600

(300)6+6 ETPs, 4 ETP-As


6/37



FTRB 0 (FTRB-A)

FTRB 2 (FTRB-A) FTRB 3 (FTRB-A)

FTRB 1 (FTRB-A)

PDFU 0PDFU-B

1

2

3

4

0

5

PDFU-B

PDFU 1

CLAC-B

CLAC1

CC3C-B

BCSU 7

0

0

0

0

0

4 8

6

4 8

8

GT4C-A GT4C-A

ETC 4 ETC 5

CC3C-BCC3C-B

BCSU 9 BCSU 10

CC3C-B

BCSU 8

CC3C-B

BCSU 6

3 6

3

BSCD

06

1

2

3

4

0

Optional c abling cabinet

LASWC-A

LANU3

LASWC-A

LANU2

GT4C-A GT4C-A

ETC 2 ETC 3

9

6

FRONT S IDE

FTRB 0 (FTRB-A)


FTRB 1 (FTRB-A)

1

0

CLOC-B

CLOC

BCSU 1 BCSU 2

S W10C -A S W10C -A

GSW2KB

0

GSW2KB

1

0

0

0

0 8

CC4C-A CC4C-A

BCSU 4 BCSU 5BCSU 3

CC3C-A

BCSU 0

3

BSCC

0 6

CM2C-A

OMU

84

84

0 63

MCMU1

MCMU0

2

3

4

5

GT6C-A

ETC0

GT6C-A

ETC1

GT4C-A

GTIC0

GT4C-A

GTIC1CL

AC-B

CLAC

LASWC-A

LANU

1

LASWC-A

LANU

0

CPRJ45-A CPGO

10

0 2 4 6 9

CPETS-E /CPETC-E /CPETS-G



CPETS-H /CPETS-F /CPETC-F

CPETS-E /CPETS -G /CPETC-E



CPETS-F /CPETS-H /CPETC-F

CC3C-A CC3C-A

CC3C-A CC3C-A CC3C-A

BSC3i 2000 (BSC3i 1000 part upgraded from BSC3i 660)

FRONT SIDE

FTRB 0 (FTRB-A)


FTRB 1 (FTRB-A)

1

0

CLOC-B

CLOC

BCSU 1 BC SU 2

S W10C -A S W10C -A

GSW2KB0

GSW2KB1

0

0

0

0 8

CC4C-A CC4C-A

BCSU 4 BC SU 5BCSU 3

BCSU 0

3

BSCC

0 6

CM2C-A

OMU

84

84

0 63

MCMU1

MCMU0

2

3

4

5

GT4C-A

GTIC0

GT4C-A

GTIC1CL

AC-B

CLAC

LASWC-A

LANU1

LASWC-A

LANU0

CPRJ45-A CPGO

10

0 4 6 9

CC3C-A

BCSU 6

CPETS-E / CPETC-E /CPETS-G

0

1

2

3

4

CPETS-E /CPETS-G /CPETC-E





upgraded Flexi BSC



BSC3i 2000 (BSC3i 1000 part upgraded from BSC3i 660;2 cabinets) to Flexi BSC (1 cabinet) upgrade

PDFU PDFU PDFU PDFU PDFU PDFU PDFU PDFU

Upgraded FlexiBSC will have two options for Packet Abis connectivity A second cabinet for the ETP units

DRAFT: in one cabinet configuration instead of the BCSU-6 an additional GTIC cartridge is installed

(NE design on-going)


7/37



Plug-in unit Exchange Terminal for PacketTransport, ETP

ETP plug-in unit provides DX200 BSC3i network element with Abis-over-Ethernetinterface and Abis-over-TDM interface towards IP BTSs. The PIU is responsiblefor IP processing, TRAU frame handling and TDM conversion for interfacing withthe BSC3i switching network (GSW).

ETP main component blocks: CN5860LP-600BG1521-CP OCTEON by Cavium Networks

16 cnMIPS processor cores @ 600MHz

Management Core has Linux OS (Cavium distribution, kernel 2.9) Fast path (u-plane) cores have OCTEON Simple Executive (thin data plane OS)

8 x TMS320TCI6486ZTZ625 (Tomahawk DSP) by TI 6 On-Chip TMS320C64x+ Megamodules (DSP Cores) @ 625MHz

All cores of DSPs run OSE compact kernel (OSEck)

Front End FPGA (field-programmable gate array), pcm mux FPGA, integrated ethernetswitch, Flash and RAM memories

ETP-A is otherwise similar as the ETP but the daughterboard has only two DSPblocks i.e. 2 x TMS320TCI6486ZTZ625 (Tomahawk DSP) by TI

ETP/ETP-A SW on the OMU Disk is a single image: GGNETPET GGNETPA GGNETPC

GGNETP* SW image contains a Boot loader, Linux kernel, SE-S image, FPGA bitstreams for Front End and PCM MUX FPGA, Applications for management coreand DSP images.


8/37



ADDMODxx plugs

BSC internal DHCP server identifies the ETPE/T/A unitsbased on information that ETP adds to a DHCPREQUEST

ETP reads the information: SlotID from backplane.

LocID (cabinet and cartridge information) from ADDMODxx plugs in

cabling positions of cartridge. ADDMODxx behind each ETP(-A) PIU are used to set unit usage/type.


9/37



Plug-in unit Packet Control Unit 2nd generation,variants D and E (PCU2-D, PCU2-E)

PCU2 plug-in unit can be used in various applications, which need DSPs.

The main application for PCU2 is to work as a packet control unit forGPRS/EDGE system. For Packet Abis new PCU2 SW modules are intoduced:

AQL_9PGX Dynamic load list for PCU2-D with Packet Abis SW AQL_EPGX Dynamic load list for PCU2-E with Packet Abis SW IGWMPPQD PQII main module for PCU2-D with Packet Abis SW

IGWMPDSD DSP main module for PCU2-D with Packet Abis SW IGWMPPQE PQIII main module for PCU2-E with Packet Abis SW IGWMPDSE DSP main module for PCU2-E with Packet Abis SW

Separate SW package for legacy PCU2 and Packet Abis PCU2 meansthat the PCU2s in different Abis mode must have a dedicated track (plug-in unit slot) in BCSU. DX platform does not support changing of the PCU2SW during BCSU switchover.

PCUs in the same pool (PCU pooling feature) have to be in the same Abismode: legacy or Packet.

Theres four PCU pool types: legacy Abis terrestrial, legacy Abis satellite,Packet Abis terrestrial, Packet Abis satellite


10/37



Plug-in unit Exchange Terminal for 2xSTM-1/OC-3,ETS2

ETS2 plug-in unit is an STM-1/OC-3 Terminal Multiplexer forDX 200 based network elements.

ETS2 has two STM-1/OC-3 optical interfaces and isresponsible for framing, mapping and multiplexing

of two times sixty-three 2.048 Mbit/s tributaries into SDH STM-1 frame

and vice versa. of two times eighty-four 1.544 Mbit/s tributaries into SONET OC-3 STS-

3 frame and vice versa.

APS 1+1 Automatic Protection Switching (ANSI) and MSP1+1 Multiplex Section Protection (ETSI)

For Packet Abis over TDM a new version of ETS2 is requiredto support ETPT connectivity redundancy model

C109474.E4A, older x3x versions are upgradable to E4A


11/37



Plug-in unit Ethernet Switch Board (24 Ethernetports), ESB24-D

ESB24-D has total of 24 Ethernet ports. ESB24-A front panel has 4 gigabit (SFP) ports.

20 10/100/1000Base-T/Tx/T ports interface through backplaneconnectors.

A new pair of ESB24-Ds is needed for ETP and ETP-A LAN

connectivity ( ETPLAN ). In BSC LAN Device Integration the new ESB24-Ds are

Switching Units SWU-6 and SWU-7.

LANU


12/37



S15 BSC LAN topology (DRAFT)

CPULANESB24-D, ESB26

SWU-0 SWU-1

OMU

0 1

ETPLANESB24-D

SWU-2 SWU-3

PCULANESB24-D, ESB26

PCU

0 1

BCSU

0 1

MCMU

0 1

SWU-6 SWU-7

ETP

0 1

0 1

ETP

0 1

0 1

SWU-4 SWU-5

PCU

0 1

More info about the BSC internal LAN topology, contact S15 LAN topology Team: Marko Valo,Marko Immonen, Timo Leinonen, Juha Toivonen

Use of Ethernet ports, Spanning tree configuration,VLAN configuration

More info about the external routers/multilayer switches/ethernet switches: BSC Site SolutionScenarious and Requirements: Alessandra Celin, Francesco Menichella

https://sharenet-

ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=412912880&objAction=Browse

L3

L3

L3

L3

BSS21323 L3 IP Connectivityproposed to be a pre-condition for new ETPLAN topology


13/37



S15 power supply limits (DRAFT)

With packet ABIS/ AoIP interfaces in use power consumption of Flexi BSCexceeds limits of the power distribution system.

Remove second AS7 from every BCSU (Instead of lapD/AS7 Packet AbisTRXSIG/OMUSIGs are using IUA/SCTP/IP/Ethernet/mainCPU). There could be an option for removing also the first AS7 if only AoIP i.e.

SIGTRAN signalling is used (SS7 over IP). But it cannot be default.

Remove X.25 AS7-C:s from OMU configuration X.25 interface to NetAct is not feasible with over 3000TRX configurations

(capacity issue).

Move FTRB 2 from PDFU-B 0/ F9 to PDFU-B 0/ F18 Change power distribution requirements so that between -40,5V and -

44,0V we demand that both site inputs must be identical enough so thatminimum 10% of NE power consumption comes from spare power supplyline. For range -44,0VDC-57,0VDC network element must be able towork with single power supply input and maximum current shall be below30A. (In ETSI EN 300 132-2 chapter 4.2 is said:The normal servicevoltage range for the -48VDC nominal supply at interface A shall be -40,5VDC to -57,0VDC. NOTE 3: When the voltage is in the range -40,5VDC to -44VDC it is recognized that there may be a slightdegradation of service performance.) In BSC configuration this slight degradation is that both power supply lines

should be available when voltage is in the range from -40,5V to -44,0V


14/37



2. ETPE/T IP interfaces- Module Objective

After this module the reader: can explain the different IP/Ethernet interfaces of an ETP plug-in unit

has an idea about Packet Abis related BSC internal IPv4 addressplanning


15/37



PCU2-D

Logical interfaces of ETPE/T/A units in BSC

PCU2-E

ETPA

all

BCSUs

GW

BCSU

EEP link

PEP HDLC link

PEP Eth link

ETPSIG-m

ETPSIG-c

ETPSIG-m

BSC

ETP

E

ETP

T

Packet Abis

over Ethernet

Packet Abisover TDM

ML PPP bundles

(Abis HDLC links)

Abis

ETPs

AoIP TC in

MGW

ETPSIG-c

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: ETPAETPE/T interface for CS user plane in AoIP TC in MGW case


16/37



Octeon

CN5860

BOOT DDR RLD

SPI4.2

RGMII #6

I2C PCI

MDIO

GPIO

UART

FPGAMultiHDLC/EthIF

FLASH

Terminal

DDR2 RLDRAM

SFP

SERDES

Ethernet

Switch

Tomahawk

DSP#0

Tomahawk

DSP#7

2x FPGA

PCM-MUXEth

PHY

Eth

PHY

Eth

PHY

RGMII SGMII

SGMII

SGMII

RGMII

RGMII

TSIP

TSIP

TSIP

TSIP

DDR2

DDR2

Clocks

PowerSupply

MDIO

MDIO

MDIO

E2PROM I/O

SFP

Backplane Conn.

-48V

TCL0A/B

MDIO

Mainboard Daughterboard

-UB/B0V

Config

Config

.

.

.

RGMII#5

RGMII#4

BackplaneConn.

PCM4M

SERDES

SFP

Hotlink

Hotlink (Red.)

SFP

SPI4.2

Ckout

8KA/B, 8MA/B

Host IF

HostIF

QSGMII

Eth

Quad

PHY

10/100/1000 Base T/TX/T

10/100/1000 Base T/TX/T

10/100/1000 Base T/TX/T

Eth

PHY

Eth

PHY

RGMII

RGMII

10/100/1000BaseT/TX/T

10/100/1000BaseT/TX/T

RGMII #7

Eth

PHY

10/100/1000 Base T/TX/T

Eth

PHY

10/100/1000BaseT/TX/T

BackplaneConn.

Debug

Port

Clocks

LV12V Power

SupplyLV

SFPHotlink

SFPHotlink (Red.)

SFPHotlink

SFPHotlink (Red.)

Cartr Info

SwitchoverPLL/XO

ZBT

DDR2

CPLD

Exchange Terminal for Packet Transport (ETP)

IL0 IL1

IM0_0

IM0_1

IM0_2

EL0External Link 0: Abis CS/PS u-planes, e2e measurement packets and SynchE, Telnet, ssh. IL0/1Internal Link 0/1: ETPSIG-c, ETPSIG-m, PEP Link, EEP link, DHCP, FTP (SW upgrade). IN0 Internal Octeon - DSP interface. IM0_0Internal direct link between Sn+ load sharing pair. IM0_1/IM0_2Internal links normally not connected.

IN0

IM0

EL0


17/37



ETPE/T

0-0

active

BCSU

0

ETPSIG-m/c addresses and connectivity

ETPSIG-c

No VLAN

ETPSIG-m

No VLAN

ETPE/T

0-1

idle

ETPE/T

1-0

active

ETPE/T

1-1

idle

ETPE/T

2-0

active

ETPE/T

2-1

idle

ETPE/T

3-0

active

ETPE/T

3-1

idle

ETPE/T

4-0

active

ETPE/T

4-1

idle

ETPE/T

5-0

active

ETPE/T

5-1

idle

BCSU

1BCSU

2

BCSU

3BCSU

4BCSU

5

BCSU

6

SP-EX

Each active and idle ETPE/T has one IPv4 address for ETPSIG-m (type P; tagged I, M, D) Each active and idle ETPE/T has one GW BCSU for ETPSIG-m Each active ETPE/T has one IPv4 address for ETPSIG-c (type L; tagged V, I, C) ETPSIG-c connectivity is between the active ETPE/T and every WO-EX BCSU Every WO-EX BCSU has one shared IPv4 adress for ETPSIG-m and ETPSIG-c (type L; tagged I, M, C)

= one IPv4 address


18/37



BCSU

0

PA over Ethernet BSC internal host port VLANs

BCSU

1

BCSU

2

BCSU

3

BCSU

4

BCSU

5

BCSU

6

ETPE ETPAs

PCU2-Es

CS U-plane

Optional

BCF group level

VLANOMUSIG

Optional

BCF group level

VLAN

ETPSIG-c

No VLAN

ETPSIG-m

No VLAN

PS U-plane

Optional

BCF group level

VLAN

EEP link

BSC internal

CS u-plane VLAN

PEP linkBSC internal

PS u-plane VLAN

MCMU

DHCP

no VLAN

TRXSIG

Optional

BCF group level

VLAN


19/37



BCSU

0

PA over TDM BSC internal host port VLANs

BCSU

1

BCSU

2

BCSU

3

BCSU

4

BCSU

5

BCSU

6

ETPT

STMU

PCU2-Es

MCMU

CS U-plane

over TDM

OMUSIG

no

VLAN

ETPSIG-c

No VLAN

ETPSIG-mNo VLAN

PS U-plane

over TDM

PEP link

BSC internal

PS u-plane VLAN

DHCP

no VLAN

TRXSIG

no

VLAN

ETPAs

EEP link

BSC internal

CS u-plane VLAN

OMUSIG/TRXSIG is routed through ETPT i.e.ETPT is serving as next-hop gateway towardsBTS from BCSU.


20/37



Packet Abis over Ethernet external VLAN usage

BCF

BCF

BCF

BCF

BCF

Broadcast domain A

BSC

Broadcast domain B

Limited broadcast domains

will protect the other BTS site regions

VLAN ID A

BCF

VLAN ID B

If Abis is L2 (switched network) ETPE EL0 has to be able to terminate upto 30VLAN interfaces used to group BCFs

Inside the BCF group same VLAN id is used for the TRXSIG and CS/PS u-planes,but they may have different VLAN priority.

OMUSIG may have a separate VLAN id or also OMUSIG can use the same VLANas TRXSIG and u-planes.


21/37



Packet Abis IP-Addressing Planning (DRAFT)

Each VLAN forms one subnet

L3 IP Connectivity: one public (routable) /28 (upto 14 nodes) subnet needed

for OMUSIG and TRXSIG-External ETPE/T EL0 addressing

Depends on the network to be used (Switched or Routed Network betweenETPs and BTSs)

7 New internal subnets for BSC /27 (upto 30 nodes) subnet for ETPSIG-M-Internal (e.g. 10.0.1.0/27)

/27 subnet for ETPSIG-C-Internal (e.g. 10.0.1.32/27)

/27 subnet for OMUTRXSIG-Internal (e.g. 10.0.1.64/27)

/27 subnet for EEP (e.g. 10.0.1.96/27)

/25 (upto 126 nodes) subnet for PEP (e.g. 10.0.2.0/25)

/30 (two nodes) subnet for ETP internal IM0

/24 (upto 254 nodes) subnet for ETP internal IN0 OPEN ISSUE: These addresses are used internally so can they be similar in

every BSC? IM0 and IN0 addresses can be the same also for different ETPpairs in the same BSC.

maybecombined

to one

subnet


22/37



3. Configuring the Packet Abis BSC - ModuleObjective

After this module the reader: has an idea how to integrate the ETPE/T units into the BSC

1. Platform: Commissioning and Integrating ETPE/T

2. Platform: configuring PCU2 for Packet Abis

3. Platform: configuring ETS2 for Packet Abis over TDM

4. Platform: configuring LAN Devive Integration

5. Platform: configuring ETPE/T network interfaces

6. Platform: Configuring ETPE/T IP addresses

7. Platform: configuring ETPSIG interfaces

8. Applications: Configuring PEP links

9. Platform: Configuring BCSU network interfaces for OMUSIG and TRXSIG

10.Platform: Configuring BCSU IP addresses for OMUSIG and TRXSIG

11.Platform: IP Routing Data Handling


23/37



Platform: Commissioning and integrating ETPE/T

Platform equipment management, basic maintenance and SW handlingcommands ZWTU Create functional unit

ZWTP Create plug-in unit ZWUCConnect functional unitNOTE: after basic equipment management user has to configure the network interfacesand IP addresses needed for etpsig-m.

ZUSWorking state and restart handling ZUDDiagnostics handling ZA. Alarm system administration

ZWD...Embedded software handling L: ..... FORCE SOFTWARE UPGRADE OF ETP UNITS

M: .....INQUIRE VERSIONS OF SOFTWARE OF ETP UNITS

WORKING STATE OF UNITS

UNIT PHYS STATE LOCATION INFO

ETPE-0-0 1403 WO-EX ACTV

ETPE-0-1 1404 WO-EX -

HCM MML use case document, under updating currently: https://sharenet-

ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1#_Toc245874511
https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1


24/37



Platform: configuring PCU2 for Packet Abis

The DSP pcm function type parameter is used to dedicate a

PCU2 unit into Packet Abis use. Value PCUPAB means Packet Abis, in legacy Abis the value is

PCUDSP.

ZWTP:BCSU,0:PCU2_D,0,1::PCUPAB,4,272&&273,TSL,0&&31:PCUPPC,4,276&&277,TSL,0&&31:;

//Different PCU sw id will be selected in this command according to pcmfunction types and store the id in equipm

ZWUC:BCSU,0:PCU2_D,0:;

//64kbit/s circuits like 272-0, 272-1,272-3 will be automatically added intoCGR "PCUPAB" in WUC command.


25/37



Platform: configuring ETS2 for Packet Abis

Changes to the HW configuration of the ETS2/SET/STMU unit when it'sused with the ETPT for Packet Abis over TDM:

First limitation is that user has to equip ETPT first(WTU,WTP, and WUC), afterthat equip the ETS2/STMU similar as legacy. There's change in the command when equiping STMU ET:s with plug-in unit,

the pcm function ETT00 is not used. ETSI (commands are implemented and under module test in this month):

ZWTU:ET,64&&126:1F1-0:UNIT=STMU,IND=0,IF=0;

ZWTP:ET,64&&126:ETS2,0,1::GENERAL,8,64&&126,NO:; // pcm 64&&126 shouldrefer to GSWB pcms, and they are for traffic, so no ETT00.

ANSI (commands will be implemented in next month):

ZWTU:ET,2048&&2131:1F1-0:UNIT=STMU,IND=0,IF=0;

ZWTP:ET,2048&&2131:ETS2,0,1::GENERAL,8,2048&&2131,NO:;

after ETPT and STMU/ET:s equiped, user needs to use a new port connectioncommand WTA to describe the hotlink connections between STMU and ETPT,ETPT and GSWB as well, for hw supervision purpose. (Port connectioncommands are implemented & module tested & under entity test)

HCM MML use case document, under updating currently: https://sharenet-

ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1#_Toc245874511
https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink/411060218/ETP+Use+Cases+in+HW+Configuration+Management.doc?func=doc.Fetch&nodeid=411060218&vernum=7&viewType=1


26/37



Platform: configuring new ESB24-D LAN DeviveIntegration (B10/B11 (S11/S12) platform feature feature31500)

New SWU units SWU-6 and SWU-7 handled with: Equipment management (ZWT)

Working State and restart handling (ZUS)

Internal LAN management (ZWY)

Topology Management (ZW6) LAN HW supervision handling ZYF)

DRAFT: three new LAN topologies T8, T9 and T10 T8: Upgraded Flexi with L3 capability

T9: New delivery Flexi with L3 capability

T10:BSC3i 1000/2000 with L3 capability


27/37



Platform: configuring ETPE/T network interfaces

ZQRA:ETPE,0,0:: IDENTIFY NETWORK INTERFACE NAME:

ETHERNET: EL0 EL1IL0 IL1 IM0 IN0

VLAN: VLAN0-VLAN4094

BONDING: BOND0

SPECIFY MAXIMUM TRANSMISSION UNIT

User configures each ETPE/T network interface (ethernets and VLANs)one by one

A special caseafter configuring ETP IL0 and IL1 user shall bond themtogether

QRA:ETPE,0,0::BOND0,IL0,IL1 /* SPECIFY THE BONDING MAC ADDRESS:

MAC: ############

ENTER MAC ## IN HEXADECIMAL FORMAT

DEFAULT IS SYSTEM GENERATED MAC */

In ETP case user does not have to specify the bonding MAC address. ETP will use the existingMAC.

ETPE/T will automatically bond the IL0 and IL1 together during start-up


28/37



Platform: Configuring ETPE/T IP addresses

ZQRN:ETPE,0,0::interface_name:ipv4_address:netmask length:

/* /* SPECIFY IP ADDRESS TYPE

L ... LOGICAL IP ADDRESS

P ... PHYSICAL IP ADDRESS

DEFAULT IS LOGICAL IP ADDRESS */

/* SPECIFY IP ADDRESS ATTRIBUTE(S):

V ... VIRTUAL IP ADDRESS

I ... INTERNAL IP ADDRESS D ... DYNAMIC IP ADDRESS FOR DHCP CLIENT

XXX A USER DEFINABLE TAG

DEFAULT IS ATTRIBUTE NOT DEFINED */

One address can have several attributes. The user definable tag can bee.g. a three letter abbreviation, in BSC case PEP and EEP.

User configures the IP addresses one by one

NOTE: a pre-defined attribute D shall be used for the ETPE/T etpsig-maddress. ETPE/T gets it from the BSC DHCP server during start-up.

Final implementationmay be that theres a

separate ZQRxcommand to configure

the attributes/tags.


29/37



ETPE/T IP address types and attributes perinterface EL0 and EL0 VLANs

Upto 30 carrier sense Virtual address(es) i.e. one address per BCF group (incase of L2 u-plane connectivity VLANs can be used to group the BCFs to limitthe size of the broadcast domains).

BOND0 (IL0/1) and BOND0 (IL0/1) VLANs One Physical Dynamic Internal Management IPv4 address for etpsig-m (both

units of a pair have an etpsig-m address of its own) attribute D means that BSC DHCP server allocates the address during start-up.

One Logical Virtual Internal Control IPv4 address for etpsig-c One Logical Virtual Internal PEPtagged IPv4 address One Logical Virtual Internal EEPtagged IPv4 address NOTE: User has to configure also the BCSU etpsig-m/c, PCU PEP and ETPA

EEP IPv4 endpoint addresses!

IM0

One Physical Internal IPv4 address for pair unit connectivity IN0 One Physical Internal IPv4 adress for Octeon side with a big enough subnet This user defined physical address is a base to the IN0. Octeon will calculate

and apply DSP core addresses as offset of this base address.

Check S15 informative CR163: IP Address Identification Tags


30/37



Platform: configuring ETPSIG interfaces

After user has configured the BCSU and ETP Networkinterfaces and IPv4 addresses the user can configure the

etpsig-m and etpsig-c links.

ZD2C CREATE IUA MESSAGING PARAMETERS DRAFT:

: , :

, , : : : : ;

ZD2D DELETE IUA MESSAGING CONFIGURATION

ZD2I INTERROGATE IUA MESSAGING CONFIGURATION

DRAFT: During first etpsig-c creation the system checks thatETP/ETP-A plug-in unit lisence exist.


31/37



Applications: Configuring PEP links

After user has configured the BCSU/PCU2 and ETP Network

interfaces and IPv4 addresses the user can configure thePCU2-E PEP links.

Configuring PCU2ETPE/T connection (PEP link) ESKCREATE ETP-PCU CONNECTION

up to 32 logical PCUs of PCU2-Ds to one ETPT/ETPE. up to 8 PCU2-Es to one ETPT/ETPE.

also mixed configurations e.g. 16 x PCU2-D logical PCUs + 4 x PCU2-E

ESHREMOVE ETP-PCU CONNECTION

ESLOUTPUT PACKET ABIS CONFIGURATION

PCU2s in the same pool can be connected to differentETPE/Ts, but then the Abis connectivity of the pool isfragmented.


32/37



Platform: configuring BCSU network interfaces forOMUSIG and TRXSIG

ZQRA:BCSU,n::

/* IDENTIFY NETWORK INTERFACE NAME: ETHERNET: EL0 EL1IL0 IL1 IM0 IN0

VLAN: VLAN0-VLAN4094

The same BCSU network interfaces EL0/EL1 are shared byother applications:

A-if SIGTRAN

BSC-BSC interface for DFCA

Etpsig-m and etpsig-c


33/37



Platform: Configuring BCSU IP addresses forOMUSIG and TRXSIG ZQRN:BCSU,n::interface_name:ipv4_address:netmask

length: Amount of addresses depends on

is Packet Abis over Ethernet or over TDM?

is Packet Abis over Ethernet switched (L2) or routed (L3) network?

is BSS21323 L3 IP Connectivity feature in use?

if Abis over Ethernet is switched (L2), is the L2 terminated in an externalmultilayer switch in the BSC edge or is the L2 terminated to the BSC itself?


34/37



Platform: IP Routing Data Handling

User has to create route( s) if BSC and BTS site(s) are indifferent subnets i.e. Abis is a routed network.

ZQKC CREATE STATIC ROUTE /* SPECIFY DESTINATION IP ADDRESS:

DOTTED DECIMAL INTEGER (#.#.#.#) IN QUOTATION MARKS FOR IPV4ADDRESSES

DEFAULT IS DEFAULT ROUTE

/* SPECIFY GATEWAY IP ADDRESS:

DOTTED DECIMAL INTEGER (#.#.#.#) IN QUOTATION MARKS FOR IPV4ADDRESSES

Special case for routes is the Packet Abis over TDM. The

ETP IL0/1 etpsig-c address shall be created as a gatewayaddress for the BCSU OMUSIG and TRXSIG interfaces.

SS21231


35/37



BSS21231 Packet Abisintroduction to testing in DX platform Zhu Hang, B14 I&V coordinator, NSN Hangzhou:

DX200 Platform will do the entity testing within scrum team in different area when item

development is finished. One complete regression testing will be planned and executed in main and critical areas. The areas marked with REDmeans the testing will be done in platform,others still need to

be confirmed such as testing method.

Currently many areas are developed without entity testing due to lack of real HW.

DMX Messaging IUA/UDP

IP management

ETP Licensing

DHCP server services for DMXmessaging

ETP Software loading

Recovery

HW configuration management

Hw supervision / ETS2modifications

Service Terminal

Diagnostic

Clock and synchronization

Security

Alarm interface

User Authentication

User Interface

Calendar and Time Management

Logging System

ETP Hw supervision

Event forwarder

BSS21231 P k t Abi


36/37



BSS21231 Packet AbisHow to test (out of scope of this presentation)Configurations have to be planned

BSC generations to be used

Packet Abis and TDM Ater Packet Abis and AoIP TC in MGW PCU2-E and PCU2-D Packet Abis over TDM and over Ethernet, transmission and equipment protection models

Etpsig-m/c performance and robustness especially during different restartsCS call cases - different codecs, CS data, TFO, TrFO, voice quality

PS datathroughput shall be as good as with legacy AbisETP performance is the biggest challenge, some notes and estimates: Traffic models have to be planned From Octeon perspective the dominant factor is packet per second. However, for a given

packet per second, packet size will contribute a delta load.

On DSP, idle PEP HDLC links consume CPU. And then this idle load gets utilized oncedata started flowing and in addition CPU is needed for packet processing and exchangeswith Octeon. From DSP perspective packet size also contributes load.

OSC is unknown to ETP. For ETP, an OSC may mean upto 4 independent calls with totalcalls being 8192.

From Octeon perspective loads caused by TDM Ater CS traffic and AoIP TC in MGW CStraffic are same. However, DSPs will get saturated before Octeon.

From Octeon perspective loads caused by PCU2-D PS traffic and PCU2-E PS traffic aresame. However, DSPs will get saturated before Octeon.

In Packet Abis over TDM case TRXSIG/OMUSIG packets are processed like U Planepackets and cause similar load.

BSS21231 P k t Abi


37/37


BSS21231 Packet Abissome additional information links

ETP IS:

https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399914099

https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399914099

ETP-A IS:

https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399889976

https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399889976

NE HW IS:s in NE HW System Engineering folder:

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

ETP messaging over IUA, Feature 31584, DX 200 Platform Feature

Implementation Principles :https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/413483376

IP Management FImS

https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/397160278
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399914099https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399914099https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=409845325&objAction=Browse&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=409845325&objAction=Browse&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=409845325&objAction=Browse&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/413483376https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/397160278https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/397160278https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/397160278https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/397160278https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/413483376https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/413483376https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/413483376https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=409845325&objAction=Browse&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=409845325&objAction=Browse&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=409845325&objAction=Browse&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=409845325&objAction=Browse&viewType=1https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399889976https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399914099https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399914099https://sharenet-ims.inside.nokiasiemensnetworks.com/Guest/Open/399914099https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399914099https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399914099https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/399914099

Documents

Packet Abis BSC NE Configurations. ETPE_T IP Interfaces, Configuring BSC