> New In Release 10.0
> This chapter provides information on the major features and functionality added to the software with this release. Topics covered in this chapter are:
> Common Features
> HNB-GW in UMTS Femto Network
> The HNB-GW is new in Release 10.0.
> With this release, Cisco Systems introduced Home-NodeB Gateway. 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.
> Benefits
> The HNB-GW service is supported on Cisco’s industry-leading ASR 5000 platforms, delivering unrivaled throughput, call transaction rates, and packet processing, along with significant memory resources.
> 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: This is an indicative list of features supported in this release. Kindly contact your local Cisco representative for more information on supported features.
> Description
> 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.
> 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.
> HNB-GW Deployment in 3G UMTS Network
> For more information on this product, refer HNB Gateway in UMTS Networks chapter of this guide.
> License Keys
> Requires separate product license key.
> Content Filtering in Release 10.0
> This section in development.
> ECS Features
> This section in development.
> eHRPD Features
> This section contains information on new 9.0 features that pertain to the HRPD Serving Gateway (HSGW) and the PDN Gateway (P-GW) supporting eHRPD network services.
> New HSGW Features
> This section in development.
> New P-GW Features
> This section in development.
> ESS Features
> This section in development.
> GSS Features
> This section in development.
> HA Features
> This section in development.
> inPilot Features
> This section in development.
> LTE/SAE Features
> This section contains information on new 10.0 features that pertain to the PDN Gateway (P-GW), the Mobility Management Entity (MME) and the Serving Gateway (S-GW) supporting LTE/SAE network services.
> This section in development.
> PDSN Features
> This section in development.
> Peer-to-Peer Features
> This section in development.
> SCM Features
> This section provides information for new features in Release 10.0 for the Session Control Manager (SCM). Additional information on these features can be found in the Session Control Manager Overview chapter, in the Session Control Manager Administration Guide, and in the CLI Reference Guide.
> IMS Architecture
> Interrogating-CSCF
> The I-CSCF can now be incorporated into the Serving-CSCF only. There are no longer any I-CSCF features supported by an integrated Proxy/I-CSCF.
> Emergency-CSCF Supported
> The Emergency-CSCF (E-CSCF) is a network element in IMS which is responsible for routing an emergency call to a Public Safety Answering Point (PSAP).
> To identify the next hop PSAP, E-CSCF interacts with the Location Retrieval Function (LRF). LRF provides the necessary routing information so that E-CSCF can route the request to the appropriate PSAP.
> E-CSCF Interfaces
> The following diagram shows the interfaces/reference points associated with the E-CSCF:
> SIP Interfaces
> MI - The reference point between the E-CSCF and Location Retrieval Function (LRF). The MI interface is used for routing an emergency call to a Public Safety Answering Point (PSAP). The E-CSCF interacts with the Location Retrieval Function (LRF) to identify the next hop PSAP.
> New Features and Functionality - Base Software
> Call Types Supported
> The following new call type is supported:

> • | Emergency calls - are managed through the addition of an Emergency Call/Session Control Function (E-CSCF) that routes emergency calls to a Public Safety Answering Point (PSAP).

> Emergency Call Support
> P-CSCF gives priority to emergency calls, especially in a congested network. In addition, P-CSCF rejects new calls to any user who is in an emergency call.
> MSRP Support
> The SCM supports Message Session Relay Protocol (MSRP) session and page modes.
> Shared Initial Filter Criteria (SiFC)
> If both the HSS and the S-CSCF support this feature, subsets of iFC may be shared by several service profiles. The HSS downloads the unique identifiers of the shared iFC sets to the S-CSCF. The S-CSCF uses a locally administered database to map the downloaded identifiers onto the shared iFC sets.
> If the S-CSCF does not support this feature, the HSS will not download identifiers of shared iFC sets.
> New Features and Functionality - Licensed Enhanced Feature Support
> IPv4-IPv6 Interworking
> MSRP is now supported when IPv4-IPv6 interworking is enabled.
> IPv6 Support
> In addition to supporting IPv4, the SCM supports IPv6 addressing. A CSCF service can be configured with v6 addresses to support an all v6 network.
> Important: For this feature, you may bind a CSCF service to either an IPv4 address or to an IPv6 address, but not both simultaneously.
> The following diagram shows the implementation where CSCF supports only IPv4.
> IPv4 Configuration
> With IPv6 support, the configuration supported would look like the following diagram. The DNS server could be either IPv4 or IPv6.
> IPv6 Configuration
> Important: The policy interface to PCRF will be IPv6 based when DIAMETER supports IPv6.
> Supported Standards
> The SCM service now complies with the following standards for CDMA2000 PDSN and UMTS GGSN network wireless data services.
> Release 8 3GPP References
> Important: The SCM currently supports the following Release 8 3GPP specifications. Most 3GPP specifications are also used for 3GPP2 support; any specifications that are unique to 3GPP2 would be listed under Release 8 3GPP2 References.

> • | TS 23.167 IP Multimedia Subsystem (IMS) emergency sessions

> • | TS 24.229 IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3

> • | TS 29.214 Policy and charging control over Rx reference point

> • | TS 33.178 Security aspects of early IP Multimedia Subsystem (IMS)

> • | TS 33.978 Security aspects of early IP Multimedia Subsystem (IMS)

> SGSN Features
> This section in development.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883