## 3 Proposed System Architecture
### Proposed System and Algorithm
\begin{table}
\begin{tabular}{c c c} \hline
**Inputs** & **Degrees** & **Scales** \\ \hline \multirow{3}{*}{RSRP} & Poor & \(-\infty\) to \(-95\) dBm \\  & Fair & \(-95\) to \(-75\) dBm \\  & Excellent & \(-75\) to \(-10\) dBm \\ \hline \multirow{3}{*}{Speed} & Slow & 0 to 20 km/h \\  & Moderate & 20 to 80 km/h \\  & Fast & 80 to 180 km/h \\  & Very Fast & 180 to 220 km/h \\ \hline \multirow{3}{*}{Load} & Low & 0 to 40 \% \\  & Medium & 40 to 80 \% \\ \cline{1-1}  & High & 80 to 100 \% \\ \hline \end{tabular}
\end{table} 
Table 1: Membership principles for FLC inputs. ```
1:if\(t>1\)then
2:if\(RSRP_{t}>RSRP_{s}+HOM\)and\(RSRP_{t}\geq Q_{Rx}\)then\(\triangleright\)\(Q_{Rx}\): Reference Sensitivity
3:\(timer\gets timer+1\)
4:if\(timer==1\)then
5:\(Trigger\)\(\mathit{Timer}\)\(\mathit{\leftarrow}\)\(MP\)
6:elseif\(timer\geq 2\)then
7:if\(cell\_ID_{t}(t)==cell\_ID_{t}(t-1)\)then
8:\(Trigger\)\(\mathit{Timer}\)\(\mathit{\leftarrow}\)\(Trigger\)\(\mathit{\leftarrow}\)\(MP\)
9:else
10:\(\mathit{timer}\)\(\mathit{\leftarrow}\)\(1\)
11:\(Trigger\)\(\mathit{\leftarrow}\)\(MP\)
12:endif
13:endif
14:else
15:\(timer\)\(\mathit{\leftarrow}\)\(0\)
16:\(Trigger\)\(\mathit{\leftarrow}\)\(0\)
17:endif
18:else



+++ ==WARNING: Truncated because of repetitions==



++

In Algorithm 1, a timer is applied as a counter that is initiated upon meeting the condition stated in Equation (3). The timer increments only after the initiation of the HO decision, and the cell ID of the target cell (cell_ID\({}_{t}\)) must be different from that of the previous simulation time; otherwise, the timer is set to zero. The maximum timer value for a user can be calculated as Equation (4):

\[timer=\frac{TTT}{MP}, \tag{4}\]

where \(MP\) is the measurement periodicity for each simulation cycle, within which the measurements are made, and it is set to 40 ms. The rules that govern the FLC outputs for TTT and HOM are illustrated in Figure 6. This decision is based on our expertise and is consistent with the implementation of the Mamdani FIS for estimating system outputs. Our expertise has been developed through an iterative process, involving the adjustment of different TTT and HOM values in relation to varying input parameters, such as UE speed, RSRP, and cell load, to achieve the minimum RLF and HOPP values. These parameters significantly impact system performance and are considered essential metrics for TTT and HOM adjustments. Figure 6: Rules governing TTT and HOM. Considering all input parameters for setting the TTT and HOM is crucial. Relying on a single input parameter (e.g., RSRP) is insufficient for setting HCPs (e.g., TTT or HOM). For example, if the serving cell requests an HO and the TTT is set based on the target cell's excellent RSRP levels, the TTT duration should be set very long. However, if the UE speed is high under the same conditions, this could lead to an RLF due to a late HO. Conversely, if TTT is set based on slow UE speed, it should also be set very long. In this case, if the RSRP is poor, it will cause RLF too. The same principle applies to the combination of UE speed with RSRP and cell load, as well as to the setting of the HOM. Setting the rules in FLC is based on the defined ranges of specific input parameters. For instance, the combination of UE speed, RSRP, and RSRQ in [19] generates different rules to output TTT and HOM. The effect of each input parameter on any output parameter is distinctive; for example, RSRQ may impact TTT variation differently than cell load. The number of rules is directly proportional to the number of distinct ranges of the input parameters. A combination of three input parameters with three distinct degrees each will create a total of 27 rules, whereas considering two input parameters with three distinct degrees and one with four distinct degrees will create a total of 36 rules. Additionally, the TTT and HOM ranges are related to the maximum and minimum ranges of the input parameters, which will also impact system performance due to limitations in those parameters.