# Comparative Analysis of 5G Mobile Communication Network Architectures
## 6 Simulation Using Actual Field Data
### Simulation Assumptions  
**Total amount of computing resources for the clouds:** For the simulation, all three network architectures were assigned the same amount of total computing resources. This was done to assess proposed architectures under same set of conditions for fair comparison. The total amount of computing resources was determined as follows. Initially, the amount of computing resources necessary to handle the data traffic during the peak time was determined for each of the six regions. Next, the total amount of computing resources was set to the sum of the individual resources determined for each region, which totaled to 52,200 MHz. Therefore, for all three network architectures, the total amount of computing resources was set to 52,200 MHz. Table 2 shows computing resource allocation for each network architecture.  
**Computing resource allocation for CCC architecture:** For the CCC architecture, the entire 52,200 MHz of computing resources were allocated to the central cloud.  
**Computing resource allocation for HCC architecture:** For the HCC architecture, the computing resources were allocated to both the central cloud and edge clouds. The key issue was determining the allocation ratio between the central cloud and edge clouds. This was done by performing a trend analysis using the simulation model. Computing resources were distributed to six edge clouds, and the amount allocated to each edge cloud was the same as that of the MEC architecture. For each edge cloud, the computing resources were then decreased in steps of 1% from the original resource amount,  
\begin{table}
\begin{tabular}{c c c c} \hline \hline  & \multicolumn{3}{c}{**Computing Resource Allocation (MHz)**} \\ \hline
**Regions** & **CCC** & **HCC** & **MEC** \\ \hline Central Cloud & 52,200 & 7830 & - \\ Region 1 & - & 8271 & 9730 \\ Region 2 & - & 7735 & 9100 \\ Region 3 & - & 7353 & 8650 \\ Region 4 & - & 7072 & 8320 \\ Region 5 & - & 7013 & 8250 \\ Region 6 & - & 6928 & 8150 \\ Total Resources & 52,200 & 52,200 & 52,200 \\ \hline \hline \end{tabular}
\end{table}
Table 2: Computing resource allocation for three architectures.  
and allocated to the central cloud. The simulation was then conducted to assess the performance of the HCC architecture. The results of the trend analysis revealed that the optimal allocation ratio between the central cloud and edge clouds for this particular task traffic was 15% allocation to the central cloud and 85% allocation to edge clouds. Therefore, out of 52,200 MHz of computing resources, approximately 7830 MHz was allocated to the central cloud, and the rest of the resources were allocated to the six edge clouds in their respective regions, as listed in Table 2. One thing to note is that for HCC, the amount of computing resource allocated to the central cloud is 7830 MHz, which is not too much different from other edge clouds allocation amounts. In real situation, there would be more amount of resource allocated to the central cloud. However, for this case study, since all three network architectures compared must have same amount of computing resources, this was determined to be reasonable.  
**Computing resource allocation for MEC architecture:** For the MEC architecture, the entire amount of computing resources was allocated to the edge clouds located in the six base stations. The resource allocated to each edge cloud corresponded to the computing resources required to handle peak task traffic for Scenario 1.