Terminal devices, communication methods, and integrated circuits

Abstract

The amount of data processing required for receiving data at the terminal is reduced according to the format of the control signal that instructs uplink transmission. [Solution] The terminal device includes a receiving unit that receives a trigger frame requesting the transmission of an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU), which includes a first user information field identified by an association ID (AID) 12 subfield set to a first value, and the first user information field includes common information, and a control circuit that decodes the trigger frame, wherein the first value indicates to a High Efficiency (HE) terminal that the first user information field includes user-specific information for a particular STA.

Description

Technical Field

[0004] , , , , ,

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

Background Art

[0002] In the Institute of Electrical and Electronics Engineers (IEEE), a study on the next-generation wireless local area network (LAN) standard IEEE 802.11be (hereinafter also referred to as "11be"), which is a successor standard to the standard IEEE 802.11ax (hereinafter also referred to as "11ax"), is underway. IEEE 802.11ax is also called "High Efficiency (HE)", and IEEE 802.11be is also called "Extremely High Throughput (EHT)".

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Summary of the Invention

[0004] However, there is room for consideration regarding the format of the control signal that instructs uplink transmission, which can reduce the amount of data received by the terminal.

[0005] Non-limiting embodiments of this disclosure contribute, for example, to the provision of a communication device and communication method that can reduce the amount of receiving processing at a terminal depending on the format of a control signal instructing uplink transmission.

[0006] A terminal device according to one embodiment of the present disclosure includes a receiving unit that receives a trigger frame requesting the transmission of an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU), the trigger frame including a first user information field identified by an association ID (AID) 12 subfield set to a first value, the first user information field including common information, and a control circuit that decodes the trigger frame, wherein the first value indicates to a High Efficiency (HE) terminal that the first user information field includes user-specific information for a particular STA.

[0007] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0008] According to one embodiment of the present disclosure, the amount of receiving processing at the terminal can be reduced depending on the format of the control signal that instructs uplink transmission.

[0009] Further advantages and effects of one embodiment of this disclosure will be made apparent from the specification and drawings. Such advantages and / or effects are provided by several embodiments and features described in the specification and drawings, but not all of them are necessarily provided in order to obtain one or more identical features. [Brief explanation of the drawing]

[0010] [Figure 1] A diagram showing an example of the trigger frame format. [Figure 2] A diagram showing an example of the format of a Common info field. [Figure 3] A diagram showing an example of the format for the User info field. [Figure 4] This diagram shows an example of the value (AID; Association ID) set in the AID12 subfield of the User info field and its description. [Figure 5] Block diagram showing a partial configuration example of an Access Point (AP). [Figure 6] Block diagram showing a partial configuration example of the terminal. [Figure 7] Block diagram showing an example of AP configuration. [Figure 8] Block diagram showing an example of terminal configuration [Figure 9] This diagram shows an example of a User Info field in EHT / EHT+ format, compared to the HE format. [Figure 10] A diagram showing an example of a Specific AID table in Operation Example 1-1. [Figure 11] This diagram shows an example of the placement of the User info list in Operation Example 1-1. [Figure 12] A diagram showing an example of a Specific AID table in Operation Example 1-2. [Figure 13] This diagram shows an example of the placement of the User info list in Operation Example 1-2. [Figure 14] A diagram showing an example of a Specific AID table in Operation Example 1-3. [Figure 15] This diagram shows an example of the placement of the User info list in operation example 1-3. [Figure 16] This diagram shows an example of the arrangement of the User info list in modified versions of operation examples 1-1 to 1-3. [Figure 17] A diagram showing an example of an extended Common field for EHT. [Figure 18] Figure showing an example of the arrangement of the User Info List when applying the common field of FIG. 17 [Figure 19] Figure showing an example of the arrangement of the User Info List when using multiple Reserved fields in the Common field [Figure 20] Figure showing an example of the RU (Resource Unit) arrangement method in the User Info List according to Operation Example 2-1 [Figure 21] Figure showing an example of the RU arrangement method in the User Info List according to Operation Example 2-2 [Figure 22] Figure showing an example of the Specific AID table in Operation Example 2-2 [Figure 23] Figure showing an example of the RU arrangement method in the User Info List according to Operation Example 2-3 [Figure 24] Figure showing an example of the Specific AID table in Operation Example 2-3 [Figure 25] Figure showing an example of the RU arrangement method in the User Info List according to Operation Example 2-4 [Figure 26] Figure showing an example of the Specific AID table in Operation Example 2-4 [Figure 27] Figure showing an example of the User Info field in the EHT / EHT+ format in Operation Example 2-5 compared with the HE format [Figure 28] Figure showing an example of the Specific AID table in Operation Example 2-5 [Figure 29] Figure showing an example of the arrangement of the User info List in Operation Example 2-5 [Figure 30] Figure showing a comparison example of the modified example of the User Info field in the EHT / EHT+ format with the HE format [Figure 31] Figure showing a comparison example of the modified example of the User Info field in the EHT / EHT+ format with the HE format [Figure 32]This diagram shows variations of the User Info field in the EHT / EHT+ format, compared to the HE format. [Figure 33] This diagram shows variations of the User Info field in the EHT / EHT+ format, compared to the HE format. [Modes for carrying out the invention]

[0011] Embodiments of this disclosure will be described in detail below with reference to the drawings.

[0012] [Embodiment 1] 11ax specifies the introduction of uplink OFDMA (Orthogonal Frequency-Division Multiple Access). An access point (AP, also called a "base station") sends a control signal (for example, a "trigger frame") to multiple terminals (also called "STAs (Station)") that it houses, instructing them to transmit uplink OFDMA signals. Note that "notification" may be read as "instruction".

[0013] For example, as shown in Figure 1, a trigger frame defines a Common Info field and a User Info List field (see, for example, Non-Patent Document 1). The Common Info field contains information common to multiple HE terminals (11ax terminals) multiplexed by OFDMA. The User Info List field contains one or more User Info fields, and each User Info field may contain information unique to each HE terminal multiplexed by OFDMA. Figure 2 shows an example of the configuration of the Common Info field, and Figure 3 shows an example of the configuration of the User Info field (see, for example, Non-Patent Document 1).

[0014] The AID12 subfield in the User Info field is used, for example, to notify the Association ID (AID), which is a terminal-specific ID assigned to the terminal during association. In the current IEEE 802.11 standard, values ​​from 1 to 2007 are used as AIDs, and other values ​​are unused (reserve) as AIDs. In the following, the method of allocating frequency resources (RU: Resource Unit) to a specific terminal by notifying the AID assigned to the terminal will be called "Individually addressed RU". Note that transmission using individually addressed RU is sometimes called Scheduled access.

[0015] Furthermore, in 11ax, as shown in Figure 4 for example, a specific AID (hereinafter sometimes referred to as "Specific AID") selected from AIDs that are not used for individually designated RUs (hereinafter sometimes referred to as "unused AIDs" or "reserve AIDs") is used as the value of the AID12 subfield to notify RUs that are not individually designated RUs.

[0016] For example, by setting the Specific AID to AID=0 or AID=2045 as the value of the AID12 subfield, the terminal is instructed that the RU indicated by the RU Allocation subfield, which is the RU allocation information in the User Info field, is a Random Access RU (hereinafter sometimes referred to as "RA-RU") (see, for example, Non-Patent Document 1). Also, by setting the Specific AID to AID=2046, the terminal is instructed that the RU indicated by the RU Allocation subfield in the User Info field is an unallocated RU (also called an Unassigned RU).

[0017] In 11be (EHT) and its next-generation version, beyond 11be (hereinafter sometimes referred to as "EHT+"), the reuse of the 11ax (HE) trigger frame as a control signal to instruct multiple terminals to transmit uplink OFDMA signals is being considered (see, for example, Non-Patent Documents 2, 3, and 4).

[0018] For EHT, the following three requirements are being considered for a new trigger frame for EHT: First, a single trigger frame should be able to specify a combination of HE terminals, EHT terminals, and EHT+ terminals. Second, backward compatibility is required; in other words, the new trigger frame should not affect the operation of HE terminals (for example, HE terminals should be able to receive the new trigger frame). Third, forward compatibility is required; in other words, the new trigger frame should be easily extendable for EHT+.

[0019] However, in addition to the requirements mentioned above, there is room for consideration regarding the new method of transmitting trigger frames, taking into account the terminal's receiving processing load and the overhead of trigger frames. Furthermore, there is room for consideration regarding the placement order of individually designated RUs, RA-RUs, and unassigned RUs.

[0020] Below, we will describe an efficient method for transmitting trigger frames, taking into account the terminal's receiving processing load and the overhead of control signals, in addition to the requirements for the new trigger frame mentioned above.

[0021] [Configuration of the wireless communication system] The wireless communication system according to Embodiment 1 comprises an AP100 and a terminal 200. The AP100 and terminal 200 are examples of wireless communication devices. The AP100 may also be positioned as an example of a wireless transmission device, and the terminal 200 may be positioned as an example of a wireless reception device.

[0022] For example, AP100 sends a Trigger frame to terminal 200 instructing it to send an uplink signal (which may also be called "uplink transmission"). Terminal 200 receives the Trigger frame and uses the resources indicated by the Trigger frame to send an uplink signal (for example, an OFDMA signal) to AP100. The uplink signal sent by terminal 200 may include signals such as data signals and RA signals.

[0023] Here, terminal 200 may be an HE terminal, an EHT terminal, or an EHT+ terminal. AP100 may, for example, send a single trigger frame to multiple terminals of different versions (hereinafter sometimes referred to as "terminal versions") and receive uplink signals from each terminal 200. AP100 separates and decodes the uplink signals of each terminal 200 that are placed on the resources assigned to each terminal 200 from the received signals. AP100 may, for example, be an AP that supports EHT or EHT+ in addition to HE.

[0024] Figure 5 is a block diagram showing a partial configuration example of AP100 according to this embodiment, and Figure 6 is a block diagram showing a partial configuration example of terminal 200 according to this embodiment.

[0025] In AP100 shown in Figure 5, the control unit (or control circuit) 11 generates a control signal (e.g., a trigger frame) that instructs the terminal 200 to transmit an uplink signal. The transmission unit (or transmission circuit) 12 transmits the control signal (trigger frame).

[0026] The processing of the control unit 11 (for example, generating control signals) may include, for example, associating information regarding the format of the terminal information field in a control signal that instructs the transmission of an uplink signal, and unused identification information for terminal identification information assigned to individually specified terminals, according to the terminal version.

[0027] For example, the control unit 11 may set a Specific AID in the Trigger frame, selected from unused IDs that are not used for the terminal ID assigned to the individually specified terminal. This Specific AID may be associated with (or given meaning to) a definition regarding the format of the terminal information field (or may be called the "user information field"). The control unit 11 may, for example, give different meanings to the Specific AID depending on the terminal version. In other words, the interpretation of the Specific AID by the terminal 200 may differ depending on the terminal version.

[0028] On the other hand, in the terminal 200 shown in Figure 6, the receiving unit (or receiving circuit) 21 receives, for example, a control signal (e.g., a trigger frame) that instructs the terminal 200 to transmit an uplink signal.

[0029] The control unit (or control circuit) 22 transmits an uplink signal based on a control signal that instructs the transmission of an uplink signal. The control unit 22 also determines the terminal information field to be received based on, for example, information regarding the format of the terminal information field in the control signal that instructs the transmission of an uplink signal, and an association with unused identification information for the terminal identification information assigned to the individually specified terminal, according to the terminal version. The receiving unit 21 performs reception processing on the determined terminal information field.

[0030] For example, the control unit 22 interprets the definition regarding the format of the terminal information field based on the Specific AID detected in the trigger frame, and the receiving unit 21 performs reception processing according to that interpretation.

[0031] [AP Configuration] Figure 7 is a block diagram showing an example configuration of AP100 according to this embodiment. As illustrated in Figure 7, AP100 may include, for example, a scheduling unit 101, a terminal information acquisition unit 102, a Common Info generation unit 103, an AID control unit 104, a User Info generation unit 105, a Trigger frame generation unit 106, an error correction coding unit 107, a modulation unit 108, a wireless transmission / reception unit 109, a demodulation unit 110, and an error correction decoding unit 111.

[0032] Furthermore, some or all of the scheduling unit 101, terminal information acquisition unit 102, Common Info generation unit 103, AID control unit 104, User Info generation unit 105, and Trigger frame generation unit 106 may constitute, for example, an access control (Medium Access Control, MAC) unit (corresponding to, for example, the control unit 11 in Figure 5). Also, the wireless transmission / reception unit 109 may correspond to, for example, the transmission unit 12 in Figure 5.

[0033] The scheduling unit 101 determines the uplink radio resources and the format of the User Info field to be applied for each terminal 200 based on terminal information output from the terminal information acquisition unit 102 (for example, information such as the terminal version and wireless quality for each predetermined bandwidth). The uplink radio resources may include information or parameters such as the allocated bandwidth, modulation scheme and coding rate (MCS), and target reception level. The wireless resource information and User Info field format for the terminal 200 determined by the scheduling unit 101 are output to the User Info generation unit 105 and the Common Info generation unit 103, for example.

[0034] The Common Info generation unit 103 generates a Common Info field by reusing the HE format exemplified in Figure 2, for example, and outputs it to the Trigger frame generation unit 106. The size of the Common Info field can be the same as the HE format, for example. This ensures backward compatibility. Here, AP100 may also notify terminal 200 of information using the reserved field of Common Info for EHT and / or EHT+ terminals (details will be described later).

[0035] The AID control unit 104 holds information (for example, a table (hereinafter sometimes referred to as the "Specific AID table")) that defines the interpretation of the Specific AID and the User info field in each terminal version, and outputs the Specific AID table to the User Info generation unit 105. The Specific AID table may be defined as a standard. In addition, a part of the Specific AID table may be determined for each AP 100 and notified to the associated terminals 200.

[0036] The User Info generation unit 105 generates a User Info List containing one or more User Info fields and outputs it to the Trigger frame generation unit 106. The User Info field may be the same size as the HE format exemplified in Figure 3, for example. This ensures backward compatibility. In addition to the HE format exemplified in Figure 3 (which may also be called the HE-specific User Info field), the User Info field may also be a newly defined EHT / EHT+ format (which may also be called the EHT-specific User Info field or EHT+-specific User Info field). Note that the " / " in notation such as "A / B" means "and / or" or "at least one of (A and B)".

[0037] The EHT format and the EHT+ format may each include, for example, a field containing common information (Common Info field) shared among terminals 200, and a field containing user information specific to each terminal 200, similar to the HE format.

[0038] To instruct the EHT / EHT+ terminals on the identification information of these formats, the User Info generation unit 105 generates a User Info field containing a Specific AID and User Info fields to which each format is applied, for example, based on the definition of the Specific AID table from the AID control unit 104. A portion of the Specific AID value (e.g., 2045) may be used to represent a special User Info field containing common information for EHT / EHT+ (or EHT-specific common information, or EHT+-specific common information), and this special User Info field may be used as a delimiter to indicate the arrangement of User Info fields for EHT / EHT+. The EHT / EHT+ terminal 200, for example, maintains the same Specific AID table as AP100 and interprets the format definition of the User Info field in the received Trigger frame using the definition of the Specific AID table (details will be described later).

[0039] Here, the Common Info field to which the EHT / EHT+ format is applied may include, for example, the UL BW subfield (upstream transmission bandwidth). While HE supports a maximum bandwidth of 160 MHz, EHT may support a maximum bandwidth of, for example, 320 MHz. Therefore, the EHT / EHT+ terminal 200 may obtain the upstream transmission bandwidth from the UL BW subfield included in the Common information in the EHT / EHT+ format included in the User info field, in addition to (or instead of) the UL BW subfield included in the Common Info field in the HE format. Note that the term "obtain" may be interpreted interchangeably with terms such as "recognize," "understand," "identify," or "specify."

[0040] Furthermore, the User info field using the EHT / EHT+ format may have a different size for the RU allocation subfield (information on uplink transmission bandwidth position and bandwidth) compared to the HE format. For example, to indicate a range of up to 320 MHz, the RU allocation subfield in the EHT / EHT+ format of the User info field destined for EHT / EHT+ terminal 200 may be larger than the RU Allocation subfield (8 bits) in the HE format.

[0041] The Trigger frame generation unit 106 generates a Trigger frame by adding a MAC header, padding, and FCS (frame check sequence) to a set of Common Info fields from the Common Info generation unit 103 and a User Info List (multiple User Info fields) from the User Info generation unit 105, following the format illustrated in Figure 1, for example. The generated Trigger frame is output to the error correction coding unit 107, for example.

[0042] The error correction coding unit 107, for example, takes a transmission data signal including a trigger frame as input, performs error correction coding on the input signal, and outputs the coded signal to the modulation unit 108.

[0043] The modulation unit 108 modulates the signal input from the error correction coding unit 107, for example, and outputs the modulated data signal to the wireless transceiver unit 109. If the modulated data signal is an orthogonal frequency division multiplexing (OFDM) signal, the AP100 (for example, the modulation unit 108) may map the modulated signal to a predetermined frequency resource, perform an inverse fast Fourier transform (IFFT) to convert it into a time waveform, and add a cyclic prefix (CP) to form an OFDM signal.

[0044] The wireless transceiver 109 applies wireless transmission processing, such as D / A (digital to analog) conversion and upconversion to the carrier frequency, to the modulated signal output from the modulation unit 108, and transmits the processed signal to the terminal 200 via the antenna. The wireless transceiver 109 also receives the signal transmitted from the terminal 200 via the antenna, applies wireless reception processing, such as downconversion to the baseband and A / D (analog to digital) conversion, to the received signal, and outputs the processed signal to the demodulation unit 110.

[0045] The demodulation unit 110 performs demodulation processing on the input signal, for example, and outputs the resulting signal to the error correction decoding unit 111. If the input signal is an OFDM signal, the AP100 (for example, the demodulation unit 110) may apply CP removal processing and Fast Fourier Transform (FFT) processing to the OFDM signal.

[0046] The error correction decoding unit 111 decodes the signal input from the demodulation unit 110, for example, to obtain the received data signal from the terminal 200. If the decoded received data contains the terminal information described above, the terminal information is output to the terminal information acquisition unit 102, for example.

[0047] [Device Configuration] Figure 8 is a block diagram showing an example configuration of terminal 200 according to this embodiment. The terminal 200 shown in Figure 8 may include, for example, a wireless transmission / reception unit 201, a demodulation unit 202, an error correction / decoding unit 203, a Common Info acquisition unit 204, an AID control unit 205, a User Info acquisition unit 206, a data generation unit 207, an error correction / encoding unit 208, and a modulation unit 209.

[0048] Furthermore, some or all of the Common Info acquisition unit 204, AID control unit 205, User Info acquisition unit 206, and data generation unit 207 may constitute, for example, an access control (MAC) unit (corresponding, for example, to the control unit 22 in Figure 6). Also, the wireless transmission / reception unit 201 may correspond, for example, to the receiving unit 21 in Figure 6.

[0049] The wireless transceiver 201, for example, receives a received signal using an antenna, performs wireless reception processing on the received signal such as down-conversion and A / D conversion, and outputs the resulting received signal to the demodulation unit 202.

[0050] The demodulation unit 202 performs demodulation processing on the received signal input from the wireless transceiver unit 201, for example, and outputs the demodulated signal to the error correction decoding unit 203. If the input signal is an OFDM signal, the terminal 200 (for example, the demodulation unit 202) may apply, for example, CP removal processing and FFT processing to the OFDM signal.

[0051] The error correction decoding unit 203, for example, 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 the trigger frame from the received data signal to the Common Info acquisition unit 204 and the User Info acquisition unit 206.

[0052] The Common Info acquisition unit 204 extracts information from the Common Info field from the Trigger frame output from the error correction / decoding unit 203, for example, to obtain terminal common information for generating an uplink signal (for example, information such as the type of data to be transmitted and the duration of the uplink signal). The obtained terminal common information is output to the User Info acquisition unit 206, for example.

[0053] The AID control unit 205 may operate in the same manner as the AID control unit 104 in AP100, for example. For example, the AID control unit 205 may output a Specific AID table that defines the interpretation of the User info field for each terminal version to the User Info acquisition unit 206.

[0054] The User Info Acquisition Unit 206 extracts a User Info List (multiple User Info fields) from the Trigger frame output from the Common Info Acquisition Unit 204, and processes the User Info fields in the order they are arranged, while determining the format of the User Info fields using the Specific AID table from the AID Control Unit 205. If it determines that there is an assignment of an individually designated RU or an RA-RU, the User Info Acquisition Unit 206 outputs, for example, terminal common information and terminal individual information used for data generation to the data generation unit 207.

[0055] For example, the User Info acquisition unit 206 compares the AID of terminal 200 assigned by AP100 during association with the AID included in the AID12 subfield of the User info field. If these AIDs match, it can determine that a specially designated RU has been assigned by AP100. In response to this determination, terminal 200 performs reception processing of the remaining terminal-specific information used to generate the uplink signal (e.g., RU placement information, MCS, spatial multiplexing information, uplink target power information) based on the format of the User info field.

[0056] Even if the AIDs do not match, terminal 200 may, for example, if it obtains an access opportunity through an AID indicating an RA-RU (e.g., 0 or 2045), process the reception of the remaining terminal-specific information necessary for generating an uplink random access signal (e.g., RU placement information, MCS, uplink target power information) based on a predetermined format. Furthermore, terminal 200 may stop receiving subsequent User info fields if it detects an AID indicating an unassigned RU. Also, terminal 200 may stop receiving subsequent subfields if it detects an AID indicating the start of padding.

[0057] The data generation unit 207 generates data of a predetermined type and size based on, for example, common terminal information and individual terminal information from the User Info acquisition unit 206, and outputs it to the error correction encoding unit 208.

[0058] The error correction coding unit 208, for example, takes the data signal from the data generation unit 207 as input, and based on the terminal common information and terminal individual information from the User Info acquisition unit 206, performs error correction coding on the transmitted data and outputs the coded signal to the modulation unit 209.

[0059] The modulation unit 209 modulates, for example, the signal input from the error correction coding unit 208, and outputs the modulated signal to the wireless transmission / reception unit 201 based on the terminal common information and terminal specific information from the User Info acquisition unit 206. When the modulated signal is an OFDM signal, the terminal 200 (for example, the modulation unit 209) may form an OFDM signal by, for example, performing IFFT processing after mapping the modulated signal to a frequency resource and then adding a CP.

[0060] The wireless transmission / reception unit 201 applies wireless transmission processing such as up-conversion and D / A conversion to the input signal from the modulation unit 209, and transmits the signal after the wireless transmission processing from the antenna.

[0061] <Operations of the AID control unit 205 and the User Info acquisition unit 206> Hereinafter, an example of the Specific AID table generated by the AID control unit 205 of the terminal 200 and an example of a method for determining the format of the User Info field using the Specific AID table in the User Info acquisition unit 206 will be described.

[0062] The Specific AID table held by the AID control unit 205 indicates that the definition of the format of the terminal information field associated with a specific ID "Specific AID" selected from unused IDs not used for the terminal ID assigned to a specifically designated terminal 200 is changed according to the terminal version such as HE, EHT, or EHT+.

[0063] By using the Specific AID table, in addition to the three aforementioned requirements (for example, that combinations of HE terminals, EHT terminals, and EHT+ terminals can be indicated in one Trigger frame, ensuring backward compatibility, and ensuring forward compatibility), it is possible to reduce the reception processing amount of the terminal 200 and reduce the overhead of the Trigger frame.

[0064] Furthermore, by giving different meanings to the Specific AIDs (0, 2045, 2046, 4095) defined in HE as exemplified in Figure 4, in EHT and EHT+, it is not necessary to introduce new Specific AIDs, thus reducing the consumption of unused AIDs. Therefore, scalability for future systems can be maintained.

[0065] Here, an example of a User Info field in the EHT / EHT+ format is shown in the lower part of Figure 9 in comparison with the HE format. Compared to the User Info field in the HE format (same as Figure 3) shown in the upper part of Figure 9, the size of the RU allocation subfield in the EHT / EHT+ format User Info field may be expanded (for example, expanded by 1 bit from 8 bits to 9 bits). This expansion allows for an increase in the range of supported allocation bandwidth (for example, from 160 MHz to 320 MHz).

[0066] Furthermore, in EHT, whether or not DCM (Dual subCarrier Modulation) is applied may be included in the MCS table. Therefore, the UL DCM subfield (1 bit) exemplified in the upper part of Figure 9 may be deleted as exemplified in the lower part of Figure 9. Also, in EHT+, the maximum number of supported SS (Spatial streams) may be expanded (for example, increased from 8 to 16). Therefore, as exemplified in the lower part of Figure 9, the size of the SS Allocation / RA-RU Information subfield may be expanded (increased) by 1 bit from 6 bits to 7 bits. Also, the Reserved (1 bit) exemplified in the upper part of Figure 9 may be deleted in the lower part of Figure 9. This makes it possible to match the size of the User Info field to the size of the HE format and ensure backward compatibility.

[0067] Next, we will describe a non-restrictive example of how the relationship between Specific AID and the definition of the User Info field format containing Specific AID (which may be rephrased as "association" or "semantic assignment") can vary depending on the terminal version.

[0068] (Example of operation 1-1) Figure 10 shows an example of a Specific AID table in Operation Example 1-1. In Figure 10, as a non-restrictive example, AID=4094 and 4093 may be newly defined as Specific AIDs. In Figure 10, "Undefined (Reserve)" means that it is not defined as a Specific AID. For Specific AIDs (0, 2045, 2046) specified or defined in HE, the same meaning may apply to EHT / EHT+ terminal 200. On the other hand, Specific AID=4095 has different meanings for HE terminal 200 and EHT / EHT+ terminal 200. For each generation of terminal 200 in HE / EHT / EHT+, values ​​that are not defined as either AID or Specific AID may be ignored as Undefined (Reserve), but may be defined as Specific AIDs in future generations.

[0069] When HE terminal 200 detects AID=4095, it may interpret this as the start of padding based on HE's specifications and stop receiving subsequent bit information. When interpreting this as the start of padding, HE terminal 200 assumes that there is no information beyond the AID12 subfield of the User Info field; in other words, all bits in the subsequent information are 1 to the end, and does not need to consider the delimiters of the User Info field beyond the AID12 subfield.

[0070] On the other hand, if the EHT / EHT+ terminal 200 detects AID=4095, it may interpret the User Info field where AID=4095 was detected as, for example, the format of Common Info for EHT. In other words, the EHT / EHT+ terminal 200 may interpret the bit information following the AID12 subfield as extended signaling indicating the format of Common Info for EHT. Thus, in order to notify common information, the EHT trigger frame may use a part of the User Info field with a Specific AID in addition to (or instead of) the Common Info field. The special User Info field used for this purpose is also called an extended Common Info field, and the extended Common Info field with AID=4095 is also called an extended Common Info field for EHT.

[0071] Furthermore, if HE terminal 200 detects AID=4094, it does not need to perform any special processing. For example, since HE terminal 200 is instructed to start padding by the User Info field (AID=4095) that it received earlier, it is expected that it will not detect AID=4094.

[0072] On the other hand, if the EHT terminal 200 detects AID=4094, it may interpret the User Info field where AID=4094 was detected as the start of padding and stop receiving subsequent bit information. Also, if the EHT+ terminal 200 detects AID=4094, it may interpret the User Info field where AID=4094 was detected as, for example, the format of the EHT+ extended Common Info. In other words, the EHT+ terminal 200 may interpret the bit information following the AID12 subfield (AID=4094) as extended signaling indicating the format of the EHT+ Common Info.

[0073] Furthermore, the HE / EHT terminal 200 does not need to perform any special processing if it detects AID=4093. The HE / EHT terminal 200 is instructed to start padding by the User Info field (AID=4095 or 4094) it received earlier, so it is expected that it will not detect AID=4093. On the other hand, if the EHT+ terminal 200 detects AID=4093, it can interpret the User Info field in which AID=4093 was detected as the start of padding and stop receiving subsequent bit information.

[0074] Note that the contents of the Specific AID table are not limited to the example shown in Figure 10. For example, by changing the meaning of the format definition of the User Info field for Specific AID to a different meaning than in Figure 10, it is possible to flexibly specify which User Info field each of the terminals 200 with different terminal versions will process. This also applies to the Specific AID tables in other operation examples described later.

[0075] (Example of User info list placement) Figure 11 shows an example of the User info list placement in Operation Example 1-1. As shown in Figure 11, the User Info field between the HE-oriented Common Info format and the EHT-oriented Extended Common Info format (in other words, the EHT-oriented padding start indicated by AID=4095) contains the HE-oriented User Info format.

[0076] The User Info field between the Extended Common Info format for EHT and the Extended Common Info format for EHT+ (in other words, the start of EHT padding indicated by AID=4094) should contain the User Info format for EHT. Similarly, the User Info field between the Extended Common Info format for EHT+ and the start of EHT+ padding (AID=4093) should contain the User Info format for EHT+.

[0077] This configuration allows a single trigger frame to instruct the system to use a format appropriate for each terminal version across combinations of 200 terminals of different versions, thus satisfying the requirements for both backward and forward compatibility.

[0078] Furthermore, as shown in Figure 11, since the target User Info field can be distinguished for each terminal version, the processing load for terminal 200 can be reduced. In addition, since the User Info field that instructs the start of padding for each terminal version is shared with the notification of Common Info for different terminal versions, the increase in trigger frame overhead can be suppressed.

[0079] Note that the Common Info field for HE (see Figure 2, for example) is received by all HE / EHT / EHT+ terminals 200 regardless of terminal version differences. EHT / EHT+ terminals 200 may overwrite the Common Info for HE with information contained in the extended Common Info field for EHT / EHT+ (for example, information such as UL BW).

[0080] (Example 1-2) Figure 12 shows an example of a Specific AID table in Operation Example 1-2. In Figure 12, as a non-restrictive example, AID=2044 and 2043 may be newly defined as Specific AIDs. In Figure 12, "Undefined (Reserve)" means that it is not defined as a Specific AID. Specific AIDs (0, 2045, 4095) specified or defined in HE may have the same meaning in EHT / EHT+ terminal 200. On the other hand, Specific AID=2046 has a different meaning in HE terminal 200 and EHT / EHT+ terminal 200. For each generation of HE / EHT / EHT+ terminal 200, values ​​that are not defined as either AID or Specific AID may be ignored as Undefined (Reserve), but may be defined as Specific AIDs in future generations.

[0081] When HE terminal 200 detects AID=2046, it may interpret this as an unassigned RU notification and stop receiving subsequent User Info fields. Since, when interpreted as an unassigned RU notification, all subfields other than the RU Allocation subfield become reserved, HE terminal 200 may stop receiving subsequent User Info fields.

[0082] On the other hand, if the EHT / EHT+ terminal 200 detects AID=2046, it may interpret the User Info field in which AID=2046 was detected as being in the format of, for example, the EHT-specific extended Common Info field. In other words, the EHT / EHT+ terminal 200 changes the interpretation of the meaning of the User Info field in the AID12 subfield.

[0083] Furthermore, HE terminal 200 does not need to perform any special processing if it detects AID=2044 or AID=2043. Since HE terminal 200 is instructed to send an unassigned RU notification by the User Info field (AID=2046) it received earlier, it is expected that it will not detect AID=2044 or AID=2043.

[0084] On the other hand, if EHT terminal 200 detects AID=2044, it may interpret the User Info field in which AID=2044 was detected as an unassigned RU notification and stop receiving subsequent User Info fields. Also, if EHT+ terminal 200 detects AID=2044, it may interpret the User Info field in which AID=2044 was detected as being in the format of the EHT+ extended Common Info field. In other words, EHT+ terminal 200 may change the interpretation of the meaning of the User Info field itself in the AID12 subfield (AID=2044).

[0085] Furthermore, if the HE / EHT terminal 200 detects AID=2043, it does not need to perform any special processing. The HE / EHT terminal 200 is instructed to send an unassigned RU notification by the User Info field (AID=2046 or 2044) it received earlier, so it is expected that it will not detect AID=2043. On the other hand, if the EHT+ terminal 200 detects AID=2043, it can interpret the User Info field in which AID=2043 was detected as an unassigned RU notification and stop receiving subsequent User Info fields.

[0086] The above operation example 1-2 will produce the same effect as operation example 1-1.

[0087] (Example of User info list placement) Figure 13 shows an example of the User info list placement in operation example 1-2. As shown in Figure 13, the User Info field between the HE-oriented Common Info format and the EHT-oriented Extended Common Info format (in other words, the unassigned RU notification indicated by AID=2046) contains the HE-oriented User Info format.

[0088] The User Info format for EHT should be placed in the User Info field between the Extended Common Info format for EHT and the Extended Common Info format for EHT+ (in other words, the unassigned RU notification for EHT indicated by AID=2044). Similarly, the User Info format for EHT+ should be placed in the User Info field between the Extended Common Info format for EHT+ and the unassigned RU notification for EHT+ (AID=2043).

[0089] This configuration allows a single trigger frame to instruct the system to use a format appropriate for each terminal version across combinations of 200 terminals of different versions, thus satisfying the requirements for both backward and forward compatibility.

[0090] Furthermore, as shown in Figure 13, since the target User Info field can be distinguished for each terminal version, the processing load for terminal 200 can be reduced. In addition, since the User Info field that indicates unassigned RUs for each terminal version is shared with the notification of Common Info for different terminal versions, the increase in trigger frame overhead can be suppressed.

[0091] Note that the Common Info field for HE (see Figure 2, for example) is received by all HE / EHT / EHT+ terminals 200 regardless of terminal version differences. EHT / EHT+ terminals 200 may overwrite the HE-oriented extended Common Info with information contained in the EHT / EHT+-oriented extended Common Info field (for example, information such as UL BW).

[0092] (Examples of operation 1-3) Figure 14 shows an example of a Specific AID table in Operation Example 1-3. In Figure 14, as in Operation Example 1-1, AID=4094 may be newly defined as a Specific AID. However, AID=4093 does not need to be defined. In Figure 14, "Undefined (Reserve)" means that it is not defined as a Specific AID. For Specific AIDs (0, 2045, 2046) specified or defined in HE, the same meaning may apply to EHT / EHT+ terminal 200. On the other hand, Specific AID=4095 has different meanings for HE terminal 200 and EHT / EHT+ terminal 200, as in Operation Example 1-1. For each generation of terminal 200 in HE / EHT / EHT+, values ​​that are not defined as either AID or Specific AID may be ignored as Undefined (Reserve), but may be defined as Specific AIDs in future generations.

[0093] If the HE terminal 200 detects AID=4095, for example, it may interpret this as the start of padding and stop receiving subsequent bit information. On the other hand, if the EHT / EHT+ terminal 200 detects AID=4095, it may interpret the User Info field where AID=4095 was detected as, for example, the format of the extended Common Info for EHT. In other words, the EHT / EHT+ terminal 200 may interpret the bit information following the AID12 subfield as extended signaling indicating the format of the Common Info for EHT.

[0094] Furthermore, if the HE terminal 200 detects AID=4094 for the first time, for example, it does not need to perform any special processing. Since the HE terminal 200 is instructed to start padding by the User Info field (AID=4095) that it received earlier, it is expected that AID=4094 will not be detected.

[0095] On the other hand, if the EHT terminal 200 detects AID=4094 for the first time, it may interpret the User Info field where it detected AID=4094 as the start of padding and stop receiving subsequent bit information. Similarly, if the EHT+ terminal 200 detects AID=4094 for the first time, it may interpret the User Info field where it detected AID=4094 as being in the format of the EHT+ extended Common Info. In other words, the EHT+ terminal 200 may interpret the bit information following the AID12 subfield as extended signaling indicating the format of the EHT+ Common Info.

[0096] Furthermore, the HE / EHT terminal 200 does not need to perform any special processing when it detects AID=4094 for the second time. The HE / EHT terminal 200 is instructed to start padding by the User Info field it received earlier, so it is expected that it will not detect AID=4094 for the second time. On the other hand, if the EHT+ terminal 200 detects AID=4094 for the second time, it can interpret the User Info field that detected AID=4094 for the second time as indicating the start of padding, and may stop receiving subsequent bit information.

[0097] The above operation examples 1-3 achieve the same effect as operation example 1-1. Furthermore, according to operation example 1-3, since one Specific AID (e.g., 4094) is reused for different terminal versions, the number of newly introduced Specific AIDs can be reduced compared to operation examples 1-1 and 1-2. Therefore, the scalability of the system in the future can be maintained.

[0098] (Example of User info list placement) Figure 15 shows an example of the User info list placement in operation example 1-3. As shown in Figure 15, the User Info format for HE is placed in the User Info field between the Common Info format for HE and the extended Common Info format for EHT (in other words, the start of padding indicated by AID=4095).

[0099] The User Info field between the EHT-oriented extended Common Info format and the EHT+-oriented extended Common Info format (in other words, the start of EHT-oriented padding indicated by the first AID=4094) should contain the EHT-oriented User Info format. Similarly, the User Info field between the EHT+-oriented extended Common Info format and the start of EHT+-oriented padding (the second AID=4094) should contain the EHT+-oriented User Info format.

[0100] This configuration allows a single trigger frame to instruct the system to use a format appropriate for each terminal version across combinations of 200 terminals of different versions, thus satisfying the requirements for both backward and forward compatibility.

[0101] Furthermore, as shown in Figure 15, since the target User Info field can be distinguished for each terminal version, the processing load for terminal 200 can be reduced. In addition, since the User Info field that instructs the start of padding for each terminal version is shared with the notification of Common Info for different terminal versions, the increase in trigger frame overhead can be suppressed.

[0102] Note that the Common Info field for HE (see Figure 2, for example) is received by all HE / EHT / EHT+ terminals 200 regardless of terminal version differences. EHT / EHT+ terminals 200 may overwrite the HE-oriented extended Common Info with information contained in the EHT / EHT+-oriented extended Common Info field (for example, information such as UL BW).

[0103] (Supplement to examples 1-1 to 1-3) The User Info fields may be arranged in chronological order from lower (or older) terminal versions to higher (or newer) terminal versions, as shown in Figures 11, 13, and 15, for example.

[0104] In this case, for example, a Specific AID that specifies the format for a new terminal version will not mean that a User Info field for an older terminal version is placed in a position prior to the User Info field containing that Specific AID in terms of time.

[0105] This allows, for example, terminal 200 to skip the reception process (e.g., decryption) of the User Info field intended for terminal 200 with a lower terminal version than terminal 200 itself. For example, in Figure 11, the EHT / EHT+ terminal 200 can skip the reception process of the User Info field until AID=4095 is detected from Common Info.

[0106] For example, by changing the semantic meaning of the format definition of the User Info field for Specific AID, the User Info fields may be arranged in chronological order from newer to older terminal versions, or in an order independent of the terminal version.

[0107] Furthermore, two or more of the above-described operational examples 1-1 to 1-3 may be implemented in combination. In other words, the Specific AID table may be composed of entries from two or more of the three Specific AID tables illustrated in Figures 10, 12, and 14.

[0108] Furthermore, in the above-described operation examples 1-1 to 1-3, a User Info List containing a mixture of User Info fields in HE, EHT, and EHT+ formats was assumed as a non-limiting example, but the system is not limited to this. For example, as shown in Figure 16, AP100 may generate a User Info List in a configuration where there are no User Info fields in HE format, using the Specific AID table exemplified in operation example 1-1 (see Figure 10). Since the beginning of the User Info field is a Specific AID (AID=4095) which signifies the start of padding, the HE terminal 200 can stop receiving the User Info field.

[0109] Alternatively, AP100 may use, for example, a reserved field of the HE format Common Info (e.g., B63 in Figure 2) to notify terminal 200 whether the Common Info field is in HE format or EHT format.

[0110] For example, as shown in Figure 17, by setting the reserved value of the HE format to 1, the Common Info field of the EHT format is notified, the UL BW subfield is increased by 1 bit, and the UL STBC (Space-time block coding) subfield is reduced by 1 bit to apply an EHT format. This allows for increased bandwidth support in EHT, and even if STBC is not supported, beamforming can be used as a substitute, minimizing the impact on performance.

[0111] When applying the Common Info field in this EHT format, the User Info field that follows the Common Info field may be in the EHT format. In this case, as shown in Figure 18, for example, AP100 can generate a Trigger frame that does not include the Common Info field or User Info field in HE format.

[0112] This reduces the trigger frame overhead when there are no HE terminals 200 among the terminals connected to AP100, or when the number of HE terminals 200 is relatively small.

[0113] Furthermore, AP100 may use the reserved field of the UL HE-SI-A2 Reserved field, in addition to (or instead of) the reserved field of the Common Info field, to notify terminal 200 whether or not a User Info field in EHT / EHT+ format is included. For example, if EHT+ terminal 200 is instructed that the EHT+ format is not included, it can stop receiving subsequent User Info Lists (User Info fields), thereby reducing the amount of data it needs to process.

[0114] Figure 19 shows an example of the arrangement of the User info List when the reserved fields of the Common Info field and the reserved fields of the UL HE-SI-A2 Reserved field are used for format notification. For example, bit = "10" for each reserved field may indicate that User info fields in EHT format are included, but User info fields in EHT+ format are not. Alternatively, bit = "11" for each reserved field may indicate that both User info fields in EHT format and EHT+ format are included.

[0115] <Operation example of Trigger frame generation unit 106> Next, the method of arranging the User Info field by the Trigger frame generation unit 106 of AP100 will be described.

[0116] In HE, for reducing the reception processing of the terminal 200, the arrangement order of the User Info field is defined in the order of individually specified RU (AID = 1 to 2007), RA-RU (AID = 0, 2045), and unallocated RU (AID = 2046). For example, when an individually specified RU is allocated (when the notification information of the AID12 subfield matches its own AID), the terminal 200 stops the reception processing of the subsequent User Info field and generates an uplink signal.

[0117] When an individually specified RU is not allocated and an RA-RU allocation opportunity is obtained (for example, when the OBO (OFDMA Backoff Counter) becomes zero), the terminal 200 stops the reception processing of the subsequent User Info field and generates an uplink signal. And when an unallocated RU is detected, the terminal 200 stops the reception processing of the subsequent User Info field.

[0118] In this way, assuming the specified arrangement order, the terminal can reduce the reception processing by stopping the reception processing.

[0119] Here, for the User Info field for RA-RU and the User Info field for unallocated RU, similar to the User Info field for individually specified RU, in order to arrange the RU allocation subfield extended for the HE format, it is conceivable to use the same EHT / EHT+ format as in FIG. 9.

[0120] Furthermore, for example, EHT terminal 200 can gain access through RA-RU in HE and EHT formats, and EHT+ terminal 200 can gain access through RA-RU in HE, EHT, and EHT+ formats. In such cases where different versions of RA-RU formats are mixed in a single trigger frame, one or more of the following rules may be applied.

[0121] (1) The EHT / EHT+ terminal 200 will be accessible using HE format RA-RU in addition to EHT / EHT+ format RA-RU. (2) The EHT / EHT+ terminal 200 shall be able to access only RA-RUs in EHT / EHT+ format.

[0122] Under rule (1), HE terminal 200 may have an unfair opportunity to access RA-RU compared to EHT / EHT+ terminal 200, but rule (2) can improve fairness. Also, when using rule (1), fairness can be improved by lowering the priority of EHT / EHT+ terminals in the UORA (Uplink OFDMA Random Access) parameters (for example, by making the OCW (OFDMA contention window) larger than that of HE).

[0123] The following describes operational examples regarding the placement of individually designated RUs, RA-RUs, and unassigned RUs in the HE / EHT / EHT+ format.

[0124] (Example of operation 2-1) As example 2-1, Figure 20 shows an example of how to arrange individually designated RUs, RA-RUs, and unassigned RUs in the User Info List.

[0125] Figure 20 shows an example of arranging the User Info fields in order of terminal version using the Specific AID table illustrated in Figure 10. Furthermore, for each terminal version, the arrangement order is individual assigned RU, RA-RU, and unassigned RU.

[0126] The Specific AID table definition allows us to determine the HE / EHT / EHT+ format; therefore, Specific AIDs indicating RA-RU in EHT / EHT+ format can reuse the same value (0 or 2045) as HE. Similarly, Specific AIDs indicating unassigned RU in EHT / EHT+ format can reuse the same value (2046) as HE.

[0127] According to Operation Example 2-1, the same arrangement order as HE can be applied within the User Info field of each terminal version in which terminal 200 performs reception processing, thus reducing the reception processing load on terminal 200.

[0128] (Example of operation 2-2) As example 2-2, Figure 21 shows an example of how to arrange individually designated RUs, RA-RUs, and unassigned RUs in the User Info List.

[0129] In example 2-2, for instance, the Specific AID table shown in Figure 22 is used to mix different terminal versions, with the order of individually designated RUs, RA-RUs, and unassigned RUs being used. In Figure 22, "Undefined (Reserve)" means that it is not defined as a Specific AID. Specific AIDs specified or defined in HE (0, 2045, 2046, 4095) can have the same meaning in EHT / EHT+ terminal 200. On the other hand, Specific AID=2008 has different meanings in HE terminal 200 and EHT / EHT+ terminal 200. For example, Specific AID=2008 means "Individually Designated AID" for HE terminal 200 and "EHT Common Info" for EHT terminal 200. Also, in Figure 22, Specific AID=2011 has different meanings in HE / EHT terminal 200 and EHT+ terminal 200. For example, Specific AID=2011 means "Individually Designated AID" for HE / EHT terminal 200 and "EHT+ Common Info" for EHT+ terminal 200. Values ​​not defined as either AID or Specific AID for each generation of HE / EHT / EHT+ terminal 200 may be ignored as undefined (reserve), but may be defined as Specific AID in future generations.

[0130] As shown in Figure 22, for example, by adding Specific AIDs to the EHT that indicate EHT Common Info (e.g., AID=2008), RA-RU (e.g., AID=2009), and unassigned RU (e.g., AID=2010), the format of the User Info field containing that AID can be specified.

[0131] Furthermore, in EHT+, by adding new Specific AIDs that indicate EHT+ Common Info (e.g., AID=2011), RA-RU (e.g., AID=2012), and unassigned RU (e.g., AID=2013), it is possible to specify the format of the User Info field containing that AID.

[0132] Thus, according to example 2-2, the same arrangement order as HE can be applied to each of the User Info Lists (in other words, multiple User Info fields) (in other words, the arrangement order can be maintained), thus simplifying or reducing the receiving processing of terminal 200.

[0133] (Example of operation 2-3) In example 2-3, AP100 and terminal 200 may, for example, uniquely determine in advance (for example, during association) which terminal version should be received in the trigger frame based on terminal 200's capabilities. AP100 recognizes the versions supported by terminal 200 based on terminal 200's capabilities and notifies terminal 200 of the version to be received in the trigger frame.

[0134] Note that version synchronization between AP100 and terminal 200 is not limited to the time of association. For example, AP100 and terminal 200 may negotiate separately to synchronize version recognition before sending the trigger frame.

[0135] Terminal 200 performs the reception process assuming, for example, the format of the User Info field that was previously agreed upon between AP100 and Terminal 200.

[0136] As example 2-3, Figure 23 shows an example of how to arrange individually designated RUs, RA-RUs, and unassigned RUs in the User Info List. In example 2-3, for example, the Specific AID table shown in Figure 24 is used, and different versions are mixed, with the arrangement order being individually designated RUs, RA-RUs, and unassigned RUs. In Figure 24, Specific AIDs (0, 2045, 2046, 4095) specified or defined in HE can have the same meaning in EHT / EHT+ terminal 200. On the other hand, Specific AID=2008 has different meanings in HE terminal 200 and EHT / EHT+ terminal 200. For example, Specific AID=2008 means "AID for individual designation" for HE terminal 200 and "EHT Common Info" for EHT / EHT+ terminal 200. Furthermore, in Figure 24, Specific AID=2009 has different meanings for HE / EHT terminal 200 and EHT+ terminal 200. For example, Specific AID=2009 means "Individually Designated AID" for HE / EHT terminal 200 and "EHT+ Common Info" for EHT+ terminal 200.

[0137] As illustrated in Figure 24, a new Specific AID (e.g., AID=2008) is added to EHT to specify EHT Common Info. Similarly, a new Specific AID (e.g., AID=2009) is added to EHT+ to specify EHT+ Common Info. By adding these Specific AIDs, the format of the User Info field containing that AID can be specified.

[0138] Thus, as shown in example 2-3, the same arrangement order as HE can be applied to each of the User Info Lists (in other words, multiple User Info fields), thus reducing the receiving processing for terminal 200.

[0139] Furthermore, in Operation Example 2-3, by pre-determining the format that terminal 200 should receive between AP100 and terminal 200 (in other words, ensuring mutual understanding), the number of Specific AIDs to be additionally introduced can be reduced compared to the example in Figure 22. Therefore, future expandability can be maintained.

[0140] Furthermore, notification of the format of the User Info field for individual designation (SA; Scheduled access) is not required. Terminal 200 may perform the receiving process assuming the format of its own terminal version. Also, EHT / EHT+ terminal 200 can stop the receiving process early if there is no Common field.

[0141] Furthermore, if the format that terminal 200 should receive is determined in advance, a Trigger frame format corresponding to each version of HE, EHT, and EHT+ may be defined. In other words, a new Trigger frame that does not contain multiple terminal versions within a single Trigger frame may be newly defined for EHT and EHT+. AP100 may use an Aggregated-MPDU (MAC Protocol Data Unit) containing these multiple Trigger frames to instruct terminal 200 to transmit uplink.

[0142] (Example of operation 2-4) As example 2-4, Figure 25 shows an example of how to arrange individually designated RUs, RA-RUs, and unassigned RUs in the User Info List.

[0143] In example 2-4, for instance, the Specific AID table shown in Figure 26 is used, mixing different versions, and the order of placement is individual-specified RUs, RA-RUs, and unassigned RUs. Compared to the example in Figure 22, the Specific AIDs indicating the EHT Common Info field and EHT+ Common Info field are changed from 2008 to 2007 and from 2009 to 2006, respectively. In other words, in HE, a Specific AID for the EHT / EHT+ terminal 200 is selected and applied from AID=1 to 2007, which are the AIDs of individual-specified RUs. In Figure 26, "Undefined (Reserve)" means that it is not defined as a Specific AID. For Specific AIDs specified or defined in HE (0, 2045, 2046, 4095), the meaning is the same for the EHT / EHT+ terminal 200. On the other hand, Specific AID=2007 has a different meaning for the HE terminal 200 and the EHT / EHT+ terminal 200. For example, Specific AID=2007 means "Individual AID for Designation" for HE terminal 200, and "EHT Common Info" for EHT / EHT+ terminal 200. Also, in Figure 26, Specific AID=2006 has different meanings for HE / EHT terminal 200 and EHT+ terminal 200. For example, Specific AID=2006 means "Individual AID for Designation" for HE / EHT terminal 200, and "EHT+ Common Info" for EHT+ terminal 200.

[0144] In HE, in order to reduce the receiving processing for terminal 200, there is a provision that in the User Info List, User Info fields with AID=1 to 2007 used in individually designated RUs should not be placed chronologically after User Info fields with AID=2008 or higher.

[0145] When terminal 200 detects an AID of 2008 or higher, it can determine that there is no allocation of an individually designated RU, and therefore terminal 200, which does not perform RA transmission, can stop processing (for example, transmission processing).

[0146] Furthermore, by using the Specific AID table illustrated in Figure 26, the above-mentioned requirements regarding the arrangement order of User Info fields in HE can be met in versions EHT and later, thus reducing the receiving processing of EHT / EHT+ terminal 200 in the same way as HE terminal 200.

[0147] The value used for the Specific AID for EHT / EHT+ terminal 200 from AID=1 to 2007 may be determined, for example, in the standard. Alternatively, for example, the value used for the Specific AID from AID=1 to 2007 may be determined for each AP100. The determined Specific AID may then be notified from AP100 to terminal 200, for example, during negotiation, or it may be announced via beacon.

[0148] (Example of operation 2-5) Instead of defining a new Specific AID for the EHT / EHT+ terminal 200 that notifies of RA-RUs and unassigned RUs, the reserved field in the User Info field may be used to specify the format for EHT / EHT+.

[0149] An example of a User Info field for RA-RU notification in EHT / EHT+ format is shown in the lower part of Figure 27. Compared to the User Info field in HE format (same as Figure 3) shown in the upper part of Figure 27, the size of the RU allocation subfield may be expanded in the User Info field in EHT / EHT+ format (for example, expanded by 1 bit from 8 bits to 9 bits). This expansion allows for an increase in the range of supported allocation bandwidth (for example, from 160 MHz to 320 MHz).

[0150] Furthermore, in the User Info field of the EHT / EHT+ format, whether or not DCM is applied can be included in the MCS table; therefore, the UL DCM subfield (1 bit) exemplified in the upper part of Figure 27 can be deleted as exemplified in the lower part of Figure 27.

[0151] Furthermore, as shown in Figure 27, the Reserved field (1 bit) in the HE format may be replaced by the Version Info field in the EHT / EHT+ format. For example, as shown in Figure 27, a value of 0 in the Version Info field may indicate the HE format for RA-RU, and a value of 1 in the Version Info field may indicate the EHT / EHT+ format for RA-RU.

[0152] The introduction of the Version Info field eliminates the need to, for example, newly introduce unused AIDs as Specific AIDs. Therefore, the Specific AID table exemplified in Figure 26 can be reduced in size as shown in Figure 28. This reduces the consumption of unused AIDs, thus maintaining scalability for future system expansion.

[0153] Figure 29 shows an example of the User info List layout in operation example 2-5. As illustrated in Figure 29, for example, a value of 0 in the Version Info field may indicate the HE format for RA-RU, and a value of 1 in the Version Info field may indicate the EHT / EHT+ format for RA-RU.

[0154] Alternatively, an EHT / EHT+ format may be defined that follows the position and size of the subfields of the HE format. An example of such an EHT / EHT+ format is shown in the lower part of Figure 30. As shown in the lower part of Figure 30, the bits at the position of the UL DCM subfield (upper part of Figure 29), which is unnecessary in EHT / EHT+, are used as additional bits in the RU Allocation field (for example, 9 bits MSB (Most Significant Bit)).

[0155] As a result, even when the Reserved field is used as the Version Info field for the RA-RU User Info field, as described above, the position and size of the subfields can be the same as in the HE format. Terminal 200 can obtain information from each subfield assuming the HE format, regardless of the value of the Version Info field, thus simplifying the reception processing of terminal 200.

[0156] Furthermore, the EHT / EHT+ format, which follows the position and size of the subfields in the HE format described above, is not limited to use in RA-RU notifications. For example, the EHT / EHT+ format may be applied additionally or alternatively to individually designated RU notifications.

[0157] Furthermore, the EHT / EHT+ format may use the bit at the position of the Reserved field (1 bit) in the HE format as an additional bit in the SS Allocation / RA-RU Information field (for example, a 7-bit MSB).

[0158] In the example in Figure 30 (RA-RU example), the size of the SS Allocation / RA-RU Information can be reduced by 1 bit compared to the example in Figure 9 (individually designated RU example), and the HE format size (e.g., 6 bits) can be applied. This is because, in individually designated RUs, the information in the SS Allocation / RA-RU Information subfield indicates the spatial multiplexing number, and this is to accommodate the expansion of spatial multiplexing in EHT.

[0159] On the other hand, in RA-RU, the information in the SS Allocation / RA-RU Information subfield indicates the number of consecutive RA-RUs (the spatial multiplexing of RA-RUs can be fixed at 1). Although EHT has a wider allocation range compared to HE, by limiting it to a range where the number of consecutive RA-RUs can be represented by 6 bits, the Reserved field can be used as the Version Info field, as shown in the example in Figure 30.

[0160] (others) In the example described above, the EHT format and EHT+ format are notified by a User Info field to which a Specific AID is applied, but this is not limited to this. For example, the HE format and formats of EHT and later versions (e.g., the EHT format and the EHT+ format) are notified by a User Info field to which a Specific AID is applied, and for notifying formats of EHT and later versions, a subfield indicating version information may be added to the User Info field to explicitly notify the EHT and later versions.

[0161] For example, as shown in Figure 31, instead of the UL DCM subfield (1 bit) in the HE format, a Version Info subfield (1 bit) indicating either EHT or EHT+ may be provided. Furthermore, the format of other subfields (e.g., Trigger dependent Per User Info) may be changed depending on the Version Info field (whether it is EHT or EHT+). This eliminates the need to introduce unused AIDs as new Specific AIDs, thus maintaining the system's scalability for the future.

[0162] Alternatively, as shown in Figure 32, for example, the format for EHT / EHT+ may be specified using the Reserved field of Trigger-dependent User Info in addition to (or instead of) the reserved field of the User Info field.

[0163] In the example in Figure 32, the reserved field (1 bit) in the User Info field indicates whether the version is HE or a version other than HE. Then, if the reserved field in the User Info field indicates a version other than HE, the Reserved field in the Trigger dependent User Info indicates whether the version is EHT or EHT+.

[0164] The PPDU format of an uplink signal indicated by a trigger frame may be the PPDU format corresponding to the format of the User Info field in the trigger frame. In other words, an uplink signal indicated by a User Info field in HE format may be transmitted in HE TB PPDU format. Similarly, an uplink signal indicated by a User Info field in EHT format may be transmitted in EHT TB PPDU format. Furthermore, an uplink signal indicated by a User Info field in EHT+ format may be transmitted in EHT+ TB PPDU format. In this case, if the User Info field contains version information (e.g., a Version Info subfield), the Version Info field will indicate the TB PPDU format to be transmitted.

[0165] The method of transmitting multiple versions using a single trigger frame in the above-described embodiment (referred to as Method A) and the method of transmitting multiple trigger frames in defined formats for each version using Aggregated-MPDU (referred to as Method B) may be used in combination. For example, if the format that terminal 200 should receive is not determined in advance between AP100 and terminal 200 (or is not determined), Method A may be used, while if the format that terminal 200 should receive is determined in advance (or is determined), Method B may be used.

[0166] The format of the trigger frame may be changed depending on the type of Multi-AP Operation. For example, the Common Info field may include the Multi-AP (MAP) type (e.g., Coordinated Spatial Reuse (C-SR), Coordinated Orthogonal Frequency Division Multiple Access (C-OFDMA), Joint Transmissions (JT), Coordinated Beamforming (CBF)), and the User Info field may use a format appropriate to the type. In this case as well, the method of this embodiment can be applied similarly.

[0167] In the embodiments described above, the size of the User Info field in the EHT format and EHT+ format is set to the same size as the HE format in order to ensure backward compatibility, but this is not the only example.

[0168] For example, when defining a Specific AID that indicates a version boundary, as illustrated in the User Info List in Figure 11, the size of the User Info field in EHT format and EHT+ format may be different from that of HE format.

[0169] For example, the RU allocation subfield and SS Allocation subfield of the User Info field may be defined to be larger in size for the EHT and EHT+ formats, which have a wider allocation range and support a greater number of spatial multiplexes, than for the HE format. For example, the EHT / EHT+ format may include additional information to distinguish between multiple versions after EHT (EHT, EHT+, EHT++, etc.). The size and content of each subfield in the User Info field may then be changed according to the version distinguished by the additional information.

[0170] If you use values ​​for the start of padding for older versions (e.g., 4095 for HE) or unassigned RU notification (e.g., 2046 for HE) in the Specific AID, backward compatibility can be ensured because older versions of terminal 200 will stop decrypting subsequent User Info fields.

[0171] Furthermore, as illustrated in Figure 27 or Figure 30, the method of indicating version information using the Reserved (1 bit) field in the User Info field is not limited to the User Info field for RA-RUs. For example, it can be applied similarly to individually designated RUs or unassigned RUs.

[0172] Furthermore, while the examples in Figures 27 and 30 show how to distinguish between HE and EHT and later versions using one bit, additional information (called Further Version Info) can be added to distinguish between multiple versions such as EHT, EHT+, and EHT++.

[0173] For example, Figure 33 shows an example of a User Info Field with Further Version Info added. In the example in Figure 33, the Reserved field (1 bit) is used as the Version Info subfield to include information that distinguishes between HE and EHT and later versions. If an EHT or later version is specified (for example, if Version Info field = 1), the Further Version Info subfield (for example, 3 bits) may include information that distinguishes between multiple versions after EHT (EHT, EHT+, EHT++, etc.). To ensure backward compatibility and match the size of the HE format, for example, the SS Allocation / RA-RU Information subfield (6 bits in the HE format) may be reduced.

[0174] In the case of RA-RU, the number of consecutive RA-RUs indicated by this subfield may be reduced to 3 bits. For example, the number of consecutive RA-RUs may be limited to 1 to 7 and reduced to 3 bits. This is because when the RA-RU size is large, there is little need to indicate a large number of consecutive RA-RUs. Also, when reducing the RA-RU size, it can be indicated as before using the HE format.

[0175] Alternatively, the number of consecutive RA-RUs could be limited to powers of two, and the RA-RU Information subfield could be represented by the exponent of two to reduce its size. Furthermore, the number of consecutive RA-RUs could not be limited to powers of two, but rather determined within the range that can be represented by the applicable RA-RU size (e.g., 3 bits). For example, the standard could define a rule where subfield values ​​= 0, 1, 2, 3, ..., 7 represent consecutive RA-RUs = 1, 2, 8, 32, ..., 64, respectively.

[0176] Furthermore, in the case of individually designated RUs, the number of bits in the SS Allocation subfield may be reduced by limiting the spatial multiplexing of UL MU-MIMO. The limit may be a rule such as reducing the upper limit of the number of multiplexing operations that can be applied, or limiting the number of multiplexing operations that can be applied by a power of 2, as described above. Alternatively, for example, the starting stream number in spatial multiplexing included in SS Allocation may be derived by terminal 200 decrypting the RU allocation subfield from the User Info field of all individually designated RUs included in the User Info List and determining how many times the same RU allocation has been instructed. This reduces the size of the SS Allocation subfield.

[0177] In the embodiments described above, the term "...part" may be replaced with other terms such as "...circuitry," "...device," "...unit," or "...module."

[0178] This disclosure can be implemented in software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be implemented in part or in whole as an integrated circuit (LSI), and each process described in the above embodiments may be controlled in part or in whole by a single LSI or a combination of LSIs. An LSI may consist of individual chips, or it may consist of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the degree of integration, LSIs may be referred to as ICs, system LSIs, super LSIs, or ultra LSIs.

[0179] The method of integration is not limited to LSIs; it may also be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (Field Programmable Gate Arrays) that can be programmed after LSI manufacturing, or reconfigurable processors that allow for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used. This disclosure may be implemented as digital or analog processing.

[0180] Furthermore, if advancements in semiconductor technology or other derived technologies lead to the emergence of integrated circuit technologies that replace LSIs, then naturally, it would be possible to use those technologies to integrate functional blocks. The application of biotechnology, for example, is a possibility.

[0181] This disclosure is applicable to all types of devices, systems, and equipment having communication capabilities (collectively referred to as communication equipment). Communication equipment may include a radio transceiver and a processing / control circuit. A radio transceiver may include a receiver and a transmitter, or both as functions. A radio transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar. Non-exclusive examples of communication devices include telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, vehicles or mobile transport with communication capabilities (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

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

[0183] Communication includes data communication via cellular systems, wireless LAN systems, and communication satellite systems, as well as data communication using combinations of these.

[0184] Furthermore, the communication device also includes devices such as controllers and sensors that are connected to or linked to a communication device that performs the communication functions described in this disclosure. For example, this includes controllers and sensors that generate control signals and data signals used by the communication device that performs the communication functions of the communication device.

[0185] Furthermore, communication equipment includes infrastructure facilities such as base stations, access points, and any other devices, devices, and systems that communicate with or control the aforementioned non-limited types of equipment.

[0186] A base station according to one embodiment of the present disclosure may include a control circuit that associates information regarding the format of a terminal information field in a control signal that instructs the transmission of an uplink signal with unused identification information for terminal identification information assigned to a terminal that is individually specified, according to the terminal version, and a transmission circuit that transmits the control signal including the associated unused identification information.

[0187] In one embodiment of the present disclosure, the control circuit may associate the unused identification information with a format that instructs the start of padding for a first terminal version and a format that instructs information common to multiple terminals for a second terminal version.

[0188] In one embodiment of the present disclosure, the control circuit may associate the unused identification information with a format that indicates unallocated resources for a first terminal version and a format that indicates information common to multiple terminals for a second terminal version.

[0189] In one embodiment of the present disclosure, the control circuit may change the definition of the format of the terminal information field in a plurality of terminal information fields included in the control signal, according to the arrangement order of the terminal information field using the unused identification information, depending on the terminal version.

[0190] In one embodiment of the present disclosure, the control circuit may arrange a plurality of terminal information fields included in the control signal according to terminal version, and within a single terminal version, the terminal information fields may be arranged in the order of individually designated resources, random access resources, and unassigned resources.

[0191] A terminal according to one embodiment of the present disclosure may include a control circuit that determines the terminal information field to be received based on an association of information regarding the format of the terminal information field in a control signal that instructs the transmission of an uplink signal, and unused identification information assigned to a terminal to be individually specified, according to the terminal version, and a receiving circuit that performs reception processing of the determined terminal information field.

[0192] In a communication method according to one embodiment of the present disclosure, the base station may associate information regarding the format of the terminal information field in a control signal that instructs the transmission of an uplink signal with unused identification information for terminal identification information assigned to a terminal that is individually specified, according to the terminal version, and transmit the control signal that includes the associated unused identification information.

[0193] In a communication method according to one embodiment of the present disclosure, the terminal may determine the terminal information field to be received based on the association of information regarding the format of the terminal information field in the control signal that instructs the transmission of an uplink signal, and unused identification information assigned to the terminal identification information of the individually specified terminal, according to the terminal version, and perform reception processing of the determined terminal information field.

[0194] A communication device according to one embodiment of the present disclosure includes a circuit that sets a first value in the Association ID (AID) 12 subfield of a first field of a trigger frame requesting an Extremely High Throughput (EHT) Trigger-Based (TB) Physical Layer Protocol Data Unit (PPDU), and a transmitter that transmits the trigger frame, wherein the first value indicates that the first field contains information commonly used to transmit the EHT TB PPDU.

[0195] In a communication device according to one embodiment of the present disclosure, the first value may indicate that the trigger frame includes a user information field for the EHT after the first field.

[0196] In a communication device according to one embodiment of the present disclosure, the first value may be interpreted as an indication by a High Efficiency (HE) station (STA) that the first field is addressed to another STA.

[0197] In a communication device according to one embodiment of the present disclosure, the length of the first field may be equal to the length of the first user information field of the trigger frame.

[0198] A communication device according to one embodiment of the present disclosure is an EHT access point (AP), and the circuit may not set the first value in the AID12 subfield of each user field containing user-specific information addressed to an STA associated with the EHT AP.

[0199] In a communication device according to one embodiment of the present disclosure, the first field may be located immediately after the common information field in the trigger frame.

[0200] In a communication device according to one embodiment of the present disclosure, a first user information field addressed to the EHT STA may follow the first field.

[0201] In a communication device according to one embodiment of the present disclosure, the common information field of the trigger frame may include information indicating whether the first field exists in the trigger frame.

[0202] In a communication device according to one embodiment of the present disclosure, the first user information field of the trigger frame includes a resource unit (RU) allocation subfield and a first subfield, wherein the RU allocation subfield, together with the first subfield, indicates an RU for the transmission of the EHT TB PPDU.

[0203] In a communication device according to one embodiment of the present disclosure, the trigger frame may request HE TB PPDU based on the user information field of the trigger frame.

[0204] In a communication device according to one embodiment of the present disclosure, the trigger frame includes the first field, a user information field for EHT, and a user information field for HE, and the trigger frame may request the EHT TB PPDU and the HE TB PPDU.

[0205] In a communication device according to one embodiment of the present disclosure, the first field includes version information of the first field, and the version information may indicate one of either an EHT version or a post-EHT version.

[0206] In a communication device according to one embodiment of the present disclosure, the transmission of the EHT TB PPDU may be random access.

[0207] A communication method according to one embodiment of the present disclosure includes the steps of: setting a first value in the Association ID (AID) 12 subfield of a first field of a trigger frame requesting an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU); and transmitting the trigger frame, wherein the first value indicates that the first field contains information commonly used to transmit the EHT TB PPDU.

[0208] A communication device according to one embodiment of the present disclosure includes a receiver that receives a trigger frame requesting an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU), the first value of which is set in the association ID (AID) 12 subfield of the first field of the trigger frame, and a transmitter that transmits the EHT TB PPDU, wherein the first value indicates that the first field contains information commonly used to transmit the EHT TB PPDU.

[0209] In a communication device according to one embodiment of the present disclosure, the first value may indicate that the trigger frame includes a user information field for the EHT after the first field.

[0210] In a communication device according to one embodiment of the present disclosure, the first value may be interpreted as an indication by a High Efficiency (HE) station (STA) that the first field is addressed to another STA.

[0211] In a communication device according to one embodiment of the present disclosure, the length of the first field may be equal to the length of the first user information field of the trigger frame.

[0212] In a communication device according to one embodiment of the present disclosure, the trigger frame is transmitted from an EHT access point (AP), and the EHT AP may not set the first value in the AID12 subfield of each user field containing user-specific information addressed to an STA associated with the EHT AP.

[0213] In a communication device according to one embodiment of the present disclosure, the first field may be located immediately after the common information field in the trigger frame.

[0214] In a communication device according to one embodiment of the present disclosure, a first user information field addressed to the EHT STA may follow the first field.

[0215] In a communication device according to one embodiment of the present disclosure, the common information field of the trigger frame may include information indicating whether the first field exists in the trigger frame.

[0216] In a communication device according to one embodiment of the present disclosure, the first user information field of the trigger frame includes a resource unit (RU) allocation subfield and a first subfield, wherein the RU allocation subfield, together with the first subfield, indicates an RU for the transmission of the EHT TB PPDU.

[0217] In a communication device according to one embodiment of the present disclosure, the trigger frame may request HE TB PPDU based on the user information field of the trigger frame.

[0218] In a communication device according to one embodiment of the present disclosure, the trigger frame includes the first field, a user information field for EHT, and a user information field for HE, and the trigger frame may request the EHT TB PPDU and the HE TB PPDU.

[0219] In a communication device according to one embodiment of the present disclosure, the first field includes version information of the first field, and the version information may indicate one of either an EHT version or a post-EHT version.

[0220] In a communication device according to one embodiment of the present disclosure, the transmission of the EHT TB PPDU may be random access.

[0221] A communication method according to one embodiment of the present disclosure includes the steps of: receiving a trigger frame requesting an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU), where a first value is set in the Association ID (AID) 12 subfield of a first field of the trigger frame; and transmitting the EHT TB PPDU, wherein the first value indicates that the first field contains information commonly used to transmit the EHT TB PPDU.

[0222] All disclosures in the specification, drawings, and abstract contained in the Japanese application 2020-180361, filed on 28 October 2020, are incorporated herein by reference. [Industrial applicability]

[0223] One embodiment of this disclosure is useful for wireless communication systems. [Explanation of Symbols]

[0224] 11 Control Unit 12 Transmitter 21 Receiving unit 22 Control Unit 100 AP 101 Scheduling Unit 102 Terminal Information Acquisition Unit 103 Common Info generation part 104 AID Control Unit 105 User Info generation section 106 Trigger frame generation section 107 Error Correction Encoding Unit 108 Modulation section 109 Wireless Transceiver Unit 110 Demodulation Unit 111 Error Correction and Decoding Unit 200 terminals 201 Wireless Transceiver Unit 202 Demodulation Unit 203 Error Correction and Decoding Unit 204 Common Info Acquisition Department 205 AID Control Unit 206 User Info acquisition section 207 Data Generation Unit 208 Error Correction Encoding Unit 209 Modulation section

Claims

1. A receiving unit receives a trigger frame requesting the transmission of an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU), which includes a first user information field identified by an association ID (AID) 12 subfield set to a first value, and the first user information field includes common information. A control circuit for decoding the trigger frame, Equipped with, The first value indicates that, for High Efficiency (HE) terminals, the first user information field contains user-specific information for a particular STA. Terminal device.

2. The trigger frame includes a common information field, The first user information field is a special user information field that does not contain user-specific information but includes extended common information not provided in the common information field. The terminal device according to claim 1.

3. The first value mentioned above is 2007, For EHT terminals, the first user information field indicates that it includes the common information. The terminal device according to claim 1.

4. The trigger frame includes a user information field for EHT and a user information field for HE. The trigger frame requests the transmission of the EHT TB PPDU and HE TB PPDU. The terminal device according to claim 1.

5. The first user information field includes a version subfield indicating the version information of the PPDU. The terminal device according to claim 1.

6. The first value is, For the EHT terminal, it is indicated that the first user information field does not contain user-specific information. For HE terminals, the first user information field indicates that it contains the user-specific information. The terminal device according to claim 1.

7. The aforementioned common information is information that is commonly used by multiple terminals for the transmission of the EHT TB PPDU. The terminal device according to claim 1.

8. A trigger frame requesting the transmission of an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU) is received, and the trigger frame includes a first user information field identified by an association ID (AID) 12 subfield set to a first value, wherein the first user information field includes common information. The trigger frame is decoded, The first value indicates that, for High Efficiency (HE) terminals, the first user information field contains user-specific information for a particular STA. Communication method.

9. The trigger frame includes a common information field, The first user information field is a special user information field that does not contain user-specific information but includes extended common information not provided in the common information field. The communication method according to claim 8.

10. The first value mentioned above is 2007, For EHT terminals, the first user information field indicates that it includes the common information. The communication method according to claim 8.

11. The trigger frame includes a user information field for EHT and a user information field for HE. The trigger frame requests the transmission of the EHT TB PPDU and HE TB PPDU. The communication method according to claim 8.

12. The first user information field includes a version subfield indicating the version information of the PPDU. The communication method according to claim 8.

13. The first value is, For the EHT terminal, it is indicated that the first user information field does not contain user-specific information. For HE terminals, the first user information field indicates that it contains the user-specific information. The communication method according to claim 8.

14. The aforementioned common information is information that is commonly used by multiple terminals for the transmission of the EHT TB PPDU. The communication method according to claim 8.

15. A trigger frame requesting the transmission of an Extremely High Throughput (EHT) trigger-based (TB) physical layer protocol data unit (PPDU) is received, and the trigger frame includes a first user information field identified by an association ID (AID) 12 subfield with a first value set, wherein the first user information field includes common information, and processing is performed. The process of decoding the trigger frame, Control, The first value indicates that, for High Efficiency (HE) terminals, the first user information field contains user-specific information for a particular STA. Integrated circuit.

Images