Information instruction method and communication device

Abstract

To provide an information instruction method, specifically in the field of wireless fidelity technology.SOLUTION: The method includes an access point (AP) determining resource instruction information and transmitting the resource instruction information. The resource instruction information includes a plurality of bit sequences. A first bit sequence in the plurality of bit sequences corresponds to a first resource unit. The first resource unit is a resource unit in a resource block set that is allocated to a first station (STA) or a plurality of STAs. The resource block set includes at least two resource units. The method provided in an embodiment of the present application is used for two content channels to transmit HE-SIGNAL B in order to indicate that the plurality of resource units are allocated to one or more stations, for the purpose of reducing a signaling overhead.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] This application claims the priority of Chinese Patent Application No. 202010028819.4, titled "Information Indication Method and Communication Device", filed with the China National Intellectual Property Administration on January 11, 2020, and further claims the priority of Chinese Patent Application No. 202010172693.8, titled "Information Indication Method and Communication Device", filed with the China National Intellectual Property Administration on March 12, 2020. The entire content of the above applications is incorporated herein by reference in its entirety.

[0002] This application relates to the field of wireless fidelity technology, and in particular, to an information indication method and a communication device.

Background Art

[0003] To support orthogonal frequency division multiple access (OFDMA) transmission, the frequency band resources are divided into several resource units in 802.11ax, and each station or each group of stations can perform transmission with only one of the resource units. In other words, currently supported is that only one resource unit is allocated to one station or multiple users. However, in the future, it may be supported that multiple resource units are allocated to one or more stations. How to allocate multiple resource units to one or more stations is a problem to be solved currently.

Summary of the Invention

Means for Solving the Problems

[0004] This application provides an information indication method and a communication device. To reduce signaling overhead, two content channels are used to transmit HE-SIG B for indicating that multiple resource units are allocated to one or more stations.

[0005] According to the first embodiment, an information indicating method is provided. The method includes the following:

[0006] An access point (AP) determines resource instruction information. This resource instruction information includes multiple bit sequences. The first bit sequence in these multiple bit sequences corresponds to a first resource unit. The first resource unit is a resource unit within a resource block set assigned to a first station (STA) or multiple STAs. A resource block set contains at least two resource units.

[0007] The AP (Application Programmer) detects resource instruction information.

[0008] For resource instruction information in the first embodiment, which is optional, please refer to the implementation of resource instruction information in a specific embodiment.

[0009] According to a second embodiment, an information indicating method is provided. The method includes the following:

[0010] An access point (AP) generates a first instruction. This first instruction is used to indicate that multiple stations (STAs) will perform multi-use multiple input multiple output (MU-MIMO) transmission across discontinuous bandwidths.

[0011] AP transmits the first instruction information.

[0012] For the first instruction information in the second embodiment, which is optional, please refer to the implementation of the instruction information in the specific embodiment.

[0013] According to a third aspect, a communication device is provided. The communication device includes a module configured to perform a method relating to the first aspect or any one of possible implementations of the first aspect, or the communication device includes a module configured to perform a method relating to the second aspect or any one of possible implementations of the second aspect.

[0014] According to a fourth aspect, one embodiment of the present application provides a computer-readable storage medium configured to store a computer program, the computer program including instructions for performing either the first aspect or a possible implementation of the first aspect, or instructions for performing either the second aspect or a possible implementation of the second aspect.

[0015] According to a fifth aspect, one embodiment of the present application provides a computer program, which includes instructions for performing either the first aspect or a possible implementation of the first aspect, or instructions for performing either the second aspect or a possible implementation of the second aspect.

[0016] According to a sixth aspect, one embodiment of this application provides a communication system, which includes communication devices and stations provided in a third aspect. [Brief explanation of the drawing]

[0017] [Figure 1] This invention illustrates a network architecture for a wireless local area network to which one embodiment may be applied. [Figure 2] This is a diagram showing the internal structure of an access point and station according to one embodiment of this application. [Figure 3] This is another diagram showing the internal structure of an access point and station according to one embodiment of this application. [Figure 4] This shows 80M multi-user puncturing mode 1 in 802.11ax. [Figure 5]Shows the 80M multi-user puncturing mode 2 in 802.11ax. [Figure 6] Shows the 160M multi-user puncturing mode 1 in 802.11ax. [Figure 7] Shows the 160M multi-user puncturing mode 2 in 802.11ax. [Figure 8] It is a schematic diagram of the frame structure of the HE MU PPDU according to an embodiment of this application. [Figure 9] It is a schematic diagram of the structure of HE-SIG-B according to an embodiment of this application. [Figure 10] It is a schematic diagram of the frame structure of the 40MHz HE-SIG-B according to an embodiment of this application. [Figure 11] It is a schematic diagram of the frame structure of the EHT PPDU according to an embodiment of this application. [Figure 12] It is a schematic diagram of resource partitioning for allocating an 80MHz spectrum bandwidth to one user according to an embodiment of this application. [Figure 13] It is a schematic flowchart of a single-user punctured transmission method according to an embodiment of this application. [Figure 14] ]>It is a schematic diagram of resource partitioning for allocating an 80MHz spectrum bandwidth to four users according to an embodiment of this application. [Figure 15] It is a schematic flowchart of a full-bandwidth MU-MIMO punctured transmission method according to an embodiment of this application. [Figure 16] It is a schematic diagram of the overlap between resource units assigned to different users according to an embodiment of this application. [Figure 17] It is a schematic diagram of resource partitioning for allocating a 160MHz spectrum bandwidth to two users according to an embodiment of this application. [Figure 18] It is a schematic diagram of resource partitioning for allocating a 160MHz spectrum bandwidth to five users according to an embodiment of this application. [Figure 19]This is a schematic diagram of the frame structure of a trigger frame according to one embodiment of this application. [Figure 20] This is a schematic diagram of the structure of a user information field in a trigger frame according to one embodiment of this application. [Figure 21] This is a schematic flowchart of an uplink full-bandwidth MU-MIMO punctured transmission method according to one embodiment of this application. [Figure 22] This is a schematic diagram of the structure of AP according to one embodiment of this application. [Modes for carrying out the invention]

[0018] To further clarify the purpose, technical solutions, and advantages of the embodiments of this application, the embodiments of this application will be described in more detail below with reference to the accompanying drawings.

[0019] Embodiments of this application may be applied to wireless local area network (WLAN) scenarios, or to IEEE 802.11 system standards, such as IEEE 802.11ax standards, or next-generation standards or further next-generation standards. Alternatively, embodiments of this application may be applied to wireless local area network systems, such as the Internet of Things (IoT) or the Vehicle to X (V2X). Indeed, embodiments of this application may be further applied to other conceivable communication systems, such as global system for mobile communications (GSM), code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA®) systems, general packet radio service (GPRS), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, and future 5G communication systems.

[0020] For example, Figure 1 is a diagram of a WLAN network architecture to which one embodiment of this application is applicable. Figure 1 uses an example in which the WLAN includes one AP and STA1 and STA2 associated with the AP. The AP can schedule radio resources for STA1 and STA2 and transmit data for STA1 and STA2 using the scheduled radio resources. The data includes uplink data information and / or downlink data information. It should be understood that the number of APs and STAs in Figure 1 is merely an example. There may be more or fewer APs and STAs. An AP may communicate with STA1 or STA2, or with STA1 and STA2. If the WLAN includes multiple APs and multiple STAs, it should be understood that this embodiment of this application is also applicable to communication between APs. For example, APs can communicate with each other by using a distributed system (DS). Any AP can schedule radio resources for STAs associated with the AP and / or STAs not associated with the AP and transmit data for STAs using the scheduled radio resources. This embodiment of this application is also applicable to communication between STAs.

[0021] In this embodiment of this application, the Station (STA) may be various user terminals, user equipment, access devices, subscriber stations, subscriber units, mobile stations, user agents, user devices, etc., having wireless communication capabilities. User terminals may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem having wireless communication capabilities, and various forms of user equipment (UE), mobile stations (MS), terminals, terminal equipment, portable communication devices, handheld devices, portable computing devices, entertainment devices, game devices or systems, global positioning system devices, or any other suitable devices configured to perform network communication by using a wireless medium. For ease of explanation, in this specification, the aforementioned devices are collectively referred to as Stations or STAs. In this embodiment of this application, the Access Point (AP) is a device deployed in a wireless communication network and providing wireless communication capabilities to an STA associated with the AP. The Access Point (AP) may be used as a hub in a communication system. The AP may be a communication device such as a base station, router, gateway, repeater, communication server, switch, or bridge. Base stations may include various forms of macro base stations, micro base stations, relay stations, etc. For the sake of simplicity, in this specification, the aforementioned devices are collectively referred to as access points (APs).

[0022] Specifically, the AP and STA in this application may be APs and STAs to which the IEEE 802.11 system standard is applicable. Figure 2 is a diagram of the internal structure of an AP and STA according to one embodiment of this application. The 802.11 system standard primarily focuses on the physical layer (PHY) and media access control (MAC) portions of 802.11. Therefore, the STA provided in this embodiment of this application is generally a terminal product that supports the MAC layer and PHY layer of the 802.11 system standard, such as a mobile phone or notebook computer. Figure 2 is a diagram of the structure of a multi-antenna AP and a single-antenna STA, but it should be noted that in actual scenarios, the AP and STA may each include multiple antennas, and each may be a device having three or more antennas.

[0023] Figure 3 is another diagram of the internal structure of AP and STA according to one embodiment of this application. AP and STA each include, at the lowest layer, a PHY baseband module, a MAC layer module, a logical link control (LLC) layer module, and a radio frequency module, i.e., an antenna, and at the upper layer, an Internet Protocol (IP) processing module, a transmission control protocol (TCP) / user datagram protocol (UDP) processing module, and an application layer module. Information transmission between the lowest and upper layers is achieved using an upper-layer interface.

[0024] The AP communicates with the STA. The AP can allocate resources to the STA. The STA performs data transmission on the allocated resources. For example, the Wi-Fi protocol preceding 802.11ax, for example 802.11ac, requires that transmissions must occupy adjacent bandwidths, including four types of bandwidths: 20MHz, 40MHz, 80MHz, and 160MHz. One 20MHz is designated as the primary 20MHz. If a 20MHz within a bandwidth is occupied by a transmission from another station, the PPDU transmission bandwidth must be reduced. The reduced bandwidth must include the primary 20MHz. All other 20MHz adjacent to the primary 20MHz are idle and available. For example, in an adjacent 80MHz bandwidth, the first 20MHz is the primary 20MHz, but the second 20MHz channel is busy. In this case, according to the requirements of the adjacent bandwidths, only the PPDU on the primary 20MHz can be transmitted, i.e., the idle 40MHz is wasted in the 80MHz bandwidth.

[0025] To aggregate more channels and create a larger available bandwidth, the 802.11ax protocol proposes a preamble punctured transmission scheme. Discontinuous channels can be aggregated together. In the example above, the access point is made capable of transmitting a 20MHz + 40MHz PPDU to use idle channels more efficiently. Specifically, in the four types of transmission bandwidths defined in the 802.11ax standard, the preamble punctured transmission scheme can only be implemented in the 80MHz and 160MHz bandwidths of the four types of transmission bandwidths. The four preamble punctured transmission schemes proposed in 802.11ax are described individually below.

[0026] The 80MHz bandwidth includes a primary 20MHz P20, a secondary 20MHz S20, and a secondary 40MHz S40. Here, S40 is further divided into S40-L (left 20MHz in S40) and S40-R (right 20MHz in S40). Preamble punctured transmission schemes corresponding to 80MHz are shown in Figures 4 and 5. In Figure 4, only S20 is punctured in the 80MHz bandwidth. In Figure 5, only one 20MHz in S40 is punctured in the 80MHz bandwidth.

[0027] The 160MHz bandwidth includes a primary 20MHz P20, a secondary 20MHz S20, a secondary 40MHz S40, and a secondary 80MHz S80. Here, S40 is further divided into S40-L and S40-R. The preamble puncture schemes corresponding to 160MHz are shown in Figures 6 and 7. In Figure 6, in the 160MHz bandwidth, only S20 may be punctured in the primary 80MHz (including P20, S20, and S40), and 20MHz may be punctured in the secondary 80MHz. This is shown using the HE-SIG-B field in 802.11ax. In Figure 7, in the 160MHz bandwidth, the primary 40MHz (including P20 and S20) of the primary 80MHz (including P20, S20, and S40) is not punctured, and 20MHz may be punctured in the secondary 40MHz and secondary 80MHz. This is demonstrated using the HE-SIG-B field in 802.11ax.

[0028] Two preamble punctured transmission modes for the 80 MHz bandwidth and two preamble punctured transmission modes for the 160 MHz bandwidth in 802.11ax can be indicated using indication information. This indication information is located in the high efficiency signal A (HE-SIG-A) field of the PPDU preamble in 802.11ax. It should be noted that neither the second preamble puncturing mode for the 80 MHz bandwidth nor the two preamble puncturing modes for the 160 MHz bandwidth can specifically indicate a particular punctured 20 MHz. The receiving end needs to further analyze the resource allocation indication information within the common information portion of the following field, i.e., the HE-SIG-B field of the HE PPDU preamble in 802.11ax. HE-SIG-B is primarily used to perform downlink multi-user transmissions, including OFDMA and MU-MIMO, for multiple stations, providing resource unit allocation information and station transmission parameters. In other words, the preamble punctured transmission method in 802.11ax is only applicable to multi-user transmissions.

[0029] Figure 8 shows the multi-user frame format proposed in the 802.11ax protocol, namely the high-efficiency multi-user physical protocol data unit (HE MU PPDU). The frame format consists of three parts: the legacy preamble (L-preamble), the high-efficiency preamble (HE-preamble), and the physical layer convergence protocol service data unit (PSDU). The HE preamble further includes fields such as the repeated legacy signal (RL-SIG), HE-SIG-A, high-efficiency signal B (HE-SIG-B), high-efficiency short training field (HE-STF), and high-efficiency long training field (HE-LTF).

[0030] Figure 9 shows the HE-SIG B field format proposed in the 802.11ax protocol. HE-SIG B is divided into two parts. The first part is the common field, which includes 1 to N resource unit allocation subfields (RU Allocation subfields), a Center 26-Tone resource unit instruction field for bandwidths of 80 MHz or more, a Cyclic Redundancy Code (CRC) used for checking, and a Tail subfield used for cyclic recovery. In addition, there are User Specific fields, which include 1 to M user fields in the resource unit allocation sequence. Here, generally, every other set of M user fields is in a group, followed by one CRC and one tail field, except for the last group. The last group can contain one or two user fields. Therefore, user fields in the last group are indicated using dashed lines. A Padding field may follow the tail field after the last group of user fields.

[0031] The AP can append resource allocation information to HE-SIG-B to indicate the RUs assigned to the STA. When orthogonal frequency division multiple access (OFDMA) and multiple user multiple input multiple output (MU-MIMO) technologies are applied, the spectral bandwidth is divided into several resource units (RUs) in the WLAN protocol. The IEEE 802.11ax protocol specifies that the spectral bandwidth can be divided into several types of RUs for 20MHz, 40MHz, 80MHz, and 160MHz, including 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs (the largest RU in a 20MHz bandwidth), 484-tone RUs (the largest RU in a 40MHz bandwidth), 996-tone RUs (the largest RU in an 80MHz bandwidth), and 2*996-tone RUs (the largest RU in a 160MHz bandwidth). Each RU contains a continuous tone. For example, a 26-tone RU is an RU containing 26 continuous tones. The spectral bandwidth resource division is represented using one or more 8-bit sequences, where each 8-bit corresponds to one 20 MHz in the spectral bandwidth.

[0032] For example, in the 802.11ax protocol, the index table for the resource unit allocation subfield is shown in Table 1. Because the index table is used to indicate allocated resources, it is sometimes called the resource allocation information table.

[0033] [Table 1A] [Table 1B]

[0034] The concept of Content Channel (CC) is further introduced in the 802.11ax protocol. When the bandwidth is only 20 MHz, HE-SIG-B includes only one CC. The CC includes one Resource Unit Allocation subfield used to indicate the RU allocated at 20 MHz. The Resource Unit Allocation subfield occupies 8 bits which can be used to indicate all possible RU permutations and combinations within the 20 MHz bandwidth in an indexed manner. For RUs whose size is 106 tone RUs or more, the number of users or the number of user information fields in the RU's SU / MU-MIMO transmission, e.g., the character x or y in Table 1, must be further indicated. For further details, see the 802.11ax protocol.

[0035] When the transmit bandwidth is greater than 20 MHz, the RL-SIG field and HE-SIG-A field in the L-preamble and HE-preamble are transmitted repeatedly every 20 MHz, and HE-SIG B uses the "1212" transmission method. That is, HE-SIG B contains two CCs. One CC is transmitted every odd-numbered 20 MHz in the transmit bandwidth. The CC contains resource allocation information for the odd-numbered 20 MHz subchannels and station information transmitted on the odd-numbered 20 MHz subchannels. The other CC is transmitted every even-numbered 20 MHz in the transmit bandwidth. The other CC contains resource allocation information for the even-numbered 20 MHz subchannels and station information transmitted on the even-numbered 20 MHz subchannels. It should be understood that the contents of the resource unit allocation subfield are partially displayed in each of the two CCs. By reading the two CCs, the STA can know the RU to be obtained after dividing the spectral bandwidth resources.

[0036] For example, Figure 10 shows the structure of a 40MHz HE-SIG-B. When the bandwidth is 40MHz, there are two CCs, CC1 and CC2. CC1 includes a resource unit allocation subfield for a range that includes odd-numbered 20MHz (i.e., the first 20MHz) and a corresponding user-specific field. CC2 includes a resource unit allocation subfield for a range that includes even-numbered 20MHz (i.e., the second 20MHz) and a corresponding user-specific field.

[0037] In another example, when the bandwidth is 80 MHz, there are also two CCs. The two CCs are CC1 and CC2. CC1 includes a resource unit allocation subfield within the range of odd-numbered 242 tone RUs (i.e., the first 20 MHz and the third 20 MHz) and the corresponding user-specific field. CC2 includes a resource unit allocation subfield within the range of even-numbered 242 tone RUs (i.e., the second 20 MHz and the fourth 20 MHz) and the corresponding user-specific field.

[0038] While multiple RU allocation modes are configured for the resource unit allocation subfield shown in Table 1, a maximum allocation of 160 MHz is supported, and in the future, larger bandwidths, such as 320 MHz, may be supported. Currently, the 802.11ax protocol does not define all possible RU permutations and combinations at 320 MHz and does not have an allocation instruction scheme for the 320 MHz bandwidth.

[0039] In addition, to reduce the complexity of transmission and reception, OFDMA transmission may allocate only one resource block to each station or each group of stations for information transmission. Here, each group of stations indicates that the group of stations performs MU-MIMO transmission with the corresponding resource block. In other words, the following is currently supported: only one RU is assigned to one user. The following is not supported: multiple RUs are assigned to one user. In the future, it may be supported that multiple RUs are assigned to one user in order to increase spectrum utilization. How to assign multiple RUs to one user is a problem that needs to be solved now.

[0040] In addition, an AP can communicate with a single STA. This is also called single-user transmission. In the 802.11ax protocol, single-user transmission is only supported in adjacent bandwidths. However, to increase spectrum utilization, the next-generation protocol of 802.11ax, such as 802.11be, may support single-user transmission in discontinuous bandwidths. In other words, it may be possible to puncture several subchannels within a bandwidth (e.g., 20 MHz is used as the unit). Similarly, an AP may communicate with multiple STAs. For example, multiple STAs perform full-bandwidth MU-MIMO transmission. However, in the 802.11ax protocol, the 802.11ax protocol is only supported in adjacent bandwidths, and single-user transmission is only supported in adjacent bandwidths. In the future, full-bandwidth MU-MIMO transmission may be supported in discontinuous bandwidths. For single-user punctured transmission and full-bandwidth MU-MIMO transmission, how the AP indicates the RU assigned to the STA is a problem that needs to be resolved now. It should be understood that single-user punctured transmission indicates that one station is performing transmissions across multiple discontinuous RUs. Similarly, full-bandwidth MU-MIMO punctured transmission indicates that a group of stations is performing MU-MIMO transmissions across discontinuous RUs.

[0041] To solve the aforementioned technical problems, one embodiment of this application provides an information indicating method. In this method, the AP can reuse fields in the PPDU preamble to indicate a single-user punctured PPDU or a multi-user punctured PPDU. In addition, the AP reuses bit sequences in the resource allocation information table to indicate that multiple RUs are assigned to one station in a single-user transmission, or that multiple RUs are assigned to one or more stations in a multi-user transmission. Compared to the MU punctured transmission method in 802.11ax, this application can reduce signaling overhead.

[0042] Hereinafter, with reference to the attached drawings, the single-user punctured transmission method and the full-bandwidth MU-MIMO punctured transmission method according to the embodiments of this application will be described individually.

[0043] In the current 802.11ax standard, single-user transmission and full-bandwidth MU-MIMO transmission are only supported on adjacent bandwidths. In other words, subchannels within a bandwidth are not punctured. However, to increase spectrum utilization, next-generation protocols of 802.11ax, such as the 802.11be standard, may support single-user punctured transmission and full-bandwidth MU-MIMO punctured transmission. In other words, single-user and multi-user transmissions in full-bandwidth MU-MIMO will be able to perform transmissions on punctured bandwidths.

[0044] Therefore, in this embodiment of the application, when the AP needs to perform a downlink single-user punctured transmission, it is further necessary to indicate whether the PPDU to be transmitted is a single-user punctured PPDU or a multi-user punctured PPDU. Similarly, when the AP needs to perform a downlink full-bandwidth MU-MIMO transmission, it is further necessary to indicate whether the PPDU should be transmitted by a full-bandwidth MU-MIMO punctured transmission.

[0045] Specifically, in this embodiment of the application, the first instruction information can be used to inform the STA whether the PPDU to be transmitted is a single-user punctured PPDU or a multi-user punctured PPDU, which can be considered to be in different transmission modes. It can be understood that a single-user punctured PPDU is in a first transmission mode, and a multi-user punctured PPDU is in a second transmission mode. In this case, the first instruction information can be used to indicate the first and second transmission modes. Specifically, the instruction information can be conveyed in one or more fields of the PPDU. Below, a possible structure of a PPDU is used as an example to illustrate some implementations of the first instruction information.

[0046] In another embodiment of this application, the first instruction information may be used to inform the STA that the PPDU should be transmitted by single-user full-bandwidth transmission, single-user full-bandwidth punctured transmission, full-bandwidth MU-MIMO transmission, full-bandwidth MU-MIMO punctured transmission, or OFDMA transmission. MU-MIMO transmission is also permitted with respect to resource blocks in OFDMA transmission. Resource blocks in OFDMA transmission can also be punctured.

[0047] Optionally, single-user full-bandwidth punctured transmission and full-bandwidth MU-MIMO punctured transmission may be combined with Mode A. In this mode, the EHT signal field includes information about resource allocation, such as information about puncturing. This is specifically mentioned in Solution (4).

[0048] Optionally, full-bandwidth MU-MIMO transmission and OFDMA transmission may be combined in mode B. In this mode, whether the EHT signal field contains resource allocation information, such as RU resource allocation information, is further determined using another field, such as the compression mode indicator field in 802.11ax. An EHT signal field that does not contain resource allocation-related information may be used for full-bandwidth MU-MIMO transmission and optionally for single-user transmission. An EHT signal field that contains resource allocation-related information may be used for OFDMA transmission and optionally for single-user transmission.

[0049] The PPDU in this embodiment of this application may be an EHT PPDU. Figure 11 shows an example of the frame structure of an EHT PPDU. As shown in Figure 11, an EHT PPDU may include fields such as an L preamble field, a binary phase shift keying (BPSK) symbol field, an extremely high throughput (EHT) signal field, an extremely high throughput short training field (EHT-STF), an extremely high throughput long training field (EHT-LTF), and a data field. The L preamble field may include a legacy signal field (L-STF) and a legacy long training field (L-LTF). The BPSK symbol field may include an L-SIG field, an RL-SIG field, and a U-SIG field.

[0050] In this embodiment of this application, resource indication information used to indicate the RU assigned to the STA may be transmitted in the EHT signal field. The EHT signal field may include a common field and a user-specific field. Resource allocation information may be transmitted in the common field. The station identifier may be transmitted in the user-specific field.

[0051] The U-SIG field may include a version-independent info field and a version-dependent info field. The version-independent info field may include a 3-bit Wi-Fi version field, a 1-bit downlink / uplink field, a BSS color field with at least 6 bits, a TxOP field with at least 7 bits, a CRC field with at least 4 bits, and a 6-bit tail field. Furthermore, the version-independent info field may further include a bandwidth field. The version-dependent info field may include a PPDU format field, and may further include one or more of the following: a modulation coding scheme field, a spatial flow field, a coding field, etc.

[0052] In one implementation of the first instruction information, the first instruction information may be conveyed in one field within the U-SIG field. For simplicity of explanation, in this embodiment of the application, this field is referred to as the first field. The first field may be a predetermined field within the U-SIG field, or it may be a newly added field within the U-SIG field. The first field may occupy two or more bits. For example, if the value of the first field is a first value, e.g., "00", it may indicate a single-user PPDU with no punctures; if the value of the first field is a second value, e.g., "01", it may indicate a single-user PPDU with punctures; if the value of the first field is a third value, e.g., "10", it may indicate a multi-user PPDU with no punctures; or if the value of the first field is a fourth value, e.g., "11", it may indicate a multi-user PPDU with punctures. It should be noted that in this embodiment of this application, the value of the first field may also be understood, in some embodiments, as the value transmitted in the first field.

[0053] For example, the first field may be a predetermined field within the U-SIG field, such as a PPDU format field. If the first field is a newly added field within the U-SIG field, it should be understood that the first field is located before the common field in the EHT signal field.

[0054] In another implementation of the first instruction information, the first instruction information may instead be conveyed by two fields within the U-SIG field. For ease of explanation, in this embodiment of the application, the two fields are referred to as the first field and the second field, respectively. Both the first and second fields may be predetermined fields within the U-SIG field or newly added fields within the U-SIG field. Alternatively, the first field may be a predetermined field within the U-SIG field and the second field may be a newly added field within the U-SIG field. Alternatively, the first field may be a newly added field within the U-SIG field and the second field may be a predetermined field within the U-SIG field. The first field is used to indicate the format of the PPDU to be transmitted, including single-user PPDUs or multi-user PPDUs. The second field is used to indicate whether or not to perform a punctured transmission. For example, the second field occupies one or more bits. If the value of the second field is a first value, e.g., "1", it may indicate puncturing. Correspondingly, if the value of the second field is a second value, for example "0", it can indicate that there is no puncture.

[0055] For example, the first field may be a PPDU format field, and the second field may be a newly added field within the U-SIG field, such as a puncturing field. If the value of the second field indicates puncturing, it should be noted that there is a common field included in the EHT signal field in the PPDU, and the EHT signal field can convey resource allocation information. For example, the EHT signal field may include a resource unit allocation subfield used to convey resource allocation information, or the EHT signal field may include a bitmap, which is used to indicate punctured bandwidth resources. If the value of the second field indicates no puncturing, there may be no common field included in the EHT signal field in the PPDU.

[0056] In another example, the first field is the PPDU format field, and the second field is the bandwidth field. The bandwidth field is used to indicate whether the bandwidth is puncturing mode bandwidth or non-puncturing mode bandwidth.

[0057] For example, in 802.11ax, there are 3 bits to indicate bandwidth. The first four values ​​indicate 20M, adjacent 40M, adjacent 80M, and adjacent 160M. The last four values ​​indicate punctured 80M bandwidth and punctured 160M bandwidth. For example, in 802.11be, the bandwidth field may occupy 4 bits. In other words, the values ​​of the bandwidth field are in [0,15], i.e., 16 values. The first five of the 16 values ​​are used to indicate 20M, adjacent 40M, adjacent 80M, adjacent 160M, and adjacent 320M. Optionally, one value may be included and used to indicate 240M. The unused values ​​of the 16 values ​​each indicate punctured 40M, punctured 80M, punctured 160M, and punctured 320M. For example, the sixth value out of 16 is used to indicate a punctured 40M, and the seventh value is used to indicate a punctured 80M. In this solution, if an 80M single-user punctured PPDU is sent, the PPDU format field will indicate a single-user PPDU, and the value in the bandwidth field will be one of several values ​​indicating a punctured 80M.

[0058] When an AP instructs each STA to transmit data, the AP must notify each STA of the RUs assigned to it by the AP. Specifically, the AP can indicate the RUs assigned to each STA using the bit sequences in Table 1, i.e., the Resource Allocation Information Table. One or more bit sequences indicate that the spectral bandwidth resource is divided into several resource block sets accordingly. A single resource block set may contain one or more resource blocks. The number of bit sequences depends on the bandwidth of the U-SIG field and is equal to bandwidth / 20MHz, where the bandwidth is a multiple of 20MHz. Indivisible bandwidth is described separately. One resource block set is assigned to each STA. Resource blocks include attributes such as size and location. Each resource block set corresponds to one user information field or one group of user information fields. This is similar to the resource unit allocation field and one or more user information fields included in HE-SIG B of 802.11ax. If one resource block set corresponds to one user information field, it indicates that the resource block set is allocated to the user for transmission. If a resource block set corresponds to a group of user information fields, it indicates that the resource block set is allocated to a group of users for transmission. For a group of user information fields, for example, for resource blocks that may be used for MU-MIMO transmission, it should be understood that the number of user information fields included in the group of user information fields is indicated using a resource unit allocation field, e.g., the letters x or y in the table. Details are the same as in 802.11ax. Based on the correspondence between one or more resource block sets and one or more subsequent user information fields obtained by partitioning the bandwidth indicated by one or more resource block allocation fields, a user can know the specific resource block set to which their downlink data will be transmitted, only after receiving the correspondence.

[0059] In this embodiment of this application, a resource allocation information table of the 802.11ax standard may be used. In other words, the bit sequences in Table 1 indicate that one resource block set is allocated to one STA for transmission. A resource block set includes at least two resource units. It should be understood that the bit sequences used in this embodiment of this application may be predetermined bit sequences or undefined bit sequences, i.e., reserved bit sequences, such as "011101 x 1 x 0", "01111 y 2 y 1 y 0", "11011 y 2 y 1 y 0", or "111 x 4 x 3 x 2 x 1 x 0". In the following description, the following example is used. That is, the bit sequences used in this embodiment of this application are the reserved bit sequences in Table 1, and the reserved bit sequences occupy m bits. In the following description, m is 8 or greater.

[0060] The solutions provided in the embodiments of this application will be described separately below using a single-user punctured transmission scenario and a full-bandwidth MU-MIMO punctured transmission scenario.

[0061] One embodiment of this application provides a single-user punctured transmission method. In this method, multiple reserved bit sequences are used to indicate that one resource block set is assigned to one user (STA), i.e., that the transmission is performed with multiple RUs, and the multiple reserved bit sequences may be further used to indicate specific locations where the spectral bandwidth is punctured. One reserved bit sequence corresponds to one RU in one resource block set. Different reserved bit sequences indicate different types of assigned RUs. For example, the value of the reserved bit sequence is a first value to indicate that one RU in the resource block set is a 242-tone RU, the value of the reserved bit sequence is a second value to indicate that one RU in the resource block set is a 484-tone RU, the value of the reserved bit sequence is a third value to indicate that one RU in the resource block set is a 996-tone RU, and so on. It should be understood that 242-tone RUs, 484-tone RUs, and 996-tone RUs can also be considered different types of RUs.

[0062] In Table 1, “01110001” indicates a “242-tone RU null (0 station)” indicated as “242(0)”. In this embodiment of the application, the reserved bit sequence may similarly be indicated as RU(same), where “RU” indicates the type of RU, e.g., a 242-tone RU or a 484-tone RU. Resource blocks conveying the “same” resource unit assignment field and another resource block conveying the “same” resource unit assignment field are assigned to one set of resource blocks. In other words, multiple resource blocks are assigned to one user or one group of users. It should be noted that resource blocks here refer to resource blocks of 242 tone or more. If it is indicated that one set of resource blocks is assigned to one STA, the reserved bit sequence may be indicated as RU(same, 1), where “1” indicates the number of STAs to which the resource block set is assigned for transmission. In a single-user punctured transmission scenario, there is only one STA. For example, in Table 1, the reserved bit sequence is "111 x 4 x 3 x 2 x 1 x 0". In this case, "11100000" can be represented as 242 (same, 1) and "11100001" can be represented as 484 (same, 1).

[0063] To facilitate understanding, with reference to Figure 12, how the reserved bit sequences in Table 1 are used in this embodiment of this application will be described below to show that one resource block set is allocated to one STA (STA1 in Figure 12) for transmission. Figure 12 is a schematic diagram of allocating 80 MHz. For example, the 80 MHz bandwidth can be divided into four subchannels, each of which may be 20 MHz or 242 tone RUs. From left to right, the four subchannels are numbered 1 through 4, and the four subchannels are shown as RU1, RU2, RU3, and RU4, respectively.

[0064] Since the AP allocates 80MHz resources, it should be understood that the HE-SIG-B field in the PPDU contains CC1 and CC2, where CC1 contains two resource unit allocation fields and CC2 contains two resource unit allocation fields. Each of the four resource unit allocation fields conveys one reserved bit sequence.

[0065] For example, multiple RUs assigned to STA by the AP are discontinuous. For instance, the AP assigns RU1, RU3, and RU4 to STA1, i.e., RU2 is punctured in an 80 MHz bandwidth. In other words, in this embodiment of the application, discontinuous bandwidth is supported in a single-user transmit scenario, i.e., approximately 20 MHz of bandwidth can be punctured. In this case, the AP needs to indicate the punctured RU in addition to the multiple RUs used for transmission on STA1.

[0066] In the first example, the reserved bit sequence may be used to indicate the type of each RU included in the allocated resource block set, and the total number of STAs to which multiple RUs are allocated for transmission. Resource allocation information included in the CC may be referred to as RU(same, 1). If a RU is punctured, the resource allocation information included in the CC is indicated as RU(0). For example, in Table 1, "01110001" indicates that a 242-tone RU is punctured and indicated as 242(0).

[0067] For example, in the case of the spectral resources shown in Figure 12, CH1, i.e., the first 242 tone RU, may be represented using 242(same, 1). Similarly, the second 242 tone RU may be represented using 242(0), the third 242 tone RU may be represented using 242(same, 1), and the fourth 242 tone RU may be represented using 242(same, 1). Similarly, for CCs described in the 802.11ax standard, resource allocation information for odd-numbered channels (i.e., the m-bit sequence in the resource allocation table) is set for CC1, and resource allocation information for even-numbered channels is set for CC2. That is, 242(same, 1) is set for CC1 to represent the first 20M, 242(0) is set for CC2 to represent the second 20M, 242(same, 1) is set for CC1 to represent the third 20M, and 242(same, 1) is set for CC2 to represent the fourth 20M. In other words, to indicate that RU1, RU3, and RU4 are assigned to STA1, RU2 is punctured, and RU1, RU3, and RU4 are all 242-tone RUs, the resource allocation information contained in CC1 may be 242(same, 1) + 242(same, 1), and the resource allocation information contained in CC2 may be 242(0) + 242(same, 1).

[0068] As another example, to indicate that RU1, RU3, and RU4 are assigned to STA1, RU2 is punctured, RU1 is a 242-tone RU, and RU3 and RU4 are both 484-tone RUs, the resource assignment information contained in CC1 may be 242(same, 1) + 484(same, 1), and the resource assignment information contained in CC2 may be 242(0) + 484(same, 1). In this example, RU3 and RU4 are contiguous and assigned to STA1 with a granularity of 484 tones. This differs from the previous example. In this design, STA1 receives CC1 and CC2. All assigned RUs can be obtained by interpreting only CC1 or CC2 instead of interpreting both CC1 and CC2.

[0069] In a single-user punctured transmission scenario, it should be understood that the number of STAs to which multiple RUs are allocated for transmission is 1 by default. Therefore, the resource allocation information included in CC1 may be 242 (same) + 242 (same), and the resource allocation information included in CC2 may be 242 (same) + 242 (same). Similarly, the resource allocation information included in CC1 may be 484 (same) + 484 (same), and the resource allocation information included in CC2 may be 484 (same) + 484 (same).

[0070] In a single-user punctured transmission scenario, when sending resource allocation information to the STA, the AP can indicate the receiving address of the receiving end. The receiving address can convey the STA identifier, i.e., the association identifier. Since the STA can determine whether resource instruction information is sent to the STA based on the receiving address, in a conceivable form, CC1 and CC2 do not have to include user information fields corresponding to resource unit allocation fields, or if they do, the included user information fields do not have to include the STA identifier.

[0071] Naturally, in other possible designs, CC1 and CC2 may also include user information fields corresponding to their respective resource unit allocation fields. For example, CC1 includes the user information field of STA1, and CC2 also includes the user information field of STA1. The identifier of STA1 can be conveyed in the user information fields within CC1 and CC2. For example, the resource allocation information contained in CC1 may be 242(same, 1) + 242(same, 1) and the user information field of STA1, and the resource allocation information contained in CC2 may be 242(0) + 242(same, 1) and the user information field of STA1. In this design embodiment, the AP does not append the identifier of STA to the specified receiving address when transmitting resource allocation information, but STA can still determine the RU assigned to STA by the AP by reading the user information fields within CC1 and CC2.

[0072] In another implementation of the first example, the second example may use a reserved bit sequence to indicate the type of each RU and the number of user information fields included in the allocated resource block set. The resource allocation information included in the CC is indicated as RU(same, k), where k is used to indicate the number of user information fields. For example, the value of the reserved bit sequence should be the fourth value to indicate that one RU in the resource block set is a 242-tone RU and the corresponding number of user information fields is a specific value; the value of the reserved bit sequence should be the fifth value to indicate that one RU in the resource block set is a 484-tone RU and the corresponding number of user information fields is a specific value, and so on. For example, the value of the reserved bit sequence should be the fourth value to indicate that one RU in the resource block set is a 242-tone RU and the corresponding number of user information fields is a specific value, e.g., 1. For example, the value of the reserved bit sequence should be the fifth value to indicate that one RU in the resource block set is a 242-tone RU and the corresponding number of user information fields is a specific value, e.g., 2. The value of the received bit sequence is the 12th value to indicate that one RU in the resource block set is a 484-tone RU and the corresponding number in the user information field is a specific value, e.g., 1, and so on.

[0073] For example, to show that RU1, RU3, and RU4 are assigned to STA1 corresponding to the spectral bandwidth shown in Figure 12, the resource allocation information included in CC1 may be 242(same, 1) + 242(same, 0) and the user information field of STA1, and the resource allocation information included in CC2 may be 242(0) + 242(same, 1) and the user information field of STA1. RU2 is punctured. RU1, RU3, and RU4 are all 242-tone RUs. The number of user information fields corresponding to RU1 is 1. The number of user information fields corresponding to RU2 is 0. The number of user information fields corresponding to RU3 is 0. The number of user information fields corresponding to RU4 is 1. Alternatively, to indicate that RU1, RU3, and RU4 are assigned to STA1, the resource allocation information included in CC1 may be 242(same, 0) + 242(same, 1) and the user information field of STA1, and the resource allocation information included in CC2 may be 242(0) + 242(same, 1) and the user information field of STA1. RU2 is punctured. RU1, RU3, and RU4 are all 242-tone RUs. The number of user information fields corresponding to RU1 is 0. The number of user information fields corresponding to RU2 is 1. The number of user information fields corresponding to RU3 is 0. The number of user information fields corresponding to RU4 is 1.

[0074] Alternatively, to indicate that RU1, RU3, and RU4 are assigned to STA1, the resource allocation information included in CC1 may be 242(same, 1) + 484(same, 0) and the user information field of STA1, and the resource allocation information included in CC2 may be 242(0) + 484(same, 1) and the user information field of STA1. RU2 is punctured. RU1 is a 242 tone RU. RU3 and RU4 form a 484 tone RU. The number of user information fields set in CC1 corresponding to RU1 is 1. The number of user information fields set in CC2 corresponding to RU2 is 0. The number of user information fields set in CC1 corresponding to RU3 is 0. The number of user information fields set in CC2 corresponding to RU4 is 1. The user fields may or may not convey the identifier of STA1.

[0075] It should be understood that this embodiment of the application does not limit the specific user information fields that convey the identifier of STA1, provided that STA1 can obtain the identifier of STA1 from CC1 and CC2.

[0076] It should be noted that the allocation of an 80 MHz bandwidth by the AP is used only as an example in the embodiments described above. This embodiment of the application is applicable to other bandwidths, e.g., 40 MHz, 160 MHz, and further, to the 320 MHz bandwidth supported by the next-generation protocol 802.11be, which will be obtained through a gradual change based on the current 802.11ax protocol. The difference lies in the different number of resource allocation information contained in CC1. For example, in the case of 160 MHz, the resource allocation information contained in CC1 may be 242(same, 1)+242(same, 1)+242(same, 1)+242(same, 1), and the resource allocation information contained in CC2 may be 242(same, 1)+242(same, 1)+242(same, 1)+242(same, 1), and so on. Further details are not described here.

[0077] It should be noted that if one or more fields in the preamble indicate a single-user punctured transmission, 242(1) in the table can be reused as a variation of 242(same, 1) to indicate that the RU corresponding to the 242(1) bit sequence is assigned to one STA. Similarly, the variation of 484(same, 1) can be represented as 484(1). Alternatively, 484(1) in the table may be reused to indicate that the RU corresponding to the 484(1) bit sequence is assigned to one STA. Similarly, the following are further included: namely, 996(1) in Table 1 is used to replace 996(same, 1), and the newly added 996*2(1) is used to replace 996*2(same, 1).

[0078] Figure 13 shows a downlink single-user punctured transmission method according to one embodiment of this application. The method may include the following steps:

[0079] S1301.AP generates a PPDU. The PPDU preamble may include a first field and a second field. The first field is used to indicate that the PPDU to be sent is a single-user punctured PPDU. The second field includes multiple resource unit assignment fields. Each resource unit assignment field is used to indicate one RU in a set of resource blocks assigned to the first STA.

[0080] S1302.AP sends the PPDU to the first STA.

[0081] S1303. The first STA receives the PPDU and receives or transmits data information based on the allocated resource block set.

[0082] It should be understood that the first field may be located within the aforementioned U-SIG field. The first field includes one or more subfields used to convey the aforementioned first instruction information. For specific ways in which the first instruction information is added to the U-SIG field, please refer to the description of the embodiments above. Details will not be repeated here. The second field may be a common field in the aforementioned EHT-SIG field. The second field includes multiple resource unit assignment fields. Each resource unit assignment field can convey the aforementioned reserved bit sequence used to indicate one RU in the resource block set assigned to the first STA. Indeed, the puncturing location can also be indicated by using the reserved bit sequence. For specific implementations, please refer to the aforementioned embodiments in a single-user punctured transmission scenario. Details will not be repeated here.

[0083] One embodiment of this application further provides a full-bandwidth MU-MIMO punctured transmission method. In this method, multiple reserved bit sequences are used to indicate that one resource block set (i.e., multiple RUs) is allocated to one group of stations (multiple STAs) for MIMO transmission, and these reserved bit sequences may be further used to indicate specific locations where the frequency bandwidth is punctured. One reserved bit sequence corresponds to one RU in one resource block set. It should be understood that this group of STAs may be STAs performing full-bandwidth MU-MIMO transmission. Similarly, in this scenario, one m bit sequence in the resource allocation information table indicates one RU. The RU is one RU in a resource block set allocated to n STAs and used by n users to perform MU-MIMO transmission. For example, one m bit sequence in the resource allocation information table indicates a 242-tone RU, and the 242-tone RU is allocated to four STAs for MU-MIMO transmission performed by four STAs. For brevity, the m bit sequence is shown as 242(same, 4). Specifically, the m-bit sequence represents one 242-tone RU. The 242-tone RU is one RU within the resource block set allocated to the four STAs for MU-MIMO transmission performed by the four STAs.

[0084] Referring below to Figure 14, how the reserved bit sequences in Table 1 are used in one embodiment of this application to show that multiple RUs are assigned to one group of STAs for MIMO transmission, Figure 14 is a schematic diagram of an 80 MHz allocation. For example, the 80 MHz bandwidth may be divided into four subchannels, each of which is 20 MHz or can be considered as 242 tone RUs. From left to right, the four subchannels are numbered 1 to 4, and the four subchannels are shown as RU1, RU2, RU3, and RU4, respectively. Figure 14 shows an example in which the AP indicates that multiple RUs are assigned to one group of STAs (STA1 to STA4) for MIMO transmission. It should be understood that in this embodiment of this application, the number of multiple STAs is not limited.

[0085] Specifically, in the first example, the reserved bit sequence may be used to indicate the type of each RU included in the allocated resource block set and the total number of STAs allocated for transmission to the resource block set. Resource allocation information included in the CC is shown as RU(same, n), where n represents the total number of STAs allocated for transmission to the resource block set. If a RU is punctured, the resource allocation information included in the CC is shown as RU(0). For example, in Table 1, "01110001" indicates that a 242-tone RU is punctured and shown as (0).

[0086] For example, to indicate that three discontinuous RUs (RU1, RU3, and RU4) are assigned to four STAs for transmission, that RU2 is punctured, and that RU1, RU3, and RU4 are all 242-tone RUs, the resource allocation information included in CC1 may be 242(same, 4) + 242(same, 4), and the resource allocation information included in CC2 may be 242(0) + 242(same, 4).

[0087] In a conceivable design, it should be understood that each CC contains two user information fields from STA. For example, the resource allocation information contained in CC1 may be 242(same, 4) + 242(same, 4), the user information field of STA1, and the user information field of STA2, and the resource allocation information contained in CC2 may be 242(0) + 242(same, 4), the user information field of STA3, and the user information field of STA4.

[0088] As another example, to show that three discontinuous RUs (RU1, RU3, and RU4) are assigned to four STAs for transmission, with RU2 being punctured, RU1 being a 242-tone RU, and RU3 and RU4 forming a 484-tone RU, the resource allocation information contained in CC1 may be 242(same, 4) + 484(same, 4), and the resource allocation information contained in CC2 may be 242(0) + 484(same, 4). In this example, RU3 and RU4 are contiguous and assigned to STA1 with a granularity of 484 tones. This differs from the previous example. In this design, STA1 receives CC1 and CC2. The assigned RUs can be obtained by interpreting only CC1 or CC2 to form a larger resource block, instead of interpreting both CC1 and CC2.

[0089] In another implementation of the first example, the second example may use a reserved bit sequence to indicate the type of each RU and the number of user information fields in the allocated resource block set. The resource allocation information contained in the CC is represented as RU(same, k), where k is the number of user information fields.

[0090] For example, to indicate that three discontinuous RUs (RU1, RU3, and RU4) are assigned to four STAs for transmission, the resource allocation information included in CC1 may be 242(same, 1) + 242(same, 1), and the resource allocation information included in CC2 may be 242(0) + 242(same, 2). RU2 is punctured. RU1, RU3, and RU4 are all 242-tone RUs. The number of user information fields set in CC1 corresponding to RU1 is 1. The number of user information fields set in CC2 corresponding to RU2 is 1. The number of user information fields set in CC1 corresponding to RU3 is 0. The number of user information fields set in CC2 corresponding to RU4 is 2.

[0091] Alternatively, to indicate that three discontinuous RUs (RU1, RU3, and RU4) are allocated to four STAs for transmission, the resource allocation information included in CC1 may be 242(same, 2) + 484(same, 0), and the resource allocation information included in CC2 may be 242(0) + 484(same, 2). RU2 is punctured. RU1 is a 242-tone RU. RU3 and RU4 form a 484-tone RU. The number of user information fields set in CC1 corresponding to RU1 is 2. The number of user information fields set in CC2 corresponding to RU2 is 0. The number of user information fields set in CC1 corresponding to RU3 is 0. The number of user information fields set in CC2 corresponding to RU4 is 2.

[0092] In a conceivable design, it should be understood that each CC contains user information fields from two STAs. For example, CC1 and CC2 contain user information fields from STA1 and STA2, and CC2 also contains user information fields from STA3 and STA4.

[0093] In other implementations of the first and second examples, reserved bit sequences can be used to indicate the type of each RU included in the allocated resource block set, which includes 242 (same), 484 (same), 996 (same), and 996*2 (same). Here, it is not necessary to add n or k. In other words, in the first example, the total number of STAs to which multiple RUs are allocated for transmission may be indicated using other signaling, and in the second example, the total number of user information fields in the two CCs is the total number of STAs to which multiple RUs are allocated for transmission. For example, an AP may use the second instruction information to indicate the total number of STAs to which multiple RUs are allocated for transmission, or the number of user information fields. For implementations of the second instruction information, see the implementations of the first instruction information in the embodiments described above. Details are not described here.

[0094] In a conceivable design, the second instruction information may be conveyed in a first field of the PPDU. The first field may be located before the common field of the EHT-SIG field in the PPDU, and may be, for example, the U-SIG field or another conceivable field. For example, the U-SIG field occupies multiple bits. Some of these bits are used to indicate the total number of STAs n in the assignment or the number of user information fields k.

[0095] If the AP can support simultaneous communication with, for example, 16 STAs, i.e., the range of n is [1, 16] and there are at least four types of RUs, then it should be understood that the reserved bit sequences shown in Table 1 obviously do not represent all cases. Therefore, in this embodiment of the application, the bit sequences used may occupy more than 8 bits, for example, 9 bits. For example, the reserved bit sequences in Table 1 are used to implement the AP assigning multiple RUs to 16 STAs using the reserved bit sequences, and the reserved bit sequences occupy 9 bits. In other words, in this embodiment of the application, m is 8 or greater.

[0096] In other embodiments, if the first instruction information in this embodiment of this application is used to indicate a full-bandwidth MU-MIMO punctured transmission scenario, other instruction information in this embodiment of this application may be used to indicate that one resource block set is allocated to multiple STAs for transmission and to indicate where the spectral bandwidth is punctured. The instruction information may be conveyed, for example, in a common field of the EHT field in the PPDU. For example, one field may be newly defined in the common field to indicate a bandwidth puncturing bitmap. For example, for an 80 MHz bandwidth, the field may occupy 4 bits. In other words, in this embodiment of this application, a 4-bit bandwidth puncturing bitmap may be used to indicate a particular punctured 20 MHz. For example, the value of the field "1011" may indicate that a second 20 MHz is punctured, and "1111" may indicate that 80 MHz is not punctured. Alternatively, for example, for a 320 MHz bandwidth, the field may occupy 15 or 16 bits. Alternatively, the number of bits occupied by the field is fixed, meaning the number does not change with bandwidth. For example, the number of bits occupied by the field is the number of 20M included in the maximum bandwidth, e.g., 16 bits. The field can be used to implement the assignment of multiple RUs to multiple STAs and to support the assignment of multiple discontinuous RUs.

[0097] It should be understood that the bandwidth puncturing bitmap can also be replaced with the available channel bitmap to indicate whether multiple 20MHz frequencies from low to high are idle within the bandwidth. For example, a first value, e.g., 1, is set with respect to the available channel bitmap to indicate that a corresponding 20MHz is idle, and a second value, e.g., 0, is set with respect to the available channel bitmap to indicate that a corresponding 20MHz is busy. In addition, the available channel bitmap can also indicate whether multiple 20MHz frequencies from high to low are idle within the bandwidth.

[0098] It should be noted that when an AP instructs a single-user punctured transmission using one or more fields in the preamble, 242(1) in Table 1 can be reused as a variation of 242(same, 1) to indicate that the RU corresponding to the 242(1) bit sequence is assigned to one STA. Similarly, 484(1) in Table 1 can be reused as a variation of 484(same, 1) to indicate that the RU corresponding to the 242(1) bit sequence is assigned to one STA. Likewise, 996(1) in Table 1 can be reused to replace 996(same, 1), and the newly added 996*2(1) can be reused to replace 996*2(same, 1).

[0099] Figure 15 shows a downlink full-bandwidth MU-MIMO punctured transmission method according to one embodiment of this application. The method may include the following steps:

[0100] S1501.AP generates a PPDU. The PPDU preamble may include a first field and a second field. The first field is used to indicate that the PPDU to be sent is a single-user punctured PPDU. The second field includes multiple resource unit assignment fields. Each resource unit assignment field is used to indicate one RU in a set of resource blocks assigned to one group of STAs.

[0101] S1502.AP sends a PPDU.

[0102] The S1503.STA group receives PPDUs. Each STA group receives or transmits data information based on its assigned resource block set.

[0103] It should be understood that the first field may be the aforementioned U-SIG field used to convey the first instruction information. For specific embodiments of appending the first instruction information to the U-SIG field, please refer to the description of the embodiments above, which will not be repeated here. Alternatively, if this embodiment of the application is particularly applicable to a downlink full-bandwidth MU-MIMO punctured transmission scenario, the PPDU may be generated when the AP needs to perform a downlink full-bandwidth MU-MIMO transmission. The preamble of the PPDU indicates that a group of users is performing a downlink full-bandwidth MU-MIMO punctured transmission. This is similar to the single-user punctured transmission scenario. The specific method is as follows: one value in the PPDU format field of the U-SIG field indicates a multi-user transmission, and one or more values ​​in the puncturing field or bandwidth field indicate a punctured transmission. The punctured transmission method indicated by the bandwidth field is similar to that in 802.11ax. Some values ​​in the bandwidth field indicate the punctured bandwidth. For example, the fifth value represents 80M in punctured scheme 1, and the sixth value represents 80M bandwidth in punctured scheme 2. One of the two values ​​may indicate puncturing.

[0104] The U-SIG field further includes a compression field. If the compression field is set to a first value, for example 1, it indicates that there is no resource unit allocation field or bandwidth puncturing bitmap / available channel bitmap in the common field of the EHT SIG field. When the compression field is set to a first value and the indication information indicates non-puncturing, in this case, a subfield similar to "HE-SIG-B symbol or number of multi-user multi-input multi-output stations" located in the U-SIG field or other fields within HE-SIG A indicates the number of multi-user multi-input multi-output stations.

[0105] If the Compression field is set to a second value, for example 0, it indicates the presence of a Resource Unit Allocation field or Bandwidth Puncturing Bitmap / Available Channel Bitmap in the Common Fields of the EHT SIG field. When the Compression field is set to a second value and the indication information indicates non-puncturing, in this case, a subfield similar to "Number of HE-SIG-B Symbols or Multi-User Multi-Input Multi-Output Stations" in HE-SIG A in Table 2, located in the U-SIG field or another field, indicates the number of OFDM symbols in the EHT-SIG field. When the Compression field is set to a second value and the indication information indicates puncturing, in this case, a subfield similar to "Number of HE-SIG-B Symbols or Multi-User Multi-Input Multi-Output Stations" in HE-SIG A, located in the U-SIG field or another field, indicates the number of multi-user multi-input multi-output stations.

[0106] [Table 2]

[0107] The second field may be a common field in the aforementioned EHT-SIG field. The second field includes multiple resource unit assignment fields. Each resource unit assignment field can convey the aforementioned reserved bit sequence used to indicate one RU in a set of resource blocks assigned to a group of STAs. Indeed, puncturing locations can also be indicated by using the reserved bit sequence. For specific implementations, please refer to the aforementioned embodiment in a single-user punctured transmission scenario. Details will not be repeated here.

[0108] In a conceivable application scenario, for example, a downlink OFDMA PPDU transmission scenario, in this embodiment of the application, a reserved bit sequence in the resource allocation information table may be used to indicate that more than 242 tone RUs are allocated to a single station or a group of stations for data transmission. In the case of a group of stations, the group of stations performs MU-MIMO transmission for more than 242 tone RUs.

[0109] Referring to Figure 16, it should be noted that in one embodiment of this application, it is assumed that no overlap is permitted between the frequency bands included in multiple RUs assigned to different stations. Figure 16 is a schematic diagram of a 160 MHz allocation. In Figure 16, for example, the 160 MHz bandwidth is divided into eight subchannels, each subchannel being 242 tone RUs. From left to right, the eight subchannels are numbered CH1 to CH8, and the eight subchannels are shown as RU1, RU2, RU3, RU4, RU5, RU6, RU7, and RU8, respectively. RU2 and RU6 are punctured. No overlap is permitted between the frequency band ranges of multiple RUs assigned to different stations. Specifically, resources are allocated to two stations, as shown in Figure 14. RU1, RU3, and RU4 may be allocated to one station, and RU5, RU7, and RU8 may be allocated to the other station. However, it is not permissible to assign RU1 and RU5 to one station and RU3, RU4, RU7, and RU8 to the other station. It should be understood that this embodiment of the application may be used when there is overlap between the frequency bands included in multiple RUs assigned to a station. In this case, the modes of assigning multiple RUs to the same station are limited but not random.

[0110] In this embodiment of the application, since duplication is not permitted among multiple RUs assigned to different stations, in this embodiment of the application, the last assigned RU may be indicated for an STA to indicate a particular RU assigned to the same STA among multiple assigned RUs. In other words, in this embodiment of the application, the following may be indicated: the assigned RU is the last RU belonging to multiple RUs assigned to an STA. Alternatively, the last RU in multiple RUs assigned to an STA may be used as an identifier to distinguish between RUs assigned to different STAs. In other words, the last RU belongs to the last RU of the previous STA, but the first RU following the last RU is assigned to the current STA.

[0111] In a conceivable implementation, in addition to the type of each RU within the allocated resource block set, the reserved bit sequence may further indicate a third directive and the total number of stations to which multiple RUs of 242 tones or more are allocated for transmission. The third directive is used to indicate the last RU in the multiple RUs allocated to the STA.

[0112] The third instruction information may include the first and second identification information. Changes to the first and second identification information can indicate the last RU of the previous STA. In other words, changes to the first and second identification information indicate the frequency boundaries of RUs assigned to different STAs. For example, resource allocation information contained in one resource unit allocation subfield may be indicated as RU(same, A, n), where "RU" indicates the type of RU, e.g., 242-tone RU or 484-tone RU; "same" means that the reserved bit sequence conveyed in the resource unit allocation subfield is the same; "A" indicates the first identification information; and "n" indicates the total number of stations to which multiple RUs of 242-tone RU or more are allocated for transmission. If "A" indicates the last RU in multiple RUs of a first STA, it should be understood that the second identification information "B" may be used to indicate the last RU in multiple RUs of a second STA. In other words, resource allocation information contained in one resource unit allocation field in CC may be indicated as RU(same, B, n). It should be noted that in RU(x, y, z), RU represents the size, x represents the same, y represents A or B, and z represents n. Here, RU(x, y, z) must be represented using one reserved bit sequence, as long as one parameter differs.

[0113] In another embodiment, in addition to the type of assigned RU, the reserved bit sequence may further indicate the total number of user information fields for a station to which multiple RUs of 242 tone RUs or more are assigned for transmission, and third instruction information. For example, resource assignment information contained in one resource unit assignment subfield may be indicated as RU(same, A, k) or RU(same, B, k), where k is the number of user information fields. This is the same as in the embodiment described above.

[0114] To facilitate understanding, the following will refer to Figures 17 and 18 to explain how the AP indicates one or more STAs to which multiple RUs of 242 tone RUs or more are allocated for data transmission.

[0115] Figure 17 is a schematic diagram of the allocation of 160 MHz. For example, the 160 MHz bandwidth is divided into eight subchannels, each subchannel having 242 tone RUs. From left to right, the eight subchannels are numbered CH1 to CH8, and are shown as RU1, RU2, RU3, RU4, RU5, RU6, RU7, and RU8, respectively. RU2 and RU6 are divided into multiple smaller resource blocks. Assume that AP allocates RU1, RU3, and RU4 to STA1 and RU5, RU7, and RU8 to STA2. STA1 and STA2 perform single-user transmissions on the 160 MHz bandwidth. RU2 and RU6 may be allocated to other STAs.

[0116] In the first example, the reserved bit sequence may be used to indicate the type of each RU included in the allocated resource block set, third instruction information, and the total number of STAs to which multiple RUs of 242 tone RUs or more are allocated for transmission. Resource allocation information included in the CC may be indicated as RU (same, A or B, 1).

[0117] For example, to indicate that RUs corresponding to the same bit sequence are assigned to the same STA, the resource allocation information included in CC1 may be 242(same, A, 1)+242(same, A, 1)+242(same, B, 1)+242(same, B, 1), and the resource allocation information included in CC2 may be X+242(same, A, 1)+Y+242(same, B, 1). The changes in A and B indicate a specific RU that is the last RU among the multiple RUs of STA1. Since the total number of STAs to which multiple RUs of 242 tone RUs or more are assigned for transmission is 1, CC1 may include one user information field of STA1 and one user information field of STA2, and CC2 may include one user information field of STA1 and one user information field of STA2. Here, X and Y separately indicate multiple smaller resource blocks obtained by dividing 20 MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0118] Alternatively, the resource allocation information contained in CC1 may be 242(same, A, 1)+484(same, A, 1)+242(same, B, 1)+484(same, B, 1), and the resource allocation information contained in CC2 may be X+484(same, A, 1)+Y+484(same, B, 1), indicating that RUs corresponding to the same bit sequence are assigned to the same STA. The changes in A and B indicate a specific RU that is the last RU among multiple RUs in STA1. It should be understood that CC1 may contain one user information field of STA1 and one user information field of STA2, and CC2 may contain one user information field of STA1 and one user information field of STA2. Here, X and Y separately represent multiple smaller resource blocks obtained by dividing 20MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0119] In another implementation of the first example, the reserved bit sequence may be used to indicate the type of RU assigned, third instruction information, and the total number of user information fields in the STA to which multiple RUs of 242 tone RUs or more are assigned for transmission. Resource assignment information included in the CC may be represented as RU(same, A or B, k), where the value of k is 0 or 1. Here, RU(same, A or B, 0) can further indicate that the number of user information fields corresponding to the resource bit sequence included in the CC is 0, and RU(same, A or B, 1) can further indicate that the number of user information fields corresponding to the resource bit sequence included in the CC is 1.

[0120] In this case, to indicate that RUs corresponding to the same bit sequence are assigned to the same STA, the resource allocation information contained in CC1 may be 242(same, A, 1) + 242(same, A, 0) + 242(same, B, 0) + 242(same, B, 0), and the resource allocation information contained in CC2 may be X + 242(same, A, 0) + Y + 242(same, B, 1). The changes in A and B indicate a specific RU that is the last RU among multiple RUs of STA1. In this case, CC1 may include the user information field of STA1, and CC2 may include the user information field of STA2. Here, X and Y separately indicate multiple smaller resource blocks obtained by dividing 20 MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0121] Alternatively, the resource allocation information contained in CC1 may be 242(same, A, 1) + 484(same, A, 0) + 242(same, B, 0) + 484(same, B, 0), and the resource allocation information contained in CC2 may be X + 484(same, A, 0) + Y + 484(same, B, 1). It should be understood that CC1 may contain the user information field of STA1, and CC2 may contain the user information field of STA2. Here, X and Y separately represent multiple smaller resource blocks obtained by dividing 20MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0122] Figure 18 is a schematic diagram of 160MHz allocation. For example, the 160MHz bandwidth is divided into eight subchannels, each subchannel having 242 tone RUs. From left to right, the eight subchannels are numbered CH1 to CH8, and are shown as RU1, RU2, RU3, RU4, RU5, RU6, RU7, and RU8, respectively. RU2 and RU6 are divided into multiple smaller resource blocks. Assume that AP allocates RU1, RU3, and RU4 to STA1, and RU5, RU7, and RU8 to the four STAs STA2, STA3, STA4, and STA5. STA1 to STA4 perform full-bandwidth MU-MIMO transmission over the 160MHz bandwidth.

[0123] In the first example, the reserved bit sequence may be used to indicate the type of each RU included in the allocated resource block set, third instruction information, and the total number of STAs to which multiple RUs of 242 tone RUs or more are allocated for transmission. In this case, the resource allocation information included in the CC may be indicated as RU(same, A or B, n).

[0124] For example, to indicate that RUs corresponding to the same bit sequence are assigned to the same STA, the resource allocation information contained in CC1 may be 242(same, A, 1)+242(same, A, 1)+242(same, B, 4)+242(same, B, 4), and the resource allocation information contained in CC2 may be X+242(same, A, 0)+Y+242(same, B, 0). The changes in A and B indicate a specific RU that is the last RU among multiple RUs of STA1. In this case, CC1 contains user information fields for STA1 to STA5, and CC2 contains user information fields corresponding to CH2 and CH6. Here, X and Y separately indicate multiple smaller resource blocks obtained by dividing 20MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0125] Alternatively, to indicate that RUs corresponding to the same bit sequence are assigned to the same STA, the resource allocation information contained in CC1 may be 242(same, A, 1)+484(same, A, 1)+242(same, B, 4)+484(same, B, 4), and the resource allocation information contained in CC2 may be X+484(same, A, 0)+Y+484(same, B, 0), where the changes in A and B indicate a specific RU that is the last RU among multiple RUs of STA1. In this case, CC1 contains user information fields for STA1 to STA5, and CC2 contains user information fields corresponding to CH2 and CH6. Here, X and Y separately indicate multiple smaller resource blocks obtained by dividing 20MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0126] In another implementation of the first example, the reserved bit sequence may be used to indicate the type of each RU included in the allocated resource block set, third instruction information, and the total number of user information fields in the STA to which multiple RUs of 242 tone RUs or more are allocated for transmission. Resource allocation information included in the CC may be represented as RU(same, A or B, k). It should be understood that the value of k is 0-5. For example, RU(same, A or B, 0) may further indicate that the number of user information fields corresponding to the resource bit sequence included in the CC is 0, and RU(same, A or B, 1) may further indicate that the number of user information fields corresponding to the resource bit sequence included in the CC is 1.

[0127] In this case, to indicate that RUs corresponding to the same bit sequence are assigned to the same STA, the resource allocation information contained in CC1 may be 242(same, A, 1) + 242(same, A, 0) + 242(same, B, 0) + 242(same, B, 5), and the resource allocation information contained in CC2 may be X + 242(same, A, 0) + Y + 242(same, B, 0). The changes in A and B indicate a specific RU that is the last RU among multiple RUs of STA1. In this case, CC1 contains user information fields for STA1 to STA5, and CC2 contains user information fields corresponding to CH2 and CH6. Here, X and Y separately indicate multiple smaller resource blocks obtained by dividing 20MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0128] Alternatively, the resource allocation information included in CC1 may be 242(same, A, 1) + 484(same, A, 0) + 242(same, B, 0) + 484(same, B, 5), and the resource allocation information included in CC2 may be X + 484(same, A, 0) + Y + 484(same, B, 1). It should be understood that CC1 includes the user information fields STA1 to STA5, and CC2 includes the user information fields corresponding to CH2 and CH6. Here, X and Y separately represent multiple smaller resource blocks obtained by dividing 20 MHz. This can be specifically shown using the 802.11ax standard, i.e., using the currently defined bit sequences in Table 1.

[0129] One embodiment of this application further provides an information instruction method used for uplink data transmission by STAs. In an uplink multi-user data transmission scenario, when multiple STAs need to transmit uplink data information simultaneously, the AP first sends a trigger frame to each STA involved in the multi-user data transmission, indicating the RU assigned to each STA in the trigger frame. After receiving the trigger frame, each STA then sends an uplink OFDMA frame, or a MU-MIMO frame, or a hybrid OFDMA and MU-MIMO frame as a response. The AP can then trigger each STA to transmit uplink data information with the RU assigned by the AP by sending an acknowledgment frame based on the received uplink OFDMA frame, or the received MU-MIMO frame, or the received hybrid OFDMA and MU-MIMO frame.

[0130] The structure of the trigger frame is shown in Figure 19. This structure includes a frame control field, a duration field, a receive address field, a transmit address field, a common information field, a user information list field, a padding field, and a frame check sequence field. The common information field and the user information list field are similar to the common field and multiple user information fields of HE-SIG B in the downlink multi-user transmission described above. For example, the common information field includes a trigger type field, an uplink length field, a further trigger frame field, a carrier sense requirement field, a bandwidth field, and a common information field based on the trigger frame type.

[0131] As shown in Figure 20, the user information field may include an association identifier field, a resource unit assignment field, an uplink coding type field, an uplink modulation coding scheme field, an uplink dual-carrier modulation field, a spatial stream assignment or random access resource unit information field, an uplink received signal strength indicator field, a reserved field, and a user information list field based on the trigger frame type.

[0132] In this embodiment of the application, multiple STAs are enabled to perform full-bandwidth multi-user MU-MIMO transmissions over discontinuous bandwidths. In this case, if the uplink trigger frame scheduling method in 802.11ax is still used, the number of user information fields for all users that need to be repeatedly involved in MU-MIMO transmissions over several discontinuous RUs increases with relatively high signaling overhead. Figure 12 is used as an example. In the uplink full-bandwidth multi-user MU-MIMO punctured transmission scenario, the trigger frame needs to include the user information fields of STA1-STA4 in transmissions at 20M (RU1) and 40M (RU3 and RU4, corresponding to 484-tone resource blocks). A total of eight user information fields need to be included.

[0133] With this in mind, one embodiment of this application provides a novel structure for trigger frames used for uplink multi-user MU-MIMO punctured transmission to avoid repeated transmission of information for MU-MIMO user groups corresponding to multiple discontinuous resource blocks due to punctured bandwidth, thereby reducing signaling overhead.

[0134] In a conceivable design, a new type, namely uplink full bandwidth multi-user MU-MIMO punctured transmission, can be added to the trigger type field of the trigger frame.

[0135] For example, the trigger type field shown in Figure 19 may also indicate an uplink full-bandwidth multi-user MU-MIMO punctured transmit. It should be understood that the trigger type field contains multiple bits. One value in the trigger type field is used to indicate that the trigger frame is used to trigger an uplink full-bandwidth multi-user MU-MIMO punctured transmit.

[0136] In other possible designs, a field may be added to the common information field of the trigger frame to indicate uplink-full bandwidth multi-user MU-MIMO punctured transmission.

[0137] For example, in the common information field of the trigger frame shown in Figure 19, a new field, for example, a first field, is defined. The first field may occupy one or more bits. The value of the first field is a first value (e.g., 1) to indicate an uplink full-bandwidth multi-user MU-MIMO punctured transmission. The value of the first field is a second value (e.g., 0) to indicate that there is no uplink full-bandwidth multi-user MU-MIMO punctured transmission.

[0138] In addition, the resource unit allocation field in the user information field in the trigger frame shown in Figure 20 may be replaced with a bandwidth puncturing bitmap field. In other words, the resource unit allocation field is used to indicate whether each 20MHz from low to high frequency within the bandwidth is punctured, or whether each 20MHz from low to high frequency within the bandwidth, excluding the primary 20MHz channel, is punctured. For example, in the case of an 80MHz bandwidth, the resource unit allocation field may occupy 4 bits. In other words, in this embodiment of the application, a 4-bit bandwidth puncturing bitmap may be used to indicate a particular punctured 20MHz. For example, the field value "1011" may indicate that the second 20MHz is punctured, and "1111" may indicate that the 80MHz is not punctured. Alternatively, for example, in the case of a 320MHz bandwidth, the resource unit allocation field may occupy 15 bits (each 20MHz excluding the primary 20MHz) or 16 bits (each 20MHz). Alternatively, the number of bits occupied by the resource unit allocation field may be fixed, meaning the number does not change with bandwidth. For example, the number of bits occupied by the resource unit allocation field may be 16 bits, the number of 20M included in the maximum bandwidth. The resource unit allocation field can be used to implement the allocation of multiple RUs to one or more STAs and to support the allocation of multiple discontinuous RUs.

[0139] In other conceivable implementations, the bandwidth puncturing bitmap field is replaced with an available channel bitmap to indicate specific available 20MHz within the bandwidth from low to high frequencies, or specific available 20MHz within the bandwidth from low to high frequencies, excluding the primary 20MHz channel.

[0140] Figure 21 shows an uplink full-bandwidth multi-user MU-MIMO punctured transmission method according to one embodiment of this application. The method may include the following steps:

[0141] S2101.AP generates a trigger frame. The trigger frame includes a first field and a second field. The first field is used to indicate that the trigger frame is used to schedule an uplink full-bandwidth multi-user MU-MIMO punctured transmission. The second field is used to indicate the identifiers of multiple STAs.

[0142] S2102.AP sends a trigger frame.

[0143] Each group of S2103.STA receives a trigger frame. Each STA transmits uplink data information based on its assigned resource block set.

[0144] S2104.AP receives information about uplink multi-user transmissions sent by one or more STAs and provides acknowledgment information as feedback.

[0145] The first field may be a common information field for the trigger frame. The second field may be a user information field. For specific implementations, please refer to the description of the embodiments above. It should be understood that the common information field for the trigger frame further includes one or more of the uplink length field, further trigger frame fields, carrier sense requirement field, and bandwidth fields, a bandwidth puncturing bitmap field or available channel bitmap, etc. The common information field further includes one or more of the uplink coding type field, uplink modulation coding scheme field, uplink dual carrier modulation field, spatial stream allocation or random access resource unit information field, and uplink received signal strength indicator field.

[0146] In step S2104, each STA should understand that it will send an uplink multi-user transmission after a predetermined interval. The predetermined interval is the SIFS time. The uplink multi-user transmission is an uplink MU-MIMO transmission. In step S2104, the acknowledgment information may be a downlink OFDMA acknowledgment or a multi-user block acknowledgment.

[0147] In the aforementioned solution in this application, bit sequences in the resource allocation information table may be used to indicate a resource block set assigned to one STA, or a resource block set assigned to multiple STAs. One bit sequence corresponds to one RU in the resource block set.

[0148] In the aforementioned embodiments of this application, the methods provided in the embodiments of this application are described separately in terms of AP, STA, and the interaction between AP and STA. To implement the functions in the methods provided in the embodiments of this application, network devices and terminals may include hardware structures and / or software modules to implement the functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether one of several functions is implemented in the form of a hardware structure, software module, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0149] A communication device for carrying out the method described above in the embodiments of this application will be described below with reference to the attached drawings. Therefore, all of the above may be used in subsequent embodiments. Repeated information will not be described again.

[0150] Figure 22 is a schematic diagram of the structure of a communication device. The communication device may be a device applied to the AP side, or it may be a component (e.g., a chip or circuit) of a device applied to the AP side. The communication device is configured to perform the functions realized by the AP in the embodiments of the method described above. As shown in Figure 22, the communication device may include a processing module 2201 and a transceiver module 2202.

[0151] In some embodiments, the processing module 2201 is configured to determine resource instruction information. The resource instruction information includes a plurality of bit sequences. The first bit sequence in the plurality of bit sequences corresponds to a first resource unit. The first resource unit is a resource unit in a resource block set assigned to a first STA or a plurality of STAs. The resource block set includes at least two resource units.

[0152] The transceiver module 2202 is configured to transmit resource instruction information.

[0153] In some other embodiments, the processing module 2201 is configured to generate first instruction information. The first instruction information is used to indicate that multiple STAs perform full-bandwidth multi-user MU-MIMO transmissions with discontinuous bandwidth.

[0154] The transceiver module 2202 is configured to transmit the first instruction information.

[0155] It should be understood that the communication device is an AP in the aforementioned method, and that the communication device has any of the functions of an AP in the aforementioned method.

[0156] The above describes the communication device in this embodiment of the application. The following describes possible product forms of the communication device. It should be understood that any product in any form having the functions of the communication device shown in Figure 22 falls within the scope of protection of the embodiments of this application. It should be further understood that the following description is merely an example and does not indicate that the product forms of the communication device in this embodiment of the application are limited thereto.

[0157] In conceivable product forms, the communication device in this embodiment of this application can be implemented using a general bus system structure.

[0158] The communication device includes a processor and a transceiver that is internally connected to the processor and communicates with the processor. In some embodiments, the processor is configured to determine resource instruction information. The resource instruction information includes a plurality of bit sequences. A first bit sequence in the plurality of bit sequences corresponds to a first resource unit. The first resource unit is a resource unit in a resource block set assigned to a first STA or a plurality of STAs. The resource block set includes at least two resource units. The transceiver is configured to transmit the resource instruction information. Optionally, the communication device may further include memory. The memory is configured to store instructions to be executed by the processor.

[0159] In other embodiments, the processor is configured to generate first instruction information. The first instruction information is used to indicate that multiple STAs perform full-bandwidth multi-user MU-MIMO transmissions in discontinuous bandwidth. The transceiver is configured to transmit the first instruction information. Optionally, the communication device may further include memory. The memory is configured to store instructions to be executed by the processor.

[0160] In a conceivable product form, the communication device in this embodiment of this application may be implemented using a general-purpose processor.

[0161] A general-purpose processor for implementing a communication device includes a processing circuit and an output interface internally connected to the processing circuit and communicating with the processing circuit. The processing circuit is configured to determine resource instruction information. The resource instruction information includes a plurality of bit sequences. The first bit sequence in the plurality of bit sequences corresponds to a first resource unit. The first resource unit is a resource unit in a resource block set assigned to a first STA or a plurality of STAs. The resource block set includes at least two resource units. The output interface is configured to transmit the resource instruction information. Optionally, the general-purpose processor may further include a storage medium. The storage medium is configured to store instructions to be executed by the processing circuit.

[0162] A general-purpose processor for implementing a communication device includes a processing circuit and an input interface internally connected to the processing circuit and communicating with the processing circuit. The processing circuit is configured to generate first instruction information. The first instruction information is used to indicate that multiple STAs perform full-bandwidth multi-user MU-MIMO transmissions with discontinuous bandwidth. The input interface is configured to transmit the first instruction information. Optionally, the general-purpose processor may further include a storage medium. The storage medium is configured to store instructions to be executed by the processing circuit.

[0163] In conceivable product forms, the communication device in this embodiment of this application may be further implemented by using one or more FPGAs (field-programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, individual hardware components, any other suitable circuits, or any combination of circuits capable of performing the functions described in this application.

[0164] It should be understood that the various product forms of communication devices mentioned above possess any of the functions of the AP in the embodiment of the method. Details will not be repeated here.

[0165] In short, prior art does not allow the use of punctured channels during single-user transmission and full-bandwidth multi-user MU-MIMO transmission. This application is a technical solution proposed to enable the use of punctured channels during single-user transmission and full-bandwidth multi-user MU-MIMO transmission. Specifically, embodiments of this application provide a single-user punctured transmission method and a full-bandwidth MU-MIMO punctured transmission method. The relevant solutions for implementing the two methods are described separately below.

[0166] It should be noted below that m≧8, for example, m=8 or m=9; n=one of 1 to 16; and a punctured 242-tone RU (i.e., 20M) may be indicated by using an m-bit sequence. Briefly, "242(0)" is used to mark an m-bit sequence. In other words, "242(0)" may be thought of as representing an m-bit sequence. An m-bit sequence indicates either a null 242-tone RU or a punctured 242-tone RU.

[0167] (1) Solution for single-user punctured transmission method Embodiment 1: One or more fields within the U-SIG field are used to indicate whether the PPDU to be transmitted is a single-user punctured PPDU.

[0168] Embodiment 2: How to indicate a specific puncturing location during single-user punctured transmission?

[0169] Specific solution 1: The m-bit sequence in the resource allocation table represents a RU. An RU is one of several RUs allocated to a user. Here, m ≥ 8.

[0170] For example, the m-bit sequence in the resource allocation table represents a 242-tone RU. The 242-tone RU is one of several RUs assigned to a user. Simply put, "242 (same, 1)" is used to mark the m-bit sequence. In other words, you can think of "242 (same, 1)" as representing the m-bit sequence. The m-bit sequence represents a 242-tone RU. The 242-tone RU is one of several RUs assigned to a user.

[0171] Therefore, in the puncturing shown in Figure 12, the first 242-tone RU (i.e., 20M) is represented using 242(same, 1), the second 242-tone RU is represented using 242(0), the third 242-tone RU is represented using 242(same, 1), and the fourth 242-tone RU is represented using 242(same, 1). For CCs as described in the 802.11ax standard, resource allocation information for odd-numbered channels (i.e., m-bit sequences in the resource allocation table) is set for CC1, and resource allocation information for even-numbered channels is set for CC2. In this case, 242(same, 1) is set for CC1 to represent the first 20M, 242(0) is set for CC2 to represent the second 20M, 242(same, 1) is set for CC1 to represent the third 20M, and 242(same, 1) is set for CC2 to represent the fourth 20M. The information transmitted under CC1 and CC2 includes, in the case of CC1, 242(same, 1) and 242(same, 1), and in the case of CC2, 242(0) and 242(same, 1).

[0172] Optionally, CC1 and CC2 each contain one additional user information field, and the information conveyed by CC1 and CC2 includes the user information fields 242(same, 1), 242(same, 1), and STA1 for CC1, and the user information fields 242(0), 242(same, 1), and STA1 for CC2.

[0173] It should be understood that an m-bit sequence can further indicate RUs with other sizes. For example, an m-bit sequence in a resource allocation table indicates a 484-tone RU. A 484-tone RU is one of several RUs assigned to a user. Simply put, "484(same, 1)" is used to mark an m-bit sequence. In other words, "484(same, 1)" can be thought of as representing an m-bit sequence. An m-bit sequence indicates a 484-tone RU. A 484-tone RU is one of several RUs assigned to a user. In the case of puncturing shown in Figure 12, the information conveyed by CC1 and CC2 may further include, in the case of CC1, 242(same, 1) and 484(same, 1), and in the case of CC2, 242(0) and 484(same, 1).

[0174] Optionally, CC1 and CC2 each contain one additional user information field, and the information conveyed by CC1 and CC2 includes the user information fields 242(same, 1), 484(same, 1), and STA1 in the case of CC1, and the user information fields 242(0), 484(same, 1), and STA1 in the case of CC2.

[0175] It should be further understood that an m-bit sequence can further represent RUs of other sizes. For example, an m-bit sequence in a resource allocation table might represent 996 RUs, where 996 RUs are one of several RUs allocated to a user. For example, an m-bit sequence in a resource allocation table might represent 2*996 RUs, where 2*996 RUs are one of several RUs allocated to a user. This optional solution is similar to the previously mentioned solution, and its details are not explained here.

[0176] Specific solution 2: The m-bit sequence in the resource allocation table represents a RU. An RU is one of several RUs assigned to a user. The number of user information fields corresponding to an RU is 0. Other m-bit sequences in the resource allocation table represent RUs. An RU is one of several RUs assigned to a user. The number of user information fields corresponding to an RU is 1. Here, m ≥ 8.

[0177] For example, the m-bit sequence in the resource allocation table represents a 242-tone RU. The 242-tone RU is one of several RUs assigned to a user. The number of user information fields corresponding to the 242-tone RU is 0. Simply put, "242 (same, 0)" is used to mark the m-bit sequence. In other words, you can think of "242 (same, 0)" as representing the m-bit sequence, the m-bit sequence representing a 242-tone RU, the 242-tone RU being one of several RUs assigned to a user, and the number of user information fields corresponding to the 242-tone RU being 0. Other m-bit sequences in the resource allocation table represent a 242-tone RU. The 242-tone RU is one of several RUs assigned to a user. The number of user information fields corresponding to the 242-tone RU is 1. Simply put, "242 (same, 1)" is used to mark the m-bit sequence. In other words, "242 (same, 1)" can be thought of as representing an m-bit sequence, where the m-bit sequence indicates a 242-tone RU, where the 242-tone RU is one of several RUs assigned to the user, and where the number of user information fields corresponding to the 242-tone RU is 1.

[0178] If CC1 and CC2 each contain a single user information field, the single-user puncturing shown in Figure 12 includes one of the following pieces of information conveyed by CC1 and CC2: (1) In the case of CC1, the user information fields 242(same, 1), 242(same, 0), and STA1; and in the case of CC2, the user information fields 242(0), 242(same, 1), and STA1, or (2) For CC1, the user information fields 242(same, 0), 242(same, 1), and STA1; and for CC2, the user information fields 242(0), 242(same, 1), and STA1.

[0179] It should be understood that an m-bit sequence can further indicate RUs with other sizes. For example, an m-bit sequence in a resource allocation table indicates a 484-tone RU. A 484-tone RU is one of several RUs assigned to a user. The number of user information fields corresponding to the 484-tone RU is 0. Simply put, "484(same, 0)" is used to mark an m-bit sequence. In other words, you can think of "484(same, 0)" as representing an m-bit sequence, where the m-bit sequence indicates a 484-tone RU, where a 484-tone RU is one of several RUs assigned to a user, and the number of user information fields corresponding to the 484-tone RU is 0. In another example, an m-bit sequence in a resource allocation table indicates a 484-tone RU. A 484-tone RU is one of several RUs assigned to a user. The number of user information fields corresponding to the 484-tone RU is 1. Simply put, "484(same, 1)" is used to mark an m-bit sequence. In other words, "484 (same, 1)" can be thought of as representing an m-bit sequence, where the m-bit sequence indicates a 484-tone RU, where the 484-tone RU is one of several RUs assigned to the user, and where the number of user information fields corresponding to the 484-tone RU is 1.

[0180] If CC1 and CC2 each contain a single user information field, the single-user puncturing shown in Figure 12 may also contain any one of the following additional information: (1) In the case of CC1, the user information fields 242 (same, 1), 484 (same, 0), and STA1; and in the case of CC2, the user information fields 242 (0), 484 (same, 1), and STA1, or (2) For CC1, the user information fields 242 (same, 0), 484 (same, 1), and STA1; and for CC2, the user information fields 242 (0), 484 (same, 1), and STA1.

[0181] It should be further understood that an m-bit sequence can further represent RUs of other sizes. For example, an m-bit sequence in a resource allocation table represents 996 RUs, where 996 RUs is one of several RUs allocated to a user, and the number of user information fields corresponding to 996 RUs is 0. In another example, an m-bit sequence in a resource allocation table represents 996 RUs, where 996 RUs is one of several RUs allocated to a user, and the number of user information fields corresponding to 996 RUs is 1. In yet another example, an m-bit sequence in a resource allocation table represents 2*996 RUs, where 2*996 RUs is one of several RUs allocated to a user, and the number of user information fields corresponding to 2*996 RUs is 0. In yet another example, an m-bit sequence in a resource allocation table represents 2*996 RUs, where 2*996 RUs is one of several RUs allocated to a user, and the number of user information fields corresponding to 996 RUs is 1.

[0182] (2) Solutions for Downlink Full Bandwidth MU-MIMO Punctured Transmission Method Embodiment 1: One or more fields within the U-SIG field are used to indicate whether the PPDU to be transmitted is a PPDU in a full-bandwidth MU-MIMO punctured transmission.

[0183] Embodiment 2: How to indicate a specific puncturing location during full-bandwidth MU-MIMO transmission?

[0184] The full-bandwidth MU-MIMO punctured transmission shown in Figure 14 can be implemented using several of the following solutions.

[0185] Specific solution 1: The m-bit sequence in the resource allocation table represents a RU. A RU is one of several RUs allocated to n users for a MU-MIMO run by n users, where m ≥ 8 and n = 1 to 16. The m-bit sequence in the resource allocation table represents a 242-tone RU. A 242-tone RU is one of several RUs allocated to 4 users for a MU-MIMO run by 4 users. Simply put, "242 (same, 4)" is used to mark the m-bit sequence. In other words, "242 (same, 4)" can be thought of as representing the m-bit sequence. The m-bit sequence represents a 242-tone RU. A 242-tone RU is one of several RUs allocated to 4 users for a MU-MIMO run by 4 users.

[0186] Therefore, in the case of full-bandwidth MU-MIMO punctured transmission shown in Figure 14, the first 20M is represented using 242(same, 4), the second 20M is represented using 242(0), the third 20M is represented using 242(same, 4), and the fourth 20M is represented using 242(same, 4). In the method for setting resource allocation information (i.e., m-bit sequences in the resource allocation table) for odd-numbered and even-numbered channels, the information conveyed by CC1 and CC2 includes 242(same, 4) and 242(same, 4) for CC1, and 242(0) and 242(same, 4) for CC2.

[0187] Optionally, if each CC contains two user information fields, for example, the information conveyed by CC1 and CC2 would include, in the case of CC1, 242(same, 4), 242(same, 4), the user information field of STA1 and the user information field of STA2, and in the case of CC2, 242(0), 242(same, 4), the user information field of STA3 and the user information field of STA4.

[0188] It should be understood that an m-bit sequence can further indicate RUs with other sizes. For example, an m-bit sequence in a resource allocation table indicates a 484-tone RU. A 484-tone RU is one of several RUs assigned to four users for a MU-MIMO run by four users. Simply put, "484(same, 4)" is used to mark an m-bit sequence. In other words, you can think of "484(same, 4)" as representing an m-bit sequence. The m-bit sequence indicates a 484-tone RU. A 484-tone RU is one of several RUs assigned to four users for a MU-MIMO run by four users. In this case, the information conveyed in CC1 and CC2 may further include, in the case of CC1, 242(same, 4) and 484(same, 4), and in the case of CC2, 242(0) and 484(same, 4).

[0189] If each CC optionally includes two user information fields, the information conveyed by CC1 and CC2 will be as follows: for CC1, 242 (same, 4), 484 (same, 4), the user information field of STA1 and the user information field of STA2; and for CC2, 242 (0), 484 (same, 4), the user information field of STA3 and the user information field of STA4.

[0190] It should be further understood that an m-bit sequence can further represent RUs of other sizes. For example, an m-bit sequence in a resource allocation table represents 996 RUs, and 996 RUs is one of several RUs allocated to four users for a MU-MIMO run by four users. For example, an m-bit sequence in a resource allocation table represents 2*996 RUs, and 2*996 RUs is one of several RUs allocated to four users for a MU-MIMO run by four users. This optional solution is similar to the previously mentioned solution. Details are not explained here.

[0191] Indeed, an m-bit sequence can represent one of several RUs assigned to n users with respect to MU-MIMO performed by n users, where n = 1 to 16. The example n = 4 is used only as an illustration. The specific value of n is not limited to this embodiment of the application.

[0192] Specific solution 2: An m-bit sequence in a resource allocation table represents a RU. A RU is one of several RUs assigned to n users for a MU-MIMO run by n users. A RU corresponds to k user information fields. For example, an m-bit sequence in a resource allocation table represents a 242-tone RU, which is one of several RUs assigned to four users for a MU-MIMO run by four users, and a 242-tone RU corresponds to one user information field. Simply put, "242 (same, 1)" is used to mark an m-bit sequence. In other words, "242 (same, 1)" can be thought of as representing an m-bit sequence. An m-bit sequence represents a 242-tone RU. A 242-tone RU is one of several RUs assigned to four users for a MU-MIMO run by four users. A 242-tone RU corresponds to one user information field.

[0193] Therefore, in the case of full-bandwidth MU-MIMO punctured transmission shown in Figure 14, the first 20M is represented using 242(same, 1), the second 20M is represented using 242(0), the third 20M is represented using 242(same, 1), and the fourth 20M is represented using 242(same, 2). In the method for setting resource allocation information (i.e., m-bit sequences in the resource allocation table) for odd-numbered and even-numbered channels, the information conveyed by CC1 and CC2 includes, for CC1, 242(same, 1), 242(same, 1), the user information field of STA1 and the user information field of STA2, and for CC2, 242(0), 242(same, 2), the user information field of STA3 and the user information field of STA4.

[0194] It should be understood that an m-bit sequence can further represent RUs with other sizes. For example, an m-bit sequence in a resource allocation table represents a 484-tone RU, which is one of several RUs assigned to four users for MU-MIMO performed by four users, and the 484-tone RU corresponds to one user information field. Simply put, "484(same, 1)" is used to mark an m-bit sequence. In other words, "484(same, 1)" can be thought of as representing an m-bit sequence. An m-bit sequence represents a 484-tone RU. A 484-tone RU is one of several RUs assigned to four users for MU-MIMO performed by four users. A 484-tone RU corresponds to one user information field. Also, 484(same, 2) represents an m-bit sequence. An m-bit sequence represents a 484-tone RU. A 484-tone RU is one of several RUs assigned to four users for MU-MIMO performed by four users. A 484 tone RU corresponds to two user information fields. In this case, the information conveyed by CC1 and CC2 is as follows: for CC1, it includes 242 (same, 1), 484 (same, 1), the user information field of STA1 and the user information field of STA2; and for CC2, it includes 242 (0), 484 (same, 2), the user information field of STA3 and the user information field of STA4.

[0195] It should be further understood that an m-bit sequence can further represent RUs of other sizes. For example, an m-bit sequence in a resource allocation table represents 996 RUs, where 996 RUs is one of several RUs allocated to four users for MU-MIMO performed by four users, and 996 RUs corresponds to k user information fields, represented by 996(same, k). For example, an m-bit sequence in a resource allocation table represents 2*996 RUs, where 2*996 RUs is one of several RUs allocated to four users for MU-MIMO performed by four users, and 2*996 RUs corresponds to k user information fields, represented by 2*996(same, k).

[0196] Indeed, an m-bit sequence can represent one of several RUs assigned to n users with respect to MU-MIMO performed by n users, where n = 1 to 16. The example n = 4 is used only as an illustration. The specific value of n is not limited to this embodiment of the application.

[0197] (3) Downlink OFDMA transmission In conventional technology, to reduce the complexity of transmission and reception, only one RU can be assigned to one user / user group in OFDMA transmission.

[0198] One embodiment of this application further provides a method for assigning resources, in which multiple RUs can be assigned to a single user / user group.

[0199] Specific solution 1: Resource allocation methods allow for the assignment of multiple RUs to a single user. These methods include:

[0200] In the resource allocation table, an m-bit sequence indicates one of several RUs assigned to a user, and another m-bit sequence indicates one of several RUs assigned to another user.

[0201] For example, the m-bit sequence in the resource allocation table indicates 242 tone RUs among multiple RUs allocated to a user. Simply put, "242 (same, A)" is used to mark the m-bit sequence. Other m-bit sequences indicate one of multiple RUs allocated to other users. Simply put, "242 (same, B)" is used to mark the other m-bit sequence.

[0202] In the multi-user resource allocation shown in Figure 17, the resource allocation information (i.e., m-bit sequence) assigned to STA1 includes the first 20M, the third 20M, and the fourth 20M, and the resource allocation information corresponding to the three 20Ms can be represented as 242 (same, A), and the resource allocation information (i.e., m-bit sequence) assigned to STA2 includes the fifth 20M, the seventh 20M, and the eighth 20M, and the resource allocation information corresponding to the three 20Ms can be represented as 242 (same, B). The second and sixth 20Ms are 20Ms that are divided into smaller RUs. Assume that the resource allocation information (i.e., m-bit sequence) corresponding to the second 20M is represented using X, and the resource allocation information (i.e., m-bit sequence) corresponding to the sixth 20M is represented using Y. In a method for setting resource allocation information (i.e., m-bit sequences in a resource allocation table) for odd-numbered and even-numbered channels, the information conveyed by CC1 and CC2 is such that, for CC1, it includes 242(same, A), 242(same, A), 242(same, B), and 242(same, B), and for CC2, it includes X, 242(same, A), Y, and 242(same, B).

[0203] Optionally, CC1 further includes the user information fields of STA1, and CC2 further includes the user information fields of STA2. In other words, the information conveyed by CC1 and CC2 is as follows: for CC1, it includes 242 (same, A), 242 (same, A), 242 (same, B), 242 (same, B), and the user information fields of STA1; and for CC2, it includes X, 242 (same, A), Y, 242 (same, B), and the user information fields of STA2.

[0204] Naturally, CC1 may also include the user information fields of STA2, and CC2 may also include the user information fields of STA1.

[0205] Indeed, CC1 may, as an alternative, include the user information fields of STA1 and STA2, and CC2 may also include the user information fields of STA1 and STA2.

[0206] In this method, it should be understood that RUs in multiple RUs assigned to a user may be RUs of any size, for example, 242-tone RUs, 484-tone RUs, 996 RUs, or 2*996 RUs, and similarly, RUs in multiple RUs assigned to other users may be RUs of any size, for example, 242-tone RUs, 484-tone RUs, 996 RUs, or 2*996 RUs. During a single resource allocation, RUs of various sizes can be allocated in combination, depending on the specific case.

[0207] For example, the resource allocation in Figure 17 may be further shown as follows: In the case of CC1, 242 (same, A), 484 (same, A), 242 (same, B), 484 (same, B), and For CC2, X, 484 (same, A), Y, and 484 (same, B).

[0208] Here, 242 (same, A) represents an m-bit sequence, where the sequence represents 242 tone RUs in multiple RUs assigned to the user; 484 (same, A) represents an m-bit sequence, where the sequence represents 484 tone RUs in multiple RUs assigned to the user; 242 (same, B) represents an m-bit sequence, where the sequence represents 242 tone RUs in multiple RUs assigned to other users; and 484 (same, B) represents an m-bit sequence, where the sequence represents 484 tone RUs in multiple RUs assigned to other users.

[0209] Specific solution 2: Resource instruction methods include the following:

[0210] The m-bit sequence in the resource allocation table indicates one of several RUs assigned to a user, with 0 user fields corresponding to the RU. The m-bit sequence in the resource allocation table indicates one of several RUs assigned to a user, with 1 user field corresponding to the RU. The m-bit sequence in the resource allocation table indicates one of several RUs assigned to another user, with 0 user fields corresponding to the RU. The m-bit sequence in the resource allocation table indicates one of several RUs assigned to another user, with 1 user field corresponding to the RU.

[0211] For example, the m-bit sequence in the resource allocation table indicates a 242-tone RU in multiple RUs allocated to a user, where the number of user fields corresponding to the 242-tone RU is 0, and the m-bit sequence is represented using 242(same, A, 0). The m-bit sequence in the resource allocation table indicates one of multiple RUs allocated to a user, where the number of user fields corresponding to the RU is 1, and the m-bit sequence is represented using 242(same, A, 1). The m-bit sequence in the resource allocation table indicates one of multiple RUs allocated to another user, where the number of user fields corresponding to the RU is 0, and the m-bit sequence is represented using 242(same, B, 0). The m-bit sequence in the resource allocation table indicates one of multiple RUs allocated to another user, where the number of user fields corresponding to the RU is 1, and the m-bit sequence is represented using 242(same, B, 1).

[0212] If, by option, the user information fields of STA1 and STA2 are set for CC1, and the user information fields of STA1 and STA2 are also set for CC2, the resource allocation in Figure 17 may be further shown as follows.

[0213] For CC1, the fields are 242 (same, A, 1), 242 (same, A, 0), 242 (same, B, 1), 242 (same, B, 0), the user information field of STA1, and the user information field of STA2. For CC2, the fields are X, 242 (same, A, 1), Y, 242 (same, B, 1), the user information field of STA1, and the user information field of STA2.

[0214] In this method, it should be understood that RUs in multiple RUs assigned to a user may be RUs of any size, for example, 242-tone RUs, 484-tone RUs, 996 RUs, or 2*996 RUs, and similarly, RUs in multiple RUs assigned to other users may be RUs of any size, for example, 242-tone RUs, 484-tone RUs, 996 RUs, or 2*996 RUs. During a single resource allocation, RUs of various sizes can be allocated in combination, depending on the specific case.

[0215] Specific solution 3: Resource allocation methods allow for the assignment of multiple RUs to a single user group. These methods include:

[0216] The m-bit sequence in the resource allocation table indicates one of several RUs assigned to a user group.

[0217] For example, the m-bit sequence in the resource allocation table indicates a 242-tone RU in multiple RUs assigned to a user group. As shown in Figure 18, three 242-tone RUs (i.e., the 5th 20M, the 7th 20M, and the 8th 20M) are assigned to a user group (the user group includes STA2-STA5). Any of the three 242-tone RUs can be indicated using the m-bit sequence. Briefly, "242 (same, B, 4)" is used to mark the m-bit sequence.

[0218] In Figure 18, the first 20M, the third 20M, and the fourth 20M are assigned to user:STA1. Any one of the three 20M may be represented using another m bit sequence. Briefly, "242(same, A, 1)" is used to mark the other m bit sequence. The second and sixth 20M in Figure 18 are divided into m smaller RUs and may be represented respectively using existing bit sequences already used in 11ax. For brief explanation, the second and sixth 20M are marked with X and Y, respectively. Thus, the information conveyed in CC1 and CC2 in Figure 18 includes, for CC1, 242(same, A, 1), 242(same, A, 1), 242(same, B, 4), and 242(same, B, 4), and for CC2, X, 242(same, A, 1), Y, and 242(same, B, 4).

[0219] Optionally, if CC1 further includes the user information fields STA1 to STA5, then CC2 further includes a second 20M user information field and a sixth 20M user information field. The information conveyed by CC1 and CC2 is as follows: in the case of CC1, 242(same, A, 1), 242(same, A, 1), 242(same, B, 4), 242(same, B, 4), the user information field of STA1, the user information field of STA2, the user information field of STA3, the user information field of STA4, and the user information field of STA5; in the case of CC2, X, 242(same, A, 1), Y, 242(same, B, 4), the second 20M user information field, and the sixth 20M user information field.

[0220] In the above, different stations to which multiple RUs are assigned are identified by changing the identifiers A and B. Furthermore, in another embodiment, identifiers A and B are assigned separately to two stations to which multiple RUs are assigned. If it is necessary to indicate more stations to which multiple RUs are assigned, for example three stations, more identifiers, for example A, B, and C, are required for distinction.

[0221] All solutions in (1), (2), and (3) describe the information conveyed in CC1 and CC2. CC1 and CC2 are contained in the EHT-SIG field. The EHT-SIG field is contained in the PPDU. See Figure 11 for the structure of the PPDU.

[0222] In the communication process, the transmitting end generates and transmits a PPDU. The PPDU includes an EHT-SIG field. The EHT-SIG field includes CC1 and CC2. For information conveyed in CC1 and CC2, please refer to the various specific solutions in (1), (2), and (3).

[0223] Solutions (1), (2), and (3) all use a bit sequence to indicate one of several RUs assigned to a single user / user group, as well as a punctured channel in relation to an existing 242(0).

[0224] In addition to this method, it should be understood that bitmaps may also be used to indicate punctured channels. A bandwidth puncturing bitmap is appended to the EHT common field. For example, a 4-bit bitmap is used for an 80M bandwidth, and a 16-bit or 15-bit bitmap is used for a 320MHz bandwidth. One bit in the bitmap is set to a first value to indicate that the corresponding 20M is punctured, or to a second value to indicate that the corresponding 20M is not punctured. Alternatively, one bit in the bitmap is set to a first value to indicate that the corresponding 20M is not punctured, or to a second value to indicate that the corresponding 20M is punctured. The bandwidth puncturing bitmap is described in detail in (4) below.

[0225] The bandwidth puncturing bitmap may also be a bandwidth puncturing mode as described in detail in (4) below.

[0226] Alternatively, resource allocation information in the EHT common field may be omitted. For example, the bandwidth puncturing bitmap or bandwidth puncturing mode in the EHT common field may be omitted. In addition, the bandwidth field in the U-SIG is replaced with the bandwidth and puncturing mode fields. This will be explained in detail in (4) below.

[0227] A bandwidth puncturing bitmap, a bandwidth puncturing mode, or a method of bandwidth and puncturing mode is preferably used in solutions (1) and (2), and optionally in solution (3).

[0228] In all of the solutions in (1), (2), and (3), it should be further understood that the m-bit sequence is not limited to the m-bit sequence in the resource allocation table. The m-bit sequence may be any other form of m-bit sequence.

[0229] (4) Uplink full bandwidth MU-MIMO punctured transmission In this embodiment, a method of instruction is provided for uplink full-bandwidth MU-MIMO punctured transmission to avoid the following case, namely, bandwidth puncture, which results in multiple discontinuous resource blocks being allocated separately to MU-MIMO user groups, and consequently, the user information fields of users within the MU-MIMO user group being repeated multiple times. The full-bandwidth multi-user MU-MIMO punctured transmission shown in Figure 14 is an example. The AP allocates 40M, including a first 20M, a third 20M, and a fourth 20M, separately to STA1-STA4. In this case, the trigger frame transmitted by the AP must contain eight user information fields. Four of the eight user information fields contain the four user information fields of STA1-STA4 to which the first 20M is allocated separately. The remaining four user information fields contain the four user information fields of STA1-STA4 to which the 40M, including the third and fourth 20M, is allocated separately.

[0230] It appears that the trigger frame sent by the AP needs to include eight user information fields. This wastes a lot of resources.

[0231] This embodiment provides an instruction method for uplink full-bandwidth MU-MIMO punctured transmission. The method includes the following:

[0232] A trigger frame is generated and sent. The trigger frame has the following characteristics:

[0233] 1. The trigger type field of the trigger frame may indicate an uplink full-bandwidth MU-MIMO punctured transmission. Alternatively, a bit or field may be appended to the common information field of the trigger frame, and the bit or field may indicate an uplink full-bandwidth multi-user MU-MIMO punctured transmission. In addition, uplink full-bandwidth MU-MIMO punctured transmission optionally further includes a special case, namely, an uplink full-bandwidth single-user punctured transmission. Uplink full-bandwidth MU-MIMO punctured transmission may further be understood as indicating that the user information field includes a bandwidth puncturing bitmap field or a bandwidth puncturing mode field. Optionally, the RU assignment indicator field may not be included.

[0234] 2. The RU assignment field in the user information field is replaced with the bandwidth puncturing bitmap field or the bandwidth puncturing mode field. Each 20M is represented using 1 bit. For example, an 80M bandwidth is represented using a 4-bit bitmap, and a 320MHz bandwidth is represented using a 16-bit bitmap. One bit in the bitmap is set to a first value to indicate that the corresponding 20M is punctured, or to a second value to indicate that the corresponding 20M is not punctured. Alternatively, one bit in the bitmap is set to a first value to indicate that the corresponding 20M is not punctured, or to a second value to indicate that the corresponding 20M is punctured. Alternatively, the length of the bandwidth puncturing bitmap does not change with bandwidth. For example, the length of the bandwidth puncturing bitmap is 16 bits. In other forms, one bit may be removed from the puncturing bitmap in the above forms because puncturing is not permitted for the primary 20M channel within the bandwidth. For example, the length of the bandwidth puncturing bitmap does not change with bandwidth. In this case, the length of the bandwidth puncturing bitmap is 15 bits. It does not include an indication of whether the primary 20M is punctured or not. Each 20M within the bandwidth indicated by the bandwidth puncturing bitmap is arranged from high frequency to low frequency or from low frequency to high frequency.

[0235] The bandwidth puncturing mode field is also used to indicate a specific punctured 20MHz within the bandwidth. In this case, for ease of implementation, the modes indicated by the bandwidth puncturing mode field are limited. Puncture is not performed for any one or more of the 20MHz. The modes may include the following (a specific table is provided below):

[0236] [Table 3A] [Table 3B]

[0237] Because the puncturing modes indicated by the bandwidth puncturing mode field are limited, the modes included in the table above require only 6 bits for indication. If more puncturing modes are subsequently included, the length of the bandwidth puncturing mode field may be 7 bits, 8 bits, 9 bits, or any other number of bits.

[0238] In another embodiment, the multiple puncturing modes indicated by the bandwidth puncturing mode field vary with bandwidth. The bandwidth is indicated by the bandwidth field in the trigger frame. Specifically, if the bandwidth is 20M or 40M, there are no puncturing modes. In this case, the bandwidth puncturing mode field may be 0 bits. If the bandwidth is 80M, the modes indicated by the bandwidth puncturing mode field include mode numbers 1-4, which require 2 bits. If the bandwidth is 160M, the modes indicated by the bandwidth puncturing mode field include mode numbers 5-16, which require 4 bits. If the bandwidth is 240M, the modes indicated by the bandwidth puncturing mode field include mode numbers 17-25, which require 4 bits. If the bandwidth is 320M, the modes indicated by the bandwidth puncturing mode field include mode numbers 26-37, which require 4 bits. A preferred embodiment is that the modes indicated by the bandwidth puncturing mode field vary with bandwidth, but their length does not change. In the example above, the length of the bandwidth puncturing mode field is the maximum number of bits required for the entire bandwidth, i.e., 4. For example, if the bandwidth is 80M, the modes indicated by the bandwidth puncturing mode field include mode numbers 1 to 4. Here, values ​​0 to 3 in the 4-bit bandwidth puncturing mode field represent mode numbers 1 to 4, respectively. Other values ​​are reserved values.

[0239] It should be noted that a 160M bandwidth may include two 80M bands, which may not be consecutive, or a 160M bandwidth may include an adjacent 160M band. A 240M bandwidth may include a 160M and an 80M band, which may not be consecutive, or a 240M bandwidth may include an adjacent 240M band. A 320M bandwidth may include two 160M bands, which may not be consecutive, or a 320M bandwidth may include an adjacent 320M band.

[0240] The following provides a method for further reducing the signaling overhead of the trigger frame. In full-bandwidth puncturing mode, not only can the user information field that transmits duplicate AIDs be avoided, but the RU assignment instruction field / bandwidth puncturing bitmap field / bandwidth puncturing mode field of the user information field can also be omitted. Specifically, this is as follows:

[0241] 1. The trigger type field of the trigger frame may indicate an uplink full-bandwidth MU-MIMO punctured transmission. Uplink full-bandwidth MU-MIMO punctured transmission optionally further includes a special case, namely, an uplink full-bandwidth single-user punctured transmission.

[0242] 2. The user information field of the trigger frame does not include resource allocation information, such as the RU allocation field, the bandwidth puncturing bitmap field, or the bandwidth puncturing mode field.

[0243] 3. The bandwidth field in the common field of the trigger frame is replaced with either a bandwidth puncturing bitmap field or a bandwidth and puncturing mode field.

[0244] Uplink full bandwidth MU-MIMO punctured transmission can be further understood as indicating that the user information field does not include information regarding resource allocation, such as the bandwidth puncturing bitmap field, bandwidth and puncturing mode field, or RU allocation instruction field. Optionally, the common fields of the trigger frame include the bandwidth puncturing bitmap field or the bandwidth and puncturing mode field.

[0245] The bandwidth puncturing bitmap field is the same as in the method described above. However, in this case, the bandwidth puncturing bitmap field has a predetermined length, for example, 15 bits or 16 bits. The bandwidth puncturing bitmap can be all first values, for example, 1, to indicate that all 20M are not punctured. If the bandwidth puncturing bitmap contains consecutive 1s and the other values ​​are 0, it indicates that the bandwidth is not punctured.

[0246] Six non-punctured bandwidth modes, including 20M, 40M, 80M, 160, 240M, and 320M, are added to the puncturing modes in Table 1 with respect to the bandwidth and puncturing mode fields. In other words, at least 43 modes are included. The bandwidth and puncturing mode fields may be 6 bits. If more modes are subsequently included, the bandwidth and puncturing mode fields may be 7 bits, 8 bits, 9 bits, or any other number of bits.

[0247] It should be noted that the primary 20M within the bandwidth cannot be punctured.

[0248] When the full-bandwidth multi-user MU-MIMO punctured transmission shown in Figure 14 is represented using a trigger frame having the two characteristics described above, the trigger frame only needs to contain four user information fields, and the RU allocation field in each user information field is replaced with a bandwidth puncturing bitmap field.

[0249] Based on the same technical concept, one embodiment of this application provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions. When an instruction is executed by a computer, the computer is enabled to execute an information instruction method on the AP side in the embodiment of the method described above.

[0250] One embodiment of this application provides a computer program product including instructions. When the computer program product is executed on a computer, the computer is enabled to perform an embodiment of the method in either one of the first and second embodiments or any possible implementation of either embodiment.

[0251] One embodiment of this application further provides a chip system. The chip system includes a processor configured to support an AP in carrying out an information instruction method, such as generating or processing data and / or information in the embodiments described above. In a conceivable design, the chip system further includes memory. The memory is configured to store program instructions and data necessary for a data transmission device. The chip system may include a chip or a chip and other separate devices.

[0252] One embodiment of this application further provides a communication system. The system includes at least one first access point and at least one first STA in the embodiments described above.

[0253] As those skilled in the art will see, embodiments of this application may be provided as methods, systems, or computer program products. Accordingly, this application may take the form of hardware-only embodiments, software-only embodiments, or embodiments involving a combination of software and hardware. Furthermore, this application may take the form of a computer program product that includes computer-usable program code and is implemented on one or more computer-usable storage media (including, but not limited to, disk memory, optical memory, etc.).

[0254] This application is described in relation to flowcharts and / or block diagrams of methods, devices (systems), and computer program products relating to this application. It should be understood that computer program instructions may be used to implement each process and / or block in the flowchart and / or block diagram, as well as combinations of processes and / or blocks in the flowchart and / or block diagram. These computer program instructions may be given to a processor of a general-purpose computer, a dedicated computer, an embedded processor, or any other programmable data processing device to produce a machine, thereby the instructions executed by the processor of the computer or any other programmable data processing device produce a machine for implementing a particular function in one or more processes in the flowchart and / or one or more blocks in the block diagram.

[0255] These computer program instructions, which can instruct a computer or any other programmable data processing device to operate in a particular manner, can be stored in computer-readable memory, thereby producing an artifact that includes an instruction unit. The instruction unit implements a particular function in one or more processes of a flowchart and / or one or more blocks of a block diagram.

[0256] These computer program instructions may be loaded into a computer or other programmable data processing device, thereby executing a series of operations and steps on the computer or other programmable device, resulting in computer-implemented processing. Therefore, instructions executed on a computer or other programmable device provide steps for implementing specific functions in one or more processes in a flowchart and / or one or more blocks in a block diagram.

[0257] Clearly, a person skilled in the art can make various modifications and variations to this application without departing from its scope. This application is intended to cover these modifications and variations to the same extent as provided for by the following claims and their equivalent art. [Explanation of symbols]

[0258] 2201 Processing Module 2202 Transceiver Module

Claims

1. A general-purpose processor for instructing information, comprising a processing circuit and an output interface internally connected to the processing circuit and communicating with the processing circuit, The processing circuit is configured to generate a physical layer protocol data unit (PPDU), the preamble of the PPDU includes a U-SIG field, the U-SIG field includes first instruction information indicating the transmission mode of the PPDU, the transmission mode of the PPDU includes single-user full-bandwidth transmission, single-user full-bandwidth punctured transmission, full-bandwidth MU-MIMO transmission, full-bandwidth MU-MIMO punctured transmission, or OFDMA transmission. The first instruction information is transmitted in a PPDU format field and a puncturing field. The PPDU format field indicates the format of the PPDU, and the PPDU format includes single-user PPDU, MU-MIMO PPDU, or OFDMA PPDU. The puncturing field indicates whether or not to perform punctured transmission. The output interface is configured to transmit the PPDU. General-purpose processor.

2. If the puncturing field is a bandwidth puncturing bitmap field, then the bits in the bandwidth puncturing bitmap field correspond to 20M, the first value of the bit in the bandwidth puncturing bitmap field indicates that the corresponding 20M is punctured, and the second value of the bit in the bandwidth puncturing bitmap field indicates that the corresponding 20M is not punctured. If the puncturing field is a bandwidth puncturing mode field, the bandwidth puncturing mode field indicates a puncturing mode in which different 20Ms are punctured with different bandwidths. The general-purpose processor according to claim 1.

3. The general-purpose processor according to claim 1 or 2, wherein the general-purpose processor further comprises a storage medium, the storage medium being configured to store instructions to be executed by the processing circuit.

4. The general-purpose processor according to any one of claims 1 to 3, wherein the preamble of the PPDU includes an EHT-SIG field, the EHT-SIG field includes a common field and a user-specific field, the user-specific field includes one or more user fields, and the user field includes a station association identifier (AID).

5. The general-purpose processor according to claim 4, wherein when the first instruction information indicates the single-user full-bandwidth transmission or the single-user full-bandwidth punctured transmission, the user-specific field includes one user field.

6. The general-purpose processor according to claim 4, wherein when the first instruction information indicates the single-user full-bandwidth transmission, the single-user full-bandwidth punctured transmission, the full-bandwidth MU-MIMO transmission, or the full-bandwidth MU-MIMO punctured transmission, the common field does not include resource allocation information.

7. The general-purpose processor according to claim 4, wherein when the first instruction information indicates the OFDMA transmission, the common field includes resource allocation information.

8. The general-purpose processor according to claim 7, wherein the resource allocation information includes one or more bit sequences, the one or more bit sequences indicating that a spectral resource is divided into several sets of resource units, the set of resource units includes one or more resource units, and the set of resource units is allocated to one or more stations.

9. The general-purpose processor according to claim 8, wherein the bit sequence occupies 9 bits.

10. The general-purpose processor according to claim 8, wherein the bit sequence is used to indicate the size and location of a plurality of sets of resource units.

11. The general-purpose processor according to claim 8, wherein the resource allocation information is further used to indicate the last resource unit of the set of resource units to be allocated to the previous STA in two adjacent STAs.

12. The first instruction information is conveyed in the PPDU format field and the puncturing field. The PPDU format field indicates the format of the PPDU, and the format of the PPDU includes a single-user PPDU, a full-bandwidth MU-MIMO PPDU, or an OFDMA PPDU. The puncturing field occupies multiple bits, and the value of one of those bits indicates that the PPDU is not punctured. A general-purpose processor according to any one of claims 1 to 11.

13. The general-purpose processor according to any one of claims 1 to 12, wherein the PPDU further includes a second instruction information, the second instruction information is used to indicate the number of STAs.

14. A general-purpose processor for instructing information, comprising a processing circuit and an output interface internally connected to the processing circuit and communicating with the processing circuit, The output interface is configured to receive a Physical Layer Protocol Data Unit (PPDU), the preamble of the PPDU includes a U-SIG field, the U-SIG field includes first instruction information indicating the transmission mode of the PPDU, the transmission mode of the PPDU includes single-user full-bandwidth transmission, single-user full-bandwidth punctured transmission, full-bandwidth MU-MIMO transmission, full-bandwidth MU-MIMO punctured transmission, or OFDMA transmission. The first instruction information is transmitted in a PPDU format field and a puncturing field. The PPDU format field indicates the format of the PPDU, and the PPDU format includes single-user PPDU, MU-MIMO PPDU, or OFDMA PPDU. The puncturing field indicates whether or not to perform punctured transmission. The processing circuit is configured to determine the transmission mode of the PPDU according to the first instruction information. General-purpose processor.

15. If the puncturing field is a bandwidth puncturing bitmap field, then the bits in the bandwidth puncturing bitmap field correspond to 20M, the first value of the bit in the bandwidth puncturing bitmap field indicates that the corresponding 20M is punctured, and the second value of the bit in the bandwidth puncturing bitmap field indicates that the corresponding 20M is not punctured. If the puncturing field is a bandwidth puncturing mode field, the bandwidth puncturing mode field indicates a puncturing mode in which different 20Ms are punctured with different bandwidths. The general-purpose processor according to claim 14.

16. The general-purpose processor according to claim 14, wherein the general-purpose processor further comprises a storage medium, the storage medium being configured to store instructions to be executed by the processing circuit.

17. The general-purpose processor according to any one of claims 14 to 16, wherein the preamble of the PPDU includes an EHT-SIG field, the EHT-SIG field includes a common field and a user-specific field, the user-specific field includes one or more user fields, and the user field includes a station association identifier (AID).

18. The general-purpose processor according to claim 17, wherein when the first instruction information indicates the single-user full-bandwidth transmission or the single-user full-bandwidth punctured transmission, the user-specific field includes one user field.

19. The general-purpose processor according to claim 17, wherein when the first instruction information indicates the single-user full-bandwidth transmission, the single-user full-bandwidth punctured transmission, the full-bandwidth MU-MIMO transmission, or the full-bandwidth MU-MIMO punctured transmission, the common field does not include resource allocation information.

20. The general-purpose processor according to claim 17, wherein when the first instruction information indicates the OFDMA transmission, the common field includes resource allocation information.

21. The general-purpose processor according to claim 20, wherein the resource allocation information includes one or more bit sequences, the one or more bit sequences indicating that a spectral resource is divided into several sets of resource units, the set of resource units includes one or more resource units, and the set of resource units is allocated to one or more stations.

22. The general-purpose processor according to claim 21, wherein the bit sequence occupies 9 bits.

23. The general-purpose processor according to claim 21, wherein the bit sequence is used to indicate the size and location of a plurality of sets of resource units.

24. The general-purpose processor according to claim 21, wherein the resource allocation information is further used to indicate the last resource unit of the set of resource units to be allocated to the previous STA in two adjacent STAs.

25. The first instruction information is conveyed in the PPDU format field and the puncturing field. The PPDU format field indicates the format of the PPDU, and the format of the PPDU includes a single-user PPDU, a full-bandwidth MU-MIMO PPDU, or an OFDMA PPDU. The puncturing field occupies multiple bits, and the value of one of those bits indicates that the PPDU is not punctured. A general-purpose processor according to any one of claims 14 to 24.

26. The general-purpose processor according to any one of claims 14 to 25, wherein the PPDU further includes a second instruction information, the second instruction information is used to indicate the number of STAs.

Images