offset.time: This implementation is similar to the ATM
Block Transfer and Delayed Transmission (ABT-DT). The ingress node sends each
control packet, followed by its corresponding data burst after an offset time. Thus,
data bursts are sent without waiting for any acknowledgment or feedback on the reservation
requests. This one-way reservation scheme avoids the two-way-reservation
propagation delay in order to reduce the data waiting time at the ingress nodes. In this
scheme, to efficiently calculate the offset time, some sort of source routing is used to
determine the number of intermediate nodes from source to destination.
Channel.Reservation.Schemes
Under the source-routing-dependent offset time implementation, four channel reservation
schemes can be identified. Depending on when the channel reservation starts and ends, the
reservation schemes differ in their burst-dropping performance and their complexity. Accompanied
by the illustration in Figure 2, the schemes are briefly explained as follows:
???. Scheme.1: Each BCP contains the offset time that separates it from its corresponding
DB, but not the duration of the DB. Thus, the core nodes reserve a channel as soon
as they receive the BCP (reservation request).
Pages:
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764