Method and apparatus used for wireless communication

Abstract

The present application discloses a method and apparatus used for wireless communication. A first receiver receives a first message and a second message, the first message indicating a first transmission opportunity on a first channel, and the end moment of the first transmission opportunity being a first moment. The second message indicates that the first transmission opportunity ends at a second moment, the second moment being earlier than the first moment. A first transmitter sends a third message, the third message indicating a second transmission opportunity on the first channel, and the end moment of the second transmission opportunity being the first moment. The first channel is a main channel of a first basic service set, and a first node belongs to the first basic service set. The transmission time required by data to be sent of the first node is greater than the time which can be used for data transmission within the second transmission opportunity. According to the present application, delay reduction is facilitated, and the fairness of channel contention is ensured.

Description

A method and apparatus for wireless communication

[0001] This application claims priority to the Chinese Patent Application No. 202410412408.3, filed on April 7, 2024, entitled “A method and apparatus for wireless communication” and to the Chinese Patent Application No. 202410438164.6, filed on April 11, 2024, entitled “A method and apparatus for wireless communication”, the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0002] The present application relates to a method and apparatus in a wireless communication system, and more particularly, to a method and apparatus for reducing latency and ensuring fairness of channel contention in a wireless local area network (WLAN). BACKGROUND

[0003] Wi-Fi (Wireless Fidelity) has become a ubiquitous technology in today’s world, providing connectivity for billions of devices and being the preferred way for more and more users to access the Internet, and has the trend of gradually replacing wired access. Wi-Fi technology has become the mainstream technical standard of WLAN (Wireless Local Area Network) due to its relatively simple implementation, reliable communication, high flexibility and relatively low implementation cost. To adapt to the ever-increasing new business applications and reduce the gap with the transmission performance of wired networks, each generation of Wi-Fi standards strives to improve wireless transmission rates. With the further increase of Wi-Fi application requirements for high transmission rate, low latency and high reliability, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 Working Group formed the UHR (Ultra High Reliability) Study Group (SG) in 2022, starting the research work of the next generation of IEEE 802.11 standards, and formed the UHR TG (Task Group) in 2023, officially starting the standardization work of the future Wi-Fi 8 protocol.

[0004] The maximum operating bandwidth of Wi-Fi devices has been supported up to 320MHz through techniques such as preamble puncturing, channel bonding, etc. However, according to the current specification, the primary channel is the only channel that can perform the back-off procedure, and only when it is idle does the node allow frame exchange, which limits the spectrum utilization. That is, the blocking of the primary channel is still a bottleneck in terms of system reliability, because if an interfering transmission (such as an overlapping basic service set transmission or other prior art) overlaps with the channel, there can be a large amount of bandwidth of the secondary channels that is idle. Therefore, a new mechanism, non-primary channel access, is discussed in UHR SG, which allows nodes to still exchange frames in secondary channels when the primary channel is busy. Moreover, this mechanism can utilize bandwidth that cannot be used based on traditional techniques, which helps to reduce latency and improve throughput and spectral efficiency. SUMMARY

[0005] When a UHR node triggers non-primary channel access due to detecting an overlapping basic service set (OBSS) transmission opportunity (TXOP), the UHR node cannot monitor the status of the primary channel after switching to the secondary channel due to device capability constraints. The problem is that if the OBSS TXOP is truncated, the primary channel will enter the idle state prematurely, and will again be contended for by other nodes of the overlapping basic service set to initiate a TXOP. If the end time of the newly initiated TXOP exceeds the end time of the OBSS TXOP that triggered the non-primary channel access, the UHR node will still be unable to initiate frame exchange on the primary channel for a long time when it switches back to the primary channel because the primary channel is occupied.

[0006] To solve the above problems, the application discloses a solution. In the case of no conflict, the embodiments of the application and the features in the embodiments can be combined with each other at will. It should be noted that in the description of the application, WLAN scenario is only taken as a typical application scenario or example; the application is also applicable to other scenarios (such as relay network, P2P network, and scenario supporting half-duplex user equipment) facing similar problems, and similar technical effects in the WLAN scenario can also be achieved. Further, although the original intention of the application is to aim at WLAN, the application can also be used in WMAN (Wireless Metropolitan Area Network), WRAN (Wireless Regional Area Network), WSN (wireless specialty network) and other wireless networks. In addition, using a unified solution in different scenarios (including but not limited to WLAN scenario and WMAN scenario) can help reduce hardware complexity and cost. In the case of no conflict, the embodiments of the first node device and the features in the embodiments can be applied to the second node device, and vice versa. In particular, the explanation of the terminology (Terminology), noun, function, and variable (if not specially stated) in the application can refer to the definition in the IEEE 802.11, IEEE 802.15, and IEEE 802.22 specification protocols.

[0007] The application discloses a method used in a first node for wireless communication, characterized in that comprising:

[0008] receiving a first message and a second message, the first message indicating a first transmission opportunity on a first channel, an end time of the first transmission opportunity being a first time; the second message indicating that the first transmission opportunity ends at a second time, the second time being earlier than the first time;

[0009] sending a third message, the third message indicating a second transmission opportunity on the first channel, an end time of the second transmission opportunity being the first time;

[0010] wherein the first channel is a primary channel of a first basic service set, and the first node belongs to the first basic service set; a transmission time required by the data to be sent by the first node is greater than a time that can be used for transmitting data in the second transmission opportunity.

[0011] As an embodiment, the benefits of the above method include: facilitating the nodes triggering non-primary channel access due to the first transmission opportunity to compete for the idle first channel at the first time.

[0012] As an embodiment, the above method has the benefit of being compatible with existing channel access techniques.

[0013] According to an aspect of the present application, the above method is characterized in that the first node is a user terminal.

[0014] According to an aspect of the present application, the above method is characterized in that the first time is determined according to a duration field included in the first message and an end time of a PPDU (PHY protocol data unit) carrying the first message; and the second time is determined according to an end time of a PPDU carrying the second message.

[0015] According to an aspect of the present application, the above method is characterized in that the third message is sent only when the second time is earlier than the first time by more than a first threshold.

[0016] As an embodiment, the above method has the benefit of the first node sending the third message only when the remaining time before the first time is long enough.

[0017] According to an aspect of the present application, the above method is characterized in that it comprises:

[0018] receiving, by the first receiver, a fourth message on the first channel, the fourth message indicating to perform a non-primary channel access coordination and a basic service set group performing the non-primary channel access coordination.

[0019] As an embodiment, the above method has the benefit of the method in the present application relying on multi-AP (access point) negotiation.

[0020] According to an aspect of the present application, the above method is characterized in that the fourth message is received earlier than the second message.

[0021] According to an aspect of the present application, the above method is characterized in that it comprises:

[0022] receiving, by the first receiver, a fifth message on the first channel, the fifth message indicating a third transmission opportunity, a sender of the fifth message being a node in a second basic service set, the second basic service set belonging to the service set group performing the non-primary channel access coordination;

[0023] triggering a first operation, the first operation being a non-primary channel access;

[0024] The first operation comprises: switching to a second channel during the third transmission opportunity; sending or receiving on the second channel; switching back to the first channel before the end time of the third transmission opportunity; and the second channel is a secondary channel of the first basic service set.

[0025] As an embodiment, the method has the feature that the first node can initiate frame exchange on the secondary channel when the primary channel is busy.

[0026] As an embodiment, the method has the benefit of reducing delay, improving throughput and spectral efficiency.

[0027] The present application discloses a method used in a second node for wireless communication, which has the features of comprising:

[0028] sending a first message and a second message, the first message indicating a first transmission opportunity on a first channel, the end time of the first transmission opportunity being a first time; and the second message indicating that the first transmission opportunity ends at a second time, the second time being earlier than the first time;

[0029] receiving a third message, the third message indicating a second transmission opportunity on the first channel, the end time of the second transmission opportunity being the first time;

[0030] The first channel is a primary channel of a first basic service set, and the second node belongs to the first basic service set; and the transmission time required by the data to be sent by the first node is greater than the time that can be used for data transmission in the second transmission opportunity.

[0031] According to an aspect of the present application, the method has the feature that the second node is an 802.11 AP.

[0032] According to an aspect of the present application, the method has the feature that the first time is determined according to a duration field included in the first message and the end time of a PPDU carrying the first message; and the second time is determined according to the end time of a PPDU carrying the second message.

[0033] According to an aspect of the present application, the method has the feature that the third message is sent only when the time by which the second time is earlier than the first time is greater than a first threshold.

[0034] According to an aspect of the present application, the method has the feature of comprising:

[0035] sending a fourth message on the first channel, the fourth message indicating to perform non-primary channel access coordination and a basic service set group performing the non-primary channel access coordination.

[0036] According to an aspect of the present application, the method is characterized in that the fourth message is sent earlier than the second message.

[0037] According to an aspect of the present application, the method is characterized in that it comprises:

[0038] receiving a fifth message on the first channel, the fifth message indicating a third transmission opportunity, the sender of the fifth message being a node in a second basic service set, the second basic service set belonging to the service set group performing the non-primary channel access coordination;

[0039] triggering a first operation, the first operation being a non-primary channel access;

[0040] wherein the first operation comprises: switching to a second channel during the third transmission opportunity; transmitting, or receiving, on the second channel; switching back to the first channel before an end time of the third transmission opportunity; the second channel being a secondary channel of the first basic service set.

[0041] The present application discloses a first node used for wireless communication, characterized in that it comprises:

[0042] a first receiver, receiving a first message and a second message, the first message indicating a first transmission opportunity on a first channel, an end time of the first transmission opportunity being a first time; the second message indicating that the first transmission opportunity ends at a second time, the second time being earlier than the first time;

[0043] a first transmitter, sending a third message, the third message indicating a second transmission opportunity on the first channel, an end time of the second transmission opportunity being the first time;

[0044] wherein the first channel is a primary channel of a first basic service set, the first node belonging to the first basic service set; a transmission time required by data to be sent by the first node being greater than a time that can be used for transmitting data in the second transmission opportunity.

[0045] The present application discloses a second node used for wireless communication, characterized in that it comprises:

[0046] a second transmitter, sending a first message and a second message, the first message indicating a first transmission opportunity on a first channel, an end time of the first transmission opportunity being a first time; the second message indicating that the first transmission opportunity ends at a second time, the second time being earlier than the first time;

[0047] a second receiver configured to receive a third message, the third message indicating a second transmission opportunity of the first channel, an end time of the second transmission opportunity being the first time;

[0048] wherein the first channel is a primary channel of a first basic service set, and the second node belongs to the first basic service set; and a transmission time required by the data to be transmitted by the first node is greater than a time available for transmitting data in the second transmission opportunity. BRIEF DESCRIPTION OF DRAWINGS

[0049] Other features, objects, and advantages of the application will become more apparent from the following detailed description when read in conjunction with the accompanying drawings:

[0050] Fig. 1 illustrates a signal processing flowchart in a first node according to one embodiment of the present application;

[0051] Fig. 2 illustrates a network architecture diagram according to one embodiment of the present application;

[0052] Fig. 3 illustrates a diagram of a wireless protocol stack according to one embodiment of the present application;

[0053] Fig. 4 illustrates a hardware module diagram of a communication device according to one embodiment of the present application;

[0054] Fig. 5 illustrates a flowchart of wireless signal transmission between a first node and a second node according to one embodiment of the present application;

[0055] Fig. 6 illustrates a time domain relationship diagram of a first transmission opportunity and a second transmission opportunity according to one embodiment of the present application;

[0056] Fig. 7 illustrates a flowchart of wireless signal transmission between a first node and a second node according to one embodiment of the present application;

[0057] Fig. 8 illustrates a signal processing flowchart in a first node according to one embodiment of the present application;

[0058] Fig. 9 illustrates a time diagram of a first node operating on a first channel and a second channel according to one embodiment of the present application;

[0059] Fig. 10 illustrates a spatial topology diagram of first to fourth nodes according to one embodiment of the present application;

[0060] Fig. 11 illustrates a structural block diagram of a processing apparatus in a first node according to one embodiment of the present application;

[0061] Fig. 12 illustrates a structural block diagram of a processing apparatus in a second node according to one embodiment of the present application. DETAILED DESCRIPTION

[0062] The technical solutions of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily without conflict.

[0063] Embodiment 1

[0064] Embodiment 1 illustrates a signal processing flowchart in a first node according to an embodiment of the present application, as shown in FIG. 1. In FIG. 1, each block represents a step.

[0065] In embodiment 1, the first node 100 receives a first message indicating a first transmission opportunity on a first channel in step 101, the end time of the first transmission opportunity is a first time; receives a second message indicating that the first transmission opportunity ends at a second time in step 102, the second time is earlier than the first time; sends a third message indicating a second transmission opportunity on the first channel in step 103, the end time of the second transmission opportunity is the first time; wherein the first channel is the primary channel of the first basic service set (BSS), and the first node belongs to the first basic service set; the transmission time required by the data to be sent by the first node is greater than the time that can be used for data transmission in the second transmission opportunity.

[0066] As an embodiment, the message type of the first message is a control frame.

[0067] As an embodiment, the first message is an RTS (request to send) frame.

[0068] As an embodiment, the first message is a CTS (clear to send) frame.

[0069] As an embodiment, the first message is a trigger frame.

[0070] As a sub-embodiment of the above-mentioned embodiment, the first message is a MU-RTS (multiple users-RTS) trigger frame, and the value of the trigger type subfield in the Common Info field of the first message is 3.

[0071] As a sub-embodiment of the above-mentioned embodiment, the first message is not a MU-RTS TXS (triggered TXOP sharing) frame.

[0072] As one embodiment, the first message is sent at least on the first channel.

[0073] As one embodiment, the first channel is one of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, a primary 320MHz channel of the first basic service set.

[0074] As one embodiment, the first message indicates a channel bandwidth occupied by the first transmission opportunity.

[0075] As one embodiment, the channel bandwidth occupied by the first transmission opportunity includes at least the first channel.

[0076] As one embodiment, the first node supports channel bonding.

[0077] As one embodiment, the second node supports channel bonding.

[0078] As one embodiment, the channel bandwidth occupied by the first transmission opportunity includes one or more contiguous 20MHz channels.

[0079] As one embodiment, the channel bandwidth occupied by the first transmission opportunity is in a sub-7GHz (sub-7 gigahertz) frequency band.

[0080] As a sub-embodiment of the above embodiment, the channel bandwidth occupied by the first transmission opportunity is in one of {a 2.4GHz frequency band, a 5GHz frequency band, a 6GHz frequency band}.

[0081] As one embodiment, the first node supports preamble puncturing.

[0082] As one embodiment, the second node supports preamble puncturing.

[0083] As one embodiment, the channel bandwidth occupied by the first transmission opportunity includes non-contiguous channels.

[0084] As one embodiment, the channel bandwidth occupied by the first transmission opportunity includes a secondary channel of the first basic service set.

[0085] As one embodiment, the channel bandwidth occupied by the first transmission opportunity is a primary 20MHz channel and a secondary 40MHz channel of the first basic service set.

[0086] As one embodiment, the channel bandwidth occupied by the first transmission opportunity is a primary 40MHz channel and a secondary 80MHz channel of the first basic service set.

[0087] As one embodiment, the channel bandwidth occupied by the first transmission opportunity is a primary 80MHz channel and a secondary 160MHz channel of the first basic service set.

[0088] As one embodiment, a RXVECTOR (Receive Vector) parameter BSS_COLOR of the PPDU carrying the first message is a BSS color of the first basic service set.

[0089] As one embodiment, the PPDU carrying the first message is a non-HT (high throughput) PPDU.

[0090] As one embodiment, a TA (transmission address) field of the first message is a MAC address of the second node; wherein a value of Individual / Group bit is 0.

[0091] As one embodiment, the PPDU carrying the first message is a non-HT duplicate PPDU.

[0092] As one embodiment, the TA field of the first message is a bandwidth signaling TA of the second node; wherein the value of Individual / Group bit is 1.

[0093] As one embodiment, a TXVECTOR (Transmit Vector) parameter CH_BANDWIDTH_IN_NON_HT of the PPDU carrying the first message is used to modify the first 7 bits of the scrambling sequence to indicate the bandwidth of the PPDU carrying the first message.

[0094] As one embodiment, a TXVECTOR parameter FORMAT of the PPDU carrying the first message is NOT_HT, and a TXVECTOR parameter NON_HT_MODULATION is NON_HT_DUP_OFDM.

[0095] As one embodiment, a bandwidth signaling TA included in the first message indicates the channel bandwidth occupied by the first transmission opportunity.

[0096] As one embodiment, the PPDU carrying the first message is a HE (high efficiency) TB (trigger-based) PPDU.

[0097] As an embodiment, the PPDU carrying the first message is an EHT (extremely high throughput) MU PPDU.

[0098] As an embodiment, the PPDU carrying the first message is an EHT TB PPDU.

[0099] As an embodiment, the PPDU carrying the first message is a UHR PPDU.

[0100] As an embodiment, the TA field of the first message is a transmitted BSSID.

[0101] As an embodiment, an uplink bandwidth subfield in a general information field included in the first message indicates a bandwidth of the PPDU carrying the first message.

[0102] As an embodiment, an uplink bandwidth subfield in a general information field included in the first message indicates a channel bandwidth occupied by the first transmission opportunity.

[0103] As an embodiment, the first message includes a Duration field, which indicates a duration of the first transmission opportunity.

[0104] As an embodiment, a value of the Duration field included in the first message is set to a time, in microseconds, required for transmitting pending data or management frames, plus a CTS frame, plus an Ack or BlockAck frame, plus appropriate IFSs (interframe spaces), rounded up.

[0105] As an embodiment, the appropriate IFSs include at least one or more SIFSs (short IFSs).

[0106] As a sub-embodiment of the above embodiment, the value of the Duration field included in the first message can be added with a time required for transmitting any NDP (null data PPDU) and explicit feedback of the NDP, if needed.

[0107] As a sub-embodiment of the above embodiment, the value of the Duration field included in the first message can be added with a time required for transmitting the requested HE TB PPDU and a time required for transmitting explicit Ack or feedback of the requested HE TB PPDU, if needed.

[0108] As a sub-embodiment of the above-mentioned embodiment, the value of the duration field included in the first message can be reduced by the time required for transmitting the CTS frame and a SIFS.

[0109] As a sub-embodiment of the above-mentioned embodiment, the value of the duration field included in the first message can be reduced by the time required for transmitting an Ack or BlockAck frame and a SIFS.

[0110] As an embodiment, the first node performs an update-NAV operation at the moment of receiving the end of the PPDU carrying the first message.

[0111] As an embodiment, the first node updates the NAV according to the value of the duration field included in the first message.

[0112] As an embodiment, the first node updates the NAV according to the duration information indicated by the RXVECTOR parameter TXOP_DURATION of the PPDU carrying the first message.

[0113] As an embodiment, the RA field included in the first message is the MAC address of the second node; wherein the first message is a CTS-to-self frame sent by the second node.

[0114] As an embodiment, the RA field included in the first message is the MAC address of a third node; wherein the third node is a node other than the first node and the second node associated with the first basic service set.

[0115] As a sub-embodiment of the above-mentioned embodiment, the first message is an RTS sent by the second node to the third node.

[0116] As a sub-embodiment of the above-mentioned embodiment, the first message is a CTS response to an RTS frame or a MU-RTS trigger frame of the third node by the second node.

[0117] As an embodiment, the RA (receiver address) field included in the first message is a broadcast address.

[0118] As an embodiment, the condition for the first node to update the NAV includes that the RA field of the first message is the MAC address of any node other than the first node.

[0119] As an embodiment, the condition under which the first node updates the NAV comprises: none of the values of the AID 12 subfield of any of the user info fields included in the first message is equal to the 12 LSBs of the AID (association identifier) of the first node; wherein the user info field is not a Special user info field.

[0120] As an embodiment, the condition under which the first node updates the NAV further comprises: the value of the duration field included in the first message is greater than the value of the NAV timer of the first node.

[0121] As an embodiment, the condition under which the first node updates the NAV further comprises: the value indicated by the RXVECTOR parameter TXOP_DURATION of the PPDU carrying the first message is greater than the value of the NAV timer of the first node.

[0122] As an embodiment, the condition under which the first node updates the NAV further comprises: the MAC layer of the first node does not receive a PHY-RXSTART.indication primitive within a NAV Timeout time after the end of the reception of the PPDU carrying the first message.

[0123] As an embodiment, the NAV timer of the first node is set to the value of the duration field included in the first message.

[0124] As an embodiment, the NAV timer of the first node is set to the value indicated by the RXVECTOR parameter TXOP_DURATION of the PPDU carrying the first message.

[0125] As an embodiment, for the first node, the PPDU carrying the first message is an intra-BSS PPDU.

[0126] As an embodiment, the first node only updates an intra-BSS NAV timer.

[0127] As an embodiment, the condition under which the first node updates the NAV further comprises: the value of the duration field included in the first message is greater than the value of the intra-BSS NAV timer of the first node.

[0128] As an embodiment, the condition under which the first node updates the NAV further comprises: a value indicated by a TXOP_DURATION field of a RXVECTOR parameter of the PPDU carrying the first message is greater than a value of an intra-BSS NAV timer of the first node.

[0129] As an embodiment, the first node does not perform the operation of updating the NAV when a RA field included in the first message is a MAC address of the first node.

[0130] As an embodiment, the first node does not perform the operation of updating the NAV when a value of an AID 12 subfield of one of User Info fields included in the first message is equal to 12 LSBs of an AID of the first node.

[0131] As an embodiment, the second message is a control frame.

[0132] As an embodiment, the second message is a CF-End (contention free-end) frame.

[0133] As an embodiment, the second message is a trigger frame; a value of a trigger type subfield in Common Info of the second message is between 8 and 15.

[0134] As an embodiment, the second message is transmitted at least on the first channel.

[0135] As an embodiment, the second message is transmitted on the same channel as the first message.

[0136] As an embodiment, the PPDU carrying the second message is a non-HT PPDU.

[0137] As an embodiment, the PPDU carrying the second message is a non-HT duplicate PPDU.

[0138] As an embodiment, the PPDU carrying the second message and the PPDU carrying the first message have the same value of a CH_BANDWIDTH_IN_NON_HT parameter of a TXVECTOR.

[0139] As an embodiment, a value of a FORMAT parameter of a TXVECTOR of the PPDU carrying the second message is NOT_HT, and a value of a NON_HT_MODULATION parameter of the TXVECTOR is NON_HT_DUP_OFDM.

[0140] As an embodiment, the second message includes a duration field with a value of 0.

[0141] As one embodiment, the RA field included in the second message is a broadcast address.

[0142] As one embodiment, the BSSID (TA) field included in the second message is the BSSID of the first basic service set.

[0143] As one embodiment, the BSSID associated with the first node matches the BSSID of the BSSID (TA) field included in the second message.

[0144] As one embodiment, the individual / group bit of the BSSID (TA) field included in the second message is 1.

[0145] As one embodiment, the RXVECTOR parameter BSS_COLOR of the PPDU carrying the first message is the BSS color of the first basic service set.

[0146] As one embodiment, the PPDU carrying the first message is an intra-BSS PPDU for the first node.

[0147] As one embodiment, the second message indicates that the first transmission opportunity is truncated.

[0148] As one embodiment, the second message indicates that the use of at least the first channel is released.

[0149] As one embodiment, the second message indicates that the first transmission opportunity ends at the second time.

[0150] As one embodiment, the second message indicates that the first node resets the NAV at the second time.

[0151] As one embodiment, the first node resets the value of a maintained NAV timer to 0 at the second time.

[0152] As one embodiment, the first node resets the value of an intra-BSS NAV timer to 0 at the second time.

[0153] As one embodiment, the message type of the third message is a control frame.

[0154] As one embodiment, the third message is an RTS frame.

[0155] As one embodiment, the third message is a trigger frame.

[0156] As a sub-example of the above embodiment, the third message is a MU-RTS trigger frame, and a value of a trigger type subfield in a general information field of the third message is 3.

[0157] As a sub-example of the above embodiment, the first message is not a MU-RTS TXS frame.

[0158] As an example, the third message indicates a channel bandwidth occupied by the second transmission opportunity.

[0159] As an example, the channel bandwidth occupied by the second transmission opportunity includes one or more contiguous 20MHz channels.

[0160] As an example, the channel bandwidth occupied by the second transmission opportunity is in a sub-7GHz (sub-7 gigahertz) frequency band.

[0161] As a sub-example of the above embodiment, the channel bandwidth occupied by the second transmission opportunity is in a 2.4GHz frequency band.

[0162] As a sub-example of the above embodiment, the channel bandwidth occupied by the second transmission opportunity is in a 5GHz frequency band.

[0163] As a sub-example of the above embodiment, the channel bandwidth occupied by the second transmission opportunity is in a 6GHz frequency band.

[0164] As an example, the channel bandwidth occupied by the second transmission opportunity is one of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, and a primary 320MHz channel of the first basic service set.

[0165] As an example, the channel bandwidth occupied by the second transmission opportunity includes non-contiguous channels.

[0166] As an example, the channel bandwidth occupied by the second transmission opportunity includes a secondary channel of the first basic service set.

[0167] As an example, the channel bandwidth occupied by the second transmission opportunity is a primary 20MHz channel and a secondary 40MHz channel of the first basic service set.

[0168] As an example, the channel bandwidth occupied by the second transmission opportunity is a primary 40MHz channel and a secondary 80MHz channel of the first basic service set.

[0169] As an example, the channel bandwidth occupied by the second transmission opportunity is a primary 80MHz channel and a secondary 160MHz channel of the first basic service set.

[0170] As one embodiment, the channel bandwidth occupied by the second transmission opportunity at least partially overlaps the channel bandwidth occupied by the first transmission opportunity.

[0171] As one embodiment, the channel bandwidth occupied by the second transmission opportunity and the channel bandwidth occupied by the first transmission opportunity both include the first channel.

[0172] As one embodiment, the second transmission opportunity includes at least the transmission opportunity of the first node on the first channel.

[0173] As one embodiment, the RXVECTOR parameter BSS_COLOR of the PPDU carrying the third message is the BSS color of the first basic service set.

[0174] As one embodiment, the PPDU carrying the third message is a non-HT PPDU.

[0175] As one embodiment, the TA field of the third message is the MAC address of the first node; wherein the value of the individual / group bit is 0.

[0176] As one embodiment, the PPDU carrying the third message is a non-HT duplicate PPDU.

[0177] As one embodiment, the TA field of the third message is the bandwidth signaling TA of the first node; wherein the value of the individual / group bit is 1.

[0178] As one embodiment, the TXVECTOR parameter CH_BANDWIDTH_IN_NON_HT of the PPDU carrying the third message is used to modify the first 7-bit of the scrambling sequence to indicate the bandwidth of the PPDU carrying the third message.

[0179] As one embodiment, the TXVECTOR parameter FORMAT of the PPDU carrying the third message is NOT_HT, and the TXVECTOR parameter NON_HT_MODULATION is NON_HT_DUP_OFDM.

[0180] As one embodiment, the bandwidth signaling TA included in the third message indicates the channel bandwidth occupied by the second transmission opportunity.

[0181] As one embodiment, the PPDU carrying the third message is one of HE TB PPDU, EHT MU PPDU, EHT TB PPDU, UHR PPDU.

[0182] As an embodiment, the TA field of the third message is a transmitted BSSID.

[0183] As an embodiment, an uplink bandwidth subfield in a general information field included in the third message indicates a bandwidth of a PPDU carrying the third message.

[0184] As an embodiment, an uplink bandwidth subfield in a general information field included in the third message indicates a channel bandwidth occupied by the second transmission opportunity.

[0185] As an embodiment, the first node transmits the third message after the second time.

[0186] As an embodiment, the first node transmits the third message after determining that the first channel is idle.

[0187] As an embodiment, the first node transmits the third message after successfully contending for the first channel.

[0188] As an embodiment, the first node contends for the first channel based on DCF (distributed coordination function).

[0189] As an embodiment, the first node contends for the first channel based on EDCA (enhanced distributed channel access).

[0190] As an embodiment, the first node transmits the third message after a first EDCAF (EDCA function) included in the first node successfully contends for the first channel.

[0191] As an embodiment, at least one transmission queue associated with a first access category (AC) has MSDU (MAC service data unit) to transmit; wherein the first access category is an access category associated with the first EDCAF.

[0192] As an embodiment, an amount of data to be transmitted by the first node is at least greater than an RTS threshold (dot11RTSThreshold).

[0193] As an embodiment, the first node determines whether the first channel is idle based on physical carrier sensing and virtual carrier sensing.

[0194] As an embodiment, the first node determines whether the first channel is idle by CCA (clear channel assessment) and NAV state.

[0195] As an embodiment, the first node determines that the first channel is idle by energy detection (ED) finding that the received signal strength is less than a first sensitivity threshold; or by signal detection (SD) finding that the received signal strength is less than a second sensitivity threshold.

[0196] As an embodiment, the first sensitivity threshold and the second sensitivity threshold are predefined; the first sensitivity threshold is greater than the second sensitivity threshold.

[0197] As an embodiment, the first sensitivity threshold is -82 dBm, and the second sensitivity threshold is -62 dBm.

[0198] As an embodiment, the first sensitivity threshold and the second sensitivity threshold are related to the first channel.

[0199] As an embodiment, the first sensitivity threshold and the second sensitivity threshold are referred to the CCA sensitivity section of the protocol 802.11b / g / a, 802.11n, 802.11ac, 802.11ax, 802.11be PHY.

[0200] As an embodiment, the first node determines that the first channel is idle when the BSS color of the received signal is different from the BSS color associated with the first node, and the received signal strength is less than a third sensitivity threshold.

[0201] As an embodiment, the third sensitivity threshold is adaptive, and the third sensitivity threshold is between the first sensitivity threshold and the second sensitivity threshold.

[0202] As an embodiment, the third sensitivity threshold is used for OBSS_PD (OBSS packet detection).

[0203] As an embodiment, the first node supports spatial reuse operation based on OBSS_PD.

[0204] As an embodiment, the third sensitivity threshold is referred to the section 26.10.2 of the protocol 802.11ax and 802.11be.

[0205] As one embodiment, the first node detects the first channel for a first waiting time after the second time, and confirms that the first channel remains idle.

[0206] As one embodiment, the first waiting time is one of DIFS (distributed IFS), EIFS (extended IFS), PIFS (priority IFS), and AIFS[AC] (arbitration IFS).

[0207] As one embodiment, the length of the AIFS[AC] is associated with an AIFSN (arbitration interframe space number) [AC].

[0208] As one embodiment, both the length of the AIFS[AC] and the value of the AIFSN[AC] are associated with the first access category.

[0209] As one embodiment, the first access category is one of VO (voice), VI (video), BE (best effort), and BK (background).

[0210] As one embodiment, the candidates of the first access category further include A_VO (Alternate_VO) and A_VI (Alternate_VI).

[0211] As one embodiment, the value of the first access category depends on the service type of the data to be transmitted.

[0212] As one embodiment, the AIFS[AC] is equal to AIFSN[AC]×aSlotTime+aSIFSTime.

[0213] As one embodiment, the value of the AIFSN[AC] is an integer greater than or equal to 1.

[0214] As one embodiment, the value of the AIFSN[AC] is one of {1, 2, 3, 7}.

[0215] As one embodiment, the first waiting time is EIFS-DIFS+AIFS[AC].

[0216] As an embodiment, the first waiting time is AIFSN[AC] x aSlotTime - aRxTxTurnaroundTime.

[0217] As an embodiment, the first waiting time is EIFS - DIFS + AIFS[AC] - aRxTxTurnaroundTime.

[0218] As an embodiment, the definitions and values of the parameters aSlotTime, aSIFSTime, aRxTxTurnaroundTime depend on the protocol version supported by the first node and its device capability, referring to 802.11 protocol in particular.

[0219] As an embodiment, the starting time of the first waiting time is the second time.

[0220] As an embodiment, the starting time of the first waiting time is later than the second time.

[0221] As an embodiment, the first node, or the first EDCAF, starts or restarts a backoff counter at the ending time of the first waiting time.

[0222] As an embodiment, at the ending time of the first waiting time, the values of all NAV timers maintained by the first node are zero.

[0223] As an embodiment, at the ending time of the first waiting time, the values of the basic NAV timer and the BSS internal NAV timer of the first node are both zero.

[0224] As an embodiment, at the ending time of the first waiting time, the value of the TXNAV timer maintained by the first EDCAF is zero.

[0225] As an embodiment, the value of the backoff counter is set to an integer, which is selected randomly from a uniform distribution and has a value ranging from 0 to CW (contention window).

[0226] As an embodiment, the value of the backoff counter is decremented by one each time a channel is detected to be idle in a backoff slot.

[0227] As an embodiment, the value of the CW is related to the first access category associated with the first EDCAF.

[0228] As an embodiment, the value of the CW is related to the number of times the first node fails to contend for the channel.

[0229] As one embodiment, the first node transmits the third message when the value of the backoff counter decreases to zero.

[0230] As one embodiment, the third message is transmitted on the first channel.

[0231] As one embodiment, the third message is transmitted on a channel other than the first channel.

[0232] As one embodiment, the condition for the third message to be transmitted on a channel other than the first channel includes that at least one secondary channel other than the first channel remains idle during a DIFS period before the third message is transmitted.

[0233] As one embodiment, the condition for the third message to be transmitted on a channel other than the first channel includes that at least one secondary channel other than the first channel remains idle during a PIFS period before the third message is transmitted.

[0234] As one embodiment, the third message is transmitted only if the second time is earlier than the first time by more than a first threshold.

[0235] As one embodiment, the first threshold is predefined.

[0236] As one embodiment, the first threshold is indicated by an AP to which the first node is associated.

[0237] As one embodiment, the fourth message indicates the first threshold.

[0238] As one embodiment, the first threshold is used to decide whether to contend for a transmission opportunity on the first channel before the first time.

[0239] As one embodiment, the first threshold is at least greater than a time required to transmit the third message, plus a time required to receive a response to the third message, plus a time required to receive an acknowledgement of a data frame transmitted in the second transmission opportunity, if needed, and appropriate IFSs.

[0240] As one embodiment, the third message includes a duration field indicating a duration of the second transmission opportunity.

[0241] As one embodiment, a value of the duration field of the third message is set to a time, in microseconds, between an end time of a PPDU carrying the third message and the first time, rounded up.

[0242] As one embodiment, a transmission time required for the first node to transmit data is greater than a time available for data transmission in the second transmission opportunity.

[0243] As one embodiment, the time in the second transmission opportunity that can be used for data transmission is at most the value of the duration field of the third message minus the time needed to transmit the response to the third message, minus the time needed to transmit the acknowledgement of the data frame in the second transmission opportunity if needed, minus suitable IFSs.

[0244] As one embodiment, the first node can only transmit part of the pending data in the second transmission opportunity.

[0245] As one embodiment, the first node contends for the channel again after the first time instant and transmits the remaining part of the pending data.

[0246] As one embodiment, the first node transmits a plurality of MSDUs in the second transmission opportunity.

[0247] As one embodiment, the plurality of MSDUs is at least part of all MSDUs comprised in the pending data of the first node.

[0248] As one embodiment, the part of MSDUs with higher priority among the all MSDUs is transmitted in the second transmission opportunity.

[0249] As one embodiment, at least one of the plurality of MSDUs transmitted in the second transmission opportunity is in the transmission queue of the first access category.

[0250] As one embodiment, all of the plurality of MSDUs transmitted in the second transmission opportunity are in the transmission queue of the first access category.

[0251] As one embodiment, the plurality of MSDUs transmitted in the second transmission opportunity comprises all MSDUs in the transmission queue of the first access category and part of MSDUs in the transmission queue of part of other access categories.

[0252] As one embodiment, the non-primary channel access refers to the operation that the 802.11 node switches from the primary channel to the secondary channel to perform channel access when the 802.11 node detects the OBSS TXOP on the primary channel.

[0253] As one embodiment, the non-primary channel access further comprises the operation that the 802.11 node switches back from the secondary channel to the primary channel at the end of the OBSS TXOP on the primary channel.

[0254] Although the above operation is referred to as non-primary channel access in this application, the term "non-primary channel access" can be replaced by other names including "secondary channel access" without changing the behavior of the above operation.

[0255] As an embodiment, the fourth node receives the first message, or receives a response to the first message, triggering the non-primary channel access.

[0256] As an embodiment, the fourth node is a node in a second basic service set; wherein the second basic service set is an adjacent basic service set to the first basic service set, and a primary channel of the second basic service set is the first channel.

[0257] As an embodiment, a basic service area (BSA) of the first basic service set and a basic service area of the second basic service set at least partially overlap.

[0258] As an embodiment, the fourth node is located in an overlapping service area of the first basic service set and the second basic service set.

[0259] As an embodiment, for the fourth node, the first basic service set is an OBSS.

[0260] As an embodiment, the fourth node switches to a third channel, and switches back to the first channel at the first time.

[0261] As an embodiment, the third channel is a secondary channel of the second basic service set.

[0262] As an embodiment, the third channel is one of {secondary 20MHz channel, secondary 40MHz channel, secondary 80MHz channel, secondary 160MHz channel, secondary 320MHz channel} of the second basic service set.

[0263] As an embodiment, the third channel has the same bandwidth as the first channel.

[0264] As an embodiment, none of the channels on which the first message, the second message and the third message are sent includes the third channel.

[0265] As an embodiment, none of the channel bandwidths occupied by the first transmission opportunity and the second transmission opportunity includes the third channel.

[0266] As an embodiment, the third channel is indicated by an AP of the second basic service set.

[0267] As one embodiment, the third channel is negotiated by the AP of the first basic service set and the AP of the second basic service set.

[0268] As one embodiment, the third channel is negotiated by the second node and the fourth node.

[0269] As one embodiment, the first receiver receives a fourth message on the first channel, the fourth message indicating to perform non-primary channel access coordination.

[0270] As one embodiment, the non-primary channel access coordination means that the nodes of the second basic service set consider triggering non-primary channel access due to the first transmission opportunity; the second transmission opportunity initiated by the first node ends at the first time point when the first transmission opportunity is truncated; wherein the transmission time required by the data to be transmitted by the first node is greater than the time that can be used for data transmission in the second transmission opportunity.

[0271] As one embodiment, the first channel is idle at least partially after the first time point.

[0272] As one embodiment, the first channel is idle at least SIFS+aSlotTime after the first time point.

[0273] As one embodiment, the above method has the advantage that the fairness of the nodes of the OBSS in competing for the first channel when switching back to the first channel at the first time point after triggering non-primary channel access can be ensured.

[0274] Embodiment 2

[0275] Figure 2 illustrates the architecture of an IEEE 802.11 local area network. A basic service set (BSS) is the basic building block of an IEEE 802.11 local area network, consisting of a group of terminals that can communicate with each other. A BSS includes an independent BSS (IBSS) and an infrastructure BSS; in an IBSS, the terminals can communicate directly with each other, and in an infrastructure BSS, the terminals communicate with each other through association with a central terminal, also referred to as an access point. An infrastructure BSS can be interconnected with other infrastructure BSSs through an access point via a distribution system (DS), and a plurality of infrastructure BSSs interconnected via a DS can form an extended service set (ESS) to extend the coverage area of the network. As shown, BSS 231 is an IBSS, including terminal 201 and terminal 202 that can communicate directly with each other. As shown, BSS 232 and BSS 233 are infrastructure BSSs, and communication between terminals in an infrastructure BSS is relayed through an access point, e.g., terminal 203 in BSS 232 needs to send data to terminal 204 in BSS 232, first sends the data to access point 211, which then relays the data to terminal 204; the reverse is also true. As shown, BSS 232 and BSS 233 form ESS 234, and access points 211 and 212 in the same ESS 234 use the same service set identifier (SSID), and BSS 232 and BSS 233 are typically overlapping. Terminals belonging to the same ESS 234 can communicate with each other, e.g., terminal 203 in BSS 232 can communicate with terminal 205 in BSS 233, and in this case, access points 211 and 212 have bridging functionality to transfer data between different access points via a distribution system medium (DSM).

[0276] A BSS can be identified to user terminals by a SSID and to other devices by a Basic SSID (BSSID), which can be the MAC (Medium Access Control) address of the access point 211. The access point 211 periodically broadcasts beacon frames including the BSSID to enable any terminal within the wireless coverage of the access point 211 to associate or re-associate with the access point 211 to establish a respective downlink 223 and uplink 224 (uplink and downlink can be collectively referred to as a Wi-Fi link) with the access point 211. The beacon can include an identification of the primary channel used by the respective access point 211 and a timing synchronization function for establishing or maintaining timing synchronization with the access point 211.

[0277] A terminal is a logical entity of a MAC single addressable instance and a physical layer (PHY) interface facing the wireless medium (WM). In IEEE 802.11, a terminal is an addressable unit, which in IBSS can transmit beacon frames to announce the presence of a WLAN. In infrastructure basic service set, to establish a Wi-Fi link with an access point 211, a terminal 203 is configured to perform passive or active scanning on frequency channels in one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz bands). To perform passive scanning, a terminal 203 listens for beacons periodically transmitted by a respective access point 211. To perform active scanning, a terminal 203 generates probe requests and transmits these probe requests sequentially on each channel to be scanned, and listens for probe responses from access points 211. A terminal 203 identifies or selects an access point 211 to associate with by scan information obtained through passive or active scanning, and performs authentication and association operations to establish a communication link with the selected access point 211. An access point 211 assigns an association identifier (AID) to a terminal 203 at the end of the association operation, which the access point 211 uses to track the terminal 203. A terminal includes, but is not limited to, a mobile phone, a laptop computer, a personal digital assistant (PDA), a media device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, a flying vehicle, a narrowband Internet of Things device, a machine type communication device, a land vehicle, a car, an in-vehicle device, an in-vehicle communication unit, a wearable device, or any other similar functional device. A terminal can also be referred to by those skilled in the art as a non-AP station, a non-AP multi-link device (MLD), a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0278] An access point is an entity that includes terminals and provides access to a distribution system, DS, for associated terminals over a wireless medium, WM, and includes terminal and distribution system access functions, DSAF. An access point can be referred to as an AP multi-link device (AP MLD), a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (Transmission Reception Point), or some other suitable terminology. An access point can provide access to an external network for terminals in a WLAN via respective WiFi links.

[0279] A distribution system, DS, is a backbone network that transports data between access points, often referred to as a backbone network, which is typically Ethernet. An access point provides a uniform interface to upper layers, such as an IP (Internet Protocol) layer, through a logical link control (LLC) layer. IP packets for all users are transported through a gateway (GW), which provides IP address allocation for terminals within the respective network segment and other functions, and is also referred to as an IP router. The gateway is connected to an Internet service 230. The Internet service 230 includes operator corresponding Internet protocol services, which can include the Internet, an intranet, an IMS (IP Multimedia Subsystem), and a PS (Packet Switching) streaming service.

[0280] As an embodiment, the terminal 201 corresponds to a first node in the present application, and the terminal 202 corresponds to a second node in the present application.

[0281] As an embodiment, the access point 211 corresponds to a first node in the present application, and the terminal 203 corresponds to a second node in the present application.

[0282] As an embodiment, the access point 211 and the terminals 201, 202, 203 all support WiFi.

[0283] As an embodiment, the access point 211 and the terminals 201, 202, 203 all support the 802.11 protocol.

[0284] As an embodiment, the access point 211 and the terminals 201, 202, 203 are one of DMG (Directional Multi-Gigabit) devices, EDMG (enhanced directional multi-gigabit) devices, CDMG (China directional multi-gigabit) devices, CMMG (China millimeter-wave multi-gigabit) devices, S1G devices, HE (High Efficiency) devices, EHT (Extreme High Throughput) devices, UHR (Ultra High Reliability) devices.

[0285] As an embodiment, the access point 211 is an AP.

[0286] As an embodiment, the access point 211 is an MLD (multi-link device).

[0287] As an embodiment, the access point 211 is a base station.

[0288] As an embodiment, the access point 211 is a Femtocell.

[0289] As an embodiment, the access point 211 is a router.

[0290] As an embodiment, the access point 211 is a test equipment (e.g. a transceiver simulating part of the functionality of a base station, a signaling tester).

[0291] As an embodiment, the access point 211 is a vehicle mounted equipment.

[0292] As an embodiment, the terminal 201 is an MLD.

[0293] As an embodiment, the terminals 202, 203 are not MLDs.

[0294] As an embodiment, the terminal 201 is an AP.

[0295] As an embodiment, the terminal 202 is a relay device.

[0296] As an embodiment, the terminals 201, 202, 203 are mobile phones.

[0297] As an embodiment, the terminals 201, 202, 203 are consumer electronics such as smart watches.

[0298] As one embodiment, the terminals 201, 202, 203 are vehicles including cars.

[0299] As one embodiment, the wireless link from the terminal 201 to the terminal 202 is a downlink 222, the terminal 201 is a source terminal, the terminal 202 is a destination terminal, and the downlink 222 is used to perform downlink transmission.

[0300] As one embodiment, the wireless link from the terminal 202 to the terminal 201 is an uplink 221, the terminal 202 is a source terminal, the terminal 201 is a destination terminal, and the uplink 221 is used to perform uplink transmission.

[0301] As one embodiment, the wireless link from the access point 211 to the terminal 203 is a downlink 223, and the downlink 223 is used to perform downlink transmission.

[0302] As one embodiment, the wireless link from the terminal 203 to the access point 211 is an uplink 224, and the uplink 224 is used to perform uplink transmission.

[0303] As one embodiment, the sender of the first message includes the access point 211 or the terminal 201.

[0304] As one embodiment, the receiver of the first message includes the terminal 203 or the terminal 202.

[0305] Embodiment 3

[0306] Embodiment 3 illustrates a diagram of a wireless protocol stack according to one embodiment of the application, as shown in FIG. 3. IEEE 802.11 employs a CSMA / CA (carrier sense multiple access / collision avoidance) protocol to control access to the transmission medium. FIG. 3 shows the wireless protocol architecture in two layers: the data link layer and the physical layer, where the physical layer is the lowest layer and implements various physical layer signal processing functions, which will be referred to herein as PHY 301. The data link layer is above the physical layer and is responsible for the link between terminals and terminals, or between terminals and access points, and includes a MAC 302. The MAC 302 cooperates with the PHY 301 to accomplish data transmission and various management services.

[0307] The MAC 302 is responsible for encapsulating MSDUs (MAC service data units) into MPDUs (MAC protocol data units) frames, delimiting the frames, implementing frame synchronization, processing destination and source MAC addresses, and handling frames in case of transmission errors. For data frames or some larger management packets from upper layers, it implements packet fragmentation and defragmentation, and performs integrity protection and cryptographic encapsulation for data that needs protection. The PHY 301 is divided into two sub-layers: the Physical Layer Convergence Procedure (PLCP) sub-layer and the Physical Medium Dependent (PMD) sub-layer. Frames received from the MAC 302 are processed in the PLCP sub-layer to add a PHY header to generate a PPDU (PHY protocol data unit), which typically contains a preamble and a PHY header to assist in synchronization of the received data and demodulation of the MPDU. The PMD is then responsible for encoding and modulating the MPDU for transmission over the air using an antenna.

[0308] The MAC 302 implements access control, if based on CSMA / CA, governed by the distributed coordination function (DCF), if contention-free service is required, governed by the point coordination function (PCF) built on top of the DCF. Between the DCF and the PCF, the hybrid coordination function (HCF) can also be used. In the DCF, the medium is checked for availability by carrier sensing, the physical carrier sensing function is provided by the PHY 301, the virtual carrier sensing function is provided by the network allocation vector (NAV). To ensure medium access and data transmission, the exchange of RTS (request to send) and CTS (clear to send) can be used. The IEEE 802.11 frame usually contains a duration field to reserve medium access time. Before attempting to transmit any data, the medium must be checked for idle. If busy, access must be delayed and the backoff algorithm used to avoid collision. If the medium is idle for longer than the DIFS (distributed interframe space), transmission can be performed immediately. In the PCF, when the access point takes over the wireless medium, it polls the terminals connected to it according to the polling list to see if they have data to transmit. During the contention-free period, the terminals cannot transmit data unless the access point requests them to do so with a polling frame. The MAC 302 can include error recovery, i.e. the sender is responsible for retransmission if no acknowledgement (ACK) is received for each frame sent. The MAC 302 can provide priority for delay-sensitive services, in the case of a single transmission queue, the delay-sensitive service data frames are placed at the front of the queue, in the case of multiple transmission queues, a queue is dedicated to the transmission of high-priority delay-sensitive services. To save energy, the terminal can enter a sleep state periodically. In the sleep state, the access point stores frames for each terminal in the sleep state. If there are stored frames, the access point informs the terminal in the subsequent Beacon frame, and the terminal awakened from the sleep state can use the PS (power save)-Poll frame to obtain the stored frames. The management functions of the MAC 302 also include channel management, connection management, quality of service, power control, security management, and time synchronization.Among other things, the channel management includes channel scanning, channel measurement, and channel switching; the connection management includes user authentication, association, re-association, dis-association, and point-to-point connection; the quality of service includes QoS traffic scheduling and traffic flow management; the power management includes transmission power management and adaptive transmission power control; the security management includes key generation and distribution; and the time synchronization includes high layer synchronization support. Although not shown, the terminal can also have several upper layers above the MAC 302, including an LLC layer.

[0309] As an example, the wireless protocol architecture in FIG. 3 is applicable to the first node in the present application.

[0310] As an example, the wireless protocol architecture in FIG. 3 is applicable to the second node in the present application.

[0311] Embodiment 4

[0312] Embodiment 4 illustrates a hardware module diagram of a communication device according to an embodiment of the present application, as shown in FIG. 4. FIG. 4 is a block diagram of a first communication device 450 and a second communication device 410 that communicate with each other in an access network.

[0313] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454, and an antenna 452.

[0314] The second communication device 410 includes a controller / processor 475, a memory 476, a data source 477, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter / receiver 418, and an antenna 420.

[0315] The third communication device 490 includes a control component 491, an information component 496, a memory 495, and a reflecting surface 492.

[0316] In transmissions from the second communication device 410 to the first communication device 450, upper layer data frames from the Internet or upper layer data frames from a data source 477 are provided to a controller / processor 475 at the second communication device 410. The Internet and data source 477 represent all protocol layers above the MAC layer. The controller / processor 475 implements the functionality of the MAC layer. In transmissions from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, ciphering, packet segmentation and reordering, mapping between traffic and links, and radio resource allocation to the first communication device 450. The controller / processor 475 is also responsible for retransmission of lost packets, and signaling to the first communication device 450. A transmit processor 416 and a multi-antenna transmit processor 471 implement various signal processing functions for the PHY layer (i.e., physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of coded bits to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding and beamforming of the coded and modulated symbols, generating one or more spatial streams. The transmit processor 416 then maps to each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots), in the time and / or frequency domain, and then performs an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, which is then provided to a respective antenna 420.

[0317] In transmissions from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its respective antenna 452. Each receiver 454 recovers information modulated onto an RF carrier and provides the recovered information at baseband, as a stream of symbols, to a receive processor 456. The receive processor 456 and a multiple access receiver processor 458 implement various signal processing functions of the PHY layer. The multiple access receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multiple access symbol stream from the receivers 454. The receive processor 456 converts the baseband multiple access symbol stream from the multiple access receiver processor 458 from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals are demultiplexed from the received symbol stream by the receive processor 456, with the reference signals to be used for channel estimation and the data signals to be recovered after multi-antenna detection in the multiple access receiver processor 458 for any spatial streams that are destined to or received by the first communication device 450. The symbols on each spatial stream are demodulated and recovered by the receive processor 456 and generate soft decisions. The receive processor 456 then decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channels. The upper layer data and control signals are then provided to a controller / processor 459. The controller / processor 459 implements the functions of the MAC layer. The controller / processor 459 can be associated with a memory 460 that stores program codes and data. The memory 460 can be referred to as a computer-readable medium. In transmissions from the second communication device 410 to the first communication device 450, the controller / processor 459 provides packet de-assembly, deciphering, header decompression, control signal processing to recover upper layer data frames from the second communication device 410. The upper layer data frames are then provided to all protocol layers above the MAC layer.

[0318] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 provides upper layer data frames to a controller / processor 459 using. The data source 467 represents all protocol layers above the MAC layer. Similar to the transmit function described at the second communication device 410 in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, ciphering, packet segmentation and reordering, and mapping between traffic and links. The controller / processor 459 is also responsible for retransmission of lost packets, and signaling to the second communication device 410. A transmit processor 468 performs modulation mapping, channel coding processing, and a multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding and beamforming processing, and then the transmit processor 468 modulates the resulting spatial streams into multi-carrier symbol streams, which are provided to different antennas 452 via transmitters 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol streams provided by the multi-antenna transmit processor 457 into radio frequency symbol streams, and then provides the radio frequency symbol streams to the antennas 452.

[0319] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the receive functions described at the first communication device 450 in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functions of the PHY layer. A controller / processor 475 implements the functions of the MAC layer. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides packet reassembly, deciphering, header decompression, control signal processing to recover upper layer data frames from the first communication device 450. The upper layer data frames from the controller / processor 475 can be provided to the Internet or all protocol layers above the MAC layer.

[0320] The third communication device 490 can be controlled by the first communication device 410 and / or the second communication device 450 to alter channel realization in a controlled manner, improve channel diversity, provide robustness to channel blockage / fading, which can be referred to as a control node for the third communication device 490. At least one of the transmit processor 416, receive processor 470, and controller / processor 475 of the first communication device 410 can be configured to perform aspects in connection with the information component 496 or controller component 491 of the third communication device 490, or at least one of the transmit processor 468, receive processor 456, and controller / processor 459 of the second communication device 450 can be configured to perform aspects in connection with the information component 496 or controller component 491 of the third communication device 490.

[0321] The first communication device 410 and / or the second communication device 450 use the third communication device 490 for communication, sensing, and / or positioning functions. Information of the third communication device 490 can be known by the network based on network planning, and a base station can provide the location and other information of the third communication device 490 to other nodes (e.g., terminals in a cell). For example, a base station can transmit information of the third communication device 490 in system information. Terminals in the coverage of a cell can receive system information to discover the existence, location, capability, or other information about the third communication device 490.

[0322] In transmissions where the first communication device 410 and / or the second communication device 450 use the third communication device 490 for communication, at the third communication device 490, multiple resonant elements make up a reflecting surface 492 that receives downlink signals from the first communication device 410 or uplink signals from the second communication device 450, and each resonant element can adjust (e.g., apply a phase shift to directionally reflect the received signal) the respective received signal. The control component 491 can configure the phase or amplitude changes by applying precoding weights to each resonant element to enable the third communication device 490 to re-radiate an output beam in a different direction given a particular input beam.

[0323] In some cases, when the third communication device 490 operates passively to only reflect or refract beams from a transmitter to a receiver, the third communication device 490 can operate as a near passive device without substantial power consumption. In some cases, the direction of reflection or refraction can be controlled by a control node or network controller.

[0324] In transmission from the control node and the third communication device 490, at the third communication device 490, an information component 496 receives signals from the control node and further processes the received signals (e.g., digitizes the received signals), and provides the processed signals to a control component 491. At the third communication device 490, the information / data provided by the control component 491 is sent or provided to the control node after processing by the information component 496. The third communication device 490 can include a memory 495 configured to temporarily store modulation configurations and corresponding time slots provided by the control node.

[0325] As one embodiment, the first communication device 450 apparatus includes at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the first communication device 450 apparatus at least to receive a first message and a second message, the first message indicating a first transmission opportunity on a first channel, an end time of the first transmission opportunity being a first time; the second message indicating that the first transmission opportunity ends at a second time, the second time being earlier than the first time; send a third message, the third message indicating a second transmission opportunity on the first channel, an end time of the second transmission opportunity being the first time; wherein the first channel is a primary channel of a first basic service set, the first node belonging to the first basic service set; a transmission time required by the first node for data to be sent being greater than a time available for transmission of data in the second transmission opportunity.

[0326] As one embodiment, the first communication device 450 apparatus includes a memory storing a program of computer readable instructions to produce actions when executed by at least one processor, the actions comprising: receiving a first message and a second message; sending a third message.

[0327] As one embodiment, the second communication device 410 apparatus comprises at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the performance of the following. The second communication device 410 apparatus is caused to at least: transmit a first message and a second message, the first message indicating a first transmission opportunity on a first channel, an end time of the first transmission opportunity being a first time; the second message indicating that the first transmission opportunity ends at a second time, the second time being earlier than the first time; receive a third message, the third message indicating a second transmission opportunity on the first channel, an end time of the second transmission opportunity being the first time; wherein the first channel is a primary channel of a first basic service set, the second node belonging to the first basic service set; a transmission time required by the first node for data to be transmitted being greater than a time available for transmission of data in the second transmission opportunity.

[0328] As one embodiment, the second communication device 410 apparatus comprises a memory storing a program of computer readable instructions to produce actions when executed by at least one processor, the actions comprising: transmitting a first message and a second message; receiving a third message.

[0329] As one embodiment, the first communication device 450 corresponds to the first node in the present application.

[0330] As one embodiment, the second communication device 410 corresponds to the second node in the present application.

[0331] As one embodiment, the first communication device 450 is a terminal.

[0332] As one embodiment, the first communication device 450 is a non-AP STA.

[0333] As one embodiment, the first communication device 450 is an AP.

[0334] As one embodiment, the first communication device 450 is a dependent AP of an MLD.

[0335] As one embodiment, the second communication device 410 is an AP.

[0336] As one embodiment, the second communication device 410 is a non-AP STA.

[0337] As one embodiment, the second communication device 410 is a dependent AP of an MLD.

[0338] As an embodiment, the second communication device 410 is a relay device.

[0339] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468 or the controller / processor 459 is configured to receive the first message in the present application; at least one of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470 or the controller / processor 475 is configured to send the first message in the present application.

[0340] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468 or the controller / processor 459 is configured to receive the second message in the present application; at least one of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470 or the controller / processor 475 is configured to send the second message in the present application.

[0341] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468 or the controller / processor 459 is configured to send the third message in the present application; at least one of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470 or the controller / processor 475 is configured to receive the third message in the present application.

[0342] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468 or the controller / processor 459 is configured to receive the fourth message in the present application; at least one of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470 or the controller / processor 475 is configured to send the fourth message in the present application. Embodiment 5

[0343] Embodiment 5 illustrates a flow chart of wireless signal transmission between a first node and a second node according to an embodiment of the present application, as shown in FIG. 5. In FIG. 5, each block represents a step, and the first node N51 communicates with the second node N52 through a wireless interface. It is particularly pointed out that the order in the present embodiment does not limit the order of signal transmission and implementation in the present application.

[0344] For the first node N51, comprising: receiving the first message at step S511; receiving the second message at step S512; transmitting the third message at step S513.

[0345] For the second node N52, comprising: transmitting the first message at step S521; transmitting the second message at step S522; receiving the third message at step S523.

[0346] As an embodiment, the first node N51 is the first node in the present application.

[0347] As an embodiment, the second node N52 is the second node in the present application.

[0348] As an embodiment, the second node is a TXOP holder of the first transmission opportunity.

[0349] As an embodiment, the first message is used for the second node to obtain the first transmission opportunity.

[0350] As an embodiment, the first node is not a TXOP responder of the first transmission opportunity.

[0351] As an embodiment, the first node receives the first message and performs an updating NAV operation.

[0352] As an embodiment, the first node receives the first message and does not perform an updating NAV operation.

[0353] As an embodiment, whether the updating NAV operation is performed or not is subject to the description of the RA field and / or user information field of the first message in Embodiment 1.

[0354] As an embodiment, the first node is a TXOP responder of the first transmission opportunity.

[0355] As an embodiment, the first transmitter transmits a first response frame as a response to receiving the first message; the first response frame is a CTS frame.

[0356] As an embodiment, the RA field of the first response frame is the same as the TA field of the first message.

[0357] As an embodiment, the PPDU carrying the first response frame is a non-HT PPDU.

[0358] As an embodiment, the RA field of the first response frame is the MAC address of the second node; wherein the individual / group bit is 0.

[0359] As one embodiment, the PPDU carrying the first response frame is a non-HT duplicate PPDU.

[0360] As one embodiment, the RA field of the first response frame is bandwidth signaling TA of the second node; wherein the individual / group bit is 1.

[0361] As one embodiment, the TXVECTOR parameter FORMAT of the PPDU carrying the first response frame is NOT_HT, and the TXVECTOR parameter NON_HT_MODULATION is NON_HT_DUP_OFDM.

[0362] As one embodiment, the channel of the PPDU carrying the first response frame is not larger than the channel of the PPDU carrying the first message.

[0363] As one embodiment, an uplink bandwidth subfield in the general information field included in the first message indicates the channel on which the first response frame is sent.

[0364] As one embodiment, an uplink bandwidth subfield in the general information field included in the first message indicates the bandwidth of the PPDU carrying the first response frame.

[0365] As one embodiment, the first node and the second node perform multi-frame transmission in the first transmission opportunity.

[0366] As one embodiment, the second node is a responder of the first transmission opportunity, and the third node is a holder of the first transmission opportunity.

[0367] As one embodiment, the first message is used for the third node to obtain the first transmission opportunity.

[0368] As one embodiment, the first message is a CTS frame fed back by the second node to an RTS frame sent by the third node.

[0369] As one embodiment, the second node and the third node perform multi-frame transmission in the first transmission opportunity.

[0370] As one embodiment, the multi-frame transmission performed in the first transmission opportunity includes a frame (such as a group addressed frame or a frame transmitted using an acknowledgement policy that does not require immediate acknowledgement) sent by a holder of the first transmission opportunity that does not require immediate acknowledgement, or an A-MPDU (aggregate-MPDU) containing only such a frame.

[0371] As one embodiment, the multi-frame transmission within the first transmission opportunity comprises: a frame requiring immediate acknowledgement (e.g. a separately addressed frame transmitted using an acknowledgement policy requiring immediate acknowledgement) or an A-MPDU containing at least one such frame transmitted by the holder of the first transmission opportunity, followed by an acknowledgement frame fed back by the responder of the corresponding first transmission opportunity after SIFS.

[0372] As one embodiment, the multi-frame transmission within the first transmission opportunity comprises: a trigger frame transmitted by the holder of the first transmission opportunity, or an A-MPDU containing at least one such frame, used to schedule the uplink transmission of the responder of the first transmission opportunity; a HE TB PPDU carrying uplink data transmitted by the holder of the first transmission opportunity immediately after SIFS; an acknowledgement frame fed back by the holder of the first transmission opportunity optionally immediately after the HE TB PPDU.

[0373] As one embodiment, the first transmission opportunity comprises a channel sounding.

[0374] As one embodiment, the multi-frame transmission within the first transmission opportunity comprises: an NDP (Null data PPDU) Announcement frame, an NDP, an A-MPDU containing one or more Compressed Beamforming frames.

[0375] As one embodiment, the multi-frame transmission within the first transmission opportunity comprises: a Beamforming Report Poll frame, or a BFRP (beamforming report poll) trigger frame.

[0376] As one embodiment, the IFS between the frames transmitted within the first transmission opportunity is SIFS.

[0377] As one embodiment, the first transmission opportunity can be truncated.

[0378] As one embodiment, the second message is used by the second node to truncate the first transmission opportunity.

[0379] As one embodiment, the second message is a CF-End frame transmitted by the third node and forwarded by the second node to truncate the first transmission opportunity.

[0380] As one embodiment, as a behavior after receiving the second message, the first node resets the NAV at the second time instant.

[0381] As one embodiment, the first node contends for the first channel after the second time.

[0382] As one embodiment, the third message is used for the first node to obtain the second transmission opportunity.

[0383] As one embodiment, the first node is a holder of the second transmission opportunity.

[0384] As one embodiment, the second node is a responder of the second transmission opportunity.

[0385] As one embodiment, the second transmitter, as a response to receiving the third message, transmits a second response frame; the second response frame is a CTS frame.

[0386] As one embodiment, the first receiver receives the second response frame, and a RA field of the second response frame indicates the first node.

[0387] As one embodiment, a duration field of the second response frame includes a value of a duration field of the third message minus all symbol times of a PPDU carrying the second response frame, minus a SIFS.

[0388] As one embodiment, the PPDU carrying the second response frame is a non-HT PPDU.

[0389] As one embodiment, a RA field of the second response frame is a MAC address of the first node; and a personal / group bit is 0.

[0390] As one embodiment, the PPDU carrying the second response frame is a non-HT duplicate PPDU.

[0391] As one embodiment, a RA field of the second response frame is a bandwidth signaling TA of the first node; and a personal / group bit is 1.

[0392] As one embodiment, a TXVECTOR parameter FORMAT of the PPDU carrying the second response frame is NOT_HT, and a TXVECTOR parameter NON_HT_MODULATION is NON_HT_DUP_OFDM.

[0393] As one embodiment, a channel of the PPDU carrying the second response frame is not larger than a channel of the PPDU carrying the third message.

[0394] As one embodiment, an uplink bandwidth subfield in a general information field of the third message indicates a channel on which the second response frame is transmitted.

[0395] As one embodiment, an uplink bandwidth subfield in a generic information field included in the third message indicates a bandwidth of a PPDU carrying the second response frame.

[0396] As one embodiment, the first node and the second node perform multi-frame transmission in the first transmission opportunity.

[0397] As one embodiment, an IFS between the plurality of frames transmitted in the second transmission opportunity is SIFS.

[0398] As one embodiment, the multi-frame transmission performed in the second transmission opportunity includes the plurality of MPDUs included in pending data of the first node.

[0399] As one embodiment, the first node supports MSDU fragmentation, and the second node supports MSDU defragmentation.

[0400] As one embodiment, the plurality of MSDUs transmitted in the second transmission opportunity are a result of fragmentation of one or more MSDUs in a transmission queue of the first access category.

[0401] As one embodiment, a partial fragment of one of the plurality of MSDUs is not in the plurality of fragmented MSDUs transmitted in the second transmission opportunity.

[0402] As one embodiment, the plurality of fragmented MSDUs are of the same length.

[0403] As one embodiment, the plurality of fragmented MSDUs are not greater than a fragmentation threshold (dot 11 Fragmentation Threshold).

[0404] As one embodiment, the plurality of MSDUs are not fragmented MSDUs.

[0405] As one embodiment, the first node and the second node support MSDU aggregation.

[0406] As one embodiment, the plurality of MSDUs transmitted in the second transmission opportunity are aggregated in a plurality of A-MSDUs.

[0407] As one embodiment, the plurality of A-MSDUs include a case of only one A-MSDU.

[0408] As one embodiment, the MSDUs included in any of the plurality of A-MSDUs share a same MAC header and a same FCS (frame check sequence).

[0409] As one embodiment, the MSDUs included in any of the plurality of A-MSDUs have a same TA field and a same RA field.

[0410] As one embodiment, the MSDUs included in any of the plurality of A-MSDUs are not fragmented MSDUs.

[0411] As one embodiment, any of the plurality of A-MSDUs cannot be fragmented.

[0412] As one embodiment, the MSDUs included in any of the plurality of A-MSDUs have a same priority parameter.

[0413] As one embodiment, the MSDUs included in any of the plurality of A-MSDUs are MSDUs in a same access category transmission queue.

[0414] As one embodiment, the MSDUs included in any of the plurality of A-MSDUs are all MSDUs in the first access category transmission queue.

[0415] As one embodiment, the MSDUs included in any of the plurality of A-MSDUs are associated with a same TID (traffic identifier).

[0416] As one embodiment, the plurality of MSDUs are carried in a plurality of MPDUs.

[0417] As one embodiment, any of the plurality of MPDUs is a QoS (quality of service) data frame.

[0418] As one embodiment, at least one of the plurality of MPDUs includes an A-MSDU.

[0419] As one embodiment, at least one of the plurality of MPDUs includes only one MSDU.

[0420] As one embodiment, the first node and the second node support MPDU aggregation.

[0421] As one embodiment, the multiple MPDUs transmitted within the second transmission opportunity are aggregated in multiple A-MPDUs.

[0422] As one embodiment, the multiple A-MPDUs include the case of only one A-MPDU.

[0423] As one embodiment, any A_MPDU of the multiple A-MPDUs cannot be fragmented.

[0424] As one embodiment, the multiple MPDUs included in any A_MPDU of the multiple A-MPDUs share the same PHY header.

[0425] As one embodiment, the MSDUs included in any A_MPDU of the multiple A-MPDUs have the same priority parameter.

[0426] As one embodiment, the MSDUs included in any A-MPDU of the multiple A-MPDUs are MSDUs in a transmission queue of the same access category.

[0427] As one embodiment, the MSDUs included in any A-MPDU of the multiple A-MPDUs are all MSDUs in a transmission queue of the first access category.

[0428] As one embodiment, the MSDUs included in any A-MPDU of the multiple A-MPDUs have the same TID (Traffic identifier).

[0429] As one embodiment, the first node and the second node support Multi-TID (Multi-Traffic Identifier).

[0430] As one embodiment, the MSDUs included in any A-MPDU of the multiple A-MPDUs have different priority parameters.

[0431] As one embodiment, the MSDUs included in any A-MPDU of the multiple A-MPDUs are from different access categories.

[0432] As one embodiment, at least part of the MSDUs included in any A-MPDU of the multiple A-MPDUs are from the first access category.

[0433] As one embodiment, the multiple MPDUs are carried in multiple PPDUs.

[0434] As one embodiment, at least one of the plurality of PPDUs includes an A-MPDU.

[0435] As one embodiment, at least one of the plurality of PPDUs includes only one MPDU.

[0436] As one embodiment, the second transmission opportunity includes Sounding.

[0437] As one embodiment, the first node transmits an NDP announcement frame and an NDP before transmitting the plurality of PPDUs including the plurality of MSDUs.

[0438] As one embodiment, the first node transmits a beamforming report poll frame, or BFRP, trigger frame before transmitting the plurality of PPDUs including the plurality of MSDUs.

[0439] As one embodiment, the first node receives feedback including one or more compressed beamforming frames before transmitting the plurality of PPDUs including the plurality of MSDUs.

[0440] As one embodiment, the multi-frame transmission within the second transmission opportunity includes an acknowledgement by the second node for the plurality of PPDUs.

[0441] As one embodiment, a duration field of the third message indicates that an end of the second transmission opportunity is the first time.

[0442] As one embodiment, the end of the second transmission opportunity being the first time includes an end of a last frame transmitted by the first node within the second transmission opportunity being the first time.

[0443] As a sub-embodiment of the above embodiment, the last frame transmitted by the first node is a CTS-to-self frame.

[0444] As a sub-embodiment of the above embodiment, the last frame transmitted by the first node is a CF-End frame.

[0445] As a sub-embodiment of the above embodiment, the last frame transmitted by the first node is a last of the plurality of PPDUs; wherein the first node indicates an acknowledgement policy of no immediate acknowledgement is required.

[0446] As an embodiment, the end time of the second transmission opportunity is the first time comprises: the end time of the last frame sent by the second node within the second transmission opportunity is the first time.

[0447] As a sub-embodiment of the above embodiment, the last frame sent by the second node is an acknowledgement frame for the last PPDU of the plurality of PPDUs.

[0448] As a sub-embodiment of the above embodiment, the last frame sent by the second node is a block acknowledgement frame for all the plurality of PPDUs.

[0449] As an embodiment, one of the plurality of MSDUs is only partially transmitted.

[0450] As an embodiment, at least one of the plurality of MSDUs is a fragmented MSDU.

[0451] As an embodiment, the first node guarantees the end time of the second transmission opportunity is the first time by dynamic frame fragmentation operation.

[0452] As an embodiment, the first node guarantees the end time of the second transmission opportunity is the first time by controlling the number of octets of at least one MSDU(s) carried by the last PPDU of the plurality of PPDUs.

[0453] As an embodiment, the first node guarantees the end time of the second transmission opportunity is the first time by controlling the number of octets of at least part of the plurality of MSDUs carried by all the plurality of PPDUs.

[0454] As an embodiment, the first node guarantees the end time of the second transmission opportunity is the first time by adjusting the MCS (Modulation and Coding Scheme).

[0455] As an embodiment, the first node guarantees the end time of the second transmission opportunity is the first time by adjusting the NSS (Number of spatial stream).

[0456] Embodiment 6

[0457] Embodiment 6 illustrates a schematic diagram of time domain relationship between the first transmission opportunity and the second transmission opportunity according to an embodiment of the present application, as shown in FIG. 6. In FIG. 6, the rectangle represents the duration of the transmission opportunity on the first channel for the first node.

[0458] As one embodiment, the first message indicates a duration of the first transmission opportunity on at least the first channel.

[0459] As one embodiment, the first message indicates that the ending time of the first transmission opportunity is the first time.

[0460] As one embodiment, the first time is determined according to a duration field included in the first message and an ending time of the PPDU carrying the first message.

[0461] As one embodiment, the first time is the time of the ending time of the PPDU carrying the first message plus a value of a duration field included in the first message.

[0462] As one embodiment, the ending time of the PPDU carrying the first message is the time when a PHY-RXEND.indication primitive of the PPDU carrying the first message is received by a MAC layer of the first node.

[0463] As one embodiment, the second time is determined by the first node according to an ending time of the PPDU carrying the second message.

[0464] As one embodiment, the ending time of the PPDU carrying the second message is the time when a PHY-RXEND.indication primitive of the PPDU carrying the second message is received by a MAC layer of the first node.

[0465] As one embodiment, the second time is the time when a PHY-RXEND.indication primitive of the PPDU carrying the second message is received by a MAC layer of the first node.

[0466] As one embodiment, the first node starts to transmit the third message at a third time.

[0467] As one embodiment, the third time is the time when a value of the backoff counter associated with the first node decreases to zero.

[0468] As one embodiment, the third time is the time when a value of the backoff counter associated with the first EDCAF decreases to zero.

[0469] As one embodiment, the third message is transmitted only when a time of the third time being earlier than the first time is greater than the first threshold.

[0470] As one embodiment, there is a fourth transmission opportunity between the second time instant and the third time instant.

[0471] As one embodiment, the holder of the fourth transmission opportunity is a node other than the first node and the second node within the first basic service set.

[0472] As one embodiment, the holder of the fourth transmission opportunity is the third node.

[0473] As one embodiment, within the fourth transmission opportunity, the first node, or the first EDCAF, associates the backoff counter pending.

[0474] As one embodiment, at least part of the pending data of the first node arrives before the third time instant.

[0475] As one embodiment, at least part of the pending data of the first node arrives before the backoff timer is started.

[0476] As one embodiment, at least part of the pending data of the first node is not transmitted at the first time instant.

[0477] As one embodiment, the first node contends for the channel again after the first time instant to transmit the remaining pending data.

[0478] Embodiment 7

[0479] Embodiment 7 illustrates a flowchart of wireless signal transmission between a first node and a second node according to one embodiment of the present application, as shown in FIG. 7. In FIG. 7, each block represents a step, and the first node N71 communicates with the second node N72 through a wireless interface. It is particularly pointed out that the order in this embodiment does not limit the order of signal transmission and implementation in the present application.

[0480] For the first node N71, it includes: receiving a fourth message at step S711; receiving a second message at step S712.

[0481] For the second node N72, it includes: sending a fourth message at step S721; sending a second message at step S722.

[0482] As one embodiment, the fourth message is carried in a MMPDU (MAC management protocol data unit).

[0483] As one embodiment, the fourth message is carried in a management frame.

[0484] As one embodiment, the fourth message is carried in an Extended frame.

[0485] As one embodiment, the fourth message is carried in a Beacon frame.

[0486] As one embodiment, the fourth message is carried in a Coordination frame.

[0487] As one embodiment, the fourth message is carried in an Action frame.

[0488] As one embodiment, the fourth message is carried in an MPDU.

[0489] As one embodiment, the fourth message is carried in a Data frame.

[0490] As one embodiment, the fourth message includes a first field indicating the non-primary channel access coordination.

[0491] As one embodiment, the fourth message includes at least a first field in an element indicating multi-AP coordination in a MMPDU carrying the fourth message; wherein an Element ID of the element indicating multi-AP coordination has a value of 255, and an Element ID Extension has a value of an integer between 136 and 255.

[0492] As one embodiment, the element indicating multi-AP coordination includes a second field indicating the non-primary channel access coordination.

[0493] As one embodiment, the fourth message includes at least a first field in an element indicating non-primary channel access coordination in a MMPDU carrying the fourth message; wherein an Element ID of the element indicating non-primary channel access coordination has a value of 255, and an Element ID Extension has a value of an integer between 136 and 255.

[0494] As one embodiment, the fourth message includes at least a first field in an Action field used to indicate multi-AP coordination in a MMPDU carrying the fourth message; wherein a Category of the Action field indicating non-primary channel access coordination has a value of an integer between 38 and 125.

[0495] As one embodiment, the Action field indicating multi-AP coordination includes a second field indicating the non-primary channel access coordination.

[0496] As one embodiment, the at least first field comprised in the fourth message is located in an Action field of the MMPDU carrying the fourth message indicating non-primary channel access coordination; wherein the category value of the Action field indicating non-primary channel access coordination is an integer between 38 and 125.

[0497] As one embodiment, the at least first field comprised in the fourth message is located in a QoS Control field of the MPDU carrying the fourth message.

[0498] As one embodiment, the at least first field comprised in the fourth message is located in a HT Control field of the MPDU carrying the fourth message.

[0499] As one embodiment, the at least first field comprised in the fourth message is located in an A-Control subfield within a HE variant HT Control field of the MPDU carrying the fourth message; wherein the Control ID subfield comprised in the A-Control subfield indicates a value being an integer between 10 and 14.

[0500] As one embodiment, the at least first field comprised in the fourth message is located in a UHR variant HT Control field of the MPDU carrying the fourth message.

[0501] As one embodiment, the fourth message is sent by a serving AP of the first node.

[0502] As one embodiment, the fourth message is sent by a serving AP of the first basic service set association.

[0503] As one embodiment, the serving AP is the second node.

[0504] As one embodiment, the fourth message is sent by the second node and received by the first node before the second time instant.

[0505] As one embodiment, the first node receives the first message earlier than the step S711.

[0506] As one embodiment, the second node sends the first message earlier than the step S721.

[0507] As one embodiment, the fourth message is sent by the second node and received by the first node during the first transmission opportunity; wherein the second node is the holder of the first transmission opportunity.

[0508] As one embodiment, the fourth message is sent at a TBTT (target beacon transmission time).

[0509] As one embodiment, the first transmission opportunity comprises the TBTT, and the first node receives the fourth message at the TBTT.

[0510] As one embodiment, the TBTT is before the second time.

[0511] As one embodiment, the TBTT is before the time when the second message is sent.

[0512] As one embodiment, the PPDU carrying the MMPDU comprising the fourth message is one of the plurality of PPDUs.

[0513] As one embodiment, the first node receives the first message later than the step S711.

[0514] As one embodiment, the second node sends the first message later than the step S721.

[0515] As one embodiment, the fourth message is sent by the second node and received by the first node before the first transmission opportunity.

[0516] As one embodiment, the second node sends the fourth message at a TBTT before sending the first message.

[0517] As one embodiment, the second node contends for the first channel before sending the first message, and sends the fourth message.

[0518] As one embodiment, the second node negotiates the non-primary channel access coordination with AP(s) of a neighboring basic service set before the second time.

[0519] As one embodiment, the second node negotiates the non-primary channel access coordination with at least an AP of the second basic service set before the second time.

[0520] As one embodiment, the neighboring basic service set comprises at least the second basic service set.

[0521] As one embodiment, the AP(s) of the neighboring basic service set comprises at least the fourth node; wherein the fourth node is an AP of the second basic service set.

[0522] As one embodiment, the second node transmits a first coordination frame, the first coordination frame indicating the non-primary channel access coordination.

[0523] As one embodiment, the first coordination frame indicates the second channel; wherein the second channel is a target secondary channel for nodes of the first basic service set to trigger the non-primary channel access.

[0524] As one embodiment, the target secondary channel means a secondary channel to switch to when triggering the non-primary channel access.

[0525] As one embodiment, the first coordination frame is unicast, a RA field of the first coordination frame indicating the fourth node.

[0526] As one embodiment, the first coordination frame is broadcast, the second node polling AP(s) of the neighboring basic service set for feedback of the first coordination frame.

[0527] As one embodiment, the second node receives at least an acknowledgement of the first coordination frame from the fourth node, indicating participation in the non-primary channel access coordination.

[0528] As one embodiment, the basic service set group performing the non-primary channel access coordination includes at least the second basic service set.

[0529] As one embodiment, the basic service set group performing the non-primary channel access coordination excludes a basic service set that does not receive an acknowledgement of the first coordination frame.

[0530] As one embodiment, the second node receives a second coordination frame, the second coordination frame indicating a non-primary channel access coordination.

[0531] As one embodiment, the second coordination frame is an acknowledgement of the first coordination frame from the fourth node.

[0532] As one embodiment, a TA field of the second coordination frame is a BSSID of the second basic service set.

[0533] As one embodiment, a TA field of the second coordination frame is a transmission BSSID of the second basic service set.

[0534] As one embodiment, the second coordination frame indicates the third channel; wherein the third channel is a target secondary channel for nodes of the second basic service set to trigger the non-primary channel access.

[0535] As one embodiment, the second node transmits an acknowledgement of the second coordination frame.

[0536] As one embodiment, the second node does not transmit the first message and the second message on the third channel.

[0537] As one embodiment, the fourth message indicates the basic service set group performing the non-primary channel access coordination.

[0538] As one embodiment, the fourth message indicates a target secondary channel of any basic service set in the basic service set group performing the non-primary channel access coordination.

[0539] As one embodiment, the fourth message indicates that the target secondary channel of the second basic service set is the third channel.

[0540] As one embodiment, the second node indicates, through the fourth message, that the first node does not transmit the third message on the third channel.

[0541] As one embodiment, the second node indicates, through the fourth message, that all nodes in the first basic service set participating in the first transmission opportunity and the second transmission opportunity do not transmit frames on the third channel.

[0542] As one embodiment, the third message transmitted by the first node after the second time is not on the third channel.

[0543] Embodiment 8

[0544] Embodiment 8 illustrates a signal processing flowchart in a first node according to one embodiment of the present application, as shown in FIG. 8. In FIG. 8, each block represents a step.

[0545] In embodiment 8, the first node 800 receives a fifth message in step 801, the fifth message indicating a third transmission opportunity, the sender of the fifth message being a node in a second basic service set, the second basic service set belonging to the service set group performing the non-primary channel access coordination; triggers a first operation in step 802, the first operation being a non-primary channel access; wherein the first operation comprises: switching to a second channel during the third transmission opportunity; transmitting, or receiving, on the second channel; switching back to the first channel before an end time of the third transmission opportunity; the second channel being a secondary channel of the first basic service set.

[0546] As one embodiment, the message type of the fifth message is a control frame.

[0547] As one embodiment, the fifth message is an RTS frame.

[0548] As one embodiment, the fifth message is a CTS frame.

[0549] As one embodiment, the fifth message is a trigger frame.

[0550] As a sub-embodiment of the above embodiment, the fifth message is a MU-RTS trigger frame, and a value of a trigger type subfield in a general information field of the fifth message is 3.

[0551] As one embodiment, the fifth message is sent by the fourth node.

[0552] As one embodiment, the first node measures a signal strength of the fifth message, and the signal strength of the fifth message is greater than the second sensitivity threshold.

[0553] As one embodiment, a PPDU carrying the fifth message is an inter-BSS PPDU.

[0554] As one embodiment, a RXVECTOR parameter BSS_COLOR of the PPDU carrying the fifth message is a BSS color of the second basic service set.

[0555] As one embodiment, the first node measures a signal strength of the fifth message, and the signal strength of the fifth message is greater than the third sensitivity threshold.

[0556] As one embodiment, the fifth message is sent at least on the first channel.

[0557] As one embodiment, the fifth message is not sent on the second channel.

[0558] As one embodiment, the fifth message indicates the third transmission opportunity, and the third transmission opportunity is an OBSS TXOP.

[0559] As one embodiment, a duration field included in the fifth message indicates an ending moment of the third transmission opportunity.

[0560] As one embodiment, the ending moment of the third transmission opportunity is a fourth moment.

[0561] As one embodiment, the first node and the second node negotiate the non-primary channel access capability.

[0562] As one embodiment, the first node and the second node exchange the non-primary channel access capability in an association stage.

[0563] As one embodiment, the first node indicates support of the non-primary channel access capability through an association request frame.

[0564] As one embodiment, the second node indicates support of the non-primary channel access capability through an association response frame.

[0565] As one embodiment, the fourth message is used to configure and activate the non-primary channel access.

[0566] As one embodiment, the fourth message is used to configure and activate the non-primary channel access coordination.

[0567] As one embodiment, the first node indicates the non-primary channel access related device capability through an association request frame.

[0568] As one embodiment, the second node indicates the non-primary channel access related device capability through an association response frame.

[0569] As one embodiment, the non-primary channel access related device capability includes at least a channel switch delay.

[0570] As one embodiment, the non-primary channel access related device capability includes an operating bandwidth during the non-primary channel access.

[0571] As one embodiment, the first node satisfies a first set of conditions, triggering the first operation.

[0572] As one embodiment, the first set of conditions includes that a value of a duration field included in the fifth message is greater than a second threshold.

[0573] As one embodiment, the second threshold is configured by the fourth message.

[0574] As one embodiment, the fourth message includes a fourth field indicating the second threshold.

[0575] As one embodiment, the second threshold is a positive integer in unit of millisecond.

[0576] As one embodiment, the second threshold is used to evaluate whether one of the conditions triggering the non-primary channel access is satisfied.

[0577] As one embodiment, the first set of conditions includes that the second basic service set is included in a basic service set group performing the non-primary channel access coordination, indicated by the fourth message.

[0578] As one embodiment, the first node receives the fourth message before receiving the fifth message.

[0579] As one embodiment, the first node triggers the non-primary channel access after receiving the fifth message.

[0580] As one embodiment, the fourth message indicates that the target secondary channel of the first basic service set is the second channel.

[0581] As one embodiment, the fourth message includes a third field indicating that the secondary channel used by a node of the first basic service set to perform the non-primary channel access is the second channel.

[0582] As one embodiment, the non-primary channel access includes the first node switching to the second channel.

[0583] As one embodiment, the second node transmits a first trigger frame on the second channel.

[0584] As one embodiment, the second node receives the fifth message, and the second node triggers the non-primary channel access.

[0585] As one embodiment, the second node switches to the second channel.

[0586] As one embodiment, the first node receives the first trigger frame transmitted by the second node on the second channel.

[0587] As one embodiment, the first trigger frame is transmitted at least on the second channel, and the first trigger frame is not transmitted on the first channel.

[0588] As one embodiment, the first trigger frame is a MU-RTS frame, and a value of a trigger type subfield in a general information field of the first trigger frame is 3.

[0589] As one embodiment, the first trigger frame is a BSRP (buffer status report poll) frame, and a value of a trigger type subfield in a general information field of the first trigger frame is 4.

[0590] As one embodiment, the PPDU carrying the first trigger frame is one of a non-HT PPDU, a non-HT duplicate PPDU, an HE TB PPDU, an EHT TB PPDU, and a UHR TB PPDU.

[0591] As one embodiment, the first trigger frame is used to obtain the fifth transmission opportunity.

[0592] As one embodiment, the fifth transmission opportunity is a transmission opportunity on at least the second channel.

[0593] As one embodiment, the fifth transmission opportunity occupies a channel that does not include the first channel.

[0594] As an embodiment, the first trigger frame comprises a duration field whose value indicates the end time of the fifth transmission opportunity.

[0595] As an embodiment, the end time of the fifth transmission opportunity is earlier than the fourth time.

[0596] As an embodiment, a resource unit (RU) allocation field of the first user info field indicates the first RU.

[0597] As an embodiment, the first RU is at least part of a bandwidth comprised by the second channel.

[0598] As an embodiment, the first user info field is one of all user info fields comprised by the first trigger frame whose AID 12 subfield has a value equal to 12 LSBs of the AID of the first node.

[0599] As an embodiment, the first user info field is one of all user info fields comprised by the first trigger frame whose AID 12 subfield has a value equal to 0.

[0600] As an embodiment, the first RU is a random access (RA)-RU.

[0601] As an embodiment, the first node transmits a third response frame on the first RU.

[0602] As an embodiment, the first node receives the third response frame transmitted by the second node on the first RU.

[0603] As an embodiment, the third response frame is a CTS frame.

[0604] As an embodiment, the third response frame is a QoS Null frame.

[0605] As an embodiment, a PPDU carrying the third response frame is one of a HE TB PPDU, an EHT TB PPDU, and a UHR TB PPDU.

[0606] As an embodiment, at least the first node and the second node perform multi-frame transmission within the fifth transmission opportunity.

[0607] As an embodiment, the third transmission opportunity is truncated, and the end time of the last transmission opportunity of one or more transmission opportunities initiated again in the second basic service set is the fourth time.

[0608] Embodiment 9

[0609] Example 9 illustrates a time diagram of a first node operating on a first channel and a second channel according to one embodiment of the application, as shown in FIG. 9. In FIG. 9, the left hatched rectangle represents the time that the first node operates on the first channel; the vertical hatched rectangle represents the time that the first node operates on the second channel.

[0610] As one embodiment, the gray hatched rectangle in FIG. 9 indicates the duration of the OBSS TXOP.

[0611] As one embodiment, the gray hatched rectangle in FIG. 9 indicates the duration of the third transmission opportunity indicated by the fifth message.

[0612] As one embodiment, the gray hatched rectangle in FIG. 9 indicates the duration of the transmission opportunity of any basic service set in the basic service set group performing the non-primary channel access coordination.

[0613] As one embodiment, the first node triggers a non-primary channel access at a fifth time.

[0614] As one embodiment, the fifth time is the end time of receiving the PPDU carrying the fifth message.

[0615] As one embodiment, the end time of receiving the PPDU carrying the fifth message is the time that the MAC layer of the first node receives the PHY-RXEND.indication primitive of the PPDU carrying the fifth message.

[0616] As one embodiment, the first node switches channel to the second channel at the fifth time.

[0617] As one embodiment, the T1 time in FIG. 9 comprises at least the time required for the first node to switch from the first channel to the second channel.

[0618] As one embodiment, the T1 time is the time required for the first node to switch from the first channel to the second channel.

[0619] As one embodiment, the T1 time is related to the device capability of the first node.

[0620] As one embodiment, the first trigger frame is transmitted at least after the end time of the T1 time.

[0621] As one embodiment, the time that the first node operates on the first channel comprises the at least one transmission opportunity.

[0622] As one embodiment, the time the first node operates on the first channel comprises the fifth transmission opportunity.

[0623] As one embodiment, the fourth time is determined according to a duration field included in the fifth message and an end time of receiving the PPDU carrying the fifth message.

[0624] As one embodiment, the fourth time is the end time of receiving the PPDU carrying the fifth message plus a value of a duration field included in the fifth message.

[0625] As one embodiment, the end time of receiving the PPDU carrying the fifth message is a time when a MAC layer of the first node receives a PHY-RXEND.indication primitive of the PPDU carrying the fifth message.

[0626] As one embodiment, the T2 time in FIG. 9 at least comprises a time required for the first node to switch from the second channel to the first channel.

[0627] As one embodiment, the T2 time is a time required for the first node to switch from the second channel to the first channel.

[0628] As one embodiment, the T2 time is related to a device capability of the first node.

[0629] As one embodiment, an end time of the fifth transmission opportunity is a start time of the T2 time.

[0630] As one embodiment, the first node switches from the second channel back to the first channel before the fourth time.

[0631] As one embodiment, a time when the first node switches from the second channel back to the first channel is not later than the fourth time.

[0632] As one embodiment, the first node listens to the first channel at the fourth time.

[0633] Embodiment 10

[0634] Embodiment 10 illustrates a spatial topology diagram of the first to fourth nodes according to one embodiment of the present application, as shown in FIG. 10. In FIG. 10, the oval area represents the basic service area of AP1 and AP2, and the square block represents a non-AP user equipment.

[0635] As one embodiment, STA1 is the first node in the present application.

[0636] As one embodiment, the STA1 is the first node in the present application.

[0637] As one embodiment, the STA2 is the third node in the present application.

[0638] As one embodiment, the STA1 and the STA2 are both associated with the AP1.

[0639] As one embodiment, the STA1 and the STA2 are both located in the basic service area of the AP1.

[0640] As one embodiment, the AP1 is the holder of the first transmission opportunity.

[0641] As one embodiment, the first message is an RTS frame sent by the AP1.

[0642] As one embodiment, the first message is an MU-RTS trigger frame sent by the AP1.

[0643] As one embodiment, the first message is a CTS-to-self frame sent by the AP1.

[0644] As one embodiment, the second message is a CF-End frame sent by the AP1.

[0645] As one embodiment, the fourth message is a frame sent by the AP1 indicating the non-primary channel access coordination.

[0646] As one embodiment, the third message is an RTS frame sent by the STA1.

[0647] As one embodiment, the STA2 is the holder of the first transmission opportunity.

[0648] As one embodiment, as a response to receiving the RTS frame sent by the STA2, the first message is a CTS frame sent by the AP1; wherein the RA field of the first message is the same as the TA field of the RTS frame sent by the STA2.

[0649] As one embodiment, as a response to receiving the CF-End frame sent by the STA2, the second message is a CF-End frame sent by the AP1.

[0650] As one embodiment, the STA1 is the first node in the present application.

[0651] As one embodiment, the STA1 is the first node in the present application.

[0652] As an embodiment, the STA1 is the holder of the first transmission opportunity.

[0653] As an embodiment, the first message is an RTS frame sent by the STA1.

[0654] As an embodiment, the first message is a CTS frame sent by the STA1.

[0655] As an embodiment, the second message is a CF-End frame sent by the STA1.

[0656] As an embodiment, the third message is an RTS frame sent by the AP1.

[0657] As an embodiment, the third message is an MU-RTS trigger frame sent by the AP1.

[0658] As an embodiment, the third message is a CTS-to-self frame sent by the AP1.

[0659] As an embodiment, the AP2 is the fourth node in the present application.

[0660] As an embodiment, the AP1 is located in the basic service area of the AP2.

[0661] As an embodiment, the AP2 receives the first message on the first channel, triggering the non-primary channel access.

[0662] As an embodiment, the AP2 switches to the third channel before the first time.

[0663] As an embodiment, the AP2 cannot receive the second message on the third channel.

[0664] As an embodiment, the AP2 cannot receive the third message on the third channel.

[0665] As an embodiment, the STA1 is located in the basic service area of the AP2.

[0666] As an embodiment, the fifth message is an RTS frame sent by the AP2.

[0667] As an embodiment, the fifth message is a CTS frame sent by the AP2.

[0668] As an embodiment, the fifth message is an MU-RTS trigger frame sent by the AP2.

[0669] As an embodiment, the STA1 receives the fifth message on the first channel, triggering the non-primary channel access.

[0670] As an embodiment, the AP1 receives the fifth message on the first channel, triggering the non-primary channel access.

[0671] As an embodiment, the AP1 and the AP2 both support Multi-AP Coordination.

[0672] As an embodiment, the AP2 is located in the basic service area of the AP1.

[0673] As an embodiment, the AP1 and the AP2 negotiate the non-primary channel access coordination.

[0674] Embodiment 11

[0675] Embodiment 11 illustrates a structural block diagram of a processing apparatus in a first node according to an embodiment of the present application, as shown in FIG. 11. In FIG. 11, the processing apparatus 1100 in the first node includes a first receiver 1101, a first transmitter 1102.

[0676] In embodiment 11, the first receiver 1101 receives a first message and a second message, the first message indicating a first transmission opportunity on a first channel, an ending time of the first transmission opportunity being a first time; the second message indicating that the first transmission opportunity ends at a second time, the second time being earlier than the first time;

[0677] The first transmitter 1102 transmits a third message, the third message indicating a second transmission opportunity on the first channel, an ending time of the second transmission opportunity being the first time;

[0678] Wherein, the first channel is a primary channel of a first basic service set, the first node belonging to the first basic service set; a transmission time required by the data to be transmitted by the first node is greater than a time that can be used for transmitting data in the second transmission opportunity.

[0679] As an embodiment, the first time is determined according to a duration field included in the first message and an ending time of a PPDU carrying the first message; the second time is determined according to an ending time of a PPDU carrying the second message.

[0680] As an embodiment, the third message is transmitted by the first transmitter 1102 only when a time by which the second time is earlier than the first time is greater than a first threshold.

[0681] As an embodiment, the first receiver 1101 receives, on the first channel, a fourth message, the fourth message indicating to perform non-primary channel access coordination and a basic service set group performing the non-primary channel access coordination.

[0682] As an embodiment, the first receiver 1101 receives, on the first channel, a fourth message, the fourth message indicating to perform non-primary channel access coordination and a basic service set group performing the non-primary channel access coordination; the fourth message is received earlier than the second message.

[0683] As an embodiment, the first receiver 1101 receives, on the first channel, a fourth message, the fourth message indicating to perform non-primary channel access coordination and a basic service set group performing the non-primary channel access coordination;

[0684] The first receiver 1101 receives, on the first channel, a fifth message, the fifth message indicating a third transmission opportunity, a sender of the fifth message is a node in a second basic service set, the second basic service set belongs to the service set group performing the non-primary channel access coordination;

[0685] Triggering a first operation, the first operation is a non-primary channel access;

[0686] The first operation comprises: switching to a second channel during the third transmission opportunity; transmitting, or receiving, on the second channel; switching back to the first channel before an end time of the third transmission opportunity; the second channel is a secondary channel of the first basic service set.

[0687] As an embodiment, the first node 1100 is a non-AP STA.

[0688] As an embodiment, the first node 1100 is a user terminal.

[0689] As an embodiment, the first node 1100 is a relay device.

[0690] As an embodiment, the first node 1100 is an AP.

[0691] As an embodiment, the first receiver 1101 comprises at least one of the receiver 454 (including the antenna 452), the reception processor 456, the multi-antenna reception processor 458 and the controller / processor 459 in FIG. 4.

[0692] As an embodiment, the first receiver 1101 comprises at least one of the receiver 454 (including the antenna 452), the reception processor 456, the multi-antenna reception processor 458 or the controller / processor 459 in FIG. 4.

[0693] As one embodiment, the first transmitter 1102 includes at least one of the transmitter 454 (including the antenna 452), the transmit processor 468, the multi-antenna transmit processor 457, and the controller / processor 459 in FIG. 4.

[0694] As one embodiment, the first transmitter 1102 includes at least one of the transmitter 454 (including the antenna 452), the transmit processor 468, the multi-antenna transmit processor 457, or the controller / processor 459 in FIG. 4.

[0695] Embodiment 12

[0696] Embodiment 12 illustrates a structure block diagram of a processing apparatus in a second node according to one embodiment of the present application, as shown in FIG. 12. In FIG. 12, the processing apparatus 1200 in the second node includes a second receiver 1201, a second transmitter 1202.

[0697] In embodiment 12, the second transmitter 1202 transmits a first message and a second message, the first message indicates a first transmission opportunity in a first channel, an ending time of the first transmission opportunity is a first time; the second message indicates that the first transmission opportunity ends at a second time, the second time is earlier than the first time;

[0698] The second receiver 1201 receives a third message, the third message indicates a second transmission opportunity in the first channel, an ending time of the second transmission opportunity is the first time;

[0699] Wherein, the first channel is a primary channel of a first basic service set, the second node belongs to the first basic service set; a transmission time required by the data to be transmitted by the first node is greater than a time that can be used for transmitting data in the second transmission opportunity.

[0700] As one embodiment, the first time is determined according to a duration field included in the first message and an ending time of a PPDU carrying the first message; the second time is determined according to an ending time of a PPDU carrying the second message.

[0701] As one embodiment, the third message is received by the second receiver 1201 only when a time that the second time is earlier than the first time is greater than a first threshold.

[0702] As one embodiment, the second transmitter 1202 transmits a fourth message on the first channel, the fourth message indicates to perform a non-primary channel access cooperation and a basic service set group performing the non-primary channel access cooperation.

[0703] As one embodiment, the second transmitter 1202 transmits, on the first channel, a fourth message, the fourth message indicating to perform non-primary channel access coordination and a basic service set group to perform the non-primary channel access coordination; the fourth message is received earlier than the second message.

[0704] As one embodiment, the second transmitter 1202 transmits, on the first channel, a fourth message, the fourth message indicating to perform non-primary channel access coordination and a basic service set group to perform the non-primary channel access coordination; the fourth message is received earlier than the second message.

[0705] The second receiver 1201 receives, on the first channel, a fifth message, the fifth message indicating a third transmission opportunity, a sender of the fifth message is a node in a second basic service set, the second basic service set belongs to the service set group to perform the non-primary channel access coordination;

[0706] triggering a first operation, the first operation being a non-primary channel access;

[0707] wherein the first operation comprises: switching to a second channel during the third transmission opportunity; transmitting, or receiving, on the second channel; switching back to the first channel before an end time of the third transmission opportunity; the second channel being a secondary channel of the first basic service set.

[0708] As one embodiment, the first node 1200 is an AP.

[0709] As one embodiment, the first node 1200 is a non-AP STA.

[0710] As one embodiment, the first node 1200 is a user terminal.

[0711] As one embodiment, the second receiver 1201 comprises at least one of the receiver 418 (including the antenna 420), the receive processor 470, the multi-antenna receive processor 472 and the controller / processor 475 in FIG. 4.

[0712] As one embodiment, the second receiver 1201 comprises at least one of the receiver 418 (including the antenna 420), the receive processor 470, the multi-antenna receive processor 472 and the controller / processor 475 in FIG. 4.

[0713] As one embodiment, the second transmitter 1202 comprises at least one of the transmitter 418 (including the antenna 420), the transmit processor 416, the multi-antenna transmit processor 471 and the controller / processor 475 in FIG. 4.

[0714] As an embodiment, the second transmitter 1202 includes at least one of the transmitter 418 (including the antenna 420), the transmit processor 416, the multi-antenna transmit processor 471 and the controller / processor 475 in FIG. 4 of the present application.

[0715] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software functional module. The present application is not limited to any specific form of combination of software and hardware. The first type of communication node or UE or terminal in the present application includes but is not limited to mobile phones, tablets, notebooks, network cards, low-power devices, eMTC (enhanced Machine Type Communication) devices, NB-IoT devices, vehicle-mounted communication equipment, aircraft, airplanes, drones, remote-controlled aircraft and other wireless communication devices. The second type of communication node or base station or network-side device in the present application includes but is not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, eNBs, gNBs, transmission and reception nodes TRPs (Transmission and Reception Points), relay satellites, satellite base stations, aerial base stations and other wireless communication devices.

[0716] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first message and a second message, wherein the first message indicates a first transmission opportunity on a first channel, and an end time of the first transmission opportunity is a first time; and the second message indicates that the first transmission opportunity ends at a second time, and the second time is earlier than the first time. A first transmitter sends a third message, where the third message indicates a second transmission opportunity on the first channel, and the end time of the second transmission opportunity is the first time; wherein the first channel is the main channel of the first basic service set, and the first node belongs to the first basic service set; and the transmission time required for the data to be sent by the first node is greater than the time that can be used to transmit data in the second transmission opportunity.

2. The first node according to claim 1, wherein: The first moment is determined according to the duration field included in the first message and the end moment of the PPDU (PHY protocol data unit) carrying the first message; the second moment is determined according to the end moment of the PPDU carrying the second message.

3. The first node according to any one of claims 1 or 2, characterized in that The third message is sent only when the second moment is earlier than the first moment by a time greater than a first threshold.

4. The first node according to any one of claims 1 to 3, characterized in that: include: The first receiver receives a fourth message on the first channel, where the fourth message indicates execution of non-primary channel access cooperation and a basic service set group for executing the non-primary channel access cooperation.

5. The first node according to claim 4, characterized in that The fourth message is received earlier than the second message.

6. The first node according to any one of claims 4 or 5, characterized in that: include: The first receiver receives a fifth message on the first channel, where the fifth message indicates a third transmission opportunity, and a sender of the fifth message is a node in a second basic service set, where the second basic service set belongs to the service set group that performs the non-primary channel access coordination; triggering a first operation, where the first operation is non-primary channel access; The first operation includes: switching to the second channel during the third transmission opportunity; sending or receiving on the second channel; switching back to the first channel before the end of the third transmission opportunity; and the second channel is a secondary channel of the first basic service set.

7. A second node used for wireless communication, characterized in that: include: The second transmitter sends a first message and a second message, wherein the first message indicates a first transmission opportunity on a first channel, and an end time of the first transmission opportunity is a first time; and the second message indicates that the first transmission opportunity ends at a second time, and the second time is earlier than the first time. a second receiver receiving a third message, wherein the third message indicates a second transmission opportunity on the first channel, and an end time of the second transmission opportunity is the first time; The first channel is the main channel of the first basic service set, and the second node belongs to the first basic service set; the transmission time required for the data to be sent by the first node is greater than the time that can be used to transmit data in the second transmission opportunity.

8. A method for a first node in wireless communication, characterized in that: include: receiving a first message and a second message, wherein the first message indicates a first transmission opportunity on a first channel, and an end time of the first transmission opportunity is a first time; and the second message indicates that the first transmission opportunity ends at a second time, and the second time is earlier than the first time; sending a third message, where the third message indicates a second transmission opportunity on the first channel, and an end time of the second transmission opportunity is the first time; The first channel is the main channel of the first basic service set, the first node belongs to the first basic service set, and the transmission time required for the data to be sent by the first node is greater than the time that can be used to transmit data in the second transmission opportunity.

9. A method for a second node used in wireless communication, characterized in that: include: Sending a first message and a second message, wherein the first message indicates a first transmission opportunity on a first channel, and an end time of the first transmission opportunity is a first time; and the second message indicates that the first transmission opportunity ends at a second time, and the second time is earlier than the first time; receiving a third message, wherein the third message indicates a second transmission opportunity on the first channel, and an end time of the second transmission opportunity is the first time; The first channel is the main channel of the first basic service set, and the second node belongs to the first basic service set; the transmission time required for the data to be sent by the first node is greater than the time that can be used to transmit data in the second transmission opportunity.

Images