2 Features

Security Edge Protection Proxy (SEPP) 23.4.x has been updated with the following enhancements:

Release 23.4.3

No new features or feature enhancements have been introduced in this release.

Release 23.4.2

No new features or feature enhancements have been introduced in this release.

Release 23.4.1

No new features or feature enhancements have been introduced in this release.

Release 23.4.0

  • Load Sharing among Multiple Remote SEPP Nodes: With load sharing among multiple Remote SEPP nodes feature, SEPP can now efficiently distribute incoming traffic among multiple remote SEPPs. To enable this, the operator needs to configure a single virtual FQDN for the remote SEPPs. SEPP retrieves multiple Remote SEPP records from the DNS server and distributes the traffic according to the priority and weight associated with each record. Hence, SEPP can simultaneously route the incoming requests to multiple Remote SEPPs.

For more information about the feature, see the "Load Sharing among Multiple Remote SEPP Nodes" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and the "Remote SEPP" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy REST API Specification Guide.

  • Separate Port Configurations for N32c and N32f on the Egress Routes: In some deployments, there is a need to have different service IPs and ports for n32c and n32f interfaces although the endpoint SEPP may have the same name. To improve traffic segregation, the Egress Gateway is enhanced by configuring different ports for the n32c and n32f connections on both the Remote SEPP Set and its local configurations. Separate ports for n32c and n32f interfaces provide the flexibility to configure different IP address or port for both interfaces.

For more information about the feature, see the "Separate Port Configurations for N32c and N32f on the Egress Routes" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and the "Remote SEPP" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy REST API Specification Guide.

  • Support for cnDBTier APIs in CNC Console: With the implementation of this feature, cnDBTier APIs are integrated into the CNC Console. SEPP users can view specific cnDBTier APIs such as checking the cnDBTier version, status of cnDBTier clusters, and georeplication status on the CNC Console. The cnDBTier APIs can be viewed (read only) from the CNC Console.

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

  • Mediation Rules using CNC Console and REST APIs: With this feature enhancement, mediation rules are being stored in the database. The existing rules can be retrieved, modified, deleted, and new rules can be configured and applied to mediation microservice using the CNC Console or REST APIs.

For more information about the feature, see the "5G SBI Message Mediation Support" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and the "Mediation Rules Configuration" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy REST API Specification Guide.