Communication devices and communication methods

By optimizing the RU allocation method in IEEE 802.11be and employing techniques such as bitmap format, combined numbering, and allocation type switching, the problem of low frequency resource allocation efficiency in IEEE 802.11ax was solved, resulting in reduced signaling volume and increased throughput.

CN123124104APending Publication Date: 2026-11-17PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202611133857.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-03-13
Filing Date
2021-01-19
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, the allocation efficiency of frequency resources in wireless communication is low. In particular, the allocation of non-contiguous RUs is not supported in IEEE 802.11ax, which leads to an increase in signaling volume and a decrease in throughput.

Method used

By introducing a new RU allocation method in IEEE 802.11be, which utilizes bitmap format, combination numbering, combination presence/absence information, and allocation type switching, the notification of RU allocation information is optimized, signaling volume is reduced, and frequency resource allocation efficiency is improved.

Benefits of technology

It effectively suppressed the increase in signaling volume, improved the efficiency and throughput of frequency resource allocation, and enhanced the flexibility of RU allocation and scheduling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124104A_ABST
    Figure CN123124104A_ABST
Patent Text Reader

Abstract

This invention discloses a communication device and a communication method thereof. The communication device comprises: a transmitting circuit for transmitting a trigger frame including a user information field, the user information field including resource unit (RU) allocation information and first information included in a subfield different from the RU allocation information; and a control circuit for controlling the reception of uplink signals using RU combinations composed of multiple RUs determined based on the user information field, the user information field indicating the size and location of the multiple RUs, thereby uniquely determining the RU combination composed of the multiple RUs solely through the user information field; RU structure information representing a list of RU combination candidates defined by specifications; and a combination of the RU allocation information and the first information representing an RU combination index corresponding to one of the RU combination candidates in the RU structure information.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application filed on January 19, 2021, with application number 202180020577.7 and title "Terminal and Communication Method". Technical Field

[0002] This disclosure relates to communication devices and communication methods thereof. Background Technology

[0003] Research is underway on IEEE 802.11be, a specification for next-generation wireless local area networks (LANs) that is the successor to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, IEEE 802.11ax. IEEE 802.11be is also known, for example, as Extreme High Throughput (EHT).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent literature 1: IEEE 802.11-19 / 1907r2, Multiple RU combinations for EHT

[0007] Non-patent literature 2: IEEE 802.11-19 / 1914r4, Multiple RU discussion

[0008] Non-patent literature 3: IEEE 802.11-20 / 0023r2, Multiple RU aggregation

[0009] Non-patent document 4: IEEE 802.11-19 / 1908r4, Multi-RU support

[0010] Non-patent literature 5: IEEE P802.11ax TM / D6.0 Summary of the Invention

[0011] However, the allocation methods for frequency resources in wireless communications such as wireless LANs have not been fully studied.

[0012] The non-limiting embodiments of this disclosure contribute to providing a terminal and communication method that can improve the efficiency of frequency resource allocation.

[0013] An embodiment of this disclosure includes a terminal comprising: a receiving circuit for receiving first information relating to a plurality of resource units in a resource allocation candidate; and a control circuit for controlling communication using the resource units based on the first information.

[0014] Furthermore, these general or specific methods can be implemented either by a system, apparatus, method, integrated circuit, computer program, or recording medium, or by any combination of such systems, apparatus, methods, integrated circuits, computer programs, and recording media.

[0015] According to one embodiment of this disclosure, the allocation efficiency of frequency resources can be improved.

[0016] Further advantages and effects of one embodiment of this disclosure will become apparent in the specification and drawings. The relevant advantages and / or effects are provided through several embodiments and the features described in the specification and drawings, but it is not necessarily necessary to provide all of them in order to obtain one or more of the same features. Attached Figure Description

[0017] Figure 1 This is a diagram illustrating an example of the signaling format in downlink (DL) orthogonal frequency division multiple access (OFDMA).

[0018] Figure 2 This is a diagram illustrating an example of Resource Unit (RU) allocation.

[0019] Figure 3 This is a diagram illustrating an example of the format of a trigger frame.

[0020] Figure 4 This is a diagram illustrating an example of RU allocation.

[0021] Figure 5 This is a diagram illustrating an example of RU allocation in an uplink (UL) OFDMA.

[0022] Figure 6 This is a diagram representing an allocation example of RU.

[0023] Figure 7 This is a diagram illustrating an example of RU allocation.

[0024] Figure 8This is a block diagram illustrating a structural example of a portion of the AP involved in Implementation 1.

[0025] Figure 9 This is a block diagram illustrating a structural example of a portion of the STA involved in Embodiment 1.

[0026] Figure 10 This is a block diagram illustrating a structural example of the AP involved in Implementation 1.

[0027] Figure 11 This is a block diagram illustrating a structural example of the STA involved in Implementation Method 1.

[0028] Figure 12 This is a diagram illustrating an example of the signaling format in DL OFDMA.

[0029] Figure 13 This is a diagram representing an example of RU allocation involved in Method 1.

[0030] Figure 14 This is a diagram representing an example of RU allocation involved in method 2.

[0031] Figure 15 This is a diagram representing an RU allocation example involved in method 3.

[0032] Figure 16 This is a diagram illustrating an example of the signaling format involved in Method 4.

[0033] Figure 17 This is a diagram illustrating an example of the signaling format involved in Method 5.

[0034] Figure 18 This is a diagram representing an RU allocation example involved in method 6.

[0035] Figure 19 This is a diagram illustrating an example of RU allocation involved in method 6.

[0036] Figure 20 This is a diagram representing an RU allocation example involved in method 7.

[0037] Figure 21 This is a diagram representing an RU allocation example involved in method 8.

[0038] Figure 22 This is a diagram representing an RU allocation example involved in method 8.

[0039] Figure 23 This is a diagram representing an RU allocation example involved in method 8. Detailed Implementation

[0040] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0041] In IEEE 802.11be, methods are being investigated, for example, in Orthogonal Frequency Division Multiple Access (OFDMA) transmission, for allocating multiple resource units (RUs) to one STA (or station, terminal) in continuous or discontinuous frequency domains (see, for example, non-patent documents 1-4). Frequency utilization efficiency can be improved based on this RU allocation.

[0042] In IEEE 802.11ax, for example, continuous RU allocation can be performed in the frequency domain, but non-continuous RU allocation is not supported. Furthermore, in IEEE 802.11ax, for example, the methods for notifying information related to RU allocation differ between downlink (DL) OFDMA and uplink (UL) OFDMA (see, for example, non-patent document 5).

[0043] For example, Figure 1 This is a diagram illustrating an example of the signaling format associated with DL OFDMA in IEEE 802.11ax.

[0044] like Figure 1 As shown, information related to RU allocation, such as the common field containing public information for multiple users (or STAs) within the HE-SIG-B field of the High Efficiency (HE) preamble, is notified. Furthermore, in Figure 1 In this context, information related to RU allocation is used to allocate one RU to one STA. For example, the common field within the HE-SIG-B field may contain an RU allocation subfield. This RU allocation subfield may contain, for instance, common RU allocation information for multiple STAs being allocated. For example, information related to the RU's size and location in the frequency domain (in other words, information related to the RU's configuration) can be provided through the RU allocation subfield. Furthermore, for example... Figure 1As shown, the RUs notified via the RU allocation subfield can be allocated based on the order of the user fields corresponding to each STA within the user-specific fields (which contain user-specific information specific to multiple users (or STAs)) in the HE-SIG-B field. Additionally, the RU configuration can be replaced with, for example, "RU settings".

[0045] Figure 2 This is a diagram illustrating an example of information related to the size of the RU and its location in the frequency domain that is communicated in the RU allocation subfield within the HE preamble. For example, in... Figure 1 When the RU Allocation subfield shown contains a value of 8 (binary: 00001000), eight RUs, including a 52-tone RU (e.g., an RU consisting of RU#1 and RU#2) and a 26-tone RU (an RU consisting of each of RU#3 to RU#9), can be assigned to multiple STAs. Furthermore, for example, the order of the user fields corresponding to each STA contained in the user-specific field (e.g., in...) can be used... Figure 1 (The order is STA1, STA2), as shown in the image. Figure 2 The 52-tone RU shown is assigned to STA1, and the 26-tone RU (RU#3) is assigned to STA2. Similarly, if the RU Allocation subfield contains a value of 8, the RU can be assigned to other STAs (e.g., STA8).

[0046] also, Figure 3 This is a diagram illustrating an example of the signaling format associated with UL OFDMA in IEEE 802.11ax.

[0047] like Figure 3As shown, information related to RU allocation is communicated through the STA-specific field, the RU Allocation subfield, within the Per User Info field of the Trigger frame. In UL OFDMA, for example, multiple consecutive RUs can be allocated to a single STA. Figure 4 This is a diagram illustrating an example of the information (in other words, information about the structure of the RU) that is provided in the RU Allocation subfield within the trigger frame, relating to the size of the RU and its location in the frequency domain. For instance, one RU can be assigned to a STA at a granularity of 26 tones or more (in other words, the RU size) within 80 MHz.

[0048] For example Figure 5 As shown, if STA1 is indicated with 4 (binary: 00000100) in the RU Allocation subfield, then a fifth 26-tone RU can be assigned to STA1. Furthermore, for example... Figure 5 As shown, if STA2 is indicated with 39 (binary: 00100111) in the RU Allocation subfield, then a third 52-tone RU can be assigned to STA2. Similarly, for example... Figure 5 As shown, if 40 (binary: 00101000) is indicated for STA3 in the RU Allocation subfield, then the fourth 52-tone RU can be assigned to STA3.

[0049] The above describes the notification method for information related to DL and RU allocation in IEEE 802.11ax.

[0050] Here, for example, regarding the signaling format based on IEEE 802.11ax (e.g. Figure 1 One method for allocating multiple RUs to one STA will be explained. Figure 6 An example of the format for a user-specific field in this method.

[0051] For example, the same STA identification information can be set in multiple user fields (e.g., STA ID in DL, association identifier (AID) in UL) (e.g., see Non-Patent Literature 2). Figure 6 The user-specific fields shown each contain two user fields corresponding to STA1 and STA2, respectively. Additionally, for example... Figure 7 As shown, when the RU allocation subfield in the notified HE preamble is 6 (binary: 00000110), it is possible to base it on... Figure 6 The user-specific field shown is assigned RUs in the order STA1, STA2, STA1, and STA2. This method makes it possible to assign multiple RUs to a single STA. For example, in... Figure 7 In this system, it becomes possible to assign two non-contiguous RUs to each STA.

[0052] However, in this method, because multiple user fields are set for a single STA allocated multiple RUs, there is a possibility that the signaling volume per STA will increase. For example, the increased signaling volume per STA may lead to increased overhead and decreased throughput. Figure 1 or Figure 6 The user block field shown is, for example, composed of a 21-bit user field, a 4-bit cyclic redundancy check (CRC) field, and a 6-bit tail bit field. In other words, Figure 1 or Figure 6 A single user block field, as shown, can consist of at least 31 bits. Therefore, for example... Figure 6 As shown, when more than two user fields are set for one STA, the format is similar to that of IEEE 802.11ax (e.g., Figure 1 Compared to the previous version, there is a possibility of increasing the signaling amount by at least 31 bits.

[0053] Therefore, in one embodiment of this disclosure, a method for suppressing the increase of signaling volume and allocating multiple RUs to one STA is described.

[0054] (Implementation Method 1)

[0055] [Structure of wireless communication system]

[0056] The wireless communication system according to the present embodiment includes at least one AP 100 and at least one STA 200.

[0057] Figure 8 is a block diagram illustrating a structural example of a part of the AP 100 according to an embodiment of the present disclosure. In Figure 8 the illustrated AP 100, the wireless transceiver unit 104 (e.g., corresponding to a transmission circuit) transmits first information (e.g., RU allocation information to be described later) related to a plurality of RUs for one terminal (e.g., STA 200) among resource allocation candidates (e.g., RU candidates). The control unit 101 controls communication using the RUs based on the first information.

[0058] Figure 9 is a block diagram illustrating a structural example of a part of the STA 200 according to an embodiment of the present disclosure. In Figure 9 the illustrated STA 200, the wireless transceiver unit 202 (e.g., corresponding to a reception circuit) receives first information (e.g., RU allocation information to be described later) related to a plurality of RUs among resource allocation candidates (e.g., RU candidates). The control unit 204 (e.g., corresponding to a control circuit) controls communication using the RUs based on the first information.

[0059] <Structural example of AP 100>

[0060] Figure 10 is a block diagram illustrating a structural example of the AP 100. Figure 10 The illustrated AP 100 includes, for example, a control unit 101, a data transmission processing unit 102, an allocation unit 103, a wireless transceiver unit 104, an antenna 105, an extraction unit 106, and a data reception processing unit 107.

[0061] The control unit 101 may perform scheduling for the STA 200 in at least one of DL and UL, for example. The control unit 101 may determine parameters such as the number of STAs 200 to which resources (e.g., RUs) are allocated (e.g., the number of multiplexes), the frequency bandwidth, or the frequency resources allocated to each STA 200. The control unit 101 may generate, based on the determined parameters, a control signal (e.g., a preamble) that instructs the STA 200 to receive a downlink signal, for example. In addition, the control unit 101 may generate, based on the determined parameters, a control signal (e.g., a Trigger frame) that instructs the STA 200 to transmit an uplink signal.

[0062] An example of the RU allocation method will be described later.

[0063] For example, the control unit 101 outputs the generated control signal (e.g., an EHT preamble or a Trigger frame) to the wireless transmitting and receiving unit 104. Further, the control unit 101 may, for example, output information related to resource allocation for downlink data to the allocation unit 103, and output information related to resource allocation for uplink data to the extraction unit 106.

[0064] The data transmission processing unit 102 performs transmission processing such as encoding and modulation on input transmission data (e.g., downlink data), and outputs the data signal after the transmission processing to the allocation unit 103.

[0065] The allocation unit 103 allocates (in other words, maps) the data signal input from the data transmission processing unit 102 to a resource (e.g., RU) based on, for example, the information related to resource allocation for downlink data input from the control unit 101, and outputs the mapped signal to the wireless transmitting and receiving unit 104.

[0066] The wireless transmitting and receiving unit 104 performs communication with, for example, the STA 200. For example, the wireless transmitting and receiving unit 104 performs wireless transmission processing on the data signal (e.g., downlink data) input from the allocation unit 103 or the control signal (e.g., a preamble or a Trigger frame) input from the control unit 101, and transmits a wireless signal from the antenna 105. For example, the wireless transmitting and receiving unit 104 may multiplex (e.g., time-division multiplex) the data signal and the control signal (e.g., a preamble).

[0067] Further, for example, the wireless transmitting and receiving unit 104 performs wireless reception processing on a wireless signal received by the antenna 105, and outputs a received signal after the wireless reception processing to the extraction unit 106.

[0068] The extraction unit 106 extracts, from the received signal input from the wireless transmitting and receiving unit 106, a received data signal corresponding to each STA 200 based on, for example, the information related to resource allocation for uplink data input from the control unit 101, and outputs the extracted received data signal to the data reception processing unit 107.

[0069] The data reception processing unit 107 may, for example, 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 (e.g., received data).

[0070] <Example of Configuration of STA 200>

[0071] Figure 11 is a block diagram showing an example of the configuration of the STA 200. Figure 11The STA200 shown includes, for example, an antenna 201, a wireless transmission and reception unit 202, an extraction unit 203, a control unit 204, a data reception and processing unit 205, a data transmission and processing unit 206, and a distribution unit 207.

[0072] The wireless transceiver unit 202, for example, communicates with the AP100. The wireless transceiver unit 202 performs wireless reception processing on the wireless signals received through the antenna 201 and outputs the processed received signal to the extraction unit 203. Furthermore, for example, the wireless transceiver unit 202 performs wireless transmission processing on data signals (e.g., uplink data) input from the distribution unit 207 and transmits wireless signals from the antenna 201.

[0073] Extraction unit 203 extracts (in other words, detects) control signals (e.g., preamble or trigger frame) from the received signal input by wireless transmitter / receiver unit 202 and outputs them to control unit 204. Furthermore, extraction unit 203 extracts data from the received signal and outputs it to data receiver / processor unit 205.

[0074] The control unit 204, for example, determines, based on the control signal input from the extraction unit 203, the resources (e.g., RU) allocated to downlink data for the STA 200 or the resources (e.g., RU) allocated to uplink data for the STA 200. The control unit 204 outputs information related to the allocation of downlink data resources to the data receiving and processing unit 205, and outputs information related to the allocation of uplink data resources to the allocation unit 207.

[0075] Furthermore, examples of RU allocation methods will be described later.

[0076] The data receiving and processing unit 205 extracts the signal to be sent to STA 200 from the data portion input by the extraction unit 203, for example, based on information related to downlink data resource allocation input from the control unit 204. Then, the data receiving and processing unit 205 can perform receiving processing such as demodulation and decoding on the extracted signal, and output the received signal (e.g., received data).

[0077] 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 distribution unit 207.

[0078] The allocation unit 207, for example, allocates (in other words, maps) the data signal input from the data transmission processing unit 206 to a resource (e.g., RU) based on information related to the allocation of uplink data input from the control unit 204, and outputs the mapped signal to the wireless transmission and reception unit 202.

[0079] [RU Allocation Method]

[0080] Figure 12 This represents an example of the signaling format used in the DL involved in this embodiment. Figure 12 The signaling format shown is an example based on the signaling format in IEEE 802.11be, but is not limited thereto.

[0081] exist Figure 12 The EHT-SIG field of the preamble shown (e.g., EHT preamble) may contain, for example, fields that contain information common to multiple STA200s (e.g., EHT-SIG-common field) and user-specific information that is specific to the STA (e.g., EHT-SIG-per User field).

[0082] In addition, Figure 12 The EHT-SIG-common field (in other words, the user common field) shown may contain fields (e.g., RU configuration information subfield) that contain information related to the structure of the RU (e.g., RU structure information). The RU structure information may contain information related to the size of the RU and its location in the frequency domain. In other words, the RU structure information may contain information related to RU candidates that can be assigned to the STA200 (in other words, resource allocation candidates).

[0083] In addition, Figure 12 The EHT-SIG-per User field shown may contain, for example, more than one User Block field. Within each User Block field, for example, it may contain a User field corresponding to one or two STA200s (in...). Figure 12For example, there are user fields #STA1 corresponding to STA1 and user fields #STA2 corresponding to STA2. Furthermore, each user field (in other words, user-specific fields) may contain, for example, fields containing information related to the RUs assigned to the corresponding STA200 (hereinafter referred to as RU assignment information) (e.g., RU assignment information subfield). The RU assignment information may, for example, contain information related to the RUs assigned to STA200 from among the RU candidates notified through the RU structure information.

[0084] The following section illustrates an example of an RU allocation method based on RU structure information and RU allocation information.

[0085] [Method 1]

[0086] In method 1, for example, AP100 can notify STA200 of information related to RUs assigned to it in bitmap form using RU allocation information contained in the User field. In other words, for example, the RU allocation information includes bitmap information indicating the presence or absence of an allocation to STA200 (e.g., a user) among multiple RU candidates (e.g., resource allocation candidates) notified through RU structure information.

[0087] For example, RU allocation information can be constructed using bits corresponding to multiple RU candidates shown in the RU structure information notified in the Common field (e.g., EHT-SIG-common field). Furthermore, the value of the bit corresponding to each RU candidate (e.g., 0 or 1) can be determined based on whether it has been allocated to STA200. For example, bit = 0 could indicate that the RU corresponding to that bit has not been allocated to STA200, and bit = 1 could indicate that the RU corresponding to that bit has been allocated to STA200. The relationship between the bit value and the presence or absence of RU allocation can also be reversed.

[0088] Figure 13 This is a diagram illustrating an example of the RU structure information, RU allocation information, and RU allocation results involved in Method 1.

[0089] exist Figure 13 As an example, regarding RU structure information, we can also imagine the definition of the RU Allocation subfield used in the DL of IEEE 802.11ax. Figure 13The RU structure information shown is equivalent to, for example, the RU allocation subfield used in IEEE 802.11ax DL, where RU allocation subfield = 6 (binary: 00000110). In other words, in Figure 13 In the example, the RU structure notified by the RU structure information is a pattern in which the frequencies of RU#1, 2, 4, 6, and 7 are configured with 26 tones, and the frequencies of RU#3 and 5 are configured with 52 tones in a 20MHz bandwidth.

[0090] Furthermore, the RU structure shown in the RU structure information is not limited to... Figure 13 The example shown could be either a RU structure corresponding to a value other than 6 in the DL of IEEE 802.11ax with RU Allocation subfield = 6, or a different RU structure than the RU structure in the DL of IEEE 802.11ax.

[0091] Furthermore, in the RU Allocation subfield used in IEEE 802.11ax DL, RUs are appended with numbers in units of 26 tones (e.g., in...). Figure 2 In the middle, these are RU#1~RU#9), and here, one RU number can be assigned to each of the 52 tone RUs. For example, in Figure 13 In this context, the RUs of the 52 tones are assigned RU#3 and RU#5 respectively. Therefore, in Figure 13 In the example shown, the range of RU numbers that can be allocated within a 20MHz bandwidth is RU#1 to #7. Furthermore, the range of RU numbers (in other words, the number of RU candidates) can be determined based on RU structure information (e.g., the value of the RU Allocation subfield). Figure 13 The difference is 6).

[0092] In addition, Figure 13 The RU allocation information shown may include, for example, information indicating the RU number assigned to STA200 among RUs #1 to #7 notified via the RU structure information (e.g., information in bitmap form). For example, as... Figure 13As shown, when a STA200 is assigned RU#[2,3] (e.g., bitmap: 0110000) as in Case 1 via RU allocation information, the frequency resources of RU#2 and RU#3 can be allocated to that STA200. Similarly, for example, when a STA200 is assigned RU#[5,6] (e.g., bitmap: 0000110), RU#[2,5] (e.g., bitmap: 0100100), or RU#[3,6] (e.g., bitmap: 0010010) via RU allocation information as in Cases 2-3, it indicates that each STA is allocated to the frequency configuration of the assigned RU.

[0093] Thus, according to method 1, AP100 notifies STA200 of the allocated RU number in bitmap form via the RU allocation information in the User field. This bitmap-based RU allocation, for example, improves the flexibility of RU allocation. Figure 13 As shown, based on the RU allocation information contained in a user field, one or more RUs can be assigned to a single STA200. Furthermore, based on this RU allocation information, it is possible to... Figure 13 As shown in cases 1 and 2, RU allocation with continuous frequency configuration can be set, while RU allocation with non-contiguous frequency configuration can be set as shown in cases 3 and 4.

[0094] Furthermore, according to method 1, the increase in signaling volume in RU allocation can be suppressed, thereby improving throughput. For example, in Figure 13 In the example shown, the signaling bits for the RU allocation information contained in the User field are 7 bits (e.g., bits corresponding to RU#1 through RU#7 respectively). Therefore, compared to the methods described above (e.g., Figure 6 The increase in the number of signaling bits in the RU allocation information involved in Method 1 is 24 bits less than the increase in the number of signaling bits in Method 2 (e.g., an increase of 31 bits).

[0095] [Method 2]

[0096] In method 2, for example, it is possible to define (e.g., limit) the combinations of RUs that can be assigned to one STA200 from all possible combinations of RUs. Furthermore, for example, AP100 can notify information about the combinations of RUs assigned to STA200 from the combinations of RUs via RU allocation information contained in the User field. In other words, the RU allocation information contains information related to any one of multiple combinations of multiple RU candidates (e.g., resource allocation candidates) that are notified, for example, through RU structure information.

[0097] For example, the RU allocation information may include: information identifying the combination of RUs assigned to STA200 (e.g., RU combination number) and information indicating the frequency domain configuration of the RUs corresponding to the combination of RUs assigned to STA200 (e.g., either continuous allocation or non-contiguous allocation).

[0098] Figure 14 This is a diagram illustrating an example of the RU structure information, RU allocation information, and RU allocation results involved in Method 2.

[0099] exist Figure 14 In this example, compared with method 1 ( Figure 13 Similarly, regarding RU structure information, one can envision the definition of the RU Allocation subfield used in the DL of IEEE 802.11ax. Figure 14 The RU structure information shown is equivalent to, for example, the RU allocation subfield used in IEEE 802.11ax DL, where RU allocation subfield = 6 (binary: 00000110). In other words, in Figure 14 In the example, the RU structure notified by the RU structure information is that, in a 20MHz bandwidth, the frequency configuration of RU#1,2,4,6,7 is composed of 26 tones, and the frequency configuration of RU#3,5 is composed of 52 tones.

[0100] Furthermore, the structure of the RU shown in the RU structure information is not limited to... Figure 14 The example shown could be either a RU structure corresponding to a value other than 6 in the DL of IEEE 802.11ax with RU Allocation subfield = 6, or a different RU structure than the RU structure in the DL of IEEE 802.11ax.

[0101] In addition, Figure 14 The RU allocation information shown may include information such as RU combination numbers and frequency configuration methods (continuous or discontinuous). For example, in Figure 14 In this context, for RU combinations, four types of combinations are defined, including two types of continuous allocations and two types of non-contiguous allocations (e.g., cases 1-4). For example, based on RU allocation information, it is possible to... Figure 14 As shown in cases 1 and 2, RU allocation with continuous frequency configuration can be set, while RU allocation with non-contiguous frequency configuration can be set as shown in cases 3 and 4.

[0102] Additionally, the U combination numbers #1 and #2 notified via RU allocation information, and the RU numbers in the RU structure notified via RU structure information (in...) Figure 14 The connection between RU#1~#7 is as follows: for example, it can be notified from AP100 to STA200, or it can be specified by the specification.

[0103] Thus, according to method 2, a combination of RUs is set that can be allocated to one RU of STA200 from all possible RU combinations. Then, AP100 notifies STA200 of the combination number and frequency configuration of the RUs allocated to it via, for example, RU allocation information in the user field. Based on this RU allocation, for example, it is possible to suppress the increase in signaling volume in RU allocation and improve throughput. Figure 14 In the example shown, the number of signaling bits for RU allocation information contained in the User field is 2 bits (e.g., in cases 1-4). Therefore, the increase in the number of signaling bits for RU allocation information involved in Method 2 is different from the methods described above (e.g., Figure 6 Compared to an increase of 31 bits in the number of signaling bits in ), there are 29 fewer bits.

[0104] In addition, Figure 14 The text describes, but is not limited to, cases where RU combination numbers and frequency configurations (contiguous or non-contiguous allocation) are notified to the STA200 via RU allocation information. For example, RUs notified via RU structure information (e.g., in...) Figure 14 A subset of combinations of RUs (RUs #1 to #7) can be notified through RU allocation information. For example, it can also include combinations of RUs that are equivalent to either contiguous or non-contiguous allocations.

[0105] In addition, Figure 14 For example, the case where two RUs are assigned to STA200 via RU allocation information is described, but this is not a limitation; one or more RUs may also be notified via RU allocation information. Furthermore, for example, the number of RUs associated may vary depending on the RU combination number.

[0106] Furthermore, the combination of RUs that can be assigned to the STA200 through RU allocation information is not limited to four types; it can also be two, three, or more than five types.

[0107] [Method 3]

[0108] In method 3, for example, AP100 can notify STA200, through RU allocation information contained in the User field, whether a combination of multiple RUs has been allocated to STA200 (in other words, whether a combination of RUs exists). In other words, the RU allocation information contains information indicating whether a combination of multiple RU candidates (e.g., resource allocation candidates) notified, for example, through RU structure information, is used for the allocation of STA200 (e.g., users).

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

[0110] In Method 3, as an example, we envision a combination of RUs with a large RU size (Large-size RU) of RU size of 20MHz (e.g., 242 tones) or larger.

[0111] Figure 15 This is a diagram illustrating an example of the RU structure information, RU allocation information, and RU allocation results involved in Method 3.

[0112] exist Figure 15 As an example, regarding RU structure information, we can envision the definition of the RU Allocation subfield used in the DL of IEEE 802.11ax. Figure 15 The RU structure information shown is equivalent to, for example, RU Allocation subfield = 192-199 (binary: 11000y2y1y0) [242 tones] and RU Allocation subfield = 200-207 (binary: 11001y2y1y0) [484 tones]. In other words, in Figure 15 In the example, the RU structure notified by the RU structure information is a pattern in which one of each of 242 tones (equivalent to a 20MHz band) and 484 tones (equivalent to a 40MHz bandwidth) is defined within an 80MHz bandwidth.

[0113] Furthermore, the RU structure shown in the RU structure information is not limited to the following: Figure 15The example shown could be an RU structure corresponding to values ​​other than 192-199 and 200-207 of the RU Allocation subfield in IEEE 802.11ax, or a different RU structure than the RU structure in IEEE 802.11ax DL.

[0114] Furthermore, for example, the frequency configuration of the two RUs (e.g., RU#1 and RU#2) of the 242-tone RU and the 484-tone RU, which are notified via RU structure information, can be... Figure 15 The four modes are shown.

[0115] In addition, Figure 15 The RU allocation information shown may include, for example, information indicating whether the combination of RU#1 and RU#2, which was notified via the RU structure information, has been allocated to STA200 (in other words, the presence or absence of the combination). For example, in Figure 15 Within an 80MHz bandwidth, there are one type of RU combination: 242-tone RUs and 484-tone RUs. Therefore, the STA200 can identify the RUs assigned to the STA200 (e.g., the presence or absence of RU combinations) based on RU allocation information indicating the presence or absence of RU combinations.

[0116] For example Figure 15 As shown, when the RU allocation information indicates that there are RU combinations, STA200 can determine that the RU combination notified through the RU structure information (e.g., RU#1 and RU#2) has been allocated to STA200. On the other hand, when the RU allocation information indicates that there are no RU combinations, STA200 can determine that the RUs notified through the RU structure information (e.g., RU#1 and RU#2) have been allocated to different STAs respectively.

[0117] Thus, according to method 3, when there is only one combination of RUs, AP100 notifies STA200 of the presence or absence of an RU combination assigned to it via RU allocation information in the user field. Based on this RU allocation, for example, it is possible to suppress the increase in signaling volume during RU allocation and improve throughput. For example, in... Figure 15 In the example shown, the number of signaling bits for RU allocation information contained in the Userfield is 1 bit (e.g., present or absent). Therefore, the increase in the number of signaling bits for RU allocation information involved in Method 3 is different from the methods described above (e.g., Figure 6 An increase in the number of signaling bits in (e.g., an increase of 31 bits) is 30 bits less than the increase in the number of signaling bits in (e.g., an increase of 31 bits).

[0118] In addition, Figure 15 The text describes the situation where information related to the presence or absence of RU combinations is contained in the User field. However, information related to the presence or absence of RU combinations can also be indicated through the RU structure information in the Common field. For example, information related to the presence or absence of RU combinations in the Common field, or information related to OFDMA and non-OFDMA, can be appended to the RU Allocation subfield as in the example described in Method 6 below, or it can be appended to a field different from the RU Allocation subfield.

[0119] In addition, Figure 15 In the example, the case where there is only one combination pattern of RU (in other words, the number of combinations of RU) is explained, but there can also be more than two combination patterns of RU.

[0120] Furthermore, in this embodiment, the combination of RUs in the category of large-size RUs has been described, but the combination of RUs is not limited to this. For example, the combination of RUs can be a combination of RUs in the category of small-size RUs, or a combination of RUs in both the large-size RU and small-size RU categories.

[0121] [Method 4]

[0122] In method 4, for example, control information may be notified in a common field or a user field, which is used to switch the allocation method of RUs based on the RU allocation information contained in the user field. In other words, for example, STA200 may receive information representing the structure of the RU allocation information (in other words, the allocation type) and control communication based on the structure of the RU allocation information shown in that information.

[0123] Figure 16 This is an example of the signaling format used in the DL involved in method 4.

[0124] like Figure 16As shown, for example, in the RU assignment information field of the User field (e.g., the RU assignment information subfield), the allocation type of the RU assignment method can be set to switch. For example, STA200 can switch the definition of the RU assignment value based on the allocation type.

[0125] For example, any one of methods 1 to 3 can be set as the allocation method for RU. Figure 16 In the example, methods 2 and 3 are switched by the assignment type. For example, in Figure 16 In this case, the RU allocation method based on method 2 can be set when allocation type = 0, and the RU allocation method based on method 3 can be set when allocation type = 1.

[0126] Furthermore, for example, regardless of the allocation type (in other words, the allocation method of the RU), when the size of the RU allocation information is set to a fixed value, such as... Figure 16 As shown, additional padding bits are used to align the dimensions. Furthermore, in Figure 16 The example shows the case where the allocation type is configured within the RU allocation information of the User field. However, the allocation type can also be included in a field that is different from the RU allocation information of the User field, the RU structure information in the Common field, or a field that is different from the RU structure information of the Common field.

[0127] According to method 4, for example, by switching the RU allocation method such as methods 1 to 3, the increase in signaling bits can be suppressed and the scheduling flexibility can be improved.

[0128] Furthermore, while Method 4 describes the case where the allocation type is included in a common field or a user field and notified, the allocation type can also be implicitly notified to STA200 based on other information. For example, if the bandwidth allocated to STA200 is less than 20MHz, STA200 determines that Method 2 (or Method 1) is set; if the bandwidth is greater than 20MHz, STA200 can also determine that Method 3 is set and switch the RU allocation method based on the RU allocation information.

[0129] [Method 5]

[0130] In method 5, for example, for STA200, the RU structure information may not be included in the group containing the RU allocation information.

[0131] For example, RU structure information can be notified to STA200 before RU allocation information is notified. For example, AP100 can send a beacon containing RU structure information to STA200.

[0132] Alternatively, for example, the RU structure information can be either pre-set in STA200 or defined (in other words, specified) in a specification document (or specification).

[0133] As an example, Method 5 can be applied to RU allocation for trigger frames in UL OFDMA. Figure 17 This section presents a structural example of the trigger frame in UL OFDMA as described in Method 5.

[0134] exist Figure 17 The Common Info field shown may, for example, omit RU structure information. As mentioned above, RU structure information can be communicated to STA200 via beacons or defined in the specification document.

[0135] In addition, such as Figure 17 As shown, the Per User Info field can, for example, contain RU allocation information corresponding to any of the methods 1-4 described above. Figure 17 For example, the Per User Info field can contain information related to the allocation type (e.g., an Allocation Type subfield) and the RU allocation information corresponding to that allocation type (e.g., an RU Allocation subfield). Additionally, in... Figure 17 As an example, the RU allocation information (e.g., including allocation type and RU allocation value) involved in method 4 has been described. However, the RU allocation method is not limited to method 4; it can 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, it is also possible not to include... Figure 17 The allocation type shown.

[0136] For example, each STA200 can determine the RUs assigned to it based on the maintained RU structure information and the RU allocation information notified via a trigger frame. In other words, in the UL, similar to the DL in methods 1 to 4 or methods 6 to 8 described above, for example, the allocation of multiple RUs, such as consecutive or non-consecutive allocation, becomes possible through the RU allocation information notified in a Per UserInfo field (e.g., user-specific information) corresponding to the STA200.

[0137] Therefore, according to method 5, for example, in the trigger frame of UL OFDMA, it is also possible to suppress the increase in signaling volume related to RU allocation and improve throughput.

[0138] [Method 6]

[0139] In method 6, for example, AP100 may notify RU structure information (e.g., RU candidates or resource allocation candidates) and combinations of RU candidates (e.g., a list of RU combinations) in a common field, and notify notification information (e.g., the combination number of RUs) for identifying combinations assigned to STA200 through RU allocation information contained in a user field.

[0140] Figure 18 This is a diagram illustrating an example of the RU structure information, RU allocation information, and RU allocation results involved in method 6.

[0141] exist Figure 18 As an example, regarding RU structure information, we can envision the definition of the RU Allocation subfield used in the DL of IEEE 802.11ax. Figure 18 The RU structure information shown is, for example, equivalent to the RU allocation subfield used by DL in IEEE 802.11ax = 6 (binary: 00000110).

[0142] In addition, Figure 18 The RU structure information shown may include, for example, RU combination information related to combinations of multiple RU candidates. RU combination information may be defined in an undefined area of ​​the RU Allocation subfield used in DL, for example, IEEE 802.11ax.

[0143] Figure 19This is a diagram illustrating an example of the RU structure information involved in method 6. In Figure 19 Regarding RU structure information, it's conceivable that, for example, a RU allocation subfield could be defined within the EHT-SIG-common field as RU structure information. For instance, in the RU allocation subfield used in IEEE 802.11ax's DL, the undefined region (in other words, undefined entries) contains 52 entries (e.g., RU allocation subfield = 116-127 and 216-255). Therefore, for example, RU combination information can be appended to this undefined entry. That is, several values ​​of the RU allocation subfield, similar to the IEEE 802.11ax case, represent RU structures with allocations not containing combinations of multiple RUs, while specific values ​​different from those representing RU structures with allocations not containing combinations of multiple RUs represent specific RU structures with allocations containing combinations of multiple RUs.

[0144] exist Figure 19 The example shown may include RU combination information representing the RU combinations involved in methods 1-3. For example, in Figure 19 In this context, RU combination information, representing combinations of 26-tone RUs and 52-tone RUs with bandwidths less than 20MHz, can be defined in the RU Allocation subfields = 116 and 117. Furthermore, for example, in... Figure 19 In this context, the RU combination information, representing the combination of 242-tone RUs and 484-tone RUs with a bandwidth of 20MHz or more, can be defined in the RU Allocation subfield = 216 and 217.

[0145] In addition, Figure 19 In this context, "-A" and "-B" represent pairs of identical combinations. For example, Figure 19 The "-A" shown can be used with Figure 18 The combination corresponding to RU combination number = 1 shown is... Figure 19 The "-B" shown can be used with Figure 18The combination corresponding to RU combination number 2 is shown.

[0146] Furthermore, the RU combination is not limited to Figure 19 The example shown may, for instance, include some or all of the RU combinations specified in the IEEE 802.11be standard. Furthermore, the schema of the RU Allocation subfield may also include unassigned information.

[0147] For example, in Figure 18 The RU structure information shown can include RU structures corresponding to RU Allocation subfield = 6 and RU combinations corresponding to RU Allocation subfield = 116 or 117.

[0148] also, Figure 18 The RU allocation information shown may include, for example, information indicating the RU combination number assigned to each STA200 among the RU combinations of RU#1 to RU#7 that are notified through the RU structure information.

[0149] For example, in Figure 18 In the context of consecutive frequency configurations of RU combinations, the RU allocation subfield is 116 (e.g., Figure 19 When the RU structure information is specified and the RU combination number = 1 is notified via RU allocation information, the STA200 can determine that the RU corresponding to the RU combination number 1 in the consecutive RU configurations (e.g., RU#2 and RU#3) is the allocated RU. Similarly, when the RU allocation subfield = 116 (e.g., ... Figure 19 When the RU structure information is specified and the RU combination number = 2 is notified through the RU allocation information, the STA200 can determine that the RU corresponding to the RU combination number 2 of the consecutive RU configuration (e.g., RU#5 and RU#6) is the allocated RU (not shown).

[0150] In addition, for example, in Figure 18 In the context of non-contiguous frequency configurations of RU combinations, the RU allocation subfield is 117 (e.g., Figure 19When the RU structure information is specified and the RU combination number = 2 is notified via RU allocation information, the STA200 can determine that the RU corresponding to RU combination number 2 in the non-contiguous RU configuration (e.g., RU#3 and RU#6) is the allocated RU. Similarly, when the RU allocation subfield = 117 (e.g., ... Figure 19 When the RU structure information is specified and the RU combination number = 1 is notified through the RU allocation information, the STA200 can determine that the RU corresponding to the RU combination number 1 of the non-contiguous RU configuration (e.g., RU#2 and RU#5) is the allocated RU (not shown).

[0151] Thus, according to method 6, by including RU combination information (in other words, a list of RU combinations) in the common field, it is possible to suppress the increase in signaling volume related to RU allocation in the user field, thereby improving throughput. For example, in Figure 18 In the example shown, the number of signaling bits for the RU allocation information in the User field is 1 bit. Therefore, the increase in the number of signaling bits for the RU allocation information involved in Method 6 is similar to the methods described above (e.g., Figure 6 An increase in the number of signaling bits in (e.g., an increase of 31 bits) is 30 bits less than the increase in the number of signaling bits in (e.g., an increase of 31 bits).

[0152] In addition, Figure 18 as well as Figure 19 The text describes combinations of one or two RUs, but a combination of RUs can contain more than three RUs.

[0153] [Method 7]

[0154] In method 7, for example, AP100 may notify information related to the RU allocation of multiple STA200s (in other words, multiple users) in the RU allocation information contained in the User field corresponding to each STA200.

[0155] In other words, RU allocation information for a specific STA200 can be set in both the user field (or user-specific field) received by that STA200 and the user field for other STAs.

[0156] Figure 20 This is a diagram illustrating an example of the RU structure information, RU allocation information, and allocation results involved in method 7.

[0157] exist Figure 20As an example, regarding RU structure information, the definition of the RU allocation subfield used by the DL of IEEE 802.11ax can be envisioned in the same way as in Implementation 1. Figure 20 The RU structure information shown is equivalent to, for example, the RU allocation subfield used in IEEE 802.11ax DL, where RU allocation subfield = 6 (binary: 00000110). In other words, in Figure 20 In the example, the RU structure notified by the RU structure information is that, in a 20MHz bandwidth, the frequency configuration of RU#1,2,4,6,7 is composed of 26 tones, and the frequency configuration of RU#3,5 is composed of 52 tones.

[0158] Furthermore, the structure of the RU shown in the RU structure information is not limited to... Figure 20 The example shown could be either a different RU structure than the 6th value of the RU Allocation subfield in the DL of IEEE 802.11ax, or a different RU structure than the RU structure in the DL of IEEE 802.11ax.

[0159] In addition, Figure 20 The RU allocation information shown may include, for example, information (e.g., RU number) related to the RUs (RUs) that are assigned to multiple STA200s, which are notified through the RU structure information (RUs #1 to #7).

[0160] For example, such as Figure 20 As shown, RU allocation information can be communicated in the form of (a) a bitmap and in the form of (b) an RU allocation table.

[0161] In (a) bitmap form, the RU allocation information may include, for example, information indicating the RU number (in other words, the RU allocation) of the RUs that are notified through the RU structure information and are respectively assigned to multiple STA200s.

[0162] For example, the bit strings (e.g., 7 bits) corresponding to the 7 RU#1~RU#7 notified via RU structure information can contain the corresponding quantities of multiple STA200s. Figure 20 In the example shown in bitmap form, the RU allocation information can be composed of 14 bits (7 bits × 2 users) indicating the presence or absence of allocation for each of RU#1 to RU#7 for STA1 and STA2.

[0163] For example, in Figure 20In scenario 1, the RU numbers allocated to STA1 are 2 and 3 (the bits corresponding to RU#2 and #3 are active (ON). For example, bitmap: 0110000), and the RU numbers allocated to STA2 are 5 and 6 (the bits corresponding to RU#5 and #6 are active (ON). For example, bitmap: 0000110). Accordingly, for example, each STA200 can determine that the pairing of consecutive RU numbers 2 and 3 in the frequency domain is the allocated RU for STA1, and the pairing of consecutive RU numbers 5 and 6 in the frequency domain is the allocated RU for STA2.

[0164] In addition, for example, in Figure 20 In scenario 2 shown, the RU numbers allocated to STA1 are 2 and 5 (the bits corresponding to RU#2 and #5 are active (ON). For example, bitmap: 0100100), and the RU numbers allocated to STA2 are 3 and 6 (the bits corresponding to RU#3 and #6 are active (ON). For example, bitmap: 0010010). Accordingly, for example, each STA200 can determine that the pairing of RU numbers 2 and 5, which are not consecutive in the frequency domain, is the allocated RU to STA1, and the pairing of RU numbers 3 and 6, which are not consecutive in the frequency domain, is the allocated RU to STA2.

[0165] Furthermore, in the (b) RU allocation table form, for example, it can be defined as follows: Figure 20 The diagram shows the allocation pattern (or allocation status) of each STA200 (in other words, each user) to each RU (e.g., RU#1~#7). The association between RUs and users can be represented, for example, in a table. The RU allocation information can include, for example, a number that identifies the association between the RU and the user (e.g., also called the RU allocation table number).

[0166] exist Figure 20 In the example, in the RU allocation corresponding to RU allocation table number = 1, the pairing of RU numbers 2 and 3 is allocated to user 1 (e.g., STA1), and the pairing of RU numbers 5 and 6 is allocated to user 2 (e.g., STA2). Accordingly, for example, each STA200 can determine that the pairing of consecutive RU numbers 2 and 3 in the frequency domain is the allocated RU for STA1, and the pairing of consecutive RU numbers 5 and 6 in the frequency domain is the allocated RU for STA2.

[0167] In addition, Figure 20In the example, in the RU allocation corresponding to RU allocation table number 2, the pairing of RU numbers 2 and 5 is allocated to user 1 (e.g., STA1), and the pairing of RU numbers 3 and 6 is allocated to user 2 (e.g., STA2). Accordingly, for example, each STA200 can determine that the pairing of RU numbers 2 and 5, which are not consecutive in the frequency domain, is the allocated RU for STA1, and the pairing of RU numbers 3 and 6, which are not consecutive in the frequency domain, is the allocated RU for STA2.

[0168] Thus, according to method 7, for example, STA200 can determine the RU allocation for multiple STA200 by reading the RU allocation information contained in any one of the Userfields corresponding to multiple STA200.

[0169] Furthermore, according to method 7, for example, it is possible to suppress the increase in the signaling volume allocated to the RU and improve throughput.

[0170] For example, in Figure 20 In the bitmap example shown, the signaling bits for RU allocation information (e.g., RU allocation for 2 STAs) contained in the User field are 14 bits. Therefore, the increase in the number of signaling bits for RU allocation information involved in the bitmap form of Method 7, compared to the methods described above (e.g., ... Figure 6 Compared to an increase in the number of signaling bits in ), such as an increase of 31 bits, there are 17 fewer bits.

[0171] In addition, for example, in Figure 20 In the example of the RU allocation table format shown, the signaling bits for the RU allocation information (e.g., RU allocation status for 4 modes) contained in the User field are 2 bits. Therefore, the increase in the number of signaling bits for the RU allocation information involved in the RU allocation table format of Method 7, compared to the methods described above (e.g., Figure 6 Compared to an increase of 31 bits in the number of signaling bits in ), there are 29 fewer bits.

[0172] Furthermore, for example, in the IEEE 802.11ax DL, the number of user fields contained in the user-specific field is equal to the number of RUs notified via RU allocation, and the order of the user fields corresponding to each STA indicates the location of the RUs allocated to each STA. Thus, in the IEEE 802.11ax DL, since RU allocation for a STA is determined based on the order of the user fields contained in the user-specific field, for example, each STA may be unable to determine the RU allocation related to itself or other STAs if a user field is incorrectly decoded. In other words, each STA may be unable to determine the RU based on information from a single user field (e.g., the user field corresponding to each STA).

[0173] On the other hand, according to method 7, even if a certain user field fails to be decoded, as long as other user fields are successfully decoded, each STA200 can determine the RU allocation for the multiple STA200s. In other words, according to method 7, STA200 can determine the allocated RU for STA200 without depending on the order of the user fields contained in the user-specific field.

[0174] in addition, Figure 20 The bitmap-style RU allocation information and the RU allocation table-style RU allocation information shown are examples of the association between RUs and STAs (or users), but are not limited to these. For example, in the bitmap-style or RU allocation table-style RU allocation information, STAs assigned consecutive RUs and STAs assigned non-consecutive RUs can coexist. Furthermore, in the bitmap-style or RU allocation table-style RU allocation information, the number of RUs assigned to each STA can also be different. Additionally, in the RU allocation table-style RU allocation information, a combination of all possible RU allocations for multiple STAs (in other words, the association between RUs and STAs) can be defined, or a combination of some of the combinations of all RU allocations can be defined.

[0175] [Method 8]

[0176] In method 8, for example, AP100 can use the RU allocation information contained in the User field to notify STA200 of the start position (e.g., also called the start RU) and the end position (e.g., also called the end RU) of the RU. In addition, the RU allocation information may also include the length (e.g., also called the RU length) of the RU allocated to STA200 instead of the end RU.

[0177] For example, STA200 can change the RU number notified through RU allocation information according to specified rules.

[0178] The following will illustrate methods 1 to 3 for determining RU as an example.

[0179] Furthermore, in the following examples, regarding the RU structure information, we can assume the definition of the RU allocation subfield used in IEEE 802.11ax DL. Below, as an example, we will explain the case where the RU structure information is equivalent to, for example, the RU allocation subfield used in IEEE 802.11ax DL = 0 (binary: 00000000). In other words, in the following example, the RU structure notified by the RU structure information is a pattern where RU#1~#9 are configured with 26 tones in a 20MHz bandwidth.

[0180] In addition, the RU structure shown in the RU structure information can be either a RU structure corresponding to a value other than 0 in the DL of IEEE 802.11ax with RU Allocation subfield = 0, or a different RU structure than the RU structure in the DL of IEEE 802.11ax.

[0181] <Decision Method 1>

[0182] Figure 21 This is a diagram illustrating an example of the RU structure information, RU allocation information, and RU allocation results involved in decision method 1.

[0183] exist Figure 21 The RU allocation information shown may include, for example, information related to the starting RU (e.g., RU start number) and ending RU (e.g., ending RU number) or RU length of the RU assigned to STA200.

[0184] exist Figure 21In this context, the range of the start RU and end RU (or RU length) that can be notified through RU allocation information can be set to, for example, the range of RUs that can be notified through RU structure information (e.g., 1 to 9).

[0185] For example, STA200 can use RUs whose numbers are obtained by cyclically shifting the RU numbers from the start RU number to the end RU number for communication control. Alternatively, STA200 can use RUs whose numbers are obtained by cyclically shifting the RU numbers within a range starting from the start RU number for communication control.

[0186] As Figure 21 The example configuration illustrates the case where the starting RU is 4 and the ending RU is 9 (6 for the RU length). In this case, for example, the range of RU numbers #4 to #9 (also called virtual RU numbers) can be set within the virtual RU allocation range. For example, the STA200 can 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. Figure 21 In this configuration, since the cyclic shift is set to 3, 3 RUs are allocated to each end of the 20MHz bandwidth for the STA200.

[0187] According to decision method 1, by cyclically shifting the allocation of RUs, it becomes possible to allocate discontinuous RUs in the frequency domain, which can improve the flexibility of scheduling.

[0188] <Decision Method 2>

[0189] In Method 2, the application of the "wrap around" method is explained.

[0190] Figure 22 This is a diagram illustrating an example of the RU structure information, RU allocation information, and RU allocation results involved in decision method 2.

[0191] exist Figure 22 The RU allocation information shown may include, for example, information related to the starting RU (e.g., the starting RU number) and the ending RU (e.g., the ending RU number) or RU length of the RU assigned to STA200.

[0192] exist Figure 22 In this context, the range of the start RU and end RU (or RU length) that can be notified through RU allocation information can be set, for example, as the range of RUs that can be notified through RU structure information (e.g., 1~9).

[0193] For example, if the ending RU number is less than the starting RU number, STA200 can use RUs from the starting RU number to the ending RU number, and RUs from the initial RU number to the ending RU number, for communication control. Alternatively, if the length of the RUs from the starting RU number to the ending RU number (e.g., also called the first RU length) is shorter than the length of the RUs notified via RU allocation information (e.g., also called the second RU length), STA200 can use RUs from the starting RU number to the ending RU number, and RUs from the initial RU number to the range of (second RU length - first RU length) for communication control.

[0194] As Figure 22 The example configuration illustrates the case where the starting RU is 7 and the ending RU is 3 (6 for the RU length). In this example, the position of the ending RU is smaller than the position of the starting RU. Therefore, the STA200 can, for example, extend the distance from the starting RU (RU#7) to the ending RU (RU#3). Figure 22 The range up to RU#9 and from the beginning (in other words, the initial RU) Figure 22 The range from RU#1 to the end of RU (RU#3) is set as the RU allocation range.

[0195] Furthermore, for example, if the RU is notified via RU allocation information, the STA200 can calculate the end of the RU as follows.

[0196] End RU = mod(Start RU + RU length - 1, Total RU count)

[0197] For example, in Figure 22 In the example, the ending RU = mod(7 + 6 - 1, 9) = 3. In other words, in Figure 22 In the example, STA200 is allocated 3 RUs from the beginning RU#7 to the end RU#9, and 3 RUs from the initial RU#1 to the remaining 3 RUs in the range of the notified RU length of 6, for a total of 6 RUs.

[0198] According to decision method 2, the wrap-around method makes it possible to allocate discontinuous RUs in the frequency domain, which can improve scheduling flexibility.

[0199] <Decision Method 3>

[0200] Figure 23 This is a diagram illustrating an example of the RU structure information, RU allocation information, and RU allocation results involved in decision method 3.

[0201] exist Figure 23 The RU allocation information shown may, for example, include multiple combinations of the start RU and end RU (or RU length) of the RUs assigned to STA200. Figure 23 (There are 2 groups in the middle). In other words, multiple consecutive regions (e.g., also called clusters) can be notified in the frequency domain through RU allocation information.

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

[0203] For example, in Figure 23 In this context, the range of the start RU and the end RU (or RU length) can be set to the range of RUs notified through the RU structure information (e.g., 1~9).

[0204] As Figure 23 The example settings in the example explain the cases where the start RU_1 is 2 and the end RU_1 is 3 (2 in terms of RU length), and the start RU_2 is 7 and the end RU_2 is 7 (1 in terms of RU length).

[0205] like Figure 23 As shown, it is possible to assign non-contiguous RUs #2, #3, and #7 to one STA200. Furthermore, the RU length of the region consisting of RUs #2 and #3 is 2 RUs, and the RU length of the region consisting of RUs #7 is 1 RU, both of which are less than the specified value of 2 RUs.

[0206] According to decision method 3, it becomes possible to allocate RUs to non-contiguous regions in the frequency domain, thereby improving scheduling flexibility. Furthermore, for example, in decision method 3, by setting the RU length below a predetermined value, it is possible to suppress the increase in the number of signaling bits.

[0207] The above explains methods 1 to 3 for making decisions.

[0208] Thus, according to method 8, AP100 notifies STA200 of the start RU and end RU (or RU length) of the RU assigned to it via the RU allocation information in the User field. Furthermore, STA200 (e.g., the user) determines the actual RU to be assigned based on the RU number notified via the RU allocation information, according to prescribed rules. Method 8 can suppress the increase in signaling volume for RU allocation and improve throughput.

[0209] For example, in Figure 21 (Determination Method 1) and Figure 22In (Determination Method 2), since the range of the start RU and the end RU (or RU length) is 1~9, the number of bits for each start RU and end RU (or RU length) is 4 bits, and the number of signaling bits for the RU allocation information in each user field is 8 bits. Therefore, Figure 21 as well as Figure 22 The increase in the number of signaling bits for the RU allocation information shown is related to the method described above (e.g., Figure 6 Compared to an increase in the number of signaling bits in ), such as an increase of 31 bits, there are 23 fewer bits.

[0210] In addition, for example, in Figure 23 In method 3, since the range of the start RU and the end RU (or RU length) is 1 to 9, and the length of the continuous region (RU length) is set to less than 2, the start RU has 4 bits, and the RU length has 1 bit. Therefore, Figure 23 The signaling bits for the RU allocation information in each user field shown are 5 × 2 = 10 bits. Therefore, Figure 23 The increase in the number of signaling bits for the RU allocation information shown is related to the method described above (e.g., Figure 6 Compared to an increase in the number of signaling bits in ), such as an increase of 31 bits, there are 21 fewer bits.

[0211] Methods 1 through 8 have been explained above.

[0212] As described above, according to this embodiment, for example, AP100 sends RU allocation information related to multiple RUs in the RU candidates (in other words, resource allocation candidates) for one STA200, and controls communication using RUs based on the RU allocation information. Furthermore, for example, STA200 receives RU allocation information related to multiple RUs in the RU candidates (in other words, resource allocation candidates), and controls communication using RUs based on the RU allocation information.

[0213] Accordingly, for example, AP100 can allocate multiple RUs (e.g., consecutive RUs or non-consecutive RUs) for one STA200 in the RU allocation information within one Userfield corresponding to that STA200. Thus, according to this embodiment, for example, compared with the method described above (e.g., Figure 6 Compared to other methods, this approach can suppress the increase in the number of signaling bits in the user field, thereby improving throughput. Therefore, according to this embodiment, the increase in signaling volume can be suppressed, and multiple RUs can be allocated to one STA200, improving the efficiency of frequency resource allocation.

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

[0215] (Other implementation methods)

[0216] In the above embodiments, the cases where RU structure information is included in the common field and RU allocation information is included in the user field have been described, but this is not a limitation. For example, RU structure information may also be included in the user field of the DL. In other words, RU structure information may not be included in the common field.

[0217] Furthermore, in the above implementation, the same RU allocation method (in other words, RU assignment method) can also be applied to both DL and UL.

[0218] As an example, the trigger frame for UL OFDMA can also be extended to include multiple RU combination information in the Per User Info field. Alternatively, the same format as the extended UL OFDMA trigger frame can be applied to DL OFDMA.

[0219] In addition, as another example, with Figure 12 Similarly, for UL OFDMA, the RU structure information within the channel band (e.g., RU configuration information: the size and location of each RU) can also be notified in the common information for STAs (e.g., common field). The RU allocation information (e.g., RU assignment information) consisting of multiple RU numbers included in the RU structure can also be notified in a single user-specific information (e.g., user field). Furthermore, for example, the same RU structure information as in DL can be included in the common information (common Info) of the trigger frame. This reduces the size of the user information (user Info) and decreases the overall signaling overhead.

[0220] Furthermore, the bandwidth and RU combination parameters shown in the above embodiments are examples. For bandwidths and RU combinations different from the illustrated ones, the same method as in the above embodiments can be applied. For example, the bandwidth can be set to any one of 20MHz, 40MHz, 80MHz, 160MHz, 240MHz, and 320MHz, or other bandwidths. Furthermore, for example, the RU combination can be a combination of multiple RUs of at least one size selected from 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, and 996-tone RUs. Moreover, the RU size is not limited to this and can be other sizes.

[0221] Furthermore, in the above embodiments, as an example, the format based on IEEE 802.11be was described, but the format of an embodiment of this disclosure is not limited to the IEEE 802.11be format. An embodiment of this disclosure, for example, can also be applied to the next-generation specification 802.11p for automotive applications, that is, it can also be applied to IEEE 802.11bd (NGV (Next Generation V2X)).

[0222] This disclosure can be implemented by software, hardware, or software cooperating with hardware. The functional blocks used in the above embodiments can also be implemented, partially or entirely, as integrated circuits, i.e., LSIs. The processes described in the above embodiments can also be controlled, partially or entirely, by an LSI or a combination of LSIs. An LSI can be constructed from a single chip or a single chip containing part or all of the functional blocks. An LSI can include data input and output. Due to differences in integration level, LSIs are sometimes also referred to as ICs, system LSIs, Super LSIs, or Ultra LSIs.

[0223] The method of integrating the LSI is not limited to LSI; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Furthermore, it can be implemented after LSI fabrication using programmable FPGAs (Field-Programmable Gate Arrays), reconfigurable connections of internal circuit cells within the LSI, or configured reconfigurable processors. This disclosure can also be implemented as digital or analog processing.

[0224] Furthermore, if an integrated circuit technology emerges that replaces LSI through advancements in semiconductor technology or other derived technologies, it will certainly be possible to use this technology for the integration of functional blocks. There is also the possibility of applying biotechnology, among other things.

[0225] This disclosure can be implemented in various types of devices, apparatuses, and systems with communication capabilities (collectively, communication devices). A communication device may also include a wireless transceiver and processing / control circuitry. A wireless transceiver may include a receiving unit and a transmitting unit, or include them as a function. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include amplifiers, RF modulators / demodulators, or similar components. Non-limiting examples of communication devices include telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital still image / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, electronic health and electronic medical (telemedicine prescription) devices, vehicles or mobile transportation mechanisms with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.

[0226] Communication devices are not limited to portable or mobile devices, but also include various types of devices, equipment, and systems that are not portable or fixed, such as smart home devices (home appliances, lighting machines, smart meters or measuring devices, control panels, etc.), vending machines, and other "things" that may exist on IoT (Internet of Things) networks.

[0227] In terms of communications, in addition to data communications conducted by cellular systems, wireless LAN systems, and communication satellite systems, it also includes data communications conducted by combinations of these.

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

[0229] In addition, the communication device includes the infrastructure equipment for communicating with or controlling the various devices described above (not limited to those mentioned above), such as base stations, access points, and other devices, equipment, and systems.

[0230] An embodiment of this disclosure includes a terminal comprising: a receiving circuit for receiving first information relating to a plurality of resource units in a resource allocation candidate; and a control circuit for controlling communication using the resource units based on the first information.

[0231] In one embodiment of this disclosure, the receiving circuit receives second information related to the resource allocation candidate in a user common field of the signaling, and receives the first information in a user private field of the signaling.

[0232] In one embodiment of this disclosure, the first information includes bitmap information indicating the presence or absence of allocation in the resource allocation candidates.

[0233] In one embodiment of this disclosure, the first information includes information relating to any one of the multiple combinations of the resource allocation candidates.

[0234] In one embodiment of this disclosure, the first information includes information identifying the combination and information relating to the frequency domain configuration of the resource unit corresponding to the combination.

[0235] In one embodiment of this disclosure, the receiving circuit receives second information representing the resource allocation candidates and the plurality of combinations in a user common field of signaling, the first information including information identifying the combinations.

[0236] In one embodiment of this disclosure, the first information includes information indicating whether the combination of the resource allocation candidates is used in the allocation.

[0237] In one embodiment of this disclosure, the receiving circuit receives third information representing the structure of the first information, and the control circuit performs control of the communication based on the structure shown by the third information.

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

[0239] In one embodiment of this disclosure, the resource allocation candidates are pre-set in the terminal or specified by the specification.

[0240] In one embodiment of this disclosure, the first information for the terminal is set in the first user-specific field for the terminal and the second user-specific field for other terminals received by the receiving circuit.

[0241] In one embodiment of this disclosure, the first information includes information representing the start resource unit number and the end resource unit number in the frequency domain. The control circuit uses resource units whose numbers are cyclically shifted from the start resource unit number to the end resource unit number to control the communication.

[0242] In one embodiment of this disclosure, the first information includes information representing the start resource unit number and the end resource unit number in the frequency domain. When the end resource unit number is less than the start resource unit number, the control circuit uses resource units from the start resource unit number to the end resource unit number and from the initial resource unit number to the end resource unit number to control the communication.

[0243] In one embodiment of this disclosure, the number of consecutive resource elements in the frequency domain among the plurality of resource elements is below a predetermined value.

[0244] An embodiment of the present disclosure includes a base station comprising: a transmitting circuit for transmitting first information relating to a plurality of resource units in a resource allocation candidate for a terminal; and a control circuit for controlling communication using the resource units based on the first information.

[0245] In a communication method according to an embodiment of this 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.

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

[0247] All disclosures of the specification, drawings, and abstract contained in Japanese Patent Application No. 2020-044072, filed on March 13, 2020, are incorporated herein by reference.

[0248] Industrial availability

[0249] One embodiment of this disclosure is useful for wireless communication systems.

[0250] Explanation of reference numerals in the attached figures

[0251] 100 AP

[0252] 101, 204 Control Department

[0253] 102, 206 Data Transmission and Processing Department

[0254] Distribution Department 103, 207

[0255] 104, 202 Wireless Transmitter / Receiver Unit

[0256] 105, 201 antennas

[0257] Extraction Department 106, 203

[0258] Data Receiving and Processing Department 107, 205

[0259] 200 STA.

Claims

1. A communication device comprising: The transmitting circuit transmits a trigger frame including a user information field, which includes resource unit (RU) allocation information and first information included in a subfield different from the RU allocation information; and The control circuit uses a combination of multiple RUs determined based on the user information field to control the reception of uplink signals. The user information field indicates the size and location of multiple RUs, thereby uniquely identifying the RU combination composed of the multiple RUs through the user information field alone. The RU structure information represents a list of candidate RU combinations defined by the specification. The combination of the RU allocation information and the first information represents a RU combination index corresponding to one of the RU combination candidates in the RU structure information.

2. A communication method, wherein, The communication device performs the following processing: A trigger frame is sent that includes a user information field containing resource unit (RU) allocation information and first information included in a subfield different from the RU allocation information. The reception of uplink signals is controlled by using a combination of multiple RUs determined based on the user information field. The user information field indicates the size and location of multiple RUs, thereby uniquely identifying the RU combination composed of the multiple RUs through the user information field alone. The RU structure information represents a list of candidate RU combinations defined by the specification. The combination of the RU allocation information and the first information represents a RU combination index corresponding to one of the RU combination candidates in the RU structure information.

Citation Information

Patent Citations

  • Game machine

    JP2020044072A