First communication device, communication method, and integrated circuit

Abstract

In the present invention, an access point comprises a control circuit that generates a control signal that indicates uplink transmission of a plurality of terminals and that includes information regarding the destination of uplink transmission for each of the plurality of terminals, and a transmission circuit that transmits the control signal.

Description

Access point, terminal, and communication method

[0001] The present disclosure relates to an access point, a terminal, and a communication method.

[0002] The Institute of Electrical and Electronics Engineers (IEEE) is currently developing specifications for IEEE 802.11be (hereinafter also referred to as "11be") as a successor standard to the IEEE 802.11ax (hereinafter also referred to as "11ax"). For example, 11ax is also called High Efficiency (HE), and 11be is also called Extremely High Throughput (EHT). Furthermore, discussions are also underway regarding the required specifications for the successor standard to 11be (see, for example, Non-Patent Documents 3 and 4). For example, the successor standard to 11be is also called "EHT-plus" or "beyond 11be."

[0003] IEEE 802.11-21 / 0268r8, PDT: Channel access for Triggered TXOP SharingIEEE 802.11-20 / 1312r8, AP assisted SU PPDU Tx for 11be R1IEEE 802.11-22 / 0046r1, Next 802.11 generation after 11beIEEE 802.11-22 / 0059r0, Beyond 'be'IEEE 802.11-22 / 0039r3, CR for 35.2.1.3 part -2IEEE 802.11-21 / 0485r3, EHT TF Clarifications

[0004] However, the allocation method of transmission opportunities in wireless communication such as wireless LAN has not been fully studied.

[0005] Non-limiting embodiments of the present disclosure contribute to providing an access point, a terminal, and a communication method that can improve the efficiency of allocating transmission opportunities in wireless communication.

[0006] An access point according to one embodiment of the present disclosure includes a control circuit that generates a control signal instructing uplink transmissions of multiple terminals, the control signal including information regarding the destination of the uplink transmission for each of the multiple terminals, 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, it is possible to improve the efficiency of allocation of transmission opportunities in wireless communication.

[0009] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some 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.

[0010] Figure showing an example of a Trigger frameFigure showing an example of a Common Info fieldFigure showing an example of a User Info fieldFigure showing an example of a Special User Info fieldFigure showing an example of TXOP Sharing modeSequence diagram showing an example of the operation of TXOP Sharing mode 2Sequence diagram showing an example of the operation of TXOP Sharing for multiple terminals (STAs) using Frequency Division Multiplexing (FDM)Block diagram showing an example of the configuration of a part of an access point (AP)Block diagram showing an example of the configuration of a part of a terminalBlock diagram showing an example of the configuration of an APFigure showing an example of TXOP Sharing modeFigure showing an example of an User Info fieldFigure showing an example of a method for notifying an allocated bandwidthFigure showing an example of a method for notifying an allocated bandwidthFigure showing an example of an example of destination informationBlock diagram showing an example of the configuration of a terminalSequence diagram showing an example of the operation of TXOP SharingFigure showing an example of destination informationSequence diagram showing an example of the operation of TXOP SharingFigure showing an example of a User Info fieldSequence diagram showing an example of the operation of TXOP SharingSequence diagram showing an example of the operation of TXOP SharingSequence diagram showing an example of the operation of TXOP SharingFigure showing an example of an EHT Medium Access Control (MAC) Capabilities Information fieldFigure showing an example of a User Info field

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

[0012] In 11be, similar to 11ax, a priority control method called Enhanced Distributed Channel Access (EDCA) may be used to prioritize individual transmission opportunities for access categories (ACs). In EDCA, for example, once an AC acquires the right to transmit, it can continuously transmit radio signals at a minimum waiting time (Short Inter Frame Space: SIFS). The time during which this continuous transmission is possible may be called "Transmission Opportunity (TXOP)." The upper limit of the TXOP time may be specified for each AC, for example.

[0013] 11be considers, for example, "TXOP sharing," which allocates at least a portion of the time of a TXOP acquired by an access point (AP, also called "AP-STA (Station)" or "base station") to a terminal (STA, also called "non-AP STA"). For example, a procedure (e.g., "Triggered TXOP sharing procedure") in which an AP triggers TXOP sharing for one STA is considered (see, for example, Non-Patent Documents 1 and 2).

[0014] 11ax, for example, introduces a mechanism (e.g., "Triggered UL operation") in which an AP schedules radio resources for STAs' uplink signals using a control signal (hereinafter referred to as a "trigger frame (TF)") that instructs the transmission of uplink signals. Triggered UL operation improves the efficiency of orthogonal multiplexing for STAs' uplink signals, thereby improving throughput performance.

[0015] For example, in Triggered UL operation, the AP dynamically grasps the status of each STA, such as the transmission buffer status (e.g., BSR: Buffer Status Report) or communication quality of each STA, and calculates multiple radio parameters to be applied to each STA's uplink signal (e.g., uplink response signal to a Trigger frame) based on the STA's status. The radio parameters include, for example, the signal length, Modulation and Coding Scheme (MCS), the number of spatial streams, and the transmit power for the uplink signal. Thus, in Triggered UL operation, the AP's scheduling process (e.g., calculation) may become complicated.

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

[0017] On the other hand, in TXOP sharing, for example, when an AP allocates a portion of the acquired TXOP to a certain STA, a transmission prohibition period (NAV: Network Allocation Vector) may be set for STAs other than the STA to which the portion of the TXOP has been allocated. By setting the NAV, collisions of transmission signals of STAs to which the portion of the TXOP has been allocated can be suppressed. Furthermore, STAs to which TXOP sharing is applied can improve signal transmission efficiency by determining radio parameters to be applied to the transmission signals of the STAs based on the transmission buffer status or communication quality of the STAs. For example, in TXOP sharing, the AP does not need to perform at least a portion of scheduling for uplink signals transmitted by STAs, which simplifies AP processing compared to triggered UL operation.

[0018] In this way, 11be supports TXOP sharing in addition to triggered UL operation, thereby reducing collisions of uplink signals between STAs and improving throughput performance through simple processing at the AP.

[0019] Beyond 11be proposes the need to improve the performance of peer-to-peer (P2P) or Direct Link (DiL) communication between terminals (see, for example, Non-Patent Documents 3 and 4). For example, the method by which an AP instructs multiple terminals performing P2P communication to perform TXOP sharing (for example, a trigger frame format or procedure) has not been fully considered.

[0020] In 11be, for example, it is being considered that an AP instructs one terminal (STA) to perform TXOP sharing (hereinafter also referred to as "TXS") using a trigger frame (hereinafter referred to as "MU-RTS trigger frame") in which Multi-User Request-To-Send (MU-RTS) is set as the trigger frame type (e.g., referred to as "Trigger Type") (see, for example, Non-Patent Document 1). Note that an MU-RTS trigger frame to which TXOP sharing is applied is sometimes called an "MU-RTS TXS trigger frame (MU-RTS TXS TF)."

[0021] Fig. 1 is a diagram showing an example of a Trigger frame. As shown in Fig. 1, the Trigger frame includes a field (e.g., a "Common Info field") that includes information common to multiple terminals that are frequency-division multiplexed (FDM), and a field called a User Info List. The User Info List may include, for example, one or more fields (e.g., a "User Info field") that include information individual (or unique) to a terminal.

[0022] In addition, in 11be, for example, a field (for example, a "Special User Info field") that includes information for terminals that support 11be (EHT) may be included in the Trigger frame (not shown).

[0023] Fig. 2 is a diagram showing an example of the configuration of a Common Info field considered in 11be (e.g., EHT) (see, for example, Non-Patent Document 5). Fig. 3 is a diagram showing an example of the configuration of a User Info field in MU-RTS TXS TF considered in 11be (EHT) (see, for example, Non-Patent Document 5). Fig. 4 is a diagram showing an example of the configuration of a Special User Info field (see, for example, Non-Patent Document 6).

[0024] For example, the Trigger Type subfield in the Common Info field shown in Fig. 2 is a subfield that indicates the type of trigger frame (e.g., the type of signal that the AP causes the terminal to transmit). For example, the AP can instruct a predetermined terminal to transmit an MU-RTS TXS trigger frame by setting the Trigger Type to a value that indicates MU-RTS (e.g., in the case of 11be, the Trigger Type subfield value = 3). For example, when the terminal receives an MU-RTS TXS trigger frame and the Association ID (AID) of the terminal is specified in the User Info field included in the received MU-RTS TXS trigger frame, the terminal may transmit a Clear To Send (CTS) frame to the AP.

[0025] In 11be, in the case of an MU-RTS TXS Trigger frame, for example, the area B20-B21 in the Common Info field shown in FIG. 2 is recognized as a "TXOP Sharing Mode" subfield related to the TXOP sharing setting.

[0026] In addition, for a trigger frame of a type different from the MU-RTS TXS trigger frame, the area B20-21 in the common information field may be recognized as the "GI and HE / EHT-LTF Type" subfield. The GI and HE / EHT-LTF Type subfield may include, for example, parameter information related to the HE-Long Training Field (LTF) and EHT-LTF. For example, the information included in the GI and HE / EHT-LTF Type subfield is not used for transmitting a CTS frame that does not include HE / EHT-LTF.

[0027] FIG. 5 is a diagram showing an example of the TXOP Sharing Mode considered in 11be (see, for example, Non-Patent Document 1).

[0028] In FIG. 5, when the TXOP Sharing Mode is 0 (TXOP Sharing Mode subfield value=0), TXOP sharing (e.g., MU-RTS TXOP Sharing) is not performed, and the terminal transmits a CTS frame to the AP, for example, as a response to the MTS frame.

[0029] Also, in FIG. 5, when the TXOP Sharing Mode is 1 or 2 (TXOP Sharing Mode subfield value=1 or 2), TXOP sharing (e.g., MU-RTS TXOP Sharing) may be implemented.

[0030] For example, when TXOP Sharing Mode is 1 (also referred to as TXOP Sharing Mode 1), the scheduled terminal can transmit wireless frames to the AP to which it connects (e.g., the associated AP) during an allocation period corresponding to a portion of the TXOP. For example, when TXOP Sharing Mode is 1, the terminal does not transmit wireless frames to APs or STAs other than the AP to which it connects.

[0031] Furthermore, for example, when TXOP Sharing Mode is 2 (also referred to as TXOP Sharing Mode 2), as shown in FIG. 6, in an allocation period corresponding to a part of the TXOP (Time allocated in MU-RTS TX TF), a scheduled terminal (e.g., Non-AP STA 1 or STA 1, also referred to as "Terminal 1") can transmit wireless frames to the AP to which it connects or to another terminal (e.g., Non-AP STA 2 or STA 2, also referred to as "Terminal 2").

[0032] When the above-mentioned TXOP Sharing Mode is 1 or greater (or is non-zero), i.e., when TXOP sharing is applied, the MU-RTS Trigger frame is sometimes called an "MU-RTS TXS Trigger frame (MU-RTS TXS TF)."

[0033] Here, as shown in FIG. 6 , when an AP receives a CTS frame (e.g., a CTS response) from a scheduled terminal (e.g., terminal 1) in response to an MU-RTS TXS Trigger frame, the AP may determine that TXOP sharing has been properly instructed to the terminal. In this case, the AP does not need to transmit a signal other than an ACK response (e.g., a Block Ack) requested by the scheduled terminal during the allocation period. Note that, for example, as shown in FIG. 6 , if carrier sense is IDLE during a Point Coordination Function (PCF) Interframe Space (PIFS) within the allocation period, the AP may retrieve the TXOP from the terminal and transmit a signal addressed to another terminal during the remaining TXOP period.

[0034] For example, in 11be, the number of terminals that can be instructed using the MU-RTS TXS Trigger frame is one, and one User Info field shown in Fig. 3 is set in the MU-RTS TXS Trigger frame (see, for example, Non-Patent Document 1). Furthermore, during the allocation period for a terminal in TXOP Sharing, the terminal may determine parameters such as the MCS of the transmission signal and transmit a Single User (SU) PPDU of a specified bandwidth (for example, a 20 MHz × N (N is an integer) bandwidth). Furthermore, for example, the use of the Allocation Duration subfield of the User Info field as shown in Fig. 3 may be considered for instructing the allocation period for the terminal.

[0035] Here, for example, a method (for example, a trigger frame format or procedure) by which an AP instructs multiple terminals with which terminal-to-terminal communication (for example, a P2P-link) is set to perform TXOP sharing has not been fully considered.

[0036] In a non-limiting example of the present disclosure, an example of a method in which an AP instructs TXOP sharing to multiple terminals (also referred to as "P2P terminals") with which a P2P-link is established will be described.

[0037] (First Embodiment) In this embodiment, a case where TXOP sharing is performed to a plurality of terminals by FDM will be described.

[0038] FIG. 7 shows an example of a sequence in which an AP performs TXOP sharing using FDM with terminal 1 (STA 1) and terminal 3 (STA 3) in TXOP Sharing Mode 2 (e.g., when a scheduled terminal communicates with a connected AP or another terminal).

[0039] 7, as an example, a P2P link is established between terminal 1 (STA 1) and terminal 2 (STA 2), and a P2P link is established between terminal 3 (STA 3) and terminal 4 (STA 4). Note that in IEEE 802.11, a pair of terminals performing P2P communication may be set up using a procedure called Tunneled Direct Link Setup (TDLS).

[0040] In FIG. 7, the AP may allocate orthogonal frequency resources (for example, 20 MHz channel×N (channels in 20 MHz units)) to each of terminal 1 and terminal 3 using, for example, an MU-RTS TXS Trigger frame.

[0041] Here, terminal 1 and terminal 3 may each determine the time length and destination (e.g., the connected AP or another P2P terminal) of an uplink signal (e.g., SU PPDU). Therefore, as shown in FIG. 7 , the time length of the SU PPDU may differ between terminal 1 and terminal 3, which may cause the transmission timing and reception timing at the AP to overlap. For example, if the transmission timing and reception timing overlap, an AP that does not support full-duplex communication may not process either the transmitted signal or the received signal. Furthermore, even if the AP supports full-duplex communication, for example, self-interference (when the received signal contains adjacent channel interference of the transmitted signal) may occur, resulting in degradation of reception performance.

[0042] For example, as shown in Fig. 7, an ACK (e.g., Block Ack) frame transmitted from the AP to terminal 1 and an SU PPDU frame (e.g., DATA to AP in non-TB PPDU) transmitted from terminal 3 to the AP may overlap. In this case, for example, the AP may not be able to receive the SU PPDU frame from terminal 3, and STA 3 may retransmit the SU PPDU. In this way, the time resources allocated by the AP may not be used effectively.

[0043] In this embodiment, for example, a method of controlling the destination of a TXOP shared time resource for a plurality of P2P terminals will be described.

[0044] [Configuration of Wireless Communication System] The wireless communication system according to this embodiment may include, for example, AP 100 shown in Fig. 8 and terminal (STA) 200 shown in Fig. 9. Two or more of at least one of AP 100 and terminal 200 may be present in the wireless communication system. AP 100 may, for example, transmit a trigger frame (e.g., MU-RTS TXS Trigger frame) instructing TXOP sharing to terminal 200. Terminal 200 may receive the MU-RTS TXS Trigger frame and transmit a signal to AP 100 or another terminal based on resources (e.g., allocation time (or allocation period) and allocation band (or allocation channel)) instructed by the received MU-RTS TXS Trigger frame.

[0045] 8 is a block diagram showing a partial configuration example of an AP 100 according to an embodiment of the present disclosure. In the AP 100 shown in FIG. 8, a control unit (e.g., corresponding to a control circuit) generates a control signal (e.g., a trigger frame) that instructs multiple terminals to perform uplink transmission, the control signal including information (e.g., destination information) regarding the destination of the uplink transmission for each of the multiple terminals. A transmission unit (e.g., corresponding to a transmission circuit) transmits the control signal.

[0046] 9 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. 9, a receiver (e.g., corresponding to a receiver circuit) receives a control signal (e.g., a trigger frame) instructing uplink transmissions of multiple terminals, the control signal including information (e.g., destination information) regarding the destinations of the uplink transmissions for each of the multiple terminals. A controller (e.g., corresponding to a control circuit) controls the uplink transmissions based on the control signal.

[0047] [Configuration Example of AP 100] The AP 100 generates, for example, a trigger frame (for example, an MU-RTS TXS trigger frame) that instructs TXOP sharing to a plurality of terminals, and transmits the MU-RTS TXS trigger frame to the terminal 200.

[0048] Fig. 10 is a block diagram showing an example configuration of AP 100. AP 100 shown in Fig. 10 may include, for example, a scheduling unit 101, a common info generating unit 102, a user info generating unit 103, a trigger frame generating unit 104, an error correction coding unit 105, a modulation unit 106, a wireless transmission / reception unit 107, a demodulation unit 108, an error correction decoding unit 109, and a terminal information holding unit 110.

[0049] For example, the scheduling unit 101, the Common Info generating unit 102, the User Info generating unit 103, the Trigger frame generating unit 104, and the terminal information holding unit 110 may be included in an access control unit (e.g., a Medium Access Control (MAC) processing unit).

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

[0051] The scheduling unit 101 may perform scheduling for, for example, the terminal 200. For example, the scheduling unit 101 may determine a TXOP Sharing mode to be applied to the terminal 200 and allocated radio resources (including, for example, at least one of an allocation period and an allocation band in TXOP sharing) based on terminal information input from the terminal information storage unit 110.

[0052] For example, the TXOP Sharing mode may include the TXOP Sharing mode for multiple terminals in addition to the TXOP Sharing mode for one terminal described above. When the TXOP Sharing mode for multiple terminals is applied, the scheduling unit 101 may determine information about the destination of uplink transmission (hereinafter referred to as "destination information") for the multiple terminals 200 to which TXOP sharing is applied.

[0053] The destination information may include, for example, information indicating whether uplink transmission to the AP 100 is permitted. For example, the destination information may include information indicating a destination that is permitted to transmit and receive signals using the allocated radio resources. As an example, the destination information may be information indicating either permission to communicate with one of the AP 100 and a terminal other than the multiple terminals 200 to which TXOP sharing is applied, or permission to communicate with another terminal (or denial of permission to communicate with the AP 100).

[0054] The allocated radio resources may include, for example, a partial period (e.g., time resources) of the TXOP acquired by the AP 100. Furthermore, for example, when TXOP sharing to multiple terminals is applied by FDM, the allocated radio resources may include a channel (e.g., a band in 20 MHz units) to be allocated to each terminal 200. For example, the allocated radio resources (e.g., allocated band) may include at least a partial band of the band to which the trigger frame is allocated, or may include a band different from the band to which the trigger frame is allocated.

[0055] The terminal information may also include, for example, capability information of the terminal 200, a transmission buffer state, control information related to P2P settings, and information related to Sub-Channel Selective Transmission (SST) Mode.

[0056] The capability information may include, for example, information indicating whether the terminal 200 is capable of transmitting and receiving on a channel different from the primary channel (for example, a secondary channel). Furthermore, if the terminal 200 supports multi-link transmission, the capability information may include, for example, information indicating whether simultaneous transmission and reception are possible (for example, whether the terminal is capable of simultaneous transmit and receive (STR)).

[0057] The transmission buffer status may include, for example, information about the AC and size of a transmission buffer in the terminal 200 that is destined for the AP 100. The transmission buffer status may also include, for example, information about the AC and size of a transmission buffer that is destined for another terminal (e.g., also referred to as a "Direct Link Peer (DLP) STA") that is connected to the terminal 200 via a P2P link (or a Direct Link).

[0058] The P2P setting information may include, for example, terminal information (for example, a terminal ID) of the terminal that performs P2P communication with the terminal 200. The P2P setting information may also include, for example, information indicating whether or not to perform off-channel (a setting for performing P2P communication outside the operation band of the AP 100).

[0059] The information about the SST mode may include, for example, information indicating whether or not the SST mode is set for the terminal 200. Furthermore, if the terminal 200 is a terminal for which the SST mode is set, the information about the SST mode may include, for example, information indicating a sub-channel (a channel different from the primary channel) to be used when the target wake time (TWT) is applied.

[0060] The scheduling unit 101 outputs, for example, information on the determined TXOP sharing mode of each terminal 200 and the allocated radio resources to the common info generating unit 102 and the user info generating unit 103 .

[0061] The Common Info generating unit 102 may generate, for example, control information included in a Common Info field that is common to multiple terminals 200. The Common Info generating unit 102 may generate information in the Trigger type subfield and the TXOP sharing mode subfield based on information related to TXOP sharing input from the scheduling unit 101, for example.

[0062] Furthermore, the common info generating unit 102 may generate information about the allocation period for the terminal 200 based on information about the allocated radio resources input from the scheduling unit 101, for example.

[0063] The association between the TXOP sharing mode and the information indicating the TXOP sharing mode in the Trigger frame (the value of the TXOP sharing mode subfield) may be, for example, information in a table format (e.g., referred to as a "TXOP sharing mode table"), or information in a format other than a table. FIG. 11 is a diagram showing an example of the TXOP sharing mode table. The TXOP sharing mode table may be defined, for example, in a specification. The TXOP sharing mode table shown in FIG. 11 may include, for example, the TXOP sharing mode described in Non-Patent Document 1 shown in FIG. 5 (e.g., TXOP sharing mode = 0 to 2) and the TXOP sharing mode for multiple terminals 200 (e.g., TXOP sharing mode = 3).

[0064] For example, when implementing TXOP sharing, the Common Info generation unit 102 may generate an MU-RTS TXS Trigger frame by setting the Trigger type subfield to MU-RTS and the TXOP sharing mode subfield to a predetermined value (for example, in the case of the TXOP sharing mode table of Figure 11, any value greater than or equal to 1).

[0065] The Common Info generating unit 102 may output information relating to the generated Common Info field to the Trigger frame generating unit 104 .

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

[0067] The User Info generation unit 103 may generate, for example, control information to be included in a Special User Info field or a User Info field individual to the terminal 200. The User Info generation unit 103 may generate information on the Special User Info field or a User Info field individual to the terminal 200 based on a specified format, for example, and generate information on a User Info List including a User Info field for each of the multiple terminals 200. The User Info generation unit 103 may output the information on the User Info List to the Trigger frame generation unit 104, for example.

[0068] 12 , based on information on the allocated radio resources input from the scheduling unit 101, the User Info generating unit 103 may generate the ID of the terminal 200 (information in the AID12 subfield), information on the band allocated to the terminal 200 (for example, a band in 20 MHz channel units) (for example, information in the RU Allocation subfield), information on the allocation period to the terminal 200 (information in the Allocation Duration subfield), and destination information on destinations permitted to transmit and receive using the radio resources allocated to the terminal 200 (for example, information in the Destination Mode subfield). The User Info generating unit 103 may output the generated User Info List to the Trigger frame generating unit 104, for example.

[0069] Allocation band information for terminal 200 (for example, information notified in the RU allocation subfield in FIG. 12 ) may indicate, for example, the position of a 20 MHz×N frequency resource allocated to terminal 200. For example, as a method for notifying the position of the 20 MHz×N frequency resource, a method for notifying the frequency resource of a CTS frame by MU-RTS used in 11ax may be applied.

[0070] FIG. 13 is a diagram showing an example of a method for notifying frequency resources using an MU-RTS Trigger frame. In MU-RTS supported in IEEE 802.11ax, for example, frequency resources for CTS may be individually notified to terminal 200 by combining a "UL BW subfield" included in the Common Info field of the MU-RTS Trigger frame and an "RU Allocation subfield" included in the User Info field of the MU-RTS Trigger frame. For example, as shown in FIG. 13 , the UL BW subfield specifies the uplink Operation bandwidth (e.g., 20 MHz, 40 MHz, 80 MHz, or 160 MHz), and the RU allocation subfield specifies the location of frequency resources allocated to communications in the allocation period. In this embodiment, for example, the channel to be used by terminal 200 in the TXOP sharing allocation period may be indicated by a method similar to the method shown in FIG. 13 . Note that the channel to be used by terminal 200 in the TXOP sharing allocation period may also be indicated by a method different from the method shown in FIG. 13 .

[0071] Furthermore, in an Operation band including 320 MHz newly supported in 11be, when the location of a frequency resource for communication in an allocation period is notified, for example, the "UL Bandwidth Extension subfield" included in the Special User Info field shown in Fig. 4 may be used. For example, the Operation bandwidth may be notified to terminal 200 by combining the UL BW subfield of the Common Info field and the UL Bandwidth Extension subfield of the Special User Info field.

[0072] The notification method shown in FIG. 13 is a method for notifying the location of frequency resources including the Primary 20 MHz channel, but the present embodiment is not limited to this. For example, as shown in FIG. 14, a method for notifying frequency resources of any 20 MHz×N channels within the Operation band that does not include the Primary 20 MHz channel may be used.

[0073] In addition, information regarding the allocation period to terminal 200 (for example, information notified in the Allocation Duration subfield of Figure 12) may include, for example, information indicating the allocation period to be shared with terminal 200 within the TXOP acquired by AP 100, at a predetermined time granularity (for example, in units of 16 us) and within a range of a predetermined time length (for example, up to 8 ms) from the end timing of the MU-RTS TXS TF.

[0074] Furthermore, destination information regarding destinations permitted to transmit and receive using the allocated radio resources (e.g., information notified in the Destination Mode subfield in FIG. 12) may include, for example, the information shown in FIG. 15. As shown in FIG. 15, for example, when the value of the Destination Mode subfield is 0, another terminal is set as the destination permitted to transmit and receive using the allocated radio resources, and AP 100 may not be set (for example, it may be set only to another terminal). As shown in FIG. 15, for example, when the value of the Destination Mode subfield is 1, AP 100 or another terminal may be set as the destination permitted to transmit and receive using the allocated radio resources.

[0075] Note that destination information permitted for transmission and reception using the allocated radio resources may be notified to terminal 200, for example, when a TXOP sharing mode is applied to multiple terminals (for example, when the TXOP Sharing Mode subfield value is 3 in FIG. 11 ). For example, when a TXOP Sharing mode is applied to one terminal, destination information permitted for transmission and reception using the allocated radio resources does not need to be notified to terminal 200.

[0076] Furthermore, the number of User Info fields included in the User Info List may be associated with, for example, the TXOP sharing mode indicated in the TXOP sharing mode subfield. For example, when the TXOP sharing mode is a mode that applies TXOP sharing to one terminal (for example, when TXOP sharing mode = 1 or 2 is indicated in the TXOP sharing mode table shown in FIG. 11), the User Info List may include one User Info field. When the TXOP sharing mode is a mode that applies TXOP sharing to multiple terminals (for example, when TXOP sharing mode = 3 is indicated in the TXOP sharing mode table shown in FIG. 11), the User Info List may include multiple User Info fields.

[0077] Note that the Special User Info field may include control information for one terminal 200, regardless of the TXOP sharing mode.

[0078] The trigger frame generation unit 104 may generate a trigger frame including information in the Common Info field input from the Common Info generation unit 102 and information in the User Info List (e.g., a Special User Info field and at least one User Info field) input from the User Info generation unit 103, based on the format shown in Fig. 1, for example. The trigger frame may include at least one of a MAC header, padding, and frame check sequence (FCS) in addition to the Common Info field and the User Info List. The trigger frame generation unit 104 may output the generated trigger frame to the error correction coding unit 105, for example.

[0079] The error correction coding unit 105 performs error correction coding on the transmission data signal including the trigger frame input from the trigger frame generation unit 104, and outputs the coded signal to the modulation unit .

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

[0081] In addition, if the modulated data signal is an Orthogonal Frequency Division Multiplexing (OFDM) signal, the AP 100 (e.g., the modulation unit 106) 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).

[0082] The radio transmitting / receiving unit 107 performs radio transmission processing such as D / A conversion and up-conversion to a carrier frequency on the modulated signal input from the modulation unit 106, and transmits the signal after the radio transmission processing via an antenna to the terminal 200. The radio transmitting / receiving unit 107 also receives a signal transmitted from the 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 the radio reception processing to the demodulation unit 108.

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

[0084] The error correction decoding unit 109, for example, decodes the signal input from the demodulation unit 108 to obtain a received data signal from the terminal 200. For example, if the above-mentioned terminal information is included in the received data after decoding, the error correction decoding unit 109 outputs decoded data including the terminal information to the terminal information holding unit 110.

[0085] The terminal information holding unit 110 may, for example, acquire (or hold) terminal information (which may include, for example, capability information of the terminal 200, transmission buffer status, P2P setting information, or information regarding SST Mode) from the decoded data input from the error correction decoding unit 109, and output the acquired terminal information to the scheduling unit 101.

[0086] [Configuration Example of Terminal 200] Terminal 200 receives, for example, from AP 100, a trigger frame (for example, an MU-RTS TXS trigger frame) instructing TXOP sharing, and transmits an uplink response signal (for example, a CTS frame) in response to the trigger frame to AP 100. Then, based on the instruction of the MU-RTS TXS trigger frame, for example, terminal 200 communicates with an authorized destination (for example, AP 100 or another terminal) using the allocated channel within the allocation period.

[0087] Fig. 16 is a block diagram showing an example configuration of terminal 200. Terminal 200 shown in Fig. 16 may include, for example, a radio transceiver 201, a demodulator 202, an error correction decoder 203, a common info acquirer 204, a user info acquirer 205, a scheduling unit 206, a data generator 207, an error correction encoder 208, and a modulator 209.

[0088] For example, at least one of the Common Info acquisition unit 204, the User Info acquisition unit 205, the scheduling unit 206, and the data generation unit 207 may be included in an access control unit (for example, a MAC processing unit).

[0089] Furthermore, at least one of the demodulation unit 202, error correction decoding unit 203, Common Info acquisition unit 204, User Info acquisition unit 205, scheduling unit 206, data generation unit 207, error correction coding unit 208, and modulation unit 209 shown in Fig. 16 may be included in, for example, the control unit shown in Fig. 9. Furthermore, the wireless transmission / reception unit 201 shown in Fig. 16 may be included in, for example, the receiving unit shown in Fig. 9.

[0090] 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 209, and transmits the signal after radio transmission processing from the antenna.

[0091] Demodulation section 202 performs demodulation processing on received data input from wireless transmission / reception section 201, for example, and outputs the demodulated signal to error correction decoding section 203. Note that when 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.

[0092] 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 204 and the user info acquisition unit 205.

[0093] The Common Info acquisition unit 204 may extract information corresponding to the Common Info field from the Trigger frame input from the error correction decoding unit 203, for example, and acquire terminal common information regarding TXOP sharing.

[0094] The terminal common information regarding TXOP sharing may include, for example, information on the TXOP sharing mode and information on the channel assigned to terminal 200. The terminal common information may also include information on the assignment period to terminal 200. The terminal common information may also include, for example, information indicating that the TXOP sharing mode is FDM-based for multiple terminals.

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

[0096] The User Info acquisition unit 205 may, for example, extract information corresponding to the User Info List (e.g., at least one User Info field 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 TXOP sharing mode) input from the Common Info acquisition unit 204. For example, when the TXOP sharing mode indicates TXOP sharing to multiple terminals, the User Info acquisition unit 205 may perform reception processing of multiple User Info fields. Furthermore, when the TXOP sharing mode indicates TXOP sharing to a single terminal, the User Info acquisition unit 205 may perform reception processing of a single User Info field.

[0097] For example, the User Info acquisition unit 205 may decode information identifying the terminal 200 (e.g., a terminal ID or an AID) included in the User Info field, and when it determines that there is an allocation instruction addressed to the terminal 200, it may acquire at least one of terminal-specific information regarding TXOP sharing (e.g., allocated radio resources such as an allocation period and an allocation channel, and destination information regarding destinations that are permitted to transmit and receive using the allocated radio resources) and terminal-common information (e.g., including information on the TXOP Sharing Mode and UL BW) from the User Info field.

[0098] The User Info acquisition unit 205 may output, for example, the terminal-specific information and the terminal-common information to the scheduling unit 206 and the data generation unit 207 .

[0099] The scheduling unit 206 may determine the allocated radio resources and the destination of uplink transmission, for example, based on information (including, for example, terminal-specific information and terminal-common information) input from the user information acquisition unit 205. The scheduling unit 206 may control data transmission in the allocated radio resources for TXOP sharing instructed by the AP 100, for example, based on the allocated radio resources. The control of data transmission may include, for example, control of the allocation period, the allocation channel, and the destination within the allocation period.

[0100] The scheduling unit 206 may output, for example, control information related to data generation (including, for example, radio parameters to be applied to the data signal (signal length, modulation method, error correction coding rate, spatial multiplexing number, transmission power, etc.)) to the data generation unit 207.

[0101] Here, some of the radio parameters to be applied to the data signal (for example, at least one of the signal length, modulation method, error correction coding rate, spatial multiplexing number, and transmission power) may be determined by the terminal 200 based on parameters such as the transmission buffer state or communication quality of the terminal 200. In other words, some of the radio parameters to be applied to the data signal do not need to be instructed by the AP 100.

[0102] The length of the data signal may be, for example, within the allocation period instructed by the AP 100. The transmission channel to be assigned to the data signal may be determined based on the assigned channel instructed by the AP 100.

[0103] Furthermore, the destination of a signal during the allocation period may be determined according to information acquired by the User Info acquisition unit 205. For example, in the definition shown in Fig. 15, if the Destination Mode subfield value of the User Info field is 0, the scheduling unit 206 sets (for example, limits) the destination of a signal during the allocation period to another terminal that has P2P configured. For example, if the Destination Mode subfield value is 0, the AP 100 does not need to be set as the destination of a signal during the allocation period.

[0104] 15, for example, when the Destination Mode subfield value is 1, the scheduling unit 206 sets the destination of the signal during the allocation period to another terminal for which P2P is set, or to the AP 100. For example, the scheduling unit 206 may select the destination according to the priority of the transmission packet.

[0105] The data generation unit 207 generates a data signal (e.g., a CTS frame, data addressed to AP 100, or data addressed to another terminal) based on, for example, control information input from the scheduling unit 206 and information input from the User Info acquisition unit 205, and outputs the data signal to the error correction coding unit 208.

[0106] For example, the data generator 207 may generate a CTS frame after (e.g., immediately after) receiving an MU-RTS TXS Trigger frame. Furthermore, the data generator 207 may generate a data signal (e.g., SU-PPDU) for a permitted destination after (e.g., SIFS after) transmitting the CTS frame.

[0107] The error correction coding unit 208 performs error correction coding on the data signal input from the data generation unit 207, and outputs the coded signal to the modulation unit 209. Note that the coding rate for the data signal may be determined by the terminal 200, for example.

[0108] Modulation section 209 modulates the signal input from error correction coding section 208 and outputs the modulated signal to radio transmission / reception section 201. Note that the modulation scheme applied in modulation section 209 may be determined by, for example, terminal 200. Furthermore, when the modulated signal is an OFDM signal, terminal 200 (for example, modulation section 209) may form the OFDM signal by mapping the modulated signal to frequency resources, performing IFFT processing, and adding a CP.

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

[0110] Below, we will explain a method of instructing TXOP sharing (e.g., allocation of a portion of the transmission opportunity (TXOP) acquired by AP100) to multiple terminals 200 (e.g., Non-AP terminals) other than AP100 using one Trigger frame (e.g., MU-RTS TXS Trigger frame) generated by AP100 (e.g., Common Info generation unit 102, User Info generation unit 103, and Trigger frame generation unit 104).

[0111] The plurality of terminals 200 other than the AP 100 may include, for example, a pair of terminals 200 that perform P2P communication (for example, terminal-to-terminal communication).

[0112] <Example of Notification of Terminal Common Information> The terminal common information may include, for example, information on the TXOP sharing mode.

[0113] The AP 100 may generate information for the TXOP sharing mode subfield (e.g., TXOP sharing mode subfield value) based on, for example, the TXOP sharing mode table shown in Fig. 11. The TXOP sharing mode table shown in Fig. 11 may include, for example, information instructing TXOP sharing to multiple terminals (e.g., TXOP Sharing Mode subfield value = 3).

[0114] For example, when instructing TXOP sharing to multiple terminals 200 different from the AP 100, the AP 100 may generate a Trigger frame including information indicating TXOP sharing mode subfield value = 3 in the TXOP sharing mode table shown in Fig. 11. For example, the AP 100 may set information regarding TXOP sharing to multiple terminals (for example, information instructing multiple terminals to share a transmission opportunity) in a Common Info field common to the terminals 200 in the Trigger frame.

[0115] Furthermore, when setting information regarding TXOP sharing for multiple terminals, the AP 100 may set, for example, multiple individual User Info fields for multiple terminals 200 to which TXOP sharing applies in the Trigger frame.

[0116] <Example of notification of terminal-specific information> The terminal-specific information may include, for example, information about the band allocated to the terminal 200 (e.g., 20 MHz×N band), information about the period allocated to the terminal 200, and destination information for which transmission and reception using the radio resources allocated to the terminal 200 are permitted.

[0117] The allocated band may be set to, for example, a band included in the transmission band of the MU-RTS TXS Trigger frame transmitted by the AP 100. For example, the allocated band may be at least a part of the band to which the MU-RTS TXS Trigger frame is allocated.

[0118] The allocation period may be set to, for example, a part of the TXOP period acquired by the AP 100. Also, different periods may be instructed to the multiple terminals 200 as allocation periods.

[0119] Note that information regarding the allocation period may not necessarily be included in the terminal-specific information, but may also be included in other fields. For example, information regarding the allocation period may be included in some subfields (e.g., UL Length subfield, Reserved subfield) of the Common Info field as terminal-common information.

[0120] 15, for example, another terminal (for example, the terminal 200 and a terminal configured for P2P) may be set (for example, limited) as a destination permitted for transmission and reception using the allocated wireless resources, or the AP 100 and the other terminal may be set. When the AP 100 and the other terminal are set as the destination information, the terminal 200 may select either the AP 100 or the other terminal as a destination.

[0121] For example, as shown in FIG. 12, AP 100 may set a subfield (e.g., Destination Mode subfield) indicating destination information in the User Info field in the area B29, which is a reserved area in the existing User Info field of FIG. 3.

[0122] The name of the subfield that indicates the destination information is not limited to Destination Mode, and may be other names. The subfield that indicates the destination information is not limited to the B29 area, and may be set to other areas. The types of destinations that can be notified in the destination information (e.g., destination candidates) are not limited to the two types shown in FIG. 15 , and may be three or more types.

[0123] Furthermore, for example, when TXOP sharing mode to multiple terminals is applied (for example, when TXOP sharing mode = 3 in Figure 11), the B29 area of ​​the User Info field shown in Figure 12 may be set to the Destination Mode subfield, and when TXOP sharing to multiple terminals is not applied, the B29 area of ​​the User Info field shown in Figure 12 may be set to another subfield (for example, a Reserved area).

[0124] For example, in the definition shown in Fig. 15, when the Destination Mode subfield = 0, the destination permitted for transmission and reception using the allocated wireless resources of terminal 200 indicated by the AID12 subfield shown in Fig. 12 is set to another terminal (for example, a P2P terminal), and AP 100 does not have to be set. For example, when the Destination Mode subfield value = 0, the destination is limited to another terminal (for example, a P2P terminal), and uplink transmission to AP 100 is not permitted.

[0125] 15, for example, when the Destination Mode subfield value is 1, either the AP 100 or another terminal (e.g., a P2P terminal) may be set as the destination permitted for transmission and reception using the allocated wireless resource of the terminal 200 indicated by the AID12 subfield shown in Fig. 12. For example, when the Destination Mode subfield value is 1, uplink transmission to the AP 100 may be permitted.

[0126] Note that the association between the Destination Mode subfield value and the destinations (for example, P2P terminals, and the AP 100 and P2P terminals) that are permitted to transmit and receive using the allocated wireless resources is not limited to the example shown in Fig. 15. For example, the destination may be set so that transmission and reception with the AP 100 is permitted, but transmission and reception with P2P terminals is not permitted.

[0127] Furthermore, when the Destination Mode subfield value = 1, the destination of the signal transmitted from terminal 200 and the time length of the transmitted signal may be determined by terminal 200, for example.

[0128] For example, among multiple terminals 200 (including, for example, terminal 1 and terminal 2) instructed to share TXOPs by one MU-RTS TXS Trigger frame, if the transmission band of terminal 1 is set to Primary 20 MHz, the transmission band of terminal 2 may be set to a frequency resource that does not include a primary channel. In this case, terminal 2 may transmit a CTS frame and data using, for example, a frequency resource that does not include a primary channel (for example, a band instructed for terminal 2) in response to the MU-RTS TXS Trigger frame.

[0129] Furthermore, terminal 200 that has received the MU-RTS TXS Trigger frame may transmit a CTS frame based on, for example, a carrier sense result in the frequency resource for CTS notified by the MU-RTS TXS Trigger frame. For example, if the frequency resource for CTS notified by the MU-RTS TXS Trigger frame does not include the primary channel, terminal 200 may transmit a CTS frame in the notified frequency resource even if the primary channel is busy.

[0130] The base station 100 may receive a response signal (CTS frame) to the MU-RTS TXS Trigger frame, for example, in an allocated band for each terminal 200 indicated by the MU-RTS TXS Trigger frame (for example, the transmission band of the terminal 200 or a frequency resource for CTS).

[0131] The method of notifying the allocation channel is not limited to the above-described case of indicating the location of the 20 MHz×N frequency resource allocated to terminal 200, but may be a method of notifying other frequency resources.

[0132] FIG. 17 is a diagram showing an example of a sequence in which TXOP sharing is instructed to a plurality of terminals, and each terminal 200 is instructed as to a transmission destination for which transmission and reception using the allocated radio resources is permitted.

[0133] In Figure 17, for example, AP 100 (referred to as "AP") may instruct information regarding TXOP sharing mode to multiple terminals 200 other than AP 100 (Non-AP STA 1 (hereinafter, terminal 1) and Non-AP STA 3 (hereinafter, terminal 3) in Figure 17) as terminal common information.

[0134] For example, the multiple terminals 200 to which TXOP sharing with multiple terminals is applied may be terminals for which P2P is configured (for example, TDLS is configured or Direct link is configured). In the example shown in Fig. 17, a P2P link (for example, TDLS is configured) is configured in advance between terminal 1 and Non-AP STA 2 (hereinafter, terminal 2), and a P2P link (TDLS is configured) is configured in advance between terminal 3 and Non-AP STA 4 (hereinafter, terminal 4). For example, in Fig. 17, the AP 100 may instruct terminal 1 and terminal 3 to share TXOP with multiple terminals by notifying them of the TXOP sharing mode subfield value = 3 shown in Fig. 11.

[0135] 17, for example, AP 100 may notify, as terminal-specific information for each of a plurality of terminals 200 (e.g., terminal 1 and terminal 3), destination information permitted for transmission and reception using the allocated radio resources (e.g., permission for communication with either another terminal or AP 100, or permission for communication with another terminal), information regarding the allocation channel (e.g., RU allocation), and information regarding the allocation period (e.g., Time allocated in MU-RTS TXS TF shown in FIG. 17). Note that in the example of FIG. 17, the same period is specified as the allocation period for terminal 1 and terminal 3.

[0136] For example, in Fig. 17 , AP 100 may use the MU-RTS TXS Trigger frame to notify terminal 1 of a Destination Mode subfield value = 1, thereby instructing terminal 2 or AP 100 as a destination for which transmission and reception using the allocated radio resources is permitted. Also, for example, in Fig. 17 , AP 100 may use the MU-RTS TXS Trigger frame to notify terminal 3 of a Destination Mode subfield value = 0, thereby instructing terminal 4 as a destination for which transmission and reception using the allocated radio resources is permitted. In other words, in Fig. 17 , AP 100 permits terminal 1 to perform uplink transmission to AP 100, and does not permit terminal 3 to perform uplink transmission to AP 100.

[0137] 17, the AP 100 may instruct, for example, terminal 1 and terminal 3 to communicate using orthogonal frequency resources (20 MHz×N channels). In the example shown in FIG. 17, 20 MHz channel #1 is instructed to terminal 1, and 20 MHz channel #2 is instructed to terminal 3.

[0138] In Figure 17, for example, based on the received MU-RTS TXS Trigger frame, terminal 1 and terminal 3 may transmit a CTS frame (CTS response) addressed to AP 100 and a data signal (DATA) to each destination in their respective allocated channels during the TXOP sharing allocation period.

[0139] For example, in Fig. 17, terminal 1 may transmit a CTS frame to AP 100 on the specified 20 MHz channel #1, and then transmit a data signal (e.g., SU PPDU) to AP 100, which is permitted as one of the destinations. Also, for example, in Fig. 17, terminal 3 may transmit a CTS frame to AP 100 on the specified 20 MHz channel #2, and then transmit a data signal to terminal 4, which is permitted as a destination.

[0140] In this way, the AP 100 may, for example, cause each terminal 200 to transmit (e.g., return) a CTS frame in the allocated band (e.g., including a band that does not include the Primary channel) instructed in the MU-RTS TXS Trigger frame. In this way, the AP 100 can grasp that the scheduled terminal 200 has started communication in the allocated period (e.g., that the instruction from the AP 100 has been transmitted successfully) by receiving the CTS frame in the allocated band instructed in the MU-RTS TXS Trigger frame.

[0141] Also, for example, in the example shown in Figure 17, during the TXOP Sharing allocation period, of terminal 1 and terminal 3 to which TXOP Sharing is applied, terminal 1 is allowed to communicate with AP 100, and terminal 3 is not allowed to notify AP 100.

[0142] With this setting, the AP 100 communicates (e.g., receives a data signal and transmits an ACK) with one terminal 200 (e.g., terminal 1) of terminals 1 and 3 to which TXOP sharing is applied during the TXOP sharing allocation period. For example, in the example shown in FIG. 17 , the AP 100 communicates with terminal 1 during the TXOP sharing allocation period, but does not communicate with terminals 2 to 4 other than terminal 1. This allows the AP 100 to prevent the timing of transmitting a signal (e.g., a Block Ack) to terminal 1 from overlapping with the timing of receiving a signal from another terminal (e.g., any of terminals 2 to 4), as shown in FIG. 17 . Furthermore, the AP 100 can prevent the timing of receiving a signal from terminal 1 from overlapping with the timing of transmitting a signal to another terminal (e.g., any of terminals 2 to 4).

[0143] As described above, in this embodiment, the AP 100 generates and transmits a Trigger frame that instructs multiple terminals to perform uplink transmission, and that includes destination information regarding the destination of the uplink transmission for each of the multiple terminals 200. For example, the AP 100 instructs the multiple terminals 200 to communicate with one of the multiple terminals 200 to which TXOP sharing is applied during the TXOP sharing allocation period by providing destination information (e.g., whether or not uplink transmission to the AP 100 is permitted).

[0144] This allows a single trigger frame to instruct multiple terminals 200 to share TXOPs, thereby improving allocation efficiency in TXOP sharing.

[0145] Furthermore, in this embodiment, for example, the destination of the TXOP shared time resource can be appropriately controlled for multiple terminals 200 (e.g., P2P terminals), and therefore overlapping of the transmission timing and reception timing for multiple terminals 200 at the AP 100 can be prevented. Therefore, for example, overlapping of an ACK frame transmitted from the AP 100 to a certain terminal 200 with an SU PPDU frame transmitted from another terminal 200 to the AP 100 can be prevented. This makes it possible to prevent retransmission of the SU PPDU of another terminal 200 due to the AP 100 being unable to receive the SU PPDU frame from that other terminal 200, and improves the utilization efficiency of the time resource allocated by the AP 100.

[0146] Also, in Figure 17, for example, at least some of the radio parameters used for TXOP sharing may be determined (or scheduled) by terminal 200 without being scheduled by AP 100, so TXOP sharing for multiple terminals 200 can be achieved with simple processing.

[0147] Therefore, according to this embodiment, it is possible to improve allocation efficiency in TXOP sharing in wireless communication.

[0148] Note that, for example, when AP 100 has a function of suppressing self-interference, it does not need to suppress overlapping of transmission timing and reception timing in AP 100. For example, in FIG. 17 , when AP 100 has a function of suppressing self-interference, it may notify both terminal 1 and terminal 3 of Destination Mode subfield value = 1 using the MU-RTS TXS Trigger frame. This allows, for example, both terminal 1 and terminal 3 to specify another terminal (terminal 2 or terminal 4) or AP 100 as a destination for which transmission and reception using the allocated radio resources is permitted, and terminal 1 and terminal 3 can flexibly select the destination for uplink transmission.

[0149] Furthermore, in this embodiment, AP 100 notifies terminal 200 of TXOP sharing for multiple terminals based on the MU-RTS TXS Trigger frame format agreed upon in 11be Release 1 (e.g., a format specified in 11be Release 1). This allows a common Trigger frame format to be applied between, for example, a terminal compatible with 11be Release 1 that supports TXOP sharing for one terminal (e.g., referred to as an "11be Release 1 compatible terminal") and terminal 200 that supports TXOP sharing for multiple terminals in this embodiment (e.g., a terminal compatible with a future version). For example, by using the MU-RTS TXS Trigger frame format described in this embodiment to set (e.g., limit to some values) the TXOP sharing mode supported by 11be Release 1 compatible terminals (e.g., a value of 0, 1, or 2), AP 100 can notify the TXOP sharing mode for 11be Release 1 compatible terminals.

[0150] (First Variation of First Embodiment) In the example shown in Fig. 17 , a case has been described in which the destination information indicates destinations that are permitted to transmit and receive using allocated radio resources for the entire allocation period for multiple terminals 200. Therefore, in the example shown in Fig. 17 , when terminal 1 and terminal 3 each hold transmission data addressed to AP 100 in a buffer, terminal 3 is not permitted to transmit to AP 100, and therefore does not transmit transmission data addressed to AP 100 during the TXOP sharing allocation period. The contents of instructions given by the destination information are not limited to this.

[0151] In the first modification, for example, the terminal-specific information notified by the AP 100 may include destination information for which transmission and reception using the allocated radio resources is permitted for each portion of the TXOP sharing allocation period, as shown in Fig. 18. For example, the destination information may indicate the destination of uplink transmission for each of a plurality of portions (or time periods) obtained by dividing the TXOP sharing allocation period (a portion of the TXOP time period).

[0152] In the example shown in FIG. 18 , the destination information (e.g., information in the Destination Mode subfield) may indicate destinations that are permitted to transmit and receive using the allocated radio resources in each of the first and second halves of the allocation period, by dividing the allocation period into a first half and a second half.

[0153] For example, in FIG. 18 , when the value of the Destination Mode subfield is 0, communication to AP 100 is set to be disallowed in both the first and second halves of the allocation period. When the value of the Destination Mode subfield is 1, communication to AP 100 is set to be disallowed in the first half of the allocation period, and communication to AP 100 is set to be allowed in the second half of the allocation period. When the value of the Destination Mode subfield is 2, communication to AP 100 is set to be allowed in the first half of the allocation period, and communication to AP 100 is set to be disallowed in the second half of the allocation period. When the value of the Destination Mode subfield is 3, communication to AP 100 is set to be allowed in both the first and second halves of the allocation period.

[0154] FIG. 19 is a diagram showing an example of a sequence in which TXOP sharing is instructed to a plurality of terminals, and each terminal 200 is instructed as to a transmission destination for which transmission and reception using the allocated radio resources is permitted.

[0155] In the example shown in FIG. 19 , AP 100 communicates (e.g., receives a data signal and transmits an ACK) with one of terminals 1 and 3, to which TXOP sharing is applied, during each portion (first half and second half) of the TXOP sharing allocation period. For example, AP 100 may use the MU-RTS TXS Trigger frame to notify terminal 1 of a Destination Mode subfield value = 2 and to notify terminal 3 of a Destination Mode subfield value = 1. As a result, as shown in FIG. 19 , AP 100 communicates with terminal 1 during the first half of the TXOP sharing allocation period, but does not communicate with terminals 2, 3, and 4, which are different from terminal 1. Also, as shown in FIG. 19 , AP 100 communicates with terminal 3 during the second half of the TXOP sharing allocation period, but does not communicate with terminals 1, 2, and 4, which are different from terminal 3.

[0156] In this way, in the first modification, the AP 100 instructs a terminal 200 to communicate with one of the multiple terminals 200 to which TXOP sharing is applied during the TXOP sharing allocation period, thereby preventing overlapping of transmission and reception timings at the AP 100. Also, in the first modification, as shown in Fig. 19 , by dividing the period during which transmission to the AP 100 is permitted during the TXOP sharing allocation period, each of the multiple terminals 200 (e.g., terminal 1 and terminal 3) to which TXOP sharing is applied can transmit transmission data addressed to the AP 100 even if each holds transmission data addressed to the AP 100 in a buffer.

[0157] 18 and 19, the case where the TXOP sharing allocation period is equally divided into the first half and the second half has been described, but the method for dividing the TXOP sharing allocation period is not limited to this. For example, the number of divisions into which the allocation period is divided is not limited to two, and it may be divided into three or more periods (or portions). Furthermore, the allocation period is not limited to being equally divided, and may be divided unevenly.

[0158] 18 has described, as an example, a case in which transmission to another terminal is permitted regardless of the value of the Destination Mode subfield, but the present invention is not limited to this, and whether or not transmission to another terminal is permitted may be set according to the value of the Destination Mode subfield. For example, for any value of the Destination Mode subfield, transmission to AP 100 may be permitted, and transmission to another terminal may be set not to be permitted.

[0159] (Variation 2 of Embodiment 1) In Variation 1, as a method for notifying destination information indicating destinations that are permitted to transmit and receive using allocated radio resources for each part of the TXOP sharing allocation period, a case has been described in which an association between a combination of whether transmission and reception are permitted in each part of the allocation period and the value of the Destination Mode subfield is defined, as shown in FIG. 18 , but the present invention is not limited to this.

[0160] In the second modification, as a method of notifying destination information indicating destinations permitted to transmit and receive using the allocated radio resources for each portion of the TXOP sharing allocation period, the AP 100 may notify the same terminal 200 of multiple User Info fields corresponding to each portion of the allocation period. For example, the AP 100 may instruct the same terminal 200 of destination information (e.g., Destination Mode) indicating whether transmission and reception using the allocated radio resources is permitted for each Allocation Duration in multiple User Info fields (e.g., for each portion of the allocation period).

[0161] For example, multiple User Info fields with the same AID (or duplicated AIDs) set may be placed in one Trigger frame, as shown in Fig. 20. Each of the multiple User Info fields corresponds to a different period (portion) within the allocation period, and different values ​​can be set in the destination information (e.g., the value of the Destination Mode subfield) in each User Info field.

[0162] 19 , even when terminal 1 and terminal 3 each hold transmission data addressed to AP 100 in a buffer, the allocation period during which transmission to AP 100 is permitted can be flexibly set (e.g., divided) according to the amount of transmission data buffered in each of terminal 1 and terminal 3. Therefore, according to Modification 2, transmission data addressed to AP 100 can be efficiently transmitted.

[0163] (Embodiment 2) In this embodiment, a case will be described in which TXOP sharing is performed with different allocation periods for a plurality of terminals (for example, STAs).

[0164] The wireless communication system according to this embodiment may include an AP 100 and a terminal 200, similar to the first embodiment.

[0165] AP100 can improve the efficiency of wireless resource utilization and system performance by, for example, setting different allocation times for each terminal 200 (e.g., P2P terminal) performing P2P, depending on the transmission buffer capacity of each terminal 200.

[0166] For example, in TXOP sharing, depending on the settings of the secondary channel and the allocation period, the resource utilization efficiency of the allocation period may decrease.

[0167] As an example, a case will be described in which 20 MHz channel #1 (primary channel) is allocated to terminal 1 (non-AP STA 1) and 20 MHz channel #2 (secondary channel) is allocated to terminal 3 (non-AP STA 3) as shown in Fig. 21. As shown in Fig. 21, the allocation periods (time allocated in MU-RTS TXS TF) set for terminal 1 and terminal 3 are different. For example, the allocation period set for terminal 3 is shorter than the allocation period set for terminal 1.

[0168] 21, after the allocation period of 20 MHz channel #2 (secondary channel) to terminal 3 ends, the radio resource (allocated band) of 20 MHz channel #2 (secondary channel) indicated by the dotted line becomes an available resource, and the radio resource of 20 MHz channel #1 (primary channel) is used by terminal 1. Therefore, because the primary channel is being used by terminal 1, the carrier sense result of AP 100 becomes Busy. Therefore, even though the radio resource (allocated band) of 20 MHz channel #2 (secondary channel) is an available resource (for example, the carrier sense result is Idle), AP 100 cannot transmit a signal in the resource corresponding to the secondary channel, which may result in a reduction in system performance.

[0169] In this embodiment, a method for efficiently performing TXOP sharing with different allocation periods for a plurality of terminals 200 using one MU-RTS TXS Trigger frame will be described.

[0170] [Configuration of Base Station] An example configuration of the AP 100 according to this embodiment may be the same as that shown in Fig. 10. For example, in the AP 100 according to this embodiment, the operation of the scheduling section 101 may be different from that in the first embodiment.

[0171] The scheduling unit 101 determines the allocation period and the allocated radio resources to be applied to the terminal 200 based on the terminal information input from the terminal information holding unit 110, for example.

[0172] For example, the scheduling unit 101 may determine the allocation period for each terminal 200 according to the transmission buffer capacity of the terminal 200 to be scheduled. Furthermore, the scheduling unit 101 may, for example, among multiple terminals 200 to be scheduled using one MU-RTS TXS Trigger frame, more easily allocate the allocation band to a primary channel (20 MHz×N channels including a 20 MHz primary channel) for a terminal 200 with a shorter determined allocation period. For example, among multiple terminals 200 to be scheduled using one MU-RTS TXS Trigger frame, the scheduling unit 101 may allocate the primary channel to the terminal 200 with the shortest allocation period, and allocate secondary channels to the other terminals 200. As a result, during the TXOP sharing allocation period (e.g., a portion of the TXOP), the allocation time for terminals 200 allocated to the primary channel among the multiple terminals 200 is shorter than the allocation time for terminals 200 allocated to the secondary channel.

[0173] Furthermore, scheduling section 101 may determine the data length (e.g., PPDU length) to be transmitted after the end of an allocation period on the primary channel, for example, based on the difference in allocation times to multiple terminals 200. For example, scheduling section 101 may determine the data length (e.g., PPDU length) based on the difference between the allocation period on the secondary channel and the allocation period on the primary channel, among the allocation times to multiple terminals 200. For example, the PPDU length to be transmitted after the end of an allocation period on the primary channel may be determined based on the difference between the maximum allocation period and the minimum allocation period between terminals 200 to be scheduled.

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

[0175] [Terminal Configuration] An example configuration of terminal 200 according to this embodiment may be the same as that shown in Fig. 16. For example, in terminal 200 according to this embodiment, the operation of demodulation section 202 may be different from that in the first embodiment.

[0176] For example, in embodiment 1, the demodulation unit 202 first performs demodulation processing on the primary channel determined by the AP 100 to connect to, and if the demodulated signal is not a signal addressed to the terminal 200, does not perform demodulation processing on the secondary channel.

[0177] In this embodiment, for example, when TXOP Sharing for multiple terminals 200 is applied in an MU-RTS TXS Trigger frame, the specification may be such that PPDU transmission to a secondary channel that does not include a primary channel is permitted during the TXOP period acquired by AP 100 (for example, the period notified in the UL Length subfield of the terminal common information of the Trigger Frame).

[0178] Therefore, in this embodiment, for example, within the TXOP time of AP 100 or within the time notified by the MU-RTS TXS Trigger frame (e.g., UL length subfield), AP 100 and terminal 200 may be permitted to communicate on a secondary channel that does not include the primary channel.

[0179] In the terminal 200, the demodulation unit 202 may perform the same demodulation process on the secondary channel in addition to the primary channel. For example, the demodulation unit 202 may perform the demodulation process on the secondary channel regardless of whether the signal demodulated on the primary channel is a signal addressed to the terminal 200.

[0180] In order to reduce the amount of processing in terminal 200, terminal 200 that performs demodulation processing of the Secondary channel may be limited to terminal 200 indicated in the User Info subfield of the MU-RTS TXS Trigger frame.

[0181] The processing of the other components in the terminal 200 may be the same as that in the first embodiment, for example.

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

[0183] FIG. 22 is a diagram showing an example of a sequence in which TXOP sharing is instructed to a plurality of terminals 200 and each terminal 200 is instructed as to a transmission destination for which transmission and reception using the allocated radio resources is permitted.

[0184] In FIG. 22, for example, AP 100 (referred to as "AP") may instruct multiple terminals 200 other than AP 100 (terminals 1 and 3 in FIG. 22) on information regarding TXOP sharing mode as terminal common information.

[0185] For example, the multiple terminals 200 to which TXOP sharing with multiple terminals is applied may be terminals for which P2P is already configured (for example, TDLS is already configured or Direct link is already configured). In the example shown in Fig. 22, a P2P link is already configured (for example, TDLS is already configured) between terminal 1 and terminal 2, and a P2P link is already configured (TDLS is already configured) between terminal 3 and terminal 4. For example, in Fig. 22, the AP 100 may instruct terminal 1 and terminal 3 to share the TXOP with multiple terminals by notifying the terminals of the TXOP sharing mode subfield value = 3 shown in Fig. 11.

[0186] Also, in FIG. 22 , for example, AP 100 may notify each of multiple terminals 200 (e.g., terminal 1 and terminal 3) of destination information (e.g., Destination Mode) that is permitted for transmission and reception using the allocated radio resources, information about the allocation channel (e.g., RU allocation), and information about the allocation period as terminal-specific information.

[0187] For example, in the example shown in Fig. 22 , AP 100 may instruct terminal 3, which has a smaller transmission buffer capacity, to assign a shorter allocation period (Time allocated in MU-RTS TXS TF to STA3 in Fig. 22 ) compared to the allocation period for terminal 1 (Time allocated in MU-RTS TXS TF to STA1 in Fig. 22 ). Therefore, in the example shown in Fig. 22 , the allocation period for terminal 3 is shorter than the allocation period for terminal 1.

[0188] Then, AP 100 may set the allocation band for terminal 3 to the primary channel (20 MHz channel #1) and the allocation band for other terminals 200 to be scheduled (e.g., including terminal 1) to the secondary channel (e.g., including 20 MHz channel #2).

[0189] As a result, after the allocation period for terminal 3 on the primary channel ends, if the result of carrier sense for a predetermined time (for example, PIFS) is Idle, AP 100 can transmit a signal addressed to another terminal on the primary channel, which is an available resource, even if the secondary channel is being used, as shown in Fig. 22. Therefore, according to this embodiment, in TXOP sharing in which allocation periods differ for multiple terminals 200, radio resources can be effectively used after the allocation periods for some terminals 200 have ended, thereby improving resource utilization efficiency and system performance.

[0190] Furthermore, AP 100 may set the data length (PPDU length) to be transmitted after the end of the allocation period on the primary channel to the difference between the maximum allocation period and the minimum allocation period between scheduled terminals 200. In the example of Fig. 22, AP 100 may determine the PPDU length based on the difference between the allocation period for terminal 1 and the allocation period for terminal 3. This allows for effective use of available resources, thereby improving system performance.

[0191] Furthermore, for example, in the remaining TXOP period after the end of the allocation period for all terminals 200, the AP 100 may transmit signals using the entire band of the transmission band of the Trigger frame, including the Secondary 20 MHz channel. This allows for effective use of radio resources in TXOP sharing, in which allocation periods differ for multiple terminals 200, and thus improves system performance.

[0192] For example, as shown in FIG. 23, after the allocation period for terminal 3 ends, AP 100 may transmit a signal addressed to another terminal on the primary channel.

[0193] Thereafter, the AP 100 may transmit signals on the secondary channel in addition to the primary channel during the remaining TXOP period after the allocation period for all terminals 200 (e.g., terminal 1 and terminal 3) ends. At this time, the AP 100 may transmit PPDUs on a secondary channel that does not include the primary channel, as shown in Fig. 23 . Furthermore, the terminal 200 may perform demodulation processing on the secondary channel, for example, regardless of the result of demodulation on the primary channel.

[0194] As shown in Figure 23, even if the primary channel is allocated to another terminal after the allocation period for terminal 3 ends, AP 100 can communicate on a secondary channel that does not include the primary channel after the allocation period for terminal 1 on the secondary channel ends.

[0195] As a result, the AP 100 can transmit signals on the secondary 20 MHz channel during the remaining TXOP period after the end of the allocation period for all terminals 200. Therefore, according to this embodiment, radio resources can be used effectively, and system performance can be improved.

[0196] Also, for example, in Fig. 23, when the terminals 200 performing demodulation processing of the secondary channel are limited to the terminals 200 indicated in the User Info subfield of the MU-RTS TXS Trigger frame, the signal transmitted on the secondary channel may be a signal addressed to terminal 1 or terminal 3. When TXOP Sharing for multiple terminals is indicated, the terminal 200 may perform demodulation processing of the secondary channel in addition to the primary channel during the TXOP period notified in the trigger frame.

[0197] In the examples shown in FIGS. 22 and 23, the case where the number of terminals 200 to which TXOP sharing is applied is two has been described, but the present invention is not limited to this and may be three or more.

[0198] 22 and 23, the PPDU length is determined based on the difference between the maximum allocation period and the minimum allocation period among the allocation periods for terminal 200 to which TXOP sharing is applied, but this is not limiting. For example, the PPDU length may be determined based on the difference between the allocation period for the primary channel and an allocation period longer than the allocation period for the primary channel among the allocation periods for terminal 200 to which TXOP sharing is applied.

[0199] 22 and 23, a case has been described in which the allocation band for a terminal 200 to which the shortest allocation period is set among terminals 200 to which TXOP sharing is applied is set to the primary channel, but this is not limiting. For example, the above-described embodiment may be applied between the primary channel and a secondary channel to which a longer allocation period than the allocation period for the primary channel is set.

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

[0201] (Other Embodiments) (1) In the first and second embodiments, examples of transmission and reception on a secondary channel (for example, a channel that does not include the primary 20 MHz channel) have been described. However, the following setting example may be applied as a method for setting a secondary channel.

[0202] <Configuration Example 1> In configuration example 1, terminal 200 scheduled by the MU-RTS TXS Trigger frame may transmit a P2P link in a band indicated by the Trigger frame during a TXOP sharing period. For example, if the band indicated by the Trigger frame includes a Secondary channel (or does not include a Primary channel), terminal 200 may transmit a P2P link in the band.

[0203] For example, in configuration example 1, the same rules as those for UL MU transmission using existing trigger frames (e.g., Basic Trigger, etc.) may be applied. In this way, in configuration example 1, transmission on the secondary channel can be easily achieved by applying existing rules.

[0204] <Configuration Example 2> In configuration example 2, the terminal 200 to which the AP 100 assigns the secondary channel is a terminal configured for Sub-Channel Selective (SST) mode (for example, referred to as an SST terminal).

[0205] For example, AP 100 may instruct an SST terminal to transmit on the secondary channel set in SST Mode during the TXOP sharing period using an MU-RTS TXS Trigger frame that instructs TXOP Sharing.

[0206] The SST setup is established by, for example, trigger-enabled TWT negotiation, similar to 11ax, and the AP 100 may instruct transmission on the secondary channel during the TWT period using an MU-RTS TXS Trigger frame (for example, extended MU-RTS TXS TF) according to configuration example 2. In this way, in configuration example 2, transmission on the secondary channel can be easily realized by reusing existing functions.

[0207] <Configuration Example 3> In Configuration Example 3, the method for prior notification of the channel to be used for transmission and reception during the TXOP sharing allocation period may be the off-channel configuration mechanism (TDLS Channel Switch Request / Response frame) that negotiates the channel to be used for transmission and reception between a pair of P2P terminals in TDLS. In this way, in Configuration Example 3, transmission on the secondary channel can be easily realized by reusing existing functions.

[0208] Setting examples 1 to 3 have been described above.

[0209] It is also possible to apply a combination of any of the above setting examples 1 to 3. For example, by combining setting example 1 and setting example 2, the terminal 200 that the AP 100 assigns to the secondary channel may be an SST terminal, and the terminal 200 that the AP 100 assigns to the primary channel may be a terminal 200 in which SST mode is not set.

[0210] (2) In the first and second embodiments, TXOP sharing for the terminal 200 in which a TDLS (P2P link) has been set has been described. However, the following operation example may be applied as the operation of TXOP sharing related to TDLS.

[0211] <Operation Example 1> In Operation Example 1, a Non-STR (non-simultaneous transmit and receive) terminal in which TDLS has been set on multiple links does not need to transmit (or respond to) a CTS frame in response to an RTS frame from AP 100 on the other links when TXOP sharing is being performed on one of the multiple links.

[0212] This makes it possible to prevent the transmission timing and reception timing of non-STR terminals from overlapping, even when TXOP sharing is set in multiple P2P links, for example.

[0213] <Operation Example 2> In operation example 2, a TDLS procedure for TXOP sharing may be newly defined.

[0214] In the existing TDLS, the AP 100 may relay request frames and response frames (hereinafter also referred to as request / response frames) between P2P terminals. In this case, since the setting contents in the TDLS are exchanged as encapsulated data, the AP 100 does not need to decode the request / response frames between P2P terminals.

[0215] In the second operational example, in the TDLS for TXOP sharing, the AP 100 may decode and interpret (or identify or understand) the contents of a request / response frame between P2P terminals. For example, the request / response frame for TXOP sharing may include terminal information (e.g., a terminal ID, capability information, etc.) of the destination of the P2P communication.

[0216] This allows the AP 100 to identify information related to the P2P link, and therefore, for example, can avoid instructing TXOP sharing simultaneously to multiple terminals 200 that have overlapping terminal pairs (e.g., communication partners) in the P2P link. For example, if the AP 100 understands, by interpreting the Request / Response frame between P2P terminals, that a P2P link is set between terminal 1 and terminal 2, and that a P2P link is set between terminal 1 and terminal 3, it does not need to instruct TXOP sharing simultaneously to terminals 2 and 3, which are terminal pairs with terminal 1.

[0217] Therefore, overlapping of transmission timing and reception timing of P2P terminals can be prevented in operation example 2. In the case of the above example, overlapping of transmission timing between terminal 2 and terminal 3 can be prevented for terminal 1.

[0218] Furthermore, when an off-channel (e.g., a setting for P2P communication outside the operation band of the AP 100) is implemented in the P2P link configuration, the AP 100 can identify the off-channel by interpreting the request / response frame between P2P terminals. A P2P terminal that implements off-channel communication cannot, for example, perform scheduling in the operation band of the AP 100. Therefore, the AP 100 may exclude terminals 200 that implement off-channel communication from the scheduling targets for TXOP sharing. This can improve the efficiency of TXOP sharing scheduling in the AP 100.

[0219] <Operation Example 3> In operation example 3, a frame (for example, a type of TDLS Action frame) that the terminal 200 notifies or negotiates with the AP 100 may be newly defined.

[0220] In Operation Example 3, for example, a new frame may be defined instead of reusing an existing Request / Response frame as in the above-described Operation Example 2. This allows the information exchange shown in Operation Example 2 to be carried out more efficiently.

[0221] Operation examples 1 to 3 have been described above.

[0222] It should be noted that any of the above operation examples 1 to 3 may be applied in combination. For example, by combining operation example 2 and operation example 3, a procedure may be adopted in which part of the information related to the TDLS used for TXOP sharing is notified to the AP 100 by an existing TDLS frame, and other information is notified to the AP 100 by a newly defined frame.

[0223] (3) In each of the above embodiments, Capability information indicating whether the terminal 200 supports each mode of the TXOP sharing mode may be defined and notified from the terminal 200 to the AP 100 .

[0224] For example, when TXOP Sharing Mode 3 described in each of the above embodiments is set, as shown in FIG. 24 , a subfield indicating whether or not the terminal 200 supports TXOP Sharing Mode 3 (e.g., Triggered TXOP Sharing Mode 3 Support subfield) may be set (e.g., added) to a field that notifies capability information (e.g., EHT MAC Capabilities Information field).

[0225] For example, the Triggered TXOP Sharing Mode 3 Support subfield may be defined using some of the reserved bits (B9 in the example shown in FIG. 24) in the existing EHT MAC Capabilities Information field.

[0226] This allows the AP 100 to instruct TXOP Sharing in accordance with (for example, in a limited manner) the TXOP sharing mode supported by the terminal 200 .

[0227] (4) In each of the above embodiments, when signals of multiple terminals 200 are frequency-division multiplexed (FDM), the AP 100 may notify each terminal 200 (for example, the terminal 200 to be scheduled and the P2P terminal to which the terminal 200 is to be sent may be included) of the maximum transmit power that each terminal 200 can transmit during the allocation period by including the maximum transmit power in the terminal-specific information (for example, the User Info field) of the Trigger frame. By notifying the maximum transmit power, adjacent channel interference in frequency multiplexing can be suppressed.

[0228] For example, as shown in FIG. 25, the maximum transmission power (Maximum Transmit Power subfield in FIG. 25) may be indicated using a part of the reserved area of ​​the User Info field (for example, FIG. 12) in each of the above embodiments.

[0229] For example, the AP 100 may determine the maximum transmission power of each terminal 200 based on path loss or received power information between the AP and the P2P terminal that is fed back in advance from the terminal 200 .

[0230] (5) In the above-described embodiments, the case where an AP notifies multiple terminals of TXOP sharing has been described. However, the device that notifies TXOP sharing is not limited to an STA.

[0231] For example, the method of notifying TXOP sharing from an AP to multiple terminals described in embodiments 1 and 2 may also be applied to a method of notifying allocation of radio resources (time resources and frequency resources) from a Sharing AP to a Shared AP in Multi-AP Coordination transmission.

[0232] Multi-AP cooperative communication includes, for example, "Coordinated-Frequency Division Multiple Access (FDMA)," in which different frequency resources are allocated among multiple APs, and "Coordinated-Time Division Multiple Access (TDMA)," in which different time resources are allocated among multiple APs. In these multi-AP cooperative communications, the notification method using the MU-RTS TXS Trigger frame described above may be used to allocate radio resources from the Sharing AP to the Shared AP.

[0233] For example, the above-mentioned TXOP sharing (radio resource allocation) from an AP to multiple terminals may be interpreted as radio resource allocation (including TXOP sharing) from a Shared AP to multiple Sharing APs in multi-AP cooperative communication.

[0234] In addition, the above-mentioned TXOP sharing (radio resource allocation) from an AP to multiple P2P terminals may also be interpreted as radio resource allocation (including TXOP sharing) from a Shared AP in multi-AP cooperative communication to pairs of multiple Sharing APs and terminals under the Sharing APs.

[0235] Furthermore, when using an MU-RTS TXS Trigger frame in multi-AP cooperative communication, the TXOP sharing mode for multi-AP cooperative communication may be explicitly notified. For example, the TXOP sharing mode for multi-AP cooperative communication may be notified in a reserved area for TXOP Sharing Mode in the Common Info field shown in Fig. 2. Alternatively, a subfield for notifying the TXOP sharing mode for multi-AP cooperative communication may be provided in part of the subfields of the Common Info field (e.g., part of the subfields not used for transmitting CTS frames).

[0236] (6) In the sequence diagrams shown in the above-described embodiments, a case where a CTS frame is responded to an MU-RTS TXS Trigger frame has been described as an example, but an embodiment of the present disclosure is not limited to this. For example, the AP 100 may use a Trigger frame to instruct the terminal 200 whether or not to respond with a CTS frame. This allows the terminal 200 to omit the CTS frame response in an environment where hidden terminals are expected to occur less frequently, thereby improving throughput performance.

[0237] (7) In each of the above-described embodiments, the fields in which the control information including the TXOP Sharing Mode, Destination Mode, or Maximum Transmit Power is placed are not limited to the above-described fields and may be placed in other fields. Furthermore, the number of bits for notifying the control information including the TXOP Sharing Mode, Destination Mode, or Maximum Transmit Power is not limited to the above-described examples and may be other numbers of bits.

[0238] Furthermore, in each of the above-described embodiments, the field that indicates the allocation period of TXOP sharing is not limited to the UL Length subfield, and may be another subfield.

[0239] Furthermore, in each of the above-mentioned embodiments, the configuration of the Trigger frame and the configuration of the Common Info field and User Info field within the Trigger frame are not limited to the above-mentioned examples, and may be other configurations in which, for example, at least one of other subfields is added and some subfields are deleted in each of the above-mentioned fields.

[0240] Furthermore, for example, the signals of multiple terminals 200 allocated in TXOP sharing may be multiplexed in at least one of frequency resources and time resources that are different during the allocation period.

[0241] Furthermore, in each of the above-described embodiments, as an example, a case has been described in which an MU-RTS TXS Trigger frame is used to notify multiple terminals of a Sharing AP, but the Trigger type for notifying multiple terminals of a Sharing AP is not limited to MU-RTS, and may be another Trigger type, or may be a Trigger type newly defined in a future version.

[0242] Furthermore, the other terminal notified by the terminal 200 in P2P communication may be a terminal under the control of the AP 100 to which the terminal 200 is connected, or may be a terminal under an AP different from the AP 100 to which the terminal 200 is connected.

[0243] 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. For example, an embodiment of the present disclosure may be applied to IEEE 802.11bd (NGV (Next Generation V2X)), which is the next-generation standard of IEEE 802.11p, an in-vehicle standard.

[0244] (Additional Information) Information indicating whether terminal 200 supports the functions, operations, or processes described in each of the above-described embodiments may be transmitted (or notified) from terminal 200 to AP 100, for example, as capability information or capability parameters of terminal 200.

[0245] The capability information may include an information element (IE) that individually indicates whether the terminal 200 supports at least one of the functions, operations, or processes described in the above-described embodiments. Alternatively, the capability information may include an information element that indicates whether the terminal 200 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments. An information element may also be simply referred to as an element.

[0246] For example, based on the capability information received from the terminal 200, the AP 100 may determine (or decide or assume) the functions, operations, or processes that the terminal 200 that sent the capability information supports (or does not support). The AP 100 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the AP 100 may control TXOP sharing to multiple STAs based on the capability information received from the terminal 200.

[0247] Note that the fact that the terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments may be interpreted as meaning that such some of the functions, operations, or processes are restricted in the terminal 200. For example, information or a request regarding such restrictions may be notified to the AP 100.

[0248] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or may be implicitly notified to AP 100 in association with information known at AP 100 or information sent to AP 100.

[0249] The present disclosure can be realized by software, hardware, or software in conjunction with 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 also be called an IC, system LSI, super LSI, or ultra LSI.

[0250] The integrated circuit method is not limited to LSI, and 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.

[0251] 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 may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0252] 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 radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio 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.

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

[0254] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

[0255] 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.

[0256] 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.

[0257] An access point according to one embodiment of the present disclosure includes a control circuit that generates a control signal instructing uplink transmissions of multiple terminals, the control signal including information regarding the destination of the uplink transmission for each of the multiple terminals, and a transmission circuit that transmits the control signal.

[0258] In one embodiment of the present disclosure, the radio resources allocated to the uplink transmission are at least a portion of the time of the transmission opportunity acquired by the access point and at least a portion of the band to which the control signal is allocated.

[0259] In one embodiment of the present disclosure, the information about the transmission destination indicates whether or not the uplink transmission to the access point is permitted.

[0260] In one embodiment of the present disclosure, the information regarding the destination indicates either permission for communication with another terminal different from the plurality of terminals or the access point, or permission for communication with the other terminal.

[0261] In one embodiment of the present disclosure, the plurality of terminals are terminals for which terminal-to-terminal communication is set up.

[0262] In one embodiment of the present disclosure, the radio communication device further comprises a receiving circuit that receives a response signal to the control signal in a band designated by the control signal.

[0263] In one embodiment of the present disclosure, the information about the destination indicates the destination for each of a plurality of portions into which the part of time is divided.

[0264] In one embodiment of the present disclosure, during the part of the time, the allocation time for a terminal allocated to the primary channel among the plurality of terminals is shorter than the allocation time for a terminal allocated to the secondary channel.

[0265] In one embodiment of the present disclosure, during the transmission opportunity time, the access point and the plurality of terminals are permitted to communicate in a band that does not include a primary channel.

[0266] In one embodiment of the present disclosure, during the part of the time, the access point and the plurality of terminals are permitted to communicate in a band that does not include a primary channel.

[0267] In one embodiment of the present disclosure, the terminal to which the band not including the primary channel is instructed is a terminal in which Sub-Channel Selective (SST) Mode is set.

[0268] A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives a control signal instructing upstream transmissions of multiple terminals, the control signal including information regarding the destination of the upstream transmissions for each of the multiple terminals, and a control circuit that controls the upstream transmissions based on the control signal.

[0269] In a communication method according to one embodiment of the present disclosure, an access point generates a control signal instructing allocation of uplink transmissions to multiple terminals, the control signal including information regarding the destination of the uplink transmission for each of the multiple terminals, and transmits the control signal.

[0270] In a communication method according to one embodiment of the present disclosure, a terminal receives a control signal instructing allocation of uplink transmissions for multiple terminals, the control signal including information regarding the destination of the uplink transmission for each of the multiple terminals, and controls the uplink transmission based on the control signal.

[0271] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2022-084544, filed on May 24, 2022, are incorporated herein by reference in their entirety.

[0272] One embodiment of the present disclosure is useful in wireless communication systems.

[0273] 100 AP 101, 206 Scheduling unit 102 Common Info generation unit 103 User Info generation unit 104 Trigger frame generation unit 105, 208 Error correction coding unit 106, 209 Modulation unit 107, 201 Radio transmission / reception unit 108, 202 Demodulation unit 109, 203 Error correction decoding unit 110 Terminal information holding unit 200 Terminal 204 Common Info acquisition unit 205 User Info acquisition unit 207 Data generation unit

Claims

1. A control circuit that generates a control signal including first information indicating whether or not to transmit to a first communication device; a transmitting circuit for transmitting the control signal to a second communication device; A first communication device comprising:

2. The control signal includes second information regarding time resources of a TXOP (Transmission Opportunity). The first communication device according to claim 1 .

3. The control signal includes second information regarding time resources of a TXOP (Transmission Opportunity), data is transmitted from the second communication device to a third communication device based on the second information; The first communication device according to claim 1 .

4. The transmission to the first communication device is a response signal to the control signal. The first communication device according to claim 1 .

5. The control signal is used for Coordinated-TDMA (Time Division Multiple Access), The first communication device according to claim 1 .

6. The control signal is transmitted in a User Info field of a trigger frame. The first communication device according to claim 1 .

7. Further comprising a receiver for receiving a transmission to the first communication device. The first communication device according to claim 1 .

8. The control signal is transmitted separately from capability information indicating whether or not an operation related to transmission to the first communication device is supported. The first communication device according to claim 1 .

9. The first communication device generating a control signal including first information indicating whether or not to transmit to the first communication device; transmitting the control signal to a second communication device; Communication method.

10. The control signal includes second information regarding a time resource of a TXOP (Transmission Opportunity). The communication method according to claim 9.

11. The control signal includes second information regarding time resources of a TXOP (Transmission Opportunity), data is transmitted from the second communication device to a third communication device based on the second information; The communication method according to claim 9.

12. The transmission to the first communication device is a response signal to the control signal. The communication method according to claim 9.

13. The control signal is used for Coordinated-TDMA (Time Division Multiple Access). The communication method according to claim 9.

14. The control signal is transmitted in a User Info field of a trigger frame. The communication method according to claim 9.

15. Receiving a transmission to the first communication device. The communication method according to claim 9.

16. The control signal is transmitted separately from capability information indicating whether or not an operation related to transmission to the first communication device is supported. The communication method according to claim 9.

17. An integrated circuit for use in a first communication device, comprising: a generation circuit that controls generation of a control signal including first information indicating whether or not to perform transmission to the first communication device; a transmitting circuit for controlling transmission of the control signal to the second communication device; An integrated circuit comprising: