> PDN Gateway Overview
> The Cisco® ASR 5x00 provides wireless carriers with a flexible solution that functions as Packet Data Network (PDN) Gateway (P-GW) in 3GPP2 Long Term Evolution-System Architecture Evolution (LTE-SAE) and evolved High Rate Packet Data (eHRPD) wireless data networks.
> This overview provides general information about the P-GW including:

> • | Product Description

> • | Network Deployment(s)

> • | Features and Functionality - Base Software

> • | Features and Functionality - Inline Service Support

> • | Features and Functionality - External Application Support

> • | Features and Functionality - Optional Enhanced Feature Software

> • | How the PDN Gateway Works

> • | Supported Standards

> Product Description
> The P-GW is the node that terminates the SGi interface towards the PDN. If a UE is accessing multiple PDNs, there may be more than one P-GW for that UE. The P-GW provides connectivity to the UE to external packet data networks by being the point of exit and entry of traffic for the UE. A UE may have simultaneous connectivity with more than one P-GW for accessing multiple PDNs. The P-GW performs policy enforcement, packet filtering for each user, charging support, lawful interception and packet screening.
> P-GW in the Basic E-UTRAN/EPC Network
> P-GW in the Basic E-UTRAN/EPC and eHRPD Network
> Another key role of the P-GW is to act as the anchor for mobility between 3GPP and non-3GPP technologies such as WiMAX and 3GPP2 (CDMA 1X and EvDO).
> P-GW functions include:

> • | Mobility anchor for mobility between 3GPP access systems and non-3GPP access systems. This is sometimes referred to as the SAE Anchor function.

> • | Policy enforcement (gating and rate enforcement)

> • | Per-user based packet filtering (deep packet inspection)

> • | Charging support

> • | Lawful Interception

> • | UE IP address allocation

> • | Packet screening

> • | Transport level packet marking in the downlink;

> • | Down link rate enforcement based on Aggregate Maximum Bit Rate (AMBR)

> The following are additional P-GW functions when supporting non-3GPP access (eHRPD):

> • | P-GW includes the function of a Local Mobility Anchor (LMA) according to draft-ietf-netlmm-proxymip6, if PMIP-based S5 or S8 is used.

> • | The P-GW includes the function of a DSMIPv6 Home Agent, as described in draft-ietf-mip6-nemo-v4traversal, if S2c is used.

> Platform Requirements
> The P-GW service runs on a Cisco® ASR 5x00 chassis running StarOS. The chassis can be configured with a variety of components to meet specific network deployment requirements. For additional information, refer to the Installation Guide for the chassis and/or contact your Cisco account representative.
> Licenses
> The P-GW is a licensed Cisco product. Separate session and feature licenses may be required. Contact your Cisco account representative for detailed information on specific licensing requirements. For information on installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations chapter in the System Administration Guide.
> Network Deployment(s)
> This section describes the supported interfaces and the deployment scenarios of a PDN Gateway.
> PDN Gateway in the E-UTRAN/EPC Network
> The following figure displays the specific network interfaces supported by the P-GW. Refer to Supported Logical Network Interfaces (Reference Points) for detailed information about each interface.
> Supported P-GW Interfaces in the E-UTRAN/EPC Network
> The following figure displays a sample network deployment of a P-GW, including all of the interface connections with other 3GPP Evolved-UTRAN/Evolved Packet Core network devices.
> P-GW in the E-UTRAN/EPC Network
> Supported Logical Network Interfaces (Reference Points)
> The P-GW provides the following logical network interfaces in support of E-UTRAN/EPC network:
> S5/S8 Interface
> This reference point provides tunneling and management between the S-GW and the P-GW, as defined in 3GPP TS 23.401 and TS 23.402. The S8 interface is an inter-PLMN reference point between the S-GW and the P-GW used during roaming scenarios. The S5 interface is used between an S-GW and P-GW located within the same administrative domain (non-roaming). It is used for S-GW relocation due to UE mobility and if the S-GW needs to connect to a non-collocated P-GW for the required PDN connectivity.
> Supported protocols

> • | Transport Layer: UDP, TCP

> • | Tunneling:

> • | GTP: GTPv2-C (signaling channel), GTPv1-U (bearer channel)

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> S6b Interface
> This reference point, between a P-GW and a 3GPP AAA server/proxy, is used for mobility-related authentication. It may also be used to retrieve and request parameters related to mobility and to retrieve static QoS profiles for UEs (for non-3GPP access) in the event that dynamic PCC is not supported.
> From Release 12.2 onwards, the S6b interface has been enhanced to pass on the UE assigned IPv6 address (IPv6 prefix and IPv6 interface ID) to the AAA server. S6b interface also has support for Framed-IPv6-Pool, Framed IP Pool, and served party IP address AVPs based IP allocation. With this support, based on the Pool name and APN name received from AAA server, the selection of a particular IP pool from the configuration is made for assigning the IP address.
> The S6b interface on the P-GW or GGSN can be manually disabled to stop all message traffic to the 3GPP AAA during overload conditions. When the interface is disabled, the system uses locally configured APN-specific parameters including: Framed-Pool, Framed-IPv6-Pool, Idle-Timeout, Charging-Gateway-Function-Host, Server-Name (P-CSCF FQDN). This manual method is used when the HSS/3GPP AAA is in overload condition to allow the application to recover and mitigate the impact to subscribers
> Release 12.3 onwards, the IPv6 address reporting through Authorization-Authentication-Request (AAR) towards the S6b interface is no longer a default feature. It is now configurable through the CLI.
> Another enhancement on S6b interface support is the new S6b retry-and-continue functionality that creates an automatic trigger in the GGSN and P-GW to use the locally configured APN profile upon receipt of any uniquely defined Diameter error code on the S6b interface for an Authorization-Authentication-Request (AA-R) only. This procedure would be utilized in cases where a protocol, transient, or permanent error code is returned from the both the primary and secondary AAA to the GGSN or P-GW. In case of retry-and-continue functionality, P-GW should query from DNS server if it is configured in APN. S6b failure handling continues the data call. This behavior is only applicable to the aaa-custom15 Diameter dictionary.
> Important: The S6b interface can be disabled via the CLI in the event of a long-term AAA outage.
> Supported protocols:

> • | Transport Layer: TCP, SCTP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> SGi Interface
> This reference point provides connectivity between the P-GW and a packet data network (3GPP TS 23.401). This interface can provide access to a variety of network types including an external public or private PDN and/or an internal IMS service provisioning network.
> Supported protocols:

> • | Transport Layer: TCP, UDP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> Gx Interface
> This signalling interface supports the transfer of policy control and charging rules information (QoS) between the Policy and Charging Enforcement Function (PCEF) on the P-GW and a Policy and Charging Rules Function (PCRF) server (3GPP TS 23.401).
> Supported protocols:

> • | Transport Layer: TCP, SCTP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> For more information on the Gx interface, refer to Dynamic Policy Charging Control (Gx Reference Interface) in the Features and Functionality - Base Software section of this chapter.
> Gy Interface
> The Gy reference interface enables online accounting functions on the P-GW in accordance with 3GPP Release 8 and Release 9 specifications.
> Supported protocols:

> • | Transport Layer: TCP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> For more information on the Gy interface and online accounting, refer to Gy Interface Support in the Features and Functionality - Base Software section of this chapter.
> Gz Interface
> The Gz reference interface enables offline accounting functions on the P-GW. The P-GW collects charging information for each mobile subscriber UE pertaining to the radio network usage.
> Supported protocols:

> • | Transport Layer: TCP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> Gn/Gp Interface
> This reference point provides tunneling and management between the P-GW and the SGSN during handovers between the EPS and 3GPP 2G and/or 3G networks (3GPP TS 29.060). For more information on the Gn/Gp interface, refer to Gn/Gp Handoff Support in the Features and Functionality - Base Software section of this chapter.
> Supported protocols

> • | Transport Layer: UDP, TCP

> • | Tunneling: GTP: GTP-C (signaling channel)

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> Rf Interface
> The Rf interface enables offline accounting functions on the P-GW in accordance with 3GPP Release 8 and Release 9 specifications. The P-GW collects charging information for each mobile subscriber UE pertaining to the radio network usage.
> Supported protocols:

> • | Transport Layer: TCP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> PDN Gateway Supporting eHRPD to E-UTRAN/EPC Connectivity
> The following figure displays the specific network interfaces supported by the P-GW in an eHRPD network. Refer to Supported Logical Network Interfaces (Reference Points) for detailed information about each interface.
> P-GW Interfaces Supporting eHRPD to E-UTRAN/EPC Connectivity
> The following figure displays a sample network deployment of a P-GW in an eHRPD Network, including all of the interface connections with other 3GPP Evolved-UTRAN/Evolved Packet Core network devices.
> P-GW in the E-UTRAN/EPC Network Supporting the eHRPD Network
> Supported Logical Network Interfaces (Reference Points)
> The P-GW provides the following logical network interfaces in support of eHRPD to E-UTRAN/EPC connectivity:
> S5/S8 Interface
> This reference point provides tunneling and management between the S-GW and the P-GW, as defined in 3GPP TS 23.401. The S8 interface is an inter-PLMN reference point between the S-GW and the P-GW used during roaming scenarios. The S5 interface is used between an S-GW and P-GW located within the same administrative domain (non-roaming). It is used for S-GW relocation due to UE mobility and if the S-GW needs to connect to a non-collocated P-GW for the required PDN connectivity.
> Supported protocols:

> • | Transport Layer: UDP, TCP

> • | Tunneling:

> • | GTP: IPv4 or IPv6 GTP-C (signaling channel) and GTP-U (bearer channel)

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> S2a Interface
> This reference point supports the bearer interface by providing signaling and mobility support between a trusted non-3GPP access point (HSGW) and the PDN Gateway. It is based on Proxy Mobile IP but also supports Client Mobile IPv4 FA mode which allows connectivity to trusted non-3GPP IP access points that do not support PMIP.
> Supported protocols:

> • | Transport Layer: UDP, TCP

> • | Tunneling: GRE IPv6

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> S6b Interface
> This reference point, between a P-GW and a 3GPP AAA server/proxy, is used for mobility-related authentication. It may also be used to retrieve and request parameters related to mobility and to retrieve static QoS profiles for UEs (for non-3GPP access) in the event that dynamic PCC is not supported.
> From Release 12.2 onwards, the S6b interface has been enhanced to pass on the UE assigned IPv6 address (IPv6 prefix and IPv6 interface ID) to the AAA server. S6b interface also has support for Framed-IPv6-Pool, Framed IP Pool, and served party IP address AVPs based IP allocation. With this support, based on the Pool name and APN name received from AAA server, the selection of a particular IP pool from the configuration is made for assigning the IP address.
> The S6b interface on the P-GW or GGSN can be manually disabled to stop all message traffic to the 3GPP AAA during overload conditions. When the interface is disabled, the system uses locally configured APN-specific parameters including: Framed-Pool, Framed-IPv6-Pool, Idle-Timeout, Charging-Gateway-Function-Host, Server-Name (P-CSCF FQDN). This manual method is used when the HSS/3GPP AAA is in overload condition to allow the application to recover and mitigate the impact to subscribers
> Release 12.3 onwards, the IPv6 address reporting through Authorization-Authentication-Request (AAR) towards the S6b interface is no longer a default feature. It is now configurable through the CLI.
> Another enhancement on S6b interface support is the new S6b retry-and-continue functionality that creates an automatic trigger in the GGSN and P-GW to use the locally configured APN profile upon receipt of any uniquely defined Diameter error code on the S6b interface for an Authorization-Authentication-Request (AA-R) only. This procedure would be utilized in cases where a protocol, transient, or permanent error code is returned from the both the primary and secondary AAA to the GGSN or P-GW. In case of retry-and-continue functionality, P-GW should query from DNS server if it is configured in APN. S6b failure handling continues the data call. This behavior is only applicable to the aaa-custom15 Diameter dictionary.
> Important: The S6b interface can be disabled via the CLI in the event of a long-term AAA outage.
> Supported protocols:

> • | Transport Layer: TCP, SCTP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> SGi Interface
> This reference point provides connectivity between the P-GW and a packet data network. This interface can provide access to a variety of network types including an external public or private PDN and/or an internal IMS service provisioning network.
> Supported protocols:

> • | Transport Layer: TCP, UDP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> Gx Interface
> This signalling interface supports the transfer of policy control and charging rules information (QoS) between the Policy and Charging Enforcement Function (PCEF) on the P-GW and a Policy and Charging Rules Function (PCRF) server (3GPP TS 23.401).
> Supported protocols:

> • | Transport Layer: TCP, SCTP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> For more information on the Gx interface, refer to Dynamic Policy Charging Control (Gx Reference Interface) in the Features and Functionality - Base Software section of this chapter.
> Rf Interface
> The Rf reference interface enables offline accounting functions on the P-GW in accordance with 3GPP Release 8 and Release 9 specifications. The P-GW collects charging information for each mobile subscriber UE pertaining to the radio network usage.
> Supported protocols:

> • | Transport Layer: TCP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> For more information on Rf accounting, refer to the section in the Features and Functionality - Base Software section of this chapter.
> Gy Interface
> The Gy reference interface enables online accounting functions on the P-GW in accordance with 3GPP Release 8 and Release 9 specifications.
> Supported protocols:

> • | Transport Layer: TCP

> • | Network Layer: IPv4, IPv6

> • | Data Link Layer: ARP

> • | Physical Layer: Ethernet

> For more information on the Gy interface and online accounting, refer to Gy Interface Support in the Features and Functionality - Base Software section of this chapter.
> Features and Functionality - Base Software
> This section describes the features and functions supported by default in the base software for the P-GW service and do not require any additional licenses to implement the functionality.
> This section describes the following features:

> • | 3GPP R9 Volume Charging Over Gx

> • | AAA Server Groups

> • | ANSI T1.276 Compliance

> • | APN Support

> • | Assume Positive for Gy-based Quota Tracking

> • | Bulk Statistics Support

> • | Congestion Control

> • | Default and Dedicated EPC Bearers

> • | DHCP Support

> • | Direct Tunnel Support

> • | Domain Based Flow Definitions

> • | DSCP Marking

> • | Dynamic Policy Charging Control (Gx Reference Interface)

> • | Enhanced Charging Service (ECS)

> • | GnGp Handoff Support

> • | IMS Emergency Bearer Handling

> • | IP Access Control Lists

> • | IP Address Hold Timers

> • | IPv6 Capabilities

> • | Local Break-Out

> • | Management System Overview

> • | Mobile IP Registration Revocation

> • | Non-Optimized e-HRPD to Native LTE (E-UTRAN) Mobility Handover

> • | Multiple PDN Support

> • | Online/Offline Charging

> • | Proxy Mobile IPv6 (S2a)

> • | QoS Bearer Management

> • | RADIUS Support

> • | Source IP Address Validation

> • | Subscriber Level Trace

> • | Threshold Crossing Alerts (TCA) Support

> • | UE Time Zone Reporting

> • | Virtual APN Support

> Important: To configure the basic service and functionality on the system for the P-GW service, refer to the configuration examples provided in this guide.
> 3GPP R9 Volume Charging Over Gx
> Also known as accumulated usage tracking over Gx, this 3GPP R9 enhancement provides a subset of the volume and charging control functions defined in TS 29.212 based on usage quotas between a P-GW and PCRF. The quotas can be assigned to the default bearer or any of the dedicated bearers for the PDN connection.
> This feature enables volume reporting over Gx, which entails usage monitoring and reporting of the accumulated usage of network resources on an IP-CAN session or service data flow basis. PCRF subscribes to the usage monitoring at session level or at flow level by providing the necessary information to PCEF. PCEF in turn reports the usage to the PCRF when the conditions are met. Based on the total network usage in real-time, the PCRF will have the information to enforce dynamic policy decisions.
> When usage monitoring is enabled, the PCEF can monitor the usage volume for the IP-CAN session, or applicable service data flows, and report accumulated usage to the PCRF based on any of the following conditions:

> • | When a usage threshold is reached,

> • | When all PCC rules for which usage monitoring is enabled for a particular usage monitoring key are removed or deactivated,

> • | When usage monitoring is explicitly disabled by the PCRF,

> • | When an IP CAN session is terminated or,

> • | When requested by the PCRF.

> Accumulated volume reporting can be measured by total volume, the uplink volume, or the downlink volume as requested by the PCRF. When receiving the reported usage from the PCEF, the PCRF deducts the value of the usage report from the total allowed usage for that IP-CAN session, usage monitoring key, or both as applicable.
> AAA Server Groups
> Value-added feature to enable VPN service provisioning for enterprise or MVNO customers. Enables each corporate customer to maintain its own AAA servers with its own unique configurable parameters and custom dictionaries.
> This feature provides support for up to 800 AAA server groups and 800 NAS IP addresses that can be provisioned within a single context or across the entire chassis. A total of 128 servers can be assigned to an individual server group. Up to 1,600 accounting, authentication and/or mediation servers are supported per chassis.
> 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. periodic forced password changes

> These measures are applicable to the ASR 5x00 and the Web Element Manager since both require password authentication. A subset of these guidelines where applicable to each platform will be implemented. A known subset of guidelines, such as certificate authentication, are not applicable to either product. Furthermore, the platforms support a variety of authentication methods such as RADIUS and SSH which are dependent on external elements. ANSI T1.276 compliance in such cases will be the domain of the external element. ANSI T1.276 guidelines will only be implemented for locally configured operators.
> APN Support
> The P-GW's Access Point Name (APN) support offers several benefits:

> • | Extensive parameter configuration flexibility for the APN.

> • | Creation of subscriber tiers for individual subscribers or sets of subscribers within the APN.

> • | Virtual APNs to allow differentiated services within a single APN.

> Up to 1024 APNs can be configured in the P-GW. An APN may be configured for any type of PDP context, i.e., PPP, IPv4, IPv6 or both IPv4 and IPv6. Many dozens of parameters may be configured independently for each APN.
> Here are a few highlights of what may be configured:

> • | Accounting: RADIUS, GTPP or none. Server group to use. Charging characteristics. Interface with mediation servers.

> • | Authentication: Protocol, such as, CHAP or PAP or none. Default username/password. Server group to use. Limit for number of PDP contexts.

> • | Enhanced Charging: Name of rulebase to use, which holds the enhanced charging configuration (e.g., eG-CDR variations, charging rules, prepaid/postpaid options, etc.).

> • | IP: Method for IP address allocation (e.g., local allocation by P-GW, Mobile IP, DHCP, etc.). IP address ranges, with or without overlapping ranges across APNs.

> • | Tunneling: PPP may be tunneled with L2TP. IPv4 may be tunneled with GRE, IP-in-IP or L2TP. Load-balancing across multiple tunnels. IPv6 is tunneled in IPv4. Additional tunneling techniques, such as, IPsec and VLAN tagging may be selected by the APN, but are configured in the P-GW independently from the APN.

> • | QoS: IPv4 header ToS handling. Traffic rate limits for different 3GPP traffic classes. Mapping of R98 QoS attributes to work around particular handset defections. Dynamic QoS renegotiation (described elsewhere).

> After an APN is determined by the P-GW, the subscriber may be authenticated/authorized with an AAA server. The P-GW allows the AAA server to return VSAs (Vendor Specific Attributes) that override any/all of the APN configuration. This allows different subscriber tier profiles to be configured in the AAA server, and passed to the P-GW during subscriber authentication/authorization.
> Important: For more information on APN configuration, refer to the PDN Gateway Configuration chapter this guide.
> Assume Positive for Gy-based Quota Tracking
> In the current implementation, the PCEF uses a Diameter based Gy interface to interact with the OCS and obtain quota for each subscriber's data session. Now, the PCEF can retry the OCS after a configured amount of quota has been utilized or after a configured amount of time. The quota value would be part of the dcca-service configuration, and would apply to all subscribers using this dcca-service. The temporary quota will be specified in volume (MB)and/or time (minutes) to allow for enforcement of both quota tracking mechanisms, individually or simultaneously.
> When a user consumes the interim total quota or time configured for use during failure handling scenarios, the PCEF shall retry the OCS server to determine if functionality has been restored. In the event that services have been restored, quota assignment and tracking will proceed as per standard usage reporting procedures. Data used during the outage will be reported to the OCS. In the event that the OCS services have not been restored, the PCEF should reallocate with the configured amount of quota and time assigned to the user. The PCEF should report all accumulated used data back to OCS when OCS is back online. If multiple retries and interim allocations occur, the PCEF shall report quota used during all allocation intervals.
> When the Gy interface is unavailable, the P-GW shall enter “assume positive” mode. Unique treatment is provided to each subscriber type. Each functional application shall be assigned unique temporary quota volume amounts and time periods based on a command-level AVP from the PCRF on the Gx interface. In addition, a configurable option has been added to disable assume positive functionality for a subscriber group identified by a command-level AVP sent on the Gx interface by the PCRF.
> Bulk Statistics Support
> The system's support for bulk statistics allows operators to choose to view not only statistics that are of importance to them, but also to configure the format in which it is presented. This simplifies the post-processing of statistical data since it can be formatted to be parsed by external, back-end processors.
> When used in conjunction with the Web Element Manager, the data can be parsed, archived, and graphed.
> The system can be configured to collect bulk statistics (performance data) and send them to a collection server (called a receiver). Bulk statistics are statistics that are collected in a group. The individual statistics are grouped by schema. Following is a list of supported schemas for P-GW:

> • | APN: Provides Access Point Name statistics

> • | Card: Provides card-level statistics

> • | Context: Provides context service statistics

> • | Diameter-acct: Provides Diameter Accounting statistics

> • | Diameter-auth: Provides Diameter Authentication statistics

> • | ECS: Provides Enhanced Charging Service statistics

> • | EGTPC: Provides Evolved GPRS Tunneling Protocol - Control message statistics

> • | FA: Provides FA service statistics

> • | GTPC: Provides GPRS Tunneling Protocol - Control message statistics

> • | GTPP: Provides GPRS Tunneling Protocol - Prime message statistics

> • | GTPU: Provides GPRS Tunneling Protocol - User message statistics

> • | HA: Provides HA service statistics

> • | IMSA: Provides IMS Authorization service statistics

> • | IP Pool: Provides IP pool statistics

> • | LMA: Provides Local Mobility Anchor service statistics

> • | P-GW: Provides P-GW node-level service statistics

> • | Port: Provides port-level statistics

> • | PPP: Provides Point-to-Point Protocol statistics

> • | RADIUS: Provides per-RADIUS server statistics

> • | System: Provides system-level statistics

> The system supports the configuration of up to 4 sets (primary/secondary) of receivers. Each set can be configured with to collect specific sets of statistics from the various schemas. Statistics can be pulled manually from the system or sent at configured intervals. The bulk statistics are stored on the receiver(s) in files.
> The format of the bulk statistic data files can be configured by the user. Users can specify the format of the file name, file headers, and/or footers to include information such as the date, system host name, system uptime, the IP address of the system generating the statistics (available for only for headers and footers), and/or the time that the file was generated.
> When the Web Element Manager is used as the receiver, it is capable of further processing the statistics data through XML parsing, archiving, and graphing.
> The Bulk Statistics Server component of the Web Element Manager parses collected statistics and stores the information in the PostgreSQL database. If XML file generation and transfer is required, this element generates the XML output and can send it to a Northbound NMS or an alternate bulk statistics server for further processing.
> 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.
> Important: For more information on bulk statistic configuration, refer to the Configuring and Maintaining Bulk Statistics chapter in the System Administration Guide.
> Congestion Control
> The congestion control feature allows you to set policies and thresholds and specify how the system reacts when faced with a heavy load condition.
> Congestion control monitors the system for conditions that could potentially degrade performance when the system is under heavy load. Typically, these conditions are temporary (for example, high CPU or memory utilization) and are quickly resolved. However, continuous or large numbers of these conditions within a specific time interval may have an impact the system’s ability to service subscriber sessions. Congestion control helps identify such conditions and invokes policies for addressing the situation.
> Congestion control operation is based on configuring the following:

> • | Congestion Condition Thresholds: Thresholds dictate the conditions for which congestion control is enabled and establishes limits for defining the state of the system (congested or clear). These thresholds function in a way similar to operation thresholds that are configured for the system as described in the Thresholding Configuration Guide. The primary difference is that when congestion thresholds are reached, a service congestion policy and an SNMP trap, starCongestion, are generated.

> A threshold tolerance dictates the percentage under the configured threshold that must be reached in order for the condition to be cleared. An SNMP trap, starCongestionClear, is then triggered.

> • | Port Utilization Thresholds: If you set a port utilization threshold, when the average utilization of all ports in the system reaches the specified threshold, congestion control is enabled.

> • | Port-specific Thresholds: If you set port-specific thresholds, when any individual port-specific threshold is reached, congestion control is enabled system-wide.

> • | Service Congestion Policies: Congestion policies are configurable for each service. These policies dictate how services respond when the system detects that a congestion condition threshold has been crossed.

> Important: For more information on congestion control, refer to the Congestion Control chapter in the System Administration Guide.
> Default and Dedicated EPC Bearers
> Provides a foundation for contributing towards improved Quality of User Experience (QoE) by enabling deterministic end-to-end forwarding and scheduling treatments for different services or classes of applications pursuant to their requirements for committed bandwidth resources, jitter and delay. In this way, each application receives the service treatment that users expect.
> In the StarOS 9.0 release, the Cisco EPC core platforms support one or more EPS bearers (default plus dedicated). An EPS bearer is a logical aggregate of one or more Service Data Flows (SDFs), running between a UE and a P-GW in the case of a GTP-based S5/S8 interface, and between a UE and HSGW (HRPD Serving Gateway) in case of a PMIP-based S2a interface. In networks where GTP is used as the S5/S8 protocol, the EPS bearer constitutes a concatenation of a radio bearer, S1-U bearer and an S5/S8 bearer anchored on the P-GW. In cases where PMIPv6 is used the EPS bearer is concatenated between the UE and HSGW with IP connectivity between the HSGW and P-GW.
> Note: This release supports only GTP-based S5/S8 and PMIPv6 S2a capabilities with no commercial support for PMIPv6 S5/S8.
> An EPS bearer uniquely identifies traffic flows that receive a common QoS treatment between a UE and P-GW in the GTP-based S5/S8 design, and between a UE and HSGW in the PMIPv6 S2a approach. If different QoS scheduling priorities are required between Service Data Flows, they should be assigned to separate EPS bearers. Packet filters are signalled in the NAS procedures and associated with a unique packet filter identifier on a per-PDN connection basis.
> One EPS bearer is established when the UE connects to a PDN, and that remains established throughout the lifetime of the PDN connection to provide the UE with always-on IP connectivity to that PDN. That bearer is referred to as the default bearer. A PDN connection represents a traffic flow aggregate between a mobile access terminal and an external Packet Data Network (PDN) such as an IMS network, a walled garden application cloud or a back-end enterprise network. Any additional EPS bearer that is established to the same PDN is referred to as a dedicated bearer. The EPS bearer Traffic Flow Template (TFT) is the set of all 5-tuple packet filters associated with a given EPS bearer. The EPC core elements assign a separate bearer ID for each established EPS bearer. At a given time a UE may have multiple PDN connections on one or more P-GWs.
> DHCP Support
> The P-GW supports dynamic IP address assignment to subscriber IP PDN contexts using the Dynamic Host Control Protocol (DHCP), as defined by the following standards:

> • | RFC 2131, Dynamic Host Configuration Protocol

> • | RFC 2132, DHCP Options and BOOTP Vendor Extensions

> The method by which IP addresses are assigned to a PDN context is configured on an APN-by-APN basis. Each APN template dictates whether it will support static or dynamic addresses. Dynamically assigned IP addresses for subscriber PDN contexts can be assigned through the use of DHCP.
> The P-GW acts as a DHCP server toward the UE and a DHCP client toward the external DHCP server. The DHCP server function and DHCP client function on the P-GW are completely independent of each other; one can exist without the other.
> The P-GW does not support DHCP-relay.
> Important: Currently, the P-GW only supports DHCP with IPv4 addresses. IPv6 address support is planned at a later date.
> Deferred IPv4 Address Allocation
> Apart from obtaining IP addresses during initial access signalling, a UE can indicate via PCO options that it prefers to obtain IP address and related configuration via DHCP after default bearer has been established. This is also know as Deferred Address Allocation.
> IPv4 addresses are becoming an increasingly scarce resource. Since 4G networks like LTE are always on, scarce resources such as IPv4 addresses cannot/should not be monopolized by UEs when they are in an ECM-IDLE state.
> PDN-type IPv4v6 allows a dual stack implementing. The P-GW allocates an IPv6 address only by default for an IPv4v6 PDN type. The UE defers the allocation of IPv4 addresses based upon its needs, and relinquishes any IPv4 addresses to the global pool once it is done. The P-GW may employ any IPv4 address scheme (local pool or external DHCP server) when providing an IPv4 address on demand.
> Direct Tunnel Support
> When Gn/Gp interworking with pre-release SGSNs is enabled, the GGSN service on the P-GW supports direct tunnel functionality.
> Direct tunnel improves the user experience (e.g. expedited web page delivery, reduced round trip delay for conversational services, etc.) by eliminating SGSN tunnel “switching” latency from the user plane. An additional advantage of direct tunnel from an operational and capital expenditure perspective is that direct tunnel optimizes the usage of user plane resources by removing the requirement for user plane processing on the SGSN.
> The direct tunnel architecture allows the establishment of a direct user plane tunnel between the RAN and the GGSN, bypassing the SGSN. The SGSN continues to handle the control plane signalling and typically makes the decision to establish direct tunnel at PDP Context Activation. A direct tunnel is achieved at PDP context activation by the SGSN establishing a user plane (GTP-U) tunnel directly between RNC and GGSN (using an Update PDP Context Request toward the GGSN).
> A major consequence of deploying direct tunnel is that it produces a significant increase in control plane load on both the SGSN and GGSN components of the packet core. It is therefore of paramount importance to a wireless operator to ensure that the deployed GGSNs are capable of handling the additional control plane loads introduced of part of direct tunnel deployment. The Cisco GGSN and SGSN offer massive control plane transaction capabilities, ensuring system control plane capacity will not be a capacity limiting factor once direct tunnel is deployed.
> Important: For more information on direct tunnel support, refer to the Direct Tunnel appendix in this guide.
> Domain Based Flow Definitions
> This solution provides improved flexibility and granularity in obtaining geographicallycorrect exact IP entries of the servers by snooping DNS responses.
> Currently, it is possible to configure L7 rules to filter based on domain (m.google.com). Sometimes multiple servers may serve a domain, each with its own IP address. Using an IP-rule instead of an http rule will result in multiple IP-rules; one IP-rule for each server “behind” the domain, and it might get cumbersome to maintain a list of IP addresses for domain-based filters.
> In this solution, you can create ruledefs specifying hostnames (domain names) and parts of hostnames (domain names). Upon the definition of the hostnames/domain names or parts of them, the P-GW will monitor all the DNS responses sent towards the UE and will snoop only the DNS response, which has q-name or a-name as specified in the rules, and identify all the IP addresses resulted from the DNS responses. DNS snooping will be done on live traffic for every subscriber.
> DSCP Marking
> Provides support for more granular configuration of DSCP marking.
> For Interactive Traffic class, the P-GW supports per-gateway service and per-APN configurable DSCP marking for Uplink and Downlink direction based on Allocation/Retention Priority in addition to the current priorities.
> The following matrix may be used to determine the Diffserv markings used based on the configured traffic class and Allocation/Retention Priority:
> Default DSCP Value Matrix

> Allocation Priority | 1 | 2 | 3
> Traffic Handling Priority |  |  |
> 1 | ef | ef | ef
> 2 | af21 | af21 | af21
> 3 | af21 | af21 | af21

> ‌
> In addition, the P-GW allows configuration of diameter packets with DSCP values.
> Dynamic Policy Charging Control (Gx Reference Interface)
> Dynamic policy and charging control provides a primary building block toward the realization of IMS multimedia applications. In contrast to statically provisioned architectures, the dynamic policy framework provides a centralized service control layer with global awareness of all access-side network elements. The centralized policy decision elements simplify the process of provisioning global policies to multiple access gateways. Dynamic policy is especially useful in an Always-On deployment model as the usage paradigm transitions from a short lived to a lengthier online session in which the volume of data consumed can be extensive. Under these conditions dynamic policy management enables dynamic just in-time resource allocation to more efficiently protect the capacity and resources of the network.
> Dynamic Policy Control represents the ability to dynamically authorize and control services and application flows between a Policy Charging Enforcement Function (PCEF) on the P-GW and the PCRF. Policy control enables a centralized and decoupled service control architecture to regulate the way in which services are provisioned and allocated at the bearer resource layer.
> The StarOS 9.0 release included enhancements to conform with 3GPP TS 29.212 and 29.230 functions. The Gx reference interface uses Diameter transport and IPv6 addressing. The subscriber is identified to the PCRF at session establishment using IMSI based NAI's within the Subscription-ID AVP. Additionally the IMEI within the Equipment-Info AVP is used to identify the subscriber access terminal to the policy server. The Gx reference interface supports the following capabilities:

> • | Authorize the bearer establishment for a packet flow

> • | Dynamic L3/L4 transfer of service data flow filters within PCC rules for selection and policy enforcement of downlink/uplink IP CAN bearers

> • | Support static pre-provisioned L7 rulebase name attribute as trigger for activating Inline Services such as Peer-to-Peer Detection

> • | Authorize the modification of a service data flow

> • | Revoke the authorization of a packet flow

> • | Provision PCC rules for service data flows mapped to default or dedicated EPS bearers

> • | Support P-GW initiated event triggers based on change of access network gateway or IP CAN

> • | Provide the ability to set or modify APN-AMBR for a default EPS bearer

> • | Create or modify QoS service priority by including QCI values in PCC rules transmitted from PCRF to PCEF functions

> Enhanced Charging Service (ECS)
> The Enhanced Charging Service provides an integrated in-line service for inspecting subscriber data packets and generating detail records to enable billing based on usage and traffic patterns. Other features include:

> • | Content Analysis Support

> • | Content Service Steering

> • | Support for Multiple Detail Record Types

> • | Diameter Credit Control Application

> • | Accept TCP Connections from DCCA Server

> • | Gy Interface Support

> The Enhanced Charging Service (ECS) is an in-line service feature that is integrated within the system. ECS enhances the mobile carrier's ability to provide flexible, differentiated, and detailed billing to subscribers by using Layer 3 through Layer 7 deep packet inspection with the ability to integrate with back-end billing mediation systems.
> ECS interacts with active mediation systems to provide full real-time prepaid and active charging capabilities. Here the active mediation system provides the rating and charging function for different applications.
> In addition, ECS also includes extensive record generation capabilities for post-paid charging with in-depth understanding of the user session. Refer to the Support for Multiple Detail Record Types section for more information.
> The major components include:

> • | Service Steering: Directs subscriber traffic into the ECS subsystem. Service Steering is used to direct selective subscriber traffic flows via an Access Control List (ACL). It is used for other redirection applications as well for both internal and external services and servers.

> • | Protocol Analyzer: The software stack responsible for analyzing the individual protocol fields and states during packet inspection. It performs two types of packet inspection:

> • | Shallow Packet Inspection: inspection of the layer 3 (IP header) and layer 4 (e.g. UDP or TCP header) information.

> • | Deep Packet Inspection: inspection of layer 7 and 7+ information. Deep packet inspection functionality includes:

> • | Detection of URI (Uniform Resource Identifier) information at level 7 (e.g., HTTP, WTP, RTSP Uniform Resource Locators (URLs)).

> • | Identification of true destination in the case of terminating proxies, where shallow packet inspection would only reveal the destination IP address / port number of a terminating proxy.

> • | De-encapsulation of upper layer protocol headers, such as MMS-over-WTP, WSP-over-UDP, and IP-over GPRS.

> • | Verification that traffic actually conforms to the protocol the layer 4 port number suggests.

> • | Rule Definitions: User-defined expressions, based on protocol fields and/or protocol-states, which define what actions to take when specific field values are true. Expressions may contain a number of operator types (string, =, >, etc.) based on the data type of the operand. Each Ruledef configuration is consisting of multiple expressions applicable to any of the fields or states supported by the respective analyzers.

> • | Rule Bases: a collection of rule definitions and their associated billing policy. The rule base determines the action to be taken when a rule is matched. It is possible to define a rule definition with different actions.

> Mediation and Charging Methods
> To provide maximum flexibility when integrating with billing mediation systems, ECS supports a full range of charging and authorization interfaces.

> • | Pre-paid: In a pre-paid environment, the subscribers pay for service prior to use. While the subscriber is using the service, credit is deducted from subscriber's account until it is exhausted or call ends. The pre-paid accounting server is responsible for authorizing network nodes (GGSNs) to grant access to the user, as well as grant quotas for either time connected or volume used. It is up to the network node to track the quota use, and when these use quotas run low, the network node sends a request to the pre-paid server for more quota.

> If the user has not used up the purchased credit, the server grants quota and if no credit is available to the subscriber the call will be disconnected. ECS and DCCA manage this functionality by providing the ability to setup quotas for different services.
> Pre-paid quota in ECS is implemented using DIAMETER Credit Control Application (DCCA). DCCA supports the implementation of real-time credit control for a variety of services, such as networks access, messaging services, and download services.
> In addition to being a general solution for real-time cost and credit control, DCCA includes these features:

> • | Real-time Rate Service Information - DCCA can verify when end subscribers' accounts are exhausted or expired; or deny additional chargeable events.

> • | Support for Multiple Services - DCCA supports the usage of multiple services within one subscriber session. Multiple Service support includes; 1) ability to identify and process the service or group of services that are subject to different cost structures 2) independent credit control of multiple services in a single credit control sub-session.

> Refer to the Diameter Credit Control Application section for more information.

> • | Post-paid: In a post-paid environment, the subscribers pay after use of the service. A AAA server is responsible for authorizing network nodes (GGSNs) to grant access to the user and a CDR system generates G-CDRs/eG-CDRs/EDRs/UDRs or Comma Separated Values (CSVs) for billing information on pre-defined intervals of volume or per time.

> Important: Support for the Enhanced Charging Service requires a service license; the ECS license is included in the P-GW session use license. For more information on ECS, refer to the Enhanced Charging Service Administration Guide.
> Content Analysis Support
> The Enhanced Charging Service is capable of performing content analysis on packets of many different protocols at different layers of the OSI model.
> The ECS content analyzers are able to inspect and maintain state across various protocols at all layers of the OSI stack. ECS system supports, inspects, and analyzes the following protocols:

> • | IP

> • | TCP

> • | UDP

> • | DNS

> • | FTP

> • | TFTP

> • | SMTP

> • | POP3

> • | HTTP

> • | ICMP

> • | WAP: WTP and WSP

> • | Real-Time Streaming: RTP and RTSP

> • | MMS

> • | SIP and SDP

> • | File analysis: examination of downloaded file characteristics (e.g. file size, chunks transferred, etc.) from file transfer protocols such as HTTP and FTP.

> Traffic analyzers in enhanced charging subsystem are based on configured rules. Rules used for Traffic analysis analyze packet flows and form usage records. Usage records are created per content type and forwarded to a pre-paid server or to a mediation/billing system. A traffic analyzer performs shallow (Layer 3 and Layer 4) and deep (above Layer 4) packet inspection of the IP packet flows.
> The Traffic Analyzer function is able to do a shallow (layer 3 and layer 4) and deep (above layer 4) packet inspection of IP Packet Flows.
> It is able to correlate all layer 3 packets (and bytes) with higher layer trigger criteria (e.g. URL detected in a HTTP header) and it is also perform stateful packet inspection to complex protocols like FTP, RTSP, SIP that dynamically open ports for the data path and by this way, user plane payload is differentiated into “categories”.
> The Traffic Analyzer works on the application level as well and performs event based charging without the interference of the service platforms.
> Important: This functionality is available for use with the Enhanced Charging Service which requires a session-use license. For more information on ECS, refer to the Enhanced Charging Service Administration Guide.
> Content Service Steering
> Content Service Steering (CSS) directs selective subscriber traffic into the ECS subsystem (In-line services internal to the system) based on the content of the data presented by mobile subscribers.
> CSS uses Access Control Lists (ACLs) to redirect selective subscriber traffic flows. ACLs control the flow of packets into and out of the system. ACLs consist of “rules” (ACL rules) or filters that control the action taken on packets matching the filter criteria.
> ACLs are configurable on a per-context basis and applies to a subscriber through either a subscriber profile or an APN profile in the destination context.
> Important: For more information on CSS, refer to the Content Service Steering chapter of the System Administration Guide.
> Important: For more information on ACLs, refer to the IP Access Control Lists chapter of the System Administration Guide.
> Support for Multiple Detail Record Types
> To meet the requirements of standard solutions and at the same time, provide flexible and detailed information on service usage, the Enhanced Charging Service (ECS) provides the following type of usage records:

> • | Event Detail Records (EDRs)

> • | Usage Detail Records (UDRs)

> ECS provides for the generation of charging data files, which can be periodically retrieved from the system and used as input to a billing mediation system for post-processing. These files are provided in a standard format, so that the impact on the existing billing/mediation system is minimal and at the same time, these records contain all the information required for billing based on the content.
> GTPP accounting in ECS allows the collection of counters for different types of data traffic into detail records. The following types of detail records are supported:

> • | Event Detail Records (EDRs): An alternative to standard G-CDRs when the information provided by the G-CDRs is not sufficient to do the content billing. EDRs are generated according to explicit action statements in rule commands that are user-configurable. The EDRs are generated in comma separated values (CSV) format, generated as defined in traffic analysis rules.

> • | User Detail Records (UDRs): Contain accounting information related to a specific mobile subscriber. The fields to be reported in them are user-configurable and are generated on any trigger of time threshold, volume threshold, handoffs, and call termination. The UDRs are generated in comma separated values (CSV) format, generated as defined in traffic analysis rules.

> Important: This functionality is available for use with the Enhanced Charging Service which requires a session-use license. For more information on ECS, refer to the Enhanced Charging Service Administration Guide.
> Diameter Credit Control Application
> Provides a pre-paid billing mechanism for real-time cost and credit control based on the following standards:

> • | RFC 3588, Diameter Base Protocol, September 2003

> • | RFC 4006, Diameter Credit-Control Application, August 2005

> The Diameter Credit Control Application (DCCA) is used to implement real-time credit-control for a variety of end user services such as network access, Session Initiation Protocol (SIP) services, messaging services, download services etc.
> Used in conjunction with ECS, the DCCA interface uses a mechanism to allow the user to be informed of the charges to be levied for a requested service. In addition, there are services such as gaming and advertising that may credit as well as debit from a user account.
> DCCA also supports the following:

> • | Real-time Rate Service Information: The ability to verify when end subscribers' accounts are exhausted or expired; or deny additional chargeable events.

> • | Support for Multiple Services: The usage of multiple services within one subscriber session is supported. Multiple Service support includes:

> • | The ability to identify and process the service or group of services that are subject to different cost structures.

> • | Independent credit control of multiple services in a single credit control sub-session.

> Important: This functionality is available for use with the Enhanced Charging Service, which requires a session-use license. For more information on ECS, refer to the Enhanced Charging Service Administration Guide.
> Accept TCP Connections from DCCA Server
> This feature allows for peer Diameter Credit Control Application servers to initiate a connection the NGME.
> This feature allows peer diameter nodes to connect to the NGME on TCP port 3868 when the diameter server is incapable of receiving diameter incoming diameter requests.
> Important: For more information on Diameter support, refer to the AAA and GTPP Interface Administration and Reference.
> Gy Interface Support
> The Gy interface enables the wireless operator to implement a standardized interface for real time content based charging with differentiated rates for time based and volume based charging.
> As it is based on a quota mechanism, the Gy interface enables the wireless operator to spare expensive Prepaid System resources.
> As it enables time-, volume-, and event-based charging models, the Gy interface flexibly enables the operator to implement charging models tailored to their service strategies.
> 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 provides an online charging interface that works with the ECS deep packet inspection feature. With Gy, customer traffic can be gated and billed in an “online” or “prepaid” style. Both time- and volume-based charging models are supported. In all of these models, differentiated rates can be applied to different services based on shallow or deep packet inspection.
> Gy is a Diameter interface. As such, it is implemented atop, and inherits features from, the Diameter Base Protocol. The system supports the applicable Base network and application features, including directly connected, relayed or proxied DCCA servers using TLS or plaintext TCP.
> In the simplest possible installation, the system exchanges Gy Diameter messages over Diameter TCP links between itself and one “prepay” server. For a more robust installation, multiple servers would be used. These servers may optionally share or mirror a single quota database so as to support Gy session failover from one server to the other. For a more scalable installation, a layer of proxies or other Diameter agents can be introduced to provide features such as multi-path message routing or message and session redirection features.
> The Cisco implementation is based on the following standards:

> • | RFC 4006 generic DCCA, including:

> • | CCR Initial, Update, and Final signaling

> • | ASR and RAR asynchronous DCCA server messages

> • | Time, Total-Octets, and Service-Specific-Units quota management

> • | Multiple independent quotas using Multiple-Services-Credit-Control

> • | Rating-Group for quota-to-traffic association

> • | CC-Failure-Handling and CC-Session-Failover features

> • | Final-Unit-Action TERMINATE behavior

> • | Tariff-Time-Change feature.

> • | 3GPP TS 32.299 online mode “Gy” DCCA, including:

> • | Final-Unit-Action REDIRECT behavior

> • | Quota-Holding-Time: This defines a user traffic idle time, on a per category basis, after which the usage is returned and no new quota is explicitly requested

> • | Quota-Thresholds: These AVPs define a low value watermark at which new quota will be sought before the quota is entirely gone; the intent is to limit interruption of user traffic.

> These AVPs exist for all quota flavors, for example “Time-Quota-Threshold”.

> • | Trigger-Type: This AVP defines a set of events which will induce a re-authentication of the current session and its quota categories.

> Gn/Gp Handoff Support
> In LTE deployments, smooth handover support is required between 3G/2G and LTE networks, and Evolved Packet Core (EPC) is designed to be a common packet core for different access technologies. P-GW supports handovers as user equipment (UE) moves across different access technologies.
> Cisco's P-GW supports inter-technology mobility handover between 4G and 3G/2G access. Interworking is supported between the 4G and 2G/3G SGSNs, which provide only Gn and Gp interfaces but no S3, S4 or S5/S8 interfaces. These Gn/Gp SGSNs provide no functionality introduced specifically for the evolved packet system (EPS) or for interoperation with the E-UTRAN. These handovers are supported only with a GTP-based S5/S8 and P-GW supports handoffs between GTPv2 based S5/S8 and GTPv1 based Gn/Gp tunneled connections. In this scenario, the P-GW works as an IP anchor for the EPC.
> Important: To support the seamless handover of a session between GGSN and P-GW, the two independent services must be co-located on the same node and configured within the same context for optimum interoperation.
> Important: For more information on Gn/GP handoffs, refer to Gn/Gp GGSN/SGSN (GERAN/UTRAN) in the Supported Logical Network Interfaces (Reference Points) section in this chapter.
> IMS Emergency Bearer Handling
> With this support, a UE is able to connect to an emergency PDN and make Enhanced 911 (E911) calls while providing the required location information to the Public Safety Access Point (PSAP).
> E911 is a telecommunications-based system that is designed to link people who are experiencing an emergency with the public resources that can help. This feature supports E911-based calls across the LTE and IMS networks. In a voice over LTE scenario, the subscriber attaches to a dedicated packet data network (PDN) called EPDN (Emergency PDN) in order to establish a voice over IP connection to the PSAP. Signaling either happens on the default emergency bearer, or signaling and RTP media flow over separate dedicated emergency bearers. Additionally, different than normal PDN attachment that relies on AAA and PCRF components for call establishment, the EPDN attributes are configured locally on the P-GW, which eliminates the potential for emergency call failure if either of these systems is not available.
> Emergency bearer services are provided to support IMS emergency sessions. Emergency bearer services are functionalities provided by the serving network when the network is configured to support emergency services. Emergency bearer services are provided to normally attached UEs and to UEs that are in a limited service state (depending on local service regulations, policies, and restrictions). Receiving emergency services in limited service state does not require a subscription.
> The standard (refer to 3GPP TS 23.401) has identified four behaviors that are supported:

> • | Valid UEs only

> • | Authenticated UEs only

> • | MSI required, authentication optional

> • | All UEs

> To request emergency services, the UE has the following two options:

> • | UEs that are in a limited service state (due to attach reject from the network, or since no SIM is present), initiate an ATTACH indicating that the ATTACH is for receiving emergency bearer services. After a successful attach, the services that the network provides the UE is solely in the context of Emergency Bearer Services.

> • | UEs that camp normally on a cell initiates a normal ATTACH if it requires emergency services. Normal attached UEs initiated a UE Requested PDN Connectivity procedure to request Emergency Bearer Services.

> IP Access Control Lists
> IP access control lists allow you to set up rules that control the flow of packets into and out of the system based on a variety of IP packet parameters.
> IP access lists, or access control lists (ACLs) as they are commonly referred to, are used to control the flow of packets into and out of the system. They are configured on a per-context basis and consist of “rules” (ACL rules) or filters that control the action taken on packets that match the filter criteria. Once configured, an ACL can be applied to any of the following:

> • | An individual interface

> • | All traffic facilitated by a context (known as a policy ACL)

> • | An individual subscriber

> • | All subscriber sessions facilitated by a specific context

> Important: For more information on IP access control lists, refer to the IP Access Control Lists chapter in the System Administration Guide.
> IP Address Hold Timers
> Also known as address quarantining, this subscriber-level CLI introduces an address hold timer to temporarily buffer a previously assigned IP address from an IP address pool to prevent it from being recycled and reassigned to a new subscriber session. It is especially useful during inter-RAT handovers that sometimes lead to temporary loss of the mobile data session.
> This feature provides a higher quality user experience for location-based services where the remote host server needs to reach the mobile device.
> IPv6 Capabilities
> Enables increased address efficiency and relieves pressures caused by rapidly approaching IPv4 address exhaustion problem.
> The P-GW offers the following IPv6 capabilities:
> Native IPv6 and IPv6 transport

> • | Support for any combination of IPv4, IPv6 or dual stack IPv4/v6 address assignment from dynamic or static address pools on the P-GW.

> • | Support for native IPv6 transport and service addresses on PMIPv6 S2a interface. Note that transport on GTP S5/S8 connections in this release is IPv4 based.

> • | Support for IPv6 transport for outbound traffic over the SGi reference interface to external Packet Data Networks.

> IPv6 Connections to Attached Elements
> IPv6 transport and interfaces are supported on all of the following connections:

> • | Diameter Gx policy signaling interface

> • | Diameter Gy online charging reference interface

> • | S6b authentication interface to external 3GPP AAA server

> • | Diameter Rf offline charging interface

> • | Lawful Intercept (X1, X2 interfaces)

> Routing and Miscellaneous Features

> • | OSPFv3

> • | MP-BGP v6 extensions

> • | IPv6 flows (Supported on all Diameter QoS and Charging interfaces as well as Inline Services (e.g. ECS)

> Local Break-Out
> Provides a standards-based procedure to enable LTE operators to generate additional revenues by accepting traffic from visited subscribers based on roaming agreements with other mobile operators.
> Local Breakout is a policy-based forwarding function that plays an important role in inter-provider roaming between LTE service provider networks. Local Breakout is determined by the SLAs for handling roaming calls between visited and home networks. In some cases, it is more beneficial to locally breakout a roaming call on a foreign network to the visited P-W rather than incur the additional transport costs to backhaul the traffic to the Home network.
> If two mobile operators have a roaming agreement in place, Local Break-Out enables the visited user to attach to the V-PLMN network and be anchored by the local P-GW in the visited network. The roaming architecture relies on the HSS in the home network and also introduces the concept of the S9 policy signaling interface between the H-PCRF in the H-PLMN and the V-PCRF in the V-PLMN. When the user attaches to the EUTRAN cell and MME (Mobility Management Entity) in the visited network, the requested APN name in the S6a NAS signaling is used by the HSS in the H-PLMN to select the local S-GW (Serving Gateway) and P-GWs in the visited EPC network.
> Management System Overview
> The system's management capabilities are designed around the Telecommunications Management Network (TMN) model for management - focusing on providing superior quality network element (NE) and element management system (Cisco Web Element Manager) functions. The system provides element management applications that can easily be integrated, using standards-based protocols (CORBA and SNMPv1, v2), into higher-level management systems - giving wireless operators the ability to integrate the system into their overall network, service, and business management systems. In addition, all management is performed out-of-band for security and to maintain system performance.
> Cisco's O&M module offers comprehensive management capabilities to the operators and enables them to operate the system more efficiently. There are multiple ways to manage the system either locally or remotely using its out-of-band management interfaces.
> These include:

> • | Using the command line interface (CLI)

> • | Remote login using Telnet, and Secure Shell (SSH) access to CLI through SPIO card's Ethernet management interfaces

> • | Local login through the Console port on SPIO card using an RS-232 serial connection

> • | Using the Web Element Manager application

> • | Supports communications through 10 Base-T, 100 Base-TX, 1000 Base-TX, or 1000

> • | Base-SX (optical gigabit Ethernet) Ethernet management interfaces on the SPIO

> • | Client-Server model supports any browser (i.e. Microsoft Internet Explorer v5.0 and above or Netscape v4.7 or above, and others)

> • | Supports Common Object Request Broker Architecture (CORBA) protocol and Simple Network Management Protocol version 1 (SNMPv1) for fault management

> • | Provides complete Fault, Configuration, Accounting, Performance, and Security (FCAPS) capabilities

> • | Can be easily integrated with higher-level network, service, and business layer applications using the Object Management Group's (OMG’s) Interface Definition Language (IDL)

> The following figure demonstrates these various element management options and how they can be utilized within the wireless carrier network.
> Element Management Methods
> Important: P-GW management functionality is enabled by default for console-based access. For GUI-based management support, refer to the Web Element Management System section in this chapter.
> Important: For more information on command line interface based management, refer to the Command Line Interface Reference.
> Mobile IP Registration Revocation
> Mobile IP registration revocation functionality provides the following benefits:

> • | Timely release of Mobile IP resources at the HSGW and/or P-GW

> • | Accurate accounting

> • | Timely notification to mobile node of change in service

> Registration Revocation is a general mechanism whereby either the P-GW or the HSGW providing Mobile IP functionality to the same mobile node can notify the other mobility agent of the termination of a binding. Mobile IP Registration Revocation can be triggered at the HSGW by any of the following:

> • | Session terminated with mobile node for whatever reason

> • | Session renegotiation

> • | Administrative clearing of calls

> • | Session Manager software task outage resulting in the loss of HSGW sessions (sessions that could not be recovered)

> Important: Registration Revocation functionality is also supported for Proxy Mobile IP. However, only the P-GW can initiate the revocation for Proxy-MIP calls.
> Important: For more information on MIP registration revocation support, refer to the Mobile IP Registration Revocation appendix in this guide.
> Multiple PDN Support
> Enables an APN-based user experience that enables separate connections to be allocated for different services including IMS, Internet, walled garden services, or off-deck content services.
> The MAG function on the S-GW can maintain multiple PDN or APN connections for the same user session. The MAG runs a single node level Proxy Mobile IPv6 tunnel for all user sessions toward the LMA function of the P-GW. When a user wants to establish multiple PDN connections, the MAG brings up the multiple PDN connections over the same PMIPv6 session to one or more P-GW LMA's. The P-GW in turn allocates separate IP addresses (Home Network Prefixes) for each PDN connection and each one can run one or multiple EPC default & dedicated bearers. To request the various PDN connections, the MAG includes a common MN-ID and separate Home Network Prefixes, APN's and a Handover Indication Value equal to one in the PMIPv6 Binding Updates.
> Non-Optimized e-HRPD to Native LTE (E-UTRAN) Mobility Handover
> This feature enables a seamless inter-technology roaming capability in support of dual mode e-HRPD/e-UTRAN access terminals.
> The non-optimized inter-technology mobility procedure is rooted at the P-GW as the mobility anchor point for supporting handovers for dual radio technology e-HRPD/E-UTRAN access terminals. To support this type of call handover, the P-GW supports handoffs between the GTP-based S5/S8 (GTPv2-C / GTPv1-U) and PMIPv6 S2a tunneled connections. It also provisions IPv4, IPv6, or dual stack IPv4/IPv6 PDN connections from a common address pool and preserves IP addresses assigned to the UE during inter-technology handover. In the current release, the native LTE (GTP-based) P-GW service address is IPv4-based, while the e-HRPD (PMIP) address is an IPv6 service address.
> During the initial network attachment for each APN that the UE connects to, the HSS returns the FQDN of the P-GW for the APN. The MME uses DNS to resolve the P-GW address. When the PDN connection is established in the P-GW, the P-GW updates the HSS with the IP address of the P-GW on PDN establishment through the S6b authentication process. When the mobile user roams to the e-HRPD network, the HSS returns the IP address of the P-GW in the P-GW Identifier through the STa interface and the call ends up in the same P-GW. The P-GW is also responsible for initiating the session termination on the serving access connection after the call handover to the target network.
> During the handover procedure, all dedicated EPS bearers must be re-established. On LTE- handovers to a target e-HRPD access network, the dedicated bearers are initiated by the mobile access terminal. In contrast, on handovers in the opposite direction from e-HRPD to LTE access networks, the dedicated bearers are network initiated through Gx policy interactions with the PCRF server.
> Finally, in order to support the inter-technology handovers, the P-GW uses common interfaces and Diameter endpoint addresses for the various reference points:

> • | S6b: Non-3GPP authentication

> • | Gx: QoS Policy and Charging

> • | Rf: Offline Charging

> All three types of sessions are maintained during call handovers. The bearer binding will be performed by the HSGW during e-HRPD access and by the P-GW during LTE access. Thus, the Bearer Binding Event Reporting (BBERF) function needs to migrate between the P-GW and the HSGW during the handover. The HSGW establishes a Gxa session during e-HRPD access for bearer binding and releases the session during LTE access. The HSGW also maintains a limited context during the e-HRPD <->LTE handover to reduce latency in the event of a quick handover from the LTE RAN back to the e-HRPD network.
> Important: For more information on handoff interfaces, refer to the Supported Logical Network Interfaces (Reference Points) section in this chapter.
> Online/Offline Charging
> The Cisco EPC platform offers support for online and offline charging interactions with external OCS and CGF/CDF servers.
> Online Charging
> Gy/Ro Reference Interface:
> The StarOS 9.0 online prepaid reference interface provides compatibility with the 3GPP TS 23.203, TS 32.240, TS 32.251 and TS 32.299 specifications. The Gy/Ro reference interface uses Diameter transport and IPv6 addressing. Online charging is a process whereby charging information for network resource usage must be obtained by the network in order for resource usage to occur. This authorization is granted by the Online Charging System (OCS) upon request from the network. The P-GW uses a charging characteristics profile to determine whether to activate or deactivate online charging. Establishment, modification or termination of EPS bearers is generally used as the event trigger on the PCRF to activate online charging PCC rules on the P-GW.
> When receiving a network resource usage request, the network assembles the relevant charging information and generates a charging event towards the OCS in real-time. The OCS then returns an appropriate resource usage authorization that may be limited in its scope (e.g. volume of data or duration based). The OCS assigns quotas for rating groups and instructs the P-GW whether to continue or terminate service data flows or IP CAN bearers.
> The following Online Charging models and functions are supported:

> • | Time based charging

> • | Volume based charging

> • | Volume and time based charging

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

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

> • | Event based charging

> • | Billing cycle bandwidth rate limiting: Charging policy is enforced through interactions between the PDN GW and Online Charging Server. The charging enforcement point periodically conveys accounting information for subscriber sessions to the OCS and it is debited against the threshold that is established for the charging policy. Subscribers can be assigned a max usage for their tier (gold, silver, bronze for example), the usage can be tracked over a month, week, day, or peak time within a day. When the subscriber exceeds the usage limit, bandwidth is either restricted for a specific time period, or dropped depending on their tier of service.

> • | Fair usage controls

> Offline Charging
> Ga/Gz Reference Interfaces
> The Cisco P-GW supports 3GPP-compliant offline charging as defined in TS 32.251,TS 32.297 and 32.298. Whereas the S-GW generates SGW-CDRs to record subscriber level access to PLMN resources, the P-GW creates PGW-CDRs to record user access to external networks. Additionally, when Gn/Gp interworking with pre-release SGSNs is enabled, the GGSN service on the P-GW records G-CDRs to record user access to external networks.
> To provide subscriber level accounting, the Cisco S-GW and P-GWs support integrated Charging Transfer Functions (CTF) and Charging Data Functions (CDF). Each gateway uses Charging-ID's to distinguish between default and dedicated bearers within subscriber sessions. The Ga/Gz reference interface between the CDF and CGF is used to transfer charging records via the GTPP protocol. In a standards based implementation, the CGF consolidates the charging records and transfers them via an FTP/S-FTP connection over the Bm reference interface to a back-end billing mediation server. The Cisco EPC gateways also offer the ability to FTP/S-FTP charging records between the CDF and CGF server. CDR records include information such as Record Type, Served IMSI, ChargingID, APN Name, TimeStamp, Call Duration, Served MSISDN, PLMN-ID, etc. The ASR 5x00 platform offers a local directory to enable temporary file storage and buffer charging records in persistent memory located on a pair of dual redundant RAID hard disks. Each drive includes 147GB of storage and up to 100GB of capacity is dedicated to storing charging records. For increased efficiency it also possible to enable file compression using protocols such as GZIP. The Offline Charging implementation offers built-in heart beat monitoring of adjacent CGFs. If the Cisco P-GW has not heard from the neighbor CGF within the configurable polling interval, they will automatically buffer the charging records on the local drives until the CGF reactivates itself and is able to begin pulling the cached charging records.
> The P-GW supports a Policy Charging Enforcement Function (PCEF) to enable Flow Based Bearer Charging (FBC) via the Gy reference interface to adjunct OCS servers (See Online Charging description above).
> Rf Reference Interface
> The Cisco EPC platforms also support the Rf reference interface to enable direct transfer of charging files from the CTF function of the P-GW to external CDF/CGF servers. This interface uses Diameter Accounting Requests (Start, Stop, Interim, and Event) to transfer charging records to the CDF/CGF. Each gateway relies on triggering conditions for reporting chargeable events to the CDF/CGF. Typically as EPS bearers are activated, modified or deleted, charging records are generated. The EPC platforms include information such as Subscription-ID (IMSI), Charging-ID (EPS bearer identifier) and separate volume counts for the uplink and downlink traffic.
> Proxy Mobile IPv6 (S2a)
> Provides a mobility management protocol to enable a single LTE-EPC core network to provide the call anchor point for user sessions as the subscriber roams between native EUTRAN and non-native e-HRPD access networks
> S2a represents the trusted non-3GPP interface between the LTE-EPC core network and the evolved HRPD network anchored on the HSGW. In the e-HRPD network, network-based mobility provides mobility for IPv6 nodes without host involvement. Proxy Mobile IPv6 extends Mobile IPv6 signaling messages and reuses the HA function (now known as LMA) on the P-GW. This approach does not require the mobile node to be involved in the exchange of signaling messages between itself and the Home Agent. A proxy mobility agent (e.g. MAG function on HSGW) in the network performs the signaling with the home agent and does the mobility management on behalf of the mobile node attached to the network.
> The S2a interface uses IPv6 for both control and data. During the PDN connection establishment procedures the P-GW allocates the IPv6 Home Network Prefix (HNP) via Proxy Mobile IPv6 signaling to the HSGW. The HSGW returns the HNP in router advertisement or based on a router solicitation request from the UE. PDN connection release events can be triggered by either the UE, the HSGW or the P-GW.
> In Proxy Mobile IPv6 applications the HSGW (MAG function) and P-GW (LMA function) maintain a single shared tunnel and separate GRE keys are allocated in the PMIP Binding Update and Acknowledgement messages to distinguish between individual subscriber sessions. If the Proxy Mobile IP signaling contains Protocol Configuration Options (PCOs) it can also be used to transfer P-CSCF or DNS server addresses
> QoS Bearer Management
> Provides a foundation for contributing towards improved Quality of User Experience (QoE) by enabling deterministic end-to-end forwarding and scheduling treatments for different services or classes of applications pursuant to their requirements for committed bandwidth resources, jitter and delay. In this way, each application receives the service treatment that users expect.
> An EPS bearer is a logical aggregate of one or more Service Data Flows (SDFs), running between a UE and a P-GW in case of GTP-based S5/S8, and between a UE and HSGW in case of PMIP-based S2a connection. An EPS bearer is the level of granularity for bearer level QoS control in the EPC/E-UTRAN. The Cisco P-GW maintains one or more Traffic Flow Templates (TFT's) in the downlink direction for mapping inbound Service Data Flows (SDFs) to EPS bearers. The P-GW maps the traffic based on the downlink TFT to the S5/S8 bearer. The Cisco PDN GW offers all of the following bearer-level aggregate constructs:
> QoS Class Identifier (QCI): An operator provisioned value that controls bearer level packet forwarding treatments (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc). The Cisco EPC gateways also support the ability to map the QCI values to DiffServ code points in the outer GTP tunnel header of the S5/S8 connection. Additionally, the platform also provides configurable parameters to copy the DSCP marking from the encapsulated payload to the outer GTP tunnel header.
> Guaranteed Bit Rate (GBR): A GBR bearer is associated with a dedicated EPS bearer and provides a guaranteed minimum transmission rate in order to offer constant bit rate services for applications such as interactive voice that require deterministic low delay service treatment.
> Maximum Bit Rate (MBR): The MBR attribute provides a configurable burst rate that limits the bit rate that can be expected to be provided by a GBR bearer (e.g. excess traffic may get discarded by a rate shaping function). The MBR may be greater than or equal to the GBR for a given Dedicated EPS bearer.
> Aggregate Maximum Bit Rate (AMBR): AMBR denotes a bit rate of traffic for a group of bearers destined for a particular PDN. The Aggregate Maximum Bit Rate is typically assigned to a group of Best Effort service data flows over the Default EPS bearer. That is, each of those EPS bearers could potentially utilize the entire AMBR, e.g. when the other EPS bearers do not carry any traffic. The AMBR limits the aggregate bit rate that can be expected to be provided by the EPS bearers sharing the AMBR (e.g. excess traffic may get discarded by a rate shaping function). AMBR applies to all Non-GBR bearers belonging to the same PDN connection. GBR bearers are outside the scope of AMBR.
> Policing and Shaping: The Cisco P-GW offers a variety of traffic conditioning and bandwidth management capabilities. These tools enable usage controls to be applied on a per-subscriber, per-EPS bearer or per-PDN/APN basis. It is also possible to apply bandwidth controls on a per-APN AMBR capacity. These applications provide the ability to inspect and maintain state for user sessions or Service Data Flows (SDFs) within them using shallow L3/L4 analysis or high touch deep packet inspection at L7. Metering of out-of-profile flows or sessions can result in packet discards or reducing the DSCP marking to Best Effort priority. When traffic shaping is enabled the P-GW enqueues the non-conforming session to the provisioned memory limit for the user session. When the allocated memory is exhausted, the inbound/outbound traffic for the user can be transmitted or policed in accordance with operator provisioned policy.
> RADIUS Support
> Provides a mechanism for performing authorization, authentication, and accounting (AAA) for subscriber PDP contexts based on the following standards:

> • | RFC-2618, RADIUS Authentication Client MIB, June 1999

> • | RFC-2620, RADIUS Accounting Client MIB, June 1999

> • | RFC-2865, Remote Authentication Dial In User Service (RADIUS), June 2000

> • | 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

> The Remote Authentication Dial-In User Service (RADIUS) protocol is used to provide AAA functionality for subscriber PDP contexts. (RADIUS accounting is optional since GTPP can also be used.)
> Within contexts configured on the system, there are AAA and RADIUS protocol-specific parameters that can be configured. The RADIUS protocol-specific parameters are further differentiated between RADIUS Authentication server RADIUS Accounting server interaction.
> Among the RADIUS parameters that can be configured are:

> • | Priority: Dictates the order in which the servers are used allowing for multiple servers to be configured in a single context.

> • | Routing Algorithm: Dictate the method for selecting among configured servers. The specified algorithm dictates how the system distributes AAA messages across the configured AAA servers for new sessions. Once a session is established and an AAA server has been selected, all subsequent AAA messages for the session will be delivered to the same server.

> In the event that a single server becomes unreachable, the system attempts to communicate with the other servers that are configured. The system also provides configurable parameters that specify how it should behave should all of the RADIUS AAA servers become unreachable.
> The system provides an additional level of flexibility by supporting the configuration RADIUS server groups. This functionality allows operators to differentiate AAA services for subscribers based on the APN used to facilitate their PDP context.
> In general, 128 AAA Server IP address/port per context can be configured on the system and it selects servers from this list depending on the server selection algorithm (round robin, first server). Instead of having a single list of servers per context, this feature provides the ability to configure multiple server groups. Each server group, in turn, consists of a list of servers.
> This feature works in following way:

> • | All RADIUS authentication/accounting servers configured at the context-level are treated as part of a server group named “default”. This default server group is available to all subscribers in that context through the realm (domain) without any configuration.

> • | It provides a facility to create “user defined” RADIUS server groups, as many as 399 (excluding “default” server group), within a context. Any of the user defined RADIUS server groups are available for assignment to a subscriber through the APN configuration within that context.

> Since the configuration of the APN can specify the RADIUS server group to use as well as IP address pools from which to assign addresses, the system implements a mechanism to support some in-band RADIUS server implementations (i.e. RADIUS servers which are located in the corporate network, and not in the operator's network) where the NAS-IP address is part of the subscriber pool. In these scenarios, the P-GW supports the configuration of the first IP address of the subscriber pool for use as the RADIUS NAS-IP address.
> Important: For more information on RADIUS AAA configuration, refer AAA and GTPP Interface Administration and Reference.
> Source IP Address Validation
> Insures integrity between the attached subscriber terminal and the PDN GW by mitigating the potential for unwanted spoofing or man-in-the-middle attacks.
> The P-GW includes local IPv4/IPv6 address pools for assigning IP addresses to UEs on a per-PDN basis. The P-GW defends its provisioned address bindings by insuring that traffic is received from the host address that it has awareness of. In the event that traffic is received from a non-authorized host, the P- GW includes the ability to block the non-authorized traffic. The P-GW uses the IPv4 source address to verify the sender and the IPv6 source prefix in the case of IPv6.
> Subscriber Level Trace
> Provides a 3GPP standards-based session level trace function for call debugging and testing new functions and access terminals in an LTE environment.
> As a complement to Cisco's protocol monitoring function, the P-GW supports 3GPP standards based session level trace capabilities to monitor all call control events on the respective monitored interfaces including S5/S8, S2a, SGi, and Gx. The trace can be initiated using multiple methods:

> • | Management initiation via direct CLI configuration

> • | Management initiation at HSS with trace activation via authentication response messages over S6a reference interface

> • | Signaling based activation through signaling from subscriber access terminal

> Important: Once the trace is provisioned, it can be provisioned through the access cloud via various signaling interfaces.
> The session level trace function consists of trace activation followed by triggers. The time between the two events is treated much like Lawful Intercept where the EPC network element buffers the trace activation instructions for the provisioned subscriber in memory using camp-on monitoring. Trace files for active calls are buffered as XML files using non-volatile memory on the local dual redundant hard drives on the ASR 5x00 platform. The Trace Depth defines the granularity of data to be traced. Six levels are defined including Maximum, Minimum and Medium with ability to configure additional levels based on vendor extensions.
> All call control activity for active and recorded sessions is sent to an off-line Trace Collection Entity (TCE) using a standards-based XML format over a FTP or secure FTP (SFTP) connection. In the current release the IPv4 interfaces are used to provide connectivity to the TCE. Trace activation is based on IMSI or IMEI. Once a subscriber level trace request is activated it can be propagated via the S5/S8 signaling to provision the corresponding trace for the same subscriber call on the P-GW. The trace configuration will only be propagated if the P-GW is specified in the list of configured Network Element types received by the S-GW. Trace configuration can be specified or transferred in any of the following message types:

> • | S5/S8: Create Session Request

> • | S5/S8: Modify Bearer Request

> • | S5/S8: Trace Session Activation (New message defined in TS 32.422)

> Performance Goals: As subscriber level trace is a CPU intensive activity the max number of concurrently monitored trace sessions per Cisco P-GW is 32. Use in a production network should be restricted to minimize the impact on existing services.
> Threshold Crossing Alerts (TCA) Support
> Thresholding on the system is used to monitor the system for conditions that could potentially cause errors or outage. Typically, these conditions are temporary (i.e high CPU utilization, or packet collisions on a network) and are quickly resolved. However, continuous or large numbers of these error conditions within a specific time interval may be indicative of larger, more severe issues. The purpose of thresholding is to help identify potentially severe conditions so that immediate action can be taken to minimize and/or avoid system downtime.
> The system supports Threshold Crossing Alerts for certain key resources such as CPU, memory, IP pool addresses, etc. With this capability, the operator can configure threshold on these resources whereby, should the resource depletion cross the configured threshold, a SNMP Trap would be sent.
> The following thresholding models are supported by the system:

> • | Alert: A value is monitored and an alert condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.

> • | Alarm: Both high and low threshold are defined for a value. An alarm condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.

> Thresholding reports conditions using one of the following mechanisms:

> • | SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or clear) of each of the monitored values.

> Generation of specific traps can be enabled or disabled on the chassis. Ensuring that only important faults get displayed. SNMP traps are supported in both Alert and Alarm modes.

> • | Logs: The system provides a facility called threshold for which active and event logs can be generated. As with other system facilities, logs are generated Log messages pertaining to the condition of a monitored value are generated with a severity level of WARNING.

> Logs are supported in both the Alert and the Alarm models.

> • | Alarm System: High threshold alarms generated within the specified polling interval are considered “outstanding” until a the condition no longer exists or a condition clear alarm is generated. “Outstanding” alarms are reported to the system's alarm subsystem and are viewable through the Alarm Management menu in the Web Element Manager.

> The Alarm System is used only in conjunction with the Alarm model.
> Important: For more information on threshold crossing alert configuration, refer to the Thresholding Configuration Guide.
> UE Time Zone Reporting
> This feature enables time-based charging for specialized service tariffs, such as super off-peak billing plans
> Time Zone of the UE is associated with UE location (Tracking Area/Routing Area). The UE Time Zone Information Element is an attribute the MME tracks on a Tracking Area List basis and propagates over S11 and S5/S8 signalling to the P-GW.
> Time zone reporting can be included in billing records or conveyed in Gx/Gy signaling to external PCRF and OCS servers.
> Virtual APN Support
> Virtual APNs allow differentiated services within a single APN.
> The Virtual APN feature allows a carrier to use a single APN to configure differentiated services. The APN that is supplied by the MME is evaluated by the P-GW in conjunction with multiple configurable parameters. Then, the P-GW selects an APN configuration based on the supplied APN and those configurable parameters.
> APN configuration dictates all aspects of a session at the P-GW. Different policies imply different APNS. After basic APN selection, however, internal re-selection can occur based on the following parameters:

> • | Service name

> • | Subscriber type

> • | MCC-MNC of IMSI

> • | Domain name part of username (user@domain)

> • | S-GW address

> Features and Functionality - Inline Service Support
> This section describes the features and functions of inline services supported on the P-GW. These services require additional licenses to implement the functionality.
> This section describes the following features:

> • | Content Filtering

> • | Header Enrichment: Header Insertion and Encryption

> • | Mobile Video Gateway

> • | Network Address Translation (NAT)

> • | Peer-to-Peer Detection

> • | Personal Stateful Firewall

> • | Traffic Performance Optimization (TPO)

> Content Filtering
> The Cisco P-GW offers two variants of network-controlled content filtering / parental control services. Each approach leverages the native DPI capabilities of the platform to detect and filter events of interest from mobile subscribers based on HTTP URL or WAP/MMS URI requests:

> • | Integrated Content Filtering: A turnkey solution featuring a policy enforcement point and category based rating database on the Cisco P-GW. An offboard AAA or PCRF provides the per-subscriber content filtering information as subscriber sessions are established. The content filtering service uses DPI to extract URLs or URIs in HTTP request messages and compares them against a static rating database to determine the category match. The provisioned policy determines whether individual subscribers are entitled to view the content.

> • | Content Filtering ICAP Interface: This solution is appropriate for mobile operators with existing installations of Active Content Filtering external servers. The service continues to harness the DPI functions of the ASR 5x00 platform to extract events of interest. However in this case, the extracted requests are transferred via the Integrated Content Adaptation Protocol (ICAP) with subscriber identification information to the external ACF server which provides the category rating database and content decision functions.

> Integrated Adult Content Filter
> Provides a value-added service to prevent unintended viewing of objectionable content that exploits underage children. Content Filtering offers mobile operators a way to increase data ARPU and subscriber retention through a network-based solution for parental controls and content filtering. The integrated solution enables a single policy decision and enforcement point thereby streamlining the number of signaling interactions with external AAA/Policy Manager servers. When used in parallel with other services such as Enhanced Content Charging (ECS) it increases billing accuracy of charging records by insuring that mobile subscribers are only charged for visited sites they are allowed to access.
> The Integrated Adult Content Filter is a subscriber-aware inline service provisioned on an ASR 5x00 running P-GW services. Integrated Content Filtering utilizes the local DPI engine and harnesses a distributed software architecture that scales with the number of active P-GW sessions on the system.
> Content Filtering policy enforcement is the process of deciding if a subscriber should be able to receive some content. Typical options are to allow, block, or replace/redirect the content based on the rating of the content and the policy defined for that content and subscriber. The policy definition is transferred in an authentication response from a AAA server or Diameter policy message via the Gx reference interface from an adjunct PCRF. The policy is applied to subscribers through rulebase or APN/Subscriber configuration. The policy determines the action to be taken on the content request on the basis of its category. A maximum of one policy can be associated with a rulebase.
> ICAP Interface
> Provides a value-added service to prevent unintended viewing of objectionable content that exploits underage children. Content Filtering offers mobile operators a way to increase data ARPU and subscriber retention through a network-based solution for parental controls and content filtering. The Content Filtering ICAP solution is appropriate for operators with existing installations of Active Content Filtering servers in their networks.
> The Enhanced Charging Service (ECS) for the P-GW provides a streamlined Internet Content Adaptation Protocol (ICAP) interface to leverage the Deep Packet Inspection (DPI) to enable external Application Servers to provide their services without performing the DPI functionality and without being inserted in the data flow. The ICAP interface may be attractive to mobile operators that prefer to use an external Active Content Filtering (ACF) Platform. If a subscriber initiates a WAP (WAP1.x or WAP2.0) or Web session, the subsequent GET/POST request is detected by the deep packet inspection function. The URL of the GET/POST request is extracted by the local DPI engine on the ASR 5x00 platform and passed, along with subscriber identification information and the subscriber request, in an ICAP message to the Application Server (AS). The AS checks the URL on the basis of its category and other classifications like, type, access level, content category and decides if the request should be authorized, blocked or redirected by answering the GET/POST message. Depending upon the response received from the ACF server, the P-GW either passes the request unmodified or discards the message and responds to the subscriber with the appropriate redirection or block message.
> Header Enrichment: Header Insertion and Encryption
> Header enrichemt provides a value-added capability for mobile operators to monetize subscriber intelligence to include subscriber-specific information in the HTTP requests to application servers.
> Extension header fields (x-header) are the fields that can be added to headers of a protocol for a specific purpose. The enriched header allows additional entity-header fields to be defined without changing the protocol, but these fields cannot be assumed to be recognizable by the recipient. Unrecognized fields should be ignored by the recipient and must be forwarded by transparent proxies.
> Extension headers can be supported in HTTP/WSP GET and POST request packets. The Enhanced Charging Service (ECS) for the P-GW offers APN-based configuration and rules to insert x-headers in HTTP/WSP GET and POST request packets. The charging action associated with the rules will contain the list of x-headers to be inserted in the packets. Protocols supported are HTTP, WAP 1.0 and WAP 2.0 GET, and POST messages.
> Important: For more information on ECS, see the Enhanced Charging Service Administration Guide.
> The data passed in the inserted HTTP header attributes is used by end application servers (also known as Upsell Servers) to identify subscribers and session information. These servers provide information customized to that specific subscriber.
> The Cisco P-GW can include the following information in the http header:

> • | User-customizable, arbitrary text string

> • | Suscriber‘s MSISDN (the RADIUS calling-station-id, in clear text)

> • | Subscriber‘s IMSI

> • | Subscriber‘s IP address

> • | S-GW IP address (in clear text)

> X-Header encryption enhances the header enrichment feature by increasing the number of fields that can be supported and through encryption of the fields before inserting them.
> The following limitations to insertion of x-header fields in WSP headers apply:

> • | x-header fields are not inserted in IP fragmented packets.

> • | In case of concatenated request, x-header fields are only inserted in first GET or POST request (if rule matches for the same). X-header fields are not inserted in the second or later GET/POST requests in the concatenated requests. For example, if there is ACK+GET in packet, x-header is inserted in the GET packet. However, if GET1+GET2 is present in the packet and rule matches for GET2 and not GET1 x-header is still inserted in GET2. In case of GET+POST also, x-header is not inserted in POST.

> • | In case of CO, x-header fields are not inserted if the WTP packets are received out of order (even after proper reordering).

> • | If route to MMS is present, x-headers are not inserted.

> • | x-headers are not inserted in WSP POST packet when header is segmented. This is because POST contains header length field which needs to be modified after addition of x-headers. In segmented WSP headers, header length field may be present in one packet and header may complete in another packet.

> Mobile Video Gateway
> The Cisco ASR 5x00 chassis provides mobile operators with a flexible solution that functions as a Mobile Video Gateway in 2.5G, 3G, and 4G wireless data networks.
> The Cisco Mobile Video Gateway consists of new software for the ASR 5x00. The Mobile Video Gateway is the central component of the Cisco Mobile Videoscape. It employs a number of video optimization techniques that enable mobile operators to enhance the video experience for their subscribers while optimizing the performance of video content transmission through the mobile network.
> The Mobile Video Gateway features and functions include:

> • | DPI (Deep Packet Inspection) to identify subscriber requests for video vs. non-video content

> • | Transparent video re-addressing to the Cisco CAE (Content Adaptation Engine) for retrieval of optimized video content

> • | CAE load balancing of HTTP video requests among the CAEs in the server cluster

> • | Video optimization policy control for tiered subscriber services

> • | Video white-listing, which excludes certain video clips from video optimization

> • | Video pacing for “just in time” video downloading

> • | TCP link monitoring

> • | Dynamic inline transrating

> • | Dynamically-enabled TCP proxy

> • | Traffic performance optimization

> • | N+1 redundancy support

> • | SNMP traps and alarms (threshold crossing alerts)

> • | Mobile video statistics

> • | Bulk statistics for mobile video

> The Cisco CAE is an optional component of the Cisco Mobile Videoscape. It runs on the Cisco UCS (Unified Computing System) platform and functions in a UCS server cluster to bring additional video optimization capabilities to the Mobile Videoscape. For information about the features and functions of the Cisco CAE, see the CAE product documentation.
> Important: For more information on the Mobile Video Gateway, refer to the Mobile Video Gateway Administration Guide.
> Network Address Translation (NAT)
> NAT translates non-routable private IP address(es) to routable public IP address(es) from a pool of public IP addresses that have been designated for NAT. This enables to conserve on the number of public IP addresses required to communicate with external networks, and ensures security as the IP address scheme for the internal network is masked from external hosts, and each outgoing and incoming packet goes through the translation process.
> NAT works by inspecting both incoming and outgoing IP datagrams and, as needed, modifying the source IP address and port number in the IP header to reflect the configured NAT address mapping for outgoing datagrams. The reverse NAT translation is applied to incoming datagrams.
> NAT can be used to perform address translation for simple IP and mobile IP. NAT can be selectively applied/denied to different flows (5-tuple connections) originating from subscribers based on the flows' L3/L4 characteristics—Source-IP, Source-Port, Destination-IP, Destination-Port, and Protocol.
> NAT supports the following mappings:

> • | One-to-One

> • | Many-to-One

> Important: For more information on NAT, refer to the Network Address Translation Administration Guide.
> NAT64 Support
> This feature helps facilitate the co-existence and gradual transition to IPv6 addressingscheme in the networks.
> With the dwindling IPv4 public address space and the growing need for more routable addresses, service providers and enterprises will continue to build and roll out IPv6 networks. However, because of the broad scale IPv4 deployment, it is not practical that the world changes to IPv6 overnight. There is need to protect the IPv4 investment combined with the need to expand and grow the network will force IPv4 and IPv6 networks to co-exist together for a considerable period of time and keep end-user experience seamless.
> The preferred approaches are to run dual stacks (both IPv4 and IPv6) on the end hosts, dual stack routing protocols, and dual stack friendly applications. If all of the above is available, then the end hosts will communicate natively using IPv6 or IPv4 (using NAT). Tunneling through the IPv4 or IPv6 is the next preferred method to achieve communication wherever possible. When all these options fail, translation is recommended.
> Stateful NAT64 is a mechanism for translating IPv6 packets to IPv4 packets and vice-versa. The system supports a Stateful NAT64 translator based on IETF Behave WG drafts whose framework is described in draft-ietf-behave-v6v4-framework-10. Stateful NAT64 is available as part of the existing NAT licenses from the current system implementation. The NAT44 and NAT64 will co-exist on the chassis and share the resources needed for NATing.
> Peer-to-Peer Detection
> Allows operators to identify P2P traffic in the network and applying appropriate controlling functions to ensure fair distribution of bandwidth to all subscribers.
> Peer-to-Peer (P2P) is a term used in two slightly different contexts. At a functional level, it means protocols that interact in a peering manner, in contrast to client-server manner. There is no clear differentiation between the function of one node or another. Any node can function as a client, a server, or both—a protocol may not clearly differentiate between the two. For example, peering exchanges may simultaneously include client and server functionality, sending and receiving information.
> Detecting peer-to-peer protocols requires recognizing, in real time, some uniquely identifying characteristic of the protocols. Typical packet classification only requires information uniquely typed in the packet header of packets of the stream(s) running the particular protocol to be identified. In fact, many peer-to-peer protocols can be detected by simple packet header inspection. However, some P2P protocols are different, preventing detection in the traditional manner. This is designed into some P2P protocols to purposely avoid detection. The creators of these protocols purposely do not publish specifications. A small class of P2P protocols is stealthier and more challenging to detect. For some protocols no set of fixed markers can be identified with confidence as unique to the protocol.
> Operators care about P2P traffic because of the behavior of some P2P applications (for example, Bittorrent, Skype, and eDonkey). Most P2P applications can hog the network bandwidth such that 20% P2P users can generate as much as traffic generated by the rest 80% non-P2P users. This can result into a situation where non-P2P users may not get enough network bandwidth for their legitimate use because of excess usage of bandwidth by the P2P users. Network operators need to have dynamic network bandwidth / traffic management functions in place to ensure fair distributions of the network bandwidth among all the users. And this would include identifying P2P traffic in the network and applying appropriate controlling functions to the same (for example, content-based premium billing, QoS modifications, and other similar treatments).
> Cisco’s P2P detection technology makes use of innovative and highly accurate protocol behavioral detection techniques.
> Important: For more information on peer-to-peer detection, refer to the Application Detection and Control Administration Guide.
> Personal Stateful Firewall
> The Personal Stateful Firewall is an in-line service feature that inspects subscriber traffic and performs IP session-based access control of individual subscriber sessions to protect the subscribers from malicious security attacks.
> The Personal Stateful Firewall supports stateless and stateful inspection and filtering based on the configuration.
> In stateless inspection, the firewall inspects a packet to determine the 5-tuple—source and destination IP addresses and ports, and protocol—information contained in the packet. This static information is then compared against configurable rules to determine whether to allow or drop the packet. In stateless inspection the firewall examines each packet individually, it is unaware of the packets that have passed through before it, and has no way of knowing if any given packet is part of an existing connection, is trying to establish a new connection, or is a rogue packet.
> In stateful inspection, the firewall not only inspects packets up through the application layer / layer 7 determining a packet's header information and data content, but also monitors and keeps track of the connection's state. For all active connections traversing the firewall, the state information, which may include IP addresses and ports involved, the sequence numbers and acknowledgement numbers of the packets traversing the connection, TCP packet flags, etc. is maintained in a state table. Filtering decisions are based not only on rules but also on the connection state established by prior packets on that connection. This enables to prevent a variety of DoS, DDoS, and other security violations. Once a connection is torn down, or is timed out, its entry in the state table is discarded.
> The Enhanced Charging Service (ECS) / Active Charging Service (ACS) in-line service is the primary vehicle that performs packet inspection and charging. For more information on ECS, see the Enhanced Charging Service Administration Guide.
> Important: For more information on Personal Stateful Firewall, refer to the Personal Stateful Firewall Administration Guide.
> Traffic Performance Optimization (TPO)
> Though TCP is a widely accepted protocol in use today, it is optimized only for wired networks. Due to inherent reliability of wired networks, TCP implicitly assumes that any packet loss is due to network congestion and consequently invokes congestion control measures. However, wireless links are known to experience sporadic and usually temporary losses due to several reasons, including the following, which also trigger TCP congestion control measures resulting in poor TCP performance.
> Reasons for delay variability over wireless links include:

> • | Channel fading effect, subscriber mobility, and other transient conditions

> • | Link-layer retransmissions

> • | Handoffs between neighboring cells

> • | Intermediate nodes, such as SGSN and e-NodeB, implementing scheduling polices tuned to deliver better QoS for select services; resulting is variable delay in packet delivery for other services

> The TPO inline service uses a combination of TCP and HTTP optimization techniques to improve TCP performance over wireless links.
> Important: For more information on TPO, refer to the Traffic Performance Optimization Administration Guide.
> Features and Functionality - External Application Support
> This section describes the features and functions of external applications supported on the P-GW. These services require additional licenses to implement the functionality.
> This section describes the following feature(s):

> • | Web Element Management System

> Web Element Management System
> Provides a graphical user interface (GUI) for performing fault, configuration, accounting, performance, and security (FCAPS) management of the ASR 5x00.
> The Web Element Manager is a Common Object Request Broker Architecture (CORBA)-based application that provides complete fault, configuration, accounting, performance, and security (FCAPS) management capability for the system.
> For maximum flexibility and scalability, the Web Element Manager application implements a client-server architecture. This architecture allows remote clients with Java-enabled web browsers to manage one or more 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.
> Web Element Manager Network Interfaces
> Important: For more information on WEM support, refer to the WEM Installation and Administration Guide.
> Features and Functionality - Optional Enhanced Feature Software
> This section describes the optional enhanced features and functions for the P-GW service.
> Each of the following features requires the purchase of an additional license to implement the functionality with the P-GW service.
> Important: For information on installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations chapter in the System Administration Guide.
> This section describes the following features:

> • | Always-On Licensing

> • | GRE Protocol Interface Support

> • | Inter-Chassis Session Recovery

> • | IP Security (IPSec) Encryption

> • | L2TP LAC Support

> • | Lawful Intercept

> • | Layer 2 Traffic Management (VLANs)

> • | Local Policy Decision Engine

> • | MPLS Forwarding with LDP

> • | NEMO Service Supported

> • | Session Recovery Support

> • | Smartphone Tethering Detection Support

> • | Traffic Policing and Shaping

> • | User Location Information Reporting

> Always-On Licensing
> Use of Always On Licensing requires that a valid license key be installed. Contact your Cisco account representative for information on how to obtain a license.
> Traditionally, transactional models have been based on registered subscriber sessions. In an “always-on” deployment model, however, the bulk of user traffic is registered all of the time. Most of these registered subscriber sessions are idle a majority of the time. Therefore, Always-On Licensing charges only for connected-active subscriber sessions.
> A connected-active subscriber session would be in “ECM Connected state,” as specified in 3GPP TS 23.401, with a data packet sent/received within the last one minute (on average). This transactional model allows providers to better manage and achieve more predictable spending on their capacity as a function of the Total Cost of Ownership (TCO).
> GRE Protocol Interface Support
> Use of GRE Interface Tunneling requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> The P-GW supports GRE generic tunnel interfaces in accordance with RFC 2784, Generic Routing Encapsulation (GRE). The GRE protocol allows mobile users to connect to their enterprise networks through GRE tunnels.
> GRE tunnels can be used by the enterprise customers of a carrier 1) To transport AAA packets corresponding to an APN over a GRE tunnel to the corporate AAA servers and, 2) To transport the enterprise subscriber packets over the GRE tunnel to the corporation gateway.
> The corporate servers may have private IP addresses and hence the addresses belonging to different enterprises may be overlapping. Each enterprise needs to be in a unique virtual routing domain, known as VRF. To differentiate the tunnels between same set of local and remote ends, GRE Key will be used as a differentiation.
> GRE tunneling is a common technique to enable multi-protocol local networks over a single-protocol backbone, to connect non-contiguous networks and allow virtual private networks across WANs. This mechanism encapsulates data packets from one protocol inside a different protocol and transports the data packets unchanged across a foreign network. It is important to note that GRE tunneling does not provide security to the encapsulated protocol, as there is no encryption involved (like IPSec offers, for example).
> GRE tunneling consists of three main components:

> • | Passenger protocol-protocol being encapsulated. For example: CLNS, IPv4 and IPv6.

> • | Carrier protocol-protocol that does the encapsulating. For example: GRE, IP-in-IP, L2TP, MPLS and IPSec.

> • | Transport protocol-protocol used to carry the encapsulated protocol. The main transport protocol is IP.

> Important: For more information on GRE protocol interface support, refer to the GRE Protocol Interface appendix in this guide.
> Inter-Chassis Session Recovery
> Use of Interchassis Session Recovery requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> The ASR 5x00 provides industry leading carrier class redundancy. The systems protects against all single points of failure (hardware and software) and attempts to recover to an operational state when multiple simultaneous failures occur.
> The system provides several levels of system redundancy:

> • | Under normal N+1 PSC/PSC2 hardware redundancy, if a catastrophic packet processing card failure occurs all affected calls are migrated to the standby packet processing card if possible. Calls which cannot be migrated are gracefully terminated with proper call-termination signaling and accounting records are generated with statistics accurate to the last internal checkpoint

> • | If the Session Recovery feature is enabled, any total PSC/PSC2 failure will cause a PSC switchover and all established sessions for supported call-types are recovered without any loss of session.

> Even though Cisco provides excellent intra-chassis redundancy with these two schemes, certain catastrophic failures which can cause total chassis outages, such as IP routing failures, line-cuts, loss of power, or physical destruction of the chassis, cannot be protected by this scheme. In such cases, the MME Inter-Chassis Session Recovery feature provides geographic redundancy between sites. This has the benefit of not only providing enhanced subscriber experience even during catastrophic outages, but can also protect other systems such as the RAN from subscriber re-activation storms.
> The Interchassis Session Recovery feature allows for continuous call processing without interrupting subscriber services. This is accomplished through the use of redundant chassis. The chassis are configured as primary and backup with one being active and one in recovery mode. A checkpoint duration timer is used to control when subscriber data is sent from the active chassis to the inactive chassis. If the active chassis handling the call traffic goes out of service, the inactive chassis transitions to the active state and continues processing the call traffic without interrupting the subscriber session. The chassis determines which is active through a propriety TCP-based connection called a redundancy link. This link is used to exchange Hello messages between the primary and backup chassis and must be maintained for proper system operation.

> • | Interchassis Communication

> Chassis configured to support Interchassis Session Recovery communicate using periodic Hello messages. These messages are sent by each chassis to notify the peer of its current state. The Hello message contains information about the chassis such as its configuration and priority. A dead interval is used to set a time limit for a Hello message to be received from the chassis' peer. If the standby chassis does not receive a Hello message from the active chassis within the dead interval, the standby chassis transitions to the active state. In situations where the redundancy link goes out of service, a priority scheme is used to determine which chassis processes the session. The following priority scheme is used:

> • | router identifier

> • | chassis priority

> • | SPIO MAC address

> • | Checkpoint Messages

> Checkpoint messages are sent from the active chassis to the inactive chassis. Checkpoint messages are sent at specific intervals and contain all the information needed to recreate the sessions on the standby chassis, if that chassis were to become active. Once a session exceeds the checkpoint duration, checkpoint data is collected on the session. The checkpoint parameter determines the amount of time a session must be active before it is included in the checkpoint message.
> Important: For more information on inter-chassis session recovery support, refer to the Interchassis Session Recovery chapter in the System Administration Guide.
> IP Security (IPSec) Encryption
> Use of Network Domain Security requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> IPSec encryption enables network domain security for all IP packet switched LTE-EPC networks in order to provide confidentiality, integrity, authentication, and anti-replay protection. These capabilities are insured through use of cryptographic techniques.
> The Cisco P-GW supports IKEv1 and IPSec encryption using IPv4 addressing. IPSec enables the following two use cases:

> • | Encryption of S8 sessions and EPS bearers in roaming applications where the P-GW is located in a separate administrative domain from the S-GW

> • | IPSec ESP security in accordance with 3GPP TS 33.210 is provided for S1 control plane, S1 bearer plane and S1 management plane traffic. Encryption of traffic over the S1 reference interface is desirable in cases where the EPC core operator leases radio capacity from a roaming partner's network.

> Important: For more information on IPSec support, refer to the IP Security appendix in this guide.
> L2TP LAC Support
> Use of L2TP LAC requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> The system configured as a Layer 2 Tunneling Protocol Access Concentrator (LAC) enables communication with L2TP Network Servers (LNSs) for the establishment of secure Virtual Private Network (VPN) tunnels between the operator and a subscriber's corporate or home network.
> The use of L2TP in VPN networks is often used as it allows the corporation to have more control over authentication and IP address assignment. An operator may do a first level of authentication, however use PPP to exchange user name and password, and use IPCP to request an address. To support PPP negotiation between the P-GW and the corporation, an L2TP tunnel must be setup in the P-GW running a LAC service.
> L2TP establishes L2TP control tunnels between LAC and LNS before tunneling the subscriber PPP connections as L2TP sessions. The LAC service is based on the same architecture as the P-GW and benefits from dynamic resource allocation and distributed message and data processing.
> The LAC sessions can also be configured to be redundant, thereby mitigating any impact of hardware or software issues. Tunnel state is preserved by copying the information across processor cards.
> Important: For more information on this feature support, refer to the L2TP Access Concentrator appendix in this guide.
> Lawful Intercept
> The feature use license for Lawful Intercept on the P-GW is included in the P-GW session use license.
> The Cisco Lawful Intercept feature is supported on the P-GW. Lawful Intercept is a licensed-enabled, standards-based feature that provides telecommunications service providers with a mechanism to assist law enforcement agencies in monitoring suspicious individuals for potential illegal activity. For additional information and documentation on the Lawful Intercept feature, contact your Cisco account representative.
> Layer 2 Traffic Management (VLANs)
> Use of Layer 2 Traffic Management requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> Virtual LANs (VLANs) 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.
> Important: For more information on VLAN support, refer to the VLANs chapter in the System Administration Guide.
> Local Policy Decision Engine
> Use of the Local Policy Decision Engine requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> The Local Policy Engine is an event-driven rules engine that offers Gx-like QoS and policy controls to enable user or application entitlements. As the name suggests, it is designed to provide a subset of a PCRF in cases where an operator elects not to use a PCRF or scenarios where connections to an external PCRF are disrupted. Local policies are used to control different aspects of a session like QoS, data usage, subscription profiles, and server usage by means of locally defined policies. A maximum of 1,024 local policies can be provisioned on a P-GW system.
> Local policies are triggered when certain events occur and the associated conditions are satisfied. For example, when a new call is initiated, the QoS to be applied for the call could be decided based on the IMSI, MSISDN, and APN.
> Potential uses cases for the Local Policy Decision Engine include:

> • | Disaster recovery data backup solution in the event of a loss of PCRF in a mobile core network.

> • | Dedicated bearer establishment for emergency voice calls.

> • | Network-initiated bearer establishment on LTE to non-3GPP inter-domain handovers.

> Important: For more information on configuring the Local Policy Decision Engine, refer to the Configuring Local QoS Policy section in the PDN Gateway Configuration chapter of this guide.
> MPLS Forwarding with LDP
> Use of MPLS requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> Multi Protocol Label Switching (MPLS) is an operating scheme or a mechanism that is used to speed up the flow of traffic on a network by making better use of available network paths. It works with the routing protocols like BGP and OSPF, and therefore it is not a routing protocol.
> MPLS generates a fixed-length label to attach or bind with the IP packet's header to control the flow and destination of data. The binding of the labels to the IP packets is done by the label distribution protocol (LDP). All the packets in a forwarding equivalence class (FEC) are forwarded by a label-switching router (LSR), which is also called an MPLS node. The LSR uses the LDP in order to signal its forwarding neighbors and distribute its labels for establishing a label switching path (LSP).
> In order to support the increasing number of corporate APNs, which have a number of different addressing models and requirements, MPLS is deployed to fulfill at least the following two requirements:

> • | The corporate APN traffic must remain segregated from other APNs for security reasons.

> • | Overlapping of IP addresses in different APNs.

> When deployed, the MPLS backbone automatically negotiates routes using the labels binded with the IP packets. Cisco P-GW as an LSR learns the default route from the connected provider edge (PE), while the PE populates its routing table with the routes provided by the P-GW.
> Important: For more information on MPLS support, refer to the Multi-Protocol Label Switching (MPLS) Support appendix in this guide.
> NEMO Service Supported
> Use of NEMO requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> The P-GW may be configured to enable or disable Network Mobility (NEMO) service.
> When enabled, the system includes NEMO support for a Mobile IPv4 Network Mobility (NEMO-HA) on the P-GW platform to terminate Mobile IPv4 based NEMO connections from Mobile Routers (MRs) that attach to an Enterprise PDN. The NEMO functionality allows bi-directional communication that is application-agnostic between users behind the MR and users or resources on Fixed Network sites.
> The same NEMO4G-HA service and its bound Loopback IP address supports NEMO connections whose underlying PDN connection comes through GTP S5 (4G access) or PMIPv6 S2a (eHRPD access).
> Important: For more information on NEMO support, refer to the Network Mobility (NEMO) chapter in this guide.
> Session Recovery Support
> The feature use license for Session Recovery on the P-GW is included in the P-GW session use license.
> Session recovery 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.
> In the telecommunications industry, over 90 percent of all equipment failures are software-related. With robust hardware failover and redundancy protection, any card-level hardware failures on the system can quickly be corrected. However, software failures can occur for numerous reasons, many times without prior indication. StarOS Release 9.0 adds the ability to support stateful intra-chassis session recovery for P-GW sessions.
> When session recovery occurs, the system reconstructs the following subscriber information:

> • | Data and control state information required to maintain correct call behavior

> • | Subscriber data statistics that are required to ensure that accounting information is maintained

> • | A best-effort attempt to recover various timer values such as call duration, absolute time, and others

> Session recovery is also useful for in-service software patch upgrade activities. If session recovery is enabled during the software patch upgrade, it helps to preserve existing sessions on the active PSC/PSC2 during the upgrade process.
> Important: For more information on session recovery support, refer to the Session Recovery chapter in the System Administration Guide.
> Smartphone Tethering Detection Support
> Use of Smartphone Tethering Detection requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> On the P-GW, using the inline heuristic detection mechanism, it is now possible to detect and differentiate between the traffic from the mobile device and a tethered device connected to the mobile device.
> Traffic Policing and Shaping
> Use of Per-Subscriber Traffic Policing/Shaping requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> Traffic policing and shaping allows you to manage bandwidth usage on the network and limit bandwidth allowances to subscribers. Shaping allows you to buffer excesses to be delivered at a later time.
> Traffic Policing
> Traffic policing enables the configuring and enforcing of bandwidth limitations on individual subscribers and/or APNs of a particular traffic class in 3GPP/3GPP2 service.
> Bandwidth enforcement is configured and enforced independently on the downlink and the uplink directions.
> A Token Bucket Algorithm (a modified trTCM) [RFC2698] is used to implement the Traffic-Policing feature. The algorithm used measures the following criteria when determining how to mark a packet:

> • | Committed Data Rate (CDR): The guaranteed rate (in bits per second) at which packets can be transmitted/received for the subscriber during the sampling interval.

> • | Peak Data Rate (PDR): The maximum rate (in bits per second) that subscriber packets can be transmitted/received for the subscriber during the sampling interval.

> • | Burst-size: The maximum number of bytes that can be transmitted/received for the subscriber during the sampling interval for both committed (CBS) and peak (PBS) rate conditions. This represents the maximum number of tokens that can be placed in the subscriber’s “bucket”. Note that the committed burst size (CBS) equals the peak burst size (PBS) for each subscriber.

> The system can be configured to take any of the following actions on packets that are determined to be in excess or in violation:

> • | Drop: The offending packet is discarded.

> • | Transmit: The offending packet is passed.

> • | Lower the IP Precedence: The packet’s ToS bit is set to “0”, thus downgrading it to Best Effort, prior to passing the packet. Note that if the packet’s ToS bit was already set to “0”, this action is equivalent to “Transmit”.

> Traffic Shaping
> Traffic Shaping is a rate limiting method similar to the Traffic Policing, but provides a buffer facility for packets exceeded the configured limit. Once the packet exceeds the data-rate, the packet queued inside the buffer to be delivered at a later time.
> The bandwidth enforcement can be done in the downlink and the uplink direction independently. If there is no more buffer space available for subscriber data system can be configured to either drop the packets or kept for the next scheduled traffic session.
> Important: For more information on traffic policing and shaping, refer to the Traffic Policing and Shaping appendix in this guide.
> User Location Information Reporting
> Use of User Location Information (ULI) Reporting requires that a valid license key be installed. Contact your local Sales or Support representative for information on how to obtain a license.
> ULI Reporting allows the eNodeB to report the location of a UE to the MME, when requested by a P-GW.
> The following procedures are used over the S1-MME interface to initiate and stop location reporting between the MME and eNodeB:

> • | Location Reporting Control: The purpose of Location Reporting Control procedure is to allow the MME to request that the eNodeB report where the UE is currently located. This procedure uses UE-associated signaling.

> • | Location Report Failure Indication: The Location Report Failure Indication procedure is initiated by an eNodeB in order to inform the MME that a Location Reporting Control procedure has failed. This procedure uses UE-associated signalling.

> • | Location Report: The purpose of Location Report procedure is to provide the UE's current location to the MME. This procedure uses UE-associated signalling.

> The start/stop trigger for location reporting for a UE is reported to the MME by the S-GW over the S11 interface. The Change Reporting Action (CRA) Information Element (IE) is used for this purpose. The MME updates the location to the S-GW using the User Location Information (ULI) IE.
> The following S11 messages are used to transfer CRA and ULI information between the MME and S-GW:

> • | Create Session Request: The ULI IE is included for E-UTRAN Initial Attach and UE-requested PDN Connectivity procedures. It includes ECGI and TAI. The MME includes the ULI IE for TAU/ X2-Handover procedure if the P-GW has requested location information change reporting and the MME support location information change reporting. The S-GW includes the ULI IE on S5/S8 exchanges if it receives the ULI from the MME. If the MME supports change reporting, it sets the corresponding indication flag in the Create Session Request message.

> • | Create Session Response: The CRA IE in the Create Session Response message can be populated by the S-GW to indicate the type of reporting required.

> • | Create Bearer Request: The CRA IE is included with the appropriate Action field if the Location Change Reporting mechanism is to be started or stopped for the subscriber in the MME.

> • | Modify Bearer Request: The MME includes the ULI IE for TAU/Handover procedures and UE-initiated Service Request procedures if the P-GW has requested location information change reporting and the MME supports location information change reporting. The S-GW includes this IE on S5/S8 exchanges if it receives the ULI from the MME.

> • | Modify Bearer Response: The CRA IE is included with the appropriate Action field if the Location Change Reporting mechanism is to be started or stopped for the subscriber in the MME.

> • | Delete Session Request: The MME includes the ULI IE for the Detach procedure if the P-GW has requested location information change reporting and MME supports location information change reporting. The S-GW includes this IE on S5/S8 exchanges if it receives the ULI from the MME.

> • | Update Bearer Request: The CRA IE is included with the appropriate Action field if the Location Change Reporting mechanism is to be started or stopped for the subscriber in the MME.

> • | Change Notification Request: If no existing procedure is running for a UE, a Change Notification Request is sent upon receipt of an S1-AP location report message. If an existing procedure is running, one of the following messages reports the ULI:

> • | Create Session Request

> • | Create Bearer Response

> • | Modify Bearer Request

> • | Update Bearer Response

> • | Delete Bearer Response

> • | Delete Session Request

> If an existing Change Notification Request is pending, it is aborted and a new one is sent.
> Important: Information on configuring User Location Information (ULI) Reporting support is located in the Configuring Optional Features on the MME section of the Mobility Management Entity Configuration chapter in the Mobility Management Entity Administration Guide.
> How the PDN Gateway Works
> This section provides information on the function of the P-GW in an EPC E-UTRAN network and presents call procedure flows for different stages of session setup and disconnect.
> The P-GW supports the following network flows:

> • | PMIPv6 PDN Gateway Call Session Procedures in an eHRPD Network

> • | GTP PDN Gateway Call Session Procedures in an LTE-SAE Network

> PMIPv6 PDN Gateway Call/Session Procedures in an eHRPD Network
> The following topics and procedure flows are included:

> • | Initial Attach with IPv6IPv4 Access

> • | PMIPv6 Lifetime Extension without Handover

> • | PDN Connection Release Initiated by UE

> • | PDN Connection Release Initiated by HSGW

> • | PDN Connection Release Initiated by P-GW

> Initial Attach with IPv6/IPv4 Access
> This section describes the procedure of initial attach and session establishment for a subscriber (UE).
> Initial Attach with IPv6/IPv4 Access Call Flow
> Initial Attach with IPv6/IPv4 Access Call Flow Description

> Step | Description
> 1 | The subscriber (UE) attaches to the eHRPD network.
> 2a | The eAN/PCF sends an A11 RRQ to the HSGW. The eAN/PCF includes the true IMSI of the UE in the A11 RRQ.
> 2b | The HSGW establishes A10s and respond back to the eAN/PCF with an A11 RRP.
> 3a | The UE performs LCP negotiation with the HSGW over the established main A10.
> 3b | The UE performs EAP over PPP.
> 3c | EAP authentication is completed between the UE and the 3GPP AAA. During this transaction, the HSGW receives the subscriber profile from the AAA server.
> 4a | After receiving the subscriber profile, the HSGW sends the QoS profile in A11 Session Update Message to the eAN/PCF.
> 4b | The eAN/PCF responds with an A11 Session Update Acknowledgement (SUA).
> 5a | The UE initiates a PDN connection by sending a PPP-VSNCP-Conf-Req message to the HSGW. The message includes the PDNID of the PDN, APN, PDN-Type=IPv6/[IPv4], PDSN-Address and, optionally, PCO options the UE is expecting from the network.
> 5b | The HSGW sends a PBU to the P-GW.
> 5c | The P-GW processes the PBU from the HSGW, assigns an HNP for the connection and responds back to the HSGW with PBA.
> 5d | The HSGW responds to the VSNCP Conf Req with a VSNCP Conf Ack.
> 5e | The HSGW sends a PPP-VSNCP-Conf-Req to the UE to complete PPP VSNCP negotiation.
> 5f | The UE completes VSNCP negotiation by returning a PPP-VSNCP-Conf-Ack.
> 6 | The UE optionally sends a Router Solicitation (RS) message.
> 7 | The HSGW sends a Router Advertisement (RA) message with the assigned Prefix.

> ‌
> PMIPv6 Lifetime Extension without Handover
> This section describes the procedure of a session registration lifetime extension by the P-GW without the occurrence of a handover.
> PMIPv6 Lifetime Extension (without handover) Call Flow
> PMIPv6 Lifetime Extension (without handover) Call Flow Description

> Step | Description
> 1 | The UE is attached to the EPC and has a PDN connection with the P-GW where PDNID=x and an APN with assigned HNP.
> 2 | The HSGW MAG service registration lifetime nears expiration and triggers a renewal request for the LMA.
> 3 | The MAG service sends a Proxy Binding Update (PBU) to the P-GW LMA service with the following attributes: Lifetime, MNID, APN, ATT=HRPD, HNP.
> 4 | The P-GW LMA service updates the Binding Cache Entry (BCE) with the new granted lifetime.
> 5 | The P-GW responds with a Proxy Binding Acknowledgement (PBA) with the following attributes: Lifetime, MNID, APN.

> ‌
> PDN Connection Release Initiated by UE
> This section describes the procedure of a session release by the UE.
> PDN Connection Release by the UE Call Flow
> PDN Connection Release by the UE Call Flow Description

> Step | Description
> 1 | The UE is attached to the EPC and has a PDN connection with the P-GW for PDN-ID=x and APN with assigned HNP.
> 2 | The UE decides to disconnect from the PDN and sends a PPP VSNCP-Term-Req with PDNID=x.
> 3 | The HSGW starts disconnecting the PDN connection and sends a PPP-VSNCP-Term-Ack to the UE (also with PDNID=x).
> 4 | The HSGW begins the tear down of the PMIP session by sending a PBU Deregistration to the P-GW with the following attributes: Lifetime=0, MNID, APN, ATT=HRPD, HNP. The PBU Deregistration message should contain all the mobility options that were present in the initial PBU that created the binding.
> 5 | The P-GW looks up the Binding Cache Entry (BCE) based on the HNP, deletes the binding, and responds to the HSGW with a Deregistration PBA with the same attributes (Lifetime=0, MNID, APN, ATT=HRPD, HNP).
> 6 | The HSGW optionally sends a Router Advertisement (RA) with assigned HNP and prefix lifetime=0.

> ‌
> PDN Connection Release Initiated by HSGW
> This section describes the procedure of a session release by the HSGW.
> PDN Connection Release by the HSGW Call Flow
> PDN Connection Release by the HSGW Call Flow Description

> Step | Description
> 1 | The UE is attached to the EPC and has a PDN connection with the P-GW for PDN-ID=x and APN with assigned HNP.
> 2 | The HSGW MAG service triggers a disconnect of the PDN connection for PDNID=x.
> 3 | The HSGW sends a PPP VSNCP-Term-Req with PDNID=x to the UE.
> 4 | The UE acknowledges the receipt of the request with a VSNCP-Term-Ack (PDNID=x).
> 5 | The HSGW begins the tear down of the PMIP session by sending a PBU Deregistration to the P-GW with the following attributes: Lifetime=0, MNID, APN, HNP. The PBU Deregistration message should contain all the mobility options that were present in the initial PBU that created the binding.
> 6 | The P-GW looks up the BCE based on the HNP, deletes the binding, and responds to the HSGW with a Deregistration PBA with the same attributes (Lifetime=0, MNID, APN, ATT=HRPD, HNP).
> 7 | The HSGW optionally sends a Router Advertisement (RA) with assigned HNP and prefix lifetime=0.

> ‌
> PDN Connection Release Initiated by P-GW
> This section describes the procedure of a session release by the P-GW.
> PDN Connection Release by the P-GW Call Flow
> PDN Connection Release by the P-GW Call Flow Description

> Step | Description
> 1 | The UE is attached to the EPC and has a PDN connection with the P-GW for PDN-ID=x and APN with assigned HNP.
> 2 | A PGW trigger causes a disconnect of the PDN connection for PDNID=x and the PGW sends a Binding Revocation Indication (BRI) message to the HSGW with the following attributes: MNID, APN, HNP.
> 3 | The HSGW responds to the BRI message with a Binding Revocation Acknowledgement (BRA) message with the sane attributes (MNID, APN, HNP).
> 4 | The HSGW MAG service triggers a disconnect of the UE PDN connection for PDNID=x.
> 5 | The HSGW sends a PPP VSNCP-Term-Req with PDNID=x to the UE.
> 6 | The UE acknowledges the receipt of the request with a VSNCP-Term-Ack (PDNID=x).
> 7 | The HSGW optionally sends a Router Advertisement (RA) with assigned HNP and prefix lifetime=0.

> ‌
> GTP PDN Gateway Call/Session Procedures in an LTE-SAE Network
> The following topics and procedure flows are included:

> • | Subscriber-initiated Attach (initial)

> • | Subscriber-initiated Detach

> Subscriber-initiated Attach (initial)
> This section describes the procedure of an initial attach to the EPC network by a subscriber.
> Subscriber-initiated Attach (initial) Call Flow
> Subscriber-initiated Attach (initial) Call Flow Description

> Step | Description
> 1 | The UE initiates the Attach procedure by the transmission of an Attach Request (IMSI or old GUTI, last visited TAI (if available), UE Network Capability, PDN Address Allocation, Protocol Configuration Options, Attach Type) message together with an indication of the Selected Network to the eNodeB. IMSI is included if the UE does not have a valid GUTI available. If the UE has a valid GUTI, it is included.
> 2 | The eNodeB derives the MME from the GUTI and from the indicated Selected Network. If that MME is not associated with the eNodeB, the eNodeB selects an MME using an “MME selection function”. The eNodeB forwards the Attach Request message to the new MME contained in a S1-MME control message (Initial UE message) together with the Selected Network and an indication of the E-UTRAN Area identity, a globally unique E-UTRAN ID of the cell from where it received the message to the new MME.
> 3 | If the UE is unknown in the MME, the MME sends an Identity Request to the UE to request the IMSI.
> 4 | The UE responds with Identity Response (IMSI).
> 5 | If no UE context for the UE exists anywhere in the network, authentication is mandatory. Otherwise this step is optional. However, at least integrity checking is started and the ME Identity is retrieved from the UE at Initial Attach. The authentication functions, if performed this step, involves AKA authentication and establishment of a NAS level security association with the UE in order to protect further NAS protocol messages.
> 6 | The MME sends an Update Location (MME Identity, IMSI, ME Identity) to the HSS.
> 7 | The HSS acknowledges the Update Location message by sending an Update Location Ack to the MME. This message also contains the Insert Subscriber Data (IMSI, Subscription Data) Request. The Subscription Data contains the list of all APNs that the UE is permitted to access, an indication about which of those APNs is the Default APN, and the 'EPS subscribed QoS profile' for each permitted APN. If the Update Location is rejected by the HSS, the MME rejects the Attach Request from the UE with an appropriate cause.
> 8 | The MME selects an S-GW using “Serving GW selection function” and allocates an EPS Bearer Identity for the Default Bearer associated with the UE. If the PDN subscription context contains no P-GW address the MME selects a P-GW as described in clause “PDN GW selection function”. Then it sends a Create Default Bearer Request (IMSI, MME Context ID, APN, RAT type, Default Bearer QoS, PDN Address Allocation, AMBR, EPS Bearer Identity, Protocol Configuration Options, ME Identity, User Location Information) message to the selected S-GW.
> 9 | The S-GW creates a new entry in its EPS Bearer table and sends a Create Default Bearer Request (IMSI, APN, S-GW Address for the user plane, S-GW TEID of the user plane, S-GW TEID of the control plane, RAT type, Default Bearer QoS, PDN Address Allocation, AMBR, EPS Bearer Identity, Protocol Configuration Options, ME Identity, User Location Information) message to the P-GW.
> 10 | If dynamic PCC is deployed, the P-GW interacts with the PCRF to get the default PCC rules for the UE. The IMSI, UE IP address, User Location Information, RAT type, AMBR are provided to the PCRF by the P-GW if received by the previous message.
> 11 | The P-GW returns a Create Default Bearer Response (P-GW Address for the user plane, P-GW TEID of the user plane, P-GW TEID of the control plane, PDN Address Information, EPS Bearer Identity, Protocol Configuration Options) message to the S-GW. PDN Address Information is included if the P-GW allocated a PDN address Based on PDN Address Allocation received in the Create Default Bearer Request. PDN Address Information contains an IPv4 address for IPv4 and/or an IPv6 prefix and an Interface Identifier for IPv6. The P-GW takes into account the UE IP version capability indicated in the PDN Address Allocation and the policies of operator when the P-GW allocates the PDN Address Information. Whether the IP address is negotiated by the UE after completion of the Attach procedure, this is indicated in the Create Default Bearer Response.
> 12 | The Downlink (DL) Data can start flowing towards S-GW. The S-GW buffers the data.
> 13 | The S-GW returns a Create Default Bearer Response (PDN Address Information, S-GW address for User Plane, S-GW TEID for User Plane, S-GW Context ID, EPS Bearer Identity, Protocol Configuration Options) message to the new MME. PDN Address Information is included if it was provided by the P-GW.
> 14 | The new MME sends an Attach Accept (APN, GUTI, PDN Address Information, TAI List, EPS Bearer Identity, Session Management Configuration IE, Protocol Configuration Options) message to the eNodeB.
> 15 | The eNodeB sends Radio Bearer Establishment Request including the EPS Radio Bearer Identity to the UE. The Attach Accept message is also sent along to the UE.
> 16 | The UE sends the Radio Bearer Establishment Response to the eNodeB. In this message, the Attach Complete message (EPS Bearer Identity) is included.
> 17 | The eNodeB forwards the Attach Complete (EPS Bearer Identity) message to the MME.
> 18 | The Attach is complete and UE sends data over the default bearer. At this time the UE can send uplink packets towards the eNodeB which are then tunnelled to the S-GW and P-GW.
> 19 | The MME sends an Update Bearer Request (eNodeB address, eNodeB TEID) message to the S-GW.
> 20 | The S-GW acknowledges by sending Update Bearer Response (EPS Bearer Identity) message to the MME.
> 21 | The S-GW sends its buffered downlink packets.
> 22 | After the MME receives Update Bearer Response (EPS Bearer Identity) message, if an EPS bearer was established and the subscription data indicates that the user is allowed to perform handover to non-3GPP accesses, and if the MME selected a P-GW that is different from the P-GW address which was indicated by the HSS in the PDN subscription context, the MME sends an Update Location Request including the APN and P-GW address to the HSS for mobility with non-3GPP accesses.
> 23 | The HSS stores the APN and P-GW address pair and sends an Update Location Response to the MME.
> 24 | Bidirectional data is passed between the UE and PDN.

> ‌
> Subscriber-initiated Detach
> This section describes the procedure of detachment from the EPC network by a subscriber.
> Subscriber-initiated Detach Call Flow
> Subscriber-initiated Detach Call Flow Description

> Step | Description
> 1 | The UE sends NAS message Detach Request (GUTI, Switch Off) to the MME. Switch Off indicates whether detach is due to a switch off situation or not.
> 2 | The active EPS Bearers in the S-GW regarding this particular UE are deactivated by the MME sending a Delete Bearer Request (TEID) message to the S-GW.
> 3 | The S-GW sends a Delete Bearer Request (TEID) message to the P-GW.
> 4 | The P-GW acknowledges with a Delete Bearer Response (TEID) message.
> 5 | The P-GW may interact with the PCRF to indicate to the PCRF that EPS Bearer is released if PCRF is applied in the network.
> 6 | The S-GW acknowledges with a Delete Bearer Response (TEID) message.
> 7 | If Switch Off indicates that the detach is not due to a switch off situation, the MME sends a Detach Accept message to the UE.
> 8 | The MME releases the S1-MME signalling connection for the UE by sending an S1 Release command to the eNodeB with Cause = Detach.

> ‌
> Supported Standards
> The P-GW service complies with the following standards.

> • | Release 9 3GPP References

> • | Release 8 3GPP References

> • | 3GPP2 References

> • | IETF References

> • | Object Management Group (OMG) Standards

> Release 9 3GPP References
> Important: The P-GW currently supports the following Release 9 3GPP specifications. Most 3GPP specifications are also used for 3GPP2 support; any specifications that are unique to 3GPP2 are listed under 3GPP2 References.

> • | 3GPP TR 21.905: Vocabulary for 3GPP Specifications

> • | 3GPP TS 22.115: Service aspects; Charging and billing

> • | 3GPP TS 23.003: Numbering, addressing and identification

> • | 3GPP TS 23.007: Restoration procedures

> • | 3GPP TS 23.060. General Packet Radio Service (GPRS); Service description; Stage 2

> • | 3GPP TS 23.203: Policy and charging control architecture

> • | 3GPP TS 23.207: End-to-end Quality of Service (QoS) concept and architecture

> • | 3GPP TS 23.216: Single Radio Voice Call Continuity (SRVCC); Stage 2

> • | 3GPP TS 23.228: IP Multimedia Subsystem (IMS); Stage 2

> • | 3GPP TS 23.401: General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

> • | 3GPP TS 23.402. Architecture enhancements for non-3GPP accesses

> • | 3GPP TS 24.008: Mobile radio interface Layer 3 specification; Core network protocols

> • | 3GPP TS 29.060: General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface

> • | 3GPP TS 29.061: Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)

> • | 3GPP TS 29.212: Policy and Charging Control over Gx reference point

> • | 3GPP TS 29.214: Policy and Charging control over Rx reference point

> • | 3GPP TS 29.229: Cx and Dx interfaces based on Diameter protocol

> • | 3GPP TS 29.230: Diameter applications; 3GPP specific codes and identifiers

> • | 3GPP TS 29.272: Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol

> • | 3GPP TS 29.273: 3GPP EPS AAA Interfaces

> • | 3GPP TS 29.274: 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3

> • | 3GPP TS 29.275: Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3

> • | 3GPP TS 29.281: General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)

> • | 3GPP TS 29.282: Mobile IPv6 vendor specific option format and usage within 3GPP

> • | 3GPP TS 32.240: Telecommunication management; Charging management; Charging architecture and principles

> • | 3GPP TS 32.251: Telecommunication management; Charging management; Packet Switched (PS) domain charging

> • | 3GPP TS 32.298: Telecommunication management; Charging management; Charging Data Record (CDR) parameter description

> • | 3GPP TS 32.299: Telecommunication management; Charging management; Diameter charging application

> Release 8 3GPP References
> Important: The P-GW currently supports the following Release 8 3GPP specifications. Most 3GPP specifications are also used for 3GPP2 support; any specifications that are unique to 3GPP2 are listed under 3GPP2 References.

> • | 3GPP TR 21.905: Vocabulary for 3GPP Specifications

> • | 3GPP TS 23.003: Numbering, addressing and identification

> • | 3GPP TS 23.007: Restoration procedures

> • | 3GPP TS 23.060. General Packet Radio Service (GPRS); Service description; Stage 2

> • | 3GPP TS 23.107: Quality of Service (QoS) concept and architecture

> • | 3GPP TS 23.203: Policy and charging control architecture

> • | 3GPP TS 23.401: General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

> • | 3GPP TS 23.402. Architecture enhancements for non-3GPP accesses

> • | 3GPP TS 23.869: Support for Internet Protocol (IP) based IP Multimedia Subsystem (IMS) Emergency calls over General Packet Radio Service (GPRS) and Evolved Packet Service (EPS)

> • | 3GPP TS 24.008: Mobile radio interface Layer 3 specification; Core network protocols

> • | 3GPP TS 24.229: IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3

> • | 3GPP TS 27.060: Mobile Station (MS) supporting Packet Switched Services

> • | 3GPP TS 29.061: Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)

> • | 3GPP TS 29.210. Charging rule provisioning over Gx interface

> • | 3GPP TS 29.212: Policy and Charging Control over Gx reference point

> • | 3GPP TS 29.213: Policy and Charging Control signaling flows and QoS

> • | 3GPP TS 29.273: 3GPP EPS AAA Interfaces

> • | 3GPP TS 29.274: Evolved GPRS Tunnelling Protocol for Control plane (GTPv2-C)

> • | 3GPP TS 29.275: Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols

> • | 3GPP TS 29.281: GPRS Tunnelling Protocol User Plane (GTPv1-U)

> • | 3GPP TS 29.282: Mobile IPv6 vendor specific option format and usage within 3GPP

> • | 3GPP TS 32.295: Charging management; Charging Data Record (CDR) transfer

> • | 3GPP TS 32.298: Telecommunication management; Charging management; Charging Data Record (CDR) encoding rules description

> • | 3GPP TS 32.299: Charging management; Diameter charging applications

> • | 3GPP TS 36.300. EUTRA and EUTRAN; Overall description Stage 2

> • | 3GPP TS 36.412. EUTRAN S1 signaling transport

> • | 3GPP TS 36.413. EUTRAN S1 Application Protocol (S1AP)

> 3GPP2 References

> • | X.S0057-0 v3.0 E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects

> IETF References

> • | RFC 768: User Datagram Protocol (STD 6).

> • | RFC 791: Internet Protocol (STD 5).

> • | RFC 1701, Generic Routing Encapsulation (GRE)

> • | RFC 1702, Generic Routing Encapsulation over IPv4 networks

> • | RFC 2131: Dynamic Host Configuration Protocol

> • | RFC 2460: Internet Protocol, Version 6 (IPv6) Specification

> • | RFC 2473: Generic Packet Tunneling in IPv6 Specification

> • | RFC 2698: A Two Rate Three Color Marker

> • | RFC 2784: Generic Routing Encapsulation (GRE)

> • | RFC 2890: Key and Sequence Number Extensions to GRE

> • | RFC 3162: RADIUS and IPv6

> • | RFC 3266: Support for IPv6 in Session Description Protocol (SDP)

> • | RFC 3319: Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers

> • | RFC 3588: Diameter Base Protocol

> • | RFC 3589: Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5

> • | RFC 3646: DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

> • | RFC 3775: Mobility Support in IPv6

> • | RFC 4004: Diameter Mobile IPv4 Application

> • | RFC 4005: Diameter Network Access Server Application

> • | RFC 4006: Diameter Credit-Control Application

> • | RFC 4282: The Network Access Identifier

> • | RFC 4283: Mobile Node Identifier Option for Mobile IPv6 (MIPv6)

> • | RFC 4861: Neighbor Discovery for IP Version 6 (IPv6)

> • | RFC 4862: IPv6 Stateless Address Autoconfiguration

> • | RFC 5094: Mobile IPv6 Vendor Specific Option

> • | RFC 5149: Service Selection for Mobile IPv6

> • | RFC 5213: Proxy Mobile IPv6

> • | RFC 5447: Diameter Mobile IPv6: Support for NAS to Diameter Server Interaction

> • | RFC 5555: Mobile IPv6 Support for Dual Stack Hosts and Routers

> • | RFC 5844: IPv4 Support for Proxy Mobile IPv6

> • | RFC 5845: Generic Routing Encapsulation (GRE) Key Option for Proxy Mobile IPv6

> • | RFC 5846: Binding Revocation for IPv6 Mobility

> • | Internet-Draft (draft-ietf-dime-qos-attributes-07): QoS Attributes for Diameter

> • | Internet-Draft (draft-ietf-mip6-nemo-v4traversal-06.txt): Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)

> • | Internet-Draft (draft-ietf-netlmm-grekey-option-01.txt): GRE Key Option for Proxy Mobile IPv6, work in progress

> • | Internet-Draft (draft-ietf-netlmm-pmip6-ipv4-support-02.txt) IPv4 Support for Proxy Mobile IPv6

> • | Internet-Draft (draft-ietf-netlmm-proxymip6-07.txt): Proxy Mobile IPv6

> • | Internet-Draft (draft-ietf-mext-binding-revocation-02.txt): Binding Revocation for IPv6 Mobility, work in progress

> • | Internet-Draft (draft-meghana-netlmm-pmipv6-mipv4-00.txt) Proxy Mobile IPv6 and Mobile IPv4 interworking

> Object Management Group (OMG) Standards

> • | CORBA 2.6 Specification 01-09-35, Object Management Group

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