PROPOSAL SUMMARY FOR RTS/ANP proposed so far

Slides:



Advertisements
Similar presentations
LB84 General AdHoc Group Sept. Closing TGn Motions
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
IEEE WG Status Report – July 2005
IEEE White Space Radio Contribution Title
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
WRAN Protocol Reference Model(PRM)
Waveform Generator Source Code
[ Considering of Intra-cell multiple CBP response]
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
[place presentation subject title text here]
IEEE P Wireless RANs Date:
(Presentation name) For (Name of group) (Presenter’s name,title)
Fractional Bandwidth Usage
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
On Coexistence Mechanisms
WRAN Protocol Reference Model(PRM)
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
IEEE P Wireless RANs Date:
IEEE WG Opening Report – March 2007
November Opening Report
On Coexistence Mechanisms
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Experimental DTV Sensor
IEEE WG Opening Report – July 2008
“Comment Status” Definitions
ADS Study Group Mid-week Report
IEEE P Wireless RANs Date:
IEEE P Wireless RANs Date:
Spectrum Sensing Tiger Team
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
IEEE WG Opening Report – July 2007
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
Annex on TG1 detection for draft
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
[ Policies and Procedure Summary]
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
New Code for Symbol-to-Chip Spreading for Multiple PPDs
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGu Timeline Date: Authors: July 2005 July 2005
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

PROPOSAL SUMMARY FOR RTS/ANP proposed so far March 2007 doc.: IEEE 802.22-07/0101r0 PROPOSAL SUMMARY FOR RTS/ANP proposed so far IEEE P802.22 Wireless RANs Date: 2007-03-06 Authors: 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 patcom@iee.org. > Soo-Young Chang, Huawei Technologies Submission Slide 1

PROPOSAL SUMMARY FOR RTS/ANP proposed so far March 2007 doc.: IEEE 802.22-07/0101r0 PROPOSAL SUMMARY FOR RTS/ANP proposed so far Soo-Young Chang Huawei Technologies Mar. 6, 2007 Soo-Young Chang, Huawei Technologies Submission Slide 2

March 2007 doc.: IEEE 802.22-07/0101r0 INTRODUCTION Three proposals suggested for RTS/ANP issues for the initialization period and non- initialization period One proposal for the initialization period Two proposals for the non-initialization period To tackle various problems The author tried not to add his opinions/thoughts/comments to these proposals. Soo-Young Chang, Huawei Technologies Submission Slide 3

PROBLEMS IDENTIFIED SO FAR March 2007 doc.: IEEE 802.22-07/0101r0 PROBLEMS IDENTIFIED SO FAR Denial-of-service by “rogue” SPDs the PPD could suffer from denial-of-service if requests to transmit (RTS) arrive continuously or in large numbers from legitimate or rogue SPDs. Collision/congestion problem by multiple SPDs the PPD could suffer from collision/congestion problems also if requests to transmit (RTS) arrive continuously or in large numbers from legitimate or rogue SPDs. Soo-Young Chang, Huawei Technologies Submission Slide 4

THREE PROPOSALS March 2007 doc.: IEEE 802.22-07/0101r0 For the PPD initialization period Proposal 1 No RTS/ANP slot after a PPD beacon frame in initialization phase of the PPD. Illustration: [PPD][Sync burst with index 0] --> [PPD][Sync burst with index 0] --> For outside the PPD initialization period Proposal 2 RTS/ANP slot after each beacon frame (PPD or SPD) Illustration: [PPD or SPD][RTS/ANP slot] --> [PPD or SPD][RTS/ANP slot] --> ... Proposal 3 PPD sends a mandatory NACK in the RTS/ANP slot following an SPD beacon frame. Example: [PPD][RTS/ACK] --> [SPD][RTS/NACK] --> [PPD][RTS/ACK] --> [SPD][RTS/NACK] ... (this example illustrates the worst case, where an RTS is received in every RTS/ANP slot) Soo-Young Chang, Huawei Technologies Submission Slide 5

March 2007 doc.: IEEE 802.22-07/0101r0 PROPOSAL 1 No RTS/ANP slot after a PPD beacon frame in initialization phase of the PPD. Illustration: [PPD] [Sync burst with index 0]  [PPD][Sync burst with index 0]  …. Soo-Young Chang, Huawei Technologies Submission Slide 6

Go to non-initialization phase March 2007 doc.: IEEE 802.22-07/0101r0 Proposal 1 Start A PD turns on and it becomes the PPD PPD transmits one frame PPD transmits one sync burst with index 0 Timer: Initialization over? no yes Go to non-initialization phase Soo-Young Chang, Huawei Technologies Submission Slide 7

PROPOSAL 2 RTS/ANP slot after each beacon frame (PPD or SPD) Mar. 2007 doc.: IEEE 802.22-07/00xxr0 RTS/ANP slot after each beacon frame (PPD or SPD) Illustration: [PPD or SPD][RTS/ANP slot]  [PPD or SPD][RTS/ANP slot]  ... (2-1) the PPD issues NACKs to all SPDs whenever it needs to send its own beacon in the next frame and after then it transmits its beacon in the next frame and/or (2-2) the PPD issues a NACK to an SPD that the PPD judges it is a "rogue" SPD after the fixed number of repetition of continuous and repeated RTSs by the SPD. (optional) Soo-Young Chang, Huawei Technologies Submission Slide 8

Mar. 2007 doc.: IEEE 802.22-07/00xxr0 Proposal 2-1 only Start PPD transmits one frame PPD listens RTS no RTS received? yes PPD needs to transmit its own frame? yes no PPD transmits NACK PPD transmits ACK An SPD transmits one frame Soo-Young Chang, Huawei Technologies Submission Slide 9

Proposal 2-1 and 2-2 optional Start PPD transmits one frame PPD listens RTS no RTS received? yes PPD needs to transmit its own frame? yes no PPD transmits NACK PPD transmits ACK An SPD transmits one frame This SPD transmitted more than N consecutive frames? Proposal 2-1 and 2-2 yes no optional

PROPOSAL 3 March 2007 doc.: IEEE 802.22-07/0101r0 PPD sends a mandatory NACK in the RTS/ANP slot following an SPD beacon frame. Example: [PPD][RTS/ACK]  [SPD][RTS/NACK]  [PPD][RTS/ACK]  [SPD][RTS/NACK] ... this example illustrates the worst case, where an RTS is received in every RTS/ANP slot Soo-Young Chang, Huawei Technologies Submission Slide 11

Proposal 3