21 9 5G NSA Solution Guide PDF

5G Non Standalone Solution Guide, StarOS Release 21.
9
First Published: 2018-07-31
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
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.
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: www.cisco.com
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.
CONTENTS
PREFACE About this Guide vii

Conventions Used vii
Supported Documents and Resources viii
Related Common Documentation viii
Related Product Documentation viii
Obtaining Documentation viii
Contacting Customer Support ix
CHAPTER 1 5G Non Standalone Solution Overview 1

Overview 1
Product Description 1
Qualified Platforms 2
Licenses 2
How the 5G NSA Works 2
Dual Connectivity 3
CHAPTER 2 5G NSA for MME 5

Feature Summary and Revision History 5
Feature Description 6
How It Works 10
Architecture 10
Limitations 10
Flows 11
Initial Registration Procedure 11
E-RAB Modification Procedure 13
Standards Compliance 15
5G Non Standalone Solution Guide, StarOS Release 21.9

iii
Contents
Configuring 5G NSA for MME 15

Enabling DCNR in MME Service 15
Enabling DCNR in Call Control Profile 16
Configuring APN AMBR Values 16
Configuring Dedicated Bearer MBR Values 17
Configuring UE AMBR Values 17
Monitoring and Troubleshooting 18

Show Commands and Outputs 18
Bulk Statistics 21
MME Schema 21
TAI Schema 24
CHAPTER 3 5G NSA for SAEGW 25

How It Works 29
Architecture 29
Limitations 30
Flows 30
Supported Standards 33
Configuring 5G NSA for SAEGW 33
Enabling DCNR in P-GW Service 33
Configuring Bearer Duration Statistics for URLLC QCI 34
Configuring EGTPC QCI Statistics for URLLC QCI 34
Configuring Extended Bandwidth with New Radio 35
Configuring Network-Initiated Setup/Teardown Events for URLLC QCI 35
Configuring URLLC QCI in APN Configuration 36
Configuring URLCC QCI In Charging Action 36
Configuring URLCC QCI in QCI QOS Mapping Table 37

Bulk Statistics 42
APN Schema 42
P-GW Schema 44

iv
Contents
SAEGW Schema 45
S-GW Schema 45
System Schema 46
CHAPTER 4 5G NSA for SGSN 49

How It Works 53
Limitations 53
Flows 53
Standards Compliance 55
Configuring 5G NSA for SGSN 56
Enabling DCNR in Call Control Profile 56
Configuring DCNR in SGSN Global Configuration 56
Bulk Statistics 60

v
Contents

vi
About this Guide
This preface describes the 5G Non Standalone Solution Guide, how it is organized and its document conventions.
The 5G Non Standalone (NSA) solution runs on Cisco® ASR 5000, ASR 5500 and virtualized platforms.
• Conventions Used, on page vii
• Supported Documents and Resources, on page viii
• Contacting Customer Support, on page ix
Conventions Used
The following tables describe the conventions used throughout this documentation.
Notice Type Description

Information Note Provides information about important features or
instructions.
Caution Alerts you of potential damage to a program, device,

or system.
Warning Alerts you of potential personal injury or fatality. May

also alert you of potential electrical hazards.
Typeface Conventions Description

Text represented as a screen display This typeface represents displays that appear on your
terminal screen, for example:
Login:
Text represented as commands This typeface represents commands that you enter,
for example:
show ip access-list
This document always gives the full form of a
command in lowercase letters. Commands are not
case sensitive.

vii
About this Guide
Supported Documents and Resources
Typeface Conventions Description

Text represented as a command variable This typeface represents a variable that is part of a
command, for example:
show card slot_number
slot_number is a variable representing the desired
chassis slot number.
Text represented as menu or sub-menu names This typeface represents menus and sub-menus that
you access within a software application, for example:
Click the File menu, then click New
Supported Documents and Resources

Related Common Documentation
The most up-to-date information for this product is available in the product Release Notes provided with each
product release.
• AAA Interface Administration and Reference
• Command Line Interface Reference
• GTPP Interface Administration and Reference
• Installation Guide (platform dependent)
• Release Change Reference
• Statistics and Counters Reference
• System Administration Guide (platform dependent)
Related Product Documentation

The following product documents are also available and work in conjunction with the 5G NSA solution:
• MME Administration Guide
• P-GW Administration Guide
• S-GW Administration Guide
• SAEGW Administration Guide
• SGSN Administration Guide
Obtaining Documentation
The most current Cisco documentation is available on the following website:

viii
About this Guide
Contacting Customer Support
http://www.cisco.com/cisco/web/psa/default.html
Use the following path selections to access the 5G NSA documentation:
Products > Wireless > Mobile Internet> Platforms > Cisco ASR 5000 Series

Use the information in this section to contact customer support.
Refer to the support area of http://www.cisco.com for up-to-date product documentation or to submit a service
request. A valid username and password are required to access this site. Please contact your Cisco sales or
service representative for additional information.

ix
About this Guide

x
CHAPTER 1
5G Non Standalone Solution Overview
This chapter contains general overview information about the 5G NR Non Standalone (NSA) solution, including
sections for:
• Overview, on page 1
• Product Description, on page 1
• How the 5G NSA Works, on page 2
Overview
5G is the next generation of 3GPP technology, after 4G/LTE, defined for wireless mobile data communication.
5G will bridge wireless and wireline networks by introducing a major network architectural change from radio
access to core.
The 5G standards are introduced in 3GPP Release 15 to cater to the needs of 5G networks. The 5G framework
will take advantage of the massive throughput and low latency that new radio provides.
The two solutions defined by 3GPP for 5G networks are:
• 5G Non Standalone (NSA): The existing LTE radio access and core network (EPC) is used as an anchor
for mobility management and coverage to add the 5G carrier. 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.
Product Description
The 5G Non Standalone (NSA) solution enables operators using Cisco EPC Packet Core to launch 5G services
in shorter time and leverage existing infrastructure. NSA leverages the existing LTE radio access and core

1
Qualified Platforms
network (EPC) to anchor 5G NR using the Dual Connectivity feature. This solution provides a seamless option
to deploy 5G services with very less disruption in the network.
The 5G NSA solution is 3GPP compliant and can inter-operate with any RAN and network functions. Cisco
MME, SGSN, S-GW, P-GW, and PCRF services support 5G NSA. See the product-specific feature chapters
in this guide for 5G NSA.
The initial deployments of 5G services are based on 5G NSA, also called option-3. The variants of option-3
are option-3, option-3a and option-3x.
Option-3/3a/3x are transparent to MME and P-GW, and translates to an E-RAB modification procedure at
MME.
• Option-3 — Traffic is split across 4G and 5G at eNodeB.
• Option-3a — Traffic is split across 4G and 5G at EPC (S-GW).
• Option-3x — Traffic is split across 4G and 5G at 5G cell.
The following figure illustrates the interfaces and nodes for option-3 and the variants.
Figure 1: NSA Option-3 Variants
Qualified Platforms
The 5G NSA solution runs on Cisco ASR 5000, ASR 5500, and virtualized platforms. For additional platform
information, see the appropriate System Administration Guide and/or contact your Cisco account representative.
Licenses
5G NSA is a licensed Cisco solution. Contact your Cisco account representative for detailed information on
specific licensing requirements. For information on installing and verifying licenses, refer to the Managing
License Keys section of the Software Management Operations chapter in the System Administration Guide.
How the 5G NSA Works

This section provides information on the function of the 5G NSA in an EPC network.

2
Dual Connectivity
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.
Figure 2: 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
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.

3
Dual Connectivity

4
CHAPTER 2
5G NSA for MME
• Feature Summary and Revision History, on page 5
• Feature Description, on page 6
• How It Works, on page 10
• Configuring 5G NSA for MME, on page 15
• Monitoring and Troubleshooting, on page 18
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

• MME Administration Guide
Revision History
Revision Details Release

5
5G NSA for MME
Feature Description
The 5G NSA solution for MME supports the following functionality 21.9
in this release:
• DCNR capability exchange with peer SGSN in MM context over
S3 interface.
• MME support of statistics for DCNR PDNs.
• NR security algorithms for DCNR capable UEs to support 5G
security.
This feature is not fully qualified in this release.
The 5G NSA solution is qualified on the ASR 5000 platform. 21.5
First introduced. 21.8
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
The 5G standards are introduced in 3GPP Release 15 to cater to the needs of 5G networks.
• 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.
(5GC).
Dual Connectivity

6
5G NSA for MME
Feature Description

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

7
5G NSA for MME
Feature Description
• 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 Support:
Important The support for 5G security is not fully qualified in this release. It is available
only for testing purposes. For more information, contact your Cisco Account
representative.
The "UE Additional Security Capability" and "Replayed UE Additional Security Capability" IEs for
MME are supported as per 3GPP TS 24.301.
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.

8
5G NSA for MME
Feature Description
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 MME provides additional security capabilities received through the "UE Additional Security
Capability" IE for NR in the "NR UE 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.
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

9
5G NSA for MME
How It Works
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.
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.

10
5G NSA for MME
Flows
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.
Figure 4: 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".

11
5G NSA for MME
Initial Registration Procedure
Step Description
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 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 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 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.

12
5G NSA for MME
E-RAB Modification Procedure
Step Description
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 "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.
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.

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.

13
5G NSA for MME
Figure 5: 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 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.
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 MeNB) immediately after switching the path.

14
5G NSA for MME
Standards Compliance
Step Description
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.
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 on MME involves:
• Enabling DCNR in MME Service, on page 15
• Enabling DCNR in Call Control Profile, on page 16
• Configuring APN AMBR Values, on page 16
• Configuring Dedicated Bearer MBR Values, on page 17
• Configuring UE AMBR Values , on page 17
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:

15
5G NSA for MME
Enabling DCNR in Call Control Profile
• 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.

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.

16
5G NSA for MME
Configuring Dedicated Bearer MBR Values
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.
• 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
qos ue-ambr { max-ul mbr_up max-dl mbr_down }
remove qos ue-ambr
end
NOTES:
the name of a call control profile entered as an alphanumeric string of 1 to 64 characters.
• 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.

17
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

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.

18
5G NSA for MME
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.
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.

19
5G NSA for MME
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.
• Handover Statistics:
• 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).
• 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).
• ESM Statistics:

20
5G NSA for MME
Bulk Statistics
DCNR User PDN Connections:

• Attempted — Indicates the total number of attempts made for DCNR user PDN connections
associated with all MME services on the system.
• Success — Indicates the total number of successful attempts for DCNR user PDN connections
• Failures — Indicates the total number of attempts failed for for DCNR user PDN connections
• 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.
show mme-service statistics s1ap

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
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 Description
attached-dcnr-subscriber The current total number of attached subscribers

capable of operating in DCNR.

21
5G NSA for MME
MME Schema
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.

22
5G NSA for MME
MME Schema
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
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
dcnr-dns-pgw-selection-nr The total number of times P-GW DNS selection

procedures were performed with DNS RR including
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.
esmevent-dcnr-user-pdncon-attempt The total number of EPS Session Management events

- DCNR User PDN connections - attempted.

23
5G NSA for MME
TAI Schema
esmevent-dcnr-user-pdncon-success The total number of EPS Session Management events

- DCNR User PDN connections - successes.
esmevent-dcnr-user-pdncon-failure The total number of EPS Session Management events

- DCNR User PDN connections - failures.
pdn-dcnr-user-all The current total number of DCNR user PDN

connections in any state.
pdn-dcnr-user-connected The current total number of DCNR user connected

PDNs.
pdn-dcnr-user-idle 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.
tai-esmevent-dcnr-user-pdncon-attempt The total number of DCNR User PDN connection

EPS Session Management events attempted per TAI.
tai-esmevent-dcnr-user-pdncon-success The total number of successful DCNR User PDN

connection EPS Session Management events per TAI.
tai-esmevent-dcnr-user-pdncon-failure The total number of failed DCNR User PDN

connection EPS Session Management events per TAI.

24
CHAPTER 3
5G NSA for SAEGW
• Configuring 5G NSA for SAEGW, on page 33

Summary Data
Applicable Product(s) or Functional Area • P-GW

• S-GW
• SAEGW
Applicable Platform(s) • ASR 5000

• ASR 5500
• VPC-DI
• VPC-SI

25
5G NSA for SAEGW
Feature Description

• P-GW Administration Guide
• S-GW Administration Guide
• SAEGW Administration Guide
Revision History
The 5G NSA solution for SAEGW supports the following functionality 21.9
in this release:
• P-GW support of Secondary RAT Data Usage Report in Gz CDRs
• 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. 21.5
The 5G NSA solution for SAEGW supports the following functionality 21.8
in this release:
• Feature License
• Dedicated Bearers
• Gy interface
• URLLC QCI
Feature Description
Overview

26
5G NSA for SAEGW
Feature Description
(5GC).
Dual Connectivity

27
5G NSA for SAEGW
Feature Description
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 functionalities:

• 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
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 configuting “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

28
5G NSA for SAEGW
How It Works
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.
• Secondary RAT Usage Data Report Handling:
P-GW supports Secondary RAT Data Usage Report in Gz and Rf CDRs
• Statictics support for DCNR PDNs:
S-GW and P-GW statictics support for DCNR PDNs
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 4294967295 bits per second, the
"Max-Requested-Bandwidth-UL" or DL, AVP must be present, and set to its upper limit 4294967295 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

29
5G NSA for SAEGW
Limitations
Gy (OCS)
New AVPs "Extended-Max-Request-BW-UL" and "Extended-Max-Requested-BW-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 4294967295 bits per second, P-GW
sets the "Max-Requested-Bandwidth-UL/DL" AVP to its upper limit 4294967295 and sets the
"Extended-Max-Requested-BW-UL/DL" to the required bandwidth value in kilobits per second in
CCR-I/CCR-U messages.
5G NSA feature supports only standard Gy "dcca-custom13" dictionary.
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 to handle 5G throughput for 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(saperated for uplink and downlink) including the time of the report.
Limitations
This section describes the known limitations for 5G NSA feature
• 5G NSA is implemented only for Gx standard dictionary (r8-gx-standard).
• 5G NSA has been implemented only for Gy standard dictionary "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.
• ICSR support for 5G NSA is not available.
• When PCRF sends "Extended-Max-Requested-BW-UL/DL" AVP, it is expected to send
"Extended-Max-Requested-BW-UL/DL" with maximum value 4294967295 bps. When
"Extended-Max-Requested-BW-UL/DL" AVP is present, P-GW ignores the received value in
"Max-Requested-Bandwidth-UL/DL" AVP and assumes it to be 4294967295 bps.
• When PCRF sends "Extended-GBR-UL/DL" AVP, it is expected to send "Extended-GBR-UL/DL" with
maximum value 4294967295 bps. When "Extended-GBR-UL/DL" AVP is present, P-GW ignores the
received value in "Guaranteed-Bitrate-UL/DL" AVP and assumes it to be 4294967295 bps.
• S-GW-CDR on Gz interface will not carry the RAN secondary RAT usage data report.
• 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.

30
5G NSA for SAEGW
Flows
Initial Registration by DCNR Capable UE
Step Description
1 The DCNR capable UE sets the "DCNR bit" in the NAS message "Attach Request"
of "UE Network Capability" IE.
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 “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" and sends 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, HSS sends
Subscription-Data with “Access-Restriction" carrying “NR as Secondary RAT Not
Allowed".
5 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.
6 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 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".

31
5G NSA for SAEGW
Flows
Step Description
7 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
4294967295 bps and "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 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.
8 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 Sesssion 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 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.
10 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.
11 eNodeB sends Uplink NAS Transport with NAS message Attach Complete - Activate
Default EPS Bearer Context Accept.
12 MME sends Modify Bearer Request to S-GW with S1-U FTEID details as received
in the Initial Context Setup Response message.
13 MME receives the Modify Bearer Response message from S-GW.

32
5G NSA for SAEGW
Supported Standards
Supported Standards
Cisco's implementation of the 5G NSA complies with the following standards:
Terrestrial Radio Access Network (E-UTRAN) access
• 3GPP 29.212 Release 15.2.0 - Policy and Charging Control (PCC)
• 3GPP 29.274 Release 15.2.0 - 3GPP Evolved Packet System (EPS); Evolved General Packet Radio
Service (GPRS) Tunneling Protocol for Control plane (GTPv2-C); Stage 3
• 3GPP 32.299 Release 15.2.0 - Charging Management; Diameter Charging Applications
• 3GPP 32.298 Release 15.2.0 - 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 33
• Configuring Bearer Duration Statistics for URLLC QCI, on page 34
• Configuring EGTPC QCI Statistics for URLLC QCI, on page 34
• Configuring Extended Bandwidth with New Radio, on page 35
• Configuring Network-Initiated Setup/Teardown Events for URLLC QCI, on page 35
• Configuring URLLC QCI in APN Configuration, on page 36
• Configuring URLCC QCI In Charging Action, on page 36
• Configuring URLCC QCI in QCI QOS Mapping Table , on page 37
Enabling DCNR in P-GW Service

Standalone (NSA).
configure
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.

33
5G NSA for SAEGW
Configuring Bearer Duration Statistics for URLLC QCI
Configuring Bearer Duration Statistics for URLLC QCI

Use the following configuration to configure QCI based duration statistics for URLLC QCI.
configure
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
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.
• no: Disables APN candidate list(s) for the apn-expansion bulkstat schema.
• default: Disables an APN candidate list for the apn-expansion bulkstat schema.

34
5G NSA for SAEGW
Configuring Extended Bandwidth with New Radio
Configuring Extended Bandwidth with New Radio

Use the following configuration to configure extended bandwidth with new radio in IMS authorization service
mode.
configure
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 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 InitiatedSetup/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.

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

36
5G NSA for SAEGW
Configuring URLCC QCI in QCI QOS Mapping Table
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.


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

Diameter Policy Control:
Supported Features:
• extended-bw-nr
show gtpu statistics

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

37
5G NSA for SAEGW
• 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

4G Bearers Released By Reasons:
Admin disconnect — Displays dedicated bearers released due to adminstration 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.

38
5G NSA for SAEGW
show pgw-service statistics all verbose

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

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

39
5G NSA for SAEGW
• 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.
• 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 83.

40
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 statistiscs all verbose

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

41
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 to in support of the 5G NSA feature.
APN Schema
The following 5G NSA feature related bulk statistics are available in the APN schema.
qci80-actbear The total number of QCI80 active bearers.
qci80-setupbear The total number of QCI80 bearers setup.
qci80-relbear The total number of QCI80 released bearers.
qci80-uplinkpkt-fwd The total number of QCI80 uplink packets forwarded.

42
5G NSA for SAEGW
APN Schema
qci80-dwlinkpkt-fwd The total number of QCI80 downlink packets

forwarded.

forwarded.

forwarded.
qci80-uplinkbyte-fwd The total number of QCI80 uplink bytes forwarded.
qci80-dwlinkbyte-fwd The total number of QCI80 downlink bytes forwarded.
qci80-uplinkpkt-drop The total number of QCI80 uplink packets dropped.
qci80-dwlinkpkt-drop The total number of QCI80 downlink packets dropped.
qci80-uplinkbyte-drop The total number of QCI80 uplink bytes dropped.
qci80-dwlinkbyte-drop The total number of QCI80 downlink bytes dropped.
qci80-uplinkpkt-drop-mbrexcd The total number of QCI80 uplink packets dropped

due to MBR being exceeded.


43
5G NSA for SAEGW
P-GW Schema

qci80-dwlinkpkt-drop-mbrexcd The total number of QCI80 downlink packets dropped



qci80-uplinkbyte-drop-mbrexcd The total number of QCI80 uplink bytes dropped due

to MBR being exceeded.


qci80-dwlinkbyte-drop-mbrexcd The total number of QCI80 uplink bytes dropped due



qci80-rejbearer The total number of QCI80 rejected bearers.
sessstat-bearrel-ded-admin-clear-qci80 The total number dedicated bearers released due to

admin clear from P-GW for QCI80.


P-GW Schema
The following 5G NSA feature related bulk statistics available in the P-GW schema.

44
5G NSA for SAEGW
SAEGW Schema
pgw-anchor-pdns-dcnr-current-active The total number of currently active P-GW anchored

DCNR PDNs.
pgw-anchor-pdns-dcnr-cumulative-activated The total number of P-GW anchored PDNs that are

setup as DCNR PDN.
pgw-anchor-pdns-dcnr-cumulative-deactivated The total number of P-GW anchored PDNs that were

either released or degrades to a non-DNCR PDN.
sessstat-pdn-dcnr-current-active Session Statistics - DCNR PDN-Type Statistics -

Current Active.
sessstat-pdn-dcnr-cumulative-activated Session Statistics - DCNR PDN-Type Statistics -

Cumulative PDNs Activated.
sessstat-pdn-dcnr-cumulative-deactivated Session Statistics - DCNR PDN-Type Statistics -

Cumulative PDNs Deactivated.
SAEGW Schema
The following 5G NSA feature related bulk statistics available in the SAEGW schema.
saegw-collocated-pdns-dcnr-current-active The total number of currently active SAEGW

collapsed DCNR PDNs.
saegw-collocated-pdns-dcnr-cumulative-activated The total number of SAEGW collapsed PDNs that are

setup as a DCNR PDN.
saegw-collocated-pdns-dcnr-cumulative-deactivated 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.
sessstat-pdn-dcnr-current-active The total number of currently active S-GW DCNR

PDNs.
sessstat-pdn-dcnr-cumulative-activated The total number of S-GW PDNs that are setup as a

DCNR PDN.
sessstat-pdn-dcnr-cumulative-deactivated The total number of S-GW DCNR PDNs released.
sgw-anchor-pdns-dcnr-current-active The total number of currently active S-GW anchored

DCNR PDNs.
sgw-anchor-pdns-dcnr-cumulative-activated The total number of S-GW anchored PDNs that are

setup as a DCNR PDN.

45
5G NSA for SAEGW
System Schema
sgw-anchor-pdns-dcnr-cumulative-deactivated 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.
sess-bearerdur-5sec-qci80 The current number of bearer sessions with a duration

of 5 seconds and having a QCI of 80.







sess-bearerdur-1min-qci80 The current number of bearer sessions with a duration

of 1 minute and having a QCI of 80.



of 2 minutes and having a QCI of 80.


46
5G NSA for SAEGW
System Schema










sess-bearerdur-1hr-qci80 The current number of bearer sessions with a duration

of 1 hour and having a QCI of 80.



of 4 hours and having a QCI of 80.





47
5G NSA for SAEGW
System Schema




sess-bearerdur-over24hr-qci80 The current number of bearer sessions with a duration

of over 24 hours and having a QCI of 80.


sess-bearerdur-2day-qci80 The current number of bearer sessions with a duration

of 2 days and having a QCI of 80.









48
CHAPTER 4
5G NSA for SGSN
• Configuring 5G NSA for SGSN, on page 56

Summary Data
Applicable Product(s) or Functional Area SGSN
Applicable Platform(s) ASR 5000

• SGSN Administration Guide
Revision History
Revision Details Release

49
5G NSA for SGSN
Feature Description
Feature Description
Overview
(5GC).
Dual Connectivity

50
5G NSA for SGSN
Feature Description
The 5G NSA solution for SGSN supports the following functionalities:
• Dual Connectivity with New Radio (DCNR):
The UE supporting dual connectivity with New Radio (NR) sets the DCNR bit to "dual connectivity with
NR supported" in the MS network capability IE of the "Attach Request" or "Routing Area Update Request"
message.
If the MS supports dual connectivity of E-UTRA with New Radio (NR), then the MS sets the Dual
connectivity of E-UTRA with NR capability bit to "Mobile station supports dual connectivity of E-UTRA
with NR" in the MS network capability IE of the "Attach Request" or "Routing Area Update Request"
message.

51
5G NSA for SGSN
Feature Description
SGSN informs DCNR support to GGSN by setting the DCNR bit in the UP Function Selection Indication
Flags IE of the Create PDP Context Request message.
If all the conditions (UE DCNR capable, SGSN 5G-NSA support) are met, SGSN sends the GPRS
Location Update Request with “nrAsSecondaryRAT” bit set in the Supported Features IE in MAP
Interface Gr.
• Dynamic Gateway Selection:
When DCNR capable UE attempts to register in SGSN and all DCNR validations are successful (for
example, DCNR feature configuration on SGSN, HLR not sending "access-restriction" for NR, and so
on) for dynamic gateway selection, SGSN uses the following service parameters received from DNS
server (in NAPTR response) over other service parameters to select NR capable gateway:
• x-3gpp-pgw:x-gn+nc-nr
• x-3gpp-pgw:x-gp+nc-nr
In order to select a network node with a particular network capability, the character string "+nc-<network
capability>" must be appended to the "app-protocol" name where "nc" indicates "network capability",
"nr" indicates "new radio", "x-gn" is "app protocol" and "x-3gpp-ggsn/pgw" are app services.
For a DCNR capable UE, when the service parameters are received without network capability and new
radio character string "+nc-nr", SGSN uses other service parameters to perform dynamic gateway selection.
When the dynamic selection of gateway fails for any other reasons, SGSN fallbacks and selects the
locally configured gateway.
• DCNR Support to GGSN:
SGSN advertises the DCNR feature support by sending "NR as Secondary RAT" feature bit in "Supported
Features" towards HLR, if DCNR feature is configured at SGSN and UE advertises DCNR capability
in NAS.
When DCNR capable UE attempts to register in SGSN and when all DCNR validations are successful
(for example, DCNR feature configuration on SGSN, HLR not sending access-restriction for NR, and
so on), the SGSN sets the UP Function Selection Indication Flags IE with DCNR flag set to 1 in the
Create PDP Context Request message. This flag enables the selection of a PGW-U optimized for NR,
when the UE establishes the PDN connection first through Gn-SGSN and the Gn-SGSN will pass a
corresponding indication over Gn/Gp to the GGSN/P-GW.
• Subscription Control:
SGSN handles the reception of “NR as Secondary RAT Not Allowed” bit in Extended-Access Restriction
Data IE in “Insert Subscriber Data” message from HLR.
• Extended Bandwith:
SGSN handles the reception of "Extended Maximum Bit rate DL" and "Extended Maximum Bit rate
UL" in AMBR IE received in the "Insert Subscriber Data" message from HLR.
• Access Restriction Data:
SGSN supports Access Restriction data information in MM Context IE while receiving/sending from/to
peer SGSN during ISRAU and SRNS Relocation procedures.

52
5G NSA for SGSN
How It Works
How It Works
Limitations
This section describes the known limitations for 5G NSA feature:
• To support EPC QOS parameters like "APN-AMBR", "E-ARP" and "UE-AMBR", “Support for EPC
QoS Attributes on SGSN” feature must be enabled. Currently this feature is supported only on 3G not
on 2G. So Extended Bandwidth support is only on 3G-SGSN.
• 5G-NSA enabled SGSN uses only MAP Protocol on the Gr Interface, Diameter Protocol on the s6d
Interface is not supported.
• If HLR does not send "Extended-Access Restriction" data IE in Insert Subscribe Data message, SGSN
assumes that NR as secondary RAT is allowed and it processes the UE request as DCNR enabled.
• When SGSN cannot find a collocated PGW/GGSN which “+nc-nr” in DNS response, SGSN falls back
and triggers "A" query to get the normal GGSN information.
• SGSN with 5G-NSA feature enabled selects only the collocated PGW/GGSN in DNS response, for
example “x-3gpp-pgw x-gn+nc-nr/ x-3gpp-pgw x-gp+nc-nr.”
Flows
This section describes the call flow procedures related to SGSN for 5G NSA.

53
5G NSA for SGSN
Flows
Figure 8: Initial Attach Request with DCNR
1. DCNR capable UE sends “DCNR bit” in NAS message “Attach Request” in “MS Network Capability”
IE.
2. SGSN successfully authenticates the UE.
3. SGSN advertises the DCNR feature support by sending “NR as Secondary RAT” feature bit in “Supported
Features”.
4. If HLR determines that the UE is not authorized for DCNR services, HLR sends Subscription-Data with
“Extended Access-Restriction” carrying “NR as Secondary RAT Not Allowed”.
5. SGSN determines the Gateway which is NR capable from the DNS response.
6. SGSN sends Create PDP Context Request with the UP Function Selection Indication Flags coded with
DCNR bit to the selected gateway.

54
5G NSA for SGSN
Figure 9: Inter SGSN RAU
1. DCNR capable UE sets “DCNR bit” in NAS message “RAU Request” in “MS Network Capability” IE.
2. New-SGSN triggers SGSN Context Request message to OLD-SGSN where the UE is previously attached
to get UE context.
3. OLD-SGSN fills the MM-Context with Access-Restriction Data IE with NRSRNA in SGSN Context
Response message.
4. After Authentication and verifying subscription information, NEW SGSN sends RAU Accept message
to UE.
Cisco's implementation of the 5G NSA feature complies with the following standards:
• 3GPP 23.003 Release 15.2.0 - 3rd Generation Partnership Project; Technical Specification Group Core
Network and Terminals; Numbering, addressing and identification.

55
5G NSA for SGSN
Configuring 5G NSA for SGSN
Terrestrial Radio Access Network (E-UTRAN) access.
Networkand Terminals; Mobile Application Part (MAP) specification.
Networkand Terminals; Mobile radio interfaceLayer3 specification; Core network protocols; Stage3.
• 3GPP 29.060 Release 15.1.0 - 3rd GenerationPartnershipProject Technical Specification Group Core
Network; General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP)acrossthe Gn and
Gp interface.
Networkand Terminals; Domain Name System Procedures; Stage3.
Networkand Terminals; Domain Name System Procedures; Stage3.
Configuring 5G NSA for SGSN

This section describes how to configure 5G NSA to support SGSN.
Configuring 5G NSA involves:

Standalone (NSA).
configure
[ no | remove ] dcnr
end
NOTES:
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.
Removes existing configuration related to DCNR at Call-Control-Profile level (either ‘dcnr’ or ’ no dcnr’
), and behaviour depends on the configuration at sgsn-global level.
Configuring DCNR in SGSN Global Configuration

Use the following configuration to enable Dual Connectivity with New Radio (DCNR) for 5G NSA support
in the SGSN Global Configuration mode.

56
5G NSA for SGSN
With this configuration, SGSN processes the UEs with 5G capability and selects the gateways that are NR
capable to inform the peer MME/SGSN nodes.
config
sgsn-global
[ no ] dcnr
end
NOTES:
• dcnr: Configures DCNR to support 5G NSA.
• no: Disables the DCNR support.
• This feature is applicable only to Gn-SGSN.


show sgsn-mode
SGSN Global Configuration:
• Dual Connectivity Support with NR capability
show subscribers sgsn-only/gprs-only full

MS Network Capability:
• DCNR capability: Indicates MS is capable of DCNR or not.
Subscription Data:
Extended ARD:
• NR-As-Secondary-RAT-Not-Allowed - Advertises the DCNR feature support by sending “NR as
Secondary RAT” feature bit towards HLR provided DCNR feature is configured at SGSN and UE
advertises DCNR capability in NAS.
show gmm-sm statistics

Session Statistics:
Attached Subscribers:

57
5G NSA for SGSN
• 3G-with-DCNR-Attached - The total number of subscribers with DCNR allowed for 3G service.
• 2G-with-DCNR-Attached - The total number of subscribers with DCNR allowed for 2G service.
Activated Subscribers:
• 3G Activated with DCNR - Total number of activated subscribers with DCNR capable allowed for 2g
service.
• 2G Activated with DCNR - Total number of activated subscribers with DCNR capable allowed for 2g
service.
Activate PDP Contexts:

Total Actv PDP Ctx:
• 3G-Actv Pdp CTx with DCNR - The total number of active PDP contexts established with NR capable
P-GW/GGSN.
• 2G-Actv Pdp Ctx with DCNR - The total number of active PDP contexts established with NR capable
P-GW/GGSN.
Message Statistics:
Specific Procedures:
Attach Request:
• 3G-with-DCNR-Cap-Attached - Total number of 3G Attach Requests received from DCNR capable
UEs.
• 2G-with-DCNR-Cap-Attached - Total number of 2G Attach Requests received from DCNR capable
UEs.
Attach Accept:
Total-Attach-Accept:
• 3G-Attach-Accept-with-DCNR - Total number of 3G Attach Requests accepted with DCNR allowed for
DCNR capable UEs.
• 2G-Attach-Accept-with-DCNR - Total number of 2G Attach Requests accepted with DCNR allowed for
DCNR capable UEs.
Attach Complete:
• 3G-Att-Comp-with-DCNR-Cap - Total number of attach complete received for DCNR allowed UEs for
3G service.
• 2G-Att-Comp-with-DCNR-Cap - Total number of attach complete received for DCNR allowed UEs for
2G service.
Attach Reject:
• 3G-Attach-Reject-with-DCNR - Total number of 3G Attach Requests Rejected for DCNR capable UEs.
• 2G-Attach-Reject-with-DCNR - Total number of 2G Attach Requests Rejected for DCNR capable UEs.
Routing Area Update Request:

58
5G NSA for SGSN
• 3G-RAU-Req-with-DCNR-Cap - Total number of 3G RAU Requests received from DCNR capable UEs.
• 2G-RAU-Req-with-DCNR-Cap - Total number of 2G RAU Requests received from DCNR capable UEs.
Routing Area Update Accept:

• 3G-RAU-Acc-with-DCNR-Cap - Total number of 3G RAU Requests accepted with DCNR allowed for
DCNR capable UEs.
• 2G-RAU-Acc-with-DCNR-Cap - Total number of 2G RAU Requests accepted with DCNR allowed for
DCNR capable UEs.
Routing Area Update Complete:

• 3G-RAU-Comp-with-DCNR-Cap - Total number of 3G RAU complete received for DCNR allowed
UEs.
• 2G-RAU-Comp-with-DCNR-Cap - Total number of 2G RAU complete received for DCNR allowed
UEs.
Routing Area Update Reject:

• 3G-RAU-Rej-with-DCNR-Cap - Total number of 3G RAU Requests Rejected for DCNR capable UEs.
• 2G-RAU-Rej-with-DCNR-Cap - Total number of 2G RAU Requests Rejected for DCNR capable UEs.
Session Management Messages Statistics:

• 3G-Actv-Request-with-DCNR-Capability - Total number of 3G Activation Requests received for DCNR
allowed UEs.
• 2G-Actv-Request-with-DCNR-Capability - Total number of 2G Activation Requests received for DCNR
allowed UEs.
Primary-Actv-Request:
• 3G-Primary-Actv-Request-with-DCNR-Capability - Total number of 3G primary Activation Requests
received for DCNR allowed UEs.
• 2G-Primary-Actv-Request-with-DCNR-Capability - Total number of 2G primary Activation Requests
received for DCNR allowed UEs
Activate Context Accept:

• 3G-Acvt-Accept-with-DCNR - Total number of 3G Primary Activation Accepted with PDP context
established with NR capable P-GW/GGSN.
• 2G-Acvt-Accept-with-DCNR - Total number of 2G Primary Activation Accepted with PDP context
Activate Context Reject:

• 3G-Acvt-Reject-with-DCNR - Total number of 3G Primary Activation Rejected for DCNR allowed UEs
• 2G-Acvt-Reject-with-DCNR - Total number of 2G Primary Activation Rejected for DCNR. allowed
UEs.
SRNS statistics:

59
5G NSA for SGSN
Bulk Statistics
Attempted
Inter-SRNS UE involved Inter-SRNS UE not involved (new SGSN with MME) -
• Inter-SRNS NRSRNA UE involved Inter-SRNS NRSRNA UE not involved (old SGSN) - Inter-SGSN
SRNS from the local SGSN to the peer SGSN is attempted with relocation type 'UE not involved' and
DCNR allowed.
• Inter-SRNS NRSRNA UE involved Inter-SRNS NRSRNA UE not involved (new SGSN) - Inter-SGSN
SRNS to the local SGSN from the peer SGSN is attempted with relocation type 'UE not involved and
DCNR allowed
Inter-SRNS UE not involved (new SGSN with MME):

• Inter-SRNS NRSRNA UE not involved (old SGSN) - Inter-SGSN SRNS from the local SGSN to the
peer SGSN is attempted with relocation type 'UE not involved' and DCNR allowed
• Inter-SRNS NRSRNA UE not involved (new SGSN) – Inter-SGSN SRNS from the local SGSN to the
peer SGSN is attempted with relocation type 'UE not involved' and DCNR allowed.
Sucessful:
Total SRNS:
• Intra-SGSN SRNS (new SGSN with MME) - Intra SGSN from local SGSN to peer MME is attempted
with relocation type UE not Involved /Involved and DCNR allowed.
• Inter-SRNS NRSRNA UE involved (old SGSN) - Inter-SGSN SRNS to the peer SGSN from the local
SGSN with dcnr is attempted with relocation type 'UE involved' and DCNR allowed.
• Inter-SRNS NRSRNA UE involved (new SGSN) - Inter-SGSN SRNS to the peer SGSN from the local
SGSN with DCNR is attempted with relocation type 'UE involved’ and DCNR allowed.
Bulk Statistics
The following 5G NSA feature related bulk statistics are available in the SGSN schema.

2G-attached-with-dcnr The total number of subscribers with DCNR allowed
for 2G service.
2G-attached-pdp-with-dcnr the total number of subscribers attached having PDF

2G-activated-pdp-with-dcnr The total number of active PDP contexts established

with NR capable P-GW/GGSN.
2G-attach-req-with-dcnr The total number of 2G Attach Requests received

from DCNR capable UEs.
2G-attach-accept-with-dcnr The total number of 2G Attach Requests accepted

with DCNR allowed for DCNR capable UEs.
2G-attach-reject-with-dcnr The total number of 2G Attach Requests Rejected for

DCNR capable UEs.

60
5G NSA for SGSN
Bulk Statistics
2G-rau-with-dcnr The total number of 2G RAU Requests received from

DCNR capable UEs.
2G-rau-accept-with-dcnr The total number of 2G RAU Requests accepted with

DCNR allowed for DCNR capable UEs.
2G-rau-complete-with-dcnr The total number of 2G RAU complete received for

DCNR allowed UEs.
2G-rau-reject-with-dcnr The total number of 2G RAU Requests Rejected for

DCNR capable UEs.
2G-total-active-with-dcnr The total number of 2G Activation Requests received

for DCNR allowed UEs.
2G-total-primary-active-with-dcnr The total number of 2G primary Activation Requests

2G-total-primary-active-accept-with-dcnr The total number of 2G Primary Activation Accepted

with PDP context established with NR capable
P-GW/GGSN.
2G-total-primary-active-reject-with-dcnr The total number of 2G Primary Activation Rejected

for DCNR.allowed UEs.
3G-attach-complete-with-dcnr The total number of attach complete received for

DCNR allowed UEs.
2G-attach-complete-with-dcnr The total number of attach complete received for

DCNR allowed UEs.
3G-attached-with-dcnr The total number of subscribers with DCNR allowed

for 3G service.
3G-attached-pdp-with-dcnr The total number of subscribers attached having pdp

3G-activated-pdp-with-dcnr The total number of active PDP contexts established

with NR capable P-GW/GGSN.
3G-attach-req-with-dcnr The total number of 3G Attach Requests received

from DCNR capable UEs.
3G-attach-accept-with-dcnr The total number of 3G Attach Requests accepted

with DCNR allowed for DCNR capable UEs.
3G-attach-reject-with-dcnr The total number of 3G Attach Requests Rejected for

DCNR capable UEs.
3G-rau-with-dcnr The total number of 3G RAU Requests received from

DCNR capable UEs.

61
5G NSA for SGSN
Bulk Statistics
3G-rau-accept-with-dcnr The total number of 3G RAU Requests accepted with

DCNR allowed for DCNR capable UEs.
3G-rau-complete-with-dcnr The total number of 3G RAU complete received for

DCNR allowed UEs.
3G-rau-reject-with-dcnr The total number of 3G RAU Requests Rejected for

DCNR capable UEs.
3G-total-active-with-dcnr The total number of 3G Activation Requests received

for DCNR allowed UEs.
3G-total-primary-active-with-dcnr The total number of 3G primary Activation Requests

3G-total-primary-active-accept-with-dcnr The total number of 3G Primary Activation Accepted

with PDP context established with NR capable
P-GW/GGSN.
3G-total-primary-active-reject-with-dcnr The total number of 3G Primary Activation Rejected

for DCNR.allowed UEs.
Important It is an assumed that all the UEs are DCNR capable for the below mentioned counters.
att_old_sgsn_inter_srns_dcnr_ue_involved Inter-SGSN is attempted with relocation type 'UE

involved' and DCNR allowed.
att_old_sgsn_inter_srns_dcnr_ue_not_involved Inter-SGSN SRNS from the local SGSN to the peer

SGSN is attempted with relocation type 'UE not
att_new_sgsn_inter_srns_dcnr_ue_involved Inter-SGSN SRNS to the local SGSN from the peer

SGSN is attempted with relocation type 'UE involved'
and DCNR allowed.
att_new_sgsn_inter_srns_dcnr_ue_not_involved Inter-SGSN SRNS to the local SGSN from the peer

involved and DCNR allowed.
suc_old_sgsn_inter_srns_dcnr_ue_involved Inter-SGSN SRNS to the peer SGSN from the local

SGSN with DCNR is attempted with relocation type
'UE involved' and DCNR allowed.
suc_old_sgsn_inter_srns_dcnr_ue_not_involved Inter-SGSN SRNS from the local SGSN to the peer

suc_new_sgsn_inter_srns_dcnr_ue_involved Inter-SGSN SRNS to the peer SGSN from the local

SGSN with DCNR is attempted with relocation type
'UE involved’ and DCNR allowed.

62
5G NSA for SGSN
Bulk Statistics
suc_new_sgsn_inter_srns_dcnr_ue_not_involved Inter-SGSN SRNS from the local SGSN to the peer


63
5G NSA for SGSN
Bulk Statistics

64

21 9 5G NSA Solution Guide PDF

Uploaded by

Copyright:

Available Formats

21 9 5G NSA Solution Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

21 9 5G NSA Solution Guide PDF

Uploaded by

Copyright:

Available Formats

5G Non Standalone Solution Guide, StarOS Release 21.

PREFACE About this Guide vii

CHAPTER 1 5G Non Standalone Solution Overview 1

CHAPTER 2 5G NSA for MME 5

5G Non Standalone Solution Guide, StarOS Release 21.9

Configuring 5G NSA for MME 15

Monitoring and Troubleshooting 18

CHAPTER 3 5G NSA for SAEGW 25

Monitoring and Troubleshooting 37

5G Non Standalone Solution Guide, StarOS Release 21.9

CHAPTER 4 5G NSA for SGSN 49

5G Non Standalone Solution Guide, StarOS Release 21.9

5G Non Standalone Solution Guide, StarOS Release 21.9

Notice Type Description

Caution Alerts you of potential damage to a program, device,

Warning Alerts you of potential personal injury or fatality. May

Typeface Conventions Description

5G Non Standalone Solution Guide, StarOS Release 21.9

Typeface Conventions Description

Supported Documents and Resources

Related Product Documentation

5G Non Standalone Solution Guide, StarOS Release 21.9

Contacting Customer Support

5G Non Standalone Solution Guide, StarOS Release 21.9

5G Non Standalone Solution Guide, StarOS Release 21.9

Note The 5G NSA solution is supported in this release.

5G Non Standalone Solution Guide, StarOS Release 21.9

How the 5G NSA Works

5G Non Standalone Solution Guide, StarOS Release 21.9

5G Non Standalone Solution Guide, StarOS Release 21.9

5G Non Standalone Solution Guide, StarOS Release 21.9

Feature Summary and Revision History

Applicable Product(s) or Functional Area MME

Applicable Platform(s) • ASR 5000

Feature Default Disabled - Configuration Required

Related Changes in This Release Not applicable

Related Documentation • 5G Non Standalone Solution Guide

Revision Details Release

5G Non Standalone Solution Guide, StarOS Release 21.9

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

First introduced. 21.8

Note The 5G NSA solution is supported in this release.

5G Non Standalone Solution Guide, StarOS Release 21.9

The following figure illustrates the E-UTRA-NR Dual Connectivity architecture.

5G Non Standalone Solution Guide, StarOS Release 21.9

5G Non Standalone Solution Guide, StarOS Release 21.9

5G Non Standalone Solution Guide, StarOS Release 21.9

S6a (HSS) Interface

S1AP (eNodeB) Interface

NAS (UE) Interface

5G Non Standalone Solution Guide, StarOS Release 21.9

Initial Registration Procedure

2 MME successfully authenticates the UE.

5G Non Standalone Solution Guide, StarOS Release 21.9

6 P-GW sends CCR-I to PCRF advertising the DCNR by sending

7 PCRF sends CCA-I advertising the DCNR by sending "Extended-BW-NR" feature

5G Non Standalone Solution Guide, StarOS Release 21.9

13 MME receives the Modify Bearer Response message from S-GW.

E-RAB Modification Procedure