Download File - Computer Networks & Information Security
Download File - Computer Networks & Information Security Download File - Computer Networks & Information Security
Receive-Initiated Collision Avoidance [Garcia99Mobicom] A receiver sends a message to a sender requesting it to being a packet transfer Difficulty: The receiver must somehow know (or poll to find out) when a sender has a packet to send Issue of fairness using receiver-based protocols has not been studied (to my knowledge) No reason to believe that receiver-initiated approach can achieve better fairness than source-initiate approach 302
Using Receiver’s Help in a Sender-Initiated Protocol For the scenario below, when node A sends an RTS to B, while node C is transmitting to D, node B cannot reply with a CTS, since B knows that D is sending to C When the transfer from C to D is complete, node B can send a Request-to-send-RTS to node A [Bharghavan94Sigcomm] Node A then immediately sends RTS to node B A B C D 303
- Page 251 and 252: Geocasting using Modified Anycastin
- Page 253 and 254: Other Geocasting Schemes [Macwan01
- Page 255 and 256: Some Related Work Content-based Mu
- Page 257 and 258: Capacity of Fixed Ad Hoc Networks [
- Page 259 and 260: Continues from last slide … Dela
- Page 261 and 262: Measured Scaling Law [Gupta01] Mea
- Page 263 and 264: Medium Access Control Protocols 263
- Page 265 and 266: Hidden Terminal Problem Node B can
- Page 267 and 268: Reliability Wireless links are pro
- Page 269 and 270: IEEE 802.11 Wireless MAC Distribut
- Page 271 and 272: Collision Avoidance With half-dupl
- Page 273 and 274: B1 = 25 B2 = 20 cw = 31 DCF Example
- Page 275 and 276: MAC Protocols: Issues Hidden Termi
- Page 277 and 278: Binary Exponential Backoff in DCF
- Page 279 and 280: IEEE 802.11 Distributed Coordinatio
- Page 281 and 282: Fairness Issue Assume that initial
- Page 283 and 284: MACAW Solution for Fairness When a
- Page 285 and 286: Distributed Fair Scheduling (DFS) [
- Page 287 and 288: Impact of Collisions After collisi
- Page 289 and 290: Distributed Fair Scheduling DFS us
- Page 291 and 292: Fairness in Multi-Hop Networks Not
- Page 293 and 294: Balanced MAC degree of node j p_ij
- Page 295 and 296: Balanced MAC Results show that it
- Page 297 and 298: Estimation-Based Fair MAC Fair sha
- Page 299 and 300: Proportional Fair Contention Resolu
- Page 301: Sender-Initiated Protocols The pro
- Page 305 and 306: Receiver-Based Adaptive Rate Contro
- Page 307 and 308: Capacity and MAC Protocols The MAC
- Page 309 and 310: Energy Conserving MAC Since many m
- Page 311 and 312: A Power Aware Multi-Access Protocol
- Page 313 and 314: PAMAS PAMAS uses a control channel
- Page 315 and 316: Another Proposal in PAMAS To avoid
- Page 317 and 318: UDP on Mobile Ad Hoc Networks 317
- Page 319 and 320: UDP Performance Several relevant s
- Page 321 and 322: UDP Performance Difficult to ident
- Page 323 and 324: Overview of Transmission Control Pr
- Page 325 and 326: Transmission Control Protocol (TCP)
- Page 327 and 328: Cumulative Acknowledgements A new
- Page 329 and 330: Window Based Flow Control Sliding
- Page 331 and 332: Window Based Flow Control Congesti
- Page 333 and 334: How does TCP detect a packet loss?
- Page 335 and 336: Retransmission Timeout (RTO) calcul
- Page 337 and 338: Fast Retransmission Timeouts can t
- Page 339 and 340: Congestion Avoidance and Control S
- Page 341 and 342: Congestion Control On detecting a
- Page 343 and 344: Congestion window (segments) 25 20
- Page 345 and 346: ssthresh = Fast Recovery min(cwnd,
- Page 347 and 348: Slow-start Congestion avoidance F
- Page 349 and 350: Performance of TCP Several factors
- Page 351 and 352: Random Errors May Cause Fast Retran
Receive-Initiated Collision Avoidance<br />
[Garcia99Mobicom]<br />
A receiver sends a message to a sender requesting it<br />
to being a packet transfer<br />
Difficulty: The receiver must somehow know (or poll<br />
to find out) when a sender has a packet to send<br />
Issue of fairness using receiver-based protocols has<br />
not been studied (to my knowledge)<br />
No reason to believe that receiver-initiated approach can<br />
achieve better fairness than source-initiate approach<br />
302