SaMOG Administration Guide, StarOS Release 17 Last Updated: February 27, 2015 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS About This Guide ................................................................................................ v Conventions Used ....................................................................................................................................vi Supported Documents and Resources ................................................................................................... vii Related Common Documentation ...................................................................
▀ Contents Lawful Intercept .................................................................................................................................. 37 Local Breakout Support ...................................................................................................................... 37 LBO Decision based on AAA Policy and Local Policy ................................................................... 38 Prepaid LBO Support ...............................................................
About This Guide This preface describes the SaMOG Administration Guide, how it is organized, and its document conventions. The guide provides information on the SaMOG (S2a-based Mobility over GTP) Gateway and includes network deployments and interfaces, feature descriptions, session establishment and disconnection flows, configuration instructions, and CLI commands for monitoring the system.
About This Guide ▀ Conventions Used Conventions Used The following tables describe the conventions used throughout this documentation. Icon Notice Type Description Information Note Provides information about important features or instructions. Caution Alerts you of potential damage to a program, device, or system. Warning Alerts you of potential personal injury or fatality. May also alert you of potential electrical hazards.
About This Guide Supported Documents and Resources ▀ Supported Documents and Resources Related Common Documentation The most up-to-date information for this product is available in the product Release Notes provided with each product release.
About This Guide ▀ Contacting Customer Support Contacting Customer Support Use the information in this section to contact customer support. Refer to the support area of http://www.cisco.com for up-to-date product documentation or to submit a service request. A valid username and password are required to access this site. Please contact your Cisco sales or service representative for additional information.
Chapter 1 SaMOG Gateway Overview This chapter contains an overview of the SaMOG (S2a Mobility Over GTP) Gateway.
SaMOG Gateway Overview ▀ Product Description Product Description Until recently, Wireless LAN (WLAN) security was considered poor in strength and ease-of-use compared with that of LTE networks and devices, and operators used their core networks to add security layers such as IKEv2 for UE authentication and authorization and IPSec for network security between the UEs and the core network gateways. With the deployment of 802.1x, 802.11u, 802.11i, and Hotspot 2.
SaMOG Gateway Overview Product Description ▀ Qualified Platforms The SaMOG Gateway is a StarOS™ application that runs on Cisco ASR 5x00 and virtualized platforms. For additional platform information, refer to the appropriate System Administration Guide and/or contact your Cisco account representative. Licenses The SaMOG Gateway is a licensed Cisco product.
SaMOG Gateway Overview ▀ SaMOG Services SaMOG Services The SaMOG Gateway acts as the termination point of the WLAN access network. The SaMOG service enables the WLAN UEs in the trusted non-3GPP IP access network to connect to the EPC network via Wireless LAN Controllers (WLCs). During configuration, the SaMOG service gets associated with two services: the Convergence Gateway (CGW) service and the Multi Radio Mobility Entity (MRME) service.
SaMOG Gateway Overview SaMOG Services ▀ DSCP marking. Each traffic class is mapped to a QCI value according to mapping defined in TS 23.203. Therefore, DSCP values must be configured for different QCI values. DSCP markings can be configured to control the DSCP markings for downlink packets. The IP header of the packet is updated with the value in TOS field.
SaMOG Gateway Overview ▀ SaMOG Services provide network-based mobility management on behalf of the UEs attached to the network. With this approach, the attached UEs are no longer involved in the exchange of signaling messages for mobility. The LMA function on the SaMOG Gateway's CGW service and the MAG function on the WLCs maintain a single shared tunnel.
SaMOG Gateway Overview SaMOG Services ▀ MRME Features and Functions The MRME service includes the following features and functions. EAP Authentication over RADIUS—MRME The SaMOG Gateway's MRME service supports Extensible Authentication Protocol (EAP) over RADIUS to interact with the WLCs for authenticating the WLAN UEs based on RFC 3579. Two attributes, EAP-Message and MessageAuthenticator, are used to transport EAP messages as defined in RFC 3579.
SaMOG Gateway Overview ▀ SaMOG Services As per RFC 29.273, UEs without an IMSI are not authorized via the STa Interface. If the Emergency NAI includes an IMEI or MAC username format, the authentication request will be rejected. EAP Identity of Fast Reauthentication NAI Formats—MRME Where the AAA server supports fast reauthentication, the AAA server assigns an identity to the subscriber which is used by the subscriber's UE to initiate a reattach or reauthentication.
SaMOG Gateway Overview SaMOG Services ▀ Normal: @nai.epc.mnc.mcc.3gppnetwork.org Decorated: nai.epc.mnc.mcc.3gppnetwork.org!@nai.epc.mnc.mcc.3gppnetwork.org Important: Currently, SaMOG does not support multi-PLMN. If the PLMN ID of a UE changes during a reattach procedure, the User-Name changes from root to decorated NAI format or vice versa.
SaMOG Gateway Overview ▀ SaMOG Services The SaMOG Gateway’s MRME service supports the selection of a 3GPP AAA proxy based on the IMSI via the operator policy feature. The operator policy provides mechanisms to fine tune the behavior of subsets of subscribers above and beyond the behaviors described in the user profile.
SaMOG Gateway Overview SaMOG Services ▀ Table 1. P-GW Static Selection Step Description 1. The SaMOG Gateway’s MRME service receives the P-GW FQDN or P-GW IP address from the AAA server as part of the MIP-Home-Agent-Host AVP in the Diameter EAP Answer message. 2. If it receives a P-GW FQDN, and if the FQDN starts with “topon”, the MRME service removes the first two labels of the received FQDN to obtain the Canonical Node Name (ID) of the P-GW.
SaMOG Gateway Overview ▀ SaMOG Services Step Description 5. Each of the resulting NAPTR RRs for that record set will be resolved further by performing DNS SRV queries using the replacement string pointed to by the NAPTR RRs. 6. The MRME service receives a list of P-GW FQDNs from the DNS. After all the SRV queries are completed, the MRME service builds a candidate list of P-GW host names. 7.
SaMOG Gateway Overview SaMOG Services ▀ When SaMOG interacts with pre-release 7 network elements (RADIUS based interfaces) it uses A/AAA queries. When SaMOG interacts with post-release 7 network elements (Diameter based interfaces) it uses the NAPTR queries. RADIUS Accounting Proxy—MRME The SaMOG Gateway's MRME service proxies RADIUS accounting messages to a RADIUS accounting server and selects the server based on an IMSI range.
SaMOG Gateway Overview ▀ Network Deployment and Interfaces Network Deployment and Interfaces The SaMOG Gateway provides IP access from the WLAN UEs to the P-GW and the Packet Data Network (PDN) in the Evolved Packet Core (EPC) network. From Release 16.0 and above, the SaMOG Gateway provides IP access from the WLAN UEs to GGSN/P-GW and the Packet Data Network (PDN) over PMIPv6 or EoGRE tunnel.
SaMOG Gateway Overview Network Deployment and Interfaces ▀ Figure 4. SaMOG Gateway in the EPC Network Network Elements This section provides a description of the network elements that work with the SaMOG Gateway in the E-UTRAN/EPC network. eNodeB The evolved Node B (eNodeB) is the termination point for all radio-related protocols. As a network, E-UTRAN is simply a mesh of eNodeBs connected to neighboring eNodeBs via the X2 interface.
SaMOG Gateway Overview ▀ Network Deployment and Interfaces P-GW The Packet Data Network Gateway (P-GW) is the network node that terminates the SGi interface towards the PDN. The P-GW provides connectivity to external PDNs for the subscriber UEs by being the point of entry and exit for all subscriber UE traffic. A subscriber UE may have simultaneous connectivity with more than one P-GW for accessing multiple PDNs.
SaMOG Gateway Overview Network Deployment and Interfaces ▀ Table 3. Logical Network Interfaces on the SaMOG Gateway Interface Description WLAN Interface The interface to the WLCs and WLAN UEs in the trusted non-3GPP IP access network has not yet been defined in the 3GPP standards.
SaMOG Gateway Overview ▀ How the SaMOG Gateway Works How the SaMOG Gateway Works This section describes the SaMOG Gateway during session establishment and disconnection. SaMOG Gateway Session Establishment The figure below shows a SaMOG Gateway session establishment flow. The table that follows the figure describes each step in the flow. Figure 5.
SaMOG Gateway Overview How the SaMOG Gateway Works ▀ Table 5. SaMOG Gateway Session Establishment Step Description 1. An association between the UE and WLC is established. 2. The initial attach procedure starts with the authenticator sending an EAP Request/Identity message toward the supplicant. 3. The UE responds to the EAP Request/Identity message with an EAP Response/Identity message, which contains the user credentials. 4.
SaMOG Gateway Overview ▀ How the SaMOG Gateway Works Figure 6. P-GW Initiated Session Disconnection Table 6. P-GW Initiated Session Disconnection Step Description 1. The P-GW sends a Delete Bearer Request message to the SaMOG Gateway’s CGW service as part of session deletion. 2. The CGW service returns a Delete Bearer Response message to the P-GW and marks the session for deletion. 3. The CGW service sends a Binding Revocation Indication message to the WLC. 4.
SaMOG Gateway Overview How the SaMOG Gateway Works ▀ WLC Initiated Session Disconnection The figure below shows the message flow during a WLC initiated session disconnection. The table that follows the figure describes each step in the message flow. Figure 7. WLC Initiated Session Disconnection Table 7. WLC Initiated Session Disconnection Step Description 1.
SaMOG Gateway Overview ▀ How the SaMOG Gateway Works Step Description 9. The MRME service sends a RADIUS Accounting Stop Response message to the WLC and clears the call at the SaMOG Gateway. AAA Server Initiated Session Disconnection The figure below shows the message flow during an AAA server initiated session disconnection. The table that follows the figure describes each step in the message flow. Figure 8. AAA Server Initiated Session Disconnection Table 8.
SaMOG Gateway Overview How the SaMOG Gateway Works ▀ Step Description 5. The MRME service sends a RADIUS Accounting Stop Response message to the WLC and clears the call at the SaMOG Gateway. 6. The MRME service triggers call deletion by the CGW service. 7. The CGW service triggers a session deletion on the P-GW by sending a Delete Session Request message over the S2a interface. 8. The P-GW acknowledges the session deletion by sending a Delete Session Response message to the CGW service. 9.
SaMOG Gateway Overview ▀ Features and Functionality - Base Software Features and Functionality - Base Software This section describes the SaMOG Gateway features and functions.
SaMOG Gateway Overview Features and Functionality - Base Software ▀ 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 statistics, see the System Administration Guide. Congestion Control Support SaMOG enhances on the StarOS framework to provide congestion control policies and threshold crossing alerts to ensure smooth performance of the SaMOG service and prevent congestion.
SaMOG Gateway Overview ▀ Features and Functionality - Base Software Ethernet over GRE (EoGRE) SaMOG can use both PMIPv6 and EoGRE based access from a trusted WLAN network to connect subscribers to 3G/4G networks. This feature enables 4G/3G subscribers to connect to EPC/Internet using the trusted WiFi SSIDs served by EoGRE enabled Residential Gateways in SaMOG. SaMOG acts as the tunnel endpoint for the EoGRE tunnel initiated from the Residential Gateway.
SaMOG Gateway Overview Features and Functionality - Base Software ▀ Secondary P-GW or GGSN Fallback The SaMOG Gateway supports session establishment between the GTP interface and an alternate P-GW or GGSN when connection establishment fails towards the primary P-GW or GGSN (response timeout or localized issues).
SaMOG Gateway Overview ▀ Features and Functionality - Base Software SNMP Traps The SaMOG Gateway generates SNMP traps for the SaMOG service startup and shutdown events. For detailed descriptions of the traps, refer to the SNMP MIB Reference guide. 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.
SaMOG Gateway Overview Features and Functionality - License Enhanced Feature Software ▀ Features and Functionality - License Enhanced Feature Software This section describes the optional enhanced features and functions for SaMOG service. Important: The following features require the purchase of an additional feature license to implement the functionality with the SaMOG service. For more information on the feature licenses, contact your Cisco account representative.
SaMOG Gateway Overview ▀ Features and Functionality - License Enhanced Feature Software The APN provided by the AAA server is mapped to the locally configured P-GW or GGSN service IP. This eliminates the need for a DNS. The local P-GW or local GGSN assigns the IP using a locally configured IP pool after receiving the subscriber information from the AAA server. The subscriber information is received from the SaMOG service to the local P-GW service or local GGSN service through a GTP tunnel.
SaMOG Gateway Overview Features and Functionality - License Enhanced Feature Software ▀ The DIAMETER AAA server sends the APN information in the APN-Configuration AVP in DEA. This AVP may however be absent in case the AAA server authorizes only LBO, to indicate that any APN can be used for LBO for the subscriber. The operator can configure "local-offload" for each APN supporting LBO under the APN profile.
SaMOG Gateway Overview ▀ Features and Functionality - License Enhanced Feature Software Call Flows with Local Breakout Attach Procedure Figure 10.
SaMOG Gateway Overview Features and Functionality - License Enhanced Feature Software ▀ SaMOG Administration Guide, StarOS Release 17 ▄ 41
SaMOG Gateway Overview ▀ Features and Functionality - License Enhanced Feature Software Table 10. Attach Procedure Call Flow Descriptions Step Description 1 UE associates with AP and WLC. 2 WLC starts EAP based authentication with UE and requests for the permanent identity of the user. 3 UE responds with the permanent identity (IMSI) stored on the SIM. 4 WLC requests SaMOG for authentication using Radius Access Request message.
SaMOG Gateway Overview Features and Functionality - License Enhanced Feature Software ▀ UE Initiated Detach Figure 11. UE Initiated Detach Call Flow Table 11. UE Initiated Detach Call Flow Descriptions Step Description 1 UE initiates DHCP Release or L2 layer detach towards wireless network. 2 If access-type is EoGRE, UE sends a "DHCP Release" message to SaMOG. If the access-type is PMIPv6, WLC sends a PBU (De-registration) to SaMOG. 3 SaMOG sends a "Radius POD" to WLC.
SaMOG Gateway Overview ▀ Features and Functionality - License Enhanced Feature Software AAA Initiated Detach Figure 12. AAA Initiated Detach Call Flow Table 12. AAA Initiated Detach Call Flow Descriptions Step Description 1 AAA sends STa Abort Session Req message to SaMOG. 2-3 SaMOG responds with an STa Abort Session Rsp message to AAA, and "Radius POD" message to WLC. 4 WLC initiates a Radius-Accounting-Stop Request message to SaMOG. 5 SaMOG sends Radius-Accounting-Stop Response message to WLC.
SaMOG Gateway Overview Features and Functionality - License Enhanced Feature Software ▀ For the LBO prepaid support, the SaMOG Gateway generates S-GW CDRs. Any packet drops on the interface P-GW service due to online credit control will still be counted in SGW-CDRs. However, operators can consider enabling P-GW CDRs in the internal P-GW as required. Session Recovery Support SaMOG has the ability to recover fully created sessions in the event of process level or card level failures.
SaMOG Gateway Overview ▀ Features and Functionality - License Enhanced Feature Software Web-based authorization can be performed in the following scenarios: The UE with the Universal Integrated Circuit Card (UICC) does not support EAP-AKA, EAP-SIM, or EAPAKA’ based authentication. The UE with the UICC uses a prepaid voucher. The UE does not have a UICC (laptop, tablet, etc).
SaMOG Gateway Overview Features and Functionality - License Enhanced Feature Software ▀ Limitations, Restrictions, and Dependencies This section identifies limitations, restrictions, and dependencies for the SaMOG Web Authorization feature: After a successful portal-based authentication, the UE will be disconnected and a new connection attempt is required to setup the TAL phase session. The Web Authorization feature cannot be configured with the pseudonym and fast reauthorization NAIs.
SaMOG Gateway Overview ▀ Supported Standards Supported Standards The SaMOG Gateway complies with the following standards: 3GPP References IETF References 3GPP References 3GPP TS 23.234-a.0.0: “Universal Mobile Telecommunications System (UMTS); LTE; 3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release 10)”. 3GGP TS 23.261-a.1.
SaMOG Gateway Overview Supported Standards ▀ IETF References RFC 2460 (December 1998): “Internet Protocol, Version 6 (IPv6) Specification”. RFC 2461 (December 1998): “Neighbor Discovery for IP Version 6 (IPv6)”. RFC 2473 (December 1998): “Generic Packet Tunneling in IPv6 Specification”. RFC 3588 (September 2003): “Diameter Base Protocol”. RFC 3602 (September 2003): The AES-CBC Cipher Algorithm and Its Use with IPsec”.
Chapter 2 Configuring the SaMOG Gateway This chapter provides configuration instructions for the SaMOG (S2a Mobility Over GTP) Gateway. Information about the commands in this chapter can be found in the Command Line Interface Reference.
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway This section provides a high-level series of steps and the associated configuration file examples for configuring the system to perform as a SaMOG Gateway in a test environment. For a configuration example without instructions, see the Sample SaMOG Gateway Configuration File section in this guide.
Configuring the SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway ▀ Required Information Description MRME service name The name of the MRME service to associate with this SaMOG service. This is the MRME service name configured previously in this procedure. CGW service name The name of the CGW service to associate with this SaMOG service. This is the CGW service name configured previously in this procedure.
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway Required Information Description SaMOG context name The name of the SaMOG context configured earlier. AAA DIAMETER STa1 group name The primary AAA group name for use over the STa interface, which can be from 1 to 63 alpha and/or numeric characters. DIAMETER endpoint name The DIAMETER authentication endpoint name for use with this AAA group.
Configuring the SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway ▀ Required Information Description Configuring and Binding the Interfaces SaMOG service Interface port/slot The slot and port number to which you want to bind the SaMOG service. GTP SaMOG interface name and context The SaMOG interface and context name that will be bound to the SaMOG interface port/slot.
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway Step 9 Enable Local breakout for an APN by applying the example configuration in the Configuring Local Breakout section. Step 10 Optional. Enable web-based authorization by applying the example configuration in the Configuring Web-based Authorization section. Step 11 Configure and bind interfaces to the relevant interfaces by applying the example configuration in the Configuring and Binding the Interfaces section.
Configuring the SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway ▀ radius client ip4_address/subnetmask encrypted key key disconnect-message destport port_no exit cgw-service cgw_service_name bind ipv4-address ipv4_address associate egress-egtp_service egress-egtp_service_name revocation enable session-delete-delay timeout timeout_msecs exit samog-service samog_service_name associate mrme-service mrme_service_name assoicate cgw-service cgw_service_name associate subscriber-map subscriber_
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway accounting context context_name aaa-group aaa_group_name accounting context context_name gtpp-group gtpp_group_name assocaite accounting-policy policy_name exit apn-profile profile_name accounting mode none local-offload address-resolution-mode local pgw-address IP_address qos default-bearer qci qci_id qos default-bearer arp arp_value preemption-capability may vulnerability notpreemptable qos apn-ambr max-ul mbr-up max-dl
Configuring the SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway ▀ context samog_context_name egtp-service egtp_service_name associate gtpu-service egtp_service_name gtpc bind ipv4-address ipv4_address exit gtpu-service gtpu_service_name bind ipv4-address ipv4_address exit Configuring AAA Create the AAA group for DIAMETER authentication and then configure AAA accounting and authentication by applying the example configuration below.
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway radius attribute nas-ip-address address ipv4-address radius accounting server ipv4_address encrypted key key port port_no exit aaa group default exit gtpp group default exit diameter endpoint STA_endpoint_name origin realm realm_name use-proxy origin host STa_endpoint_ipv4_address address ipv4_address port port_no no watchdog-timeout peer peer_name realm samog_realm_name address ipv4_address port port_no exit Configuring
Configuring the SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway ▀ gtpp attribute diagnostics gtpp attribute dynamic-flag gtpp attribute record-type sgsnpdprecord gtpp attribute record-type sgwrecord gtpp attribute qos max-length qos_max_length end config call-control-profile call_control_profile_name accounting context samog_context_name gtpp group gtpp_group_name Configuring DNS Configure DNS for the SaMOG gateway by applying the example configuration below.
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway Configuring Local Breakout Important: The Local Breakout (LBO) feature is license dependent. Contact your local Cisco account representative for licensing requirements. Optionally, configure local breakout for an APN.
Configuring the SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway ▀ ip access-group group_name [ in | out ] exit call-control-profile profile_name timeout imsi cache timer_value subscriber multi-device authenticate context context_name auth-method { [ eap ] [non-eap] } end Configuring and Binding the Interfaces The interfaces created previously now must be bound to physical ports. Bind the system interfaces by applying the example configuration below.
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway end Enabling Logging Optional. Enable event logging for the SaMOG Gateway by applying the example configuration below from the Command Line Interface Exec Mode.
Configuring the SaMOG Gateway Configuring the System to Perform as a SaMOG Gateway ▀ snmp trap enable CGWServiceStop end To disable the generation of an SNMP trap: config contextsamog_context_name snmp trap suppress trap_name end Configuring Bulk Statistics Use the following configuration example to enable SaMOG bulk statistics: config bulkstats collection bulkstats mode sample-interval minutes transfer-interval minutes file no remotefile format format /localdisk/bulkstats/bulkstat%date%%time%.
Configuring the SaMOG Gateway ▀ Configuring the System to Perform as a SaMOG Gateway The samog schema command specifies that the SaMOG schema is used to gather statistics. The schema_name is an arbitrary name (in the range of 1 to 31 characters) to use as a label for the collected statistics defined by the format option. The format option defines within quotation marks the list of variables in the SaMOG schema to collect. The format string can be in the range of 1 to 3599.
Chapter 3 SaMOG Gateway Offline Charging The SaMOG Gateway supports generation of CDR files for offline charging. In Offline Charging, charging information is collected concurrently with resource usage and passed through a chain of logical charging functions. At the end of the process, CDR files are generated by the network and transferred to the network operator's Billing Domain. Figure 13.
SaMOG Gateway Offline Charging ▀ SaMOG CDR Formats SaMOG CDR Formats As 3GPP specifications does not define a CDR format for SaMOG, the S-GW CDR and SGSN CDR record formats are used to define the CDR formats. The record format can be selected using a CLI command under the GTPP Group Configuration Mode. By default, for an SaMOG license, the S-GW record type is used, and for an SaMOG 3G license, the SGSN record type is used.
SaMOG Gateway Offline Charging SaMOG CDR Formats ▀ Field Category Description Serving Node Address OC List of serving node control plane IP addresses (e.g. S-GW, SaMOG) used during record generation. MRME service IP address. Serving Node Type OC List of serving node types in control plane. PGW PLMN Identifier OC PLMN identifier (MCC MNC) of the P-GW used. Received in the APN OI part in PBU. For SaMOG 3G license, it will be set to GGSN PLMN ID.
SaMOG Gateway Offline Charging ▀ SaMOG CDR Formats Field Category Description Node ID OM Name of the recording entity. This field contains an identifier string for the node that generates the CDR. On the SaMOG Gateway, the NodeID field is a printable string of the ndddSTRING format. Local Record Sequence Number OM Consecutive record number created by the node. The number is allocated sequentially including all CDR types.
SaMOG Gateway Offline Charging SaMOG CDR Formats ▀ Table 16. SaMOG SGSN CDR Format Field Category Description Record Type M SGSN IP CAN bearer record. Set to SGSN record type. Served IMSI C IMSI of the served party, if available. Received in User name Radius AVP from WLC. SGSN Address used OM The IP address of the current SGSN. CGW service IP address. Charging ID M IP CAN bearer identifier used to identify this IP CAN bearer in different records created by PCNs.
SaMOG Gateway Offline Charging ▀ SaMOG CDR Formats Field Category Description Record Sequence Number C Partial record sequence number in the current SGSN, only present in case of partial records. A running sequence number with range of 1 through 4294967295 used to link partial records generated by the SaMOG for a specific bearer context (characterized with the same Charging ID and SaMOG address pair). This field will not be present if the first record is also the final record.
SaMOG Gateway Offline Charging Triggers for Generation of Charging Records ▀ Triggers for Generation of Charging Records The following section describes the triggers for the generation of partial and final SaMOG CDRs. SaMOG CDRs are updated (not closed) for any of the following conditions: QoS Change: When a QoS change is detected, the “List of Traffic Data Volumes” is added to the CDR. Tarrif Time Change: When the tarrif time changes, the “List of Traffic Data Volumes” is added to the CDR.
SaMOG Gateway Offline Charging ▀ Configuring the SaMOG CDRs Configuring the SaMOG CDRs The SaMOG Gateway uses the custom24 GTPP dictionary to generate SGW and SGSN CDRs. The following table lists the configuration commands related to creating and formatting the CDRs. These commands appear at different portions of the system configuration file. gttp group - These are commands specified within the billing context. Table 17.
SaMOG Gateway Offline Charging Configuring the SaMOG CDRs ▀ Command Default Comment gtpp attribute record-type {sgwrecord | sgsnpdprecord } No If not explicitly configured, the record type selection is based on the SaMOG license used. cc profile buckets index = 0-15 number = 4 Specifies the number of traffic volume container changes due to QoS changes or tariff time that can occur before an accounting record is closed.
SaMOG Gateway Offline Charging ▀ Configuring the SaMOG CDRs Command Default Comment accounting mode gtpp gtpp Enabled Enable this command to generate the bearer based SaMOG CDRs. accounting context [ gtpp group ] GTPP group Default If GTPP group is not configured, the default value is used. If the accounting context is not configured, SaMOG service context is used.
Chapter 4 Monitoring the SaMOG Gateway This chapter provides information for monitoring the status and performance of the SaMOG (S2a Mobility Over GTP) Gateway using the show commands found in the CLI (Command Line Interface). These command have many related keywords that allow them to provide useful information on all aspects of the system ranging from current software configuration through call activity and status.
Monitoring the SaMOG Gateway ▀ Monitoring SaMOG Gateway Status and Performance Monitoring SaMOG Gateway Status and Performance The following table contains the CLI commands used to monitor the status of the SaMOG Gateway features and functions. Output descriptions for most of the commands are located in the Statistics and Counters Reference. Table 18.
Monitoring the SaMOG Gateway Monitoring SaMOG Gateway Status and Performance ▀ To do this: Enter this command: View Subscribers Currently Accessing the System View a list of subscribers currently accessing the system. show subscribers all View a list of SaMOG Gateway subscribers currently accessing the system. show subscribers samog-only [ all | full ] View a list of SaMOG Gateway subscribers currently accessing the system per SaMOG service. View the P-CSCF addresses received from the P-GW.
Monitoring the SaMOG Gateway ▀ Clearing Statistics and Counters Clearing Statistics and Counters It may be necessary to periodically clear statistics and counters in order to gather new information. The system provides the ability to clear statistics and counters based on their grouping. Statistics and counters can be cleared using the CLI clear command. Refer to the Command Line Interface Reference for detailed information on using this command.
