P-GW Changes in Release 21.2

Transcription

1 P-GW Changes in Release This chapter identifies features and functionality added to, modified for, or deprecated from the P-GW in the StarOS 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-GW Administration Guide for this release. Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line Interface 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 information on the show commands, refer to the Statistics and Counters Reference for this release. For detailed information on the counters and disconnect reasons, refer to the BulkstatStatistics_documentation.xls spreadsheet that is 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 various multi-product enhancements sections, some of which might include content applicable to your P-GW. AAA Changes CF Changes ECS Changes GTPP Changes Lawful Intercept Changes NAT Changes SNMP MIB Changes System and Platform Changes P-GW changes for include: 3GPP Changes to the Gx Interface, page 2 APN Configuration Errors Display, page 3 1

2 3GPP Changes to the Gx Interface P-GW Changes in Release Auto Correction of VoLTE Sessions, page 5 Cisco Ultra Traffic Optimization, page 8 Civic Address Display Format Changed in Monitor Protocol and show subscribers pgw-only full all Command Output, page 18 CLI Configuration for APN String, page 19 Error Message Provides Additional Information for TDF Ruledef Validation, page 21 FAPA Disabled Due to Bandwidth Policy Usage, page 22 Inclusion of APN AMBR in the Create Session Response, page 23 Incorrect Cause Code in Create Session Response by P-GW, page 25 Increase in ARP Support, page 26 NEMO-LMA Heartbeat, page 29 Piggyback Support on S2b Interface, page 32 Spare Protocol Types Supported in RAN-NAS IE for S2b Interface, page 33 Update Bearer Request Sends Exact Same CRI in CCA-U for Dynamic Rule Already Installed, page 34 3GPP Changes to the Gx Interface Feature Information Summary Data Status Introduced-In Release Modified-In Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Modified Functionality 21.1 P-GW, SAEGW ASR 5500 Yes, only for Customer specific Gx Dictionary. CSCvc99275 P-GW Administration Guide SAEGW Administration Guide 2

3 P-GW Changes in Release Feature Changes Revision History Revision history details are not provided for features introduced before release. Revision Details Modified in this release. Release Release Date April 27, 2017 Feature Changes Currently, P-GW sends 3GPP-User-Location-Info AVP in CCR-U for the event trigger Successful_Resource_Allocation, only if there is a change in the ULI. This feature has been implemented to comply with the 3GPP specifications. With this feature, P-GW sends 3GPP-User-Location-Info in CCR-U for the event trigger Successful_Resource_Allocation, even if there is no a change in the ULI. If the Resource-Allocation-Notification AVP is included in the Charging-Rule-Install AVP, 3GPP-User-Location-Information is included in the CCR-U sent towards the PCRF. Limitations Following are the limitations of this feature: 1 This feature works with diameter dictionary dpca-custom8. 2 Resource-Allocation-Notification AVP should be included within a Charging-Rule-Install AVP while installing/modifying rule. APN Configuration Errors Display Feature Summary Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Modified Functionality P-GW 3

4 Feature Changes P-GW Changes in Release Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation ASR 5500 Enabled CSCvc44163 Release Change Reference Revision History Revision history details are not provided for features introduced before release. Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes Previous Behavior: In releases prior to, configuration errors were not flagged for a condition where: 1 Rulebase associated with an APN contains the CLI 'billing-records egcdr' (generation of ACS Gz records) and, 2 GTPP group associated with an APN does not have a valid GTPP dictionary configuration (Gz billing cannot be done without this.) New Behavior: From release onwards, errors for the above mentioned condition is flagged in the following format: [local]asr5000# show configuration errors section apn ###################################################################################################### Displaying APN-configuration errors ###################################################################################################### Error : Rulebase <rulebase_name> configured for APN <apn_name> dictates generation of egcdrs/pgwcdr's but associated GTPP group <group_name> does not have a valid GTPP dictionary configuration. Total 1 error(s) in this section! Additionally, warning logs are triggered when a call is brought up on such APN's. 4

5 P-GW Changes in Release Auto Correction of VoLTE Sessions Auto Correction of VoLTE Sessions Feature Information Summary Data Status Introduced-In Release Modified-In Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Modified Functionality P-GW ASR 5500 Disabled CSCvc72275 P-GW Administration Guide Command Line Interface Reference Revision History Revision history details are not provided for features introduced before Release. Revision Details New in this release. Release Release Date April 27, 2017 Feature Description When dynamic rules for IP Multimedia Subsystem (IMS) sessions are lost after a switchover, VoLTE calls are impacted. To recover the calls, the IMS sessions have to be cleared manually to re-establish the PDN with the correct dynamic rules. The Auto Correction of VoLTE Sessions feature enables a dynamic rule check such that when the P-GW receives an RAR (Re-Auth-Request) message, it automatically identifies and rectifies the issue without manual intervention. This features only applies to the APN that is configured on that uses the "RAR" message as a trigger for the check. 5

6 How It Works P-GW Changes in Release How It Works After the APN receives any RAR message from the Policy Control and Charging Rules Function (PCRF), a Re-Auth- Answer (RAA) message is immediately sent. When the feature is enabled, an additional check is done at the P-GW to verify if there are any dynamic rules associated with the default bearer. Assuming the Session Initiation Protocol (SIP) rule on the default bearer is recovered, other dedicated bearers are also recovered. If dynamic rules are not associated with the default bearer, the call is terminated. Then, a Delete Bearer Request is sent for the default bearer with the cause code - Reactivation Required. To ensure the reason code is sent, the APN must be configured with "pdn-behavior ims". Subsequently, a Credit-Control-Request-Type (CCR-T) is sent to PCRF and other diameter interfaces (s6b, Gy, and Rf). Thereby, the automatic recovery procedure involves termination of a subscriber connection when an anomaly is detected. The subscriber has to then reconnect to the network. The mobile originated or terminated call is rejected for the subscriber where the dynamic rules are lost after a switchover. Configuring the Auto Correction of VoLTE Sessions Feature The following section provides the configuration commands to enable or disable the feature. Enabling or Disabling the Dynamic Rule Check The new CLI command, pdn validate-post-switchover, is added to enable the dynamic rule check for the auto correction of the VoLTE session. To enable this feature, configure the command at the base APN. This feature should be configured only for the VoLTE/IMS APNs for which auto recovery is required. This feature is disabled by default. To enable or disable the feature, enter the following commands: Notes: configure context <context_name> apn <apn_name> [no] pdn validate-post-switchover end no: Disables the configured Auto correction of VoLTE sessions on the base APN. pdn validate-post-switchover: Validates the dynamic rules for automatic recovery after a switchover. Monitoring and Troubleshooting This section provides information regarding show commands and/or their outputs in support of the Auto Correction of VoLTE Sessions feature. Show Commands This section lists all the show commands available to monitor this feature. 6

7 P-GW Changes in Release Monitoring and Troubleshooting show configuration apn The above CLI command is introduced to check if the feature is enabled at the APN level. If "pdn validate-post-switchover" is present then the feature is enabled. show active-charging service statistics This command has been modified to display the following output: show active-charging service statistics ACS Data Statistics: Packets Dropped due to System-Limit L4-Flows: 0 Packets Dropped - Invalid Len in IP Hdr(Dwlink): 0 Packets Dropped - Invalid Ver in IP Hdr(Dwlink): 0 Packets Not Processed due to Flow-limit: 0 Packets Not Processed due to CLP not found: 0 Packets Dropped CLP in Preservation Mode: 0 Total Pkts: 0 Total Collisions in data session hash: 0 ACS Reject Reason: RuleBase Mismatch : 0 Bandwidth-Policy Mismatch : 0 CBB-Policy Mismatch : 0 CF Policy Mismatch : 0 No RuleBase configured in APN/Subs: 0 No active rule in Rulebase/Subs: 0 No Bandwidth-Policy configured in APN/Subs: 0 No Resources: 0 Max Sessions: 0 Reject Probability Exceeded: 0 Rule Recovery Failed: 0 CDR Flow Control Initiated: 0 Protocol Reject stats: WTP Non-initial PDU: 0 WSP-CO Non-initial Connect PDU 0 Dynamic Rule Statistics: Total Subscribers: 0 Current Subscribers: 0 Charging Msg Received: 0 Rule Defn Received: 0 Installs Received: 0 Removes Received: 0 Installs Succeeded: 0 Removes Succeeded: 0 ADC Rules Received: 0 Total ADC Rules: 0 ADC Install Succeeded: 0 ADC Install Failed: 0 ADC Custom Mute Received: 0 ADC Custom Unmute Received: 0 ADC Start Sent: 0 ADC Stop Sent: 0 L7 Rules Received: 0 L7 Install Succeeded: 0 L7 Install Failed: 0 Installs Failed: 0 Removes Failed: 0 Install Failure Reason: No Resources: 0 No Rulebase Match: 0 No RuleName Match: 0 Rulebase Count Exceeded: 0 Local Copy Failed: 0 Invalid Protocol: 0 Invalid Source Mask: 0 Invalid Dest Mask: 0 No Grp-of-Rdef Match: 0 ADC Invalid Rule: 0 ADC Invalid Readdress: 0 L7 Rule Invalid: 0 L7 Protocol Invalid: 0 L7 Field Invalid: 0 L7 Operator Invalid: 0 L7 Value Invalid: 0 L7 Case-Sens Invalid: 0 Remove Failure Reason: No RuleName Match: 0 No Grp-of-Rdef Match: 0 Local Copy Failed: 0 Bandwidth Limiting Statistics: ITC Drops: Uplink Packets: 0 Uplink Bytes: 0 7

8 Cisco Ultra Traffic Optimization P-GW Changes in Release Downlink Packets: 0 Downlink Bytes: 0 Dynamic Rule Bandwidth Limiting Drops: Uplink Packets: 0 Uplink Bytes: 0 Downlink Packets: 0 Downlink Bytes: 0 Per-Bearer Bandwidth Limiting Drops: Uplink Packets: 0 Uplink Bytes: 0 Downlink Packets: 0 Downlink Bytes: 0 Credit-Control Group Statistics: CC Dropped Uplink Packets: 0 CC Dropped Uplink Bytes: 0 CC Dropped Downlink Packets: 0 CC Dropped Downlink Bytes: 0 Readdressing Failure Statistics (Packets): Non SYN Flow: 0 Duplicate Key: 0 Dropped Pkts: 0 First-request-only redirections: 0 Fallback Statistics: Bandwidth Policy Applied: 0 Bandwidth Policy Failed: 0 Bulk Statistics This section lists all the bulk statistics that have been added, modified, or deprecated to support this feature. ECS Schema This section displays the new bulk stats that have been added to indicate dynamic recovery failure : dyn_rule_recovery_failure: The total number of sessions terminated due to dynamic rule recovery failure. dyn_rule_recovery_num_sess_not_terminated: The total number of sessions that are not terminated after switchover because dynamic rules were not installed on the default bearer. Cisco Ultra Traffic Optimization Feature Information Summary Data Status Introduced-In Release Modified-In Release(s) Applicable Product(s) New Feature P-GW 8

9 P-GW Changes in Release Overview Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation ASR 5500 Disabled CSCvc19391 P-GW Administration Guide Command Line Interface Reference Guide Revision History Revision history details are not provided for features introduced before release. Revision Details New in this release. Release Release Date April 27, 2017 Overview In a high-bandwidth bulk data flow scenario, user experience is impacted due to various wireless network conditions and policies like shaping, throttling, and other bottlenecks that induce congestion, especially in the RAN. This results in TCP applying its saw-tooth algorithm for congestion control and impacts user experience, and overall system capacity is not fully utilized. The Cisco Ultra Traffic Optimization (CUTO) solution provides clientless optimization of TCP and HTTP traffic. The CUTO solution is integrated with Cisco P-GW and has the following benefits: Increases the capacity of existing cell sites and therefore, enables more traffic transmission. Improves Quality of Experience (QoE) of users by providing more bits per second. Provides instantaneous stabilizing and maximizing per subscriber throughput, particularly during network congestion. How CUTO Works The CUTO solution achieves its capabilities by: Stabilizing the TCP session at given or optimum target bandwidth. Monitoring the TCP session and minimizing bursts. Timing adjustment without discarding packets, and with limited buffering. Stabilizing and reducing TCP performance jitter. 9

10 How CUTO Works P-GW Changes in Release Increasing the number of simultaneous sessions served and reducing connection latency. Providing adequate logging information for debugging and operability. Architecture StarOS has a highly optimized packet processing framework, the CUTO engine, where the user packets (downlink) are processed in the operating systems user space. The high-speed packet processing, including the various functions of the P-GW, is performed in the user space. The CUTO engine is integrated into the packet processing path of Cisco s P-GW with a well-defined Application Programming Interface (API) of StarOS. The following graphic shows a high-level overview of P-GW packet flow with Traffic Optimization. Handling of Traffic Optimization Data Record The Traffic Optimization Data Record (TODR) is generated only on the expiry of idle-timeout of the CUTO engine. No statistics related to session or flow from P-GW is included in this TODR. The data records are a separate file for the Traffic Optimization statistics and available to external analytics platform. 10

11 P-GW Changes in Release How CUTO Works List of Attributes and File Format All TODR attributes of Traffic Optimization is enabled by a single CLI command. The output is always comma separated, and in a rigid format. Standard TODR The following is the format of a Standard TODR: instance_id,flow_type,srcip,dstip,policy_id,dscp, flow_first_pkt_rx_time_ms,flow_last_pkt_rx_time_ms,flow_cumulative_rx_bytes Example: 1,0, , ,0,0, , , Where: instance_id: Instance ID. flow_type: Standard flow (0) srcip: Indicates the source IP address. dstip: Indicates the destination IP address. policy_id: Indicates the Traffic Optimization policy ID. dscp: Indicates the DSCP code for upstream packets. flow_first_pkt_rx_time_ms: Indicates the timestamp of when the first packet was detected during the Traffic Optimization. flow_last_pkt_rx_time_ms: Indicates the timestamp of when the last packet was detected during the Traffic Optimization. flow_cumulative_rx_bytes: Indicates the number of bytes transferred by this flow. Large TODR The following is a sample output of a Large TODR. 2,1,2606:ae00:c663:b66f:0000:0058:be03:ae01,0172:0020:0224:0059:2200:0000:0000:0033,0,0, , , , ,3900,3900,0,0,0,11,0,0,11,1,1, ,1950,4,0,0,1, ,0,2010,0,0,1, ,0,2007,0,0,1, ,0,2008, 0,0,1, ,0,2005,0,0,1, ,0,2003,0,0,1, ,0,2005,0,0,1, ,0, 2003,0,0,1, ,0,1848,0,0,0, ,0,2002,0,0,1, ,0,107,0,0 Where: instance_id: Instance ID. flow_type: Large flow (1) srcip: Indicates the source IP address. dstip: Indicates the destination IP address. policy_id: Indicates the Traffic Optimization policy ID. dscp: Indicates the DSCP code for upstream packets. flow_first_pkt_rx_time_ms: Indicates the timestamp of when the first packet was detected during the Traffic Optimization. 11

12 How CUTO Works P-GW Changes in Release flow_last_pkt_rx_time_ms: Indicates the timestamp of when the last packet was detected during the Traffic Optimization. flow_cumulative_rx_bytes: Indicates the number of bytes transferred by this flow. large_detection_time_ms: Indicates the timestamp of when the flow was detected as Large. avg_burst_rate_kbps: Indicates the average rate in Kbps of all the measured bursts. avg_eff_rate_kbps: Indicates the average effective rate in Kbps. final_link_peak_kbps: Indicates the highest detected link peak over the life of the Large flow. recovered_capacity_bytes: Indicates the recovered capacity in Kbps for this Large flow. recovered_capacity_ms: Indicates the timestamp of recovered capacity for this Large flow. phase_count: Indicates the Large flow phase count. min_gbr_kbps: Indicates the Minimum Guaranteed Bit Rate (GBR) in Kbps. max_gbr_kbps: Indicates the Maximum Guaranteed Bit Rate (MBR) in Kbps. phase_count_record: Indicates the number of phases present in this record. end_of_phases: 0 (not end of phases) or 1 (end of phases). Large flow phase attributes: phase_type: Indicates the type of the phase phase_start_time_ms: Indicates the timestamp for the start time of the phase. burst_bytes: Indicates the burst size in bytes. burst_duration_ms: Indicates the burst duration in milliseconds. link_peak_kbps: Indicates the peak rate for the flow during its life. flow_control_rate_kbps: Indicates the rate at which flow control was attempted (or 0 if non-flow control phase). Licensing The CUTO is a licensed Cisco solution. Contact your Cisco account representative for 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 System Administration Guide. Limitations and Restrictions The values which the P-GW chooses to send to the CUTO engine are the values associated from the bearer GBR and bearer MBR. For this release, only downlink GBR and MBR are sent to the engine for Traffic Optimization. 12

13 P-GW Changes in Release Configuring CUTO Configuring CUTO This section provides information on enabling support for the CUTO solution. Loading Traffic Optimization Use the following command under the Global Configuration Mode to load Traffic Optimization as a solution: configure require active-charging traffic-optimization Enabling or disabling the Traffic Optimization can be done through the Service-scheme framework. Enabling CUTO Configuration Profile Use the following command under ACS Configuration Mode to enable the Traffic Optimization profile: configure active-charging service service_name traffic-optimization-profile end Notes: The above CLI command enables config-traffic-optim, a new configuration mode. Configuring the Operating Mode Use the following command to configure the operating mode under Traffic Optimization Profile Mode for the CUTO Library: configure active-charging service service_name traffic-optimization-profile mode [ active passive ] end Notes: mode: Sets the mode of operation for Traffic Optimization. active: Active mode where both Traffic Optimization and flow monitoring is done on the packet. passive: Passive mode where no flow-control is performed but monitoring is done on the packet. Configuring Threshold Value Use the following command to configure the threshold value for the TCP flow to be considered for the CUTO: configure active-charging service service_name traffic-optimization-profile 13

14 Configuring CUTO P-GW Changes in Release Notes: heavy-session detection-threshold bytes end detection-threshold bytes: Specifies the Detection Threshold (in bytes), beyond which it is considered as heavy session. bytes must be an integer from 1 to For optimum Traffic Optimization benefits, it is recommended to set the threshold above 3 MB. Enabling CUTO Configuration Profile Using Service-scheme Framework The service-scheme framework is used to enable TCP Optimization at APN, Rulebase, QCI and Rule level. There are two main constructs for the service-scheme framework: Subscriber-base This helps in associating subscribers with service-scheme based on the subs-class configuration. subs-class The conditions defined under subs-class enables in classifying the subscribers based on rule-base, APN, v-apn name. The conditions can also be defined in combination, and both OR as well as AND operators are supported while evaluating them. Service-scheme This helps in associating actions based on trigger conditions which can be triggered either at call-setup time, Bearer-creation time, or flow-creation time. trigger-condition For any trigger, the trigger-action application is based on conditions defined under the trigger-condition. trigger-actions Defines the actions to be taken on the classified flow. These actions can be Traffic Optimization, throttle-suppress, and so on. Session Setup Trigger The any-match = TRUE, a wildcard configuration, is the only supported condition for this trigger and so this is applicable to all the flows of the subscriber. Following is a sample configuration: config active-charging service service_name trigger-action trigger_action_name traffic-optimization trigger-condition trigger_condition_name1 any-match = TRUE service-scheme service_scheme_name trigger sess-setup priority priority_value trigger-condition trigger_condition_name1 trigger-action trigger_action_name subs-class sub_class_name apn = apn_name 14

15 P-GW Changes in Release Configuring CUTO subscriber-base subscriber_base_name priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name end Bearer Creation Trigger The trigger conditions related to QCI can be used for this trigger, and so this is applicable to all the flows of specific bearers. The following is a sample configuration: configure active-charging service service_name trigger-action trigger_action_name traffic-optimization trigger-condition trigger_condition_name1 any-match = TRUE trigger-condition trigger_condition_name2 qci = qci_value service-scheme service_scheme_name trigger bearer-creation priority priority_value trigger-condition trigger_condition_name2 trigger-action trigger_action_name subs-class sub_class_name apn = apn_name subscriber-base subscriber_base_name priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name end Flow Creation Trigger The trigger conditions related to rule-name and QCI can be used here, and so this is related to specific flow. The following is a sample configuration: configure active-charging service service_name trigger-action trigger_action_name traffic-optimization trigger-condition trigger_condition_name1 any-match = TRUE trigger-condition trigger_condition_name2 qci = qci_value trigger-condition trigger_condition_name3 rule-name = rule_name 15

16 Configuring CUTO P-GW Changes in Release service-scheme service_scheme_name trigger bearer-creation priority priority_value trigger-condition trigger_condition_name3 trigger-action trigger_action_name subs-class sub_class_name apn = apn_name subscriber-base subscriber_base_name priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name Notes: end trigger_condition_name3 can have only rules, only QCI, both rule and QCI, or either of rule and QCI. The following table illustrates the different levels of Traffic Optimization and their corresponding Subscriber Class configuration and Triggers. Traffic Optimization Levels Applicable to all the calls or flows Applicable to all calls or flows of a rulebase Applicable to all calls or flows of an APN Applicable to all flows of a Bearer Applicable to a particular flow Subscriber Class configuration and Triggers subs-class sc1 any-match = TRUE Sessetup trigger condition is any-match = TRUE subs-class sc1 rulebase = prepaid Sessetup trigger condition is any-match = TRUE subs-class sc1 apn = cisco.com Sessetup trigger condition is any-match = TRUE trigger-condition TC1 qci = 1 Bearer creation trigger condition is TC1 trigger-condition TC1 qci = 1 rule-name = tcp multi-line-or all-lines Flow creation trigger condition is TC1 In case of LTE to ehrpd handover, since QCI is not valid for ehrpd, it is recommended to configure rule-name as the trigger-condition under service-scheme. 16

17 P-GW Changes in Release Monitoring and Troubleshooting Generating TODR Use the following command under ACS Configuration Mode to enable the Traffic Optimization Data Record (TODR) generation: configure active-charging service service_name traffic-optimization-profile data-record end Notes: If previously configured, use the no data-record command to disable generating TODR. Monitoring and Troubleshooting This section provides information regarding commands available to monitor and troubleshoot the CUTO on the P-GW. CUTO Show Commands and/or Outputs This section provides information regarding show commands and their outputs in support of CUTO solution. show active-charging traffic-optimization counters The show active-charging traffic-optimization counters sessmgr { all instance number } is a newly introduced command where: counters Displays aggregate flow counters/statistics from CUTO engine. This CLI command is license dependent and visible only if the license is loaded. The following is a sample output: show active-charging traffic-optimization counters sessmgr all Traffic Optimization Flows: Active Normal Flow Count : 0 Active Large Flow Count : 0 Active Managed Large Flow Count : 0 Active Unmanaged Large Flow Count : 0 Total Normal Flow Count : 0 Total Large Flow Count : 0 Total Managed Large Flow Count : 0 Total Unmanaged Large Flow Count : 0 Total IO Bytes : 0 Total Large Flow Bytes : 0 Total Recovered Capacity Bytes : 0 Total Recovered Capacity ms : 0 show active-charging traffic-optimization info This is a newly introduced show command in Exec Mode where: 17

18 Civic Address Display Format Changed in Monitor Protocol and show subscribers pgw-only full all Command Output P-GW Changes in Release traffic-optimization Displays all Traffic Optimization options. info Displays CUTO engine information. The output of this CLI command displays the version, mode, and configuration values. The following is a sample output: show active-charging traffic-optimization info Version : Mode : Active Configuration: Threshold Bytes : Lower Bandwidth : 0 Upper Bandwidth : 0 Min Session Time : 0 Min Session Size : 0 Civic Address Display Format Changed in Monitor Protocol and show subscribers pgw-only full all Command Output Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Modified Functionality P-GW ASR 5500 Enabled CSCvc75489 P-GW Administration Guide Revision History Revision history details are not provided for features introduced before release. 18

19 P-GW Changes in Release Feature Changes Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes The civic address displayed in the show subscribers pgw-only full all command output and the civic address displayed in the monitor protocol of the Gy and Gz interfaces is required to be reformatted for better clarity. The current release addresses this change. Previous Behavior: The civic address in the show subscribers pgw-only full all command output and the civic address in the monitor protocol of the Gy and Gz interfaces used to be displayed as follows (CIVIC Address : IN234grna). Gy Monitor Protocol Output: Civic-Addr: IN234grna Gz Monitor Protocol Output: twanuserlocationinformation civicaddress IN234grna Command Output: show sub pgw-only full all TWAN User Location Information: SSID : blizzard BSSID : AA:A0:C9:00:C8:29 CIVIC Address : IN234grna New Behavior: In the show subscribers pgw-only full all command output, the civic address for the Gy and Gz interfaces is now displayed as follows: Gy Monitor Protocol Output: Civic-Addr: CC:IN CAType:23 CALen:4 CAVal:grna, Gz Monitor Protocol Output: twanuserlocationinformation civicaddress Command Output: CC:IN CAType:23 CALen:4 CAVal:grna show sub pgw-only full TWAN User Location Information CIVIC Address : CC:IN CAType:23 CALen:4 CAVal:grna, CLI Configuration for APN String Feature Summary Summary Data Status Modified Functionality 19

20 Feature Changes P-GW Changes in Release Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation P-GW ASR 5500 Enabled CSCvc94975 P-GW Administration Guide Revision History Revision history details are not provided for features introduced before Release. Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes When an APN name is configured, if an extra period is added in the APN name, it duplicates the APN name leading to assert in the egtpinmgr. The current release resolves this issue. Previous Behavior: When an APN name was configured with an extra period, the APN string was accepted with a NULL token. For example, apn internet.com and apn internet..com was allowed. New Behavior: When an APN name is configured with an extra period, an error is displayed thereby disallowing the use of apn internet.com and apn internet..com strings. Impact on Customer: Configuring null token APN string is not allowed. The advantage in this release is that an error is displayed in the egtpinmgr when a null token APN string is configured. 20

21 P-GW Changes in Release Error Message Provides Additional Information for TDF Ruledef Validation Error Message Provides Additional Information for TDF Ruledef Validation Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Modified Functionality P-GW, S-GW, SAEGW, GGSN ASR 5500 Enabled CSCvc39124 Release Change Reference Revision History Revision history details are not provided for features introduced before release. Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes Dynamic TDF ruledefs are shown as errors in the show config errors command output. This issue is seen when the dynamic TDF application-based ruledefs are configured under ECS (Active Charging Service) and not included in the rulebase. The error message in the log is very concise and limited in information. The current release addresses this issue. Previous Behavior: 21

22 FAPA Disabled Due to Bandwidth Policy Usage P-GW Changes in Release Dynamic TDF ruledefs configured in the Active Charging Service that do not have any reference to the local rulebases are displayed as errors in the show configuration errors command output with limited information: Error : Ruledef <7-7-FOTA-ONSTAR-DYNAMIC-CNT-01> is not used in any rulebase or group-of-ruledefs. Error : group-of-ruledefs <group> is not used in any rulebase. New Behavior: When dynamic TDF ruledefs are configured in the Active Charging Service and are not included in the local rulebase, the show configuration errors command output continues to display them as errors. These errors now provide additional information thereby indicating the possibility that the configured ruledef can be ADC: Error : Ruledef <7-7-FOTA-ONSTAR-DYNAMIC-CNT-01> is not used in any rulebase or group-of-ruledefs. It can be a dynamically enabled ADC ruledef and could be ignored. Error : group-of-ruledefs <group> is not used in any rulebase. It can be a dynamically enabled ADC group and could be ignored. FAPA Disabled Due to Bandwidth Policy Usage Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Modified Functionality P-GW ASR 5500 Enabled CSCvd34551 P-GW Administration Guide Revision History Revision history details are not provided for features introduced before release. 22

23 P-GW Changes in Release Feature Changes Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes In the existing FAPA behavior, it was observed that if traffic hits a charging action that has a "flow limit-for-bandwidth id" configured, those flows would not engage the FAPA. The current release resolves this issue. Previous Behavior: When traffic hit a charging action with "flow limit-for-bandwidth id" configured, it did not engage into FAPA even when all other eligibility conditions of engagement were met. New Behavior: When traffic hits a charging action with "flow limit-for-bandwidth id" configured, it now engages into FAPA when all other eligibility conditions of engagement are met. Customer Impact: Performance improvement can be observed in throughput due to FAPA engagement. Inclusion of APN AMBR in the Create Session Response Feature Information Summary Data Status Introduced-In Release Modified-In Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release New Functionality P-GW ASR 5500 Enabled CSCvd

24 Feature Changes P-GW Changes in Release Related Documentation Command Line Interface Reference P-GW System Administration Guide Statistics and Counters Reference Revision History Revision history details are not provided for features introduced before release. Revision Details New in this release. Release Release Date April 27, 2017 Feature Changes Currently, APN AMBR is included in the Create Session Response even if it is not modified by the PCRF. This feature has been implemented to comply to the 3GPP specifications. With this feature, now APN AMBR will be included on the S5/S8, S4/S11, and S2a/S2b interfaces if the received APN-AMBR has been modified by the PCRF. Previous Behavior: APN AMBR was included in Create Session Response even if it was not modified by the PCRF. New Behavior: Now, APN AMBR will be included on the S5/S8, S4/S11, and S2a/S2b interfaces if the received APN-AMBR has been modified by the PCRF. A new CLI command has been added to enable/disable inclusion of the APN-AMBR value in the Create Session Response for the modified value received by the PCRF. P-GW supports APN-AMBR value upto kbps. Command Changes egtp Two new keywords have been added to the egtp command to enable/disable inclusion of APN-AMBR value in Create Session Response for modified value received by PCRF. configure context context_name pgw service service_name [ default no ] egtp create-session-rsp apn-ambr-always-include end 24

25 P-GW Changes in Release Performance Indicator Changes Notes: default: APN AMBR is not included in the CS Response if APN AMBR is not received from the PCRF. P-GW supports APN-AMBR value upto kbps. no: Does not include APN AMBR in the CS Response. This is the default behavior. create-session-rsp: Provides an option to include APN-AMBR in the Create Session Response apn-ambr-always-include: Always includes APN-AMBR IE in Create Session Response. Performance Indicator Changes show config This command has been modified to display the following output: plmn id mcc 404 mnc 00 plmn id mcc 404 mnc 005 primary plmn id mcc 404 mnc 090 fqdn host abc.net realm 3gpp.org dns-client context ISP1 associate ggsn-service GGSN associate egtp-service PGW21EGTP egtp create-session-rsp apn-ambr-always-include show pgw-service name This command has been modified to display the following output: EGTP SGW Restoration Handling: Disabled Session Hold Timer: n/a Timeout: n/a EGTP Modify bearer cmd negotiate qos: Disabled EGTP GnGp Modify bearer res with APN-AMBR: Disabled EGTP Modify bearer res with CHARGING-ID: Disabled EGTP Modify bearer res with CHARGING-FQDN or CHARGING-GW-ADDRESS: Disabled EGTP Modify bearer res with MSISDN: Disabled EGTP Modify Bearer Response with Context Not Found cause if IMEI/IMEISV mismatch: Disabled EGTP Bit Rate in Rounded Down Kbps: Disabled EGTP Suppress Update Bearer Request (no bitrate change): Disabled EGTP Create Session Response with APN-AMBR IE: Enabled Incorrect Cause Code in Create Session Response by P-GW Feature Information Summary Data Status Introduced-In Release Modified Functionality 25

26 Feature Changes P-GW Changes in Release Modified-In Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation P-GW, SAEGW ASR 5500 Enabled CSCvd00526 P-GW Administration Guide. SAEGW Administration Guide. Revision History Revision history details are not provided for features introduced before release. Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes Previous Behavior: "Create Session Request" with reserved QCI was rejected by the P-GW with the cause code "EGTP_CAUSE_SERVICE_NOT_SUPPORTED" in the "Create Session Response" message. New Behavior: Now, "Create Session Request" with reserved QCI is rejected by the P-GW with the cause code "EGTP_CAUSE_MANDATORY_IE_INCORRECT" in the "Create Session Response" message. Impact on Customer: Cause code change in Create Session Response message will be seen. Increase in ARP Support Feature Information Summary Data Status Modified Functionality 26

27 P-GW Changes in Release Feature Changes Introduced-In Release Modified-In Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation P-GW, SAEGW, S-GW ASR 5500 Disabled CSCvc89562 Command Line Interface Reference Revision History Revision history details are not provided for features introduced before release. Revision Details Modified in this release. Release Release Date April 27, 2017 Feature Changes Earlier, the maximum number of three ARPs that were supported on emps profile. This feature extends configuration support to increase maximum of eight ARPs. This support has been extended to other CLI commands as well. Following are the features that can be configured for maximum 8 ARPs: 1 allow-on-congestion CLI command 2 emps profile 3 Overload profile and self-protection CLI 4 GTPC RLF Throttling CLI After upgrade/downgrade, existing sessions will continue its emps characteristics until the next transaction on the session. It will fetch the new configuration during the first transaction after upgrade/downgrade. 27

28 Configuring the ARPs P-GW Changes in Release Configuring the ARPs The following section provides the different configuration commands that support configuration of ARPs. allow-on-congestion This CLI command has been modified to support configuration of max 8 ARP's for the "allow-on-congestion" congestion CLI. egtp-service: Notes: configure context <context_name> egtp-service <egtp-service_name> [no] gtpc allow-on-congestion arp <arp-value> end arp: Configures the gateway to allow calls for this ARP even under congestion. Enter ARP Priority Level, ranging from integer emps-profile This CLI command has been modified to extend the support from 3 emps ARPs to 8 emps ARPs. Notes: configure [no] emps-profile <emps-profile_name> earp {[1..15] {[1.15] {[1..15]}}} end earp: Configures earp values ranging from integer Configures maximum of 8 earp priority level values so that sessions with configured earp priority values can be marked as emps sessions. gtpc-overload-control-profile Currently, P-GW supports 3 ARPs under Overload Profile and self-protection CLI's. This CLI command has been modified to extend the support to 8 emps ARPs. Notes: configure gtpc-overload-control-profile<gtpc-overload-control-profile_name> [no] throttling-behavior {earp { }*} {exclude} [no] self-protection-behavior {earp { }*} {exclude} end earp: Configures maximum of 8 EARP priority level values so that incoming request messages for configured earp priority values are not rejected even if system is under self-protection mode. 28

29 P-GW Changes in Release NEMO-LMA Heartbeat throttling-behaviour already supports 8 ARP values. No change has been made to this command. RLF already supports 8 ARP values. No change has been made to this command. NEMO-LMA Heartbeat Feature Information Summary Data Status Introduced-In Release Modified-In Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation New Feature P-GW ASR 5500 Disabled CSCuw08182 NEMO PMIPv6 Heartbeat on LMA (SAEGW) Command Line Interface Reference P-GW Administration Guide SAEGW Administration Guide Revision History Revision history details are not provided for features introduced before release. Revision Details New in this release. Release Release Date April 27,

30 Feature Description P-GW Changes in Release Feature Description Path management mechanism through Heartbeat messages between the Mobile Router (MR) and Network Mobility-Local Mobility Anchor (NEMO-LMA) is important to know the availability of the peers, to detect failures, quickly inform peers if recovery from the node fails and allow a peer to take appropriate action. How It Works The MR and the LMA exchange Heartbeat messages at regular intervals to detect the status of availability between them. The NEMO-LMA initiates a Heartbeat exchange with the MR, by sending a Heartbeat Request message, to check if the MR is reachable. The NEMO-LMA records the sequence number of the last Heartbeat Request message and is used to match the corresponding Heartbeat Response. The NEMO-LMA responds to a Heartbeat Request message with a Heartbeat Response message, irrespective of whether there is PMIPv6 session with the corresponding peer. Binding Error When the Binding Error message, with status set to 2, is received in response to a Heartbeat Request message, the NEMO-LMA does not use Heartbeat messages further with the corresponding peer. Failure Detection When the LMA node does not receive the Heartbeat response for the configurable parameter max-heartbeat-retransmission <value> exceed-action drop-session, the NEMO-LMA concludes that the peer is not reachable. As such, the Heartbeat request to the peer is stopped and clears the NEMO-LMA session without any traps. Restart Detection If the restart counter value is different from the previous received value, then it assumes that the peer had crashed and recovered. And so, the existing NEMO-LMA sessions are cleared. License Requirements Use of NEMO requires that a valid license key be installed. Contact your Cisco account or Support representative for information on how to obtain a license. Configuring NEMO-LMA Heartbeat Use the following commands under LMA Service Configuration Mode to clear NEMO-LMA sessions without generating traps: configure context context_name lma-service service_name heartbeat retransmission max number [ exceed-action drop-session ] end Notes: 30

31 P-GW Changes in Release Monitoring and Troubleshooting the NEMO-LMA Heartbeat retransmission max: The maximum number of heartbeat retransmissions allowed. The number must be an integer from 0 to 15. Default: 3 exceed-action: Specifies the action to be taken after the maximum number of Heartbeat retransmissions is reached. drop-session: Used for dropping the session when path failure is detected. The exceed-action and drop-session keywords are valid only for NEMO-LMA sessions and takes effect if the Heartbeat feature is enabled. Monitoring and Troubleshooting the NEMO-LMA Heartbeat The following sections describe commands available to monitor and troubleshoot the feature. monitor protocol When using the monitor protocol command, enable option 48 to monitor the Heartbeat Request/Reply messages. show lma-service statistics Use this command to see the statistics related to Heartbeat messages. The output generated appears similar to the following: Total Disconnects: 1 Lifetime expiry: 0 Deregistrations: 0 Admin Drops: 0 Path Failure Drops: 1 Other Reasons: 0 show session disconnect-reasons Use this command to see the call disconnected due to heartbeat path failure. The output generated appears similar to the following: mme-guti_realloc_failed-detach(615) mme-pcscf-rest-detach(616) Reject-ho-old-tun-path-failure(617) mip-path-failure(618) Bulk Statistics LMA Schema The following new bulk statistics variable is added to the LMA schema in support of this feature: lma-pathfailsessionscleared If any path failures/restarted counter value changes for the NEMO-LMA Heartbeat feature, the sessions disconnection counter is incremented. 31

32 Piggyback Support on S2b Interface P-GW Changes in Release Piggyback Support on S2b Interface Feature Information Summary Data Status Introduced-In Release Modified-In Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation New Functionality epdg, P-GW ASR 5500 Enabled CSCvc97504, CSCvd09958 epdg S2b Piggybacking Support epdg Administration Guide P-GW Administration Guide Revision History Revision history details are not provided for features introduced before release. Revision Details New in this release. Release Release Date April 27, 2017 Feature Description This feature supports piggybacking of "Create Session Response" and "Create Bearer Request" messages on epdg and P-GW over the S2b interface. If piggybacking flag is set by the epdg in the Create Session Request, P-GW can now send Create Session Response and Create Bearer Request together to the epdg and eliminate the possibility of reordering of these messages. 32

33 P-GW Changes in Release Spare Protocol Types Supported in RAN-NAS IE for S2b Interface Spare Protocol Types Supported in RAN-NAS IE for S2b Interface Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Related Documentation Modified Functionality P-GW ASR 5500 Enabled CSCvd40558 P-GW Administration Guide Command Line Interface Reference Revision History Revision history details are not provided for features introduced before release. Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes Just after starting the call model, P-GW receives a large number of negative CBResponse and UBResponse messages. The RAN-NAS IE coming in the messages have spare protocol types (6 to 15) that are not supported. Protocol types (6 to 15) are sent by epdg to report internal failures. The current release resolves this issue. Previous Behavior: For S2b interface, spare protocol types in RAN/NAS IE were not supported. 33

34 Command Changes P-GW Changes in Release New Behavior: For RAN/NAS IE, the spare protocol types are now supported using a CLI and the length for cause value for these spare IE can also be configured. This support is available only for the S2b interface. Spare protocol types are supported only for Failed Create Bearer Response/Failed Update Bearer Response messages. The cause value length depicts the length of cause value to be decoded; it can be 1 octet or 2 octets. The default value is 2 octets. Mismatch between length of cause value IE and configured CLI value leads to IE being ignored. Customer Impact: CLI needs to be added for allowing spare RAN/NAS protocol types. Command Changes ran-nas decode proto-type-spare cause-value-length This is a new command added to the egtp Service Configuration mode. Run this command to enable spare protocol types for the S2b interface: config context <context_name> egtp-service <service_name> ran-nas decode proto-type-spare cause-value-length <1 2> Update Bearer Request Sends Exact Same CRI in CCA-U for Dynamic Rule Already Installed Feature Information Summary Data Status Introduced in Release Modified in Release(s) Applicable Product(s) Applicable Platform(s) Default Setting Related CDETS ID(s) Related Changes in This Release Modified Functionality P-GW ASR 5500 Enabled CSCvd

35 P-GW Changes in Release Feature Changes Related Documentation P-GW Administration Guide Revision History Revision history details are not provided for features introduced before release. Revision Details New behavior change in this release. Release Release Date April 27, 2017 Feature Changes After dynamic rule is installed, CCR-U is sent with SUCCESSFUL_RESOURCE_ALLOCATION. However on sending the same CRI as that of the dynamic rule in CCA-U, the Update Bearer Request (UBR) is sent by the P-GW for this rule even if the CRI is exactly the same. This causes the CCR-U and UBR to continously loop. The current release resolves this issue. Ideally, if invalid values of pre-emption-capability or pre-emption-vulnerability AVP is sent from the PCRF, IMSA validates them. If it is invalid, it converts them to default values, that is, pre-emption-capability: 1 (Default Value) and pre-emption-vulnerability: 0 (Default Value). Previous Behavior: While installing dynamic rules, if PCRF sends pre-emption-capability or pre-emption-vulnerability (or both) AVP values other than 0 (Enabled) or 1 (Disabled), the same values were propagated to the P-GW. New Behavior: While installing dynamic rules, if PCRF sends pre-emption-capability or pre-emption-vulnerability (or both) AVP values other than 0 (Enabled) or 1 (Disabled), on receiving these, the IMSA converts them to the default values (as per 3GPP TS V Section: /47) and propagates them to the P-GW. 35