Communication devices and communication methods
By introducing control and transmission circuits into the wireless communication system and utilizing dRU-related information for link adaptation, the problem of low spectrum efficiency in wireless LANs is solved, achieving efficient wireless communication control and improving throughput.
Patent Information
- Application Number
- CN202580029134.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-05-08
- Filing Date
- 2025-04-03
- Publication Date
- 2026-11-17
AI Technical Summary
In the existing technology, wireless communication control methods for wireless LANs have not been fully studied, especially the problem of how to effectively utilize distributed frequency modulation resource units (dRUs) for link adaptation to improve spectrum efficiency under the strict power spectral density constraints in the 6 GHz band.
By introducing control and transmission circuits into the wireless communication system, information related to discretely configured dRUs in the frequency band is determined and transmitted, including parameters such as rRU/dRU allocation, MCS, number of spatial streams, and bandwidth. A request-based and non-request-based link adaptation process is adopted, and information is exchanged using newly added control ID and UHR control fields to achieve link adaptation suitable for dRUs and rRUs.
It improves wireless communication throughput and enhances spectral efficiency and communication quality through link adaptation suitable for dRU and rRU.
Smart Images

Figure CN123126004A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to communication devices and communication methods. Background Technology
[0002] As a standard for next-generation wireless LANs (Local Area Networks, also known as WLANs), IEEE 802.11bn is being planned as a successor to IEEE 802.11be, which is the standard for IEEE 802.11. Furthermore, IEEE 802.11be is also known as "Extremely High Throughput (EHT)," and IEEE 802.11bn is also known as "Ultra High Reliability (UHR)."
[0003] Existing technical documents
[0004] Non-patent literature
[0005] Non-patent document 1: IEEE 802.11-23 / 2020r1 High Level Perspective on Distributed Tone RU for 11bn
[0006] Non-patent document 2: IEEE 802.11-24 / 0400r0 Hybrid PPDU and Distribution Bandwidth for DRU Summary of the Invention
[0007] Control methods for wireless communications, such as wireless LANs, have not been fully studied.
[0008] The non-limiting embodiments disclosed herein contribute to providing communication devices and methods capable of appropriately controlling wireless communication.
[0009] A communication apparatus according to an embodiment of the present disclosure includes: a control circuit that determines control information for link adaptation, which includes information related to a first resource, the first resource being discretely configured in a frequency band; and a transmission circuit that transmits the control information.
[0010] It should be noted that these general or specific methods can be implemented by systems, apparatuses, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, apparatuses, methods, integrated circuits, computer programs, and recording media.
[0011] According to one embodiment of this disclosure, wireless communication control can be appropriately performed.
[0012] Further advantages and effects of one embodiment of this disclosure will be illustrated by the specification and drawings. These advantages and / or effects are provided by the various embodiments and the features described in the specification and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. Attached Figure Description
[0013] Figure 1 This is a diagram showing an example of the format of the ControlInformation subfield within the Extremely High Throughput (EHT) Link Adaptive (ELA) control field.
[0014] Figure 2 This is a diagram illustrating examples of transmission for regular resource units (rRU) and distributed RUs (dRU).
[0015] Figure 3 This is a diagram illustrating an example of the Solicited Link Adaptation process.
[0016] Figure 4 This is a diagram illustrating an example of an unsolicited link adaptation process (the case of non-triggered physical layer protocol data units (non-TB PPDUs)).
[0017] Figure 5 This is a diagram illustrating an example of a non-requested link adaptation process (in the case of TB PPDU).
[0018] Figure 6 This is a block diagram showing an example of the structure of a node.
[0019] Figure 7 This is a diagram showing an example of the format of the High Throughput (HT) Control field.
[0020] Figure 8 This is a diagram showing an example of the definition of a Control ID.
[0021] Figure 9 This is a diagram showing an example of a Control ID definition.
[0022] Figure 10 This is a diagram showing an example of the format of a UHR Control field.
[0023] Figure 11 This is a diagram showing an example of the format of the Frame Control field.
[0024] Figure 12 This is a diagram showing an example of the format of the Control Information subfield within the UHR Link Adaptive (ULA) control field.
[0025] Figure 13 This is a diagram illustrating an example of the definition of the rRU / dRU Allocation subfield.
[0026] Figure 14 This is a diagram illustrating an example definition of a DRU index.
[0027] Figure 15 This is a diagram illustrating an example definition of a DRU index.
[0028] Figure 16 This is a diagram illustrating an example definition of a DRU index.
[0029] Figure 17 This is a diagram showing an example of the format of the User Info field in a Basic Trigger frame.
[0030] Figure 18 This is a diagram illustrating an example of the indication process for rRU / dRU allocation in a basic trigger frame.
[0031] Figure 19 This is a diagram showing an example of the format of the Control Information subfield within the ULA Control field.
[0032] Figure 20 This is a diagram illustrating an example of the definition of the rRU / dRU Allocation subfield.
[0033] Figure 21 This is a diagram illustrating an example of the definition of the rRU / dRU Allocation subfield.
[0034] Figure 22 This is a diagram showing an example of the format of the user information field in a basic trigger frame.
[0035] Figure 23 This is a diagram illustrating an example of the indication process for rRU / dRU allocation in a basic trigger frame.
[0036] Figure 24 This is a diagram showing an example of the format of the Control Information subfield within the ULA Control field.
[0037] Figure 25 This is a diagram illustrating an example of the definition of the RU Allocation / Distribution BW subfield.
[0038] Figure 26 This is a diagram showing an example of the format of the Control Information subfield within the ULA Control field.
[0039] Figure 27 This is a diagram showing an example of the format of the Control Information subfield within the ULA Control field.
[0040] Figure 28 This is a diagram showing an example of the format of the Control Information subfield within the ULA Control field. Detailed Implementation
[0041] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
[0042] In the 6 GHz band, the power spectral density (PSD) limitation is more stringent compared to other bands. For example, for terminals in low-power indoor (LPI) mode (e.g., also known as stations or non-AP STAs), the PSD limitation can be specified as -1 dBm / MHz. In IEEE 802.11bn, the introduction of a "Distributed-Tone Resource Unit" (also referred to as dRU or DRU) is being investigated to overcome this PSD limitation and improve spectral efficiency by maximizing transmit power (e.g., see Non-Patent Documents 1, 2). Furthermore, a dRU, for example, refers to an RU composed of tone (frequency resources) discretely (or dispersedly, diffusely) configured within the band.
[0043] Link adaptation methods for dRU transmission have not been sufficiently studied. Existing standards specify a link adaptation process that optimizes communication speed by exchanging recommended modulation and coding schemes (MCS) or recommended RUs (e.g., tone positions) between terminals. However, this link adaptation process is defined for RUs (hereinafter also referred to as "Regular RU," rRU, or RRU) as defined in the existing 11ax / 11be standards. Furthermore, an rRU, for example, refers to an RU consisting of continuously configured tone (frequency resources) within a frequency band. Figure 1 This shows an example of the format of the Control Information subfield within the EHT link adaptation (ELA) Control subfield. Figure 1 The RU allocation shown defines rRU.
[0044] In a non-limiting embodiment of this disclosure, a method for appropriately controlling link adaptation for dRU transmission is described.
[0045] [Structure of a wireless communication system]
[0046] One embodiment of the wireless communication system disclosed herein may include, for example, an access point (AP) 100 and a STA 200 (not an AP STA). For example, AP 100 transmits downlink (DL) signals to STA 200. Additionally, STA 200 transmits uplink (UL) signals to AP 100, for example.
[0047] In one embodiment of this disclosure, the switching information (control information) for link adaptation includes information related to the dRU. The dRU-related information may include at least one of the information shown in Table 1. The information shown in Table 1 includes information related to either the rRU or the dRU. For example, the dRU-related information shown in Table 1 may include: "rRU / dRU" information indicating which of the dRU and rRU is being used; dRU or rRU allocation information ("rRU / dRU Allocation"); information indicating the recommended MCS (coding and modulation scheme) for transmissions using the rRU or dRU ("rRU-MCS / dRU-MCS"); information indicating the recommended number of spatial streams for transmissions using the rRU or dRU ("rRU-NSS / dRU-NSS"); or information indicating the recommended bandwidth for transmissions using the rRU or dRU ("rRU-BW / dRU-BW"). Additionally, the information related to dRU shown in Table 1 may also include information indicating the power boost value when transmitting using dRU (“dRU Power Boost”).
[0048] [Table 1]
[0049] Table 1 Examples of information related to dRU
[0050] Figure 2 Examples of transmissions for rRU and dRU are shown. Figure 2 The rRU transmission shown uses a bandwidth of 40 MHz. Additionally, in... Figure 2 The dRU transmission shown is performed with a bandwidth of 80 MHz. Figure 2 In the dRU transmission shown, when using 26-tone RUs (e.g., denoted as "RU26"), a maximum power boost of 11.14 dB can be achieved compared to rRUs because of the use of RUs distributed at 13-tone intervals for transmission.
[0051] Next, an example of the link adaptation process will be explained.
[0052] Figure 3 An example of a request-based (requested) link adaptation process is shown. Figure 4 An example of an unsolicited (non-TB PPDU) link adaptation process is shown. Figure 5This illustrates an example of an unsolicited (non-requested) link adaptation process (in the case of TB PPDU). TB PPDU is an abbreviation for Trigger-based Physical layer Protocol Data Unit.
[0053] exist Figure 3 In the example of the Solicited Link Adaptation (ULA) process shown, Node 1 sends an MCS request (MRQ) for UHR Link Adaptation to Node 2. The ULA (MRQ) may contain, for example, the RU or MRU (multiple resource unit) that is requesting the MCS recommendation value, as well as information related to the dRU. Upon receiving the ULA (MRQ) from Node 1, Node 2 sends an MCS feedback (MFB) to Node 1. The ULA (MFB) may contain, for example, information related to the dRU as shown in Table 1. Upon receiving the ULA (MFB) from Node 2, Node 1, based on the recommendation value contained in the ULA (MFB), determines which rRU or dRU is applied (rRU / dRU), the MCS, the number of spatial flows (NSS), the bandwidth (BW), and other transmission parameters, and then transmits the data.
[0054] exist Figure 4 In the example of an unsolicited link adaptation process (without a TB PPDU), Node 1 sends a ULA (MFB) to Node 2 without being requested by Node 2. The ULA (MFB) may contain, for example, dRU-related information as shown in Table 1. Upon receiving the ULA (MFB) from Node 1, Node 2 determines the rRU / dRU, MCS, NSS, BW, and other transmission parameters based on the recommended values contained in the ULA (MFB), and then transmits the data. Figure 4 In the example, node 2 performs a non-TB PPDU (non-trigger-based PPDU) transmission as an independent transmission without triggering.
[0055] exist Figure 5In the example of the unsolicited link adaptation process shown (in the case of TB PPDU), Node 2 sends a ULA (MFB) to Node 1 without being requested by Node 1. The ULA (MFB) may, for example, contain dRU-related information as shown in Table 1. Upon receiving the ULA (MFB) from Node 2, Node 1 determines the rRU / dRU, MCS, NSS, BW, and other transmission parameters based on the recommended values contained in the ULA (MFB), and instructs Node 2 to transmit data. Figure 5 In the example, the trigger frame sent by node 1 specifies the transmission parameters used by node 2 when sending a TB PPDU (trigger-based PPDU). Node 2 sends data based on the transmission parameters specified by the trigger frame.
[0056] Figure 6 An example structure of a node (e.g., corresponding to a communication device) is shown. The node could be, for example, an AP 100 or a STA 200. Figure 6 In this system, the control unit (e.g., corresponding to a control circuit) determines (or generates) control information for link adaptation, which includes information related to frequency resources (dRUs) discretely configured in the frequency band. Additionally, the control unit controls link adaptation, for example, based on control information received from other nodes. The communication unit (e.g., corresponding to a transmitting or receiving circuit) transmits and receives control information with other nodes.
[0057] According to one embodiment of this disclosure, throughput can be improved because link adaptation can be performed separately for dRU and rRU.
[0058] The following describes various implementations related to examples of control methods for link adaptive operation of dRU and rRU.
[0059] (Implementation Method 1)
[0060] In this embodiment, in the HT Control field (hereinafter also referred to as HT Control) of the exchange information used for link adaptation, the A-Control subfield (hereinafter also referred to as A-Control) is set with a Control ID (for example, a newly added Control ID) for the ULA. For example, if the value of the Control ID subfield included in the HT Control corresponds to the value of the ULA, the ControlInformation subfield in the HT Control contains information related to the dRU.
[0061] Figure 7 This shows an example of the structure of an A-Control within an HT Control.
[0062] like Figure 7 As shown, the MAC header contains an HT Control, and when the variant of the HT Control is HE (e.g., B0 and B1 are [1,1]), an A-Control exists. Figure 7 As shown, A-Control contains a Control List subfield (hereinafter also referred to as Control List) and padding bits. The Control List consists of one or more Control subfields. The Control subfield consists of a Control ID subfield (hereinafter also referred to as Control ID) and a Control Information subfield (hereinafter also referred to as ControlInformation).
[0063] Figure 8 This shows an example of a Control ID definition.
[0064] exist Figure 8 In the example, it is defined that when the Control ID value is 10 (which is an undefined value (Reserved) in the existing standard), the content of the Control Information is ULAControl. For example, in Figure 8 In addition to setting Control ID value=2, a new Control ID value=10 is also set. Control ID value=2 is defined as indicating that the content of Control Information is High Efficiency (HE) Link Adaptation (HLA) or EHT Link Adaptation (ELA), and Control ID value=10 is defined as indicating that the content of Control Information is ULA Control. Furthermore, although in Figure 8 In the example, Control ID value=10 is defined as representing a ULA Control, but other undefined values can also be defined as representing a ULA Control.
[0065] In specifying ULA Control (in Figure 8 In the case of Control ID value=10, Figure 7The Control Information shown may include, for example, information related to the dRU (or rRU) as shown in Table 1 (e.g., information related to the ULA).
[0066] Thus, in this embodiment, by setting the ControlID for ULA in the A-Control of HT Control, information related to the dRU or rRU can be notified in the exchange information used for link adaptation (e.g., the Control Information subfield). Therefore, according to this embodiment, link adaptation suitable for dRU and rRU respectively can be performed, and throughput can be improved.
[0067] (Implementation Method 2)
[0068] In this embodiment, in the A-Control of the HT Control used for link adaptation exchange information, a common (hereinafter referred to as "HLA / ELA / ULA shared") Control ID is set for HT Link Adaptation (HLA), EHT Link Adaptation (ELA), and ULA. For example, if the value of the Control ID subfield included in the HT Control is a value that corresponds to the common value of HLA / ELA / ULA, the Control Information subfield in the HT Control contains information related to dRU.
[0069] Alternatively, for example, a ULA can be indicated by setting the value in the ControlInformation subfield that shares a Control ID with HLA / ELA / ULA (e.g., the value of the RU Allocation subfield). In other words, HLA, ELA, and ULA can be distinguished based on the value in the Control Information subfield that shares a Control ID with HLA / ELA / ULA.
[0070] Furthermore, in this embodiment, the structure of the A-Control within the HT Control can be, for example, the same as in embodiment 1 (e.g., Figure 7 The structures are the same.
[0071] Figure 9 This shows an example of a Control ID definition.
[0072] exist Figure 9In the example, a control shared by HLA / ELA / ULA (also known as the HLA / ELA / ULA Control) is defined when Control ID value=2. When specifying the HLA / ELA / ULA Control (in... Figure 9 In the case where Control ID value=2) and the value of Control Information indicates ULA, Figure 7 The Control Information shown may include, for example, information related to the dRU (or rRU) as shown in Table 1 (e.g., information related to the ULA).
[0073] For example, as a value of Control Information, the RU Allocation subfield within the Control Information subfield can be defined as the "rRU / dRU Allocation" subfield, which represents the allocation of rRUs or dRUs, and the value of rRU / dRU Allocation can be used to indicate the ULA.
[0074] Thus, in this embodiment, by setting a shared Control ID for HLA / ELA / ULA in the A-Control of HT Control and indicating the ULA through the value of the Control Information subfield, information related to the dRU or rRU can be notified in the exchange information used for link adaptation (e.g., the Control Information subfield). Therefore, according to this embodiment, link adaptation suitable for dRU and rRU respectively can be performed, and throughput can be improved.
[0075] Furthermore, in this embodiment, since information related to ULA, as well as information related to HLA and ELA, is associated with a common Control ID, i.e., associated with an existing Control ID, it is possible to retain undefined values (reserved) in the Control ID subfield for future standard extensions.
[0076] (Implementation Method 3)
[0077] In this embodiment, a "UHR Control" field (a newly added Control field) corresponding to UHR is set in the MAC header. For example, in addition to existing control fields (e.g., HT Control field), a new UHR Control field can be set (or defined) in the MAC header.
[0078] Figure 10 This shows an example of the structure of the UHR Control field.
[0079] like Figure 10 As shown, the MAC header contains a UHR Control field (hereinafter, UHR Control). Figure 10 When the variant within the UHR Control shown is a UHR (e.g., B0 and B1=[0,0]), the UHR Control contains an A-Control subfield. For example... Figure 10 As shown, A-Control contains a Control List and padding bits. The Control List consists of one or more Control subfields. Each Control subfield consists of a Control ID and Control Information.
[0080] Control Information may include, for example, information related to dRU (or rRU) as shown in Table 1 (e.g., information related to UHR link adaptation).
[0081] Here, in Figure 10 In the example, the UHR Control is 8 octets in size, with 2 bits used to specify variants of the UHR Control (e.g., B0 and B1), and the Control ID is 4 bits in size. In this case, the Control Information is at most 58 bits in size. For example, because... Figure 7 The HT Control's ControlInformation size is at most 26 bits, therefore compared to the HT Control, Figure 10 The UHR Control shown can be configured with more information. Additionally, in Figure 10 In the example, the size of the UHR Control field is set to 8 octets, but the size of the UHR Control field is not limited to this and can be other sizes.
[0082] Figure 11 Show Figure 10 The format example shown is for the Frame Control field. Figure 11The “+UHRC” subfield shown is a field indicating whether the MAC header contains UHR Control. For example, undefined (reserved) values for the Subtype subfield or Control Frame Extension subfield of the existing standard Frame Control field can be defined (e.g., newly defined) to make its representation format include the Frame Control field format containing the +UHRC subfield. Figure 11 This shows an example of a format that includes a +UHRC subfield when the Control Frame Extension subfield is 12.
[0083] Thus, according to this embodiment, by setting the UHR Control field (the newly added Control field) in the MAC header, information related to the dRU or rRU can be notified in the exchange information used for link adaptation (e.g., the Control Information subfield). Therefore, according to this embodiment, link adaptation suitable for dRU and rRU respectively can be performed, and throughput can be improved.
[0084] The above embodiments 1 to 3 have described structural examples (frame structure examples) of exchange information for link adaptation. In the following embodiments 5 to 8, examples of control information included in the exchange information for link adaptation (e.g., the ControlInformation subfield) will be described.
[0085] (Implementation Method 4)
[0086] In this embodiment, the case where the control information in the Control Information subfield includes information indicating which of the rRU and dRU is applied (e.g., a subfield specifying rRU / dRU) will be described.
[0087] Figure 12 This shows an example of the format of the Control Information subfield within the Control subfield (hereinafter also referred to as the ULA Control (ULAControl) subfield) when a ULA is specified.
[0088] exist Figure 12 The Control Information subfield shown contains a "rRU / dRU" subfield defined in B25, specifying either the rRU or dRU. Furthermore, the specified rRU / dRU (rRU or dRU) is used as the reference point. Figure 12The “rRU / dRUAllocation” subfield shown switches between RU allocation (rRU case) and dRU allocation (dRU case) in 11be. In other words, when dRU is specified, the existing RU and MRU are interpreted as DRU in the rRU / dRU Allocation subfield.
[0089] Figure 13 This shows an example definition of the rRU / dRU Allocation subfield. For example... Figure 13 As shown, the DRU is defined in the same way as existing RUs and MRUs (e.g., corresponding to rRUs). In Figure 13 In this process, the system switches between RU and MRU and DRU based on the value of the rRU / dRU subfield within the Control Information subfield.
[0090] Figure 14 This shows an example definition of the DRU index for a 20 MHz UHR PPDU. Figure 14 As shown, the subcarrier index is defined relative to the existing RU (e.g., rRU) with an interval (i: subcarrier separation interval) corresponding to each size (tone number) of the dRU. Figure 14 In the example, the subcarriers (or tones) used to configure the dRU are set by the start subcarrier index, the end subcarrier index, and the subcarrier interval i. For example, in the case of a 26-tone DRU, the subcarrier index interval (i) is 9; in the case of a 52-tone DRU, the subcarrier index interval (i) is 4; and in the case of a 106-tone DRU, the subcarrier index interval (i) is 2.
[0091] Similarly, Figure 15 This shows an example definition of the DRU index for a 40 MHz UHR PPDU. Figure 16 An example definition of the DRU index for an 80 MHz UHR PPDU is shown. The DRU index for 160 / 320 MHz UHR PPDUs can also be defined similarly. Additionally, in Figure 14 , Figure 15 and Figure 16 The definition of the DRU index shown can be used to define the dRU index using subcarriers other than those not used for signal configuration (such as Guard or Null subcarriers).
[0092] Thus, in this embodiment, by including a subfield for specifying rRU / dRU in the control information within the Control Information subfield, information related to the dRU or rRU can be notified based on the specified RU type (rRU or dRU). Therefore, according to this embodiment, link adaptation suitable for dRU and rRU respectively can be performed, and throughput can be improved.
[0093] Alternatively, the method for specifying rRU / dRU described in this embodiment can also be applied to the dRU / rRU indication method in the RU Allocation of the Basic Trigger Frame.
[0094] Figure 17 This shows an example of the format for the UHR variant User Info field in the basic trigger frame. For Figure 17 The rRU / dRU Allocation subfield shown can be used as follows: Figure 13 The DRU is defined in the same way as the existing RU and MRU, as shown. Alternatively, it can be defined through... Figure 17 The “rRU / dRU” subfield shown switches between RU and MRU and DRU. The rRU / dRU subfield can be defined in the undefined (reserved) bits of the existing EHT variant User Info fieldformat.
[0095] Figure 18 This example illustrates the process of indicating rRU / dRU allocation for a basic trigger frame. Figure 18 As shown, the AP sends basic trigger frames containing the rRU / dRU subfield and the rRU / dRU Allocation subfield to non-AP STA 1 and non-AP STA 2, respectively. Non-AP STA 1 and non-AP STA 2 receive the basic trigger frames from the AP and transmit data (e.g., TB PPDU) using the rRU or dRU allocated by the basic trigger frames.
[0096] Therefore, allocation information related to dRU or rRU can be notified based on the RU type (rRU or dRU) specified by the basic trigger frame.
[0097] In addition, Figure 17 The document describes the case where the rRU / dRU subfield is set in the user information field (e.g., terminal-specific information), but the rRU / dRU subfield can also be set in the common information field (e.g., terminal general information).
[0098] (Implementation Method 5)
[0099] In this embodiment, a method for distinguishing between the application of rRU and dRU (e.g., distinguishing RU types) based on the value of the RU Allocation subfield within the Control Information subfield will be described.
[0100] Figure 19 This shows an example of the format of the Control Information subfield within the ULA Control subfield.
[0101] exist Figure 19 In the Control Information subfield shown, rRU / dRU (e.g., rRU or dRU) are distinguished based on the value of the rRU / dRUAllocation subfield defined in B9-B16.
[0102] Figure 20 and Figure 21 This shows an example of the definition of the rRU / dRU Allocation subfield.
[0103] Figure 20 The following example illustrates this: Values 107 to 127, which are not defined in the existing standard in the “RU Allocation subfields B7-B1”, are defined to represent the DRU size and DRU index.
[0104] Figure 21 The following example illustrates: The values in B7-B1 of the RU Allocation subfield, which are different from... Figure 20 Undefined values, values not defined in existing standards, are defined to represent DRU size and DRU index. Figure 21 For example, when the value of B7-B1 of the RU Allocation subfield is 70, the bandwidth (MHz) is 80, 160, or 320, and the dRU bandwidth (MHz) is limited to 20, 40, or 80, the bandwidth used for dRU transmission (e.g., defined as 80, 160, or 320) can be interpreted as 20, 40, or 80. Additionally, for example, in... Figure 21 In the case where the value of B7-B1 in the RU Allocation subfield is 87 to 88, the value of the bandwidth (MHz) (20, 40, 80, 160 or 320) can be directly used as the bandwidth for dRU transmission.
[0105] Thus, in this embodiment, by distinguishing between rRU and dRU based on the RUAllocation subfield value within the Control Information subfield, information related to either dRU or rRU can be communicated. Therefore, according to this embodiment, link adaptation suitable for dRU and rRU respectively can be performed, and throughput can be improved.
[0106] In addition, in this embodiment, rRU / dRU is distinguished based on the RU Allocation subfield value, thereby eliminating the need to notify the information used to specify the RU type (rRU / dRU).
[0107] Alternatively, the method of distinguishing rRU / dRU by the RU Allocation subfield value described in this embodiment can also be applied to the dRU / rRU indication method of RU Allocation in the basic trigger frame.
[0108] Figure 22 This shows an example of the format of the UHR variant User Info field in the basic trigger frame. For Figure 22 The rRU / dRU Allocation subfield shown can be used as follows: Figure 20 or Figure 21 As shown, values in B7-B1 of the RU Allocation subfield that are not defined in the existing standard are defined to represent DRUs. This definition allows for the differentiation between rRUs and dRUs.
[0109] Figure 23 This example illustrates the process of indicating rRU / dRU allocation for a basic trigger frame. Figure 23 As shown, the AP sends a basic trigger frame containing the rRU / dRU Allocation subfield to both 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.
[0110] Therefore, it is possible to distinguish between rRU and dRU based on the RU Allocation subfield value indicated by the basic trigger frame, and to notify the allocation information associated with dRU or rRU.
[0111] (Implementation Method 6)
[0112] In this embodiment, a method is described in which the recommended distribution bandwidth (Distribution BW) or bandwidth (BW) is notified through the ControlInformation subfield when applying dRU or broadband rRU, without notifying other RU-related information (e.g., tone location information).
[0113] For example, when using a dRU or a broadband rRU (e.g., allocating an rRU with a bandwidth greater than a specified value), the Control Information subfield may contain information related to the recommended bandwidth (e.g., distributed bandwidth or BW) but not information related to the recommended tone location.
[0114] Here, distribution bandwidth refers to the bandwidth used in the dRU (e.g., the bandwidth between the two ends of the dRU). In this embodiment, the information notified is set (e.g., limited to) information related to the recommended distribution bandwidth or recommended bandwidth (BW) because when using a dRU or a wideband rRU, the transmission characteristics are less dependent on the RU's location (Tone location) due to frequency diversity effects. In this embodiment, this property is utilized to omit the notification of other information (e.g., Tone location information) while notifying the recommended distribution bandwidth or bandwidth (BW).
[0115] Figure 24 This shows an example of the format of the Control Information subfield within the ULA Control subfield.
[0116] exist Figure 24 The Control Information subfield shown indicates the dRU size or recommended distributed bandwidth through the value of the “RU Allocation / Distribution BW” subfield defined in B9-B16. Figure 25 Show Figure 24 The example shown is a definition of the RU Allocation / Distribution BW subfield. Figure 25 As shown in the example, an undefined value in the RU Allocation subfield of 11be can be defined as representing the DRU size and distribution BW. Figure 25 In the example, the dRU index may not be defined.
[0117] Figure 26 This shows another formatted example of the Control Information subfield within the ULA Control subfield. Figure 26 The Control Information subfield shown uses the value of the “Distribution BW” subfield defined in B18-B20 to indicate the distribution bandwidth. Figure 26 The Distribution BW subfield shown is a field that replaces the interpreted BW subfield defined in the existing 11be. Additionally, in Figure 26 Alternatively, the RUAllocation subfield can be omitted.
[0118] Thus, in this embodiment, when applying a dRU or a broadband rRU, by notifying the recommended distribution BW or bandwidth (BW), link adaptation suitable for the dRU and rRU respectively can be performed according to the notified recommended distribution BW or recommended BW, thereby improving throughput.
[0119] (Implementation Method 7)
[0120] In this embodiment, the case where the Control Information subfield contains information related to both rRU and dRU is described. That is, the Control Information subfield defines subfields indicating recommended values for rRU and recommended values for dRU.
[0121] Figure 27 This shows an example of the format of the Control Information subfield within the ULA Control subfield.
[0122] exist Figure 27 The Control Information subfields shown, defined in B2-B4, B5-B8, B9-B16, B17, and B18-B20 respectively, represent the recommended values for applying rRUs, corresponding to the NSS, MCS, RU allocation, PS160, and BW defined in the existing ELA Control (ELAControl) subfields.
[0123] In addition, Figure 27The Control Information subfields shown, defined in B25-B27, B28-B31, B32-B39, B40, and B41-B43 respectively, represent the recommended values for applying dRUs, corresponding to the NSS, MCS, RU allocation, PS160, and BW values defined in the existing ELA Control subfields. Additionally, the values defined in... Figure 27 The dRU-Power Boost of the B44-TBD is information indicating the power boost value when the dRU is transmitting.
[0124] Thus, in this embodiment, the Control Information subfield defines subfields indicating recommended values for rRUs and recommended values for dRUs. This enables link adaptation tailored to dRUs and rRUs respectively, thereby improving throughput.
[0125] (Implementation Method 8)
[0126] In this embodiment, a method is described that includes information related to the dRU but not information related to the rRU in the Control Information subfield. In this embodiment, for example, when using an rRU, the ELA Control specified in 11be can be used.
[0127] Figure 28 This shows an example of the format of the Control Information subfield within the ULA Control subfield. Figure 28 The Control Information subfields shown, defined in B2-B4, B5-B8, B9-B16, B17, and B18-B20 respectively, represent the recommended values for applying dRUs, corresponding to the NSS, MCS, RU Allocation, PS160, and BW values defined in the existing ELA Control subfields. Additionally, the values defined in... Figure 28 The dRU-Power Boost of the B25-TBD indicates the power boost value when the dRU is transmitting.
[0128] Thus, in this embodiment, the Control Information subfield contains information related to dRUs but not information related to rRUs. Therefore, for example, ULA Control and ELA Control can be used in combination to perform link adaptation suitable for dRUs and rRUs respectively, thereby improving throughput.
[0129] The various embodiments of this disclosure have been described above.
[0130] The above-described implementation methods can be used in combination or interchangeably as appropriate.
[0131] While embodiments have been described above with reference to the accompanying drawings, this disclosure is not limited to the above embodiments. Those skilled in the art will readily conceive of various modifications or alterations within the scope of the claims. It should be understood that these modifications or alterations are also within the technical scope of this disclosure. Furthermore, the constituent elements in the embodiments can be arbitrarily combined without departing from the spirit of this disclosure.
[0132] In the above embodiments, the term "part" used for each structural element can also be replaced with other terms such as "circuitry", "assembly", "device", "unit" or "module".
[0133] The interface name (frame name), field name, or subfield name described in the above embodiments may also be other names.
[0134] Furthermore, in the above embodiments, the field (or subfield) used for notifying control information is only one example; other fields or subfields may also be used. Additionally, the number of bits or octets used for notifying control information in each field or subfield is only one example; other numbers of bits or octets may also be used.
[0135] Furthermore, the signal format described in the above embodiments is only one example. It may also be other configurations that include adding other fields and deleting some fields, or other configurations that include adding other subfields and deleting some subfields among the above fields.
[0136] Furthermore, the parameters such as bandwidth (or distributed BW), RU size (e.g., dRU size), RU index (e.g., dRU index), subcarrier index, and subcarrier spacing i described in the above embodiments are all examples, and other values may also be used.
[0137] Furthermore, although the above embodiments illustrate a case based on the format specified in IEEE 802.11 as an example, the format of an embodiment of this disclosure is not limited to the IEEE 802.11 format.
[0138] This disclosure can be implemented in software, hardware, or software in cooperation with hardware. The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration), and the processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or it can be composed of a single chip containing some or all of the functional blocks. An LSI may also include data input and output. Depending on the degree of integration, an LSI may also be referred to as an "IC (Integrated Circuit)," a "System LSI," a "Super LSI," or an "Ultra LSI."
[0139] 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. Alternatively, it can utilize a programmable FPGA (Field Programmable Gate Array) manufactured using the LSI, or a reconfigurable processor that can reconfigure the connections or settings of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.
[0140] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.
[0141] This disclosure can be implemented in all kinds of devices, apparatuses, and systems with communication capabilities (collectively referred to as "communication devices"). A communication device may also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these units. 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 an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.
[0142] Communication devices are not limited to portable or movable devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. Examples include: smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.
[0143] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.
[0144] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.
[0145] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.
[0146] In addition, in recent years, CPS (Cyber Physical Systems), a new concept that creates new added value through information collaboration between physical space and cyberspace, has attracted much attention in IoT (Internet of Things) technology. This CPS concept can also be adopted in the above implementation.
[0147] That is, as a basic configuration of CPS, for example, it is possible to connect edge servers located in physical space to cloud servers located in information space via a network, and to process data in a distributed manner through processors mounted on both servers. Here, the processing data generated in the edge server or cloud server is preferably generated on a standardized platform, which improves the efficiency of building systems that include various sensor arrays or IoT application software.
[0148] A communication apparatus according to an embodiment of the present disclosure includes: a control circuit that determines control information for link adaptation, which includes information related to a first resource, the first resource being discretely configured in a frequency band; and a transmission circuit that transmits the control information.
[0149] In one embodiment of this disclosure, the information associated with the first resource includes information indicating which of the first and second resources is being applied, the second resource being continuously configured in a frequency band.
[0150] In one embodiment of this disclosure, the information related to the first resource includes the allocation information of the first resource.
[0151] In one embodiment of this disclosure, the information related to the first resource includes at least one of the following: a recommended coding and modulation scheme, a recommended number of spatial streams, and a recommended bandwidth for transmission using the first resource.
[0152] In one embodiment of this disclosure, the information associated with the first resource includes information representing a power boost value when transmitting using the first resource.
[0153] In one embodiment of this disclosure, the information related to the first resource is included in a control information subfield within the control field of the control information.
[0154] In one embodiment of this disclosure, the control field is a high throughput control field, i.e., an HT control field. When the value of the control ID subfield included in the HT control field is the value corresponding to the ultra-high reliability link adaptive (UHR) link adaptive, the control information subfield includes the information related to the first resource.
[0155] In one embodiment of this disclosure, the control field is a high throughput control field, i.e., an HT control field. When the value of the control ID subfield included in the HT control field is a value that corresponds to HLA, ELA, and ULA, the control information subfield includes the information related to the first resource. HLA refers to HT link adaptation, ELA refers to ultra-high throughput link adaptation, i.e., EHT link adaptation, and ULA refers to ultra-high reliability link adaptation, i.e., UHR link adaptation.
[0156] In one embodiment of this disclosure, the control field is a control field corresponding to Ultra-High Reliability (UHR).
[0157] In one embodiment of this disclosure, the control information subfield includes information indicating which of the first and second resources is being applied, the second resource being configured continuously in the frequency band.
[0158] In one embodiment of this disclosure, the application of the first resource is distinguished from the application of the second resource continuously configured in the frequency band based on the value of the RU allocation subfield included in the control information subfield.
[0159] In one embodiment of this disclosure, when the first resource is applied, or when the bandwidth allocated to the continuously configured second resource is above a predetermined value, the control information subfield includes information related to the recommended bandwidth, but does not include information related to the recommended resource location.
[0160] In one embodiment of this disclosure, the control information subfield simultaneously includes information related to the first resource and information related to the second resource continuously configured in the frequency band.
[0161] In one embodiment of this disclosure, the control information subfield includes the information related to the first resource, but does not include the information related to the second resource that is continuously configured in the frequency band.
[0162] A communication apparatus according to an embodiment of the present disclosure includes: a receiving circuit that receives control information for link adaptation including information related to a first resource, the first resource being discretely configured in a frequency band; and a control circuit that controls the link adaptation based on the control information.
[0163] In a communication method according to an embodiment of this disclosure, the communication device performs the following steps: determining control information for link adaptation that includes information related to a first resource, the first resource being discretely configured in a frequency band; and transmitting the control information.
[0164] In a communication method according to an embodiment of this disclosure, the communication device performs the following steps: receiving control information for link adaptation that includes information related to a first resource, the first resource being discretely configured in a frequency band; and controlling the link adaptation based on the control information.
[0165] The entire contents of the specification, drawings and abstract contained in Japanese Patent Application No. 2024-076056, filed on May 8, 2024, are incorporated herein by reference.
[0166] Industrial applicability
[0167] One embodiment of this disclosure is useful for wireless communication systems.
[0168] Explanation of reference numerals in the attached figures
[0169] 100 access points
[0170] 200 Terminals (STA)
Claims
1. A communication device comprising: Control circuitry that determines control information for link adaptation, including information related to a first resource, which is discretely configured in a frequency band; and A transmitting circuit that transmits the control information.
2. The communication device according to claim 1, wherein, The information related to the first resource includes information indicating which of the first and second resources is being applied, the second resource being continuously configured in the frequency band.
3. The communication device according to claim 1, wherein, The information related to the first resource includes the allocation information of the first resource.
4. The communication device according to claim 1, wherein, The information related to the first resource includes at least one of the following: a recommended coding and modulation scheme, a recommended number of spatial streams, and a recommended bandwidth for transmissions using the first resource.
5. The communication device according to claim 1, wherein, The information related to the first resource includes information indicating the power boost value when transmitting using the first resource.
6. The communication device according to claim 1, wherein, The information related to the first resource is contained in the control information subfield within the control field of the control information.
7. The communication device according to claim 6, wherein, The control field is the high throughput control field, i.e., the HT control field. When the value of the control ID subfield included in the HT control field is the value corresponding to the ultra-high reliability link adaptation (UHR link adaptation), the control information subfield includes the information related to the first resource.
8. The communication device according to claim 6, wherein, The control field is the high throughput control field, i.e., the HT control field. When the value of the control ID subfield included in the HT control field is a value that corresponds to HLA, ELA and ULA, the control information subfield includes the information related to the first resource. HLA refers to HT link adaptation, ELA refers to ultra-high throughput link adaptation (EHT link adaptation), and ULA refers to ultra-high reliability link adaptation (UHR link adaptation).
9. The communication device according to claim 6, wherein, The control field is the control field corresponding to Ultra-High Reliability (UHR).
10. The communication device according to claim 6, wherein, The control information subfield contains information indicating which of the first and second resources is being applied, with the second resource being configured continuously in the frequency band.
11. The communication device according to claim 6, wherein, Based on the value of the RU allocation subfield contained in the control information subfield, the application of the first resource is distinguished from the application of the second resource continuously configured in the frequency band.
12. The communication device according to claim 6, wherein, When the first resource is applied, or when the bandwidth allocated to the continuously configured second resource is above a specified value, the control information subfield contains information related to the recommended bandwidth, but not information related to the recommended resource location.
13. The communication device according to claim 6, wherein, The control information subfield contains both information related to the first resource and information related to the second resource that is continuously configured in the frequency band.
14. The communication device according to claim 6, wherein, The control information subfield includes the information related to the first resource, but does not include the information related to the second resource that is continuously configured in the frequency band.
15. A communication device comprising: A receiving circuit receives control information for link adaptation, including information related to a first resource, which is discretely configured in a frequency band; and A control circuit that controls the link to adapt based on the control information.
16. A communication method, wherein, The communication device performs the following steps: The system determines control information for link adaptation, including information related to a first resource, which is discretely configured in the frequency band; and Send the control information.
17. A communication method, wherein, The communication device performs the following steps: Receive control information for link adaptation, including information related to a first resource, which is discretely configured in a frequency band; and The link is controlled to adapt based on the control information.
Citation Information
Patent Citations
Chemical vaporizer
JP2024076056A
