**5. FHAMIPv6/MPLS integration**

FHAMIPv6 protocol was created as an extension to support FHMIPv6 hierarchical addresses in MANET networks, but FHAMIPv6, is not an protocol to provide quality services in such networks. For this reason, it was necessary to integrate MPLS and FHAMIPv6 in order to provide QoS in MANET networks.

22 Mobile Networks

In order to extend the different results obtained in the simulations, the function (figure29) shows the behavior of the different simulation scenarios. With this functions could predict what will happen with the metrics (Delay, Throughput, Send and Received Packets) and the number nodes. In this manner, we could predict what happens when the number of nodes

**Jitter and Lost Packets**

Fig. 29. The figure show the functions Jitter and Lost Packets vs. Number nodes

the other hand, the average jitter analysed reached 38 ms.

y = 0.1056x2 - 5.0501x + 108.14

y = 0.0034x2 - 0.2381x + 9.1021

FHAMIPv6 in order to provide QoS in MANET networks.

lost when the AMN moved either towards the APAR or to the ANAR.

This research shows the effects of the FHAMIP/AODV integration over the QoS metrics. The simulation proved that the average delay was approximately 112,27 ms and was penalized by the AODV signalling, so it was necessary to update the status of the routes. On

0 10 20 **Nodes** 30 40 50

Jitter(ms)

Lost Packets (%)

Regarding the loss of packets, a total of 86 did not reach the destination. Most of them were

The jitter was quite satisfactory given the fact that it exceeds 176 Kbps. In general, the delay and the jitter suffer the strong effects of the AODV routing updates. Some nodes stop sending TCP packets to transmit useful AODV signalling to recalculate routes, increasing the delay in a TCP session significantly. A possible solution (assuming that only a node moves on) would be to modify AODV in order to stop routes updating until the APAR and the ANAR receive a MAP\_REG\_REQUEST from the AMN. This would indicate that the

FHAMIPv6 protocol was created as an extension to support FHMIPv6 hierarchical addresses in MANET networks, but FHAMIPv6, is not an protocol to provide quality services in such networks. For this reason, it was necessary to integrate MPLS and

and flow of the traffic is increased.

**4.3 Conclusions** 

0

100 120

AMN is in its own area.

**5. FHAMIPv6/MPLS integration** 

To achieve the integration was necessary to modify the source codes of MPLS and FHAMIP. In this section the same way as in the other sections, we used the base scenario proposed by R. Hsieh and then the number of nodes and traffic flow was increased in order to analyze the scalability of the integration. The Tests were realized with: 9, 20 and 30 nodes. The QoS metrics analyzed were: Delay, jitter, throughput, send and received packets and lost packets.

The figure 30 Shows that initially the AMN is in the area of the AHA in communication with the ACN, it can also be observed that the core MPLS is formed by MAP/GW1, LSR2, LSR3, PAR/LER1, NAR/LER2 nodes. Where the MAP/GW1 node performs the functions of default gateway, the nodes LSR3 and LSR2 are used simultaneously as Label Switching Routers and intermediate nodes FHAMIPv6; it can also be observed that the nodes PAR/LER1 and NAR/LER2 have functions of MPLS edge router and access router for FHAMIPv6. Furthermore, the node AN1 only functions as an intermediate FHAMIPv6 node and has no has no MPLS functions, while ACN and AHA nodes correspond to the corresponding node and base agent respectively, lastly the AMN node represents the mobile node. With regards to the characteristics of the wired links, table7 presents details. From the table above, we can highlight the fact that the link AN1 - MAP/GW1 has a superior bandwidth and delay than the rest, because it represents a connection with Internet.

Fig. 30. Scenario of simulation

Mechamisms to Provide Quality of Service on 4G New Generation Networks 25

At the initial instant the mobile node (AMN) is in the area of its home agent (AHA) as shown in Figure 29, then at t = 1.2s the AMN starts transferring FTP traffic with the ACN, there upon between t = 3.5s and t = 4.5s MPLS / RSVP resource reservation takes place on the path MAP/GW1 - LSR2 - PAR/LER1. Then at time t = 10s the AMN begins its displacement towards the PAR/LER1, at a speed of 100m / s arriving shortly to this area from which it will use the PAR/LER1 - LSR2 - MAP / GW1 - AN1 route to communicate. A few seconds later between t = 14.5s and t = 15.5s resource reservation along the route MAP/GW1 - LSR3 - NAR/LER2 takes place anticipating the subsequent transfer made by the AMN which moves at 10m / s from PAR/LER1 toward the NAR/LER2 at t = 16s. From there on, the traffic will follow the NAR/LER2 - LSR3 - MAP/GW1 - AN1 route to

communicate with the ACN and the AHA. This is illustrated in the figure 32.

In the same way, we simulated with 20 and 30 nodes. See figures 33 and 34.

Fig. 32. AMN in NAR/LER zone

**5.2 Scalability** 


Table 7. Presents the characteristics of the wired wireless links.
