Access point, terminal, and communication method

Abstract

This access point comprises: a transmission circuit that transmits a control signal including allocation information pertaining to a bandwidth of a first band, among communication bands, to which a first allocation is applied in which frequency resources allocated to an uplink signal are discretely arranged; and a control circuit that controls the reception of the uplink signal in the first band.

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 / 0303r0, TGbn January 2024 Meeting MinutesIEEE 802.11-23 / 1919r1, dRU Proposal

[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 transmitting circuit that transmits a control signal including allocation information regarding a first band of a communication band to which a first allocation is applied, in which frequency resources allocated to uplink signals are discretely arranged, and a control circuit that controls reception of the uplink signals in the first band.

[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 Resource Unit (RU) allocationDiagram showing an example of RU allocation in an 80MHz Physical layer Protocol Data Unit (PPDU)Block 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 terminalDiagram showing an example of a Distribute-tone RU (DRU)Block diagram showing an example of the configuration of an APBlock diagram showing an example of the configuration of a terminalDiagram showing an example of Orthogonal Frequency Division Multiplexing (OFDM) operation between a Regular RU (RRU) and a DRUDiagram showing an example of an RU allocation tableDiagram showing an example of distribution band settingDiagram showing an example of DRU allocationDiagram showing an example of distribution band settingDiagram showing an example of an RU indexDiagram showing an example of Multiple DRU

[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 Document 2).

[0013] 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") to instruct the transmission of uplink OFDMA signals to multiple terminals (STAs, also called "non-AP STAs") 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] In Figure 4, "Bandwidth (MHz)" indicates the transmission bandwidth (communication bandwidth) of the TB PPDU, "RU or MRU size" indicates the number of tones to which the terminal's uplink signals (Data (including Pilot), STF (Short Training Field), and LTF (Long Training Field) signals) are assigned, and "RU or MRU index" indicates the position of the RU or MRU in the TB PPDU band.

[0022] As an example, when the bandwidth of the TB PPDU is 80 MHz, the RU allocation may be defined as shown in Fig. 5. As shown in Fig. 5, the RU indexes are defined in order from the lowest frequency (the left side in Fig. 5) with the DC tone at the center, excluding the guard band and null subcarrier tones. For example, when the value of the RU allocation subfield is 19-36 as shown in Fig. 4, the RU size is 26 tones, and the RU indexes correspond to RU#20-RU#37 (any of the 26-tone RUs enclosed in a thick frame at the top of Fig. 5).

[0023] 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. DRU refers to an RU consisting of tones that are distributed (or dispersed or diffused) over a specific bandwidth.

[0024] For example, in existing standards prior to 11be, an RU (hereinafter also referred to as a "Regular RU (RRU)") consisting of multiple consecutive tones of the RU size, as shown in Figure 5, is allocated to each terminal as a TB PPDU resource.

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

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

[0027] Furthermore, in 11bn, the inclusion of a distribution bandwidth (Distribution BW) narrower than the TB PPDU bandwidth as a band for discretely allocating RUs in a DRU (hereinafter referred to as the "Distribution BW") is being considered (see, for example, Non-Patent Document 4). However, sufficient consideration has not been given to control signals for supporting DRUs with a distribution bandwidth narrower than the TB PPDU bandwidth. For example, there is room for consideration of RU allocation for DRUs that is easy to implement and requires little overhead.

[0028] In a non-limiting example of the present disclosure, an example of a method for controlling RU allocation for a DRU that is easy to implement and requires little overhead will be described.

[0029] [Configuration of Wireless Communication System] The wireless communication system according to this embodiment may include, for example, an AP 100 (for example, a wireless transmitting device) and a terminal 200 (for example, a wireless receiving device). In the wireless communication system, there may be, for example, two or more terminals 200.

[0030] For example, the AP 100 transmits a Trigger frame instructing the terminal 200 to transmit a TB PPDU, and the terminal 200 receives the Trigger frame. The terminal 200 transmits the TB PPDU to the AP 100 using the DRU frequency resource instructed by the Trigger frame.

[0031] Fig. 6 is a block diagram illustrating a configuration example of a portion of an AP 100 according to an embodiment of the present disclosure. In the AP 100 illustrated in Fig. 6, a communication unit (e.g., corresponding to a transmission circuit) transmits a control signal (e.g., a trigger frame) including allocation information regarding a first band (e.g., a distribution band) to which a first allocation (e.g., a DRU allocation) in which frequency resources (e.g., RUs) allocated to uplink signals are discretely allocated within a communication band (e.g., a TB PPDU band) is applied. A control unit (e.g., corresponding to a control circuit) controls reception of uplink signals in the first band.

[0032] 7 is a block diagram illustrating a configuration example of a portion of a terminal 200 according to an embodiment of the present disclosure. In the terminal 200 illustrated in FIG. 7 , a communication unit (e.g., corresponding to a receiving circuit) receives a control signal (e.g., a trigger frame) including allocation information regarding a first band (e.g., a distribution band) to which a first allocation (e.g., a DRU allocation) in which frequency resources (e.g., RUs) allocated to uplink signals are discretely allocated within a communication band (e.g., a TB PPDU band) is applied. A control unit (e.g., corresponding to a control circuit) controls transmission of uplink signals in the first band.

[0033] (Embodiment 1) In a DRU, for example, when the tone interval is 1 MHz (equivalent to approximately 13 tones) or more, the power boost gain does not change depending on the tone interval. For example, in a DRU, when the tone interval is 1 MHz (equivalent to approximately 13 tones) or more, the power boost gain is the same regardless of the tone interval.

[0034] For example, the upper diagram in Fig. 8 shows an example of a DRU with a distribution bandwidth of 80 MHz and an RU size of 26 Tone. Also, the lower diagram in Fig. 8 shows an example of a DRU with a distribution bandwidth of 40 MHz and an RU size of 26 Tone.

[0035] In the upper diagram of Figure 8, the tone spacing is 36, which means that 1 tone is allocated per 1 MHz (approximately 13 tones), thereby maximizing the power boost gain (for example, the transmit power for 26 tones is 13.15 dBm). In the lower diagram of Figure 8, the tone spacing is 18, which is narrower than the upper diagram, but since 1 tone is allocated per 1 MHz (approximately 13 tones), the power boost gain can be maximized, just like when the distribution bandwidth is 80 MHz (for example, the transmit power for 26 tones is 13.15 dBm).

[0036] In this way, in a DRU, the PSD per tone is determined by the tone interval. Therefore, for example, by defining the distribution band so that the tone interval is equal to or greater than a predetermined number, it is possible to suppress a decrease in power boost gain.

[0037] In the embodiment, the distribution bandwidth according to the RU size is defined while reusing the existing RU allocation notification for the RRU, thereby realizing the RU allocation notification for the DRU that is easy to implement and has low overhead.

[0038] [Configuration Example of AP 100] FIG. 9 is a block diagram showing a configuration example of the AP 100. As shown in FIG.

[0039] The AP 100 generates a Trigger frame that instructs the terminal 200 to transmit a TB PPDU (a response signal from the terminal 200 in response to the Trigger frame), and transmits the Trigger frame to the terminal 200 .

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

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

[0042] 9 , scheduling section 101 may perform scheduling for terminal 200, for example. For example, scheduling section 101 determines AIDs (Associated Identifications) of one or more terminals 200 that instruct TB PPDU transmission, and frequency resource information for transmitting TB PPDUs (terminal signals) for each terminal 200, and outputs the information to user information generating section 103 and common information generating section 104. Furthermore, scheduling section 101 holds scheduling information related to TB PPDUs from terminal 200, and outputs the information to tone demapping section 110, demodulation section 111, and error correction decoding section 112 for reception processing.

[0043] The frequency resource information of the terminal (e.g., RU allocation information) may include, for example, the RU type (e.g., information indicating either DRU or RRU), RU size, and RU position information. For example, if the RU type is DRU, the frequency resource information may include information on the Tone interval, Tone position (also referred to as the Tone offset or Tone start position), and Distribution band. Note that the frequency resource information of the terminal may be used as frequency resources for transmitting STF and LTF in addition to data from terminal 200.

[0044] For example, the RU type may be included in the User Info field. For example, one reserved bit in the User Info field in the existing standard may be used as a separate subfield to notify the RU type (DRU or RRU). Note that the RU type may also be included in the Common Info field (an example will be described later).

[0045] Note that RU type information does not need to be included in the frequency resource information. For example, RU type information may not be notified, and the RU type for terminals that support DRU (e.g., DRU capable STAs) may be controlled as DRU. Similarly, the RU type for terminals that do not support DRU (e.g., DRU non-capable STAs) may be controlled as RU.

[0046] The RU table setting unit 102 holds an RU allocation table (also called an RU table) in which, for example, frequency resource information for a DRU or an RRU is associated with bit information. In the case of DRU allocation (when the RU type is DRU), the RU table setting unit 102 holds an RU allocation table for a DRU in which at least the value of the RU allocation subfield is associated with the RU size, RU index, and Distribution band, and outputs the RU allocation table to the User Info generation unit 103.

[0047] For example, the RU allocation table for DRUs may be a table that reuses the RU allocation table for RRU allocation defined in 11be shown in Figure 4, with information about the Distribution band added. An example of the RU allocation table for DRUs will be described later. In addition, for RRU allocation, the RU allocation table shown in Figure 4 may be used.

[0048] Note that information about the distribution bandwidth does not have to be defined in the RU allocation table. For example, information about the distribution bandwidth may be included in the definition of the RU index for the DRU. For example, the start position of the tone allocation (or the distribution bandwidth), the tone interval (e.g., the interval between valid tones excluding guard and null tones), and the end position of the tone allocation may be defined as the RU index for the DRU. In this example, the difference between the start position and end position of the tone allocation corresponds to the distribution bandwidth.

[0049] The User Info generation unit 103 converts the control information, including the terminal ID and / or frequency resource information for the TB PPDU, input from the scheduling unit 101, into predetermined bit information using the RU allocation table input from the RU table setting unit 102. The User Info generation unit 103 then generates a User Info field and a Special User Info field including the converted bit information and outputs them to the Trigger frame generation unit 105.

[0050] The Common Info generation unit 104 converts the control information for the TB PPDU (e.g., the bandwidth of the TB PPDU, LTF symbol information, AP transmission power information, etc.) input from the scheduling unit 101 into predetermined bit information. For example, the Common Info generation unit 104 may include the RU type as terminal common information. For example, reserved bits in the Common Info field for 11be (EHT variant) may be used to notify the RU type. The Common Info generation unit 104 generates a Common Info field including the converted bit information and outputs it to the Trigger frame generation unit 105.

[0051] The trigger frame generation unit 105 generates a trigger frame including a Common Info field input from the Common Info generation unit 104, a Special User Info field input from the User Info generation unit 103, 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 105 outputs the generated trigger frame to the error correction coding unit 106.

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

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

[0054] 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 107) may map the modulated signal to a predetermined frequency resource, convert it into a time waveform by performing an Inverse Fast Fourier Transform (IFFT) process, and add a cyclic prefix (CP) to form an OFDM signal.

[0055] Radio transmitting / receiving section 108 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 107, and transmits the signal after radio transmission processing via an antenna to terminal 200. Radio transmitting / receiving section 108 also receives a signal transmitted from terminal 200 via the antenna, performs predetermined radio reception processing on the received signal 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 109.

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

[0057] Based on the frequency resource information for the DRU input from the scheduling unit 101, the tone demapping unit 110 acquires the received signal at a specified tone position from the received signal input from the OFDM demodulation unit 109 and outputs it to the demodulation unit 111.

[0058] The demodulation unit 111 performs corresponding demodulation processing on the received signal input from the tone demapping unit 110 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 112.

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

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

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

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

[0063] 10, 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 210, and transmits the signal after radio transmission processing from the antenna.

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

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

[0066] 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 206.

[0067] 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 206. 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 206.

[0068] The RU table setting unit 205 holds an RU allocation table that is identical to the RU allocation table of the RU table setting unit 102 of the AP 100 (for example, a table that associates frequency resource information for the DRU or RRU with bit information), and outputs the RU allocation table to the User Info decoding unit 206.

[0069] The User Info decoding unit 206 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. The User Info decoding unit 206 decodes terminal-specific information from the terminal common information input from the Common Info decoding unit 204, the User Info field, and the User Info field including the AID of the terminal 200 included in the Special User Info field.

[0070] For example, the User Info decoding unit 206 uses the RU allocation table input from the RU table setting unit 205 to acquire frequency resource information from frequency resource information (bit information) for the TB PPDU included in the terminal individual information.

[0071] The frequency resource information may include the RU type, RU size, RU index, etc. For example, if the RU type is DRU, the frequency resource information may include information on the Tone interval, Tone position, and Distribution band from the RU allocation table for DRU. Furthermore, the frequency resource information may be used as a frequency resource for transmitting STF and LTF in addition to data from terminal 200.

[0072] The User Info decoding unit 206 outputs the decoded terminal individual information (control information for TB PPDU transmission including frequency resource information) to the error correction coding unit 207 , the modulation unit 208 and the Tone mapping unit 209 .

[0073] The error correction coding unit 207 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 unit 206 , and outputs the signal to the modulation unit 208 .

[0074] The modulation unit 208 performs modulation processing on the signal coded in the error correction coding unit 207 using a predetermined modulation method based on the control information (modulation method, etc.) for TB PPDU transmission input from the User Info decoding unit 206, and outputs the processed signal to the Tone mapping unit 209.

[0075] The Tone mapping unit 209 places the modulated signal input from the modulation unit 208 at a predetermined Tone position based on the control information (such as frequency resource information) for TB PPDU transmission input from the User Info decoding unit 206, and outputs it to the OFDM modulation unit 210.

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

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

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

[0079] AP 100 uses a Trigger frame to notify terminal 200 of frequency resources for DRU and instructs terminal 200 to transmit a TB PPDU (uplink signal transmission) using DRU. Terminal 200 uses the received Trigger frame to identify frequency resources for DRU for terminal 200 and transmits a TB PPDU (uplink signal transmission) using DRU.

[0080] As described above, the AP 100 and the terminal 200 have RU table configuration units 102 and 205. The RU table configuration units 102 and 205 hold, for example, an RU allocation table for a DRU that associates frequency resource information for the DRU (for example, including information on the Distribution band) with bit information, in addition to an existing RU allocation table for an RRU (for example, the table shown in FIG. 4 ).

[0081] An example of an RU allocation table for a DRU will be described below.

[0082] In the RU allocation table for DRU, the value of the RU allocation subfield (i.e., the value of the RU allocation information) is associated with at least the RU size, RU index, and Distribution band.

[0083] As described above, in order to maintain the power boost gain, a distribution bandwidth narrower than the TB PPDU bandwidth may be defined so that the Tone interval is equal to or greater than a predetermined number according to the RU size. For example, an RU allocation table may be defined in which a distribution bandwidth narrower than the TB PPDU bandwidth is set for a DRU whose RU size is equal to or smaller than a threshold.

[0084] For example, if the TB PPDU bandwidth is 80 MHz, the distribution bandwidth of a DRU with an RU size of 26 tones (hereinafter also referred to as a "26-tone DRU") may be set (or limited) to 40 MHz, which is narrower than the TB PPDU bandwidth. On the other hand, the distribution bandwidth of a DRU with an RU size greater than 26 tones may be set to a bandwidth equal to the TB PPDU bandwidth (e.g., 80 MHz). In other words, the distribution bandwidth of a DRU with an RU size greater than 26 tones is not set to a bandwidth narrower than the TB PPDU bandwidth.

[0085] By using such an RU allocation table for DRU, terminal 200 can specify the RU size, RU index, and also the distribution bandwidth for DRU allocation, for example, based on the value of the RU allocation subfield. In this way, by reusing an existing RU notification method for DRU allocation, support for DRUs can be easily achieved. Furthermore, in this embodiment, by adding notification of the distribution bandwidth to the RU allocation table for DRUs, limited to a predetermined RU size (e.g., an RU size equal to or smaller than a threshold), it is possible to suppress an increase in the amount of signaling of frequency resources for DRUs compared to when the distribution bandwidth is notified independently.

[0086] Furthermore, by limiting the RU size to a threshold or less and defining a distribution bandwidth narrower than the TB PPDU bandwidth, flexible scheduling becomes possible while maintaining power boost gain for any RU size. Defining a distribution bandwidth narrower than the TB PPDU bandwidth enables OFDMA multiplexing of a terminal that does not support DRU (RRU) (e.g., a terminal that supports RRU) and a terminal that supports DRU within one TB PPDU bandwidth (e.g., 80 MHz), as shown in Fig. 11 , for example.

[0087] Furthermore, by defining a distribution bandwidth narrower than the TB PPDU bandwidth, it becomes possible to OFDMA multiplex terminals that are limited to using a narrow channel bandwidth (e.g., terminals that are limited to using a 20 MHz channel) within a TB PPDU that uses a wider channel bandwidth. Furthermore, even when a portion of a 20 MHz channel is preamble punctured (e.g., when the TB PPDU bandwidth is 80 MHz and a portion of the 20 MHz channel is punctured (no transmission)), it becomes possible to schedule terminals 200 that apply DRU to bands other than the punctured band.

[0088] An example of an RU allocation table for a DRU will be described below.

[0089] <First Example> In a first example, the distribution bandwidth in a DRU with an RU size equal to or smaller than a specified value (threshold value) is set to be narrower than the TB PPDU bandwidth.

[0090] For example, if the TB PPDU bandwidth is 80 MHz, the distribution bandwidth of a DRU with an RU size of 26 tones (26-tone DRU) is set (or limited) to 40 MHz. On the other hand, the distribution bandwidth of a DRU with an RU size greater than 26 tones is set to a bandwidth equal to the TB PPDU bandwidth (e.g., 80 MHz). In other words, the distribution bandwidth of a DRU with an RU size of 26 tones or less is set to be narrower than the TB PPDU bandwidth.

[0091] In this case, for example, as shown in FIG. 12, information on the distribution bandwidth may be associated with the 26-tone DRU table in the RU allocation table (for example, the "PPDU Bandwidth (MHz)" column corresponding to "RU / MRU size" = 26).

[0092] In the example of Fig. 12, for a 26-tone DRU in which a distribution bandwidth narrower than the TB PPDU bandwidth is defined, the position of the distribution bandwidth (40 MHz) in the 80 MHz TB PPDU bandwidth is associated with the RU allocation value (e.g., "B7-B1 of the RU Allocation subfield"). Here, the position of the distribution bandwidth in the TB PPDU bandwidth indicates, for example, either the first 40 MHz within the 80 MHz (40 MHz #1 in Fig. 12) or the last 40 MHz within the 80 MHz (40 MHz #2 in Fig. 12), as shown in Fig. 13.

[0093] In Fig. 12, in a 26-tone DRU, 26 tones are distributed over 40 MHz (484 tones) at intervals of 18 tones (the intervals counting the number of valid tones). For example, the 18 values ​​of 19-36 (19-27 and 28-36) in the RU allocation subfield in Fig. 12 correspond to a 40 MHz distribution band (Distribution BW = 40 MHz #2).

[0094] Here, the correspondence between the 18 values ​​of 19-36 (19-27 and 28-36) in the RU allocation subfield in Fig. 12 and the DRU allocation pattern may be set to a DRU allocation pattern in which the first tone position is changed (or shifted) by 1 tone, as shown in Fig. 14. For example, when the value of the RU Allocation subfield is 19, RUs are allocated at 18-tone intervals from the first tone of the 40 MHz #2 distribution band. Also, for example, when the value of the RU Allocation subfield is 20, RUs are allocated at 18-tone intervals from the first tone + 1 tone in the 40 MHz #2 distribution band. Thereafter, the value of the RU Allocation subfield is similarly associated with the DRU allocation pattern; for example, when the value of the RU Allocation subfield is 36, RUs are allocated at 18-tone intervals from the first tone + 17 tone in the 40 MHz #2 distribution band.

[0095] In this way, when defining a Distribution bandwidth narrower than the TB PPDU bandwidth, by including information about the location of the Distribution band in the RU allocation table, it is possible to reduce the frequency resources that cannot be allocated without increasing the overhead related to DRU notifications, thereby suppressing the deterioration of scheduling flexibility.

[0096] <Second Example> In a second example, the distribution band is set according to the RU size.

[0097] For example, the distribution band (e.g., bandwidth) may vary depending on the RU size of the DRU. Also, for example, the interval between adjacent tones (frequency resources) in the distribution band may be the same (or approximately the same) regardless of the RU size.

[0098] For example, as shown in Figure 15, when the TB PPDU bandwidth is 80 MHz, the distribution bandwidth of a 26-tone DRU may be set to 20 MHz, and the distribution bandwidth of a 52-tone DRU may be set to 40 MHz. Also, the distribution bandwidth of a DRU larger than 52 tones may be set to 80 MHz (e.g., the same bandwidth as the TB PPDU bandwidth). In other words, different distribution bandwidths are set for DRU RU sizes of 26 tones, 52 tones, and 106 tones or more.

[0099] For example, by setting the distribution bandwidth of a 26-tone DRU to 20 MHz, the tone interval becomes 9. Also, by setting the distribution bandwidth of a 52-tone DRU to 40 MHz, the tone interval becomes 9, just like the 26-tone DRU. In this way, the tone interval is 9 for both the 26-tone DRU and the 52-tone DRU RU sizes, so the power boost gain is the same.

[0100] As shown in Fig. 16, four distribution bands for the 26-tone DRU are defined within 80 MHz, and information on each distribution band (information indicating any of 20 MHz #1 to 20 MHz #4 in Fig. 16) is associated with a value in the RU Allocation subfield in the RU allocation table shown in Fig. 15. Similarly, as shown in Fig. 16, two distribution bands for the 52-tone DRU are defined within 80 MHz, and information on each distribution band (information indicating any of 40 MHz #1 to 40 MHz #2 in Fig. 16) is associated with a value in the RU Allocation subfield in the RU allocation table shown in Fig. 15.

[0101] In this way, by setting the distribution band according to the RU size so that the tone interval is equal to or greater than the specified value, the power boost gain can be maintained regardless of the RU size.

[0102] Furthermore, for example, by setting the Distribution bandwidth to 20 MHz in a TB PPDU bandwidth of 80 MHz, it becomes possible to flexibly apply OFDMA multiplexing using DRU even in cases where there is a preamble puncture that causes a non-transmission interval in 20 MHz channel units, or where there is a terminal that operates only on 20 MHz channels.

[0103] <Third Example> In a third example, information about the Distribution bandwidth is included in the RU index for the DRU (DRU index).

[0104] For example, information about the distribution band (allocation information) may be included in the definition of the RU index for the DRU (DRU index). For example, the distribution band may not be defined (or specified) in the RU allocation table, and instead a DRU index (e.g., information about the position of the distribution band) consisting of three elements: [tone start position: tone interval: tone end position] may be defined, as shown in FIG.

[0105] The distribution bandwidth may be implicitly indicated by the DRU index (e.g., the difference between the start and end positions of the tone arrangement). Note that the tone interval counts the number of valid tones excluding guard tones and null tones. Tones are also sometimes called subcarriers.

[0106] In the definition of the RU index of the RRU and DRU shown in Figure 17, for example, the DC position is set to Tone number 0, and subcarriers with frequencies lower than DC are assigned negative numbers, and subcarriers with frequencies higher than DC are assigned positive numbers. The distribution bandwidth corresponds to "end tone position - start tone position + tone interval" in the definition for the DRU.

[0107] In this way, by defining an RU index for the DRU and entering an RU index associated with the RU allocation value in the RU allocation table shown in Figures 12 and 15, the Distribution bandwidth of the DRU (including a bandwidth smaller than the TB PPDU bandwidth) can be implicitly notified.

[0108] Note that the DRU index is not limited to being composed of three elements: the Tone start position (or the start position of the Distribution band), the Tone interval (the interval between adjacent Tones), and the Tone end position (or the end position of the Distribution band). For example, if the bandwidth of the Distribution band is notified separately or is specified in advance, the DRU index may be composed of either the Tone start position or the Tone end position and the Tone interval. Terminal 200 can identify the allocation of DRUs based on, for example, the DRU index and the bandwidth of the Distribution band.

[0109] An example of the RU allocation table for the DRU has been described above.

[0110] Thus, in this embodiment, AP 100 and terminal 200 transmit and receive a Trigger frame including allocation information regarding a Distribution band (e.g., bandwidth) that applies DRU allocation in which RUs (e.g., Tones) allocated to uplink signals are discretely arranged within the TB PPDU band, and control the transmission and reception of uplink signals in the Distribution band.

[0111] As a result, even if a bandwidth narrower than the TB PPDU bandwidth is set as the Distribution bandwidth for DRU allocation, AP 100 can appropriately notify terminal 200 of information related to the Distribution bandwidth (for example, RU allocation). Thus, according to this embodiment, it is possible to improve the efficiency of transmission control in wireless communication.

[0112] (Embodiment 2) In this embodiment, a method of setting the Distribution band for one terminal to be non-contiguous within the TB PPDU band (also called "Multiple DRU", for example) will be described.

[0113] [Configuration Example of AP 100] The configuration of AP 100 according to this embodiment may be the same as that of AP 100 according to Embodiment 1 (for example, FIG. 9). In AP 100 according to this embodiment, the operation of Common Info generation unit 104 differs from that of Embodiment 1.

[0114] In this embodiment, Common Info generating section 104 includes information on frequency resources not to be allocated to terminal 200 (for example, subchannel information (information in 20 MHz channel units)) in information on frequency resources to be allocated to terminal 200 for TB PPDU. Hereinafter, this subchannel information is also referred to as "non-allocated subchannel information."

[0115] For example, the non-allocated subchannel information may use information from the Punctured Channel Information field (5 bits) included in the U-SIG of the 11be preamble. The Punctured Channel Information field reports information on subchannels to which preamble puncturing has been applied (information indicating a 20 MHz channel to which puncturing has been applied in the PPDU band). In 11be, subchannel information is included in the EHT MU PPDU but not in the TB PPDU. Common Info generation section 104 may include similar information in the Common Info field and report this as non-allocated subchannel information to which terminal 200's signal is not allocated in the TB PPDU.

[0116] The non-allocated subchannel information may be notified using, for example, reserved bits in the common info field or the trigger dependent common info subfield in an existing standard, or may be notified as terminal common information using reserved bits in the special user info field or the trigger dependent user info subfield in an existing standard.

[0117] As described above, when the Trigger Dependent Common Info subfield or the Trigger Dependent User Info subfield is used, a type (Trigger type) that prompts TB PPDU transmission by DRU allocation may be newly added as the Trigger type. When this Trigger type is indicated, the Common Info generation unit 104 may include non-allocated subchannel information in the Trigger Dependent Common Info subfield or the Trigger Dependent User Info subfield.

[0118] As an example, when puncturing a portion of a 20 MHz channel in an 80 MHz channel, the bit information including the DRU frequency resource information generated by the User Info generation unit 103 notifies an allocation in which the distribution band matches the TB PPDU band (e.g., 80 MHz). For example, any 106-tone DRU allocation pattern (e.g., a pattern in which 80 MHz (996 tones) are allocated at 9-tone intervals) may be notified. Then, the AP 100 notifies a multiple DRU allocation (non-contiguous distribution bands) in combination with the above-mentioned non-allocation subchannel information. In this case, the frequency resources allocated to uplink signals in the distribution band are the resources obtained by excluding the band notified by the non-allocation subchannel information from the TB PPDU band (80 MHz) notified by the frequency resource information.

[0119] [Configuration Example of Terminal 200] The configuration of terminal 200 according to this embodiment may be the same as that of terminal 200 according to Embodiment 1 (for example, FIG. 10 ). In terminal 200 according to this embodiment, the operations of Common Info decoding section 204 and User Info decoding section 206 differ from those in Embodiment 1.

[0120] In this embodiment, Common Info decoding section 204 obtains unallocated subchannel information from the signal after error correction decoding, and outputs the information to User Info decoding section 206 .

[0121] The User Info decoder 206 acquires frequency resource information (bit information) for the TB PPDU intended for the terminal 200 from the error correction decoded signal, and acquires the frequency resource information based on the RU allocation table input from the RU table setting unit 205 and the non-allocated subchannel information input from the Common Info decoder 204. Note that if non-allocated subchannel information is included in the Special User Info field, the User Info decoder 206 acquires the non-allocated subchannel information from the error correction decoded signal.

[0122] The User Info decoding unit 206 acquires DRU frequency resource information for which one Distribution band is set in the TB PPDU band from the frequency resource information (bit information) and the RU allocation table, as in embodiment 1. The User Info decoding unit 206 combines the acquired DRU frequency resource information with unallocated subchannel information to acquire Multiple DRU allocation.

[0123] For example, in the DRU frequency resource information, the 20 MHz channel band indicated by the non-allocation subchannel information is unallocated (masked). For example, as shown in Figure 18, if a 106-tone DRU placement pattern is reported as DRU frequency resource information and the third 20 MHz channel within 80 MHz is reported as unallocated as non-allocation subchannel information, terminal 200 allocates signals by the DRU to the first 40 MHz band and the last 20 MHz band of the 80 MHz channel. In other words, the frequency resources allocated to uplink signals in the TB PPDU band (80 MHz in Figure 18) are the 106 tones reported by the DRU frequency resource information minus the third 20 MHz channel within 80 MHz reported by the non-allocation subchannel information.

[0124] This enables non-contiguous DRU allocation using the distribution band even when preamble puncture is applied. Also, by making non-allocation information common to all terminals, the increase in overhead can be suppressed.

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

[0126] When transmitting an NDP (null data packet) for uplink reception quality (Sounding) from the DRU, frequency hopping may be performed between distribution bands. For example, the distribution band may be different for each NDP transmission timing. For example, frequency hopping may be performed for each LTF symbol for the SS (Spatial Stream) as follows: Distribution band 20MHz#1 ⇒ 20MHz#3 ⇒ 20MHz#2 ⇒ 20MHz#4

[0127] Furthermore, the RU type (information indicating either a DRU or an RRU) is not limited to being notified for each terminal by terminal-specific information (e.g., a User Info field). For example, the RU type may be notified by terminal common information (a Common Info field or a Special User Info field). For example, a terminal that supports a DRU determines whether the RU allocation is for a DRU or an RRU based on the above notification. On the other hand, a terminal that does not support a DRU may recognize the RU allocation as for an RRU without relying on the above notification (e.g., ignoring the notification).

[0128] In addition, the RU type (information indicating either a DRU or an RRU) may be notified by being included in terminal common information (Common Info field, Special User Info field) or terminal individual information (User Info field) as information (e.g., a bitmap in which each bit corresponds to each subchannel) notified for each subband or subblock (e.g., an 80 MHz frequency subblock).

[0129] 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 an RU allocation notification of a PPDU (such as a UHR MU PPDU) that is not a response to a trigger frame.

[0130] 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).

[0131] In each of the above embodiments, the trigger frame that notifies the distribution bandwidth may be a basic trigger frame or another trigger frame. In each of the above embodiments, the control signal that notifies the distribution bandwidth is not limited to a trigger frame, and may be, for example, a MAC header (for example, defining a new field) or a preamble.

[0132] In addition, in each of the above-described embodiments, the field (or subfield) used for notifying control information (for example, information on the Distribution band) 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.

[0133] Furthermore, in each of the above-mentioned embodiments, the values ​​of parameters such as the TB PPDU bandwidth, Distribution bandwidth, RU size, threshold for RU size, RU index, Tone interval in DRU, and Tone (or subcarrier) size are examples and may be other values.

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

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

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

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

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

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

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

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

[0142] A communications device 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 device.

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

[0144] An access point according to one embodiment of the present disclosure includes a transmitting circuit that transmits a control signal including allocation information regarding a first band that applies a first allocation in which frequency resources allocated to uplink signals are discretely arranged within a communication band, and a control circuit that controls reception of the uplink signals in the first band.

[0145] In an embodiment of the present disclosure, the value of the allocation information is associated with the first band, the size of the frequency resource allocated to the uplink signal, and the position of the frequency resource allocated to the uplink signal.

[0146] In one embodiment of the present disclosure, when the size of the frequency resource is equal to or smaller than a threshold, the bandwidth of the first band is narrower than the communication band.

[0147] In one embodiment of the present disclosure, the value of the allocation information is associated with the position of the first band in the communication band.

[0148] In one embodiment of the present disclosure, the bandwidth of the first band varies depending on the size of the frequency resource.

[0149] In one embodiment of the present disclosure, the interval between adjacent frequency resources in the first band is the same regardless of the size of the frequency resources.

[0150] In one embodiment of the present disclosure, the allocation information includes information regarding the location of the frequency resource, and the information regarding the location is composed of a starting position of the first band in the communication band, a spacing between adjacent frequency resources, and an ending position of the first band.

[0151] In one embodiment of the present disclosure, the frequency resources allocated to the uplink signal in the first band are the frequency resources notified by the allocation information minus the frequency resources notified by the non-allocation information.

[0152] In one embodiment of the present disclosure, the control signal is a Trigger frame.

[0153] In one embodiment of the present disclosure, the Trigger frame is a Basic Trigger frame.

[0154] In an embodiment of the present disclosure, the trigger frame is a trigger frame of a type that prompts transmission of the uplink signal according to the first allocation.

[0155] In one embodiment of the present disclosure, the control signal includes information indicating either the first allocation or a second allocation in which the frequency resources allocated to the uplink signal are arranged contiguously.

[0156] In an embodiment of the present disclosure, information indicating either the first allocation or the second allocation is notified for each terminal.

[0157] In an embodiment of the present disclosure, information indicating either the first allocation or the second allocation is notified for each subband.

[0158] In one embodiment of the present disclosure, the information indicating either the first allocation or the second allocation is a bitmap indicating whether the frequency resources in the first subband are the first allocation or the second allocation using bits corresponding to the first subband.

[0159] In one embodiment of the present disclosure, the sub-band is an 80 MHz frequency sub-block.

[0160] In an embodiment of the present disclosure, information indicating either the first allocation or the second allocation is included in terminal common information.

[0161] A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives a control signal including allocation information regarding a first band that applies a first allocation in which frequency resources allocated to an uplink signal are discretely arranged within a communication band, and a control circuit that controls transmission of the uplink signal based on the control signal.

[0162] In a communication method according to one embodiment of the present disclosure, an access point transmits a control signal including allocation information regarding a first band of a communication band to which a first allocation is applied, in which frequency resources allocated to an uplink signal are discretely arranged, and controls reception of the uplink signal based on the control signal.

[0163] In a communication method according to one embodiment of the present disclosure, a terminal receives a control signal including allocation information regarding a first band of a communication band to which a first allocation is applied, in which frequency resources allocated to an uplink signal are discretely arranged, and controls transmission of the uplink signal based on the control signal.

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

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

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

Claims

1. An access point comprising: a transmitting circuit that transmits a control signal including allocation information regarding a first band that applies a first allocation in which frequency resources allocated to uplink signals are discretely arranged within a communication band; and a control circuit that controls reception of the uplink signals in the first band.

2. The access point according to claim 1, wherein the value of the allocation information is associated with the first band, the size of the frequency resource allocated to the uplink signal, and the position of the frequency resource allocated to the uplink signal.

3. The access point according to claim 2, wherein when the size of the frequency resource is equal to or smaller than a threshold, the bandwidth of the first band is narrower than the communication band.

4. The access point according to claim 2, wherein the value of the allocation information is associated with the position of the first band in the communication band.

5. The access point according to claim 1, wherein the bandwidth of the first band varies depending on the size of the frequency resource.

6. The access point according to claim 5, wherein the interval between adjacent frequency resources in the first band is the same regardless of the size of the frequency resources.

7. The access point according to claim 1, wherein the allocation information includes information relating to the location of the frequency resources, and the information relating to the location is configured by the starting position of the first band in the communication band, the interval between adjacent frequency resources, and the ending position of the first band.

8. The access point according to claim 1, wherein the frequency resources allocated to the uplink signal in the first band are the frequency resources notified by the allocation information minus the frequency resources notified by the non-allocation information.

9. The access point according to claim 1, wherein the control signal is a Trigger frame.

10. The access point according to claim 9, wherein the trigger frame is a basic trigger frame.

11. The access point according to claim 9, wherein the trigger frame is a trigger frame of a type that prompts transmission of the uplink signal according to the first allocation.

12. The access point according to claim 1, wherein the control signal includes information indicating either the first allocation or a second allocation in which the frequency resources allocated to the uplink signal are arranged contiguously.

13. The access point according to claim 12, wherein information indicating either the first allocation or the second allocation is notified to each terminal.

14. The access point according to claim 12, wherein information indicating either the first allocation or the second allocation is notified for each subband.

15. The access point according to claim 14, wherein the information indicating either the first allocation or the second allocation is a bitmap indicating whether a frequency resource in a first subband is the first allocation or the second allocation by using a bit corresponding to the first subband.

16. The access point of claim 14, wherein the sub-band is an 80 MHz frequency sub-block.

17. The access point according to claim 12, wherein information indicating either the first allocation or the second allocation is included in terminal common information.

18. A terminal comprising: a receiving circuit that receives a control signal including allocation information regarding a first band that applies a first allocation in which frequency resources allocated to uplink signals are discretely arranged within a communication band; and a control circuit that controls transmission of the uplink signals based on the control signal.

19. A communication method in which an access point transmits a control signal including allocation information regarding a first band to which a first allocation is applied, in which frequency resources allocated to uplink signals are discretely arranged within a communication band, and controls reception of the uplink signals based on the control signal.

20. A communication method in which a terminal receives a control signal including allocation information regarding a first band that applies a first allocation in which frequency resources allocated to uplink signals are discretely arranged within a communication band, and controls transmission of the uplink signals based on the control signal.

Images