Academia.eduAcademia.edu

Figure from:Traffic Modeling of LTE Mobile Broadband Network Based on NS2 Simulator

See full PDFdownloadDownload figure
Figure 3

Figure 3

Related Figures (9)

Fig. 1 E-UTRAN and EPC Architecture E-UTRAN architecture based on, eNB-1, eNB-2, and eNB-3 acts as a base station, and called E-UTRAN Node B. MME represents the Mobility Management Entity. S-GW is a serving gateway, and last, P-GW is a PDN (Packet Data Network) Gateway. Each eNB are connected to the MME/SAE Gateway by the S1 interface where as X2 interface is interconnecting the eNBs. The X2 interface is used also on U-plane for temporary user downlink data. The main functions of the eNB are: (1) radio resource management (radio bearer control, radio admission and connection mobility control, dynamic scheduling) and (2) routing user plane data towards SAE Gateway. The main task of MME/SAE Gateway is to distribute the migration of messages to eNBs; security control; encryption of user data, switching of U-plane to support of UE mobility; idle mode mobility handling [6].
Fig. 1 E-UTRAN and EPC Architecture E-UTRAN architecture based on, eNB-1, eNB-2, and eNB-3 acts as a base station, and called E-UTRAN Node B. MME represents the Mobility Management Entity. S-GW is a serving gateway, and last, P-GW is a PDN (Packet Data Network) Gateway. Each eNB are connected to the MME/SAE Gateway by the S1 interface where as X2 interface is interconnecting the eNBs. The X2 interface is used also on U-plane for temporary user downlink data. The main functions of the eNB are: (1) radio resource management (radio bearer control, radio admission and connection mobility control, dynamic scheduling) and (2) routing user plane data towards SAE Gateway. The main task of MME/SAE Gateway is to distribute the migration of messages to eNBs; security control; encryption of user data, switching of U-plane to support of UE mobility; idle mode mobility handling [6].
Fig. 2 shows the interface protocol stacks of S1 and X2. We used the same block diagram for two interfaces because it is similar, where the term (SI, X2 - AP) means that (S1-AP) or (X2-AP). Fig. 2 (S1 and X2) Interface User and Control Planes
Fig. 2 shows the interface protocol stacks of S1 and X2. We used the same block diagram for two interfaces because it is similar, where the term (SI, X2 - AP) means that (S1-AP) or (X2-AP). Fig. 2 (S1 and X2) Interface User and Control Planes
Fig.5 Congestion window (cwnd) of TCP Reno over LTE model
Fig.5 Congestion window (cwnd) of TCP Reno over LTE model
That mean, in slow-start phase, cwnd will increase until congestion happen or until cwnd less than slow start threshold (ssthresh). But if congestion happened, cwnd will decrease by (1/cewnd). Fig. 5 shows the congestion window and other phases, where the slow-start time was about 0.5 sec, and congestion point of network set on 55 Kbytes because the maximum expected window size is 110 Kbytes. That mean, Reno cwnd kept to the classical and standard behavior in our proposed topology, so we got a regular and ideal cwnd, especially in congestion avoidance phase.
That mean, in slow-start phase, cwnd will increase until congestion happen or until cwnd less than slow start threshold (ssthresh). But if congestion happened, cwnd will decrease by (1/cewnd). Fig. 5 shows the congestion window and other phases, where the slow-start time was about 0.5 sec, and congestion point of network set on 55 Kbytes because the maximum expected window size is 110 Kbytes. That mean, Reno cwnd kept to the classical and standard behavior in our proposed topology, so we got a regular and ideal cwnd, especially in congestion avoidance phase.
Fig.6 Queue Size versus time of TCP Reno over LTE model
Fig.6 Queue Size versus time of TCP Reno over LTE model
Fig.7 Lost Packets versus time of TCP Reno over LTE model
Fig.7 Lost Packets versus time of TCP Reno over LTE model
Fig. 8 Bandwidths versus time of TCP Reno over LTE model
Fig. 8 Bandwidths versus time of TCP Reno over LTE model