Telecom Network Automation is a managed cloud implementation ofNephio,an open source project from Google and the Linux Foundation. Telecom Network Automationdelivers carrier-grade, Kubernetes-based, multi-cloud, multi-vendor andbuilt-in cloud intent automation through common automation templates.

Use Telecom Network Automation to accelerate service delivery, reduce operationalprocesses, optimize network reliability, and enforce compliance and securityrequirements:

• Accelerate service delivery: Deploy new services efficiently, oradd capacity to a network by automating the entire network components andsoftware stacks provision.
• Reduce operational processes: Use a single interface for deployingand managing entire networks from initial configuration to continuousdeployment and operations.
• Optimize network reliability and availability: Test systems in thenetwork lifecycle and reduce maintenance time. Telecom Network Automationsupports the following tests and configurations:
  • Cross-version testing.
  • Vendor-specific testing.
  • Pre-submit validations for configurations.
  • Test framework integration for a multi-stage releasequalification pipeline.
• Adhere to compliance and security requirements: Maintain control ofsystem updates by reviewing audit logs for admin activity and data access.

Additionally, you can integrate Telecom Network Automation with a Google Cloud product.To learn about product integration, see the following:

• Google Distributed Cloud(GDC)
• Google Kubernetes Engine (GKE)

About Telecom Network Automation

Telecom Network Automation supports a declarative, intent-based mechanism ofcontrol-loop automation that addresses the imperative model with the advantagesof Kubernetes and Nephio. Telecom Network Automation is a centralized solution to deployentire telecom networks and manage them in a single place.

The Telecom Network Automation architecture comprises the Kubernetes Resource Modeland the Configuration as Data concept. This model and concept providedeclarative capabilities and intent reconciliation, and shows what runs in anenvironment matches your intent.

Telecom Network Automation uses standard custom resource definitions (CRD) andpluggable Kubernetes operators. Standard CRDs alleviate interoperabilityissues. The Kubernetes operators are installed on a GKE cluster thatbehaves as the Telecom Network Automation control plane. These operators processyour requests for deploying infrastructure; work through validation,automation, and reconciliation; and sync the requests to the network.

Survivability mode

If a network disconnection between the Telecom Network Automationmanaged cluster and the Telecom Network Automation management plane occurs, the workloadnetwork functions and clusters created using Telecom Network Automation can continue torun. Telecom Network Automation continues to reconnect, and until it successfullyreconnects, further monitoring and actuation is not possible.

Users are responsible for maintaining all the data stored on the clusters,workloads, redundant backups, electrical power supply to the Edge nodes, HVAC,physical security, local network connectivity, firewall rules and security.Telecom Network Automation requires a constant connection to Google Cloud.

Telecom Network Automation delivers zero-touch provisioning (ZTP) of cloudinfrastructure which translates into increased network availability andresilience while reducing maintenance downtime. Specifically,Telecom Network Automation provides the following support and delivery measures:

• Supports initial configuration, deployment, and continuous deployment andoperation, from a single pane of glass user interface (UI).

• Adopts the GitOps approach that provides continuous reconciliation withsimplified configuration management at scale. Telecom Network Automation usesKubernetes capabilities and supports configuration versioning, tagging, andadditional capabilities such as measuring intent drift.

• Embraces embedded continuous integration and continuous delivery.Specifically, Telecom Network Automation supports cross-version and vendor-specifictesting, presubmit validation of configuration, and integrate the testframework into a multi-stage release qualification pipeline that preventdefects from going into the production environment.

Collectively, these Telecom Network Automation capabilities let CSPs in theirjourney to ZTP, while maintaining their ability to exercise control on systemupdates.