Release Change Reference, StarOS Release 21.9/Ultra Services Platform Release 6.3

Transcription

1 Release Change Reference, StarOS Release 21.9/Ultra Services Platform Release 6.3 First Published: Last Modified: Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax:

2 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version. Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: go trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R) 2018 Cisco Systems, Inc. All rights reserved.

3 CHAPTER 1 Release 21.9/6.3 Features and Changes Quick Reference Release 21.9/6.3 Features and Changes, on page 1 Release 21.9/6.3 Features and Changes Features / Behavior Changes 5G NSA for MME, on page 17 5G NSA for SAEGW, on page 37 API-based VNFM Upgrade Process, on page 63 API-based AutoDeploy, AutoIT and AutoVNF Upgrade Process, on page 65 Collecting UAS Logs and VNF Diagnostic Information, on page 67 De-coupling of OS and ConfD Access, on page 69 Dual UEM Model for Redundancy, on page 195 enb Group Based Relative Capacity Transmission, on page 71 Gx Session Recovery, on page 75 Inline TCP Optimization, on page 81 IPSec Slow Path Data Plane, on page 95 Limit Max Number of IKEv1 IPSEC Managers within a Context, on page 99 Applicable Product(s) / Functional Area MME SAEGW UGP UGP UGP UGP UGP MME All products using Gx Interface P-GW IPSec IPSec Release Introduced / Modified

4 Release 21.9/6.3 Features and Changes Release 21.9/6.3 Features and Changes Quick Reference Features / Behavior Changes Mapping High Throughput Sessions on Session Managers, on page 101 Maximum Segment Size for Outgoing TCP Packets, on page 105 MME Manager Scaling for USP and VPC-DI, on page 107 Multi-VNF and Multi-tenant Support for UEM, on page 111 Network Service Headers (NSH), on page 113 NTP Client Support for UEM, on page 125 P-GW Custom Diameter Dictionary Changes for Gx Interface, on page 127 Presence Reporting Area, on page 129 Rate Limiting System Throughput Support, on page 139 SBc Message Size, on page 145 Service Function Scaling, on page 147 Short Message Service, on page 149 Support for Interim EDRs, on page 187 Triggering Iu Release Command Procedure, on page 191 UEM Patch Upgrade Process, on page 197 Unique IP Identification for Fragmented IPv6 Packets, on page 199 USP Software Version Updates, on page 201 X-Header Insertion and Encryption, on page 207 Applicable Product(s) / Functional Area P-GW, S-GW, SAEGW All products using LI MME UGP P-GW, SAEGW UGP P-GW P-GW, S-GW, SAEGW ASR 5500, VPC-DI, VPC-SI MME UGP MME P-GW, SAE-GW SGSN UGP GGSN P-GW UGP ECS Release Introduced / Modified

5 CHAPTER 2 Feature Defaults Quick Reference Feature Defaults Feature Defaults, on page 3 The following table indicates what features are enabled or disabled by default. Feature 5G NSA for MME 5G NSA for SAEGW API-based VNFM Upgrade Process API-based AutoDeploy, AutoIT and AutoVNF Upgrade Process Collecting UAS and VNF Diagnostic Logs De-coupling of OS and ConfD Access enb Group Based Relative Capacity Transmission Gx Session Recovery Inline TCP Optimization IPSec Slow Path Data Plane Limit Max Number of IKEv1 IPSEC Managers within a Context Mapping High Throughput Sessions on Session Managers Maximum Segment Size for Outgoing TCP Packets MME Manager Scaling for VPC-DI/USP Multi-VNF and Multi-tenant Support for UEM Network Service Headers (NSH) Default Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration required Disabled - Configuration required Disabled - Configuration required Enabled - Always-on Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Enabled - Always-on 3

6 Feature Defaults Feature Defaults Quick Reference Feature P-GW Custom Diameter Dictionary Changes for Gx Interface Presence Reporting Area NTP Client Support for UEM Rate Limiting System Throughput Support SBc Message Size Service Function Scaling Short Message Service Support for Interim EDRs Triggering Iu Release Command Procedure Dual UEM Model for Redundancy UEM Patch Upgrade Process Unique IP Identification for Fragmented IPv6 Packets USP Software Version Updates X-Header Insertion and Encryption Default Enabled - Always-on (for customer-specific Diameter dictionary for Gx interface) Disabled - Configuration Required Enabled - Always-on Disabled - License Required Disabled - Configuration Required Enabled - Always-on Disabled - Configuration Required Disabled - Configuration Required Disabled - Configuration Required Enabled - Configuration required Disabled - Configuration Required Enabled - Always-on Disabled - Configuration Required Disabled - Configuration Required 4

7 CHAPTER 3 Bulk Statistics Changes Quick Reference This chapter identifies bulk statistics changes added to, modified for, or deprecated from the StarOS 21.9 software release. Important For more information regarding bulk statistics identified in this section, see the latest version of the BulkstatStatistics_document.xls spreadsheet supplied with the release. Bulk statistics changes for 21.9 include: New Bulk Statistics, on page 5 Modified Bulk Statistics, on page 15 Deprecated Bulk Statistics, on page 15 New Bulk Statistics This section identifies new bulk statistics and new bulk statistic schemas introduced in release CUSP Schema The following bulk statistics are added in the CUSP schema in support of the Inline TCP Optimization (Phase 2) feature. Bulk Statistics Description tcpaccl-totflows Indicates the total number of TCP accelerated flows. tcpaccl-currflows Indicates the number of current TCP accelerated flows. tcpaccl-usr-ipv4totpkts-rx Indicates the total number of IPv4 TCP accelerated packets received from the UE. tcpaccl-usr-ipv4totbytes-rx Indicates the total number of IPv4 TCP accelerated bytes received from the UE. tcpaccl-usr-ipv4totpkts-tx Indicates the total number of IPv4 TCP accelerated packets sent towards the UE. 5

8 New Bulk Statistics Bulk Statistics Changes Quick Reference Bulk Statistics tcpaccl-usr-ipv4totbytes-tx tcpaccl-inet-ipv4totpkts-rx tcpaccl-inet-ipv4totbytes-rx tcpaccl-inet-ipv4totpkts-tx tcpaccl-inet-ipv4totbytes-tx tcpaccl-usr-ipv6totpkts-rx tcpaccl-usr-ipv6totbytes-rx tcpaccl-usr-ipv6totpkts-tx tcpaccl-usr-ipv6totbytes-tx tcpaccl-inet-ipv6totpkts-rx tcpaccl-inet-ipv6totbytes-rx tcpaccl-inet-ipv6totpkts-tx tcpaccl-inet-ipv6totbytes-tx Description Indicates the total number of IPv4 TCP accelerated bytes sent towards the UE. Indicates the total number of IPv4 TCP accelerated packets received from the internet. Indicates the total number of IPv4 TCP accelerated bytes received from the internet. Indicates the total number of IPv4 TCP accelerated packets sent towards the internet. Indicates the total number of IPv4 TCP accelerated bytes sent towards the internet. Indicates the total number of IPv6 TCP accelerated packets received from the UE. Indicates the total number of IPv6 TCP accelerated bytes received from the UE. Indicates the total number of IPv6 TCP accelerated packets sent towards the UE. Indicates the total number of IPv6 TCP accelerated bytes sent towards the UE. Indicates the total number of IPv6 TCP accelerated packets received from the internet. Indicates the total number of IPv6 TCP accelerated bytes received from the internet. Indicates the total number of IPv6 TCP accelerated packets sent towards the internet. Indicates the total number of IPv6 TCP accelerated bytes sent towards the internet. Diameter Schema The following bulk statistics are added in the Diameter schema in support of the Gx Session Recovery feature. Bulk Statistics read-ssr read-ssr-err write-ssa write-ssa-err Description Indicates the number of SSR read success at Diamproxy endpoint level. Indicates the number of SSR read failure at Diamproxy endpoint level. Indicates the number of SSR write success at Diamproxy endpoint level. Indicates the number of SSR write failure at Diamproxy endpoint level. 6

9 Bulk Statistics Changes Quick Reference New Bulk Statistics Bulk Statistics gx-sess-not-found Description Indicates the number of requests received to recover the session but the session is not found at Diamproxy endpoint level. MME Schema The following bulk statistics are added in the MME schema in support of the 5G Non Standalone (NSA) solution for MME. Bulk Statistics esmevent-dcnr-user-pdncon-attempt esmevent-dcnr-user-pdncon-success esmevent-dcnr-user-pdncon-failure pdn-dcnr-user-all pdn-dcnr-user-connected pdn-dcnr-user-idle Description The total number of EPS Session Management events - DCNR User PDN connections - attempted. The total number of EPS Session Management events - DCNR User PDN connections - successes. The total number of EPS Session Management events - DCNR User PDN connections - failures. The current total number of DCNR user PDN connections in any state. The current total number of DCNR user connected PDNs. The current total number of DCNR user idle PDNs. The following bulk statistics are added in the MME schema in support of the Short Message Service (SMS) feature. Bulk Statistics ps-sms-paging-init-events-attempted ps-sms-paging-init-events-success ps-sms-paging-init-events-failures ps-sms-paging-last-enb-success ps-sms-paging-last-tai-success ps-sms-paging-tai-list-success Description The total number of PS SMS Paging Initiation events that were attempted. The total number of PS SMS Paging Initiation events that were successful. The total number of PS SMS Paging Initiation events that failed. The total number of PS SMS Paging Initiation events that succeeded at the last known enodeb. The total number of PS SMS Paging Initiation events that succeeded at an enodeb in the TAI from which the UE was last heard. The total number of PS SMS Paging Initiation events that succeeded at an enodeb in all TAIs present in the TAI list assigned to the UE. MME-SMS Schema 7

10 New Bulk Statistics Bulk Statistics Changes Quick Reference The following bulk statistics are added in the MME-SMS schema in support of the Short Message Service (SMS) feature. The MME-SMS schema is new in release Bulk Statistics mo-sms-in-progress mt-sms-in-progress mt-sms-in-queue sms-memory-available-in-progress mo-sms-attempted mo-sms-successful mt-sms-attempted mt-sms-successful sms-memory-available-attempted sms-memory-available-successful conn-prot-data-tx conn-prot-data-rx conn-prot-ack-tx conn-prot-ack-rx conn-prot-error-tx conn-prot-error-rx Description The total number of mobile originated (MO) SMS messages that are waiting in the MME to be delivered. The total number of mobile terminated (MT) SMS messages that are waiting in the MME to be delivered. The total number of mobile terminated SMS messages in the queue. The total number of procedures for retrieval of available SMS memory in progress. The total number of mobile originated SMS messages that are attempted to be delivered by the network. The total number of mobile originated SMS messages that are successfully delivered by the network. The total number of mobile terminated SMS messages that are attempted to be delivered by the network. The total number of mobile terminated SMS messages that are successfully delivered by the network. The total number of procedures for retrieval of available SMS memory attempted. The total number of procedures for retrieval of available SMS memory successful. The total number of protocol data units sent during connection setup. The total number of protocol data units received during connection setup. The total number of Ack messages sent during connection setup. The total number of Ack messages received during connection setup. The total number of protocol errors during connection setup in Tx message. The total number of protocol errors during connection setup in Rx message. 8

11 Bulk Statistics Changes Quick Reference New Bulk Statistics Bulk Statistics conn-prot-error-nwt-fail-tx conn-prot-error-nwt-fail-rx conn-prot-error-congestion-tx conn-prot-error-congestion-rx conn-prot-error-invalid-tid-tx conn-prot-error-invalid-tid-rx conn-prot-error-invalid-semantic-tx conn-prot-error-invalid-semantic-rx conn-prot-error-invalid-mand-info-tx conn-prot-error-invalid-mand-info-rx conn-prot-error-invalid-msg-type-tx conn-prot-error-invalid-msg-type-rx conn-prot-error-invalid-prot-state-tx conn-prot-error-invalid-prot-state-rx conn-prot-error-invalid-ie-tx conn-prot-error-invalid-ie-rx Description The total number of protocol errors during connection setup due to network failure in Tx message. The total number of protocol errors during connection setup due to network failure in Rx message. The total number of protocol errors during connection setup due to congestion in Tx message. The total number of protocol errors during connection setup due to congestion in Rx message. The total number of protocol errors during connection setup due to invalid transaction ID (TID) in Tx message. The total number of protocol errors during connection setup due to invalid transaction ID (TID) in Rx message. The total number of protocol errors during connection setup due to invalid semantics in Tx message. The total number of protocol errors during connection setup due to invalid semantics in Rx message. The total number of protocol errors during connection setup as mandatory information in Tx message is invalid. The total number of protocol errors during connection setup as mandatory information in Rx message is invalid. The total number of protocol errors during connection setup due to invalid Tx message type. The total number of protocol errors during connection setup due to invalid Rx message type. The total number of protocol errors during connection setup as protocol state in Tx message is invalid. The total number of protocol errors during connection setup as protocol state in Rx message is invalid. The total number of protocol errors during connection setup as information element in Tx message is invalid. The total number of protocol errors during connection setup as information element in Rx message is invalid 9

12 New Bulk Statistics Bulk Statistics Changes Quick Reference Bulk Statistics conn-prot-error-protocol-error-tx conn-prot-error-protocol-error-rx conn-prot-error-undefined-cause-tx conn-prot-error-undefined-cause-rx conn-prot-data-dropped conn-prot-ack-dropped conn-prot-error-dropped conn-prot-inval-tid-rcvd relay-prot-data-tx relay-prot-data-rx relay-prot-ack-tx relay-prot-ack-rx relay-prot-err-tx relay-prot-err-rx relay-prot-err-unassigned-num relay-prot-err-opr-determ-barring relay-prot-err-call-barred Description The total number of protocol errors during connection setup as protocol error in Tx message. The total number of protocol errors during connection setup as protocol error in Rx message. The total number of protocol errors during connection setup due to unspecified error in Tx message. The total number of protocol errors during connection setup due to unspecified error in Rx message. The total number of data packets dropped during connection setup. The total number of Ack messages dropped during connection setup. The total number of data packets dropped during connection setup due to error in connection. The total number of messages dropped during connection setup due to invalid transaction ID (TID) received. The total number of protocol data units sent during message relay. The total number of protocol data units received during message relay. The total number of Ack messages sent during message relay. The total number of Ack messages received during message relay. The total number of protocol errors during message relay in Tx message. The total number of protocol errors during message relay in Rx message. The total number of protocol errors during message relay due to unassigned protocol number. The total number of protocol errors during message relay due to operator determined barring. The total number of protocol errors during message relay due to call barring. 10

13 Bulk Statistics Changes Quick Reference New Bulk Statistics Bulk Statistics relay-prot-err-reserved relay-prot-err-sm-transfer-rej relay-prot-err-dest-out-of-order relay-prot-err-unidentified-subs relay-prot-err-facility-rej relay-prot-err-unknown-subs relay-prot-err-netwk-out-of-order relay-prot-err-temp-fail relay-prot-err-congestion relay-prot-err-not-subscribed relay-prot-err-not-implemented relay-prot-err-interworking-err relay-prot-err-res-unavail relay-prot-err-mem-capacity-exceed relay-prot-err-inval-ref-num-tx relay-prot-err-inval-ref-num-rx relay-prot-err-inval-semantic-tx Description The total number of protocol errors during message relay due to reserved resources. The total number of protocol errors during message relay due to session manager transfer rejection. The total number of protocol errors during message relay due to out of order on destination. The total number of protocol errors during message relay due to unidentified subscriber. The total number of protocol errors during message relay due to facility rejection. The total number of protocol errors during message relay due to unknown subscriber. The total number of protocol errors during message relay due to out-of-order network. The total number of protocol errors during message relay due to temporary failure in network. The total number of protocol errors during message relay due to congestion in network. The total number of protocol errors during message relay as this service is not subscribed by subscriber. The total number of protocol errors during message relay as this service is not yet implemented. The total number of protocol errors during message relay due to interworking error between two networks or technology. The total number of protocol errors during message relay as resources are not available. The total number of protocol errors during message relay as capacity is exceeded. The total number of protocol errors during message relay as invalid reference in Tx message. The total number of protocol errors during message relay as invalid reference in Rx message. The total number of protocol errors during message relay due to invalid semantics in Tx message. 11

14 New Bulk Statistics Bulk Statistics Changes Quick Reference Bulk Statistics relay-prot-err-inval-semantic-rx relay-prot-err-inval-mand-info-tx relay-prot-err-inval-mand-info-rx relay-prot-err-inval-msg-type-tx relay-prot-err-inval-msg-type-rx relay-prot-err-inval-prot-state-tx relay-prot-err-inval-prot-state-rx relay-prot-err-inval-ie-tx relay-prot-err-inval-ie-rx relay-prot-err-protocol-error-rx relay-prot-err-protocol-error-tx relay-prot-err-unidentified-error-tx relay-prot-err-unidentified-error-rx relay-prot-smma-rx relay-prot-data-dropped relay-prot-ack-dropped relay-prot-error-dropped Description The total number of protocol errors during message relay due to invalid semantics in Rx message. The total number of protocol errors during message relay as mandatory information in Tx message is invalid. The total number of protocol errors during message relay as mandatory information in Rx message is invalid. The total number of protocol errors during message relay due to invalid Tx message type. The total number of protocol errors during message relay due to invalid Rx message type. The total number of protocol errors during message relay as protocol state in Tx message is invalid. The total number of protocol errors during message relay as protocol state in Rx message is invalid. The total number of protocol errors during message relay as information element in Tx message is invalid. The total number of protocol errors during message relay as the information element in Rx message is invalid. The total number of RP ERROR messages sent with the cause Protocol Error in the message header. The total number of protocol errors during message relay when there are protocol errors in the transmitted message. The total number of protocol errors during message relay due to unspecified error in Tx message. The total number of protocol errors during message relay due to unspecified error in Rx message. The total number RP SMMA messages received. The total number of data packets dropped during message relay. The total number of Ack messages dropped during message relay. The total number of data packets dropped during message relay due to error in connection. 12

15 Bulk Statistics Changes Quick Reference New Bulk Statistics Bulk Statistics relay-prot-decode-failure concat-mo-sms conn-prot-timer-expiry tr1n-timer-expiry tr2n-timer-expiry conn-prot-data-retrans relay-prot-msg-encode-fail conn-prot-data-tx-fail conn-prot-data-inval-tid conn-prot-max-retrans-reached mt-fail-no-db-rec mt-fail-conn-prot-data-no-ack-rcvd mt-fail-fwd-busy-subs mt-fail-fwd-detached-subs mt-fail-mt-queue-full Description The total number of messages dropped during message relay due to invalid transaction ID (TID) received. The total number of concatenated mobile originated SMS messages. The total number of events when timer expired during connection setup. The total number of events when TR1N timer expired during mobile terminated SMS is in wait state for RP-ACK. The total number of events when TR2N timer expired during mobile terminated SMS is in wait state to send RP-ACK. The total number of protocol data units retransmitted during connection setup. The total number of message encoding failures during message relay. The total number of protocol data units with Tx messages failed during connection setup. The total number of protocol data units with invalid transaction ID (ID) during connection setup. The total number of events when retransmission limit is exhausted during connection setup. The total number of mobile terminated messages failed as database record is not available. The total number of mobile terminated messages failed as no acknowledgement is received during connection setup. The total number of mobile terminated messages failed due to busy subscriber. The total number of mobile terminated messages failed due to detached subscriber. The total number of mobile terminated messages failed as messaged queue was full. P-GW Schema The following bulk statistics are added in the P-GW schema in support for DCNR PDNs on SGW and SAEGW. 13

16 New Bulk Statistics Bulk Statistics Changes Quick Reference Bulk Statistics sessstat-pdn-dcnr-current-active sessstat-pdn-dcnr-cumulative-activated sessstat-pdn-dcnr-cumulative-deactivated pgw-anchor-pdns-dcnr-current-active pgw-anchor-pdns-dcnr-cumulative-activated pgw-anchor-pdns-dcnr-cumulative-deactivated Description The total number of current active S-GW DCNR PDNs. The total number of S-GW PDNs that are setup as a DCNR PDN. The total number of S-GW DCNR PDNs released. The total number of current active P-GW anchored DCNR PDNs. The total number of P-GW anchored PDNs that are setup as a DCNR PDN. The total number of P-GW anchored DCNR PDNs that are released. S-GW Schema The following bulk statistics are added in the S-GW schema in support for DCNR PDNs on S-GW and SAEGW. Bulk Statistics sessstat-pdn-dcnr-current-active sessstat-pdn-dcnr-cumulative-activated sessstat-pdn-dcnr-cumulative-deactivated Description The total number of current active S-GW DCNR PDNs. The total number of S-GW PDNs that are setup as a DCNR PDN. The total number of S-GW DCNR PDNs released. SAEGW Schema The following bulk statistics are added in the SAEGW schema in support for DCNR PDNs on S-GW and SAEGW. Bulk Statistics saegw-collocated-pdns-dcnr-current-active sessstat-pdn-dcnr-cumulative-activated saegw-collocated-pdns-dcnr-cumulative-deactivated sgw-anchor-pdns-dcnr-current-active sgw-anchor-pdns-dcnr-cumulative-activated Description The total number of current active SAEGW collapsed DCNR PDNs. The total number of collapsed SAEGW PDNs that are setup as a DCNR PDN. The total number of collapsed SAEGW DCNR PDNs were released. The total number of current active S-GW anchored DCNR PDNs. The total number of S-GW anchored PDNs that are setup as a DCNR PDN. 14

17 Bulk Statistics Changes Quick Reference Modified Bulk Statistics Bulk Statistics sgw-anchor-pdns-dcnr-cumulative-deactivated Description The total number of S-GW anchored DCNR PDNs that are released. TAI Schema The following bulk statistics are added in the TAI schema in support of the 5G Non Standalone (NSA) solution for MME. Bulk Statistics tai-esmevent-dcnr-user-pdncon-attempt tai-esmevent-dcnr-user-pdncon-success tai-esmevent-dcnr-user-pdncon-failure Description The total number of DCNR User PDN connection EPS Session Management events attempted per TAI. The total number of successful DCNR User PDN connection EPS Session Management events per TAI. The total number of failed DCNR User PDN connection EPS Session Management events per TAI. Modified Bulk Statistics This section identifies bulk statistics that have been modified in release None in this release. Deprecated Bulk Statistics This section identifies bulk statistics that are no longer supported in release None in this release. 15

18 Deprecated Bulk Statistics Bulk Statistics Changes Quick Reference 16

19 CHAPTER 4 5G NSA for MME Feature Summary and Revision History, on page 17 Feature Description, on page 18 How It Works, on page 21 Configuring 5G NSA for MME, on page 26 Monitoring and Troubleshooting, on page 30 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) MME ASR 5000 ASR 5500 VPC-DI VPC-SI Feature Default Disabled - Configuration Required Related Changes in This Release Not applicable Related Documentation 5G Non Standalone Solution Guide AAA Interface Administration and Reference Command Line Interface Reference MME Administration Guide Statistics and Counters Reference Revision History Revision Details Release 17

20 Feature Description 5G NSA for MME The 5G NSA solution for MME supports the following functionality in this release: DCNR capability exchange with peer SGSN in MM context over S3 interface 21.9 MME support of statistics for DCNR PDNs NR security algorithms for DCNR capable UEs to support 5G security Important Support for 5G security is not fully qualified in this release. The 5G NSA solution is qualified on the ASR 5000 platform. First introduced Feature Description Cisco 5G Non Standalone (NSA) solution leverages the existing LTE radio access and core network (EPC) as an anchor for mobility management and coverage. This solution enables operators using the Cisco EPC Packet Core to launch 5G services in shorter time and leverage existing infrastructure. Thus, NSA provides a seamless option to deploy 5G services with very less disruption in the network. Overview 5G is the next generation of 3GPP technology, after 4G/LTE, defined for wireless mobile data communication. The 5G standards are introduced in 3GPP Release 15 to cater to the needs of 5G networks. The two solutions defined by 3GPP for 5G networks are: 5G Non Standalone (NSA): The existing LTE radio access and core network (EPC) is leveraged to anchor the 5G NR using the Dual Connectivity feature. This solution enables operators to provide 5G services with shorter time and lesser cost. Note The 5G NSA solution is supported in this release. 5G Standalone (SA): An all new 5G Packet Core will be introduced with several new capabilities built inherently into it. The SA architecture comprises of 5G New Radio (5G NR) and 5G Core Network (5GC). Network Slicing, CUPS, Virtualization, Multi-Gbps support, Ultra low latency, and other such aspects will be natively built into the 5G SA Packet Core architecture. Dual Connectivity The E-UTRA-NR Dual Connectivity (EN-DC) feature supports 5G New Radio (NR) with EPC. A UE connected to an enodeb acts as a Master Node (MN) and an en-gnb acts as a Secondary Node (SN). The enodeb is 18

21 5G NSA for MME Feature Description connected to the EPC through the S1 interface and to the en-gnb through the X2 interface. The en-gnb can be connected to the EPC through the S1-U interface and other en-gnbs through the X2-U interface. The following figure illustrates the E-UTRA-NR Dual Connectivity architecture. Figure 1: EN-DC Architecture If the UE supports dual connectivity with NR, then the UE must set the DCNR bit to "dual connectivity with NR supported" in the UE network capability IE of the Attach Request/Tracking Area Update Request message. If the UE indicates support for dual connectivity with NR in the Attach Request/Tracking Area Update Request message, and the MME decides to restrict the use of dual connectivity with NR for the UE, then the MME sets the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept/Tracking Area Update Accept message. If the RestrictDCNR bit is set to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept/Tracking Area Update Accept message, the UE provides the indication that dual connectivity with NR is restricted to the upper layers. If the UE supports DCNR and DCNR is configured on MME, and if HSS sends ULA/IDR with "Access-Restriction" carrying "NR as Secondary RAT Not Allowed", MME sends the "NR Restriction" bit set in "Handover Restriction List" IE during Attach/TAU/Handover procedures. Similarly, MME sets the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept/Tracking Area Update Accept message. Accordingly, UE provides the indication that dual connectivity with NR is restricted to the upper layers. The "Handover Restriction List" IE is present in the "Initial Context Setup Request" message for Attach and TAU procedure with data forwarding procedure, in the "Handover Required" message for S1 handover procedure, in the "Downlink NAS Transport" message for TAU without active flag procedure. The 5G NSA solution for MME supports the following functionalities: E-RAB Modification Procedure: When SCG (Secondary Cell Group) bearer option is applied to support DCNR, this procedure allows the Master enodeb to switch a bearer to Secondary enodeb without changing the S1-MME association. NR Capable S-GW/P-GW Selection: 19

22 Feature Description 5G NSA for MME When DCNR capable UE attempts to register in MME and when all DCNR validations are successful (for example DCNR feature configuration on MME, HSS not sending access-restriction for NR, and so on), for dynamic S-GW and P-GW selection, MME uses the following service parameters received from DNS server (in NAPTR response) over other service parameters to select NR capable S-GW/P-GW. x-3gpp-sgw:x-s5-gtp+nc-nr x-3gpp-pgw:x-s5-gtp+nc-nr When the dynamic selection of S-GW/P-GW fails for any other reasons, MME falls back and selects the locally configured S-GW/P-GW. Dynamic S-GW/P-GW Selection: Dynamic S-GW and P-GW selection by MME for DCNR capable UE is supported. When a DCNR capable UE attempts to register in MME and when all DCNR validations are successful (DCNR feature configuration on MME, HSS not sending access-restriction for NR, and so on), the MME sets the "UP Function Selection Indication Flags" IE with DCNR flag set to 1 in "Create Session Request" message. This feature supports the CUPS architecture for SGW-C and PGW-C to select SGW-U and PGW-U and support dual connectivity with NR. When S-GW receives this IE over S11, it sends the IE over S5 to P-GW. If S-GW receives the IE in a non-cups deployment, it is ignored. URLCC QCI Support: For Ultra-Reliable and Low Latency Communications (URLCC), MME supports QCI 80 (Non-GBR resource type), QCI 82 (GBR resource type), and QCI 83 (GBR resource type). MME establishes the default bearers with URLLC QCI 80, which is typically used by low latency embb applications. MME establishes the dedicated bearers with URLLC QCI 82 and QCI 83 (also with QCI 80 if dedicated bearers of non-gbr type to be established), which is typically used by discrete automation services (industrial automation). PDNs with UP Function Selection Indication: Based on the DCNR flag in the UP Function Selection Indication Flags IE, new statistics and bulk statistics are supported for the total number of current active, setup, and released DCNR PDNs on MME. NR Support in GTP MM Context over S3 Interface: MME supports the DCNR capability exchange with peer SGSN over the S3 interface. The DCNR restriction can be notified by the peer SGSN during handover to MME. The DCNR restriction information helps the target MME in performing the right S-GW selection. During handovers, the target MME performs gateway selection before getting the subscription information from the HSS and hence MME may select the NR capable S-GW for DCNR restricted UE. To prevent this, the peer SGSN will notify the Restriction information (NRSRNA) through the GTP MM context in Identification-Response/Context-Response/Forward-Relocation-Request message to MME. The S3-DCNR support includes both GTPv2 and GTPv1 protocol for S4-SGSN and Gn-SGSN respectively. 5G Security: The "UE Additional Security Capability" and "Replayed UE Additional Security Capability" IEs for MME are supported as per 3GPP TS The MME supports handling of the "UE Additional Security Capability" IE for DCNR capable UEs. This information element is used by the UE in Attach Request and Tracking Area Update messages to indicate which additional security algorithms are supported by the UE. 20

23 5G NSA for MME How It Works The MME includes the "Replayed UE Additional Security Capability" IE if the MME supports handling of UE additional security capabilities, if the MME is initiating a Security Mode Command during an Attach or Tracking Area Update procedure and the Attach Request or Tracking Area Update Request message included a "UE Additional Security Capability" IE. The "NR UE Security Capability" IE will be included by MME in the S1AP messages INITIAL CONTEXT SETUP REQUEST, UE CONTEXT MODIFICATION REQUEST, HANDOVER REQUEST, PATH SWITCH ACKNOWLEDGE and DOWNLINK NAS TRANSPORT for MME as per 3GPP TS The enode-b includes the "NR UE Security Capability" IE in PATH SWITCH REQUEST to be processed by the MME. High Throughput: 5G NR offers downlink data throughput up to 20 Gbps and uplink data throughput up to 10 Gbps. Some interfaces in EPC have the support to handle (encode/decode) 5G throughput ranges. For example, NAS supports up to 65.2 Gbps (APN-AMBR) and S5/S8/S10/S3 (GTP-v2 interfaces) support up to 4.2 Tbps. The diameter interfaces such as S6a and Gx support only up to 4.2Gbps throughput, S1-AP supports only up to 10 Gbps and NAS supports up to 10 Gbps (MBR, GBR). New AVP/IE are introduced in S6a, Gx, S1-AP and NAS interfaces to support 5G throughput rates. See the How It Works section for more information. Extended QoS: MME supports the extended QoS values towards S-GW in legacy IEs - APN-AMBR, Bearer QoS, and Flow QoS. Supported IEs: S1-AP interface: Extended UE-AMBR Downlink Extended UE-AMBR Uplink Extended E-RAB Maximum Bit Rate Downlink Extended E-RAB Maximum Bit Rate Uplink Extended E-RAB Guaranteed Maximum Bit Rate Downlink Extended E-RAB Guaranteed Maximum Bit Rate Uplink NAS interface: Extended EPS quality of service Extended APN aggregate maximum bit rate How It Works Architecture This section describes the external interfaces required to support the 5G NSA architecture. 21

24 Limitations 5G NSA for MME S6a (HSS) Interface The S6a interface supports new AVPs "Extended-Max-Requested-BW-UL" and "Extended-Max-Requested-BW-DL" in grouped AVP "AMBR" to handle the 5G throughput ranges. When the maximum bandwidth value for UL (or DL) traffic is higher than bits per second, the "Max-Requested-Bandwidth-UL" AVP (or DL) must be set to the upper limit and the "Extended-Max-Requested-BW-UL" AVP (or DL) must be set to the requested bandwidth value in kilobits per second. S1AP (enodeb) Interface Extended UE-AMBR The S1AP interface supports new IEs "Extended UE Aggregate Maximum Bit Rate Downlink" and "Extended UE Aggregate Maximum Bit Rate Uplink" in the grouped IE "UE Aggregate Maximum Bit Rate", where the units are bits/second. If the Extended UE Aggregate Maximum Bit Rate Downlink/Uplink IE is included, then the UE Aggregate Maximum Bit Rate Downlink/Uplink IE must be ignored. Extended E-RAB MBR/GBR The S1AP interface supports new AVPs "Extended E-RAB Maximum Bit Rate Downlink/Uplink" and "Extended E-RAB Guaranteed Bit Rate Downlink/Uplink" in the "GBR QoS Information" grouped IE, where the units are bits/second. NAS (UE) Interface Extended APN Aggregate Maximum Bit Rate The new IE "Extended APN aggregate maximum bit rate" is added in all applicable NAS messages to convey the 5G throughput (beyond 65.2Gbps) over NAS. The existing IE in NAS "APN-AMBR" supports APN-AMBR values up to 65.2Gbps. Extended EPS Quality of Service The new IE "Extended EPS Quality of Service" is added in all applicable NAS messages to convey the 5G throughput (beyond 10Gbps) over NAS. The existing IE in NAS "EPS Quality of Service" supports MBR and GBR values up to 10Gbps. Limitations This section describes the known limitations for the 5G NSA feature: DCNR for S3 interface is supported only for inbound handover of UE from 2G/3G to 4G. MME does not support the NR capable gateway selection during connected mode inbound handover from Gn-SGSN. Flows This section describes the call flow procedures related to MME for 5G NSA. Initial Registration Procedure The following call flow illustrates the Initial Registration procedure for DCNR capable UE. 22

25 5G NSA for MME Initial Registration Procedure Figure 2: Initial Registration of DCNR Capable UE Step Description The DCNR capable UE sets the "DCNR bit" in NAS message "Attach Request" in "UE Network Capability" IE. DCNR must be enabled at MME service or call control profile depending upon the operator requirement. MME successfully authenticates the UE. As part of the authorization process, while sending ULR to HSS, MME advertises the DCNR support by sending the "NR as Secondary RAT" feature bit in "Feature-List-ID-2". HSS sends ULA by advertising the DCNR by sending "NR as Secondary RAT" feature bit in "Feature-List-ID-2", "Max-Requested-Bandwidth-UL" as bps, "Max-Requested-Bandwidth-DL" as bps, and the extended bandwidth values in AVPs "Extended-Max-Requested-BW-UL" and "Extended-Max-Requested-BW-DL". If HSS determines that the UE is not authorized for DCNR services, then HSS sends Subscription-Data with "Access-Restriction" carrying "NR as Secondary RAT Not Allowed". MME sends the Create Session Request message with the extended APN-AMBR values in existing AMBR IE. As the APN-AMBR values in GTPv2 interface are encoded in kbps, the existing AMBR IE handles the 5G NSA bit rates. 23

26 Initial Registration Procedure 5G NSA for MME Step Description P-GW sends CCR-I to PCRF advertising the DCNR by sending "Extended-BW-NR" feature bit in "Feature-List-ID-2", "APN-Aggregate-Max-Bitrate-UL" as bps, "APN-Aggregate-Max-Bitrate-DL" as bps, and the extended bandwidth values in AVPs "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL". PCRF sends CCA-I advertising the DCNR by sending "Extended-BW-NR" feature bit in "Feature-List-ID-2", "APN-Aggregate-Max-Bitrate-UL" as bps, "APN-Aggregate-Max-Bitrate-DL" as bps, and the extended bandwidth values in AVPs "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL". PCRF can offer the same extended APN-AMBR values that are requested by PCRF or modify the extended APN-AMBR values. P-GW enforces the APN-AMBR values accordingly. P-GW honors the APN-AMBR values as offered by PCRF and sends the extended APN-AMBR values in existing APN-AMBR IE in the Create Session Response message. MME computes the UE-AMBR values and sends the extended UE-AMBR values in new IEs "Extended UE Aggregate Maximum Bit Rate Downlink" and "Extended UE Aggregate Maximum Bit Rate Uplink" by setting the legacy "UE AMBR Uplink" and "UE AMBR Downlink" values to the maximum allowed value bps (10 Gbps) in the "Initial Context Setup Request" message. MME sends the APN-AMBR values up to 65.2 Gbps in existing APN-AMBR IE in NAS Activate Default EPS Bearer Context Request Attach Accept. If the APN-AMBR values are beyond 65.2 Gbps, MME sends the extended APN-AMBR values in "Extended APN Aggregate Maximum Bit Rate" IE. If ULA is received with "Access-Restriction" carrying "NR as Secondary RAT Not Allowed", MME sends the Initial Context Setup Request message with "NR Restriction" bit set in Handover Restriction List IE. MME sets the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept message. UE provides the indication that dual connectivity with NR is restricted to the upper layers accordingly. If the DCNR feature is not configured at MME service or call control profile, then MME sets the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept message. UE provides the indication that dual connectivity with NR is restricted to the upper layers accordingly. enodeb sends the Initial Context Setup Response message. If master enodeb determines to establish the bearer on secondary enodeb, F-TEID of the secondary enodeb may be sent (transport layer address and TEID of secondary enodeb). It is transparent to MME if the bearer is established on master enodeb or secondary enodeb. enodeb sends Uplink NAS Transport with NAS message "Complete - Activate Default EPS Bearer Context Accept". 24

27 5G NSA for MME E-RAB Modification Procedure Step Description MME sends the Modify Bearer Request message to S-GW with S1-U F-TEID details as received in the Initial Context Setup Response message. MME receives the Modify Bearer Response message from S-GW. E-RAB Modification Procedure When Secondary Cell Group (SCG) bearer option is applied to support DCNR, the E-RAB Modification procedure is used to transfer bearer contexts to and from secondary enodeb or secondary gnodeb. Figure 3: E-RAB Modification Procedure by Master enodeb 25

28 Standards Compliance 5G NSA for MME Step Description The master enodeb (MeNB) sends an E-RAB Modification Indication message (enodeb address(es) and TEIDs for downlink user plane for all the EPS bearers) to the MME. The MeNB indicates if each bearer is modified or not. The "E-RAB to be Modified List" IE contains both "E-RAB to Be Modified Item" and "E-RAB not to Be Modified Item" IEs. For the bearer that need to be switched to secondary enodeb/gnodeb (SeNB), the "E-RAB to Be Modified Item" IE contains the transport layer address of gnodeb and TEID of gnodeb. The MME sends a Modify Bearer Request message (enodeb address(es) and TEIDs for downlink user plane for all the EPS bearers) per PDN connection to the S-GW, only for the affected PDN connections. The S-GW returns a Modify Bearer Response message (S-GW address and TEID for uplink traffic) to the MME as a response to the Modify Bearer Request message. For the bearers transferred to SeNB, S-GW sends one or more end marker packets on the old path (to MeNB) immediately after switching the path. The MME confirms E-RAB modification with the E-RAB Modification Confirm message. The MME indicates if each bearer was successfully modified, retained, unmodified or already released by the EPC. Standards Compliance Cisco's implementation of the 5G NSA feature complies with the following standards: 3GPP Release Numbering, addressing and identification. 3GPP Release General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access 3GPP Release Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol 3GPP Release GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 3GPP Release Domain Name System Procedures Configuring 5G NSA for MME This section describes how to configure 5G NSA to support MME. Configuring 5G NSA on MME involves: Enabling DCNR in MME Service, on page 27 Enabling DCNR in Call Control Profile, on page 27 Configuring APN AMBR Values, on page 27 26

29 5G NSA for MME Enabling DCNR in MME Service Configuring Dedicated Bearer MBR Values, on page 28 Configuring UE AMBR Values, on page 29 Enabling DCNR in MME Service Use the following configuration to enable Dual Connectivity with New Radio (DCNR) to support 5G NSA. configure context context_name mme-service service_name [ no ] dcnr end NOTES: mme-service service_name: Creates an MME service or configures an existing MME service in the current context. service_name specifies the name of the MME service as an alphanumeric string of 1 to 63 characters. no: Disables the DCNR configuration. The dcnr CLI command is disabled by default. Enabling DCNR in Call Control Profile Use the following configuration to enable Dual Connectivity with New Radio (DCNR) to support 5G Non Standalone (NSA). configure call-control-profile profile_name [ no remove ] dcnr end NOTES: call-control-profile profile_name: Creates an instance of a call control profile. profile_name specifies the name of the call control profile as an alphanumeric string of 1 to 64 characters. no: Disables the DCNR configuration in the call control profile. remove: Removes the DCNR configuration from the call control profile. The dcnr CLI command is disabled by default. Configuring APN AMBR Values Use the following configuration to configure the APN aggregate maximum bit rate (AMBR) that will be stored in the Home Subscriber Server (HSS). configure apn-profile apn_profile_name qos apn-ambr max-ul mbr_up max-dl mbr_down 27

30 Configuring Dedicated Bearer MBR Values 5G NSA for MME NOTES: remove qos apn-ambr end apn-profile apn_profile_name: Creates an instance of an Access Point Name (APN) profile. apn_profile specifies the name of the APN profile as an alphanumeric string of 1 to 64 characters. qos: Configures the quality of service (QoS) parameters to be applied. apn-ambr: Configures the aggregate maximum bit rate (AMBR) for the APN. max-ul mbr_up: Defines the maximum bit rates for uplink traffic. mbr_up must be an integer from 1 to (4 Tbps). max-dl mbr_down: Defines the maximum bit rates for downlink traffic. mbr_up must be an integer from 1 to (4 Tbps). remove: Removes the APN AMBR changes from the configuration for this APN profile. Configuring Dedicated Bearer MBR Values Use the following configuration to configure the quality of service maximum bit rate (MBR) values for the dedicated bearer. configure apn-profile apn_profile_name qos dedicated-bearer mbr max-ul mbr_up max-dl mbr_down remove qos dedicated-bearer end NOTES: apn-profile apn_profile: Creates an instance of an Access Point Name (APN) profile. apn_profile_name specifies the name of the APN profile as an alphanumeric string of 1 to 64 characters. qos: Configures the quality of service (QoS) parameters to be applied. dedicated-bearer mbr: Configures the maximum bit rate (MBR) for the dedicated bearer. max-ul mbr_up: Defines the maximum bit rate for uplink traffic. mbr_up must be an integer from 1 to (4 Tbps). max-dl mbr_down: Defines the maximum bit rate for downlink traffic. mbr_down must be an integer from 1 to (4 Tbps). remove: Deletes the dedicated bearer MBR changes from the configuration for this APN profile. Configuring Dedicated Bearer MBR Values Use the following configuration to configure the quality of service maximum bit rate (MBR) values for the dedicated bearer. configure bearer-control-profile profile_name dedicated-bearer { mbr mbr-up mbr_up mbr-down mbr_down gbr gbr-up 28

31 5G NSA for MME Configuring UE AMBR Values gbr_up gbr-down gbr_down remove dedicated-bearer { gbr mbr } end NOTES: bearer-control-profile profile_name: Creates an instance of a bearer control profile. profile_name specifies the name of the bearer control profile as an alphanumeric string of 1 to 64 characters. dedicated-bearer mbr: Configures the maximum bit rate (MBR) for the dedicated bearer. gbr-up gbr_up: Defines the guaranteed bit rate for uplink traffic. gbr_up must be an integer from 1 to (4 Tbps). gbr-down gbr_down: Defines the guaranteed bit rate for downlink traffic. gbr_down must be an integer from 1 to (4 Tbps). mbr-up mbr_up: Defines the maximum bit rate for uplink traffic. mbr_up must be an integer from 1 to (4 Tbps). mbr-down mbr_down: Defines the maximum bit rate for downlink traffic. mbr_down must be an integer from 1 to (4 Tbps). remove: Deletes the dedicated bearer MBR changes from the configuration for this bearer control profile. Configuring UE AMBR Values Use the following configuration to configure the values for aggregate maximum bit rate stored on the UE (UE AMBR). configure call-control-profile profile_name qos ue-ambr { max-ul mbr_up max-dl mbr_down } remove qos ue-ambr end NOTES: call-control-profile profile_name: Creates an instance of a call control profile. profile_name specifies the name of a call control profile entered as an alphanumeric string of 1 to 64 characters. qos: Configures the quality of service (QoS) parameters to be applied. ue-ambr: Configures the aggregate maximum bit rate stored on the UE (UE AMBR). max-ul mbr_up: Defines the maximum bit rate for uplink traffic. mbr_up must be an integer from 1 to (4 Tbps). max-dl mbr_down: Defines the maximum bit rate for uplink traffic. mbr_down must be an integer from 1 to (4 Tbps). remove: Deletes the configuration from the call control profile. 29

32 Monitoring and Troubleshooting 5G NSA for MME Monitoring and Troubleshooting This section provides information regarding show commands and bulk statistics available to monitor and troubleshoot the 5G NSA feature. Show Commands and Outputs show mme-service db record imsi The output of this command includes the following fields: ARD: Dual-Connectivity-NR-not-allowed Displays True or False to identify if the ARD received from HSS indicates the DCNR feature is allowed for the given IMSI or not. show mme-service name <mme_svc_name> The output of this command includes the "DCNR" field to indicate if the DCNR feature is enabled or disabled at MME service. show mme-service session full all The output of this command includes the following fields: UE DC-NR Information: DC-NR capable UE Indicates whether the UE is DCNR capable. DC-NR operation allowed Indicates whether the DCNR operation is allowed by MME for the DCNR capable UE. show mme-service statistics Dual Connectivity with NR Statistics: Attach Procedure Attach Request Rcvd The number of Attach Request messages received with UE advertising DCNR support. Attach Acc DCNR allowed The number of Attach Accept messages sent by the MME acknowledging the DCNR support for UE (Restrict DCNR bit not set in Attach Accept). Attach Acc DCNR denied The number of Attach Accepts sent by MME rejecting the DCNR support for the UE (Restrict DCNR bit set in Attach Accept). Attach Reject Sent The number of Attach Reject messages sent by MME whose corresponding Attach Request messages have DCNR support capability. Attach Complete Rcvd The number of Attach Complete messages received by MME whose corresponding Attach Request messages have DCNR support capability. 30

33 5G NSA for MME Show Commands and Outputs Intra MME TAU Procedure TAU Request Rcvd The number of TAU Request messages received for Intra-MME TAU procedure with UE advertising DCNR support. TAU Accept DCNR allowed The number of TAU Accept messages sent by the MME acknowledging the DCNR support for UE (Restrict DCNR bit not set in TAU Accept) for Intra-MME TAU procedure. TAU Accept DCNR denied The number of TAU Accept messages sent by the MME rejecting the DCNR support for UE (Restrict DCNR bit set in TAU Accept) for Intra-MME TAU procedure. TAU Complete Rcvd The number of TAU Complete messages received by the MME whose corresponding Intra-MME TAU Requests have DCNR support capability. Inter MME TAU Procedure TAU Request Rcvd The number of TAU Request messages received for Inter-MME TAU procedure with UE advertising DCNR support. TAU Accept DCNR allowed The number of TAU Accept messages sent by the MME acknowledging the DCNR support for UE (Restrict DCNR bit not set in TAU Accept) for Inter-MME TAU procedure. TAU Accept DCNR denied The number of TAU Accept messages sent by the MME rejecting the DCNR support for UE (Restrict DCNR bit set in TAU Accept) for Inter-MME TAU procedure. TAU Reject Sent The number of TAU Reject messages sent by the MME whose corresponding Inter-MME TAU Requests have DCNR support capability. TAU Complete Rcvd The number of TAU Complete messages received by the MME whose corresponding Inter-MME TAU Requests have DCNR support capability. Dual Connectivity with NR Subscribers Attached Calls The number of DCNR supported UEs attached with the MME. Connected Calls The number of DCNR supported UEs in connected mode at the MME. Idle Calls The number of DCNR supported UEs in idle mode at the MME. Node Selection: SGW DNS: Common The number of times S-GW DNS selection procedures are performed with DNS RR excluding the NR network capability. NR Capable The number of times S-GW DNS selection procedures are performed with DNS RR including the NR network capability. SGW Local Config Common The number of times S-GW selection procedures are performed with locally configured S-GW address, without considering the NR network capability. PGW DNS: 31

34 Show Commands and Outputs 5G NSA for MME Common The number of times P-GW DNS selection procedures are performed with DNS RR excluding the NR network capability. NR Capable The number of times P-GW DNS selection procedures are performed with DNS RR including the NR network capability. PGW Local Config: Common The number of times P-GW selection procedures are performed with locally configured P-GW address, without considering the NR network capability. Important When UE is defined with "UE usage type" and "NR Capable", S-GW/P-GW via DNS is selected in the following order: 1. MME chooses S-GW/P-GW that support both +ue and +nr services. 2. If step 1 fails, MME selects S-GW/P-GW that supports +nr service only. 3. If step 2 fails, MME selects S-GW/P-GW that supports +ue service only. 4. If step 3 fails, MME selects S-GW/P-GW without +nr or +ue service. Handover Statistics: Bearer Statistics ERAB Modification Indication Attempted The number of bearers for which the E-RAB Modification Indication procedure is attempted (bearer level stats). Success The number of bearers for which the E-RAB Modification Indication procedure has succeeded (bearer level stats). Failures The number of bearers for which the E-RAB Modification Indication procedure has failed (bearer level stats). ESM Statistics: DCNR User PDN Connections: Attempted The total number of attempts made for DCNR user PDN connections associated with all MME services on the system. Success The total number of successful attempts for DCNR user PDN connections associated with all MME services on the system. Failures The total number of attempts failed for for DCNR user PDN connections associated with all MME services on the system. DCNR User PDN Statistics: All PDNs Displays statistics for all DCNR user PDNs, connected and idle, through the MME service(s) on the system. 32

35 5G NSA for MME Bulk Statistics Connected PDNs Displays statistics for connected DCNR user PDNs through the MME service(s) on the system. Idle PDNs Displays statistics for idle DCNR user PDNs through the MME service(s) on the system. show mme-service statistics s1ap The output of this command includes the following fields: S1AP Statistics: Transmitted S1AP Data: E-RAB Modification Cfm Indicates the number of E-RAB Modification Confirm messages sent by MME upon successful E-RAB modification procedure. Received S1AP Data E-RAB Mod Ind Indicates the number of E-RAB Modification Indication messages received from the master enodeb. Bulk Statistics show subscribers mme-service The output of this command includes the "DCNR Devices" field to indicate the number of DCNR devices that are attached to the MME. This section provides information on the bulk statistics for the 5G NSA feature on MME. MME Schema The following 5G NSA feature related bulk statistics are available in the MME schema. Bulk Statistics attached-dcnr-subscriber connected-dcnr-subscriber idle-dcnr-subscriber dcnr-attach-req dcnr-attach-acc-allowed dcnr-attach-acc-denied Description The current total number of attached subscribers capable of operating in DCNR. The current total number of subscribers capable of operating in DCNR and in connected state. The current total number of subscribers capable of operating in DCNR and in idle state. The total number of Attach Request messages that are received with DCNR supported. The total number of Attach Accept messages that are sent with DCNR allowed. The total number of Attach Accept messages that are sent with DCNR denied. 33

36 MME Schema 5G NSA for MME Bulk Statistics dcnr-attach-rej dcnr-attach-comp dcnr-intra-tau-req dcnr-intra-tau-acc-allowed dcnr-intra-tau-acc-denied dcnr-intra-tau-comp dcnr-inter-tau-req dcnr-inter-tau-acc-allowed dcnr-inter-tau-acc-denied dcnr-inter-tau-rej dcnr-inter-tau-comp s1ap-recdata-erabmodind s1ap-transdata-erabmodcfm erab-modification-indication-attempted erab-modification-indication-success erab-modification-indication-failures emmevent-path-update-attempt Description The total number of DCNR requested Attach Rejected messages. The total number of Attach Complete messages that are received for DCNR supported attaches. The total number of Intra-TAU Request messages that are received with DCNR supported. The total number of Intra-TAU Accept messages that are sent with DCNR allowed. The total number of Intra-TAU Accept messages that are sent with DCNR denied. The total number of Intra-TAU Complete messages that are received for DCNR supported requests. The total number of Inter-TAU Request messages that are received with DCNR supported. The total number of Inter-TAU Accept messages that are sent with DCNR allowed. The total number of Inter-TAU Accept messages that are sent with DCNR denied. The total number of DCNR requested Inter-TAU Request messages that are rejected. The total number of Inter-TAU Complete messages that are received for DCNR supported requests. The total number of S1 Application Protocol - E-RAB Modification Indication messages received from all enodebs. The total number of E-RAB Modification Confirmation messages sent by the MME to the enodeb. The total number of bearers for which E-RAB Modification Indication messages were sent. The total number of bearers for which E-RAB Modification Indication messages were sent. The total number of bearers for which E-RAB Modification Indication failed as shown in E-RAB Modification Indication Confirm message. The total number of EPS Mobility Management events - Path Update attempted. 34

37 5G NSA for MME TAI Schema Bulk Statistics emmevent-path-update-success emmevent-path-update-failure dcnr-dns-sgw-selection-common dcnr-dns-sgw-selection-nr dcnr-dns-sgw-selection-local dcnr-dns-pgw-selection-common dcnr-dns-pgw-selection-nr dcnr-dns-pgw-selection-local esmevent-dcnr-user-pdncon-attempt esmevent-dcnr-user-pdncon-success esmevent-dcnr-user-pdncon-failure pdn-dcnr-user-all pdn-dcnr-user-connected pdn-dcnr-user-idle Description The total number of EPS Mobility Management events - Path Update successes. The total number of EPS Mobility Management events - Path Update failures. The total number of times S-GW DNS selection procedures are performed with DNS RR excluding NR network capability. The total number of times S-GW DNS selection procedures were performed with DNS RR including NR network capability. The total number of times S-GW selection procedures were performed with locally configured S-GW address, without considering the NR network capability. The total number of times P-GW DNS selection procedures were performed with DNS RR excluding NR network capability. The total number of times P-GW DNS selection procedures were performed with DNS RR including NR network capability. The total number of times P-GW selection procedures were performed with locally configured P-GW address, without considering the NR network capability. The total number of EPS Session Management events - DCNR User PDN connections - attempted. The total number of EPS Session Management events - DCNR User PDN connections - successes. The total number of EPS Session Management events - DCNR User PDN connections - failures. The current total number of DCNR user PDN connections in any state. The current total number of DCNR user connected PDNs. The current total number of DCNR user idle PDNs. TAI Schema The following 5G NSA feature related bulk statistics are available in the TAI schema. 35

38 TAI Schema 5G NSA for MME Bulk Statistics tai-esmevent-dcnr-user-pdncon-attempt tai-esmevent-dcnr-user-pdncon-success tai-esmevent-dcnr-user-pdncon-failure Description The total number of DCNR User PDN connection EPS Session Management events attempted per TAI. The total number of successful DCNR User PDN connection EPS Session Management events per TAI. The total number of failed DCNR User PDN connection EPS Session Management events per TAI. 36

39 CHAPTER 5 5G NSA for SAEGW Feature Summary and Revision History, on page 37 Feature Description, on page 39 How It Works, on page 42 Configuring 5G NSA for SAEGW, on page 46 Monitoring and Troubleshooting, on page 50 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area P-GW S-GW SAEGW Applicable Platform(s) ASR 5000 ASR 5500 VPC-DI VPC-SI Feature Default Related Changes in This Release Disabled - Configuration Required Not applicable 37

40 Feature Summary and Revision History 5G NSA for SAEGW Related Documentation 5G Non Standalone Solution Guide AAA Interface Administration and Reference Command Line Interface Reference P-GW Administration Guide S-GW Administration Guide SAEGW Administration Guide Statistics and Counters Reference Revision History The 5G NSA solution for SAEGW supports dcca-custom1, dcca-custom7 and dcca-custom8 dictionaries additionally. The 5G NSA solution for SAEGW supports the following functionality in this release: P-GW Custom Dictionaries support over Gz for extended bitrate S-GW Custom Dictionaries support over Gz for extended bitrate P-GW Custom Dictionaries support over Gy and Rf for extended bitrate S-GW support of Secondary RAT Data Usage Report in Gz CDRs The 5G NSA solution for SAEGW supports the following functionality in this release: P-GW support of Secondary RAT Data Usage Report in Gz CDRs 21.9 P-GW support of Secondary RAT Data Usage Report in Rf CDRs S-GW and P-GW support of statistics for DCNR PDNs The 5G NSA solution is qualified on the ASR 5000 platform. The 5G NSA solution for SAEGW supports the following functionality in this release: Feature License Dedicated Bearers Gy interface URLLC QCI First introduced

41 5G NSA for SAEGW Feature Description Feature Description Cisco 5G Non Standalone (NSA) solution leverages the existing LTE radio access and core network (EPC) as an anchor for mobility management and coverage. This solution enables operators using the Cisco EPC Packet Core to launch 5G services in shorter time and leverage existing infrastructure. Thus, NSA provides a seamless option to deploy 5G services with very less disruption in the network. Overview 5G is the next generation of 3GPP technology, after 4G/LTE, defined for wireless mobile data communication. The 5G standards are introduced in 3GPP Release 15 to cater to the needs of 5G networks. The two solutions defined by 3GPP for 5G networks are: 5G Non Standalone (NSA): The existing LTE radio access and core network (EPC) is leveraged to anchor the 5G NR using the Dual Connectivity feature. This solution enables operators to provide 5G services with shorter time and lesser cost. Note The 5G NSA solution is supported in this release. 5G Standalone (SA): An all new 5G Packet Core will be introduced with several new capabilities built inherently into it. The SA architecture comprises of 5G New Radio (5G NR) and 5G Core Network (5GC). Network Slicing, CUPS, Visualization, Multi-Gbps support, Ultra low latency, and other such aspects will be natively built into the 5G SA Packet Core architecture. Dual Connectivity The E-UTRA-NR Dual Connectivity (EN-DC) feature supports 5G New Radio (NR) with EPC. A UE connected to an enodeb acts as a Master Node (MN) and an en-gnb acts as a Secondary Node (SN). The enodeb is connected to the EPC through the S1 interface and to the en-gnb through the X2 interface. The en-gnb can be connected to the EPC through the S1-U interface and other en-gnbs through the X2-U interface. The following figure illustrates the E-UTRA-NR Dual Connectivity architecture. 39

42 Feature Description 5G NSA for SAEGW Figure 4: EN-DC Architecture If the UE supports dual connectivity with NR, then the UE must set the DCNR bit to "dual connectivity with NR supported" in the UE network capability IE of the Attach Request/Tracking Area Update Request message. If the UE indicates support for dual connectivity with NR in the Attach Request/Tracking Area Update Request message, and the MME decides to restrict the use of dual connectivity with NR for the UE, then the MME sets the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept/Tracking Area Update Accept message. If the RestrictDCNR bit is set to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept/Tracking Area Update Accept message, the UE provides the indication that dual connectivity with NR is restricted to the upper layers. If the UE supports DCNR and DCNR is configured on MME, and if HSS sends ULA/IDR with "Access-Restriction" carrying "NR as Secondary RAT Not Allowed", MME sends the "NR Restriction" bit set in "Handover Restriction List" IE during Attach/TAU/Handover procedures. Similarly, MME sets the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept/Tracking Area Update Accept message. Accordingly, UE provides the indication that dual connectivity with NR is restricted to the upper layers. The "Handover Restriction List" IE is present in the "Initial Context Setup Request" message for Attach and TAU procedure with data forwarding procedure, in the "Handover Required" message for S1 handover procedure, in the "Downlink NAS Transport" message for TAU without active flag procedure. Important 5G NSA feature is license controlled from release 21.8 onwards. Contact your Cisco account representative for detailed information on specific licensing requirements. The 5G NSA solution for SAEGW supports the following functionalists: High Throughput 5G NR offers downlink data throughput up to 20 Gbps and uplink data throughput up to 10 Gbps. Some interfaces in EPC have the support to handle (encode/decode) 5G throughput. For example, NAS supports up to 65.2 Gbps (APN-AMBR) and S5/S8/S10/S3 (GTP-v2 interfaces) support up to 4.2 Tbps. The diameter interfaces S6a and Gx support only up to 4.2Gbps throughput, S1-AP supports only up to 10 40

43 5G NSA for SAEGW Feature Description Gbps and NAS supports up to 10 Gbps (MBR, GBR). New AVP/IE have been introduced in S6a, Gx, S1-AP, and NAS interfaces to support 5G throughput. See the How It Works section for more information. DCNR Support on P-GW: Supports configuration of DCNR feature at the P-GW-service, by configuring Extended-BW-NR feature in IMSA service. Advertises the DCNR feature support by sending Extended-BW-NR feature bit in Feature-List-ID-2 towards PCRF. Forwards AVP "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL" in CCR messages when it receives APN-AMBR values greater than 4.2Gbps from MME/S-GW. Decodes the extended AVP "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL" when it is received from PCRF. Sends AVP "Extended-Max-Requested-BW-UL", "Extended-Max-Requested-BW-DL", "Extended-GBR-UL" and "Extended-GBR-DL" when it receives MBR and GBR values greater than 4.2Gbps from MME/S-GW. Decodes the AVP "Extended-Max-Requested-BW-UL", "Extended-Max-Requested-BW-DL", "Extended-GBR-UL" and "Extended-GBR-DL" when received from PCRF. Supports dedicated bearer establishment with extended QoS. Sends AVP Extended-Max-Requested-BW-UL and "Extended-Max-Requested-BW-DL" in Gy records. Ultra Low Latency Support: Supports 5G requirements of Ultra-Reliable and Low Latency Communications (URLLC). 3GPP introduced URLCC QCI 80 (Non-GBR resource type), QCI 82 and 83 (GBR resource type). P-GW establishes default bearers with URLLC QCI 80, which is typically used by low latency embb applications. P-GW establishes dedicated bearers with URLLC QCI 82 and 83 (also with QCI 80 if dedicated bearers of Non-GBR type to be established), which is typically used by discrete automation services (industrial automation). Dynamic S-GW and P-GW selection by MME for DCNR capable UE When DCNR capable UE attempts to register in MME and when all DCNR validations are successful (for example DCNR feature configuration on MME, HSS not sending access-restriction for NR, and son on), the MME sets UP Function Selection Indication Flags IE with DCNR flag set to 1 in Create Session Request message. This feature is relevant for CUPS architecture to help SGW-C and PGW-C to select SGW-U and PGW-U which supports dual connectivity with NR. When S-GW receives this IE over S11, it sends this IE over S5 to P-GW. S-GW ignores IE if it receives it in Non-CUPS deployment. P-GW Secondary RAT Usage Data Report Handling: P-GW supports custom24 and custom44 for Gz and aaa-custom3, aaa-custom4 and aaa-custom6 dictionaries for Rf to support Secondary RAT Data Usage Report in CDRs. Statictics support for DCNR PDNs: S-GW and P-GW statistics support for DCNR PDNs Multiple Presence Reporting Area P-GW supports negotiation of Multiple-Presence Reporting Area feature in Feature-List-ID 2 over Gx interface with PCRF. The CNO-ULI feature will be used only when the P-GW and/or the PCRF does not support Multiple-PRA and both P-GW and PCRF support CNO-ULI. Note This feature is introduced in release For more information, refer to the Presence Reporting Area chapter in the P-GW Administration Guide. 41

44 How It Works 5G NSA for SAEGW How It Works Architecture This section describes the architecture for Gx (PCRF), Gy (OCS), Gz (P-GW), and Rf (P-GW) interfaces with respect to 5G NSA for SEAEGW feature. Gx (PCRF) The Gx interface supports new AVPs to handle 5G throughput for default bearers and dedicated bearers. Gx interface introduced new "AVP Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL" in grouped "AVP QoS-Information" and "Conditional-APN-Aggregate-Max-Bitrate" to handle 5G throughput for default bearers. New AVPs "Extended-GBR-UL", "Extended-GBR-DL", "Extended-Max-Requested-BW-UL" and "Extended-Max-Requested-BW-DL" are added in grouped AVP "QoS-Information" for dedicated bearers. When the maximum bandwidth value set for UL or DL traffic is higher than bits per second, the "Max-Requested-Bandwidth-UL" or DL, AVP must be present, and set to its upper limit along with the "Extended-Max-Requested-BW-UL" or DL must be present, and set to the requested bandwidth value in kilobits per second. The same principal applies for "Extended-GBR-UL/DL" and "Extended-APN-AMBR-UL/DL". The following new AVPs are introduced in the grouped AVP QoS-Information: Extended-Max-Requested-BW-UL Extended-Max-Requested-BW-DL Extended-GBR-UL Extended-GBR-DL Extended-APN-AMBR-UL Extended-APN-AMBR-DL the following new AVPs are introduced in the grouped AVP Conditional-APN-Aggregate-Max-Bitrate. Extended-APN-AMBR-UL Extended-APN-AMBR-DL Gy (OCS) New AVPs "Extended-Max-Request-BW-UL", "Extended-Max-Requested-BW-DL", "Extended-GBR-UL", "Extended-GBR-DL", "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL" in grouped AVP QoS-Information are introduced Gy interface to handle 5G throughput for dedicated bearers. When the maximum bandwidth value set for UL/DL traffic is higher than bits per second, P-GW sets the "Max-Requested-Bandwidth-UL/DL" AVP to its upper limit and sets the "Extended-Max-Requested-BW-UL/DL" to the required bandwidth value in kilobits per second in CCR-I/CCR-U messages. The same principal applies for "Extended-GBR-UL/DL" and "Extended-APN-AMBR-UL/DL". 42

45 5G NSA for SAEGW Limitations 5G NSA feature supports Gy dcca-custom1, dcca-custom7, dcca-custom8 and standard dcca-custom13 dictionaries. Gz (P-GW) New sequence of container in PGWRecord for PGW-CDR to support RAN secondary RAT usage data report is introduced in Gz interface. AVPs "listofransecondaryratusagereports" and "RANSecondaryRATUsageReport" are introduced. New AVPs "Extended-Max-Requested-BW-UL", "Extended-Max-Requested-BW-DL", "Extended-GBR-UL", "Extended-GBR-DL", "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL" are introduced over Gz interface as part of existing "EPCQoSInformation" AVP to handle 5G throughput for default and dedicated bearers. Rf (P-GW) New AVPs "RAN-Secondary-RAT-Usage-Report" which is grouped type to support secondary RAT usage data report values is introduced in Rf interface. This contains the volume count as reported by the RAN for the secondary RAT(separated for uplink and downlink) including the time of the report. AVPs "Extended-Max-Requested-BW-UL", "Extended-Max-Requested-BW-DL", "Extended-GBR-UL", "Extended-GBR-DL", "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL" are introduced over Rf interface to handle 5G throughput for default and dedicated bearers. Gz(S-GW) New sequence of container in SGWRecord for SGW-CDR to support RAN secondary RAT usage data report is introduced in Gz interface. AVPs "listofransecondaryratusagereports" and "RANSecondaryRATUsageReport" are introduced. New AVPs "Extended-Max-Requested-BW-UL", "Extended-Max-Requested-BW-DL", "Extended-GBR-UL", "Extended-GBR-DL", "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL" are introduced over Gz interface as part of existing "EPCQoSInformation" AVP to handle 5G throughput for default and dedicated bearers. Limitations This section describes the known limitations for 5G NSA feature 5G NSA has been implemented for Gy dictionaries dcca-custom1, dcca-custom7, dcca-custom8 and standard dcca-custom13. In order to support NSA for other Gx and Gy dictionaries, dynamic dictionary must be built. Contact your Cisco Account representative for more details. Secondary RAT usage data report will not carry start or end time values prior to 00:00:00 UTC, Thursday, 1 January 1970". Flows This section describes the following call flows related to the DCNR feature. 43

46 Flows 5G NSA for SAEGW Initial Registration by DCNR Capable UE Step Description The DCNR capable UE sets the "DCNR bit" in the NAS message "Attach Request" of "UE Network Capability" IE. MME successfully authenticates the UE. As part of the authorization process, while sending ULR to HSS, MME advertises the DCNR support by sending NR as Secondary RAT" feature bit in Feature-List-ID-2". HSS sends ULA by advertising the DCNR by sending "NR as Secondary RAT" feature bit in Feature-List-ID-2" and sends Max-Requested-Bandwidth-UL as bps, Max-Requested-Bandwidth-DL as bps and the extended bandwidth values in new AVPs "Extended-Max-Requested-BW-UL" and "Extended-Max-Requested-BW-DL". If HSS determines that the UE is not authorized for DCNR services, HSS sends Subscription-Data with Access-Restriction" carrying NR as Secondary RAT Not Allowed". MME sends Create Session Request with the extended APN-AMBR values in existing AMBR IE. As the APN-AMBR values in GTP-v2 interface are encoded in kbps, the existing AMBR IE handles the 5G NSA bit rates. P-W sends CCR-I to PCRF advertising the DCNR by sending Extended-BW-NR" feature bit in Feature-List-ID-2". P-GW also sends "APN-Aggregate-Max-Bitrate-UL" as bps, "APN-Aggregate-Max-Bitrate-DL" as bps and the extended bandwidth values in new AVPs "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL". 44

47 5G NSA for SAEGW Flows Step Description PCRF sends CCA-I advertising the DCNR by sending the Extended-BW-NR" feature bit in Feature-List-ID-2". PCRF also sends "APN-Aggregate-Max-Bitrate-UL" as bps and "APN-Aggregate-Max-Bitrate-DL" as bps and the extended bandwidth values in new "AVPs Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL". PCRF offers the same extended APN-AMBR values requested by PCEF or modify the extended APN-AMBR values. P-GW enforces the APN-AMBR values accordingly. P-GW honors the APN-AMBR values as offered by PCRF and sends the extended APN-AMBR values in existing IE APN-AMBR in the Create Session Response message. MME computes the UE-AMBR values and sends the extended UE-AMBR values in new IEs Extended UE Aggregate Maximum Bit Rate Downlink" and Extended UE Aggregate Maximum Bit Rate Uplink" by setting the legacy UE AMBR Uplink" and UE AMBR Downlink" values to the maximum allowed value bps(10 Gbps) in Initial Context Setup Request. MME sends the APN-AMBR values up to 65.2 Gbps in existing IE APN-AMBR in NAS Activate Default EPS Bearer Context Request Attach Accept. If the APN-AMBR values are beyond 65.2 Gbps, MME sends the extended APN-AMBR values in new IE Extended APN aggregate maximum bit rate. If ULA is received with Access-Restriction" carrying NR as Secondary RAT Not Allowed", MME sends the Initial Context Setup Request" with NR Restriction" bit set in Handover Restriction List" IE. Also MME sets the "RestrictDCNR" bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept message. Accordingly, UE provides the indication that DCNR is restricted to the upper layers. If DCNR is not configured at MME service or call control profile level, MME sets the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the Attach Accept message. Accordingly, UE provides the indication that DCNR is restricted to the upper layers. enodeb sends the Initial Context Setup Response message. If master enodeb determines to establish the bearer on secondary enodeb, F-TEID of secondary enodeb may be sent in this step (Transport layer address and TEID of secondary enodeb). It is transparent to MME if the bearer is established on master enodeb or secondary enodeb. enodeb sends Uplink NAS Transport with NAS message Attach Complete - Activate Default EPS Bearer Context Accept. MME sends Modify Bearer Request to S-GW with S1-U FTEID details as received in the Initial Context Setup Response message. MME receives the Modify Bearer Response message from S-GW. 45

48 Supported Standards 5G NSA for SAEGW Supported Standards Cisco's implementation of the 5G NSA complies with the following standards: 3GPP Release General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access 3GPP Release Policy and Charging Control (PCC) 3GPP Release GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunneling Protocol for Control plane (GTPv2-C); Stage 3 3GPP Release Charging Management; Diameter Charging Applications 3GPP Release Charging Management; Charging Data Record (CDR) parameter description Configuring 5G NSA for SAEGW This section describes how to configure 5G NSA to support SAEGW. Configuring 5G NSA on SAEGW involves: Enabling DCNR in P-GW Service, on page 46 Configuring Bearer Duration Statistics for URLLC QCI, on page 47 Configuring EGTPC QCI Statistics for URLLC QCI, on page 47 Configuring Extended Bandwidth with New Radio, on page 48 Configuring Network-Initiated Setup/Teardown Events for URLLC QCI, on page 48 Configuring URLLC QCI in APN Configuration, on page 49 Configuring URLCC QCI In Charging Action, on page 49 Configuring URLCC QCI in QCI QOS Mapping Table, on page 50 Enabling DCNR in P-GW Service Use the following configuration to enable Dual Connectivity with New Radio (DCNR) to support 5G Non Standalone (NSA). configure context context_name pgw-service service_name [ no ] dcnr end NOTES: pgw-service service_name: Creates an P-GW service or configures a existing P-GW service. service_name must be an alphanumeric string of 1 to 63 characters. no: Disables the DCNR configuration. 46

49 5G NSA for SAEGW Configuring Bearer Duration Statistics for URLLC QCI The dcnr CLI command is disabled by default. Configuring Bearer Duration Statistics for URLLC QCI Use the following configuration to configure QCI based duration statistics for URLLC QCI. configure context context_name apn apn_name [ no ] bearer-duration-stats qci qci_val end NOTES: apn apn_name: Creates or deletes Access Point Name (APN) templates and enters the APN Configuration Mode within the current context. apn_name specifies a name for the APN template as an alphanumeric string of 1 through 62 characters that is case insensitive. bearer-duration-stats: Enables or disables per QCI call duration statistics for dedicated bearers. qci qci_val: Specifies the QoS Class Identifier. qci_val must be an integer between 1 to 9, 80, 82, and 83. no: Disables per QCI call duration statistics. Configuring EGTPC QCI Statistics for URLLC QCI Use the following configuration to configure QCI based EGTPC QCI statistics for URLLC QCI. configure context context_name apn apn_name [ no ] egtpc-qci-stats { qci80 qci82 qci83 } default egtpc-qci-stats end Notes: apn apn_name: Creates or deletes Access Point Name (APN) templates and enters the APN Configuration Mode within the current context. apn_name specifies a name for the APN template as an alphanumeric string of 1 through 62 characters that is case insensitive. egtpc-qci-stats: Enables/Disables an APN candidate list for the apn-expansion bulkstats schema. qci80: Configure apn-qci-egtpc statistics for QCI 80. qci82: Configure apn-qci-egtpc statistics for QCI 82. qci83: Configure apn-qci-egtpc statistics for QCI 83. no: Disables APN candidate list(s) for the apn-expansion bulkstats schema. default: Disables an APN candidate list for the apn-expansion bulkstats schema. 47

50 Configuring Extended Bandwidth with New Radio 5G NSA for SAEGW Configuring Extended Bandwidth with New Radio Use the following configuration to configure extended bandwidth with new radio in IMS authorization service mode. configure context context_name ims-auth-service ims_auth_service_name policy-control diameter encode-supported-features extended-bw-newradio [ no ] diameter encode-supported-features end NOTES: ims-auth-service ims_auth_service_name: Creates an IMS authentication service. ims_auth_service_name must be an alphanumeric string of 1 through 63 characters. policy-control: Configures Diameter authorization and policy control parameter for IMS authorization. extended-bw-newradio: Enables extended bandwidth with New-Radio feature. diameter encode-supported-features: Enables/Disables encoding and sending of Supported-Features AVP. no: Removes the configuration of extended bandwidth with new-radio in IMS authorization service mode. Configuring Network-Initiated Setup/Teardown Events for URLLC QCI Use the following configuration to configure network initiated setup or teardown events KPI for URLCC QCI. configure transaction-rate nw-initiated-setup-teardown-events qci qci_val [ default no ] transaction-rate nw-initiated-setup-teardown-events qci end NOTES: transaction-rate nw-initiated-setup-teardown-events: Enables operators to set the Quality of Class Identifier (QCI) value for use in tracking Network Initiated Setup/Tear down Events per Second key performance indicator (KPI) information. qci qci_val: Specifies the QoS Class Identifier. qci_val must be an integer between 1 to 9, 65, 66, 69, 70, 80, 82, 83, and 128 to 254. no: Disables the collection of network-initiated setup/teardown events for the specified QCI value. default: Returns the setting to its default value. The default is for network-initiated setup/teardown events to be tracked for all supported QCI values. 48

51 5G NSA for SAEGW Configuring URLLC QCI in APN Configuration Configuring URLLC QCI in APN Configuration Use the following configuration to configure URLCC QCI in the APN Configuration mode. configure context context_name apn apn_name qos rate-limit direction { downlink uplink } qci qci_val no qos rate-limit direction { downlink uplink } end NOTES: apn apn_name: Allows to specify the APN name as a condition. apn_name must be an alphanumeric string of 1 through 63 characters. qos rate-limit: Configures the action on a subscriber traffic flow that violates or exceeds the peak/committed data rate under traffic shaping and policing functionality. direction { downlink uplink }: Specifies the direction of traffic on which this QoS configuration needs to be applied. downlink: Apply the specified limits and actions to the downlink. uplink: Apply the specified limits and actions to the uplink. qci qci_val: Specifies the QoS Class Identifier. qci_val must be an integer between 1 to 9, 80, 82, and 83. no: Disables the QoS data rate limit configuration for the APN. Configuring URLCC QCI In Charging Action Use the following configuration to configure URLCC QCI in the Charging Action Configuration mode. configure active-charging service service_name charging-action charging_action_name qos-class-identifier qos_class_identifier no qos-class-identifier end NOTES: active-charging service service_name: Specifies name of the active charging service. service_name must be an alphanumeric string of 1 through 15 characters. charging-action charging_action_name : Creates a charging action. qos_class_identifier must be an alphanumeric string of 1 through 63 characters. qos-class-identifier qos_class_identifier: Specifies the QoS Class Identifier. qos_class_identifier must be an integer between 1 to 9, 65, 66, 69, 70, 80, 82, and 83. no: Disables the QoS Class Identifier. 49

52 Configuring URLCC QCI in QCI QOS Mapping Table 5G NSA for SAEGW Configuring URLCC QCI in QCI QOS Mapping Table Use the following configuration to configure URLCC QCI in the QCI QOS Mapping Table. configure qci-qos-mapping name [ no ] qci qci_value end NOTES: qci-qos-mapping name: Specifies the map name. name must be an alphanumeric string of 1 through 63 characters. qci qci_val: Specifies the QoS Class Identifier. qci_val must be an integer between 1 to 9, 65, 66, 69, 70, 80, 82, and 83. no: Disables the QCI value. Monitoring and Troubleshooting This section provides information regarding show commands and bulk statistics available to monitor and troubleshoot the 5G NSA feature. Show Commands and Outputs This section provides information on show commands and their corresponding outputs for the DCNR feature. show pgw-service name The output of this command includes the "DCNR" field to indicate if the DCNR feature is enabled or disabled at P-GW service. show ims-authorization service name The output of this command includes the following fields: Diameter Policy Control: Supported Features: extended-bw-nr show gtpu statistics The output of this command includes the following fields: Uplink Packets Displays the total number of QCI 80, QCI 82, and QCI 83 uplink packets. Uplink Bytes Displays the total number of QCI 80, QCI 82, and QCI 83 uplink bytes. Downlink Packets Displays the total number of QCI 80, QCI 82, and QCI 83 downlink packets. Downlink Bytes Displays the total number of QCI 80, QCI 82, and QCI 83 downlink bytes. 50

53 5G NSA for SAEGW Show Commands and Outputs Packets Discarded Displays the total number of discarded QCI 80, QCI 82, and QCI 83 packets. Bytes Discarded Displays the total number of discarded QCI 80, QCI 82, and QCI 83 bytes. show apn statistics all The output of this command includes the following fields: 4G Bearers Released By Reasons: Admin disconnect Displays dedicated bearers released due to administration clear from P-GW for QCI 80, QCI 82, and QCI 83. Bearer Active Displays the total number for QCI 80, QCI 82, and QCI 83 active bearers. Bearer setup Displays the total number for QCI 80, QCI 82, and QCI 83 bearers setup. Bearer Released Displays the total number for QCI 80, QCI 82, and QCI 83 released bearers. Bearer Rejected Uplink Bytes Forwarded Displays the total number for QCI 80, QCI 82, and QCI 83 uplink packets forwarded. Uplink pkts forwarded Displays the total number for QCI 80, QCI 82, and QCI 83 downlink packets forwarded. Uplink Bytes dropped Displays the total number for QCI 80, QCI 82, and QCI 83 uplink bytes forwarded. Downlink Bytes forwarded Displays the total number for QCI 80, QCI 82, and QCI 83 downlink bytes forwarded. Uplink pkts dropped Displays the total number for QCI 80, QCI 82, and QCI 83 uplink packets dropped. Downlink Bytes dropped Displays the total number for QCI 80, QCI 82, and QCI 83 downlink bytes dropped. Uplink Bytes dropped(mbr Excd) Displays the total number for QCI 80, QCI 82, and QCI 83 uplink bytes dropped due to MBR being exceeded. Uplink pkts dropped(mbr Excd) Displays the total number for QCI 80, QCI 82, and QCI 83 uplink packets dropped due to MBR being exceeded. Downlink pkts forwarded Displays the total number for QCI 80, QCI 82, and QCI 83 downlink packets forwarded. Downlink pkts dropped Displays the total number for QCI 80, QCI 82, and QCI 83 downlink packets dropped. Downlink Bytes dropped(mbr Excd) Displays the total number for QCI 80, QCI 82, and QCI 83 downlink bytes dropped due to MBR being exceeded. Downlink pkts dropped(mbr Excd) Displays the total number for QCI 80, QCI 82, and QCI 83 downlink packets dropped due to MBR being exceeded. 51

54 Show Commands and Outputs 5G NSA for SAEGW show pgw-service statistics all verbose The output of this command includes the following fields: Bearers By QoS characteristics: Active Displays the total number of active bearers for QCI 80, QCI 82, and QCI 83. Released Displays the total number of bearers released for QCI 80, QCI 82, and QCI 83. Setup Displays the total number of bearers setup for QCI 80, QCI 82, and QCI 83. Data Statistics Per PDN-Type: Uplink: Packets Displays the total number of uplink packets forwarded for QCI 80, QCI 82, and QCI 83. Bytes Displays the total number of uplink bytes forwarded for QCI 80, QCI 82, and QCI 83. Dropped Packets Displays the total number of uplink packets dropped for QCI 80, QCI 82, and QCI 83. Dropped Bytes Displays the total number of uplink bytes dropped for QCI 80, QCI 82, and QCI 83. Downlink: Packets Displays the total number of downlink packets forwarded for QCI 80, QCI 82, and QCI 83. Bytes Displays the total number of downlink bytes forwarded for QCI 80, QCI 82, and QCI 83. Dropped Packets Displays the total number of downlink packets dropped for QCI 80, QCI 82, and QCI 83. Dropped Bytes Displays the total number of downlink bytes dropped for QCI 80, QCI 82, and QCI 83. DCNR PDN Statistics: Active The total number of current active P-GW DCNR PDNs. Setup The total number of P-GW PDNs that are setup as a DCNR PDN. Released The total number of P-GW DCNR PDNs released. show sgw-service statistics all verbose The output of this command includes the following fields: Bearers By QoS characteristics: Active Displays the total active EPS Bearers for QCI 80, QCI 82, and QCI 83. Released Displays the total number of EPS Bearers released for QCI 80, QCI 82, and QCI 83. Setup Displays the total number of EPS bearers setup for QCI 80, QCI 82, and QCI 83. Modified Displays the total number of EPS bearers modified for QCI 80, QCI 82, and QCI 83. Dedicated Bearers Released By Reason: 52

55 5G NSA for SAEGW Show Commands and Outputs P-GW Initiated Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason P-GW initiated on the S-GW. S1 Error Indication Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason S1 error indication on the S-GW. S5 Error Indication Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason S5 error indication on the S-GW. S4 Error Indication Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason S4 error indication on the S-GW. S12 Error Indication Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason S12 error indication on the S-GW. Local Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason local error indication on the S-GW. PDN Down Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released due to PDN cleanup on the S-GW. Path Failure S1-U Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason S1-U path failure on the S-GW. Path Failure S5-U Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason S5-U path failure on the S-GW. Path Failure S5 Displays the total number of dedicated EPS bearers for QCI 80, QCI 82, and QCI 83 released with the reason S5 path failure on the S-GW. Path Failure S11 Displays the total number of dedicated bearers for QCI 80, QCI 82, and QCI 83 released due to path failure on the S11 interface. Path Failure S4-U Displays the total number of dedicated bearers for QCI 80, QCI 82, and QCI 83 released due to path failure on S4-U interface. Path Failure S12 Displays the total number of dedicated bearers for QCI 80, QCI 82, and QCI 83 released due to path failure on S12 interface. Inactivity Timeout Displays the total number of dedicated bearers for QCI 80, QCI 82, and QCI 83 released due to the inactivity timeout. Other Displays the total number of dedicated bearers for QCI 80, QCI 82, and QCI 83 released due to other reasons. Data Statistics Per Interface: S1-U/S11-U/S4-U/S12/S5-U/S8-U Total Data Statistics: Uplink: Packets Displays the total number of uplink data packets received by the S-GW for a bearer with QCI 80, QCI 82, and QCI 83. Bytes Displays the total number of uplink data bytes received by the S-GW for a bearer with QCI 80, QCI 82, and QCI 83. Dropped Packets Displays the total number of uplink data packets dropped by the S-GW for a bearer with a QCI 80, QCI 82, and QCI

56 Show Commands and Outputs 5G NSA for SAEGW Dropped Bytes Displays the total number of uplink data bytes dropped by the S-GW for a bearer with QCI 80, QCI 82, and QCI 83. Downlink: Packets Displays the total number of downlink data packets received by the S-GW for a bearer with QCI 80, QCI 82, and QCI 83. Bytes Displays the total number of downlink data bytes received by the S-GW for a bearer with QCI 80, QCI 82, and QCI 83. Dropped Packets Displays the total number of downlink data packets dropped by the S-GW for bearer with QCI 80, QCI 82, and QCI 83. Dropped Bytes Displays the total number of downlink data bytes dropped by the S-GW for a bearer with QCI 80, QCI 82, and QCI 83. DCNR PDN Statistics: Active The total number of current active S-GW DCNR PDNs. Setup The total number of S-GW PDNs that are setup as a DCNR PDN. Released The total number of S-GW DCNR PDNs released. show saegw-service statistics all verbose The output of this command includes the following fields: Bearers By QoS characteristics: Active Displays the total number of QCI 80, QCI 82, and QCI 83 active bearers. Released Displays the total number of QCI 80, QCI 82, and QCI 83 released bearers. Setup Displays the total number of QCI 80, QCI 82, and QCI 83 bearers setup. Data Statistics Per PDN-Type: Uplink: Packets Displays the total number of QCI 80, QCI 82, and QCI 83 uplink packets forwarded. Bytes Displays the total number of QCI 80, QCI 82, and QCI 83 uplink bytes forwarded. Dropped Packets Displays the total number of QCI 80, QCI 82, and QCI 83 uplink packets dropped. Dropped Bytes Displays the total number of QCI 80, QCI 82, and QCI 83 uplink bytes dropped. Downlink: Packets Displays the total number of QCI 80, QCI 82, and QCI 83 downlink packets forwarded. Bytes Displays the total number of QCI 80, QCI 82, and QCI 83 downlink bytes forwarded. Dropped Packets Displays the total number of QCI 80, QCI 82, and QCI 83 downlink packets dropped. Dropped Bytes Displays the total number of QCI 80, QCI 82, and QCI 83 downlink bytes dropped. 54

57 5G NSA for SAEGW Bulk Statistics DCNR PDNs: Colocated PDNs: Active The total number of currently active SAEGW collapsed DCNR PDNs. Setup The total number of SAEGW collapsed PDNs that are setup as a DCNR PDN. Released The total number of SAEGW collapsed DCNR PDNs released. PGW-Anchor PDNs: Active The total number of currently active P-GW anchored DCNR PDNs. Setup The total number of P-GW anchored PDNs that are setup as a DCNR PDN. Released The total number of P-GW anchored DCNR PDNs that are released. SGW-Anchor PDNs: Active The total number of current active S-GW anchored DCNR PDNs. Setup The total number of S-GW anchored PDNs that are setup as a DCNR PDN. Released The total number of S-GW anchored DCNR PDNs that are released. Bulk Statistics The following statistics are added in support of the 5G NSA feature. APN Schema The following 5G NSA feature related bulk statistics are available in the APN schema. Bulk Statistics qci80-actbear qci82-actbear qci83-actbear qci80-setupbear qci82-setupbear qci83-setupbear qci80-relbear qci82-relbear qci83-relbear qci80-uplinkpkt-fwd qci82-uplinkpkt-fwd Description The total number of QCI80 active bearers. The total number of QCI82 active bearers. The total number of QCI83 active bearers. The total number of QCI80 bearers setup. The total number of QCI82 bearers setup. The total number of QCI83 bearers setup. The total number of QCI80 released bearers. The total number of QCI82 released bearers. The total number of QCI83 released bearers. The total number of QCI80 uplink packets forwarded. The total number of QCI82 uplink packets forwarded. 55

58 APN Schema 5G NSA for SAEGW Bulk Statistics qci83-uplinkpkt-fwd qci80-dwlinkpkt-fwd qci82-dwlinkpkt-fwd qci83-dwlinkpkt-fwd qci80-uplinkbyte-fwd qci82-uplinkbyte-fwd qci83-uplinkbyte-fwd qci80-dwlinkbyte-fwd qci82-dwlinkbyte-fwd qci83-dwlinkbyte-fwd qci80-uplinkpkt-drop qci82-uplinkpkt-drop qci83-uplinkpkt-drop qci80-dwlinkpkt-drop qci82-dwlinkpkt-drop qci83-dwlinkpkt-drop qci80-uplinkbyte-drop qci82-uplinkbyte-drop qci83-uplinkbyte-drop qci80-dwlinkbyte-drop qci82-dwlinkbyte-drop qci83-dwlinkbyte-drop qci80-uplinkpkt-drop-mbrexcd qci82-uplinkpkt-drop-mbrexcd Description The total number of QCI83 uplink packets forwarded. The total number of QCI80 downlink packets forwarded. The total number of QCI82 downlink packets forwarded. The total number of QCI83 downlink packets forwarded. The total number of QCI80 uplink bytes forwarded. The total number of QCI82 uplink bytes forwarded. The total number of QCI83 uplink bytes forwarded. The total number of QCI80 downlink bytes forwarded. The total number of QCI82 downlink bytes forwarded. The total number of QCI83 downlink bytes forwarded. The total number of QCI80 uplink packets dropped. The total number of QCI82 uplink packets dropped. The total number of QCI83 uplink packets dropped. The total number of QCI80 downlink packets dropped. The total number of QCI82 downlink packets dropped. The total number of QCI83 downlink packets dropped. The total number of QCI80 uplink bytes dropped. The total number of QCI82 uplink bytes dropped. The total number of QCI83 uplink bytes dropped. The total number of QCI80 downlink bytes dropped. The total number of QCI82 downlink bytes dropped. The total number of QCI83 downlink bytes dropped. The total number of QCI80 uplink packets dropped due to MBR being exceeded. The total number of QCI82 uplink packets dropped due to MBR being exceeded. 56

59 5G NSA for SAEGW P-GW Schema Bulk Statistics qci83-uplinkpkt-drop-mbrexcd qci80-dwlinkpkt-drop-mbrexcd qci82-dwlinkpkt-drop-mbrexcd qci83-dwlinkpkt-drop-mbrexcd qci80-uplinkbyte-drop-mbrexcd qci82-uplinkbyte-drop-mbrexcd qci83-uplinkbyte-drop-mbrexcd qci80-dwlinkbyte-drop-mbrexcd qci82-dwlinkbyte-drop-mbrexcd qci83-dwlinkbyte-drop-mbrexcd qci80-rejbearer qci82-rejbearer qci83-rejbearer sessstat-bearrel-ded-admin-clear-qci80 sessstat-bearrel-ded-admin-clear-qci82 sessstat-bearrel-ded-admin-clear-qci83 Description The total number of QCI83 uplink packets dropped due to MBR being exceeded. The total number of QCI80 downlink packets dropped due to MBR being exceeded. The total number of QCI82 downlink packets dropped due to MBR being exceeded. The total number of QCI83 downlink packets dropped due to MBR being exceeded. The total number of QCI80 uplink bytes dropped due to MBR being exceeded. The total number of QCI82 uplink bytes dropped due to MBR being exceeded. The total number of QCI83 uplink bytes dropped due to MBR being exceeded. The total number of QCI80 uplink bytes dropped due to MBR being exceeded. The total number of QCI82 uplink bytes dropped due to MBR being exceeded. The total number of QCI83 uplink bytes dropped due to MBR being exceeded. The total number of QCI80 rejected bearers. The total number of QCI82 rejected bearers. The total number of QCI83 rejected bearers. The total number dedicated bearers released due to admin clear from P-GW for QCI80. The total number dedicated bearers released due to admin clear from P-GW for QCI82. The total number dedicated bearers released due to admin clear from P-GW for QCI83. P-GW Schema The following 5G NSA feature related bulk statistics available in the P-GW schema. 57

60 SAEGW Schema 5G NSA for SAEGW Bulk Statistics pgw-anchor-pdns-dcnr-current-active pgw-anchor-pdns-dcnr-cumulative-activated pgw-anchor-pdns-dcnr-cumulative-deactivated sessstat-pdn-dcnr-current-active sessstat-pdn-dcnr-cumulative-activated sessstat-pdn-dcnr-cumulative-deactivated Description The total number of currently active P-GW anchored DCNR PDNs. The total number of P-GW anchored PDNs that are setup as DCNR PDN. The total number of P-GW anchored PDNs that were either released or degrades to a non-dncr PDN. Session Statistics - DCNR PDN-Type Statistics - Current Active. Session Statistics - DCNR PDN-Type Statistics - Cumulative PDNs Activated. Session Statistics - DCNR PDN-Type Statistics - Cumulative PDNs Deactivated. SAEGW Schema The following 5G NSA feature related bulk statistics available in the SAEGW schema. Bulk Statistics saegw-collocated-pdns-dcnr-current-active saegw-collocated-pdns-dcnr-cumulative-activated saegw-collocated-pdns-dcnr-cumulative-deactivated Description The total number of currently active SAEGW collapsed DCNR PDNs. The total number of SAEGW collapsed PDNs that are setup as a DCNR PDN. The total number of SAEGW collapsed DCNR PDNs released. S-GW Schema The following 5G NSA feature related bulk statistics available in the S-GW schema. Bulk Statistics sessstat-pdn-dcnr-current-active sessstat-pdn-dcnr-cumulative-activated sessstat-pdn-dcnr-cumulative-deactivated sgw-anchor-pdns-dcnr-current-active sgw-anchor-pdns-dcnr-cumulative-activated Description The total number of currently active S-GW DCNR PDNs. The total number of S-GW PDNs that are setup as a DCNR PDN. The total number of S-GW DCNR PDNs released. The total number of currently active S-GW anchored DCNR PDNs. The total number of S-GW anchored PDNs that are setup as a DCNR PDN. 58

61 5G NSA for SAEGW System Schema Bulk Statistics sgw-anchor-pdns-dcnr-cumulative-deactivated Description The total number of S-GW anchored DCNR PDNs that are released. System Schema The following 5G NSA feature related bulk statistics are available in the System schema. Bulk Statistics sess-bearerdur-5sec-qci80 sess-bearerdur-5sec-qci82 sess-bearerdur-5sec-qci83 sess-bearerdur-10sec-qci80 sess-bearerdur-10sec-qci82 sess-bearerdur-10sec-qci83 sess-bearerdur-30sec-qci80 sess-bearerdur-30sec-qci82 sess-bearerdur-30sec-qci83 sess-bearerdur-1min-qci80 sess-bearerdur-1min-qci82 sess-bearerdur-1min-qci83 sess-bearerdur-2min-qci80 sess-bearerdur-2min-qci82 Description The current number of bearer sessions with a duration of 5 seconds and having a QCI of 80. The current number of bearer sessions with a duration of 5 seconds and having a QCI of 82. The current number of bearer sessions with a duration of 5 seconds and having a QCI of 83. The current number of bearer sessions with a duration of 10 seconds and having a QCI of 80. The current number of bearer sessions with a duration of 10 seconds and having a QCI of 82. The current number of bearer sessions with a duration of 10 seconds and having a QCI of 83. The current number of bearer sessions with a duration of 30 seconds and having a QCI of 80. The current number of bearer sessions with a duration of 30 seconds and having a QCI of 82. The current number of bearer sessions with a duration of 30 seconds and having a QCI of 83. The current number of bearer sessions with a duration of 1 minute and having a QCI of 80. The current number of bearer sessions with a duration of 1 minute and having a QCI of 82. The current number of bearer sessions with a duration of 1 minute and having a QCI of 83. The current number of bearer sessions with a duration of 2 minutes and having a QCI of 80. The current number of bearer sessions with a duration of 2 minutes and having a QCI of

62 System Schema 5G NSA for SAEGW Bulk Statistics sess-bearerdur-2min-qci83 sess-bearerdur-5min-qci80 sess-bearerdur-5min-qci82 sess-bearerdur-5min-qci83 sess-bearerdur-15min-qci80 sess-bearerdur-15min-qci82 sess-bearerdur-15min-qci83 sess-bearerdur-30min-qci80 sess-bearerdur-30min-qci82 sess-bearerdur-30min-qci83 sess-bearerdur-1hr-qci80 sess-bearerdur-1hr-qci82 sess-bearerdur-1hr-qci83 sess-bearerdur-4hr-qci80 sess-bearerdur-4hr-qci82 sess-bearerdur-4hr-qci83 sess-bearerdur-12hr-qci80 sess-bearerdur-12hr-qci82 Description The current number of bearer sessions with a duration of 2 minutes and having a QCI of 83. The current number of bearer sessions with a duration of 5 minutes and having a QCI of 80. The current number of bearer sessions with a duration of 5 minutes and having a QCI of 82. The current number of bearer sessions with a duration of 5 minutes and having a QCI of 83. The current number of bearer sessions with a duration of 15 minutes and having a QCI of 80. The current number of bearer sessions with a duration of 15 minutes and having a QCI of 82. The current number of bearer sessions with a duration of 15 minutes and having a QCI of 83. The current number of bearer sessions with a duration of 30 minutes and having a QCI of 80. The current number of bearer sessions with a duration of 30 minutes and having a QCI of 82. The current number of bearer sessions with a duration of 30 minutes and having a QCI of 83. The current number of bearer sessions with a duration of 1 hour and having a QCI of 80. The current number of bearer sessions with a duration of 1 hour and having a QCI of 82. The current number of bearer sessions with a duration of 1 hour and having a QCI of 83. The current number of bearer sessions with a duration of 4 hours and having a QCI of 80. The current number of bearer sessions with a duration of 4 hours and having a QCI of 82. The current number of bearer sessions with a duration of 4 hours and having a QCI of 83. The current number of bearer sessions with a duration of 12 hours and having a QCI of 80. The current number of bearer sessions with a duration of 12 hours and having a QCI of

63 5G NSA for SAEGW System Schema Bulk Statistics sess-bearerdur-12hr-qci83 sess-bearerdur-24hr-qci80 sess-bearerdur-24hr-qci82 sess-bearerdur-24hr-qci83 sess-bearerdur-over24hr-qci80 sess-bearerdur-over24hr-qci82 sess-bearerdur-over24hr-qci83 sess-bearerdur-2day-qci80 sess-bearerdur-2day-qci82 sess-bearerdur-2day-qci83 sess-bearerdur-4day-qci80 sess-bearerdur-4day-qci82 sess-bearerdur-4day-qci83 sess-bearerdur-5day-qci80 sess-bearerdur-5day-qci82 sess-bearerdur-5day-qci83 Description The current number of bearer sessions with a duration of 12 hours and having a QCI of 83. The current number of bearer sessions with a duration of 24 hours and having a QCI of 80. The current number of bearer sessions with a duration of 24 hours and having a QCI of 82. The current number of bearer sessions with a duration of 24 hours and having a QCI of 83. The current number of bearer sessions with a duration of over 24 hours and having a QCI of 80. The current number of bearer sessions with a duration of over 24 hours and having a QCI of 82. The current number of bearer sessions with a duration of over 24 hours and having a QCI of 83. The current number of bearer sessions with a duration of 2 days and having a QCI of 80. The current number of bearer sessions with a duration of 2 days and having a QCI of 82. The current number of bearer sessions with a duration of 2 days and having a QCI of 83. The current number of bearer sessions with a duration of 4 days and having a QCI of 80. The current number of bearer sessions with a duration of 4 days and having a QCI of 82. The current number of bearer sessions with a duration of 4 days and having a QCI of 83. The current number of bearer sessions with a duration of 5 days and having a QCI of 80. The current number of bearer sessions with a duration of 5 days and having a QCI of 82. The current number of bearer sessions with a duration of 5 days and having a QCI of

64 System Schema 5G NSA for SAEGW 62

65 CHAPTER 6 API-based VNFM Upgrade Process Feature Summary and Revision History, on page 63 Feature Changes, on page 64 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Disabled - Configuration required Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide Revision History Revision Details Release Though this feature was introduced in 6.2, it was not fully qualified. It is now fully 6.3 qualified as of this release. First introduced

66 Feature Changes API-based VNFM Upgrade Process Feature Changes Though introduced in 6.2, this feature was not fully qualified in that release. It was made available only for testing purposes. In 6.3, this feature has been fully qualified for use in the appropriate deployment scenarios. Refer to the Ultra Services Platform Deployment Automation Guide for more information. 64

67 CHAPTER 7 API-based AutoDeploy, AutoIT and AutoVNF Upgrade Process Feature Summary and Revision History, on page 65 Feature Changes, on page 66 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Disabled - Configuration required Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide Revision History Revision Details Release Though this feature was introduced in 6.2, it was not fully qualified. It is now fully 6.3 qualified as of this release. First introduced

68 Feature Changes API-based AutoDeploy, AutoIT and AutoVNF Upgrade Process Feature Changes Though introduced in 6.2, this feature was not fully qualified in that release. It was made available only for testing purposes. In 6.3, this feature has been fully qualified for use in the appropriate deployment scenarios. Refer to the Ultra Services Platform Deployment Automation Guide for more information. 66

69 CHAPTER 8 Collecting UAS Logs and VNF Diagnostic Information Feature Summary and Revision History, on page 67 Feature Changes, on page 68 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Disabled - Configuration required Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide Revision History Revision Details Release First introduced

70 Feature Changes Collecting UAS Logs and VNF Diagnostic Information Feature Changes With this release, a new script "collect_all_uas_logs.py" is available to generate and consolidate a comprehensive set of UAS logs and VNF diagnostic information from StarOS device for troubleshooting purposes. The log collection includes logs from all components in a deployed UAS cluster, i.e. from AutoIT, AutoDeploy, AutoVNF, UEM, ESC and StarOS. The VNF diagnostic information can also be collected through the use of vnf-collect-diags RPC command. To collect the diagnostic information from StarOS device, access the NCS CLI after logging in to UEM VM and run the vnf-collect-diags command. Before using the collect_all_uas_logs.py script, you should be aware of the following: AutoVNF IP and SSH credentials (username and password) AutoVNF NETCONF login credentials Login credentials for UEM and ESC Login credentials for AutoIT and AutoDeploy This script is available in the AutoIT, AutoDeploy and AutoVNF VMs in the /opt/cisco/usp/uas/scripts/ directory. A sample yaml file (sample_config.yaml) is present in the same directory along with the script. The yaml file should be updated with proper IP and credential details. Example configuration of sample_config.yaml file: uas-cluster: autovnf: : autovnf: login: user: ubuntu password: Cisco@123 netconf: user: admin password: Cisco@ Important You can exclude AutoDeploy or AutoIT for log collection by commenting out the phrase autodeploy or autoit using # in the yaml file. For example: #autodeploy: For more information on collecting the logs using the script or RPC command, see the Cisco Ultra Services Platform Deployment Automation Guide. 68

71 CHAPTER 9 De-coupling of OS and ConfD Access Feature Summary and Revision History, on page 69 Feature Changes, on page 69 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Enabled - Always-on Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Revision History Revision Details Release First introduced. N6.2 Feature Changes To enhance system security, ConfD CLI access is being de-coupled from that of the Operating System. With this release, you will be prompted to enter the ConfD admin user password whenever logging onto the ConfD CLI. 69

72 Feature Changes De-coupling of OS and ConfD Access For example: confd_cli -u admin C password: 70

73 CHAPTER 10 enb Group Based Relative Capacity Transmission Feature Summary and Revision History, on page 71 Feature Description, on page 72 Configuring enodeb Group Based Relative Capacity Support, on page 72 Monitoring and Troubleshooting, on page 72 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) MME ASR 5500 VPC-DI VPC-SI Default Setting Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference MME Administration Guide Revision History Revision Details Release First introduced

74 Feature Description enb Group Based Relative Capacity Transmission Feature Description MME allows enb group configuration to set relative-mme-capacity value for a particular group of enbs. As part of this feature user can provide relative capacity value along with 'prefix' and 'bits' of enbs to be matched in enb grouping configuration. MME uses given configuration to set relative MME capacity for enb during S1 SET UP procedure for a matching group. Configuring enodeb Group Based Relative Capacity Support relative-mme-capacity This section describes how to configure enodeb Group Based Relative Capacity Support. Use the following configuration to add Relative MME Capacity: configure lte-policy enb-group enb_group_name global-enb-id prefix network_identifier_name bits bits relative-mme-capacity relative_mme_capacity end Important Maximum of 20 enb groups are allowed to configure at any given point of time. global-enb-id prefix network_identifier_name bits bits: Global enb ID prefix contains bit string which should be matched with Hexadecimal value. network_identifier_name Must Hexadecimal number between 0x0 and 0xFFFFFFF. bits Must be an Integer from 1 to 28. relative-mme-capacity relative_mme_capacity: Sends Relative MME capacity in S1 setup response for enb which matches grouping criteria. relative_mme_capacity: Must be an Integer from 1 to 255. Monitoring and Troubleshooting This section provides information regarding show commands available to monitor and troubleshoot the enb Group Based Relative Capacity Support feature. Show Commands and Outputs show lte-policy enb-group name <enb_group_name> The output of this command includes the following fields: 72

75 enb Group Based Relative Capacity Transmission Show Commands and Outputs enb Group Name Global enb ID Prefix Number of Bits Relative MME Capacity 73

76 Show Commands and Outputs enb Group Based Relative Capacity Transmission 74

77 CHAPTER 11 Gx Session Recovery Feature Summary and Revision History, on page 75 Feature Description, on page 76 Configuring Gx Session Recovery, on page 77 Monitoring and Troubleshooting, on page 78 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) All products using Gx interface. ASR 5500 VPC - DI VPC - SI Feature Default Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference. Revision History Important Revision history details are not provided for features introduced before releases 21.2 and N5.1. Revision Details Release With this release, support has been added for Gx session recovery First introduced. Pre

78 Feature Description Gx Session Recovery Feature Description Important This feature is customer-specific, requiring a custom dictionary. For more information, contact your Cisco Account representative. The PCRF is a Diameter server and P-GW/GGSN is the PCEF. Currently, the PCRF and P-GW/GGSN work in synchronization as expected, and when Gx assume-positive is not applied. However, there are scenarios when PCEF and PCRF lose synchronization. Following are some of the scenarios, when: The PCRF is deleted locally. The PCRF has lost the Gx session information. A message is lost. To prevent such scenarios, the Gx session recovery feature is introduced. This feature allows PCRF to recover the lost Gx sessions and allows PCRF and PCEF to synchronize the rule and session information. The following table contains information about the nomenclatures that are modified in support of this feature. Field Auth-Application-Id Msg-Name1 Msg-Name2 Action Event-Trigger1 Event-Trigger2 Experimental-result-code1 Experimental-result-code2 Statistics: New Nomenclature SS-Request Command Code: SS-Answer Command Code: SS-Action AVP-Header: GX_SESSION_RECOVERY (20001) GX_SESSION_SYNC (20002) (4191) DIAMETER_GX_SESSION_SYNC_REQUESTED (4192) DIAMETER_REQUESTED_GX_SESSION_NOT_FOUND Session Sync Request and Answer Statistics: Read SSRs: Read SSR Errors: Write SSAs: Write SSA Errors: Gx Session Not Found: 76

79 Gx Session Recovery Limitations Field Bulkstats: New Nomenclature read-ssr read-ssr-err write-ssa write-ssa-err gx-sess-not-found Limitations Following are the known limitations and restrictions of this feature. Session Sync Request (SSR) is supported only with proxy mode. Session Sync Answer (SSA) messages are not retried. If Diamproxy is restarted while waiting for the response from DemuxMgr, then Session Discovery and Recovery Answer (SDA) is not sent. If DemuxMgr is restarted while processing the Session Discovery and Recovery Request (SDR), then SDA is sent with experimental result code as SESSION_NOT_FOUND so that the messenger request does not bounce. Successful SDA does not imply that session sync is being done using CCR-U. If new rules are installed in the CCA-U along with SSR, then the rule status of those rules is not reported in the CCR-U, which is sent for session sync. If the SessMgr instance is in recovering state or the CLP associated with the requested IMSI/IP-address is in disconnecting state, then the CCR-U is not triggered although SDA indicates success. Configuring Gx Session Recovery Use the following CLI commands to enable session recovery and session synchronization. configure context context_name ims-auth-service service_name policy-control diameter encode-supported-features session-recovery session-sync NOTES: end By default, session recovery and session sync features are not enabled. Use the default diameter encode-supported-features CLI command to set the default value. 77

80 Monitoring and Troubleshooting Gx Session Recovery Monitoring and Troubleshooting This section provides information about monitoring and/or troubleshooting the Gx Session Recovery feature. Show Command(s) and/or Outputs show diameter statistics proxy The output of this show command has been modified to display the following field/counters in support of the Gx Session Recovery feature: Session Sync Request and Answer Statistics: Read SSRs Read SSR Errors Write SSAs Write SSA Errors Gx Session Not Found show ims-authorization policy-control statistics service <service_name> server name <server_name> The output of this show command has been modified to display the following fields/counters in support of the Gx Session Recovery feature: Session Recovery Request CCA rcvd CCR sent Session Sync Request RAR rcvd CCA rcvd CCR sent show ims-authorization policy-control statistics The output of this show command has been modified to display the following fields/counters in support of the Gx Session Recovery feature: Session Recovery Req (The above field is introduced under DPCA Experimental Result Code Stats ) Session Sync Request Stats 78

81 Gx Session Recovery show ims-authorization service name <service_name> RAR CCA show ims-authorization service name <service_name> The output of this show command has been modified to display the following fields in support of the Gx Session Recovery feature: session-recovery session-sync show ims-authorization service statistics The output of this show command has been modified to display the following counters in support of the Gx Session Recovery feature: Session Recovery Session Sync Bulk Statistics The following bulk statistics are added in the Diameter schema in support of the Gx Session Recovery feature. Bulk Statistics read-ssr read-ssr-err write-ssa write-ssa-err gx-sess-not-found Description Indicates the number of SSR read success at Diamproxy endpoint level. Indicates the number of SSR read failure at Diamproxy endpoint level. Indicates the number of SSR write success at Diamproxy endpoint level. Indicates the number of SSR write failure at Diamproxy endpoint level. Indicates the number of requests received to recover the session but the session is not found at Diamproxy endpoint level. 79

82 Bulk Statistics Gx Session Recovery 80

83 CHAPTER 12 Inline TCP Optimization This chapter includes the following topics: Feature Summary and Revision History, on page 81 Feature Description, on page 82 How It Works, on page 82 Configuring Inline TCP Optimization, on page 83 Monitoring and Troubleshooting, on page 87 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) P-GW ASR 5500 VPC - DI VPC - SI Feature Default Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference P-GW Administration Guide Statistics and Counters Reference Revision History Revision Details Release In this release, the throughput gain has been increased. KPIs - separate counters for IP versions (IPv4/IPv6) and application protocols (HTTP/HTTPs), are added. 81

84 Feature Description Inline TCP Optimization Revision Details In this release, two new commands - accl-flags and cwnd-gain, are added to the TCP Acceleration Profile Parameters configuration. Configuring these commands increases throughput gain and optimized mid-flow proxy engagement procedures for TCP accelerated flows. Also, the output for the show tcp-acceleration-profile command has been updated. Inline TCP Optimization engine is enhanced to dynamically engage the TCP acceleration module at mid-flow. First introduced. Release Feature Description Inline TCP Optimization is an integrated solution to service providers to increase the TCP flow throughput for TCP connections. This solution enables faster transmission of data for a better user experience. The Inline TCP Optimization solution ensures accelerated TCP flows using a proprietary algorithm that provides efficient and optimal throughput at a given time. A TCP proxy has been integrated with this solution to monitor and control the TCP congestion window for optimal throughput. The Inline TCP Optimization solution also supports split TCP sessions to accommodate wireless requirements and provides feature parity with other existing inline services. Note Optimization only applies to the downlink data on the Gn interface. The Inline TCP Optimization feature is license controlled. 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. How It Works The TCP Optimization feature includes the following functionalities: TCP Connection Splicing: The TCP connections are split into two connections; one connection towards Gn and the other connection towards Gi, inside P-GW. The connections are split in a transparent manner in the P-GW so that the UE and the Gi servers are transparent to the connection being split. TCP Proxy ensures seamless movement of data across these two TCP split connections. TCP Optimization is deployed on the Gn interface (towards the UE) of the TCP stack. A user-space TCP stack in P-GW is used. Cisco library for TCP optimization: Provides algorithms that are designed to increase the TCP throughput. 82

85 Inline TCP Optimization Accelerating Selected TCP Flows Interfaces with the User-space TCP stack (Gn interface) and notifies appropriate events that occur in the TCP connection and takes actions accordingly. Provides APIs to integrate the Cisco Library (for TCP optimization) and StarOS. Note TCP Acceleration is enabled during the start of the TCP flow (when SYN packet is received). It cannot be disabled later during the flow. Accelerating Selected TCP Flows The Inline TCP Optimization solution is designed to optimize most-eligible TCP flows. The following are a few criteria to select TCP flows for acceleration: Based on the amount of data seen on the flow: Flows that have data more than that of the threshold value are accelerated. TCP acceleration is avoided in certain scenarios for throttled TCP flows. For example: ADC flows that configured to be throttled. TCP flows throttled due to breaching data limit triggered by OCS/PCRF. Tethered flows that are throttled. Based on GBR/non-GBR: Only TCP flows on default bearers is applicable for TCP acceleration. Note TCP acceleration is only supported for LTE RAT-Type. Configuring Inline TCP Optimization Enabling TCP Acceleration under Active Charging Service Use the following configuration to enable TCP acceleration: configure require active-charging active-charging service service_name tcp-acceleration end NOTES: tcp-acceleration: Enables TCP acceleration under the ACS Configuration mode. 83

86 Enabling TCP Acceleration under Trigger Action Inline TCP Optimization Enabling TCP Acceleration under Trigger Action Use the following configuration to enable TCP acceleration: configure require active-charging active-charging service service_name trigger-action trigger_action_name tcp-acceleration profile profile_name end NOTES: tcp-acceleration: Enables TCP acceleration under the ACS Trigger Action Configuration mode. profile: Identifies the TCP acceleration profile. The profile_name is a string ranging from 1 to 63 characters. Configuring a TCP Acceleration Profile Use the following configuration to configure a TCP Acceleration Profile: configure require active-charging active-charging service service_name [ no ] tcp-acceleration-profile profile_name end NOTES: tcp-acceleration-profile: Configures the TCP Acceleration feature profile for inline TCP optimization. no: Disables the TCP Acceleration profile. Configuring TCP Acceleration Profile Parameters Use the following commands to configure the TCP acceleration profile parameters: configure require active-charging active-charging service service_name [ no ] tcp-acceleration-profile profile_name accl-flags flag_value default accl-flags buffer-size { [ downlink [ 128KB 256KB 512KB 1024KB 1536KB 2048KB 2560KB 3072KB 3584KB 4096KB ] [ uplink [ 128KB 256KB 512KB 1024KB 1536KB 2048KB 2560KB 3072KB 3584KB 4096KB ] ] ] [ uplink [ 128KB 256KB 512KB 1024KB 1536KB 2048KB 2560KB 3072KB 3584KB 4096KB ] [ downlink [ 128KB 256KB 512KB 1024KB 1536KB 2048KB 2560KB 3072KB 3584KB 4096KB ] ] ] } cwnd-gain { dynamic { off on } [ factor factor_value ] factor factor_value [ dynamic { off on } ] } default cwnd-gain 84

87 Inline TCP Optimization Configuring Post-Processing Rule Name under Trigger Condition NOTES: default buffer-size [ downlink uplink ] initial-cwnd-size window_size default initial-cwnd-size max-rtt max_rtt_value default max-rtt mss mss_value default mss end default: Assigns or restores default values to its following commands. accl-flags: Configures TCP acceleration related optimization flags. The flag_value is an integer ranging from 0 to buffer-size: Configures the TCP Proxy buffer size for downlink and uplink data in Kilobytes. Note This command is supported from and later releases cwnd-gain: Configures the TCP congestion window gain. This command is used by the TCP optimization engine to continuously calculate the actual congestion window size. Scaling the window size allows the TCP optimization engine to manage the in-flight of data in the engine. The dynamic option in this command automatically scales-up the congestion window gain to ensure that it is sized correctly to allow for RTT variation during the flow. The factor option configures the TCP congestion window gain factor. The factor_value is an integer ranging from 1 to Note This command is supported from and later releases initial-cwnd-size: Configures the initial congestion window size in segments. The window_size is an integer ranging from 1 to max-rtt: Configures the maximum RTT value in milliseconds. The max_rtt_value is an integer ranging from 1 to mss: Configures the maximum segment size for TCP in Bytes. The mss_value is an integer ranging from 496 to Configuring Post-Processing Rule Name under Trigger Condition Use the following commands to configure the post-processing rule names: configure require active-charging active-charging service service_name trigger-condition trigger_condition_name post-processing-rule-name { = contains ends-with starts-with 85

88 Configuring TCP Acceleration Related EDR Attributes Inline TCP Optimization } rule_name [ no ] post-processing-rule-name rule_name end NOTES: post-processing-rule-name: Sets condition for a particular post-processing rule. The following operators specify how the rules are matched: =: Equals!=: Not Equals contains: Contains ends-with: Ends with. starts-with: Starts with name: Specifies the name of the post-processing rule. Configuring TCP Acceleration Related EDR Attributes Use the following configuration to configure the EDR attributes: configure require active-charging active-charging service service_name edr-format edr_format_name rule-variable tcp [ sn-tcp-accl sn-tcp-accl-reject-reason sn-tcp-min-rtt sn-tcp-rtt ] priority priority_value end NOTES: rule variable: Assigns a rule variable attributes for EDR or UDR. tcp: Specifies Transmission Control Protocol (TCP) related fields. sn-tcp-accl: Specifies the TCP Acceleration status for the TCP flow. 0: TCP Acceleration is not enabled on the flow. 1: TCP Acceleration is enabled on the flow. 2: Flow is eligible and attempted, but not TCP Accelerated. 3: Flow is eligible, but not attempted for TCP Acceleration sn-tcp-accl-reject-reason: Specifies reason for not accelerating the TCP flow. sn-tcp-min-rtt: Specifies min RTT observed for accelerated TCP flow. sn-tcp-rtt: Specifies smoothed RTT for accelerated TCP flow. priority: Specifies the CSV position of the field (protocol rule) in the EDR. Priority must be an integer from 1 through

89 Inline TCP Optimization Configuring Flow Length Threshold for a TCP Flow under Trigger Action Configuring Flow Length Threshold for a TCP Flow under Trigger Action The flow length threshold of a TCP flow is configured using Trigger Action under the service-scheme framework. The threshold value of the flow length is used to engage the TCP Acceleration module dynamically. Use the following configuration to engage TCP acceleration module during mid-flow: configure require active-charging active-charging service service_name trigger-action trigger_action_name tcp-acceleration flow-length threshold threshold_value no tcp-acceleration flow-length threshold end NOTES: no: Disables flow recovery for a trigger-action. flow-length: Specifies the flow length action for a TCP flow. threshold: Specifies the threshold value of the flow length in bytes, for a TCP flow. The threshold value is an integer ranging from 1 to bytes. Configuring a Flow Length Threshold Exceeded for a TCP Flow under Trigger Condition The flow length condition exceed for a TCP flow is configured using Trigger Condition under the service-scheme framework. Use the following configuration to configure a condition for a TCP flow length: configure require active-charging active-charging service service_name trigger-condition trigger_condition_name flow-length threshold exceed end NOTES: flow-length: Specifies the flow length condition for a TCP flow. threshold: Specifies the threshold value configured in the trigger-action configuration. exceed: Invokes the exceed condition when the flow length is exceeded. Monitoring and Troubleshooting This section provides information regarding monitoring and troubleshooting the feature. 87

90 Show Command(s) and/or Outputs Inline TCP Optimization Show Command(s) and/or Outputs show configuration This section provides information regarding show commands and/or their outputs in support of this feature. The output of this command displays the following fields for this feature:: tcp-acceleration tcp-accelration profile tap buffer-size downlink size uplink size initial-cwnd-size max-rtt mss show tcp-acceleration-profile { [ all ] [ name profile-name ] } The output of this command displays the following fields for this feature: TCP Acceleration Profile Name Initial Congestion Window Max RTT MSS Buffer Size (Downlink) Buffer Size (Uplink) Cwnd Gain Factor Cwnd Gain Dynamic Accl Flags Total tcp-acceleration-profile found show active-charging tcp-acceleration info The output of this command displays the following fields for this feature: TCP Acceleration Library Information Version show active-charging tcp-acceleration statistics sessmgr all The output of this command displays the following fields for this feature: TCP acceleration Statistics 88

91 Inline TCP Optimization show active-charging tcp-acceleration statistics sessmgr all Total Accelerated Flows Current Accelerated Flows Released Accelerated Flows Rejected Accelerated Flows Feature Not Supported RAT Type Not Supported Bearer Not Supported Resource Not Available (Memory) Others Subscriber Level Statistics Total Accelerated Subscribers Current Accelerated Subscribers Protocol Level Statistics Total Flows (IPv4 and IPv6) TCP HTTP HTTPS Active Flows (IPv4 and IPv6) TCP HTTP HTTPS Current Idle Flows (IPv4 and IPv6) TCP HTTP HTTPS Clearer by Idle Timer (IPv4 and IPv6) TCP HTTP HTTPS 89

92 show active-charging tcp-acceleration statistics sessmgr all Inline TCP Optimization Control Statistics IPv4 (User-Side and Inet-Side) TCP Terminations Rx TCP Terminations Tx IPv6 (User-Side and Inet-Side) TCP Terminations Rx TCP Terminations Tx Data Statistics IPv4 (User-Side and Inet-Side) Total Pkts Rx Total Bytes Rx Total Pkts Tx Total Bytes Tx HTTP (User-Side and Inet-Side) Total Pkts Rx Total Bytes Rx Total Pkts Tx Total Bytes Tx Retrans Pkts Rx Retrans Bytes Rx Retrans Pkts Tx Retrans Bytes Tx HTTPS (User-Side and Inet-Side) Total Pkts Rx Total Bytes Rx Total Pkts Tx Total Bytes Tx Retrans Pkts Rx Retrans Bytes Rx Retrans Pkts Tx Retrans Bytes Tx 90

93 Inline TCP Optimization show active-charging flows full all IPv6 (User-Side and Inet-Side) Total Pkts Rx Total Bytes Rx Total Pkts Tx Total Bytes Tx HTTP (User-Side and Inet-Side) Total Pkts Rx Total Bytes Rx Total Pkts Tx Total Bytes Tx Retrans Pkts Rx Retrans Bytes Rx Retrans Pkts Tx Retrans Bytes Tx HTTPS (User-Side and Inet-Side) Total Pkts Rx Total Bytes Rx Total Pkts Tx Total Bytes Tx Retrans Pkts Rx Retrans Bytes Rx Retrans Pkts Tx Retrans Bytes Tx show active-charging flows full all The output of this command displays the following fields for this feature:: TCP Acceleration show active-charging trigger-action name trigger_action_name On executing the above command, the following new field(s) are displayed for this feature: TCP Acceleration 91

94 show active-charging trigger-condition name name Inline TCP Optimization TCP Acceleration Treshold show active-charging trigger-condition name name The output of this command displays the following fields for this feature: Post-Processing Rule-name/GOR Flow-Length Threshold exceed Bulk Statistics The following bulk statistics are added in the CUSP schema in support of the Inline TCP Optimization (Phase 2) feature. Bulk Statistics tcpaccl-totflows tcpaccl-currflows tcpaccl-usr-ipv4totpkts-rx tcpaccl-usr-ipv4totbytes-rx tcpaccl-usr-ipv4totpkts-tx tcpaccl-usr-ipv4totbytes-tx tcpaccl-inet-ipv4totpkts-rx tcpaccl-inet-ipv4totbytes-rx tcpaccl-inet-ipv4totpkts-tx tcpaccl-inet-ipv4totbytes-tx tcpaccl-usr-ipv6totpkts-rx tcpaccl-usr-ipv6totbytes-rx tcpaccl-usr-ipv6totpkts-tx Description Indicates the total number of TCP accelerated flows. Indicates the number of current TCP accelerated flows. Indicates the total number of IPv4 TCP accelerated packets received from the UE. Indicates the total number of IPv4 TCP accelerated bytes received from the UE. Indicates the total number of IPv4 TCP accelerated packets sent towards the UE. Indicates the total number of IPv4 TCP accelerated bytes sent towards the UE. Indicates the total number of IPv4 TCP accelerated packets received from the internet. Indicates the total number of IPv4 TCP accelerated bytes received from the internet. Indicates the total number of IPv4 TCP accelerated packets sent towards the internet. Indicates the total number of IPv4 TCP accelerated bytes sent towards the internet. Indicates the total number of IPv6 TCP accelerated packets received from the UE. Indicates the total number of IPv6 TCP accelerated bytes received from the UE. Indicates the total number of IPv6 TCP accelerated packets sent towards the UE. 92

95 Inline TCP Optimization Bulk Statistics Bulk Statistics tcpaccl-usr-ipv6totbytes-tx tcpaccl-inet-ipv6totpkts-rx tcpaccl-inet-ipv6totbytes-rx tcpaccl-inet-ipv6totpkts-tx tcpaccl-inet-ipv6totbytes-tx Description Indicates the total number of IPv6 TCP accelerated bytes sent towards the UE. Indicates the total number of IPv6 TCP accelerated packets received from the internet. Indicates the total number of IPv6 TCP accelerated bytes received from the internet. Indicates the total number of IPv6 TCP accelerated packets sent towards the internet. Indicates the total number of IPv6 TCP accelerated bytes sent towards the internet. 93

96 Bulk Statistics Inline TCP Optimization 94

97 CHAPTER 13 IPSec Slow Path Data Plane This chapter describes the following topics: Feature Summary and Revision History, on page 95 Feature Description, on page 95 Configuring IPSec Software Data Path, on page 96 Monitoring and Troubleshooting, on page 96 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area IPSec (ACL Mode) Applicable Platform(s) VPC-SI Feature Default Disabled - Configuration Required Related Changes in This Release Not applicable Related Documentation Command Line Interface Reference IPSec Administration Guide Revision History Revision Details Release First introduced Feature Description Once this feature is enabled which is CLI controlled, IPSec data plane operations are handled in slow path IPSec Manager. For each IKEv1/IKEv2 Crypto Map one IPsec Manager is spawned. Once maximum limit 95

98 Limitations IPSec Slow Path Data Plane is reached, the new Crypto Map starts reusing existing IPSec Manager. The CLI command controlling this feature must be configured during the boot time. Limitations This section describes the known limitations for IPSec Software Data Path feature Transport mode IPsec is not supported. Associating IPSec Software Data Path to Virtual Routing and Forwarding (VRF) is not supported. Configuring IPSec Software Data Path This section provides information on CLI commands available in support of this feature. Configuring IPSec Software Data Path Use the following configuration to enable IPSec Software Data Path for IKEv1/IKEv2 Maps. configure [ no ] require crypto { ikev1-acl software ikev2-acl software } end NOTES: require crypto: Enables Crypto related parameters. ikev1-acl: Configures IKEv1-ACL IPSec sessions. ikev2-acl: Configures IKEv2-ACL IPSec sessions. software: IPSec Manager performs encryption, decryption and DH calculations. no: Disables IPSEC Manager from encryption, decryption and DH calculations. Monitoring and Troubleshooting This section provides information on the show commands available to support IPSec Software Data Path for IKEv1/IKEv2 Maps. Show Commands and Outputs This section provides information on show commands and their corresponding outputs for the IPSec Software Data Path for IKEv1/IKEv2 Maps: show configuration The output of this command includes the following fields: require ikev1-acl software 96

99 IPSec Slow Path Data Plane Show Commands and Outputs require ikev2-acl software 97

100 Show Commands and Outputs IPSec Slow Path Data Plane 98

101 CHAPTER 14 Limit Max Number of IKEv1 IPSEC Managers within a Context Feature Summary and Revision History, on page 99 Feature Changes, on page 99 Command Changes, on page 100 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area IPSec Applicable Platform(s) ASR 5500 Feature Default Disabled Configuration Required Related Changes in This Release Not applicable Related Documentation Command Line Interface Reference IPSec Administration Guide Revision History Revision Details Release First introduced Feature Changes If the maximum number of IKEV1 IPSec managers are already spawned in the system, then a new context with crypto map cannot be added as crypto map in a new context requires a new IPSec manager. A new CLI is introduced to limit the spawning of IKEv1 IPSec managers within a context so that the customer can limit 99

102 Command Changes Limit Max Number of IKEv1 IPSEC Managers within a Context the number of IPSec managers in each existing context and manage the spawning of new IPSec managers in new context if required later. Previous Behavior: Any number of number of IPSec managers can be spawned within a context (depends on how many crypto maps are configured). New Behavior: New CLI limit ipsecmgr ikev1 max enables to limit number of IPSec managers within a context. Customer Impact: Flexibility to manage resources under multiple contexts and avoid the situation where no more crypto maps are available to add in the system when new context is added. Important This feature works only when require crypto ikev1-acl software (Software Datapath feature) is enabled at Global Configuration Mode. Command Changes limit ipsecmgr ikev1 max This section describes the CLI configuration required to enable limiting of IPSec managers spawning within a context. Use the following configuration to limit the parameter for this context. configure context context_name limit ipsecmgr ikev1 maxmax_value default limit ipsecmgr ikev1 max end NOTES: default : Sets/Restores default value assigned for specified parameter. limit : Limits the parameter for this context. ipsecmgr : To limit ipsecmgr manager settings. ikev1 : Specifies IKEv1 tasks. max max_value : Specifies maximum ipsecmgr IKEv1 tasks. max_value must be an integer from 1 to

103 CHAPTER 15 Mapping High Throughput Sessions on Session Managers This chapter includes the following topics: Feature Summary and Revision History, on page 101 Feature Changes, on page 102 Command Changes, on page 103 Performance Indicator Changes, on page 103 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area P-GW S-GW SAEGW Applicable Platform(s) ASR 5500 VPC - DI VPC - SI Default Setting Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference P-GW Administration Guide S-GW Administration Guide SAEGW Administration Guide 101

104 Feature Changes Mapping High Throughput Sessions on Session Managers Revision History Revision Details Session managers are upgraded to manage several high throughput sessions without sharing the core and without creating a bottleneck on the CPU load. First introduced. Release 21.9 Pre 21.2 Feature Changes Session managers are upgraded to manage several high throughput sessions without sharing the core and without creating a bottleneck on the CPU load. The gateway S-GW, SAEGW or P-GW, classifies a session as a high throughput session based on a DCNR flag present in the IE: FLAGS FOR USER PLANE FUNCTION (UPF) SELECTION INDICATION, in the Create Session Request. This DCNR flag is check-pointed and recovered by the gateway. A high throughput session is placed on a session manager that has no other high throughput session. If all session manager are handling a high throughput session then these sessions are allocated using the Round-Robin method. Note The selection of session managers for non-high throughput sessions remains the same in the existing setup. Non-high throughput sessions are placed along with the high throughput sessions on the same session manager. Limitations Managing high throughput sessions on a session manager has the following limitations: The following scenarios may result in placing two high throughput sessions on a session manager: Initial attach from ehrpd/2g/3g sessions. IP addresses both IPv4 and IPv6, are placed on the same session manager. For an S-GW, the second Create Session Request (PDN) from a UE lands directly on a session manager which has the first PDN of the same UE. For a collapsed call, the second Create Session Request (PDN) from a UE lands directly on a session manager which has the first PDN of the same UE. In a Multi-PDN call from a UE that is capable of DCNR. For example: VoLTE and Internet capable of DCN will be placed on the same session manager. The DCNR flag is not defined by 3GPP for Wi-Fi. Therefore, a session cannot be assigned to a session manager during a Wi-Fi to LTE handover with the DCNR flag set. 102

105 Mapping High Throughput Sessions on Session Managers Command Changes This feature manages and supports distribution of high throughput sessions on a session manager but does not guarantee high throughput for a subscriber. In some cases, the round robin mechanism could place a high throughput session on a session manager that was already loaded with other high throughput sessions. Command Changes The session manager selection for a high throughput session is CLI controlled. A set of new CLI under the gtpc command, in the Context Configuration Mode must be enabled to place high throughput sessions evenly on the session managers. The configuration for selecting a session manager for a high throughput session is license controlled. Use the following configuration to enable session manager selection for high throughput sessions: configure context context_name [ no ] gtpc high-throughput-sub dcnr-based sessmgr-select round-robin NOTES: end By default, the session manager selection for a high throughput session is disabled. high-throughput-subscribers: Enables the GTPC configuration for high throughput subscribers. dcnr-based: Applies this configuration to all Create Session Requests that have a DCNR flag. sessmgr-select: Specifies the method to select a session manager for a DCNR session. round-robin: Selects the session managers for a high throughput session using the round-robin method. Performance Indicator Changes This section provides information regarding show commands and/or their outputs in support of this feature. show demux-mgr sessions egtpinmgr all The output of this command displays the following field in support of this feature: DCNR Session show demux-mgr statistics egtpinmgr instance instance_number The output of this command displays the following field in support of this feature: #DCNR 103

106 show demux-mgr statistics egtpinmgr instance instance_number Mapping High Throughput Sessions on Session Managers 104

107 CHAPTER 16 Maximum Segment Size for Outgoing TCP Packets Feature Summary and Revision History, on page 105 Feature Changes, on page 106 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) All products using LI. ASR 5500 VPC - DI VPC - SI Default Setting Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Lawful Intercept Configuration Guide Revision History Revision Details Release In and later releases, the Maximum Segment Size (MSS) value for outgoing TCP packets is configurable This change in behavior is also integrated with release First introduced. Pre

108 Feature Changes Maximum Segment Size for Outgoing TCP Packets Feature Changes In and later releases, a new CLI keyword is added to configure the MSS value at Lawful Intercept which determines the packet size on a TCP connection. Important For additional information, contact your Cisco Account representative. 106

109 CHAPTER 17 MME Manager Scaling for USP and VPC-DI Feature Summary and Revision History, on page 107 Feature Changes, on page 108 Command Changes, on page 108 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) MME USP VPC-DI Feature Default Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference MME Administration Guide Revision History Important Revision history details are not provided for features introduced before releases 21.2 and N5.1. Revision Details Release For VPC-DI and USP platforms, the maximum number of MME managers configured 21.9 per session card is modified in this release. First introduced. Pre

110 Feature Changes MME Manager Scaling for USP and VPC-DI Feature Changes For USP and VPC-DI platforms, the maximum number of MME managers supported per Session Function (SF) card is modified in this release. The maximum number of MME managers supported per chassis is unchanged in this release. Previous Behavior: The maximum number of MME managers supported per SF was 2 for USP and VPC-DI platforms. New Behavior: The maximum number of MME managers supported per SF is 4 for USP and VPC-DI platforms. The task facility mmemgr per-sesscard-count CLI command is extended to support up to 4 instances of MME managers on USP and VPC-DI platforms. The maximum number of MME managers supported per chassis is 48 for USP and VPC-DI platforms. The task facility mmemgr max CLI command supports up to 48 instances of MME managers for USP and VPC-DI platforms. Command Changes task facility mmemgr max In this release, a maximum number of 48 MME managers per chassis can be configured for USP and VPC-DI platforms. Use the following configuration to configure the desired number of MME managers per chassis. configure task facility mmemgr max value default task facility mmemgr max end NOTES: default: This keyword resets the number of MME managers per chassis to the default values. max value: This keyword is used to configure the maximum number of MME managers per chassis. value must be an integer from 1 to 64. It is recommended to configure a maximum of 48 MME managers per chassis. The maximum number of MME managers that can be configured per chassis varies based on the platform. The task facility mmemgr max CLI command is not enabled by default. The configuration change will be effective only after a chassis reload. The operator must save the configuration changes prior to a reload. The system issues appropriate warnings to the operator to indicate that configuration changes must be saved and the changes will be effective only after a chassis reload. 108

111 MME Manager Scaling for USP and VPC-DI task facility mmemgr per-sesscard-count task facility mmemgr per-sesscard-count In this release, a maximum number of 4 MME managers are supported per SF card in USP and VPC-DI platforms. Use the following configuration to configure the required number of MME managers per session card. configure task facility mmemgr per-sesscard-count count default task facility mmemgr per-sesscard-count end NOTES: default: This keyword resets the number of MME managers per session card to the default number of MME managers per session card/vm. When this CLI is not configured, the default number of MME managers per session card will be selected based on platform and card type. per-sesscard-count count: This keyword is used to configure the required number of MME managers to be started on each session card. count must be an integer from 1 to 8. It is recommended to configure a maximum number of 4 MME managers per SF card. This CLI is not enabled by default. 109

112 task facility mmemgr per-sesscard-count MME Manager Scaling for USP and VPC-DI 110

113 CHAPTER 18 Multi-VNF and Multi-tenant Support for UEM Feature Summary and Revision History, on page 111 Feature Changes, on page 112 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Disabled - Configuration required Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide Revision History Revision Details Release First introduced

114 Feature Changes Multi-VNF and Multi-tenant Support for UEM Feature Changes Important The support for multi-tenant feature is not fully qualified in this release. It is available only for testing purposes. For more information, contact your Cisco Accounts representative. With this release, a single cluster of UEM supports multiple VNF instances which are deployed either on the same tenant or different tenants in a single VIM. It involves Day-0 and Day-N configuration changes to support the multi-vnf instances for UEM. In order to support the multi-tenant feature, changes were made to the UAS and UEM YANG model. The support for multi-tenants and multi-vnfs is applicable in all deployment scenarios Ultra M, Standalone AutoVNF and UEM-based deployment scenarios. 112

115 CHAPTER 19 Network Service Headers (NSH) This chapter describes the following topics: Feature Summary and Revision History, on page 113 Feature Description, on page 114 How It Works, on page 114 Configuring Support for NSH Framework, on page 116 Show Commands and Outputs, on page 123 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area P-GW SAEGW Applicable Platform(s) ASR 5500 VPC-DI VPC-SI Feature Default Enabled - Always-on Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference P-GW Administration Guide SAEGW Administration Guide 113

116 Feature Description Network Service Headers (NSH) Revision History Revision Details In this release, NSH-based Traffic Identification with Traffic Steering is supported. First introduced. Release Feature Description Network Services Headers (NSH), a new service chaining protocol, is added to the network traffic in a packet header to create a dedicated service plane that is independent of the underlying transport protocol. In general, NSH describes a sequence of service nodes that a packet is routed through before reaching the destination address. The NSH includes meta-data information about the packet and service chain in an IP packet. The NSH protocol addresses the growing requirement to deploy various services functions external to the gateway. This feature introduces NSH protocol support for P-GW and SAEGW products and supports the following: Encoding and decoding of NSH format in the P-GW/SAEGW. Configurable parameters to be included for encoding in the variable header. NSH treatment for selective traffic based on configuration. Configuring the tag values for parameters present in the variable header. Selective configuration of policies for acting on the decode parameters received in the NSH. Configuring the intelligence of encoding the NSH information in every packet of a flow or only once per flow. NSH-based Traffic Identification with Traffic Steering. Important In this release, selective encryption of parameters is not supported. How It Works This section describes the working of NSH protocol support in Cisco's P-GW/SAEGW products. The Uplink Packet For the uplink packet, P-GW/SAEGW adds the NSH, if the flow matches the specified criteria. NSH has a variable length context header also. Following call flow shows the NSH protocol support in the Cisco PGW/SAEGW products for an uplink packet. 114

117 Network Service Headers (NSH) How It Works For an uplink packet, if the call flow matches the specified criteria, PGW or SAEGW adds the NSH header to the data packet. NSH header may have variable length context header, which can be encrypted if specified in the configuration. The Downlink Packet For the downlink packet, P-GW/SAEGW processes and removes the NSH and applies policies based on the extracted NSH parameters. Following call flow shows the NSH protocol support in the Cisco PGW/SAEGW products for a downlink packet. For a downlink packet, PGW or SAEGW processes and removes NSH header. Then, PGW or SAEGW apply policies based on the extracted NSH parameters. Source and destination IP address for the outer IP packet is taken from the inner IP packet. By default, NSH encapsulated packets use the port number

118 Configuring Support for NSH Framework Network Service Headers (NSH) Configuring Support for NSH Framework This section covers configuration steps used in this feature for adding support for NSH framework. Charging Action Association Service chain is associated to charging action in the following way: configure active-charging service service_name charging-action charging_action_name service-chain service_chain_name end Notes: charging-action: Defines charging action. charging_action_name: Specifies name of the charging action. This is entered as an alphanumeric string of 1 through 64 characters. service-chain: Defines service chain association. service_chain_name: Specifies name of the service chain. This is entered as an alphanumeric string of 1 through 64 characters. Service Chain Association A new CLI command nsh-format is added to the service-chain command for service-chain association. 116

119 Network Service Headers (NSH) Service Scheme Association configure service-chain <service_chain_name> nsh-format <nsh_format_name> end Notes: service-chain: Defines service chain association. service_chain_name: Specifies name of the service chain. This is entered as an alphanumeric string of 1 through 64 characters. nsh-format: Associates NSH format with the service chain. Service Scheme Association A new CLI command nsh-response-received has been added to the trigger command to the ACS service scheme configuration mode. configure active-charging service service_name service-scheme service_scheme_name [ no ] trigger { bearer-creation flow-create loc-update nsh-response-received sess-setup } end Notes: service-scheme: Enables the association of service-scheme based on subscriber class. service_scheme_name: Specifies name of the service scheme. This is entered as an alphanumeric string of 1 through 64 characters. no: Disables the trigger action for the service-scheme. trigger: Specifies the trigger action for service-scheme. bearer-creation: Triggers for every new bearer. flow-create: Triggers for every new flow. loc-update: Triggers whenever location changes of the subscriber. nsh-response-received: Triggers on NSH response packet. sess-setup: Triggers at session setup. NSH Configuration Mode The Network Service Header (NSH) configuration mode is a sub-mode of the Global Configuration mode. This NSH mode is used to encode or decode NSH. Exec > Global Configuration> Network Service Entity - IP Configuration 117

120 NSH Fields Configuration Mode Network Service Headers (NSH) configure nsh end Entering the above command sequence results in the following prompt: [local]host_name(nsh)# NSH Fields Configuration Mode The NSH Fields configuration mode is a sub-mode of the NSH Configuration mode. This NSH Fields configuration mode is used to tag value to the NSH fields. Exec > Global Configuration> Network Service Header > Network Service Header - Fields Configuration configure nsh nsh-fieldsfields_name end Entering the above command sequence results in the following prompt: [local]host_name(nsh-nshfields)# tag-value This new CLI command is added to the NSH Fields configuration mode to associate a tag value to a NSH field. configure nsh nsh-fields fields_name tag-value tag_value { content-type enterprise-id imei imsi msisdn rating-group rulebase tdf-app-id } end Notes: nsh-fields: Defines nsh fields tag values. fields_name: Specifies name of the nsh-field. This is entered as an alphanumeric string of 1 through 64 characters. tag-value Associates a tag to a field. tag_value : Tag value for the NSH field. content-type: Specifies content type of payload. enterprise-id: Specifies the enterprise-id to be sent in NSH context header. imei: Specifies imei of the subscriber. imsi: Sepcifies imsi of the subscriber. imisdn: Specifies imisdn of the subscriber. 118

121 Network Service Headers (NSH) NSH Format Configuration Mode rating-group: Specifies rating-group applied for the traffic. rulebase: Specifies rule-base of the subscribers. tdf-app-id: Specifies tdf application id applied to the traffic NSH Format Configuration Mode The NSH Format Configuration mode is a sub-mode of the NSH Configuration mode. This NSH Format mode is used to encode or decode NSH. Exec > Global Configuration> Network Service Header > Network Service Header - Format configure nsh nsh-formatformat_name end Entering the above command sequence results in the following prompt: [local]host_name(nsh-nshformat)# encode This new CLI command is added to the NSH Format configuration mode. This command defines the NSH encoding fields to be associated with the NSH format. configure nsh nsh-format format_name encode nsh-fields fields_name end Notes: nsh-format: Defines format in NSH header. format_name: Specifies name of the NSH format. This is entered as an alphanumeric string of 1 through 64 characters. encode: Associates nsh-fields for encoding. nsh-fields: Defines nsh fields tag value. fields_name: Specifies name of the fields. This is entered as an alphanumeric string of 1 through 64 characters. encoding-frequency This command defines frequency of encoding the NSH fields to be associated with the NSH format. configure nsh nsh-format format_name 119

122 decode Network Service Headers (NSH) Notes: encoding-frequency { always once-per-flow } end encoding-frequency: Defines frequency of encoding nsh-fields. always: Encodes nsh fields on every hit. once-per-flow: Encodes nsh fields once per flow. decode This command defines the NSH decoding fields to be associated with the NSH format. configure nsh nsh-format format_name decode nsh-fields fields_name end Notes: nsh-format: Defines format in NSH header. format_name: Specifies name of the NSH format. This is entered as an alphanumeric string of 1 through 64 characters. decode: Associates nsh-fields for decoding. nsh-fields: Defines nsh fields tag value. fields_name: Specifies name of the fields. This is entered as an alphanumeric string of 1 through 64 characters. Trigger Condition Configuration Mode Commands content-type This command specifies the content type to be matched. configure active-charging service service_name trigger-condition trigger_condition_name content-type { operator condition } end Notes: trigger-condition: Defines ACS trigger conditions. trigger_condition_name: Specifies name of the trigger condition. This is entered as an alphanumeric string of 1 through 64 characters. content-type: Specifies the content type. 120

123 Network Service Headers (NSH) tdf-app-id operator : Specifies how to match. Operator must be one of the following:!=: not equals!contains: not contains!ends-with: not ends with!starts-with: not starts with =: equals contains: contains ends-with: ends with starts-with: starts with condition: Specifies the condition to match. Condition must be one of the following: FALSE TRUE tdf-app-id This command specifies the identifier for application-based rules to be matched. configure active-charging service service_name trigger-condition trigger_condition_name tdf-app-id { operator condition } end Notes: trigger-condition: Defines ACS trigger conditions. trigger_condition_name: Specifies name of the trigger condition. This is entered as an alphanumeric string of 1 through 64 characters. tdf-app-id: Specifies the identifier for application based rules. operator condition: Specifies how to match. Operator must be one of the following:!=: not equals!contains: not contains!ends-with: not ends with!starts-with: not starts with =: equals contains: contains ends-with: ends with 121

124 Sample Configuration for NSH Creation Network Service Headers (NSH) starts-with: starts with condition: Specifies the condition to match. Condition must be one of the following: FALSE TRUE Sample Configuration for NSH Creation The following is a sample configuration for this NSH service creation: config nsh nsh-fields xyz tag-val 1 imei tag-val 2 imsi exit nsh-fields abc tag-val 4 content-type exit nsh-format format1 encoding frequency always encode nsh-fields xyz decode nsh-fields abc exit exit traffic-steering appliance-group firewall nsh-format format1 ip address #exit #exit service-chain sch1 sfp direction uplink service-index 1 appliance firewall #exit exit config active-charging service ACS trigger-action ta1 throttle-suppress exit trigger-condition tc1 content-type contains text exit service-scheme scheme1 trigger nsh-response-received priority 1 trigger-condition tc1 trigger-action ta1 exit exit subs-class class1 any-match = TRUE exit subscriber-base base1 priority 1 subs-class class1 bind service-scheme scheme1 exit charging-action ca1 service-chain xyz exit 122

125 Network Service Headers (NSH) Show Commands and Outputs exit exit Show Commands and Outputs show nsh statistics This section provides information regarding show commands and their outputs in support of the feature. This command has been newly added in this release to display the nsh statistics. Following is the output when you execute this command: Total Encap Successful : 0 Total Decap Successful : 0 Total Encap Failed : 0 Memory Allocation : 0 Config Error : 0 Encryption Failed : 0 Total Decap Failed : 0 Config Error : 0 Base Header Invalid Length : 0 Unsupported Version : 0 Unsupported Next Protocol : 0 Next Protocol Mismatch : 0 Unsupported MD-Type : 0 Context Header Unsupported MD-Class : 0 Unsupported Type : 0 OAM Packets Received : 0 Dropped : 0 Unknown Context Header Type : 0 show active-charging trigger-condition statistics The output of this command includes the following field for this feature: NSH-Rsp-Rcvd This field displays the matching of trigger condition based on NSH response. 123

126 show active-charging trigger-condition statistics Network Service Headers (NSH) 124

127 CHAPTER 20 NTP Client Support for UEM Feature Summary and Revision History, on page 125 Feature Changes, on page 126 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Enabled - Always-on (applicable only in UEM-based deployment model) Related Features in this Release Not Applicable Related Documentation Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide UEM-based VNF Deployment Guide (For more information on this document, contact Cisco Account representative.) Revision History Revision Details Release First introduced

128 Feature Changes NTP Client Support for UEM Feature Changes With this release, UEM is leveraged to use the NTP server address details provided through NTP configuration (ntp.cfg) file, at the time of deployment, to configure the NTP client on UEM. Important In this release, the NTP client support is applicable only for UEM-based deployment model. The NTP server can be changed during the run-time using the NTP configuration file and the corresponding service should be restarted manually. 126

129 CHAPTER 21 P-GW Custom Diameter Dictionary Changes for Gx Interface Feature Summary and Revision History, on page 127 Feature Changes, on page 128 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area P-GW Applicable Platform(s) ASR 5500 Feature Default Enabled - Always-on (for customer-specific Diameter dictionary for Gx interface) Related Changes in This Release Presence Reporting Area, on page 129 Related Documentation Not Applicable Revision History Important Revision history details are not provided for features introduced before releases 21.2 and N5.1. Revision Details Release With this release, the P-GW custom Diameter dictionary has been enhanced to include Extended-Bit-Rate (for default and dedicated bearers), and Multiple Presence Reporting Area (Multiple-PRA). First introduced. Pre

130 Feature Changes P-GW Custom Diameter Dictionary Changes for Gx Interface Feature Changes Previous Behavior: In releases earlier than , the customer-specific Diameter dictionary for Gx interface did not support the following: Extended-Bit-Rate (for default and dedicated bearers). Multiple Presence Reporting Area (Multiple-PRA) [New feature support]. New Behavior: In and later releases, the above functionalities are supported in customer-specific Diameter dictionary for Gx interface. Customer Impact: Customer-specific Diameter dictionary for Gx interface. 128

131 CHAPTER 22 Presence Reporting Area This chapter describes the following topics: Feature Summary and Revision History, on page 129 Feature Description, on page 130 How It Works, on page 130 Multiple Presence Reporting Area, on page 133 Configuring Presence Reporting Area, on page 134 Monitoring and Troubleshooting, on page 135 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area P-GW SAEGW S-GW Applicable Platform(s) ASR 5500 Feature Default Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference P-GW Administration Guide SAEGW Administration Guide S-GW Administration Guide Statistics and Counters Reference 129

132 Feature Description Presence Reporting Area Revision History Revision Details In this release Multiple Presence Reporting Area feature is supported. First introduced. Release Feature Description The Presence Reporting Area is an area defined within the 3GPP packet domain for reporting of UE presence within that area. This feature is required for policy control and in charging scenarios. In E-UTRAN, the PRA may consist in a set of neighbor or non-neighbor Tracking Areas, or enbs or cells. There are two types of Presence Reporting Areas: "UE-dedicated Presence Reporting Areas" and "Core Network pre-configured Presence Reporting Areas" that apply to an MME pool. This feature supports LTE/S4-SGSN related RAT-type. For any other RAT type, P-GW ignores the PRA information received from the PCRF. Currently single PRA-ID is supported per session as specification compliance. Currently, in P-GW, core network pre-configured presence reporting area is supported. For ICSR to N-1 release, PRA feature is not supported. PRA-ID is not supported on CDR interface, that is, Gz, Gy and Rf. How It Works During an IP-CAN session, the PCRF determines whether the reports for change of the UE presence in the PRA are required for an IP-CAN session. This determination is made based on the subscriber's profile configuration and the supported AVP features. The parameter CNO-ULI is set for the same. If reporting is required for the IP-CAN session, the PCRF provides Presence-Reporting-Area-Information AVP, which contains the PRA identifier within the Presence-Reporting-Area-Identifier AVP, to the PCEF. For a UE-dedicated PRA, PCRF provides the list of elements consisting of the PRA within the Presence-Reporting-Area-Elements-List AVP to the PCEF. The PCRF might activate the reporting changes of the UE presence in the PRA by subscribing to the CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA_REPORT event trigger at the PCEF at any time during the entire IP-CAN session. When the UE enters or leaves the PRA, PCEF reports the CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA_REPORT event. Within the PCEF also reports the PRA status within the Presence-Reporting-Area-Status AVP and PRA identifier within Presence-Reporting-Area-Identifier AVP included in Presence-Area-Information AVP. The following table describes the scenario and its associated behavior: 130

133 Presence Reporting Area How It Works Scenario When PCRF sends a new PRA ID different than the initial call setup Behavior P-GW receives the new PRA ID during the initial call setup and stores the PRA ID information. When PCRF sends a new PRA ID which is same as the initial call setup In RAR, the PRA_EVENT_TRIGGER is registered. P-GW sends PRA_ACTION PRA ID="A", ACTION=start. In CCA-U, a new PRA ID is received. P-GW stores new PRA ID information. P-GW sends PRA_ACTION PRA ID = "B", Action=start but does not send Action=stop for the earlier PRA. Important Ideally, in the above condition, PCRF disables the event triggers first and sends a new PRA-ID=B and enables the event trigger in subsequent message. PRA ID does not send any PRA Action towards S-GW, and P-GW ignores this. PRA ID Decode Behavior If PRA ID values from PCRF are 1 octet, 2 octets, and 3 octets Roaming Scenario If PRA ID received is "core network pre-configured presence reporting area", then, P-GW ignores the "Element List" coming from PCRF. Otherwise, if PRA ID is "UE-dedicated Presence Reporting Area", then, P-GW parses the "Element List" and forwards it toward the access side. MSB of the value received from the PCRF is evaluated to find the PRA type. While encoding, GTPC side zeros are prepended to make it 3 octets. For example, if PRA ID = FC ( ) is received from PCRF, it is considered as UE-dedicated PRA and while decoding it is decoded as FC. P-GW forwards PRA information toward the roaming subscriber if it is received from the PCRF or UE. Important Change of UE presence in the Presence Reporting Area reporting does not apply to the roaming scenario. Change of UE presence in the Presence Reporting Area reporting does not apply to the roaming scenario. When the serving EPC node (MME, S4-SGSN) is changed, the Presence Reporting Area identifier is transferred for all PDN connections as part of the MM Context information to the target serving node during the mobility procedure. The list of Presence Reporting Area elements are also transferred if they are provided by the P-GW. 131

134 How It Works Presence Reporting Area Scenario Handover Behavior: How the PRA identifier is communicated from source MME/S4-SGSN to target MME/S4-SGSN Behavior MME/S4-SGSN gets the PRA Identifier from source MME/S4-SGSN as part of MM Context information. When the serving EPC node (MME, S4-SGSN) is changed, the Presence Reporting Area identifier is transferred for all PDN connections as part of the MM Context information to the target serving node during the mobility procedure. The list of Presence Reporting Area elements are also transferred if they are provided by the P-GW. Handoff Behavior: How PRA is disabled when the new access type is not supported PRA Depending on the access type and internal configuration PCRF deactivates the PRA, if the new access PRA is not supported. During an IP-CAN session, P-GW notifies the PCRF that the UE is located in an access type, where local PCRF configuration is such that the reporting changes of the UE presence in the PRA are not supported. The PCRF unsubscribes to the change of UE presence in the PRA, if previously activated. Behavior if for E-UTRAN some nodes do not support PRA If PRA is enabled from PCRF, then EPC nodes supports it. If all nodes are not supported, then PRA PCRF activates Location Change Reporting. Important For E-UTRAN access, homogeneous support of reporting changes of UE presence in a network is assumed. When the PCRF configuration indicates that reporting changes of the UE presence in a PRA is supported for E-UTRAN, this means all P-GWs, MMEs, and S-GWs support it, including the MME and S-GW working in the network sharing mode. If the change of UE presence in the PRA reporting is not supported, the PCRF may instead activate location change reporting at the cell or serving area level. When access side procedure failure or collision occurs (Create or Update Bearer procedure) In Update or Create bearer procedure failure where the PRA action was sent in the request message and if PRA information was not received in response message, P-GW attempts to send the PRA action in next control procedure toward the remote peer. In Update or Create bearer procedure failure where PRA action was sent in the request message and if PRA information was not received in the response message, P-GW assumes it as PRA action was successfully communicated toward the remote peer. In the Update or Create bearer collision scenario where PRA action was sent in the request message and Update or Create procedure got aborted, P-GW attempts to send the PRA action in next control procedure toward the remote peer. 132

135 Presence Reporting Area Multiple Presence Reporting Area Multiple Presence Reporting Area Important This feature is introduced in release P-GW supports negotiation of Multiple-Presence Reporting Area feature in Feature-List-ID 2 over Gx interface with PCRF. The CNO-ULI feature will be used only when the P-GW and/or the PCRF does not support Multiple-PRA and both P-GW and PCRF support CNO-ULI. When the Multiple-PRA feature is supported during the lifetime of the IP-CAN session P-GW handles the change of UE Presence in Reporting Area(s) request from PCRF in PRA-Install AVP including the Presence-Reporting-Area-Information AVP(s) which each contains the Presence Reporting Area Identifier within the Presence-Reporting-Area-Identifier AVP. P-GW Handling the Event Trigger CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA_REPORT from PCRF for the activation of the reporting changes of UE presence in Presence Reporting Area(s). P-GW handles the PRA Identifier(s) modify request from PCRF with the new PRA within the PRA-Install AVP as described above and/or by removing the existing PRA(s) within the PRA-Remove AVP. In this case, the Presence-Reporting-Area-Identifier AVP of the removed PRA must be included within the Presence-Reporting-Area-Information AVP(s). P-GW supports PRA-Install and PRA-Remove AVPs from PCRF in the following messages: CC-Answer (CCA) Command Re-Auth-Request (RAR) Command The P-GW handles the request from PCRF to unsubscribe to the change of UE presence in Presence Reporting Area wherein PCRF provides the Event-Trigger AVP with the value CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA_REPORT (48) removed, if previously activated. P-GW supports the maximum of 4 PRA(s) for a IP-CAN session at any given point of time. The maximum number of PRAs is configurable in PCRF and must be capped to 4. P-GW will ignore the Presence Reporting Area Identifiers entries beyond 4. When the P-GW receives the presence reporting area information from the serving node over S5/S8 interface indicating that the UE is inside or outside of one or more presence reporting areas or any of the presence reporting areas is set to inactive, the P-GW will check if the reported presence reported area identifier corresponds to a presence reporting area that is relevant for the PCRF. In that case, the P-GW reports the CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA_REPORT event in the Event-Trigger AVP additionally, the P-GW also reports the presence reporting area status within the Presence-Reporting-Area-Status AVP and presence reporting area identifier within Presence-Reporting-Area-Identifier AVP included in Presence-Reporting-Area-Information AVP(s) for each of the presence reporting areas reported by the serving node. The P-GW de-activates the relevant IP-CAN specific procedure for reporting change of UE presence in Presence Reporting Area, when the PCRF and OCS unsubscribe to change of UE presence in Presence Reporting Area. PRA-Install AVP (3GPP-EPS access type) Definition 133

136 Configuring Presence Reporting Area Presence Reporting Area The PRA-Install AVP (AVP code 2845) is of type Grouped, and it is used to provision a list of new or updated Presence Reporting Area(s) for an IP-CAN session. AVP Format: PRA-Install ::= < AVP Header: 2845 > *[ Presence-Reporting-Area-Information ] *[ AVP ] PRA-Remove AVP (3GPP-EPS access type) Definition The PRA-Remove AVP (AVP code 2846) is of type Grouped, and it is used to stop the reporting of a list of Presence Reporting Area(s) for an IP-CAN session. AVP Format: PRA-Remove ::= < AVP Header: 2846 > *[ Presence-Reporting-Area-Identifier ] *[ AVP ] Configuring Presence Reporting Area Configuring PRA Use the following configuration to enable the PRA: configure context context_name ims-auth-service service_name policy-control diameter encode-supported-features cno-uli { default no } diameter encode-supported-features end NOTES: diameter encode-supported-features: Enables or disables encoding and sending of Supported-Features AVP. cno-uli: Enables Presence Reporting Area Information Reporting feature. no: Removes the previously configured supported features. default: Applies the default setting for this command. Configuring Multiple-PRA Use the following configuration to enable Multiple Presence Reporting Area (Multiple-PRA) Feature. configure context context_name ims-auth-service service_name policy-control diameter encode-supported-features multiple-pra 134

137 Presence Reporting Area Monitoring and Troubleshooting NOTES: { default no } diameter encode-supported-features end ims-auth-service service_name: Creates an IMS authentication service. service_name must be an alphanumeric string of 1 through 63 characters. policy-control: Configures Diameter authorization and policy control parameter for IMS authorization. diameter encode-supported-features: Enables encoding and sending of Supported-Features AVP. multiple-pra: Enables the Multiple Presence Reporting Area Information Reporting feature. no: Removes the previously configured supported features. default: Applies the default setting for this command. Monitoring and Troubleshooting The following sections describe the commands available to monitor the feature. Show Commands and Outputs This section provides information regarding show commands and their outputs in support of this feature. show ims-authorization service name <service-name> The output of the above command is modified to display the negotiated conditional policy features related information. The modified output is as follows: Context: ha IMS Authorization Service name: imsa-gx Diameter Policy Control: Endpoint: gx.st16.starentnetworks.com Origin-Realm: starentnetworks.com Dictionary: r8-gx-standard Supported Features: mission-critical-qcis conditional-policy-info-default-qos cno-uli Request Timeout: Initial Request : 100 deciseconds Update Request : 100 deciseconds Terminate Request : 100 deciseconds Endpoint Peer Select: Not Enabled Reauth Trigger: All Custom Reauth Trigger: QoS-Change show ims-authorization service name The output of this command includes the "multiple-pra" field to indicate if the Multiple Presence Reporting Area feature is enabled or disabled. 135

138 show ims-authorization sessions full all Presence Reporting Area show ims-authorization sessions full all The output of this command includes the following fields: CallId: 00004e26 Service Name: imsa-gx IMSI: Session ID: gx.st16.starentnetworks.com;20006;2305;598ab8cf-102 Bearer Type: GTP SGSN IP-Addr: APN: starent.com Bearer Control Mode: UE/NW State: Connected Negotiated Supported Features: 3gpp-r8 conditional-policy-info-default-qos cno-uli Auth Decision: Event Triggers: QoS-Change RAT-Change Change-Of-UE-Presence-In-PRA Usage-Report Resource-Modification-Request multiple-pra show ims-authorization service statistics The output of the above command is modified to display the PRA feature statistics. The modified output is as follows: IMS Auth Service Statistics Summary: Total Services: 2 Auth Session: Current Active: 1 Current Fallback Session: 0 Current PCRF Session: 1 Total Attempted: 1 Total Setup: 1 Total Failed: 0 Total Released: 0 Total Fallback: 0 Re-Authorization Triggers: SGSN Change: 0 PLMN Change: 0 RAT Change: 0 TFT Change: 0 Bearer Recovery: 0 Bearer Loss: 0 QoS Change: 0 Policy Failure: 0 IP-CAN Change: 0 Resources Limitation: 0 Max Num of Bearers Rchd: 0 QoS Chng Exceeding Auth: 0 RAI Change: 0 User Location Change: 0 TAI Change: 0 ECGI Change: 0 PCRF Triggered ReAuth: 0 Preservation Changed: 0 Reactivation Changed: 0 Revalidation Timeout: 0 AN GW Changed: 0 Out Of Credit Reauth: 0 Reallocation Of Credit: 0 Def EPS Bearer QoS Chng: 0 Successful Resource Alloc: 0 Usage Report: 0 Service Flow Detection: 0 UE Timezone Change: 0 UE IP Address Allocate: 0 UE IP Address Release: 0 Resource Modification Req: 0 APN AMBR Mod Failure: 0 Def Bearer QOS Mod Failure: 0 Tethering Flow Detected: 0 Chrg Correlation Exchange: 0 Subnet Change: 0 Session Recovery: 0 Session Sync: 0 Access Nw Info Report: 0 DCCA Failure Report: 0 Application Start: 0 Application Stop: 0 Change Of UE Presence In PRA: 1 136

139 Presence Reporting Area show subscribers pgw-only full all Local Fallback: CCRU sent: 0 show subscribers pgw-only full all The output of this command includes the following fields: Username : xyz Subscriber Type : Visitor Status : Online/Active State : Connected Connect Time : Mon Aug 28 07:32: Auto Delete : No Idle time : 00h00m06s MS TimeZone : n/a Daylight Saving Time: n/a Access Type: gtp-pdn-type-ipv4 Network Type: IP Access Tech: eutran pgw-service-name: pgw1 Callid: 00004e23 IMSI: MSISDN: Interface Type: S5S8GTP Low Access Priority: N/A TWAN Mode: N/A emps Bearer: No Emergency Bearer Type: N/A IMS-media Bearer: No S6b Auth Status: Enabled Access Peer Profile: default Acct-session-id (C1): C0A ThreeGPP2-correlation-id (C2): / 002shwI- Card/Cpu: 2/0 Sessmgr Instance: 1 ULI: TAI-ID: MCC: 214 MNC: 365 TAC: 0x6789 ECGI-ID: MCC: 214 MNC: 365 ECI: 0x PRA Information: PRA-ID: 0x Action: Start Status: In PRA Information: PRA-ID: 0xA11202 Action: Start Status: N/A show subscribers saegw-only full all The output of this command includes the following fields: Username : xyz SAEGW Call mode : Co-located Subscriber Type : Visitor Status : Online/Active State : Connected Bearer State : Active Connect Time : Mon Aug 28 08:21: SAEGW UID : Idle time : 00h00m19s Auto Delete : No Callid : 4e25 IMSI : Card/Cpu : 2/0 Sessmgr Instance : 1 Source context : ingress Destination context : egress Bearer Type : Default Bearer-Id : 5 Access Type : gtp-pdn-type-ipv4 Network Type : IP 137

140 show subscribers saegw-only full all Presence Reporting Area Access Tech : eutran saegw-service-name : saegw MSISDN : TWAN Mode : N/A emps Bearer : No IPv6 alloc type : n/a ECS Rulebase : prepaid Chrg Char Sel Mod : Peer Supplied Restoration priority level : n/a HLCOM Session : No IP Address : Bearer capable for restoration: No UE P-CSCF Restoration Support : No Peer Profile : PGW Access : default SGW Access : default SGW Network : default ULI : TAI-ID MCC : 214 MNC : 365 LAC : n/a TAC : 0x6789 SAC : n/a RAC : n/a CI : n/a ECI : 0x PRA Information: PRA-ID: 0x Action: Start Status: In PRA Information: PRA-ID: 0xA11202 Action: Start Status: N/A 138

141 CHAPTER 23 Rate Limiting System Throughput Support Feature Summary and Revision History, on page 139 Feature Description, on page 140 How It Works, on page 140 Configuring Rate Limiting System Throughput Support, on page 142 Monitoring and Troubleshooting, on page 143 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) All ASR 5500 VPC-DI VPC-SI Feature Default Disabled - License Required Related Changes in This Release Not applicable Related Documentation ASR 5500 System Administration Guide Command Line Interface Reference VPC-DI System Administration Guide VPC-SI System Administration Guide Revision Details Release First introduced

142 Feature Description Rate Limiting System Throughput Support Feature Description The Rate Limiting System Throughput Support feature enforces chassis throughput limit on any platform. This feature is enabled using the newly introduced license. When the license is enabled, this feature supports the following functionality: Allows change in the committed throughput value on a live node when a new license is applied. Enables monitoring of the configured committed throughput value on ASR 5500, GGSN, or PGW or a combination of nodes. Allows continuous monitoring of the served throughput as required on the ASR 5500, VPC-DI, and VPC-SI platforms. Allows configuration of a chassis-throughput threshold value such that alerts and traps are generated when the served throughput levels are close to or cross the configured threshold values (70%, 90%, 100%, and so on) compared to the committed throughput. How It Works The following sections provide a brief overview of how rate limiting works. Configuration Parameters When this feature is is implemented, the license key configures the committed throughput value. Note A new license would be required to change the configured committed throughput value. Also, when the warn level threshold is configured using the new snmp trap chassis-throughput-warn-threshold percentage trap-interval time_in_seconds CLI command, SNMP traps are raised when the served throughput reaches the warn level threshold. The time between each successive warn traps is configured such that the second warn trap is raised only after the trap interval has lapsed. Committed Throughput Enforcement When the chassis served throughput crosses the configured warn threshold percentage (70%,80% etc) of the committed throughput, traps are raised. To enforce committed throughput, the committed throughput of the chassis is divided equally among all the session cards (DPC, DPC2 cards in ASR 5500, SI instance in VPC-SI, and SF cards in VPC-DI). The per-cpu-complex throughput is calculated based on the individual card throughput values. Therefore, each session card serves its individual share of committed throughput values as explained in the following example: Scenario: Standard Implementation Platform: ASR 5500 Chassis Configuration: AMIO, SMIO, 7 DPC2 cards Committed throughput: 70 Gbps 140

143 Rate Limiting System Throughput Support How It Works For the above input calculation of committed throughput per per-card-cpu complex is as follows: There are 7 DPC2 cards; each card gets 70/7 = 10 Gbps throughput. DPC2 card has 3 CPUs; therefore, each per-card-cpu gets gets 10/3 = 3.3 Gbps throughput. Scenario: Card Insertion The following example depicts how the calculation is changed and enforced if a new card is added to the chassis. Committed throughput = 70 Gbps No of DPC2 cards = 7 +1 (new card added) = 8 Each DPC2 can now process 70/8 = 8.7 Gbps Per-cpu-complex throughput = 8.7/3 = 2.9 Gbps Therefore, each DPC2 card can serve upto 8.7 Gbps. Note In the card addition scenario, the throughput slightly reduces compared to the standard implementation. Note Demux and Standby cards are not considered for throughput calculation.therefore, these cards operate at full throughput. Scenario: Card Removal The following example depicts how the calculation is changed and enforced if a card is removed from the chassis. Committed throughput = 70 Gbps No of DPC/DPC2 cards = 7-1 (a card removed) = 6 Each DPC/DPC2 can now process 70/6 = 11.6 Gbps Per-cpu-complex throughput = 11.6/3 = 3.8 Gbps Therefore, each DPC card can serve upto 11.6 Gbps. Note In the card removal scenario, the throughput slightly increases compared to the standard implementation. Chassis Throughput Monitoring The committed throughput value is controlled through a license. The value can be viewed using the show license info CLI command. The served throughput value can be monitored using the show chassis-throughput CLI command, which allows monitoring of the served throughput on any platform. SNMP traps are raised when served throughput exceed the warning threshold levels (70%, 80%, and so on) of the committed throughput. After the values of served throughput cross normal levels, SNMP traps are raised to inform about ChassisThroughputWarn/ChassisThroughputOver state. These traps are cleared as the throughput approaches normal levels. 141

144 Licensing Rate Limiting System Throughput Support Licensing Limitations The Rate Limiting System Throughput Support is a licensed Cisco feature. 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. The Rate Limiting System Throughput Support feature has the following limitations. The effective served chassis throughput is inclusive of only the transferred bytes (tx) and not the received bytes (rx). The configured committed chassis throughput is distributed equally among all the session cards. Therefore, each session card can process data only in its individual capacity. Served throughput can never exceed committed throughput. Configuring Rate Limiting System Throughput Support The following section provides information about the CLI command in support of this feature. Configuring SNMP Traps for Warn Level and Trap Interval Thresholds Use the following CLI commands to configure the following in Global Configuration Mode: Raise SNMP traps when the served throughput crosses the warning threshold levels (70%, 80%, and so on) of the committed throughput and the frequency. Specify the trap interval (in seconds) between each successive warn traps such that the second warn trap is raised only after the trap interval has lapsed. configure snmp trap chassis-throughput-warn-threshold percentage trap-interval time in seconds end NOTES: chassis-throughput-warn-threshold percentage: Sets the chassis-throughput percentage at which a trap is raised to indicate that warning level is reached. The default value is 70%. trap-interval time in seconds: Specifies the interval (in seconds) between the warn traps. The default value is 3600 seconds. A license is required to enable the Rate Limiting System Throughput Support feature. If the license for rate-limiting-throughput is not present, chassis-throughput cannot be calculated, rate limiting cannot be enforced, and SNMP traps cannot be raised. When the rate-limiting-throughput per chassis license is applied but this CLI is not configured, it assumes the default values for the chassis throughput warn threshold and trap interval. 142

145 Rate Limiting System Throughput Support Monitoring and Troubleshooting Note For supplemental information related to this feature, refer to the Global Configuration Mode Commands section of the Command Line Reference. The following SNMP traps are generated when the configured warning level of the threshold is reached: ChassisThroughputOver ChassisThroughputWarn ChassisThroughputOverClear ChassisThroughputWarnClear For more details about these alarms/traps, See the SNMP MIB Reference. Monitoring and Troubleshooting This section provides information regarding the CLI command available in support of monitoring and troubleshooting the feature. Show Command(s) and/or Outputs show chassis-throughput This section provides information regarding the show command and/or its output in support of this feature. This new show command CLI includes the following fields to indicate the current throughput of the chassis. Chassis Throughput Card/Cpu Throughput show license info This show command CLI now includes the following fields to indicate the committed chassis throughput of the chassis. System SW - Base Throughput License Chassis Throughput 143

146 show license info Rate Limiting System Throughput Support 144

147 CHAPTER 24 SBc Message Size Feature Summary and Revision History, on page 145 Feature Changes, on page 146 Performance Indicator Changes, on page 146 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) MME ASR 5500 VPC-DI VPC-SI Feature Default Disabled Configuration Required Related Changes in This Release Not applicable Related Documentation MME Administration Guide Revision History Important Revision history details are not provided for features introduced before releases 21.2 and N5.1. Revision Details Release New SNMP trap "CBCBufSizeExceeded" is introduced and peer-id added to the existing log. The CBC can handle bigger SBc messages up to 50K bytes

148 Feature Changes SBc Message Size Revision Details First introduced. Release Pre 21.2 Feature Changes The MME uses the SBc interface, between the MME and the Cell Broadcast Center (CBC), for warning message delivery and control functions. In this release, the SBc message size is increased to handle large messages. Previous Behavior: When CBC sends the warning messages, MME dropped the SBc messages with size greater than 10K bytes. New Behavior: When CBC sends the warning messages, the MME can handle SBc messages up to 50K bytes. If the MME receives the WRITE-REPLACE WARNING REQUEST over 50K bytes, the message cannot be processed and a warning syslog is generated. When the size of the received SBc message is greater than 50 KB, a log with peer-id is displayed. The system also generates a SNMP trap CBCBufSizeExceeded. Customer Impact: With this enhancement, the CBC can send bigger SBc messages with more cell/tac information. Customer can troubleshoot easily with the new trap. Performance Indicator Changes show snmp trap statistics The output of this command includes "CBCBufSizeExceeded" field to indicate number of times the trap is hit. SNMP Traps A new trap "starcbcbufsizeexceeded" is introduced to indicate CBC message exceeded the buffer size limit. 146

149 CHAPTER 25 Service Function Scaling Feature Summary and Revision History, on page 147 Feature Changes, on page 148 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Enabled - Always-on Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Revision History Revision Details Release First introduced (This feature was not fully qualified in 6.0 release) 6.0 Manual scale-out of Service Functions (SFs) is fully supported as of this release. However, the manual scale-in of SFs is still not fully qualified yet

150 Feature Changes Service Function Scaling Feature Changes The Service Function (SF) scaling feature was first introduced in 6.0 release and made available only for testing purposes. Manual scale-out (addition) of SFs is fully supported as of this release. However, the manual scale-in (removal) of SFs is still not fully qualified yet. Refer to the Ultra Services Platform Deployment Automation Guide for more information. 148

151 CHAPTER 26 Short Message Service Feature Summary and Revision History, on page 149 Feature Description, on page 150 How It Works, on page 150 Configuring SMS Support, on page 159 Monitoring and Troubleshooting, on page 164 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) MME ASR 5500 UGP VPC-DI VPC-SI Feature Default Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference MME Administration Guide Statistics and Counters Reference Revision History Revision Details Release First introduced

152 Feature Description Short Message Service Feature Description The Short Message Service (SMS) is a means of sending messages of limited size to and from GSM/UMTS/EPS devices. SMS is a Store and Forward service, where messages are first sent to an entity called the Short Message Service Center (SMSC) and then forwarded to the recipient instead of transmitting directly to the destination. If the recipient is not connected, the message is saved in the SMSC and when the receiver becomes available, the network will contact the SMSC and forward the SMS. Thus, a GSM/UMTS/EPS PLMN supports the transfer of short messages between service centers and UEs. SMS is delivered over LTE through the following methods: SMS over SGs: The LTE UE device sends and retrieves circuit switched (CS) based SMS messages through the SGs interface. This method is already supported by the MME. SMS over IP: SIP based SMS messages are carried through IMS. The SMS to be transmitted is encapsulated in the SIP message. This method is not supported in this release. SMS in MME: SMS in MME delivers SMS services over the SGd interface to the SMSC. This method is intended for networks that do not deploy GERAN or UTRAN. This method is supported in this release. How It Works The SGd interface enables the transfer of short messages between the MME and the SMSC using Diameter protocol. SCTP is used as the transport protocol. The Short Message Control Protocol (SM-CP) and Short Message Relay Protocol (SM-RP) are traditional SMS protocols between MSC/VLR and UE. The SMS will be sent by the MME bypassing the MSC/VLR. SM-CP transmits the SMS and protects against loss caused by changing the dedicated channel. SM-RP manages the addressing and references. With the new interface configuration towards SMSC, MME will setup an SCTP association with the peer SMSC and the Diameter capability exchange will be performed. Limitations This section lists the known limitations for the SMS feature: MME will attempt to fallback to the SGs mode if SGd and SGs are enabled and if HSS rejects SMS in MME. This functionality is not supported in this release. Multiple SMSC service association is not supported. Only one endpoint will be associated with an MME service. If multiple SMSC services are required, then the SMS router must be used. The Serving Node Identity AVP is not supported in the Alert-Service-Centre-Request command. Hence SMSC needs to perform the "Send Routing Info for SM" procedure to retrieve the address of the new serving node from the HSS. Sending or processing of the "Pending MT Short Message Indication" flag under Forward Relocation Request will not be supported. 150

153 Short Message Service Flows Sending and processing of "MME number for MT SMS" and "MME Identifier for MT SMS" under Forward Relocation Request/Response are not supported. SMS will not be processed when the MME common procedure is ongoing. Notify Request to HSS for each UE due to removal of SMSC service is not supported. Notify Request to HSS is not supported if UE does an IMSI Detach. Delete Subscription Data Request from HSS is not supported for MO/MT SMS. CDR generation is not supported. Flows This section describes the call flows related to the SMS feature. Obtaining UE capability for SMS SMS Capability with HSS If the UE requests "SMS-only" in the Additional Update Type IE of combined attach and the network accepts the Attach Request for EPS services and "SMS-only", the network will indicate "SMS-only" in the Additional Update Result IE. If the SMS services are provided by SGd in the MME, the network will provide a TMSI and non-broadcast LAI in the Attach Accept message. A UE supporting SMS in MME needs to perform a registration with the HSS. The following call flow illustrates the request for registration with the HSS. Figure 5: SMS Capability with HSS Step 1 Description The UE initiates combined Attach Update or combined TAU/LAU to an MME. 151

154 HSS-initiated Removal of Registration for SMS Short Message Service Step 2 Description The MME sends an Update Location Request message to the HSS with the following data: SMS bit set in Feature-List in Supported-Features AVP. The Feature-List ID will be set to 2. "SMS-only" indication bit set in ULR-Flags AVP. MME address for MT-SMS routing in MME-Number-for-MT-SMS AVP. "SMS-only" indication set in SMS-Register-Request AVP HSS registers the UE for SMS support in MME. If the HSS accepts to register the MME identity as an MSC identity for terminating SMS services, then the HSS cancels the MSC/VLR registration from the HSS. For successful registrations, HSS sends a Location Update Answer (indication that the MME has registered for SMS) message to the MME. HSS sets the "MME Registered for SMS" bit in ULA-Flags AVP. HSS-initiated Removal of Registration for SMS The following procedure is applied when the HSS needs to indicate to the MME that it is no longer registered for SMS. Figure 6: Removal of Registration for SMS Step 1 2 Description An event will trigger the cancellation of the MME being registered for SMS. For example, removal of the SMS subscription for the UE, CS location update, and so on. The HSS sends an Insert Subscriber Data Request (Remove SMS registration) message to the MME to inform that it is no more registered for SMS in MME. 152

155 Short Message Service MO Forward Short Message Procedure Step 3 Description The MME sets the "MME Registered for SMS" parameter as not registered for SMS and the "SMS Subscription Data" is considered by the MME as invalid. It acknowledges with an Insert Subscriber Data Answer message to the HSS. MO Forward Short Message Procedure The MO Forward Short Message procedure is used between the serving MME and the SMSC to forward mobile originated short messages from a mobile user to a service center. MME checks the SMS related subscription data and forwards the short message. Figure 7: MO Forward Short Message Procedure Step Description The UE sends mobile originated SMS to MME in the Uplink NAS Transport message. MME will encapsulate the SMS in CP-DATA+RP-DATA. The message will be encoded into MO-Forward-Short-Message-Request (OFR) message and sent to SMSC. 153

156 MT Forward Short Message Procedure Short Message Service Step Description MME acknowledges the received SMS by sending CP-ACK to UE in the Downlink NAS Transport message. SMSC processes the received OFR message and responds backs with MO-Forward-Short-Message-Answer (OFA) message to MME. MME forwards the acknowledgement from SMSC in CP-DATA+RP-ACK to UE. UE acknowledges the SMS delivery by sending CP-ACK to MME in the Uplink NAS Transport message. MT Forward Short Message Procedure The MT Forward Short Message procedure is used between the SMSC and the serving MME to forward mobile terminated short messages. When receiving the MT Forward Short Message Request, the MME checks if the user is known. If it is an unknown user, an Experimental-Result-Code set to DIAMETER_ERROR_USER_UNKNOWN is returned. The MME attempts to deliver the short message to the UE. If the delivery of the short message to the UE is successful, the MME returns a Result-Code set to DIAMETER_SUCCESS. If the UE is not reachable via the MME, the MME sets the MNRF flag and returns an Experimental-Result-Code set to DIAMETER_ERROR_ABSENT_USER. If the delivery of the mobile terminated short message failed because the memory capacity exceeded, UE error, or UE not SM equipped, the MME returns an Experimental-Result-Code set to DIAMETER_ERROR_SM_DELIVERY_FAILURE with a SM Delivery Failure Cause indication. 154

157 Short Message Service MT Forward Short Message Procedure Figure 8: MT Forward Short Message Step Description The SMSC sends mobile terminated SMS to MME in the MT-Forward-Short-Message-Request (TFR) message. If the UE is in IDLE mode then MME initiates paging and establishes an S1AP connection provided UE replies with paging response. Once the UE is in CONNECTED mode, MME forwards the SMS in CP-DATA+RP-DATA to UE using the Downlink NAS Transport message. The UE acknowledges the received message by sending CP-ACK in the Uplink NAS Transport message. The UE processes the received SMS and sends CP-DATA+RP-ACK to MME. The MME sends the MT-Forward-Short-Message-Answer (TFA) command to SMSC and forwards CP-ACK to the UE in the Downlink NAS Transport message. 155

158 MT Forward Short Message Procedure (UE Unreachable) Short Message Service MT Forward Short Message Procedure (UE Unreachable) The MT Forward Short Message procedure is used between the SMSC and the serving MME to forward mobile terminated short messages for an UE that is unreachable. Figure 9: MT Forward Short Message Procedure (UE Unreachable) Step 1 2 Description The SMSC sends mobile terminated SMS to MME in the MT-Forward-Short-Message-Request (TFR) message. If the UE is paged but is not reachable, MME sets the MNRF flag and sends the MT-Forward-Short-Message-Answer (TFA) message with Subscriber-absent cause to the SMSC. 156

159 Short Message Service MT Forward Short Message Procedure (UE Memory Unavailable) Step Description When the UE becomes available and gets connected to the core network, MME clears the MNRF flag. MME sends the Alert-Service-Centre-Request (ALR) message to SMSC to inform that UE is reachable and that SMS delivery can be re-attempted. This is controlled by the mme sgd send message alr trigger mnrf CLI command and disabled by default. The SMSC responds with the Alert-Service-Centre-Answer (ALA) command to the MME and then follows the route procedure of sending MT SMS to UE. Also, the Notify Request to HSS will be sent with alert reason "user available". This is controlled by the mme s6a send message nor trigger mnrf CLI command and enabled by default. MT Forward Short Message Procedure (UE Memory Unavailable) This procedure is used between the SMSC and the serving MME to forward mobile terminated short messages for an UE that has unavailable memory. Step Description The SMSC sends mobile terminated SMS to MME in the MT-Forward-Short-Message-Request (TFR) message, but UE memory is full and returns the RP Error with cause code "Memory capacity exceeded". MME sets the MNRF flag and sends the MT-Forward-Short-Message-Answer (TFA) message with cause code "SM Delivery Failure" and failure cause "Memory capacity exceeded" to SMSC. Once the UE memory is available, it will send RP-SMMA message to MME. MME clears the MNRF flag and sends the Alert-Service-Centre-Request (ALR) message to SMSC to inform that UE memory is available and the SMS delivery can be re-attempted. This is controlled by the mme sgd send message alr trigger mnrf CLI command and disabled by default. The SMSC responds with the Alert-Service-Centre-Answer (ALA) command to the MME and then follows the route procedure of sending MT SMS to UE. The Notify Request to HSS will also be sent with alert reason "user memory available". This is controlled by the mme s6a send message nor trigger mnrf CLI command and enabled by default. MT Forward Short Message Procedure (UE Moves due to HO) This procedure is used between the SMSC and the serving MME to forward mobile terminated short messages for an UE that moves due to handover. Step 1 Description While the MNRF flag is set due to UE unreachable or UE memory unavailable, UE may do a handover (HO) and move to another MME or SGSN. 157

160 Standards Compliance Short Message Service Step Description Since the MNRF flag was set, MME will send the Alert-Service-Centre-Request (ALR) message to SMSC to inform that UE has moved to another MME or SGSN. This is controlled by the mme sgd send message alr trigger mnrf CLI command and disabled by default. The SMSC responds with the Alert-Service-Centre-Answer (ALA) command to the MME and then follows the route procedure of sending MT SMS to UE. The Notify Request to HSS will also be sent with alert reason "user memory available". This is controlled by the mme s6a send message nor trigger mnrf CLI command and enabled by default. Important This procedure has the following limitations: New Serving Node Identity AVP is not supported and SMSC needs to perform the "Send Routing Info for SM" procedure to retrieve the new serving node's address from the HSS. Sending or processing of the "Pending MT Short Message Indication" flag under Forward Relocation Request will not be supported. Standards Compliance The SMS feature complies with the following standards: 3GPP TS version : Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Technical realization of the Short Message Service (SMS) 3GPP TS version : Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface 3GPP TS version : Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 3GPP TS version : Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 3GPP TS version : Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol 3GPP TS version : Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol 3GPP TS version : Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) 3GPP TS version : Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) 158

161 Short Message Service Configuring SMS Support Configuring SMS Support This section provides information on the CLI commands to configure the SMSC service for SMS support in MME. Creating and Configuring SMSC Service Use the following configuration to enable the SMSC service and configure the parameters in SMSC service to support MO/MT SMS delivery between SMSC, MME, and UE. configure context context_name smsc-service smsc_svc_name diameter { dictionary standard endpoint endpoint_name } mme-address mme_address tmsi tmsi_value non-broadcast mcc mcc_value mnc mnc_value lac lac_value default diameter dictionary no { diameter endpoint mme-address tmsi } end NOTES: context context_name: Creates or specifies an existing context and enters the Context Configuration mode. context_name specifies the name of a context entered as an alphanumeric string of 1 to 79 characters. smsc-service smsc_svc_name: Creates and configures an SMSC Peer service to allow communication with SMSC peer. smsc_svc_name specifies the name of the SMSC service as an alphanumeric string of 1 to 63 characters. Entering this command in the Context mode results in the following prompt: [context_name]host_name(config-smsc-service)# diameter { dictionary standard endpoint endpoint_name }: Configures the Diameter interface to be associated with the SMSC service. dictionary standard: Configures the standard SGd dictionary. endpoint endpoint_name: Enables Diameter to be used for accounting and specifies which Diameter endpoint to use. endpoint_name must be an alphanumeric string of 1 to 63 characters. mme-address mme_address: Configures the MME address to send SMS on the SGd interface. mme_address specifies the MME address (ISDN identity) as an integer from 1 to 15. tmsi tmsi_value non-broadcast mcc mcc_value mnc mnc_value lac lac_value: Configures the TMSI to be sent to UE. tmsi_value specifies the 4-byte M-TMSI as an integer from 1 to non-broadcast: Configures the non-broadcast Location Area Identifier (LAI). mcc mcc_value: Configures the mobile country code (MCC) portion of non-broadcast LAI for the SMSC service as an integer from 100 through 999. mnc mnc_value: Configures the mobile network code (MNC) portion of non-broadcast LAI for the SMSC service as a 2- or 3-digit integer from 00 through

162 Configuring MME Preference for SMS Short Message Service lac lac_value: Configures the location area code (LAC) value as an integer from 1 to default: Configures the standard Diameter SGd dictionary by default. no: Disables the specified configuration. Verifying the Configuration Use the following command to verify the configuration for all SMSC services or a specified SMSC service: show smsc-service { all name smsc_svc_name statistics { all name smsc_svc_name summary } } Configuring MME Preference for SMS Use the following configuration to configure the MME preference for SMS and SMSC address. configure call-control-profile profile_name sms-in-mme { preferred [ smsc-address smsc_address ] smsc-address smsc_address subscribe [ notify ue ] } no sms-in-mme { preferred [ smsc-address ] smsc-address subscribe [ notify ue ] } default sms-in-mme { subscribe [ notify ue ] } end NOTES: call-control-profile profile_name: Creates an instance of a call control profile. profile_name specifies the name of a call control profile entered as an alphanumeric string of 1 to 64 characters. sms-in-mme: Configures the SMS capability (SGd interface for SMS) in MME. preferred: Configures the SMS preference in MME. smsc-address smsc_address: Configures the SMSC address (ISDN identity) for the MME to send SMS on the SGd interface. smsc_address must be an integer from 1 to 15. subscribe [ notify ue ]: Enables the Subscription Request for SMS services (via SGd) to HSS for all users. notify: Configures the notification to be sent to the users. ue: Sends SMS-Only indication to UE in Attach/TAU Accept message (only if HSS accepts SMS Registration for SGd). default: Restores the default configuration, which is to enable the Subscription Request for SMS services (via SGd) to HSS for all users. no: Deletes the specified configuration. Associating SMSC Service with MME Service Use the following configuration to associate an SMSC service with the MME service. 160

163 Short Message Service Configuring Alert SC Request on SGd interface configure context context_name mme-service service_name associate smsc-service smsc_svc_name [ context ctx_name ] end NOTES: context context_name: Creates or specifies an existing context and enters the Context Configuration mode. context_name specifies the name of a context entered as an alphanumeric string of 1 to 79 characters. mme-service service_name: Creates an MME service or configures an existing MME service in the current context. service_name specifies the name of the MME service as an alphanumeric string of 1 to 63 characters. associate smsc-service smsc_svc_name: Associates an SMSC service with the MME service. smsc_svc_name specifies the name for a pre-configured SMSC service to associate with the MME service as an alphanumeric string of 1 to 63 characters. context ctx_name: Identifies a specific context name where the named service is configured. If this keyword is omitted, the named service must exist in the same context as the MME service. ctx_name must be an alphanumeric string of 1 to 63 characters. Configuring Alert SC Request on SGd interface Use the following configuration to control sending the Alert SC Request (ALR) on SGd interface. The user sends the Alert SC Request on SGd interface to SMSC in the event of user availability to received SMS (if user moved to active state from idle or user's memory is available). It is also sent if the user did a handover to the new MME/SGSN and any MT SMS was pending for the user. configure call-control-profile profile_name [ no ] mme sgd send message alr trigger mnrf end NOTES: call-control-profile profile_name: Creates an instance of a call control profile. profile_name specifies the name of a call control profile entered as an alphanumeric string of 1 to 64 characters. mme: Configures MME capability. sgd: Configures MME capability on SGd interface. send: Configures MME capability to send on SGd interface. message: Configures MME capability to send message on SGd interface. alr: Configures MME capability to send Alert SC Request (ALR) on SGd interface. trigger: Configures trigger to send the message. mnrf: Sends message to trigger MNRF flag on SGd interface (SMS in MME). no: Disables sending the ALR on SGd interface. This command is disabled by default. 161

164 Configuring Notify Request on S6a Interface Short Message Service Verifying the Configuration Use the following command to verify whether Alert SC Request (MME SGd Message Options) is enabled or disabled: show call-control-profile full all Configuring Notify Request on S6a Interface Use the following configuration to control sending the Notify Request (NOR) on S6a interface. The user sends the Notify Request on S6a interface to HSS in the event of user availability to received SMS (user moved to active state from idle or user's memory is available). configure call-control-profile profile_name [ no ] mme s6a send message nor trigger mnrf end NOTES: call-control-profile profile_name: Creates an instance of a call control profile. profile_name specifies the name of a call control profile entered as an alphanumeric string of 1 to 64 characters. mme: Configures MME capability. s6a: Configure MME capbility on S6a interface. send: Configures MME capability to send on S6a interface. message: Configures MME capability to send message on S6a interface. nor: Configures MME capability to send Notify Request (NOR) on S6a interface. trigger: Configures trigger to send the message. mnrf: Sends message to trigger MNRF flag on S6a interface (SMS in MME). no: Disables sending the NOR on S6a interface. This command is enabled by default. Verifying the Configuration Configuring Queue Timers Use the following command to verify whether Notify Request (MME S6a Message Options) is enabled or disabled: show call-control-profile full all Use the following configuration to configure the MT Queue, TC1N, TR1N, and TR2N timers. configure context context_name mme-service mme_svc_name emm { mt-queue-timeout mtq_timer tc1n-timeout tc1n_timer 162

165 Short Message Service Configuring CP Data Retransmissions tr1n-timeout tr1n_timer tr2n-timeout tr2n_timer } default emm { mt-queue-timeout tc1n-timeout tr1n-timeout tr2n-timeout } end NOTES: context context_name: Creates or specifies an existing context and enters the Context Configuration mode. context_name specifies the name of a context entered as an alphanumeric string of 1 to 79 characters. mme-service service_name: Creates an MME service or configures an existing MME service in the current context. service_name specifies the name of the MME service as an alphanumeric string of 1 to 63 characters. mt-queue-timeout mtq_timer: Configures the timer to hold MT SMS in MT queue. MT SMS will be present in the queue while the previous SMS is being processed. The timer expiry will return error to SMSC for an absent subscriber. mtq_timer specifies the timeout in seconds, as an integer from 1 to 300. Default: 30 seconds tc1n-timeout tc1n_timer: Configures the retransmission timer to send CP SMS data to UE for MO/MT scenario. tc1n_timer specifies the timeout in seconds, as an integer from 1 to 20. Default: 5 seconds tr1n-timeout tr1n_timer: Configures the wait time to receive RP-Ack from UE for MT SMS, before sending error to SMSC. tr1n_timer specifies the timeout in seconds, as an integer from 1 to 300. Default: 30 seconds tr2n-timeout tr2n_timer: Configures the wait time to send RP-Ack to UE for MO SMS, before sending protocol error to UE. tr2n_timer specifies the timeout in seconds, as an integer from 1 to 300. Default: 30 seconds default: Resets the specified timer timeout to the default value. Verifying the Configuration Use the following command to verify the configuration for TC1N, TR1N, TR2N, and MT Queue timeout: show mme-service [ all name service_name ] Configuring CP Data Retransmissions Use the following configuration to configure the maximum number of retransmissions of CP data for MO or MT SMS scenario in MME. configure context context_name mme-service service_name [ default ] cp-data-max-retransmissions num_retrans end NOTES: context context_name: Creates or specifies an existing context and enters the Context Configuration mode. context_name specifies the name of a context entered as an alphanumeric string of 1 to 79 characters. 163

166 Monitoring and Troubleshooting Short Message Service mme-service service_name: Creates an MME service or configures an existing MME service in the current context. service_name specifies the name of the MME service as an alphanumeric string of 1 to 63 characters. cp-data-max-retransmissions num_retrans: Configures the number of times CP Data for SMS is retransmitted. num_retrans must be an integer from 1 to 10. default: Sets the default value to 2. Verifying the Configuration Use the following command to verify the count for maximum retransmissions of CP Data: show mme-service [ all name service_name ] Monitoring and Troubleshooting This section provides information on the show commands and bulk statistics available for the SMS Support feature. Show Commands and/or Outputs show call-control-profile full all This section provides information regarding show commands and their outputs for the SMS Support feature. The output of this command includes the following fields: SMS in MME Displays the configured value (preferred / not-preferred) for SMS in MME. SMSC Address Displays the configured SMSC address. Send SMS Subscription Request to HSS Indicates whether the SMS Subscription Request to HSS is enabled or disabled. Send SMS Subscription Notification to UE Indicates whether the SMS Subscription Notification to UE is enabled or disabled. MME S6a Message Options: Notify Req (Trigger : MNRF flag) Indicates whether the MNRF flag trigger for Notify Request is enabled or disabled. MME SGd Message Options: Alert SC Request (Trigger : MNRF flag) Indicates whether the MNRF flag trigger for Alert SC Request is enabled or disabled. show mme-service all The output of this command includes the following fields: SMSC Context Displays the name of the context in which SMSC service is configured. 164

167 Short Message Service show mme-service session full all SMSC Service Displays the name of the SMSC service associated with the MME service. TC1N Timeout Displays the timeout duration configured for the TC1N timer. This timer can be configured to any value between 1 and 20 seconds. By default, it is 5 seconds. TR1N Timeout Displays the timeout duration configured for the TR1N timer. This timer can be configured to any value between 1 and 300 seconds. By default, it is 30 seconds. TR2N Timeout Displays the timeout duration configured for the TR2N timer. This timer can be configured to any value between 1 and 300 seconds. By default, it is 30 seconds. MT Queue Timeout Displays the timeout duration configured for the MT Queue timer. This timer can be configured to any value between 1 and 300 seconds. By default, it is 30 seconds. CP Data Max Retransmissions Count Displays the number of times CP Data for SMS is retransmitted. show mme-service session full all The output of this command includes the following fields: SMS Capability Information: SGd Enabled Displays Yes or No to indicate whether SGd is enabled or not. MS Not Reachable Displays Yes or No to indicate whether MS Not Reachable is enabled or not. MS Memory Capacity Exceeded Displays Yes or No to indicate whether MS memory capacity has exceeded. show mme-service statistics The output of this command includes the following fields: Paging Initiation for PS SMS Events: Attempted The total number of ECM statistics-related PS SMS Paging Initiation events that were attempted. Success The total number of ECM statistics-related PS SMS Paging Initiation events that were successful. Failures The total number of ECM statistics-related PS SMS Paging Initiation events that failed. Success at Last n enb The total number of ECM statistics-related PS SMS Paging Initiation events that succeeded at the last known enodeb. Success at Last TAI The total number of ECM statistics-related PS SMS Paging Initiation events that succeeded at an enodeb in the TAI from which the UE was last heard. Success at TAI List The total number of ECM statistics-related PS SMS Paging Initiation events that succeeded at an enodeb in all TAIs present in the TAI list assigned to the UE. show smsc-service name <smsc_svc_name> The output of this command includes the following fields: 165

168 show smsc-service statistics all Short Message Service Service name Displays the name of the configured SMSC service. Context Displays the name of the configured context. Status Displays the status of the SMSC service. Diameter endpoint Displays the configured Diameter endpoint name. Diameter dictionary Displays the configured Diameter dictionary. Tmsi Displays the configured TMSI value. Non-broadcast-Lai Displays the configured non-broadcast MCC, MNC, and LAC values. MME-address Displays the configured MME address. show smsc-service statistics all The output of this command includes the following fields: Session Stats: Total Current Sessions Displays the total number of current SMSC sessions. Sessions Failovers Displays the number of SMSC session failovers. Total Starts Displays the total number of SMSC session starts. Total Session Updates Displays the total number of SMSC session updates. Total Terminated Displays the total number of terminated SMSC sessions. Message Stats: Total Messages Rcvd Displays the total number of messages received. Total Messages Sent Displays the total number of messages sent. OF Request Displays the total number of OF requests. OF Answer Displays the total number of OF answers. OFR Retries Displays the total number of OFR retries. OFR Timeouts Displays the total number of OFR timeouts. OFA Dropped Displays the total number of OFA dropped. TF Request Displays the total number of TF requests. TF Answer Displays the total number of TF answers. TFR Retries Displays the total number of TFR retries. TFA Timeouts Displays the total number of TFA timeouts. TFA Dropped Displays the total number of TFA dropped requests. AL Request Displays the total number of AL requests. AL Answer Displays the total number of AL answers. 166

169 Short Message Service show smsc-service statistics summary ALR Retries Displays the total number of ALR retries. ALR Timeouts Displays the total number of ALR timeouts. ALA Dropped Displays the total number of ALA dropped. Message Error Stats: Unable To Comply Displays the total number of message errors containing the result code "Unable To Comply". User Unknown Displays the total number of message errors containing the result code "User Unknown". User Absent Displays the total number of message errors containing the result code "User Absent". User Illegal Displays the total number of message errors containing the result code "User Illegal". SM Delivery Failure Displays the total number of message errors containing the result code "SM Delivery Failure". User Busy for MT SMS Displays the total number of message errors containing the result code "User Busy for MT SMS". Other Errors Displays the total number of message errors containing the result code "Other Errors". Bad Answer Stats: Auth-Application-Id Displays the absence or unexpected value in Auth-Application-Id AVP. Session-Id Displays the absence or unexpected value in Session-Id AVP. Origin-Host Displays the absence of Origin-Host AVP. Origin Realm Displays the absence of Origin-Realm AVP. Parse-Message-Errors Displays the total number of parse errors in the message. Parse-Mscc-Errors Displays the total number of parse errors in MSCC AVP. Miscellaneous Displays the total number of other miscellaneous errors. show smsc-service statistics summary The output of this command includes the following fields: SMSC Session Stats: Total Current Sessions Displays the total number of current SMSC sessions. Sessions Failovers Displays the total number of SMSC session failovers. Total Starts Displays the total number of SMSC session starts. Total Session Updates Displays the total number of SMSC session updates. Total Terminated Displays the total number of terminated SMSC sessions. 167

170 show sms statistics mme-only verbose Short Message Service show sms statistics mme-only verbose The output of this command includes the following fields: SMS Statistics: Session Statistics: MO SMS (In Progress) The total number of mobile originated (MO) SMS messages that are waiting in the MME to be delivered. MT SMS (In Progress) The total number of mobile terminated (MT) SMS messages that are waiting in the MME to be delivered. MT SMS (In Queue ) The total number of mobile terminated SMS messages in the queue. SMMA (In Progress) The total number of procedures for retrieval of available SMS memory in progress. MO-SMS Attempted The total number of mobile originated SMS messages that are attempted to be delivered by the network. MO-SMS Successful The total number of mobile originated SMS messages that are successfully delivered by the network. MT-SMS Attempted The total number of mobile terminated SMS messages that are attempted to be delivered by the network. MT-SMS Successful The total number of mobile terminated SMS messages that are successfully delivered by the network. SMMA Attempted The total number of procedures for retrieval of available SMS memory attempted. SMMA Successful The total number of procedures for retrieval of available SMS memory successful. Message Statistics: CP Layer Messages: CP Data (Tx) The total number of protocol data units sent during connection setup. CP Data (Rx) The total number of protocol data units received during connection setup. CP Ack (Tx) The total number of Ack messages sent during connection setup. CP Ack (Rx) The total number of Ack messages received during connection setup. CP Error (Tx) The total number of protocol errors during connection setup in Tx message. CP Error (Rx) The total number of protocol errors during connection setup in Rx message. CP Error Cause Stats: Network Failure (Tx)/(Rx) The total number of protocol errors during connection setup due to network failure in Tx/Rx message. Congestion (Tx)/(Rx) The total number of protocol errors during connection setup due to congestion in Tx/Rx message. 168

171 Short Message Service show sms statistics mme-only verbose Invalid TID (Tx)/(Rx) The total number of protocol errors during connection setup due to invalid transaction ID (TID) in Tx/Rx message. Invalid Semantic (Tx)/(Rx) The total number of protocol errors during connection setup due to invalid semantics in Tx/Rx message. Invalid Mand Info (Tx)/(Rx) The total number of protocol errors during connection setup as mandatory information in Tx/Rx message is invalid. Invalid Msg Type (Tx)/(Rx) The total number of protocol errors during connection setup due to invalid Tx/Rx message type. Invalid Prot State (Tx)/(Rx) The total number of protocol errors during connection setup as protocol state in Tx/Rx message is invalid. Invalid IE (Tx)/(Rx) The total number of protocol errors during connection setup as information element in Tx/Rx message is invalid. Protocol Error (Tx)/(Rx) The total number of protocol errors during connection setup as protocol error in Tx/Rx message. Undefined Cause (Tx)/(Rx) The total number of protocol errors during connection setup due to unspecified error in Tx/Rx message. Message Drop Counters: CP Data The total number of CP data packets dropped during connection setup. Retransmission Drops The total number of data packets dropped during retransmission. Unknown TID Drops The total number of data packets dropped during connection setup due to unknown transaction ID (TID). Invalid TID Drops The total number of data packets dropped during connection setup due to invalid transaction ID (TID) received. CP Ack The total number of CP acknowledgement messages dropped during connection setup. CP-ACK Drop for Invalid TID Rcvd The total number of CP-Ack messages dropped during connection setup due to invalid transaction ID (TID) received. CP Error The total number of CP data packets dropped during connection setup due to error in connection. CP-ERR Drop for Invalid TID Rcvd The total number of CP-ERR messages dropped during connection setup due to invalid transaction ID (TID) received. RP Layer Messages: RP Data (Tx) The total number of protocol data units sent during message relay. RP Data (Rx) The total number of protocol data units received during message relay. RP Ack (Tx) The total number of Ack messages sent during message relay. RP Ack (Rx) The total number of Ack messages received during message relay. RP Error (Tx) The total number of protocol errors during message relay in Tx message. 169

172 show sms statistics mme-only verbose Short Message Service RP Error (Rx) The total number of protocol errors during message relay in Rx message. RP SMMA (Rx) The total number RP SMMA messages received. RP Error Cause Stats: Unassigned Number (Tx) The total number of protocol errors sent during message relay due to unassigned protocol number. Opr. Determined Barring (Tx) The total number of protocol errors sent during message relay due to operator determined barring. Call Barred (Tx) The total number of protocol errors sent during message relay due to call barring. Reserved (Tx) The total number of protocol errors sent during message relay due to reserved resources. SM Transfer Rejected (Tx) The total number of protocol errors sent during message relay due to session manager transfer rejection. Destination Out Of Order (Tx) The total number of protocol errors sent during message relay due to out of order on destination. Unidentified Subscriber (Tx) The total number of protocol errors sent during message relay due to unidentified subscriber. Facility Rejected (Tx) The total number of protocol errors sent during message relay due to facility rejection. Unknown Subscriber (Tx) The total number of protocol errors sent during message relay due to unknown subscriber. Network Out Of Order (Tx) The total number of protocol errors sent during message relay due to out-of-order network. Temporary Failure (Tx) The total number of protocol errors sent during message relay due to temporary failure in network. Congestion (Tx) The total number of protocol errors sent during message relay due to congestion in network. Not Subscribed (Tx) The total number of protocol errors sent during message relay as this service is not subscribed by subscriber. Not Implemented (Tx) The total number of protocol errors sent during message relay as this service is not yet implemented. Interworking Error (Tx) The total number of protocol errors sent during message relay due to interworking error between two networks or technology. Resource Un-available (Tx) The total number of protocol errors sent during message relay as resources are not available. Memory Capacity Exceeded (Rx) The total number of protocol errors received during message relay as capacity is exceeded. Invalid Reference Number (Tx)/(Rx) The total number of protocol errors during message relay as invalid reference in Tx/Rx message. 170

173 Short Message Service show sms statistics mme-only verbose Invalid Semantic (Tx)/(Rx) The total number of protocol errors during message relay due to invalid semantics in Tx/Rx message. Invalid Mandatory Info (Tx)/(Rx) The total number of protocol errors during message relay as mandatory information in Tx/Rx message is invalid. Invalid Message Type (Tx)/(Rx) The total number of protocol errors during message relay due to invalid Tx/Rx message type. Invalid Protocol State (Tx)/(Rx) The total number of protocol errors during message relay as protocol state in Tx/Rx message is invalid. Invalid IE (Tx)/(Rx) The total number of protocol errors during message relay as information element in Tx/Rx message is invalid. Protocol Error (Tx)/(Rx) The total number of RP ERROR messages sent/received with the cause Protocol Error in the message header. Undefined Error (Tx)/(Rx) The total number of protocol errors during message relay due to unspecified error in Tx/Rx message. Message Drop Counters: RP Data The total number of RP data packets dropped during message relay. RP Ack The total number of RP acknowledgement messages dropped during message relay. RP Error The total number of RP data packets dropped during message relay due to error in connection. RP Decode Failures The total number of messages dropped during message relay due to invalid transaction ID (TID) received. General Statistics: Concatenated MO SMS The total number of concatenated mobile originated SMS messages. CP Timer Expiry The total number of events when timer expired during connection setup. TR1N Timer The total number of events when TR1N timer expired during mobile terminated SMS is in wait state for RP-ACK. TR2N Timer The total number of events when TR2N timer expired during mobile terminated SMS is in wait state to send RP-ACK. CP Data Retrans The total number of protocol data units retransmitted during connection setup. RP Msg Encode Fail The total number of message encoding failures during message relay. CP Data Tx Fail The total number of protocol data units with Tx messages failed during connection setup. CP Data Inv TID The total number of protocol data units with invalid transaction ID (TID) during connection setup. Max Retrans Reached The total number of events when retransmission limit is exhausted during connection setup. 171

174 Bulk Statistics Short Message Service SMSC Addr Restricted The total number of SMSC addresses restricted. MO SMSC Addr Restricted The total number of mobile originated SMSC addresses restricted. MT SMSC Addr Restricted The total number of mobile terminated SMSC addresses restricted. CP-DATA No Cp Ack Rx The total number of mobile terminated messages failed as no acknowledgement is received during connection setup. Release Indication Waiting MO CP-ACK Delivery The total number of release indications waiting to be transferred between network and MS for mobile originated control protocol acknowledgement messages that are being delivered. Release Indication Waiting MO CP-DATA Delivery The total number of release indications waiting to be transferred between network and MS for mobile originated control protocol data messages that are being delivered. Release Indication Waiting MO CP-ERR Delivery The total number of release indications waiting to be transferred between network and MS for mobile originated control protocol error messages that are being delivered. Release Indication Waiting MT CP-DATA Delivery The total number of release indications waiting to be transferred between network and MS for mobile terminated control protocol data messages that are being delivered. Release Indication Waiting MT CP-ACK Delivery The total number of release indications waiting to be transferred between network and MS for mobile terminated control protocol acknowledgement messages that are being delivered. Release Indication Waiting MT CP-ERR Delivery The total number of release indications waiting to be transferred between network and MS for mobile terminated control protocol error messages that are being delivered. MT-SMS Failures: IMSI Record Not Found The total number of mobile terminated messages failed as IMSI record is not available. Busy Subscriber The total number of mobile terminated messages failed due to busy subscriber. Detached Subscriber The total number of mobile terminated messages failed due to detached subscriber. MT Queue Full The total number of mobile terminated messages failed as messaged queue was full. Bulk Statistics This section provides information on the bulk statistics supported for the SMS feature. MME Schema The following SMS feature related bulk statistics are available in the MME schema. 172

175 Short Message Service MME-SMS Schema Bulk Statistics ps-sms-paging-init-events-attempted ps-sms-paging-init-events-success ps-sms-paging-init-events-failures ps-sms-paging-last-enb-success ps-sms-paging-last-tai-success ps-sms-paging-tai-list-success Description The total number of PS SMS Paging Initiation events that were attempted. The total number of PS SMS Paging Initiation events that were successful. The total number of PS SMS Paging Initiation events that failed. The total number of PS SMS Paging Initiation events that succeeded at the last known enodeb. The total number of PS SMS Paging Initiation events that succeeded at an enodeb in the TAI from which the UE was last heard. The total number of PS SMS Paging Initiation events that succeeded at an enodeb in all TAIs present in the TAI list assigned to the UE. MME-SMS Schema The following SMS feature related bulk statistics are available in the MME-SMS schema. Bulk Statistics mo-sms-in-progress mt-sms-in-progress mt-sms-in-queue sms-memory-available-in-progress mo-sms-attempted mo-sms-successful mt-sms-attempted mt-sms-successful sms-memory-available-attempted Description The total number of mobile originated (MO) SMS messages that are waiting in the MME to be delivered. The total number of mobile terminated (MT) SMS messages that are waiting in the MME to be delivered. The total number of mobile terminated SMS messages in the queue. The total number of procedures for retrieval of available SMS memory in progress. The total number of mobile originated SMS messages that are attempted to be delivered by the network. The total number of mobile originated SMS messages that are successfully delivered by the network. The total number of mobile terminated SMS messages that are attempted to be delivered by the network. The total number of mobile terminated SMS messages that are successfully delivered by the network. The total number of procedures for retrieval of available SMS memory attempted. 173

176 MME-SMS Schema Short Message Service Bulk Statistics sms-memory-available-successful conn-prot-data-tx conn-prot-data-rx conn-prot-ack-tx conn-prot-ack-rx conn-prot-error-tx conn-prot-error-rx conn-prot-error-nwt-fail-tx conn-prot-error-nwt-fail-rx conn-prot-error-congestion-tx conn-prot-error-congestion-rx conn-prot-error-invalid-tid-tx conn-prot-error-invalid-tid-rx conn-prot-error-invalid-semantic-tx conn-prot-error-invalid-semantic-rx conn-prot-error-invalid-mand-info-tx Description The total number of procedures for retrieval of available SMS memory successful. The total number of protocol data units sent during connection setup. The total number of protocol data units received during connection setup. The total number of Ack messages sent during connection setup. The total number of Ack messages received during connection setup. The total number of protocol errors during connection setup in Tx message. The total number of protocol errors during connection setup in Rx message. The total number of protocol errors during connection setup due to network failure in Tx message. The total number of protocol errors during connection setup due to network failure in Rx message. The total number of protocol errors during connection setup due to congestion in Tx message. The total number of protocol errors during connection setup due to congestion in Rx message. The total number of protocol errors during connection setup due to invalid transaction ID (TID) in Tx message. The total number of protocol errors during connection setup due to invalid transaction ID (TID) in Rx message. The total number of protocol errors during connection setup due to invalid semantics in Tx message. The total number of protocol errors during connection setup due to invalid semantics in Rx message. The total number of protocol errors during connection setup as mandatory information in Tx message is invalid. 174

177 Short Message Service MME-SMS Schema Bulk Statistics conn-prot-error-invalid-mand-info-rx conn-prot-error-invalid-msg-type-tx conn-prot-error-invalid-msg-type-rx conn-prot-error-invalid-prot-state-tx conn-prot-error-invalid-prot-state-rx conn-prot-error-invalid-ie-tx conn-prot-error-invalid-ie-rx conn-prot-error-protocol-error-tx conn-prot-error-protocol-error-rx conn-prot-error-undefined-cause-tx conn-prot-error-undefined-cause-rx conn-prot-data-dropped conn-prot-ack-dropped conn-prot-error-dropped conn-prot-inval-tid-rcvd relay-prot-data-tx relay-prot-data-rx Description The total number of protocol errors during connection setup as mandatory information in Rx message is invalid. The total number of protocol errors during connection setup due to invalid Tx message type. The total number of protocol errors during connection setup due to invalid Rx message type. The total number of protocol errors during connection setup as protocol state in Tx message is invalid. The total number of protocol errors during connection setup as protocol state in Rx message is invalid. The total number of protocol errors during connection setup as information element in Tx message is invalid. The total number of protocol errors during connection setup as information element in Rx message is invalid The total number of protocol errors during connection setup as protocol error in Tx message. The total number of protocol errors during connection setup as protocol error in Rx message. The total number of protocol errors during connection setup due to unspecified error in Tx message. The total number of protocol errors during connection setup due to unspecified error in Rx message. The total number of data packets dropped during connection setup. The total number of Ack messages dropped during connection setup. The total number of data packets dropped during connection setup due to error in connection. The total number of messages dropped during connection setup due to invalid transaction ID (TID) received. The total number of protocol data units sent during message relay. The total number of protocol data units received during message relay. 175

178 MME-SMS Schema Short Message Service Bulk Statistics relay-prot-ack-tx relay-prot-ack-rx relay-prot-err-tx relay-prot-err-rx relay-prot-err-unassigned-num relay-prot-err-opr-determ-barring relay-prot-err-call-barred relay-prot-err-reserved relay-prot-err-sm-transfer-rej relay-prot-err-dest-out-of-order relay-prot-err-unidentified-subs relay-prot-err-facility-rej relay-prot-err-unknown-subs relay-prot-err-netwk-out-of-order relay-prot-err-temp-fail relay-prot-err-congestion relay-prot-err-not-subscribed relay-prot-err-not-implemented Description The total number of Ack messages sent during message relay. The total number of Ack messages received during message relay. The total number of protocol errors during message relay in Tx message. The total number of protocol errors during message relay in Rx message. The total number of protocol errors during message relay due to unassigned protocol number. The total number of protocol errors during message relay due to operator determined barring. The total number of protocol errors during message relay due to call barring. The total number of protocol errors during message relay due to reserved resources. The total number of protocol errors during message relay due to session manager transfer rejection. The total number of protocol errors during message relay due to out of order on destination. The total number of protocol errors during message relay due to unidentified subscriber. The total number of protocol errors during message relay due to facility rejection. The total number of protocol errors during message relay due to unknown subscriber. The total number of protocol errors during message relay due to out-of-order network. The total number of protocol errors during message relay due to temporary failure in network. The total number of protocol errors during message relay due to congestion in network. The total number of protocol errors during message relay as this service is not subscribed by subscriber. The total number of protocol errors during message relay as this service is not yet implemented. 176

179 Short Message Service MME-SMS Schema Bulk Statistics relay-prot-err-interworking-err relay-prot-err-res-unavail relay-prot-err-mem-capacity-exceed relay-prot-err-inval-ref-num-tx relay-prot-err-inval-ref-num-rx relay-prot-err-inval-semantic-tx relay-prot-err-inval-semantic-rx relay-prot-err-inval-mand-info-tx relay-prot-err-inval-mand-info-rx relay-prot-err-inval-msg-type-tx relay-prot-err-inval-msg-type-rx relay-prot-err-inval-prot-state-tx relay-prot-err-inval-prot-state-rx relay-prot-err-inval-ie-tx relay-prot-err-inval-ie-rx relay-prot-err-protocol-error-rx Description The total number of protocol errors during message relay due to interworking error between two networks or technology. The total number of protocol errors during message relay as resources are not available. The total number of protocol errors during message relay as capacity is exceeded. The total number of protocol errors during message relay as invalid reference in Tx message. The total number of protocol errors during message relay as invalid reference in Rx message. The total number of protocol errors during message relay due to invalid semantics in Tx message. The total number of protocol errors during message relay due to invalid semantics in Rx message. The total number of protocol errors during message relay as mandatory information in Tx message is invalid. The total number of protocol errors during message relay as mandatory information in Rx message is invalid. The total number of protocol errors during message relay due to invalid Tx message type. The total number of protocol errors during message relay due to invalid Rx message type. The total number of protocol errors during message relay as protocol state in Tx message is invalid. The total number of protocol errors during message relay as protocol state in Rx message is invalid. The total number of protocol errors during message relay as information element in Tx message is invalid. The total number of protocol errors during message relay as the information element in Rx message is invalid. The total number of RP ERROR messages sent with the cause Protocol Error in the message header. 177

180 MME-SMS Schema Short Message Service Bulk Statistics relay-prot-err-protocol-error-tx relay-prot-err-unidentified-error-tx relay-prot-err-unidentified-error-rx relay-prot-smma-rx relay-prot-data-dropped relay-prot-ack-dropped relay-prot-error-dropped relay-prot-decode-failure concat-mo-sms conn-prot-timer-expiry tr1n-timer-expiry tr2n-timer-expiry conn-prot-data-retrans relay-prot-msg-encode-fail conn-prot-data-tx-fail conn-prot-data-inval-tid conn-prot-max-retrans-reached Description The total number of protocol errors during message relay when there are protocol errors in the transmitted message. The total number of protocol errors during message relay due to unspecified error in Tx message. The total number of protocol errors during message relay due to unspecified error in Rx message. The total number RP SMMA messages received. The total number of data packets dropped during message relay. The total number of Ack messages dropped during message relay. The total number of data packets dropped during message relay due to error in connection. The total number of messages dropped during message relay due to invalid transaction ID (TID) received. The total number of concatenated mobile originated SMS messages. The total number of events when timer expired during connection setup. The total number of events when TR1N timer expired during mobile terminated SMS is in wait state for RP-ACK. The total number of events when TR2N timer expired during mobile terminated SMS is in wait state to send RP-ACK. The total number of protocol data units retransmitted during connection setup. The total number of message encoding failures during message relay. The total number of protocol data units with Tx messages failed during connection setup. The total number of protocol data units with invalid transaction ID (ID) during connection setup. The total number of events when retransmission limit is exhausted during connection setup. 178

181 Short Message Service MME-SMS Schema Bulk Statistics mt-fail-no-db-rec mt-fail-conn-prot-data-no-ack-rcvd mt-fail-fwd-busy-subs mt-fail-fwd-detached-subs mt-fail-mt-queue-full Description The total number of mobile terminated messages failed as database record is not available. The total number of mobile terminated messages failed as no acknowledgement is received during connection setup. The total number of mobile terminated messages failed due to busy subscriber. The total number of mobile terminated messages failed due to detached subscriber. The total number of mobile terminated messages failed as messaged queue was full. 179

182 MME-SMS Schema Short Message Service 180

183 CHAPTER 27 SNMP MIB Changes in StarOS 21.9 and USP 6.3 This chapter identifies SNMP MIB objects, alarms and conformance statements added to, modified for, or deprecated from the StarOS 21.9 and Ultra Services Platform (USP) 6.3 software releases. SNMP MIB Object Changes for 21.9, on page 181 SNMP MIB Alarm Changes for 21.9, on page 182 SNMP MIB Conformance Changes for 21.9, on page 183 SNMP MIB Object Changes for 6.3, on page 183 SNMP MIB Alarm Changes for 6.3, on page 184 SNMP MIB Conformance Changes for 6.3, on page 185 SNMP MIB Object Changes for 21.9 This section provides information on SNMP MIB alarm changes in release Important For more information regarding SNMP MIB alarms in this section, see the SNMP MIB Reference for this release. New SNMP MIB Object This section identifies new SNMP MIB alarms available in release The following alarms are new in this release: None in this release. Modified SNMP MIB Object This section identifies SNMP MIB alarms modified in release The following alarms have been modified in this release: None in this release. Deprecated SNMP MIB Object This section identifies SNMP MIB alarms that are no longer supported in release

184 SNMP MIB Alarm Changes for 21.9 SNMP MIB Changes in StarOS 21.9 and USP 6.3 The following alarms have been deprecated in this release: None in this release. SNMP MIB Alarm Changes for 21.9 This section provides information on SNMP MIB alarm changes in release Important For more information regarding SNMP MIB alarms in this section, see the SNMP MIB Reference for this release. New SNMP MIB Alarms This section identifies new SNMP MIB alarms available in release The following alarms are new in this release: starchassisthroughputlimit starchassisthroughputmeasured starsxpeerassociated starsxpeerassociationrelease starchassisthroughputover starchassisthroughputoverclear starchassisthroughputwarn starchassisthroughputwarnclear stariftaskbootconfigapplied Modified SNMP MIB Alarms This section identifies SNMP MIB alarms modified in release The following alarms have been modified in this release: None in this release. Deprecated SNMP MIB Alarms This section identifies SNMP MIB alarms that are no longer supported in release The following alarms have been deprecated in this release: None in this release. 182

185 SNMP MIB Changes in StarOS 21.9 and USP 6.3 SNMP MIB Conformance Changes for 21.9 SNMP MIB Conformance Changes for 21.9 This section provides information on SNMP MIB alarm changes in release Important For more information regarding SNMP MIB alarms in this section, see the SNMP MIB Reference for this release. New SNMP MIB Conformance This section identifies new SNMP MIB alarms available in release The following alarms are new in this release: None in this release. Modified SNMP MIB Conformance This section identifies SNMP MIB alarms modified in release The following alarms have been modified in this release: None in this release. Deprecated SNMP MIB Conformance This section identifies SNMP MIB alarms that are no longer supported in release The following alarms have been deprecated in this release: None in this release. SNMP MIB Object Changes for 6.3 This section provides information on SNMP MIB object changes in the Ultra M MIB corresponding to release 6.3. Important For more information regarding SNMP MIB objects in this section, see the Ultra M Solutions Guide for this release. New SNMP MIB Objects This section identifies new SNMP MIB objects available in release 6.3. The following objects are new in this release: None in this release. 183

186 SNMP MIB Alarm Changes for 6.3 SNMP MIB Changes in StarOS 21.9 and USP 6.3 Modified SNMP MIB Objects This section identifies SNMP MIB objects modified in release 6.3. The following objects have been modified in this release: None in this release. Deprecated SNMP MIB Objects This section identifies SNMP MIB objects that are no longer supported in release 6.3. The following objects have been deprecated in this release: None in this release. SNMP MIB Alarm Changes for 6.3 This section provides information on SNMP MIB alarm changes in the Ultra M MIB corresponding to release 6.3. Important For more information regarding SNMP MIB alarms in this section, see the Ultra M Solutions Guide for this release. New SNMP MIB Alarms This section identifies new SNMP MIB alarms available in release 6.3. The following alarms are new in this release: None in this release. Modified SNMP MIB Alarms This section identifies SNMP MIB alarms modified in release 6.3. The following alarms have been modified in this release: None in this release. Deprecated SNMP MIB Alarms This section identifies SNMP MIB alarms that are no longer supported in release 6.3. The following alarms have been deprecated in this release: None in this release. 184

187 SNMP MIB Changes in StarOS 21.9 and USP 6.3 SNMP MIB Conformance Changes for 6.3 SNMP MIB Conformance Changes for 6.3 This section provides information on SNMP MIB conformance statement changes in the Ultra M MIB corresponding to release 6.3. Important For more information regarding SNMP MIB conformance statements in this section, see the Ultra M Solutions Guide for this release. New SNMP MIB Conformance Statements This section identifies new SNMP MIB conformance statements available in release 6.3. The following conformance statements are new in this release: None in this release. Modified SNMP MIB Conformance Statements This section identifies SNMP MIB conformance statements that are modified in release 6.3. The following conformance statements have been modified in this release: None in this release. Deprecated SNMP MIB Conformance Statements This section identifies SNMP MIB conformance statements that are no longer supported in release 6.3. The following conformance statements have been deprecated in this release: None in this release. 185

188 SNMP MIB Conformance Changes for 6.3 SNMP MIB Changes in StarOS 21.9 and USP

189 CHAPTER 28 Support for Interim EDRs Feature Summary and Revision History, on page 187 Feature Changes, on page 188 Command Changes, on page 188 Performance Indicator Changes, on page 189 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area P-GW Applicable Platform(s) ASR 5500 SAE-GW VPC - DI VPC - SI Default Setting Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference ECS Administration Guide Statistics and Counters Reference Revision History Revision Details Release First introduced

190 Feature Changes Support for Interim EDRs Feature Changes Command Changes flow end-conditon ECS supports generation of Interim EDRs EDRs that are generated for ongoing flows based on a configurable timer. Usually, EDRs are generated for flows only when the flow terminates or when the flow reaches the configured flow idle-timeout value. These flows could have time duration that is as long as 48 hours, which makes it difficult to track subscriber activity until an EDR is generated. Thus, with interim EDRs, ongoing flow activities can be tracked by configuring an interim timeout value for a flow. On expiration of the interim timer, an EDR is generated. For configuring an interim EDR, a new condition interim is CLI configurable. Based on the configuration, the interim timer is applied to newly-created flows. On expiration of the timer, an interim EDR is generated along with the following reason: sn-closure-reason (23). The information volume available until the expiration of the timer is populated in the EDR along with its respective timestamps. The Interim EDR functionality is license controlled. 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. In the ACS Rulebase Configuration mode, the flow end-condition command supports the interim condition is supported On configuring this condition, the interim timer is initiated for newly-created flows. An interim EDR is generated on expiration of the timer. Use the following configuration to enable generation of interim EDRs: configure require active-charging active-charging ervice service_name rulebase rulebase_name flow end-condition interim interim_timer_value charging-edr charging_edr_format_name end NOTES: flow: Specifies a flow related to the user session. end-condition: Specifies the end condition of the flow related to a user session that triggers EDR generation. interim: This condition specifies the interim threshold condition of the flow where an EDR is generated based on the configured timer value. The interim_timer_value is configured in minutes with a configurable range from 15 to 1440 minutes. 188

191 Support for Interim EDRs Performance Indicator Changes charging-edr: Specifies the charging EDR format that is used to generate the EDRs. charging_edr_format_name must be the name of a charging EDR format, and must be an alphanumeric string of 1 through 63 characters. The interim keyword is only applicable for new flows created and not on existing flows. Performance Indicator Changes show active-charging rulebase statistics name name The output of this command includes the following Interim EDR related fields: EDRs generated for interim Interval 189

192 show active-charging rulebase statistics name name Support for Interim EDRs 190

193 CHAPTER 29 Triggering Iu Release Command Procedure This chapter describes the following topics: Feature Summary and Revision History, on page 191 Feature Description, on page 192 Configuring RAB Messages with Cause 46, on page 193 Monitoring and Troubleshooting, on page 194 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) SGSN ASR 5500 VPC-DI VPC-SI Feature Default Disabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference SGSN Administration Guide Statistics and Counters Reference Revision History Important Revision history details are not provided for features introduced before releases 21.2 and N

194 Feature Description Triggering Iu Release Command Procedure Revision Details SGSN triggers the Iu Release procedure when it receives: RAB Release Request with cause 46 "Radio Connection With UE Lost". Release 21.8 RAB Assignment Response with cause 46 "Radio Connection With UE Lost". This feature is available in and 21.9 releases. First introduced. Pre 21.2 Feature Description SGSN triggers the Iu Release Command procedure to RNC when it receives the RAB Release Request with cause 46 "Radio Connection With UE Lost" and the RAB Assignment Response with cause 46 "Radio Connection With UE Lost". Support for RAB Release Request with cause 46 In releases prior to 21.8: When SGSN receives the RAB Release Request with cause "Radio Connection With UE Lost" from RNC, it responds with the same cause code in RAB Assignment Request (cause RAB Release). RNC then sends the RAB Assignment Response with cause RAB Release followed by Iu Release Command with cause "No Remaining RAB" to SGSN. In 21.8 and later releases: When SGSN receives the RAB Release Request with cause "Radio Connection With UE Lost" from RNC, it triggers the Iu Release Command with cause "Normal Release". RNC then sends the Iu Release Complete message to SGSN. The Iu release procedure is handled through the ranap rabrel-with-radiolost CLI command configured in the RNC Configuration mode. SGSN proceeds with the following steps when it receives the RAB Release Request with cause "Radio Connection With UE Lost": SGSN verifies if the ranap rabrel-with-radiolost CLI command is enabled. If the ranap rabrel-with-radiolost CLI command is enabled, then SGSN triggers the Iu Release command towards the RNC to release the Iu connection for that specific UE. Support for RAB Assignment Response with cause 46 In releases prior to 21.8: When RNC sends the RAB Assignment Response with cause "Radio Connection With UE Lost", SGSN sends the RAB Assignment Request with the cause "Radio Connection With UE Lost". Multiple retries are done before RNC sends the Iu Release Request message. In 21.8 and later releases: When RNC sends the RAB Assignment Response with cause "Radio Connection With UE Lost", SGSN sends the Iu Release Command immediately and there are no RAB Assignment Request retries. The Iu release procedure is handled through the ranap rab-arsp-ue-radio-lost CLI command configured in the RNC Configuration mode. 192

195 Triggering Iu Release Command Procedure Configuring RAB Messages with Cause 46 SGSN proceeds with the following steps when it receives the RAB Assignment Response with cause "Radio Connection With UE Lost": SGSN verifies if the ranap rab-arsp-ue-radio-lost CLI command is enabled. If the ranap rab-arsp-ue-radio-lost CLI command is enabled, then SGSN triggers the Iu Release Command towards the RNC to release the Iu connection for that specific UE. Configuring RAB Messages with Cause 46 This section describes how to trigger the Iu Release Command procedure with cause 46 "Radio Connection With UE Lost". Configuring RAB Assignment Response Use the following configuration to enable or disable handling of the RAB Assignment Response with cause 46 (Radio Connection With UE Lost). SGSN sends the Iu Release Command with normal cause to RNC when it receives the RAB Assignment Response with cause 46. configure context context_name iups-service service_name rnc id rnc_id [ no ] ranap rab-arsp-ue-radio-lost end NOTES: iups-service service_name: Creates an IuPS service instance and enters the IuPS Service Configuration mode. This mode defines the configuration and usage of IuPS interfaces between the SGSN and the RNCs in the UMTS radio access network (UTRAN). service_name specifies the IuPS service name as a unique alphanumeric string of 1 through 63 characters. rnc id rnc_id: Sets the identification number of the RNC configuration instance. rnc_id must be an integer from 0 to When no ranap rab-arsp-ue-radio-lost is configured, SGSN will send the RAB Assignment Request with RAB Release to RNC. This command applies to Gn-SGSN only. This command is disabled by default. Configuring RAB Release Request Use the following configuration to enable or disable handling of the RAB Release Request with cause 46 (Radio Connection With UE Lost). SGSN sends the Iu Release Command to RNC when it receives the RAB Release Request with cause 46. configure context context_name 193

196 Monitoring and Troubleshooting Triggering Iu Release Command Procedure NOTES: iups-service service_name rnc id rnc_id [ no ] ranap rab-release-with-radiolost end iups-service service_name: Creates an IuPS service instance and enters the IuPS Service Configuration mode. This mode defines the configuration and usage of IuPS interfaces between the SGSN and the RNCs in the UMTS radio access network (UTRAN). service_name specifies the IuPS service name as a unique alphanumeric string of 1 through 63 characters. rnc id rnc_id: Sets the identification number of the RNC configuration instance. rnc_id must be an integer from 0 to When no ranap rab-release-with-radiolost is configured, SGSN will send the RAB Assignment Request with RAB Release to RNC. This command applies to Gn-SGSN only. This command is disabled by default. Monitoring and Troubleshooting This section provides information regarding show commands and bulk statistics available to monitor and troubleshoot this feature. Show Commands and Outputs show iups-service all The output of this command includes the following fields: Rab release with Radio lost Indicates whether RAB Release Request with cause 46 "Radio Connection With UE Lost" is enabled or disabled. Rab assignment response with UE Radio lost Indicates whether RAB Assignment Response with cause 46 "Radio Connection With UE Lost" is enabled or disabled. Bulk Statistics The following bulk statistics are available in the SGSN schema. Iu-release-command-with-radio-lost-ue Total number of Iu interface release commands due to RAB Release Request with radio lost received. Iu-release-command-rab-ass-rsp-with-radio-lost-ue Total number of Iu interface release commands due to RAB Assignment Response with radio lost received. 194

197 CHAPTER 30 Dual UEM Model for Redundancy Feature Summary and Revision History, on page 195 Feature Changes, on page 195 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Enabled - Configuration required Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide Revision History Revision Details Release First introduced. 6.3 Feature Changes In the earlier implementation, UEM leveraged Apache Zookeeper for redundancy. Zookeeper required three VMs for UEM redundancy: 1 leader or master (active), 1 follower or slave (standby), and 1 follower (standby). When UEM is deployed for use within the Ultra M solution, it is automatically brought up with redundancy. 195

198 Feature Changes Dual UEM Model for Redundancy In this release, changes are made to the UEM redundancy model in order to optimize the VM requirements. A minimum of two UEM VMs is sufficient to support redundancy. When deployed in HA cluster, two UEM VMs are deployed: one active, one standby. The master UEM has two zookeeper instances running, both instances have their own IP, ID, PID, log/data directory and configuration files. The slave UEM also has one zookeeper running, thus meeting three zookeeper instance requirements. The UEM leverages keepalived for master/slave selection. It quickly detects and performs switchover in case of a failure of the active/standby instance. With this release, the UEM services will no longer run on the slave UEM to simplify troubleshooting, maintenance, and synchronization related issues. The number of instances for UEM can be defined as 2 or 3 through the VNFC configuration within NSD. You can decide the instance number based on the resource availability and deployment requirements. To configure the number of instances for UEM, use the following parameter for VNFC EM: number-of-instances <instance_num> Note that the number-of-instances parameter is mandatory. This parameter allows the user to configure either 2 or 3 UEM instances. In releases prior to 6.3, the default value was 3 and this parameter was not user configurable. In release 6.3 and beyond, the default value is 2. Example Configuration for AutoDeploy: nsd nsd-autovnf vnfd vpc vnfc em number-of-instances 2... For more information on the APIs, see the Cisco Ultra Services Platform NETCONF API Guide. For more information on this feature, see the Cisco Ultra Services Platform Deployment Automation Guide. 196

199 CHAPTER 31 UEM Patch Upgrade Process Feature Summary and Revision History, on page 197 Feature Changes, on page 198 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Disabled - Configuration required Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide Revision History Revision Details Release Though this feature was introduced in 6.2, it was not fully qualified. It is now fully 6.3 qualified as of this release. First introduced

200 Feature Changes UEM Patch Upgrade Process Feature Changes Though introduced in 6.2, this feature was not fully qualified in that release. It was made available only for testing purposes. In 6.3, this feature has been fully qualified for use in the appropriate deployment scenarios. Refer to the Ultra Services Platform Deployment Automation Guide for more information. 198

201 CHAPTER 32 Unique IP Identification for Fragmented IPv6 Packets Feature Summary and Revision History, on page 199 Feature Changes, on page 200 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area P-GW GGSN Applicable Platform(s) Default Setting Related Changes in This Release Related Documentation ASR 5500 Enabled - Always-on Not Applicable Not Applicable Revision History Revision Details With this release, fragmented IPv6 packets that are sent over the Gn interface use unique IP identification value. First introduced. Release Pre

202 Feature Changes Unique IP Identification for Fragmented IPv6 Packets Feature Changes Previous Behavior: In releases earlier than , for fragmented downlink NAT64 packets, the IP identification field of IP header was copied from IPv4 packet that was received on Gi interface to the IPv6 packet that was sent on the Gn interface. New Behavior: In and later releases, for fragmented downlink NAT64 packets, the IP identification field of IP header is generated on the gateway. With this release, fragmented IPv6 packets that are sent over the Gn interface use unique IP identification value. Customer Impact: None 200

203 CHAPTER 33 USP Software Version Updates Feature Summary and Revision History, on page 201 Feature Changes, on page 202 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area All Applicable Platform(s) UGP Feature Default Disabled - Configuration Required Related Features in this Release Not Applicable Related Documentation Ultra Gateway Platform System Administration Guide Ultra M Solutions Guide Ultra Services Platform Deployment Automation Guide Cisco Ultra Services Platform NETCONF API Guide Revision History Revision Details Release First introduced

204 Feature Changes USP Software Version Updates Feature Changes Cisco ESC Software Version Update The Cisco Elastic Services Controller (ESC) product is used as the virtual network function manager (VNFM) within the Ultra Services Platform. The supported ESC version in this release has been updated from to 4.2. This is the default ESC version included as part of the USP 6.3 release package and must be installed before using it. RedHat Software Version Update This release includes support for RedHat version 7.5. The RedHat 7.5 has been validated and is recommended for use with all Ultra M deployments based on OSP 10 and that leverage the Hyper-Converged architecture. Cisco UCS C240 M4S Software Version Updates The Cisco UCS C240 M4S server is used within the Ultra M solution. The following software/firmware versions have been validated and recommended for use with this release: CIMC: 3.0(4d) System BIOS: C240M a

205 CHAPTER 34 UTRAN to E-UTRAN Handover This chapter describes the following topics: Feature Summary and Revision History, on page 203 Feature Description, on page 204 Configuring UTRAN to E-UTRAN Handover, on page 204 Monitoring and Troubleshooting, on page 205 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Applicable Platform(s) SGSN (S4-SGSN) ASR 5000 ASR 5500 VPC-DI VPC-SI Feature Default Enabled - Configuration Required Related Changes in This Release Not Applicable Related Documentation Command Line Interface Reference SGSN Administration Guide Statistics and Counters Reference Revision History Revision Details Release 203

206 Feature Description UTRAN to E-UTRAN Handover First introduced. This feature is available in and 21.9 releases Feature Description The UTRAN to E-UTRAN Handover feature is used to check and avoid including the RAB IDs in the "Relocation Command" message. When this feature is enabled, the SGSN includes the RAB IDs in the "RABs To Be Released List" IE in the "Relocation Command" message if the MME does not include the F-TEID information in the "Forward Relocation Response" message (existing behavior). When this feature is disabled, the SGSN will not include the following IEs in the "Relocation Command" message if the MME does not include the F-TEID information. RABs Subject To Data Forwarding List RABs To Be Released List Configuring UTRAN to E-UTRAN Handover This section describes how to configure UTRAN to E-UTRAN Handover feature. Configuring enodeb Data Forwarding Use the following configuration to configure enable forwarding of data from the RNC to enodeb. configure context context_name iups-service service_name rnc id rnc_id [ no ] enb-data-forward end NOTES: iups-service service_name: Creates an IuPS service instance and enters the IuPS Service Configuration mode. This mode defines the configuration and usage of IuPS interfaces between the SGSN and the RNCs in the UMTS radio access network (UTRAN). service_name specifies the IuPS service name as a unique alphanumeric string of 1 through 63 characters. rnc id rnc_id: Sets the identification number of the RNC configuration instance. rnc_id must be an integer from 0 to enb-data-forward: Enables the forwarding of data from this RNC to enodeb. no: Disables the forwarding of data from this RNC to enodeb. This command is enabled by default. 204

207 UTRAN to E-UTRAN Handover Monitoring and Troubleshooting Monitoring and Troubleshooting This section provides information on show commands and their corresponding outputs for the UTRAN to E-UTRAN Handover feature. Show Commands and Outputs show iups-service all The output of this command includes the "E-NodeB Data Forwarding" field to indicate whether enodeb Data Forwarding support is enabled or disabled. 205

208 Show Commands and Outputs UTRAN to E-UTRAN Handover 206

209 CHAPTER 35 X-Header Insertion and Encryption Feature Summary and Revision History, on page 207 Feature Description, on page 208 Supported Encryption Methods, on page 213 How It Works, on page 214 Configuring X-Header Insertion and Encryption, on page 215 Monitoring and Troubleshooting the X-Header Insertion and Encryption feature, on page 218 Feature Summary and Revision History Table 1: Summary Data Applicable Products and Functional Area P-GW SAEGW Applicable Platforms ASR 5500 VPC - DI VPC - SI Feature Default Disabled - License Required Related Changes in This Release Not applicable Related Documentation Command Line Interface Reference ECS Administration Guide Statistics and Counters Reference Revision History Important Revision history details are not provided for features introduced before releases 21.2 and N

210 Feature Description X-Header Insertion and Encryption Revision Details In this release, the TLS_RSA_WITH_AES_256_GCM_SHA_384 algorithm is introduced for enhanced security. First introduced. Details 21.9 Pre 21.2 Feature Description The X-Header Insertion and X-Header Encryption features, collectively known as Header Enrichment, enables to append headers to HTTP/WSP GET and POST request packets, and HTTP Response packets for use by end applications, such as mobile advertisement insertion (MSISDN, IMSI, IP address, user-customizable, and so on). Important In this release, the X-Header Insertion and Encryption features are supported only on the GGSN and P-GW. Following are the software requirements for the new TLS_RSA_WITH_AES_256_GCM_SHA_384 attribute in CDR: Configure AES-256-GCM-sha384 encryption algorithm with 256-bit keys. This configuration is same as the one used for the RC4MD5 encryption. Use the existing re-encryption timeout CLI, which is used at rulebase level, for re-encryption. For AES-GCM encryption, use the optional salt flag. This flag is used to randomize the keys, which are generated from the passphrase, and the Initialization Vectors (IV). License Requirements X-Header Insertion X-Header Insertion and X-Header Encryption are both licensed Cisco features. A separate feature license may be required. 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. This section provides an overview of the X-Header Insertion feature. Extension header (x-header) fields are the fields not defined in RFCs or standards but can be added to headers of protocol for specific purposes. The x-header mechanism allows additional entity-header fields to be defined without changing the protocol, but these fields cannot be assumed to be recognizable by the recipient. Unrecognized header fields should be ignored by the recipient and must be forwarded by transparent proxies. The X-Header Insertion feature enables inserting x-headers in HTTP/WSP GET and POST request packets and HTTP response packets. Operators wanting to insert x-headers in HTTP/WSP request and HTTP response packets, can configure rules for it. The charging-action associated with the rules will contain the list of x-headers to be inserted in the packets. 208

211 X-Header Insertion and Encryption X-Header Encryption For example, if you want to insert the field x-rat-type in the HTTP header with a value of rat-type, the header inserted should be: x-rat-type: geran X-Header Encryption where, rat-type is geran for the current packet. This section provides an overview of the X-Header Encryption feature. X-Header Encryption enhances the X-header Insertion feature to increase the number of fields that can be inserted, and also enables encrypting the fields before inserting them. If x-header insertion has already happened for an IP flow (because of any x-header format), and if the current charging-action has the first-request-only flag set, x-header insertion will not happen for that format. If the first-request-only flag is not set in a charging-action, then for that x-header format, insertion will continue happening in any further suitable packets in that IP flow. Changes to x-header format configuration will not trigger re-encryption for existing calls. The changed configuration will however, be applicable for new calls. The changed configuration will also apply at the next re-encryption time to those existing calls for which re-encryption timeout is specified. If encryption is enabled for a parameter while data is flowing, since its encrypted value will not be available, insertion of that parameter will stop. Important Recovery of flows is not supported for this feature. TCP OOO Packets ECS handles TCP OOO packets in two ways depending on the rulebase configuration: Transmit Immediately: If the rulebase is configured to transmit immediately for TCP OOO packets, the OOO packets will be forwarded immediately, and a copy of this packet will be added to the OOO queue for analysis. Transmit After Reordering: If the rulebase is configured to transmit after reordering for TCP OOO packets, the OOO packets will be added to the OOO queue for analysis. Header insertion on OOO request packets occurs on reordering packets that are received before the OOO request timeout. When a reordering packet is received, the queued packets are forwarded. However, if a reordering packet is not received before the OOO queue timeout, the queued packet will be forwarded without any analysis done to those packets. Important When TCP OOO processing has been configured in the rulebase, a session manager crash might be observed due to overlapping TCP segments and/or reordering packet arriving within TCP OOO configured timeout value or default value (5 sec). This issue can be resolved by changing the rulebase configuration for TCP OOO packets from transmit after-reordering to transmit immediately. In 20 and later releases, TCP OOO packets will be buffered for HTTP traffic until the header enrichment is completed. The header enrichment is supported on either first request packet or all request packets, response packets, or on both. So following packets after the header enrichment is complete will not require buffering of OOO packets and the packets can be transmitted immediately. This will improve memory optimization 209

212 IP Fragmented Packets X-Header Insertion and Encryption and network performance. The out-of-order packets will be buffered as per the x-header configuration in any of the charging-action for the subscriber's rulebase. If x-header insertion is only for the request packet, then out-of-order buffering will be supported till the header completion of the request packet. If x-header insertion is only for the response packet, then out-of-order buffering will be supported till the header completion of the response packet. If x-header insertion is for both request and response packets, then out-of-order buffering will be supported till the completion of HTTP headers for that packet. Limitations of buffering TCP OOO packets: This enhancement will be supported only for HTTP flows of x-header enrichment feature. In case of pipeline flows with multiple transactions, if a new OOO request/response is received while the previous request/response is still going on, then x-header insertion will not work for the new request/response of that flow. IP Fragmented Packets ECS can perform Header Enrichment to IP fragmented packets when all the fragments are received before the reassembly timeout. If the packet size after Header Enrichment exceeds the MSS of the session, the reassembled packet gets segmented, the multiple segments are forwarded. Limitations to the Header Insertion and Encryption Features This section lists known limitations to insertion and encryption of x-header fields in HTTP/WSP request and HTTP response packets. The following are limitations to insertion and encryption of x-header fields in HTTP headers. Limitations in StarOS 14.0 and later releases: Header insertion does not occur for packets with incomplete HTTP headers. If a flow has x-header insertion and later some IP fragments are received for which reassembly fails, sequence space of that segment will be mismatched. ECS does not support applying more than one modifying action on an inbound packet before sending it on the outbound interface. For example, if header insertion is applied on a packet, then the same packet is not allowed to be modified for NAT/ALG and MSS insertion. Header enrichment works only for the first request of a packet with concatenated requests, when the packets are buffered at DCCA. There are no limitations on header enrichment for single GET or pipelined GET requests. Header enrichment works for packets at DCCA only when the packets pending of header insertion is buffered. Receive window will not be considered during header enrichment. That is, after header enrichment if packet exceeds receive window, ECS will not truncate the packet. The maximum bytes per request after header enrichment is 2400 bytes. If concatenated requests exist, a maximum of 2400 bytes after header enrichment can be inserted. 210

213 X-Header Insertion and Encryption Limitations to the Header Insertion and Encryption Features If due to header insertion, the packet size exceeds this limit, the behavior is unpredictable. Only those x-header fields in header portion of application protocol that begin with "x-" are parsed at HTTP analyzer. In URL and data portion of HTTP any field can be parsed. EDR generation for x-header fields in Response packets will not be supported. Limitations in StarOS 12.3 and earlier releases: The packet size is assumed to be less than "Internal MED MTU size, the size of header fields inserted". If the total length of packet exceeds the internal MTU size, header insertion will not occur after the addition of fields. Header insertion occurs for both HTTP GET and POST requests. However, for POST requests, the resulting packet size will likely be larger than for GET requests due to the message body contained in the request. If the previous limitation applies, then POST request will suffer a bigger limit due to this. Header insertion does not occur for retransmitted packets. Header insertion does not occur for packets with incomplete HTTP headers. Header insertion does not occur for TCP OOO and IP fragmented packets. If a flow has x-header insertion and later some IP fragments are received for which reassembly fails, sequence space of that segment will be mismatched. ECS does not support applying more than one modifying action on an inbound packet before sending it on the outbound interface. For example, if header insertion is applied on a packet, then the same packet is not allowed to be modified for NAT/ALG and MSS insertion. If a packet is buffered by ICAP, header insertion will not occur for that packet. Receive window will not be considered during header enrichment. That is, after header enrichment if packet exceeds receive window, ECS will not truncate the packet. Packet size limit is 2400 bytes, if due to header insertion packet size exceeds this limit, behavior is unpredictable. Only those x-header fields in header portion of application protocol that begin with "x-" are parsed at HTTP analyzer. In URL and data portion of HTTP any field can be parsed. The following are limitations to insertion and encryption of x-header fields in WSP headers: x-header fields are not inserted in IP fragmented packets. In case of concatenated request, x-header fields are only inserted in first GET or POST request (if rule matches for the same). X-header fields are not inserted in the second or later GET/POST requests in the concatenated requests. For example, if there is ACK+GET in packet, x-header is inserted in the GET packet. However, if GET1+GET2 is present in the packet and rule matches for GET2 and not GET1 x-header is still inserted in GET2. In case of GET+POST also, x-header is not inserted in POST. In case of CO, x-header fields are not inserted if the WTP packets are received out of order (even after proper re-ordering). If route to MMS is present, x-headers are not inserted. 211

214 Supported X-Headers X-Header Insertion and Encryption x-headers are not inserted in WSP POST packet when header is segmented. This is because POST contains header length field which needs to be modified after addition of x-headers. In segmented WSP headers, header length field may be present in one packet and header may complete in another packet. x-headers are not inserted in case of packets buffered at DCCA. Supported X-Headers This section provides information on the different x-headers supported by ECS. ECS supports insertion of various x-header fields in the HTTP/WSP GET and POST request packets and HTTP response packets. The x-headers are inserted at the end of the HTTP/WSP header. The following bearer-related x-headers are supported: 3gpp The following 3GPP associated fields are supported: apn charging-characteristics charging-id imei imsi qos rat-type s-mcc-mnc sgsn-address acr customer-id ggsn-address mdn msisdn-no-cc radius-string radius-calling-station-id session-id sn-rulebase subscriber-ip-address username user-profile uli The following HTTP-related x-headers are supported: host url In addition, ECS also allows string constants to be inserted as an x-header. For more information on configuring the x-header formats, see the insert command section in the ACS x-header Format Configuration Mode Commands chapter of the Command Line Interface Reference. 212

215 X-Header Insertion and Encryption X-Header Enrichment Anti-Spoofing X-Header Enrichment Anti-Spoofing This section provides an overview of the x-header Enrichment Anti-Spoofing feature. The Header Enrichment feature allows operators to encrypt and insert subscriber-specific fields as x-headers in to the HTTP headers of URL requests. However, this might leave the header open to spoofing by malicious external devices. The Anti-Spoofing feature enables deletion and modification of the existing x-header fields to protect the operators and subscribers from spoofing, and provides a fraud detection mechanism when an external portal is used for a subscriber or content authorization. The feature detects and removes user-generated HTTP headers if the header name is similar to the header name used in the x-header format, and when multiple entries of the same field exist in the header, all the similar entries are removed and one with a modified value is inserted at the end of the HTTP header. When anti-spoofing is enabled, and if the HTTP header in the GET or POST request spawns across more than one packet, the packets with incomplete HTTP header will be buffered. The buffered packets are sent out once the HTTP header is completed. The Anti-Spoofing feature is disabled by default and can be enabled/disabled at a field level in the CLI. Limitations to the Anti-Spoofing Feature Header enrichment does not occur if a route to the MMS analyzer exist in the rulebase. Header enrichment works only for the first request of a packet with concatenated requests, when the packets are buffered at DCCA. If a packet is buffered by ICAP, header insertion will not occur for that packet. ECS will not be able to perform header enrichment when all fragments are not received before reassembly timeout in the case of IP fragments packets. ECS does not perform more than one flow action which modifies the inbound packet before sending it on the outbound interface. If the HTTP GET or POST header is not completed in three packets, anti-spoofing will occur only for the last packet in which the header completes, as buffering supported only up to a maximum of two packets. Though insertion of fields is allowed without having "x-" in the field name, extension header fields that do not start with "x-" are not deleted. The anti-spoofing feature will not be supported for x-headers inserted in Response messages. Supported Encryption Methods In Release 21.9, the TLS_RSA_WITH_AES_256_GCM_SHA_384 algorithm is introduced for enhanced security. The supported types of encryption for encrypting x-header values are RSA, RC4MD5, and AES-256-GCM-SHA384. These encryption types are explained in the following sections. 213

216 RSA X-Header Insertion and Encryption RSA You can configure RSA encryption by using an encryption certificate. With this encryption, during a call, the configured fields of the xheader-format command are encrypted. When the charging action is hit for the traffic, then the encrypted values of the configured fields are inserted in the HTTP header. Important The encrypted values change only if the re-encryption timer times out. As RSA encryption consumes time, it is not used each time a field value changes during a call. RC4MD5 You can configure RC4MD5 encryption at charging action level. For traffic, an encryption that is configured at a charging level takes precedence over rulebase. In RC4MD5 encryption, the MD5 hash of the key, which is a 128-bit value, is used to encrypt the value using the RC4 encryption. The base 64 value of the value that is received from the RC4 encryption is then inserted in the x-header. When the charging action is hit for the traffic, then the encrypted values of the configured fields are inserted in the HTTP header. AES-256-GCM-SHA384 You can configure AES-256-GCM-SHA384 encryption at charging action level. For traffic, an encryption that is configured at a charging action level takes precedence over rulebase. In AES-256-GCM-SHA384 encryption, the SHA384 hash of the key, which is 384 bits value, is used to encrypt the value using the AES-GCM algorithm. The base 64 of this encrypted value is then inserted in the x-header. How It Works This section describes the steps involved to configure the X-Header Insertion and X-Header Encryption features. X-Header Insertion The following steps describe how X-Header Insertion works: Step 1 Step 2 Step 3 Step 4 Creating/configuring a ruledef to identify the HTTP/WSP packets in which the x-headers must be inserted. Creating/configuring a rulebase and configuring the charging-action, which will insert the x-header fields into the HTTP/WSP packets. Creating/configuring the x-header format. Configuring insertion of the x-header fields based on the message type in the charging action. 214

217 X-Header Insertion and Encryption X-Header Encryption X-Header Encryption The following steps describe how X-Header Encryption works: Step 1 Step 2 Step 3 Step 4 X-header insertion, encryption, and the encryption certificate is configured in the CLI. When the call gets connected, and after each regeneration time, the encryption certificate is used to encrypt the strings. When a packet hits a ruledef that has x-header format configured in its charging-action, x-header insertion into that packet is done using the given x-header-format. If x-header-insertion is to be done for fields which are marked as encrypt, the previously encrypted value is populated for that field accordingly. Configuring X-Header Insertion and Encryption This section describes how to configure the X-Header Insertion and Encryption features, collectively known as Header Enrichment. Configuring X-Header Insertion This section describes how to configure the X-Header Insertion feature. Important This feature is license dependent. Please contact your Cisco account representative for more information. To configure the X-Header Insertion feature: Step 1 Step 2 Create/configure a ruledef to identify the HTTP packets in which the x-headers must be inserted. For information on how to create/configure ruledefs, see the Configuring Rule Definitions section in the Enhanced Charging Service Configuration chapter. Create/configure a rulebase and configure the charging-action, which will insert the x-header fields into the HTTP packets. For information on how to create/configure rulebases, see the Configuring Rulebase section in the Enhanced Charging Service Configuration chapter. Step 3 Create the x-header format as described in Creating the X-Header Format, on page 215. Step 4 Configure the x-header format as described in Configuring the X-Header Format, on page 216. Step 5 Configure insertion of the x-header fields as described in Configuring Charging Action for Insertion of X-Header Fields, on page 216. Creating the X-Header Format To create an x-header format, use the following configuration: configure active-charging service ecs_service_name 215

218 Configuring the X-Header Format X-Header Insertion and Encryption Configuring the X-Header Format xheader-format xheader_format_name end To configure an x-header format, use the following configuration: configure active-charging service ecs_service_name xheader-format xheader_format_name insert xheader_field_name { string-constant xheader_field_value variable { bearer { 3gpp { apn charging-characteristics charging-id imei imsi qos rat-type s-mcc-mnc sgsn-address } acr customer-id ggsn-address mdn msisdn-no-cc radius-string radius-calling-station-id session-id sn-rulebase subscriber-ip-address username } [ encrypt ] http { host url } } end Configuring Charging Action for Insertion of X-Header Fields To configure a charging action for insertion of x-header fields, use the following configuration: configure active-charging service ecs_service_name charging-action charging_action_name xheader-insert xheader-format xheader_format_name [ encryption { rc4md5 aes-256-gcm-sha384 [ salt ] } [ encrypted ] key key ] [ first-request-only ] [ msg-type { response-only request-and-response } ] [ -noconfirm ] end Note If rc4md5 encryption is configured in the charging action, it will take precedence over RSA certificate based encryption for flows hitting particular charging action. X-header insertion in HTTP Response packets can be enabled/disabled using the msg-type keyword. response-only: When configured in charging-action, x-header will be inserted in HTTP Response packets with specified x-header format. request-and-response: When configured in charging-action, x-header will be inserted in both HTTP Request and Response packets with same x-header format. Configuring X-Header Encryption This section describes how to configure the X-Header Encryption feature. Important This feature is license dependent. Please contact your Cisco account representative for more information. 216