没有合适的资源?快使用搜索试试~ 我知道了~
首页ns3教程,非常适合初学者
资源详情
资源评论
资源推荐

Network Simulator 3 (ns-3.16) Patches (Version 1.0)
for Vehicle-2-Vehicle Broadcast Simulations
Developed 2013-2014
These patches have been developed jointly at WINLAB, Rutgers University and West Virginia
University as part of the V2V safety communications scalability activity of the Interoperability
Issues of Vehicle-to-Vehicle Based Safety Systems (V2V-Interoperability) Project headed by the
Crash Avoidance Metrics Partnership (CAMP) Vehicle Safety Communications 3 (VSC3)
Consortium, in partnership with the United States Department of Transportation (USDOT).

MAC Layer Patches
• Backoff Timer Countdown Correction: Adjusts the countdown procedure of backoff timer
when nodes are using 802.11 Enhanced Distributed Channel Access (EDCA) as the MAC
layer control model. [Bug 1205]
• Additional Backoff Timer Trigger: Initiates an additional backoff when a channel access
is requested and the channel is in either IFS idle or ack timeout, while the backoff timer is
zero.
• Queue Management Policy: Provides an option which allows to drop the oldest packet in
the packet queue instead of the newest packet when the queue is full.
Physical Layer Patches
• Frame Capture: Allows the nodes to switch to a stronger signal during an ongoing reception
of a packet with a weaker signal.
Other Patches
• Mobility Helper: Improves the accuracy of mobility model when GPS data is used as the
mobility trace input.

Backoff Timer Countdown Correction
The default ns-3.16 implementation of the Enhanced Distributed Channel Access (EDCA) follows
the backoff timer countdown rule from the deprecated IEEE 802.11 Distributed Coordination
Function (DCF). The mechanism seeks to reduce collisions in a distributed network of wireless
stations. In both mechanisms, stations rely on carrier sensing to determine if the wireless medium
is currently busy. If so, stations wait for a random time interval before retrying to access the
channel. This random delay is referred to as backoff.
The EDCA method prioritizes channel access into different traffic classes. It defines four Access
Categories (ACs) with different backoff parameters. In addition, it also allows each AC to have a
different Arbitration Inter-Frame Space (AIFS). The AIFS further controls how long a transmitter
has to wait after the medium becomes idle. However, the EDCA also introduces a subtle change
in the way that backoff countdown is performed.
Figure 1 - The difference between DCF and EDCA Backoff Timer Countdown
In ns-3.16, the EDCA function and the DCF function share one class, DcfManager, for backoff-
timer countdown. However, as illustrated in Figure 1, the IEEE 802.11 standard mandates different
times at which the backoff timer is decremented in the two functions. The backoff timer is
decremented at the beginning of a slot for EDCA and at the end of a slot for DCF. In other words,
for EDCA, the medium needs to be idle only for an AIFS[AC] period before the backoff timer is
decremented, while the backoff timer has to wait for one Distributed Inter-Frame Space (DIFS)

plus one SlotTime before decrementation in the DCF. In the latter case, if the medium becomes
busy again during this slot time, the backoff timer remains unchanged. Therefore, to accurately
implement the EDCA functionality, the backoff timer needs to be changed in ns-3 simulator.
The modification steps are as follows: First, the idle duration of medium is tracked by each station.
Once the idle duration of one station becomes greater than or equal to AIFS, the next step is
triggered. In step two, the slot boundary of AIFS is identified and the potential decrement for the
backoff timer counter is increased by one. Hence, the length of the idle duration after AIFS is
divided by the length of one SlotTime and, in step three, the backoff timer counter is decremented
by the quotient plus one. When the backoff timer reaches zero, the station is allowed to
immediately transmit after the medium becomes idle for one AIFS.
Additional Backoff Timer Trigger
EDCA-mac-fixes-patches.tar.gz
In ns-3, once a frame is generated in the upper layer and ready for transmission, the station requests
to access to the medium immediately. According to the standard, there are two possible situations
for this access request.
• If the medium is busy as indicated by either physical or virtual carrier sensing, and the
counter of backoff timer is equal to zero, the station should invoke a backoff procedure.
• If the counter of backoff timer is equal to zero and the medium is idle for at least one AIFS
(i.e., the medium is not seized by another station), the station should immediately start the
transmission.
Taking into consideration the situation where the counter of backoff timer is zero and the idle
duration is less than one AIFS. There are two options: after AIFS, the station either transmits the
frame immediately, or initiates an additional backoff procedure. Based on the conditions for
initiating a transmission for EDCA in the 802.11 standard: “there is a frame available for
transmission at that Enhanced Distributed Channel Access Function (EDCAF), and the backoff
timer for that EDCAF has a value of 0”. Although the situation fits the condition, the second option
is chosen, since even though the medium is indicated as idle when the station claims its request,
the medium might not be truly idle. In other words, the AIFS is a part of the EDCA function that
剩余15页未读,继续阅读
















Jerry&张
- 粉丝: 0
- 资源: 1
上传资源 快速赚钱
我的内容管理 收起
我的资源 快来上传第一个资源
我的收益
登录查看自己的收益我的积分 登录查看自己的积分
我的C币 登录后查看C币余额
我的收藏
我的下载
下载帮助

会员权益专享
最新资源
- ARM Cortex-A(armV7)编程手册V4.0.pdf
- ABB机器人保养总结解析.ppt
- 【超详细图解】菜鸡如何理解双向链表的python代码实现
- 常用网络命令的使用 ipconfig ping ARP FTP Netstat Route Tftp Tracert Telnet nslookup
- 基于单片机控制的DC-DC变换电路
- RS-232接口电路的ESD保护.pdf
- linux下用time(NULL)函数和localtime()获取当前时间的方法
- Openstack用户使用手册.docx
- KUKA KR 30 hA,KR 60 hA机器人产品手册.pdf
- Java programming with JNI
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈



安全验证
文档复制为VIP权益,开通VIP直接复制

评论1