Changes between Version 9 and Version 10 of 802.11/wlan_exp/app_notes/tutorial_token_mac

Timestamp:

Jul 8, 2015, 9:51:30 AM (9 years ago)

Author:

chunter

Comment:

--

802.11/wlan_exp/app_notes/tutorial_token_mac

@@ -23 +23 @@
 ||  ''TokenMAC avoids contention not through randomness, but rather through explicit token passing from a managing Access Point (AP).'''  ||
 
-In this tutorial, we will modify the role of an Access Point (AP) to include the responsibility of managing which device on its network has a token and is permitted to transmit.
+To create TokenMAC, we will need to alter pieces of the underlying reference design. This application note is organized into the following sections:
+
+ * '''[wiki:./CPU_HIGH Alterations to CPU_HIGH]''' -- In this section, we will describe and discuss the changes needed to the high-level MAC code to realize the design. Specifically, we will modify the AP codebase to allow it to determine which node in the network should have the token and for how long it should have it.
+ * '''[wiki:./CPU_LOW Alterations to CPU_LOW]''' -- In this section, we will describe and sicuss the changes needed to the low-level MAC code to realize the design. Here, we will not start off with the DCF code since the vast majority of that DCF behavior is irrelevant to TokenMAC. Instead, we will use the very simple [browser:ReferenceDesigns/w3_802.11/c/wlan_mac_low_nomac NoMAC] project as a starting point. Unaltered, this project acts as a straight passthrough connection between the high-level MAC and the PHY.
+ * '''[wiki:./characterization Characterizing the Design]''' -- Once the design is complete, we will use the [wiki:802.11/wlan_exp WLAN Experiments Framework] to characterize the design and analyze its strengths and its weaknesses.
+ * '''[wiki:./extensions Extensions]''' -- Having established the design's weaknesses in the previous characterization section, we will propose and construct extensions to TokenMAC to strengthen its weaknesses. The intent of this section is to demonstrate how to "close the loop" between design, experimentation, and then re-design based on what was learned during the experimental phase.
+