Teledyne LeCroy UWBSpekChek and WiMedia Platform Test User Guide User Manual
Page 23
![background image](/manuals/353633/23/background.png)
UWBSpekChek™ WiMedia Platform Compliance
Test Guide
rev3.10
2
Page 23 of 33
Notes:
In addition to passing the normal background checks, the following points are manually
verified:
• The DUT/INTD should stop sending ctrl/data in the superframe where the
reservation conflict is introduced
• The DUT/INTD should relocate its reservation and continue transmitting in the
new reservation.
• The DUT and INTD are allowed to temporarily cease demonstrating operation
during this test case. Operation must automatically restart without manual
intervention if it ceases and sufficient bandwidth remains on the channel.
Test Case 2.3: Conflicting Reservation – Whole Superframe – Hard DRP
This test verifies that the DUT follows reservation size and location rules when it
operates on a channel with existing row reservation(s). The tester reserves the entire
SF with a "hard" DRP. It transmits this reservation with the tiebreaker bit set to zero
and a second time with it set to one. In one of these cases, the tester should "win",
forcing the DUT/INTD to resolve the conflict by canceling the reservation or changing
reservation status to zero.
Once the tester wins the tie-breaker, the DUT behavior should be verified against the
protocol rules below. This test is only performed on devices that have a row reservation
component when they operate on an empty channel.
Test procedure:
1.
Start analyzer capture.
2.
Test system starts the beacon period and sends a beacon in slot 2 with a BPOIE
that indicates that slots 3, 4, 5, and 6 are occupied. The BP Length is set to 16.
3.
Standard test start-up sequence.
4.
The test system begins to transmit beacons in slots 3, 4, 5, and 6 that contain
DRP IEs that reserve the whole superframe except the first 4 MAS with
reservation type Hard DRP. The tiebreaker bit is set to one initially. After one
second the tiebreaker bit is set to zero.
5.
After 2 seconds, test system stops beaconing.
6.
After at least 2 seconds, stop analyzer capture.
Notes: