Communication methods and communication devices

Abstract

This application provides a communication method. This method may be applied to WLAN systems supporting 802.11 series protocols such as IEEE 802.11ax next-generation Wi-Fi protocols like 802.11be, Wi-Fi 7, or EHT, and next-generation protocols like Wi-Fi 8, or it may be applied to UWB-based wireless personal area network systems and sensing systems. The method includes the following: Devices communicate with each other based on frequency resources, the frequency resources include multiple resource units (MRUs), the MRUs include k × 996 + m × 484-tone MRUs, where k is an integer greater than or equal to 4 and m is equal to 0 or 1. The MRUs are designed for bandwidths greater than 320 MHz to meet OFDMA transmission requirements in future high-bandwidth scenarios.

Description

Technical Field

[0001] This application claims the priority of Chinese Patent Application No. 202310486086.2, titled "COMMUNICATION METHOD AND COMMUNICATION APPARATUS", filed with the China National Intellectual Property Administration on April 28, 2023, the entire content of which is incorporated herein by reference.

[0002] This application relates to the field of communication technologies, and more particularly, to communication methods and communication apparatuses.

Background Art

[0003] With the development of wireless local area networks (WLANs), orthogonal frequency division multiple access (OFDMA) technology has been newly introduced, enabling the entire bandwidth to be divided into multiple resource units (RUs). In other words, the allocation of user frequency domain resources is based on resource units rather than channels. For example, within a 20 MHz channel, there may be multiple RUs, and the multiple RUs may be small RUs, such as 26-tone RUs, 52-tone RUs, or 106-tone RUs, where "tone" indicates the number of subcarriers. Additionally, the RU may alternatively be a large RU, such as a 242-tone RU, 484-tone RU, or 996-tone RU.

[0004] In 802.11be, the concept of multiple resource units (MRUs) is defined, and multiple RUs can be allocated to the same user to implement more flexible frequency resource allocation. An MRU formed by combining large RUs is referred to as a large MRU, and an MRU formed by combining small RUs is referred to as a small MRU.

[0005] The standard defines corresponding MRU patterns for different bandwidths, such as 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz. However, new wider bandwidths (e.g., 640 MHz or 480 MHz) may appear in future standards, and MRU patterns within these wider bandwidths will need to be designed using new methods. [Overview of the Initiative]

[0006] Embodiments of this application provide a communication method for designing MRU patterns for high bandwidths (e.g., 640 MHz or 480 MHz) that may appear in future Wi-Fi standards in order to meet OFDMA transmission requirements in future high-bandwidth scenarios. [Means for solving the problem]

[0007] According to a first aspect, a communication method is provided. The method may be performed by an access point or station, or by a circuit configured in an access point or station. This is not limited to the present application.

[0008] The communication method includes a first device communicating with a second device based on frequency resources, the frequency resources including multiple resource units (MRUs), the MRUs including k × 996 + m × 484 - tone MRUs, where k is an integer greater than or equal to 4, and m is equal to 0 or 1.

[0009] Based on the technical solution described above, devices can communicate with each other using MRUs, the size of which may be k×996+m×484-tone MRU, where k is an integer greater than or equal to 4, and m is equal to 0 or 1. The MRUs in this technical solution are different from the MRU types defined in existing standards. The small MRUs defined in existing standards include two types: 52+26-tone MRU and 106+26-tone MRU, while the large MRU types include 484+242-tone MRU, 996+484-tone MRU, 996+484+242-tone MRU, 2×996+484-tone MRU, 3×996-tone MRU, and 3×996+484-tone MRU, which are MRUs designed for bandwidths of 320 MHz or less. In this solution, the MRU type shown is k × 996 + m × 484, and it shows an MRU pattern designed for ultra-high bandwidths of over 320 MHz, and can also show an MRU pattern for next-generation WLAN ultra-high bandwidths (e.g., 640 MHz or 480 MHz) to meet the requirements of OFDMA transmission in future high-bandwidth scenarios. Here, k is an integer greater than or equal to 4, and m is equal to 0 or 1.

[0010] Referring to the first embodiment, in some implementations of the first embodiment, the frequency resource further includes resource units RU, the RU including at least one of 484-tone RU, 996-tone RU, 2×996-tone RU, and 4×996-tone RU.

[0011] Based on the technical solutions described above, in future high-bandwidth scenarios, devices can communicate with each other using larger RUs and MRUs. Specifically, certain forms of RUs include at least one of 484-tone RUs, 996-tone RUs, 2×996-tone RUs, and 4×996-tone RUs, and certain forms of MRUs include k×996+m×484-tone MRUs. In this technical solution, RUs and MRUs can be further compatible with RU and MRU types defined after OFDMA technology was introduced into the existing 802.11be standard. For example, an RU may further include a 242-tone RU. In another example, an MRU may further include k1×996+m×484-tone MRUs (e.g., 3×996-tone MRUs and 3×996+484-tone MRUs), where k1 is a positive integer less than 4 and m is equal to 0 or 1.

[0012] Referring to the first embodiment, in some implementations of the first embodiment, the MRU is part of a frequency resource within a 640 MHz bandwidth, and the MRU includes at least one of the following: 7×996-tone MRU, 6×996-tone MRU, 5×996-tone MRU, 7×996+484-tone MRU, 6×996+484-tone MRU, 5×996+484-tone MRU, and 4×996+484-tone MRU.

[0013] Based on the technical solutions described above, if the MRUs occupied for communication between devices are part of the frequency resources within the 640 MHz bandwidth, the MRUs may include at least one of the following: 7×996-tone MRUs, 6×996-tone MRUs, 5×996-tone MRUs, 7×996+484-tone MRUs, 6×996+484-tone MRUs, 5×996+484-tone MRUs, and 4×996+484-tone MRUs, and multiple stations may improve the flexibility of the solution by jointly using the 640 MHz bandwidth by using OFDMA technology.

[0014] Referring to the first embodiment, in some implementations of the first embodiment, if the 40 MHz subchannel is not punctured within the 640 MHz bandwidth, the MRU includes at least one of a 7×996-tone MRU, a 6×996-tone MRU, and a 5×996-tone MRU, or if the punctured subchannel within the 640 MHz bandwidth includes one 40 MHz subchannel, the MRU includes at least one of a 7×996+484-tone MRU, a 6×996+484-tone MRU, a 5×996+484-tone MRU, and a 4×996+484-tone MRU.

[0015] Based on the technical solutions described above, two different MRU mode design solutions are provided by using whether or not to ignore the punctured 40 MHz (or 484-tone RU) subchannel as a criterion. In the solution where the punctured 40 MHz subchannel is not ignored, a simplified solution is provided based on a double extension of the 320 MHz MRU modes (e.g., 7×996-tone MRU, 6×996-tone MRU, 5×996-tone MRU). In the solution where the punctured 40 MHz subchannel is ignored, a more improved MRU mode design solution for 640 MHz is provided (e.g., 7×996+484-tone MRU, 6×996+484-tone MRU, 5×996+484-tone MRU, and 4×996+484-tone MRU).

[0016] Referring to the first embodiment, in some implementations of the first embodiment, if one 80 MHz subchannel is punctured within a 640 MHz bandwidth, the MRU includes 7 × 996-tone MRUs; if one 160 MHz subchannel is punctured within a 640 MHz bandwidth, the MRU includes 6 × 996-tone MRUs; if one 160 MHz subchannel and one 80 MHz subchannel are punctured within a 640 MHz bandwidth, the MRU includes 5 × 996-tone MRUs, the punctured 160 MHz subchannel is 160 MHz having the lowest or highest frequency within a 640 MHz bandwidth; if one 40 MHz subchannel is punctured within a 640 MHz bandwidth, the MRU includes 7 × 996 + 484-tone MRUs, the punctured 160 MHz subchannel and one 40 MHz subchannel are 640 When punctured within a 640 MHz bandwidth, the MRU includes 6 × 996 + 484-tone MRU, and the punctured 80 MHz subchannel is 80 MHz with the lowest or highest frequency within a 640 MHz bandwidth; when one 160 MHz subchannel and one 40 MHz subchannel are punctured within a 640 MHz bandwidth, the MRU includes 5 × 996 + 484-tone MRU, and the punctured 160 MHz subchannel is 160 MHz with the lowest or highest frequency within a 640 MHz bandwidth; when one 160 MHz subchannel, one 80 MHz subchannel, and one 40 MHz subchannel are punctured within a 640 MHz bandwidth, the MRU includes 4 × 996 + 484-tone MRU, and the punctured 160 MHz subchannel is 160 MHz with the lowest or highest frequency within a 640 MHz bandwidth; The MHz subchannel is 80 MHz, having the lowest or highest frequency within the remaining 480 MHz bandwidth after the 160 MHz subchannel has been punctured within the 640 MHz bandwidth.

[0017] Based on the technical solutions described above, different bandwidths and different numbers of subchannels (e.g., at least one of 40 MHz, 80 MHz, and 160 MHz subchannels) can be punctured in a 640 MHz bandwidth to implement more flexible spectral resource utilization.

[0018] Referring to the first embodiment, in some implementations of the first embodiment, the MRU is part of a frequency resource within a 480 MHz bandwidth, and the MRU includes at least one of a 5×996+484-tone MRU, a 5×996-tone MRU, a 4×996+484-tone MRU, and a 4×996-tone MRU.

[0019] Based on the technical solutions described above, if the MRU occupied for communication between devices is part of the frequency resources within the 480 MHz bandwidth, the MRU may include at least one of the following: 5×996+484-tone MRU, 5×996-tone MRU, 4×996+484-tone MRU, and 4×996-tone MRU, and multiple stations can jointly use the 480 MHz bandwidth by using OFDMA technology to improve the flexibility of the solution.

[0020] Referring to the first embodiment, in some implementations of the first embodiment, if the MRU corresponding to the 480 MHz bandwidth reuses the MRU corresponding to the 640 MHz bandwidth, the MRU corresponding to the 480 MHz bandwidth includes at least one of the 5×996+484 tone MRU, 5×996 tone MRU, and 4×996+484 tone MRU of the 640 MHz bandwidth; if the MRU corresponding to the 480 MHz bandwidth does not reuse any portion of the MRU within the 640 MHz bandwidth, the MRU corresponding to the 480 MHz bandwidth is generated for the 480 MHz physical layer protocol data unit (PPDU).

[0021] Based on the technical solutions described above, two different MRU mode design solutions for the 640 MHz bandwidth are provided by using whether or not a portion of the MRU corresponding to the 480 MHz bandwidth is reused as a reference. In the solution where the MRU corresponding to the 640 MHz bandwidth is reused, a simple reuse solution is provided (e.g., at least one of 5×996+484-tone MRU, 5×996-tone MRU, and 4×996+484-tone MRU for the 640 MHz bandwidth). In the solution where the MRU corresponding to the 640 MHz bandwidth is not reused, an MRU mode design solution for the 480 MHz PPDU is provided.

[0022] Referring to the first embodiment, in some implementations of the first embodiment, if one 40 MHz subchannel is punctured within a 480 MHz bandwidth, the MRU includes 5 × 996 + 484-tone MRU; if one 80 MHz subchannel is punctured within a 480 MHz bandwidth, the MRU includes 5 × 996-tone MRU; if one 80 MHz subchannel and one 40 MHz subchannel are punctured within a 480 MHz bandwidth, the MRU includes 4 × 996 + 484-tone MRU, the punctured 80 MHz subchannel is 80 MHz having the lowest or highest frequency within the 480 MHz bandwidth; or if one 160 MHz subchannel is punctured within a 480 MHz bandwidth, the MRU includes 4 × 996-tone MRU.

[0023] Based on the technical solutions described above, different bandwidths and different numbers of subchannels (e.g., 40 MHz, 80 MHz, and 160 MHz subchannels) may be punctured within a 480 MHz bandwidth to implement more flexible spectral resource utilization.

[0024] Referring to the first aspect, in some implementations of the first aspect, the method is that the first device determines frequency resources based on a resource allocation field, where the resource allocation field includes information indicating the MRU, and when the value range of the resource allocation field is 304 or more, the resource allocation field indicates the MRU.

[0025] Referring to the first aspect, in some implementations of the first aspect, when the value range of the resource allocation field is 0 or more and 303 or less, the resource allocation field indicates the MRU corresponding to a bandwidth of 320 MHz or less.

[0026] Referring to the first aspect, in some implementations of the first aspect, the resource allocation field further includes information indicating the resource unit RU, and when the value range of the resource allocation field is 304 or more, the resource allocation field indicates the RU, and the RU includes at least one of a 484 - tone RU, a 996 - tone RU, a 2×996 - tone RU, and a 4×996 - tone RU.

[0027] Referring to the first aspect, in some implementations of the first aspect, the resource allocation field is X bits, and X is an integer of 9 or more.

[0028] Based on the above technical solutions, the resource indication information may use an unused information segment within the resource allocation field defined by the existing protocol, or the function of indicating frequency resources using the resource indication information may be implemented by expanding the resource allocation field defined by the existing protocol to improve the compatibility of the solutions.

[0029] Referring to the first aspect, in some implementations of the first aspect, the frequency resource is a part of the frequency resources within a 2×P MHz bandwidth, where P is greater than 160, and the method further includes the first device determining the frequency resource based on a resource allocation field and a combination field.

[0030] Referring to the first aspect, in some implementations of the first aspect, the resource allocation field includes information indicating the MRU corresponding to the P MHz bandwidth, and the combination field indicates whether the first resource block on the left side of the direct current (DC) subcarrier within 2×P MHz and the second resource block on the right side of the DC subcarrier are combined.

[0031] Referring to the first aspect, in some implementations of the first aspect, when the combination field indicates that the first resource block and the second resource block are not combined, the first resource block and the second resource block are separately allocated to different stations, or when the combination field indicates that the first resource block and the second resource block are combined, the first resource block and the second resource block are allocated to the same station.

[0032] Based on the above technical solution, the combination field may be a field indicating whether the first resource block on the left side of the DC subcarrier within the bandwidth and the second resource block on the right side of the DC subcarrier are combined to indicate whether the first resource block and the second resource block are allocated to the same station. Compared with the above manner in which the frequency resource is indicated by the resource allocation field, the manner in which the combination field is used together with the resource allocation field is simpler and more efficient because the information included in the table corresponding to the resource allocation field is much less than the information included in the table corresponding to the resource allocation field in the second aspect.

[0033] Referring to the first embodiment, in some implementations of the first embodiment, the first resource block includes one of the following: a first adjacent RU to the left of a DC subcarrier in bandwidth, a first adjacent MRU to the left of a DC subcarrier in bandwidth, a second adjacent RU to the left of a DC subcarrier in bandwidth, or a second adjacent MRU to the left of a DC subcarrier in bandwidth, and the second resource block includes one of the following: a first adjacent RU to the right of a DC subcarrier in bandwidth, a first adjacent MRU to the right of a DC subcarrier in bandwidth, a second adjacent RU to the right of a DC subcarrier in bandwidth, or a second adjacent MRU to the right of a DC subcarrier in bandwidth.

[0034] According to a second aspect, a communication method is provided. The method may be performed by an access point or by a circuit configured within the access point. This is not limited to the present application. For convenience, the following example will be used in which the method is performed by an access point.

[0035] The access point generates a physical layer protocol data unit (PPDU), which includes a resource allocation field indicating the allocation status of the station's frequency resources. The frequency resources include multiplexed resource units (MRUs). The access point transmits the PPDU to the station, and if the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU corresponding to a bandwidth wider than 320 MHz.

[0036] Based on the technical solution described above, the PPDU transmitted to the station by the access point includes a resource allocation field, which can indicate the allocation status of frequency resources, and the frequency resources include MRU. Specifically, if the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU corresponding to a bandwidth greater than 320 MHz. This solution adds a new indication of an MRU corresponding to a bandwidth greater than 320 MHz to the resource allocation field, and can indicate an MRU pattern for next-generation WLAN ultra-high bandwidth (e.g., 640 MHz or 480 MHz) to meet the requirements of OFDMA transmission in future high-bandwidth scenarios.

[0037] Referring to the second aspect, in some implementations of the second aspect, if the value range of the resource allocation field is 0 or greater and 303 or less, the resource allocation field indicates an MRU corresponding to a bandwidth of 320 MHz or less.

[0038] Referring to the second aspect, in some implementations of the second aspect, the frequency resource further includes resource units RU, and if the value range of the resource allocation field is 304 or greater, the resource allocation field indicates a RU, and the RU includes at least one of 484-tone RU, 996-tone RU, 2×996-tone RU, and 4×996-tone RU.

[0039] Based on the technical solutions described above, the resource allocation field may further indicate RUs. Specifically, the specific forms of the RUs may include at least one of the following: 484-tone RU, 996-tone RU, 2×996-tone RU, and 4×996-tone RU.

[0040] Referring to the second aspect, in some implementations of the second aspect, the resource allocation field is X bits, where X is an integer greater than or equal to 9.

[0041] Based on the technical solutions described above, resource instruction information may use unused information segments within resource allocation fields defined in existing protocols, or the functionality to use resource instruction information to instruction frequency resources may be implemented by extending resource allocation fields defined in existing protocols to improve compatibility of the solutions.

[0042] According to a third aspect, a communication method is provided. The method may be performed by a station or by a circuit configured in the station. This is not limited to the present application. For convenience, the following examples will be used in which the method is performed by a station.

[0043] The communication method includes the station receiving a PPDU from an access point, the PPDU including a resource allocation field, the resource allocation field indicating the allocation status of the station's frequency resources, and the frequency resources including a multiplex resource unit (MRU); and the station determining the allocated frequency resources based on resource instruction information, wherein if the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU corresponding to a bandwidth wider than 320 MHz. For a description related to frequency resources and resource allocation fields, see the second aspect. Further details are not provided here.

[0044] Referring to the third aspect, in some implementations of the third aspect, the method further includes the station transmitting information to an access point on an allocated frequency resource, or the station receiving data from an access point on an allocated frequency resource.

[0045] For the technical effects of the method described in the third aspect, please refer to the technical effects in the second aspect and the possible designs of the second aspect.

[0046] A fourth aspect provides a communication method. The method may be performed by an access point or by a circuit configured within the access point. This is not limited to the present application. For convenience, the following example will be used in which the method is performed by an access point.

[0047] The communication method includes the access point generating a physical layer protocol data unit (PPDU), the PPDU including a resource allocation field and a binding field, the resource allocation field and the binding field indicating the allocation status of the station's frequency resources, and the access point transmitting the PPDU to the station.

[0048] Based on the technical solution described above, the PPDU transmitted to the station by the access point includes a resource allocation field and a coupling field, which can indicate the allocation status of the station's frequency resources.

[0049] Referring to the fourth aspect, in some implementations of the fourth aspect, the resource allocation field includes information indicating the MRU corresponding to the P MHz bandwidth, where P is greater than 160, and the coupling field indicates whether the first resource block on the left of the DC subcarrier and the second resource block on the right of the DC subcarrier are coupled at 2 × P MHz.

[0050] Specifically, the resource allocation field includes information indicating the MRU corresponding to the P MHz bandwidth, and the coupling field indicates whether the first resource block on the left of the DC subcarrier and the second resource block on the right of the DC subcarrier are coupled within 2 × P MHz, where the 2 × P MHz bandwidth is greater than the 320 MHz bandwidth. In this solution, the resource allocation and coupling fields may also indicate the MRU corresponding to bandwidths greater than 320 MHz, and may indicate the MRU pattern for next-generation WLAN ultra-high bandwidth (e.g., 640 MHz or 480 MHz) to meet the needs of OFDMA transmission in future high-bandwidth scenarios.

[0051] Furthermore, compared to the above-described method in which frequency resources are indicated by resource allocation fields, the method in which a join field is used together with the resource allocation field is simpler and more efficient because the information contained in the table corresponding to the resource allocation field is far less than the information contained in the table corresponding to the resource allocation field in the second embodiment.

[0052] Referring to the fourth aspect, in some implementations of the fourth aspect, if the join field indicates that the first resource block and the second resource block are not joined, the first resource block and the second resource block are assigned separately to different stations, or if the join field indicates that the first resource block and the second resource block are joined, the first resource block and the second resource block are assigned to the same station.

[0053] Referring to the fourth aspect, in some implementations of the fourth aspect, the frequency resources further include multiplexed resource units (MRUs).

[0054] Referring to the fourth aspect, in some implementations of the fourth aspect, the frequency resource further includes resource units RU, the RU including at least one of 484-tone RU, 996-tone RU, 2×996-tone RU, and 4×996-tone RU.

[0055] Referring to the fourth aspect, in some implementations of the fourth aspect, the first resource block includes one of the following: a first adjacent RU to the left of the DC subcarrier in the bandwidth, a first adjacent MRU to the left of the DC subcarrier in the bandwidth, a second adjacent RU to the left of the DC subcarrier in the bandwidth, or a second adjacent MRU to the left of the DC subcarrier in the bandwidth, and the second resource block includes one of the following: a first adjacent RU to the right of the DC subcarrier in the bandwidth, a first adjacent MRU to the right of the DC subcarrier in the bandwidth, a second adjacent RU to the right of the DC subcarrier in the bandwidth, or a second adjacent MRU to the right of the DC subcarrier in the bandwidth.

[0056] According to a fifth aspect, a communication method is provided. The method may be performed by a station or by a circuit configured in the station. This is not limited to the present application. For convenience, the following examples will be used to illustrate the method performed by a station.

[0057] The communication method includes the station receiving a PPDU from an access point, the PPDU including a resource allocation field and a binding field, the resource allocation field and the binding field indicating the allocation status of the station's frequency resources, and the station determining the frequency resources allocated based on resource instruction information. For a description of frequency resources, the first resource block, and the second resource block, see the fourth aspect. Further details are not described here.

[0058] Referring to the fifth aspect, in some implementations of the fifth aspect, the method further includes the station transmitting information to an access point on an allocated frequency resource, or the station receiving data from an access point on an allocated frequency resource.

[0059] For the technical effects of the method described in the fifth aspect, please refer to the fourth aspect and the technical effects in possible designs of the fourth aspect.

[0060] According to the sixth aspect, a communication device is provided for implementing the method described in the first aspect. The device is A transceiver module configured to communicate with a second device based on frequency resources, wherein the frequency resources include multiple resource units (MRUs), the MRUs include k × 996 + m × 484 - tone MRUs, where k is an integer greater than or equal to 4, and m is equal to 0 or 1.

[0061] For example, the transceiver module communicates with a second device by using frequency resources within a 640 MHz bandwidth, or the transceiver module communicates with a second device by using frequency resources within a 480 MHz bandwidth.

[0062] For the technical effects of the apparatus shown in the sixth aspect, please refer to the technical effects of the first aspect and the possible designs of the first aspect.

[0063] According to the seventh aspect, a communication device is provided for implementing the method described in the second aspect. The device includes a processing module configured to generate a PPDU, the PPDU including a resource allocation field, the resource allocation field indicating the allocation status of the station's frequency resources, the frequency resources including a multiplexed resource unit MRU. The access point transmits the PPDU to the station, and if the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU corresponding to a bandwidth wider than 320 MHz.

[0064] For example, the transceiver module may transmit the PPDU to the station using a 640 MHz bandwidth, or it may transmit the PPDU to the station using a 480 MHz bandwidth.

[0065] For the technical effects of the apparatus shown in the seventh aspect, please refer to the technical effects of the second aspect and the possible designs of the second aspect.

[0066] According to the eighth aspect, a communication device is provided which is configured to implement the method described in the third aspect. The device is A transceiver module configured to receive a PPDU from an access point, wherein the PPDU includes a resource allocation field, the resource allocation field indicating the allocation status of the station's frequency resources, and the frequency resources include a multiplex resource unit (MRU); and a processing module configured to determine the allocated frequency resources based on resource indication information, wherein when the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU corresponding to a bandwidth wider than 320 MHz.

[0067] Referring to the eighth aspect, in some implementations of the eighth aspect, the transceiver module is further configured to transmit information to an access point on an allocated frequency resource, or to receive data from an access point on an allocated frequency resource.

[0068] For example, the transceiver module receives data from the access point via a 640 MHz bandwidth RU or MRU, or the transceiver module receives data from the access point via a 480 MHz bandwidth RU or MRU.

[0069] For the technical effects of the apparatus shown in the eighth aspect, please refer to the technical effects of the third aspect and the possible designs of the third aspect.

[0070] According to the ninth aspect, a communication device is provided configured to implement the method described in the fourth aspect. The device includes a processing module configured to generate a PPDU, the PPDU comprising a resource allocation field and a binding field, the resource allocation field and the binding field indicating the allocation status of the station's frequency resources, and a transceiver module configured to transmit the PPDU to the station.

[0071] For example, the transceiver module may transmit the PPDU to the station using a 640 MHz bandwidth, or it may transmit the PPDU to the station using a 480 MHz bandwidth.

[0072] For the technical effects of the apparatus shown in the ninth aspect, please refer to the technical effects of the fourth aspect and the possible designs of the fourth aspect.

[0073] According to the tenth aspect, a communication device is provided which is configured to implement the method described in the fifth aspect. The device is A transceiver module configured to receive a PPDU from an access point, wherein the PPDU includes a resource allocation field and a binding field, the resource allocation field and the binding field indicating the allocation status of the station's frequency resources, and a processing module configured to determine the allocated frequency resources based on the resource instruction information.

[0074] Referring to the tenth aspect, in some implementations of the tenth aspect, the transceiver module is further configured to transmit information to an access point on an allocated frequency resource, or to receive data from an access point on an allocated frequency resource.

[0075] For example, the transceiver module receives data from the access point via a 640 MHz bandwidth RU or MRU, or the transceiver module receives data from the access point via a 480 MHz bandwidth RU or MRU.

[0076] For the technical effects of the apparatus shown in the tenth aspect, please refer to the technical effects of the fifth aspect and the possible designs of the fifth aspect.

[0077] For MRU modes designed for 640 MHz or 480 MHz bandwidths in the second through tenth embodiments, please refer to the description of MRU modes designed for 640 MHz or 480 MHz bandwidths in the first embodiment. Further details are not provided here.

[0078] According to the eleventh aspect, a communication system including an access point and a station is provided. The access point is configured to perform the method described in the first aspect, or the station performs the method described in the first aspect, or the access point is configured to perform the method described in the second aspect and the station performs the method described in the third aspect, or the access point is configured to perform the method described in the fourth aspect and the station performs the method described in the fifth aspect.

[0079] According to a twelfth aspect, a communication device is provided. The device includes a memory configured to store a program and a processor configured to execute the program stored in the memory. When the program stored in the memory is executed, the processor is configured to perform the method provided in the above aspects.

[0080] According to a thirteenth aspect, the present application provides a processor configured to perform the methods provided in the above aspects. In the process of performing these methods, the process of transmitting the above-described information and the process of acquiring / receiving the above-described information in the above-described methods can be understood as the process of outputting the above-described information by the processor and the process of receiving the above-described input information by the processor. When outputting information, the processor outputs the information to the transceiver so that the transceiver transmits the information. After the information is output by the processor, further processing may need to be performed on the information before the information arrives at the transceiver. Similarly, when the processor receives input information, the transceiver acquires / receives the information and inputs the information to the processor. Furthermore, after the transceiver receives the information, further processing may need to be performed on the information before the information is input to the processor.

[0081] According to the above principle, for example, receiving a request message as described in the above method can be understood as receiving input information by the processor.

[0082] Unless otherwise specified, or unless the operations related to the processor, such as transmission, transmit, and acquire / receive, are consistent with the actual function or internal logic of the operations in the relevant description, all operations may be more generally understood as the operations of the processor, such as output, receive, and input, rather than the transmission, transmit, and receive operations performed directly by the radio frequency circuitry and antenna.

[0083] In the implementation process, the processor may be a processor specifically configured to perform these methods, or a processor that executes computer instructions in memory to perform these methods, such as a general-purpose processor. The memory may be non-transitory memory, such as read-only memory (ROM). The memory and processor may be integrated on the same chip or located separately on different chips. The type of memory, as well as the arrangement of the memory and processor, is not limited to the embodiments of this application.

[0084] According to a fourteenth aspect, a computer-readable storage medium is provided. The computer-readable medium stores program code to be executed by a device, and the program code includes a method provided in the above-described aspect.

[0085] According to the 15th aspect, a computer program product including instructions is provided. When the computer program product is executed on a computer, the computer becomes capable of performing the method provided in the above aspects.

[0086] According to the sixteenth aspect, a chip is provided. The chip includes a processor and a communication interface, the processor reading instructions stored in memory via the communication interface in order to perform the method provided in the above aspects.

[0087] Optionally, in one implementation configuration, the chip may further include memory. The memory stores instructions. The processor is configured to execute instructions stored in memory. When an instruction is executed, the processor is configured to perform the method provided in the above-described embodiment. [Brief explanation of the drawing]

[0088] [Figure 1] This is a diagram illustrating an application scenario to which one embodiment of this application may be applied. [Figure 2] This application shows a communication device. [Figure 3] This is a diagram of the corresponding MRU patterns within an 80 MHz bandwidth. [Figure 4] This is a diagram showing the division of the 6 GHz frequency band. [Figure 5] This is a diagram showing the PPDU format. [Figure 6] This is a diagram of frequency resource allocation instructions. [Figure 7] This figure shows the change in MRU when the bandwidth is doubled from 160 MHz to 320 MHz, according to one embodiment of this application. [Figure 8A] This is another figure showing the change in MRU when the bandwidth is doubled from 160 MHz to 320 MHz, according to one embodiment of the present application. [Figure 8B] This is another figure showing the change in MRU when the bandwidth is doubled from 160 MHz to 320 MHz, according to one embodiment of the present application. [Figure 8C] This is another figure showing the change in MRU when the bandwidth is doubled from 160 MHz to 320 MHz, according to one embodiment of the present application. [Figure 9] This is a schematic flowchart of a communication method according to one embodiment of this application. [Figure 10(a)] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 10(b)] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 10(c)] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 10(d)] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 10(e)] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 10(f)] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 10(g)-1] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 10(g)-2] This is a diagram of multiple MRUs with a bandwidth of 640 MHz according to one embodiment of the present application. [Figure 11(a)] This figure shows the change in MRU when the bandwidth is doubled from 320 MHz to 640 MHz, according to one embodiment of this application. [Figure 11(b)] This figure shows the change in MRU when the bandwidth is doubled from 320 MHz to 640 MHz, according to one embodiment of this application. [Figure 11(c)-1] This figure shows the change in MRU when the bandwidth is doubled from 320 MHz to 640 MHz, according to one embodiment of this application. [Figure 11(c)-2] This figure shows the change in MRU when the bandwidth is doubled from 320 MHz to 640 MHz, according to one embodiment of this application. [Figure 12(a)] This figure shows a partial reuse of a 640 MHz bandwidth MRU for a 480 MHz MRU according to one embodiment of this application. [Figure 12(b)] This figure shows a partial reuse of a 640 MHz bandwidth MRU for a 480 MHz MRU according to one embodiment of this application. [Figure 12(c)-1] This figure shows a partial reuse of a 640 MHz bandwidth MRU for a 480 MHz MRU according to one embodiment of this application. [Figure 12(c)-2]This figure shows a partial reuse of a 640 MHz bandwidth MRU for a 480 MHz MRU according to one embodiment of this application. [Figure 13] This figure shows an embodiment of the present application in which an MRU corresponding to a 480 MHz bandwidth cannot reuse a portion of the 640 MHz MRU. [Figure 14(a)] This is a diagram of an MRU mode designed for a 480 MHz bandwidth according to one embodiment of the present application. [Figure 14(b)] This is a diagram of an MRU mode designed for a 480 MHz bandwidth according to one embodiment of the present application. [Figure 14(c)] This is a diagram of an MRU mode designed for a 480 MHz bandwidth according to one embodiment of the present application. [Figure 14(d)] This is a diagram of an MRU mode designed for a 480 MHz bandwidth according to one embodiment of the present application. [Figure 15] This is a diagram illustrating the decision logic for determining the MRU mode according to one embodiment of this application. [Figure 16] This is a schematic flowchart of another communication method according to one embodiment of this application. [Figure 17] This is a block diagram of a communication device according to one embodiment of this application. [Figure 18] This is a diagram of another communication device according to one embodiment of this application. [Figure 19] This is a diagram of a chip system according to one embodiment of the present application. [Modes for carrying out the invention]

[0089] The technical solution of this application will be described below with reference to the attached drawings.

[0090] The technical solutions provided in embodiments of this application support wireless local area network (WLAN) scenarios, such as 802.11a / b / g standards, 802.11n standards, 802.11ac standards, 802.11ax standards, and next-generation Wi-Fi protocols such as IEEE 802.11be, Wi-Fi 7, extremely high throughput (EHT), 802.11ad, 802.11ay, or 802.11bf, or in another example, next-generation 802.11be such as Wi-Fi 8, and related technologies from the Institute of Electrical and Electronics Engineers (IEEJ). The 802.11n standard is applicable to the IEEE 802.11 standard, and may be further applied to ultra-wideband (UWB) based wireless personal area network systems, such as the 802.15 series standards, and to sensing systems, such as the 802.11bf series standards. The 802.11n standard is referred to as high throughput (HT), the 802.11ac standard as very high throughput (VHT), the 802.11ax standard as high efficiency (HE), and the 802.11be standard as extremely high throughput (EHT). The 802.11bf standard includes two main categories of standards: low frequency (e.g., sub-7 GHz) standards and high frequency (e.g., 60 GHz) standards. Sub-7 GHz implementations primarily depend on 802.11ac, 802.11ax, 802.11be, and next-generation standards. 60 GHz implementations primarily depend on 802.11ad, 802.11ay, and next-generation standards.802.11ad is sometimes referred to as the directional multi-gigabit (DMG) standard, and 802.11ay is sometimes referred to as the enhanced directional multi-gigabit (EDMG) standard.

[0091] While embodiments of this application are primarily described using examples in which WLAN networks, particularly networks to which the IEEE 802.11 system standard applies, those skilled in the art will readily understand that various aspects of the embodiments of this application can be extended to other networks using various standards or protocols, such as high-performance radio local area networks (HIPERLAN), wireless wide area networks (WWAN), wireless personal area networks (WPAN), or other known or future-developed networks. Accordingly, regardless of the coverage area used and the wireless access protocol used, various aspects provided in the embodiments of this application are applicable to any suitable wireless network.

[0092] The technical solutions in the embodiments of this application may be further applied to various communication systems, such as WLAN communication systems, wireless fidelity (Wi-Fi) systems, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR), future 6th generation (6G) systems, Internet of Things (IoT) networks, or vehicle-to-everything (V2X).

[0093] The communication systems applicable to this application are merely illustrative examples and are not limited to those applicable to this application. This is described only once in this specification and no further details are described below.

[0094] Figure 1 is a diagram illustrating an application scenario to which one embodiment of the present application can be applied. As shown in Figure 1, the communication method provided in the present application is applicable to data communication between an access point (AP) and a station (STA). The station may be a non-access point station (non-AP STA), and is abbreviated as a non-AP station or STA. Specifically, the solution of the present application is applicable to data communication between an AP and one or more non-AP stations (e.g., data communication between AP1 and non-AP STA1 and non-AP STA2), and is also applicable to data communication between APs (e.g., data communication between AP1 and AP2) and data communication between non-AP STAs (e.g., data communication between non-AP STA2 and non-AP STA3).

[0095] An access point may be a node for a device (e.g., a mobile phone) to access a wired (or wireless) network, and is primarily located in homes, buildings, or campuses, with a typical coverage radius ranging from tens of meters to over 100 meters, and can of course be located outdoors. An access point acts as a bridge connecting wired and wireless networks. Access points are primarily used to connect various wireless network clients together and then connect the wireless network to Ethernet.

[0096] Specifically, an access point may be a terminal or network device having a Wi-Fi chip. Network devices may include servers, routers, switches, bridges, computers, mobile phones, relay stations, in-vehicle devices, wearable devices, network devices in 5G networks, network devices in 6G networks, and network devices in public land mobile networks (PLMNs), etc. This is not limited to the embodiments of this application. An access point may also be a device that supports Wi-Fi standards. For example, an access point may alternatively support one or more of the following IEEE 802.11 series standards, namely 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, and 802.11ay.

[0097] Non-AP stations may include wireless communication chips, wireless sensors, wireless communication terminals, etc., and may also be referred to as users, user equipment (UE), access terminals, subscriber units, subscriber stations, mobile stations, mobile consoles, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication devices, user agents, or user equipment. Non-AP stations may also include mobile phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, Internet of Things devices, wearable devices, terminal devices in 5G networks, terminal devices in 6G networks, terminal devices in PLMNs, etc. This is not limited to the embodiments of this application. Non-AP stations may be devices that support WLAN standards. For example, a non-AP station can support one or more of the following IEEE 802.11 series standards: 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, and 802.11ay.

[0098] For example, non-AP stations may be mobile phones, tablet computers, set-top boxes, smart TVs, smart wearable devices, in-car communication devices, computers, Internet of Things (IoT) nodes, sensors, smart cameras, smart remotes, or smart home devices such as smart water / electricity meters, or sensors within a smart city.

[0099] An AP or non-AP station may include a transmitter, receiver, memory, processor, etc. The transmitter and receiver are configured to transmit and receive packet structures, respectively. The memory is configured to store signaling information and pre-agreed preset values, etc. The processor is configured to parse the signaling information and process related data, etc.

[0100] For example, Figure 2 shows a communication device according to this application. The device shown in Figure 2 may be an AP or a non-AP station. A medium access control (MAC) layer processing module, a physical (PHY) layer processing module, a radio frequency / antenna, etc., are configured to implement the relevant functions of the transmitter and receiver described above. As shown in Figure 2, in addition to the MAC layer processing module, PHY layer processing module, radio frequency / antenna, memory, and processor, the device may further include a controller and a scheduler.

[0101] Figure 2 merely illustrates an example of the apparatus provided in this application and should not constitute a limitation of this application. For example, the apparatus may, alternatively, not include a controller and / or scheduler.

[0102] To facilitate understanding of the technical solutions in the embodiments of this application, some terms or concepts that may be used in the embodiments of this application will first be briefly explained.

[0103] 1. Resource Unit (RU): The introduction of OFDMA technology into the 802.11ax standard allows a single bandwidth to be divided into multiple RUs, which may be 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, 996-tone RUs, 2 x 996-tone RUs, etc. Each RU can be assigned to a single user to implement a more flexible frequency resource scheduling and to implement a more improved division of spectral resources.

[0104] The standard includes two types of RUs: large RUs and small RUs. RUs with a bandwidth of 242-tone RU (20 MHz) or more are called large RUs, while RUs smaller than 242-tone RU are called small RUs.

[0105] 2. Multiple Resource Units (MRUs): The 802.11be standard defines a new frequency resource unit, or MRU. To implement more flexible frequency resource allocation, multiple RUs are permitted to be assigned to the same user. MRUs formed by combining large RUs are called large MRUs, and MRUs formed by combining small RUs are called small MRUs.

[0106] Existing standards include two types of small MRUs: 52+26-tone MRUs and 106+26-tone MRUs. Existing standards also include large MRU types such as 484+242-tone MRUs, 996+484-tone MRUs, 996+484+242-tone MRUs, 2×996+484-tone MRUs, 3×996-tone MRUs, and 3×996+484-tone MRUs.

[0107] The standard defines corresponding MRU patterns for different bandwidths, such as 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz.

[0108] For example, the 484+242-tone MRU pattern within an 80 MHz bandwidth in the 802.11be standard is shown in Figure 3, and the 484+242-tone MRU pattern includes a total of four MRU patterns, namely 484+242-tone MRU 1, 484+242-tone MRU 2, 484+242-tone MRU 3, and 484+242-tone MRU 4 shown in Figure 3.

[0109] 3. Possible Future Bandwidth: In future WLAN standards, if larger bandwidths emerge, they are likely to reside in the 6 GHz frequency band. This is because 6 GHz is a new spectrum and has a wider bandwidth compared to the 2.4 GHz and 5 GHz frequency bands. As shown in Figure 4, the 6 GHz frequency band has four frequency bands: UNII-5, 6, 7, and 8. However, many countries and regions, such as the European Union and Hong Kong (China), only have a 500 MHz bandwidth in UNII-5. The wider bandwidths that may emerge in future standards are not limited to two cases, namely 480 MHz and 640 MHz. Currently, the maximum bandwidth in existing standards is 320 MHz, and new bandwidths typically emerge in the form of doubling (e.g., 2 × 320 MHz = 640 MHz) or adding half (e.g., 320 MHz + 160 MHz = 480 MHz). Therefore, the future possible bandwidth configurations defined in this application include, but are not limited to, two bandwidths of 480 MHz and 640 MHz. For ease of explanation, in the following embodiments, the two bandwidths of 480 MHz and 640 MHz are primarily used as illustrative examples.

[0110] 4. Physical Layer Protocol Data Unit (PPDU): Figure 5 shows the PPDU format. A PPDU includes the Legacy Short Training Field (L-STF), Legacy Long Training Field (L-LTF), Legacy Signal Field (L-SIG), Repeat Legacy-Signal Field (RL-SIG), Universal SIG (U-SIG), Extremely High Throughput (EHT-SIG), EHT-Short Training Field (EHT-STF), EHT-Long Training Field (EHT-LTF), Data field, and Package Extension (PE) field. L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-SIG, EHT-STF, and EHT-LTF are parts of the structure within the physical layer header (or preamble portion) of the PPDU.

[0111] L-STF, L-LTF, and L-SIG may be understood as legacy preamble fields and are used to ensure the coexistence of new and legacy devices. RL-SIG is used to enhance the reliability of legacy signal fields.

[0112] U-SIG and EHT-SIG are signal fields. U-SIG is used to carry some common information, such as information indicating the PPDU version, uplink / downlink information, information indicating the frequency domain bandwidth of the PPDU, and puncturing indication information. EHT-SIG includes information indicating resource allocation, information indicating data demodulation, etc.

[0113] It should be noted that in this embodiment of the present application, fields within a PPDU in an 802.11be scenario are used as illustrative examples. The fields within a PPDU referred to in this embodiment of the present application are not limited to fields related to 802.11be. Alternatively, the fields of a PPDU referred to in this embodiment of the present application may be fields related to 802.11be or later standard versions, including but not limited to cases where the PPDU signaling fields of the next-generation protocol are ultra-high reliability signaling (UHR-SIG).

[0114] For example, the channel bandwidth for transmitting PPDU is 20 MHz. In this case, the 20 MHz bandwidth can be formed by a total resource unit (242-tone RU) containing 242 tones, or by various combinations of resource units containing 26 tones (26-tone RU), 52 tones (52-tone RU), and 106 tones (106-tone RU). In addition to the RUs used to transmit data, several guard subcarriers, null subcarriers, or DC subcarriers may be included.

[0115] For example, the channel bandwidth for transmitting PPDU is 40 MHz. In this case, the total bandwidth is approximately equal to a replica of a 20 MHz subcarrier distribution. The total 40 MHz bandwidth may be formed by a total resource unit (484-tone RU) containing 484 tones, or by various combinations of 26-tone RUs, 52-tone RUs, 106-tone RUs, and 242-tone RUs.

[0116] For example, the channel bandwidth for transmitting PPDU is 80 MHz. In this case, the entire channel bandwidth is approximately equal to two duplicates of 40 MHz subcarrier distributions. The entire 40 MHz bandwidth may be formed by a whole resource unit (996-tone RU) containing 996 tones, or by various combinations of 26-tone RUs, 52-tone RUs, 106-tone RUs, and 242-tone RUs.

[0117] For example, the channel bandwidth for transmitting PPDU is 160 MHz. In this case, the entire bandwidth can be considered as a duplicate of two 80 MHz subcarrier distributions. The entire bandwidth may be formed by 2 × 996-tone RUs, or by various combinations of 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, and 996-tone RUs.

[0118] 5. RU Allocation: The AP may add resource allocation information to the signal field (SIG) included in the PPDU to indicate the allocated RUs to the STA. For example, the signal field may be a High Efficient Signal Field-B (HE-SIG-B) or an Extremely High Throughput Signal Field (EHT-SIG). In 802.11ax, the AP notifies the user of RU allocation by using the signal field. As shown in Figure 6, the HE-SIG includes a common field and a user-specific field, which together indicate frequency resource allocation.

[0119] Common fields include 1 to N resource unit allocation subfields (RU Allocation subfields), a cyclic redundancy code (CRC) used for checking, and a Tail subfield used for the cyclic redundancy code. User-specific fields include user fields corresponding to the RUs indicated by the resource unit allocation subfields.

[0120] Each resource unit allocation subfield is a resource unit allocation index, and each resource unit allocation index indicates the size and location of one or more resource units corresponding to one 242-tone RU. It should be understood that each resource unit allocation subfield corresponds to one 242-tone RU, and one 20 MHz corresponds to one 242-tone RU. In this case, it can also be understood that each resource unit allocation subfield corresponds to one 20 MHz. A resource unit allocation index is indicated by one or more indices, each index corresponding to one 20 MHz of bandwidth.

[0121] The user-specific fields of the signal field (HE-SIG) contain 1 to M user fields based on the resource unit allocation sequence. Two of the M user fields are typically in a group, followed by a CRC and a tail field for every two user fields. If the number of user fields is odd, the last user field is in a separate group, followed by a CRC and a tail field. For RUs containing fewer than 106 tones, a particular field portion contains the user fields corresponding to the RU. For RUs containing 106 or more tones, a particular field portion contains one or more user fields corresponding to the RU.

[0122] 6. MRU Design Rules: The MRU design rules indicated by PPDU when bandwidth is doubled are: (1) Compared to the MRU before doubling, the MRU after doubling the bandwidth includes the doubled MRU, (2) The minimum puncturing size after the bandwidth has been doubled is greater than or equal to the minimum puncturing size before the doubling. (3) Only one hole is allowed between the data subcarriers of the MRU. (4) When the MRU has multiple holes, the larger holes are located outside the data subcarriers, and the smaller holes are located between the data subcarriers.

[0123] To facilitate understanding the MRU design rules used when bandwidth is doubled, the following briefly describes the MRU changes when bandwidth is doubled from 160 MHz to 320 MHz, referring to Figures 7 and 8A-8C.

[0124] Figure 7 shows that when the bandwidth is doubled from 160 MHz to 320 MHz, the MRU mode corresponding to 160 MHz, which has a puncturing size of 484, is doubled in order to acquire the MRU mode corresponding to 320 MHz, and the puncturing size is doubled accordingly.

[0125] Figures 8A to 8C show that when the bandwidth is doubled from 160 MHz to 320 MHz, the MRU mode corresponding to 160 MHz, which has a puncturing size of 242, is doubled in order to acquire the MRU mode corresponding to 320 MHz, and the puncturing size is doubled accordingly.

[0126] As shown in Figures 7 and 8A-8C, the above-described MRU design rules can be obtained. For example, when the bandwidth is doubled from 160 MHz to 320 MHz, there is a doubled MRU (e.g., 242 is doubled to 484, 484 is doubled to 996, and 996 is doubled to 2 × 996). In another example, when the bandwidth is doubled from 160 MHz to 320 MHz, the puncturing size corresponding to 320 MHz may be 484 or 996, and is greater than or equal to the puncturing size corresponding to 160 MHz, which is 242 or 484. In yet another example, if 320 MHz corresponds to a double hole (e.g., a puncturing of 996 + 484), the 996 hole is located outside the data subcarrier and the 484 hole is located between the data subcarriers.

[0127] In addition, the following description is provided first to facilitate understanding of the embodiments of this application.

[0128] Firstly, in this application, "to indicate" may include "to indicate directly" and "to indicate indirectly." If one instruction indicates A, the instruction may indicate A directly or indirectly, but it does not necessarily indicate that the instruction will reliably transport A.

[0129] The information indicated by the referential information is called the referred information. In a specific implementation process, there are several ways of indicating the referred information, including, but not limited to, the following: The referred information may be indicated directly. For example, the referred information or an index of the referred information may be indicated. Alternatively, the referred information may be indicated indirectly by indicating other information, and there is a correlation between the other information and the referred information. Alternatively, only a part of the referred information may be indicated, and the other part of the referred information may be known or pre-agreed. For example, certain information may, alternatively, be indicated by using a pre-agreed (e.g., specified in a protocol) arrangement sequence of multiple pieces of information to reduce the referential overhead to some extent. Furthermore, the common parts of all information may be identified and indicated in a unified manner to reduce the referential overhead caused by indicating the same information separately.

[0130] Secondly, “at least one” as used in this application means one or more, and “multiple” means two or more. In addition, in the embodiments of this application, “first,” “second,” and various numbers (e.g., “#1” and “#2”) are used merely for distinction to facilitate explanation and are not used to limit the scope of the embodiments of this application. Furthermore, sequence numbers in the following processes do not imply execution order. The execution order of a process should be determined based on the function and internal logic of the process and should not constitute any limitation on the implementation process of the embodiments of this application. It should be understood that the objects described herein may be interchangeable where appropriate so that solutions other than the embodiments of this application may be described. In addition, in the embodiments of this application, words such as “S510” are merely identifiers for ease of explanation and do not limit the order in which the steps are performed.

[0131] Thirdly, in the embodiments of this application, words such as “example” or “for example” are used to give examples, illustrations, or explanations. Any embodiment or design solution described as “example” or “for example” in this application should not be construed as being preferable or having more advantages than another embodiment or design solution. More precisely, the use of words such as “example” or “for example” is intended to present relative concepts in a particular manner.

[0132] Fourth, in embodiments of this application, “storage” may mean “storage in one or more memories.” These one or more memories may be located separately or integrated into an encoder, decoder, processor, or communication device. Alternatively, some of the one or more memories may be located separately, while others are integrated into a decoder, processor, or communication device. The type of memory may be any form of storage medium; this is not limited to this application.

[0133] Fifth, in embodiments of this application, “protocol” may be a standard protocol in the field of communications, and may include, for example, the NR protocol and related protocols applied to further communications systems. This is not limited to this application.

[0134] Sixth, in the embodiments of this application, “of,” “corresponding / relevant,” “corresponding,” and “associate” may sometimes be used interchangeably. Note that unless the differences between the terms are emphasized, the expressed meanings are consistent.

[0135] Seventh, in the embodiments of this application, “case,” “when,” and “situation” may be used interchangeably in some cases. Note that when the differences between the three are not emphasized, the meaning expressed is consistent.

[0136] Eighth, the term “and / or” as used herein is merely an association to describe the related objects, and three such relationships may exist. For example, A and / or B can refer to three cases: that only A exists, that both A and B exist, and that only B exists. Furthermore, the letter “ / ” as used herein generally indicates an “or” relationship between related objects.

[0137] Referring to Figure 1, the above briefly describes scenarios to which the communication method provided in embodiments of this application may be applied, explains the basic concepts that may be used in embodiments of this application, and describes the MRU in the basic concepts. While MRU design is completed for all existing broadbands within the standard, new broadbands (e.g., 480 MHz and 640 MHz mentioned above) may appear in future standards, and MRU patterns within these broadbands will need to be newly designed. In addition, since the new bandwidths are obviously larger than 20 MHz, the new MRUs are generally larger in size.

[0138] Specifically, for non-OFDMA 320 MHz PPDUs, three large MRUs are defined in the 802.11be standard: 2×996+484-tone MRU, 3×996-tone MRU, and 3×996+484-tone MRU. In addition, for OFDMA 320 MHz PPDUs, the large MRUs that may be used include 484+242-tone MRU, 996+484-tone MRU, 2×996+484-tone MRU, 3×996-tone MRU, and 3×996+484-tone MRU.

[0139] The large MRU defined in current standards does not cover MRU forms that may exist when the bandwidth is greater than 320 MHz, such as MRU patterns in next-generation WLAN ultra-high bandwidth (e.g., 640 MHz or 480 MHz).

[0140] This application provides a communication method for designing MRU patterns for broadband that may emerge in future Wi-Fi standards in order to meet OFDMA transmission requirements in future broadband scenarios.

[0141] The technical solutions provided in this application will be described in detail below with reference to the attached drawings. Embodiments of this application may be applied to several different scenarios, including but not limited to the scenario shown in Figure 1.

[0142] It should be understood that the specific structure of an entity for performing the method provided in the embodiments of this application is not particularly limited in the following embodiments, as long as the entity can execute a program that records the code of the method provided in the embodiments of this application in order to perform communication in accordance with the method provided in the embodiments of this application. For example, an entity for performing the method provided in the embodiments of this application may be a receiving end device or a transmitting end device, or a functional module located within a receiving end device or a transmitting end device that can call and execute a program.

[0143] Without loss of generality, the communication method provided in the embodiments of this application will be described in detail below, using the interaction between a transmitting end device and a receiving end device as an example. In the embodiments of this application, the transmitting end device may be an access point AP, and the receiving end device may be a non-access point non-AP (e.g., STA). Alternatively, the transmitting end device may be an access point STA, and the receiving end device may be a non-access point AP.

[0144] Figure 9 is a schematic flowchart of a communication method according to one embodiment of this application. It includes the following steps:

[0145] S910: The first device determines the frequency resources.

[0146] Specifically, the frequency resource includes MRU, and the MRU in this application includes k × 996 + m × 484 - tone MRU, where k is an integer greater than or equal to 4, and m is equal to 0 or 1.

[0147] S920: The first device communicates with the second device based on frequency resources.

[0148] In a possible implementation, the first device is an AP (Application Platform) and the second device is an STA (Stationary Device). In this implementation, the AP can transmit downlink information (e.g., downlink data) to the STA based on frequency resources.

[0149] In another possible implementation, the first device is an STA (Stationary Device) and the second device is an AP (Audio Platform). In this implementation, the STA can transmit uplink information (e.g., uplink data) to the AP based on frequency resources.

[0150] Note that in this embodiment, for ease of explanation, the two communication parties will be referred to as AP and STA. However, understand that the names of communication devices are not limited to this embodiment, as long as the corresponding functions can be implemented. For example, AP can be replaced with access point, base station, terminal device, etc., and STA can be replaced with non-AP station, non-AP STA, user, terminal device, etc. Examples are again not described herein.

[0151] For example, this embodiment primarily relates to MRU configurations that may exist when the bandwidth is greater than 320 MHz, such as MRU patterns in next-generation WLAN ultra-high bandwidth (e.g., 640 MHz or 480 MHz). The following describes MRU patterns in different bandwidths with reference to specific examples, details of which are not described here.

[0152] As described above, in this embodiment, the new MRU mode is defined when the possible future bandwidths (e.g., 480 MHz and 640 MHz) are primarily considered. Below, a detailed explanation is provided using the 480 MHz and 640 MHz bandwidths.

[0153] Method 1: The bandwidth for transmitting PPDU is 640 MHz.

[0154] In the case shown in Method 1, the total bandwidth for transmitting PPDU is 640 MHz. With a 640 MHz bandwidth, in addition to the compatible MRU modes defined for a 320 MHz bandwidth (such as 484+242-tone MRU, 996+484-tone MRU, 2×996+484-tone MRU, 3×996-tone MRU, and 3×996+484-tone MRU), several new MRU modes are introduced in the following manner.

[0155] Method 1.1: When one 80 MHz subchannel is punctured with non-OFDMA 640 MHz (or when one 996-tone RU is punctured with non-OFDMA 640 MHz), the 640 MHz bandwidth after puncture may include 7 × 996-tone MRUs. The non-OFDMA 640 MHz may be understood to include 8 × 996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 640 MHz corresponds to 8 × 996-tone MRUs). When one 80 MHz subchannel is punctured with non-OFDMA 640 MHz, the 640 MHz bandwidth after puncture may include (8-1) × 996-tone MRUs, i.e., 7 × 996-tone MRUs.

[0156] Specifically, OFDMA transmission can be implemented if the punctured 640 MHz is allocated to one user, and the punctured 80 MHz subchannel is allocated to another user.

[0157] For example, 7 × 996-tone MRU may be considered a combination of one 4 × 996-tone RU, one 2 × 996-tone RU, and one 996-tone RU.

[0158] Alternatively, 7 x 996-tone MRU may be considered a combination of three 2 x 996-tone RUs and one 996-tone RU.

[0159] Alternatively, 7 x 996-tone MRU may be considered as a combination of 7 996-tone RUs.

[0160] Alternatively, a 7x996-tone MRU may be considered a combination of two 2x996-tone RUs and three 996-tone RUs.

[0161] It should be understood that the method of obtaining 7×996-tone MRU is not limited by embodiment. The various combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0162] It should be further understood that the data subcarriers of a 7×996-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 7×996-tone MRU, and the pilot subcarriers of a 7×996-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 7×996-tone MRU. For example, if a 7×996-tone MRU is a combination of one 4×996-tone RU, one 2×996-tone RU, and one 996-tone RU, then the data subcarriers of the 7×996-tone MRU are formed by a combination of data subcarriers of the 4×996-tone RU, 2×996-tone RU, and 996-tone RU. The pilot subcarriers of a 7×996-tone MRU include the pilot subcarriers of the 4×996-tone RU, 2×996-tone RU, and 996-tone RU.

[0163] For ease of understanding, possible forms of the 7×996-tone MRU will be described in detail below with reference to Figure 10(a). Figures 10(a) to 10(g)-2 show several MRUs with a bandwidth of 640 MHz according to one embodiment of this application.

[0164] From Figure 10(a), it can be seen that the 7×996-tone MRU pattern includes a total of eight MRU patterns, as shown in Figure 10(a): 7×996-tone MRU 1, 7×996-tone MRU 2, 7×996-tone MRU 3, 7×996-tone MRU 4, 7×996-tone MRU 5, 7×996-tone MRU 6, 7×996-tone MRU 7, and 7×996-tone MRU 8.

[0165] Method 1.2: If one 160 MHz subchannel is punctured with non-OFDMA 640 MHz (or if one 2×996-tone RU is punctured with non-OFDMA 640 MHz), the 640 MHz bandwidth after puncture may include 6×996-tone MRUs. The non-OFDMA 640 MHz may be understood to include 8×996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 640 MHz corresponds to 8×996-tone MRUs). If one 160 MHz subchannel is punctured with non-OFDMA 640 MHz, the 640 MHz bandwidth after puncture may include (8-2)×996-tone MRUs, i.e., 6×996-tone MRUs.

[0166] Specifically, OFDMA transmission can be implemented if the punctured 640 MHz is allocated to one user, and the punctured 160 MHz subchannel is allocated to another user.

[0167] For example, a 6×996-tone MRU can be considered a combination of one 4×996-tone RU and one 2×996-tone RU.

[0168] Alternatively, a 6×996-tone MRU may be considered a combination of three 2×996-tone RUs.

[0169] Alternatively, 6 x 996-tone MRU may be considered as a combination of six 996-tone RUs.

[0170] Alternatively, a 6×996-tone MRU may be considered a combination of two 2×996-tone RUs and two 996-tone RUs.

[0171] It should be understood that the method for obtaining 6 × 996-tone MRU is not limited to the embodiments. The multiple combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0172] It should be further understood that the data subcarriers of a 6×996-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 6×996-tone MRU, and the pilot subcarriers of a 6×996-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 6×996-tone MRU. For example, if a 6×996-tone MRU is a combination of two 2×996-tone RUs and two 996-tone RUs, then the data subcarriers of the 6×996-tone MRU are formed by a combination of data subcarriers of the two 2×996-tone RUs and two 996-tone RUs. The pilot subcarriers of a 6×996-tone MRU include the pilot subcarriers of two 2×996-tone RUUs and two 996-tone RUs.

[0173] To facilitate understanding, the possible forms of 6×996-tone MRU will be described in detail below with reference to Figure 10(b).

[0174] From Figure 10(b), it can be seen that the 6×996-tone MRU pattern includes a total of four MRU patterns, namely 6×996-tone MRU 1, 6×996-tone MRU 2, 6×996-tone MRU 3, and 6×996-tone MRU 4, as shown in Figure 10(b).

[0175] Scheme 1.3: If one 2×996-tone RU 1 or 2×996-tone RU 4 is punctured within the non-OFDMA 640 MHz (or one 160 MHz subchannel #1 or 160 MHz subchannel #4 is punctured within the non-OFDMA 640 MHz), and an 80 MHz subchannel is punctured within the remaining 480 MHz, then the punctured 640 MHz bandwidth may contain 5×996-tone MRUs, where 2×996-tone RU x indicates the x-th 2×996-tone RU. Different RUs do not have overlapping subcarriers. It can be understood that the non-OFDMA 640 MHz contains 8×996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 640 MHz corresponds to 8×996-tone MRUs). If the first or last 2 × 996-tone RU of a non-OFDMA 640 MHz signal is punctured, and one 80 MHz subchannel is punctured, the 640 MHz bandwidth after puncture may include (8-3) × 996-tone MRU, i.e., 5 × 996-tone MRU.

[0176] Specifically, OFDMA transmission can be implemented if the punctured 640 MHz is allocated to one user, and the punctured 240 MHz subchannel is allocated to another user.

[0177] In the case shown in Scheme 1.2, two holes are punctured in non-OFDMA 640 MHz, one hole being a 160 MHz subchannel (or 2×996-tone RU) and the other hole being an 80 MHz subchannel (or 996-tone RU). The hole in the 2×996-tone RU is larger than the hole in the 996-tone RU. From the MRU design rules explained in the basic concepts above, we can see that "if an MRU has multiple holes, the larger hole is located outside the data subcarriers, and the smaller hole is located between the data subcarriers." Therefore, in the case shown in Scheme 1.2, the hole in the 2×996-tone RU is located outside the data subcarriers. In other words, the RU is either the first 2×996-tone RU (e.g., 2×996-tone RU 1 above) or the last 2×996-tone RU (e.g., 2×996-tone RU 4 above). The hole in the 996-tone RU is located between the data subcarriers.

[0178] For example, a 5×996-tone MRU can be considered a combination of one 4×996-tone RU and one 996-tone RU.

[0179] Alternatively, a 5×996-tone MRU may be considered a combination of two 2×996-tone RUs and one 996-tone RU.

[0180] Alternatively, 5 × 996-tone MRU may be considered as a combination of five 996-tone RUs.

[0181] It should be understood that the method of obtaining 5 × 996-tone MRU is not limited to the embodiments. The various combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0182] It should be further understood that the data subcarriers of a 5×996-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 5×996-tone MRU, and the pilot subcarriers of a 5×996-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 5×996-tone MRU. For example, if a 5×996-tone MRU is a combination of two 2×996-tone RUs and one 996-tone RU, then the data subcarriers of the 5×996-tone MRU are formed by a combination of data subcarriers of the two 2×996-tone RUs and the 996-tone RU. The pilot subcarriers of a 5×996-tone MRU include the pilot subcarriers of the two 2×996-tone RUs and the 996-tone RU.

[0183] To facilitate understanding, the possible forms of 5×996-tone MRU will be described in detail below with reference to Figure 10(c).

[0184] From Figure 10(c), it can be seen that the 5×996-tone MRU pattern includes a total of 12 MRU patterns, namely 5×996-tone MRU 1, 5×996-tone MRU 2, 5×996-tone MRU 3, 5×996-tone MRU 4, 5×996-tone MRU 5, 5×996-tone MRU 6, 5×996-tone MRU 7, 5×996-tone MRU 8, 5×996-tone MRU 9, 5×996-tone MRU 10, 5×996-tone MRU 11, and 5×996-tone MRU 12, as shown in Figure 10(c).

[0185] Method 1.4: When one 40 MHz subchannel is punctured with non-OFDMA 640 MHz (or when one 484-tone RU is punctured with non-OFDMA 640 MHz), the punctured 640 MHz bandwidth may contain 7 × 996 + 484-tone MRUs. Compared to Method 1.1, in the case shown in Method 1.4, the puncturing granularity is 484-tone RUs instead of 996-tone RUs, and the puncturing granularity is smaller than that of Method 1.1. This is equivalent to a more improved MRU design solution. It can be understood that the non-OFDMA 640 MHz contains 8 × 996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 640 MHz corresponds to 8 × 996-tone MRUs). If one 40 MHz subchannel is punctured with non-OFDMA 640 MHz, the 640 MHz bandwidth after puncturing may contain (8-1) × 996 + 484-tone MRU, i.e., 7 × 996 + 484-tone MRU.

[0186] Specifically, OFDMA transmission can be implemented if the punctured 640 MHz is allocated to one user, and the punctured 40 MHz subchannel is allocated to another user.

[0187] For example, 7 × 996 + 484-tone MRU can be considered a combination of one 4 × 996-tone RU, one 2 × 996-tone RU, one 996-tone RU, and one 484-tone RU.

[0188] Alternatively, 7 × 996 + 484-tone MRU may be considered a combination of three 2 × 996-tone RUs, one 996-tone RU, and one 484-tone RU.

[0189] Alternatively, 7 × 996 + 484-tone MRU may be considered a combination of seven 996-tone RUs and one 484-tone RU.

[0190] Alternatively, 7 × 996 + 484-tone MRU may be considered a combination of two 2 × 996-tone RUs, three 996-tone RUs, and one 484-tone RU.

[0191] It should be understood that the methods for obtaining a 7×996+484-tone MRU are not limited to the embodiments. The multiple combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0192] It should be further understood that the data subcarriers of a 7×996+484-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 7×996+484-tone MRU, and the pilot subcarriers of a 7×996+484-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 7×996+484-tone MRU. For example, if a 7×996+484-tone MRU is a combination of one 4×996-tone RU, one 2×996-tone RU, one 996-tone RU, and one 484-tone RU, then the data subcarriers of the 7×996+484-tone MRU include the data subcarriers of the 4×996-tone RU, 2×996-tone RU, 996-tone RU, and 484-tone RU. The pilot subcarrier for 7×996+484-tone MRU includes pilot subcarriers of 4×996-tone RU, 2×996-tone RU, 996-tone RU, and 484-tone RU.

[0193] To facilitate understanding, the possible forms of the 7×996+484-tone MRU will be described in detail below with reference to Figure 10(d).

[0194] From Figure 10(d), the 7×996-tone MRU pattern consists of a total of 16 MRU patterns, namely, 7×996+484-tone MRU 1, 7×996+484-tone MRU 2, 7×996+484-tone MRU 3, 7×996+484-tone MRU 4, 7×996+484-tone MRU 5, 7×996+484-tone MRU 6, 7×996+484-tone MRU 7, 7×996+484-tone MRU 8, 7×996+484-tone MRU 9, 7×996+484-tone MRU 10, 7×996+484-tone MRU 11, 7×996+484-tone MRU It can be seen that this includes 12, 7×996+484-tone MRU, 13, 7×996+484-tone MRU, 14, 7×996+484-tone MRU, 15, and 77×996+484-tone MRU.

[0195] Method 1.5: If one 996-tone RU 1 or 996-tone RU 4 is punctured within a non-OFDMA 640 MHz band (or one 80 MHz subchannel #1 or 80 MHz subchannel #4 is punctured within a non-OFDMA 640 MHz band), and a 40 MHz subchannel is punctured within the remaining 560 MHz band, the punctured 640 MHz bandwidth can contain 6 × 996 + 484-tone MRUs, where 996-tone RU x indicates the x-th 996-tone RU. Different RUs do not have overlapping subcarriers. It can be understood that the non-OFDMA 640 MHz band contains 8 × 996-tone MRUs (for example, if one 80 MHz band corresponds to one 996-tone RU, then 640 MHz band corresponds to 8 × 996-tone MRUs). When the first or last 996-tone RU and one 160 MHz subchannel are punctured in non-OFDMA 640 MHz, the punctured 640 MHz bandwidth may include (8-2) × 996 + 484-tone MRU, i.e., 6 × 996 + 484-tone MRU.

[0196] Specifically, OFDMA transmission can be implemented if the punctured 640 MHz is allocated to one user, and the punctured 120 MHz subchannel is allocated to another user.

[0197] In the case shown in Method 1.5, two holes are punctured within the non-OFDMA 640 MHz, one hole being an 80 MHz subchannel (or 996-tone RU) and the other being a 40 MHz subchannel (or 484-tone RU). The hole in the 996-tone RU is larger than the hole in the 484-tone RU. From the MRU design rules explained in the basic concepts above, we can see that "if an MRU has multiple holes, the larger hole is located outside the data subcarriers, and the smaller hole is located between the data subcarriers." Therefore, in the case shown in Method 1.5, the hole in the 996-tone RU is located outside the data subcarriers. In other words, the RU is either the first 996-tone RU (e.g., 996-tone RU 1 above) or the last 996-tone RU (e.g., 996-tone RU 4 above). The hole in the 484-tone RU is located between the data subcarriers.

[0198] For example, a 6×996+484-tone MRU can be considered a combination of one 4×996-tone RU, one 2×996-tone RU, and one 484-tone RU.

[0199] Alternatively, a 6×996+484-tone MRU can be considered a combination of three 2×996-tone RUs and one 484-tone RU.

[0200] Alternatively, 6 × 996 + 484-tone MRU can be considered a combination of six 996-tone RUs and one 484-tone RU.

[0201] Alternatively, 6 × 996 + 484-tone MRU may be considered a combination of two 2 × 996-tone RUs, two 996-tone RUs, and one 484-tone RU.

[0202] It should be understood that the method for obtaining a 6 × 996 + 484-tone MRU is not limited to the embodiments. The multiple combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0203] It should be further understood that the data subcarriers of a 6×996+484-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 6×996+484-tone MRU, and the pilot subcarriers of a 6×996+484-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 6×996+484-tone MRU. For example, if a 6×996+484-tone MRU is a combination of two 2×996-tone RUs, two 996-tone RUs, and one 484-tone RU, then the data subcarriers of the 6×996-tone MRU are a combination of the data subcarriers of two 2×996-tone RUs, two 996-tone RUs, and one 484-tone RU. The pilot subcarriers of a 6×996-tone MRU include the pilot subcarriers of two 2×996-tone RUUs, two 996-tone RUs, and one 484-tone RU.

[0204] To facilitate understanding, the possible forms of the 5×996-tone MRU will be described in detail below with reference to Figure 10(e).

[0205] From Figure 10(e), it can be seen that the 6×996+484-tone MRU pattern contains a total of 28 MRU patterns, 6×996+484-tone MRU 1 to 6×996+484-tone MRU 28, as shown in Figure 10(d). The upper 80 MHz of 6×996+484-tone MRU 1 to 6×996+484-tone MRU 14 is punctured, and the lower 80 MHz of 6×996+484-tone MRU 15 to 6×996+484-tone MRU 28 is punctured.

[0206] Scheme 1.6: If one 2×996-tone RU 1 or 2×996-tone RU 4 is punctured within non-OFDMA 640 MHz (or one 160 MHz subchannel #1 or 160 MHz subchannel #4 is punctured within non-OFDMA 640 MHz), and a 40 MHz subchannel is punctured within the remaining 480 MHz, then the punctured 640 MHz bandwidth may contain 5×996+484-tone MRUs, where 2×996-tone RU x indicates the x-th 2×996-tone RU. Different RUs do not have overlapping subcarriers. It can be understood that non-OFDMA 640 MHz contains 8×996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 640 MHz corresponds to 8×996-tone MRUs). If the first or last 2 × 996-tone RU of a non-OFDMA 640 MHz signal is punctured, and one 40 MHz subchannel is punctured, the 640 MHz bandwidth after puncturing may include (8-3) × 996 + 484-tone MRU, i.e., 5 × 996 + 484-tone MRU.

[0207] Specifically, OFDMA transmission can be implemented if the punctured 640 MHz is allocated to one user, and the punctured 200 MHz subchannel is allocated to another user.

[0208] In the case shown in Scheme 1.6, two holes are punctured within the non-OFDMA 640 MHz, one hole being a 160 MHz subchannel (or 2×996-tone RU) and the other hole being a 40 MHz subchannel (or 484-tone RU). The hole in the 2×996-tone RU is larger than the hole in the 484-tone RU. From the MRU design rules explained in the basic concepts above, we can see that "if an MRU has multiple holes, the larger hole is located outside the data subcarriers, and the smaller hole is located between the data subcarriers." Therefore, in the case shown in Scheme 1.6, the hole in the 2×996-tone RU is located outside the data subcarriers. In other words, the RU is either the first 2×996-tone RU (e.g., 2×996-tone RU 1 above) or the last 2×996-tone RU (e.g., 2×996-tone RU 4 above). The holes in the 484-tone RU are located between the data subcarriers.

[0209] For example, 5 × 996 + 484-tone MRU can be considered a combination of one 4 × 996-tone RU, one 996-tone RU, and one 484-tone RU.

[0210] Alternatively, 5 × 996 + 484-tone MRU may be considered a combination of two 2 × 996-tone RUs, one 996-tone RU, and one 484-tone RU.

[0211] Alternatively, 5 × 996 + 484-tone MRU may be considered a combination of five 996-tone RUs and one 484-tone RU.

[0212] It should be understood that the method for obtaining a 5 × 996 + 484-tone MRU is not limited to the embodiments. The various combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0213] It should be further understood that the data subcarriers of a 5×996+484-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 5×996+484-tone MRU, and the pilot subcarriers of a 5×996+484-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 5×996+484-tone MRU. For example, if a 5×996+484-tone MRU is a combination of two 2×996-tone RUs, one 996-tone RU, and one 484-tone RU, then the data subcarriers of the 5×996+484-tone MRU are a combination of the data subcarriers of the two 2×996-tone RUs, the 996-tone RU, and the 484-tone RU. The pilot subcarriers of a 5×996+484-tone MRU include the pilot subcarriers of the two 2×996-tone RUs, the 996-tone RU, and the 484-tone RU.

[0214] To facilitate understanding, the possible forms of the 5×996+484-tone MRU will be described in detail below with reference to Figure 10(f).

[0215] From Figure 10(f), it can be seen that the 5×996+484-tone MRU pattern contains a total of 24 MRU patterns: 5×996+484-tone MRU 1 to 5×996+484-tone MRU 24, as shown in Figure 10(f). The upper 160 MHz of 5×996+484-tone MRU 1 to 5×996+484-tone MRU 12 is punctured, and the lower 160 MHz of 5×996+484-tone MRU 13 to 5×996+484-tone MRU 24 is punctured.

[0216] Method 1.7: One 2×996-tone RU 1 is punctured within the non-OFDMA 640 MHz range (or one 160 MHz subchannel #1 is punctured within the non-OFDMA 640 MHz range), and one 996-tone RU 3 or 996-tone RU 8 is punctured within the remaining 480 MHz range (or one 80 MHz subchannel #3 or 80 MHz subchannel #8 is punctured within the remaining 480 MHz range).

[0217] Alternatively, one 2×996-tone RU 4 may be punctured within a non-OFDMA 640 MHz PPDU (or one 160 MHz subchannel #4 may be punctured within a non-OFDMA 640 MHz), and one 996-tone RU 1 or 996-tone RU 6 may be punctured within the remaining 480 MHz (or one 80 MHz subchannel #1 or 80 MHz subchannel #6 may be punctured within the remaining 480 MHz). Also, if a 40 MHz subchannel is punctured within the remaining 400 MHz, the 640 MHz bandwidth after puncturing can contain 4×996+484-tone MRUs. 2×996-tone RU x indicates the x-th 2×996-tone RU. Different RUs do not have overlapping subcarriers. It can be understood that a non-OFDMA 640 MHz may include 8 × 996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 640 MHz corresponds to 8 × 996-tone MRUs). When one 2 × 996-tone RU, one 996-tone RU, and one 40 MHz subchannel are punctured in a non-OFDMA 640 MHz, the punctured 640 MHz bandwidth may include (8-4) × 996 + 484-tone MRUs, i.e., 4 × 996 + 484-tone MRUs.

[0218] Specifically, OFDMA transmission can be implemented if the punctured 640 MHz is allocated to one user, and the punctured 280 MHz subchannel is allocated to another user.

[0219] As shown in Method 1.7, three holes are punctured within a non-OFDMA 640 MHz, one hole being a 160 MHz subchannel (or 2×996-tone RU), one hole being an 80 MHz subchannel (or 996-tone RU), and one hole being a 40 MHz subchannel (or 484-tone RU). 2×996-tone RU is larger than 996-tone RU and 484-tone RU. From the MRU design rules explained in the basic concepts above, we can see that "if an MRU has multiple holes, larger holes are located outside the data subcarriers, and smaller holes are located between the data subcarriers." Therefore, as shown in Method 1.7, the holes in 2×996-tone RU (e.g., 2×996-tone RU 1 or 2×996-tone RU 4) are located outside the data subcarriers. Holes in 996-tone RUs are outside the bandwidth, except for the holes in 2×996-tone RUs (for example, if the hole in 2×996-tone RUs is 2×996-tone RU 1, then the hole in 996-tone RUs is 996-tone RU 3 or 996-tone RU 8, and if the hole in 2×996-tone RUs is 2×996-tone RU 4, then the hole in 996-tone RUs is 996-tone RU 1 or 996-tone RU 6). Holes in 484-tone RUs are located between data subcarriers.

[0220] For example, a 4×996+484-tone MRU can be considered a combination of one 2×996-tone RU, two 2×996-tone RUs, and one 484-tone RU.

[0221] Alternatively, a 4×996+484-tone MRU can be considered a combination of two 2×996-tone RUs and one 484-tone RU.

[0222] Alternatively, 4 × 996 + 484-tone MRU may be considered a combination of four 996-tone RUs and one 484-tone RU.

[0223] It should be understood that the method for obtaining a 4×996+484-tone MRU is not limited to the embodiments. The multiple combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0224] It should be further understood that the data subcarriers of a 4×996+484-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 4×996+484-tone MRU, and the pilot subcarriers of a 4×996+484-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 4×996+484-tone MRU. For example, if a 4×996+484-tone MRU is a combination of one 2×996-tone RU, two 2×996-tone RUs, and one 484-tone RU, then the data subcarriers of the 4×996-tone MRU are a combination of the data subcarriers of the 2×996-tone RU, two 2×996-tone RUs, and the 484-tone RU. The pilot subcarriers of a 4×996-tone MRU include the pilot subcarriers of the 2×996-tone RU, two 2×996-tone RUs, and the 484-tone RU.

[0225] To facilitate understanding, the possible forms of 4×996+484-tone MRU will be described in detail below with reference to Figures 10(g)-1 and 10(g)-2.

[0226] From Figures 10(g)-1 and 10(g)-2, it can be seen that the 4×996+484-tone MRU pattern contains a total of 40 MRU patterns: 4×996+484-tone MRU 1 to 4×996+484-tone MRU 40, as shown in Figures 10(g)-1 and 10(g)-2. The upper 240 MHz of 4×996+484-tone MRU 1 to 4×996+484-tone MRU 10 is punctured, the lower 240 MHz of 4×996+484-tone MRU 11 to 4×996+484-tone MRU 20 is punctured, the lower 80 MHz and upper 160 MHz of 4×996+484-tone MRU 21 to 4×996+484-tone MRU 30 is punctured, and the lower 160 MHz and upper 80 MHz of 4×996+484-tone MRU 31 to 4×996+484-tone MRU 40 is punctured.

[0227] Methods 1.1 to 1.7 describe in detail the MRU modes in different puncturing cases when the bandwidth for transmitting the PPDU is 640 MHz. The three puncturing methods shown in Methods 1.1 to 1.3 can be understood as directly doubling the MRU mode used when the bandwidth for transmitting the PPDU is 320 MHz.

[0228] For ease of understanding, please refer to Figures 11(a) to 11(c)-2, where the method of directly doubling the MRU mode corresponding to a 320 MHz bandwidth to obtain the MRU mode for a 640 MHz bandwidth will be explained in detail. For the MRU mode corresponding to a 320 MHz bandwidth, please refer to the MRU mode corresponding to a 320 MHz bandwidth, which is obtained by doubling 160 MHz as shown in Figures 7 and 8A to 8C. Details will not be explained again here. From Figures 7 and 8A to 8C, it can be seen that the MRU mode corresponding to a 320 MHz bandwidth includes multiple forms such as puncturing a 996-tone RU at 320 MHz, puncturing a 484-tone RU at 320 MHz, and puncturing both a 996-tone RU and a 484-tone RU at 320 MHz. Direct doubling in these forms includes several cases shown in Figures 11(a) to 11(c)-2, which correspond to puncturing of 2 × 996-tone RU at 640 MHz, puncturing of 996-tone RU at 640 MHz, and puncturing of 2 × 996-tone RU and 996-tone RU at 640 MHz, respectively.

[0229] From Figure 11(a), it can be seen that the MRU mode that punctures a 320 MHz 996-tone RU when the bandwidth is 320 MHz may be directly doubled to the MRU mode that punctures a 640 MHz 2 × 996-tone RU when the bandwidth is 640 MHz, and the 640 MHz bandwidth after puncture may include 6 × 996-tone MRUs.

[0230] From Figure 11(b), it can be seen that the MRU mode that punctures a 484-tone RU at 320 MHz when the bandwidth is 320 MHz may be directly doubled to the MRU mode that punctures a 996-tone RU at 640 MHz when the bandwidth is 640 MHz, and the 640 MHz bandwidth after puncture may include 7 × 996-tone MRUs.

[0231] From Figures 11(c)-1 and 11(c)-2, it can be seen that the MRU mode that punctures 996-tone RUs and 484-tone RUs at 320 MHz when the bandwidth is 320 MHz may be directly doubled to the MRU mode that punctures 2 × 996-tone RUs and 996-tone RUs at 640 MHz when the bandwidth is 640 MHz, and the 640 MHz bandwidth after puncturing may include 5 × 996-tone MRUs.

[0232] In addition, the four puncturing methods shown in Methods 1.4 to 1.7 can be understood as solutions in which punctured 484-tone RUs in 320 MHz MRUs are ignored. The puncturing granularity may be less than 996-tone RUs, and the methods of puncturing 2 × 996-tone RUs or 996-tone RUs shown in Methods 1.1 to 1.3 may not be used, and it may be understood that 484-tone RUs may be punctured. For specific puncturing methods, please refer to the explanations in Methods 1.4 to 1.7. Further details are not provided here.

[0233] In conclusion, two MRU modes, simple and complex, are provided for the 640 MHz bandwidth. One is a simple solution obtained through a dual extension based on the existing 320 MHz (i.e., sometimes referred to as MRU pattern #1, schemes 1.1 to 1.3), and the other is an MRU mode with a richer subchannel puncturing pattern (i.e., sometimes referred to as MRU pattern #2, schemes 1.1 to 1.7). The two designed 640 MHz oriented MRU modes can satisfy 640 MHz channel puncturing and OFDMA transmission.

[0234] Method 1 is primarily described by using an example where the bandwidth for transmitting the PPDU is 640 MHz. This application also provides a detailed MRU design solution for the case where the bandwidth for transmitting the PPDU is 480 MHz. The following description provides reference to Method 2.

[0235] Method 2: The bandwidth for transmitting PPDU is 480 MHz.

[0236] In the case shown in Method 2, the total bandwidth for transmitting the PPDU is 480 MHz. For a 480 MHz bandwidth, some MRU modes designed for a 640 MHz bandwidth in Method 1 may be reused, or the MRU modes may be redesigned for a 480 MHz bandwidth. The following methods are included:

[0237] Method 2.1: A portion of the 640 MHz MRU is reused.

[0238] Specifically, a continuous 640 MHz bandwidth may be constructed by puncturing one 2×996-tone RU 1 or 2×996-tone RU 4 within 480 MHz. Therefore, an MRU having the characteristic of puncturing one 2×996-tone RU 1 or 2×996-tone RU 4 at 480 MHz may also be used as a 640 MHz MRU.

[0239] For example, in the 5×996+484-tone MRU shown in Method 1.6, one 2×996-tone RU 1 or 2×996-tone RU 4 is punctured within a non-OFDMA 640 MHz band, and a 40 MHz subchannel is punctured within the remaining 480 MHz band. The 5×996+484-tone MRU is also applicable to a 480 MHz MRU, which is equivalent to puncturing a 40 MHz subchannel within a non-OFDMA 480 MHz band. See Figure 10(f) for specific puncturing methods. Further details are not provided here.

[0240] In another example, in the 5×996-tone MRU shown in Method 1.3, one 2×996-tone RU 1 or 2×996-tone RU 4 is punctured within a non-OFDMA 640 MHz band, and an 80 MHz subchannel is punctured within the remaining 480 MHz band. The 5×996-tone MRU is also applicable to a 480 MHz MRU, which is equivalent to puncturing an 80 MHz subchannel within a non-OFDMA 480 MHz band. See Figure 10(c) for specific puncturing methods. Further details are not provided here.

[0241] In another example, in the 4×996+484-tone MRU shown in Scheme 1.7, one 2×996-tone RU 1 and one 996-tone RU 3 or 996-tone RU 8 are punctured within a non-OFDMA 640 MHz, with a 40 MHz subchannel punctured within the remaining 400 MHz. Alternatively, one 2×996-tone RU 4 and one 996-tone RU 1 or 996-tone RU 6 are punctured within a non-OFDMA 640 MHz, with a 40 MHz subchannel punctured within the remaining 400 MHz.

[0242] The 4×996+484-tone MRU is also applicable to a 480 MHz MRU, which is equivalent to puncturing a 120 MHz subchannel with a non-OFDMA 480 MHz MRU. See Figures 10(g)-1 and 10(g)-2 for specific puncturing methods. Further details are not provided here.

[0243] To facilitate understanding, please refer to Figures 12(a) to 12(c)-2 to explain how the MRU corresponding to the 480 MHz bandwidth reuses a portion of the 640 MHz MRU.

[0244] From Figure 12(a), it can be seen that the MRU corresponding to the 480 MHz bandwidth may be in 5 × 996 + 484-tone MRU mode, and the portion shown in the dashed box in Figure 12(a) may be in MRU mode corresponding to the 480 MHz bandwidth.

[0245] From Figure 12(b), it can be seen that the MRU corresponding to the 480 MHz bandwidth may be in 5×996-tone MRU mode, and the portion shown in the dashed box in Figure 12(b) may be in MRU mode corresponding to the 480 MHz bandwidth.

[0246] From Figures 12(c)-1 and 12(c)-2, it can be seen that the MRU corresponding to a 480 MHz bandwidth may be in 4×996+484-tone MRU mode, and the portion shown in the dashed box in Figures 12(c)-1 and 12(c)-2 may be in MRU mode corresponding to a 480 MHz bandwidth.

[0247] Furthermore, while the 6×996-tone MRU in method 1.2 is also obtained by puncturing one 2×996-tone at non-OFDMA 640 MHz, it should be noted that the MRU in the 480 MHz bandwidth cannot reuse the 6×996-tone MRU mode because it must satisfy both the conditions of a continuous 480 MHz bandwidth and puncturing in a continuous bandwidth. However, as shown in Figure 13, any one of the 6×996-tone MRUs satisfies only one of the conditions.

[0248] Method 2.2: An MRU mode that satisfies a 480 MHz bandwidth is designed for a 480 MHz bandwidth, with one 40 MHz subchannel punctured with non-OFDMA 480 MHz to implement OFDMA transmission.

[0249] For example, as shown in Scheme 2.2, when one 40 MHz subchannel is punctured with non-OFDMA 480 MHz (or one 484-tone RU is punctured with non-OFDMA 480 MHz), the punctured 480 MHz bandwidth may include 5 × 996 + 484-tone MRU. It can be understood that the non-OFDMA 480 MHz includes 6 × 996-tone MRU (for example, if one 80 MHz corresponds to one 996-tone RU, then 480 MHz corresponds to 6 × 996-tone MRU). When one 40 MHz subchannel is punctured with non-OFDMA 480 MHz, the punctured 480 MHz bandwidth may include (6-1) × 996 + 484-tone MRU, i.e., 5 × 996 + 484-tone MRU.

[0250] Specifically, OFDMA transmission can be implemented if the punctured 480 MHz is allocated to one user, and the punctured 40 MHz subchannel is allocated to another user.

[0251] For example, 5 × 996 + 484-tone MRU can be considered a combination of one 4 × 996-tone RU, one 996-tone RU, and one 484-tone RU.

[0252] Alternatively, 5 × 996 + 484-tone MRU may be considered a combination of two 2 × 996-tone RUs, one 996-tone RU, and one 484-tone RU.

[0253] Alternatively, 5 × 996 + 484-tone MRU may be considered a combination of five 996-tone RUs and one 484-tone RU.

[0254] It should be understood that the method for obtaining a 5 × 996 + 484-tone MRU is not limited to the embodiments. The various combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0255] It should be further understood that the data subcarriers of a 5×996+484-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 5×996+484-tone MRU, and the pilot subcarriers of a 5×996+484-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 5×996+484-tone MRU. For example, if a 5×996+484-tone MRU is a combination of two 2×996-tone RUs, one 996-tone RU, and one 484-tone RU, then the data subcarriers of the 5×996+484-tone MRU are a combination of the data subcarriers of the two 2×996-tone RUs, the 996-tone RU, and the 484-tone RU. The pilot subcarriers of a 5×996+484-tone MRU include the pilot subcarriers of the two 2×996-tone RUs, the 996-tone RU, and the 484-tone RU.

[0256] To facilitate understanding, the possible forms of 5×996+484-tone MRU will be described in detail below with reference to Figure 14(a).

[0257] From Figure 14(a), it can be seen that the 5×996+484-tone MRU pattern contains a total of 12 MRU patterns: 5×996+484-tone MRU 1 to 5×996+484-tone MRU 12, as shown in Figure 14(a).

[0258] Method 2.3: An MRU mode that satisfies a 480 MHz bandwidth is designed for a 480 MHz bandwidth, with one 80 MHz subchannel punctured with non-OFDMA 480 MHz to implement OFDMA transmission.

[0259] For example, as shown in Scheme 2.3, when one 80 MHz subchannel is punctured at non-OFDMA 480 MHz (or one 996-tone RU is punctured at non-OFDMA 480 MHz), the 480 MHz bandwidth after puncture may include 5 × 996-tone MRUs. It can be understood that non-OFDMA 480 MHz includes 6 × 996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 480 MHz corresponds to 6 × 996-tone MRUs). When one 80 MHz subchannel is punctured at non-OFDMA 480 MHz, the 480 MHz bandwidth after puncture may include (6-1) × 996-tone MRUs, i.e., 5 × 996-tone MRUs.

[0260] For example, a 5×996-tone MRU can be considered a combination of one 4×996-tone RU and one 996-tone RU.

[0261] Alternatively, a 5×996-tone MRU may be considered a combination of two 2×996-tone RUs and one 996-tone RU.

[0262] Alternatively, 5 × 996-tone MRU may be considered as a combination of five 996-tone RUs.

[0263] It should be understood that the method of obtaining 5 × 996-tone MRU is not limited to the embodiments. The various combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0264] It should be further understood that the data subcarriers of a 5×996-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 5×996-tone MRU, and the pilot subcarriers of a 5×996-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 5×996-tone MRU. For example, if a 5×996-tone MRU is a combination of two 2×996-tone RUs and one 996-tone RU, then the data subcarriers of the 5×996-tone MRU are formed by a combination of data subcarriers of the two 2×996-tone RUs and the 996-tone RU. The pilot subcarriers of a 5×996-tone MRU include the pilot subcarriers of the two 2×996-tone RUs and the 996-tone RU.

[0265] To facilitate understanding, the possible forms of 5×996-tone MRU will be described in detail below with reference to Figure 14(b).

[0266] From Figure 14(b), it can be seen that the 5×996-tone MRU pattern contains a total of six MRU patterns, from 5×996-tone MRU 1 to 5×996-tone MRU 6, as shown in Figure 14(b).

[0267] Method 2.4: An MRU mode that satisfies a 480 MHz bandwidth is designed for a 480 MHz bandwidth, and in order to implement OFDMA transmission, one 80 MHz subchannel is punctured in non-OFDMA 480 MHz, and then one 40 MHz subchannel is punctured.

[0268] For example, in the case shown in Scheme 2.4, one 996-tone RU 1 is punctured within non-OFDMA 480 MHz (or one 80 MHz sub-channel #1 is punctured within non-OFDMA 640 MHz), and one 40 MHz sub-channel is punctured within the remaining 480 MHz (or one 484-tone RU is punctured within the remaining 480 MHz).

[0269] Alternatively, one 996-tone RU 6 is punctured within non-OFDMA 480 MHz (or one 80 MHz sub-channel #6 is punctured within non-OFDMA 640 MHz), and one 40 MHz sub-channel is punctured within the remaining 480 MHz. The 480 MHz bandwidth after puncturing may include 4×996 + 484-tone MRU. 996-tone RU x indicates the x-th 996-tone RU. Different RUs do not have overlapping sub-carriers. It can be understood that non-OFDMA 480 MHz includes 6×996-tone MRU (for example, when 1 MHz corresponds to one 996-tone RU, 640 MHz corresponds to 8×996-tone MRU). When one 996-tone RU and one 40 MHz sub-channel are punctured in non-OFDMA 480 MHz, the 480 MHz bandwidth after puncturing may include (6 - 2)×996 + 484-tone MRU, that is, 4×996 + 484-tone MRU.

[0270] Specifically, when the 480 MHz after puncturing is allocated to one user and the punctured 120 MHz sub-channel is allocated to another user, OFDMA transmission can be implemented.

[0271] In the case shown in Mode 2.4, two holes are punctured within the non-OFDMA 480 MHz. One hole is an 80 MHz subchannel (or 996-tone RU), and one hole is a 40 MHz subchannel (or 484-tone RU). The 996-tone RU is larger than the 484-tone RU. From the MRU design rules described by the above basic concept, it can be seen that "when the MRU has multiple holes, the larger-sized holes are located outside the data subcarriers, and the smaller-sized holes are located between the data subcarriers". Therefore, in the case shown in Mode 2.4, the holes of the 996-tone RU (e.g., the above-mentioned 996-tone RU 1 or the above-mentioned 996-tone RU 6) are located outside the data subcarriers. The holes of the 484-tone RU are located between the data subcarriers.

[0272] For example, a 4×996 + 484-tone MRU may be regarded as a combination of one 2×996-tone RU, two 2×996-tone RUs, and one 484-tone RU.

[0273] Alternatively, a 4×996 + 484-tone MRU may be regarded as a combination of two 2×996-tone RUs and one 484-tone RU.

[0274] Alternatively, a 4×996 + 484-tone MRU may also be regarded as a combination of four 996-tone RUs and one 484-tone RU.

[0275] It should be understood that the method of obtaining a 4×996 + 484-tone MRU is not limited in the embodiment. The above multiple combination methods are merely examples and do not constitute any limitation to the protection scope of this application.

[0276] It should be further understood that the data subcarriers of a 4×996+484-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 4×996+484-tone MRU, and the pilot subcarriers of a 4×996+484-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 4×996+484-tone MRU. For example, if a 4×996+484-tone MRU is a combination of one 2×996-tone RU, two 2×996-tone RUs, and one 484-tone RU, then the data subcarriers of the 4×996-tone MRU are a combination of the data subcarriers of the 2×996-tone RU, two 2×996-tone RUs, and the 484-tone RU. The pilot subcarriers of a 4×996-tone MRU include the pilot subcarriers of the 2×996-tone RU, two 2×996-tone RUs, and the 484-tone RU.

[0277] To facilitate understanding, the possible forms of the 5×996-tone MRU will be described in detail below with reference to Figure 14(c).

[0278] From Figure 14(c), it can be seen that the 4×996+484-tone MRU pattern contains a total of 20 MRU patterns: 4×996+484-tone MRU 1 to 4×996+484-tone MRU 20, as shown in Figure 14(c). The upper 80 MHz of 4×996+484-tone MRU 1 to 4×996+484-tone MRU 10 is punctured, and the lower 80 MHz of 4×996+484-tone MRU 11 to 4×996+484-tone MRU 20 is punctured.

[0279] Method 2.5: An MRU mode that satisfies a 480 MHz bandwidth is designed for a 480 MHz bandwidth, and one 160 MHz subchannel is punctured in non-OFDMA 480 MHz to implement OFDMA transmission.

[0280] For example, as shown in Scheme 2.4, if one 2×996-tone RU is punctured at non-OFDMA 480 MHz (or if one 160 MHz subchannel is punctured at non-OFDMA 640 MHz), the 480 MHz bandwidth after puncture may contain 4×996-tone MRUs. The non-OFDMA 480 MHz may be understood to contain 6×996-tone MRUs (for example, if one 80 MHz corresponds to one 996-tone RU, then 640 MHz corresponds to 8×996-tone MRUs). If one 996-tone RU is punctured at non-OFDMA 480 MHz, the 480 MHz bandwidth after puncture may contain (6-2)×996-tone MRUs, i.e., 4×996-tone MRUs.

[0281] Specifically, OFDMA transmission can be implemented if the punctured 480 MHz is allocated to one user, and the punctured 160 MHz subchannel is allocated to another user.

[0282] For example, a 4×996-tone MRU can be considered a combination of one 2×996-tone RU and two 2×996-tone RUs.

[0283] Alternatively, a 4×996-tone MRU may be considered a combination of two 2×996-tone RUs.

[0284] Alternatively, 4 x 996-tone MRU may be considered a combination of four 996-tone RUs.

[0285] It should be understood that the method of obtaining 4 × 996-tone MRU is not limited to the embodiments. The various combinations described above are merely examples and do not constitute any limitation to the scope of protection of this application.

[0286] It should be further understood that the data subcarriers of a 4×996-tone MRU are formed by a combination of data subcarriers of multiple RUs that make up the 4×996-tone MRU, and the pilot subcarriers of a 4×996-tone MRU are formed by the pilot subcarriers of multiple RUs that make up the 4×996-tone MRU. For example, if a 4×996-tone MRU is a combination of one 2×996-tone RU and two 2×996-tone RUs, the data subcarriers of the 4×996-tone MRU are formed by a combination of data subcarriers of the 2×996-tone RU and the two 2×996-tone RUs. The pilot subcarriers of a 4×996-tone MRU include the pilot subcarriers of the 2×996-tone RU and the two 2×996-tone RUs.

[0287] To facilitate understanding, the possible forms of the 5×996-tone MRU will be described in detail below with reference to Figure 14(d).

[0288] From Figure 14(d), it can be seen that the 4×996-tone MRU pattern contains a total of three MRU patterns, 4×996-tone MRU 1 to 4×996-tone MRU 3, as shown in Figure 14(d).

[0289] In conclusion, for a 480 MHz bandwidth, two MRU pattern design solutions are provided: one that reuses some MRU patterns from a 640 MHz bandwidth (i.e., scheme 2.1, sometimes referred to as MRU pattern #3) and one that does not reuse them (i.e., schemes 2.2 through 2.5, sometimes referred to as MRU pattern #3). The designed 480 MHz directional MRU patterns can satisfy 480 MHz channel puncturing and OFDMA transmission.

[0290] In Mode 1 and Mode 2, the possible related MRU modes are described in detail by using bandwidths of 640 MHz and 480 MHz. In this embodiment, the specific size of the bandwidth is not limited. For example, the future bandwidth may be 2×480 MHz. For the MRU mode corresponding to the 2×480 MHz bandwidth, refer to the design of the MRU mode corresponding to 480 MHz. Examples will not be described again in this specification. The MRU modes designed for different bandwidths may be referred to as the MRU modes included in the bandwidth, the MRU modes corresponding to the bandwidth, or the MRU modes included in the bandwidth. This is not limited in this application.

[0291] Furthermore, as described above, MRU modes with different bandwidths have different possibilities. Therefore, when the bandwidth can be 640 MHz or 480 MHz, before MRU allocation, the AP can determine a specific method for designing an appropriate MRU. For ease of understanding, below, referring to FIG. 15, how the AP determines the method for designing the MRU mode in this embodiment will be described in detail.

[0292] From FIG. 15, it can be seen that even if it is determined that the bandwidth is 640 MHz or 480 MHz, after the bandwidth is determined, the MRU mode may be determined by Mode 1 or Mode 2. For the specific method of determining the MRU mode, refer to the above description. Details will not be described again here.

[0293] In addition, this application further provides a communication method. The communication method can indicate the MRU mode in the communication method shown in FIG. 9. Note that the MRU mode indication method may further indicate another MRU mode. In this application, the MRU modes that can be specifically indicated by the following MRU mode methods are not limited. For ease of explanation, below, by using an example in which the MRU mode in the communication method shown in FIG. 9 is indicated, the communication method will be described in detail with reference to FIG. 16.

[0294] Figure 16 is a schematic flowchart of another communication method according to one embodiment of this application. It includes the following steps:

[0295] S1610: The AP generates the PPDU.

[0296] Specifically, PPDU is used for the allocation status of frequency resources.

[0297] In possible implementations, the PPDU includes a resource allocation field, which indicates the allocation status of frequency resources for one or more stations. For example, frequency resources include MRUs.

[0298] Specifically, in this implementation, if the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU that supports a bandwidth wider than 320 MHz. For example, in the communication method shown in Figure 9, the resource allocation field indicates an MRU mode designed for a 640 MHz bandwidth and / or an MRU mode designed for a 480 MHz bandwidth.

[0299] Furthermore, the resource allocation field is compatible with the indicator function of resource allocation fields defined in the current protocol. For example, if the value range of the resource allocation field is between 0 and 303, the resource allocation field indicates an MRU corresponding to a bandwidth of 320 MHz or less.

[0300] For example, in this implementation, the resource allocation field further indicates RUs, which include at least one of 484-tone RUs, 996-tone RUs, 2×996-tone RUs, and 4×996-tone RUs.

[0301] Optionally, the resource allocation field is X bits, where X is an integer greater than or equal to 9.

[0302] If the number of MRUs corresponding to bandwidths wider than 320 MHz, as indicated by the resource allocation field, is 28 or less (for example, MRU pattern #1 corresponding to a 640 MHz bandwidth), the resource allocation field may be X bits (where X is equal to 9) and be compatible with indicating MRUs corresponding to bandwidths of 320 MHz or less and MRUs corresponding to bandwidths wider than 320 MHz.

[0303] If the number of MRUs corresponding to bandwidths wider than 320 MHz, as indicated by the resource allocation field, is greater than 28 (for example, MRU pattern #2 corresponding to a 640 MHz bandwidth), the resource allocation field may be X bits (where X is an integer greater than 9) and may be compatible with indicating MRUs corresponding to bandwidths of 320 MHz or less and MRUs corresponding to bandwidths wider than 320 MHz.

[0304] In another possible implementation, the PPDU includes resource allocation and binding fields, which indicate the allocation status of the station's frequency resources. For example, the frequency resources include MRU.

[0305] Specifically, in this implementation, the resource allocation field includes information indicating the MRU corresponding to a P MHz bandwidth (e.g., a bandwidth of 320 MHz or less), where P is greater than 160, and the coupling field indicates whether a first resource block to the left of the DC subcarrier and a second resource block to the right of the DC subcarrier are coupled at 2 × P MHz. The first resource block to the left of the DC subcarrier may be understood as a low-frequency resource block, and the second resource block to the right of the DC subcarrier may be understood as a high-frequency resource block.

[0306] Furthermore, if the join field indicates that the first resource block and the second resource block are not joined, the first resource block and the second resource block are assigned separately to different stations; or, if the join field indicates that the first resource block and the second resource block are joined, the first resource block and the second resource block are assigned to the same station.

[0307] For example, in this implementation, the resource allocation field further indicates RUs, which include at least one of 484-tone RUs, 996-tone RUs, 2×996-tone RUs, and 4×996-tone RUs.

[0308] For example, the first resource block is: It includes one of the following: the first adjacent RU to the left of the DC subcarrier within the bandwidth, the first adjacent MRU to the left of the DC subcarrier within the bandwidth, the second adjacent RU to the left of the DC subcarrier within the bandwidth, or the second adjacent MRU to the left of the DC subcarrier within the bandwidth.

[0309] The second resource block is, It includes one of the following: the first adjacent RU to the right of a DC subcarrier within the bandwidth, the first adjacent MRU to the right of a DC subcarrier within the bandwidth, the second adjacent RU to the right of a DC subcarrier within the bandwidth, or the second adjacent MRU to the right of a DC subcarrier within the bandwidth.

[0310] Furthermore, after generating the PPDU, the AP sends the PPDU to one or more STAs, and the method shown in Figure 16 further includes the following steps.

[0311] S1620: The AP sends a PPDU to the STA, or the STA receives a PPDU from the AP.

[0312] An STA is one of one or more STAs. The PPDU transmission method is not limited in this embodiment. For details, refer to the description of the PPDU transmission method between the AP and STA specified in existing or future protocols. Details are not described here.

[0313] S1630:STA determines the assigned RU or MRU based on the PPDU.

[0314] In this embodiment, the STA can determine the assigned RU or MRU based on the received PPDU. Specifically, the STA determines the assigned RU or MRU based on the resource instruction information contained in the PPDU.

[0315] In possible implementations, the STA can receive data or information from the AP on its assigned RU or MRU. For example, the STA receives data from the AP on a RU or MRU with a 640 MHz bandwidth.

[0316] In another possible implementation, the STA may transmit data or information to the AP on its assigned RU or MRU. For example, the STA may transmit a PPDU to the AP on its assigned RU or MRU (for distinction, a PPDU transmitted to the STA by the AP may be referred to as PPDU#1, and a PPDU transmitted to the AP by the STA may be referred to as PPDU#2).

[0317] For ease of understanding, the following will detail how the PPDU in this application represents different MRUs corresponding to a 640 MHz bandwidth, with reference to Methods 3 through 5.

[0318] Method 3: The PPDU includes a resource allocation field (e.g., RU Allocation subfield).

[0319] For the sake of clarity, an example is used in which the resource allocation field is the RU Allocation subfield. For cases where the resource allocation field is a different frequency resource allocation field (e.g., a field used for frequency resource allocation as defined in a future protocol), please refer to the following description of the RU Allocation subfield. Further details are not provided in this embodiment.

[0320] Specifically, the remaining resources in the RU Allocation subfield of the standard may be used to further allocate 28 MRUs (there are 208 entries, and one MRU is allocated for every 8 entries).

[0321] In possible implementations, the MRU modes corresponding to a 640 MHz bandwidth are obtained by directly doubling the MRU modes corresponding to a 320 MHz bandwidth (e.g., MRU pattern #1), i.e., the multiple forms shown in Methods 1.1 to 1.3. The MRU modes corresponding to a 640 MHz bandwidth include a total of 24 MRU modes (e.g., a total of 8 MRU modes shown in Figure 10(a): 7×996-tone MRU 1 to 7×996-tone MRU 8 + a total of 4 MRU modes shown in Figure 10(b): 6×996-tone MRU 1 to 6×996-tone MRU 4 + a total of 12 MRU modes shown in Figure 10(c): 5×996-tone MRU 1 to 5×996-tone MRU 12 = 24 MRU modes).

[0322] In this implementation, there are 24 MRU modes corresponding to a 640 MHz bandwidth, and the remaining resources in the RU Allocation subfield can be used to allocate an additional 28 MRUs. Therefore, in this implementation, different MRUs can be represented by designing the RU Allocation subfield.

[0323] To facilitate understanding, Table 1 is provided to illustrate the possible forms of the RU Allocation subfield in this implementation.

[0324] [Table 1A] [Table 1B] [Table 1C]

[0325] In Table 1, the number of entries in each row refers to the number of RU Allocation subfield values ​​for the corresponding row (for example, the number of entries = 8 in row 3 of Table 1 indicates that there are 8 RU Allocation subfield values ​​from 304 to 311), and the RU Allocation subfield values ​​refer to the same RU allocation used in the frequency domain. However, in this case, if the RU Allocation subfield value changes, the number of user fields in the user-specific fields within the EHT-SIG content channel corresponding to the RU Allocation subfield changes accordingly.

[0326] In addition, the RU Allocation subfield of RU or MRU may be represented by a value in the range of 304 to 463 (100110y2y1y0 to 111001y2y1y0 in binary representation), where y2y1y0 indicates the number of user fields in the corresponding content channel.

[0327] Table 1 shows that when the RU Allocation subfield value is between 0 and 303, MRUs corresponding to bandwidths of 320 MHz or less may be indicated. For specific indication methods, see the explanation of how the RU Allocation subfield indicates MRUs corresponding to different bandwidths (e.g., MRUs corresponding to 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz) in the current protocol (e.g., the 802.11be standard). Details are not explained again here. Furthermore, the remaining resources of the RU Allocation subfield in the current standard can indicate an MRU mode corresponding to a 640 MHz bandwidth (e.g., MRU pattern #1). Specifically, when the RU Allocation subfield value is between 304 and 311, a 2×996-tone RU is indicated. By analogy, when the RU Allocation subfield value is between 312 and 319, a 4×996-tone RU may be indicated. Different indications are defined to show the MRU mode corresponding to the 640 MHz bandwidth, from 456 to 463 (as shown in Table 1) in the RU Allocation subfield value.

[0328] From the above explanation, it can be seen that in the instruction scheme shown in Scheme 3, a maximum of 28 MRUs may be allocated. However, if the MRU mode corresponding to the 640 MHz bandwidth (e.g., MRU pattern #2) is not directly doubled from the MRU mode corresponding to the 320 MHz bandwidth, there are a total of 132 MRU modes corresponding to the 640 MHz bandwidth (i.e., the total number of all MRU modes in Schemes 1.1 to 1.7). If an instruction is newly added to the RU Allocation field, 132 × 8 = 1056 entries are required, resulting in significant overhead. To reduce instruction overhead, this application further provides another instruction scheme.

[0329] Method 4: MRU mode is indicated by whether the resource blocks on both sides of the DC subcarrier are coupled.

[0330] Specifically, in the case shown in Method 4, the PPDU includes resource configuration fields and join fields.

[0331] For example, at least two bits may be added to the U-SIG or SIG (e.g., UHR-SIG) in next-generation Wi-Fi as a combined field (e.g., MRU combined instruction field).

[0332] In possible implementations, the MRU Combing Indication field consists of two newly added bits in the signal field, in this case, If the MRU Combing Indication field is 0, it indicates that the join will not be performed. When the MRU Combing Indication field is 1, it indicates that the first RU or MRU to the left of the DC subcarrier position is coupled with the second RU or MRU to the right of the DC subcarrier position. If the MRU Combing Indication field is 2, it indicates that the second RU or MRU to the left of the DC subcarrier position is coupled with the first RU or MRU to the right of the DC subcarrier position, or If the MRU Combing Indication field is 3, it indicates that the first RU or MRU to the left of the DC subcarrier position is coupled with the first RU or MRU to the right of the DC subcarrier position.

[0333] To facilitate understanding, the following section will explain how the MRU Combing Indication field indicates different MRUs, using specific examples.

[0334] In a 640 MHz PPDU, the DC subcarrier position divides the PPDU into two 320 MHz bands. The original RU Allocation field indication method for 320 MHz is used to indicate the two 320 MHz bandwidths separately, and then the MRU Combing Indication field indicates how the two sides of the DC subcarrier position are combined. Values ​​of the MRU Combing Indication field: The left and right RU / MRU of the DC subcarrier position at 0:640 MHz are not coupled; At 1:640 MHz, the first RU / MRU to the left of the DC subcarrier position and the second RU / MRU to the right of the DC subcarrier position are coupled; 2: The second RU / MRU to the left of the DC subcarrier position at 640 MHz and the first RU / MRU to the right of the DC subcarrier position are coupled; and At 3:640 MHz, the first RU / MRU to the left of the DC subcarrier position and the first RU / MRU to the right of the DC subcarrier position are coupled.

[0335] For example, a 640 MHz 5×996-tone MRU 1 includes, in ascending order of frequency, a 996-tone RU, 3×996-tone MRU 1, DC, 2×996-tone RU, and 2×996-tone RU.

[0336] If the MRU Combing Indication field is 0, there are no MRUs with a bandwidth wider than 320 MHz in the 640 MHz PPDU.

[0337] If the MRU Combing Indication field is 3, the first RU / MRU to the left of the 640 MHz DC subcarrier position (3×996-tone MRU 1) and the first RU / MRU to the right of the DC subcarrier position (2×996-tone RU) are combined, and the user can know that, based on the combined MRU, 5×996-tone MRU 1 is actually assigned to the 640 MHz PPDU.

[0338] In another example, a 7×996-tone MRU 4 in a 640 MHz PPDU includes, in ascending order of frequency, 3×996-tone MRU 4, 996-tone RU, DC, and 4×996-tone RU.

[0339] If the MRU Combing Indication field is 0, there are no MRUs with a bandwidth wider than 320 MHz in the 640 MHz PPDU.

[0340] If the MRU Combing Indication field is 2, the second RU / MRU to the left of the 640 MHz DC subcarrier position (3×996-tone MRU 4) and the first RU / MRU to the right of the DC subcarrier position (4×996-tone RU) are combined and assigned to the same user. Based on the combined MRU, the user can know that a 7×996-tone MRU 4 directed to the 640 MHz PPDU is actually assigned.

[0341] In another example, a 7×996-tone MRU 4 of a 640 MHz PPDU includes 4×996-tone RUs, 996-tone RUs, DCs, and 3×996-tone MRU 1 in ascending order of frequency.

[0342] If the MRU Combing Indication field is 0, there are no MRUs with a bandwidth wider than 320 MHz in the 640 MHz PPDU.

[0343] If the MRU Combing Indication field is 1, the first RU / MRU (4×996-tone RU) to the left of the 640 MHz DC subcarrier position and the second RU / MRU (3×996-tone MRU 1) to the right of the DC subcarrier position are combined and assigned to the same user. Based on the combined MRU, the user can know that 7×996-tone MRU 4 directed to the 640 MHz PPDU is actually assigned.

[0344] In addition, the current RU Allocation subfield may be extended to indicate different MRU modes, as shown in Scheme 5 below.

[0345] Method 5: The PPDU includes a resource allocation field, and the RU Allocation subfield contains 10 bits. Note that in the case shown in Method 5, the RU Allocation subfield being 10 bits is used for illustrative purposes. In practice, the RU Allocation subfield may be X bits (where X is an integer greater than 9).

[0346] In particular, in this embodiment, if the RU Allocation subfield is expanded from 9 bits (e.g., B8 B7 B6 B5 B4 B3 B2 B1 B0 in Table 1) to 10 bits (B9 B8 B7 B6 B5 B4 B3 B2 B1 B0), this corresponds to an additional 29 = 512 entries, with one MRU allocated for every 8 entries. This is equivalent to the remaining resources of the RU Allocation subfield and the resources acquired through the expansion being used for the allocation of an additional 28 + 64 = 92 MRUs. However, for 132 MRU modes corresponding to a 640 MHz bandwidth, the same entries can represent multiple MRU modes. Therefore, the number of entries after expansion can satisfy the requirement of representing 132 MRU modes.

[0347] For example, the 132 MRU modes corresponding to a 640 MHz bandwidth include 7×996+484-tone MRU, 7×996-tone MRU, 6×996+484-tone MRU, 6×996-tone MRU, 5×996+484-tone MRU, 5×996-tone MRU, and 4×996+484-tone MRU. The specific number of entries required for each MRU mode is as follows: 7×996+484-tone MRU:16×1 (The same entry represents one MRU; for example, 7×996+484-tone MRU 1 to 7×996+484-tone MRU 16 shown in Figure 10(d) have different puncturing locations, resulting in the same entry representing one MRU); 7×996-tone MRU:8×1 (The same entry represents one MRU; for example, 7×996-tone MRU 1 to 7×996-tone MRU 8 shown in Figure 10(a) have different puncturing locations, resulting in the same entry representing one MRU); 6×996+484-tone MRU:14×2 (The same entry indicates two MRUs, and in 6×996+484-tone MRU 1 to 6×996+484-tone MRU 28 shown in Figure 10(e), 996-tone RU 8 is punctured in 6×996+484-tone MRU 1 to 6×996+484-tone MRU 14, and 996-tone RU 1 is punctured in 6×996+484-tone MRU 13 to 6×996+484-tone MRU 24, and the same entry indicates two MRUs to show the MRU mode of 6×996+484-tone MRU 1 to 6×996+484-tone MRU 12 by showing the punctured 996-tone RU 8 or 996-tone RU 1); 6×996-tone MRU:4×1 (The same entry represents one MRU; for example, 6×996-tone MRU 1 to 6×996-tone MRU 4 shown in Figure 10(b) have different puncturing locations, resulting in the same entry representing one MRU); 5×996+484-tone MRU:12×2 (The same entry indicates two MRUs, and in 5×996+484-tone MRU 1 to 5×996+484-tone MRU 24 shown in Figure 10(f), 2×996-tone RU 4 is punctured in 5×996+484-tone MRU 1 to 5×996+484-tone MRU 12, and 2×996-tone RU 1 is punctured in 5×996+484-tone MRU 13 to 5×996+484-tone MRU 24, and by showing the punctured 2×996-tone RU 4 or 2×996-tone RU 1, 5×996+484-tone MRU 1 to 5×996+484-tone MRU It shows 12 MRU modes, and the same entry shows two MRUs); 5×996 tone MRU:6×2 (The same entry indicates two MRUs, and in 5×996 tone MRU 1 to 5×996 tone MRU 12 shown in Figure 10(c), 2×996 tone RU 4 is punctured in 5×996 tone MRU 1 to 5×996 tone MRU 6, and 2×996 tone RU 1 is punctured in 5×996 tone MRU 7 to 5×996 tone MRU 12, indicating the MRU modes of 5×996 tone MRU 1 to 5×996 tone MRU 6 by showing the punctured 2×996 tone RU 4 or 2×996 tone RU 1, thereby indicating the same entry indicates two MRUs); and 4×996+484 tone MRU: 10×4 (The same entry shows four MRUs, and in 4×996+484-tone 1 to 4×996+484-tone 40 shown in Figures 10(g)-1 and 10(g)-2, 2×996-tone RU 4 is punctured by 4×996+484-tone 1 to 4×996+484-tone MRU 10 and 4×996+484-tone 21 to 4×996+484-tone 30, and 2×996-tone RU 1 is punctured by 4×996+484-tone 11 to 4×996+484-tone 20 and 4×996+484-tone 31 to 4×996+484-tone 40, and 996-tone RU 6 is punctured in 4×996+484-tone 1 to 4×996+484-tone MRU 10, and 996-tone RU 1 is punctured in 4×996+484-tone 21 to 4×996+484-tone 30. Similarly, 996-tone RU 3 is punctured in 4×996+484-tone 11 to 4×996+484-tone 20, and 996-tone RU 8 is punctured in 4×996+484-tone 31 to 4×996+484-tone 40, indicating the positions of the punctured 2×996-tone RUs and the punctured 484-tone RUs, thus showing 4×996+484-tone 1 to 4×996+996-tone MRU It shows 10 MRU modes, and therefore the same entry shows 4 MRUs.

[0348] For all MRU modes, a total of (16+8+14+4+12+6+10)×8 = 560 entries are required.

[0349] The existing 802.11be standard defines a RU Allocation Table with 2^9 = 512 entries corresponding to a 9-bit RU Allocation field to indicate RUs and MRUs, with corresponding sequence numbers from 0 to 511. Entries 304-511 are currently idle and unused, with the number 208. The 9-bit RU Allocation field can be extended to 10 bits, adding 512 entries. In this case, the number of indicators available for 640 MHz PPDU oriented MRU pattern 2 is 208 + 512 = 720, which is much more than the required number of 560.

[0350] Therefore, if the 9-bit RU Allocation field is extended to 10 bits, the corresponding RU allocation table can satisfy the instructions for 640 MHz PPDU-oriented MRU pattern 2.

[0351] To facilitate understanding, Table 2 illustrates the possible forms of the RU Allocation subfield in this implementation.

[0352] [Table 2A] [Table 2B] [Table 2C] [Table 2D] [Table 2E] [Table 2F] [Table 2G] [Table 2H] [Table 2I] [Table 2J] [Table 2K]

[0353] Table 2 shows that when the RU Allocation subfield value is between 0 and 303, MRUs corresponding to bandwidths of 320 MHz or less may be indicated. For specific indication methods, please refer to the explanation of how the RU Allocation subfield indicates MRUs corresponding to different bandwidths (e.g., MRUs corresponding to 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz) in current protocols (e.g., the 802.11be standard). Further details are not provided here.

[0354] In Table 2, the number of entries in each row refers to the number of RU Allocation subfield values ​​for the corresponding row (for example, the number of entries = 8 in row 3 of Table 2 indicates that there are 8 RU Allocation subfield values ​​between 312 and 319), and the RU Allocation subfield values ​​refer to the same RU allocation used in the frequency domain. However, in this case, if the RU Allocation subfield value changes, the number of user fields in the user-specific fields within the EHT-SIG content channel corresponding to the RU Allocation subfield changes accordingly.

[0355] In addition, the RU Allocation subfield of a RU or MRU may be represented by a value in the range of 304 to 927 (00100110y2y1y0 to 1110011y2y1y0 in binary representation), where y2y1y0 indicates the number of user fields in the corresponding content channel.

[0356] Additionally, the remaining resources (304-463) in the RU Allocation subfield currently specify MRU modes corresponding to a 640 MHz bandwidth (e.g., MRU pattern #1). See Table 1 for details. Furthermore, extended resources (512-927) indicate MRU modes corresponding to a 640 MHz bandwidth (e.g., MRU pattern #2, which is an additional MRU mode compared to MRU pattern #1).

[0357] It should be noted that the communication methods shown in Figures 9 and 16 can be implemented independently. For example, a broadband MRU mode may be defined according to the method shown in Figure 9. How a newly defined MRU mode is indicated is not limited to the MRU instruction solution shown in Figure 16, or it may be a different MRU instruction solution. In another example, a newly added MRU mode is indicated according to the method described in Figure 16. The newly added MRU mode may not be an MRU mode defined in Figure 9, but an MRU mode not indicated by the RU Allocation subfield in the current protocol.

[0358] Furthermore, the communication methods shown in Figures 9 and 16 may be combined and implemented. For example, a broadband MRU mode may first be defined according to the method described in Figure 9, and then a newly defined broadband MRU mode may be shown according to the method described in Figure 16. Specifically, the cases shown in Methods 3 to 5 can be understood as concrete examples of combining and implementing the communication methods shown in Figures 9 and 16.

[0359] It should be understood that the sequence numbers of the processes described above do not indicate the order of execution. The order of execution of the processes should be determined based on the function and internal logic of the processes and should not constitute any limitation on the implementation processes of the embodiments of this application.

[0360] In the embodiments of this application, unless otherwise specified or unless there is a logical inconsistency, the terminology and / or descriptions in different embodiments are consistent and may be referenced to one another, and the technical features in different embodiments may be combined based on their internal logical relationships to form new embodiments.

[0361] It should be further understood that in some of the embodiments described above, devices within existing network architectures are primarily used as illustrative examples. It should be understood that the specific form of the device is not limited to the embodiments of this application. For example, all devices that may implement the same functionality in the future are applicable to the embodiments of this application.

[0362] In embodiments of the above method, it can be understood that the methods and operations implemented by the device (e.g., AP and STA) may also be implemented by components (e.g., chips or circuits) that can be used within the device.

[0363] In the embodiments of this application, it may be further understood that the interaction between AP and STA is primarily used as an example for illustrative purposes. This application is not limited thereto. AP may be replaced with a transmission end device, and the transmission end device may be a terminal device. STA may be replaced with a receiving end device, and the receiving end device may be a terminal device. For example, "AP" may be read as "first terminal device" and "STA" as "second terminal device".

[0364] It can be further understood that some optional features in embodiments of this application may be independent of other features in some scenarios, or may be combined with other features in some scenarios. This is not limited to this.

[0365] The above describes in detail the communication method provided in the embodiments of this application with reference to Figure 7. The communication method is described primarily in terms of the interaction between a first device and a second device. To implement the functions described above, it may be understood that the first device and the second device include corresponding hardware structures and / or software modules for performing the functions.

[0366] Those skilled in the art will recognize, in combination with the examples described in the embodiments disclosed herein, that the units and algorithmic steps can be implemented by the hardware or a combination of hardware and computer software as described in this application. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may implement the functions described for each specific application using different methods, but such implementations should not be considered to exceed the scope of this application.

[0367] The communication device provided in the embodiments of this application will be described in detail below with reference to Figures 17 to 19. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for details not described in detail, please refer to the method embodiments described above. For brevity, some details of the content will not be described again in this specification.

[0368] In embodiments of this application, the functional modules of a transmission end device or a receiving end device may be divided based on the examples of the methods described above. For example, a functional module may be divided based on its function, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. Note that in embodiments of this application, the module division is merely an example and represents only a logical functional division. Other division methods may be used in actual implementations. An example of each functional module being obtained through division based on its corresponding function is used below for illustrative purposes.

[0369] Figure 17 is a block diagram of a communication device 10 according to one embodiment of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can implement corresponding communication functions. The processing module 12 is configured to perform data processing. In other words, the transceiver module 11 is configured to perform receive and transmit-related operations. The processing module 12 is configured to perform operations other than receive and transmit. The transceiver module 11 may also be referred to as a communication interface or communication unit.

[0370] Optionally, the device 10 may further include a storage module 13. The storage module 13 may be configured to store instructions and / or data. The processing module 12 may read instructions and / or data from the storage module to enable the device to implement the operation of the device in the embodiments of the method described above.

[0371] In the design, the device 10 may correspond to the AP in the embodiment of the method described above, or it may be a component of the AP (e.g., a chip).

[0372] The device 10 can implement the corresponding steps or procedures performed by the AP in the embodiments of the method described above. The transceiver module 11 may be configured to perform the receive and transmit-related operations of the AP in the embodiments of the method described above. The processing module 12 may be configured to perform the processing-related operations of the AP in the embodiments of the method described above.

[0373] In possible implementations, the transceiver module 11 is configured to communicate with a second device based on frequency resources, the frequency resources include multiple resource units (MRUs), the MRUs include k × 996 + m × 484 - tone MRUs, where k is an integer greater than or equal to 4 and m is equal to 0 or 1.

[0374] In other possible implementations, the processing module 12 is configured to generate a PPDU, which includes a resource allocation field indicating the allocation status of the station's frequency resources, and the frequency resources include a multiplexed resource unit (MRU). The transceiver module 11 is configured to transmit the PPDU to the station, and when the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU corresponding to a bandwidth wider than 320 MHz.

[0375] In other possible implementations, the processing module 12 is configured to generate a PPDU, which includes a resource allocation field and a coupling field, the resource allocation field and the coupling field indicating the allocation status of the station's frequency resources, and the transceiver module 11 is configured to transmit the PPDU to the station.

[0376] When the device 10 is configured to perform the method shown in Figure 9, the transceiver module 11 may be configured to perform the steps of receiving and transmitting information in the method, for example, step S920, and the processing module 12 may be configured to perform the processing steps in the method, for example, step S910.

[0377] When the device 10 is configured to perform the method shown in Figure 16, the transceiver module 11 may be configured to perform the steps of receiving and transmitting information in the method, for example, step S1620, and the processing module 12 may be configured to perform the processing steps in the method, for example, step S1610.

[0378] The specific process by which the unit performs the corresponding steps described above is described in detail in the embodiments of the method described above, and for the sake of brevity, please understand that the details will not be described herein.

[0379] In an alternative design, the device 10 may correspond to the STA in the embodiment of the method described above, or it may be a component of the STA (e.g., a chip).

[0380] The device 10 can implement the corresponding steps or procedures performed by the STA in the embodiments of the method described above. The transceiver module 11 may be configured to perform the receive and transmit-related operations of the STA in the embodiments of the method described above. The processing module 12 may be configured to perform the processing-related operations of the STA in the embodiments of the method described above.

[0381] In a possible implementation, the transceiver module 11 is configured to receive a PPDU from an access point, the PPDU including a resource allocation field, which indicates the allocation status of the station's frequency resources, the frequency resources including a multiplexed resource unit (MRU), and the processing module 12 is configured to determine the allocated frequency resources based on resource indication information, and when the value range of the resource allocation field is 304 or greater, the resource allocation field indicates an MRU corresponding to a bandwidth wider than 320 MHz.

[0382] In another possible implementation, the transceiver module 11 is configured to receive a PPDU from the access point, the PPDU including a resource allocation field and a binding field, the resource allocation field and the binding field indicating the allocation status of the station's frequency resources, and the processing module 12 is configured to determine the allocated frequency resources based on the resource instruction information.

[0383] When the device 10 is configured to perform the method shown in Figure 9, the transceiver module 11 may be configured to perform the steps of receiving and transmitting information in the method, for example, step S920, and the processing module 12 may be configured to perform the processing steps in the method.

[0384] When the device 10 is configured to perform the method shown in Figure 16, the transceiver module 11 may be configured to perform the steps of receiving and transmitting information in the method, for example, step S1620, and the processing module 12 may be configured to perform the processing steps in the method, for example, step S1630.

[0385] The specific process by which the unit performs the corresponding steps described above is described in detail in the embodiments of the method described above, and for the sake of brevity, please understand that the details will not be described herein.

[0386] It should be further understood that the apparatus 10 described herein is embodied in the form of a functional module. The term “module” herein may also mean an application-specific integrated circuit (ASIC), an electronic circuit, a processor configured to run one or more software or firmware programs (e.g., a shared processor, a dedicated processor, or a group processor), memory, combinational logic circuits, and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the apparatus 10 may specifically be a mobility management network element in the embodiments described above and may be configured to perform procedures and / or steps corresponding to a mobility management network element in the embodiments of the methods described above. Alternatively, the apparatus 10 may specifically be a terminal device in the embodiments described above and may be configured to perform procedures and / or steps corresponding to a terminal device in the embodiments of the methods described above. To avoid repetition, further details are not described here.

[0387] Apparatus 10 in each of the above-described solutions has the function of implementing the corresponding steps performed by the devices (such as AP and STA) in the above-described method. The function may be implemented by hardware, or by hardware that runs the corresponding software. The hardware or software includes one or more modules corresponding to the above-described function. For example, a transceiver module may be replaced by a transceiver (for example, a transmitting unit in a transceiver module may be replaced by a transmitter, and a receiving unit in a transceiver module may be replaced by a receiver), and other units such as a processing module may be replaced by a processor to separately perform the receiving and transmitting operations and associated processing operations in each embodiment of the method.

[0388] In addition, the transceiver module 11 may alternatively be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing module may be a processing circuit.

[0389] Figure 18 is a diagram of another communication device 20 according to one embodiment of the present application. The device 20 includes a processor 21. The processor 21 is configured to execute computer programs or instructions stored in memory 22, or to read data / signaling stored in memory 22, in order to perform the method in the embodiment of the method described above. Optionally, there may be one or more processors 21.

[0390] Optionally, as shown in Figure 18, the device 20 further includes a memory 22, which is configured to store computer programs or instructions and / or data. The memory 22 may be integrated with the processor 21 or located separately. Optionally, one or more memories 22 may be present.

[0391] Optionally, the device 20 further includes a transceiver 23, as shown in Figure 18. The transceiver 23 is configured to receive and / or transmit signals. For example, the processor 21 is configured to control the transceiver 23 to receive and / or transmit signals.

[0392] In the solution, the device 20 is configured to implement the operations performed by AP and STA in the embodiment of the method.

[0393] It should be understood that the processor in this embodiment of the present application may be a central processing unit (CPU), or another general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA), or another programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.

[0394] It should be further understood that the memory referred to in this embodiment of the present application may be volatile memory and / or non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM). For example, RAM may be used as an external cache. As an example, rather than an exhaustive list, RAM includes multiple forms such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM).

[0395] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, memory (storage module) may be integrated into the processor.

[0396] The memory described herein includes, but is not limited to, these memories and any other suitable types of memory.

[0397] Figure 19 is a diagram of a chip system 30 according to one embodiment of the present application. The chip system 30 (sometimes referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0398] The logic circuit 31 may be a processing circuit within the chip system 30. The logic circuit 31 may be coupled to a memory unit and call instructions within the memory unit, thereby enabling the chip system 30 to implement the methods and functions of the embodiments of this application. The input / output interface 32 may also be an input / output circuit within the chip system 30, which outputs information processed by the chip system 30 or inputs data or signaling information to be processed into the chip system 30 for processing.

[0399] In the solution, the chip system 30 is configured to implement the operations performed by AP and STA in an embodiment of the method.

[0400] For example, the logic circuit 31 is configured to implement processing-related operations performed by the AP and STA in the embodiment of the method described above, and the input / output interface 32 is configured to implement transmission and / or reception-related operations performed by the terminal device in the embodiment of the method described above.

[0401] One embodiment of this application further provides a computer-readable storage medium that stores computer instructions for implementing a method performed by the device in the embodiment of the method described above.

[0402] For example, when a computer program is executed by a computer, the computer can implement the method executed by AP and STA in an embodiment of the method.

[0403] One embodiment of this application further provides a computer program product including instructions. When the instructions are executed by a computer, an embodiment of the method implements a method executed by AP and STA.

[0404] One embodiment of this application further provides a communication system including AP and STA.

[0405] For a description of the relevant aspects and beneficial effects of any of the devices provided above, please refer to the corresponding embodiments of the methods provided above. Further details are not provided here.

[0406] In the various embodiments provided in this application, it should be understood that the disclosed apparatus and methods may be implemented in other ways. For example, the embodiments of the described apparatus are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementations. 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, direct coupling, or communication connection shown or described may be implemented through some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented in electronic, mechanical, or other forms.

[0407] All or part of the embodiments described above may be implemented using software, hardware, firmware, or any combination thereof. If software is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded into a computer and executed, all or part of the procedures or functions according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable device. For example, the computer may be a personal computer, a server, or a network device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave). Computer-readable storage media can be any available medium accessible by a computer, or a data storage device such as a server or data center that integrates one or more available media. Available media can be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), semiconductor media (e.g., solid-state disks, SSDs), etc. For example, available media may include, but are not limited to, any medium capable of storing program code, such as USB flash drives, removable hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0408] The above description merely outlines a specific implementation of the present application and is not intended to limit the scope of protection. Any modification or substitution readily understood by a person skilled in the art within the technical scope disclosed herein shall fall within the scope of protection. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims. [Explanation of Symbols]

[0409] 10 equipment 11 Transceiver Modules 12 Processing Modules 13 Memory Modules 20 equipment 21 processors 22 memory 23 transceivers 30 Chip System 31 Logic Circuits 32 Input / Output Interfaces

Claims

1. A method of communication, A first device communicates with a second device based on frequency resources, wherein the frequency resources include a multiplexed resource unit (MRU). The aforementioned MRU includes k × 996 + m × 484 tone MRU, where k is an integer greater than or equal to 4 and m is equal to 0 or 1.

2. The method according to claim 1, wherein the frequency resource further comprises a resource unit RU, the RU comprising at least one of a 484-tone RU, a 996-tone RU, a 2×996-tone RU, and a 4×996-tone RU.

3. The aforementioned MRU is part of the frequency resources within the 640 MHz bandwidth. The aforementioned MRU is, The method according to claim 1 or 2, comprising at least one of 7×996 tone MRU, 6×996 tone MRU, 5×996 tone MRU, 7×996+484 tone MRU, 6×996+484 tone MRU, 5×996+484 tone MRU, and 4×996+484 tone MRU.

4. If the 40 MHz subchannel is not punctured within the 640 MHz bandwidth, the MRU includes at least one of the 7×996 tone MRU, the 6×996 tone MRU, and the 5×996 tone MRU, or The method according to claim 3, wherein if the punctured subchannel within the 640 MHz bandwidth includes one 40 MHz subchannel, the MRU includes at least one of the 7 × 996 + 484 tone MRU, the 6 × 996 + 484 tone MRU, the 5 × 996 + 484 tone MRU, and the 4 × 996 + 484 tone MRU.

5. If one 80 MHz subchannel is punctured within the 640 MHz bandwidth, the MRU includes the 7 × 996 tone MRU, If one 160 MHz subchannel is punctured within the 640 MHz bandwidth, the MRU includes the 6 × 996 tone MRU, If one 160 MHz subchannel and one 80 MHz subchannel are punctured within the 640 MHz bandwidth, the MRU includes the 5 × 996 tone MRU, and the punctured 160 MHz subchannel is 160 MHz having the lowest or highest frequency within the 640 MHz bandwidth. If one 40 MHz subchannel is punctured within the 640 MHz bandwidth, the MRU includes the 7 × 996 + 484 tone MRUs. If one 80 MHz subchannel and one 40 MHz subchannel are punctured within the 640 MHz bandwidth, the MRU includes the 6 × 996 + 484 tone MRU, and the punctured 80 MHz subchannel is 80 MHz having the lowest or highest frequency within the 640 MHz bandwidth. If one 160 MHz subchannel and one 40 MHz subchannel are punctured within the 640 MHz bandwidth, the MRU includes the 5 × 996 + 484 tone MRU, and the punctured 160 MHz subchannel is 160 MHz having the lowest or highest frequency within the 640 MHz bandwidth, or The method according to claim 4, wherein if one 160 MHz subchannel, one 80 MHz subchannel, and one 40 MHz subchannel are punctured within the 640 MHz bandwidth, the MRU includes the 4 × 996 + 484 tone MRU, the punctured 160 MHz subchannel is 160 MHz having the lowest or highest frequency within the 640 MHz bandwidth, and the punctured 80 MHz subchannel is 80 MHz having the lowest or highest frequency within the remaining 480 MHz bandwidth after the 160 MHz subchannel has been punctured within the 640 MHz bandwidth.

6. The aforementioned MRU is part of the frequency resources within the 480 MHz bandwidth. The method according to claim 1 or 2, wherein the MRU includes at least one of 5 × 996 + 484 tone MRU, 5 × 996 tone MRU, 4 × 996 + 484 tone MRU, and 4 × 996 tone MRU.

7. If the MRU corresponding to the 480 MHz bandwidth reuses the MRU corresponding to the 640 MHz bandwidth, the MRU corresponding to the 480 MHz bandwidth includes at least one of the 5×996+484 tone MRU, 5×996 tone MRU, and 4×996+484 tone MRU of the 480 MHz bandwidth, or The method according to claim 6, wherein if the MRU corresponding to the 480 MHz bandwidth does not reuse any portion of the MRU within the 640 MHz bandwidth, the MRU corresponding to the 640 MHz bandwidth is generated for the 480 MHz physical layer protocol data unit PPDU.

8. If one 40 MHz subchannel is punctured within the 480 MHz bandwidth, the MRU includes the 5 × 996 + 484 tone MRUs. If one 80 MHz subchannel is punctured within the 480 MHz bandwidth, the MRU includes the 5 × 996 tone MRU, One 80 MHz subchannel and one 40 MHz subchannel are punctured within the 480 MHz bandwidth, the MRU includes the 4 × 996 + 484 tone MRU, and the punctured 80 MHz subchannel is 80 MHz having the lowest or highest frequency within the 480 MHz bandwidth, or The method according to claim 7, wherein if one 160 MHz subchannel is punctured within the 480 MHz bandwidth, the MRU includes the 4 × 996 tone MRU.

9. The aforementioned method, The first device further includes the step of determining the frequency resource based on a resource allocation field, wherein the resource allocation field includes information indicating the MRU, The method according to any one of claims 1 to 8, wherein when the value range of the resource allocation field is 304 or greater, the resource allocation field indicates the MRU.

10. The method according to claim 9, wherein, if the range of the value of the resource allocation field is 0 or more and 303 or less, the resource allocation field indicates an MRU corresponding to a bandwidth of 320 MHz or less.

11. The resource allocation field further includes information indicating the resource unit RU, The method according to claim 9 or 10, wherein if the range of values ​​in the resource allocation field is 304 or greater, the resource allocation field indicates the RU, and the RU includes at least one of the 484 tone RU, the 996 tone RU, the 2 × 996 tone RU, and the 4 × 996 tone RU.

12. The method according to any one of claims 9 to 11, wherein the resource allocation field is X bits, where X is an integer greater than or equal to 9.

13. The aforementioned frequency resources are a portion of the frequency resources within a 2 × P MHz bandwidth, where P is greater than 160. The method according to any one of claims 1 to 8, further comprising the step of determining the frequency resource based on a resource allocation field and a coupling field using the first device.

14. The method according to claim 13, wherein the resource allocation field includes information indicating the MRU corresponding to the P MHz bandwidth, and the coupling field indicates whether a first resource block to the left of the DC subcarrier in the 2 × P MHz is coupled with a second resource block to the right of the DC subcarrier.

15. If the join field indicates that the first resource block and the second resource block are not joined, then the first resource block and the second resource block are assigned separately to different stations, or The method according to claim 13 or 14, wherein if the join field indicates that the first resource block and the second resource block are joined, the first resource block and the second resource block are assigned to the same station.

16. The first resource block is, The first adjacent RU to the left of the DC subcarrier within the bandwidth, the first adjacent MRU to the left of the DC subcarrier within the bandwidth, the second adjacent RU to the left of the DC subcarrier within the bandwidth, or the second adjacent MRU to the left of the DC subcarrier within the bandwidth, The aforementioned second resource block is, The method according to claim 14 or 15, comprising any one of the following: the first adjacent RU to the right of the DC subcarrier within the bandwidth, the first adjacent MRU to the right of the DC subcarrier within the bandwidth, the second adjacent RU to the right of the DC subcarrier within the bandwidth, or the second adjacent MRU to the right of the DC subcarrier within the bandwidth.

17. A communication device comprising a processor configured to read instructions stored in memory, wherein when the processor executes the instructions, the packet transmission device becomes capable of implementing the method according to any one of claims 1 to 16.

18. A chip comprising at least one processing core configured to perform the method described in any one of claims 1 to 16.

19. A terminal device comprising the chip described in claim 18.

20. A computer program product, wherein the computer program product includes computer program code, and when the computer program code is executed on a computer, the method according to any one of claims 1 to 16 is executed.

21. A computer-readable storage medium containing a computer program, wherein when the computer program is executed on a computer device, a processing module within the computer device is capable of performing the method according to any one of claims 1 to 16.

22. A communication system comprising: a first device configured to perform the method described in any one of claims 1 to 16; and a second device configured to communicate with the first device.

Images