s15 packet abis and aoip overview.ppt

BSS_feature no <Feature name>Overview
Entire NSN GSM interfaces supporting IP/ ETH
Before
BSS13
(CESoPSN)
RG20
Soc Classification level
* © Nokia Siemens Networks
Presentation / Author / Date
Dynamic Abis today
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
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
One Traffic channel
BSS15/RG20 Features
BSS21454 Packet Abis over IP/Ethernet
BSS21444 Packet Abis Security
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
ETIP = Pseudowire Emulation interface unit (TDM over IP)
HD = Hard Disk Drive
MO drive = Magneto-Optical Drive
PCU = Packet Control Unit (PCU1 or PCU2)
STMU = STM-1 Exchange Terminal (optical interface)
TCSM = Transcoder Submultiplexer (TCSM2 or TCSM3i)
Plug-in units
ETP-A Exchange Terminal for Packet Transport over A-interface
Functional units
ETPA, Exchange Terminal for Packet A-interface
ETPC, Exchange Terminal for Packet A-interface in Transcoder
BSC
TCSM
AoTDM (PT) G.711/CS Data
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
Recommended value for CESoPSN
maximum value for CESoPSN
Synchronization to
T1/E1 Interface
2MHz source
Packet Switched Network
Adaptive clock Recover uses 1 virtual TSL (64K) bandwidth as empty CESoPSN PW for synchronization (+overhead)
Jitter could influence Adaptive clock performance.
BSC
IP-BTS
GSWB
TCSM3i
MGW
IP-BTS
SET
SET
TCSM3i
MGW
BCSUs
General
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
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)
PDFU 0
FTRB 3
FTRB 2
GTIC
ETC
ETC
ETC
ETC
ETC
ETC
GTIC
MCMU
MCMU
OMU
BCSU
BCSU
BCSU
BCSU
BCSU
LANU
LANU
CLAC
GSW2KB
GSW2KB
CLOC
BCSU
(300)
PCU2-E
ETPA
all
BCSUs
GW
BCSUs
AoIP TC
in BSS
AoIP TC
in BSS
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
ETPSIG-c
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.
DMX messaging using logical addresses
DX platform delivers messages via a BCSU that acts as a Gateway (GW role nominated via D2 -MML commands and has to be the same for protecting unit)
alarms, supervision, diagnostics, recovery, IP configuration
configuration
ETPSIGs use only limited IUA protocol (IUA Data Request/Indication messages)
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 messaging inside the BSC, each BCSU has direct interface to each ETP unit
ETPSIG in case of AoIP (TC in BSS)
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
BSC
IP-BTS
GSWB
TCSM3i
MGW
IP-BTS
SET
SET
TCSM3i
MGW
BCSUs
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:
Normal TCH setup
CHANNEL ACTIVATION ACK
ETPA CS U-PLANE CONFIRM
ETPA CS U-PLANE RESERVE
ETPT
Abis CS u-plane <-> ETPA
Abis PS u-plane <-> PCUs
ETPT
HDLC
ML/MC-PPP
ETPE
Abis CS u-plane <-> ETPA
Abis PS u-plane <-> PCUs
A over IP (TC in MGW) – U-plane forwarding in ETPA
A over IP (TC in BSS) – U-plane conversion in ETPC
TCSM3i
ETPC
TR3
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
BSC
GSWB-1
ETPT-0-1
idle
ETPT-0-0
active
GSWB-0
SET-3
STMU-0
active
SET-2
SET-1
SET-0
SET-7
STMU-1
idle
SET-6
SET-5
SET-4
protecting
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.
BSC
GSWB-1
ETPT-0-0
active
GSWB-0
SET-3
STMU-0
active
SET-2
SET-1
SET-0
working
protecting
PCU2-D
BSC
IP
Legacy Abis and Packet Abis are possible with legacy A-if
Note: BSS Internal HO is a new HO type specified because of AoIP.
STMU
ETP
2n
ETPT
ETP
E1/
T1
ETP
2n
Supported Call Paths - Packet Abis and AoIP (TC in BSS)
PCU2-D
BSC
IP
Intra-BSC HO
Legacy Abis and Packet Abis are possible with AoIP (TC in BSS)
Also in case of remote TCSM3i
STMU
ETP
2n
ETPT
ETP
E1/
T1
ETP
2n
Supported Call Paths - Packet Abis and AoIP (TC in MGW, Full IP)
PCU2-D
BSC
IP
Intra-BSC HO only within Packet Abis
Legacy Abis is not possible with AoIP (TC in MGW) in S15
MSS controlled BSS Internal HO between A-if types
STMU
ETP
2n
ETPT
ETP
E1/
T1
ETP
2n
CS user plane
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)
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
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
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
S15 Firmware and memory upgrade procedure
IP Address planning
L3 BSC IP Site Connectivity upgrade
Configuring Packet Abis
Configuring L3
Configuring LAN Devices (ETPLAN)
Configuring ETS2 for Packet Abis over TDM (optional)
Configuring ETPE/T network interfaces
Configuring ETPE/T IP addresses
IP Routing Data Handling
Steps to create BCF to use Packet Abis
Create SCTP associations for OMUSIG & TRXSIG(ZOY)
Create D-channels for OMUSIG & TRXSIG (ZDW)
Create Abis HDLC links (only in case of Packet Abis over TDM)
Create BCF
Create TRXs
Open abis HDLC links (only in case of Packet Abis over TDM)
Unlock/activate created objects
Creating ETPA
ETPC local configuration
BCSU
1
BCSU
2
BCSU
3
BCSU
4
BCSU
5
BCSU
6
ETPE
ETPAs
PCU2-Es
BCSU
1
BCSU
2
BCSU
3
BCSU
4
BCSU
5
BCSU
6
ETPT
STMU
PCU2-Es
OMU
CS u-plane VLAN
OMUSIG/TRXSIG is routed through ETPT i.e. ETPT is serving as next-hop gateway towards BTS from BCSU.
Troubleshooting
Logical connection verification
Ping, tracert
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
dbcfinfo [bcf_id]
etpsig_m_info
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).
dudul
duddl
dpdul
dpddl
netstat -a
dscfp
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.
Insert footnotes as appropriate.
Nokia Siemens Networks has four information confidentiality classes: Public, For internal use, Confidential, Secret
"Public" - May be distributed to anyone. Usually public information shall be available for everyone.
"For internal use" - May be distributed to anyone employed or having a business relationship with the company under a valid non-disclosure agreement. The disclosure of small amounts of this information to the public will not cause meaningful damages to the company. ‘’For internal use’’ is the default class for Nokia Siemens Networks information, this should be included e.g. in all MS Office (master) templates.
(Previously Nokia: Company Confidential, Siemens: Internal use)
"Confidential" - May be distributed only to people who have a valid business need. The validity of the business need can be judged by anyone who is authorised to possess the information. Unintentional disclosure of this information to the public will cause significant damages to the company. ‘’Confidential’’ is the default class for any customer information.
(Previously Nokia and Siemens: Confidential)
"Secret" - May be distributed only to people who are specifically authorised by the owner of the information. Disclosure of this information to the public will cause serious damages to the company.
(Previously Nokia: Secret, Siemens: Strictly confidential)
All documents in Nokia Siemens Networks shall be labelled according to this confidentiality schema.
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
ETP/ ETP-A
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 while downloading new SW into ETP. Avoid restarting the ETP with C=TOT option as 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.
BSC
ETP/ ETP-A
While configuring etpsig-m for active and redundant ETPE/T/A ensure that the GW BCSU is the same. This is to avoid problems during switchovers and restarts.
BSC
ETP/ ETP-A
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 interface and equipment redundancy i.e. to trigger switchover if there’s a failure in the Ethernet interface. The FCLF-8521-3 does not have a link indication feature (RX_LOS is internally grounded).
BSC
ETP/ ETP-A
If electrical (copper) EL0 cabling is in use the Autoneg setting in the other peer (external switch port) shall be ON (dublex auto, speed auto). If optical (fibre) EL0 cabling is in use the Autoneg setting in the other peer (external switch port) shall be OFF.
Entity
Area
ETP/ ETP-A
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 over is to change the active unit to BL. Then the active unit goes to BL-EX and after the 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.
BTS
PAoETH PAoTDM
Differing from the default BTS SCF values for the OMUSIG SCTP signaling protocol, the Selective Acknowledgement period has to be configured to 110ms (same as in BSC).
BSC
PAoETH PAoTDM
As default SCTP bundling is in use for OMUSIG and TRXSIGs. Because of bundling delay the BTS level parameter SLO (number of timeslots to spread retransmissions) must be changed from 10 to SLO=32.
BSC
SWUs (ESB24-D)
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 when ending the monotoring It’s not enough to 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
AoIP u-plane
BSC does not supervise the e-2-e user plane of AoIP (both TC in MGW and TC in BSS) is not supervised. If NSN MGW is in use turn the RTCP u-plane supervision OFF. When integrating the ETPA/C unit remember to ping the other peer (i.e. MGW u-plane address).
BSC
AoIP
Set the NSN MSS/MGW parameter AOIP TRANSPORT TYPE PERCENTAGE to 100. Then the AoIP is used for all the call set-ups when using of AoIP is possible.
BSC
AoIP
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 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.
BSC
A-if signalling (also legacy A)
If with NSN MSS a log writing MCMU log: TWO WAY RELEASE TO SWICOP;double reserve is seen in the MCMU the BSSAP par nbr. 61 "MODIFIED RE-ESTABLISHMENT RELEASE SEQUENCE“ shall be changed to Yes in the MSS.
BSC
NPO
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 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.
BSC
NPO
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 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 and NPO pilot learning's.
Primary colours:
Supporting colours:
Raimo Ahosola
BSC Site IP Connectivity Guidelines, DN03502792
Feature description: BSS21440: Packet Abis over TDM, BSS21438 Packet Abis over Satellite, BSS21445 Packet Abis Congestion Reaction, DN0963196
Feature description: BSS21454: Packet Abis over Ethernet, BSS21439: Packet Abis Sync. ToP, IEEE1588v2,BSS30450: Packet Abis, Synchronous Ethernet, and BSS21444: Packet Abis Security, DN0963184
Feature description BSS21341: A over IP, DN0963172
etc.
CS U-plane
PS U-plane
Traffic volumes
Codec distributions
In migration cases
Air if & current Abis capacity & traffic share load based dimensioning
C-plane: from TRXSIG & OMUSIG
CS U-plane: based on Air Conf & FR, HR share (+ estimate of HR OSC)
PS U-plane: based on available Air & Abis capacity
Presentation / Author
See full story: PIR & CIR usage.ppt
LLC – Logical Link Control
RLC – Radio Link Control
RLC/MAC Block 1)
RLC Block 1)
~1500 octets
CS3 and CS4 require New HW (i.e. EDGE, S11)
CS-1
22
8
0
176
28
CS-2
32
8
0
256
33
CS-3
38
8
0
304
39
CS-4
52
8
0
416
53
MCS-1
22
31
9
176
27
MCS-2
28
31
9
224
33
MCS-3
37
31
9
296
42
MCS-4
44
31
9
352
49
MCS-5
56
37
11
448
62
MCS-6
74
37
11
592
80
MCS-7
2x56
46
10
896
119
MCS-8
2x68
46
10
1088
143
MCS-9
2x74
46
10
1184
155
Example 1
traffic
probability
CIRBTSBSC
example2
demand
Possible Packet loss due to congestion at the transport
traffic
probability
PIRt =
CIRBTSBSC
SP
WFQ
packet loss on DL Abis PL1 threshold (PL1)
packet loss on DL Abis PL2 threshold (PL2)
EF & AF4 traffic colored green
AF1 to AF3 & BE traffic colored yellow
DSCP & VLAN priority (p-bit)
Split subnets for BSC
Adjacent subnets for BTS M-planes
Adjacent subnets for BTS C-planes
Limitations for ETPE/ETPT/ETS2 unit positions risk for need to rearrange the existing STM-1 usage
ETPT to ETS2 association used in this example
ETPT line redundancy
ETPT HW redundancy
Agenda of Presentation
High level plan
BSC IP@ Plan
BCF Integration sheet
BSC data fill
Dedicated D-channels for Packet Abis
OM077 OP077
simplifies migration
Ethernet traffic vrs. CS, PS & sig traffic (comparison open)
AoIP not activated by 14th Feb
SCTP parameters to be fine tuned R&D is investigating increased SDCCH drop if SCTP bundling was used
Only few sites up so far
The 1st PAoEth site in the 28 Jan
The 1st PAoTDM site in the 3rd Feb
Thank you
Case A: CS only (4+4+4 32 TRXsig)
0
500
1000
1500
2000
2500
3000
0%
100%
CESoPSN (PWE)
Case B: GPRS only (4+4+4 32 TRXsig)
0
1000
2000
3000
4000
5000
6000
0%
100%
)
Case D: EGPRS only (2+2+2 EGPRS) 32 TRXsig)
0
1000
2000
3000
4000
5000
0%
100%
activity
CESoPSN (PW1 + PW2)
BSC/BTS
NPO
Traffic scheduling activation assumes valid value for DLCIR parameter even the given parameter is relevant only for Ethernet and not for ML-PPP. As a workaround apply: DLCIR = ML-PPP capacity.
BSC/BTS
HC
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 in both sides ( from BSC and BCF) and then BCF and HDLC link lock unlock to be performed.
BSC
HDLC
In case the associations for certain PAoTDM sites go down. The work around for this is to lock and unlock the HDLC links followed ETPT switchover.
BSC
ML PPP bundle
A Packet Abis over TDM feature specific PRFILE shall be installed to change the value of PRFILE parameter PCM_MAINT_ANNOUNCE_TL (parameter ID Class 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.
BSC/BTS
OSC
BTS SW has to be attached to BCFs before OSC can be activated
BSC
OSC
Null circuit has to be created to make CSDAP working, example: ZRCC:TYPE=SPE,NCGR=BB_ZERO,CGR=99:FORMAT=0,HUNTED=N,: ZRCA:NCGR=BB_ZERO:CRCT=0-0&-1:
PDV (jitter)+/- 5 ms+/-25 ms+/- 5 ms+/-20 ms
max packet loss
GTIC 0 or GTIC 1
1. Packet Abis over ETH and ETP-A for A plus Dynamic Abis/Ater
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
ETPEETPEETPEETPE
ETP-A
ETP-A
17
S
H
I
M
4
T
S
H
I
M
4
T
CHANNEL ACTIVATION ACK
ETPA CS U-PLANE RESERVE
ETPA CS U-PLANE CONFIRM
SB1-0
SB1-1
SB2-0
SB2-1
OPR
Tx/Rx
FAIL
STM-1/OC-3
STM-1/OC-3
STM-1/OC-3
STM-1/OC-3
Tx
0
M
Rx
Tx
0
R
Rx
Tx
1
M
Rx
Tx
1
R
Rx
ETS2
SB1-0
SB1-1
SB2-0
SB2-1
OPR
Tx/Rx
FAIL
STM-1/OC-3
STM-1/OC-3
STM-1/OC-3
STM-1/OC-3
Tx
0
M
Rx
Tx
0
R
Rx
Tx
1
M
Rx
Tx
1
R
Rx
ETS2
1. Packet Abis over TDM & ETP-A for A ( 6+6 ETPT , 4 ETP-A & 3+3 ETS2 as mate of ETPTs)
SB1-0
SB1-1
SB2-0
SB2-1
OPR
Tx/Rx
FAIL
STM-1/OC-3
STM-1/OC-3
STM-1/OC-3
STM-1/OC-3
Tx
0
M
Rx
Tx
0
R
Rx
Tx
1
M
Rx
Tx
1
R
Rx
ETS2
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
SB2
SER1
RUN
1
0
1
0
1
0
2
1
SB1
ETHSB3
ETPT
ETPT
ETPTETPTETPTETPT
ETP-A
ETP-A
17
S
H
I
M
4
T
2.
110
GSM
3.
112
AMR
5.
95
6.
111
HR

s15 packet abis and aoip overview.ppt

Documents