Revisions Revisions of document 13/1001 Revision Comments Date R0 Initial template Aug 28th R1 Sept 15th 2013 R2 Made it consistent with document 1000r2 Sept 16th 2013 R3 Included Scenario 1 from 1081r0 Included Scenario 2 from 722r2 Included Scenario 3 and 4 from 1248r0; scenario 3 likely compatible with documents 722 and 1079. Included concept from 1176r0 Added References Updated co-authors Oct 4th 2013 R4 Minor corrections Oct 4th 2013 R5 description for scenario 4a (Simone (Qualcomm), Ron (Broadcom)) Tentative addition of contributions related to traffic models; more discussion is needed: Added video traffic models from #1335 (Guoqing Li, Intel) Table for traffic models (Bill, Sony) Management Traffic profile and % of unassociated users (Reza, Cisco) Application activity intervals (Huai-Rong, Samsung) Indicated that legacy STAs can be present (Various) Nov 14th 2013
DL: AP – STA traffic P2P traffic (tethering, Soft-APs, TDLS) ‘Idle’ management (generating management traffic such as probes/beacons) Power model List of PHY, MAC, Management parameters We may want to fix the value of some parameters to limit the degrees of freedom, and for calibration Optionally, some STAs may use legacy (11n/ac) operation parameters, if required to prove effectiveness of selected HEW solutions An interfering scenario (its performance optionally tracked) Not managed or managed by a different entity than the one of the main scenario Defined by its own Topology, Traffic and parameters Per each of above items, the scenario description defines a detailed list of parameters and corresponding values. Values not specified can be set to any Values included in square brackets [] are default values to be used for calibration. All parameters values not included in [], are to be considered mandatory for performance evaluation. Simulation results should be presented together with the specification of the value used per each of the parameters in the tables. Notes on this version This document builds on document 13/1001r9, which was developed during the HEW SG phase. The document consolidates contributions on scenarios details from various authors and reflects the comments/submissions received. It is not a final version by any means and is subject to changes based on further discussion and feedback. TBDs Traffic models Channel models an penetration losses per scenario Not agreement on which channel models to be used in each scenario; some tentative included in the document Calibration scenarios; Some other topics under discussion refer to simulation methodology/parameters that can be common and fixed across all scenarios, hence they may be directly included in the Evaluation Methodology document or in an appendix of this documents Rate adaptation model Use of wrap around for scenarios 3 and 4? 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 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
Deep Sleep Listen TSDL = 3ms Power Save Mechanism parameters Mechanism Parameter Definition/Values Pick one value from the Suggested Set of Simulation Values ** Power save mode (PSM) Beacon Interval (BI) 100 TU 100 TU DTIM Integer in unit of BI { 1, 3 } PSM timeout Length of time before STA goes to sleep { 50, 100, 200 } ms Pre-Target Beacon Transmission Time (TBTT) Length of time before a STA wakes before Beacon { 0 } ms Beacon timeout Length of time after TBTT { 5 } ms save polling (PSP) Beacon Interval 100 TU 100 TU DTIM Integer in unit of BI { 1, 3 } Pre-Target Beacon Transmission Time (TBTT) Length of time before a STA before Beacon { 0 } ms Beacon timeout Length of time TBTT { 5 } ms Unscheduled automatic power save delivery Beacon Interval 100 TU 100 TU DTIM Integer in unit of BI { 1, 3 } Max SP Length Indicate the maximum number of buffered A-MSDUs, and MMPDUs that AP may deliver per SP { 2, 4, 6, ∞ } AC Access Category All ACs are both delivery and trigger enabled
Traffic model for each apartment Sim Traffic Identifier Source/Sink Traffic Model1 Traffic Model Class Identifier2 Directional3 Number of Traffic Services Assigned to STAs in Sim Population AC D1 AP/STA Buffered Video Streaming BV6 Asymmetric Bi-directional 2/2 VI D2 AP/STA Buffered Video Streaming BV3 Asymmetric Bi-directional 4/4 VI D3 AP/STA FTP FTP Asymmetric Bi-directional 2/2 BE D4 AP/STA HTTP HTTP Asymmetric Bi-directional 4/4 BE D5 AP/STA Gaming GMG Asymmetric Bi-directional 3/3 VI D6 AP/STA VoIP VOIP Symmetric 2/2 VO D7 AP/STA MGMT: Beacon 220 octets long Beacon frame @ 1 Mbps in 2.4 GHz/ @ 6 Mbps in 5 GHz is transmitted every 100 TUs Unidirectional 1/0 VI U1 STA/AP Buffered Streaming BV3 Asymmetric Bi-directional 1/1 VI
Traffic for each BSS Sim Traffic Identifier Source/Sink Traffic Model1 Traffic Class Identifier2 Directional3 Number of Traffic Services Assigned to STAs in Sim Population AC D1 AP/STA Buffered Video Streaming BV6 Asymmetric Bi-directional 12/12 VI D2 AP/STA Buffered Video Streaming BV3 Asymmetric Bi-directional 8/8 VI D3 AP/STA FTP FTP Asymmetric Bi-directional 4/4 BE D4 AP/STA HTTP HTTP Asymmetric Bi-directional 12/12 BE D5 AP/STA Gaming GMG Asymmetric Bi-directional 16/16 VI D6 AP/STA VoIP VOIP Symmetric 12/12 VO D7 AP/STA MGMT: Beacon 280 octets long Beacon frame @ 1 Mbps in 2.4 GHz/ @ 6 Mbps in 5 GHz is transmitted every 100 TUs Unidirectional 1/0 VI U1 STA/AP Buffered Video Streaming BV3 Asymmetric Bi-directional 4/4 VI U2 STA/AP FTP FTP Asymmetric Bi-directional 4/4 BE U3 STA/AP Gaming GMG Asymmetric Bi-directional 16/16 VI U4 STA/AP MGMT: Probe Req TBD Unidirectional All unassociated STAs/0 VI