SE2900 Product: Foreword

SE2900 Product
Introduction
www.huawei.com
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved.
Foreword
What are the technical problems in the application on the IP

network of the pre-NGN/IMS/CS? What role does the
SE2900 play on the core network?
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved. Page1
1
References
SE2900 Product Documentation
Objectives
Upon completion of this course, you will be able to:

Know main functions and application scenarios on the core
network.
Understand the SE2900's main features.
Describe the SE2900's architecture.
2
Contents
1. SBC Introduction
2. SE2900 Application and Features
3. SE2900 Hardware and Software
4. SE2900 Workflow
Contents
1. SBC Introduction
1.1 What Is the SBC?

1.2 Why Is the SBC Required?
3
What Is the SBC?
SBC -- Session Border Controller
Gradually become a standard product form on the NGN and IMS
network (like switch/router)
Also named border access controller (BAC)
Act as the access border gateway (ABG) on the IMS network
Solves such problems as NAT/firewall traversal, security, interworking
and QoS.
Huawei SBC: SE2300/SE2600/SE2900
Former name: SAN/EuMedia/Eudemon 2X00
SE2600, and SE2900 are used for access and interworking between
core network.
Contents
1. SBC Introduction
1.1 What Is the SBC?
1.2 Why Is the SBC Required?
4
Situations In Current IP Network
Deployment
The appearance of NAT device.
Private IP address are used for IP
Public Network
shortage in private networks.
Restrictions in their communication

NAT
Private IP segments overlap. Hospital
192.168.*.* NAT
Private IPs are not allow to transport in Location
public. 10.77.*.*
NAT
Campus
NAT is Designed for the 192.168.*.*
NAT
Enterprise
communication between public and 10.77.*.*
private network .
Basic Concept Of NAT
NAT (Network Address Translator)

NAT: <private IP address + port> <public IP address + port>
Can reduce the depletion speed of IP address space.
The IP addresses of the private LAN are hidden and protected

effectively.
TCP/UDP TCP/UDP
IP Header TCP/UDP Payload
Header
NAT
IP
The ordinary NAT equipment can
translate IP and TCP/UDP
header Link Layer
5
Basic Concept Of NAT (Cont
Cont.)
(Cont.)
Src Addr Dest Addr Src Addr Dest Addr

10.6.10.1 Internet Host 211.168.2.1 Internet Host
My
network Before NAT After NAT Internet
OutBound Packet NAT OutBound Packet
10.6.10.1 Internet
Dest Addr Src Addr Dest Addr Src Addr
10.6.10.1 Internet Host 211.168.2.1 Internet Host host
After NAT Before NAT

Return Packet Return Packet
NAT Traversal Problem in IMS/NGN

Network
NAT traversal problem in IMS/Pre-NGN network
IP Header UDP/TCP
Src Dst Header
Payload (SIP/SDP)
NAT can only translate Protocols adopted in PreNGN/ IMS,

the IP address and port such as H248/SIP, IP addresses for
number for signaling in IP signaling and media are exchanged in
packet header the payload (Such as Contact header
and SDP)
Service of IMS/PreNGN cant be

implemented, for the private IP in the
payload cant be translated
6
Network
SIP and SDP
IP in the IP header: for signaling
IP in SDP: for the media transmission

Network
IP address in SIP header
IP in the IP header: for signaling
IP in the SIP header: for subsequent

signaling routing
7
NAT Traversal Problem in IMS/NGN Network
Private network
UE1 NAT Public Router SIP server
Src IP: IP1 (private) REGISTER
Dst IP:SIP server

Src:IP1
NAT IP2
IP1
Via
Dst: SIP server
IP1
Via REGISTER
SIP server get the IP in

Via header for response
Dst: IP1(private)
No routing table to
Private network
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved.
Solution to the NAT Traversal Problem
Two common solutions:

ALG
All NAT devices must be upgraded to support ALG.
The IP addresses in both the IP header and payload must be
translated to implement enhanced NAT.
Proxy
A proxy device must be deployed to transmit signaling and media
streams.
The SBC operates in proxy mode.
8
Solution to the NAT Traversal Problem
Comparison between ALG and proxy
ALG Proxy
All NAT devices must be Only one

upgraded. proxy needs to
Problems be configured
Proxy
Investment: Who pays for the on the network.
upgrade? NAT devices
Complexity: How many NAT do not need to
devices must be upgraded? be upgraded.
Feasibility: Do all NAT devices
support upgrade?
Full Proxy
The SBC acts as a proxy for signaling and media streams.
IMS
Signaling Signaling
WAN Media
SBC SBC
Firewall/NAT Firewall/NAT
Enterprise Enterprise
SIP UE PC SIP UE
9
Reason of Adopting SBC in IMS
To save IPv4
SBC is
resource
Designed
And enhance
security
Private IP Intranets NAT is Protocols

are used in cant invented to adopted in IMS
private communicate translate the network ask for
Network for the private IP to the ability to
restriction public IP in translate the IP
(IP overlap...) the IP header in the payload
Contents
1. SBC Introduction
4. SE2900 Workflow
10
Contents

2.1 Application
2.2 Features
SE2900 on the IMS/NGN/CS Network
The SE2900 can act as the A-SBC (deployed between the

access network and the core network) and I-SBC
(deployed between two core networks).
Functions in the A-SBC scenario:
NAT traversal, QoS, PBX access, access security, media firewall,
media proxy, transcoding, and media access control
Functions in the I-SBC scenario:
Interworking, inter-network security, QoS, routing, PBX access,
transcoding, and call access control
11
A-SBC
The SE2900 supports proxy for signaling and media streams. To a UE, the
SE2900 is the core network; to the core network, the SE2900 is just a UE.
By processing signaling and media streams, the SE2600 implements
functions, such as CAC, NAT traversal, QoS, access security, and topology
hiding.
I-SBC
The SE2900 is a transfer point for signaling protocols. All signaling packets
between the two core networks pass through the SE2900 so that it can
implement functions, such as CAC.
In the I-SBC scenario, the SE2900 supports the following functions:
Conversion between SIP over SCTP and SIP over UDP
Forwarding of signaling and media streams between different networks
Embedded common audio transcoding
12
Virtual SBC
One SE2900 can be divided into several virtual A/I-SBCs to serve
different access networks. Each virtual A-SBC separately processes
signaling, media, and routing information for UEs on each access
network. In addition, a virtual SBC can serve as an A-SBC or/and I-
SBC or access the NGN/IMS/CS network.
The virtual SBC is used when multiple access networks connect to
one or more core networks. This feature has the following advantages:
Saves CAPEX and OPEX for carriers.
Simplifies network architecture.
Facilitates the delivery of universal services.
Enables fast deployment of new services.
Virtual A-SBC
13
A-SBC and I-SBC Coexistence
Contents

2.1 Application
2.2 Features
14
Signaling and Media ControlFull Proxy
The SE2900 supports SIP signaling proxy and media proxy.
For A-SBC, the UE considers the IP address of the P-CSCF as the
access-side address.
For I-SBC, the core network NE in each side consider the SBC as the
other side destination.
Path of a message from the SBC to the P-

CSCF:
IP1->IP2->P-CSCF IP
UE1
IP bearer network
UE2
Destination IP address in the REGISTER

message: access-core address of the SBC
IP1- access-side IP2- core-side

address address
DNS (1)
The domain name system (DNS) is used to route signaling messages

by translating between domain names and IP addresses.
In the A-SBC scenario, DNS query supports the disaster tolerance
deployment of P-CSCFs.
The SE2900 supports embedded DNS and external DNS.
Embedded DNS: The SE2900 supports DNS-query-based routing
based on the DNS data configuration in the local.
External DNS: The SE2900 supports DNS-query-based routing for
SIP registration or calls based on the configuration of the connection
between the SE2900 and DNS servers.
15
DNS (2)
Embedded DNS and external DNS can be configured separately or
simultaneously. If external DNS and embedded DNS are both configured,
the SE2900 performs embedded DNS query first. If the embedded DNS
query fails, the SE2900 performs external DNS query.
Media Bypass
If the SE2900 serves as a proxy for all media streams, media streams
consume a lot of network bandwidth, especially in video applications.
Therefore, media bypass is required in some scenarios to reduce the
bandwidth consumption by media streams. Media bypass enables
media streams to be transmitted between UEs without passing through
the SE2900.
Media Signaling
packets are SBC
must pass
exchanged through the
directly. SE2900.
Enterprise network Local network
Page31
16
Contents
1. SBC Introduction
4. SE2900 Workflow
Contents

3.1 SE2900 Hardware
3.2 SE2900 Software
17
SE2900 Hardware Cabinet &Subrack
1. PDB
2. Filler panel
3. SE2900 subrack
4. Air frame
5. Air deflector
Front view
Rear view
SE2900 Single Subrack and Boards
3 SPU SPU 6
3U 2 MXU MXU 5
1 VPU VPU 4
Board Name Full Name Quantity

MXUA0 Multi-Function and Switch Unit A0 2
SPUA0/SPUA1 Service Processing Unit A0/A1 2-4
VPUA0/VPUA1 Voice and Video Process Unit A0/A1 2-4
18
Self-Cascading
The SE2900 supports allows a maximum of three subracks to be cascaded to

support a maximum of 4,000,000 registered users.
MXU
MXU is the core board for system
management and service switching/data
exchanges and must be inserted in slots 2
and 5.
MXU implements power supply control,
fan management, and power distribution
management. MXUA0 manages the SPU
by communicating with BMC modules on
the SPU.
Each master subrack can be used in
conjunction with two backup subracks 1 LAN0 2 LAN1 3 RS232 4 RS485
through cascading interfaces on MXU to 5 Fabric LAN0 6 Fabric 7 Subrack ID 8 Base LAN0
LAN1 indicator H-L
implement three-subrack cascading. 9 Base LAN1 10 HLY 11 ACT 12 Wrench
In each subrack, the cascading bandwidth indicator indicator
13 OFL 14 DIP 15 Fabric 16 HD-ALM
of the Base plane is 1 Gbit/s, and the indicator/button button LAN0/LAN1 indicator
cascading bandwidth of the Fabric plane indicator
17 LAN1 LINK 18 LAN1 ACT 19 LAN0 LINK 20 LAN0 ACT
is 40 Gbit/s.
indicator indicator indicator indicator
The MXU has a 300 G hard disk.
19
SPU
SPUs are service forwarding and processing
boards and must be installed in slots 1, 3, 4,
and 6.
SPUs support service processing, interface,
and board management functions. SPUs can
be classified into two types: SPUA0 and
SPUA1. SPUA0 and SPUA1 are similar in
functions, appearances, interfaces, indicators,
and technical specifications. The differences
between SPUA0 and SPUA1 are as follows:
1 SFP 2 Optical 3 SFP 4 UID
optical interface optical locating
SPUA0: one CPU interface indicator interface indicator
SPUA1: two CPUs 7 OFL
5 HLY 6 indicator/ -
indicator Wrench button
The service processing capability of
SPUA1 is twice that of SPUA0.
VPU
VPU(Voice and Video Process Unit),
with the Digital signal processing
(DSP) daughter board, processes
media data, such as voice and
video data.
VPUA0 can support 7.5 K

media transcoding
sessions(G.711 to G.729 for
instance)
The service processing

capability of VPUA1 is twice
that of VPUA0.
20
SE2900 System logical architecture
Page40
SE2900 Subrack Board Configuration

The SE2900 has three types of configuration modes:
Minimum configuration: 2 SPUs + 2 MXUs
250,000 or 500,000 registered users
Full configuration in one subrack: 4 SPUs +2 MXUs
600,000 or 1,200,000 registered users
Full configuration in three self-cascaded subracks: 12 SPUs + 6 MXUs
2,000,000 or 4,000,000 registered users
Note:
1.Each SE2900 must use the same type of SPUs. In other words, either SPUA0 or SPUA1
can be used.
2.The numbers ahead of the number of registered users refer to SPUUA0 specifications; the
numbers following the number of registered users are SPUA1 specifications.
21
SE2900 Network Interface Configuration
MCCA 2
SPU SPU
MXU MXU
SPU SPU
MCCA 1
SPU SPU
MXU MXU
SPU SPU
MCCA subrack0 Access-side signaling

VPU VPU Core-side signaling
MXU MXU Access-side media
SPU SPU
Core-side media
All signaling interfaces are connected to the first pair of SPUs (base SPUs) in subrack 0.
Generally, access-side signaling and media packets are transmitted over the same
physical interface.
All SPUs must provide connections to media interfaces.
Contents

3.1 SE2900 Hardware
3.2 SE2900 Software
22
Software Architecture
SBC software consists of platform software (including OMU application software and
LMT application software) and SE2900 application software.
OMU application software: runs on the MXU, functions as the communication and
database server, and is the core of OAM software. The OMU application software
forwards O&M commands delivered by the LMT/WebUI client to the host and directs the
responses or operation results returned by the host to the LMT/WebUI client.
LMT application software: runs on the Windows OS of the PC hardware platform,
functions as the client connecting to the OMU server, and provides MML-based
graphical terminal.
WebUI: runs on browsers in the Windows OS, and enables users to use performance
management functions and upgrade tools, operate the KVM over IP, and download OMU
clients.
SE2900 application software: consists of processes operating on boards.
23
The SE2900
software consists of
HRU, BSU, VPU,
CMU, SCU, CDB,
SEM,HMU and
PCU.
The processes work
together to process
the SE2900's all
services.
Service Processes
Process Name Function Description Operating Mode
Central Database (CDB) Serves as the subscriber data Only a pair of active and
management module of the SCU standby CDBs can be configured
and manages subscriber distribution for each ME.
data.
Security Management Performs system security defense, Only a pair of active and
(SEM) delivers security policies to standby SEMs can be configured
processes, collects security reports for each ME.
reported by the processes, and
intercepts untrusted messages.
Connection Processes the services related to CMUs work in active/standby
Maintenance Unit calls and managing call connections mode.
(CMU) for other modules.
Highspeed Routing Unit Forwards signaling messages (for Only one HRU can be
(HRU) example, SIP messages) and configured on each SPU. The
processes media messages (for HRUs on active/standby SPUs
example, SRTP, RTP, and MSRP work in active/standby mode.
messages) under the control of
CMU.
Packet Control Unit Manages IP forwarding and control. PCUs work in active/standby
(PCU) mode.
24
Service Processes (2)
Process Name Function Description Operating Mode
Broadband Functions as the fixed link (DNS) protocol BSUs work in load-balancing
Signaling Unit (BSU) processing and forwarding module, and mode.
processes IP-layer, TCP, and SCTP
messages.
Highspeed-Routing Manages hardware (for example, FPGA Only one HMU can be configured
Management Unit and ports) dedicated for media on each SPU. The HMUs on active
(HMU) forwarding. and standby SPUs work in load-
balancing mode.
Only one HMU can be configured
on each VPU. The HMUs on all
VPUs work in load-balancing
mode.
Session Control Unit Processes services on the A-BCF and BGF. SCUs work in active/standby
(SCU) Functions as the dynamic link (SIP over mode.
TCP and SIP over TLS) protocol processing
and forwarding module, and processes IP-
layer, TCP, and SCTP messages.
Voice and Video Processes media data, including audio and VPUs work in load-balancing
Process Unit (VPU) video data. mode.
Board Type
Hardware Type Application Type Service Process Description
Configuration
SPUA0 SEISU 1BSU+4SCU+1CDB+ An SE2900 has only
1PCU+1HMU+1CM one pair of ISUs.
U+1SEM+1HRU Generally, the first
pair of SPUs in
SPUA1 SEISU 2BSU+8SCU+1CDB+ subrack 0 are used
1PCU+1HMU+2CM as ISUs.
U+1SEM+1HRU
SPUA0 SEESU 6SCU+1CMU+1BSU An SE2900 can have
+1PCU+1HMU+1HR multiple ESUs.
U
SPUA1 SEESU 11SCU+2CMU+2BS
U+1PCU+1HMU+1H
RU
VPUA0 SEVPU 1HMU+1VPU -
VPUA1
25
Relationship between board hardware types,
board application types, and service processes
Relationship between board hardware types,

board application types, and service processes
Configure SEISUs or SEESUs in slots 1 and 4 or slots 3 and 6 according

to the following rules:
When only base subracks are configured, at least a pair of SEISUs must be
configured in slots 1 and 4 or slots 3 and 6 in the base subracks.
When both a base subrack and an expansion subrack are configured, a

pair of SEESUs can be configured in slots 1 and 4 or slots 3 and 6 in the
expansion subrack, or two pairs of SEESUs can be configured in slots 1
and 4 and slots 3 and 6 in the expansion subrack.
VPU configure as SEVPU
26
Signaling Processing Procedure
Page52
Message Exchange Between Service Processes

(SIP over UDP as example)
SIP signaling messages over UDP
The HRU receives a SIP message from the access side. If this SIP message
is transmitted over UDP, the HRU forwards the message to the SCU.
The SCU processes the received SIP message. During message processing,
the SCU queries the CDB for user dispatching data.
After processing the SIP message, the SCU forwards the message to the
HRU.
The HRU forwards the message to the external network through a

physical interface.
27
Performance Specifications
Specifications (Three Self-
Item Specifications (One Subrack)
Cascaded Subracks)
Maximum number
700,000 4,000,000
of registered users
Maximum number
60,000 340,000
of concurrent calls
Maximum number of 7,500 15,000
media transcoding
sessions using G.711
Maximum number
16 x 10GE + 16 x GE 48 x 10GE + 48 x GE
of IP interfaces
MXU/SPU boards in 1+1 backup

System Power supply modules in 1+1 backup
Fan modules in 1+1 backup
Contents
1. SBC Introduction
4. SE2900 Workflow
28
Contents
4. SE2900 Workflow
4.1 A-SBC Workflow
4.2 I-SBC Workflow
A-SBC Application in IMS Network
IP: SC1 S-CSCF
NE IP Address
IP: PC1 IP: IC1 UE UE1,UE2

P-CSCF I-CSCF SBC SC (Signaling Client)
IP: MS
IP: SS SS(Signaling server)
SBC IP Bearer MS (Media server)

for media
IP: SC
MC (Media client)
IP: MC
P-CSCF PC1
IP : UE1 UE1 UE2 I-CSCF IC1
S-CSCF SC1
29
Registration flow in Full-Proxy
mode
I-CSCF I-CSCF P-CSCF
I-CSCF P-CSCF I-CSCF SBC
server
401-1
Reg 3
P-CSCF
P-CSCF
P-CSCF SBC server
SBC P-CSCF SBC
server server 401-2
Reg 2
A-SBC
A-SBC
SBC client UE1

UE1 SBC client UE1
401-3
Reg 1
UE
UE
Src IP Dst IP Contact Src IP Dst IP
Session flow of SBC (full-proxy)
1: UE send INVITE message

UE1 A-SBC P-CSCF S-CSCF Source IP = UE1
Destination IP = SC
1:invite SDP IP = UE1
2:invite
2: SBC Change source IP to SS
Change destination IP to P-CSCF
3:invite -- Change SDP IP to MS
-- Renew the mapping table
3-4-5: P-CSCF/S-CSCF forward message

4:183
6: SBC -- Change source IP to SC

5:183 -- Change destination IP to UE1
-- Change SDP IP to MC
6:183 -- Renew the mapping table
30
Session flow of SBC (caller side)
S-CSCF S-CSCF S-CSCF P-CSCF UE2

P-CSCF S-CSCF MS
183-4
INVITE 3
P-CSCF P-CSCF
P-CSCF SS UE2
SS P-CSCF MS
INVITE 2 183-5
A-SBC A-SBC
UE1 SC UE1 SC UE1 MC
INVITE 1 183-6
UE1 UE1
Src IP Dst IP SDP Src IP Dst IP SDP
Caller provide Callee provide
Media Stream with SBC

After the media negotiation
In caller UE, the callee SDP (Media) IP is SBC media client IP (MC)
In callee UE, the caller SDP (Media) IP is SBC media server IP (MS)
UE1 UE3
IP bearer
UE2
UE4
SBC Media Mapping Table Example
UE1 MC+port1 MS+port2 UE3 MC Towards private network
UE2 MC+port2 MS+port3 UE4

MS Towards public network

31
Contents
4. 4. SE2900 Workflow
4.1 A-SBC Workflow
4.2 I-SBC Workflow
I-SBC Example
SE1 SE2
Core 2
Softswitch1
I-SBC Softswitch2
Core 1
SE3 SE4
NE IP Address
UE 2
UE 1 SBC SE1 (IMS1-side signaling)
SE2 (IMS2-side signaling) Signaling
SE3 (IMS1-side media) Media
SE4 (IMS2-side media)
32
Signaling Processing Procedure
SS2 SS2
SE2 Softswitch2 SE4 Softswitch2 SE2 UE2

INVITE 3 180
I-SBC I-SBC
SE1 Softswitch1 UE1

INVITE 2 Softswitch1 SE1 UE1 180
SS1 SS1
UE1 Softswitch1 UE1 Softswitch1 UE1 SE3
INVITE 1 180
UE1 Source Destination SDP UE1 Source Destination SDP

IP IP IP IP
Provided by the caller

Provided by the callee
Media Processing Procedure
Core Network A Core Network B
Core 1 Core 2
SBC
SE3
SE4
UE2
UE1
I-SBC media mapping entry
UE1 SE3+port1 SE4+port2 UE2

Signaling

Media
33
Summary
This course introduce the SE2900 product:

Product Overview
Networking and Application Scenarios
Architecture
Signaling Flow
Thank you
www.huawei.com
34

SE2900 Product: Foreword

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SE2900 Product: Foreword

Uploaded by

Copyright:

Available Formats

SE2900 Product

Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved.

What are the technical problems in the application on the IP

SE2900 Product Documentation

Upon completion of this course, you will be able to:

2. SE2900 Application and Features

3. SE2900 Hardware and Software

1.1 What Is the SBC?

1.1 What Is the SBC?

1.2 Why Is the SBC Required?

Restrictions in their communication

Basic Concept Of NAT

NAT (Network Address Translator)

Can reduce the depletion speed of IP address space.

The IP addresses of the private LAN are hidden and protected

Src Addr Dest Addr Src Addr Dest Addr

After NAT Before NAT

NAT Traversal Problem in IMS/NGN

NAT can only translate Protocols adopted in PreNGN/ IMS,

Service of IMS/PreNGN cant be

IP in the IP header: for signaling

IP in SDP: for the media transmission

NAT Traversal Problem in IMS/NGN

IP in the IP header: for signaling

IP in the SIP header: for subsequent

UE1 NAT Public Router SIP server

Src IP: IP1 (private) REGISTER

Dst IP:SIP server

SIP server get the IP in

Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved.

Solution to the NAT Traversal Problem

Two common solutions:

All NAT devices must be Only one

The SBC acts as a proxy for signaling and media streams.

Private IP Intranets NAT is Protocols

2. SE2900 Application and Features

3. SE2900 Hardware and Software

2. SE2900 Application and Features

SE2900 on the IMS/NGN/CS Network

The SE2900 can act as the A-SBC (deployed between the

2. SE2900 Application and Features

Path of a message from the SBC to the P-

Destination IP address in the REGISTER

IP1- access-side IP2- core-side

The domain name system (DNS) is used to route signaling messages

Enterprise network Local network

2. SE2900 Application and Features

3. SE2900 Hardware and Software

4. SE2900 Hardware and Software

3.2 SE2900 Software

SE2900 Single Subrack and Boards

Board Name Full Name Quantity

The SE2900 supports allows a maximum of three subracks to be cascaded to

VPUA0 can support 7.5 K

The service processing

SE2900 Subrack Board Configuration

MCCA subrack0 Access-side signaling

MXU MXU Access-side media

4. SE2900 Hardware and Software

3.2 SE2900 Software

Relationship between board hardware types,

Configure SEISUs or SEESUs in slots 1 and 4 or slots 3 and 6 according

When both a base subrack and an expansion subrack are configured, a

UE1 MC+port1 MS+port2 UE3 MC Towards private network

UE2 MC+port2 MS+port3 UE4

UE1 SE3+port1 SE4+port2 UE2