Communication device and communication method

Abstract

A communication apparatus (100) includes circuitry (11) that sets a first value in an association ID (AID: Association ID) 12 subfield of a first field in a trigger frame that is a trigger frame that requests an Extremely High Throughput (EHT) trigger-based (TB: trigger-based) physical layer protocol data unit (PPDU: physical-layer protocol data unit), an EHT TB PPDU, and a transmitter (12) that transmits the trigger frame, the first value indicating that the first field contains information that is generally used to transmit the EHT TB PPDU.

Description

Technical Field

[0001] This disclosure relates to communication devices and communication methods. Background Technology

[0002] The Institute of Electrical and Electronics Engineers (IEEE) is working on the IEEE 802.11be (hereinafter referred to as "11be") standard, a successor to the IEEE 802.11ax (hereinafter also referred to as "11ax") standard, for next-generation wireless local area networks (LANs). IEEE 802.11ax is also known as "High Efficiency" (HE), and IEEE 802.11be is also known as "Extremely High Throughput" (EHT).

[0003] Existing technical documents

[0004] Non-patent literature

[0005] Non-patent document 1: IEEE P802.11ax / D7.0, 2020-09

[0006] Non-patent literature 2: 802.11-20 / 0764r2, Trigger Consideration, 2020-05

[0007] Non-patent literature 3: 802.11-20 / 0831r1, Trigger Frame for Frequency-domain A-PPDU Support, 2020-05

[0008] Non-patent literature 4: 802.11-20 / 1429r1, Enhanced Trigger Frame for EHT Support, 2020-09 Summary of the Invention

[0009] However, there is still room for research into the format of control signals that indicate uplink transmission, which can reduce the amount of receiving processing in the terminal.

[0010] The non-limiting embodiments of this disclosure help to provide, for example, communication devices and methods that can reduce the amount of receiving processing in a terminal according to the format of control signals that indicate uplink transmission.

[0011] A communication apparatus according to an embodiment of this disclosure includes: circuitry that sets a first value in a subfield of an association ID (AID) 12 of a first field in a trigger frame, the trigger frame being a trigger frame requesting an Extremely High Throughput (EHT) trigger-based physical-layer protocol data unit (PPDU), i.e., an EHT TB PPDU; and a transmitter that transmits the trigger frame, the first value indicating that the first field contains information generally used for transmitting the EHT TB PPDU.

[0012] It should be noted that these general or specific methods can be implemented by systems, devices, methods, integrated circuits, computer programs or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs and recording media.

[0013] According to one embodiment of this disclosure, the amount of receiving processing in the terminal can be reduced based on the format of the control signal indicating uplink transmission.

[0014] Further advantages and effects of one embodiment of this disclosure will be clearly presented by the specification and accompanying drawings. These advantages and / or effects are provided by various embodiments and the features described in the specification and drawings, but not all of them need to be provided to obtain one or more of the same features. Attached Figure Description

[0015] Figure 1 This is a diagram illustrating an example of the format of a trigger frame.

[0016] Figure 2 This is a diagram illustrating an example of the format of a Common info field.

[0017] Figure 3 This is a diagram illustrating an example of the format of a user info field.

[0018] Figure 4 This is an example diagram showing the value set in the AID (Association ID)12 subfield of the user information field and its description.

[0019] Figure 5 This is a block diagram representing a localized structural example of an AP (Access Point).

[0020] Figure 6This is a block diagram representing an example of the local structure of a terminal.

[0021] Figure 7 This is a block diagram representing a structural example of AP.

[0022] Figure 8 This is a block diagram representing a structural example of a terminal.

[0023] Figure 9 This diagram illustrates an example of a user information field in EHT / EHT+ format by comparing it with the HE format.

[0024] Figure 10 This is a diagram representing an example of the Specific AID table in Action Example 1-1.

[0025] Figure 11 This is a diagram representing the configuration example of the User info List in Action Example 1-1.

[0026] Figure 12 This is a diagram illustrating an example of the dedicated AID table in Action Example 1-2.

[0027] Figure 13 This is a diagram representing a configuration example of the user information list in action example 1-2.

[0028] Figure 14 This is a diagram representing an example of the dedicated AID table in action examples 1-3.

[0029] Figure 15 This is a diagram representing a configuration example of the user information list in action examples 1-3.

[0030] Figure 16 This is a diagram showing a configuration example of the user information list, representing variations of action examples 1-1 to 1-3.

[0031] Figure 17 This is a diagram representing an example of an extended common field used in EHT.

[0032] Figure 18 It means that it has been applied. Figure 17 The diagram shows an example configuration of a user information list in the case of common fields.

[0033] Figure 19 This is a diagram illustrating a configuration example of a user information list using multiple reserved fields from the general fields.

[0034] Figure 20This is a diagram illustrating an example of the RU (Resource Unit) configuration method in the user information list of action example 2-1.

[0035] Figure 21 This is a diagram illustrating an example of the RU configuration method in the user information list of action example 2-2.

[0036] Figure 22 This is a diagram representing an example of the dedicated AID table in action example 2-2.

[0037] Figure 23 This is a diagram illustrating an example of the RU configuration method in the user information list of action example 2-3.

[0038] Figure 24 This is a diagram representing an example of the dedicated AID table in action example 2-3.

[0039] Figure 25 This is a diagram illustrating an example of the RU configuration method in the user information list of action example 2-4.

[0040] Figure 26 This is a diagram representing an example of the dedicated AID table in action example 2-4.

[0041] Figure 27 This is a diagram illustrating an example of a user information field in the EHT / EHT+ format from Action Example 2-5, through a comparison with the HE format.

[0042] Figure 28 This is a diagram representing an example of the dedicated AID table in action example 2-5.

[0043] Figure 29 This is a diagram representing a configuration example of the user information list in action example 2-5.

[0044] Figure 30 This diagram illustrates a variation of the EHT / EHT+ format user information field by comparing it with the HE format.

[0045] Figure 31 This diagram illustrates a variation of the EHT / EHT+ format user information field by comparing it with the HE format.

[0046] Figure 32 This diagram illustrates a variation of the EHT / EHT+ format user information field by comparing it with the HE format.

[0047] Figure 33 This diagram illustrates a variation of the EHT / EHT+ format user information field by comparing it with the HE format. Detailed Implementation

[0048] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0049] [Implementation Method 1]

[0050] In 11ax, the introduction of uplink OFDMA (Orthogonal Frequency-Division Multiple Access) is specified. The access point (AP, also known as a "base station") sends control signals (e.g., "trigger frames") to the multiple terminals (STAs) housed within the AP, instructing the transmission of uplink OFDMA signals. Furthermore, "notification" can be replaced with "instruction".

[0051] For example, such as Figure 1 As shown, a general information field and a user information list field are defined in the trigger frame (for example, refer to Non-Patent Document 1). The general information field contains information common to multiple HE terminals (11ax terminals) multiplexed using OFDMA. Alternatively, the user information list field may contain one or more user information fields, each containing information specific to each HE terminal multiplexed using OFDMA. Figure 2 Example of a structure representing a general information field. Figure 3 An example of the structure representing a user information field (for example, see Non-Patent Document 1).

[0052] The AID12 subfield of the user information field is used, for example, to notify the terminal-specific ID, i.e., the association ID (AID), assigned to the terminal during association. In the current IEEE 802.11 standard, values ​​from 1 to 2007 are used as AIDs; values ​​other than these are unused (reserved). Hereinafter, the method of allocating frequency resources (RUs: resource units) to a specific terminal by notifying it of the AID assigned to the terminal will be referred to as "Individually Addressed RU." Furthermore, transmissions using individually addressed RUs are sometimes also referred to as "Scheduled access."

[0053] Additionally, in 11ax, for example, such as Figure 4 As shown, a specific AID (hereinafter sometimes referred to as "private AID") selected from AIDs that have never been used to individually specify a RU (hereinafter sometimes referred to as "unused AID" or "reserved AID") is used as the value of the AID12 subfield to notify RUs that are not individually specified.

[0054] For example, by setting AID=0 or AID=2045, which are dedicated AIDs, to the value of the AID12 subfield, the terminal is informed that the RU indicated by the RU allocation information in the user information field, i.e., the RU allocation subfield, is a Random Access RU (hereinafter sometimes referred to as "RA-RU") (see, for example, Non-Patent Document 1). Alternatively, by setting the dedicated AID to AID=2046, the terminal is informed that the RU indicated by the RU allocation subfield in the user information field is an unallocated RU (also referred to as "Unallocated RU" or "Unassigned RU").

[0055] It has been studied that the trigger frame of 11ax (HE) is also reused as a control signal to instruct multiple terminals to send uplink OFDMA signals in 11be (EHT) and the enhanced (beyond) 11be (hereinafter, sometimes referred to as "EHT+"), which is a further next-generation version (see, for example, Non-Patent Document 2, Non-Patent Document 3, Non-Patent Document 4).

[0056] In EHT, the following three requirements are considered for new trigger frames used in EHT. First, a single trigger frame must be able to indicate a combination of HE (Head-On) terminals, EHT terminals, and EHT+ terminals. Second, backward compatibility is required; in other words, the new trigger frame must not affect the operation of the HE terminal (e.g., the HE terminal can receive the new trigger frame). Third, forward compatibility is required; in other words, the new trigger frame must be easily extended for EHT+.

[0057] However, there is still room for research into methods for sending new trigger frames that take into account not only the aforementioned requirements but also the terminal's reception processing capacity and trigger frame overhead. Additionally, there is still room for research into the configuration order of separately designated RUs, RA-RUs, and unassigned RUs.

[0058] The following describes an efficient trigger frame transmission method that takes into account not only the requirements for new trigger frames mentioned above, but also the terminal's receiving processing load and control signal overhead.

[0059] [Structure of a wireless communication system]

[0060] The wireless communication system of Embodiment 1 includes an AP100 and a terminal 200. The AP100 and the terminal 200 are examples of wireless communication devices. In addition, the AP100 can be regarded as an example of a wireless transmitting device, and the terminal 200 can be regarded as an example of a wireless receiving device.

[0061] For example, AP100 sends a trigger frame to terminal 200, which indicates the transmission of an uplink signal (also referred to as "uplink transmission"). Terminal 200, for example, receives the trigger frame and uses the resources indicated by the trigger frame to transmit an uplink signal (e.g., an OFDMA signal) to AP100. Furthermore, the uplink signal transmitted by terminal 200 may include, for example, signals such as data signals or RA signals.

[0062] Here, terminal 200 can be any of HE, EHT, or EHT+ terminals. AP100 can, for example, send a trigger frame to multiple terminals with different versions (hereinafter sometimes referred to as "terminal versions"), and can receive uplink signals from each terminal 200. AP100 separates the uplink signals of each terminal 200 from the received signals, configured in the resources allocated to each terminal 200, and decodes them. Furthermore, AP100 can, for example, be an AP that supports EHT or EHT+ in addition to HE.

[0063] Figure 5 This is a block diagram illustrating a local structural example of AP100 in this embodiment. Figure 6 This is a block diagram illustrating a local structural example of the terminal 200 in this embodiment.

[0064] exist Figure 5 In the AP100 shown, the control unit (or control circuit) 11, for example, generates a control signal (e.g., a trigger frame) instructing the terminal 200 to send an uplink signal. The transmitting unit (or transmitting circuit) 12, for example, transmits the control signal (trigger frame).

[0065] In the processing of the control unit 11 (e.g., the generation of control signals), the following processing may be included, for example, associating information related to the format of the terminal information field in the control signal that indicates the transmission of the uplink signal with identification information that is not used as terminal identification information assigned to a separately designated terminal, depending on the terminal version.

[0066] For example, the control unit 11 can set a specific ID (private AID) in the trigger frame, selected from unused IDs that have never been used as a terminal ID assigned to a separately specified terminal. This private AID can be associated with (or may mean) a definition related to the format of the terminal information field (or, as may be called, the "user information field"). The control unit 11 can, for example, change the meaning of the private AID according to the terminal version. In other words, the interpretation of the private AID by the terminal 200 can be changed according to the terminal version.

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

[0068] The control unit (or control circuit) 22 transmits the uplink signal based on the control signal indicating that the uplink signal should be transmitted. Furthermore, the control unit 22 determines the terminal information field to be received, for example, based on the association between information related to the format of the terminal information field in the control signal indicating that the uplink signal should be transmitted and identification information corresponding to the terminal version, which is not used as terminal identification information assigned to a separately designated terminal. The receiving unit 21 performs reception processing on the determined terminal information field.

[0069] For example, the control unit 22 interprets the definition related to the format of the terminal information field based on the dedicated AID detected in the trigger frame, and the receiving unit 21 performs receiving processing corresponding to the interpretation.

[0070] [AP Structure]

[0071] Figure 7 This is a block diagram illustrating a structural example of AP100 in this embodiment. For example... Figure 7 As illustrated, AP100 may include, for example, a scheduling unit 101, a terminal information acquisition unit 102, a general information generation unit 103, an AID control unit 104, a user information generation unit 105, a trigger frame generation unit 106, an error correction coding unit 107, a modulation unit 108, a wireless transceiver unit 109, a demodulation unit 110, and an error correction decoding unit 111.

[0072] Furthermore, a portion or all of the scheduling unit 101, terminal information acquisition unit 102, general information generation unit 103, AID control unit 104, user information generation unit 105, and trigger frame generation unit 106 may constitute an access control (Media Access Control (MAC)) unit (e.g., equivalent to...). Figure 5 The control unit 11). Additionally, the wireless transceiver unit 109 may, for example, be equivalent to... Figure 5 The sending unit 12.

[0073] The scheduling unit 101 determines the radio resources of the uplink signal and the format of the user information field for each terminal 200 based, for example, on the terminal information output from the terminal information acquisition unit 102 (e.g., terminal version, radio quality of each specified band). Furthermore, the radio resources of the uplink signal may include, for example, information or parameters such as allocated band, modulation scheme and coding scheme (MCS), and target reception level. Additionally, the format of the radio resource information and user information field for the terminal 200 determined by the scheduling unit 101 is output to, for example, the user information generation unit 105 and the general information generation unit 103.

[0074] General information generation unit 103, for example, reuse Figure 2 The example HE format generates a general information field and outputs it to the trigger frame generation unit 106. The size of the general information field can be the same as that of the HE format, for example. This ensures backward compatibility. Here, AP100 can also use the reserved field of the general information to notify terminal 200 of information for EHT and / or EHT+ terminals (details will be described below).

[0075] The AID control unit 104, for example, retains information defining the private AIDs and the interpretation of user information fields in each terminal version (e.g., a table (hereinafter sometimes referred to as the "private AID table")), and outputs the private AID table to the user information generation unit 105. The private AID table can also be defined as a standard. Alternatively, a portion of the private AID table can be determined by each AP 100 and notified to the associated terminal 200.

[0076] User information generation unit 105 generates a user information list configured with one or more user information fields and outputs it to trigger frame generation unit 106. The size of the user information field can be, for example, similar to... Figure 3 The HE format shown is the same. This ensures backward compatibility. Additionally, in the user information field, besides applying... Figure 3 In addition to the illustrated HE format (or, as may be referred to as the "HE-specific User Info field"), the newly defined EHT / EHT+ format (or, as may be referred to as the "EHT-specific User Info field" or "EHT+-specific User Info field") can also be applied. Furthermore, the " / " in expressions such as "A / B" means "and / or" or "at least one of (A and B)".

[0077] The EHT format and EHT+ format can be in the following formats, for example, similar to HE, including a field (general information field) containing information common to all terminals 200 (general information) and a field (user information field) containing information specific to terminal 200 (user information).

[0078] To instruct the EHT / EHT+ terminal to indicate these formatted identification information, the user information generation unit 105 generates, for example, a user information field containing a dedicated AID and user information fields applying various formats, based on the definition of a dedicated AID table from the AID control unit 104. A portion of the dedicated AID value (e.g., 2045) can be used to represent a special user information field containing general information for EHT / EHT+ (or, may also be referred to as "EHT-specific general information" or "EHT+-specific general information"), and this special user information field can be used as a segment representing the configuration of user information fields for EHT / EHT+. The EHT / EHT+ terminal 200, for example, retains the same dedicated AID table as AP 100 and uses the definition of the dedicated AID table to interpret the format definitions of user information fields in the received trigger frames (details will be described below).

[0079] Here, the general information field using the EHT / EHT+ format may, for example, include a UL BW subfield (uplink transmission bandwidth). HE supports a maximum bandwidth of 160MHz, while EHT supports a maximum bandwidth of, for example, 320MHz. Therefore, the EHT / EHT+ terminal 200 can obtain the uplink transmission bandwidth not only from the UL BW subfield contained in the general information field of the HE format (or, alternatively, from the UL BW subfield contained in the general information field of the HE format), but also from the UL BW subfield contained in the general information field of the user information field. Furthermore, the term "obtain" can be interchanged with terms such as "recognize," "master," "identify," or "confirm."

[0080] Furthermore, compared to the HE format, the user information field using the EHT / EHT+ format can also modify the RU allocation subfield (uplink transmission band location and bandwidth information). For example, since the user information field sent to the EHT / EHT+ terminal 200 indicates a maximum range of 320MHz, the RU allocation subfield in the EHT / EHT+ format can be set to a larger size than the RU allocation subfield in the HE format (8 bits).

[0081] Trigger frame generation unit 106, for example, according to Figure 1The illustrated format appends a MAC header, padding, and FCS (frame check sequence) to the set of general information fields from general information generation unit 103 and user information lists (multiple user information fields) from user information generation unit 105, and generates a trigger frame. The generated trigger frame is output to error correction coding unit 107, for example.

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

[0083] The modulation unit 108, for example, modulates the signal input from the error correction coding unit 107 and outputs the modulated data signal to the wireless transceiver unit 109. Furthermore, when the modulated data signal is an Orthogonal Frequency Division Multiplexing (OFDM) signal, the AP100 (e.g., the modulation unit 108) can map the modulated signal to a specified 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.

[0084] The wireless transceiver unit 109 performs wireless transmission processing on the modulated signal output from the modulation unit 108, such as D / A (digital-to-analog) conversion and up-conversion to the carrier frequency, and transmits the processed signal to the terminal 200 via an antenna. Additionally, the wireless transceiver unit 109 receives signals transmitted from the terminal 200 via an antenna, performs wireless reception processing on the received signals, such as down-conversion to baseband and A / D (analog-to-digital) conversion, and outputs the processed signal to the demodulation unit 110.

[0085] The demodulation unit 110 performs demodulation processing on the input signal, for example, and outputs the obtained signal to the error correction decoding unit 111. In addition, when the input signal is an OFDM signal, the AP100 (for example, the demodulation unit 110) can apply CP removal processing and Fast Fourier Transform (FFT) processing to the OFDM signal.

[0086] 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 aforementioned terminal information, the terminal information is output to the terminal information acquisition unit 102, for example.

[0087] [Terminal Structure]

[0088] Figure 8 This is a block diagram illustrating a structural example of the terminal 200 in this embodiment. Figure 8 The terminal 200 shown may include, for example, a wireless transceiver unit 201, a demodulation unit 202, an error correction and decoding unit 203, a general information acquisition unit 204, an AID control unit 205, a user information acquisition unit 206, a data generation unit 207, an error correction coding unit 208, and a modulation unit 209.

[0089] Furthermore, a portion or all of the General Information Acquisition Unit 204, AID Control Unit 205, User Information Acquisition Unit 206, and Data Generation Unit 207 may constitute an Access Control (MAC) unit (e.g., equivalent to...). Figure 6 The control unit 22). Additionally, the wireless transceiver unit 201 may, for example, be equivalent to... Figure 6 The receiving unit 21.

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

[0091] The demodulation unit 202, for example, demodulates the received signal input from the wireless transceiver unit 201 and outputs the demodulated signal to the error correction decoding unit 203. Furthermore, when the input signal is an OFDM signal, the terminal 200 (e.g., the demodulation unit 202) may apply CP removal processing and FFT processing to the OFDM signal.

[0092] Error correction decoding unit 203, for example, decodes the demodulated signal input from demodulation unit 202 and outputs the decoded signal as a received data signal. Additionally, error correction decoding unit 203, for example, outputs the trigger frame from the received data signal to general information acquisition unit 204 and user information acquisition unit 206.

[0093] The general information acquisition unit 204 extracts information from the general information field of the trigger frame output by the error correction decoding unit 203, for example, to obtain terminal general information for generating the uplink signal (e.g., information such as the type of data transmitted or the duration of the uplink signal). The obtained terminal general information is output to the user information acquisition unit 206, for example.

[0094] The AID control unit 205 can operate in the same way as the AID control unit 104 in AP100. For example, the AID control unit 205 can output a dedicated AID table that defines the dedicated AID and the interpretation of user information fields in each terminal version to the user information acquisition unit 206.

[0095] The user information acquisition unit 206, for example, extracts a list of user information (multiple user information fields) from the trigger frame output by the general information acquisition unit 204. While using a dedicated AID table from the AID control unit 205 to determine the format of the user information fields, it performs user information field reception processing according to the configuration order. If it is determined that there is a separately designated RU allocation or an RA-RU allocation, the user information acquisition unit 206 outputs terminal general information and terminal specific information for generating data to the data generation unit 207.

[0096] For example, the user information acquisition unit 206 can compare the AID of the terminal 200 assigned by AP100 during association with the AID contained in the AID12 subfield of the user information field, and if these AIDs match, determine that the individually designated RU was assigned by AP100. Based on this determination, the terminal 200, for example, performs reception processing on the remaining terminal-specific information (e.g., RU configuration information, MCS, spatial multiplexing information, uplink target power information, etc.) used to generate uplink signals, based on the format of the user information field.

[0097] Even in cases of AID inconsistency, such as when an access opportunity is obtained using an AID representing a RA-RU (e.g., 0 or 2045), terminal 200 can still receive and process the remaining terminal-specific information (e.g., RU configuration information, MCS, uplink target power information, etc.) required to generate an uplink random access signal based on a prescribed format. Furthermore, for example, if an AID indicating an unassigned RU is detected, terminal 200 can stop receiving subsequent user information fields. Additionally, for example, if an AID indicating the start of padding is detected, terminal 200 can stop receiving subsequent sub-fields.

[0098] The data generation unit 207 generates data of a specified category and size based on terminal general information and terminal specific information from the user information acquisition unit 206, and outputs it to the error correction coding unit 208.

[0099] For example, the error correction coding unit 208 takes the data signal from the data generation unit 207 as input, performs error correction coding on the transmitted data based on the terminal general information and terminal specific information from the user information acquisition unit 206, and outputs the coded signal to the modulation unit 209.

[0100] The modulation unit 209 modulates the signal input from the error correction coding unit 208, and outputs the modulated signal to the wireless transceiver unit 201 based on terminal general information and terminal specific information from the user information acquisition unit 206. Furthermore, when the modulated signal is an OFDM signal, the terminal 200 (e.g., the modulation unit 209) can, for example, map the modulated signal to frequency resources, perform IFFT processing, and add a CP, thereby forming an OFDM signal.

[0101] The wireless transceiver 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 processed signal from the antenna.

[0102] <Operations of AID Control Unit 205 and User Information Acquisition Unit 206>

[0103] The following describes an example of a dedicated AID table generated in the AID control unit 205 of the terminal 200, and an example of a method for determining the format of user information fields using the dedicated AID table performed in the user information acquisition unit 206.

[0104] The dedicated AID table maintained by the AID control unit 205, for example, represents the definition of the format of the terminal information field associated with the "dedicated AID" depending on the terminal version such as HE, EHT, or EHT+. The "dedicated AID" is a specific ID selected from unused IDs that have never been used as a terminal ID assigned to a separately designated terminal 200.

[0105] By using a dedicated AID table, in addition to achieving the three requirements mentioned above (e.g., being able to use a trigger frame to indicate a combination of HE, EHT, and EHT+ terminals, ensuring backward compatibility, and ensuring forward compatibility), it is also possible to reduce the amount of receiving processing by terminal 200 and reduce the overhead of trigger frames.

[0106] Furthermore, by altering EHT or EHT+, Figure 4 The illustrated meanings of the dedicated AIDs (0, 2045, 2046, 4095) defined for HE demonstrate that no new dedicated AIDs need to be imported, thus reducing the consumption of unused AIDs. Therefore, scalability for future systems can be maintained.

[0107] Here, through comparison with the HE format, in Figure 9 The following paragraph represents an example of a user information field in EHT / EHT+ format. (and...) Figure 9 The HE format shown in the upper paragraph (and) Figure 3Compared to the user information field in the same format, the size of the RU allocation subfield can be expanded in the EHT / EHT+ format user information field (e.g., from 8 bits to 9 bits). This expansion allows for an increase in the range of supported allocation band fields (e.g., from 160MHz to 320MHz).

[0108] Additionally, in the EHT, the MCS table can include whether or not DCM (Dual Subcarrier Modulation) is applied. Therefore, as... Figure 9 The following example can be deleted. Figure 9 The UL DCM subfield (1 bit) is illustrated in the previous paragraph. Additionally, in EHT+, the maximum supported number of SS (Spatial stream) can be extended (e.g., from 8 to 16). Therefore, as... Figure 9 As illustrated in the following paragraph, the size of the SS allocation / RA-RU information subfield can be expanded (increased) by 1 bit from 6 bits to 7 bits. Additionally, in Figure 9 The following paragraph can be deleted. Figure 9 The previous paragraph illustrates the reserved space (1 bit). This ensures that the size of the user information field matches the size of the HE format, thereby guaranteeing backward compatibility.

[0109] Next, a non-limiting example is described below, which, depending on the terminal version, changes the relationship between the definition of the private AID and the user information field format containing the private AID (or can be replaced with "association" or "meaning").

[0110] (Action Example 1-1)

[0111] Figure 10 This represents an example of the dedicated AID table in action example 1-1. Figure 10 In this context, as a non-restrictive example, AID = 4094 and 4093 can be newly defined as dedicated AIDs. Figure 10 In this context, "undefined (reserved)" refers to a value that is not defined as a dedicated AID. The dedicated AIDs (0, 2045, 2046) specified or defined in HE can have the same meaning for EHT / EHT+ terminal 200. However, the meaning of dedicated AID = 4095 differs between HE terminal 200 and EHT / EHT+ terminal 200. For each generation of HE / EHT / EHT+ terminal 200, a value that is neither defined as an AID nor a dedicated AID can be ignored as undefined (reserved), but it can also be further defined as a dedicated AID in a future generation.

[0112] If AID=4095 is detected, HE terminal 200 can interpret this as the start of padding based on HE's rules and stop receiving subsequent bit information. When interpreted as the start of padding, HE terminal 200 can assume that information after the AID12 subfield of the user information field does not exist; in other words, it assumes that all bits in the subsequent information are 1 until the end, and that the user information field segment is not considered after the AID12 subfield.

[0113] On the other hand, when AID=4095 is detected, the EHT / EHT+ terminal 200 can interpret the detected user information field of AID=4095 as being in the format of general information for EHT. In other words, the EHT / EHT+ terminal 200 can interpret the bit information following the AID12 subfield as extended signaling in the format of general information for EHT. Thus, in order to notify the general information, the trigger frame for EHT can use a portion of the user information field with a special AID, in addition to using the general information field (or, instead of using the general information field). The special user information field used for this purpose is also called the "extended general information field," and the extended general information field with AID=4095 is also called the "extended general information field for EHT."

[0114] Furthermore, if AID=4094 is detected, the HE terminal 200 does not need to perform any special processing. For example, since the filling process was initiated by the previously received user information field (AID=4095), it is assumed that the HE terminal 200 will not detect AID=4094.

[0115] On the other hand, if AID=4094 is detected, the EHT terminal 200 can interpret the user information field with AID=4094 as the start of padding and stop receiving subsequent bit information. Furthermore, if AID=4094 is detected, the EHT+ terminal 200 can interpret the user information field with AID=4094 as being in the format of extended general information for EHT+. In other words, the EHT+ terminal 200 can interpret the bit information following the AID12 subfield (AID=4094) as extended signaling in the format of general information for EHT+.

[0116] Furthermore, if AID=4093 is detected, the HE / EHT terminal 200 does not require special processing. Since the previously received user information field (AID=4095 or 4094) indicates the start of padding, it is assumed that the HE / EHT terminal 200 does not detect AID=4093. On the other hand, if AID=4093 is detected, the EHT+ terminal 200 can interpret this as the detection of AID=4093 as the start of padding and stop receiving subsequent bit information.

[0117] Furthermore, the contents of the dedicated AID table are not limited to... Figure 10 The example shown. For instance, by changing the meaning of the format definition for the user information field of a dedicated AID to be consistent with... Figure 10 The different meanings allow for flexible indication of user information fields that are received and processed by terminals 200 with different terminal versions. The same applies to the dedicated AID table in other action examples described below.

[0118] (Example of user information list configuration)

[0119] Figure 11 This represents a configuration example of the user information list in action example 1-1. For example... Figure 11 As shown, the user information format for HE is configured in the user information field between the general information format for HE and the extended general information format for EHT (in other words, the start of padding for EHT represented by AID=4095).

[0120] Configure the user information format for EHT in the user information field between the extended general information format for EHT and the extended general information format for EHT+ (in other words, the padding start for EHT represented by AID=4094). Similarly, configure the user information format for EHT+ in the user information field between the extended general information format for EHT+ and the padding start for EHT+ (AID=4093).

[0121] With this configuration, a single trigger frame can be used to indicate the format corresponding to the terminal version for different versions of the terminal 200, thus satisfying the requirements for backward compatibility and forward compatibility.

[0122] In addition, such as Figure 11 As shown, the user information field of the receiving object can be distinguished according to each terminal version, thus reducing the receiving processing load of the terminal 200. In addition, the user information field indicating the start of filling according to each terminal version also serves as general information for notifying different terminal versions, thus suppressing the increase in trigger frame overhead.

[0123] Furthermore, regardless of the terminal version, HE / EHT / EHT+ terminals 200 all receive the common information fields used for HE (e.g., refer to...). Figure 2 The EHT / EHT+ terminal 200 can also override the general information used for HE with information contained in the extended general information field for EHT / EHT+ (e.g., information such as UL BW).

[0124] (Action Examples 1-2)

[0125] Figure 12 This represents an example of the dedicated AID table in action example 1-2. Figure 12 In this context, as a non-restrictive example, AID = 2044 and 2043 can be newly defined as dedicated AIDs. Figure 12 In this context, "undefined (reserved)" refers to a value that is not defined as a dedicated AID. The dedicated AIDs (0, 2045, 4095) specified or defined in HE can have the same meaning for EHT / EHT+ terminal 200. However, the meaning of dedicated AID = 2046 differs between HE terminal 200 and EHT / EHT+ terminal 200. For each generation of HE / EHT / EHT+ terminal 200, a value that is neither defined as an AID nor a dedicated AID can be ignored as undefined (reserved), but it can also be further defined as a dedicated AID in a future generation.

[0126] If AID=2046 is detected, the HE terminal 200 can interpret this as a RU notification not being allocated and stop receiving and processing the user information field thereafter. In the case of a RU notification not being allocated, all subfields except the RU allocation subfield become reserved; therefore, the HE terminal 200 can stop receiving and processing the user information field thereafter.

[0127] On the other hand, when AID=2046 is detected, the EHT / EHT+ terminal 200 can interpret the detected user information field as having the format of an extended general information field used in EHT, for example. In other words, the EHT / EHT+ terminal 200 changes the interpretation of the user information field meaning of the AID12 subfield.

[0128] Furthermore, if AID=2044 or AID=2043 is detected, the HE terminal 200 does not need to perform any special processing. Since the previously received user information field (AID=2046) indicates that no RU notification has been allocated, it is assumed that the HE terminal 200 will not detect AID=2044 or AID=2043.

[0129] On the other hand, if AID=2044 is detected, the EHT terminal 200 can interpret it as a non-assigned RU notification for the user information field and stop receiving and processing the user information field thereafter. Furthermore, if AID=2044 is detected, the EHT+ terminal 200 can interpret it as the format of the extended general information field used in EHT+. In other words, the EHT+ terminal 200 can change the interpretation of the meaning of the user information field itself within the AID12 subfield (AID=2044).

[0130] Furthermore, if AID=2043 is detected, the HE / EHT terminal 200 does not require special processing. Since the previously received user information field (AID=2046 or 2044) indicates a no-RU notification, it is assumed that the HE / EHT terminal 200 will not detect AID=2043. On the other hand, if AID=2043 is detected, the EHT+ terminal 200 can interpret the detected user information field as a no-RU notification and cease receiving and processing subsequent user information fields.

[0131] The same effect as action example 1-1 can be achieved through action example 1-2 above.

[0132] (Example of user information list configuration)

[0133] Figure 13 This represents a configuration example of the user information list in action example 1-2. For example... Figure 13 As shown, the user information format for HE is configured in the user information field between the general information format for HE and the extended general information format for EHT (in other words, the unassigned RU notification represented by AID=2046).

[0134] Configure the user information format for EHT in the user information field between the extended general information format for EHT and the extended general information format for EHT+ (in other words, the unassigned RU notification for EHT represented by AID=2044). Similarly, configure the user information format for EHT+ in the user information field between the extended general information format for EHT+ and the unassigned RU notification for EHT+ (AID=2043).

[0135] With this configuration, a single trigger frame can be used to indicate the format corresponding to the terminal version for different versions of the terminal 200, thus satisfying the requirements for backward compatibility and forward compatibility.

[0136] In addition, such as Figure 13As shown, the user information field of the receiving object can be distinguished according to each terminal version, thus reducing the receiving processing load of terminal 200. In addition, the user information field indicating the unassigned RU according to each terminal version can also be used to notify general information of different terminal versions, thus suppressing the increase in trigger frame overhead.

[0137] Furthermore, regardless of the terminal version, HE / EHT / EHT+ terminals 200 all receive the common information fields used for HE (e.g., refer to...). Figure 2 The EHT / EHT+ terminal 200 can also override the extended general information for HE with information contained in the extended general information field for EHT / EHT+ (e.g., information such as UL BW).

[0138] (Action Examples 1-3)

[0139] Figure 14 This represents an example of the dedicated AID table in action examples 1-3. Figure 14 Similar to action example 1-1, AID = 4094 can be newly defined as a dedicated AID. However, it is not necessary to define AID = 4093. Figure 14 In this context, "undefined (reserved)" refers to a value that is not defined as a dedicated AID. The dedicated AIDs (0, 2045, 2046) specified or defined in HE can have the same meaning for EHT / EHT+ terminal 200. However, similar to Operation Example 1-1, the meaning of dedicated AID = 4095 differs between HE terminal 200 and EHT / EHT+ terminal 200. For each generation of HE / EHT / EHT+ terminal 200, a value that is neither defined as an AID nor a dedicated AID can be ignored as undefined (reserved), but it can also be further defined as a dedicated AID in a future generation.

[0140] For example, if AID=4095 is detected, the HE terminal 200 can interpret this as the start of padding and stop receiving subsequent bit information. On the other hand, if AID=4095 is detected, the EHT / EHT+ terminal 200 can interpret the user information field containing AID=4095 as, for example, the format of extended general information for EHT. In other words, the EHT / EHT+ terminal 200 can interpret the bit information following the AID12 subfield as extended signaling representing a format of general information for EHT.

[0141] Furthermore, for example, if AID=4094 is detected for the first time, the HE terminal 200 does not need to perform any special processing. Since the filling process was initiated by the previously received user information field (AID=4095), it is assumed that the HE terminal 200 will not detect AID=4094.

[0142] On the other hand, upon detecting the first AID=4094, the EHT terminal 200 can interpret this as the detection of a padding start in the user information field and stop receiving subsequent bit information. Furthermore, upon detecting the first AID=4094, the EHT+ terminal 200 can interpret this as the user information field being in the format of extended general information for EHT+. In other words, the EHT+ terminal 200 can interpret the bit information following the AID12 subfield as extended signaling representing the format of general information for EHT+.

[0143] Furthermore, if a second AID=4094 is detected, the HE / EHT terminal 200 does not require special processing. Since the previously received user information field indicates the start of padding, it is assumed that the HE / EHT terminal 200 will not detect a second AID=4094. On the other hand, if a second AID=4094 is detected, the EHT+ terminal 200 can interpret the detection as the start of padding and stop receiving subsequent bit information.

[0144] The same effect as in Action Example 1-1 can be achieved through Action Example 1-3 above. Furthermore, according to Action Example 1-3, because a dedicated AID (e.g., 4094) is used for different terminal versions, the number of newly imported dedicated AIDs can be reduced compared to Action Examples 1-1 and 1-2. Therefore, the scalability of the system can be maintained in the future.

[0145] (Example of user information list configuration)

[0146] Figure 15 This represents a configuration example of the user information list in action examples 1-3. For example... Figure 15 As shown, the user information format for HE is configured in the user information field between the general information format for HE and the extended general information format for EHT (in other words, the padding start indicated by AID=4095).

[0147] In the user information field between the extended general information format for EHT and the extended general information format for EHT+ (in other words, the start of padding for EHT represented by the first AID=4094), configure the user information format for EHT. Similarly, in the user information field between the extended general information format for EHT+ and the start of padding for EHT+ (the second AID=4094), configure the user information format for EHT+.

[0148] With this configuration, a single trigger frame can be used to indicate the format corresponding to the terminal version for different versions of the terminal 200, thus satisfying the requirements for backward compatibility and forward compatibility.

[0149] In addition, such as Figure 15 As shown, the user information field of the receiving object can be distinguished according to each terminal version, thus reducing the receiving processing load of the terminal 200. In addition, the user information field indicating the start of filling according to each terminal version also serves as general information for notifying different terminal versions, thus suppressing the increase in trigger frame overhead.

[0150] Furthermore, regardless of the terminal version, HE / EHT / EHT+ terminals 200 all receive the common information fields used for HE (e.g., refer to...). Figure 2 The EHT / EHT+ terminal 200 can also override the extended general information for HE with information contained in the extended general information field for EHT / EHT+ (e.g., information such as UL BW).

[0151] (Supplement to Action Examples 1-1 to 1-3)

[0152] User information fields can be in the time direction, for example, such as Figure 11 , Figure 13 , Figure 15 As shown, configure according to the terminal version from low (or, old) to high (or, new).

[0153] In this case, for example, a special AID indicating the format for a new terminal version can be given the following meaning: it is assigned to a position earlier in time than the user information field containing the special AID, and no meaning is set for the user information field for the old terminal version.

[0154] Thus, for example, terminal 200 can skip the receiving process (e.g., decoding) of user information fields for terminals with a lower version than itself. For example, in Figure 11 In this process, the EHT / EHT+ terminal 200 can skip the reception processing of the user information field up to when AID=4095 is detected from the general information.

[0155] Furthermore, for example, by changing the meaning of the format definition for the user information field of the dedicated AID, the user information field can be configured in the time direction according to the terminal version from newest to oldest, or in an order that does not depend on the terminal version.

[0156] Alternatively, two or more of the action examples 1-1 to 1-3 above can be performed in combination. In other words, it is also possible to combine... Figure 10 , Figure 12 and Figure 14 The three examples illustrate how entries from two or more private AID tables can be combined to form a private AID table.

[0157] Furthermore, while the examples 1-1 to 1-3 above, presented as non-limiting examples, envisioned a user information list containing user information fields in various formats such as HE, EHT, and EHT+, the scope is not limited to this. For example, such as Figure 16 As shown, AP100 can also use Action Example 1-1 (refer to...) Figure 10 The dedicated AID table illustrated in the example generates a list of user information using a structure that does not have a user information field in HE format. Because the user information field is preceded by a dedicated AID (AID=4095) indicating the start of filling, the HE terminal 200 can stop receiving and processing the user information field.

[0158] Alternatively, AP100 can also use reserved fields for general information in HE format (e.g.) Figure 2 (B63) Inform terminal 200 whether it is a general information field in HE format or a general information field in EHT format.

[0159] For example, such as Figure 17 As shown, by setting the reserved value of the HE format to 1, the application is notified to the general information field of the EHT format that the UL BW subfield has been increased by 1 bit and the UL STBC (Space-time block coding) subfield has been reduced by 1 bit in the EHT format. This allows, for example, to accommodate increases in the bandwidth supported in EHT. Furthermore, even if STBC is not supported, the impact on performance can be reduced by using beamforming instead.

[0160] When the general information field uses this EHT format, the format used for EHT can be applied to the user information field that follows the general information field. In this case, for example, as... Figure 18As shown, AP100 can generate trigger frames that do not contain the general information field or user information field in HE format.

[0161] Therefore, when there are no HE terminals 200 in the terminal group connected to AP100, or when the number of HE terminals 200 is relatively small, the overhead of trigger frames can be reduced.

[0162] Alternatively, AP100 can use the UL HE-SI-A2 reserved field, in addition to (or instead of) the reserved field for general information fields, to notify terminal 200 whether user information fields in EHT / EHT+ format are included. For example, if instructed not to include EHT+ format, EHT+ terminal 200 can stop receiving subsequent user information lists (user information fields), thus reducing the amount of data processing.

[0163] Figure 19 This example demonstrates a configuration for a user information list where reserved fields for the General Information field and the UL HE-SI-A2 reserved field are used in a notification format. For instance, you could indicate that each reserved field's bit is "10" to include EHT format user information fields but exclude EHT+ format user information fields. Alternatively, you could indicate that each reserved field's bit is "11" to include both EHT and EHT+ format user information fields.

[0164] <Example of the action of trigger frame generation unit 106>

[0165] Next, the configuration method of the user information field of the trigger frame generation unit 106 of AP100 will be explained.

[0166] In HE, to reduce the reception processing of terminal 200, the configuration order of user information fields is specified according to the order of individually designated RU (AID=1~2007), RA-RU (AID=0, 2045), and unassigned RU (AID=2046). For example, when an individually designated RU is assigned (when the notification information in the AID12 subfield is consistent with its own AID), terminal 200 stops the subsequent reception processing of user information fields and generates an uplink signal.

[0167] If a terminal 200 receives an RA-RU allocation opportunity without being assigned a separately designated RU (e.g., when the OBO (OFDMA Backoff Counter) becomes zero), it stops receiving user information fields and generates an uplink signal. Furthermore, if an unassigned RU is detected, the terminal 200 stops receiving user information fields.

[0168] In this way, the terminal can reduce reception processing by pre-defined configuration sequence and stopping reception processing.

[0169] Here, regarding the user information fields for RA-RU and unassigned RU, similarly to the user information fields for separately specified RU, in order to configure the RU allocation subfield after the HE format extension, it is advisable to use the same... Figure 9 Same EHT / EHT+ format.

[0170] Additionally, for example, EHT terminal 200 obtains access opportunities through RA-RU in HE and EHT formats, while EHT+ terminal 200 obtains RA-RU access opportunities through HE, EHT, and EHT+ formats. Thus, when different versions of RA-RU formats are mixed in a single trigger frame, one or more of the following rules can be applied.

[0171] (1) In addition to accessing the EHT / EHT+ terminal 200 via RA-RU in EHT / EHT+ format, it can also access the EHT / EHT+ terminal via RA-RU in HE format.

[0172] (2) The EHT / EHT+ terminal 200 is limited to access via RA-RU in EHT / EHT+ format.

[0173] In rule (1), the access opportunity for RA-RU may be unfair compared to that of EHT / EHT+ terminal 200, but fairness can be improved by rule (2). In addition, when using rule (1), fairness can be improved by using the UORA (Uplink OFDMA Random Access) parameter to reduce the priority of EHT / EHT+ terminal (e.g., making OCW (OFDMA contention window) greater than HE).

[0174] The following describes action examples related to the configuration methods for individually specified RUs, RA-RUs, and unassigned RUs in HE / EHT / EHT+ format.

[0175] (Action Example 2-1)

[0176] As an example of action 2-1, Figure 20 This represents an example of a configuration method for individually specifying RUs, RA-RUs, and unassigned RUs in the user information list.

[0177] exist Figure 20 It is shown that using Figure 10 The example shown illustrates a dedicated AID table with user information fields configured according to the terminal version order. Furthermore, for each terminal version, a configuration order is adopted where RU, RA-RU, and unassigned RU are specified individually.

[0178] Because the HE / EHT / EHT+ format can be determined based on the definition of the dedicated AID table, the dedicated AID representing an EHT / EHT+ format RA-RU can reuse the same value as HE (0 or 2045). Similarly, the dedicated AID representing an unassigned RU in EHT / EHT+ format can reuse the same value as HE (2046).

[0179] According to Action Example 2-1, the same configuration order as HE can be applied to the user information field of each terminal version that is receiving and processing in terminal 200, thereby reducing the receiving and processing of terminal 200.

[0180] (Action Example 2-2)

[0181] As an example of action 2-2, Figure 21 This represents an example of a configuration method for individually specifying RUs, RA-RUs, and unassigned RUs in the user information list.

[0182] In action example 2-2, for example using Figure 22 The dedicated AID table shown contains data from different terminal versions and is configured in the order of individually specifying RU, RA-RU, and unassigned RU. Figure 22 In this context, "undefined (reserved)" means that it has not been defined as a dedicated AID. The dedicated AIDs (0, 2045, 2046, 4095) specified or defined in HE can have the same meaning for EHT / EHT+ terminal 200. On the other hand, the meaning of dedicated AID = 2008 differs between HE terminal 200 and EHT / EHT+ terminal 200. For example, dedicated AID = 2008 means "specifically designated AID" for HE terminal 200, but means "EHT general information" for EHT terminal 200. Furthermore, in... Figure 22In this context, the meaning of Dedicated AID=2011 differs between HE / EHT terminal 200 and EHT+ terminal 200. For example, for HE / EHT terminal 200, Dedicated AID=2011 means "specifically designated AID," while for EHT+ terminal 200, it means "EHT+ general information." For each generation of HE / EHT / EHT+ terminal 200, values ​​that are neither defined as AID nor Dedicated AID can be ignored as undefined (reserved), but they can also be further defined as Dedicated AIDs in future generations.

[0183] like Figure 22 As shown, for example, for EHT, by adding a dedicated AID that indicates general EHT information (e.g., AID=2008), a dedicated AID that indicates RA-RU (e.g., AID=2009), and a dedicated AID that indicates unassigned RU (e.g., AID=2010), it is possible to indicate the format of the user information field containing the AID.

[0184] In addition, for EHT+, the format of the user information field containing the AID can be indicated by adding a dedicated AID that indicates general EHT+ information (e.g., AID=2011), a dedicated AID that indicates RA-RU (e.g., AID=2012), and a dedicated AID that indicates an unassigned RU (e.g., AID=2013).

[0185] Thus, according to Action Example 2-2, the same configuration order as HE can be applied to the user information list (in other words, multiple user information fields) respectively (in other words, the configuration order can be maintained), thereby simplifying or reducing the receiving processing of terminal 200.

[0186] (Action Example 2-3)

[0187] In Action Examples 2-3, AP100 and terminal 200 can uniquely determine, for example in advance (e.g., during association), based on the capabilities of terminal 200, which terminal version should be received using the trigger frame. AP100 recognizes the versions supported by terminal 200 based on its capabilities and notifies terminal 200 of the version to be received using the trigger frame.

[0188] Furthermore, ensuring version consistency between AP100 and terminal 200 is not limited to the associated scenario. For example, AP100 and terminal 200 can also negotiate separately to achieve version consistency before sending the trigger frame.

[0189] Terminal 200 performs receiving processing, for example, by pre-conceiving the format of the user information field determined between AP100 and terminal 200.

[0190] As examples of actions 2-3, Figure 23 This is an example of a configuration method that specifies a single RU, RA-RU, or unassigned RU in the user information list. In action example 2-3, for example, using... Figure 24 The dedicated AID table shown contains different versions and is configured in the order of individually specifying RU, RA-RU, and unassigned RU. Figure 24 In HE, the specific AIDs (0, 2045, 2046, 4095) specified or defined can have the same meaning for EHT / EHT+ terminal 200. On the other hand, the meaning of specific AID = 2008 differs between HE terminal 200 and EHT / EHT+ terminal 200. For example, specific AID = 2008 means "specifically designated AID" for HE terminal 200, but means "EHT general information" for EHT / EHT+ terminal 200. Furthermore, in... Figure 24 In this context, the meaning of "Dedicated AID=2009" differs between HE / EHT terminal 200 and EHT+ terminal 200. For example, for HE / EHT terminal 200, "Dedicated AID=2009" means "Separately Designated AID," while for EHT+ terminal 200, it means "EHT+ General Information."

[0191] like Figure 24 As illustrated, for EHT, a new dedicated AID is added to indicate general EHT information (e.g., AID = 2008). Additionally, for EHT+, a new dedicated AID is added to indicate general EHT+ information (e.g., AID = 2009). By adding these dedicated AIDs, the format of the user information field containing that AID can be specified.

[0192] Thus, according to action example 2-3, the same configuration order as HE can be applied to the user information list (in other words, multiple user information fields), thereby reducing the receiving processing of terminal 200.

[0193] Furthermore, in action examples 2-3, by pre-determining the format that terminal 200 should receive between AP100 and terminal 200 (in other words, by pre-establishing mutual understanding), and... Figure 22 Compared to previous examples, this reduces the number of newly imported dedicated AIDs. Therefore, it allows for future scalability.

[0194] Furthermore, there is no need to specify the format of the user information field used for (SA: scheduled access) separately. Terminal 200 can assume the format of its own terminal version and perform reception processing. In addition, in the absence of a common field, EHT / EHT+ terminal 200 can stop reception processing in advance.

[0195] Furthermore, given a pre-determined format that terminal 200 should receive, trigger frame formats corresponding to each version of HE, EHT, and EHT+ can also be defined. In other words, a new trigger frame that does not contain multiple terminal versions can also be defined within EHT and EHT+. AP100 can also use an aggregated MPDU (MAC Protocol Data Unit) containing the aforementioned multiple trigger frames to instruct terminal 200 to send uplink data.

[0196] (Action Example 2-4)

[0197] As examples of actions 2-4, Figure 25 This represents an example of a configuration method for individually specifying RUs, RA-RUs, and unassigned RUs in the user information list.

[0198] In action example 2-4, for example using Figure 26 The dedicated AID table shown contains different versions and is configured in the order of individually specifying RU, RA-RU, and unassigned RU. Figure 22 Compared to the previous example, the dedicated AIDs for the EHT General Information Field and the EHT+ General Information Field changed from 2008 to 2007, and from 2009 to 2006, respectively. In other words, in HE, a dedicated AID for the EHT / EHT+ terminal 200 is selected from the AIDs of individually designated RUs, i.e., AID = 1 to 2007, and applied. Figure 26 In this context, "undefined (reserved)" refers to an AID that has not been defined as a dedicated AID. The dedicated AIDs (0, 2045, 2046, 4095) specified or defined in HE can have the same meaning for EHT / EHT+ terminal 200. However, the meaning of dedicated AID = 2007 differs between HE terminal 200 and EHT / EHT+ terminal 200. For example, dedicated AID = 2007 means "specifically designated AID" for HE terminal 200, but means "EHT general information" for EHT / EHT+ terminal 200. Furthermore, in... Figure 26 In this context, the meaning of "Dedicated AID=2006" differs between HE / EHT terminal 200 and EHT+ terminal 200. For example, for HE / EHT terminal 200, "Dedicated AID=2006" means "Separately Designated AID," while for EHT+ terminal 200, it means "EHT+ General Information."

[0199] In HE, there is a provision that, in order to reduce the receiving processing of terminal 200, in the user information list, user information fields with AID=1 to 2007 used by the RU will not be configured separately after user information fields with time greater than AID=2008.

[0200] When terminal 200 detects an AID greater than 2008, it can determine that there is no individually designated RU allocation. Therefore, terminal 200, which does not perform RA transmission, can stop processing (e.g., transmission processing).

[0201] In addition, by using Figure 26 The dedicated AID table shown can meet the configuration order requirements of the user information field in HE in later versions of EHT, and therefore can reduce the reception processing of EHT / EHT+ terminal 200 in the same way as HE terminal 200.

[0202] Furthermore, the values ​​of AIDs from 1 to 2007 used for the dedicated AID of EHT / EHT+ terminal 200 can also be determined in the standard, for example. Alternatively, the values ​​of AIDs from 1 to 2007 used for the dedicated AID can be determined by AP100, for example. Moreover, the determined dedicated AID can be notified to terminal 200 by AP100 during negotiation, or it can be broadcast to terminal 200 by AP100 using a beacon.

[0203] (Action Example 2-5)

[0204] Instead of the newly defined notification for the dedicated AID of RA-RU and unassigned RU of EHT / EHT+ terminal 200, the format for EHT / EHT+ can also be indicated by the reserved field of the user information field.

[0205] Figure 27 The following paragraph represents an example of a user information field for RA-RU notifications in EHT / EHT+ format. Figure 27 The HE format shown in the upper paragraph (and) Figure 3 Compared to the user information field in the same format, the size of the RU allocation subfield can be expanded in the EHT / EHT+ format user information field (e.g., from 8 bits to 9 bits). This expansion allows for an increase in the range of supported allocation band fields (e.g., from 160MHz to 320MHz).

[0206] Additionally, the MCS table can contain user information fields in EHT / EHT+ format, including whether DCM is applied. Therefore, such as Figure 27 The following example can be deleted. Figure 27The UL DCM subfield (1 bit) is illustrated in the previous paragraph.

[0207] In addition, such as Figure 27 As shown, the reserved field (1 bit) in HE format can be replaced with a version information field in EHT / EHT+ format. For example, as Figure 27 As shown, if the value of the version information field is 0, it indicates that RA-RU should use the HE format; if the value of the version information field is 1, it indicates that RA-RU should use the EHT / EHT+ format.

[0208] By importing version information fields, it is possible to avoid importing unused AIDs as dedicated AIDs. Therefore, for example... Figure 26 The example of the dedicated AID table can be used as follows: Figure 28 The scaling is shown. Because it reduces the consumption of unused AIDs, it maintains scalability for future systems.

[0209] Figure 29 This represents a configuration example of the user information list in action example 2-5. For example... Figure 29 For example, if the value of the version information field is 0, it indicates that the RA-RU should use the HE format; if the value of the version information field is 1, it indicates that the RA-RU should use the EHT / EHT+ format.

[0210] Instead, you can define the position and size of subfields that inherit from the HE format in EHT / EHT+ format. Figure 30 The following paragraph represents an example of this EHT / EHT+ format. For example... Figure 30 As shown in the next paragraph, the unnecessary UL DCM subfields of EHT / EHT+ will be removed. Figure 29 The bits at the position of the upper segment are set as new bits in the RU allocation field (e.g., 9-bit MSB (Most Significant Bit)).

[0211] Therefore, as described above, even when the reserved field is set as the version information field of the user information field for RA-RU, the position and size of the subfields can still be made compatible with the HE format. Terminal 200 can obtain the information of each subfield based on the HE format, rather than on the value of the version information field, thus simplifying the receiving process of terminal 200.

[0212] Furthermore, the EHT / EHT+ format for the position and size of subfields inherited from the HE format is not limited to RA-RU notifications. For example, the EHT / EHT+ format can be added or used instead for separately specified RU notifications.

[0213] Alternatively, the EHT / EHT+ format can also set the bit position of the reserved field (1 bit) in the HE format to an additional bit in the SS allocation / RA-RU information field (e.g., a 7-bit MSB).

[0214] In addition, Figure 30 In the example (the RA-RU example), with Figure 9 Compared to the example of specifying the RU separately, the size of the SS allocation / RA-RU information can be reduced by 1 bit, applying the HE format size (e.g., 6 bits). The reason is that in specifying the RU separately, the information in the SS allocation / RA-RU information subfield represents the number of space multiplexing, corresponding to an extension of the number of space multiplexing in the EHT.

[0215] On the other hand, in RA-RU, the information in the SS allocation / RA-RU information subfield represents the number of consecutive RA-RUs (the spatial multiplexing number of RA-RUs can be fixed at 1). Compared to HE, although EHT has a wider allocation range, by limiting the number of consecutive RA-RUs to a range that can be represented by 6 bits, it can achieve... Figure 30 For example, a reserved field is used as a version information field.

[0216] (other)

[0217] In the example above, although the EHT and EHT+ formats are notified separately using a user information field with a dedicated AID, this is not a limitation. For example, the HE format and later versions (e.g., EHT and EHT+ formats) could be notified via a user information field with a dedicated AID, while notifications for later versions could be made by setting a subfield representing version information in the user information field and explicitly notifying the later versions.

[0218] For example, such as Figure 31 As shown, it can also replace the HE format UL DCM subfield (1 bit) to set the version information subfield (Version Info subfield) indicating either EHT or EHT+ (1 bit). Furthermore, the format of other subfields (e.g., Triggerdependent Per User Info) can be changed based on the version information field (depending on whether it's EHT or EHT+). Therefore, there's no need to import unused AIDs as dedicated AIDs, maintaining future system scalability.

[0219] Additionally, for example, such as Figure 32As shown, in addition to the reserved fields for user information fields (or, in place of the reserved fields for user information fields), the reserved fields for trigger-dependent user information can be used to indicate the format used for EHT / EHT+.

[0220] exist Figure 32 In the example, the reserved field (1 bit) in the user information field indicates whether the version is HE or a version other than HE. Then, if the reserved field in the user information field indicates a version other than HE, the version is indicated as EHT or EHT+ by triggering the reservation that depends on the user information.

[0221] Alternatively, a PPDU (physical-layer protocol data unit) format corresponding to the format of the user information field in the trigger frame can be used as the PPDU format for the uplink signal indicated by the trigger frame. In other words, an uplink signal indicated by a user information field in HE format can be transmitted via HE TB PPDU format. Similarly, an uplink signal indicated by a user information field in EHT format can be transmitted via EHT TB PPDU format. Furthermore, an uplink signal indicated by a user information field in EHT+ format can be transmitted via EHT+ TB PPDU format. In this case, when the user information field contains version information (e.g., a version information subfield), the version information field indicates the requested TB PPDU format.

[0222] The methods described above, namely, the method of sending multiple versions of a single trigger frame (referred to as "Method A") and the method of sending multiple trigger frames in version-defined formats using aggregated MPDUs (referred to as "Method B"), can also be used in combination. For example, Method A can be used when the format that the terminal 200 should receive is not predetermined (or has not yet been determined) between the AP100 and the terminal 200, and Method B can be used when the format that the terminal 200 should receive is predetermined (or has been determined).

[0223] The format of the trigger frame can also be changed according to the Multi-AP Operation category. For example, it can be structured as follows: the general information field includes the Multi-AP category (Coordinated Spatial Reuse (C-SR), Coordinated Orthogonal Frequency Division Multiple Access (C-OFDMA), Joint Transmissions (JT), Coordinated Beamforming (CBF), etc.), and the user information field uses a structure with a format corresponding to the category. Even in this case, the method of this embodiment can be applied in the same way.

[0224] In the above embodiments, although examples are described such that, in order to ensure backward compatibility, the size of the user information field in EHT format and EHT+ format is set to the same size as that in HE format, it is not limited to this.

[0225] For example, in such Figure 11 As illustrated in the user information list, when defining a dedicated AID for the section representing the version, the size of the user information fields in EHT and EHT+ formats can also be set to a different size than that in HE format.

[0226] For example, the RU or SS subfields of user information fields in EHT and EHT+ formats, which have a wider allocation range and support more space reuse, can also be defined to a larger size than those in HE format. For instance, in EHT / EHT+ formats, new information distinguishing multiple versions after EHT (EHT, EHT+, EHT++, etc.) can also be added. Furthermore, the size or content of each subfield of the user information field can be changed based on the version distinguished by the new information.

[0227] When using a value that is a padding start for an older version (e.g., 4095 related to HE) or an unassigned RU notification (e.g., 2046 related to HE) as a dedicated AID, the older version of the terminal 200 will stop decoding the user information field thereafter, thus ensuring backward compatibility.

[0228] In addition, such as Figure 27 or Figure 30 As illustrated, the method of indicating version information through a reserved (1 bit) user information field is not limited to the user information field used by RA-RU. For example, it can also be applied to individually specified RUs or unassigned RUs.

[0229] In addition, Figure 27 and Figure 30 In the example shown, although 1 bit is used to distinguish between HE and EHT versions, additional information can be added to distinguish between multiple versions such as EHT, EHT+, and EHT++ (called "Further Version Info").

[0230] For example, Figure 33 This is an example of adding a user information field with further version information. Figure 33 In the example, the reserved field (1 bit) is used as the version information subfield, containing information to distinguish between HE and EHT versions. When an EHT version is indicated (e.g., when the version information field = 1), the further version information subfield (e.g., 3 bits) can contain information to distinguish between multiple EHT versions (EHT, EHT+, EHT++, etc.). To ensure backward compatibility and maintain the same size as the HE format, the SS allocation / RA-RU information subfield (6 bits in HE format) can be reduced, for example.

[0231] In the case of RA-RU, the number of consecutive RA-RUs notified by this subfield can be reduced to 3 bits. For example, the number of consecutive RA-RUs can also be limited to 1 to 7 and reduced to 3 bits. The reason is that when the RA-RU size is large, there is less need to indicate a large number of consecutive RA-RUs. In addition, when the RA-RU size is reduced, it is possible to use the HE format for indication as before.

[0232] Alternatively, the degrees of freedom for the number of consecutive RA-RUs can be restricted to powers of 2, and the exponents of 2 can be represented in the RA-RU information subfield, thereby reducing the size. Alternatively, the number of consecutive RA-RUs can be determined without being limited to powers of 2, within the range that the applied RA-RU size (e.g., 3 bits) can represent. For example, the standard could define a rule where subfield values ​​of 0, 1, 2, 3, ..., 7 represent consecutive RA-RU numbers of 1, 2, 8, 32, ..., 64, respectively.

[0233] Additionally, when a single RU is specified, the number of spatial multiplexing in UL MU-MIMO can be limited to reduce the number of bits in the SS allocation subfield. The limitation could be, for example, reducing the upper limit of the application's multiplexing, or limiting the application's multiplexing by an idempotency of 2 as described above. Alternatively, for example, the terminal 200 could decode the RU allocation subfield based on the user information fields of all individually specified RUs contained in the user information list, determine how many times the same RU allocation has been indicated, and thereby derive the start stream number in the spatial multiplexing included in the SS allocation. This allows for a reduction in the size of the SS allocation subfield.

[0234] The terms "...part" in the above embodiments can also be replaced with other terms such as "...circuitry", "...device", "...unit" or "...module".

[0235] This disclosure can be implemented in software, hardware, or software in cooperation with hardware. The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration), and the processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips or a single chip comprising some or all of the functional blocks. An LSI can also include data input and output. Depending on the degree of integration, an LSI can also be referred to as an "IC (Integrated Circuit)," "System LSI," "Super LSI," or "Ultra LSI."

[0236] The method of integrating LSIs is not limited to LSIs; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Alternatively, LSIs can be used to fabricate programmable FPGAs (Field Programmable Gate Arrays), or reconfigurable processors that allow for reconfiguration of the connections or settings of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.

[0237] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.

[0238] This invention can be implemented in all kinds of devices, apparatuses, and systems with communication capabilities (collectively referred to as "communication devices"). A communication device may also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these units. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.

[0239] Communication devices are not limited to portable or movable devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. Examples include: smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.

[0240] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.

[0241] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.

[0242] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.

[0243] A base station according to one embodiment of this disclosure may include: a control circuit that, depending on the terminal version, associates information related to the format of a terminal information field in a control signal indicating the transmission of an uplink signal with identification information not used for terminal identification information assigned to a separately designated terminal; and a transmission circuit that transmits the control signal containing the associated unused identification information.

[0244] In one embodiment of this disclosure, the control circuit may associate the format indicating the start of filling for a first terminal version and the format indicating information common to multiple terminals for a second terminal version in the unused identification information.

[0245] In one embodiment of this disclosure, the control circuit may associate the format indicating unallocated resources for a first terminal version and the format indicating information common to multiple terminals for a second terminal version in the unused identification information.

[0246] In one embodiment of this disclosure, the control circuit may, according to the terminal version, change the definition of the format of the terminal information field corresponding to the configuration order of the terminal information fields that use the unused identification information among the multiple terminal information fields contained in the control signal.

[0247] In one embodiment of this disclosure, the control circuit can configure multiple terminal information fields contained in the control signal according to the terminal version, and within a terminal version, configure the terminal information fields in the order of individually specifying resources, randomly accessing resources, and unallocated resources.

[0248] A terminal in one embodiment of this disclosure may include: a control circuit that determines the terminal information field to be received based on a correlation between information related to the format of the terminal information field in a control signal indicating the transmission of an uplink signal and identification information corresponding to the terminal version, and identification information not used as terminal identification information assigned to a separately designated terminal; and a receiving circuit that performs receiving processing of the determined terminal information field.

[0249] In a communication method according to one embodiment of this disclosure, a base station may associate information related to the format of a terminal information field in a control signal that indicates the transmission of an uplink signal with identification information that is not used as terminal identification information assigned to a separately designated terminal, based on the terminal version, and transmit the control signal containing the associated unused identification information.

[0250] In a communication method according to one embodiment of this disclosure, a terminal can determine the terminal information field to be received based on the association between information related to the format of the terminal information field in the control signal that indicates the transmission of the uplink signal and identification information corresponding to the terminal version, and the identification information that is not used as terminal identification information assigned to a separately designated terminal, and perform reception processing of the determined terminal information field.

[0251] A communication apparatus according to an embodiment of this disclosure includes: circuitry that sets a first value in an associated ID12 subfield, i.e., an AID12 subfield, of a first field in a trigger frame, the trigger frame being a trigger frame for a trigger-based physical layer protocol data unit (EHT TB PPDU) requesting extremely high throughput; and a transmitter that transmits the trigger frame, the first value indicating that the first field contains information generally used for transmitting the EHT TB PPDU.

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

[0253] In a communication apparatus according to one embodiment of this disclosure, the first value can be interpreted by an efficient station, i.e., a HE STA, as an indication that the first field is sent to other stations.

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

[0255] One embodiment of the communication apparatus of this disclosure may be an Extremely High Throughput Access Point (EHT AP), wherein the circuit does not set the first value in the AID12 subfield of each user field containing user-specific information destined for the site associated with the EHT AP.

[0256] In a communication apparatus according to one embodiment of this disclosure, the first field may be located immediately following the general information field in the trigger frame.

[0257] In a communication device according to one embodiment of this disclosure, the first user information field sent to an extremely high throughput station, namely an EHT STA, may be followed by the first field.

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

[0259] In a communication apparatus according to one embodiment of this disclosure, the first user information field of the trigger frame may include a resource unit allocation subfield and a first subfield, wherein the resource unit allocation subfield and the first subfield together represent the resource unit used for the transmission of the EHT TB PPDU.

[0260] In a communication apparatus according to one embodiment of this disclosure, the trigger frame may request an efficient trigger-based physical layer protocol data unit, namely HETBPPDU, through the user information field of the trigger frame.

[0261] In a communication device according to one embodiment of this disclosure, the trigger frame may include the first field, a user information field for EHT, and a user information field for HE, and the trigger frame requests the EHT TB PPDU and HETB PPDU.

[0262] In a communication device according to one embodiment of this disclosure, the first field may include version information of the first field, wherein the version information represents one of the EHT version and the host EHT version.

[0263] In a communication apparatus according to one embodiment of this disclosure, the transmission of the EHT TB PPDU can be random access.

[0264] One embodiment of the communication method disclosed herein includes the following steps: setting a first value in the associated ID12 subfield, i.e., the AID12 subfield, of a first field in a trigger frame, the trigger frame being a trigger frame for a trigger-based physical layer protocol data unit (EHT TB PPDU) requesting extremely high throughput; and sending the trigger frame, wherein the first value indicates that the first field contains information generally used for sending the EHT TB PPDU.

[0265] A communication apparatus according to an embodiment of this disclosure includes: a receiver that receives a trigger frame that is a trigger frame for a trigger-based physical layer protocol data unit (EHT TB PPDU) requesting extremely high throughput, and wherein a first value is set in an associated ID12 subfield (AID12 subfield) of a 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 generally used for transmitting the EHT TB PPDU.

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

[0267] In a communication apparatus according to one embodiment of this disclosure, the first value can be interpreted by an efficient station, i.e., a HE STA, as an indication that the first field is sent to other stations.

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

[0269] In a communication apparatus according to one embodiment of this disclosure, the trigger frame may be sent by an Extremely High Throughput Access Point (EHT AP), wherein the EHT AP does not set the first value in the AID12 subfield of each user field containing user-specific information sent to the site associated with the EHT AP.

[0270] In a communication device according to one embodiment of this disclosure, the first field may be located immediately following the general information field in the trigger frame.

[0271] In a communication device according to one embodiment of this disclosure, the first user information field sent to an extremely high throughput station, namely an EHT STA, may be followed by the first field.

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

[0273] In a communication apparatus according to one embodiment of this disclosure, the first user information field of the trigger frame may include a resource unit allocation subfield and a first subfield, wherein the resource unit allocation subfield and the first subfield together represent the resource unit used for the transmission of the EHT TB PPDU.

[0274] In a communication apparatus according to one embodiment of this disclosure, the trigger frame may request an efficient trigger-based physical layer protocol data unit, namely HETBPPDU, through the user information field of the trigger frame.

[0275] In a communication device according to one embodiment of this disclosure, the trigger frame may include the first field, a user information field for EHT, and a user information field for HE, and the trigger frame requests the EHT TB PPDU and HETB PPDU.

[0276] In a communication device according to one embodiment of this disclosure, the first field may include version information of the first field, wherein the version information represents one of the EHT version and the host EHT version.

[0277] In a communication apparatus according to one embodiment of this disclosure, the transmission of the EHT TB PPDU can be random access.

[0278] One embodiment of the communication method disclosed herein includes the following steps: receiving a trigger frame, which is a trigger frame requesting a trigger-based physical layer protocol data unit (EHT TB PPDU) for extremely high throughput, and having a first value set in the associated ID12 subfield (AID12 subfield) of the first field of the trigger frame; and sending the EHT TB PPDU, wherein the first value indicates that the first field contains information generally used for sending the EHT TB PPDU.

[0279] The entire contents of the description, drawings and abstract of the description contained in Japanese Patent Application No. 2020-180361, filed on October 28, 2020, are incorporated herein by reference.

[0280] Industrial applicability

[0281] One embodiment of the present invention is useful for wireless communication systems.

[0282] Explanation of reference numerals in the attached figures

[0283] 11 Control Department

[0284] 12. Sending Department

[0285] 21 Receiving Department

[0286] 22 Control Department

[0287] 100AP

[0288] 101 Dispatch Department

[0289] 102 Terminal Information Acquisition Department

[0290] 103 General Information Generation Department

[0291] 104 AID Control Department

[0292] 105 User Information Generation Department

[0293] 106 Trigger Frame Generation Unit

[0294] 107 Error Correction Coding Department

[0295] 108 Modulation Section

[0296] 109 Wireless Transceiver Unit

[0297] 110 Mediation Department

[0298] 111 Error Correction and Decoding Department

[0299] 200 terminals

[0300] 201 Wireless Transceiver Unit

[0301] 202 De-escalation Department

[0302] 203 Error Correction and Decoding Department

[0303] 204 General Information Acquisition Department

[0304] 205 AID Control Department

[0305] 206 User Information Acquisition Department

[0306] 207 Data Generation Department

[0307] 208 Error Correction Coding Department

[0308] 209 Modulation Section

Claims

1. A communication device, characterized in that, include: The circuit sets a first value in the associated ID12 subfield, i.e., the AID12 subfield, of the first field in the following trigger frame, which is a trigger frame for a trigger-based physical layer protocol data unit, i.e., an EHT TB PPDU, requesting extremely high throughput. as well as The transmitter sends the trigger frame. The first value indicates that the first field contains information generally used for sending the EHT TB PPDU, and the efficient site, i.e., the HE STA, interprets the first value as an indication that the first field is sent to a single specific STA represented by the first value.

2. The communication device as claimed in claim 1, wherein, The first value indicates that the trigger frame includes a user information field for EHT after the first field.

3. The communication device as claimed in claim 1, wherein, The first value is interpreted by the HE STA as an indication that the first field is sent to another site.

4. The communication device as claimed in claim 1, wherein, The length of the first field is equal to the length of the first user information field of the trigger frame.

5. The communication device as claimed in claim 1, wherein, The communication device is an EHT (Extremely High Throughput Access Point) AP. The circuit does not set the first value in the AID12 subfield of each user field that contains user-specific information sent to the site associated with the EHT AP.

6. The communication device as claimed in claim 1, wherein, In the trigger frame, the first field is located immediately following the general information field.

7. The communication device as claimed in claim 1, wherein, The first user information field sent to the EHT STA (Extremely High Throughput Station) follows the first field.

8. The communication device as claimed in claim 1, wherein, The general information field of the trigger frame contains information indicating whether the first field exists in the trigger frame.

9. The communication device as claimed in claim 1, wherein, The first user information field of the trigger frame includes a resource unit allocation subfield and a first subfield. The resource unit allocation subfield, together with the first subfield, represents the resource unit used for the transmission of the EHT TB PPDU.

10. The communication device as claimed in claim 1, wherein, The trigger frame requests an efficient trigger-based physical layer protocol data unit (HTB PPDU) through the user information field of the trigger frame.

11. The communication device as claimed in claim 1, wherein, The trigger frame includes the first field, a user information field for EHT, and a user information field for HE. The trigger frame requests the EHT TB PPDU and HE TB PPDU.

12. The communication device as claimed in claim 1, wherein, The first field contains version information for the first field. The version information refers to either the EHT version or the host EHT version.

13. The communication device as claimed in claim 1, wherein, The transmission of the EHT TB PPDU is random access.

14. The communication device as claimed in claim 1, wherein, The specific STA is the STA associated with an AID equal to the first value.

15. The communication device as claimed in claim 1, wherein, The first field does not include user-specific information, but the HE station interprets the first value as an indication that the first field includes user-specific information.

16. The communication device as claimed in claim 1, wherein, The first value indicates to the EHT station that the first field does not include user-specific information, but the HE station interprets the first value as meaning that the first field includes the user-specific information.

17. The communication device as claimed in claim 1, wherein, The information is used by multiple STAs to send the EHT TB PPDU.

18. A communication method, characterized in that, It includes the following processes: In the following trigger frame, set the first value in the associated ID12 subfield (AID12 subfield) of the first field, where the trigger frame is a trigger frame requesting a trigger-based Physical Layer Protocol Data Unit (EHT TB PPDU) for extremely high throughput; and Send the trigger frame, The first value indicates that the first field contains information generally used for sending the EHT TB PPDU, and the efficient site, i.e., the HE STA, interprets the first value as an indication that the first field is sent to a single specific STA represented by the first value.

Images