Access point, terminal, and communication method

Abstract

This access point includes: a communication circuit for transmitting a control signal including, in a single information field, an allocation of one or more resources for random access to which an allocation in which frequency resources are discretely arranged is applied; and a control circuit for controlling reception of an uplink signal on the basis of the allocation of one or more resources.

Description

Access point, terminal, and communication method

[0001] The present disclosure relates to an access point, a terminal, and a communication method.

[0002] The Study Group (SG) is currently developing the technical specifications for IEEE 802.11bn (hereinafter referred to as "11bn") as the successor to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, IEEE 802.11be (hereinafter referred to as "11be"). 11be is also known as "Extremely High Throughput (EHT)," and 11bn is also known as "Ultra High Reliability (UHR)."

[0003] IEEE P802.11be / D5.0IEEE 802.11-23 / 0079r10, IEEE 802.11 UHR Proposed CSDIEEE 802.11-24 / 0209r1, Specification Framework for TGbnIEEE Std 802.11ax-2021IEEE 802.11-23 / 1511r1, Pilot Tone Allocation and Other Considerations of Tone-Distributed RUs for UHR

[0004] However, in wireless communication such as wireless LAN, a method for a terminal to transmit an uplink signal in response to an instruction of a control signal received from an access point (AP) has not been fully considered.

[0005] Non-limiting embodiments of the present disclosure contribute to providing an access point, a terminal, and a communication method that can improve the efficiency of transmission control in wireless communication.

[0006] An access point according to one embodiment of the present disclosure includes a communication circuit that transmits a control signal in which an information field contains an allocation of one or more resources for random access to which an allocation of frequency resources is applied in which discretely arranged frequency resources are allocated, and a control circuit that controls reception of an uplink signal based on the allocation of the one or more resources.

[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, for example, it is possible to improve the efficiency of transmission control in wireless communication.

[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 a Trigger frameDiagram showing an example of the format of a User Info fieldDiagram showing an example of the format of a Special User Info fieldDiagram showing an example of a Resource Unit (RU) allocationDiagram showing an example of the format of a Common Info fieldDiagram showing an example of a Trigger typeDiagram showing an example of an Association ID (AID)Diagram showing an example of a Random access (RA)-RU Information subfieldBlock diagram showing an example of the configuration of a part of an access point (AP)Block diagram showing an example of the configuration of a part of a terminalBlock diagram showing an example of an APDiagram showing an example of an AIDDiagram showing an example of an RU indexDiagram showing an example of a Trigger typeBlock diagram showing an example of the configuration of a terminalDiagram showing an example of RA-RU configuration using Distributed-tone RU (DRU)Diagram showing an example of the order of the User Info fieldDiagram showing an example of an RA-RU Information subfieldDiagram showing an example of RA-RU configuration using a DRUDiagram showing an example of RA-RU configuration using a DRUDiagram showing an example of AIDDiagram showing an example of AID

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

[0012] As mentioned above, IEEE is currently studying 11bn, which is the successor standard to 11be (see, for example, Non-Patent Documents 2 and 3).

[0013] [Example of Trigger Frame Configuration] 11be supports uplink Orthogonal Frequency-Division Multiple Access (OFDMA). An access point (AP, also called a "base station") transmits a control signal (e.g., called a "Trigger frame") instructing the transmission of an uplink OFDMA signal to multiple terminals (STA, also called "non-AP STA") accommodated by the AP.

[0014] In 11bn as well, the Trigger frame of 11be may be reused as a control signal that instructs multiple terminals to transmit uplink OFDMA signals.

[0015] The control signal may be directed to one or more terminals, and the number of terminals that transmit a response signal based on the control signal may be one or more.

[0016] For example, as shown in Fig. 1, the Trigger frame includes a MAC header, as well as a "Common Info field" and a "User Info List" (see, for example, Non-Patent Document 1). The Common Info field includes information common to multiple terminals multiplexed by OFDMA. The User Info List includes a "Special User Info field" and multiple "User Info fields."

[0017] FIG. 2 shows an example of the format of the User Info field, and FIG. 3 shows an example of the format of the Special User Info field.

[0018] The Special User Info field shown in FIG. 3 includes common information for terminals of 11be or later. For example, the Special User Info field may include common information for 11bn terminals. The Special User Info field is a field in which a special AID (Association ID, for example, AID=2007) is set in the User Info field. It is expected that the Special User Info field will notify common information between terminals that support 11bn (or UHR) (for example, also referred to as "UHR terminals"), such as information regarding the uplink bandwidth for terminals that support 11be (or EHT) (for example, also referred to as "EHT terminals").

[0019] Furthermore, the User Info field shown in FIG. 2 includes information specific to each terminal. For example, the "RU allocation" subfield of the User Info field shown in FIG. 2 uses information in the "UL BW" subfield of the Common Info field, the "UL BW Extension" subfield of the Special User Info field, and the "PS 160" subfield of the User Info field to notify resource information of an uplink signal transmitted by a terminal in response to a trigger frame from an AP. The uplink signal is also referred to as, for example, a TB PPDU (Trigger-Based (TB) Physical layer Protocol Data Unit (PPDU)). The resource information of the uplink signal may include, for example, information on the bandwidth of the TB PPDU, the size and location of an RU (Resource Unit, frequency resource allocation unit), and an MRU (Multiple RU).

[0020] For example, the UL BW subfield and UL BW Extension subfield indicate the bandwidth of the TB PPDU that the terminal can use (e.g., any of 20, 40, 80, 160, or 320 MHz). Then, the terminal identifies (or determines or specifies) the position and size of the RU to which the uplink transmission signal is allocated in the transmission band (communication band) of the TB PPDU, based on the combined value of the RU allocation subfield and the PS 160 subfield, for example, based on the table shown in Fig. 4 (see, for example, Non-Patent Document 1).

[0021] Fig. 5 is a diagram showing an example of the format of a Common Info field for EHT terminals. The "Trigger Type" subfield of the Common Info field shown in Fig. 5 includes information indicating the type of the Trigger frame. The type of the Trigger frame is, for example, the type of signal (uplink signal) that the AP causes the terminal to transmit.

[0022] 6 shows an example of the correspondence relationship (table format) between the value of the Trigger Type subfield and the type of Trigger frame (see, for example, Non-Patent Document 1). In 11be, the types shown in FIG. 6 are defined as Trigger types.

[0023] Furthermore, for example, the Trigger Dependent User Info subfield of each of the User Info field shown in FIG. 2 and the Special User Info field shown in FIG. 3, and the Trigger Dependent Common Info subfield of the Common Info field shown in FIG. 5, contain common information that depends on the Trigger Type.

[0024] [Distributed-tone RU (DRU)] In 11bn, "Distributed-tone RU" (hereinafter referred to as DRU) is introduced to the resource allocation of TB PPDUs transmitted by terminals in response to trigger frames (see, for example, Non-Patent Document 3). DRU refers to an RU configured by tones that are distributed discretely (or dispersedly or diffusely) over a specific bandwidth. In 11bn, for example, the band in which RUs are distributed discretely in a DRU is also called the "Distribution Bandwidth (Distribution BW)."

[0025] For example, in existing standards prior to 11be, RUs (hereinafter also referred to as "Regular RUs (RRUs)") consisting of multiple consecutive tones in the frequency domain are assigned to each terminal as TB PPDU resources.

[0026] On the other hand, in the 6 GHz band supported by 11bn, there is a provision that limits the power spectrum density (PSD) of terminals (e.g., non-AP STAs) in the LPI (Low Power Indoor) band to a specified value (e.g., -1 dBm / MHz). In 11bn, for example, approximately 13 tones correspond to 1 MHz, so the above provision may limit the PSD per tone when using an RRU.

[0027] Therefore, by applying DRU, the PSD per tone can be improved by distributing the tones allocated to each terminal and reducing the number of tones per 1 MHz. This power boost gain of DRU can improve uplink throughput.

[0028] [About random access processing] IEEE 802.11ax (hereinafter referred to as "11ax"), the previous standard of 11be, introduced OFDMA-based random access (RA). 11ax is also known as "High Efficiency (HE)."

[0029] For example, the AID12 subfield of the User Info field (e.g., FIG. 2) notifies an Association ID (AID), which is a unique ID assigned to a terminal at the time of association. Hereinafter, the method of allocating frequency resources (e.g., RUs) to a specific terminal by notifying the terminal of the AID assigned to the terminal will be referred to as "Scheduled access."

[0030] In 11ax, a specific AID is used in the AID12 subfield to indicate that the User Info field notifies an RU for RA (hereinafter referred to as "RA-RU"). Figure 7 shows an example of a definition of the AID12 subfield, including a definition of the AID for RA-RU. As shown in Figure 7, by setting AID = 0 or 2045, each terminal is notified that the frequency resource indicated by the RU Allocation subfield of the User Info field is an RA-RU (see, for example, Non-Patent Document 4). Note that, as shown in Figure 7, an RA-RU indicated by AID = 0 is used for random access by associated terminals, and an RA-RU indicated by AID = 2045 is used for random access by unassociated terminals.

[0031] In the RA-RU notification introduced in 11ax, one User Info field can notify a terminal of one or more consecutive RA-RUs in the frequency domain. For example, in the User Info field indicating the RA-RU, the RU Allocation subfield indicates the position of the starting RU of the RA-RU, which is an RRU, and the RU size. Also, in the RA-RU notification, for example, in B26-B31 of the User Info field, instead of the SS Allocation subfield indicating the number of spatial streams, an "RA-RU Information" subfield indicating information about the RA-RU is set. The RA-RU Information subfield indicates the number of consecutive RA-RUs in the frequency domain, with the RA-RU, which is the RRU notified by the RU Allocation subfield, as the starting RU. Figure 8 shows an example format of the RA-RU Information subfield. B26-B30 (5-bit information) shown in Figure 8 is the "Number Of RA-RU" subfield, which indicates the number of consecutive RA-RUs in the frequency domain (for example, in the range of 1 to 32). In addition, the number of spatial streams used in random access transmission of RA-RU may be set to (for example, limited to) 1.

[0032] In this way, the AP uses one User Info field to instruct the terminal to use multiple RA-RUs that use RRUs. A terminal that has data to transmit to the AP updates (decrements) an OFDMA random access backoff (OBO) counter by the number of RA-RUs instructed by the Trigger frame based on channel access of random access, and when the OBO counter reaches 0, randomly selects one RA-RU from the one or more RA-RUs instructed by the AP by the Trigger frame and transmits an uplink signal using the selected RA-RU.

[0033] An example of the random access process has been described above.

[0034] As mentioned above, the introduction of DRUs is being considered for 11bn, but the application of DRUs to RA-RUs has not been fully explored. For example, RA-RUs using RRUs, which are introduced in 11ax, may have transmission power limitations in the 6GHz band due to PSD regulations, which may result in degraded uplink throughput performance, similar to scheduled access. Furthermore, OFDMA multiplexing is difficult between the DRUs for scheduled access, which are being considered for introduction in 11bn, and RA-RUs that use RRUs, potentially complicating scheduling and increasing the amount of signaling. Thus, there is room for further study on the notification method for RA-RUs that use DRUs.

[0035] In a non-limiting example of the present disclosure, a method for notifying one or more RA-RUs using a DRU using one User Info field, similar to an existing RRU, is described. Also, in a non-limiting example of the present disclosure, a method for facilitating the introduction of an RA-RU using a DRU by reusing an existing Trigger frame to realize notification of an RA-RU using a DRU is described.

[0036] [Configuration of Wireless Communication System] The wireless communication system according to this embodiment may include, for example, an AP 100 (for example, a wireless transceiver) and a terminal 200 (for example, a wireless transceiver). For example, the AP 100 transmits a Trigger frame to the terminal 200 instructing it to transmit a TB PPDU, and the terminal 200 receives the Trigger frame. The terminal 200 selects one of the RA-RUs instructed by the Trigger frame, and transmits the TB PPDU to the AP 100 by random access. Note that a DRU can be applied to the RA-RU.

[0037] Fig. 9 is a block diagram showing a configuration example of a portion of an AP 100 according to an embodiment of the present disclosure. In the AP 100 shown in Fig. 9, a communication unit (e.g., corresponding to a communication circuit) transmits a control signal (e.g., a trigger frame) in which an information field (e.g., a user info field) contains an allocation of one or more resources (e.g., RA-RU) for random access to which an allocation (e.g., DRU allocation) in which frequency resources (e.g., tones) are discretely allocated is applied, and a control unit (e.g., corresponding to a control circuit) controls reception of an uplink signal based on the allocation of one or more resources.

[0038] 10 is a block diagram showing a configuration example of a portion of a terminal 200 according to an embodiment of the present disclosure. In the terminal 200 shown in FIG. 10, a communication unit (e.g., corresponding to a receiving circuit) receives a control signal (e.g., a trigger frame) in which an information field (e.g., a user info field) contains an allocation of one or more resources (e.g., RA-RUs) for random access to which an allocation in which frequency resources are discretely allocated (e.g., DRU allocation) is applied. A control unit (e.g., corresponding to a control circuit) controls transmission of an uplink signal based on the control signal.

[0039] First Embodiment [Configuration Example of AP 100] FIG. 11 is a block diagram showing a configuration example of the AP 100. As shown in FIG.

[0040] The AP 100 generates a Trigger frame that instructs the terminal 200 to transmit a TB PPDU (uplink signal, for example, a response signal from the terminal 200 in response to the Trigger frame), and transmits the Trigger frame to the terminal 200. The Trigger frame may include, for example, information instructing transmission by RA-RU.

[0041] The AP 100 shown in FIG. 11 may include, for example, a scheduling unit 101, a User Info generation unit 102, a Common Info generation unit 103, a Trigger frame generation unit 104, an error correction coding unit 105, a modulation unit 106, a radio transmission / reception unit 107, an OFDM demodulation unit 108, a Tone demapping unit 109, a demodulation unit 110, and an error correction decoding unit 111.

[0042] At least one of the scheduling unit 101, the User Info generation unit 102, the Common Info generation unit 103, the Trigger frame generation unit 104, the error correction coding unit 105, the modulation unit 106, the OFDM demodulation unit 108, the Tone demapping unit 109, the demodulation unit 110, and the error correction decoding unit 111 shown in FIG. 11 may be included in the control unit shown in FIG. 9, and the wireless transmission / reception unit 107 shown in FIG. 11 may be included in the communication unit shown in FIG. 9.

[0043] 11 , the scheduling unit 101 may perform scheduling for, for example, the terminal 200. For example, the scheduling unit 101 determines frequency resource information (for example, RU allocation information) including one or more RA-RUs that instruct TB PPDU transmission, and outputs the information to the user information generating unit 102 and the common information generating unit 103. The scheduling unit 101 also holds scheduling information related to the TB PPDU from the terminal 200, and outputs the information to the tone demapping unit 109, the demodulating unit 110, and the error correction decoding unit 111 for reception processing.

[0044] The frequency resource information (e.g., RU allocation information) may include, for example, the RU type (e.g., information indicating either a DRU or an RRU), the RU size, the RU location, and the number of RA-RUs. For example, if the RU type is a DRU, the frequency resource information may include information on the Tone interval, the Tone location (also referred to as the Tone offset or the Tone start location), and the number of RA-RUs using the DRU.

[0045] For example, the RU type may be included in the User Info field. For example, in the AID12 subfield of the User Info field, an AID that is reserved in 11be (e.g., 2008-2044, 2047-4094, see FIG. 7 ) may be used to indicate that the User Info field is a User Info field indicating an RA-RU using a DRU.

[0046] Furthermore, for example, the RU type may be included in the Common Info field. For example, a Trigger type (hereinafter referred to as "DRU Trigger") that prompts transmission of an uplink signal using RU allocation by a DRU may be defined (or added or set) using a value that is not used in 11be (Reserved; see, for example, FIG. 6) in the Trigger Type subfield of the Common Info field. For example, the DRU Trigger may indicate that RU allocation using a DRU is applied to both scheduled access and random access. When terminal 200 receives the DRU Trigger, it recognizes that the frequency resource information indicated by the RU allocation subfield of the User Info field is a DRU.

[0047] Furthermore, for example, the RU type may be notified in an RU allocation subfield of a User Info field (terminal-specific information). Terminal 200 recognizes that the frequency resource information indicated by the RU allocation subfield is a DRU if the indication is in a Reserved field (e.g., a field different from the field where RUs are defined in the EHT) of the RU allocation subfield value of the EHT.

[0048] An example of the method for notifying the above-mentioned RU type will be described later.

[0049] The User Info generating unit 102 generates a User Info field by converting control information including frequency resource information for a TB PPDU including one or more RA-RUs input from the scheduling unit 101 into predetermined bit information.

[0050] Here, in the User Info field that notifies an RA-RU that uses a DRU, a specific AID may be set in the AID12 subfield. For example, as shown in Fig. 12, in 11be, the reserved AIDs (values ​​of the AID12 subfield) "2043" and "2044" may be defined as RA-RU notifications that use a DRU for associated terminals and non-associated terminals, respectively. For example, in the case of RA-RU notifications that use a DRU, AID=2043 or 2044 may be set in the User Info field, indicating that the RA-RU indicated by the User Info field is an RA-RU to which DRU allocation applies.

[0051] Furthermore, in the User Info field that notifies the RA-RU, the RU allocation subfield may indicate the starting RU of the RA-RU. For example, terminal 200 may identify the starting position of the RA-RU to which the uplink transmission signal by random access in the transmission band of the TB PPDU is allocated and the RU size (e.g., the number of Tones that constitute the RU) based on the table shown in FIG.

[0052] 4, "Bandwidth (MHz)" indicates the transmission band of the TB PPDU, and "RU or MRU size" indicates the number of tones (RU size or MRU size) to which the uplink signal of terminal 200 is allocated. Also, in FIG. 4, "RU or MRU index" indicates the position of the RU or MRU in the TB PPDU band.

[0053] The RU or MRU index defines, for example, the Tone position for each RU or MRU size for each RRU and DRU. Figure 13 shows an example of the RU index for an RRU and a DRU when the RU size is 26 tones. In the definition of the RU index for the RRU and DRU shown in Figure 13, for example, the DC position is assigned Tone number 0, and Tones with frequencies lower than DC are assigned negative numbers, and Tones with frequencies higher than DC are assigned positive numbers. In Figure 13, for an RRU, an RU index consisting of two elements, [Tone start position: Tone end position], is defined. Also, in Figure 13, for a DRU, an RU index consisting of three elements, [Tone start position: Tone interval: Tone end position], is defined. Note that the Tone interval is the interval obtained by counting the number of valid Tones excluding Guard Tones and Null Tones. Tones are also sometimes called subcarriers.

[0054] Furthermore, in the User Info field that notifies the RA-RU, for example, B26-B30 (corresponding to the SS Allocation subfield in FIG. 2 ) may be set to the Number Of RA-RU subfield. The Number Of RA-RU subfield may notify the number of RA-RUs. For example, in the case of an RRU, the Number Of RA-RU subfield may indicate the number of consecutive RA-RUs in the frequency domain. For example, in the case of a DRU, the Number Of RA-RU subfield may indicate one or more RA-RU numbers used for the DRU. For example, multiple RA-RUs may be notified by the RU allocation subfield as RA-RUs with the same starting RA-RU, RU size, Tone interval, and Distribution bandwidth (or TB PPDU bandwidth) but different Tone start positions, and multiple Tone start positions of the DRU may be notified. An example of the number of RA-RUs in a DRU will be described later.

[0055] The User Info generating unit 102 generates a User Info field and a Special User Info field including the converted bit information, and outputs them to the Trigger frame generating unit 104 .

[0056] The common info generating unit 103 converts the control information for the TB PPDU (for example, the bandwidth of the TB PPDU, LTF symbol information, AP transmission power information, etc.) input from the scheduling unit 101 into predetermined bit information.

[0057] Here, when notifying an RA-RU that uses a DRU, a trigger type (for example, DRU Trigger) that prompts uplink transmission using the DRU may be set in the Trigger Type subfield as shown in Fig. 14. Note that when notifying an RA-RU that uses an RRU, for example, as in existing standards, any one of Basic, BSRP, or BQRP may be set in the Trigger Type subfield.

[0058] Furthermore, when a DRU Trigger is applied, the same Trigger frame format as that of a Basic Trigger may be used. For example, the same format as that of a Basic Trigger may be applied to the Trigger Dependent Common Info subfield and the Trigger Dependent User Info subfield, which contain information that depends on the Trigger type. For example, the DRU Trigger may not have a subfield of the Trigger Dependent Common Info subfield, as with a Basic Trigger.

[0059] Furthermore, when the DRU Trigger is applied, unlike the Basic Trigger, the Trigger Dependent Common Info subfield may include the Trigger type (for example, any one of Basic, BSRP, and BQRP) to which the RA-RU is applied as a Trigger subtype subfield. This enables the AP 100 to promote random access using the DRU for the same purposes as those of the existing standards.

[0060] The Common Info generating unit 103 generates a Common Info field including the converted bit information and outputs it to the Trigger frame generating unit 104 .

[0061] The trigger frame generation unit 104 generates a trigger frame including a Common Info field input from the Common Info generation unit 103, a Special User Info field input from the User Info generation unit 102, and a User Info List made up of User Info fields for multiple terminals 200. In addition to the Common Info field, Special User Info field, and User Info List, a MAC header, padding, and a frame check sequence (FCS) may be added to the generated trigger frame. The trigger frame generation unit 104 outputs the generated trigger frame to the error correction coding unit 105.

[0062] The error correction coding unit 105 receives as input a transmission data signal including the trigger frame received from the trigger frame generation unit 104, performs error correction coding on the input signal, and outputs the coded signal to the modulation unit 106.

[0063] Modulation section 106 performs modulation processing on the signal input from error correction coding section 105 and outputs the modulated data signal to radio transmission / reception section 107 .

[0064] If the modulated data signal is an Orthogonal Frequency Division Multiplexing (OFDM) signal, the AP 100 may perform transmission signal processing related to OFDM. For example, the AP 100 (e.g., the modulation unit 106) may map the modulated signal to a predetermined frequency resource, convert it into a time waveform by performing an Inverse Fast Fourier Transform (IFFT), and add a Cyclic Prefix (CP) to form an OFDM signal.

[0065] Radio transmitting / receiving section 107 performs predetermined radio transmission processing such as D / A (digital-to-analog) conversion and up-conversion to a carrier frequency on the modulated signal input from modulation section 106, and transmits the signal after radio transmission processing via an antenna to terminal 200. Radio transmitting / receiving section 107 also receives signals transmitted from terminal 200 via the antenna, performs predetermined radio reception processing on the received signals such as down-conversion to baseband and A / D (analog-to-digital) conversion, and outputs the signal after radio reception processing to OFDM demodulation section 108.

[0066] The OFDM demodulation unit 108 performs, for example, demodulation processing on the signal input from the wireless transmission / reception unit 107, and performs OFDM-related received signal processing on the obtained received signal (TB PPDU from the terminal 200). For example, the OFDM demodulation unit 108 performs CP removal processing and Fast Fourier Transform (FFT) processing, and outputs the processed signal to the Tone demapping unit 109.

[0067] The Tone demapping unit 109 acquires a received signal at a specified Tone position from the received signal input from the OFDM demodulation unit 108 based on frequency resource information input from the scheduling unit 101 (for example, frequency resource information for an RA-RU using an RRU or DRU notified by a Trigger frame), and outputs the acquired signal to the demodulation unit 110.

[0068] The demodulation unit 110 performs corresponding demodulation processing on the received signal input from the tone demapping unit 109 based on information on the modulation method of the receiving terminal (QPSK, 16QAM, etc.) input from the scheduling unit 101, and outputs the result of the demodulation processing to the error correction decoding unit 111.

[0069] The error correction decoding section 111 performs error correction decoding on the received signal input from the demodulation section 110, and outputs the decoded signal as a received data signal.

[0070] [Configuration Example of Terminal 200] FIG. 15 is a block diagram showing a configuration example of the terminal 200. As shown in FIG.

[0071] The terminal 200 shown in FIG. 15 may include, for example, a radio transceiver 201, a demodulator 202, an error correction decoder 203, a Common Info decoder 204, a User Info decoder 205, an error correction encoder 206, a modulator 207, a Tone mapping unit 208, and an OFDM modulator 209.

[0072] At least one of the demodulation unit 202, error correction decoding unit 203, Common Info decoding unit 204, User Info decoding unit 205, error correction coding unit 206, modulation unit 207, Tone mapping unit 208, and OFDM modulation unit 209 shown in FIG. 15 may be included in the control unit shown in FIG. 10, and the radio transmission / reception unit 201 shown in FIG. 15 may be included in the communication unit shown in FIG. 10.

[0073] 15 , radio transmission / reception section 201 receives a signal via an antenna, performs radio reception processing such as down-conversion and A / D conversion on the received signal, and outputs the obtained received signal to demodulation section 202. Radio transmission / reception section 201 also performs radio transmission processing such as up-conversion and D / A conversion on a signal input from OFDM modulation section 209, and transmits the signal after radio transmission processing from the antenna.

[0074] Demodulation section 202 performs demodulation processing on the received signal (received data) input from radio transmission / reception section 201 and outputs the demodulated signal to error correction decoding section 203 .

[0075] If the input signal is an OFDM signal, the terminal 200 may perform OFDM-related received signal processing. For example, the terminal 200 (for example, the demodulator 202) may perform CP removal processing and FFT processing.

[0076] The error correction decoding unit 203 decodes the demodulated signal input from the demodulation unit 202 and outputs the decoded signal as a received data signal. The error correction decoding unit 203 also outputs a Trigger frame from the received data signal to the Common Info decoding unit 204 and the User Info decoding unit 205.

[0077] The Common Info decoding unit 204 extracts the Common Info field from the Trigger frame input from the error correction decoding unit 203. The Common Info decoding unit 204 decodes terminal common information included in the Common Info field and outputs the terminal common information to the User Info decoding unit 205. For example, when the Common Info field includes an RU type (information indicating either a DRU or an RRU), the Common Info decoding unit 204 outputs the RU type to the User Info decoding unit 205.

[0078] The User Info decoding unit 205 extracts a User Info List from the Trigger frame input from the error correction decoding unit 203. The extracted User Info List includes, for example, one or more User Info fields and a Special User Info field. If there is no User Info field including the AID of the terminal 200 (if there is no resource allocation for Scheduled access) and if transmission data to the AP 100 is held, the User Info decoding unit 205 decodes the User Info field in which a specific AID is set in the AID12 subfield and in which an RA-RU notification is included, and acquires information about the RA-RU. When decoding the User Info field, the User Info decoding unit 204 may use, for example, in addition to the information in the User Info field, the terminal-common information input from the Common Info decoding unit 204 and the terminal-common information included in the Special User Info field.

[0079] The User Info decoding unit 205 acquires one or more pieces of RA-RU information indicated in the User Info field for RA-RU notification. For example, when the RU type is DRU, the User Info decoding unit 205 acquires a number of RA-RUs that have the same RU size, Tone interval, and Distribution bandwidth as the starting RU of the RA-RU, but different Tone start positions.

[0080] The User Info decoding unit 205, for example, updates an OBO counter for each of the multiple RA-RUs obtained by decoding, and when the OBO counter becomes 0, randomly selects one RA-RU from the multiple RA-RUs, and outputs the selected RA-RU information and control information for TB PPDU transmission (such as coding rate) to the error correction coding unit 206, modulation unit 207, and Tone mapping unit 208.

[0081] If the updated OBO counter does not become 0, the User Info decoding unit 205 does not output to the error correction coding unit 206, and the terminal 200 does not need to perform upstream transmission by random access (it does not need to perform subsequent transmission processing).

[0082] The error correction coding section 206 performs error correction coding on the transmission signal based on the control information (such as the coding rate) for TB PPDU transmission input from the User Info decoding section 205 , and outputs the signal to the modulation section 207 .

[0083] The modulation unit 207 modulates the signal coded by the error correction coding unit 206 using a predetermined modulation method based on the control information (such as the modulation method) for TB PPDU transmission input from the User Info decoding unit 205, and outputs the processed signal to the Tone mapping unit 208.

[0084] Based on the RA-RU information input from the User Info decoding unit 205, the Tone mapping unit 208 places the modulated signal input from the modulation unit 207 at a predetermined Tone position and outputs it to the OFDM modulation unit 209.

[0085] The OFDM modulation section 209 performs IFFT processing on the modulated signal after mapping from the Tone mapping section 208 and adds a CP to form an OFDM signal, and outputs the OFDM signal to the radio transmission / reception section 201.

[0086] The configuration examples of the AP 100 and the terminal 200 have been described above.

[0087] [Example of Operation of AP 100 and Terminal 200] Next, an example of operation of the AP 100 and terminal 200 will be described.

[0088] The AP 100 uses a Trigger frame to notify the terminal 200 of one or more RA-RUs using a predetermined RU type (either DRU or RRU) and instructs the terminal 200 to transmit a TB PPDU by random access. The terminal 200, for example, uses the received Trigger frame to identify a frequency resource for an RA-RU using a predetermined RU type (either DRU or RRU) for the terminal 200 and transmits a TB PPDU (uplink signal transmission) by random access.

[0089] 16 is a diagram showing an example of an RA-RU using a DRU. In FIG. 16, as an example, the RU type is DRU, the RU size of the RA-RU is 26 tones, the tone interval within one DRU is 9, the distribution bandwidth (or TB PPDU bandwidth) is 20 MHz, the tone start position is #6, and the number of RA-RUs = 4. Note that the RU type, the RU size of the RA-RU, the tone interval within one DRU, the distribution bandwidth, and the tone start position may be notified to terminal 200, for example, by the RU Allocation subfield. Also, the number of RA-RUs may be notified to terminal 200, for example, by the Number Of RA-RU subfield.

[0090] In Figure 16, the four RA-RUs (RA1 to RA4) are resources with the same RU size, tone interval, and distribution bandwidth, but different tone start positions. In Figure 16, tone start positions #6 to #9 are set for RA1 to RA4, respectively. Note that, as shown in Figure 16, tone numbers #1 to #9 may be assigned to each of the nine consecutive tones corresponding to the tone intervals within one DRU.

[0091] Also, in Figure 16, DRUs configured with shaded tones represent RUs for scheduled access, and RUs represented with different shades are assumed to be assigned to different terminals (e.g., STA#1 to #5).

[0092] A terminal 200 holding data addressed to AP 100 randomly selects one RA-RU from four RA-RUs with different Tone start positions, as instructed by a trigger frame from AP 100, and transmits an uplink signal to AP 100 using the selected RA-RU.

[0093] In this way, by applying the DRU to the RA-RU, a power boost gain can be obtained even in random access, improving uplink throughput performance. Furthermore, as shown in Figure 16, OFDMA multiplexing between a Scheduled RU to which the DRU is applied and an RA-RU to which the DRU is applied can be easily achieved. Furthermore, by reusing the existing Trigger frame, it is easy to introduce an RA-RU by the DRU in addition to an RA-RU by the RRU. Furthermore, since one or more RA-RUs by the DRU can be notified using one User Info field, it is possible to suppress an increase in overhead.

[0094] Next, a method for notifying the RU type and an example of the operation of the terminal 200 will be described.

[0095] <First Example> In the first example, the RU type is notified by the User Info field (terminal-specific information).

[0096] For example, as described above, among the values ​​of the AID12 subfield, an AID that is unused (Reserved) in 11be (e.g., 2008-2044, 2047-4094, see FIG. 7 ) may be used to notify the RU type. For example, an AID indicating an existing RA-RU (e.g., 0, 2045) is used to indicate an RA-RU using an RRU, as per the existing standards. Also, for example, an AID that is new to the existing standards may be used to indicate an RA-RU using a DRU.

[0097] Here, 2048-4094 of the AID12 subfield are unused AIDs in 11be, and are values ​​for which the most significant bit (MSB) of the AID12 subfield (12 bits) is 1. As shown in FIGS. 7 and 12, in existing 11be, the MSB of the AID12 subfield is 1 when AID=4095. AID=4095 indicates that the data in the User Info field after the AID12 subfield is a Padding field. Therefore, in the reception process implemented by existing terminals, when the MSB of the AID12 subfield is 1, the terminal is expected to regard the fields after the AID12 subfield as Padding fields and stop decoding the subsequent User Info fields.

[0098] Therefore, instead of using 2048-4094, any of the unused AIDs in 11be, 2008-2044, may be used as the AID indicating an RA-RU using a DRU. Any of the unused AIDs in 11be, 2008-2044, is an appropriate value that does not affect the reception processing of existing terminals. For example, as shown in Fig. 12, AID12 subfield = 2043 and 2044 may be used to indicate an RA-RU using a DRU.

[0099] It should be noted that the AID indicating an RA-RU using a DRU is not limited to any one of 2008 to 2044. For example, the AID indicating an RA-RU using a DRU may be any one of 2048 to 4094.

[0100] Furthermore, the specific AID indicating an RA-RU using a DRU is not limited to an AID unused in IEEE 802.11be, and may be, for example, an AID used for scheduled access (e.g., any of 1-2007; see FIG. 7). For example, AID12 subfields = 2005 and 2006 may be defined as values ​​for notifying associated terminals and non-associated terminals of an RA-RU using a DRU, respectively. For example, AP 100 (e.g., an AP supporting UHR (also referred to as a UHR AP)) does not use AID12 subfields = 2005 and 2006 as AIDs for associated terminals 200 (do not use them for scheduled access). In this way, by setting part of the AID for scheduled access to an AID indicating an RA-RU using a DRU, a reserved area in the AID12 subfield can be secured, and future extensibility of the standard can be maintained.

[0101] Next, an example of the operation of terminal 200 that receives an AID indicating an RA-RU will be described.

[0102] A terminal 200 supporting a DRU (e.g., a terminal for 11bn or later) identifies the frequency resource (RU) indicated by the trigger frame as an RA-RU that uses an RRU when AID=0 or 2045 is indicated in a trigger frame whose trigger type is Basic, RSRP, or BQRP. Also, a terminal 200 supporting a DRU identifies the frequency resource (RU) indicated by the trigger frame as an RA-RU that uses a DRU when AID for RA-RU (e.g., AID=2043 or 2044 in FIG. 12) is indicated in a trigger frame whose trigger type is Basic, RSRP, or BQRP.

[0103] Furthermore, when AID=0 or 2045 is indicated in a Trigger frame whose Trigger type is Basic, RSRP, or BQRP, a terminal 200 that does not support DRU (e.g., a terminal compatible with 11be or earlier) identifies the frequency resource (RU) indicated by the Trigger frame as an RA-RU that uses an RRU. Furthermore, when an AID for RA-RU (e.g., AID=2043 or 2044 in FIG. 12) is indicated in a Trigger frame whose Trigger type is Basic, RSRP, or BQRP, a terminal 200 that does not support DRU stops decoding the User Info field. For example, a terminal 200 that does not support DRU may recognize AID=2043 or 2044 as an unused AID (e.g., see FIG. 7) and stop decoding the User Info field.

[0104] In this way, by setting (or defining or newly adding) an AID indicating an RA-RU using a DRU as an AID indicating an RA-RU, AP 100 can instruct a terminal 200 that supports DRU to use both the RRU and DRU RA-RUs.

[0105] Furthermore, existing standards specify the order of AIDs in the User Info field in the Trigger frame (see, for example, Non-Patent Document 4). For example, as shown in Fig. 17, subfields in the User Info field are arranged in the notification order of a Scheduled access RU using the AID of terminal 200, an RA-RU with AID = 0 or 2045, and an Unassigned RU with AID = 2046. This order specification can reduce the load on the reception processing of terminal 200. For example, when a terminal 200 that does not hold uplink data detects a User Info field indicating an RA-RU or a User Info field indicating an Unassigned RU, it can stop subsequent reception processing.

[0106] A User Info field including an AID indicating an RA-RU using a DRU (e.g., AID=2043 or 2044 in FIG. 12 ; a newly added AID) may be placed, for example, after a User Info field notifying an Unassigned RU (AID=2046) with AID=2046 in the Trigger frame. A terminal 200 that does not support a DRU does not grasp the AID indicating an RA-RU using a DRU and recognizes it as an unused value (a Reserved value). Existing standards do not specify behavior when such an unused value is detected. For example, a terminal 200 that does not support a DRU may stop reception processing when it detects a Reserved value in the AID12 subfield. For this reason, by placing a User Info field including an AID indicating an RA-RU using a DRU after a User Info field notifying Unassigned RUs (AID=2046), safe reception processing as expected by the AP 100 can be expected even when a terminal 200 that does not support a DRU stops reception processing.

[0107] Furthermore, when a User Info field including a specific AID indicating an RA-RU using a DRU is arranged after a User Info field notifying an Unassigned RU (AID=2046), Special User Info including common information for 11bn terminals may indicate whether or not a meaningful (or not unused) User Info field (e.g., a User Info field notifying an RA-RU using a DRU) exists after the User Info field notifying an Unassigned RU (AID=2046). As a result, if a meaningful User Info field exists, the 11bn terminal performs decoding processing on the User Info fields after the User Info field notifying an Unassigned RU (AID=2046), and if no meaningful User Info field exists, it does not need to perform decoding processing on the User Info fields after the Unassigned RU (AID=2046). This reduces unnecessary reception processing by the 11bn terminal.

[0108] <Second Example> In a second example, the RU type is notified by the Common Info field (terminal common information).

[0109] For example, as described above, as shown in FIG. 14, a DRU Trigger that prompts uplink signal transmission to which DRU allocation is applied in the Trigger frame may be defined (for example, set or newly added) as the Trigger type.

[0110] As described above, the same format as the Basic Trigger may be applied to the DRU Trigger. Also, for example, the Trigger Dependent Common Info subfield of the DRU Trigger may include the Trigger type to which the RA-RU is applied (for example, any one of Basic, BSRP, and BQRP).

[0111] Below, a description will be given of a method for controlling a DRU Trigger and examples (examples 1, 2, and 3) of the operation of a terminal 200 that receives a DRU Trigger.

[0112] Example 1: In Example 1, with a DRU trigger, all RU allocation information (frequency resource allocation) from AP 100 is RU notification using DRU to terminals 200. In Example 1, whether notification is for scheduled access or random access, application of DRU is commonly instructed to all terminals 200.

[0113] Example 2: In Example 2, in the case of a DRU Trigger, an indication of the RU type (either DRU or RRU) may be notified by the User Info field. For example, a bit area that is unused (Reserved) in a Trigger frame other than a DRU Trigger may be read as an RU type in a DRU Trigger. In Example 2, either an RRU or a DRU can be individually indicated to the terminal 200 as the RU type indicated by each User Info field.

[0114] Example 3: In Example 3, in the case of a DRU Trigger, an indication of the RU type (either DRU or RRU) may be notified for each predetermined subchannel (e.g., 80 MHz) by the Trigger Dependent Common Info subfield of the Common Info field. In Example 3, either an RRU or a DRU can be indicated as the RU type for each subchannel individually.

[0115] An example of the operation of the terminal 200 that receives the DRU Trigger will be described.

[0116] A terminal 200 supporting a DRU (for example, a terminal for 11bn or later) identifies the frequency resource (RU) indicated by the Trigger frame as an RA-RU that uses an RRU when AID=0 or 2045 is indicated in a Trigger frame whose Trigger type is Basic, RSRP, or BQRP. Furthermore, a terminal 200 supporting a DRU may identify the frequency resource (RU) indicated by the DRU Trigger as an RA-RU that uses a DRU in the control of Example 1 described above, as an RA-RU that uses an RRU or a DRU in accordance with the RU type indication in the User Info field in the control of Example 2 described above, and as an RA-RU that uses an RRU or a DRU for each predetermined subchannel in accordance with the indication in the Trigger Dependent Common Info subfield in the control of Example 3 described above.

[0117] Furthermore, when AID=0 or 2045 is specified in a Trigger frame whose Trigger type is Basic, RSRP, or BQRP, a terminal 200 that does not support DRU (for example, a terminal of 11be or earlier) identifies the frequency resource (RU) specified by the Trigger frame as an RA-RU that uses an RRU. Furthermore, when a DRU Trigger (a Trigger type that is not supported by the terminal 200 that does not support DRU) is specified, the terminal 200 that does not support DRU stops decoding processing of subsequent Trigger frames.

[0118] In this way, by setting (e.g., defining, adding) the DRU Trigger, the AP 100 can instruct the terminal 200 that supports the DRU to use the DRU Trigger to instruct both the RRU and the DRU RA-RU.

[0119] <Third Example> In a third example, the RU type is notified by the RU allocation subfield of the User Info field (terminal-specific information).

[0120] For example, in the definition of the EHT RU allocation subfield value shown in Figure 4, there is a reserved area where no RU is defined (e.g., 21 values ​​from 107 to 127, not shown in Figure 4). RA-RUs using DRUs are defined in this reserved area. For example, an RU size of 52 tones may be defined in the EHT reserved area, and 18 patterns of RU allocations (RU index) with different tone start positions may be defined. RA-RUs using DRUs may also be defined by restricting the tone start position or distributed bandwidth. For example, an RU size of 26 tones may be defined in the EHT reserved area, with 9 patterns of RU allocations with different tone start positions, and an RU size of 52 tones may be defined in the EHT reserved area.

[0121] An example of the operation of terminal 200 receiving the reserved area in the EHT of the RU allocation subfield will be described below.

[0122] A terminal 200 that supports DRU (e.g., a terminal of 11bn or later) identifies the frequency resource (RU) indicated by the Trigger frame as an RA-RU that uses an RRU when an AID value (e.g., 0, 2045) specifying an RA-RU is indicated and a value other than the reserved area in the EHT of the RU allocation subfield (an area where the RU is defined in the EHT) is indicated. Also, a terminal 200 that supports DRU (e.g., a terminal of 11bn or later) identifies the frequency resource (RU) indicated by the Trigger frame as an RA-RU that uses a DRU when AID=0 or 2045 is indicated and a value other than the reserved area in the EHT of the RU allocation subfield (an area different from the area where the RU is defined in the EHT) is indicated.

[0123] Furthermore, when AID=0 or 2045 is specified and a value other than the reserved area in the EHT of the RU allocation subfield (an area where RUs are defined in the EHT) is specified, a terminal 200 that does not support DRU (for example, a terminal prior to 11be) identifies the frequency resource (RU) specified by the Trigger frame as an RA-RU that uses an RRU. Furthermore, when AID=0 or 2045 is specified and a value in the reserved area in the EHT of the RU allocation subfield (an indication of an unsupported RU) is specified, a terminal 200 that does not support DRU (for example, a terminal prior to 11be) stops decoding the Trigger frame from the RU Allocation subfield onwards.

[0124] In this way, by combining an RU allocation value that is not used by the HE / EHT terminal with an AID value that specifies an RA-RU, it is possible to prevent malfunction of the HE / EHT terminal while instructing the terminal 200 that supports DRU to use RA-RUs for both the RRU and the DRU using the RU allocation subfield.

[0125] The above has described a method for controlling the DRU Trigger, and an example of the operation of terminal 200 that receives the DRU Trigger and the Reserved area of ​​the RU allocation subfield.

[0126] The RU type notification method and an example of the operation of the terminal 200 have been described above.

[0127] An example of a method for notifying the number of RA-RUs using a DRU will be described below.

[0128] As described above, the AP 100 notifies the number of RA-RUs using the DRU (e.g., one or more RA-RUs) in the Number Of RA-RU subfield, for example. For example, multiple RA-RUs using a DRU may be RA-RUs with the same start RU, RU size, Tone interval, and Distribution bandwidth (TB PPDU bandwidth) notified in the RU allocation subfield, but with different Tone start positions. For example, multiple Tone start positions of the DRU may be notified.

[0129] An example of notification of the tone start position of the DRU will be described below.

[0130] <First Example> In a first example, the Tone start positions of each of multiple RA-RUs are notified (or set) non-contiguously in the frequency domain.

[0131] 16, a case has been described in which RA-RUs in which the Tone start positions of the DRUs are consecutive are notified for the number of RA-RUs. In a first example, RA-RUs in which multiple Tone start positions are non-consecutive are notified.

[0132] For example, the AP 100 may allocate more RA-RUs than the expected number of RAs to keep the RA-RU collision rate below a predetermined value. In other words, while some of the allocated RA-RUs are used for uplink signal transmission, there is a high possibility that unused RA-RUs will occur.

[0133] Therefore, in a first example, the Tones constituting each of the multiple RA-RUs (e.g., different RA-RUs) may be allocated discontinuously. For example, by arranging the Tones of the Scheduled access RU and the Tones for the RA-RU alternately, when the RA-RU is unused, the interference effect on the Scheduled access RU due to frequency offset can be reduced, and the performance of the Scheduled access RU can be improved.

[0134] When notifying non-consecutive RA-RUs, for example, non-consecutive Tone start positions may be notified using a fixed Tone interval greater than 1 (for example, the interval between the start positions of multiple RA-RUs). For example, if the fixed Tone interval is M [tone], non-consecutive Tones may be set as the Tone start positions of each RA-RU where the number of RA-RUs = N, such as #a, #(a + M), #(a + 2 × M), ..., #(a + (N - 1) × M). Note that Tone start position #a may be notified by the RU Allocation subfield.

[0135] The fixed tone interval may be variably set depending on the TB PPDU bandwidth (or distribution bandwidth). For example, if the TB PPDU bandwidth is a 20 MHz channel, a 1 tone interval (notified by continuous tones) may be set, and if it is a 40 MHz channel or greater, a 2 tone interval (notified by non-contiguous tones) may be set.

[0136] Also, for example, information regarding the tone interval at the start position of the tone between multiple RA-RUs may be notified. For example, as shown in Fig. 18, like the RA-RU Information subfield, the Number Of RA-RU subfield notifying the number of RA-RUs may be notified by 4 bits, and the tone interval at the start position between RA-RUs may be notified by a Tone Interval subfield of 1 bit (for example, either 1 tone interval or 2 tone intervals).

[0137] FIG. 19 is a diagram showing an example of an RA-RU using a DRU. In FIG. 19, as an example, the RU type is DRU, the RU size of the RA-RU is 26 tones, the tone interval within one DRU is 9, the distribution bandwidth (or TB PPDU bandwidth) is 20 MHz, the tone start position is #2, the number of RA-RUs is 4, and the tone interval of the tone start positions between RA-RUs is 2. The RU type, the RU size of the RA-RU, the tone interval within one DRU, the distribution bandwidth, and the tone start positions may be notified to terminal 200, for example, by an RU Allocation subfield. The number of RA-RUs may be notified to terminal 200, for example, by a Number Of RA-RU subfield. The tone interval of the tone start positions between RA-RUs may be notified to terminal 200, for example, by a Tone Interval subfield.

[0138] In Fig. 19, Tone start positions #2, #4, #6, and #8 (Tone intervals of two Tones) are set for four RA-RUs (RA1 to RA4). As shown in Fig. 19, Tone numbers #1 to #9 may be assigned to each of the nine consecutive tones corresponding to the Tone intervals within one DRU.

[0139] As shown in Figure 19, for example, by allocating Scheduled access RUs to Tones #1, #3, #5, #7, and #9, the Tone interval between Scheduled access RUs of different terminals may be widened. For example, if an RA-RU is unused in Figure 19, it is possible to reduce interference due to the frequency offset between Scheduled access RUs on either side of the Tone to which the RA-RU is allocated (between adjacent Tones).

[0140] Terminal 200 may calculate the Tone start position of an RA-RU using a DRU using a predetermined formula based on the notified DRU control information (e.g., the number of RA-RUs, the Tone start position of RA-RU#1, and the Tone interval of the DRU). For example, terminal 200 may calculate the Tone start position using a DRU of RA-RU resource number n (RA-RU#n) according to the following formula: Tone start position of RA-RU#n = mod(Tone start position of RA-RU#1+n-2, Tone interval of DRU)+1

[0141] In the above formula, n=1, ..., N (N indicates the number of RA-RUs), and the function mod(A, B) indicates the remainder when A is divided by B.

[0142] Here, the tone interval of the DRU is the interval counting only valid tones excluding null and guard tones. The tone start position of RA-RU#1 (e.g., RA1 in FIG. 19) and the tone interval of the DRU (the tone interval in one DRU) are notified in the RU Allocation subfield, and the number of RA-RUs is notified in the Number of RA-RU subfield.

[0143] FIG. 20 is a diagram showing another example of an RA-RU using a DRU. In FIG. 20, as an example, the RU type is DRU, the RU size of the RA-RU is 26 tones, the tone interval within one DRU is 9, the distribution bandwidth (or TB PPDU bandwidth) is 20 MHz, the tone start position is #8, and the number of RA-RUs is 4. The tone allocation shown in FIG. 20 shows the tone allocation when the tone start position of each RA-RU is calculated using the above-mentioned calculation formula. The RU type, the RU size of the RA-RU, the tone interval within one DRU, the distribution bandwidth, and the tone start position may be notified to terminal 200, for example, by the RU Allocation subfield. The number of RA-RUs may be notified to terminal 200, for example, by the Number Of RA-RU subfield.

[0144] In Fig. 20, Tone start positions #8, #9, #1, and #2 are set for four RA-RUs (RA1 to RA4), respectively. Note that, as shown in Fig. 20, Tone numbers #1 to #9 may be assigned to each of nine consecutive tones corresponding to the Tone interval within one DRU.

[0145] <Second Example> In a second example, the number of grouping tones is notified.

[0146] In the study of DRU in 11bn, a tone grouping method has been considered in which a predetermined number of consecutive tones are grouped together (for example, by applying "tone grouping") and distributed allocation (discrete allocation) is performed for each of the grouped tones (see, for example, Non-Patent Document 5). Hereinafter, the grouped tones (for example, allocation units) are also referred to as "tone groups," and the number of tones included in a tone group is also referred to as the "number of grouped tones."

[0147] Tone grouping has the advantage of improving the accuracy of channel estimation on the receiving side through smoothing processing using multiple tones, and the advantage of improving demodulation processing performance such as frequency offset correction processing. Applying tone grouping to RA-RU that uses DRU is expected to improve demodulation processing performance.

[0148] In a second example, the AP 100 may notify the terminal 200 of the number of Grouping Tones in the RA-RU that uses the DRU, by the User Info field or Common Info field of the Trigger frame.

[0149] For example, unused bits (Reserved) in the User Info field in the existing standard may be used to notify the number of Grouping tones. For example, the number of Grouping tones = 1 (no Tone grouping) and the number of Grouping tones = 2 (with Tone grouping) may be notified by one bit. Note that notification of the number of Grouping tones is not limited to using unused bits, and bits used in the existing standard may also be used (e.g., may be replaced).

[0150] FIG. 21 is a diagram showing another example of an RA-RU using a DRU. In FIG. 21, as an example, the RU type is DRU, the RU size of the RA-RU is 26 tones, the tone interval within one DRU is 9, the distribution bandwidth (or TB PPDU bandwidth) is 20 MHz, the tone start position is #6, the number of RA-RUs is 2, and the number of grouping tones is 2. Note that the RU type, RA-RU RU size, tone interval, distribution bandwidth, and tone start position may be notified to terminal 200, for example, by an RU allocation subfield. Also, the number of RA-RUs may be notified to terminal 200, for example, by a Number Of RA-RU subfield. Also, the number of grouping tones may be notified to terminal 200, for example, by an RA-RU Information subfield.

[0151] The number of RA-RUs (two in Figure 21) is the number of RA-RUs counted as one RA-RU after Tone grouping is applied. In Figure 21, RA-RU #1 (RA1) is composed of two tones at Tone start positions #6 and #7, and RA-RU #2 (RA2) is composed of two tones at Tone start positions #8 and #9, and so the RU size after Tone grouping is applied is 26 x 2 = 52 tones.

[0152] In this way, AP 100 can notify terminal 200 of one or more RA-RUs to which Tone grouping is applied using one User Info field without increasing overhead.

[0153] An example of the operation of the AP 100 and the terminal 200 has been described above.

[0154] Thus, in this embodiment, AP 100 and terminal 200 transmit and receive a Trigger frame in which the allocation of one or more RA-RUs to which DRU allocation is applied is included in one User Info field, and control the transmission and reception of uplink signals (RA signals) based on the allocation of one or more RA-RUs.

[0155] As a result, for example, the AP 100 can notify the terminal 200 of one or more RA-RUs using a DRU using one User Info field, similar to existing RRUs. Also, since notification of an RA-RU using a DRU can be realized by reusing an existing Trigger frame (for example, a format configuration), it becomes easy to introduce an RA-RU using a DRU. Therefore, according to this embodiment, it is possible to improve the efficiency of transmission control in wireless communication.

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

[0157] Note that an AID indicating an RA-RU using a DRU may include (or be associated with) information regarding the Tone interval of the Tone start positions between multiple RA-RUs. For example, as shown in Figure 22, a specific AID indicating an RA-RU using a DRU may be associated with the Tone interval of the Tone start positions between multiple RA-RUs. By including information regarding the Tone interval of the Tone start positions between multiple RA-RUs in the AID12 subfield, the Tone intervals of the Tone start positions between multiple RA-RUs do not need to be notified individually, thereby suppressing an increase in overhead. In the example of Figure 22, AID12 subfields = 2041 and 2042 are defined as RA-RUs that use DRUs with a Tone interval of the Tone start positions = 2 (for example, the Tone start positions of each RA-RU are non-contiguous) for associated and unassociated terminals, respectively. Also, in the example of Figure 22, AID12 subfield = 2043 and 2044 are defined as RA-RUs that use DRUs with Tone interval = 1 (for example, the Tone start positions of each RA-RU are continuous) for associated terminals and unassociated terminals, respectively.

[0158] Furthermore, information regarding the number of grouping tones may be included (may be associated) in an AID indicating an RA-RU using a DRU. For example, as shown in FIG. 23, a specific AID indicating an RA-RU using a DRU may be associated with the number of grouping tones. By including information regarding the number of grouping tones in the AID12 subfield, the number of grouping tones does not need to be notified individually, thereby suppressing an increase in overhead. In FIG. 23, AID12 subfields = 2041 and 2042 are defined as RA-RUs using a DRU with a number of grouping tones = 2 (e.g., with Tone Grouping) for associated and unassociated terminals, respectively. Also, in FIG. 23, AID12 subfields = 2043 and 2044 are defined as RA-RUs using a DRU with a number of grouping tones = 1 (e.g., without Tone Grouping) for associated and unassociated terminals, respectively.

[0159] In addition, the control of the OBO counter used for channel access of random access may be controlled in common by the RA-RU using the RRU and the RA-RU using the DRU. For example, a single OBO counter may be used and updated based on the number of detected RA-RUs, regardless of the RA-RUs of the RRU and the DRU. This simplifies the control and makes implementation easier.

[0160] Alternatively, the OBO counter used for random access channel access may be controlled separately for an RA-RU that uses an RRU and an RA-RU that uses a DRU. For example, a separate OBO counter may be used for each of the DRU and the RRU, and each OBO counter may be updated for each of the RA-RUs of the RRU and the DRU based on the number of detected RA-RUs. This enables control that takes into account the collision rate and fairness in each of the RA-RU that uses an RRU and the RA-RU that uses a DRU.

[0161] Furthermore, an RA-RU to which a DRU is applied may be notified using multiple User Info fields in one Trigger frame. For example, RA-RUs with different MCSs and DRU resource information (RU size, Tone interval, number of Grouping tones, etc.) may be indicated by different User Info fields.

[0162] Furthermore, in the above-described embodiments, the uplink signal is not limited to the TB PPDU. For example, the above-described embodiments may be applied to DRU allocation of a PPDU (such as a UHR MU PPDU) that is not a response to a trigger frame.

[0163] Furthermore, the above-described embodiments are not limited to transmission and reception of uplink signals (for example, uplink PPDUs), but may also be applied to transmission and reception of downlink signals (for example, downlink PPDUs).

[0164] In addition, in each of the above-described embodiments, the field (or subfield) used for notifying control information (for example, information on an RA-RU to which a DRU is applied) is an example, and other fields or subfields may be used. Furthermore, the number of bits used for notifying control information in each field or subfield is an example, and other numbers of bits may be used.

[0165] In addition, in each of the above-mentioned embodiments, the values ​​of parameters such as the TB PPDU bandwidth, distribution bandwidth, RU size, RU index, DRU tone interval, tone interval at the tone start position between multiple RA-RUs, tone (or subcarrier) size, and number of grouping tones are examples and may be other values.

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] An access point according to one embodiment of the present disclosure includes a communication circuit that transmits a control signal in which an information field contains an allocation of one or more resources for random access to which an allocation of frequency resources is applied in which discretely arranged frequency resources are allocated, and a control circuit that controls reception of an uplink signal based on the allocation of the one or more resources.

[0177] In one embodiment of the present disclosure, the plurality of resources are resources having a bandwidth in which the frequency resources are discretely arranged and the same number of the frequency resources allocated to the uplink signal, but different starting positions of the frequency resources allocated to the uplink signal.

[0178] In one embodiment of the present disclosure, the starting positions of each of the plurality of resources are non-contiguous in the frequency domain.

[0179] In one embodiment of the present disclosure, the control signal includes information regarding intervals of the start positions among the plurality of resources.

[0180] In one embodiment of the present disclosure, in the allocation, allocation units including consecutive frequency resources are discretely arranged, and the control signal includes information regarding the number of frequency resources included in the allocation unit.

[0181] In one embodiment of the present disclosure, the control signal is a Trigger frame, and an association ID is set in a User Info field of the Trigger frame, indicating that the resource indicated by the User Info field is the resource to which the allocation applies.

[0182] In one embodiment of the present disclosure, the control signal is a trigger frame, and a trigger type that prompts transmission of the uplink signal to which the allocation is applied is set in the trigger frame.

[0183] A terminal according to one embodiment of the present disclosure includes a communication circuit that receives a control signal in which an information field contains an allocation of one or more resources for random access to which an allocation in which frequency resources are discretely arranged is applied, and a control circuit that controls transmission of an uplink signal based on the control signal.

[0184] In a communication method according to one embodiment of the present disclosure, an access point transmits a control signal in which an information field contains an allocation of one or more resources for random access to which an allocation in which frequency resources are discretely arranged is applied, and controls reception of an uplink signal based on the allocation of the one or more resources.

[0185] In a communication method according to one embodiment of the present disclosure, a terminal receives a control signal in which an information field contains an allocation of one or more resources for random access to which an allocation in which frequency resources are discretely allocated is applied, and controls transmission of an uplink signal based on the control signal.

[0186] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2024-070879, filed on April 24, 2024, are incorporated herein by reference in their entirety.

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

[0188] REFERENCE SIGNS LIST 100 AP 101 Scheduling unit 102 User Info generation unit 103 Common Info generation unit 104 Trigger frame generation unit 105, 206 Error correction coding unit 106, 207 Modulation unit 107, 201 Radio transmission / reception unit 108 OFDM demodulation unit 109 Tone demapping unit 110, 202 Demodulation unit 111, 203 Error correction decoding unit 200 Terminal 204 Common Info decoding unit 205 User Info decoding unit 208 Tone mapping unit 209 OFDM modulation unit

Claims

1. An access point comprising: a communication circuit for transmitting a control signal in which an information field contains an allocation of one or more resources for random access in which frequency resources are discretely allocated; and a control circuit for controlling reception of an uplink signal based on the allocation of one or more resources.

2. The access point according to claim 1, wherein the plurality of resources are resources having the same bandwidth in which the frequency resources are discretely allocated and the same number of the frequency resources allocated to the uplink signal, but having different starting positions for the frequency resources allocated to the uplink signal.

3. The access point according to claim 2, wherein the starting positions of each of the plurality of resources are non-contiguous in the frequency domain.

4. The access point according to claim 2, wherein the control signal includes information regarding the intervals of the start positions between the plurality of resources.

5. The access point according to claim 1, wherein in the allocation, allocation units including consecutive frequency resources are discretely arranged, and the control signal includes information regarding the number of frequency resources included in the allocation unit.

6. The access point according to claim 1, wherein the control signal is a Trigger frame, and an association ID is set in a User Info field of the Trigger frame, the association ID indicating that the resource indicated by the User Info field is the resource to which the allocation applies.

7. The access point according to claim 1, wherein the control signal is a trigger frame, and a trigger type that prompts transmission of the uplink signal to which the allocation is applied is set in the trigger frame.

8. A terminal comprising: a communication circuit for receiving a control signal in which an information field contains an allocation of one or more resources for random access to which an allocation in which frequency resources are discretely allocated is applied; and a control circuit for controlling transmission of an uplink signal based on the control signal.

9. A communication method in which an access point transmits a control signal in which one or more resource allocations for random access, in which frequency resources are discretely allocated, are included in one information field, and controls reception of uplink signals based on the one or more resource allocations.

10. A communication method in which a terminal receives a control signal in which an information field contains an allocation of one or more resources for random access to which an allocation in which frequency resources are discretely allocated is applied, and controls transmission of an uplink signal based on the control signal.

Images