Wireless communication methods and apparatus

Abstract

This disclosure provides a wireless communication method and apparatus, relating to scalable waveform and parameter set design for next-generation WLANs in a 60 GHz band. A first device wirelessly communicates with a second device in the 60 GHz band based on a specific parameter set design, said parameter set design having at least one of the following: (i) selection of a specific subcarrier frequency spacing; (ii) selection of a specific guard interval (GI) design; and (iii) reuse of a pre-existing channelization or tone plan.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically, to the design of scalable waveforms and numberologies for next-generation wireless local area networks (WLANs) in the 60 GHz range. Background Technology

[0002] Unless otherwise stated herein, the methods described in this section are not prior art to the listed claims and are not acknowledged as prior art by virtue of their inclusion in this section.

[0003] According to the Institute of Electrical and Electronics Engineers (IEEE) 802.11ad / ay / aj, next-generation wireless communications, such as the 60 GHz unlicensed spectrum band, have been used and standardized. A major advantage of the 60 GHz band is its wider spectral bandwidth, which can be used to achieve higher data rates with less interference. In the IEEE 802.11ad directional multi-gigabit (DMG) system, the channel bandwidth is 2.16 GHz, while in the IEEE 802.11ay system, the channel bandwidth is further extended to 2.16 GHz, 4.32 GHz, 6.48 GHz, and 8.64 GHz. On the other hand, the IEEE 802.11ax / be High Efficiency (HE) / Ultra-High Throughput (EHT) system has become the dominant wireless connectivity technology and is widely adopted in the market. However, the throughput of HE / EHT systems is insufficient to support future applications such as augmented reality (AR), virtual reality (VR), and the metaverse. Therefore, the challenge lies in how to leverage the wide bandwidth of the 60GHz band while simplifying the implementation as much as possible using existing IEEE 802.11ax / be designs. Consequently, a solution for scalable waveform and parameter set design for next-generation WLANs in the 60GHz band is needed. Summary of the Invention

[0004] The following overview is exemplary only and is not intended to be limiting in any way. That is, it is provided to introduce the concept, key points, benefits, and advantages of the novel and non-obvious technology described herein. The chosen implementation methods are further described in the detailed description below. Therefore, the following overview is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0005] The purpose of this disclosure is to provide a wireless communication method and apparatus relating to scalable waveform and parameter set design for next-generation WLANs in 60 GHz.

[0006] In one aspect, a method may include a processor of a first device wirelessly communicating with a second device in a 60 GHz band by (a) sending first data or first information to the second device; and (b) receiving second data or second information from the second device. When communicating wirelessly in a 60 GHz band, the method may involve the processor being designed to communicate wirelessly in a 60 GHz band based on a specific set of parameters having at least one of the following: (i) selection of a specific subcarrier frequency spacing; (ii) selection of a specific guard interval (GI) design; and (iii) reuse of a pre-existing channelization or tone plan.

[0007] In another aspect, an apparatus may include a transceiver configured to perform wireless communication and a processor coupled to the transceiver. The processor may wirelessly communicate with another apparatus in the 60 GHz band via the transceiver by either or both of the following: (a) transmitting first data or first information to the other apparatus; and (b) receiving second data or the second information from the other apparatus. When wirelessly communicating in the 60 GHz band, the processor may design the wireless communication in the 60 GHz band based on a specific set of parameters having at least one of the following: (i) selection of a specific subcarrier frequency spacing; (ii) selection of a specific guard interval (GI) design; and (iii) reuse of a pre-existing channelization or tone planning.

[0008] This invention enables the use of the relatively wide bandwidth of the 60GHz frequency band while simplifying the implementation as much as possible using existing IEEE 802.11ax / be designs.

[0009] It is worth noting that while the descriptions provided herein can be understood in the context of certain radio access technologies, networks, and network topologies (e.g., Wi-Fi), the proposed ideas, schemes, and any variations / derivatives thereof can be implemented in other types of radio access technologies, networks, and network topologies (e.g., but not limited to, Bluetooth, ZigBee, 5G / New Radio (NR), LTE, LTE-Advanced, LTE-AdvancedPro, Internet of Things (IoT), Industrial IoT (IIoT), and Narrowband IoT (NB-IoT)). Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0010] The accompanying drawings are included to provide a further understanding of this disclosure and are incorporated in and constitute a part of this disclosure. The drawings illustrate implementations of this disclosure and, together with the specification, serve to explain the principles of this disclosure. It is apparent that the drawings are not necessarily to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concept of this disclosure.

[0011] Figure 1 This is a schematic diagram of an example network environment that can implement various solutions and schemes according to this disclosure.

[0012] Figure 2 This is a schematic diagram of an example scenario based on the scheme proposed in this disclosure.

[0013] Figure 3 This is a schematic diagram of an example scenario based on the scheme proposed in this disclosure.

[0014] Figure 4 The diagram is an example design based on the scheme proposed in this disclosure.

[0015] Figure 5 The diagram is an example design based on the scheme proposed in this disclosure.

[0016] Figure 6 The diagram is an example design based on the scheme proposed in this disclosure.

[0017] Figure 7 The diagram is an example design based on the scheme proposed in this disclosure.

[0018] Figure 8 The diagram is an example design based on the scheme proposed in this disclosure.

[0019] Figure 9 The diagram is an example design based on the scheme proposed in this disclosure.

[0020] Figure 10 The diagram is an example design based on the scheme proposed in this disclosure.

[0021] Figure 11 The diagram is an example design based on the scheme proposed in this disclosure.

[0022] Figure 12 This is a block diagram of an example communication system based on an implementation of this disclosure.

[0023] Figure 13 This is a flowchart illustrating an example of an implementation of this disclosure. Detailed Implementation

[0024] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. This disclosure can be implemented in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0025] Overview

[0026] Implementations according to this disclosure relate to various techniques, methods, schemes, and / or solutions related to the design of scalable waveforms and parameter sets for next-generation WLANs in 60 GHz. According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, while these possible solutions may be described individually below, two or more of these possible solutions may be implemented in one combination or another.

[0027] It is worth noting that, in this disclosure, a regular RU (rRU) refers to an RU having continuous (e.g., adjacent to each other) tones that are not interleaved, staggered, or otherwise distributed. Furthermore, a 26-tone regular RU can be interchangeably represented as RU26 (or rRU26), a 52-tone regular RU can be interchangeably represented as RU52 (or rRU52), a 106-tone regular RU can be interchangeably represented as RU106 (or rRU106), a 242-tone regular RU can be interchangeably represented as RU242 (or rRU242), and so on. Furthermore, a multi-RU (MRU) with aggregated (26+52) tones can be interchangeably represented as MRU78 (or rMRU78), a multi-RU with aggregated (26+106) tones can be interchangeably represented as MRU132 (or rMRU132), and so on.

[0028] Since the above examples are merely exemplary and not an exhaustive list of all possibilities, the same applies to regular RUs, distributed-tone RUs, MRUs, and distributed-tone MRUs of different sizes (or different numbers of tones). It is also worth noting that in this disclosure, a 20MHz bandwidth can be interchangeably represented as BW20 or BW20M, a 40MHz bandwidth can be interchangeably represented as BW40 or BW40M, an 80MHz bandwidth can be interchangeably represented as BW80 or BW80M, a 160MHz bandwidth can be interchangeably represented as BW160 or BW160M, a 240MHz bandwidth can be interchangeably represented as BW240 or BW240M, and a 320MHz bandwidth can be interchangeably represented as BW320 or BW320M.

[0029] Figure 1 An example network environment 100 is shown in which various solutions and schemes according to this disclosure can be implemented. Figures 2 to 13 Examples of implementations of various proposed schemes in a network environment 100 according to this disclosure are shown. (Refer to...) Figures 1 to 13 The following descriptions of the various proposed solutions are provided.

[0030] Reference Figure 1 Network environment 100 may include at least STA 110 wirelessly communicating with station (STA) 120. Each of STA 110 and STA 120 may be a non-access point (non-AP) STA, or alternatively, either STA 110 or STA 120 may be used as an access point (AP) STA. In some cases, STA 110 and STA 120 may be associated with a basic service set (BSS) according to one or more IEEE 802.11 standards (e.g., IEEE 802.11be or future standards). Each of STA 110 and STA 120 may be configured to communicate with each other by utilizing scalable waveform and parameter set designs of next-generation WLANs in 60 GHz, according to various proposed schemes described below. That is, either or both of STA 110 and STA 120 may act as a "user" in the proposed schemes and examples described below. It is worth noting that although the various proposed solutions may be described individually or separately below, in actual implementation, some or all of the proposed solutions may be implemented using or otherwise combined. Of course, each proposed solution may be used individually or separately or implemented in other ways.

[0031] The IEEE 802.11ay standard defines several parameters related to Enhanced Directional Multi-Gigabit (EDMG) Orthogonal Frequency Division Multiplexing (OFDM) Physical Layer (PHY), including: bandwidth, subcarrier frequency spacing, Discrete Fourier Transform (DFT) size, number of direct-current (DC) tones, number of pilot tones, DFT period, GI, and sampling clock rate. The channel bandwidth can be any of 2160MHz, 4320MHz, 6480MHz, and 8640MHz. The subcarrier frequency spacing (ΔF) can be 5.15625MHz. The DFT size can be any of 512, 1024, 1536, and 2048. For all bandwidths (BW), the number of DC tones can be 3. The number of pilot tones can be any of 16, 36, 56, and 76. The DFT period can be 194 nanoseconds (194 ns) or equivalently 0.194 μs. The GI can be 18.18 ns (short), 36.36 ns (normal), or 72.72 ns (long). The sampling clock rate can be any of 2640 MHz, 5280 MHz, 7920 MHz, and 10560 MHz. Figure 2 Example scenario 200 illustrates IEEE 802.11ay EDMG channelizations in the 60GHz band, where #1, #2...#29 indicate all the channel numbers for each bandwidth. Figure 3 An exemplary scenario 300 is illustrated with the channel BW and the occupied BW of IEEE 802.11ay EDMG.

[0032] Under the various proposed schemes according to this disclosure, there may be some general considerations in the design of scalable waveforms and parameter sets in the 60 GHz band. Under the proposed schemes, IEEE 802.11ad / ay / aj DMG, EDMG, or China millimeter-wave multi-gigabit (CMMG) channelizations can be reused in the 60 GHz band. Furthermore, under the proposed schemes, several considerations can be given to the selection of subcarrier frequency spacing. For example, the subcarrier frequency spacing may need to be large enough to reduce phase noise and intercarrier interference (ICI) effects. Additionally, the selection of subcarrier frequency spacing can be performed without requiring a large fast Fourier transform (FFT) size. Moreover, clock sources compatible with existing IEEE 802.11ax / be designs can be utilized. Furthermore, the selection of subcarrier frequency spacing needs to be flexible for various applications. Furthermore, multiple IEEE 802.11be subcarrier frequency spacings can exist (e.g., ΔF = α * 78.125 kHz, where α is a positive integer and represents a scaling factor), and N fft *ΔF=BW(where N) fft (This represents the number of FFT subcarriers). Under the proposed scheme, the GI design needs to achieve efficiency optimization and flexibly cover different channel delay distributions. The proposed scheme can reuse IEEE 802.11ac / ax / be design elements as much as possible, such as tone planning, signaling, modulation and coding scheme (MCS), encoding, and decoding. Furthermore, in... Figures 4 to 11 In the figures, for each of the various designs based on the proposed schemes described below, several relevant parameters are proposed for each design. For each channel bandwidth under each design, the relevant parameters may include, for example, but not limited to, ΔF (subcarrier frequency spacing), T... dft (OFDM symbol duration), T gi (GI duration), T sym (symbol duration), F s (sampling frequency), N fft (Number of FFT subcarriers), N sd (Number of data carrier subcarriers), N sp (Number of pilot tone subcarriers), N dc (Number of DC tones), N st (Total number of subcarriers), Nguard (The number of protected tones) and tone planning.

[0033] Under the proposed scheme for parameter set design according to this disclosure, as a first option (option 1-a), the channel BW can remain the same as IEEE 802.11ay, for example 2160MHz, 4320MHz, 6480MHz and 8640MHz. Figure 4 Example design 400 is illustrated with respect to the parameter set design under option 1-a of the proposed scheme. For example, an IEEE 802.11be tone plan for an 80MHz bandwidth (BW80M) can be mapped to a 2160MHz bandwidth (BW2160M), a tone plan for a 160MHz bandwidth (BW160M) can be mapped to a 4320MHz bandwidth (BW4320M), and so on. Under the proposed scheme, since 2160 / 80 = 27 = 3^3, and due to the subcarrier spacing ΔF of IEEE 802.11be... eht=78.125kHz, the subcarrier frequency spacing of the 60GHz band can be defined as follows: ΔF = 78.125kHz * 3^3 = 2.109375MHz. Accordingly, 2160MHz = (78.125kHz * 3^3) * 1024 --> RU996 tone planning of BW80M in IEEE 802.11be --> Occupied channel bandwidth (OCB) = 2.1GHz; 4320MHz = (78.125kHz * 3^3) * 2048 --> RU2 * 996 tone planning of BW160M in IEEE 802.11be --> OCB = 4.2GHz; 6480MHz = (78.125kHz * 3^3) * 3072 --> RU3 * 996 tone planning of BW240M in IEEE 802.11be --> OCB = 6.3GHz; and 8640MHz = (78.125kHz * 3^3) * 4096 --> IEEE The RU4*996 tone plan for BW320M in 802.11be --> OCB = 8.4GHz. Furthermore, under the proposed scheme, the 540MHz bandwidth (BW540M) and 1080MHz bandwidth (BW1080M) can be defined as follows: 540MHz = (78.125kHz*3^3)*256 --> RU242 tone plan for BW20M in IEEE 802.11be --> OCB = 0.51GHz; 1080MHz = (78.125kHz*3^3)*512 --> RU484 tone plan for BW40M in IEEE 802.11be --> OCB = 1.02GHz. Additionally, under the proposed scheme, three GI options can be used, as follows: For short GI, T... gi,short =T dft / 32, T gi T represents the duration of GI. dft Indicates the OFDM symbol duration; for normal GI, T gi,normal =T dft / 16; and for long GI, T gi,long =T dft / 8.

[0034] Figure 5Example design 500 is shown, illustrating the parameter set design under an alternative option (Option 1-b) to the first option of the proposed scheme. Generally, Option 1-b is similar to Option 1-a, but with an increased subcarrier spacing. That is, under Option 1-b, for bandwidths of 1080MHz, 2160MHz, 4320MHz, 6480MHz, and 8640MHz, ΔF = 78.125kHz * 3^3 * 2 = 4.21875MHz, while for the BW540M, the subcarrier frequency spacing can remain ΔF = 78.125kHz * 3^3 = 2.109375MHz.

[0035] In another proposed scheme for parameter set design according to this disclosure, as a second option (option 2-a), an OCB similar to that of IEEE 802.11ay can be maintained to preserve a similar guard band. Figure 6Example design 600 is illustrated with respect to the parameter set design under option 2-a of the proposed scheme. In IEEE 802.11ay, the OCB of BW2160M is approximately 1825MHz. To map the tone planning of BW80M in IEEE 802.11be to the frequency range of BW2160M while maintaining a similar occupied BW, the subcarrier frequency spacing can be 1825MHz / 996 = 1.8323MHz. Then, the BW can become 1024 * 1.8323MHz = 1876.3MHz. To make the BW a multiple of 80MHz, the following design can be chosen: 80MHz * ceil(1876.3 / 80) = 80MHz * 24 = 1920MHz. Therefore, the subcarrier frequency spacing can be as follows: ΔF = 1920MHz / 1024 = 1.875MHz. Under the proposed scheme, since 1.875MHz = 78.125kHz * 24, the channel bandwidths of 1920MHz (BW1920M), 3840MHz (BW3840M), 5760MHz (BW5760M), and 7680MHz (BW7680M) in the 60GHz band can be defined as follows: 1920MHz = (78.125kHz * 3 * 2^3) * 1024 --> RU996 tone planning for BW80M in IEEE 802.11be --> OCB = 1.8675GHz; 3840MHz = (78.125kHz * 3 * 2^3) * 2048 --> IEEE In 802.11be, the RU2*996 tone plan of BW160M is 3.375GHz; 5760MHz = (78.125kHz*3*2^3)*3072. In 802.11be, the RU3*996 tone plan of BW240M is 5.6025GHz; 7680MHz = (78.125kHz*3*2^3)*4096. In 802.11be, the RU4*996 tone plan of BW320M is 7.47GHz. Furthermore, under the proposed scheme, the 480MHz bandwidth (BW480M) and 960MHz bandwidth (BW960M) can be defined as follows: 480MHz = (78.125kHz * 3 * 2^3) * 256 --> RU242 tone planning of BW20M in IEEE 802.11be --> OCB = 0.45375GHz; 960MHz = (78.125kHz * 3 * 2^3) * 512 --> RU484 tone planning of BW40M in IEEE 802.11be --> OCB = 0.9075GHz.It is worth noting that all BW480M, BW960M, 1920MHz bandwidth (BW1920M), 3840MHz bandwidth (BW3840M), 5760MHz bandwidth (BW5760M), and 7680MHz bandwidth (BW7680M) can be multiples of 80MHz or 160MHz. Furthermore, under the proposed scheme, three GI options are available, as follows: for short GIs, T... gi,short =T dft / 32; For normal GI, T gi,normal =T dft / 16; and for long GI, T gi,long =T dft / 8.

[0036] Figure 7 Example design 700 illustrates the parameter set design under an alternative option (option 2-b) to the proposed second option. Generally, option 2-b is similar to option 2-a, but with an increased subcarrier spacing. That is, under option 2-b, for bandwidths of 1920MHz, 3840MHz, 5760MHz, and 7680MHz, ΔF = 78.125kHz * 48 = 3.75MHz, while for BW4800M and BW960M, the subcarrier frequency spacing can remain ΔF = 78.125kHz * 24 = 1.875MHz.

[0037] In another proposed scheme for the parameter set design according to this disclosure, as a third option (option 3-a), the same channel BW as IEEE 802.11ay or a similar OCB as IEEE 802.11ay can be maintained, such that for design option 1-a the subcarrier frequency spacing ΔF = 78.125kHz * 27 and the scaling factor α = 27, or for design option 2-a ΔF = 78.125kHz * 24 and the scaling factor α = 24. Figure 8Example design 800 is shown for the parameter set design under option 3-a of the proposed scheme. In design option 3-a, a scalability factor α = 26 can be considered --> ΔF = 78.125kHz * 26 = 2.03125MHz. Therefore, the channel bandwidths of 2080MHz (BW2080M), 4160MHz (BW4160M), 6240MHz (BW6240M), and 8320MHz (BW8320M) in the 60GHz band can be defined as follows: 2080MHz = (78.125kHz * 26) * 1024 --> RU996 tone planning of BW80M in IEEE 802.11be --> OCB = 2.023GHz; 4160MHz = (78.125kHz * 26) * 2048 --> RU2 * 996 tone planning of BW160M in IEEE 802.11be --> OCB = 4.046GHz; 6240MHz = (78.125kHz * 26) * 3072 --> IEEE In 802.11be, the RU3*996 tone plan of BW240M is OCB = 6.070GHz; and 8320MHz = (78.125kHz*26)*4096. In IEEE 802.11be, the RU4*996 tone plan of BW320M is OCB = 8.093GHz. Furthermore, under the proposed scheme, the 520MHz bandwidth (BW520M) and 1040MHz bandwidth (BW1040M) can be defined as follows: 520MHz = (78.125kHz * 26) * 256 --> RU242 tone planning of BW20M in IEEE 802.11be --> OCB = 0.492GHz; and 1040MHz = (78.125kHz * 26) * 512 --> RU484 tone planning of BW40M in IEEE 802.11be --> OCB = 0.983GHz. Additionally, under the proposed scheme, three GI options are available, as follows: For short GI, T... gi,short =T dft / 32; For normal GI, T gi,normal =T dft / 16; and for long GI, T gi,long =T dft / 8.

[0038] Figure 9Example design 900 is illustrated with a parameter set design under an alternative option (option 3-b) to the proposed third option. Generally, option 3-b is similar to option 3-a, but with an increased subcarrier spacing. That is, under option 3-b, for bandwidths of 1040MHz, 2080MHz, 4160MHz, 6240MHz, and 8320MHz, ΔF = 78.125kHz * 5² = 4.0625MHz, while for BW520M, the subcarrier frequency spacing can remain ΔF = 78.125kHz * 2⁶ = 2.03125MHz.

[0039] Figure 10Example design 1000 of parameter set design under option 4-a of the proposed scheme is illustrated. Under yet another proposed scheme of parameter set design according to this disclosure, as the fourth option (option 4-a), a scaling factor α = 25 can be considered, and therefore the subcarrier frequency spacing can be ΔF = 78.125kHz * 25 = 1.953125MHz. Therefore, the channel bandwidths of 2000MHz (BW2000M), 4000MHz (BW4000M), 6000MHz (BW6000M), and 8000MHz (BW8000M) in the 60GHz band can be defined as follows: 2000MHz = (78.125kHz * 25) * 1024 --> RU996 tone planning of BW80M in IEEE 802.11be --> OCB = 1.945GHz; 4000MHz = (78.125kHz * 25) * 2048 --> RU2 * 996 tone planning of BW160M in IEEE 802.11be --> OCB = 3.890GHz; 6000MHz = (78.125kHz * 25) * 3072 --> IEEE In 802.11be, the RU3*996 tone plan of BW240M is OCB = 5.836GHz; and 8000MHz = (78.125kHz*25)*4096. In IEEE 802.11be, the RU4*996 tone plan of BW320M is OCB = 7.781GHz. Furthermore, under the proposed scheme, the 500MHz bandwidth (BW500M) and 1000MHz bandwidth (BW1000M) can be defined as follows: 500MHz = (78.125kHz * 25) * 256 --> RU242 tone planning of BW20M in IEEE 802.11be --> OCB = 0.473GHz; and 1000MHz = (78.125kHz * 25) * 512 --> RU484 tone planning of BW40M in IEEE 802.11be --> OCB = 0.945GHz. Additionally, under the proposed scheme, three GI options are available, as follows: For short GI, T... gi,short =T dft / 32; For normal GI, T gi,normal =T dft / 16; and for long GI, T gi,long =T dft / 8.

[0040] Figure 11An example design 1100 is illustrated with respect to the parameter set design under an alternative option (option 4-b) to the fourth option of the proposed scheme. Generally, option 4-b is similar to option 4-a, but with an increased subcarrier spacing. That is, under option 4-b, for bandwidths of 2000MHz, 4000MHz, 6000MHz, and 8000MHz, ΔF = 78.125kHz * 50 = 3.90625MHz, while for BW500M and BW1000M, the subcarrier frequency spacing can remain ΔF = 78.125kHz * 25 = 1.953125MHz.

[0041] Exemplary Implementation

[0042] Figure 12 An example system 1200, having at least example device 1210 and example device 1220, is illustrated according to an implementation of this disclosure. Each of devices 1210 and 1220 can perform various functions to implement the schemes, techniques, processes, and methods described herein relating to the design of scalable waveforms and parameter sets for next-generation WLANs in 60 GHz, including the various schemes described above for various proposed designs, concepts, schemes, systems, and methods, as well as the processes described below. For example, device 1210 can be implemented in STA 110, while device 1220 can be implemented in STA 120, and vice versa.

[0043] Each of devices 1210 and 1220 may be part of an electronic device, which may be a non-AP STA or AP STA, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. When implemented in an STA, each of devices 1210 and 1220 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet computer, laptop computer, or notebook computer. Each of devices 1210 and 1220 may also be part of a machine-type device, which may be a device such as a fixed or stationary device, a home appliance, a wired communication device, or a computing device. For example, each of devices 1210 and 1220 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, devices 1210 and / or 1220 may be implemented in a network node of an AP, such as in a WLAN.

[0044] In some implementations, each of devices 1210 and 1220 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. In the various embodiments described above, each of devices 1210 and 1220 may be implemented in or be implemented as an STA or AP. Each of devices 1210 and 1220 may include Figure 12 At least some of the components shown include, for example, processor 1212 and processor 1222, respectively. Each of devices 1210 and 1220 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solution of this disclosure, and therefore, such components of devices 1210 and 1220 are neither... Figure 12 As shown in the diagram, it is not described below for the sake of simplicity and brevity.

[0045] In one aspect, each of processors 1212 and 1222 may be implemented as one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 1212 and 1222, according to this disclosure, in some implementations, each of processors 1212 and 1222 may include multiple processors, while in other implementations, it may include a single processor. In another aspect, each of processors 1212 and 1222 may be implemented in hardware (and optionally firmware) having electronic components including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, configured and arranged to achieve a particular purpose according to this disclosure. In other words, in at least some implementations, each of processors 1212 and 1222 is a dedicated machine specifically designed, set up, and configured to perform specific tasks according to various implementations of this disclosure, including tasks related to the design of scalable waveforms and parameter sets for next-generation WLANs in 60 GHz.

[0046] In some implementations, device 1210 may further include a transceiver 1216 coupled to processor 1212. Transceiver 1216 may include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. In some implementations, device 1220 may further include a transceiver 1226 coupled to processor 1222. Transceiver 1226 may include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. It is noteworthy that although transceivers 1216 and 1226 are shown as being external to and separate from processors 1212 and 1222, respectively, in some implementations, transceiver 1216 may be part of processor 1212 as a system-on-a-chip (SoC), and transceiver 1226 may be part of processor 1222 as a SoC.

[0047] In some implementations, device 1210 may further include memory 1214 coupled to and accessible by processor 1212 and capable of storing data therein. In some implementations, device 1220 may further include memory 1224 coupled to and accessible by processor 1222 and capable of storing data therein. Each of memory 1214 and memory 1224 may include some type of random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively or additionally, each of memory 1214 and memory 1224 may include some type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of the memories 1214 and 1224 may include, for example, flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM) and / or phase-change memory.

[0048] Each of devices 1210 and 1220 can be a communication entity capable of communicating with each other using various schemes proposed according to this disclosure. For illustrative and non-limiting purposes, a description of the capabilities of device 1210 as STA 110 and device 1220 as STA 120 is provided below. It is worth noting that although a detailed description of the capabilities, functions, and / or technical features of device 1220 is provided below, for the sake of brevity, although a separate detailed description of device 1210 is not provided, it can be applied to device 1210. It is also worth noting that although the example implementations described below are provided in the context of WLAN, they can also be implemented in other types of networks.

[0049] Under various proposed schemes related to the scalable waveform and parameter set design of next-generation WLAN in 60 GHz according to this disclosure, utilizing device 1210 implemented as STA 110 or implemented as STA 110 in network environment 100 and device 1220 implemented as STA 120 or implemented as STA 120 in network environment 100, the processor 1212 of device 1210 can wirelessly communicate with device 1220 in the 60 GHz band via transceiver 1216 by any one or both of the following: (a) transmitting first data or first information to the second device; and (b) receiving second data or second information from the second device. In wireless communication in the 60 GHz band, processor 1212 can design wireless communication in the 60 GHz band based on a specific parameter set having at least one of the following: (i) selection of a specific subcarrier frequency spacing; (ii) selection of a specific GI design; and (iii) reuse of a pre-existing channelization or tone plan.

[0050] In some implementations, the selection of the specific subcarrier frequency spacing may involve selecting a subcarrier frequency spacing (ΔF) that is a multiple of the IEEE 802.11be subcarrier frequency spacing such that ΔF = α * 78.125 kHz, or that is a multiple of the IEEE 802.11ac subcarrier frequency spacing such that ΔF = α * 312.5 kHz, where α is a positive integer and represents a scaling factor.

[0051] In some implementations, the selection of the specific GI design may involve choosing a GI from multiple options, including: a short GI, where T gi,short＝ T dft / 32; Normal GI, where T gi,normal＝ T dft / 16; and long GI, where T gi,long＝ T dft / 8; where Tgi Indicates the duration of GI, where T dft Indicates the duration of the OFDM symbol.

[0052] In some implementations, the reuse of pre-existing channelization or tone plans may involve reusing IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11ay, or IEEE 802.11be channelization or tone plans.

[0053] In some implementations, under option 1-a, the specific parameter set design may include the following: (a) for a 540MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan according to IEEE 802.11be for a 20MHz bandwidth to a 540MHz channel bandwidth with an OCB of 0.51GHz; (b) for a 1080MHz channel bandwidth, mapping a single 484 tone resource unit (RU484) tone plan according to IEEE 802.11be for a 40MHz bandwidth to a 1080MHz channel bandwidth with an OCB of 1.02GHz; (c) for a 2160MHz channel bandwidth, mapping a single 996 tone resource unit (RU996) tone plan according to IEEE 802.11be for an 80MHz bandwidth to a 2160MHz channel bandwidth with an OCB of 2.1GHz; (d) for a 4320MHz channel bandwidth, mapping according to IEEE... (e) For a 160MHz bandwidth of 802.11be, two 996-tone resource units (RU2*996) are mapped according to the IEEE 802.11be tone planning to a 4320MHz channel bandwidth with an OCB of 4.2GHz; (f) For a 6480MHz channel bandwidth, three 996-tone resource units (RU3*996) according to the IEEE 802.11be tone planning to a 240MHz bandwidth are mapped to a 6480MHz channel bandwidth with an OCB of 6.3GHz; and (f) For an 8640MHz channel bandwidth, four 996-tone resource units (RU4*996) according to the IEEE 802.11be tone planning to a 320MHz bandwidth are mapped to an 8640MHz channel bandwidth with an OCB of 8.4GHz.

[0054] In some implementations, under option 1-a and design 400, the specific parameter set design may include at least the following: (a) for a 540MHz channel bandwidth, select ΔF = 2.109375MHz, T dft =0.474μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, Tsym =T dft +T gi F s =540MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1080MHz channel bandwidth, select ΔF = 2.109375MHz, T dft =0.474μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =1080MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a channel bandwidth of 2160MHz, choosing ΔF = 2.109375MHz, T dft =0.474μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =2160MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0055] In some implementations, under options 1-b and design 500, the specific parameter set design may include at least the following: (a) for a channel bandwidth of 540 MHz, select ΔF = 2.109375 MHz, T dft =0.474μs, Tgi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =540MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1080MHz channel bandwidth, select ΔF = 4.21875MHz, T dft =0.237μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s＝ 1080MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), tone planning for RU242; and (c) for a channel bandwidth of 2160MHz, choose ΔF = 4.21875MHz, T dft =0.237μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =2160MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484).

[0056] In some implementations, under option 2-a, the specific parameter set design may include the following: (a) for a 480MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan of 20MHz bandwidth according to IEEE 802.11ax or 802.11be to a 480MHz channel bandwidth with an OCB of 0.45375GHz; (b) for a 960MHz channel bandwidth, mapping according to IEEE (c) For a 1920MHz channel bandwidth, a single 484-tone resource unit (RU484) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 960MHz channel bandwidth with an OCB of 0.9075GHz; (d) For a 3840MHz channel bandwidth, two 996-tone resource units (RU2*996) with a 160MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 3840MHz channel bandwidth with an OCB of 3.375GHz; (e) For a 5760MHz channel bandwidth, according to the tone planning of IEEE 802.11ax or 802.11be to a 960MHz channel bandwidth with an OCB of 0.9075GHz; (c) For a 1920MHz channel bandwidth, a single 996-tone resource unit (RU996) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 960MHz channel bandwidth with an OCB of 0.9075GHz; (d) For a 3840MHz channel bandwidth, two 996-tone resource units (RU2*996) with a 160MHz bandwidth of IEEE 802.11ax or 802.11be to a 3840MHz channel bandwidth with an OCB of 3.375GHz; (e) For a 5760MHz channel bandwidth, a single 484-tone resource unit (RU484) with a 40MHz bandwidth of IEEE (f) Tone planning of three 996 tone resource units (RU3*996) with a bandwidth of 240 MHz of 802.11be is mapped to a channel bandwidth of 5760 MHz with an OCB of 5.6025 GHz; and (f) For a channel bandwidth of 7680 MHz, tone planning of four 996 tone resource units (RU4*996) with a bandwidth of 320 MHz of IEEE 802.11be is mapped to a channel bandwidth of 7680 MHz with an OCB of 7.47 GHz.

[0057] In some implementations, under option 2-a and design 600, this particular parameter set design may include at least the following: (a) for a channel bandwidth of 480MHz, select ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =480MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard= (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 960MHz channel bandwidth, select ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =960MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 1920MHz channel bandwidth, choosing ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =1920MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0058] In some implementations, under option 2-b and design 700, this particular parameter set design may include at least the following: (a) for a channel bandwidth of 480 MHz, selecting ΔF = 1.875 MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =480MHz, N fft =256, N sd =234, Nsp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 960MHz channel bandwidth, select ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =960MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 1920MHz channel bandwidth, choosing ΔF = 3.75MHz, T dft =0.267μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =1920MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11) and tone planning for RU484.

[0059] In some implementations, under option 3-a, the specific parameter set design may include the following: (a) for a 520MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan of 20MHz bandwidth according to IEEE 802.11ax or 802.11be to a 520MHz channel bandwidth with an OCB of 0.492GHz; (b) for a 1040MHz channel bandwidth, mapping according to IEEE (c) For a 2080MHz channel bandwidth, a single 484-tone resource unit (RU484) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 1040MHz channel bandwidth with an OCB of 0.983GHz; (d) For a 4160MHz channel bandwidth, two 996-tone resource units (RU2*996) with a 160MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 1040MHz channel bandwidth with an OCB of 0.983GHz; (e) For a 6240MHz channel bandwidth, according to the tone planning of IEEE 802.11ax or 802.11be to a 1040MHz channel bandwidth with an OCB of 0.983GHz; (f) For a 6240MHz channel bandwidth, a single 484-tone resource unit (RU484) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 1040MHz channel bandwidth with an OCB of 0.983GHz; (c) For a 2080MHz channel bandwidth, a single 996-tone resource unit (RU996) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be to a 1040MHz channel bandwidth with an OCB of 0.983GHz; (g) For a 6240MHz channel bandwidth, a single 996-tone resource unit (RU996) with a 40MHz bandwidth of IEEE 80 (f) Tone planning of three 996 tone resource units (RU3*996) with a bandwidth of 240 MHz of 802.11be is mapped to a channel bandwidth of 6240 MHz with an OCB of 6.070 GHz; and (f) For a channel bandwidth of 8320 MHz, tone planning of four 996 tone resource units (RU4*996) with a bandwidth of 320 MHz of IEEE 802.11be is mapped to a channel bandwidth of 8320 MHz with an OCB of 8.093 GHz.

[0060] In some implementations, under option 3-a and design 800, this particular parameter set design may include at least the following: (a) for a 520MHz channel bandwidth, select ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =520MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard= (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1040MHz channel bandwidth, select ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =1040MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 2080MHz channel bandwidth, choosing ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =2080MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0061] In some implementations, under option 3-b and design 900, the specific parameter set design may include at least the following: (a) for a 520MHz channel bandwidth, select ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =520MHz, N fft =256, N sd=234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1040MHz channel bandwidth, select ΔF = 4.0625MHz, T dft =0.246μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =1040MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for RU242; and (c) for a 2080MHz channel bandwidth, choose ΔF = 4.0625MHz, T dft =0.246μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =2080MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484).

[0062] In some implementations, under option 4-a, the specific parameter set design may include the following: (a) for a 500MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan of 20MHz bandwidth according to IEEE 802.11ax or 802.11be to a 500MHz channel bandwidth with an OCB of 0.473GHz; (b) for a 1000MHz channel bandwidth, mapping according to IEEE (c) For a 2000MHz channel bandwidth, a single 484-tone resource unit (RU484) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 1000MHz channel bandwidth with an OCB of 0.945GHz; (d) For a 4000MHz channel bandwidth, two 996-tone resource units (RU2*996) with a 160MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 1000MHz channel bandwidth with an OCB of 0.945GHz; (e) For a 6000MHz channel bandwidth, according to the tone planning of IEEE 802.11ax or 802.11be to a 1000MHz channel bandwidth with an OCB of 0.945GHz; (f) For a 6000MHz channel bandwidth, a single 484-tone resource unit (RU484) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be will be mapped according to the tone planning of IEEE 802.11ax or 802.11be to a 1000MHz channel bandwidth with an OCB of 0.945GHz; (c) For a 2000MHz channel bandwidth, a single 996-tone resource unit (RU996) with a 40MHz bandwidth of IEEE 802.11ax or 802.11be to a 1000MHz channel bandwidth with an OCB of 0.945GHz; (g) For a 6000MHz channel bandwidth, a single 996-tone resource unit (RU996) with a 40MHz bandwidth of IEEE 80 (f) Tone planning of three 996 tone resource units (RU3*996) with a bandwidth of 240 MHz of 802.11be is mapped to a 6000 MHz channel bandwidth with an OCB of 5.836 GHz; and (f) For an 8000 MHz channel bandwidth, tone planning of four 996 tone resource units (RU4*996) with a bandwidth of 320 MHz of IEEE 802.11be is mapped to an 8000 MHz channel bandwidth with an OCB of 7.781 GHz.

[0063] In some implementations, under option 4-a and design 1000, the specific parameter set design may include at least the following: (a) for a 500MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =500MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard= (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1000MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =1000MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 2000MHz channel bandwidth, choosing ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =2000MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0064] In some implementations, under option 4-b and design 1100, the specific parameter set design may include at least the following: (a) for a 500MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =500MHz, N fft =256, N sd=234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1000MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =1000MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 2000MHz channel bandwidth, choosing ΔF = 3.90625MHz, T dft =0.256μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =2000MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for RU484.

[0065] Exemplary processing

[0066] Figure 13Example process 1300 is illustrated according to an implementation of the present disclosure. Process 1300 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 1300 may represent one aspect of proposed concepts and schemes related to the design of scalable waveforms and parameter sets for next-generation WLANs in 60 GHz according to the present disclosure. Process 1300 may include one or more operations, actions, or functions as shown in one or more of block 1310 and sub-blocks 1312 and 1314. Although illustrated as discrete blocks, the individual blocks of process 1300 may be divided into additional blocks, combined into fewer blocks, or eliminated depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 1300 may be... Figure 13 The process can be executed in the order shown, or alternatively in a different order. Furthermore, one or more boxes / sub-boxes of process 1300 can be executed repeatedly or iteratively. Process 1300 can be implemented by or within devices 1210 and 1220 and any variations thereof. For illustrative purposes only and not for limitation, process 1300 is described below in the context of device 1210, implemented as a STA 110 acting as a non-AP STA, and device 1220, implemented as an AP STA, in a wireless network (e.g., WLAN) in a network environment 100 according to one or more IEEE 802.11 standards. Process 1300 may begin at box 1310.

[0067] At 1310, process 1300 may involve processor 1212 of device 1210 wirelessly communicating with device 1220 in the 60 GHz band via transceiver 1216: (a) transmitting first data or first information to the second device; and (b) receiving second data or second information from the second device. In wireless communication in the 60 GHz band, process 1300 may involve processor 1212 designing wireless communication in the 60 GHz band based on a specific set of parameters having at least one of the following: (i) selection of a specific subcarrier frequency spacing; (ii) selection of a specific GI design; and (iii) reuse of a pre-existing channelization or tone plan.

[0068] In some implementations, the selection of a specific subcarrier frequency spacing may involve selecting a subcarrier frequency spacing (ΔF) that is a multiple of the IEEE 802.11be subcarrier frequency spacing such that ΔF = α * 78.125 kHz, or that is a multiple of the IEEE 802.11ac subcarrier frequency spacing such that ΔF = α * 312.5 kHz, where α is a positive integer and represents a scaling factor.

[0069] In some implementations, the selection of a particular GI design may involve choosing a GI from multiple options, including: a short GI, where T gi,short＝ T dft / 32; Normal GI, where T gi,normal＝ T dft / 16; and long GI, where T gi,long＝ T dft / 8; where T gi Indicates the duration of GI, where T dft Indicates the duration of the OFDM symbol.

[0070] In some implementations, the reuse of pre-existing channelization or tone plans may involve reusing IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11ay, or IEEE 802.11be channelization or tone plans.

[0071] In some implementations, under option 1-a, the specific parameter set design may include the following: (a) for a 540MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan according to the IEEE 802.11be standard for a 20MHz bandwidth to a 540MHz channel bandwidth with an OCB of 0.51GHz; (b) for a 1080MHz channel bandwidth, mapping a single 484 tone resource unit (RU484) tone plan according to the IEEE 802.11be standard for a 40MHz bandwidth to a 1080MHz channel bandwidth with an OCB of 1.02GHz; (c) for a 2160MHz channel bandwidth, mapping a single 996 tone resource unit (RU996) tone plan according to the IEEE 802.11be standard for an 80MHz bandwidth to a 2160MHz channel bandwidth with an OCB of 2.1GHz; (d) for a 4320MHz channel bandwidth, mapping according to the IEEE standard for a 242MHz channel bandwidth ... (e) Tone planning of two 996 tone resource units (RU2*996) with a bandwidth of 160 MHz for 802.11be is mapped to a 4320 MHz channel bandwidth for an OCB of 4.2 GHz; (f) For a channel bandwidth of 6480 MHz, tone planning of three 996 tone resource units (RU3*996) with a bandwidth of 240 MHz for IEEE 802.11be is mapped to a 6480 MHz channel bandwidth for an OCB of 6.3 GHz; and (f) For a channel bandwidth of 8640 MHz, tone planning of four 996 tone resource units (RU4*996) with a bandwidth of 320 MHz for IEEE 802.11be is mapped to an 8640 MHz channel bandwidth for an OCB of 8.4 GHz.

[0072] In some implementations, under option 1-a and design 400, the specific parameter set design may include at least the following: (a) for a 540MHz channel bandwidth, select ΔF = 2.109375MHz, T dft =0.474μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =540MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1080MHz channel bandwidth, select ΔF = 2.109375MHz, T dft =0.474μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =1080MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a channel bandwidth of 2160MHz, choosing ΔF = 2.109375MHz, T dft =0.474μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s＝ 2160MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, Nguard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0073] In some implementations, under options 1-b and design 500, the specific parameter set design may include at least the following: (a) for a channel bandwidth of 540 MHz, select ΔF = 2.109375 MHz, T dft =0.474μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =540MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1080MHz channel bandwidth, select ΔF = 4.21875MHz, T dft 0.237μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =1080MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), tone planning for RU242; and (c) for a channel bandwidth of 2160MHz, choose ΔF = 4.21875MHz, T dft =0.237μs, T gi,short =0.015μs, T gi,normal =0.030μs, T gi,long =0.059μs, T sym =T dft +T gi F s =2160MHz, N fft =512, N sd =468, Nsp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484).

[0074] In some implementations, under option 2-a, the specific parameter set design may include the following: (a) for a 480MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan of 20MHz bandwidth according to IEEE 802.11ax or 802.11be to a 480MHz channel bandwidth for an OCB of 0.45375GHz; (b) for a 960MHz channel bandwidth, mapping a single 484 tone resource unit (RU484) tone plan of 40MHz bandwidth according to IEEE 802.11ax or 802.11be to a 960MHz channel bandwidth for an OCB of 0.9075GHz; (c) for a 1920MHz channel bandwidth, mapping according to IEEE (d) For a 3840MHz channel bandwidth, two 996-tone resource units (RU2*996) with a 160MHz bandwidth according to IEEE 802.11ax or 802.11be will be mapped to a 3840MHz channel bandwidth for an OCB, according to IEEE 802.11ax or 802.11be; (e) For a 5760MHz channel bandwidth, three 996-tone resource units (RU3*996) with a 240MHz bandwidth according to IEEE 802.11be will be mapped to a 5760MHz channel bandwidth for an OCB, according to IEEE 802.11be; and (f) For a 7680MHz channel bandwidth, a tonal plan will be mapped according to IEEE 802.11ax or 802.11be; The tone planning of four 996 tone resource units (RU4*996) with a 320MHz bandwidth of 802.11be is mapped to a 7680MHz channel bandwidth for the OCB at 7.47GHz.

[0075] In some implementations, under option 2-a and design 600, this particular parameter set design may include at least the following: (a) for a channel bandwidth of 480MHz, select ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +Tgi F s =480MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 960MHz channel bandwidth, select ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =960MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 1920MHz channel bandwidth, choosing ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =1920MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0076] In some implementations, under option 2-b and design 700, this particular parameter set design may include at least the following: (a) for a channel bandwidth of 480 MHz, selecting ΔF = 1.875 MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal=0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =480MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 960MHz channel bandwidth, select ΔF = 1.875MHz, T dft =0.533μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =960MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 1920MHz channel bandwidth, choosing ΔF = 3.75MHz, T dft =0.267μs, T gi,short =0.017μs, T gi,normal =0.033μs, T gi,long =0.067μs, T sym =T dft +T gi F s =1920MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11) and tone planning for RU484.

[0077] In some implementations, under option 3-a, the specific parameter set design may include the following: (a) for a 520MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan of 20MHz bandwidth according to IEEE 802.11ax or 802.11be to a 520MHz channel bandwidth for an occupied channel bandwidth OCB of 0.492GHz; (b) for a 1040MHz channel bandwidth, mapping a single 484 tone resource unit (RU484) tone plan of 40MHz bandwidth according to IEEE 802.11ax or 802.11be to a 1040MHz channel bandwidth for an OCB of 0.983GHz; (c) for a 2080MHz channel bandwidth, mapping according to IEEE (d) For a 4160MHz channel bandwidth, two 996-tone resource units (RU2*996) with a 160MHz bandwidth according to IEEE 802.11ax or 802.11be are mapped to a 2080MHz channel bandwidth for an OCB at 4.046GHz; (e) For a 6240MHz channel bandwidth, three 996-tone resource units (RU3*996) with a 240MHz bandwidth according to IEEE 802.11be are mapped to a 6240MHz channel bandwidth for an OCB at 6.070GHz; and (f) For an 8320MHz channel bandwidth, according to IEEE... The tone planning of four 996 tone resource units (RU4*996) with a 320MHz bandwidth of 802.11be is mapped to an 8320MHz channel bandwidth for the OCB at 8.093GHz.

[0078] In some implementations, under option 3-a and design 800, this particular parameter set design may include at least the following: (a) for a 520MHz channel bandwidth, select ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =520MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st=242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1040MHz channel bandwidth, select ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =1040MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 2080MHz channel bandwidth, choosing ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =2080MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0079] In some implementations, under option 3-b and design 900, the specific parameter set design may include at least the following: (a) for a 520MHz channel bandwidth, select ΔF = 2.03125MHz, T dft =0.492μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =520MHz, N fft=256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1040MHz channel bandwidth, select ΔF = 4.0625MHz, T dft =0.246μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =1040MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for RU242; and (c) for a 2080MHz channel bandwidth, choose ΔF = 4.0625MHz, T dft =0.246μs, T gi,short =0.015μs, T gi,normal =0.031μs, T gi,long =0.062μs, T sym =T dft +T gi F s =2080MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484).

[0080] In some implementations, under option 4-a, the specific parameter set design may include the following: (a) for a 500MHz channel bandwidth, mapping a single 242 tone resource unit (RU242) tone plan of 20MHz bandwidth according to IEEE 802.11ax or 802.11be to a 500MHz channel bandwidth for an OCB of 0.473GHz; (b) for a 1000MHz channel bandwidth, mapping a single 484 tone resource unit (RU484) tone plan of 40MHz bandwidth according to IEEE 802.11ax or 802.11be to a 1000MHz channel bandwidth for an OCB of 0.945GHz; (c) for a 2000MHz channel bandwidth, mapping according to IEEE (d) For a 4000MHz channel bandwidth, two 996-tone resource units (RU2*996) with a 160MHz bandwidth according to IEEE 802.11ax or 802.11be will be mapped to a 2000MHz channel bandwidth for an OCB at 3.890GHz; (e) For a 6000MHz channel bandwidth, three 996-tone resource units (RU3*996) with a 240MHz bandwidth according to IEEE 802.11be will be mapped to a 6000MHz channel bandwidth for an OCB at 5.836GHz; and (f) For an 8000MHz channel bandwidth, according to IEEE The tone planning of four 996 tone resource units (RU4*996) with a 320MHz bandwidth of 802.11be is mapped to an 8000MHz channel bandwidth for the OCB at 7.781GHz.

[0081] In some implementations, under option 4-a and design 1000, the specific parameter set design may include at least the following: (a) for a 500MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =500MHz, N fft =256, N sd =234, N sp =8, N dc =3, N st=242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1000MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =1000MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 2000MHz channel bandwidth, choosing ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s＝ 2000MHz, N fft =1024, N sd =980, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for the 996 tone resource unit (RU996).

[0082] In some implementations, under option 4-b and design 1100, the specific parameter set design may include at least the following: (a) for a 500MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =500MHz, N fft=256, N sd =234, N sp =8, N dc =3, N st =242, N guard = (6, 5), and tone planning for 242 tone resource units (RU242); (b) for a 1000MHz channel bandwidth, select ΔF = 1.953125MHz, T dft =0.512μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =1000MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =484, N guard = (12, 11), and tone planning for 484 tone resource units (RU484); and (c) for a 2000MHz channel bandwidth, choosing ΔF = 3.90625MHz, T dft =0.256μs, T gi,short =0.016μs, T gi,normal =0.032μs, T gi,long =0.064μs, T sym =T dft +T gi F s =2000MHz, N fft =512, N sd =468, N sp =16, N dc =5, N st =996, N guard = (12, 11), and tone planning for RU484.

[0083] Supplementary Explanation

[0084] The topics described herein sometimes illustrate different components contained within or connected to other components. It is to be understood that the architectures depicted are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components that achieve the same functionality is effectively “associated” to enable the desired functionality. Therefore, independent of architecture or intermediate components, any two components combined herein to achieve a particular function can be considered “associated” with each other to enable the desired functionality. Similarly, any two such associated components can also be considered “operationally connected” or “operationally coupled” to each other to achieve the desired functionality, and any two components that can be so associated can also be considered “operationally coupled” to each other to achieve the desired functionality. Specific examples of operationally coupled components include, but are not limited to, physically mating and / or physically interacting components and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0085] Furthermore, regarding the extensive use of any plural and / or singular terms herein, those skilled in the art can convert from plural to singular and / or from singular to plural as needed, depending on the context and / or application. For clarity, various singular / plural reciprocities may be explicitly stated herein.

[0086] Furthermore, those skilled in the art will understand that, generally, the terms used herein, and especially in the appended claims (e.g., the body of the appended claims), are generally meant as “open” terms; for example, the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” and so on. Those skilled in the art will also understand that if a particular number listed in the introduced claim is intentional, such intention will be explicitly listed in the claim, and such intention will not exist where such listing is absent. For example, to aid understanding, the appended claims may contain the use of the introductory phrases “at least one” and “one or more” that list the introduced claims. However, the use of such phrases should not be construed as implying that the introduction of the indefinite article "a" or "an" limits any particular claim containing such an introduced claim list to containing only one implementation of such a list, even when the same claim includes the introductory phrase "a or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a and / or one" should be interpreted as meaning "at least one" or "one or more"). This also applies to the use of definite articles used to introduce the claim list. Furthermore, even when a specific number of introduced claim lists is explicitly listed, those skilled in the art will recognize that such a list should be interpreted as meaning at least the number listed (e.g., in the absence of other modifiers, an unobstructed list of "two lists" means at least two lists or two or more lists). Furthermore, in cases where the convention of “at least one of A, B, and C” is used, in the sense that a person skilled in the art would understand this convention to mean, such an interpretation (e.g., “a system having at least one of A, B, and C” will include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together, etc.). In cases where the convention of “at least one of A, B, or C” is used, in the sense that a person skilled in the art would understand this convention to mean, such an interpretation (e.g., “a system having at least one of A, B, or C” will include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together, etc.). A person skilled in the art will also understand that any transitional words and / or phrases that actually present two or more alternative items, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one, any, or both of these items. For example, the phrase “A or B” would be understood to include the possibility of “A” or “B” or “A and B”.

[0087] Based on the foregoing, it will be understood that various implementations of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various implementations disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the appended claims.

Claims

1. A wireless communication method, the method comprising the following steps: The first device wirelessly communicates with the second device in the 60 GHz band via any one or both of the following: Sending first data or first information to the second device; and receiving second data or second information from the second device. The wireless communication in the 60 GHz band includes designing wireless communication in the 60 GHz band based on a specific set of parameters with a specific selection of subcarrier frequency spacing; The selection of the specific subcarrier frequency spacing includes selecting a subcarrier frequency spacing ΔF such that ΔF is a multiple of the IEEE 802.11be subcarrier frequency spacing, such that ΔF = α. 78.125 kHz, or the subcarrier frequency spacing ΔF is a multiple of the IEEE 802.11ac subcarrier frequency spacing, such that ΔF = α 312.5 kHz, where α is a positive integer and represents the scaling factor.

2. The method according to claim 1, wherein, The specific parameter set design also includes at least one of the following: Selection of specific protection interval (GI) design; and Reuse of pre-existing channelization or tone planning.

3. The method according to claim 2, wherein, The selection of a specific GI design includes choosing a GI from a number of options, including: Short GI, where Tgi, short = Tdft / 32; Normal GI, where Tgi, normal = Tdft / 16; and long GI, where Tgi, long = Tdft / 8; Where Tgi represents the duration of GI, and Where Tdft represents the duration of an OFDM symbol.

4. The method according to claim 2, wherein, The reuse of the pre-existing channelization or tone plan includes the reuse of IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11ay, or IEEE 802.11be channelization or tone plans.

5. The method according to claim 1, wherein, The specific parameter set design includes: For a 540 MHz channel bandwidth, a single 242 tone resource unit RU242 tone planning of 20 MHz bandwidth according to IEEE 802.11be will be mapped to a 540 MHz channel bandwidth with an occupied channel bandwidth OCB of 0.51 GHz; For a 1080 MHz channel bandwidth, a single 484 tone resource unit RU484 tone planning of 40 MHz bandwidth according to IEEE 802.11be will be mapped to a 1080 MHz channel bandwidth with an OCB of 1.02 GHz; For a 2160 MHz channel bandwidth, a single 996 tone resource unit RU996 tone plan of 80 MHz bandwidth according to IEEE 802.11be will be mapped to a 2160 MHz channel bandwidth with an OCB of 2.1 GHz; For a channel bandwidth of 4320 MHz, two 996-tone resource units RU2 with a bandwidth of 160 MHz will be used, according to IEEE 802.11be. The 996 tone plan is mapped to a 4320 MHz channel bandwidth of 4.2 GHz for the OCB; For a channel bandwidth of 6480 MHz, three 996-tone resource units RU3 with a bandwidth of 240 MHz will be used, according to IEEE 802.11be. The 996 tone plan is mapped to a 6480 MHz channel bandwidth of 6.3 GHz for the OCB; and For an 8640 MHz channel bandwidth, four 996-tone resource units RU4 will be used, based on the 320 MHz bandwidth of IEEE 802.11be. The 996 tone plan is mapped to an 8640 MHz channel bandwidth of 8.4 GHz in the OCB.

6. The method according to claim 1, wherein, The specific parameter set design includes: For a 540 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 2.109375 MHz, OFDM symbol duration Tdft = 0.474 μs, short guard interval (GI) duration Tgi, short = 0.015 μs, normal GI duration Tgi, normal = 0.030 μs, long GI duration Tgi, long = 0.059 μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 540 MHz, number of Fast Fourier Transform (FFT) subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 1080 MHz channel bandwidth, the following parameters are selected: ΔF = 2.109375 MHz, Tdft = 0.474 μs, Tgi, short = 0.015 μs, Tgi, normal = 0.030 μs, Tgi, long = 0.059 μs, Tsym = Tdft + Tgi, Fs = 1080 MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for the 484 tone resource unit RU484; and For a channel bandwidth of 2160 MHz, the following parameters are selected: ΔF = 2.109375 MHz, Tdft = 0.474μs, Tgi, short = 0.015μs, Tgi, normal = 0.030μs, Tgi, long = 0.059μs, Tsym = Tdft + Tgi, Fs = 2160MHz, Nfft = 1024, Nsd = 980, Nsp = 16, Ndc = 5, Nst = 996, Nguard = (12, 11), and tone planning for tone resource unit RU996.

7. The method according to claim 1, wherein, The specific parameter set design includes: For a 540 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 2.109375 MHz, OFDM symbol duration Tdft = 0.474 μs, GI duration Tgi, short = 0.015 μs, normal GI duration Tgi, normal = 0.030 μs, long GI duration Tgi, long = 0.059 μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 540 MHz, number of FFT subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 1080 MHz channel bandwidth, the following parameters are selected: ΔF = 4.21875 MHz, Tdft 0.237 μs, Tgi, short = 0.015 μs, Tgi, normal = 0.030 μs, Tgi, long = 0.059 μs, Tsym = Tdft + Tgi, Fs = 1080 MHz, Nfft = 256, Nsd = 234, Nsp = 8, Ndc = 3, Nst = 242, Nguard = (6, 5), and tone planning for RU242; and For a channel bandwidth of 2160 MHz, the following parameters are selected: ΔF = 4.21875 MHz, Tdft = 0.237μs, Tgi, short = 0.015μs, Tgi, normal = 0.030μs, Tgi, long = 0.059μs, Tsym = Tdft + Tgi, Fs = 2160 MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for the 484 tone resource unit RU484.

8. The method according to claim 1, wherein, The specific parameter set design includes: For a 480 MHz channel bandwidth, a single 242 tone resource unit RU242 tone plan of 20 MHz bandwidth according to IEEE 802.11ax or 802.11be will be mapped to a 480 MHz channel bandwidth with an OCB of 0.45375 GHz; For a 960 MHz channel bandwidth, a single 484 tone resource unit RU484 tone planning of 40 MHz bandwidth according to IEEE 802.11ax or IEEE 802.11be will be mapped to a 960 MHz channel bandwidth with an OCB of 0.9075 GHz. For a 1920 MHz channel bandwidth, a single 996 tone resource unit RU996 tone plan will be mapped to a 1920 MHz channel bandwidth with an OCB of 1.8675 GHz according to IEEE 802.11ax or IEEE 802.11be. For a channel bandwidth of 3840 MHz, two 996-tone resource units RU2 with a bandwidth of 160 MHz will be used, according to IEEE 802.11ax or IEEE 802.11be. The 996 tone plan is mapped to a 3840MHz channel bandwidth of 3.375 GHz for the OCB; For a channel bandwidth of 5760 MHz, three 996-tone resource units RU3 with a bandwidth of 240 MHz will be used, according to IEEE 802.11be. The 996-tone plan is mapped to a 5760 MHz channel bandwidth of 5.6025 GHz for the OCB; and For a channel bandwidth of 7680 MHz, four 996-tone resource units RU4 will be used, based on the 320 MHz bandwidth of IEEE 802.11be. The 996 tone plan is mapped to a 7680 MHz channel bandwidth of 7.47 GHz for the OCB.

9. The method according to claim 1, wherein, The specific parameter set design includes: For a 480 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 1.875 MHz, OFDM symbol duration Tdft = 0.533μs, short GI duration Tgi, short = 0.017μs, normal GI duration Tgi, normal = 0.033μs, long GI duration Tgi, long = 0.067μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 480 MHz, number of FFT subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 960 MHz channel bandwidth, the following parameters are selected: ΔF = 1.875 MHz, Tdft = 0.533μs, Tgi, short = 0.017μs, Tgi, normal = 0.033μs, Tgi, long = 0.067μs, Tsym = Tdft + Tgi, Fs = 960MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for the 484 tone resource unit RU484; and For a 1920 MHz channel bandwidth, the following parameters are selected: ΔF = 1.875 MHz, Tdft = 0.533μs, Tgi, short = 0.017μs, Tgi, normal = 0.033μs, Tgi, long = 0.067μs, Tsym = Tdft + Tgi, Fs = 1920MHz, Nfft = 1024, Nsd = 980, Nsp = 16, Ndc = 5, Nst = 996, Nguard = (12, 11), and tone planning for the 996 tone resource unit RU996.

10. The method according to claim 1, wherein, The specific parameter set design includes: For a 480 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 1.875 MHz, OFDM symbol duration Tdft = 0.533μs, short GI duration Tgi, short = 0.017μs, normal GI duration Tgi, normal = 0.033μs, long GI duration Tgi, long = 0.067μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 480 MHz, number of FFT subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 960 MHz channel bandwidth, the following parameters are selected: ΔF = 1.875 MHz, Tdft = 0.533μs, Tgi, short = 0.017μs, Tgi, normal = 0.033μs, Tgi, long = 0.067μs, Tsym = Tdft + Tgi, Fs = 960MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for the 484 tone resource unit RU484; and For a 1920 MHz channel bandwidth, the following parameters are selected: ΔF = 3.75 MHz, Tdft = 0.267μs, Tgi, short = 0.017μs, Tgi, normal = 0.033μs, Tgi, long = 0.067μs, Tsym = Tdft + Tgi, Fs = 1920MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for RU484.

11. The method according to claim 1, wherein, The specific parameter set design includes: For a 520 MHz channel bandwidth, a single 242 tone resource unit RU242 tone plan of 20 MHz bandwidth according to IEEE 802.11ax or 802.11be will be mapped to a 520 MHz channel bandwidth with an OCB of 0.492 GHz; For a 1040 MHz channel bandwidth, a single 484 tone resource unit RU484 tone planning of 40 MHz bandwidth according to IEEE 802.11ax or IEEE 802.11be will be mapped to a 1040 MHz channel bandwidth with an OCB of 0.983 GHz. For a 2080 MHz channel bandwidth, a single 996 tone resource unit RU996 tone plan will be mapped to a 2080 MHz channel bandwidth with an OCB of 2.023 GHz according to IEEE 802.11ax or IEEE 802.11be. For a channel bandwidth of 4160 MHz, two 996-tone resource units RU2 will be used, based on the 160 MHz bandwidth of IEEE 802.11ax or IEEE 802.11be. The 996 tone plan is mapped to a 4160MHz channel bandwidth of 4.046 GHz in the OCB; For a channel bandwidth of 6240 MHz, three 996-tone resource units RU3 will be used, based on the 240 MHz bandwidth of IEEE 802.11be. The 996 tone plan is mapped to a 6240 MHz channel bandwidth of 6.070 GHz at the OCB; and For an 8320 MHz channel bandwidth, four 996-tone resource units RU4 will be used, based on the 320 MHz bandwidth of IEEE 802.11be. The 996 tone plan is mapped to an 8320 MHz channel bandwidth of 8.093 GHz in the OCB.

12. The method according to claim 1, wherein, The specific parameter set design includes: For a 520 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 2.03125 MHz, OFDM symbol duration Tdft = 0.492 μs, short GI duration Tgi, short = 0.015 μs, normal GI duration Tgi, normal = 0.031 μs, long GI duration Tgi, long = 0.062 μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 520 MHz, number of FFT subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 1040 MHz channel bandwidth, the following parameters are selected: ΔF = 2.03125 MHz, Tdft = 0.492 μs, Tgi, short = 0.015 μs, Tgi, normal = 0.031 μs, Tgi, long = 0.062 μs, Tsym = Tdft + Tgi, Fs = 1040 MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for the 484 tone resource unit RU484; and For a 2080 MHz channel bandwidth, the following parameters are selected: ΔF = 2.03125 MHz, Tdft = 0.492μs, Tgi, short = 0.015μs, Tgi, normal = 0.031μs, Tgi, long = 0.062μs, Tsym = Tdft + Tgi, Fs = 2080 MHz, Nfft = 1024, Nsd = 980, Nsp = 16, Ndc = 5, Nst = 996, Nguard = (12, 11), and tone planning for the 996 tone resource unit RU996.

13. The method according to claim 1, wherein, The specific parameter set design includes: For a 520 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 2.03125 MHz, OFDM symbol duration Tdft = 0.492 μs, short GI duration Tgi, short = 0.015 μs, normal GI duration Tgi, normal = 0.031 μs, long GI duration Tgi, long = 0.062 μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 520 MHz, number of FFT subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 1040 MHz channel bandwidth, the following parameters are selected: ΔF = 4.0625 MHz, Tdft = 0.246 μs, Tgi, short = 0.015 μs, Tgi, normal = 0.031 μs, Tgi, long = 0.062 μs, Tsym = Tdft + Tgi, Fs = 1040 MHz, Nfft = 256, Nsd = 234, Nsp = 8, Ndc = 3, Nst = 242, Nguard = (6, 5), and tone planning for RU242; and For a 2080 MHz channel bandwidth, the following parameters are selected: ΔF = 4.0625 MHz, Tdft = 0.246μs, Tgi, short = 0.015μs, Tgi, normal = 0.031μs, Tgi, long = 0.062μs, Tsym = Tdft + Tgi, Fs = 2080 MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for 484 tone resource units (RU484).

14. The method according to claim 1, wherein, The specific parameter set design includes: For a 500 MHz channel bandwidth, a single 242 tone resource unit RU242 tone plan of 20 MHz bandwidth according to IEEE 802.11ax or 802.11be will be mapped to a 500 MHz channel bandwidth with an OCB of 0.473 GHz; For a 1000 MHz channel bandwidth, a single 484 tone resource unit RU484 tone planning of 40 MHz bandwidth according to IEEE 802.11ax or IEEE 802.11be will be mapped to a 1000 MHz channel bandwidth with an OCB of 0.945 GHz. For a 2000 MHz channel bandwidth, a single 996 tone resource unit RU996 tone plan will be mapped to a 2000 MHz channel bandwidth with an OCB of 1.945 GHz according to IEEE 802.11ax or IEEE 802.11be. For a 4000 MHz channel bandwidth, two 996-tone resource units RU2 with a bandwidth of 160 MHz will be used, according to IEEE 802.11ax or IEEE 802.11be. The 996 tone plan is mapped to a 4000MHz channel bandwidth of 3.890 GHz for the OCB; For a channel bandwidth of 6000 MHz, three 996-tone resource units RU3 with a bandwidth of 240 MHz will be used, according to IEEE 802.11be. The 996-tone plan is mapped to a 6000 MHz channel bandwidth of 5.836 GHz at the OCB; and For an 8000 MHz channel bandwidth, four 996-tone resource units RU4 will be used, based on the 320 MHz bandwidth of IEEE 802.11be. The 996 tone plan is mapped to an 8000 MHz channel bandwidth of 7.781 GHz in the OCB.

15. The method according to claim 1, wherein, The specific parameter set design includes: For a 500 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 1.953125 MHz, OFDM symbol duration Tdft = 0.512 μs, short GI duration Tgi, short = 0.016 μs, normal GI duration Tgi, normal = 0.032 μs, long GI duration Tgi, long = 0.064 μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 500 MHz, number of FFT subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 1000 MHz channel bandwidth, the following parameters are selected: ΔF = 1.953125 MHz, Tdft = 0.512 μs, Tgi, short = 0.016 μs, Tgi, normal = 0.032 μs, Tgi, long = 0.064 μs, Tsym = Tdft + Tgi, Fs = 1000 MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for the 484 tone resource unit RU484; and For a 2000 MHz channel bandwidth, the following parameters are selected: ΔF = 1.953125 MHz, Tdft = 0.512μs, Tgi, short = 0.016μs, Tgi, normal = 0.032μs, Tgi, long = 0.064μs, Tsym = Tdft + Tgi, Fs = 2000MHz, Nfft = 1024, Nsd = 980, Nsp = 16, Ndc = 5, Nst = 996, Nguard = (12, 11), and tone planning for the 996 tone resource unit RU996.

16. The method according to claim 1, wherein, The specific parameter set design includes: For a 500 MHz channel bandwidth, the following subcarrier frequency spacing is selected: ΔF = 1.953125 MHz, OFDM symbol duration Tdft = 0.512 μs, short GI duration Tgi, short = 0.016 μs, normal GI duration Tgi, normal = 0.032 μs, long GI duration Tgi, long = 0.064 μs, symbol duration Tsym = Tdft + Tgi, sampling frequency Fs = 500 MHz, number of FFT subcarriers Nfft = 256, number of data carrier subcarriers Nsd = 234, number of pilot tone subcarriers Nsp = 8, number of DC tones Ndc = 3, total number of subcarriers Nst = 242, number of left and right guard tones Nguard = (6, 5), and tone planning for 242 tone resource units RU242; For a 1000 MHz channel bandwidth, the following parameters are selected: ΔF = 1.953125 MHz, Tdft = 0.512 μs, Tgi, short = 0.016 μs, Tgi, normal = 0.032 μs, Tgi, long = 0.064 μs, Tsym = Tdft + Tgi, Fs = 1000 MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 484, Nguard = (12, 11), and tone planning for the 484 tone resource unit RU484; and For a 2000 MHz channel bandwidth, the following parameters are selected: ΔF = 3.90625 MHz, Tdft = 0.256μs, Tgi, short = 0.016μs, Tgi, normal = 0.032μs, Tgi, long = 0.064μs, Tsym = Tdft + Tgi, Fs = 2000 MHz, Nfft = 512, Nsd = 468, Nsp = 16, Ndc = 5, Nst = 996, Nguard = (12, 11), and tone planning for RU484.

17. A wireless communication device, the device comprising: A transceiver configured to perform wireless communication; as well as A processor, coupled to the transceiver and configured to perform operations including: The transceiver enables wireless communication with another device in the 60 GHz band via any one or both of the following: Sending first data or first information to the other device; and receiving second data or second information from the other device. In the wireless communication within the 60 GHz band, the processor is configured to communicate wirelessly within the 60 GHz band based on a specific set of parameters selected with specific subcarrier frequency spacing. The selection of the specific subcarrier frequency spacing includes selecting a subcarrier frequency spacing ΔF such that ΔF is a multiple of the IEEE 802.11be subcarrier frequency spacing, such that ΔF = α. 78.125 kHz, or the subcarrier frequency spacing ΔF is a multiple of the IEEE 802.11ac subcarrier frequency spacing, such that ΔF = α 312.5 kHz, where α is a positive integer and represents the scaling factor.

18. The apparatus according to claim 17, wherein, The specific parameter set design also includes at least one of the following: Selection of specific protection interval (GI) design; and Reuse of pre-existing channelization or tone planning.

19. The apparatus according to claim 18, wherein, The selection of a specific GI design includes choosing a GI from a number of options, including: Short GI, where Tgi, short = Tdft / 32; Normal GI, where Tgi, normal = Tdft / 16; and long GI, where Tgi, long = Tdft / 8; Where Tgi represents the duration of GI, and Where Tdft represents the duration of an OFDM symbol.

20. The apparatus according to claim 18, wherein, The reuse of the pre-existing channelization or tone plan includes the reuse of IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11ay, or IEEE 802.11be channelization or tone plans.

Images