Communication method, communication apparatus, and communication system

Abstract

The present application provides a communication method, a communication apparatus, and a communication system. The method comprises: in a transmission opportunity window which can be used for transmitting a non-low-delay service frame, allocating an uplink transmission resource to an LLT STA, the uplink transmission resource being used for transmitting an uplink low-delay service frame or low-delay service report frame. The preemptive transmission of low-delay services is realized, the timely sending of the low-delay services is ensured, and the user experience is enhanced.

Description

Communication method, communication device and communication system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on August 31, 2023, with application number 202311130187.2 and application name “A communication method, communication device and communication system”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of wireless communication technology, and in particular to a communication method, a communication device, and a communication system. Background Art

[0004] One of the primary goals of the next-generation Wireless Fidelity (WiFi) protocol is to reduce service transmission latency. For example, if a network device and a terminal are transmitting a non-low-latency service, and a low-latency service is required in the uplink or downlink, how to ensure the fast transmission of the low-latency service remains a challenge.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a communication method, a communication device, and a communication system for ensuring the timely delivery of low-latency services to improve user experience.

[0007] In a first aspect, embodiments of the present application provide a communication method that can be performed by a network device or a module (e.g., a chip) within a WiFi system. The method includes: transmitting a first frame, the first frame indicating a first uplink transmission resource; and receiving a first uplink low-latency service frame or a low-latency service report frame from at least one terminal device on the first uplink transmission resource within a transmission opportunity window, where the transmission opportunity window can be used to transmit non-low-latency service frames.

[0008] The above solution allocates uplink transmission resources to the terminal device within the transmission opportunity window that can be used to transmit non-low-latency service frames, so as to transmit uplink low-latency service frames or low-latency service report frames, thereby preempting the transmission of low-latency services, ensuring the timely delivery of low-latency services, and helping to improve user experience.

[0009] In one possible implementation method, the sending of the first frame includes: sending the first frame in a first time period within the transmission opportunity window; the receiving of the first uplink low-latency service frame from at least one terminal device on the first uplink transmission resource within the transmission opportunity window includes: receiving the first uplink low-latency service frame from the at least one terminal device in the first time period and on the first uplink transmission resource, and the data volume of the first uplink low-latency service frame is less than a first threshold.

[0010] The above solution can send uplink low-latency service frames with a data volume less than the first threshold in a timely manner, which helps to ensure the timely transmission of low-latency services.

[0011] In one possible implementation method, the low-latency service report frame is used to indicate the data volume of the uplink low-latency service to be transmitted; the method also includes: sending a second frame in a second time period within the transmission opportunity window, the second frame is used to indicate a second uplink transmission resource, and the second uplink transmission resource is determined based on the low-latency service report frame; receiving a second uplink low-latency service frame from the at least one terminal device in the second time period and the second uplink transmission resource, and the second uplink low-latency service frame is used to transmit the uplink low-latency service to be transmitted.

[0012] The above scheme first indicates the data volume of the uplink low-latency service to be transmitted through the low-latency service report frame, and then the network equipment allocates appropriate uplink transmission resources for the uplink low-latency service to be transmitted, and instructs the terminal equipment to send the uplink low-latency service frame on the allocated uplink transmission resources. This can ensure that appropriate uplink transmission resources are allocated for the uplink low-latency service, which helps to ensure the correct transmission of the low-latency service.

[0013] In one possible implementation method, the method further includes: sending an aggregate frame to the at least one terminal device within the transmission opportunity window, wherein the aggregate frame includes a confirmation frame for the first uplink low-latency service frame and a confirmation frame for the second uplink low-latency service frame.

[0014] In one possible implementation method, the method also includes: sending a downlink low-latency service frame within a third time period within the transmission opportunity window, the downlink low-latency service frame including downlink low-latency service data and a transmission resource indication, and the transmission resource indication is used to indicate the transmission resources of the downlink low-latency service data.

[0015] The above solution sends downlink low-latency service frames to the terminal device within the transmission opportunity window that can be used to transmit non-low-latency service frames, thereby preempting the transmission of low-latency services, ensuring the timely transmission of low-latency services, and helping to improve user experience.

[0016] In a possible implementation method, the method further includes: sending a third frame within the transmission opportunity window, the third frame carrying a preemptive transmission indication, and the preemptive transmission indication is used to indicate whether low-latency services are allowed to preempt transmission after the transmission of the third frame is completed.

[0017] The above scheme, through the preemptive transmission indication, indicates to the terminal device whether the low-latency service preemptive transmission is allowed after the downlink low-latency service frame transmission is completed, which helps the terminal device accurately determine whether the uplink low-latency service preemptive transmission is possible.

[0018] In a possible implementation method, there is a time period for sending uplink low-latency service frames or low-latency service report frames after every fixed number of non-low-latency service frames in the transmission opportunity window.

[0019] In a possible implementation method, the transmission opportunity window does not include other frames for indicating uplink transmission resources except the first frame.

[0020] The above solution indicates uplink transmission resources to the terminal device only once within a transmission opportunity window, and the terminal device subsequently uses the uplink transmission resources to send uplink low-latency service data, thus saving signaling overhead.

[0021] In a possible implementation method, sending the first frame includes: sending the first frame before the transmission opportunity window.

[0022] The above scheme indicates the uplink transmission resources to the terminal device once before the transmission opportunity window. The terminal device will subsequently use the uplink transmission resources to send uplink low-latency service data. There is no need to indicate the uplink transmission resources to the terminal device within the transmission opportunity window, which can save signaling overhead.

[0023] In a possible implementation method, the method further includes: sending a beacon frame to the at least one terminal device, wherein the beacon frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0024] In a possible implementation method, the method further includes: sending a management frame, where the management frame is used to negotiate whether to support low-latency service preemptive transmission within the transmission opportunity window;

[0025] A response frame is received, where the response frame indicates that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0026] In a possible implementation method, the method further includes: receiving a management frame, where the management frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0027] In one possible implementation method, the network device is the initiator of the transmission opportunity window, then the downlink low-latency service frame sent by the network device can be preempted for transmission between any two downlink non-low-latency service frames, and the uplink low-latency service frame received by the network device can only be preempted for transmission during a specified time period within the transmission opportunity window.

[0028] In a possible implementation method, the method further includes: sending a fourth frame within the specified time period, where the fourth frame is used to request the at least one terminal device to report a low-latency service report.

[0029] In a possible implementation method, the fourth frame is also used to indicate the next designated time period.

[0030] In one possible implementation method, the network device is the initiator of the transmission opportunity window, then the non-low-latency service frame sent by the network device can be interrupted to preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-low-latency service frame continues to be transmitted.

[0031] In one possible implementation method, there are multiple non-low-latency service frames between two adjacent specified time periods within the transmission activation window, the first non-low-latency service frame among the multiple non-low-latency service frames contains a complete leading symbol, and the other non-low-latency service frames among the multiple non-low-latency service frames contain a cropped leading symbol.

[0032] In a second aspect, embodiments of the present application provide a communication method that can be performed by a network device or a module (such as a chip) within a Wi-Fi system. The method includes: sending a communication frame to at least one terminal device within a transmission opportunity window, the communication frame including indication information and downlink low-latency service data, the indication information being used to indicate a transmission resource for the downlink low-latency service data, and the transmission opportunity window being used to transmit non-low-latency service frames.

[0033] In a third aspect, embodiments of the present application provide a communication method that can be performed by a terminal device or a module (e.g., a chip) in a WiFi system. The method includes: receiving a first frame, the first frame indicating a first uplink transmission resource; and transmitting a first uplink low-latency service frame or a low-latency service report frame on the first uplink transmission resource within a transmission opportunity window, where the transmission opportunity window can be used to transmit non-low-latency service frames.

[0034] In one possible implementation method, the receiving of the first frame includes: receiving the first frame in a first time period within the transmission opportunity window; the sending of the first uplink low-latency service frame on the first uplink transmission resource within the transmission opportunity window includes: sending the first uplink low-latency service frame on the first uplink transmission resource in the first time period, and the data volume of the first uplink low-latency service frame is less than a first threshold.

[0035] In one possible implementation method, the low-latency service report frame is used to indicate the data volume of the uplink low-latency service to be transmitted; the method also includes: receiving a second frame in a second time period within the transmission opportunity window, the second frame being used to indicate a second uplink transmission resource, and the second uplink transmission resource being determined based on the low-latency service report frame; sending a second uplink low-latency service frame in the second time period and on the second uplink transmission resource, and the second uplink low-latency service frame being used to transmit the uplink low-latency service to be transmitted.

[0036] In one possible implementation method, the method further includes: receiving an aggregate frame within the transmission opportunity window, the aggregate frame including a confirmation frame for the first uplink low-latency service frame and a confirmation frame for the second uplink low-latency service frame.

[0037] In one possible implementation method, the method also includes: receiving a downlink low-latency service frame within a third time period within the transmission opportunity window, the downlink low-latency service frame including downlink low-latency service data and a transmission resource indication, and the transmission resource indication is used to indicate the transmission resources of the downlink low-latency service data.

[0038] In a possible implementation method, the method further includes: receiving a third frame within the transmission opportunity window, the third frame carrying a preemptive transmission indication, and the preemptive transmission indication is used to indicate whether low-latency services are allowed to preempt transmission after the transmission of the third frame is completed.

[0039] In a possible implementation method, there is a time period for sending uplink low-latency service frames or low-latency service report frames after every fixed number of non-low-latency service frames in the transmission opportunity window.

[0040] In a possible implementation method, the transmission opportunity window does not include other frames for indicating uplink transmission resources except the first frame.

[0041] In a possible implementation method, the receiving the first frame includes: receiving the first frame before the transmission opportunity window.

[0042] In a possible implementation method, the method further includes: receiving a beacon frame, where the beacon frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0043] In one possible implementation method, the method also includes: receiving a management frame, which is used to negotiate whether low-latency service preemptive transmission is supported within the transmission opportunity window; and sending a response frame, which indicates that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0044] In a possible implementation method, the method further includes: sending a management frame, where the management frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0045] In one possible implementation method, the terminal device is the initiator of the transmission opportunity window, and the low-latency service frames received or sent by the terminal device can be preempted for transmission between any two non-low-latency service frames, and other low-latency service frames can only be preempted for transmission within a specified time period within the transmission opportunity window.

[0046] In one possible implementation method, the terminal device is the initiator of the transmission opportunity window, and the non-low-latency service frame sent by the terminal device can be interrupted to preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-low-latency service frame continues to be transmitted.

[0047] In one possible implementation method, there are multiple non-low-latency service frames between two adjacent specified time periods within the transmission activation window, the first non-low-latency service frame among the multiple non-low-latency service frames contains a complete leading symbol, and the other non-low-latency service frames among the multiple non-low-latency service frames contain a cropped leading symbol.

[0048] For the beneficial effects of the implementation method of the terminal device, reference may be made to the beneficial effects of the implementation method of the network device.

[0049] In a fourth aspect, an embodiment of the present application provides a communication device, which may be a network device or a module (such as a chip) in a network device. The device has the function of implementing any of the implementation methods of the first to second aspects above. The function can be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above functions.

[0050] In a fifth aspect, an embodiment of the present application provides a communication device, which can be a terminal device or a module (such as a chip) in the terminal device. The device has the function of implementing any implementation method of the third aspect above. The function can be implemented by hardware or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions.

[0051] In a sixth aspect, an embodiment of the present application provides a communication device, comprising a unit or means for executing each step of any implementation method in the above-mentioned first to third aspects.

[0052] In a seventh aspect, an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods described in the first to third aspects above. The processor comprises one or more.

[0053] Optionally, the communication device may further include a memory for storing computer instructions, the memory being coupled to a processor, and the processor executing the computer instructions stored in the memory so that the device executes any implementation method in the above-mentioned first to third aspects.

[0054] In an eighth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run by a communication device, any implementation method in the above-mentioned first to third aspects is executed.

[0055] In the ninth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when run on a communication device, enables any implementation method in the above-mentioned first to third aspects to be executed.

[0056] In the tenth aspect, an embodiment of the present application further provides a chip system, comprising: a processor for executing any implementation method in the above-mentioned first to third aspects.

[0057] In the eleventh aspect, an embodiment of the present application also provides a communication system, including a network device for executing any implementation method of the first aspect and a terminal device for executing any implementation method of the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] FIG1 is a schematic diagram of the architecture of a communication system used in an embodiment of the present application;

[0059] FIG2 is an example diagram of a method for preemptive transmission of a low-latency service in a single-user scenario provided by an embodiment of the present application;

[0060] FIG3 is a schematic diagram of a communication method provided in an embodiment of the present application;

[0061] Figure 4(a) is a schematic diagram of the equal-interval preemptive transmission scheme;

[0062] FIG4( b ) is another schematic diagram of the equal-interval preemptive transmission scheme;

[0063] FIG5 is a schematic diagram of a PSP interval for flexibly adjusting an equal-interval preemptive transmission scheme;

[0064] FIG6 is a schematic diagram showing how to reduce the number of Trigger frames in an equal-interval preemptive transmission scheme;

[0065] FIG7 is a schematic diagram of an unequal interval preemptive transmission scheme;

[0066] FIG8 is a schematic diagram of another unequal interval preemptive transmission scheme;

[0067] FIG9 is a schematic diagram of the RPD scheme;

[0068] FIG10 is another schematic diagram of the RPD scheme;

[0069] FIG11 is another schematic diagram of the RPD scheme;

[0070] FIG12 is a diagram illustrating an example of allocation of uplink transmission resources within a PSP;

[0071] FIG13 is a schematic diagram of a pattern-based RU allocation scheme;

[0072] FIG14 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0073] FIG15 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0074] Figure 1 is a schematic diagram of the architecture of a communication system used in an embodiment of the present application. The communication system 1000 shown in Figure 1 includes a wireless access network 100 and a core network 200. Optionally, the communication system 1000 also includes the Internet 300. The wireless access network 100 may include at least one network device (such as 110a and 110b in Figure 1) and may also include at least one terminal device (such as 120a-120j in Figure 1). The terminal device is wirelessly connected to the network device, and the network device is wirelessly or wiredly connected to the core network. The core network device and the network device may be independent, distinct physical devices, or the core network device's functions and the network device's logical functions may be integrated into the same physical device, or a single physical device may integrate some of the core network device's functions and some of the network device's functions. Terminal devices and network devices may be interconnected via wired or wireless connections. Figure 1 is merely a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1.

[0075] A network device is an access device that a terminal device uses to access a communication system via a wired or wireless method. A network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a WiFi system; it may also be a module or unit that performs some of the functions of a base station, for example, a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). A network device may be a macro base station (such as 110a in FIG1 ), a micro base station or an indoor station (such as 110b in FIG1 ), a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0076] A terminal device is a device with wireless transceiver capabilities that can send signals to or receive signals from a network device. Terminal devices include, but are not limited to, terminal devices, terminals, user equipment (UE), mobile stations, mobile terminals, stations (STA), etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal device can specifically be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal device.

[0077] Network devices and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of network devices and terminal devices.

[0078] The roles of network devices and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile network device. To terminal devices 120j accessing the wireless access network 100 via 120i, terminal device 120i is a network device. However, to network device 110a, 120i is a terminal device, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via an interface protocol between network devices. In this case, 120i is also a network device relative to 110a. Therefore, both network devices and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with network device functionality, while 120a-120j in Figure 1 can be referred to as communication devices with terminal device functionality.

[0079] Network devices and terminal devices, network devices and network devices, and terminal devices and terminal devices can communicate through authorized spectrum, unauthorized spectrum, or both; can communicate through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz simultaneously. The embodiments of the present application do not limit the spectrum resources used for wireless communications.

[0080] In the embodiments of the present application, the functions of the network device may also be performed by a module (such as a chip) in the network device, or by a control subsystem that includes the network device functions. The control subsystem that includes the network device functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may also be performed by a module (such as a chip or a modem) in the terminal device, or by a device that includes the terminal device functions.

[0081] In this application, a network device sends downlink signals or downlink information to a terminal device, and the downlink information is carried on a downlink channel. A terminal device sends uplink signals or uplink information to a network device, and the uplink information is carried on an uplink channel. To communicate with a network device, a terminal device needs to establish a wireless connection with a cell controlled by the network device. The cell with which a terminal device has established a wireless connection is called the serving cell of the terminal device.

[0082] For ease of explanation, this application will subsequently use STA and AP as examples of terminal devices and network devices, respectively. That is, the STA and AP that appear subsequently can be replaced by terminal devices and network devices, respectively.

[0083] In the embodiment of the present application, a non-AP device used to transmit low latency traffic (LLT) is called an LLT STA, and a non-AP device used to transmit non-low latency traffic is called a non-LLT STA.

[0084] When a communication frame sent by an LLT STA to an AP carries data for an uplink low-latency service, the communication frame is also referred to as an uplink low-latency service frame. When a communication frame sent by an AP to an LLT STA carries data for a downlink low-latency service, the communication frame is also referred to as a downlink low-latency service frame. For example, when a communication frame is a physical layer protocol data unit (PPDU), the communication frame is also referred to as an LLT PPDU, specifically including an uplink (UL) LLT PPDU and a downlink (DL) LLT PPDU.

[0085] Figure 2 is an example diagram of a preemptive transmission method for low-latency services in a single-user scenario provided by an embodiment of the present application. STA1 only transmits non-low-latency services (non-LLT), and STA2 transmits low-latency services (LLT), that is, STA1 is a non-LLT STA and STA2 is a LLT STA. Within the transmission opportunity (TXOP) window (hereinafter referred to as TXOP), non-LLT data is transmitted between the AP and STA1. Within this TXOP, even if there is high-priority LLT data to be sent, the AP cannot transmit the LLT to STA2 in time and must wait for the end of STA1's non-LLT PPDU transmission. Therefore, if STA1's non-LLT PPDU lasts too long, the LLT transmission delay will increase significantly. In order to reduce the LLT transmission delay, the AP divides STA1's long non-LLT PPDU into multiple short non-LLT PPDUs, namely the short PPDU in Figure 2, and introduces a new interframe space xIFS, allowing STA2 to preempt the channel to transmit LLT within the xIFS of the short non-LLT PPDU. As shown in Figure 2, after the AP buffers the LLT data, it suspends transmission of short non-LLT PPDUs to STA1. After xIFS, it transmits the LLT PPDU to STA2. In addition, to reduce the overhead of the confirmation frame, STA1 only responds with an confirmation frame after receiving all the short non-LLT PPDUs, resulting in a significant increase in the confirmation frame response delay. In addition, after receiving an LLT PPDU, STA2 also responds with an confirmation frame. The confirmation frame can be a block acknowledgment (BA) frame or an ACK frame. In Figure 2, SIFS stands for short interframe space, RTS stands for request to send, and CTS stands for clear to send.

[0086] The above solution has the following problems:

[0087] First, the non-LLT STA (such as STA1) waits too long for the reply confirmation frame, resulting in the inability to request the retransmission of the erroneous data in time;

[0088] Second, the transmission duration of short PPDUs and LLT PPDUs is variable, and LLT is allowed to preempt the channel between multiple short PPDUs, resulting in uncontrollable response time for confirmation frames.

[0089] Third, only the case where a single user has a low-latency service is considered, and the scenario where multiple users compete to transmit low-latency services is not considered.

[0090] Therefore, how to design a suitable low-latency service preemptive transmission method to achieve efficient transmission of multiple low-latency services remains to be solved.

[0091] Figure 3 is a schematic diagram of a communication method provided in an embodiment of the present application. This method is performed by a terminal device (e.g., an LLT STA or a non-LLT STA) or a module (e.g., a chip) for a terminal device, and a network device (e.g., an AP) or a module (e.g., a chip) for a network device. For ease of explanation, the following description uses an AP, an LLT STA, and a non-LLT STA as an example to illustrate this method.

[0092] The method comprises the following steps:

[0093] Step 301: The AP sends a first frame, and correspondingly, at least one LLT STA receives the first frame.

[0094] The first frame is used to indicate a first uplink transmission resource. Specifically, the first uplink transmission resource may include a frequency domain resource, or include a time domain and frequency domain resource.

[0095] The first uplink transmission resources may include transmission resources (such as one or more resource units (RUs)) exclusively used by the at least one LLT STA, and / or shared resources. For example, the first uplink transmission resources include exclusive resources of LLT STA1, exclusive resources of LLT STA2, and shared resources, wherein the exclusive resources of LLT STA1 are exclusively used by LLT STA1, and the exclusive resources of LLT STA2 are exclusively used by LLT STA2. The shared resources can be competed for by LLT STA1, LLT STA2, and other LLT STAs.

[0096] In step 302, the at least one LLT STA sends a first uplink low-latency service frame or a low-latency service report frame to the AP on a first uplink transmission resource within a transmission opportunity (TXOP) window. Accordingly, the AP receives the first uplink low-latency service frame or the low-latency service report frame.

[0097] The transmission opportunity window can be used to transmit non-LLT service frames (non-LLT STAs). The low-latency service report frame is used to indicate the data volume of the uplink low-latency service to be transmitted. Optionally, the low-latency service report frame also indicates the service type and / or service priority of the uplink low-latency service to be transmitted. Exemplarily, the low-latency service report frame includes at least one of a bandwidth query report (BQR) frame, a buffer status report (BSR) frame, and a null data packet (NDP) feedback report (NFR) frame.

[0098] Taking the example that the first uplink transmission resources include LLT STA1's exclusive resources, LLT STA2's exclusive resources and shared resources, LLT STA1 can send a first uplink low-latency service frame or a low-latency service report frame to the AP on LLT STA1's exclusive resources and / or shared resources. The first uplink low-latency service frame sent by LLT STA1 includes LLT STA1's uplink low-latency service or uplink low-latency service data. The low-latency service report frame sent by LLT STA1 is used to indicate the amount of data of LLT STA1's uplink low-latency service to be transmitted. LLT STA2 can send a first uplink low-latency service frame or a low-latency service report frame to the AP on LLT STA2's exclusive resources and / or shared resources. The first uplink low-latency service frame sent by LLT STA2 includes LLT STA2's uplink low-latency service or uplink low-latency service data. The low-latency service report frame sent by LLT STA2 is used to indicate the amount of uplink low-latency service data to be transmitted by LLT STA2.

[0099] The above solution allocates uplink transmission resources to LLT STAs within the transmission opportunity window that can be used to transmit non-low-latency service frames. The resources are used to transmit uplink low-latency service frames or low-latency service report frames, thereby preempting the transmission of low-latency services, ensuring the timely delivery of low-latency services, and helping to improve the user experience.

[0100] In one possible implementation method, the above-mentioned step 301 is specifically as follows: the AP sends the first frame in the first time period within the TXOP. Correspondingly, the above-mentioned step 302 is specifically as follows: the AP receives the first uplink low-latency service frame from at least one LLT STA in the first time period and on the first uplink transmission resource within the TXOP, and the data volume of the first uplink low-latency service frame is less than the first threshold. This can be understood as at least one LLT STA sending small data of low-latency service to the AP in the first time period and on the first uplink transmission resource. Optionally, after receiving the first uplink low-latency service frame, the AP sends an acknowledgment frame (such as a BA frame) for the first uplink low-latency service frame to the at least one LLT STA.

[0101] In one possible implementation method, if in step 302 above, at least one LLT STA sends a low-latency service report frame to the AP on a first uplink transmission resource within a TXOP, then after receiving the low-latency service report frame, the AP determines a second uplink transmission resource based on the low-latency service report frame and sends a second frame to the at least one LLT STA in a second time period within the TXOP, where the second frame is used to indicate the second uplink transmission resource. Then, the at least one LLT STA sends a second uplink low-latency service frame to the AP in a second time period within the TXOP and on the second uplink transmission resource, where the second uplink low-latency service frame is used to transmit the uplink low-latency service to be transmitted. Optionally, the data volume of the second uplink low-latency service frame is greater than or equal to a first threshold. For example, when the LLT STA has large data of low-latency services (i.e., the data volume of the low-latency services is greater than or equal to the first threshold) that needs to be sent to the AP, a low-latency service report frame can be sent to the AP first, and then the AP allocates sufficient uplink transmission resources, i.e., the second uplink transmission resources, to the LLT STA based on the low-latency service report frame, and then the LLT STA sends the large data of low-latency services on the second uplink transmission resources. In this way, the correct transmission of low-latency service data can be guaranteed. Optionally, after receiving the second uplink low-latency service frame, the AP sends a confirmation frame (such as a BA frame) for the second uplink low-latency service frame to the at least one LLT STA. In this implementation method, the first time period can be a time period before the second time period, and there can be a time interval between the first time period and the second time period, or they can be continuous. Alternatively, the first time period and the second time period are the same time period.

[0102] In one possible implementation, when an AP sends an acknowledgment frame for a received uplink low-latency service frame to a terminal device, it may aggregate multiple acknowledgment frames into a single frame (referred to as an aggregate frame) for transmission. For example, within a transmission opportunity window, the AP sends an aggregate frame to at least one terminal device, where the aggregate frame includes an acknowledgment frame for a first uplink low-latency service frame and an acknowledgment frame for a second uplink low-latency service frame.

[0103] In one possible implementation, the AP may further send a downlink low-latency service frame to at least one LLT STA within a third time period within the TXOP. The downlink low-latency service frame includes downlink low-latency service data and a transmission resource indicator, where the transmission resource indicator is used to indicate the transmission resource for the downlink low-latency service data. The third time period may be the same as the first time period or the second time period, or different from both the first time period and the second time period.

[0104] In one possible implementation, a third frame is sent within the transmission opportunity window. This third frame can be a data frame (e.g., an uplink / downlink low-latency service frame, an uplink / downlink non-low-latency service frame) or a control frame. This third frame carries a preemption transmission indicator, which indicates whether preemption transmission of low-latency services is allowed after the third frame is transmitted. Based on the preemption transmission indicator, the LLT STA can determine whether to preempt transmission of uplink low-latency service data after the third frame.

[0105] In one possible implementation, a time period for sending uplink low-latency service frames or low-latency service report frames exists after every fixed number of non-low-latency service frames within a TXOP. This means that after the AP sends a fixed number of non-low-latency service frames, a preemptive transmission window exists. During this preemptive transmission window, the AP can send downlink low-latency service frames to an LLT STA, or an LLT STA can send uplink low-latency service frames to the AP.

[0106] In one possible implementation, within a TXOP, only the first frame used for the first uplink transmission resource exists, and no other frames other than the first frame are used to indicate the uplink transmission resource. This means that within a TXOP, the uplink transmission resource is indicated only once to the LLT STA, and the LLT STA subsequently uses this uplink transmission resource to send uplink low-latency service data. This reduces signaling overhead.

[0107] In one possible implementation method, the first frame sent in the above step 301 can be sent before the TXOP, that is, the uplink transmission resource is indicated to the LLT STA once before the TXOP, and the LLT STA subsequently uses the uplink transmission resource to send uplink low-latency service data. There is no need to indicate the uplink transmission resource to the LLT STA within the TXOP, which can save signaling overhead.

[0108] In one possible implementation, before step 301, the AP sends a beacon frame to at least one LLT STA. This beacon frame indicates support for low-latency service preemptive transmission within the TXOP. Specifically, if the AP decides to support low-latency service preemptive transmission within a particular TXOP, it notifies the LLT STA via a beacon frame.

[0109] In another implementation method, before the above step 301, the AP sends a management frame to at least one LLT STA, which is used to negotiate whether low-latency service preemptive transmission is supported within the TXOP. If the at least one LLT STA determines that low-latency service preemptive transmission is supported within the TXOP, a response frame is sent to the AP, which indicates that low-latency service preemptive transmission is supported within the TXOP.

[0110] In another possible implementation, before step 301, the LLT STA sends a management frame to the AP, indicating support for low-latency service preemptive transmission within the TXOP. Specifically, if the LLT STA decides to support low-latency service preemptive transmission within a particular TXOP, it notifies the AP via a management frame.

[0111] In one possible implementation method, if the AP is the initiator of the transmission opportunity window, the downlink low-latency service frame sent by the AP can be preempted for transmission between any two downlink non-low-latency service frames, and the uplink low-latency service frame received by the AP is preempted for transmission only in a specified time period within the transmission opportunity window. Optionally, the AP sends a fourth frame within the specified time period, and the fourth frame is used to request at least one terminal device to report a low-latency service report. Optionally, the fourth frame is also used to indicate the next specified time period. The time period here is also referred to as a preemption service period (PSP), and the PSP provides an uplink and / or downlink preemption transmission time window for the LLT STA to ensure the latency requirements of the low-latency service.

[0112] In one possible implementation method, if the AP is the initiator of the transmission opportunity window, the non-low-latency service frame sent by the AP can be interrupted to preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-low-latency service frame continues to be transmitted.

[0113] In one possible implementation method, if a STA (such as an LLT STA or a non-LLT STA) is the initiator of the transmission opportunity window, the low-latency service frames received or sent by the LLT STA can be preempted for transmission between any two non-low-latency service frames, and other low-latency service frames can only be preempted for transmission within a specified time period within the transmission opportunity window.

[0114] In one possible implementation method, if a STA (such as an LLT STA or a non-LLT STA) is the initiator of the transmission opportunity window, the non-low-latency service frame sent by the non-LLT STA can be interrupted so that the LLT STA can preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-LLT STA continues to transmit the non-low-latency service frame.

[0115] In one possible implementation, multiple non-low-latency service frames exist between two adjacent designated time periods within the transmission activation window. The first of these frames contains a complete preamble symbol, while the remaining frames contain clipped preamble symbols. This reduces signaling overhead.

[0116] In the embodiment of the present application, preemptive transmission may or may not be supported within a TXOP, and it is necessary to determine whether the TXOP supports preemptive transmission based on dynamic indication. The following introduces four different implementation methods for the AP to notify whether the TXOP supports preemptive transmission.

[0117] Implementation method 1: The AP sends a beacon frame, and a new preemptive transmission enable / support indication is added to the Beacon frame, such as a 1-bit PreemptionSupport subfield, which is used to indicate whether the TXOP enables / supports preemptive transmission of low-latency services. For example, if PreemptionSupport is configured to 1, it indicates that all TXOPs in the current basic service set (BSS) or TXOPs initiated by the AP support preemptive transmission. Alternatively, if PreemptionSupport is configured to 1, it indicates that the current AP supports preemptive transmission of low-latency services. If the preemptive transmission function needs to be enabled, it needs to be indicated through additional signaling.

[0118] Implementation method 2: Within a TXOP, the TXOP initiator and the receiver exchange management frames to negotiate support / rejection of low-latency service preemptive transmission within the current TXOP.

[0119] Implementation method three: Within a TXOP, the TXOP initiator sends a control frame or management frame, such as an RTS frame, carrying a preemptive transmission indication to notify the current TXOP of support / rejection of preemptive transmission of low-latency services, and can also be used to notify preemptive transmission parameters.

[0120] Implementation Method 4: Outside a TXOP, the AP sends a management frame to notify the user of preemptive transmission. Alternatively, within a TXOP, the TXOP initiator sends a management frame to notify the user of support or rejection of preemptive transmission for the current TXOP. If preemptive transmission is enabled, all TXOPs within the current BSS or TXOPs initiated by the AP support preemptive transmission until the AP notifies the user of the disabled feature. This management frame can also be used to notify the user of preemptive transmission parameters, such as the PSP parameters. If the management frame is individually or group-addressed, the receiver must respond with a response frame. If the management frame is a broadcast frame, the receiver does not need to respond with a response frame.

[0121] The method embodiment of Figure 3 is described below with reference to the accompanying drawings. In the examples of Figures 4(a), 4(b), and 5 to 13 below, the LLT PPDU sent by the AP is a specific example of a downlink low-latency service frame, the LLT PPDU sent by the LLT STA is a specific example of an uplink low-latency service frame, the non-LLT PPDU sent by the AP is a specific example of a downlink non-low-latency service frame, and the BSR frame sent by the LLT STA is a specific example of a low-latency service report frame. Among them, STA1 is a non-LLT STA, and STA2 to STA4 are all LLT STAs. Within the TXOP, the long non-LLT PPDU sent by the AP to STA1 is divided into multiple short non-LLT PPDUs for transmission, with an inter-frame interval of SIFS. In the following examples, a preemptive service period (PSP) is divided to provide the LLT STA with an uplink and / or downlink preemptive transmission time window to ensure the latency requirements of the low-latency service. Among them, the PSP can be the first time period, the second time period or the third time period in the embodiment of Figure 3, or a combination of any two or three time periods among the first time period, the second time period or the third time period. Within the PSP, the LLT STA can send a low-latency service report frame (such as a BSR frame), an uplink low-latency service frame (such as an LLT PPDU) and an acknowledgment frame (such as a BA frame) for the received downlink low-latency service frame, and the AP can send a downlink low-latency service frame (such as an LLT PPDU) and an acknowledgment frame for the received uplink low-latency service frame. And, within the PSP, the non-LLT STA can send an acknowledgment frame for the received downlink non-low-latency service frame (such as a non-LLT PPDU) to the AP. The following embodiments support multi-user preemptive transmission and provide a flexible acknowledgment frame reporting mechanism for non-LLT PPDU.

[0122] The following description is divided into four parts. The first part includes the equal-interval preemption transmission scheme, involving Figures 4(a), 4(b), 5, and 6; the second part includes the unequal-interval preemption transmission scheme, involving Figures 7 and 8; the third part includes the restricted preemption delivery (RPD) scheme, involving Figures 9 to 11; and the fourth part includes the resource allocation scheme within the PSP, involving Figures 12 and 13. It should be noted that the following four parts can be implemented independently or in combination.

[0123] Part 1: Equal-interval transmission scheme

[0124] Figure 4(a) illustrates a preemptive transmission scheme with equal intervals. In this example, a specified number of non-LLT PPDUs are inserted into a PSP at each interval. The PSP interval can be flexibly configured by the user (e.g., the number of non-LLT PPDUs in the interval), or the PSP interval can be specified by the protocol (i.e., statically configured).

[0125] Within each PSP, the AP sends a Trigger frame to configure uplink transmission resources and related parameters for STAs (including LLT STAs and / or non-LLT STAs). Within each PSP, a non-LLT STA (such as STA1) can report a BA frame for the received non-LLT PPDU, thereby resolving the issue of excessive acknowledgment frame response delay in existing mechanisms.

[0126] Within each PSP, the AP allocates designated uplink transmission resources (such as one or more RUs) to the LLT STA. The LLT STA reports a BSR frame according to the designated uplink transmission resources, or transmits a small amount of UL LLT data (i.e., uplink LLT PPDU). Specifically, when the amount of UL LLT data is small, the LLT STA can use designated uplink transmission resources or shared uplink transmission resources to send uplink LLT PPDUs without reporting BSR frames. In this case, the AP does not need to transmit additional Trigger frames to schedule the LLT STA to send uplink LLT PPDUs. For example, after LLT STA2 receives the Trigger frame in the second PSP in Figure 4(a), it sends the LLT PPDU based on the uplink transmission resources adjusted by the Trigger.

[0127] When the amount of UL LLT data is large (that is, the UL LLT cannot be fully transmitted within the uplink transmission frame of the length specified by the Trigger frame), the LLT STA uses the specified uplink transmission resources to report the BSR frame. After receiving the BSR frame, the AP uniformly allocates uplink transmission resources based on the UL LLT cached by different LLT STAs. Within the PSP, after the AP receives the BSR frame, it transmits a Trigger frame at an interval of SIFS to notify the STA of the uplink transmission resources and related parameters. The LLT STA receives the Trigger frame and sends an LLT PPDU carrying UL LLT data according to the uplink transmission resources allocated by the AP. After receiving the uplink LLT PPDU, the AP replies with a BA frame at an interval of SIFS. If the AP has cached DL LLT data, the AP can send an LLT PPDU carrying DL LLT data at an interval of SIFS after transmitting the BA frame. For example, in the second PSP in Figure 4(a), LLT STA3 and LLT STA4 first report a BSR. The AP then sends a Trigger frame to allocate uplink transmission resources. LLT STA3 and LLT STA4 each send an LLT PPDU on the allocated uplink transmission resources. The AP then sends a BA frame to LLT STA3 and LLT STA4 within the PSP. Because the AP has already buffered the DL LLT data for LLT STA3 and LLT STA 4, after sending the BA frame, the AP can then send an LLT PPDU carrying the DL LLT data to LLT STA3 and LLT STA4. LLT STA3 and LLT STA4 then send BA frames to the AP.

[0128] Within a PSP, if the AP allocates uplink transmission resources for a non-LLT STA, then after receiving the Trigger frame, the non-LLT STA can send a BA frame to the AP in response to the previously received non-LLT PPDU. For example, in Figure 4(a), STA1 in the second PSP sends BA frames for non-LLT PPDU1 and non-LLT PPDU2 to the AP based on the uplink transmission resources allocated by the Trigger frame.

[0129] To further reduce air interface overhead, the AP is allowed to send aggregated frames. For example, as shown in Figure 4(b), orthogonal frequency division multiple access (OFDMA) can be used to simultaneously transmit the Trigger frame and the BA frame, or to simultaneously transmit the non-LLT PPDU and the BA frame, or to simultaneously transmit the LLT PPDU and the BA frame.

[0130] In one implementation method, the embodiment of the present application can reasonably configure the PSP interval according to the LLT characteristics of different application scenarios, that is, configure the time interval between two adjacent PSPs to reduce signaling overhead and improve media utilization. Figure 5 is a schematic diagram of flexibly adjusting the PSP interval of the equal-interval preemptive transmission scheme. In this example, the PSP interval is 3, that is, 1 PSP is inserted for every 3 non-LLT PPDUs transmitted. Compared with the case where the PSP interval is 1 in Figure 4 (a) or Figure 4 (b), increasing the PSP interval can effectively reduce signaling overhead. Of course, the PSP interval of 3 is only used as an example for illustration here, and it can be flexibly configured according to needs in actual applications.

[0131] In one implementation method, when the AP notifies the STA (including LLT STA and non-LLT STA) of the uplink transmission resources using any of the following methods 1) to 5), if the STA's uplink transmission resources and related parameters remain unchanged, the AP does not need to send a Trigger frame within the PSP, thereby reducing the sending of Trigger frames and saving signaling overhead.

[0132] Method 1): Outside the TXOP, the AP and STA exchange management frames to specify the STA's uplink transmission resources and related parameters.

[0133] Method 2): At the start of the TXOP, the AP sends a Trigger frame to specify the STA's uplink transmission resources and related parameters.

[0134] Method 3): In the first PSP, the AP sends a Trigger frame to specify the STA's uplink transmission resources and related parameters.

[0135] Within any PSP, if the AP does not send a Trigger frame, the STA uses the uplink transmission resources configured in the most recently received management frame or Trigger frame to send uplink data. When the uplink transmission resources of a STA within a PSP change, the AP sends a Trigger frame within the PSP to update the STA's uplink transmission resources and related parameters.

[0136] Figure 6 illustrates how to reduce the number of trigger frames in a preemptive transmission scheme with equal intervals. Within a PSP, if the AP sends a trigger frame, the STA, after receiving the trigger frame, transmits uplink data according to the specified uplink transmission resources and related parameters after a SIFS interval. Within a PSP, if the AP does not send a trigger frame, the STA uses any of the following methods, 1 through 5, to determine the start time of the PSP, thereby aligning uplink transmissions:

[0137] Method 1: The signaling (SIG) field in the non-LLT PPDU sent by the AP carries an increment / decrement count indication. The STA detects the non-LLT PPDU. When it detects that the increment / decrement count indication of any non-LLT PPDU reaches the specified threshold, the non-LLT PPDU transmission ends and the interval SIFS is the PSP start time. Specifically, the next PSP start time = non-LLT PPDU transmission end time + interframe gap.

[0138] Taking countdown as an example, the initial value of the counter is set to N-1, and the threshold is specified to 0, where N is the number of non-LLT PPDUs between two adjacent PSPs. Referring to Figure 6, N = 2, when the LLT STA detects that the count indication (count) in the non-LLT PPDU = 0, it indicates that the non-LLT PPDU is the last non-LLT PPDU between the two adjacent PSPs. Therefore, it can be determined that the start time of the next PSP is equal to the sum of the non-LLT PPDU transmission end time and the interframe interval.

[0139] Method 2: The SIG field in the non-LLT PPDU sent by the AP carries a 1-bit indicator bit, such as the PreemptionIndication subfield. Based on the 0 / 1 state of the indicator bit, it is determined whether the current non-LLT PPDU transmission end time + interframe gap is the start time of the PSP.

[0140] For example, when the PreemptionIndication subfield in the non-LLT PPDU is bit 1, it indicates that the non-LLT PPDU is the last non-LLT PPDU between two adjacent PSPs. Therefore, it can be determined that the start time of the next PSP is equal to the sum of the end time of the non-LLT PPDU transmission and the inter-frame interval.

[0141] Method 3: From the start of the TXOP or the end of any PSP where a trigger frame is detected, the STA detects non-LLT PPDUs and counts up / down. When the count value reaches the specified threshold, the non-LLT PPDU transmission ends and the interframe gap elapses, which is the start time of the PSP.

[0142] In mode 3, the STA detects whether the non-LLT PPDU is the last non-LLT PPDU between two adjacent PSPs. If it is determined that the non-LLT PPDU is the last non-LLT PPDU between two adjacent PSPs, the start time of the next PSP is determined to be equal to the sum of the non-LLT PPDU transmission end time and the inter-frame interval.

[0143] In mode 3, the LLT STA uses the following method a or method b to avoid counting LLT PPDUs, thereby avoiding incorrect calculation of the number of non-LLT PPDUs between two adjacent PSPs.

[0144] Method a: Add a 1-bit indicator in the SIG field of the PPDU to distinguish non-LLT PPDU from LLT PPDU.

[0145] In method b, the LLT STA ignores the PPDU count within the PSP because all PPDUs within the PSP are LLT PPDUs.

[0146] Method 4: The AP sends a control frame or management frame to notify the periodic PSP parameters, that is, the duration between PSPs remains unchanged.

[0147] Method 5: Within a PSP, the AP sends a Trigger frame to notify the next PSP parameters, which includes the next PSP start time or the interval between the current PSP start time and the next PSP start time. Within a TXOP, the first PSP parameters can be notified via a control frame at the start of the TXOP or by a management frame sent by the AP before the first PSP in the TXOP.

[0148] In one implementation, if the AP does not transmit a Trigger frame within the PSP, to avoid the impact of hidden nodes, at the start of the PSP, STAs (including LLT STAs and non-LLT STAs) do not detect whether the channel is busy or idle and directly send uplink transmission frames. If the AP may transmit Trigger frames within some PSPs, a method needs to be designed to prevent the STA's uplink transmission frame from colliding with the Trigger frame sent by the AP at the start of the PSP. A possible solution is to have the STA send uplink data if it does not detect a Trigger frame within a specified interval (such as SIFS) after the start of the PSP; if the STA detects a Trigger frame, it sends uplink data based on the uplink transmission resources configured in the Trigger frame.

[0149] Part 2: Unequal Interval Preemptive Transmission Scheme

[0150] In one implementation, to save signaling overhead, the number of PSPs can be reduced. This means that PSPs appear aperiodically. Specifically, the number of non-LLT PPDUs between adjacent PSPs is not fixed, meaning that PSPs appear at unequal intervals. In an unequal-interval preemptive transmission scheme, the PSP interval is no longer specified. LLT STAs initiate PSPs, meaning that any non-LLT PPDU can be followed by a PSP. Figure 7 illustrates the unequal-interval preemptive transmission scheme.

[0151] If an LLT STA has buffered UL LLT data, after completing transmission of a non-LLT PPDU, a PSP is inserted after a specified interval (such as slot 1) to report a BSR frame or preemptively transmit UL LLT data. The interframe interval between the non-LLT PPDU and the PSP, as well as within the PSP, is slot 1, typically set to SIFS. The transmission rules within the PSP are similar to those of the equal-interval scheme. When the amount of UL LLT data is small, the LLT STA uses the allocated uplink transmission resources to transmit UL LLT data, as shown in LLT STA3 in Figure 7. When the amount of UL LLT data is large, the LLT STA uses the allocated uplink transmission resources to report a BSR frame. After receiving the BSR frame, the AP transmits a Trigger frame after a SIFS interval to trigger the LLT STA to perform uplink preemptive transmission, as shown in LLT STA4 in Figure 7. Within the PSP, the AP is allowed to allocate a small amount of uplink transmission resources to non-LLT STAs for reporting BA frames.

[0152] If the AP has cached DL LLT data, after the non-LLT PPDU transmission is completed, after a specified interval (such as the specified interval is the modified interframe space (MIFS), and MIFS = slot1 + slot2), a PSP is inserted to preempt the transmission of DL LLT data. The values ​​of slot1 and slot2 can be flexibly configured, for example, MIFS is not less than the AP's transceiver switching time twice. After the AP transmits any non-LLT PPDU, it checks whether there is an uplink signal on the uplink transmission resource allocated to the LLT STA at an interval of slot1 (such as slot1 = SIFS). If there is an uplink signal, a PSP is inserted after the non-LLT PPDU, and the AP receives the uplink transmission data within the PSP. If there is no uplink signal and the AP has cached DL LLT, a PSP is inserted after the interval of slot2, and the DL LLT PPDU is transmitted to one or more LLT STAs within the PSP. If there is no uplink signal and the AP has not buffered the DL LLT, it will continue to transmit the non-LLT PPDU after slot 2. The LLT STA determines the PSP start time by detecting the non-LLT PPDU.

[0153] In one implementation method, the AP can add a preemptive transmission indication in PPDUs (including non-LLT PPDU and LLT PPDU), such as adding a 1-bit PreemptionIndication subfield in the SIG field to indicate whether low-latency services are allowed to preempt transmission after the current PPDU transmission is completed. As shown in Figure 8, it is another schematic diagram of the unequal interval preemptive transmission scheme. Among them, when the PreemptionIndication subfield is configured to 1, it means that low-latency services are allowed to preempt transmission after the current PPDU transmission is completed; when the PreemptionIndication subfield is configured to 0, it means that low-latency services are not allowed to preempt transmission after the current PPDU transmission is completed. When the LLT STA detects that the PreemptionIndication subfield of any PPDU is set to 1, it determines that the current PPDU ends and preemptive transmission is allowed within the specified interval. When the PreemptionIndication field value of a PPDU is 0, the interframe interval between the PPDU and the next frame is SIFS. When the PreemptionIndication field value of a PPDU is 1 and the PPDU is not preempted by a low-latency service after the PPDU ends, the interframe interval between the PPDU and the next frame is MIFS. When the PreemptionIndication field value of a PPDU is 1 and the PPDU is preempted by a low-latency service after the PPDU ends, the interframe interval between the PPDU and the next frame is slot 1. For the meaning of MIFS, slot 1, and SIFS, refer to the previous description.

[0154] If the AP does not transmit a trigger frame at the start of the PSP, the STA can use any of the following methods to determine the start of the PSP and align uplink transmissions:

[0155] Method 1: If the LLT STA has buffered UL LLT data, the LLT STA can seize the channel to transmit the UL LLT PPDU or BSR frame after the PPDU transmission is completed and at an interval of slot 1 (for example, SIFS).

[0156] Method 2: If the LLT STA does not cache the UL LLT data, the LLT STA can detect whether there is a Trigger frame (used to request the LLTSTA that reports the BSR frame at the start time of the PSP to transmit UL LLT data) or DL ​​LLT PPDU at intervals of slot 1 (for example, SIFS) after the PPDU transmission is completed.

[0157] Part III: RPD Transmission Scheme

[0158] The RPD solution is illustrated below with reference to FIG9 to FIG11 .

[0159] Figure 9 is a schematic diagram of the RPD scheme. In this example, the AP is the TXOP initiator. LLT PPDUs sent by the AP can preempt transmission between any two non-LLT PPDUs. Other LLT PPDUs preempt transmission only within the PSP. Within the PSP, the AP sends a Trigger frame requesting the LLT STA to report a low-latency service report frame, such as a BSR frame. The Trigger frame can also be used to notify the next PSP parameters. If it is a periodic PSP, the PSP parameters can be used, and there is no need to separately notify the next PSP parameters in the Trigger frame. Within the PSP, the AP can schedule STA1 to respond with a BA frame. For example, within the TXOP, the AP and STA1 exchange management frames to negotiate whether preemptive transmission is supported or rejected within the current TXOP. After negotiating that the current TXOP supports preemptive transmission for low-latency services, the AP sends a management frame to notify LLT STA2-LLT STA4 that the current TXOP supports preemptive transmission for low-latency services and informs them of the PSP parameters. This management frame can be a Trigger frame requesting a response or an Action frame that does not require a response. Optionally, the interframe interval in this example is SIFS to prevent other STAs from occupying the channel due to an excessively long interframe interval.

[0160] Figure 10 is another schematic diagram of the RPD scheme. In this example, STA is the TXOP initiator. If there is peer-to-peer (P2P) communication between STA1 and LLT STA2, the LLT PPDU sent by STA1 can preempt transmission between any two non-LLT PPDUs, and the remaining LLT PPDUs can only preempt transmission within the PSP. If the TXOP initiator (i.e. STA1) serves as the receiver of P2P communication, the LLT PPDU received by STA1 can preempt transmission between any two non-LLT PPDUs. If the LLT PPDU received by STA1 is allowed to preempt transmission within the TXOP, the inter-frame interval of the non-LLT PPDU is MIFS; otherwise, the inter-frame interval is SIFS. Within the PSP, the AP can send independently addressed BA frames, or the AP can reply to STA1 with a BA frame using OFDMA.

[0161] Figure 11 is another schematic diagram of the RPD scheme. In this example, the AP is the TXOP initiator and can interrupt the non-LLT PPDU transmission in advance. When there is no UL / DL LLT preemptive transmission, only one non-LLT PPDU is transmitted between PSPs, effectively reducing the air interface overhead introduced by the preamble symbol, inter-frame spacing, etc. of the non-LLT PPDU. The non-LLT PPDU duration is determined according to the PSP interval. When the TXOP initiator buffers the LLT data to be transmitted, the TXOP initiator interrupts the current non-LLT PPDU transmission, and preempts the transmission of the LLT PPDU after a SIFS interval. After the LLT PPDU transmission is completed, the TXOP initiator continues to transmit the non-LLT PPDU after a SIFS interval, and determines the duration of the non-LLT PPDU within the remaining time until the next PSP start time. Note that the non-LLT PPDU transmission should end before the PSP start time. LLT data sent by non-TXOP initiators is only allowed to be preempted within the PSP. The interframe interval is SIFS to prevent other STAs from occupying the channel due to a long interframe interval. In addition, to reduce the air interface overhead introduced by the preamble symbol and interframe spacing, between adjacent PSPs, the complete preamble symbol can be transmitted only in the first non-LLT PPDU. The preamble symbols of the remaining non-LLT PPDUs can be trimmed according to one or more of the following methods: 1) reducing the duration of the non-high throughput (HT) short training field (L-STF), non-HT long training field (L-LTF), ultrahigh reliability (UHR) short training field (UHR-STF), and ultrahigh reliability long training field (UHR-LTF); 2) deleting some or all fields such as the non-HT signaling field (L-SIG), repeated non-HT signaling field (RL-SIG), universal signaling field (U-SIG), and ultrahigh reliability signaling field (UHR-SIG).

[0162] In one implementation method, for the unequal interval preemptive transmission scheme, within the PSP, when the AP allocates designated RUs for preemptive transmission to LLT STAs, if the AP only detects whether there is a preemptive transmission signal on the primary 20MHz channel, then the AP needs to allocate designated RUs to different LLT STAs within the primary 20MHz channel. The existing protocol supports a maximum of 9 LLT STAs. For example, in order to expand the number of LLT STAs, LLT STAs can be grouped, and RUs are allocated to each group of STAs on the primary 20MHz channel. Each RU only specifies a group, and STAs in the same group compete for the same RU to access the channel. If the AP detects that the RU of any designated group has a signal transmission, then the AP allocates uplink transmission resources to all STAs in the group. If the AP detects whether there is a preemptive transmission signal on the primary 20MHz channel and the secondary 20MHz channel, then the AP can allocate designated RUs to different LLT STAs within the two 20MHz channels. The existing protocol supports a maximum of 18 LLT STAs. If the AP detects whether there is a preemptive transmission signal on the entire bandwidth, the AP can allocate designated RUs to different LLT STAs within the full bandwidth. The existing protocol supports a maximum of 72 LLT STAs (corresponding to 160MHz) or 144 LLT STAs (corresponding to 320MHz).

[0163] Part 4: Uplink Transmission Resource Allocation Scheme within PSP

[0164] Figure 12 shows an example of uplink transmission resource allocation within a PSP. In this example, the uplink transmission resources include one or more RUs. The attributes and identifiers of STA1 through STA4 are shown in Table 1. The STA identifier is represented by an association identifier (AID).

[0165] Table 1

[0166] In a PSP, a Trigger frame is used to indicate at least one of the following types of RUs:

[0167] 1) Designated RU of LLT STA, used for LLT STA to report BSR frames, transmit UL LLT PPDU, etc.;

[0168] 12 , the designated RU of the LLT STA includes transmission resources exclusively occupied by STA2 to STA4.

[0169] 2) Associated users randomly access RU (AID=0), which is used for associated users to compete for uplink data transmission.

[0170] The RU corresponding to AID=0 can be used by multiple STAs associated with the AP. For example, if STA1 to STA4 are associated with the AP, the RU allocated by the AP and corresponding to AID=0 can be used by STA1 to STA4. For example, if STA1 wins the RU, it will be used by STA1.

[0171] 3) Unassociated user random access RU (AID=2045) is used for unassociated users to compete for network access.

[0172] Among them, the RU corresponding to AID=2045 can be used by STAs not associated with the AP to compete for network access and thus associate with the AP. For example, STA5 uses the RU corresponding to AID=2045 to compete for network access. After joining the network, the STAs associated with the AP include STA1 to STA5.

[0173] 4) Designated RU of non-LLT STA, used for non-LLT STA to report BA frames.

[0174] 12 , the designated RU of the non-LLT STA includes transmission resources exclusively occupied by STA1.

[0175] In one implementation method, the protocol may specify the RU allocation pattern for preemptive transmission, that is, different RU allocation schemes are adopted in different PSPs to avoid user collisions and improve anti-interference capabilities. Figure 13 is a schematic diagram of a pattern-based RU allocation scheme. The AP and LLT STA can negotiate the RU allocation pattern through management frames. Within the TXOP, the LLT STA adopts different RU allocation schemes in different PSPs in turn according to the negotiated RU allocation pattern. Three examples are given in Figure 13. In Example 1, the subcarrier spacing (tone) is 26-tone, and a cyclic shift interval of 1 is used to shift the RU resource allocation. In Example 2, the subcarrier spacing (tone) is 26-tone, and a cyclic shift interval of 2 is used to shift the RU resource allocation. In Example 3, the subcarrier spacing (tone) is 52-tone, and a cyclic shift interval of 1 is used to shift the RU resource allocation.

[0176] In one implementation, to minimize interference between LLT STAs, the AP can flexibly assign specific RUs to different subchannels based on the LLT STA's location (e.g., digital map) and signal strength (e.g., RSSI). For example, for geographically distant STAs with similar received signal strength indications (RSSIs), the AP can assign adjacent RUs. For geographically close STAs with similar RSSIs, the AP can assign RUs on different subchannels.

[0177] It is understood that in order to implement the functions in the above embodiments, the terminal device or network device includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0178] Figures 14 and 15 are schematic diagrams of the structures of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the terminal device or network device in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments. In the embodiments of the present application, the communication device can be a terminal device or a network device, or a module (such as a chip) applied to the terminal device or the network device.

[0179] The communication device 1400 shown in Figure 14 includes a processing unit 1410 and a transceiver unit 1420. The communication device 1400 is used to implement the functions of the terminal device or network device in the above method embodiment.

[0180] When the communication device 1400 is used to implement the functions of the network device (such as AP) in the above method embodiment, the processing unit 1410 is used to control the transceiver unit 1420 to send a first frame, and the first frame is used to indicate a first uplink transmission resource; within the transmission opportunity window, a first uplink low-latency service frame or a low-latency service report frame is received from at least one terminal device on the first uplink transmission resource, and the transmission opportunity window can be used to transmit non-low-latency service frames.

[0181] In one possible implementation method, the processing unit 1410 is used to control the transceiver unit 1420 to send a first frame, specifically including: sending the first frame in a first time period within the transmission opportunity window; the processing unit 1410 is used to control the transceiver unit 1420 to receive a first uplink low-latency service frame from at least one terminal device on the first uplink transmission resource within the transmission opportunity window, specifically including: receiving the first uplink low-latency service frame from the at least one terminal device in the first time period and on the first uplink transmission resource, and the data volume of the first uplink low-latency service frame is less than a first threshold.

[0182] In one possible implementation method, the low-latency service report frame is used to indicate the data volume of the uplink low-latency service to be transmitted; the processing unit 1410 is also used to control the transceiver unit 1420 to send a second frame in a second time period within the transmission opportunity window, and the second frame is used to indicate a second uplink transmission resource, and the second uplink transmission resource is determined based on the low-latency service report frame; the second uplink low-latency service frame is received from the at least one terminal device in the second time period and the second uplink transmission resource, and the second uplink low-latency service frame is used to transmit the uplink low-latency service to be transmitted.

[0183] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to send an aggregate frame to the at least one terminal device within the transmission opportunity window, and the aggregate frame includes a confirmation frame for the first uplink low-latency service frame and a confirmation frame for the second uplink low-latency service frame.

[0184] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to send a downlink low-latency service frame within a third time period within the transmission opportunity window, wherein the downlink low-latency service frame includes downlink service data and a transmission resource indication, and the transmission resource indication is used to indicate the transmission resources of the downlink low-latency service data.

[0185] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to send a third frame within the transmission opportunity window, and the third frame carries a preemptive transmission indication, and the preemptive transmission indication is used to indicate whether low-latency services are allowed to preempt transmission after the transmission of the third frame is completed.

[0186] In a possible implementation method, there is a time period for sending uplink low-latency service frames or low-latency service report frames after every fixed number of non-low-latency service frames in the transmission opportunity window.

[0187] In a possible implementation method, the transmission opportunity window does not include other frames for indicating uplink transmission resources except the first frame.

[0188] In a possible implementation method, the processing unit 1410 is configured to control the transceiver unit 1420 to send the first frame, specifically including: being configured to send the first frame before the transmission opportunity window.

[0189] In a possible implementation method, the processing unit 1410 is further used to control the transceiver unit 1420 to send a beacon frame to the at least one terminal device, and the beacon frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0190] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to send a management frame, which is used to negotiate whether low-latency service preemptive transmission is supported within the transmission opportunity window; and receive a response frame, which indicates that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0191] In a possible implementation method, the processing unit 1410 is further configured to control the transceiver unit 1420 to receive a management frame, where the management frame is configured to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0192] In one possible implementation method, the network device is the initiator of the transmission opportunity window, and the downlink low-latency service frame sent by the transceiver unit 1420 can be preempted for transmission between any two downlink non-low-latency service frames, and the uplink low-latency service frame received by the transceiver unit 1420 can only be preempted for transmission during a specified time period within the transmission opportunity window.

[0193] In a possible implementation method, the processing unit 1410 is further used to control the transceiver unit 1420 to send a fourth frame within the specified time period, and the fourth frame is used to request the at least one terminal device to report a low-latency service report.

[0194] In a possible implementation method, the fourth frame is also used to indicate the next designated time period.

[0195] In one possible implementation method, the network device is the initiator of the transmission opportunity window, and the non-low-latency service frame sent by the transceiver unit 1420 can be interrupted to preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-low-latency service frame continues to be transmitted.

[0196] In one possible implementation method, there are multiple non-low-latency service frames between two adjacent specified time periods within the transmission activation window, the first non-low-latency service frame among the multiple non-low-latency service frames contains a complete leading symbol, and the other non-low-latency service frames among the multiple non-low-latency service frames contain a cropped leading symbol.

[0197] When the communication device 1400 is used to implement the functions of the network device (such as AP) in the above method embodiment, the processing unit 1410 is used to control the transceiver unit 1420 to send a communication frame to at least one terminal device within the transmission opportunity window, and the communication frame includes indication information and downlink low-latency service data, and the indication information is used to indicate the transmission resources of the downlink low-latency service data, and the transmission opportunity window can be used to transmit non-low-latency service frames.

[0198] When the communication device 1400 is used to implement the functions of the terminal device (such as LLT STA) in the above method embodiment, the processing unit 1410 is used to control the transceiver unit 1420 to receive a first frame, where the first frame is used to indicate a first uplink transmission resource; and to send a first uplink low-latency service frame or a low-latency service report frame on the first uplink transmission resource within a transmission opportunity window, where the transmission opportunity window can be used to transmit non-low-latency service frames.

[0199] In one possible implementation method, the processing unit 1410 is used to control the transceiver unit 1420 to receive the first frame, specifically including: receiving the first frame in the first time period within the transmission opportunity window; the processing unit 1410 is used to control the transceiver unit 1420 to send the first uplink low-latency service frame on the first uplink transmission resource within the transmission opportunity window, specifically including: sending the first uplink low-latency service frame in the first time period and on the first uplink transmission resource, and the data amount of the first uplink low-latency service frame is less than the first threshold.

[0200] In one possible implementation method, the low-latency service report frame is used to indicate the data volume of the uplink low-latency service to be transmitted; the processing unit 1410 is also used to control the transceiver unit 1420 to receive a second frame in a second time period within the transmission opportunity window, and the second frame is used to indicate a second uplink transmission resource, and the second uplink transmission resource is determined based on the low-latency service report frame; a second uplink low-latency service frame is sent in the second time period and on the second uplink transmission resource, and the second uplink low-latency service frame is used to transmit the uplink low-latency service to be transmitted.

[0201] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to receive an aggregate frame within the transmission opportunity window, wherein the aggregate frame includes a confirmation frame for the first uplink low-latency service frame and a confirmation frame for the second uplink low-latency service frame.

[0202] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to receive a downlink low-latency service frame within a third time period within the transmission opportunity window, wherein the downlink low-latency service frame includes downlink service data and a transmission resource indication, and the transmission resource indication is used to indicate the transmission resources of the downlink low-latency service data.

[0203] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to receive a third frame within the transmission opportunity window, and the third frame carries a preemptive transmission indication, and the preemptive transmission indication is used to indicate whether low-latency services are allowed to preempt transmission after the transmission of the third frame is completed.

[0204] In a possible implementation method, there is a time period for sending uplink low-latency service frames or low-latency service report frames after every fixed number of non-low-latency service frames in the transmission opportunity window.

[0205] In a possible implementation method, the transmission opportunity window does not include other frames for indicating uplink transmission resources except the first frame.

[0206] In a possible implementation method, the processing unit 1410 is configured to control the transceiver unit 1420 to receive the first frame, specifically including: receiving the first frame before the transmission opportunity window.

[0207] In a possible implementation method, the processing unit 1410 is further configured to control the transceiver unit 1420 to receive a beacon frame, where the beacon frame is configured to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0208] In one possible implementation method, the processing unit 1410 is also used to control the transceiver unit 1420 to receive a management frame, which is used to negotiate whether low-latency service preemptive transmission is supported within the transmission opportunity window; and send a response frame, which indicates that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0209] In a possible implementation method, the processing unit 1410 is further configured to control the transceiver unit 1420 to send a management frame, where the management frame is configured to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

[0210] In one possible implementation method, the terminal device is the initiator of the transmission opportunity window, and the low-latency service frame received or sent by the transceiver unit 1420 can be preempted for transmission between any two non-low-latency service frames, and other low-latency service frames can only be preempted for transmission within a specified time period within the transmission opportunity window.

[0211] In one possible implementation method, the terminal device is the initiator of the transmission opportunity window, and the non-low-latency service frame sent by the transceiver unit 1420 can be interrupted to preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-low-latency service frame continues to be transmitted.

[0212] In one possible implementation method, there are multiple non-low-latency service frames between two adjacent specified time periods within the transmission activation window, the first non-low-latency service frame among the multiple non-low-latency service frames contains a complete leading symbol, and the other non-low-latency service frames among the multiple non-low-latency service frames contain a cropped leading symbol.

[0213] For a more detailed description of the processing unit 1410 and the transceiver unit 1420, reference can be made to the relevant description in the above method embodiment, which will not be repeated here.

[0214] The communication device 1500 shown in Figure 15 includes a processor 1510 and an interface circuit 1520. The processor 1510 and the interface circuit 1520 are coupled to each other. It is understood that the interface circuit 1520 can be a transceiver or an input / output interface. Optionally, the communication device 1500 may also include a memory 1530 for storing instructions executed by the processor 1510, or storing input data required by the processor 1510 to execute instructions, or storing data generated after the processor 1510 executes instructions.

[0215] When the communication device 1500 is used to implement the above method embodiment, the processor 1510 is used to implement the functions of the above processing unit 1410 , and the interface circuit 1520 is used to implement the functions of the above transceiver unit 1420 .

[0216] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0217] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, mobile hard disks, compact disc read-only memory (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a terminal device or a network device. Of course, the processor and storage medium can also exist as discrete components in an access network device or a terminal.

[0218] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. A computer program refers to a set of instructions that instruct an electronic computer or other device with message processing capabilities to perform each step of the action, usually written in a certain programming language and running on a certain target architecture. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instruction can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0219] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0220] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next related objects are in an "or" relationship; in the formulas of this application, the character " / " indicates that the previous and next related objects are in a "division" relationship.

[0221] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A communication method, characterized in that: Applied to a network device in a wireless fidelity WiFi system, the method comprises: Sending a first frame, where the first frame is used to indicate a first uplink transmission resource; A first uplink low-latency service frame or a low-latency service report frame is received from at least one terminal device on the first uplink transmission resource within a transmission opportunity window, and the transmission opportunity window can be used to transmit a non-low-latency service frame.

2. The method according to claim 1, characterized in that The sending of the first frame comprises: Sending the first frame in a first time period within the transmission opportunity window; The receiving a first uplink low-latency service frame from at least one terminal device on the first uplink transmission resource within the transmission opportunity window includes: The first uplink low-latency service frame is received from the at least one terminal device in the first time period and on the first uplink transmission resource, and the data volume of the first uplink low-latency service frame is less than a first threshold.

3. The method according to claim 1 or 2, characterized in that The low-latency service report frame is used to indicate the data volume of the uplink low-latency service to be transmitted; The method further comprises: Sending a second frame in a second time period within the transmission opportunity window, where the second frame is used to indicate a second uplink transmission resource, where the second uplink transmission resource is determined based on the low-latency service report frame; A second uplink low-latency service frame is received from the at least one terminal device in the second time period and on the second uplink transmission resource, wherein the second uplink low-latency service frame is used to transmit the uplink low-latency service to be transmitted.

4. The method according to claim 3, characterized in that The method further comprises: An aggregate frame is sent to the at least one terminal device within the transmission opportunity window, wherein the aggregate frame includes a confirmation frame for the first uplink low-latency service frame and a confirmation frame for the second uplink low-latency service frame.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: A downlink low-latency service frame is sent within a third time period within the transmission opportunity window, wherein the downlink low-latency service frame includes data of the downlink low-latency service and a transmission resource indication, and the transmission resource indication is used to indicate the transmission resource of the data of the downlink low-latency service.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: A third frame is sent within the transmission opportunity window, wherein the third frame carries a preemptive transmission indication, and the preemptive transmission indication is used to indicate whether a low-latency service is allowed to preempt transmission after the transmission of the third frame is completed.

7. The method according to any one of claims 1 to 6, characterized in that There is a time period for sending an uplink low-latency service frame or a low-latency service report frame after every fixed number of non-low-latency service frames in the transmission opportunity window.

8. The method according to claim 1 or 2, characterized in that: The transmission opportunity window does not include other frames for indicating uplink transmission resources except the first frame.

9. The method according to claim 1, characterized in that The sending of the first frame comprises: The first frame is sent before the transmission opportunity window.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: A beacon frame is sent to the at least one terminal device, wherein the beacon frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

11. The method according to any one of claims 1 to 9, characterized in that The method further comprises: Sending a management frame, where the management frame is used to negotiate whether to support low-latency service preemptive transmission within the transmission opportunity window; A response frame is received, wherein the response frame indicates that low-latency service preemptive transmission is supported within the transmission opportunity window.

12. The method according to any one of claims 1 to 9, characterized in that The method further comprises: A management frame is received, where the management frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

13. The method according to any one of claims 1 to 12, characterized in that If the network device is the initiator of the transmission opportunity window, the downlink low-latency service frame sent by the network device can be preempted for transmission between any two downlink non-low-latency service frames, and the uplink low-latency service frame received by the network device can be preempted for transmission only in a specified time period within the transmission opportunity window.

14. The method according to claim 13, characterized in that The method further comprises: A fourth frame is sent within the specified time period, where the fourth frame is used to request the at least one terminal device to report a low-latency service report.

15. The method according to claim 14, characterized in that The fourth frame is also used to indicate the next designated time period.

16. The method according to any one of claims 1 to 12, characterized in that If the network device is the initiator of the transmission opportunity window, the non-low-latency service frame sent by the network device can be interrupted to preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-low-latency service frame continues to be transmitted.

17. The method according to any one of claims 1 to 16, characterized in that There are multiple non-low-latency service frames between two adjacent specified time periods within the transmission activation window, the first non-low-latency service frame among the multiple non-low-latency service frames includes a complete leading symbol, and the other non-low-latency service frames among the multiple non-low-latency service frames include cropped leading symbols.

18. A communication method, characterized in that: Applied to a terminal device in a wireless fidelity WiFi system, the method comprises: receiving a first frame, where the first frame is used to indicate a first uplink transmission resource; A first uplink low-latency service frame or a low-latency service report frame is sent on the first uplink transmission resource within a transmission opportunity window, and the transmission opportunity window can be used to transmit a non-low-latency service frame.

19. The method according to claim 18, characterized in that The receiving of the first frame comprises: receiving the first frame in a first time period within the transmission opportunity window; The sending a first uplink low-latency service frame on the first uplink transmission resource within the transmission opportunity window includes: The first uplink low-latency service frame is sent in the first time period and on the first uplink transmission resource, and the data volume of the first uplink low-latency service frame is less than a first threshold.

20. The method according to claim 18 or 19, characterized in that The low-latency service report frame is used to indicate the data volume of the uplink low-latency service to be transmitted; The method further comprises: Receiving a second frame in a second time period within the transmission opportunity window, where the second frame is used to indicate a second uplink transmission resource, where the second uplink transmission resource is determined based on the low-latency service report frame; A second uplink low-latency service frame is sent in the second time period and on the second uplink transmission resource, where the second uplink low-latency service frame is used to transmit the uplink low-latency service to be transmitted.

21. The method of claim 20, wherein: The method further comprises: An aggregate frame is received within the transmission opportunity window, wherein the aggregate frame includes a confirmation frame for the first uplink low-latency service frame and a confirmation frame for the second uplink low-latency service frame.

22. The method according to any one of claims 18 to 21, characterized in that The method further comprises: A downlink low-latency service frame is received within a third time period within the transmission opportunity window, wherein the downlink low-latency service frame includes data of the downlink low-latency service and a transmission resource indication, and the transmission resource indication is used to indicate a transmission resource for the data of the downlink low-latency service.

23. The method according to any one of claims 18 to 21, characterized in that The method further comprises: A third frame is received within the transmission opportunity window, wherein the third frame carries a preemption transmission indication, and the preemption transmission indication is used to indicate whether a low-latency service is allowed to preempt transmission after the transmission of the third frame is completed.

24. The method according to any one of claims 18 to 23, characterized in that There is a time period for sending an uplink low-latency service frame or a low-latency service report frame after every fixed number of non-low-latency service frames in the transmission opportunity window.

25. The method according to claim 18 or 19, characterized in that The transmission opportunity window does not include other frames for indicating uplink transmission resources except the first frame.

26. The method of claim 18, wherein: The receiving of the first frame comprises: The first frame is received prior to the transmission opportunity window.

27. The method according to any one of claims 18 to 26, characterized in that The method further comprises: A beacon frame is received, where the beacon frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

28. The method according to any one of claims 18 to 26, characterized in that The method further comprises: receiving a management frame, wherein the management frame is used to negotiate whether to support low-latency service preemptive transmission within the transmission opportunity window; A response frame is sent, wherein the response frame indicates that low-latency service preemptive transmission is supported within the transmission opportunity window.

29. The method according to any one of claims 18 to 26, characterized in that The method further comprises: A management frame is sent, where the management frame is used to indicate that low-latency service preemptive transmission is supported within the transmission opportunity window.

30. The method according to any one of claims 18 to 29, characterized in that If the terminal device is the initiator of the transmission opportunity window, the low-latency service frame received or sent by the terminal device can be preempted for transmission between any two non-low-latency service frames, and other low-latency service frames are only transmitted within a specified time period within the transmission opportunity window. Preempt transmission.

31. The method according to any one of claims 18 to 29, characterized in that If the terminal device is the initiator of the transmission opportunity window, the non-low-latency service frame sent by the terminal device can be interrupted to preempt the transmission of the low-latency service frame, and after the transmission of the low-latency service frame is completed, the non-low-latency service frame continues to be transmitted.

32. The method according to any one of claims 18 to 31, characterized in that There are multiple non-low-latency service frames between two adjacent specified time periods within the transmission activation window, the first non-low-latency service frame among the multiple non-low-latency service frames includes a complete leading symbol, and the other non-low-latency service frames among the multiple non-low-latency service frames include cropped leading symbols.

33. A communication device, characterized in that: The invention comprises a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method described in any one of claims 1 to 17 or the method described in any one of claims 18 to 32.

34. A computer program product, characterized in that The computer program product comprises instructions, which, when executed on a processor, cause the processor to perform the method according to any one of claims 1 to 17 or the method according to any one of claims 18 to 32.

35. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction, and when the computer program or instruction is executed by the communication device, the method described in any one of claims 1 to 17, or the method described in any one of claims 18 to 32 is implemented.

36. A communication system, characterized in that: It comprises a network device for executing the method described in any one of claims 1 to 17, and a terminal device for executing the method described in any one of claims 18 to 32.

Images