Method and device used for wireless communication

Abstract

The invention discloses a method and a device used for wireless communication. The first receiver receives a first message and a second message, the first message indicates a first transmission opportunity in a first channel, and an end moment of the first transmission opportunity is a first moment; the second message indicates that the first transmission opportunity ends at a second moment, and the second moment is earlier than the first moment; the first transmitter sends a third message, the third message indicates a second transmission opportunity in the first channel, and the ending moment of the second transmission opportunity is the first moment; wherein the first channel is a main channel of a first basic service set, and the first node belongs to the first basic service set; the transmission time required by the to-be-sent data of the first node is longer than the time which can be used for transmitting the data in the second transmission opportunity. According to the invention, the delay is reduced, and the fairness of channel competition is ensured.

Description

Technical Field

[0001] The present application relates to methods and devices in wireless communication systems, and more particularly to methods and devices for reducing delay and ensuring channel competition fairness in a wireless local area network (WLAN). Background Art

[0002] Wi-Fi (Wireless Fidelity) has become a ubiquitous technology in today's world, providing connections for billions of devices. It is also the preferred way for more and more users to access the Internet, and it has a tendency to gradually replace wired access. Wi-Fi technology has become the mainstream technical standard for WLAN (Wireless Local Area Network) due to its relatively simple implementation, reliable communication, high flexibility and relatively low implementation cost. In order to adapt to the endless emergence of new business applications and narrow the gap with wired network transmission performance, each generation of Wi-Fi standards is committed to improving wireless transmission rates. As Wi-Fi applications continue to demand high transmission rates, 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 research on the next-generation IEEE 802.11 standard, and formed the UHRTG (Task Group) in 2023 to formally standardize the future Wi-Fi 8 protocol.

[0003] Through preamble puncturing, channel bundling and other technologies, the maximum operating bandwidth of Wi-Fi devices has been supported to 320MHz, but according to the current specifications, the main channel is the only channel that can perform the back-off procedure. Even if the remaining auxiliary channels are available, nodes are allowed to initiate frame exchanges only when the main channel is idle, which limits spectrum utilization. In other words, the blocking of the main channel is still a bottleneck in terms of system reliability, because if interfering transmissions (such as overlapping basic service set transmissions or other existing technologies) overlap with the channel, a large amount of auxiliary channel bandwidth may be idle. Therefore, a new mechanism is discussed in the UHR SG, namely non-primary channel access, which allows nodes to exchange frames on the auxiliary channel when the main channel is busy. Moreover, this mechanism can utilize bandwidth that cannot be used based on traditional technologies, which helps to reduce latency and improve throughput and spectrum efficiency. Summary of the invention

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

[0005] In view of the above problems, the present application discloses a solution. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other. It should be noted that in the description of the present application, only the WLAN scenario is used as a typical application scenario or example; the present application is also applicable to other scenarios other than WLAN facing similar problems (such as relay networks, P2P networks, and scenarios supporting half-duplex user equipment), and can also achieve similar technical effects in WLAN scenarios. Furthermore, although the original intention of the present application is for WLAN, the present application can also be used for wireless networks such as WMAN (Wireless Metropolitan Area Network), WRAN (Wireless Regional Area Network), and WSN (wireless specialty network). In addition, the use of a unified solution for different scenarios (including but not limited to WLAN scenarios and WMAN scenarios) can also help reduce hardware complexity and cost. In the absence of conflict, the embodiments of the first node device of the present application and the features in the embodiments can be applied to the second node device, and vice versa. In particular, the interpretation of the terminology, nouns, functions, and variables in this application (unless otherwise specified) may refer to the definitions in the IEEE 802.11, IEEE 802.15, and IEEE 802.22 standard protocols.

[0006] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0007] 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;

[0008] sending 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;

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

[0010] As an embodiment, the benefits of the above method include: it is beneficial for nodes that are triggered to access the non-primary channel due to the first transmission opportunity to fairly compete for the idle first channel at the first moment.

[0011] As an embodiment, the benefits of the above method include: the method in the present application is compatible with existing channel access technologies.

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

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

[0014] According to one aspect of the present application, the above method is characterized in that the third message is sent only when the time when the second moment is earlier than the first moment is greater than a first threshold.

[0015] As an embodiment, the characteristics of the above method include: the first node will send the third message only when the remaining time before the first moment is long enough.

[0016] According to one aspect of the present application, the above method is characterized in that it includes:

[0017] The first receiver receives a fourth message on the first channel, where the fourth message indicates execution of non-primary channel access coordination and a basic service set group for executing the non-primary channel access coordination.

[0018] As an embodiment, the characteristics of the above method include: the method in the present application relies on multi-AP (access point) negotiation.

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

[0020] According to one aspect of the present application, the above method is characterized in that it includes:

[0021] 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;

[0022] triggering a first operation, wherein the first operation is non-primary channel access;

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

[0024] As an embodiment, the characteristics of the above method include: the first node can access the auxiliary channel to initiate frame exchange when the primary channel is busy.

[0025] As an embodiment, the benefits of the above method include: reducing delay, improving throughput and spectrum efficiency.

[0026] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0027] Sending a first message and a second message, wherein the first message indicates a first transmission opportunity on a first channel, and the 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;

[0028] 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;

[0029] The first channel is the main channel of the first basic service set, the second 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.

[0030] According to one aspect of the present application, the above method is characterized in that the second node is an 802.11AP.

[0031] According to one aspect of the present application, the above method is characterized in that the first moment is determined according to the duration field included in the first message and the end moment of the PPDU carrying the first message; and the second moment is determined according to the end moment of the PPDU carrying the second message.

[0032] According to one aspect of the present application, the above method is characterized in that the third message is sent only when the time when the second moment is earlier than the first moment is greater than a first threshold.

[0033] According to one aspect of the present application, the above method is characterized in that it includes:

[0034] A fourth message is sent on the first channel, where the fourth message indicates execution of non-primary channel access coordination and a basic service set group for executing the non-primary channel access coordination.

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

[0036] According to one aspect of the present application, the above method is characterized in that it includes:

[0037] 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;

[0038] triggering a first operation, wherein the first operation is non-primary channel access;

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

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

[0041] 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;

[0042] A first transmitter sends 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;

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

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

[0045] A 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;

[0046] A second receiver receives 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;

[0047] The first channel is the main channel of the first basic service set, the second 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0049] Figure 1 A signal processing flow chart in a first node according to an embodiment of the present application is illustrated;

[0050] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is illustrated;

[0051] Figure 3 A schematic diagram illustrating a wireless protocol stack according to an embodiment of the present application is illustrated;

[0052] Figure 4 A hardware module schematic diagram of a communication device according to an embodiment of the present application is illustrated;

[0053] Figure 5 A flowchart illustrating wireless signal transmission between a first node and a second node according to an embodiment of the present application;

[0054] Figure 6 A schematic diagram illustrating the time domain relationship between a first transmission opportunity and a second transmission opportunity according to an embodiment of the present application is illustrated;

[0055] Figure 7 A flowchart illustrating wireless signal transmission between a first node and a second node according to an embodiment of the present application;

[0056] Figure 8 A signal processing flow chart in a first node according to an embodiment of the present application is illustrated;

[0057] Fig. 9 A time diagram illustrating a first node operating on a first channel and a second channel according to an embodiment of the present application;

[0058] Fig.10 An example of a spatial topology diagram of the first to fourth nodes according to an embodiment of the present application is shown;

[0059] Fig.11 An example structural block diagram of a processing device in a first node according to an embodiment of the present application is shown;

[0060] Fig.12 The structural block diagram of the processing device in the second node according to an embodiment of the present application is illustrated. DETAILED DESCRIPTION

[0061] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, in the absence of conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other.

[0062] Example 1

[0063] Embodiment 1 illustrates a signal processing flow chart in a first node according to an embodiment of the present application, as shown in the attached Figure 1 As shown in the attached Figure 1 In the example, each box represents a step.

[0064] In Example 1, the first node 100 receives a first message in step 101, the first message indicating a first transmission opportunity on a first channel, and the end time of the first transmission opportunity is a first time; receives a second message in step 102, the second message indicating that the first transmission opportunity ends at a second time, and the second time is earlier than the first time; sends a third message in step 103, the third message indicating 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 a primary channel of a first basic service set (BSS), and the first 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.

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

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

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

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

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

[0070] As a sub-embodiment of the above embodiment, the first message is not a MU-RTS TXS (triggered TXOPsharing) frame.

[0071] As an embodiment, the first message is sent at least on the first channel.

[0072] As an embodiment, the first channel is one of a main 20 MHz channel, a main 40 MHz channel, a main 80 MHz channel, a main 160 MHz channel, and a main 320 MHz channel of the first basic service set.

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

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

[0075] As an embodiment, the first node supports channel bundling.

[0076] As an embodiment, the second node supports channel bundling.

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

[0078] As an embodiment, the channel bandwidth occupied by the first transmission opportunity is in the sub-7GHz (below 7 GHz) frequency band.

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

[0080] As an embodiment, the first node supports preamble puncturing.

[0081] As an embodiment, the second node supports preamble puncturing.

[0082] As an embodiment, the channel bandwidth occupied by the first transmission opportunity includes discontinuous channels.

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

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

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

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

[0087] As an embodiment, the RXVECTOR (receive vector) parameter BSS_COLOR of the PPDU carrying the first message is the BSS color (color) of the first basic service set.

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

[0089] As an embodiment, the TA (transmission address) field of the first message is the MAC address of the second node; wherein the value of the individual / group bit is 0.

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

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

[0092] As an 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.

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

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

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

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

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

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

[0099] As an embodiment, the TA field of the first message is a transmitted basic service set identifier (transmittedBSSID).

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

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

[0102] As an embodiment, the first message includes a duration field, indicating the duration of the first transmission opportunity.

[0103] As an embodiment, the value of the duration field included in the first message is set to the time required to transmit the pending data or management frame, plus a CTS frame, plus an acknowledgment (Ack) or block acknowledgment (BlockAck) frame, plus appropriate IFSs (interframe spaces), rounded up, in microseconds.

[0104] As an embodiment, the suitable IFSs include at least one or more SIFS (short IFS, short frame interval).

[0105] As a sub-embodiment of the above embodiment, the value of the duration field included in the first message may be added with the time required to transmit any NDP (null data PPDU) and explicit feedback of the NDP (if necessary).

[0106] As a sub-embodiment of the above embodiment, the value of the duration field included in the first message can be added with the time for transmitting the requested HE TB PPDU and the time for display confirmation or feedback (if necessary) of the requested HE TB PPDU.

[0107] As a sub-embodiment of the above embodiment, the value of the duration field included in the first message may be reduced by the time required to transmit the CTS frame and one SIFS.

[0108] As a sub-embodiment of the above embodiment, the value of the duration field included in the first message may be minus the time required to transmit an Ack or BlockAck frame and a SIFS.

[0109] As an embodiment, the first node performs an operation of updating a NAV (network allocation vector) at the end moment of receiving the PPDU carrying the first message.

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

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

[0112] 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 (clear to send) frame sent by the second node.

[0113] As an embodiment, the RA domain included in the first message is a 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.

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

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

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

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

[0118] As an embodiment, the condition for the first node to update the NAV includes: the value of the AID12 subfield of any user information field in all user information fields included in the first message is not equal to the 12 LSBs (least significant bits) of the AID (association identifier) ​​of the first node; wherein, the user information field is not a special user information field.

[0119] As an embodiment, the condition for the first node to update the NAV also includes: the value of the duration field included in the first message is greater than the value of the NAV timer of the first node.

[0120] As an embodiment, the condition for the first node to update the NAV also includes: 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.

[0121] As an embodiment, the condition for the first node to update the NAV also includes: the MAC layer of the first node does not receive the PHY-RXSTART.indication (physical layer-receive start indication) primitive within the NAV timeout (NAVTimeout) time after the end time of receiving the PPDU carrying the first message.

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

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

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

[0125] As an embodiment, the first node only updates the BSS internal NAV timer.

[0126] As an embodiment, the condition for the first node to update the NAV also includes: the value of the duration field included in the first message is greater than the value of the BSS internal NAV timer of the first node.

[0127] As an embodiment, the condition for the first node to update the NAV also includes: the value indicated by the RXVECTOR parameter TXOP_DURATION of the PPDU carrying the first message is greater than the value of the BSS internal NAV timer of the first node.

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

[0129] As an embodiment, when the value of the AID12 subfield in one of the user information (User Info) fields included in the first message is equal to 12 LSBs of the AID of the first node, the first node does not perform the NAV update operation.

[0130] As an embodiment, the message type of the second message is a control frame.

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

[0132] As an embodiment, the second message is a trigger frame; the value of the trigger type subfield in the common information (CommonInfo) of the second message is between 8 and 15.

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

[0134] As an embodiment, the channel through which the second message is sent is the same as that of the first message.

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

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

[0137] As an embodiment, the TXVECTOR parameter CH_BANDWIDTH_IN_NON_HT of the PPDU carrying the second message and the PPDU carrying the first message are the same.

[0138] As an embodiment, the TXVECTOR parameter FORMAT (format) of the PPDU carrying the second message is NOT_HT, and the TXVECTOR parameter NON_HT_MODULATION is NON_HT_DUP_OFDM.

[0139] As an embodiment, the value of the duration field included in the second message is 0.

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

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

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

[0143] As an embodiment, the personal / group bit of the BSSID (TA) field included in the second message is 1.

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

[0145] As an embodiment, for the first node, the PPDU carrying the first message is a BSS internal PPDU.

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

[0147] As an embodiment, the second message indicates that at least the right to use the first channel is released.

[0148] As an embodiment, the second message indicates that the first transmission opportunity ends at the second moment.

[0149] As an embodiment, the second message instructs the first node to reset the NAV at the second moment.

[0150] As an embodiment, the first node resets the value of the maintained NAV timer to 0 at the second moment.

[0151] As an embodiment, the first node resets the value of the BSS internal NAV timer to 0 at the second moment.

[0152] As an embodiment, the message type of the third message is a control frame.

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

[0154] As an embodiment, the third message is a trigger frame.

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

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

[0157] As an embodiment, the third message indicates the channel bandwidth occupied by the second transmission opportunity.

[0158] As an embodiment, the channel bandwidth occupied by the second transmission opportunity includes one or more continuous 20 MHz channels.

[0159] As an embodiment, the channel bandwidth occupied by the second transmission opportunity is in the sub-7GHz (below 7 GHz) frequency band.

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

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

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

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

[0164] As an embodiment, the channel bandwidth occupied by the second transmission opportunity includes discontinuous channels.

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

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

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

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

[0169] As an embodiment, the channel bandwidth occupied by the second transmission opportunity at least partially overlaps with the channel bandwidth occupied by the first transmission opportunity.

[0170] As an 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.

[0171] As an embodiment, the second transmission opportunity includes at least a transmission opportunity of the first node on the first channel.

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

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

[0174] As an 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.

[0175] As an embodiment, the PPDU carrying the third message is a non-HT repeat PPDU.

[0176] As an 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.

[0177] As an embodiment, the TXVECTOR parameter CH_BANDWIDTH_IN_NON_HT of the PPDU carrying the third message is used to modify the first 7 bits of the scrambling sequence to indicate the bandwidth of the PPDU carrying the third message.

[0178] As an 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.

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

[0180] As an embodiment, the PPDU carrying the third message is one of HE TB PPDU, EHT MUPPDU, EHTTB PPDU, and UHRPPDU.

[0181] As an embodiment, the TA field of the third message is a transmitted basic service set identifier (transmittedBSSID).

[0182] As an embodiment, the uplink bandwidth subfield in the general information field included in the third message indicates the bandwidth of the PPDU that carries the third message.

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

[0184] As an embodiment, the first node sends the third message after the second moment.

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

[0186] As an embodiment, the first node sends the third message after successfully competing for the first channel.

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

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

[0189] As an embodiment, the first EDCAF (EDCA function) included in the first node sends the third message after successfully competing for the first channel.

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

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

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

[0193] As an embodiment, the first node determines whether the first channel is idle through CCA (clear channel assessment) and NAV status.

[0194] As an embodiment, the first node finds through energy detection that the received signal strength is less than a first sensitivity threshold; or finds through signal detection that the received signal strength is less than a second sensitivity threshold, thereby determining that the first channel is idle.

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

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

[0197] As an embodiment, the values ​​of the first sensitivity threshold and the second sensitivity threshold are related to the first channel.

[0198] As an embodiment, the values ​​of the first sensitivity threshold and the second sensitivity threshold refer to the CCA sensitivity section of the 802.11b / g / a, 802.11n, 802.11ac, 802.11ax, and 802.11be PHY protocols.

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

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

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

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

[0203] As an embodiment, the value of the third sensitivity threshold refers to section 26.10.2 of protocols 802.11ax and 802.11be.

[0204] As an embodiment, the first node detects the first channel within a first waiting time after the second moment and confirms that the first channel remains idle.

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

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

[0207] As an embodiment, the duration of the AIFS[AC] and the value of the AIFSN[AC] are both associated with the first access category.

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

[0209] As an embodiment, the candidates of the first access category also include A_VO (Alternate_VO, alternative voice) and A_VI (Alternate_VI, alternative video).

[0210] As an embodiment, the value of the first access category depends on the service type of the data to be sent.

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

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

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

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

[0215] As an embodiment, the first waiting time is AIFSN[AC]×aSlotTime−aRxTxTurnaroundTime.

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

[0217] As an embodiment, the definition and value of the parameters aSlotTime, aSIFSTime, and aRxTxTurnaroundTime depend on the protocol version supported by the first node and its device capabilities, with specific reference to the 802.11 protocol.

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

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

[0220] As an embodiment, the first node, or the first EDCAF, starts or restarts the backoff timer at the end of the first waiting time.

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

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

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

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

[0225] As an embodiment, whenever it is detected that the channel is idle in a backoff slot, the value of the backoff counter is reduced by one.

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

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

[0228] As an embodiment, when the value of the backoff counter decreases to zero, the first node sends the third message.

[0229] As an embodiment, the third message is sent at least on the first channel.

[0230] As an embodiment, the condition for sending the third message in a channel other than the first channel includes: at least one auxiliary channel other than the first channel remains idle during a DIFS period before the third message is sent.

[0231] As an embodiment, the condition for sending the third message in a channel other than the first channel includes: at least one auxiliary channel other than the first channel remains idle during the PIFS period before the third message is sent.

[0232] As an embodiment, the third message is sent only when the time by which the second moment is earlier than the first moment is greater than a first threshold.

[0233] As an embodiment, the first threshold is predefined.

[0234] As an embodiment, the first threshold is indicated by an AP associated with the first node.

[0235] As an embodiment, the first threshold is indicated by the second node.

[0236] As an embodiment, the fourth message indicates the first threshold.

[0237] As an embodiment, the first threshold is used to decide whether to compete for the transmission opportunity on the first channel before the first moment.

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

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

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

[0241] As an embodiment, the transmission time required for 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.

[0242] As an embodiment, the time that can be used for data transmission in the second transmission opportunity is at most the value of the duration field in the third message minus the time required to transmit a response to the third message, minus the time required to confirm the data frame transmitted in the second transmission opportunity (if necessary), and minus the appropriate IFSs.

[0243] As an embodiment, the first node can only transmit a portion of the data to be sent in the second transmission opportunity.

[0244] As an embodiment, the first node competes for the channel again after the first moment and transmits the remaining part of the data to be sent.

[0245] As an embodiment, the first node sends a plurality of MSDUs within the second transmission opportunity.

[0246] As an embodiment, the multiple MSDUs are at least a part of all MSDUs included in the data to be sent by the first node.

[0247] As an embodiment, some MSDUs with higher priorities among all the MSDUs are sent in the second transmission opportunity.

[0248] As an embodiment, at least one MSDU among the multiple MSDUs sent in the second transmission opportunity is located in the transmission queue of the first access category.

[0249] As an embodiment, the multiple MSDUs sent in the second transmission opportunity are all located in the transmission queue of the first access category.

[0250] As an embodiment, the multiple MSDUs sent in the second transmission opportunity include all MSDUs in the transmission queue of the first access category and part of the MSDUs in the transmission queues of other access categories.

[0251] As an embodiment, non-primary channel access means that when an 802.11 node detects an OBSS TXOP on a primary channel, the 802.11 node switches from a primary channel to a secondary channel to perform a channel access operation.

[0252] As an embodiment, the non-primary channel access further includes: the 802.11 node switches from the secondary channel back to the primary channel at the end time of the OBSS TXOP of the primary channel.

[0253] Although the above operation is referred to as non-primary channel access in the present application, the term "non-primary channel access" may also be replaced by other names including "auxiliary channel access" without changing the behavior of the above operation.

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

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

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

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

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

[0259] As an embodiment, the fourth node switches to the third channel, and switches back to the first channel at the first moment.

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

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

[0262] As an embodiment, the bandwidth of the third channel is the same as that of the first channel.

[0263] As an embodiment, the channels through which the first message, the second message and the third message are sent do not include the third channel.

[0264] As an embodiment, the channel bandwidths occupied by the first transmission opportunity and the second transmission opportunity do not include the third channel.

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

[0266] As an embodiment, the third channel is negotiated between the AP of the first basic service set and the AP of the second basic service set.

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

[0268] As an embodiment, the first receiver receives a fourth message on the first channel, and the fourth message indicates to perform non-primary channel access coordination.

[0269] As an embodiment, the non-main channel access coordination means: considering the node of the second basic service set triggering non-main channel access because of the first transmission opportunity; when the first transmission opportunity is truncated, the second transmission opportunity initiated by the first node ends at the first moment; wherein, the transmission time required for 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.

[0270] As an embodiment, the first channel is idle for at least part of the time after the first moment.

[0271] As an embodiment, the first channel is idle for at least SIFS+aSlotTime after the first moment.

[0272] As an embodiment, the above method has the advantage of being able to ensure fairness in the competition for the first channel when the OBSS node switches back to the first channel at the first moment after triggering the non-primary channel access.

[0273] Example 2

[0274] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 shown. Figure 2The architecture of IEEE 802.11 local area network is described. Basic Service Set (BSS) is the basic module (building block) of IEEE802.11 local area network, which is composed of a group of terminals that can communicate with each other. BSS includes independent basic service set (IBSS) and basic basic service set; wherein, terminals in IBSS can communicate directly with each other, and terminals in basic basic service set are associated with a central terminal and communicate with each other through the central terminal, and the central terminal is also called access point. Basic basic service set can be interconnected with other basic basic service sets through access point via distribution system (DS), and multiple basic basic service sets can be interconnected via DS to form an extended basic service set (ESS) to extend the coverage area of ​​the network. As shown in the figure, BSS231 is an IBSS, and the terminal 201 and terminal 202 included therein can communicate directly. As shown in the figure, BSS232 and BSS233 are basic service sets respectively. The communication between terminals in the basic service set needs to be forwarded through the access point. For example, if the terminal 203 in BSS232 needs to send data to the terminal 204 in BSS232, the data needs to be sent to the access point 211 first, and then the access point 211 forwards the data to the terminal 204; and vice versa. As shown in the figure, BSS232 and BSS233 form ESS234. The access point 211 and the access point 212 in the same ESS234 use the same service set identifier (ServiceSet Identifier, SSID), and BSS232 and BSS233 are usually overlapped. Terminals belonging to the same ESS 234 can communicate with each other. As shown in the figure, terminal 203 located in BSS 232 can communicate with terminal 205 located in BSS 233. At this time, access point 211 and access point 212 respectively have bridging functions, and transmit data between different access points through distribution system medium (DSM).

[0275] The BSS can identify the user terminal through the SSID, and can also identify other devices through the Basic Service Set Identifier (BSSID), which can be the MAC (Medium Access Control) address of the access point 211. The access point 211 periodically broadcasts a beacon frame including the BSSID, so that any terminal within the wireless coverage of the access point 211 can associate or re-associate with the access point 211 to establish a corresponding downlink 223 and uplink 224 (the uplink and downlink can be collectively referred to as a Wi-Fi link) with the access point 211. The beacon may include: an identifier of the primary channel used by the corresponding access point 211 and a timing synchronization function for establishing or maintaining timing synchronization with the access point 211.

[0276] A terminal is a single addressable instance of a MAC and a logical entity of a physical layer (PHY) interface facing a wireless medium (WM). In IEEE 802.11, a terminal is an addressable unit. In an IBSS, a terminal can send a beacon frame to announce the existence of a WLAN. In a basic basic service set, in order to establish a Wi-Fi link with an access point 211, the terminal 203 is configured to perform passive or active scanning on frequency channels in one or more frequency bands (e.g., 2.4 GHz (gigahertz), 5 GHz, 6 GHz, or 60 GHz bands). In order to perform passive scanning, the terminal 203 listens to beacons periodically sent by the corresponding access point 211. In order to perform active scanning, the terminal 203 generates a probe request and transmits these probe requests sequentially on each channel to be scanned, and listens for probe responses from the access point 211. The terminal 203 identifies or selects the access point 211 to be associated with through the scanning information obtained by passive or active scanning, and performs authentication and association operations to establish a communication link with the selected access point 211. The access point 211 assigns an association identifier (AID) to the terminal 203 at the end of the association operation, and the access point 211 uses the AID to track the terminal 203. The 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, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, a car, a vehicle-mounted device, a vehicle-mounted communication unit, a wearable device, or any other similar functional device. Technical personnel in the relevant field may also refer to the terminal as a non-AP (access point) station, a non-AP multi-link device (non-AP MLD (multi-link device)), 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.

[0277] An access point is an entity that includes a terminal and provides access to a distribution system DS for associated terminals via a wireless medium (wireless medium, WM). An access point includes a terminal and a distribution system access function (DSAF). An access point may 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, a transmitting and receiving node) or some other suitable term. An access point may provide access to an external network to a terminal in a WLAN via a corresponding WiFi link.

[0278] The distribution system DS is a backbone network for transmitting data between access points, usually called a backbone network, which is usually Ethernet. The access point provides a unified interface through the logical link control (LLC) layer as the upper layer, such as the IP (Internet Protocol) layer. All users' IP packets are transmitted through the gateway (GW). The gateway provides IP address allocation and other functions for terminals in the corresponding network segment. The gateway is also called an IP router. The gateway is connected to the Internet service 230. The Internet service 230 includes the operator's corresponding Internet protocol service, which may specifically include the Internet, intranet, IMS (IP Multimedia Subsystem) and PS (Packet Switching) streaming services.

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

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

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

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

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

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

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

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

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

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

[0289] As an embodiment, the access point 211 is a test device (eg, a transceiver that simulates some functions of a base station, a signaling tester).

[0290] As an embodiment, the access point 211 is a vehicle-mounted device.

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

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

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

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

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

[0296] As an embodiment, the terminals 201, 202, and 203 are consumer electronic products such as smart watches.

[0297] As an embodiment, the terminals 201, 202, 203 are transportation vehicles including cars.

[0298] As an 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.

[0299] As an 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.

[0300] As an 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.

[0301] As an 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.

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

[0303] As an embodiment, the recipient of the first message includes terminal 203 or terminal 202.

[0304] Example 3

[0305] Embodiment 3 illustrates a schematic diagram of a wireless protocol stack according to an embodiment of the present application, as shown in the attached Figure 3 IEEE 802.11 uses the CSMA (carrier sense multiple access) / CA (collision avoidance) protocol to control access to the transmission medium. Figure 3The wireless protocol architecture is shown 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 as PHY 301 in this article. The data link layer is above the physical layer and is responsible for the link between terminals or between terminals and access points through the physical layer. The data link layer includes MAC 302. MAC 302 and PHY 301 work together to complete data transmission and various management services.

[0306] MAC302 is responsible for encapsulating MSDU (MAC service data unit) into MPDU (MAC protocol data unit) frames, defining frames, achieving frame synchronization, processing destination MAC addresses and source MAC addresses, and processing frames when transmission errors occur. For data frames from upper layers or some larger management packets, packet segmentation and defragmentation are implemented, and integrity protection and cryptographic encapsulation are performed on data that needs to be protected. PHY301 is divided into two sublayers: the Physical Layer Convergence Procedure (PLCP) sublayer and the Physical Medium Dependent (PMD) sublayer. The frame received from MAC302 is added with a PHY header at the PLCP sublayer to generate a PPDU (PHY protocol data unit). Usually, the PPDU contains a pilot signal (preamble) and a PHY header to assist in the synchronization of received data and demodulation of the MPDU. Then, the PMD is responsible for encoding and modulating the MPDU and transmitting it into the air using the antenna.

[0307] MAC302 implements access control. If it is based on CSMA / CA access, it is controlled by the distributed coordination function (DCF). If a contention-free service is required, it can be controlled by the point coordination function (PCF) based on the DCF. Between DCF and PCF, a hybrid coordination function (HCF) can also be used. In DCF, carrier sensing is used to determine whether the medium is in an available state. The physical carrier sensing function is provided by PHY301, and the virtual carrier sensing function is provided by the network allocation vector (NAV). In order to ensure the right to use the medium and data transmission is not interrupted, the terminal can use the RTS (request to send) / CTS (clear to send) exchange method. IEEE 802.11 frames usually contain a duration field to reserve the medium usage time. Before trying to transmit any data, it is necessary to check whether the medium is in an idle state. If it is in a busy state, access must be delayed and a backoff algorithm must be used to avoid collisions. If the medium idle time is longer than DIFS (distributed interframe space), transmission can be performed immediately. In PCF, after the access point takes over the wireless medium, it will query the terminals connected to it according to the polling list to see if there is data to be transmitted. During the contention-free period, the terminal shall not transmit data unless the access point makes a request with a polling frame. MAC302 may include an error recovery function, that is, the transmitter is responsible for retransmission if the confirmation (ACK) information is not received for each frame sent. MAC302 can provide priority for delay-sensitive services. When there is only one transmission queue, the delay-sensitive service data frame is placed at the front of the queue. When multiple transmission queues are used, one queue will be used exclusively to transmit high-priority sensitive services. In order to achieve terminal energy saving, it can enter a sleep state periodically. In the sleep state, the access point will temporarily store frames for each terminal in the sleep state. If there are temporary frames, the access point will inform the terminal in the subsequent Beacon frame, and the terminal awakened from the power saving state can use the PS (power save)-Poll (polling) frame to obtain these temporary frames. The management functions of MAC302 also include channel management, connection management, quality of service, power control, security management, and time synchronization.Among them, channel management includes channel scanning, channel measurement, and channel switching; connection management includes user authentication, association, reassociation, and disassociation, and point-to-point connection; quality of service includes QoS service scheduling and service flow management; power management includes transmit power management and adaptive transmit power control; security management includes key generation and distribution; time synchronization includes high-level synchronization support. Although not shown in the figure, the terminal may also have several upper layers above MAC302, including an LLC layer.

[0308] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0309] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0310] Example 4

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

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

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

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

[0315] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the upper layer data frame from the Internet or the upper layer data frame from the data source 477 is provided to the controller / processor 475. The Internet and the data source 477 represent all the protocol layers above the MAC layer. The controller / processor 475 implements the functionality of the MAC layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, mapping between services and links, and wireless resource allocation to the first communication device 450. The controller / processor 475 is also responsible for the retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the 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, as well as mapping of 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 processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0316] In the transmission 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 corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the PHY layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream with the first communication device 450 as the destination or receiver. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the MAC layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides packet segmentation, decryption, header decompression, control signal processing to recover the upper layer data frame from the second communication device 410. The upper layer data frame is then provided to all protocol layers above the MAC layer.

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

[0318] 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 reception functions at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the PHY layer. The controller / processor 475 implements the MAC layer functions. 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 segmentation, decryption, header decompression, control signal processing to recover the upper layer data frame from the first communication device 450. Upper layer data frames from controller / processor 475 may be provided to all protocol layers above the Internet or MAC layer.

[0319] The third communication device 490 may be controlled by the first communication device 410 and / or the second communication device 450 to change channel implementation in a controlled manner, improve channel diversity, and provide robustness to channel blocking / fading, and the first communication device 410 or the second communication device 450 may be referred to as a control node of 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 may be configured to perform various aspects in combination 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 may be configured to perform various aspects in combination with the information component 496 or controller component 491 of the third communication device 490.

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

[0321] In the transmission in which the first communication device 410 and / or the second communication device 450 uses the third communication device 490 for communication, at the third communication device 490, a plurality of resonance units form a reflection surface 492, and a downlink signal is received from the first communication device 410, or an uplink signal is received from the second communication device 450, and each resonance unit can adjust (for example, apply a phase shift to directionally reflect the received signal) the corresponding received signal. The control component 491 can configure the phase or amplitude change by applying a precoding weight to each resonance unit so that the third communication device 490 can re-radiate the output beam in different directions given a specific input beam.

[0322] In some cases, when the third communication device 490 operates passively to only reflect or refract the beam from the transmitter to the receiver, the third communication device 490 can be used as a nearly passive device, operating without a large amount of power consumption. In some cases, the reflection or refraction direction can be controlled by a control node or network controller.

[0323] In the transmission from the control node and the third communication device 490, at the third communication device 490, the information component 496 receives the signal from the control node and further processes the received signal (e.g., digitizes the received signal), and provides the processed signal to the control component 491. At the third communication device 490, the information / data of the control component 491 is provided to the information component 496 for processing and then sent or provided to the control node. The third communication device 490 may include a memory 495, which is configured to temporarily store the modulation configuration and the corresponding time slot provided by the control node.

[0324] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least: receives a first message and a second message, the first message indicates a first transmission opportunity on a first channel, and the end time of the first transmission opportunity is a first time; the second message indicates that the first transmission opportunity ends at a second time, and the second time is earlier than the first time; sends a third message, 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 a first basic service set, and the first node belongs to the first basic service set; the transmission time required for the first node's data to be sent is greater than the time that can be used to transmit data in the second transmission opportunity.

[0325] As an embodiment, the first communication device 450 comprises: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving a first message and a second message; and sending a third message.

[0326] As an embodiment, the second communication device 410 device includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 410 device at least: sends a first message and a second message, the first message indicates a first transmission opportunity on a first channel, and the end time of the first transmission opportunity is a first time; the second message indicates that the first transmission opportunity ends at a second time, and the second time is earlier than the first time; receives a third message, 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 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.

[0327] As an embodiment, the second communication device 410 apparatus includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending a first message and a second message; and receiving a third message.

[0328] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0329] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0330] As an embodiment, the first communication device 450 is a terminal.

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

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

[0333] As an embodiment, the first communication device 450 is an affiliated AP of an MLD.

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

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

[0336] As an embodiment, the second communication device 410 is an affiliated AP of an MLD.

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

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

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

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

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

[0342] 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 the attached figure. Figure 5 As shown in the attached Figure 5 In the embodiment, each box represents a step, and the first node N51 and the second node N52 communicate with each other through the wireless interface. It is particularly noted that the sequence in this embodiment does not limit the signal transmission sequence and implementation sequence in this application.

[0343] for First node N51, including: receiving a first message in step S511; receiving a second message in step S512; and sending a third message in step S513.

[0344] for Second node N52 , including: sending a first message in step S521; sending a second message in step S522; and receiving a third message in step S523.

[0345] As an embodiment, the first node N51 is the first node in this application.

[0346] As an embodiment, the second node N52 is the second node in this application.

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

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

[0349] As an embodiment, the first node is not a responder to the first transmission opportunity.

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

[0351] As an embodiment, the first node receives the first message and does not perform a NAV update operation.

[0352] As an embodiment, the condition for executing the NAV update operation or not refers to the description of the RA field and / or user information field of the first message in Embodiment 1.

[0353] As an embodiment, the first node is a responder (TXOPresponder) of the first transmission opportunity.

[0354] As an embodiment, the first transmitter, in response to receiving the first message, sends a first response frame; the first response frame is a CTS frame.

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

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

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

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

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

[0360] As an 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.

[0361] As an embodiment, the channel for transmitting the PPDU carrying the first response frame is no larger than the channel for transmitting the PPDU carrying the first message.

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

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

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

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

[0366] As an embodiment, the first message is used by the third node to obtain the first transmission opportunity.

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

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

[0369] As an embodiment, the multi-frame transmission performed within the first transmission opportunity includes: frames that do not require immediate confirmation (such as group-addressed frames or frames transmitted using a confirmation strategy that does not require immediate confirmation) sent by the holder of the first transmission opportunity, or A-MPDU (aggregate-MPDU) that only contains such frames.

[0370] As an embodiment, the multi-frame transmission performed within the first transmission opportunity includes: a frame that requires immediate confirmation and is sent by the holder of the first transmission opportunity (such as a separately addressed frame transmitted using an acknowledgment strategy that requires immediate confirmation), or an A-MPDU containing at least one such frame, followed by a corresponding acknowledgment frame fed back by the responder of the first transmission opportunity after SIFS.

[0371] As an embodiment, the multi-frame transmission performed within the first transmission opportunity includes: a trigger frame sent by the holder of the first transmission opportunity, or an A-MPDU containing at least one such frame, which is used to schedule the uplink transmission of the responder of the first transmission opportunity; an HE TB PPDU carrying uplink data sent by the holder of the first transmission opportunity immediately after SIFS; and a confirmation frame fed back by the holder of the first transmission opportunity optionally followed by SIFS after the HE TB PPDU.

[0372] As an embodiment, the first transmission opportunity includes channel sounding.

[0373] As an embodiment, the multi-frame transmission performed in the first transmission opportunity includes: NDP (Nulldata PPDU) announcement frame, NDP, A-MPDU containing one or more Compressed Beamforming frames.

[0374] As an embodiment, the multi-frame transmission performed in the first transmission opportunity includes: a beamforming report poll frame, or a BFRP (beamforming report poll) trigger frame.

[0375] As an embodiment, the IFS between multiple frames transmitted in the first transmission opportunity is SIFS.

[0376] As an embodiment, the first transmission opportunity may be truncation.

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

[0378] As an embodiment, the second message is a CF-End frame sent by the third node and forwarded by the second node and used to truncate the first transmission opportunity.

[0379] As an embodiment, as an action after receiving the second message, the first node resets the NAV at the second moment.

[0380] As an embodiment, the first node competes for the idle first channel after the second moment.

[0381] As an embodiment, the third message is used by the first node to obtain the second transmission opportunity.

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

[0383] As an embodiment, the second node is a responder of the second transmission opportunity.

[0384] As an embodiment, the second transmitter, in response to receiving the third message, sends a second response frame; the second response frame is a CTS frame.

[0385] As an embodiment, the first receiver receives the second response frame, and the RA field of the second response frame indicates the first node.

[0386] As an embodiment, the value of the duration field included in the second response frame is: the value of the duration field included in the third message minus all symbol times of the PPDU carrying the second response frame, minus one SIFS.

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

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

[0389] As an embodiment, the PPDU carrying the second response frame is a non-HT repeat PPDU.

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

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

[0392] As an embodiment, the channel for transmitting the PPDU carrying the second response frame is no greater than the channel for transmitting the PPDU carrying the third message.

[0393] As an embodiment, the uplink bandwidth subfield in the general information field included in the third message indicates the channel to which the second response frame is sent.

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

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

[0396] As an embodiment, the IFS between multiple frames transmitted in the second transmission opportunity is SIFS.

[0397] As an embodiment, the multi-frame transmission performed in the second transmission opportunity includes the multiple MPDUs included in the data to be sent by the first node.

[0398] As an embodiment, the first node supports MSDU fragmentation, and the second node supports MSDU defragmentation.

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

[0400] As an embodiment, a partial fragment of one of the multiple MSDUs is not included in the multiple fragmented MSDUs transmitted in the second transmission opportunity.

[0401] As an embodiment, the lengths of the multiple fragmented MSDUs are the same.

[0402] As an embodiment, the MSDUs of the multiple fragments are not greater than a fragmentation threshold (dot11FragmentationThreshold).

[0403] As an embodiment, the multiple MSDUs are not fragmented MSDUs.

[0404] As an embodiment, the first node and the second node support MSDU aggregation.

[0405] As an embodiment, the multiple MSDUs transmitted in the second transmission opportunity are aggregated into multiple A-MSDU(s).

[0406] As an embodiment, the multiple A-MSDU(s) include only one A-MSDU.

[0407] As an embodiment, the MSDUs included in any A-MSDU among the multiple A-MSDU(s) share the same MAC header and FCS (frame check sequence).

[0408] As an embodiment, the values ​​of the TA field and the RA field of the MSDUs included in any A-MSDU among the multiple A-MSDU(s) are the same.

[0409] As an embodiment, the MSDUs included in any A-MSDU among the multiple A-MSDU(s) are not fragmented MSDUs.

[0410] As an embodiment, any A-MSDU among the multiple A-MSDU(s) cannot be fragmented.

[0411] As an embodiment, the MSDUs included in any A-MSDU among the multiple A-MSDU(s) have the same priority parameter.

[0412] As an embodiment, the MSDUs included in any A-MSDU among the multiple A-MSDU(s) are MSDUs in a transmission queue of the same access category.

[0413] As an embodiment, the MSDUs included in any A-MSDU among the multiple A-MSDU(s) are all MSDUs in the transmission queue of the first access category.

[0414] As an embodiment, the TID (Traffic identifier) ​​associated with the MSDUs included in any A-MSDU among the multiple A-MSDU(s) is the same.

[0415] As an embodiment, the multiple MSDUs are carried on multiple MPDUs.

[0416] As an embodiment, any MPDU among the multiple MPDUs is a QoS (quality of service) data frame.

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

[0418] As an embodiment, at least one MPDU among the plurality of MPDUs includes only one MSDU.

[0419] As an embodiment, the first node and the second node support MPDU aggregation.

[0420] As an embodiment, the multiple MPDUs transmitted in the second transmission opportunity are aggregated into multiple A-MPDU(s).

[0421] As an embodiment, the multiple A-MPDUs include only one A-MPDU.

[0422] As an embodiment, any A_MPDU among the multiple A-MPDUs cannot be fragmented.

[0423] As an embodiment, the multiple MPDUs included in any A_MPDU among the multiple A-MPDUs share the same PHY header.

[0424] As an embodiment, the MSDUs included in any A_MPDU among the multiple A-MPDUs have the same priority parameter.

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

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

[0427] As an embodiment, the TID (Traffic identifier) ​​associated with the MSDUs included in any A-MPDU among the multiple A-MPDUs is the same.

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

[0429] As an embodiment, the MSDUs included in any A-MPDU among the multiple A-MPDUs have different priority parameters.

[0430] As an embodiment, the MSDUs included in any A-MPDU among the multiple A-MPDUs are from different access categories.

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

[0432] As an embodiment, the multiple MPDUs are carried on multiple PPDUs.

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

[0434] As an embodiment, at least one PPDU among the multiple PPDUs includes only one MPDU.

[0435] As an embodiment, the second transmission opportunity includes channel sounding (Sounding).

[0436] As an embodiment, the first node sends an NDP announcement frame and an NDP before transmitting the multiple PPDUs including the multiple MSDUs.

[0437] As an embodiment, the first node sends a beamforming report poll frame, or a BFRP (beamforming report poll) trigger frame before transmitting the multiple PPDUs including the multiple MSDUs.

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

[0439] As an embodiment, the multi-frame transmission performed during the second transmission opportunity includes an acknowledgement by the second node for the multiple PPDUs.

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

[0441] As an embodiment, the end time of the second transmission opportunity being the first time includes: the end time of the last frame sent by the first node in the second transmission opportunity being the first time.

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

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

[0444] As a sub-embodiment of the above embodiment, the last frame sent by the first node is the last PPDU among the multiple PPDUs; wherein the first node indicates to adopt a confirmation strategy that does not require immediate confirmation.

[0445] As an embodiment, the end time of the second transmission opportunity being the first time includes: the end time of the last frame sent by the second node in the second transmission opportunity being the first time.

[0446] As a sub-embodiment of the above embodiment, the last frame sent by the second node is an acknowledgment frame for the last PPDU in the multiple PPDUs.

[0447] As a sub-embodiment of the above embodiment, the last frame sent by the second node is a block confirmation frame for all of the multiple PPDUs.

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

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

[0450] As an embodiment, the first node ensures that the end time of the second transmission opportunity is the first time through dynamic frame slicing operation.

[0451] As an embodiment, the first node ensures that the end time of the second transmission opportunity is the first time by controlling the number of bytes (Octets) of at least one MSDU(s) carried by the last PPDU among the multiple PPDUs.

[0452] As an embodiment, the first node ensures that the end time of the second transmission opportunity is the first time by controlling the number of bytes of at least part of the multiple MSDUs carried by all the multiple PPDUs.

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

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

[0455] Example 6

[0456] Embodiment 6 illustrates a schematic diagram of the time domain relationship between the first transmission opportunity and the second transmission opportunity according to an embodiment of the present application, as shown in the attached figure. Figure 6 As shown in the attached Figure 6 In FIG. 1 , rectangles represent transmission opportunity durations on the first channel for the first node.

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

[0458] As an embodiment, the first message indicates that the end time of the first transmission opportunity is the first time.

[0459] As an embodiment, the first time is determined according to the duration field included in the first message and the end time of the PPDU carrying the first message.

[0460] As an embodiment, the first moment is the end moment of receiving the PPDU carrying the first message plus the value of the duration field included in the first message.

[0461] As an embodiment, the end time of receiving the PPDU carrying the first message is the time when the MAC layer of the first node receives the PHY-RXEND.indication (physical layer reception end indication) primitive of the PPDU carrying the first message.

[0462] As an embodiment, the first node determines the second time according to the end time of receiving the PPDU carrying the second message.

[0463] As an embodiment, the end time of receiving the PPDU carrying the second message is the time when the MAC layer of the first node receives the PHY-RXEND.indication primitive of the PPDU carrying the second message.

[0464] As an embodiment, the second moment is the moment when the MAC layer of the first node receives the PHY-RXEND.indication primitive of the PPDU carrying the second message.

[0465] As an embodiment, the first node starts sending the third message at a third moment.

[0466] As an embodiment, the third moment is the moment when the value of the backoff counter associated with the first node decreases to zero.

[0467] As an embodiment, the third moment is the moment when the value of the backoff counter associated with the first EDCAF decreases to zero.

[0468] As an embodiment, the third message is sent only when the time that the third moment is earlier than the first moment is greater than the first threshold.

[0469] As an embodiment, there is a fourth transmission opportunity between the second moment and the third moment.

[0470] As an embodiment, the holder of the fourth transmission opportunity is a node other than the first node and the second node in the first basic service set.

[0471] As an embodiment, the holder of the fourth transmission opportunity is the third node.

[0472] As an embodiment, within the fourth transmission opportunity, the backoff counter associated with the first node, or the first EDCAF, is pending.

[0473] As an embodiment, at least part of the data to be sent by the first node arrives before the third moment.

[0474] As an embodiment, at least part of the data to be sent by the first node arrives before the backoff timer is started.

[0475] As an embodiment, at the first moment, at least part of the data to be sent by the first node has not been transmitted.

[0476] As an embodiment, the first node competes for the channel again after the first moment to transmit the remaining data to be sent.

[0477] Example 7

[0478] Embodiment 7 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 the attached figure. Figure 7 As shown in the attached Figure 7 In the embodiment, each box represents a step, and the first node N71 and the second node N72 communicate with each other through the wireless interface. It is particularly noted that the sequence in this embodiment does not limit the signal transmission sequence and implementation sequence in this application.

[0479] for First node N71 , including: receiving a fourth message in step S711; and receiving a second message in step S712.

[0480] for Second node N72 , including: sending a fourth message in step S721; and sending a second message in step S722.

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

[0482] As an embodiment, the fourth message is carried in a management frame.

[0483] As an embodiment, the fourth message is carried in an extended frame.

[0484] As an embodiment, the fourth message is carried in a beacon frame.

[0485] As an embodiment, the fourth message is carried in a coordination frame.

[0486] As an embodiment, the fourth message is carried in an action frame.

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

[0488] As an embodiment, the fourth message is carried in a data frame.

[0489] As an embodiment, the fourth message includes a first field, and the first field indicates the non-primary channel access coordination.

[0490] As an embodiment, the fourth message includes at least a first field located in an element indicating multi-AP collaboration in the MMPDU carrying the fourth message; wherein the element identifier (Element ID) value of the element indicating multi-AP collaboration is 255, and the value of the element identifier extension (Element ID Extension) is an integer between 136 and 255.

[0491] As an embodiment, the element indicating multi-AP collaboration includes a second field, and the second field indicates non-primary channel access collaboration.

[0492] As an embodiment, the fourth message includes at least a first field located in an element indicating non-main channel access coordination in the MMPDU carrying the fourth message; wherein the element identifier value of the element indicating non-main channel access coordination is 255, and the value of the element identifier extension is an integer between 136 and 255.

[0493] As an embodiment, at least the first field included in the fourth message is located in the MMPDU carrying the fourth message and is used to indicate an action field for multi-AP collaboration; wherein the category value of the action field indicating non-primary channel access collaboration is an integer between 38 and 125.

[0494] As an embodiment, the action field indicating multi-AP coordination includes a second field, and the second field indicates non-primary channel access coordination.

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

[0496] As an embodiment, at least the first field included in the fourth message is located in the QoS control field of the MPDU carrying the fourth message.

[0497] As an embodiment, at least a first field included in the fourth message is located in the HT control field of the MPDU carrying the fourth message.

[0498] As an embodiment, at least the first field included in the fourth message is an A-Control subfield located in the HE variant HT control field of the MPDU carrying the fourth message; wherein the value indicated by the control identifier (Control ID) subfield included in the A-Control subfield is an integer between 10 and 14.

[0499] As an embodiment, at least the first field included in the fourth message is located in the UHR variant HT control field of the MPDU carrying the fourth message.

[0500] As an embodiment, the fourth message is sent through the service AP of the first node.

[0501] As an embodiment, the fourth message is sent through the service AP associated with the first basic service set.

[0502] As an embodiment, the serving AP is the second node.

[0503] As an embodiment, the fourth message is sent by the second node and received by the first node before the second moment.

[0504] As an embodiment, the first node receives the first message earlier than step S711.

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

[0506] As an 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.

[0507] As an embodiment, the fourth message is sent at TBTT (target beacon transmission time).

[0508] As an embodiment, the first transmission opportunity includes the TBTT, and the first node receives the fourth message at the TBTT.

[0509] As an embodiment, the TBTT is before the second moment.

[0510] As an embodiment, the TBTT is before the moment when the second message is sent.

[0511] As an embodiment, the PPDU carrying the MMPDU including the fourth message is one of the multiple PPDUs.

[0512] As an embodiment, the first node receives the first message later than step S711.

[0513] As an embodiment, the behavior of the second node sending the first message is later than the step S721.

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

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

[0516] As an embodiment, the second node competes for the first channel and sends the fourth message before sending the first message.

[0517] As an embodiment, the second node negotiates the non-primary channel access coordination with the AP(s) of the adjacent basic service set before the second moment.

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

[0519] As an embodiment, the adjacent basic service set includes at least the second basic service set.

[0520] As an embodiment, the AP(s) of the adjacent basic service set includes at least the fourth node; wherein the fourth node is the AP of the second basic service set.

[0521] As an embodiment, the second node sends a first coordination frame, and the first coordination frame indicates the non-primary channel access coordination.

[0522] As an embodiment, the first collaborative frame indicates the second channel; wherein the second channel is a target auxiliary channel for the node of the first basic service set to trigger access to the non-primary channel.

[0523] As an embodiment, the target auxiliary channel means: the auxiliary channel switched to when the non-primary channel access is triggered.

[0524] As an embodiment, the first collaborative frame is unicast, and the RA field of the first collaborative frame indicates the fourth node.

[0525] As an embodiment, the first collaborative frame is broadcast, and the second node polls the AP(s) of the adjacent basic service set to feed back the first collaborative frame.

[0526] As an embodiment, the second node receives confirmation of the first cooperation frame from at least the fourth node, indicating participation in the non-primary channel access cooperation.

[0527] As an embodiment, the basic service set group for executing the non-primary channel access coordination includes at least the second basic service set.

[0528] As an embodiment, the basic service set group for performing the non-primary channel access cooperation does not include a basic service set for which an acknowledgement for the first cooperation frame has not been received.

[0529] As an embodiment, the second node receives a second coordination frame, and the second coordination frame indicates non-primary channel access coordination.

[0530] As an embodiment, the second collaborative frame is a confirmation of the first collaborative frame by the fourth node.

[0531] As an embodiment, the TA field of the second collaborative frame is the BSSID of the second basic service set.

[0532] As an embodiment, the TA field of the second collaborative frame is the transmission BSSID of the second basic service set.

[0533] As an embodiment, the second collaborative frame indicates the third channel; wherein the third channel is the target auxiliary channel for the node of the second basic service set to trigger access to the non-primary channel.

[0534] As an embodiment, the second node sends an acknowledgment of the second collaborative frame.

[0535] As an embodiment, the second node does not send the first message and the second message on the third channel.

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

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

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

[0539] As an embodiment, the second node instructs the first node through the fourth message not to send the third message on the third channel.

[0540] As an embodiment, the second node instructs all nodes participating in the first transmission opportunity and the second transmission opportunity in the first basic service set not to send frames on the third channel through the fourth message.

[0541] As an embodiment, the third message sent by the first node after the second moment is not on the third channel.

[0542] Example 8

[0543] Embodiment 8 illustrates a signal processing flow chart in the first node according to an embodiment of the present application, as shown in the attached Figure 8 As shown in the attached Figure 8 In the example, each box represents a step.

[0544] In Example 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 is a node in a second basic service set, and the second basic service set belongs to the service set group that performs the non-main channel access collaboration; triggers a first operation in step 802, and the first operation is non-main channel access; wherein the first operation includes: 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; the second channel is an auxiliary channel of the first basic service set.

[0545] As an embodiment, the message type of the fifth message is a control frame.

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

[0547] As an embodiment, the fifth message is a CTS frame.

[0548] As an embodiment, the fifth message is a trigger frame.

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

[0550] As an embodiment, the fifth message is sent by the fourth node.

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

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

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

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

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

[0556] As an embodiment, the fifth message is not sent on the second channel.

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

[0558] As an embodiment, the duration field included in the fifth message indicates the end time of the third transmission opportunity.

[0559] As an embodiment, the end time of the third transmission opportunity is the fourth time.

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

[0561] As an embodiment, the first node and the second node exchange the non-primary channel access capability during the association phase.

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

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

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

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

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

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

[0568] As an embodiment, the device capabilities related to the non-primary channel access include at least channel switching delay.

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

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

[0571] As an embodiment, the first condition set includes: the value of the duration field included in the fifth message is greater than a second threshold.

[0572] As an embodiment, the second threshold is configured by the fourth message.

[0573] As an embodiment, the fourth message includes a fourth field, and the fourth field indicates a second threshold.

[0574] As an embodiment, the second threshold is a positive integer, and the unit is milliseconds.

[0575] As an embodiment, the second threshold is used to evaluate whether one of the conditions for triggering the non-primary channel access is met.

[0576] As an embodiment, the first condition set includes: the basic service set group for executing the non-primary channel access coordination indicated by the fourth message includes the second basic service set.

[0577] As an embodiment, the first node receives the fourth message before receiving the fifth message.

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

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

[0580] As an embodiment, the fourth message includes a third field, and the third field indicates that the auxiliary channel used by the node of the first basic service set to perform the non-primary channel access is the second channel.

[0581] As an embodiment, the non-primary channel access includes: the first node switching to the second channel.

[0582] As an embodiment, the second node sends a first trigger frame on the second channel.

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

[0584] As an embodiment, the second node switches to the second channel.

[0585] As an embodiment, the first node receives the first trigger frame sent by the second node on the second channel.

[0586] As an embodiment, the first trigger frame is sent on at least the second channel, and the first trigger frame is not sent on the first channel.

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

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

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

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

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

[0592] As an embodiment, the channel occupied by the fifth transmission opportunity does not include the first channel.

[0593] As an embodiment, the value of the duration field included in the first trigger frame indicates the end time of the fifth transmission opportunity.

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

[0595] As an embodiment, the RU (resource unit) allocation field of the first user information field indicates the first RU.

[0596] As an embodiment, the first RU is at least a portion of the bandwidth included in the second channel.

[0597] As an embodiment, the first user information field is a user information field in which the value of the AID12 subfield is equal to 12 LSBs of the AID of the first node among all user information fields included in the first trigger frame.

[0598] As an embodiment, the first user information field is a user information field in which the value of the AID12 subfield is equal to 0 among all user information fields included in the first trigger frame.

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

[0600] As an embodiment, the first node sends a third response frame in the first RU.

[0601] As an embodiment, the first node receives a third response frame sent by the second node at the first RU.

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

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

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

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

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

[0607] Example 9

[0608] Embodiment 9 illustrates a time diagram of a first node operating on a first channel and a second channel according to an embodiment of the present application, as shown in the attached figure. Fig. 9 As shown in the attached Fig. 9 In the figure, a rectangle filled with a left slash indicates the time when the first node operates on the first channel; a rectangle filled with a vertical line indicates the time when the first node operates on the second channel.

[0609] As an example, Fig. 9 The gray filled rectangle in FIG. 1 represents the duration of the OBSS TXOP.

[0610] As an embodiment, the attached Fig. 9 The gray-filled rectangle in indicates the duration of the third transmission opportunity indicated by the fifth message.

[0611] As an embodiment, the attached Fig. 9 The grey-filled rectangle in indicates the duration of the transmission opportunity of any basic service set in the basic service set group for performing the non-primary channel access coordination.

[0612] As an embodiment, the first node triggers non-primary channel access at the fifth moment.

[0613] As an embodiment, the fifth moment is the end moment of receiving the PPDU carrying the fifth message.

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

[0615] As an embodiment, the first node switches the channel to the second channel at the fifth moment.

[0616] As an example, Fig. 9 The T1 time includes at least the time required for the first node to switch from the first channel to the second channel.

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

[0618] As an embodiment, the T1 time is related to the equipment capability of the first node.

[0619] As an embodiment, the first trigger frame is sent at least after the end time of the T1 time.

[0620] As an embodiment, the time during which the first node operates on the first channel includes the at least one transmission opportunity.

[0621] As an embodiment, the time during which the first node operates on the first channel includes the fifth transmission opportunity.

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

[0623] As an embodiment, the fourth moment is the moment of adding the end moment of receiving the PPDU carrying the fifth message to the value of the duration field included in the fifth message.

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

[0625] As an example, Fig. 9 The T2 time includes at least the time required for the first node to switch from the second channel to the first channel.

[0626] As an embodiment, the T2 time is the time required for the first node to switch from the second channel to the first channel.

[0627] As an embodiment, the T2 time is related to the equipment capability of the first node.

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

[0629] As an embodiment, the first node switches from the second channel back to the first channel before the fourth moment.

[0630] As an embodiment, the time when the first node switches from the second channel back to the first channel is no later than the fourth time.

[0631] As an embodiment, the first node listens to the first channel at the fourth moment.

[0632] Example 10

[0633] Embodiment 10 illustrates a schematic diagram of the spatial topology of the first to fourth nodes according to an embodiment of the present application, as shown in the attached figure. Fig.10 As shown in the attached Fig.10In the figure, the ellipse area represents the basic service area of ​​AP1 and AP2, and the square box represents the non-AP user equipment.

[0634] As an embodiment, STA1 is the first node in this application.

[0635] As an embodiment, the AP1 is the second node in the present application.

[0636] As an embodiment, STA2 is the third node in this application.

[0637] As an embodiment, both STA1 and STA2 are associated with AP1.

[0638] As an embodiment, the STA1 and the STA2 are both located in the basic service area of ​​the AP1.

[0639] As an embodiment, the AP1 is the holder of the first transmission opportunity.

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

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

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

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

[0644] As an embodiment, the fourth message is a frame sent by the AP1 to indicate the non-primary channel access coordination.

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

[0646] As an embodiment, the STA2 is the holder of the first transmission opportunity.

[0647] As an 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.

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

[0649] As an embodiment, the AP1 is the first node in this application.

[0650] As an embodiment, the STA1 is the second node in this application.

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

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

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

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

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

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

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

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

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

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

[0661] As an embodiment, the AP2 switches to the third channel before the first moment.

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

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

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

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

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

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

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

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

[0670] As an embodiment, both the AP1 and the AP2 support multi-AP coordination.

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

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

[0673] Embodiment 11

[0674] Embodiment 11 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in the attached figure. Fig.11 As shown in the attached Fig.11 In the example, the processing device 1100 in the first node includes a first receiver 1101 and a first transmitter 1102.

[0675] In embodiment 11, the first receiver 1101 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;

[0676] The first transmitter 1102 sends 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;

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

[0678] As an embodiment, the first moment is determined according to the duration field included in the first message and the end moment of the PPDU carrying the first message; and the second moment is determined according to the end moment of the PPDU carrying the second message.

[0679] As an embodiment, the third message is sent by the first transmitter 1102 only when the second moment is earlier than the first moment by more than a first threshold.

[0680] As an embodiment, the first receiver 1101 receives a fourth message on the first channel, wherein 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.

[0681] As an embodiment, the first receiver 1101 receives a fourth message on the first channel, wherein the fourth message indicates performing non-primary channel access collaboration and a basic service set group for performing the non-primary channel access collaboration; the fourth message is received earlier than the second message.

[0682] As an embodiment, the first receiver 1101 receives a fourth message on the first channel, where the fourth message indicates performing non-primary channel access collaboration and a basic service set group for performing the non-primary channel access collaboration;

[0683] The first receiver 1101 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;

[0684] triggering a first operation, wherein the first operation is non-primary channel access;

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

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

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

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

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

[0690] As an embodiment, the first receiver 1101 includes the attached Figure 4 The receiver 454 (including antenna 452), receive processor 456, multi-antenna receive processor 458 and controller / processor 459.

[0691] As an embodiment, the first receiver 1101 includes the attached Figure 4 At least one of the receiver 454 (including antenna 452), receive processor 456, multi-antenna receive processor 458 or controller / processor 459.

[0692] As an embodiment, the first transmitter 1102 includes the attached Figure 4 The transmitter 454 (including antenna 452), transmit processor 468, multi-antenna transmit processor 457 and controller / processor 459.

[0693] As an embodiment, the first transmitter 1102 includes the attached Figure 4 At least one of the transmitter 454 (including antenna 452), the transmit processor 468, the multi-antenna transmit processor 457 or the controller / processor 459.

[0694] Example 12

[0695] Embodiment 12 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in the attached figure. Fig.12 As shown in the attached Fig.12 In the embodiment, the processing device 1200 in the second node includes a second receiver 1201 and a second transmitter 1202.

[0696] In embodiment 12, the second transmitter 1202 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;

[0697] The second receiver 1201 receives 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;

[0698] The first channel is the main channel of the first basic service set, the second 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.

[0699] As an embodiment, the first moment is determined according to the duration field included in the first message and the end moment of the PPDU carrying the first message; and the second moment is determined according to the end moment of the PPDU carrying the second message.

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

[0701] As an embodiment, the second transmitter 1202 sends a fourth message on the first channel, wherein the fourth message indicates performing non-primary channel access cooperation and a basic service set group for performing the non-primary channel access cooperation.

[0702] As an embodiment, the second transmitter 1202 sends a fourth message on the first channel, wherein the fourth message indicates performing non-primary channel access cooperation and a basic service set group for performing the non-primary channel access cooperation; the fourth message is received earlier than the second message.

[0703] As an embodiment, the second transmitter 1202 receives a fourth message on the first channel, the fourth message indicating execution of non-primary channel access cooperation and a basic service set group for executing the non-primary channel access cooperation;

[0704] The second receiver 1201 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;

[0705] triggering a first operation, wherein the first operation is non-primary channel access;

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

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

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

[0709] As an embodiment, the first node 1200 is a user terminal.

[0710] As an embodiment, the second receiver 1201 includes the attached Figure 4 The receiver 418 (including antenna 420), receive processor 470, multi-antenna receive processor 472 and controller / processor 475.

[0711] As an embodiment, the second receiver 1201 includes the attached Figure 4At 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.

[0712] As an embodiment, the second transmitter 1202 includes the attached Figure 4 The transmitter 418 (including antenna 420), transmit processor 416, multi-antenna transmit processor 471 and controller / processor 475.

[0713] As an embodiment, the second transmitter 1202 includes the attached Figure 4 At least one of the transmitter 418 (including antenna 420), the transmit processor 416, the multi-antenna transmit processor 471 and the controller / processor 475.

[0714] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the 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 function module, and the present application is not limited to any specific form of software and hardware combination. The first type of communication node or UE or terminal in the present application includes but is not limited to mobile phones, tablet computers, notebooks, Internet cards, low-power devices, eMTC (enhanced Machine Type Communication, enhanced machine type communication) equipment, NB-IoT equipment, vehicle-mounted communication equipment, aircraft, airplanes, drones, remote-controlled aircraft and other wireless communication equipment. The second type of communication node or base station or network side equipment in the present application includes but is not limited to macrocellular base stations, microcellular base stations, home base stations, relay base stations, eNB, gNB, transmission and reception nodes TRP (Transmission and Reception Point, transmission and reception point), relay satellites, satellite base stations, aerial base stations and other wireless communication equipment.

[0715] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope 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, 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; wherein the first channel is a main channel of a first basic service set, and the first node belongs to the first basic service set; and a transmission time required for data to be sent by the first node is greater than a time that can be used to transmit data in the second transmission opportunity.

2. The first node according to claim 1, characterized in that: The first moment is determined according to the duration field included in the first message and the end moment of the PPDU (PHYprotocol 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, the fifth message indicating a third transmission opportunity, the sender of the fifth message is a node in a second basic service set, and the second basic service set belongs to the service set group that performs the non-primary channel access coordination; triggering a first operation, wherein 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: A 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 receives 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, the second 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.

8. A method for a first node used 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, 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, 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 the 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, the second 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.

Images