Submission doc.: IEEE 802.11-16/0336r0 March 2016 Xiaofei Wang (InterDigital)Slide 1 Relay Improvement: Regarding CID 9058 & 9075 Date: 2016-03-11 Authors:

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /1357r3 Nov Slide 1 Dynamic TIM and Page Segmentation Date: Authors: Weiping Sun, Seoul National University.
Advertisements

Submission doc.: IEEE 11-10/0259r0 March 2013 Jarkko Kneckt (Nokia)Slide 1 CID 266 & CID 281 Date: Authors:
Doc.: IEEE /0089r0 Submission Listen interval update Jan 2013 Slide 1 Date: Authors: Jinsoo Choi, LG Electronics.
Doc.: IEEE /1294r0 Submission November 2008 Kenan Xu, Nortel NetworksSlide 1 Enhancing BSS Transition Management Date: Authors:
Doc.: IEEE /0247r1 Submission March 2010 Sudheer Grandhi, InterDigital Communications, LLCSlide 1 AP Connection Period in TDLS Date:
Doc.: IEEE /0537r0 Submission May 2010 Kazuyuki Sakoda, Sony CorporationSlide 1 General frame format comment resolution overview Date:
Route Metric Proposal Date: Authors: July 2007 Month Year
Multi-STA BA Design Date: Authors: March 2016 Month Year
FILS Reduced Neighbor Report
Resolving Deadlocks in Comment Resolution
AP Power Saving Date: Authors: May 2017 Month Year
ANQP-SD Response When Service Mismatches
Month Year doc.: IEEE yy/xxxxr0 May 2012
Relay Flow Control Date: Authors: May 2013 Month Year
On AP Power Saving Usage Model
Purpose Indication of WUR Packets
P802.11aq Waiver request regarding IEEE RAC comments
P802.11aq Waiver request regarding IEEE RAC comments
Month Year Month Year doc.: IEEE yy/xxxxr0 doc.: IEEE /0135r0
Enhancing BSS Transition Management
Follow UP of Unifying Queue Size Report
Discussion on CID2199 Date: Authors: Jan 2014 Name Company
Comment resolution on BSR CID 8426
September 2008 doc.: IEEE /1003r0 August 2010
TGn Gen Ad Hoc July Motions
Proposed Modifications in TGh Draft Proposal
TGn Gen Ad Hoc May Motions
STA wake up using BSS Parameter Update Counter
FILS Handling of Large Objects
Group Delay for Group Addressed Wake Up Frames
Providing Faster GAS Response
Comment resolution on BSR CID 8426
TIM Compression for No Buffered Unicast Traffic
Resolution for CID 118 and 664 Date: Authors: Month Year
CR for CID 1105 Date: Authors: January 2019 Month Year
Discussion on CR for CID 5066
QoS STA function applied to Mesh STA
Proposed Resolutions to RFI comments of LB 166 on IEEE s D7.0
AP Power Down Notification
Comment resolution on BSR CID 8426
Enhancing BSS Transition Management
Follow UP of Unifying Queue Size Report
CID#89-Directed Multicast Service (DMS)
Comment resolution on CID 20175
QoS STA function applied to Mesh STA
Amendment for emergency alert system notification
Power Efficiency for Individually Addressed Frames Reception
Comment resolution on CID 20175
Route Metric Proposal Date: Authors: July 2007 Month Year
LB97 Coex: Duplicate DSSS
P802.11aq Waiver request regarding IEEE RAC comments
P802.11aq Waiver request regarding IEEE RAC comments
Comment resolution #79 Date: 2009, November 17 Authors: November 2009
Timing Measurement Date: Authors: Jan 2010 November 2007
Resolutions of the Remaining Power Management Comments
STA wake up using BSS Parameter Update Counter
doc.: IEEE <doc# >
AP Connection Period in TDLS
Month Year doc.: IEEE yy/xxxxr0 May 2012
Purpose Indication of WUR Packets
doc.: IEEE <doc# >
On AP Power Saving Usage Model
Proposed Change to Intra-Mesh Congestion Notification Frame
TGn Gen Ad Hoc March Status
Congestion Control Comments Resolution
TXOP Truncation Enhancement
Timing Measurement Date: Authors: Jan 2010 November 2007
On the Need for an ai Annex
Discussion on Functional Requirements
Purpose Indication of WUR Packets
Presentation transcript:

Submission doc.: IEEE /0336r0 March 2016 Xiaofei Wang (InterDigital)Slide 1 Relay Improvement: Regarding CID 9058 & 9075 Date: Authors:

Submission doc.: IEEE /0336r0 March 2016 Xiaofei Wang (InterDigital)Slide 2 Abstract This contribution highlights a problem for 11ah relay that was associated with CID 9058 & 9075 and discusses potential solutions.

Submission doc.: IEEE /0336r0 CID 9058 & 9075 Slide 3Xiaofei Wang (InterDigital) March TResolution to i-459 is incorrect. The comment identifies a specific technical problem and a specific technical solution. The assertion in the resolution is thus false. No valid technical reason for rejecting the commenter's proposed change is given. Include the specification requested, an alternate technical change to satisfy the comment, or record a valid technical reason why no change is required to the draft TCID 8459 was rejected based on "non specific technical details have been provided". The original comment was "An S1G relay AP may control the number of relays using No More Relay Flag, however, there does not seem to be any control on how many STAs each relay is allowed to associate. When it comes to controlling relayed traffic flow, it matters how many relays there are and how many STAs are associated with each relay. A limit on the number of STAs that each relay is allowed to associate should be considered." If needed, a presentation to the group can be submitted to explain the technical problem. Will provide a submission if desired. Both CIDs relate to CID 8459.

Submission doc.: IEEE /0336r0 CID 8459 Slide 4Xiaofei Wang (InterDigital) March /0159r1 An S1G relay AP may control the number of relays using No More Relay Flag, however, there does not seem to be any control on how many STAs each relay is allowed to associate. When it comes to controlling relayed traffic flow, it matters how many relays there are and how many STAs are associated with each relay. A limit on the number of STAs that each relay is allowed to associate should be considered. Suggest to add a limit on the number of STAs that each relay is allowed to associate, for example in the Relay Activation Response frames REJECTED (EDITOR: :07:43Z) The comment fails to identify a technical issue in sufficient detail. Should a S1G STA have some (optional) control on the numbers of STAs its relays can associate?

Submission doc.: IEEE /0336r0 11ah supports multi-hop relays A S1G STA can refuse more relays by setting the “No More Relay Flag” A S1G relay may use flow control if it is overwhelmed by traffic A S1G STA can turn on/off a Relay STA March 2016 Xiaofei Wang (InterDigital)Slide 5 A Few S1G Relay Characteristics

Submission doc.: IEEE /0336r0 Currently, there is no restrictions on how many STAs are allowed to associate with a Relay AP Theoretically up to 6000 STAs per Relay AP Aside from traffic generated by end STAs, there will also be a lot of Reachable Address reporting Aggregated traffic over a few hops of relays may overwhelm Relays and RootAPs Particularly when some S1G STAs may be operating on battery power A S1G STA has no control of how many next-hop Relay STAs that its relays STAs have (through the associated Relay APs) A S1G STA has no control of how many hops are attached to its Relay STAs (through the associated Relay APs) There is no possible way to predict how much traffic is routed through each Relay: it may be overwhelming! March 2016 Slide 6 Traffic Congestion Problem

Submission doc.: IEEE /0336r0 Such a problem may be hard to solve using existing mechanisms Flow control is designed to solve temporary problems, not for long-term issue such as there is too much traffic A STA that has visibility of the congested traffic cannot turn off its Relay STAs that are causing the problems easily after coverage has been established It is not aware of how many hops are beyond each Relay STAs It is not aware of how many Relays are associated with each Relay STAs It may cause severe coverage issues Potential solutions: Relay tree add/trim algorithms Restrict Relay STA behavior at time of activation March 2016 Slide 7 Traffic Congestion Problem

Submission doc.: IEEE /0336r0 Relay tree add/trim algorithm Complicated May be less desirable at the stage of 11ah Restrict Relay STA behavior at time of activation Simple Can be easily added E.g., by adding (optional) information to Relay Activation Element on how many STAs a Relay STA is allowed to associate through its Relay AP Two options: Reuse existing reserved bits Add optional field March 2016 Slide 8 Potential Solutions (1/2)

Submission doc.: IEEE /0336r0 Option 1: Reuse one or more bits from B3 – B7 Use a small set of numbers to indicate possible restrictions on the number of STA a Relay STA is allowed to associate: e.g., no restriction, 128, 256, 1024, etc. Option 2: Use one bit in B3 – B7 to indicate the presence of an optional Number of STA field Number of STA field may be one or two bytes long Indicated number may be precise or quantized as for Option 1 Other changes required to the draft: Section 10.51: add some descriptions on limit of number of STAs each Relay STA is allowed to associate through its Relay AP March 2016 Slide 9 Potential Solutions (2/2)

Submission doc.: IEEE /0336r0 Conclusion Slide 10Xiaofei Wang (InterDigital) March 2016 A traffic congestion problem is presented that are associated with CID 9058 & 9075 The problem is shown to be not easily solved using existing mechanisms Potential solutions have been discussed and presented

Submission doc.: IEEE /0336r0 Straw Poll 1 Slide 11Xiaofei Wang (InterDigital) March 2016 Do you agree that a Relay STA may optionally be restricted to associate with a limited number of STAs through its Relay AP? Y/N/A:

Submission doc.: IEEE /0336r0 Straw Poll 2 Slide 12Xiaofei Wang (InterDigital) March 2016 Which option do you prefer to limit the number of STAs that a Relay STA is allowed to associate through its Relay AP? Option 1 as presented on Slide 9 Y/N/A Option 2 as presented on Slide 9 Y/N/A Other options Y/N/A