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. |
|
Features / Behavior Changes |
Release Introduced / Modified |
Default |
|---|---|---|
|
2023.04.0 |
Disabled – Configuration required to enable |
|
|
2023.04.0 |
Not Applicable |
|
|
Call Handling in the Absence of PCF Configuration in DNN Profile |
2023.04.0 |
Not Applicable |
|
2023.04.0 |
Not Applicable |
|
|
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 |
Enabled – Always-on |
|
|
2023.04.0 |
Enabled – Always-on |
|
|
2023.04.0 |
Enabled – Always-on | |
|
2023.04.0 |
Disabled – Configuration required to enable |
|
|
Non-Standard PLMN List Configuration for MccMncExceptionList Dynamic Update |
2023.04.0 |
Disabled – Configuration required to enable |
|
2023.04.0 |
Enabled – Always-on |
|
|
2023.04.0 |
Disabled - Configuration required to enable |
|
|
Routing CCR-U/CCR-T Message to the Bounded Peer from CCR-I/U or CCA-I/U Message |
2023.04.0 |
Enabled – Always-on |
|
2023.04.0 |
Disabled – Configuration Required |
|
|
Statistics Updates for Internal Transaction Triggered for RAR Scenario |
2023.04.0 |
Not Applicable |
|
2023.04.0 |
Disabled – Configuration required to enable |
|
|
Wait Time Display for Ongoing Bulk clear Subscriber CLI and Blocking the Consecutive CLI |
2023.04.0 |
Enabled – Always-on |
|
2023.04.0 |
Enabled – Configuration required to disable |
| Applicable Product(s) or Functional Area | SMF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Enabled – Always-on |
| Related Changes in this Release | Not Applicable |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
|
First Introducted. |
2023.04.0 |
SMF provides the following support for 3GPP R16 specification compliance:
SMF decodes the ePCO IE in PDU session establishment request to:
Check the UE support for QoS rules and QoS descriptions with the ePCO length of two octets option in the PDU Session establishment request. It is used during 4G modification for encoding QoS rules and QoS descriptions in the ePCO IE for EPS interworking.
Indicates the local IP address in TFT in S1 node for a PDU session during 5G-4G internetworking.
SMF supports semantic and syntactic error handling for the QoS Rules and Qos description or for mapped EPS Bearer Contexts errors from the UE.
SMF handles CB or UB responses with ePCO containing 5GSM cause and all the cases for emergency sessions where the AMF rejects N1 PDU Session Modify request received by sending N1 PDU Session Modify reject.
Mandates the MFBR validation while receiving the GBR flow creation or QoS modification from PCF.
Updated the event management CLI with the event names, actiondef and ruledef for the configuration of 4G and 5G error handling.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > EPS Networking chapter.
|
Applicable Product or Functional Area |
SMF |
|
Applicable Platform |
SMI |
|
Feature Default Setting |
Not Applicable. |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
Enhanced the High Availability Redundancy support to minimize the session loss during application VIP switchover between master nodes. |
2023.04.0 |
|
Support added for the following sub-features:
|
2023.03.0 |
|
Support added for Maintenance Mode. |
2021.04.0 |
|
Geographic Redundancy (GR) support introduced. |
2021.02.0 |
|
First introduced. |
Pre-2020.02.0 |
In the High Availability redundancy support, there is session loss whenever an application VIP's switch over from Master-1 node to Master-2 node or vice versa, due to any unhealthy application or BGP/BFD link downtime with a leaf or due to any other fault on the active Master node.
The High Availability redundancy support is enhanced in SMF in a way that when the gRPC IPC stream breaks, the App-Infra library re-tries immediately and the IPC connection is re-established between gRPC endpoints within milliseconds.
This helps avoid the session loss during the VIP switchovers.
For more information, see the UCC 5G SMF Configuration and Administration Guide > Redundancy Support chapter.
| Applicable Product(s) or Functional Area | SMF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Disabled – Configuration Required |
| Related Changes in this Release | Not Applicable |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
|
2023.04.0 |
|
Added support for the following features:
|
2023.01.0 |
|
Added support for SMF—
|
2022.04.0 |
|
Introduced support for Diff-Serv-Code-Point (DSCP) or Type of Service (ToS) QoS functions during interaction with PCF. |
2021.02.3.t3 |
|
Introduced support for the following features:
|
2021.02.3 |
|
Introduced support for non-standard QCI for dynamic PCC and session rules |
2021.02.2 |
|
Introduced support for the following features:
|
2021.02.0 |
|
Introduced support for the following:
|
2021.01.0 |
|
Introduced support for the following:
|
2020.03.0 |
|
First introduced. |
Pre-2020.02.0 |
Previous Behavior: SMF mandated the configuration of PCF/PCRF in DNN profile even when the local policy was configured through the pcf-interaction command.
New Behavior: PCF or PCRF configuration remains optional if the local policy is configured. Subscriber call setup is successful even in the absence of PCF or PCRF configuration in DNN profile.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Policy and User Plane Management chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
Added support for:
|
2023.04.0 |
|
Added support for:
|
2023.03.0 |
|
Added support for:
|
2023.02.0 |
|
Added support for:
|
2022.04.0 |
|
Added support for configuration-based control of UDM and PCF messages. |
2021.02.3.t3 |
|
Added support for N2 cause and diagnostic IEs. |
2021.02.3 |
|
Added support for:
|
2021.02.0 |
|
First introduced. |
Pre-2020.02.0 |
To define the failure handling behaviour, SMF supports the the Credit-Control-Failure-Handling Attribute Value Pair (AVP). The Online Charging Server (OCS) sends this AVP to the Diameter endpoint. The Diameter endpoint uses the value of this AVP to derive the Gy request failure handling behavior. This scenario is applicable when the requests are prevented due to a network problem.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Interfaces Support chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Not Applicable |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
First introduced. |
2023.04.0 |
Previous Behavior: SMF did not trigger the N1N2 setup request on the N11 interface when SMF received the Downlink Data Request (DLDR) in the N3 activated state. The difference in the upContext state between SMF and UPF resulted in UPF triggering the DLDR. With the N3 in inactive state, UPF used to send the session report request to SMF.
New Behavior: The new CLI command reactivate-n3-on-dupl-activation-dldr is added in the supported features at SMF to reactivate the N3 when DLDR is received in the N3 activated state. After this CLI is enabled and if the DLDR is received in the ACTIVATED state, then SMF changes the upState to DEACTIVATED and reactivates the N3 connection.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > UP Session Activation and Deactivation Service Request Procedures.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Not Applicable |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
Added support for DRB level data forwarding in IDFT during N2-based handover. |
2023.04.0 |
|
First introduced. |
Pre-2020.02.0 |
In the Inter NG-RAN Node N2-based Handover-Execution phase during the indirect data forwarding process, when the SMF receives a Handover Request Acknowledge, it validates whether it meets the criteria for Session Level Forwarding.
In case the Handover Request Acknowledge message does not meet the criteria for Session Level Forwarding, and if a Data forwarding response DRB List is present, SMF proceeds with the DRB Level Forwarding.
For more information, see the UCC 5G SMF Configuration and Administration Guide > Handover Procedures chapter.
| Applicable Products or Functional Area | SMF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Enabled – Always-on |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
|
Added the wait time display for ongoing bulk clear subscriber CLI and blocking the consecutive CLI. |
2023.04.0 |
|
Added the following support:
|
2023.03.0 |
|
As part of the IP pool allocation per slice and DNN feature, added example configuration to configure NSSAI labels of smf_service_stats metrics. |
2022.04.0 |
|
Introduced support for classification and configuration of application metrics |
2021.02.3 |
|
Added support for the following enhancements:
|
2021.02.2 |
|
Added support for the following enhancements:
|
2021.02.0 |
|
First introduced. |
Pre-2020.02.0 |
Previous Behavior: Diameter peer was considered down only if sending Device Watchdog Request (DWR) failed. Even if the Device Watchdog Answer (DWA) was not received or was received with error result-code, the peer was not considered in the error state.
New Behavior: In addition to the failure in sending DWR, even if the DWA is not received or is received with error result-code, then also peer is considered to be in error state.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Diameter Endpoint chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Product(s) or Functional Area |
SMI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
2023.04.0 |
|
Added support for the following features:
|
2023.01.0 |
|
Added support for SMF—
|
2022.04.0 |
|
Introduced support for Diff-Serv-Code-Point (DSCP) or Type of Service (ToS) QoS functions during interaction with PCF. |
2021.02.3.t3 |
|
Introduced support for the following features:
|
2021.02.3 |
|
Introduced support for non-standard QCI for dynamic PCC and session rules |
2021.02.2 |
|
Introduced support for the following features:
|
2021.02.0 |
|
Introduced support for the following:
|
2021.01.0 |
|
Introduced support for the following:
|
2020.03.0 |
|
First introduced. |
Pre-2020.02.0 |
SMF allows creating dedicated GBR bearers for 4G and 5G without PCF interaction, using the local policy configuration. This feature creates two bearers:
Default Non-GBR Bearer The default bearer/flow is created based on the QoS received from UDM (in case of NR) or MME (in case of E-UTRA).
Dedicated GBR Bearer: Dedicated GBR flows/bearers are additionally created based on local policy configuration.
For more information, see the UCC 5G SMF Configuration and Administration Guide > Policy and User Plane Management chapter.
| Applicable Products or Functional Area | SMF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Enabled – Always-on |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
|
Added the Gx and Gy custom dictionary support for RAR messages. |
2023.04.0 |
| First introduced. | 2023.03.0 |
SMF extends the custom dictionary support for Re-Authorization Request (RAR) messages in addition to the existing dictionary support for the Credit Control - Initial (CCR-I), Credit Control - Update (CCR-U), and Credit Control - Terminate (CCR-T) messages.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Diameter Endpoint chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
Added support for:
|
2023.04.0 |
|
Added support for:
|
2023.03.0 |
|
Added support for:
|
2023.02.0 |
|
Added support for:
|
2022.04.0 |
|
Added support for configuration-based control of UDM and PCF messages. |
2021.02.3.t3 |
|
Added support for N2 cause and diagnostic IEs. |
2021.02.3 |
|
Added support for:
|
2021.02.0 |
|
First introduced. |
Pre-2020.02.0 |
SMF allows the following functionalities over Gz Interface:
Modify Bearer Request Triggers: SMF receives the Modify Bearer Request from S-GW for the User Location and TimeZone changes, change notifications. SMF supports N4 Query Interface and Recalculate Interface IEs for Rulebase change, Secondary RAT Usage limit, and Record closing triggers.
Gz Bearer Modification: PCRF-initiated modification of a default Bearer through Gx CCR-U and Gx RAR. You can perform the following functions:
Add rules to the Default Bearer
Delete rules from the Default Bearer
Rulebase Modification
Asynchronous and Synchronous Usage Report for Offline Bearer Recalculation: SMF receives Asynchronous and Synchronous Usage Reporting for Offline Bearer recalculation.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Interfaces Support chapter.
SMF allows the following functionalities over Gy interface enhancements:
Final Unit Indication (FUI) support in CCR-U: As part of Gy Usage Reporting, SMF supports FUI in CCA-U from OCS. FUI is enabled during the session creation or update. After FUI activation, when there is any update triggers due to an event trigger or Usage report, SMF sends subsequent CCR-U toward OCS without requesting further Quota and receives CCA-U.
Failure Handling Template (FHT) Enhancement: During the Modify Bearer Request procedure, if there are N4 Modification Query URR, Gy CCR-U (Usage), or Gy CCA-U (failure) instances, the FHT action is Continue. The FHT subaction is Unknown or None. In this scenario, SMF allocates High Quota with no Gy CCR-T during detach. There is no Gy CCR-U during any trigger/update.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Subscriber Charging chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
Added support for:
|
2023.04.0 |
|
Added support for:
|
2023.03.0 |
|
Added support for:
|
2023.02.0 |
|
Added support for:
|
2022.04.0 |
|
Added support for configuration-based control of UDM and PCF messages. |
2021.02.3.t3 |
|
Added support for N2 cause and diagnostic IEs. |
2021.02.3 |
|
Added support for:
|
2021.02.0 |
|
First introduced. |
Pre-2020.02.0 |
The SMF handles the periodic Secondary RAT data volume report messages from the MME over the S5 or S8 interface in the Modify Bearer Request, Change Notification Request, Delete Session Request, and Delete Bearer Response based on the Intended Receiver PGW-C (IRPGW) flag. SMF retains the Usage-Report if IRPGW = 1.
The SMF supports multiple instances of Secondary RAT Usage Data Report IEs. It stores reports until they are sent out to OFCS based on the triggers. SMF sends out the stored secondary RAT usage data report through gtpp-ep endpoint when any of the charging triggers are met.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Interfaces Support chapter.
| Applicable Product(s) or Functional Area | SMF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Enabled – Always-on |
| Related Changes in this Release | Not Applicable |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
|
Added the following support:
|
2023.04.0 |
|
Added the following support:
|
2023.03.0 |
|
Added support for:
|
2023.02.0 |
|
FB Call Continuity Cause Code Expansion |
2021.02.2 |
|
Added support for:
|
2021.02.0 |
|
Introduced procedure to support dynamic configuration of the Access Profile configuration. |
2020.03.0 |
|
New CLI command in the DNN profile configuration to reject calls from 4G-only UE devices. |
2020.02.1 |
| First introduced. |
Pre-2020.02.0 |
The HSS Initiated Bearer QoS Modification procedure is used in one or several of the EPS Bearer QoS parameters. For example, the EPS Bearer QoS parameters can be QCI or the ARP of the default EPS Bearer. If the HSS changes the default Bearer QCI or the ARP and APN-AMBR, the HSS initiates such message to the MME, which then generates the Modify Bearer Command (MBC) toward the P-GW through S-GW.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > EPS Interworking chapter.
| Applicable Product(s) or Functional Area | SMF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Disabled – Configuration Required |
| Related Changes in this Release | Not Applicable |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
|
2023.04.0 |
|
Added support for the following features:
|
2023.01.0 |
|
Added support for SMF—
|
2022.04.0 |
|
Introduced support for Diff-Serv-Code-Point (DSCP) or Type of Service (ToS) QoS functions during interaction with PCF. |
2021.02.3.t3 |
|
Introduced support for the following features:
|
2021.02.3 |
|
Introduced support for non-standard QCI for dynamic PCC and session rules |
2021.02.2 |
|
Introduced support for the following features:
|
2021.02.0 |
|
Introduced support for the following:
|
2021.01.0 |
|
Introduced support for the following:
|
2020.03.0 |
|
First introduced. |
Pre-2020.02.0 |
With the N7 optimization support, the SMF skips the N7 Update message by sending the UE IP address in the N7 Create message. After you enable this feature, the SMF allocates the IP address and performs the UPF selection before connecting with the PCF. If you have configured the SMF to select an alternate UPF that needs IP reallocation, then during the N4 failure, the SMF sends an N7 Update message after the N4 Success message to indicate the new IP address.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Policy and User Plane Management chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Product(s) or Functional Area |
SMI |
|
Feature Default Setting |
Enabled – Always-on |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
Added the N10 fail open support. |
2023.04.0 |
|
First introduced. |
2020.02.2 |
This feature provides the following support:
Fail open for ignore and continue failure handling actions as well for the call during the N10 message failures.
Interaction with SCP Model-D.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > UDM Integration chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
|
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
Added support for the following features:
|
2023.04.0 |
|
Added support for the following features:
|
2023.03.0 |
|
Nexthop forwarding address configuration added to IPv6 address range and prefix range. |
2023.01.4 |
|
Added support for the following features:
|
2023.01.0 |
|
Added support for the following features:
|
2022.04.0 |
|
Added support for the following features:
|
2021.02.0 |
|
IP Address Validation with CDL Configuration introduced. |
2021.02.0 |
|
Updated quarantine time range to 3600 seconds. |
2021.02.0 |
|
VRF Support introduced. |
2020.02.5 |
|
First introduced. |
Pre-2020.02.0 |
Network Address Translation (NAT) is a service that enables private IP networks to use the internet and cloud. NAT translates private IP addresses in an internal network to a public IP address before packets are sent to an external network. This helps to save IP addresses and improve security.
When NAT is enabled on the UPF, external platforms require the real-time NAT binding updates. This allows the mapping of private IP address to public IP address used on the Gi interface to be provided to external platforms.
SMF supports NAT Binding Record functionality where, N4 Session Report Request Message is used for providing NAT Binding Record Information from UPF to SMF. After SMF receives NAT Binding Record Information from UPF, it sends the corresponding NAT Binding Updates to the AAA Server over the RADIUS interface.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > IP Address Management chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
Added the non-standard PLMN list configuration. |
2023.04.0 |
|
Removed the visitor-hrt CLI keyword from the configuration in Operator Policy. |
2021.02.3 |
|
First introduced. |
2021.01.0 |
Previous Behavior: No CLI command existed for the non-standard PLMN values.
New Behavior: The new non-standard-plmn-list CLI command is added in the SMF profile. Use this command to enable SMF to update MccMncExceptionList dynamically.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Multiple PLMN Support chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
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: At the time of GTPv2 MBReq message processing, Modify Bearer Request (MBR) from a Visitor PLMN (V-PLMN) or any PLMN was accepted by PGW-C+SMF.
New Behavior: If the inter-plmn CLI is not configured in PGW-C+SMF, MBR from a V-PLMN is rejected by PGW-C+SMF. To handle handovers from V-PLMN, configuring the inter-plmn-ho in the DNN profile is mandatory.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Roaming Support chapter.
| Feature Name |
Release Information |
Description |
|---|---|---|
|
N4 Resource or Association Release |
2023.04 |
SMF supports clearing resources with respect to a particular UPF from the SMF using a CLI release-resource . |
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Disabled-Configuration required to enable. |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
Added support for the following features:
|
2023.04.0 |
|
Added support for the following features:
|
2023.03.0 |
|
Nexthop forwarding address configuration added to IPv6 address range and prefix range. |
2023.01.4 |
|
Added support for the following features:
|
2023.01.0 |
|
Added support for the following features:
|
2022.04.0 |
|
Added support for the following features:
|
2021.02.0 |
|
IP Address Validation with CDL Configuration introduced. |
2021.02.0 |
|
Updated quarantine time range to 3600 seconds. |
2021.02.0 |
|
VRF Support introduced. |
2020.02.5 |
|
First introduced. |
Pre-2020.02.0 |
SMF introduces a CLI release-resource that triggers and automates N4 associations or resources releasing process per UPF from the SMF. As part of this feature, SMF performs two primary functions when release-resource is triggered:
It clears all the IP pools associated to the peer.
It clears the calls using the pool.
It deletes the routes.
A new call disconnect reason is added to the SMF Disconnect Statistics. Also, the routes are re-registered with UPF post a quarantine time of 2 minutes.
For more information, see the UCC 5G SMF Configuration and Administration Guide > IP Address Management chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
Added VRF support for Diameter interfaces. |
2023.04.0 |
|
The following enhancements are introduced:
|
2023.01.0 |
|
Support overlapping AAA server addresses for PAPN use case |
2022.04.0 |
|
First introduced. |
2020.02.5 |
Previous Behavior: No bounded peer existed.
New Behavior: Peer with which the last CCR-I/U interaction happened is considered as the bounded peer. Route matching the bounded peer is given the highest priority for sending subsequent CCR-U/T messages.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Diameter Endpoint chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Not Applicable |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
First introduced. |
2023.04.0 |
Previous Behavior: When the Modify Bearer Request (MBR) or Modify Bearer Command (MBC) triggered RADIUS update towards RADIUS accounting server, the procType label was updated as PDU Session Modify - SMF initiated.
For Gy metrics, proc_name label displayed the PDU Session Modify - SMF initiated value.
New Behavior: The new statistics PDN Session Modify - PCRF initiated is added for this scenario.
For more information, refer to the UCC 5G Session Management Function, Statistics Reference > SMF Metrics chapter.
| Applicable Product(s) or Functional Area | SMF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Disabled – Configuration Required |
| Related Changes in this Release | Not Applicable |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
|
First introduced. |
2023.04.0 |
Previous Behavior: If the predefined rules are mapped to a dedicated flow/bearer, the SMF did not send the Create QER Request to the UPF.
New Behavior: If the predefined rules are mapped to a dedicated flow/bearer, the SMF sends the Create QER Request for both default and dedicated flows to the UPF.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Policy and User Plane Management chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
Added VRF support for Diameter interfaces. |
2023.04.0 |
|
The following enhancements are introduced:
|
2023.01.0 |
|
Support overlapping AAA server addresses for PAPN use case |
2022.04.0 |
|
First introduced. |
2020.02.5 |
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Diameter Endpoint and Virtual Routing and Forwarding Function chapters.
|
Applicable Product(s) or FunctionalArea |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Not Applicable |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
| Revision Details | Release |
|---|---|
|
Added the wait time display for ongoing bulk clear subscriber CLI and blocking the consecutive CLI. |
2023.04.0 |
|
Added the following support:
|
2023.03.0 |
|
As part of the IP pool allocation per slice and DNN feature, added example configuration to configure NSSAI labels of smf_service_stats metrics. |
2022.04.0 |
|
Introduced support for classification and configuration of application metrics |
2021.02.3 |
|
Added support for the following enhancements:
|
2021.02.2 |
|
Added support for the following enhancements:
|
2021.02.0 |
|
First introduced. |
Pre-2020.02.0 |
Previous Behavior: The Ops Center didn't display the expected waiting time for an ongoing bulk clear subscriber CLI command. In addition, you could run the clear subscriber CLI while the processing of the earlier CLI was still in progress.
New Behavior: The Ops Center displays the expected waiting time for an ongoing bulk clear subscriber CLI command. In addition, the clear subscriber CLI gets blocked while the processing of the earlier CLI is in progress.
Customer Impact: Ease of use and maintenance in processing of the subcriber profiles.
For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Troubleshooting Information chapter.
|
Applicable Product(s) or Functional Area |
SMF |
|
Applicable Platform(s) |
SMI |
|
Feature Default Setting |
Disabled – Configuration Required |
|
Related Changes in this Release |
Not Applicable |
|
Related Documentation |
Not Applicable |
|
Revision Details |
Release |
|---|---|
|
Enhancements to SBI Message Priority Mechanism and Message-Prioritization based on Procedures |
2023.04.0 |
|
5QI Mapping support introduced |
2023.03.0 |
|
UPF Interaction while Deleting WPS Dynamic Rule |
2021.01.0 |
|
SBI Message Priority Mechanism and Message-Prioritization based on Procedures are introduced. |
2021.01.0 |
|
The Wireless Priority Services feature is fully qualified in this release. |
2020.03.0 |
|
First introduced. This feature is not fully qualified in this release. For more information, contact your Cisco Account representative. |
2020.02.0 |
The primary usage of SBI Message Priority (SMP) is to provide guidance to 5GC NF acting as HTTP/2 clients or servers while making throttling decisions related to overload control. You can use the priority information for routing in the proxies. Eventually a server uses the priority information to process higher-priority requests before lower-priority requests. The SMP mechanism uses the "3gpp-Sbi-Message-Priority" custom HTTP header to set and carry the message priority between the client and the server. The custom HTTP header enforces the message priority end to end between the client and the server through one or more proxies.
Note |
Stream Priority mechanism is not supported. |
3gpp-Sbi-Message-Priority = "3gpp-Sbi-Message-Priority" ":" (DIGIT / %x31-32 DIGIT / "3" %x30-31)3gpp-Sbi-Message-Priority "0"3gpp-Sbi-Message-Priority: 10For more information, refer to the UCC 5G SMF Configuration and Administration Guide > Wireless Priority Services chapter.
Feedback