# Customer-Oriented Quality of Service Management Method for the Future Intent-Based Networking
## 3 A Description of the Proposed Customer-Oriented Quality of Service Management Method for IBN
### Development of a Simulation Model of Intent-Based Networking
#### 3.1.1 General Stages of Network Simulation
Here also, we establish links between routers (network topology is formed) and calculate IP pools for network components. The research was conducted according to the topology of the network model depicted in Figure 5. After initialization, the program goes directly to the network's simulation, which can be divided into the following components: generation of packets by the network's customers; packet handling by switches; packet handling by routers; packets sending from customers to switches; packets sending by switches; packets sending by routers; routing tables updating; network statistics consuming and charts updating. Every next iteration is all in circle. Figure 4: The scheme of connections between the factors influencing customer satisfaction. * Packets generation by customer devices The generation of customer packets takes place in several stages:  
1. We generate a session and select its parameters such as session usage time, service type, desired QoE score, and destination node;
2. Generate packets for the session until it is completed;
3. Upon completion, we generate a new session with new parameters. In this simulation program, seven types of electronic services that can be transmitted by the network are selected: VoIP (voice over Internet Protocol), data transfer, interactive data, IPTV Internet Protocol Television, service packets, videoconferencing, video on demand [40]. Each type of service has its own parameters such as: the packet average size, deviation from the average size, maximum service use time, the number of packets that generate service in a second, maximum number of dropped packets, maximum delay for packet transmission, service ID. The distribution of probabilities of using the services is chosen, taking into account the average use of customers in modern networks. The values of the probabilities are given in Table 2.  
Each service has its own parameters. When modeling, one can adjust all values for specific variants. The configuration of the parameters used is summarized in Table 3. \begin{table}
\begin{tabular}{c c} \hline \hline
**Service Type** & **Percentage Equivalent, \%** \\ \hline Voice over Internet Protocol (VoIP) & 15 \\ Data transmission & 15 \\ Interactive data & 5 \\ Internet Protocol Television (IPTV) & 20 \\ Service packets & 22 \\ Videoconferencing & 21 \\ Video on demand & 2 \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Distribution of e-service usage in the network. Figure 5: Topology of the investigated network. After the session is created, the customer will generate packets with the corresponding parameters of each iteration of the network. * Packet processing by switch  
Each switch contains a list of active customers, an ARP (Address Resolution Protocol) table for packet switching, and a host name identifier. Each iteration switch collects all packets from active customers and serves according to switching table. If the IP addresses of the recipient are located on this local network, the packet will be sent to the corresponding port. If the IP address corresponds to another network, the packet will be sent to the router. In the process of packet processing, the switch will also read (analysis) the fields in the packet, which are responsible for the sender and receiver's MAC (Media Access Control) addresses according to the current network operating standards. When using the standard network's packet service method, the switch will handle packets according to the received time. When using the proposed method, all packets will be sorted. Detailed information of the new method will be considered later. * Packet processing by router  
Each router contains a list of IP subnets of interfaces to which switches are connected, a pool of IP networks (DHCP, Dynamic Host Configuration Protocol analogue), lists of local and global interfaces, a node name identifier, and a routing table.