Explore Cisco
How to Buy

Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

5G Non Standalone Solution Guide, StarOS Release 21.5

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

5G Non Standalone Solution Guide, StarOS Release 21.5

Chapter Title

5G NSA for MME

Results

Updated:
June 4, 2018

Chapter: 5G NSA for MME

5G NSA for MME

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

MME

Applicable Platform(s)

  • 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

The 5G NSA solution is qualified on the ASR 5000 platform.

21.5

First introduced.

21.8

Feature Description

The 5G NSA solution for MME supports the following functionality:

  • 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, etc), 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 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 will support the CUPS architecture for 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. If S-GW receives IE in non-CUPS deployment, it is ignored.

  • Ultra-low latency QCI — URLLC QCI 80 (Non-GBR resource type), QCI 82 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 also 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).

  • E-RAB modification procedure

  • Handles the "DCNR bit" in "UE network capability" IE.

  • Advertises the DCNR feature support by sending "NR as Secondary RAT" feature bit in "Feature-List-ID-2" towards HSS provided the DCNR feature is configured at MME and UE advertises the DCNR capability in NAS.

  • Receives DCNR feature support from HSS when HSS sends the "NR as Secondary RAT" feature bit in "Feature-List-ID-2".

  • Decodes the extended AVP (Extended-Max-Requested-BW-UL and Extended-Max-Requested-BW-DL) which is received from HSS.

  • Handles ULA/IDR from HSS with "Access-Restriction" carrying "NR as Secondary RAT Not Allowed".

  • The following new IEs are supported with this feature.

    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

  • Sends the extended QoS values towards S-GW in legacy IE APN-AMBR, Bearer QoS, and Flow QoS.

  • Configuration of DCNR at the MME service and call control profile.

  • Extension of UE-AMBR limits in call control profile for higher throughput.

  • Extension of APN-AMBR and MBR limits in APN profile for higher throughput.

  • Statistics for DCNR feature and E-RAB modification feature.

How It Works

Architecture

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 existing IE in NAS "APN-AMBR" supports APN-AMBR values up to 65.2Gbps, to convey the 5G throughput (beyond 65.2Gbps) over NAS. A new IE "Extended APN aggregate maximum bit rate" is added in all applicable NAS messages.

Extended EPS Quality of Service

As the existing IE in NAS "EPS Quality of Service" supports MBR and GBR values up to 10Gbps, to convey the 5G throughput (beyond 10Gbps) over NAS, a new IE "Extended EPS Quality of Service" is added in all applicable NAS messages. The structure of IE "Extended EPS Quality of Service" and the units for encoding/decoding is displayed below.

Flows

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

Initial Registration Procedure

This section describes the Initial Registration procedure for DCNR capable UE.

Figure 1. Initial Registration of DCNR Capable UE

Step

Description

1

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.

2

MME successfully authenticates the UE.

3

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

4

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 4294967295 bps, "Max-Requested-Bandwidth-DL" as 4294967295 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, then HSS sends Subscription-Data with "Access-Restriction" carrying "NR as Secondary RAT Not Allowed".

5

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.

6

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 4294967295 bps, "APN-Aggregate-Max-Bitrate-DL" as 4294967295 bps, and the extended bandwidth values in new AVPs "Extended-APN-AMBR-UL" and "Extended-APN-AMBR-DL".

7

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 4294967295 bps, "APN-Aggregate-Max-Bitrate-DL" as 4294967295 bps, and the extended bandwidth values in new 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.

8

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.

9

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

10

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.

11

eNodeB sends Uplink NAS Transport with NAS message "Complete - Activate Default EPS Bearer Context Accept".

12

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.

13

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, this procedure is used to transfer bearer contexts to and from secondary eNodeB or secondary gNodeB.

Figure 2. E-RAB Modification Procedure by Master eNodeB

Step

Description

1

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 master eNodeB indicates if each bearer is modified or not. The "E-RAB to be Modified List" IE contains both "E-RAB to Be Modified Item IEs" and "E-RAB not to Be Modified Item IEs". For the bearer that need to be switched to secondary eNodeB/gNodeB (SeNB), "E-RAB to Be Modified Item IEs" contains the transport layer address of gNodeB and TEID of gNodeB.

2

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.

3

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.

4

For the bearers transferred to SeNB, S-GW sends one or more end marker packets on the old path (to Master eNodeB) immediately after switching the path.

5

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

Configuring 5G NSA for MME

This section describes how to configure 5G NSA to support MME.

Configuring 5G NSA involves:

Enabling DCNR in MME Service

Use the following configuration to enable Dual Connectivity with New Radio (DCNR) to support 5G Non Standalone (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.

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.

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 
      remove qos apn-ambr  
      end

NOTES:

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

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

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

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 — Indicates the number of Attach Request messages received with UE advertising DCNR support.

    • Attach Acc DCNR allowed — Indicates 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 — Indicates 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 — Indicates the number of Attach Reject messages sent by MME whose corresponding Attach Request messages have DCNR support capability.

    • Attach Complete Rcvd — Indicates 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 — Indicates the number of TAU Request messages received for Intra-MME TAU procedure with UE advertising DCNR support.

    • TAU Accept DCNR allowed — Indicates 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 — Indicates 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 — Indicates 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 — Indicates the number of TAU Request messages received for Inter-MME TAU procedure with UE advertising DCNR support.

    • TAU Accept DCNR allowed — Indicates 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 — Indicates 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 — Indicates the number of TAU Reject messages sent by the MME whose corresponding Inter-MME TAU Requests have DCNR support capability.

    • TAU Complete Rcvd — Indicates 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 — Indicates the number of DCNR supported UEs attached with the MME.

    • Connected Calls — Indicates the number of DCNR supported UEs in connected mode at the MME.

    • Idle Calls — Indicates the number of DCNR supported UEs in idle mode at the MME.

    Handover Statistics:

    • Intra MME Handover:

      • Path Update procedures

        • Attempted — Indicates the number of E-RAB Modification Indication procedures attempted (procedure level stats).

        • Success — Indicates the number of E-RAB Modification Indication procedures succeeded (procedure level stats).

        • Failures — Indicates the number of E-RAB Modification Indication procedures failed (procedure level stats).

      Bearer Statistics

      • ERAB Modification Indication

        • Attempted — Indicates the number of bearers for which the E-RAB Modification Indication procedure is attempted (bearer level stats).

        • Success — Indicates the number of bearers for which the E-RAB Modification Indication procedure has succeeded (bearer level stats).

        • Failures — Indicates the number of bearers for which the E-RAB Modification Indication procedure has failed (bearer level stats).

    Node Selection:

    SGW DNS:

    • Common — Indicates the number of times S-GW DNS selection procedures are performed with DNS RR excluding the NR network capability.

    • NR Capable — Indicates the number of times S-GW DNS selection procedures are performed with DNS RR including the NR network capability.

    SGW Local Config

    • Common — Indicates 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 — Indicates the number of times P-GW DNS selection procedures are performed with DNS RR excluding the NR network capability.

    • NR Capable — Indicates the number of times P-GW DNS selection procedures are performed with DNS RR including the NR network capability.

    PGW Local Config:

    • Common — Indicates 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.

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.

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.

Bulk Statistics

The following 5G NSA feature related bulk statistics are available in the MME schema.

Bulk Statistics

Description

attached-dcnr-subscriber

The current total number of attached subscribers capable of operating in DCNR.

connected-dcnr-subscriber

The current total number of subscribers capable of operating in DCNR and in connected state.

idle-dcnr-subscriber

The current total number of subscribers capable of operating in DCNR and in idle state.

dcnr-attach-req

The total number of Attach Request messages that are received with DCNR supported.

dcnr-attach-acc-allowed

The total number of Attach Accept messages that are sent with DCNR allowed.

dcnr-attach-acc-denied

The total number of Attach Accept messages that are sent with DCNR denied.

dcnr-attach-rej

The total number of DCNR requested Attach Rejected messages.

dcnr-attach-comp

The total number of Attach Complete messages that are received for DCNR supported attaches.

dcnr-intra-tau-req

The total number of Intra-TAU Request messages that are received with DCNR supported.

dcnr-intra-tau-acc-allowed

The total number of Intra-TAU Accept messages that are sent with DCNR allowed.

dcnr-intra-tau-acc-denied

The total number of Intra-TAU Accept messages that are sent with DCNR denied.

dcnr-intra-tau-comp

The total number of Intra-TAU Complete messages that are received for DCNR supported requests.

dcnr-inter-tau-req

The total number of Inter-TAU Request messages that are received with DCNR supported.

dcnr-inter-tau-acc-allowed

The total number of Inter-TAU Accept messages that are sent with DCNR allowed.

dcnr-inter-tau-acc-denied

The total number of Inter-TAU Accept messages that are sent with DCNR denied.

dcnr-inter-tau-rej

The total number of DCNR requested Inter-TAU Request messages that are rejected.

dcnr-inter-tau-comp

The total number of Inter-TAU Complete messages that are received for DCNR supported requests.

s1ap-recdata-eRabModInd

The total number of S1 Application Protocol - E-RAB Modification Indication messages received from all eNodeBs.

s1ap-transdata-eRabModCfm

The total number of E-RAB Modification Confirmation messages sent by the MME to the eNodeB.

erab-modification-indication-attempted

The total number of bearers for which E-RAB Modification Indication messages were sent.

erab-modification-indication-success

The total number of bearers for which E-RAB Modification Indication messages were sent.

erab-modification-indication-failures

The total number of bearers for which E-RAB Modification Indication failed as shown in E-RAB Modification Indication Confirm message.

emmevent-path-update-attempt

The total number of EPS Mobility Management events - Path Update attempted.

emmevent-path-update-success

The total number of EPS Mobility Management events - Path Update successes.

emmevent-path-update-failure

The total number of EPS Mobility Management events - Path Update failures.

dcnr-dns-sgw-selection-common

The total number of times S-GW DNS selection procedures are performed with DNS RR excluding NR network capability.

dcnr-dns-sgw-selection-nr

The total number of times S-GW DNS selection procedures were performed with DNS RR including NR network capability.

dcnr-dns-sgw-selection-local

The total number of times S-GW selection procedures were performed with locally configured S-GW address, without considering the NR network capability.

dcnr-dns-pgw-selection-common

The total number of times P-GW DNS selection procedures were performed with DNS RR excluding NR network capability.

dcnr-dns-pgw-selection-nr

The total number of times P-GW DNS selection procedures were performed with DNS RR including NR network capability.

dcnr-dns-pgw-selection-local

The total number of times P-GW selection procedures were performed with locally configured P-GW address, without considering the NR network capability.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco