You are on page 1of 11

Iu-PS over IP Architecture

RAN Gateway Protocol Interaction

NTP Server DNS Server

RAN Gateway

AAA
Wm RADIUS Uu

HLR

Up IPsec

Security Gateway

Up H.248 GTP-U

IP Network Controller
SIGTRAN

RANAP SIGTRAN / IP SGSN

Iu-ps Sig GW MGW


RANAP ALCAP / ATM MSC

CS & PS Bearers Up Session Protocol Authentication/Authorization Signaling Management Other


TR-069 AP Management

RTP SNMP NMS

Iu-cs

OA&M Network

mobile core network

Physical Realization

RAN Gateway
SPC = INC
RANAP SPC = SigGW
SIGTRAN

ALCAP SPC = CS-MGW1

INC
SIGTRAN H.248

SigGW
ALCAP SPC = MGW
RTP H.248

CS-MGW1
RANAP SPC = MSS

LBR A

MGW
ALCAP SPC = CS-MGW2

MSS

RTP GTP-U

LBR B

ATM

CS-MGW2
CS Domain

SeGW
IP
Iu-PS CP (RANAP) & UP (GTP-U)
RANAP SPC = SGSN

PS Domain

SGSN
Iu-PS CP (RANAP) & UP (GTP-U)

Description of Iu-PS over IP Solution

RANAP Signaling Path


The RANAP control path is between the INC and the SGSN over a SIGTRAN bearer
IP layer and SCTP/M3UA layer protection is provided The INC relays bearer setup information (e.g. IP address and Tunnel Endpoint ID) to the femtocell to setup the GTP-U path

Iu-PS Control Plane Redundant Operation

Redundancy Options for Iu-PS Physical Layer Path Protection


There are two active, independent IP paths through the RAN Gateway to two destination IP ports at the SGSN These paths support both control and user plane traffic GTP-U traffic is routed as normal IP traffic through the RAN GW to the SGSN

INC SCTP End-Point IP Address


Each INC CN blade SCTP interface appears to the Core Network as a single Virtual IP address, reachable from the SGSN through either Cisco router

The RAN GW HA design ensures that any single failure of an INC Ethernet interface, switch blade, Cisco router or intervening physical link will not affect reachability of that IP address from the SGSN

Redundancy Options for Iu-PS

M3UA Transport Redundancy


CN services are supported on an active/standby blade pair in the INC There are two SCTP associations between each blade and the SGSN for a total of four SCTP associations between each INC and SGSN The active INC CN blade supports two SCTP associations in load shared mode The standby INC CN blade supports two SCTP associations in loadshared mode that only become active after a failover event

SCTP Multi-homing and Link Redundancy


The INC does not support SCTP destination multi-homing and therefore each SCTP association supports a single destination IP address only A failure in the IP path between the INC and the destination IP address of the SGSN will result in loss of the SCTP association, triggering a failover to the remaining SCTP association

Control Plane Resilience over IP

INC
SCTP-11
IP-11 IP-12

SGSN
VIP-1

VIP: Virtual IP Address


Placement in diagram indicates location and reachability from the SGSN
SCTP-11: VIP-1 to IP-11 SCTP-12: VIP-1 to IP-21
SCTP-21: VIP-2 to IP-12 SCTP-22: VIP-2 to IP-22

IuIS-1
(I-IPSP-1)

SGSN-1
(S-IPSP-1)

IP-21 IP-22

IuIS-2
(I-IPSP-2)

VIP-2

SGSN-2
(S-IPSP-2)

SCTP-22

a) Logical Path

INC INC IuIS-1


(I-IPSP-1)
VIP-1 VIP-2

SGSN SigGW SGSN-1


(S-IPSP-1)
IP-11 IP-12

SW-1

LBR A

SW-1

IP-21 IP-22

IuIS-2
(I-IPSP-2)

SW-2

VIP-1 VIP-2 LBR B

SW-2

SGSN-2
(S-IPSP-2)

b) Physical Path

Failover Scenarios (1)


Process Failure Modes (assumes IuIS-1 is active)
If SGSN-1 fails, IuIS-1 will detect the failure of SCTP-11, stop using SGSN-1 & continue to use SGSN-2 (SCTP-12) for all traffic If SGSN-2 fails, IuIS-1 will detect the failure of SCTP-12, stop using SGSN-2 & continue to use SGSN-1 (SCTP-11) for all traffic If IuIS-1 fails, IuIS-2 becomes active and starts using both SGSN-1 and SGSN-2 (SCTP-21 & SCTP-22) in load-sharing mode

If IuIS-2 fails, no failover is triggered, and IuIS-1 continues to use both SGSN-1 and SGSN-2 (SCTP-11 & SCTP-12) in load-sharing mode

Failover Scenarios (2)


Interface Failure Modes (assumes IuIS-1 is active)
If the local INC Ethernet interface, switch or LBR fails, the IuIS Virtual IP address remains in service over the remaining available IP path. No external failure is visible and no external failover event is triggered If SGSN-1 IP-11 fails, IuIS-1 will detect the failure of SCTP-11, stop using SGSN-1 and continue to use SGSN-2 (SCTP-12) for all traffic.
If SGSN-1 IP-12 fails, it does not impact any ongoing traffic with IuIS-1

If SGSN-2 IP-21 fails, IuIS-1 will detect the failure of SCTP-12, stop using SGSN-2 and continue to use SGSN-1 (SCTP-11) for all traffic
If SGSN-2 IP-22 fails, it does not impact any ongoing traffic with IuIS-1

If IuIS-1 VIP-1 fails (due to failure of IuIS-1 module), IuIS-2 becomes active and starts using both SGSN-1 and SGSN-2 (SCTP-21 & SCTP-22) in load-sharing mode If IuIS-2 VIP-2 fails (due to failure of IuIS-2 module), no failover is triggered, and IuIS-1 continues to use both SGSN-1 and SGSN-2 (SCTP-11 & SCTP-12) in loadsharing mode

Additional Iu-PS over IP Feature Information

SCTP
The INC supports client mode only, where the INC initiates association. Therefore, the SGSN must support server mode or combined client/server mode. The INC does not support SCTP multi-homing. It can interoperate with a multi-homed peer using only one of the available remote IP addresses.

M3UA
The INC supports the Single Exchange Initiator model for IPSP operations i.e. INC always initiates ASP-UP or ASP-ACTIVE messages and ignores those messages if received from the peer IPSP The INC expects the IPSP peer (SGSN) to operate in load shared mode (active-active) The INC itself operates in override mode (active-standby)