Cisco Cisco ASR 5000
Serving Gateway Overview
▀ Features and Functionality - Base Software
▄ S-GW Administration Guide, StarOS Release 18
30
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 chapter 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
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 chapter 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.
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.
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:
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:
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:
The S-GW supports interface-based ACLs only. For more information on IP access control lists,
refer to the IP Access Control Lists chapter in the System Administration Guide.