The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Information on new features, enhancements, and behavior changes in the Release Change Reference (RCR) document will now be available under the What’s New in this Release section in the 5G release notes.
 Note |
This document will be deprecated in 2024.01 and later releases. |
The following table indicates the default values of features and behavior changes introduced or modified in this release.
|
Features/ Behavior Changes |
Default |
Release Introduced/Modified |
|---|---|---|
|
Enabled – Always-on |
2023.04.0 |
|
|
Enabled – Always-on |
2023.04.0 |
|
|
Disabled – Configuration Required |
2023.04.0 |
|
|
Disabled – Configuration Required |
2023.04.0 |
|
|
Disabled – Configuration Required |
2023.04.0 |
|
|
Disabled – Configuration Required |
2023.04.0 |
|
|
Disabled – Configuration Required |
2023.04.0 |
|
|
Enabled – Always-on |
2023.04.0 |
|
|
Not Applicable |
2023.04.0 |
|
|
Enabled – Always-on |
2023.04.0 |
|
|
Disabled – Configuration Required |
2023.04.0 |
|
|
Enabled – Always-on |
2023.04.0 |
|
|
Disabled – Configuration Required |
2023.04.0 |
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
The Prometheus metrics label for microcheckpoints are made agnostic to the type.
Previous Behavior: The Prometheus label string was the underlying microcheckpoint type which prevented the RCM checkpoint manager to be agnostic to the checkpoint types.
For example: UPLANE_PDR_INFO
New Behavior: The new Prometheus label strings are now agnostic strings.
For example: MicroType234
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
Previous Behavior: In the show sx-service statistics all CLI command, some discard reason statistics were listed under "Session Management Messages:".
New Behavior: All discard reason statistics will now be listed under "Session Rejection Stats:" in the output of the show sx-service statistics all CLI command.
| Applicable Product(s) or Functional Area | 5G-UPF |
| Applicable Platform(s) |
VPC-SI |
| Feature Default Setting | Disabled – Configuration Required |
| Related Changes in this Release | Not Applicable |
| Related Documentation | UCC 5G UPF Configuration and Administration Guide |
| Revision Details | Release |
|---|---|
|
2023.04.0 |
|
Support has been added for the following functionality:
|
2021.02.0 |
| New L7 protocols have been introduced as part of Deep Packet Inspection (DPI). | 2021.01.0 |
|
The following EDR attributes have been added for TCP:
|
2021.01.0 |
| New DNS attributes have been introduced in EDRs. | 2021.01.0 |
| First introduced. | 2020.02.0 |
The EDR configuration supports two new attributes sn-last-uplink-pkt-time and sn-last-downlink-pkt-time to identify the data stall issue.
For more information, refer to the UCC 5G UPF Configuration and Administration Guide > Deep Packet Inspection and Inline Services chapter.
| Applicable Product(s) or Functional Area | 5G-UPF |
| Applicable Platform(s) |
VPC-SI |
| Feature Default Setting | Disabled – Configuration Required |
| Related Changes in this Release | Not Applicable |
| Related Documentation | UCC 5G UPF Configuration and Administration Guide |
| Revision Details | Release |
|---|---|
|
2023.04.0 |
|
Support has been added for the following functionality:
|
2021.02.0 |
| New L7 protocols have been introduced as part of Deep Packet Inspection (DPI). | 2021.01.0 |
|
The following EDR attributes have been added for TCP:
|
2021.01.0 |
| New DNS attributes have been introduced in EDRs. | 2021.01.0 |
| First introduced. | 2020.02.0 |
The Firewall feature inspects subscriber traffic performing IP session-based access control to protect subscribers from security attacks.
UPF supports the TCP Idle Timeout action to drop the subscriber flow or send reset on TCP timeout expiry.
For more information, refer to the UCC 5G UPF Configuration and Administration Guide > Deep Packet Inspection and Inline Services chapter.
|
Applicable Product(s) or Functional Area |
5G-UPF |
|
Applicable Platform(s) |
VPC-SI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
UCC 5G UPF Configuration and Administration Guide |
|
Revision Details |
Release |
|---|---|
|
Added support for binding multiple GTPU IP addresses to ensure even distribution of traffic across the VPP worker threads on UPF. |
2023.04.0 |
|
Added support for IP separation per interface to allow separate networks for N3 and N9 interfaces. |
2023.03.0 2023.02.0 |
| First introduced. |
2020.02.0 |
UPF allows binding of multiple GTPU IP addresses to provide high uplink throughput in Private 5G deployments. UPF creates unique GTPU 3-tuple hash entries to ensure uniform distribution of ingress traffic on all VPP worker threads.
For more information, refer to the UCC 5G UPF Configuration and Administration Guide > UPF Ingress Interfaces chapter.
| Applicable Product(s) or Functional Area | 5G-UPF |
| Applicable Platform(s) |
VPC-SI |
| Feature Default Setting | Disabled – Configuration Required |
| Related Changes in this Release | Not Applicable |
| Related Documentation | UCC 5G UPF Configuration and Administration Guide |
| Revision Details | Release |
|---|---|
|
2023.04.0 |
|
Support has been added for the following functionality:
|
2021.02.0 |
| New L7 protocols have been introduced as part of Deep Packet Inspection (DPI). | 2021.01.0 |
|
The following EDR attributes have been added for TCP:
|
2021.01.0 |
| New DNS attributes have been introduced in EDRs. | 2021.01.0 |
| First introduced. | 2020.02.0 |
The Network Address Translation (NAT) feature translates non-routable private IP addresses to routable public IP addresses from a pool of public IP addresses.
UPF supports NAT on the N4 interface to configure network addresses and send NAT binding records to N4. The NAT policy and IP pool for NAT public IP addresses are configured on UPF for N4.
For more information, refer to the UCC 5G UPF Configuration and Administration Guide > Deep Packet Inspection and Inline Services chapter.
| Applicable Product(s) or Functional Area | 5G-UPF |
| Applicable Platform(s) |
VPC-SI |
| Feature Default Setting | Disabled - Configuration Required |
| Related Changes in this Release | Not Applicable |
| Related Documentation | UCC 5G UPF Configuration and Administration Guide |
| Revision Details | Release |
|---|---|
|
UPF supports Recalculate IE on the N4 interface for PGWCDR generation. |
2023.04.0 |
UPF supports the Recalculate Measurement custom IE as received over the N4 interface. This IE is added to the Update-URR process (URR-ID: Gz-Bearer) to support the PGW-CDR generation due to the max_LOSDV change condition.
For more information, refer to the UCC 5G UPF Configuration and Administration Guide > Charging Support chapter.
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
UP now sends the PFCP error cause code PFCP_CAUSE_NO_RESOURCE_AVAILABLE in the following failure scenarios during:
Sx Establishment Request and Sx Modification request message processing
Bearer stream creation failure for Sxa
TEP row add failure for Sxa
Local local_gtpu_endpt address mismatch or unavailable
Above failure scenarios for N4 visited call
PFCP_IE_QGR_INFO IE processing memory failures
NAT rulebase change or policy change cases and failure due to
FW-and-NAT policy initilization failure during call setup or rulebase change
Invalid clp destination context
Memory allocation failure
Sx Establishment or Sx Modification message processing – local GTPU TEID allocation failure
Previous Behavior: UP sent the error cause PFCP_CAUSE_REQUEST_REJECTED for the above failure scenarios.
New Behavior: UP sends the error cause PFCP_CAUSE_NO_RESOURCE_AVAILABLE instead of PFCP_CAUSE_REQUEST_REJECTED for the above failure scenarios.
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
Previous Behavior: The Old Roaming Status field in the output of the show subscribers user-plane-only full all command was defined for both intra-PLMN and inter-PLMN handover.
New Behavior: The Old Roaming Status field in the output of the show subscribers user-plane-only full all command is applicable for inter-PLMN handover only. This field will not be defined for intra-PLMN HO.
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
Previous Behavior: During an error scenario where incorrect IMSI is used due to wrong TEID for the same UPF combo call, handover used to pass.
New Behavior: If IMSI mismatches during the same UPF combo call handover, then Handover Modify Request fails with offending IE Outer Header Creation (OHC).
Customer Impact: The customer will observe handover failure in the error scenario.
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
The behavior of UPF has changed in the following scenarios for a converged core call when:
N4 and SxA are on the same UPF
S-GW relocation is triggered where target SGW-u is same as that of source SGW-u
SMF initiates N4 Modification to update downlink FAR with new TEID and IP
UPF uses the TEID and finds the target Sxa session
Previous Behavior: If the Sxa session was not found, then UPF updated FAR and retained the N4 call as combo only.
New Behavior: UPF inspects SMGR-ID in TEID:
1. If SMGR-ID in TEID does not match, then UPF marks the N4 call as non-combo and updates FAR.
2. If SMGR-ID matches and the corresponding Sxa session is not present, then UPF rejects N4 Modification with cause Mandatory IE Incorrect and faulty IE Outer Header Creation.
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI SMI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
UCC 5G UPF Configuration and Administration Guide |
|
Revision Details |
Release |
|---|---|
|
The number of Sx/N4 peer nodes is increased from 16 to 18. |
2023.04.0 |
|
First introduced. |
2021.01.0 |
A single UPF can establish multiple N4 or Sx interfaces with any number of control plane network functions such as SMF, cnSGWc, SAEGW-C, PGW-C, and SGW-C. The maximum number of supported N4 or Sx peer nodes has been increased from 16 nodes to 18 nodes in this release.
For more information, refer to the UCC 5G UPF Configuration and Administration Guide > Roaming Support chapter.
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
UCC 5G UPF Configuration and Administration Guide |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
UPF uses TLS for protection of X3 traffic towards the mediation server (MDF).
For more information on this feature, contact your Cisco account representative.
|
Applicable Product (s) or Functional Area |
5G-UPF |
|
Applicable Platforms |
VPC-SI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
UCC 5G UPF Configuration and Administration Guide |
|
Revision Details |
Release |
|---|---|
|
First introduced. |
2023.04.0 |
The Wireless Priority Services (WPS) feature provides finer control for priority handling over multiple interfaces in UPF and RCM.
UPF supports WPS services based on the message priority indicated by SMF. The configured priority value set on SMF will be sent to UPF over N4 as part of the PFCP header. For more information, refer to the UCC 5G UPF Configuration and Administration Guide > WPS Prioritization on RCM and UPF chapter.
RCM supports WPS prioritization based on the priority determined between UPF and RCM. Earlier, RCM supported up to 4 queues with precedence values of 1, 2, 3, and 0 (no precedence) to create corresponding queues with the same session priority. Now, it is extended to 5 queues with precedence values of 1, 2, 3, 4, and 0 (no precedence). The session-priority-profile configuration (UPF) maps the received session priority (0–15) to precedence values 1-4. For more information, refer to the UCC 5G RCM Configuration and Administration Guide > WPS Prioritization on RCM chapter.
Feedback