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.
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.
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.
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.
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.
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, 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).
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.
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.
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 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.
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.
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.
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.
[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.
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.
For more information please refer to inPilot Installation and Administration Guide and
inPilot Online Help.
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.
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.
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.
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.
For more information, please refer to the Network Address Translation Administration Guide.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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:
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.
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.
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.
For more information, please refer to the Peer-to-Peer Detection Administration Guide.
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.
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.
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.
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).
|
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.
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.