Terminals and communication methods

Abstract

Set the format of the control signal that controls uplink transmission appropriately. [Solution] The base station comprises a control circuit that generates an uplink transmission control signal, which includes a field common to multiple terminals containing information about the version of the wireless communication standard and subfields whose settings differ according to the version, and a transmission circuit that transmits the control signal.

Description

Technical Field

[0001] This disclosure relates to a base station, a terminal, and a communication method.

Background Art

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

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

Non-Patent Document 6

[0004] However, the method for configuring the format of control signals that control uplink transmission in wireless communication such as Wi-Fi has not been sufficiently studied.

[0005] Non-limiting embodiments of this disclosure contribute to providing a base station and communication method that can appropriately configure the format of control signals that control uplink transmission.

[0006] A base station according to one embodiment of the present disclosure comprises a control circuit that generates an uplink transmission control signal, which includes in a field common to multiple terminals information about the version of the wireless communication standard and subfields whose settings differ according to the version, and a transmission circuit that transmits the control signal.

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

[0008] According to one embodiment of this disclosure, for example, the format of the control signal that controls uplink transmission can be appropriately set.

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

[0010] [Figure 1] Figure showing an example of a trigger frame [Figure 2] Figure showing an example of a Common Info field [Figure 3] Figure showing an example of a User Info field [Figure 4] Figure showing an example of a Special User Info field [Figure 5] Figure showing an example of a trigger type [Figure 6] Block diagram showing a partial configuration example of an access point (AP: Access Point) [Figure 7] Block diagram showing a partial configuration example of a terminal [Figure 8] Block diagram showing a configuration example of an AP [Figure 9] Figure showing an example of a trigger type according to Embodiment 1 [Figure 10] Block diagram showing a configuration example of a terminal [Figure 11] Sequence diagram showing operation examples of an AP and a terminal [Figure 12] Figure showing an example of a Common Info field according to Embodiment 1 [Figure 13] Figure showing an example of a Common Info field according to Embodiment 1 [Figure 14] Figure showing an example of a Common Info field according to Embodiment 1 [Figure 15] Figure showing an example of a Common Info field according to Embodiment 1 [Figure 16] Figure showing an example of a Common Info field according to Embodiment 1 [Figure 17] Figure showing an example of a trigger type according to Embodiment 2 [Figure 18] Figure showing an example of a trigger type according to Embodiment 2 [Figure 19] Figure showing an example of a Common Info field according to Embodiment 2 [Figure 20] Figure showing an example of the User Info field according to Embodiment 2 [Figure 21] Figure showing an example of the Special User Info field according to Embodiment 2 [Figure 22] Figure showing an example of the User Info field [Figure 23] Figure showing an example of the Feedback type subfield according to Embodiment 2 [Figure 24] Figure showing an example of the User Info field [Figure 25] Figure showing an example of the User Info field

Embodiments for Carrying out the Invention

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

[0012] In 11ax (e.g., HE), the introduction of orthogonal frequency division multiple access (e.g., OFDMA: Orthogonal Frequency Division Multiple Access) in the uplink (UL: Uplink) is defined. For example, an access point (AP: Access Point; also referred to as a "base station") transmits a control signal (hereinafter referred to as a "trigger frame") that instructs the transmission of an uplink signal (e.g., an uplink OFDMA signal) to a plurality of terminals (STA: Station; also referred to as a "non-AP STA") accommodated by the AP.

[0013] In 11be (e.g., EHT), it has been agreed to reuse the trigger frame of 11ax (HE) as a control signal for instructing a plurality of terminals to transmit an uplink signal (e.g., an uplink OFDMA signal) (see, for example, Non-Patent Documents 1 and 3).

[0014] Figure 1 shows an example of a trigger frame. As shown in Figure 1, the trigger frame includes a field containing information common to multiple terminals being OFDMA multiplexed (e.g., a "Common Info field") and a field called a User Info List (see, for example, Non-Patent Documents 1, 2, and 3). The User Info field may include, for example, one or more fields containing information specific to each terminal (e.g., "User Info fields").

[0015] Figure 2 shows an example configuration of a Common Info field (e.g., Common Info field format and EHT variant) considered in 11be (e.g., EHT). Figure 3 shows an example configuration of a User Info field (e.g., User Info field format and EHT variant) considered in 11be (EHT) (see, for example, Non-Patent Document 3). Figure 4 shows an example configuration of a Special User Info field containing information for a terminal corresponding to 11be (e.g., EHT) (hereinafter referred to as "EHT terminal") (see, for example, Non-Patent Document 3).

[0016] For example, the "Trigger Type" subfield in the Common Info field shown in Figure 2 is a subfield that indicates the type of trigger frame (for example, the type of signal that the AP sends to the terminal). Figure 5 shows an example of the types defined as Trigger Types in 11ax (see, for example, Non-Patent Document 2).

[0017] Furthermore, for example, the "Trigger Dependent Common Info" subfield within the Common Info field shown in Figure 2 may contain information that depends on the trigger type (e.g., common information).

[0018] Furthermore, 11be (EHT) may introduce new trigger types that differ from those defined in 11ax, for example.

[0019] For example, the application of uplink beamforming to the uplink response signal to the trigger frame of an EHT terminal is being considered (see, for example, Non-Patent Document 4). To apply uplink beamforming, for example, a new trigger type may be introduced to prompt the terminal to send a Sounding Null Data Packet (NDP) so that the AP can acquire the precoding information used by each terminal, or a new trigger type that includes the precoding information to be applied to the uplink response signal in the User Info field.

[0020] The uplink response signal is sometimes referred to as, for example, the EHT trigger-based physical layer protocol data unit (EHT TB PPDU) or HE TB PPDU.

[0021] Furthermore, EHT is considering the application of Multi-AP coordination (hereinafter referred to as "cooperative communication"), in which multiple APs cooperate to communicate with each terminal (for example, at least one of data transmission and reception) (see, for example, Non-Patent Document 5). To realize cooperative communication, a new Trigger type may be introduced to instruct terminals or APs participating in cooperative transmission with control information related to cooperative communication.

[0022] For example, when introducing a new Trigger type (e.g., the transmission of Sounding NDP or control of cooperative communication as described above) in EHT or a further future version (hereinafter referred to as "EHT+"), one of the Reserved areas (8-15) of the Trigger type subfield value in the Common Info field shown in Figure 5 may be used. As an example, if Trigger type subfield value = 8, a Trigger type that instructs the transmission of Sounding NDP may be set, and if Trigger type subfield value = 9, a Trigger type related to control of cooperative communication may be set. Note that the setting of the Trigger type for the Trigger type subfield value is not limited to these examples.

[0023] Here, the method for adding a new trigger type to HE in EHT has not been sufficiently considered. For example, the formatting of the trigger frame (e.g., at least one of the Common Info field and User Info field) when adding a new trigger type to HE in EHT (e.g., setting the field (or subfield)) is worth considering.

[0024] In non-limiting embodiments of this disclosure, examples of setting the signal format are described.

[0025] (Embodiment 1) For example, a Trigger type specified using the Reserved area (8-15) of the Trigger type subfield value in the Common Info field defined in HE is an unsupported Trigger type for a terminal corresponding to HE (for example, referred to as an "HE terminal"). For example, according to the HE specification, if an HE terminal is instructed by an AP to use an unsupported Trigger type (for example, the Trigger type value corresponding to the Reserved area), it may abort the reception processing of that Trigger frame.

[0026] For example, if a new Trigger type added in EHT is indicated using the Trigger type subfield in the Common Info field defined in HE, the HE terminal will stop processing the Trigger frame, and the EHT terminal will process the Trigger frame. After receiving the Trigger frame, the EHT terminal may, for example, send an EHT TB PPDU (a TB PPDU in the format corresponding to EHT) to the AP as a response signal.

[0027] Here, the trigger frame contains control information for the HE terminal (for example, control information for HE TB PPDU transmission). Therefore, as mentioned above, when a new trigger type is specified for the EHT terminal, some subfield information, including control information for the HE terminal (for example, for HE TB PPDU transmission), may become useless information for the EHT terminal receiving the trigger frame.

[0028] Examples of control information for HE terminals include the "UL Space Time Block Coding (STBC)" subfield, the "UL Spatial Reuse" subfield, and the "Doppler" subfield within the Common Info field shown in Figure 2. These subfields contain information for HE terminals and may be subfields (Reserved areas) that do not need to be received by EHT terminals responding with EHT TB PPDU (see, for example, Non-Patent Documents 1 and 3).

[0029] Thus, when a new trigger type for EHT terminals is notified using the Reserved area of ​​the Trigger type subfield value within the Common Info field defined in HE, some subfields may become redundant information for the EHT terminal, potentially increasing overhead.

[0030] Non-limiting embodiments of this disclosure describe a method for suppressing an increase in overhead in a trigger frame when a new trigger type for an EHT terminal is notified.

[0031] [Configuration of the wireless communication system] The wireless communication system according to this embodiment may include, for example, an AP100 shown in Figure 6 and a terminal 200 shown in Figure 7. There may be two or more AP100s and terminals 200s in the wireless communication system. The AP100 may, for example, send a trigger frame to the terminal 200 instructing it to perform an uplink OFDMA transmission. The terminal 200 receives the trigger frame and may use the resources indicated by the received trigger frame to send an uplink OFDMA signal to the AP100.

[0032] Here, AP100 can be, for example, an AP that supports EHT and is backward compatible with HE (for example, an AP that also supports HE).

[0033] Furthermore, terminal 200 may be either an HE terminal or an EHT terminal, for example. AP100 may send a single trigger frame to multiple terminals 200 with different versions of wireless communication standards (e.g., either HE or EHT), such as the wireless LAN standard, and receive uplink OFDMA signals from each terminal 200. AP100 may, for example, separate and decode the uplink signals of the resources allocated to each terminal 200 from the received signals.

[0034] Figure 6 is a block diagram showing a partial configuration example of AP100 according to one embodiment of the present disclosure. In the AP100 shown in Figure 6, the control unit (e.g., corresponding to a control circuit) generates an uplink transmission control signal (e.g., a trigger frame) which includes information about the wireless communication standard version and subfields whose settings differ depending on the version in a field common to multiple terminals (e.g., a Common Info field). The transmission unit (e.g., corresponding to a transmission circuit) transmits the control signal.

[0035] Figure 7 is a block diagram showing a partial configuration example of a terminal 200 according to one embodiment of the present disclosure. In the terminal 200 shown in Figure 7, the receiving unit (e.g., corresponding to a receiving circuit) receives an uplink transmission control signal (e.g., a trigger frame) which includes information about the wireless communication standard version and subfields whose settings differ depending on the version in a field common to multiple terminals (e.g., a Common Info field). The control unit (e.g., corresponding to a control circuit) determines the settings based on the information about the version.

[0036] [Example configuration of AP100] AP100 generates a trigger frame that instructs terminal 200 to transmit an uplink signal, such as a data signal or an NDP signal, and sends the trigger frame to terminal 200.

[0037] Figure 8 is a block diagram showing an example configuration of AP100. The AP100 shown in Figure 8 may include, for example, a scheduling unit 101, a User Info generation unit 102, a Trigger type setting unit 103, a Common Info generation unit 104, a Trigger frame generation unit 105, an error correction coding unit 106, a modulation unit 107, a wireless transmission / reception unit 108, a demodulation unit 109, an error correction decoding unit 110, and a terminal information acquisition unit 111.

[0038] For example, the scheduling unit 101, the User Info generation unit 102, the Trigger type setting unit 103, the Common Info generation unit 104, the Trigger frame generation unit 105, and the terminal information acquisition unit 111 may be included in the access control unit (for example, the Medium Access Control (MAC) processing unit).

[0039] Furthermore, at least one of the scheduling unit 101, User Info generation unit 102, Trigger type setting unit 103, Common Info generation unit 104, Trigger frame generation unit 105, error correction coding unit 106, modulation unit 107, demodulation unit 109, error correction decoding unit 110, and terminal information acquisition unit 111 shown in Figure 8 may be included in the control unit shown in Figure 6, for example. Also, the wireless transmission / reception unit 108 shown in Figure 8 may be included in the transmission unit shown in Figure 6, for example.

[0040] The scheduling unit 101 may, for example, perform scheduling for the terminal 200. For example, the scheduling unit 101 may determine the trigger type corresponding to the type of uplink response signal and information regarding the radio resources of the uplink response signal based on control information such as the version (e.g., HE or EHT) that the terminal 200 corresponds to, or individual radio quality information for the bandwidth, which is included in the terminal information input from the terminal information acquisition unit 111. Information regarding the radio resources of the uplink response signal may include, for example, the allocated bandwidth, modulation scheme and coding rate (MCS), and target reception level. The scheduling unit 101 outputs, for example, the determined trigger type information and the radio resource information for each terminal 200 to the User Info generation unit 102 and the Common Info generation unit 104.

[0041] The User Info generation unit 102 may, for example, generate control information contained in individual User Info fields for terminal 200 (or STA). The User Info generation unit 102 may, for example, generate information about individual User Info fields for terminal 200 based on a defined format, and generate information about a User Info List containing User Info fields for each of multiple terminals 200. The User Info generation unit 102 may, for example, output information about the User Info List to the Trigger frame generation unit 105.

[0042] The Trigger type setting unit 103 may, for example, set an association between the Trigger type corresponding to the type of uplink response signal and information indicating the Trigger type within the Trigger frame (for example, the Trigger type subfield value), and store information regarding the set Trigger type. The Trigger type setting unit 103 may output information regarding the set Trigger type to the Common Info generation unit 104.

[0043] The association between the trigger type and the information indicating the trigger type within the trigger frame may be in the form of information in a table format (for example, called the "Trigger type table"), or in a format other than a table. Figure 9 shows an example of a trigger type table held by the trigger type setting unit 103. The trigger type table shown in Figure 9 may include, for example, the trigger type defined in the HE shown in Figure 5 (for example, any of Trigger type subfield value=0 to 7), and trigger types for EHT terminals that are not supported by the HE terminal, such as Sounding NDP and Multi-AP coordination (for example, Trigger type subfield value=8 or 9).

[0044] The Common Info generation unit 104 may, for example, generate control information included in a Common Info field common to multiple terminals 200. The Common Info generation unit 104 may, for example, generate information for the Trigger type subfield based on information regarding the Trigger type instruction input from the scheduling unit 101 and information regarding the Trigger type input from the Trigger type setting unit 103 (for example, a Trigger type table).

[0045] The Trigger type (also called a Trigger frame variant, for example) indicated in the Trigger type subfield may be uniquely associated with information (for example, called version information) regarding the version (or "generation") of a wireless LAN standard (in other words, a communication standard), such as HE-compatible or EHT-compatible. The Common Info generation unit 104 may, for example, generate a Common Info field containing the Trigger type subfield based on a format (for example, field settings) corresponding to the version information associated with the Trigger type, and output information regarding the generated Common Info field to the Trigger frame generation unit 105.

[0046] For example, when the Common Info generation unit 104 specifies a Trigger type that supports HE (and may also support EHT terminals), it may generate a Common Info field based on the format shown in Figure 2. Alternatively, when the Common Info generation unit 104 specifies a Trigger type that supports EHT (and may not support HE terminals), it may generate a Common Info field with settings for subfields that can be received by EHT terminals (for example, some subfields in the format shown in Figure 2) that differ from those in the HE-compatible case. Examples of Common Info field settings will be described later.

[0047] Note that the term "settings" in fields (e.g., subfields) within a trigger frame may be replaced with other terms such as "definition" or "interpretation."

[0048] The Trigger frame generation unit 105 may generate a Trigger frame that includes information from the Common Info field input from the Common Info generation unit 104 and information from the User Info List (e.g., multiple User Info fields) input from the User Info generation unit 102, based on the format shown in Figure 1. The Trigger frame may include, for example, at least one of the following: the Common Info field and the User Info List, as well as the MAC header, Padding, and FCS (frame check sequence). The Trigger frame generation unit 105 may output the generated Trigger frame to the error correction coding unit 106.

[0049] The error correction coding unit 106, for example, errors-corrects and encodes the transmission data signal, which includes the trigger frame input from the trigger frame generation unit 105, and outputs the encoded signal to the modulation unit 107.

[0050] The modulation unit 107 performs modulation processing on the signal input from the error correction coding unit 106, for example, and outputs the modulated signal to the wireless transceiver unit 108.

[0051] Furthermore, if the modulated data signal is an orthogonal frequency division multiplexing (OFDM) signal, AP100 (for example, the modulation unit 107) may 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.

[0052] The wireless transceiver 108 performs wireless transmission processing on the modulated signal input from the modulation unit 107, such as D / A conversion and upconversion to the carrier frequency, and transmits the processed signal to the terminal 200 via the antenna. The wireless transceiver 108 also receives the signal transmitted from the terminal 200 via the antenna, performs wireless reception processing on the received signal, such as downconversion to the baseband and A / D conversion, and outputs the processed signal to the demodulation unit 109.

[0053] The demodulation unit 109 performs demodulation processing on the signal input from the wireless transceiver unit 108, for example, and outputs the demodulated signal to the error correction decoding unit 110. If the signal input to the demodulation unit 109 is an OFDM signal, the AP100 (for example, the demodulation unit 109) may perform CP removal processing and Fast Fourier Transform (FFT) processing.

[0054] The error correction decoding unit 110 decodes the signal input from the demodulation unit 109 to obtain the received data signal from the terminal 200. If the decoded received data contains the terminal information described above, the error correction decoding unit 110 outputs the decoded data containing the terminal information to the terminal information acquisition unit 111.

[0055] The terminal information acquisition unit 111 may, for example, acquire terminal information (for example, version information of terminal 200 and individual wireless quality information for a defined bandwidth) from the decoded data input from the error correction decoding unit 110, and output the acquired terminal information to the scheduling unit 101. Note that "terminal information" means, for example, information relating to terminal 200, and may be read as "Capability information".

[0056] [Example configuration of terminal 200] Terminal 200 receives, for example, a Trigger frame from AP100 that instructs it to transmit an uplink signal such as a data signal or an NDP signal, and sends an uplink response signal to AP100 for the Trigger frame.

[0057] Figure 10 is a block diagram showing an example configuration of terminal 200. The terminal 200 shown in Figure 10 may include, for example, a wireless transceiver unit 201, a demodulation unit 202, an error correction decoding unit 203, a trigger type setting unit 204, a common information acquisition unit 205, a user information acquisition unit 206, a format determination unit 207, a data generation unit 208, an error correction coding unit 209, and a modulation unit 210.

[0058] For example, the Trigger type setting unit 204, the Common Info acquisition unit 205, the User Info acquisition unit 206, the format determination unit 207, and the data generation unit 208 may be included in the access control unit (for example, the MAC processing unit).

[0059] Furthermore, at least one of the demodulation unit 202, error correction decoding unit 203, trigger type setting unit 204, common information acquisition unit 205, user information acquisition unit 206, format determination unit 207, data generation unit 208, error correction coding unit 209, and modulation unit 210 shown in Figure 10 may be included in the control unit shown in Figure 7, for example. Also, the wireless transmission / reception unit 201 shown in Figure 10 may be included in the receiving unit shown in Figure 7, for example.

[0060] The wireless transceiver unit 201, for example, receives a received signal via an antenna, performs wireless reception processing on the received signal such as down-conversion and A / D conversion, and outputs the processed signal to the demodulation unit 202. The wireless transceiver unit 201 also performs wireless transmission processing on the signal input from the modulation unit 210, for example, performs up-conversion and D / A conversion, and transmits the processed signal from the antenna.

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

[0062] The error correction decoding unit 203 may, for example, decode the demodulated signal input from the demodulation unit 202 and output the decoded signal as the received data signal. The error correction decoding unit 203 may also, for example, output the trigger frame from the received data signal to the Common Info acquisition unit 205 and the User Info acquisition unit 206.

[0063] The Trigger type setting unit 204 may perform operations similar to those of the Trigger type setting unit 103 of AP100, for example. For example, the Trigger type setting unit 204 may output information about predefined Trigger types (e.g., a Trigger type table) to the Common Info acquisition unit 205.

[0064] The Common Info acquisition unit 205 may, for example, extract information corresponding to the Common Info field from the Trigger frame input from the error correction decoding unit 203 based on information input from the Trigger type setting unit 204 (e.g., Trigger type table), and acquire terminal common information regarding the generation of the uplink signal. The terminal common information may include, for example, the type of the uplink response signal (e.g., data) and the duration of the uplink signal.

[0065] Here, for example, if terminal 200 is an HE terminal, and the Trigger type subfield value contained in the Trigger type subfield is a value not supported by the HE terminal, terminal 200 may determine that it is an HE-incompatible version (or an EHT-compatible version) and abort the reception process. On the other hand, if the Trigger type subfield value contained in the Trigger type subfield is a value supported by the HE terminal, terminal 200 may determine that it is an HE-compatible version and perform reception processing of the Common Info field based on the specified HE terminal format (for example, the format shown in Figure 2).

[0066] For example, an HE terminal that supports the Trigger type table shown in Figure 5 may cancel the reception process if it receives a value of 8 or greater for the Trigger type subfield value, and may proceed with the reception process for the Common Info field if it receives a value of 7 or less for the Trigger type subfield value.

[0067] Furthermore, for example, if terminal 200 is an EHT terminal, terminal 200 may configure the format of the Trigger frame (e.g., Common Info field) differently depending on the Trigger type indicated by the Trigger type subfield, similar to the operation of AP100. For example, if the Trigger type is an HE-compatible type, terminal 200 may process the reception of the Common Info field based on the format definition shown in Figure 2. On the other hand, if the Trigger type is an EHT-compatible type (in other words, not HE-compatible), terminal 200 may process the reception of the Common Info field based on a format in which some subfield settings of the format shown in Figure 2 have been modified. Note that if terminal 200 is an EHT terminal, the Special User Info field may be included in the User Info List.

[0068] The Common Info acquisition unit 205 may output the extracted terminal common information to the User Info acquisition unit 206.

[0069] The User Info Acquisition Unit 206 may, for example, extract information corresponding to the User Info field from the Trigger frame input from the Error Correction Decoding Unit 203 and acquire terminal-specific information regarding the generation of the uplink signal. For example, the User Info Acquisition Unit 206 may extract a User info List (for example, multiple User Info fields and a Special User Info field) from the Trigger frame input from the Error Correction Decoding Unit 203 and perform reception processing of the User info field based on terminal common information (for example, including the Trigger type) input from the Common Info Acquisition Unit 205. For example, if the User Info Acquisition Unit 206 determines that there is an assignment instruction addressed to terminal 200, it may acquire the Trigger type or information related to data generation from the User info field. The User Info Acquisition Unit 206 may, for example, output terminal-specific information and terminal common information to the Format Determination Unit 207, the Data Generation Unit 208, the Error Correction Decoding Unit 209, and the Modulation Unit 210.

[0070] Furthermore, if terminal 200 is an HE terminal, the User Info acquisition unit 206 may, for example, perform the reception processing of the User info field based on a format for HE terminals. Also, if terminal 200 is an EHT terminal, the User Info acquisition unit 206 may, for example, perform the reception processing of the User info field based on a format for EHT terminals.

[0071] The format determination unit 207 may determine the format of the uplink response signal (for example, a format corresponding to EHT TB PPDU or HE TB PPDU) based on information input from the User Info acquisition unit 206 (for example, including the Trigger type). The format determination unit 207 may output information regarding the determined format (for example, the TB PPDU format) to the data generation unit 208.

[0072] The data generation unit 208 generates a data signal of a specified type and size based on, for example, information about the TB PPDU format input from the format determination unit 207, common terminal information input from the User Info acquisition unit 206, and individual terminal information, and outputs the data signal to the error correction encoding unit 209.

[0073] The error correction coding unit 209, for example, based on information input from the User Info acquisition unit 206 (e.g., common terminal information and individual terminal information), performs error correction coding on the data signal input from the data generation unit 208 and outputs the coded signal to the modulation unit 210.

[0074] The modulation unit 210 modulates the signal input from the error correction coding unit 209 and outputs the modulated signal to the wireless transceiver unit 201 based on the information input from the User Info acquisition unit 206 (for example, common terminal information and individual terminal information). If the modulated signal is an OFDM signal, the terminal 200 (for example, the modulation unit 210) may form an OFDM signal by mapping the modulated signal to a frequency resource, performing IFFT processing, and adding a CP.

[0075] [Example of operation of AP100 and terminal 200] Next, an example of the operation of AP100 and terminal 200 according to this embodiment will be described.

[0076] Figure 11 is a flowchart showing an example of the operation of AP100 and terminal 200 in this embodiment.

[0077] In Figure 11, AP100 generates a Trigger frame for at least one terminal 200 (S101). AP100 may generate a Trigger frame that includes, for example, version information corresponding to terminal 200 (e.g., either HE or EHT version) in the Common Info field, and subfields whose settings differ depending on the version corresponding to terminal 200. For example, if the corresponding version of terminal 200 is EHT, AP100 may determine a different format from the format of the Common Info field defined in HE. In other words, for example, if the corresponding version of terminal 200 is EHT, AP100 may change the format of the Common Info field defined in HE. Alternatively, for example, AP100 may generate a Trigger type that includes version information by associating version information with a Trigger type.

[0078] AP100, for example, sends the generated Trigger frame to terminal 200, and terminal 200 receives the Trigger frame from AP100 (S102). The Trigger frame may include, for example, a Trigger type subfield value associated with version information, and subfields whose settings differ depending on the version.

[0079] Terminal 200 generates an uplink response signal based on the received Trigger frame (S103). Terminal 200 may determine the setting of a subfield in the Common Info field included in the Trigger frame based on version information (e.g., either HE or EHT version) associated with the Trigger type subfield value included in the Trigger frame. For example, if the corresponding version of Terminal 200 is EHT, Terminal 200 may determine a format different from the format of the Common Info field defined in HE. In other words, for example, if the corresponding version of Terminal 200 is EHT, Terminal 200 may change the interpretation of at least one subfield of the Common Info field defined in HE.

[0080] Terminal 200 transmits the generated uplink response signal to AP100 (S104). AP100 receives the uplink response signal for the Trigger frame, for example, based on the Trigger type of the Trigger frame (for example, the version information associated with the Trigger type).

[0081] [Example of operation related to Common Info field] The following describes an example of generating information for the Common Info field in AP100. For example, it describes an example of how to determine the EHT format to be applied to the Common Info field according to the version information in AP100.

[0082] <Example of version information notification> Version information may be communicated, for example, by the value of the Trigger type subfield. In other words, version information may be associated with the type of Trigger frame.

[0083] For example, AP100 and terminal 200 may set the Trigger type table shown in FIG. 9. In FIG. 9, each of Trigger type subfield value = 0 to 7 is the Trigger type defined in HE (for example, FIG. 5). Also, in FIG. 9, each of Trigger type subfield value = 8 to 9 is the Trigger type defined in EHT (in other words, the Trigger type not defined in HE).

[0084] For example, in FIG. 9, when the Trigger type subfield value is 7 (for example, a threshold) or less (in the case of 0 to 7), the associated version is HE, and when the Trigger type subfield value is greater than 7 (for example, in the case of 8 to 9), the associated version is EHT.

[0085] In this way, by associating the Trigger type with the version information, it becomes possible to notify the version information according to the value regarding the Trigger type included in the Trigger frame.

[0086] <Example of determining the format of the <Common Info field>> AP100 may determine the format (for example, field settings) of the Common Info field based on, for example, the version information associated with the Trigger type.

[0087] For example, when AP100 indicates a Trigger type corresponding to HE, it may determine the format of the Common Info field shown in FIG. 2.

[0088] On the other hand, for example, when AP100 specifies an EHT-compatible Trigger type, it may determine a format for some subfields of the Common Info field format shown in Figure 2 that differs from the format shown in Figure 2. For example, some subfields may contain information related to control information for EHT terminals. AP100 may set some subfields differently depending on whether it is HE-compatible or EHT-compatible.

[0089] Some subfields may be, for example, subfields not referenced by EHT terminals, or subfields relating to control information for HE terminals. For example, the format of an EHT-compatible Common Info field may be a format in which the interpretation of subfields not referenced by EHT terminals within the Common Info field defined in HE is changed to a format that provides information for EHT terminals. Subfields not referenced by EHT terminals may include, for example, at least one of the UL STBC subfield, the UL Spatial Reuse subfield, and the Doppler subfield.

[0090] In the following, for example, in an EHT-enabled Common Info field, a subfield with different settings from an HE-enabled Common Info field will be referred to as a "second trigger-dependent Common Info field (Trigger-dependent Common Info 2)".

[0091] Thus, in the Common Info field, AP100 may set some subfields to be subfields that depend on the trigger type (for example, a second trigger-dependent Common Info field) when the version is EHT. This reduces the number of fields (e.g., subfields) that the EHT terminal does not refer to in the trigger frame when an EHT-compatible trigger type is specified, thereby reducing the overhead of the trigger frame.

[0092] Figures 12 and 13 show an example of a Common Info field that applies when the Trigger type is EHT-compatible (in other words, when HE is not compatible).

[0093] For Common Info fields that apply when the Trigger type is HE-enabled (for example, Figure 2), in the example shown in Figure 12, the UL Spatial Reuse subfield (the subfield corresponding to B37-B52) is changed to Trigger dependent Common Info 2, and in the example shown in Figure 13, the UL STBC subfield (the field corresponding to B26) and the Doppler subfield (the subfield corresponding to B53) are changed to Trigger dependent Common Info 2.

[0094] In the example shown in Figure 12, AP100 and terminal 200 can utilize 16 bits as a second trigger-dependent common info field, which has the advantage of increasing the amount of information that can be notified to the EHT terminal compared to Figure 13 (e.g., 2 bits).

[0095] Furthermore, for example, the UL Spatial Reuse subfield may contain information for Spatial Reuse for HE terminals of an Overlapped BSS (OBSS), so there may be cases where the UL Spatial Reuse subfield cannot be used as Trigger dependent Common Info 2. In this case, for example, as shown in Figure 13, the two bits of the UL STBC subfield and Doppler subfield may be used as the second Trigger dependent Common Info field. This has the advantage of increasing the amount of information that can be notified to the EHT terminal without affecting Spatial Reuse of the OBSS HE terminal.

[0096] Here, within the trigger frame, for example, the Trigger Dependent Common Info subfield, or the User Info field that follows the Common Info field, may differ in field size and at least one of the bit positions of each piece of information depending on the trigger type. Terminal 200, for example, determines the trigger type, then identifies (or determines, decides) the bit positions of the Trigger Dependent Common Info field and the User Info field, and performs reception processing.

[0097] On the other hand, Common Info fields that can be set as a second Trigger-dependent Common Info field, such as the UL STBC subfield, UL Spatial Reuse subfield, or Doppler subfield shown in Figures 12 and 13, may be subfields whose size or bit position is not dependent on the Trigger type.

[0098] In this embodiment, for example, the settings (or definitions) of at least some of the subfields in the Common Info field that are transmitted independently of the Trigger type (or version information) (in other words, subfields that are different from the subfields that depend on the Trigger type) may differ depending on the version information. For example, AP100 and terminal 200 may reinterpret some of the information whose bit positions are defined independently of the Trigger type (or version information) based on the Trigger type (or version information).

[0099] As a result, even if the subfield settings are reinterpreted according to the trigger type (or version information), as shown in Figures 12 and 13, the bit positions extracted by terminal 200 for that subfield remain unchanged, thus simplifying the receiving process of terminal 200 (for example, the information extraction process).

[0100] Furthermore, when applying Trigger-dependent Common Info 2 in the case of EHT support, terminal 200 may use both the Trigger-dependent Common Info included in the case of HE support and the Trigger-dependent Common Info 2 set in the case of EHT support as common information dependent on the trigger type. This increases the amount of information (in other words, the amount of notification) that can be notified to terminal 200 by common information dependent on the trigger type without increasing overhead.

[0101] Furthermore, in HE, for example, there may be trigger types where the size of the Trigger dependent Common Info subfield is 0. Examples of trigger types where the size of the Trigger dependent Common Info subfield is 0 include Beamforming Report Poll (BFRP), Multi-User Block ACK Request (MU-BAR), Multi-User Request to Send (MU-RTS), Buffer Status Report Poll (BSRP), Bandwidth Query Report Poll (BQRP), and NDP Feedback Report Poll (NFRP).

[0102] Figures 12 and 13 show that, for example, even in the case of a Trigger type where the size of the Trigger dependent Common Info is 0, it is possible to transmit information for the EHT terminal using Trigger dependent Common Info 2 for the EHT terminal (for example, a subfield whose size and bit positions do not change).

[0103] Furthermore, the bit positions of subfields that are reinterpreted when EHT is supported (e.g., Trigger dependent Common Info 2) may differ depending on the Trigger type. For example, as shown in Figure 14, when the Trigger Type subfield value is 8, Trigger dependent Common Info 2 may be set in bits B37-B39 and the Reserved area in bits B40-B52 of the UL Spatial Reuse subfield, which does not need to be received by the EHT terminal. Also, for example, as shown in Figure 15, when the Trigger Type subfield value is 9, Trigger dependent Common Info 2 may be set in bits B37-B41 and the Reserved area in bits B42-B52 of the UL Spatial Reuse subfield, which does not need to be received by the EHT terminal. In this way, by setting some bits of Tigger dependent Common Info 2 and the Reserved area in other bits of subfields that the EHT terminal does not refer to in the HE definition, the Reserved area can be secured, improving the extensibility of future versions.

[0104] Note that the bit positions and sizes where Trigger Dependent Common Info 2 is set in Figures 14 and 15 are examples, and at least one of the bit positions and sizes may differ from those in Figures 14 and 15. Also, while Figures 14 and 15 describe the case where the UL Spatial Reuse subfield is set in two areas, Trigger Dependent Common Info 2 and the Reserved area, the number of areas to which it is set is not limited to two; it may be three or more areas.

[0105] Furthermore, if the EHT-compatible Trigger type is a Sounding NDP (for example, a Trigger type that instructs a response signal that does not generate data), then at least one definition (interpretation) of a subfield containing data generation information not used for NDP generation may differ from the HE definition. Figure 16 shows an example where the UL STBC subfield, LDPC Extra Symbol Segment subfield, Pre-FEC Padding Factor subfield, PE Disambiguity subfield, UL SpatialReuse subfield, and Doppler subfield shown in Figure 2 are set in Trigger Dependent Common Info 2. The subfields to which Trigger Dependent Common Info 2 is set are not limited to the examples shown in Figure 16.

[0106] <Example of a second trigger-dependent Common Info field> For example, if the trigger type is EHT-enabled (or HE-incompatible) and is an NDP for sounding, the trigger dependent Common Info 2 may include, for example, extended information (e.g., number of streams) regarding the number of EHT-Long Training field (LTF) symbols in the response signal (TB PPDU). Increasing the number of symbols through notification of Trigger Dependent Common Info 2 can improve channel estimation accuracy.

[0107] Alternatively, Trigger dependent Common Info 2 may include information regarding the EHT-LTF tone mapping interval. This would allow, for example, the EHT-LTF to be frequency-multiplexed by Distributed-FDMA among multiple AP100s.

[0108] Alternatively, Trigger-dependent Common Info 2 may include information regarding the EHT-LTF stream number used by each terminal 200 for reception, or information regarding the Tone position within the Tone mapping interval, in the Trigger-dependent User Info of the User Info field.

[0109] Furthermore, for example, if the EHT-compatible Trigger type is Multi-AP coordination, the Trigger dependent Common Info 2 may include information on the type of cooperative transmission, as shown below. This allows terminal 200 to send information corresponding to the type of cooperative transmission as a response signal, and AP 100 can improve the efficiency of cooperative communication control. Coordinated Spatial Reuse ·Coordinated Orthogonal Frequency Division Multiple Access Joint Transmissions Coordinated Beamforming

[0110] Furthermore, if the Trigger type is Multi-AP coordination, AP100 and terminal 200 may determine that they are EHT-compatible versions and may replace the field that is a User Info field in HE with a field containing information for EHT (for example, an AP Info field). For example, the AP Info field may include instructions for sending control information used for coordinated transmission from the AP scheduling the coordinated transmission (for example, also called a sharing AP) to the APs participating in the coordinated transmission (for example, also called a shared AP).

[0111] <Example of format determination process> This section describes how the format determination unit 207 of terminal 200 determines the TB PPDU format (for example, either EHT TB PPDU or HE TB PPDU format) according to the version information.

[0112] For example, if the Trigger type is of an HE-compatible type, the format determination unit 207 may determine the TB PPDU format according to the information indicated in at least one of the Common Info field and the User Info field (including, for example, the Special User Info subfield).

[0113] For example, the format determination unit 207 may determine the format based on information regarding the presence or absence of a Special User Info subfield indicated in the Common Info field. For example, the format determination unit 207 may apply EHT TB PPDU if it is indicated that a Special User Info subfield exists, and apply HE TB PPDU if it is indicated that a Special User Info subfield does not exist.

[0114] Alternatively, the format determination unit 207 may determine the format based, for example, on information regarding the transmission bandwidth allocation of the TB PPDU. For example, if allocation to Secondary 160MHz is instructed, the format determination unit 207 may apply EHT TB PPDU.

[0115] Furthermore, for example, if the Trigger type is of an EHT-compatible type, the format determination unit 207 may apply the EHT TB PPDU regardless of the information in the Common Info field and the User Info field.

[0116] The above explains an example of how the format determination process works.

[0117] In this embodiment, AP100 generates a Trigger frame in which the Common Info field contains information about the version of the wireless communication standard, such as HE or EHT, and a subfield whose settings differ depending on the version, and transmits it to terminal 200. Terminal 200 then determines the settings of the subfield in the Common Info field of the Trigger frame based on the information about the version of the wireless communication standard, such as HE or EHT, included in the Trigger frame.

[0118] According to this embodiment, for example, even when a new trigger type for EHT or a further version is added to HE, the format of the trigger frame can be appropriately set (or changed) according to the version, thereby suppressing an increase in overhead in the trigger frame.

[0119] (Embodiment 2) For example, in EHT, it is being considered to instruct an Aggregated-PPDU (A-PPDU) that frequency multiplexes the uplink response signal of the HE terminal (HE TB PPDU) and the uplink response signal of the EHT terminal (EHT TB PPDU) using a single trigger frame (see, for example, Non-Patent Document 6).

[0120] For example, A-PPDU may be performed within a 320MHz bandwidth. For instance, an AP can instruct A-PPDU by assigning frequency bandwidths based on the formats recognized by HE and EHT terminals, respectively, using a single trigger frame. As an example, an HE terminal supporting a maximum bandwidth of 160MHz may be assigned Primary 160MHz, and an EHT terminal supporting a maximum bandwidth of 320MHz may be assigned Secondary 160MHz. Note that the frequency bandwidth to which A-PPDU is applied is not limited to 320MHz; other bandwidths may also be used.

[0121] In Embodiment 1, if a trigger type that can be added in the EHT (a trigger type not supported by the HE terminal) is specified in the Trigger type subfield within the Common Info field, the HE terminal will stop processing the reception of the trigger frame. Therefore, if a trigger type not supported by the HE terminal is specified in the Trigger type subfield within the Common Info field, it may not be possible to specify an A-PPDU in a single trigger frame.

[0122] This embodiment describes a method for applying A-PPDU to response signals between an HE terminal and an EHT terminal in a trigger frame that instructs a new trigger frame (in other words, a trigger type not supported in HE) to an EHT terminal.

[0123] [Base station configuration] The configuration example of AP100 according to this embodiment may be the same as in Figure 8. For example, in AP100 according to this embodiment, the operation of the Trigger type setting unit 103 and the Common Info generation unit 104 may differ from that of Embodiment 1.

[0124] The Trigger type setting unit 103 may, for example, set an association between a Trigger type corresponding to the type of uplink response signal and information indicating the Trigger type within the Trigger frame (e.g., Trigger type subfield value), and may store information related to the set Trigger type (e.g., information in a table format).

[0125] In this embodiment, the Trigger type setting unit 103 may set, for example, a predefined Trigger type table for HE terminals (for example, Figure 5) and a Trigger type table for EHT terminals that are different from those for HE terminals (an example will be described later). Here, the Trigger type table for EHT terminals may include new Trigger types that HE terminals do not support. The Trigger type setting unit 103 outputs, for example, information about the set Trigger tables to the Common Info generation unit 104.

[0126] The Common Info generation unit 104 generates a Trigger type subfield that specifies the Trigger type for HE terminals and a subfield that specifies the Trigger type for EHT terminals (for example, called the "Trigger type 2 subfield") based on the Trigger type instruction input from the scheduling unit 101 and the Trigger type table input from the Trigger type setting unit 103. In other words, the Common Info generation unit 104 may set information about the type of Trigger frame (for example, the Trigger type subfield value) in the Common Info field of the Trigger frame using multiple subfields.

[0127] For example, the Trigger type subfield for HE terminals and the Trigger type 2 subfield for EHT terminals may be different. The Trigger type specified in the Trigger type subfield is the type associated with the HE-compatible version information, and the Trigger type specified in the Trigger type 2 subfield may be the type associated with the EHT-compatible version information.

[0128] The Common Info generation unit 104 generates a Common Info field that includes a Trigger type subfield and a Trigger type 2 subfield, and outputs the generated Common Info field to the Trigger frame generation unit 105.

[0129] The processing of other components in AP100 may be the same as, for example, the processing in Embodiment 1.

[0130] [Device Configuration] The configuration example of the terminal 200 according to this embodiment may be the same as that shown in Figure 10. For example, in the terminal 200 according to this embodiment, the operation of the Trigger type setting unit 204 and the Common Info acquisition unit 205 may differ from that of Embodiment 1.

[0131] The Trigger type setting unit 204 may, for example, output a Trigger type table for HE terminals to the Common Info acquisition unit 205 if terminal 200 is an HE terminal. Furthermore, if terminal 200 is an EHT terminal, the Trigger type setting unit 204 may output both a Trigger type table for HE terminals and a Trigger type table for EHT terminals to the Common Info acquisition unit 205.

[0132] The Common Info acquisition unit 205 extracts information from the Common Info field based on, for example, the Trigger frame input from the error correction decoding unit 203 and the Trigger type table input from the Trigger type setting unit 204, and acquires terminal common information for generating an uplink signal, including the type of uplink response signal (for example, the type of data to be transmitted or the duration of the uplink signal).

[0133] For example, when the terminal 200 is a HE terminal, the Common Info acquisition unit 205 may identify the Trigger type from the Trigger type subfield of the Common Info field using the Trigger type table for HE terminals. Also, for example, when the terminal 200 is an EHT terminal, the Common Info acquisition unit 205 may identify the Trigger type from the Trigger type subfield and the Trigger type 2 subfield of the Common Info field using the respective Trigger type tables for HE terminals and EHT terminals (examples will be described later).

[0134] The processing of other components in the terminal 200 may be the same as, for example, the processing in Embodiment 1.

[0135] <Trigger type table for EHT terminals> FIG. 17 is a diagram showing an example of the Trigger type table for EHT terminals included in a subfield different from the Trigger type subfield for HE terminals.

[0136] In FIG. 17, Trigger Type 2 subfield value = 0 means, for example, following the instruction of the Trigger Type subfield for HE terminals (e.g., FIG. 5). In this case, the EHT terminal acquires the Trigger type indicated in the Trigger type subfield. In other words, when Trigger Type 2 subfield value = 0, the same Trigger Type is indicated for both the EHT terminal and the HE terminal by the Trigger frame. Also, in FIG. 17, Trigger Type 2 subfield values = 1, 2 mean, for example, Trigger Types for EHT terminals (e.g., Sounding NDP transmission or cooperative communication) not supported by the HE terminal.

[0137] In this case, AP100 and terminal 200 may set the Trigger type subfield value for HE terminals (terminal 200 whose version corresponds to HE) using the Trigger type subfield (for example, Figure 5) in multiple subfields related to Trigger type within the Trigger frame, and set the Trigger type subfield value for EHT terminals (terminal 200 whose version corresponds to EHT) using both the Trigger type subfield (for example, Figure 5) and the Trigger type 2 subfield (for example, Figure 17).

[0138] Figure 18 shows another example of a Trigger type table for EHT terminals.

[0139] As shown in Figure 18, the Trigger type table for EHT terminals may include not only Trigger Types for EHT terminals (e.g., Trigger Type 2 subfield value = 8, 9) but also Trigger Types for HE terminals (e.g., Trigger Type 2 subfield value = 0~7). In this case, AP100 and terminal 200 may, for example, set the Trigger type subfield value for HE terminals using the Trigger type subfield (e.g., Figure 5) and the Trigger type subfield value for EHT terminals using the Trigger type 2 subfield (e.g., Figure 17) in multiple subfields related to Trigger type within the Trigger frame.

[0140] By individual settings of the Trigger type table (or Trigger type subfield) for HE terminals and EHT terminals, the AP100 can, for example, instruct different Trigger types for HE terminals and EHT terminals respectively. Therefore, since the Trigger types with high usage frequencies in each of the HE terminals and EHT terminals can be individually set, the system performance can be improved.

[0141] <Operation examples of the Common Info generation unit 104 and the Common Info acquisition unit 205> FIG. 19 is a diagram showing an example of the Common Info field according to the present embodiment.

[0142] As shown in FIG. 19, the Trigger type 2 subfield for EHT terminals may be set, for example, in the Reserved area within the Common Info field (e.g., FIG. 2) defined in HE. For example, in the Common Info field shown in FIG. 2 or FIG. 19, the fields (subfields) corresponding to B56 to B59 are subfields with different settings according to the version of the wireless communication standard (e.g., HE or EHT).

[0143] Also, for example, the sizes of the Trigger Dependent Common Info subfield and the Trigger Dependent User Info subfield for EHT terminals may be made to match the sizes for HE terminals. Thereby, the backward compatibility of EHT can be maintained.

[0144] [[ID=@18]]For example, the HE terminal may identify the Trigger type based on, for example, the Trigger type subfield (e.g., B0 to B3) shown in FIG. 19. Note that since the HE terminal interprets the Trigger Type 2 subfield shown in FIG. 19 as the Reserved area, it does not have to receive the Trigger Type 2 subfield.

[0145] Furthermore, for example, the EHT terminal receives the Trigger type 2 subfield (e.g., B56-B59) shown in Figure 19. For example, when referring to the Trigger type table shown in Figure 17, if the EHT terminal is instructed to use Trigger Type 2 subfield value = 0, it may further identify the Trigger type based on the Trigger type subfield (e.g., B0-B3) shown in Figure 19. Also, for example, when referring to the Trigger type table shown in Figure 18, the EHT terminal identifies the Trigger type based on the Trigger type 2 subfield and does not need to receive the Trigger type subfield (e.g., B0-B3).

[0146] The AP100 can, for example, instruct the HE terminal to use a different trigger type than the EHT terminal, even if the HE terminal is not supported by the EHT terminal. This means that the HE terminal does not have to stop receiving trigger frames based on the trigger type for the HE terminal, even if the trigger type for the EHT terminal is not supported by the HE terminal. Therefore, for example, an uplink response signal is generated on both the EHT terminal and the HE terminal, making A-PPDU applicable.

[0147] Therefore, according to this embodiment, AP100 can instruct A-PPDU to multiple terminals 200, including HE terminals and EHT terminals, in a single trigger frame that instructs a new trigger frame (in other words, a trigger type not supported in HE) for an EHT terminal.

[0148] Furthermore, control information regarding A-PPDU may be instructed to each terminal 200 in any field within the Trigger frame (for example, the User Info field).

[0149] Furthermore, the Trigger type 2 subfield for EHT terminals is included in a subfield (e.g., the Reserved area) that is transmitted regardless of the Trigger type in the Common Info field. Therefore, the bit position for extracting the Trigger type for EHT terminals does not change regardless of the Trigger type, thus simplifying the reception processing at terminal 200.

[0150] The embodiments of this disclosure have been described above.

[0151] (Other embodiments) (1) In each of the embodiments described above, the new trigger type for HE is not limited to the trigger type newly added in EHT. In other words, the version of the wireless communication standard is not limited to HE and EHT, but may be other versions. For example, one aspect of this disclosure may similarly be applied to new trigger types added in a further future version of EHT (e.g., referred to as EHT+). In that case, the operation of the EHT terminal in the embodiments described above may be replaced with the operation of a terminal corresponding to EHT+ (e.g., an EHT+ terminal).

[0152] For example, AP100 and terminal 200 may have different Common Info field formats depending on whether the Trigger type is EHT+ compatible (a new Trigger type supported in EHT+), EHT compatible, or HE compatible (for example, the meaning of some subfields may be changed).

[0153] This allows different formats of Common Info fields to be applied between EHT+ terminals and EHT or HE terminals, achieving the same effects as in the embodiment described above.

[0154] Furthermore, the format of the Common Info field is not limited to two types of settings between EHT+ compatibility and EHT or HE compatibility; it may also be three types, or even four or more, between EHT+ compatibility, EHT compatibility, and HE compatibility.

[0155] (2) In the embodiments described above, an example was given in which the format of the Common Info field is set according to the version information associated with the Trigger type. However, the invention is not limited to this, and for example, some subfields of the format of the User Info field may be set according to the version information associated with the Trigger type.

[0156] For example, if the trigger frame specifies a Sounding NDP, which is an EHT-compatible trigger type, then if the trigger type is HE-compatible (e.g., Figure 3), the reserved area subfield (e.g., B25) may include the EHT-LTF stream number ("Number of Spatial Streams" subfield), as shown in Figure 20.

[0157] Note that the subfield set in the User Info field according to the version information is not limited to the EHT-LTF stream number, but may contain other information as well.

[0158] Furthermore, in each of the embodiments described above, for example, some subfields of the Special User Info field format may be set according to the version information associated with the Trigger type. For example, if an EHT-compatible Trigger type is indicated in the Trigger frame, and the Trigger type is HE-compatible (for example, Figure 4), a second Trigger dependent Common Info field (Trigger dependent Common Info 2) may be set in the Reserved area subfield (for example, B37-B39), as shown in Figure 21.

[0159] Furthermore, the subfield set in the Special User Info field according to the version information is not limited to the second Trigger Dependent Common Info field, but may be set in other fields. Also, the subfield set in the Special User Info field according to the version information may be at least one bit of the Reserved area (e.g., B37-B39) in the case of HE support.

[0160] (3) In the embodiments described above, an NDP for sounding and a trigger type for coordinating communication were described as examples of EHT-compatible trigger types, but trigger types that support EHT and beyond are not limited to these.

[0161] An example of a Trigger type set after EHT may include a type that prompts data transmission with uplink beamforming applied. In this case, the User Info field may include beamforming information to be applied to terminal 200.

[0162] (4) In each of the embodiments described above, a method for setting (for example, changing) the format of the Common Info field according to the Trigger type associated with the version information, such as HE compatibility or EHT compatibility, was explained. However, the information associated with the version information is not limited to the Trigger type and may be other information.

[0163] For example, information of any type notified by the trigger frame may be associated with version information, and at least one format of the Common Info field, User Info field, and Special User Info field may be set according to the information of that type.

[0164] Figure 22 shows an example of an HE-enabled User Info field used when the Trigger type is NFRP (a type that instructs terminal 200 to send an NDP feedback report).

[0165] The "Feedback Type" subfield shown in Figure 22 contains information about the type of feedback to be given to the multiple terminals 200 instructed by the Starting AID. HE supports one type of Feedback Type, for example, Resource request. If an HE terminal is instructed by AP100 to have Resource request as the Feedback Type, it may hold the data to be sent and, if requesting resource allocation, may feed back an NDP as a response signal to AP100.

[0166] Here, EHT or EHT+ may support new Feedback Types. For example, as shown in Figure 23, EHT may add Acknowledgment (information about whether the data was decoded correctly) as a new value for Feedback Type.

[0167] In this case, for example, similar to Embodiment 1, when AP100 sends an Acknowledgment as Feedback Type to an EHT terminal, it may set the format of the User Info field according to the EHT-compatible version. Also, when an EHT terminal receives an Acknowledgment as Feedback Type, it may perform reception processing based on a User Info field format according to the EHT-compatible version that differs from the HE-compatible format. For example, as shown in Figure 24, in the User Info field according to the EHT-compatible version, a part of the Reserved area in HE may be set (e.g., changed) to the TID subfield (an identifier representing the type of traffic). This allows AP100 to feed back Acknowledgment information for the traffic type indicated by the TID to the EHT terminal. Also, when an HE terminal receives an Acknowledgment as Feedback Type, it may cancel the reception processing.

[0168] Alternatively, for example, similar to Embodiment 2, AP100 may individually specify the Feedback Type for EHT terminals and HE terminals using different subfields. For example, as shown in Figure 25, a portion of the Reserved area in HE may be set (e.g., modified) to the Feedback Type subfield for EHT terminals (e.g., Feedback Type 2 subfield) and the TID subfield. This allows AP100 to individually specify the Feedback Type for HE terminals and EHT terminals with a single Trigger frame, similar to Embodiment 2. For example, AP100 may instruct HE terminals to send a Resource request and EHT terminals to send an Acknowledgment with a single Trigger frame.

[0169] Note that the Feedback type for EHT terminals is not limited to Acknowledgement, but may include other types of information. Also, the information set for the Feedback type for EHT terminals is not limited to TID, but may include other information.

[0170] (5) Further newer versions of EHT have been described using the term "EHT+", but are not limited to this term and other terms may be used.

[0171] The transmission access method for the uplink response signal to the trigger frame is not limited to OFDMA, but may be other methods.

[0172] Furthermore, although the above embodiment was described based on the 11be format as an example, the format to which one embodiment of this disclosure is applied is not limited to the 11be format. One embodiment of this disclosure may, for example, be applied to IEEE 802.11bd (NGV (Next Generation V2X)), which is the next-generation standard to the automotive standard IEEE 802.11p.

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

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

[0175] Furthermore, if advancements in semiconductor technology or related technologies lead to the emergence of integrated circuit technologies that replace LSIs, then naturally, these technologies could be used to integrate functional blocks. The application of biotechnology, for example, is a possible possibility.

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

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

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

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

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

[0181] A base station according to one embodiment of the present disclosure comprises a control circuit that generates an uplink transmission control signal, which includes in a field common to multiple terminals information about the version of the wireless communication standard and subfields whose settings differ according to the version, and a transmission circuit that transmits the control signal.

[0182] In one embodiment of the present disclosure, the version information is associated with the type of control signal.

[0183] In one embodiment of the present disclosure, if the value relating to the type is less than or equal to a threshold, the version is High Efficiency (HE), and if the value is greater than the threshold, the version is Extreme High Throughput (EHT).

[0184] One embodiment of the present disclosure further comprises a receiving circuit that receives a response signal to the control signal based on the version associated with the type.

[0185] In one embodiment of the present disclosure, the control circuit causes the settings of at least some of the subfields in the common field that are different from the first subfield which depends on the type of control signal, to vary according to the version.

[0186] In one embodiment of the present disclosure, the subfields are at least one of the UL Space Time Block Coding (STBC) subfield, the UL Spatial Reuse subfield, the Doppler subfield, and the Reserved subfield.

[0187] In one embodiment of the present disclosure, the control circuit, when the version is Extreme High Throughput (EHT), sets some of the subfields to a second subfield that depends on the type.

[0188] In one embodiment of the present disclosure, the transmitting circuit transmits type-dependent information using both the first subfield and the second subfield.

[0189] In one embodiment of the present disclosure, the control circuit sets information regarding the type of the control signal in the common field using a plurality of subfields.

[0190] In one embodiment of the present disclosure, the control circuit sets information regarding the type of terminal for which the version corresponds to High Efficiency (HE) using a first subfield, and sets information regarding the type of terminal for which the version corresponds to Extreme High Throughput (EHT) using a second subfield.

[0191] In one embodiment of the present disclosure, the second subfield is set in the Reserved region of the control signal when the version is HE.

[0192] In one embodiment of the present disclosure, the control circuit sets the type information for a terminal whose version corresponds to EHT using both the first subfield and the second subfield.

[0193] A terminal according to one embodiment of the present disclosure includes a receiving circuit for receiving an uplink transmission control signal, which has a field common to multiple terminals that includes information about the version of the wireless communication standard and subfields whose settings differ according to the version, and a control circuit that determines the settings based on the information about the version.

[0194] In a communication method according to one embodiment of the present disclosure, the base station generates an uplink transmission control signal that includes in a field common to multiple terminals information about the version of the wireless communication standard and subfields whose settings differ according to the version, and transmits the control signal.

[0195] In a communication method according to one embodiment of the present disclosure, a terminal receives an uplink transmission control signal, which includes in a field common to multiple terminals information about the version of the wireless communication standard and subfields whose settings differ according to the version, and determines the settings based on the information about the version.

[0196] All disclosures in the specification, drawings, and abstract contained in the Japanese application 2021-081515, filed on 13 May 2021, are incorporated herein by reference. [Industrial applicability]

[0197] One embodiment of this disclosure is useful for wireless communication systems. [Explanation of symbols]

[0198] 100 AP 101 Scheduling Unit 102 User Info generation section 103,204 Trigger type setting section 104 Common Info generation section 105 Trigger frame generation section 106,209 Error Correction Encoding Unit 107,210 Modulation section 108,201 Wireless Transceiver Unit 109,202 Demodulation section 110,203 Error Correction and Decoding Unit 111 Terminal Information Acquisition Unit 200 terminals 205 Common Info Acquisition Department 206 User Info acquisition section 207 Format determination section 208 Data Generation Unit

Claims

1. A control circuit that generates a control signal to control uplink transmission, The system comprises a transmitting circuit that transmits the aforementioned control signal, The control signal includes common information including a first subfield and a second subfield, the first subfield and the second subfield are used to set information about the type of the control signal, the second subfield indicates information about the version of the wireless communication standard, and the control signal further includes subfields whose settings differ according to the version. Base station.

2. The information regarding the version is associated with the type of control signal. The base station according to claim 1.

3. The system further comprises a receiving circuit that receives a response signal to the control signal based on the version associated with the aforementioned type, The base station according to claim 2.

4. The control circuit makes the settings of at least a portion of the third subfield, which is different from the first subfield relating to the type of control signal, in the common information, different according to the version. The base station according to claim 1.

5. The third subfield is at least one of the following: UL Space Time Block Coding (STBC) subfield, UL Spatial Reuse subfield, Doppler subfield, and Reserved subfield. The base station according to claim 4.

6. The control circuit, when the version is Extreme High Throughput (EHT), sets the third subfield to the second subfield relating to the type. The base station according to claim 4.

7. The transmitting circuit transmits information about the type using both the first subfield and the second subfield. The base station according to claim 6.

8. The second subfield is set in the Reserved region of the control signal when the version is High Efficiency (HE). The base station according to claim 1.

9. The control circuit sets information regarding the type of control signal for a terminal whose version supports Extreme High Throughput (EHT) using both the first subfield and the second subfield. The base station according to claim 1.

10. The base station is, Generate a control signal to control uplink transmission, A communication method for transmitting the aforementioned control signal, The control signal includes common information including a first subfield and a second subfield, the first subfield and the second subfield are used to set information about the type of the control signal, the second subfield indicates information about the version of the wireless communication standard, and the control signal further includes subfields whose settings differ according to the version. Communication method.

Images