S6B-bypass Support for eMPS Session

This chapter describes the following topics:

• Feature Summary and Revision History, on page 1• Feature Changes, on page 2• Command Changes, on page 2• Performance Indicator Changes, on page 3

Feature Summary and Revision HistorySummary Data

• P-GW

• SAE-GW

Applicable Product(s) or FunctionalArea

• ASR 5500

• VPC - DI

• VPC - SI

Applicable Platform(s)

Disabled - Configuration RequiredDefault Setting

Not ApplicableRelated Changes in This Release

• Command Line Interface Reference

• P-GW Administration Guide

• SAE-GW Administration Guide

Related Documentation

Revision History

ReleaseRevision Details

21.8S6B bypass is implemented during S6B authorization/re-authorization failuresfor eMPS Sessions

S6B-bypass Support for eMPS Session1

ReleaseRevision Details

21.3First introduced.

Feature ChangesEnhanced Multimedia Priority Services (eMPS) sessions can be created successfully in case of S6Bauthorization/re-authorization failures by using locally configured S6B values. To ensure continuous eMPSsessions, S6B bypass is implemented during S6B authorization/re-authorization failures. The S6B bypass isimplemented in the following scenarios:

• For advance priority users when processing the Create Session Request (WPS ARP).

• When P-GW performs authorization and re-authorization for existing eMPS sessions.

A new keyword emps is added as part of the failure-handling-template configuration in the AAA ServerGroup Configurationmode to provide S6B bypass only for eMPS subscribers during S6B failures. The operatorshould configure the emps keyword with the failure-handling-template to provide failure handling for eMPSsubscribers. If failure-handling-template is configured without emps keyword, failure handling is applied toall subscribers.

Failure handling for eMPS subscribers in AAAGroup is implemented only with the failure-handling templatemechanism.

Note

The S6B-bypass for an eMPS session functionality includes the following:

• Once P-GW assumes bypass for an eMPS session, it doesn’t not perform authorization/re-authorizationfor subsequent scenarios.

• In a new call establishment or in aWIFI to LTE hand-off scenario, the S6B authorization/re authorizationAAR messages for eMPS is sent on the basis of default bearer ARP only because the type of dedicatedbearer; whether eMPS or not, is unknown. S6B authorized/reauthorized request initiation will occurbefore the PCRF communication for creating a dedicated bearer.

• Changes to the configuration during run-time is applied to all S6B transactions initiated after theconfiguration change

The S6B-bypass Support for eMPS Sessions is license controlled. Contact your Cisco account representativefor detailed information on specific licensing requirements. For information on installing and verifying licenses,refer to the Managing License Keys section of the Software Management Operations chapter in the SystemAdministration Guide

Command ChangesThis section describes the CLI configuration required to enable S6B-bypass Support for eMPS Sessions

S6B-bypass Support for eMPS Session2

S6B-bypass Support for eMPS SessionFeature Changes

empsThe emps keyword implements the failure-handling template for eMPS subscribers during S6Bauthorization/re-authorization failures.

Use the following configuration to enable failure-handling for eMPS subscribers:

configurecontext context_name

aaa groupgroup_namediameter authentication failure-handling-template template_name emps

[ no ] diameter authentication failure-handling-template empsend

NOTES:

• failure-handling template: Associates a previously created failure handling template with theauthentication application in the AAA group. The template_name specifies the name for a pre-configuredfailure handling template. The template_namemust be an alphanumeric string of 1 through 63 characters.By default, the template is not associated in the AAA group.

• emps: This keyword specifies the failure-handling behavior for eMPS Sessions applicable during S6Bauthorization and re-authorization.

• no: Disassociates the failure-handling template with the AAA group authentication.

Performance Indicator ChangesThis section provides information regarding show commands and/or their outputs in support of this feature.

show diameter aaa-statistics allOn executing the above command the following new field is displayed for this feature:

• FH Behavior (eMPS)

• Continue

• With Retry

• Without Retry

• Retry and Terminate

• Retry and Terminate

• Retry Term without STR

• Termination

• Terminate

• Terminate without STR

S6B-bypass Support for eMPS Session3

S6B-bypass Support for eMPS Sessionemps

Bulk StatisticsThe following bulk statistics are added in the Diameter-Auth Schema for the S6B Bypass Support for eMPSSessions feature

• fh-continue-retry-emp: Indicates the number of times failure handling action “continue” is taken usingthe eMPS template..

• fh-continue-wo-retry-emps: Indicates the number of times the failure handling action “continue withoutretry” is taken using eMPS template.

• fh-retry-and-term-emps: Indicates the number of times failure handling “retry and terminate” is takenusing eMPS template.

• fh-retry-and-term-wo-str-emps: Indicates the number of times failure handling “retry and terminatewithout STR” is taken using eMPS template.

• fh-terminate-emps: Indicates the number of times failure handling “terminate” is taken using eMPStemplate.

• fh-terminate-wo-str-emps: Indicates the number of times failure handling “terminate without STR” istaken using eMPS template.

S6B-bypass Support for eMPS Session4

S6B-bypass Support for eMPS SessionBulk Statistics