submission doc.: ieee 802.11-14/1106r1 september 2014 peng shao, nec communication systems,...

15
Submission doc.: IEEE 802.11- 14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd. Slide 1 WLAN Frame Collision Information Date: 2014-09-05 Authors: N am e A ffiliations A ddress Phone em ail Peng Shao NEC Com munication System s, Ltd. 1753, Shim onum abe, N akahara-ku,K aw asaki- shi, K anagaw a Japan 211- 8666 +81-44-435-1177 [email protected] YukiBaba NEC Com munication System s, Ltd. 1753, Shim onum abe, N akahara-ku,K aw asaki- shi, K anagaw a Japan 211- 8666 +81-44-435-1177 [email protected] AkiraM atsum oto NEC Com munication System s, Ltd. 1753, Shim onum abe, N akahara-ku,K aw asaki- shi, K anagaw a Japan 211- 8666 +81-44-435-1177 matsumoto.kr@ ncos.nec.c o.jp PeterD avis Telecognix Corporation Yoshida Shim ooji-cho 58- 13, Sakyo-ku,K yoto Japan 606-8314 +81-75-213-3599 [email protected]

Upload: branden-baker

Post on 21-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 1

WLAN Frame Collision InformationDate: 2014-09-05

Name Affiliations Address Phone email Peng Shao NEC Communication

Systems, Ltd. 1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa Japan 211-8666

+81-44-435-1177 [email protected]

Yuki Baba NEC Communication Systems, Ltd.

1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa Japan 211-8666

+81-44-435-1177 [email protected]

Akira Matsumoto NEC Communication Systems, Ltd.

1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa Japan 211-8666

+81-44-435-1177 [email protected]

Peter Davis Telecognix Corporation

Yoshida Shimooji-cho 58-13, Sakyo-ku, Kyoto Japan 606-8314

+81-75-213-3599 [email protected]

Authors:

Page 2: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 2

Abstract

• Frame Collision in 11ax scenarios is a severe problem, which is an obstacle to realizing the goals of 11ax.

• In this contribution, we propose that supporting the use of Frame Collision information will be useful for reducing collisions by management and control in 11ax.

Page 3: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Background 1/2

• Frame Collision is when two (or more) frame signals are transmitted or arrive at the same time

• Frame Collisions occur when CSMA/CA fails• Failure of carrier-sensing (”hidden-terminal”)• Failure of avoidance due to identical backoff times

• Frame Collisions cause performance degradation• Interference, frame errors, retransmissions

• Frame Collisions occur often in 11ax scenarios with many terminals and high transmission rates [1][2]

• Necessity of collision management in 11ax has been mentioned in TGax [3][4]

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 3

Page 4: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Background 2/2

• Information related to Frame Collision is effective for reducing collisions by management and control• Examples: Site Survey, Channel Selection, Association, Rate

Control, Power Control, etc.

• Various forms of Frame Collision information can be obtained • Examples: Transmitter side, Receiver side, separate sensor

(“sniffer”)

• Frame Collision Detection (FCD) is needed to provide useful Frame Collision information

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 4

Page 5: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 5

(a) Power before and after frame

Frame Collision Pattern

時間

Power Signal

interference

frame

(b) Power changes during frame

power increase

power fluctuation

Examples of FCD: Power Signal Analysis

time

power colliding frames power

time

Page 6: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Examples of FCD: Power Signals

1. RSSI signal from power signal sensor [5] or spectral scan mode of WLAN card [6]

2. PHY state signal from WLAN card [7]

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 6

RSSIRSSI

timetime

power power

Frame-B Frame-A Frame-A Frame-A Frame-A + Frame-B

No collisions Collision

time

tx_frame/2rx_clear

countCollision

Page 7: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Frame Collision (FC) Information

• Examples• Existence or non-existence of collision events• Statistics of collisions

• ex. number or percentage of collisions• Collision TYPE information

• Store and share as Information Elements

• Use for management and control

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 7

Page 8: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Incorrect rate control (unknown cause of loss):

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 8

Using FC information for Control 1/2Example of Rate Control

No ACK received Decrease transmission rate

Leads to increased probability of collision

Optimal rate control (loss cause known to be collision):

No ACK received+ collision detected

Increase transmission rate

Leads to decreasedprobability of collision

Page 9: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Example of Collision Types

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 9

Sa

Sb

Ea

Eb

t

Power

Pa

Pb

Type Itransmitter of frame B cannot sense frame A

Type II: transmitters of A and B

choose same backoff

Type IIItransmitter of frame A cannot sense frame B

: Frame B(interference): Frame A

Sa<Sb Sa=Sb Sa>Sb

Page 10: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Using FC information for Control 2/2Examples of use of Collision Type Information

September 2014

Example of collision Collision type Examples of control by transmitter of frame A

Type I: transmitter of frame B cannot sense frame A

Increase transmission power

Type II: transmitters of A and B choose same backoff

Do nothing, orIncrease CWmin

Type III: transmitter of frame A cannot sense frame B

Decrease CCA level

: Frame B(interference): Frame A

Peng Shao, NEC Communication Systems, Ltd.Slide 10

A

B

A

B

B

A

Page 11: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Peng Shao, NEC Communication Systems, Ltd.

September 2014

Use power time series information before, during and after frames

Colliding signal

frame A

Threshold

Examples of Collision Type Classification Method

Colliding signal

frame A

Threshold

Slide 11

時間

A

B

時間

A

B

Frame Collision PatternPower Signal

Page 12: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Summary and Next Steps

• Proposal of use of Frame Collision information for improving management and control in 11ax

• Examples of Frame Collision Detection using power signal analysis

• Examples of control using Frame Collision information

• For greater effect, information of collision types can be used

Next:

• Propose method for handling FC information in 11ax

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 12

Page 13: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Straw Poll

Do you agree that TGax should support frame collision information?

Yes No Abstain

September 2014

Peng Shao, NEC Communication Systems, Ltd.Slide 13

Page 14: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Peng Shao, NEC Communication Systems, Ltd.

September 2014

Slide 14

References[1] “MAC Efficiency Analysis for HEW SG”, IEEE 802.11-13/0505r0, Minyoung Park (Intel)

[2] “Possible Approaches for HEW”, IEEE 802.11-13/0758r0, Katsuo Yunoki (KDDI Labs)

[3] “Understanding Current Situation of Public Wi-Fi Usage - Possible Requirements for HEW -”, IEEE 802.11-13/0523r2, Katsuo Yunoki (KDDI Labs)

[4] “Consideration on Efficiency Enhancement”, IEEE 802.11-13/0854r1, SangHyun Chang (Samsung

[5] IEICE Technical Report, SIP2012-125, p259-264, March 2014 , P. Shao

[6] “ath9k spectral scan”, http://wireless.kernel.org/en/users/Drivers/ath9k/spectral_scan/

[7] “Fwd: FW: Channel busy cycles”, ath9k-devel ML, http://article.gmane.org/gmane.linux.drivers.ath9k.devel/9887/

Page 15: Submission doc.: IEEE 802.11-14/1106r1 September 2014 Peng Shao, NEC Communication Systems, Ltd.Slide 1 WLAN Frame Collision Information Date: 2014-09-05

Submission

doc.: IEEE 802.11-14/1106r1

Peng Shao, NEC Communication Systems, Ltd.

Backup: Example of rx_clear count

September 2014

Slide 15

Result of CCA

:0 :1

rx_clear count

0 2 4 4 4 4 2 0 time

time

time

power