Training Document WRAN13.0 BSC6900 (V900R013C00) LBO Feature Description-20110212-A-1.0

Security Level: Internal Use
WRAN13.0 BSC6900
(V900R013C00) LBO Feature
Description
Global Technical Support
www.huawei.com
Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
Upon completion of this course, you will be able to:
Explain the design and implementation method of the radio network

controller (RNC) local breakout (LBO) feature.
Configure or enable RNC LBO
Understand the impacts on the system (counters) and precautions

after the RNC LBO feature is enabled.
Page2
Contents
1. Purpose and Application Scenarios of the RNC LBO
Feature
2. Design and Implementation Method of the RNC LBO
Feature
3. Configuration of the RNC LBO Feature
4. References of the RNC LBO Feature
Page3
Purpose of the RNC LBO Feature

LBO sends some packet switched (PS) service data to the Internet
through the RNC Internet egress rather than through the backbone,
SGSN, and GGSN between the IuPS and Gi interfaces. The
advantages of LBO are as follows:
Transmission resources are saved.
SGSN and GGSN node cost is reduced.
Data transmission delay is shortened.
Page4
Definition of the RNC LBO
LBO is a new feature introduced in MBSC RAN13. RAN13 LBO

supports NAT-based offload.
Offload is a sub-feature of LBO. With this sub-feature, the RNC

transmits some PS service data through the RNC Internet egress.
In NAT mode, offload of downlink data flows is implemented

through uplink data flow control.
RNC
Iub
SGSN
IuP
s
GGSN
G
n
Gi
Offload
Gi
Application Scenarios
The Gi interface between the RNC and the Internet is supported only by
the FG2c and GOUc. There are no special scenario requirements.
Advantages of the feature

Transmission resources are saved.
SGSN and GGSN node cost is reduced.
Data transmission delay is shortened.
Restrictions of the feature

The service mobility is degraded. The data flows on the application
layer are interrupted during relocation.
Page6
Networking, Hardware, and Software

Planning
Involved network element (NE): RNC
Networking requirements
There are no special networking requirements.
The Gi interface uses IP transmission.
Hardware requirements
The Gi interface is supported only by the FG2c and GOUc.
Software requirements
RNC: V9RAN13
Page7
Contents
Feature
Feature
Page8
Design and Implementation Method

RAN13 LBO supports NAT-based offload.
The offload policy refers to the following:
1. Control-plane determination: RAB-based determination of user class (gold, silver, and copper), traffic class, international mobile equipment
identity (IMEI), international mobile subscriber identity (IMSI), direct tunnel user, and cell capability.
2. User-plane determination: Stream-based determination. You can specify whether offload is implemented for the streams corresponding to
the destination IP address of the user equipment (UE).
M2000
LMT
Offload Policy
Policy
Matching
Page9
Offload Determination in the Control

Plane
During service establishment, the RAB that allows offload is identified, and offload is configured
for the user plane.
The data flows sent from the IuPS interface can use the same services as on the traditional network.
The data flows sent from the offload interface are not worse (offload data flows feature short delay and
low cost) than IuPS data flows in all aspects except mobility.
Offload RAB condition
The operator enables offload.
The access cell supports offload.
The IMSI of the UE is within the offload-capable IMSI segment specified by the operator.
The IMEI of the UE is within the offload-capable IMEI segment specified by the operator. (optional)
Only one RAB supports offload.
The Packet Data Protocol (PDP) type of the access user is IPv4.
The access point name (APN) requested by the UE is within the offload-capable APN range. (optional)
The RAB parameter (gold/silver/copper, service type) of the access user allows offload.
Whether the non-direct tunnel service of the RNC supports offload. The direct tunnel service refers to
the service in which data is transmitted directly from the RNC to the GGSN without passing through
SGSN. The RNC can obtains the service peer address from the RAB Assignment message to
determine whether the user is a direct tunnel user.
Offload Determination in the User Plane
The operator provides services such as the multimedia messaging service (MMS), WAP gateway, and portal.
The servers may be located on the mobile network and behind the GGSN. Most services are value-added
services that require particular charging. Therefore, when users access the servers, the data must be
transmitted through the mobile network. The IP addresses of the servers can be configured on the RNC in
advance. Then, the RNC can identify the data flows by checking the server IP addresses in the UE data packets
and the GTPU can send the data flows to the core network through the IuPS interface.
The other data flows are generated and sent by the RNC through the Gi interface to the external network. This
can reduce the cost and shorten service delay.
Web
Browsing P2P
RAB
Destination Address
Matching
Data packet
Offload
Other IP Address
WAP MMS
Special Server Ip
Address
Internet
IuPS
MMS
WAP
Offload
Policy
NAT Solution
The RNC can analyze only uplink data flows and it sends the data flows that meet the rules through the Gi interface.
In actual applications, the downlink data volume overwhelms the uplink data volume. The source IP address in the
uplink data must be translated to the external network address of the Gi interface by means of NAT so that downlink
data enters the Gi interface, that is, the data packets returned by the servers are sent to the RNC rather than the
GGSN. In this way, downlink data flow control is implemented by means of uplink data flow control.
NAT streams data, but you need to know the following NAT restrictions:
1. Some protocols, such as File Transfer Protocol (FTP), carry the requested data transmission port number in the
flow control payload. Consequently, data transmission cannot be established. In this case, data of such protocols
must be processed by upper-layer protocols (ALG), and then data can pass through NAT. ALG is short for
application level gateway. Currently, the RNC supports the ALG algorithm for FTP, Internet Control Message
Protocol (ICMP), Hypertext Transfer Protocol (HTTP), Real-Time Streaming Protocol (RTSP), and Simple Mail
Transfer Protocol (SMTP) data flows.
2. If these data flows are encrypted by using IPSec, upper-layer protocol processing cannot be implemented and
data cannot pass through NAT.
SIP:66.2.2.2/3000
DIP:88.1.1.1/21
10.1.1.100
SIP:10.1.1.100/21
DIP:88.1.1.1/21
RAB
SIP:88.1.1.1/21
DIP:10.1.1.100/21
NAT
LBO
policy
66.2.2.2
88.1.1.1
Gi for
offload
SIP:88.1.1.1/21
DIP:66.2.2.2/3000
GTPU
IuPs
Gi
GGSN
Local GW Mode
In local GW mode, the RNC integrates GGSN functions. The RNC can process
local services and can connect to another RNC through the IuPS interface. For
the SGSN, the RNC works as a GGSN that supports the standard Gi/Gn
interface. The offload policy is controlled by the SGSN, and service offload is
implemented by means of GGSN selection (GGSN integrated in the RNC).
The R13 version implements offload only in NAT mode.
RNC
IuPs
Gn
RNC
RAB1
RAB2
LocalGW
GTPU
Gn
SGSN
Gi
IuPs
GGSN
Gi
Signaling Process of Offload

UE
RNC
SGSN
GGSN
PDN
1. RRC Connection
Setup
2. Service Request
The RNC analyzes the NAS messages (PDP

context activation request and received messages)
to obtain information about LBO determination,
configuration, and charging.
Based on the configured offload determination

conditions, the RNC identifies the RAB that
requires offload. For the RAB that may require
offload, the RNC configures the user-plane context
(user-plane offload determination and Gi interface).
The RNC configures the downlink data forwarding

route of the Gi interface board (mapping between
the UE IP address and the user-plane instance).
The user plane performs offload determination for

uplink data flows based on the destination IP
addresses and then selects the Gi or IuPS
interface to transmit the data.
3. Security Functions
4. Service Accept
5. Activate PDP Context Request
NAS analysis
6. Create PDP Context Request
7. Create PDP Context Response
8. RAB_Assignment_Reqest
9. RB Setup
10. Setup GTPU Tunnel
11. Offload policy
SetupOffload
context
12. RAB_Assignment_Response
13. Activate PDP Context Accept
NAS Message
analysis
Gi Port configuration
14 User
plane
Offload
policy
NodeB
RNC
GGSN
SGSN
PDN
Mobility of Offload
Gi
Gi Offload
Gi Offload
GGSN
IuPs
RNC
NodeB
Iur
NodeB
RNC
RNC
NodeB
NodeB
A UE moves between base transceiver stations

(BTSs) in the following scenarios in the case
that the RNC provides the Gi interface:
1. The UE moves within the RNC. The service
continuity is not affected.
2. The UE moves between RNCs that provide Iur
interfaces. The Iur interfaces guarantee service
continuity, and the serving RNC implements
offload.
3. The UE moves between RNCs that do not
provide the Iur interface. The SRNS is relocated,
then the Gi interface of the original RNC cannot
be used any longer. The new RNC is required to
provide services for the UE by using the Gi or
IuPS interface. The anchor IP address, however,
is changed, and all the offload sessions are
interrupted. Upper-layer protocol processing is
required to recover the sessions.
Intranet Security of Offload

The external network security can be guaranteed by deploying firewalls. The uplink traffic from UEs,
however, directly enter the Gi domain. The traffic is a dangerous attack source for the Gi domain and
other UEs.
The traffic of a user can directly access the device in the Gi domain and consume device resources.
The traffic of a user can directly attack other UEs and cause fee loss of other users.
The traffic of a user can scan the IP address, search system bugs, and may consume the routing
resources of the bearer device that is capable of learning.
The packets of an unauthorized user can attack the system by using IP address spoofing.
The RNC that supports LBO needs to take security measures to defend against the UE IP attack in the
user plane.
The RNC identifies and discards the spoofing packets from UEs (the source address is different from
the allocated address) and the spoofing packets from the external network (the source IP address is
the same as the destination IP address). In addition, the RNC releases the user from which the
number of spoofing packets exceeds the threshold in a unit period.
The RNC limits the SYN packet connection rate of mobile users to defend against the distributed
denial of service (DDoS) attacks from users.
Constantly Online of Offload

If offload is completely implemented for UE data transmission, the GGSN
releases the Iu interface after detecting that the UE does not transmit data
for a long time. As a result, the service is interrupted. The following solution
is provided to rectify this fault:
The RNC sends PING packets to keep the PDP context alive before the
inactivity detection timer expires.
Modify the inactivity detection configuration on the GGSN, that is, extend the
time limit in which no packet is sent before release, or disable inactivity
detection. The RNC controls user inactivity detection. The RNC requests to
release the RAB only if the RAB does not transmit data for a long time. When
the RAB/Iu connection is released, the GGSN deletes the PDP context.
Contents
Feature
Feature
Page18
Data Configuration Procedure
Describes the key data configuration procedure and key parameters.
Step 1: Enable offload.

ADD/MOD UOFFLOAD: CnOpIndex=0, OffloadSwitch=ON, NonDTRAB=
PERMIT_OFFLOAD, RegAPN= NOT_PERMIT_OFFLOAD, GiPercent=80;
Step 2: Set the type and priority of the service that supports offload.
ADD UOFFLOADRAB:CnOpIndex=0, UserPriority=GOLDEN_USER,
OffloadService=STREAMING-1&INTERACTIVE-1&BACKGROUND-1;
Step 3: Set the list of IMSIs that support offload.

ADD UOFFLOADIMSI: CnOpIndex=0, IMSIStart="000000000000000",
IMSIEnd="999999999999999";
Step 4: Set the cell that supports offload.

MOD UCELLALGOSWITCH: CellId=0, OffloadSwitch=ON;
Step 5: Add the Gi interface.

ADD UGIPORT: SRN=0, SN=14, PORTTYPE=ETHER, PN=0;
Page19
Step 6: Set an IP address for the Gi interface.

ADD ETHIP: SRN=0, SN=14, PN=0, IPINDEX=0, IPADDR="10.53.50.69",
MASK="255.255.255.240";
Step 7: Set a route for the Gi interface.

ADD IPRT: SRN=0, SN=14, DSTIP="0.0.0.0", DSTMASK="0.0.0.0",
NEXTHOP="10.53.50.68", PRIORITY=HIGH, REMARK="Gi";
Step 8: Add the NAT address pool.

ADD UNATRESPOOL: SRN=0, SN=14, PN=0, NATINDEX=0,
STARTADDR="172.168.0.100", ENDADDR="172.168.0.101", MAXPN=65535,
MINPN=10000;
Step 9: Enable NAT.

SET UNATSWITCH: NATSW=ON;
Page20
Step 10: Enable the corresponding ALG function.

SET UNATALG: PROTOCOLTYPE=FTP, ALGSW=ON, AGINGTIMER=600;
SET UNATALG: PROTOCOLTYPE=MSN, ALGSW=ON, AGINGTIMER=240;
SET UNATALG: PROTOCOLTYPE=ICMP, ALGSW=ON, AGINGTIMER=20;
SET UNATALG: PROTOCOLTYPE=RTSP, ALGSW=ON, AGINGTIMER=120;
SET UNATALG: PROTOCOLTYPE=SMTP, ALGSW=ON, AGINGTIMER=240;
Step 11: Enable IMEI determination.

ADD UOFFLOAD:RsvdPara1=LBO_IMEITAC_SWITCH-1;
Step 12: Add an IMEI device number.

ADD UOFFLOADIMEITAC: TAC=12345678, Description="Iphone";
Step 13: Add the host IP address or network segment that cannot be accessed in
offload mode.
ADD UUNOFFLOADIP: CnOpIndex=0, IpAddr="10.141.115.218",
Mask="255.255.255.255";
Page21
Impact on KPIs
This feature is a Trial feature, and no counter is added.
Configuration Procedure on the CME
The configuration step is described as follows:
Step1: Enable the offload switch.

The procedure for navigating to the Global SIPTO Parameters table is as follows: On the Main View
tab, right-click an MBSC, and choose UMTS Radio Global Configuration Express from the shortcut
menu. On the Properties tab, click Global SIPTO Parameters. The Global SIPTO Parameters table is
displayed.
Page24
Step2: Set the offload service type and priority.

The procedure for navigating to the SIPTO RAB Restriction table is as follows: On the Main View tab,
right-click an MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu.
On the Properties tab, click SIPTO RAB Restriction. The SIPTO RAB Restriction table is displayed in
the right pane.
Page25

Step3: Set the IMSI range.
The procedure for navigating to the SIPTO IMSI Range table is as follows: On the Main View tab, rightclick an MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu. On
the Properties tab, click SIPTO IMSI Range. The SIPTO IMSI Range table is displayed in the right
pane.
Page26
Step4: Turn on the offload switch of a cell.

MOD UCELLALGOSWITCH: CellId=0, OffloadSwitch=ON;
The procedure for navigating to the Cell Algorithm Switches table is as follows: On the Main View tab,
right-click a cell, and choose Cell Configuration Express from the shortcut menu. On the Properties
tab, click Cell Algorithm Switches. The Cell Algorithm Switches table is displayed in the right pane.
Page27
Step5: Run the ADD UGIPORT: SRN=0, SN=14, PORTTYPE=ETHER, PN=0; command to add a Gi port.
The procedure for navigating to the Gi port table is as follows: On the Transmission View tab, right-click
Gi, and choose Gi Configuration Express from the shortcut menu. On the Properties tab, click Gi port.
The Gi port table is displayed in the right pane.
Page28
Step6: Configure IP addresses for Gi ports.

The procedure for navigating to the ETHIP table is as follows: On the Transmission View tab, right-click
Gi, and choose Gi Configuration Express from the shortcut menu. On the Properties tab, click
Ethernet Port IP Address. The ETHIP table is displayed in the right pane.
Page29
Step7: Add IP routes for a Gi.

The procedure for navigating to the IP Route table is as follows: On the Transmission View tab, rightclick Gi, and choose Gi Configuration Express from the shortcut menu. On the Properties tab, click IP
Route. The IP Route table is displayed in the right pane.
Page30
Step8: Add an NAT resource pool.

The procedure for navigating to the NAT resource pool table is as follows: On the Transmission View
tab, right-click Gi, and choose Gi Configuration Express from the shortcut menu. On the Properties
tab, click NAT resource pool. The NAT resource pool table is displayed in the right pane.
Page31
Step9: Turn on the NAT switch.

The procedure for navigating to the NAT function switch table is as follows: On the Transmission View
tab, right-click Gi, and choose Gi Configuration Express from the shortcut menu. On the Properties
tab, click NAT function switch. The NAT function switch table is displayed in the right pane.
Page32
Step10: Turn on the ALG switch.

The procedure for navigating to the NAT function parameters table is as follows: On the Transmission
View tab, right-click Gi, and choose Gi Configuration Express from the shortcut menu. On the
Properties tab, click NAT function parameters. The NAT function parameters table is displayed in the
right pane.
Page33
Step11: Turn on LBO_IMEITAC_SWITCH.

The procedure for navigating to the OFFLOAD table is as follows: On the Main View tab, right-click an
MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu. On the
Properties tab, click OFFLOAD. The OFFLOAD table is displayed in the right pane.
Page34
Step12: Add an IMEI TAC.

The procedure for navigating to the OFFLOADIMEITAC table is as follows: On the Main View tab, rightclick an MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu. On
the Properties tab, click OFFLOADIMEITAC. The OFFLOADIMEITAC table is displayed in the right
pane.
Page35
Step13: Add a host IP address or network segment that is not permitted to be accessed in offload mode.
The procedure for navigating to the UNOFFLOADIP table is as follows: On the Main View tab, right-click
an MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu. On the
Properties tab, click UNOFFLOADIP. The UNOFFLOADIP table is displayed in the right pane.
Page36
Contents
Feature
Feature
Page23
Acronyms and Abbreviations

LBO
Local BreakOut
NAT
Network Address Translation
ALG
Application Level Gateway
GI
GPRS interface
GGSN
Gateway GPRS Support Node
SGSN
Serving GPRS Support Node
CN
Core Network
NE
Network Element
Page25
Thank you
www.huawei.com

Training Document WRAN13.0 BSC6900 (V900R013C00) LBO Feature Description-20110212-A-1.0

Загружено:

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

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

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

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

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

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

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

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

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

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

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

Training Document WRAN13.0 BSC6900 (V900R013C00) LBO Feature Description-20110212-A-1.0

Загружено:

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

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

Security Level: Internal Use

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

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

Explain the design and implementation method of the radio network

Configure or enable RNC LBO

Understand the impacts on the system (counters) and precautions

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

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

Purpose of the RNC LBO Feature

Transmission resources are saved.

SGSN and GGSN node cost is reduced.

Data transmission delay is shortened.

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

Definition of the RNC LBO

LBO is a new feature introduced in MBSC RAN13. RAN13 LBO

Offload is a sub-feature of LBO. With this sub-feature, the RNC

In NAT mode, offload of downlink data flows is implemented

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

Advantages of the feature

Restrictions of the feature

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

Networking, Hardware, and Software

Involved network element (NE): RNC

There are no special networking requirements.

The Gi interface uses IP transmission.

The Gi interface is supported only by the FG2c and GOUc.

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

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

Design and Implementation Method

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

Offload Determination in the Control

Offload RAB condition

The operator enables offload.

The access cell supports offload.

Only one RAB supports offload.

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

Offload Determination in the User Plane

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

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

The R13 version implements offload only in NAT mode.

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

Signaling Process of Offload

The RNC analyzes the NAS messages (PDP

Based on the configured offload determination

The RNC configures the downlink data forwarding

The user plane performs offload determination for

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

A UE moves between base transceiver stations

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

Intranet Security of Offload

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

Constantly Online of Offload

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

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

Data Configuration Procedure

Describes the key data configuration procedure and key parameters.

Step 1: Enable offload.

Step 3: Set the list of IMSIs that support offload.

Step 4: Set the cell that supports offload.

Step 5: Add the Gi interface.

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

Data Configuration Procedure

Step 6: Set an IP address for the Gi interface.