Access point, terminal and communication method
By employing the DRU allocation method for Tone groups in wireless communication systems, the problem of low efficiency in transmitting uplink signals by terminals is solved, achieving more efficient communication and better channel estimation accuracy, and improving uplink throughput.
Patent Information
- Application Number
- CN202580026417.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-12
- Filing Date
- 2025-03-17
- Publication Date
- 2026-11-10
AI Technical Summary
In wireless communication, existing technologies have not fully explored methods for terminals to send uplink signals based on control signals received from access points, resulting in low communication efficiency.
The DRU allocation method based on Tone groups is adopted. By discretely configuring frequency resources in the wireless communication system, the interval of Tone groups is used to control and receive uplink signals, ensuring power enhancement gain and channel estimation accuracy.
It improves the transmission control efficiency of wireless communication, enhances power boost gain and channel estimation accuracy, and increases uplink throughput.
Smart Images

Figure CN123077239A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to access points, terminals, and communication methods. Background Technology
[0002] As a successor to the IEEE 802.11 standard IEEE 802.11be (hereinafter referred to as "11be"), the Study Group (SG) is advancing the technical specifications of IEEE 802.11bn (hereinafter referred to as "11bn"). 11be is also known as "Extremely High Throughput (EHT)". Furthermore, 11bn is also known as "Ultra High Reliability (UHR)".
[0003] Existing technical documents
[0004] Non-patent literature
[0005] Non-patent literature 1: IEEE P802.11be / D5.0
[0006] Non-patent document 2: IEEE 802.11-23 / 0079r10, IEEE 802.11 UHR Proposed CSD
[0007] Non-patent document 3: IEEE 802.11-24 / 0303r0, TGbn January 2024 Meeting Minutes
[0008] Non-patent document 4: IEEE 802.11-23 / 1117r0, dRU Signaling for UHR
[0009] Non-patent literature 5: IEEE 802.11-23 / 1511r1, Pilot Tone Allocation and Other Considerations of Tone-Distributed RUs for UHR
[0010] Non-patent document 6: IEEE 802.11-23 / 2021r1, Principle and Methodology for dRUTone Plan Design Summary of the Invention
[0011] However, in wireless communications such as wireless LANs, the method for terminals to send uplink signals based on instructions from control signals received from access points (APs) has not been sufficiently studied.
[0012] The non-limiting embodiments of this disclosure help to provide access points, terminals, and communication methods that can improve the efficiency of transmission control in wireless communication.
[0013] A terminal according to an embodiment of this disclosure includes: a transmitting circuit that transmits a control signal, the control signal including allocation information for allocating an uplink signal based on a resource allocation in which allocation includes allocation units of one or more frequency resources configured discretely at intervals set according to the number of frequency resources included in the allocation unit; and a control circuit that controls the reception of the uplink signal based on the allocation information.
[0014] It should be noted that these general or specific methods can be implemented by systems, devices, methods, integrated circuits, computer programs or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs and recording media.
[0015] According to one embodiment of this disclosure, for example, the efficiency of transmission control in wireless communication can be improved.
[0016] Further advantages and effects of one embodiment of this disclosure will be illustrated by the specification and drawings. These advantages and / or effects are provided by the various embodiments and the features described in the specification and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. Attached Figure Description
[0017] Figure 1 This is a diagram showing an example of the format of a trigger frame.
[0018] Figure 2 This is a diagram showing an example of the format of a User Info field.
[0019] Figure 3 This is a diagram showing an example of the format of the Special User Info field.
[0020] Figure 4 This is a diagram illustrating an example of resource unit (RU) allocation.
[0021] Figure 5This is a diagram illustrating an example of the RU configuration in a 20 MHz Physical Layer Protocol Data Unit (PPDU).
[0022] Figure 6 This is a diagram illustrating an example of a tone plan for a distributed-tone RU (DRU).
[0023] Figure 7 This is a block diagram showing a structural example of an Access Point (AP).
[0024] Figure 8 This is a block diagram showing a structural example of a portion of a terminal.
[0025] Figure 9 This is a block diagram illustrating an example of the structure of an AP.
[0026] Figure 10 This is a block diagram showing an example of the terminal's structure.
[0027] Figure 11 This is a diagram showing an example of the RU index used by DRU.
[0028] Figure 12 This is a diagram illustrating an example of a RU index.
[0029] Figure 13 This is a diagram showing an example of the RU index used by DRU.
[0030] Figure 14 This is a diagram showing an example of the RU index used by DRU.
[0031] Figure 15 This is a diagram showing an example of the RU index used by DRU.
[0032] Figure 16 This is a diagram showing an example of the RU index used by DRU.
[0033] Figure 17 This is a diagram showing an example of a notification of RU type.
[0034] Figure 18 This is a diagram illustrating an example of a trigger-based (TB) PPDU.
[0035] Figure 19 This is a diagram illustrating an example of Tone planning.
[0036] Figure 20 This is a diagram showing an example of a TB PPDU.
[0037] Figure 21 This is a diagram showing an example of a TB PPDU. Detailed Implementation
[0038] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
[0039] As mentioned above, IEEE is studying 11bn as a successor standard to 11be (see, for example, non-patent literature 2).
[0040] 11be supports uplink OFDMA (Orthogonal Frequency-Division Multiple Access). The access point (AP, or also called a "base station") sends control signals (e.g., called "trigger frames") to the multiple terminals (STAs, or also called "non-AP STAs") housed by the AP, instructing them to send uplink OFDMA signals.
[0041] In 11bn, it is also possible to use the trigger frame of 11be as a control signal to instruct multiple terminals to send uplink OFDMA signals.
[0042] Furthermore, the control signal can send instructions to more than one terminal. Additionally, more than one terminal can send a response signal based on the control signal.
[0043] For example, such as Figure 1 As shown, in addition to the MAC header, the trigger frame also includes a "Common Info field" and a "User Info List" (see, for example, Non-Patent Document 1). The Common Info field contains information common to multiple terminals multiplexed via OFDMA. The User Info List includes a "Special User Info field" and multiple User Info fields.
[0044] Figure 2 This shows an example of the format for a user information field. Figure 3 This shows an example of the format for a special user information field.
[0045] Figure 3The special user information field shown contains general information for terminals supporting 11be and later standards. For example, the special user information field may contain general information for 11bn terminals. The special user information field is a field that sets a special AID (Association ID, e.g., AID = 2007) for the user information field. It is expected that the special user information field will inform terminals supporting 11bn (or UHR) (e.g., also referred to as "UHR terminals") of information common to both, such as uplink bandwidth-related information for terminals supporting 11be (or EHT) (e.g., also referred to as "EHT terminals").
[0046] also, Figure 2 The user information fields shown contain information specific to each terminal. For example, Figure 2 The “RU Allocation” subfield of the user information field, as shown, uses information from the “UL BW” subfield of the public information field, the “UL BW Extension” subfield of the special user information field, and the “PS 160” subfield of the user information field to inform the terminal of the resource information of the uplink signal sent in response to the trigger frame from the AP. Additionally, the uplink signal is also referred to as a TB PPDU (Trigger-Based (TB) Physical layer Protocol Data Unit). Furthermore, the resource information of the uplink signal may include information related to the bandwidth of the TB PPDU, the size and location of the RU (Resource Unit; frequency resource allocation unit), and the MRU (Multiple RU).
[0047] For example, the UL BW subfield and UL BW extended subfield indicate the bandwidth of the TB PPDU that the terminal can use (e.g., one of 20, 40, 80, 160, or 320 MHz). Furthermore, the terminal is, for example, based on... Figure 4 The table shown identifies (or determines, confirms) the location and size of the RU that allocates the uplink transmission signal in the transmission band (communication band) of the TB PPDU based on the value obtained by combining the RU allocation subfield and the PS 160 subfield (for example, see Non-Patent Document 1).
[0048] exist Figure 4In this context, "bandwidth (MHz)" indicates the transmit frequency band (communication band) of the TB PPDU, and "RU or MRU size" indicates the tone number (frequency modulation number) of the uplink signal (data including pilot, STF (Short Training Field), and LTF (Long Training Field) signals) of the configured terminal. Furthermore, "RU or MRU index" indicates the position of the RU or MRU within the TB PPDU frequency band.
[0049] As an example, with a TB PPDU bandwidth of 20 MHz, it can be defined as follows: Figure 5 The RU configuration shown. (As shown in the image) Figure 5 As shown, with DC tone as the center, excluding the guard band and null subcarrier, the tone starts from a lower frequency (in... Figure 5 The RU indexes are defined sequentially from left to right. For example, the value of the subfield assigned to the RU index is... Figure 4 In the case of values from 0 to 8 shown, the RU size is 26 tones, and the RU indices correspond to RU#1 to RU#9 respectively. Figure 5 One of the 26-tone RUs on the top layer).
[0050] In 11bn, "Distributed-tone RU" (hereinafter referred to as "DRU") is introduced into the resource allocation of TB PPDU sent by the terminal in response to the trigger frame. DRU refers to an RU consisting of tones that are discretely (or dispersedly, diffusely) deployed in a specific bandwidth.
[0051] For example, in existing standards prior to 11be, such as Figure 5 As shown, an RU (hereinafter also referred to as a regular RU (RRU)) consisting of multiple consecutively arranged Tones whose number is the same as the Tone number represented by the RU size is allocated to each terminal as a TBPPDU resource.
[0052] On the other hand, within the 6 GHz band supported by 11bn, there are regulations limiting the transmit power spectral density (PSD) to a specified value (e.g., -1 dBm / MHz) for terminals in the LPI (Low Power Indoor) band (e.g., non-AP STA). In 11bn, for example, approximately 13 tones are equivalent to 1 MHz; therefore, according to the aforementioned regulations, the PSD per tone may be limited if an RRU is used.
[0053] Therefore, by applying DRUs to distribute the Tones allocated to each terminal and reduce the number of Tones per 1 MHz, the PSD of each Tone can be improved. This power boost gain from DRUs can also increase uplink throughput.
[0054] In 11bn, a "Tone Plan" is being studied that defines the configuration pattern of the Tone of the DRU (e.g., see Non-Patent Document 4). In Non-Patent Document 4, for example, as... Figure 6 As shown, the study is investigating RU allocation using existing RRUs and supporting DRUs corresponding to existing RU sizes (e.g., 26-tone, 52-tone, 106-tone, etc.). Here, the tone near the DC and the guard can be set to a null tone (no terminal signal assigned) similar to existing standards (e.g., standards prior to 11be). Additionally, tone is also referred to as a "subcarrier".
[0055] The valid tones, excluding null tones, are sequentially assigned to each terminal. For example, in the case of a 26-tone DRU (hereinafter referred to as "26-tone DRU") with a 20MHz channel in the TB PPDU band, tones are assigned to each terminal at 9-tone intervals. By making the starting tone position of the DRU different among the terminals, OFDMA multiplexing can be performed in the TB PPDU band. For example, by... Figure 6 The 26 DRU_1, 26 DRU_2, 52 DRU_2 or 106 DRU_2 shown are assigned to different terminals and can be used for OFDMA multiplexing.
[0056] Furthermore, in the DRU research of 11bn, a type of tone grouping is being studied, which groups a specified number of consecutive tones into a group (e.g., applying "tone grouping") and distributes them according to each group of tones after tone grouping (e.g., see non-patent documents 5, 6). Hereinafter, the tones after tone grouping (e.g., the allocation units) will also be referred to as "tone groups", and the number of tones contained in a tone group will also be referred to as "grouping tone number". In addition, the DRU that applies tone grouping will also be referred to as "tone group based DRU".
[0057] Tone grouping offers several advantages: it improves channel estimation accuracy at the receiver by smoothing multiple tones and enhances the performance of demodulation processes such as frequency offset correction. However, the increased number of tones per 1 MHz due to the sequential configuration of multiple tones may reduce power gain.
[0058] The introduction of tone grouping into the DRUs of IEEE 802.11bn is under investigation, but tone planning with tone grouping has not been fully discussed. For example, there is still room for research into RU allocation with tone grouping that is easy to install and has low overhead.
[0059] In a non-limiting embodiment of this disclosure, an example of a control method for RU allocation that applies tone grouping, which is easy to install and has low overhead, is described.
[0060] [Structure of a wireless communication system]
[0061] The wireless communication system of this embodiment may include, for example, an AP 100 (e.g., a wireless transmitting device) and a terminal 200 (e.g., a wireless receiving device). In the wireless communication system, for example, there may be two or more terminals 200.
[0062] For example, AP 100 sends a trigger frame to terminal 200 instructing it to send a TB PPDU, and terminal 200 receives the trigger frame. Terminal 200 uses the DRU frequency resources indicated by the trigger frame to send a TB PPDU to AP 100.
[0063] Figure 7 This is a block diagram illustrating a structural example of a portion of an AP 100 according to an embodiment of this disclosure. Figure 7 In the AP 100 shown, the communication unit (e.g., corresponding to the transmitting circuit) transmits a control signal (e.g., a trigger frame) containing allocation information for uplink signals based on resource allocation (e.g., DRU allocation based on tone groups). In this resource allocation, allocation units (e.g., tone groups) comprising one or more frequency resources (e.g., tone or subcarriers) are discretely configured at intervals (tone intervals) set according to the number of frequency resources (e.g., grouping tone number) within the allocation unit. The control unit (e.g., corresponding to the control circuit) controls the reception of uplink signals based on the allocation information.
[0064] Figure 8This is a block diagram illustrating a structural example of a portion of a terminal 200 according to an embodiment of the present disclosure. Figure 8 In the terminal 200 shown, the communication unit (e.g., corresponding to the receiving circuit) receives a control signal (e.g., a trigger frame) containing allocation information for allocating uplink signals based on resource allocation (e.g., DRU allocation based on tone groups). In this resource allocation, allocation units (e.g., tone groups) comprising one or more frequency resources (e.g., tone or subcarriers) are discretely configured at intervals (tone intervals) set according to the number of frequency resources (e.g., grouping tone number) within the allocation unit. The control unit (e.g., corresponding to the control circuit) controls the transmission of the uplink signals based on the allocation information.
[0065] (Implementation Method 1)
[0066] In this embodiment, in the allocation of DRUs of the same size within a specified TB PPDU bandwidth (e.g., a 20 MHz channel), the more Grouping Tones there are, the wider the Tone interval between Tone groups is set. For example, in this embodiment, in DRUs that apply Tone grouping (e.g., Tone group-based DRUs), the Tone interval of the Tone group is set according to the number of Tones in the Tone group.
[0067] This allows existing RU allocation subfields to be reused in DRUs that apply tone grouping (e.g., tone-group-based DRUs), with examples provided later.
[0068] Additionally, the Grouping Tone number refers to the number of Tones contained in a discretely configured (or distributed) Tone group (assignment unit) in Tone grouping (or a DRU based on Tone grouping) (e.g., the number of one or more consecutive Tones).
[0069] Furthermore, by increasing the number of Grouping Tones and widening the Tone intervals between Tone groups, the number of RU indices (e.g., equivalent to OFDMA multiplexing numbers) in the TB PPDU band can be set to be the same (or approximately the same) regardless of the number of Grouping Tones. Therefore, even in Tone-based DRUs, the values of the RU allocation subfield of the RRU, the RU size, and the relationships between the RU indices can be reused (e.g., existing RU allocation tables).
[0070] Furthermore, by increasing the Tone spacing between Tone groups, the number of Tones allocated per 1 MHz (e.g., about 13 Tones) can be reduced, thus ensuring power boost gain in the Tone group-based DRU.
[0071] [Structure example of AP 100]
[0072] Figure 9 This is a block diagram showing an example of the structure of AP 100.
[0073] AP 100 generates a trigger frame that instructs terminal 200 to send a TB PPDU (terminal 200's response signal to the trigger frame) and sends the trigger frame to terminal 200.
[0074] Figure 9 The AP 100 shown may include, for example, a scheduling unit 101, an RU table setting unit 102, a user information generation unit 103, a common information generation unit 104, a trigger frame generation unit 105, an error correction coding unit 106, a modulation unit 107, a wireless transceiver unit 108, an OFDM demodulation unit 109, a tone demapping unit 110, a demodulation unit 111, and an error correction decoding unit 112.
[0075] in addition, Figure 9 At least one of the following units may be included: scheduling unit 101, RU table setting unit 102, user information generation unit 103, common information 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. Figure 7 In the control unit shown, Figure 9 The wireless transceiver unit 108 shown may be included in Figure 7 shown in the Communications Department.
[0076] exist Figure 9 In this process, the scheduling unit 101 can, for example, schedule the terminals 200. For instance, the scheduling unit 101 determines the AID (Association ID) of one or more terminals 200 instructed to transmit TB PPDUs and the frequency resource information for transmitting TB PPDUs (terminal signals) for each terminal 200, and outputs this information to the user information generation unit 103 and the common information generation unit 104. Furthermore, the scheduling unit 101 stores scheduling information related to the TB PPDUs from the terminals 200 and outputs this scheduling information to the tone demapping unit 110, the demodulation unit 111, and the error correction decoding unit 112 for reception processing.
[0077] The frequency resource information of the terminal (e.g., RU allocation information) may include information such as RU type (e.g., information indicating either DRU or RRU), RU size, and RU location. For example, when the RU type is DRU, the frequency resource information may include information such as tone interval, tone location (also called tone offset or tone start position), and grouping tone number. In addition to the data of the terminal 200, the terminal's frequency resource information can also be used as frequency resources for transmitting STF and LTF.
[0078] For example, the RU type can be included in the user information field. For instance, one bit from the reserved bits in the existing standard's user information field can be used as another subfield to implement notification of whether control is given for a DRU (containing information about the number of Grouping Tones) or an RRU. When using a subset of subfields of the user information field, for example, the trigger type used for DRU can be imported, and the DRU information can be included in the trigger-related user information subfield. Furthermore, in DRU mode, the number of Spatial Streams (SS) of the TB PPDU can be limited (e.g., limited to SS number = 1), and a subset of bits from the SS allocation subfield can be used for DRU notification. Additionally, the RU type can also be included in the public information field (examples of which will be described later).
[0079] Furthermore, some information about the RU type can also be included in the public information field or the special user information field that notifies the terminal. For example, the reserved bits of the special user information field in the existing standard can be used to notify the Grouping Tone number as general terminal information, and the reserved bits of the user information field can be used to notify the information indicating whether it is a DRU or an RRU as terminal-specific information.
[0080] Furthermore, RU type information may not be included in the frequency resource information. For example, RU type information can be omitted, and the RU type for DRU-enabled terminals (e.g., DRU-capable STAs) can be controlled as DRU. Similarly, the RU type for DRU-unsupported terminals (e.g., DRU-non-capable STAs) can be controlled as RU. In this case, the Grouping Tone number information can be ignored for DRU-non-capable STAs.
[0081] The RU table setting unit 102 stores, for example, a corresponding RU allocation table (or RU table) between frequency resource information and bit information used for DRUs or RRUs. In the case of DRU allocation (where the RU type is DRU), the RU table setting unit 102 stores the RU allocation table for DRUs and outputs it to the user information generation unit 103. In the RU allocation table for DRUs, at least the value of the RU allocation subfield is made to correspond to the RU index defined according to the RU size and the number of Grouping Tones (or Tone interval).
[0082] For example, the RU allocation table used by DRU can be reused. Figure 4 The diagram shows the RU allocation table defined in 11be for RRU allocation, and refers to the RU index defined based on the number of Grouping Tones used when applying DRU. For example, the definition of the RU index used in the RU allocation table for DRU can vary depending on the number of Grouping Tones.
[0083] For example, an RU index defined based on the number of Grouping Tones can be used as an RU index for DRUs. It is defined as the start position of the Tone configuration, the Tone interval (e.g., the interval of valid Tones excluding Guard and Null Tones), and the end position of the Tone configuration. An example of an RU index defined based on the number of Grouping Tones will be illustrated later. Additionally, in the case of RRU allocation, the following can be used... Figure 4 The table shown.
[0084] The user information generation unit 103 uses the RU allocation table input from the RU table setting unit 102 to convert the control information input from the scheduling unit 101, which includes terminal ID and / or TB PPDU frequency resource information, into specified bit information. Then, the user information generation unit 103 generates a user information field and a special user information field containing the converted bit information, and outputs them to the trigger frame generation unit 105.
[0085] The common information generation unit 104 converts the control information (e.g., the bandwidth, LTF symbol information, and AP transmit power information of the TB PPDU input from the scheduling unit 101) into specified bit information. For example, the common information generation unit 104 may include the RU type as terminal general information. For example, reserved bits in the common information field for 11be-oriented (EHT variant) may be used for RU type notification. The common information generation unit 104 generates a common information field containing the converted bit information and outputs it to the trigger frame generation unit 105.
[0086] The trigger frame generation unit 105 generates a trigger frame, which includes: a public information field input from the public information generation unit 104; and a user information list input from the user information generation unit 103, consisting of a special user information field and a user information field for multiple terminals 200. In addition to the public information field, the special user information field, and the user information list, a MAC header, padding, and FCS (frame check sequence) may be appended to the generated trigger frame. The trigger frame generation unit 105 outputs the generated trigger frame to the error correction coding unit 106.
[0087] The error correction coding unit 106 takes the transmission data signal containing the trigger frame input from the trigger frame generation unit 105 as input, performs error correction coding on the input signal, and outputs the coded signal to the modulation unit 107.
[0088] The modulation unit 107 modulates the signal input from the error correction coding unit 106 and outputs the modulated data signal to the wireless transceiver unit 108.
[0089] Furthermore, when the modulated data signal is an Orthogonal Frequency Division Multiplexing (OFDM) signal, AP 100 can perform OFDM-related transmission signal processing. For example, AP 100 (e.g., modulation unit 107) can map the modulated signal to a specified frequency resource, perform Inverse Fast Fourier Transform (IFFT) processing to convert it into a time waveform, and form an OFDM signal by adding a Cyclic Prefix (CP).
[0090] The wireless transceiver unit 108 performs prescribed wireless transmission processing on the modulated signal input from the modulation unit 107, including D / A (digital-to-analog) conversion and up-conversion to the carrier frequency, and transmits the processed signal to the terminal 200 via an antenna. Furthermore, the wireless transceiver unit 108 receives signals transmitted from the terminal 200 via an antenna, performs prescribed wireless reception processing on the received signals, including down-conversion to baseband and A / D (analog-to-digital) conversion, and outputs the processed signal to the OFDM demodulation unit 109.
[0091] The OFDM demodulation unit 109 demodulates the signal input from the wireless transceiver unit 108, and performs OFDM-related received signal processing on the 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.
[0092] Tone demapping unit 110 obtains the received signal at the specified tone position from the received signal input by OFDM demodulation unit 109 based on the DRU frequency resource information (e.g., including the number of grouping tones of the receiving terminal) input from scheduling unit 101, and outputs it to demodulation unit 111.
[0093] The demodulation unit 111 performs corresponding demodulation processing on the received signal input from the tone demapping unit 110 based on the modulation scheme information (QPSK, 16QAM, etc.) of the receiving terminal input from the scheduling unit 101, and outputs the demodulation processing result to the error correction decoding unit 112. Furthermore, when there are multiple grouping tones, the demodulation unit 111 uses the received LTF symbols to perform channel estimation processing using consecutive tones, thereby improving accuracy. Additionally, in the channel estimation processing (including frequency offset correction), the demodulation unit 111 can also use the received STF symbols for processing, in addition to LTF symbols.
[0094] The error correction decoding unit 112 performs error correction decoding on the received signal input from the demodulation unit 111 and outputs the decoded signal as a received data signal.
[0095] [Structure example of terminal 200]
[0096] Figure 10 This is a block diagram showing a structural example of terminal 200.
[0097] Figure 10 The terminal 200 shown may include, for example, a wireless transceiver unit 201, a demodulation unit 202, an error correction decoding unit 203, a common information decoding unit 204, an RU table setting unit 205, a user information decoding unit 206, an error correction coding unit 207, a modulation unit 208, a tone mapping unit 209, and an OFDM modulation unit 210.
[0098] in addition, Figure 10At least one of the demodulation unit 202, error correction decoding unit 203, common information decoding unit 204, RU table setting unit 205, user information decoding unit 206, error correction coding unit 207, modulation unit 208, tone mapping unit 209, and OFDM modulation unit 210 shown may be included in Figure 8 In the control unit shown, Figure 10 The wireless transceiver unit 201 shown may be included in Figure 8 shown in the Communications Department.
[0099] exist Figure 10 In this configuration, the wireless transceiver unit 201 receives signals via an antenna, performs wireless reception processing such as down-conversion and A / D conversion on the received signals, and outputs the obtained received signals to the demodulation unit 202. Furthermore, the wireless transceiver unit 201 performs wireless transmission processing such as up-conversion and D / A conversion on the input signals from the OFDM modulation unit 210, and transmits the processed signals from the antenna.
[0100] The demodulation unit 202 demodulates the received signal (received data) input from the wireless transceiver unit 201 and outputs the demodulated signal to the error correction decoding unit 203.
[0101] Furthermore, when the input signal is an OFDM signal, the terminal 200 can perform OFDM-related received signal processing. For example, the terminal 200 (e.g., demodulation unit 202) can perform CP removal processing and FFT processing.
[0102] 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. Furthermore, the error correction decoding unit 203 outputs the trigger frame from the received data signal to the common information decoding unit 204 and the user information decoding unit 206.
[0103] The common information decoding unit 204 extracts the common information field from the trigger frame input by the error correction decoding unit 203. The common information decoding unit 204 decodes the terminal general information contained in the common information field and outputs the terminal general information to the user information decoding unit 206. For example, if the common information field contains the RU type, the common information decoding unit 204 outputs the RU type to the user information decoding unit 206.
[0104] The RU table setting unit 205 stores the same RU allocation table as the RU allocation table of the RU table setting unit 102 of the AP 100 (for example, establishing a corresponding RU table with frequency resource information for DRU or RRU and bit information), and outputs the RU allocation table to the user information decoding unit 206.
[0105] The user information decoding unit 206 extracts a user information list from the trigger frame input by the error correction decoding unit 203. The extracted user information list may contain, for example, one or more user information fields and special user information fields. The user information decoding unit 206 decodes terminal-specific information based on the terminal general information input from the public information decoding unit 204, and the user information field containing the AID of the terminal 200 contained in the user information fields and special user information fields.
[0106] For example, the user information decoding unit 206 uses the RU allocation table input from the RU table setting unit 205 to obtain frequency resource information based on the frequency resource information (bit information) of the TB PPDU contained in the terminal-specific information.
[0107] Frequency resource information may include RU type, RU size, and RU index. For example, when the RU type is DRU, the frequency resource information may include RU index information defined based on the Tone interval, Tone position, and GroupingTone number in the DRU RU allocation table. Furthermore, in addition to the data from terminal 200, the frequency resource information can also be used as frequency resources for transmitting STF and LTF.
[0108] The user information decoding unit 206 outputs the decoded terminal-specific information (including TB PPDU transmission control information containing frequency resource information) to the error correction coding unit 207, the modulation unit 208, and the tone mapping unit 209.
[0109] The error correction coding unit 207 performs error correction coding on the transmitted signal based on the TB PPDU transmission control information (coding rate, etc.) input from the user information decoding unit 206, and outputs it to the modulation unit 208.
[0110] The modulation unit 208 modulates the signal encoded by the error correction coding unit 207 according to the TB PPDU transmission control information (modulation mode, etc.) input from the user information decoding unit 206, and outputs the processed signal to the tone mapping unit 209.
[0111] Tone mapping unit 209, based on TB PPDU transmission control information (frequency resource information, etc.) input from user information decoding unit 206, configures the modulated signal input from modulation unit 208 at a predetermined tone position and outputs it to OFDM modulation unit 210. For example, when the number of grouping tones is greater than 1, tone mapping unit 209 will configure the same number of tones as the number of grouping tones consecutively.
[0112] The OFDM modulation unit 210 performs IFFT processing on the mapped modulation signal from the Tone mapping unit 209, forms an OFDM signal by adding a CP, and outputs the OFDM signal to the wireless transceiver unit 201.
[0113] The above describes the structural examples of AP 100 and terminal 200.
[0114] [Operational Examples of AP 100 and Terminal 200]
[0115] Next, an operational example of AP 100 and terminal 200 will be explained.
[0116] AP 100 uses a trigger frame to notify terminal 200 of the frequency resources used by the Tone Group-based DRU and instructs the transmission of a TB PPDU for the Tone Group-based DRU. Terminal 200 uses the received trigger frame to determine the frequency resources used by the Tone Group-based DRU for terminal 200 and transmits a TB PPDU for the Tone Group-based DRU.
[0117] As described above, AP 100 and terminal 200 have RU table setting units 102 and 205. RU table setting units 102 and 205, for example, store existing RRU allocation tables (e.g., ...). Figure 4 In addition to the table shown, it also stores the DRU allocation table that establishes the corresponding DRU use frequency resource information and bit information.
[0118] The following is an example of using the RU allocation table for DRU.
[0119] In the DRU allocation table, the value of the RU allocation subfield (i.e., the value of the RU allocation information) corresponds at least to the RU size and the RU index defined according to the Grouping Tone number.
[0120] Regarding the RU index defined based on the number of Grouping Tones, the following approach can be adopted: In the allocation of DRUs of the same size within a specified TB PPDU bandwidth (e.g., a 20 MHz channel), the more Grouping Tones there are, the wider the Tone interval is set between Tone groups.
[0121] Figure 11 This shows an example of the RU index definition when the TB PPDU has a 20 MHz channel and the Grouping Tone number is 2.
[0122] like Figure 11As shown, for a RU index, two consecutive Tones are allocated. That is, the DRU corresponding to each RU index is composed of discretely configured Tone groups (allocation units) with a Grouping Tone number of 2. Furthermore, as... Figure 11 As shown, with Figure 6 Compared to the case where the Grouping Tone number is 1, the Tone interval is defined (or set) to be wider. For example, in the case of 26 toneDRU, when the Grouping Tone number is 1 (see...), Figure 6 The Tone interval is defined as 9 Tones; in contrast, when the Grouping Tone number is 2 (see [reference]). Figure 11 The tone interval is defined as 18 tones. Similarly, in the case of a 52-tone DRU, when the grouping tone count is 1 (see [reference]). Figure 6 Tone intervals are defined as 4 tones or 5 tones; conversely, when the grouping tone number is 2 (see [reference]). Figure 11 The tone interval is defined as 8 tones or 10 tones. The same applies to the 106-tone DRU.
[0123] Thus, by increasing the number of Grouping Tones (the number of Tones contained in a Tone group) and widening the Tone intervals between Tone groups, the number of RU indexes (equivalent to the OFDMA multiplexing number) can be set to be the same regardless of the number of Grouping Tones. Therefore, even in Tone-based DRUs, the relationships between the values of the RU allocation subfield, RU size, and RU index of DRUs without Grouping (e.g., DRUs with a Grouping Tone number of 1) and RRUs can be reused. For example, the RU size used by Tone-based DRUs and the RU indexes defined according to the Grouping Tone number can be mapped to the values of existing RU allocation subfields. By using existing RU allocation subfields, the import of Tone-based DRUs can be easily achieved.
[0124] Furthermore, by increasing the tone spacing between tone groups, the number of assigned tones per 1 MHz (approximately 13 tones) can be reduced, thus ensuring power gain in tone-group-based DRUs. For example, in a 26-ton DRU, when the grouping tone number is 2, compared to the case where the grouping tone number is 1 (e.g., refer to...), Figure 6Similarly, if the tone interval is set to 9 tones, the maximum number of tones per 1 MHz (approximately 13 tones) is 4 tones. In this case, compared to setting the tone interval to 18 tones according to this embodiment (for example, refer to...), Figure 11 Compared to the previous tone planning, the PSD of each tone is reduced by half, resulting in a 3 dB decrease in power boost gain. In this embodiment, this decrease in power boost gain can be suppressed by increasing the tone spacing between tone groups.
[0125] The following is an example of an RU index defined based on the Grouping Tone number.
[0126] <First Example>
[0127] The first example illustrates an instance of defining an RU index for each Grouping Tone number.
[0128] For example, such as Figure 12 As shown, for each Grouping Tone, a DRU index can be defined consisting of three elements: [starting position of Grouping Tone: Tone interval: ending position of Grouping Tone].
[0129] Additionally, the aforementioned tone interval is, for example, an interval obtained by counting the number of valid tones (the number of tones corresponding to the frequency bands that can allocate uplink signals) in the TB PPDU band (or communication band), excluding the DC tone (the band corresponding to DC), Guard Tone (the band corresponding to the guard band), and Null Tone. Furthermore, tone is also called a subcarrier.
[0130] Figure 12 The example shows the definition of the RU index when the TB PPDU has a 20 MHz channel bandwidth and the RU size is 26 tone. Figure 12 In the example, the RU index, the tone position of the RRU, the tone position of the DRU with a grouping tone number of 1 (i.e., no tone grouping), and the tone position of the DRU with a grouping tone number of 2 are defined. Figure 12 In the definition of the RU index shown, for example, the DC position is set to Tone number 0, subcarriers with frequencies lower than DC are assigned negative numbers, and subcarriers with frequencies higher than DC are assigned positive numbers.
[0131] For example, in the case of a DRU where the RU type indicates the number of Grouping Tones = 2, and the RU assignment value indicates RU1 where the RU size = 26 (e.g., in...) Figure 4 In the RU allocation table shown, if the RU allocation value is 0, use Figure 12 The definition of RU1 shown establishes a correspondence between the Tone-group-based DRU and the Tone positions [-121 -120:18:104 105]. In this case, for the Tone-group-based DRU, consecutive Tones, namely Tone#-121 and Tone#-120, are grouped, and two Tones are assigned sequentially at intervals of 18 valid Tones. The last two Tones (the 25th and 26th Tones constituting the 26-tone DRU) are Tone#104 and Tone#105. For Figure 12 The other RU indexes shown are also assigned Tones in the same way.
[0132] In addition, although Figure 12 A RU index with Grouping Tone=2 is defined, but the number of Grouping Tones is not limited to 2. RU configurations (RU indexes) with more than 2 Grouping Tones can also be defined.
[0133] Figure 13 This shows an example of the definition of an RU index with Grouping Tone=3. Figure 14 This shows an example of the definition of a RU index with Grouping Tone=4. Figure 13 and Figure 14 In this case, since 26 tone DRUs are not divisible by the grouping tone number, the RU index number (OFDMA multiplexing number) is 8 compared to grouping tones = 1 or 2, reducing the multiplexing number equivalent to one terminal. In this situation, some valid tones become unused tones, but by setting tones near the DC (Distribution Center) that are susceptible to interference to unused tones, the impact on system performance caused by the increase in unused tones can be reduced.
[0134] Furthermore, it can still be used even when Grouping Tone = 3 or 4. Figure 4 The RU allocation table shown. For example, by... Figure 4 The RU allocation value of 8 indicates that RU9 is an undefined RU index when Grouping Tone = 3 or 4, and therefore will not be indicated. However, because Figure 13 and Figure 14 The RU index defined in [the document] can be used with existing RU allocation tables ( Figure 4 The values of the RU allocation table are established accordingly, so the existing RU allocation table can be used.
[0135] Thus, for example, by increasing the number of grouping tones, the accuracy of channel estimation and frequency offset tolerance can be improved.
[0136] <Second Example>
[0137] In the second example, the definition of the RU index when setting the number of Grouping Tones based on the RU size of the DRU (e.g., also called the DRU size) is explained.
[0138] For example, the number of Tones contained in a Tone group (assignment unit) can vary depending on the DRU size.
[0139] For example, such as Figure 15 and Figure 16 As shown, the number of Grouping Tones can vary depending on the DRU size. Figure 15 This is an example of a 20MHz channel, where the grouping tones for DRU sizes of 26, 52, and 106 tones are set to 1, 2, and 4 respectively. Figure 15 In this context, when the DRU size is 26 Tones, Tone grouping should not be applied.
[0140] also, Figure 16 This is an example of a 40 MHz channel, where the grouping tones for DRU sizes of 26, 52, and 106 tones are set to 1, 1, and 2 respectively. Figure 16 In this context, when the DRU size is 26 or 52, Tonegrouping should not be applied.
[0141] Thus, in Figure 15 and Figure 16 In this context, a smaller DRU size allows for a smaller number of Grouping Tones. Conversely, a larger DRU size allows for a larger number of Grouping Tones, thus enabling distributed allocation without increasing the number of Tones allocated per 1 MHz (approximately 13 Tones). Furthermore, in... Figure 15 and Figure 16 In the example, regardless of the DRU size, the tone spacing between grouping tones is 9 tones or more, so the specified power boost gain can be maintained even when tone grouping is applied.
[0142] In addition, tone planning can be implemented for channels such as 20 MHz. Figure 15 ) and Tone planning for the 40 MHz channel ( Figure 16 As such, the relationship between DRU size and the number of grouping tones differs depending on the TB PPDU bandwidth or distribution bandwidth. Therefore, regardless of the TB PPDU bandwidth or distribution bandwidth, it is possible to set the tone interval between grouping tones to a specified number of tones or more (within...). Figure 15 and Figure 16 In the example, the number of tones is 9 or higher, and the specified power boost gain can be maintained even when tones grouping is applied.
[0143] Furthermore, the second example illustrates the case where a smaller DRU size results in a lower number of Grouping Tones, but the relationship between DRU size and the number of Grouping Tones is not limited to this. For example, a smaller DRU size could also result in a higher number of Grouping Tones.
[0144] Furthermore, the second example illustrates a case where the tone interval between grouping tones is a constant value (e.g., 9 tones) regardless of the DRU size, but it is not limited to this. For example, similar to the first example, the more grouping tones determined by the DRU size, the wider the tone interval between tone groups can be set.
[0145] <Third Example>
[0146] In the third example, the setting of the number of Grouping Tones in the specified sub-channel (e.g., whether different numbers of Grouping Tones exist mixed together) is explained.
[0147] As illustrated in the Tone planning example above, the Tone interval varies depending on the number of Grouping Tones within a TB PPDU band or a Distribution band where DRU allocation is implemented. Therefore, scheduling can become complex when OFDMA multiplexing DRUs with different Tone intervals.
[0148] Therefore, in the third example, DRUs with different grouping tones are not applied within the specified sub-channel. That is, within the specified sub-channel, the grouping tone number is the same (common) number for multiple terminals 200.
[0149] In addition, the specified sub-channel can be, for example, an 80 MHz channel as the receiving processing unit in the 11be standard, a TB PPDU band (the entire uplink transmit band), or a 20 MHz channel as the smallest sub-channel unit, or other bands.
[0150] For example, AP 100 (e.g., Figure 9 The public information generation unit 104 uses the public information field of the trigger frame, which is an information field shared by multiple terminals 200, or the reserved bits of the special user information field, to notify the number of Grouping Tones in the specified sub-channel as terminal general information.
[0151] For example, AP 100 can notify terminal 200 that the RRU and DRU (Grouping Tone number = 1) are in the specified range. Figure 6 The Tone plan shown) and DRU (Grouping Tone number = 2 (e.g., Figure 11 The information of one of the Tone schemes shown (e.g., 2 bits of information).
[0152] In addition, in such Figure 15 and Figure 16 As shown, when using different grouping tones based on DRU size, AP 100 can also schedule only DRUs with the same grouping tone number. For example, this could be done in applications... Figure 16 Under the Tone planning, AP 100 allocates DRUs with the same number of Grouping Tones (Grouping Tone = 1) and sizes of RUs of 26 and 52 within the specified sub-channel.
[0153] This simplifies the scheduling of terminals 200 by AP 100 and facilitates the implementation of DRU based on Tone groups. Furthermore, by notifying the Grouping Tone number as general information for all terminals, the signaling load is reduced compared to notifying each terminal individually.
[0154] The above provides an example of an RU index defined based on the Grouping Tone number.
[0155] Thus, in this embodiment, AP 100 and terminal 200 transmit and receive trigger frames containing allocation information based on DRU allocation based on Tone group, and control the transmission and reception of uplink signals based on the allocation information, wherein Tone groups containing one or more Tones are discretely configured with Tone intervals set according to the number of Grouping Tones.
[0156] Therefore, for example, even in tone planning using tone grouping, AP 100 can suppress the increase in overhead and appropriately notify terminal 200 of the RU allocation using tone grouping. Thus, according to this embodiment, the transmission control efficiency in wireless communication can be improved.
[0157] (Implementation Method 2)
[0158] In this embodiment, a method for applying different Grouping Tone numbers to LTF symbols and data symbols (including pilots) used in channel estimation processing, etc., will be described.
[0159] [Structure example of AP 100]
[0160] The structure of AP 100 in this embodiment can be the same as that of AP 100 in embodiment 1 (e.g., Figure 9 The structure is the same. In this embodiment of AP 100, the operation of the common information generation unit 104 and the tone demapping unit 110 is different from that in embodiment 1.
[0161] In this embodiment, the grouping tone counts for LTF symbols and data symbols can be different. For example, AP100 notifies terminal 200 of the grouping tone counts for LTF symbols and data symbols via a trigger frame.
[0162] For example, the public information generation unit 104 notifies the terminal 200 of the number of grouping tones for LTF symbols (referred to as UHR-LTF in the case of 11bn) and data symbols (including pilots) used for TB PPDU, as well as the number of LTF symbols.
[0163] For example, the number of LTF symbols can be notified through the Number Of HE / EHT-LTF Symbols subfield of the public information field.
[0164] Furthermore, for example, the number of repetitions of the LTF symbol can be combined with the number of spatial streams in the user information field for notification. For example, when the number of LTF symbols is the same as the number of SS symbols, the number of repetitions is set to 1. Alternatively, for example, when the number of LTF symbols is greater than the number of SS symbols, the quotient obtained by dividing the number of LTF symbols by the number of SS symbols can be used as the number of repetitions for notification.
[0165] In addition, for example, the Grouping Tone numbers applied to LTF and Data respectively can be included in the DRU notification pattern and notified as RU type.
[0166] For example, such as Figure 17 As shown, a correspondence can be established between the grouping tone number applied to LTF and data (hereinafter referred to as LTF / data Grouping Tone information) and RU type values (e.g., the value of the RU type subfield), and the value of the RU type subfield can be notified from AP100 to terminal 200. Figure 17 In this context, when the RU type value (RU type subfield value) is 0 to 2, the number of grouping tones applied to LTF symbols and data symbols is the same. On the other hand, when the RU type value (RU type subfield value) is 3, the number of grouping tones applied to LTF symbols is different from the number of grouping tones applied to data symbols, and control is performed to apply tone grouping to LTF symbols but not to data symbols.
[0167] LTF / Data Grouping Tone information (e.g., LTF / Data Grouping Tone information) Figure 17 For example, notifications for RU types can be sent using reserved bits in the common information field or the Trigger Dependent CommonInfo subfield. Alternatively, LTF / Data Grouping Tone information can be sent as terminal general information in reserved bits in the special user information field or the Trigger Dependent CommonInfo subfield.
[0168] Additionally, when using the trigger-related public information subfield or the trigger-related user information subfield, the type that prompts the sending of the TB PPDU that applied the DRU allocation can be added as the trigger type, and when this trigger type is indicated, LTF / Data Grouping Tone information can be included in the trigger-related public information subfield or the trigger-related user information subfield.
[0169] Tone demapping unit 110 uses DRU frequency resource information, including the grouping tone number of the receiving terminal, input from scheduling unit 101, to acquire the received signal from a predetermined tone position in the signal input from OFDM demodulation unit 109, and outputs it to demodulation unit 111. Here, if the LTF of the receiving terminal is different from the grouping tone number of the data, tone demapping unit 110 acquires the received signal from the tone position based on the grouping tone number set for LTF and data respectively.
[0170] Here, the Tone demapping unit 110 obtains the number of repetitions of the LTF symbol based on the control information received from the scheduling unit 101 and directed to the terminal 200, and determines the Grouping Tone position corresponding to the pre-defined number of repetitions.
[0171] [Structure example of terminal 200]
[0172] The structure of the terminal 200 in this embodiment can be the same as that of the terminal 200 in embodiment 1 (for example, Figure 10 The structure is the same. However, in the terminal 200 of this embodiment, the operation of the Tone mapping unit 209 is different from that in embodiment 1.
[0173] In this embodiment, the Tone mapping unit 209 configures the modulated signal at a predetermined Tone position based on the TB PPDU transmission control information (frequency resource information, etc.) input from the user information decoding unit 206, and outputs it to the OFDM modulation unit 210. For example, when the number of Grouping Tones is greater than 1, the Tone mapping unit 209 configures the same number of Tones as the number of Grouping Tones consecutively.
[0174] Here, in the TB PPDU transmission control information input from the user information decoding unit 206, if the grouping tone number of LTF and data is different, the tone mapping unit 209 uses the grouping tone number set for LTF and data respectively to allocate tone positions and outputs it to the OFDM modulation unit 210.
[0175] Furthermore, the Tone mapping unit 209 configures the Grouping Tone according to a rule pre-agreed upon by both the transmitting and receiving parties, for example, based on the number of repetitions of the LTF symbol. The Tone position (frequency hopping mode) corresponding to the number of repetitions of the LTF symbol can be defined in the specification, or it can be notified from the AP 100 to the terminal 200 when the terminal 200 connects (or associates) to the AP 100.
[0176] Furthermore, when spatial multiplexing the transmitted data, LTF symbols can be repeatedly transmitted in a number corresponding to the number of spatial multiplexing (or the number of spatial streams (SS)). For example, multiple LTF symbols, multiplied by an orthogonal code of length equal to the number of spatial multiplexing (or the number of SS), and the same number as the number of SS, can be repeatedly transmitted a specified number of times. For instance, with 3 SS and 2 repetitions, a total of 6 LTF symbols can be transmitted, which are obtained by repeating the 3 symbols multiplied by the orthogonal code twice. In this case, the position of the tone configured for the LTF symbols can be different for each repetition.
[0177] Figure 18 This illustrates an example of a TB PPDU with different Grouping Tone numbers applied to LTF symbols and data symbols. Figure 18 In this configuration, the grouping tone number for LTF symbols is set to 2, and the grouping tone number for data symbols is set to 1. Furthermore, LTF symbols are retransmitted twice (the same number of LTF symbols as the number of SS symbols are retransmitted twice).
[0178] Figure 19 Show Figure 18 An example of tone planning for the LTF symbol of the 0th repetition (Repetition#0), the LTF symbol of the 1st repetition (Repetition#1), and the data symbol.
[0179] like Figure 18 As shown, the number of grouping tones for data symbols is 1, while the number of grouping tones for LTF symbols is 2. Therefore, as explained in Embodiment 1, for a given DRU size, the tone spacing between grouping tones of LTF symbols is set to be wider than the tone spacing between grouping tones of data symbols. For example, in the case of DRU size = 26 tones, the tone spacing for data symbols is 9 tones, while the tone spacing for LTF symbols is 18 tones.
[0180] In addition, such as Figure 19As shown, the grouping tone configuration of the LTF symbol is offset by 9 tones between the 0th and 1st repetitions. This allows the LTF symbol of a specific repetition to be configured at the location of the data symbol's tone. For example, AP 100 can demodulate the first tone of a data symbol (e.g., an odd-numbered tone) using the tone of the 0th repetition of the LTF symbol, and demodulate the second tone (e.g., an even-numbered tone) using the tone of the 1st repetition of the LTF symbol. Therefore, AP 100 can perform high-precision channel estimation, frequency offset correction, and other demodulation processing using multiple grouped tones of LTF symbols.
[0181] Thus, by setting the grouping tones for LTF symbols and data symbols separately, for example, by applying tone grouping to LTF symbols, the performance of demodulation processes such as channel estimation and frequency offset correction at the receiver can be improved. Furthermore, for example, by not applying tone grouping to data symbols, the power boost gain can be increased.
[0182] Additionally, the LTF that is repeatedly sent by the application is also called "Extra-LTF".
[0183] Furthermore, the grouping tone number for STF symbols (e.g., UHR-STF) can be set to the same number as that for LTF symbols. For example, it can be controlled such that tone grouping (set to grouping tone number > 1) is applied to both STF and LTF symbols, but tone grouping (set to grouping tone number = 1) is not applied to data symbols.
[0184] Alternatively, the grouping tone number for STF symbols (e.g., UHR-STF) can be set to the same number as that for data symbols. For example, it is possible to control the application of tone grouping to LTF symbols (setting the grouping tone number > 1) while not applying tone grouping to STF symbols and data symbols (setting the grouping tone number = 1).
[0185] In addition, for example, such as Figure 20 As shown, it is also possible to avoid repeating LTF symbols and instead configure the transmission for each tone (e.g., apply them separately). Figure 19Each tone plan for Repetition#0 and Repetition#1 makes the orthogonal code (OCC) multiplied with the LTF symbol different. Since the number of LTF symbols can be reduced, the overhead can be reduced.
[0186] Furthermore, in this embodiment, the following control is described: Tone Grouping is applied to LTF symbols (setting the Grouping Tone number > 1), but not to data symbols (setting the Grouping Tone number = 1), but this is not limited to this. For example, the following control can also be performed: Tone Grouping is not applied to LTF symbols (setting the Grouping Tone number = 1), but Tone Grouping is applied to data symbols (setting the Grouping Tone number > 1). Alternatively, Tone Grouping can be applied to both LTF symbols and data symbols, and the Grouping Tone number for each LTF symbol and data symbol can be set separately.
[0187] The various embodiments of this disclosure have been described above.
[0188] Furthermore, when applying DRU, the type of LTF symbol (also known as UHR-LTF Type in the 11bn standard) can be set (or restricted / limited) to a type with the same symbol length as the data symbol (also known as 4×UHR-LTF in the 11bn standard). This ensures that the minimum tone interval of the LTF symbol is equal to the minimum tone interval of the data symbol, and allows the LTF symbol to be configured at a frequency position that is the same as or close to the tone of the discretely configured data symbols, thus improving demodulation performance. For example, the GI And UHR-LTF Type subfield in the common information field of the trigger frame indicates one of 1×UHT-LTF (1 / 4 of the data symbol length), 2×UHT-LTF (1 / 2 of the data symbol length), or 4×UHT-LTF (the data symbol length). For example, when applying DRU with the aforementioned LTF symbol type restriction, the GI And UHR-LTF Type subfield can be reinterpreted as having a meaning different from the data symbol length. For example, as... Figure 21 As shown, when DRU is applied, the information indicated by the GI And UHR-LTF Type subfield can be reinterpreted as the number of grouping tones applied to LTF symbols.
[0189] Furthermore, frequency hopping (Tone hopping) performed for each repeated transmission of LTF can also include the application of midamble.
[0190] Furthermore, the RU type (indicating information about either DRU or RRU) or Grouping Tone number is not limited to being notified separately for each terminal via terminal-specific information (e.g., user information fields). For example, the RU type or Grouping Tone number can also be notified via terminal-general information (public information fields or special user information fields). For instance, a terminal supporting DRUs can determine whether an RU allocation is for DRUs or RRUs based on the aforementioned notification. On the other hand, a terminal not supporting DRUs can identify an RU allocation as for RRUs without relying on the aforementioned notification (e.g., ignoring the notification).
[0191] In addition, the RU type (indicating information of either DRU or RRU) or the number of Grouping Tones can also be included in terminal general information (public information field, special user information field) or terminal specific information (user information field) as information that is notified separately for each sub-band or sub-channel (e.g., an 80 MHz channel).
[0192] Furthermore, in the above embodiments, the uplink signal is not limited to TB PPDU. For example, the above embodiments can also be applied to RU allocation notifications for PPDUs (UHR MU PPDU, etc.) that are not responses to trigger frames.
[0193] Furthermore, the above embodiments are not limited to the transmission and reception of uplink signals (e.g., uplink PPDU), but can also be applied to the transmission and reception of downlink signals (e.g., downlink PPDU).
[0194] Furthermore, in the above embodiments, the trigger frame for notifying the Grouping Tone count can be a basic trigger frame or other trigger frames. Additionally, in the above embodiments, the control signal for notifying the Grouping Tone count is not limited to a trigger frame; for example, it can be a MAC header (e.g., defining a new field) or a preamble.
[0195] Furthermore, in the above embodiments, the field (or subfield) used for notifying control information is only one example; other fields or subfields may also be used. Additionally, the number of bits used for notifying control information in each field or subfield is only one example; other numbers of bits may also be used.
[0196] Furthermore, in the above embodiments, the values of parameters such as the frequency band of the TB PPDU, the number of grouping tones, the RU size (DRU size), the threshold for the RU size, the RU index, the tone interval in the DRU, the size of the tone (or subcarrier), or the tone position are all examples and may be other values.
[0197] Furthermore, the signal format described in the above embodiments is only one example. It may also be another structure in which at least one of the following has been added or deleted: other fields have been added or deleted: other subfields ...
[0198] Furthermore, although the above embodiments illustrate a case based on the format specified in IEEE 802.11 as an example, the format of an embodiment of this disclosure is not limited to the IEEE 802.11 format.
[0199] This disclosure can be implemented in software, hardware, or software in cooperation with hardware. The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration), and the processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or it can be composed of a single chip containing some or all of the functional blocks. An LSI may also include data input and output. Depending on the degree of integration, an LSI may also be referred to as an "IC (Integrated Circuit)," a "System LSI," a "Super LSI," or an "Ultra LSI."
[0200] The method of integrating the LSI is not limited to LSI; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Alternatively, it can utilize a programmable FPGA (Field Programmable Gate Array) manufactured using the LSI, or a reconfigurable processor that can reconfigure the connections or settings of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.
[0201] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.
[0202] This disclosure can be implemented in all kinds of devices, apparatuses, and systems with communication capabilities (collectively referred to as "communication devices"). A communication device may also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these units. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.
[0203] Communication devices are not limited to portable or movable devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. Examples include: smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.
[0204] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.
[0205] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.
[0206] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.
[0207] An access point according to an embodiment of this disclosure includes: a transmitting circuit that transmits a control signal, the control signal including allocation information for allocating uplink signals based on a resource allocation in which allocation includes allocation units of one or more frequency resources configured discretely at intervals set according to the number of frequency resources included in the allocation unit; and a control circuit that controls the reception of the uplink signals based on the allocation information.
[0208] In one embodiment of this disclosure, when the resource sizes of the resource allocations are the same, the more frequency resources included in the allocation unit, the wider the interval is set.
[0209] In one embodiment of this disclosure, within a certain sub-channel, the number of frequency resources included in the allocation unit is the number shared by multiple terminals.
[0210] In one embodiment of this disclosure, the control signal is a trigger frame that notifies information related to the quantity of frequency resources contained in the allocation unit through an information field shared by the multiple terminals.
[0211] In one embodiment of this disclosure, the number of frequency resources included in the allocation unit varies depending on the size of the resource allocated.
[0212] In one embodiment of this disclosure, the larger the resource size of the resource allocation, the more frequency resources are included in the allocation unit.
[0213] In one embodiment of this disclosure, the number of frequency resources included in the allocation unit differs between long training field symbols (LTF symbols) and data symbols.
[0214] In one embodiment of this disclosure, the control signal is a trigger frame that notifies the terminal of the number of frequency resources contained in the allocation unit for the LTF and the number of frequency resources contained in the allocation unit for the data symbol.
[0215] In one embodiment of this disclosure, a number of Long Training Field Symbols (LTF symbols) corresponding to the number of spatial streams are repeatedly transmitted, and the location of the frequency resources configured for the LTF symbols is different for each repeated transmission.
[0216] In one embodiment of this disclosure, when the resource allocation is applied, the LTF type of the long training field symbol, i.e., the LTF symbol, is set to a type with the same symbol length as the data symbol.
[0217] In one embodiment of this disclosure, the interval is an interval obtained by counting frequency resources in the communication frequency band, excluding the frequency band corresponding to DC and the frequency band corresponding to the guard band, within the frequency band capable of allocating the uplink signal.
[0218] In one embodiment of this disclosure, the control signal is a trigger frame.
[0219] In one embodiment of this disclosure, the trigger frame is a basic trigger frame.
[0220] In one embodiment of this disclosure, the trigger frame is a trigger frame of the type that prompts the transmission of the uplink signal based on the resource allocation.
[0221] In one embodiment of this disclosure, each terminal is notified of information relating to the quantity of frequency resources contained in the allocation unit.
[0222] In one embodiment of this disclosure, information relating to the number of frequency resources contained in the allocation unit is notified separately for each sub-band.
[0223] In one embodiment of this disclosure, the control signal is a trigger frame, and the user information field of the trigger frame includes a Spatial Stream (SS) Allocation subfield, i.e., an SS allocation subfield, which represents the number of spatial streams of the uplink signal. A portion of the bits in the SS allocation subfield informs information related to the allocation of the discrete configuration of the frequency resources to be allocated to the uplink signal.
[0224] A terminal according to an embodiment of this disclosure includes: a receiving circuit that receives a control signal, the control signal including allocation information for allocating an uplink signal based on a resource allocation in which allocation includes allocation units of one or more frequency resources configured discretely at intervals set according to the number of frequency resources included in the allocation unit; and a control circuit that controls the transmission of the uplink signal based on the allocation information.
[0225] In a communication method according to an embodiment of this disclosure, an access point performs the following steps: sending a control signal, the control signal including allocation information for allocating uplink signals based on resource allocation, wherein the resource allocation includes allocation units of one or more frequency resources configured discretely at intervals set according to the number of frequency resources included in the allocation unit; and controlling the reception of the uplink signals based on the allocation information.
[0226] In a communication method according to an embodiment of this disclosure, a terminal performs the following steps: receiving a control signal, the control signal including allocation information for allocating an uplink signal based on a resource allocation in which allocation includes allocation units of one or more frequency resources configured discretely at intervals set according to the number of frequency resources included in the allocation unit; and controlling the transmission of the uplink signal based on the allocation information.
[0227] The entire contents of the description, drawings and abstract contained in Japanese Patent Application No. 2024-064766, filed on April 12, 2024, are incorporated herein by reference.
[0228] Industrial applicability
[0229] One embodiment of this disclosure is useful for wireless communication systems.
[0230] Explanation of reference numerals in the attached figures
[0231] 100 AP
[0232] 101 Dispatch Department
[0233] 102, 205 RU Table Setting Department
[0234] 103 User Information Generation Department
[0235] 104 Public Information Generation Department
[0236] 105 Trigger Frame Generation Unit
[0237] Error Correction Coding Department (106, 207)
[0238] Modulation sections 107 and 208
[0239] 108, 201 Wireless Transceiver Unit
[0240] 109 OFDM Demodulation Department
[0241] 110 Tone Demapping Unit
[0242] 111, 202 Demodulation Department
[0243] Error correction and decoding departments 112 and 203
[0244] 200 terminals
[0245] 204 Public Information Decoding Department
[0246] 206 User Information Decoding Department
[0247] 209 Tone Mapping Department
[0248] 210 OFDM Modulation Section
Claims
1. An access point, comprising: A transmitting circuit that transmits control signals, the control signals containing allocation information for allocating uplink signals based on a resource allocation that includes allocation units of one or more frequency resources configured discretely at intervals set according to the number of frequency resources contained in the allocation unit; and A control circuit that controls the reception of the uplink signal based on the allocation information.
2. The access point according to claim 1, wherein, When the resource sizes of the resource allocations are the same, the more frequency resources contained in the allocation unit, the wider the interval is set.
3. The access point according to claim 1, wherein, Within a certain sub-channel, the number of frequency resources contained in the allocation unit is the number shared by multiple terminals.
4. The access point according to claim 3, wherein, The control signal is a trigger frame. Information related to the quantity of frequency resources contained in the allocation unit is communicated through a shared information field of the multiple terminals.
5. The access point according to claim 1, wherein, The number of frequency resources contained in the allocation unit varies depending on the size of the allocated resources.
6. The access point according to claim 5, wherein, The larger the resource size of the resource allocation, the more frequency resources are set to be included in the allocation unit.
7. The access point according to claim 1, wherein, The number of frequency resources contained in the allocation unit differs between long training field symbols (LTF symbols) and data symbols.
8. The access point according to claim 7, wherein, The control signal is a trigger frame. The trigger frame notifies the terminal of the number of frequency resources contained in the allocation unit for the LTF, and the number of frequency resources contained in the allocation unit for the data symbol.
9. The access point according to claim 1, wherein, The number of long training field symbols, or LTF symbols, corresponding to the number of spatial streams, is repeatedly sent. The location of the frequency resources configured for the LTF symbol differs for each repeated transmission.
10. The access point according to claim 1, wherein, When the resource allocation described above is applied, the LTF type of the long training field symbol, i.e., the LTF symbol, is set to a type with the same symbol length as the data symbol.
11. The access point according to claim 1, wherein, The interval is obtained by counting frequency resources within the communication frequency band, excluding the frequency band corresponding to DC and the frequency band corresponding to the guard band, in the frequency band that can allocate the uplink signal.
12. The access point according to claim 1, wherein, The control signal is a trigger frame.
13. The access point according to claim 12, wherein, The trigger frame is a basic trigger frame.
14. The access point according to claim 12, wherein, The trigger frame is a type of trigger frame that prompts the transmission of the uplink signal based on the resource allocation.
15. The access point according to claim 1, wherein, Each terminal is notified of information related to the quantity of frequency resources contained in the allocation unit.
16. The access point according to claim 1, wherein, Information related to the number of frequency resources contained in the allocation unit is notified separately for each sub-band.
17. The access point according to claim 1, wherein, The control signal is a trigger frame, and the user information field of the trigger frame includes a space stream allocation subfield, i.e., an SS allocation subfield, which represents the number of space streams of the uplink signal. A portion of the bits in the SS allocation subfield informs information related to the allocation of the discrete configuration of the frequency resources to be allocated to the uplink signal.
18. A terminal, comprising: A receiving circuit receives a control signal containing allocation information for allocating uplink signals based on a resource allocation that includes allocation units of one or more frequency resources discretely configured at intervals set according to the number of frequency resources contained in the allocation unit; and A control circuit that controls the transmission of the uplink signal based on the allocation information.
19. A communication method, wherein, The access point performs the following steps: Send a control signal, the control signal containing allocation information for allocating uplink signals based on a resource allocation in which allocation includes one or more frequency resource allocation units configured discretely at intervals set according to the number of frequency resources contained in the allocation unit; as well as The uplink signal reception is controlled based on the allocation information.
20. A communication method, wherein, The terminal performs the following steps: Receive control signals, the control signals containing allocation information for allocating uplink signals based on resource allocation, wherein the resource allocation includes allocation units of one or more frequency resources configured discretely at intervals set according to the number of frequency resources contained in the allocation unit; as well as The uplink signal is transmitted based on the allocation information.
Citation Information
Patent Citations
Scattering prevention structure of decorative molding, and side visor
JP2024064766A
