The Cisco® ASR
5x00 core platform provides wireless carriers with a flexible solution
that functions as a Serving Gateway (S-GW) in Long Term Evolution-System
Architecture Evolution (LTE-SAE) wireless data networks.
Features and Functionality
- Base Software
This section describes
the features and functions supported by default in the base software
for the S-GW service and do not require any additional licenses
to implement the functionality.
IMPORTANT:
To configure the basic
service and functionality on the system for the S-GW service, refer
to the configuration examples provided in the Serving Gateway Administration
Guide.
The following features
are supported and brief descriptions are provided in this section:
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 Platform 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-level Traffic
Policing
The S-GW now
supports traffic policing for roaming scenarios where the foreign
P-GW does not enforce traffic classes. Traffic policing is used
to enforce bandwidth limitations on subscriber data traffic. It
caps packet bursts and data rates at configured burst size and data
rate limits respectively for given class of traffic.
Traffic Policing is
based on RFC2698- A Two Rate Three Color Marker (trTCM) algorithm.
The trTCM meters an IP packet stream and marks its packets green, yellow,
or red. A packet is marked red if it exceeds the Peak Information
Rate (PIR). Otherwise it is marked either yellow or green depending
on whether it exceeds or doesn't exceed the Committed Information
Rate (CIR). The trTCM is useful, for example, for ingress policing
of a service, where a peak rate needs to be enforced separately
from a committed rate.
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 partial list of supported schemas:
-
System: Provides
system-level statistics
-
Card: Provides
card-level statistics
-
Port: Provides
port-level statistics
-
MAG: Provides
MAG service statistics
-
S-GW: Provides
S-GW node-level service statistics
-
IP Pool: Provides
IP pool statistics
-
APN: Provides
Access Point Name statistics
The system supports
the configuration of up to four 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.
The Cisco Web Element
Manager 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 its PostgreSQL database. It can also
generate XML output and can send it to a Northbound NMS or an alternate
bulk statistics server for further processing.
Additionally, the Bulk
Statistics server can archive files to an alternative directory
on the server. 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.
Circuit Switched
Fall Back (CSFB) Support
Circuit Switched
Fall Back (CSFB) enables the UE to camp on an EUTRAN cell and originate
or terminate voice calls through a forced switchover to the circuit
switched (CS) domain or other CS-domain services (for example, Location
Services (LCS) or supplementary services). Additionally, SMS delivery
via the CS core network is realized without CSFB. Since LTE EPC
networks were not meant to directly anchor CS connections, when
any CS voice services are initiated, any PS based data activities
on the EUTRAN network will be temporarily suspended (either the
data transfer is suspended or the packet switched connection is
handed over to the 2G/3G network).
CSFB provides an interim
solution for enabling telephony and SMS services for LTE operators
that do not plan to deploy IMS packet switched services at initial service
launch.
The S-GW supports CSFB
messaging over the S11 interface over GTP-C. Supported messages
are:
The S-GW forwards Suspend
Notification messages towards the P-GW to suspend downlink data
for non-GBR traffic; the P-GW then drops all downlink packets. Later, when
the UE finishes with CS services and moves back to E-UTRAN, the
MME sends a Resume Notification message to the S-GW which forwards
the message to the P-GW. The downlink data traffic then resumes.
Closed Subscriber Group
Support
The S-GW supports
the following Closed Subscriber Group (CSG) Information Elements (IEs)
and Call Detail Record:
- User CSG Information (UCI)
IE in S5/S8
- CSG Information Reporting
Action IE and functionality in S5/S8
- An SGW-CDR that includes
a CSG record
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 establish limits for defining the state of
the system (congested or clear). These thresholds function in a
way similar to operational 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 appendix
in the System Administration Guide.
Downlink Delay Notification
This feature is
divided between the following:
- Value Handling
- Throttling
- EPS Bearer ID and ARP
Support
Value Handling
This feature provides
for the handling of delay value information elements (IEs) at the
S-GW. When a delay value is received at the S-GW from a particular
MME, the S-GW delays sending data notification requests for all
idle calls belonging to that particular MME. Once the timer expires,
requests can be sent. The delay value at the S-GW is determined
by the factor received in the delay value IE (as a part of either
a Modify Bearer Request or a Data Downlink Notification Request)
and a hard-coded base factor of 50 ms at the S-GW
Throttling
This feature provides
additional controls allowing the S-GW to set factors that “throttle” the continuous
sending and receiving of DDN messages. A single command configures
the throttling parameters supporting this feature,
A description of the ddn throttle command
is located in the S-GW Service Configuration Mode Commands chapter
in the Command Line Interface
Reference.
EPS Bearer ID and
ARP Support
This feature allows
support for Priority Paging support in the network. This is mainly
needed for MPS subscriber support. The paging priority in the paging
message is set by MME based on ARP received in Downlink Data Notification
message.
In order to support MPS
requirement for Priority Paging in the network for MPS subscriber, DDN
message has been enhanced to support passing ARP and EBI information.
When the S-GW sends a Downlink Data Notification message, it shall
include both EPS Bearer ID and ARP. If the Downlink Data Notification
is triggered by the arrival of downlink data packets at the S-GW,
the S-GW shall include the EPS Bearer ID and ARP associated with
the bearer on which the downlink data packet was received. If the
Downlink Data Notification is triggered by the arrival of control
signaling, the S-GW shall include the EPS Bearer ID and ARP, if
present in the control signaling. If the ARP is not present in the
control signaling, the S-GW shall include the ARP in the stored
EPS bearer context. If multiple EPS Bearers IDs are reported in
the Downlink Data Notification message, the S-GW shall include all
the EBI values and the ARP associated with the bearer with the highest
priority (lowest ARP value). For more information, see TS 23.401
(section 5.3.4.3) and 29.274 (section 7.2.11). Details are discussed
in CR-859 of 3GPP specifications.
Dynamic GTP Echo Timer
The Dynamic GTP
Echo Timer enables the eGTP and GTP-U services to better manage
GTP paths during network congestion. As opposed to the default echo
timer which uses fixed intervals and retransmission timers, the
dynamic echo timer adds a calculated round trip timer (RTT) that
is generated once a full request/response procedure has
completed. A multiplier can be added to the calculation for additional support
during congestion periods.
For more information,
refer to the Configuring
the GTP Echo Timer section located in the Configuring Optional
Features on the eGTP S-GW section of the Serving Gateway Configuration chapter.
Event Reporting
The S-GW can
be configured to send a stream of user event data to an external
server. As users attach, detach, and move throughout the network,
they trigger signaling events, which are recorded and sent to an
external server for processing. Reported data includes failure reasons,
nodes selected, user information (IMSI, IMEI, MSISDN), APN, failure
codes (if any) and other information on a per PDN-connection level.
Event data is used to track the user status via near real time monitoring
tools and for historical analysis of major network events.
The S-GW Event Reporting appendix
at the end of this guide describes the trigger mechanisms and event
record elements used for event reporting.
The SGW sends each
event record in comma separated values (CSV) format. The record
for each event is sent to the external server within 60 seconds
of its occurrence. The session-event-module command
in the Context Configuration mode allows an operator to set the
method and destination for transferring event files, as well as the
format and handling characteristics of event files. For a detailed
description of this command, refer to the Command Line Interface
Reference.
Idle-mode Signaling
Reduction Support
The S-GW now supports
Idle-mode Signaling Reduction (ISR) allowing for a control connection
to exist between an S-GW and an MME and S4-SGSN. The S-GW stores
mobility management parameters from both nodes while the UE stores
session management contexts for both the EUTRAN and GERAN/UTRAN.
This allows a UE, in idle mode, to move between the two network
types without needing to perform racking area update procedures,
thus reducing the signaling previously required. ISR support on the
S-GW is embedded and no configuration is required however, an optional
feature license is required to enable this feature.
ISR support on the S-GW
is embedded and no configuration is required, however, an optional
feature license must be purchased to enable this feature.
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, 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:
-
-
All traffic facilitated
by a context (known as a policy ACL)
-
-
All subscriber sessions
facilitated by a specific context
IMPORTANT:
The S-GW supports
interface-based ACLs only. For more information on IP access control lists,
refer to the IP Access
Control Lists appendix in the System Administration Guide.
IPv6 Capabilities
IPv6 enables
increased address efficiency and relieves pressures caused by rapidly
approaching IPv4 address exhaustion problem.
The S-GW platform
offers the following IPv6 capabilities:
IPv6 Connections to
Attached Elements
IPv6 transport and
interfaces are supported on all of the following connections:
-
Diameter Gxc policy
signaling interface
-
Diameter Rf offline
charging interface
-
Lawful Intercept (X1,
X2 interfaces)
Routing and Miscellaneous
Features
-
-
-
IPv6 flows (Supported
on all Diameter QoS and Charging interfaces as well as Inline Services
(for example, ECS, P2P detection, Stateful Firewall, etc.)
LIPA Support
A LIPA (Local IP Access)
PDN is a PDN Connection for local IP access for a UE connected to
a HeNB. The LIPA architecture includes a Local Gateway (LGW) acting
as an S-GW GTPv2 peer. The LGW is collocated with HeNB in the operator
network behaves as a PGW from SGW perspective. Once the default
bearer for the LIPA PDN is established, then data flows directly
to the LGW and from there into the local network without traversing
the core network of the network operator.
In order to support
millions of LIPA GTPC peers, S-GW memory management has been enhanced
with regards to GTPv2 procedures and as well as to support the maintenance
of statistics per peer node.
Establishment of LIPA
PDN follows a normal call flow similar to that of a normal PDN as per
23.401; the specification does not distinguish between a LGW and
a PGW call. As a result, the S-GW supports a new configuration option
to detect a LIPA peer. As a fallback mechanism, heuristic detection
of LIPA peer based on data flow characteristics of a LIPA call is
also supported.
Whenever a peer is detected
as a LIPA peer, the S-GW will disable GTPC echo mechanism towards
that particular peer and stop maintaining some statistics for that
peer.
A configuration option
in APN profile explicitly indicates that all the PDN’s
for that APN are LIPA PDN’s, so all GTPC peers on S5 for
that APN are treated as LGW, and thus no any detection algorithm
is applied to detect LGW.
Location Reporting
Location reporting
can be used to support a variety of applications including emergency calls,
lawful intercept, and charging. This feature reports both user location
information (ULI).
ULI data reported in
GTPv2 messages includes:
-
TAI-ID: Tracking
Area Identity
-
MCC: MNC: Mobile
Country Code, Mobile Network Code
-
The S-GW stores the
ULI and also
reports the information to the accounting framework. This may lead
to generation of Gz and Rf Interim records. The S-GW also forwards
the received ULI to the
P-GW. If the S-GW receives the UE time zone IE from the MME, it
forwards this IE towards the P-GW across the S5/S8 interface.
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
(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 the SPIO card via an RS-232 serial connection
-
Using the Web Element
Manager application
-
Supports communications
through 10 Base-T, 100 Base-TX, 1000 Base-TX, or
-
1000Base-SX (optical
gigabit Ethernet) Ethernet management interfaces on the SPIO
-
Client-Server model
supports any browser (such as, Microsoft Internet Explorer v6.0 and
above or 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.
Figure 5. 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 Manager section
in this chapter.
IMPORTANT:
For more information
on command line interface based management, refer to the Command Line Interface
Reference and P-GW
Administration 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 offdeck content services.
The Mobile Access Gateway
(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 (PMIP) tunnel for all user sessions toward the Local
Mobility Anchor (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 LMAs.
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 and dedicated bearers. To request the various PDN connections,
the MAG includes a common MN-ID and separate Home Network Prefixes,
APNs and a Handover Indication Value equal to one in the PMIPv6
Binding Updates.
IMPORTANT:
Up to 11 multiple PDN
connections are supported.
Node Functionality
GTP Echo
This feature helps
exchange capabilities of two communicating GTP nodes, and uses the
new feature based on whether it is supported by the other node.
This feature allows the
S-GW to exchange its capabilities (MABR, PRN, NTSR) with the peer
entities through ECHO messages. By this, if both the peer nodes
support some common features, then they can make use of new messages
to communicate with each other.
With new “node
features” IE support in ECHO request/response
message, each node can send its supported features (MABR, PRN, NTSR).
This way, S-GW can learn the peer node’s supported features.
S-GW’s supported features can be configured by having some
configuration at the service level.
IMPORTANT:
Note that the S-GW does
not support MABR functionality.
If S-GW wants to use
new message, such as P-GW Restart Notification, then S-GW should check
if the peer node supports this new feature or not. If the peer does
not support it, then S-GW should fall back to old behavior.
If S-GW receives a new
message from the peer node, and if S-GW does not support this new message,
then S-GW should ignore it. If S-GW supports the particular feature,
then it should handle the new message as per the specification.
Online/Offline
Charging
The Cisco EPC
platforms support offline charging interactions with external OCS
and CGF/CDF servers. To provide subscriber level accounting,
the Cisco EPC platform supports integrated Charging Transfer Function
(CTF) and Charging Data Function (CDF) / Charging Gateway
Function (CGF). Each gateway uses Charging-IDs to distinguish between
default and dedicated bearers within subscriber sessions.
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 neighboring CGF within
the configurable polling interval, it 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.
Online: Gy Reference
Interface
The P-GW supports
a Policy Charging Enforcement Function (PCEF) to enable Flow Based Bearer
Charging (FBC) via the Gy reference interface to adjunct Online
Charging System (OCS) servers. 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.
The Gy interface provides an online charging interface that works
with the ECS Deep Packet Inspection feature. With Gy, customer traffic can
be gated and billed. Both time- and volume-based charging models
are supported.
Offline: Gz Reference
Interface
The Cisco P-GW
and S-GW support 3GPP Release 8 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 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 supports integrated Charging Transfer
Function (CTF) and Charging Data Function (CDF). Each gateway uses
Charging-IDs to distinguish between default and dedicated bearers
within subscriber sessions.
The 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
or SFTP connection over the Bm reference interface to a back-end
billing mediation server. The Cisco EPC gateways also offer the
ability to transfer charging records between the CDF and CGF serve
via FTP or SFTP. CDR records include information such as Record
Type, Served IMSI, ChargingID, APN Name, TimeStamp, Call Duration,
Served MSISDN, PLMN-ID, etc.
Offline: Rf Reference
Interface
Cisco EPC
platforms also support the Rf reference interface to enable direct
transfer of charging files from the CTF function of the S-GW to
external CDF or 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.
Operator Policy Support
The operator
policy provides mechanisms to fine tune the behavior of subsets
of subscribers above and beyond the behaviors described in the user
profile. It also can be used to control the behavior of visiting
subscribers in roaming scenarios, enforcing roaming agreements and
providing a measure of local protection against foreign subscribers.
An operator policy associates
APNs, APN profiles, an APN remap table, and a call-control profile
to ranges of IMSIs. These profiles and tables are created and defined
within their own configuration modes to generate sets of rules and
instructions that can be reused and assigned to multiple policies.
In this manner, an operator policy manages the application of rules
governing the services, facilities, and privileges available to
subscribers. These policies can override standard behaviors and
provide mechanisms for an operator to get around the limitations
of other infrastructure elements, such as DNS servers and HSSs.
The operator policy
configuration to be applied to a subscriber is selected on the basis
of the selection criteria in the subscriber mapping at attach time.
A maximum of 1,024 operator policies can be configured. If a UE
was associated with a specific operator policy and that policy is
deleted, the next time the UE attempts to access the policy, it
will attempt to find another policy with which to be associated.
A default operator policy
can be configured and applied to all subscribers that do not match any
of the per-PLMN or IMSI range policies.
The S-GW uses operator
policy to set the Accounting Mode - GTPP (default), RADIUS/Diameter
or none. However, the accounting mode configured for the call-control
profile will override this setting.
Changes to the operator
policy take effect when the subscriber re-attaches and subsequent EPS
Bearer activations.
Peer GTP Node Profile
Configuration Support
Provides flexibility
to the operators to have different configuration for GTP-C and Lawful Intercept,
based on the type of peer or the IP address of the peer
Peer profile feature
allows flexible profile based configuration to accommodate growing requirements
of customizable parameters with default values and actions for peer
nodes of S-GW. With this feature, configuration of GTP-C parameters
and disabling/enabling of Lawful Intercept per MCC/MNC
or IP address based on rules defined.
A new framework of peer-profile
and peer-map is introduced. Peer-profile configuration captures
the GTP-C specific configuration and/or Lawful Intercept
enable/disable configuration. GTP-C configuration covers
GTP-C retransmission (maximum number of retries and retransmission
timeout) and GTP echo configuration. Peer-map configuration matches
the peer-profile to be applied to a particular criteria. Peer-map
supports criteria like MCC/MNC (PLMN-ID) of the peer or
IP-address of the peer. Peer-map can then be associated with S-GW service.
Intent of this feature
is to provide flexibility to operators to configure a profile which
can be applied to a specific set of peers. For example, have a different
retransmission timeout for foreign peers as compared to home peers.
P-GW Restart Notification
Support
This procedure
optimizes the amount of signaling involved on S11/S4 interface
when P-GW failure is detected.
P-GW Restart Notification
Procedure is a standards-based procedure supported on S-GW to notify
detection of P-GW failure to MME/S4-SGSN. P-GW failure
detection will be done at S-GW when it detects that the P-GW has
restarted (based on restart counter received from the restarted
P-GW) or when it detects that P-GW has failed but not restarted
(based on path failure detection). When an S-GW detects that a peer
P-GW has restarted, it shall locally delete all PDN connection table
data and bearer contexts associated with the failed P-GW and notify
the MME via P-GW Restart Notification. S-GW will indicate in the
echo request/response on S11/S4 interface that
the P-GW Restart Notification procedure is supported.
P-GW Restart Notification
Procedure is an optional procedure and is invoked only if both the
peers, MME/S4-SGSN and S-GW, support it. This procedure
optimizes the amount of signaling involved on S11/S4 interface
when P-GW failure is detected. In the absence of this procedure,
S-GW will initiate the Delete procedure to clean up all the PDNs
anchored at that failed P-GW, which can lead to flooding of GTP
messages on S11/S4 if there are multiple PDNs using that
S-GW and P-GW.
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 (TFTs) 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
P-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 (for example, scheduling weights, admission thresholds,
queue management thresholds, link layer protocol configuration,
etc). Cisco EPC gateways also support the ability to map the QCI
values to DiffServ codepoints 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.
IMPORTANT:
The S-GW does not
support non-standard QCI values. QCI values 1 through 9 are standard values
and are defined in 3GPP TS 23.203; the S-GW supports these standard
values.
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 (SDF's)
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.
Rf Diameter Accounting
Provides the
framework for offline charging in a packet switched domain. The
gateway support nodes use the Rf interface to convey session related,
bearer related or service specific charging records to the CGF and
billing domain for enabling charging plans.
The Rf reference interface
enables offline accounting functions on the HSGW in accordance with
3GPP Release 8 specifications. In an LTE application the same reference
interface is also supported on the S-GW and P-GW platforms. The
Cisco gateways use the Charging Trigger Function (CTF) to transfer
offline accounting records via a Diameter interface to an adjunct
Charging Data Function (CDF) / Charging Gateway Function
(CGF). The HSGW and Serving Gateway collect charging information
for each mobile subscriber UE pertaining to the radio network usage
while the P-GW collects charging information for each mobile subscriber
related to the external data network usage.
The S-GW collects
information per-user, per IP CAN bearer or per service. Bearer charging is
used to collect charging information related to data volumes sent
to and received from the UE and categorized by QoS traffic class.
Users can be identified by MSISDN or IMSI.
Flow Data Records (FDRs)
are used to correlate application charging data with EPC bearer usage
information. The FDRs contain application level charging information
like service identifiers, rating groups, IMS charging identifiers
that can be used to identify the application. The FDRs also contain
the authorized QoS information (QCI) that was assigned to a given
flow. This information is used correlate charging records with EPC bearers.
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 S-GW supports 3GPP standards
based session level trace capabilities to monitor all call control events
on the respective monitored interfaces including S1-U, S11, S5/S8,
and Gxc. 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
Note: 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
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 an 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:
-
S11: Create Session
Request
-
S11: Trace Session
Activation
-
S11: Modify Bearer
Request
As subscriber level
trace is a CPU intensive activity the maximum number of concurrently monitored
trace sessions per Cisco P-GW or S-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 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.
Features and Functionality
- Optional Enhanced Feature Software
This section
describes the optional enhanced features and functions for the S-GW
service.
Each of the following
features require the purchase of an additional license to implement
the functionality with the S-GW service.
This section describes
following features:
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).
Direct Tunnel
In accordance
with standards, one tunnel functionality enables the SGSN to establish
a direct tunnel at the user plane level - a GTP-U tunnel, directly
between the RAN and the S-GW.
Figure 7. GTP-U with Direct Tunnel
In effect, a direct
tunnel reduces data plane latency as the tunnel functionality acts
to remove the SGSN from the data plane and limit the SGSN to the
control plane for processing. This improves the user experience
(for example, expedites web page delivery, reduces round trip delay
for conversational services). Additionally, direct tunnel functionality
implements the standard SGSN optimization to improve the usage of
user plane resources (and hardware) by removing the requirement
from the SGSN to handle the user plane processing.
Typically, the SGSN
establishes a direct tunnel at PDP context activation using an Update PDP
Context Request towards the S-GW. This means a significant increase
in control plane load on both the SGSN and S-GW components of the
packet core. Hence, deployment requires highly scalable S-GWs since
the volume and frequency of Update PDP Context messages to the S-GW will
increase substantially. The ASR 5x00 platform capabilities ensure
control plane capacity will not be a limiting factor with direct
tunnel deployment.
For more information
on Direct Tunnel configuration, refer to the Direct Tunnel Configuration appendix
in this guide.
Intelligent Paging
for ISR
In case of Idle-mode
Signaling Reduction (ISR) active and UE is idle, the S-GW will send
Downlink Data Notification (DDN) Message to both the MME and the S4-SGSN
if it receives the downlink data or network initiated control message
for this UE. In turn, the MME and the S4-SGSN would do paging in
parallel consuming radio resources.
To optimize the radio
resource, the S-GW will now perform intelligent paging. When configured
at S-GW service level for each APN, the S-GW will page in a semi-sequential
fashion (one by one to peer MME or S4-SGSN based on last known RAT
type) or parallel to both the MME and S4-SGSN.
Inter-Chassis Session
Recovery
The ASR 5x00
platform provide 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
packet processing card 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 packet processing card failure will cause
a packet processing card 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 (ICSR) 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.
ICSR 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 ICSR 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:
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 appendix in System
Administration Guide.
IP Security (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 S-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:
You must purchase
an IPSec license to enable IPSec. For more information on IPSec support,
refer to the Cisco StarOS
IP Security (IPSec) Reference.
Lawful Intercept
The Cisco Lawful
Intercept feature is supported on the S-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)
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 appendix in the System Administration
Guide.
Overcharging Protection
Support
Use of Overcharging
Protection requires that a valid license key be installed. Contact
your Cisco account representative for information on how to obtain
a license.
Overcharging Protection
helps in avoiding charging the subscribers for dropped downlink packets
while the UE is in idle mode. In some countries, it is a regulatory
requirement to avoid such overcharging, so it becomes a mandatory
feature for operators in such countries. Overall, this feature helps
ensure subscriber are not overcharged while the subscriber is in
idle mode.
P-GW will never be aware
of UE state (idle or connected mode). Charging for downlink data is
applicable at P-GW, even when UE is in idle mode. Downlink data
for UE may be dropped at S-GW when UE is in idle mode due to buffer
overflow or delay in paging. Thus, P-GW will charge the subscriber
for the dropped packets, which isn’t desired. To address
this problem, with Overcharging Protection feature enabled, S-GW
will inform P-GW to stop or resume charging based on packets dropped
at S-GW and transition of UE from idle to active state.
Once the criterion to
signal “stop charging” is met, S-GW will send
Modify Bearer Request (MBReq) to P-GW. MBReq would be sent for the
PDN to specify which packets will be dropped at S-GW. MBReq will
have a new private extension IE to send “stop charging” and “start charging” indication
to P-GW.
When the MBReq with
stop charging is received from a S-GW for a PDN, P-GW will stop charging
for downlink packets but will continue sending the packets to S-GW.
P-GW will resume sending
downlink packets after receiving “stop charging” request
when either of these conditions is met:
- When the S-GW (which
had earlier sent “stop charging” in MBReq) sends “start charging” in
MBReq.
- When the S-GW changes
(which indicates that maybe UE has relocated to new S-GW).
Separate Paging for
IMS Service Inspection
Use of Separate Paging
for IMS Service Inspection requires that a valid license key be
installed. Contact your Cisco account representative for information
on how to obtain a license.
When some operators add
an additional IMS service besides VoLTE such as RCS, they can use
the same IMS bearer between the two services. In this case, separate
paging is supported at the MME using an ID which can be assigned
from the S-GW according to the services, where the S-GW distinguishes
IMS services using a small DPI function to inspect where the traffic
comes from using an ID which is assigned from SGW according to the
services. The S-GW distinguishes IMS services using a small DPI
function to inspect where the traffic comes from (for example IP,
Port and so on). After the MME receives this ID from the S-GW after
IMS service inspection, the MME will do classified separate paging
for each of the services as usual.
Session Recovery
Support
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 has the ability to support stateful intra-chassis
session recovery (ICSR) for S-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 packet services
card during the upgrade process.
IMPORTANT:
For more information
on session recovery support, refer to the Session Recovery appendix
in the System Administration Guide.