MAX Per BCC Data Rate Date: Authors: Month Year

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0424r0 Submission March 2012 Ron Porat, Broadcom Downclocking Options for TGaf PHY Date: Authors: Slide 1.
Advertisements

Doc.: IEEE /401r1 Submission May 2012 Mark RISON (CSR)Slide 1 Highest Supported Data Rate Date: Authors:
Doc.: IEEE SubmissionSlide 1 Interleavers for 160MHz Transmission Date: Authors: Mediatek.
Doc.:IEEE /0820r0 Submission July 13, 2010 Sudhir Srinivasa et al.Slide 1 MCS Selection and Padding Equations Date: Authors:
Doc.: IEEE /1289r0 Submission November 2015 Thomas Handte, SonySlide 1 Non-Uniform Constellations for 1024-QAM Date: 2015/11/08 Authors:
1x/2x/4x OFDM Symbol in HE SU PPDU with BCC
VHT Capabilities and Operation elements and VHTC field
1x/2x/4x OFDM Symbol in HE SU PPDU with BCC
Support of 1x/2x/4x OFDM Symbol in HE SU PPDU
China S1G Spectrum Performance Analysis
11ac 80MHz Transmission Flow
ACK Indication and EIFS
Signalling Support for Full Bandwidth MU-MIMO Compressed SIG-B Mode
Relay Flow Control Date: Authors: May 2013 Month Year
SIG Fields Design of Long Preamble
1MHz SIG Field Discussions
Rate 7/8 LDPC Code for 11ay Date: Authors:
Month Year Month Year doc.: IEEE yy/xxxxr0 doc.: IEEE /0135r0
Preamble Parameters Date: Authors: Slide 1.
China S1G Spectrum Performance Analysis
Sounding and P Matrix Proposal
Proposed Correction of LDPC Tone Mapping Equation
VHT Packet Duration Signaling
LDPC for 1024QAM Date: Authors: July 2016
Proposed Specification Framework for TGac – Introductory Comments
MCS table for SC EDMG Date: 2016-November-07 Authors: November 2016
VHT-STF for 11AC Date: Authors: Month Year
MAX Per BCC Data Rate Date: Authors: Month Year
Proposed Scope for Tgac Ad Hoc Groups
CSN & BSS Bridging Date: Authors: Jan 2013
Proposed Specification Framework for TGac – Introductory Comments
Smoothing Bit and Beam-Change Indication Bit for 2MHz Preamble
VHTSIG Considerations
Straw polls and Motions on Spec text for and
Straw polls and Motions on Spec text
Proposed Specification Framework for TGac – Introductory Comments
160 MHz Transmission Flow Date: Authors: September 2010
VHT in Below 6 GHz Frequency Bands
VHT in Below 6 GHz Frequency Bands
MU-MIMO support for Heterogeneous Devices
Data Subcarrier and Interleaving for 120MHz
256 QAM Mapping Date: Authors: Month Year
Single User MCS Proposal
D1.0 PHY Comments Discussion
Straw Polls and Motions on 256 QAM and BW: Optional-Mandatory Features
Bits Consideration for SIGNAL fields
Straw polls and Motions on Spec text for and
D1.0 PHY Comments Discussion
On TX EVM Date: Authors: September 2017 Month Year
11ac 80MHz Transmission Flow
Bits Consideration for SIGNAL fields
Straw polls and Motions on Spec text for and
256 QAM Mapping Date: Authors: Month Year
160 MHz Transmission Flow Date: XX Authors: September 2010
Discussion on Rank Adaptation
Proposed Scope for Tgac Ad Hoc Groups
Below 6GHz 11vht PAR scope and purpose discussion
VHT Capabilities and Operation elements and VHTC field
Capability on Doppler Mode
SIG Fields Design of Long Preamble
Transmit OOB emission Date: Authors: Month Year Month Year
SIG-A Changes for Ranging NDP
NGV PHY Performance Results
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
VHT LO Leakage Requirement
VHT LO Leakage Requirement
VHT LO Leakage Requirement
VHT LO Leakage Requirement
80 MHz Channelization Date: Authors: July 2010 Month Year
Additional SC MCSs in clause 20 (DMG PHY)
Presentation transcript:

MAX Per BCC Data Rate Date: 2010-09-12 Authors: Month Year doc.: IEEE 802.11-yy/xxxxr0 MAX Per BCC Data Rate Date: 2010-09-12 Authors: Slide 1 Jun Zheng, Broadcom John Doe, Some Company

Max Data Rate for Each BCC Encoder Due to the hardware limitations of Viterbi decoder, we need to set a threshold of the maximum data rate for each BCC encoder/decoder pair Propose to use 600Mbps as the maximum per BCC data rate It is a reasonable threshold within the current hardware limit It will not lead to too many BCC encoder/decoder pairs, i.e. only 4 BCC encoders for the support of 160MHz-3streams-256QAM 802.11n had 300 Mbps per BCC encoder, and 600 Mbps per encoder can be achieved in most cases by simply doubling the clock speed which allows us to reuse the 11n viterbi decoder (with minor modifications) Jun Zheng, Broadcom

Max Data Rate for Each BCC Encoder (Cont.) For each MCS rate, the number of BCC encoders is calculated based on SGI (400ns guard interval) E.g. for the case of 80MHz-2streams-mcs7-64QAM-R5/6: 800ns GI frame has PHY rate 585Mbps 400ns GI frame has PHY rate 650 Mbps For both cases, 2 BCC encoders would be used There should be no limit on the number of BCC encoders so that LDPC can be optional for all rates Jun Zheng, Broadcom

Straw Poll Do you support updating the IEEE Specification Framework for TGac to require that: The maximum data rate per BCC encoder be 600Mbps The number of BCC encoders for a particular combination of MCS, Nsts and BW be determined by the short GI data rate and that the same number of encoders be used for the corresponding normal GI rate The number of BCC encoders not be limited? Yes: No: Abs: Jun Zheng, Broadcom