> New Feature Summary
> This guide identifies features and functionality added or modified between software releases 9.0 and 10.0. Topics covered in this chapter are:

> l | Related Documents

> l | Common Features in Release 10.0

> l | ASN GW Features in Release 10.0

> l | Content Filtering in Release 10.0

> l | ECS Features in Release 10.0

> l | ESS Features in Release 10.0

> l | Firewall Features in Release 10.0

> l | GGSN Features in Release 10.0

> l | GSS Features in Release 10.0

> l | HA Features in Release 10.0

> l | HNB-GW Features in Release 10.0

> l | HSGW Features in Release 10.0

> l | inPilot Features in Release 10.0

> l | IP Services Gateway Features in Release 10.0

> l | NAT Features in Release 10.0

> l | PDIF Features in Release 10.0

> l | Packet Data Gateway/Tunnel Termination Gateway Features in Release 10.0

> l | PDN Gateway Features in Release 10.0

> l | PDSN Features in Release 10.0

> l | Peer-to-Peer Features in Release 10.0

> l | Session Control Manager Features in Release 10.0

> l | Serving Gateway Features in Release 10.0

> l | Web Element Manager Features in Release 10.0

> Related Documents
> Additional information on these items is located in the documents provided with the 10.0 release, see the table below.

> 10.0 Release Documentation
> Document | Part Number
> Cisco ASR 5000 Series Product Overview Guide | OL-22938-01
> Cisco ASR 5000 Series Packet Data Serving Node Administration Guide | OL-22939-01
> Cisco ASR 5000 Series SNMP MIB Reference | OL-22942-01
> Cisco ASR 5000 Series Gateway GPRS Support Node Administration Guide | OL-22944-01
> Cisco ASR 5000 Series Command Line Interface Reference | OL-22948-01
> Cisco ASR 5000 Series Enhanced Charging Services Administration Guide | OL-22951-01
> Cisco ASR 5000 Series Session Control Manager Administration Guide | OL-22952-01
> Cisco ASR 5000 Series Access Service Network Gateway Administration Guide | OL-22953-01
> Cisco ASR 5000 Series AAA Interface Administration and Reference | OL-23000-01
> Cisco ASR 5000 Series Release 9.0 to Release 10.0 Change Reference | OL-22958-01
> Cisco ASR 5000 Series Content Filtering Services Administration Guide | OL-22959-01
> Cisco ASR 5000 Series Peer-to-Peer Detection Administration Guide | OL-22960-01
> Cisco ASR 5000 Series IP Services Gateway Administration Guide | OL-22961-01
> Cisco ASR 5000 Series Packet Data Interworking Function Administration Guide | OL-22963-01
> Cisco ASR 5000 Series Thresholding Configuration Guide | OL-22967-01
> Cisco ASR 5000 Series System Administration Guide | OL-22970-01
> Cisco ASR 5000 Series Home Agent Administration Guide | OL-22980-01
> Cisco ASR 5000 Series Enhanced Feature Configuration Guide | OL-22983-01
> Cisco ASR 5000 Series Packet Data Network Gateway Administration Guide | OL-22985-01
> Cisco ASR 5000 Series Serving Gateway Administration Guide | OL-22986-01
> Cisco ASR 5000 Series Mobility Management Entity Administration Guide | OL-22987-01
> Cisco ASR 5000 Series Lawful Intercept Configuration Guide | OL-22988-01
> Cisco ASR 5000 Series Statistics and Counters Reference | OL-22991-01
> Cisco ASR 5000 Series Network Address Translation Administration Guide | OL-22992-01
> Cisco ASR 5000 Series Mobility Unified Reporting System Installation and Administration Guide | OL-22993-01
> Cisco ASR 5000 Series Aggregation Services Router Installation and Administration Guide | OL-22996-01
> Cisco ASR 5000 Series Mobility Femto Gateway Administration Guide | OL-22997-01
> Cisco ASR 5000 Series 3G Home NodeB Gateway Administration Guide | OL-22998-01
> Cisco ASR 5000 Series Packet Data Gateway/Tunnel Termination Gateway Administration Guide | OL-22999-01

> Common Features in Release 10.0
> This section provides information on new features that are common to products in Release 10.0.
> 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:

> l | HNB Registration/De-registration Function

> l | UE Registration/De-registration Function for HNB

> l | Iuh User-plane Management Functions

> l | Iuh User plane Transport Bearer Handling

> l | 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.
> For more information on this product, refer HNB Gateway Administration Guide.
> License Keys
> Requires separate product license key.
> Acceptance/Rejection of Messages with Different Origin Host - Behavioral Change
> This Diameter related behavioral change is applicable to all products that use Gx interface.
> In earlier releases, a message received from a different host name was accepted only if the host was configured as a secondary host in the application configuration.
> In this release, messages received with a different origin host are accepted if there is a route entry configured in the diameter endpoint configuration.
> To accept messages from host host_x “route-entry host host_x peer peer_y” must be configured in the Diameter endpoint. The session will be bound to host host_x and all subsequent messages initiated from PCEF will have destination host as host_x.
> BCM Mode Validation against Network Request Supported AVP - Behavioral Change
> This Diameter related behavioral change is applicable to GGSN in StarOS 10.0 releases.
> In earlier releases, the Bearer Control Mode received from PCRF was not validated in the GGSN.
> In this release, if the GGSN broadcasts Network Request Support AVP as NOT supported, and PCRF sends BCM as UE_NW in CCA I, the session will be terminated.
> In case if GGSN broadcasts Network Request Support AVP as NOT supported, PCRF should authorize the BCM as UE_ONLY and not UE_NW.
> CCA Result Code 4011 at MSCC Level - Behavioral Change
> This Diameter related behavioral change is applicable to StarOS 10.0 releases, and is applicable to all customers other than Vodafone.
> In this release, the CCA result-code 4011 (DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE) is allowed at the MSCC level and will cause the particular service identified by the MSCC to go offline and not the subscriber.
> Default Charging Method in CCR-I Messages - Behavioral Change
> This Diameter related behavioral change is applicable to GGSN in StarOS 10.0 releases.
> In StarOS 8.1, the default charging method was not being sent in CCR-I messages for Vf-Gx dictionary (dpca-custom9), Standard R7 Gx dictionary (dpca-custom4), and ATT dictionary (dpca-custom2).
> In this release, the default charging method is sent in CCR-I message. For this, new AVPs Online/Offline will be sent in CCR-I message based on the configuration.
> QoS-Upgrade and QoS Negotiation AVPs in CCR Messages - Behavioral Change
> This Diameter related behavioral change is applicable to GGSN in StarOS 9.0 and later releases.
> In StarOS 8.1, the QoS-Upgrade and QoS Negotiation AVPs were not sent in CCR messages.
> In this release, if UE sets the QoS Upgrade and QoS Negotiation bits in CPC/UPC messages, the values are communicated to PCRF in CCR messages. New AVPs QoS-Upgrade and QoS Negotiation AVPs will be sent in Vf-Gx dictionary (dpca-custom9).
> Unsupported Event Trigger in RAR Message - Behavioral Change
> This Diameter related behavioral change is applicable to all products that use Gx interface in StarOS 10.0 releases.
> In StarOS 9.0, the PCEF on receiving an unsupported EVENT_TRIGGER AVP value in RAR message ignores it and processes the RAR message.
> In this release, when an unsupported EVENT_TRIGGER AVP value is received in RAR message, the RAR message is treated as erroneous and DIAMETER_INVALID_AVP_VALUE is returned, and further information in RAR is ignored.
> ASN GW Features in Release 10.0
> This section provides information for new features in the ASN GW Service in Release 10.0.
> None for this release.
> Content Filtering in Release 10.0
> This section provides information on new features for Release 10.0 in the Content Filtering product.
> CF-APPS Re-architecture
> The Content Filtering architecture is redesigned so that the CF Application components like CDP, CCI and RE are now part of external applications, WEM and inPilot.
> The CDP functionality is handled by WEM, and the RE functionality has been moved to inPilot to support the CF-EDR based reporting. The CF-CCI functionality has been eliminated on account of this redesign.
> For more information, please refer to the WEM Online Help and inPilot Online Help.
> ECS Features in Release 10.0
> This section provides information on new features in the Enhanced Charging Service in Release 10.0.
> Fair Usage
> The Fair Usage feature enables to perform SessMgr instance-level load balancing for in-line service features, and resource usage control for subscribers. For information, refer to the feature description in the Enhanced Charging Service Administration Guide.
> X-Header Encryption
> X-Header Encryption enhances the X-header Insertion feature to increase the number of fields that can be inserted, and also enables encrypting the fields before inserting them. For information, refer to the feature description in the Enhanced Charging Service Administration Guide.
> ICAP Failure Action on Re-transmitted Packets - Behavioral Change
> In this release the failure-action discard behavior to be taken on re-transmitted packets when the ICAP response is not received for the original request and the retransmitted request comes in has changed. Fore more information, please refer to the ICAP Interface Support chapter of the System Enhanced Feature Configuration Guide.
> ESS Features in Release 10.0
> This section contains information on features that pertain to the Local-External Storage Server (L-ESS) and Remote (Long Term)-External Storage Server (R-ESS).
> None for this release.
> Firewall Features in Release 10.0
> This section provides information for new features in the Stateful Firewall product in Release 10.0.
> None for this release.
> GGSN Features in Release 10.0
> This section provides information for new features for the GGSN Service in Release 10.0.
> Common Gateway Access Support
> Benefits
> This is a consolidated solution that combines 3G and 4G access technologies in a common gateway supporting logical services of HA, PGW, and GGSN to allow users to have the same user experience, independent of the access technology available.
> Description
> In today’s scenarios, an operator may have multiple access networks (CDMA, eHRPD and LTE) plus a GSM/UMTS solution for international roaming. Therefore, the operator needs a solution to allow customers to access services with the same IP addressing behavior and to use a common set of egress interfaces, regardless of the access technology (3G or 4G).
> This solution allows static customers to access their network services with the same IP addressing space assigned for wireless data, regardless of the type of connection (CDMA, eHRPD/LTE or GSM/UMTS). Subscribers using static IP addressing will be able to get the same IP address regardless of the access technology.
> Following commands added to GGSN Service Configuration Mode for this support:
> To enable system to accept duplicate call session with same IP address:
> [default] newcall duplicate-subscriber-requested-address {accept | reject}
> To enable system to allow authorization with 3GPP AAA/HSS over S6b interface:
> [default] authorize-with-hss
> To enable system to provide DNS query support for P-CSCF, if received from 3GPP AAA/HSS in AAA message:
> dns-client context dns_ctxt_name
> default dns-client context
> To configure the FQDN for HSS address resolution:
> [no | default] fqdn host host_name realm realm_id
> For more information on this product, refer Common Gateway Access Support section in GGSN Service Administration Guide.
> License Keys
> Requires separate product license key.
> GSS Features in Release 10.0
> This section provides information for new GSS features for Release 10.0
> None for this release.
> HA Features in Release 10.0
> This section provides information for new features in the Home Agent product in Release 10.0.
> None for this release.
> HNB-GW Features in Release 10.0
> This section provides information for new features in the Home-NodeB Gateway product in Release 10.0.
> HNB-GW feature is new in Release 10.0.
> No new feature is added for this release.
> HSGW Features in Release 10.0
> This section contains information on new 10.0 features that pertain to the HRPD Serving Gateway (HSGW) supporting eHRPD network services.
> No new feature is added for this release.
> inPilot Features in Release 10.0
> This section provides information on new features in the current inPilot Release 10.0.x, which supports StarOS 9.0.
> Content Filtering Reports
> The Content Filtering Reporting Engine (CF-RE) reports provide the summary of traffic over Content Filtering categories, actions, and ratings.
> The CF-RE report also provides the list of top N subscribers and URLs based on their unique subscriber’s hit count and total usage.
> Distributed Architecture of inPilot
> inPilot supports the distributed model to allow the deployment which enables network wide view or work load balancing. Newly introduced component, Remote Data Processor (RDP), plays the role of pre-processing the input files from gateways. One or more RDPs, installed separately on remote machines can be registered to a master inPilot and one RDP can process files from one or more gateways.
> RDP periodically sends the intermediate data to registered master inPilot. The role of inPilot in such deployments is mostly for report generation, report viewing, RDP management and optionally data processing.
> IMPORTANT: For Bulkstat, there is no support for distributed model and all the bulkstat input files will be parsed by master inPilot only.
> Support for E-mailing Reports
> In this release, the inPilot application allows users to configure e-mail IDs and SMTP servers to send generated reports.
> For more information please refer to inPilot Installation and Administration Guide and inPilot Online Help.
> Weekly and Monthly Reports
> In this release, inPilot supports generating weekly and monthly reports. The weekly reports provide details of the following:

> l | Total traffic

> l | Total traffic by category

> l | VOIP Call Duration

> l | Total unclassified traffic (TCP and UDP)

> l | Top N subscribers

> The monthly reports provide the details of total traffic across the top N protocols / application categories in a month.
> Password Security and Access Control Feature
> The current release of inPilot allows only authenticated users to access the inPilot application. The user name and password of the inPilot user should comply to the minimum complexity requirements.
> This ensures data privacy and security for inPilot at Operating System level. It also aids in preventing unauthorized access of database by end-users. Users with only certain privileges are allowed to access inPilot directories and view various reports through GUI.
> DPI Report Filtering
> The users can select one or more filters based on which these reports are displayed. In the current release, the following filters are supported.

> l | Category

> l | Protocol

> l | IP Protocol

> l | Radio Access Type (RAT)

> l | Type Allocation Code (TAC)

> l | Access Point Name (APN)

> l | Serving GPRS Support Node (SGSN)

> If a single filter is selected then the graphs appear with a comparison against two groups, filter and non-filters. Also, the table displays values for filter and non-filter. If multiple filters are selected, for example, if APN and RAT filters are selected, then traffic distribution will be calculated per (selected) APN with respect to the selected RAT.
> Anonymize Subscriber Data
> inPilot GUI and excel report displays subscriber's private data like Mobile Station Integrated Services Digital Network (MSISDN) in encrypted format in all the subscriber-based reporting.
> Users with administrative privilege can only decrypt the MSISDNs using a shell script utility. For information on how to use this script, see the inPilot Installation and Administration Guide.
> This feature is available only with the fresh installation.
> Support for Unknown URLs
> For CF reporting, inPilot should parse CF-EDRs and generate the unknown/unratedURL database. This database will be pulled periodically by WEM and subsequently deliver to Rulespace. The unknown URL files can either be time based or URL count based.
> IP Services Gateway Features in Release 10.0
> This section provides information for new features in the IP Services Gateway product.
> None for this release.
> NAT Features in Release 10.0
> This section contains information for new features in the Network Address Translation (NAT) product in Release 10.0.
> NAT ALG Support
> This release supports NAT Application Level Gateways (ALGs) for the following protocol:

> l | Point-to-Point Tunneling Protocol (PPTP)

> l | Session Initiation Protocol (SIP)

> l | Trivial File Transfer Protocol (TFTP)

> For more information, please refer to the Network Address Translation Administration Guide.
> NAT IP Pool Group Support
> This release supports grouping of NAT IP pools.
> Similar NAT pools can be grouped into NAT IP pool groups. This enables to bind dis contiguous IP address blocks in individual NAT IP pools to a single NAT pool group.
> When configuring a NAT pool group, note that only those NAT pools that have similar characteristics can be grouped together. The similarity is determined by the NAT Pool Type (One-to-One / Many-to-One), users configured per NAT IP address (applicable only to Many-to-one NAT pools), NAT IP Address Allocation Mode (On-demand/Not-on-demand), and Port Chunk Size (applicable only to Many-to-one NAT pools) parameters.
> IMPORTANT: Dissimilar NAT pools cannot be grouped together.
> It is recommended that for each NAT pool in a NAT pool group the other parameters also be configured with the same values, so that the NAT behavior is predictable across all NAT pools in that NAT pool group.
> The NAT pool from which a NAT IP address is assigned will determine the actual values to use for all parameters.
> It is recommended that in a Firewall-and-NAT policy all the realms configured either be NAT pools or NAT pool groups. If both NAT pool(s) and NAT pool group(s) are configured, ensure that none of the NAT pool(s) are also included in the NAT pool group.
> For more information, please refer to the Network Address Translation Administration Guide.
> PDIF Features in Release 10.0
> This section provides information for new features in the Packet Data Interworking Function.
> Session Counting License
> In Release 10.0, the PDIF is a licensed product with a session counting license, which can be purchased in 1,000 or 10,000 session increments. For information about PDIF licenses, contact your sales representative.
> PSC2 Support
> In Release 10.0, the PDIF supports the Packet Services Card 2 (PSC2). The PSC2 is the next-generation packet forwarding card for the ASR 5000. The PSC2 provides increased aggregate throughput and performance, and a higher number of subscriber sessions.
> Multiple PDIF Services
> In Release 10.0, the PDIF supports multiple PDIF services running simultaneously on the same ASR 5000. This feature enables operators to configure PDIF services with different crypto templates to support multiple subscriber handsets and to set per-service maximum session limits. The total number of sessions for all PDIF services running simultaneously on the same ASR 5000 must fall under the PDIF session counting license limit.
> Packet Data Gateway/Tunnel Termination Gateway Features in Release 10.0
> This section provides information for new features in the Packet Data Gateway/Tunnel Termination Gateway (PDG/TTG) Features in Release 10.0.
> Lawful Intercept
> In Release 10.0, the PDG/TTG supports lawful interception (LI) of subscriber session information to provide telecommunication service providers (TSPs) with a mechanism to assist law enforcement agencies (LEAs) in the monitoring of suspicious individuals (referred to as targets) for potential criminal activity.
> IMS Emergency Call Handling
> In Release 10.0, the PDG/TTG supports IMS emergency call handling per 3GPP TS 33.234. This feature is enabled by configuring a special WLAN access point name (W-APN), which includes a W-APN network identifier for emergency calls (sos, for example), and can be configured with no authentication.
> The DNSs in the network are configured to resolve the special W-APN to the IP address of the PDG/TTG. When a WLAN UE initiates an IMS emergency call, the UE sends a W-APN that includes the same W-APN network identifier (sos) as the one that is configured on the PDG/TTG. This W-APN network identifier is prefixed to the W-APN operator identifier per 3GPP TS 23.003. The W-APN operator identifier sent by the UE must match the PLMN ID (MCC and MNC) that is configured on the PDG/TTG (visited network). When the PDG/TTG receives the W-APN from the UE in the IDr, the PDG/TTG marks the call as an emergency call and proceeds with call establishment, even in the event of an authentication or EAP failure from the AAA/EAP server.
> If the PDG/TTG detects that an old IKE SA for the special W-APN already exists, it deletes the IKE SA and sends an INFORMATIONAL message with a Delete payload to the WLAN UE to delete the old IKE SA on the UE.
> IPSec Session Recovery Support
> In Release 10.0, the session recovery feature is a licensed feature. It provides seamless failover and nearly instantaneous reconstruction of subscriber session information in the event of a hardware or software fault within the same chassis, preventing a fully-connected user session from being dropped. For information about the required software license for this feature, contact your sales representative.
> Session recovery is performed by mirroring key software processes (the IPSec manager, session manager, and AAA manager, for example) on the PDG/TTG. These mirrored processes remain in an idle state (in standby mode), where they perform no processing until they may be needed in the case of a software failure (a session manager task aborts, for example). The system spawns new instances of standby mode sessions and AAA managers for each active control processor being used.
> PDN Gateway Features in Release 10.0
> This section contains information on new 10.0 features that pertain to the eGTP PDN Gateway (P-GW) supporting LTE network services.
> Gy Support
> The Gy interface provides a standardized Diameter interface for real time content based charging of data services. It is based on the 3GPP standards and relies on quota allocation. It is the connection between the P-GW and an On-line Charging Server.
> The following Online Charging models and functions are supported:

> l | Time based charging

> l | Volume based charging

> l | Volume and time based charging

> l | Final Unit Indication and termination or redirection of service data flows when quota is consumed

> l | Reauthorization triggers to rearm quotas for one or more rating groups using multi-service credit control (MSCC) instances

> l | Event based charging

> l | Billing cycle bandwidth rate limiting

> l | Fair usage controls

> Lawful Intercept Support
> In accordance with 3GPP TS 33.108 Release 8 requirements, the Cisco P-GW supports the Lawful Intercept Access Function for intercepting control and data messages of mobile targets.
> The Cisco P-GW provides access to the intercepted Content of Communications (CC) and the Intercept Related Information (IRI) of the mobile target and services related to the target on behalf of Law Enforcement Agencies. In this release the P-GW supports the following three interfaces:

> l | X1 provisioning interface from Administrative Function (ADMF) using CLI over SSH

> l | X2 event delivery interface for transferring Intercept Related Information (IRI) to a Delivery Function/Mediation server

> l | X3 content delivery

> VLAN Tagging Support
> P-GW now supports Virtual LANs (VLANs) which provide greater flexibility in the configuration and use of contexts and services.
> VLANs are configured as “tags” on a per-port basis and allow more complex configurations to be implemented. The VLAN tag allows a single physical port to be bound to multiple logical interfaces that can be configured in different contexts. Therefore, each Ethernet port can be viewed as containing many logical ports when VLAN tags are employed.
> For more information on VLAN support, refer to the VLANs chapter in the System Enhanced Feature Configuration Guide.
> IPv6 Support on S5/S8 Interface
> The eGTP P-GW now supports IPv6 transport for tunneling and management on the S5/S8 interface to/from the Serving Gateway.
> IPv6 Pool Support in P-GW Pool Groups
> The P-GW now supports:

> l | Assignment of IPv6 prefix by using pool group in APN configuration

> l | Even distribution of IPv6 prefix assignments from multiple IPv6 prefix pools which fall under the same pool group

> l | Assignment of IPv6 prefix pools and IPv4 addresses from multiple pools which share the same pool group name

> PDSN Features in Release 10.0
> This section provides information for new features in the Packet Data Serving Node in Release 10.0.
> None for this release.
> Peer-to-Peer Features in Release 10.0
> This section provides information for new features for Release 10.0 in the in-line Peer-to-Peer support.
> P2P Voice Call Duration
> The P2P product has the capability to detect network traffic created by P2P VoIP clients such as Skype, Yahoo, MSN, Gtalk, Oscar. The VoIP call duration is a direct indication to the revenue impact of the network operator. The P2P product is well poised to process the network traffic online to detect and control the VoIP presence, and generate records that can be used to calculate the VoIP call durations.
> For more information, please refer to the Peer-to-Peer Overview chapter in the Peer-to-Peer Detection Administration Guide.
> Random Drop Charging Action
> The random drop charging action is added as an option to degrade P2P voice calls. This is achieved by randomly dropping packets of the voice calls over the voice call period. Voice data is encoded in multiple packets by the codec. Since there is a possibility of packets being dropped in a network, the codec replicates the same information across multiple packets. This provides resilience to random packet drops in the network. For a considerable degradable voice quality, a chunk of packets need to be dropped. By this way, the codec will be unable to decode the required voice information. The chunk size for achieving degradation of voice call varies from one protocol to another.
> For more information, please refer to the Peer-to-Peer Overview chapter in the Peer-to-Peer Detection Administration Guide.
> New Protocols
> The P2P solution now detects the following new protocols:

> l | ActiveSync

> l | Aimini

> l | Battlefield

> l | Freenet

> l | IAX

> l | IPTV

> l | Nimbuzz

> l | OpenFT

> l | Paltalk

> l | Pandora

> l | QQgame

> l | Quake

> l | RDP

> l | SecondLife

> l | Warcraft3

> For more information, please refer to the Peer-to-Peer Detection Administration Guide.
> Session Control Manager Features in Release 10.0
> 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 section of the Product Overview, 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:

> l | 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
> 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.
> With IPv6 support, the configuration supported would look like the following diagram. The DNS server could be either IPv4 or IPv6.
> 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.

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

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

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

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

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

> Serving Gateway Features in Release 10.0
> This section contains information on new 10.0 features that pertain to the eGTP Serving Gateway (S-GW) supporting LTE network services.
> Session Recovery Support
> The S-GW now 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.
> IPv6 Support for S5/S8 Interface
> The eGTP S-GW now supports IPv6 transport for tunneling and management on the S5/S8 interface to/from the PDN Gateway.
> IPv6 Support for S11 and S1-U Interfaces
> The eGTP S-GW now supports IPv6 transport for tunneling and management on the S11 and S1-U interfaces to/from the MME and eNodeB respectively.
> Web Element Manager Features in Release 10.0
> This section provides information for new features for the Web Element Manager application in Release 10.0.
> None for this release.

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