802.11 Ac Basics

Cisco Confidential 2011 Cisco and/or its affiliates. All rights reserved.
1
802.11ac Basics
Speaker Name Jerome Henry
Speaker Title Technical Marketing Engineer
Date Summer 2013
2011 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2
802.11a/g use , BPSK, QPSK, 16-QAM or 64-QAM
64 small waves (called Carriers, or Tones)
No relationship between 64 carriers and 64 in 64-QAM
Some carriers are not used for data:
48 data subcarriers (in green)
4 pilot subcarriers (in red) for synchronization and tracking
12 zero subcarriers (in black) for calibration on sides and
center

Inside each carrier, symbols are separated by
silences (guard intervals), and some of them are
repeated

000 000
000 001
000 011
000 010
001 001 011 001 010 001
001 011 011 011 010 001
001 010 011 010 010 010
001 000 010 000 011 000
100 010
111 000 101 000 100 000 110 000
110 001 111 001 101 001 100 001
100 011 101 011 111 011 110 011
101 010 111 010 110 010
110 100 000 100 001 100 011 100 010 100
010 101 011 101 001 101 000 101
010 111 011 111 001 111 000 111
010 110 011 110 001 110 000 110 110 110 111 110 101 110 100 110
110 111 111 111 101 111 100 111
110 101 111 101 101 101 100 101
111 100 101 100 100 100
64-QAM
110 110
001 101
100 010
110 110
001 101
100 010
Modulation Data Rate per
Carrier (kb/s)
Total Gross Data
Rate (Mb/s)
Repeat
ratio
Total Net Data
Rate (Mb/s)
64-QAM 1125 72 1/3 48
64-QAM 1125 72 1/4 54
802.11n aggregates two carriers to more
than double the speed: 128 subcarriers
14 zero subcarriers (vs. 12) for calibration on sides
and center
6 pilot subcarriers (vs. 4) for synchronization and
tracking
108 data subcarriers (vs. 48)
54 Mb/s to 108+11 = 119 Mb/s
Usable only in the 5GHz band
802.11n also allows several co-existing radios on the same frequency (MIMO)
Up to 4 radios, to receive and / or to send:

abcdef
def
abc
MIMO
AP
Sending side: send more symbols,
in parallel (spatial multiplexing)
abc
abc
abc
MIMO
AP
Sending side: synchronize signals for better resulting
signal at receiving end (Transmit Beamforming, TxBF, ClientLink)
abc
abc
abc
MIMO
AP
Receiving side: synchronize signals for better
signal (Maximal Ration Combining, MRC)
Spatial
Streams
Data rate (20
MHz channel,
800 ns GI)
Data rate (20
MHz channel,
400 ns GI)
Data rate (40
MHz channel,
800 ns GI)
Data rate (40
MHz channel,
400 ns GI)
1 65.5 72.2 135 150
2 130 144.4 270 300
3 195 216.7 405 450
4 260 288.8 540 600
MCS Modulation Ratio 20 MHz channel

40 MHz channel

800 ns GI 400 ns GI 800 ns GI 400 ns GI
0 BPSK 1/2 6.5 7.2 13.5 15
1 QPSK 1/2 13 14.4 27. 30
2 QPSK 3/4 19.5 21.7 40.5 45
3 16-QAM 1/2 26 28.9 54 60
4 16-QAM 3/4 39 43.3 81 90
5 64-QAM 2/3 52 57.8 108 120
6 64-QAM 3/4 58.5 65 121.5 135
7 64-QAM 5/6 65 72.2 135 150
Greenfield header (pure 802.11n, for networks with no 802.11a/b/g stations)
RIFS (Reduced Interframe Space, 2 s space for bursts)
Antenna selection (implement 8 antennas, use 4)
Unequal modulation (e.g. Spatial multiplexing, sending one 64-QAM signal and another
BPSK signal)
LSIG TXOP protection (802.11n stations reserve bandwidth using legacy frame header
space)
Dual CTS protection (AP send to CTS when using Space Time Block Coding, STBC,
which extends the range of the cell: one CTS for non-STBC stations (short range), and
one CTS for STBC stations (longer range))

Increase channel width beyond 40 MHz
Increase number of spatial streams more than 4
Improve the modulation? Is 64-QAM the best we can do?
Better manage the cell
Why would only one device send at a time?
If we can have one device send 3 streams at the same time on the same frequency, why not have 3
devices send 1 stream at the same time on the same frequency instead?
Why would all devices be on the same frequency?
If we can send one 40 MHz signal, why not send two 20 MHz signals instead?

160 MHz-wide channel width
Up to 160 MHz for APs
80 MHz for stations, 160 MHz optional
More spatial streams
Up to 8 spatial streams
8 radio circuits sending or receiving
Better modulation
256-QAM
(8 bits per symbol vs. 6 bits for QAM-64)
Up to 4 times faster
MCS Modulation Ratio 20 MHz channel

40 MHz channel

80 MHz channel 160 MHz channel
800 ns GI 400 ns GI 800 ns GI 400 ns GI 800 ns GI 400 ns GI 800 ns GI 400 ns GI
0 BPSK 1/2 6.5 7.2 13.5 15 29.3 32.5 58.5 65
1 QPSK 1/2 13 14.4 27. 30 58.5 65 117 130
2 QPSK 3/4 19.5 21.7 40.5 45 87.8 97.5 175.5 195
3 16-QAM 1/2 26 28.9 54 60 117 130 234 260
4 16-QAM 3/4 39 43.3 81 90 175.5 195 351 390
5 64-QAM 2/3 52 57.8 108 120 234 260 468 520
6 64-QAM 3/4 58.5 65 121.5 135 263.3 292.5 526.5 585
7 64-QAM 5/6 65 72.2 135 150 292.5 325 585 650
8 256-QAM 3/4 78 86.7 162 180 351 390 702 780
9 256-QAM 5/6 N/A N/A 180 200 390 433.3 780 866.7
8 spatial streams but many (battery-operated) clients will be 1 SS are we going to
waste 7 SS (like we waste 3 SS with 802.11n?)
No! With MU-MIMO, up to 4 clients can receive signals at the same time, on the same
frequency
Each client has a dedicated spatial stream
No collisions anymore
Full-duplex becomes possible
def
abc
MIMO AP
1 2 3 4 5 6 7 8
0
1000
2000
3000
4000
5000
6000
7000
No of Spatial Streams
P
H
Y

L
a
y
e
r

T
h
r
o
u
g
h
p
u
t

(
M
b
p
s
)
802.11ac PHY Rates, MCS9, Short GI

20MHz
40MHz
80MHz
160MHz
Throughput will all depend on stations!
Example best case:
160 MHz-wide channel, 8 antenna AP
with MU-MIMO support
One 4-SS, 160 MHz client, 3.47 Gbps data rate
to this client
One 2-SS, 160 MHz client, 1.73 Gbps data rate
to this client
Two 1-SS, 160 MHz clients, 867 Mbps data rate
to each client
Total cell throughput, 6.93 Gbps!
But in reality, clients are not expected
to support more than 80 MHz
(only the APs will support 160 MHz)
With current WPA2, blocks of 128 bits are encrypted with 128 bit AES/CCMP:
802.11 MAC header CCMP Payload (data) MIC FCS
PN part 1
8 bytes
Reserved Key ID Packet Number - PN part 2
4 bytes
2 bytes 4 bytes 1 byte 1 byte
8 bytes 26 / 30(802.11n) bytes
01011001 0000000 SA Length PN
2 bytes 6 bytes 6 bytes 2 bytes
1. Create a 128 bit Init Block (starting block)
You need to calculate the MIC and encrypt the packet in parallel lets look at the MIC:
2. Encrypt with AES (128 bit key)
= you get a 128 bit encrypted result
3. Apply an XOR with the first 128 bits of payload
Data
16 bytes
AES Encrypted
16 bytes
AES
XOR Result
16 bytes
5. Apply an XOR with the next128 bits of payload
Data
16 bytes
AES Encrypted
16 bytes
AES
XOR Result
16 bytes
6. Repeat 4 and 5 as you go through the frame
XOR is a simple binary operation:
You take each bit of data and encrypted block and
apply the recipe:
0 XOR 0 -> 0
0 XOR 1 -> 1
1 XOR 0 -> 1
1 XOR 1 -> 0
With current WPA2, blocks of 128 bits are encrypted with 128 bit AES/CCMP:
8 bytes 4 bytes 8 bytes 26 / 30(802.11n) bytes
Once you get to the last 128 bits of the payload (with padding if needed):
Data
16 bytes
AES Encrypted
16 bytes
XOR Result
16 bytes
AES Encrypted
16 bytes
AES
AES Encrypted
8 bytes
7. Take the 64 most significant bits:
thats your unencrypted MIC (TBC)
Congratulation, you have your MIC. Now, lets encrypt the payload:
01011001 0000000 SA Length PN
2 bytes 6 bytes 6 bytes 2 bytes
1. Take your 128 bit Init Block (starting block)
= you get a 128 bit encrypted result
3. Apply an XOR with the first 128 bits of payload
= you get your first 128 bit payload chunk
Data
16 bytes
AES Encrypted
16 bytes
AES
XOR Result
16 bytes
4. Increment your PN by +1
6. Apply an XOR with the next 128 bits of payload
Data
16 bytes
AES Encrypted
16 bytes
AES
XOR Result
16 bytes
7. Repeat 4 to 6 as you go through the frame
5. Encrypt this new block with AES
Congratulation, you have your MIC. Now, lets encrypt the payload:
Once you get to the last 128 bits of the payload (with padding if needed):
XOR Result
16 bytes
AES Encrypted
16 bytes
AES
AES Encrypted
8 bytes
1. Increase PN by 1, encrypt the 128 bit Init Block (starting block)
2. XOR with the Unencrypted MIC
3. Keep the most significant 64 bits
4. Congratulations! You have a encrypted
packet with an encrypted MIC
AES Encrypted
8 bytes
AES CCMP uses blocks of 128 bits, with a 128 bit key:
128 bit key is getting a bit light, especially if you want FIPS certification (you will require 256 bit keys at
some point)
Blocks of 128 bits: with 802.11n A-MPDU max length of 65,535 octets, you may need more than 24 580
calculations to encrypt a frame
If your throughput is about 270 Mbps (3SS 450 Mbps), this represents more than 13 million calculations
per second (just to encrypt)
Imagine 6.93 Gbps close to 350 million calculations per second
In their wisdom, the 802.11ac members decided that more efficiency would soon be needed:
A first change is that 802.11ac allows for 256 bit keys, even with WPA2/CCMP and 128-bit blocks
Packet format and process would stay the same, except that MIC would change from 64 bits (8 bytes) to
128 bits (16 bytes)
A second change is that AES with Counter Cipher Mode (CCM) with Block Chaining Message
Authentication Code (CMAC) Protocol (CCMP) is not the only possible mechanism anymore
A new mechanism, AES with GCM with Galois Message Authentication Code (GMAC) Protocol (GCMP)
is allowed
Key is 128 or 256 bits
Block can be 128, 192, 256, 384, 512 or 704 bit long
A great strength of this mechanism is that you can calculate (still using AES) the different elements
needed for the MIC determination in parallel, saving an enormous amount of time
GCMP was recently allowed in 802.11ac, experiments are being made so see how much time is saved
GCMP (with 128 bit blocks and key) was already allowed by 802.11ad
You can process some phases of the encryption/authentication in parallel:
802.11 MAC header GCMP Payload (data) MIC FCS
Data
16 bytes
1. Cut your frames in chunks of 128 bits:
Data
16 bytes
Data
16 bytes

2. Take a number (IV, usually 0), increment +1 so that you have as many IVs as data chunks:
Counter 0 (IV)
16 bytes
Counter 1 (IV)
16 bytes
Counter n
16 bytes

3. Perform Galois Field multiplication on the counter:
GF x GF x GF x
GF result 0
16 bytes
GF result 1
16 bytes
GF result n
16 bytes

WARNING: simplified scheme for educational
purpose
The last phase is serial:
802.11 MAC header GCMP Payload (data) MIC FCS
5. Apply your result to the data chunks:
GF result 0
16 bytes
GF result 1
16 bytes
GF result n
16 bytes

Data
16 bytes
Data
16 bytes
Data
16 bytes

6. Concatenate the results to get your 16 byte MIC:
GHASH 0
16 bytes
GHASH 1
16 bytes
GHASH n
16 bytes

GHASH 0+1
16 bytes

MIC
16 bytes

More streams: its not that easy!
Multiple streams reach multiple receiving circuits
Distinguishing one from the other is difficult
Larger channel is easier than more streams

Throughput
0
20
40
60
80
100
120
140
160
180
200
220
240
0 10 20 30 40 50 60 70 80
Range (m)
O
T
A

T
h
r
o
u
g
h
p
u
t

(
M
b
p
s
)
1x1 - 20 MHz
2x2 - 20 MHz
3x3 - 20 MHz
4x4 - 20 MHz
1x1 - 40 MHz
2x2 - 40 MHz
Here again, not that easy!
Where do I find 160 MHz?
One 80 MHz channel in 2.4GHz
Two 160 MHz channels in 5 GHz (with DFS; one without DFS band)
802.11ac focuses on 5 GHz
Even in 5 GHz, a new protocol
does not make the spectrum
wider
One great advantage of 802.11ac will be to increase the 5 GHz adoption
But multiple 802.11ac cell coexistence will be a challenge
And can you afford 8 radios in your mobile device?

In the US there are currently there are 22/10/5/1 channels with bandwidth 20/40/80/160MHz channels
With opening up of 5.35-5.47GHz & 5.85-5.925GHz, the number of channels increases to 34/16/8/3
If the industry manages to take back the TDWR channels, the number of increases to 37/18/9/4

1
4
4

1
4
0

1
3
6

1
3
2

1
2
8

1
2
4

1
2
0

1
1
6

1
1
2

1
0
8

1
0
4

1
0
0

1
6
5

1
6
1

1
5
7

1
5
3

1
4
9

6
4

6
0

5
6

5
2

4
8

4
4

4
0

3
6

Channel #
20 MHz
40 MHz
80 MHz
160 MHz
UNII-1 UNII-2
UNII-2 Extended UNII-3
5250
MHz
5350
MHz
5470
MHz
5725
MHz
9
6

9
2

8
8

8
4

8
0

7
6

7
2

6
8

1
6
9

1
7
3

1
7
7

1
8
1

5825
MHz
5925
MHz
Available
TDWR channels, not yet available To become available Special OOBE must be met
The number of channels with 20/40/80/160MHz bandwidth in other countries
is currently:
EU: 17/8/4/2
China: 5/2/1/0 about to expand number of channels
India: 13/6/3/1
Japan: 19/9/4/2
Russia: 16/8/4/1
Efforts are underway globally to expand the availability of 5Ghz, including for
use by wide 802.11ac channels
WFA Wave 1 certification includes only a subset of features:
80 MHz is mandatory, 256QAM is optional (but all vendors put it in)
Ability to RX 1/2/3SS is tested
2SS is mandatory for non-battery-powered APs
Only 1SS is mandatory for battery powered APs and clients
For Wave 1, the majority of vendors focus on 80 MHz, 1-3SS and 256QAM
Wave 1 products are based on 11ac D3.0 (May 2012) and started June/July 2013
The WFA brand name is Wi-Fi CERTIFIED ac
Wave 2 should include: 256QAM, 160MHz, 4SS 3.5Gbps PHY, 2.4Gbps MAC
Fort Wave 2, it is expected that 160 MHz devices appear with 1-3SS for low- to high-end
products (data rates of 867-2600 Mbps)
Marketing roadmap for Wave 2 has not yet be approved
In between, 802.11ac draft 5 was recirculated and approved with few comments
Amendment final approval is expected in late 2013

80 MHz, 3 SS => 1.3 Gbps
80 MHz, 2 SS => 866.7 Mbps
80 MHz, 1 SS => 433.3 Mbps
256 QAM is very rewarding,
for marketing
However, noise affects dense signal
(high QAM density) more than signal w/lower density
1.3 Gbps range is likely to be short!

0
45
90
135
180
225
270
315
0
45
90
135
180
225
270
315
QPSK 16-QAM
1000 points mapped,
no noise
0
45
90
135
180
225
270
315
0
45
90
135
180
225
270
315
1000 points
mapped, with noise
Channel sounding for MU
To make efficient use of a channel (and beam form!), stations need to know the channel characteristics they
can send test frames [sounding frames] of known structure, which allows the receiver to understand the channel
specs, and return them to the sender
Industry did not settle on any of the channel sounding mechanisms of 11n, and BF is being done via proprietary
mechanisms
But for MU-MIMO, a unique sounding mechanism is important, and 11ac community agreed on a single
sounding mechanism - Same mechanism is applicable for SU-MIMO
ACK for MU
AP polls each client for ACK. This adds overhead, but is more robust
RTS/CTS for MU
No new RTS/CTS mechanism is added for MU
But the spec allows AP for proprietary mechanisms using conventional RTS/CTS
802.11ac MU MIMO is like 802.11n MIMO, except instead of one client, there are up to four
clients
AP does pre-coding for all the clients within the MU group simultaneously
In MU precoding, when AP beamforms space-time streams to one client, it simultaneously null-
steers those space-time streams to the rest.
All users MPDUs are padded to the same number of OFDM symbols
MU-MIMO is technically risky and challenging:
Needs precise channel estimation (CSI) to maintain deep nulls
Precise channel estimation adds overhead
Rate adaptation is more difficult
Throughput benefits are sensitive to MU grouping
WFA Wave 2 certification:
MU-MIMO
Null-steering:To send data to user 1, the AP forms a strong beam
toward user 1, shown as the top-right lobe of the blue curve. At the
same time the AP minimizes the energy for user 1 in the direction
of user 2 and user 3. This is called "null steering" and is shown as
the blue notches. Same logic applies to red and yellow beams.
One issue of 802.11n is 40 MHz coexistence with 20 MHz channels
B sends on Ch 36 (because it senses 802.11a AP on Ch 40)
802.11an AP does CCA on 36,40, hears nothing, transmits
40 MHz signal collides at B

36,40 40 B
Collision
on 40
802.11n 802.11a 802.11n
CCA: 40 is busy
-> use 36 only
CCA: 36 and 40 clear
-> use 36 and 40
36
36+40
This issue could be a lot worse for 802.11ac:
802.11ac can use 20 MHz, 40 MHz (20 MHz primary/secondary), 80 MHz (40 MHz primary/secondary)

36
Primary 20
40 44 48
36
Primary 20
40 44 48
36
Primary 20
40 44 48
36
Primary 20
40 44 48
Free?
Secondary 20
Free?
Secondary 40
Secondary 20
Secondary 20
Primary 40
Primary 40
This issue could be a lot worse for 802.11ac:
If secondary20 is busy, transmitter cannot extend to secondary40
OBSS (802.11n or 802.11ac) with primary on local AP secondary would cause both APs to block each
other
Choice of primary channel is critical for 802.11ac

Best configuration: both primary 20s aligned
Second best: primary 20s far apart (e.g. 36 and 48)

36
Primary 20
40 44 48
Secondary 40 Secondary 20
36
Secondary 20
40 44 48
Secondary 40 Primary 20
Block Block Wasted
Block
36
With wide bandwidth options, 802.11ac has made RTS/CTS procedures OBSS friendly
Based on a Cisco proposal, 802.11ac added a bandwidth reservation mechanism to legacy
RTS/CTS frames
Legacy devices recognize NAV and defer
Yet, three bits are hidden in scrambling sequence of the legacy PPDU that indicates desired BW that
sender wishes to send PPDU with
RTS sent on primary channel is duplicated on secondary channels, so that nearby stations
belonging to OBSS know about upcoming transmission
The responder, responds with CTS on primary channel, and it duplicates the CTS frame on
some or all of the secondary channels
Depending on capabilities, bandwidth indication could be static or dynamic, where the RTS-
sender could narrow the bandwidth to adapt to the condition on the other side
Interference at the responder side

Initiator sends RTS on channels that its senses are free
Subsequent exchange depend on the capabilities of both sides
Dynamic bandwidth reservation:
Responder sends CTS only on channels that it sense are free. Initiator transmits data only over
channels indicated free by CTS response
Static bandwidth reservation:
If the initiator has static capability, the responder sends CTS only if all the requested channels are free,
otherwise sends no CTS
RTS
CTS
CTS
Data transmission
Data transmission
RTS is in 20MHz 11a
format, but indicates: (1)
80MHz BW, (2) initiator is
capable of dynamic BW
CTS is in 20MHz 11a format, but indicates 40MHz
BW
Example of Dynamic
Bandwidth Reservation
RTS with BW signaling is
optional
CTS with BW signaling in
response to RTS with BW
signaling is a mandatory
test

RTS
RTS
RTS
There has been debates on how to reduce processing in a station for the frames that are not
addressed to the station, especially with large frames
Three fields in 11ac physical header (PLCP) allow for power saving:
Partial Association ID (PAID): A station receiving a unicast frame (or rather PPDU) with PAID not
matching its own is allowed to stop receiver processing
Group ID (GID): AP announces ahead of time what stations belong to a MU GID. In a MU PPDU,
those clients that do not belong to the GID in PLCP may drop the MU PPDU.
TXOP PS: AP indicates to clients if there are no more MPDUs for them in the remaining of a TXOP
and those clients may go to power save. This has some overhead for AP, but AP can disallow TXOP
PS entirely.
TXOP PS is not a popular features for AP vendors and they are not tested in WFA Wave 1
certificate.

In 11ac, all PPDUs are in form of AMPDU
Very large payloads are possible in 11ac (up to 1,048,575 octets!),
The goal is to maintain efficiency: same amount of bytes is transmitted in less time, which increases the relative
percentage of IFS and header overhead
At the same time, longer frames means longer header, if signaling the length of the PSDU in bytes
Alternative is to signal the number of OFDM symbols, which is an AMPDU format
But AMPDU with single MPDU (and necessary padding if needed) is allowed

AMPDU aggregation is a mandatory test
RX AMPDU of AMSDU is an optional test
802.11ac
ACK
802.11ac
Header
Packet
802.11ac
Header
Packet
802.11ac
Header
Packet
802.11n
ACK
802.11n
Header
Packet Packet Packet
802.11n
Header
Packet
802.11n
ACK
Standard frame A-MSDU
A-MPDU
MPDU
MSDU
Clients are already out there, all supporting 80 Mhz (and 256-QAM)
Broadcom (4335:1SS, 256-QAM, 433.3 Mbps and 4352:2 SS, 256-QAM, 867 Mbps)
Marvell (Avastar 88W8897: 2 SS, 256-QAM, 867 Mbps)
Qualcomm (WCM3680: 1 SS, 256-QAM, 433.3 Mbps, QCA9862: 2 SS, 256-QAM, 867 Mbps)
Mediatek (MT7610 and MT7650: 1 SS, 256-QAM, 433.3Mbps)
Redpine (RS9117: 1 SS, 256-QAM, 433.3Mbps)
Intel (Wilkins Peak 2: 2 SS, 256-QAM, 867 Mbps
APs are coming out too, including the 802.11ac module for the 3600 (3 SS, 80 MHz, 256 QAM, 1.3 Gbps)
First issues might be collisions with legacy systems, I do not get the speed written on the box, and my non-
certified client cannot communicate with your AP
Because Wave 1
Su = single User
MU = Multiple User
Too many MCS/SS to list them all!
802.11ac adopts a coding technique :
Bits 0-1 represent 1 SS
Bits 2-3 represent 2 SS
Etc, bits 14-15 represent 8 SS
Then, for each group:
0 indicates support for VHT-MCS 0-7 for n spatial streams
1 indicates support for VHT-MCS 0-8 for n spatial streams
2 (10) indicates support for VHT-MCS 0-9 for n spatial streams
3 (11) indicates that n spatial streams is not supported

No GCMP in wave 1
Q2 12
Chip vendor
Plug-fests
Begin
Feb 12
802.11ac
Draft 2
Approved
Q4 13
802.11ac
IEEE
Ratification
May 12
802.11ac
Draft 3
Q1 13
802.11ac
IEEE
Final Letter Ballot/
First sponsor ballot
Cisco Confidential For NDA use only, not for further disclosure or distribution
Q1 14
Estimated
Wave 2
industry
Certification
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2012 2013 2014
Q1 13
Wave 1
industry
Certification
Cisco Confidential For NDA use only, not for further disclosure or distribution
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2012 2013 2014
1
st
Gen .11ac
Smartphones
Tablets
(1x1, 2x2)
Broader
.11ac client
adoption &
proliferation
Consumer
Class APs
Linksys,
NetGear,
D-Link

AP3600
802.11ac
Wave 1
Module
Q1 13
Estimated
Wave 1
industry
Certification
Mobile chips will be optimized for lower power consumption to allow
5GHz/11ac support
Post-iPhone 5 and other smartphones in CY13 will likely be 11ac capable
HTC already has a model available
Higher powered Tablets will be 11ac enabled in CY13
Thank you.

802.11 Ac Basics

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

802.11 Ac Basics

Diunggah oleh

Hak Cipta:

Format Tersedia

Cisco Confidential 2011 Cisco and/or its affiliates. All rights reserved.

Anda mungkin juga menyukai