Communication device and communication method

Abstract

Provided is a communication device that appropriately performs wireless communication. The communication device comprises: a control circuit that determines control information for link adaptation including information on a first resource discretely disposed in a frequency band; and a transmission circuit that transmits the control information.

Description

Communication device and communication method

[0001] The present disclosure relates to a communication device and a communication method.

[0002] IEEE 802.11bn is currently under consideration as the next-generation standard for wireless LANs (Local Area Networks, also known as WLANs) that will succeed IEEE 802.11be, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. IEEE 802.11be is also known as "Extremely High Throughput (EHT)," and IEEE 802.11bn is also known as "Ultra High Reliability (UHR)."

[0003] IEEE 802.11-23 / 2020r1 High Level Perspective on Distributed Tone RU for 11bnIEEE 802.11-24 / 0400r0 Hybrid PPDU and Distribution Bandwidth for DRU

[0004] There has been insufficient consideration given to methods for controlling wireless communications such as wireless LAN.

[0005] Non-limiting examples of the present disclosure contribute to providing a communication device and a communication method that can appropriately control wireless communication.

[0006] A communication device according to one embodiment of the present disclosure includes a control circuit that determines control information for link adaptation including information about first resources that are discretely arranged in a frequency band, and a transmission circuit that transmits the control information.

[0007] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0008] According to an embodiment of the present disclosure, wireless communication can be appropriately controlled.

[0009] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features.

[0010] Diagram showing an example of the format of the Control Information subfield in the Extremely High Throughput (EHT) link adaptation (ELA) control fieldDiagram showing an example of transmission of a regular resource unit (rRU) and a distributed RU (dRU)Diagram showing an example of a Solicited Link Adaptation procedureDiagram showing an example of an Unsolicited Link Adaptation procedure (for non-Trigger-based Physical layer Protocol Data Unit (non-TB-PPDU))Diagram showing an example of an Unsolicited Link Adaptation procedure (for TB PPDU)Block diagram showing an example of a node configurationDiagram showing an example of the format of the High Throughput (HT) Control fieldDiagram showing an example of a Control ID definitionDiagram showing an example of a Control ID definitionDiagram showing an example of a UHR Control field formatDiagram showing an example of a Frame Control field formatDiagram showing an example of the format of the Control Information subfield in the UHR Link Adaptation (ULA) Control fieldDiagram showing an example of a definition of the rRU / dRU Allocation subfieldDiagram showing an example of a DRU index definitionDiagram showing an example of a DRU index definitionDiagram showing an example of a DRU index definitionDiagram showing an example of a format of the User Info field in a Basic Trigger framerRU / dRU in a Basic Trigger frame Diagram showing an example of the procedure for indicating Allocation Diagram showing an example of the format of the Control Information subfield in the ULA Control field Diagram showing an example of the definition of the rRU / dRU Allocation subfield Diagram showing an example of the definition of the rRU / dRU Allocation subfield Diagram showing an example of the format of the User Info field in the Basic Trigger frame rRU / dRU in the Basic Trigger frameDiagram showing an example of the allocation instruction procedure Diagram showing an example of the format of the Control Information subfield in the ULA Control field Diagram showing an example of the definition of the RU Allocation / Distribution BW subfield Diagram showing an example of the format of the Control Information subfield in the ULA Control field Diagram showing an example of the format of the Control Information subfield in the ULA Control field Diagram showing an example of the format of the Control Information subfield in the ULA Control field

[0011] Hereinafter, each embodiment of the present disclosure will be described in detail with reference to the drawings.

[0012] The 6 GHz frequency band has stricter power spectral density (PSD) limitations than other frequency bands. For example, a terminal in Low Power Indoor (LPI) mode (e.g., a station (STA) or non-AP STA) may be limited to a PSD of −1 dBm / MHz. The IEEE 802.11bn standard is considering introducing “Distributed-Tone Resource Units” (dRUs or DRUs) to overcome this PSD limitation and improve spectral efficiency by maximizing transmission power (see, for example, Non-Patent Documents 1 and 2). Note that a dRU refers to an RU configured with tones (frequency resources) that are discretely (or dispersedly or diffusely) allocated in a frequency band.

[0013] Link adaptation methods for dRU transmission have not been fully studied. Existing standards specify a link adaptation procedure for optimizing communication speeds by exchanging parameters such as a recommended modulation and coding scheme (MCS) or a recommended RU (e.g., tone location) between terminals. However, this link adaptation procedure is specified for RUs (hereinafter referred to as "Regular RUs" or "RRUs") defined in the existing 11ax / 11be standards. Note that an rRU refers to an RU configured with tones (frequency resources) contiguously allocated in a frequency band. Figure 1 shows an example format of the Control Information subfield in the EHT link adaptation (ELA) Control subfield. The rRU is defined in the RU Allocation shown in Figure 1.

[0014] In a non-limiting example of the present disclosure, a method for appropriately controlling link adaptation for dRU transmission will be described.

[0015] [Configuration of Wireless Communication System] A wireless communication system according to an embodiment of the present disclosure may include, for example, an access point (AP) 100 and a STA 200 (non-AP STA). For example, the AP 100 transmits a downlink (DL) signal to the STA 200. Furthermore, the STA 200 transmits an uplink (UL) signal to the AP 100.

[0016] In one embodiment of the present disclosure, information about the dRU is included in the exchange information (control information) for link adaptation. The information about the dRU may include, for example, at least one of the information shown in Table 1. The information shown in Table 1 includes information about the rRU or the dRU. For example, the information about the dRU shown in Table 1 may include "rRU / dRU" information indicating whether a dRU or an rRU is applied, dRU or rRU allocation information ("rRU / dRU Allocation"), information indicating a modulation and coding scheme (MCS) recommended for transmission using the rRU or dRU ("rRU-MCS / dRU-MCS"), information indicating the number of spatial streams recommended for transmission using the rRU or dRU ("rRU-NSS / dRU-NSS"), or information indicating a bandwidth recommended for transmission using the rRU or dRU ("rRU-BW / dRU-BW"). Furthermore, the information about the dRU shown in Table 1 may include information indicating a power boost value for transmission using the dRU ("dRU Power Boost").

[0017] Figure 2 shows an example of rRU and dRU transmission. In the rRU transmission shown in Figure 2, transmission is performed in a 40 MHz bandwidth. Also, in the dRU transmission shown in Figure 2, transmission is performed in an 80 MHz bandwidth. In the dRU transmission shown in Figure 2, when a 26-tone RU (e.g., represented as "RU26") is used, transmission is performed using RUs spaced at 13-tone intervals, enabling a maximum power boost of 11.14 dB compared to the rRU.

[0018] Next, an example of the Link Adaptation procedure will be described.

[0019] Figure 3 shows an example of a Solicited Link Adaptation procedure, Figure 4 shows an example of an Unsolicited Link Adaptation procedure (for non-TB PPDU), and Figure 5 shows an example of an Unsolicited Link Adaptation procedure (for TB PPDU). Note that TB PPDU is an abbreviation for Trigger-based Physical layer Protocol Data Unit.

[0020] In the example of the Solicited Link Adaptation procedure shown in FIG. 3 , Node 1 transmits an MCS request (MRQ) of UHR link adaptation (ULA) to Node 2. The ULA (MRQ) may include, for example, information about the RU or multiple resource unit (MRU) for which a recommended MCS value is requested, and about the dRU. Upon receiving the ULA (MRQ) from Node 1, Node 2 transmits MCS feedback (MFB) of the ULA to Node 1. The ULA (MFB) may include, for example, information about the dRU as shown in Table 1. Upon receiving the ULA (MFB) from Node 2, Node 1 determines transmission parameters, such as whether rRU or dRU is to be applied (rRU / dRU), MCS, number of spatial streams (NSS), and bandwidth (BW), based on the recommended value included in the ULA (MFB), and transmits data.

[0021] In the example of the Unsolicited Link Adaptation procedure (for non-TB PPDU) shown in Figure 4, Node 1 transmits a ULA (MFB) to Node 2 without being requested by Node 2. The ULA (MFB) may include, for example, information about the dRU as shown in Table 1. Upon receiving the ULA (MFB) from Node 1, Node 2 determines transmission parameters such as rRU / dRU, MCS, NSS, and BW based on the recommended values ​​included in the ULA (MFB) and transmits data. In the example of Figure 4, Node 2 transmits a non-TB PPDU (non-trigger based PPDU), which is a standalone transmission without a trigger.

[0022] In the example of the Unsolicited Link Adaptation procedure (for TB PPDU) shown in FIG. 5 , Node 2 transmits a ULA (MFB) to Node 1 without being requested by Node 1. The ULA (MFB) may include, for example, information about the dRU as shown in Table 1. Upon receiving the ULA (MFB) from Node 2, Node 1 determines transmission parameters such as rRU / dRU, MCS, NSS, and BW based on the recommended values ​​included in the ULA (MFB) and instructs Node 2 to transmit data. In the example of FIG. 5 , the Trigger frame transmitted by Node 1 specifies transmission parameters for the TB PPDU (trigger-based PPDU) transmitted by Node 2. Node 2 transmits data based on the transmission parameters specified by the Trigger frame.

[0023] FIG. 6 shows an example configuration of a node (e.g., corresponding to a communication device). The node may be, for example, AP 100 or STA 200. In FIG. 6, a control unit (e.g., corresponding to a control circuit) determines (or generates) control information for link adaptation, including information about frequency resources (dRUs) discretely allocated in a frequency band. The control unit also controls link adaptation, for example, based on control information received from other nodes. A communication unit (e.g., corresponding to a transmission circuit or reception) transmits and receives control information to and from other nodes.

[0024] According to an embodiment of the present disclosure, link adaptation suitable for each of the dRU and the rRU can be performed, thereby improving throughput.

[0025] The following describes embodiments relating to examples of methods for controlling link adaptation operations of a dRU and an rRU.

[0026] (Embodiment 1) In this embodiment, a Control ID for ULA (for example, a new Control ID) is set in the A-Control subfield (hereinafter also referred to as A-Control) of the HT Control field (hereinafter also referred to as HT Control) in exchange information for Link Adaptation. For example, if the value of the Control ID subfield included in the HT Control corresponds to ULA, information about dRU is included in the Control Information subfield in the HT Control.

[0027] FIG. 7 shows an example of the configuration of A-Control within HT Control.

[0028] As shown in Fig. 7, HT Control is included in the MAC header, and A-Control exists when the Variant in HT Control is HE (for example, when B0 and B1 are [1, 1]). As shown in Fig. 7, A-Control includes a Control List subfield (hereinafter also referred to as Control List) and Padding bits, and the Control List is made up of one or more Control subfields. The Control subfield is made up of a Control ID subfield (hereinafter also referred to as Control ID) and a Control Information subfield (hereinafter also referred to as Control Information).

[0029] FIG. 8 shows an example of a definition of a Control ID.

[0030] In the example of Fig. 8, when the Control ID value is 10 (an undefined value (reserved) in the existing standards), it is defined that the content of Control Information is ULA Control. For example, in Fig. 8, in addition to Control ID value = 2 which defines that the content of Control Information is High Efficiency (HE) Link Adaptation (HLA) or EHT Link Adaptation (ELA), Control ID value = 10 which defines that the content of Control Information is ULA Control is newly set. Note that, although ULA Control is defined as Control ID value = 10 in the example of Fig. 8, ULA Control may also be defined as another undefined value.

[0031] When ULA Control is specified (in FIG. 8, when Control ID value=10), the Control Information shown in FIG. 7 may include, for example, information about the dRU (or rRU) (e.g., information about the ULA) as shown in Table 1.

[0032] In this manner, in the present embodiment, a Control ID for ULA is set in the A-Control of the HT Control, thereby enabling notification of information related to the dRU or rRU in exchange information for link adaptation (for example, the Control Information subfield). Therefore, according to the present embodiment, link adaptation suitable for each of the dRU and rRU can be performed, thereby improving throughput.

[0033] (Embodiment 2) In this embodiment, a Control ID common to HT Link Adaptation (HLA), EHT Link Adaptation (ELA), and ULA (hereinafter also referred to as "HLA / ELA / ULA common") is set in the A-Control of the HT Control in the exchange information for Link Adaptation. For example, if the value of the Control ID subfield included in the HT Control is a value that corresponds commonly to HLA / ELA / ULA, information about the dRU is included in the Control Information subfield in the HT Control.

[0034] Alternatively, for example, the ULA may be indicated by a value in a Control Information subfield in which a Control ID common to the HLA / ELA / ULA is set (for example, the value of the RU Allocation subfield). In other words, the HLA, ELA, and ULA may be distinguished from each other by the value in a Control Information subfield in which a Control ID common to the HLA / ELA / ULA is set.

[0035] In this embodiment, the configuration of the A-Control in the HT Control may be the same as that of the first embodiment (for example, FIG. 7).

[0036] FIG. 9 shows an example of a definition of a Control ID.

[0037] In the example of Fig. 9, a control shared by HLA / ELA / ULA (also referred to as HLA / ELA / ULA control) is defined when Control ID value = 2. When HLA / ELA / ULA control is specified (Control ID value = 2 in Fig. 9) and a ULA is indicated by the value of Control Information, the Control Information shown in Fig. 7 may include, for example, information on the dRU (or rRU) (e.g., information on the ULA) as shown in Table 1.

[0038] For example, as the value of Control Information, the RU Allocation subfield in the Control Information subfield may be defined as an “rRU / dRU Allocation” subfield indicating the allocation of an rRU or dRU, and the value of rRU / dRU Allocation may indicate that it is a ULA.

[0039] As described above, in this embodiment, a Control ID common to HLA / ELA / ULA is set in the A-Control of the HT Control, and by indicating the ULA using the value of the Control Information subfield, it becomes possible to notify information related to the dRU or rRU in exchange information for link adaptation (for example, the Control Information subfield). Thus, according to this embodiment, link adaptation suitable for each of the dRU and rRU can be performed, thereby improving throughput.

[0040] Furthermore, in this embodiment, information regarding the ULA is associated with a Control ID that is common to information regarding the HLA and ELA, i.e., an existing Control ID, so that the undefined value (Reserved) in the Control ID subfield can be reserved for future expansion in the standard.

[0041] (Embodiment 3) In this embodiment, a "UHR Control field" (new Control field) corresponding to UHR is set in the MAC header. For example, in addition to an existing Control field (e.g., HT Control field), a UHR Control field may be newly set (or defined) in the MAC header.

[0042] FIG. 10 shows an example of the configuration of the UHR Control field.

[0043] As shown in Fig. 10, the MAC header contains a UHR Control field (hereinafter also referred to as UHR Control). When the Variant in the UHR Control shown in Fig. 10 is UHR (for example, B0 and B1 = [0, 0]), the UHR Control contains an A-Control subfield. As shown in Fig. 10, the A-Control contains a Control List and Padding bits, and the Control List is made up of one or more Control subfields. The Control subfield is made up of a Control ID and Control Information.

[0044] The control information may include, for example, information about the dRU (or rRU) as shown in Table 1 (for example, information about UHR Link Adaptation).

[0045] In the example of Fig. 10, the size of the UHR Control is 8 octets, the UHR Control variant designation bits are 2 bits (e.g., B0 and B1), and the Control ID size is 4 bits. In this case, the size of the Control Information is a maximum of 58 bits. For example, since the size of the Control Information in the case of the HT Control shown in Fig. 7 is a maximum of 26 bits, more information can be set in the UHR Control shown in Fig. 10 than in the HT Control. Note that, although the size of the UHR Control field is 8 octets in the example of Fig. 10, the size of the UHR Control field is not limited to this and may be other sizes.

[0046] Figure 11 shows an example of the format of the Frame Control field shown in Figure 10. The "+UHRC" subfield shown in Figure 11 is a field indicating the presence or absence of UHR Control in the MAC header. For example, a Frame Control field format including a +UHRC subfield may be defined (e.g., newly defined) in an undefined value (Reserved) in the Subtype subfield or Control Frame Extension subfield of the Frame Control field in existing standards. The example in Figure 11 shows an example of a format including a +UHRC subfield when the Control Frame Extension subfield is 12.

[0047] As described above, according to the present embodiment, by setting a UHR Control field (a new Control field) in the MAC header, it becomes possible to notify information related to the dRU or rRU in exchange information for Link Adaptation (for example, the Control Information subfield). Therefore, according to the present embodiment, Link Adaptation suitable for each of the dRU and the rRU can be performed, and throughput can be improved.

[0048] As described above, exemplary configurations (frame configuration examples) of exchange information for Link Adaptation have been described in Embodiments 1 to 3. In the following Embodiments 5 to 8, examples of control information included in exchange information for Link Adaptation (for example, the Control Information subfield) will be described.

[0049] (Embodiment 4) In this embodiment, a case will be described in which the control information in the Control Information subfield includes information indicating which of rRU and dRU is applied (for example, a subfield specifying rRU / dRU).

[0050] FIG. 12 shows an example of the format of the Control Information subfield in the Control subfield (hereinafter also referred to as the ULA Control subfield) when a ULA is specified.

[0051] In the Control Information subfield shown in Fig. 12, an "rRU / dRU" subfield that specifies either an rRU or a dRU is defined in B25. In addition, the "rRU / dRU Allocation" subfield shown in Fig. 12 switches between an 11be RU Allocation (for an rRU) and an Allocation for a dRU (for a dRU) in accordance with the specified rRU / dRU (rRU or dRU). In other words, when a dRU is specified, the existing RU and MRU are read as DRUs in the rRU / dRU Allocation subfield.

[0052] Figure 13 shows an example of the definition of the rRU / dRU Allocation subfield. As shown in Figure 13, a DRU is defined in the same way as the existing RU and MRU (e.g., corresponding to an rRU). In Figure 13, switching between the RU and MRU and the DRU is performed according to the value of the rRU / dRU subfield in the Control Information subfield.

[0053] Figure 14 shows an example of the definition of the DRU index of a 20 MHz UHR PPDU. As shown in Figure 14, for an existing RU (e.g., rRU), the subcarrier index is defined with an interval (i: subcarrier separation interval) corresponding to each tone size of the dRU. In the example of Figure 14, the subcarrier (or tone) on which the dRU is allocated is set by the start subcarrier index, the end subcarrier index, and the subcarrier interval i. For example, for a 26-tone DRU, the subcarrier index interval (i) is 9, for a 52-tone DRU, the subcarrier index interval (i) is 4, and for a 106-tone DRU, the subcarrier index interval (i) is 2.

[0054] Similarly, Figure 15 shows an example of a definition of the DRU index for a 40 MHz UHR PPDU, and Figure 16 shows an example of a definition of the DRU index for an 80 MHz UHR PPDU. The DRU index for a 160 / 320 MHz UHR PPDU can also be defined in a similar manner. Note that in the definitions of the DRU index shown in Figures 14, 15, and 16, the dRU index may be defined by subcarriers excluding subcarriers that are not used for signal allocation, such as Guard or Null.

[0055] In this way, in this embodiment, by including a subfield that specifies an rRU / dRU as control information in the Control Information subfield, it becomes possible to notify information about the dRU or rRU according to the type of RU specified (rRU or dRU). Therefore, according to this embodiment, link adaptation suitable for each of the dRU and rRU can be performed, and throughput can be improved.

[0056] The method of specifying rRU / dRU described in this embodiment may also be applied to the method of indicating dRU / rRU in RU allocation in a Basic Trigger Frame.

[0057] Fig. 17 shows an example of the format of the UHR variant User Info field of the Basic Trigger frame. For the rRU / dRU Allocation subfield shown in Fig. 17, DRU may be defined in the same way as the existing RU and MRU as shown in Fig. 13. Furthermore, switching between RU and MRU and DRU may be performed by the "rRU / dRU" subfield shown in Fig. 17. The rRU / dRU subfield may be defined by undefined (reserved) bits in the existing EHT variant User Info field format.

[0058] Fig. 18 shows an example procedure for indicating rRU / dRU Allocation in a Basic Trigger frame. As shown in Fig. 18, the AP transmits a Basic Trigger frame including an rRU / dRU subfield and an rRU / dRU Allocation subfield to each of non-AP STA 1 and non-AP STA 2. Non-AP STA 1 and non-AP STA 2 receive the Basic Trigger frame from the AP and transmit data (e.g., TB PPDU) using the rRU or dRU allocated by the Basic Trigger frame.

[0059] This makes it possible to notify allocation information regarding a dRU or an rRU according to the type of RU (rRU or dRU) specified by the Basic Trigger frame.

[0060] In addition, although FIG. 17 describes the case where the rRU / dRU subfield is set in the User Info field (e.g., terminal-specific information), the rRU / dRU subfield may also be set in the Common Info field (e.g., terminal-common information).

[0061] (Embodiment 5) In this embodiment, a method of distinguishing between application of rRU and application of dRU (for example, distinguishing between RU types) based on the value of the RU Allocation subfield in the Control Information subfield will be described.

[0062] FIG. 19 shows an example format of the Control Information subfield in the ULA Control subfield.

[0063] In the Control Information subfield shown in FIG. 19, rRU / dRU (for example, rRU or dRU) are distinguished by the value of the rRU / dRU Allocation subfield defined in B9-B16.

[0064] 20 and 21 show examples of definitions of the rRU / dRU Allocation subfield.

[0065] FIG. 20 shows an example in which the DRU size and DRU index are defined in 107-127, which are undefined values ​​in the existing standard, of the "B7-B1 of the RU Allocation" subfield.

[0066] Figure 21 shows an example in which the DRU size and DRU index are defined in an undefined value in the RU Allocation subfield B7-B1 that is undefined in existing standards and different from the undefined value in Figure 20. In Figure 21, for example, if the value of the RU Allocation subfield B7-B1 is 70, the Bandwidth (MHz) is 80, 160, or 320, and the Bandwidth (MHz) of the dRU is limited to 20, 40, or 80, then the Bandwidth used for dRU transmission (defined as, for example, 80, 160, or 320) may be read as 20, 40, or 80. Also, for example, in Figure 21, if the value of the RU Allocation subfield B7-B1 is 87-88, the Bandwidth (MHz) value (20, 40, 80, 160, or 320) may be used as is as the Bandwidth used for dRU transmission.

[0067] In this way, in this embodiment, by distinguishing between rRUs and dRUs using the RU Allocation subfield value in the Control Information subfield, it becomes possible to notify information related to dRUs or rRUs. Therefore, according to this embodiment, link adaptation suitable for each of dRUs and rRUs can be performed, thereby improving throughput.

[0068] Furthermore, in this embodiment, by distinguishing between rRUs and dRUs using the RU Allocation subfield value, information specifying the RU type (rRU / dRU) does not need to be notified.

[0069] The method of distinguishing between rRUs and dRUs using the RU Allocation subfield value described in this embodiment may also be applied to the method of indicating dRUs and rRUs in RU allocation in a Basic Trigger Frame.

[0070] Figure 22 shows an example format of the UHR variant User Info field of the Basic Trigger frame. Regarding the rRU / dRU Allocation subfield shown in Figure 22, as shown in Figure 20 or 21, DRU may be defined as a value undefined in existing standards among B7-B1 of the RU Allocation subfield. By defining it in this way, it becomes possible to distinguish between rRU and dRU.

[0071] Fig. 23 shows an example procedure for indicating rRU / dRU Allocation in a Basic Trigger frame. As shown in Fig. 23, the AP transmits a Basic Trigger frame including an rRU / dRU Allocation subfield to each of non-AP STA 1 and non-AP STA 2. Non-AP STA 1 and non-AP STA 2 receive the Basic Trigger frame from the AP and transmit data (e.g., TB PPDU) using the rRU or dRU allocated by the Basic Trigger frame.

[0072] This makes it possible to distinguish between rRUs and dRUs by the RU Allocation subfield value indicated by the Basic Trigger frame, and makes it possible to notify allocation information regarding dRUs or rRUs.

[0073] (Embodiment 6) In this embodiment, when a dRU is applied or a wideband rRU is applied, a method is described in which a recommended Distribution bandwidth (Distribution BW) or bandwidth (BW) is notified by the Control Information subfield, and information about other RUs (e.g., tone location information) is not notified.

[0074] For example, when a dRU is applied or when a wideband rRU is applied (e.g., when the bandwidth allocated to the rRU is equal to or greater than a predetermined value), the Control Information subfield may include information about the recommended bandwidth (e.g., Distribution bandwidth or BW) and may not include information about the recommended tone position.

[0075] Here, Distribution bandwidth refers to the bandwidth used in the dRU (for example, the bandwidth at both ends of the dRU). In this embodiment, the recommended Distribution bandwidth or bandwidth (BW) is set (for example, limited) as the information to be notified because, when a dRU is applied or a wideband rRU is applied, the frequency diversity effect tends to make the characteristics less dependent on the RU position (tone position). In this embodiment, this tendency is utilized to notify the recommended Distribution bandwidth or bandwidth (BW), while omitting notification of other information (for example, tone position information).

[0076] FIG. 24 shows an example format of the Control Information subfield in the ULA Control subfield.

[0077] In the Control Information subfield shown in Fig. 24, the dRU size or recommended Distribution bandwidth is notified by the value of the "RU Allocation / Distribution BW" subfield defined in B9-B16. Fig. 25 shows an example definition of the RU Allocation / Distribution BW subfield shown in Fig. 24. As shown in the example of Fig. 25, the DRU size and Distribution BW may be defined for an undefined value in the RU Allocation subfield of 11be. In the example of Fig. 25, the dRU index does not need to be defined.

[0078] Figure 26 shows another example format of the Control Information subfield in the ULA Control subfield. In the Control Information subfield shown in Figure 26, the Distribution bandwidth is notified by the value of the "Distribution BW" subfield defined in B18-B20. The Distribution BW subfield shown in Figure 26 is a field that replaces the BW subfield defined in the existing 11be standard. Note that in Figure 26, the RU Allocation subfield does not need to be used.

[0079] In this way, in this embodiment, when a dRU is applied or a wideband rRU is applied, by notifying the recommended Distribution BW or bandwidth (BW), link adaptation appropriate for each of the dRU and rRU can be performed according to the notified recommended Distribution BW or recommended BW, thereby improving throughput.

[0080] (Embodiment 7) In this embodiment, a case will be described in which both information on rRU and information on dRU are included in the Control Information subfield. That is, in the Control Information subfield, subfields indicating recommended values ​​for both rRU and dRU are defined.

[0081] FIG. 27 shows an example format of the Control Information subfield in the ULA Control subfield.

[0082] In the Control Information subfield shown in FIG. 27, the rRU-NSS, rRU-MCS, RU Allocation, PS160, and rRU-BW defined in B2-B4, B5-B8, B9-B16, B17, and B18-B20, respectively, indicate recommended values ​​when applying the rRU corresponding to the NSS, MCS, RU Allocation, PS160, and BW defined in the existing ELA Control subfield.

[0083] In the Control Information subfield shown in Fig. 27, the dRU-NSS, dRU-MCS, dRU Allocation, dRU PS160, and dRU-BW defined in B25-B27, B28-B31, B32-B39, B40, and B41-B43, respectively, indicate recommended values ​​when a dRU corresponding to the NSS, MCS, RU Allocation, PS160, and BW defined in the existing ELA Control subfield is applied. In addition, the dRU-Power Boost defined in B44-TBD in Fig. 27 is information indicating the Power Boost value when a dRU is transmitted.

[0084] In this way, in this embodiment, a subfield that indicates the recommended values ​​for both rRU and dRU is defined in the Control Information subfield. This makes it possible to perform link adaptation appropriate for each of the dRU and rRU, thereby improving throughput.

[0085] (Embodiment 8) In this embodiment, a method will be described in which information about a dRU is included in the Control Information subfield, but information about an rRU is not included. In this embodiment, for example, when an rRU is applied, ELA Control defined in 11be may be used.

[0086] Figure 28 shows an example format of the Control Information subfield in the ULA Control subfield. In the Control Information subfield shown in Figure 28, the dRU-NSS, dRU-MCS, dRU Allocation, dRU PS160, and dRU-BW defined in B2-B4, B5-B8, B9-B16, B17, and B18-B20, respectively, indicate recommended values ​​when applying a dRU corresponding to the NSS, MCS, RU Allocation, PS160, and BW defined in the existing ELA Control subfield. In addition, the dRU-Power Boost defined in B25-TBD in Figure 28 is information indicating the Power Boost value when transmitting a dRU.

[0087] In this way, in the present embodiment, information about the dRU is included in the Control Information subfield, but information about the rRU is not included. This makes it possible to perform link adaptation appropriate for each of the dRU and rRU by combining ULA Control and ELA Control, for example, and improve throughput.

[0088] The embodiments of the present disclosure have been described above.

[0089] The above-described embodiments may be used in combination as appropriate, or may be used by switching between them.

[0090] Although the embodiments have been described above with reference to the drawings, the present disclosure is not limited to such examples. It is clear that a person skilled in the art can conceive of various modifications or alterations within the scope of the claims. It is understood that such modifications or alterations also fall within the technical scope of the present disclosure. Furthermore, the components in the embodiments may be combined in any manner without departing from the spirit of the present disclosure.

[0091] In the above-described embodiments, the notation "... part" used for each component may be replaced with other notations such as "... circuit," "... assembly," "... device," "... unit," or "... module."

[0092] The interface names (frame names), field names, or subfield names described in the above-described embodiments may be other names.

[0093] In each of the above-described embodiments, the field (or subfield) used for notifying control information is an example, and other fields or subfields may be used. Furthermore, the number of bits or the number of octets used for notifying control information in each field or subfield is an example, and other numbers of bits or octets may be used.

[0094] Furthermore, the signal formats described in each of the above-mentioned embodiments are merely examples, and other configurations may be used in which at least one of other fields is added and some fields is deleted, and other configurations may be used in which at least one of other subfields is added and some subfields are deleted in each of the above-mentioned fields.

[0095] Furthermore, the parameters described in each of the above-mentioned embodiments, such as Bandwidth (or Distribution BW), RU size (e.g., dRU size), RU index (e.g., dRU index), subcarrier index, and subcarrier spacing i, are merely examples, and other values ​​may be used.

[0096] Furthermore, in the above embodiment, as an example, a case based on the format defined in IEEE 802.11 has been described, but the format to which an embodiment of the present disclosure is applied is not limited to the IEEE 802.11 format.

[0097] The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may also be called an IC, system LSI, super LSI, or ultra LSI.

[0098] The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0099] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0100] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

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

[0102] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

[0103] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0104] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0105] Furthermore, in recent years, in the field of IoT (Internet of Things) technology, CPS (Cyber ​​Physical Systems) has been attracting attention as a new concept that creates new added value by linking information between physical space and cyberspace. This CPS concept can also be adopted in the above-described embodiment.

[0106] That is, as a basic configuration of a CPS, for example, an edge server located in physical space and a cloud server located in cyberspace can be connected via a network, and processing can be distributed and performed by processors installed on both servers. Here, it is preferable that each piece of processing data generated in the edge server or cloud server is generated on a standardized platform, and the use of such a standardized platform can improve the efficiency of building a system that includes a variety of sensor groups and IoT application software.

[0107] A communication device according to one embodiment of the present disclosure includes a control circuit that determines control information for link adaptation including information about first resources that are discretely arranged in a frequency band, and a transmission circuit that transmits the control information.

[0108] In one embodiment of the present disclosure, the information about the first resource includes information indicating whether the first resource or a second resource arranged contiguously in a frequency band is applied.

[0109] In one embodiment of the present disclosure, the information about the first resource includes allocation information of the first resource.

[0110] In one embodiment of the present disclosure, the information regarding the first resource includes at least one of information regarding a recommended coding and modulation scheme, a recommended number of spatial streams, and a recommended bandwidth for transmission using the first resource.

[0111] In one embodiment of the present disclosure, the information about the first resource includes information indicating a power boost value when transmitting using the first resource.

[0112] In one embodiment of the present disclosure, the information about the first resource is included in a Control Information subfield in a Control field of the control information.

[0113] In one embodiment of the present disclosure, the Control field is a High Throughput (HT) Control field, and when a value of a Control ID subfield included in the HT Control field corresponds to Ultra High Reliability (UHR) link adaptation, the Control Information subfield includes information about the first resource.

[0114] In one embodiment of the present disclosure, the Control field is a High Throughput (HT) Control field, and when a value of a Control ID subfield included in the HT Control field corresponds to a common value of HT link adaptation (HLA), Extremely High Throughput (EHT) Link Adaptation (ELA), and Ultra High Reliability (UHR) link adaptation (ULA), the Control Information subfield includes information about the first resource.

[0115] In one embodiment of the present disclosure, the control field is a control field corresponding to Ultra High Reliability (UHR).

[0116] In one embodiment of the present disclosure, the Control Information subfield includes information indicating which of the first resource and second resources arranged contiguously in a frequency band is applied.

[0117] In one embodiment of the present disclosure, the application of the first resource and the application of second resources that are arranged contiguously in the frequency band are distinguished by the value of the RU Allocation subfield included in the Control Information subfield.

[0118] In one embodiment of the present disclosure, when the first resource is applied or when the bandwidth to which the contiguously arranged second resource is allocated is equal to or greater than a predetermined value, the Control Information subfield includes information about the recommended bandwidth but does not include information about the recommended resource location.

[0119] In one embodiment of the present disclosure, the Control Information subfield includes both information about the first resource and information about second resources that are arranged contiguously in a frequency band.

[0120] In one embodiment of the present disclosure, the Control Information subfield includes information about the first resource, but does not include information about second resources that are arranged contiguously in a frequency band.

[0121] A communication device according to one embodiment of the present disclosure includes a receiving circuit that receives control information for link adaptation including information regarding a first resource allocation that is discretely arranged in a frequency band, and a control circuit that controls the link adaptation based on the control information.

[0122] In a communication method according to an embodiment of the present disclosure, a communication device determines control information for link adaptation including information about first resources discretely arranged in a frequency band, and transmits the control information.

[0123] In a communication method according to one embodiment of the present disclosure, a communication device receives control information for link adaptation including information about first resources that are discretely arranged in a frequency band, and controls the link adaptation based on the control information.

[0124] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2024-076056, filed May 8, 2024, are incorporated herein by reference in their entirety.

[0125] One embodiment of the present disclosure is useful in wireless communication systems.

[0126] 100 Access point 200 Terminal (STA)

Claims

1. A communication device comprising: a control circuit that determines control information for link adaptation, the control information including information about first resources that are discretely arranged in a frequency band; and a transmission circuit that transmits the control information.

2. The communication device according to claim 1, wherein the information about the first resource includes information indicating whether the first resource or a second resource arranged contiguously in a frequency band is to be applied.

3. The communication device according to claim 1, wherein the information relating to the first resource includes allocation information of the first resource.

4. The communication device according to claim 1, wherein the information about the first resource includes at least one of a recommended coding and modulation scheme, a recommended number of spatial streams, and a recommended bandwidth for transmission using the first resource.

5. The communication device according to claim 1, wherein the information about the first resource includes information indicating a power boost value during transmission using the first resource.

6. The communication device according to claim 1, wherein the information regarding the first resource is included in a Control Information subfield in a Control field of the control information.

7. The communication device according to claim 6, wherein the Control field is a High Throughput (HT) Control field, and when a value of a Control ID subfield included in the HT Control field corresponds to Ultra High Reliability (UHR) link adaptation, the Control Information subfield includes information about the first resource.

8. The communication device according to claim 6, wherein the Control field is a High Throughput (HT) Control field, and when a value of a Control ID subfield included in the HT Control field corresponds to a value commonly corresponding to HT link adaptation (HLA), Extremely High Throughput (EHT) Link Adaptation (ELA), and Ultra High Reliability (UHR) link adaptation (ULA), the Control Information subfield includes information regarding the first resource.

9. The communication device according to claim 6, wherein the control field is a control field corresponding to Ultra High Reliability (UHR).

10. The communication device according to claim 6, wherein the Control Information subfield includes information indicating which of the first resource and second resources arranged contiguously in a frequency band is applied.

11. The communication device according to claim 6, wherein the application of the first resource and the application of second resources arranged contiguously in the frequency band are distinguished depending on the value of the RU Allocation subfield included in the Control Information subfield.

12. The communication device according to claim 6, wherein when the first resource is applied or when the bandwidth to which the contiguously arranged second resource is allocated is equal to or greater than a predetermined value, the Control Information subfield includes information on the recommended bandwidth but does not include information on the recommended resource position.

13. The communication device according to claim 6, wherein the Control Information subfield includes both information about the first resource and information about second resources that are arranged contiguously in a frequency band.

14. The communication device according to claim 6, wherein the Control Information subfield includes information about the first resource, but does not include information about second resources that are arranged contiguously in a frequency band.

15. A communication device comprising: a receiving circuit that receives control information for link adaptation, the control information including information regarding first resource allocations that are discretely arranged in a frequency band; and a control circuit that controls the link adaptation based on the control information.

16. A communication method, comprising: a communication device determining control information for link adaptation including information about first resources discretely arranged in a frequency band; and transmitting the control information.

17. A communication method, comprising: a communication device receiving control information for link adaptation including information about first resources discretely allocated in a frequency band; and controlling the link adaptation based on the control information.

Images