HNB-GW Administration Guide, StarOS Release 19 First Published: September 30, 2015 Last Modified: December 15, 2015 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
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.
CONTENTS Preface About This Guide xi Conventions Used xi Supported Documents and Resources xii Related Common Documentation xii Related Product Documentation xii Obtaining Documentation xiii Contacting Customer Support xiii CHAPTER 1 HNB Gateway in Wireless Network 1 Product Description 1 HNB Access Network Elements 3 Home NodeB 3 Security Gateway (SeGW) 3 HNB Gateway (HNB-GW) 4 HNB Management System (HMS) 4 Licenses 4 Platform Requirements 5 Network Deployment and Interfaces 5 HNB Gateway in 3G UMTS Ne
Contents DHCP Interface Support Between HNB-GW and HMS 12 RADIUS Change of Authorization Extensions 13 Emergency Call Handling 13 Femto to Femto Handoff via CN 14 GTP-U Tunnels Management Support 15 HNB-UE Access Control 16 HNB Management Function 16 Hybrid Access Mode Support 17 Intra-Domain Multiple CN Support Through Iu-Flex 18 Iu Signalling Link Management Support 19 IuH User-Plane Transport Bearer Handling Support 19 LAI-based FAP Roaming Restriction Support 19 Multiple HNB-GW Service Support 19 Multi
Contents ANSI T1.
Contents Bindings 78 Services and Networks 78 CHAPTER 3 HNB-GW Service Configuration Procedures 81 Information Required to Configure the System as an HNB-GW 82 Required Local Context Configuration Information 83 Required System-Level Configuration Information 83 Required Source Context Configuration Information 87 Required Destination Context Configuration Information 89 RTP Pool Configuration 90 IPv4 RTP Pool Creation Over IuCS 91 IPv4 RTP Pool Creation Over Iuh 92 RTP IP Pool Configuration Verification
Contents Creating and Associating DSCP Template for Control Packets over Iu Interface 106 DHCP Configuration 106 Configuring DHCP Service 107 Configuring Subscriber Template for HNB 107 IuCS over ATM Configuration 108 Configuring the SONET Card 108 Configuring Linkset Id and ATM Parameters 108 Configuring ALCAP Service and AAL2 Node 109 Configuring the ATM Port 109 Associating ALCAP Service with HNB-CS Network Service 110 Iu-Flex Configuration 110 Iu-Flex over IuCS Interface Configuration 110 Iu-Flex over
Contents Using the GTPU Test Echo Command 127 Using the GTPv0 Test Echo Command 128 Using the IPsec Tunnel Test Command 128 Performance Improvement Commands 129 Turning off IPC Message Aggregation To Reduce Latency Towards Core Network 129 CHAPTER 7 Engineering Rules 131 DHCP Service Engineering Rules 131 HNB-GW Engineering Rules 131 Interface and Port Engineering Rules 132 IuCS Interface Rules 132 IuPS Interface Rules 132 Service Engineering Rules 133 CHAPTER 8 CoA, RADIUS DM, and Session Redirection
Contents Viewing the Redirected Session Entries for a Subscriber 142 HNB-GW Administration Guide, StarOS Release 19 ix
Contents HNB-GW Administration Guide, StarOS Release 19 x
About This Guide This preface describes the HNBGW Administration Guide, how it is organized, and its document conventions. The Home NodeB Gateway (HNBGW) is a StarOS application that runs on Cisco ASR 5x00 platforms. For additional platform information, refer to the appropriate System Administration Guide and/or contact your Cisco account representative.
About This Guide Supported Documents and Resources Typeface Conventions Description Text represented as commands This typeface represents commands that you enter, for example: show ip access-list This document always gives the full form of a command in lowercase letters. Commands are not case sensitive.
About This Guide Obtaining Documentation Obtaining Documentation The most current Cisco documentation is available on the following website: http://www.cisco.com/cisco/web/psa/default.html Use the following path selections to access the ePDG documentation: Support > Product Support > Wireless > Additional Products > ASR 5000 Series > HNB-GW Administration Guide. Contacting Customer Support Use the information in this section to contact customer support. Refer to the support area of http://www.cisco.
About This Guide Contacting Customer Support HNB-GW Administration Guide, StarOS Release 19 xiv
CHAPTER 1 HNB Gateway in Wireless Network The Cisco® ASR5x00 system provides 3GPP wireless carriers with a flexible solution that functions as a Home NodeB Gateway (HNB-GW) in HNB Access Network to connect UEs with existing UMTS networks. The Home NodeB Gateway works as a gateway for Home NodeBs (HNBs) to access the core networks.
HNB Gateway in Wireless Network Product Description 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 a Home NodeB (HNB) with limited range radio access in home or Enterprise.
HNB Gateway in Wireless Network HNB Access Network Elements • 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.
HNB Gateway in Wireless Network Licenses Basic function of this entity are: • Authentication of HNB • 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.
HNB Gateway in Wireless Network Platform Requirements Platform Requirements The HNB-GW is a STAROS application that runs on Cisco® ASR 5x00 and virtualized platforms. For additional information, refer to appropriate System Administration Guide and/or contact your Cisco account representative. Network Deployment and Interfaces This section describes the supported interfaces and deployment scenario of HNB-GW in 3G Femto access network.
HNB Gateway in Wireless Network Supported Logical Interfaces • 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.
HNB Gateway in Wireless Network Features and Functionality - Base Software • 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.
HNB Gateway in Wireless Network AAA Server Group Support • Multiple MSC Selection without Iu-Flex, on page 20 • Network Access Control Functions through SeGW, on page 21 • Open Access Mode Support, on page 22 • Paging Optimization Support, on page 23 • QoS Management with DSCP Marking, on page 24 • RADIUS Support, on page 24 • System Management Features, on page 41 • UE Management Function for Pre-Rel-8 UEs, on page 25 • IPNE services enhancement, on page 26 • Grid based paging, on page 28 • IURH based F2F
HNB Gateway in Wireless Network Access Control List Support • 3GPP TS 25.414 V9.0.0 (2009-12): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface data transport and transport signalling (Release 9) • 3GPP TS 25.415 V8.0.0 (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface user plane protocols (Release 8) • 3GPP TS 25.467 V8.0.0.
HNB Gateway in Wireless Network ATM VC Management Support Important For more information on Access Control List configuration, refer IP Access Control List chapter in System Administration Guide. ATM VC Management Support Support for Asynchronous Transfer Mode (ATM) virtual circuits (VC) management function of AAL2 and AAL5 protocol by the HNB-GW in accordance with the following standards: • 3GPP TR 29.814 V7.1.
HNB Gateway in Wireless Network Congestion Control and Management Support • Error Handling: Reporting of some basic error situations, where there are no function-specific error messages defined. • Reset: Function to end the CB message broadcasting to specific service areas by the CBC. • BulkstatsBulkstat variables related to IuBC are added to HNBGW for CBS. • TCP Mode : A new mode 'Server Only'is introduced.
HNB Gateway in Wireless Network DHCP Interface Support Between HNB-GW and HMS Important For more information on Congestion Control support, refer Congestion Control chapter in System Administration Guide. DHCP Interface Support Between HNB-GW and HMS DHCP interface support at HNB-GW is provided to allocate IP address to HNB using DHCP procedure. Without this support IP address is allocated using locally configured IP pool. HNB connects to HNB Security Gateway (Se-GW) via IPSec tunnel.
HNB Gateway in Wireless Network RADIUS Change of Authorization Extensions RADIUS Change of Authorization Extensions Important Dynamic extensions other than RADIUS Change of Authorization (CoA) and Disconnect Message (DM) are not supported on HNB-GW. Dynamic RADIUS extension support provide operators with greater control over subscriber sessions by providing the ability to dynamically manage HNB-UE White-List and/or disconnect the subscriber session.
HNB Gateway in Wireless Network Femto to Femto Handoff via CN • Single Iu and Single RAB: In case of emergency call, HNB-GW does not allow multiple RABs for UE. This means that UE must have only one Iu connection, either CS or PS, and have only one RAB on that Iu connection. HNB-GW implements "Single IU, Single RAB policy" when UE registration comes with Emergency. The RUA-CONNECT has an IE called "establishment cause" which can take values as "Normal" or "Emergency".
HNB Gateway in Wireless Network GTP-U Tunnels Management Support Identifying PLMN ID from Relocation Request A Relocation Request message coming in an SCCP CR message comes directly to HNBMGR from LinkMGR. Earlier the HNBMGR did not have CS/PS network configuration and therefore it did not have the capability to identify the CS/PS network and the plmn id of the request too. HNBMGR has been enhanced to store the CS/PS network configuration.
HNB Gateway in Wireless Network HNB-UE Access Control • 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 Adaptation (RUA) signalling (Release 9) • 3GPP TS 25.469 V9.0.
HNB Gateway in Wireless Network Hybrid Access Mode Support • 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.
HNB Gateway in Wireless Network Intra-Domain Multiple CN Support Through Iu-Flex Important For more information on Hybrid Access Mode support configuration, refer Hybrid Access Mode Configuration section of HNB-GW Administration Guide. Intra-Domain Multiple CN Support Through Iu-Flex Iu-Flex is the routing functionality for intra domain connection of HNB-GW nodes to multiple CN nodes (MSC/SGSN).
HNB Gateway in Wireless Network Iu Signalling Link Management Support Iu Signalling Link Management Support Support for Iu signal link management function for HNB-GW in accordance with the following standards: • 3GPP TS 25.412 V8.0.0 (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface signalling transport (Release 8) • 3GPP TS 25.413 V7.9.
HNB Gateway in Wireless Network Multiple MSC Selection without Iu-Flex With support of multiple HNB-GW service on same chassis operator can utilize the various combination of subscriber access network and connectivity model. This feature can also be utilized if operator wants to use specific HNB-GW services for residential and enterprise service on the same chassis.
HNB Gateway in Wireless Network Network Access Control Functions through SeGW For this support the HNB-GW uses HNB's LAC, received during registration procedure in HNB_REGISTER_REQUEST message, to distribute RANAP-Initial UE message to an MSC. It maps the LAC with MSC point code and a set of LACs configured for each MSC, connected to the HNB-GW.
HNB Gateway in Wireless Network Open Access Mode Support 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.
HNB Gateway in Wireless Network Paging Optimization Support Important HNB-GW support both "Open" mode and "Closed" mode HNBs simultaneously. In case HNB registration is disabled the HNB-GW sends HNB-REGISTER-REJECT with O&M Intervention cause. • UE registration: 1 HNB-GW does not perform access control check of any UE registration request received from an Open Access-mode HNB. 2 HNB-GW also does not perform any check on the UE-identity received in the registration request from an Open Access mode HNB.
HNB Gateway in Wireless Network QoS Management with DSCP Marking ongoing in HNBGW for same domain, Paging will be dropped. If any paging request coming for an IMSI for a particular domain while paging procedure is ongoing in HNBGW for different domain, Paging will be served according to paging algorithm of that domain..
HNB Gateway in Wireless Network UE Management Function for Pre-Rel-8 UEs • RFC-2866, RADIUS Accounting, June 2000 • RFC-2867, RADIUS Accounting Modifications for Tunnel Protocol Support, June 2000 • RFC-2868, RADIUS Attributes for Tunnel Protocol Support, June 2000 • RFC-2869, RADIUS Extensions, June 2000 Within context configured on the system, there are AAA and RADIUS protocol-specific parameters that can be configured.
HNB Gateway in Wireless Network IPNE services enhancement IPNE services enhancement MINE (Mobile and IP Network Enabler) Client referred as IPNE Client for HNBGW cloud service provides a central portal for wireless operators and partners to share and exchange session/network information to realize intelligent services. A MINE client component running on various network nodes likePGW and HNBGW within operator's network to collect and distribute session/network information to MINE servers.
HNB Gateway in Wireless Network IPNE services enhancement General Feture description • IPNE client is a service running within the SMGR context PGW service or HNBGW service • Any external service that wants to interact with IPNE should call IPNE API to create an IPNE handle for each session.
HNB Gateway in Wireless Network Grid based paging Limitations MINE server support available either through actual server or tools. IPNE service configuration and associations will remain as they were in the previous release of HNBGW. Grid based paging Grid based paging is the way to find a UE amongst the HNBs by the HNBGW.
HNB Gateway in Wireless Network Multi-Operator Core Network (MOCN) HENBGW will not route messages at IP level as well as not terminate RNA. HNBs will talk to each other over proprietary interface directly. HNBGW should implement HNBAP TNL Messages which includes TNL-Update-Request, TNL-Update-Response & TNL-Update-Failure and HNBAP Reloc-Complete. Important Iurh-support is a license controlled feature at HNBGW.
HNB Gateway in Wireless Network Multi-Operator Core Network (MOCN) In case of network sharing, single radio network will be shared by more than one network operator. This information about availability of multiple operators needs to be propagated to MS so that it can select correct (home or equivalent) network out of all available networks.
HNB Gateway in Wireless Network Multi-Operator Core Network (MOCN) Network Sharing - HNB without MOCN, CN with EPLMN and MOCN, non-supported UE with rerouting Figure 5: Network Sharing - HNB without MOCN, CN with EPLMN and MOCN, non-supported UE with rerouting In this scenario HNB supports MOCN. CN also supports MOCN. HNB broadcasts common PLMN and PLMN List as well. Supported UEs are able to read all these PLMNs. 1 RMS provisions common PLMN - C as the PLMN of the HNB.
HNB Gateway in Wireless Network Multi-Operator Core Network (MOCN) 9 HNB sends UE Registration request with UE Identity as IMSI to HNBGW. HNBGW is considering that it always receives UE Registration Request with IMSI. MOCN will work even if IMSI is not received; only that re-routing load will increase. 10 HNBGW performs access control on the UE Registration request and sends UE Registration Accept if successful.
HNB Gateway in Wireless Network HNBGW Emergency Call behavior overhaul 1 RMS provisions common PLMN - C as the PLMN of the HNB. It also provisions PLMN A and PLMN B in HNB. 2 HNB sends Common PLMN in HNB Registration Request. 3 HNBGW sends Access Request towards AAA. 4 Optional Allowed PLMN List is sent in Access Accept. This is not implemented in 17.0. 5 HNBGW sends HNB Register Accept to HNB. HNB broadcasts Common PLMN and the PLMN list. 6 UE1 was registered in Macro RNC with PLMN X and LAC X.
HNB Gateway in Wireless Network HNBGW Emergency Call behavior overhaul Architecture This section describes the call flow of RUA connect with Establishment type "Emergency" Figure 7: RUA connect with Establishment type "Emergency" 1 UE1 is registered in HNBGW with HNB1. 2 HNBGW receives RUA connect with "Attach Request" from UE1. Establishment cause IE has value Emergency. 3 Both normal and emergency registered UEs are allowed to accept RUA connects with cause Emergency.
HNB Gateway in Wireless Network 10k UEs per HNB support UE was not stored, HNBGW could not recognize that the incoming Relocation Request is for a UE whose UE context it already has, and it will not know the Registration type of the UE. • During intra-HNBGW SRNS relocation, if a normal UE has 1 or more emergency IUs, and if UE is going to fail access control checks on target HNB (e.g.
HNB Gateway in Wireless Network Hybrid and ACL Phase I support With HNBGW Hybrid and ACL Phase I support HNBGW returns the membership status of the UE with respect to the HNB in the UE Register accept message. Also max length of the list of IMSI (white-list) representing the UEs that can register with an HNB is increased to 150 from 27. Overview This feature provides the UE a means to know its CSG membership status in case of hybrid mode HNB.
HNB Gateway in Wireless Network Hybrid and ACL Phase I support Flows A high level message sequence diagram below explains the overview of the new feature and exchanges of messages between different involved network entities: Figure 8: Hybrid and ACL Call Flow with Involved Networks 1 To register an HNB with HNBGW, (1) HNB register request is sent by HNB to HNBGW. HNB sends HNB-ID to identify itself with the HNBGW.
HNB Gateway in Wireless Network IURH HNB Configuration Transfer 5 Now to initiate a PS or CS call, UE first initiates LA update (IMSI attach) for CS network or Attach Request (GPRS attach) for PS network. This triggers the HNB to initiate (6) UE register request towards HNBGW. HNB passes UE IMSI in the (6) UE register request to HNBGW.
HNB Gateway in Wireless Network IURH HNB Configuration Transfer Architecture Below diagram describes the architecture of IURH HNBG Configuration Transfer. Figure 9: IURH HNB Configuration Transfer Architecture HNB1 and HNB2 both are registered with HNBGW using HNB Registration Procedure. During HNB Registration Procedure, both the HNBs provide their CELL IDs and IP address for direct IURH connectivity in the "Iurh signalling TNL Address" IE.
HNB Gateway in Wireless Network IURH HNB Configuration Transfer each neighbor HNB requested. It provides a set of IP-Address, SCTP IP Address and IURH TNL IP-Address and other information (like access mode) of each requested HNB, which can be used for direct IURH connectivity. If HNBGW is not in position to provide the information of requested HNB, then provides the reason why the information cannot be provided. HNB1 communicates with HNB2 on given IURH IP address for IURH handover.
HNB Gateway in Wireless Network System Management Features indicated in the Neighbor Information Request List IE in the request. The request will be made only for those neighbor HNB's for which HNB does not poses the IURH IP address information. The HNB CONFIGURATION TRANSFER REQUEST will contain the request in Neighbor Information Request IE [1], which contains the HNB Cell identifier (9.2.42 of [1]). The HNB cell identifier uniquely identifies the Cell (HNB) (9.2.25 [1]) within given PLMN Id (9.2.
HNB Gateway in Wireless Network Bulk Statistics Support • 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.
HNB Gateway in Wireless Network Bulk Statistics Support • HNB-GW-HNBAP: Provides HNBAP-level statistics for HNB-GW service • HNB-GW-HNBAP-ACCESS-CLOSED: Provides HNBAP-level statistics filtered for HNBs registered for Closed access mode with HNB-GW service • HNB-GW-HNBAP-ACCESS-HYBRID: Provides HNBAP-level statistics filtered for HNBs registered for Hybrid access mode with HNB-GW service • HNB-GW-HNBAP-ACCESS-OPEN: Provides HNBAP-level statistics filtered for HNBs registered for Open access mode with HNB-G
HNB Gateway in Wireless Network Threshold Crossing Alerts (TCA) Support Additionally, if archiving of the collected statistics is desired, the Bulk Statistics server writes the files to an alternative directory on the server. A specific directory can be configured by the administrative user or the default directory can be used. Regardless, the directory can be on a local file system or on an NFS-mounted file system on the Web Element Manager server.
HNB Gateway in Wireless Network ANSI T1.276 Compliance ANSI T1.276 Compliance ANSI T1.276 specifies security measures for Network Elements (NE). In particular it specifies guidelines for password strength, storage, and maintenance security measures. ANSI T1.276 specifies several measures for password security. These measures include: • Password strength guidelines • Password storage guidelines for network elements • Password maintenance, e.g.
HNB Gateway in Wireless Network IP Security (IPSec) • Change of Authorization: The system supports CoA messages from the AAA server to change data filters associated with a subscriber session. The CoA request message from the AAA server must contain attributes to identify NAS and the subscriber session and a data filter ID for the data filter to apply to the subscriber session. • Disconnect Message: The DM message is used to disconnect subscriber sessions in the system from a RADIUS server.
HNB Gateway in Wireless Network Session Recovery Session Recovery The Session Recovery feature provides seamless failover and reconstruction of subscriber session information in the event of a hardware or software fault within the system preventing a fully connected user session from being disconnected. Session recovery is performed by mirroring key software processes (e.g. session manager and AAA manager) within the system.
HNB Gateway in Wireless Network How HNB-GW Works systems via the server component which implements the CORBA interfaces. The server component is fully compatible with the fault-tolerant Sun® Solaris® operating system. The following figure demonstrates various interfaces between the Cisco Web Element Manager and other network components. Important For more information on WEM support, refer WEM Installation and Administration Guide.
HNB Gateway in Wireless Network HNB Provisioning and Registration Procedure The following figure and the text that follows describe the message flow for HNB provisioning and registration with HNB-GW procedure. Figure 13: HNB Provisioning and Registration Setup Call Flow 1 HNB initialization is performed to obtain HNB configuration from the HNB Management System (HMS). Similarly, HNB-GW discovery is performed to obtain the initial serving HNB-GW information.
HNB Gateway in Wireless Network UE Registration Procedure • HNB Operating Parameters: Such as the selected LAC, RAC, SAC, etc. 6 The HNB-GW uses the information from the HNB-REGISTER-REQUEST message to perform access control of the HNB (e.g. whether a particular HNB is allowed to operate in a given location, etc).
HNB Gateway in Wireless Network Iu Connection Procedures • UE Identity: IMSI of the (U)SIM associated with the UE and the indication about UE capabilities provided in step 1. Important The UE IMSI provided in the UE-REGISTER message is unauthenticated. 7 The HNB-GW checks UE capabilities and if these indicate that CSG is not supported the HNB-GW shall perform access control for the particular UE attempting to utilize the specific HNB.
HNB Gateway in Wireless Network Iu Connection Procedures The following figure and the text that follows describe the message flow for an Iu connection establishment procedure. Figure 15: Iu Connection Establishment Call Flow 1 Upon receiving of UE-REGISTER-ACCEPT message from HNB-GW, the HNB then sends a RUA CONNECT message to HNB-GW containing the RANAP Initial UE message.
HNB Gateway in Wireless Network Iu Connection Procedures the establishment of IuH and IuPS/IuCS connection through HNB, HNB-GW, and SGSN/MSC in core network. Network Initiated Iu Connection Release Procedure This procedure is applicable for release of IuH and IuPS/IuCS connection between HNB to HNB-GW and HNB-GW to SGSN/MSC in core network. The following figure and the text that follows describe the message flow for an Iu connection release procedure initiated by CN (SGSN/MSC).
HNB Gateway in Wireless Network Paging and Serving RNS Relocation Procedures 3 On reception of RANAP Iu Release command in RUA-DIRECT-TRANSFER message the HNB triggers the RCC Connection Release procedure and responds to HNB-GW with RANAP Iu Release Complete command in RUA-DISCONNECT Response message.
HNB Gateway in Wireless Network RANAP Reset Procedures SRNS Relocation Procedure This procedure is applicable for intra-CN or inter-CN handover procedure between HNB to HNB-GW and HNB-GW to SGSN/MSC in core network. The following text describes the call flow for SRNS relocation procedure on HNB-GW: 1 HNB-GW receives Relocation-Request from SGSN/MSC in case subscriber moves from Macrocell to Femtocell in a connected mode. 2 If the request does not contain IMSI (i.e.
HNB Gateway in Wireless Network CBS Call Procedures CN Initiated RANAP Reset Procedure This procedure is applicable for HNB-initiated RANAP Reset procedure between HNB, HNB-GW, and SGSN/MSC in core network. The following text describes the call flow for HNB-initiated RANAP Reset procedure: 1 2 3 4 CN (SGSN/MSC) sends RANAP-RESET command message to HNB-GW for a session. On receiving RANAP-RESET from CN, the HNB-GW starts Guard timer for configured timeout duration.
HNB Gateway in Wireless Network CBS Call Procedures • HNB is responsible for initiating PAGING towards UE when HNB receives WRITE-REPLACE message with Paging-ETWS-Indicator. • HNB responds with ERROR Indication procedure if it receives SABP messages from HNB-GW which can not be detected due to syntactic error. HNB also includes message identifier in the error indication messages for which error has been detected.
HNB Gateway in Wireless Network CBS Call Procedures ◦HNB-GW supports following Elementary Procedures (EP) divided into Class 1 and Class 2; and encoding and decoding of SABP messages: Table 1: Class 1 EPs Elementary Procedure Initiating Message Successful Outcome Response Message Unsuccessful Outcome Response Message Write-Replace WRITE-REPLACE WRITE-REPLACE COMPLETE WRITE-REPLACE FAILURE Kill KILL KILL COMPLETE KILL FAILURE Load Status Enquiry LOAD QUERY LOAD QUERY COMPLETE LOAD QUERY FAILUR
HNB Gateway in Wireless Network CBS Call Procedures ◦In case of Class 2 EPs, HNB-GW receives SABP messages from HNB and sends it to CBC. ◦HNB initiates the RESTART and FAILURE procedures and HNB-GW transparently passes it to the CBC. ◦ERROR INDICATION is initiated by both HNB-GW and HNB.
HNB Gateway in Wireless Network CBS Call Procedures 2 Two types of ERROR Indication messages are possible: 3 Case 1: HNB-GW detects Error in the incoming message from CBC. HNB-GW sends ERROR indication to CBC. HNB-GW includes message identifier, for which error has been detected, in ERROR indication. 4 Case 2: Incoming SABP message from CBC is forwarded to HNB by HNB-GW. HNB detects error in this message which must have been detected at HNB-GW.
HNB Gateway in Wireless Network CBS Call Procedures During the lifetime of Registered HNB, multiple RESTART requests can be received by HNB-GW. HNB-GW forwards these registration requests to the CBC. RESTART Indication may be triggered from the CBC by a RESET request also. This allows recovering from situations where a PDU may occasionally be lost.
HNB Gateway in Wireless Network CBS Call Procedures Call Flows: Handling Class 1 Elementary Procedures WRITE-REPLACE This procedure broadcasts the new information or replaces a message already broadcast to a selected service area or areas.
HNB Gateway in Wireless Network CBS Call Procedures 2 HNB-GW receives WRITE-REPLACE message from CBC and forward this message to the corresponding HNBs in SERVICE AREA LIST provided in the WRITE-REPLACE message. 3 While forwarding message to HNB, HNB-GW modifies WRITE-REPLACE message SERVICE AREA LIST IE. This list only contains Service area to which that HNB belongs.
HNB Gateway in Wireless Network CBS Call Procedures KILL This procedure stops the broadcasting of the indicated messages. Following figure and text points describe the KILL call procedure: Figure 21: KILL Message Call Flow 1 HNB-GW receives KILL message from CBC and forwards this message to the corresponding HNBs in SERVICE AREA LIST provided in the KILL message. 2 While forwarding message to HNB, HNB-GW modifies KILL message SERVICE AREA LIST IE.
HNB Gateway in Wireless Network CBS Call Procedures Important Different message types are identified with different message keys which include message identifier and 12 leftmost bits of old serial number. b If message key for two KILL messages is same, then for those service areas, new KILL is dropped. c If TCP connection is down then the KILL response to be sent to CBC can be dropped. RESET from CBC takes care of such situations. Other collisions are either taken care by HNB or by SABP timeout.
HNB Gateway in Wireless Network CBS Call Procedures 2 HNB-GW forwards it to corresponding HNBs in SERVICE AREA LIST provided in the message. 3 Collision Cases: a ASR5x00 allows multiple KILL for a particular service area, considering that these KILL messages are different. Important Different message types are identified with different message keys which include message identifier and 12 leftmost bits of old serial number.
HNB Gateway in Wireless Network CBS Call Procedures LOAD QUERY The LOAD-QUERY procedure is used obtain the current permissible bandwidth available for broadcast within particular Service Area(s). Following figure and text points describe the LOAD-QUERY call procedure: Figure 23: LOAD-QUERY Call Flow 1 CBC sends LOAD-QUERY message to HNB-GW. 2 HNB-GW forwards the LOAD-QUERY enquiry message to corresponding HNBs in SERVICE AREA LIST provided in the message.
HNB Gateway in Wireless Network CBS Call Procedures RESET The purpose of the Reset procedure is to end broadcasting in one or more Service Areas in the RNC. This procedure is also used by CBC in case of CBC recovery. Following figure and text points describe the RESET call procedure: Figure 24: RESET Message Call Flow 1 CBC sends RESET message to HNB-GW. 2 HNB-GW forwards it to the corresponding HNBs in the SERVICE AREA LIST provided in the message.
HNB Gateway in Wireless Network Supported Standards Supported Standards The HNB-GW complies with the following standards for 3G UMTS Femto wireless data services. • 3GPP References, on page 69 • IETF References, on page 70 • ITU-T Recommendations, on page 73 • Object Management Group (OMG) Standards, on page 73 3GPP References • 3GPP TS 23.003 V8.9.
HNB Gateway in Wireless Network IETF References • 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) • 3GPP TS 25.469 V9.2.0 (2010-06): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iuh interface Home Node B (HNB) Application Part (HNBAP) signalling (Release 9) • 3GPP TS 29.060 V9.0.
HNB Gateway in Wireless Network IETF References • RFC-1570, PPP LCP Extensions, January 1994 • RFC-1643, Definitions of Managed Objects for the Ethernet-like Interface Types, July 1994 • RFC-1701, Generic Routing Encapsulation (GRE), October 1994 • RFC-1850, OSPF Version 2 Management Information Base, November 1995 • RFC-1901, Introduction to Community-based SNMPv2, January 1996 • RFC-1902, Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2), January 1996 •
HNB Gateway in Wireless Network IETF References • RFC 2409, The Internet Key Exchange (IKE) • RFC-2460, Internet Protocol Version 6 (IPv6) • RFC-2461, Neighbor Discovery for IPv6 • RFC-2462, IPv6 Stateless Address Auto configuration • RFC-2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers • RFC-2486, The Network Access Identifier (NAI), January 1999 • RFC-2571, An Architecture for Describing SNMP Management Frameworks, April 1999 • RFC-2572, Message Processing and
HNB Gateway in Wireless Network ITU-T Recommendations • RFC-3143, Known HTTP Proxy/Caching Problems, June 2001 • RFC-3193, Securing L2TP using IPSEC, November 2001 • RFC-3314, Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards, September 2002 • RFC-3316, Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts, April 2003 • RFC-3706, A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) Peers, February 2004 • RFC-3543, Registration
HNB Gateway in Wireless Network Object Management Group (OMG) Standards HNB-GW Administration Guide, StarOS Release 19 74
CHAPTER 2 Understanding the Service Operation The system provides wireless carriers with a flexible solution for providing Security Gateway (SeGW) and Home-NodeB Gateway (HNB-GW) functionality for 3G UMTS networks. The system functioning as an HNB-GW is capable of supporting the following types of subscriber sessions: • CS Session over IuCS: The subscriber is provided voice, video, and CS data service on circuit switch session through MSC in CS network.
Understanding the Service Operation Logical Interfaces Contexts on the system can be categorized as follows: • Source context: Also referred to as the "ingress" context, this context provides the subscriber's point-of-entry in the system. It is also the context in which services are configured.
Understanding the Service Operation Logical Interfaces • 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.
Understanding the Service Operation Bindings 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. • DHCP: This is the interface used by the HNB-GW to communicate with a Dynamic Host Control Protocol (DHCP) Server. The system can be configured to dynamically provide IP addresses for HNBs from the DHCP server in HMS.
Understanding the Service Operation Services and Networks In StarOS 12.1 and earlier, the CS network configured at the system level need to be associated with a Radio Network PLMN configured within HNB-GW service with desired granularity; PLMN level or location-area in that PLMN. In StarOS Release 14.0 and later, the CS network configured at the system level need to be associated with a SCCP Network configured at Gloal Configuration mode.
Understanding the Service Operation Services and Networks HNB-GW Administration Guide, StarOS Release 19 80
CHAPTER 3 HNB-GW Service Configuration Procedures This chapter is meant to be used in conjunction with the other chapters that describes the information needed to configure the system to support HNB-GW functionality for use in HNB access networks. It is recommended that you identify the options from the previous chapters that are required for your specific deployment. You can then use the procedures in this chapter to configure those options.
HNB-GW Service Configuration Procedures Information Required to Configure the System as an HNB-GW Caution While configuring any base-service or enhanced feature, it is highly recommended to take care of conflicting or blocked IP addresses and port numbers for binding or assigning. In association with some service steering or access control features, like Access Control List configuration, use of inappropriate port number may result in communication loss.
HNB-GW Service Configuration Procedures Required Local Context Configuration Information Required Local Context Configuration Information Table 3: Required Information for Local Context Configuration Required Information Description Management Interface Configuration Interface name An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface will be recognized by the system. Multiple names are needed if multiple interfaces will be configured.
HNB-GW Service Configuration Procedures Required System-Level Configuration Information Required Information Description SS7 Routing Domain id and variant An identification for SS7 routing domain and must be an integer between 1 and 12 by which the SS7 routing domain will be identified and configured. A variant can be configured for the SS7 routing domain. some of them are: • ansi: American National Standards Institute (U.S.A.
HNB-GW Service Configuration Procedures Required System-Level Configuration Information Required Information Description Peer Server Process (PSP) instance Specifies the peer server process instance in peer server id. The instance must be an integer from 1 to 4.
HNB-GW Service Configuration Procedures Required System-Level Configuration Information Required Information Description RTP IP Pool name An identification string from 1 to 63 characters (alpha and/or numeric) by which the RTP pool is configured and associated with CS network configuration to allocate RTP IP address to session managers in HNB-GW service over IuCS towards CS core networks. Default MSC point code Specifies the default MSC point-code with HNB-CS network instance.
HNB-GW Service Configuration Procedures Required Source Context Configuration Information Required Source Context Configuration Information Table 5: Required Information for Source Context Configuration Required Information Description Source context name An identification string from 1 to 79 characters (alpha and/or numeric) by which the Source context is recognized by the system.Generally it is identified as source context.
HNB-GW Service Configuration Procedures Required Source Context Configuration Information Required Information Description RTP IP Pool name An identification string from 1 to 63 characters (alpha and/or numeric) by which the RTP pool is configured and associated with HNB-GW service to allocate RTP IP address to Session Manager instances over Iuh towards HNB.
HNB-GW Service Configuration Procedures Required Destination Context Configuration Information Required Information Description GTP-U service name An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service can be associated with HNB-GW system in HNB-GW service for GTP-U tunnel towards HNB access network (HNB). It is pre-configured in Context configuration mode. Multiple names are needed if multiple GTP-U services is used.
HNB-GW Service Configuration Procedures RTP Pool Configuration Required Information Description Physical port number The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces.
HNB-GW Service Configuration Procedures IPv4 RTP Pool Creation Over IuCS When a group of pools have the same priority, an algorithm is used to determine a probability for each pool based on the number of available addresses, then a pool is chosen based on the probability. This method, over time, allocates addresses evenly from the group of pools. Important Note that setting different priorities on each individual pool can cause addresses in some pools to be used more frequently.
HNB-GW Service Configuration Procedures IPv4 RTP Pool Creation Over Iuh IPv4 RTP Pool Creation Over Iuh Use the following example to create the IPv4 address RTP pool for RTP address allocation over Iuh interface towards HNB.
HNB-GW Service Configuration Procedures HNB-GW Service Configuration RG00 SG00 PG00 SG00 Total pool3 30.30.0.0 pool2 20.20.0.0 pool1 10.10.0.0 vpnpool 192.168.1.250 Pool Count: 5 255.255.0.0 255.255.0.0 255.255.0.0 192.168.1.254 0 10 0 0 65534 65524 65534 5 HNB-GW Service Configuration HNB-GW services are configured within source contexts and allow the system to function as an HNB-GW in the 3G UMTS wireless data network.
HNB-GW Service Configuration Procedures HNB-GW Service Configuration To configure the system to work as HNB-GW service with SeGW enabled: Step 1 Optional. Configure threshold parameters by applying the example configuration in the Total HNB-GW Session Thresholds chapter in Thresholding Configuration Guide. Step 2 Optional. Configure system to enable logging facilities for HNB-GW service session subscriber and protocols by applying the example configuration in the Logging Facility Configuration section.
HNB-GW Service Configuration Procedures Hashing Algorithm Configuration Step 24 Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.
HNB-GW Service Configuration Procedures Peer Server Id Configuration for PS Core Network end-point address context end-point bind end Notes: • is IP address of the end point associated with application server process for M3UA end-point parameters in a specific SS7 routing domain instance.
HNB-GW Service Configuration Procedures SCCP Network Instance Configuration associate asp instance end Notes: • is SS7 Routing domain identity number already configured for SS7 routing domain instance. • is the address of MSC configured in HNB-CS Network Configuration section and to be used for SCCP network instance.
HNB-GW Service Configuration Procedures HNB-CS Network Configuration • is name of the packet switched network used with HNB-GW for IuPS session. • is address of the SGSN in SS7 point code format to be used for packet switched traffic through HNB-GW. • is name of the GTP-U service configured in to provide GTP-U tunnel over IuPS interface for packet switched traffic towards PS-CN.
HNB-GW Service Configuration Procedures HNB-GW Service Configuration HNB-GW Service Configuration Use the following example to configure a single of multiple HNB-GW service on system in source context to provide access to HNBs towards core networks: configure sgsn-global aggregate-ipc-msg { linkmgr | sessmgr } { flush-frequency frequency | num-msgs number_msgs } exit context hnbgw-service -noconfirm sctp bind address sctp bind port rtp mux rtcp repo
HNB-GW Service Configuration Procedures GTP-U Service Configuration [no|default] paging {cs-domain|ps-domain} phase2 paging-grid-fanout timeout [no|default] paging {cs-domain|ps-domain} phase3 paging-area-fanout timeout exit Notes: • phase1 page-last-known-hnb: Paging Phase1 Configuration - Forwards Page Req to last-known-hnb. Page the last known HNB for the call.
HNB-GW Service Configuration Procedures x.509 Certificate Configuration x.509 Certificate Configuration Use the following example to configure the x.509 certificates on the system to provide security certification between FAP and SeGW on HNB-GW. configure certificate name
HNB-GW Service Configuration Procedures Multiple MSC Selection without Iu-Flex Configuration exit ikev2-ikesa transform-set list payload match childsa [match {ipv4 | ipv6}] ip-address-alloc dynamic ipsec transform-setlist exit ikev2-ikesa keepalive-user-activity end configure context hnbgw-service security-gateway bind address crypto-template context end Notes: •
HNB-GW Service Configuration Procedures Hybrid Access Mode Configuration configure hnbgw-global end Notes: • is name of the source context in which HNB-GW service is configured. • is name of the HNB-GW service in which Open Access mode support is to be configured. • is number of the UEs allowed to be registered through any Open HNB in Open Access Mode support. By default 16 UEs are allowed.
HNB-GW Service Configuration Procedures Verifying HNB-GW Configuration context hnbgw-service -noconfirm associate cbs-service end Notes: • is name of the source context in which HNB-GW service is configured. • is name of the HNB-GW service in which Open Access mode support is to be configured. • is the IPv4 type IP address of CBS service. • is the IPv4 type IP address of CBC server.
HNB-GW Service Configuration Procedures DSCP Marking Configuration DSCP Marking Configuration Step 1 Step 2 Step 3 Step 4 Modify HNB-GW service to configure the DSCP marking for SCTP and UDP packets over Iuh interface by applying the example configuration in the Configuring DSCP Marking over Iuh Interface section.
HNB-GW Service Configuration Procedures Creating and Associating DSCP Template for Control Packets over Iu Interface • is name of the source context in which HNB-GW service is configured. • is name of the HNB-GW service in which Open Access mode support is to be configured. • For more commands and keyword options, refer Command Line Interface Reference.
HNB-GW Service Configuration Procedures Configuring DHCP Service Configuring DHCP Service Configure a DHCP service for DHCP interface support in the HNB-GW service by applying the following example configuration: configure context dhcp-service -noconfirm dhcp client-identifier ike-id dhcp server selection-algorithm use-all dhcp server dhcp server port 61610 end Notes: • is name of the source context in which HNB-GW service is configured.
HNB-GW Service Configuration Procedures IuCS over ATM Configuration IuCS over ATM Configuration Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Configure and activate the SONET card by applying the example configuration in the Configuring the SONET Card section. Modify the configured SS7 Routing Domain configuration with Linkset Id and ATM parameters by applying the example configuration in the Configuring Linkset Id and ATM Parameters section.
HNB-GW Service Configuration Procedures Configuring ALCAP Service and AAL2 Node priority signaling-link-code exit exit route destination-point-code linkset-id end Notes: • is pre-configured SS7 Routing Domain instance configured at the system level to provide IuCS-over-ATM support to HNB-GW service.
HNB-GW Service Configuration Procedures Associating ALCAP Service with HNB-CS Network Service • is name of the context in which ALCAP service is configured. • is name of the pre-configured ALCAP service which is bound to ATM port for IuCS-over-ATM between HNB-GW and CS core network. • is a pre-configured AAL2 node in ALCAP Service Configuration mode. • is a pre-configured identifier for AAL2 path in AAL2 Node Configuration mode.
HNB-GW Service Configuration Procedures Iu-Flex over IuPS Interface Configuration null-nri offload-msc point-code end Notes: • is name of the HNB-CS network which is already configured and associated with HNB-GW service. • must be an integer between 1 and 10. A zero NRI length value disables the Iu-Flex feature on HNB-GW service.
HNB-GW Service Configuration Procedures Logging Facility Configuration Logging Facility Configuration Use the following example to configure the HNB-GW system to enable the logging and debug facilities for HNB-GW subscriber and related protocols. Important This section provides the minimum instruction set for configuring logging facilities for system monitoring that allows the user to monitor the events and logging.
HNB-GW Service Configuration Procedures Congestion Control Configuration Congestion Control Configuration Step 1 Configure Congestion Control Threshold by applying the example configuration in the Configuring the Congestion Control Threshold section. Step 2 Configure Service Congestion Policies by applying the example configuration in the Configuring Service Congestion Policies section. Step 3 Optional.
HNB-GW Service Configuration Procedures Configuring New Call Policy Configuring New Call Policy To create a new call policy in a busy our or planned maintenance or other operator intervened scenario, apply the following example configuration: newcall policy hnbgw-service [all | name ] reject Notes: • For HNB-GW service sessions reject is the default action for all new calls coming on a specific or all HNB-GW service instance.
HNB-GW Service Configuration Procedures Event IDs for HNB-GW Service Traps Object Id starThreshClearHNBGWHnbSess starentTraps 485 starThreshHNBGWUeSess starentTraps 486 starThreshClearHNBGWUeSess starentTraps 487 starThreshHNBGWIuSess starentTraps 488 starThreshClearHNBGWIuSess starentTraps 489 starHNBGWSGSNRanapReset starentTraps 1155 starHNBGWMSCRanapReset starentTraps 1156 starALCAPNodeReset starentTraps 1157 starALCAPPathReset starentTraps 1158 starALCAPBlock starentTraps 1159 sta
HNB-GW Service Configuration Procedures Event IDs for HNB-GW Service Facility Event ID Range HNB Manager Facility Events 158000-158199 ALCAP Manager Facility Events 160500-160899 ALCAP Protocol Facility Events 160900-161399 SCTP Protocol Facility Events 87300-87499 AAL2 Protocol Facility Events 173200-173299 RANAP User Adaptation Protocol Facility Even 152000-152009 RANAP Protocol Facility Event 87700-87899 AAA Client Facility Events 6000-6999 Alarm Controller Facility Events 65000-65999
CHAPTER 4 Handin with FAP Aggregator This chapter describes Handin with FAP aggregator feature, below are the links to the main sections of the document: • Feature Description, page 117 • How It Works, page 118 Feature Description HNBGW communicates to HNBs on the IUH interface. The HNB can be a normal HNB or an HNB aggregator. Each HNB has a 28 bit unique Cell ID. The Cell ID comprises of the RNC ID and CID.
Handin with FAP Aggregator How It Works resulting integer value. These 20 bits carry a value which is unique for each aggregator. This combined with the remaining 8 bits gives a unique value for each individual HNB behind the aggregator. On receiving a Relocation Request message, HNBGW will first do a lookup using the entire 28 bit Cell ID (if there are normal HNBs too in addition to the aggregator HNBs).
Handin with FAP Aggregator Architecture The following flowchart provides the HNBGW behavior during SRNS Relocation handin procedure: Figure 26: SRNS Relocation Handin Procedure On receiving an HNB Register request message from an HNB at a particular HNBGW service, if the handin with aggregator feature is enabled in the HNBGW service and the 16th bit in the Cell ID is set to 1, then HNBMgr will maintain a lookup table on the HNB context based on the higher 20 bits of the Cell ID.
Handin with FAP Aggregator Architecture HNBGW will not allow multiple HNB aggregators with the same value for the higher 20 bits of their Cell ID. On detecting such a duplicate HNB registration, HNBGW will keep the old registration and delete the new registration.
CHAPTER 5 Monitoring the Service This chapter provides information for monitoring service status and performance using the show commands found in the Command Line Interface (CLI). These command have many related keywords that allow them to provide useful information on all aspects of the system ranging from current software configuration through call activity and status.
Monitoring the Service Monitoring System Status and Performance To do this: Enter this command: Monitor HNB-GW subscribers by call identifier monitor subscriber callid call_id Monitor HNB-GW subscribers by user name identifier monitor subscriber usernamesubscriber_name Monitor HNB-GW subscribers by IMSI value monitor subscriber imsiimsi Monitor HNB-GW subscribers by IP address of UE monitor subscriber ipaddripv4_address Monitoring HNB and UE by Protocol Monitoring Monitor HNB through Protocol Mon
Monitoring the Service Monitoring System Status and Performance To do this: Enter this command: View Subscribers Currently Accessing the System View a listing of subscribers currently accessing the system show subscribers hnbgw-only all View information for a specific subscriber show subscribers hnbgw-only full username username View Subscriber Counters View counters for a specific subscriber show subscribers counters username subscriber_name View Recovered Session Information View session state in
Monitoring the Service Monitoring Logging Facility To do this: Enter this command: View session disconnect reasons specific to HNB-GW service show hnbgw disconnect-reasons View session disconnect reasons with verbose output show session disconnect-reasons View HNB-GW Service Configuration Display a HNB-GW Service Status View all configured HNB-GW services configuration in show hnbgw-service all verbose detail View configuration errors in HNB-GW section in detail show configuration errors section hnbg
Monitoring the Service Clearing Statistics and Counters To do this: Enter this command: Monitor AAL2 logging facility on HNB-GW system logging filter active facility aal2 { critical | error | warning | unusual | info | trace | debug } Monitor Diameter logging facility on HNB-GW logging filter active facility diameter { critical | error | system warning | unusual | info | trace | debug } Monitor ALCAP logging facility on HNB-GW logging filter active facility alcap { critical | error | system warning | u
Monitoring the Service Clearing Statistics and Counters HNB-GW Administration Guide, StarOS Release 19 126
CHAPTER 6 Troubleshooting the Service This chapter provides information and instructions for using the system command line interface (CLI) for troubleshooting issues that may arise during service operation. • Test Commands, page 127 • Performance Improvement Commands, page 129 Test Commands In the event that an issue was discovered with an installed application or line card, depending on the severity, it may be necessary to take corrective action.
Troubleshooting the Service Using the GTPv0 Test Echo Command Keyword/Variable Description all Specifies that GTP-U echo requests will be sent to all Nodes that currently have sessions with the HNB-GW service. The following figure displays a sample of this command's output showing a successful GTPU echo-test from an HNB-GW service bound to address 192.168.157.32 to an SGSN with an address of 192.168.157.2. GTPU test echo -------------SGSN: 192.168.157.
Troubleshooting the Service Performance Improvement Commands Keyword/Variable Description ip_pool_name The name of the IP pool configured for IPsec Tunnel. ip_pool_name can be from 1 to 63 alpha and/or numeric characters in length and is case sensitive. des_ip_address The IP address of destination node of IPsec tunnel. src_ip_address The IP address of source node of IPsec tunnel.
Troubleshooting the Service Turning off IPC Message Aggregation To Reduce Latency Towards Core Network Keyword/Variable Description flush-frequency frequency Configure the frequency, in 100-millisecond intervals, that the aggregated IPC messages will be flushed. frequency : Enter an integer from 1 to 3. Default is 1. num-msgs number_msgs Configure the number of IPC messages to aggregate before flushing.
CHAPTER 7 Engineering Rules This section provides engineering rules or guidelines that must be considered prior to configuring the system for your network deployment.
Engineering Rules Interface and Port Engineering Rules • A maximum of 16 PS-network instances can be configured on system for HNB-GW network function but multiple HNB-GW services can be associated with the same PS-network instance. • A particular HNB-GW service can be associated with more than one CS/PS network entity. • A maximum of 12 HNB-SCCP-network instance can be configured on system for HNB-GW network function.
Engineering Rules Service Engineering Rules • Multiple SGSNs (maximum 25) can be configured through IuPS interfaces within the HNB-GW service instance. Service Engineering Rules The following engineering rules apply to services configured within the system: • A maximum of 256 services (regardless of type) can be configured per system. Caution Large numbers of services greatly increase the complexity of management and may impact overall system performance (i.e.
Engineering Rules Service Engineering Rules HNB-GW Administration Guide, StarOS Release 19 134
CHAPTER 8 CoA, RADIUS DM, and Session Redirection (Hotlining) This chapter describes Change of Authorization (CoA), Disconnect Message (DM), and Session Redirect (Hotlining) support in the system. RADIUS attributes, Access Control Lists (ACLs) and filters that are used to implement these features are discussed. The product administration guides provide examples and procedures for configuration of basic services on the system.
CoA, RADIUS DM, and Session Redirection (Hotlining) DM Overview Important Changing ACL and rulebase together in a single CoA is not supported. For this, two separate CoA requests can be sent through AAA server requesting for one attribute change per request. DM Overview The DM message is used to disconnect subscriber sessions in the system from a RADIUS server. The DM request message should contain necessary attributes to identify the subscriber session.
CoA, RADIUS DM, and Session Redirection (Hotlining) Enabling CoA and DM radius change-authorize-nas-ip end Notes: • must be the name of the AAA context where you want to enable CoA and DM. For more information on configuring the AAA context, if you are using StarOS 12.3 or an earlier release, refer to the Configuring Context-Level AAA Functionality section of the AAA and GTPP Interface Administration and Reference. If you are using StarOS 14.
CoA, RADIUS DM, and Session Redirection (Hotlining) Enabling CoA and DM The following attributes are also supported: • Event-Timestamp: This attribute is a timestamp of when the event being logged occurred. • If 3GPP2 service is configured following additional attributes are supported: • 3GPP2-Disconnect-Reason: This attribute indicates the reason for disconnecting the user. This attribute may be present in the RADIUS Disconnect-request Message from the Home Radius server to the PDSN.
CoA, RADIUS DM, and Session Redirection (Hotlining) Enabling CoA and DM Viewing CoA and DM Statistics View CoA and DM message statistics by entering the following command: show session subsystem facility aaamgr The following is a sample output of this command.
CoA, RADIUS DM, and Session Redirection (Hotlining) Session Redirection (Hotlining) Session Redirection (Hotlining) Important Functionality described for this feature in this segment is not applicable for HNB-GW sessions. Overview Session redirection provides a means to redirect subscriber traffic to an external server by applying ACL rules to the traffic of an existing or a new subscriber session.
CoA, RADIUS DM, and Session Redirection (Hotlining) Operation dynamically to existing subscriber sessions. By default, the ACL is applied as both the input and output filter for the matching subscriber unless the Filter-Id in the CoA message bears the prefix in: or out:. For information on CoA messages and how they are implemented in the system, refer to RADIUS Change of Authorization and Disconnect Message, on page 135. Important Changing ACL and rulebase together in a single CoA is not supported.
CoA, RADIUS DM, and Session Redirection (Hotlining) Viewing the Redirected Session Entries for a Subscriber Viewing the Redirected Session Entries for a Subscriber View the redirected session entries for a subscriber by entering the following command: show subscribers debug-info { callid | msid | username } The following command displays debug information for a subscriber with the MSID 0000012345: show subscribers debug-info msid 0000012345 The following is a sample output of this command:
CoA, RADIUS DM, and Session Redirection (Hotlining) Viewing the Redirected Session Entries for a Subscriber SMGR_STATE_OPEN SMGR_EVT_NEWCALL SMGR_STATE_NEWCALL_ARRIVED SMGR_EVT_ANSWER_CALL SMGR_STATE_NEWCALL_ANSWERED SMGR_EVT_LINE_CONNECTED SMGR_STATE_LINE_CONNECTED SMGR_EVT_LINK_CONTROL_UP SMGR_STATE_LINE_CONNECTED SMGR_EVT_AUTH_REQ SMGR_STATE_LINE_CONNECTED SMGR_EVT_IPADDR_ALLOC_SUCCESS SMGR_STATE_LINE_CONNECTED SMGR_EVT_AUTH_SUCCESS SMGR_STATE_LINE_CONNECTED SMGR_EVT_UPDATE_SESS_CONFIG SMGR_STATE_LINE_C
CoA, RADIUS DM, and Session Redirection (Hotlining) Viewing the Redirected Session Entries for a Subscriber HNB-GW Administration Guide, StarOS Release 19 144
