P-GW Changes in Release 21 - Cisco...Tocomplywiththe“LongTermEvolution(LTE)AccessNetworkGovernmentIndustryRequirements(GIR) forNationalSecurity/EmergencyPreparedness(NS/EP)NextGenerationNetwork(NGN)Priority”tosupport

P-GW Changes in Release 21.1

This chapter identifies features and functionality added to, modified for, or deprecated from the P-GW inthe StarOS 21.1 software release.

The following identifies all of the P-GW enhancements included in this release:

Feature Changes - new or modified features or behavior changes. For details, refer to the P-GWAdministration Guide for this release.

Command Changes - changes to any of the CLI command syntax. For details, refer to the Command LineInterface Reference for this release.

Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons,counters and/or fields in new or modified schema and/or show command output. For detailed informationon the show commands, refer to the Statistics and Counters Reference for this release. For detailed informationon the counters and disconnect reasons, refer to the BulkstatStatistics_documentation.xls spreadsheet thatis included as part of the software companion package for this release.

This release includes enhancements that are applicable to multiple products. The following lists the variousmulti-product enhancements sections, some of which might include content applicable to your P-GW.

Important

• AAA Changes

• CF Changes

• ECS Changes

• GTPP Changes

• Lawful Intercept Changes

• NAT Changes

• SNMP MIB Changes

• System and Platform Changes

P-GW changes for 21.1 include:

• 3GPP R13 Emergency Call Support on the ePDG and P-GW, page 2

• 3GPP ULI Reporting Support Enhanced, page 8

Release Change Reference, StarOS Release 21.1 1

• APN AMBR Enforcement for L2TP Calls, page 10

• Availability of SSID Information in Gx, Gy, Gz, and LI Interface, page 10

• Availability of the IMEISV on Gx, Gy, and LI Interface, page 11

• Behavior of CCR-U message to PCRF, page 12

• Bulkstats for GTP-C Messages by ARP Value, page 13

• Change in APN and P-GW Service Statistics, page 19

• Correction in Counter Name and Description, page 20

• Correction to CRA display for EGTPC Monitor Protocol, page 20

• Create Bearer Request with CRA Failure, page 21

• Exclude S11 from GTPC Overload Ingress Throttling, page 21

• Expanded Prioritization for VoLTE/Emergency Calls, page 25

• GTPUMgr Performance Optimization, page 34

• Handling IMEI or IMSI Mismatch During Handover, page 35

• Handling TAU Modify Bearer Request Scenarios, page 37

• Modify Bearer Response Using Controlled Parameters, page 37

• Monitor Protocol Display for Civic Address Field, page 41

• NetLoc for WiFi EPC, page 41

• Support for Node Identifier IE Type in Create Session Request, page 46

• P-GW Accepts Modify Bearer Command Request from Old S-GW, page 46

3GPP R13 Emergency Call Support on the ePDG and P-GWCSCvb76292 - Emergency call support as per 3GPP R13 on ePDG & PGW

Feature Default: Enabled

Applicable Products: ePDG, P-GW

Feature DescriptionThe ePDG and P-GW support emergency call establishment over untrusted WiFi for the P-GW as per 3GPPRelease 13. Emergency bearer services are provided to support IMS emergency sessions. Emergency bearerservices are functionalities provided by the serving network when the network is configured to supportemergency services. Emergency bearer services are provided to normal attached UEs and, depending on localregulation, to UEs that are in limited service state. Receiving emergency services in a limited service statedoes not require a subscription.

Authentication Authorization Requests (AAA) to Diameter now carry the new Emergency-Indication AVPfor Untrusted WiFi emergency calls. Diameter requests related to PDN connections for emergency serviceshave the highest priority. Depending on regional/national requirements and network operator policy, these

Release Change Reference, StarOS Release 21.12

P-GW Changes in Release 21.13GPP R13 Emergency Call Support on the ePDG and P-GW

Diameter requests are the last to be throttled, in the event that the 3GPP AAA Server has to apply trafficreduction.

Supported Functionality

3GPP Release 13 Emergency Call Support on the ePDG and P-GW includes the following functionality:

• Emergency call establishment over untrusted WiFi for the P-GW. The P-GW includes the newEmergency-Indication AVP over the AAA s6b interface only during Emergency PDN connectionestablishment.

• Lawful Intercept is supported for Emergency PDNs over the s2b interface.

• Various Create Session Request message IEs have been modified to support all four different behaviorsof emergency bearer establishment.

• Intra- and Inter-chassis recovery are supported for emergency call over the s2b interface.

• Network initiated dedicated bearer creation is supported for emergency calls over the s2b interface.

• The maximum APN restriction is ignored for emergency APN.

• Multiple PDNs are supported for emergency calls over the s2b interface.

• Context replacement for emergency calls over the s2b interface without IMSI with same IMEI issupported.

• P-GW emergency related statistics and bulkstats are available.

• Graceful shutdown of s2b emergency calls is supported.

Previous Behavior: Emergency calls were not supported for the s2b interface. Also, handoff between thes2b interface and LTE was not supported for emergency calls.

New Behavior: Emergency calls are now supported on the s2b interface and handover is also supported foremergency calls from the s2b interface to LTE and vice-versa for "authenticated imsi" only.

How it WorksThe ePDG sends a Create Session Request (CSReq) message to the P-GW. The P-GW deduces the emergencyrelated policies to apply from the Access Point Name (APN) received in the CSReq message. For emergencyattached User Equipment (UE), if the International Mobile Station Identifier (IMSI) cannot be authenticated


P-GW Changes in Release 21.1How it Works

or the UE has not provided it, then the International Mobile Equipment Identifier (IMEI) is used as UEidentifier.

Figure 1: Call Flow: 3GPP R13 Emergency Call Support on the ePDG and P-GW

The P-GW sends the Emergency-Indication AVP over the s6b interface so that the 3GPP AAA server onlyapplies specific policies for emergency services. For an unauthenticated UE, the 3GPP AAA server does notupdate the Home Subscriber Server (HSS) with the identity of the P-GW. For an authenticated UE, thisindication is sent together with the "PDN GW currently in use for emergency services" message, whichcomprises the PDN GW address and the indication that the PDN connection is for emergency services to theHSS, which stores it as part of the UE context for emergency services.

Support is available for all four different behaviors of emergency bearer establishment:

• Valid UEs only.

• Only UEs that are authenticated are allowed.

• IMSI required, authentication optional.

• All UEs are allowed.

This section describes the new Attribute Value Pair (AVP) and modified Information Elements that supportthe feature.



Emergency-Indication AVP

A new Emergency-Indication AVP is defined in the Authentication and Authorization Request to signal arequest to establish a PDN connection for emergency services.

The P-GW signals a new Emergency-Indication AVP to the 3GPP AAA Server in the Authorization Requestover the S6b interface. In this case, the 3GPP AAA Server does not check the APN received from the P-GW(which contains an emergency APN) against the APNs authorized in the user subscription. This AVP issupported in the standard S6b dictionary aaa-custom21.

Information Elements

This section describes other important elements in a Create Session Request that have been modified to workproperly with the feature.

Table 1: Information Elements in a Create Session Request

Ins.IE TypeCondition/CommentPInformationElements

0IMSIThe IMSI is included in the message on the S4/S11interface, and on the S5/S8 interface if provided by theMME/SGSN, except for the case:

- If the UE is emergency attached and the UE is UICCless.

The IMSI shall be included in the message on the S4/S11interface, and on the S5/S8 interface if provided by theMME/SGSN, but not used as an identifier.

- If UE is emergency attached but IMSI is not authenticated.

The IMSI is included in the message on the S2a/S2binterface.

CIMSI




0MSISDNFor an E-UTRAN Initial Attach and a Handover fromTrusted or Untrusted Non-3GPP IP Access to E-UTRANthe IE is included when used on the S11 interface, ifprovided in the subscription data from the HSS. For a PDPContext Activation procedure and a Handover fromTrustedor Untrusted Non-3GPP IP Access to UTRAN/GERANthe IE is includedwhen used on the S4 interface, if providedin the subscription data from the HSS.

The IE is included for the case of a UE Requested PDNConnectivity, if the MME has it stored for that UE. It isincluded when used on the S5/S8 interfaces if provided bythe MME/SGSN.

The ePDG includes this IE on the S2b interface during anAttach with GTP on S2b , UE initiated Connectivity toAdditional PDN with GTP on S2b and a Handover toUntrusted Non-3GPP IP Access with GTP on S2b, InitialAttach for emergency session (GTP on S2b), if providedby the HSS/AAA.

The TWAN includes this IE on the S2a interface during anInitial Attach in WLAN on GTP S2a, UE initiatedConnectivity to Additional PDN with GTP on S2a and aHandover to TWAN with GTP on S2a, if provided by theHSS/AAA.

CMSISDN

0MEIThe MME/SGSN includes the ME Identity (MEI) IE onthe S11/S4 interface:

- If the UE is emergency attached and the UE is UICCless.

- If the UE is emergency attached and the IMSI is notauthenticated.

For all other cases the MME/SGSN includes the MEIdentity (MEI) IE on the S11/S4 interface if it is available.

CME Identity(MEI)

The TWAN/ePDG shall include the ME Identity (MEI) IEon the S2a/S2b interface, if it is available.

CO

0ServingNetwork

This IE is included on the S4/S11, S5/S8 and S2b interfacesfor an E-UTRAN initial attach, a Handover from Trustedor Untrusted Non-3GPP IP Access to E-UTRAN, a PDPContext Activation, a Handover from Trusted or UntrustedNon-3GPP IPAccess toUTRAN/GERAN, aUE requestedPDN connectivity, an Attach with GTP on S2b, a UEinitiated Connectivity to Additional PDNwith GTP on S2b,a Handover to Untrusted Non-3GPP IP Access with GTPon S2b and an Initial Attach for emergency session (GTPon S2b).

CServingNetwork




0IndicationThis IE shall be included if any one of the applicable flagsis set to 1.

Applicable flags are:

- Unauthenticated IMSI: This flag is set to 1 on the S4/S11and S5/S8 interfaces if the IMSI present in the message isnot authenticated and is for an emergency attached UE.

CIndicationFlags

0SelectionMode

This IE is included on the S4/S11 and S5/S8 interfaces foran E-UTRAN initial attach, a Handover from Trusted orUntrusted Non-3GPP IP Access to E-UTRAN, a PDPContext Activation, a Handover from Trusted or UntrustedNon-3GPP IP Access to UTRAN/GERAN and a UErequested PDN connectivity

This IE is included on the S2b interface for an Initial Attachwith GTP on S2b, a Handover to Untrusted Non-3GPP IPAccess with GTP on S2b, a UE initiated Connectivity toAdditional PDNwith GTP on S2b and an Initial Attach foremergency session (GTP on S2b)

The IE indicates whether a subscribed APN or anon-subscribed APN chosen by theUE/MME/SGSN/ePDG/TWAN was selected.

This IE is included on the S2a interface for an Initial Attachin WLAN on GTP S2a, a Handover to TWAN with GTPon S2a and a UE initiated Connectivity to Additional PDNwith GTP on S2a. The value is set to "MS or networkprovided APN, subscription verified".

CSelectionMode

When available, this IE is sent by the MME/SGSN on theS11/S4 interface during TAU/RAU/HO with S-GWrelocation.

CO

0IP AddressThe ePDG includes this IE on the S2b interface during anInitial Attach for emergency session (GTP on S2b).Otherwise the ePDG shall include this IE on the S2binterface based on local policy.

COUE Local IPAddress

0PortNumber

The ePDG includes this IE on the S2b interface if NAT isdetected and the UE Local IP Address is present.

COUE PDP Port

1TWANIdentifier

This IE is included on the S2b interface if the WLANLocation Information is available.

COWLANLocationInformation

0TWANIdentifierTimestamp

This IE is included on the S2b interface, if the WLANLocation Timestamp is available.

COWLANLocationTimestamp



Emergency Handover Support

Two types of emergency call handovers are supported:

• Handover of Emergency Calls from Untrusted WiFi to LTE: Handover of s2b emergency calls toLTE is supported. Since an emergency call in LTE does not have s6b interface authorization enabled,handover of emergency calls from untrustedWiFi to LTE triggers a Session Termination Request (STR)to the s6b server.

• Handover of Emergency Calls from LTE to S2b: Handovers from LTE to S2b are supported. Whilethe UE moves from LTE to untrusted WiFi, LTE triggers an Authentication Authorization Request(AAR) to the s6b server with the AVPEmergency-Indication sent in that Authentication andAuthorizationRequest (AAR). Also, an STR is sent when a WiFi (s2b) call is cleared.

Configuring AAA Failure Handling for s2b Emergency CallsEmergency calls over the s2b interface should not be rejected due to a failure from the S6b server. To ensurethis, failure handling must be configured in the APN which is used for emergency calls .

Handling is configured in the aaa group so that emergency calls continue regardless of failures as indicatedby the result code.

To configure AAA failure handling for s2b emergency calls:configure

context ingress_context_nameaaa group default

diameter authentication failure-handling authorization-request result-code 3000to 5999 action continue

diameter authentication failure-handling authorization-request request-timeoutaction continue

endNote the following assumptions:

• If an IP-CAN Session Modification Request triggered by the PCRF removes all PCC rules with a QCIother than the default bearer QCI and the QCI used for IMS signaling, then the PCEF starts a configurableemergency inactivity timer. When the configured period of time expires, the P-GW initiates an IP-CANSession Termination Request for the IP-CAN session serving the IMS Emergency session

• If the Gx/S6b interface returns a Virtual APN, which is not configured as an emergency APN, then thecall is rejected with the cause code "APN_DENIED_NO_SUBSCRIPTION

3GPP ULI Reporting Support EnhancedCSCvb45350 - 3GPP ULI Reporting gaps on PGW/GGSN

Related CDETs: CSCvb93820 - ULI is coming as absent in show cli o/p of billing testcase dict custom35


Applicable Products: GGSN, P-GW


P-GW Changes in Release 21.1Configuring AAA Failure Handling for s2b Emergency Calls

Feature ChangeThis feature enhancement covers ULI related gaps in P-GW and GGSN as per 3GPP standards.

S4SGSN reports ULI to the P-GW through S-GW. P-GW determines the changes in the ULI with previouslyreceived ULI. If any change is detected and same change has been requested by the PCRF as an event triggerthen the ULI is reported to the PCRF.

SGSN reports ULI to the GGSN. GGSN determines the changes in the ULI with previously received ULI. Ifany change is detected and same change has been requested by the PCRF as an event trigger, then the ULI isreported to the PCRF. Support has also been added to detect the change in RAI received as part of the ULIfield at GGSN.

Following table summarizes the Change Reporting Action (CRA) values based on Event Triggers receivedfrom the PCRF, which the P-GW communicates with S4 SGSN.

CRA Sent to S4 SGSNEvent Trigger From PCRF

Start Reporting CGI/SAI and RAI (5)USER_LOCATION_CHANGE (13)

Start Reporting RAI (2)RAI_CHANGE (12)

Start Reporting CGI/SAI and RAI (5)USER_LOCATION_CHANGE + RAI_CHANGE

Following table summarizes the MS Info Change Reporting Action values based on Event Triggers receivedfrom the PCRF which GGSN communicates to SGSN.

MS Info Change Reporting Actiontowards SGSNEvent Trigger from PCRF

Start Reporting CGI/SAI (1)USER_LOCATION_CHANGE (13)

Start Reporting RAI (2)RAI_CHANGE (12)

Start Reporting CGI/SAI (1)BOTH (12,13)

P-GW/GGSN reports the CRA/MS Info Change Reporting Action immediately on receiving the Event Triggerswithout waiting for other events like APN/AMBR update or QoS update.

Behavior Change

Previous of Change Reporting Action: Following table illustrates the old and new behavior of ChangeReporting Action with respect to the Event Triggers received from PCRF, when the Access Node is S4SGSN.

CRA Sent to S4SGSNCRA Sent to S4SGSNEvent Trigger From PCRF

5(START_REPORTING_CGI_RAI)6(START_REPORTING_TAI_ECGI)

ULI_CHANGE(13)

2 (START_REPORTING_RAI)No CRA SentRAI_CHANGE(12)


P-GW Changes in Release 21.1Feature Change

CRA Sent to S4SGSNCRA Sent to S4SGSNEvent Trigger From PCRF

5 (START_REPORTING_CGI_RAI)6(START_REPORTING_TAI_ECGI)

BOTH (12,13)

Behavior of MS Info Change Reporting Action: Following table illustrates the old and new behavior ofMS Info CRA with respect to the Event Triggers received from PCRF, when the Access Node is SGSN.

CRA Sent to SGSNCRA Sent to SGSNEvent Trigger From PCRF

1 (START_REPORTING_CGI/SAI)1(START_REPORTING_CGI/SAI)

ULI_CHANGE(13)

2 (START_REPORTING_RAI)No CRA SentRAI_CHANGE(12)

1 (START_REPORTING_CGI/SAI)1(START_REPORTING_CGI/SAI)

BOTH (12,13)

Limitations

1 In GGSN, when a newULI is received in the Network Request Updated PDP Context (NRUPC) Response,it is not reported to the PCRF.

2 In GGSN, when a dedicated bearer is deleted or call is dropped, ULI change is not detected.

APN AMBR Enforcement for L2TP CallsCSCva04622 - APN AMBR Enforcement (L2TP) - UPLOAD not enforced

Applicable Products: P-GW, SAEGW

Feature ChangesPrevious Behavior: For L2TP calls, APN AMBR based rate limit on uplink was not enforced.

New Behavior: For L2TP calls, APN AMBR based rate limit on uplink is now enforced.

Impact on customer: In uplink data path, for L2TP calls, APN AMBR based rate limiting is enforced.

Availability of SSID Information in Gx, Gy, Gz, and LI InterfaceCSCva53626 - Civic Address Information/AP-Group-Name" to be sent by PGW in Gx, Gy, Gz & LI records


This feature is enabled only if "Network Provided User Location Information reporting extensions overS2b interface" is enabled on ePDG and "Civic Address in TWAN-Identifier IE" is enabled on SaMOG.

Important


P-GW Changes in Release 21.1APN AMBR Enforcement for L2TP Calls

Applicable Products: P-GW

Feature DescriptionOn the S2a interface P-GW receives the identity of theWifi access point in the TWAN-IDENTIFIER attributein the CREATE SESSION REQUEST message. This information consists of AP MAC address, SSID, andCIVIC Address (which may contain information like AP Group name).

For location tracking and location based policy purpose, the above information needs to be propagated to thePolicy Server (Gx), Quota Server(Gy), Charging Gateway(Gz) and LI Server. This new feature enhances theP-GW to propagate the AP SSID, BSSID and Civic Address on all these interfaces whenever received on theS2a interface.

Gx Interface

On the Gx interface this information is sent to PCRF in CCR-I/CCR-U and CCR-T messages in TWANIDENTIFIER attribute. The standard Gx dictionary configuration is sufficient for this.

Gy Interface

On the Gy interface this information is sent to quota server in CCR-I/CCR-U and CCR-T messages in a CiscoVendor specific attribute named "Civic-Addr" whenever dcca_custom33 dictionary is configured for thisinterface.

Gz Interface

On the Gz interface this information is sent to charging gateway in the CDR (Charging Data Records) inTWANUserLocationInformation attribute whenever custom53 dictionary is configured on this interface.

LI Interface

On the LI interface the information is sent to the LI server in the IRI events in "twan_identifier" field. Nospecific dictionary change is needed for this.

The PGW receives this SSID/BSSID/Civic Address information on s2a interface from a Trusted WLANnetwork (via SaMOG). If Cisco SaMOG is used then the functionality of sending this information fromSaMOG to PGW can be controlled via a configuration (refer the SaMOG functionality for this). Thisfeature will lead to 3-4% increase in baseline AAAmgr memory usage.

Important

Availability of the IMEISV on Gx, Gy, and LI InterfaceCSCvb69264 - IMEISV availability on Gx, GY & LI Interface for S2a over GTPv2 Interface




P-GW Changes in Release 21.1Feature Description

Feature ChangesWith this feature, the International Mobile Equipment Identity Software Version (IMEISV) information willbe available in Gx, Gy and LI for S2a over GTPv2 Interface for SaMOG Local BreakOut (LBO).

Previous Behavior: The IMEISVwas sent by the P-GW, for trustedWiFi, over Gx interface. For Gy interface,the IMEISV was sent by the P-GW, for trusted WiFi, only in case of SaMOG LBO.

New Behavior: The IMEISV is sent by the P-GW, for trusted WiFi, over Gx interface in CCR-I and CCR-U.For Gy interface, the IMEISV is sent by the P-GW, for trustedWiFi, in CCR-I and CCR-U and not just duringSaMOG LBO.

The following functionality has been implemented to support the feature:

• For Non-SIM devices, which are not equipped with IMEI value, the SaMOG encodes the Non-SIMdevice’s MAC address in IMEISV attribute towards the P-GW.

• The SaMOG encodes the UE-MAC in the IMEISV Information Element (IE) of Create Session Requesttowards the P-GW/GGSN.

• To support inter-operability with different vendor(s) P-GW/GGSN, the SaMOG sends the UE-MACencoded in decimal format.

• The P-GW forwards the IMEISV to Gx and Gy in Credit Control Request-Initial (CCR-I) and CreditControl Request-Update (CCR-U), for interface type S2a.

• The IMEI/IMEISV is sent within the User-Equipment-Info AVP over Gx and Gy in INITIAL andUPDATE REQUEST.

• The IMEI/IMEISV is sent in Observed IMEI Information Element (IE) towards the LI interface.

Notes:

• A Basic LI license is a pre-requisite for this feature to work.

• The LI tapping is done based only on the first 14 digits of the IMEISV.

• Support of standard dictionaries for Gx and Gy, like r8-gx-standard and dcca-custom8, is required.

Behavior of CCR-U message to PCRFCSCvc01095 - Cisco PGW does not send CCR-U message to PCRF when Update Bearer Request is rejected

Applicable Products: P-GW, SAE-GW

Feature ChangesPrevious Behavior: CCR-U was not sent to Gx when Update Bearer Request is rejected due to bearer levelGTP Cause "Context Not Found".

New Behavior: CCR-U is sent to Gx when Update Bearer Request is rejected due to bearer level GTP Cause"Context Not Found". CCR-U will not be sent if the message level GTP Cause is "Context Not Found".


P-GW Changes in Release 21.1Feature Changes

Bulkstats for GTP-C Messages by ARP ValueCSCvb62562 - Bulk stats for GTP-C messages by ARP value

Feature Default: Disabled

Applicable Products: P-GW, SAE-GW, S-GW

Feature DescriptionTo comply with the “Long Term Evolution (LTE) Access Network Government Industry Requirements (GIR)for National Security/Emergency Preparedness (NS/EP) Next Generation Network (NGN) Priority” to supportemergency calls over Voice over LTE (VoLTE), several Key Performance Indicators (KPIs) have beenintroduced with this feature. This feature is utilized to collect statistics for total number of GTP-C messagesreceived for Enhanced Multimedia Priority Service (eMPS) session for specified interval (in minutes). Thelist of GTP-C messages are defined in accordance with the GIR document. As part of this feature:

• The S-GW will generate peg counts of the total number of received GTP-C messages containing anAllocation and Retention Priority (ARP), chosen from the set of values allocated for NS/EP NGN-PSuse, for a specified interval (in minutes). This peg count is administered at the S-GW level.

• The P-GW will generate peg counts of the total number of received GTP-C messages containing anARP, chosen from the set of values allocated for NS/EPNGN-PS use, for a specified interval (in minutes).This peg count is administered at the specific P-GW level.

• The peg counts for GTP-C messages are broken down by message type similar to existing GTP-Cmessage counters. The bulkstats are broken down by applicable S-GW and P-GW service and S5, S8,S11, and S4 interfaces.

In earlier releases, bulkstats were not present for eMPS session. With this release 21.1, bulkstats are addedfor eMPS session/message.

Piggy-back Message

For piggy-back messages, if either of the messages have matching ARP or result into converting non-eMPSsession to eMPS session, then both messages are counted as eMPS message and corresponding statistics forboth messages are incremented.

If Modify Bearer Request is piggy-backed with Create Bearer Response on S11 interface of S-GW and CreateBearer Response result into converting non-eMPS session into eMPS session, then Modify Bearer Responsestatistics will not increment for this Modify Bearer Request.

Bulkstats Collection and Reset

Bulkstats are added under eGTP-C Schema and pgw-egtpc-s5s8 Schema. These eMPS bulkstats in eGTP-CSchema and pgw-egtpc-s5s8 Schema holds value only for a bulkstat interval, that is, value of these bulkstatsshows number of eMPS messages exchanged during the bulkstat interval.

LimitationsThis section identifies the known limitations of the feature:


P-GW Changes in Release 21.1Bulkstats for GTP-C Messages by ARP Value

• Peer level and APN level statistics are not collected.

• MPS statistics recovery is not supported.

• MPS statistics are not collected for CSReq, DDNReq, and change notification messages rejected bydemux with ARP for eMPS sessions.

• MPS statistics are not collected for retried/re-transmitted messages.

Licensing

Bulkstats for GTP-CMessages by ARPValue feature requires that a valid license key be installed. Contactyour Cisco Account or Support representative for information on how to obtain a license.

Important

Performance Indicator Changes

S-GW Ingress S4 InterfaceThe following CLI commands are modified to display the eMPS session related GTP-C message statistics forS4 interface of S-GW Ingress:

• show egtpc statistics interface sgw-ingress interface-type s4

• interface-type: Displays interface level GTP-C message statistics

• s4: Displays interface level GTP-C message statistics for S4 interface

• show egtpc statistics egtp-service sgw_egtpc_service_name interface-type s4

• s4: Interface type S4 for S-GW eGTP-C interface

The output of the above CLI commands displays the following new parameters:

• Total eMPS Statistics: Cumulative GTP-C message statistics for messages received/transmitted oneMPS Sessions.

• Current interval eMPS Statistics: GTP-C message statistics for messages received/transmitted oneMPS Sessions for current statistics collection interval. Statistics collection interval will be same asbulkstats collection interval. If bulk stats collection is not configured, then Current MPS Statistics willbe same as Total MPS Statistics.

• Create Session Request (Total RX): This counter will be incremented by S-GWwhen it receives Createsession request message on S4 interface containing an ARP value configured in MPS Profile.

• Create Session Response (Total TX): This counter will be incremented by S-GW when it transmitsCreate session response message on S4 interface containing an ARP value configured in MPS Profile.


P-GW Changes in Release 21.1Performance Indicator Changes

S-GW Ingress S11 InterfaceThe following CLI commands are modified to display the eMPS session related GTP-C message statistics forS11 interface of S-GW Ingress:

• show egtpc statistics interface sgw-ingress interface-type s11


• s11: Displays interface level GTP-C message statistics for S11 interface

• show egtpc statistics egtp-service sgw_egtpc_service_name interface-type s11

• s11: Interface type S11 for S-GW eGTP-C interface




• Create Session Request (Total RX): This counter will be incremented by S-GWwhen it receives Createsession request message on S11 interface containing an ARP value configured in MPS Profile.

• Create Session Response (Total TX): This counter will be incremented by S-GW when it transmitsCreate session response message on S11 interface containing an ARP value configured in MPS Profile.

• Modify Bearer Request (Total RX): This counter will be incremented by S-GW when it receivesModify Bearer request message on S11 interface containing an ARP value configured in MPS Profile.

• Modify Bearer Response (Total TX): This counter will be incremented by S-GW when it transmitsModify Bearer response message on S11 interface containing an ARP value configured in MPS Profile.

• Create Bearer Request (Total TX): This counter will be incremented by S-GW when it transmitsCreate Bearer request message on S11 interface containing an ARP value configured in MPS Profile.

• Create Bearer Response (Total RX): This counter will be incremented by S-GW when it receivesCreate Bearer response message on S11 interface containing an ARP value configured in MPS Profile.

• Downlink Data Notification (Total TX): This counter will be incremented by S-GWwhen it transmitsDownlink Data Notification message on S11 interface containing an ARP value configured in MPSProfile.

• Downlink Data Notification Ack (Total RX): This counter will be incremented by S-GW when itreceives Downlink Data NotificationAckmessage on S11 interface containing anARP value configuredin MPS Profile.

• Update Bearer Request (Total TX): This counter will be incremented by S-GW when it transmitsUpdate Bearer request message on S11 interface containing an ARP value configured in MPS Profile.

• Update Bearer Response (Total RX): This counter will be incremented by S-GW when it receivesUpdate Bearer response message on S11 interface containing an ARP value configured in MPS Profile.



S-GW Egress GTP-based S5/S8 InterfaceThe following CLI commands are modified to display the eMPS session related GTP-C message statistics forS5/S8 interface of S-GW Egress:

• show egtpc statistics interface sgw-egress interface-type s5s8


• s5s8: Displays interface level GTP-C message statistics for S5/S8 interface

• show egtpc statistics egtp-service sgw_egtpc_service_name interface-type sgw-s5s8

• sgw-s5s8: Interface type S5/S8 for S-GW eGTP-C interface




• Create Session Request (Total TX): This counter will be incremented by S-GW when it transmitsCreate session request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Create Session Response (Total RX): This counter will be incremented by S-GW when it receivesCreate session response message on S5/S8 interface containing an ARP value configured inMPS Profile.

• Modify Bearer Request (Total TX): This counter will be incremented by S-GW when it transmitsModify Bearer request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Modify Bearer Response (Total RX): This counter will be incremented by S-GW when it receivesModify Bearer response message on S5/S8 interface containing an ARP value configured inMPS Profile.

• Create Bearer Request (Total RX): This counter will be incremented by S-GWwhen it receives CreateBearer request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Create Bearer Response (Total TX): This counter will be incremented by S-GW when it transmitsCreate Bearer response message on S5/S8 interface containing an ARP value configured inMPS Profile.

• Update Bearer Request (Total RX): This counter will be incremented by S-GW when it receivesUpdate Bearer request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Update Bearer Response (Total TX): This counter will be incremented by S-GW when it transmitsUpdate Bearer response message on S5/S8 interface containing an ARP value configured inMPS Profile.

P-GW Ingress GTP-based S5/S8 InterfaceThe following CLI commands are modified to display the eMPS session related GTP-C message statistics forS5/S8 interface of P-GW Ingress:

• show egtpc statistics interface pgw-ingress interface-type s5s8



• show egtpc statistics egtp-service pgw_egtpc_service_name interface-type s5s8

• s5s8: Interface type S5/S8 for P-GW eGTP-C interface.




• Create Session Request (Total RX): This counter will be incremented by P-GWwhen it receives Createsession request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Create Session Response (Total TX): This counter will be incremented by P-GW when it transmitsCreate session response message on S5/S8 interface containing an ARP value configured inMPS Profile.

• Modify Bearer Request (Total RX): This counter will be incremented by P-GW when it receivesModify Bearer request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Modify Bearer Response (Total TX): This counter will be incremented by P-GW when it transmitsModify Bearer response message on S5/S8 interface containing an ARP value configured inMPS Profile.

• Create Bearer Request (Total TX): This counter will be incremented by P-GWwhen it receives CreateBearer request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Create Bearer Response (Total RX): This counter will be incremented by P-GW when it receivesCreate Bearer response message on S5/S8 interface containing an ARP value configured inMPS Profile.

• Update Bearer Request (Total TX): This counter will be incremented by P-GW when it transmitsUpdate Bearer request message on S5/S8 interface containing an ARP value configured in MPS Profile.

• Update Bearer Response (Total RX): This counter will be incremented by P-GW when it receivesUpdate Bearer response message on S5/S8 interface containing an ARP value configured inMPS Profile.

clear egtpcThe following CLI commands are modified to clear eMPS statistics at interface level and eGTP-C servicelevel:

• clear egtpc statistics interface-type interface-pgw-ingress interface s5s8: Clears interface statisticsalong with eMPS statistics for all eGTP-C services of P-GW Ingress type and S5/S8 interface.

• clear egtpc statistics interface-type [ interface-sgw-ingress | interface-sgw-egress ] interface [ s4 |s11 | sgw-s5s8 ]: Clears interface statistics along with eMPS statistics for all eGTP-C services of S-GWIngress type and S4 or S11 interface/S-GW Egress type and S5/S8 interface.

• clear egtpc statistics egtp-service pgw_egtpc_service_name interface [ s5s8 ]: Clears interface statisticsalong with eMPS statistics for all P-GW eGTP-C services and S5/S8 interface.

• clear egtpc statistics egtp-service sgw_egptc_service_name interface [ s11 | s4 | sgw-s5s8 ]: Clearsinterface statistics along with eMPS statistics for all S-GW eGTP-C services and S4 or S11 or S5/S8interface.



P-GW eGTP-C S5/S8 SchemaThe following new bulk statistics variables are added to the P-GW eGTP-C S5/S8 schema in support of thisfeature:

• tun-recv-cresessreq-emps – The total number of tunnel - create session request - messages received bythe system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-sent-cresessresp-emps – The total number of tunnel - create session response - messages sent by thesystem for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-recv-modbearerreq-emps – The total number of tunnel - modify bearer request - messages receivedby the system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-sent-modbearerresp-emps – The total number of tunnel - modify bearer response - messages sentby the system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-sent-crebearerreq-emps – The total number of tunnel - create bearer request - messages sent by thesystem for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-recv-crebearerresp-emps – The total number of tunnel - create bearer response - messages receivedby the system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-sent-updbearerreq-emps – The total number of tunnel - update bearer request - messages sent by thesystem for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-recv-updbearerresp-emps – The total number of tunnel - update bearer response - messages receivedby the system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

eGTP-C SchemaThe following new bulk statistics variables are added to the eGTP-C schema in support of this feature:

• s11-tun-recv-cresessreq-emps – The total number of tunnel - create session request - messages receivedby the system for eMPS subscriber on interface s11. This stat is for current bulkstat interval only.

• s11-tun-sent-cresessresp-emps – The total number of tunnel - create session response - messages sentby the system for eMPS subscriber on interface s11. This stat is for current bulkstat interval only.

• s11-tun-recv-modbearerreq-emps – The total number of tunnel - modify bearer request - messagesreceived by the system for eMPS subscriber on interface s11. This stat is for current bulkstat intervalonly.

• s11-tun-sent-modbearerresp-emps – The total number of tunnel - modify bearer response - messagessent by the system for eMPS subscriber on interface s11. This stat is for current bulkstat interval only.

• s11-tun-sent-crebearerreq-emps – The total number of tunnel - create bearer request - messages sent bythe system for eMPS subscriber on interface s11. This stat is for current bulkstat interval only.

• s11-tun-recv-crebearerresp-emps – The total number of tunnel - create bearer response - messagesreceived by the system for eMPS subscriber on interface s11. This stat is for current bulkstat intervalonly.

• s11-tun-sent-updbearerreq-emps – The total number of tunnel - update bearer request - messages sentby the system for eMPS subscriber on interface s11. This stat is for current bulkstat interval only.



• s11-tun-recv-updbearerresp-emps – The total number of tunnel - update bearer response - messagesreceived by the system for eMPS subscriber on interface s11. This stat is for current bulkstat intervalonly.

• s11-tun-sent-ddnreq-emps – The total number of downlink data notification - messages sent by thesystem for eMPS subscriber on interface s11. This stat is for current bulkstat interval only.

• s11-tun-recv-ddnack-emps – The total number of downlink data notificatino acknowledge - messagesreceived by the system for eMPS subscriber on interface s11. This stat is for current bulkstat intervalonly.

• s4-tun-recv-cresessreq-emps – The total number of tunnel - create session request - messages receivedby the system for eMPS subscriber on interface s4. This stat is for current bulkstat interval only.

• s4-tun-sent-cresessresp-emps – The total number of tunnel - create session response - messages sent bythe system for eMPS subscriber on interface s4. This stat is for current bulkstat interval only.

• tun-sent-cresessreq-emps – The total number of tunnel - create session request - messages sent by thesystem for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-recv-cresessresp-emps – The total number of tunnel - create session response - messages receivedby the system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-sent-modbearerreq-emps – The total number of tunnel - modify bearer request - messages sent bythe system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-recv-modbearerresp-emps – The total number of tunnel - modify bearer response - messages receivedby the system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-recv-crebearerreq-emps – The total number of tunnel - create bearer request - messages received bythe system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-sent-crebearerresp-emps – The total number of tunnel - create bearer response - messages sent bythe system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-recv-updbearerreq-emps – The total number of tunnel - update bearer request - messages receivedby the system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

• tun-sent-updbearerresp-emps – The total number of tunnel - update bearer response - messages sent bythe system for eMPS subscriber on interface s5s8. This stat is for current bulkstat interval only.

Change in APN and P-GW Service StatisticsCSCvb40297- mod-uebear & ue-init-modfail bulkstat not hit for 4g & 3g respectively


Feature ChangesWhen P-GW sends a Modify Bearer Failure Indication to the S-GW, the UE-initiated modification failurecounter in APN statistics is wrongly incremented. The current release resolves this issue.

Previous Behavior: CCR-U was not sent to Gx when Update Bearer Request is rejected due to bearer levelGTP Cause "Context Not Found".


P-GW Changes in Release 21.1Change in APN and P-GW Service Statistics

New Behavior: CCR-U is sent to Gx when Update Bearer Request is rejected due to bearer level GTP Cause"Context Not Found". CCR-U will not be sent if the message level GTP Cause is "Context Not Found".

Correction in Counter Name and DescriptionCSCvc12401 - PGW counter sessstat-beardel-ded giving wrong info.

Applicable Products: P-GW, SAEGW

Feature ChangesThis cdet introduces bulkstat variable name and description change.

Previous Behavior: The description of the following three bulkstat variables' to display count of networkinitiated dedicated bearer deletion was incorrect.

• sessstat-beardel-ded (P-GW Schema)

• pgw-sessstat-beardel-ded (SAEGW Schema)

• saegw-ggsn-sessstat-beardel-ded (SAEGW Schema)

New Behavior: The bulk stat variable names listed above have been changed to the following respectively:

• sessstat-beardel (P-GW Schema)

• pgw-sessstat-beardel (SAEGW Schema)

• saegw-ggsn-sessstat-beardel (SAEGW Schema)

Also, description of these counters has been correctly updated to reflect that these counters show the countof total bearers deleted for respective schema.

Impact on customer: Scripts may need to be updated to use the new variable names.

Correction to CRA display for EGTPC Monitor ProtocolCSCvb54946 - CRA display is incorrect in mon pro


Feature ChangesThe Change Reporting Action (CRA) display output for the EGTPC (74) monitor protocol will be changedfrom 'Start Reporting CGAI/SAI and RAI' to 'Start Reporting CGI/SAI and RAI' in this release.

Previous Behavior: The CRA for EGTPC monitor protocol with value 5 was displayed incorrectly as 'StartReporting CGAI/SAI and RAI'.

CHANGE REPORT ACT:

Value: 5 (Start Reporting CGAI/SAI and RAI)


P-GW Changes in Release 21.1Correction in Counter Name and Description

New Behavior: The CRA for EGTPC monitor protocol with value 5 is corrected to display 'Start ReportingCGI/SAI and RAI'.

CHANGE REPORT ACT:

Value: 5 (Start Reporting CGI/SAI and RAI)

Create Bearer Request with CRA FailureCSCvc27320 - After Create Bearer Request with CRA failure, CRA is not going in next immediate message


Feature ChangesPrevious Behavior: When P-GW sends Create Bearer Request with CRA value requested from the PCRFand receives Create Bearer Request failure, P-GW does not send the CRA value in the next message goingto the S-GW. Typically, P-GW must send CRA value in the next message going towards S-GW.

New Behavior: When P-GW sends Create Bearer Request with CRA value requested from the PCRF andreceives Create Bearer Request failure, P-GW now sends the CRA value in the next message going to theS-GW.

Exclude S11 from GTPC Overload Ingress ThrottlingCSCvb45868 - Exclude SGW ingress interface from GTP-C overload ingress throttling

Applicable Products: GGSN, P-GW, S-GW, SAEGW

Feature ChangesPrevious Behavior: Earlier, GTPC incoming throttling CLI was enabled at the context level and applied toall P-GW, S-GW, SAEGW, and GGSN services configured in that context. It enabled throttling of the interfacelike S5, S8(P-GW), S4, S11(S-GW), and Gn Gp(GGSN). Disabling throttling exclusively for S-GW ingressGTPC interfaces (S4, S11) was not possible.

Earlier, the help string for CLI keyword ingress said " Configures Throttling Parameters of Incoming NewCreate GTPC messages for GGSN, P-GW and other GTP services in this context".

New Behavior: New keywords exclude and sgw-interface have been added to the CLI command gtpcoverload-protection ingress to disable throttling exclusively for S-GW ingress GTPC interfaces (S4, S11).See the "Command Changes" section for more information.

The help string for CLI keyword ingress has been modified as follows, "Configures throttling parameters forincoming new call GTPC messages for GGSN, P-GW, S-GW and SAEGW services in this context".


P-GW Changes in Release 21.1Create Bearer Request with CRA Failure

Command Changes

exclude sgw-interfaceNew keywords exclude and sgw-interface have been added to the CLI command gtpc overload-protectioningress to disable throttling exclusively for S-GW ingress GTPC interfaces (S4, S11).

configureconext context_name

gtpc overload-protection ingress { msg-rate msg_rate } [delay-tolerance duration] [queue-sizesize ][exclude {sgw-interface}]

end

Notes:

• exclude: Exclusion options.

• sgw-interface: Resets the incoming throttling parameters "msg-rate" and "queue-size" to their defaultvalues for GTPC incoming new call messages at SGW ingress interface (S4, S11). The message queuesize considered for Congestion Control feature for PGW/SGW/GGSN is reset to default value of 10K,if this keyword is configured.

• ingress: Configures throttling parameters for incoming new call GTPC messages for GGSN, PGW,SGW and SAEGW services in this context.

1 When gtpc overload-protection ingress CLI is configured without the exclude sgw-interface option,the configured values of msg rate, delay tolerance and queue-size are enabled on new call messages atS-GW ingress interface (S4, S11).

2 When exclude sgw-interfaceis configured for the GTPC messages on the S-GW interface (S4, S11),below are the values taken by different parameters:

• msg-rate:Default value; default value is 0

• queue-size:Default value; default value is 10000

• delay-tolerance:Configured Value for the GTPC messages on the S-GW interface (S4, S11)

3 If exclude sgw-interfaceis configured, GTPC ingress messages throttling is applied (with the configuredvalues ofmsg rate, delay tolerance and queue-size) to the external interfaces of P-GW and GGSN suchas S5, S8, S2b, Gn/Gp, only to the new call create messages incoming from outside of the ASR5k. GTPCingress message throttling is also applied to the internal interfaces of the SAEGW such as the S5/S8interfaces, only to the new call create messages received at the local P-GW of the SAEGW.

4 If ingress throttling is configured using gtpc overload-protection ingress with exclude sgw-interface,then for congestion control calculation for P-GW/S-GW/GGSN/SAEGW demuxmgr based on messagequeue size, the default queue size value of 10K is used.

If ingress throttling is configured using gtpc overload-protection ingresswithout exclude sgw-interface,then for congestion control calculation for P-GW/S-GW/GGSN/SAEGW demuxmgr based on messagequeue size, the configured queue-size value will be used.

The following table describes various scenarios of the configuration:


P-GW Changes in Release 21.1Command Changes

BehaviourChange

Queue-sizeconsidered forCongestionControlThreshold forP-GW/GGSN/S-GW

Queue-sizeused for GTPCIncomingThrottling forS-GW

Queue-sizeused for GTPCIncomingThrottling forP-GW/GGSN

If "excludesgw-interface"configured

GTPC IncomingThrottlingQueue-sizeConfiguration(100..10K)

NoConfigured_congestion_threshold* 10K (Default)

10K (Default)10K (Default)NoNoconfiguration/Defaultconfiguration

NoConfigured_congestion_threshold* 10K (Default)

10K (Default)10K (Default)YesNoconfiguration/Defaultconfiguration

NoConfigured_congestion_threshold* 5k (or theconfiguredvalue)

5k (or theconfiguredvalue)


No5K (or anyconfiguredvalue from100..10K)

YesConfigured_congestion_threshold* 10k (this isthe behaviourchange forcongestioncontrol, if"excludesgw-interface"is configured)

10k (because"excludesgw-interface"is configured)


Yes5k (or Anyconfiguredvalue from100..10K)


show ggsn-service name | allThis command has been modified to display the following output:

In case of default configuration:

GTPC Incoming Throttling Params: Configured (Default)Message Rate (per sec): 0(Disbaled)Dealy Tolerance (secs): 5Queue Size: 10000S-GW Interface Excluded: NoQueue size for Congestion Control: 10000

When exclude sgw-interface is enabled along with other incoming throttling parameters:

GTPC Incoming Throttling Params: ConfiguredMessage Rate (per sec): 4000Dealy Tolerance (secs): 8Queue Size: 3000



S-GW Interface Excluded: YesQueue size for Congestion Control: 10000

Without exclude sgw-interface configured:

GTPC Incoming Throttling Params: ConfiguredMessage Rate (per sec): 4000Dealy Tolerance (secs): 8Queue Size: 3000S-GW Interface Excluded: NoQueue size for Congestion Control: 3000

show pgw-service name | allThis command has been modified to display the following output:




GTPC Incoming Throttling Params: ConfiguredMessage Rate (per sec): 4000Dealy Tolerance (secs): 8Queue Size: 3000S-GW Interface Excluded: YesQueue size for Congestion Control: 10000


GTPC Incoming Throttling Params: ConfiguredMessage Rate (per sec): 4000Dealy Tolerance (secs): 8Queue Size: 3000S-GW Interface Excluded: NoQueue size for Congestion Control: 3000

show sgw-service name | allThis command has been modified to display the following output:




GTPC Incoming Throttling Params: ConfiguredMessage Rate (per sec): 0(Disbaled)Dealy Tolerance (secs): 8Queue Size: 10000S-GW Interface Excluded: YesQueue size for Congestion Control: 10000


GTPC Incoming Throttling Params: Configured



Message Rate (per sec): 4000Dealy Tolerance (secs): 8Queue Size: 3000S-GW Interface Excluded: NoQueue size for Congestion Control: 3000

Expanded Prioritization for VoLTE/Emergency CallsCSCvb53652 - SGW/PGW should support DSCP marking for eMPS session


Applicable Products: P-GW, SAE-GW, S-GW

Feature DescriptionThe National Security/Emergency Preparedness (NS/EP) Next Generation Network (NGN) Priority Services(NGN-PS) (formerly called NGN Government Emergency Telecommunications Service (GETS)) is a set ofvoice, video and data services that are based on services available from public packet-switched ServiceProviders. The NS/EP NGN-PS provides priority treatment for a Service User’s NS/EP communications andis particularly needed when the Service Providers’ networks are impaired due to congestion and/or damagefrom natural disasters (such as floods, earthquakes and hurricanes) and man-made disasters (such as physical,cyber or other forms of terrorist attacks).

In earlier releases, the DSCP marking of control message from P-GW and S-GW was based on associatedegtpc-service configuration.

With Release 21.1, for control message belonging to eMPS session or containing Allocation and RetentionPriority (ARP) associated with eMPS profile, the DSCP marking is based on eMPS profile configured DSCPvalue.

As part of this enhancement, support is also added for marking of certain GTP-C message at the P-GW andS-GW for priority treatment as defined in the Government Industry Requirements (GIR) NS/EP NGN.

Relationships to Other FeaturesBulkstats for GTP-C Messages by ARP Value: The S-GW/P-GW will generate peg counts of the totalnumber of received GTP-C messages containing an ARP, chosen from the set of values allocated for NS/EPNGN-PS use, for a specified interval (in minutes). This peg count is administered at the S-GW/P-GW level.

To prevent throttling of GTP-C messages corresponding to eMPS PDNs or messages containing ARP fromset of configured ARP(PL) reserved for NS/EP NGN priority service, following configuration are to beconsidered:

1 Load Overload control

In overload control profile, the set of ARPs reserved for NS/EP NGN-PS use for eMPS services shouldalso be defined under throttling-behavior exclude and self-protection-behavior excludeCLI commands.This will ensure that incoming GTP-C messages for eMPS PDN or containing ARP from set of reservedARP for eMPS use are not throttled. Example of configuring Load Overload configuration:

configuregtpc-overload-control-profile profile_name

throttling-behavior { earp { 1...15 } * } { exclude }


P-GW Changes in Release 21.1Expanded Prioritization for VoLTE/Emergency Calls

self-protection-behavior { earp { 1...15 } * } { exclude }end

2 For Prioritized handling of calls under Congestion condition

ARP reserved under NS/EPNGN-PS for eMPS services is recommended to be configured under followingcongestion control CLI command. This will ensure that new call requests are not throttled during congestioncondition defined by the congestion-control CLI command at context level:configure

context context_nameegtp-service service_name

gtpc allow-on-congestion arp arp_valueend

3 GTP-C RLF Throttling

• If GTP-C RLF Throttling feature is enabled, then gtpc overload-protection egressthrottling-override-policy CLI command should be configured with ARP(PL), reserved for NS/EPNGN-PS use, for eMPS services to bypass RLF throttling.

• If GTP-C RLF Throttling for incoming messages is configured using gtpc overload-protectioningress msg-rate message_rate CLI command, then eMPS related messages can get throttled.Currently, there is no bypass policy for incoming RLF throttling.

Any existing features which works on ARP (PL) configurations will continue to work as before irrespectiveof whether ARP values configured are same as reserved under NS/EP NGN-PS for eMPS services. Ifexisting features need to work with eMPS requirements, then same ARP (PL) values should be configuredas reserved NS/EP NGN-PS for eMPS services.

Important

LicensingThe DSCP marking capability requires that a valid license key be installed. Contact your Cisco Account orSupport representative for information on how to obtain a license.

How It Works

GIR Document References

The following table describes the requirements of this feature as per the GIR document.

DescriptionRequirement No.

[202] The S-GW shall transmit with priority a GTP-C “Downlink DataNotification” message or a GTP-C “Create Bearer Request” message or aGTP-C “Update Bearer Request” message, any of which contains an ARPchosen from the set allocated by the Service Provider for use by NS/EPNGN-PS.

R-127


P-GW Changes in Release 21.1How It Works

DescriptionRequirement No.

[204] The S-GW shall mark for priority treatment the S11 “Create SessionResponse” message from the S-GW to the MME which contains requestto establish a bearer or bearers with an ARP corresponding to an NS/EPNGN-PS call/session.

R-130

[205] The S-GW shall mark for priority treatment the S11 “Create BearerRequest” and S11 “Update Bearer Request” messages from the SGW tothe MME which contains an indication that a UE currently has anestablished/updated bearer or bearers for NS/EP NGN-PS service.

R-132

[206] In the case where the S5/S8 Interface is GTP-based, the S-GW shallmark for priority treatment the S5/S8 “Create Session Request” messagefrom the S-GW to the PDN-GW which contains an indication that a UEwill establish a bearer or bearers for NS/EP NGN-PS.

R-134

[207] In the case where the S5/S8 Interface is GTP-based, the S-GW shallmark for priority treatment the S5/S8 “Create Bearer Response” and “UpdateBearer Response”messages from the S-GW to the PDN-GWwhich containan indication that a UE currently has established / updated a bearer orbearers for NS/EP NGN-PS.

R-137

[213] In the case where the S5/S8 Interface is GTP-based, the PDN-GWshall mark for priority treatment the S5/S8 “Create Session Response”message from the PDN-GW to the S-GW which contains a request toestablish a bearer or bearers with an ARP corresponding to an NS/EPNGN-PS call/session.

R-143

[216] In the case where the S5/S8 Interface is GTP- based, the PDN-GWshall mark for priority treatment the S5/S8 “Create Bearer Request” and“Update Bearer Request”messages from the PDN-GW to the S-GWwhichcontain an indication that a UE currently has an established/updated beareror bearers for NS/EP NGN-PS.

R-146

Configuring Expanded Prioritization for VoLTE/Emergency CallsThe following section provides the configuration commands to enable the feature.

Configuring eMPS Profile and its Associated AttributesAt ConfigurationMode level, CLI command option is introduced to define an eMPS profile and its associatedattributes like:

• eARP configuration: This configuration is used for marking a bearer/PDN as an eMPS.


P-GW Changes in Release 21.1Configuring Expanded Prioritization for VoLTE/Emergency Calls

• DSCP configuration: This configuration is used at S-GW/P-GW to mark various outgoing GTP-Cmessages associated with an eMPS PDN with configured DSCP marking.

configure[ no ] emps-profile emps_profile_name -noconfirm[ no ] earp { [ 1...15 ] { [ 1...15 ] { [ 1...15 ] } } }[ no ] dscp-marking dscp_valueend

Notes:

• emps-profile emps_profile_name: Configures eMPS profile for defining attributes of an eMPS session.The emps_profile_name is a string of size from 1 to 63.

• earp: Configures a maximum of 3 eARP priority level (PL) values so that sessions with configuredeARP priority values can be marked as eMPS sessions.

• -noconfirm: Creates a new eMPS profile without prompting for confirmation.

• dscp-marking dscp_value: Specifies the DSCP value to be applied to eMPS sessions. The dscp_valueis a hexadecimal number between 0x0 and 0x3F.

• Maximum of 3 eARP values can be configured under an eMPS profile. The above CLI syntax providesflexibility to configure one or more (max 3) eARP values in a single command. For example:

earp 1 2 3

-Or-

earp 4

• The latest set of eARP values configured will overwrite the previous configuration. For example: Invokingbelow two commands in sequence will configure only eARP value 4.

earp 1 2 3

earp 4

• eMPS profile name should be unique and is treated case insensitive across context.

• The no earp command can be used to disable all configured eARP values. However, this will not deletethe corresponding eMPS profile. The no emps-profile emps_profile_name CLI command will deletethe profile.

• Warningmessage:When no of a non-existent eMPS profile is executed, a warning message is displayed.For example:no emps-profile xyzeMPS Profile : xyz does not exist

There will be no warning message if no of an un-configured eARP is executed.

• There will be a warning and confirmation message when existing profile is deleted:This operation will result in deletion of this eMPS Profile.Are you sure? [Yes|No]:

• Maximum of 64 different eMPS profiles can be configured.


P-GW Changes in Release 21.1Configuring Expanded Prioritization for VoLTE/Emergency Calls

Associating an eMPS Profile with P-GW ServiceThe commands illustrated below associates an eMPS profile to P-GW service.

configurecontext context_name

pgw-service service_nameassociate emps-profile emps_profile_nameend

Notes:

• no associate emps-profile: Disables the feature.

• emps-profile emps_profile_name: Associates an eMPS profile with the P-GW service. Theemps_profile_name is a string of size 1 to 63.

• The eMPS profile name in input is treated as case insensitive.

• By default, no eMPS profile is associated with pgw-service.

• For SAE-GW associated P-GW service, the eMPS profiles should be same as configured in associatedS-GW service. In case of any discrepancy, it will be reported in the show configuration error CLIcommand output.

Associating an eMPS Profile with S-GW ServiceThe commands illustrated below associates an eMPS profile to S-GW service.


sgw-service service_nameassociate emps-profile emps_profile_nameend

Notes:

• no associate emps-profile: Disables the feature.

• emps-profile emps_profile_name: Associates an eMPS profile with the S-GW service. Theemps_profile_name is a string of size 1 to 63.

• The eMPS profile name in input is treated as case insensitive.

• By default, no eMPS profile is associated with sgw-service.

• For SAE-GW associated S-GW service, the eMPS profiles should be same as configured in associatedP-GW service. In case of any discrepancy, it will be reported in the show configuration error CLIcommand output.

Monitoring and Troubleshooting the Expanded Prioritization forVoLTE/Emergency Calls

This section provides information regarding show commands and/or their outputs in support of thisenhancement.


P-GW Changes in Release 21.1Monitoring and Troubleshooting the Expanded Prioritization for VoLTE/Emergency Calls

Show Command(s) and/or Outputs

show emps-profile { all | name <emps_profile_name> }

The above CLI command is introduced to see a particular or all eMPS profile(s) configured with its associatedattributes. Also, the output of an existing show config [ verbose ] CLI command is modified to reflect aneMPS configuration:

• earp configured: <earp_value>

• dscp-marking configured: <dscp-value>

These CLI commands can be used to verify if the configuration is appropriate.

show pgw-service { name <name> | all }

The output of this command is modified to reflect the eMPS profile associated with the P-GW service:

• eMPS Profile Name : <emps_profile_name>

Maximum of one eMPS profile can be associated with P-GW service at a time; the latest configurationwill overwrite the previously associated configuration.

Important

show sgw-service { name <name> | all }

The output of this command is modified to reflect the eMPS profile associated with the S-GW service:

• eMPS Profile Name : <emps_profile_name>

Maximum of one eMPS profile can be associated with S-GW service at a time; the latest configurationwill overwrite the previously associated configuration.

Important

show subscribers pgw-only full all

The output of this command is modified to reflect whether the session is eMPS or not. For example:Username: 0123456789@usernameSubscriber Type : VisitorStatus : Online/ActiveState : ConnectedConnect Time : Wed Sep 7 07:02:49 2016Auto Delete : NoIdle time : 00h00m08sMS TimeZone : n/a Daylight Saving Time: n/aAccess Type: gtp-pdn-type-ipv4 Network Type: IPAccess Tech: eUTRAN pgw-service-name: pgw_serviceCallid: 00004e21 IMSI: 123456789012341MSISDN: 0123456789Interface Type: S5S8GTP Low Access Priority: N/ATWAN Mode: N/AeMPS Bearer: YesEmergency Bearer Type: N/AIMS-media Bearer: No



show subscribers saegw-only full all

The output of this command is modified to reflect whether the session is eMPS or not. For example:Username: 0123456789@usernameSAEGW Call mode : Co-locatedSubscriber Type : Home...MSISDN: 0123456789TWAN Mode: N/AeMPS Bearer: YesMS TimeZone : Daylight Saving Time: n/aMEI : 1122334455667788 Accounting mode : GTPP

show pgw-service statistics

The output of this command is modified to display the eMPS PDN statistics information. For example:PDNs By Emergency-Type:Emergency PDNs:Active: 0 Setup: 0Authentic IMSI: 0 Authentic IMSI: 0

.

.

.eMPS PDNs:Current Active: 1 Cumulative Activated: 1Cumulative De-activated: 1

IPv4v6 PDN-Type Received with DAF False : 0Where:

• Current Active: Increments when any PDN is setup as an eMPS PDN or upgraded to eMPS PDN.Decrements when an eMPS PDN is released or when it degrades to a non-eMPS PDN.

• Cumulative Activated: Increments when any PDN is setup as an eMPS PDN or upgrades to an eMPSPDN.

• CumulativeDe-activated: Increments when an eMPS PDN is released or when it degrades to a non-eMPSPDN.

show saegw-service statistics all function pgw

The output of this command is modified to display the eMPS PDN statistics information. For example:PDNs By Emergency-Type:Emergency PDNs:Active: 0 Setup: 0Authentic IMSI: 0 Authentic IMSI: 0

.

.

.eMPS PDNs:Current Active: 1 Cumulative Activated: 1Cumulative De-activated: 1

IPv4v6 PDN-Type Received with DAF False : 0Where:






show saegw-service statistics

The output of this command is modified to display the eMPS statistics for PGW-Anchored/SGW-AnchoredPDNs associated with the saegw-service. For example:PDNs By Emergency-Type:Emergency PDNs:Active: 0 Setup: 0Released: 0...eMPS PDNs:Colocated PDNs:Current Active: 1 Cumulative Activated: 1Cumulative De-activated: 0PGW-Anchor PDNs:Current Active: 1 Cumulative Activated: 1Cumulative De-activated: 0SGW-Anchor PDNs:Current Active: 1 Cumulative Activated: 1Cumulative De-activated: 0

The above statistics information are further classified based on SAE-GW call types:

• Colocated eMPS PDNs: It reflects the eMPS PDN statistics information for collapsed PDNs.

• PGW-Anchor eMPS PDNs: It reflects the eMPS PDN statistics information for PGW-Anchor PDNs.

• SGW-Anchor eMPS PDNs: It reflects the eMPS PDN statistics information for SGW-Anchor PDNs.

Where:




show sgw-service statistics all

The output of this command is modified to reflect whether the session is eMPS or not. For example:Subscribers Total:Active: 0 Setup: 2Released: 1...eMPS PDN Statistics:Current Active: 1 Cumulative Activated: 1Cumulative De-activated: 0



show saegw-service statistics all function sgw

The output of this command is modified to display the eMPS PDN statistics information. For example:Subscribers Total:Active: 0 Setup: 0Released: 0...eMPS PDN Statistics:Current Active: 1 Cumulative Activated: 1Cumulative De-activated: 0

show configuration error

System will show configuration errors for following scenarios:

• When different eMPS profiles are configured under pgw-service and sgw-service associated to samesae-gw service. For example:############################################################

Displaying SAEGW-Service system errors############################################################Error : eMPS profile of SGW <sgw-service> and PGW service <pgw_service>is not same for SAEGW service <saegw-service> in the context <context_name>.Total 1 error(s) in this section !

• When non-existent emps-profile is associated to pgw-service. For example:############################################################

Displaying PGW-Service system errors############################################################Error : eMPS Profile <emps_profile_pgw> configured for PGW service <pgw_service>is not present in the systemTotal 1 error(s) in this section !

• When non-existent emps-profile is associated to sgw-service. For example:############################################################

Displaying SGW-Service system errors############################################################Error : eMPS Profile <emps_profile_sgw> configured for SGW service <sgw_service>is not present in the systemTotal 1 error(s) in this section !

Bulkstats for Expanded Prioritization for VoLTE/Emergency Calls

PGW Schema

The following bulk statistics have been added to the P-GW schema as part of this enhancement:

• sessstat-pdn-emps-current-active – The total number of currently active P-GW eMPS PDNs.

• sessstat-pdn-emps-cumulative-activated – The total number of P-GW PDNs that are either setup as aneMPS PDN or upgrades to an eMPS PDN.

• sessstat-pdn-emps-cumulative-deactivated – The total number of P-GW PDNs that were either releasedor degrades to a non-eMPS PDN.

SGW Schema

The following bulk statistics have been added to the S-GW schema as part of this enhancement:



• sessstat-pdn-emps-current-active – The total number of currently active S-GW eMPS PDNs.

• sessstat-pdn-emps-cumulative-activated – The total number of S-GW PDNs that are either setup as aneMPS PDN or upgrades to an eMPS PDN.

• sessstat-pdn-emps-cumulative-deactivated – The total number of S-GW PDNs that were either releasedor degrades to a non-eMPS PDN.

SAEGW Schema

The following bulk statistics have been added to the SAE-GW schema as part of this enhancement:

• pgw-anchor-pdns-emps-current-active – The total number of currently active P-GW anchored eMPSPDNs.

• pgw-anchor-pdns-emps-cumulative-activated – The total number of P-GW anchored PDNs that areeither setup as an eMPS PDN or upgrades to an eMPS PDN.

• pgw-anchor-pdns-emps-cumulative-deactivated – The total number of P-GW anchored PDNs that wereeither released or degrades to a non-eMPS PDN.

• saegw-colocated-pdns-emps-current-active – The total number of currently active SAE-GW collapsedeMPS PDNs.

• saegw-colocated-pdns-emps-cumulative-activated – The total number of SAE-GW collapsed PDNs thatare either setup as an eMPS PDN or upgrades to an eMPS PDN.

• saegw-colocated-pdns-emps-cumulative-deactivated – The total number of SAE-GW collapsed PDNsthat were either released or degrades to a non-eMPS PDN.

• sgw-anchor-pdns-emps-current-active – The total number of currently active S-GW anchored eMPSPDNs.

• sgw-anchor-pdns-emps-cumulative-activated – The total number of S-GW anchored PDNs that are eithersetup as an eMPS PDN or upgrades to an eMPS PDN.

• sgw-anchor-pdns-emps-cumulative-deactivated – The total number of S-GW anchored PDNs that wereeither released or degrades to a non-eMPS PDN.

GTPUMgr Performance OptimizationCSCva48154 - GTPUMgr Performance Optimization Standby Chassis


Applicable Products: GGSN, P-GW, SAEGW, S-GW

Feature DescriptionSessmgr will optimize ADD/DELETE entry for each session/bearer to GTPUMgr on a need basis, whichreduces the signaling toward the GTPUMgr on standby chassis. During audit, missing entries received fromSessmgr to GTPUMgr will be added to reduce the audit failures and retain calls. These changes allow asubstantial reduction in standby CPU usage, performance improvements in GTPUMgr, and no GTPUMgraudit failures.


P-GW Changes in Release 21.1GTPUMgr Performance Optimization

SESSMgr-GTPUMgr Audit Failure Optimization

Previous Behavior:When GTPUMgr and Sessmgr are out of synch during session recovery/ICSR recovery,which can happen for reasons such as GTP-U remote TEIDs mismatch, GTPUMgr audit failures are triggeredand calls are cleared.

New Behavior:GTPUMgr audit failures during session recovery/ICSR recovery have been reduced to retainthe maximum number of calls. Instead of detecting GTPUMgr audit failure and clearing call, Sessmgr entriesare now reinstalled on GTPUMgr once audit procedure is complete in session recovery/ICSR recovery.

SESSMgr-GTPUMgr Signaling Optimization on Standby Chassis

Previous Behavior: GTPUMgr was hitting high CPU utilization on standby chassis in high VoLTE callconnection/disconnection scenarios. For every VoLTE bearer establishment and deletion, RAR is triggeredfrom PCRF. Upon receiving a full checkpoint on the standby chassis, GTPUMgr signaling for delete and thenadd was sent for every bearer.

Call getting clear by GTPUMgr when duplicate ADD session sent from Session Manager to GTPUMGR forsame callid.

New Behavior: On standby chassis, signaling to GTPUMgr will now be optimized during full checkpointinstallation so that only the new bearer addition/deletion related signaling is communicated to GTPUMgr.Signaling to GTPUMgr on standby chassis for existing bearers, if there's no change in bearers, shall not begenerated on new full checkpoint install request.

This functionality reduces standby chassis GTPUMgr CPU usage in high VoLTE call connection/disconnectionscenarios.

Handling IMEI or IMSI Mismatch During HandoverCSCvc21444 - Option to reject theMBReq/UPCwhen IMEI inMBreq/UPC different than the session presentin PGW

Applicable Products: GGSN, P-GW

Feature ChangesDuring certain network scenarios, when a subscriber's session using a control tunnel endpoint ID (TEID) withP-GW/GGSN is disconnected, the session might be cleared locally (P-GW/GGSN) while it remains activeon the peer node.When another subscriber connects to P-GW/GGSN from a home network, there is a probabilitythat P-GW/GGSN might assign the same TEID value that was allotted during the earlier session to thissubscriber. When S-GW/SGSN forwards the MBReq/UPC message to P-GW/GGSN with the TEID from thestale session, the session is considered as a handover for the earlier subscriber and P-GWCDRs are generatedfor that subscriber. The earlier subscriber is thus charged incorrectly.

Previous Behavior: Handover of MBReq/UPC was accepted even when IMEI/IMSI in MBreq/UPC wasdifferent than the session present in P-GW/GGSN.

New Behavior: With this release, handover of MBReq/UPC is rejected when IMEI/IMSI in MBreq/UPC isdifferent than the session present in P-GW/GGSN. This change in behavior is controlled by newly introducedkeywords in egtp modify-bearer-rsp and gtpc CLI commands.


P-GW Changes in Release 21.1Handling IMEI or IMSI Mismatch During Handover

Command Changes

egtp

The reject imei-mismatch keywords are added to the egtp modify-bearer-rsp CLI command under theP-GW Service Configuration Mode for configuring the P-GW to reject IMEI in the MBReq message duringhandover, when the IMEI is different than the one present in P-GW.


pgw-service service_name[ default | no ] egtp modify-bearer-rsp reject imei-mismatchend

Notes:

• default: Resets the command to the default setting.

• no: Disables the configuration statement.

• reject: Modify Bearer Response reject options.

• imei-mismatch: Rejects Modify Bearer Request (MBReq) with CONTEXT_NOT_FOUND (CC 64)cause if IMEI/IMEISV received inMBReq does not match with the IMEI/IMEISV of an existing session.

• By default, the MBReq will be accepted even if IMEI/IMEISV received in MBReq does not match withthe IMEI/IMEISV of an existing session.

gtpc

The update-pdp-resp reject imsi-mismatch keywords are added to the gtpcCLI command under the GGSNService ConfigurationMode for configuring the GGSN to reject IMSI in theMBReqmessage during handover,when the IMSI is different than the one present in GGSN.


ggsn-service service_name[ default | no ] gtpc update-pdp-resp reject imsi-mismatchend

Notes:

• default: Resets the command to the default setting.

• no: Disables the configuration statement.

• update-pdp-resp: Updates PDP Response options.

• reject: Updates PDP Response reject options.

• imsi-mismatch: Rejects Update PDP Request with NON_EXISTENT (CC 192) cause if IMSI receivedin Update PDP Request does not match with the IMSI of an existing session.

• By default, the Update PDP Request will be accepted even if IMSI received in Update PDP Requestdoes not match with the IMSI of an existing session.


P-GW Changes in Release 21.1Command Changes


show pgw-service name <service_name>This command is enhanced to display the current status of reject imei-mismatch option. The following sampledisplay is only a portion of the output:EGTP Bit Rate in Rounded Down Kbps : DisabledEGTP Suppress Update Bearer Request (no bitrate change) : DisabledEGTP Modify Bearer Response with Context Not Found cause if IMEI/IMEISV mismatch :Enabled/Disabled

show ggsn-service name <service_name>This command is enhanced to display the current status of the reject imsi-mismatch option. The followingsample display is only a portion of the output:GTPC Prioritized Rel99 ARP(s) :GTPC Update PDP Response with Non Existent cause if IMSI mismatch : Enabled/Disabled3GPP Qos to DSCP Mapping (for G-PDUs):

Handling TAU Modify Bearer Request ScenariosCSCvc74089 - RejectingMBReq fails when IMEI inMBreq is diff than sess present in PGW during S4SGSNto 4g Ho


Feature ChangesPrevious Behavior: The Modify Bearer Request (MBReq) for Tracking Area Update (TAU) without S-GWchange was accepted, if the IMEI present in MBReq was different than the IMEI of current session.

New Behavior: With this release, the MBReq for TAU without S-GW change is rejected, if IMEI present inMBReq is different than the IMEI of current session.

The Modify Bearer Response message is sent with message level cause as REQUEST_REJECTED (0x5E)and bearer context level cause as CONTEXT_NOT_FOUND (0x40).

Modify Bearer Response Using Controlled ParametersCSCvb87712 - CSFB fix for hub partners





Feature DescriptionWith the enhancement in this release, the P-GW service includes configurable parameters to includeCharging-ID, Charging FQDN or Charging Gateway address, and MSISDN in Modify Bearer Response. AllModify Bearer Response messages will send these parameters if CLI is enabled irrespective of scenarios likeS-GW relocation and GnGp to LTE handover. This feature is not license-controlled and the behavior iscontrolled using CLI.

With the previous implementation, P-GW includes the Charging-ID in theModify Bearer Response (MBRsp)only if a change in S-GW is detected where the P-GW compares both new and old S-GW IP addresses. Incases where the operator uses the same IP address for both Gp and S8 interfaces, the P-GW does not detectany S-GW change and does not include the Charging-ID in the Modify Bearer Response during CSFB. Thiscauses the foreign S-GW to terminate the session and forces the UE to reconnect.

This feature introduces new CLI commands to include the following IEs in the Modify Bearer Response onthe S5/S8 PGW GTP-C interface. The default behavior of the CLI is disabled.

The new CLIs will resolve the issues where multiple S-GW or S-GW/SGSN sharing the same IP addressesbehind hub will not be able to detect the S-GW change by P-GW during inter-SGW handover or GnGphandover.

• Charging-ID – P-GW includes the Charging-ID IE in every Modify Bearer Response message in caseof GnGp to LTE HO if it is enabled through CLI or S-GW change is detected.

• Charging FQDN or Charging Gateway Address – P-GW includes the Charging FQDN IE (if available)in every Modify Bearer Response message in case of GnGp to LTE HO if it is enabled through CLI orS-GW change is detected.

• MSISDN – P-GW includes the MSISDN IE in every Modify Bearer Response message in case of GnGpto LTE HO if it is enabled through CLI or S-GW change is detected.

The following table explains the behavior of the new CLI commands enabled or disabled in various scenarios.

CLI ControlMSISDNCharging FQDN orCharging GatewayAddress

Charging-IDScenario

CLI isdisabled.

Standard: Alwayssend

New Behavior:Always send





S-GW relocation (IPaddress change)

CLI isdisabled.

Standard: Do not send

New Behavior: Donot send





S-GW relocation(No IP addresschange)

CLI is enabled.Non standard

New Behavior: Send

Non standard

New Behavior: Send

Non standard

New Behavior: Send

S-GW relocation(No IP addresschange)



CLI ControlMSISDNCharging FQDN orCharging GatewayAddress

Charging-IDScenario

CLI isdisabled.

Standard: Only incase of inter S-GW






GnGp SGSN toMME/S4SGSNhandoff

(Home/Roaming)

(IP address change)

CLI isdisabled.

Standard: Only incase of inter S-GW







(Home/Roaming)

(No IP addresschange)


New Behavior: Send

Non standard

New Behavior: Send

Non standard

New Behavior: Send


(Home/Roaming)

(No IP addresschange)


New Behavior: Send

Non standard

New Behavior: Send

Non standard

New Behavior: Send

S-GW/SGSN doesnot change andMBRsp availablefor all otherscenarios

LimitationsThe limitations with this feature are listed below:

• Charging-ID parameter is part of Bearer Context IE in MBRsp message. In scenarios when BearerContext IE is not going in MBRsp, the Charging-ID parameter will not be sent even if the correspondingCLI configuration is enabled.

• If all parameters are available in P-GW and the CLI configuration is enabled only for specific parameters,then only those parameters are included in the MBRsp message.

• When this feature is enabled on P-GW, it will be applicable to all home and roaming S-GW.

• When this feature is enabled on P-GW, the S-GW needs to additionally include Charging-ID, ChargingFQDN/Charging Gateway address and MSISDN parameters received in Modify Bearer Response, evenif these parameters are not expected to be included. As per Rel. 13 TS 29.274 specification, the S-GWmust discard them.



Configuring parameters in Modify Bearer ResponseUse the following configuration in the P-GW Service Configuration mode to configure parameters –Charging-ID, Charging FQDN or Charging Gateway address, and MSISDN in Modify Bearer Response.These parameters are applicable only forModify Bearer Response. Themodify-bearer-rsp keyword is addedin this release.

configurecontext context_namepgw-service service_nameegtp modify-bearer-rsp { charging-fqdn-or-gw-addr | charging-id | msisdn }{ default | no } egtp modify-bearer-rspend

Notes:

• charging-fqdn-or-gw-addr – Sends Modify Bearer Response with Charging FQDN or ChargingGateway address whichever is present.

• charging-id – Sends Modify Bearer Response with Charging-ID.

• msisdn – Sends Modify Bearer Response with MSISDN.

• default egtpmodify-bearer-rsp –Removes all three parameters while default for individual parameterremoves the corresponding parameter.

All parameters will be disabled by default.

• no egtp modify-bearer-rsp – Removes all three parameters while no for individual parameter removesthe corresponding parameter.

Verifying the ConfigurationEnter the following command in the Execmode to view the configured parameters inModify Bearer Response:

show pgw-service name service_name

Enter the following command in the Exec mode to verify the configuration:

show configuration [ verbose ]

Sample output of the show configuration command:

pgw-service pgw_serviceplmn id mcc 123 mnc 765 primaryassociate ggsn-service ggsn1associate egtp-service pgw_in_egtpegtp modify-bearer-rsp charging-idegtp modify-bearer-rsp charging-fqdn-or-gw-addregtp modify-bearer-rsp msisdnsetup-timeout 55exit

Monitoring and TroubleshootingThis section provides information on the show commands available to support this feature.


P-GW Changes in Release 21.1Configuring parameters in Modify Bearer Response

show pgw-service allThe following new fields are added to the output of this command to indicate the status of the parametersconfigured in Modify Bearer Response message:

• EGTP Modify bearer res with CHARGING-ID – Indicates whether Modify Bearer Response messagewith Charging-ID is enabled or disabled.

• EGTPModify bearer res with CHARGING-FQDNor CHARGING-GW-ADDRESS – Indicates whetherModify Bearer Response message with Charging FQDN or Charging Gateway address is enabled ordisabled.

• EGTP Modify bearer res with MSISDN – Indicates whether Modify Bearer Response message withMSISDN is enabled or disabled.

Monitor Protocol Display for Civic Address FieldCSCvc56186 - [SaMOG LBO-PGW] Gx mon pro: civic-addr missing in TWAN-Identifier decode

Applicable Products: P-GW, SaMOG

Feature ChangesThe P-GW supports Civic Address field in TWAN-Identifier of GTPv2 and Gx interface.

Previous Behavior: The Civic Address field was not displayed in theMonitor Protocol output of Gx interface(Option 75->3) and was not properly displayed for GTPv2 interface (Option 74).

NewBehavior: The Civic Address field is displayed in theMonitor Protocol output of Gx andGTPv2 interface.

NetLoc for WiFi EPCCSCvb38413 - NetLoc Support on S2a/S2b


Applicable Products: P-GW, SAE-GW

Feature DescriptionWith this feature, the IMS network can retrieve location information of the UE fromWLAN access network.This improves location related feature and functionality for the operator. This feature also helps in chargingsubscribers based on location information.

Please note that the support for LTE NetLoc already exists from prior releases. With this release, NetLocsupport is extended for WLAN access. Basic implementation is already supported for passing necessaryparameter to different internal modules like SM, IMSA and ECS.


P-GW Changes in Release 21.1Monitor Protocol Display for Civic Address Field

How It WorksWhen the Application Function (AF) requests the PCRF to report the access network information, the PCRFprovides the requested access network information indication (for example, user location and/or user timezoneinformation) to the PCEF within the Required-Access-Info AVP which is included in theCharging-Rule-Definition AVP of an appropriate PCC rule.

The PCRF also provides the ACCESS_NETWORK_INFO_REPORT event trigger within the Event-TriggerAVP. If the ACCESS_NETWORK_INFO_REPORT event trigger is set, upon installation, modification andremoval of any PCC rule(s) containing the Required-Access-Info AVP, the P-GW determines if it can obtainthe required location information for the used IP CAN type.

During bearer deactivation or UE detach procedure, the P-GW provides the access network information tothe PCRF within the TWAN-Identifier AVP. The P-GW also provides information on when the UE was lastknown to be in that location within the User-Location-Info-Time AVP, and/or UE-Local-IP-Address AVP asapplicable for S2a/S2b interface:

• For Trusted WLAN, the User Location Information (ULI) is provided in the TWAN Identifier AVP.

• For UntrustedWLAN, the ULI contains the TWAN Identifier, the UE’s Local IP address and optionally,UDP source port number (if NAT is detected).

When the ULI is requested by the PCRF and it’s not provided to the PCEF, the PCEF provides the servingPLMN identifier within the 3GPP-SGSN-MCC-MNC AVP. And when the time zone is requested by thePCRF, the PCEF provides it within the 3GPP-MS-TimeZone AVP. Please note that the timezone is applicableonly for Trusted WLAN interface. For WLAN access, the PCEF also includes the AN-Trusted AVP whilereporting access network information.

During the IP-CAN session termination procedure, the PCEFwill, if ACCESS_NETWORK_INFO_REPORTevent trigger is set, provide the access network information to the PCRF by including the ULI (if it wasprovided to the PCEF), the information on when the UE was last known to be in that location withinUser-Location-Info-Time AVP (if it was provided to the PCEF), the PLMN identifier within the3GPP-SGSN-MCC-MNC AVP (if the user location information was not provided to the PCEF) and thetimezone information within the 3GPP-MS-TimeZone AVP.

The WLAN location information received from S2a/S2b interface is reported on all the P-GW supportedinterfaces (Gx, Gy, and Gz).

Accounting RequirementsAs part of accounting requirements, the following Dictionaries are used:

• Gx: r8-gx-standard

• Gy:

• S2a: custom-8 with Rel-11

• S2b: custom-8 with Rel-13

• Gx:

• S2a: custom-48 and custom-52

• S2b: custom-52



The following fields in PGW-CDRs are introduced as part of Gz requirement:

• custom-52 dictionary (as part of uWANUserLocationInfo):

• uELocalIPAddress

• uDPSourcePort

• sSID

• bSSID

The custom-52 is a new standard dictionary introduced in compliance with 3GPP Release 13.

LimitationsThis section identifies the known limitations/restrictions of this feature.

• The User Location Information (ULI) on S2b includes UE local IP address and optionally, UDP sourceport number (if NAT is detected). It also includes WLAN Location Information (and its age). Locationchange is considered if any of the following information changes: UE local IP address, UDP port, orWLAN Location.

• On Gz, for WLAN location change, the ULI change trigger is used.

• On Gy, for WLAN location change, the location_any trigger is used.

• The Rf and S2a RADIUS, and LI interfaces are not considered as part of this feature.

• There are no changes done over S6b interface.

• Only SSID and BSSID of TWAN/UWAN Identifier are considered as part of this feature.

• UE local IP address field is mandatory on Gz and Gy as part of UWANUserLocationInfo.

• For S2b, when the received UWANUserLocationInfo is different than the previousUWANUserLocationInfo, then below are few error case handling:

• For Gy, if the received parameters doesn't contain IP Address, the P-GW doesn’t generate aULI-Change report.

• For Gz, the container with 'ULI change' is closed only when the UWANUserLocationInfo valuecorresponding to the container contains the IP-Address.

• This feature is controlled by NetLoc and Wifi Integration License.

• In case of S2b interface, UE Local IP Address and Port, WLAN ID and WLAN Timestamp are reset to0 if they are not received in CSReq/CBRsp/UBRsp/DBRsp.

• As per 3GPP TS 32.298, TWAN Identifier is present at Record level in Gz.

• The WLAN-timestamp is not sent over Gy and Gz interface.

• The UE-location-IP-Address change event trigger is not part of this feature.

• The EPC_Routed Feature (Reference 3GPP TS 29.212) is not supported.



Configuring the NetLoc for WiFi EPC FeatureThe following sections provide the configuration commands to enable the feature.

Configuring the NetLoc TWAN for GxThe commands illustrated below configures the NetLoc trusted WLAN feature over Gx interface.


ims-auth-service service_namepolicy-control

diameter encode-supported-features netloc-trusted-wlanend

Notes:

• no diameter encode-supported-features: Disables the feature.

• This command takes effect when Gx is enabled on S2b call.

• By default, the feature is disabled and TWAN information will not be sent over Gx.

Configuring the NetLoc UWAN for GxThe commands illustrated below configures the NetLoc untrusted WLAN feature over Gx interface.


ims-auth-service service_namepolicy-control

diameter encode-supported-features netloc-untrusted-wlanend

Notes:

• no diameter encode-supported-features: Disables the feature.

• This command takes effect when Gx is enabled on S2b call.

• By default, the feature is disabled and UWAN information will not be sent over Gx.

Configuring the NetLoc UWAN for GyThe commands illustrated below configures dictionary control of the AVPs that need to be added based on3GPP Rel.13.

active-charging serviceservice_namecredit-control

diameter update-dictionary-avps 3gpp-rel13end

Notes:

• no diameter update-dictionary-avps: Disables the feature.

• This command takes effect when Gy is enabled on S2b call.


P-GW Changes in Release 21.1Configuring the NetLoc for WiFi EPC Feature

• By default, the feature is disabled and UWAN information will not be sent over Gy.

Configuring the NetLoc UWAN for GzThe commands illustrated below configures the NetLoc untrusted WLAN feature over Gz interface.


gtpp group group_namegtpp attribute uwanuliend

Notes:

• no gtpp attribute uwanuli: Disables the feature.

• This command takes effect when Gz is enabled on S2b call.

• By default, the feature is disabled and UWAN information will not be sent over Gz.

Monitoring and Troubleshooting the NetLoc for WiFi EPC FeatureThis section provides information regarding show commands and/or their outputs in support of this feature.

Show Commands and/or OutputsThe following table lists the CLI commands that will help to monitor and/or troubleshoot this feature.

DescriptionCLI Commands

Displays the following newly introduced fields forwhich the values will be populated on S2a/S2b calls:TWAN User Location Information:

SSID:BSSID:

UWAN User Location Information:UE Local IP Address:UDP Port:SSID:BSSID:

show subscribers pgw-only full all

show subscriber saegw-only full all

Displays the following newly introduced fields forwhich the values will be populated when they areconfigured as Supported Features AVP in IMSAuthorization Service Configuration mode:

• netloc-trusted-wlan

• netloc-untrusted-wlan

show ims-authorization service all verbose


P-GW Changes in Release 21.1Monitoring and Troubleshooting the NetLoc for WiFi EPC Feature

DescriptionCLI Commands

Displays the following newly introduced field forwhich the value will be populated when the gtppattribute uwanuli CLI command is configured inthe GTPP Server Group configuration mode:

• UWAN User Location Information present:

show gtpp group all

Support for Node Identifier IE Type in Create Session RequestCSCvc11894 - PGW selecting ePDG provided AAA on S6b


This feature is only available if the Sending SWm 3GPP AAA FQDN Address in CSReq feature is enabledon the ePDG.

Important

Related CDETS: CSCvc78782


Feature DescriptionWith this feature, the P-GW will use the same 3GPP-AAA server, as ePDG, for a particular user on S6binterface. In compliance with 3GPP TS 29.274, support is added to encode a new Information Element (IE)type called “Node Identifier” in Create Session Request. For additional details, refer the 3GPP TS 29.274-d50section 7.2.1 and section 8.107.

LimitationsThis section identifies the limitations of this feature.

• DRA scenario is not supported.

• If peer entry is not found on the P-GW, call is established with existing selection logic.

• If peer entry is found but it does not respond, existing selection logic will be followed.

P-GW Accepts Modify Bearer Command Request from Old S-GWCSCvc30269 - Modify Bearer Command from old SGW is being honoured although call moves to new SGW



P-GW Changes in Release 21.1Support for Node Identifier IE Type in Create Session Request

Feature ChangesIn Cisco P-GW after successful S-GW relocation, if the old S-GW sends theModify Bearer Command request,the P-GW accepts it and proceeds with normal processing. This issue occurs when there is a delay or latencyin the network during S-GW relocation when the Delete Session Request does not reach the old S-GW beforeit sends the Modify Bearer Command request to the P-GW. The current release resolves this issue.

Previous Behavior: After successful S-GW relocation, the P-GW accepts re-transmitted Modify BearerCommand request from the old S-GW and processes it like it was received from the new S-GW.

New Behavior: After successful S-GW relocation, P-GW does not accept the Modify Bearer Commandrequest from the old S-GW. Instead, the P-GW sends a Modify Bearer Failure Indication with cause code"Invalid Peer".





Documents

P-GW Changes in Release 21 - Cisco...Tocomplywiththe“LongTermEvolution(LTE)AccessNetworkGovernmentIndustryRequirements(GIR) forNationalSecurity/EmergencyPreparedness(NS/EP)NextGenerationNetwork(NGN)Priority”tosupport