Terminals and access points (APs)

Abstract

To improve the efficiency of frequency resource allocation. [Solution] The terminal comprises a receiving circuit that receives a trigger frame including a user information field that includes resource unit (RU) allocation information and first information indicating a combination of RUs, and a control circuit that controls the transmission of an uplink signal using the combination of RUs, wherein the RU allocation information and the first information indicate an RU combination number that indicates one of the RU allocation candidates in the list of RU configuration information defined in the standard, and the user information field identifies the combination of RUs by indicating the size and position of the multiple RUs that constitute the combination of RUs.

Description

Technical Field

[0001] This disclosure relates to a terminal and a communication method.

Background Art

[0002] The Institute of Electrical and Electronics Engineers (IEEE) is advancing the study of the standard IEEE 802.11be for the next-generation wireless local area network (LAN), which is a successor standard to IEEE 802.11ax of IEEE 802.11. IEEE 802.11be is also called, for example, Extream High Throughput (EHT).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the method of allocating frequency resources in wireless communication such as Wi-Fi has not been sufficiently considered.

[0005] Non-limiting embodiments of this disclosure contribute to providing terminals and communication methods that can improve the efficiency of frequency resource allocation. [Means for solving the problem]

[0006] A terminal according to one embodiment of the present disclosure comprises a receiving circuit that receives first information relating to a plurality of resource units in a resource allocation candidate, and a control circuit that controls communication using the resource units based on the first information.

[0007] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media. [Effects of the Invention]

[0008] According to one embodiment of the present disclosure, the efficiency of frequency resource allocation can be improved.

[0009] Further advantages and effects of one embodiment of this disclosure will be made apparent from the specification and drawings. Such advantages and / or effects are provided by several embodiments and features described in the specification and drawings, but not all of them are necessarily provided in order to obtain one or more identical features. [Brief explanation of the drawing]

[0010] [Figure 1] This diagram shows an example of a signaling format in Downlink (DL) Orthogonal Frequency Division Multiple Access (OFDMA). [Figure 2]Figure showing an example of Resource Unit (RU) Allocation [Figure 3] Figure showing an example of the format of a Trigger frame [Figure 4] Figure showing an example of RU Allocation [Figure 5] Figure showing an example of RU allocation in Uplink (UL) OFDMA [Figure 6] Figure showing an example of RU allocation [Figure 7] Figure showing an example of RU Allocation [Figure 8] Block diagram showing a partial configuration example of an AP according to Embodiment 1 [Figure 9] Block diagram showing a partial configuration example of a STA according to Embodiment 1 [Figure 10] Block diagram showing a configuration example of an AP according to Embodiment 1 [Figure 11] Block diagram showing a configuration example of a STA according to Embodiment 1 [Figure 12] Figure showing an example of a signaling format in DL OFDMA [Figure 13] Figure showing an example of RU allocation according to Method 1 [Figure 14] Figure showing an example of RU allocation according to Method 2 [Figure 15] Figure showing an example of RU allocation according to Method 3 [Figure 16] Figure showing an example of a signaling format according to Method 4 [Figure 17] Figure showing an example of a signaling format according to Method 5 [Figure 18] Figure showing an example of RU allocation according to Method 6 [Figure 19] Figure showing an example of RU Allocation according to Method 6 [Figure 20] Figure showing an example of RU allocation according to Method 7 [Figure 21] Figure showing an example of RU allocation according to Method 8 [Figure 22] Figure showing an example of RU allocation according to Method 8 [Figure 23] A diagram showing an example of RU allocation related to Method 8. [Modes for carrying out the invention]

[0011] Each embodiment of this disclosure will be described in detail below with reference to the drawings.

[0012] IEEE 802.11be, for example, explores methods for allocating multiple Resource Units (RUs) to a single STA (also called a Station or terminal) in continuous or discontinuous frequency domains in Orthogonal Frequency Division Multiple Access (OFDMA) transmission (see, for example, Non-Patent Documents 1-4). This RU allocation can improve frequency utilization efficiency.

[0013] In IEEE 802.11ax, for example, consecutive RU allocation is possible in the frequency domain, but discontinuous RU allocation is not supported. Also, in IEEE 802.11ax, the method of notifying information regarding RU allocation differs between downlink (DL) OFDMA and uplink (UL) OFDMA (see, for example, Non-Patent Document 5).

[0014] For example, Figure 1 shows an example of a signaling format for DL ​​OFDMA in IEEE 802.11ax.

[0015] As shown in Figure 1, information regarding RU allocation is notified, for example, in the Common field containing common information shared by multiple users (or STAs) within the HE-SIG-B field of the High Efficiency (HE) preamble. Also, in Figure 1, the RU allocation information results in the allocation of one RU to one STA. For example, the Common field within the HE-SIG-B field may contain an RU Allocation subfield. The RU Allocation subfield may contain, for example, common RU allocation information for multiple STAs to be allocated. For example, the RU Allocation subfield may notify information regarding the size of the RU and the location of the RU in the frequency domain (in other words, information regarding the RU configuration). Also, for example, as shown in Figure 1, the RU notified in the RU Allocation subfield may be allocated to multiple users (or STAs) within the HE-SIG-B field according to the order of the User fields corresponding to each STA, which are contained in the User Specific field containing individual user information for each STA. Note that the RU configuration may be rephrased as, for example, "RU settings".

[0016] Figure 2 shows an example of information regarding the size of the RU and the position of the RU in the frequency domain, as notified in the RU Allocation subfield within the HE preamble. For example, if the value in the RU Allocation subfield shown in Figure 1 is 8 (binary: 00001000), then eight RUs, including a 52-tone RU (e.g., a RU composed of RU#1 and RU#2) and a 26-tone RU (each composed of RU#3 to RU#9), may be assigned to multiple STAs. Alternatively, for example, based on the order of the User fields corresponding to each STA in the User Specific field (e.g., STA1, STA2 in Figure 1), the 52-tone RU shown in Figure 2 may be assigned to STA1, and the 26-tone RU (RU#3) may be assigned to STA2. Similarly, if the value in the RU Allocation subfield is 8, the RU may be assigned to another STA (e.g., STA8).

[0017] Figure 3 shows an example of a signaling format for UL OFDMA in IEEE 802.11ax.

[0018] As shown in Figure 3, information regarding RU allocation is notified in the RU Allocation subfield within the Per User Info field, which is an individual STA field within the User Info List field of the Trigger frame. In UL OFDMA, for example, multiple consecutive RUs can be assigned to a single STA. Figure 4 shows an example of information regarding the size of the RU and the location of the RU in the frequency domain (in other words, information regarding the configuration of the RU) notified in the RU Allocation subfield of the Trigger frame. For example, one RU may be designated to an STA with a granularity of 26 tones or more within 80 MHz (in other words, RU size).

[0019] For example, as shown in Figure 5, if 4 (binary: 00000100) is specified for STA1 in the RU Allocation subfield, STA1 may be assigned the 5th 26-tone RU. Also, for example, as shown in Figure 5, if 39 (binary: 00100111) is specified for STA2 in the RU Allocation subfield, STA2 may be assigned the 3rd 52-tone RU. Similarly, for example, as shown in Figure 5, if 40 (binary: 00101000) is specified for STA3 in the RU Allocation subfield, STA3 may be assigned the 4th 52-tone RU.

[0020] The above explains how to notify information regarding RU allocation in DL and UL under IEEE 802.11ax.

[0021] Here, we describe one method of assigning multiple RUs to a single STA, for example, based on the IEEE 802.11ax signaling format (e.g., Figure 1). Figure 6 shows an example of the format of the User Specific field in this method.

[0022] For example, the same STA identification information (e.g., STA ID in DL, association identifier (AID) in UL) may be set in multiple User fields (see, for example, Non-Patent Document 2). For example, the User Specific field shown in Figure 6 contains two User fields each corresponding to STA1 and STA2. Also, for example, if RU Allocation subfield=6 (binary: 00000110) in the HE preamble is notified as shown in Figure 7, RUs may be assigned in the order of STA1, STA2, STA1 and STA2 based on the User Specific field shown in Figure 6. This method makes it possible to assign multiple RUs to a single STA. For example, in Figure 7, it is possible to assign two non-contiguous RUs to each STA.

[0023] However, this method can increase the amount of signaling per STA because multiple User fields are set for a single STA to which multiple RUs are assigned. For example, an increase in the amount of signaling per STA can increase overhead and decrease throughput. In a single User Block field shown in Figure 1 or Figure 6, for example, the User field consists of 21 bits, the Cyclic Redundancy Check (CRC) field consists of 4 bits, and the tail bit field consists of 6 bits. In other words, a single User Block field shown in Figure 1 or Figure 6 can consist of at least 31 bits. Therefore, if two or more User fields are set for a single STA, for example as shown in Figure 6, the amount of signaling can increase by at least 31 bits compared to the IEEE 802.11ax format (e.g., Figure 1).

[0024] Therefore, in one embodiment of this disclosure, a method for assigning multiple RUs to a single STA while suppressing an increase in the signaling amount is described.

[0025] (Embodiment 1) [Configuration of the wireless communication system] The wireless communication system according to this embodiment includes at least one AP100 and at least one STA200.

[0026] Figure 8 is a block diagram showing a partial configuration example of AP100 according to one embodiment of the present disclosure. In the AP100 shown in Figure 8, the wireless transceiver 104 (corresponding to, for example, a transmission circuit) transmits first information (for example, RU allocation information described later) regarding multiple RUs for one terminal (for example, STA200) in a resource allocation candidate (for example, RU candidate). The control unit 101 controls communication using the RUs based on the first information.

[0027] FIG. 9 is a block diagram showing a partial configuration example of the STA200 according to an embodiment of the present disclosure. In the STA200 shown in FIG. 9, a wireless transmission / reception unit 202 (for example, corresponding to a reception circuit) receives first information (for example, RU allocation information described later) regarding a plurality of RUs in a resource allocation candidate (for example, an RU candidate). A control unit 204 (for example, corresponding to a control circuit) controls communication using the RU based on the first information.

[0028] <Configuration example of AP100> FIG. 10 is a block diagram showing a configuration example of the AP100. The AP100 shown in FIG. 10 includes, for example, a control unit 101, a data transmission processing unit 102, an allocation unit 103, a wireless transmission / reception unit 104, an antenna 105, an extraction unit 106, and a data reception processing unit 107.

[0029] The control unit 101 may perform scheduling for the STA200 in at least one of DL and UL, for example. The control unit 101 may determine parameters such as the number of STA200s (for example, the multiplicity) to which a resource (for example, an RU) is allocated, the frequency bandwidth, or the frequency resources allocated to each STA200. Based on the determined parameters, the control unit 101 may generate, for example, a control signal (for example, a preamble) instructing the reception of a downlink signal for the STA200. Also, based on the determined parameters, the control unit 101 may generate a control signal (for example, a Trigger frame) instructing the transmission of an uplink signal for the STA200.

[0030] Note that an example of the RU allocation method will be described later.

[0031] The control unit 101 outputs the generated control signal (for example, an EHT preamble or a Trigger frame) to the wireless transmission / reception unit 104, for example. Also, the control unit 101 may output information regarding the resource allocation of downlink data to the allocation unit 103 and output information regarding the resource allocation of uplink data to the extraction unit 106, for example.

[0032] The data transmission processing unit 102 performs transmission processing such as encoding and modulation on the input transmission data (for example, downstream data), and outputs the data signal after the transmission processing to the allocation unit 103.

[0033] The allocation unit 103 allocates (or maps, in other words) the data signal input from the data transmission processing unit 102 to a resource (for example, RU) based on the information regarding resource allocation of the downstream data input from the control unit 101, and outputs the signal after mapping to the wireless transceiver unit 104.

[0034] The wireless transceiver unit 104 communicates with the STA 200, for example. For example, the wireless transceiver unit 104 performs wireless transmission processing on the data signal (for example, downstream data) input from the allocation unit 103 or the control signal (for example, preamble or Trigger frame) input from the control unit 101, and transmits a wireless signal from the antenna 105. For example, the wireless transceiver unit 104 may multiplex (for example, time-division multiplex) the data signal and the control signal (for example, preamble).

[0035] Also, for example, the wireless transceiver unit 104 performs wireless reception processing on the wireless signal received by the antenna 105, and outputs the received signal after the wireless reception processing to the extraction unit 106.

[0036] The extraction unit 106 extracts the received data signal corresponding to each STA 200 from the received signal input from the wireless transceiver unit 104 based on the information regarding resource allocation of the upstream data input from the control unit 101, and outputs it to the data reception processing unit 107.

[0037] The data reception processing unit 107 may perform reception processing such as demodulation and decoding on the received data signal input from the extraction unit 106, and output the signal after the reception processing (for example, received data).

[0038] <Configuration example of STA200> Figure 11 is a block diagram showing an example configuration of the STA200. The STA200 shown in Figure 11 includes, for example, an antenna 201, a wireless transmitting / receiving unit 202, an extraction unit 203, a control unit 204, a data receiving processing unit 205, a data transmission processing unit 206, and an allocation unit 207.

[0039] The wireless transceiver unit 202 communicates with, for example, AP100. The wireless transceiver unit 202 performs wireless reception processing on the wireless signal received by the antenna 201 and outputs the received signal after wireless reception processing to the extraction unit 203. Also, for example, the wireless transceiver unit 202 performs wireless transmission processing on the data signal (for example, uplink data) input from the allocation unit 207 and transmits a wireless signal from the antenna 201.

[0040] The extraction unit 203 extracts (in other words, detects) control signals (e.g., preamble or trigger frame) from the received signal input from the wireless transceiver unit 202 and outputs them to the control unit 204. The extraction unit 203 also extracts data from the received signal and outputs it to the data reception processing unit 205.

[0041] The control unit 204 determines, for example, the resources (e.g., RU) allocated to the STA200 for downlink data, or the resources (e.g., RU) allocated to the STA200 for uplink data, based on the control signal input from the extraction unit 203. The control unit 204 may, for example, output information regarding resource allocation for downlink data to the data reception processing unit 205, and output information regarding resource allocation for uplink data to the allocation unit 207.

[0042] Examples of RU allocation methods will be discussed later.

[0043] The data reception processing unit 205 extracts a signal destined for STA200 from the data portion input from the extraction unit 203, for example, based on resource allocation information for the downlink data input from the control unit 204. The data reception processing unit 205 then performs reception processing such as demodulation and decoding on the extracted signal and may output the signal after reception processing (for example, received data).

[0044] The data transmission processing unit 206 performs transmission processing such as encoding and modulation on the input transmission data (e.g., uplink data), and outputs the processed data signal to the allocation unit 207.

[0045] The allocation unit 207, for example, assigns (or maps) the data signal input from the data transmission processing unit 206 to a resource (e.g., RU) based on the resource allocation information for the uplink data input from the control unit 204, and outputs the mapped signal to the wireless transceiver unit 202.

[0046] [RU allocation method] Figure 12 shows an example of a signaling format for DL ​​according to this embodiment. The signaling format shown in Figure 12 is based on the IEEE 802.11be signaling format as an example, but is not limited to this.

[0047] The EHT-SIG field in the preamble shown in Figure 12 (e.g., EHT preamble) may include, for example, a field containing information common to multiple STA200s (e.g., EHT-SIG-common field) and a field containing user-specific information for each STA (e.g., EHT-SIG-per user field).

[0048] Furthermore, the EHT-SIG-common field (in other words, the user common field) shown in Figure 12 may include, for example, a field containing information about the configuration of the RU (e.g., RU configuration information) (e.g., RU configuration information subfield). The RU configuration information may include, for example, information about the size of the RU and the location of the RU in the frequency domain. In other words, the RU configuration information may include, for example, information about RU candidates that can be assigned to STA200 (in other words, resource assignment candidates).

[0049] Furthermore, the EHT-SIG-per user field shown in Figure 12 may include, for example, one or more User Block fields. Each User Block field may include, for example, User fields corresponding to one or two STA200s (in Figure 12, for example, User field#STA1 corresponding to STA1 and User field#STA2 corresponding to STA2). In addition, each User field (in other words, individual user field) may include a field containing, for example, information about the RU assigned to the corresponding STA200 (hereinafter referred to as RU assignment information) (for example, RU assignment information subfield). The RU assignment information may include, for example, information about the RU assigned to the STA200 from among the RU candidates notified by the RU configuration information.

[0050] The following describes an example of how to allocate RUs based on RU configuration information and RU allocation information.

[0051] [Method 1] In Method 1, AP100 may notify STA200 of information regarding the RU to be assigned, for example, by the RU assignment information contained in the User field, in bitmap format. In other words, the RU assignment information includes bitmap information indicating whether or not an assignment is made to STA200 (e.g., User) among multiple RU candidates (e.g., resource assignment candidates) notified by the RU configuration information.

[0052] For example, RU assignment information may consist of bits corresponding to each of the multiple candidates for the RU indicated in the RU configuration information notified in the Common field (e.g., the EHT-SIG-common field). The value of the bit corresponding to each candidate RU (e.g., 0 or 1) may be determined based on whether or not it is assigned to STA200. For example, bit=0 may indicate that the RU corresponding to that bit is not assigned to STA200, and bit=1 may indicate that the RU corresponding to that bit is assigned to STA200. The relationship between the bit value and whether or not an RU is assigned may also be reversed.

[0053] Figure 13 shows an example of RU configuration information, RU allocation information, and RU allocation results related to Method 1.

[0054] In Figure 13, as an example, the RU configuration information can be assumed to be the definition of the RU Allocation subfield for DL ​​in IEEE 802.11ax. The RU configuration information shown in Figure 13 corresponds, for example, to IEEE 802.11ax DL RU Allocation subfield = 6 (binary: 00000110). In other words, in the example in Figure 13, the RU configuration notified by the RU configuration information is a pattern in which the frequency arrangement of RU#1,2,4,6,7 consists of 26 tones and the frequency arrangement of RU#3,5 consists of 52 tones in a 20MHz bandwidth.

[0055] Note that the RU configuration shown in the RU configuration information is not limited to the example shown in Figure 13. For example, it may be an RU configuration corresponding to a value other than RU Allocation subfield=6 for DL ​​in IEEE 802.11ax, or it may be an RU configuration other than the RU configuration for DL ​​in IEEE 802.11ax.

[0056] Furthermore, in the IEEE 802.11ax DL RU Allocation subfield, RUs are numbered in units of 26 tones (for example, RU#1 to RU#9 in Figure 2), but here, one RU number may be assigned to 52-tone RUs. For example, in Figure 13, RU#3 and RU#5 are assigned to the 52-tone RUs, respectively. Therefore, in the example shown in Figure 13, the range of assignable RU numbers in a 20MHz bandwidth is RU#1 to #7. Note that the range of RU numbers (in other words, the number of RU candidates) may differ depending on the RU configuration information (for example, the value of the RU Allocation subfield (6 in Figure 13)).

[0057] Furthermore, the RU allocation information shown in Figure 13 may include information (e.g., information in bitmap format) indicating the RU number to be assigned to the STA200 from among RU#1 to #7 notified by the RU configuration information. For example, as shown in Figure 13, if RU#[2,3] (e.g., bitmap: 0110000) is specified for a certain STA200 by the RU allocation information as in Case 1, then the frequency resources of RU#2 and RU#3 may be allocated to that STA200. Similarly, if RU#[5,6] (e.g., bitmap: 0000110), RU#[2,5] (e.g., bitmap: 0100100), or RU#[3,6] (e.g., bitmap: 0010010) is specified for an STA200 by the RU allocation information as in Cases 2 to 3, it indicates that each STA is assigned to the frequency arrangement of the specified RU.

[0058] Thus, according to Method 1, AP100 notifies STA200 of the assigned RU number in bitmap format based on the RU assignment information in the User field. RU assignment in bitmap format improves flexibility in RU assignment, for example. For instance, as shown in Figure 13, one or more RUs can be assigned to a single STA200 using RU assignment information contained in a single User field. Furthermore, this RU assignment information allows for the setting of RU assignments with consecutive frequency configurations, as in Cases 1 and 2 shown in Figure 13, and also allows for the setting of RU assignments with discontinuous frequency configurations, as in Cases 3 and 4.

[0059] Furthermore, Method 1 can suppress the increase in signaling amount in RU allocation and improve throughput. For example, in the example shown in Figure 13, the number of signaling bits in the RU allocation information included in the User field is 7 bits (for example, bits corresponding to RU#1 to RU#7). Therefore, the increase in the number of signaling bits in the RU allocation information according to Method 1 is 24 bits less than the increase in the number of signaling bits in the method described above (for example, Figure 6) (for example, an increase of 31 bits).

[0060] [Method 2] In Method 2, for example, the combination of RUs that can be assigned to one STA200 may be set (e.g., limited) from all possible combinations of RUs. Furthermore, AP100 may notify information about the combination of RUs that can be assigned to STA200 from among the RU combinations, for example, by RU assignment information contained in the User field. In other words, the RU assignment information includes information about one of several combinations of several RU candidates (e.g., resource assignment candidates) notified by the RU configuration information.

[0061] For example, the RU assignment information may include information identifying the combination of RUs to be assigned to STA200 (e.g., RU combination number) and information indicating the frequency domain arrangement of the RUs corresponding to the RU combination assigned to STA200 (e.g., either continuous assignment or non-continuous assignment).

[0062] Figure 14 shows an example of RU configuration information, RU allocation information, and RU allocation results related to Method 2.

[0063] In Figure 14, as an example, the RU configuration information may be assumed to be the definition of the RU Allocation subfield for DL ​​in IEEE 802.11ax, similar to Method 1 (Figure 13). The RU configuration information shown in Figure 14 corresponds, for example, to IEEE 802.11ax DL RU Allocation subfield = 6 (binary: 00000110). In other words, in the example in Figure 14, the RU configuration notified by the RU configuration information is a pattern in which the frequency arrangement of RU#1,2,4,6,7 consists of 26 tones and the frequency arrangement of RU#3,5 consists of 52 tones in a 20MHz bandwidth.

[0064] Note that the RU configuration shown in the RU configuration information is not limited to the example shown in Figure 14. For example, it may be an RU configuration corresponding to a value other than RU Allocation subfield=6 for DL ​​in IEEE 802.11ax, or an RU configuration other than the RU configuration for DL ​​in IEEE 802.11ax.

[0065] Furthermore, the RU allocation information shown in Figure 14 may include, for example, information regarding the RU combination number and the frequency arrangement method (continuous or discontinuous). For example, in Figure 14, four types of combinations (e.g., Case 1 to 4) are set for the RU combination, including two types of continuous allocation and two types of discontinuous allocation. For example, the RU allocation information allows for the setting of RU allocations with continuous state-ren configurations, as in Cases 1 and 2 shown in Figure 14, and RU allocations with discontinuous frequency configurations, as in Cases 3 and 4.

[0066] Furthermore, the association between U combination numbers #1 and #2 notified by RU allocation information and the RU numbers in the RU configuration notified by RU configuration information (RU#1 to #7 in Figure 14) may be notified, for example, from AP100 to STA200, or may be specified in the standard.

[0067] Thus, according to Method 2, a combination of RUs that can be assigned to one STA200 is set from all possible combinations of RUs. Then, AP100 notifies the STA200 of the RU combination number and frequency allocation, for example, using the RU assignment information in the User field. This RU assignment can suppress the increase in the signaling amount in RU assignment and improve throughput. For example, in the example shown in Figure 14, the number of signaling bits in the RU assignment information included in the User field is 2 bits (for example, 4 cases from Case 1 to 4). Therefore, the increase in the number of signaling bits in the RU assignment information according to Method 2 is 29 bits less than the increase in the number of signaling bits in the method described above (for example, Figure 6) (for example, an increase of 31 bits).

[0068] Figure 14 illustrates the case where the RU combination number and frequency allocation (continuous or non-continuous allocation) are notified to the STA200 by the RU allocation information, but it is not limited to this. For example, the RU allocation information may notify some combinations of RUs (for example, RU#1 to RU#7 in Figure 14) that are notified by the RU configuration information. For example, it may include RU combinations that correspond to either continuous or non-continuous allocation.

[0069] Furthermore, while Figure 14 illustrates the case where, for example, two RUs are assigned to STA200 by RU allocation information, it is not limited to this, and one or three or more RUs may be notified by RU allocation information. Also, for example, the number of associated RUs may differ depending on the RU combination number.

[0070] Furthermore, the RU allocation information does not limit the number of RU combinations that can be assigned to STA200 to four; it may be two, three, or even five or more combinations.

[0071] [Method 3] In Method 3, for example, AP100 may notify STA200 whether or not multiple combinations of RUs are assigned to STA200 (in other words, whether or not there are RU combinations) based on the RU assignment information contained in the User field. In other words, the RU assignment information includes information indicating whether or not a combination of multiple RU candidates (e.g., resource assignment candidates) notified by the RU configuration information is used for the assignment of STA200 (e.g., user).

[0072] Here, the combination patterns of multiple RUs can be classified into categories such as small-size RUs (e.g., 26, 52, 106 tones) with a bandwidth of less than 20 MHz, and large-size RUs (e.g., 242, 484, 996 tones) with a bandwidth of 20 MHz or more, and the RU combinations can be set to combinations of RUs within each category.

[0073] Method 3 assumes, as an example, a combination of RUs with a large RU size of 20 MHz (for example, 242 tones) or more.

[0074] Figure 15 shows an example of RU configuration information, RU allocation information, and RU allocation results related to Method 3.

[0075] In Figure 15, as an example, the RU configuration information can be assumed to be the definition of the RU Allocation subfield for DL ​​in IEEE 802.11ax. The RU configuration information shown in Figure 15 corresponds, for example, to RU Allocation subfield=192-199 (binary: 11000y2y1y0) [242 tone] and RU Allocation subfield=200-207 (binary: 11001y2y1y0) [484 tone]. In other words, in the example in Figure 15, the RU configuration notified by the RU configuration information is a pattern in which 242 tones equivalent to a 20MHz bandwidth and 484 tones equivalent to a 40MHz bandwidth are defined one each within an 80MHz bandwidth.

[0076] Note that the RU configuration shown in the RU configuration information is not limited to the example shown in Figure 15. For example, it may be an RU configuration corresponding to values ​​other than 192-199 and 200-207 of the RU Allocation subfield for DL ​​in IEEE 802.11ax, or it may be an RU configuration other than the RU configuration for DL ​​in IEEE 802.11ax.

[0077] Furthermore, for example, the frequency arrangement of the two RUs (e.g., RU#1 and RU#2), such as the 242-tone RU and the 484-tone RU, as notified by the RU configuration information, can be one of the four patterns shown in Figure 15.

[0078] Furthermore, the RU assignment information shown in Figure 15 may include information indicating, for example, whether the combination of RU#1 and RU#2 notified by the RU configuration information is assigned to STA200 (in other words, whether the combination exists or not). For example, in Figure 15, there is one type of RU combination within the 80MHz bandwidth: a 242-tone RU and a 484-tone RU. Therefore, STA200 can recognize the RU assigned to it (for example, whether the RU combination exists or not) based on the RU assignment information indicating the presence or absence of the RU combination.

[0079] For example, as shown in Figure 15, if the RU assignment information indicates that there is a RU combination, STA200 may determine that the RU combination notified by the RU configuration information (e.g., RU#1 and RU#2) is assigned to STA200. On the other hand, if the RU assignment information indicates that there is no RU combination, STA200 may determine that each of the RUs notified by the RU configuration information (e.g., RU#1 and RU#2) is assigned to a different STA.

[0080] Thus, according to Method 3, if there is only one combination of RUs, AP100 notifies STA200 of the presence or absence of an RU combination to be assigned using the RU assignment information in the User field. This RU assignment can, for example, suppress the increase in the signaling amount in RU assignment and improve throughput. For example, in the example shown in Figure 15, the number of signaling bits in the RU assignment information included in the User field is 1 bit (e.g., present or absent). Therefore, the increase in the number of signaling bits in the RU assignment information according to Method 3 is 30 bits less than the increase in the number of signaling bits in the method described above (e.g., Figure 6) (e.g., an increase of 31 bits).

[0081] In Figure 15, we have illustrated the case where information regarding the presence or absence of RU combinations is included in the User field. However, information regarding the presence or absence of RU combinations may also be indicated by the RU configuration information in the Common field. For example, information regarding the presence or absence of RU combinations, or information regarding OFDMA and non-OFDMA in the Common field, may be added to the RU Allocation subfield, as in the example described in Method 6 below, or it may be added to a field different from the RU Allocation subfield.

[0082] Furthermore, while Figure 15 illustrates the case where there is only one RU combination pattern (in other words, one type of RU combination), there may be two or more RU combination patterns.

[0083] Furthermore, although this embodiment describes combinations of RUs in the Large-size RU category, the combinations of RUs are not limited to these. For example, the combination of RUs may be a combination of RUs in the Small-size RU category, or a combination of RUs in both the Large-size RU and Small-size RU categories.

[0084] [Method 4] In Method 4, for example, control information for switching the RU allocation method based on the RU allocation information contained in the User field may be notified in the Common field or User field. In other words, for example, the STA200 may receive information indicating the configuration of the RU allocation information (in other words, the allocation type) and control communication according to the configuration of the RU allocation information indicated by that information.

[0085] Figure 16 shows an example of a signaling format for DL ​​related to Method 4.

[0086] As shown in Figure 16, for example, an allocation type that switches the RU allocation method may be provided in the RU allocation information field (e.g., RU assignment information subfield) of the User field. STA200 may, for example, switch the definition of the RU assignment value based on the allocation type.

[0087] For example, any of methods 1 to 3 may be set as the method for allocating RUs. In the example in Figure 16, method 2 and method 3 are switched depending on the allocation type. For example, in Figure 16, if allocation type = 0, the RU allocation method using method 2 may be set, and if allocation type = 1, the RU allocation method using method 3 may be set.

[0088] Furthermore, if the size of the RU allocation information is fixed regardless of the allocation type (in other words, the method of allocating RUs), padding bits may be added to make the size consistent, as shown in Figure 16. Also, although the example in Figure 16 shows the case where the allocation type is placed within the RU allocation information in the User field, the allocation type may be included in a field different from the RU allocation information in the User field, in the RU configuration information in the Common field, or in a field different from the RU configuration information in the Common field.

[0089] According to Method 4, for example, by switching between RU allocation methods such as Methods 1 to 3, scheduling flexibility can be improved while suppressing the increase in signaling bits.

[0090] While Method 4 describes the case where the assignment type is included in the Common field or User field for notification, the assignment type may also be implicitly notified to the STA200 based on other information, for example. For example, if the frequency bandwidth to be allocated to the STA200 is less than 20 MHz, the STA200 may determine that Method 2 (or Method 1) is set, and if the frequency bandwidth is 20 MHz or more, the STA200 may determine that Method 3 is set, and switch the RU assignment method based on the RU assignment information.

[0091] [Method 5] In Method 5, RU configuration information does not need to be included in the packet containing RU assignment information for, for example, STA200.

[0092] For example, RU configuration information may be notified to STA200 before RU assignment information is notified. For example, AP100 may send a beacon containing RU configuration information to STA200.

[0093] Alternatively, the RU configuration information may be pre-configured in, for example, STA200, or it may be defined (in other words, specified) in the specification (or standard).

[0094] As an example, Method 5 may be applied to RU allocation for Trigger frames in UL OFDMA. Figure 17 shows an example of the configuration of a Trigger frame in UL OFDMA according to Method 5.

[0095] The Common Info field shown in Figure 17 does not necessarily have to include, for example, RU configuration information. As mentioned above, RU configuration information may be notified to the STA200 by a beacon, or it may be defined in the specification.

[0096] Furthermore, as shown in Figure 17, the Per User Info field may include, for example, RU allocation information corresponding to any of the methods 1 to 4 described above. In Figure 17, as an example, the Per User Info field may include information about the allocation type (e.g., Allocation Type subfield) and RU allocation information corresponding to that allocation type (e.g., RU Allocation subfield). Note that in Figure 17, as an example, RU allocation information related to Method 4 (e.g., including allocation type and RU allocation value) is explained, but the RU allocation method is not limited to Method 4, but may also be any of Methods 1 to 3, or Methods 6 to 8 described later. In the case of Methods 1 to 3, for example, the allocation type shown in Figure 17 may not be included.

[0097] For example, each STA200 may identify the RU to be assigned to it based on the RU configuration information it holds and the RU assignment information notified by the Trigger frame. In other words, even with UL, similar to DL in methods 1 to 4 or methods 6 to 8 described above, it is possible to assign multiple RUs, such as sequential or non-sequential assignments, based on the RU assignment information notified in a single Per User Info field (e.g., individual user information) corresponding to the STA200.

[0098] Therefore, according to Method 5, for example, even in Trigger frames in UL OFDMA, it is possible to suppress the increase in the amount of signaling related to RU allocation and improve throughput.

[0099] [Method 6] In Method 6, AP100 may, for example, notify RU configuration information in the Common field, which shows the RU configuration (e.g., RU candidates or resource allocation candidates) and combinations of RU candidates (e.g., a list of RU combinations), and notify information that identifies the combination to be assigned to STA200 (e.g., RU combination number) based on the RU allocation information contained in the User field.

[0100] Figure 18 shows an example of RU configuration information, RU allocation information, and RU allocation results related to Method 6.

[0101] In Figure 18, as an example, the RU configuration information can be assumed to be the definition of the RU Allocation subfield for DL ​​in IEEE 802.11ax. The RU configuration information shown in Figure 18 corresponds, for example, to RU Allocation subfield = 6 (binary: 00000110) for DL ​​in IEEE 802.11ax.

[0102] Furthermore, the RU configuration information shown in Figure 18 may include, for example, RU combination information relating to combinations of multiple RU candidates. The RU combination information may be defined, for example, in the undefined area of ​​the RU Allocation subfield for DL ​​in IEEE 802.11ax.

[0103] Figure 19 shows an example of RU configuration information related to Method 6. In Figure 19, the RU configuration information assumes, for example, the definition of the RU Allocation subfield, and the RU Allocation subfield may be included as RU configuration information in the EHT-SIG-common field. For example, in the RU Allocation subfield for DL ​​in IEEE 802.11ax, there are 52 undefined entries (in other words, undefined entries) (e.g., RU Allocation subfield=116-127 and 216-255). Therefore, for example, RU combination information may be added to these undefined entries. That is, some of the values ​​in the RU Allocation subfield indicate an RU configuration that does not include the allocation of multiple RU combinations, similar to the case of IEEE 802.11ax, and certain values ​​different from the values ​​that indicate an RU configuration that does not include the allocation of multiple RU combinations indicate a specific RU configuration that includes the allocation of multiple RU combinations.

[0104] In the example shown in Figure 19, RU combination information indicating RU combinations related to methods 1 to 3 may be included. For example, in Figure 19, RU combination information indicating combinations of 26-tone RUs and 52-tone RUs, which are small-size RUs with a bandwidth of less than 20 MHz, may be defined in RU Allocation subfield = 116 and 117. Also, for example, in Figure 19, RU combination information indicating combinations of 242-tone RUs and 484-tone RUs, which are large-size RUs with a bandwidth of 20 MHz or more, may be defined in RU Allocation subfield = 216 and 217.

[0105] In Figure 19, "-A" and "-B" indicate that they are pairs of the same combination. For example, "-A" in Figure 19 may correspond to the combination with RU combination number = 1 shown in Figure 18, and "-B" in Figure 19 may correspond to the combination with RU combination number = 2 shown in Figure 18.

[0106] Furthermore, the RU combinations are not limited to the examples shown in Figure 19, and may include, for example, some or all of the RU combinations defined in the IEEE 802.11be specification. Also, the pattern of the RU Allocation subfield may include unassigned information.

[0107] For example, the RU configuration information shown in Figure 18 may include RU configurations corresponding to RU Allocation subfield=6, and RU combinations corresponding to RU Allocation subfield=116 or 117.

[0108] Furthermore, the RU assignment information shown in Figure 18 may include, for example, information indicating the RU combination number assigned to each STA200 from among the RU combinations in RU#1 to RU#7 notified by the RU configuration information.

[0109] For example, in Figure 18, if the RU configuration information specifies RU Allocation subfield = 116 (e.g., Figure 19) for a combination of RUs with a consecutive frequency arrangement, and the RU allocation information notifies RU combination number = 1, then STA200 may determine that the RUs corresponding to RU combination number 1 of the consecutive RU arrangement (e.g., RU#2 and RU#3) are the allocated RUs. Similarly, if the RU configuration information specifies RU Allocation subfield = 116 (e.g., Figure 19) and the RU allocation information notifies RU combination number = 2, then STA200 may determine that the RUs corresponding to RU combination number 2 of the consecutive RU arrangement (e.g., RU#5 and RU#6) are the allocated RUs (not shown).

[0110] Furthermore, for example, in Figure 18, if the RU configuration information specifies RU Allocation subfield = 117 (for example, Figure 19) for a discontinuous frequency arrangement of RU combinations, and the RU allocation information notifies RU combination number = 2, then STA200 may determine that the RUs corresponding to RU combination number 2 of the discontinuous RU arrangement (for example, RU#3 and RU#6) are the allocated RUs. Similarly, if the RU configuration information specifies RU Allocation subfield = 117 (for example, Figure 19) and the RU allocation information notifies RU combination number = 1, then STA200 may determine that the RUs corresponding to RU combination number 1 of the discontinuous RU arrangement (for example, RU#2 and RU#5) are the allocated RUs (not shown).

[0111] Thus, according to Method 6, by including RU combination information (in other words, a list of RU combinations) in the Common field, the increase in the amount of signaling related to RU assignment in the User field can be suppressed, and throughput can be improved. For example, in the example shown in Figure 18, the number of signaling bits for the RU assignment information in the User field is 1 bit. Therefore, the increase in the number of signaling bits for the RU assignment information according to Method 6 is 30 bits less than the increase in the number of signaling bits in the method described above (for example, Figure 6) (for example, an increase of 31 bits).

[0112] Although Figures 18 and 19 illustrate combinations of one or two RUs, the number of RUs included in an RU combination may be three or more.

[0113] [Method 7] In Method 7, AP100 may, for example, notify information regarding the RU assignments of multiple STA200s (in other words, multiple users) in each of the RU assignment information contained in the User field corresponding to each STA200.

[0114] In other words, the User field (in other words, the user-specific field) received by a certain STA200 and the User field for another STA may each be set with RU assignment information for that STA200.

[0115] Figure 20 shows an example of RU configuration information, RU allocation information, and allocation results related to Method 7.

[0116] In Figure 20, as an example, the RU configuration information may be assumed to be the same as in Embodiment 1, where it is the definition of the RU Allocation subfield for DL ​​in IEEE 802.11ax. The RU configuration information shown in Figure 20 corresponds, for example, to IEEE 802.11ax DL RU Allocation subfield = 6 (binary: 00000110). In other words, in the example in Figure 20, the RU configuration notified by the RU configuration information is a pattern in which the frequency arrangement of RU#1,2,4,6,7 consists of 26 tones and the frequency arrangement of RU#3,5 consists of 52 tones in a 20MHz bandwidth.

[0117] Note that the RU configuration shown in the RU configuration information is not limited to the example shown in Figure 20. For example, it may be an RU configuration corresponding to a value other than 6 for the DL RU Allocation subfield in IEEE 802.11ax, or it may be an RU configuration other than the RU configuration for DL ​​in IEEE 802.11ax.

[0118] Furthermore, the RU assignment information shown in Figure 20 may include, for example, information (e.g., RU numbers) regarding the RUs assigned to each of the multiple STA200s from among RU#1 to #7 notified by the RU configuration information.

[0119] For example, as shown in Figure 20, RU allocation information can be notified in (a) bitmap format and (b) RU allocation table format.

[0120] (a) In bitmap format, the RU assignment information may include, for example, information indicating the RU number (in other words, the assigned RU) that is assigned to each of the multiple STA200s from among the RUs notified by the RU configuration information.

[0121] For example, the bit sequences (e.g., 7 bits) corresponding to each of the seven RU#1 to RU#7 notified by the RU configuration information may be included for multiple STA200s. In the example bitmap format shown in Figure 20, the RU assignment information may consist of 14 bits (7 bits x 2 users) indicating whether each of RU#1 to RU#7 is assigned to STA1 and STA2.

[0122] For example, in Case 1 shown in Figure 20, the assigned RU numbers for STA1 are 2 and 3 (bits corresponding to RU#2 and #3 are ON; for example, bitmap: 0110000), and the assigned RU numbers for STA2 are 5 and 6 (bits corresponding to RU#5 and #6 are ON; for example, bitmap: 0000110). This allows each STA200 to identify, for example, that a pair of consecutive RU numbers 2 and 3 in the frequency domain is the assigned RU for STA1, and a pair of consecutive RU numbers 5 and 6 in the frequency domain is the assigned RU for STA2.

[0123] Furthermore, in Case 2 shown in Figure 20, for example, the assigned RU numbers for STA1 are 2 and 5 (bits corresponding to RU#2 and #5 are ON; for example, bitmap: 0100100), and the assigned RU numbers for STA2 are 3 and 6 (bits corresponding to RU#3 and #6 are ON; for example, bitmap: 0010010). This allows each STA200 to identify, for example, that a discontinuous pair of RU numbers 2 and 5 in the frequency domain is the assigned RU for STA1, and a discontinuous pair of RU numbers 3 and 6 in the frequency domain is the assigned RU for STA2.

[0124] Furthermore, in (b) the RU assignment table format, for example, an assignment pattern (or assignment status) for each STA200 (in other words, each user) to each RU (e.g., RU#1 to #7) may be defined, as shown in Figure 20. The association between RUs and users may be represented, for example, in a table. The RU assignment information may include, for example, a number that identifies the association between RUs and users (for example, called the RU assignment table number).

[0125] In the example in Figure 20, for the RU allocation corresponding to RU allocation table number = 1, the assigned RU numbers for user 1 (e.g., STA1) are the pair of RU numbers 2 and 3, and the assigned RU numbers for user 2 (e.g., STA2) are the pair of RU numbers 5 and 6. This allows each STA200 to identify, for example, that the pair of consecutive RU numbers 2 and 3 in the frequency domain is the assigned RU for STA1, and the pair of consecutive RU numbers 5 and 6 in the frequency domain is the assigned RU for STA2.

[0126] Furthermore, in the example in Figure 20, in the RU allocation corresponding to RU allocation table number 2, the assigned RU numbers for user 1 (e.g., STA1) are the pair of 2 and 5, and the assigned RU numbers for user 2 (e.g., STA2) are the pair of 3 and 6. This allows each STA200 to identify, for example, that the discontinuous pair of RU numbers 2 and 5 in the frequency domain is the assigned RU for STA1, and the discontinuous pair of RU numbers 3 and 6 in the frequency domain is the assigned RU for STA2.

[0127] Thus, according to Method 7, the STA200 can identify the RU assignments for multiple STA200s by, for example, reading the RU assignment information contained in one of the User fields corresponding to multiple STA200s.

[0128] Furthermore, Method 7 can, for example, suppress the increase in the signaling amount for RU allocation and improve throughput.

[0129] For example, in the bitmap format example shown in Figure 20, the signaling bits of the RU assignment information included in the User field (e.g., RU assignments for two STAs) are 14 bits. Therefore, the increase in the signaling bits of the RU assignment information in the bitmap format of Method 7 is 17 bits less than the increase in the signaling bits in the method described above (e.g., Figure 6) (e.g., an increase of 31 bits).

[0130] Furthermore, in the example of the RU assignment table format shown in Figure 20, the number of signaling bits for the RU assignment information (e.g., 4 patterns of RU assignment status) included in the User field is 2 bits. Therefore, the increase in the number of signaling bits for the RU assignment information in the RU assignment table format of Method 7 is 29 bits less than the increase in the number of signaling bits in the method described above (e.g., Figure 6) (e.g., an increase of 31 bits).

[0131] Furthermore, in IEEE 802.11ax DL, for example, the number of User fields included in the User Specific field is equal to the number of RUs notified by RU Allocation, and the order of User fields corresponding to each STA indicates the position of the RU assigned to each STA. Thus, in IEEE 802.11ax DL, the RU assignment to an STA is determined based on the order of User fields included in the User Specific field. For example, if an STA misdecodes a certain User field, it may not be able to determine the RU assignment for that STA or other STAs. In other words, each STA may not be able to determine the RU based on the information of a single User field (for example, the User field corresponding to each STA).

[0132] On the other hand, according to Method 7, even if each STA200 fails to decode one User field, if it succeeds in decode other User fields, it is possible to identify the RU assignment for each of the multiple STA200s. In other words, according to Method 7, the assigned RU for each STA200 can be identified regardless of the order of the User fields included in the User Specific field.

[0133] Note that the associations between RUs and STAs (or Users) in the bitmap-format RU assignment information and the RU assignment table-format RU assignment information shown in Figure 20 are examples only and are not limited to these. For example, the bitmap-format or RU assignment table-format RU assignment information may contain a mixture of STAs to which consecutive RUs are assigned and STAs to which non-contiguous RUs are assigned. Also, the number of RUs assigned to each STA may differ in the bitmap-format or RU assignment table-format RU assignment information. Furthermore, in the RU assignment table-format RU assignment information, all possible combinations of RU assignments for multiple STAs (in other words, associations between RUs and STAs) may be defined, or only some of the possible combinations of RU assignments may be defined.

[0134] [Method 8] In Method 8, AP100 may notify STA200 of the start position of the RU to be assigned (e.g., also called the start RU) and the end position of the RU (e.g., also called the end RU) by RU assignment information included in the User field. Alternatively, the RU assignment information may include the length of the RU to be assigned to STA200 (e.g., also called the RU length) instead of the end RU.

[0135] STA200 may, for example, convert the RU number notified by the RU allocation information according to a prescribed rule.

[0136] The following explains methods 1-3 for determining RU as an example.

[0137] In the following example, the RU configuration information can be assumed to be the definition of the RU Allocation subfield for DL ​​in IEEE 802.11ax. Below, as an example, we will explain the case where the RU configuration information corresponds to, for example, IEEE 802.11ax DL RU Allocation subfield = 0 (binary: 00000000). In other words, in the following example, the RU configuration notified by the RU configuration information is a pattern consisting of 26 tones of RU#1 to #9 in a 20MHz bandwidth.

[0138] Note that the RU configuration shown in the RU configuration information may be an RU configuration corresponding to a value other than RU Allocation subfield=0 for DL ​​in IEEE 802.11ax, or an RU configuration other than the RU configuration for DL ​​in IEEE 802.11ax.

[0139] <Decision method 1> Figure 21 shows an example of RU configuration information, RU allocation information, and RU allocation results related to determination method 1.

[0140] The RU allocation information shown in Figure 21 may include, for example, information regarding the start RU (e.g., RU start number) and end RU (e.g., end RU number) or RU length of the RU assigned to STA200.

[0141] In Figure 21, the range of start and end RUs (or RU length) that can be notified by the RU allocation information may be set to, for example, the range of RUs notified by the RU configuration information (e.g., 1 to 9).

[0142] STA200 may control communication using RU numbers obtained by cyclically shifting RU numbers from a starting RU number to an ending RU number. Alternatively, STA200 may control communication using RU numbers obtained by cyclically shifting RU numbers within a range from a starting RU number to an RU length.

[0143] As an example of the settings in Figure 21, let's explain the case where the starting RU is 4 and the ending RU is 9 (or 6 in the case of RU length). In this case, for example, the virtual RU allocation range may be set to the range of RU numbers #4 to #9 (for example, also called virtual RU numbers). The STA200 may calculate the actual allocated RU numbers by performing a cyclic shift of a specified number (in other words, a cyclic shift amount) on the virtual RU numbers. In Figure 21, since the cyclic shift amount is set to 3, three RUs are allocated to each end of the 20MHz bandwidth for the STA200.

[0144] According to determination method 1, the cyclic shift of assigned RUs makes it possible to assign discontinuous RUs in the frequency domain, thereby improving scheduling flexibility.

[0145] <Decision method 2> Method 2 describes the case where the "wrap around" method is applied.

[0146] Figure 22 shows an example of RU configuration information, RU allocation information, and RU allocation results related to determination method 2.

[0147] The RU allocation information shown in Figure 22 may include, for example, information regarding the start RU (e.g., start RU number) and end RU (e.g., end RU number) or RU length of the RU assigned to STA200.

[0148] In Figure 22, the range of start and end RUs (or RU length) that can be notified by the RU allocation information may be set to, for example, the range of RUs notified by the RU configuration information (e.g., 1 to 9).

[0149] For example, if the ending RU number is smaller than the starting RU number, STA200 may control communication using the RUs from the starting RU number to the final RU number and the RUs from the first RU number to the ending RU number. Alternatively, if the RU length from the starting RU number to the final RU number (e.g., referred to as the first RU length) is shorter than the RU length notified by the RU allocation information (e.g., referred to as the second RU length), STA200 may control communication using the RUs from the starting RU number to the final RU number and the RUs from the first RU number to RU numbers within the range of (second RU length - first RU length).

[0150] As an example of the settings in Figure 22, let's explain the case where the starting RU is 7 and the ending RU is 3 (6 in the case of RU length). In this example, the position of the ending RU is smaller than the position of the starting RU. Therefore, the STA200 may set the RU assignment range to include, for example, the range from the starting RU (RU#7) to the final RU (RU#9 in Figure 22), and the range from the beginning (in other words, the first) RU (RU#1 in Figure 22) to the ending RU (RU#3).

[0151] Furthermore, for example, if the RU length is notified by RU allocation information, STA200 may calculate the end RU as follows. End RU = mod (Start RU + RU length - 1, Total RU count)

[0152] For example, in the example in Figure 22, the end RU = mod(7+6-1, 9) = 3. In other words, in the example in Figure 22, STA200 is allocated a total of 6 RUs: 3 RUs from the start RU#7 to the final RU#9, and 3 RUs from the first RU#1 to RU#3, which corresponds to the remaining 3 RUs of the notified RU length of 6.

[0153] According to decision method 2, the wrap-around method allows for the allocation of discontinuous RUs in the frequency domain, thereby improving scheduling flexibility.

[0154] <Decision method 3> Figure 23 shows an example of RU configuration information, RU allocation information, and RU allocation results related to determination method 3.

[0155] The RU allocation information shown in Figure 23 may include, for example, multiple combinations (two sets in Figure 23) of the start and end RUs (or RU lengths) of the RUs allocated to STA200. In other words, the RU allocation information may notify of multiple consecutive regions (for example, also called clusters) in the frequency domain.

[0156] Furthermore, among the multiple RUs for STA200, the length of the continuous region in the frequency domain (e.g., number of RUs, RU length, or RU size) may be set to a specified value (e.g., 2RU) or less.

[0157] For example, in Figure 23, the range of the start RU and end RU (or RU length) may be set to the range of RUs notified by the RU configuration information (e.g., 1 to 9).

[0158] As an example of the settings in Figure 23, we will explain the case where the starting RU_1 is 2, the ending RU_1 is 3 (2 if RU length), the starting RU_2 is 7, and the ending RU_2 is 7 (1 if RU length).

[0159] As shown in Figure 23, the discontinuous RUs of RU#2, #3, and #7 can be assigned to a single STA200. Furthermore, the RU length of the region composed of RU#2 and RU#3 is 2RU, and the RU length of the region composed of RU#7 is 1RU, both of which are less than or equal to the specified value of 2RU.

[0160] According to determination method 3, RUs can be assigned to discontinuous regions in the frequency domain, improving scheduling flexibility. Furthermore, in determination method 3, for example, the increase in the number of signaling bits can be suppressed by setting the RU length to below a specified value.

[0161] The above explains the decision methods 1 to 3.

[0162] Thus, according to Method 8, AP100 notifies STA200 of the start and end RUs (or RU length) of the RUs to be assigned, based on the RU assignment information in the User field. STA200 (e.g., the user) then determines the actual assigned RUs according to the prescribed rules based on the RU numbers notified by the RU assignment information. Method 8 can suppress the increase in the amount of RU assignment signaling and improve throughput.

[0163] For example, in Figure 21 (Determination Method 1) and Figure 22 (Determination Method 2), the range of the start RU and end RU (or RU length) is 1 to 9, so the number of bits for each of the start RU and end RU (or RU length) is 4 bits, and the number of signaling bits for the RU assignment information of each User field is 8 bits. Therefore, the increase in the number of signaling bits for the RU assignment information shown in Figures 21 and 22 is 23 bits less than the increase in the number of signaling bits in the method described above (for example, Figure 6) (for example, an increase of 31 bits).

[0164] Furthermore, for example, in Figure 23 (Determination Method 3), the range of the start RU and end RU (or RU length) is 1 to 9, and the length of the contiguous region (RU length) is set to 2 or less. Therefore, the number of bits for the start RU is 4 bits, and the number of bits for the RU length is 1 bit. Thus, the number of signaling bits for the RU assignment information of each User field shown in Figure 23 is 5 × 2 = 10 bits. Consequently, the increase in the number of signaling bits for the RU assignment information shown in Figure 23 is 21 bits less than the increase in the number of signaling bits in the method described above (for example, Figure 6) (for example, an increase of 31 bits).

[0165] The above explains methods 1 through 8.

[0166] As described above, according to this embodiment, AP100 transmits RU allocation information for multiple RUs for a single STA200 in a candidate RU (in other words, a candidate resource allocation), and controls communication using the RUs based on the RU allocation information. STA200 also receives RU allocation information for multiple RUs in a candidate RU (in other words, a candidate resource allocation), and controls communication using the RUs based on the RU allocation information.

[0167] As a result, AP100 can assign multiple RUs (e.g., consecutive RUs or discontinuous RUs) to a single STA200 in the RU assignment information within a single User field corresponding to that STA200. Therefore, according to this embodiment, compared to the method described above (e.g., Figure 6), for example, the increase in the number of signaling bits in the User field can be suppressed and throughput can be improved. Thus, according to this embodiment, the increase in the amount of signaling can be suppressed and multiple RUs can be assigned to a single STA200, improving the efficiency of frequency resource allocation.

[0168] The embodiments of this disclosure have been described above.

[0169] (Other embodiments) In the embodiments described above, the case in which RU configuration information is included in the Common field and RU assignment information is included in the User field was explained, but the invention is not limited to this. For example, RU configuration information may be included in the User field of the DL. In other words, RU configuration information does not have to be included in the Common field.

[0170] Furthermore, in the embodiments described above, the same RU assignment method (in other words, RU designation method) may be applied to both DL and UL.

[0171] For example, the UL OFDMA trigger frame may be extended to include multiple RU combination information in the Per User Info field. Alternatively, a format similar to the extended UL OFDMA trigger frame may be applied to DL OFDMA.

[0172] As another example, for UL OFDMA, similar to the DL OFDMA format shown in Figure 12, common information for the STA (e.g., Common field) may include RU configuration information within the channel bandwidth (e.g., RU configuration information: size and location of each RU), while individual user information (e.g., User field) may include RU assignment information consisting of multiple RU numbers included in the RU configuration. Alternatively, for example, the Common Info of the Trigger frame may include RU configuration information similar to that of DL. This reduces the size of User Info information and thus the overall signaling overhead.

[0173] Furthermore, the parameters such as frequency bandwidth and RU combinations shown in the above-described embodiment are merely examples, and the same method as in the above-described embodiment can be applied to frequency bandwidth and RU combinations different from those exemplified. For example, the frequency bandwidth may be set to any of 20MHz, 40MHz, 80MHz, 160MHz, 240MHz, and 320MHz, or other frequency bandwidths may be set. Also, for example, the RU combination may be a combination of multiple RUs of at least one size from 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, and 996-tone RU. Moreover, the RU size is not limited to these and may be other sizes.

[0174] Furthermore, although the above embodiment was described based on the IEEE 802.11be format as an example, the format to which one embodiment of this disclosure is applied is not limited to the IEEE 802.11be format. One embodiment of this disclosure can also be applied, for example, to IEEE 802.11bd (NGV (Next Generation V2X)), which is the next-generation standard to the automotive standard 802.11p.

[0175] This disclosure can be implemented in software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be implemented in part or in whole as an integrated circuit (LSI), and each process described in the above embodiments may be controlled in part or in whole by a single LSI or a combination of LSIs. An LSI may consist of individual chips, or it may consist of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the degree of integration, LSIs may be referred to as ICs, system LSIs, super LSIs, or ultra LSIs.

[0176] The method of integration is not limited to LSIs; it may also be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (Field Programmable Gate Arrays) that can be programmed after LSI manufacturing, or reconfigurable processors that allow for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used. This disclosure may be implemented as digital or analog processing.

[0177] Furthermore, if advancements in semiconductor technology or other derived technologies lead to the emergence of integrated circuit technologies that replace LSIs, then naturally, it would be possible to use those technologies to integrate functional blocks. The application of biotechnology, for example, is a possibility.

[0178] This disclosure is applicable to all types of devices, systems, and equipment having communication capabilities (collectively referred to as communication equipment). Communication equipment may include a radio transceiver and a processing / control circuit. A radio transceiver may include a receiver and a transmitter, or both as functions. A radio transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar. Non-exclusive examples of communication devices include telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, vehicles or mobile transport with communication capabilities (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

[0179] Communication devices are not limited to portable or movable devices, but also include all kinds of non-portable or fixed devices, devices, and systems, such as smart home devices (appliances, lighting equipment, smart meters or measuring instruments, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0180] Communication includes data communication via cellular systems, wireless LAN systems, and communication satellite systems, as well as data communication using combinations of these.

[0181] Furthermore, the communication device also includes devices such as controllers and sensors that are connected to or linked to a communication device that performs the communication functions described in this disclosure. For example, this includes controllers and sensors that generate control signals and data signals used by the communication device that performs the communication functions of the communication device.

[0182] Furthermore, communication equipment includes infrastructure facilities such as base stations, access points, and any other devices, devices, and systems that communicate with or control the aforementioned non-limited types of equipment.

[0183] A terminal according to one embodiment of the present disclosure comprises a receiving circuit that receives first information relating to a plurality of resource units in a resource allocation candidate, and a control circuit that controls communication using the resource units based on the first information.

[0184] In one embodiment of the present disclosure, the receiving circuit receives second information relating to the resource allocation candidate in the user common field of the signaling and receives the first information in the user individual field of the signaling.

[0185] In one embodiment of the present disclosure, the first information includes bitmap information indicating whether or not an allocation has been made in the resource allocation candidate.

[0186] In one embodiment of the present disclosure, the first information includes information relating to any one of a plurality of combinations of the resource allocation candidates.

[0187] In one embodiment of the present disclosure, the first information includes information identifying the combination and information regarding the arrangement of resource units in the frequency domain corresponding to the combination.

[0188] In one embodiment of the present disclosure, the receiving circuit receives second information indicating the resource allocation candidates and the plurality of combinations in a user common field of signaling, and the first information includes information identifying the combination.

[0189] In one embodiment of the present disclosure, the first information includes information indicating whether the combination of resource allocation candidates is used for allocation.

[0190] In one embodiment of the present disclosure, the receiving circuit receives third information indicating the configuration of the first information, and the control circuit controls the communication according to the configuration indicated by the third information.

[0191] In one embodiment of the present disclosure, the receiving circuit receives a beacon containing second information relating to the resource allocation candidate.

[0192] In one embodiment of this disclosure, the resource allocation candidates are pre-configured in the terminal or specified in a standard.

[0193] In one embodiment of the present disclosure, the first information for the terminal is set in a first user-specific field for the terminal and a second user-specific field for other terminals, respectively, which are received by the receiving circuit.

[0194] In one embodiment of the present disclosure, the first information includes information indicating a start resource unit number and an end resource unit number in the frequency domain, and the control circuit controls the communication using resource units with resource unit numbers obtained by cyclically shifting the resource unit numbers from the start resource unit number to the end resource unit number.

[0195] In one embodiment of the present disclosure, the first information includes information indicating a starting resource unit number and an ending resource unit number in the frequency domain, and the control circuit controls the communication using resource units from the starting resource unit number to the final resource unit number and resource units from the first resource unit number to the ending resource unit number if the ending resource unit number is smaller than the starting resource unit number.

[0196] In one embodiment of the present disclosure, the number of resource units that are consecutive in the frequency domain among the plurality of resource units is less than or equal to a specified value.

[0197] A base station according to one embodiment of the present disclosure comprises a transmission circuit that transmits first information relating to a plurality of resource units for one terminal in a resource allocation candidate, and a control circuit that controls communication using the resource units based on the first information.

[0198] In a communication method according to one embodiment of the present disclosure, a terminal receives first information relating to a plurality of resource units in a resource allocation candidate, and controls communication using the resource units based on the first information.

[0199] In a communication method according to one embodiment of the present disclosure, the base station transmits first information relating to a plurality of resource units for one terminal in a resource allocation candidate, and controls communication using the resource units based on the first information.

[0200] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2020-044072, filed on March 13, 2020, are incorporated herein by reference. [Industrial applicability]

[0201] One embodiment of this disclosure is useful for wireless communication systems. [Explanation of symbols]

[0202] 100 AP 101,204 Control Unit 102,206 Data transmission processing unit 103,207 allocated units 104,202 Wireless Transceiver Unit 105,201 antennas 106,203 Extraction part 107,205 Data reception processing unit 200 STA

Claims

1. A receiving circuit that receives a trigger frame including a user information field which includes resource unit (RU) allocation information and first information indicating a combination of the RUs, A control circuit that controls the transmission of an uplink signal using the aforementioned combination of RUs, It is equipped with, The RU assignment information and the first information indicate a RU combination number that represents one of the RU assignment candidates in the list of RU configuration information defined in the standard, The user information field identifies the combination of RUs by indicating the size and position of the multiple RUs that constitute the combination of RUs. Terminal.

2. A transmission circuit that transmits a trigger frame including a user information field that includes resource unit (RU) allocation information and first information indicating a combination of the RUs, A control circuit that controls the reception of an uplink signal using the aforementioned combination of RUs, It is equipped with, The RU assignment information and the first information indicate a RU combination number that represents one of the RU assignment candidates in the list of RU configuration information defined in the standard, The user information field identifies the combination of RUs by indicating the size and position of the multiple RUs that constitute the combination of RUs. Access point (AP).

Images