Network Configuration

Adapting resources to align with network elements and business processes is essential. Ensuring the service is tailored to the customer’s specifications, or by ensuring intricacies of each network element are correct are all vital steps in low/no touch operation. It may also be a cyber factor such as ensuring the vendor, model, software and firmware versions in the network are all correct and secure.

An example of complexity might also be the handling a single service order item. An order can trigger a complex sequence of changes, necessitating a range of configuration commands. These commands might be employed to add, create, modify, or even delete configurations within the network element, depending on the order’s specific requirements. This level of detail ensures that each service alteration is executed precisely, reflecting the dynamic nature of network operations.

Service cessation requests introduce additional layers of complexity. Depending on the customer’s circumstances or service agreement, a cessation can be either soft or hard. A soft cease temporarily disables the network configuration, maintaining it in a dormant state. This is particularly useful when a customer may temporarily not require the service, such as during extended absences, allowing for easy reactivation later. Conversely, a hard cease involves removing network configurations, often used in more permanent service termination scenarios, like bill non-payment. Once resolved, the service can be re-enabled, demonstrating the system’s flexibility and responsiveness to various customer and service needs.

By pairing this with Life Cycle Management (LCM), a customer can now have a full overview of their network configuration ensuring its correctly configured but also that other existing services are not unnecessarily or adversely affected by the new configuration. This can be delivered as part of a fully autonomous model, creating a zero-touch experience for the Operator.