Pure ALOHA The original version of the protocol (now called Pure ALOHA, and the one implemented in ALOHAnet) was quite simple: • If you have data to send, send the data • If, while you are transmitting data, you receive any data from another station, there has been a message collision. All transmitting stations will need to try resending
later. Pure ALOHA does not check whether the channel is busy before transmitting. Since collisions can occur and data may have to be sent again, ALOHA cannot efficiently use 100% of the capacity of the communications channel. How long a station waits until it retransmits, and the likelihood a collision occurs are interrelated, and both affect how efficiently the channel can be used. This means that the concept of
retransmit later is a critical aspect; The quality of the backoff scheme chosen significantly influences the efficiency of the protocol, the ultimate channel capacity, and the predictability of its behavior. To assess Pure ALOHA, there is a need to predict its throughput, the rate of (successful) transmission of frames. First make a few simplifying assumptions: • All frames have the same length. • Stations cannot generate a frame while transmitting or trying to transmit. That is, while a station is sending or trying to resend a frame, it cannot be allowed to generate more frames to send. • The population of stations attempting to transmit (both new transmissions and retransmissions) follows a
Poisson distribution. Let refer to the time needed to transmit one frame on the channel, and define
frame-time as a unit of time equal to . Let refer to the mean used in the Poisson distribution over transmission-attempt amounts. That is, on average, there are transmission attempts per
frame-time. Consider what needs to happen for a frame to be transmitted successfully. Let refer to the time at which it is intended to send a frame. It is preferable to use the channel for one frame-time beginning at , and all other stations to refrain from transmitting during this time. For any frame-time, the probability of there being transmission-attempts during that frame-time is: \frac{G^k e^{-G}}{k!} The average number of transmission-attempts for two consecutive frame-times is . Hence, for any pair of consecutive frame-times, the probability of there being transmission attempts during those two frame-times is: :\frac{(2G)^k e^{-2G}}{k!} Therefore, the probability (Prob_{pure}) of there being zero transmission-attempts between and (and thus of a successful transmission for us) is: :Prob_{pure}=e^{-2G} The throughput can be calculated as the rate of transmission attempts multiplied by the probability of success, and it can be concluded that the throughput (S_{pure}) is: :S_{pure}=Ge^{-2G} The maximum throughput is frames per frame-time (reached when G=0.5), which is approximately 0.184 frames per frame-time. This means that, in Pure ALOHA, only about 18.4% of the time is used for successful transmissions.
Slotted ALOHA An improvement to the original ALOHA protocol was Slotted ALOHA, which introduced discrete time slots and increased the maximum throughput. A station can start a transmission only at the beginning of a time slot, and thus collisions are reduced. In this case, only transmission-attempts within 1 frame-time and not 2 consecutive frame-times need to be considered, since collisions can only occur during each time slot. Thus, the probability of there being zero transmission attempts by other stations in a single time slot is: Prob_{slotted} = e^{-G} the probability of a transmission requiring exactly k attempts is (k-1 collisions and 1 success): The chief difference between Slotted and Reservation ALOHA is that with Slotted ALOHA, any slot is available for utilization without regard to prior usage. Under Reservation ALOHA's
contention-based reservation schema, the slot is temporarily considered "owned" by the station that successfully used it. Additionally, Reservation ALOHA simply stops sending data once the station has completed its transmission. As a rule, idle slots are considered available to all stations that may then implicitly reserve (utilize) the slot on a contention basis.
Packet Reservation Multiple Access Packet reservation multiple access (PRMA) is an implicit reservation scheme. Some fixed number of slots form a frame. After each frame, the satellite broadcasts the status of each slot from the previous frame, which indicates the reservation status of the corresponding slots of the next frame. All ground stations wishing to transmit compete exactly like slotted ALOHA during any "free slot" of that next frame (i.e., either no one transmitted in that slot of the previous frame, or there was a collision when multiple ground stations transmitted in that slot of the previous frame). If exactly one ground station happens to transmit during a "free slot", that ground station succeeds in reserving that slot of a frame -- the corresponding slot is implicitly reserved in all future frames. From then on, the satellite broadcasts that that particular ground station has reserved that slot of the frame, and that ground station can continue transmitting with a guaranteed data rate during that slot of the frame; other ground stations are careful
not to transmit during that slot of the frame, so there are no collisions during reserved slots. When a ground station with a reserved slot has nothing to send, it simply stops transmitting, which gives up its reservation; the satellite notices its reserved slot is idle in one frame, and broadcasts that fact, which indicates that that slot will be a "free slot" in the next frame. Maximum channel efficiency for slotted ALOHA is 36%; PRMA improves maximum channel efficiency to 80%. Maximum channel efficiency for slotted ALOHA is 36%; DAMA improves maximum channel efficiency to 80%. The
AX.25 packet radio protocol is based on the CSMA approach with collision recovery, based on the experience gained from ALOHAnet. A variation of CSMA,
CSMA/CD is used in early versions of
Ethernet. ALOHA and the other random-access protocols have an inherent variability in their throughput and delay performance characteristics. For this reason, applications that need highly deterministic load behavior may use
master/slave or
token-passing schemes (such as
Token Ring or
ARCNET) instead of
contention systems. ==Hardware==