Ultra Cloud Core Access and Mobility 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-2025 |
|
End of Life |
EoL |
30-Apr-2025 |
|
End of Software Maintenance |
EoSM |
29-Oct-2026 |
|
End of Vulnerability and Security Support |
EoVSS |
29-Oct-2026 |
|
Last Date of Support |
LDoS |
31-Oct-2027 |
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 |
|---|---|
| amf.2025.02.0.SPA.tgz | 2025.02.0 |
| cdl-1.12.1-amf-2025.02.0.SPA.tgz | 1.12.1 |
| NED package | ncs-6.4.3-amf-nc-2025.02.0 |
| NSO |
6.4.3 |
Descriptions for the various packages provided with this release are available in the Release Package Descriptions section.
Verified Compatibility
|
Products |
Version |
|---|---|
|
Ultra Cloud Core SMI |
2025.02.1.17 |
|
Ultra Cloud CDL |
1.12.1 |
For more information on the Ultra Cloud Core SMI, refer to the documents for this release available at:
What's New in this Release
Features and Enhancements
This section covers a brief description of the features and enhancements introduced in this release.
| Feature | Description | ||
|---|---|---|---|
|
AMF includes functionality to facilitate location services for Network Induced Location Requests, ensuring compliance and improving service capabilities. Command introduced: location lmf-positioning ni-lr — Used to to enable NI-LR for location services. Default Setting: Disabled – Configuration Required |
|||
|
Location Services - Compliance to 3GPP Specification Revision 18 |
MT-LR and NI-LR supports revision 18.6 of the 3GPP specification. This update with the latest revision ensures compliance with the most current regulatory requirements. Command introduced: profile compliance compliance_profile_name { service service_name { version spec 3gpp_spec_version } } — Used to configure the 3gpp spec compliance version for namf-loc and nlmf-loc. Default Setting: Disabled – Configuration Required |
||
|
NF Discovery based on Preferred Locality |
AMF includes the "3gpp-Sbi-Discovery-preferred-locality" HTTP header when communicating with the SCP. By populating this header, AMF enables more efficient NF selection based on locality during peer NF discovery, resulting in optimized network function interactions and improved service delivery.
|
Behavior Changes
This section covers a brief description of behavior changes introduced in this release.
| Behavior Change | Description |
|---|---|
|
HTTP header "3gpp-Sbi-Discovery-service-names" in SCP Model D Indirect Communication |
Previous Behavior: The AMF used to send the "3gpp-Sbi-Discovery-service-names" HTTP header to the SCP in an array format for all messages. Example: 3gpp-sbi-discovery-service-names : ["nsmf-pdusession"] New Behavior: The "3gpp-Sbi-Discovery-service-names" HTTP header is now sent as a plain string to the SCP, but only when you configure the discovery-params [ service-names ] within the SCP network element profile. Example: 3gpp-sbi-discovery-service-names : nsmf-pdusession |
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.
Certificate Validation
AMF 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.
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 will find the SHA512 checksum. If you do not see the whole checksum, you can expand it by pressing "..." 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.
|
Operating System |
SHA512 checksum calculation command examples |
||
|---|---|---|---|
|
Microsoft Windows |
Open a command line window and type the following command:
|
||
|
Apple MAC |
Open a terminal window and type the following command:
|
||
|
Linux |
Open a terminal window and type the following command:
OR
|
||
|
|||
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.
Open Bugs for this Release
The following table lists the open bugs in this specific software release.
 Note |
This software release may contain open bugs first identified in other releases. Additional information for all open bugs for this release is available in the Cisco Bug Search Tool. |
|
Bug ID |
Headline |
|---|---|
|
Service pod memory leak seen after SCTP pod kill. |
Resolved Bugs for this Release
The following table lists the resolved bugs 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 |
|---|---|---|
|
"error: [DatastoreUpdate] 413 : Unique keys exceeded the limit" during Perf longevity for MobiltyReg |
No | |
|
LI events are not generating post LI pod kill |
No |
|
|
AMF does not handle Error Indication received from gNB appropriately |
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.
|
Software Packages |
Description |
|---|---|
|
amf.<version>.SPA.tgz |
The offline release signature package. This package contains the AMF deployment software, NED package, as well as the release signature, certificate, and verification information. |
|
ncs-<nso_version>-amf-<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.
Feedback