Cisco ASR 5000 Series Instruction Manual

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY
OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED
WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to
part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own
expense.
The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to
part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can
radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the
equipment off and on, users are encouraged to try to correct the interference by using one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain
version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL
FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR
ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone number s. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illust rative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
© 2010 Cisco Systems, Inc. and/or its affiliated entities. All rights reserved.

Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
CONTENTS
About this Guide ................................................................................................. v
Conventions Used.................................................................................................................................................... vi
Contacting Customer Support ...............................................................................................................................viii
HNB Gateway in UMTS Network........................................................................ 9
Product Description................................................................................................................................................ 10
HNB Access Network Elements........................................................................................................................ 11
Home NodeB ................................................................................................................................................ 11
Security Gateway (SeGW)............................................................................................................................ 12
HNB Gateway (HNB-GW)........................................................................................................................... 12
HNB Management System (HMS) ............................................................................................................... 12
Product Specification ............................................................................................................................................. 13
Licenses ............................................................................................................................................................. 13
Hardware Requirements .................................................................................................................................... 13
Platforms....................................................................................................................................................... 13
System Hardware Components..................................................................................................................... 13
Operating System Requirements ....................................................................................................................... 14
Network Deployment and Interfaces ...................................................................................................................... 15
HNB Gateway in 3G UMTS Network............................................................................................................... 15
Supported Interfaces .......................................................................................................................................... 15
Features and Functionality - Base Software ........................................................................................................... 17
UE Management Function for Pre-Rel-8 UEs ................................................................................................... 17
UE Management Function for Rel-8 UEs.......................................................................................................... 17
HNB Management Function.............................................................................................................................. 18
GTP-U Tunnels Management Support .............................................................................................................. 18
Network Access Control Functions through SeGW .......................................................................................... 18
Authentication and Key Agreement (AKA) ................................................................................................. 19
3GPP AAA Server Support .......................................................................................................................... 19
System Management Features ........................................................................................................................... 19
Management System Overview .................................................................................................................... 20
Bulk Statistics Support.................................................................................................................................. 21
Threshold Crossing Alerts (TCA) Support ................................................................................................... 22
ANSI T1.276 Compliance ............................................................................................................................ 23
Features and Functionality - Licensed Enhanced Feature Software ....................................................................... 24
How HNB-GW Works ........................................................................................................................................... 25
HNB Provisioning and Registration Procedure ................................................................................................. 25
UE Registration Procedure ................................................................................................................................ 27
UE Registration Procedure of Non-CSG UEs or Non-CSG HNBs .............................................................. 27
UE Registration Procedure of CSG UEs and CSG or Hybrid HNBs............................................................ 29
Iu Connection Procedures.................................................................................................................................. 31
Iu Connection Establishment Procedure ....................................................................................................... 31
Network Initiated Iu Connection Release Procedure .................................................................................... 33
Supported Standards............................................................................................................................................... 36
3GPP References ............................................................................................................................................... 36
IETF References ................................................................................................................................................ 36
ITU-T Recommendations .................................................................................................................................. 39
Object Management Group (OMG) Standards .................................................................................................. 39

▀Contents
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Understanding the Service Operation ............................................................ 41
Terminology........................................................................................................................................................... 42
Contexts............................................................................................................................................................. 42
Logical Interfaces.............................................................................................................................................. 43
Bindings ............................................................................................................................................................ 44
Services and Networks ...................................................................................................................................... 44
HNB-GW Service Configuration Procedures ................................................. 47
Information Required to Configure the System as an HNB-GW ........................................................................... 48
Required Local Context Configuration Information ......................................................................................... 48
Required System-Level Configuration Information .......................................................................................... 49
Required Source Context Configuration Information ....................................................................................... 51
Required Destination Context Configuration Information ................................................................................ 53
RTP Pool Configuration......................................................................................................................................... 55
IPv4 RTP Pool Creation Over IuCS .................................................................................................................. 55
RTP IP Pool Configuration Verification ........................................................................................................... 56
HNB GW Service Configuration ........................................................................................................................... 58
Iuh Interface Configuration ............................................................................................................................... 58
SS7 Routing Domain Configuration.................................................................................................................. 59
SCCP Network Instance Configuration............................................................................................................. 60
GTP-U Service Configuration........................................................................................................................... 60
HNB-PS Network Configuration ...................................................................................................................... 61
HNB-CS Network Configuration ...................................................................................................................... 62
HNB-GW Service Configuration ...................................................................................................................... 62
Security Gateway and Crypto map Template Configuration............................................................................. 63
Verifying HNB-GW Configuration................................................................................................................... 64
Event IDs for HNB-GW Service............................................................................................................................ 67
Verifying and Saving Your Configuration ...................................................... 69
Verifying the Configuration ................................................................................................................................... 70
Feature Configuration....................................................................................................................................... 70
Service Configuration........................................................................................................................................ 71
Context Configuration....................................................................................................................................... 72
System Configuration........................................................................................................................................ 72
Finding Configuration Errors ............................................................................................................................ 72
Saving the Configuration ....................................................................................................................................... 74
Saving the Configuration on the Chassis ............................................................................................................... 75
Monitoring the Service ..................................................................................... 77
Monitoring System Status and Performance .......................................................................................................... 78
Clearing Statistics and Counters ............................................................................................................................ 80
Troubleshooting the Service ........................................................................... 81
Test Commands...................................................................................................................................................... 82
Using the GTPU Test Echo Command.............................................................................................................. 82
Using the GTPv0 Test Echo Command ............................................................................................................ 83
Using the IPsec Tunnel Test Command ............................................................................................................ 83
Engineering Rules............................................................................................. 85
DHCP Service Engineering Rules.......................................................................................................................... 86
HNB-GW Engineering Rules................................................................................................................................. 87
Lawful Intercept Engineering Rules ...................................................................................................................... 88
MBMS Bearer Service Engineering Rules............................................................................................................. 89
Service Engineering Rules ..................................................................................................................................... 90

Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
About this Guide
This document pertains to features and functionality that run on and/or that are related to the Cisco® ASR 5000 Chassis,
formerly the Starent Networks ST40.

About this Guide
▀Conventions Used
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Conventions Used
The following tables describe the conventions used throughout this documentation.
Icon
Notice Type
Description
Information Note
Provides information about important features or instructions.
Caution
Alerts you of potential damage to a program, device, or system.
Warning
Alerts you of potential personal injury or fatality. May also alert you of potential
electrical hazards.
Electro-Static Discharge
(ESD)
Alerts you to take proper grounding precautions before handling a product.
Typeface Conventions
Description
Text represented as a
This typeface represents displays that appear on your terminal screen, for example:
Text represented as
This typeface represents commands that you enter, for example:
This document always gives the full form of a command in lowercase letters. Commands
are not case sensitive.
Text represented as a
This typeface represents a variable that is part of a command, for example:
slot_number is a variable representing the desired chassis slot number.
Text represented as menu or sub-
menu names
This typeface represents menus and sub-menus that you access within a software
application, for example:
Click the File menu, then click New
Command Syntax
Conventions
Description
{ or
}
Required keywords and variables are surrounded by grouped brackets.
Required keywords and variables are those components that are required to be entered as part of the
command syntax.

About this Guide
Conventions Used ▀
Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
Command Syntax
Conventions
Description
[ or
]
Optional keywords or variables, or those that a user may or may not choose to use, are surrounded by square
brackets.
|
With some commands there may be a group of variables from which the user chooses one. These are called
alternative variables and are documented by separating each variable with a vertical bar (also known as a
pipe filter).
Pipe filters can be used in conjunction with required or optional keywords or variables. For example:
OR
[ | ]

About this Guide
▀Contacting Customer Support
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Contacting Customer Support
Use the information in this section to contact customer support.
For New Customers: Refer to the support area of http://www.cisco.com for up-to-date product documentation or to
submit a service request. A valid username and password is required to this site. Please contact your local sales or
service representative for additional information.
For Existing Customers with support contracts through Starent Networks: Refer to the support area of
https://support.starentnetworks.com/ for up-to-date product documentation or to submit a service request. A valid
username and password is required to this site. Please contact your local sales or service representative for additional
information.
IMPORTANT:For warranty and repair information, please be sure to include the Return Material Authorization
(RMA) tracking number on the outside of the package.

Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
Chapter 1
HNB Gateway in UMTS Network
The Cisco® ASR 5000 Platform provides 3GPP wireless carriers with a flexible solution that functions as an Home
NodeB Gateway (HNB-GW) in HNB Access Network to connect UEs with existing UMTS networks.
The Home NodeB Gateway is the HNB access network gateway used to connect the Home NodeBs (HNBs) to access
the existing wireless network. The HNB-GW concentrates connections from a large amount of femtocells (HNBs) using
Iuh interface and terminates the connection to existing Core Networks (CS or PS) using the standard Iu (IuCS or IuPS)
interface.
This overview provides general information about the HNB Gateway including:
Product Description
Product Specification
Network Deployment and Interfaces
Features and Functionality - Base Software
Features and Functionality - Licensed Enhanced Feature Software
How HNB-GW Works
Supported Standards

HNB Gateway in UMTS Network
▀Product Description
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Product Description
The Home NodeB Gateway is the HNB network access concentrator used to connect the Home NodeBs (HNBs)/Femto
Access Point (FAP) to access the UMTS network through HNB Access Network. It aggregates Home Node-B or Femto
Access Points to a single network element and then integrates them into the Mobile Operators Voice, Data and
Multimedia networks.
Femtocell is an important technology and service offering that enables new Home and Enterprise service capabilities for
Mobile Operators and Converged Mobile Operators (xDSL/Cable/FFTH plus Wireless). The Femtocell network consists
of a plug-n-play customer premise device generically called an Home NodeB (HNB) with limited range radio access in
home or Enterprise. The HNB will auto-configure itself with the Operators network and the user can start making voice,
data and multimedia calls.
The figure given describes a high level view of UMTS network with Femtocell and HNB-GW.
Figure 1. HNB-GW Deployment in 3G UMTS Network
Once a secure tunnel has been established between the HNB and the SeGW and the HNB has been configured by the
HMS, the Operator has to connect the Femtocell network to their Core Network and services. There are several
interworking approaches to Circuit Switch (CS) and Packet Switch (PS) domains. One approach is to make the
Femtocell network appear as a standard Radio Access Network (RAN) to the Core Network. In addition to the HNB,
SeGW and HMS the RAN approach requires a network element generically called a Femto Gateway (FGW/HNB-GW).
The HNB-GW provides interworking and aggregation of large amount of Femtocell sessions toward standard CN
interfaces (e.g. Iu-CS/PS, A1/2, A10/11, R6). In this approach services and mobility are completely transparent to CN
elements (e.g. MSC, xGSN, PDSN/HA, ASN GW).
The other approach is to connect the Femtocell to an IMS Network to provide CS services to subscribers when on the
Femtocell and deploy a new network element generically called a Convergence Server to provide service continuity and

HNB Gateway in UMTS Network
Product Description ▀
Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
mobility over standard interfaces at the MSC layer (e.g GSM-MAP, IS-41). These two approaches are clearly different
in how CS based services and mobility are achieved.
In accordance with 3GPP standard, the HNB-GW provides following functions and procedures in UMTS core network:
HNB Registration/De-registration Function
UE Registration/De-registration Function for HNB
Iuh User-plane Management Functions
Iuh User plane Transport Bearer Handling
Iu Link Management Functions
IMPORTANT:Some of the features may not be available in this release. Kindly contact your local Cisco
representative for more information on supported features.
HNB Access Network Elements
This section provides the brief description and functionality of various network elements involved in the UMTS Femto
access network. The HNB access network includes the following functional entities:
Home NodeB
Security Gateway (SeGW)
HNB Gateway (HNB-GW)
HNB Management System (HMS)
Home NodeB
A Home NodeB (HNB) is the a customer premise equipment that offers Uu interface to UE and Iuh over IPSec tunnel to
HNB-GW for accessing UMTS Core Network (PS or CS) in femtocell access network.
It also provides the support to HNB registration and UE registration over Iuh with HNB-GW. Apart from these
functions HNB also supports some RNC like functions as given below:
RAB management functions
Radio Resource Management functions
Iu Signalling Link management
GTP-U Tunnels management
Buffer Management
Iu U-plane frame protocol initialization
Mobility management functions
Security Functions
Service and Network Access functions

HNB Gateway in UMTS Network
▀Product Description
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Paging co-ordination functions
UE Registration for HNB
Iuh user-plane Management functions
Security Gateway (SeGW)
Security Gateway is a logical entity in Cisco HNB-GW. Basic function of this entity are; 1) authentication of HNB and
2) providing access to HMS and HNB-GW
This entity terminates the secure tunnelling for Iuh and TR-069 between HNB and HNB-GW and HMS respectively.
In this implementation it is an optional element which is situated on HNB-GW.
HNB Gateway (HNB-GW)
The HNB-GW provides the access to Femto user to UMTS core network. It acts as an access gateway to HNB and
concentrates connections from a large amount of HNBs. The Iuh interface is used between HNB and HNB-GW and
HNB-GW connects with the Core Networks (CS or PS) using the generic Iu (Iu-CS or Iu-PS) or Gn interface.
It also terminates Gn and other interfaces from UMTS core networks to provide mobile data services to HNB and to
interact with HMS to perform HNB authentication and authorization.
HNB Management System (HMS)
It is a network element management system for HNB access. Management interface between HNB and HMS is based
on TR-069 family of standards.
It performs following functions while managing HNB access network:
Facilitates HNB-GW discovery for HNB
Provision of configuration data to the HNB
Performs location verification of HNB and assigns appropriate serving elements (HMS, Security Gateway and
HNB-GW)
The HNB Management System (HMS) comprises of the following functional entities:
File Server: used for file upload or download, as instructed by TR-069 manager
TR-069 Manager: Performs CM, FM and PM functionality to the HNB through Auto-configuration server
(HMS)

HNB Gateway in UMTS Network
Product Specification ▀
Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
Product Specification
This section describes the hardware and software requirement for HNB Gateway.
The following information is located in this section:
Licenses
Hardware Requirements
Operating System Requirements
Licenses
The HNB-GW is a licensed product. A session use license key must be acquired and installed to use the HNB-GW
service.
The following licenses are available for this product:
HNB-GW Software Bundle License, 10K Sessions, 600-00-9020
HNB-GW Software Base License, 1K Sessions, 600-00-9020
For more information on supported features, refer Features and Functionality[ section.
Hardware Requirements
Information in this section describes the hardware required to enable the HNB-GW service.
Platforms
The HNB-GW service operates on the following platforms:
ASR 5000
System Hardware Components
The following application and line cards are required to support HNB-GW services on the system:
System Management Cards (SMC): Provides full system control and management of all cards within the ASR
5000 platform. Up to two SMC can be installed; one active, one redundant.

HNB Gateway in UMTS Network
▀Product Specification
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Packet Services Cards (PSC/PSC2): Within the ASR 5000 platform, PSCs/PSC2s provide high-speed, multi-
threaded EPS Bearer context processing capabilities for HNB-GW services. Up to 14 PSCs/PSC2s can be
installed, allowing for multiple active and/or redundant cards.
Switch Processor Input/Outputs (SPIOs): Installed in the upper-rear chassis slots directly behind the
SPCs/SMCs, SPIOs provide connectivity for local and remote management, central office (CO) alarms. Up to
two SPIOs can be installed; one active, one redundant.
Line Cards: The following rear-loaded line cards are currently supported by the system:
Ethernet 10/100 and/or Ethernet 1000 Line Cards: Installed directly behind PSCs, these cards
provide the physical interfaces to elements in the LTE/SAE network. Up to 26 line cards should be
installed for a fully loaded system with 13 active PSCs/PSC2, 13 in the upper-rear slots and 13 in the
lower-rear slots for redundancy. Redundant PSCs/PSC2s do not require line cards.
Quad Gig-E Line Cards (QGLCs): The 4-port Gigabit Ethernet line card is used in the ASR 5000
system only and is commonly referred to as the Quad-GigE Line Card or the QGLC. The QGLC is
installed directly behind its associated PSC/PSC2 to provide network connectivity to the packet data
network.
10 Gig-E Line Cards (XGLCs): The 10 Gigabit Ethernet Line Card is used in the ASR 5000 system
only and is commonly referred to as the XGLC. The XGLC supports higher speed connections to
packet core equipment, increases effective throughput between the ASR 5000 and the packet core
network, and reduces the number of physical ports needed on the ASR 5000.
The one-port XGLC supports the IEEE 802.3-2005 revision which defines full duplex operation of 10
Gigabit Ethernet.
The XGLC is configured and monitored via the System Management Card (SMC) over the system’s
control bus. Both SMCs must be active to maintain maximum forwarding rates.
Redundancy Crossbar Cards (RCCs): Installed in the lower-rear chassis slots directly behind the SPCs/SMCs,
RCCs utilize 5 Gbps serial links to ensure connectivity between Ethernet 10/100/Ethernet 1000/Quad-Gig-
E/10-Gig-E line cards and every PSC/PSC2 in the system for redundancy. Two RCCs can be installed to
provide redundancy for all line cards and PSCs/PSC2.
IMPORTANT:Additional information pertaining to each of the application and line cards
required to support LTE/SAE services is located in the Hardware Platform Overview chapter of the
Product Overview Guide.
Operating System Requirements
The HNB-GW is available for ASR 5000 running StarOS™ Release 10.0 or later.

HNB Gateway in UMTS Network
Network Deployment and Interfaces ▀
Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
Network Deployment and Interfaces
This section describes the supported interfaces and deployment scenario of HNB-GW in 3G Femto access network.
The following information is provided in this section:
HNB Gateway in 3G UMTS Network
Supported Interfaces
HNB Gateway in 3G UMTS Network
The following figure displays simplified network views of the HNB-GW in an Femto access network accessing UMTS
PS or CS Core Network.
Figure 2. The HNB-GW in UMTS Network and Interfaces
HNB-GW
IPsec
Gatew ay
CS Service
PS Service
HNB-GW AP
Location Services
Broadcast Services
In-line Services
HPLMN/VPLMN
AAA
Location Services
Broadcast Services
Iu-PC/e2
Iu-BC
TR-069/196
SSL/ORBEM
Gi/IP Offload
Gn/Direct Tunnel
GGSN
SGSN
Iu-PS/Iu-Flex
Iu-CS/Iu-Flex
MSC HLR
Optional Services
Optional
Element
PS Mobile Data
Services
Iuh
IPsec IKEv2
RNS
Uu
AAA
HNB
EMS
HMS
Supported Interfaces
In support of both mobile and network originated subscriber UE contexts, the HNB-GW provides the following network
interface support:

HNB Gateway in UMTS Network
▀Network Deployment and Interfaces
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Iuh Interface: This interface is the reference point for the control plane protocol between Home NodeB and
HNB-GW. Iuh uses SCTP over IPSec IKEv2 tunnel as the transport layer protocol for guaranteed delivery of
signaling messages between HNB-GW and Home NodeB.
This is the interface used by the HNB-GW to communicate with HNB on the same Femtocell Access Network.
This interface serves as path for establishing and maintaining subscriber UE contexts.
One or more Iuh interfaces can be configured per system context.
IuCS: This interface is the reference point in UMTS which links the HNB-GW, which acts as an RNC (Radio
Network Controller), with a Mobile Switching Centre (3G MSC) in the 3G UMTS Femtocell Access Network.
This interface provides an IuCS over IP or IuCS over ATM (IP over AAL5 over ATM) interface between the
MSC and the RNC (HNB-GW) in the 3G UMTS Femtocell Access Network. RAN Application Part (RANAP)
is the control protocol that sets up the data plane (GTP-U) between these nodes. SIGTRAN (M3UA/SCTP) or
QSAAL (MTP3B/QSAAL) handle IuCS (control) for the HNB-GW.
This is the interface used by the HNB-GW to communicate with 3G MSC on the same Public Land Mobile
Network (PLMN). This interface serves as path for establishing and maintaining the CS access for Femtocell
UE to circuit switched UMTS core networks
One or more IuCS interfaces can be configured per system context.
IuPS: This interface is the reference point between HNB-GW and SGSN. This interface provides an IuPS over
IP or IuPS over ATM (IP over AAL5 over ATM) interface between the SGSN and the RNC (HNB-GW) in the
3G UMTS Femtocell Access Network. RAN Application Part (RANAP) is the control protocol that sets up the
data plane (GTP-U) between these nodes. SIGTRAN (M3UA/SCTP) or QSAAL (MTP3B/QSAAL) handle Iu-
PS-C (control) for the HNB-GW.
This is the interface used by the HNB-GW to communicate with SGSN on the same Public Land Mobile
Network (PLMN). This interface serves as path for establishing and maintaining the PS access for Femtocell
UE to packet switched UMTS core networks.
One or more Iu-PS interfaces can be configured per system context.
Gi: This interface is the reference point between HNB-GW and IP Offload Gateway. It is used by the HNB-GW
to communicate with Packet Data Networks (PDNs) through IP Offload Gateway in the H-PLMN/V-PLMN.
Examples of PDNs are the Internet or corporate intranets.
One or more Gi interfaces can be configured per system context.
Gn: This interface is the reference point between HNB-GW and GGSN. It is used by the HNB-GW to
communicate with GGSNs on the same GPRS/UMTS Public Land Mobile Network (PLMN).
One or more Gn interfaces can be configured per system context.
TR-069: This interface is an application layer protocol which is used for remote configuration of terminal
devices, such as DSL modems, HNBs and STBs. TR-069 provides an auto configuration mechanism between
the HNB and a remote node in the service provider network termed the Auto Configuration Server. The
standard also uses a combination of security measures including IKEv2 (Internet Key Exchange v2) and IPsec
(IP Security) protocols to authenticate the operator and subscriber and then guarantee the privacy of the data
exchanged.
One TR-069 interface can be configured per HNB node.

HNB Gateway in UMTS Network
Features and Functionality - Base Software ▀
Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
Features and Functionality - Base Software
This section describes the features and functions supported by default in base software on HNB-GW service and do not
require any additional license to implement the functionality with the HNB-GW service.
IMPORTANT:To configure the basic service and functionality on the system for HNB-GW service, refer
configuration examples provide in HNB-GW Administration Guide.
Following features and supports are discussed in this section:
UE Management Function for Pre-Rel-8 UEs
UE Management Function for Rel-8 UEs
HNB Management Function
System Management Features
UE Management Function for Pre-Rel-8 UEs
Support for Pre-Rel-8 UE registration and de-registration in 3G UMTS HNB Access Network in accordance with the
following standards:
3GPP TS 25.467 V8.0.0. (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN architecture for 3G Home NodeB; Stage 2 (Release 8)
3GPP TS 25.469 V8.1.0 (2009-03): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN Iuh interface Home Node B Application Part (HNBAP) signalling (Release 8)
IETF RFC 4960, Stream Control Transmission Protocol, December 2007
The HNB-GW provides UE registration and de-registration procedure for the HNB to convey pre-Rel-8 UE
identification data to the HNB-GW in order to perform access control for the UE in the HNB-GW. The UE Registration
also establishes a UE specific context identifier to be used between HNB and HNB-GW. The procedure triggered when
the UE attempts to access the HNB via an initial NAS message and there is no context in the HNB allocated for that UE.
UE Management Function for Rel-8 UEs
Support for Rel-8 UE registration and de-registration in 3G UMTS HNB Access Network in accordance with the
following standards:
3GPP TS 25.467 V8.0.0. (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN architecture for 3G Home NodeB; Stage 2 (Release 8)
3GPP TS 25.469 V8.1.0 (2009-03): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN Iuh interface Home Node B Application Part (HNBAP) signalling (Release 8)

HNB Gateway in UMTS Network
▀Features and Functionality - Base Software
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
IETF RFC 4960, Stream Control Transmission Protocol, December 2007
The HNB-GW provides UE registration and de-registration procedure for the HNB to convey Rel-8 UE identification
data to the HNB-GW in order to perform access control for the UE in the HNB-GW. The UE Registration also
establishes a UE specific context identifier to be used between HNB and HNB-GW. The procedure triggered when the
UE attempts to access the HNB via an initial NAS message and there is no context in the HNB allocated for that UE.
HNB Management Function
Support for HNB registration and de-registration in 3G UMTS HNB Access Network accordance with the following
standards:
3GPP TS 25.469 V8.1.0 (2009-03): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN Iuh interface Home Node B Application Part (HNBAP) signalling (Release 8)
IETF RFC 4960, Stream Control Transmission Protocol, December 2007
The HNB-GW provides HNB registration and de-registration procedure to register the HNB with the HNB-GW. This
procedure enables the HNB-GW to provide service and core network connectivity for the HNB. This procedure is the
first HNBAP procedure triggered after the SCTP association has become operational between HNB and HNB-GW.
GTP-U Tunnels Management Support
Support to manage the GTP-U tunnels between HNB-GW and GSNs by in accordance with the following standards:
3GPP TS 25.467 V9.1.0 (2009-12): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN architecture for 3G Home Node B (HNB); Stage 2 (Release 9)
3GPP TS 25.468 V9.0.0 (2009-12): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN Iuh Interface RANAP User Adaption (RUA) signalling (Release 9)
3GPP TS 25.469 V9.0.0 (2009-12): 3rd Generation Partnership Project; Technical Specification Group Radio
Access Network; UTRAN Iuh interface Home Node B Application Part (HNBAP) signalling (Release 9)
Network Access Control Functions through SeGW
These functions enable secure user and device level authentication between the authenticator component of the HNB-
GW and a 3GPP HSS/AuC and Diameter-based Wm interface support.
This section describes following features:
Authentication and Key Agreement (AKA)
3GPP AAA Server Support

HNB Gateway in UMTS Network
Features and Functionality - Base Software ▀
Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide ▄
OL-22991-01
Authentication and Key Agreement (AKA)
HNB-GW provides Authentication and Key Agreement mechanism for user authentication procedure over the HNB
Access Network. The Authentication and Key Agreement (AKA) mechanism performs authentication and session key
distribution in networks. AKA is a challenge- response based mechanism that uses symmetric cryptography.
The AKA is the procedure that take between the user and network to authenticate themselves towards each other and to
provide other security features such as integrity and confidentiality protection.
In a logical order this follows the following procedure:
1. Authentication: Performs authentication by, identifying the user to the network; and identifying the network to
the user.
2. Key agreement: Performs key agreement by, generating the cipher key; and generating the integrity key.
3. Protection: When the AKA procedure is performed it protects, the integrity of messages; confidentiality of
signalling data; and confidentiality of user data
3GPP AAA Server Support
This interface between the SeGW and AAA Server provides a secure connection carrying authentication, authorization,
and related information. in accordance with the following standards:
3GPP TS 33.320 V9.1.0 (2010-03): 3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; Security of Home Node B (HNB) / Home evolved Node B (HeNB) (Release 9)
This reference point is located between 3GPP AAA Server/Proxy and HNB-GW. The functionality of this reference
point is to enable following requirements on SeGW:
The SeGW shall be authenticated by the HNB using a SeGW certificate.
The SeGW shall authenticate the HNB based on HNB certificate.
The SeGW authenticates the hosting party of the HNB in cooperation with the AAA server using EAP-AKA.
The SeGW shall allow the HNB access to the core network only after successful completion of all required
authentications.
Any unauthenticated traffic from the HNB shall be filtered out at the SeGW
System Management Features
This section describes following features:
Management System Overview
Bulk Statistics Support
Threshold Crossing Alerts (TCA) Support
ANSI T1.276 Compliance

HNB Gateway in UMTS Network
▀Features and Functionality - Base Software
▄Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide
OL-22991-01
Management System Overview
The system's management capabilities are designed around the Telecommunications Management Network (TMN)
model for management - focusing on providing superior quality network element (NE) and element management system
(Web Element Manager) functions. The system provides element management applications that can easily be integrated,
using standards-based protocols (CORBA and SNMPv1, v2), into higher-level management systems - giving wireless
operators the ability to integrate the system into their overall network, service, and business management systems. In
addition, all management is performed out-of-band for security and to maintain system performance.
Operation and Maintenance module of ASR 5000 offers comprehensive management capabilities to the operators and
enables them to operate the system more efficiently. There are multiple ways to manage the system either locally or
remotely using its out-of-band management interfaces. These include:
Using the command line interface (CLI)
Remote login using Telnet, and Secure Shell (SSH) access to CLI through SPIO card's Ethernet management
interfaces
Local login through the Console port on SPIO card using an RS-232 serial connection
Using the Web Element Manager application
Supports communications through 10 Base-T, 100 Base-TX, 1000 Base-TX, or 1000
Base-SX (optical gigabit Ethernet) Ethernet management interfaces on the SPIO
Client-Server model supports any browser (i.e. Microsoft Internet Explorer v5.0 and above or Netscape v4.7 or
above, and others)
Supports Common Object Request Broker Architecture (CORBA) protocol and Simple Network Management
Protocol version 1 (SNMPv1) for fault management
Provides complete Fault, Configuration, Accounting, Performance, and Security (FCAPS) capabilities
Can be easily integrated with higher-level network, service, and business layer applications using the Object
Management Group's (OMG’s) Interface Definition Language (IDL)
The following figure demonstrates these various element management options and how they can be utilized within the
wireless carrier network.