Upload
rdtiwari123
View
127
Download
4
Tags:
Embed Size (px)
Citation preview
IUPS over IP (UA6 -PM33363)IUCS over IP (fast feature patching over
UA6 before UA7)
Laurent Rigault - FOA TRIAL engineer – O4th December 2008 – Version
v01_5
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.2
The goal of this slidepack
1. Present migration path and high level migration IuPSoATM to IuPSoIP
2. Highlight the hardware requirements
3. Highlight the main parameters used for configuration
4. SCTP and M3UA
5. Detail SCTP, M3UA, RANAP call flow establishment
6. External Routing configuration examples
7. RNC carrier Grade redundancy and router routing configuration example
8. Wireshark tracing examples (CS, PS, SRNS relocation without IuR)
9. Terms and definition, ALU Lab Ottawa example with ALU SGSN
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.3
Introduction
The feature enables the IuPS Control Plane of the RNC to support an SS7 stack over IP (SCCP/M3UA/SCTP/IP/Ethernet) as well as adding the ability for the underlying transport of the IuPS User Plane to be done over Ethernet (GTP-U /UDP /IP /Ethernet).
With this feature, an ATM-based SS7 stack and an IP-based SS7 stack will co-exist on the RNC for the Iu interface (ATM for IuCS/IuPS and IP for IuPS). The support of IP for the IuPS is on a per-interface instance, i.e., one instance must be either ATM or IP for both the Control and User Planes of that instance.
Important: Different SGSN SS7 point code must be used for ATM and IP SGSN connectivity to a defined RNC because different SGSN must be used
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.4
Protocol stacks
An IuPS interface instance is either Full ATM (CP + UP) or Full IP (CP+ UP)
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.5
1Migration in case of direct connection between RNC and SGSN
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.6
Migration of networks with IuFlex activated only in RAN (1/3)
SGSN 1
RNC RNC
Initial State Transient State
Final State
MSC1
MSC1
SGSN ATM CN node
IP CN nodeSGSN
ATM
RNC RNC
SGSN 1 SGSN 1 SGSN 2 SGSN 2
ATM
IP IP
Purpose is to migrate without Outage
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.7
Migration of networks with IuFlex activated only in RAN (2/3)
In the initial state the RNC is connected to CN1 using ATM transport.
During the transient state the network is reconfigured as follows:
1.A new SGSN (SGSN2) is added which can support IP transport.
2.IuFlex is configured on the RNC. This means that the RNC will now start to use the IuFlex NAS node selection function to determine which SGSN to direct any new calls to. However, at this stage only knowledge about SGSN 1 is configured in the RNC and therefore all calls continue to be directed to SGSN 1.
3.The Iu-PS link is configured between SGSN 2 and the RNC. It is possible to configure this second Iu-PS link because the RNC has now been enabled for IuFlex. The initial administrative state for the Iu-PS link is locked.
4.SGSN 2 is made the preferred choice when the RNC selects a SGSN for any new calls. This is achieved by provisioning SGSN 2 with a higher capacity indication relative to SGSN 1. Therefore when the load balancing function is triggered within the RNC it will select SGSN 2 over SGSN 1.
5.The Iu-PS link between SGSN 2 and the RNC is unlocked so that any new calls will now be directed towards SGSN 2 by the RNC load balancing function.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.8
Migration of networks with IuFlex activated only in RAN (3/3)
During the final state, IP network topology for the Iu-CS is achieved as follows:
6.The Iu-PS link between SGSN 1 and the RNC is either locked or is shutdown. If the link is locked the Iu-PS link is immediately taken out of service. If the link is shutdown any established calls are given the opportunity to complete prior to the Iu-PS link entering the locked state. Any calls still present when the link is locked will be lost but there will be no service loss since new calls will be directed to SGSN 2.
7.Provisioning information pertaining to SGSN 1 can now be removed from the RNC.
8.The IuFlex configuration can now be de-provisioned from the RNC.
The ONLY migration step supported is ”migration of networks with IuFlex activated only in RAN” due to the lack of Iu-Flex deployment in the field.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.9
Hardware Requirements2
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.10
Here are the ordered steps to follow before configuring/activating IuPS over IP:
Software requirement: RNC UA06 supporting the Iu-PS over IP feature.
Hardware requirement: the RNC is equipped with two 4 ports Giga Ethernet cards,
An IP network is available (including IP path redundancy to 1 or 2 routers).
The RNC IP transport configuration is provisioned, i.e.: – GE configuration, – VLANs configuration,– VRs configuration, – Static Routes configuration, – QOS configuration
Overview of the common requirements
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.11
RNC 4pGigE with LX or SX SFP
The RNC must be equipped with 2 GigE 4 ports cards. The 4pGigE cards must go in slots 14 & 15. If PS cards are present in the RNC in slots 14 & 15, they must be replaced by the two 4pGigE cards. This is illustrated in the following figure:
Possible RNC CAPACITY decrease
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.12
RNC 4pGe card main specification using LX or SX SFPs
The 4pGe card has an operating capability of full data line rate (1 Gbit/s) for each port,
however, the aggregated backplane interface throughput for the four ports is 2.5 Gbit/s.
The two boards are used in load sharing mode (both actives simultaneously), thus 8 GiGE ports
are available for a RNC using direct IP interfaces. The main capabilities of this FP are :
• Support for 1000BASE-SX (short wavelength) and 1000BASE-LX (long wavelength) per port
basis
• Maximum segment length for 1000BASE-LX single mode is 10km (SINGLE MODE fiber
used)
• Ethernet II (ingress & egress) , 802.3 LLC SNAP encapsulation (ingress only)
• Full Gigabit Ethernet bandwidth (one Gbit/s) supported on each FP port
• Aggregate bandwidth of approximately 2.5 Gbit/s supported on all four FP ports(depending
on packet size and service)
• Full duplex only
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.13
PP8600 Router (Nortel Networks) 8616SXE Module
Passport 8616SXE Module
The Passport 8616SXE Module provides 16 1000BASE-SX ports
(850 nm, short wavelength, Gigabit Ethernet) for riser connections, server
attachments, or interswitch links. The short wavelength optical transceivers
used
in the module provide transmission ranges up to 275 meters (m) using
62.5 μm
MULTI MODE (MM) fiber cable or up to 550 m using 50 μm multimode fiber
cable.
The Passport 8616SXE Module supports standards-based 1000 Mb/s full-duplex
operation only.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.14
ATM and IP Network
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.15
IuPS over IP impacts synthesis
2 * 4pGE boards to be installed in RNC => uses two PS slots leading to possible capacity decrease depending existing RNC market model
the Bandwidth processing power per 4pGE board is 2.5 Gbps
Optical SFPs are required for RNC GE connectivity
Optional network taps can be installed on fiber links for tools connectivity (protocol analyzers) : RNC site
For IP path redundancy, external routers in front of the RNC are required i.e ALU SR 7750
An IP network is required:
may run in parallel with an ATM one if operator owns both type of networks (may be the case for existing customers)
The RNC existing IP addressing plan may be reviewed/extended to take into account:
The newly introduced M3UA/SCTP stack
The existing IuPS UP over IP over ATM
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.16
IuPSoIP and IuCSoIP description3
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.17
RNC IuPS over IP data path
IuPS VR
Localmedia(traffic type:ss7CPlane)
Localmedia(traffic type:rnc)
PDCPDCPDC
UserPlanePMC RABPMC RABPMC RAB
PP
PP
PP
4 port GE
LAN / VLAN
ControlPlane
A PSFP/DCPS FP is composed of 6 PMC and one PDC
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.18
RNC subnet sizes : Engineering inputs
PMC Ids PMC IdsSlot Card 1 2 3 4 5 6 Slot Card 1 2 3 4 5 6
0 CP 8 OC31 CP 9 OC32 PSFP PMC-M TMU RAB RAB PC RAB 10 PSFP RAB TMU RAB RAB PC RAB
subnet 0 x.y.z.81 x.y.z.82 x.y.z.84 subnet 0 x.y.z.31 x.y.z.33 x.y.z.34 x.y.z.36subnet128 x.y.z.209 x.y.z.210 x.y.z.212 subnet128 x.y.z.159 x.y.z.161 x.y.z.162 x.y.z.164
3 PSFP PMC-M TMU RAB RAB PC RAB 11 PSFP RAB TMU RAB RAB PC RABsubnet 0 x.y.z.75 x.y.z.76 x.y.z.78 subnet 0 x.y.z.25 x.y.z.27 x.y.z.28 x.y.z.30subnet128 x.y.z.203 x.y.z.204 x.y.z.206 subnet128 x.y.z.153 x.y.z.155 x.y.z.156 x.y.z.158
4 PSFP RAB TMU NI RAB PC OMU 12 PSFP RAB TMU RAB RAB PC TMUsubnet 0 x.y.z.67 x.y.z.70 subnet 0 x.y.z.19 x.y.z.21 x.y.z.22subnet128 x.y.z.195 x.y.z.198 subnet128 x.y.z.147 x.y.z.149 x.y.z.150
5 PSFP RAB TMU NI RAB PC OMU 13 PSFP RAB TMU RAB RAB PC TMUsubnet 0 x.y.z.61 x.y.z.64 subnet 0 x.y.z.13 x.y.z.15 x.y.z.16subnet128 x.y.z.189 x.y.z.192 subnet128 x.y.z.141 x.y.z.143 x.y.z.144
6 PSFP RAB TMU RAB RAB PC RAB 14 4pGEsubnet 0 x.y.z.55 x.y.z.57 x.y.z.58 x.y.z.60subnet128 x.y.z.183 x.y.z.185 x.y.z.186 x.y.z.188
7 PSFP RAB TMU RAB RAB PC RAB 15 4pGEsubnet 0 x.y.z.49 x.y.z.51 x.y.z.52 x.y.z.54subnet128 x.y.z.177 x.y.z.179 x.y.z.180 x.y.z.182
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.19
Engineering rules for assigning SCTP associations (1/2)
It is recommended that each DPC be assigned at least two SCTP associations. The two associations that lead to the same DPC must be assigned to two different PSFP (or PDC) cards. This provides protection for the associations against PSFP (or PDC) card failures.
On the RNC, PSFP cards will be paired for the purpose of 1:1 sparing distribution and software migration (this configuration called the “SPLIT SHELF” is not yet supported in UA6). PSFP pairs will be slots 2 & 3, 4 & 5, 6 & 7, 10 & 11 and 12 & 13 (slots 0 & 1 are reserved for the CP cards, slots 8 & 9 for the ATM line cards and slots 14 & 15 for the GigE cards). Therefore, as a good engineering practice in order to plan future sofware releases, when two or more SCTP associations are configured to a DPC, it is recommended that they be assigned to different PSFP pairs.
SCTP associations must not be assigned to PSFP cards 4 & 5 where the NI resides.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.20
Engineering rules for assigning SCTP associations (2/2)
All SCTP associations should be evenly distributed across PSFP cards so that, roughly speaking, each PSFP supports a similar traffic load.
Adding a new pair of PSFPs to the RNC is an opportunity to rebalance the distribution of SCTP associations across the PSFP cards as per the above guidelines. This may be performed at the time of PSFP card addition or at a later time.
Only 2 outgoing streams and 2 incoming streams within an SCTP association will be supported. One outgoing/incoming pair is used for M3UA management and the other pair is used for transmitting/receiving user data.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.21
PDC
localmedia
IuPS CP over IP – direct connectivity (no Signalling GW)
potential physical pathspacket routing for association1packet routing for association2
The Network Interface (NI) component has an active and hot spared M3UA instance within the RNC. There are up to 8 Processor Daughter Cards (PDCs), each of which has one or more active SCTP endpoints. The M3UA layer load shares over redundant associations to each Destination Point Code and monitors the states of the associations. There are two active 4-port Gigabit Ethernet cards with redundant links to the edge routers. Protected default routes are used to guard against GigE card, link and adjacent router failures.
IP path redundancy is managed by PDR (at a time all SCTP associations are carried over the same link in case above). PDC (and then SCTP associations) redundancy is managed by having at least 2 PDC to the same destination.
.
.
.
SGSN1 IP Network
Router1
PDC1SCTP EPT1
PDC8SCTP EPT8
GigE1
GigE2
NI(a)
M3UA
RNC
SCTP EPT
SCTP EPT
assoc1
Router2
usable associations
VR PP
PP
PP
assoc2 PDR
assoc2
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.22
General Considerations for IP addressing 1/2
RNC - IU-PS Control Plane: • In RNC, SCTP is terminated on PDC (except those on PSFPs that have NI PMCs): 1 IP address
per PDC is required.• An SCTP is identified by an IP address and the SCTP port number.• As associations are always initiated by the RNC, the RNC needs to know which IP address/ port
number of the peer M3UA node to send the SCTP INIT chunk : Peer M3UA Process and Entity (PMP & PME) provisioning is required.
ATM / IP IuFlex mix restriction: • CP and UP for one PS call use either ATM or IP but no mix between ATM and IP With 2 IuPS instances on your RNC, to force calls to always go a specific core, lock the other instance using NSP GUI.With both IuPS instances unlocked, PS traffic will be load-shared between the 2 cores based on the weightings assigned
in the Iu Flex provisioning (capacityIndication value under PsCoreNetworkAccess – the higher the value, the more likely the call will go to that PS Core).
RNC - IU-PS User Plane: • In RNC, GTP-U is terminated on PMC-RAB (dynamically allocated, per call).• Each RAB as its own IP address and manage several GTP endpoints (GTP TEID).• The same UP IP addresses are used for IUPS over IP/Ethernet and for IUPS over IP/ATM.• Max configuration, with GigE IP cards == 32 PMC-RABs• The User Plane IP addresses are provided by the RANAP protocol:
• RANAP RAB assignment Request CN transport layer IP address with GTP TEI CN.• RANAP RAB assignment Response RNC PMC RAB IP address with GTP TEI RNC.
RNC PsCoreNetworkAccess/0 (ATM) capacityIndication 1 to 100 (initial 1) RNC PsCoreNetworkAccess/1 (IP) capacityIndication 1 to 100 (initial 1)
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.23
General Considerations for IP addressing 2/2
RNC - IU-CS User Plane:
In RNC, RTP is terminated on Protocol Port IUBUPLANE relayed internal to PMC RAB using
IUBUPLANEINT.
The User Plane IP addresses are provided by the RANAP protocol:
RANAP RAB assignment Request CN transport layer IP address and BindingID CN.
RANAP RAB assignment Response RNC PMC RAB IP address and BindingID RNC.
Each BindingID will be used by RNC and CN as source/dest UDP RTP port
Source: my understanding from wireshark IuCS trace No docs yet since Tested on fast feature for CUTC UA6 IPRAN
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.24
Iu flex – CoreNetworkInstance
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.25
IuoIP Control plane (CS or PS call establishment)
Vr/1
Pp/SS7CPLANE ( LocalMedia If/7 )
Pp/LOCALMEDIA (LocalMedia If/0)
OC-3 - card0 15 pX 4pGE – card
(PS u-plane traffic)
10.32.1.33
172.xx.1.126
172.0.1.254
NodeB/UE side Core side
Sctp/m3ua/sccp stack
SGSN gigE card
cplane
IUB Interface(ATM)
NBAP + UENBAP= controlUE: direct tranfer
RANAP control
Pp/ETH_XXX e.g. (La/140) ca/14 p0
SCTP (on PDCs):172.0.1.241 172.0.1.242172.0.1.243 …
Giga Ethernet port (SX or LX)
NEW
PS SCTPassoc CS SCTP
Assoc
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.26
IuPSoIP – user plane (after call is established)
AAL2/ AAL5
NodeB/UE side Core side
Sctp/m3ua/sccp stack
cplane
IUB Interface(ATM)
Vr/1
Pp/SS7CPLANE ( LocalMedia If/7 )
Pp/LOCALMEDIA (LocalMedia If/0)
OC-3 – card 80 15 pX 4pGE – card
RABS; dyn. Allocated:172.xx.1.60, 61, 75…
(PS u-plane traffic)
172.xx.1.126
Pp/ETH_XXX e.g. (La/140) ca/14 p0
IuUp_PS(uplane)
Traffic(uplane)
uplane
RLC/ MAC/ FP; aal2 packets
Ip packets (through gtp)
IP port
SCTP (on PDCs):172.0.1.241 172.0.1.242172.0.1.243 …
10.0.100.254
172.0.1.254
IP_MUX
default route
NEW
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.27
IuCSoIP – user plane (after call is established)
NodeB/UE side Core side
Sctp/m3ua/sccp stack
cplane
IUB Interface(ATM)
Vr/1
Pp/SS7CPLANE ( LocalMedia If/7 )
Pp/LOCALMEDIA (LocalMedia If/0)
OC-3 – card0 15 pX 4pGE – card
172.xx.1.126
Pp/ETH_XXX e.g. (La/140) ca/14 p0
IuUp_CS(uplane)
Traffic(uplane)
uplane
RLC/ MAC/ FP; aal2 packets
IP packets (through UDP/RTP)
IP port
SCTP (on PDCs):172.0.1.241 172.0.1.242172.0.1.243 …
10.0.100.254
172.0.1.254
IP_MUX
default route
NEW
Pp/IUBUPLANE (LocalMedia If/5)
Pp/IUBUPLANEINT (LocalMedia If/6)
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.28
IuCSoIP using Hybrid IuB internal RNC pipes
IuCSoIP (fast feature development only using patched sw modules) for now which can not be used:
- when Hybrid IuB is configured
- or when HSDPA / HSUPA is activated at RNC fddCell side
IuCSoIP User plane is using RNC internal Hybrid IuB protocol ports:
- Pp/IUBUPLANE
- Pp/IUBUPLANEINT
IUPSoIP and IuCSoIP are working fine together for Multi-RAB but no HSDPA call can demontrated when IuCSoIP is configured.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.29
IuCSoIP no configuration wizzard yet available using WIPS
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.30
Hybrid Iub Overview
This feature introduces a hybrid transport (ATM & IP) on the Iub interface on the iBTS.
In the hybrid Iub interface:
- the R99 CS and PS, signaling and OAM traffic remains on the ATM/PCM
- the HSPA (HSDPA and E-DCH) is supported on IP/Ethernet.
Hybrid Iub requires the xCCM in the BTS.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.31
Hybrid IuB: ATM and IP flow seperation
Node B RNC
ATM Network Domain
IP/Ethernet Domain
NBAP: NCP and CCP
Common Channels: FACH, RACH, Paging
SRB and TRB DCH
HSDPA & E-DCH I/B Traffic
BTS U-PLANE IP@ + UDP#(IP @ is configured)
RNC U-PLANE IP@ + UDP#(IP@ is configured)
E-DCH GBR Traffic
HSDPA GBR traffic
ALCAP
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.32
SCTP, M3UA4
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.33
SIGTRAN SCTP terminology (reminder)
•Tranport address: combination of SCTP port IP address (IPv4, IPv6)
•Association: SCTP connection between 2 endpoints
•Path: route taken from one host to a specific destination transport address of its peer
•Stream: unidirectional logical channel, usually in-sequence delivery; unordered delivery possible
•Chunk: unit of information within an SCTP packet, consisting of a chunk header and specific content
Ref: SCTP for Beginners (google: SCTP Beginners)http://www.sctp.dehttp://www.sctp.org
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.34
Illustration of SCTP streams, packets and chunks
Message 1 Message 2
SCTP
Com
m
on Heade
r
Data Chunks
SCTP PDU
SCTP
Contro
l Chunk
s
Data
Chunks
Headers
IP
IP datagram
IP Layer IP Layer
User layer
SCTP layer
SCTP Endpoin
t
SCTP Endpoin
t
SCTP Association
User layer
User Data
Uses
Rx Streams
Tx
Rx
Tx Streams
SCTP layer
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.35
M3UA Terminology (RFC 4666)
Application Server (AS) – A logical entity that represents an application utilizing the
services of the signalling transport.
Application Server Process (ASP) – A process instance of an Application Server. An
ASP contains an SCTP endpoint which means an ASP processes traffic coming from an
SCTP association. For redundancy reasons there may be more than one ASP in an AS.
IP Server Process (IPSP) – Similar to an ASP, it is a process instance of an IP-based
application that uses M3UA in a point-to-point fashion. The key difference between an
ASP and an IPSP is that an IPSP does not depend on the services of an SG.
Routing Key and Routing Context – A Routing Key consists of a set of SS7
parameters used to define a range of signalling traffic to be handled by a particular
Application Server. There is a 1:1 relationship between an AS and a Routing Key. A
value that uniquely identifies a Routing Key is called Routing Context. Routing Keys and
Contexts may be statically provisioned or dynamically registered between M3UA peers.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.36
M3UA Signalling Gateway (SG) and Application Server (AS)
Signalling Gateway
SG is a signalling agent capable of sending/receiving legacy SS7 messages at the edge of the SS7/IP network.
SG contains one or more Signalling Gateway Process (SGP) serving as active, backup, loadshare or broadcast processes
Application Server
AS is a logical entity, such as a virtual switch or database element capable of handling call processing, transaction for a specific routing key
AS is identified by a routing key, which is a set of SS7 parameters such as SIO/DPC/OPC/SSN
AS is modelled as 1 or more Application Server Processes (ASP) , SGP or IP Server Process (IPSP)
SGP1
SGP2
ASP1
ASP2
SS7 IP
SG AS
IPSP1
IPSP2
AS
IPSP1
IPSP2
AS
IP
IP
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.37
Relations of xS, xSP and SCTP endpoints in M3UA arch.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.38
root
SS7
Mtp3/1
ServInd/3
Sccp/1
Rem/n
Mtp3C
M3uaC
M3ua/1
ServInd/3
DestSP/n
Sctp/n
existing component
new component
modified component
service link
dynamic component
Legend:
SrcEP/n
Assoc/n
SctpPath/n
Lp/n
PMP/n PME/n
RNC Provisionning model
n=0 to 15 to allow mapping on LP Only 8 can be configured
n=0 to 511 up to 8 IP @
n=0 to 7
1 IP @
Dynamic component
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.39
Example
IP network
RNCopc=5
dpc=1
dpc=3
ss7 m3ua/1 pmp/0 assoc/0
ss7 m3ua/1 pmp/0 assoc/1
ss7 m3ua/1 pmp/2 assoc/0
ss7 m3ua/1 pmp/3 assoc/0
dpc=2
ss7 m3ua/1 pmp/1 assoc/0
ss7 m3ua/1 pmp/1 assoc/1
« PME domain »
Pme 0
Pme 1
Pme 2
SG
pmp0
pmp1
srcEP1
srcEP2
pmp2
pmp3
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.40
IPSP Configuration detail for SS7 Point Code
SGSN Core NetworkRNC (IPSP)
IPSP AS
1PC = 4 ASP ASP
ASPASPPC 91
d -p ss7 m3ua/1 destSp/0Ss7 M3ua/1 DestSP/0 protocolVariant = itu destPointCode = 91 networkIndicator = International linkToPeerM3uaEnt = Ss7 M3ua/1 PME/0
d -p Ss7 M3ua/1 Ss7 M3ua/1 origPointCode = 4 ackTimer = 60 seconds recoveryTimer = 2 seconds seqCtrlTimer = 800 msec heartBeatTimer = disabled
172.0.1.24110.0.100.129
10.0.100.130172.0.1.242
PDC, sctp/2
PDC, sctp/3
Proposed Std M3UA configuration: IPSP, 2 associations, 2 different sctps (ASPs) on diff PDCs, 2 pmps (ASPs) on core side.
Proposed Std M3UA configuration: IPSP, 2 associations, 2 different sctps (ASPs) on diff PDCs, 2 pmps (ASPs) on core side.
Pmp/0
Pmp/1
1
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.41
Components Statistics
ss7 m3ua/* pmp/* assoc/* sctpassoc assoc stateprimaryPath (pPath) inboundStreams (ibs) outboundStreams (obs)
closed cookieWait initChunksTx (initTx) initChunksRx (initRx) cookieSent shutdownChunksTx (sdTx) shutdownChunksRx (sdRx) cookieEchoed bytesToUpperLayerProtocols (bToUL) established bytesFromUpperLayerProtocols (bFrUL) shutdownPending fragmentedUserMsgs (fragMsgs) shutdownSent reassembledUserMsgs (reassemMsgs) shutdownReceived segmentsTx (segTx) segmentsRx (segRx) shutdownAckSent
pmp pmpstateM3uaDataMsgTx (m3uaDataTx) M3uaDataMsgRx (m3uaDataRx)
Down m3uaSsnmTx m3uaSsnmRx m3uaAspsmTx m3uaAspsmRx
Inactive m3uaAsptmTx m3uaAsptmRx m3uaMgmtTx m3uaMgmtRx
Active ss7 m3ua/* pmp/* assoc/* sctpPath/* destIpAddress pathStatus
dataChunksTx dataChunksRx heartbeatChunksTx heartbeatChunksRx
activeheartbeatAckChunksTx heartbeatAckChunksRx sackChunksTx sackChunksRx
inactiveRetransmittedChunks errorChunksTx errorChunksRx mostRecentRto
SCTP & M3UA RNC real time checks and counters
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.42
Core Network Table for M3Ua : 2 associations in IPSP mode
AS
Core Network side
ASP1 ASP2
IPSP
1 “link” per association (nomultihoming)
Descr = ASP no 2Node ID =2Script port (to SCTP) = 1
Descr = first ASPNode ID = 1Script port (to SCTP) = 1
PDC2 Note: RNC - PDC IP addresses to use,172.0.1.241 172.0.1.242172.0.1.243172.0.1.244 …
Device under Test:Routing Key DPC= 91 (DEC)Routing Key OPC= 4 (DEC) (Routing Key SI=3 (SCCP) / SS= 0 Routing Context: 10 rncId hardcoded)Traffic Mode type: LoadshareMin. Active ASP=1
(aliasList for Link) IP address – Port NoLink1 - Remote ASP : 172.0.1.241 2905 (RNC)
- Local ASP: 10.0.100.129 2905 (SGSN)
1 1(aliasList for Link) IP address – Port NoLink1 - Remote ASP : 172.0.1.241 2905 (RNC)
- Local ASP: 10.0.100.130 2905 (SGSN)
172.0.1.242
10.0.100.129 10.0.100.130
RNC side
M3UA Simulated IPSP:UseNetworkAppearance = False (i.e. 1 network) UseRoutingContext = False (RNC doesn’t)NumMaxStreams=2 (default)RoutingKeyDPC (DEC) =91RoutingKeyOPC (DEC) =4(routing key SI=3, SS=0, Context=10)Traffic Mode = LoadshareMin. Active ASP = 1Destination Point Code =91 (DEC)User port =3
PDC3
172.0.1.241
LP/2 LP/3
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.43
M3UA IPSP/ASP and M3UA Multi-Homing or Multi SCTP association
M3UA can act either as IPSP (point-to-point connection with SGSN) or as
ASP (connection via SG).
In case of IPSP, there is no need to support Routing Key management.
In case of ASP-SGP, only Routing Key static configuration at SGP is supported (no
registration procedure).
Multi-homing helps to resolve route failure in the network but does not help to
resolve board failure in the RNC
Furthermore, today other protocols like VRRP (Virtual Routing Redundancy
Protocol) permit to achieve network redundancy.
Then multi-homing on RNC side is not needed (one single IP address per
association on RNC side) but the RNC shall support a multi-homed
SGSN as described in 4.4.2 (address management at association setup, path
selection, path and peer monitoring).
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.44
IPSP Configuration detail (1 to 2 with multi-homing)
SGSNRNC (IPSP)
IPSP
AS1 to 2PC = 4
# links (multi-homing)
ASP ASPASP
2 assoc. :diff PDCs, 1 IP address each 2 ASPs, 2 IP addresses each on SGSN
PC = 91
(1) PME(1) DestSp = 91(2) PMPs, 2 associations (1 each) + 2 IP
addresses each (multi-homing).
d -p ss7 Sctp/* SrcEp/1 ip, assocs+====+----------------+---------------------|Sctp| ip | assocs+====+----------------+---------------------| 3|172.0.1.241 |Ss7 M3ua/1 PMP/0 Assoc/0| 6|172.0.1.242 |Ss7 M3ua/1 PMP/1 Assoc/0
d -p Ss7 M3ua/1 PME/*+===+--------------------+---------------------+------+----|PME| lToDestSp | pmps | red |minA+===+--------------------+---------------------+------+----| 0|Ss7 M3ua/1 DestSP/0 |Ss7 M3ua/1 PMP/0 |loadsh| 1| | |Ss7 M3ua/1 PMP/1 | |
d -p Ss7 M3ua/1 PMP/* ass/* linkToSourceEndPoint+===+=====+--------------------+----------------------------|PMP|Assoc| ep |Response+===+=====+--------------------+----------------------------| 0| 0|Ss7 Sctp/3 SrcEp/1 || 1| 0|Ss7 Sctp/6 SrcEp/1 |
d -p Ss7 M3ua/1 PMP/*+===+---------------------+----------------+-----+----|PMP| pmpToPmes | pIpAddr |pPort|type+===+---------------------+----------------+-----+----| 0|Ss7 M3ua/1 PME/0 |10.0.100.129 | 2905|ipsp| | |10.0.100.133 | || 1|Ss7 M3ua/1 PME/0 |10.0.100.130 | 2905|ipsp| | |10.0.100.134 | |
ASP1 to 2
1 IP addr / assoc.2 IP addrs / assoc.
Multi-homing
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.45
SCTP, M3UA, RANAP call flow establishment5 SCTP, M3UA and RANAP
establishment5
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.46
SCTP establishment
Client (RNC) Server
(CN)
------------ INIT -------------------->
<-------- INIT-ACK -----------------
---- COOKIE-ECHO/data ------>
<------ COOKIE-ACK/data -------
------------ HEARTBEAT---------->
<-------- HEARTBEAT-ACK --------
------------ HEARTBEAT---------->
<-------- HEARTBEAT-ACK --------
…
So far there are 13 chunk types defined for standard use:ID Chunk Type ----- ---------- 0 Payload Data (DATA) 1 Initiation (INIT) 2 Initiation Acknowledgement (INIT ACK) 3 Selective Acknowledgement (SACK) 4 Heartbeat Request (HEARTBEAT) 5 Heartbeat Acknowledgement (HEARTBEAT ACK) 6 Abort (ABORT) 7 Shutdown (SHUTDOWN) 8 Shutdown Acknowledgement (SHUTDOWN ACK)9 Operation Error (ERROR) 10 State Cookie (COOKIE ECHO)11 Cookie Acknowledgement (COOKIE ACK) 12 Reserved for Explicit Congestion Notification Echo (ECNE) 13 Reserved for Congestion Window Reduced (CWR)14 Shutdown Complete (SHUTDOWN COMPLETE) 15-255 Reserved
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.47
M3UA Establishment (RC 4666)
IPSP (RNC) ASP (SGSN or MSC)
|-------------ASP Up---------------->|
|<----------ASP Up Ack--------------|
|<----NTFY(AS-INACTIVE)(RCn)---|
|-------- ASP Active(RCn)--------->|
|-----ASP Active Ack (RCn)------->|
|-----NTFY(AS-ACTIVE)(RCn)----->|
…
|-------------M3UA BEAT----------->|
|<----------M3UA BEAT Ack---------|
RCn: Optional Routing Context Number
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.48
Beijing UIIV Lab IuPSoIP and IuCSoIP single association example
SGSNRNC (IPSP)
IPSP AS1 to 1PC = 500 ASP
ASPASP
PC = 2
d -p ss7 Sctp/* SrcEp/1 ip, assocsSs7 Sctp/* SrcEp/1+====+----------------+---------------------|Sctp| ip | assocs+====+----------------+---------------------| 2|10.32.1.65 |Ss7 M3ua/1 PMP/0 Assoc/0| 3|10.32.1.66 |Ss7 M3ua/1 PMP/1 Assoc/0
d -p Ss7 M3ua/1 PME/*+===+--------------------+---------------------+------+----|PME| lToDestSp | pmps | red |minA+===+--------------------+---------------------+------+----| 0|Ss7 M3ua/1 DestSP/0 |Ss7 M3ua/1 PMP/0 |loadsh| 1
| 1|Ss7 M3ua/1 DestSP/1 |Ss7 M3ua/1 PMP/1 |loadsh| 1
d -p Ss7 M3ua/1 PMP/* ass/* linkToSourceEndPoint+===+=====+--------------------+----------------------------|PMP|Assoc| ep |Response+===+=====+--------------------+----------------------------| 0| 0|Ss7 Sctp/2 SrcEp/1 || 1| 0|Ss7 Sctp/3 SrcEp/1 |
d -p Ss7 M3ua/1 DestSP/*+======+-------+----------+------+----------------|DestSP|variant| dpc |netInd| lToPme+======+-------+----------+------+----------------| 0|itu |2 |nation|Ss7 M3ua/1 PME/0| 1|itu |1 |nation|Ss7 M3ua/1 PME/1
1 to 1
MSC
AS PC = 1ASP
d -p Ss7 M3ua/1 PMP/*+===+---------------------+----------------+-----+----|PMP| pmpToPmes | pIpAddr |pPort|type+===+---------------------+----------------+-----+----| 0|Ss7 M3ua/1 PME/0 |10.0.100.1 | 2905|ipsp| 1|Ss7 M3ua/1 PME/1 |10.0.102.1 | 2905|ipsp
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.49
Wireshark SCTP and M3UA initialization example
10.32.1.65: RNC PS src SCTP assoc IP addr10.0.100.1: SGSN PS SCTP assoc IP addrSGSN PC: 2RNC PC: 500
10.32.1.66: RNC PS src SCTP assoc IP addr10.0.102.1: MSC CS SCTP assoc IP addrMSC PC: 1(MSC not in use in that trace snapshot)
M3UA BEAT message sent by RNC before M3UA is ACTIVE is just ignored (no ERR sent) by ALU SGSN
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.50
M3UA - IPSP server, 1ASP -- SCCP sync (message flow)
AssocUpNotify
IP - SCTP M3UA SCCP(PC=91)
M_SCTP_ESTABLISH_IND
M_ASP_UP_IND
M_AS_INACTIVE_IND
M_ASP_ACTIVE_IND
M_AS_ACTIVE_IND
ASP UP (asp_id, info_string)
UP_ACK=[info_string]
NTFY: AS_State_Change=AS_Inactive
ASP_ACTIVE=[LoadShare + routing_cntxt value [=10]
ASP_ACTIVE_ACK
NTFY=[AS_State_Change=AS_Active]
M3ua mngmt
M_AS_RESTART
AS ACTIVE
ASP ACTIVE
ASP UP
SCTP association is up
ASP is up
AS is inactive
ASP is active
AS is active
interlayer restart_begins sio=#3 opc=91
Client: SCTP ESTAB REQ
ASP UP CONF
ASP ACT REQ
ASP ACT CONF
AS ACT IND
InitIndication=[SctpInstanceNum=1]
SetOutStream=[SctpInstanceNum=1 OutBoundStrCount=2]{2}
{3}
(asp_id)
(asp_id)
(asp_id)
(as_id)
(as_id)
(as_id)
M_NOTIFY_IND asp_id, AS_State_Change=AS_Inactive
See next pageSctpInstanceNum, INACTIVE
Trigger to M3ua_init context to restart SCCP layer
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.51
IPSP server, 1 ASP -- M3UA + SCCP initialization (message flow)
IP - SCTP M3UA SCCP(PC=91)
M3ua mngmt
Client: sccpsetup
interlayer restart_begins sio=#3 opc=91{3}SctpInstanceNum, INACTIVE
interlayer restart_ends sio=#3 opc=91{3}
…
UDT sio=#c3 dpc=4 opc=91 sls=0 ro_pcl=$00 CDA=[AddrInd…] CGA=[AddrInd…] DATA=[SCMG SST assn=#8e apc=4 smi=#00]
UDT sio=#c3 dpc=91 opc=4 sls=0 ro_pcl=$00 CDA=[AddrInd…] CGA=[AddrInd…] DATA=[SCMG SSA assn=#8e apc=4 smi=#00]
Sub-system Test msgs
Sub-system Allow msgs
To ranap( SCCP ready )
M3UA service_indicator=SCCP
(accepted)
SctpInstanceNum, ACTIVE
Inact ack
Act ack
From previous page
(or)UDT sio=#c3 dpc=91 opc=4 sls=0 ro_pcl=$00 CDA=[AddrInd…] CGA=[AddrInd…]
DATA=[SCMG SSA assn=#8e apc=4 smi=#00] SSA first, then no need for SST
M3UA service_indicator=SCCP
M3UA service_indicator=SCCP
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.52
SCCP SSA and RANAP RESET
10.200.1.66: RNC CS src SCTP assoc IP addr10.0.100.1: MSC CS SCTP assoc IP addrMSC PC: 1RNC PC: 200
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.53
SCTP, M3UA, RANAP call flow establishment5 External router static route
configuration example6
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.54
Router table towards RNC (only static route supported in RNC)
TWO “redundant” static route with two Metric allowing one to be used at a time in each
router dynamic routing table
PDR Config: Metric 5 (card 14) and Metric 10 (card15)
ip static-route create 10.32.1.64/255.255.255.240 next-hop 10.31.1.33 cost 5 preference 5
ip static-route create 10.32.1.64/255.255.255.240 next-hop 10.31.1.37 cost 10 preference 10
2 static route for IuPSoIP User Plane LOCALMEDIA 10.150.33.128/25 (one only if no PDR
used)
ip static-route create 10.150.33.128/255.255.255.128 next-hop 10.31.1.33 cost 5 preference 5
ip static-route create 10.150.33.128/255.255.255.128 next-hop 10.31.1.37 cost 10 preference 10
2 static route for IuCSoIP User Plane IUCSUPLANE 120.10.11.1 (one only if no PDR used)
ip static-route create 120.10.11.1/255.255.255.255 next-hop 10.31.1.33 cost 5 preference 5
ip static-route create 120.10.11.1/255.255.255.255 next-hop 10.31.1.37 cost 10 preference 10
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.55
SR7750 Iu-PSoIP configuration and PDR static route example
interface "IuPS to RNC4369 vlan 696" create
address 10.69.1.22/30
sap 1/1/3:696 create
interface "IuPS to RNC4369 vlan 695" create
address 10.69.1.18/30
sap 1/1/1:695 create
interface "Iu-UP to SGSN1" create
address 10.0.2.2/29
sap 2/1/19 create
interface "Iu-CP to SGSN1 stnC/D eth2" create
address 10.0.1.1/29
sap 2/1/20:110 create
interface "Iu-CP to SGSN1 stnC/D eth3" create
address 10.0.1.33/29
sap 2/1/20:111 create
static-route 10.69.1.0/28 next-hop 10.69.1.17 cpe-check
10.69.1.17 drop-count 2 metric 5
static-route 10.69.1.0/28 next-hop 10.69.1.21 cpe-check
10.69.1.21 drop-count 2 preference 10 metric 10
static-route 172.253.69.0/24 next-hop 10.69.1.17 cpe-
check 10.69.1.17 drop-count 2 metric 5
static-route 172.253.69.0/24 next-hop 10.69.1.21 cpe-
check 10.69.1.21 drop-count 2 preference 10 metric 10
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.56
RNC 4pGe card PDR (Protected Default Route)
PDR (Protected Default Route) is used in the RNC for IP flows over 4pGe Card. It is
defined as an IP static default route (identified by the destination address 0.0.0.0) with
two or more (up to 4) outbound IP interfaces (next hops) for forwarding IP traffic. The
set of next hops are used to protect IP flows with static routing during the route convergence caused by port failures, card failures and software migration. Each
next hop uses a unique IP subnet. At any time, only one port/interface is selected as the active forwarding port/interface for a specific IP flow.
Added Note:
On each default route an IP routing priority is configured using the metric (or cost
in PP8600) and preference (both RNC and Router have to be configured with the
same metric and preference). The most priority route being the one with IP active
connectivity of the lowest metric-cost value.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.57
Static ARP if needed towards Core Network (if not supporting other routing)
RAN 4
ip arp add ports 3/10 ip 10.0.103.1 mac 00:03:a2:95:02:01 vlan 103 (RAN4 IUCS UserPlane CN)
ip arp add ports 3/10 ip 10.0.102.1 mac 00:03:a2:95:02:01 vlan 103 (RAN4 IUCS CPlane CN)
ip arp add ports 3/10 ip 10.0.101.1 mac 00:03:a2:95:02:01 vlan 103 (RAN4 IUPS UserPlane CN)
ip arp add ports 3/10 ip 10.0.100.1 mac 00:03:a2:95:02:01 vlan 103 (RAN4 IUPS CPlane CN)
RAN 200
ip arp add ports 3/10 ip 10.1.103.1 mac 00:03:a2:95:02:01 vlan 103 (RAN200 IUCS UserPlane CN)
ip arp add ports 3/10 ip 10.1.102.1 mac 00:03:a2:95:02:01 vlan 103 (RAN200 IUCS CPlane CN)
ip arp add ports 3/10 ip 10.1.101.1 mac 00:03:a2:95:02:01 vlan 103 (RAN200 IUPS UserPlane CN)
ip arp add ports 3/10 ip 10.1.100.1 mac 00:03:a2:95:02:01 vlan 103 (RAN200 IUPS CPlane CN)
mac 00:03:a2:95:02:01 vlan 103 SGSN mac address ethernet single Interface (SGSN) and associated VLAN 103 router identification
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.58
SCTP, M3UA, RANAP call flow establishment5 RNC Carrier Grade7
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.59
IP Protected Default Route redundancy
RNC uses Protected Default Routes (PDR) to provided IP route failure protection at Layer 3 PDRs are IP static default routes with 2-4 next hops for forwarding
IP traffic.
PDRs protects against (~1 second outage) 4pGE card and port failure Adjacent router failure Hitless software migration (future)
Heartbeat Monitoring Mechanism ICMP echo requests are used to detect adjacent router failures heartbeat polling (configurable) an alarm will be generated by Vr Ip Static Route NextHop for the
heartbeat failure
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.60
IP Protected Default Route redundancy
PDR constraints
Up to 2 VR instance can be supported with PDR Up to 4 next hops (interfaces) can be provisioned per
PDR Up to 4 VLAN per GE link can be supported with PDR PDRs are not compatible with ECMP enabled
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.61
Iu PS over IP User Plane – coexistence with ATM based IuPS
4pGE
4pGE
Active
Standby
PP3
PP4
PP1
PP2
VR16pOC3 To ATM SGSNs
PDR (w/o Heartbeat): 0.0.0.0 nh1 prio1 nh2
prio2
IP/Ethernet Domain
IP/ATM Domain
nh1
nh2
Dest. :e.f.g.h
Dest. : a.b.c.d
Best match routes :a.b.c.d nhw prio1 nhx prio2 e.f.g.h nhy prio1
nhz prio2
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.62
Four-port Gigabit Ethernet (GE) with Protected Default Route (PDR)
X : Faults detected without heartbeat causing route to backup to R2
X: Faults detected with heartbeat (needed in case of L2 intermediate eqpt) causing route to backup to R2
Note : - heartbeat ONLY available on ProtectedDefaultRoute (PDR)
- PDR does NOT support ECMP
If metric1 < metric 2, IP path default through R1
Route :0.0.0.0 NH1=R1 metric1 NH2=R2 metric2
4pGE
4pGE
Active
R2
R1
heartbeat
Active
RNC
Subnet 2 (/30)
PP2
Subnet 1 (/30)
VR
PP1
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.63
Optical Giga Ethernet to Wire Ethernet conveters
It is possible in case of Optical Giga Ethernet connectivity issue to the facing RNC router to use ‘conveter boxes’.
Such ‘conveter box’ will just simply conveter the optical GigE signal to wire Ethernet commonly use IP connection.
When testing PDR by RNC card reset or GiGE port lock or fiber disconnection this conveter box will mask the failure created at RNC side to the router because the ethernet signal never does down due to optical side being down.
Therefore such ‘conveter box’ can’t be used for PDR testing.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.64
Use of Conveter boxes for LX module facing PP8600 SX module
RNC
LP/144pGe Cards
LP/154pGe Cards
ETH/0
ETH/3
ETH/0
ETH/3
Converter box
GiGe <> Eth
Converter box
GiGe <> Eth
BTS ROUTERPP8600
XCCM
ETH
ETH
GigE
ETH
GiGE
LX
SX
LX
SX
ETH
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.65
SCTP, M3UA, RANAP call flow establishment5 GTP within UMTS7
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.66
ATM/IPATM/IP
GTP in the UMTS Network
UTRANUTRAN
IP NetworkIP Network
Uu
HLRHLR
OtherOtherPLMNPLMN
SGSNSGSNservingserving
GGSNGGSNGatewayGateway
GSNGSN
Iu-PS
Gc
GiGn
GSNGGSNSGSN
GPRS Support NodeGateway GSNServing GSN
DataSignaling
Gr
Gp
IPIPBackboneBackbone
Gp
Gn
PLMN: Public Land Mobile Network
Gn == Interface between GPRS Support Nodes (GSNs) within a PLMNGp == Interface between GPRS Support Nodes (GSNs) in different PLMNs
NEW: Direct GTP tunnels can now be established between RNC and GGSN
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.67
Appl. Appl.
GTP-C
UDP
IP
MAC
RF
MS RNC/NodeB SGSN GGSN MG
GTP-C
UDP
IP
SCCP
MTP3B
RANAP
SCCP
MTP3B
MAC
RF
L2
L1
L2
L1
Airlink Iu-PS Gn Gi
RLC RLC
AAL-5
ATM
AAL-5
ATM
L2
L1
L2
L1
GPRS Tunneling Protocol (29.060)•Access/core network control PDU tunelling•Tunnel creation/deletion
Transport (25.412, 25.414)•Based on ATM virtual circuits•AAL-2/5 packet encapsulation•Wide selection of physical layers
RANAP Signaling Protocol (25.413)•Access/core network control PDU tunneling
SAAL-NNI SAAL-NNI
RRM RRM
RANAP
Source GTP_presentation.ppt
UMTS Protocol Stack – GTP-C (Gn) Control Plane
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.68
IP/UDP/GTP Envelope
Appl
UDP
IP
Appl
UDP
IP
GTP
UDP
IP
MAC
RF
MS
RNC/NodeB SGSN GGSN
MG
GTP
UDP
IP
GTP
UDP
IP
GTP
UDP
IP
MAC
RF
L2
L1
L2
L1
Airlink Iu-PS Gn Gi
PDCP PDCP
AAL-5
ATM
AAL-5
ATM
L2
L1
L2
L1
GPRS Tunneling Protocol (29.060)
•Access/core network bearer PDU tunelling
•Tunnel creation/deletion
Transport Layer (25.412, 25.414)•Based on ATM virtual circuits•AAL-2/5 packet encapsulation•Wide selection of physical layers
Source GTP_presentation.ppt
UMTS Protocol Stack – GTP-U (Iu and Gn) Data Plane
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.69
Tunnel Endpoint IDentifier (TEID): unambiguously identifies a tunnel endpoint in the receiving GTP-U or GTP-C protocol entity .The receiving end side of a GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID values are exchanged between tunnel endpoints using GTP-C (or RANAP, over the Iu) messages.
GTP-U Message: GTP-U or user plane messages are exchanged between GSN pairs or GSN/RNC pairs in a path. The user plane messages are used to carry user data packets, and signalling messages for path management and error indication.GTP-PDU: GTP Protocol Data Unit is either a GTP-C message or a GTP-U message Signalling Message: any GTP-PDU except the G-PDU
Ref: 3GPP TS 29.060 V8.1.0 (2007-09) – GTP protocolGTP protocol
A GTP tunnel is identified in each node with a TEID, an IP address and a UDP port number. A GTP tunnel is necessary to forward packets between an external packet data network and an MS user.
Packet Data Protocol (PDP): network protocol used by an external packet data network interfacing to GPRS
GTP (GTP-C and GTP-U) is defined for the Gn interface, i.e. the interface between GSNs within a PLMN, and for the Gp interface between GSNs in different PLMNs. Only GTP-U is defined for the Iu interface between Serving GPRS Support Node (SGSN) and the UMTS Terrestrial Radio Access Network (UTRAN). GTP allows multi-protocol packets to be tunnelled through the UMTS/GPRS Backbone between GSNs and between SGSN and UTRAN.
On the Iu interface, the Radio Access Network Application Part (RANAP) protocol and signalling part of GTP-U are performing the control function for user plane (GTP-U).
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.70
IP Transport Option: In the IP transport option GTP-U over UDP over IP shall be supported as the transport for data streams on the Iu-PS interface.
The transport bearer is identified by the GTP-U TEID and the IP address (source TEID, destination TEID, source IP address, destination IP address).---The GTP-U protocol shall be used over the Iu interface toward the packet switched domain.
There are two options for the transport layer for data streams over Iu-PS:
1) ATM based Transport (ATM transport option)
2) IP based Transport (IP transport option)
The following figure shows the protocol stacks of the two options.
IP
AAL5
Physical Layer
ATM
Protocol Stack for the ATM transport option
UDP
Protocol Stack for the IP transport option
Data Link Layer
UDP
GTP-U GTP-U
Physical Layer
IPv6 (RFC 2460) IPv4 optional (RFC 791)
Figure 3. Transport network layer for data streams over Iu-PS.
Packet switched domain: Transport network user plane
Source 3GPP 25.414 spec: Data transport + transport signalling
When the Iu UP protocol layer uses the services of a GTP-U transport, it uses an established GTP-U tunnel for transferring frames between the GTP-U tunnel endpoints at both ends of the Iu User plane access points. The RANAP Control Plane signalling over Iu handles the signalling to establish and release the GTP-U tunnels.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.71
Wireshark traces snapshots8
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.72
RNC ATMSPY not Available in UA6.0 for IPRAN
16pOC3 RNC card ATMSPY tool is not available for migration to 4pGe RNC card to spy IPRAN protocol stacks such as SCTP/M3UA/RANAP over IP
Therefore an external SPY trace tool must be used such as WIRESHARK sniffer freeware.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.73
Wireshark RANAP decoding setup
Uncheck the boxe in SCTP preferences
Edit/Preferences/SCTP
Try heuristic sub-dissectors first
Show always control chunks (can be set or not if needed but it does not cause the no decoding of RANAP with IMSI-DIRECTORY protocol display instead)
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.74
Wireshark Decode UDP as RTP PDU
For some reason RTP is not automatically decoded by wireshark(although it can support RTP).
Inside wireshark, we can decode the RTP packets manually by selecting one UDP packet “decode as” then select RTP, and the RTP header information is OK.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.75
Mobile Originated PS over IP voice call (‘CN’ RAB Assignment Request)
SGSN user plane Ip address: 10.0.101.1
GTP TEI #2 for downlink user data of this activated PDP context
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.76
Mobile Originated PS over IP voice call (’RNC‘ RAB Assignment Response)
RNC local Media PMC RAB IP address: 10.150.33.203
GTP TEI #289h for downlink user data of this activated PDP context
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.77
PS Uplink data transfer (PMC RAB to SGSN using ‘SGSN activated PDP GTP TEI’
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.78
PS Downlink data (SGSN to RNC PMC RAB using ‘RNC activated PDP GTP TEI’
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.79
Mobile Originated CS over IP voice call (CN bindingID EA60h -> 60000 decimal)
MSC user plane transport processor IP address: 10.103.0.1
MSC bindingID 60000 decimal (UDP RTP user plane IP port)
Note: Re-used for all Iu-CS voice/video call per MSC design but could be different for each new call like the RNC does.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.80
Mobile Originated CS over IP voice call (RNC bindingID C0D7h -> 49367 decimal)
RNC user plane transport processor IP address: 120.10.11.1
RSC bindingID 49367 decimal (UDP RTP user plane IP port for that call)
Note: Next call will use 49368 UDP port at RNC side and so on.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.81
Mobile to Mobile Iu-CSoIP user plane multiple UDP ports and MSC single port
CS or video call 1 using UDP port 49178 and second one using UDP port 49179
MSC is using for both calls teh same port 60000.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.82
SRNS relocation without IUR (ue_involved)
UA6.0 feature tested with IuPSoIP and IuCSoIP:33814 Intra-Frequency Inter-RNC HHO without Iur
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.83
RNC UA6.0 load lineup with Patches for IuCSoIP and SRNS relocation no IuR
1> d-p sw
avList = base_RI60065, atmNetworking_RI60065,
genericUtilities_RI60065,ip_RI60065,
wanDte_RI60065, iRNC_RI60065,
networking_RI60065, ss7_RI60065,
wirelessCommon_RI60065, fabric_RI60065,
patch_RI60065, ethernet_RI60065,
secureShell_RI60065, ipsec_RI60065,
baseExt_RI60065084002, ss7Apc_RI60065084002,
RNCCiph_RI60065084002, apcBase_RI60065084002FF,
iRNCApc_RI60065084002FF, cnp_RI60065RELOCPT2,
cRNCApc_RI60065RELOCPT2
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.84
3GPP 23.060 CALL FLOW (applicable for PS, voice and video calls)
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.85
PS SRNS relocation Wireshark trace snapshot
Source RNC point code: 500Target RNC point code: 200SGSN point code: 2
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.86
Voice or Video call SRNS relocation Wireshark trace snapshot
Source RNC point code: 500Target RNC point code: 200MSC point code: 1
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.87
Terms and definition,Ottawa Config with ALU SGSN9
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.88
More IPRAN information and presentation
Additional presenation (Iu-PSoIP , Hybrid IuB)
https://wcdma-ll.app.alcatel-lucent.com/livelink/livelink.exe?func=ll&objId=43896097&objAction=browse&sort=name&viewTy
pe=1
UA07 IP Transport Functional Specification
https://wcdma-ll.app.alcatel-lucent.com/livelink/livelink.exe?func=ll&objId=49743485&objAction=browse
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.89
Terms
AS Application Server (M3UA)ASP Application Server Process (M3UA)CN Core NetworkECMP Equal Cost Multi PathGTP GPRS Tunnelling ProtocolGTP-C GTP ControlGTP-U GTP UserIMSI International Mobile Subscriber IdentityIP Internet ProtocolIPSP IP Server Process (M3UA)IPv4 Internet Protocol version 4IPv6 Internet Protocol version 6 M3UA MTP3 User Adaptation LayerNSAP Network Service Access PointPDP Packet Data ProtocolPDU Protocol Data UnitPLMN Public Land Mobile NetworkQoS Quality of ServiceRAB Radio Access BearerSFP Small Form-Factor Pluggable SG Signalling GatewaySGSN Serving GPRS Support NodeRANAP Radio Access Network Application PartTCP Transmission Control ProtocolTEID Tunnel Endpoint IdentifierTNL Transport Network LayerUDP User Datagram ProtocolUP User Plane--------
RNC specifics
PME PeerM3uaEntity
PMP PeerM3uaProcess
(ServInd) M3uaServiceIndicator
(DestSP) DestinationSignalingPoint
SrcEp SourceEndPoint (RNC)
SCTP Stream Control Tx Protocol(SCTP path, SCTP association)
M3UA MTP 3 User Adaptation
PDC RNC software element which providesinter-process communicationPMC-PDC, PDC-CP.The PDC is in charged of handlingSaalNNI and Sctp.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.90
Dot1.q – VLAN tagging
Dot1.q is based on protocol 802.1q
Multiplexing of several subnets (VLAN) over one connexion (in our case an optical connexion).
IP packets will have a VLAN Tag information at origin and router facing will route them according to that VLAN Tag to the correct target VLAN according to the router routing table.
Mainly used for inter-switches communication.
RNC Passport provisioning update of maxframesize if VLAN tagging used
lp/x eth/y maxframesize. Value should be 1518 if in port mode (no vlans), or should be set to 1522 if VLANs are provisioned.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.91
Public versus private IP addresses
Besides the reserved IP addresses (0.0.0.0/8 and 127.0.0.0/8) there are other
addresses not used on the public Internet. These private subnets consist of private IP
addresses and are usually behind a firewall or router that performs NAT (network
address translation). NAT is needed because private IP addresses are nonroutable on
the public Internet, so they must be translated into public IP addresses before they
touch the Internet. Private IPs are never routed because no one really owns them. And
since anyone can use them, there's no right place to point a private IP address to on
the public Internet. Private IP addresses are used in most LAN and WAN environments,
unless you're lucky enough to own a Class A or at least a Class B block of addresses, in
which case you might have enough IPs to assign internal and external IP addresses.
The following blocks of IP addresses are allocated for private networks:
10.0.0.0/8 (10.0.0.0 to 10.255.255.255)
172.16.0.0/12 (172.16.0.0 to 172.31.255.255)
192.168.0.0/16 (192.168.0.0 to 192.168.255.255)
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.92
RNC4369 7750
SGSN
6850 omniswitch
Lp/14 eth/0
Lp/15 eth/0
Port 1/1/1
Port 1/1/3
2/1/20
2/1/19
Cplane
Uplane
station_c
station_d
UIIV Ottawa RNC example – Routing protection
Stations e to j
• RNC can only perform static routing.• Engineering rules state to use PDR (protected default route).• Weighting (parameter called metric) is used to have 1 GigE port preferred over the other (per VR).• All IP traffic on that VR would go out that preferred GigE port (if it is available). So for IuPSoIP, both Cplane and uplane are over the same port.• If unavailable, traffic would go out the other GigE port.• Once preferred port (route) is available again, traffic switches back – revertive protection• 7750 must be provisioned with same route preferences
GigE
GigE
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.93
UIIV Ottawa Network – naming & IP address schemes to ALU SGSN
RNC4369 7750SGSN
6850 omniswitch
Lp/14 eth/0vlan 695
10.69.1.17
Lp/15 eth/0vlan 696
10.69.1.21
1/1/1vlan 695
10.69.1.18
1/1/3vlan 696
10.69.1.22
2/1/20
2/1/19
Cplane
Uplane
station_c
station_d
10.0.1.2
10.0.1.3
Stations e to j
Vlan id<rncid>5 IuPSoIP on card 14<rncid>6 IuPSoIP on card 15<rncid>1 hybrid Iub on card 14. <rncid>2 hybrid Iub on card 15.
IP addresses10.<rncid>.1.17 IuPSoIP on card 1410.<rncid>.1.21 IuPSoIP on card 1510.<rncid>.0.1 hybrid Iub on card 14. 10.<rncid>.0.5 hybrid Iub on card 15.
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.94
RNC4369 7750SGSN
6850 omniswitch
Lp/14 eth/0vlan 695
10.69.1.17
Lp/15 eth/0vlan 696
10.69.1.21
1/1/1vlan 695
10.69.1.18
1/1/3vlan 696
10.69.1.22
2/1/20vlan 11010.0.1.1
2/1/1910.0.2.2
Cplane
Uplane
station_c
station_d
10.0.1.2
10.0.1.3
d -p la/* to see lans provisioned and if linked to protocol portsd -p la/* vlan/* to see vlans provisioned and if linked to protocol portsd -p vr/1 pp/* ip log/* to see the IP addresses assigned to above lans or vlans
UIIV Ottawa Network – LAN / VLAN connectivity between boxes
7750 next hop IP address is RNC lan/vlan IP address + 1 (because it’s a point-to-point subnet of 2 addresses)
Stations e to j
d -p la/* to see lans provisioned and if linked to protocol portsd -p la/* vlan/* to see vlans provisioned and if linked to protocol portsd -p vr/1 pp/* ip log/* to see the IP addresses assigned to above lans or vlans
172.24.4.47172.24.4.56
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.95
RNC4369
7750
SGSN
6850 omniswitch
UIIV Ottawa Network – IuPSoIP Cplane only shown
station_c
station_d
10.0.1.2
10.0.1.310.69.1.2
10.69.1.3
SCTP endpoints
Lp/14 eth/0
Lp/15 eth/0
Vr/1
Normal working state shown• RNC and 7750 both provisioned to prefer using lp/14 eth/0• Both sctp associations take same route through our network (no other choice)• All links are GigE
SCTP endpoint address on RNC (similar to linkset link in IuPSoATM)2-8 addresses per RNC (address is defined per PSFP card)To see provisioning:d -p ss7 sctp/* to see the PSFPs usedd -p ss7 sctp/* srcep/* to see the SCTP addresses on RNC
SCTP endpoint address on SGSNd -p ss7 m3ua/1 pmp/* to see it on RNC
2/1/20vlan 11010.0.1.1
PP/ss7cplane10.69.1.14
Address is 10.<rncid>.1.14
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.96
RNC4369
7750
SGSN
6850 omniswitch
UIIV Ottawa Network – IuPSoIP Uplane only shown
Lp/14 eth/0
Lp/15 eth/0
Vr/1
Normal working state shown• RNC and 7750 both provisioned to prefer using lp/14 eth/0
On RNC for IuPSoIP, user plane is exactly the same as it is for IuPSoATM that you are used to. There is no user plane code changes nor provisioning that is different.
PP/Localmedia172.253.69.126
2/1/1910.0.2.2
Uplane Stations e to j
172.24.4.47172.24.4.56
RABs
Address is 172.253.<rncid>.126
All Rights Reserved © Alcatel-Lucent 2006, #####IPRAN TIS Skill Focus Nov 2008 / p.97
www.alcatel-lucent.comwww.alcatel-lucent.com