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

Abstract

This provides a method for transmitting physical layer protocol data units, etc. [Solution] The method comprises generating a Physical Layer Protocol Data Unit (PPDU), wherein the PPDU includes a Long Training Field (LTF), the length of which is greater than a first length, where 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 160 MHz, and transmitting the PPDU on a target channel, where the target channel is greater than 160 MHz. The frequency domain sequence of the LTF provided in embodiments of the present invention takes into account phase rotation at non-pilot positions, multiple puncturing patterns of 240 MHz / 320 MHz, and multiple RU coupling, thereby the final frequency domain sequence of the LTF has relatively small PAPR values ​​in multiple RUs in multiple puncturing patterns of 240 MHz / 320 MHz.

Description

[Technical Field]

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

[0002] With the development of mobile internet and the proliferation of intelligent terminals, data traffic is growing rapidly, and users are placing increasingly high demands on the quality of communication services. The Institute of Electrical and Electronics Engineers (IEEE) 802.11ax standard can no longer satisfy user demands such as high throughput, low jitter, and low latency. Therefore, the development of next-generation wireless local area network (WLAN) technology, namely the IEEE 802.be standard, is urgently needed.

[0003] Unlike IEEE 80.2ax, IEEE 802.be uses ultra-wide bandwidths such as 240 MHz and 320 MHz to achieve ultra-high transmission rates and support ultra-high user density scenarios. Therefore, how to design the long training field (LTF) sequence for wider channel bandwidths is a matter of concern. [Overview of the Initiative]

[0004] This invention provides a method and apparatus for transmitting physical layer protocol data units to design a long training field for wider channel bandwidth.

[0005] A method for transmitting a physical layer protocol data unit is provided according to a first aspect, comprising generating a physical layer protocol data unit (PPDU), the PPDU comprising a long training field (LTE), the length of the frequency domain sequence of the long training field being longer than a first length, the first length being the length of the frequency domain sequence of the long training field of the PPDU transmitted on a channel having a bandwidth of 160 MHz, and transmitting the PPDU on a target channel having a bandwidth greater than 160 MHz.

[0006] The frequency domain sequence of the LTF supplied in this embodiment of the present application takes into account phase rotation at non-pilot positions, multiple puncturing patterns of 240 MHz / 320 MHz, and multiple RU coupling, thereby the final frequency domain sequence of the LTF has a relatively small PAPR with multiple RUs in multiple puncturing patterns of 240 MHz / 320 MHz.

[0007] A method for receiving a physical layer protocol data unit according to a second aspect, A method is provided which includes receiving a physical layer protocol data unit (PPDU) on a target channel, the PPDU comprising a long training field (LTE), the length of the frequency domain sequence of the long training field being longer than a first length, the first length being the length of the frequency domain sequence of the long training field of a PPDU transmitted on a channel with a bandwidth of 160 MHz, and the bandwidth of the target channel being greater than 160 MHz, and which includes receiving and parsing the PPDU.

[0008] The frequency domain sequence of the LTF received in this embodiment of the present application has a relatively small PAPR in multiple RUs in multiple puncturing patterns at 240 MHz / 320 MHz. [Brief explanation of the drawing]

[0009] [Figure 1] This is a schematic diagram of a communication system applied to the method according to the embodiment of this application. [Figure 2] This is a diagram showing the internal structure of an access point applied to an embodiment of the present invention. [Figure 3] This is a diagram showing the internal structure of a station applied to an embodiment of the present invention. [Figure 4] The 80MHz tone plan is shown. [Figure 5] This is a flowchart of the method according to the embodiment of the present application. [Modes for carrying out the invention]

[0010] The following describes the technical solution of this application with reference to the attached drawings.

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

[0012] The following is used as an example for illustrative purposes. Only a WLAN system is used as an example below to describe the application scenarios and methods in the embodiments of this application.

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

[0014] In the embodiments of the present application, the initiator device may be an STA in the WLAN, and correspondingly, the responder device may be an AP in the WLAN. Indeed, alternatively, in the embodiments of the present application, the initiator device may be an AP in the WLAN, and the responder device may be an STA in the WLAN.

[0015] To facilitate understanding of the embodiments of this application, the communication system shown in Figure 1 is first used as an example to detail the communication system applicable to the embodiments of this application. The scenario system shown in Figure 1 may be a WLAN system. The WLAN system in Figure 1 may include one or more APs and one or more STAs. In Figure 1, one AP and three STAs are used as an example. Wireless communication may be performed between the AP and STA according to various standards. For example, wireless communication between the AP and STA may be performed by single-user multiple-input multiple-output (SU-MIMO) technology or multi-user multiple-input multiple-output (MU-MIMO) technology.

[0016] An AP is also called a wireless access point or hotspot. An AP is an access point for mobile users to access a wired network and is mainly located in homes, buildings, and campuses, or outdoors. An AP acts as a bridge connecting wired and wireless networks. The primary function of an AP is to connect wireless network clients together and then connect the wireless network to Ethernet. Specifically, an AP may be a terminal device or network device equipped with a wireless fidelity (Wi-Fi) chip. Optionally, an AP may be a device that supports multiple WLAN standards such as 802.11. Figure 2 shows a diagram of the internal structure of an AP product. An AP may have multiple antennas or a single antenna. In Figure 2, the AP includes a physical layer (PHY) processing circuit and a media access control (MAC) layer processing circuit. The physical layer processing circuit may be configured to process physical layer signals, and the MAC layer processing circuit may be configured to process MAC layer signals. The 802.11 standard focuses on the PHY and MAC portions, while this embodiment of the present application focuses on protocol design in the MAC and PHY.

[0017] STA products are typically terminal products that comply with the 802.11 series standard, such as mobile phones and notebook computers. Figure 3 shows a diagram of the structure of an STA with a single antenna. In actual scenarios, an STA may also have multiple antennas, and may be a device with more than two antennas. In Figure 3, the STA includes a physical layer (PHY) processing circuit and a media access control (MAC) layer processing circuit. The physical layer processing circuit may be configured to process physical layer signals, and the MAC layer processing circuit may be configured to process MAC layer signals.

[0018] The following describes the embodiments of this application and related matters.

[0019] The following first describes some aspects related to the embodiments of this application.

[0020] 1.802.11be Tone Plan Figure 4 shows an 802.11be 80MHz subcarrier design. A 240MHz bandwidth and a 320MHz bandwidth are added to 802.11be; the 240MHz bandwidth is obtained by directly linking three 802.11be 80MHz subcarriers, and the 320MHz bandwidth is obtained by directly linking four 802.11be 80MHz subcarriers.

[0021] In the 80MHz subcarrier design shown in Figure 4, the indices for the data subcarrier and pilot subcarrier at RU26 are listed in Table 1. [Table 1]

[0022] It should be noted that in Table 1, each row in the second and third columns represents one RU. For example, the last row in the second column represents RU18[-38:-13]. The position of RU18 is from the subcarrier numbered -38 to the subcarrier numbered -13. The fourth column sequentially shows the pilot subcarrier indices of the corresponding 26-tone RU. For example, the first 26-tone RU includes the subcarrier numbered -499 to the subcarrier numbered -474, in which case the pilot subcarriers are from the subcarrier numbered -494 to the subcarrier numbered -480.

[0023] The following table describes similar meanings, and it should be understood that the descriptions will not be repeated below.

[0024] In the 80MHz subcarrier design shown in Figure 4, the indices for the data subcarrier and pilot subcarrier in RU52 are listed in Table 2. [Table 2]

[0025] In the 80MHz subcarrier design shown in Figure 4, the indices for the data subcarrier and pilot subcarrier in RU106 are listed in Table 3. [Table 3]

[0026] In the 80MHz subcarrier design shown in Figure 4, the indices for the data subcarrier and pilot subcarrier in RU242 are listed in Table 4. [Table 4]

[0027] In the 80MHz subcarrier design shown in Figure 4, the indices of the data subcarriers and pilot subcarriers in the RU484 are listed in Table 5. An 80MHz 484-tone RU in 802.11ax is an RU consisting of 484 consecutive subcarriers. An 80MHz 484-tone RU in 802.11be consists of 468 data subcarriers and 16 pilot subcarriers, with five DC subcarriers or null subcarriers in between. For example, in the first 484-tone RU, the subcarriers are numbered from -500 to -12. The five DC subcarriers are numbered -258, -257, -256, -255, and -254. The 16 pilot subcarriers are numbered -494, -468, -426, -400, -360, -334, -292, -266, -246, -220, -178, -152, -112, -86, -44, and -18. [Table 5]

[0028] In the 80MHz subcarrier design in Figure 4, the indices of the data subcarriers and pilot subcarriers in RU996 are listed in Table 6. The 80MHz 996-tone RU in 802.11be consists of 980 data subcarriers and 16 pilot subcarriers, with 5 DC subcarriers in between. For example, in the first 484-tone RU, the subcarriers are numbered from -500 to 500, and the 5 DC subcarriers are 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. [Table 6]

[0029] The LTE sequence provided in this embodiment of the present application is used for 240 MHz and 320 MHz bandwidths, which are configured using the tone plan shown in Figure 4.

[0030] The subcarrier design for the 160MHz bandwidth is based on two 80MHz, i.e., [subcarrier index of RU at 80MHz, subcarrier index of pilot position]-521 and [subcarrier index of RU at 80MHz, subcarrier index of pilot position]+521.

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

[0032] The subcarrier design for a 320MHz bandwidth is based on two 160MHz subcarriers, namely [subcarrier index at 160MHz]-1024 and [subcarrier index at 160MHz]+1024.

[0033] 2.240MHz puncturing pattern and 320MHz puncturing pattern A bitmap is used to indicate the puncturing pattern. Each bit indicates whether one 20MHz subchannel is punctured. For example, "0" indicates that the 20MHz subchannel corresponding to that bit is punctured, and "1" indicates that the 20MHz subchannel corresponding to that bit is not punctured. Optionally, the bits correspond to 20MHz subchannels from lower to higher channel frequencies, from left to right.

[0034] Puncture pattern between 2 and 1.240 MHz Pattern 1: [111111111111], supports a channel bandwidth of 240MHz and 3072 subcarriers. Pattern 2: [001111111111], corresponds to an available channel bandwidth of 200MHz. Pattern 3: [110011111111], corresponds to an available channel bandwidth of 200MHz. Pattern 4: [111100111111], corresponds to an available channel bandwidth of 200MHz. Pattern 5: [111111001111], corresponds to an available channel bandwidth of 200MHz. Pattern 6: [111111110011], corresponds to an available channel bandwidth of 200MHz. Pattern 7: [111111111100], corresponds to an available channel bandwidth of 200MHz. Pattern 8: [000011111111], corresponds to an available channel bandwidth of 160MHz. Pattern 9: [111100001111], corresponds to an available channel bandwidth of 160MHz. Pattern 10: [111111110000], corresponds to an available channel bandwidth of 160MHz.

[0035] Puncture pattern between 2-2.320MHz Specifically, channel puncturing patterns for 320MHz can be classified into two types: one type is compatible with 240MHz puncturing, and the other is not. "Compatible" means that after 240MHz is formed by channel puncturing for 320MHz, further puncturing is performed based on the 240MHz formed by the puncturing; in other words, puncturing continues to be performed on the 240MHz formed by the puncturing.

[0036] (A) 320MHz channel puncturing is compatible with 240MHz channel puncturing.

[0037] Pattern 1: [1111111111111111], supports a channel bandwidth of 320MHz and 4096 subcarriers. Pattern 2: [0011111111111111], corresponds to an available channel bandwidth of 280MHz. Pattern 3: [1100111111111111], corresponds to an available channel bandwidth of 280MHz. Pattern 4: [1111001111111111], corresponds to an available channel bandwidth of 280MHz. Pattern 5: [1111110011111111], corresponds to an available channel bandwidth of 280MHz. Pattern 6: [1111111100111111], corresponds to an available channel bandwidth of 280MHz. Pattern 7: [1111111111001111], corresponds to an available channel bandwidth of 280MHz. Pattern 8: [1111111111110011], corresponds to an available channel bandwidth of 280MHz. Pattern 9: [11111111111111100], corresponds to an available channel bandwidth of 280MHz. Pattern 10: [1111000011111111], corresponds to an available channel bandwidth of 240MHz. Pattern 11: [1111111100001111], corresponds to an available channel bandwidth of 240MHz. Pattern 12: [1111111111110000], corresponds to an available channel bandwidth of 240MHz. Pattern 13: [0000111111111111], corresponds to an available channel bandwidth of 240MHz.

[0038] Based on the 240 MHz available channel bandwidth formed in pattern 10, further puncturing is performed to obtain patterns 14 to 22.

[0039] Pattern 14: [0011000011111111], corresponds to an available channel bandwidth of 200MHz. Pattern 15: [1100000011111111], corresponds to an available channel bandwidth of 200MHz. Pattern 16: [1111000000111111], corresponds to an available channel bandwidth of 200MHz. Pattern 17: [1111000011001111], corresponds to an available channel bandwidth of 200MHz. Pattern 18: [1111000011110011], corresponds to an available channel bandwidth of 200MHz. Pattern 19: [1111000011111100], corresponds to an available channel bandwidth of 200MHz. Pattern 20: [0000000011111111], corresponds to an available channel bandwidth of 160MHz. Pattern 21: [1111000000001111], corresponds to an available channel bandwidth of 160MHz. Pattern 22: [1111000011110000], corresponds to an available channel bandwidth of 160MHz.

[0040] Based on the 240 MHz available channel bandwidth formed in pattern 11, further puncturing is performed to obtain pattern 31 from pattern 23.

[0041] Pattern 23: [0011111100001111], corresponds to an available channel bandwidth of 200MHz. Pattern 24: [1100111100001111], corresponds to an available channel bandwidth of 200MHz. Pattern 25: [1111001100001111], corresponds to an available channel bandwidth of 200MHz. Pattern 26: [1111110000001111], corresponds to an available channel bandwidth of 200MHz. Pattern 27: [1111111100000011], corresponds to an available channel bandwidth of 200MHz. Pattern 28: [1111111100001100], corresponds to an available channel bandwidth of 200MHz. Pattern 29: [0000111100001111], corresponds to an available channel bandwidth of 160MHz. Pattern 30: [1111000000001111], corresponds to an available channel bandwidth of 160MHz. Pattern 31: [1111111100000000], corresponds to an available channel bandwidth of 160MHz.

[0042] Based on the 240 MHz available channel bandwidth formed in pattern 12, further puncturing is performed to obtain patterns 32 to 40.

[0043] Pattern 32: [0011111111110000], corresponds to an available channel bandwidth of 200MHz. Pattern 33: [1100111111110000], corresponds to an available channel bandwidth of 200MHz. Pattern 34: [1111001111110000], corresponds to an available channel bandwidth of 200MHz. Pattern 35: [1111110011110000], corresponds to an available channel bandwidth of 200MHz. Pattern 36: [1111111100110000], corresponds to an available channel bandwidth of 200MHz. Pattern 37: [1111111111000000], corresponds to an available channel bandwidth of 200MHz. Pattern 38: [0000111111110000], corresponds to an available channel bandwidth of 160MHz. Pattern 39: [1111000011110000], corresponds to an available channel bandwidth of 160MHz. Pattern 40: [1111111100000000], corresponds to an available channel bandwidth of 160MHz.

[0044] Based on the 240 MHz available channel bandwidth formed in pattern 13, further puncturing is performed to obtain patterns 41 to 49.

[0045] Pattern 41: [0000001111111111], corresponds to an available channel bandwidth of 200MHz. Pattern 42: [0000110011111111], corresponds to an available channel bandwidth of 200MHz. Pattern 43: [0000111100111111], corresponds to an available channel bandwidth of 200MHz. Pattern 44: [0000111111001111], corresponds to an available channel bandwidth of 200MHz. Pattern 45: [0000111111110011], corresponds to an available channel bandwidth of 200MHz. Pattern 46: [0000111111111100], corresponds to an available channel bandwidth of 200MHz. Pattern 47: [0000000011111111], corresponds to an available channel bandwidth of 160MHz. Pattern 48: [0000111100001111], corresponds to an available channel bandwidth of 160MHz. Pattern 49: [0000111111110000], corresponds to an available channel bandwidth of 160MHz.

[0046] (B) 320MHz channel puncturing is incompatible with 240MHz channel puncturing.

[0047] Pattern 1: 320MHz [1111111111111111], supports a channel bandwidth of 320MHz and 4096 subcarriers. Pattern 2: 280MHz [0011111111111111], corresponds to an available channel bandwidth of 280MHz. Pattern 3: 280MHz [1100111111111111], supports an available channel bandwidth of 280MHz. Pattern 4: 280MHz [1111001111111111], corresponds to an available channel bandwidth of 280MHz. Pattern 5: 280MHz [1111110011111111], corresponds to an available channel bandwidth of 280MHz. Pattern 6: 280MHz [1111111100111111], supports an available channel bandwidth of 280MHz. Pattern 7: 280MHz [1111111111001111], supports an available channel bandwidth of 280MHz. Pattern 8: 280MHz [1111111111110011], supports an available channel bandwidth of 280MHz. Pattern 9: 280MHz [11111111111111100], supports an available channel bandwidth of 280MHz. Pattern 10: 240MHz [1111000011111111], corresponds to an available channel bandwidth of 240MHz. Pattern 11: 240MHz [1111111100001111], corresponds to an available channel bandwidth of 240MHz. Pattern 12: 240MHz [11111111111110000], corresponds to an available channel bandwidth of 240MHz. Pattern 13: 240MHz [0000111111111111], corresponds to an available channel bandwidth of 240MHz.

[0048] 3.240MHz multiple RU coupling and 320MHz multiple RU coupling Multiple RU coupling method for 3-1.240MHz RU26, RU52, RU26+RU52, RU106, RU26+RU106, RU242, RU484, RU242+RU484, RU996, RU484+RU996, RU242+RU484+RU996, RU484+2*RU996, and 3*RU996.

[0049] Multiple RU coupling method for 3-2.320MHz RU26, RU52, RU26+RU52, RU106, RU26+RU106, RU242, RU484, RU242+RU484, RU996, RU484+RU996, RU242+RU484+RU996, RU484+2*RU996, 3*RU996, 3*RU996+RU484, and 4*RU996.

[0050] RU2*996 represents two RU996s and may be alternatively represented as 2*RU996. RU3*996 may be alternatively represented as 3*RU996, and RU4*996 may be alternatively represented as 4*RU996. RUA+RUB is equivalent to RUB+RUA and refers to a combination or concatenation of RUA and RUB.

[0051] The modes considered for a 1xLTF sequence across a 240MHz bandwidth include those described in 2-1.

[0052] The modes considered for a 1xLTF sequence across a 320MHz bandwidth include those described in section 2-2.

[0053] The modes considered for 2xLTF / 4xLTF sequences across a 240MHz bandwidth include those listed in Table A below. [Table 7]

[0054] 240MHz is formed by linking three 80MHz units. Each 80MHz unit has 36 26-tone RUs, each having a sequence number from smallest to largest and corresponding frequencies from lowest to highest. The implementation is similar for 52-tone RUs (RU52), 106-tone RUs (RU106), 242-tone RUs (RU242), 484-tone RUs (RU484), and 996-tone RUs (RU996).

[0055] Multiple RU coupling involves assigning multiple RUs to a single STA. Each RU still uses its own data subcarrier and pilot subcarrier positions. For example, with RU26+RU52, RU26 uses its own data subcarrier and pilot subcarrier positions, and RU52 uses its own data subcarrier and pilot subcarrier positions.

[0056] Table A shows that RU26+RU52 has fixed combination or linked modes. Since there are four fixed combination modes for every 80MHz, there are 12 combination or linked modes at 240MHz. Details are as follows:

[0057] The first 80MHz of the 240MHz bandwidth is 1st RU26 + RU52: 8th RU26 and 3rd RU52, The second RU26 + RU52: the 11th RU26 and the 6th RU52, The third RU26+RU52: the 26th RU26 and the 11th RU52, and 4th RU26 + RU52: 29th RU26 and 14th RU52 Includes.

[0058] The second 80MHz of the 240MHz bandwidth is, The 5th RU26 + RU52: the 44th RU26 and the 19th RU52, 6th RU26 + RU52: 47th RU26 and 22nd RU52, The 7th RU26+RU52: the 62nd RU26 and the 27th RU52, and 8th RU26 + RU52: 65th RU26 and 30th RU52 Includes.

[0059] The fifth RU26+RU52 in the 240MHz bandwidth is the first RU26+RU52 in the second 80MHz bandwidth. The implementation is the same as described below.

[0060] The third 80MHz of the 240MHz bandwidth is, 9th RU26 + RU52: 80th RU26 and 35th RU52, 10th RU26 + RU52: 83rd RU26 and 38th RU52, The 11th RU26+RU52: the 98th RU26 and the 43rd RU52, and 12th RU26 + RU52: 101st RU26 and 46th RU52 Includes.

[0061] The ninth RU26+RU52 in the 240MHz bandwidth is the first RU26+RU52 in the third 80MHz bandwidth. The implementation is the same as described below.

[0062] It should be understood that each 80MHz has 36 RU26s, which are represented sequentially from left to right (from low frequency to high frequency) as the 1st RU26, the 2nd RU26, ..., and the 36th RU26, as shown in Figure 4. 240MHz consists of three 80MHz units, and the RU26s included in 240MHz are represented sequentially from left to right (from low frequency to high frequency) as the 1st RU26, the 2nd RU26, ..., and the 108th RU26. In other words, the RU26s included in the first 80 MHz of 240 MHz are represented as the 1st RU26, the 2nd RU26, ..., the 36th RU26, in order; the RU26s included in the second 80 MHz of 240 MHz are represented as the 37th RU26, the 38th RU26, ..., the 72nd RU26, in order; and the RU26s included in the third 80 MHz of 240 MHz are represented as the 73rd RU26, the 74th RU26, ..., the 108th RU26, in order.

[0063] Table A shows that RU26+RU106 has fixed combination or linked modes. Since there are four fixed combination modes for every 80MHz, there are 12 combination or linked modes at 240MHz. Details are as follows:

[0064] The first 80MHz of the 240MHz bandwidth is 1st RU26 + RU106: 5th RU26 and 1st RU106, The second RU26 + RU106: the 14th RU26 and the 4th RU106, The third RU26+RU106: the 23rd RU26 and the 5th RU106, and 4th RU26 + RU106: 32nd RU26 and 8th RU106 Includes.

[0065] The second 80MHz of the 240MHz bandwidth is, The 5th RU26 + RU106: the 41st RU26 and the 9th RU106, 6th RU26 + RU106: 50th RU26 and 12th RU106, The 7th RU26+RU106: the 59th RU26 and the 13th RU106, and 8th RU26 + RU106: 68th RU26 and 16th RU106 Includes.

[0066] The fifth RU26+RU106 in the 240MHz bandwidth is the first RU26+RU106 in the second 80MHz bandwidth. The implementation is the same as described below.

[0067] The third 80MHz of the 240MHz bandwidth is, 9th RU26 + RU106: 77th RU26 and 17th RU106, 10th RU26 + RU106: 86th RU26 and 20th RU106, The 11th RU26+RU106: the 95th RU26 and the 21st RU106, and 12th RU26 + RU106: 104th RU26 and 24th RU106 Includes.

[0068] The ninth RU26+RU106 in the 240MHz bandwidth is the first RU26+RU106 in the third 80MHz bandwidth. The implementation is the same as described below.

[0069] It should be understood that both the Xth RU26 and the Yth RU106 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0070] Table A shows that RU242+RU484 has fixed combination or linking modes. Since there are four fixed combination modes for every 80MHz, there are 12 combination or linking modes at 240MHz. Details are as follows:

[0071] The first 80MHz of the 240MHz bandwidth is 1st RU242 + RU484: 1st RU242 and 2nd RU484, The second RU242 + RU484: The second RU242 and the second RU484, 3rd RU242+RU484: 3rd RU242 and 1st RU484, and 4th RU242 + RU484: 4th RU242 and 1st RU484 Includes.

[0072] The second 80MHz of the 240MHz bandwidth is, 5th RU242 + RU484: 5th RU242 and 4th RU484, 6th RU242 + RU484: 6th RU242 and 4th RU484, 7th RU242+RU484: 7th RU242 and 3rd RU484, and 8th RU242 + RU484: 8th RU242 and 3rd RU4844 Includes.

[0073] The fifth RU242+RU484 in the 240MHz bandwidth is the first RU242+RU484 in the second 80MHz bandwidth. The implementation is the same as described below.

[0074] The third 80MHz of the 240MHz bandwidth is, 9th RU242 + RU484: 9th RU242 and 6th RU484, 10th RU242 + RU484: 10th RU242 and 6th RU484, 11th RU242+RU484: 11th RU242 and 5th RU484, and 12th RU242 + RU484: 12th RU242 and 5th RU484 Includes.

[0075] The ninth RU242+RU484 with a 240MHz bandwidth is the first RU242+RU484 with a 3rd bandwidth of 80MHz. The implementation is the same as described below.

[0076] It should be understood that both the Zth RU242 and the Xth RU484 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and further details will not be explained here.

[0077] Table A shows that RU484+RU996 has fixed combination or linked modes. There are eight fixed combination modes at 240MHz. Details are as follows: The first RU484 + RU996: the second RU484 and the second RU996, The second RU484 + RU996: the first RU484 and the second RU996, The third RU484 + RU996: the fourth RU484 and the first RU996, The 4th RU484 + RU996: the 3rd RU484 and the 1st RU996, The 5th RU484 + RU996: the 4th RU484 and the 3rd RU996, The 6th RU484 + RU996: the 3rd RU484 and the 3rd RU996, The 7th RU484 + RU996: the 6th RU484 and the 2nd RU996, and The 8th RU484 + RU996: the 5th RU484 and the 2nd RU996.

[0078] It should be understood that both the Xth RU484 and the Yth RU996 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and further details will not be explained here.

[0079] There are 16 modes at 240MHz, if the RU242+RU484+RU996 modes need to be considered during the design of a 240MHz sequence. Details are as follows: The first RU242 + RU484 + RU996: the second RU242, the second RU484, and the second RU996, The second RU242 + RU484 + RU996: the first RU242, the second RU484, and the second RU996, The third RU242 + RU484 + RU996: the fourth RU242, the first RU484, and the second RU996, The fourth RU242+RU484+RU996: the third RU242, the first RU484, and the second RU996, The 5th RU242 + RU484 + RU996: the 6th RU242, the 4th RU484, and the 1st RU996, The 6th RU242 + RU484 + RU996: the 5th RU242, the 4th RU484, and the 1st RU996, The 7th RU242 + RU484 + RU996: the 8th RU242, the 3rd RU484, and the 1st RU996, The 8th RU242+RU484+RU996: the 7th RU242, the 3rd RU484, and the 1st RU996, The 9th RU242+RU484+RU996: the 6th RU242, the 4th RU484, and the 3rd RU996, The 10th RU242+RU484+RU996: the 5th RU242, the 4th RU484, and the 3rd RU996, The 11th RU242+RU484+RU996: the 8th RU242, the 3rd RU484, and the 3rd RU996, The 12th RU242+RU484+RU996: the 7th RU242, the 3rd RU484, and the 3rd RU996, The 13th RU242+RU484+RU996: the 10th RU242, the 6th RU484, and the 2nd RU996, The 14th RU242+RU484+RU996: the 9th RU242, the 6th RU484, and the 2nd RU996, The 15th RU242+RU484+RU996: the 12th RU242, the 5th RU484, and the 2nd RU996, and The 16th RU242+RU484+RU996: the 11th RU242, the 5th RU484, and the 2nd RU996.

[0080] It should be understood that the Zth RU242, the Xth RU484, and the Yth RU996 are all represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0081] There are six modes at 240MHz, where the RU484+RU2*996 mode needs to be considered during the design of a 240MHz sequence. Details are as follows: The first RU484 + RU2 * 996: the second RU484, the second RU996, and the third RU996, The second RU484 + RU2 * 996: the first RU484, the second RU996, and the third RU996, The third RU484 + RU2 * 996: the fourth RU484, the first RU996, and the third RU996, The 4th RU484 + RU2 * 996: the 3rd RU484, the 1st RU996, and the 3rd RU996, The 5th RU484 + RU2 * 996: the 6th RU484 and the 1st RU996 and the 2nd RU996, and The 6th RU484 + RU2*996: the 5th RU484, the 1st RU996, and the 2nd RU996.

[0082] It should be understood that the Xth RU484 and the Yth RU996 are all represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0083] When the RU996+RU996+RU996 mode needs to be considered during the design of a 240MHz sequence, there is one mode at 240MHz, namely the full-bandwidth mode, specifically a combination or concatenation of the first RU996, the second RU996, and the third RU996.

[0084] The modes considered for 2xLTF / 4xLTF sequences across a 320MHz bandwidth include those listed in Table B below. [Table 8]

[0085] Mode 1: A mode with full bandwidth, puncturing, and multiple RU coupling at 320 MHz. Mode 1 does not consider transmissions acquired by 240 MHz performing puncturing on 320 MHz. In other words, the sequence design primarily considers full bandwidth, puncturing, and multiple RU coupling at 320 MHz / 160 + 160 MHz.

[0086] Each 80MHz unit has 36 26-tone RUs, each with a sequence number from smallest to largest and corresponding frequencies from lowest to highest. The implementation is similar for 52-tone RUs (RU52), 106-tone RUs (RU106), 242-tone RUs (RU242), 484-tone RUs (RU484), and 996-tone RUs (RU996).

[0087] Multiple RU coupling involves assigning multiple RUs to a single STA. Each RU still uses its own data subcarrier and pilot subcarrier positions. For example, with RU26+RU52, RU26 uses its own data subcarrier and pilot subcarrier positions, and RU52 uses its own data subcarrier and pilot subcarrier positions.

[0088] Table B shows that RU26+RU52 has fixed combination or linked modes. Since there are four fixed combination modes for every 80MHz, there are 16 combination or linked modes at 320MHz. Details are as follows: 1st RU26 + RU52: 8th RU26 and 3rd RU52, The second RU26 + RU52: the 11th RU26 and the 6th RU52, The third RU26 + RU52: the 26th RU26 and the 11th RU52, 4th RU26 + RU52: 29th RU26 and 14th RU52, The 5th RU26 + RU52: the 44th RU26 and the 19th RU52, 6th RU26 + RU52: 47th RU26 and 22nd RU52, 7th RU26 + RU52: 62nd RU26 and 27th RU52, 8th RU26 + RU52: 65th RU26 and 30th RU52, 9th RU26 + RU52: 80th RU26 and 35th RU52, 10th RU26 + RU52: 83rd RU26 and 38th RU52, 11th RU26 + RU52: 98th RU26 and 43rd RU52, 12th RU26 + RU52: 101st RU26 and 46th RU52, 13th RU26 + RU52: 116th RU26 and 51st RU52, 14th RU26 + RU52: 119th RU26 and 54th RU52, The 15th RU26+RU52: the 134th RU26 and the 59th RU52, and The 16th RU26 + RU52: the 137th RU26 and the 62nd RU52.

[0089] It should be understood that both the Xth RU26 and the Yth RU52 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and further details will not be explained here.

[0090] Table B shows that RU26+RU106 has fixed combination or linking modes. Since there are four fixed combination modes for every 80MHz, there are 16 combination or linking modes at 320MHz. Details are as follows: 1st RU26 + RU106: 5th RU26 and 1st RU106, The second RU26 + RU106: the 14th RU26 and the 4th RU106, The third RU26 + RU106: the 23rd RU26 and the 5th RU106, 4th RU26 + RU106: 32nd RU26 and 8th RU106, The 5th RU26 + RU106: the 41st RU26 and the 9th RU106, 6th RU26 + RU106: 50th RU26 and 12th RU106, 7th RU26 + RU106: 59th RU26 and 13th RU106, 8th RU26 + RU106: 68th RU26 and 16th RU106, 9th RU26 + RU106: 77th RU26 and 17th RU106, 10th RU26 + RU106: 86th RU26 and 20th RU106, 11th RU26 + RU106: 95th RU26 and 21st RU106, 12th RU26 + RU106: 104th RU26 and 24th RU106, 13th RU26 + RU106: 113th RU26 and 25th RU106, 14th RU26 + RU106: 122nd RU26 and 28th RU106, The 15th RU26+RU106: the 131st RU26 and the 29th RU106, and The 16th RU26 + RU106: the 140th RU26 and the 32nd RU106.

[0091] It should be understood that both the Xth RU26 and the Yth RU106 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0092] Table B shows that RU242+RU484 has fixed combination or linking modes. Since there are four fixed combination modes for every 80MHz, there are 16 combination or linking modes at 320MHz. Details are as follows: 1st RU242 + RU484: 1st RU242 and 2nd RU484, The second RU242 + RU484: The second RU242 and the second RU484, 3rd RU242 + RU484: 3rd RU242 and 1st RU484, 4th RU242 + RU484: 4th RU242 and 1st RU484, 5th RU242 + RU484: 5th RU242 and 4th RU484, 6th RU242 + RU484: 6th RU242 and 4th RU484, 7th RU242 + RU484: 7th RU242 and 3rd RU484, 8th RU242 + RU484: 8th RU242 and 3rd RU484, 9th RU242 + RU484: 9th RU242 and 6th RU484, 10th RU242 + RU484: 10th RU242 and 6th RU484, 11th RU242 + RU484: 11th RU242 and 5th RU484, 12th RU242 + RU484: 12th RU242 and 5th RU484, 13th RU242 + RU484: 13th RU242 and 8th RU484, 14th RU242 + RU484: 14th RU242 and 8th RU484, 15th RU242+RU484: 15th RU242 and 7th RU484, and 16th RU242 + RU484: 16th RU242 and 7th RU484.

[0093] It should be understood that both the Xth RU242 and the Yth RU484 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0094] Table B shows that RU484+RU996 has fixed combination or linking modes. Since there are four fixed combination modes for both the primary 160MHz and secondary 160MHz, there are eight combination or linking modes at 320MHz. Details are as follows. The first RU484 + RU996: the second RU484 and the second RU996, The second RU484 + RU996: the first RU484 and the second RU996, The third RU484 + RU996: the fourth RU484 and the first RU996, The 4th RU484 + RU996: the 3rd RU484 and the 1st RU996, The 5th RU484 + RU996: the 6th RU484 and the 4th RU996, 6th RU484 + RU996: 5th RU484 and 4th RU996, The 7th RU484+RU996: the 8th RU484 and the 3rd RU996, and The 8th RU484 + RU996: the 7th RU484 and the 3rd RU996.

[0095] It should be understood that both the Xth RU484 and the Yth RU996 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and further details will not be explained here.

[0096] The RU2*996 covers two cases: primary 160MHz and secondary 160MHz. Details are as follows. 1st RU2*996: 1st RU996 and 2nd RU996, and The second RU2*996: the third RU996 and the fourth RU996.

[0097] It should be understood that the Xth RU996 is represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0098] RU3*996 refers to any three combinations of the four RU996 values. Details are as follows: 1st RU3*996: 1st RU996, 3rd RU996, and 4th RU996, The second RU3*996: the first RU996, the second RU996, and the fourth RU996, The third RU3*996: the first RU996, the second RU996, and the third RU996, and The fourth RU3*996: the second RU996, the third RU996, and the fourth RU996.

[0099] It should be understood that the Xth RU996 is represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0100] Details regarding the RU3*996+RU484 combination mode are as follows: The first RU3*996+RU484: the second RU484 and the second RU996 and the third RU996 and the fourth RU996, The second RU3*996+RU484: the first RU484, the second RU996, the third RU996, and the fourth RU996, The third RU3*996+RU484: the first RU996 and the fourth RU484 and the third RU996 and the fourth RU996, The fourth RU3*996+RU484: the first RU996, the third RU484, the third RU996, and the fourth RU996, The 5th RU3*996+RU484: the 1st RU996, the 2nd RU996, the 6th RU484, and the 4th RU996, The 6th RU3*996+RU484: the 1st RU996, the 2nd RU996, the 5th RU484, and the 4th RU996, The 7th RU3*996+RU484: the 1st RU996, the 2nd RU996, the 3rd RU996, and the 8th RU484, The 8th RU3*996+RU484: the 1st RU996, the 2nd RU996, the 3rd RU996, and the 7th RU484.

[0101] It should be understood that both the Xth RU996 and the Yth RU484 are represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and further details will not be explained here.

[0102] The RU4*996+RU484 combination mode is a 320MHz full bandwidth mode. Details are as follows: the first RU996, the second RU996, the third RU996, and the fourth RU996.

[0103] It should be understood that the Xth RU996 is represented by numbering from left to right (from low frequency to high frequency). This is the same as described above, and the details will not be explained again here.

[0104] Mode 2: This mode at 320MHz involves full bandwidth, puncturing, and multiple RU coupling, taking into account compatibility with some situations at 240MHz. Specifically, if any 80MHz is punctured from 320MHz or not considered, the remaining RU2*996 formed by not considering one of the RU484 in RU3*996 is not considered. Its puncturing scenario is similar to patterns 14 through 49 (24 in total) in puncturing scenario (A) at 320MHz.

[0105] Mode 3: A mode with full bandwidth, puncturing, and multiple RU coupling at 320 MHz, taking into account compatibility with full bandwidth, puncturing, and multiple RU coupling at 240 MHz.

[0106] Mode 3 considers compatibility with all situations involving MRU and puncturing at 240 MHz. That is, if any 80 MHz is punctured from 320 MHz or not considered, the remaining RU2*996 formed by not considering one RU484 of RU3*996 is not considered. The puncturing scenario is similar to patterns 14 to 49 in the 320 MHz puncturing scenario (A). In addition, the 240 MHz puncturing scenario is considered. Thus, the number of cases for RU2*996 in Mode 3 changes from 2 in Mode 2 to 12.

[0107] There are 16 modes at 320MHz, if the RU242+RU484+RU996 modes need to be considered during the design of a 320MHz sequence. Details are as follows: The first RU242 + RU484 + RU996: the second RU242, the second RU484, and the second RU996, The second RU242 + RU484 + RU996: the first RU242, the second RU484, and the second RU996, The third RU242 + RU484 + RU996: the fourth RU242, the first RU484, and the second RU996, The fourth RU242+RU484+RU996: the third RU242, the first RU484, and the second RU996, The 5th RU242 + RU484 + RU996: the 6th RU242, the 4th RU484, and the 1st RU996, The 6th RU242 + RU484 + RU996: the 5th RU242, the 4th RU484, and the 1st RU996, The 7th RU242 + RU484 + RU996: the 8th RU242, the 3rd RU484, and the 1st RU996, The 8th RU242+RU484+RU996: the 7th RU242, the 3rd RU484, and the 1st RU996, 9th RU242+RU484+RU996: 10th RU242, 6th RU484, and 4th RU996 The 10th RU242 + RU484 + RU996: the 9th RU242, the 6th RU484, and the 4th RU996, The 11th RU242 + RU484 + RU996: the 12th RU242, the 5th RU484, and the 4th RU996, The 12th RU242 + RU484 + RU996: the 11th RU242, the 5th RU484, and the 4th RU996, The 13th RU242+RU484+RU996: the 14th RU242, the 8th RU484, and the 3rd RU996, The 14th RU242 + RU484 + RU996: the 13th RU242, the 8th RU484, and the 3rd RU996, The 15th RU242+RU484+RU996: the 16th RU242 and the 7th RU484 and the 3rd RU996, and The 16th RU242 + RU484 + RU996: the 15th RU242, the 7th RU484, and the 3rd RU996.

[0108] This embodiment of the present application provides a plurality of possible LTF sequences. Some LTF sequences each have the smallest PAPR value within the entire bandwidth. Some LTF sequences have the smallest maximum PAPR considering the entire bandwidth and multiple puncturing patterns comprehensively, so they have optimal overall performance across the entire bandwidth and multiple puncturing patterns. Some LTF sequences comprehensively consider PAPR across the entire bandwidth, multiple puncturing patterns, and multiple multiple RUs, so the LTF sequences have optimal overall performance across the entire bandwidth, multiple puncturing patterns, and multiple multiple RUs.

[0109] 4. After the content related to the embodiments of this application has been explained, the details of the embodiments of this application will be described below. As shown in Figure 5, an embodiment of the present invention provides a method for transmitting physical layer protocol data units. The method includes the following steps:

[0110] S101: Generate a physical layer protocol data unit (PPDU), which includes a long training field (LTF), the length of which is the frequency domain sequence of the LTF, and the length of which is the 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.

[0111] S102; This involves transmitting a PPDU on the target channel, where the bandwidth of the target channel is greater than 160 MHz.

[0112] This embodiment of the present application focuses on the frequency domain sequence of the LTF of the PPDU transmitted over 240 MHz and 320 MHz. Accordingly, the above steps may be simplified as follows:

[0113] S201: Generate a PPDU, which is transmitted over a channel with a bandwidth of 240MHz / 320MHz, and the PPDU includes an LTF, the frequency domain sequence of the LTF being one of several possible LTF frequency domains provided below.

[0114] S202: Transmit PPDU on a channel with a bandwidth of 240MHz / 320MHz.

[0115] This embodiment of the present application focuses on several possible frequency domain sequences of LTF (the frequency domain sequences of LTE are hereinafter abbreviated as LTF sequences). Before describing the several possible LTF sequences provided in this embodiment of the present application, The method for constructing an LTE sequence is explained first.The specific method is as follows: i. Determine the sequence structure of the LTF sequence; and ii. Next (1) Relatively small PAPR: Requirements for linear power amplifiers are relaxed; (2) Phase rotation at non-pilot positions: Multiple streams are considered (the size of the P matrix is ​​2×2, 4×4, 6×6, 8×8, 12×12, or 16×16); (3) Consideration of the puncturing problem; and (4) Consideration of multiple RU joint transmission or multiple RU coupling (where multiple RUs are assigned to the same STA) Based on design criteria including these, the LTF sequence is determined by a computer-based search.

[0116] Alternatively, to put it another way, the design criteria include consideration of the PAPR value in the case of full bandwidth, multiple puncturing patterns, and multiple multiple RU couplings, as well as consideration of phase rotation at non-pilot positions.

[0117] Specifically, the sequence design takes into account the optimal maximum PAPR in multiple cases (e.g., full bandwidth, puncturing, and multiple RUs). Smaller RUs are concatenated with larger RUs within the transmission bandwidth, and the sequence with the optimal PAPR for each type of RU (multiple RU concatenation or single RU) is selected. The LTF is used for MIMO channel estimation, and since the number of streams increases to 16 in the next-generation Wi-Fi standard, the maximum PAPR of the obtained LTF is the result of considering multi-stream scenarios at non-pilot locations (e.g., P matrix sizes of 2x2, 4x4, 6x6, 8x8, 12x12, or 16x16).

[0118] The following describes several possible LTF sequences provided in this embodiment of the present application.

[0119] 1xLTF in a 1.240MHz bandwidth (abbreviated as LTF1x240M sequence) 1-1.

number

[0120] The LTF1x240M sequence exhibits relatively low PAPR values ​​for various puncturing patterns at 240MHz.

[0121] Specifically, when the IFFT size of the Fast Fourier Transform is set to 3072, the PAPR values ​​for the LTF1x240M sequence with puncturing patterns 1 to 10 for 240MHz are listed in Table 7 below. [Table 9]

[0122] Specifically, when the IFFT size of the Fast Fourier Transform is set to 4096, the PAPR values ​​for the LTF1x240M sequence with puncturing patterns 1 to 10 for 240MHz are listed in Table 8 below. [Table 10]

[0123] How to obtain the LTF1x240M sequence in 1-1: i. Determine the sequence structure of the LTF1x240M sequence, and the sequence structure of the LTF1x240M sequence is:

number

number

[0124] In other words, the supplied LTF1x240M sequence has the minimum PAPR value when considering the full bandwidth, various puncturing patterns, and multiple streams. Based on different puncturing patterns,

number

[0125] 1-2.

number

[0126] The LTF1x240M sequence exhibits relatively low PAPR values ​​for various puncturing patterns at 240MHz.

[0127] Specifically, when the IFFT size of the Fast Fourier Transform is set to 3072, the PAPR values ​​for the LTF1x240M sequence with puncturing patterns 1 to 10 for 240MHz are listed in Table 9 below. [Table 11]

[0128] Specifically, when the IFFT size of the Fast Fourier Transform is set to 4096, the PAPR values ​​for the LTF1x240M sequence with puncturing patterns 1 to 10 for 240MHz are listed in Table 10 below. [Table 12]

[0129] In the method for obtaining the LTF1x240M sequence in 1-2, the sequence structure of the LTF1x240M sequence determined by this method is

number

[0130] 1-3.

number

[0131] The LTF1x240M sequence exhibits relatively low PAPR values ​​for various puncturing patterns for 240 MHz. Specifically, the PAPR value of the LTF1x240M sequence for puncturing pattern 1 for 240 MHz is 7.3553 dB.

[0132] In the method for obtaining the LTF1x240M sequence in 1-3, the sequence structure of the LTF1x240M sequence determined by this method is

number

[0133] 1-4.

number

[0134] The LTF1x240M sequence exhibits relatively low PAPR values ​​for various puncturing patterns at 240MHz.

[0135] Specifically, when the IFFT size of the Fast Fourier Transform is set to 3072, the PAPR values ​​for the LTF1x240M sequence with puncturing patterns 1 to 10 for 240MHz are listed in Table 11 below. [Table 13]

[0136] Specifically, when the IFFT size of the fast Fourier transform is set to 4096, the PAPR values of the LTF1x240M sequences for puncturing patterns 1 to 10 for 240 MHz are listed in Table 12 below.

Table 14

[0137] In the method of obtaining the LTF1x240M sequence in 1 - 4, the sequence structure of the LTF1x240M sequence determined by this method is

Number

[0138] 2. 1xLTF at 320 MHz bandwidth (abbreviated as LTF1x320M sequence for short) 2 - 1.

Number

Number

[0139] The LTF1x320M sequence has a relatively low PAPR value for puncturing patterns at 320MHz (A) (i.e., 240MHz puncturing is compatible). For example, the PAPR value of the LTF1x320M sequence for puncturing pattern at 320MHz (A) is 9.0837dB. The PAPR values ​​for other puncturing patterns are each lower than 9.0837dB. For example, the PAPR value for puncturing pattern 1 is 8.9944dB.

[0140] Specifically, for the puncturing pattern at 320MHz (A), the PAPR values ​​for the LTF1x320M sequence from puncturing pattern X to Y for 320MHz are listed in Table 13 below. [Table 15]

[0141] The PAPR values ​​for the LTF1x320M sequence in the puncturing pattern at 320MHz (B) (i.e., 240MHz puncturing is incompatible) are listed in Table 14 below. [Table 16]

[0142] How to obtain the LTF1x320M sequence in 2-1: i. Determine the sequence structure of the LTF1x320M sequence, and the sequence structure of the LTF1x320M sequence is:

number

[0143] 2-2. [Number] exists. LTF1x80M is the 80MHz 1xLTF sequence in the 802.11ax standard. For the specific sequence, refer to the 802.11ax standard.

[0144] The LTF1x320M sequence has a relatively low PAPR value in the punching pattern at 320MHz (i.e., 240MHz punching is not compatible). Specifically, the PAPR value of the LTF1x320M sequence in punching pattern 1 for 320MHz is 7.5364dB.

[0145] 2-3. [Number] exists. LTF1x160M is the 160MHz 1xLTF sequence in the 802.11ax standard. For the specific sequence, refer to the 802.11ax standard.

[0146] The LTF1x320M sequence has a relatively low PAPR value in various punching patterns for 320MHz.

[0147] For example, the PAPR value of the LTF1x320M sequence in the puncturing pattern in (A) at 320 MHz is 9.4002 dB. The PAPR values in other puncturing patterns are all 9.4002 dB. For example, the PAPR value is 8.4364 dB in puncturing pattern 1.

[0148] As another example, among the puncturing patterns at 320 MHz in (B) (i.e., the 240 MHz puncturing is not compatible), the PAPR values of the LTF1x320M sequences from puncturing pattern 1 to 13 for 320 MHz are listed in Table 15 below.

Table 17

[0149] 2-4.

Number

[0150] The PAPR value of the LTF1x320M sequence in puncturing pattern 1 in the puncturing patterns at 320 MHz in (A) is 8.1866 dB.

[0151] 2-5.

Number

[0152] The PAPR value for the LTF1x320M sequence in the puncturing pattern within the puncturing pattern at 320MHz (A) is 9.0837dB. The PAPR values ​​for the other puncturing patterns are also 9.0837dB.

[0153] 2-6.

number

[0154] The PAPR value for the LTF1x320M sequence with puncturing pattern 1 for 320MHz is 6.2230dB.

[0155] 2-7.

number

[0156] The PAPR values ​​for the LTF1x320M sequences in puncturing patterns 1 to 13 within the puncturing pattern at 320MHz (B) are listed in the table below. [Table 18]

[0157] 3. 2xLTF in a 240MHz bandwidth (abbreviated as LTF2x240M sequence) 3-1.

number

[0158] The LTF2x240M sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth of 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz). For example, the PAPR value of the LTF2x240M sequence for the full bandwidth, a certain puncturing pattern, and a certain RU (or multiple RU coupling) is 10.9621 dB. The PAPR values ​​for the other puncturing patterns are each smaller than 10.9621 dB. For example, the PAPR value is 10.9621 dB for the full bandwidth or puncturing pattern 1.

[0159] The sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full 240 MHz bandwidth, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz).

[0160] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or a single RU) at the first 80 MHz, the second 80 MHz, and the third 80 MHz.

[0161] Table of PAPR values ​​for RU at the first 80MHz, second 80MHz, and third 80MHz: [Table 19]

[0162] As shown in Figure 4, the row for RU52 contains one RU26 between the second and third RU52s, one RU26 between the sixth and seventh RU52s, one RU26 between the tenth and eleventh RU52s, and one RU26 between the fourteenth and fifteenth RU52s. Therefore, the values ​​at the corresponding positions in the row for RU52 in the table represent the PAPR values ​​of RU26 at those corresponding positions.

[0163] Similarly, as shown in Figure 4, the row for RU106 contains one RU26 between the first and second RU106, one RU26 between the third and fourth RU106, one RU26 between the fifth and sixth RU106, and one RU26 between the seventh and eighth RU106. Therefore, the values ​​at the corresponding positions in the row for RU106 in the table represent the PAPR values ​​of RU26 at those corresponding positions.

[0164] It should be noted that the values ​​from left to right in the first row of the table above are the PAPR values ​​for the 1st to 36th RU26 at 80MHz for the sequence in question, from left to right. The values ​​from left to right in the second row of the table above are the PAPR values ​​for the 1st to 16th RU52 at 80MHz for the sequence in question, from left to right. The values ​​from left to right in the third row of the table above are the PAPR values ​​for the 1st to 8th RU106 at 80MHz for the sequence in question, from left to right. The values ​​from left to right in the fourth row of the table above are the PAPR values ​​for the 1st to 4th RU242 at 80MHz for the sequence in question, from left to right. The values ​​from left to right in the fifth row of the table above are the PAPR values ​​for the 1st and 2nd RU484 at 80MHz for the sequence in question, from left to right. The value in row 6 of the table above is the PAPR value for RU996 at 80 MHz for the sequence. The value in row 7 of the table above is the PAPR value for the first to fourth RU26+RU52s at 80 MHz intervals for the sequence. The value in row 8 of the table above is the PAPR value for the first to fourth RU26+RU106s at 80 MHz intervals for the sequence. The value in row 9 of the table above is the PAPR value for the first to fourth RU242+RU484s at 80 MHz intervals for the sequence. The value in row 10 of the table above is the PAPR value for RU coupling at 80 MHz for the sequence (the coupling is RU242+RU242 formed by the first and fourth RU242s at 80 MHz intervals).

[0165] It should be understood that the correspondence between PAPR values ​​and RUs in the table above is applicable to the table of PAPR values ​​for other RUs at 80 MHz within this specification. In other words, the PAPR values ​​in the table of PAPR values ​​for other RUs at 80 MHz within this specification correspond one-to-one with the RUs described in the previous paragraph. The following description provides only the PAPR values ​​in the table. The correspondence between PAPR values ​​and RUs in the table is again not described.

[0166] As another example, the sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 20]

[0167] It should be noted that the values ​​from left to right in the first row of the table above are, in order, the PAPR values ​​for the RU coupling of RU484+RU996 in the first to eighth modes at 240MHz. The values ​​from left to right in the second row of the table above are, in order, the PAPR values ​​for the RU coupling of RU242+RU484+RU996 in the first to sixteenth modes at 240MHz. The values ​​from left to right in the third row of the table above are, in order, the PAPR values ​​for the RU coupling of RU484+2*RU996 in the first to sixth modes at 240MHz. The values ​​from left to right in the fourth row of the table above are, in order, the PAPR values ​​for the RU coupling of 2*RU996 in the first to third modes at 240MHz. The values ​​in the fifth row of the table above are the PAPR values ​​for 3*RU996 at 240MHz.

[0168] It should be understood that the correspondence between PAPR values ​​for RUs with bandwidths greater than 80 MHz (i.e., RU couplings) and RU couplings in the table above is applicable to the table of PAPR values ​​for other RUs with bandwidths greater than 80 MHz within this specification. In other words, the PAPR values ​​in the table of PAPR values ​​for other RUs with bandwidths greater than 80 MHz correspond one-to-one with the RU couplings described in the previous paragraph. The following description provides only the PAPR values ​​in the table. The correspondence between PAPR values ​​in the table and RU couplings is again not described.

[0169] 3-2.

number

[0170] The LTF2x240M sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth for 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz). The PAPR value of the LTF2x240M sequence for the full bandwidth or puncturing pattern 1 for 240 MHz is 9.6089 dB.

[0171] The sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full 240 MHz bandwidth, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz).

[0172] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or a single RU) at the first 80 MHz, the second 80 MHz, and the third 80 MHz.

[0173] Table of PAPR values ​​for RU at the first 80MHz and third 80MHz: [Table 21]

[0174] Table of PAPR values ​​for RU at 80MHz (second example): [Table 22]

[0175] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 23]

[0176] 3-3.

number

[0177] The LTF2x240M sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth of 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz). For example, the PAPR value of the LTF2x240M sequence for the full bandwidth, a certain puncturing pattern, or a certain RU (or multiple RU coupling) is 9.7242 dB. The PAPR values ​​for the other puncturing patterns are each lower than 9.7242 dB.

[0178] The sequence exhibits relatively low PAPR values ​​in various cases at 240 MHz (including the full 240 MHz bandwidth, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz).

[0179] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or a single RU) at the first 80 MHz, the second 80 MHz, and the third 80 MHz.

[0180] Table of PAPR values ​​for RU at the first 80MHz and third 80MHz: [Table 24]

[0181] Table of PAPR values ​​for RU at 80MHz (second example): [Table 25]

[0182] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 26]

[0183] 3-4.

number

[0184] The LTF2x240M sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth of 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz). The PAPR value of the LTF2x240M sequence with puncturing pattern 1 for 240 MHz is 9.4304 dB.

[0185] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or a single RU) at the first 80 MHz, the second 80 MHz, and the third 80 MHz.

[0186] Table of PAPR values ​​for RU at the first 80MHz, second 80MHz, and third 80MHz:

[0187] Table of PAPR values ​​for RU at the first 80MHz and third 80MHz: [Table 27]

[0188] Table of PAPR values ​​for RU at 80MHz (second example): [Table 28]

[0189] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 29]

[0190] 3-5.

number

[0191] The LTF2x240M sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth of 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz). For example, the PAPR value of the LTF2x240M sequence for one puncturing pattern is 9.6179 dB. The PAPR values ​​for other puncturing patterns are each smaller than 9.6179 dB.

[0192] The sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth of 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz).

[0193] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or a single RU) at the first 80 MHz, the second 80 MHz, and the third 80 MHz.

[0194] Table of RU values ​​at 80MHz (first): [Table 30]

[0195] Table of RU values ​​at the second 80MHz: [Table 31]

[0196] Table of RU values ​​at 80MHz (third table): [Table 32]

[0197] As another example, the sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 33]

[0198] 4.320MHz bandwidth 2xLTF (abbreviated as LTF2x320M sequence) 4-1.

number

[0199] The sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz). For example, the PAPR value for the LTF2x320M sequence in the full bandwidth, with a certain puncturing pattern, and with a certain RU (or multiple RU coupling) is 10.9310 dB. The PAPR values ​​for the other puncturing patterns are each lower than 10.9310 dB. For example, the PAPR value is 10.4917 dB in the full bandwidth or with puncturing pattern 1.

[0200] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) at the first 80MHz, second 80MHz, third 80MHz, and fourth 80MHz.

[0201] Table of PAPR values ​​for RU at 80MHz for the 1st, 2nd, 3rd, and 4th: [Table 34]

[0202] As another example, the sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 35]

[0203] It should be noted that the values ​​from left to right in the first row of the table above are, in order, the PAPR values ​​for the RU coupling of RU484+RU996 in the first to eighth modes at 320MHz. The values ​​from left to right in the second row of the table above are, in order, the PAPR values ​​for the RU coupling of RU242+RU484+RU996 in the first to sixteenth modes at 320MHz. The values ​​from left to right in the third row of the table above are, in order, the PAPR values ​​for the RU coupling of RU484+3*RU996 in the first to eighth modes at 320MHz. The values ​​from left to right in the fourth row of the table above are, in order, the PAPR values ​​for the RU coupling of 3*RU996 in the first to fourth modes at 320MHz. The values ​​from left to right in the 5th row of the table above are, in order, the PAPR values ​​for the RU coupling of RU484+2*RU996 in the 1st to 24th modes at 320MHz. The values ​​from left to right in the 5th row of the table above are, in order, the PAPR values ​​for the RU coupling of RU484+2*RU996 in the 1st to 6th modes at 320MHz in 80MHz increments. The values ​​from left to right in the 6th row of the table above are, in order, the PAPR values ​​for the RU coupling of 2*RU996 in the 1st to 12th modes at 320MHz. The values ​​from left to right in the 6th row of the table above are, in order, the PAPR values ​​for the RU coupling of 2*RU996 in the 1st to 3rd modes at 320MHz in 80MHz increments. The values ​​in the 7th row of the table are the PAPR values ​​for 4*RU996 at 320MHz.

[0204] The correspondence between PAPR values ​​for RUs with bandwidths greater than 80 MHz (i.e., RU couplings) and RU couplings in the table above should be understood to be applicable to the table of PAPR values ​​for other RUs with bandwidths greater than 80 MHz within this specification. In other words, the PAPR values ​​in the table of PAPR values ​​for other RUs with bandwidths greater than 80 MHz (i.e., RU couplings) correspond one-to-one with the RU couplings described in the previous paragraph. The following description provides only the PAPR values ​​in the table. The correspondence between PAPR values ​​in the table and RU couplings is again not described.

[0205] 4-2.

number

[0206] For example, the PAPR value for an LTF1x320M sequence across the entire bandwidth, with a certain puncturing pattern, or with a certain RU coupling is 10.5867 dB. The PAPR values ​​for other puncturing patterns are also 10.5867 dB, respectively.

[0207] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) at the first 80MHz, second 80MHz, third 80MHz, and fourth 80MHz.

[0208] Table of PAPR values ​​for RU at 80MHz for the 1st and 3rd MHz: [Table 36]

[0209] Table of PAPR values ​​for RU at 80MHz for the second and fourth MHz: [Table 37]

[0210] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 38]

[0211] 4-3.

number

[0212] The LTF2x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz). For example, the PAPR value for the full bandwidth, a certain puncturing pattern, or a certain RU (or multiple RU coupling) is 11.2017 dB.

[0213] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) at the first 80MHz, second 80MHz, third 80MHz, and fourth 80MHz.

[0214] Table of PAPR values ​​for RU at 80MHz for the 1st and 3rd MHz: [Table 39]

[0215] Table of PAPR values ​​for RU at 80MHz for the second and fourth MHz: [Table 40]

[0216] As another example, the sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 41]

[0217] 4-4.

number

[0218] The LTF2x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz).

[0219] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz:

[0220] Table of RU values ​​for the 1st and 4th 80MHz: [Table 42]

[0221] Table of RU values ​​at the second 80MHz: [Table 43]

[0222] Table of RU values ​​at 80MHz (third table): [Table 44]

[0223] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 45]

[0224] 4-5.

number

[0225] The LTF2x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz).

[0226] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz:

[0227] Table of RU values ​​at 80MHz (first): [Table 46]

[0228] Table of RU values ​​at the second 80MHz: [Table 47]

[0229] Table of RU values ​​at 80MHz (third table): [Table 48]

[0230] Table of RU values ​​at 80MHz (4th): [Table 49]

[0231] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 50]

[0232] 4-6.

number

[0233] The sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz).

[0234] Specifically, the PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first to the fourth 80MHz are given below. The RUs are sorted sequentially. For example, RU26 at the first 80MHz are, in order, the 1st to 36th RU26 within the 320MHz bandwidth, based on the order in the table, and RU26 at the second 80MHz are, in order, the 37th to 72nd RU26 within the 320MHz bandwidth, based on the order in the table. [Table 51] [Table 52] [Table 53] [Table 54]

[0235] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 55]

[0236] 4-7.

number

[0237] The sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz).

[0238] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz: [Table 56] [Table 57] [Table 58]

[0239] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 59]

[0240] 4-8.

number

[0241] The sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz).

[0242] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz: [Table 60] [Table 61] [Table 62]

[0243] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 63]

[0244] 4xLTF (abbreviated as LTF4x240M sequence) with a 5.240MHz bandwidth. 5-1.

number

[0245] The LTF4x240M sequence exhibits relatively low PAPR values ​​across the entire bandwidth at 240 MHz, for certain puncturing patterns, or for certain RUs (or multiple RU combinations). For example, the PAPR value of this sequence across the entire bandwidth at 240 MHz is 9.8723 dB. The PAPR values ​​for other puncturing patterns are each lower than 9.8723 dB. The LTF4x240M sequence exhibits relatively low PAPR values ​​in Table A at 240 MHz. For example, the PAPR value of this sequence for certain puncturing patterns or for certain multiple RUs is 9.7535 dB, while the PAPR values ​​for other puncturing patterns are each lower than 9.7535 dB.

[0246] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the third 80 MHz.

[0247] Table of RU values ​​at 80MHz for the 1st, 2nd, and 3rd: [Table 64]

[0248] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 65]

[0249] 5-2.

number

[0250] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the third 80 MHz.

[0251] Table of RU values ​​for the first 80MHz and third 80MHz: [Table 66]

[0252] Table of RU values ​​at the second 80MHz: [Table 67]

[0253] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 68]

[0254] 5-3.

number

[0255] The LTF4x240M sequence has a relatively low PAPR value in Table A at 240 MHz. For example, the PAPR value of this sequence for the entire bandwidth or for a certain puncturing pattern at 240 MHz is 9.7047 dB. The PAPR values ​​for other puncturing patterns are each lower than 9.7047 dB.

[0256] The sequence has relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full 240 MHz bandwidth, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz). For example, the sequence has the following PAPR values ​​for RUs (including multiple RU couplings or single RUs) from the first 80 MHz to the third 80 MHz.

[0257] Table of RU values ​​for the 1st and 3rd 80MHz: [Table 69]

[0258] Table of RU values ​​at the second 80MHz: [Table 70]

[0259] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 71]

[0260] 5-4.

number

[0261] The LTF4x240M sequence exhibits a relatively low PAPR value in Table A at 240 MHz. The PAPR value of the LTF4x240M sequence across the entire 240 MHz bandwidth is 9.2127 dB.

[0262] The sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth of 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz).

[0263] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the third 80 MHz:

[0264] Table of RU values ​​for the 1st and 3rd 80MHz: [Table 72]

[0265] Table of RU values ​​at the second 80MHz: [Table 73]

[0266] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 74]

[0267] 5-5.

number

[0268] The LTF4x240M sequence has a relatively low PAPR value in Table A at 240 MHz. For example, the PAPR value of this sequence for the entire bandwidth or for a certain puncturing pattern at 240 MHz is 9.7047 dB. The PAPR values ​​for other puncturing patterns are each lower than 9.7047 dB.

[0269] The sequence exhibits relatively low PAPR values ​​in various cases in Table A for 240 MHz (including the full bandwidth of 240 MHz, various puncturing patterns for 240 MHz, and various multiple RU couplings for 240 MHz).

[0270] For example, the sequence has the following PAPR values ​​with respect to RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the third 80 MHz:

[0271] Table of RU values ​​for the 1st and 3rd 80MHz: [Table 75]

[0272] Table of RU values ​​at the second 80MHz: [Table 76]

[0273] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table A: [Table 77]

[0274] 4xLTF (abbreviated as LTF4x320M sequence) with a 6.320MHz bandwidth 6-1.

number

[0275] The LTF4x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz). For example, the PAPR value of this sequence for one puncturing pattern for 320 MHz is 10.7708 dB. The PAPR values ​​for other puncturing patterns are each lower than 10.7708 dB. For example, the PAPR value for puncturing pattern 1 is 10.3033 dB.

[0276] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0277] Table of RU values ​​at 80MHz for the 1st, 2nd, 3rd, and 4th: [Table 78]

[0278] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 79]

[0279] 6-2.

number

[0280] The LTF4x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth for 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz). The PAPR value of the LTF4x320M sequence for the full bandwidth or puncturing pattern 1 for 320 MHz is 9.9610 dB.

[0281] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0282] Table of RU values ​​for the 1st and 3rd 80MHz: [Table 80]

[0283] Table of RU values ​​at 80MHz for the second and fourth MHz: [Table 81]

[0284] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 82]

[0285] 6-3.

number

[0286] The LTF4x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz). For example, the PAPR value of the sequence for one pattern for 320 MHz is 10.2793 dB (when RU484 + RU2*996 is not considered). The PAPR values ​​for other puncturing patterns are each less than 10.2793 dB.

[0287] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0288] Table of RU values ​​for the 1st and 3rd 80MHz: [Table 83]

[0289] Table of RU values ​​at 80MHz for the second and fourth MHz: [Table 84]

[0290] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 85]

[0291] 6-4.

number

[0292] The LTF4x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B at 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz). The PAPR value of the LTF4x320M sequence at the full bandwidth of 320 MHz is 9.4793 dB.

[0293] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0294] Table of RU values ​​for the 1st and 4th 80MHz: [Table 86]

[0295] Table of RU values ​​for the second and third 80MHz: [Table 87]

[0296] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 88]

[0297] 6-5.

number

[0298] The LTF4x320M sequence exhibits relatively low PAPR values ​​in various cases in Table B for 320 MHz (including the full bandwidth of 320 MHz, various puncturing patterns for 320 MHz, and various multiple RU couplings for 320 MHz). For example, the PAPR value of the sequence for one pattern for 320 MHz is 10.1186 dB. The PAPR values ​​for other puncturing patterns are each less than 10.1186 dB.

[0299] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0300] Table of RU values ​​for the 1st and 3rd 80MHz: [Table 89]

[0301] Table of RU values ​​at 80MHz for the second and fourth MHz: [Table 90]

[0302] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 91]

[0303] 6-6.

number

[0304] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0305] Table of RU values ​​at 80MHz (first): [Table 92]

[0306] Table of RUs at the second 80 MHz: [Table 93]

[0307] Table of RUs at the third 80 MHz: [Table 94]

[0308] Table of RUs at the fourth 80 MHz: [Table 95]

[0309] The sequence has the following PAPR values for other RUs at a bandwidth greater than 80 MHz in Table B (i.e., RU aggregation): [Table 96]

[0310] 6-7. [Number] exist. LTF4x80M _part1 , LTF4x80M _part2 , LTF4x80M _part3 , LTF4x80M _part4 , and LTF4x80M _part5 are sequences obtained by dividing the 80 MHz 4xLTF sequence based on the sizes of the five parts of the 80 MHz 2xLTF sequence in the 802.11ax standard. LTF4x80MHz is the 80 MHz 4xLTF sequence in the 802.11ax standard. For specific sequences, refer to the 802.11ax standard.

[0311] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0312] Table of RU values ​​at 80MHz (first): [Table 97]

[0313] Table of RU values ​​at the second 80MHz: [Table 98]

[0314] Table of RU values ​​at 80MHz (third table): [Table 99]

[0315] Table of RU values ​​at 80MHz (4th): [Table 100]

[0316] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 101]

[0317] 6-8.

number

[0318] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0319] Table of RU values ​​at 80MHz (first): [Table 102]

[0320] Table of RU values ​​at the second 80MHz: [Table 103]

[0321] Table of RU values ​​at 80MHz (third table): [Table 104]

[0322] Table of RU values ​​at 80MHz (4th): [Table 105]

[0323] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B: [Table 106]

[0324] 6 - 9. [Number] exists.

[0325] LTF4x80M _part1 , LTF4x80M _part2 , LTF4x80M _part3 , and LTF4x80M _part4 is a sequence obtained by dividing the 80 MHz 4xLTF sequence of the 802.11ax standard specification based on the following four parts. The 80 MHz 4xHE - LTF sequence covers from sub - carrier index - 500 to sub - carrier index 500. The number of sequence elements is 1001. Therefore, when there are four parts, LTF4x80M _part1 is the first 250 values, that is, from the first sequence element value to the 250th sequence element value, and so on. Specifically, for example, LTF4x80M _part1 = LTF4x80MHz(1:250).

[0326] LTF4x80 _part2 = LTF4x80MHz(251:500), LTF4x80 _part3 = LTF4x80MHz(502:751), and LTF4x80 _part4 = LTF4x80MHz(752:1001).

[0327] Specifically, the sequence has the following PAPR values for the RU (including multiple RUs combined or a single RU) from the first 80 MHz to the fourth 80 MHz.

[0328] Table of RU in the first 80 MHz:

Table 107

[0329] Table of RU in the second 80 MHz: [Table 108]

[0330] Table of RU values ​​at 80MHz (third table): [Table 109]

[0331] Table of RU values ​​at 80MHz (4th): [Table 110]

[0332] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B.

[0333] For specific RU coupling formats, a bitmap is used to indicate the puncturing pattern. Each bit indicates whether one 20MHz is punctured. For example, "0" indicates that the 20MHz corresponding to that bit is punctured, meaning that the 20MHz is not considered in combinations during multiple RU coupling, while "1" indicates that the 20MHz corresponding to that bit is not punctured. Arbitrarily, the bits correspond from left to right, from the lowest channel frequency to the highest 20MHz.

[0334] RU484+RU3*996:[0011111111111111], [1100111111111111], [1111001111111111], [11111100111 11111], [1111111100111111], [1111111111001111], [1111111111110011], [1111111111111100].

[0335] RU3*996:[1111000011111111], [1111111100001111], [1111111111110000], [0000111111111111].

[0336] RU2*996+RU484:[0011111111110000], [1100111111110000], [1111001 111110000], [1111110011110000], [1111111100110000], [11111111110 00000], [0000001111111111], [0000110011111111], [00001111001111 11], [0000111111001111], [0000111111110011], [0000111111111100].

[0337] RU2*996:[1111111100000000], [0000000011111111], [0000111111110000].

[0338] RU484+RU996:[0011111100000000], [1100111100000000], [1111001100000000], [111111000000 0000], [0000000000111111], [0000000011001111], [0000000011110011], [0000000011111100].

[0339] RU4*996:[1111111111111111]. [Table 111]

[0340] 6-10.

number

[0341] LTF4x80M _part1 LTF4x80M_part2 LTF4x80M _part3 LTF4x80M _part4 , and LTF4x80M _part5 This sequence was obtained by dividing the 80MHz 4xLTF sequence based on the size of the five parts of the 80MHz 2xLTF sequence in the 802.11ax standard. LTF 4x80MHz is the 80MHz 4xLTF sequence in the 802.11ax standard. For specific sequences, please refer to the 802.11ax standard.

[0342] Specifically, the sequence has the following PAPR values ​​for RUs (including multiple RU combinations or single RUs) from the first 80 MHz to the fourth 80 MHz.

[0343] Table of RU values ​​at 80MHz (first): [Table 112]

[0344] Table of RU values ​​at the second 80MHz: [Table 113]

[0345] Table of RU values ​​at 80MHz (third table): [Table 114]

[0346] Table of RU values ​​at 80MHz (4th): [Table 115]

[0347] The sequence has the following PAPR values ​​for other RUs in a bandwidth greater than 80 MHz (i.e., RU coupling) in Table B.

[0348] For specific RU coupling formats, a bitmap is used to indicate the puncturing pattern. Each bit indicates whether one 20MHz is punctured. For example, "0" indicates that the 20MHz corresponding to that bit is punctured, meaning that the 20MHz is not considered in combinations during multiple RU coupling, while "1" indicates that the 20MHz corresponding to that bit is not punctured. Arbitrarily, the bits correspond from left to right, from the lowest channel frequency to the highest 20MHz.

[0349] RU484+RU3*996:[0011111111111111], [1100111111111111], [1111001111111111], [11111100111 11111], [1111111100111111], [1111111111001111], [1111111111110011], [1111111111111100].

[0350] RU3*996:[1111000011111111], [1111111100001111], [1111111111110000], [0000111111111111].

[0351] RU2*996+RU484:[0011111111110000], [1100111111110000], [1111001 111110000], [1111110011110000], [1111111100110000], [11111111110 00000], [0000001111111111], [0000110011111111], [00001111001111 11], [0000111111001111], [0000111111110011], [0000111111111100].

[0352] RU2*996:[1111111100000000], [0000000011111111], [0000111111110000].

[0353] RU484+RU996:[0011111100000000], [1100111100000000], [1111001100000000], [111111000000 0000], [0000000000111111], [0000000011001111], [0000000011110011], [0000000011111100].

[0354] RU4*996:[1111111111111111]. [Table 116]

[0355] The above describes the method of transmitting / receiving the physical layer protocol data unit provided in the embodiments of this application. The following describes the product of the embodiments of this application.

[0356] Embodiments of the present invention are devices for transmitting physical layer protocol data units, A processing unit configured to generate 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 longer 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 160 MHz, and the processing unit, A transmitting unit configured to transmit the PPDU on a target channel, wherein the bandwidth of the target channel is greater than 160 MHz, and The present invention provides an apparatus that includes the following:

[0357] The apparatus for transmitting physical layer protocol data units provided in this embodiment of the present application takes into account phase rotation at non-pilot positions, multiple puncturing patterns of 240 MHz / 320 MHz, and multiple RU coupling, thereby the frequency domain sequence ultimately resulting in the LTF having a relatively small PAPR with multiple RUs in multiple puncturing patterns of 240 MHz / 320 MHz.

[0358] An embodiment of the present invention is a device for receiving a physical layer protocol data unit, A receiving unit that receives a Physical Layer Protocol Data Unit (PPDU) on a target channel, wherein the PPDU includes a long training field, the length of the frequency domain sequence of the long training field is longer than a first length, the first length being the length of the frequency domain sequence of the long training field of a PPDU transmitted on a channel with a bandwidth of 160 MHz, and the bandwidth of the target channel is greater than 160 MHz. A processing unit that parses the aforementioned PPDU and To provide an apparatus having the following features.

[0359] According to the device that receives the Physical Layer Protocol data unit provided in this embodiment of the present application, the frequency domain sequence of the LTF parsed by the device has a relatively small PAPR with multiple RUs in multiple puncturing patterns of 240 MHz / 320 MHz.

[0360] It should be understood that the transmission / reception device for physical layer protocol data units provided in the embodiments of this application has all the functions and technical details of the above-described method of transmission / reception of physical layer protocol data units. For specific technical details, please refer to the above-described method. Details are not described again here.

[0361] The above describes the transmission / reception device for physical layer protocol data units in the embodiments of the present application. The following describes possible product forms of the transmission / reception device for physical layer protocol data units. It should be understood that any form of product having the functions of the above-described transmission / reception device for physical layer protocol data units falls within the scope of protection of the embodiments of the present application. Furthermore, it should be understood that the following description is merely an example and does not limit the product forms of the transmission / reception device for physical layer protocol data units in the embodiments of the present application.

[0362] In possible product configurations, the transmission / reception devices for the physical layer protocol data units described in the embodiments of this application may be implemented using a common bus architecture.

[0363] A device for transmitting physical layer protocol data units includes a processor and a transceiver. The processor is configured to generate physical layer protocol data units (PPDUs), the PPDUs including a long training field (LTF), the length of the frequency-domain sequence of the LTF being longer than a first length, the first length being the length of the frequency-domain sequence of the LTF of the PPDU transmitted over a channel with a bandwidth of 160 MHz. The transceiver is configured to transmit the PPDU over a target channel with a bandwidth greater than 160 MHz.

[0364] It should be understood that a device transmitting physical layer protocol data units possesses all the functions and technical details of the above-described method for transmitting physical layer protocol data units. For specific technical details, please refer to the above-described method. Further details are not provided here.

[0365] Optionally, a device transmitting physical layer protocol data units may further include memory. The memory is configured to store instructions that can be executed by the processor.

[0366] A device for receiving a Physical Layer Protocol data unit includes a processor and a transceiver. The transceiver is configured to receive a Physical Layer Protocol data unit (PPDU) on a target channel, the PPDU including a long training field, the length of the frequency domain sequence of the long training field being longer than a first length, the first length being the length of the frequency domain sequence of the long training field of a PPDU transmitted on a channel with a bandwidth of 160 MHz, and the bandwidth of the target channel being greater than 160 MHz. The processor is configured to parse the PPDU.

[0367] It should be understood that a device receiving a physical layer protocol data unit possesses all the functions and technical details of the method described above for receiving a physical layer protocol data unit. For specific technical details, please refer to the method described above. Further details are not provided here.

[0368] Optionally, a device receiving a physical layer protocol data unit may further include memory. The memory is configured to store instructions that can be executed by the processor.

[0369] In possible product configurations, the transmission / reception device for the physical layer protocol data unit in the embodiments of the present invention may be implemented by a general-purpose processor.

[0370] A device transmitting a physical layer protocol data unit includes a processing circuit and a transceiver interface. The processing circuit is configured to generate a physical layer protocol data unit (PPDU), the PPDU including a long training field (LTF), the length of the frequency domain sequence of the LTF being longer than a first length, the first length being the length of the frequency domain sequence of the LTF of the PPDU transmitted over a channel with a bandwidth of 160 MHz. The transceiver interface is configured to transmit the PPDU over a target channel with a bandwidth greater than 160 MHz.

[0371] Optionally, a device transmitting physical layer protocol data units may further include a storage medium. The storage medium is configured to store instructions that can be executed by a processing circuit.

[0372] It should be understood that a device transmitting physical layer protocol data units possesses all the functions and technical details of the above-described method for transmitting physical layer protocol data units. For specific technical details, please refer to the above-described method. Further details are not provided here.

[0373] A device for receiving a Physical Layer Protocol data unit includes a processing circuit and a transceiver interface. The transceiver interface is configured to receive a Physical Layer Protocol data unit (PPDU) on a target channel, the PPDU including a long training field, the length of the frequency domain sequence of the long training field being longer than a first length, the first length being the length of the frequency domain sequence of the long training field of a PPDU transmitted on a channel with a bandwidth of 160 MHz, and the bandwidth of the target channel being greater than 160 MHz. The processing circuit is configured to parse the PPDU.

[0374] Optionally, a device that receives physical layer protocol data units may further include a storage medium. The storage medium is configured to store instructions that can be executed by the processing circuit.

[0375] It should be understood that a device receiving a physical layer protocol data unit possesses all the functions and technical details of the method described above for receiving a physical layer protocol data unit. For specific technical details, please refer to the method described above. Further details are not provided here.

[0376] In possible product configurations, the transmitting / receiving device for the physical layer protocol data unit in the embodiments of this application may be further implemented by using any combination of one or more FPGAs (field programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, and discrete hardware components, any other suitable circuitry, or any circuitry capable of performing the various functions described throughout this application.

[0377] Embodiments of the present invention further provide a computer program product, which includes computer program code. When the computer program code is executed on a computer, the computer can perform the methods of the embodiment shown in Figure 5.

[0378] Embodiments of the present invention further provide a computer-readable medium that stores program code. When the program code is executed by a computer, the computer can perform the method of the embodiment shown in Figure 5.

[0379] It should be understood that in some embodiments provided herein, the disclosed systems, apparatus, and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementation. For example, multiple units or components may be coupled or integrated into other systems, or some features may be ignored or not performed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be implemented by using some interface. Indirect coupling or communication connection between apparatus or units may be implemented electronically, mechanically, or in other forms.

[0380] Units described as separate parts may or may not be physically separated, and the parts shown as units may or may not be one or more physical units, may be located in one place, or may be distributed across multiple network units. Some or all of the units may be selected based on the actual requirements to achieve the objectives of the solution of the embodiment.

[0381] Furthermore, the functional units of the embodiments of the present invention may be integrated into a single processing unit, or each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0382] When a function is implemented in the form of a software function unit and sold or used as an independent product, the function may be stored on a computer-readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be implemented in the form of a software product, either essentially or in part with respect to the prior art, or all or part of the technical solution. The software product is stored on a storage medium and includes several instructions that instruct a computer device (which may be a personal computer, server, network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0383] The above description merely illustrates a specific implementation of the present application and is not intended to limit the scope of protection. Any modification or substitution that a person skilled in the art could easily conceive within the scope of the art disclosed herein should fall within the scope of protection. Accordingly, the scope of protection of this application should be subject to the scope of protection of the claims.

Claims

1. A method for transmitting physical layer protocol data units, The process involves generating a Physical Layer Protocol Data Unit (PPDU), wherein the PPDU includes a long training field, and the process of generating the PPDU includes a long training field. The PPDU is transmitted on a target channel, the bandwidth of the target channel is 320 MHz, and the frequency domain sequence of the long training field of the PPDU is [Math 1] And, LTF1x80MHz left 80MHz in the 802.11ax standard left It is a 1x LTF sequence, LTF1x80MHz right 80MHz in the 802.11ax standard right The transmission is a 1x LTF sequence. A method of having.

2. LTF1x80MHz left teeth, [Math 2] And, LTF1x80MHz right teeth, [Math 3] That is, The method according to claim 1.

3. A method for receiving a physical layer protocol data unit, The method involves receiving a Physical Layer Protocol Data Unit (PPDU) on a target channel, wherein the PPDU includes a long training field, the bandwidth of the target channel is 320 MHz, and the frequency domain sequence of the long training field of the PPDU is [Math 4] and is LTF1x80MHz left is 80MHz in the 802.11ax standard left is a 1x LTF sequence, and LTF1x80MHz right is 80MHz in the 802.11ax standard right is a 1x LTF sequence, said receiving, To parse the aforementioned PPDU and A method of having.

4. LTF1x80MHz left teeth, [Math 5] And, LTF1x80MHz right teeth, [Math 6] That is, The method according to claim 3.

5. A device for transmitting physical layer protocol data units, A processing unit configured to generate a Physical Layer Protocol Data Unit (PPDU), wherein the PPDU includes a long training field, and the processing unit and A transmitting unit configured to transmit the PPDU on a target channel, wherein the bandwidth of the target channel is 320 MHz, and the frequency domain sequence of the long training field of the PPDU is [Number 7] And, LTF1x80MHz left 80MHz in the 802.11ax standard left It is a 1x LTF sequence, LTF1x80MHz right 80MHz in the 802.11ax standard right The transmission unit and the 1x LTF sequence A device having.

6. LTF1x80MHz left teeth, [Number 8] And, LTF1x80MHz right teeth, [Number 9] That is, The apparatus according to claim 5.

7. A device for receiving physical layer protocol data units, A receiving unit configured to receive a Physical Layer Protocol Data Unit (PPDU) on a target channel, wherein the PPDU includes a long training field, the bandwidth of the target channel is 320 MHz, and the frequency domain sequence of the long training field of the PPDU is [Number 10] And, LTF1x80MHz left 80MHz in the 802.11ax standard left It is a 1x LTF sequence, LTF1x80MHz right 80MHz in the 802.11ax standard right The receiving unit is a 1x LTF sequence, A processing unit configured to parse the PPDU A device having.

8. LTF1x80MHz left teeth, [Math 11] And, LTF1x80MHz right teeth, [Math 12] That is, The apparatus according to claim 7.

9. Configured to store computer programs, The computer program, when executed on a computer, has instructions that cause the computer to perform the method described in claim 1 or 2. Computer-readable storage medium.

10. A computer program having an instruction that causes a computer to perform the method described in claim 1 or 2 when executed on a computer.

11. Configured to store computer programs, The computer program, when executed on a computer, has instructions that cause the computer to perform the method described in claim 3 or 4. Computer-readable storage medium.

12. A computer program having instructions that cause a computer to perform the method described in claim 3 or 4 when executed on a computer.

Images