O that their resources can be freed up to alleviate the congestion situation. When the congestion is removed from the network and it comes back to a normal operating volume, then the orchestrator starts the services again. Hence, this is a method to provide temporary relief in a highly congested network. Automation, Orchestration, and Testing Implementation of network slicing This is one of the most important use cases for automation. It entirely depends on the availability of an orchestrator. As you will have read about and understood the various network slices and their uses, you will also know that network slicing is nothing but segmenting the network such that certain resources are made available for certain purposes. The slicing is horizontal across all the components of the network for a given use case (for example, IoT). A reservation of the resources is made and the network functions are deployed via an orchestrator. This orchestrator is not only responsible for the life cycle management of a slice but also for its configuration. We have gone through a few examples showing where network orchestration is key to building relevant capabilities; can you think of more examples? Integration planning in a multivendor environment By now, we are well aware of the complexity and the sheer number of components that constitute a 5G network. Integrating these would not be a trivial task. Each network component is a part of the puzzle that needs to fit in an airtight way for the network to function. Hence, there are multiple aspects to consider when we go about laying the foundations of the network and planning its integration. The following points should come in handy while doing so, and it should be noted that all of these steps should be automated for faster test cycles and integration: Unit testing: This is the most basic part of testing and, possibly, the starting point for any network engineer before they can start the integration of the components. It is important to check the sanity of each network component be