Communication method, communication device and communication system

Abstract

The embodiment of the invention relates to a communication method, communication equipment and a communication system. The communication method comprises the following steps: in a first TXOP, responding to data sent by a TXOP holding end, and replying a block acknowledgement Block Ack frame to the TXOP holding end; wherein the Block Ack frame comprises at least one of a first identifier and a first identification domain; the first identifier identifies whether the TXOP response end requests the TXOP holding end to share part of transmission time of the first TXOP for low-delay service data transmission or not; and the first identification domain identifies the duration required by the TXOP response end to transmit the low-delay service data so as to cope with the sudden low-delay service, improve the low-delay service data transmission mechanism and reduce the transmission delay.

Description

Communication method, communication equipment and communication system Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method, communication equipment, and communication system. Background Art

[0002] Currently, Wi-Fi technology research focuses on Ultra High Reliability (UHR), with the goal of improving the reliability of Wireless Local Area Networks (WLAN) connections, reducing latency, improving manageability, increasing throughput at different signal-to-noise ratio (SNR) levels, and reducing device-level power consumption.

[0003] In Ultra High Resolution (UHR), low-latency service transmission mechanisms will be further enhanced to support multi-connection scenarios. To enhance throughput at varying signal-to-noise ratio (SNR) levels, transmission opportunity (TXOP) sharing may be adopted in Ultra High Resolution (UHR). Therefore, the TXOP sharing mechanism needs to be further refined to meet the transmission requirements of Ultra High Resolution (UHR).

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a communication method, a communication device, and a communication system to further improve the TXOP sharing mechanism to meet the transmission requirements of UHR.

[0006] In one aspect, an embodiment of the present disclosure provides a communication method, applied to a TXOP responder, the method comprising:

[0007] In a first TXOP, in response to data sent by a TXOP holding end, replying a Block Ack frame to the TXOP holding end; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0008] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0009] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0010] On the other hand, an embodiment of the present disclosure further provides a communication method, applied to a TXOP holding end, the method comprising:

[0011] In a first TXOP, during a process of sending data to a TXOP responder, receiving a Block Ack frame sent by the TXOP responder; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0012] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0013] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0014] On the other hand, an embodiment of the present disclosure further provides a communication device, wherein the communication device is a TXOP responder, and the TXOP responder includes:

[0015] a first processing module, configured to, within a first TXOP, reply a Block Ack frame to the TXOP holding end in response to data sent by the TXOP holding end; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0016] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0017] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0018] On the other hand, an embodiment of the present disclosure further provides a communication device, wherein the communication device is a TXOP holding end, and the TXOP holding end includes:

[0019] a second processing module, configured to receive, during a process of sending data to a TXOP responder within the first TXOP, a Block Ack frame sent by the TXOP responder, wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0020] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0021] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0022] On the other hand, an embodiment of the present disclosure further provides a communication device, wherein the communication device is a TXOP responder, including:

[0023] one or more processors;

[0024] The TXOP responder is used to implement the communication method described in the embodiment of the present disclosure.

[0025] On the other hand, an embodiment of the present disclosure further provides a communication device, wherein the communication device is a TXOP holder, including:

[0026] one or more processors;

[0027] The TXOP holding end is used to implement the communication method described in the embodiment of the present disclosure.

[0028] An embodiment of the present disclosure further provides a communication system, including a TXOP responder and a TXOP holder; wherein the TXOP responder is configured to implement the communication method described in the embodiment of the present disclosure, and the TXOP holder is configured to implement the communication method described in the embodiment of the present disclosure.

[0029] The embodiment of the present disclosure further provides a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the communication method as described in the embodiment of the present disclosure.

[0030] In an embodiment of the present disclosure, during the process of a TXOP holder transmitting data to a TXOP responder, if the TXOP responder needs to transmit other low-latency service data, the first identifier in the Block Ack frame is set to indicate that the TXOP responder is requesting the TXOP holder to share a portion of the first TXOP's transmission time for low-latency service data transmission. Furthermore, the first identification field in the Block Ack frame sent back to the TXOP holder is set to indicate the duration required for the TXOP responder to transmit the low-latency service data. In other words, the TXOP responder will transmit the low-latency service data to the receiver of the low-latency service data within the TXOP shared by the TXOP holder. In this way, if the TXOP holder has low-latency service data cached within the TXOP for transmission to the receiver of the low-latency service data, the first identifier and first identification field in the device Block Ack frame can be used to request the TXOP holder to allocate a portion of the TXOP's transmission time. This allows for coping with sudden low-latency services, improving the low-latency service data transmission mechanism, and reducing transmission latency.

[0031] Additional aspects and advantages of the embodiments of the present disclosure will be given in part in the following description, which will become apparent from the following description or be learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0033] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0034] FIG2 is one of exemplary interaction diagrams of a method provided according to an embodiment of the present disclosure;

[0035] FIG3 is a second exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0036] FIG4 is a schematic diagram of the structure of a Block Ack frame provided according to an embodiment of the present disclosure;

[0037] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0038] FIG6 is a second flow chart of the communication method provided in an embodiment of the present disclosure;

[0039] FIG7 is a schematic diagram of the structure of a TXOP responder proposed in an embodiment of the present disclosure;

[0040] FIG8 is a schematic diagram of the structure of a TXOP holding terminal proposed in an embodiment of the present disclosure;

[0041] FIG9 is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure;

[0042] FIG10 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0043] The embodiments of the present disclosure provide a communication method, a communication device, and a communication system.

[0044] In a first aspect, an embodiment of the present disclosure provides a communication method, applied to a TXOP responder, the method comprising:

[0045] In a first TXOP, in response to data sent by a TXOP holding end, replying a Block Ack frame to the TXOP holding end; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0046] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0047] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0048] In the above embodiment, when a TXOP holder sends data to a TXOP responder, if the TXOP responder needs to transmit other low-latency service data, the first identifier in the Block Ack frame is set to indicate that the TXOP responder is requesting the TXOP holder to share a portion of the first TXOP's transmission time for low-latency service data transmission. Furthermore, the first identification field in the Block Ack frame sent back to the TXOP holder is set to indicate the duration required for the TXOP responder to transmit the low-latency service data. This means that the TXOP responder will transmit the low-latency service data to the receiver of the low-latency service data within the TXOP shared by the TXOP holder. In this way, if the TXOP holder has low-latency service data buffered within the TXOP for transmission to the receiver of the low-latency service data, it can request the TXOP holder to allocate a portion of the TXOP's transmission time via the first identifier and first identification field in the device Block Ack frame. This allows for the handling of bursty low-latency services, improves the low-latency service data transmission mechanism, and reduces transmission latency.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the first identifier is carried in a block acknowledgment control BA Control field of the Block Ack frame;

[0050] The first identifier is set to a first parameter value, indicating that the TXOP responder does not request the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0051] The first identifier is set to a second parameter value, indicating that the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0052] In the above embodiment, if the TXOP responder does not need to transmit low-latency service data to the low-latency service data receiver within the TXOP, the first identifier in the Block Ack frame is set to the first parameter value. If the TXOP responder does need to transmit low-latency service data to the low-latency service data receiver within the TXOP, the first identifier in the Block Ack frame is set to the second parameter value. By defining the value of the first identifier in the Block Ack frame, the low-latency service transmission mechanism within the TXOP is further improved.

[0053] In combination with some embodiments of the first aspect, in some embodiments, when the first identifier is set to the second parameter value, the Block Ack frame includes a transmission opportunity request information TXOP Request Info field, and the first identification field is carried in the TXOP Request Info field.

[0054] In the above embodiment, when the first identifier is set to the second parameter value, the TXOP time for low-latency service data transmission is further identified by setting a first identification field, which is carried in the TXOP Request Info field.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, after replying a Block Ack frame to the TXOP holding end, the method further includes:

[0056] The first identifier is set to the first parameter value, and data sent by the TXOP holding end is received;

[0057] or,

[0058] The first identifier is set to the second parameter value, and a multi-user request to transmit transmission opportunity sharing trigger MU-RTS TXS Trigger frame sent by the TXOP holder is received; wherein the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes the device identification of the target device that shares part of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by the TXOP holder to each of the target devices.

[0059] In the above embodiment, the TXOP responder sets the first identifier to the first parameter value, indicating that the TXOP responder currently does not need the TXOP holder to share the TXOP for low-latency service data transmission. In this case, the TXOP responder will continue to receive data sent by the TXOP holder within the TXOP. If the TXOP responder sets the first identifier to the second parameter value, indicating that the TXOP responder currently needs the TXOP holder to share the TXOP for low-latency service data transmission, the TXOP responder receives the MU-RTS TXS Trigger frame sent by the TXOP holder and determines, based on the second identification field of the MU-RTS TXS Trigger frame, whether the target device with which the TXOP portion of the transmission time is shared matches. If so, the TXOP responder determines the transmission time allocated by the TXOP holder based on the third identification field of the MU-RTS TXS Trigger frame. The low-latency service data is then transmitted within the transmission time allocated by the TXOP holder, ensuring timely and efficient transmission of the low-latency service data.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, after receiving the MU-RTS TXS Trigger frame sent by the TXOP holder, the method includes:

[0061] The device identifier in the second identifier field does not include the device identifier of the TXOP responder, does not respond to the MU-RTS TXS Trigger frame, and receives data sent by the TXOP holder;

[0062] or,

[0063] The device identification in the second identification field includes the device identification of the TXOP responder, and the low-latency service data is transmitted within the transmission time shared by the TXOP holder for the TXOP responder.

[0064] In the above embodiment, if the second identification field of the MU-RTS TXS Trigger frame does not include the device identification of the TXOP responder, the MU-RTS TXS Trigger frame will not be responded to, and data sent by the TXOP holder will continue to be accepted. If the second identification field of the MU-RTS TXS Trigger frame includes the device identification of the TXOP responder, the low-latency service data will be transmitted within the transmission time allocated by the TXOP holder, thereby ensuring the timely and effective transmission of the low-latency service data and reducing the transmission delay of the low-latency service data.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, transmitting the low-latency service data within the transmission time shared by the TXOP holder for the TXOP responder includes:

[0066] Sending a request to send (RTS) frame to a receiving end of the low-latency service data; wherein the receiving address of the RTS frame is the address of the receiving end; and the duration of the RTS frame is set to be the sum of the duration of the receiving end sending a clear-to-send (CTS) frame, the duration required for the TXOP responder to transmit the low-latency service data, the duration of the receiving end sending an acknowledgment (ACK) frame, and the sum of three short frame intervals.

[0067] Receive the CTS frame sent by the receiving end, and send the low-latency service data to the receiving end.

[0068] In the above embodiment, the TXOP responder first sends an RTS frame to the receiving end of the low-latency service data within the transmission time allocated by the TXOP holding end. The receiving end then sends a CTS frame to the TXOP responder after a short frame interval. After receiving the CTS frame, the TXOP responder transmits the low-latency service data after a short frame interval. The receiving end receives the low-latency service data and feeds back an ACK frame to the TXOP responder after a short frame interval, thereby completing the transmission of the low-latency service data and improving the low-latency service data transmission mechanism.

[0069] In conjunction with some embodiments of the first aspect, in some embodiments, the TXOP holding end includes a station device, and the TXOP responding end includes an access point device;

[0070] or,

[0071] The TXOP holding end and the TXOP responding end are two TDLS devices that have established a channel and are directly connected to establish a TDLS link.

[0072] In the above embodiment, the TXOP responder may be an access point device or a TDLS device that has established a TDLS link, which further improves the low-latency service transmission mechanism of the access point device or the TDLS device within the TXOP.

[0073] In a second aspect, an embodiment of the present disclosure provides a communication method, applied to a TXOP holder, the method comprising:

[0074] In a first TXOP, during a process of sending data to a TXOP responder, receiving a Block Ack frame sent by the TXOP responder; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0075] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0076] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the first identifier is carried in a block acknowledgment control BA Control field of the Block Ack frame;

[0078] The first identifier is set to a first parameter value, indicating that the TXOP responder does not request to use part of the transmission time of the first TXOP shared by the TXOP holder for low-latency service data transmission;

[0079] The first identifier is set to a second parameter value, indicating that the TXOP responder requests to use a portion of the transmission time of the first TXOP shared by the TXOP holder for low-latency service data transmission.

[0080] In combination with some embodiments of the second aspect, in some embodiments, when the first identifier is set to the second parameter value, the Block Ack frame includes a transmission opportunity request information TXOP Request Info field, and the first identification field is carried in the TXOP Request Info field.

[0081] In conjunction with some embodiments of the second aspect, in some embodiments, after receiving the Block Ack frame sent by the TXOP responder, the method further includes:

[0082] The first identifier is set to the first parameter value, and data is sent to the TXOP responder;

[0083] or,

[0084] The first identifier is set to the second parameter value, and a multi-user request to transmit transmission opportunity sharing trigger MU-RTS TXS Trigger frame is sent to the TXOP responder; wherein the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes the device identification of the target device that shares part of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by the TXOP holder to each of the target devices.

[0085] In combination with some embodiments of the second aspect, in some embodiments, within the transmission time allocated by the TXOP holder to the target device, the TXOP holder sends data only when it receives a data sending request from the target device and responds to the data sending request.

[0086] In conjunction with some embodiments of the second aspect, in some embodiments, the TXOP holding end includes an access point device, and the TXOP responding end includes a station device;

[0087] or,

[0088] The TXOP holding end and the TXOP responding end are two TDLS devices that have established a channel and are directly connected to establish a TDLS link.

[0089] In a third aspect, an embodiment of the present disclosure further provides a communication device, which is a TXOP responder, and the TXOP responder includes a first processing module; wherein the TXOP responder is used to execute an optional implementation method of the first aspect.

[0090] In a fourth aspect, an embodiment of the present disclosure further provides a communication device, which is a TXOP holding end and includes: a second processing module; wherein the above-mentioned TXOP holding end is used to execute the optional implementation method of the second aspect.

[0091] In a fifth aspect, an embodiment of the present disclosure further provides a communication device, wherein the communication device is a TXOP responder, including:

[0092] one or more processors;

[0093] The TXOP responder is used to execute the optional implementation of the first aspect.

[0094] In a sixth aspect, an embodiment of the present disclosure further provides a communication device, wherein the communication device is a TXOP holding end, including:

[0095] one or more processors;

[0096] The TXOP holding end is used to execute the optional implementation of the second aspect.

[0097] In the seventh aspect, an embodiment of the present disclosure further provides a communication system, comprising a TXOP responding end and a TXOP holding end; wherein the TXOP responding end is configured to execute the optional implementation method as described in the first aspect, and the TXOP holding end is configured to perform the optional implementation method as described in the second aspect.

[0098] In an eighth aspect, an embodiment of the present disclosure further provides a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute the optional implementation methods described in the first and second aspects.

[0099] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0100] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0101] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0102] It is understandable that the aforementioned TXOP responder, TXOP holder, communication system, storage medium, program product, computer program, chip, or chip system are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0103] The embodiments of the present disclosure provide a communication method, a communication device, and a communication system. In some embodiments, the terms communication method, signal transmission method, wireless frame transmission method, etc. can be used interchangeably, and the terms information processing system, communication system, etc. can be used interchangeably.

[0104] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0105] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0106] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0107] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0108] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0109] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0110] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0111] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0112] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0113] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0114] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0115] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0116] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0117] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0118] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0119] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0120] As shown in FIG1 , a communication system 100 includes a Transmit Opportunity (TXOP) responder 101 (which may be an Access Point, AP, or P2P AP) and a TXOP holder 102 (which may be a Station, STA, or P2P STA).

[0121] In some embodiments, TXOP responder 101 and TXOP holder 102 may include, for example, a wireless communication chip, a wireless sensor, or a wireless communication terminal that supports WiFi communication. Optionally, the wireless communication terminal may be, for example, a mobile phone, a wearable device, an Internet of Things device that supports WiFi communication, a car with WiFi communication capability, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device used in industrial control, a wireless terminal device used in self-driving, a wireless terminal device used in remote medical surgery, a wireless terminal device used in a smart grid, a wireless terminal device used in transportation safety, a wireless terminal device used in a smart city, or a wireless terminal device used in a smart home, but is not limited thereto.

[0122] Specifically, TXOP responder 101 and TXOP holder 102 may be terminal devices or network devices equipped with a Wireless Fidelity (WiFi) chip. Optionally, TXOP responder 101 and TXOP holder 102 may support multiple WLAN standards, such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, 802.11bf, and 802.11bn, as well as the next generation 802.11 protocol, but are not limited thereto.

[0123] In some embodiments, the TXOP responder 101 can be an access point for a mobile terminal to enter a wired network. The AP is equivalent to a bridge connecting a wired network and a wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet. Specifically, the AP can be a terminal device or a network device with a wireless fidelity chip. Optionally, the AP can support multiple WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a, 802.11bf, 802.11bn, and support the next generation 802.11 protocol, but is not limited to this.

[0124] Optionally, in an embodiment of the present disclosure, the AP and STA may be devices supporting multiple connections, for example, they may be represented as a multi-connection access point device (AP MLD) and a multi-connection site device (Non-Access Point Multi-Link Device, Non-AP MLD), respectively; the AP MLD may represent an access point supporting multi-connection communication functions, and the non-AP MLD may represent a site supporting multi-connection communication functions.

[0125] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0126] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0127] The various embodiments of the present disclosure can be applied to wireless local area networks (WLANs), such as those using the 802.11 series of protocols. In a WLAN, a Basic Service Set (BSS) is a fundamental component of a WLAN. A BSS network consists of station devices with some association within a specific coverage area. One scenario of association is that stations communicate directly with each other in an ad hoc network, which is called an Independent Basic Service Set (IBSS). Another more common scenario is that in a BSS network, there is only one central station dedicated to managing the BSS, called an access point, and all other STAs in the network are associated with it. Other stations in the BSS network that are not the central station are called terminals, also called non-AP STAs. Terminals and non-AP STAs are collectively referred to as STAs. When describing STAs, there is no need to distinguish between APs and non-AP STAs. In the same BSS network, due to distance, transmission power, and other factors, a STA cannot detect other STAs that are farther away from it, and the two STAs are each other's hidden nodes.

[0128] FIG2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the method includes:

[0129] In step 201, the TXOP responder 101 replies with a Block Ack frame.

[0130] In WLAN communication scenarios, the Transmit Opportunity (TXOP) mechanism is introduced. A TXOP refers to a bounded time period during which a device (such as an AP or STA) can transmit a specific communication category. For example, a STA obtains a TXOP through competition. Once the TXOP is obtained, the STA can transmit frames of a specific communication category within the TXOP. For another example, an AP obtains a TXOP through competition. Once the TXOP is obtained, the AP can transmit frames of a specific communication category within the TXOP. Frames can specifically be data frames, control frames, and management frames. When a device obtains a TXOP through channel competition, the device is called a TXOP holder. During the frame exchange sequence, the TXOP holder sends frames to other devices. If the device does not obtain a TXOP during this process, the device is called a TXOP responder. Correspondingly, the TXOP holder is called a TXOP initiator.

[0131] In actual communication scenarios, while the TXOP holder is sending data to the associated TXOP responder, the TXOP responder may have cached low-latency service data for transmission to other devices. Since only the TXOP holder can actively send data within a TXOP, other devices can only receive data or send response frames to their own data. Therefore, the TXOP responder can only transmit low-latency service data to other devices after the TXOP reserved by the TXOP holder has ended. This can significantly delay the transmission of low-latency service data.

[0132] In a TXOP, there are a TXOP holder and a TXOP responder. The TXOP holder can be a STA or a P2P STA, the TXOP responder can be an AP or a P2P STA, and other station devices can be STAs or P2P APs.

[0133] In the disclosed embodiment, when the TXOP holder is a STA, after obtaining a TXOP transmission opportunity, the STA sends a request to send (RTS) frame to the TXOP responder (AP). The RTS frame is used to reserve the right to use the communication medium for the TXOP responder to use.

[0134] When the TXOP holder is a P2P STA, after obtaining the TXOP transmission opportunity, the P2P STA sends an RTS frame to the TXOP responder (P2P STA). The RTS frame is used to reserve the right to use the communication medium for the TXOP responder to use.

[0135] In the embodiment of the present disclosure, after receiving the RTS frame, the TXOP responder feeds back a clear to send (CTS) frame to the TXOP holder to confirm the transmission of the TXOP holder.

[0136] In the disclosed embodiment, after receiving the CTS frame, the TXOP holder confirms that the CTS is a feedback of the RTS frame previously sent by itself and the TXOP holder channel is idle, then the TXOP holder sends data to the TXOP responder.

[0137] In the embodiment of the present disclosure, the TXOP responder, in response to data sent by the TXOP holding end within the first TXOP, replies to the TXOP holding end with a Block Ack frame; wherein the Block Ack frame includes at least one of the first identifier and the first identification field;

[0138] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0139] The first identification field identifies the time required for the TXOP responder to transmit low-latency service data.

[0140] This disclosed embodiment uses the AP as the TXOP responder and the STA as the TXOP holder. When the AP receives uplink data from the STA and has temporary or burst low-latency service data to transmit, the AP includes a first identifier and a first identification field in the Block Ack frame it responds to the STA. The first identifier identifies whether the AP requests the STA to share part of the TXOP transmission time for temporary or burst low-latency service data transmission; the first identification field identifies the duration required for the AP to transmit the temporary or burst low-latency service data.

[0141] In some embodiments, the first identifier is carried in a BA Control field of the Block Ack frame;

[0142] The first identifier is set to a first parameter value, indicating that the TXOP responder does not request the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0143] The first identifier is set to a second parameter value, indicating that the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0144] For example, the BA Control field of the Block Ack frame includes a first identifier. When the first identifier is set to 0, it indicates that the TXOP responding end does not request the TXOP holding end to share part of the transmission time of the first TXOP for low-latency service data transmission; when the first identifier is set to 1, it indicates that the TXOP responding end requests the TXOP holding end to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0145] In some embodiments, when the first identifier is set to the second parameter value, the Block Ack frame includes a TXOP Request Info field, and the first identifier field is carried in the TXOP Request Info field.

[0146] For example, when the first identifier is set to 1, the Block Ack frame further includes a first identification field, and the first identification field is carried in the TXOP Request Info field.

[0147] In some embodiments, as shown in FIG4 , the TXOP Requested Info field may be 2 octets in size, with the first identification field being 9 bits in units of 16 μs (each bit representing 16 μs); the remaining 7 bits may be reserved. The transmission duration indicated by the first identification field is determined by the AP based on the size of temporary or burst low-latency service data in its transmit buffer.

[0148] In step 202, the TXOP holder 102 receives a Block Ack frame.

[0149] In an embodiment of the present disclosure, in a process of sending data to a TXOP responder within a first TXOP, a Block Ack frame sent by the TXOP responder is received; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0150] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0151] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0152] The STA may respond based on the Block Ack frame received from the AP. For example, when the first identifier is set to 0, it indicates that the AP does not request the STA to share part of the transmission time of the first TXOP for low-latency service data transmission, and the STA continues to send data to the AP; when the first identifier is set to 1, it indicates that the AP requests the STA to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0153] Step 203: The first identifier in the Block Ack frame is set to the second parameter value, and the TXOP holder 102 sends a MU-RTS TXS Trigger frame.

[0154] In an embodiment of the present disclosure, the first identifier is set to the second parameter value, and a MU-RTS TXS Trigger frame is sent to the TXOP responder; wherein the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes a device identifier of a target device that shares part of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by the TXOP holder to each of the target devices.

[0155] For example, after receiving a short interframe space (SIFS) of the Block Ack frame, the STA sends a MU-RTS TXS Trigger frame to the AP. The MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes but is not limited to a second identification field and a third identification field. The second identification field is used to identify the device identification of the target device that carries the portion of the transmission time shared by the first TXOP in the User Info field. Optionally, the second identification field can be the media access control (MAC) address of the target AP. The third identification field is used to identify the TXOP duration allocated by the STA to the AP.

[0156] The TXOP duration allocated by the STA to the AP is greater than or equal to the sum of the duration of the AP sending the RTS frame to the receiver of the low-latency service data (STA or P2P AP), the duration of the receiver sending the CTS frame back to the AP, the duration required for the AP to transmit the low-latency service data to the receiver, the duration of the receiver sending the acknowledgement (ACK) frame or Block Ack frame back to the AP, and the duration of the four short frame intervals.

[0157] Among them, the four short frame intervals include a short frame interval between the MU-RTS TXS Trigger frame and the RTS frame, a short frame interval between the RTS frame and the CTS frame, a short frame interval between the CTS frame and the data frame transmitting low-latency service data, and a short frame interval between the data frame transmitting low-latency service data and the receiving end feedback ACK frame or BA frame.

[0158] Step 204: The TXOP responder 101 receives the MU-RTS TXS Trigger frame.

[0159] In the disclosed embodiment, the AP responds based on a received MU-RTS TXS Trigger frame sent by a STA. The MU-RTS TXS Trigger frame includes a second identification field and a third identification field, wherein the second identification field includes a device identification of a target device that shares a portion of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by the TXOP holder to each target device.

[0160] In some embodiments, the device identification in the second identification field does not include the device identification of the TXOP responder, does not respond to the MU-RTS TXS Trigger frame, and receives data sent by the TXOP holder;

[0161] or,

[0162] The device identification in the second identification field includes the device identification of the TXOP responder, and the low-latency service data is transmitted within the transmission time shared by the TXOP holder for the TXOP responder.

[0163] For example, if the device identifier of the TXOP responding end identified in the second identification field (User Info field) in the MU-RTS TXS Trigger frame does not match the AP device identifier, the AP does not respond and remains in the receiving state; if the identification information of the second identification field in the MU-RTS TXS Trigger frame matches the AP device identifier, the AP acts as the temporary holder of the TXOP and sends its cached temporary / burst low-latency service data to the receiving end.

[0164] Step 205: The TXOP responder 101 sends an RTS frame.

[0165] In an embodiment of the present disclosure, transmitting the low-latency service data within the transmission time shared by the TXOP holder for the TXOP responder includes:

[0166] Sending an RTS frame to a receiving end of the low-latency service data; wherein the receiving address of the RTS frame is the address of the receiving end; and the duration of the RTS frame is set to be the sum of the duration of the CTS frame sent by the receiving end, the duration required for the TXOP responder to transmit the low-latency service data, the duration of the ACK frame sent by the receiving end, and the sum of the durations of three short frame intervals;

[0167] Receive the CTS frame sent by the receiving end, and send the low-latency service data to the receiving end.

[0168] For example, after receiving a MU-RTS TXS Trigger frame and after a SIFS interval, the AP sends an RTS frame to the receiving end. The destination address of the RTS is the receiving end address, and the duration (Duration field) of the RTS frame is set to: the duration of the receiving end sending the CTS frame, the duration required for the TXOP responder to transmit the low-latency service data, the duration of the receiving end sending the ACK frame, and the sum of the three short frame intervals.

[0169] Among them, the three short frame intervals include a short frame interval between the RTS frame and the CTS frame, a short frame interval between the CTS frame and the data frame transmitting low-latency service data, and a short frame interval between the data frame transmitting low-latency service data and the receiving end feedback ACK frame or BA frame.

[0170] Step 206: The low-latency service data receiving end 103 receives the RTS frame.

[0171] In the embodiment of the present disclosure, the receiving end receives the RTS frame sent by the AP within the transmission time shared by the STA.

[0172] Step 207: The low-latency service data receiving end 103 sends a CTS frame.

[0173] In the disclosed embodiment, a receiving end sends a CTS frame back to the AP one SIFS after receiving an RTS frame sent by the AP. The CTS frame carries the AP address, and the Duration field of the CTS frame is set to the sum of the duration required for the AP to transmit low-latency service data, the duration for the receiving end to send an ACK frame or Block Ack frame back to the AP, and the sum of the two short frame intervals.

[0174] Among them, the two short frame intervals include a short frame interval between the CTS frame and the data frame transmitting low-latency service data, and a short frame interval between the data frame transmitting low-latency service data and the receiving end feedback ACK frame or BA frame.

[0175] Step 208: The TXOP responder 101 receives the CTS frame.

[0176] The AP receives a CTS frame fed back by the receiving end within the TXOP transmission time allocated by the STA, and determines that the current channel of the receiving end is idle based on the CTS frame.

[0177] Step 209: The TXOP responder 101 sends low-latency service data.

[0178] The AP sends the temporary low-latency service data to the receiving end one SIFS after receiving the CTS sent by the receiving end.

[0179] In step 210 , the low-latency service data receiving end 103 receives the low-latency service data.

[0180] The receiving end receives a data frame including low-latency service data sent by the AP within the TXOP transmission time allocated by the STA.

[0181] In step 211 , the low-latency service data receiving end 103 sends an ACK frame or a Block ACK frame.

[0182] After receiving the data frame including the low-latency service data sent by the AP, the receiving end sends an ACK frame or a Block ACK frame in response.

[0183] In step 212, the TXOP responder 101 receives an ACK frame or a Block ACK frame.

[0184] The AP receives the ACK frame or Block ACK frame fed back by the receiving end. The STA stops data transmission during the TXOP transmission time shared by the STA. When the TXOP transmission time shared by the STA ends, the STA becomes the holder of the remaining TXOP and can send data to the AP during the remaining TXOP.

[0185] The communication method provided in the embodiments of the present disclosure is also applicable to two STAs engaged in P2P communication. When the TXOP responder (P2P STA) caches temporary low-latency services destined for another communication device (AP or STA), the TXOP holder (STA) can use the aforementioned communication method to share a portion of its TXOP transmission time with the P2P STA. The P2P STA can then transmit low-latency service data to the AP or other STA within the shared TXOP transmission time.

[0186] The communication method provided by the embodiments of the present disclosure can effectively handle sudden low-latency services and ensure the timely and efficient transmission of low-latency services. Furthermore, the communication method provided by the embodiments of the present disclosure can be applied not only to STAs sharing part of their TXOP with APs, but also to P2P scenarios, where it can share part of its TXOP with P2P sites that require it, enabling them to transmit low-latency communication services in a timely and efficient manner.

[0187] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 201 can be implemented as an independent embodiment, step 202 can be implemented as an independent embodiment, step 203 can be implemented as an independent embodiment, step 204 can be implemented as an independent embodiment, step 209 can be implemented as an independent embodiment, and step 210 can be implemented as an independent embodiment; the combination of step 201 and step 202 can be implemented as an independent embodiment, the combination of step 202 and step 203 can be implemented as an independent embodiment, the combination of step 203 and step 204 can be implemented as an independent embodiment, the combination of step 204 and step 209 can be implemented as an independent embodiment, and the combination of step 209 and step 210 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0188] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0189] As an example, referring to Figure 3, the Basic Service Set (BSS) in the figure includes a TXOP responder (which can be an AP or a P2P AP, and is described below using the AP as an example), a TXOP holder (which can be STA1 or a P2P STA, and is described below using STA1 as an example), a low-latency service data receiver (which can be STA2 or a PAP AP, and is described below using STA2 as an example), and other site devices (Other STAs).

[0190] FIG3 shows an optional implementation of the embodiment of the present disclosure, including the following steps:

[0191] Step 301: STA1 sends an RTS frame to the AP.

[0192] In actual communication scenarios, STAs and APs negotiate to communicate during specific service hours and remain dormant during other times to conserve device energy. To ensure low-latency service communication, the Restricted Target Wake Time (R-TWT) protocol is defined. Low-latency service communication occurs within the R-TWT service period (SP), while other communication services are suspended or postponed during this period.

[0193] Among them, for deterministic or periodic low-latency services, the R-TWT mechanism can effectively ensure the timely transmission of low-latency communication services. However, when the AP or STA faces some temporary or sudden low-latency services, the R-TWT mechanism is no longer applicable. Among them, when the AP is the holder of the TXOP and is sending data to its associated STA1, if STA1 has uplink or P2P low-latency communication services cached on the end, the AP can trigger the Transmission Opportunity Sharing (TXS) process to allocate part of the time in its reserved TXOP to STA1, and STA1 uses the allocated TXOP to send the low-latency service to the AP or the STA corresponding to the P2P link in a timely manner.

[0194] In the embodiment of the present disclosure, when the TXOP holder is STA1, STA1 sends an RTS frame to the AP after obtaining the TXOP transmission opportunity. The RTS frame is used to reserve the right to use the communication medium for the AP to use.

[0195] It should be noted that, during the entire TXOP, the channel of Other STA is always in the busy state (NAV Busy)

[0196] Step 302: The AP sends a CTS frame to STA1.

[0197] In the embodiment of the present disclosure, after receiving the RTS frame, the AP feeds back a CTS frame to STA1 to confirm the transmission of STA1.

[0198] Step 303: STA1 sends data to the AP.

[0199] In the embodiment of the present disclosure, after STA1 receives the CTS frame, it confirms that the CTS is the feedback of the RTS frame it previously sent, and the TXOP holding end channel is idle, then STA1 sends data to the AP.

[0200] Step 304: The AP transmits low-latency service data to STA2.

[0201] In the embodiment of the present disclosure, the AP, in response to data sent by STA1 within the first TXOP, replies to STA1 with a Block Ack frame; wherein the Block Ack frame includes at least one of the first identifier and the first identification field;

[0202] The first identifier identifies whether the AP requests STA1 to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0203] The first identification field identifies the duration required for the AP to transmit low-latency service data.

[0204] In the embodiment of the present disclosure, when the AP is receiving uplink data sent by STA1 and has temporary or burst low-latency service data to transmit (at this time, the STA2 channel is busy), the AP carries a first identifier and a first identification field in the Block Ack frame in response to STA1. The first identifier identifies whether the AP requests STA1 to share part of the transmission time of the TXOP for temporary or burst low-latency service data transmission; the first identification field identifies the duration required for the AP to transmit the temporary or burst low-latency service data.

[0205] In some embodiments, the first identifier is carried in a BA Control field of the Block Ack frame;

[0206] The first identifier is set to a first parameter value, indicating that the AP does not request STA1 to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0207] The first identifier is set to a second parameter value, indicating that the AP requests STA1 to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0208] For example, the BA Control field of the Block Ack frame includes a first identifier. When the first identifier is set to 0, it indicates that the AP does not request STA1 to share part of the transmission time of the first TXOP for low-latency service data transmission; when the first identifier is set to 1, it indicates that the AP requests STA1 to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0209] In some embodiments, when the first identifier is set to the second parameter value, the Block Ack frame includes a TXOP Request Info field, and the first identifier field is carried in the TXOP Request Info field.

[0210] For example, when the first identifier is set to 1, the Block Ack frame further includes a first identification field, and the first identification field is carried in the TXOP Request Info field.

[0211] In some embodiments, the TXOP Requested Info field may be 2 octets in size, with the first identification field consisting of 9 bits, expressed in units of 16 μs (each bit representing 16 μs); the remaining 7 bits may be reserved. The transmission duration indicated by the first identification field is determined by the AP based on the size of temporary or burst low-latency service data in its transmit buffer.

[0212] Step 305: The AP sends a Block Ack frame to STA1.

[0213] In the embodiment of the present disclosure, after setting the first identifier and the first identification field in the Block Ack frame, the AP sends the Block Ack frame to STA1.

[0214] Step 306: STA1 sends a MU-RTS TXS Trigger frame to the AP.

[0215] STA1 may respond based on the Block Ack frame received from the AP. For example, when the first identifier is set to 0, it indicates that the AP does not request STA1 to share part of the transmission time of the first TXOP for low-latency service data transmission, and STA1 continues to send data to the AP; when the first identifier is set to 1, it indicates that the AP requests STA1 to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0216] In an embodiment of the present disclosure, the first identifier is set to the second parameter value, and a MU-RTS TXS Trigger frame is sent to the AP; wherein the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes a device identifier of a target device that shares part of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by STA1 to each of the target devices.

[0217] For example, after receiving a short frame interval of a Block Ack frame, STA1 sends a MU-RTS TXS Trigger frame to the AP. The MU-RTS TXS Trigger frame includes a User Info field, which includes but is not limited to a second identification field and a third identification field. The second identification field is used to identify the device identification of the target device that carries the portion of the transmission time shared by the first TXOP in the User Info field. Optionally, the second identification field can be the MAC address of the target AP. The third identification field is used to identify the TXOP duration allocated by STA1 to the AP.

[0218] The TXOP duration allocated by STA1 to the AP is greater than or equal to the duration of the AP sending the RTS frame to the receiver (STA2) of the low-latency service data, the duration of the receiver feeding back the CTS frame to the AP, the duration required for the AP to transmit the low-latency service data to STA2, the duration of STA2 feeding back the ACK frame or Block Ack frame to the AP, and the sum of the four short frame intervals.

[0219] Among them, the four short frame intervals include a short frame interval between the MU-RTS TXS Trigger frame and the RTS frame, a short frame interval between the RTS frame and the CTS frame, a short frame interval between the CTS frame and the data frame transmitting low-latency service data, and a short frame interval between the data frame transmitting low-latency service data and the STA2 feedback ACK frame or BA frame.

[0220] Step 307: The AP sends an RTS frame to STA2 within the TXOP transmission time shared by STA1.

[0221] In the embodiment of the present disclosure, transmitting the low-latency service data within the transmission time shared by STA1 for the AP includes:

[0222] Send an RTS frame to STA2; wherein the receiving address of the RTS frame is the address of STA2; the duration of the RTS frame is set to: the duration of STA2 sending the CTS frame, the duration required for the AP to transmit the low-latency service data, the duration of STA2 sending the ACK frame, and the sum of the three short frame intervals;

[0223] Receive the CTS frame sent by the receiving end, and send the low-latency service data to the receiving end.

[0224] For example, after receiving the MU-RTS TXS Trigger frame and after a SIFS interval, the AP sends an RTS frame to STA2. The destination address of the RTS is STA2's address, and the duration (Duration field) of the RTS frame is set to: the duration of STA2 sending the CTS frame, the duration required for the AP to transmit the low-latency service data, the duration of STA2 sending the ACK frame, and the sum of the three short frame intervals.

[0225] Among them, the three short frame intervals include a short frame interval between the RTS frame and the CTS frame, a short frame interval between the CTS frame and the data frame transmitting low-latency service data, and a short frame interval between the data frame transmitting low-latency service data and the STA2 feedback ACK frame or BA frame.

[0226] In the embodiment of the present disclosure, after STA1 shares the TXOP transmission time, STA2 may reset the channel state so that STA2 and the AP can communicate normally within the TXOP transmission time shared by STA1.

[0227] Step 308: STA2 sends a CTS frame to the AP within the TXOP transmission time shared by STA1.

[0228] In the disclosed embodiment, STA2 sends a CTS frame back to the AP one SIFS after receiving the RTS frame sent by the AP. The CTS frame carries the AP address, and the Duration field of the CTS frame is set to the sum of the duration required for the AP to transmit low-latency service data, the duration of STA2's ACK frame or Block Ack frame feedback to the AP, and the sum of the two short frame intervals.

[0229] Among them, the two short frame intervals include a short frame interval between the CTS frame and the data frame transmitting low-latency service data, and a short frame interval between the data frame transmitting low-latency service data and the STA2 feedback ACK frame or BA frame.

[0230] Step 309: The AP sends low-latency service data to STA2 within the TXOP transmission time shared by STA1.

[0231] Among them, the AP sends the temporary low-latency service data DATA to STA2 after receiving a SIFS of the CTS sent by STA2.

[0232] In step 310, STA2 sends an ACK frame or a Block ACK frame to the AP within the TXOP transmission time shared by STA1.

[0233] After receiving the data frame including the low-latency service data sent by the AP, STA2 sends an ACK frame or a Block ACK frame in response.

[0234] Optionally, after the AP receives the ACK frame or Block ACK frame sent by STA2, the low-latency service data transmission ends. If there is still remaining time in the TXOP, STA1 holds the remaining TXOP and can send data to the AP within the remaining TXOP.

[0235] As can be seen, in this embodiment of the disclosure, when STA1, as the TXOP holder, is transmitting uplink data to its associated AP, and the AP needs to transmit other low-latency services to STA2, the AP can send the TXOP request in a response frame. After receiving this request, STA1, as the TXOP holder, can share the reserved TXOP with the AP, allowing it to transmit low-latency services within the shared TXOP. This embodiment of the disclosure can effectively address sudden low-latency services, further improve the low-latency transmission mechanism, and reduce the transmission delay of low-latency communication services.

[0236] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0237] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0238] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0239] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0240] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0241] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0242] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 305 may be implemented as an independent embodiment, step 306 may be implemented as an independent embodiment, and step 309 may be implemented as an independent embodiment; the combination of step 304 and step 305 may be implemented as an independent embodiment, the combination of step 305 and step 306 may be implemented as an independent embodiment, and the combination of step 309 and step 310 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0243] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 .

[0244] FIG5 is a flowchart of a communication method according to an embodiment of the present disclosure.

[0245] As shown in FIG5 , the above method may be applied to the TXOP responder 101. The above method includes:

[0246] Step 501: In a first TXOP, in response to data sent by a TXOP holding end, reply a Block Ack frame to the TXOP holding end; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0247] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0248] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0249] Step 502: The first identifier is set to the first parameter value, and data sent by the TXOP holder is received;

[0250] or,

[0251] The first identifier is set to the second parameter value, and a MU-RTS TXS Trigger frame sent by the TXOP holder is received; wherein the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes a device identifier of a target device that shares part of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by the TXOP holder to each of the target devices.

[0252] Step 503: Send an RTS frame to the receiving end of the low-latency service data; wherein the receiving address of the RTS frame is the address of the receiving end; the duration of the RTS frame is set to: the duration of the receiving end sending the CTS frame, the duration required for the TXOP responder to transmit the low-latency service data, the duration of the receiving end sending the ACK frame, and the sum of the three short frame intervals.

[0253] Step 504: Receive the CTS frame sent by the receiving end.

[0254] Step 505: Send the low-latency service data to the receiving end.

[0255] Step 506: Receive the ACK frame or Block ACK frame sent by the receiving end.

[0256] Optionally, in the embodiment of the present disclosure, the first identifier is carried in the BA Control field of the Block Ack frame;

[0257] The first identifier is set to a first parameter value, indicating that the TXOP responder does not request the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0258] The first identifier is set to a second parameter value, indicating that the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission.

[0259] Optionally, in an embodiment of the present disclosure, when the first identifier is set to the second parameter value, the Block Ack frame includes a TXOP Request Info field, and the first identification field is carried in the TXOP Request Info field.

[0260] Optionally, in the embodiment of the present disclosure, the device identifier in the second identifier field does not include the device identifier of the TXOP responder, does not respond to the MU-RTS TXS Trigger frame, and receives data sent by the TXOP holder;

[0261] or,

[0262] The device identification in the second identification field includes the device identification of the TXOP responder, and the low-latency service data is transmitted within the transmission time shared by the TXOP holder for the TXOP responder.

[0263] Optionally, in the embodiment of the present disclosure, the TXOP holding end includes a station device, and the TXOP responding end includes an access point device;

[0264] or,

[0265] The TXOP holding end and the TXOP responding end are respectively two TDLS devices that have established a TDLS link.

[0266] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 501 can be implemented as an independent embodiment, step 502 can be implemented as an independent embodiment, step 503 can be implemented as an independent embodiment, and step 505 can be implemented as an independent embodiment; the combination of step 501 and step 502 can be implemented as an independent embodiment, the combination of step 502 and step 503 can be implemented as an independent embodiment, and the combination of step 505 and step 506 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0267] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 5 .

[0268] FIG6 is a second flowchart of a communication method according to an embodiment of the present disclosure.

[0269] As shown in FIG6 , the above method may be applied to the TXOP holding terminal 102. The above method includes:

[0270] Step 601, in a process of sending data to a TXOP responder within a first TXOP, receiving a Block Ack frame sent by the TXOP responder; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0271] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0272] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0273] Step 602: The first identifier is set to the first parameter value, and data is sent to the TXOP responder.

[0274] or,

[0275] The first identifier is set to the second parameter value, and a MU-RTS TXS Trigger frame is sent to the TXOP responder; wherein the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes a device identifier of a target device that shares part of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by the TXOP holder to each of the target devices.

[0276] Optionally, in the embodiment of the present disclosure, the first identifier is carried in the BA Control field of the Block Ack frame;

[0277] The first identifier is set to a first parameter value, indicating that the TXOP responder does not request to use part of the transmission time of the first TXOP shared by the TXOP holder for low-latency service data transmission;

[0278] The first identifier is set to a second parameter value, indicating that the TXOP responder requests to use a portion of the transmission time of the first TXOP shared by the TXOP holder for low-latency service data transmission.

[0279] Optionally, in an embodiment of the present disclosure, when the first identifier is set to the second parameter value, the Block Ack frame includes a TXOP Request Info field, and the first identification field is carried in the TXOP Request Info field.

[0280] Optionally, in the embodiment of the present disclosure, within the transmission time allocated by the TXOP holder to the target device, the TXOP holder sends data only when receiving a data sending request from the target device and responding to the data sending request.

[0281] Optionally, in the embodiment of the present disclosure, the TXOP holding end includes an access point device, and the TXOP responding end includes a station device;

[0282] or,

[0283] The TXOP holding end and the TXOP responding end are respectively two TDLS devices that have established a TDLS link.

[0284] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 601 may be implemented as an independent embodiment, step 602 may be implemented as an independent embodiment, or the combination of step 601 and step 602 may be implemented as an independent embodiment.

[0285] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 6 .

[0286] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0287] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0288] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0289] FIG7 is a schematic diagram of the structure of a TXOP responder proposed in an embodiment of the present disclosure. As shown in FIG7 , a TXOP responder 700 may include: a first processing module 701 .

[0290] In some embodiments, the first processing module 701 is configured to reply a Block Ack frame to the TXOP holding end in response to data sent by the TXOP holding end within the first TXOP; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0291] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0292] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0293] Optionally, the first processing module 701 is configured to execute at least one of the communication steps (eg, step 201, step 305, step 501, but not limited thereto) executed by the TXOP responder 101 in any of the above methods, which will not be described in detail here.

[0294] FIG8 is a schematic diagram of the structure of a TXOP holding end proposed in an embodiment of the present disclosure. As shown in FIG8 , a TXOP holding end 800 may include: a second processing module 801 .

[0295] In some embodiments, the second processing module 801 is configured to, during a process of sending data to a TXOP responder within a first TXOP, receive a Block Ack frame sent by the TXOP responder; wherein the Block Ack frame includes at least one of a first identifier and a first identification field;

[0296] The first identifier identifies whether the TXOP responder requests the TXOP holder to share part of the transmission time of the first TXOP for low-latency service data transmission;

[0297] The first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

[0298] Optionally, the second processing module 801 is configured to execute at least one of the communication steps (eg, step 202 and step 601 , but not limited thereto) executed by the TXOP holder 102 in any of the above methods, which will not be described in detail here.

[0299] Figure 9 is a schematic diagram of the structure of a terminal 900 (e.g., user equipment) proposed in an embodiment of the present disclosure. Terminal 900 can be a chip, chip system, or processor that supports a network device implementing any of the above methods, or a chip, chip system, or processor that supports a terminal implementing any of the above methods. Terminal 900 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0300] As shown in Figure 9, terminal 900 includes one or more processors 901. Processor 901 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Terminal 900 is used to perform any of the above methods.

[0301] In some embodiments, the terminal 900 further includes one or more memories 902 for storing instructions. Optionally, all or part of the memories 902 may be located outside the terminal 900.

[0302] In some embodiments, the terminal 900 further includes one or more transceivers 904. When the terminal 900 includes one or more transceivers 904, the transceiver 904 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 201, step 202, step 203, step 204, step 205, step 206, step 207, step 208, step 209, step 210, step 211, step 212, step 301, step 302, step 303, step 305, step 306, step 307, step 308, step 309, step 310, step 501, step 502, step 503, step 504, step 505, step 506, step 601, step 602, but not limited thereto), and the processor 901 performs other steps (for example, step 304).

[0303] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0304] In some embodiments, terminal 900 may include one or more interface circuits 903. Optionally, interface circuit 903 is connected to memory 902. Interface circuit 903 may be configured to receive signals from memory 902 or other devices, and may be configured to send signals to memory 902 or other devices. For example, interface circuit 903 may read instructions stored in memory 902 and send the instructions to processor 901.

[0305] The terminal 900 described in the above embodiment may be a communication device such as a user device, but the scope of the terminal 900 described in the present disclosure is not limited thereto, and the structure of the terminal 900 may not be limited by FIG. 9 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0306] FIG10 is a schematic diagram of the structure of a chip 1000 according to an embodiment of the present disclosure. If the terminal 900 is a chip or a chip system, reference may be made to the schematic diagram of the structure of the chip 1000 shown in FIG10 , but the present disclosure is not limited thereto.

[0307] The chip 1000 includes one or more processors 1001 , and the chip 1000 is configured to execute any of the above methods.

[0308] In some embodiments, chip 1000 further includes one or more 1003. Optionally, interface circuit 1003 is connected to memory 1002. Interface circuit 1003 can be used to receive signals from memory 1002 or other devices, and interface circuit 1003 can be used to send signals to memory 1002 or other devices. For example, interface circuit 1003 can read instructions stored in memory 1002 and send the instructions to processor 1001.

[0309] In some embodiments, the interface circuit 1003 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step 201, step 202, step 203, step 204, step 205, step 206, step 207, step 208, step 209, step 210, step 211, step 212, step 301, step 302, step 303, step 305, step 306, step 307, step 308, step 309, step 310, step 501, step 502, step 503, step 504, step 505, step 506, step 601, step 602, but not limited to this), and the processor 1001 executes other steps (for example, step 304).

[0310] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0311] In some embodiments, the chip 1000 further includes one or more memories 1002 for storing instructions. Alternatively, all or part of the memory 1002 may be external to the chip 1000.

[0312] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the terminal 900, the terminal 900 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0313] The present disclosure also provides a program product, which, when executed by the terminal 900, enables the terminal 900 to perform any of the above methods. Optionally, the program product is a computer program product.

[0314] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, applied to a TXOP responder, characterized in that the method includes: Within a first transmission opportunity (TXOP), in response to data sent by the TXOP holder, sending a Block Ack frame to the TXOP holder; wherein, the Block Ack frame includes at least one of a first identifier and a first identification field; The first identifier indicates whether the TXOP responder requests the TXOP holder to share a part of the transmission time of the first TXOP for low-latency service data transmission; The first identification field indicates the duration required for the TXOP responder to transmit the low-latency service data.

2. The communication method according to claim 1, characterized in that The first identifier is carried in the Block Ack Control (BA Control) field of the Block Ack frame; The first identifier is set to a first parameter value, indicating that the TXOP responder does not request the TXOP holder to share a part of the transmission time of the first TXOP for low-latency service data transmission; The first identifier is set to a second parameter value, indicating that the TXOP responder requests the TXOP holder to share a part of the transmission time of the first TXOP for low-latency service data transmission.

3. The communication method according to claim 2, characterized in that When the first identifier is set to the second parameter value, the Block Ack frame includes a Transmission Opportunity Request Information (TXOP Request Info) field, and the first identification field is carried in the TXOP Request Info field.

4. The communication method according to claim 2, characterized in that After sending the Block Ack frame to the TXOP holder, the method further includes: Setting the first identifier to the first parameter value and receiving data sent by the TXOP holder; Or, Setting the first identifier to the second parameter value and receiving a Multi-User Request to Send Transmission Opportunity Sharing Trigger (MU-RTS TXS Trigger) frame sent by the TXOP holder; wherein, the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes the device identifier of the target device that shares a part of the transmission time of the first TXOP, and the third identification field indicates the transmission time allocated by the TXOP holder for each target device.

5. The communication method according to claim 4, characterized in that After receiving the MU-RTS TXS Trigger frame sent by the TXOP holder, the method includes: If the device identifier in the second identification field does not include the device identifier of the TXOP responder, not responding to the MU-RTS TXS Trigger frame and receiving data sent by the TXOP holder; Or, The device identifier in the second identifier field includes the device identifier of the TXOP responder. During the transmission time shared by the TXOP holder for the TXOP responder, the low-latency service data is transmitted.

6. The communication method according to claim 5, wherein, during the transmission time shared by the TXOP holder for the TXOP responder, transmitting the low-latency service data includes: sending a Request to Send (RTS) frame to the receiver of the low-latency service data; wherein, the destination address of the RTS frame is the address of the receiver; the duration of the RTS frame is set to be the sum of the duration for the receiver to send a Clear to Send (CTS) frame, the duration required for the TXOP responder to transmit the low-latency service data, the duration for the receiver to send an Acknowledgment (ACK) frame, and the duration of three short frame intervals; receiving the CTS frame sent by the receiver, and sending the low-latency service data to the receiver.

7. The communication method according to any one of claims 1 to 6, wherein, the TXOP holder includes a station device, and the TXOP responder includes an access point device; or, the TXOP holder and the TXOP responder are respectively two TDLS devices that have established a direct connection through a channel to establish a TDLS link.

8. A communication method applied to a TXOP holder, wherein, the method includes: during a first Transmission Opportunity (TXOP), in the process of sending data to a TXOP responder, receiving a Block Ack frame sent by the TXOP responder; wherein, the Block Ack frame includes at least one of a first identifier and a first identifier field; the first identifier indicates whether the TXOP responder requests the TXOP holder to share a part of the transmission time of the first TXOP for transmitting low-latency service data; the first identifier field indicates the duration required for the TXOP responder to transmit the low-latency service data.

9. The communication method according to claim 8, wherein, the first identifier is carried in the Block Ack Control (BA Control) field of the Block Ack frame; the first identifier is set to a first parameter value, indicating that the TXOP responder does not request to use the part of the transmission time of the first TXOP shared by the TXOP holder for transmitting low-latency service data; the first identifier is set to a second parameter value, indicating that the TXOP responder requests to use the part of the transmission time of the first TXOP shared by the TXOP holder for transmitting low-latency service data.

10. The communication method according to claim 9, wherein, when the first identifier is set to the second parameter value, the Block Ack frame includes a TXOP Request Info field, and the first identifier field is carried in the TXOP Request Info field. ​ 11. The communication method according to claim 9, wherein, after receiving the Block Ack frame sent by the TXOP responder, the method further includes: setting the first identifier to the first parameter value and sending data to the TXOP responder; or setting the first identifier to the second parameter value and sending a multi-user request to send transmission opportunity sharing trigger (MU-RTS TXS Trigger) frame to the TXOP responder; wherein, the MU-RTS TXS Trigger frame includes a second identification field and a third identification field, the second identification field includes the device identifier of the target device that shares a part of the transmission time of the first TXOP, and the third identification field identifies the transmission time allocated by the TXOP holder for each target device.

12. The communication method according to claim 11, wherein, within the transmission time allocated by the TXOP holder for the target device, the TXOP holder only sends data when receiving a data transmission request from the target device and responding to the data transmission request.

13. The communication method according to any one of claims 8 to 12, wherein, the TXOP holder includes an access point device, and the TXOP responder includes a station device; or the TXOP holder and the TXOP responder are respectively two TDLS devices that have established a TDLS link through a direct connection of a channel.

14. A communication device, the communication device is a TXOP responder, wherein, the TXOP responder includes: a first processing module, configured to, within a first TXOP, in response to data sent by a TXOP holder, reply a Block Ack frame to the TXOP holder; wherein, at least one of a first identifier and a first identification field is included in the Block Ack frame; the first identifier identifies whether the TXOP responder requests the TXOP holder to share a part of the transmission time of the first TXOP for low-latency service data transmission; the first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

15. A communication device, the communication device is a TXOP holder, wherein, the TXOP holder includes: a second processing module, configured to, within a first TXOP, in the process of sending data to a TXOP responder, receive the Block Ack frame sent by the TXOP responder; wherein, at least one of a first identifier and a first identification field is included in the Block Ack frame; the first identifier identifies whether the TXOP responder requests the TXOP holder to share a part of the transmission time of the first TXOP for low-latency service data transmission for it; the first identification field identifies the duration required for the TXOP responder to transmit the low-latency service data.

16. A communication device, the communication device is a TXOP responder, wherein, includes: One or more processors; Wherein, the TXOP response end is used to execute the communication method described in any one of claims 1 to 7.

17. A communication device, which is a TXOP holder, Characterized in that, It includes: One or more processors; Wherein, the TXOP holder is used to execute the communication method described in any one of claims 8 to 13.

18. A communication system, Characterized in that, It includes a TXOP response end and a TXOP holder; wherein, the TXOP response end is configured to implement the communication method described in any one of claims 1 to 7, and the TXOP holder is configured to implement the communication method described in any one of claims 8 to 13.

19. A storage medium, which stores instructions, Characterized in that, When the instructions run on the communication device, the communication device is caused to execute the communication method described in any one of claims 1 to 7, or execute the communication method described in any one of claims 8 to 13.

Images