Features

Previous Next JavaScript must be enabled to correctly display this content

2 Features

This chapter lists the added or updated features in release 25.2.2xx. For more information about the features, see Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

Release 25.2.200

Hosted SEPP:

The Hosted SEPP feature enhances Oracle’s Hosted SEPP deployment by enabling multi tenancy support. This feature introduces the ability to handle multiple Fully Qualified Domain Names (FQDNs) and certificates for different tenants, providing improved flexibility in inter network communications and partner routing. With the new model, the SEPP can handle multiple identities, facilitating seamless connectivity to different roaming and hosted partners using different FQDNs. This eliminates the constraints of using a single FQDN for all connections, thus improving the efficiency of traffic routing and reducing the need for manual intervention.

Configuration Status: This feature is disabled by default.

For more information, see the "Hosted SEPP" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

Support for Max-Response Timer Header in SEPP:

The feature enables the SEPP to validate, add, or modify timestamp headers in both ingress and egress request paths. Once enabled, it prevents delays and service degradation by enforcing a maximum allowable response time, ensuring that requests are processed within an acceptable time window. Any messages that exceed the defined response time threshold are automatically rejected, which enhances the overall efficiency and responsiveness of the network. The feature works by embedding timestamps in the headers of messages sent from the AMF to the SEPP.

Configuration Status: This feature is disabled by default.

For more information, see "Support for Max-Response Timer Header in SEPP" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

Support for PLMN Validation in Get Access Token Requests for Roaming Subscribers: This feature enhances validation and error handling for OAuth Token Request (GET_Access_Token) messages, ensuring only valid, authenticated requests with correct PLMN IDs are processed. SEPP validates incoming requests against negotiated PLMN IDs, ensuring they match local network requirements and content type specifications. Mandatory parameters are enforced, and invalid requests trigger error responses, which are logged for further analysis. Valid requests are forwarded to the local NF, while metrics and logs are captured to monitor system performance. Alerts are triggered based on error rates, enabling proactive issue resolution.

Configuration Status: This feature is enabled by default.

For more information, see "Support for PLMN Validation in Get Access Token Requests for Roaming Subscribers" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

Error Response and Logging Enhancement for SEPP: In the enhanced error response mechanism, SEPP now includes additional context in error messages, such as the server FQDN, NF service name, vendor name, and a unique error ID. This makes it easier to identify the exact cause of errors. Further, the logging enhancements introduce new attributes in error logs, including status, title, detailed descriptions, and sender/receiver information, enabling quicker identification of issues and reducing downtime during fault resolution. The Error Response and Logging Enhancement feature improves SEPP's ability to capture and communicate error details, aiding in faster troubleshooting.

Configuration Status: This feature is disabled by default.

For more information, see "Error Response and Logging Enhancement for SEPP" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide, and "Customizable Parameters" in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

Lifecycle Management (LCM) Based Automation: Lifecycle Management (LCM) Automation optimizes the deployment and upgrade processes of SEPP by reducing the steps required to initiate. The following automation enhancements are supported in this release:

Helm Enhancements for Service Account: This enhancement allows you to automatically create user-defined service accounts without any manual intervention.

Helm Enhancements for NF Alert Configurations on OSO: SEPP leverages the oso-alr-config Helm chart, introduced in the OSO package, to apply alert rules through Helm upgrades. While the oso-alr-config Helm chart is deployed automatically during the OSO installation, SEPP performs Helm upgrades to apply or update the required alert rules. Both manual and automated configurations are supported.

Configuration Status: This feature is disabled by default.

For more information, see "Lifecycle Management (LCM) Based Automation" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

Support for bypassing ASM sidecars: The integration of Aspen Service Mesh (ASM) within the internal NF POD has drawbacks. To improve performance, SEPP now allows bypassing ASM sidecars for intra-namespace traffic. Additionally, operational issues in PRINS mode on the N32 interface, when routed through ASM, prompted the removal of ASM from the N32 gateways in the SEPP deployment. While ASM will still be used for inter-NF communication where necessary, these changes are part of enabling the one-sided ASM in SEPP.

Configuration Status: This feature is disabled by default.

For more information, see "Configuring SEPP to Support Aspen Service Mesh" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

SEPP Traffic Prioritization using Egress Gateway Pod Protection: With the implementation of this feature, rate limiting mechanism is applied for Egress Gateway pods. This mechanism allows pods to process a predefined number of requests. When the request rate exceeds the threshold, the pods take action to protect themselves. Depending on the configuration, the pods either reject the additional requests with a custom error code or allows the request.

Configuration Status: This feature is disabled by default.

For more information, see "SEPP Traffic Prioritization using Egress Gateway Pod Protection" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

SEPP and NRF Communication: This feature enables SEPP to set NRF configuration eliminating the need to manually create routes post installation, including automatic route creation to remove REST based routing overhead. It enables real-time NF status and capacity information, helping SEPP select healthy, available services for reliable communication, with dynamic updates, retry and rerouting support, and no delay in inter-PLMN NRF traffic. Additionally, it supports dynamic NF registration and deregistration, support for both HTTP and HTTPS NRF instances, static and virtual NRF instances, and route correction in case SCP is deployed, allowing for scalable and flexible network configuration in a cloud-native 5G environment..

Configuration Status: This feature is enabled by default.

For more information, see the "SEPP and NRF Communication" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

Support for cnDBTier Georeplication Status Across All Sites API in CNC Console: With this enhancement, cnDBTier Georeplication Status Across All Sites can be viewed on CNCC Console GUI.

Configuration Status: This enhancement is enabled by default, with no additional configurations.

For more information, see the "Support for cnDBTier APIs in CNC Console" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

Support for OpenAPI JSON Specification in CSAR: With this enhancement, the existing OpenAPI specifications provided in YAML format are transitioned to JSON format to improve compatibility with external tools, API change tracking across releases, and ensures a consistent and standardized API specification format.

Configuration Status: This enhancement is enabled by default, with no additional configurations.

Application Framework Change: Springboot has been replaced with Micronaut as the framework for SEPP microservices.

Configuration Status: This enhancement is enabled by default, with no additional configurations.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.