Duplicate Static IP Detection and Resolution

This feature provides a mechanism to handle error scenarios where the same static IP gets allocated to two different UEs or two different PDU sessions belonging to the same UE or DNN.

This feature ensures that such duplicate IP allocations are detected and appropriate actions are taken to prevent conflicts.

Command introduced:

condition duplicate-ip — Use this command in policy rule management configuration to detect the duplicate static IP allocations and reject or terminate such session requests.

Enhancements to N3IWF: Network-Initiated Service Requests, Inter-PLMN Handover, and Core-Agnostic Location Parameters

Following are the additional enhancement to the N3IWF for the seamless communication between the Wi-Fi network and the cellular network.

• Network initiated service request through N3IWF

• Inter PLMN Wi-Fi to NR handover

• Inter PLMN NR to Wi-Fi handover

• Wi-Fi (N3IWF) to Evolved Universal Terrestrial Radio Access (EUTRA) HO

• EUTRA to Wi-Fi (N3IWF) HO

• Next Generation Core-Agnostic (N3GA) location parameters

Load and Overload Control over SBI, GTP-C, and N4 Interfaces

This feature handles the load and overload control mechanism for GTPC, N4, and SBA Interfaces. This feature improves the network robustness by considering the load and overload status of self and the peer nodes.

Commands Enhanced:

• profile overload-exclude overload_exclude_profile_namemessage-priority [ n4 | n7 | n10 | n11 | n16 | n40 | s5 ] upto message_priority

• profile overload-exclude overload_exclude_profile_name procedure-list [ session-delete | new-call | xnho | modify | chf-reauth | inter-rat-ho | intra-rat-ho | imexit-nw | imexit-ue | usar ]

Default Settings: Disabled—Configuration Required to Enable

Message Priority Negotiation for High Priority Messages

At any given circumstance, the SMF must ensure that the high-priority messages (WPS, emergency, etc.) continue uninterruptedly.

SMF uses Message Priority (MP) Negotiation as the method to ensure uninterrupted communication between SMF and peer nodes. This mechanism allows the SMF to compare the message priority value present in the inbound message with the message priority value present in the local configuration.

This way, the high priority inbound and outbound messages in a WPS Session get prioritized and processed on SMF.

Default Setting: Always Enabled

SMF

Previous Behavior: The frequency of calculating the load factor was fixed at an interval of 30 seconds. As there was no support to change this interval, it was causing an overloaded system to stay overloaded until the next interval of 30 seconds. There was no mechanism to change this frequency according to the situations.

Also, by default all the pods that were not participating in message-handling were getting excluded from the load factor calculation.

New Behavior: The process of load factor calculation is enhanced to allow the user to configure the suitable interval. This enhancement also provides the capability to configure the specific non-participating pods to be excluded from the load factor calculation. Also, the show resources output is enhanced to display the load factor of the various pod instances.

The following new CLI is introduced as part of this enhancement:

load factor { calc-frequency calc_frequency_time | exclude-pods exclude_pod_name }

Note: This CLI is backward-compatible. Therefore, if these load factor parameters are not configured, it considers the old behavior for calculating the load factor.

Enhanced Show CLI Output to Display the GR Instance ID of the Overloaded Peers

Previous Behavior: The network operator did not have the visibility into the instances of the peers that are overloaded.

New Behavior: The show CLI show overload-info peer all is enhanced to display the GR Instance ID of the peers that are overloaded. This allows the peers to have detailed information about the peer overload status.

Customer Impact: The network operator has detailed information about the overloaded peer.

Message Priority Negotiation for High Priority Messages

Previous Behavior: SMF was not considering the message priority of the incoming messages over N4, GTPC, and SBA interfaces. SMF used to send the message priority in outgoing messages.

New Behavior: SMF extracts the message priority of the incoming messages, negotiates the extracted MP value with the configured interface specific MP value, and sends out the best among them in the outgoing message.

SMF Handling of SmContextStatusNotify for WiFi (N3IWF) to NR Handover

Previous Behavior: By default, SMF sends the SmContextStatusNotify to AMF without checking the "3GPP 23.502" compliance version for "WiFi (N3IWF) to NR" and "NR to WiFi" handover in intra-PLMN scenarios.