## 4 Use Case and Simulation of the Proposed System
### PMIPv6/AAND--Inter-Technology Handover  
This section gives details on the post action of the inter-technology handover of PMIPv6/AAND with the multiple VIs. The activation and deactivation property of every HNP is present in the HNP list. The concerned property represents its activation state. The activated HNP is represented by the bold font, and the deactivated HNP state is represented by the ordinary font as in Table 1.  
Figure 11: PMIPv6/AAND—Simulation Topology [9].  
Concurrent Connection of PMIPv6/AAND  
Once multi-homing MN binds to the MAG, the MAG sends a PBU to the LMA. As soon as the LMA is given the PBU message from the MAG, the LMA assigns the LL-ID to an HNP, although the MN-ID is alike and generates new BCEs. Table 1 represents the LMA BCE as soon as the virtual interface VL1 is found via PI 1 towards the MAG1, as shown in Figure 12. The HNP1 is owed to MN VL1.  
Whenever the new HNP is allocated by the LMA, the LMA updates the HNP list for each entry that has the same MN-ID. Furthermore, each allocated HNP has a similar attribute to multiple VI's. The HNP 'pci' type is used for the latest attached VI LL-ID, and the HNP'sec' type is used for inter-technology handover. Table 2 shows the LMA BCE when the MN is mounted to the MAG2 using VI 2 through PI 2. The VI 2 is given HNP2. Once assigned HNP2, the LMA must update its HNP list of BCE entries linked to the same MN-ID.  
\begin{table}
\begin{tabular}{c c c c} \hline
**MN-ID** & **CoA** & **LL-ID** & **HNP List** \\ \hline MN-1 & Proxy CoA1 & XXX & HNP1, **Pci** \\ \hline \end{tabular}
\end{table}
Table 1: Binding details to the cache before updating.  
Figure 12: PMIPv6/AAND—support for Multiple Virtual Interface [9].  
The LMA posts the proxy binding acknowledgment (PBA) with the modified HNP list to the MAG following a modification of the BCE. The LMA also posts the message unsolicited PBA (UPBA) to other MAGs. The UPBA is used to synchronize the HNP list and is forwarded without the PBU message by the LMA. When the MAG is given the PBA message, the MAG's binding update list (BUL) is added to the HNP list that is incorporated in the PBA message, and the MAG locates the routing table by HNP property.  
If MN receives the packets associated with the deactivated HNP, the MAG updates the BUL's HNP list and sends a PBU message to the LMA, which includes the updated HNP list. The PBU includes the additional information to advise inter-technology handover and updating of the HNP list.  
Moreover, it includes one of the reserved field flags in PBU message format. While the inter-technology handover from PI 1 to PI 2 occurs, the MAG2 gets the HNP1-related packets as shown in Figure 12. The MAG2 could even recognize that inter-technology handover is being executed and will upload the PBU message for notification to the LMA. After the inter-technology handover, the LMA receives the PBU message from the MAG, and the LMA activates the banned HNP. Table 3 explains the state of the HNP list after triggering.  
Since modifying the BCE, the LMA will forward the UPBA message for synchronization to each MAG associated with the same MN-ID in the BCE. HNP lists in the BCE connected to the same MN-ID should be synchronized. The MAG sets the routing table based on the HNP list included in the UPBA message when the MAG receives the UPBA message and updates the BUL's own HNP list. Table 4 explains the MAG2 BUL following the receipt of the message from UPBA. When the MN receives the RS message, the MAG sends a RA message to the MN including the enabled HNP. Table 4 explains the state of the HNP list of binding update details.