Iups Ip + Direct Tunnel Knowledge Sharing Session: Alan Loo / Tsd 03/06/2009

Security Level:
IuPS IP + Direct Tunnel

Knowledge Sharing Session
Alan Loo / TSD

www.huawei.com
03/06/2009
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Objectives
• Upon completion of this knowledge sharing session, you

will…
 Be familiar with IuPS IP concept

 Understanding of IuPS IP protocol stack
 Data configuration for IuPS IP
 Basic Interconnect mode for IuPS IP (to be updated)
 Understanding of Direct Tunnel feature
 Signaling Flow for IuPS + Direct Tunnel (to be included in
next knowledge sharing session)
 Basic knowledge of routing protocols – BFD, OSPF, VRRP
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Basic Concept of IuPS IP
• RNC BSC6810 supports IP-based networking on the Iu

interface.
• RNC and the SGSN/GGSN communicate based on the IP

protocol stack.
• RNC interface boards for IP based IuPS

• FG2a
• GOUa
• UOIa (IP)

Board Specifications

Basic Concept of IuPS IP
• RINT boards such as FG2a and GOUa are used commonly as

the IP interface board on RNC. We usually select GOU board
because GOU uses GE optical ports and suitable for scenario
where the RNC is located far away from the Provider Edge (PE-
router/switches).
• In rare occasion where the distance of RNC and PE is less than

100m, we can use FG2 board; this board provides FE and GE
electrical ports.
• A GOU board can support a maximum of 1800 IP paths but if

GOU is used for IuPS, only 32 IP paths can be configured for
each adjacent node eg. SGSN (only 32 IP Paths to SGSN)

Control Message Flow on Iu
interface
• Control plane message flow between RNC and SGSN

• RINT processes the control plane messages and sends
the messages to SPUa board for processing (Flow 1)

User Plane message flow on Iu
interface
• User plane message flow between RNC and SGSN/GGSN

•  Iub RINT  DPUb (DPUb processes user plane data) 
IuPS RINT  SGSN/GGSN

SIGTRAN
M3UA M2UA IUA SUA M2PA V5UA ….
SCTP
IP
• Signaling Transport (SIGTRAN) protocol stack is interworking

standards established by Internet Engineering Task Force (IETF)
for interworking between signaling system SS7 and IP.
• Support transmission of switched circuit networking signaling
messages through IP network.
• SS7 signaling message can be transmitted efficiently and
reliably on IP network through Stream Control Transmission
Protocol (SCTP)

IuPS IP Protocol Stack

Communication between RNC and
SGSN

M3UA Introduction
 M3UA is a protocol for supporting the transport of any SS7 MTP3-User signaling
(e.g., ISUP, SCCP and TUP messages) over the IP Network using the services of
the Stream control transmission protocol (SCTP)
 M3UA is used in Iu interfaces based on IP transmission.
 M3UA allows for all the functionality of MTP3 to be done over IP. Supports the
transport of MTP3-User signaling over IP.

M3UA Terminology Introduction
 Application Server (AS) - A logical entity serving a specific routing key.
 An example of an application server is a virtual switch element handling all call processing for a
unique range of PSTN trunks, identified by an SS7 SIO/DPC/OPC/CIC_range.
 Application Server Process (ASP) - A process instance of an application server.
 IP Server Process (IPSP) - A process instance of an IP-based application.
 Signaling Gateway (SG) - An SG is a signaling agent that receives/sends SCN native signaling at the
edge of the IP network.
 Signaling Gateway Process (SGP) - A process instance of a signaling gateway. It serves as an
active, backup, load-sharing or broadcast process of a signaling gateway.
 In WCDMA system, the UMG, SGSN and RNC can work as SGP. The HLR, MSC server and RNC can
work as ASP and IPSP.

M3UA protocol stack (IPSP-IPSP)
SCTP client  IPSP client  ASP

SCTP server IPSP server  SGP

M3UA protocol stack (ASP-SGP)

M3UA function
 Service provided by M3UA
 Support MTP3 user message transfer.
 Providing inter-connection to MTP3 network and network management
 Manage the SCTP association between SG and ASP or IPSP and IPSP.
 Support network routing function, such as among multiple ASP and SGP
connections
 Benefits of M3UA:
 Replace physical SS7 links with virtual IP associations
 Maintain deterministic qualities demanded in signaling.
 Eliminate SS7 bandwidth restrictions

Relevant Concept of M3UA configuration
Case 1 Case 2
M3LKS
M3LKS
M3LNK1 CN M3LNK1 CN
RNC RNC
M3LNK2 M3LNK2 STP
M3LE M3LNK3 M3DE M3LE M3LNK3 M3DE
IPSP IPSP ASP SGP SP
 AS: Application Server

 ASP: Application Server Process
 SP: Signaling Point
 IPSP: IP Server Process
 SGP: Signaling Gateway
 SS7: Signaling 7 Signaling Point

IuPS IP Data Configuration
• For IUPS-IP data configuration, we perform data configuration

according to the protocol stack from bottom to top. The IUPS
data consists of
• - Physical layer
• - TRM mapping
• - Factor table
• - Control plane data
• - User plane data.

• Configuring Physical Layer Data
• SET ETHPORT
(set attributes of GOU board, auto negotiation, flow control etc)

• ADD ETHIP
(add IP address of GE port on GOU that will be used to
connect to PE)

• ADD DEVIP
(add device IP address when using layer 3 networking)

• Configuring Transport Resource Mapping
• ADD TRMMAP
(add transport resource mapping, dscp values etc)

• Configuring Factor Table
• - ADD FACTORTABLE
(add factor table – use default values unless you know what
you are doing)

• Configuring IuPS Control Plane
• - ADD SCTPLNK (similar to SAALLNK for ATM. Set signaling link

mode to client for Iu-PS because RNC is client and SGSN is Server)
• - ADD N7DPC (add destination signaling point, beartype must be

M3UA)
• - ADD CNDOMAIN (add PS domain)
• - ADD CNNODE (add CN node, bearer type = IP)
• - ADD ADJNODE (add adjacent node)
• - ADD ADJMAP (set mapping between adjacent node and

transmission resource map)

• Configuring IuPS Control Plane
• //M3UA Similar to MTP3 links.

• - ADD M3LE (RNC as local entity, M3UA_IPSP is used)
• - ADD M3DE (SGSN as destination M3UA entity)
• - ADD M3LKS (add M3UA signaling linkset, same like ATM MTP3B linkset)
• - ADD M3LNK (add M3UA signaling link, same like MTP3B link for ATM)
• - ADD M3RT (add M3UA route)

• Configuring IuPS User Plane

• ADD PORTCTRLER
• ADD IPPATH (Path type for Iu-PS is usually RT and NRT)
• ADD IPRT (when using L3 networking)

IuPS IP Configuration Summary
 Physical Layer
 FG2a or GOUa board is recommended for Iu interfaces.
 Each FE/GE port can be assigned only one IP address.(one master IP

address and up to 5 secondary IP addresses)
 The IP addresses must be unique.
 If active/standby GOU/FG2a is used, only need to add DEVIP on active

board (Even Slot ..14….16…..18…)
 Each interface board can be configured with a maximum of five device IP

addresses, which cannot be on the same network segment.

Iu IP Configuration Specification
 Signaling Plane
 One SPUa subsystem controls a maximum of 150 SCTP links.
 The RNC can correspond to a maximum of 119 DSPs.
 Each M3UA signaling link set has a maximum of 16 M3UA

signaling links. Each SPUa subsystem can control a maximum of
64 M3UA signaling links.
 The RNC supports a maximum of 238 M3UA routes.

Iu IP Configuration Specification
 User Plane
 One RNC can configure maximum 2,000 adjacent nodes
 One SPUa subsystem controls a maximum of 1,200 AAL2 paths and IP paths
totally. One RNC supports a maximum of 12,000 AAL2 paths and IP paths totally.
 One adjacent node of IUPS type supports a maximum of 32 IP paths.
 If an adjacent node is of IUPS type, it can be configured with only the RT, NRT, or
QOSPATH type of IP paths.
 For the Iu-PS interface, the PATHCHK parameter of an IP path must be set to
ENABLED. For any other interface, the PATHCHK parameter of an IP path is set
to DISABLED by default, which can be changed according to actual requirements.

IuPS IP Interconnect Mode
• RNC Board Redundancy - GOU
• GOUa boards can be configured in active/standby slots in

RNC.
• 2 backup modes:
• Board backup with no port backup
• Board backup with port backup.

• 2 GOU boards are configured as active/standby relationship,
one GOU is active and the other is standby. The standby
board synchronise its data with the active board in real time.
This backup mode can be turned on when adding board
through ADD BRD command as shown below.

• The switchover between boards kicks in when the active
GOU is reset or faulty, while standby GOU is working
properly. When the GOUs board are switched over, the
initially active GOU becomes standby, and the standby
GOU becomes active. The switchover between active and
standby GOU does not affect ongoing services. Manual
board switchover can be done by using MML SWP BRD.

• Board backup with port backup
• When the GOU boards work in backup mode (active/standby),
the GE ports on active/standby boards can also be configured
for backup.
• This port backup method can be turned on using MML

command ADD ETHREDPORT. Example below shows the
configuration of GE port 0 on slot 16 as backup.

• When GE ports work in backup mode, one port is active
and the other is standby (as shown below). The active
port is responsible for transceiving data.

• The switchover between active and standby ports on GOU
happens when the conditions below are fulfilled or manually
switchover using MML SWP ETHPORT.
• Active port is faulty but standby port works properly.
• Active GOU is faulty but standby GOU works properly.
• Board where the active port is located is reset.
• The switchover between the active and standby ports slightly

affects the data transmission (when the traffic carried on the
port is high) but does not interrupt ongoing services.

• Load Sharing on GOU GE ports
• Load sharing feature is applicable on GE ports that are located
either on the same board (i) or on active/standby boards (ii)
• (i) (ii)

• Load Sharing on GOU GE ports
• However, the RNC does not support load sharing between GE
ports that are located on different boards where there are no
active/standby relationship (a), and between active and standby
ports (b)
• (a) (b)

• Concept of GE ports Load Sharing
• The data of one user is transmitted through one GE port,

instead of being shared by ports.
• Load sharing between GE ports of RNC is applicable

when using layer 3 networking between RNC and other
NEs (PE-router/switches).

• The concept of load sharing is RNC will distribute the data
streams that have the same destination IP/address to different
physical ports, so the ports can share the load. This requires
different IP routes. Load sharing between 2 GE ports requires 2
IPRT that have the same destination IP, address mask and
priority, but different next hops. An example is shown below.

IuPS Interconnect Mode
• Benefits of GE ports load sharing
• The data traffic is shared by the ports to avoid occurrence

where some ports are busy while others are idle.
• Load sharing enhances reliability of data transmission.
• * GE ports load sharing do not double the capacity of GOU

• Networking mode for IuPS using GOU

• (extracted from Huawei RNC Documentation)
• Single-Homing Layer 3 Networking
• Dual-Homing Layer 3 Networking
• Direct Connection with Load Sharing

• Single-Homing Layer 3 Networking
• Active/Standby GOU with Port Backup
• The active and standby FE/GE ports of the RNC connect to the
Provider Edge (PE), which further connects to the data network. The
active and standby FE/GE ports of the RNC share one IP address, that
is, IP1-1. The PE configures the active and standby ports of the RNC in
one VLAN and uses one interface IP address of the VLAN, that is, IP1-0.

• Dual-Homing Layer 3 Networking
• Active/Standby GOU with Port Backup
• The active and standby FE/GE ports of the RNC connect to two
PEs. Link Aggregation (LAG) is applied to the interconnection
links between the PEs to increase the bandwidth and reliability
of the links. The active and standby FE/GE ports of the RNC
share one IP address, that is, IP1-1. The PEs configures the
active and standby ports of the RNC in one VLAN and uses one
virtual VRRP IP address – IP1-0

• Direct Connection with Load Sharing

• Active/Standby GOU with NO port back
• Direct connection with load sharing from RNC to
SGSN/GGSN
• This mode is applicable when the RNC and SGSN is
located in the same equipment room. In this networking
mode, the GOU board can work in board backup mode
and the GE ports work in load sharing mode to carry
services

• Active/Standby GOU with GE Port 0 Backup

• VRRP – Master/Backup PE
• Link Aggregation between PEs.

• 2 Active GOUs.
• Load Sharing on GE ports of each GOU
• When board faulty, services will be impacted.
• When port faulty, services will not be impacted because
data will be routed to another port for transceiving.
• 2 IPRT on each GOU.

IuPS Direct Tunnel
• Only one GTP-U tunnel is setup between RNC and GGSN,

bypassing SGSN compared to the conventional two
tunnel solution, thus reducing the delay in processing
user plane data.
• One tunnel solution reduces SGSN processing loads on

handling user plane data.
• The conventional two tunnel method has another GTP-U

tunnel setup between SGSN and GGSN, and SGSN will
need to perform user data processing.

IuPS Direct Tunnel
• Protocol stack structure of the user plane that adopts two

tunnels

IuPS Direct Tunnel
• Protocol stack structure of user plane that uses One

Tunnel

IuPS Direct Tunnel
• One tunnel is transparent to RNC. The only changes that
need to be made on RNC are to:
• Check One Tunnel license and IU over IP on RNC
• Add IPPATH directly pointing to GGSN User Plane IP
Address
• Add IPRT to GGSN User Plane (next hop is depending on
the actual network design)

IuPS Direct Tunnel
• If one tunnel feature is used, SGSN will not be able to perform any User trace
because SGSN no longer process user plane data. The user plane data is
processed by GGSN directly. However, when the network design is as below (A
direct connection), SGSN should have the feature of forwarding the User Plane
data to GGSN, but SGSN will not process the data. It is just a forwarding
method. The IPRT next hop address is SGSN Data Forwarding Board IP. The
same IPRT has to be added on GGSN, destination IP as RNC GOU DEVIP, and
next hop is SGSN Data Forwarding Board IP.

IuPS Direct Tunnel
• When Layer 3 networking is used- RNC GOU connects to Router,
L3 switches; the User Plane data is directly passing from RNC
to GGSN through the PE devices, without any handling or
processing by SGSN. The IPRT next hop is PE Devices’ IP. The
same IPRT has to be added on GGSN with destination address
as RNC GOU DEVIP and next hop is PE IP. Please note that
SGSN signaling IPRT has to be added on RNC as well due to the
L3 networking, and vice versa. Tracing can be done on GGSN
Create GTP-U message and check DTI value if Direct Tunnel is
in used.

OSPF
• Open Shortest Path First

• Dynamic routing protocol for use in IP networks.
• OSPF detects changes in the topology, such as link
failures, very quickly and converges on a new loop-free
routing structure within seconds.
• It computes the shortest path tree for each route using a
method based on Dijkstra's algorithm, a shortest path
first algorithm.
• OSPF is an interior gateway protocol that routes Internet
Protocol (IP) packets solely within a single routing
domain (autonomous system). It gathers link state
information from available routers and constructs a
topology map of the network

BFD
• Bidirectional Forwarding Detection

• A network protocol used to detect faults between two
forwarding engines.
• BFD establishes a session between two endpoints over a
particular link.
• If more than one link exists between two systems,
multiple BFD sessions may be established to monitor
each one of them.
• SET BFDPROTOSW: SRN=0, SN=16; SWITCH=BFD_ON;
• This command is used to open the BFD Protocol switch if
you want to connect with older version VRP using Muti-
BFD detect.

VRRP
• Redundancy protocol designed to increase the availability of the default

gateway servicing hosts on the same subnet.
• Advertising a "virtual router" (representation of master and backup routers
acting as a group) as a default gateway to the host instead of one physical
router.
• VRRP can select a new router to take over the transmission when the physical
router fails.
• Hosts set the IP address of the virtual router as the next-hop address of their
own default routes

Thank You.
www.huawei.com

Гораздо больше, чем просто документы.

Iups Ip + Direct Tunnel Knowledge Sharing Session: Alan Loo / Tsd 03/06/2009

Загружено:

Сведения о документе

Дата загрузки

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Описание:

Авторское право:

Доступные форматы

Iups Ip + Direct Tunnel Knowledge Sharing Session: Alan Loo / Tsd 03/06/2009

Оригинальное название:

Загружено:

Описание:

Авторское право:

Доступные форматы

Похожие издания

Security Level:

IuPS IP + Direct Tunnel

Alan Loo / TSD

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

• Upon completion of this knowledge sharing session, you

 Be familiar with IuPS IP concept

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

• RNC BSC6810 supports IP-based networking on the Iu

• RNC and the SGSN/GGSN communicate based on the IP

• RNC interface boards for IP based IuPS

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

• RINT boards such as FG2a and GOUa are used commonly as

• In rare occasion where the distance of RNC and PE is less than

• A GOU board can support a maximum of 1800 IP paths but if

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

• Control plane message flow between RNC and SGSN

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

• User plane message flow between RNC and SGSN/GGSN

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

• Signaling Transport (SIGTRAN) protocol stack is interworking

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

 M3UA is used in Iu interfaces based on IP transmission.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

unique range of PSTN trunks, identified by an SS7 SIO/DPC/OPC/CIC_range.

 Application Server Process (ASP) - A process instance of an application server.

 IP Server Process (IPSP) - A process instance of an IP-based application.

edge of the IP network.

 Signaling Gateway Process (SGP) - A process instance of a signaling gateway. It serves as an

active, backup, load-sharing or broadcast process of a signaling gateway.

work as ASP and IPSP.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

SCTP client  IPSP client  ASP

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

 Providing inter-connection to MTP3 network and network management

 Maintain deterministic qualities demanded in signaling.

 Eliminate SS7 bandwidth restrictions

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

IPSP IPSP ASP SGP SP

 AS: Application Server

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

• For IUPS-IP data configuration, we perform data configuration

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

• Configuring Physical Layer Data

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

• Configuring Physical Layer Data

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

• Configuring Factor Table

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

• - ADD SCTPLNK (similar to SAALLNK for ATM. Set signaling link

• - ADD N7DPC (add destination signaling point, beartype must be

• - ADD CNDOMAIN (add PS domain)