## 4 Major Components of Network Slicing System
### Intent-Based Networking (IBN) Tool  
The IBN tool encompasses six major components named the intent manager, the policy store, the contract design, the resource manager, the OSM policy configurator, the RAN policy configurator, and the DL Module. The IBN system can automate the network slicing procedure by just providing higher-level configurations from the front-end of the IBN tool. The functionality of each component is as follows; the contract design provides an easy way for users (operators, subscribers) of the system to define their intentions by using the front-end of the IBN tool. Users of the system define their resource requirements for creating a slice by just dragging and dropping at the front-end portal of the system. The intent manager acts as a coordinator for all the components and communicates directly with them. When a contract comes from the operator, it fetches the architecture information from the policy store and generates a graph by mapping both contract information and architecture information; after that, it sends that graph information to the policy configurator; the RAN related requirements can be sent to the RAN policy configurator and core and to the OSM core policy configurator as well. Moreover, the network functions information, version information, IP address scheme, and network instances images are stored in the policy store database repository. The policy store is a well-organized database repository that has all the information related to core network functions and registered eNodeB information. It stores the information according to the 5G architecture design. Further, the policy configurator extracts the information related to resources from the graph which is provided by the intent manager and converts that information in the form of a slice template. That slice template is according to the network orchestrator acceptable format; for example, for theOSM core, the policy configurator can give the slice template in the form of a JSON file which contains the information related to the deployment of the network functions and their mapping. The design of the OSM policy configurator is well explained in our paper [38; 39; 40]. On the other hand, the RAN policy configurator also generates the policies' template in the form of JSON which could be further sent to the FLEXRAN controller for slice creation at eNodeB. Afterward, FlexRAN deploys those configurations to the eNB through the master controller and agents via Southbound API. Finally, the requested network slice can be deployed at the access network. In this way, dedicated EPC and RAN resources can be assigned to a requested slice using specified S-NSSAI in the slice template. The IBN tool not only automates the policies for the deployment of the network slices but is a generic system for multiple orchestrators tomanage the whole network slicing procedure; it also monitors the network slice resources with the DL model during execution and updates the resources in case of failure or resource over-utilization. Hence, the DL model continuously monitors the resources and updates accordingly. The complete working functionality of each component is explained below.