Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 11-13/1411r0 Submission Nov. 2013 Minho Cheong (ETRI)Slide 1 From PAR to Functional Requirements of HEW Date: 2013-11-13 Authors: NameAffiliationsAddressPhoneemail.

Similar presentations


Presentation on theme: "Doc.: IEEE 11-13/1411r0 Submission Nov. 2013 Minho Cheong (ETRI)Slide 1 From PAR to Functional Requirements of HEW Date: 2013-11-13 Authors: NameAffiliationsAddressPhoneemail."— Presentation transcript:

1 doc.: IEEE 11-13/1411r0 Submission Nov. 2013 Minho Cheong (ETRI)Slide 1 From PAR to Functional Requirements of HEW Date: 2013-11-13 Authors: NameAffiliationsAddressPhoneemail Minho CheongETRI161 Gajeong-dong, Yuseong-Gu, Daejoen, Korea +82 42 860 5635minho@etri.re.kr Jae Seung LeeETRI161 Gajeong-dong, Yuseong-Gu, Daejoen, Korea +82 42 860 1326jasonlee@etri.re.kr Hyoung Jin KwonETRI161 Gajeong-dong, Yuseong-Gu, Daejoen, Korea +82 42 860 1698kwonjin@etri.re.kr Sok-Kyu LeeETRI161 Gajeong-dong, Yuseong-Gu, Daejoen, Korea +82 42 860 5919sk-lee@etri.re.kr

2 doc.: IEEE 11-13/1411r0 Submission Abstract This presentation gives set of issues on how to evolve our consensus from PAR to functional requirements of HEW Nov. 2013 Slide 2Minho Cheong (ETRI)

3 doc.: IEEE 11-13/1411r0 Submission PAR What it is –Specify the scope & purpose of the task group activity When to do –As an outcome of the study group to prepare the task group activity itself What it has –Scope of proposed project –Purpose of proposed project –Additional explanatory notes Characteristics –Sometimes, it admits relative numbers or qualitative description –It can have some more contents in its explanatory notes if they are helpful for guidance Nov. 2013 Slide 3Minho Cheong (ETRI)

4 doc.: IEEE 11-13/1411r0 Submission Functional Requirements What it is –Specify the basic core of mandatory features (derived from PAR) When to do –As an outcome of the earlier stage of the task group to prepare draft description (or spec. framework document) What it has –Requirements for system performance –Requirements for user experience –Requirements for backward compatibility & coexistence –Compliance to PAR Characteristics –Should be quantitative with absolute numbers –Having more detail compared to the PAR Nov. 2013 Slide 4Minho Cheong (ETRI)

5 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11n (PAR) 12. Scope of Proposed Project: –The scope of this project is to define an amendment that shall define standardized modifications to both the 802.11 physical layers (PHY) and the 802.11 Medium Access Control Layer (MAC) so that modes of operation can be enabled that are capable of much higher throughputs, with a maximum throughput of at least 100Mbps, as measured at the MAC data service access point (SAP). 13. Purpose of Proposed Project: –The purpose of the project is to improve the 802.11 wireless local area network (LAN) user experience by providing significantly higher throughput for current applications and to enable new applications and market segments. Slide 5 September 2013 Minho Cheong et. al, ETRI

6 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11n (PAR) Additional Explanatory Notes: –The scope of the MAC and PHY enhancements assume a baseline specification defined by 802.11 and its amendments and anticipated amendments a, b, d, e, g, h, i and j. The enhancements shall be to support higher throughput. The amendment shall not redefine mechanisms in the baseline that do not pertain to higher throughput. –Some of the modes of operation defined in the HT amendment shall be backwards compatible and interoperable with 802.11a and/or 802.11g. –Existing 802.11 standards are typically designated by their peak physical data rates. For example, 802.11a has a peak data rate of 54Mbps. This amendment has chosen to use a performance metric of throughput measured at the MAC data SAP. This amendment seeks to improve the peak throughput to at least 100Mbps, measured at the MAC data SAP. Depending on the scenario, this represents an improvement of at least 4 times the throughput obtainable using existing 802.11 systems. –In order to make efficient use of scarce spectral resources in unlicensed bands, the highest throughput mode defined by the HT amendment shall achieve a spectral efficiency of at least 3 bits per second per Hertz for the PSDU. Slide 6 September 2013 Minho Cheong et. al, ETRI

7 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11n (PAR) Additional Explanatory Notes: In the process of formulating this PAR, it was found that there are multiple user scenarios. Accordingly, the task group will undertake the following steps: –1. Identify and define usage models, channel models and related MAC and application assumptions. Initial usage models envisioned include hot-spot, enterprise and residential; others may be included. –2. Identify and define evaluation metrics that characterize the important aspects of a particular usage model. The evaluation metrics may include but are not limited to the items listed in Table 1, provided as an illustration of the format. –3. Develop a technical requirement specification. –4. Define a process for evaluations. The impact of an HT device on the operation of a legacy network shall be comparable to that of any other legacy device identified in the baseline defined above. Slide 7 September 2013 Minho Cheong et. al, ETRI

8 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11n (Functional Requirements) NumberNameRequirement 1Single Link HT rate supported Demonstrate at least one set of conditions under which 100 Mbps at the top of the MAC SAP can be achieved. Provide all relevant information to document this. 2HT rate supported in 20MHz channel Proposal supports at least one mode of operation that supports 100Mbps throughput at the top of the MAC SAP in a 20MHz channel. Provide all relevant information to document this. 3Supports 5GHz bandsProtocol supports 5GHz bands (including those supported by.11a) 4.11a backwards compatibility Some of the modes of operation defined in the proposal shall be backwards compatible with 802.11a. 5.11g backwards compatibility If it supports 2.4 GHz operation, some of the modes of operation defined in the proposal shall be backwards compatible with 802.11g. Nov. 2013 Slide 8Minho Cheong (ETRI)

9 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11n (Functional Requirements) Nov. 2013 Slide 9Minho Cheong (ETRI) 6Control of support for legacy STA from.11n AP A.11n AP can be configured to reject or accept associations from legacy STA because they are legacy STA. 7.11e QoS supportThe proposal shall permit implementation of the 802.11e amendment within a.11n STA 8Spectral EfficiencyThe highest throughput mode of the proposal shall achieve a spectral efficiency of at least 3 bps/Hz for the PSDU 9Compliance to PARThe proposal complies with all the mandatory requirements of the PAR [5] and 5 Criteria [6] 10Existence of single spatial stream transmission modes Proposal shall define single spatial stream transmission modes that provide at least one mode of operation that supports a maximum throughput of at least 50 Mbps in a 20MHz channel as measured at the MAC data SAP. 11Interoperability with single spatial stream non AP stations A.11n AP or STA shall interoperate with a single spatial stream entity defined as a non- AP STA that complies with the.11n proposal with the exception of only supporting single spatial stream transmission modes as required by FR10. NumberNameRequirement

10 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11n (PAR vs. FR) Nov. 2013 Slide 10Minho Cheong (ETRI) RequirementsPAR (gray: explanatory notes) FRNote Max. per-user throughput> 100Mbps at MAC SAP > 4 times compared to before > 100Mbps at MAC SAP Max. per-user throughput using 20MHz channel > 100Mbps at MAC SAPMore strict requirement than the above Band5GHz (as well as 2.4GHz) Backward compatibility11g/11a Interoperability11g/11a11g/11a (11n AP can control) QoS11e support Peak spectral efficiency> 3bps/Hz PHY rate Single SS mode (peak rate) > 50Mbps at MAC SAPTo allow SISO mode Single SS mode (interoperability) support Compliance to PARNeedless to sayYES

11 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ah (PAR) 5.2 Scope of Proposed Standard: –This amendment defines an Orthogonal Frequency Division Multiplexing (OFDM) Physical layer (PHY) operating in the license-exempt bands below 1 GHz, e.g., 868-868.6 MHz (Europe), 950 MHz -958 MHz (Japan), 314-316 MHz, 430-434 MHz, 470-510 MHz, and 779-787 MHz (China), 917 – 923.5 MHz (Korea) and 902-928 MHz (USA), and enhancements to the IEEE 802.11 Medium Access Control (MAC) to support this PHY, and provides mechanisms that enable coexistence with other systems in the bands including IEEE 802.15.4 and IEEE P802.15.4g. The data rates defined in this amendment optimize the rate vs. range performance of the specific channelization in a given band. –This amendment also adds support for: transmission range up to 1 km data rates > 100 kbit/s –while maintaining the 802.11 WLAN user experience for fixed, outdoor, point to multi point applications. Slide 11 Nov. 2013 Minho Cheong (ETRI)

12 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ah (PAR) 5.4 Purpose of Proposed Standard: –The purpose of this amendment defines operation of license-exempt 802.11 wireless networks in frequency bands below 1 GHz excluding the TV White Space bands. Slide 12 Nov. 2013 Minho Cheong (ETRI)

13 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ah (PAR) 8.1 Additional Explanatory Notes: (Item Number and Explanation) –None Slide 13 Nov. 2013 Minho Cheong (ETRI)

14 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ah (Functional Requirements) 2.1 System Performance 2.1.1 Supporting band TGah R1 – The TGah amendment shall describe operation in the license-exempt band below 1 GHz excluding the TV White Space bands. Example operating bands could include one or more of the following: 863-868.6 MHz (Europe), 915.9 -928.1 MHz (Japan), 755-787 MHz (China), 917- 923.5 MHz (Korea), 866-869 MHz, 920-925 MHz (Singapore) and 902-928 MHz (U.S.). 2.1.2 Coverage and data rate TGah R2 – The TGah amendment shall support mode of operation in which PHY data rate at least 100 Kbps is provided with coverage of 1km under regulatory constraints. TGah R3 – The TGah amendment shall provide at least a mode of operation capable of achieving a maximum aggregate Multi-Station data rate of 20Mbps as measured at the PHY data service access point (SAP) in S1G band. Nov. 2013 Slide 14Minho Cheong (ETRI)

15 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ah (Functional Requirements) 2.1.3 OFDM PHY modulation TGah R4 – The TGah amendment shall use an Orthogonal Frequency Division Multiplexing (OFDM) PHY modulation. 2.1.4 Number of associations TGah R5 – The TGah amendment shall support a mode of operation that supports the number of associations beyond 2007 for outdoor applications. 2.2 Mainintaining the 802.11 User Experience TGah R6 – The TGah amendment shall maintain the network architecture of the 802.11 system for fixed, outdoor, point-to-multi-point applications and support compability to 802.11 management plane defined in the existing 802.11 standard and its amendments. Nov. 2013 Slide 15Minho Cheong (ETRI)

16 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ah (Functional Requirements) 2.3 Coexistence with 802.15.4 and 802.15.4g devices TGah R7 – The TGah amendment shall provide a mechanism to enable coexistence with other systems in the bands including 802.15.4 and 802.15.4g. 2.4 Enhanced Power Saving TGah R8 – The TGah amendment shall provide an enhanced power saving mechanism to support battery-powered operation with long replacement cycle. 2.5 Compliance to PAR TGah R9 - The proposal complies with the PAR and 5 Criteria. Nov. 2013 Slide 16Minho Cheong (ETRI)

17 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ah (PAR vs. FR) Nov. 2013 Slide 17Minho Cheong (ETRI) RequirementsPAR (gray: explanatory notes) FRNote BandBelow 1GHz excluding TVWS (enumerating some countries) Below 1GHz excluding TVWS (enumerating some countries) Coexistence802.15.4 & 802.15.4g Data rate> 100kbps>100kbps (PHY rate)To differentiate from 802.15.4g CoverageUp to 1kmUp to 1km (under regulations) Btw. rate & coverageShall optimizeShall support the above two requirements at the same time Maximum throughput of high data rate mode > 20Mbps (aggregated on multi- STAs at PHY SAP) To allow high data rate offloading mode ModulationOFDM Number of associations> 2007 (for outdoor)To cover sensors User experienceMaintain 802.11 user experience Power savingShall support enhanced one Compliance to PARNeedless to sayYES

18 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ac (PAR) 5.2 Scope of Proposed Standard: –This amendment defines standardized modifications to both the 802.11 physical layers (PHY) and the 802.11 Medium Access Control Layer (MAC) that enable modes of operation capable of supporting: A maximum multi-station (STA) throughput (measured at the MAC data service access point), of at least 1 Gbps and a maximum single link throughput (measured at the MAC data service access point), of at least 500 Mbps. –Below 6 GHz carrier frequency operation excluding 2.4 GHz operation while ensuring backward compatibility and coexistence with legacy IEEE802.11 devices in the 5 GHz unlicensed band. Slide 18 Nov. 2013 Minho Cheong (ETRI)

19 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ac (PAR) 5.4 Purpose of Proposed Standard: –The purpose of the amendment is to improve the 802.11 wireless local area network (LAN) user experience by providing significantly higher basic service set (BSS) throughput for existing WLAN application areas and to enable new market segments for operation below 6 GHz including distribution of multiple multimedia/data streams. Slide 19 Nov. 2013 Minho Cheong (ETRI)

20 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ac (PAR) 8.1 Additional Explanatory Notes: (Item Number and Explanation) –5.2) The project may include the capability to handle multiple simultaneous communications. The multi-STA throughput is defined as the sum of the MAC SAP throughputs across all active transmissions within a set of STAs. The 1 Gbps maximum multi-STA throughput may be achieved when considering multiple simultaneously actively- communicating STAs, e.g., a BSS with 1 access point (AP) and 3 or more STAs. Though the primary metric used in the scope of the project deals with MAC SAP throughput, the intent is to provide enhancements over IEEE802.11n on the following inter-dependent performance indicators: throughput at the MAC data SAP, range of operation, aggregate network capacity (spectrum efficiency), power consumption (peak and average). 1.1) This is an amendment to the then current revision of the IEEE standard 802.11 Slide 20 Nov. 2013 Minho Cheong (ETRI)

21 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ac (Functional Requirements) 2.1 System Performance 2.1.1 Multi-STA throughput measured at the MAC SAP to be at least 1 Gbps. TGac R1 – The TGac amendment shall provide at least a mode of operation capable of achieving a maximum Multi-Station aggregate throughput of more than 1 Gbps as measured at the MAC data service access point (SAP), utilizing no more than 80 MHz of channel bandwidth in 5 GHz band. 2.1.2 Single-STA throughput measured at the MAC SAP to be at least 500 Mbps. TGac R2 – The TGac amendment shall provide at least a mode of operation capable of achieving a maximum Single-Station throughput of more than 500 Mbps as measured at the MAC data service access point (SAP), utilizing no more than 80 MHz of channel bandwidth in 5GHz band. Nov. 2013 Slide 21Minho Cheong (ETRI)

22 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ac (Functional Requirements) 2.2 Backward Compatibility with 802.11a/n devices operating in 5 GHz Refer to the IEEE Std. 802.15.2-2003, section 3.1 for the definitions of backward compatible. TGac R3- The TGac admendment shall provide backward compatibility with IEEE802.11a devices operating in the 5 GHz frequency band. TGac R4- The TGac admendment shall provide backward compatibility with IEEE802.11n devices operating in the 5 GHz frequency band. Nov. 2013 Slide 22Minho Cheong (ETRI)

23 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ac (Functional Requirements) 2.3 Coexistence with 802.11a/n devices operating in 5 GHz Refer to the IEEE Std. 802.15.2-2003, section 3.1 for the definitions of coexistence. TGac R5 – The TGac amendment shall provide mechanisms that ensure coexistence between TGac and legacy IEEE802.11a/n devices. 2.4 Compliance to PAR TGac R6 - The proposal complies with the PAR and 5 Criteria. Nov. 2013 Slide 23Minho Cheong (ETRI)

24 doc.: IEEE 11-13/1411r0 Submission e.g., 802.11ac (PAR vs. FR) Nov. 2013 Slide 24Minho Cheong (ETRI) RequirementsPAR (gray: explanatory notes) FRNote Maximum multi-STA throughput > 1Gbps at MAC SAP (utilizing no more than 80MHz) Set minimum BW Maximum single-link throughput > 500Mbps at MAC SAP (utilizing no more than 80MHz) Set minimum BW Throughput (general)Enhancement over 802.11nNeedless to say Band< 6GHz excluding 2.4GHz5GHz band Backward compatibilityLegacy 802.11 in 5GHz band802.11a/11n in 5GHz band CoexistenceLegacy 802.11 in 5GHz band802.11a/11n in 5GHz band Example of technologyMultiple simultaneous comm.Hint on MU-MIMO Example of scenarioBSS (1 AP & 3 or more STAs)At least 3 STA’s Range of operationEnhancement over 802.11nDifficult to achieve Aggregate network capacity (spectrum efficiency) Enhancement over 802.11nDifficult to quantify Power consumption (peak & average) Enhancement over 802.11nDifficult to quantify Compliance to PARNeedless to sayYES

25 doc.: IEEE 11-13/1411r0 Submission Observations from History PAR –Try to give a number on the most important metric (if possible) –Admit relative numbers or qualitative description (if inevitable) –Try some technical examples with very comprehensive expressions (if needed in the explanatory notes) Functional Requirements –Strongly prefer numbers (especially, absolute numbers) –Numbers shall be easily measurable in reality –Shall not give any ambiguity when being read –Try to specify the coupled relation (if exists between key metrics) Nov. 2013 Slide 25Minho Cheong (ETRI)

26 doc.: IEEE 11-13/1411r0 Submission How to Move Forward in HEW Nov. 2013 Slide 26Minho Cheong (ETRI) RequirementsPAR Issues now (gray: explanatory notes) FRNote Per-STA throughput (average or statistics) Qualitative or Quantitative? (significant increase or X times?) Absolute numbers for average Absolute numbers for statistics FR may need a detailed representative scenarios Area throughputQualitative or Quantitative? (significant increase or X times?) Absolute numbers for average Absolute numbers for statistics Only per-STA throughput or area throughput as well? User experienceQualitative or Quantitative? Need to enumerate more metrics? Absolute numbers for average Band2.4GHz and 5GHz band Backward compatibilityLegacy devices in 2.4 & 5GHz (allow exception or not?) TBD CoexistenceLegacy devices in 2.4 & 5GHz (allow exception or not?) TBD Example of problemsRe-visiting here or not?NONE Example of technologyMultiple simultaneous comm. in several dimensions? NONE Example of scenarioHow detailed ones we need?NONE Range of operationQualitative or Quantitative? (including outdoor or up to X m?) TBD Power consumptionQualitative or Quantitative?TBD Compliance to PARNeedless to sayYES

27 doc.: IEEE 11-13/1411r0 Submission How to Move Forward in HEW Crucial issue –Qualitative PAR? because difficult to define, measure and agree –or Quantitative PAR? for more concrete impression to the market Schedule issue –History of VHT/802.11ac May 2008: PAR text agreed in the SG Nov. 2008: TG started (6 months gap) –If we really consider the TG start scheduled in July 2014 January 2014 (or March 2014) will be the chance to get consensus We need a good procedure to get consensus or delaying the TG switch Nov. 2013 Slide 27Minho Cheong (ETRI)

28 doc.: IEEE 11-13/1411r0 Submission How to Move Forward in HEW Stages to go (all on consensus) from PAR to FR –Stage 0: Current status (debating over the PAR) –Stage 1: Having the PAR –Stage 2: quite simplified simulation check to get relative numbers Choose one (simple) representative scenario to check Check simulations results with the 802.11ac technology Try to get consensus on just initial set of HEW technology for trial Check simulation results with that technology & get relative numbers –Stage 3: Less simplified simulation check to get absolute numbers Use a set of simulation scenarios defined in the official doc. (Try to get consensus on just initial set of HEW technology for trial) Check simulation results with that technology & get absolute numbers –Stage 4: Functional Requirements doc. with absolute numbers Nov. 2013 Slide 28Minho Cheong (ETRI)

29 doc.: IEEE 11-13/1411r0 Submission How to Move Forward in HEW If we want the Qualitative PAR during the SG, –Stage 0 : Current status (Nov. 2013) –Stage 1 : Having the PAR (March 2014) –Stage 3 : Less simplified check for absolute numbers –Stage 4 : FR with absolute numbers (within year 2014?) If we want the Quantitative PAR during the SG, –Stage 0 : Current status (Nov. 2013) –Stage 2 : Quite simplified check for relative numbers –Stage 1 : Having the PAR (March 2014) –Stage 3 : Less simplified check for absolute numbers –Stage 4 : FR with absolute numbers (within year 2014?) Nov. 2013 Slide 29Minho Cheong (ETRI)


Download ppt "Doc.: IEEE 11-13/1411r0 Submission Nov. 2013 Minho Cheong (ETRI)Slide 1 From PAR to Functional Requirements of HEW Date: 2013-11-13 Authors: NameAffiliationsAddressPhoneemail."

Similar presentations


Ads by Google