# Weighted-CAPIC Caching Algorithm for Priority Traffic in Named Data Network
## 6 Simulation Results and Analysis  
The number of request levels shows how often the pattern of consumer demand changes during the simulation time of request pattern change. Request level 6 means that the pattern of consumer demand changes six times. The higher the request level, the more often the demand pattern changes. Weighted-CAPIC provides the highest cache hit ratio for class 1, which is on average 46% larger than Dynamic-CAPIC, four times \begin{table}
\begin{tabular}{l l} \hline \hline
**Parameter** & **Value** \\ \hline Number of routers & 50 \\ \hline Content store proportion (class 1, 2, and 3) & 1. Weighted-CAPIC and Dynamic-CAPIC: dynamic according to the formula 2. Static-CAPIC: 5\%, 10\% and 15\% of total content number, normalized to total capacity of 150 \\ \hline Number of content & 500 (1 st class) 700 (2 nd class) 1000 (3 rd class) \\ \hline Number of rounds & 10.000 \\ \hline Frequency Limit Factor & 1600 \\ \hline Number of request level & 2 times: (10, 20, 30) and (20 30 10) \\  & 4 times: (10, 20, 30), (20 10 30), (30 20 10), \\  & and (10 30 20) \\  & 6 times (10, 20, 30), (20 10 30), (30 20 10), (20 30 10), \\  & (30 10 20) and (10 30 20) \\ \hline Difference in request rate & 10, 20, 30 (difference: 10) \\  & 10, 30, 50 (difference: 20) \\  & 10, 40, 70 (difference: 30) \\  & 10, 50, 90 (difference: 40) \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Simulation parameters. larger than Static-CAPIC, and two times larger than LCD+Sharing, as in Figure 2. This result is in accordance with the goal of the Weighted-CAPIC algorithm, which provides the highest performance for the class with the highest priority. The result also proves that Weighted-CAPIC can accommodate dynamically changing traffic patterns in the system. Class 1 is a priority class. It has a longest request duration as in Table 1. The information has a long time to go before it becomes obsolete. The content is usually still requested over the years. Therefore, storing content in the network will provide an advantage for these repeated content requests. The Weighted-CAPIC path stretch has the same value as Dynamic-CAPIC, and its value is the smallest compared to Static-CAPIC and LCD+Sharing schemes. With the same path stretch, Weighted-CAPIC provides the larger cache hit ratio compared to Dynamic-CAPIC. The second class cache hit ratio for Weighted-CAPIC is 14.6% smaller than LCD+Sharing, 7% smaller than Dynamic-CAPIC, and 2% larger than Static-CAPIC, as in Figure 3. The second class with UGC traffic type is the second priority, after real-time traffic. So, based on the formula, Weighted-CAPIC provides a smaller portion of storage for this second class compared to the first class. This can also be regarded as compensation, because Weighted-CAPIC has given a more significant cache portion for the first class, which is a priority class. The content store capacity is fixed in every NDN router, and the cache portion must be adjusted based on the content class's needs. In Weighted-CAPIC, this adjustment is made using a formula that is ran on each NDN router. Figure 2: Cache hit ratio and path stretch of class \(1\) for various level of request. The Weighted-CAPIC path stretch has the same value as Dynamic-CAPIC, having a smaller value of about 0.2% than Static-CAPIC. In this second class, the Weighted-CAPIC path-stretch value is higher than the first class, which means that it is necessary to pass longer distances to obtain the desired content for this second class. Weighted-CAPIC gives the smallest cache hit ratio value for class 3, as in Figure 4, because the priority of the third class is the lowest. In addition, by looking at Figures 2-4, it can be seen that Weighted-CAPIC provides the lowest cache hit ratio for the third class compared to first and second. Again, this corresponds to the priorities of classes 1, 2, and 3. Path stretch decreases when the request level increases for all caching schemes. Weighted-CAPIC provides the highest network cache hit ratio parameter.