Base station and communication method

Abstract

This base station comprises: a control circuit which generates a control signal for uplink transmission including, in a field common to a plurality of terminals, information pertaining to a version of the wireless communication specification and a subfield that is differently configured according to the version; and a transmission circuit which transmits the control signal.

Description

[Technical Field]

[0001] The present disclosure relates to a base station, a terminal, and a communication method. [Background technology]

[0002] The Institute of Electrical and Electronics Engineers (IEEE) is currently studying the IEEE 802.11be (hereinafter referred to as "11be") standard for next-generation wireless local area networks (LANs), which will be the successor to the IEEE 802.11ax (hereinafter referred to as "11ax"). For example, IEEE 802.11ax is also known as High Efficiency (HE), and IEEE 802.11be is also known as Extreme High Throughput (EHT). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] IEEE P802.11be / D0.4 [Non-patent document 2] IEEE P802.11ax / D8.0 [Non-patent document 3] IEEE 802.11-21 / 0259r4, “Proposed Draft Specification for Trigger frame for EHT” [Non-patent document 4] IEEE 802.11-20 / 1672r2, “UL Beamforming for TB PPDUs in 11be” [Non-patent document 5] IEEE 802.11-19 / 0804r0, “Multi-AP Transmission Procedure” [Non-patent document 6] IEEE 802.11-21 / 0366r3, “Discussion on HE or EHT variant differentiation of a trigger frame” Summary of the Invention

[0004] However, there has been insufficient consideration given to a method for setting the format of a control signal that controls uplink transmission in wireless communication such as wireless LAN.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a base station and a communication method that can appropriately set the format of a control signal that controls uplink transmission.

[0006] A base station according to one embodiment of the present disclosure includes a control circuit that generates a control signal for uplink transmission, the control signal including, in a field common to multiple terminals, information regarding the version of a wireless communication standard and a subfield with settings that differ depending on the version, and a transmission circuit that transmits the control signal.

[0007] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

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

[0009] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0010] [Figure 1] An example of a trigger frame [Figure 2] A diagram showing an example of the Common Info field [Figure 3] An example of a User Info field [Figure 4] A diagram showing an example of the Special User Info field [Figure 5] An example of a trigger type [Figure 6] Block diagram showing a partial configuration example of an access point (AP) [Figure 7] Block diagram showing an example of the configuration of a part of a terminal [Figure 8] Block diagram showing an example of an AP configuration [Figure 9] FIG. 1 shows an example of a trigger type according to the first embodiment. [Figure 10] Block diagram showing an example of a terminal configuration [Figure 11] Sequence diagram showing an example of the operation of an AP and a terminal [Figure 12] FIG. 1 is a diagram showing an example of a Common Info field according to the first embodiment; [Figure 13] FIG. 1 is a diagram showing an example of a Common Info field according to the first embodiment; [Figure 14] FIG. 1 is a diagram showing an example of a Common Info field according to the first embodiment; [Figure 15] FIG. 1 is a diagram showing an example of a Common Info field according to the first embodiment; [Figure 16] FIG. 1 is a diagram showing an example of a Common Info field according to the first embodiment; [Figure 17] FIG. 10 is a diagram showing an example of a trigger type according to the second embodiment. [Figure 18] FIG. 10 is a diagram showing an example of a trigger type according to the second embodiment. [Figure 19] FIG. 10 is a diagram showing an example of a Common Info field according to the second embodiment. [Figure 20] FIG. 10 is a diagram showing an example of a User Info field according to the second embodiment; [Figure 21] FIG. 10 is a diagram showing an example of a Special User Info field according to the second embodiment; [Figure 22] An example of a User Info field [Figure 23] FIG. 10 is a diagram showing an example of a Feedback type subfield according to the second embodiment. [Figure 24] An example of a User Info field [Figure 25] An example of a User Info field DETAILED DESCRIPTION OF THE INVENTION

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

[0012] 11ax (e.g., HE) specifies the introduction of Orthogonal Frequency Division Multiple Access (e.g., OFDMA) in the uplink (UL). For example, an access point (AP, also called a "base station") transmits a control signal (hereinafter referred to as a "trigger frame") instructing transmission of an uplink signal (e.g., an uplink OFDMA signal) to multiple terminals (STAs, also called "non-AP STAs") 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 that instructs multiple terminals to transmit uplink signals (e.g., uplink OFDMA signals) (see, for example, Non-Patent Documents 1 and 3).

[0014] Fig. 1 is a diagram showing an example of a Trigger frame. As shown in Fig. 1, the Trigger frame includes a field (for example, a "Common Info field") that includes information common to multiple terminals that are OFDMA multiplexed, 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 (for example, "User Info field") that include information individual (or unique) to a terminal.

[0015] FIG. 2 is a diagram showing an example of the configuration of a Common Info field (for example, a Common Info field format and an EHT variant) considered in 11be (for example, EHT). FIG. 3 is a diagram showing an example of the configuration of a User Info field (for example, a User Info field format and an EHT variant) considered in 11be (EHT) (for example, see Non-Patent Document 3). FIG. 4 is a diagram showing an example of the configuration of a Special User Info field including information for a terminal (hereinafter referred to as an "EHT terminal") compatible with 11be (for example, EHT) (for example, see Non-Patent Document 3).

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

[0017] Also, for example, the "Trigger Dependent Common Info" subfield in the Common Info field shown in FIG. 2 may include information that depends on the Trigger type (for example, common information).

[0018] Furthermore, in 11be (EHT), for example, a new trigger type different from the trigger type defined in 11ax may be introduced.

[0019] For example, the application of uplink beamforming to an uplink response signal to a 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 terminals to transmit a sounding null data packet (NDP) so that the AP can acquire precoding information used by each terminal, or a trigger type that includes precoding information to be applied to the uplink response signal in the user info field.

[0020] The uplink response signal may also be called, for example, an EHT trigger-based physical layer protocol data unit (EHT TB PPDU) or an EHT TB PPDU.

[0021] Furthermore, in EHT, for example, 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 sending and receiving data), is being considered (see, for example, Non-Patent Document 5). To realize cooperative communication, it is possible to introduce a new trigger type that instructs terminals or APs participating in cooperative transmission on control information related to cooperative communication.

[0022] For example, when a new Trigger type (for example, the transmission of the Sounding NDP or the control of cooperative communication described above) is introduced in EHT or a further future version (hereinafter, for example, referred to as "EHT+"), there is a possibility that one of the reserved areas (8 to 15) of the Trigger type subfield value in the Common Info field shown in Fig. 5 may be used. As an example, when the Trigger type subfield value = 8, a Trigger type instructing the transmission of the Sounding NDP may be set, and when the Trigger type subfield value = 9, a Trigger type relating to the 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, in the EHT, a method for adding a new trigger type to the HE has not been fully studied. For example, there is room for study on the format setting (e.g., field (or subfield) setting) of the trigger frame (e.g., at least one of the Common Info field and the User Info field) when adding a new trigger type to the HE in the EHT.

[0024] In a non-limiting embodiment of the present disclosure, an example of setting a signal format will be described.

[0025] (Embodiment 1) For example, a Trigger type indicated using a Reserved field (8 to 15) of the Trigger type subfield value in the Common Info field defined in the HE is an unsupported Trigger type for a terminal corresponding to the HE (e.g., referred to as an "HE terminal"). For example, in the HE specifications, when an unsupported Trigger type (e.g., a Trigger type value corresponding to the Reserved field) is indicated by the AP, the HE terminal may perform an operation to stop receiving the Trigger frame.

[0026] For example, when a new Trigger type added in the EHT is indicated using a Trigger type subfield in a Common Info field defined in the HE, the HE terminal stops receiving the Trigger frame, and the EHT terminal continues receiving the Trigger frame. After receiving the Trigger frame, the EHT terminal may transmit an EHT TB PPDU (TB PPDU in a format compatible with the EHT) as a response signal to the AP, for example.

[0027] Here, the Trigger frame includes control information for the HE terminal (for example, control information for HE TB PPDU transmission). Therefore, as described above, when a new Trigger type for the EHT terminal is specified, information in some subfields including control information for the HE terminal (for example, for HE TB PPDU transmission) may be 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 in the Common Info field shown in Fig. 2. These subfields include information for HE terminals, and can be subfields (reserved areas) that do not need to be received by EHT terminals that respond with EHT TB PPDUs (see, for example, Non-Patent Documents 1 and 3).

[0029] In this way, when a new Trigger type for an EHT terminal is notified using the reserved area of ​​the Trigger type subfield value in the Common Info field defined in the HE, some subfields may be useless information for the EHT terminal, which may increase overhead.

[0030] In a non-limiting embodiment of the present disclosure, a method for suppressing an increase in overhead in a trigger frame when a new trigger type for an EHT terminal is notified will be described.

[0031] [Wireless communication system configuration] The wireless communication system according to this embodiment may include, for example, AP 100 shown in Fig. 6 and terminal 200 shown in Fig. 7. There may be two or more APs 100 and two or more terminals 200 in the wireless communication system. AP 100 may, for example, transmit a Trigger frame instructing terminal 200 to perform uplink OFDMA transmission. Terminal 200 may receive the Trigger frame and transmit an uplink OFDMA signal to AP 100 using a resource instructed by the received Trigger frame.

[0032] Here, the AP 100 may be, for example, an AP that supports EHT and has backward compatibility with HE (for example, an AP that also supports HE).

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

[0034] Fig. 6 is a block diagram showing a partial configuration example of an AP100 according to an embodiment of the present disclosure. In the AP100 shown in Fig. 6, a control unit (e.g., corresponding to a control circuit) generates an uplink transmission control signal (e.g., a Trigger frame) including, in a field common to multiple terminals (e.g., a Common Info field), information about the version of the wireless communication standard and a subfield with settings that vary depending on the version. A transmission unit (e.g., corresponding to a transmission circuit) transmits the control signal.

[0035] 7 is a block diagram illustrating a configuration example of a portion of a terminal 200 according to an embodiment of the present disclosure. In the terminal 200 illustrated in FIG. 7, a receiver (e.g., corresponding to a receiver circuit) receives an uplink transmission control signal (e.g., a trigger frame) that includes, in a field common to multiple terminals (e.g., a common info field), information about the version of the wireless communication standard and subfields whose settings vary depending on the version. Furthermore, a controller (e.g., corresponding to a control circuit) determines settings based on the information about the version.

[0036] [AP100 configuration example] The AP 100 generates a trigger frame that instructs the terminal 200 to transmit an uplink signal such as a data signal or an NDP signal, and transmits the trigger frame to the terminal 200, for example.

[0037] Fig. 8 is a block diagram showing an example configuration of AP 100. AP 100 shown in Fig. 8 may include, for example, a scheduling unit 101, a User Info generating unit 102, a Trigger type setting unit 103, a Common Info generating unit 104, a Trigger frame generating unit 105, an error correction encoding 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 generating unit 102, the Trigger type setting unit 103, the Common Info generating unit 104, the Trigger frame generating unit 105, and the terminal information acquiring unit 111 may be included in an access control unit (e.g., a Medium Access Control (MAC) processing unit).

[0039] Furthermore, at least one of the scheduling unit 101, the User Info generating unit 102, the Trigger type setting unit 103, the Common Info generating unit 104, the Trigger frame generating unit 105, the error correction encoding unit 106, the modulating unit 107, the demodulating unit 109, the error correction decoding unit 110, and the terminal information acquiring unit 111 shown in Fig. 8 may be included in, for example, the control unit shown in Fig. 6. Furthermore, the radio transmitting and receiving unit 108 shown in Fig. 8 may be included in, for example, the transmission unit shown in Fig. 6.

[0040] The scheduling unit 101 may perform scheduling for, for example, the terminals 200. For example, the scheduling unit 101 may determine a trigger type corresponding to the type of uplink response signal and information related to the radio resources of the uplink response signal based on control information such as a version supported by the terminal 200 (for example, HE or EHT) or radio quality information specific to each band, which is included in the terminal information input from the terminal information acquisition unit 111. The information related to the radio resources of the uplink response signal may include, for example, an allocated band, a modulation and coding scheme (MCS: Modulation and Coding Scheme), and a target reception level. The scheduling unit 101 outputs, for example, the information related to the determined trigger type and the radio resource information of each terminal 200 to the User Info generation unit 102 and the Common Info generation unit 104.

[0041] The User Info generating unit 102 may generate, for example, control information to be included in a User Info field individual to the terminal 200 (or STA). The User Info generating unit 102 may generate information regarding the User Info field individual to the terminal 200 based on a specified format, for example, and may generate information regarding a User Info List including a User Info field for each of the multiple terminals 200. The User Info generating unit 102 may output the information regarding the User Info List to the Trigger frame generating unit 105, for example.

[0042] 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 in the trigger frame (for example, a trigger type subfield value), and may hold information related to the set trigger type. The trigger type setting unit 103 may output information related to the set trigger type to the common info generating unit 104.

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

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

[0045] The Trigger type (also referred to as a Trigger frame variant, for example) indicated in the Trigger type subfield may be uniquely associated with information (referred to as version information, for example) relating to the version (also referred to as a "generation") of a WLAN standard (in other words, a communication standard), such as HE compatibility or EHT compatibility. The Common Info generating unit 104 may generate a Common Info field including the Trigger type subfield, for example, based on a format (for example, field settings) according to the version information associated with the Trigger type, and output information relating to the generated Common Info field to the Trigger frame generating unit 105.

[0046] For example, when specifying a Trigger type compatible with HE (which may also be compatible with EHT terminals), the Common Info generating unit 104 may generate the Common Info field based on the format shown in Fig. 2. Also, when specifying a Trigger type compatible with EHT (for example, not compatible with HE terminals), the Common Info generating unit 104 may generate the Common Info field by setting subfields that can be received by EHT terminals (for example, some subfields in the format shown in Fig. 2) differently from when compatible with HE. An example of setting the Common Info field will be described later.

[0047] It should be noted that the term "setting" of a field (eg, subfield) in a Trigger frame may be replaced with other terms such as "definition" or "interpretation."

[0048] 1, the trigger frame generation unit 105 may generate a trigger frame including information of the Common Info field input from the Common Info generation unit 104 and information of the User Info List (e.g., multiple User Info fields) input from the User Info generation unit 102. In addition to the Common Info field and the User Info List, the trigger frame may include at least one of a MAC header, padding, and a frame check sequence (FCS). The trigger frame generation unit 105 may output the generated trigger frame to the error correction coding unit 106, for example.

[0049] The error correction coding unit 106 performs error correction coding on the transmission data signal including the trigger frame input from the trigger frame generation unit 105 , for example, and outputs the coded signal to the modulation unit 107 .

[0050] Modulation section 107 performs modulation processing on the signal input from error correction coding section 106, for example, and outputs the modulated signal to radio transmission / reception section .

[0051] In addition, if the modulated data signal is an Orthogonal Frequency Division Multiplexing (OFDM) signal, AP100 (e.g., modulation unit 107) may form an OFDM signal by mapping the modulated signal to a specified frequency resource, performing an Inverse Fast Fourier Transform (IFFT) process to convert it into a time waveform, and adding a Cyclic Prefix (CP).

[0052] Radio transmitting / receiving section 108 performs radio transmission processing such as D / A conversion and up-conversion to a carrier frequency on the modulated signal input from modulation section 107, and transmits the signal after radio transmission processing via an antenna to terminal 200. Radio transmitting / receiving section 108 also receives, for example, a signal transmitted from terminal 200 via an antenna, performs radio reception processing on the received signal such as down-conversion to baseband and A / D conversion, and outputs the signal after radio reception processing to demodulation section 109.

[0053] The demodulation unit 109 performs demodulation processing on the signal input from the wireless transmission / reception unit 108, for example, and outputs the demodulated signal to the error correction decoding unit 110. Note that if the signal input to the demodulation unit 109 is an OFDM signal, the AP 100 (for example, the demodulation unit 109) may perform CP removal processing and Fast Fourier Transform (FFT) processing.

[0054] For example, the error correction decoding unit 110 decodes the signal input from the demodulation unit 109 to obtain a received data signal from the terminal 200. For example, if the decoded received data includes the above-mentioned terminal information, the error correction decoding unit 110 outputs decoded data including the terminal information to the terminal information acquisition unit 111.

[0055] The terminal information acquisition unit 111 may acquire terminal information (for example, version information of the terminal 200 and radio quality information specific to the specified band) 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 related to the terminal 200, and may be read as "capability information."

[0056] [Example of terminal 200 configuration] The terminal 200 receives, for example, a trigger frame from the AP 100 instructing transmission of an uplink signal such as a data signal or an NDP signal, and transmits, to the AP 100, an uplink response signal in response to the trigger frame.

[0057] Fig. 10 is a block diagram showing an example configuration of terminal 200. Terminal 200 shown in Fig. 10 may include, for example, radio transceiver 201, demodulator 202, error correction decoder 203, trigger type setting unit 204, common info acquirer 205, user info acquirer 206, format determiner 207, data generator 208, error correction encoder 209, and modulator 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 an access control unit (for example, a MAC processing unit).

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

[0060] Radio transmitting / receiving section 201 receives a received signal via an antenna, performs radio reception processing such as down-conversion and A / D conversion on the received signal, and outputs the signal after radio reception processing to demodulation section 202. Radio transmitting / receiving section 201 also performs radio transmission processing such as up-conversion and D / A conversion on a signal input from modulation section 210, and transmits the signal after radio transmission processing from an antenna.

[0061] Demodulation section 202 performs demodulation processing on received data input from radio transmission / reception section 201, for example, and outputs the demodulated signal to error correction decoding section 203. Note that if the signal input to demodulation section 202 is an OFDM signal, terminal 200 (e.g., demodulation section 202) may perform CP removal processing and FFT processing, for example.

[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 a received data signal. Furthermore, the error correction decoding unit 203 may, for example, output a 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 the same operation as, for example, the trigger type setting unit 103 of the AP 100. For example, the trigger type setting unit 204 may output information on predefined trigger types (for example, a trigger type table) to the common info acquisition unit 205.

[0064] The Common Info acquisition unit 205 may acquire terminal common information related to the generation of an uplink signal by extracting information corresponding to the Common Info field from the Trigger frame input from the error correction decoding unit 203, for example, based on information (for example, a Trigger type table) input from the Trigger type setting unit 204. The terminal common information may include, for example, the type of the uplink response signal (for example, data) and the time length of the uplink signal.

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

[0066] For example, an HE terminal that supports the Trigger type table shown in FIG. 5 may suspend reception processing when receiving a value of Trigger type subfield value=8 or greater, and may perform reception processing of the Common Info field when receiving a value of Trigger type subfield value=7 or less.

[0067] Also, for example, when terminal 200 is an EHT terminal, similar to the operation of AP 100, terminal 200 may change the setting of the format of the Trigger frame (for example, Common Info field) depending on the Trigger type indicated by the Trigger type subfield. For example, when the Trigger type is an HE-compatible type, terminal 200 may perform reception processing of the Common Info field based on the definition of the format shown in FIG. 2. On the other hand, for example, when the Trigger type is an EHT-compatible type (in other words, when HE is not compatible), terminal 200 may perform reception processing of the Common Info field based on a format in which the settings of some subfields of the format shown in FIG. 2 have been changed. Note that when 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] For example, the User Info acquisition unit 206 may extract information corresponding to the User Info field from the Trigger frame input from the error correction decoding unit 203, and acquire terminal-individual information related to the generation of an uplink signal. For example, the User Info acquisition unit 206 may extract a User Info List (e.g., 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 (e.g., including the Trigger type) input from the Common Info acquisition unit 205. For example, when the User Info acquisition unit 206 determines that there is an allocation instruction addressed to the terminal 200, it may acquire information related to the Trigger type or data generation from the User Info field. For example, the User Info acquisition unit 206 may output the terminal-individual information and the terminal common information to the format determination unit 207, the data generation unit 208, the error correction coding unit 209, and the modulation unit 210.

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

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

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

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

[0074] Modulation section 210 modulates the signal input from error correction coding section 209, and outputs the modulated signal to radio transmission / reception section 201 based on information input from User Info acquisition section 206 (for example, terminal common information and terminal individual information). When the modulated signal is an OFDM signal, terminal 200 (for example, modulation section 210) may form the OFDM signal by mapping the modulated signal to frequency resources, performing IFFT processing, and adding a CP.

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

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

[0077] 11, for example, 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 (for example, one of the versions HE and EHT) in a Common Info field and a subfield whose setting varies depending on the version corresponding to terminal 200. For example, if the version corresponding to terminal 200 is EHT, AP100 may determine a format of the Common Info field that differs from the format defined in HE. In other words, for example, if the version corresponding to terminal 200 is EHT, AP100 may change the format of the Common Info field defined in HE. Furthermore, for example, AP100 may generate a Trigger type that includes version information by associating the version information with a Trigger type.

[0078] For example, the AP 100 transmits the generated Trigger frame to the terminal 200, and the terminal 200 receives the Trigger frame from the AP 100 (S102). The Trigger frame may include, for example, a Trigger type subfield value associated with version information and a subfield whose setting varies depending on the version.

[0079] Terminal 200 generates an uplink response signal, for example, 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, for example, based on version information (for example, either the HE or EHT version) associated with the Trigger type subfield value included in the Trigger frame. For example, if the version supported by terminal 200 is EHT, terminal 200 may determine a format different from the format of the Common Info field defined in the HE. In other words, for example, if the version supported by terminal 200 is EHT, terminal 200 may change the interpretation of at least one subfield of the Common Info field defined in the HE.

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

[0081] [Example of Common Info field operation] The following describes an example of generating information in the Common Info field in the AP 100. For example, a method of determining the EHT format to be applied to the Common Info field in accordance with version information in the AP 100 will be described.

[0082] <Example of version information notification> The version information may be notified by, for example, the value of the Trigger type subfield. In other words, the version information may be associated with the type of the 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 undefined in HE).

[0084] For example, in FIG. 9, when the Trigger type subfield value is 7 (for example, the threshold value) 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 the 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 instructing an EHT-compatible Trigger type, the AP 100 may determine a format with settings different from the settings of some subfields in the format of the Common Info field shown in Fig. 2. For example, information related to control information for EHT terminals may be set in some subfields. The AP 100 may set the settings of some subfields differently depending on whether the AP is HE-compatible or EHT-compatible.

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

[0090] In the following, for example, in the EHT-compatible Common Info field, a subfield with a different setting from that in the HE-compatible Common Info field is referred to as a "second Trigger dependent Common Info field (Trigger dependent Common Info 2)."

[0091] In this way, when the version in the Common Info field is EHT, the AP 100 may set some subfields to subfields that depend on the Trigger type (for example, the second Trigger dependent Common Info field). This makes it possible to reduce fields (for example, subfields) that are not referenced by EHT terminals in the Trigger frame when an EHT-compatible Trigger type is specified, thereby reducing the overhead of the Trigger frame.

[0092] 12 and 13 are diagrams showing an example of a Common Info field that is applied when the Trigger type is EHT compatible (in other words, when HE is not compatible).

[0093] In the example shown in FIG. 12, with respect to the Common Info field (e.g., FIG. 2) applied when the Trigger type is HE compatible, the UL Spatial Reuse subfield (subfield corresponding to B37 to B52) is changed to Trigger dependent Common Info 2, and in the example shown in FIG. 13, the UL STBC subfield (field corresponding to B26) and Doppler subfield (subfield corresponding to B53) are changed to Trigger dependent Common Info 2.

[0094] In the example shown in Figure 12, AP 100 and terminal 200 can use 16 bits as the second Trigger dependent Common Info field, which has the advantage of increasing the amount of information that can be notified to EHT terminals compared to Figure 13 (e.g., 2 bits).

[0095] Furthermore, for example, since the UL Spatial Reuse subfield may contain information for spatial reuse for HE terminals in an overlapped BSS (OBSS), there may be cases where the UL spatial reuse subfield cannot be used for Trigger dependent Common Info 2. In this case, for example, as shown in Fig. 13, 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 EHT terminals without affecting spatial reuse of HE terminals in an OBSS.

[0096] Here, within the Trigger frame, for example, the Trigger Dependent Common Info subfield or the User Info field after the Common Info field may have a different field size and / or bit position of each piece of information depending on the Trigger type. After determining the Trigger type, for example, the terminal 200 identifies (or judges or determines) the bit positions of the Trigger Dependent Common Info field and the User Info field, and performs reception processing.

[0097] On the other hand, the Common Info field that may be set in the second Trigger-dependent Common Info field, such as the UL STBC subfield, the UL Spatial Reuse subfield, or the Doppler subfield shown in Figures 12 and 13, may be a subfield whose size or bit position is transmitted independently of 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 independent of the Trigger type (or version information) (in other words, subfields different from subfields that depend on the Trigger type) may differ depending on the version information. For example, the AP 100 and the terminal 200 may reinterpret some of the information whose bit positions are defined independent of the Trigger type (or version information) based on the Trigger type (or version information).

[0099] As a result, even if the subfield setting is reinterpreted depending on the Trigger type (or version information), as shown in Figures 12 and 13, the bit position that terminal 200 extracts for that subfield does not change, thereby simplifying the reception processing (e.g., information extraction processing) of terminal 200.

[0100] Furthermore, when applying Trigger dependent Common Info 2 in the case of EHT support, terminal 200 may use, for example, a combination of both subfields of Trigger dependent Common Info, which is also included in the case of HE support, and Trigger dependent Common Info 2, which is set in the case of EHT support, as common information that depends on the trigger type. This makes it possible to increase the amount of information that can be notified to terminal 200 by common information that depends on the trigger type (in other words, the amount of notification) without increasing overhead.

[0101] Also, for example, in HE, there may be a Trigger type in which the size of the Trigger dependent Common Info subfield is 0. Examples of Trigger types in which 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] In Figures 12 and 13, for example, even in the case of a Trigger type in which the size of Trigger dependent Common Info is 0, it is possible to transmit information for the EHT terminal in Trigger dependent Common Info 2 for the EHT terminal (e.g., a subfield whose size and bit position do not change).

[0103] Furthermore, the bit position of a subfield (e.g., Trigger dependent Common Info 2) that is interpreted in the case of EHT support may differ depending on the Trigger type. For example, as shown in Fig. 14, when the Trigger Type subfield value is 8, Trigger dependent Common Info 2 may be set in B37-B39 of the UL Spatial Reuse subfields that the EHT terminal does not need to receive, and a reserved area may be set in B40-B52. For example, as shown in Fig. 15, when the Trigger Type subfield value is 9, Trigger dependent Common Info 2 may be set in B37-B41 of the UL Spatial Reuse subfields that the EHT terminal does not need to receive, and a reserved area may be set in B42-B52. In this way, by setting Trigger dependent Common Info 2 in some bits of the subfields that the EHT terminal does not refer to in the HE definition and setting a reserved area in the other bits, the reserved area can be secured, thereby improving the extensibility of future versions.

[0104] Note that the bit position and size in which Trigger Dependent Common Info 2 is set in Figures 14 and 15 are examples, and at least one of the bit position and size may be different from those in Figures 14 and 15. Also, in Figures 14 and 15, the case where the UL Spatial Reuse subfield is set in two areas, Trigger Dependent Common Info 2 and the Reserved area, has been described, but the number of areas in which it is set is not limited to two, and it may be three or more areas.

[0105] Furthermore, when the EHT-compatible Trigger type is a Sounding NDP (for example, a Trigger type that indicates a response signal for which no data is generated), for example, the definition (interpretation) of at least one of the subfields including information for generating data not used for NDP generation may be made different from the definition of the HE. Fig. 16 is a diagram showing, as an example, an example in which 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 Fig. 2 are set in Trigger Dependent Common Info 2. The subfields in which Trigger Dependent Common Info 2 is set are not limited to the example shown in Fig. 16.

[0106] <Example of the second Trigger dependent Common Info field> For example, when the EHT-compatible (or HE-incompatible) Trigger type is NDP for Sounding, Trigger dependent Common Info 2 may include extended information (e.g., the number of streams) on the number of EHT-Long Training field (LTF) symbols of the response signal (TB PPDU). Increasing the number of symbols by notifying Trigger Dependent Common Info 2 can improve the accuracy of channel estimation.

[0107] Alternatively, information regarding the EHT-LTF Tone mapping interval may be included in Trigger dependent Common Info 2. This makes it possible to frequency-multiplex EHT-LTF among multiple APs 100 by Distributed-FDMA, for example.

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

[0109] Furthermore, for example, when the EHT-compatible Trigger type is Multi-AP coordination, the following cooperative transmission type information may be included in Trigger dependent Common Info 2. This allows the terminal 200 to transmit, for example, information according to the cooperative transmission type as a response signal, and the 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, when the Trigger type is Multi-AP coordination, AP 100 and terminal 200 may determine that the version is EHT compatible, and may replace a field that is a User Info field in HE with a field including information for EHT (for example, an AP Info field). For example, the AP Info field may include an instruction to send control information used for cooperative transmission from an AP that schedules cooperative transmission (for example, also referred to as a sharing AP) to APs participating in the cooperative transmission (for example, also referred to as shared APs).

[0111] <Example of format determination> A method for determining the TB PPDU format (for example, either the EHT TB PPDU or HE TB PPDU format) according to the version information in format determination section 207 of terminal 200 will be described.

[0112] For example, when the Trigger type is a type compatible with HE, the format determination unit 207 may determine the TB PPDU format according to 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 the EHT TB PPDU when it is indicated that the Special User Info subfield is present, and may apply the HE TB PPDU when it is indicated that the Special User Info subfield is not present.

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

[0115] Furthermore, for example, when the Trigger type is a type that supports EHT, the format determining section 207 may apply the EHT TB PPDU regardless of the information in the Common Info field and the User Info field.

[0116] An example of the format determination operation has been described above.

[0117] As described above, in the present embodiment, AP 100 generates a Trigger frame including, in the Common Info field, information relating to the version of the wireless communication standard, such as HE or EHT, and subfields with settings that vary depending on the version, and transmits this Trigger frame to terminal 200. Furthermore, terminal 200 determines the settings of subfields in the Common Info field of the Trigger frame, for example, based on the information relating to the version of the wireless communication standard, such as HE or EHT, that is included in the Trigger frame.

[0118] According to this embodiment, even if 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 use a single trigger frame to indicate an Aggregated-PPDU (A-PPDU) that frequency-multiplexes an uplink response signal (HE TB PPDU) of an HE terminal and an uplink response signal (EHT TB PPDU) of an EHT terminal (see, for example, non-patent document 6).

[0120] For example, A-PPDU may be transmitted within a 320 MHz band. For example, the AP can instruct A-PPDU by using one trigger frame to assign frequency bands based on the formats recognized by the HE terminal and the EHT terminal. As an example, a primary 160 MHz band may be assigned to an HE terminal that supports a maximum bandwidth of 160 MHz, and a secondary 160 MHz band may be assigned to an EHT terminal that supports a maximum bandwidth of 320 MHz. Note that the frequency bandwidth to which A-PPDU is applied is not limited to 320 MHz, and other bandwidths may also be used.

[0121] Here, in the first embodiment, if a Trigger type that can be added in the EHT (a Trigger type not supported by the HE terminal) is indicated in the Trigger type subfield in the Common Info field, the HE terminal suspends reception processing of the Trigger frame. Therefore, if a Trigger type not supported by the HE terminal is indicated in the Trigger type subfield in the Common Info field, there is a possibility that an A-PPDU cannot be indicated in one Trigger frame.

[0122] In this embodiment, a method is described in which A-PPDU can be applied to response signals between an HE terminal and an EHT terminal in a trigger frame that indicates a new trigger frame for an EHT terminal (in other words, a trigger type not supported in the HE).

[0123] [Base station configuration] An example of the configuration of the AP 100 according to this embodiment may be the same as that in Fig. 8. For example, in the AP 100 according to this embodiment, the operations of the Trigger type setting unit 103 and the Common Info generating unit 104 may be different from those in the first embodiment.

[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 in the trigger frame (for example, a trigger type subfield value), and may store information relating to the set trigger type (for example, information in table format).

[0125] In this embodiment, trigger type setting section 103 may set, for example, a predefined trigger type table for HE terminals (e.g., FIG. 5 ) and a trigger type table for EHT terminals (an example of which will be described later) that is different from the trigger type table for HE terminals. Here, the trigger type table for EHT terminals may include a new trigger type that is not supported by HE terminals. Trigger type setting section 103 outputs information about the set trigger table to common info generating section 104, for example.

[0126] The Common Info generating unit 104 generates a Trigger type subfield indicating a Trigger type for an HE terminal and a subfield indicating a Trigger type for an EHT terminal (for example, referred to as a "Trigger type 2 subfield"), based on, for example, an instruction of the Trigger type input from the scheduling unit 101 and a Trigger type table input from the Trigger type setting unit 103. In other words, the Common Info generating unit 104 may set information related to the type of the Trigger frame (for example, the Trigger type subfield value) using multiple subfields in the Common Info field of the Trigger frame.

[0127] For example, the Trigger type subfield for an HE terminal and the Trigger type 2 subfield for an EHT terminal may be different. The Trigger type indicated in the Trigger type subfield may be a type associated with version information compatible with HE, and the Trigger type indicated in the Trigger type 2 subfield may be a type associated with version information compatible with EHT.

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

[0129] The processing of the other components in the AP 100 may be the same as the processing in the first embodiment, for example.

[0130] [Device configuration] An example configuration of terminal 200 according to this embodiment may be the same as that in Fig. 10. For example, in terminal 200 according to this embodiment, the operations of Trigger type setting section 204 and Common Info acquisition section 205 may be different from those in the first embodiment.

[0131] For example, when terminal 200 is an HE terminal, trigger type setting section 204 may output a trigger type table for HE terminals to common info acquisition section 205. Furthermore, when terminal 200 is an EHT terminal, trigger type setting section 204 may output a trigger type table for HE terminals and a trigger type table for EHT terminals to common info acquisition section 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 (for example, including the type of data to be transmitted or the time length of the uplink signal), including the type of the uplink response 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 the processing in the first embodiment, for example.

[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 that are not supported by the HE terminal (e.g., Sounding NDP transmission or cooperative communication).

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

[0138] FIG. 18 is a diagram showing another example of the Trigger type table for EHT terminals.

[0139] As shown in Fig. 18, the Trigger type table for EHT terminals may include Trigger types for HE terminals (for example, Trigger Type 2 subfield values ​​= 0 to 7) in addition to Trigger Types for EHT terminals (for example, Trigger Type 2 subfield values ​​= 8, 9). In this case, AP 100 and terminal 200 may, for example, set the Trigger type subfield value for HE terminals using the Trigger type subfield (for example, Fig. 5) in multiple subfields related to the Trigger type in the Trigger frame, and set the Trigger type subfield value for EHT terminals using the Trigger type 2 subfield (for example, Fig. 17).

[0140] By individually setting 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 a 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] 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] Also, for example, the EHT terminal receives the Trigger type 2 subfield (for example, B56 to B59) shown in Fig. 19. For example, when referring to the Trigger type table shown in Fig. 17, if the Trigger Type 2 subfield value = 0 is instructed, the EHT terminal may further identify the Trigger type based on the Trigger type subfield (for example, B0 to B3) shown in Fig. 19. Also, for example, when referring to the Trigger type table shown in Fig. 18, the EHT terminal may identify the Trigger type based on the Trigger type 2 subfield, and may not receive the Trigger type subfield (for example, B0 to B3).

[0146] For example, even when the AP 100 instructs an EHT terminal of a trigger type that is not supported by the HE terminal, the AP 100 can separately instruct the HE terminal of a trigger type different from that of the EHT terminal. As a result, even if the trigger type for the EHT terminal is not supported by the HE terminal, the HE terminal does not need to stop receiving the trigger frame based on the trigger type for the HE terminal. Therefore, for example, an uplink response signal is generated in both the EHT terminal and the HE terminal, making it possible to apply A-PPDU.

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

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

[0149] Furthermore, the Trigger type 2 subfield for EHT terminals is included in a subfield (for example, a 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, which simplifies the reception process in terminal 200.

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

[0151] (Other embodiments) (1) In each of the above-described embodiments, 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, and may be another version. For example, the same aspects of the present disclosure may be similarly applied to a new trigger type added in a future version of EHT (e.g., referred to as EHT+). In that case, the operation of the EHT terminal in the above-described embodiments may be replaced with the operation of a terminal compatible with EHT+ (e.g., EHT+ terminal).

[0152] For example, AP100 and terminal 200 may change the format of the Common Info field (for example, may change the meaning of some subfields) depending on whether the Trigger type is EHT+ compatible (a trigger type newly supported in EHT+), EHT compatible, or HE compatible.

[0153] This allows common info fields of different formats to be applied between EHT+ terminals and EHT terminals or HE terminals, and provides the same effects as those of the above-described embodiment.

[0154] The format of the Common Info field is not limited to two types set between EHT+ compatibility and EHT compatibility or HE compatibility, but may be three types set between EHT+ compatibility, EHT compatibility, and HE compatibility, or may be four or more types.

[0155] (2) In each of the above-described embodiments, an example has been described in which the format of the Common Info field is set according to the version information associated with the Trigger type. However, this is not limited to this. 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, when a Sounding NDP, which is an EHT-compatible trigger type, is indicated in the trigger frame, if the trigger type is HE-compatible (e.g., Figure 3), the EHT-LTF stream number ("Number of Spatial Streams" subfield) may be included in the reserved area subfield (e.g., B25), as shown in Figure 20.

[0157] The subfield set in accordance with the version information in the User Info field is not limited to the stream number of EHT-LTF, and may be other information.

[0158] Also, for example, in each of the above-mentioned embodiments, some subfields of the format of the Special User Info field may be set according to the version information associated with the Trigger type. For example, when an EHT-compatible Trigger type is indicated in the Trigger frame, if the Trigger type is HE-compatible (for example, FIG. 4), a second Trigger dependent Common Info field (Trigger dependent Common Info 2) may be set in the subfields (for example, B37 to B39) that are reserved areas, as shown in FIG. 21.

[0159] 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, and other fields may be set. Also, the subfield set in the Special User Info field according to the version information may be at least one bit in a reserved area (e.g., B37 to B39) in the case of HE compatibility.

[0160] (3) In the above-described embodiment, the trigger type instructing the sounding NDP and cooperative communication has been described as an example of the trigger type compatible with EHT. However, the trigger types compatible with EHT and beyond are not limited to these.

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

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

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

[0164] FIG. 22 is a diagram showing an example of a User Info field compatible with HE that is used when the Trigger type is NFRP (a type that instructs the terminal 200 to transmit an NDP feedback report).

[0165] 22 includes information about the type of feedback to be given to multiple terminals 200 designated by Starting AID. In the HE, for example, one type, Resource request (resource allocation request), is supported as the Feedback Type. For example, when the AP 100 designates Resource request as the Feedback Type, the HE terminal may hold data to be transmitted, and when requesting resource allocation, may feed back an NDP to the AP 100 as a response signal.

[0166] Here, new Feedback Types may be supported in EHT or EHT+. For example, as shown in Fig. 23, in EHT, Acknowledgment (information on whether data has been correctly decoded) may be added as a new value of Feedback Type.

[0167] In this case, for example, as in the first embodiment, when transmitting an Acknowledgment as a Feedback Type to an EHT terminal, the AP 100 may set the format of the User Info field according to the EHT support version. Furthermore, when the EHT terminal receives an Acknowledgment as the Feedback Type, the EHT terminal may perform reception processing based on the format of the User Info field according to the EHT support version that is different from the HE support format. For example, as shown in FIG. 24, in the User Info field according to the EHT support version, a part of the Reserved area in the HE may be set (for example, changed) to a TID subfield (an identifier indicating a traffic type). This allows the AP 100 to feed back, to the EHT terminal, Acknowledgment information of the traffic type specified by the TID. Furthermore, when the HE terminal receives an Acknowledgment as the Feedback Type, the HE terminal may stop reception processing.

[0168] Alternatively, for example, similar to the second embodiment, AP100 may indicate the Feedback Type individually using different subfields for EHT terminals and HE terminals. For example, as shown in FIG. 25, part of the Reserved area in the HE may be set (for example, changed) to a Feedback Type subfield (for example, Feedback Type 2 subfield) and a TID subfield for EHT terminals. This allows AP100 to indicate the Feedback Type individually to the HE terminal and the EHT terminal using one Trigger frame, similar to the second embodiment. For example, AP100 may indicate a Resource request to the HE terminal and an Acknowledgment to the EHT terminal using one Trigger frame.

[0169] The Feedback type for the EHT terminal is not limited to Acknowledgement and may be other types of information. Also, the information set in the case of the Feedback type for the EHT terminal is not limited to TID and may be other information.

[0170] (5) Although the newer version of EHT has been described using the term “EHT+,” it is not limited to this and other terms may also be used.

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

[0172] Furthermore, although the above embodiment has been described based on the 11be format as an example, the format to which an embodiment of the present disclosure is applied is not limited to the 11be format. An embodiment of the present disclosure may be applied to, for example, IEEE 802.11bd (NGV (Next Generation V2X)), a next-generation standard of IEEE 802.11p, which is an in-vehicle standard.

[0173] The present disclosure can be realized by software, hardware, or software linked to hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may be called an IC, system LSI, super LSI, or ultra LSI.

[0174] The integrated circuit method is not limited to LSI, but may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0175] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology can be used to integrate functional blocks. The application of biotechnology is also a possibility.

[0176] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a wireless transceiver and processing / control circuitry. The wireless transceiver may include a receiver and a transmitter, or both functions. The wireless transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0177] Communications equipment is not limited to portable or mobile equipment, but also includes non-portable or fixed equipment, devices, and systems of any kind, such as smart home devices (such as appliances, lighting equipment, smart meters or metering devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0178] Communications include data communications via cellular systems, wireless LAN systems, communications satellite systems, etc., as well as data communications via combinations of these.

[0179] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0180] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0181] A base station according to one embodiment of the present disclosure includes a control circuit that generates a control signal for uplink transmission, the control signal including, in a field common to multiple terminals, information regarding the version of a wireless communication standard and a subfield with settings that differ depending on the version, and a transmission circuit that transmits the control signal.

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

[0183] In one embodiment of the present disclosure, if the value relating to the type is equal to or less than 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] In one embodiment of the present disclosure, the device further includes 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 changes the setting of at least a part of subfields in the common field that are different from a first subfield depending on the type of the control signal, depending on the version.

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

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

[0188] In one embodiment of the present disclosure, the transmission circuit transmits the 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 about 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, in the plurality of subfields, information regarding the type for a terminal whose version corresponds to High Efficiency (HE) using a first subfield, and sets information regarding the type for a terminal whose version corresponds to Extreme High Throughput (EHT) using a second subfield.

[0191] In one embodiment of the present disclosure, the second subfield is set to a reserved area in the control signal when the version is HE.

[0192] In one embodiment of the present disclosure, the control circuit sets the type-related 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 that receives a control signal for uplink transmission, the control signal including, in a field common to multiple terminals, information regarding the version of a wireless communication standard and a subfield with settings that differ depending on the version, and a control circuit that determines the settings based on the information regarding the version.

[0194] In a communication method according to one embodiment of the present disclosure, a base station generates a control signal for uplink transmission, which includes, in a field common to multiple terminals, information regarding the version of a wireless communication standard and a subfield with settings that differ depending on the version, and transmits the control signal.

[0195] In a communication method according to one embodiment of the present disclosure, a terminal receives a control signal for uplink transmission, which includes, in a field common to multiple terminals, information regarding the version of a wireless communication standard and a subfield whose setting differs depending on the version, and determines the setting based on the information regarding the version.

[0196] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2021-081515, filed on May 13, 2021, are incorporated herein by reference in their entirety. [Industrial Applicability]

[0197] One embodiment of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0198] 100 AP 101 Scheduling Department 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 coding section 107,210 Modulation section 108,201 Radio transmitter / receiver 109,202 Demodulation section 110,203 Error correction decoding unit 111 Terminal information acquisition unit 200 devices 205 Common Info Acquisition Department 206 User Info acquisition section 207 Format Decision Unit 208 Data Generation Department

Claims

1. A control circuit for generating a control signal for controlling upstream transmission; a transmission circuit for transmitting the control signal; the control signal includes common information including a first subfield and a second subfield, information regarding a type of the control signal is set using the first subfield and the second subfield, the second subfield indicates information regarding a version of a wireless communication standard, and the control signal further includes a subfield whose setting is different depending on the version. Base station.

2. The information about the version is associated with a type of the control signal. The base station of claim 1 .

3. a receiving circuit for receiving a response signal to the control signal based on the version associated with the type. The base station of claim 2.

4. the control circuit varies the setting of at least a part of a third subfield, which is different from the first subfield and is related to the type of the control signal, in the common information, depending on the version; The base station of claim 1 .

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

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

7. the transmission circuit transmits information about the type using both the first sub-field and the second sub-field. The base station of claim 6.

8. The second subfield is set in a reserved area in the control signal when the version is High Efficiency (HE). The base station of claim 1 .

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

10. The base station is generating a control signal for controlling upstream transmission; A communication method for transmitting the control signal, the control signal includes common information including a first subfield and a second subfield, information regarding a type of the control signal is set using the first subfield and the second subfield, the second subfield indicates information regarding a version of a wireless communication standard, and the control signal further includes a subfield whose setting is different depending on the version. Communication method.

Images