This section describes the external interfaces required to support the 5G NSA architecture.

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 4294967295 bits per second, the "Max-Requested-Bandwidth-UL" AVP (or DL) must be set to the upper limit 4294967295 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.

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.

• Maximum of 11 reports can be sent in single GTPV2 message towards S-GW.

• Reports sent without handover flag during handover procedure will be dropped by MME.

• Reports are not stored as part of session recovery.

• At any point of time only two reports per bearer will be handled by MME.

• Filling of “Secondary RAT Data Usage Request” IE in E-RAB MODIFY REQUEST message and handling of report in ERAB Modify RESPONSE is not supported.

• During 4g to 3g/2g IRAT handover without S-GW change, if PGW reporting is enabled, reports will be sent over the Change Notification message. Reports will not be sent to S-GW, even if the S-GW reporting is configured.

This section describes the call flow procedures related to MME for 5G NSA.

Cisco's implementation of the 5G NSA feature complies with the following standards:

• 3GPP 23.003 Release 15.2.0 - Numbering, addressing and identification.

• 3GPP 23.401 Release 15.2.0 - General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

• 3GPP 29.272 Release 15.2.0 - Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol

• 3GPP 29.274 Release 15.2.0 - 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3

• 3GPP 29.303 Release 15.2.0 - Domain Name System Procedures

Cisco's implementation of the Secondary RAT Usage Reporting complies with the following standards:

• 3GPP 29.274: 15.5.0 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunneling Protocol for Control plane (GTPv2-C) Stage 3

• 3GPP 36.413: 15.3.0 Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)

• 3GPP 23.401: 15.5.0 General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

Use the following configuration to enable 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, name must be an string from 1 to 63 characters.

• no : Disables the DCNR configuration.

• The dcnr CLI command is disabled by default.

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, it must be an string from 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.

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 profile_name  
      qos apn-ambr max-ul mbr_up max-dl mbr_down 
      remove qos apn-ambr 
      end 

NOTES:

• apn-profile profile_name : Creates an instance of an access point name (APN) profile. 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.

• 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 4000000000000 (4 Tbps).

• max-dl mbr_down : Defines the maximum bit rates for downlink traffic. mbr_up must be an integer from 1 to 4000000000000 (4 Tbps).

• remove : Removes the APN AMBR changes from the configuration for this APN profile.

Use the following configuration to enable Secondary RAT Data Usage Report to support 5G NSA.

configure  
      call-control-profile profile_name 
         secondary-rat data-usage-report { pgw [ sgw ] | sgw [ pgw ] } 
         [ no | remove ] secondary-rat data-usage-report 
         end 

Important

Both CLI configuration and the current running procedure are taken into account while filling the flags IRSGW/IRPGW in GTPv2 messages towards S-GW/P-GW.

NOTES:

• no : Disables the Secondary RAT Usage Report at call-control-profile.

• remove : Removes the Secondary-RAT Usage Report configuration from call-control-profile. It fallbacks to MME service-level configuration.

• secondary-rat data-usage-report { pgw [ sgw ] | sgw [ pgw ] } MME sets IR-SGW and IR-PGW flags based on the available options configured for Secondary-RAT data usage report. By default, MME disables the Secondary-RAT data usage reporting towards both SGW and PGW. If the configuration is removed from call-control-profile, then it fall-back to MME-SERVICE level configuration for Secondary-RAT-Data-Usage-Report functionality.

  • secondary-rat data-usage-report sgw Disables the Secondary-RAT Usage Report option for P-GW and enables only for S-GW.

  • secondary-rat data-usage-report pgw Disables the Secondary-RAT Usage Report option for SGW and enables only for PGW.

  • secondary-rat data-usage-report sgw pgw Enables Secondary-RAT Usage Report option for both SGW and PGW.

  • secondary-rat data-usage-report pgw sgw Enables Secondary-RAT Usage Report option for both SGW and PGW.

Use the following configuration to enable Secondary RAT Data Usage Report to support 5G NSA.

configure  
   context context_name  
      mme-service service_name 
         secondary-rat data-usage-report { pgw [ sgw ] | sgw [ pgw ] } 
         no secondary-rat data-usage-report 
         end 

Important

Both CLI configuration and the current running procedure are taken into account while filling the flags IRSGW/IRPGW in GTPv2 messages towards S-GW/P-GW.

NOTES:

• no : Disables the Secondary RAT Usage Report at mme-service.

• secondary-rat data-usage-report { pgw [ sgw ] | sgw [ pgw ] } MME sets IR-SGW and IR-PGW flags based on the available options configured for Secondary-RAT data usage report. By default, MME disables the Secondary-RAT data usage reporting towards both SGW and PGW. If the configuration is removed from call-control-profile, then it fall-back to MME-SERVICE level configuration for Secondary-RAT-Data-Usage-Report functionality.

  • secondary-rat data-usage-report sgw : Disables the Secondary-RAT Usage Report option for P-GW and enables only for S-GW.

  • secondary-rat data-usage-report pgw : Disables the Secondary-RAT Usage Report option for S-GW and enables only for P-GW.

  • secondary-rat data-usage-report sgw pgw : Enables Secondary-RAT Usage Report option for both S-GW and P-GW.

  • secondary-rat data-usage-report pgw sgw : Enables Secondary-RAT Usage Report option for both S-GW and P-GW.

Use the following configuration to configure mapping of EPC QOS (non-standard QCIs) to 3GPP Pre-Release 8 QOS.

configure  
   bearer-control-profile profile_name  
      pre-rel8-qos-mapping qci qci_val 
      remove pre-rel8-qos-mapping qci 
      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.

• remove : Removes the DCNR configuration from the call control profile.

• 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.

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 4000000000000 (4 Tbps).

• max-dl mbr_down : Defines the maximum bit rate for downlink traffic. mbr_down must be an integer from 1 to 4000000000000 (4 Tbps).

• remove : Deletes the dedicated bearer MBR changes from the configuration for this APN profile.

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 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 string from 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 4000000000000 (4 Tbps).

• gbr-down gbr_down : Defines the guaranteed bit rate for downlink traffic. gbr_down must be an integer from 1 to 4000000000000 (4 Tbps).

• mbr-up mbr_up : Defines the maximum bit rate for uplink traffic. mbr_up must be an integer from 1 to 4000000000000 (4 Tbps).

• mbr-down mbr_down : Defines the maximum bit rate for downlink traffic. mbr_down must be an integer from 1 to 4000000000000 (4 Tbps).

• remove : Deletes the dedicated bearer MBR changes from the configuration for this bearer control profile.

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 4000000000000 (4 Tbps).

• max-dl mbr_down : Defines the maximum bit rate for uplink traffic. mbr_down must be an integer from 1 to 4000000000000 (4 Tbps).

• remove : Deletes the configuration from the call control profile.

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.

  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:

  • 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: MME chooses S-GW/P-GW that support both +ue and +nr services. If step 1 fails, MME selects S-GW/P-GW that supports +nr service only. If step 2 fails, MME selects S-GW/P-GW that supports +ue service only. 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 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.

  • 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.

• Paging Initiation for PS QCI-80, QCI 82, and QCI 83 Events:

  • Attempted — The total number of ECM statistics related to PS paging initiation events attempted for QCI 80, QCI 82, and QCI 83.

  • Success — The total number of ECM statistics related to PS paging initiation events successful for QCI 80, QCI 82, and QCI 83.

  • Failures — The total number of ECM statistics related to PS paging initiation events failed for QCI 80, QCI 82, and QCI 83.

    • Success at Last n eNB — The total number of ECM statistics related to PS paging initiation events succeeded at the last known eNodeB for QCI 80, QCI 82, and QCI 83.

    • Success at Last TAI — The total number of ECM statistics related to PS paging initiation events succeeded at the eNodeB in the TAI from which the UE was last heard for QCI 80, QCI 82, and QCI 83.

    • Success at TAI List — The total number of ECM statistics related PS paging initiation events succeeded at the eNodeB in all TAIs present in the TAI list assigned to the UE for QCI 80, QCI 82, and QCI 83.

show mme-service statistics dcnr

The output of this command includes the following fields:

Secondary RAT Usage Reports Rx Count

• UE Ctxt Release Req — Indicates the number of secondary RAT data usage reports received in UE context release request message.

• UE Ctxt Release Cmpl — Indicates the number of secondary RAT data usage reports received in UE context release complete message .

• E-RAB Mod Ind — Indicates the number of secondary RAT data usage reports received in eRAB Modification Indication message.

• E-RAB Release Ind — Indicates the number of secondary RAT data usage reports received in eRAB Release Indication message.

• E-RAB Release Resp — Indicates the number of secondary RAT data usage reports received in eRAB Release Response message.

• Secondary RAT Data Usage Report[Periodic] — Indicates the number of secondary RAT data usage reports received in Secondary RAT Data Usage Report message without Handover flag.

• Seccondary RAT Data Usage Report[Handover] — Indicates the number of secondary RAT data usage reports received in Secondary RAT Data Usage Report message with Handover flag.

• S10 Fwd Reloc Cmpl Ack — Indicates the number of secondary RAT data usage reports received in Forward Reloc Complete Ack message from MME to MME.

• Dropped Periodic Report[HO in progress] — Indicates the number of secondary RAT data usage reports dropped when Secondary RAT Data Usage Report message was received without Handover flag during Handover.

Secondary RAT Usage Reports Tx Count:

• Create Session Req — Indicates the number of secondary RAT data usage reports sent in Create Session Request .

• Delete Session Req — Indicates the number of secondary RAT data usage reports sent in Delete Session Request.

• Delete Bearer Rsp — Indicates the number of secondary RAT data usage reports sent in Delete Bearer Response .

• Release Access Brr Req — Indicates the number of secondary RAT data usage reports sent in Release Access Bearer Request.

• Delete Bearer Cmd —Indicates the number of secondary RAT data usage reports sent in Delete Bearer Command.

• Modify Bearer Req — Indicates the number of secondary RAT data usage reports sent in Modify Bearer Request.

• Change Notification — Indicates the number of secondary RAT data usage reports sent in Change Notification.

• S10 Fwd Reloc Cmpl Ack — Indicates the number of secondary RAT data usage reports sent in Forward Reloc Complete Ack.

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.

Received S1AP Data:

• Secondary RAT Data Usage Report — Indicates the number of Secondary RAT Data Usage Report messages received from eNodeB.

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.

show call-control-profile full all

The output of this command includes the following fields:

• DCNR

• Secondary RAT Usage Report

show mme-service all

The output of this command includes the following fields:

• DCNR

• Secondary RAT Usage Report

This section provides information on the bulk statistics for the 5G NSA feature on MME.