Motivation

January 2008
doc.: IEEE 802.22-07/0542r1
IEEE P802.22
Wireless RANs
Effective NPD Periodic Update
Date: 2008-01-04
Author(s):
Name
Baowei Ji
Company
Samsung Telecom.
America
Address
Phone
USA
+1-972-761-7167
Shan Cheng
Samsung Electronics
Korea
+82 31 279 7557
Jinxia Cheng
Samsung Electronics
China
+86 10 6439 0088
3133
David
Mazzarese
Samsung Electronics
Korea
+82 10 3279 5210
Euntaek Lim
Samsung Electronics
Korea
+82 31 279 5917
email
[email protected].
com
cheng.shan@sam
sung.com
jinxia.cheng@sa
msung.com
d.mazzarese@sa
msung.com
et.lim@samsung.
com
Abstract
Address comment #19.
Similar as the requirement for an SPD to periodically update its existence, the NPD shall also
periodically send heartbeat signals to let the PPD and other SPDs know its existence. However, to the
opposite of the operation of an SPD, the NPD should send the NPD codeword when the PPD has not
sent NACK in the last superframe, namely when it is not the PPD that has sent beacon frame in the
current superframe. This will guarantee that only the NPD is transmitting at that Rx period, which is
free of collision. Moreover, the NPD will try to avoid sending its codeword at the Rx periods when
other SPDs may also send their RTS codeword, which reduces the potential collisions.
Notice: This document has been prepared to assist IEEE 802.22. It is offered as a basis for discussion and is not binding on the
contributing individual(s) or organization(s). The material in this document is subject to change in form and content after
further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution,
and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE
Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit
others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and
accepts that this contribution may be made public by IEEE 802.22.
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures
<http://standards.ieee.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known
use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with
respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the
Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in
the development process and increase the likelihood that the draft publication will be approved for publication. Please notify
the Chair <Carl R. Stevenson> as early as possible, in written or electronic form, if patented technology (or technology under
patent application) might be incorporated into a draft standard being developed within the IEEE 802.22 Working Group. If you
have questions, contact the IEEE Patent Committee Administrator at <[email protected]>.
Submission
page 1
Baowei Ji, Samsung Electronics
January 2008
doc.: IEEE 802.22-07/0542r1
Motivation
The current P802.22.1/D2 work document has good features, such as
1. An SPD and the NPD shall periodically update the PPD about their existence.
2. An SPD shall re-try RTS transmission only when the PPD sends NACK in the last ANP period in order to
avoid wasting RTS transmission opportunities.
One concern with Item 1 is that the NPD has to do periodic update far more frequent than the other SPDs do.
Actually, the NPD has to transmit the NPD codeword at least once every 10-superframe interval. This could result
in collisions with the RTS transmissions from other SPDs.
When the NPD has a beacon frame to send out, it will operate just like other SPDs --- send an RTS codeword
first, and if permitted by the PPD, send the beacon frame. Even when an SPD does periodic update, it still has to
use the same procedure because the SPD can only be identified from the information embedded in the beacon
frame sent by it. For all those kinds of operation, the NPD and/or an SPD shall send an RTS codeword only when
the PPD has sent NACK in the last superframe, namely, the PPD has just sent its beacon frame in the current
superframe and it is possible for the PPD to allow other PD to send beacon frame in the next superframe.
However, the periodic update of the NPD could be treated differently because of the uniqueness of the NPD
codeword. To the contrary to what described above, the NPD shall try to send the NPD codeword when the PPD
has not sent NACK in the last superframe, i.e., the PPD has not transmit its beacon frame in the current
superframe. Even though the PPD will definitely deny any request from other PDs so that that it can send its
beacon frame in the next superframe, the uniqueness of the NPD codeword still broadcasts its existence and
satisfying the purpose of NPD periodic update. This will guarantee that only the NPD is transmitting at that Rx
period, which is free of collision. Moreover, the NPD will try to avoid sending its codeword at the Rx periods
when other SPDs may also send their RTS codeword, which reduces the potential collisions. It could occur that
the PPD has continuously sent NACK in a large number of consecutive superframes, in which case the NPD shall
send the NPD codeword if its periodic timer expires.
One last change should have been done in the last letter-ballot comment resolving process. An SPD shall never
send an RTS burst if the PPD has not sent NACK in the last ANP period. Note that the PPD has to send NACK at
least every other superframe.
Suggested text to be included in the draft
Modify 7.4.2 as follows:
7.4.2 Transmission protocol
All transmissions shall be made using the ALOHA protocol. Only the PPD shall transmit beacon frames
unless an SPD has been granted permission to do so in place of the PPD. In order to gain permission to
transmit a beacon frame, an SPD transmits an RTS burst without first listening for other beaconing devices. If the PPD has
sent NACK in the last ANP period, the MLME of the SPD generates the PLME-INITIATE-RTS-BURST.request message so
that the PLME shall send the RTS burst in the Rx period of the current superframe. Otherwise, the MLME defers and shall
not generate the PLME-INITIATE-RTS-BURST.request message unless the PPD has sent NACK in the last ANP period.
When the NPD has beacon frame to transmit, it shall go through the same procedure including the re-try procedure as
specified in 7.4.3. However, the periodic update of the NPD shall be treated differently because of the uniqueness of the NPD
codeword. As shown in Figure xx, the NPD starts the NPD codeword transmission procedure when its periodic timer is about
to expire within 2 superframes. If the PPD has not sent NACK in the last ANP period, the MLME of the NPD shall generate
the PLME-NPD-HEARTBEAT.request message so that the PLME shall send the NPD codeword in the Rx period of the
current superframe. Otherwise, it defers to the next superframe if the NPD periodic update timer has not expired yet. When
the timer expires, the NPD shall send the NPD codeword even if the PPD has sent NACK in the last ANP period.
In the event that two or more SPDs transmit an RTS burst simultaneously, at least one should be
successfully received by the PPD. In this case if no RTS burst is received, the PPD will transmit a NACK
during the ANP and then continue to transmit its own beacon frame. If one is received and the PPD does not
elect to transmit its own beacon frame, the PPD will transmit the ACK corresponding to the RTS burst it
heard. In the unlikely event that two or more SPDs chose the same RTS codeword and so received the
Submission
page 2
Baowei Ji, Samsung Electronics
January 2008
doc.: IEEE 802.22-07/0542r1
corresponding ACK, both will proceed to transmit a beacon frame. An SPD will know whether the PPD
received its beacon frame by examining the contents of the PPD's subsequent beacon frames. The PPD's
beacon frame shall only contain the data from an SPD if it correctly received the SPD's beacon frame.
Normal Operation
Will the NPD periodic update timer
expire within 2 superframes?
No
Yes
Has the NPD periodic update timer
expired?
Wait until the
next superframe
Yes
No
Has the PPD sent NACK
in the last superframe?
No
Yes
No
Send NPD codeword in the Rx
period of the current superframe
Complete the RTS transmission,
reset the NPD Periodic update timer.
Figure xx- The procedure for NPD to transmit the NPD codeword
Modify the paragraph between lines 24-34 on page 68 as follows:
If the PPD detects an RTS burst from an SPD and has decided to reserve the upcoming superframe for that
SPD, the PPD shall transmit the ACK corresponding to the received RTS codeword during the ANP. The
PPD shall then enable its receiver for a period of one slot. If, during this time, the beacon frame of the SPD
is detected, the receiver shall remain on, and the beacon frame shall be received and passed to the next
higher layer via the MLME-INCOMING-BEACON.indication primitive. Immediately following the beacon
frame reception (and following the one-slot period, if a beacon frame is not detected), the receiver shall
remain enabled through the receive period, where the PPD again listens for an RTS burst. No SPD shall
transmit an RTS burst during the receive period following another SPD’s beacon frame. However, if the
PPD does hear one, it shall be ignored. Only the NPD could send the NPD codeword during the Rx period following another
SPD’s beacon frame. The PPD shall transmit a NACK during the ANP no matter what it has received in the Rx period
whether it receives
an RTS burst or not, in order to ensure that at least every other beacon frame is transmitted by the PPD. Nonetheless, the PPD
and other SPDs are still informed of the existence of the NPD if the NPD codeword is received during this ANP period
because of the uniqueness of the codeword.
Submission
page 3
Baowei Ji, Samsung Electronics