Patent Description:
The present disclosure relates generally to wireless communication systems, and more particularly to data transmission and reception over multiple communication channels.

Wireless local area networks (WLANs) have evolved rapidly over the past two decades, and development of WLAN standards such as the Institute for Electrical and Electronics Engineers (IEEE) <NUM> Standard family has improved single-user peak data rates. One way in which data rates have been increased is by increasing the frequency bandwidth of communication channels used in WLANs. For example, the IEEE <NUM>. 11n Standard permits aggregation of two <NUM> sub-channels to form a <NUM> aggregate communication channel, whereas the more recent IEEE <NUM> ax Standard permits aggregation of up to eight <NUM> sub-channels to form up to <NUM> aggregate communication channels. Work has now begun on a new iteration of the IEEE <NUM> Standard, which is referred to as the IEEE <NUM> The Standard, or Extremely High Throughput (EHT) WLAN. The IEEE <NUM>. 11be Standard may permit aggregation of as many as sixteen <NUM> sub-channels (or perhaps even more) to form up to <NUM> aggregate communication channels (or perhaps even wider aggregate communication channels). Additionally, the IEEE <NUM>. 11be Standard may permit aggregation <NUM> sub-channels in different frequency segments (for example, separated by a gap in frequency) to form a single aggregate channel. Further, the IEEE <NUM>1be Standard may permit aggregation <NUM> sub-channels in different radio frequency (RF) bands to form a single aggregate channel.

The current draft of the IEEE <NUM>. 11ax Standard (referred to herein as "the IEEE <NUM> ax Standard" for simplicity) defines an "<NUM>+<NUM>" transmission mode in which a communication device simultaneously transmits in two <NUM> channel segments within a single radio frequency (RF) band. The two <NUM> channel segments may be separated in frequency within the single RF band. Transmissions in the two <NUM> channel segments are synchronized, i.e., the transmissions begin at a same start time and end at a same end time. <CIT> describes a UE using different carriers wherein the timeline is divided into UL and DL slots. The UE is synchronized when all its carriers are in UL mode or in DL mode, while it is unsynchronized when one carrier is in UL mode and another one is in DL mode.

In an embodiment, a method for simultaneously transmitting in a plurality of frequency segments comprises: determining, at a communication device, whether simultaneous transmissions in a first frequency segment and a second frequency segment are to be synchronized in time; in response to the communication device determining that simultaneous transmissions in the first frequency segment and the second frequency segment are to be synchronized in time, transmitting a first packet in the first frequency segment beginning at a first time, and transmitting a second packet in the second frequency segment beginning at the first time; and in response to the communication device determining that simultaneous transmissions in the first frequency segment and the second frequency segment are to be unsynchronized in time, transmitting a third packet in the first frequency segment beginning at a second time, and transmitting a fourth packet in the second frequency segment beginning at a third time that is different than the second time.

In another embodiment, a communication device comprises: a wireless network interface device comprising: one or more integrated circuit (IC) devices, and a plurality of radio frequency (RF) radios including at least a first RF radio and a second RF radio, wherein the plurality of RF radios are implemented at least partially on the one or more IC devices. The one or more IC devices are configured to: determine whether simultaneous transmissions in a first frequency segment and a second frequency segment are to be synchronized; and in response to the communication device determining that simultaneous transmissions in the first frequency segment and the second frequency segment are to be synchronized, control the first RF radio to transmit a first packet in the first frequency segment beginning at a first time, and control the second RF radio to transmit a second packet in the second frequency segment beginning at the first time. The one or more IC devices are further configured to: in response to the communication device determining that simultaneous transmissions in the first frequency segment and the second frequency segment are to be unsynchronized, control the first RF radio to transmit a third packet in the first frequency segment beginning at a second time, and control the second RF radio to transmit a fourth packet in the second frequency segment beginning at a third time that is different than the second time.

A next generation wireless local area network (WLAN) protocol (e.g., the IEEE <NUM> The Standard, sometimes referred to as the Extremely High Throughput (EHT) WLAN Standard) may permit simultaneous transmissions in different channel segments. The different channel segments may be in a single radio frequency (RF) band or in different RF bands. The different channel segments may have a same bandwidth or different bandwidths.

The IEEE <NUM>. 11ax Standard permits synchronized transmissions (i.e., the transmissions begin at a same start time and end at a same end time) in two <NUM> channel segments (referred to as an "<NUM>+<NUM>) transmission), and requires that the two <NUM> channel segments be idle at the same time in order for the synchronized transmissions to proceed. Finding times when both <NUM> channel segments are idle, however, is often difficult for many WiFi deployments, thus limiting the usefulness of the <NUM>+<NUM> transmission mode.

In some embodiments described below, a communication device is configured to transmit synchronously in different channel segments (e.g., the transmissions begin at a same start time) in some scenarios, and to transmit asynchronously in different channel segments (e.g., the transmissions are not required to begin at a same start time) in other scenarios. Transmitting asynchronously in the different channel segments does not require that the different channel segments be idle at a same time, at least in some embodiments, thus permitting simultaneous use of the different channel segments more frequently as compared to a communication system that always requires that transmissions in different channel segments be synchronous (e.g., the transmissions begin at a same start time) and that the different channel segments be idle at a same time, at least in some embodiments and/or situations.

<FIG> is a block diagram of an example wireless local area network (WLAN) <NUM>, according to an embodiment. The WLAN <NUM> includes an access point (AP) <NUM> that comprises a host processor <NUM> coupled to a network interface device <NUM>. The network interface device <NUM> includes one or more medium access control (MAC) processors <NUM> (sometimes referred to herein as "the MAC processor <NUM>" for brevity) and one or more physical layer (PHY) processors <NUM> (sometimes referred to herein as "the PHY processor <NUM>" for brevity). The PHY processor <NUM> includes a plurality of transceivers <NUM>, and the transceivers <NUM> are coupled to a plurality of antennas <NUM>. Although three transceivers <NUM> and three antennas <NUM> are illustrated in <FIG>, the AP <NUM> includes other suitable numbers (e.g., <NUM>, <NUM>, <NUM>, <NUM>, etc.) of transceivers <NUM> and antennas <NUM> in other embodiments. In some embodiments, the AP <NUM> includes a higher number of antennas <NUM> than transceivers <NUM>, and antenna switching techniques are utilized.

The network interface device <NUM> is implemented using one or more integrated circuits (ICs) configured to operate as discussed below. For example, the MAC processor <NUM> may be implemented, at least partially, on a first IC, and the PHY processor <NUM> may be implemented, at least partially, on a second IC. As another example, at least a portion of the MAC processor <NUM> and at least a portion of the PHY processor <NUM> may be implemented on a single IC. For instance, the network interface device <NUM> may be implemented using a system on a chip (SoC), where the SoC includes at least a portion of the MAC processor <NUM> and at least a portion of the PHY processor <NUM>.

In an embodiment, the host processor <NUM> includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a random access memory (RAM), a read-only memory (ROM), a flash memory, etc. In an embodiment, the host processor <NUM> may be implemented, at least partially, on a first IC, and the network device <NUM> may be implemented, at least partially, on a second IC. As another example, the host processor <NUM> and at least a portion of the network interface device <NUM> may be implemented on a single IC.

In various embodiments, the MAC processor <NUM> and/or the PHY processor <NUM> of the AP <NUM> are configured to generate data units, and process received data units, that conform to a WLAN communication protocol such as a communication protocol conforming to the IEEE <NUM> Standard or another suitable wireless communication protocol. For example, the MAC processor <NUM> may be configured to implement MAC layer functions, including MAC layer functions of the WLAN communication protocol, and the PHY processor <NUM> may be configured to implement PHY functions, including PHY functions of the WLAN communication protocol. For instance, the MAC processor <NUM> may be configured to generate MAC layer data units such as MAC service data units (MSDUs), MAC protocol data units (MPDUs), aggregate MPDUs (A-MPDUs), etc., and provide the MAC layer data units to the PHY processor <NUM>. MPDUs and A-MPDUs exchanged between the MAC processor <NUM> and the PHY processor <NUM> are sometimes referred to as physical layer convergence procedure (PLCP) (or simply "PHY") service data units (PSDUs).

The PHY processor <NUM> may be configured to receive MAC layer data units (or PSDUs) from the MAC processor <NUM> and encapsulate the MAC layer data units (or PSDUs) to generate PHY data units such as PLCP (or "PHY") protocol data units (PPDUs) for transmission via the antennas <NUM>. Similarly, the PHY processor <NUM> may be configured to receive PHY data units that were received via the antennas <NUM>, and extract MAC layer data units encapsulated within the PHY data units. The PHY processor <NUM> may provide the extracted MAC layer data units to the MAC processor <NUM>, which processes the MAC layer data units.

PHY data units are sometimes referred to herein as "packets", and MAC layer data units are sometimes referred to herein as "frames".

In connection with generating one or more radio frequency (RF) signals for transmission, the PHY processor <NUM> is configured to process (which may include modulating, filtering, etc.) data corresponding to a PPDU to generate one or more digital baseband signals, and convert the digital baseband signal(s) to one or more analog baseband signals, according to an embodiment. Additionally, the PHY processor <NUM> is configured to upconvert the one or more analog baseband signals to one or more RF signals for transmission via the one or more antennas <NUM>.

In connection with receiving one or more signals RF signals, the PHY processor <NUM> is configured to downconvert the one or more RF signals to one or more analog baseband signals, and to convert the one or more analog baseband signals to one or more digital baseband signals. The PHY processor <NUM> is further configured to process (which may include demodulating, filtering, etc.) the one or more digital baseband signals to generate a PPDU.

The PHY processor <NUM> includes amplifiers (e.g., a low noise amplifier (LNA), a power amplifier, etc.), a radio frequency (RF) downconverter, an RF upconverter, a plurality of filters, one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs), one or more discrete Fourier transform (DFT) calculators (e.g., a fast Fourier transform (FFT) calculator), one or more inverse discrete Fourier transform (IDFT) calculators (e.g., an inverse fast Fourier transform (IFFT) calculator), one or more modulators, one or more demodulators, etc..

The PHY processor <NUM> is configured to generate one or more RF signals that are provided to the one or more antennas <NUM>. The PHY processor <NUM> is also configured to receive one or more RF signals from the one or more antennas <NUM>.

The MAC processor <NUM> is configured to control the PHY processor <NUM> to generate one or more RF signals by, for example, providing one or more MAC layer data units (e.g., MPDUs) to the PHY processor <NUM>, and optionally providing one or more control signals to the PHY processor <NUM>, according to some embodiments. In an embodiment, the MAC processor <NUM> includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a read ROM, a flash memory, etc. In another embodiment, the MAC processor <NUM> includes a hardware state machine.

The MAC processor <NUM> includes, or implements, a multi-channel segment transmission controller <NUM> that is configured to determine when transmissions in different channel segments are to be transmitted synchronously (e.g., the transmissions begin at a same start time), and when transmissions in different channel segments can be transmitted asynchronously (e.g., the transmissions are not required to begin at a same start time), according to an embodiment. When transmissions in different channel segments are to be transmitted synchronously, the multi-channel segment transmission controller <NUM> prompts the PHY processor <NUM> to begin the transmissions in the different channel segments at a same time, according to some embodiments. When transmissions in different channel segments are to be transmitted asynchronously, the multi-channel segment transmission controller <NUM> prompts the PHY processor <NUM> to begin the transmissions in the different channel segments at different times, according to some embodiments.

In an embodiment, the multi-channel segment transmission controller <NUM> is implemented by a processor executing machine readable instructions stored in a memory, where the machine readable instructions cause the processor to perform acts described in more detail below. In another embodiment, the multi-channel segment transmission controller <NUM> additionally or alternatively comprises hardware circuity that is configured to perform acts described in more detail below. In some embodiments, the hardware circuitry comprises one or more hardware state machines that are configured to perform acts described in more detail below.

The WLAN <NUM> includes a plurality of client stations <NUM>. Although three client stations <NUM> are illustrated in <FIG>, the WLAN <NUM> includes other suitable numbers (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc.) of client stations <NUM> in various embodiments. The client station <NUM>-<NUM> includes a host processor <NUM> coupled to a network interface device <NUM>. The network interface device <NUM> includes one or more MAC processors <NUM> (sometimes referred to herein as "the MAC processor <NUM>" for brevity) and one or more PHY processors <NUM> (sometimes referred to herein as "the PHY processor <NUM>" for brevity). The PHY processor <NUM> includes a plurality of transceivers <NUM>, and the transceivers <NUM> are coupled to a plurality of antennas <NUM>. Although three transceivers <NUM> and three antennas <NUM> are illustrated in <FIG>, the client station <NUM>-<NUM> includes other suitable numbers (e.g., <NUM>, <NUM>, <NUM>, <NUM>, etc.) of transceivers <NUM> and antennas <NUM> in other embodiments. In some embodiments, the client station <NUM>-<NUM> includes a higher number of antennas <NUM> than transceivers <NUM>, and antenna switching techniques are utilized.

The network interface device <NUM> is implemented using one or more ICs configured to operate as discussed below. For example, the MAC processor <NUM> may be implemented on at least a first IC, and the PHY processor <NUM> may be implemented on at least a second IC. As another example, at least a portion of the MAC processor <NUM> and at least a portion of the PHY processor <NUM> may be implemented on a single IC. For instance, the network interface device <NUM> may be implemented using an SoC, where the SoC includes at least a portion of the MAC processor <NUM> and at least a portion of the PHY processor <NUM>.

In an embodiment, the host processor <NUM> includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the host processor <NUM> may be implemented, at least partially, on a first IC, and the network device <NUM> may be implemented, at least partially, on a second IC. As another example, the host processor <NUM> and at least a portion of the network interface device <NUM> may be implemented on a single IC.

In various embodiments, the MAC processor <NUM> and the PHY processor <NUM> of the client device <NUM>-<NUM> are configured to generate data units, and process received data units, that conform to the WLAN communication protocol or another suitable communication protocol. For example, the MAC processor <NUM> may be configured to implement MAC layer functions, including MAC layer functions of the WLAN communication protocol, and the PHY processor <NUM> may be configured to implement PHY functions, including PHY functions of the WLAN communication protocol. The MAC processor <NUM> may be configured to generate MAC layer data units such as MSDUs, MPDUs, etc., and provide the MAC layer data units to the PHY processor <NUM>. The PHY processor <NUM> may be configured to receive MAC layer data units from the MAC processor <NUM> and encapsulate the MAC layer data units to generate PHY data units such as PPDUs for transmission via the antennas <NUM>. Similarly, the PHY processor <NUM> may be configured to receive PHY data units that were received via the antennas <NUM>, and extract MAC layer data units encapsulated within the PHY data units. The PHY processor <NUM> may provide the extracted MAC layer data units to the MAC processor <NUM>, which processes the MAC layer data units.

The PHY processor <NUM> is configured to downconvert one or more RF signals received via the one or more antennas <NUM> to one or more baseband analog signals, and convert the analog baseband signal(s) to one or more digital baseband signals, according to an embodiment. The PHY processor <NUM> is further configured to process the one or more digital baseband signals to demodulate the one or more digital baseband signals and to generate a PPDU. The PHY processor <NUM> includes amplifiers (e.g., an LNA, a power amplifier, etc.), an RF downconverter, an RF upconverter, a plurality of filters, one or more ADCs, one or more DACs, one or more DFT calculators (e.g., an FFT calculator), one or more IDFT calculators (e.g., an IFFT calculator), one or more modulators, one or more demodulators, etc..

The MAC processor <NUM> is configured to control the PHY processor <NUM> to generate one or more RF signals by, for example, providing one or more MAC layer data units (e.g., MPDUs) to the PHY processor <NUM>, and optionally providing one or more control signals to the PHY processor <NUM>, according to some embodiments. In an embodiment, the MAC processor <NUM> includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the MAC processor <NUM> includes a hardware state machine.

In some embodiments, the MAC processor <NUM> includes a multi-channel segment transmission controller (not shown) the same as or similar to the multi-channel segment transmission controller <NUM> of the AP <NUM>. For example, the client station <NUM>-<NUM> is configured transmit synchronously in different channel segments (e.g., the transmissions begin at a same start time) in some scenarios, and to transmit asynchronously in different channel segments (e.g., the transmissions are not required to begin at a same start time) in other scenarios, according to some embodiments.

In an embodiment, each of the client stations <NUM>-<NUM> and <NUM>-<NUM> has a structure that is the same as or similar to the client station <NUM>-<NUM>. Each of the client stations <NUM>-<NUM> and <NUM>-<NUM> has the same or a different number of transceivers and antennas. For example, the client station <NUM>-<NUM> and/or the client station <NUM>-<NUM> each have only two transceivers and two antennas (not shown), according to an embodiment.

In an embodiment, multiple different frequency bands within the RF spectrum are employed for signal transmissions within the WLAN <NUM>. In an embodiment, different communication devices (i.e., the AP <NUM> and the client stations <NUM>) may be configured for operation in different frequency bands. In an embodiment, at least some communication devices (e.g., the AP <NUM> and the client station <NUM>) in the WLAN <NUM> may be configured for simultaneous operation over multiple different frequency bands. Exemplary frequency bands include, a first frequency band corresponding to a frequency range of approximately <NUM>-<NUM> ("<NUM> band"), and a second frequency band corresponding to a frequency range of approximately <NUM>-<NUM> ("<NUM> band") of the RF spectrum. In an embodiment, one or more communication devices within the WLAN may also be configured for operation in a third frequency band in the <NUM>-<NUM> range ("<NUM> band"). Each of the frequency bands comprise multiple component channels which may be combined within the respective frequency bands to generate channels of wider bandwidths, as described above. In an embodiment corresponding to multi-channel segment operation over a first channel segment and a second channel segment, the first channel segment and the second channel segment may be in separate frequency bands, or within a same frequency band. In some embodiments, at least one communication device (e.g., at least the AP <NUM>) in the WLAN <NUM> is configured for simultaneous operation over any two of the <NUM> band, the <NUM> band, and the <NUM> band. In some embodiments, at least one communication device (e.g., at least the AP <NUM>) in the WLAN <NUM> is configured for simultaneous operation over all three of the <NUM> band, the <NUM> band, and the <NUM> band.

<FIG> is a diagram of an example synchronized transmission <NUM> over different channel segments, according to an embodiment. In an embodiment, the transmission <NUM> is generated and transmitted by the network interface device <NUM> (<FIG>) to one or more client stations <NUM> (e.g., the client station <NUM>-<NUM>). In another embodiment, the transmission <NUM> is generated and transmitted by the network interface device <NUM> (<FIG>) to the AP <NUM>.

In an embodiment, the transmission <NUM> corresponds to a single user (SU) transmission that is generated and transmitted to a single communication device. In another embodiment, the transmission <NUM> corresponds to a multi-user (MU) transmission that includes data for multiple communication devices (e.g., multiple ones of the client stations <NUM>). For example, in an embodiment, the MU transmission <NUM> is an OFDMA transmission. In another embodiment, the MU transmission <NUM> is an MU-MIMO transmission.

The transmission <NUM> comprises a first RF signal <NUM> in a first channel segment <NUM> and a second RF signal <NUM> in a second channel segment <NUM>. The first RF signal <NUM> corresponds to a first PPDU and the second RF signal <NUM> corresponds to a second PPDU, according to an embodiment. The first signal comprises a PHY preamble <NUM> and a PHY data portion <NUM>. The second signal <NUM> comprises of a PHY preamble <NUM>, a data portion <NUM>, and optional padding <NUM>. The transmission <NUM> is synchronized such that transmission of the first signal <NUM> and the second signal <NUM> start at a same time t<NUM>. In some embodiments, the first signal <NUM> and the second signal <NUM> also end at a same time t<NUM>.

In some embodiments, the PHY preamble <NUM> and the PHY preamble <NUM> are not required to have a same duration and/or to end at a same time. In other embodiments, the PHY preamble <NUM> and the PHY preamble <NUM> are required to have a same duration and/or to end at a same time.

In an embodiment in which the second RF signal <NUM> would otherwise have a shorter duration than the first RF signal <NUM>, the PHY data portion <NUM> is appended with a packet extension field <NUM> so that transmission of the signal <NUM> ends at t<NUM>. In an embodiment, the packet extension field <NUM> includes arbitrary data that is ignored by receivers.

In another embodiment in which the second RF signal <NUM> has a shorter duration than the first RF signal <NUM>, duration information in a MAC header (not shown) within the PHY data portion <NUM> is set to indicate that the transmission of the signal <NUM> ends at t<NUM>, which causes another communication device to set a network allocation vector (NAV) timer of the other communication device to a value that indicates transmission of the signal <NUM> will end at t<NUM>.

In another embodiment in which the second RF signal <NUM> would otherwise have a shorter duration than the first RF signal <NUM>, padding information is included in the PHY data portion <NUM> so that transmission of the signal <NUM> ends at t<NUM>.

Example formats of the PHY preamble <NUM> and the PHY preamble <NUM> are described in more detail below. In an embodiment, at least a portion of the PHY preamble <NUM> and at least a portion of the PHY preamble <NUM> include different information. In another embodiment, at least a portion of the PHY preamble <NUM> and at least a portion of the PHY preamble <NUM> have the same structure and/or include the same information. In some embodiments, at least a portion of the PHY preamble <NUM> and at least a portion of the PHY preamble <NUM> are identical.

In an embodiment in which the first channel segment <NUM> comprises multiple component channels (e.g., <NUM> subchannels), at least a portion of the PHY preamble <NUM> (e.g., a legacy portion) is generated by generating a field corresponding to one component channel and duplicating the field over one or more other component channels corresponding to the first channel segment <NUM>. In an embodiment in which the second channel segment <NUM> comprises multiple component channels (e.g., <NUM> subchannels), at least a portion of the PHY preamble <NUM> (e.g., a legacy portion) is generated by generating a field corresponding to one component channel and duplicating the field over one or more other component channels corresponding to the second channel segment <NUM>.

In various embodiments, the first channel segment <NUM> and the second channel segment <NUM> are in different RF bands or are co-located in a same RF band. In an embodiment, the RF band(s) correspond to the <NUM> band, the <NUM> band, and the <NUM> bands, as described above. The first channel segment <NUM> and the second channel segment <NUM> may each be comprised of one or more of component channels. In an embodiment, a frequency bandwidth of the first channel segment <NUM> (i.e., a frequency bandwidth of the first signal <NUM>) is different than a frequency bandwidth of the second channel segment <NUM> (i.e., a frequency bandwidth of the second signal <NUM>). In another embodiment, the frequency bandwidth of the first channel segment <NUM> is the same as the frequency bandwidth of the second channel segment <NUM>.

In an embodiment, the first channel segment <NUM> and the second channel segment <NUM> are separated in frequency. For example, a gap in frequency exists between the first channel segment <NUM> and the second channel segment <NUM>. In various embodiments, the gap is at least <NUM>, at least <NUM>, at least <NUM>, at least <NUM>, etc..

In some embodiments, the first signal <NUM> is transmitted via a first number of spatial or space-time streams (hereinafter referred to as "spatial streams" for brevity), and the second signal <NUM> is transmitted via a second number of spatial streams that is different than the first number of spatial streams. In one such embodiment, the PHY preamble <NUM> includes a first number of LTFs corresponding to the first number of spatial streams, and the PHY preamble <NUM> includes a second number of LTFs (different than the first number of LTFs) corresponding to the second number of spatial streams. In another such embodiment, the PHY preamble <NUM> and the PHY preamble <NUM> comprise a same number of LTFs even when the first signal <NUM> is transmitted via a first number of spatial streams and the second signal <NUM> is transmitted via a second number of spatial streams that is different than the first number of spatial streams. In an embodiment, the same number of LTFs correspond to one of the first signal <NUM> and the second signal <NUM> with the larger number of spatial streams. In other embodiments, the first signal <NUM> and the second signal <NUM> are transmitted via a same number of spatial streams.

In an embodiment, at least the PHY data portion <NUM> and at least the PHY data portion <NUM> employ different encoding schemes and/or modulation schemes. As an example, in an embodiment, the PHY data portion <NUM> is generated using a first MCS and the PHY data portion <NUM> is generated using a second, different MCS. In other embodiments, the PHY data portion <NUM> and the PHY data portion <NUM> are generated using a same MCS.

In an embodiment, the transmission <NUM> corresponds to a single PPDU, where a first frequency portion of the single PPDU is transmitted via the first channel <NUM> and a second frequency portion of the single PPDU is transmitted via the second channel <NUM>. In another embodiment, the first signal <NUM> corresponds to a first PPDU and the second signal <NUM> corresponds to a second PPDU. In an embodiment, each of the PHY preambles <NUM> and <NUM>, and the PHY data portions <NUM> and <NUM>, are comprised of one or more OFDM symbols.

<FIG> is a diagram of an example unsynchronized transmission <NUM> over different channel segments, according to an embodiment. In an embodiment, the transmission <NUM> is generated and transmitted by the network interface device <NUM> (<FIG>) to one or more client stations <NUM> (e.g., the client station <NUM>-<NUM>). In another embodiment, the transmission <NUM> is generated and transmitted by the network interface device <NUM> (<FIG>) to the AP <NUM>.

The unsynchronized transmission <NUM> is similar to the synchronized transmission <NUM> of <FIG>, and like-numbered elements are not described in detail for brevity. Unlike the synchronized transmission <NUM> of <FIG>, transmission of the signal <NUM> and transmission of the signal <NUM> begin at different times. Additionally, transmission of the signal <NUM> and transmission of the signal <NUM> end at different times, according to some embodiments. Further, the signal <NUM> does not include the packet extension field <NUM> of <FIG>, according to some embodiments.

Referring now to <FIG> and <FIG>, a communication device (e.g., the AP <NUM>, the client station <NUM>-<NUM>, etc.) is configured to generate and transmit a synchronized transmission such as the transmission <NUM> (<FIG>) at some times (and/or in some scenarios), and to generate and transmit an unsynchronized transmission such as the transmission <NUM> (<FIG>) at other times (and/or in other scenarios), according to some embodiments. For example, transmitting an unsynchronized transmission in different channel segments does not require that the different channel segments be idle at a same time, at least in some embodiments, thus permitting simultaneous use of the different channel segments when a synchronized transmission may not be possible (e.g., when the synchronized transmission requires that the different channel segments are idle at the same time), at least in some embodiments and/or situations. On the other hand, unsynchronized transmissions in the different channel segments may not be permitted in some scenarios, such as when the different channel segments are relatively close in frequency, at least in some embodiments and/or situations.

<FIG> is a diagram of an example synchronized downlink MU OFDMA transmission <NUM> over different channel segments, according to an embodiment. In an embodiment, the transmission <NUM> is generated and transmitted by the network interface device <NUM> (<FIG>) to a plurality of client stations <NUM>.

The OFDMA transmission <NUM> comprises a first RF signal <NUM> in a first channel segment <NUM> and a second RF signal <NUM> in a second channel segment <NUM>. In various embodiments, the first channel segment <NUM> and the second channel segment <NUM> are similar to the first channel segment <NUM> and the second channel segment <NUM>, respectively, as described above with reference <FIG>. The transmission <NUM> is synchronized such that the first RF signal <NUM> and the second RF signal <NUM> start at a same time t<NUM>. In some embodiments, the first RF signal <NUM> and the second RF signal <NUM> end at a same time t<NUM>.

The first signal <NUM> comprises a PHY preamble <NUM> and a PHY data portion <NUM>. The second signal <NUM> comprises of a PHY preamble <NUM> and a data portion <NUM>. In some embodiments, the PHY preamble <NUM> and the PHY preamble <NUM> are not required to have a same duration and/or to end at a same time. In other embodiments, the PHY preamble <NUM> and the PHY preamble <NUM> are required to have a same duration and/or to end at a same time.

In another embodiment in which the second RF signal <NUM> has a shorter duration than the first RF signal <NUM>, duration information in a MAC header (not shown) within the PHY data portion <NUM> is set to indicate that the transmission of the signal <NUM> ends at t<NUM>, which causes another communication device to set a NAV timer of the other communication device to a value that indicates transmission of the signal <NUM> will end at t<NUM>.

In another embodiment in which the second RF signal <NUM> would otherwise have a shorter duration than the f first RF signal <NUM>, padding information is included in the PHY data portion <NUM> so that transmission of the signal <NUM> ends at t<NUM>.

In an embodiment, the PHY preamble <NUM> and the PHY preamble <NUM> are formatted in a manner similar to the PHY preamble <NUM>. Example formats of the PHY preamble <NUM> and the PHY preamble <NUM> are described in more detail below. In an embodiment, at least a portion of the PHY preamble <NUM> and at least a portion of the PHY preamble <NUM> include different information. In another embodiment, at least a portion of the PHY preamble <NUM> and at least a portion of the PHY preamble <NUM> have the same structure and/or include the same information. In some embodiments, at least a portion of the PHY preamble <NUM> and at least a portion of the PHY preamble <NUM> are identical.

In an embodiment in which the first channel segment <NUM> comprises multiple component channels (e.g., <NUM> subchannels), at least a portion of the PHY preamble <NUM> (e.g., a legacy portion) is generated by generating a field corresponding to one component channel and duplicating the field over one or more other component channels corresponding to the first channel segment <NUM>. In an embodiment in which the second channel segment <NUM> comprises multiple component channels, at least a portion of the PHY preamble <NUM> (e.g., a legacy portion) is generated by generating a field corresponding to one component channel and duplicating the field over one or more other component channels corresponding to the second channel segment <NUM>.

In an embodiment, the first communication channel <NUM> and the second communication channel <NUM> are separated in frequency. For example, a gap in frequency exists between the first communication channel <NUM> and the second communication channel <NUM>. In various embodiments, the gap is at least <NUM>, at least <NUM>, at least <NUM>, at least <NUM>, etc..

In some embodiments, the first signal <NUM> is transmitted via a first number of spatial streams, and the second signal <NUM> is transmitted via a second number of spatial streams that is different than the first number of spatial streams. In one such embodiment, the PHY preamble <NUM> includes a first number of LTFs corresponding to the first number of spatial streams, and the PHY preamble <NUM> includes a second number of LTFs (different than the first number of LTFs) corresponding to the second number of spatial streams. In another such embodiment, the PHY preamble <NUM> and the PHY preamble <NUM> comprise a same number of LTFs even when the first signal <NUM> is transmitted via a first number of spatial streams and the second signal <NUM> is transmitted via a second number of spatial streams that is different than the first number of spatial streams. In an embodiment, the same number of LTFs correspond to one of the first signal <NUM> and the second signal <NUM> with the larger number of spatial streams. In other embodiments, the first signal <NUM> and the second signal <NUM> are transmitted via a same number of spatial streams.

In an embodiment, at least a PHY data portion <NUM> and at least a PHY data portion <NUM> employ different encoding schemes and/or modulation schemes.

The PHY data portion <NUM> and the PHY data portion <NUM> include respective frequency multiplexed data for respective client stations <NUM>. Individual data within the data portion <NUM> are transmitted to corresponding client stations <NUM> in corresponding allocated frequency resource units (RUs) <NUM>. Individual data within the data portion <NUM> are transmitted to corresponding client stations <NUM> in corresponding allocated RUs <NUM>. In various embodiments, transmitted signals corresponding to some or all of RUs <NUM>/<NUM> use different encoding schemes and/or modulation schemes. As an example, transmitted signals corresponding to the RU <NUM>-<NUM> and the RU <NUM>-<NUM> are generated using different MCSs and/or different numbers of spatial/space-time streams, etc. In an embodiment in which a duration of data in an RU <NUM> is shorter than a duration of the PHY data portion <NUM>, padding is added to the data in the RU <NUM> to ensure the duration of the PHY data portions in both communication channels are the same.

In at least some embodiments, at least some of the client stations <NUM> are configured to operate only in one RF band. In such embodiments, RUs are allocated to the client station <NUM> only within the RF band in which the client station <NUM> is configured to operate. As an illustrative embodiment, STA2 and STA3 are configured to operate only in a first RF band. Hence, data corresponding to STA2 and STA3 is transmitted over RUs within the first channel segment <NUM>, which is within the first RF band in an embodiment. Similarly, STA4 is configured to operate only in a second RF band. Hence, data corresponding to STA4 is transmitted over RUs within the second channel segment <NUM>, which is within the second RF band in an embodiment. On the other hand, STA1 is configured for operation in both the first RF band and the second RF band. Hence, data corresponding to STA1 may be transmitted in RUs located in either or both of the first channel segment <NUM> and the second channel segment <NUM>.

<FIG> is a diagram of an example unsynchronized MU OFDMA transmission <NUM> over different channel segments, according to an embodiment. In an embodiment, the transmission <NUM> is generated and transmitted by the network interface device <NUM> (<FIG>) to one or more client stations <NUM> (e.g., the client station <NUM>-<NUM>). In another embodiment, the transmission <NUM> is generated and transmitted by the network interface device <NUM> (<FIG>).

Referring now to <FIG> and <FIG>, a communication device (e.g., the AP <NUM>, the client station <NUM>-<NUM>, etc.) is configured to generate and transmit a synchronized transmission such as the transmission <NUM> (<FIG>) at some times (and/or in some scenarios), and to generate and transmit an unsynchronized transmission such as the transmission <NUM> (<FIG>) at other times (and/or in other scenarios), according to some embodiments.

<FIG> is a flow diagram of an example method <NUM> for transmitting via multiple frequency segments in a wireless communication network, according to an embodiment. The AP <NUM> of <FIG> is configured to implement the method <NUM>, according to some embodiments. The client station <NUM>-<NUM> of <FIG> is additionally or alternatively configured to implement the method <NUM>, according to other embodiments. The method <NUM> is described in the context of the AP <NUM> merely for explanatory purposes and, in other embodiments, the method <NUM> is implemented by the client station <NUM>-<NUM> or another suitable communication device, according to various embodiments.

At block <NUM>, a communication device determines (e.g., the AP <NUM> determines, the network interface <NUM> determines, the MAC processor <NUM> determines, the multi-channel segment transmission controller <NUM> determines, etc.) whether simultaneous respective transmissions in a plurality of frequency segments are to be synchronized (e.g., the simultaneous respective transmissions are to begin at a same time). In various embodiments, the plurality of frequency segments are contiguous in frequency, or one or more adjacent pairs of frequency segments are separated in frequency by a respective gap in frequency. In various embodiments, each frequency segment in the plurality of frequency segments spans a same frequency bandwidth, or frequency segments in the plurality of frequency segments span different frequency bandwidths. In various embodiments, two or more frequency segments in the plurality of frequency segments are in a same RF band (e.g., the <NUM> band, the <NUM> band, the <NUM> band, etc.), or two or more frequency segments in the plurality of frequency segments are in different RF bands.

In various embodiments, determining whether the simultaneous respective transmissions are to be synchronized at block <NUM> is based on a variety of parameters and/or factors. For example, in one embodiment, determining whether the simultaneous respective transmissions are to be synchronized at block <NUM> is based on a bandwidth of a frequency gap between adjacent frequency segments in the plurality of frequency segments. For instance, when a frequency gap between a first frequency segment and a second frequency segment is less than a threshold, the communication device determines (e.g., the AP <NUM> determines, the network interface <NUM> determines, the MAC processor <NUM> determines, etc.) at block <NUM> that the simultaneous transmissions in the first frequency segment and the second frequency segment are to be synchronized (e.g., the simultaneous respective transmissions are to begin at a same time); whereas when the frequency gap between the first frequency segment and the second frequency segment is greater than the threshold, the communication device determines (e.g., the AP <NUM> determines, the network interface <NUM> determines, the MAC processor <NUM> determines, etc.) at block <NUM> that the simultaneous transmissions in the first frequency segment and the second frequency segment are not required to be synchronized, according to an illustrative embodiment. When the first frequency segment and the second frequency segment are relatively close in frequency (e.g., the frequency gap between the first frequency segment and the second frequency segment is less than the threshold), an amount (or probability) of inter-channel interference is relatively high, and thus requiring synchronized transmissions improves performance (e.g., overall throughput); whereas when the first frequency segment and the second frequency segment are relatively far apart in frequency (e.g., the frequency gap between the first frequency segment and the second frequency segment is greater than the threshold), the amount (or probability) of inter-channel interference is relatively low, and thus requiring synchronized transmissions is not required, according to an illustrative embodiment.

As another example, in another embodiment, determining whether the simultaneous respective transmissions are to be synchronized at block <NUM> is additionally or alternatively based on bandwidth capabilities of one or more other communication devices that are to receive the simultaneous respective transmissions. For instance, in response to the AP <NUM> determining (e.g., the network interface <NUM> determines, the MAC processor <NUM> determines, etc.) that one or more of the other communication devices are not capable of receiving unsynchronized transmissions, the AP <NUM> determines at block <NUM> that the simultaneous respective transmissions in the plurality of frequency segments are to be synchronized, according to an illustrative embodiment.

As another example, determining whether the simultaneous respective transmissions are to be synchronized at block <NUM> is based on an overall frequency bandwidth of the plurality of frequency segments in the plurality of frequency segments. For instance, when the overall bandwidth is less than a threshold, the communication device determines (e.g., the AP <NUM> determines, the network interface <NUM> determines, the MAC processor <NUM> determines, etc.) at block <NUM> that the simultaneous transmissions in the first frequency segment and the second frequency segment are to be synchronized (e.g., the simultaneous respective transmissions are to begin at a same time); whereas when the overall bandwidth is greater than the threshold, the communication device determines (e.g., the AP <NUM> determines, the network interface <NUM> determines, the MAC processor <NUM> determines, etc.) at block <NUM> that the simultaneous transmissions in the first frequency segment and the second frequency segment are not required to be synchronized, according to an illustrative embodiment. When the overall bandwidth is relatively narrow (e.g., the overall bandwidth is less than the threshold), the probability of finding times when all frequency segments in the plurality of frequency segments are idle is relatively high and benefits of synchronized transmissions may improve performance (e.g., overall throughput); whereas when the overall bandwidth is relatively wide (e.g., the overall bandwidth is greater than the threshold), the probability of finding times when all frequency segments in the plurality of frequency segments are idle is relatively low and benefits of synchronized transmissions will not outweigh performance degradation due increased failures to find times when all frequency segments are idle, according to an illustrative embodiment.

When it is determined at block <NUM> that simultaneous respective transmissions in the plurality of frequency segments are to be synchronized, the flow proceeds to block <NUM>. At block <NUM>, the AP <NUM> simultaneously transmits (e.g., the network interface device <NUM> simultaneously transmits, the PHY processor <NUM> simultaneously transmits, etc.) via the plurality of frequency segments in a synchronized manner. Simultaneously transmitting at block <NUM> comprises transmitting a first signal via a first frequency segment at a first time, and transmitting a second signal via a second frequency segment at the first time, according to an embodiment.

In some embodiments, prior to simultaneously transmitting in a synchronized manner at block <NUM>, the AP <NUM> determines (e.g., the network interface device <NUM> determines, the MAC processor <NUM> determines, etc.) when the plurality of frequency segments are idle at a same time, and begins the simultaneous, synchronous transmission at block <NUM> after determining that the plurality of frequency segments are idle at the same time. In some embodiments, prior to simultaneously transmitting in a synchronized manner at block <NUM>, the AP <NUM> waits (e.g., the network interface device <NUM> waits, the MAC processor <NUM> waits, etc.) until the plurality of frequency segments are all determined to be idle at the same time, and then begins the simultaneous, synchronous transmission at block <NUM>.

In some embodiments, simultaneously transmitting at block <NUM> comprises transmitting signals such as described above with reference to <FIG>. In other embodiments, simultaneously transmitting at block <NUM> comprises transmitting signals such as described above with reference to <FIG>. In other embodiments, simultaneously transmitting at block <NUM> comprises transmitting other suitable signals having other suitable formats.

In some embodiments, simultaneously transmitting at block <NUM> comprises the multi-channel segment transmission controller <NUM> prompting the PHY processor <NUM> to begin the first transmission in the first frequency segment at the first time and to begin the second transmission in the second frequency segment at the first time.

On the other hand, when it is determined at block <NUM> that simultaneous respective transmissions in the plurality of frequency segments are to be unsynchronized, the flow proceeds to block <NUM>. Simultaneously transmitting at block <NUM> comprises transmitting a third signal via a third frequency segment at a second time, and transmitting a fourth signal via a fourth frequency segment at a third time, according to an embodiment. In some embodiments, the third frequency segment is the first frequency segment (block <NUM>), and the fourth frequency segment is the second frequency segment (block <NUM>), according to an embodiment.

In some embodiments, unlike the synchronous transmissions at block <NUM>, the AP <NUM> does not need to determine when the plurality of frequency segments are idle at a same time, or wait for a time when the plurality of frequency segments are idle at a same time, before a transmission at block <NUM> in one of the frequency segments can begin. For example, when the AP <NUM> determines (e.g., the network interface device <NUM> determines, the MAC processor <NUM> determines, etc.) that a first frequency segment among the plurality of frequency segments is idle, the AP <NUM> can begin transmitting (at block <NUM>) in the first frequency segment even though the AP <NUM> determines (e.g., the network interface device <NUM> determines, the MAC processor <NUM> determines, etc.) that a second frequency segment among the plurality of frequency segments is not also idle at the same time, according to an embodiment. When the AP <NUM> later determines the second frequency segment has also become idle, the AP <NUM> can begin transmitting (at block <NUM>) in the second frequency segment simultaneously with the transmission (at block <NUM>) in the first frequency segment.

In some embodiments, simultaneously transmitting at block <NUM> comprises the multi-channel segment transmission controller <NUM> prompting the PHY processor <NUM> to begin the third transmission in the third frequency segment at the second time and to begin the fourth transmission in the fourth frequency segment at the third time.

In some embodiments, the first frequency segment is the same as the third frequency segment, and the second frequency segment is the same as the fourth frequency segment. In other embodiments, the first frequency segment is different from the third frequency segment, and/or the second frequency segment is different from the fourth frequency segment.

In some embodiments, the first packet is the same as the third packet, and the second packet is the same as the fourth packet. In other embodiments, the first packet is different from the third packet, and/or the second packet is different from the fourth packet.

<FIG> is a diagram of an example network interface device <NUM> configured for multi-channel segment operation, according to an embodiment. For instance, in an embodiment, the network interface device <NUM> is configured for synchronous and/or asynchronous transmission/reception over multiple frequency segments. In an embodiment, the network interface device <NUM> corresponds to the network interface device <NUM> of the AP <NUM> of <FIG>. In another embodiment, the network interface device <NUM> corresponds to the network interface device <NUM> of the client station <NUM>-<NUM> of <FIG>.

The network interface device <NUM> is configured for operation over two frequency segments. The network interface device <NUM> includes a MAC processor <NUM> coupled to a PHY processor <NUM>. The MAC processor <NUM> exchanges frames (or PSDUs) with the PHY processor <NUM>.

In an embodiment, the MAC processor <NUM> corresponds to the MAC processor <NUM> of <FIG>. In another embodiment, the MAC processor <NUM> corresponds to the MAC processor <NUM> of <FIG>. In an embodiment, the PHY processor <NUM> corresponds to the PHY processor <NUM> of <FIG>. In another embodiment, the PHY processor <NUM> corresponds to the PHY processor <NUM> of <FIG>.

The PHY processor <NUM> includes a single baseband signal processor <NUM>. The single baseband signal processor <NUM> is coupled to a first RF radio (Radio-<NUM>) <NUM> and a second RF radio (Radio-<NUM>) <NUM>. In an embodiment, the RF radio <NUM> and the RF radio <NUM> correspond to the transceivers <NUM> of <FIG>. In another embodiment, the RF radio <NUM> and the RF radio <NUM> correspond to the transceivers <NUM> of <FIG>. In an embodiment, the RF radio <NUM> is configured to operate on a first RF band, and the RF radio <NUM> is configured to operate on a second RF band. In another embodiment, the RF radio <NUM> and the RF radio <NUM> are both configured to operate on the same RF band.

In an embodiment, the MAC processor <NUM> generates data corresponding to MAC layer data units (e.g., frames) and provides the frames (or PSDUs) to the baseband signal processor <NUM>. The baseband signal processor <NUM> is configured to receive frames (or PSDUs) from the MAC processor <NUM>, and encapsulate the frames (or PSDUs) into respective packets and generate respective baseband signals corresponding to the respective packets. The baseband signal processor <NUM> provides the respective baseband signals to the Radio-<NUM><NUM> and the Radio-<NUM><NUM>. The Radio-<NUM><NUM> and Radio-<NUM><NUM> upconvert the respective baseband signals to generate respective RF signals for transmission via the first frequency segment and the second frequency segment, respectively. The Radio-<NUM><NUM> transmits a first RF signal via the first frequency segment and the Radio-<NUM><NUM> transmits a second RF signal via the second frequency segment.

In some embodiments, the MAC processor <NUM> determines whether frames are to be transmitted synchronously or asynchronously, and informs the baseband signal processor <NUM> whether the frames are to be transmitted synchronously or asynchronously when providing the frames to the baseband signal processor <NUM>. In some embodiments, the MAC processor <NUM> determines in which frequency segment a frame is to be transmitted, and informs the baseband signal processor <NUM> of the frequency segment in which the frame is to be transmitted when providing the frame to the baseband signal processor <NUM>.

When the first RF signal and the second RF signal are to be synchronized, the baseband signal processor <NUM> is configured to ensure that respective transmitted signals over the first frequency segment and the second frequency segment are synchronized. For example, the baseband signal processor <NUM> is provide the respective baseband signals to the Radio-<NUM><NUM> and the Radio-<NUM><NUM> beginning at a same time.

The Radio-<NUM><NUM> and the Radio-<NUM><NUM> are also configured to receive respective RF signals via the first frequency segment and the second frequency segment, respectively. The Radio-<NUM><NUM> and the Radio-<NUM><NUM> generate respective baseband signals corresponding to the respective received signals. The generated respective baseband signals are provided to the baseband signal processor <NUM>. The baseband signal processor <NUM> generates respective PSDUs corresponding to the respective received signals, and provides the PSDUs to the MAC processor <NUM>. The MAC processor <NUM> processes the PSDUs received from the baseband signal processor <NUM>.

<FIG> is a diagram of example PPDUs <NUM> and <NUM> transmitted in respective frequency segments, according to an embodiment. For example, PPDU <NUM> is transmitted in a first frequency segment and PPDU <NUM> is transmitted in a second frequency segment. In some embodiments and/or scenarios, the first frequency segment is separated in frequency from the second frequency segment by a gap in frequency. In other embodiments and/or scenarios, the first frequency segment is adjacent in frequency to the second frequency segment, and the first frequency segment is not separated in frequency from the second frequency segment.

In some embodiments, the PHY processor <NUM> (<FIG>) is configured to generate and transmit the PPDUs <NUM> and <NUM>. In some embodiments, the PHY processor <NUM> (<FIG>) is configured to generate and transmit the PPDUs <NUM> and <NUM>. In some embodiments, the baseband processor <NUM> (<FIG>) is configured to generate the PPDUs <NUM> and <NUM> and the radios <NUM>, <NUM> (<FIG>) are configured to transmit the PPDUs <NUM> and <NUM>.

The PPDU <NUM> includes a legacy PHY preamble <NUM> (sometimes referred to as a legacy preamble <NUM>), a non-legacy PHY preamble (e.g., an EHT preamble) <NUM>, and a PHY data portion <NUM>. The legacy preamble <NUM> comprises a legacy short training field (L-STF) <NUM>, a legacy long training field (L-LTF) <NUM>, and a legacy signal field (L-SIG) <NUM>. The L-SIG <NUM> includes a rate subfield (not shown) and a length subfield (not shown) that together indicate a duration of the PPDU <NUM>. In some embodiments, the EHT preamble <NUM> includes PHY parameters regarding the PPDU <NUM> that are for use by receiver devices to properly process the PPDU <NUM>, such as a modulation and coding scheme (MCS) subfield that indicates an MCS used for the PHY data portion <NUM>. When the PPDU <NUM> is an MU PPDU, the EHT preamble <NUM> includes allocation information that indicates frequency resource unit (RU) allocation information, spatial stream allocation information, etc. In some embodiments, the EHT preamble <NUM> includes one or more long training fields, the number of which varies depending on how many spatial streams are used to transmit the PHY data portion <NUM>.

The PPDU <NUM> includes a legacy preamble <NUM>, a non-legacy PHY preamble (e.g., an EHT preamble) <NUM>, and a PHY data portion <NUM>. The legacy preamble <NUM> comprises an L-STF <NUM>, an L-LTF <NUM>, and an L-SIG <NUM>. The L-SIG <NUM> includes a rate subfield (not shown) and a length subfield (not shown) that together indicate a duration of the PPDU <NUM>. In some embodiments, the EHT preamble <NUM> includes PHY parameters regarding the PPDU <NUM> that are for use by receiver devices to properly process the PPDU <NUM>, such as an MCS subfield that indicates an MCS used for the PHY data portion <NUM>. When the PPDU <NUM> is an MU PPDU, the EHT preamble <NUM> includes allocation information that indicates frequency RU allocation information, spatial stream allocation information, etc. In some embodiments, the EHT preamble <NUM> includes one or more long training fields, the number of which varies depending on how many spatial streams are used to transmit the PHY data portion <NUM>.

In some embodiments in which transmission of the PPDU <NUM> and the PPDU <NUM> is synchronized, the PPDU <NUM> includes a packet extension field <NUM> so that a duration of the PPDU <NUM> is the same as a duration of the PPDU <NUM>. In other embodiments, the PHY data portion <NUM> additionally or alternatively includes padding as discussed above. In other embodiments, a signal extension is additionally or alternatively used for PPDU <NUM> so that receiver devices set their NAV counters to a value that indicates a duration that corresponds to a duration of the PPDU <NUM> as discussed above. In some embodiments in which transmission of the PPDU <NUM> and the PPDU <NUM> is asynchronous, the PPDU <NUM> does not include the packet extension field <NUM>.

In some embodiments, a duration of the EHT preamble <NUM> is different (or is not required to be the same) as a duration of the EHT preamble <NUM>. In other embodiments, the duration of the EHT preamble <NUM> is required to be the same as the duration of the EHT preamble <NUM> (e.g., padding bits are added (if needed) to the EHT preamble <NUM> so that a duration of the EHT preamble <NUM> is the same as the duration of the EHT preamble <NUM>).

In embodiments in which the PPDU <NUM> has a different duration than the PPDU <NUM>, the L-SIG <NUM> includes different information than the L-SIG <NUM>. For example, the length subfield in the L-SIG <NUM> indicates a different length than the length subfield in the L-SIG <NUM>.

<FIG> is a diagram of an example non-legacy preamble (e.g., an EHT preamble) <NUM> that is used as the non-legacy preamble <NUM> or the non-legacy preamble <NUM>, according to some embodiments.

In some embodiments, the PHY processor <NUM> (<FIG>) is configured to generate the non-legacy preamble <NUM>. In some embodiments, the PHY processor <NUM> (<FIG>) is configured to generate the non-legacy preamble <NUM>. In some embodiments, the baseband processor <NUM> (<FIG>) is configured to generate the non-legacy preamble <NUM>.

The non-legacy preamble <NUM> includes a first signal field (EHT-SIGA) <NUM>, a second signal field (EHT-SIGB) <NUM>, a short training field (EHT-STF) <NUM>, and one or more long training fields (EHT-LTFs) <NUM>. In an embodiment, when a PHY data portion corresponding to the non-legacy preamble <NUM> is to be transmitted via n spatial streams (where n is a suitable positive integer), the non-legacy preamble <NUM> includes no more than n EHT-LTFs <NUM>. In another embodiment, when a PHY data portion corresponding to the non-legacy preamble <NUM> is to be transmitted via n spatial streams, the non-legacy preamble <NUM> includes at least n EHT-LTFs <NUM>.

In some embodiments, EHT-SIGB <NUM> is included for MU PPDUs and is not included for single user (SU) PPDUs.

In various embodiments, the EHT-SIGA <NUM> and/or the EHT-SIGB <NUM> indicate an MCS (or multiple MCSs for an MU PPDU) used for the PHY data portion corresponding to the non-legacy preamble <NUM>. Thus, when different MCSs are used for different frequency segments, content of the EHT-SIGAs <NUM> in the different frequency segments is different.

Similarly, when different numbers of spatial streams are used for different frequency segments, the number of EHT-LTFs <NUM> in the different frequency segments is different, at least in some embodiments.

Referring now to <FIG>, in embodiments in which the L-SIG <NUM> and the L-SIG <NUM> include different information, a duplicate of the L-SIG <NUM> is transmitted in each subchannel (e.g., each <NUM> subchannel) of the first frequency segment, and a duplicate of the L-SIG <NUM> is transmitted in each subchannel (e.g., each <NUM> subchannel) of the second frequency segment. In embodiments in which one or more subchannels in a frequency segment are punctured (e.g., not used for transmission), a duplicate of the L-SIG <NUM>/<NUM> is not transmitted in punctured subchannels.

In embodiments in which the non-legacy signal field <NUM> includes different information in different frequency segments, a duplicate of the non-legacy signal field <NUM> that includes information for the first frequency segment is transmitted in each subchannel (e.g., each <NUM> subchannel) of the first frequency segment, and a duplicate of the non-legacy signal field <NUM> that includes information for the second frequency segment is transmitted in each subchannel (e.g., each <NUM> subchannel) of the second frequency segment. In embodiments in which one or more subchannels in a frequency segment are punctured (e.g., not used for transmission), a duplicate of the non-legacy signal field <NUM> is not transmitted in punctured subchannels.

Similarly, in embodiments in which the non-legacy signal field <NUM> includes different information in different frequency segments, a duplicate of the non-legacy signal field <NUM> that includes information for the first frequency segment is transmitted in each subchannel (e.g., each <NUM> subchannel) of the first frequency segment, and a duplicate of the non-legacy signal field <NUM> that includes information for the second frequency segment is transmitted in each subchannel (e.g., each <NUM> subchannel) of the second frequency segment. In embodiments in which one or more subchannels in a frequency segment are punctured (e.g., not used for transmission), a duplicate of the non-legacy signal field <NUM> is not transmitted in punctured subchannels.

In some embodiments (e.g., in which the PPDU <NUM> is a MU PPDU and the PPDU <NUM> is an SU PPDU), a duplicate of the non-legacy signal field <NUM> that includes information for the first frequency segment is transmitted in each subchannel (e.g., each <NUM> subchannel) of the first frequency segment, and the non-legacy signal field <NUM> is not transmitted in the second frequency segment.

In some embodiments, the non-legacy signal field <NUM> includes a bandwidth subfield <NUM> that indicates an overall bandwidth of only the frequency segment in which the PPDU <NUM>/<NUM> is transmitted. For example, when the PPDU <NUM> is transmitted in a first frequency segment having an overall bandwidth of <NUM> and the PPDU <NUM> is transmitted in a second frequency segment having an overall bandwidth of <NUM>, the bandwidth subfield <NUM> in the PPDU <NUM> indicates a bandwidth of <NUM>, whereas the bandwidth subfield <NUM> in the PPDU <NUM> indicates a bandwidth of <NUM>.

In some embodiments, the non-legacy signal field <NUM> includes a frequency segment identifier (ID) subfield <NUM> that indicates the frequency segment in which the PPDU <NUM>/<NUM> is transmitted. For example, when the PPDU <NUM> is transmitted in a first frequency segment and the PPDU <NUM> is transmitted in a second frequency segment, the frequency segment ID subfield <NUM> in the PPDU <NUM> indicates the first frequency segment, whereas the frequency segment ID subfield <NUM> in the PPDU <NUM> indicates the second frequency segment.

In some embodiments, the non-legacy signal field <NUM> also includes one or more other subfields (not shown) that indicate one or more of: i) whether a simultaneous transmission is occurring in any other frequency segment(s), ii) a number of other frequency segments in which the simultaneous transmission is occurring, iii) respective overall frequency bandwidth(s) of the other frequency segment(s), and iv) a cumulative frequency bandwidth of all of the frequency segments in which simultaneous transmissions are occurring.

In some embodiments, legacy preambles and non-legacy preambles having formats such as discussed above with reference to <FIG> are used with the transmissions discussed above with reference to <FIG> and <FIG>.

Although certain orderings of fields and subfields are illustrated in <FIG>, in other embodiments, other suitable orderings fields and subfields are utilized. In other embodiments, PHY preambles include one or more other suitable fields/subfields in addition to the fields and subfields illustrated in <FIG>. Similarly, in some embodiments, one or more of the fields/subfields illustrated in <FIG> are omitted.

At least some of the various blocks, operations, and techniques described above may be implemented utilizing hardware, a processor executing firmware instructions, a processor executing software instructions, or any combination thereof. When implemented utilizing a processor executing software or firmware instructions, the software or firmware instructions may be stored in any computer readable memory such as on a magnetic disk, an optical disk, or other storage medium, in a RAM or ROM or flash memory, processor, hard disk drive, optical disk drive, tape drive, etc. The software or firmware instructions may include machine readable instructions that, when executed by one or more processors, cause the one or more processors to perform various acts.

When implemented in hardware, the hardware may comprise one or more of discrete components, an integrated circuit, an application-specific integrated circuit (ASIC), a programmable logic device (PLD), etc..

Claim 1:
A method for simultaneously transmitting in a plurality of frequency segments, comprising:
determining (<NUM>), at a communication device, whether simultaneous transmissions in a first frequency segment and a second frequency segment are to be synchronized in time;
in response to the communication device determining that simultaneous transmissions in the first frequency segment and the second frequency segment are to be synchronized in time (<NUM>),
transmitting a first packet in the first frequency segment beginning at a first time, and
transmitting a second packet in the second frequency segment beginning at the first time; and
in response to the communication device determining that simultaneous transmissions in the first frequency segment and the second frequency segment are to be unsynchronized in time (<NUM>),
transmitting a third packet in the first frequency segment beginning at a second time, and
transmitting a fourth packet in the second frequency segment beginning at a third time that is different than the second time.