5G Converged Core Session Management Function

Introduction

This Release Notes identifies changes and issues related to this software release.

Release Lifecycle Milestones

Release Lifecycle Milestone

Milestone

Date

First Customer Ship

FCS

30-Apr-2024

End of Life

EoL

30-Apr-2024

End of Software Maintenance

EoSM

29-Oct-2025

End of Vulnerability and Security Support

EoVSS

31-Oct-2025

Last Date of Support

LDoS

31-Oct-2026

These milestones and the intervals between them are defined in the Cisco Ultra Cloud Core (UCC) Software Release Lifecycle Product Bulletin available on cisco.com.

Release Package Version Information

Software Packages

Version

ccg-2024.02.2.SPA.tgz 2024.02.2
NED package

ncs-5.6.8-ccg-nc-2024.02.2

ncs-6.1-ccg-nc-2024.02.2

NSO

5.6.8

6.1.3

Descriptions for the various packages provided with this release Release Package Descriptions section.

Verified Compatibility

What's New in This Release

Features and Enhancements

There are no new features and enhancements in this release.

Behavior Changes

This section covers a brief description of behavior changes introduced in this release.

Behavior Change Description

Handling FHT Terminate Sub Action in CCA-I

Previous Behavior: SMF terminates the session without sending the Gy CCR-T whenever the Gy CCR-I has failed with FHT action Terminate and sub action WITH_TERM_REQUEST.

New Behavior: SMF terminates the session and sends the Gy CCR-T whenever the Gy CCR-I fails with FHT action Terminate and sub action WITH_TERM_REQUEST.

Validity Time and Volume/Time Quota Threshold Usage for FUI URR

Previous Behavior: SMF used to initially trigger CCR-U whenever exhaustion of volume or time quota is reported by UPF for any FUI MSCC. SMF reports the usage in Gy-CCRU to OCS without RSU and subsequently terminates the PDU session.

When SMF receives time quota threshold usage from UPF for FUI URR, it neither terminates the PDU session nor request any further quota.

New Behavior: For FHT with Continue action, SMF terminates the PDU session immediately after receiving quota exhaustion for any FUI URR and reports the final usage to OCS through Gy-CCRT if CLI is configured to terminate the session or had received command level FUI. SMF sends Gy-CCRT to OCS with Termination Cause "DIAMETER-ADMINISTRATIVE" and MSCC Reporting reason as "FINAL".

If the usage report is received due to volume/time threshold or validity time, SMF reports the usage report only through Gy-CCR-U and continues to request for further quota.

When both time quota and validity time are received and the time quota exceeds validity time or when validity time alone is received without time quota, then SMF sends Gy-CCRU with MSCC reporting reason as "VALIDITY-TIME" and requests further quota.

Quota Allocation for Online FUI and non-FUI URRs

Previous Behavior: SMF used to allocate the maximum quota only to non-FUI online URRs for a FHT with Continue action and None/Unknown sub-action. SMF sends Gy-offline-flag to UPF setting it to True.

New Behavior: SMF allocates the maximum quota to both FUI and non-FUI online URRs after FHT with Continue action and None/Unknown sub-action. SMF subsequently sends Gy-offline-flag to UPF with the flag set to True.

Installation and Upgrade Notes

This Release Note does not contain general installation and upgrade instructions. Refer to the existing installation documentation for specific installation and upgrade considerations.

Software Integrity Verification

To verify the integrity of the software image you have from Cisco, you can validate the SHA512 checksum information against the checksum identified by Cisco for the software.

Image checksum information is available through Cisco.com Software Download Details. To find the checksum, hover the mouse pointer over the software image you have downloaded.

At the bottom you find the SHA512 checksum, if you do not see the whole checksum you can expand it by pressing the "..." at the end.

To validate the information, calculate a SHA512 checksum using the information in Table 1 and verify that it matches either the one provided on the software download page.

To calculate a SHA512 checksum on your local desktop, refer to the table below.

Table 1. Checksum Calculations per Operating System

Operating System

SHA512 checksum calculation command examples

Microsoft Windows

Open a command line window and type the following command:

> certutil.exe -hashfile filename.extension SHA512

Apple MAC

Open a terminal window and type the following command:

$ shasum -a 512 filename.extension

Linux

Open a terminal window and type the following command:

$ sha512sum filename.extension

OR

$ shasum -a 512 filename.extension

Note

 

filename is the name of the file.

extension is the file extension (for example, .zip or .tgz).

If the SHA512 checksum matches, you can be sure that no one has tampered with the software image or the image has not been corrupted during download.

If the SHA512 checksum does not match, we advise you to not attempt upgrading any systems with the corrupted software image. Download the software again and verify the SHA512 checksum again. If there is a constant mismatch, please open a case with the Cisco Technical Assistance Center.

Certificate Validation

SMF software images are signed via x509 certificates. Please view the .README file packaged with the software for information and instructions on how to validate the certificates.

Open Bugs for This Release

There are no open bugs in this release.

Resolved Bugs for This Release

The following table lists the known bugs that are resolved in this specific software release.


Note


This software release may contain bug fixes first introduced in other releases. Additional information for all resolved bugs for this release are available in the Cisco Bug Search Tool.


Bug ID

Headline

Behavior Change

CSCwj49267 cnpgw shall handle Terminate SubAction in CCA-I Response Yes
CSCwj75299 SMF is showing higher ip pool utilization than the actual subs count on the node No
CSCwj92088 Quota Push from OCS fails when GyCCA-I has MSCC without ResultCode No
CSCwj98574 Call is terminated when OCS sends FUI(terminate) + MSCC ResultCode absent in Gy CCAU Yes
CSCwk25421 CCR-T from CCG is not getting accepted by OCS No
CSCwk28976 Session not getting terminated bec of FUI when UPF reports volth and volqu at the sametime Yes
CSCwk35703 Gx Termination cause is incorrect when session gets terminated because of Gy FUI No

Operator Notes

Cloud Native Product Version Numbering System

The show helm list command displays detailed information about the version of the cloud native product currently deployed.

The appropriate version number field increments after a version has been released. The new version numbering format is a contiguous sequential number that represents incremental changes between releases. This format facilitates identifying the changes between releases when using Bug Search Tool to research software releases.

Release Package Descriptions

The following table provides descriptions for the packages that are available with this release.

Table 2. Release Package Information

Software Packages

Description

ccg.<version>.SPA.tgz

The SMF offline release signature package. This package contains the SMF deployment software, NED package, as well as the release signature, certificate, and verification information.

ncs-<nso_version>-ccg-nc-<version>.tar.gz

The NETCONF NED package. This package includes all the yang files that are used for NF configuration.

Note that NSO is used for the NED file creation.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, refer to https://www.cisco.com/c/en/us/support/index.html.