Method and apparatus for transmitting / receiving physical layer protocol data units

Abstract

The application provides a method for transmitting a physical layer protocol data unit, comprising: generating a physical layer protocol data unit (PPDU), wherein the PPDU comprises a long training field (LTF), and a length of a frequency domain sequence of the LTF is greater than a first length, and the first length is a length of a frequency domain sequence of the LTF of a PPDU transmitted on a channel with a bandwidth of 160 MHz; and transmitting the PPDU on a target channel, wherein a bandwidth of the target channel is greater than 160 MHz. The frequency domain sequence of the LTF provided by the embodiments of the application considers non-pilot position phase flipping, various puncturing modes of 240M / 320M, and multi-RU merging, and finally provides a frequency domain sequence of the LTF with a lower PAPR value under various puncturing modes of 240M / 320M and on the merged multi-RU.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a method and apparatus for transmitting / receiving physical layer protocol data units. Background Technology

[0002] With the development of mobile internet and the popularization of smart terminals, data traffic is growing rapidly, and users' demands for communication service quality are also increasing. The IEEE 802.11ax standard is no longer able to meet users' needs in terms of high throughput, low jitter, and low latency. Therefore, there is an urgent need to develop the next generation of wireless local area network (WLAN) technology, namely the IEEE 802.11be standard.

[0003] Unlike IEEE 802.11ax, IEEE 802.11be will employ ultra-large bandwidths, such as 240MHz and 320MHz, to achieve ultra-high transmission rates and support ultra-dense user scenarios. Therefore, how to design long training field (LTF) sequences for such larger channel bandwidths is a question worthy of attention. Summary of the Invention

[0004] This application provides a method and apparatus for transmitting physical layer protocol data units, which can design long training domain sequences for larger channel bandwidths.

[0005] In a first aspect, a method for transmitting physical layer protocol data units is provided, comprising: generating a physical layer protocol data unit (PPDU), the PPDU including a long training field (LTF), wherein the length of the frequency domain sequence of the LTF is greater than a first length, the first length being the length of the frequency domain sequence of the LTF of the PPDU transmitted on a channel with a bandwidth of 160MHz; and transmitting the PPDU on a target channel, wherein the bandwidth of the target channel is greater than 160MHz.

[0006] The frequency domain sequence of the LTF provided in this application takes into account phase reversal at non-pilot positions, multiple puncturing methods at 240M / 320M, and merging of multiple RUs. The final frequency domain sequence of the LTF has a low PAPR value under multiple puncturing methods at 240M / 320M and under the merged multiple RUs.

[0007] Secondly, a method for receiving a physical layer protocol data unit is provided, comprising: receiving a physical layer protocol data unit (PPDU), wherein the PPDU includes a long training field (LTF), the length of the frequency domain sequence of the LTF is greater than a first length, the first length being the length of the frequency domain sequence of the LTF of the PPDU transmitted on a channel with a bandwidth of 160MHz; and parsing the PPDU.

[0008] The frequency domain sequence of the LTF received in this application embodiment has a low PAPR value under various puncturing methods at 240M / 320M and on multiple merged RUs. Attached Figure Description

[0009] Figure 1 This is a schematic diagram of a communication system applicable to the methods of the embodiments of this application;

[0010] Figure 2 This is an internal structure diagram of the access point applicable to embodiments of this application;

[0011] Figure 3 This is an internal structure diagram of the site applicable to the embodiments of this application;

[0012] Figure 4 It is an 80MHz tone plan;

[0013] Figure 5 This is a flowchart of a method according to an embodiment of this application. Detailed Implementation

[0014] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0015] The technical solutions of this application embodiment can be applied to various communication systems, such as: wireless local area network (WLAN) communication systems, global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) systems, general packet radio service (GPRS), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems, or new radio (NR), etc.

[0016] The following is an illustrative example, using a WLAN system as an example, to describe the application scenarios and methods of the embodiments of this application.

[0017] Specifically, the embodiments of this application can be applied to wireless local area networks (WLANs), and can be applied to any of the protocols in the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series currently used in WLANs. A WLAN may include one or more basic service sets (BSSs), and the network nodes in the basic service set include access points (APs) and stations (STAs).

[0018] In this embodiment, the initiating device can be a STA in a WLAN, and correspondingly, the responding device is an AP in a WLAN. Of course, in this embodiment, the initiating device can also be an AP in a WLAN, and the responding device can be a STA in a WLAN.

[0019] To facilitate understanding of the embodiments of this application, let's first take... Figure 1 The communication system shown in the diagram is used as an example to describe in detail the communication system applicable to the embodiments of this application. For example... Figure 1 The system shown in the scenario could be a WLAN system. Figure 1 A WLAN system may include one or more access points (APs) and one or more STAs. Figure 1 Take one access point (AP) and three STAs as an example. The AP and STAs can communicate wirelessly using various standards. For example, the AP and STAs can use single-user multiple-input multiple-output (SU-MIMO) or multi-user multiple-input multiple-output (MU-MIMO) technology for wireless communication.

[0020] An AP, also known as a wireless access point or hotspot, is an access point for mobile users to access a wired network. It is primarily deployed in homes, buildings, and campuses, but can also be deployed outdoors. An AP acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet. Specifically, an AP can be a terminal device or network device with a wireless fidelity (WiFi) chip. Optionally, an AP can be a device that supports multiple WLAN standards such as 802.11. Figure 2 The diagram shows the internal structure of an AP product, which can be either multi-antenna or single-antenna. Figure 2 In this application, the access point (AP) includes physical layer (PHY) processing circuitry and media access control (MAC) processing circuitry. The PHY processing circuitry processes physical layer signals, and the MAC processing circuitry processes MAC layer signals. The 802.11 standard focuses on the PHY and MAC components; this application's embodiments focus on the protocol design for the MAC and PHY.

[0021] STA products are typically terminal products that support the 802.11 series standards, such as mobile phones and laptops. Figure 3 The diagram shows the structure of a single-antenna STA. In real-world scenarios, a STA can also have multiple antennas, and may even be a device with two or more antennas. Figure 3In this context, the STA can include physical layer (PHY) processing circuitry and media access control (MAC) processing circuitry. The physical layer processing circuitry can be used to process physical layer signals, and the MAC layer processing circuitry can be used to process MAC layer signals.

[0022] The following describes embodiments of this application and related content.

[0023] First, let me introduce several contents related to the embodiments of this application:

[0024] 1. 11be carrier planning (tone plan)

[0025] 11be 80MHz subcarrier design as follows Figure 4 As shown, 240MHz and 320MHz bandwidths have been added to 11be. The 240MHz bandwidth is the direct splicing of three 11be 80MHz subcarriers, and the 320MHz bandwidth is the direct splicing of four 11be 80MHz subcarriers.

[0026] in, Figure 4 In the design of the 80MHz subcarrier, the data subcarrier and pilot subcarrier indices of RU 26 are shown in Table 1.

[0027] Table 1

[0028]

[0029]

[0030] Note: Each row in columns 2 and 3 of Table 1 indicates a RU. For example, the last row in column 2 indicates RU18 [-38-13], where RU18 is located from subcarrier number -38 to subcarrier number -13. Column 4 indicates the pilot subcarrier indices in the corresponding 26-tone RUs in sequence. For example, the first 26-tone RU consists of subcarrier number -499 to subcarrier number -474, where the pilot subcarriers are subcarrier number -494 and subcarrier number -480.

[0031] It should be understood that the table below expresses the same meaning, and this meaning will not be repeated below.

[0032] in, Figure 4 In the design of the 80MHz subcarrier, the data subcarrier and pilot subcarrier indices of RU 52 are shown in Table 2.

[0033] Table 2

[0034]

[0035] in, Figure 4 In the design of the 80MHz subcarrier, the data subcarrier and pilot subcarrier indices of RU 106 are shown in Table 3.

[0036] Table 3

[0037]

[0038]

[0039] in, Figure 4 In the design of the 80MHz subcarrier, the data subcarrier and pilot subcarrier indices of RU 242 are shown in Table 4.

[0040] Table 4

[0041]

[0042] in, Figure 4 In the design of the 80MHz subcarrier, the data subcarrier and pilot subcarrier indices of RU 484 are shown in Table 5. The 80MHz 484-tone RU of 11ax is an RU composed of 484 consecutive subcarriers. Although the 80MHz 484-tone RU of 11be still has 468 data subcarriers and 16 pilot subcarriers, there are 5 DC subcarriers or empty subcarriers in the middle. For example, the first 484-tone RU has subcarrier numbers from -500 to -12, with 5 DC subcarriers numbered as -258, -257, -256, -255, and -254, and 16 pilot subcarriers numbered as -494, -468, -426, -400, -360, -334, -292, -266, -246, -220, -178, -152, -112, -86, -44, and -18.

[0043] Table 5

[0044]

[0045] in, Figure 4In the design of the 80MHz subcarrier, the data subcarrier and pilot subcarrier indices of the RU 996 are shown in Table 6. The 80MHz 996-tone RU of 11be has 980 data subcarriers and 16 pilot subcarriers, with 5 DC subcarriers in between. For example, in the first 484-tone RU, the subcarrier numbers range from -500 to 500, with the 5 DC subcarriers numbered -2, -1, 0, 1, and 2. The 16 pilot subcarriers are numbered -468, -400, -334, -266, -220, -152, -86, -18, +18, +86, +152, +220, +266, +334, +400, and +468.

[0046] Table 6

[0047]

[0048] The LTF sequence provided in this application embodiment is used on a 240MHz bandwidth and a 320MHz bandwidth, wherein the 240MHz bandwidth and the 320MHz bandwidth are determined by, for example, Figure 4 The tone plan shown is constructed.

[0049] The design of the 160MHz bandwidth subcarrier is based on two 80MHz subcarriers, [RU subcarrier index in 80MHz, pilot position subcarrier index]-521:80MHz[RU subcarrier index in 80MHz, pilot position subcarrier index]+521.

[0050] The 240MHz bandwidth is based on three 80MHz bands.

[0051] The design of the 320MHz bandwidth subcarrier is based on two 160MHz (Pilot indices in 160MHz)-1024 (Pilot indices in 160MHz)+1024.

[0052] 2. 240MHz and 320MHz punching methods

[0053] A bitmap is used to represent the puncturing method. Each bit indicates whether a 20MHz channel is punctured or not. For example, "0" indicates that the corresponding 20MHz channel is punctured, and "1" indicates that the corresponding 20MHz channel is not punctured. Optionally, the bits from left to right correspond to 20MHz channels with frequencies ranging from low to high.

[0054] 2-1, 240MHz Drilling Method

[0055] Method 1: [1 1 1 1 1 1 1 1 1 1 1 1 1], with a corresponding channel bandwidth of 240MHz and 3072 subcarriers.

[0056] Method 2: [0 0 1 1 1 1 1 1 1 1 1 1], the corresponding available channel bandwidth is 200MHz.

[0057] Method 3: [1 1 0 0 1 1 1 1 1 1 1 1], the corresponding available channel bandwidth is 200MHz.

[0058] Method 4: [1 1 1 1 0 0 1 1 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0059] Method 5: [1 1 1 1 1 1 0 0 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0060] Method 6: [1 1 1 1 1 1 1 1 1 0 0 1 1], the corresponding available channel bandwidth is 200MHz.

[0061] Method 7: [1 1 1 1 1 1 1 1 1 1 1 0 0], the corresponding available channel bandwidth is 200MHz.

[0062] Method 8: [0 0 0 0 1 1 1 1 1 1 1 1 1], corresponding to an available channel bandwidth of 160MHz.

[0063] Method 9: [1 1 1 1 0 0 0 0 1 1 1 1], the corresponding available channel bandwidth is 160MHz.

[0064] Method 10: [1 1 1 1 1 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 160MHz.

[0065] 2-2, 320MHz Drilling Method

[0066] Specifically, the channel puncturing method for 320MHz can be divided into two types: one is 240MHz compatible puncturing, and the other is incompatible with 240MHz puncturing. Among them, "compatible" means that after puncturing 320MHz to form 240MHz, puncturing is carried out on the basis of the 240MHz formed by puncturing, that is, the 240MHz formed after puncturing is further punctured.

[0067] A. 320MHz channel bandwidth compatible with 240MHz channel puncturing.

[0068] Method 1: [1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1], with a corresponding channel bandwidth of 320MHz and 4096 subcarriers.

[0069] Method 2: [0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0070] Method 3: [1 1 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0071] Method 4: [1 1 1 1 0 0 1 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0072] Method 5: [1 1 1 1 1 1 0 0 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0073] Method 6: [1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0074] Method 7: [1 1 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0075] Method 8: [1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 1 1], with a corresponding available channel bandwidth of 280MHz.

[0076] Method 9: [1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0], the corresponding available channel bandwidth is 280MHz.

[0077] Method 10: [1 1 1 1 0 0 0 0 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 240MHz.

[0078] Method 11: [1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1], with a corresponding available channel bandwidth of 240MHz.

[0079] Method 12: [1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0], with a corresponding available channel bandwidth of 240MHz.

[0080] Method 13: [0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 240MHz.

[0081] Based on the 240MHz available channel bandwidth formed by method 10, further puncturing is performed to obtain puncturing methods 14 to 22:

[0082] Method 14: [0 0 1 1 0 0 0 0 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0083] Method 15: [1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0084] Method 16: [1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1], the corresponding available channel bandwidth is 200MHz.

[0085] Method 17: [1 1 1 1 0 0 0 0 1 1 0 0 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0086] Method 18: [1 1 1 1 0 0 0 0 1 1 1 1 0 0 1 1], the corresponding available channel bandwidth is 200MHz.

[0087] Method 19: [1 1 1 1 0 0 0 0 1 1 1 1 1 1 0 0], the corresponding available channel bandwidth is 200MHz.

[0088] Method 20: [0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 160MHz.

[0089] Method 21: [1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1], with a corresponding available channel bandwidth of 160MHz.

[0090] Method 22: [1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 160MHz.

[0091] Based on the 240MHz available channel bandwidth formed by method 11, further puncturing is performed to obtain puncturing methods 23 to 31:

[0092] Method 23: [0 0 1 1 1 1 1 1 0 0 0 0 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0093] Method 24: [1 1 0 0 1 1 1 1 0 0 0 0 1 1 1 1], the corresponding available channel bandwidth is 200MHz.

[0094] Method 25: [1 1 1 1 0 0 1 1 0 0 0 0 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0095] Method 26: [1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1], the corresponding available channel bandwidth is 200MHz.

[0096] Method 27: [1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 1], with a corresponding available channel bandwidth of 200MHz.

[0097] Method 28: [1 1 1 1 1 1 1 1 1 0 0 0 0 1 1 0 0], the corresponding available channel bandwidth is 200MHz.

[0098] Method 29: [0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1], the corresponding available channel bandwidth is 160MHz.

[0099] Method 30: [1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1], with a corresponding available channel bandwidth of 160MHz.

[0100] Method 31: [1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0], with a corresponding available channel bandwidth of 160MHz.

[0101] Based on the 240MHz available channel bandwidth formed by method 12, further puncturing is performed to obtain puncturing methods 32 to 40:

[0102] Method 32: [0 0 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 200MHz.

[0103] Method 33: [1 1 0 0 1 1 1 1 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 200MHz.

[0104] Method 34: [1 1 1 1 0 0 1 1 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 200MHz.

[0105] Method 35: [1 1 1 1 1 1 0 0 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 200MHz.

[0106] Method 36: [1 1 1 1 1 1 1 1 1 0 0 1 1 0 0 0 0], the corresponding available channel bandwidth is 200MHz.

[0107] Method 37: [1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0], the corresponding available channel bandwidth is 200MHz.

[0108] Method 38: [0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 160MHz.

[0109] Method 39: [1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 160MHz.

[0110] Method 40: [1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0], with a corresponding available channel bandwidth of 160MHz.

[0111] Based on the 240MHz available channel bandwidth formed by method 13, further puncturing is performed using puncturing methods 32 to 40:

[0112] Method 41: [0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0113] Method 42: [0 0 0 0 1 1 0 0 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0114] Method 43: [0 0 0 0 1 1 1 1 0 0 1 1 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0115] Method 44: [0 0 0 0 1 1 1 1 1 1 0 0 1 1 1 1], with a corresponding available channel bandwidth of 200MHz.

[0116] Method 45: [0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 1 1], with a corresponding available channel bandwidth of 200MHz.

[0117] Method 46: [0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 0 0], the corresponding available channel bandwidth is 200MHz.

[0118] Method 47: [0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 160MHz.

[0119] Method 48: [0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1], with a corresponding available channel bandwidth of 160MHz.

[0120] Method 49: [0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 160MHz.

[0121] B. 320MHz channel bandwidth is incompatible with 240MHz channel puncturing.

[0122] Method 1: 320MHz [1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1], with a corresponding channel bandwidth of 320MHz and 4096 subcarriers.

[0123] Method 2: 280MHz [0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1], corresponding to an available channel bandwidth of 280MHz.

[0124] Method 3: 280MHz [1 1 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0125] Method 4: 280MHz [1 1 1 1 0 0 1 1 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0126] Method 5: 280MHz [1 1 1 1 1 1 0 0 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0127] Option 6: 280MHz [1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0128] Method 7: 280MHz [1 1 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1], with a corresponding available channel bandwidth of 280MHz.

[0129] Method 8: 280MHz [1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 1 1], the corresponding available channel bandwidth is 280MHz.

[0130] Method 9: 280MHz [1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0], the corresponding available channel bandwidth is 280MHz.

[0131] Method 10: 240MHz [1 1 1 1 0 0 0 0 1 1 1 1 1 1 1 1 1], with a corresponding available channel bandwidth of 240MHz.

[0132] Method 11: 240MHz [1 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1], the corresponding available channel bandwidth is 240MHz.

[0133] Method 12: 240MHz [1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0], the corresponding available channel bandwidth is 240MHz.

[0134] Method 13: 240MHz [0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1], corresponding to an available channel bandwidth of 240MHz.

[0135] 3. And 240MHz multi-RU merging and 320MHz multi-RU merging

[0136] 2-3, 240MHz multi-RU merging method:

[0137] RU26, RU52, RU26+RU52, RU106, RU26+RU106, RU242, RU484, RU242+RU484, RU996, RU484+RU996, RU242+RU484+RU996, RU484+2*RU996, 3*RU996.

[0138] 2-4, 320MHz multi-RU merging method:

[0139] RU26,RU52,RU26+RU52,RU106,RU26+RU106,RU242,RU484,RU242+RU484,RU996,RU4 84+RU996, RU242+RU484+RU996, RU484+2*RU996, 3*RU996, 3*RU996+RU484, 4*RU996.

[0140] RU2*996 is two RU996 values, which can also be represented as 2*RU996. RU3*996 can also be represented as 3*RU996, and RU4*996 can also be represented as 4*RU996. RUA+RUB is equivalent to RUB+RUA, which refers to the combination or splicing of RUA and RUB.

[0141] The patterns considered for a 1x LTF sequence with a bandwidth of 240MHz are shown in 2-1.

[0142] The patterns considered for 1xLTF sequences with a bandwidth of 320MHz are shown in Figure 2-2.

[0143] The patterns considered for 2xLTF / 4xLTF sequences under a 240MHz bandwidth are shown in Table A below:

[0144] Table A

[0145]

[0146] The 240MHz band is composed of three 80MHz bands, and each 80MHz band contains 36 26-tone RUs, with serial numbers from smallest to largest and corresponding frequencies from lowest to highest. The same applies to 52-tone RUs (RU 52), 106-tone RUs (RU 106), 242-tone RUs (RU242), 484-tone RUs (RU484), and 996-tone RUs (RU996).

[0147] Multi-RU merging involves assigning multiple RUs to a single STA. Each RU still uses its own data subcarrier and pilot subcarrier positions. For example, in RU26+RU52, RU26 uses its own data subcarrier positions and pilot positions, while RU52 uses its own data subcarrier positions and pilot subcarrier indices.

[0148] RU26+RU52 has fixed merging or joint patterns in Table A. There are 4 fixed merging patterns in each 80MHz range, resulting in 12 merging or joint patterns in the 240MHz range, as detailed below:

[0149] The first 80MHz of the 240MHz bandwidth includes:

[0150] The first RU26+RU52: the 8th RU26 and the 3rd RU52;

[0151] The second RU26+RU52: the 11th RU26 and the 6th RU52;

[0152] The third RU26+RU52: the 26th RU26 and the 11th RU52;

[0153] The fourth RU26+RU52: the 29th RU26 and the 14th RU52;

[0154] The second 80MHz of the 240MHz bandwidth includes:

[0155] The fifth RU26+RU52: the 44th RU26 and the 19th RU52;

[0156] The sixth RU26+RU52: the 47th RU26 and the 22nd RU52;

[0157] The seventh RU26+RU52: the 62nd RU26 and the 27th RU52;

[0158] The eighth RU26+RU52: the 65th RU26 and the 30th RU52;

[0159] The fifth RU26+RU52 under the 240MHz bandwidth is the first RU26+RU52 under the second 80MHz bandwidth, and so on.

[0160] The third 80MHz band in the 240MHz bandwidth includes:

[0161] The ninth RU26+RU52: the 80th RU26 and the 35th RU52;

[0162] The tenth RU26+RU52: the 83rd RU26 and the 38th RU52;

[0163] The eleventh RU26+RU52: the 98th RU26 and the 43rd RU52;

[0164] The twelfth RU26+RU52: the 101st RU26 and the 46th RU52;

[0165] The ninth RU26+RU52 under a 240MHz bandwidth is also the first RU26+RU52 under the third 80MHz bandwidth, and so on.

[0166] It should be understood that each 80MHz module has 36 RU26 modules, such as... Figure 4As shown, from left to right (from low frequency to high frequency), they are sequentially designated as the 1st RU26, the 2nd RU26, ..., the 36th RU26. The 240MHz band consists of three 80MHz bands, sequentially designated from left to right (from low frequency to high frequency) as the 1st RU26, the 2nd RU26, ..., the 108th RU26. Specifically, the RU26 contained in the first 80MHz band of the 240MHz band are designated as the 1st RU26, the 2nd RU26, ..., the 36th RU26; the RU26 contained in the second 80MHz band of the 240MHz band are designated as the 37th RU26, the 38th RU26, ..., the 72nd RU26; and the RU26 contained in the third 80MHz band of the 240MHz band are designated as the 73rd RU26, the 78th RU26, ..., the 108th RU26.

[0167] RU26+RU106 have fixed merging or joint patterns in Table A. There are 4 fixed merging patterns in each 80MHz range, resulting in 12 merging or joint patterns in the 240MHz range, as detailed below:

[0168] The first 80MHz of the 240MHz bandwidth includes:

[0169] The first RU26 + RU106: the fifth RU26 and the first RU106;

[0170] The second RU26+RU106: the 14th RU26 and the 4th RU106;

[0171] The third RU26+RU106: the 23rd RU26 and the 5th RU106;

[0172] The fourth RU26+RU106: the 32nd RU26 and the 8th RU106;

[0173] The second 80MHz of the 240MHz bandwidth includes:

[0174] The fifth RU26+RU106: the 41st RU26 and the 9th RU106;

[0175] The sixth RU26+RU106: the 50th RU26 and the 12th RU106;

[0176] The seventh RU26+RU106: the 59th RU26 and the 13th RU106;

[0177] The eighth RU26+RU106: the 68th RU26 and the 16th RU106;

[0178] The fifth RU26+RU106 under the 240MHz bandwidth is the first RU26+RU106 under the second 80MHz bandwidth, and so on.

[0179] The third 80MHz band in the 240MHz bandwidth includes:

[0180] The ninth RU26+RU106: the 77th RU26 and the 17th RU106;

[0181] The tenth RU26+RU106: the 86th RU26 and the 20th RU106;

[0182] The eleventh RU26+RU106: the 95th RU26 and the 21st RU106;

[0183] The twelfth RU26+RU106: the 104th RU26 and the 24th RU106;

[0184] The ninth RU26+RU52 under a 240MHz bandwidth is the first RU26+RU106 under the third 80MHz bandwidth, and so on.

[0185] It should be understood that the Xth RU26 and the Yth RU106 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0186] Among them, RU242+RU484 has fixed merging or joint patterns in Table A. There are 4 fixed merging patterns in each 80MHz range, so there are 12 merging or joint patterns in 240MHz range, as detailed below:

[0187] The first 80MHz of the 240MHz bandwidth includes:

[0188] First RU242+RU484: First RU242 and second RU484;

[0189] The second RU242+RU484: the second RU242 and the second RU484;

[0190] The third RU242+RU484: The third RU242 and the first RU484;

[0191] The fourth RU242+RU484: the fourth RU242 and the first RU484;

[0192] The second 80MHz of the 240MHz bandwidth includes:

[0193] The fifth RU242+RU484: the fifth RU242 and the fourth RU484;

[0194] The sixth RU242+RU484: the sixth RU242 and the fourth RU484;

[0195] The seventh RU242+RU484: the seventh RU242 and the third RU484;

[0196] The eighth RU242+RU484: the eighth RU242 and the third RU484;

[0197] The fifth RU242+RU484 under the 240MHz bandwidth is the first RU242+RU484 under the second 80MHz bandwidth, and so on.

[0198] The third 80MHz band in the 240MHz bandwidth includes:

[0199] The ninth RU242+RU484: the ninth RU242 and the sixth RU484;

[0200] The tenth RU242+RU484: the tenth RU242 and the sixth RU484;

[0201] The eleventh RU242+RU484: the eleventh RU242 and the fifth RU484;

[0202] The twelfth RU242+RU484: the twelfth RU242 and the fifth RU484;

[0203] The ninth RU242+RU484 under a 240MHz bandwidth is the first RU242+RU484 under a third 80MHz bandwidth, and so on.

[0204] It should be understood that the Zth RU242 and the Xth RU484 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0205] Among them, RU484+RU996 has fixed merging or joint patterns in Table A, and there are 8 fixed merging patterns for 240MHz, as detailed below:

[0206] First RU484+RU996; Second RU484 and Second RU996;

[0207] The second RU484+RU996: the first RU484 and the second RU996;

[0208] The third RU484+RU996: the fourth RU484 and the first RU996;

[0209] The fourth RU484+RU996: the third RU484 and the first RU996;

[0210] The fifth RU484+RU996: the fourth RU484 and the third RU996;

[0211] The sixth RU484+RU996: the third RU484 and the third RU996;

[0212] The seventh RU484+RU996: the sixth RU484 and the second RU996;

[0213] The eighth RU484+RU996: the fifth RU484 and the second RU996;

[0214] It should be understood that the Xth RU484 and the Yth RU996 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0215] When designing a 240MHz sequence, if the pattern RU242+RU484+RU996 needs to be considered, there are 16 possible patterns for 240MHz, as follows:

[0216] The first RU242+RU484+RU996; the second RU242 and the second RU484 and the second RU996;

[0217] The second RU242+RU484+RU996: the first RU242, the second RU484, and the second RU996;

[0218] The third RU242+RU484+RU996: the fourth RU242 combined with the first RU484 and the second RU996;

[0219] The fourth RU242+RU484+RU996: the third RU242 combined with the first RU484 and the second RU996;

[0220] The fifth RU242+RU484+RU996: the sixth RU242 and the fourth RU484 and the first RU996;

[0221] The sixth RU242+RU484+RU996: the fifth RU242 and the fourth RU484 and the first RU996;

[0222] The seventh RU242+RU484+RU996: the eighth RU242 and the third RU484 and the first RU996;

[0223] The eighth RU242+RU484+RU996: the seventh RU242 and the third RU484 and the first RU996;

[0224] The ninth RU242+RU484+RU996: the sixth RU242, the fourth RU484, and the third RU996;

[0225] The tenth RU242+RU484+RU996: the fifth RU242, the fourth RU484, and the third RU996;

[0226] The eleventh RU242+RU484+RU996: the eighth RU242 and the third RU484 and the third RU996;

[0227] The twelfth RU242+RU484+RU996: the seventh RU242 and the third RU484 and the third RU996;

[0228] The thirteenth RU242+RU484+RU996: the tenth RU242, the sixth RU484, and the second RU996;

[0229] The fourteenth RU242+RU484+RU996: the ninth RU242, the sixth RU484, and the second RU9966;

[0230] The fifteenth RU242+RU484+RU996: the twelfth RU242, the fifth RU484, and the second RU996;

[0231] The sixteenth RU242+RU484+RU996: the eleventh RU242, the fifth RU484, and the second RU996;

[0232] It should be understood that the Zth RU242, the Xth RU484, and the Yth RU996 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above description, and will not be repeated here.

[0233] When designing a 240MHz sequence, if the pattern RU484+RU2*996 needs to be considered, there are 6 possible patterns for 240MHz, as follows:

[0234] The first RU484 + RU2 * 996: the second RU484, the second RU996, and the third RU996;

[0235] The second RU484+RU2*996: the first RU484, the second RU996, and the third RU996;

[0236] The first RU484 + RU2*996: the fourth RU484, the first RU996, and the third RU996;

[0237] The second RU484+RU2*996: the third RU484 and the first RU996 and the third RU996;

[0238] The first RU484 + RU2*996: the sixth RU484, the first RU996, and the second RU996;

[0239] The second RU484+RU2*996: the fifth RU484 combined with the first RU996 and the second RU996;

[0240] It should be understood that the Xth RU484 and the Yth RU996 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0241] When designing a 240MHz sequence, if the pattern RU996+RU996+RU996 needs to be considered, there is one pattern in 240MHz, which is the full bandwidth pattern. Specifically, it is the combination or combination of the first RU996, the second RU996, and the third RU996.

[0242] The patterns considered for 2xLTF / 4xLTF sequences under a 320MHz bandwidth are shown in Table B below:

[0243] Table B

[0244]

[0245] Style 1: Full bandwidth, puncturing, and multi-RU merging style under 320MHz; Style 1 does not consider the transmission of 240MHz transmission which is the transmission formed by puncturing 320MHz PPDU. That is to say, the main consideration in the design sequence is the full bandwidth, puncturing, and multi-RU style under 320MHz / 160+160MHz PPDU.

[0246] Each 80MHz zone contains 36 26-tone RUs, with serial numbers increasing from small to large and corresponding frequencies increasing from low to high. The same applies to 52-tone RUs (RU 52), 106-tone RUs (RU 106), 242-tone RUs (RU242), 484-tone RUs (RU484), and 996-tone RUs (RU996).

[0247] Multi-RU merging involves assigning multiple RUs to a single STA. Each RU still uses its own data subcarrier and pilot subcarrier positions. For example, in RU26+RU52, RU26 uses its own data subcarrier positions and pilot positions, while RU52 uses its own data subcarrier positions and pilot subcarrier indices.

[0248] RU26+RU52 has fixed merging or joint patterns in Table B. There are 4 fixed merging patterns in each 80MHz range, resulting in 16 merging or joint patterns in the 320MHz range, as detailed below:

[0249] The first RU26+RU52: the 8th RU26 and the 3rd RU52;

[0250] The second RU26+RU52: the 11th RU26 and the 6th RU52;

[0251] The third RU26+RU52: the 26th RU26 and the 11th RU52;

[0252] The fourth RU26+RU52: the 29th RU26 and the 14th RU52;

[0253] The fifth RU26+RU52: the 44th RU26 and the 19th RU52;

[0254] The sixth RU26+RU52: the 47th RU26 and the 22nd RU52;

[0255] The seventh RU26+RU52: the 62nd RU26 and the 27th RU52;

[0256] The eighth RU26+RU52: the 65th RU26 and the 30th RU52;

[0257] The ninth RU26+RU52: the 80th RU26 and the 35th RU52;

[0258] The tenth RU26+RU52: the 83rd RU26 and the 38th RU52;

[0259] The eleventh RU26+RU52: the 98th RU26 and the 43rd RU52;

[0260] The twelfth RU26+RU52: the 101st RU26 and the 46th RU52;

[0261] The thirteenth RU26+RU52: the 116th RU26 and the 51st RU52;

[0262] The fourteenth RU26+RU52: the 119th RU26 and the 54th RU52;

[0263] The fifteenth RU26+RU52: the 134th RU26 and the 59th RU52;

[0264] The sixteenth RU26+RU52: the 137th RU26 and the 62nd RU52;

[0265] It should be understood that the Xth RU26 and the Yth RU52 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0266] RU26+RU106 have fixed merging or joint patterns in Table B. There are 4 fixed merging patterns in each 80MHz range, resulting in 16 merging or joint patterns in the 320MHz range, as detailed below:

[0267] The first RU26 + RU106: the fifth RU26 and the first RU106;

[0268] The second RU26+RU106: the 14th RU26 and the 4th RU106;

[0269] The third RU26+RU106: the 23rd RU26 and the 5th RU106;

[0270] The fourth RU26+RU106: the 32nd RU26 and the 8th RU106;

[0271] The fifth RU26+RU106: the 41st RU26 and the 9th RU106;

[0272] The sixth RU26+RU106: the 50th RU26 and the 12th RU106;

[0273] The seventh RU26+RU106: the 59th RU26 and the 13th RU106;

[0274] The eighth RU26+RU106: the 68th RU26 and the 16th RU106;

[0275] The ninth RU26+RU106: the 77th RU26 and the 17th RU106;

[0276] The tenth RU26+RU106: the 86th RU26 and the 20th RU106;

[0277] The eleventh RU26+RU106: the 95th RU26 and the 21st RU106;

[0278] The twelfth RU26+RU106: the 104th RU26 and the 24th RU106;

[0279] The thirteenth RU26+RU106: the 113th RU26 and the 25th RU106;

[0280] The fourteenth RU26+RU106: the 122nd RU26 and the 28th RU106;

[0281] The fifteenth RU26+RU106: the 131st RU26 and the 29th RU106;

[0282] The sixteenth RU26+RU106: the 140th RU26 and the 32nd RU106;

[0283] It should be understood that the Xth RU26 and the Yth RU106 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0284] Among them, RU242+RU484 has fixed merging or joint patterns in Table B. There are 4 fixed merging patterns in each 80MHz range, so there are 16 merging or joint patterns in 320MHz range, as detailed below:

[0285] First RU242+RU484: First RU242 and second RU484;

[0286] The second RU242+RU484: the second RU242 and the second RU484;

[0287] The third RU242+RU484: The third RU242 and the first RU484;

[0288] The fourth RU242+RU484: the fourth RU242 and the first RU484;

[0289] The fifth RU242+RU484: the fifth RU242 and the fourth RU484;

[0290] The sixth RU242+RU484: the sixth RU242 and the fourth RU484;

[0291] The seventh RU242+RU484: the seventh RU242 and the third RU484;

[0292] The eighth RU242+RU484: the eighth RU242 and the third RU484;

[0293] The ninth RU242+RU484: the ninth RU242 and the sixth RU484;

[0294] The tenth RU242+RU484: the tenth RU242 and the sixth RU484;

[0295] The eleventh RU242+RU484: the eleventh RU242 and the fifth RU484;

[0296] The twelfth RU242+RU484: The twelfth RU242 and the fifth RU484.

[0297] The thirteenth RU242+RU484: The thirteenth RU242 and the eighth RU484;

[0298] The fourteenth RU242+RU484: the fourteenth RU242 and the eighth RU484;

[0299] The fifteenth RU242+RU484: the fifteenth RU242 and the seventh RU484;

[0300] The sixteenth RU242+RU484: the sixteenth RU242 and the seventh RU484;

[0301] It should be understood that the Xth RU242 and the Yth RU484 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above description, and will not be repeated here.

[0302] Among them, RU484+RU996 has fixed merging or combination patterns in Table B. There are four fixed merging patterns each in the primary 160MHz and secondary 160MHz, so there are eight merging or combination patterns in 320MHz, as detailed below:

[0303] First RU484+RU996; Second RU484 and Second RU996;

[0304] The second RU484+RU996: the first RU484 and the second RU996;

[0305] The third RU484+RU996: the fourth RU484 and the first RU996;

[0306] The fourth RU484+RU996: the third RU484 and the first RU996;

[0307] The fifth RU484+RU996: the sixth RU484 and the fourth RU996;

[0308] The sixth RU484+RU996: the fifth RU484 and the fourth RU996;

[0309] The seventh RU484+RU996: the eighth RU484 and the third RU996;

[0310] The eighth RU484+RU996: the seventh RU484 and the third RU996;

[0311] It should be understood that the Xth RU484 and the Yth RU996 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0312] RU2*996 refers to either a primary 160MHz or a secondary 160MHz, as detailed below:

[0313] The first RU2*996: the first RU996 and the second RU996;

[0314] The second RU2*996; the third RU996 and the fourth RU996;

[0315] It should be understood that the Xth RU996 is numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0316] Where RU3*996 refers to any combination of three RU996 units out of the four RU996 units, specifically as follows:

[0317] The first RU3*996: the first RU996, the third RU996, and the fourth RU996;

[0318] The second RU3*996: the first RU996, the second RU996, and the fourth RU996;

[0319] The third RU3*996: the first RU996, the second RU996, and the third RU996;

[0320] The fourth RU3*996: the second RU996, the third RU996, and the fourth RU996;

[0321] It should be understood that the Xth RU996 is numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0322] The combination pattern of RU3*996+RU484 is as follows:

[0323] The first RU3*996+RU484: the second RU484 and the second RU996 and the third RU996 and the fourth RU996;

[0324] The second RU3*996+RU484: the first RU484, the second RU996, the third RU996, and the fourth RU996;

[0325] The third RU3*996+RU484: the first RU996 and the fourth RU484 and the third RU996 and the fourth RU996;

[0326] The fourth RU3*996+RU484: the first RU996 and the third RU484 and the third RU996 and the fourth RU996;

[0327] The fifth RU3*996+RU484: the first RU996, the second RU996, the sixth RU484, and the fourth RU996;

[0328] The sixth RU3*996+RU484: the first RU996, the second RU996, the fifth RU484, and the fourth RU996;

[0329] The seventh RU3*996+RU484: the first RU996, the second RU996, the third RU996, and the eighth RU484;

[0330] The eighth RU3*996+RU484: the first RU996, the second RU996, the third RU996, and the seventh RU484; it should be understood that the Xth RU996 and the Yth RU484 are numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0331] The combination pattern of RU4*996+RU484 is a full bandwidth pattern of 320MHz, specifically the combination pattern of the first RU996, the second RU996, the third RU996, and the fourth RU996.

[0332] It should be understood that the Xth RU996 is numbered sequentially from left to right (from low frequency to high frequency), similar to the above, and will not be repeated here.

[0333] Style 2: Full bandwidth at 320MHz, with puncturing and multiple RU merging, considering compatibility with 2*996+484 at 240MHz;

[0334] Style 2 considers partial compatibility with 240MHz. When any 80MHz hole corresponding to 320MHz is removed or disregarded, the remaining RU3*996 will have one RU484 that is disregarded, forming RU2*996+RU484. In the case of hole punching, it is similar to methods 14-49 (24 in total) in 320MHz hole punching scenario A.

[0335] Style 3: Full bandwidth, punched, multi-RU merging style at 320MHz, considering compatibility with full bandwidth, punched, and multi-RU merging at 240MHz.

[0336] Style 3 considers all scenarios for 240MHz MRU compatibility and puncturing. When any 80MHz puncturing scenario in 320MHz is removed or disregarded, the remaining RU3*996 includes RU484, which is disregarded, forming RU2*996+RU484. In puncturing scenarios, it's similar to methods 14-49 in 320MHz puncturing scenario A. Furthermore, it considers 240MHz puncturing scenarios, so compared to Style 2, RU2*996 has 12 possible scenarios instead of 2.

[0337] When designing a 320MHz sequence, if the pattern RU242+RU484+RU996 needs to be considered, there are 16 possible patterns for 320MHz, as follows:

[0338] The first RU242+RU484+RU996; the second RU242 and the second RU484 and the second RU996;

[0339] The second RU242+RU484+RU996: the first RU242, the second RU484, and the second RU996;

[0340] The third RU242+RU484+RU996: the fourth RU242 combined with the first RU484 and the second RU996;

[0341] The fourth RU242+RU484+RU996: the third RU242 combined with the first RU484 and the second RU996;

[0342] The fifth RU242+RU484+RU996: the sixth RU242 and the fourth RU484 and the first RU996;

[0343] The sixth RU242+RU484+RU996: the fifth RU242 and the fourth RU484 and the first RU996;

[0344] The seventh RU242+RU484+RU996: the eighth RU242 and the third RU484 and the first RU996;

[0345] The eighth RU242+RU484+RU996: the seventh RU242 and the third RU484 and the first RU996;

[0346] The ninth RU242+RU484+RU996: the tenth RU242 and the sixth RU484 and the fourth RU996;

[0347] The tenth RU242+RU484+RU996: the ninth RU242, the sixth RU484, and the fourth RU996;

[0348] The eleventh RU242+RU484+RU996: the twelfth RU242, the fifth RU484, and the fourth RU996;

[0349] The twelfth RU242+RU484+RU996: the eleventh RU242, the fifth RU484, and the fourth RU996;

[0350] The thirteenth RU242+RU484+RU996: the fourteenth RU242, the eighth RU484, and the third RU996;

[0351] The fourteenth RU242+RU484+RU996: the thirteenth RU242, the eighth RU484, and the third RU9966;

[0352] The fifteenth RU242+RU484+RU996: the sixteenth RU242, the seventh RU484, and the third RU996;

[0353] The sixteenth RU242+RU484+RU996: the fifteenth RU242, the seventh RU484, and the third RU996;

[0354] This application provides various possible LTF sequences. Some LTF sequences have the lowest PAPR value under full bandwidth; some LTF sequences have the lowest maximum PAPR considering full bandwidth and multiple puncturing methods, thus exhibiting the best overall performance under full bandwidth and multiple puncturing methods; and some LTF sequences comprehensively consider PAPR under full bandwidth, multiple puncturing methods, and multiple merged RUs, thus exhibiting the best overall performance under full bandwidth, multiple puncturing methods, and multiple merged RUs.

[0355] 4. After introducing the content related to the embodiments of this application, the detailed content of the embodiments of this application will be described below:

[0356] like Figure 5 As shown, this application provides a method for transmitting physical layer protocol data units, including:

[0357] S101. Generate a Physical Protocol Data Unit (PPDU), wherein the PPDU includes a Long Training Field (LTF), and the length of the frequency domain sequence of the LTF is greater than a first length, wherein the first length is the length of the frequency domain sequence of the LTF of the PPDU transmitted on a channel with a bandwidth of 160MHz.

[0358] S102. Transmit the PPDU on the target channel, wherein the bandwidth of the target channel is greater than 160MHz.

[0359] This application focuses on the frequency domain sequence of the LTF of PPDUs transmitted at 240MHz and 320MHz. Therefore, the above steps can also be simplified to:

[0360] S201. Generate a PPDU, which is transmitted on a channel with a bandwidth of 240MHz / 320MHz. The PPDU includes an LTF, and the frequency domain sequence of the LTF is any one of the various possible frequency domain sequences of the LTF provided below.

[0361] S202, Transmit the PPDU on a channel with a bandwidth of 240MHz / 320MHz.

[0362] This application focuses on various possible frequency domain sequences of LTF (hereinafter, the frequency domain sequence of LTF is simply referred to as LTF sequence). Before introducing the various possible LTF sequences provided in this application, First, let's introduce the method for constructing LTF sequences. The specific method is as follows:

[0363] i. Determine the sequence structure of the LTF sequence;

[0364] ii. Determine LTF sequences by computer search based on the following design criteria, which include:

[0365] 1) Lower PAPR: Reduces the requirements for the linear power amplifier;

[0366] 2) Phase reversal at non-pilot positions: Consider multiple flows (P matrix size is 2x2, 4x4, 6x6, 8x8, 12x12, 16x16);

[0367] 3) Consider the drilling issue;

[0368] 4) Consider multi-RU joint transmission or merging (multiple RUs assigned to the same STA).

[0369] Alternatively, in other words, the design criteria include: considering PAPR values ​​under full bandwidth, multiple punching methods, and multiple RU merging, and considering phase reversal at non-pilot positions.

[0370] Specifically, the designed sequence considers the optimal maximum PAPR under multiple modes (e.g., full bandwidth, puncturing, and multiple RUs). Within the transmission bandwidth, from small RUs to large RUs, the sequence with the optimal PAPR for various RUs (multiple RUs combined or a single RU) is selected. Since LTF is used for MIMO channel estimation, and the number of streams has increased to 16 in the new generation of WiFi standards, the maximum PAPR values ​​of the obtained LTF all consider multi-stream scenarios in non-pilot locations (e.g., P matrix sizes of 2x2, 4x4, 6x6, 8x8, 12x12, 16x16).

[0371] The following describes several possible LTF sequences provided in the embodiments of this application. :

[0372] 1. A 1x LTF sequence with a bandwidth of 240MHz (abbreviated as LTF1x240M sequence)

[0373] 1-1, A possible LTF1x240M sequence = [LTF1x80M 0 23 LTF1x80M 0 23 —LTF1x80M], where LTF1x80M is the LTF sequence of 80MHz 1x in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0374] The LTF1x240M sequence exhibits low PAPR values ​​under various punching methods at 240MHz.

[0375] Specifically, when the Fast Fourier Transform (IFFT) size is 3072, the PAPR values ​​of this LTF1x240M sequence under 240MHz puncturing modes 1-10 are shown in Table 7 below.

[0376] Table 7

[0377] <![CDATA[Sequence: LTF1x240M Sequence = [LTF1x80M 0 23 LTF1x80M 0 23 -LTF1x80M]]]> PAPR[dB] Method 1: 240MHz [1 1 1 1 1 1 1 1 1 1 1 1 1] 7.5154 Method 2: 200MHz [0 01 1 1 1 1 1 1 1 1 1 1] 7.0253 Method 3: 200MHz [1 1 0 0 1 1 1 1 1 1 1 1 1] 7.1208 Method 4: 200MHz [1 1 1 1 0 0 1 1 1 1 1 1 1] 8.2661 Method 5: 200MHz [1 1 1 1 1 1 0 0 1 1 1 1] 7.9758 Method 6: 200MHz [1 1 1 1 1 1 1 1 0 0 1 1] 7.1286 Method 7: 200MHz [1 1 1 1 1 1 1 1 1 1 1 0 0] 6.9607 Method 8: 160MHz [0 0 0 0 1 1 1 1 1 1 1 1 1] 8.148 Method 9: 160MHz [1 1 1 1 0 0 0 0 1 1 1 1] 8.3072 Mode 10: 160MHz [1 1 1 1 1 1 1 1 0 0 0 0] 7.9794 The maximum PAPR value comes from method 9. 8.3072

[0378] Specifically, when the Fast Fourier Transform (IFFT) size is 4096, the PAPR values ​​of this LTF1x240M sequence under 240MHz puncturing modes 1-10 are shown in Table 8 below.

[0379] Table 8

[0380]

[0381]

[0382] The method for obtaining the LTF1x240M sequence of 1-1 above includes:

[0383] i. Determine the sequence structure of the LTF1x240M sequence. The sequence structure of the LTF1x240M sequence is [LTF1x80M0]. 23 ±LTF1x80M 0 23 ±LTF1x80M];

[0384] ii. Using computer search, based on the following design criteria, determine the LTF1x240M sequence = [LTF1x80M0]. 23 LTF1x80M 0 23 —LTF1x80M], the design criteria include: 1) smaller PAPR: reducing the requirements for linear power amplifiers; 2) phase flipping at non-pilot positions: considering multiple streams (P matrix size is 1x1, 2x2, 4x4, 6x6, 8x8, 12x12, 16x16); 3) considering the punching problem; 4) considering multi-RU joint transmission or merging (multiple RUs are assigned to the same STA).

[0385] In other words, the LTF1x240M sequence provided above yields the lowest PAPR value, considering full bandwidth, various puncturing methods, and multi-stream scenarios. Depending on the puncturing method, you can also choose LTF1x240M sequence = [LTF1x80M 0...]. 23 LTF1x80M 0 23 [LTF1x80M], LTF1x240M sequence = [LTF1x80M 0] 23 -LTF1x80M0 23 [LTF1x80M], or LTF1x240M sequence = [LTF1x80M 0] 23 -LTF1x80M 0 23 —LTF1x80M].

[0386] 1-2, Another possible LTF1x240M sequence = [LTF1x160M 0 23 —LTF1x80M], where LTF1x160M is the LTF sequence of 160MHz 1x in the 11ax standard, and the specific sequence can be found in the 11ax standard; LTF1x80M is the LTF sequence of 80MHz 1x in the 11ax standard, and the specific sequence can be found in the 11ax standard.

[0387] The LTF1x240M sequence exhibits low PAPR values ​​under various punching methods at 240MHz.

[0388] Specifically, when the Fast Fourier Transform (IFFT) size is 3072, the PAPR values ​​of this LTF1x240M sequence under 240MHz puncturing modes 1-10 are shown in Table 9 below.

[0389] Table 9

[0390]

[0391]

[0392] Specifically, when the Fast Fourier Transform (IFFT) size is 4096, the PAPR values ​​of this LTF1x240M sequence under 240MHz puncturing modes 1-10 are shown in Table 10 below.

[0393] Table 10

[0394]

[0395]

[0396] The method for obtaining the LTF1x240M sequence described in 1-2 above determines the sequence structure of the LTF1x240M sequence as [±LTF1x160M 0...]. 23 [±LTF1x80M], except for the other methods, the sequence construction methods described above are the same.

[0397] 1-3, Another possible LTF1x240M sequence = [LTF1x80MHz] left 0—LTF1x80MHz right 0 23 —LTF1x80MHz left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right Among them, LTF1x80MHz left 80MHz in the 1x case of the 11ax standard left The LTF sequence, for details please refer to the 11ax standard; LTF 1x80MHz right 80MHz in the 1x case of the 11ax standard right The LTF sequence is available in the 11ax standard.

[0398] The LTF1x240M sequence exhibits a low PAPR value in 240MHz punch mode 1. Specifically, the PAPR value of the LTF1x240M sequence in 240MHz punch mode 1 is 7.3553dB.

[0399] The method for obtaining the LTF1x240M sequence described in 1-3 above determines the sequence structure of the LTF1x240M sequence as [LTF1x80MHz]. left 0±LTF1x80MHz right 0 23 ±LTF1x80MHz left 0±LTF1x80MHz right 0 23 ±LTF1x80MHz left 0±LTF1x80MHz right Apart from that, the other methods are the same as the sequence construction methods described above.

[0400] 1-4. Another possible LTF1x240M sequence = [LTF1x80MHz] left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right Among them, LTF1x80MHz left 80MHz in the 1x case of the 11ax standard left The LTF sequence, for details please refer to the 11ax standard; LTF 1x80MHz right 80MHz in the 1x case of the 11ax standard right The LTF sequence is available in the 11ax standard.

[0401] The LTF1x240M sequence exhibits low PAPR values ​​under various punching methods at 240MHz.

[0402] Specifically, when the Fast Fourier Transform (IFFT) size is 3072, the PAPR values ​​of this LTF1x240M sequence under 240MHz puncturing modes 1-10 are shown in Table 11 below.

[0403] Table 11

[0404]

[0405]

[0406] Specifically, when the Fast Fourier Transform (IFFT) size is 4096, the PAPR values ​​of this LTF1x240M sequence under 240MHz puncturing modes 1-10 are shown in Table 12 below.

[0407] Table 12

[0408]

[0409] The method for obtaining the LTF1x240M sequences described in 1-4 above determines the sequence structure of the LTF1x240M sequence as [LTF1x80MHz]. left 0±LTF1x80MHz right 0 23 ±LTF1x80MHz left 0±LTF1x80MHz right 0 23 ±LTF1x80MHz left 0±LTF1x80MHz right Apart from that, the other methods are the same as the sequence construction methods described above.

[0410] 2. A 1x LTF sequence with a bandwidth of 320MHz (abbreviated as LTF1x320M sequence)

[0411] 2-1. A possible LTF1x320M sequence = [LTF1x80M 0 23 LTF1x80M 0 23 —LTF1x80M0 23 —LTF1x80M], where LTF1x80M is the 80MHz 1x LTF sequence in the 11ax standard; the specific sequence can be found in the 11ax standard. Depending on the drilling method, the LTF1x320M sequence can also be selected = [LTF1x80M 0]. 23 LTF1x80M 0 23 LTF1x80M0 23 —LTF1x80M], or LTF1x320M sequence = [LTF1x80M0] 23 LTF1x80M 0 23 LTF1x80M 0 23 LTF1x80M], or LTF1x320M sequence = [LTF1x80M0] 23 —LTF1x80M 0 23 LTF1x80M 0 23 LTF1x80M], or LTF1x320M sequence =

[0412] [LTF1x80M 0 23 —LTF1x80M 0 23 —LTF1x80M 0 23 [LTF1x80M], or LTF1x320M sequence = [LTF1x80M 0] 23 —LTF1x80M 0 23 —LTF1x80M 0 23 —LTF1x80M] etc.

[0413] The LTF1x320M sequence has a low PAPR value in the A-type punch mode at 320MHz (i.e., compatible with 240MHz punch mode). For example, the PAPR value of the LTF1x320M sequence in a certain punch mode under the A-type punch mode at 320MHz is 9.0837dB, and the PAPR value of other punch modes is lower than 9.0837dB. For example, the PAPR value in punch mode 1 is 8.9944dB.

[0414] Specifically, under the A-type 320MHz puncturing mode, the PAPR values ​​of this LTF1x320M sequence under the X-type 320MHz puncturing mode and the Y-type puncturing mode are shown in Table 13 below.

[0415] Table 13

[0416]

[0417] The PAPR values ​​of the LTF1x320M sequence under B-mode 320MHz (i.e., incompatible with 240MHz puncturing) are shown in Table 14.

[0418] Table 14

[0419]

[0420] Methods for obtaining 2-1 LTF1x320M sequences include:

[0421] i. Determine the sequence structure of the LTF1x320M sequence. The sequence structure of the LTF1x240M sequence is [LTF1x80M 0]. 23 ±LTF1x80M 0 23 ±LTF1x80M 0 23 ±LTF1x80M];

[0422] ii. Using computer search, based on the following design criteria, determine the LTF1x240M sequence = [LTF1x80M0]. 23 LTF1x80M 0 23—LTF1x80M 0 23 —LTF1x80M], the design criteria include: 1) smaller PAPR: reducing the requirements for linear power amplifiers; 2) phase flipping at non-pilot positions: considering multiple streams (P matrix size is 2x2, 4x4, 6x6, 8x8, 12*12, 16*16); 3) considering the punching problem; 4) considering multi-RU joint transmission or merging (multiple RUs are assigned to the same STA).

[0423] 2-2, Another possible LTF1x320M sequence = [LTF1x80M 0 23 LTF1x80M 0 23 —LTF1x80M0 23 LTF1x80M], where LTF1x80M is the LTF sequence of 80MHz 1x in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0424] The LTF1x320M sequence exhibits a low PAPR value in 320MHz B-mode puncturing (i.e., incompatible with 240MHz puncturing). Specifically, the PAPR value of the LTF1x320M sequence in 320MHz puncturing mode 1 is 7.5364dB.

[0425] 2-3. Another possible LTF1x320M sequence = [LTF1x160M 0 23 —LTF1x160M], where LTF1x160M is the LTF sequence of 160MHz 1x in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0426] The LTF1x320M sequence exhibits low PAPR values ​​under various punching methods at 320MHz.

[0427] For example, the PAPR value of this LTF1x320M sequence under a certain puncturing mode of 320MHz A puncturing mode is 9.4002dB, and the PAPR value under other puncturing modes is lower than 9.4002dB. For example, the PAPR value under puncturing mode 1 is 8.4364dB.

[0428] For example, under the B-mode 320MHz puncturing (i.e., incompatible with 240MHz puncturing), the PAPR values ​​of this LTF1x320M sequence under 320MHz puncturing modes 1-13 are shown in Table 15 below.

[0429] Table 15

[0430]

[0431]

[0432] 2-4. Another possible LTF1x320M sequence = [LTF1x80MHz] left 0LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right 0 23 —LTF1x80MHz left 0LTF1x80MHz right Among them, LTF1x80MHz left 80MHz in the 1x case of the 11ax standard left The LTF sequence, for details please refer to the 11ax standard; LTF 1x80MHz right 80MHz in the 1x case of the 11ax standard right The LTF sequence is available in the 11ax standard.

[0433] The PAPR value of this LTF1x320M sequence in 320MHz A puncture mode 1 is 8.1866dB.

[0434] 2-5. Another possible LTF1x320M sequence = [LTF1x80MHz] left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right Among them, LTF1x80MHz left 80MHz in the 1x case of the 11ax standard left The LTF sequence, for details please refer to the 11ax standard; LTF 1x80MHz right 80MHz in the 1x case of the 11ax standard right The LTF sequence is available in the 11ax standard.

[0435] The PAPR value of this LTF1x320M sequence under a certain puncturing method in the A puncturing mode at 320MHz is 9.0837dB, while the PAPR value under other puncturing methods is less than 9.0837dB.

[0436] 2-6. Another possible LTF1x320M sequence = [LTF1x80MHz] left 0—LTF1x80MHz right 0 23 —LTF1x80MHz left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right Among them, LTF1x80MHz left 80MHz in the 1x case of the 11ax standard left The LTF sequence, for details please refer to the 11ax standard; LTF 1x80MHz right 80MHz in the 1x case of the 11ax standard right The LTF sequence is available in the 11ax standard.

[0437] The PAPR value of the LTF1x320M sequence in 320MHz punch mode 1 is 6.2230dB.

[0438] 2-7. Another possible LTF1x320M sequence = [LTF1x80MHz] left 0—LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right Among them, LTF1x80MHz left 80MHz in the 1x case of the 11ax standard left The LTF sequence, for details please refer to the 11ax standard; LTF 1x80MHz right 80MHz in the 1x case of the 11ax standardright The LTF sequence is available in the 11ax standard.

[0439] The PAPR values ​​of this LTF1x320M sequence under 320MHz B puncture mode 1-puncture mode 13 are shown in the table below.

[0440]

[0441] 3. 2x LTF sequences with a bandwidth of 240MHz (abbreviated as LTF2x240M sequences)

[0442] 3-1. A possible LTF2x240M sequence = [LTF2x80M 0 23 LTF2x80M 0 23 LTF2x80M], where LTF2x80M is the 80MHz 2x LTF sequence in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0443] The LTF2x240M sequence exhibits low PAPR values ​​under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU combining at 240MHz). For example, the PAPR value of the LTF2x240M sequence is 10.9621dB under full bandwidth, a certain puncturing method, or a certain RU (or multi-RU combining), and the PAPR value under other puncturing methods is lower than 10.9621dB. For instance, the PAPR value is 10.9621dB under full bandwidth or puncturing method 1.

[0444] This sequence has a low PAPR value under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU merging at 240MHz).

[0445] For example, the PAPR values ​​of the sequence for each RU (including combinations of multiple RUs or a single RU) at the first 80MHz, second 80MHz, and third 80MHz are as follows:

[0446] PAPR values ​​for each RU at the first, second, and third 80MHz frequencies:

[0447]

[0448] like Figure 4As shown, in the RU52 row, there is one RU26 between the 2nd RU52 and the 3rd RU52, one RU26 between the 6th RU52 and the 7th RU52, one RU26 between the 10th RU52 and the 11th RU52, and one RU26 between the 14th RU52 and the 15th RU52; correspondingly, the value at the corresponding position in the RU52 row of this table represents the PAPR value of the RU26 at the corresponding position.

[0449] Similarly, as Figure 4 As shown, in the RU106 row, there is one RU26 between the first RU106 and the second RU106, one RU26 between the third RU106 and the fourth RU106, one RU26 between the fifth RU106 and the sixth RU106, and one RU26 between the seventh RU106 and the eighth RU106; correspondingly, the value at the corresponding position in the RU106 row of this table represents the PAPR value of the RU26 at the corresponding position.

[0450] Note that the values ​​in the first row of the table above, from left to right, represent the PAPR values ​​of the sequence at 80MHz, from the 1st RU26 to the 36th RU26. The values ​​in the second row, from left to right, represent the PAPR values ​​of the sequence at 80MHz, from the 1st RU52 to the 16th RU52. The values ​​in the third row, from left to right, represent the PAPR values ​​of the sequence at 80MHz, from the 1st RU106 to the 8th RU106. The values ​​in the fourth row, from left to right, represent the PAPR values ​​of the sequence at 80MHz, from the 1st RU242 to the 4th RU242. The values ​​in the fifth row, from left to right, represent the PAPR values ​​of the sequence at 80MHz, from the 1st RU484 to the 2nd RU484. The values ​​in row 6 of the table above are the PAPR values ​​of the sequence on RU996 at 80MHz. The values ​​in row 7 of the table above are the PAPR values ​​of the sequence on the first RU26+RU52 to the fourth RU26+RU52 in each 80MHz range. The values ​​in row 8 of the table above are the PAPR values ​​of the sequence on the first RU26+RU106 to the fourth RU26+RU106 in each 80MHz range. The values ​​in row 9 of the table above are the PAPR values ​​of the sequence on the first RU242+RU484 to the fourth RU242+RU484 in each 80MHz range. The values ​​in row 10 of the table above are the PAPR values ​​of the sequence on the combined RU (RU242+RU242, composed of the first and fourth RU242 in each 80MHz range) of each 80MHz range.

[0451] It should be understood that the correspondence between PAPR values ​​and RUs in the table above applies to the PAPR value tables for the other RUs within the 80MHz range described in this paper; that is, the PAPR values ​​in the PAPR value tables for the other RUs within the 80MHz range described in this paper correspond one-to-one with the RUs mentioned in the previous paragraph. In the following text, only the PAPR values ​​in the tables will be given, and the correspondence between PAPR values ​​and RUs in the tables will not be elaborated upon further.

[0452] For example, the PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table A are as follows:

[0453]

[0454] Note that the values ​​in the first row of the table above, from left to right, are the PAPR values ​​for the first to eighth combination RUs of RU484+RU996 at 240MHz, as described above. The values ​​in the second row, from left to right, are the PAPR values ​​for the first to sixteenth combination RUs of RU242+RU484+RU996 at 240MHz, as described above. The values ​​in the third row, from left to right, are the PAPR values ​​for the first to sixth combination RUs of RU484+2*RU996 at 240MHz, as described above. The values ​​in the fourth row, from left to right, are the PAPR values ​​for the first to third combination RUs of 2*RU996 at 240MHz, as described above. The values ​​in the fifth row are the PAPR values ​​for 3*RU996 at 240MHz, as described above.

[0455] It should be understood that the correspondence between the PAPR values ​​of RUs (i.e., combined RUs) exceeding 80MHz in the above table and the combined RUs themselves applies to the table of PAPR values ​​for other RUs (i.e., combined RUs) exceeding 80MHz in this paper. In other words, the PAPR values ​​in the table of PAPR values ​​for other RUs (i.e., combined RUs) exceeding 80MHz in this paper correspond one-to-one with the combined RUs mentioned in the previous paragraph. Elsewhere, only the PAPR values ​​in the table will be given, and the correspondence between the PAPR values ​​and combined RUs in the table will not be elaborated further.

[0456] 3-2, A possible LTF2x240M sequence = [LTF2x160M 0 23[LTF2x80M], where LTF2x160M is the 160MHz 2x LTF sequence in the 11ax standard, and LTF2x80M is the 80MHz 2x LTF sequence in the 11ax standard. For specific sequences, please refer to the 11ax standard.

[0457] The LTF2x240M sequence exhibits low PAPR values ​​under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU combining at 240MHz). The PAPR value of the LTF2x240M sequence at full bandwidth at 240MHz or under puncturing method 1 is 9.6089dB.

[0458] This sequence has a low PAPR value under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU merging at 240MHz).

[0459] For example, the PAPR values ​​of the sequence for each RU (including combinations of multiple RUs or a single RU) at the first 80MHz, second 80MHz, and third 80MHz are as follows:

[0460] PAPR value table for each RU in the first 80MHz and third 80MHz:

[0461]

[0462] The second 80MHz PAPR value table for each RU:

[0463]

[0464] The PAPR values ​​for other RUs (i.e., combined RUs) exceeding 80MHz in Table A for this sequence are as follows:

[0465]

[0466] 3-3, A possible LTF2x240M sequence = [LTF2x160M 0 23 —LTF2x80M], where LTF2x160M is the LTF sequence of 160MHz 2x in the 11ax standard, and LTF2x80M is the LTF sequence of 80MHz 2x in the 11ax standard. For specific sequences, please refer to the 11ax standard.

[0467] The LTF2x240M sequence exhibits low PAPR values ​​under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU combining at 240MHz). For example, the PAPR value of the LTF2x240M sequence is 9.7242dB under full bandwidth, a certain puncturing method, or a certain RU (or multi-RU combining), while the PAPR value under other puncturing methods is lower than 9.7242dB.

[0468] This sequence has a low PAPR value under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU merging at 240MHz).

[0469] For example, the PAPR values ​​of the sequence for each RU (including combinations of multiple RUs or a single RU) at the first 80MHz, second 80MHz, and third 80MHz are as follows:

[0470] PAPR tables for the first 80MHz and the third RUs:

[0471]

[0472] PAPR table for each RU in the second 80MHz series:

[0473]

[0474]

[0475] The PAPR values ​​for other RUs (multiple RU combinations or single RUs) exceeding 80MHz in this sequence, as shown in Table A, are as follows:

[0476]

[0477] 3-4. A possible LTF2x240M sequence = [LTF2x80M] part1 LTF2x80M part2 —LTF2x80M part3 LTF2x80M part4 LTF2x80M part5 0 23 LTF2x80M part1 LTF2x80M part2 —LTF2x80M part3 —LTF2x80M part4 —LTF2x80M part5 0 23 LTF2x80M part1LTF2x80M part2 —LTF2x80M part3 LTF2x80M part4 LTF2x80M part5 ], of which, LTF2x80M part1 LTF2x80M part2 LTF2x80M part3 LTF2x80M part4 LTF2x80M part5 2 x 80MHz in the 11ax standard part1 LTF sequence, 2x80MHz part2 LTF sequence, 2x 80MHz part3 LTF sequence, 2x 80MHz part4 LTF sequence, 2x 80MHz part5 The LTF sequence is available in the 11ax standard.

[0478] The LTF2x240M sequence exhibits low PAPR values ​​under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU combining at 240MHz). The PAPR value of the LTF2x240M sequence at 240MHz puncturing method 1 is 9.4304dB.

[0479] For example, the PAPR values ​​of the sequence for each RU (including combinations of multiple RUs or a single RU) at the first 80MHz, second 80MHz, and third 80MHz are as follows:

[0480] PAPR values ​​for each RU at the first, second, and third 80MHz frequencies:

[0481] The first and third 80MHz RU tables:

[0482]

[0483] The second 80MHz RU table:

[0484]

[0485]

[0486] The PAPR values ​​for other RUs (multiple RU combinations or single RUs) exceeding 80MHz in this sequence, as shown in Table A, are as follows:

[0487]

[0488] 3-5. A possible LTF2x240M sequence = [LTF2x80M] part1 —LTF2x80M part2 —LTF2x80M part3 —LTF2x80M part4 LTF2x80M part5 0 23 —LTF2x80M part1 LTF2x80M part2 —LTF2x80M part3 —LTF2x80M part4 LTF2x80M part5 0 23 LTF2x80M part1 LTF2x80M part2 —LTF2x80M part3 LTF2x80M part4 LTF2x80M part5 ], of which, LTF2x80M part1 LTF2x80M part2 LTF2x80M part3 LTF2x80M part4 LTF2x80M part5 2 x 80MHz in the 11ax standard part1 LTF sequence, 2x80MHz part2 LTF sequence, 2x 80MHz part3 LTF sequence, 2x 80MHz part4 LTF sequence, 2x 80MHz part5 The LTF sequence is available in the 11ax standard.

[0489] The LTF2x240M sequence exhibits low PAPR values ​​under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU combining at 240MHz). For example, the PAPR value of the LTF2x240M sequence is 9.6179dB under a certain puncturing method, and the PAPR value is lower than 9.6179dB under other puncturing methods.

[0490] This sequence has a low PAPR value under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU merging at 240MHz).

[0491] For example, the PAPR values ​​of the sequence for each RU (including combinations of multiple RUs or a single RU) at the first 80MHz, second 80MHz, and third 80MHz are as follows:

[0492] The first 80MHz RU table:

[0493]

[0494]

[0495] The second 80MHz RU table:

[0496]

[0497] The third 80MHz RU table:

[0498]

[0499]

[0500] For example, the PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table A are as follows:

[0501]

[0502] 4. 2x LTF sequences with a bandwidth of 320MHz (abbreviated as LTF2x320M sequences)

[0503] 4-1. A possible LTF2x320M sequence = [LTF2x80M 0 23 LTF2x80M 0 23 —LTF2x80M0 23 —LTF2x80M], where LTF2x80M is the 80MHz 2x LTF sequence in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0504] Under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU combining at 320MHz), the PAPR value is relatively low. For example, the PAPR value of this LTF2x320M sequence is 10.9310dB under full bandwidth, a certain puncturing method, or a certain RU (or multi-RU combining), and the PAPR value under other puncturing methods is lower than 10.9310dB. For example, the PAPR value under full bandwidth or puncturing method 1 is 10.4917dB. For example, the PAPR values ​​of this sequence for each RU (including multiple combinations of RUs or a single RU) in the first 80MHz, second 80MHz, third 80MHz, and fourth 80MHz are as follows:

[0505] Table of PAPR values ​​for the first, second, third, and fourth 80MHz RUs:

[0506]

[0507] For example, the PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0508]

[0509]

[0510] Note that the values ​​in the first row of the table above, from left to right, represent the PAPR values ​​of the first to eighth combination RUs of the RU484+RU996 at 320MHz, as described above. The values ​​in the second row, from left to right, represent the PAPR values ​​of the first to sixteenth combination RUs of the RU242+RU484+RU996 at 320MHz, as described above. The values ​​in the third row, from left to right, represent the PAPR values ​​of the first to eighth combination RUs of the RU484+3*RU996 at 320MHz, as described above. The values ​​in the fourth row, from left to right, represent the PAPR values ​​of the first to fourth combination RUs of the 3*RU996 at 320MHz, as described above. The values ​​in the fifth row of the table represent the PAPR values ​​of the first to twenty-fourth combination RUs of RU484+2*RU996 at 320MHz, as described above. The values ​​in each sub-row of the fifth row, from left to right, represent the PAPR values ​​of the first to sixth combination RUs of RU484+2*RU996 within each 80MHz range of 320MHz. The values ​​in the sixth row of the table represent the PAPR values ​​of the first to twelfth combination RUs of 2*RU996 at 320MHz, as described above. The values ​​in each sub-row of the sixth row, from left to right, represent the PAPR values ​​of the first to third combination RUs of 2*RU996 within each 80MHz range of 320MHz. The values ​​in the seventh row of the table represent the PAPR values ​​of the 4*RU996 combination at 320MHz, as described above.

[0511] It should be understood that the correspondence between the PAPR values ​​of RUs (i.e., combined RUs) exceeding 80MHz in the above table and the combined RUs themselves applies to the table of PAPR values ​​for other RUs (i.e., combined RUs) exceeding 80MHz in this paper. In other words, the PAPR values ​​in the table of PAPR values ​​for other RUs (i.e., combined RUs) exceeding 80MHz in this paper correspond one-to-one with the combined RUs mentioned in the previous paragraph. Elsewhere, only the PAPR values ​​in the table will be given, and the correspondence between the PAPR values ​​and combined RUs in the table will not be elaborated further.

[0512] 4-2, A possible LTF2x320M sequence = [LTF2x160M 0 23[LTF2x160M], where LTF2x160M is the 160MHz 2x LTF sequence in the 11ax standard; the specific sequence can be found in the 11ax standard. This LTF2x320M sequence has a PAPR value of 10.1655dB under 320MHz full bandwidth or puncturing mode 1. Alternatively, it has a lower PAPR value under various conditions in Table B at 320MHz (including 320MHz full bandwidth, various 320MHz puncturing modes, and various multi-RU combining at 320MHz).

[0513] For example, the PAPR value of this LTF2x320M sequence is 10.5867dB under full bandwidth, a certain puncturing method, or a certain merged RU, while the PAPR value under other puncturing methods is lower than 10.5867dB.

[0514] For example, the PAPR values ​​of the sequence for each RU (including combinations of multiple RUs or a single RU) at the first 80MHz, second 80MHz, third 80MHz, and fourth 80MHz are as follows:

[0515] The first and third 80MHz RU tables:

[0516]

[0517] The second and fourth 80MHz RU tables:

[0518]

[0519]

[0520] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0521]

[0522] 4-3. A possible LTF2x320M sequence = [LTF2x160M 0 23 —LTF2x160M], where LTF2x160M is the 160MHz 2x LTF sequence in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0523] The LTF2x320M sequence exhibits low PAPR values ​​under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU combining at 320MHz). For example, the PAPR value is 11.2017dB under full bandwidth, a certain puncturing method, or a certain RU (or multi-RU combining).

[0524] For example, the PAPR values ​​of the sequence for each RU (including combinations of multiple RUs or a single RU) at the first 80MHz, second 80MHz, third 80MHz, and fourth 80MHz are as follows:

[0525] The first and third 80MHz RU tables:

[0526]

[0527]

[0528] The second and fourth 80MHz RU tables:

[0529]

[0530] For example, the PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0531]

[0532]

[0533] 4-4. A possible LTF2x320M sequence = [LTF2x80Mpart1 LTF2x80Mpart2—LTF2x80Mpart3 LTF2x80Mpart4 LTF2x80Mpart5 0] 23 LTF2x80Mpart1LTF2x80Mpart2—LTF2x80Mpart3—LTF2x80Mpart4—LTF2x80Mpart5 0 23 LTF2x80Mpart1—LTF2x80Mpart2LTF2x80Mpart3 LTF2x80Mpart4—LTF2x80Mpart5 0 23 [LTF2x80Mpart1 LTF2x80Mpart2 —LTF2x80Mpart3LTF2x80Mpart4 LTF2x80Mpart5], where LTF2x80Mpart1, LTF2x80Mpart2, LTF2x80Mpart3, LTF2x80Mpart4, and LTF2x80Mpart5 are respectively 2x 80MHz in the 11ax standard. part1 LTF sequence, 2x 80MHz part2 LTF sequence, 2x 80MHz part3 LTF sequence, 2x 80MHz part4 LTF sequence, 2x80MHzpart5 The LTF sequence is available in the 11ax standard.

[0534] The LTF2x320M sequence exhibits a low PAPR value under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU merging at 320MHz).

[0535] For example, the PAPR values ​​of each (multiple RU combinations or single) RU in this sequence from the first 80MHz to the fourth 80MHz are as follows:

[0536] The first and fourth 80MHz RU tables:

[0537]

[0538] The second 80MHz RU table:

[0539]

[0540]

[0541] The third 80MHz RU table:

[0542]

[0543] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0544]

[0545] 4-5. A possible LTF2x320M sequence = [LTF2x80Mpart1—LTF2x80Mpart2—LTF2x80Mpart3—LTF2x80Mpart4 LTF2x80Mpart5 0] 23 —LTF2x80Mpart1LTF2x80Mpart2—LTF2x80Mpart3—LTF2x80Mpart4 LTF2x80Mpart5 0 23 LTF2x80Mpart1 LTF2x80Mpart2—LTF2x80Mpart3 LTF2x80Mpart4LTF2x80Mpart5 0 23LTF2x80Mpart1—LTF2x80Mpart2—LTF2x80Mpart3—LTF2x80Mpart4—LTF2x80Mpart5], where LTF2x80Mpart1, LTF2x80Mpart2, LTF2x80Mpart3, LTF2x80Mpart4, and LTF2x80Mpart5 are respectively 2x80MHz in the 11ax standard. part1 LTF sequence, 2x 80MHz part2 LTF sequence, 2x 80MHz part3 LTF sequence, 2x 80MHz part4 LTF sequence, 2x 80MHz part5 The LTF sequence is available in the 11ax standard.

[0546] The LTF2x320M sequence exhibits a low PAPR value under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU merging at 320MHz).

[0547] For example, the PAPR values ​​of each (multiple RU combinations or single) RU in this sequence from the first 80MHz to the fourth 80MHz are as follows:

[0548] The first 80MHz RU table:

[0549]

[0550] The second 80MHz RU table:

[0551]

[0552]

[0553] The third 80MHz RU table:

[0554]

[0555] The fourth 80MHz RU table:

[0556]

[0557]

[0558] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0559]

[0560]

[0561] 4-6. Another possible LTF2x320M sequence = [LTF2x80M_part1,LTF2x80M_part2,(-1)*LTF2x80M_part3,LTF2x80M_part4,LTF2x80M_part5,0 23 ,(-1)*LTF2x80M_part1,LTF2x80M_part2, (-1)*LTF2x80M_part3,(-1)*LTF2x80M_part4,LTF2x80M_part5,0 23 , (-1)*LTF2x80M_part1,(-1)*LTF2x80M_part2,LTF2x80M_part3,LTF2x80M_part4,LTF2x80M_part5,0 23 ,LTF2x80M_part1,(-1)*LTF2x80M_part2,(-1)*LTF2x80M_part3,(-1)*LTF2x80M_part4,LTF2x80M_part5];

[0562] This sequence has a low PAPR value under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU merging at 320MHz).

[0563] The specific PAPR values ​​of each (multiple RU combinations or single RUs) in the first to fourth 80MHz bands are as follows, where the sizes of each RU are arranged in order. For example, the RU26 in the first 80MHz band are the first to the thirty-sixth RU26 in the 320MHz bandwidth according to the table order, and the RU26 in the second 80MHz band are the thirty-seventh to the seventy-second RU26 in the 320MHz bandwidth according to the table order.

[0564]

[0565]

[0566] The PAPR values ​​for other RUs (multiple RU combinations or single RUs) exceeding 80MHz in this sequence are as follows:

[0567]

[0568] 4-7. Another possible LTF2x320M sequence = [LTF2x80M_part1,LTF2x80M_part2,(-1)*LTF2x80M_part3, (-1)*LTF2x80M_part4,(-1)*LTF2x80M_part5,0 23 ,(-1)*LTF2x80M_part1, (-1)*LTF2x80M_part2,(-1)*LTF2x80M_part3,(-1)*LTF2x80M_part4, (-1)*LTF2x80M_part5,0 23 ,(-1)*LTF2x80M_part1,LTF2x80M_part2,LTF2x80M_part3,LTF2x80M_part4,LTF2x80M_part5,0 23 ,LTF2x80M_part1,LTF2x80M_part2,LTF2x80M_part3,LTF2x80M_part4,LTF2x80M_part5];

[0569] This sequence has a low PAPR value under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU merging at 320MHz).

[0570] For example, the PAPR values ​​of each (multiple RU combinations or single) RU in this sequence from the first 80MHz to the fourth 80MHz are as follows:

[0571]

[0572] The PAPR values ​​for this sequence in other RUs (multiple RU combinations or a single RU) exceeding 80MHz are as follows:

[0573]

[0574] 4-8. Another possible LTF2x320M sequence = [LTF2x80M_part1,LTF2x80M_part2,(-1)*LTF2x80M_part3, (-1)*LTF2x80M_part4,(-1)*LTF2x80M_part5,0 23 ,(-1)*LTF2x80M_part1, (-1)*LTF2x80M_part2,(-1)*LTF2x80M_part3,(-1)*LTF2x80M_part4, (-1)*LTF2x80M_part5,023 ,(-1)*LTF2x80M_part1,LTF2x80M_part2,LTF2x80M_part3,LTF2x80M_part4,LTF2x80M_part5,0 23 ,LTF2x80M_part1,LTF2x80M_part2,LTF2x80M_part3,LTF2x80M_part4,LTF2x80M_part5];

[0575] This sequence has a low PAPR value under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU merging at 320MHz).

[0576] For example, the PAPR values ​​of each (multiple RU combinations or single) RU in this sequence from the first 80MHz to the fourth 80MHz are as follows:

[0577]

[0578] The PAPR values ​​for this sequence in other RUs (multiple RU combinations or a single RU) exceeding 80MHz are as follows:

[0579]

[0580] 5. 4x LTF sequences with a bandwidth of 240MHz (abbreviated as LTF4x240M sequences)

[0581] 5-1. A possible LTF4x240M sequence = [LTF4x80M 0 23 LTF4x80M 0 23 —LTF4x80M], where LTF4x80M is the LTF sequence of 80MHz 4x in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0582] The LTF4x240M sequence exhibits a low PAPR value across the full bandwidth of 240MHz, or under a specific puncturing method or a specific RU (or multiple RU merging) configuration. For example, the PAPR value of this sequence is 9.8723dB across the full bandwidth of 240MHz, and the PAPR value is less than or equal to 9.8723dB under other puncturing methods. The LTF4x240M sequence also exhibits a low PAPR value at 240MHz (Table A). For example, the PAPR value of this sequence is 9.7535dB under a specific puncturing or multiple RU configuration, and the PAPR value is less than or equal to 9.7535dB under other puncturing methods.

[0583] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the third 80MHz are as follows.

[0584] The first, second, and third 80MHz RU tables:

[0585]

[0586] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table A are as follows:

[0587]

[0588] 5-2. A possible LTF4x240M sequence = [LTF4x160M 0 23 [LTF4x80M], where LTF4x160M is the 160MHz 4x LTF sequence in the 11ax standard, and LTF4x80M is the 80MHz 4x LTF sequence in the 11ax standard; specific sequences can be found in the 11ax standard. This LTF4x240M sequence has a low PAPR value under Table A at 240MHz. For example, the PAPR value of this LTF4x240M sequence at the full bandwidth of 240MHz is 9.2127dB.

[0589] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the third 80MHz are as follows.

[0590] The first and third 80MHz RU tables:

[0591]

[0592] The second 80MHz RU table:

[0593]

[0594]

[0595] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table A are as follows:

[0596]

[0597] 5-3. A possible LTF4x240M sequence = [LTF4x160M 0 23—LTF4x80M], where LTF4x160M is the LTF sequence of 160MHz 4x in the 11ax standard, and LTF4x80M is the LTF sequence of 80MHz 4x in the 11ax standard. For specific sequences, please refer to the 11ax standard.

[0598] The LTF4x240M sequence has a low PAPR value in Table A at 240MHz. For example, the PAPR value of this sequence is 9.7047dB in a certain full bandwidth or puncturing mode at 240MHz, and the PAPR value is less than 9.7047dB in other puncturing modes.

[0599] This sequence exhibits low PAPR values ​​under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU merging at 240MHz). For example, the PAPR values ​​of each (multiple RU combinations or single) RU in the first 80MHz to the third 80MHz are as follows.

[0600] The first and third 80MHz RU tables:

[0601]

[0602]

[0603] The second 80MHz RU table:

[0604]

[0605] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table A are as follows:

[0606]

[0607]

[0608] 5-4. A possible LTF4x240M sequence = [LTF4x80MHz] left 0LTF4x80MHz right 0 23 LTF4x80MHz left 0—LTF4x80MHz right 0 23 LTF4x80MHz left 0LTF4x80MHz right Among them, LTF4x80MHz left 80MHz in the 4x case of the 11ax standard leftLTF sequence, LTF4x80MHz right 80MHz in the 4x case of the 11ax standard left The LTF sequence is available in the 11ax standard.

[0609] The LTF4x240M sequence exhibits a low PAPR value under Table A at 240MHz. The PAPR value of the LTF4x240M sequence at the full bandwidth of 240MHz is 9.2127dB.

[0610] This sequence has a low PAPR value under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU merging at 240MHz).

[0611] For example, the PAPR values ​​of the individual (multiple RU combinations or single) RUs in the sequence from the first 80MHz to the third 80MHz are as follows:

[0612] The first and third 80MHz RU tables:

[0613]

[0614] The second 80MHz RU table:

[0615]

[0616] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table A are as follows:

[0617]

[0618] 5-5. A possible LTF4x240M sequence = [LTF4x80MHz] left 0LTF4x80MHz right 0 23 LTF4x80MHz left 0—LTF4x80MHz right 0 23 —LTF4x80MHz left 0—LTF4x80MHz right Among them, LTF4x80MHz left 80MHz in the 4x case of the 11ax standard left LTF sequence, LTF4x80MHz right 80MHz in the 4x case of the 11ax standard left The LTF sequence is available in the 11ax standard.

[0619] The LTF4x240M sequence has a low PAPR value in Table A at 240MHz. For example, the PAPR value of this sequence is 9.7047dB at the full bandwidth of 240MHz or under a certain puncturing method, and the PAPR value is less than 9.7047dB under other puncturing methods.

[0620] This sequence has a low PAPR value under various conditions in Table A at 240MHz (including full bandwidth at 240MHz, various puncturing methods at 240MHz, and various multi-RU merging at 240MHz).

[0621] For example, the PAPR values ​​of the individual (multiple RU combinations or single) RUs in the sequence from the first 80MHz to the third 80MHz are as follows:

[0622] The first and third 80MHz RU tables:

[0623]

[0624] The second 80MHz RU table:

[0625]

[0626]

[0627] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table A are as follows:

[0628]

[0629] 6. 4x LTF sequences with a bandwidth of 320MHz (abbreviated as LTF4x320M sequences)

[0630] 6-1. A possible LTF4x320M sequence = [LTF4x80M 0 23 LTF4x80M 0 23 —LTF4x80M0 23 —LTF4x80M], where LTF4x80M is the LTF sequence of 80MHz 4x in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0631] This LTF4x320M sequence exhibits low PAPR values ​​under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU combining at 320MHz). For example, the PAPR value of this sequence is 10.7708dB under a certain puncturing method at 320MHz, and the PAPR values ​​under other methods are all less than 10.7708dB; for example, the PAPR value under puncturing method 1 is 10.3033dB. Depending on the considerations, it is also possible to...

[0632] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0633] The first, second, third, and fourth 80MHz RU tables:

[0634]

[0635] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0636]

[0637]

[0638] 6-2. A possible LTF4x320M sequence = [LTF4x160M 0 23 LTF4x160M], where LTF4x160M is the LTF sequence of 160MHz 4x in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0639] The LTF2x320M sequence exhibits low PAPR values ​​under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU combining methods at 320MHz). The PAPR value of the LTF4x320M sequence is 9.9610dB under 240MHz puncturing or full bandwidth method 1.

[0640] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0641] The first and third 80MHz RU tables:

[0642]

[0643] The second and fourth 80MHz RU tables:

[0644]

[0645] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0646]

[0647] 6-3. A possible LTF4x320M sequence = [LTF4x160M 0 23 —LTF4x160M], where LTF4x160M is the LTF sequence of 160MHz 4x in the 11ax standard. For the specific sequence, please refer to the 11ax standard.

[0648] The LTF4x320M sequence exhibits low PAPR values ​​under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU combining methods at 320MHz). For example, the PAPR value of this sequence is 10.2842dB (considering RU484+RU2*996) or 10.2793dB (without considering RU484+RU2*996) under a certain 320MHz method, and the PAPR value is less than 10.2793dB under other puncturing methods.

[0649] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0650] The first and third 80MHz RU tables:

[0651]

[0652] The second and fourth 80MHz RU tables:

[0653]

[0654] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0655]

[0656] 6-4. A possible LTF4x320M sequence = [LTF4x80MHz] left 0LTF4x80MHz right 0 23 LTF4x80MHz left 0—LTF4x80MHz right 0 23—LTF4x80MHz left 0LTF4x80MHz right 0 23 LTF4x80MHz left 0LTF4x80MHz right ], of which, LTF4x80MHz left 80MHz in the 4x case of the 11ax standard left LTF sequence, LTF4x80MHz right 80MHz in the 4x case of the 11ax standard left The LTF sequence is available in the 11ax standard.

[0657] The LTF4x320M sequence exhibits a low PAPR value under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU combining at 320MHz). The PAPR value of the LTF4x320M sequence at full bandwidth at 320MHz is 9.4793dB.

[0658] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0659] The first and fourth 80MHz RU tables:

[0660]

[0661] The second and third 80MHz RU tables:

[0662]

[0663] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0664]

[0665] 6-5. A possible LTF4x320M sequence = [LTF4x80MHz] left 0—LTF4x80MHz right 0 23 —LTF4x80MHz left 0—LTF4x80MHz right 0 23 —LTF4x80MHz left 0LTF4x80MHz right 0 23 LTF4x80MHzleft 0LTF4x80MHz right ], of which, LTF4x80MHz left 80MHz in the 4x case of the 11ax standard left LTF sequence, LTF4x80MHz right 80MHz in the 4x case of the 11ax standard left The LTF sequence is available in the 11ax standard.

[0666] The LTF4x320M sequence exhibits low PAPR values ​​under various conditions in Table B at 320MHz (including full bandwidth at 320MHz, various puncturing methods at 320MHz, and various multi-RU combining methods at 320MHz). For example, the PAPR value of this sequence is 10.1186dB under a certain puncturing method at 320MHz, and the PAPR value is less than 10.1186dB under other puncturing methods.

[0667] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0668] The first and third 80MHz RU tables:

[0669]

[0670]

[0671] The second and fourth 80MHz RU tables:

[0672]

[0673] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0674]

[0675]

[0676] 6-6. A possible LTF4x320M sequence = [LTF4x80M_part1,LTF4x80M_part2,(-1)*LTF4x80M_part3,LTF4x80M_part4,(-1)*LTF4x80M_part5,023,LTF4x80M_part1,(-1)*LTF4x80M_part2,(-1)*LTF4x80M_part3,(-1)*LTF4x80M_part4,(-1)*LTF4x80M_part5,023 ,(-1)*LTF4x80M_part1,(-1)*LTF4x80M_part2,(-1)*LTF4x80M_part3,LTF4x80M_part4,(-1)*LTF4x80M_part5,023,(-1)*LTF4x80M_part1,LTF4x80M_part2,(-1)*LTF4x80M_part3,(-1)*LTF4x80M_part4,(-1)*LTF4x80M_part5],where,LTF4x80MHz _part1 ,LTF4x80MHz _part2 ,LTF4x80MHz _part3 ,LTF4x80MHz _part4 and LTF4x80MHz _part5 The 80MHz LTF sequence in the 4x case of the 11ax standard is a sequence divided into 5 parts of a 2x 80MHz LTF. LTF4x80MHz is the 80MHz sequence in the 4x case of the 11ax standard. left The LTF sequence is available in the 11ax standard.

[0677] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0678] The first 80MHz RU table:

[0679]

[0680] The second 80MHz RU table:

[0681]

[0682] The third 80MHz RU table:

[0683]

[0684] The fourth 80MHz RU table:

[0685]

[0686] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0687]

[0688] 6-7. A possible LTF4x320M sequence = [LTF4x80M_part1, LTF4x80M_part2, (-1)*LTF4x80M_part3, LTF4x80M_part4, (-1)*LTF4x80M_part5, 0 23 ,(-1)*LTF4x80M_part1,LTF4x80M_part2,(-1)*LTF4x80M_part3,(-1)*LTF4x80M_part4,(-1)*LTF4x80M_part5,0 23 ,(-1)*LTF4x80M_part1,(-1)*LTF4x80M_part2,(-1)*LTF4x80M_part3,LTF4x80M_part4,(-1)*LTF4x80M_part5,0 23 ,(-1)*LTF4x80M_part1,LTF4x80M_part2,LTF4x80M_part3,LTF4x80M_part4,LTF4x80M_part5];,where LTF4x80MHz _part1 ,LTF4x80MHz _part2 ,LTF4x80MHz _part3 ,LTF4x80MHz _part4 and LTF4x80MHz _part5 The 80MHz LTF sequence in the 4x case of the 11ax standard is a sequence divided into 5 parts of a 2x 80MHz LTF. LTF4x80MHz is the 80MHz sequence in the 4x case of the 11ax standard. left The LTF sequence is available in the 11ax standard.

[0689] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0690] The first 80MHz RU table:

[0691]

[0692] The second 80MHz RU table:

[0693]

[0694] The third 80MHz RU table:

[0695]

[0696]

[0697] The fourth 80MHz RU table:

[0698]

[0699] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0700]

[0701]

[0702] 6-8. A possible LTF4x320M sequence = [LTF4x80M_part1, LTF4x80M_part2, (-1)*LTF4x80M_part3, LTF4x80M_part4, (-1)*LTF4x80M_part5, 0 23 ,(-1)*LTF4x80M_part1,LTF4x80M_part2,(-1)*LTF4x80M_part3,(-1)*LTF4x80M_part4,(-1)*LTF4x80M_part5,0 23 ,(-1)*LTF4x80M_part1,(-1)*LTF4x80M_part2,(-1)*LTF4x80M_part3,LTF4x80M_part4,(-1)*LTF4x80M_part5,0 23 ,(-1)*LTF4x80M_part1,LTF4x80M_part2,LTF4x80M_part3,LTF4x80M_part4,LTF4x80M_part5];;,where,LTF4x80MHz _part1 ,LTF4x80MHz _part2 ,LTF4x80MHz _part3 ,LTF4x80MHz _part4 and LTF4x80MHz _part5The 80MHz LTF sequence in the 4x case of the 11ax standard is a sequence divided into 5 parts of a 2x 80MHz LTF. LTF4x80MHz is the 80MHz sequence in the 4x case of the 11ax standard. left The LTF sequence is available in the 11ax standard.

[0703] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0704] The first 80MHz RU table:

[0705]

[0706] The second 80MHz RU table:

[0707]

[0708] The third 80MHz RU table:

[0709]

[0710] The fourth 80MHz RU table:

[0711]

[0712]

[0713] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0714]

[0715] 6-9. A possible LTF4x320M sequence = [LTF4x80M_part1, (-1)*LTF4x80M_part2, 0, LTF4x80M_part3, LTF4x80M_part4, 0] 23 ,LTF4x80M_part1,LTF4x80M_part2,0,(-1)*LTF4x80M_part3,LTF4x80M_part4,0 23 ,LTF4x80M_part1,(-1)*LTF4x80M_part2,0,(-1)*LTF4x80M_part3,(-1)*LTF4x80M_part4,0 23,(-1)*LTF4x80M_part1,(-1)*LTF4x80M_part2,0,(-1)*LTF4x80M_part3,LTF4x80M_part4];

[0716] Among them, LTF4x80MHz _part1 ,LTF4x80MHz _part2 ,LTF4x80MHz _part3 ,LTF4x80MHz _part4 The 80MHz LTF sequence in the 4x case of the 11ax standard is divided into the following 4 parts. The 80MHz 4x HE-LTF sequence is from subcarrier index -500 to subcarrier index 500, and the total length of the sequence is 1001. So if it is divided into 4 parts, then LTF4x80_part1 is the first 250 values, from the first sequence value to the 250th sequence value, and so on. Specifically, LTF4x80_part1 = LTF4x80MHz(1:250).

[0717] LTF4x80_part2=LTF4x80MHz(251:500);

[0718] LTF4x80_part3=LTF4x80MHz(502:751);

[0719] LTF4x80_part4=LTF4x80MHz(752:1001).

[0720] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0721] The first 80MHz RU table:

[0722]

[0723] The second 80MHz RU table:

[0724]

[0725] The third 80MHz RU table:

[0726]

[0727] The fourth 80MHz RU table:

[0728]

[0729] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0730] The specific combined RU form is as follows: [A bitmap is used to represent the puncturing method, with each bit indicating whether a 20MHz MHz channel is punctured or not. For example, "0" indicates that the 20MHz corresponding to that bit is punctured or is not considered for merging when multiple RUs are combined, and "1" indicates that the 20MHz corresponding to that bit is not punctured. Optionally, the bits from left to right correspond to the channel frequencies from low to high in the order of 20MHz]:

[0731] RU 484+3*996 are as follows: [0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1],[1 1 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1],[11 1 1 0 0 1 1 1 1 1 1 1 1 1 1 1],[1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1 1],[1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1],[11 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1 0 0 1 1],[1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0]

[0732] RU 3*996: [1 1 1 1 0 0 0 0 1 1 1 1 1 1 1 1],[1 1 1 1 1 1 1 1 0 0 0 0 11 1 1],[1 1 1 1 1 1 1 11 1 1 1 0 0 0 0],[0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1]

[0733] RU 2*996+484: [0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0], [1 1 0 0 1 1 1 1 1 1 11 0 0 0 0],

[0734] [1 1 1 1 0 0 1 1 1 1 1 1 0 0 0 0],[1 1 1 1 1 1 0 0 1 1 1 1 0 0 0 0],

[0735] [1 1 1 1 1 1 1 1 1 0 0 1 1 0 0 0 0],[1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0],

[0736] [0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1],[0 0 0 0 1 1 0 0 1 1 1 1 1 1 1 1],

[0737] [0 0 0 0 1 1 1 1 0 0 1 1 1 1 1 1],[0 0 0 0 1 1 1 1 1 1 0 0 1 1 1 1],

[0738] [0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 1 1],[0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0],

[0739] RU 2*996: [1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0], [0 0 0 0 0 0 0 0 1 1 1 1 11 1 1], [0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0]

[0741] RU 484+996: [0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0], [1 1 0 0 1 1 1 1 0 0 0 00 0 0 0],

[0742] [1 1 1 1 0 0 1 1 0 0 0 0 0 0 0 0],[1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0],

[0743] [0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1],[0 0 0 0 0 0 0 0 1 1 0 0 1 1 1 1],

[0744] [0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 1 1],[0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0]

[0745] RU 4*996: [1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1]

[0746]

[0747] 6-10. A possible LTF4x320M sequence = [LTF4x80M_part1, (-1)*LTF4x80M_part2, LTF4x80M_part3, LTF4x80M_part4, LTF4x80M_part5, 0 23 ,(-1)*LTF4x80M_part1,(-1)*LTF4x80M_part2,(-1)*LTF4x80M_part3,LTF4x80M_part4,(-1)*LTF4x80M_part5,0 23 ,(-1)*LTF4x80M_part1,LTF4x80M_part2,LTF4x80M_part3,LTF4x80M_part4,LTF4x80M_part5,0 23 ,LTF4x80M_part1,LTF4x80M_part2,LTF4x80M_part3,LTF4x80M_part4,(-1)*LTF4x80M_part5];

[0748] Among them, LTF4x80MHz _part1 ,LTF4x80MHz _part2 ,LTF4x80MHz _part3 ,LTF4x80MHz _part4 and LTF4x80MHz _part5 The 80MHz LTF sequence in the 4x case of the 11ax standard is a sequence divided into 5 parts of a 2x 80MHz LTF. LTF4x80MHz is the 80MHz sequence in the 4x case of the 11ax standard. left The LTF sequence is available in the 11ax standard.

[0749] Specifically, the PAPR values ​​of each (multiple RU combinations or single) RU in the sequence from the first 80MHz to the fourth 80MHz are as follows.

[0750] The first 80MHz RU table:

[0751]

[0752] The second 80MHz RU table:

[0753]

[0754] The third 80MHz RU table:

[0755]

[0756] The fourth 80MHz RU table:

[0757]

[0758] The PAPR values ​​for this sequence on other RUs (i.e., combined RUs) exceeding 80MHz in Table B are as follows:

[0759] The specific combined RU form is as follows: [A bitmap is used to represent the puncturing method, with each bit indicating whether a 20MHz MHz channel is punctured or not. For example, "0" indicates that the 20MHz corresponding to that bit is punctured or is not considered for merging when multiple RUs are combined, and "1" indicates that the 20MHz corresponding to that bit is not punctured. Optionally, the bits from left to right correspond to the channel frequencies from low to high in the order of 20MHz]:

[0760] RU 484+3*996 are as follows: [0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1],[1 1 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1],[11 1 1 0 0 1 1 1 1 1 1 1 1 1 1 1],[1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1 1],[1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1],[11 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 1 1 1 0 0 1 1],[1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0]

[0761] RU 3*996: [1 1 1 1 0 0 0 0 1 1 1 1 1 1 1 1],[1 1 1 1 1 1 1 1 0 0 0 0 11 1 1],[1 1 1 1 1 1 1 11 1 1 1 0 0 0 0],[0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1]

[0762] RU 2*996+484: [0 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0], [1 1 0 0 1 1 1 1 1 1 11 0 0 0 0],

[0763] [1 1 1 1 0 0 1 1 1 1 1 1 0 0 0 0],[1 1 1 1 1 1 0 0 1 1 1 1 0 0 0 0],

[0764] [1 1 1 1 1 1 1 1 1 0 0 1 1 0 0 0 0],[1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0],

[0765] [0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1],[0 0 0 0 1 1 0 0 1 1 1 1 1 1 1 1],

[0766] [0 0 0 0 1 1 1 1 0 0 1 1 1 1 1 1],[0 0 0 0 1 1 1 1 1 1 0 0 1 1 1 1],

[0767] [0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 1 1],[0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0],

[0768] RU 2*996: [1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0], [0 0 0 0 0 0 0 0 1 1 1 1 11 1 1], [0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0]

[0770] RU 484+996: [0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0], [1 1 0 0 1 1 1 1 0 0 0 00 0 0 0],

[0771] [1 1 1 1 0 0 1 1 0 0 0 0 0 0 0 0],[1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0],

[0772] [0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1],[0 0 0 0 0 0 0 0 1 1 0 0 1 1 1 1],

[0773] [0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 1 1],[0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0]

[0774] RU 4*996: [1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1]

[0775]

[0776] The above describes a method for transmitting / receiving physical layer protocol data units provided by embodiments of this application. The following describes the product of embodiments of this application.

[0777] This application provides an apparatus for transmitting physical layer protocol data units, comprising:

[0778] A generation unit is used to generate a Physical Protocol data unit (PPDU), wherein the PPDU includes a Long Training Field (LTF), and the length of the frequency domain sequence of the LTF is greater than a first length, wherein the first length is the length of the frequency domain sequence of the LTF of the PPDU transmitted on a channel with a bandwidth of 160MHz.

[0779] A transmitting unit is configured to transmit the PPDU on a target channel, wherein the bandwidth of the target channel is greater than 160MHz.

[0780] The device for transmitting physical layer protocol data units provided in this application takes into account non-pilot position phase reversal, multiple puncturing methods at 240M / 320M, and multiple RU merging. The frequency domain sequence of the LTF provided has a low PAPR value under multiple puncturing methods at 240M / 320M and on merged multiple RUs.

[0781] This application provides an apparatus for receiving physical layer protocol data units, comprising:

[0782] A receiving unit is configured to receive a Physical Layer Protocol Data Unit (PPDU) on a target channel. The PPDU includes a long training domain, and the length of the frequency domain sequence of the long training domain is greater than a first length, where the first length is the length of the frequency domain sequence of the long training domain of the PPDU transmitted on a channel with a bandwidth of 160MHz, wherein the bandwidth of the target channel is greater than 160MHz.

[0783] A processing unit is used to parse the PPDU.

[0784] The apparatus for receiving physical layer protocol data units provided in this application has a low PAPR value for the frequency domain sequence of the parsed LTF under various puncturing methods at 240M / 320M and on multiple merged RUs.

[0785] It should be understood that the embodiments of this application provide an apparatus for transmitting / receiving physical layer protocol data units, which has all the functions and all the technical details of the above-described method for transmitting / receiving physical layer protocol data. For specific technical details, please refer to the above method, which will not be repeated here.

[0786] The apparatus for transmitting / receiving physical layer protocol data units according to embodiments of this application has been described above. The following describes possible product forms of the apparatus for transmitting / receiving physical layer protocol data units. It should be understood that any product with the above-described apparatus functions for transmitting / receiving physical layer protocol data units falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product form of the apparatus for transmitting / receiving physical layer protocol data units according to embodiments of this application to these forms.

[0787] As one possible product form, the apparatus for transmitting / receiving physical layer protocol data units described in the embodiments of this application can be implemented by a general bus architecture.

[0788] The apparatus for transmitting physical layer protocol data units includes a processor and a transceiver. The processor is used to generate physical layer protocol data units (PPDUs), each PPDU including a long training field (LTF). The frequency domain sequence of the LTF has a length greater than a first length, which is the length of the frequency domain sequence of the LTF of the PPDU transmitted on a channel with a bandwidth of 160 MHz. The transceiver is used to transmit the PPDU on a target channel, wherein the bandwidth of the target channel is greater than 160 MHz.

[0789] It should be understood that the apparatus for transmitting physical layer protocol data units has all the functions and all the technical details of the above-described method for transmitting physical layer protocol data. For specific technical details, please refer to the above method, which will not be repeated here.

[0790] Optionally, the means for transmitting physical layer protocol data units may further include a memory for storing instructions executed by the processor.

[0791] The apparatus for receiving physical layer protocol data units includes a processor and a transceiver. The transceiver is used to receive physical layer protocol data units (PPDUs) on a target channel. The PPDU includes a long training domain, the length of which is greater than a first length, where the first length is the length of the frequency domain sequence of the long training domain of the PPDU transmitted on a channel with a bandwidth of 160 MHz, and the bandwidth of the target channel is greater than 160 MHz. The processor is used to parse the PPDU.

[0792] It should be understood that the apparatus for receiving physical layer protocol data units has all the functions and all the technical details of the above-described method for receiving physical layer protocol data. For specific technical details, please refer to the above-described method, which will not be repeated here.

[0793] Optionally, the means for receiving physical layer protocol data units may further include a memory for storing instructions executed by a processor.

[0794] As a possible product form, the apparatus for transmitting / receiving physical layer protocol data units described in the embodiments of this application can be implemented by a general-purpose processor.

[0795] The apparatus for transmitting physical layer protocol data units includes a processing circuit and a transceiver interface. The processing circuit is used to generate physical layer protocol data units (PPDUs). The PPDU includes a long training field (LTF). The length of the frequency domain sequence of the LTF is greater than a first length, which is the length of the frequency domain sequence of the LTF of the PPDU transmitted on a channel with a bandwidth of 160MHz. The transceiver interface is used to transmit the PPDU on a target channel, wherein the bandwidth of the target channel is greater than 160MHz.

[0796] Optionally, the means for transmitting physical layer protocol data units may further include a storage medium for storing instructions executed by the processor.

[0797] It should be understood that the apparatus for transmitting physical layer protocol data units has all the functions and all the technical details of the above-described method for transmitting physical layer protocol data. For specific technical details, please refer to the above method, which will not be repeated here.

[0798] The apparatus for receiving physical layer protocol data units includes a processing circuit and a transceiver interface. The transceiver interface is used to receive physical layer protocol data units (PPDUs) on a target channel. The PPDU includes a long training domain, and the length of the frequency domain sequence of the long training domain is greater than a first length, which is the length of the frequency domain sequence of the long training domain of the PPDU transmitted on a channel with a bandwidth of 160MHz, wherein the bandwidth of the target channel is greater than 160MHz. The processing circuit is used to parse the PPDU.

[0799] Optionally, the means for receiving physical layer protocol data units may further include a storage medium for storing instructions executed by the processing circuit.

[0800] It should be understood that the apparatus for receiving physical layer protocol data units has all the functions and all the technical details of the above-described method for receiving physical layer protocol data. For specific technical details, please refer to the above-described method, which will not be repeated here.

[0801] As a possible product form, the apparatus for transmitting / receiving physical layer protocol data units described in the embodiments of this application can also be implemented using one or more FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0802] This application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to perform... Figure 5 The method in the illustrated embodiment.

[0803] This application also provides a computer-readable medium storing program code that, when executed on a computer, causes the computer to perform... Figure 5 The method in the illustrated embodiment.

[0804] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0805] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0806] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0807] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0808] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for receiving physical layer protocol data units, characterized in that, include: Physical layer protocol data unit (PPDU) is received on a target channel. The PPDU includes a long training domain, and the length of the frequency domain sequence of the long training domain is greater than a first length, which is the length of the frequency domain sequence of the long training domain of the PPDU transmitted on a channel with a bandwidth of 160MHz. The bandwidth of the target channel is 320MHz. Channel estimation is performed based on the received long training domain. The frequency domain sequence of the long training domain is: [LTF1x80MHz left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right The LTF1x80MHz left 80MHz in IEEE 802.11ax left 1x LTF sequence, the LTF 1x 80MHz right 80MHz in IEEE 802.11ax right 1x LTF sequence.

2. The method according to claim 1, characterized in that, The target channel includes four channels with a bandwidth of 80MHz.

3. The method according to claim 2, characterized in that, In the 80MHz carrier planning, the number of resource units for the 26 subcarriers is 36.

4. An apparatus for receiving physical layer protocol data units, characterized in that, include: A receiving unit is configured to receive a Physical Layer Protocol Data Unit (PPDU) on a target channel. The PPDU includes a long training domain, and the length of the frequency domain sequence of the long training domain is greater than a first length, where the first length is the length of the frequency domain sequence of the long training domain of the PPDU transmitted on a channel with a bandwidth of 160MHz, and the bandwidth of the target channel is 320MHz. The processing unit is configured to perform channel estimation based on the received long training domain. The frequency domain sequence of the long training domain is: [LTF1x80MHz left 0LTF1x80MHz right 0 23 LTF1x80MHz left 0LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right 0 23 —LTF1x80MHz left 0—LTF1x80MHz right The LTF1x80MHz left 80MHz in IEEE 802.11ax left 1x LTF sequence, the LTF 1x 80MHz right 80MHz in IEEE 802.11ax right 1x LTF sequence.

5. The apparatus according to claim 4, characterized in that, The target channel includes four channels with a bandwidth of 80MHz.

6. The apparatus according to claim 5, characterized in that, In the 80MHz carrier planning, the number of resource units for the 26 subcarriers is 36.

7. A computer-readable storage medium, characterized in that, Used to store a computer program, the computer program including instructions for implementing the method as described in any one of claims 1 to 3.

8. A computer product, characterized in that, The computer product includes instructions for implementing the method as described in any one of claims 1 to 3.

Images