Discussion is needed; Use of wrap around with CSMA may create artefacts Is the ‘random’ position of STAs randomly generated by each simulation run, or are we going to have a file with common positions? Several channel model and RF related parameters that are likely to be common and fixed across scenarios see #1383 Scenarios summary This document reports the initial agreement according to document 11-13/1000r2. Scenario Name Topology Management Channel Model Homogeneity ~Traffic Model 1 Residential A - Apartment building e.g. ~10m x 10m apartments in a multi-floor building ~10s of STAs/AP, P2P pairs Unmanaged Indoor Flat Home 2 Enterprise B - Dense small BSSs with clusters e.g. ~10-20m inter AP distance, ~100s of STAs/AP, P2P pairs Managed Indoor Flat Enterprise 3 Indoor Small BSS Hotspot C - Dense small BSSs, uniform e.g. ~10-20m inter AP distance ~100s of STAs/AP, P2P pairs Mobile 4 Outdoor Large BSS Hotspot D - Large BSSs, uniform e.g. 100-200m inter AP distance ~100s of STAs/AP, P2P Managed Outdoor Flat Mobile 4a Outdoor BSS Hotspot + Residential D+A Managed + Unmanaged Hierarchical Mobile + Home
Per each use same primary channel across BSSs Aggregation [A-MPDU / max aggregation size / BA window size, No A-MSDU, with immediate BA] Max # of retries 10 RTS/CTS Threshold [no RTS/CTS] Association X% of STAs are associated with the strongest AP, Y% of STAs are associated with the second-strongest AP, and Z% of STAs associate with the third-strongest AP. Z% of STAs are not associated. Association is based on RSSI, i.e., received power as determined by path loss, shadowing, and any penetration loss (but not multipath). Detailed distribution to be decided. [X=100,Y=0,Z=0] Management It is allowed to assume that all APs belong to the same management entity Traffic model (per each BSS) - TBD # Source/Sink Name Traffic definition Flow specific parameters AC Downlink D1 AP/STA1 to AP/STA10 Highly compressed (streaming) T2 D2 to AP/STA20 Web browsing T4 D3 AP/STA21 to AP/STA30 Local file transfer T3 D4 AP/STA31 to AP/STA 70 Multicast Streaming T8 Uplink U1 STA1/AP to STA10/AP Highly compressed video (streaming) – UL TCP ACKs… U2 STA11/AP to STA20/AP Web browsing: – UL TCP ACKs… U3 STA21/AP to STA30/AP file transfer T3 U4 STA/AP31 to STA/AP 70 - - P2P P1 NONE (see interfering scenarios) Idle / Management M1 AP Beacon TX M2 to STA TBD Probe Req. TY
Outputs: MAC tput. Test 2b: Deferral Test 2 Goal: This test case is designed to verify whether the simulator can correctly handle deferral procedure after collision happens with the existing of hidden nodes. Assumptions: AP1 and AP2 can not hear each other. ( ever) Interference Assumptions: If any part of an MPDU sees interference, that MPDU should fail If any part of a data preamble sees interference, all MPDUs should fail If an MPDU, or data premable sees no interference, it should pass If an ACK overlaps with the transmission of an OBSS AP, the PER on the ACK should be 0. (i.e. the ACK should pass) Backoff If no ACK is received, the transmitter should double it’s CW. If an ACK is received, the transmitter should reset its CW If no MPDUs are decoded, no ACK should be sent. After 10 missing ACKS, the CW should be reset. PER definition PER= 1-Acked data MPDUs/Total data MPDUs sent ( TPUT can be computed from number of successfully ACKed MPDUs and the total time) data MPDUs are measured by the transmitters
Traffic Model # Traffic model name Description Application traffic (Forward / Backward) Application Load (Mbps) (Forward / Backward) A-MPDU Size (B) (Forward / Backward) T1 Local file transfer FTP/TCP transfer of large file within local network FTP file transfer / FTP TCP ACK Full buffer / 0.1 Max / 64 T2 Lightly compressed T3 Internet streaming video/audio T4 4k streaming T5 Online game server T6 Management: Beacon T7 Management: Probe requests T8 Multicast Video Streaming UDP/IP transfer of compressed video streaming UDP packet transfer/Nothing 3-6Mbps/Nothing T8 Gaming T9 VoIP Reference traffic profile for Scenario 4 Traffic Model # Traffic model name Description Application traffic (Forward / Backward) Application Load (Mbps) (Forward / Backward) A-MPDU Size (B) (Forward / Backward) T1 Local file transfer FTP/TCP transfer of large file within local network FTP file transfer / FTP TCP ACK Full buffer / 0.1 Max A-MPDU / 64 T2 Lightly compressed video T3 Internet streaming video/audio T4 4k video streaming T5 Online game server T6 Management: Beacon T7 Management: Probe requests T8 VoIP References for traffic models 11-13/486, “HEW video traffic modeling” Guoqing Li et al, (Intel) [1] [2] [3]11-09-0296-16-00ad-evaluation-methodology.doc