Terminals and communication methods

Abstract

To improve the communication efficiency of cooperative communication in wireless communication. [Solution] The terminal is a terminal associated with a first access point and comprises a receiving circuit that receives signals, a control circuit that sets information regarding a transmission prohibition period based on the information contained in the received signals and controls transmission based on the information regarding the transmission prohibition period, and a transmitting circuit that transmits signals to the first access point. When the terminal receives a signal transmitted from the first access point or a second access point and sets information regarding a transmission prohibition period based on the received signals, the control circuit permits transmission to the transmitting circuit regardless of the setting status of the information regarding the transmission prohibition period when the second access point is communicating with the first access point, and prohibits transmission to the transmitting circuit according to the setting status of the information regarding the transmission prohibition period when the second access point is not communicating with the first access point.

Description

Technical Field

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

Background Art

[0002] As a successor standard to 802.11ax (hereinafter referred to as "11ax"), which is a standard of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, the technical specification of 802.11be (hereinafter referred to as "11be") is being developed in a task group (TG: Task Group).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

Summary of the Invention

[0004] However, there is room for study on a method for controlling cooperative communication in wireless communication.

[0005] Non-limiting embodiments of this disclosure contribute to providing communication devices and communication methods that improve the communication efficiency of cooperative communication in wireless communication.

[0006] A communication device according to one embodiment of the present disclosure comprises a receiving circuit for receiving a signal and a control circuit for setting different transmission prohibition periods depending on whether the source of the signal belongs to a group relating to cooperative communication common to the communication device. It is equipped with.

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

[0008] According to one embodiment of the present disclosure, the communication efficiency of cooperative communication in wireless communication can be improved.

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

[0010] [Figure 1] This diagram shows an example of Multi-Access Point (MAP) Coordination control. [Figure 2] A diagram illustrating an example of negotiation between Access Points (APs). [Figure 3] A diagram showing an example of an AP candidate set and a Virtual Basic Service Set (BSS). [Figure 4] A diagram showing an example of a Network Allocation Vector (NAV). [Figure 5] Figure showing an example of NAV control in MAP coordination [Figure 6] Figure showing an example of NAV control in MAP coordination [Figure 7] Figure showing an example of NAV control in MAP coordination [Figure 8] Figure showing an example of NAV control in MAP coordination [Figure 9] Figure showing an example of BSS arrangement in MAP coordination [Figure 10] Sequence diagram showing an example of the operations of an AP and a Station (STA) [Figure 11] Block diagram showing an example of the configuration of a part of an AP and a STA [Figure 12] Block diagram showing an example of the configuration of an AP [Figure 13] Block diagram showing an example of the configuration of a STA [Figure 14] Figure showing an example of a MAP coordination operation element [Figure 15] Figure showing an example of the assignment of identifiers related to a coordination group [Figure 16] Figure showing an example of the notification of a coordination group based on user information [Figure 17] Figure showing an example of a MAP coordination information element [Figure 18] Figure showing an example of NAV control in MAP coordination according to Method 1 [Figure 19] Figure showing an example of NAV control in MAP coordination according to Method 1 [Figure 20] Figure showing an example of NAV control in MAP coordination according to Method 2 [Figure 21] Figure showing an example of NAV control in MAP coordination according to Method 2 [Figure 22]Figure showing an example of the User Info field of the Trigger frame according to Method 2-1 [Figure 23] Figure showing an example of the operation of MAP coordination using multiple Transmission Opportunities (TXOPs) [Figure 24] Figure showing an example of the operation of Sequential sounding in MAP coordination [Figure 25] Figure showing an example of the operation of Joint sounding in MAP coordination [Figure 26] Figure showing an example of MAP sounding [Figure 27] Figure showing an example of MAP sounding [Figure 28] Figure showing an example of the Trigger frame format including multiple user informations [Figure 29] Figure showing an example of the control of NAV based on the transmission order of user information [Figure 30] Figure showing an example of the control of NAV based on the common information of the Trigger frame [Figure 31] Figure showing an example of the User Info field of the Trigger frame [Figure 32] Figure showing an example of the control of NAV based on user information [Figure 33] Figure showing an example of the User field of the Extremely High Throughput (EHT)-SIG [Figure 34] Figure showing an example of the STA Info field of the Null Data Packet Announcement (NDPA) [Figure 35] Figure showing an example of the Universal SIG (U-SIG) [Figure 36] Figure showing an example of the operation of Triggered TXOP Sharing with TXOP Sharing Mode = 1 [Figure 37]This diagram shows an example of Triggered TXOP Sharing operation with TXOP Sharing Mode=2. [Modes for carrying out the invention]

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

[0012] [About Multi-AP (MAP) coordination] In 11be, Multi-AP (MAP) coordination (also known as "cooperative communication") is being considered, in which multiple access points (also called "base stations," hereafter referred to as "APs (Access Points)") cooperate to transmit and receive data (see, for example, Non-Patent Document 1).

[0013] In MAP coordination, for example, an AP that has obtained a Transmission Opportunity (TXOP) is called a "Sharing AP". An AP may obtain a TXOP, for example, through Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA).

[0014] Furthermore, in MAP coordination, for example, an AP that is coordinately controlled by a Sharing AP is called a "Shared AP".

[0015] Furthermore, in MAP coordination, for example, terminals belonging to (or associated with) a Sharing AP (also called stations (STA) or non-AP STA) may be called "Sharing STA," and STAs belonging to a Shared AP may be called "Shared STA."

[0016] Figure 1 shows an example of a method for controlling MAP coordination. In Figure 1, for example, it is assumed that the MAP coordination process is divided into three stages: the "Tx indication and request" phase, the "Schedule allocation" phase, and the "Data Tx" phase.

[0017] Figure 2 shows an example of negotiation between APs (e.g., Sharing APs and Shared APs) in MAP coordination (e.g., the Tx indication and request phase and the Schedule allocation phase). In the example in Figure 2, AP1 can be a Sharing AP, and AP2 and AP3 can be Shared APs.

[0018] As shown in Figure 2, in the first stage, the Tx indication and request phase, the Sharing AP (AP1) sends a Coordinated AP TXOP Indication (CTI) frame to the Shared APs (AP2 and AP3) and requests a response regarding whether or not they can participate in MAP coordination. In response to the CTI from AP1, the Shared APs (AP2 and AP3) send a Coordinated AP TXOP Request (CTR) frame to the Sharing AP (AP1) and respond regarding whether or not they can participate in MAP coordination.

[0019] Furthermore, as shown in Figure 2, in the second stage, the Schedule allocation phase, the Sharing AP (AP1) sends a Coordinated AP TXOP AP Schedule frame (CTAS) frame to the Shared APs (AP2 and AP3), notifying each Shared AP of available resource information (e.g., frequency resources and time resources) and allocation information such as the transmission start time. Next, the Sharing AP (AP1) and Shared APs (AP2 and AP3) send, for example, a Coordinated AP TXOP Local Schedule (CTLS) frame, notifying the terminals under each AP of available resource information and allocation information such as the transmission start time.

[0020] Then, as shown in Figure 1, in the third stage Data Tx (for example, the Data Tx phase), the AP and STA perform coordinated transmission based on the allocation information. For example, coordinated transmission in the Data TX phase may include Joint Transmission (JT), Corrdinated Beamforming (CBF), Coordinated Spatial Reuse (CSR), Coordinated Orthogonal Frequency Division Multiple Access (COFDMA), or Coordinated Time Division Multiple Access (CTDMA). Furthermore, the coordinated transmission may be either downlink coordinated transmission or uplink coordinated transmission.

[0021] Note that the control method for MAP coordination shown in Figures 1 and 2 is just one example and is not limited to the method shown in Figures 1 and 2.

[0022] [About collaborative groups] Furthermore, examples of groups that perform MAP coordination (also called, for example, "coordination groups") include "AP candidate sets" and "Virtual Basic Service Sets (Virtual BSS)" (see, for example, Non-Patent Documents 2 and 3).

[0023] Figure 3 shows an example of an AP candidate set and a Virtual BSS.

[0024] As shown in Figure 3, the AP candidate set may be a group consisting of multiple APs (for example, AP1, AP2, AP3, and AP4). For example, a Sharing AP and a Shared AP that perform MAP coordination may be selected from the APs included in the AP candidate set.

[0025] Furthermore, as shown in Figure 3, a Virtual BSS may be a group composed of multiple Basic Service Sets (BSS) (e.g., BSS1 and BSS2) for performing MAP coordination. APs participating in a Virtual BSS may, for example, have a common Service Set identifier (SSID). Also, APs included in a Virtual BSS may, for example, share information about the STAs belonging to each BSS (e.g., the Association identifier (AID) of the STAs).

[0026] [Regarding the transmission restriction period (NAV: Network Allocation Vector)] An AP or STA (hereinafter sometimes referred to as "terminal" or, for convenience, "AP / STA") that has obtained a TXOP may include information about the transmission blackout period (Network Alocation Vector (NAV)) in the transmission signal and notify other APs / STAs. By notifying of the NAV, other APs / STAs will suppress channel access for a certain period of time through virtual carrier sense (for example, virtually considering the carrier sense state as busy). The NAV period may be notified, for example, in the Duration / ID subfield of the Medium Access Control (MAC) header or in the TXOP subfield of the SIG field of the preamble.

[0027] AP / STA updates a counter (e.g., NAV counter) based on the duration of the notified NAV, deducts the NAV counter according to the elapsed time, and recognizes that the virtual carrier sense state is idle if the NAV counter is 0.

[0028] In 11ax, for example, two types of NAV are used: "intra-BSS NAV" and "Basic NAV" (see, for example, Non-Patent Document 4).

[0029] Figure 4 shows examples of intra-BSS NAV and Basic NAV.

[0030] In the example in Figure 4, AP1, STA1, and STA2 belong to BSS1, and STA3 belongs to BSS2. Also in the example in Figure 4, AP1 acquires a TXOP and sends a transmission signal (e.g., Request-To-Send (RTS)) to STA1, and STA1 sends a response signal to the RTS (e.g., Clear-To-Send (CTS)) to AP1. Then AP1 sends transmission data (Tx Data) to STA1, and STA1 sends a response signal (Acknowledge (Ack)) to AP1 for the transmission data.

[0031] As shown in Figure 4, when a signal addressed to STA1 or a signal addressed to AP1 is transmitted or received, STA2 and STA3 may perform NAV-related control (e.g., setting, updating, etc.) based on the information contained in the signal addressed to STA1 or AP1 (e.g., information about TXOP).

[0032] For example, as shown in Figure 4, when NAV is notified by a signal transmitted from an AP / STA belonging to the BSS to which the STA belongs (hereinafter referred to as the "common BSS"; BSS1 in Figure 4), the Intra-BSS NAV is updated.

[0033] Furthermore, as shown in Figure 4, if the NAV is notified by a signal transmitted from an AP / STA belonging to a different BSS (hereinafter referred to as "Overlapped BSS (OBSS)") than the BSS to which the STA belongs (for example, BSS2), the Basic NAV is updated.

[0034] The Intra-BSS NAV and Basic NAV may each be managed by separate NAV counters, for example. For instance, an AP / STA supporting 11ax would recognize the virtual carrier sense state as idle if both the Intra-BSS NAV and Basic NAV counters are zero.

[0035] The control methods for NAV in MAP coordination have not been sufficiently studied. For example, in the NAV control method in 11ax, coordinated transmission in MAP coordination may be hindered by the NAV. For this reason, NAV control methods in MAP coordination are being investigated (see, for example, Non-Patent Document 5).

[0036] Figure 5 shows an example of a NAV control method in MAP coordination. In the example shown in Figure 5, AP1 (Sharing AP) and STA1 belong to BSS1, and AP2 (Shared AP) and STA2 belong to BSS2.

[0037] In the example shown in Figure 5, AP1 sends a MAP coordination participation request signal (CTI) to AP2. Here, AP1 may use the CTI to AP2 to notify surrounding APs / STAs of the TXOP period. In Figure 5, STA2, which belongs to a different BSS (BSS2) than AP1, updates its Basic NAV based on the CTI sent from AP1 to AP2. STA2 may, for example, set the NAV period based on the TXOP acquired by AP1. As shown in Figure 5, even if AP2 sends a trigger frame (TF) to STA2 instructing it to transmit an uplink signal (UL transmission) in order for STA2 to update its Basic NAV, STA2 cancels the UL transmission due to the Basic NAV. Thus, NAV control may prevent coordinated communication via MAP coordination.

[0038] The discussion is about how to resolve the issue of coordinated communication not occurring due to NAV control.

[0039] Figure 6 shows an example of the NAV control method, which is the first solution.

[0040] As shown in Figure 6, the TXOP acquired by the Sharing AP (e.g., AP1) is updated in multiple parts. For example, in Figure 6, the period of the first TXOP (TXOP1) notified by the CTI transmitted by AP1 may be set before each STA (e.g., STA1 and STA2) transmits a UL. The period of the second TXOP (TXOP2) notified by the Trigger frame transmitted by each AP (e.g., AP1 and AP2) may be set, for example, until each AP (e.g., AP1 and AP2) finishes transmitting a response (e.g., Ack) signal to each STA (e.g., STA1 and STA2)'s UL transmission.

[0041] In Figure 6, for example, when STA2 receives a CTI from AP1 to AP2, it updates the Basic NAV based on the TXOP1 included in the received CTI. Therefore, as shown in Figure 6, the NAV set on STA2 can be cleared before STA2's UL transmission (for example, the NAV counter becomes zero). Also, as shown in Figure 6, since the Trigger frame that notifies the duration of TXOP2 is a signal addressed to STA2, STA2 does not update the NAV even if it receives the Trigger frame. Therefore, in Figure 6, STA2 is able to perform UL transmission (for example, cooperative communication).

[0042] Note that the method shown in Figure 6 does not limit the number of TXOPs to two; it may be three or more.

[0043] Figure 7 shows an example of the second solution, the NAV control method.

[0044] As shown in Figure 7, when STA2 receives a MAP coordination participation request signal (CTI) sent from AP1 to AP2, it updates the Basic NAV based on the TXOP included in the received CTI. In Figure 7, for example, a Shared STA (STA2) belonging to a Shared AP (AP2) may temporarily ignore the Basic NAV when it receives a Trigger frame sent from the Shared AP. As a result, as shown in Figure 7, STA2 can perform UL transmission (e.g., coordinated communication) even when the NAV counter of the Basic NAV is non-zero.

[0045] The above describes an example of a NAV control method in MAP coordination.

[0046] For example, even with the NAV control method shown in Figures 6 and 7, there is a possibility that AP / STA may not be able to transmit signals during MAP coordination.

[0047] For example, Figure 8 shows an example of cooperative communication using CTDMA. As shown in Figure 8, in cooperative communication using CTDMA, AP1 and AP2 may control UL transmission to STA1 and STA2 using different time resources. Also, in Figure 8, similar to Figure 6, the TXOP acquired by AP1 (Sharing AP) may be divided into multiple TXOPs (e.g., TXOP1, TXOP2, and TXOP3) based on the timing of UL transmission by each STA.

[0048] For example, as shown in Figure 8, when STA2 receives a MAP coordination participation request signal (CTI) sent from AP1 to AP2, it updates the Basic NAV based on TXOP1 included in the received CTI. Also, as shown in Figure 8, when AP2 and STA2 receive a Trigger frame sent from AP1 to STA1, they update the Basic NAV based on TXOP2 included in the received Trigger frame.

[0049] As shown in Figure 8, AP2 updates the Basic NAV based on the Trigger frame sent by AP1 to STA1, and therefore cancels the transmission of a Trigger frame to STA2. In this way, coordinated transmission in MAP coordination can be hindered by the NAV.

[0050] Furthermore, for example, in the NAV control method, which is the second solution described above, a Shared STA may ignore the configured Basic NAV and perform a UL transmission when triggered by a Shared AP to which the STA belongs. Here, for example, if a Shared AP that does not participate in coordinated transmission fails to receive a signal from a Sharing AP (for example, a signal containing information about TXOP), there may be a case where the Shared STA updates the Basic NAV while the Shared AP does not. In this case, if the Shared AP that does not participate in coordinated transmission sends a Trigger frame, the Shared STA can ignore the configured Basic NAV and perform a UL transmission. Therefore, in this case, for example, a conflict may occur between the UL transmission of the Shared STA that does not participate in coordinated transmission and the coordinated transmission. Thus, a rule that ignores the configured NAV can cause a conflict.

[0051] In one non-limiting embodiment of this disclosure, a method is described for suppressing interference with AP / STA transmission and reception due to NAV control in MAP coordination and for improving the communication efficiency of cooperative communication in MAP coordination.

[0052] In a non-limiting embodiment of the present disclosure, the AP / STA may determine control regarding the NAV based, for example, on the source information of the received signal. According to a non-limiting embodiment of the present disclosure, by switching the control method regarding the NAV based on the coordinating group performing MAP coordination, coordinated transmission can be properly performed in MAP coordination without being hindered by the NAV.

[0053] [Configuration of the wireless communication system] A wireless communication system according to one embodiment of the present disclosure includes at least one coordinating group that performs MAP coordination. The coordinating group includes, for example, a plurality of AP100s and at least It includes one STA200. For example, in Downlink (DL) communication, AP100 corresponds to a "downlink radio transmitter" and STA200 corresponds to a "downlink radio receiver". Also, in Uplink (UL) communication, AP100 corresponds to an "uplink radio receiver" and STA200 corresponds to an "uplink radio transmitter". For example, AP100 transmits DL signals to other AP100s or STA200s. Also, for example, STA200 transmits UL signals based on signals received from AP100.

[0054] In the following example, multiple AP100s and multiple STA200s perform MAP coordination. For example, as shown in Figure 9, two AP100s (AP1 and AP2) send and receive control signals related to MAP coordination between APs, AP1 and AP2 send trigger frames to STA1 and STA2 via CTDMA, and STA1 and STA2 send UL signals.

[0055] As shown in Figure 9, AP1 and STA1 may belong to BSS1, and AP2 and STA2 may belong to BSS2. Also, as shown in Figure 9, it is assumed that BSS1 and BSS2 overlap at least partially.

[0056] Figure 10 is a sequence diagram showing an example of operation related to MAP coordination by AP100 and STA200 of a wireless communication system according to one embodiment of the present disclosure.

[0057] In the example shown in Figure 10, AP1 acquires TXOP and acts as a Sharing AP, leading MAP coordination.

[0058] AP1 sends a request to AP2 to participate in MAP coordination (e.g., CTI) (S101).

[0059] AP2 performs, for example, reception processing of a Multi-AP coordination participation request signal (S102). For example, AP2 may decide whether or not to participate in MAP coordination based on capability information regarding MAP coordination.

[0060] Furthermore, STA1 and STA2, whose destinations differ from those of the MAP coordination participation request signal transmitted from AP1 (e.g., AP2), may perform control processing related to NAV (e.g., updating the NAV counter, or selecting the type of NAV counter to update) (S103-1, S103-2). For example, STA1 and STA2 may decide on NAV control based on information regarding the duration of NAV notified by the MAP coordination participation request signal, and whether or not AP1, the source of the MAP coordination participation request signal, belongs to a common BSS. Thereafter, if STA1 and STA2 receive a signal with a different destination than their respective STA (e.g., if the AID of STA1 and STA2 is not included in the destination information of the received signal), they may perform NAV control processing similar to that in S103-1 and S103-2 (e.g., S106-1, S106-2, S109-1 and S109-2).

[0061] AP2 sends MAP coordination participation response information (e.g., CTR) to AP1, including whether or not it can participate in MAP coordination (S104).

[0062] AP1 processes the reception of the Multi-AP coordination participation response information signal (S105). For example, AP1 may determine the MAP coordination method (e.g., JT, CBF, CSR, COFDMA, or CTDMA) and schedule based on information about APs participating in MAP coordination (e.g., Shared APs). Then, AP1 sends the MAP coordination scheduling information to the Shared APs (e.g., including AP2) (S107). AP2 processes the reception of the MAP coordination scheduling information from AP1 (S108).

[0063] MAP coordination scheduling information may include, for example, information about coordinating AP100s (e.g., AP100's SSID or STA200's AID), resource information available to each AP100 (e.g., frequency resource information or time resource information), information about amplitude or phase weighting in coordinated transmission (also called steering, spatial mapping, or transmit precoding), or transmit power information.

[0064] AP1 and AP2, for example, send MAP Coordination local scheduling information (e.g., CTLS) to the STAs under each AP (S110-1 and S110-2).

[0065] The Multi-AP coordination local scheduling information may include, for example, resource information for STA200 to receive DL MAP coordination signals (e.g., frequency resource information or reception timing information), or resource information for STA200 to transmit UL MAP coordination signals (e.g., frequency resource information, transmission timing information, or transmission power information). Each AP100 and STA200 performs coordinated transmission based on Multi-AP coordination scheduling information and Multi-AP coordination local scheduling information. In the example shown in Figure 10, an example of coordinated transmission is shown in which STA200 transmits a UL signal in CTDMA. Note that the coordinated transmission method is not limited to CTDMA and other methods may be used.

[0066] For example, AP1 sends a Trigger frame to STA1 within the time resource notified by the MAP coordination scheduling information (S111-1). STA1 processes the received Trigger frame (S112-1) and sends a UL signal to AP1 based on the control information contained in the Trigger frame (S113-1). AP1 processes the received UL signal (S114-1) and sends a response signal (Ack) to STA1 based on the error detection result, for example (S115-1).

[0067] In the case of CTDMA, AP2 and STA2 may then perform the same transmission and reception processing as AP1 and STA1 (S111-2 to S115-2).

[0068] The above describes examples of MAP coordination operations using AP100 and STA200.

[0069] Figure 11 is a block diagram showing some configuration examples of AP100 or STA200 according to one embodiment of the present disclosure. In the AP100 or STA200 shown in Figure 11 (for example, corresponding to a communication device), the receiving unit (for example, corresponding to a receiving circuit) receives a signal. The control unit (for example, corresponding to a control circuit) sets different settings regarding the transmission blackout period (NAV) depending on whether the signal source belongs to a common cooperative communication group (common cooperative group) with the communication device (for example, AP100 or STA200).

[0070] [Example configuration of AP100] Figure 12 is a block diagram showing an example configuration of AP100 (for example, a downlink wireless transmitter or an uplink wireless receiver). The AP100 shown in Figure 12 may include, for example, a wireless receiver 101, a preamble demodulation unit 102, a data demodulation unit 103, a data decoding unit 104, a NAV control unit 105, a scheduling unit 106, a data generation unit 107, a data encoding unit 108, a data modulation unit 109, a preamble generation unit 110, and a wireless transmitter 111.

[0071] For example, at least one of the preamble demodulation unit 102, data demodulation unit 103, data decoding unit 104, NAV control unit 105, scheduling unit 106, data generation unit 107, data encoding unit 108, data modulation unit 109, and preamble generation unit 110 may be included in the control unit shown in Figure 11, and the wireless receiving unit 101 may be included in the transmitting unit shown in Figure 11.

[0072] The wireless receiver 101 receives signals transmitted from other AP100s (e.g., downlink wireless transmitters) or STA200s (e.g., downlink wireless receivers) via an antenna and performs wireless reception processing on the received signals, such as downconversion and analog-to-digital (A / D) conversion. For example, the wireless receiver 101 divides the received signal after wireless reception processing into a preamble section (also called a preamble signal) and a data section (also called a data signal), outputs the preamble signal to the preamble demodulation section 102, and outputs the data signal to the data demodulation section 103.

[0073] The preamble demodulation unit 102 may, for example, perform demodulation processing such as a Fourier transform (e.g., Fast Fourier Transform (FFT)) on the preamble signal input from the wireless receiver unit 101 to extract control signals contained in the preamble signal. The control signals may include, for example, reception control information used for demodulation and decoding of the data signal, such as frequency bandwidth (BW), Modulation and Coding Scheme (MCS), or error correction code.

[0074] Furthermore, the preamble demodulation unit 102 performs channel estimation based on a reference signal included in the preamble signal, for example, and derives the estimated channel value. The preamble demodulation unit 102 outputs reception control information to the data demodulation unit 103 and the data decoding unit 104, for example, and outputs the estimated channel value to the data demodulation unit 103.

[0075] Furthermore, if the preamble demodulation unit 102 includes, for example, destination information (e.g., STA-ID of user information included in the SIG field) or TXOP information in the preamble signal, it outputs this information to the NAV control unit 105.

[0076] The data demodulation unit 103 performs a Fourier transform (e.g., FFT) on the data signal input from the wireless receiver unit 101, and demodulates the data signal after the FFT based on the reception control information and channel estimate input from the preamble demodulation unit 102. The data demodulation unit 103 outputs the demodulated data signal to the data decoding unit 104.

[0077] The data decoding unit 104 decodes the demodulated data signal input from the data demodulation unit 103 based on, for example, the reception control information input from the preamble demodulation unit 102. For example, the data decoding unit 104 may perform error detection on the decoded data signal, such as a Cyclic Redundancy Check (CRC). If, for example, the decoded data signal is free of errors (in other words, decoding errors), the data decoding unit 104 outputs the MAC header and destination information (for example, the AID of the user information included in the trigger frame) contained in the decoded data signal to the NAV control unit 105. The data decoding unit 104 also outputs the decoded data signal and the error detection result to the scheduling unit 106.

[0078] The NAV control unit 105 controls the NAV using, for example, the destination information and TXOP information input from the preamble demodulation unit 102, and at least one of the MAC header and destination information input from the data decoding unit 104.

[0079] For example, the NAV control unit 105 may decide whether or not to update the NAV individually for each type of NAV, depending on whether the destination of the data signal is AP100, based on the destination information or the source address included in the MAC header. In other words, the NAV control unit 105 may set different NAV settings depending on whether or not the source of the data signal belongs to a common cooperation group with AP100. When updating the NAV, the NAV control unit 105 may decide the period of the NAV to be updated based on, for example, the TXOP information and at least one of the values ​​of the Duration / ID field included in the MAC header. The NAV control unit 105 outputs the value of the NAV counter for each type of NAV to the scheduling unit 106.

[0080] The scheduling unit 106 may, for example, decide whether or not to perform transmission in MAP coordination based on the value of the NAV counter input from the NAV control unit 105. If transmission is performed, the scheduling unit 106 determines the scheduling information for the coordinated signal. The scheduling information for the coordinated signal may include, for example, the method of coordinated transmission in MAP coordination, user information participating in the coordinated transmission, resource information available to each user individually, and information such as MCS or error correction codes. The scheduling unit 106 may also determine the scheduling information for the coordinated signal based on the scheduling information notified by the decoded data signal input from the data decoding unit 104. The scheduling unit 106 outputs the scheduling information for the coordinated signal to the data generation unit 107, the data encoding unit 108, the data modulation unit 109, and the preamble generation unit 110. If transmission is not performed by NAV, the scheduling unit 106 does not need to output scheduling information to the data generation unit 107, the data encoding unit 108, and the data modulation unit 109.

[0081] The data generation unit 107 generates a data sequence to be transmitted to the AP100 (e.g., a downlink wireless transmitter) or STA200 (e.g., a downlink wireless receiver) based on scheduling information of the coordinated signal input from the scheduling unit 106, and outputs the data sequence to the data encoding unit 108.

[0082] For example, the data sequence transmitted to AP100 may include a response signal to a MAP coordination participation request. Also, for example, the data sequence transmitted to STA200 may include resource information for STA200 to transmit or receive coordination signals, a trigger frame for requesting the transmission of UL signals, and a response signal (Ack or Block Ack) to signals transmitted from STA200.

[0083] The data encoding unit 108 encodes the data sequence input from the data generation unit 107 based on scheduling information input from the scheduling unit 106, and outputs the encoded data to the data modulation unit 109.

[0084] The data modulation unit 109 modulates and performs an inverse Fourier transform (e.g., Inverse Fast Fourier Transform (IFFT)) on the encoded data input from the data encoding unit 108 based on scheduling information input from the scheduling unit 106, and outputs the modulated data signal to the wireless transmission unit 111.

[0085] The preamble generation unit 110 generates a preamble signal based on scheduling information input from, for example, the scheduling unit 106. For example, the preamble generation unit 110 modulates and performs IFFT processing on the preamble signal and outputs the preamble signal to the wireless transmission unit 111.

[0086] The wireless transmission unit 111 generates a wireless frame (which may be referred to as, for example, a "packet signal" or a "packet") including a data signal input from the data modulation unit 109 and a preamble signal input from the preamble generation unit 110. The wireless transmission unit 111 performs wireless transmission processing such as Digital-to-Analog (D / A) conversion and up-conversion to the carrier frequency on the generated wireless frame, and transmits the signal after the wireless transmission processing to another AP 100 or STA 200 via an antenna.

[0087] <Configuration example of STA200> FIG. 13 is a block diagram showing a configuration example of the STA 200 (for example, a downstream wireless reception device). The STA 200 shown in FIG. 13 may include, for example, a wireless reception unit 201, a preamble demodulation unit 202, a data demodulation unit 203, a data decoding unit 204, a NAV control unit 205, a transmission signal generation unit 206, and a wireless transmission unit 207.

[0088] Note that, for example, at least one of the preamble demodulation unit 202, the data demodulation unit 203, the data decoding unit 204, the NAV control unit 205, and the transmission signal generation unit 206 may be included in the control unit shown in FIG. 11, and the wireless reception unit 201 may be included in the reception unit shown in FIG. 11.

[0089] The wireless reception unit 201 receives a signal transmitted from the AP 100 (downstream wireless transmission device) via an antenna, and performs wireless reception processing such as down-conversion and A / D conversion on the received signal. The wireless reception unit 201 extracts a preamble from the signal after the wireless reception processing and outputs it to the preamble demodulation unit 202. Further, the wireless reception unit 201 extracts a data signal from the signal after the wireless reception processing and outputs it to the data demodulation unit 203.

[0090] The preamble demodulation unit 202 performs demodulation processing, such as FFT, on the preamble signal input from the wireless receiver unit 201, and extracts, for example, receiver control information (e.g., BW, MCS, or error correction code) used for demodulating and decoding the data signal from the demodulated preamble signal. The preamble demodulation unit 202 outputs, for example, the extracted receiver control information to the data demodulation unit 203 and the data decoding unit 204. The preamble demodulation unit 202 also performs channel estimation based on a reference signal included in the preamble signal and derives a channel estimate. The preamble demodulation unit 202 outputs the channel estimate to the data demodulation unit 203. Furthermore, if, for example, the preamble signal contains destination information or TXOP information, the preamble demodulation unit 202 outputs this information to the NAV control unit 205.

[0091] The data demodulation unit 203 demodulates the data signal input from the wireless receiver unit 201 based on, for example, the reception control information and channel estimate input from the preamble demodulation unit 202, and outputs the demodulated data signal destined for STA200 to the data decoding unit 204.

[0092] The data decoding unit 204 decodes the data signal input from the data demodulation unit 203 based on the reception control information input from the preamble demodulation unit 202, for example, and performs error detection such as CRC. If the decoded data is free of errors, the data decoding unit 204 outputs the MAC header and destination information included in the decoded data to the NAV control unit 205 and outputs the decoded data signal to the transmission signal generation unit 206.

[0093] The NAV control unit 205 controls the NAV using, for example, the destination information and TXOP information input from the preamble demodulation unit 202, and at least one of the MAC header and destination information input from the data decoding unit 204.

[0094] For example, the NAV control unit 205 may decide whether or not to update the NAV individually for each type of NAV based on destination information or the source address included in the MAC header (in other words, depending on whether or not the destination of the data signal is the STA200). In other words, the NAV control unit 205 may set different NAV settings depending on whether or not the source of the data signal belongs to a common cooperation group with the STA200. When updating the NAV, the NAV control unit 205 may decide the period of the NAV to be updated based on, for example, TXOP information and at least one of the values ​​of the Duration / ID field included in the MAC header. The NAV control unit 205 outputs the value of the NAV counter for each type of NAV to the transmission signal generation unit 206.

[0095] The transmission signal generation unit 206 determines whether or not to transmit based on the value of the NAV counter input from the NAV control unit 205. If transmission is performed, the transmission signal generation unit 206 generates a transmission signal based on the decoded data signal input from the data decoding unit 204, for example. For example, if the decoded data signal includes a trigger frame, the transmission signal generation unit 206 may generate a data sequence to be transmitted in a Trigger-based Physical Layer Convergence Procedure Protocol Data Unit (TB PPDU) based on the control information included in the trigger frame. The transmission signal generation unit 206 also encodes the data sequence and generates a data signal by performing modulation and IFFT processing on a predetermined frequency resource. The transmission signal generation unit 206 adds a preamble signal to the data signal to generate a wireless frame (e.g., a packet signal) and outputs it to the wireless transmission unit 207.

[0096] The wireless transmission unit 207 performs wireless transmission processing, such as D / A conversion and upconversion to the carrier frequency, on the wireless frame input from the transmission signal generation unit 206, and transmits the processed signal to the AP100 via the antenna.

[0097] [Examples of AP100 and STA200 operation] Next, we will describe examples of the operation of AP100 and STA200 in this embodiment.

[0098] In one non-limiting embodiment of this disclosure, for example, AP100 and STA200 may switch control over NAV depending on whether the signal is transmitted from a terminal (e.g., AP / STA) belonging to a common cooperation group. In other words, AP100 and STA200 may have different settings for NAV depending on whether the source of the received signal belongs to a common cooperation group.

[0099] Here, a coordinating group may be a group consisting of multiple AP100s (for example, an AP candidate set, or a group of destination APs to which an STA200 sends channel quality information), or a group consisting of multiple AP / STAs (for example, a Virtual BSS). A common coordinating group refers to, for example, the coordinating group to which an AP100 or STA200 receiving a signal belongs.

[0100] In the following explanation, the case where "terminal" is a non-AP terminal (non-AP STA) will be described as an example, but unless otherwise specified, "terminal" may refer to either an AP or a non-AP terminal. In other words, one non-limiting embodiment of this disclosure may be applied to either the operation of AP100 or the operation of STA200.

[0101] Here, the terminal (AP / STA) may determine whether or not it belongs to a common cooperation group with the terminal that transmitted the received signal, based on the identifier (or identification information) contained in the received signal.

[0102] Identifiers include, for example, BSSID, BSS color, AP candidate set ID, or Virtual BSSID.

[0103] Identifiers for the coordination group may be included in the MAP coordination operation element shown in Figure 14, for example. As shown in Figure 14, the MAP coordination operation element may include an "AP candidate set ID" that identifies the AP candidate set and a "Virtual BSSID" that identifies the Virtual BSS. AP100 may notify STA200, for example, by including the Multi-AP coordination operation element in at least one of the beacon signal, probe response signal, and association response signal.

[0104] Furthermore, as shown in Figure 15, for example, at least one of the AP candidate set ID and Virtual BSSID may be notified as part of the BSSID. The BSSID is notified, for example, by 46 bits of the 48-bit BSSID field, excluding the top 2 bits. For example, AP100 may assign some of the bits used for BSSID assignment in the BSSID field (e.g., 46 bits) to at least one of the AP candidate set and Virtual BSSID and notify STA200 of this.

[0105] Furthermore, the terminal (AP / STA) may determine, based on user information contained in the received signal, whether or not the terminal belongs to a common cooperation group with the transmitting terminal.

[0106] For example, as shown in Figure 16, the terminal corresponding to the information about the source of the received signal (Transmitter Address (TA)) contained in the MAC header of the received signal and the terminal corresponding to the user information (User Info) contained in the received signal may be determined to be terminals belonging to a common cooperation group.

[0107] For example, a terminal may determine whether or not it belongs to a common cooperation group based on whether or not the user information contained in the received signal includes user information addressed to that terminal. For example, if the user information contained in the received signal includes user information addressed to that terminal, the terminal (AP / STA) may determine that the sender belongs to a common cooperation group. In other words, if the user information contained in the received signal does not include user information addressed to that terminal, the terminal (AP / STA) may determine that the sender does not belong to a common cooperation group.

[0108] Furthermore, the terminal may determine whether the source of the received signal belongs to a common coordination group based on the information about coordination groups included in the beacon signal. For example, as shown in Figure 17, a "MAP coordination information element" containing the identifier of a terminal belonging to the coordination group may be notified to the terminal. The identifier included in the MAP coordination information element may be the identifier of AP100 or the identifier of STA200. The terminal may, for example, determine whether it and the terminal that sent the received signal belong to a common coordination group based on the MAP coordination information element that was previously notified and included in the beacon signal.

[0109] Furthermore, if the cooperative group is composed of multiple AP100s, the STA200 may determine whether the terminal and the terminal that transmits the received signal belong to the same cooperative group, depending on whether the cooperative group of the terminal that transmits the received signal and the cooperative group of the AP100 to which the STA200 belongs are the same.

[0110] Furthermore, if a coordinating group consists of multiple AP / STAs, AP / STAs that do not participate in coordinating transmission do not need to be included in the coordinating group.

[0111] Next, an example of a NAV control method based on the method described above will be explained.

[0112] [Method 1] In Method 1, for example, if a terminal (AP / STA) receives a signal containing information about TXOP from another terminal belonging to a common coordination group (in other words, is notified of it), it will not update (or configure) its NAV. In other words, if a terminal (AP / STA) is notified of TXOP by a signal transmitted from a terminal belonging to a common coordination group, it decides not to update its NAV.

[0113] For example, a terminal may determine whether it and the source terminal belong to a common coordination group based on signals received before or during MAP coordination processing.

[0114] <Example 1 of Method 1> In Example 1 of Method 1, the STA200 does not update the NAV if it is notified of information regarding TXOP by a signal transmitted from a terminal (AP / STA) belonging to a common cooperation group.

[0115] Figure 18 shows an example of NAV control operation according to Example 1 of Method 1. In the example shown in Figure 18, AP1 (Sharing AP) and STA1 belong to BSS1, and AP2 (Shared AP) and STA2 belong to BSS2. Also, in the example shown in Figure 18, AP1, AP2, STA1, and STA2 belong to a common cooperation group.

[0116] If, for example, the NAV control method specified in 11ax described above is applied to the wireless communication system configuration example shown in Figure 18, then when STA1 and STA2 receive signals related to MAP coordination negotiation transmitted by AP1 and AP2 (e.g., CTI, CTR, or CTAS), they will update the NAV (Intra-BSS NAV or Basic NAV) because the received signal is not addressed to STA1 and STA2. As a result, UL transmission (UL Tx) by STA1 and STA2 may be canceled.

[0117] In contrast, in Example 1 of Method 1, the STA200 decides whether or not to update the NAV depending on whether or not the received signal is transmitted from a terminal belonging to a common cooperation group.

[0118] For example, as shown in Figure 18, since STA1 and STA2 and AP1 belong to a common coordination group, STA1 and STA2 do not update the NAV even when they receive a MAP coordination negotiation signal (e.g., CTI or CTAS addressed to AP2) transmitted from AP1.

[0119] Similarly, as shown in Figure 18, for example, since STA1 and STA2 and AP2 belong to a common coordination group, STA1 and STA2 do not update the NAV even when they receive a MAP coordination negotiation signal (e.g., a CTR addressed to AP1) transmitted from AP2.

[0120] Therefore, as shown in Figure 18, after MAP coordination negotiation, STA1 and STA2 become capable of performing UL transmission when instructed to do so by the trigger frame.

[0121] On the other hand, as shown in Figure 18, terminals that do not belong to the same cooperation group as AP1 and AP2 (Other AP / STA) will set up Basic NAV when they receive a MAP coordination negotiation signal from AP1 or AP2.

[0122] Thus, in Example 1 of Method 1, STA200 does not update the NAV when the source of the received signal belongs to a common cooperation group, and updates the NAV when the source of the received signal does not belong to a common cooperation group. This NAV control allows STA200 to transmit UL signals without being hindered by the NAV setting by the transmission signal of AP100, which belongs to a common cooperation group, for example.

[0123] Furthermore, STA200 may update its NAV if it receives a signal that is different from a MAP coordination signal, even if it is a transmission signal from a terminal belonging to a coordinating group. STA200 may also distinguish signals that are different from MAP coordination signals by, for example, an identifier (e.g., BSSID or BSScolor for non-coordinating transmissions).

[0124] <Example 2 of Method 1> In Example 2 of Method 1, AP100 does not update the NAV if it is notified of information regarding TXOP by a signal transmitted from a terminal (AP / STA) belonging to a common cooperation group.

[0125] Figure 19 shows an example of NAV control operation according to Example 2 of Method 1. In the example shown in Figure 19, AP1 (Sharing AP) and STA1 belong to BSS1, and AP2 (Shared AP) and STA2 belong to BSS2. Also, in the example shown in Figure 19, AP1, AP2, STA1, and STA2 belong to a common cooperation group.

[0126] In Figure 19, for example, as in Figure 8, the TXOP acquired by AP1 (Sharing AP) may be divided into multiple TXOPs (e.g., TXOP1, TXOP2, and TXOP3) based on the timing of UL transmission from each STA. Therefore, even when Basic NAV is configured, as in STA2 shown in Figure 19, UL transmission instructed by the Trigger frame from AP2 becomes possible.

[0127] If, for example, the NAV control method specified in 11ax described above is applied to the wireless communication system configuration example shown in Figure 19, then when AP2 receives a Trigger frame from AP1 destined for STA1, for example, since the received signal is not a signal destined for AP2, it updates (or sets) the Basic NAV. As a result, the transmission of a Trigger frame from AP2 destined for STA2 may be canceled.

[0128] In contrast, in Example 2 of Method 1, AP100 decides whether or not to update the NAV depending on whether or not the received signal is transmitted from a terminal belonging to a common cooperation group.

[0129] For example, as shown in Figure 19, since AP2 and AP1 belong to a common cooperation group, AP2 does not update the NAV even when it receives a Trigger frame sent from AP1 to STA1.

[0130] Thus, in Example 2 of Method 1, AP100 does not update the NAV when the source of the received signal belongs to a common cooperation group, and updates the NAV when the source of the received signal does not belong to a common cooperation group. This NAV control allows AP100 to perform coordinated transmission without being hindered by the NAV setting of other AP100s that belong to the common cooperation group, for example.

[0131] Furthermore, AP100 may update its NAV if it receives a signal that is different from a MAP coordination signal, even if it is a transmission signal from a terminal belonging to a cooperative group. AP100 may distinguish a signal that is different from a MAP coordination signal by, for example, an identifier (e.g., BSSID or BSScolor for non-cooperative transmission).

[0132] The above explains Method 1.

[0133] For example, in Example 1 of Method 1 (Figure 18), an example of STA200 operation was described. However, in Example 1 of Method 1, AP100 does not need to update its NAV if it receives information about TXOP from a terminal (AP / STA) belonging to a common cooperation group, similar to Example 2. For example, in Figure 18, AP2 does not need to update its NAV if it receives a Trigger frame from AP1 addressed to STA1.

[0134] [Method 2] In Method 2, for example, if a terminal (AP / STA) receives a signal containing information about TXOP from another terminal belonging to a common cooperation group (in other words, is notified), it updates the Intra-BSS NAV.

[0135] Furthermore, in Method 2, if the user information of a signal (e.g., Trigger frame) transmitted from another terminal belonging to a common cooperation group includes the identifier (e.g., AID) of the terminal (itself), the terminal may respond without considering Intra-BSS NAV. For example, if the user information of a signal transmitted from another terminal belonging to a common cooperation group includes the identifier of the terminal, the terminal may ignore Intra-BSS NAV and transmit a UL signal.

[0136] Figure 20 shows an example of NAV control operation according to Method 2. In the example shown in Figure 20, AP1 (Sharing AP) and STA1 belong to BSS1, and AP2 (Shared AP) and STA2 belong to BSS2. Also in the example shown in Figure 20, AP1, AP2, STA1, and STA2 belong to a common cooperation group. Also in the example shown in Figure 20, AP3 and STA3 do not belong to a common cooperation group with AP1, AP2, STA1, and STA2.

[0137] If the NAV control method specified in 11ax described above is applied to the example wireless communication system configuration shown in Figure 20, STA1 will update the Intra-BSS NAV by, for example, a signal from AP1 to AP2 (e.g., CTI, CTAS) and the Basic NAV by, for example, a signal from AP2 to AP1 (e.g., CTR). Similarly, if the NAV control method specified in 11ax described above is applied, STA2 will update the Basic NAV by, for example, a signal from AP1 to AP2 (e.g., CTI, CTAS) and the Intra-BSS NAV by, for example, a signal from AP2 to AP1 (e.g., CTR).

[0138] Thus, for example, in the 11ax NAV control method, STA1 updates the Basic NAV based on signals from AP2, and STA2 updates the Basic NAV based on signals from AP1, which may cause the transmission of UL signals, which are instructed by trigger frames from APs belonging to the common BSS, to be discontinued.

[0139] In contrast, in Method 2, terminals (AP / STA) update their Intra-BSS NAV when a TXOP is notified by a signal transmitted from a terminal belonging to a common cooperation group. For example, as shown in Figure 20, if STA1 and STA2 receive a signal from AP1 and AP2 destined for another terminal, they may update their Intra-BSS NAV regardless of the BSS to which they belong (in other words, instead of Basic NAV), as long as the source terminal belongs to a common cooperation group.

[0140] Furthermore, in Method 2, for example, in the example shown in Figure 20, if STA1 is instructed to transmit a UL signal by a Trigger frame sent from AP1, which belongs to a common cooperation group, it may set the Intra-BSS NAV counter to 0 (in other words, reset it) and perform the UL transmission.

[0141] Furthermore, as shown in Figure 20, STA2, like STA1, sets its Intra-BSS NAV counter to 0 when instructed to perform UL transmission by a Trigger frame sent from AP2, which belongs to the common cooperation group. However, as shown in Figure 20, even when the Intra-BSS NAV counter is set to 0 in STA2, Basic NAV is set in STA2 by a transmission signal from another terminal (e.g., AP3) that does not belong to the common cooperation group, so STA2 cancels UL transmission.

[0142] Note that Figure 20 illustrates the case where STA200 sets the Intra-BSS NAV counter to 0 when it is instructed (requested) to transmit a UL signal by a Trigger frame sent from AP100 belonging to a common coordination group, but it is not limited to this. For example, as shown in Figure 21, when STA200 is instructed to transmit a UL signal by a Trigger frame sent from AP100 belonging to a common coordination group, it may transmit the UL signal without considering (e.g., ignoring) Intra-BSS NAV for a certain period (e.g., the signal length transmitted in response to the Trigger frame, or the time resources notified by the Trigger frame). For example, STA200 may decrement the Intra-BSS NAV counter according to the elapsed time even during the period when Intra-BSS NAV is not considered.

[0143] Thus, in Method 2, if STA200 receives a signal containing information about TXOP from a source belonging to a common coordination group, it may set an Intra-BSS NAV (e.g., a transmission blackout period for the common BSS). Alternatively, if STA200 receives a signal containing information about TXOP from a source that does not belong to a common coordination group, it may set a Basic NAV (e.g., a transmission blackout period for the OBSS).

[0144] Furthermore, if STA200 receives a Trigger frame containing user information addressed to STA200, it may deactivate the Intra-BSS NAV settings. In other words, STA200 does not need to deactivate the Basic NAV settings even if it receives a Trigger frame containing user information addressed to STA200.

[0145] Therefore, AP100 only needs to notify terminals belonging to a common coordinating group of information regarding Intra-BSS NAV. This allows, for example, STA200 participating in coordinated transmission (STA200 within the coordinating group) to disable only Intra-BSS NAV and enable STA200 to transmit UL signals.

[0146] Furthermore, in Method 2, for example, UL transmission by STA200s that do not participate in coordinated transmission can be suppressed by not disabling the Intra-BSS NAV of STA200s that do not participate in coordinated transmission (e.g., STA200s outside the coordinated group). Also, for example, UL transmission by STA200s that do not belong to the common coordinated group can be suppressed by disabling the Intra-BSS NAV of STA200s that belong to the common coordinated group, and not disabling the Basic NAV for transmission signals from terminals that do not belong to the common coordinated group. Therefore, according to Method 2, conflicts in MAP coordination can be suppressed.

[0147] <Method 2-1> In Method 2-1, AP100 may include in the transmission signal control information indicating that it will transmit without considering (ignoring) Intra-BSS NAVs notified by terminals belonging to a common cooperation group. STA200 may receive control information indicating that it will transmit while ignoring Intra-BSS NAVs (for example, information regarding the deactivation of the Intra-BSS NAV corresponding to a common cooperation group), and based on the received information, deactivate the Intra-BSS NAV.

[0148] Figure 22 shows an example of a transmission signal (e.g., a trigger frame) that includes control information to indicate a transmission that does not take Intra-BSS NAV into consideration.

[0149] As shown in Figure 22, control information (for example, the "ignore NAV" subfield) that notifies a transmission that does not consider Intra-BSS NAV (a transmission that ignores Intra-BSS NAV) may be included in the user information of the trigger frame. For example, if ignore NAV=1, STA200 may cancel or temporarily ignore Intra-BSS NAV and send the TB PPDU. For example, the period for which Intra-BSS NAV is ignored may be notified to STA200 by the UL Length subfield in the Common field of the trigger frame.

[0150] On the other hand, for example, if ignore NAV=0, STA200 does not need to ignore Intra-BSS NAV.

[0151] Thus, by Method 2-1, for example, AP100 can notify STA200 individually whether or not to ignore Intra-BSS NAV, thereby enabling a specific STA200 to ignore Intra-BSS NAV and transmit UL signals, and also notify other terminals whether or not each STA200 will ignore Intra-BSS NAV.

[0152] The above describes an example of a NAV control method in MAP coordination.

[0153] Thus, in this embodiment, AP100 and STA200 may perform different NAV-related controls depending on whether the received signal is a signal transmitted from a terminal (e.g., AP / STA) belonging to a common cooperation group.

[0154] For example, as in Method 1, in a common coordination group, each terminal does not need to update (set) the NAV even when it receives a signal intended for another terminal. This prevents AP100, which belongs to the coordination group, from being unable to transmit a Trigger frame in MAP coordination, for example. Also, it prevents STA200 from being unable to transmit a UL when it receives a Trigger frame. Therefore, according to this embodiment, it is possible to avoid the coordination transmission in MAP coordination being hindered by the NAV.

[0155] Furthermore, as in Method 2, for example, terminals (AP / STA) belonging to a common cooperation group may update the Intra-BSS NAV without updating the Basic NAV based on signals related to the common cooperation group. This allows, for example, a rule to ignore the NAV to be applied only to terminals belonging to the common cooperation group, thus avoiding conflicts caused by configured rules to ignore the NAV.

[0156] Thus, according to this embodiment, in MAP coordination, interference with AP / STA transmission and reception by NAV control is suppressed, and cooperative communication in MAP coordination can be performed appropriately, thereby improving the communication efficiency of cooperative communication in MAP coordination.

[0157] One embodiment of the present disclosure has been described above.

[0158] (Other embodiments) (1) In the above-described embodiment, an example was given in which STA200 transmits a UL signal in CTDMA of MAP coordination, but the coordination method is not limited to CTDMA and other methods may be used.

[0159] (2) Example 2 of Method 1 and Method 2 may be applied in combination. For example, AP100 does not need to update the NAV when it receives a signal from a terminal belonging to a common cooperation group destined for another terminal, as shown in Figure 19. Also, for example, STA200 may update the Intra-BSS NAV when it receives a signal from a terminal belonging to a common cooperation group destined for another terminal, and may ignore (for example, temporarily ignore) the Intra-BSS NAV when it receives a trigger frame instructing the transmission of a UL signal.

[0160] (3) Methods 1 and 2 of the embodiments described above show examples in which negotiation between AP100s (e.g., Tx Indication and Request phase and Schedule Allocation phase) and coordinated transmission (Data Tx phase) are performed within a single TXOP, as shown in Figure 1, but are not limited thereto. For example, one non-limiting embodiment of this disclosure may be applied to MAP coordination using multiple TXOPs.

[0161] For example, as shown in Figure 23, a three-stage MAP coordination process may be performed across multiple TXOPs. In the example shown in Figure 23, the first TXOP performs the Tx Indication and Request phase to determine which AP100s will participate in the MAP coordination, and the second TXOP performs the Schedule Allocation phase and the Data Tx phase.

[0162] Note that the number of TXOPs and the combinations of operations performed in each TXOP shown in Figure 23 are examples only and are not limited to those shown.

[0163] (4) Methods 1 and 2 of the above-described embodiments may also be applied to MAP sounding.

[0164] MAP sounding is a method of acquiring channel information in a coordinated manner through sounding performed in coordination between AP100 devices. Examples of sounding performed in coordination between AP100 devices include sequential sounding as shown in Figure 24, or joint sounding as shown in Figure 25.

[0165] For example, in Figures 24 and 25, STA1 is a sharing AP belonging to AP1, which is a sharing AP, and STA2 is a shred STA belonging to AP2, which is a shared AP. For example, in sequential sounding as shown in Figure 24, AP2 updates its Basic NAV with a TXOP notified by a Null Data Packet Announcement (NDPA) from AP1. Therefore, AP2 may stop sending NDPAs due to the Basic NAV.

[0166] In this case, for example, as in Example 2 of Method 1, AP2 can achieve sequential sounding (e.g., transmission of signals such as NDPA) by not updating the Basic NAV in the TXOP notified by NDPA from AP1, which belongs to a common cooperative transmission group.

[0167] Furthermore, there are no restrictions on when MAP sounding is performed.

[0168] For example, as shown in Figure 26, Multi-AP sounding may be performed before the decision on whether or not to participate in MAP coordination is made through negotiation between AP100s, and channel information that may be used for MAP coordination may be obtained in advance.

[0169] Alternatively, as shown in Figure 27, for example, after determining whether or not to participate in MAP coordination through negotiation between AP100s, Multi-AP sounding may be performed to obtain channel information to be used for coordinated transmission.

[0170] (5) Although Method 2 described a method for notifying the temporary disregard of Intra-BSS NAV, the method for notifying the temporary disregard of Intra-BSS NAV is not limited to notification by control information.

[0171] For example, AP100 may instruct the order in which STA200 ignores Intra-BSS NAV based on the transmission order (or arrangement order) of user information in the trigger frame. For example, as shown in Figure 28, if the trigger frame contains multiple user information, the STA200 instructed by User Info#1 may ignore Intra-BSS NAV and transmit the UL signal after a specified time (e.g., Short Inter Frame Space (SIFS)) has elapsed since receiving the trigger frame.

[0172] Similarly, an STA200 indicated by the Mth user information (where M is greater than 1 and less than or equal to N, the maximum value of the user information) will know the STA ID contained in the M-1th user information. For example, if an STA200 indicated by the Mth user information detects the STA ID of the M-1th user information from the received signal (i.e., receives a signal from the M-1th STA), it may transmit a UL signal after SIFS.

[0173] Furthermore, the period during which Intra-BSS NAV will be ignored for multiple STA200s whose trigger frames contain user information may be notified, for example, in the common information of the trigger frame (e.g., the UL Length subfield of Common Info).

[0174] Figure 29 shows an example of how the order in which ignore NAV is applied is notified based on the order in which user information is transmitted. As shown in Figure 29, STA1, which is indicated by the user information at the beginning of the trigger frame, sends a UL signal after SIFS receives the trigger frame. Also, as shown in Figure 29, STA2, which is indicated by the second user information in the trigger frame, sends a UL signal after SIFS receives the UL signal from STA1.

[0175] (6) In Method 2, the period for ignoring Intra-BSS NAV for multiple STA200s may be notified by common information in the Trigger frame. For example, the period for ignoring Intra-BSS NAV may be set in common for multiple STA200s. In this case, the duration of the ignore NAV may be notified in the common information of the Trigger frame (for example, the UL Length subfield of Common Info).

[0176] For example, as shown in Figure 30, AP1 notifies each STA (STA1 and STA2) of the ignore NAV period (e.g., T[us]) in the UL Length subfield of the trigger frame. STA1 may send a UL signal of length T[us] after receiving the trigger frame via SIFS. STA2 may also send a UL signal of length T[us] after receiving the trigger frame via SIFS+T[us].

[0177] (7) In Method 2-1, the time allocation information for ignore NAV may be individually notified to the STA200 using the user information of the Trigger frame. For example, as shown in Figure 31, AP100 may use the Trigger Dependent User Info in the user information to notify the ignore NAV length subfield.

[0178] For example, as shown in Figure 32, AP1 may notify each STA of individual ignore NAV time allocation information to the User Info corresponding to STA1 and STA2, respectively. For example, as shown in Figure 32, STA1 may send a UL signal of length T1[us] after receiving a trigger frame via SIFS. Similarly, STA2 may send a UL signal of length T2[us] after receiving a trigger frame via SIFS+T1[us]+SIFS.

[0179] (8) In Method 2-1, a method was described in which control information (ignore NAV subfield) indicating that Intra-BSS NAV should be temporarily ignored and transmitted is included in the user information of the Trigger frame. However, the method is not limited to this, and notification may be given using other user information.

[0180] For example, as shown in Figure 33, the ignore NAV may be notified using the Reserved subfield included in the user information (User field) of the EHT-SIG.

[0181] Alternatively, as shown in Figure 34, for example, the ignore NAV may be notified using the Reserved subfield included in the NDPA user information (STA Info field).

[0182] Furthermore, the information used to notify ignore NAV is not limited to user information. For example, ignore NAV may be notified in common information. Figure 35 shows an example of notifying ignore NAV in common information. As shown in Figure 35, ignore NAV may be notified using the Disregard subfield included in U-SIG. When ignore NAV is notified in common information, terminals may, for example, control NAV for each BSS. For example, if ignore NAV=1, terminals of BSSs that have a BSS color common to the BSS color notified by the BSS color subfield of U-SIG may temporarily ignore and transmit the Intra-BSS NAV.

[0183] (9) Methods 1 and 2 are not limited to application to MAP coordination. For example, methods 1 and 2 may be applied to Triggered TXOP Sharing.

[0184] Triggered TXOP Sharing is a transmission method that uses a Multi-User (MU)-RTS TXOP Sharing (TXS) trigger frame to allocate a portion of the TXOPs acquired by AP100 to STA200. Furthermore, Triggered TXOP Sharing can switch between two communication methods depending on the value of the TXOP Sharing Mode subfield included in the MU-RTS TXS trigger frame.

[0185] The first communication method is that when TXOP Sharing Mode = 1 is notified in the MU-RTS TXS Trigger frame, STA200 will send a UL to its affiliated AP100 during the TXOP assigned to STA200.

[0186] The second communication method is that when TXOP Sharing mode = 2 is notified in the MU-RTS TXS Trigger frame, STA200 transmits between the TXOPs assigned to it and AP100 or other STAs.

[0187] Furthermore, if TXOP Sharing Mode = 0, Triggered TXOP Sharing will not occur. In addition, the control signal that AP100 uses to notify STA200 of scheduling information (e.g., CTLS in Figure 2) may be notified using a MU-RTS Trigger frame or a MU-RTS TXS Trigger frame.

[0188] Figure 36 shows an example of applying Method 2 when TXOP Sharing Mode = 1. In the example shown in Figure 36, AP1 and STA1 belong to a common cooperation group.

[0189] As shown in Figure 36, AP1 notifies other terminals of a TXOP by sending a CTS signal (called CTS-to-self) that includes AP1's address as the destination information. When STA1 receives a CTS-to-self signal from AP1, it updates the Intra-BSS NAV.

[0190] Next, AP1 sends a MU-RTS TXS Trigger frame containing TXOP Sharing Mode = 1 to STA1 and assigns a TXOP to STA1. If the NAV control method defined in 11ax described above is applied, STA1 may abort transmissions from STA1 to AP1 due to an Intra-BSS NAV notified by AP1. In contrast, if method 2 is applied, STA1 may temporarily ignore the Intra-BSS NAV for the duration of the time resources notified by the MU-RTS TXS Trigger frame if it is notified of Triggered TXOP Sharing by AP1, which is a common coordinating group. For example, STA1 may send a CTS signal to AP1 in response to the MU-RTS TXS Trigger frame, and then send a Data signal to AP1 using a PPDU that is not a TB PPDU.

[0191] Figure 37 shows an example of applying Method 2 when TXOP Sharing Mode = 2. In the example shown in Figure 37, AP1, STA1, and STA2 belong to a common cooperation group.

[0192] As shown in Figure 37, AP1 notifies STA1 and STA2 of the TXOP by transmitting a CTS-to-self signal. When STA1 and STA2 receive the CTS-to-self signal from AP1, they update the Intra-BSS NAV.

[0193] Next, AP1 sends a MU-RTS TXS Trigger frame containing TXOP Sharing Mode = 2 to STA1 and assigns a TXOP to STA1. If the NAV control method defined in 11ax described above is applied, STA1 may cancel transmissions from STA1 to AP1 or STA2 due to an Intra-BSS NAV notified by AP1. Similarly, STA2 may cancel transmissions from STA2 to STA1 due to an Intra-BSS NAV notified by AP1. In contrast, if method 2 is applied, STA1 may temporarily ignore the Intra-BSS NAV for the duration of the time resources notified by the MU-RTS TXS Trigger frame when it is notified of Triggered TXOP Sharing by AP1, which is a common coordinating group.

[0194] For example, STA1 may, after sending a CTS signal to AP1 in response to a MU-RTS TXS Trigger frame, send a Data signal to another STA (e.g., STA2) using a PPDU other than TB PPDU.

[0195] Furthermore, as shown in Figure 37, STA2, which receives a Data signal from STA1, a common cooperation group, may temporarily ignore the Intra-BSS NAV in order to send an Ack signal for the Data signal.

[0196] (10) The values ​​such as the number of APs, STAs, and BSSs used in the above-described embodiments are examples only and are not limited to them; other values ​​may be set.

[0197] Furthermore, while the above embodiment describes a configuration example based on the 11ax frame format, the format to which this embodiment of the disclosure is applied is not limited to the 11ax format.

[0198] Furthermore, although the above embodiment describes the operation in UL communication, one embodiment of this disclosure is not limited to UL communication, but may also be applied to DL communication or sidelinks, for example.

[0199] Furthermore, the frame configuration (e.g., format) described in the above embodiment is merely an example and is not limited to these; other configurations are also possible. For example, in these frame configurations, some fields may not be set, and other fields may be set.

[0200] (11) Information indicating whether or not STA200 supports the functions, operations, or processes described in the embodiments described above may be transmitted (or notified) from STA200 to AP100 as, for example, STA200 capability information or capability parameters.

[0201] The capability information may include an information element (IE) that individually indicates whether STA200 supports at least one of the functions, operations, or processes shown in each of the embodiments described above. Alternatively, the capability information may include an information element that indicates whether STA200 supports any two or more combinations of the functions, operations, or processes shown in each of the embodiments described above. An information element is also simply called an element.

[0202] AP100 may, for example, determine (or decide or assume) which functions, operations, or processes are supported (or not supported) by STA200, the source of the capability information, based on capability information received from STA200. AP100 may perform operations, processes, or controls in accordance with the determination result based on the capability information. For example, AP100 may control MAP coordination based on capability information received from STA200.

[0203] Furthermore, the fact that STA200 does not support some of the functions, operations, or processes shown in each of the embodiments described above may be interpreted as meaning that such some functions, operations, or processes are restricted in STA200. For example, information or requests regarding such restrictions may be notified to AP100.

[0204] Information regarding the capabilities or limitations of STA200 may be defined, for example, in the standard, or it may be implicitly communicated to AP100 in association with information known to AP100 or information transmitted to AP100.

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

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

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

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

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

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

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

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

[0213] A communication device according to one embodiment of the present disclosure is a communication device comprising a receiving circuit for receiving a signal and a control circuit for setting different transmission prohibition periods depending on whether the source of the signal belongs to a group relating to cooperative communication common to the communication device.

[0214] In one embodiment of the present disclosure, the control circuit determines whether the transmitter belongs to the group based on the identification information contained in the signal.

[0215] In one embodiment of the present disclosure, the control circuit determines that the sender belongs to the group if the signal includes user information addressed to the communication device.

[0216] In one embodiment of the present disclosure, the control circuit determines whether the transmitter belongs to the group based on the information about the group contained in the beacon signal.

[0217] In one embodiment of the present disclosure, the communication device is a station (STA), and the control circuit does not set the transmission prohibition period when it receives the signal containing information about a transmission opportunity from the transmitter belonging to the group.

[0218] In one embodiment of the present disclosure, the communication device is an access point, and the control circuit does not set the transmission prohibition period when it receives the signal containing information about a transmission opportunity from the source belonging to the group.

[0219] In one embodiment of the present disclosure, the control circuit sets a first transmission prohibition period for a Basic Service Set (BSS) common to the communication device when it receives the signal containing information about a transmission opportunity from a source belonging to the group, and sets a second transmission prohibition period for a BSS different from that of the communication device when it receives the signal containing information about a transmission opportunity from a source not belonging to the group.

[0220] In one embodiment of the present disclosure, when the control circuit receives a trigger frame containing user information addressed to the communication device, it releases the setting of the first transmission prohibition period.

[0221] In one embodiment of the present disclosure, the present invention further comprises a receiving circuit that receives information regarding the release of the setting of the first transmission prohibition period, and the control circuit releases the setting of the first transmission prohibition period based on the information.

[0222] In a communication method according to one embodiment of the present disclosure, the communication device receives a signal and sets different settings regarding the transmission prohibition period depending on whether the source of the signal belongs to a common cooperative communication group with the communication device.

[0223] All disclosures in the specification, drawings, and abstract contained in the Japanese application 2021-128430, filed on August 4, 2021, are incorporated herein by reference. [Industrial applicability]

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

[0225] 100 AP 101,201 Wireless receiver 102 Preamble demodulation section 103 Data Demodulation Unit 104 Data Decoding Unit 105,205 NAV control section 106 Scheduling Unit 107 Data Generation Unit 108 Data Encoding Section 109 Data Modulation Section 110 Preamble generation section 111,207 Wireless Transmitter 200 STA 202 Preamble demodulation section 203 Data Demodulation Unit 204 Data Decoding Unit 206 Transmission signal generation unit

Claims

1. A terminal associated with the first access point, A receiving circuit that receives signals, A control circuit that sets information regarding a transmission prohibition period based on the information contained in the received signal and controls transmission based on the information regarding the transmission prohibition period, A transmitting circuit that transmits a signal to the first access point, It is equipped with, When a signal transmitted from the first access point or a second access point different from the first access point is received, and information regarding the transmission prohibition period is set based on the received signal, The aforementioned control circuit is When the second access point is communicating in coordination with the first access point, the transmission circuit is permitted to transmit regardless of the setting status of the information regarding the transmission prohibition period. When the second access point is not communicating in coordination with the first access point, the transmission circuit is prohibited from transmitting according to the setting status of the information regarding the transmission prohibition period. Terminal.

2. The setting of the information regarding the transmission prohibition period is determined based on the value of the TXOP subfield included in the received signal. The terminal according to claim 1.

3. The value of the TXOP subfield is included in the U-SIG field of the PPDU preamble of the received signal. The terminal according to claim 2.

4. The terminal and the first access point belong to a first Basic Service Set (BSS), and the second access point belongs to a second BSS that is different from the first BSS. The control circuit, if the received signal is a signal transmitted from the first access point or the second access point, determines whether the first access point and the second access point are in cooperative communication based on the BSS Color contained in the received signal. The terminal according to claim 1.

5. The BSS Color is included in the U-SIG field of the PPDU preamble of the received signal. The terminal according to claim 4.

Images