EXHIBIT L

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 1 of 860 PageID #:

3245
1

Exhibit A-30

Invalidity Claim Chart for U.S. Patent No. 7,924,802 vs. IEEE 802.11n Draft 2.0

IEEE 802.11n Draft 2.0 (“802.11n D2.0”) was completed in February 2007 and published in March 2007. 802.11n D2.0 anticipates 

asserted claims 1–4, 6–10, 13, 14, 17, and 21–24 of U.S. Patent No. 7,924,802 (“the ’802 Patent”) under 35 U.S.C. § 102. 802.11n 

D2.0 also renders obvious asserted claims 1–4, 6–10, 13, 14, 17, and 21–24 of the ’802 Patent under 35 U.S.C. § 103, alone based on 

the state of the art and/or in combination with one or more other references identified in Exs. A-1–A-31, Cover Pleading, and First 

Supplemental Ex. A-Obviousness Chart.

1

 

To the extent Plaintiff alleges that 802.11n D2.0 does not disclose any particular limitation of the asserted claims in the ’802 Patent, 

either expressly or inherently, it would have been obvious to a person of ordinary skill in the art as of the priority date o f the ’802

Patent to modify 802.11n D2.0 and/or to combine the teachings of 802.11n D2.0 with other prior art references, including but not 

limited to the present prior art references found in Exs. A-1–A-31, Cover Pleading, First Supplemental Ex. A-Obviousness Chart, and 

the relevant section of charts for other prior art for the ’802 Patent in a manner that would render the asserted claims of these patents 

invalid as obvious.

With respect to the obviousness of the asserted claims of the ’802 Patent under 35 U.S.C. § 103, one or more of the principles 

enumerated by the United States Supreme Court in KSR v. Teleflex, 550 U.S. 398 (2007) apply, including: (a) combining various 

claimed elements known in the prior art according to known methods to yield a predictable result; and/or (b) making a simple 

substitution of one or more known elements for another to obtain a predictable result; and/or (c) using a known technique to improve a 

similar device or method in the same way; and/or (d) applying a known technique to a known device or method ready for 

improvement to yield a predictable result; and/or (e) choosing from a finite number of identified, predictable solutions with a 

reasonable expectation of success or, in other words, the solution was one which was “obvious to try” ; and/or (f) a known work in one 

field of endeavor prompting variations of it for use either in the same field or a different field based on given design ince ntives or 

other market forces in which the variations were predictable to one of ordinary skill in the art; and/or (g) a teaching, suggestion, or 

motivation in the prior art that would have led one of ordinary skill in the art to modify the prior art reference or to comb ine the 

1

 Samsung is investigating this prior art and has not yet completed discovery from third parties, who may have relevant information 

concerning the prior art, and therefore, Samsung reserves the right to supplement this chart after additional discovery is received. To 

the extent that any of the prior art discloses the same or similar functionality or feature(s) of any of the accused products, Samsung

reserves the right to argue that said feature or functionality does not practice any limitation of any of the asserted claims, and to argue, 

in the alternative, that if said feature or functionality is found to practice any limitation of any of the asserted claims in the ’802 Patent, 

then the prior art reference teaches the limitation and that the claim is not patentable. 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 2 of 860 PageID #:

3246
2

teachings of various prior art references to arrive at the claimed invention. It therefore would have been obvious to one of ordinary 

skill in the art to combine the disclosures of these references in accordance with the principles and rationales set forth ab ove. 

The citations to portions of any reference in this chart are exemplary only. For example, a citation that refers to or discusses a figure or 

figure item should be understood to also incorporate by reference that figure and any additional descriptions of that figure as if set 

forth fully therein. Samsung reserves the right to rely on the entirety of the references cited in this chart to show that the asserted 

claims of the ’802 Patent are invalid. Citations presented for one claim limitation are expressly incorporated by reference into all 

other limitations for that claim as well as all limitations of all claims on which that claim depends. Samsung also reserves the right to 

rely on additional citations or sources of evidence that also may be applicable, or that may become applicable in light of cl aim 

construction, changes in Plaintiff’s infringement contentions, and/or information obtained during discovery as the case progresses. 

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[1.1] A method of 

transmitting information in a 

wireless communication 

channel comprising:

To the extent the preamble is limiting, 802.11n D2.0 discloses “A method of transmitting information 

in a wireless communication channel comprising.” See, e.g.: 

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 3 of 860 PageID #:

3247
3

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 4 of 860 PageID #:

3248
4

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[1.2] transmitting first 

information across a first 

frequency range using a 

wireless transmitter, the first 

frequency range having a first 

center frequency, a first 

highest frequency, and a first 

lowest frequency; and

802.11n D2.0 discloses “transmitting first information across a first frequency range using a wireless 

transmitter, the first frequency range having a first center frequency, a first highest frequency, and a 

first lowest frequency.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is s et to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 5 of 860 PageID #:

3249
5

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 6 of 860 PageID #:

3250
6

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a resp onse that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halve s of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 7 of 860 PageID #:

3251
7

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 8 of 860 PageID #:

3252
8

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 9 of 860 PageID #:

3253
9

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 10 of 860 PageID #:

3254
10

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 11 of 860 PageID #:

3255
11

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 12 of 860 PageID #:

3256
12

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 13 of 860 PageID #:

3257
13

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 14 of 860 PageID #:

3258
14

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 15 of 860 PageID #:

3259
15

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 16 of 860 PageID #:

3260
16

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 17 of 860 PageID #:

3261
17

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 18 of 860 PageID #:

3262
18

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 19 of 860 PageID #:

3263
19

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 20 of 860 PageID #:

3264
20

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 21 of 860 PageID #:

3265
21

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 22 of 860 PageID #:

3266
22

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 23 of 860 PageID #:

3267
23

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 24 of 860 PageID #:

3268
24

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 25 of 860 PageID #:

3269
25

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 26 of 860 PageID #:

3270
26

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 27 of 860 PageID #:

3271
27

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[1.3] simultaneously 

transmitting second 

information across a second 

frequency range using the 

same wireless transmitter, the 

second frequency range 

having a second center 

frequency greater than the 

802.11n D2.0 discloses “simultaneously transmitting second information across a second frequency 

range using the same wireless transmitter, the second frequency range having a second center 

frequency greater than the first center frequency, a second highest frequency, and a second lowest 

frequency.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 28 of 860 PageID #:

3272
28

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

first center frequency, a 

second highest frequency, and 

a second lowest frequency.

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, th ere are no non-HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 29 of 860 PageID #:

3273
29

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 30 of 860 PageID #:

3274
30

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 31 of 860 PageID #:

3275
31

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 32 of 860 PageID #:

3276
32

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 33 of 860 PageID #:

3277
33

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 34 of 860 PageID #:

3278
34

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both chan nels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 35 of 860 PageID #:

3279
35

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 36 of 860 PageID #:

3280
36

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 37 of 860 PageID #:

3281
37

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 38 of 860 PageID #:

3282
38

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 39 of 860 PageID #:

3283
39

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 40 of 860 PageID #:

3284
40

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 41 of 860 PageID #:

3285
41

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 42 of 860 PageID #:

3286
42

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 43 of 860 PageID #:

3287
43

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 44 of 860 PageID #:

3288
44

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 45 of 860 PageID #:

3289
45

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 46 of 860 PageID #:

3290
46

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 47 of 860 PageID #:

3291
47

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 48 of 860 PageID #:

3292
48

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 49 of 860 PageID #:

3293
49

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 50 of 860 PageID #:

3294
50

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 51 of 860 PageID #:

3295
51

Claim 1 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[2.1] The method of claim 1 802.11n D2.0 discloses all the elements of claim 1 for all the reasons provided above.

[2.2] wherein frequency 

difference between the first 

center frequency and the 

802.11n D2.0 discloses “wherein frequency difference between the first center frequency and the 

second center frequency is greater than the sum of one-half the first frequency range and one-half the 

second frequency range.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 52 of 860 PageID #:

3296
52

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

second center frequency is 

greater than the sum of onehalf the first frequency range 

and one-half the second 

frequency range.

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Informatio n Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non-HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 53 of 860 PageID #:

3297
53

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 54 of 860 PageID #:

3298
54

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 55 of 860 PageID #:

3299
55

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 56 of 860 PageID #:

3300
56

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 2 0

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 57 of 860 PageID #:

3301
57

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non-HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non-HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 58 of 860 PageID #:

3302
58

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit proce -

dures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n 82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit proced ure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 59 of 860 PageID #:

3303
59

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 60 of 860 PageID #:

3304
60

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 61 of 860 PageID #:

3305
61

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 62 of 860 PageID #:

3306
62

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 63 of 860 PageID #:

3307
63

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical d efinition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 64 of 860 PageID #:

3308
64

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 65 of 860 PageID #:

3309
65

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 66 of 860 PageID #:

3310
66

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 67 of 860 PageID #:

3311
67

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 68 of 860 PageID #:

3312
68

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 69 of 860 PageID #:

3313
69

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 70 of 860 PageID #:

3314
70

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 71 of 860 PageID #:

3315
71

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 72 of 860 PageID #:

3316
72

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 73 of 860 PageID #:

3317
73

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 74 of 860 PageID #:

3318
74

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 75 of 860 PageID #:

3319
75

Claim 2 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 3 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[3.1] The method of claim 1 802.11n D2.0 discloses all the elements of claim 1 for all the reasons provided above.

[3.2] wherein the first and 

second information are 

transmitted using the same 

802.11n D2.0 discloses “wherein the first and second information are transmitted using the same 

power amplifier in said wireless transmitter.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 76 of 860 PageID #:

3320
76

Claim 3 of the ’802 Patent Prior Art Reference – 802.11n D2.0

power amplifier in said 

wireless transmitter.

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematic al

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 77 of 860 PageID #:

3321
77

Claim 3 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 78 of 860 PageID #:

3322
78

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 79 of 860 PageID #:

3323
79

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 80 of 860 PageID #:

3324
80

Claim 3 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 81 of 860 PageID #:

3325
81

Claim 3 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 4 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[4.1] The method of claim 3 802.11n D2.0 discloses all the elements of claim 3 for all the reasons provided above.

[4.2] wherein the bandwidth 

of said power amplifier is 

greater than the difference 

between the first lowest 

frequency and the second 

highest frequency.

802.11n D2.0 discloses “wherein the bandwidth of said power amplifier is greater than the difference 

between the first lowest frequency and the second highest frequency.” See, e.g.: 

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 82 of 860 PageID #:

3326
82

Claim 4 of the ’802 Patent Prior Art Reference – 802.11n D2.0

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 83 of 860 PageID #:

3327
83

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 84 of 860 PageID #:

3328
84

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 85 of 860 PageID #:

3329
85

Claim 4 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 86 of 860 PageID #:

3330
86

Claim 4 of the ’802 Patent Prior Art Reference – 802.11n D2.0

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[6.1] The method of claim 1 802.11n D2.0 discloses all the elements of claim 1 for all the reasons provided above.

[6.2] wherein the first 

information corresponds to a 

first wireless protocol and the 

second information 

corresponds to a second 

wireless protocol.

802.11n D2.0 discloses “wherein the first information corresponds to a first wireless protocol and the 

second information corresponds to a second wireless protocol.” See, e.g.:

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 87 of 860 PageID #:

3331
87

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 88 of 860 PageID #:

3332
88

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 89 of 860 PageID #:

3333
89

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 90 of 860 PageID #:

3334
90

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 91 of 860 PageID #:

3335
91

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 92 of 860 PageID #:

3336
92

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 93 of 860 PageID #:

3337
93

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 94 of 860 PageID #:

3338
94

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A mod ulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 95 of 860 PageID #:

3339
95

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 96 of 860 PageID #:

3340
96

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 97 of 860 PageID #:

3341
97

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 98 of 860 PageID #:

3342
98

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 99 of 860 PageID #:

3343
99

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 100 of 860 PageID #:

3344
100

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 101 of 860 PageID #:

3345
101

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 102 of 860 PageID #:

3346
102

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 103 of 860 PageID #:

3347
103

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 104 of 860 PageID #:

3348
104

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 105 of 860 PageID #:

3349
105

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 106 of 860 PageID #:

3350
106

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 107 of 860 PageID #:

3351
107

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 108 of 860 PageID #:

3352
108

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 109 of 860 PageID #:

3353
109

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 110 of 860 PageID #:

3354
110

Claim 6 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[7.1] The method of claim 1 802.11n D2.0 discloses all the elements of claim 1 for all the reasons provided above.

[7.2] wherein the first 

information and the second 

information are the same data 

802.11n D2.0 discloses “wherein the first information and the second information are the same data 

transmitted across two different frequencies.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 111 of 860 PageID #:

3355
111

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

transmitted across two 

different frequencies.

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on b oth 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, the re are no non-HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 112 of 860 PageID #:

3356
112

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 113 of 860 PageID #:

3357
113

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protec tion

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 114 of 860 PageID #:

3358
114

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 115 of 860 PageID #:

3359
115

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this sub clause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 116 of 860 PageID #:

3360
116

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mix ed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 117 of 860 PageID #:

3361
117

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 118 of 860 PageID #:

3362
118

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A mod ulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 119 of 860 PageID #:

3363
119

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 120 of 860 PageID #:

3364
120

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 121 of 860 PageID #:

3365
121

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 122 of 860 PageID #:

3366
122

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 123 of 860 PageID #:

3367
123

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 124 of 860 PageID #:

3368
124

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 125 of 860 PageID #:

3369
125

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 126 of 860 PageID #:

3370
126

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 127 of 860 PageID #:

3371
127

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 128 of 860 PageID #:

3372
128

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 129 of 860 PageID #:

3373
129

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 130 of 860 PageID #:

3374
130

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 131 of 860 PageID #:

3375
131

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 132 of 860 PageID #:

3376
132

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 133 of 860 PageID #:

3377
133

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 134 of 860 PageID #:

3378
134

Claim 7 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[8.1] The method of claim 1 802.11n D2.0 discloses all the elements of claim 1 for all the reasons provided above.

[8.2] wherein the first 

information and the second 

802.11n D2.0 discloses “wherein the first information and the second information are from the same 

data stream.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 135 of 860 PageID #:

3379
135

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

information are from the same 

data stream.

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 136 of 860 PageID #:

3380
136

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 137 of 860 PageID #:

3381
137

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 138 of 860 PageID #:

3382
138

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 139 of 860 PageID #:

3383
139

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 140 of 860 PageID #:

3384
140

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 141 of 860 PageID #:

3385
141

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical tr ansmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is s et to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding typ es and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 142 of 860 PageID #:

3386
142

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 143 of 860 PageID #:

3387
143

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 144 of 860 PageID #:

3388
144

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 145 of 860 PageID #:

3389
145

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 146 of 860 PageID #:

3390
146

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 147 of 860 PageID #:

3391
147

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 148 of 860 PageID #:

3392
148

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 149 of 860 PageID #:

3393
149

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 150 of 860 PageID #:

3394
150

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 151 of 860 PageID #:

3395
151

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 152 of 860 PageID #:

3396
152

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 153 of 860 PageID #:

3397
153

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 154 of 860 PageID #:

3398
154

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 155 of 860 PageID #:

3399
155

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 156 of 860 PageID #:

3400
156

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 157 of 860 PageID #:

3401
157

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 158 of 860 PageID #:

3402
158

Claim 8 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[9.1] The method of claim 1 802.11n D2.0 discloses all the elements of claim 1 for all the reasons provided above.

[9.2] wherein first information 

and second information 

comprise a plurality of OFDM 

802.11n D2.0 discloses “wherein first information and second information comprise a plurality of 

OFDM symbols, wherein a first symbol is transmitted during a first time slot across the first 

frequency range and a second symbol is transmitted during the first time slot across the second 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 159 of 860 PageID #:

3403
159

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

symbols, wherein a first 

symbol is transmitted during a 

first time slot across the first 

frequency range and a second 

symbol is transmitted during 

the first time slot across the 

second frequency range, and 

wherein a third symbol is 

transmitted during a second 

time slot across the first 

frequency range and a fourth 

symbol is transmitted during 

the second time slot across a 

second frequency range.

frequency range, and wherein a third symbol is transmitted during a second time slot across the first 

frequency range and a fourth symbol is transmitted during the second time slot across a second 

frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 160 of 860 PageID #:

3404
160

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 161 of 860 PageID #:

3405
161

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 162 of 860 PageID #:

3406
162

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 163 of 860 PageID #:

3407
163

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 164 of 860 PageID #:

3408
164

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 165 of 860 PageID #:

3409
165

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 166 of 860 PageID #:

3410
166

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A mod ulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 167 of 860 PageID #:

3411
167

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 168 of 860 PageID #:

3412
168

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 169 of 860 PageID #:

3413
169

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 170 of 860 PageID #:

3414
170

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 171 of 860 PageID #:

3415
171

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 172 of 860 PageID #:

3416
172

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 173 of 860 PageID #:

3417
173

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 174 of 860 PageID #:

3418
174

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 175 of 860 PageID #:

3419
175

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 176 of 860 PageID #:

3420
176

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 177 of 860 PageID #:

3421
177

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 178 of 860 PageID #:

3422
178

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 179 of 860 PageID #:

3423
179

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 180 of 860 PageID #:

3424
180

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 181 of 860 PageID #:

3425
181

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 182 of 860 PageID #:

3426
182

Claim 9 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[10.1] A method of 

transmitting information in a 

To the extent the preamble is limiting, 802.11n D2.0 discloses “A method of transmitting information 

in a wireless communication channel comprising.” See, e.g.: 

20.1 Introduction

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 183 of 860 PageID #:

3427
183

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

wireless communication 

channel comprising:

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 184 of 860 PageID #:

3428
184

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.2] receiving a first digital 

signal comprising first data to 

be transmitted;

802.11n D2.0 discloses “receiving a first digital signal comprising first data to be transmitted.” See, 

e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 185 of 860 PageID #:

3429
185

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmissio n.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 186 of 860 PageID #:

3430
186

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 187 of 860 PageID #:

3431
187

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a respon se that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 188 of 860 PageID #:

3432
188

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 189 of 860 PageID #:

3433
189

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non-HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 190 of 860 PageID #:

3434
190

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed f ormat and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non-HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 191 of 860 PageID #:

3435
191

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical trans mit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow th e transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 192 of 860 PageID #:

3436
192

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 193 of 860 PageID #:

3437
193

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 194 of 860 PageID #:

3438
194

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 195 of 860 PageID #:

3439
195

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 196 of 860 PageID #:

3440
196

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 197 of 860 PageID #:

3441
197

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 198 of 860 PageID #:

3442
198

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 199 of 860 PageID #:

3443
199

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 200 of 860 PageID #:

3444
200

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 201 of 860 PageID #:

3445
201

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 202 of 860 PageID #:

3446
202

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 203 of 860 PageID #:

3447
203

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 204 of 860 PageID #:

3448
204

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 205 of 860 PageID #:

3449
205

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 206 of 860 PageID #:

3450
206

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 207 of 860 PageID #:

3451
207

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 208 of 860 PageID #:

3452
208

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.3] receiving a second 

digital signal comprising 

second data to be transmitted;

802.11n D2.0 discloses “receiving a second digital signal comprising second data to be transmitted.” 

See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 209 of 860 PageID #:

3453
209

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Ope rating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 210 of 860 PageID #:

3454
210

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 211 of 860 PageID #:

3455
211

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 212 of 860 PageID #:

3456
212

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 213 of 860 PageID #:

3457
213

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Su pport for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 214 of 860 PageID #:

3458
214

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are support ed.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 215 of 860 PageID #:

3459
215

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 216 of 860 PageID #:

3460
216

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 217 of 860 PageID #:

3461
217

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 218 of 860 PageID #:

3462
218

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 219 of 860 PageID #:

3463
219

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 220 of 860 PageID #:

3464
220

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 221 of 860 PageID #:

3465
221

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 222 of 860 PageID #:

3466
222

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 223 of 860 PageID #:

3467
223

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 224 of 860 PageID #:

3468
224

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 225 of 860 PageID #:

3469
225

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 226 of 860 PageID #:

3470
226

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 227 of 860 PageID #:

3471
227

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 228 of 860 PageID #:

3472
228

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 229 of 860 PageID #:

3473
229

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 230 of 860 PageID #:

3474
230

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 231 of 860 PageID #:

3475
231

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 232 of 860 PageID #:

3476
232

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.4] converting the first 

digital signal into a first 

analog signal using a first 

digital-to-analog converter, 

the first analog signal carrying 

the first data across a first 

frequency range;.

802.11n D2.0 discloses “converting the first digital signal into a first analog signal using a first 

digital-to-analog converter, the first analog signal carrying the first data across a first frequency 

range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 233 of 860 PageID #:

3477
233

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Ope rating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 234 of 860 PageID #:

3478
234

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 235 of 860 PageID #:

3479
235

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 236 of 860 PageID #:

3480
236

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 237 of 860 PageID #:

3481
237

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Su pport for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 238 of 860 PageID #:

3482
238

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are support ed.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 239 of 860 PageID #:

3483
239

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 240 of 860 PageID #:

3484
240

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 241 of 860 PageID #:

3485
241

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 242 of 860 PageID #:

3486
242

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 243 of 860 PageID #:

3487
243

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 244 of 860 PageID #:

3488
244

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 245 of 860 PageID #:

3489
245

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 246 of 860 PageID #:

3490
246

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 247 of 860 PageID #:

3491
247

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 248 of 860 PageID #:

3492
248

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 249 of 860 PageID #:

3493
249

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 250 of 860 PageID #:

3494
250

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 251 of 860 PageID #:

3495
251

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 252 of 860 PageID #:

3496
252

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 253 of 860 PageID #:

3497
253

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 254 of 860 PageID #:

3498
254

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 255 of 860 PageID #:

3499
255

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 256 of 860 PageID #:

3500
256

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.5] converting the second 

digital signal into a second 

analog signal using a second 

digital-to-analog converter, 

the second analog signal 

carrying the second data 

802.11n D2.0 discloses “converting the second digital signal into a second analog signal using a 

second digital-to-analog converter, the second analog signal carrying the second data across a second 

frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 257 of 860 PageID #:

3501
257

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

across a second frequency 

range;

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Ope rating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 258 of 860 PageID #:

3502
258

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 259 of 860 PageID #:

3503
259

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 260 of 860 PageID #:

3504
260

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 261 of 860 PageID #:

3505
261

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Su pport for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 262 of 860 PageID #:

3506
262

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are support ed.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 263 of 860 PageID #:

3507
263

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 264 of 860 PageID #:

3508
264

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 265 of 860 PageID #:

3509
265

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 266 of 860 PageID #:

3510
266

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 267 of 860 PageID #:

3511
267

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 268 of 860 PageID #:

3512
268

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 269 of 860 PageID #:

3513
269

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 270 of 860 PageID #:

3514
270

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 271 of 860 PageID #:

3515
271

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 272 of 860 PageID #:

3516
272

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 273 of 860 PageID #:

3517
273

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 274 of 860 PageID #:

3518
274

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 275 of 860 PageID #:

3519
275

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 276 of 860 PageID #:

3520
276

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 277 of 860 PageID #:

3521
277

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 278 of 860 PageID #:

3522
278

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 279 of 860 PageID #:

3523
279

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 280 of 860 PageID #:

3524
280

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.6] up-converting the first 

analog signal to a first RF 

center frequency to produce a 

first up-converted analog 

signal, wherein the first upconverted analog signal 

comprises a first up-converted 

frequency range from the first 

802.11n D2.0 discloses “up-converting the first analog signal to a first RF center frequency to 

produce a first up-converted analog signal, wherein the first up-converted analog signal comprises a 

first up-converted frequency range from the first RF center frequency minus one-half the first 

frequency range to the first RF center frequency plus one-half the first frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 281 of 860 PageID #:

3525
281

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

RF center frequency minus 

one-half the first frequency 

range to the first RF center 

frequency plus one-half the 

first frequency range;

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is s et to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 282 of 860 PageID #:

3526
282

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 283 of 860 PageID #:

3527
283

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a resp onse that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halve s of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 284 of 860 PageID #:

3528
284

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 285 of 860 PageID #:

3529
285

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and chann elization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 286 of 860 PageID #:

3530
286

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 287 of 860 PageID #:

3531
287

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 288 of 860 PageID #:

3532
288

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 289 of 860 PageID #:

3533
289

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 290 of 860 PageID #:

3534
290

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 291 of 860 PageID #:

3535
291

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 292 of 860 PageID #:

3536
292

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 293 of 860 PageID #:

3537
293

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 294 of 860 PageID #:

3538
294

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 295 of 860 PageID #:

3539
295

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 296 of 860 PageID #:

3540
296

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 297 of 860 PageID #:

3541
297

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 298 of 860 PageID #:

3542
298

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 299 of 860 PageID #:

3543
299

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 300 of 860 PageID #:

3544
300

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 301 of 860 PageID #:

3545
301

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 302 of 860 PageID #:

3546
302

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 303 of 860 PageID #:

3547
303

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 304 of 860 PageID #:

3548
304

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.7] up-converting the 

second analog signal to a 

second RF center frequency 

greater than the first center RF 

frequency to produce a second 

up-converted analog signal, 

wherein the second upconverted analog signal 

802.11n D2.0 discloses “up-converting the second analog signal to a second RF center frequency 

greater than the first center RF frequency to produce a second up-converted analog signal, wherein 

the second up-converted analog signal comprises a second up-converted frequency range from the 

second RF center frequency minus one-half the second frequency range to the second RF center 

frequency plus one-half the second frequency range, and wherein a frequency difference between the 

first RF center frequency and the second RF center frequency is greater than the sum of one-half the 

first frequency range and one-half the second frequency range.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 305 of 860 PageID #:

3549
305

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

comprises a second upconverted frequency range 

from the second RF center 

frequency minus one-half the 

second frequency range to the 

second RF center frequency 

plus one-half the second 

frequency range, and wherein 

a frequency difference 

between the first RF center 

frequency and the second RF 

center frequency is greater 

than the sum of one-half the 

first frequency range and onehalf the second frequency 

range;

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 306 of 860 PageID #:

3550
306

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 307 of 860 PageID #:

3551
307

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 308 of 860 PageID #:

3552
308

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 309 of 860 PageID #:

3553
309

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 310 of 860 PageID #:

3554
310

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 311 of 860 PageID #:

3555
311

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 312 of 860 PageID #:

3556
312

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 313 of 860 PageID #:

3557
313

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 314 of 860 PageID #:

3558
314

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 315 of 860 PageID #:

3559
315

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 316 of 860 PageID #:

3560
316

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 317 of 860 PageID #:

3561
317

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 318 of 860 PageID #:

3562
318

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 319 of 860 PageID #:

3563
319

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 320 of 860 PageID #:

3564
320

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 321 of 860 PageID #:

3565
321

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 322 of 860 PageID #:

3566
322

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 323 of 860 PageID #:

3567
323

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 324 of 860 PageID #:

3568
324

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 325 of 860 PageID #:

3569
325

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 326 of 860 PageID #:

3570
326

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 327 of 860 PageID #:

3571
327

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 328 of 860 PageID #:

3572
328

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.8] combining the first upconverted analog signal and 

the second up-converted 

analog signal to produce a 

combined up-converted 

signal;

802.11n D2.0 discloses “combining the first up-converted analog signal and the second up-converted 

analog signal to produce a combined up-converted signal.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 329 of 860 PageID #:

3573
329

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is s et to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 330 of 860 PageID #:

3574
330

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 331 of 860 PageID #:

3575
331

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a resp onse that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halve s of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 332 of 860 PageID #:

3576
332

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 333 of 860 PageID #:

3577
333

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and chann elization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 334 of 860 PageID #:

3578
334

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 335 of 860 PageID #:

3579
335

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 336 of 860 PageID #:

3580
336

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 337 of 860 PageID #:

3581
337

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 338 of 860 PageID #:

3582
338

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 339 of 860 PageID #:

3583
339

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 340 of 860 PageID #:

3584
340

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 341 of 860 PageID #:

3585
341

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 342 of 860 PageID #:

3586
342

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 343 of 860 PageID #:

3587
343

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 344 of 860 PageID #:

3588
344

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 345 of 860 PageID #:

3589
345

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 346 of 860 PageID #:

3590
346

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 347 of 860 PageID #:

3591
347

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 348 of 860 PageID #:

3592
348

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 349 of 860 PageID #:

3593
349

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 350 of 860 PageID #:

3594
350

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 351 of 860 PageID #:

3595
351

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 352 of 860 PageID #:

3596
352

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.9] amplifying the 

combined up-converted signal 

in a power amplifier resulting 

in an amplified combined upconverted signal; and

802.11n D2.0 discloses “amplifying the combined up-converted signal in a power amplifier resulting 

in an amplified combined up-converted signal.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 353 of 860 PageID #:

3597
353

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is s et to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 354 of 860 PageID #:

3598
354

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 355 of 860 PageID #:

3599
355

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a resp onse that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halve s of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 356 of 860 PageID #:

3600
356

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 357 of 860 PageID #:

3601
357

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and chann elization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 358 of 860 PageID #:

3602
358

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 359 of 860 PageID #:

3603
359

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 360 of 860 PageID #:

3604
360

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 361 of 860 PageID #:

3605
361

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 362 of 860 PageID #:

3606
362

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 363 of 860 PageID #:

3607
363

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 364 of 860 PageID #:

3608
364

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 365 of 860 PageID #:

3609
365

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 366 of 860 PageID #:

3610
366

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 367 of 860 PageID #:

3611
367

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 368 of 860 PageID #:

3612
368

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 369 of 860 PageID #:

3613
369

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 370 of 860 PageID #:

3614
370

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 371 of 860 PageID #:

3615
371

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 372 of 860 PageID #:

3616
372

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 373 of 860 PageID #:

3617
373

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 374 of 860 PageID #:

3618
374

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 375 of 860 PageID #:

3619
375

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 376 of 860 PageID #:

3620
376

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.10] transmitting the 

amplified combined upconverted signal on a first 

antenna,

802.11n D2.0 discloses “transmitting the amplified combined up-converted signal on a first antenna.” 

See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 377 of 860 PageID #:

3621
377

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. Th e type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 378 of 860 PageID #:

3622
378

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 379 of 860 PageID #:

3623
379

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 380 of 860 PageID #:

3624
380

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 381 of 860 PageID #:

3625
381

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 382 of 860 PageID #:

3626
382

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 383 of 860 PageID #:

3627
383

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 384 of 860 PageID #:

3628
384

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 385 of 860 PageID #:

3629
385

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 386 of 860 PageID #:

3630
386

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 387 of 860 PageID #:

3631
387

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 388 of 860 PageID #:

3632
388

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 389 of 860 PageID #:

3633
389

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 390 of 860 PageID #:

3634
390

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 391 of 860 PageID #:

3635
391

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 392 of 860 PageID #:

3636
392

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 393 of 860 PageID #:

3637
393

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 394 of 860 PageID #:

3638
394

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 395 of 860 PageID #:

3639
395

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 396 of 860 PageID #:

3640
396

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 397 of 860 PageID #:

3641
397

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 398 of 860 PageID #:

3642
398

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 399 of 860 PageID #:

3643
399

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 400 of 860 PageID #:

3644
400

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[10.11] wherein the 

bandwidth of said power 

amplifier is greater than the 

difference between a lowest 

frequency in the first upconverted frequency range 

and a highest frequency in the 

802.11n D2.0 discloses “wherein the bandwidth of said power amplifier is greater than the difference 

between a lowest frequency in the first up-converted frequency range and a highest frequency in the 

second up-converted frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 401 of 860 PageID #:

3645
401

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

second up-converted 

frequency range.

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 a re described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 402 of 860 PageID #:

3646
402

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 403 of 860 PageID #:

3647
403

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 404 of 860 PageID #:

3648
404

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 405 of 860 PageID #:

3649
405

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatia l streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 406 of 860 PageID #:

3650
406

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non-HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non-HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 407 of 860 PageID #:

3651
407

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit proce -

dures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 408 of 860 PageID #:

3652
408

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 409 of 860 PageID #:

3653
409

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 410 of 860 PageID #:

3654
410

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 411 of 860 PageID #:

3655
411

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 412 of 860 PageID #:

3656
412

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 413 of 860 PageID #:

3657
413

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields o f

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 414 of 860 PageID #:

3658
414

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 415 of 860 PageID #:

3659
415

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 416 of 860 PageID #:

3660
416

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 417 of 860 PageID #:

3661
417

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 418 of 860 PageID #:

3662
418

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 419 of 860 PageID #:

3663
419

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 420 of 860 PageID #:

3664
420

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 421 of 860 PageID #:

3665
421

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 422 of 860 PageID #:

3666
422

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 423 of 860 PageID #:

3667
423

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 424 of 860 PageID #:

3668
424

Claim 10 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[13.1] The method of claim 10 802.11n D2.0 discloses all the elements of claim 10 for all the reasons provided above.

[13.2] wherein the first digital 

signal is encoded using a first 

wireless protocol and the 

802.11n D2.0 discloses “wherein the first digital signal is encoded using a first wireless protocol and 

the second digital signal is encoded using a second wireless protocol.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 425 of 860 PageID #:

3669
425

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

second digital signal is 

encoded using a second 

wireless protocol.

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 a re described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 426 of 860 PageID #:

3670
426

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 427 of 860 PageID #:

3671
427

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 428 of 860 PageID #:

3672
428

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 an d Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 429 of 860 PageID #:

3673
429

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 430 of 860 PageID #:

3674
430

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 431 of 860 PageID #:

3675
431

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical tr ansmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is s et to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding typ es and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 432 of 860 PageID #:

3676
432

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against d elay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 433 of 860 PageID #:

3677
433

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 434 of 860 PageID #:

3678
434

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 435 of 860 PageID #:

3679
435

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 436 of 860 PageID #:

3680
436

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 437 of 860 PageID #:

3681
437

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 438 of 860 PageID #:

3682
438

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 439 of 860 PageID #:

3683
439

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 440 of 860 PageID #:

3684
440

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 441 of 860 PageID #:

3685
441

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 442 of 860 PageID #:

3686
442

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 443 of 860 PageID #:

3687
443

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 444 of 860 PageID #:

3688
444

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 445 of 860 PageID #:

3689
445

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 446 of 860 PageID #:

3690
446

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 447 of 860 PageID #:

3691
447

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 448 of 860 PageID #:

3692
448

Claim 13 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[14.1] The method of claim 10 802.11n D2.0 discloses all the elements of claim 10 for all the reasons provided above.

[14.2] wherein the second 

data is the same as the first 

802.11n D2.0 discloses “wherein the second data is the same as the first data, the method further 

comprising.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 449 of 860 PageID #:

3693
449

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

data, the method further 

comprising:

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 a re described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 450 of 860 PageID #:

3694
450

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 451 of 860 PageID #:

3695
451

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 452 of 860 PageID #:

3696
452

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 an d Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 453 of 860 PageID #:

3697
453

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 454 of 860 PageID #:

3698
454

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 455 of 860 PageID #:

3699
455

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 456 of 860 PageID #:

3700
456

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 457 of 860 PageID #:

3701
457

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 458 of 860 PageID #:

3702
458

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 459 of 860 PageID #:

3703
459

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 460 of 860 PageID #:

3704
460

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 461 of 860 PageID #:

3705
461

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 462 of 860 PageID #:

3706
462

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 463 of 860 PageID #:

3707
463

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 464 of 860 PageID #:

3708
464

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 465 of 860 PageID #:

3709
465

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 466 of 860 PageID #:

3710
466

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 467 of 860 PageID #:

3711
467

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 468 of 860 PageID #:

3712
468

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 469 of 860 PageID #:

3713
469

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 470 of 860 PageID #:

3714
470

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 471 of 860 PageID #:

3715
471

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 472 of 860 PageID #:

3716
472

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[14.3] receiving the 

transmitted signal on a second 

antenna;

802.11n D2.0 discloses “receiving the transmitted signal on a second antenna.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 473 of 860 PageID #:

3717
473

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on b oth 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, the re are no non-HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 474 of 860 PageID #:

3718
474

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 475 of 860 PageID #:

3719
475

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 476 of 860 PageID #:

3720
476

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 477 of 860 PageID #:

3721
477

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 478 of 860 PageID #:

3722
478

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 479 of 860 PageID #:

3723
479

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 480 of 860 PageID #:

3724
480

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 481 of 860 PageID #:

3725
481

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 482 of 860 PageID #:

3726
482

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 483 of 860 PageID #:

3727
483

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 484 of 860 PageID #:

3728
484

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 485 of 860 PageID #:

3729
485

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 486 of 860 PageID #:

3730
486

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 487 of 860 PageID #:

3731
487

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 488 of 860 PageID #:

3732
488

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 489 of 860 PageID #:

3733
489

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 490 of 860 PageID #:

3734
490

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 491 of 860 PageID #:

3735
491

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 492 of 860 PageID #:

3736
492

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 493 of 860 PageID #:

3737
493

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 494 of 860 PageID #:

3738
494

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 495 of 860 PageID #:

3739
495

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 496 of 860 PageID #:

3740
496

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[14.4] amplifying the received 

signal in a low noise amplifier 

resulting in an amplified 

received up-converted signal, 

wherein the bandwidth of said 

low noise amplifier is greater 

than the difference between 

the lowest frequency in the 

802.11n D2.0 discloses “amplifying the received signal in a low noise amplifier resulting in an 

amplified received up-converted signal, wherein the bandwidth of said low noise amplifier is greater 

than the difference between the lowest frequency in the first up-converted frequency range and the 

highest frequency in the second up-converted frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 497 of 860 PageID #:

3741
497

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

first up-converted frequency 

range and the highest 

frequency in the second upconverted frequency range;

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is s et to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 498 of 860 PageID #:

3742
498

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 499 of 860 PageID #:

3743
499

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a resp onse that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halve s of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 500 of 860 PageID #:

3744
500

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 501 of 860 PageID #:

3745
501

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and chann elization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 502 of 860 PageID #:

3746
502

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 503 of 860 PageID #:

3747
503

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 504 of 860 PageID #:

3748
504

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 505 of 860 PageID #:

3749
505

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 506 of 860 PageID #:

3750
506

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 507 of 860 PageID #:

3751
507

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 508 of 860 PageID #:

3752
508

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 509 of 860 PageID #:

3753
509

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 510 of 860 PageID #:

3754
510

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 511 of 860 PageID #:

3755
511

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 512 of 860 PageID #:

3756
512

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 513 of 860 PageID #:

3757
513

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 514 of 860 PageID #:

3758
514

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 515 of 860 PageID #:

3759
515

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 516 of 860 PageID #:

3760
516

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 517 of 860 PageID #:

3761
517

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 518 of 860 PageID #:

3762
518

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 519 of 860 PageID #:

3763
519

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 520 of 860 PageID #:

3764
520

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these reference s. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[14.5] down-converting the 

amplified received upconverted signal using a first 

down-converter and a signal 

corresponding to the first RF 

center frequency to produce a 

fourth analog signal 

802.11n D2.0 discloses “down-converting the amplified received up-converted signal using a first 

down-converter and a signal corresponding to the first RF center frequency to produce a fourth 

analog signal corresponding to the first analog signal.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 521 of 860 PageID #:

3765
521

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

corresponding to the first 

analog signal; and

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Ope rating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 522 of 860 PageID #:

3766
522

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 523 of 860 PageID #:

3767
523

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 524 of 860 PageID #:

3768
524

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 525 of 860 PageID #:

3769
525

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Su pport for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 526 of 860 PageID #:

3770
526

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are support ed.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 527 of 860 PageID #:

3771
527

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 528 of 860 PageID #:

3772
528

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 529 of 860 PageID #:

3773
529

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 530 of 860 PageID #:

3774
530

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 531 of 860 PageID #:

3775
531

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 532 of 860 PageID #:

3776
532

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 533 of 860 PageID #:

3777
533

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 534 of 860 PageID #:

3778
534

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 535 of 860 PageID #:

3779
535

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 536 of 860 PageID #:

3780
536

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 537 of 860 PageID #:

3781
537

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 538 of 860 PageID #:

3782
538

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 539 of 860 PageID #:

3783
539

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 540 of 860 PageID #:

3784
540

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 541 of 860 PageID #:

3785
541

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 542 of 860 PageID #:

3786
542

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 543 of 860 PageID #:

3787
543

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 544 of 860 PageID #:

3788
544

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[14.6] down-converting the 

amplified received upconverted analog signal using 

a second down-converter and 

a signal corresponding to the 

second RF center frequency to 

produce a fifth analog signal 

802.11n D2.0 discloses “down-converting the amplified received up-converted analog signal using a 

second down-converter and a signal corresponding to the second RF center frequency to produce a 

fifth analog signal corresponding to the second analog signal.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 545 of 860 PageID #:

3789
545

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

corresponding to the second 

analog signal.

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Ope rating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 546 of 860 PageID #:

3790
546

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 547 of 860 PageID #:

3791
547

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 548 of 860 PageID #:

3792
548

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 549 of 860 PageID #:

3793
549

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Su pport for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 550 of 860 PageID #:

3794
550

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are support ed.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 551 of 860 PageID #:

3795
551

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 552 of 860 PageID #:

3796
552

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 553 of 860 PageID #:

3797
553

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 554 of 860 PageID #:

3798
554

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 555 of 860 PageID #:

3799
555

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 556 of 860 PageID #:

3800
556

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 557 of 860 PageID #:

3801
557

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 558 of 860 PageID #:

3802
558

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 559 of 860 PageID #:

3803
559

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 560 of 860 PageID #:

3804
560

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 561 of 860 PageID #:

3805
561

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 562 of 860 PageID #:

3806
562

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 563 of 860 PageID #:

3807
563

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 564 of 860 PageID #:

3808
564

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 565 of 860 PageID #:

3809
565

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 566 of 860 PageID #:

3810
566

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 567 of 860 PageID #:

3811
567

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 568 of 860 PageID #:

3812
568

Claim 14 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[17.1] A wireless 

communication system 

comprising:

To the extent the preamble is limiting, 802.11n D2.0 discloses “A wireless communication system 

comprising.” See, e.g.: 

20.1 Introduction

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 569 of 860 PageID #:

3813
569

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for op eration in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and r eceive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Su pport for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 570 of 860 PageID #:

3814
570

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these reference s. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[17.2] a baseband digital 

system for providing a first 

digital signal comprising a 

first data to be transmitted and 

a second digital signal 

comprising a second data to 

be transmitted;

802.11n D2.0 discloses “a baseband digital system for providing a first digital signal comprising a 

first data to be transmitted and a second digital signal comprising a second data to be transmitted.” 

See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 571 of 860 PageID #:

3815
571

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on b oth 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, the re are no non-HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 572 of 860 PageID #:

3816
572

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 573 of 860 PageID #:

3817
573

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 574 of 860 PageID #:

3818
574

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a n on-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 575 of 860 PageID #:

3819
575

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 576 of 860 PageID #:

3820
576

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 577 of 860 PageID #:

3821
577

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical trans mit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow th e transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 578 of 860 PageID #:

3822
578

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 579 of 860 PageID #:

3823
579

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 580 of 860 PageID #:

3824
580

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 581 of 860 PageID #:

3825
581

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 582 of 860 PageID #:

3826
582

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 583 of 860 PageID #:

3827
583

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 584 of 860 PageID #:

3828
584

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 585 of 860 PageID #:

3829
585

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 586 of 860 PageID #:

3830
586

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 587 of 860 PageID #:

3831
587

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 588 of 860 PageID #:

3832
588

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 589 of 860 PageID #:

3833
589

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 590 of 860 PageID #:

3834
590

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 591 of 860 PageID #:

3835
591

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 592 of 860 PageID #:

3836
592

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 593 of 860 PageID #:

3837
593

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 594 of 860 PageID #:

3838
594

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[17.3] a first digital-to-analog 

converter for receiving the 

first digital signal and 

converting the first digital 

signal into a first analog 

signal, the first analog signal 

802.11n D2.0 discloses “a first digital-to-analog converter for receiving the first digital signal and 

converting the first digital signal into a first analog signal, the first analog signal carrying the first 

data across a first frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 595 of 860 PageID #:

3839
595

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

carrying the first data across a 

first frequency range;

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non-HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 596 of 860 PageID #:

3840
596

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 597 of 860 PageID #:

3841
597

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 598 of 860 PageID #:

3842
598

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 599 of 860 PageID #:

3843
599

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high th roughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non-HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 600 of 860 PageID #:

3844
600

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 601 of 860 PageID #:

3845
601

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit proce -

dures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. Thes e transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit pro cedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 602 of 860 PageID #:

3846
602

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 603 of 860 PageID #:

3847
603

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 604 of 860 PageID #:

3848
604

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 605 of 860 PageID #:

3849
605

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 606 of 860 PageID #:

3850
606

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 607 of 860 PageID #:

3851
607

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 608 of 860 PageID #:

3852
608

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 609 of 860 PageID #:

3853
609

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 610 of 860 PageID #:

3854
610

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 611 of 860 PageID #:

3855
611

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 612 of 860 PageID #:

3856
612

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 613 of 860 PageID #:

3857
613

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 614 of 860 PageID #:

3858
614

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 615 of 860 PageID #:

3859
615

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 616 of 860 PageID #:

3860
616

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 617 of 860 PageID #:

3861
617

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 618 of 860 PageID #:

3862
618

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[17.4] a second digital-toanalog converter for receiving 

the second digital signal and 

converting the second digital 

signal into a second analog 

signal, the second analog 

signal carrying the second 

802.11n D2.0 discloses “a second digital-to-analog converter for receiving the second digital signal 

and converting the second digital signal into a second analog signal, the second analog signal 

carrying the second data across a second frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 619 of 860 PageID #:

3863
619

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

data across a second 

frequency range;

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Ope rating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 620 of 860 PageID #:

3864
620

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 621 of 860 PageID #:

3865
621

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 622 of 860 PageID #:

3866
622

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 623 of 860 PageID #:

3867
623

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Su pport for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 624 of 860 PageID #:

3868
624

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are support ed.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 625 of 860 PageID #:

3869
625

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 626 of 860 PageID #:

3870
626

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 627 of 860 PageID #:

3871
627

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 628 of 860 PageID #:

3872
628

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 629 of 860 PageID #:

3873
629

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 630 of 860 PageID #:

3874
630

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 631 of 860 PageID #:

3875
631

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 632 of 860 PageID #:

3876
632

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 633 of 860 PageID #:

3877
633

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 634 of 860 PageID #:

3878
634

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 635 of 860 PageID #:

3879
635

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 636 of 860 PageID #:

3880
636

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 637 of 860 PageID #:

3881
637

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 638 of 860 PageID #:

3882
638

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 639 of 860 PageID #:

3883
639

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 640 of 860 PageID #:

3884
640

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 641 of 860 PageID #:

3885
641

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 642 of 860 PageID #:

3886
642

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[17.5] a first up-converter 

circuit having a first input 

coupled to receive the first 

analog signal and a second 

input coupled to receive a first 

modulation signal having a 

first RF frequency, wherein 

the first up-converter outputs 

802.11n D2.0 discloses “a first up-converter circuit having a first input coupled to receive the first 

analog signal and a second input coupled to receive a first modulation signal having a first RF 

frequency, wherein the first up-converter outputs a first up-converted analog signal comprising a first 

up-converted frequency range from the first RF frequency minus one-half the first frequency range to 

the first RF frequency plus one-half the first frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 643 of 860 PageID #:

3887
643

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

a first up-converted analog 

signal comprising a first upconverted frequency range 

from the first RF frequency 

minus one-half the first 

frequency range to the first 

RF frequency plus one-half 

the first frequency range;

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non-HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 644 of 860 PageID #:

3888
644

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 645 of 860 PageID #:

3889
645

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halve s of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 646 of 860 PageID #:

3890
646

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 647 of 860 PageID #:

3891
647

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and chann elization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed fo rmat is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 648 of 860 PageID #:

3892
648

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 649 of 860 PageID #:

3893
649

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 650 of 860 PageID #:

3894
650

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 651 of 860 PageID #:

3895
651

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 652 of 860 PageID #:

3896
652

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 653 of 860 PageID #:

3897
653

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 654 of 860 PageID #:

3898
654

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 655 of 860 PageID #:

3899
655

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 656 of 860 PageID #:

3900
656

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 657 of 860 PageID #:

3901
657

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 658 of 860 PageID #:

3902
658

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 659 of 860 PageID #:

3903
659

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 660 of 860 PageID #:

3904
660

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 661 of 860 PageID #:

3905
661

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 662 of 860 PageID #:

3906
662

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 663 of 860 PageID #:

3907
663

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 664 of 860 PageID #:

3908
664

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 665 of 860 PageID #:

3909
665

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 666 of 860 PageID #:

3910
666

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[17.6] a second up-converter 

circuit having a first input 

coupled to receive the second 

analog signal and a second 

input coupled to receive a 

second modulation signal 

having a second RF 

frequency, wherein the second 

802.11n D2.0 discloses “a second up-converter circuit having a first input coupled to receive the 

second analog signal and a second input coupled to receive a second modulation signal having a 

second RF frequency, wherein the second up-converter outputs a second up-converted analog signal 

comprising a second up-converted frequency range from the second RF frequency minus one-half the 

second frequency range to the second RF frequency plus one-half the second frequency range, and 

wherein frequency difference between the first RF frequency and the second RF frequency is greater 

than the sum of one-half the first frequency range and one-half the second frequency range.” See, 

e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 667 of 860 PageID #:

3911
667

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

up-converter outputs a second 

up-converted analog signal 

comprising a second upconverted frequency range 

from the second RF frequency 

minus one-half the second 

frequency range to the second 

RF frequency plus one-half 

the second frequency range, 

and wherein frequency 

difference between the first 

RF frequency and the second 

RF frequency is greater than 

the sum of one-half the first 

frequency range and one-half 

the second frequency range; 

and

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non-greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is s et to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 668 of 860 PageID #:

3912
668

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 669 of 860 PageID #:

3913
669

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a resp onse that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halve s of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 670 of 860 PageID #:

3914
670

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 671 of 860 PageID #:

3915
671

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed form at is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 672 of 860 PageID #:

3916
672

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 673 of 860 PageID #:

3917
673

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 674 of 860 PageID #:

3918
674

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 675 of 860 PageID #:

3919
675

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 676 of 860 PageID #:

3920
676

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 677 of 860 PageID #:

3921
677

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 678 of 860 PageID #:

3922
678

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 679 of 860 PageID #:

3923
679

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 680 of 860 PageID #:

3924
680

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 681 of 860 PageID #:

3925
681

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 682 of 860 PageID #:

3926
682

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 683 of 860 PageID #:

3927
683

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 684 of 860 PageID #:

3928
684

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 685 of 860 PageID #:

3929
685

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 686 of 860 PageID #:

3930
686

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 687 of 860 PageID #:

3931
687

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 688 of 860 PageID #:

3932
688

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 689 of 860 PageID #:

3933
689

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 690 of 860 PageID #:

3934
690

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[17.7] a power amplifier 

coupled to receive the first 

and second up-converted 

analog signals, wherein the 

bandwidth of the power 

amplifier is greater than the 

difference between a lowest 

frequency in the first up802.11n D2.0 discloses “a power amplifier coupled to receive the first and second up-converted 

analog signals, wherein the bandwidth of the power amplifier is greater than the difference between a 

lowest frequency in the first up-converted frequency range and a highest frequency in the second upconverted frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 691 of 860 PageID #:

3935
691

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

converted frequency range 

and a highest frequency in the 

second up-converted 

frequency range.

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non-HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 692 of 860 PageID #:

3936
692

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 693 of 860 PageID #:

3937
693

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 694 of 860 PageID #:

3938
694

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phas e shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phas e is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 695 of 860 PageID #:

3939
695

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 696 of 860 PageID #:

3940
696

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 697 of 860 PageID #:

3941
697

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 698 of 860 PageID #:

3942
698

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 699 of 860 PageID #:

3943
699

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 700 of 860 PageID #:

3944
700

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 701 of 860 PageID #:

3945
701

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 702 of 860 PageID #:

3946
702

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 703 of 860 PageID #:

3947
703

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 704 of 860 PageID #:

3948
704

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 705 of 860 PageID #:

3949
705

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 706 of 860 PageID #:

3950
706

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 707 of 860 PageID #:

3951
707

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 708 of 860 PageID #:

3952
708

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 709 of 860 PageID #:

3953
709

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 710 of 860 PageID #:

3954
710

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 711 of 860 PageID #:

3955
711

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 712 of 860 PageID #:

3956
712

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 713 of 860 PageID #:

3957
713

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 714 of 860 PageID #:

3958
714

Claim 17 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[21.1] The communication 

system of claim 17

802.11n D2.0 discloses all the elements of claim 17 for all the reasons provided above.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 715 of 860 PageID #:

3959
715

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[21.2] wherein the first data of 

the first digital signal is 

encoded using a first wireless 

protocol and the first data of 

the second digital signal is 

encoded using a second 

wireless protocol.

802.11n D2.0 discloses “wherein the first data of the first digital signal is encoded using a first 

wireless protocol and the first data of the second digital signal is encoded using a second wireless 

protocol.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 716 of 860 PageID #:

3960
716

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 a re described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 717 of 860 PageID #:

3961
717

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 718 of 860 PageID #:

3962
718

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 an d Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 719 of 860 PageID #:

3963
719

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 720 of 860 PageID #:

3964
720

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 721 of 860 PageID #:

3965
721

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 722 of 860 PageID #:

3966
722

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 723 of 860 PageID #:

3967
723

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 724 of 860 PageID #:

3968
724

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 725 of 860 PageID #:

3969
725

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 726 of 860 PageID #:

3970
726

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 727 of 860 PageID #:

3971
727

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 728 of 860 PageID #:

3972
728

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 729 of 860 PageID #:

3973
729

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 730 of 860 PageID #:

3974
730

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 731 of 860 PageID #:

3975
731

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 732 of 860 PageID #:

3976
732

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 733 of 860 PageID #:

3977
733

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 734 of 860 PageID #:

3978
734

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 735 of 860 PageID #:

3979
735

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 736 of 860 PageID #:

3980
736

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 737 of 860 PageID #:

3981
737

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 738 of 860 PageID #:

3982
738

Claim 21 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[22.1] The communication 

system of claim 17

802.11n D2.0 discloses all the elements of claim 17 for all the reasons provided above.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 739 of 860 PageID #:

3983
739

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[22.2] wherein the second 

data corresponds to the first 

data and wherein the power 

amplifier outputs a third upconverted signal comprising 

the up-converted first analog 

signal and the up-converted 

second analog signal.

802.11n D2.0 discloses “wherein the second data corresponds to the first data and wherein the power 

amplifier outputs a third up-converted signal comprising the up-converted first analog signal and the 

up-converted second analog signal.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 740 of 860 PageID #:

3984
740

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

is required depends on the type of transmission as well as the type of the non-HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 741 of 860 PageID #:

3985
741

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on b oth 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 742 of 860 PageID #:

3986
742

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 743 of 860 PageID #:

3987
743

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 744 of 860 PageID #:

3988
744

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 745 of 860 PageID #:

3989
745

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 746 of 860 PageID #:

3990
746

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit sta te

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 747 of 860 PageID #:

3991
747

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 748 of 860 PageID #:

3992
748

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 749 of 860 PageID #:

3993
749

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 750 of 860 PageID #:

3994
750

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 751 of 860 PageID #:

3995
751

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 752 of 860 PageID #:

3996
752

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 753 of 860 PageID #:

3997
753

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 754 of 860 PageID #:

3998
754

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 755 of 860 PageID #:

3999
755

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 756 of 860 PageID #:

4000
756

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 757 of 860 PageID #:

4001
757

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 758 of 860 PageID #:

4002
758

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 759 of 860 PageID #:

4003
759

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 760 of 860 PageID #:

4004
760

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 761 of 860 PageID #:

4005
761

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 762 of 860 PageID #:

4006
762

Claim 22 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[23.1] The communication 

system of claim 17

802.11n D2.0 discloses all the elements of claim 17 for all the reasons provided above.

[23.2] wherein first and 

second data to be transmitted 

802.11n D2.0 discloses “wherein first and second data to be transmitted comprise a plurality of 

OFDM symbols, wherein a first symbol is transmitted during a first time slot across the first upCase 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 763 of 860 PageID #:

4007
763

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

comprise a plurality of OFDM 

symbols, wherein a first 

symbol is transmitted during a 

first time slot across the first 

up-converted frequency range 

and a second symbol is 

transmitted during the first 

time slot across the second 

up-converted frequency range, 

and wherein a third symbol is 

transmitted during a second 

time slot across the first upconverted frequency range 

and a fourth symbol is 

transmitted during the second 

time slot across a second upconverted frequency range.

converted frequency range and a second symbol is transmitted during the first time slot across the 

second up-converted frequency range, and wherein a third symbol is transmitted during a second time 

slot across the first up-converted frequency range and a fourth symbol is transmitted during the 

second time slot across a second up-converted frequency range.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 764 of 860 PageID #:

4008
764

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 a re described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 765 of 860 PageID #:

4009
765

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 766 of 860 PageID #:

4010
766

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 an d Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non-PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 767 of 860 PageID #:

4011
767

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 768 of 860 PageID #:

4012
768

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 769 of 860 PageID #:

4013
769

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical tr ansmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is s et to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding typ es and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 770 of 860 PageID #:

4014
770

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against d elay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 771 of 860 PageID #:

4015
771

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 772 of 860 PageID #:

4016
772

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 773 of 860 PageID #:

4017
773

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 774 of 860 PageID #:

4018
774

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 775 of 860 PageID #:

4019
775

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 776 of 860 PageID #:

4020
776

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 777 of 860 PageID #:

4021
777

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 778 of 860 PageID #:

4022
778

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 779 of 860 PageID #:

4023
779

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 780 of 860 PageID #:

4024
780

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 781 of 860 PageID #:

4025
781

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 782 of 860 PageID #:

4026
782

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 783 of 860 PageID #:

4027
783

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 784 of 860 PageID #:

4028
784

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 785 of 860 PageID #:

4029
785

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 786 of 860 PageID #:

4030
786

Claim 23 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

[24.1] An electronic circuit 

comprising:

To the extent the preamble is limiting, 802.11n D2.0 discloses “An electronic circuit comprising.” 

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. ACase 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 787 of 860 PageID #:

4031
787

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Obviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these reference s. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[24.2] a first down-converter 

circuit having a first input 

coupled to receive a first upconverted signal, a second 

input coupled to receive a first 

demodulation signal having a 

first RF frequency, and an 

output, wherein the first 

down-converter circuit 

outputs a first down-converted 

signal on the first downconverter output;

802.11n D2.0 discloses “a first down-converter circuit having a first input coupled to receive a first 

up-converted signal, a second input coupled to receive a first demodulation signal having a first RF 

frequency, and an output, wherein the first down-converter circuit outputs a first down-converted 

signal on the first down-converter output.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that s upports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 788 of 860 PageID #:

4032
788

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 789 of 860 PageID #:

4033
789

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 790 of 860 PageID #:

4034
790

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a respon se that is sent as a nonHT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on b oth 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 791 of 860 PageID #:

4035
791

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non-HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 792 of 860 PageID #:

4036
792

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 793 of 860 PageID #:

4037
793

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the len gth of the guard interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 794 of 860 PageID #:

4038
794

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical trans mit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow th e transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 795 of 860 PageID #:

4039
795

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 796 of 860 PageID #:

4040
796

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 797 of 860 PageID #:

4041
797

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 798 of 860 PageID #:

4042
798

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 799 of 860 PageID #:

4043
799

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 800 of 860 PageID #:

4044
800

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 801 of 860 PageID #:

4045
801

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 802 of 860 PageID #:

4046
802

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 803 of 860 PageID #:

4047
803

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 804 of 860 PageID #:

4048
804

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 805 of 860 PageID #:

4049
805

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 806 of 860 PageID #:

4050
806

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 807 of 860 PageID #:

4051
807

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 808 of 860 PageID #:

4052
808

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 809 of 860 PageID #:

4053
809

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 810 of 860 PageID #:

4054
810

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 811 of 860 PageID #:

4055
811

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[24.3] a second downconverter circuit having a first 

input coupled to receive the 

first up-converted signal, a 

second input coupled to 

receive a second 

demodulation signal having a 

second RF frequency different 

802.11n D2.0 discloses “a second down-converter circuit having a first input coupled to receive the 

first up-converted signal, a second input coupled to receive a second demodulation signal having a 

second RF frequency different than the first RF frequency, and an output, wherein the second downconverter outputs a second down-converted signal on the second down-converter output, wherein the 

first up-converted signal comprises a first signal modulated at the first RF frequency and a second 

signal modulated at the second RF frequency.” See, e.g.: 

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 812 of 860 PageID #:

4056
812

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

than the first RF frequency, 

and an output, wherein the 

second down-converter 

outputs a second downconverted signal on the 

second down-converter 

output, wherein the first upconverted signal comprises a 

first signal modulated at the 

first RF frequency and a 

second signal modulated at 

the second RF frequency; and

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that suppo rts the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non-HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 are described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 813 of 860 PageID #:

4057
813

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 814 of 860 PageID #:

4058
814

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 815 of 860 PageID #:

4059
815

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phas e shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phas e is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 816 of 860 PageID #:

4060
816

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatial streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 817 of 860 PageID #:

4061
817

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 818 of 860 PageID #:

4062
818

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. These transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit procedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 819 of 860 PageID #:

4063
819

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 820 of 860 PageID #:

4064
820

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub-carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 821 of 860 PageID #:

4065
821

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 822 of 860 PageID #:

4066
822

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 823 of 860 PageID #:

4067
823

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 824 of 860 PageID #:

4068
824

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 825 of 860 PageID #:

4069
825

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 826 of 860 PageID #:

4070
826

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 827 of 860 PageID #:

4071
827

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 828 of 860 PageID #:

4072
828

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 829 of 860 PageID #:

4073
829

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 830 of 860 PageID #:

4074
830

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 831 of 860 PageID #:

4075
831

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 832 of 860 PageID #:

4076
832

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 833 of 860 PageID #:

4077
833

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 834 of 860 PageID #:

4078
834

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 835 of 860 PageID #:

4079
835

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

[24.4] a filter having an input 

coupled to the output of the 

first down-converter and the 

output of the second downconverter, and in accordance 

therewith, the filter receives 

802.11n D2.0 discloses “a filter having an input coupled to the output of the first down-converter and 

the output of the second down-converter, and in accordance therewith, the filter receives the first and 

second down-converted signals.” See, e.g.: 

high throughput duplicate format (HT duplicate format): A PPDU format of the HT PHY in which signals in two halves of the 

occupied channel width contain the same information. This is the HT mode that supports the lowest rate.

See, e.g., 802.11n D2.0 § 3.n19

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 836 of 860 PageID #:

4080
836

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

the first and second downconverted signals.

non-HT duplicate: A mode of operation of the PHY that duplicates a 20 MHz non-HT transmission in two adjacent 20 MHz channels, 

allowing a non-HT BSS on either channel to receive the transmission.

See, e.g., 802.11n D2.0 § 3.n32

9.13.3.1 General

HT transmissions shall be protected if there are other STAs (HT or non-HT) that cannot interpret HT transmissions

correctly. The fields Operating Mode and Non-greenfield STAs Present in the HT Information element

within the Beacon and Probe Response frames are used to determine if protection is required for

transmission.

When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required since all associated HT stations in the BSS are capable of decoding HT mixed format and HT

greenfield format transmissions.

When the Operating Mode field is set to 0 or 2 and the Non-greenfield STAs Present field is set to 1, HT transmissions that use the 

greenfield preamble shall be protected.

NOTE 1—When the Operating Mode field is set to 0 or 2 and Non-greenfield STAs Present field is set to 0, no protection

is required for 40 MHz transmissions since enough of the preamble is sent on both 20 MHz halves of the 40 MHz

transmission to ensure that a 20 MHz STA is able to decode the preamble and infer the duration of the transmission.

NOTE 2—When the BSS is operating in the 2.4 GHz band and when the Operating Mode field is set to 0 or 2, there are no non -HT 

STAs in the BSA and thus the Use Protection subfield of the ERP Information Element is set to 0.

When the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set

to 0, HT transmissions may be protected accoding to implementation dependent criteria. When the Operating

Mode field is set to 1, the Use Protection field in the ERP Information Element is set to 0 and the Non -greenfield

STAs Present field is set to 1, HT transmissions using HT greenfield format shall be protected. When

the Operating Mode field is set to 1 and the Use Protection field in the ERP Information Element is set to 1,

HT transmissions shall be protected using the mechanisms described in Table n49 (Protection requirements

for Operating Modes of 1 and 3)

When the Operating Mode field is set to 3, HT transmissions shall be protected. The type of protection that

is required depends on the type of transmission as well as the type of the non -HT STAs that are present in the

BSS. The specific mechanisms that are to be used for protection for Operating Mode set to 3 a re described in

Table n49 (Protection requirements for Operating Modes of 1 and 3)

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 837 of 860 PageID #:

4081
837

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

If the transmission requires protection and Use Protection field within the ERP Information Element is set to

0 or the ERP Information Element is not present in the Beacon, HT transmissions shall be protected in one of

the following ways:

a) Control frames such as RTS/CTS or CTS-to-self prior to the HT transmissions:

1) For 20 MHz transmissions, use the rates defined in Clause 17 or Clause 19

2) For 40 MHz transmissions, use the non-HT duplicate frames defined in Clause 20.

NOTE—The rate for protection frames are selected based on the rules described in 9.6.3.1 (Rate selection for

control frames that initialize a TXOP) and 9.6.3.2 (Rate selection for control frames that are not control

response frames).

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 838 of 860 PageID #:

4082
838

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

b) Using a non-HT preamble, transmit first a PPDU that requires a response frame. The remaining

TXOP following the first PPDU exchange may contain GF and/or RIFS sequences.

c) L-SIG TXOP protection

d) Using a mixed format preamble, transmit first a PPDU that requires a response that is sent as a non -

HT frame or non-HT duplicate frame. The remaining TXOP following the first PPDU exchange

may contain HT greenfield format and/or RIFS sequences.

See, e.g., 802.11n D2.0 § 9.13.3.1

11.16 Phased Coexistence Operation

The following definitions apply in this subclause:

— A PCO-capable AP is an HT AP that sets the PCO field in the HT Extended Capabilities field to the

value 1.

— A PCO AP is an HT AP that is operating PCO.

— A PCO BSS is an HT BSS that is operated by a PCO AP.

— A PCO-capable non-AP STA is an HT non-AP STA that sets the PCO field in the HT Extended

Capabilities field to the value 1.

— A PCO non-AP STA is an HT non-AP STA that is associated with a PCO BSS and following PCO.

— A PCO-capable STA is either a PCO-capable AP or a PCO-capable non-AP STA.

— A PCO STA is either a PCO AP or a PCO non-AP STA.

— A non-PCO-capable 20/40 STA is a 20/40 capable STA that sets the PCO field in the HT Extended

Capabilities field to the value 0.

Phased Coexistence Operation (PCO) is an optional coexistence mechanism in which a PCO AP divides time

into alternating 20 MHz and 40 MHz phases (see Figure n61 (Phased Coexistence Operation)). The PCO AP

reserves the 20 MHz primary channel and the 20 MHz secondary channel in turn to start the 40 MHz phase

and resets the NAV in the 20 MHz channels in the opposite order to start the 20 MHz phase. Due to the protection

of the 40 MHz period in both channels, it is tolerant of overlapping BSSs on both 20 MHz halves of

a 40 MHz channel.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 839 of 860 PageID #:

4083
839

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

A PCO STA that does not know the current PCO phase shall transmit in a 20 MHz PPDU.

During the 40 MHz phase, a PCO STA shall transmit data frames using a 40 MHz HT PPDU and control

frames using a non-HT duplicate or a 40 MHz HT PPDU, except that any CF-End frame shall be sent using

a 40 MHz HT PPDU only. During the 40 MHz phase, protection is not required as in a 40 MHz BSS with

Supported Channel Width Set field in the HT Capabilities Info field set to 1 and Operating Mode field in the

HT Information element set to the value 0. A PCO STA shall update its NAV using Duration/ID field information

from any frame received in the primary channel or 40 MHz channel.

During the 20 MHz phase, a PCO STA shall only transmit frames using a 20 MHz (HT or non -HT) PPDU.

The protection of a PCO STA during the 20 MHz phase is the same as protection in a 20 MHz BSS.

A non-PCO-capable 20/40 STA regards the PCO BSS as 20/40 MHz BSS. The protection of a non -PCO-capable

20/40 STA that associates with the PCO BSS is the same as protection in a 20/40 MHz BSS.

The PCO Transition Time field in the HT Extended Capabilities field is measured from the end of the PPDU

carrying the Set PCO Phase frame. The PCO STA shall be able to receive a PPDU using the new channel

width no later than the value specified in the PCO Transition Time field after the end of the PPDU carrying

the Set PCO Phase frame.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 840 of 860 PageID #:

4084
840

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 11.16

20.1 Introduction

Clause 20 (High Throughput (HT) PHY specification ) specifies the PHY Entity for a high throughput (HT)

orthogonal frequency division multiplexing (OFDM) system. The HT STA shall be compliant with PHY

specifications as defined in Clause 17 for operation in the 5 GHz bands, and Clauses 18 and 19 for operation

in the 2.4 GHz bands . The HT features are applicable to operation in either the 2.4 GHz band or the 5 GHz

bands, or both, as specified in 20.3.14 (Channel numbering and channelization). The HT OFDM PHY is

based on the OFDM PHY defined in Clause 17, with extensibility up to 4 spatial streams, operating in 20

MHz bandwidth. Additionally, transmission using 1 to 4 spatial streams is also defined for operation in 40

MHz bandwidth. These features are capable of supporting data rates up to 600 Mb/s (4 spatial streams, 40

MHz bandwidth). The HT OFDM PHY data subcarriers are modulated using binary phase shift keying

(BPSK), quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16-QAM), or 64-

QAM. Forward error correction coding (convolutional coding) is used with a coding rate of 1/2, 2/3, 3/4, or

5/6. Low-density parity-check (LDPC) codes are added . Other features at both transmit and receive sides are

400 ns short guard interval (GI), transmit beamforming, HT greenfield format , space-time block codes (STBC),

and 40 MHz operation. The HT OFDM PHY defined in Clause 20 is mandatory for all equal modulation

rates specified for 1 and 2 spatial streams (MCSs 0 through 15) at an AP and for 1 spatial stream (MCSs 0

through 7) at a STA using 20 MHz channel width. Support for all other MCSs in 2 to 4 spatia l streams in 20

MHz, and for all MCSs in 1-4 spatial streams using 40 MHz channel width is optional. The maximum MPDU

length is extended to 65535 octets.

The HT PHY supports non-HT operation in the 2.4 GHz band as defined by Clause 19. It supports non -HT

operation in the 5 GHz bands in as defined by Clause 17.

See, e.g., 802.11n D2.0 § 20.1

20.1.3 PPDU Formats

The PPDU format transmitted by an HT STA is determined by the TXVECTOR FORMAT,

CH_BANDWIDTH , CH_OFFSET and MCS parameters as defined in this subclause.

The FORMAT parameter determines the overall structure of the PPDU as follows:

— Non-HT format: packets of this format are structured according to the Clause 17 (OFDM) or 19

(ERP) specification. Support for Non-HT Format is mandatory.

— HT mixed format: packets of this format contain a preamble compatible with the non-HT receivers.

The non-HT Short Training Field (L-STF), the non-HT Long Training Field (L-LTF) and the nonHT SIGNAL field are defined so they can be decoded by non-HT Clause 17 and 19 STAs. The rest

of the packet cannot be decoded by Clause 17 or Clause 19 STAs. Support for HT mixed format is

mandatory.

— HT greenfield format: HT packets of this format do not contain a non-HT compatible part. Support

for HT greenfield format is optional. An HT STA that does not support the reception of an HT

greenfield format packet shall be able to detect that an HT greenfield format packet is an HT transmission

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 841 of 860 PageID #:

4085
841

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

(as opposed to a non-HT transmission). In this case the receiver shall decode the HT-SIG

and determine if the HT-SIG cyclic redundancy check (CRC) passes.

The operation of the PHY in the frequency domain is determined by the CH_BANDWIDTH and

CH_OFFSET parameters. Table n55 (PPDU format as a function of CH_BANDWIDTH and CH_OFFSET

parameters) shows the combination of CH_BANDWIDTH and CH_OFFSET parameters that are supported.

Support of 20 MHz Non-HT Format and 20 MHz HT Format with one and two spatial streams is mandatory

at APs. Support of 20 Mhz Non-HT Format and 20 MHz HT Format with one spatial stream is mandatory

the non-AP STAs.

See, e.g., 802.11n D2.0 § 20.1.3

20.3.2 PLCP frame format

Two formats are defined for the PLCP (PHY Layer Convergence Protocol): HT mixed format and greenfield

format. These two formats are called HT formats. Figure n62 (PPDU frame format) shows the non -HT format1

and the HT formats. There is also an HT duplicate format (specified in 20.3.10.10.4) used for MCS 32

that provides the lowest rate in a 40 MHz channel. In addition to the HT formats, there is a non -HT duplicate

format (specified in 20.3.10.11 (Non-HT duplicate transmission)) that duplicates the 20 MHz non-HT packet

in two 20 MHz halves of a 40 MHz channel.

1 The Non-HT format is shown related to the terminology of this subclause. The Non-HT PPDU format is defined in 17.3.3 and 17.3.2.

See, e.g., 802.11n D2.0 § 20.3.2

m) Divide the complex number string for each of the resulting NSS spatial streams into groups of NSD

complex numbers, where the value of NSD is determined from the CH_OFFSET field of TXVECTOR

and the CH_BANDWIDTH field of TXVECTOR. Each such group is associated with one

OFDM symbol in one spatial stream. In each group, the complex numbers are indexed 0 to NSD -1

and mapped hereafter onto OFDM subcarriers as described in 20.3.10.10.2 (Transmission in 20

MHz HT format), 20.3.10.10.3 (Transmission in 40 MHz HT Format), 20.3.10.10.4 (Transmission

in HT duplicate format), and 20.3.10.11 (Non-HT duplicate transmission).

See, e.g., 802.11n D2.0 § 20.3.4.m

For each group NST of subcarriers and each of the NTX transmit chains, convert the subcarriers to

time domain using inverse Fourier transform. Prepend to the Fourier-transformed waveform a circular

extension of itself thus forming a GI, and truncate the resulting periodic waveform to a single

OFDM symbol length by applying time domain windowing. Determine the length of the guar d interval

according to the SHORT_GI field in the TXVECTOR. Refer to 20.3.10.10 (OFDM modulation)

and 20.3.10.11 (Non-HT duplicate transmission) for details.

See, e.g., 802.11n D2.0 § 20.3.4.r

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 842 of 860 PageID #:

4086
842

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Append the OFDM symbols associated with each transmit chain one after another, starting after the

final field of the PLCP preamble. Refer to 20.3.2 (PLCP frame format) and 20.3.7 (Mathematical

description of signals) for details.

See, e.g., 802.11n D2.0 § 20.3.4.s

Up-convert the resulting complex baseband waveform associated with each transmit chain to an RF

signal according to the center frequency of the desired channel and transmit. Refer to 20.3.7 (Mathematical

description of signals) for details. The transmit chains are connected to antenna elements

according to ANTENNA_SET of the TXVECTOR if antenna selection is applied.

See, e.g., 802.11n D2.0 § 20.3.4.t

20.3.22 PLCP transmit procedure

There are three options for transmit PLCP procedure. The first two options, for which typical transmit proce -

dures are shown in Figure n81 (PLCP transmit procedure (HT mixed format PPDU)) and Figure n82 (PLCP

transmit procedure (HT greenfield format PPDU)), are selected if the FORMAT field of PHY-TXSTART.request(

TXVECTOR) is set to HT_MF or HT_GF respectively. Thes e transmit procedures do not describe the

operation of optional features, such as LDPC. The third option is to follow the transmit procedure as in Clause

17 or 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is set to NON_HT, CW

indicates NON_HT_CBW20, and NON_HT_MODULATION indicates OFDM, follow the transmit procedure

as in Clause 17. If the FORMAT field is set to NON_HT, CH_BANDWIDTH indicates

NON_HT_CBW20, and NON_HT_MODULATION indicates other than OFDM, follow the transmit pro cedure

as in Clause 19. And furthermore, if the FORMAT field is set to NON_HT and CH_BANDWIDTH

indicates NON_HT_CBW40, follow the transmit procedure as in Clause 17 duplicated on both channels. In

all these options, in order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity

shall be in the transmit state. Further, the PHY shall be set to operate at the appropriate frequency through

station management via the PLME. Other transmit parameters, such as MCS Coding types and TX power, are

set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2 (TXVECTOR

and RXVECTOR parameters).

A clear channel shall be indicated by PHY-CCA.indication(IDLE). The MAC considers this indication before

issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the

PHYTXSTART.request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request

are specified in Table n56 (TXVECTOR and RXVECTOR parameters).

The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:

— PMD_TXPWRLVL

— PMD_TX_PARAMETERS

— PMD_EXPANSIONS_MAT

— PMD_EXPANSIONS_MAT_ON

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 843 of 860 PageID #:

4087
843

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start,

based on the parameters passed in the PHY-TXSTART.request primitive. The data shall then be exchanged

between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the

MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,

the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be

based on the LDPC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation

rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2 (PLCP

frame format).

The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE

field and PSDU are encoded by the encoder selected by the LDPC_CODING, CH_BANDWIDTH, and

MCS parameters of the TXVECTOR as described in 20.3.3 (Transmitter block diagram). At the PMD layer,

the data octets are sent in bit 0–7 order and presented to the PHY through PMD_DATA.request primitives.

Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHYTXSTART

shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after

the transmission of the final bit of the last PSDU octet, according to the number supplied in the LENGTH

field.

The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART

shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive

from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be stuffed

to make the C-PSDU length multiples of the OFDM symbol.

In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay

spread.

A typical state machine implementation of the transmit PLCP is provided in Figure n83 (PLCP transmit state

machine). Requests (.req) and confirmations(.confirm) are issued once per state as shown. This state machine

does not describe the operation of optional features, such as LDPC or STBC.

See, e.g., 802.11n D2.0 § 20.3.22

20.3.6 Timing related parameters

Table n58 (Timing related constants) defines the timing related parameters.

See, e.g., 802.11n D2.0 § 20.3.6

20.3.7 Mathematical description of signals

For the description of the convention on mathematical description of signals see 17.3.2.4

In the case of either a 20 MHz Non-HT Format transmission or a 20 MHz HT Format transmission, the channel

is divided into 64 sub-carriers. In the 20 MHz Non-HT Format, the signal is transmitted on sub-carriers -

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 844 of 860 PageID #:

4088
844

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

26 to -1 and 1 to 26, with 0 being the center (DC) carrier. In the 20 MHz HT Format, the signal is transmitted

on sub-carriers -28 to -1 and 1 to 28.

In the case of the 40 MHz HT Format, two adjacent 20 MHz channels are used. The channel is divided into

128 sub-carriers. The signal is transmitted on sub-carriers -58 to -2 and 2 to 58.

In the case of 40 MHz HT Upper Format or 40 MHz HT Lower Format, the upper or lower 20 MHz channel

is divided into 64 sub-carriers. The signal is transmitted on sub-carriers -60 to -4 in the case of a 40 MHz HT

Lower Format transmission and on sub-carriers 4 to 60 in the case of a 40 MHz HT Upper Format transmission.

In the case of the HT duplicate and Non-HT duplicate formats, the same data are transmitted over two adjacent

20 MHz channels. In this case, the 40 MHz channel is divided into 128 sub -carriers and the data are transmitted

on carriers -58 to -6 and 6 to 58.

The transmitted signal is described in complex base-band signal notation. The actual transmitted signal is related

to the complex baseband signal by the following relation:

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 845 of 860 PageID #:

4089
845

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 846 of 860 PageID #:

4090
846

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 847 of 860 PageID #:

4091
847

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.7 and Figure n65

20.3.8 Transmission in the upper/lower 20 MHz of a 40 MHz channel

When transmitting in the upper/lower 20 MHz portion of a 40 MHz channel, the mathematical definition of

transmission shall follow that of a 20 MHz channel with in Equation (20-1) replaced by .

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 848 of 860 PageID #:

4092
848

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.8

20.3.9.4.3 The HT SIGNAL field

The HT SIGNAL field is used to carry information required to interpret the HT packet formats. The fields of

the HT SIGNAL field are described in Table n63 (Fields of HT SIGNAL field).

The structure of the HT-SIG1 and HT-SIG2 fields is defined in Figure n67 (Format of HT-SIG1 and HTSIG2).

...

See, e.g., 802.11n D2.0 § 20.3.9.4.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 849 of 860 PageID #:

4093
849

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.2

See, e.g., 802.11n D2.0 § 20.3.10.10.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 850 of 860 PageID #:

4094
850

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.10.4

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 851 of 860 PageID #:

4095
851

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.10.11

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 852 of 860 PageID #:

4096
852

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.1

See, e.g., 802.11n D2.0 § 20.3.14.2

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 853 of 860 PageID #:

4097
853

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.14.3

20.3.20.2 Spectral flatness

In a 20 MHz channel and in corresponding 20 MHz transmission in a 40 MHz channel, the average energy

of the constellations in each of the spectral lines –16 to –1 and +1 to +16 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –28 to –17

and +17 to +28 shall deviate no more than +2/–4 dB from the average energy of spectral lines –16 to –1 and

+1 to +16.

In a 40 MHz transmission (excluding HT duplicate format and non-HT duplicate format) the average energy

of the constellations in each of the spectral lines –42 to –2 and +2 to +42 shall deviate no more than ± 2 dB

from their average energy. The average energy of the constellations in each of the spectral lines –43 to –58

and +43 to +58 shall deviate no more than +2/–4 dB from the average energy of spectral lines –42 to –2 and

+2 to +42.

In HT duplicate format and non-HT duplicate format the average energy of the constellations in each of the

spectral lines -42 to -33, -31 to -6, +6 to +31, and +33 to +42 shall deviate no more than ± 2 dB from their

average energy. The average energy of the constellations in each of the spectral lines -43 to -58 and +43 to

+58 shall deviate no more than +2/-4 dB from the average energy of spectral lines -42 to -33, -31 to -6, +6

to +31, and +33 to +42.

See, e.g., 802.11n D2.0 § 20.3.20.2

20.3.20.3 Transmit power

The maximum allowable transmit power by regulatory domain is defined in Annex I.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 854 of 860 PageID #:

4098
854

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 § 20.3.20.3

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 855 of 860 PageID #:

4099
855

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 856 of 860 PageID #:

4100
856

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n55

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 857 of 860 PageID #:

4101
857

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 858 of 860 PageID #:

4102
858

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Table n58

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 859 of 860 PageID #:

4103
859

Claim 24 of the ’802 Patent Prior Art Reference – 802.11n D2.0

See, e.g., 802.11n D2.0 Figure n65

Furthermore, this claim element is obvious in light of 802.11n D2.0 itself, when combined with any 

of the other references as charted for this claim element in Exs. A-1–A-31, First Supplemental Ex. AObviousness Chart, and/or when combined with the knowledge of one of ordinary skill in the art. 

Motivations to combine may come from the knowledge of the person of ordinary skill themselves, or 

from the known problems and predictable solutions as embodied in these references. Further 

motivations to combine references and additional details may be found in the Cover Pleading and 

First Supplemental Ex. A-Obviousness Chart.

Case 2:23-cv-00285-JRG-RSP Document 59-12 Filed 07/11/24 Page 860 of 860 PageID #:

4104