In the HAVC sub-layer, when a new HAVC environment starts, the switching module will create a switching table in order to maintain the physical connection.
In this section, we will present HAVC protocol, which consists of addressing, encapsulation, connection, and multiple transmission.
The address of HAVC (i.e., HAVC MAC address) is defined to be compatible with the standard Ethernet application programming interface (i.e., the standard MAC-48 or extended unique identifier (EUI)-48 ).
8 and 9 illustrate HAVC connection and the corresponding timing diagram, respectively.
HAVC-D is a method of distributing HAVC frames among all available HAVC paths (for example, N paths as shown in Fig.
where [Tr.sub.i] := Maximum HAC frame size/Bandwidth of the i-th HAVC path is the corresponding maximum transmission time, and
Td := Round trip time of the i-th HAVC path/2 is the corresponding end-to-end delay (between the user and HAVC-S), and then HAVC frames are sent through the HAVC path having the lowest score.
The result has shown that latency of HAVC is about 2-4 ms larger than that of IPSec (which is considered as a baseline) and its alternative, namely secure sockets layer (SSL) [32, Chapter 27].
Now, we test the average file transfer throughput for HAVC. The sizes of data in this test are 1 MB, 5 MB, 25 MB, 50 MB, and 100 MB.
Further, it is worthwhile to evaluate how well the proposed HAVC performs in dynamic networking conditions.
In this subsection, we conduct two HAVC experiments: one on TCP applications and the other on UDP applications.