Relay communication method, relay communication device, and wireless communication device

Abstract

Embodiments of the present application provide a relay communication method, a relay communication device, and a wireless communication device. The relay communication device comprises a relay function unit and an A-MPDU deaggregation unit, which is used for communicating with the relay function unit. If the A-MPDU deaggregation unit receives a frame sent by an upper-level node, the A-MPDU deaggregation unit performs A-MPDU deaggregation on the received frame. The relay communication method comprises: receiving an MU-RTS-TXS TF sent by a first node, the MU-RTS-TXS TF indicating a transmission opportunity (TXOP) obtained by the first node; scheduling transmission between the relay communication device and a plurality of second nodes and sharing a portion of time of the obtained TXOP with the relay communication device and the plurality of second nodes for use.

Description

Relay communication method, relay communication device, and wireless communication device Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a relay communication method, relay communication equipment, and wireless communication equipment. Background Art

[0002] The existing 802.11 standards typically consider direct communication between one access point (AP) and one or more associated non-AP stations (STAs). However, when the STA is far from the AP, high path loss or severe interference can lead to poor link quality (SNR or SINR), thus affecting the communication rate. Therefore, in Wi-Fi 8, improving the throughput of distant users through relays has become a research focus. Designing a highly reliable and low-latency relay architecture and protocol is an urgent issue. Therefore, it is necessary to propose a relay communication method, relay communication equipment, and wireless communication equipment to improve existing technologies.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a relay communication method, a relay communication device, and a wireless communication device to improve the problems of the prior art and other problems.

[0005] An embodiment of the present application provides a relay communication device, comprising: a relay function unit, wherein the relay function unit performs local reception or selective forwarding of a Media Access Control (MAC) Protocol Data Unit (MPDU) between an upper-level node and a lower-level node based on a destination address (DA) of a received frame; and an Aggregated Media Access Control Protocol Data Unit (A-MPDU) deaggregation unit, configured to communicate with the relay function unit, wherein if the A-MPDU deaggregation unit receives the frame sent by the upper-level node, the A-MPDU deaggregation unit performs A-MPDU deaggregation on the received frame.

[0006] Through the above technical solution, the relay communication device includes a relay function unit and an A-MPDU deaggregation unit for communicating with the relay function unit, wherein the A-MPDU deaggregation unit performs A-MPDU deaggregation on the received frames sent by the upper-level node, thereby enabling the relay communication device to achieve a highly reliable and low-latency relay (Relay) architecture and protocol.

[0007] An embodiment of the present application provides a relay communication method, which is executed on a relay communication device, wherein the relay communication method includes: receiving a multi-user request to send transmission opportunity sharing trigger frame MU-RTS-TXS TF sent by a first node, wherein the MU-RTS-TXS TF indicates a transmission opportunity TXOP obtained by the first node; scheduling transmission between the relay communication device and multiple second nodes and sharing part of the obtained TXOP time with the relay communication device and the multiple second nodes for use.

[0008] Through the above technical solution, the transmission between the relay communication device and multiple second nodes is scheduled and part of the obtained TXOP time is shared with the relay communication device and the multiple second nodes. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0009] A relay communication method provided by an embodiment of the present application is executed on a relay communication device, wherein the relay communication method includes: sending a multi-user request to send a transmission opportunity sharing trigger frame MU-RTS-TXS TF to at least one first node and / or at least one second node, wherein the MU-RTS-TXS TF instructs the relay communication device to schedule the transmission between the first node and the at least one second node after obtaining the transmission opportunity TXOP and share part of the obtained TXOP time with the first node and the at least one second node for use, wherein at least one of the first node, the relay communication device and the at least one second node is multiple.

[0010] Through the above technical solution, transmission between the first node and at least one second node is scheduled, and a portion of the obtained TXOP time is shared with the first node and the at least one second node, where at least one of the first node, the relay communication device, and the at least one second node is multiple. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0011] An embodiment of the present application provides a relay communication method, which is executed on a first node, wherein the relay communication method includes: sending a multi-user request to send transmission opportunity sharing trigger frame MU-RTS-TXS TF to a relay communication device, wherein the MU-RTS-TXS TF indicates the transmission opportunity TXOP obtained by the first node; scheduling transmission between the relay communication device and multiple second nodes and sharing part of the obtained TXOP time with the relay communication device and the multiple second nodes for use.

[0012] Through the above technical solution, the transmission between the relay communication device and multiple second nodes is scheduled and part of the obtained TXOP time is shared with the relay communication device and the multiple second nodes. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0013] An embodiment of the present application provides a relay communication method, which is executed on a first node, wherein the relay communication method includes: receiving a multi-user request to send transmission opportunity sharing trigger frame MU-RTS-TXS TF sent by a relay communication device, wherein the MU-RTS-TXS TF instructs the relay communication device to schedule transmission between the first node and at least one second node after obtaining a transmission opportunity TXOP and share part of the obtained TXOP time with the first node and the at least one second node for use, wherein at least one of the first node, the relay communication device and the at least one second node is multiple.

[0014] Through the above technical solution, transmission between the first node and at least one second node is scheduled, and a portion of the obtained TXOP time is shared with the first node and the at least one second node, where at least one of the first node, the relay communication device, and the at least one second node is multiple. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0015] A wireless communication device provided in an embodiment of the present application includes: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the above-mentioned relay communication method.

[0016] The relay communication device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned relay communication method.

[0017] The first node provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned relay communication method.

[0018] The chip provided in the embodiment of the present application is used to implement the above-mentioned relay communication method.

[0019] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned relay communication method.

[0020] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned relay communication method.

[0021] The computer program product provided in an embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned relay communication method.

[0022] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned method for relay communication.

[0023] Through the above technical solution, the relay communication device includes a relay function unit and an A-MPDU deaggregation unit for communicating with the relay function unit, wherein the A-MPDU deaggregation unit performs A-MPDU deaggregation on the frames sent by the received upper-level node, thereby enabling the relay communication device to implement a highly reliable and low-latency relay (Relay) architecture and protocol. Through the above technical solution, the transmission between the relay communication device and multiple second nodes is scheduled and part of the obtained TXOP time is shared with the relay communication device and the multiple second nodes. In this way, relay (Relay) link scheduling and transmission design can be implemented in different scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0025] FIG1A is a schematic diagram of a relay communication system architecture provided in an embodiment of the present application;

[0026] FIG1B is a schematic diagram of a relay communication system architecture provided in an embodiment of the present application;

[0027] FIG1C is a schematic diagram of a relay communication system architecture provided in an embodiment of the present application;

[0028] FIG2A is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0029] FIG2B is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0030] FIG2C is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0031] FIG2D is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0032] FIG3 is a schematic diagram of a network topology for relay transmission according to an embodiment of the present application;

[0033] FIG4A is a schematic diagram of a scenario of scheduling and transmission of relay communications provided in an embodiment of the present application;

[0034] FIG4B is a schematic diagram of a scenario of scheduling and transmission of relay communication provided in an embodiment of the present application;

[0035] FIG4C is a schematic diagram of a scenario of scheduling and transmission of relay communication provided in an embodiment of the present application;

[0036] FIG4D is a schematic diagram of a scenario of scheduling and transmission of relay communication provided in an embodiment of the present application;

[0037] FIG4E is a schematic diagram of a scenario of scheduling and transmission of relay communications provided in an embodiment of the present application;

[0038] FIG4F is a schematic diagram of a scenario of scheduling and transmission of relay communication provided in an embodiment of the present application;

[0039] FIG4G is a schematic diagram of a scenario of scheduling and transmission of relay communications provided in an embodiment of the present application;

[0040] FIG4H is a schematic diagram of a scenario of scheduling and transmission of relay communications provided in an embodiment of the present application;

[0041] FIG4I is a schematic diagram of a scenario of scheduling and transmission of relay communications provided in an embodiment of the present application;

[0042] FIG5 is a schematic structural diagram of a wireless communication device provided in an embodiment of the present application;

[0043] FIG6 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0044] FIG7 is a schematic block diagram of a wireless communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0046] It should be understood that the term "and / or" in this document merely describes the association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the associated objects are in an "or" relationship. In some embodiments of the present invention, "AP" can represent "AP STA" or "AP MLD." This means that the term "AP" as used herein may be used interchangeably with "AP STA" or "AP MLD." "STA" can represent "AP STA" or "non-AP STA" or "AP MLD" or "non-AP MLD." This means that the term "STA" as used herein may be used interchangeably with "AP STA" or "AP MLD" or "non-AP STA" or "non-AP MLD." "non-AP STA" can represent "non-AP MLD." This means that the term "non-AP STA" as used herein may be used interchangeably with "non-AP STA" or "non-AP MLD."

[0047] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

[0048] The technical solutions of the embodiments of the present application can be applied to various relay communication systems. For example, a relay communication device 100A used in the embodiments of the present application is shown in FIG1A . The relay communication device 100A may include a relay function unit 101A. The relay function unit 101A may perform local reception or selective forwarding of a media access control protocol data unit (MPDU) between an upper-level node and a lower-level node based on the destination address (DA) of the received frame. The frame is a unicast frame, a broadcast frame, or a multicast frame.

[0049] The relay communication device 100A further includes an aggregated media access control protocol data unit (A-MPDU) deaggregation unit 102A. The A-MPDU deaggregation unit 102A is configured to communicate with the relay function unit 101A. If the A-MPDU deaggregation unit 102A receives the frame sent by the upper-level node, the A-MPDU deaggregation unit 102A performs A-MPDU deaggregation on the received frame.

[0050] Through the above technical solution, the relay communication device 100A includes a relay function unit 101A and an A-MPDU deaggregation unit 102A for communicating with the relay function unit 101A, wherein the A-MPDU deaggregation unit 102A performs A-MPDU deaggregation on the received frames sent by the upper-level node, thereby enabling the relay communication device 100A to achieve a highly reliable and low-latency relay (Relay) architecture and protocol.

[0051] Specifically, in some embodiments of the present invention, after receiving a unicast frame, the relay function unit 101A of the relay communication device 100A performs the following operations: the relay function unit 101A examines the (A-)MPDU received at the relay via the wireless medium (WM). If the DA indicated therein matches the relay address, the (A-)MPDU is delivered to the local higher-level entity. Otherwise, the (A-)MPDU is forwarded to the next node via the WM using the four-address frame format or the A-MPDU format.

[0052] Specifically, in some embodiments of the present invention, after the relay communication device 100A receives a broadcast frame or a multicast frame, the relay function unit 101A behaves as follows: the (A-)MPDU with the destination address is the group address (including the MPDU) received at the relay through the WM, is passed by the relay function unit 101A, and then forwarded to the next node through the WM, using the four-address frame format or the A-MPDU format.

[0053] In some embodiments of the present invention, the relay communication device 100A may be a non-multi-link device station (non-MLD STA) or a multi-link device station (MLD STA).

[0054] As shown in FIG. 1B , the relay communication device 100B is a non-multi-link device station (non-MLD STA).

[0055] In some embodiments of the present invention, the relay communication device 100B includes a relay function unit 101B. The relay function unit 101B can perform local reception or selective forwarding of media access control protocol data units (MPDUs) between an upper-level node and a lower-level node based on the destination address (DA) of the received frame. The relay communication device 100B also includes an aggregated media access control protocol data unit (A-MPDU) deaggregation unit 102B. The A-MPDU deaggregation unit 102B is configured to communicate with the relay function unit 101B. If the A-MPDU deaggregation unit 102B receives the frame sent by the upper-level node, the A-MPDU deaggregation unit 102B performs A-MPDU deaggregation on the received frame. The frame is a unicast frame, a broadcast frame, or a multicast frame.

[0056] Through the above technical solution, the relay communication device 100B includes a relay function unit 101B and an A-MPDU deaggregation unit 102B for communicating with the relay function unit 101B, wherein the A-MPDU deaggregation unit 102B performs A-MPDU deaggregation on the received frames sent by the upper-level node, thereby enabling the relay communication device 100B to achieve a highly reliable and low-latency relay (Relay) architecture and protocol.

[0057] In some embodiments of the present invention, the relay communication device 100B further includes an MPDU header and cyclic redundancy check CRC verification unit 103B, which is used to communicate with the A-MPDU deaggregation unit 102B, wherein if the MPDU header and CRC verification unit 103B receives the frame sent by the upper-level node through the A-MPDU deaggregation unit 102B, the MPDU header and CRC verification unit 103B will perform MPDU header and CRC verification on the received frame.

[0058] In some embodiments of the present invention, the relay communication device 100B also includes an address filtering unit 104B, which is used to communicate with the MPDU header and CRC verification unit 103B, wherein if the address filtering unit 104B receives the frame sent by the upper-level node through the MPDU header and CRC verification unit 103B, the address filtering unit 104B will perform address filtering on the received frame.

[0059] In some embodiments of the present invention, the relay communication device 100B further includes a block confirmation scoreboard 105B, which is used to communicate with the address filtering unit 104B, wherein if the block confirmation scoreboard 105B receives the frame sent by the upper-level node through the address filtering unit 104B, the block confirmation scoreboard 105B will perform confirmation scoring on the received frame.

[0060] In some embodiments of the present invention, the relay communication device 100B further includes a duplicate detection unit 106B for communicating with the block confirmation scoreboard 105B, wherein if the duplicate detection unit 106B receives the frame sent by the upper-level node through the block confirmation scoreboard 105B, the duplicate detection unit 106B performs duplicate detection on the received frame.

[0061] In some embodiments of the present invention, the relay communication device 100B further includes a replay detection unit 107B configured to communicate with the duplicate detection unit 106B. If the replay detection unit 107B receives the frame sent by the upper-level node through the duplicate detection unit 106B, the replay detection unit 107B performs replay detection on the received frame. The replay detection unit 107B is configured to receive data or robust management frames from another station (STA) to detect whether the received data or robust management frames are unauthorized retransmissions. That is, the STA can be an AP STA or a non-AP STA.

[0062] In some embodiments of the present invention, the relay communication device 100B further includes an MPDU header and CRC creation unit 108B for communicating with the relay function unit 101B, wherein if the MPDU header and CRC creation unit 108B receives the frame sent by the next-level node through the relay function unit 101B, the MPDU header and CRC creation unit 108B performs MPDU header and CRC creation on the received frame.

[0063] In some embodiments of the present invention, the relay communication device 100B further includes an A-MPDU aggregation unit 109B for communicating with the MPDU header and CRC creation unit 108B, wherein if the A-MPDU aggregation unit 109B receives the frame sent by the next-level node through the MPDU header and CRC creation unit 108B, the A-MPDU aggregation unit 109B performs A-MPDU aggregation on the received frame.

[0064] In some embodiments of the present invention, the relay communication device 100B further includes an MPDU encryption and integrity unit 110B, and the relay function unit 100B is configured between the MPDU encryption and integrity unit 110B and the MPDU header and CRC creation unit 108B to perform transmission. In some embodiments of the present invention, the relay communication device 100B further includes an MPDU decryption and integrity unit 111B, and the relay function unit 100B is configured between the replay detection unit 107B and the MPDU decryption and integrity unit 111B to perform reception.

[0065] Specifically, in some embodiments of the present invention, as shown in FIG1B , the architecture (data plane architecture) of a relay communication device 100B as a non-MLD HT / HE / EHT STA includes a relay function unit 101B compared to the data plane architecture of a traditional non-MLD HT / HE / EHT STA. In some embodiments of the present invention, a non-MLD HT / HE / EHT STA includes both AP STAs and non-AP STAs. This means that the relay communication device 100B can be a STA with AP functionality, i.e., an AP STA, or a STA without AP functionality, i.e., a non-AP STA. During transmission, the relay function unit 101B is located between the MPDU Encryption (TX) and Integrity Unit 110B and the MPDU Header + CRC Creation (TX) Unit 108B. The relay function unit 101B is located between the replay detection unit 107B (Replay Detection in Relay Unit) and the MPDU decryption and integrity unit 111B (MPDU Decryption (RX) and Integrity Unit) during reception.

[0066] The function of the relay function unit 101B (Relay Function Unit) is to perform local reception or selective forwarding of (A-)MPDUs between the upper-level node and the lower-level node based on the destination address (DA) of the received frame. If the DA of the received frame is the relay communication device 100B (the relay itself), local reception is performed and MAC layer upper-layer operations such as MPDU Decryption are no longer forwarded; if the DA of the received frame is another node, the received frame fragments are reselected at the relay function unit 101B (the reselection rule is to only forward successfully received frame fragments based on the results of the block acknowledgment scoreboard 105B (Block Ack Score Boarding)) and forwarded to the next step of processing, such as MPDU Header+CRC Creation and A-MPDU Aggregation.

[0067] Furthermore, the replay detection unit 107B and its operations are newly added to the traditional HT / HE / EHT STA architecture. Their primary functions are as follows: The replay detection mechanism defines a method by which a relay receiving data or robust management frames from another STA can detect whether the received frames are unauthorized retransmissions. This replay protection mechanism is provided for data frames of STAs using the Robust Security Network Association (RSNA) mechanism. A robust management frame replay protection mechanism is also provided for STAs using the Cipher-block chaining Message Authentication Code Protocol (CCMP) with Counter Mode, the Galois Counter Mode Protocol (GCMP), and the Broadcast / Multicast Integrity Protocol (BIP). In some embodiments of the present invention, a STA includes an AP STA or a non-AP STA. That is, a STA can be either an AP STA or a non-AP STA.

[0068] Specifically, in some embodiments of the present invention, as shown in FIG1B , a relay communication device 100B receives a frame sent by an upper-level node. An example process in the data plane architecture is as follows:

[0069] 1) Perform A-MPDU de-aggregation.

[0070] 2) Perform MPDU Header + CRC Validation.

[0071] 3) Perform Address 1 address filtering.

[0072] 4) Perform Block Ack Scoreboarding.

[0073] 5) Perform Duplicate Detection (optional step).

[0074] 6) Perform Replay Detection (optional step).

[0075] The relay communication device 100B then repackages the received data at the relay function unit 101B and forwards it to the next-level node according to the instructions of the relevant frame. The example process in the data plane architecture is as follows:

[0076] 1) Perform MPDU Header + CRC Creation.

[0077] 2) Perform A-MPDU Aggregation.

[0078] The technical effect that can be achieved by this architectural design is as follows: After receiving the data sent by the upper-level node, the relay communication device 100B only needs to deaggregate the A-MPDU, then verify the MPDU, and then forward it through the relay function unit 101B through a few simple steps (as described above). After re-aggregating the MPDU, it is sent to the next-level node without going through other MAC processing (such as the MPDU decryption / encryption unit (MPDU Decryption / Encryption Unit), block acknowledgment buffering and reordering unit (Block Ack Buffering and Reordering Unit)), which greatly saves the processing time of the relay data packet and can achieve low-latency relay operation.

[0079] It's worth noting that Figure 1B also illustrates the data plane architecture when relay communication device 100B functions as a traditional AP / non-AP STA (i.e., without relay functionality). In this case, Figure 1B does not include relay function unit 101B or replay detection unit 107B, located between relay function unit 101B and duplicate detection unit 106B, and the steps associated with them. The remaining steps may not necessarily be executed in their entirety; only portions may be performed based on specific requirements.

[0080] Specifically, in some embodiments of the present invention, after receiving a unicast frame, the relay function unit 101B of the relay communication device 100B behaves as follows: the relay function unit 101B examines the (A-)MPDU received at the relay via the WM. If the DA matches the relay address, the (A-)MPDU is delivered to the local higher-level entity. Otherwise, the (A-)MPDU is forwarded to the next node via the WM using the four-address frame format or the A-MPDU format.

[0081] Specifically, in some embodiments of the present invention, after the relay communication device 100B receives a broadcast frame or a multicast frame, the relay function unit 101B behaves as follows: the (A-)MPDU with the destination address is the group address (including the MPDU) received at the relay through the WM, is passed by the relay function unit 101B, and then forwarded to the next node through the WM, using the four-address frame format or the A-MPDU format.

[0082] Specifically, for Block Ack protocols that are not protected Block Ack protocols, the "MPDU Decryption (RX) and Integrity (MPDU Decryption and Integrity Unit 111B)" and "Block Ack Buffering and Reordering" procedures can be performed in either order (RX). For protected Block Ack protocols, these two procedures should be performed in the order shown.

[0083] As shown in Figure 1C, the relay communication device 100C is a multi-link device station (MLD STA). The frame is a unicast frame, a broadcast frame, or a multicast frame. In some embodiments of the present invention, the relay communication device 100C includes both AP MLD and non-AP MLD. That is, the relay communication device 100C can be an AP MLD with AP functionality or a non-AP MLD without AP functionality. Furthermore, the relay communication device 100C can be an MLD that has both AP MLD and non-AP MLD capabilities.

[0084] In some embodiments of the present invention, the relay communication device 100C includes a relay function unit 101C. The relay function unit 101C can perform local reception or selective forwarding of media access control protocol data units (MPDUs) between an upper-level node and a lower-level node based on the destination address (DA) of the received frame. The relay communication device 100C also includes an aggregated media access control protocol data unit (A-MPDU) deaggregation unit 102C. The A-MPDU deaggregation unit 102C is configured to communicate with the relay function unit 101C. If the A-MPDU deaggregation unit 102C receives the frame sent by the upper-level node, the A-MPDU deaggregation unit 102C performs A-MPDU deaggregation on the received frame.

[0085] Through the above technical solution, the relay communication device 100C includes a relay function unit 101C and an A-MPDU deaggregation unit 102C for communicating with the relay function unit 101C, wherein the A-MPDU deaggregation unit 102C performs A-MPDU deaggregation on the received frames sent by the upper-level node, thereby enabling the relay communication device 100C to achieve a highly reliable and low-latency relay (Relay) architecture and protocol.

[0086] In some embodiments of the present invention, the relay communication device 100C further includes an MPDU header and cyclic redundancy check CRC verification unit 103C, which is used to communicate with the A-MPDU deaggregation unit 102C, wherein if the MPDU header and CRC verification unit 103C receives the frame sent by the upper-level node through the A-MPDU deaggregation unit 102C, the MPDU header and CRC verification unit 103C will perform MPDU header and CRC verification on the received frame.

[0087] In some embodiments of the present invention, the relay communication device 100C also includes an address filtering unit 104C, which is used to communicate with the MPDU header and CRC verification unit 103C, wherein if the address filtering unit 104C receives the frame sent by the upper-level node through the MPDU header and CRC verification unit 103C, the address filtering unit 104C will perform address filtering on the received frame.

[0088] In some embodiments of the present invention, the relay communication device 100C further includes a block confirmation scoreboard 105C, which is used to communicate with the address filtering unit 104C, wherein if the block confirmation scoreboard 105C receives the frame sent by the upper-level node through the address filtering unit 104C, the block confirmation scoreboard 105C will perform confirmation scoring on the received frame.

[0089] In some embodiments of the present invention, the relay communication device 100C further includes a duplicate detection unit 106C, which is used to communicate with the block confirmation scoreboard 105C, wherein if the duplicate detection unit 106C receives the frame sent by the upper-level node through the block confirmation scoreboard 105C, the duplicate detection unit 106C will perform duplicate detection on the received frame.

[0090] In some embodiments of the present invention, the relay communication device 100C further includes a replay detection unit 107C configured to communicate with the duplicate detection unit 106C. If the replay detection unit 107C receives the frame sent by the upper-level node via the duplicate detection unit 106C, the replay detection unit 107C performs replay detection on the received frame. The replay detection unit 107C is configured to receive data or a robust management frame from another station (STA) to detect whether the received data or robust management frame is an unauthorized retransmission. In some embodiments of the present invention, the STA includes an AP MLD or a non-AP MLD. That is, the STA can be both an AP MLD and a non-AP MLD.

[0091] In some embodiments of the present invention, the relay communication device 100C further includes an MPDU header and CRC creation unit 108C for communicating with the relay function unit 101C, wherein if the MPDU header and CRC creation unit 108C receives the frame sent by the next-level node through the relay function unit 101C, the MPDU header and CRC creation unit 108C performs MPDU header and CRC creation on the received frame.

[0092] In some embodiments of the present invention, the relay communication device 100C further includes an A-MPDU aggregation unit 109C for communicating with the MPDU header and CRC creation unit 108C, wherein if the A-MPDU aggregation unit 109C receives the frame sent by the next-level node through the MPDU header and CRC creation unit 108C, the A-MPDU aggregation unit 109C performs A-MPDU aggregation on the received frame.

[0093] In some embodiments of the present invention, the relay communication device 100C further includes an MPDU encryption unit 110C and a traffic identifier TID to link mapping unit 111C, and the relay function unit 100C is configured between the MPDU encryption unit 110C and the TID to link mapping unit 111C to perform transmission.

[0094] In some embodiments of the present invention, the relay communication device 100C further includes a link merging unit 112C. The relay function unit 100C is configured between the link merging unit 112C and the block confirmation scoreboard 105C to perform reception.

[0095] In some embodiments of the present invention, the relay communication device further includes an MLD upper layer media access control MAC sublayer 113C, and at least one of the relay function unit 101C, the MPDU encryption unit 110C, the TID-to-link mapping unit 111C, the link merging unit 112C, and the block acknowledgment scoreboard 105C is configured in the MLD upper layer MAC sublayer 113C.

[0096] Specifically, in some embodiments of the present invention, as shown in FIG. 1C , when the relay communication device 100C is an MLD, a data plane architecture is added, compared to a traditional MLD data plane architecture, to a relay function unit 101C. During transmission, the relay function unit 101C is located between the MPDU encryption unit 110C and the TID-to-link mapping unit 111C. During reception, the relay function unit 101C is located between the link merging unit 112C and the block acknowledgment scoreboard 105C of the MLD upper MAC sublayer 113C.

[0097] The function of the relay function unit 101C (Relay Function Unit) is to perform local reception or selective forwarding of (A-)MPDUs between the upper-level node and the lower-level node based on the destination address (DA) of the received frame. If the DA of the received frame is the relay communication device 100C (the relay itself), local reception is performed and MAC layer upper-layer operations such as MPDU Decryption are no longer forwarded; if the DA of the received frame is another node, the received frame fragments are reselected at the relay function unit 101C (the reselection rule is to only forward successfully received frame fragments based on the results of the block acknowledgment scoreboard 105C (Block Ack Score Boarding)) and forwarded to the next step of processing, such as MPDU Header+CRC Creation and A-MPDU Aggregation.

[0098] In addition, two additional units, Replay Detection (in Relay) 107C and Duplicate Detection (in Relay) 106C, and their steps are defined. Their functions are as follows:

[0099] Replay Detection Unit 107C (Replay Detection (in Relay)): The replay detection mechanism defines a method by which a relay receiving data or robust management frames from another STA can detect whether the received frame is an unauthorized retransmission. This replay protection mechanism is provided for data frames of STAs using the Robust Security Network Association (RSNA) mechanism. A robust management frame replay protection mechanism is also provided for STAs using the Cipher-block chaining Message Authentication Code Protocol (CCMP) with Counter Mode, the Galois Counter Mode Protocol (GCMP), and the Broadcast / Multicast Integrity Protocol (BIP). In some embodiments of the present invention, the STA includes an AP MLD or a non-AP MLD. That is, the STA can be both an AP MLD and a non-AP MLD.

[0100] Duplicate Detection (in Relay) 106C: Due to the MAC-level acknowledgment and retransmission involved in the protocol, a relay may receive a frame multiple times. The Duplicate Detection (in Relay) process attempts to filter out these duplicates.

[0101] With this design, the relay function unit 101C, located in the MAC sublayer 113C above the MLD layer, can flexibly select one or more links to receive relay frames and then use another link or links to forward the relay frames. The links selected by the relay function unit for receiving and sending frames can be identical, completely different, or partially identical, and this is not a limitation of the present invention.

[0102] Specifically, in some embodiments of the present invention, as shown in FIG1C , a relay communication device 100C receives a frame sent by an upper-level node. An example process in the data plane architecture is as follows:

[0103] 1) Perform A-MPDU de-aggregation.

[0104] 2) Perform MPDU Header + CRC Validation.

[0105] 3) Perform Address 1address filtering.

[0106] 4) Perform Block Ack Scoreboarding.

[0107] 5) Perform Link Merging (optional step).

[0108] 6) Perform Duplicate Detection (optional step).

[0109] 7) Perform Replay Detection (optional step).

[0110] The relay communication device 100C then repackages the received data at the relay function unit 101C and forwards it to the next-level node according to the instructions of the relevant frame. The example process in the data plane architecture is as follows:

[0111] 1) Perform TID-to-Link mapping (optional step).

[0112] 2) Perform MPDU Header + CRC Creation.

[0113] 3) Perform A-MPDU Aggregation.

[0114] The technical effect that can be achieved by this architectural design is as follows: After receiving the data sent by the upper-level node, the relay communication device 100C only needs to deaggregate the A-MPDU, then verify the MPDU, and then forward it through the Relay Function through a few simple steps (as described above). After reaggregating the MPDU, it is sent to the next-level node. It does not need to go through the entire upper-layer MAC process (such as the MPDU decryption / encryption unit (MPDU Decryption / Encryption Unit), block acknowledgment buffering and reordering unit (Block Ack Buffering and Reordering Unit)), which greatly saves the processing time of the relay data packet and can achieve low-latency relay operation.

[0115] It's worth noting that Figure 1C also illustrates the data plane architecture for relay communication device 100C operating as a traditional MLD (i.e., without relay functionality). In this case, relay function unit 101C and its associated steps are not shown in Figure 1C . The remaining steps may not necessarily be executed in their entirety; only portions may be performed based on specific requirements.

[0116] Specifically, in some embodiments of the present invention, after receiving a unicast frame, the relay function unit 101C of the relay communication device 100C behaves as follows: the relay function unit 101C examines the (A-)MPDU received at the relay via the WM. If the DA matches the relay address, the (A-)MPDU is delivered to the local higher-level entity. Otherwise, the (A-)MPDU is forwarded to the next node via the WM using the four-address frame format or the A-MPDU format.

[0117] Specifically, in some embodiments of the present invention, after the relay communication device 100C receives a broadcast frame or a multicast frame, the relay function unit 101C behaves as follows: an (A-)MPDU with a destination address is a group address (including an MPDU) received at the relay through the WM, is passed by the relay function unit 101C, and then forwarded to the next node through the WM, using a four-address frame format or an A-MPDU format.

[0118] Specifically, in some embodiments of the present invention, if all attached non-AP STAs to which the TID of the MPDU carried in the frame is mapped are in a doze state, the AP MLD buffers the individually addressed frame. Specifically, in some embodiments of the present invention, the TID-to-link mapping control can transmit the MPDU in the link.

[0119] Figure 2A is a flow chart of the relay communication method provided in an embodiment of the present application. As shown in Figure 2A, the relay communication method is executed on a relay communication device and includes at least one of the following operations: Operation 201A: Receive a multi-user request to transmit transmission opportunity sharing trigger frame MU-RTS-TXS TF sent by a first node. The MU-RTS-TXS TF indicates the transmission opportunity TXOP obtained by the first node. Operation 202A: Schedule the transmission between the relay communication device and multiple second nodes and share part of the time of the obtained TXOP with the relay communication device and the multiple second nodes. In the scheme shown in Figure 2A, the MU-RTS-TXS TF is sent by the first node to the relay communication device and is used for scheduling subsequent data transmission between the relay communication device, the second node and the first node.

[0120] Through the above technical solution, the transmission between the relay communication device and multiple second nodes is scheduled and part of the obtained TXOP time is shared with the relay communication device and the multiple second nodes. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0121] FIG2B is a flow chart of a relay communication method provided in an embodiment of the present application. As shown in FIG2B , the relay communication method provided in an embodiment of the present application is executed in a relay communication device, wherein the relay communication method includes: Operation 201B: Sending a multi-user request to transmit transmission opportunity sharing trigger frame MU-RTS-TXS TF to at least one first node and / or at least one second node. The MU-RTS-TXS TF instructs the relay communication device to schedule transmission between the first node and at least one second node after obtaining a transmission opportunity TXOP and share part of the obtained TXOP time with the first node and the at least one second node, wherein at least one of the first node, the relay communication device, and the at least one second node is plural. In the scheme shown in FIG2B , the MU-RTS-TXS TF is sent by the relay communication device to the first and / or second node and is used to schedule subsequent data transmission between the relay communication device, the second node, and the first node.

[0122] Through the above technical solution, transmission between the first node and at least one second node is scheduled, and a portion of the obtained TXOP time is shared with the first node and the at least one second node, where at least one of the first node, the relay communication device, and the at least one second node is multiple. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0123] FIG2C is a flow chart of a relay communication method provided in an embodiment of the present application. As shown in FIG2C , the relay communication method provided in an embodiment of the present application is executed on a first node, wherein the relay communication method includes: Operation 201C: Sending a multi-user request to transmit transmission opportunity sharing trigger frame MU-RTS-TXS TF to a relay communication device. The MU-RTS-TXS TF indicates the transmission opportunity TXOP obtained by the first node. Operation 202C: Scheduling transmissions between the relay communication device and multiple second nodes and sharing a portion of the obtained TXOP time with the relay communication device and the multiple second nodes. In one embodiment, the first node is, for example, an AP, and the second node is, for example, a STA. In another embodiment, the first node is, for example, a STA, and the second node is, for example, an AP. In the scheme shown in FIG2C , the MU-RTS-TXS TF is sent by the first node to the relay communication device and is used to schedule subsequent data transmissions between the relay communication device, the second nodes, and the first node.

[0124] Through the above technical solution, the transmission between the relay communication device and multiple second nodes is scheduled and part of the obtained TXOP time is shared with the relay communication device and the multiple second nodes. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0125] FIG2D is a flow chart of a relay communication method provided in an embodiment of the present application. As shown in FIG2D , the relay communication method provided in an embodiment of the present application is executed at a first node, wherein the relay communication method includes: Operation 201D: Receiving a multi-user request to transmit transmission opportunity sharing trigger frame (MU-RTS-TXS TF) sent by a relay communication device. The MU-RTS-TXS TF instructs the relay communication device, after obtaining a transmission opportunity (TXOP), to schedule transmission between the first node and at least one second node and share a portion of the obtained TXOP time with the first node and the at least one second node. At least one of the first node, the relay communication device, and the at least one second node is plural. In one embodiment, the first node is, for example, an AP, and the second node is, for example, a STA. In another embodiment, the first node is, for example, a STA, and the second node is, for example, an AP. In the scheme shown in FIG2D , the MU-RTS-TXS TF is sent by the relay communication device to the first node and is used to schedule subsequent data transmissions between the relay communication device, the second node, and the first node.

[0126] Through the above technical solution, transmission between the first node and at least one second node is scheduled, and a portion of the obtained TXOP time is shared with the first node and the at least one second node, where at least one of the first node, the relay communication device, and the at least one second node is multiple. In this way, relay link scheduling and transmission design can be implemented in different scenarios.

[0127] In some embodiments of the present invention, the relay communication method further includes: the relay communication device performing data transmission with the first node before obtaining the portion of the TXOP time. For example, before the first node sends the MU-RTS-TXS TF to the relay communication device, the first node may first send data to be relayed to the relay communication device; and after the first node sends the MU-RTS-TXS TF to the relay communication device, the first node may stop data transmission within the TXOP time window.

[0128] In some embodiments of the present invention, the relay communication method further includes: the relay communication device performing data transmission with the first node after obtaining the portion of the TXOP time. For example, after the relay communication device receives the MU-RTS-TXS TF, the relay communication device may relay data received from the second node to the first node within the time window of the shared TXOP.

[0129] In some embodiments of the present invention, the relay communication method further includes determining an allocation strategy for the TXOP with respect to the relay communication device and the plurality of second nodes. In some embodiments of the present invention, the allocation strategy for the TXOP is determined by the first node based on the buffer status of the relay communication device and the plurality of second nodes. In some embodiments of the present invention, the allocation strategy for the TXOP is determined by the relay communication device based on the buffer status of the first node and the plurality of second nodes. In some embodiments of the present invention, the buffer carries the data service type and the corresponding data volume cached by the device. When determining the allocated duration during TXOP sharing, TXOPs can be allocated preferentially to devices with services having low-latency characteristics. Longer durations can also be allocated to services with large buffer volumes, and shorter durations can be allocated to services with small buffer volumes, thereby better enabling priority transmission of low-latency services to reduce latency.

[0130] In some embodiments of the present invention, sharing the obtained part of the TXOP time with the relay communication device and the multiple second nodes for use includes: the relay communication device shares the part of the TXOP time with at least one of the multiple second nodes for use by sending indication signaling to the multiple second nodes, so as to receive data sent by at least one of the multiple second nodes during the part of the time.

[0131] In some embodiments of the present invention, when the channel idle duration is equal to the interframe space (xIFS), the relay communication device receives data sent by the multiple second nodes and relays the data to the first node. The length of the xIFS is greater than the length of the short interframe space (SIFS), and the xIFS is less than or equal to the length of the point coordination function interframe space (PIFS). In this way, regardless of whether the second node can directly establish communication with the first node and receive instructions, the second node can obtain a TXOP from the relay communication device and transmit data to the relay communication device or the first node.

[0132] In some embodiments of the present invention, the scheduling includes: receiving data to be transmitted and a receiving address RA or a destination address DA of the data to be transmitted, and transmitting the data to be transmitted according to the RA or the DA.

[0133] In some embodiments of the present invention, there are multiple relay communication devices, the RAs of the data to be transmitted respectively indicate the multiple relay communication devices, and the DAs of the data to be transmitted respectively indicate the multiple second nodes. In this manner, the same data to be transmitted can be relayed to different second nodes via multiple relay communication devices, thereby improving transmission efficiency.

[0134] In some embodiments of the present invention, there are multiple relay communication devices, the RAs of the data to be transmitted respectively indicate the multiple relay communication devices, and the DAs of the data to be transmitted indicate the same second node. In this manner, the data to be transmitted can be relayed to the same second node via multiple relay devices, thereby improving transmission reliability by providing redundant data.

[0135] In some embodiments of the present invention, there are multiple relay communication devices, multiple data to be transmitted, the RAs of the multiple data to be transmitted respectively indicate the multiple relay communication devices, and the DAs of the multiple data to be transmitted respectively indicate the multiple second nodes. In this manner, the multiple data to be transmitted can be relayed to different second nodes via the multiple relay communication devices, thereby improving transmission efficiency.

[0136] In some embodiments of the present invention, there are multiple relay communication devices, multiple data to be transmitted, the RAs of the multiple data to be transmitted respectively indicate the multiple relay communication devices, and the DAs of the multiple data to be transmitted indicate the same second node. In this manner, the multiple data to be transmitted can be relayed to the same second node via the multiple relay communication devices, thereby providing redundant transmission paths to improve transmission reliability.

[0137] FIG3 is a schematic diagram of a relay transmission network topology provided in an embodiment of the present application. As shown in FIG3 , the relay transmission network topology provided in an embodiment of the present application may include one or more APs (e.g., AP 1), one or more relay nodes (e.g., Relay 1 to Relay b), and one or more STAs (e.g., STA 1 to STA c). Specifically, the relay transmission scenarios can be categorized as follows:

[0138] 1) 1 AP <-> 1 Relay node <-> 1 STA;

[0139] 2) 1 AP <-> 1 Relay node <-> multiple STAs;

[0140] 3) 1 AP <-> multiple relay nodes <-> 1 STA;

[0141] 4) 1 AP <-> multiple relay nodes <-> multiple STAs;

[0142] 5) Multiple APs <-> 1 Relay node <-> 1 STA;

[0143] 6) Multiple APs <-> 1 Relay node <-> multiple STAs;

[0144] 7) Multiple APs <-> Multiple Relay nodes <-> 1 STA;

[0145] 8) Multiple APs <-> Multiple Relay nodes <-> Multiple STAs

[0146] The relay node is, for example, the relay communication device 100A shown in FIG1A , the relay node is, for example, the relay communication device 100B shown in FIG1B , and the relay node is, for example, the relay communication device 100C shown in FIG1C .

[0147] It's worth noting that the relay transmission scenario is described using the example of an AP obtaining a TXOP and sharing it with a relay node and / or STA. The AP corresponds to the first node described above, and the STA (which in some scenarios also includes the AP and / or relay) corresponds to the second node described above. However, the present invention is not limited to this. For example, a non-AP STA may obtain a TXOP and share it with an AP and / or relay node (i.e., the STA serves as the first node mentioned above), or a relay node may obtain a TXOP and share it with an AP and / or STA. These details will not be elaborated in the present invention.

[0148] In addition, the present invention shares part or all of the time resources of the obtained TXOP with other devices for relay transmission after the AP / Relay node / STA obtains the TXOP. Alternatively, the present invention shares part or all of the frequency / channel / RU resources of the obtained TXOP with other devices for relay transmission after the AP / Relay node / STA obtains the TXOP (for example, after AP 1 obtains the TXOP, it sends data to Relay 1 through channel 1, and then AP 1 schedules Relay 1 to use channel 2 to send the relayed data to STA 1). Due to space limitations, the present invention will not elaborate on each one.

[0149] In relay transmission scenarios, APs (such as AP 1 to AP a) and STAs (such as STA 1 to STA c) may be far apart, and their wireless signals may not reach each other, resulting in a hidden terminal problem. In this case, the AP and STA may simultaneously (obtain TXOP) and send (Data) frames to the relay node, causing signal collisions and the relay node failing to receive signals from the AP and STA. To resolve this potential conflict, 1) the AP can send an RTS frame (or other applicable frame) to the relay node when it detects channel idleness through CCA. The relay node immediately responds with a CTS frame (or other corresponding frame) after receiving the RTS frame for a SIFS period. Since the relay node's signal can reach the STA, the STA, upon receiving the CTS frame sent by the relay node, knows that another device (such as the AP) is currently communicating with the relay node. The STA then suspends sending (data) frames to the relay node. Alternatively, 2) the STA can send an RTS frame (or other applicable frame) to the relay node when it detects channel idleness through CCA. The relay node immediately responds with a CTS frame (or other corresponding frame) after receiving the RTS frame for a SIFS period. Since the relay node's signal can reach the AP, the AP, upon receiving the CTS frame sent by the relay node, knows that another device (such as the STA) is currently communicating with the relay node. The AP then suspends sending (data) frames to the relay node. This resolves the potential conflict caused by the aforementioned hidden terminal problem. It is worth noting that this method is applicable to all processes of relay transmission, such as before the AP transmits data to the Relay node, or after the AP shares the TXOP with other nodes.

[0150] Scenario 1: Scheduling and transmission from one AP to one relay node to one STA

[0151] Figure 4A is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 4A, there is only one AP (i.e., AP 1) and one Relay node (i.e., Relay 1) in the BSS, and the Relay node only provides relay service to one STA (i.e., STA 1).

[0152] This example illustrates a process in which, after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1, and then AP 1 shares part of the TXOP time obtained with Relay 1 and STA 1 for relay transmission (for example, Relay 1 transmits data to AP 1). However, the present invention is not limited to this process. Alternatively, after obtaining a TXOP, AP 1 first shares part of the TXOP time with Relay 1 and STA 1 for relay transmission (for example, STA 1 transmits data to Relay 1), and then transmits data between Relay 1 and AP 1 (for example, Relay 1 transmits data to AP 1).

[0153] The steps in FIG. 4A are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0154] 1) After AP 1 obtains a TXOP, it sends a data frame. The RA field of the data frame is set to Relay 1's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that the data frame originates from AP 1, is sent by AP 1 to Relay 1, and is destined for STA 1.

[0155] 2) Relay 1 receives the data frame sent by AP 1 and responds with an acknowledgment frame (Ack frame / BlockAck frame) to AP 1 after a SIFS interval, indicating that Relay 1 has received the data frame requested by AP 1 for forwarding. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded the data frame and does not need to confirm with AP 1.

[0156] 3) AP 1 sends a MU-RTS TXS TF to Relay 1 and / or STA 1. AP 1 shares part of the TXOP time it obtains (the specific time is indicated in the MU-RTS TXS TF) with Relay 1 and / or STA 1 for use. The TA of the MU-RTS TXS TF is set to the MAC address of AP 1, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates that the specific target recipient is Relay 1 and / or STA 1. Specific time: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (e.g., Relay 1 and / or STA 1).

[0157] 4) After a SIFS interval between AP 1 sending the MU-RTS TXS TF, Relay 1 and / or STA 1 simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of AP 1's shared TXOP. The RA in the CTS frame sent by Relay 1 and / or STA 1 is set to AP 1's MAC address. Note that STA 1 may be outside AP 1's signal coverage area. In this case, STA 1 cannot receive the MU-RTS TXS TF sent by AP 1. Therefore, STA 1 will not reply with a CTS frame; only Relay 1 will reply with a CTS frame.

[0158] 5) Relay 1 sends a relayed data frame after a SIFS interval after sending a CTS frame. The RA of this relayed data frame is set to STA 1's MAC address, the TA is set to Relay 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that the data frame originated from AP 1, was sent by Relay 1 to STA 1, and was destined for STA 1.

[0159] 6) STA 1 receives the relayed data frame sent by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA 1 has received the data frame forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's MAC address.

[0160] 7) Relay 1 receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA 1 successfully received the Data frame that AP 1 requested Relay 1 to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to AP 1's MAC address, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address.

[0161] 8) After completing the relay transmission within the TXOP shared by AP 1, if there is still time remaining, Relay 1 or STA 1 can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS duration, it will proactively reclaim the TXOP usage right and AP 1 will continue with other operations.

[0162] The effect achieved by this embodiment is as follows: In a scenario with only one AP, one relay node, and one STA, the AP can directly schedule transmission between the relay node and the STA after obtaining a TXOP. There is no need for the relay node and the STA to compete for channel usage rights separately. Transmission between the relay node and the STA is performed only after successfully obtaining the TXOP, which reduces the delay of relay transmission to a certain extent.

[0163] Scenario 2: Scheduling and transmission from one AP to one relay node to multiple STAs

[0164] In some embodiments of the present invention, the first node, the relay communication device and the at least one second node are respectively a first node (1 AP), a relay communication device (1 Relay node) and multiple second nodes (multiple STAs), and the one relay communication device provides relay services for the multiple second nodes.

[0165] Figure 4B is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 4B, there is only one AP (i.e., AP 1), one Relay node (i.e., Relay 1) and multiple STAs (i.e., STA 1 to STA c) in the BSS, and the Relay node provides relay services to multiple STAs (i.e., STA 1 to STA c).

[0166] Specifically, in some embodiments of the present invention, this example is described as follows: after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1, and then AP 1 shares part of the TXOP time obtained with Relay 1 and STA 1 to STA c for relay transmission (for example, Relay 1 transmits data to AP 1 to STA c). However, the present invention is not limited to this process. It is also possible that after obtaining a TXOP, AP 1 first shares part of the TXOP time with Relay 1 and STA 1 to STA c for relay transmission (for example, STA 1 to STA c transmit data to Relay 1), and then transmission is performed between Relay 1 and AP 1 (for example, Relay 1 transmits data to AP 1).

[0167] The steps in FIG. 4B are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0168] 1) After AP 1 obtains a TXOP, it sends a data frame (Data i). The RA field of Data i is set to Relay 1's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's (and / or STA c's) MAC address. This indicates that the data frame originates from AP 1, is sent by AP 1 to Relay 1, and is destined for STA 1 (and / or STA c).

[0169] 2) Relay 1 receives the data frame from AP 1 and responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay 1 received the data frame requested by AP 1 for forwarding. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can be omitted, meaning that Relay 1 has not yet successfully forwarded the data frame and does not need to confirm with AP 1.

[0170] 3) AP 1 sends a MU-RTS TXS TF to Relay 1 and / or STA 1 to STA c. AP 1 shares part of its acquired TXOP time (the specific time is indicated in the MU-RTS TXS TF) with Relay 1 and / or STA 1 to STA c. The TA of the MU-RTS TXS TF is set to AP 1's MAC address, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates that the specific target recipient is Relay 1 and / or STA 1 to STA c. Specific time: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (e.g., Relay 1 and / or STA 1 to STA c).

[0171] 4) After a SIFS interval between AP 1's MU-RTS TXS TF transmission, Relay 1 and / or STAs 1 to STA c simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of AP 1's shared TXOP. The RA field of the CTS frame sent by Relay 1 and / or STAs 1 to STA c is set to AP 1's MAC address. Note that STAs 1 to STA c may be outside AP 1's signal coverage area. In this case, they cannot receive the MU-RTS TXS TF sent by AP 1. Therefore, STAs 1 to STA c do not reply with a CTS frame; only Relay 1 does.

[0172] 5) Relay 1 sends the relayed Data i after a SIFS interval after sending a CTS frame. The RA of this relayed Data i is set to the MAC address of STA 1 (or STA c), the TA is set to the MAC address of Relay 1, the SA is set to the MAC address of AP 1, and the DA is set to the MAC address of STA 1 (or STA c). This indicates that this Data frame originated from AP 1, was sent by Relay 1 to STA 1 (or STA c), and then destined for STA 1 (or STA c).

[0173] 6) STA 1 (or STA c) receives Data i relayed by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA 1 (or STA c) has received Data i forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's (or STA c's) MAC address.

[0174] 7) Relay 1 receives the Ack / BlockAck frame from STA 1 (or STA c) and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA 1 (or STA c) successfully received Data i, which AP 1 requested Relay 1 to forward. If a relayed Ack frame is sent, the RA is set to AP 1's MAC address, and no TA exists. If a relayed BlockAck frame is sent, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address.

[0175] 8) STA c can also send a data frame (Data j) within the TXOP shared by AP 1. The RA of Data j is set to Relay 1's MAC address, the TA is set to STA c's MAC address, the SA is set to STA c's MAC address, and the DA is set to AP 1's MAC address. This indicates that the data frame originates from STA c, is sent by STA c to Relay 1, and is destined for AP 1.

[0176] 9) Relay 1 receives Data j from STA c and sends the relayed Data j after a SIFS period. The RA of this relayed Data j is set to AP 1's MAC address, the TA is set to Relay 1's MAC address, the SA is set to STA c's MAC address, and the DA is set to AP 1's MAC address. This indicates that Data j originated from STA c, was sent by Relay 1, received by AP 1, and then destined for AP 1.

[0177] 10) AP 1 receives Data j from Relay 1 and responds with an Ack / BlockAck frame after a SIFS interval, indicating that AP 1 has received Data j. If it is an Ack frame, the RA is set to Relay 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to AP 1's MAC address.

[0178] 11) Relay 1 receives the Ack / BlockAck frame from AP 1 and relays it to STA c after a SIFS, informing STA c that destination node AP 1 successfully received Data j forwarded by Relay 1. If it is an Ack frame, the RA is set to STA c's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to STA c's MAC address, and the TA is set to Relay 1's MAC address.

[0179] 12) After completing the relay transmission within the TXOP shared by AP 1, if there is still time remaining, Relay 1 or STA 1-STA c can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS duration, it proactively reclaims the TXOP usage right and AP 1 continues with other operations.

[0180] The effects that can be achieved by this embodiment are as follows: In a scenario with only one AP, one Relay node, and multiple STAs, on the one hand, this embodiment supports the effect of one Relay node providing relay services for multiple STAs. On the other hand, after the AP obtains a TXOP, it can directly schedule transmissions between the Relay node and multiple STAs. There is no need for the Relay node and multiple STAs to compete for channel usage rights separately. After successfully obtaining a TXOP, the Relay node or STA can then transmit between the Relay node and the STA, thereby reducing the delay of relay transmission to a certain extent.

[0181] Because STA c may not be within the signal coverage of AP 1, when AP 1 sends the MU-RTS TXS TF shared TXOP (to Relay 1, STA 1, and / or STA c), STA c cannot know when to send Data j, which needs to be relayed to AP 1 via Relay 1, to Relay 1. To solve this problem, there are two methods:

[0182] 1. Explicit method:

[0183] After Relay 1 finishes using the TXOP shared by AP 1, it proactively sends a MU-RTS TXS TF to STA c, sharing the remaining time with STA c again. Then, after Relay 1 responds to the CTS frame, it immediately sends Data j to Relay 1. Relay 1 can then perform subsequent operations, such as relaying Data j to AP 1. Alternatively, Relay 1 sends any other frame to STA c that indicates that STA c can use the current TXOP for transmission. After receiving the indication signaling, STA c can immediately send Data j to Relay 1 after sending the response frame. STA c can also immediately send Data j to Relay 1 without sending a response frame. Relay 1 can then perform subsequent operations, such as relaying Data j to AP 1.

[0184] 2. Implicit method:

[0185] After Relay 1 finishes using the TXOP shared by AP 1, it can suspend channel use. STA c, after detecting through CCA that the channel has been idle for xIFS, can proactively send Data j to Relay 1. Relay 1 can then perform subsequent operations, such as relaying Data j to AP 1. Note that the length of xIFS is greater than SIFS but less than or equal to PIFS.

[0186] Scenario 3: Scheduling and transmission from one AP to multiple relay nodes to one STA

[0187] In some embodiments of the present invention, the first node, the relay communication device and the at least one second node are respectively a first node (1 AP), multiple relay communication devices (multiple Relay nodes) and a second node (1 STA), and the multiple relay communication devices provide relay services for the one second node.

[0188] Figure 4C is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 4C, there is only one AP (i.e., AP 1) in the BSS, multiple Relay nodes (i.e., Relay 1 to Relay b), and multiple Relay nodes can all provide relay services for the same STA (i.e., STA 1).

[0189] This example illustrates a situation where, after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1 through Relay b. AP 1 then shares part of the TXOP time with Relay 1 through Relay b and STA 1 for relay transmission (e.g., Relay 1 through Relay b each transmit data to STA 1). However, the present invention is not limited to this process. Alternatively, after AP 1 obtains a TXOP, AP 1 first shares part of the TXOP time with Relay 1 through Relay b and STA 1 for relay transmission (e.g., STA 1 transmits data to Relay 1 through Relay b). Then, data is transmitted between Relay 1 through Relay b and AP 1 (e.g., Relay 1 through Relay b transmit data to AP 1).

[0190] The steps in FIG. 4C are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0191] Option 1 (including only steps 1) and 2) below): The AP sends data to multiple relay nodes simultaneously, and the multiple relay nodes respond synchronously for confirmation.

[0192] 1) After AP 1 obtains a TXOP, it sends a data frame (Data a). The RA of Data a is set to the multicast address corresponding to the MAC addresses of Relays 1 through Relay b, the TA is set to AP 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that Data a originates from AP 1, is sent by AP 1 to Relays 1 through Relay b, and is destined for STA 1.

[0193] 2) Relay 1 through Relay b receive Data a from AP 1 and, after a SIFS, simultaneously reply with an Ack / BlockAck frame to AP 1, indicating that Relay 1 through Relay b received Data a, which AP 1 requested them to forward. If it's an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it's a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to the MAC addresses of Relay 1 through Relay b, respectively. Note that this step doesn't need to be omitted; that is, Relay 1 hasn't yet successfully forwarded the Data frame and doesn't need to acknowledge AP 1.

[0194] Option 2 (including only steps 1) and 2) below): The AP sends data to multiple relay nodes in a time-division manner, and the multiple relay nodes confirm the data separately.

[0195] 1) After AP 1 obtains a TXOP, it sends a Data frame (Data i). The RA of Data i is set to Relay 1's MAC address, the TA is set to AP 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that Data i originated from AP 1, was sent by AP 1 to Relay 1, and its destination is STA 1. After receiving Data i from AP 1, Relay 1 responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay 1 has received Data i, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address.

[0196] 2) AP 1 then sends Data j, where the RA of Data j is set to Relay b's MAC address, the TA is set to AP 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that Data j originated from AP 1, was sent by AP 1 to Relay b, and was destined for STA 1. Relay b receives Data j from AP 1 and, after a SIFS, responds with an Ack / BlockAck frame to AP 1, indicating that Relay b received Data j, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay b's MAC address.

[0197] 3) AP 1 sends a MU-RTS TXS TF to Relay 1 through Relay b and / or STA 1. AP 1 shares part of its acquired TXOP time (the specific time is indicated in the MU-RTS TXS TF) with Relay 1 through Relay b and / or STA 1. The TA of the MU-RTS TXS TF is set to AP 1's MAC address, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates the specific target recipients as Relay 1 through Relay b and / or STA 1. Specific time: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (e.g., Relay 1 through Relay b and / or STA 1).

[0198] 4) After a SIFS interval between AP 1 sending the MU-RTS TXS TF, Relays 1 through Relay b and / or STA 1 simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of AP 1's shared TXOP. The RA field in the CTS frame sent by Relays 1 through Relay b and / or STA 1 is set to AP 1's MAC address. Note that STA 1 may be outside AP 1's signal coverage area. In this case, STA 1 cannot receive the MU-RTS TXS TF sent by AP 1 and will not reply with a CTS frame. Only the relays among Relays 1 through Relay b that receive the MU-RTS TXS TF will reply with a CTS frame.

[0199] 5) Relay 1 then sends the relayed Data i after a SIFS interval after sending a CTS frame. The RA of the relayed Data i is set to STA 1's MAC address, the TA is set to Relay 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that Data i originates from AP 1, is sent by Relay 1 to STA 1, and is destined for STA 1.

[0200] 6) STA 1 receives Data i from Relay 1 and responds with an Ack / BlockAck frame after a SIFS interval, indicating that STA 1 has received Data i. If it is an Ack frame, the RA is set to Relay 1's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's MAC address.

[0201] 7) Relay 1 receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA 1 has successfully received Data i, which AP 1 requested Relay 1 to forward. If a relayed Ack frame is sent, the RA is set to AP 1's MAC address, and no TA exists. If a relayed BlockAck frame is sent, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address.

[0202] 8) Relay b also sends Data j, where the RA of Data j is set to STA 1's MAC address, the TA is set to Relay b's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This means that Data j originates from AP 1, is sent by Relay b to STA 1, and is destined for STA 1.

[0203] 9) STA 1 receives Data j from Relay b and responds with an Ack / BlockAck frame SIFS later, indicating that STA 1 has received Data j. If it is an Ack frame, the RA is set to Relay b's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay b's MAC address, and the TA is set to STA 1's MAC address.

[0204] 10) Relay b receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA 1 successfully received Data j, which AP 1 requested Relay b to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to AP 1's MAC address, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay b's MAC address.

[0205] 11) After completing relay transmission within the TXOP shared by AP 1, if there is still time remaining, Relay 1 to Relay b or STA 1 can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS duration, it will proactively reclaim the TXOP usage right and AP 1 will continue with other operations.

[0206] Note: In this example, Data i and Data j can be regarded as part of Data a respectively.

[0207] The effects that can be achieved by this embodiment are as follows: In a scenario with only one AP, multiple Relay nodes, and one STA, on the one hand, this embodiment supports the effect of multiple Relay nodes providing relay services for one STA. On the other hand, after the AP obtains a TXOP, it can directly schedule transmissions between multiple Relay nodes and the STA. There is no need for multiple Relay nodes and the STA to compete for channel usage rights separately. After successfully obtaining a TXOP, the Relay node or STA can then transmit between the Relay node and the STA, thereby reducing the delay of relay transmission to a certain extent.

[0208] Scenario 4: Scheduling and transmission from one AP to multiple relay nodes to multiple STAs

[0209] In some embodiments of the present invention, the first node, the relay communication device and the at least one second node are respectively a first node (1 AP), multiple relay communication devices (multiple Relay nodes) and multiple second nodes (multiple STAs), and at least one of the multiple relay communication devices provides relay service for at least one of the multiple second nodes.

[0210] Figure 4D is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 4D, there is only one AP (i.e., AP 1), multiple Relay nodes (i.e., Relay 1 to Relay b) and multiple STAs (i.e., STA 1 to STA c) in the BSS, and multiple Relay nodes can provide relay services for multiple STAs.

[0211] This example illustrates that after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1 to Relay b. AP 1 then shares part of the TXOP time with Relay 1 to Relay b and STA 1 to STA c for relay transmission (for example, Relay 1 first transmits data to STA 1 to STA c, and then Relay b transmits data to STA 1 to STA c). However, the present invention is not limited to this process. Alternatively, after obtaining a TXOP, AP 1 first shares part of the TXOP time with Relay 1 to Relay b and STA 1 to STA c for relay transmission (for example, STA 1 to STA c first transmits data to Relay 1, and then STA 1 to STA c transmits data to Relay b). Then, data is transmitted between Relay 1 to Relay b and AP 1 (for example, Relay 1 to Relay b transmits data to AP 1).

[0212] The steps in FIG. 4D are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0213] Option 1 (including only steps 1) and 2) below): The AP sends data to multiple relay nodes simultaneously, and the multiple relay nodes respond synchronously for confirmation (completely consistent with the corresponding content of Option 1 in Figure 4C).

[0214] 1) After AP 1 obtains a TXOP, it sends a data frame (Data a). The RA of Data a is set to the multicast address corresponding to the MAC addresses of Relays 1 through Relay b, the TA is set to AP 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that Data a originates from AP 1, is sent by AP 1 to Relays 1 through Relay b, and is destined for STA 1.

[0215] 2) Relay 1 through Relay b receive Data a from AP 1 and, after a SIFS period, simultaneously reply with an Ack / BlockAck frame to AP 1, indicating that Relay 1 through Relay b received Data a, which AP 1 requested them to forward. If it's an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it's a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to the MAC addresses of Relay 1 through Relay b, respectively. Note that this step doesn't need to be omitted; that is, Relay 1 hasn't yet successfully forwarded the Data frame and doesn't need to confirm with AP 1.

[0216] Option 2 (including only steps 1) and 2) below): The AP sends data to multiple relays in a time-division manner, and the multiple relays confirm the data respectively (completely consistent with the corresponding content of Option 2 in Figure 4C).

[0217] 1) After AP 1 obtains a TXOP, it sends a Data frame (Data i). The RA of Data i is set to Relay 1's MAC address, the TA is set to AP 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that Data i originated from AP 1, was sent by AP 1 to Relay 1, and its destination is STA 1. After receiving Data i from AP 1, Relay 1 responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay 1 has received Data i, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address.

[0218] 2) AP 1 then sends Data j, where the RA of Data j is set to Relay b's MAC address, the TA is set to AP 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA 1's MAC address. This indicates that Data j originated from AP 1, was sent by AP 1 to Relay b, and was destined for STA 1. Relay b receives Data j from AP 1 and, after a SIFS, responds with an Ack / BlockAck frame to AP 1, indicating that Relay b received Data j, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay b's MAC address.

[0219] 3) AP 1 sends a MU-RTS TXS TF to Relay 1 through Relay b and / or STA 1 through STA c. AP 1 shares part of its acquired TXOP time (the specific time is indicated in the MU-RTS TXS TF) with Relay 1 through Relay b and / or STA 1 through STA c. The TA of the MU-RTS TXS TF is set to AP 1's MAC address, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates the specific target recipients: Relay 1 through Relay b and / or STA 1 through STA c. Specific time: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (e.g., Relay 1 through Relay b and / or STA 1 through STA c).

[0220] 4) After a SIFS interval between AP 1 sending the MU-RTS TXS TF, Relays 1 through Relay b and / or STAs 1 through STA c simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of the TXOP shared by AP 1. The RA in the CTS frames sent by Relays 1 through Relay b and / or STAs 1 through STA c is set to AP 1's MAC address. Note that some or all of STAs 1 through STA c may not be within AP 1's signal coverage. In this case, some or all of STAs 1 through STA c cannot receive the MU-RTS TXS TF sent by AP 1. Consequently, some or all of STAs 1 through STA c will not reply with a CTS frame. Only those nodes among Relays 1 through Relay b and / or STAs 1 through STA c that receive the MU-RTS TXS TF will reply with a CTS frame.

[0221] 5) Data transmission then begins between Relay 1 and STAs 1 to c. Relay 1 sends Data i1 after a SIFS interval after sending a CTS frame. The RA field of Data i1 is set to STA 1's MAC address, the TA field is set to Relay 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that Data i1 originates from AP 1, is sent by Relay 1 to STA 1, and is destined for STA 1.

[0222] 6) STA 1 receives Data i1 from Relay 1 and responds with an Ack / BlockAck frame after a SIFS interval, indicating that STA 1 has received Data i1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's MAC address.

[0223] 7) Relay 1 receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA 1 successfully received Data i1, which AP 1 requested Relay 1 to forward. If a relayed Ack frame is sent, the RA is set to AP 1's MAC address, and no TA exists. If a relayed BlockAck frame is sent, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address.

[0224] 8) Relay 1 sends relayed Data i2, where the RA of Data i2 is set to STA c's MAC address, the TA is set to Relay 1's MAC address, the SA is set to AP 1's MAC address, and the DA is set to STA c's MAC address. This indicates that Data i2 originated from AP 1, was sent by Relay 1 to STA c, and then destined for STA c.

[0225] 9) STA c receives Data i2 from Relay 1 and responds with an Ack / BlockAck frame after a SIFS interval, indicating that STA c has received Data i2. If it is an Ack frame, the RA is set to Relay 1's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA c's MAC address.

[0226] 10) Relay 1 receives the Ack / BlockAck frame from STA c and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA c successfully received Data i2, which AP 1 requested Relay 1 to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to AP 1's MAC address, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay c's MAC address.

[0227] 11) Data transmission occurs between Relay b and STAs 1 to c. Relay b sends relayed Data j1, where the RA field is set to STA 1's MAC address, the TA field is set to Relay b's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that Data j1 originates from AP 1, is sent by Relay b to STA 1, and is destined for STA 1.

[0228] 12) STA 1 receives Data j1 from Relay b and responds with an Ack / BlockAck frame after a SIFS interval, indicating that STA 1 has received Data j1. If it is an Ack frame, the RA is set to Relay b's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay b's MAC address, and the TA is set to STA 1's MAC address.

[0229] 13) Relay b receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA 1 successfully received Data j1, which AP 1 requested Relay b to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to AP 1's MAC address, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay b's MAC address.

[0230] 14) Relay b sends relayed Data j2, where the RA of Data j2 is set to the MAC address of STA c, the TA is set to the MAC address of Relay b, the SA is set to the MAC address of AP 1, and the DA is set to the MAC address of STA c. This indicates that Data j2 originates from AP 1, is sent by Relay b to STA c, and is destined for STA c.

[0231] 15) STA c receives Data j2 from Relay b and responds with an Ack / BlockAck frame SIFS later, indicating that STA c received Data j2. If it is an Ack frame, the RA is set to Relay b's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay b's MAC address, and the TA is set to STA c's MAC address.

[0232] 16) Relay b receives the Ack / BlockAck frame from STA c and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1, indicating that STA c successfully received Data j2, which AP 1 requested Relay b to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to AP 1's MAC address, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay b's MAC address.

[0233] 17) After completing relay transmission within the TXOP shared by AP 1, if there is still time remaining, Relay 1 to Relay b or STA 1 to STA c can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS duration, it proactively reclaims the TXOP usage right and AP 1 continues with other operations.

[0234] Note: In this example, Data i and Data j can be considered as part of Data a respectively. In addition, Data i1 and Data i2 can be considered as

[0235] Don't regard it as part of Data i. Data j1 and Data j2 can be regarded as part of Data j respectively.

[0236] The effects that can be achieved by this embodiment are as follows: In a scenario with only one AP, multiple Relay nodes, and multiple STAs, on the one hand, this embodiment supports one or more Relay nodes providing relay services for one or more STAs (including one Relay providing relay services for one STA; one Relay node providing relay services for multiple STAs; multiple Relay nodes providing relay services for one STA; and multiple Relay nodes providing relay services for multiple STAs). On the other hand, after obtaining a TXOP, the AP can directly schedule transmissions between multiple Relay nodes and multiple STAs. There is no need for multiple Relay nodes and multiple STAs to compete for channel usage rights respectively. After successfully obtaining a TXOP, the Relay node or STA can then transmit between the Relay node and the STA, thereby reducing the delay of relay transmission to a certain extent.

[0237] Scenario 5: Scheduling and transmission of multiple APs <-> 1 relay node <-> 1 STA

[0238] In some embodiments of the present invention, the first node, the relay communication device and the at least one second node are respectively multiple first nodes (multiple APs), a relay communication device (1 Relay node) and a second node (1 STA), and the multiple first nodes provide relay services for the one second node through the one relay communication device. The MU-RTS-TXS TF also instructs the one first node to schedule the transmission between the relay communication device and another one or more first nodes after obtaining the transmission opportunity TXOP and share part of the obtained TXOP time with the other one or more first nodes for use.

[0239] Figure 4E is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 5.3-6, there are multiple APs (i.e., AP 1 to AP a) and one Relay (i.e., Relay 1) in the network, and the Relay only provides relay service to one STA (i.e., STA 1).

[0240] This example illustrates a situation where, after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1. AP 1 then shares part of the TXOP time it obtains with other APs (e.g., AP a in the figure), Relay 1, and STA 1 for relay transmission (e.g., AP a transmits data to Relay 1, and Relay 1 transmits data to AP 1). However, the present invention is not limited to this process. Alternatively, after obtaining a TXOP, AP 1 first shares part of the TXOP time with Relay 1 and STA 1 for relay transmission (e.g., STA 1 transmits data to Relay 1). Then, data is transmitted between Relay 1 and AP 1 and / or AP a (e.g., Relay 1 transmits data to AP 1 and / or AP a).

[0241] The steps in FIG. 4E are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0242] 1) After AP 1 obtains a TXOP, it sends a data frame (e.g., Data i). The RA field of Data i is set to Relay 1's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that the data frame originates from AP 1, is sent by AP 1 to Relay 1, and is destined for STA 1.

[0243] 2) Relay 1 receives Data i from AP 1 and responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay 1 has received Data i, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data i and does not need to confirm with AP 1.

[0244] 3) AP 1 sends a MU-RTS TXS TF to AP a and Relay 1 (and STA 1). AP 1 shares part of its acquired TXOP time (the specific time is indicated in the MU-RTS TXS TF) with AP a and Relay 1 (and STA 1). The TA of the MU-RTS TXS TF is set to AP 1's MAC address, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates that the specific target recipients are AP a and Relay 1 (and STA 1). Specific time: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (e.g., AP a and / or Relay 1 and / or STA 1).

[0245] 4) After a SIFS interval between AP 1's MU-RTS TXS TF transmission, AP a and Relay 1 (and STA 1) simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of AP 1's shared TXOP. The RA field of the CTS frame sent by AP a and Relay 1 (and STA 1) is set to AP 1's MAC address. Note that STA 1 may be outside AP 1's signal coverage area. In this case, STA 1 cannot receive the MU-RTS TXS TF sent by AP 1. Therefore, STA 1 does not reply with a CTS frame; only AP a and Relay 1 reply with a CTS frame.

[0246] 5) AP a sends Data j, which needs to be relayed by Relay 1. The RA of Data j is set to Relay 1's MAC address, the TA is set to AP a's MAC address, the SA is set to AP a's MAC address, and the DA is set to STA 1's MAC address. This means that Data j originates from AP a, is sent by Relay 1, is received by STA 1, and is destined for STA 1.

[0247] 6) Relay 1 receives Data j from AP a and responds with an Ack / BlockAck frame to AP a after a SIFS interval, indicating that Relay 1 received Data j, which AP a requested it to forward. If it is an Ack frame, the RA is set to AP a's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP a's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data j and does not need to confirm with AP a.

[0248] 7) Relay 1 sends the relayed Data frame (which can be part or all of Data i requested to be relayed by AP 1, part or all of Data j requested to be relayed by AP a, or part or all of Data i + Data j requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA 1, the TA is set to the MAC address of Relay 1, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA 1. This means that the data frame originates from AP 1 and / or AP a, is sent by Relay 1 to STA 1, and is destined for STA 1.

[0249] 8) STA 1 receives the relayed data frame sent by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA 1 has received the data frame forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's MAC address.

[0250] 9) Relay 1 receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1 and / or AP a. This indicates that STA 1 has successfully received the data frame that AP 1 and / or AP a requested Relay 1 to forward. If the relayed Ack frame is received, the RA is set to the MAC address of AP 1 and / or AP a, and no TA exists.

[0251] If relaying a BlockAck frame, RA is set to the MAC address of AP 1 and / or AP a, and TA is set to the MAC address of Relay 1.

[0252] 10) After completing the relay transmission within the TXOP shared by AP 1, if there is still time remaining, AP a and / or Relay 1 and / or STA 1 can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS time, it proactively reclaims the TXOP usage right and AP 1 continues with other operations.

[0253] MAC address: If Relay 1 relays part or all of Data i and Data j requested by both AP 1 and AP a, SA can be handled using the following two methods:

[0254] i. SA is set to the multicast address corresponding to AP 1 and AP a; (the multicast address prior information must be negotiated with Relay 1 and STA 1 in advance).

[0255] ii. Carry the MAC addresses of AP 1 and AP a in the Data frame (including SA).

[0256] The effects that can be achieved by this embodiment are as follows: In a scenario with multiple APs, one Relay node, and one STA, on the one hand, this embodiment supports the effect of multiple APs providing relay services for one STA through the same Relay node. On the other hand, after one AP obtains a TXOP, it can directly schedule transmissions between one or more other APs and the Relay node. There is no need for other APs, Relay nodes, and STAs to compete for channel usage rights. After successfully obtaining a TXOP, the AP, Relay node, or STA can then transmit between the AP and the Relay node and / or the Relay node and the STA, thereby reducing the delay of relay transmission to a certain extent.

[0257] Scenario 6: Scheduling and transmission between multiple APs and one relay node and multiple STAs

[0258] In some embodiments of the present invention, the first node, the relay communication device and the at least one second node are respectively multiple first nodes (multiple APs), one relay communication device (1 Relay) and multiple second nodes (multiple STAs), and the multiple first nodes provide relay services for at least one of the multiple second nodes through the one relay communication device. The MU-RTS-TXS TF also instructs the one first node to schedule the transmission between the relay communication device and another one or more first nodes after obtaining the transmission opportunity TXOP and share part of the obtained TXOP time with the other one or more first nodes for use.

[0259] Figure 4F is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 4F, there are multiple APs (i.e., AP 1 to AP a), one Relay node (i.e., Relay 1) and multiple STAs (i.e., STA 1 to STA c) in the network, and the Relay node provides relay services to multiple STAs (i.e., STA 1 to STA c).

[0260] This example illustrates a situation where, after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1. AP 1 then shares part of the TXOP time with other APs (e.g., AP a in the figure), Relay 1, and STAs 1 to STA c for relay transmission (e.g., AP a transmits data to Relay 1, and Relay 1 transmits data to AP 1 to STA c). However, the present invention is not limited to this process. Alternatively, after obtaining a TXOP, AP 1 first shares part of the TXOP time with Relay 1 and STAs 1 to STA c for relay transmission (e.g., STA 1 to STA c transmit data to Relay 1). Then, data is transmitted between Relay 1 and AP 1 and / or AP a (e.g., Relay 1 transmits data to AP 1 and / or AP a).

[0261] The steps in FIG. 4F are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0262] 1) After AP 1 obtains a TXOP, it sends a data frame (e.g., Data i). The RA field of Data i is set to Relay 1's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that the data frame originates from AP 1, is sent by AP 1 to Relay 1, and is destined for STA 1.

[0263] 2) Relay 1 receives Data i from AP 1 and responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay 1 has received Data i, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data i and does not need to confirm with AP 1.

[0264] 3) AP 1 sends a MU-RTS TXS TF to AP a and Relay 1 (and STAs 1 to STA c). AP 1 shares a portion of its acquired TXOP time (the specific time is indicated in the MU-RTS TXS TF) with AP a and Relay 1 (and STAs 1 to STA c). The TA of the MU-RTS TXS TF is set to AP 1's MAC address, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates the specific target recipients: AP a and Relay 1 (and STAs 1 to STA c). Specific time: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (e.g., AP a and / or Relay 1 and / or STAs 1 to STA c).

[0265] 4) After a SIFS interval between AP 1 sending the MU-RTS TXS TF, AP a and Relay 1 (and STAs 1 to STA c) simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of the shared TXOP. The RA fields of the CTS frames sent by AP a and Relay 1 (and STAs 1 to STA c) are both set to AP 1's MAC address. Note that some or all of STAs 1 to STA c may be outside AP 1's signal coverage. In this case, STAs among STAs 1 to STA c that cannot receive the MU-RTS TXS TF sent by AP 1 will not reply with a CTS frame. Only STAs that receive the MU-RTS TXS TF sent by AP 1, along with AP a and Relay 1, reply with a CTS frame.

[0266] 5) AP a sends Data j, which needs to be relayed by Relay 1. The RA of Data j is set to Relay 1's MAC address, the TA is set to AP a's MAC address, the SA is set to AP a's MAC address, and the DA is set to STA 1's MAC address. This means that Data j originates from AP a, is sent by Relay 1, is received by STA 1, and is destined for STA 1.

[0267] 6) Relay 1 receives Data j from AP a and responds with an Ack / BlockAck frame to AP a after a SIFS interval, indicating that Relay 1 received Data j, which AP a requested it to forward. If it is an Ack frame, the RA is set to AP a's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP a's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data j and does not need to confirm with AP a.

[0268] 7) Relay 1 sends the relayed Data frame (which can be part or all of Data i requested to be relayed by AP 1, part or all of Data j requested to be relayed by AP a, or part or all of Data i + Data j requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA 1, the TA is set to the MAC address of Relay 1, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA 1. This means that the data frame originates from AP 1 and / or AP a, is sent by Relay 1 to STA 1, and is destined for STA 1.

[0269] 8) STA 1 receives the relayed data frame sent by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA 1 has received the data frame forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's MAC address.

[0270] 9) Relay 1 receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1 and / or AP a. This indicates that STA 1 has successfully received the data frame that AP 1 and / or AP a requested Relay 1 to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to the MAC address of AP 1 and / or AP a, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to the MAC address of AP 1 and / or AP a, and the TA is set to the MAC address of Relay 1.

[0271] 10) Relay 1 sends a relayed Data frame (which may be part or all of Data i requested to be relayed by AP 1, part or all of Data j requested to be relayed by AP a, or part or all of Data i + Data j requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA c, the TA is set to the MAC address of Relay 1, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA c. This means that the data frame originated from AP 1 and / or AP a, was sent by Relay 1 to STA c, and then the destination node is STA c.

[0272] 11) STA c receives the relayed data frame sent by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA c has received the data frame forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA c's MAC address.

[0273] 12) Relay 1 receives the Ack / BlockAck frame sent by STA c and sends a relay Ack / BlockAck frame to AP 1 and / or AP a after SIFS time, indicating that STA c has successfully received the Data frame requested by AP 1 and / or AP a to be forwarded by Relay 1. If the relay Ack frame is received, the RA is set to the MAC address of AP 1 and / or AP a. 2, there is no TA. If the relay BlockAck frame, RA is set to the MAC address of AP 1 and / or AP a. 2 , TA is set to the MAC address of Relay 1.

[0274] 13) After completing the relay transmission within the TXOP shared by AP 1, if there is still time remaining, AP a and / or Relay 1 and / or STA 1 to STA c can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS duration, it proactively reclaims the TXOP usage right and AP 1 continues with other operations.

[0275] MAC address: If Relay 1 relays part or all of Data i and Data j requested by both AP 1 and AP a, SA can be handled using the following two methods:

[0276] i. SA is set to the multicast address corresponding to AP 1 and AP a; (the multicast address prior information must be negotiated with Relay 1 and STA 1 in advance).

[0277] ii. Carry the MAC addresses of AP 1 and AP a in the Data frame (including SA).

[0278] The effects that can be achieved by this embodiment are as follows: In a scenario with multiple APs, one Relay, and multiple STAs, on the one hand, this embodiment supports the effect of multiple APs providing relay services for one or more STAs through the same Relay. On the other hand, after one AP obtains a TXOP, it can directly schedule transmissions between one or more other APs and the Relay. This eliminates the need for other APs, Relays, and multiple STAs to compete for channel usage rights. After successfully obtaining a TXOP, the AP, Relay, or STA can then perform transmissions between the AP and the Relay and / or the Relay and the STA, thereby reducing the delay of relay transmissions to a certain extent.

[0279] Scenario 7: Scheduling and transmission of multiple APs <-> multiple relay nodes <-> one STA

[0280] In some embodiments of the present invention, the first node, the relay communication device and the at least one second node are respectively multiple first nodes (multiple APs), multiple relay communication devices (multiple Relay nodes) and one second node (1 STA), and the multiple first nodes provide relay services for the one second node through the multiple relay communication devices. The MU-RTS-TXS TF also instructs the one first node to schedule the transmission between the relay communication device and another one or more first nodes after obtaining the transmission opportunity TXOP and share part of the obtained TXOP time with the another one or more first nodes for use.

[0281] Figure 4G is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 4G, there are multiple APs (i.e., AP 1 to AP a) and multiple Relay nodes (i.e., Relay 1 to Relay b) in the network, and these Relay nodes all provide relay services to the same STA (i.e., STA 1).

[0282] This example illustrates a situation where, after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1-Relay b. AP 1 then shares part of the TXOP time with other APs (e.g., AP a in the figure) and Relay 1-Relay b (and STA 1) for relay transmission (e.g., AP a transmits data to Relay 1, and Relay 1-Relay b transmit data to STA 1). However, the present invention is not limited to this process. Alternatively, after obtaining a TXOP, AP 1 first shares part of the TXOP time with Relay 1-Relay b (and STA 1) for relay transmission (e.g., STA 1 transmits data to Relay 1-Relay b). Then, data is transmitted between Relay 1-Relay b and AP 1 and / or AP a (e.g., Relay 1-Relay b transmits data to AP 1 and / or AP a).

[0283] The steps in FIG. 4G are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0284] 1) After AP 1 obtains a TXOP, it sends a data frame (e.g., Data i). The RA field of Data i is set to Relay 1's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that the data frame originates from AP 1, is sent by AP 1 to Relay 1, and is destined for STA 1.

[0285] 2) Relay 1 receives Data i from AP 1 and responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay 1 has received Data i, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data i and does not need to confirm with AP 1.

[0286] 3) AP 1 sends Data j within the acquired TXOP. The RA field of Data j is set to Relay b's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that the Data frame originated from AP 1, was sent by AP 1 to Relay b, and was destined for STA 1.

[0287] 4) Relay b receives Data j from AP 1 and responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay b received Data j, which AP 1 requested it to forward. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay b's MAC address. Note that this step can also be omitted, meaning that Relay b has not yet successfully forwarded Data j and does not need to confirm with AP 1.

[0288] 5) AP 1 sends a MU-RTS TXS TF to AP a and Relays 1 through b (and STA 1). AP 1 shares a portion of its TXOP time (the specific time is indicated in the MU-RTS TXS TF) with AP a and Relays 1 through b (and STA 1). The TA of the MU-RTS TXS TF is set to AP 1's MAC address, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates the specific target recipients: AP a and Relays 1 through b (and STA 1). Specific duration: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (e.g., AP a and / or Relays 1 through b and / or STA 1).

[0289] 6) After a SIFS interval between AP 1 sending the MU-RTS TXS TF, AP a and Relays 1-2 (and STA 1) simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of the shared TXOP. The RA field in the CTS frames sent by AP a and Relays 1-2 (and STA 1) is set to AP 1's MAC address. Note that STA 1 may be outside AP 1's signal coverage. In this case, STA 1 cannot receive the MU-RTS TXS TF sent by AP 1 and will not reply with a CTS frame. Only AP a and the relays among Relays 1-2 that receive the MU-RTS TXS TF sent by AP 1 will reply with a CTS frame.

[0290] 7) AP a sends Data m, which needs to be relayed by Relay 1. The RA of Data m is set to Relay 1's MAC address, the TA is set to AP a's MAC address, the SA is set to AP a's MAC address, and the DA is set to STA 1's MAC address. This means that Data m originates from AP a, is sent by Relay 1, is received by STA 1, and is destined for STA 1.

[0291] 8) Relay 1 receives Data m from AP a and responds with an Ack / BlockAck frame to AP a after a SIFS interval, indicating that Relay 1 received Data m, which AP a requested it to forward. If it is an Ack frame, the RA is set to AP a's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP a's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data m and does not need to confirm with AP a.

[0292] 9) AP a sends Data n, which needs to be relayed by Relay b. The RA of Data n is set to Relay b's MAC address, the TA is set to AP a's MAC address, the SA is set to AP a's MAC address, and the DA is set to STA 1's MAC address. This means that Data n originates from AP a, is sent by Relay b to STA 1, and is destined for STA 1.

[0293] 10) Relay b receives Data n from AP a and responds with an Ack / BlockAck frame to AP a after a SIFS interval, indicating that Relay b received Data n, which AP a requested it to forward. If it is an Ack frame, the RA is set to AP a's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP a's MAC address, and the TA is set to Relay b's MAC address. Note that this step can also be omitted, meaning that Relay b has not yet successfully forwarded Data n and does not need to confirm with AP a.

[0294] 11) Relay 1 sends a relayed Data frame (which may be part or all of Data i requested to be relayed by AP 1, part or all of Data m requested to be relayed by AP a, or part or all of Data i + Data m requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA 1, the TA is set to the MAC address of Relay 1, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA 1. This means that the data frame originates from AP 1 and / or AP a, is sent by Relay 1 to STA 1, and is destined for STA 1.

[0295] 12) STA 1 receives the relayed data frame sent by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA 1 has received the data frame forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's MAC address.

[0296] 13) Relay 1 receives the Ack / BlockAck frame from STA 1 and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1 and / or AP a. This indicates that STA 1 has successfully received the Data frame that AP 1 and / or AP a requested Relay 1 to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to the MAC address of AP 1 and / or AP a, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to the MAC address of AP 1 and / or AP a, and the TA is set to the MAC address of Relay 1.

[0297] 14) Relay b sends a relayed Data frame (which may be part or all of Data j requested to be relayed by AP 1, part or all of Data n requested to be relayed by AP a, or part or all of Data j + Data n requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA 1, the TA is set to the MAC address of Relay b, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA 1. This means that the data frame originated from AP 1 and / or AP a, was sent by Relay b to STA 1, and then the destination node is STA 1.

[0298] 15) STA 1 receives the relayed data frame sent by Relay b and responds with an Ack / BlockAck frame to Relay b after a SIFS interval, indicating that STA 1 has received the data frame forwarded by Relay b. If it is an Ack frame, the RA is set to Relay b's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay b's MAC address, and the TA is set to STA 1's MAC address.

[0299] 16) Relay b receives the Ack / BlockAck frame sent by STA 1 and sends a relayed Ack / BlockAck frame to AP 1 and / or AP a after SIFS time, indicating that STA 1 has successfully received the Data frame that AP 1 and / or AP a requested Relay b to forward. If the relayed Ack frame is set, RA is set to the MAC address of AP 1 and / or AP a. 2 , there is no TA; if the relay BlockAck frame, RA is set to the MAC address of AP 1 and / or AP a 2 , TA is set to the MAC address of Relay b.

[0300] 17) After completing the relay transmission within the TXOP shared by AP 1, if there is still time remaining, AP a and / or Relay 1 to Relay b and / or STA 1 can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS time, it will proactively reclaim the TXOP usage right and AP 1 will continue with other operations.

[0301] MAC address: If Relay 1 relays part or all of Data i and Data m requested by both AP 1 and AP a, or if Relay b relays part or all of Data j and Data n requested by both AP 1 and AP a, SA can be handled using the following methods:

[0302] i. SA is set to the multicast address corresponding to AP 1 and AP a. (The multicast address information must be negotiated with Relay 1 through Relay b and STA 1 in advance.)

[0303] ii. Carry the MAC addresses of AP 1 and AP a in the Data frame (including SA).

[0304] The effects that can be achieved by this embodiment are as follows: In a scenario with multiple APs, multiple Relay nodes, and one STA, on the one hand, this embodiment supports the effect of multiple APs providing relay services for one STA through multiple different Relay nodes. On the other hand, after one AP obtains a TXOP, it can directly schedule transmissions between one or more other APs and one or more Relay nodes. There is no need for other APs, Relay nodes, and STAs to compete for channel usage rights. After successfully obtaining a TXOP, the AP, Relay node, or STA can then transmit between the AP and the Relay node and / or the Relay node and the STA, thereby reducing the delay of relay transmission to a certain extent.

[0305] Scenario 8: Scheduling and transmission of multiple APs <-> multiple relay nodes <-> multiple STAs

[0306] In some embodiments of the present invention, the first node, the relay communication device and the at least one second node are respectively multiple first nodes (multiple APs), multiple relay communication devices (multiple Relay nodes) and multiple second nodes (multiple STAs), and the multiple first nodes provide relay services for at least one of the multiple second nodes through the multiple relay communication devices. The MU-RTS-TXS TF also instructs the one first node to obtain a transmission opportunity TXOP, schedule the transmission between the relay communication device and another one or more first nodes, and share part of the obtained TXOP time with the other one or more first nodes for use.

[0307] Figure 4H is a schematic diagram of the scheduling and transmission scenario of relay communication provided in an embodiment of the present application. As shown in Figure 5.3-9, there are multiple APs (i.e., AP 1 to AP a), multiple Relays (i.e., Relay 1 to Relay b) and multiple STAs (i.e., STA 1 to STA c) in the network, and multiple Relays can provide relay services to multiple STAs (i.e., STA 1 to STA c).

[0308] This example illustrates a situation where, after AP 1 obtains a TXOP, AP 1 first sends data to Relay 1-Relay b. AP 1 then shares part of its TXOP time with other APs (e.g., AP a in the figure) and Relay 1-Relay b (and STA 1-STA c) for relay transmission (e.g., AP a transmits data to Relay 1, and Relay 1-Relay b transmit data to STA 1-STA c). However, the present invention is not limited to this process. Alternatively, after obtaining a TXOP, AP 1 may first share part of the TXOP time with Relay 1-Relay b (and STA 1-STA c) for relay transmission (e.g., STA 1-STA c transmits data to Relay 1-Relay b). Then, data is transmitted between Relay 1-Relay b and AP 1 and / or AP a (e.g., Relay 1-Relay b transmits data to AP 1 and / or AP a).

[0309] The steps in FIG. 4H are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0310] 1) After AP 1 obtains a TXOP, it sends a data frame (e.g., Data i). The RA field of Data i is set to Relay 1's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that the data frame originates from AP 1, is sent by AP 1 to Relay 1, and is destined for STA 1.

[0311] 2) Relay 1 receives Data i from AP 1 and responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay 1 has received Data i, which AP 1 requested to be forwarded. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data i and does not need to confirm with AP 1.

[0312] 3) AP 1 sends Data j within the acquired TXOP. The RA field of Data j is set to Relay b's MAC address, the TA field is set to AP 1's MAC address, the SA field is set to AP 1's MAC address, and the DA field is set to STA 1's MAC address. This indicates that the Data frame originated from AP 1, was sent by AP 1 to Relay b, and was destined for STA 1.

[0313] 4) Relay b receives Data j from AP 1 and responds with an Ack / BlockAck frame to AP 1 after a SIFS interval, indicating that Relay b received Data j, which AP 1 requested it to forward. If it is an Ack frame, the RA is set to AP 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP 1's MAC address, and the TA is set to Relay b's MAC address. Note that this step can also be omitted, meaning that Relay b has not yet successfully forwarded Data j and does not need to confirm with AP 1.

[0314] 5) AP 1 sends a MU-RTS TXS TF to AP a and Relays 1 through b (and STAs 1 through c). AP 1 shares a portion of its allocated TXOP time (the specific time is indicated in the MU-RTS TXS TF) with AP a and Relays 1 through b (and STAs 1 through c). The TA of the MU-RTS TXS TF is set to AP 1's MAC address, and the RA can be set to a multicast address or a broadcast address. The User Info field in the User Info List of the MU-RTS TXS TF indicates the specific target recipients: AP a and Relays 1 through b (and STAs 1 through c). The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the duration of the shared TXOP time with other devices (e.g., AP a and / or Relays 1 through b and / or STAs 1 through c).

[0315] 6) After a SIFS interval between AP 1's MU-RTS TXS TF transmission, AP a and Relays 1 through Relay b (and STAs 1 through STA c) simultaneously reply with a CTS frame to AP 1, indicating their acceptance and use of the shared TXOP. The RA field of the CTS frames sent by AP a and Relays 1 through Relay b (and STAs 1 through STA c) is set to AP 1's MAC address. Note that some or all of STAs 1 through STA c may be outside AP 1's signal coverage. In this case, some or all of STAs 1 through STA c that cannot receive the MU-RTS TXS TF sent by AP 1 will not reply with a CTS frame. Only AP a, Relays 1 through Relay b, and STAs 1 through STA c that receive the MU-RTS TXS TF sent by AP 1 will reply with a CTS frame.

[0316] 7) AP a sends Data m, which needs to be relayed by Relay 1. The RA of Data m is set to Relay 1's MAC address, the TA is set to AP a's MAC address, the SA is set to AP a's MAC address, and the DA is set to the MAC address of STA 1 and / or STA c. This indicates that Data m originates from AP a, is sent by Relay 1 to STA 1, and is destined for STA 1 and / or STA c.

[0317] 8) Relay 1 receives Data m from AP a and responds with an Ack / BlockAck frame to AP a after a SIFS interval, indicating that Relay 1 received Data m, which AP a requested it to forward. If it is an Ack frame, the RA is set to AP a's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP a's MAC address, and the TA is set to Relay 1's MAC address. Note that this step can also be omitted, meaning that Relay 1 has not yet successfully forwarded Data m and does not need to confirm with AP a.

[0318] 9) AP a sends Data n, which needs to be relayed by Relay b. The RA of Data n is set to Relay b's MAC address, the TA is set to AP a's MAC address, the SA is set to AP a's MAC address, and the DA is set to the MAC address of STA 1 and / or STA c. This means that Data n originates from AP a, is sent by Relay b to STA 1 and / or STA c, and is destined for STA 1 and / or STA c.

[0319] 10) Relay b receives Data n from AP a and responds with an Ack / BlockAck frame to AP a after a SIFS interval, indicating that Relay b received Data n, which AP a requested it to forward. If it is an Ack frame, the RA is set to AP a's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to AP a's MAC address, and the TA is set to Relay b's MAC address. Note that this step can also be omitted, meaning that Relay b has not yet successfully forwarded Data n and does not need to confirm with AP a.

[0320] 11) Relay 1 sends a relayed Data frame (which may be part or all of Data i requested to be relayed by AP 1, part or all of Data m requested to be relayed by AP a, or part or all of Data i + Data m requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA 1, the TA is set to the MAC address of Relay 1, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA 1. This means that the data frame originates from AP 1 and / or AP a, is sent by Relay 1 to STA 1, and is destined for STA 1.

[0321] 12) STA 1 receives the relayed data frame sent by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA 1 has received the data frame forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and there is no TA. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA 1's MAC address.

[0322] 13) Relay 1 receives the Ack / BlockAck frame sent by STA 1 and sends a relayed Ack / BlockAck frame to AP 1 and / or AP a after a SIFS period, indicating that STA 1 has successfully received the Data frame that AP 1 and / or AP a requested Relay 1 to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to the MAC address of AP 1 and / or AP a, and there is no TA. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to the MAC address of AP 1 and / or AP a. 1 , TA is set to the MAC address of Relay 1.

[0323] 14) Relay 1 sends the relayed Data frame (which can be part or all of Data i requested to be relayed by AP 1, part or all of Data m requested to be relayed by AP a, or part or all of Data i + Data m requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA c, the TA is set to the MAC address of Relay 1, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA 1. This means that the data frame originates from AP 1 and / or AP a, is sent by Relay 1 to STA c, and is destined for STA c.

[0324] 15) STA c receives the relayed Data frame sent by Relay 1 and responds with an Ack / BlockAck frame to Relay 1 after a SIFS interval, indicating that STA c has received the Data frame forwarded by Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to STA c's MAC address.

[0325] 16) Relay 1 receives the Ack / BlockAck frame sent by STA c and sends a relayed Ack / BlockAck frame to AP 1 and / or AP a after a SIFS period, indicating that STA c has successfully received the Data frame that AP 1 and / or AP a requested Relay 1 to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to the MAC address of AP 1 and / or AP a, and there is no TA. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to the MAC address of AP 1 and / or AP a. 1 , TA is set to the MAC address of Relay 1.

[0326] 17) Relay b sends a relayed Data frame (which can be part or all of Data j requested to be relayed by AP 1, part or all of Data n requested to be relayed by AP a, or part or all of Data j + Data n requested to be forwarded by AP 1 and AP a, but this is not limited to this in the present invention). The RA of the relayed Data frame is set to STA 1's MAC address, the TA is set to Relay b's MAC address, the SA is set to the MAC address of AP 1 and / or AP a, and the DA is set to STA 1's MAC address. This indicates that the Data frame originated from AP 1 and / or AP a, was sent by Relay b to STA 1, and then destined for STA 1.

[0327] 18) STA 1 receives the relayed Data frame sent by Relay b and responds with an Ack / BlockAck frame to Relay b after a SIFS interval, indicating that STA 1 has received the Data frame forwarded by Relay b. If it is an Ack frame, the RA is set to Relay b's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay b's MAC address, and the TA is set to STA 1's MAC address.

[0328] 19) Relay b receives the Ack / BlockAck frame sent by STA 1 and sends a relayed Ack / BlockAck frame to AP 1 and / or AP a after a SIFS period, indicating that STA 1 has successfully received the Data frame that AP 1 and / or AP a requested Relay b to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to the MAC address of AP 1 and / or AP a, and there is no TA. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to the MAC address of AP 1 and / or AP a. 1 , TA is set to the MAC address of Relay b.

[0329] 20) Relay b sends a relayed Data frame (which may be part or all of Data j requested to be relayed by AP 1, part or all of Data n requested to be relayed by AP a, or part or all of Data j + Data n requested to be forwarded by AP 1 and AP a, which is not limited in the present invention). The RA of the relayed Data frame is set to the MAC address of STA c, the TA is set to the MAC address of Relay b, and the SA is set to the MAC address of AP 1 and / or AP a. 1 , DA is set to the MAC address of STA 1. This means that the data frame originates from AP 1 and / or AP a, is sent by Relay b to STA c, and then the destination node is STA c.

[0330] 21) STA c receives the relayed data frame sent by Relay b and responds with an Ack / BlockAck frame to Relay b after a SIFS interval, indicating that STA c received the data frame forwarded by Relay b. If it is an Ack frame, the RA is set to Relay b's MAC address, and no TA exists. If it is a BlockAck frame, the RA is set to Relay b's MAC address, and the TA is set to STA c's MAC address.

[0331] 22) Relay b receives the Ack / BlockAck frame from STA c and, after a SIFS, sends a relayed Ack / BlockAck frame to AP 1 and / or AP a. This indicates that STA c successfully received the data frame that AP 1 and / or AP a requested Relay b to forward. If the relayed Ack frame is a relayed Ack frame, the RA is set to the MAC address of AP 1 and / or AP a, and no TA exists. If the relayed BlockAck frame is a relayed BlockAck frame, the RA is set to the MAC address of AP 1 and / or AP a, and the TA is set to the MAC address of Relay b.

[0332] 23) After completing the relay transmission within the TXOP shared by AP 1, if there is still time remaining, AP a and / or Relay 1 to Relay b and / or STA 1 to STA c can proactively send a termination frame (such as a CF-End frame or other frame) to AP 1 to return the remaining TXOP time to AP 1 for continued use; or if AP 1 detects through CCA that the channel idle time is greater than or equal to the PIFS duration, it proactively reclaims the TXOP usage right and AP 1 continues with other operations.

[0333] MAC address: If Relay 1 relays part or all of Data i + Data m requested by both AP 1 and AP a, or if Relay b relays part or all of Data j + Data n requested by both AP 1 and AP a, SA can be handled using the following two methods.

[0334] i. SA is set to the multicast address corresponding to AP 1 and AP a. (The multicast address information must be negotiated in advance with Relay 1 to Relay b and STA 1 to STA c.)

[0335] ii. Carry the MAC addresses of AP 1 and AP a in the Data frame (including SA).

[0336] The effects that can be achieved by this embodiment are as follows: In a scenario with multiple APs, multiple Relay nodes, and multiple STAs, on the one hand, this embodiment supports the effect of multiple APs providing relay services for one or more STAs through multiple different Relay nodes. On the other hand, after one of the APs obtains a TXOP, it can directly schedule transmissions between one or more other APs and one or more Relay nodes. There is no need for other APs, Relay nodes, and STAs to compete for channel usage rights respectively. After successfully obtaining a TXOP, the AP, Relay node, or STA then performs transmissions between the AP and the Relay node and / or the Relay node and the STA, thereby reducing the delay of relay transmission to a certain extent.

[0337] Scenario 9: Scheduling and transmission between multiple APs and one relay node and multiple STAs (taking the relay node obtaining and sharing TXOPs as an example)

[0338] In some embodiments of the present invention, taking the example of a Relay node obtaining and sharing TXOP, it is also applicable to the scheduling and transmission of 1 AP<->1 Relay node<->1 STA, the scheduling and transmission of 1 AP<->1 Relay node<->multiple STAs, the scheduling and transmission of 1 AP<->multiple Relay nodes<->1 STA, the scheduling and transmission of 1 AP<->multiple Relay nodes<->multiple STAs, the scheduling and transmission of multiple APs<->1 Relay node<->1 STA, the scheduling and transmission of multiple APs<->multiple Relay nodes<->1 STA, and the scheduling and transmission of multiple APs<->multiple Relay nodes<->multiple STAs.

[0339] As shown in FIG4I , there are multiple APs (i.e., AP 1 to AP a), one relay node (i.e., Relay 1) and multiple STAs (i.e., STA 1 to STA c) in the network, and the relay node provides relay services to the multiple STAs (i.e., STA 1 to STA c).

[0340] This example illustrates a situation where, after Relay 1 obtains a TXOP, Relay 1, as a (non-AP STA) node, has data Data a to send to AP a. Relay 1 then shares part of its obtained TXOP time with an AP (e.g., AP 1 in the figure) and a STA (e.g., STA c in the figure). (For example, AP 1 transmits Data b to Relay 1, and STA c transmits Data c to Relay 1.) However, the present invention is not limited to this process. Alternatively, after obtaining a TXOP, Relay 1 may first share part of the TXOP time with STA 1, and then share part of the TXOP time with AP a.

[0341] The steps in FIG. 4I are as follows (the present invention is not limited to the following process, and only some of the steps may be performed, or the order of some steps may be changed):

[0342] 1) After obtaining a TXOP, Relay 1 sends a data frame (e.g., Data a). The RA field of Data a is set to AP a's MAC address, the TA field is set to Relay 1's MAC address, the SA field is set to Relay 1's MAC address, and the DA field is set to AP a's MAC address. This indicates that the data frame originated from Relay 1, was sent by Relay 1 to AP a, and is destined for AP a.

[0343] 2) AP a receives Data a from Relay 1 and responds with an Ack / BlockAck frame after a SIFS interval, indicating that AP a received Data a from Relay 1. If it is an Ack frame, the RA is set to Relay 1's MAC address, and no TA is present. If it is a BlockAck frame, the RA is set to Relay 1's MAC address, and the TA is set to AP a's MAC address. Note that this step can also be omitted, meaning that Relay 1 itself has no data to send to AP a.

[0344] 3) Relay 1 sends a MU-RTS TXS TF to AP 1. Relay 1 shares part of the TXOP time it obtains (the specific time is indicated in the MU-RTS TXS TF) with AP 1 for use. The TA of the MU-RTS TXS TF is set to the MAC address of Relay 1, and the RA is set to the MAC address, broadcast address, or multicast address of AP 1. If it is set to a broadcast address or multicast address, the User Info field in the User Info List in the MU-RTS TXS TF indicates that the specific target recipient is AP 1.

[0345] Specific time: The Allocation Duration field of the User Info field of the MU-RTS TXS TF indicates the length of time shared with other devices (eg, AP 1 to AP a and / or STA 1 to STA c).

[0346] 4) After Relay 1 sends the MU-RTS TXS TF, AP 1 replies with a CTS frame to Relay 1, indicating that it accepts and uses the TXOP shared by Relay 1. The RA of the CTS frame sent by AP 1 is set to Relay 1's MAC address.

[0347] 5) AP 1 sends Data b which needs to be relayed by Relay 1 to STA 1. The RA of Data b is set to the MAC address of Relay 1, the TA is set to the MAC address of AP 1, the SA is set to the MAC address of AP 1, and the DA is set to

[0348] MAC address of STA 1. This means that Data b originates from AP 1, is sent by Relay 1 to STA 1, and then

[0349] The destination node is STA 1.

[0350] 6) Relay 1 receives Data b from AP 1 and responds to AP 1 with an Ack / BlockAck frame after SIFS time, indicating that

[0351] Relay 1 receives Data b, which AP 1 requests to forward. If it is an Ack frame, RA is set to AP 1's MAC address, and TA does not exist. If it is a BlockAck frame, RA is set to AP 1's MAC address, and TA is set to Relay 1's MAC address. It is worth noting that this step can also be absent, that is, at this time Relay 1 has not successfully completed Data b.

[0352] Forwarding does not require confirmation to AP 1.

[0353] 7) After the time shared by AP 1 (i.e., TXOP allocated for AP 1 in the figure) ends, Relay 1 re-sends the relayed Data frame (which can be part or all of Data b requested to be relayed by AP 1, which is not limited in the present invention) as the TXOP holder (within the TXOP used by Relay 1), where the RA of the relayed Data frame is set to STA 1's

[0354] MAC address, TA is set to the MAC address of Relay 1, SA is set to the MAC address of AP 1, and DA is set to

[0355] MAC address of STA 1. This indicates that the data frame originated from AP 1, was sent by Relay 1 to STA 1, and was destined for STA 1.

[0356] 8) STA 1 receives the relayed Data frame sent by Relay 1 and responds to Relay 1 with an Ack / BlockAck frame after SIFS time, indicating that STA 1 has received the Data frame forwarded by Relay 1. If it is an Ack frame, RA is set to Relay 1.

[0357] 1's MAC address, there is no TA. If it is a BlockAck frame, RA is set to Relay 1's MAC address.

[0358] TA is set to the MAC address of STA 1.

[0359] 9) Relay 1 receives the Ack / BlockAck frame sent by STA 1 and sends a relayed Ack / BlockAck frame to AP 1 after SIFS time.

[0360] Ack / BlockAck frame means that STA 1 has successfully received the Data frame that AP 1 requested Relay 1 to forward. If the relay receives an Ack frame, RA is set to AP 1's MAC address and there is no TA. If the relay receives a BlockAck frame,

[0361] RA is set to the MAC address of AP 1, and TA is set to the MAC address of Relay 1.

[0362] 10) Relay 1 (within the TXOP used by Relay 1) continues to send MU-RTS TXS TF to STA c. Relay 1 shares part of the TXOP time it obtains (the specific time is indicated in the MU-RTS TXS TF) with STA c.

[0363] The TA of the MU-RTS TXS TF is set to the MAC address of Relay 1, and the RA is set to the MAC address, broadcast address, or multicast address of STA c. If it is set to a broadcast address or a multicast address, the User Info List in the MU-RTS TXS TF

[0364] The User Info field in the MU-RTS TXS TF indicates that the specific target receiver is STA c. Specific time: The Allocation Duration field in the User Info field of the MU-RTS TXS TF indicates the duration shared with other devices (such as AP 1 to AP a and / or STA 1 to

[0365] The length of time of STA c).

[0366] 11) After Relay 1 sends the MU-RTS TXS TF, STA c replies with a CTS frame to Relay 1, indicating that it accepts and uses the TXOP shared by Relay 1. The RA of the CTS frame sent by STA c is set to the MAC address of Relay 1.

[0367] 12) STA c sends Data c, which needs to be relayed by Relay 1 to AP a. The RA of the relayed Data c is set to the MAC address of Relay 1, the TA is set to the MAC address of STA c, the SA is set to the MAC address of STA c, and the DA is set to the MAC address of AP a. This means that Data c originates from STA c, is sent by Relay 1 to AP a, and then

[0368] The destination node is AP a.

[0369] 13) Relay 1 receives Data c from STA c. After SIFS, STA c responds with an Ack / BlockAck frame, indicating that

[0370] Relay 1 receives Data c, which STA c requests to forward. If it is an Ack frame, RA is set to STA c's MAC address, and there is no TA. If it is a BlockAck frame, RA is set to STA c's MAC address, and TA is set to Relay 1.

[0371] 1's MAC address. Note that this step may not be necessary, meaning that Relay 1 has not yet successfully forwarded Data c and does not need to confirm with STA c.

[0372] 14) Relay 1 sends the relayed Data frame (which can be part or all of Data c requested to be relayed by STA c, and the present invention is not limited to this). The RA of the relayed Data frame is set to the MAC address of AP a, and the TA is set to Relay 1.

[0373] The MAC address of relay 1 is set, SA is set to the MAC address of STA c, and DA is set to the MAC address of AP a. This means that the data frame originated from STA c, was sent by relay 1 to AP a, and then the destination node is AP a.

[0374] 15) AP a receives the relayed Data frame sent by Relay 1 and responds with an Ack / BlockAck to Relay 1 after SIFS time.

[0375] A frame indicates that AP a received a Data frame forwarded by Relay 1. If it is an Ack frame, RA is set to Relay 1's MAC address, and no TA exists. If it is a BlockAck frame, RA is set to Relay 1's MAC address, and TA is set to AP a's MAC address.

[0376] 16) Relay 1 receives the Ack / BlockAck frame from AP a and, after a SIFS, sends a relayed Ack / BlockAck frame to STA c. This indicates that AP a successfully received the Data frame that STA c requested Relay 1 to forward. If a relayed Ack frame is used, the RA is set to STA c's MAC address, and no TA exists. If a relayed BlockAck frame is used, the RA is set to STA c's MAC address, and the TA is set to Relay 1's MAC address.

[0377] The effects that can be achieved by this embodiment are as follows: In a scenario with multiple APs, one Relay node, and multiple STAs, on the one hand, this embodiment supports the effect of multiple APs providing relay services for one or more STAs through the same Relay node. On the other hand, after obtaining a TXOP, the Relay node can directly schedule transmissions between another one or more APs and the Relay node, as well as schedule transmissions between another one or more STAs and the Relay node. There is no need for the AP and STA to compete for channel usage rights separately. After successfully obtaining a TXOP, the AP, Relay node, or STA then performs transmissions between the AP and the Relay node and / or the Relay node and the STA, thereby reducing the delay of relay transmission to a certain extent.

[0378] Figure 5 is a schematic diagram of a wireless communication device 500 provided in an embodiment of the present application. The wireless communication device can be a relay communication device, an AP, or a STA. The wireless communication device 500 shown in Figure 5 includes a processor 510, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application. In some embodiments of the present invention, the AP includes an AP STA or an AP MLD, and the STA includes an AP STA or a non-AP STA or an AP MLD or a non-AP MLD.

[0379] Optionally, as shown in FIG5 , the wireless communication device 500 may further include a memory 520. The processor 510 may call and execute a computer program from the memory 520 to implement the method in the embodiment of the present application. The memory 520 may be a separate device independent of the processor 510 or may be integrated into the processor 510.

[0380] Optionally, as shown in FIG5 , the wireless communication device 500 may further include a transceiver 530. The processor 510 may control the transceiver 530 to communicate with other devices. Specifically, the transceiver 530 may send information or data to other devices or receive information or data sent by other devices. The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include one or more antennas.

[0381] Optionally, the wireless communication device 500 may specifically be a relay communication device in an embodiment of the present application, and the wireless communication device 500 may implement the corresponding processes implemented by the relay communication device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0382] Optionally, the wireless communication device 500 may specifically be a mobile AP in an embodiment of the present application, and the wireless communication device 500 may implement the corresponding processes implemented by the AP in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0383] Optionally, the wireless communication device 700 may be a STA in an embodiment of the present application, and the wireless communication device 700 may implement the corresponding processes implemented by the STA in each method of the embodiment of the present application. For the sake of brevity, they are not described here. In some embodiments of the present invention, the STA includes an AP STA or a non-AP STA or an AP MLD or a non-AP MLD.

[0384] Figure 6 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 600 shown in Figure 6 includes a processor 610, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0385] Optionally, as shown in FIG6 , the chip 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application. The memory 620 may be a separate device independent of the processor 610 or may be integrated into the processor 610.

[0386] Optionally, the chip 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0387] Optionally, the chip 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0388] Optionally, the chip can be applied to the relay communication device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the relay communication device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0389] Optionally, the chip can be applied to the AP in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the AP in each method in the embodiments of the present application. For the sake of brevity, they are not described here.

[0390] Optionally, the chip can be applied to the STA in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0391] FIG7 is a schematic block diagram of a wireless communication system 700 provided in an embodiment of the present application. As shown in FIG7 , the communication system 700 includes an AP 710, a relay communication device 720, and an STA 730. The AP 710 can be used to implement the corresponding functions implemented by the AP in the above method, the relay communication device 720 can be used to implement the corresponding functions implemented by the relay communication device in the above method, and the STA 730 can be used to implement the corresponding functions implemented by the STA in the above method. For the sake of brevity, these functions are not further described here.

[0392] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment may be completed by hardware integrated logic circuits in the processor or software instructions.

[0393] It is understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory. The embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

[0394] Optionally, the computer-readable storage medium may be applied to the relay communication device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the relay communication device in the various methods of the embodiments of the present application. For the sake of brevity, these processes are not described in detail here. Optionally, the computer-readable storage medium may be applied to the AP in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of the present application. For the sake of brevity, these processes are not described in detail here. Optionally, the computer-readable storage medium may be applied to the STA in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, these processes are not described in detail here.

[0395] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0396] Optionally, the computer program product may be applied to the relay communication device in the embodiments of the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the relay communication device in the various methods of the embodiments of the present application. For the sake of brevity, these instructions are not described in detail here. Optionally, the computer program product may be applied to the AP in the embodiments of the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of the present application. For the sake of brevity, these instructions are not described in detail here. Optionally, the computer program product may be applied to the STA in the embodiments of the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, these instructions are not described in detail here.

[0397] The embodiment of the present application also provides a computer program.

[0398] Optionally, the computer program may be applied to the relay communication device in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the relay communication device in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. Optionally, the computer program may be applied to the AP in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the AP in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. Optionally, the computer program may be applied to the STA in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the STA in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here.

[0399] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0400] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A relay communication device, comprising: A relay function unit, wherein the relay function unit performs local reception or selective forwarding of Media Access Control Protocol Data Unit (MPDU) between an upper-level node and a lower-level node based on the destination address (DA) of the received frame; and An Aggregate Media Access Control Protocol Data Unit (A-MPDU) deaggregation unit for communicating with the relay function unit, wherein if the A-MPDU deaggregation unit receives the frame sent by the upper-level node, the A-MPDU deaggregation unit performs A-MPDU deaggregation on the received frame.

2. The relay communication device according to claim 1 further includes an MPDU header and a cyclic redundancy check (CRC) verification unit for communicating with the A-MPDU deaggregation unit, wherein, If the MPDU header and CRC verification unit receives the frame sent by the upper-level node through the A-MPDU deaggregation unit, the MPDU header and CRC verification unit performs MPDU header and CRC verification on the received frame.

3. The relay communication device according to claim 2 further includes an address filtering unit configured to communicate with the MPDU header and CRC verification unit, wherein, If the address filtering unit receives the frame sent by the upper-level node through the MPDU header and CRC verification unit, the address filtering unit performs address filtering on the received frame.

4. The relay communication device according to claim 3 further includes a block acknowledgment scoreboard for communicating with the address filtering unit, wherein, If the block acknowledgment scoreboard receives the frame sent by the upper-level node through the address filtering unit, the block acknowledgment scoreboard performs acknowledgment scoring on the received frame.

5. The relay communication device according to claim 4 further includes a duplicate detection unit configured to communicate with the block acknowledgment scoreboard, wherein, If the duplicate detection unit receives the frame sent by the upper-level node through the block acknowledgment scoreboard, the duplicate detection unit performs duplicate detection on the received frame.

6. The relay communication device according to claim 5 further includes a playback detection unit for communicating with the duplicate detection unit, wherein, If the replay detection unit receives the frame sent by the upper-level node through the duplicate detection unit, the replay detection unit performs replay detection on the received frame, wherein the replay detection unit is used to receive data or robust management frames from another station (STA) to detect whether the received data or robust management frames are unauthorized retransmissions.

7. The relay communication device according to any one of claims 1 to 6 further includes an MPDU header and CRC creation unit for communicating with the relay function unit, wherein, If the MPDU header and CRC creation unit receives the frame sent by the lower-level node through the relay function unit, the MPDU header and CRC creation unit performs MPDU header and CRC creation on the received frame.

8. The relay communication device according to claim 7 further includes an A-MPDU aggregation unit for communicating with the MPDU header and CRC creation unit, wherein, If the A-MPDU aggregation unit receives the frame sent by the lower-level node through the MPDU header and CRC creation unit, the A-MPDU aggregation unit performs A-MPDU aggregation on the received frame.

9. The relay communication device according to any one of claims 1 to 8, wherein, The relay communication device is a non-Multi-Link Device Station (non-MLD STA), and the relay communication device further includes an MPDU encryption and integrity unit, and the relay function unit is configured between the MPDU encryption and integrity unit and the MPDU header and CRC creation unit to perform transmission.

10. The relay communication device according to claim 9, wherein, The relay communication device further includes an MPDU decryption and integrity unit, and the relay function unit is configured between the replay detection unit and the MPDU decryption and integrity unit to perform reception.

11. The relay communication device according to any one of claims 1 to 8, wherein, The relay communication device is a multi-link device station (MLD). The relay communication device further includes an MPDU encryption unit and a traffic identifier (TID) to link mapping unit. The relay function unit is configured between the MPDU encryption unit and the TID to link mapping unit to perform transmission.

12. The relay communication device according to claim 11, wherein, The relay communication device further includes a link aggregation unit. The relay function unit is configured between the link aggregation unit and the block acknowledgment scoreboard to perform reception.

13. The relay communication device according to claim 12, wherein, The relay communication device further includes an MLD upper layer media access control (MAC) sublayer. At least one of the relay function unit, the MPDU encryption unit, the TID to link mapping unit, the link aggregation unit, and the block acknowledgment scoreboard is configured in the MLD upper layer MAC sublayer.

14. The relay communication device according to any one of claims 1 to 13, wherein, The frame is a unicast frame, a broadcast frame, or a multicast frame.

15. A relay communication method, which is executed on a relay communication device, wherein, The relay communication method includes: Receiving a multi-user request to send transmission opportunity sharing trigger frame (MU-RTS-TXS TF) sent by a first node, where the MU-RTS-TXS TF indicates the transmission opportunity (TXOP) obtained by the first node. Scheduling a transmission between the relay communication device and a plurality of second nodes and sharing a part of the obtained TXOP for use by the relay communication device and the plurality of second nodes.

16. The relay communication method according to claim 15, wherein, The relay communication method further includes determining an allocation policy for the TXOP of the relay communication device and the plurality of second nodes.

17. The relay communication method according to claim 16, wherein, The allocation policy of the TXOP is determined by the first node according to the buffer states of the relay communication device and the plurality of second nodes.

18. The relay communication method according to claim 16, wherein, The allocation policy of the TXOP is determined by the relay communication device according to the buffer states of the first node and the plurality of second nodes.

19. The relay communication method according to claim 15, wherein, The sharing a part of the obtained TXOP for use by the relay communication device and the plurality of second nodes includes: The relay communication device shares a part of the TXOP for use by at least one of the plurality of second nodes by sending indication signaling to the plurality of second nodes, so as to receive data sent by at least one of the plurality of second nodes during the part of the time.

20. The relay communication method according to claim 15, wherein, When the channel idle duration is an inter-frame space (xIFS), the relay communication device receives data sent by the plurality of second nodes to relay the data to the first node. The length of the xIFS is greater than the length of the short inter-frame space (SIFS), and the xIFS is less than or equal to the length of the point coordination function inter-frame gap (PIFS).

21. The relay communication method according to claim 15, wherein, The scheduling includes: receiving data to be transmitted and the receiving address (RA) or destination address (DA) of the data to be transmitted, and transmitting the data to be transmitted according to the RA or the DA.

22. The relay communication method according to claim 21, wherein, There are a plurality of relay communication devices. The RAs of the data to be transmitted respectively indicate the plurality of relay communication devices, and the DAs of the data to be transmitted respectively indicate the plurality of second nodes.

23. The relay communication method according to claim 21, wherein, There are a plurality of relay communication devices. The RAs of the data to be transmitted respectively indicate the plurality of relay communication devices, and the DA of the data to be transmitted indicates the same second node.

24. The relay communication method according to claim 21, wherein, There are multiple relay communication devices, and there are multiple data to be transmitted. The RAs of the multiple data to be transmitted respectively indicate multiple relay communication devices, and the DAs of the multiple data to be transmitted respectively indicate the multiple second nodes.

25. The relay communication method according to claim 21, wherein there are multiple relay communication devices, and there are multiple data to be transmitted. The RAs of the multiple data to be transmitted respectively indicate multiple relay communication devices, and the DAs of the multiple data to be transmitted indicate the same second node.

26. The relay communication method according to claim 15, the relay communication method further comprising: Before obtaining the partial time of the TXOP, the relay communication device performs data transmission with the first node.

27. The relay communication method according to claim 15, the relay communication method further comprising: After obtaining the partial time of the TXOP, the relay communication device performs data transmission with the first node.

28. The relay communication method according to any one of claims 15 to 27, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, one relay communication device, and multiple second nodes. The one relay communication device provides relay services for the multiple second nodes.

29. The relay communication method according to any one of claims 15 to 27, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and one second node. The multiple relay communication devices provide relay services for the one second node.

30. The relay communication method according to any one of claims 15 to 27, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and multiple second nodes. At least one of the multiple relay communication devices provides relay services for at least one of the multiple second nodes.

31. The relay communication method according to any one of claims 15 to 27, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and one second node. The multiple first nodes provide relay services for the one second node through the one relay communication device. The MU-RTS-TXS TF further indicates that after the one first node obtains the transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares the obtained partial time of the TXOP for the use of the another or multiple first nodes.

32. The relay communication method according to any one of claims 15 to 27, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and multiple second nodes. The multiple first nodes provide relay services for at least one of the multiple second nodes through the one relay communication device. The MU-RTS-TXS TF further indicates that after the one first node obtains the transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares the obtained partial time of the TXOP for the use of the another or multiple first nodes.

33. The relay communication method according to any one of claims 15 to 27, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, multiple relay communication devices, and one second node. The multiple first nodes provide relay services for the one second node through the multiple relay communication devices. The MU-RTS-TXS TF also instructs that after a first node obtains a transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares a part of the obtained TXOP time for the use of the another or multiple first nodes.

34. The relay communication method according to any one of claims 15 to 27, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, multiple relay communication devices, and multiple second nodes. The multiple first nodes provide relay services for at least one of the multiple second nodes through the multiple relay communication devices. The MU-RTS-TXS TF also instructs that after a first node obtains a transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares a part of the obtained TXOP time for the use of the another or multiple first nodes.

35. A relay communication method, which is executed by a relay communication device, wherein, The relay communication method includes: Sending a multi-user request to send transmission opportunity sharing trigger frame MU-RTS-TXS TF to at least one first node and / or at least one second node, where the MU-RTS-TXS TF instructs that after the relay communication device obtains a transmission opportunity TXOP, it schedules the transmission between the first node and at least one second node and shares a part of the obtained TXOP time for the use of the first node and the at least one second node, and at least one of the first node, the relay communication device, and the at least one second node is multiple.

36. The relay communication method according to claim 35, the relay communication method further includes: Before obtaining the TXOP, the relay communication device performs data transmission with the first node and / or the at least one second node.

37. The relay communication method according to claim 35, the relay communication method further includes: After obtaining the TXOP, the relay communication device performs data transmission with the first node and / or the at least one second node.

38. The relay communication method according to any one of claims 35 to 37, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, one relay communication device, and multiple second nodes, and the one relay communication device provides relay services for the multiple second nodes.

39. The relay communication method according to any one of claims 35 to 37, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and one second node. The multiple relay communication devices provide relay services for the one second node. The MU-RTS-TXS TF also instructs that after a relay communication device obtains a transmission opportunity TXOP, it schedules the transmission between the first node and / or the at least one second node and another or multiple relay communication devices and shares a part of the obtained TXOP time for the use of the another or multiple relay communication devices.

40. The relay communication method according to any one of claims 35 to 37, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and multiple second nodes. At least one of the multiple relay communication devices provides relay services for at least one of the multiple second nodes. The MU-RTS-TXS TF also instructs that after a relay communication device obtains a transmission opportunity TXOP, it schedules the transmission between the first node and / or the at least one second node and another or multiple relay communication devices, and shares a part of the obtained TXOP time for the use of the another or multiple relay communication devices.

41. The relay communication method according to any one of claims 35 to 37, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and one second node. The multiple first nodes provide relay services for the one second node through the one relay communication device.

42. The relay communication method according to any one of claims 35 to 37, wherein The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and multiple second nodes. The multiple first nodes provide relay services for at least one of the multiple second nodes through the one relay communication device.

43. The relay communication method according to any one of claims 35 to 37, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, multiple relay communication devices, and one second node. The multiple first nodes provide relay services for the one second node through the multiple relay communication devices. The MU-RTS-TXS TF also instructs that after a relay communication device obtains a transmission opportunity TXOP, it schedules the transmission between the first node and / or the at least one second node and another or multiple relay communication devices, and shares a part of the obtained TXOP time for the use of the another or multiple relay communication devices.

44. The relay communication method according to any one of claims 35 to 37, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, multiple relay communication devices, and multiple second nodes. The multiple first nodes provide relay services for at least one of the multiple second nodes through the multiple relay communication devices. The MU-RTS-TXS TF also instructs that after a relay communication device obtains a transmission opportunity TXOP, it schedules the transmission between the first node and / or the at least one second node and another or multiple relay communication devices, and shares a part of the obtained TXOP time for the use of the another or multiple relay communication devices.

45. A relay communication method, which is executed on a first node, wherein, The relay communication method includes: Sending a multi-user request-to-send transmission opportunity sharing trigger frame MU-RTS-TXS TF to a relay communication device, where the MU-RTS-TXS TF indicates the transmission opportunity TXOP obtained by the first node; Scheduling the transmission between the relay communication device and multiple second nodes, and sharing a part of the obtained TXOP time for the use of the relay communication device and the multiple second nodes.

46. The relay communication method according to claim 45, wherein, The relay communication method further includes determining an allocation strategy for the TXOP of the relay communication device and the multiple second nodes.

47. The relay communication method according to claim 46, wherein, The allocation policy of the TXOP is determined by the first node according to the buffer states of the relay communication device and the multiple second nodes.

48. The relay communication method according to claim 46, wherein, The allocation policy of the TXOP is determined by the relay communication device according to the buffer states of the first node and the multiple second nodes.

49. The relay communication method according to claim 45, wherein, Sharing a part of the obtained TXOP time for use by the relay communication device and the multiple second nodes includes: The relay communication device shares a part of the TXOP time for use by at least one of the multiple second nodes by sending indication signaling to the multiple second nodes, so as to receive data sent by at least one of the multiple second nodes during the part of the time.

50. The relay communication method according to claim 45, wherein, When the channel idle duration is the inter-frame spacing xIFS, the first node receives data sent by the multiple second nodes through the relay communication device, where the length of the xIFS is greater than the length of the short inter-frame space SIFS, and the xIFS is less than or equal to the length of the point coordination function inter-frame gap PIFS.

51. The relay communication method according to claim 45, wherein, The scheduling includes: determining the data to be transmitted and the receiving address RA or the destination address DA of the data to be transmitted, and determining the transmission of the data to be transmitted according to the RA or the DA.

52. The relay communication method according to claim 51, wherein, There are multiple relay communication devices, and the RAs of the data to be transmitted respectively indicate the multiple relay communication devices, and the DAs of the data to be transmitted respectively indicate the multiple second nodes.

53. The relay communication method according to claim 51, wherein, There are multiple relay communication devices, and the RAs of the data to be transmitted respectively indicate the multiple relay communication devices, and the DA of the data to be transmitted indicates the same second node.

54. The relay communication method according to claim 51, wherein, There are multiple relay communication devices, and there are multiple data to be transmitted. The RAs of the multiple data to be transmitted respectively indicate the multiple relay communication devices, and the DAs of the multiple data to be transmitted respectively indicate the multiple second nodes.

55. The relay communication method according to claim 51, wherein there are multiple relay communication devices, and there are multiple data to be transmitted. The RAs of the multiple data to be transmitted respectively indicate the multiple relay communication devices, and the DAs of the multiple data to be transmitted indicate the same second node.

56. The relay communication method according to claim 55, the relay communication method further includes: Before obtaining the part of the TXOP time, the relay communication device performs data transmission with the first node.

57. The relay communication method according to claim 45, the relay communication method further includes: After obtaining the part of the TXOP time, the relay communication device performs data transmission with the first node.

58. The relay communication method according to any one of claims 45 to 57, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, one relay communication device, and multiple second nodes. The one relay communication device provides relay services for the multiple second nodes.

59. The relay communication method according to any one of claims 45 to 57, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and one second node. The multiple relay communication devices provide relay services for the one second node.

60. The relay communication method according to any one of claims 45 to 57, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and multiple second nodes, and at least one of the multiple relay communication devices provides relay services for at least one of the multiple second nodes.

61. The relay communication method according to any one of claims 45 to 57, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and one second node. The multiple first nodes provide relay services for the one second node through the one relay communication device. The MU-RTS-TXS TF further instructs that after the one first node obtains the transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares a part of the obtained TXOP time for the use of the another or multiple first nodes.

62. The relay communication method according to any one of claims 45 to 57, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and multiple second nodes. The multiple first nodes provide relay services for at least one of the multiple second nodes through the one relay communication device. The MU-RTS-TXS TF further instructs that after the one first node obtains the transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares a part of the obtained TXOP time for the use of the another or multiple first nodes.

63. The relay communication method according to any one of claims 45 to 57, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, multiple relay communication devices, and one second node. The multiple first nodes provide relay services for the one second node through the multiple relay communication devices. The MU-RTS-TXS TF further instructs that after the one first node obtains the transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares a part of the obtained TXOP time for the use of the another or multiple first nodes.

64. The relay communication method according to any one of claims 45 to 57, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, multiple relay communication devices, and multiple second nodes. The multiple first nodes provide relay services for at least one of the multiple second nodes through the multiple relay communication devices. The MU-RTS-TXS TF further instructs that after the one first node obtains the transmission opportunity TXOP, it schedules the transmission between the relay communication device and another or multiple first nodes and shares a part of the obtained TXOP time for the use of the another or multiple first nodes.

65. A relay communication method, which is executed by a first node, wherein, The relay communication method includes: Receive a multi-user request to send a transmission opportunity sharing trigger frame MU-RTS-TXS TF sent by a relay communication device, where the MU-RTS-TXS TF indicates that after the relay communication device obtains a transmission opportunity TXOP, it schedules a transmission between the first node and at least one second node and shares a part of the obtained TXOP time for use by the first node and the at least one second node, where at least one of the first node, the relay communication device, and the at least one second node is multiple.

66. The relay communication method according to claim 65, the relay communication method further comprising: Before obtaining the TXOP, the relay communication device performs data transmission with the first node and / or the at least one second node.

67. The relay communication method according to claim 65, the relay communication method further comprising: After obtaining the TXOP, the relay communication device performs data transmission with the first node and / or the at least one second node.

68. The relay communication method according to any one of claims 65 to 67, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, one relay communication device, and multiple second nodes, and the one relay communication device provides relay services for the multiple second nodes.

69. The relay communication method according to any one of claims 65 to 67, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and one second node, the multiple relay communication devices provide relay services for the one second node, and the MU-RTS-TXS TF further indicates that after the one relay communication device obtains a transmission opportunity TXOP, it schedules a transmission between the first node and / or the at least one second node and another or multiple relay communication devices and shares a part of the obtained TXOP time for use by the another or multiple relay communication devices.

70. The relay communication method according to any one of claims 65 to 67, wherein, The first node, the relay communication device, and the at least one second node are respectively one first node, multiple relay communication devices, and multiple second nodes, at least one of the multiple relay communication devices provides relay services for at least one of the multiple second nodes, and the MU-RTS-TXS TF further indicates that after the one relay communication device obtains a transmission opportunity TXOP, it schedules a transmission between the first node and / or the at least one second node and another or multiple relay communication devices and shares a part of the obtained TXOP time for use by the another or multiple relay communication devices.

71. The relay communication method according to any one of claims 65 to 67, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and one second node, and the multiple first nodes provide relay services for the one second node through the one relay communication device.

72. The relay communication method according to any one of claims 65 to 67, wherein, The first node, the relay communication device, and the at least one second node are respectively multiple first nodes, one relay communication device, and multiple second nodes, and the multiple first nodes provide relay services for at least one of the multiple second nodes through the one relay communication device.

73. The relay communication method according to any one of claims 65 to 67, wherein, The first node, the relay communication device, and the at least one second node are respectively a plurality of first nodes, a plurality of relay communication devices, and one second node. The plurality of first nodes provide relay services for the one second node through the plurality of relay communication devices. The MU-RTS-TXS TF further instructs that after one relay communication device obtains a transmission opportunity TXOP, it schedules the transmission between the first node and / or the at least one second node and another or multiple relay communication devices and shares a part of the obtained TXOP time for the use of the another or multiple relay communication devices.

74. The relay communication method according to any one of claims 65 to 67, wherein, The first node, the relay communication device, and the at least one second node are respectively a plurality of first nodes, a plurality of relay communication devices, and a plurality of second nodes. The plurality of first nodes provide relay services for at least one of the plurality of second nodes through the plurality of relay communication devices. The MU-RTS-TXS TF further instructs that after one relay communication device obtains a transmission opportunity TXOP, it schedules the transmission between the first node and / or the at least one second node and another or multiple relay communication devices and shares a part of the obtained TXOP time for the use of the another or multiple relay communication devices.

75. A wireless communication device, comprising: A processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 15 to 74.

Images