2 Feature Descriptions
This chapter provides a summary of each feature released in Cloud Native features release 2.2.1.
Automated Testing Suite (ATS)
- Provides NF Specific login support - Only NF specific pipelines are visible.
- Provides RBAC authorization.
- Allows to deploy ATS using either Helm2 or Helm3 helm versions.
- Enables all the NF teams with the basic environment, framework and a GUI (Jenkins) to execute all the functional test cases.
Cloud Native Environment (CNE)
- Enhanced Platform Alerts: Additional platform alerts were added to detect conditions where common services are working at reduced capacity or have failed.
- DB Tier Overlay: A DB Tier Overlay was created to allow customers to install only the DB Tier, for cases where OC-CNE is not used. The DB Tier Overlay will install the DB Tier on KubeVirt VMs in the customer's CNE, so KubeVirt is required.
- Fixed IP Support for vCNE: Customers have the option of selecting specific IP addresses to be used by the Bastion Host, Kubernetes primary and secondary nodes, and DB Tier nodes.
- DB Tier Dual Channel HA Replication: Two replication channels are automatically established between mate sites. While only one channel will be active at a time, (as was the case in previous releases), a failure of the Active replication channel will be detected automatically, and the Standby channel promoted to Active, to keep cross-site replication in service. Manual repair of failed channels is required.
Cloud Native Core Console (CNCC)
- Supports Aspen Service Mesh (ASM) integration
- Supports OSO integration
- Single Sign-On Support using SAML 2.0
- Support for additional UDR Screens:
- Global Configurations
- Service Configurations
- Data repository service
- Notify service
- NRF client service
- Helm V3 Support and Custom Annotation and label support
Cloud Native Core Policy (CNC Policy)
- Support integration with Aspen Service Mesh 1.4
- Converged Policy Framework for PCF and cnPCRF
- Two-phase deployment of policies
- Support for CNE 1.5 platform
- Import/Export enhancements for policies
- Subscriber Activity Logging enhancements
- PI-C Policy Actions and Conditions enhancements
- Converged Policy Geo-redundancy Support
- CN-PCRF API/PPI Support
- Stale Session Handling Enhancements
- Spending Limit Pending Counter Enhancements
- Inter-working support with DRA for policy initiated requests
CNC NF Data Collector
CNC NF Data Collector collects Network Functions’ deployment data when NFs are deployed. Also, it collects logs, metrics, traces, and alerts when any functionality issue occurs after the NF deployment is complete. You can run CNC NF Data Collector to generate the required tarballs and examine the log files present in the tarballs for debugging purposes. Using this data, you can determine an NF issue by accessing logs, metrics, traces, and alerts of the NF.
- Network Function Deployment Data Collector
- Network Function Logs, Metrics, Traces, Alerts Data Collector
Cloud Native Diameter Routing Agent (CnDRA)
There are no new features/updates implemented in CNC 2.2.1 release.
Binding Support Function (BSF)
- BSF related Configuration Management API/PPI enhancements
- OAuth2 Support as producer NF in BSF
- Integration with the latest NRF Client to comply with all new NRF client features
- Autoscaling with liveness and readiness probe support
Inter-Working Function (IWF)
- Supports observability (Metrics, KPIs, Alerts, logging, SNMP MIBs ) with CNE.
- Supports API gateway Integration
Network Repository Function (NRF)
- Support for Aspen Service Mesh Integration
- OCNRF two Site Geo-Redundancy Support
- Support for non-Geo-Redundant NRF Upgrade (OCNRF 1.7.0 will be fresh installation)
- Support for adding Custom Labels and Annotation to Kubernetes Resources
- Support for adding Prefix/Suffix to Container Names
- Compatible with network functions which are compliant with Release 29.510 v15.5 (Sept 2019) version
Network Slice Selection Function (NSSF)
- Support for HTTP OPTIONS method for NS-Availability
- Compliant to 29.531 version 15.5 with following assumption:
- OCNSSF is currently not supporting Roaming and 5G to NON-5G handovers.
Service Communication Proxy (SCP)
- Ingress gateway helm charts are updated to stop generation of netty metrics
- SCPIngressGatewayPodMemoryUsage alert is added in SCP Alerts and Mib files to include memory usage alert for Ingress gateway
- New metrics are added to calculate NF wide rate:
- ocscp_metric_nf_total_http_tx_req
- ocscp_metric_nf_total_http_rx_req
- ocscp_metric_nf_total_http_rx_res
- ocscp_metric_nf_total_http_tx_res
- ocscp_metric_nf_total_http_rx_res_xx
- ocscp_metric_nf_total_http_tx_res_xx
- Alerts/Alarms are updated as follows:
- Expressions updated with correct labels:
- SCPSoothsayerNotificationPodMemoryUsage
- SCPWorkerPodMemoryUsage
- SCPPilotPodMemoryUsage
- NFInstanceConnectionDown
- Expression modified to use different function:
- SCPInstanceDown
- Expressions updated with correct labels:
- Aspen Service Mesh 1.4.6-am9 (ASM) Integration with OSO
- Cluster role binding is provided as optional feature
- Use of Helm hooks for creating DB tables
- Added new metrics and logs to enable debugging error scenarios
- Ingress Gateway support (optional) to increase per connection throughput
- Mediation Enhancement for supporting 3GPP version level inter-operability
- Support for mediation alerts and metrics
- Enhance OCSCP helm chart labels and annotations as per new guideline
Security Edge Proxy Protection (SEPP)
There are no new features/updates implemented in CNC 2.2.1 release.
Unified Data Repository (UDR)
- Supports Aspen Service Mesh (ASM) integration
- Supports features enablement for UDR services
- Supports SLFGroupName provisioning for SLF data
- Integrated with CNC-Console for UDR configuration along with Provisioning
- Integrated with Egress API gateway for egress traffic of UDR
- Supports customizable labels and annotations for Helm charts
- Supports Helm test for validating NF deployment
- Supports Diameter Sh support for subscriber profile
- Provisioning Gateway integrated with Egress API gateway
- Provisioning Gateway supports SLF provisioning using SLFGroupName