Communication method and apparatus

Abstract

Provided in the embodiments of the present application are a communication method and an apparatus. The method comprises: a first apparatus sending first information to a second apparatus, the first information being used for requesting establishment of a preemptive session; then receiving second information from the second apparatus, the second information being used for indicating that the preemptive session has been successfully established; on the basis of the preemptive session, the first apparatus receiving at least one first PPDU sent by the second apparatus, the at least one first PPDU carrying data of a first service, and the length of the first PPDU being less than a first preset value; and / or, on the basis of the preemptive session, the first apparatus sending at least one second PPDU to the second apparatus, the at least one second PPDU carrying data of a second service, and the length of the second PPDU being less than a second preset value. In this method, by means of the established preemptive session, the first apparatus and the second apparatus can transmit the PPDUs carrying the service data and having lengths less than corresponding preset values, thereby ensuring the transmission performance of the services.

Description

A communication method and apparatus

[0001] Cross-reference to Related Applications

[0002] This application claims priority to the Chinese Patent Application No. 202411012206.6, filed on July 24, 2024, and entitled “A communication method and apparatus”, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the field of communication technology, and in particular to a communication method and apparatus. BACKGROUND

[0004] Low latency is an important research target of the wireless local area network (WLAN) standard. Although current technologies can improve the support for low latency services, the next generation of WLAN standards, such as ultra high reliability (UHR), have higher requirements for low latency, i.e., ultra low latency of less than a few milliseconds. There is a demand for such ultra low latency in some practical application scenarios such as virtual reality (VR), augmented reality (AR), industrial internet of things (IoT), remote medical treatment, etc., and the current WLAN standard cannot currently meet these requirements.

[0005] To this end, a preemption transmission capable of solving ultra low latency is proposed. The principle is to interrupt the transmission of non-low latency services that are currently being transmitted, and to give priority to the transmission of low latency services. After the transmission of low latency services is completed, the transmission of non-low latency services is resumed. The low latency services and non-low latency services described herein are relative.

[0006] In a pre-emption transmission scenario, because different data frames have different quality of service (QoS) requirements, a sending end splits a data frame to be sent into multiple shorter physical layer protocol data units (PPDUs) for sending, and an receiving end feeds back an acknowledgement frame after receiving each PPDU. If the receiving end has data of a low-latency service to send, the receiving end can carry indication information in the acknowledgement frame to inform the sending end, and the sending end then gives the transmission opportunity to the receiving end to send data. However, no technology currently proposes to use the pre-emption session establishment process to guarantee the communication quality of the above service, such as how to determine which service data the sending end performs splitting on and how to split through the pre-emption session establishment process to guarantee the communication quality of the subsequent service. SUMMARY

[0007] Embodiments of the present application provide a communication method and device, which can effectively use the pre-emption session establishment process to guarantee the communication quality of the subsequent service.

[0008] In a first aspect, the present application provides a communication method, which can be applied to a first device, or a component (for example, a processor, a chip, or a chip system, etc.) of the first device, or a logic node, a logic module, or software capable of realizing all or part of the functions of the first device, or a device used in conjunction with the first device. Taking the case where the method is applied to the first device as an example, the method includes: the first device sends first information to a second device, the first information being used to request to establish a pre-emption session; the first device receives second information from the second device, the second information being used to indicate that the pre-emption session is successfully established; the first device receives at least one first physical layer protocol data unit (PPDU) sent by the second device based on the pre-emption session; the at least one first PPDU carries data of a first service, and the length of the first PPDU is less than a first preset value; and / or the first device sends at least one second physical layer protocol data unit (PPDU) to the second device based on the pre-emption session; the at least one second PPDU carries data of a second service, and the length of the second PPDU is less than a second preset value.

[0009] In the embodiments of the present application, the first device is taken as a non-access point, and the second device is taken as an access point as an example to introduce the solutions of the embodiments of the present application.

[0010] In the solution of the present application, the first device and the second device can transmit at least one first PPDU carrying first service data and / or transmit at least one second PPDU carrying second service data through the established preemption session, and the length of each first PPDU is less than the maximum length of the first PPDU (i.e., the first preset value), and the length of each second PPDU is less than the maximum length of the second PPDU (i.e., the second preset value), so that the transmission performance / communication performance (such as transmission rate, reliability, etc.) of the first service and / or the second service can be effectively guaranteed.

[0011] In a possible implementation, the first information includes first indication information and / or second indication information; the first indication information indicates service identification information corresponding to the first service, and the second indication information indicates service identification information corresponding to the second service. Through this implementation, the second device can effectively obtain the service identification information corresponding to the first service and / or the service identification information corresponding to the second service, and then through these service identification information, it can effectively determine which services belong to the first service and / or the second service.

[0012] In a possible implementation, the first information includes third indication information and / or fourth indication information; the third indication information indicates service identification information corresponding to a third service, and the fourth indication information indicates service identification information corresponding to a fourth service, the first service is a service other than the third service, and the second service is a service other than the fourth service. Through this implementation, the second device can effectively obtain the service identification information corresponding to the third service and / or the service identification information corresponding to the fourth service, and through these service identification information, it can effectively determine which services belong to the third service and / or the fourth service, and then indirectly and effectively determine which services belong to the first service and / or the second service.

[0013] In the embodiments of the present application, the third service and the fourth service can refer to low-latency services. The transmission direction of the third service and the fourth service can not be limited; for example, the third service can refer to uplink low-latency services, and the fourth service can refer to downlink low-latency services; or the third service can refer to downlink low-latency services, and the fourth service can refer to uplink low-latency services. In the present application, the first service is a service other than the third service, and the second service is a service other than the fourth service, so the first service and the second service can refer to non-low-latency services, and the transmission direction of the first service and the second service can also not be limited.

[0014] It should be noted that, in the present application, the first device is taken as a non-access point (Non-AP) and the second device is taken as an access point (AP) as an example to introduce the embodiment of the present application. The second device sends data of a first service to the first device, and the first device sends data of a second service to the second device. Therefore, the first service can be used to represent a downlink non-low-latency service, and the second service can be used to represent an uplink non-low-latency service.

[0015] In the embodiment of the present application, the service identification information can be, but is not limited to, a service identification TID list and / or a service identification TID bitmap. The TID list includes at least one TID, and the TID bitmap includes at least one bit, which is used to represent the at least one TID.

[0016] In a possible implementation, the first information further includes fifth indication information. The fifth indication information indicates one or more of the following: a first preset value, a second preset value.

[0017] Through the implementation, the second device can effectively obtain the maximum length of the first PPDU corresponding to the first service (or the maximum threshold of the first PPDU) and / or the maximum length of the second PPDU corresponding to the second service (or the maximum threshold of the second PPDU).

[0018] In a possible implementation, the first information further includes sixth indication information. The sixth indication information indicates whether seventh indication information is allowed to be carried in acknowledgement information of the at least one second PPDU (here, the acknowledgement information can refer to acknowledgement information of one second PPDU, part of the second PPDU, or all of the second PPDU) after the preemption session is established. The seventh indication information indicates that there is data of a low-latency service to be transmitted between the second device and the third device.

[0019] In the above, the sixth indication information can further indicate whether a TXS mode requested by the following sixth information (the sixth information is used to indicate a TXS mode requested by the second device) is allowed to be set as the second mode.

[0020] Through the implementation, when there is data of a low-latency service to be transmitted between the second device and other devices after the preemption session is established, the second device can effectively inform the first device through the acknowledgement information fed back to the first device.

[0021] In a possible implementation, the second information includes eighth indication information; the eighth indication information indicates whether the ninth indication information is allowed to be carried in the acknowledgement information of the at least one first PPDU (here, the acknowledgement information can refer to the acknowledgement information of one first PPDU, part of the first PPDU, or all the first PPDU) after the establishment of the pre-emption session, and the ninth indication information indicates that there is data of low-latency service to be transmitted between the first device and the third device.

[0022] In the above, the eighth indication information can further indicate whether the TXS mode requested by the fifth information (the fifth information is used to indicate the TXS mode requested by the first device) is allowed to be set as the second mode.

[0023] Through the implementation, the first device can effectively inform the second device of the existence of data of low-latency service to be transmitted between the first device and the second device through the acknowledgement information fed back to the second device after the establishment of the pre-emption session.

[0024] In a possible implementation, the method can further include: after receiving the at least one first PPDU sent by the second device, the first device sends first acknowledgement information of the at least one first PPDU to the second device, and the first acknowledgement information carries third information used to indicate a time length required by the first device to transmit data of low-latency service; and / or after sending the at least one second PPDU to the second device, the first device receives second acknowledgement information of the at least one second PPDU sent by the second device, and the second acknowledgement information carries fourth information used to indicate a time length required by the second device to transmit data of low-latency service.

[0025] Through the implementation, when the first device and / or the second device has data of low-latency service to be transmitted, the first device and / or the second device can effectively inform the data receiving end of a time length required by the first device and / or the second device to transmit data of low-latency service, which is equivalent to indicating or implying to the data receiving end that there is data of low-latency service to be transmitted. The first device and the second device can serve as data receiving ends of each other, for example, the first device transmits data to the second device, and the second device is the data receiving end of the first device; or the second device transmits data to the first device, and the first device is the data receiving end of the second device.

[0026] In a possible implementation, the first confirmation information further includes fifth information, where the fifth information indicates that, when the TXS mode requested by the first device is the first mode, the first device has data of low-latency service to be sent to the second device; the fifth information indicates that, when the TXS mode requested by the first device is the second mode, the first device has data of low-latency service to be sent to the second device and / or the third device; and / or the second confirmation information further includes sixth information, where the sixth information indicates that, when the TXS mode requested by the second device is the first mode, the second device has data of low-latency service to be sent to the first device; the sixth information indicates that, when the TXS mode requested by the second device is the second mode, the second device has data of low-latency service to be sent to the first device and / or the third device.

[0027] In the above, the fifth information can also be used to indicate the TXS mode requested by the first device, and the sixth information can also be used to indicate the TXS mode requested by the second device.

[0028] For example, the first confirmation information can be a first multi-user block acknowledgement (MBA) frame, the first MBA frame includes first association identifier (AID) traffic identifier (TID) information, and the first AID TID information includes the third information and / or the fifth information; and / or the second confirmation information can be a second multi-user block acknowledgement (MBA) frame, the second MBA frame includes second AID TID information, and the second AID TID information includes the fourth information and / or the sixth information.

[0029] In the embodiments of the present application, the value of the association identifier in the first AID TID information and / or the second AID TID information can be a third preset value. For example, the first AID TID information and / or the second AID TID information is Per AID TID information, the Per AID TID information includes an AID11 field, and the value of the AID11 field is an integer value between 2008 and 2044, or is 2046 or 2047.

[0030] Through the implementation, the first device and / or the second device can effectively inform the data receiving end (the first device and the second device can be used as the data receiving end of each other) of the TXS mode requested by the first device and / or the second device.

[0031] In a possible implementation, the method can further include: receiving, by the first device, a first trigger frame sent by the second device, where the first trigger frame is used to trigger the first device to send, to the second device, a second PPDU corresponding to a second service, and a length of the second PPDU is less than a second preset value. Optionally, the implementation can be performed before the first device sends, to the second device, the second PPDU corresponding to the second service.

[0032] By the implementation, the first device can send the second PPDU corresponding to the second service to the second device, and the length of the second PPDU is limited to be within the second preset value range (i.e., the length of the second PPDU should be less than the second preset value).

[0033] In a possible implementation, the method can further include: receiving, by the first device, the second trigger frame sent by the second device, and the second trigger frame includes a first field, and the first field is used to indicate a first time length allocated by the second device for the low-latency service data.

[0034] By the implementation, the first device can effectively obtain the first time length allocated by the second device for the low-latency service data, and then the first device can effectively transmit the low-latency service data within the first time length.

[0035] In a possible implementation, the second trigger frame further includes a second field; when the value of the second field is a first value, the second field is used to indicate that the first device sends the low-latency service data to the second device within the first time length after receiving the second trigger frame; and when the value of the second field is a second value, the second field is used to indicate that the first device sends the low-latency service data to the second device and / or a third device within the first time length after receiving the second trigger frame.

[0036] Exemplarily, the second trigger frame can be an MU-RTS-TXS trigger frame, and the second field can be a TXS mode field carried in the MU-RTS-TXS trigger frame.

[0037] By the implementation, the first device can send the low-latency service data to the second device within the first time length allocated by the second device, and can also send the low-latency service data to the second device and / or a third device (i.e., other devices) within the first time length.

[0038] In a second aspect, a communication method is provided. The method can be applied to a second device, or a component (e.g., a processor, a chip, or a chip system, etc.) of the second device, or a logic node, a logic module, or software capable of realizing all or part of the functions of the second device, or a device used in conjunction with the second device. In the case of the method being applied to the second device, the method includes: receiving, by the second device, first information from a first device, the first information being used to request establishment of a pre-emption session; sending, by the second device, second information to the first device, the second information being used to indicate that the pre-emption session is successfully established; sending, by the second device, at least one first physical layer protocol data unit (PPDU) to the first device based on the pre-emption session, the at least one first PPDU carrying data of a first service, and a length of the first PPDU being less than a first preset value; and / or receiving, by the second device, at least one second physical layer protocol data unit (PPDU) sent by the first device based on the pre-emption session, the at least one second PPDU carrying data of a second service, and a length of the second PPDU being less than a second preset value.

[0039] In the embodiments of the present application, the first device is taken as a non-access point (Non-AP), and the second device is taken as an access point (AP) as an example to introduce the solutions of the embodiments of the present application.

[0040] In the solutions of the present application, the first device and the second device can transmit at least one first PPDU carrying data of a first service and / or at least one second PPDU carrying data of a second service through the established pre-emption session, and a length of each first PPDU is less than a maximum length of the first PPDU (i.e., the first preset value), and a length of each second PPDU is less than a maximum length of the second PPDU (i.e., the second preset value), thereby effectively ensuring the transmission performance / communication performance (e.g., transmission rate, reliability, etc.) of the first service and / or the second service.

[0041] In a possible implementation, the first information includes first indication information and / or second indication information; the first indication information indicates service identification information corresponding to the first service, and the second indication information indicates service identification information corresponding to the second service.

[0042] Through the implementation, the second device can effectively obtain the service identification information corresponding to the first service and / or the service identification information corresponding to the second service, and then through the service identification information, it can effectively determine which services belong to the first service and / or the second service.

[0043] In a possible implementation, the first information includes third indication information and / or fourth indication information; the third indication information indicates service identification information corresponding to the third service, and the fourth indication information indicates service identification information corresponding to the fourth service, the first service is a service other than the third service, and the second service is a service other than the fourth service.

[0044] By this implementation, the second device can effectively obtain the service identification information corresponding to the third service and / or the service identification information corresponding to the fourth service, and through the service identification information, it can be determined which services belong to the third service and / or the fourth service, and then it can be indirectly and effectively determined which services belong to the first service and / or the second service.

[0045] In the embodiments of the present application, the third service and the fourth service can refer to low-latency services. The transmission direction of the third service and the fourth service can not be limited; for example, the third service can refer to uplink low-latency services, and the fourth service can refer to downlink low-latency services; or the third service can refer to downlink low-latency services, and the fourth service can refer to uplink low-latency services. In the present application, the first service is a service other than the third service, and the second service is a service other than the fourth service, so the first service and the second service can refer to non-low-latency services, and the transmission direction of the first service and the second service can also not be limited.

[0046] It should be noted that, in the present application, the first device is taken as a non-access point (Non-AP), and the second device is taken as an access point (AP) as an example to introduce the embodiments of the present application. The second device sends data of the first service to the first device, and the first device sends data of the second service to the second device. Therefore, the first service can refer to downlink non-low-latency services, and the second service can refer to uplink non-low-latency services.

[0047] In the embodiments of the present application, the service identification information can be, but is not limited to, a service identification TID list and / or a service identification TID bitmap; the TID list includes at least one TID; and the TID bitmap includes at least one bit, which is used to represent the at least one TID one by one.

[0048] In a possible implementation, the first information further includes fifth indication information; the fifth indication information indicates one or more of the following: a first preset value and a second preset value.

[0049] By this implementation, the second device can effectively obtain the maximum length of the first PPDU corresponding to the first service (or the maximum threshold of the first PPDU) and / or the maximum length of the second PPDU corresponding to the second service (or the maximum threshold of the second PPDU).

[0050] In a possible implementation, the first information further includes sixth indication information; the sixth indication information indicates whether seventh indication information is allowed to be carried in acknowledgement information of the at least one second PPDU (here, the acknowledgement information can refer to acknowledgement information of one second PPDU, part of the second PPDU, or all of the second PPDU) after the pre-emption session is established, and the seventh indication information indicates that there is data of low-latency service to be transmitted between the second device and the third device.

[0051] In the above, the sixth indication information can further indicate whether a TXS mode requested by sixth information (the sixth information is used to indicate a TXS mode requested by the second device) is allowed to be set as the second mode.

[0052] Through the implementation, the second device can effectively inform the first device of data of low-latency service to be transmitted between the second device and other devices through the acknowledgement information fed back to the first device after the pre-emption session is established.

[0053] In a possible implementation, the second information includes eighth indication information; the eighth indication information indicates whether ninth indication information is allowed to be carried in acknowledgement information of the at least one first PPDU (here, the acknowledgement information can refer to acknowledgement information of one first PPDU, part of the first PPDU, or all of the first PPDU) after the pre-emption session is established, and the ninth indication information indicates that there is data of low-latency service to be transmitted between the first device and the third device.

[0054] In the above, the eighth indication information can further indicate whether a TXS mode requested by fifth information (the fifth information is used to indicate a TXS mode requested by the first device) is allowed to be set as the second mode.

[0055] Through the implementation, the first device can effectively inform the second device of data of low-latency service to be transmitted between the first device and other devices through the acknowledgement information fed back to the second device after the pre-emption session is established.

[0056] In a possible implementation, the method can further include: receiving, by the second device, first acknowledgement information of the at least one first PPDU sent by the first device after the second device sends the at least one first PPDU to the first device, and the first acknowledgement information carries third information used to indicate a time length required by the first device to send data of low-latency service; and / or sending, by the second device, second acknowledgement information of the at least one second PPDU to the first device after the second device receives the at least one second PPDU sent by the second device, and the second acknowledgement information carries fourth information used to indicate a time length required by the second device to send data of low-latency service.

[0057] In this implementation, when the first device and / or the second device have low-latency service data to be transmitted, they can effectively inform the data receiving end of the time required to transmit the low-latency service data. This is equivalent to indicating or implying to the data receiving end that there is low-latency service data to be transmitted. The first and second devices can act as each other's data receiving ends. For example, if the first device sends data to the second device, then the second device is the data receiving end of the first device; if the second device sends data to the first device, then the first device is the data receiving end of the second device.

[0058] In one possible implementation, the first confirmation information further includes a fifth piece of information, wherein the fifth piece of information indicates that when the TXS mode requested by the first device is the first mode, the first device has low-latency service data to be sent to the second device; the fifth piece of information indicates that when the TXS mode requested by the first device is the second mode, the first device has low-latency service data to be sent to the second device and / or the third device; and / or, the second confirmation information further includes a sixth piece of information, wherein the sixth piece of information indicates that when the TXS mode requested by the second device is the first mode, the second device has low-latency service data to be sent to the first device; the sixth piece of information indicates that when the TXS mode requested by the second device is the second mode, the second device has low-latency service data to be sent to the first device and / or the third device.

[0059] In the above, the fifth piece of information can also be used to indicate the TXS mode requested by the first device. The sixth piece of information can also be used to indicate the TXS mode requested by the second device.

[0060] For example, the first confirmation information may be a first multi-user block confirmation MBA frame, the first MBA frame including first associated identification service identifier information, the first associated identification service identifier information including the aforementioned third information and / or fifth information; and / or, the second confirmation information may be a second multi-user block confirmation MBA frame, the second MBA frame including second associated identification service identifier information, the second associated identification service identifier information including the aforementioned fourth information and / or sixth information.

[0061] In this embodiment of the application, the value of the associated identifier in the first associated identifier business identifier information and / or the second associated identifier business identifier information can be a third preset value. For example, the first associated identifier business identifier information and / or the second associated identifier business identifier information is Per AID TID information, which includes an AID11 field. The value of the AID11 field is an integer value between 2008 and 2044, or 2046 or 2047.

[0062] Through this implementation, the first device and / or the second device can effectively inform the data receiver of their requested TXS mode (the first device and the second device can act as each other's data receivers).

[0063] In one possible implementation, the method may further include: the second device sending a first trigger frame to the first device, the first trigger frame being used to trigger the first device to send a second PPDU corresponding to the second service to the second device, wherein the length of the second PPDU is less than a second preset value. Optionally, this implementation may be performed before the second device receives the second PPDU corresponding to the second service sent from the first device.

[0064] This implementation method enables the first device to send the second PPDU corresponding to the second service to the second device, and limits the length of the second PPDU to a second preset value range (i.e., the length of the second PPDU should be less than the second preset value), thereby ensuring the communication quality of the second service.

[0065] In one possible implementation, the method may further include: the second device sending a second trigger frame to the first device, the second trigger frame including a first field, the first field being used to indicate a first duration allocated by the second device for low-latency service data.

[0066] In the above description, the second device receives a first confirmation message from the first device. This first confirmation message carries third information, which indicates the duration required for the first device to transmit low-latency service data. Therefore, the first duration indicated by the first field can be equal to the duration required by the third information for the first device to transmit low-latency service data. Alternatively, the first duration indicated by the first field may be less than the duration required by the third information for the first device to transmit low-latency service data.

[0067] This implementation enables the first device to effectively obtain the first duration allocated by the second device for low-latency service data, thereby enabling the first device to effectively transmit low-latency service data within the first duration.

[0068] In one possible implementation, the second trigger frame further includes a second field; when the value of the second field is a first value, the second field is used to instruct the first device to send the low-latency service data to the second device within a first duration after receiving the second trigger frame; when the value of the second field is a second value, the second field is used to instruct the first device to send the low-latency service data to the second device and / or the third device within a first duration after receiving the second trigger information.

[0069] For example, the second trigger frame can be a MU-RTS-TXS trigger frame, and the second field can be the TXS mode field carried in the MU-RTS-TXS trigger frame.

[0070] This implementation allows the first device to send low-latency service data only to the second device within a first time period allocated by the second device, and may also send low-latency service data to the second device and / or the third device (i.e., other devices) within the first time period.

[0071] Thirdly, this application also provides a communication device, which is the first device or a chip corresponding to the first device. The communication device has the functions of implementing the first aspect and any of the possible embodiments described above. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0072] In one possible design, the communication device includes a processor configured to support the communication device in performing the corresponding functions of the first device in the method described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and other communication devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0073] In one possible design, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0074] In one possible design, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the method provided in the first aspect, and will not be repeated here.

[0075] Fourthly, this application also provides a communication device, which is a second device or a chip corresponding to a second device. The communication device has the functions of implementing the second aspect described above and any of the possible embodiments therein. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0076] In one possible design, the communication device includes a processor configured to support the communication device in performing the corresponding functions of the second device in the method described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and other communication devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0077] In one possible design, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0078] In one possible design, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the method provided in the second aspect, and will not be repeated here.

[0079] Fifthly, a communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement the methods of the first aspect and any possible implementation thereof through logic circuits or execution code instructions.

[0080] In a sixth aspect, a communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement the methods in the second aspect and any of the possible implementations thereof through logic circuits or execution code instructions.

[0081] In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed by a processor, implement the methods of any one of the first and second aspects and any possible implementation thereof.

[0082] Eighthly, a computer program product storing instructions is provided, which, when executed by a processor, implement the methods of the first and second aspects and any possible implementation thereof.

[0083] A ninth aspect provides a chip system including a processor and potentially a memory for implementing the methods of the first and second aspects and any possible implementation thereof. The chip system may be composed of chips or may include chips and other discrete devices.

[0084] In a tenth aspect, a communication system is provided, the communication system comprising the terminal equipment described in the first aspect and the network equipment described in the second aspect.

[0085] It should be noted that the technical effects that can be achieved by any of the third to tenth aspects or any of the third to tenth aspects can be referred to the description of the technical effects that can be achieved by any of the first and second aspects or any of the first and second aspects, which will not be repeated here. Attached Figure Description

[0086] Figure 1 is a schematic diagram of a preemptive transmission interaction;

[0087] Figure 2 is a schematic diagram of a communication system architecture to which the method of the embodiments of this application can be applied;

[0088] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0089] Figure 4 is a schematic flowchart of the method of Embodiment 1 of this application;

[0090] Figure 5A is a schematic diagram of two possible structures of the preemptive session establishment request message provided in the embodiments of this application;

[0091] Figure 5B is a schematic diagram of two other possible structures of the preemptive session establishment request message provided in the embodiments of this application;

[0092] Figure 5C is a schematic diagram of another possible structure of the preemptive session establishment request message provided in the embodiments of this application;

[0093] Figure 6A is a schematic flowchart of the method of Embodiment 2 of this application;

[0094] Figure 6B is an interactive diagram of Embodiment 2 of this application combined with Embodiment 1;

[0095] Figure 7A is a schematic diagram of the structure of an MBA frame;

[0096] Figure 7B is a schematic diagram of the two field structures for each Per AID TID information;

[0097] Figure 7C is a schematic diagram of the field structure of Per AID TID information provided in an embodiment of this application;

[0098] Figure 7D is a schematic diagram of the structure of a trigger frame provided in an embodiment of this application;

[0099] Figure 8A is a schematic flowchart of the method of Embodiment 3 of this application;

[0100] Figure 8B is an interactive diagram of Embodiment 3 of this application combined with Embodiment 1;

[0101] Figure 9 is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0102] Figure 10 is a schematic diagram of another communication device according to an embodiment of this application;

[0103] Figure 11 is a schematic diagram of a chip device structure according to an embodiment of this application. Detailed Implementation

[0104] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0105] The terms, terminology, and features used in the embodiments of this application will be explained below. It should be noted that these explanations are intended to make the embodiments of this application easier to understand and should not be regarded as limiting the scope of protection claimed by this application.

[0106] 1. Low-latency services, non-low-latency services:

[0107] Low-latency services refer to services that require data transmission with low (short) latency (or services that require rapid transmission), while non-low-latency services refer to services that do not require data transmission with low latency (or services that do not require rapid transmission). In this embodiment, low-latency and non-low-latency services can be relative terms. For example, if the transmission time of service 1 is shorter than that of service 2, then service 1 can be called a low-latency service, and service 2 a non-low-latency service. Low-latency services have a relatively low tolerance for latency, while non-low-latency services have a relatively high tolerance for latency. Therefore, the latency / transmission priority of low-latency services can usually be set relatively high, and the latency / transmission priority of non-low-latency services can be set relatively low.

[0108] 2. Physical Layer Protocol Data Unit (PPDU):

[0109] A PPDU (Physical Layer Data Transmission Unit) is the smallest unit of the physical layer used for data transmission. Its main function is to encode and decode upper-layer data and convert it into physical signals for transmission. In the 802.11 standard, PPDUs are formed through the Physical Layer Convergence Procedure (PLCP) sublayer, providing asynchronous transmission of Medium Access Control (MAC) Protocol Data Units (MPDUs) between workstations. The frame structure of the PPDU ensures that the physical layer of the receiving workstation can synchronize each individual incoming frame, thus achieving efficient data transmission.

[0110] 3. To gain an advantage:

[0111] Preemptive transmission is used to meet the data transmission needs of low-latency or ultra-low-latency services. The preemptive transmission process involves interrupting the currently transmitting non-low-latency data to prioritize the transmission of low-latency data. Once the low-latency data transmission is complete, the non-low-latency data transmission resumes. Here, "low-latency" and "non-low-latency" services are relative. Low-latency services require data packet transmission latency to be less than or equal to a set latency value. Non-low-latency services may also have latency requirements, but their latency requirements are longer than those of low-latency services.

[0112] Typically, preemptive transmission can be divided into preemptive transmission at the Physical Layer Protocol Data Unit (PPDU) level and preemptive transmission at the Transmission Opportunity (TXOP) level.

[0113] PPDU-level priority refers to the ability of the sender to interrupt the transmission of the long PPDU (non-low-latency service packet) and proceed with the transmission of the low-latency service packet if a new buffered data packet for the low-latency service arrives during the transmission of a long PPDU. After the low-latency service packet transmission is complete, the remaining non-low-latency service long PPDU transmission resumes. Here, "long packet" refers to a relatively long data packet.

[0114] TXOP-level priority means that within a TXOP, the sender initially sends a non-low-latency service data frame PPDU1. If there is a need to transmit low-latency service data packets (including the needs of the sender, receiver, or other communication equipment), the low-latency service data packets can be transmitted after the PPDU1 transmission is completed within the same TXOP.

[0115] It should be noted that in the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0116] Furthermore, unless otherwise stated, the ordinal numbers such as "first," "second," or "1," "2," etc. (except in special cases indicating numerical values) mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects. For example, "first information" and "second information" are only used to distinguish different phase information, and do not indicate that the size, priority, or importance of these two pieces of information are different.

[0117] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0118] The terms "comprising" and "having," and any variations thereof, used in the following description of embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. Furthermore, the term "for indicating" used in the description of embodiments of this application can include both direct and indirect indication. When describing an indication message for indicating A, it may include whether the indication message directly indicates A or indirectly indicates A, but does not necessarily mean that the indication message carries A.

[0119] The preceding text introduced some of the terms / terms used in the embodiments of this application. The following text introduces the technical background involved in the embodiments of this application.

[0120] In a preemptive transmission scenario, when the sending end sends data to the receiving end, it can break the data frame into multiple shorter PPDUs before sending them. After receiving each PPDU, the receiving end will return an acknowledgment frame to the sending end. If the receiving end has low-latency services to be sent, it can carry indication information in the acknowledgment frame to inform the sending end that it needs to send low-latency services. Then the sending end can hand over the transmission opportunity (TXOP) to the receiving end for transmission.

[0121] For example, referring to Figure 1, STA1 acts as the TXOP initiator, and STA2 acts as the TXOP responder. STA1 sends non-low latency service data to STA2, carrying the non-low latency service data frame through multiple shorter target PPDUs (such as PPDU1, PPDU2, PPDU3) and transmitting them. After receiving PPDU1 from STA1, STA2 sends a block acknowledgment (BA) frame to STA1. If STA2 has low latency (LL) service data to be transmitted, it can include indication information in BA2 upon receiving PPDU2 from STA1, informing STA1 of the LL service data to be transmitted. After receiving BA2, STA1 suspends the transmission of non-low latency service data. Subsequently, STA2 sends low latency service data to STA1. After receiving the low latency service data, STA1 returns a BA to STA2. Once STA2 has finished transmitting the low-latency service data, STA1 can continue to send PPDU3 for non-low-latency services to STA2. After receiving PPDU3, STA2 sends BA3 to STA1.

[0122] Based on the preemptive transmission scenario described above, however, no technology currently proposes to use the preemptive session establishment process to guarantee the communication quality of subsequent services. For example, how to determine which service data the sender will split and how to split it through the preemptive session establishment process in order to guarantee the communication quality of subsequent services.

[0123] Based on the above problems, this application proposes a communication method and apparatus. This method can effectively utilize the preemptive session establishment process to ensure the communication quality of subsequent services.

[0124] The embodiments of this application can be applied to WLAN scenarios, for example, to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 system standards, such as the 802.11be standard, Wi-Fi 7 or Extremely High Throughput (EHT), 802.11bf, and next-generation standards of 802.11be, such as Wi-Fi 8 or even later. Alternatively, the embodiments of this application can also be applied to wireless local area network systems such as Internet of Things (IoT) networks or Vehicle-to-X (V2X) networks. Of course, the embodiments of this application can also be applied to other possible communication systems, such as worldwide interoperability for microwave access (WiMAX) communication systems, 5G communication systems, and future communication systems.

[0125] The following examples illustrate how the embodiments of this application can be applied to WLAN scenarios. It should be understood that WLAN standards have evolved from 802.11a / g to 802.11n, 802.11ac, 802.11ax, and the currently discussed 802.11be. 802.11n can also be called high throughput (HT); 802.11ac can also be called very high throughput (VHT); 802.11ax can also be called high efficiency (HE) or Wi-Fi 6; 802.11be can also be called EHT or Wi-Fi 7. Standards prior to HT, such as 802.11a / b / g, can be collectively referred to as non-high throughput (Non-HT).

[0126] Referring to Figure 2, a network architecture diagram of a WLAN applicable to an embodiment of this application is shown. Figure 2 illustrates an example of a WLAN including one access point (AP) and two stations (STAs). STAs associated with an AP can receive wireless frames sent by the AP and can also send wireless frames to the AP. Furthermore, this embodiment of the application is also applicable to communication between APs, for example, APs can communicate with each other through a distributed system (DS), and this embodiment of the application is also applicable to communication between STAs. It should be understood that the number of APs and STAs in Figure 2 is merely an example, and there may be more or fewer.

[0127] Access points are devices that allow terminal devices (such as mobile phones) to access wired (or wireless) networks. They are primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. They can also be deployed outdoors. An access point acts as a bridge between wired and wireless networks, connecting various wireless network clients and then connecting the wireless network to the Ethernet. Specifically, access points can be terminal devices (such as mobile phones) or network devices (such as routers) with Wi-Fi chips, or wireless communication chips, wireless sensors, or wireless communication terminals with access point functionality. Access points can be devices that support the 802.11be standard. They can also be devices that support various wireless local area networks (WLAN) standards within the 802.11 family, including 802.11ax, 802.11ac, 802.11ad, 802.11ay, 802.11n, 802.11g, 802.11b, 802.11a, and 802.11be next-generation.

[0128] A site can be a wireless communication chip, wireless sensor, or wireless communication terminal, and can also be referred to as a user. For example, a site can be a mobile phone supporting Wi-Fi communication, a tablet computer supporting Wi-Fi communication, a set-top box supporting Wi-Fi communication, a smart TV supporting Wi-Fi communication, a smart wearable device supporting Wi-Fi communication, an in-vehicle communication device supporting Wi-Fi communication, and a computer supporting Wi-Fi communication, etc. Optionally, the site can support the 802.11be standard. The site can also support various wireless local area network (WLAN) standards of the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, and 802.11be next generation.

[0129] For example, access points and sites can be devices used in the Internet of Vehicles (IoV), IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0130] The AP and STA involved in the embodiments of this application can be APs and STAs that comply with the IEEE 802.11 system standard. An AP is a device deployed in a wireless communication network to provide wireless communication functions for its associated STAs. The AP can serve as the hub of the communication system and is typically a network-side product that supports the MAC and PHY of the 802.11 system standard. Examples include base stations, routers, gateways, repeaters, communication servers, switches, or bridges. The base station can include various forms of macro base stations, micro base stations, repeater stations, etc. For ease of description, the devices mentioned above are collectively referred to as APs. STAs are typically terminal products that support the media access control (MAC) and physical layer (PHY) of the 802.11 system standard, such as mobile phones and laptops.

[0131] The communication system architecture or network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of communication system or network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application can also be applied to similar technical problems.

[0132] Unless otherwise specified in this document, the term "first device" and "second device" are used as the main entities for description.

[0133] The "first device" (or "second device") can be a terminal, a device with terminal functions, or a device that implements terminal functions. For example, the "first device" (or "second device") can be a terminal (such as a Non-AP STA or Non-AP MLD), a module (e.g., a chip or circuit) in a terminal (such as a Non-AP STA or Non-AP MLD), or a module or unit that fully or partially implements a terminal (such as a Non-AP STA or Non-AP MLD), or a logic module or software, etc.

[0134] Alternatively, the "first device" (or "second device") can be a network device, a device with network device functions, or a device that implements network device functions. For example, the "first device" (or "second device") can be an access network device (such as an AP, AP MLD), or the "first device" (or "second device") can be a module (e.g., a chip or circuit) in an access network device (such as an AP, AP MLD), or it can be a module or unit (e.g., CU, DU, or RU), logic module, or software that fully or partially implements an access network device (such as an AP, AP MLD). Alternatively, the "first device" (or "second device") can be a core network device. Or, the "first device" (or "second device") can be a server, such as a cloud server. Or, the "first device" (or "second device") can also be a device or apparatus with sensing and / or positioning capabilities, or a device or apparatus capable of performing artificial intelligence tasks. Among these, a device capable of performing artificial intelligence tasks can be called an artificial intelligence task execution device.

[0135] Furthermore, in this application, the "first device" can be either the initiator (or initiator) or the responder (or responder) of the preemptive session establishment, and the "second device" can also be either the initiator (or initiator) or the responder (or responder) of the preemptive session establishment. For example, when the "first device" is the initiator of the preemptive session establishment, the "second device" can be the responder; when the "second device" is the initiator of the preemptive session establishment, the "first device" can be the responder.

[0136] The following description uses "first device" as the initiator of the preemptive session and "second device" as the responder to the preemptive session as an example to illustrate the scheme of the embodiments of this application. Furthermore, "first device" can be replaced by "first equipment," "first communication device," or "initiating device," etc., and "second device" can be replaced by "second equipment," "second communication device," or "responding device," etc. In the following description, "third device" can refer to any device or equipment other than the first device and the second device.

[0137] In this application, "send" and "receive" refer to the direction of information / data / signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, and "send information" can include direct transmission or indirect transmission through other units or modules. "Receive information from YY" can be understood as the source of the information being YY, and "receive information" can include receiving directly from YY or receiving indirectly from YY through other units or modules. Furthermore, "send" can also be understood as the "output" of a chip interface, and "receive" can be understood as the "input" of a chip interface. In other words, "send" or "receive" can occur between devices, such as a base station and a terminal transmitting or receiving data via an air interface. "Send" or "receive" can also occur within a device, such as transmitting or receiving data between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0138] It should be understood that the names of the messages (or information) in the following processes in this application are merely examples. As communication technology evolves, the names of the messages (or information, etc.) in the following processes may change. However, regardless of how the names change, as long as their meaning is the same as the function or meaning of the messages (or information, etc.) in this application, they all fall within the protection scope of this application. For example, "first information" can be replaced with "first radio frame," or "preemptive session establishment request message," or "preemptive session establishment request frame," etc.; "second information" can be replaced with "second radio frame," or "preemptive session establishment response message," or "preemptive session establishment response frame," etc. Furthermore, some names involving "information" in this application can be replaced with "frame," for example, "first confirmation information" can be replaced with "first confirmation frame," and "second confirmation information" can be replaced with "second confirmation frame." Similar information in this application can be replaced with the aforementioned replacement forms, and will not be listed here individually.

[0139] The solutions of the embodiments of this application will be described below.

[0140] This application provides a communication method, which can be applied to, but is not limited to, the architecture shown in FIG3. The method can be executed by a first device (or a second device), a module of the first device (or the second device) (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of the first device (or the second device). Furthermore, this application does not impose specific limitations on the specific structure of the execution entities (first device, second device) or the number of each execution entity, as long as communication can be performed by running a program that records the code of the method provided in this application.

[0141] For ease of description, the first device is referred to as the initiator of the preemptive session establishment, and the second device as the responder. The interaction between the first and second devices is illustrated in the following description. The order of the steps in the following processes is merely illustrative. In practical applications, the execution order of the steps in each process can be adjusted, and all or some of the steps described below can be executed adaptively.

[0142] Referring to Figure 3, the method provided in this application embodiment may include the following:

[0143] S301: The first device sends a first message to the second device, the first message being used to request the establishment of a preemptive session. Accordingly, the second device receives the first message from the first device.

[0144] In this application, the first device can be a non-access point (e.g., Non-AP STA, Non-AP MLD) in the communication network, and the second device can be an access point (e.g., AP, AP MLD) in the communication network; or, the first device can be an access point (e.g., AP, AP MLD) in the communication network, and the second device can be a non-access point (e.g., Non-AP STA, Non-AP MLD) in the communication network.

[0145] In the following text, the first device is used as a non-access point (Non-AP) and the second device is used as an access point (AP) as examples to introduce the scheme of the embodiments of this application. When the roles of the two are reversed, the principle of the scheme is the same and they can be referred to each other.

[0146] S302: The second device sends a second message to the first device, the second message indicating that the preemptive session has been successfully established. Accordingly, the first device receives the second message sent by the second device.

[0147] The above-mentioned S301 and S302 belong to the preemptive session establishment stage. After the preemptive session is successfully established, in this embodiment of the application, any one of the following steps S303 and S304 may be executed, and it is also possible to execute both of the following steps S303 and S304.

[0148] In this embodiment, the second information may be used to indicate that the preemptive session establishment has failed. In this case, the preemptive transmission method is not used between the first device and the second device. Furthermore, the first device may also re-initiate a request to the second device to establish a preemptive session.

[0149] S303: The second device sends at least one first physical layer protocol data unit (PPDU) to the first device based on a preemptive session; the at least one first PPDU carries data of the first service, and the length of the first PPDU is less than a first preset value.

[0150] S304: The first device sends at least one second physical layer protocol data unit (PPDU) to the second device based on a preemptive session; the at least one second PPDU carries data of the second service, and the length of the second PPDU is less than a second preset value.

[0151] In one possible implementation, based on the above-described S304, the method of this application embodiment may further include: the second device sending a first trigger frame (e.g., a basic trigger frame) to the first device, the first trigger frame being used to trigger the first device to send at least one second PPDU corresponding to the second service to the second device, and the length of the second PPDU being less than a second preset value. Correspondingly, the first device receives the first trigger frame sent by the second device. Optionally, this step may be performed before the above-described S304.

[0152] The following section will provide a detailed description of the first and second information in the aforementioned preemptive session establishment process (S301-S302).

[0153] In this application embodiment, the information carried by the first information may include, but is not limited to, the following possible implementations:

[0154] Implementation Method 1: The first information includes first indication information and / or second indication information; wherein, the first indication information indicates the service identification information corresponding to the first service, and the second indication information indicates the service identification information corresponding to the second service.

[0155] Implementation Method 2: The first information includes the third instruction information and / or the fourth instruction information; wherein, the third instruction information indicates the service identification information corresponding to the third service, the fourth instruction information indicates the service identification information corresponding to the fourth service, the first service is a service other than the third service, and the second service is a service other than the fourth service.

[0156] In the embodiments of this application, the third service and the fourth service can refer to low-latency services. The transmission direction of the third service and the fourth service is not limited; for example, the third service can refer to an uplink low-latency service, and the fourth service can refer to a downlink low-latency service; or the third service can refer to a downlink low-latency service, and the fourth service can refer to an uplink low-latency service. In this application, the first service is a service other than the third service, and the second service is a service other than the fourth service. Therefore, the first service and the second service can refer to non-low-latency services, and the transmission direction of the first service and the second service is also not limited.

[0157] It should be noted that in this application, the first device is used as a non-access point (Non-AP STA) and the second device is used as an access point (AP) as an example to introduce the implementation scheme of this application. The second device (AP) sends the data of the first service to the first device (Non-AP STA), and the first device (Non-AP STA) sends the data of the second service to the second device (AP). The first service can refer to the downlink non-low latency service, and the second service can refer to the uplink non-low latency service.

[0158] If we take the first device as the access point (AP) and the second device as the non-access point (Non-AP STA) as an example to introduce the embodiment of this application, the second device (Non-AP STA) sends the data of the first service to the first device (AP), and the first device (AP) sends the data of the second service to the second device (Non-AP STA). Then the first service can refer to the uplink non-low latency service, and the second service can refer to the downlink non-low latency service.

[0159] In this embodiment of the application, the aforementioned service identification information (such as the service identification information corresponding to the first service, the service identification information corresponding to the second service, the service identification information corresponding to the third service, and the service identification information corresponding to the fourth service) may be, but is not limited to, a service identification TID list and / or a service identification TID bitmap; wherein, the service identification TID list includes at least one TID; the service identification TID bitmap includes at least one bit, which is applied one-to-one to represent at least one TID.

[0160] For example, if the TID bitmap includes 8 bits, then these 8 bits can be used to represent TID 0 to 7; as another example, if the TID bitmap includes 16 bits, then these 16 bits can be used to represent TID 0 to 15.

[0161] In one possible implementation, the first information mentioned above may further include a fifth instruction; the fifth instruction may indicate one or more of the following: a first preset value, a second preset value.

[0162] In some embodiments of this application, for the first service, the length of the first PPDU (the first PPDU is used to carry the data of the first service) can be uniformly referenced to a first preset value, wherein the first preset value can also be called the maximum length (or maximum threshold) of the first PPDU; when the second device transmits at least one first PPDU corresponding to the first service, the length of the at least one first PPDU can be the same or different, but both should be limited to the range of the first preset value.

[0163] For the second service, the length of the second PPDU (the second PPDU is used to carry the data of the second service) can be uniformly referenced to the second preset value, which can also be called the maximum length (or maximum threshold) of the second PPDU; when the first device transmits at least one second PPDU corresponding to the second service, the length of the at least one second PPDU can be the same or different, but should be limited to the range of the second preset value.

[0164] In other embodiments of this application, the first service (which may also be the second service) may include one or more groups; if the first service includes multiple groups, the multiple groups may correspond to multiple first preset values ​​with different values, then the aforementioned fifth indication information may indicate a preset value list, which contains the first preset values ​​corresponding to the multiple groups respectively.

[0165] For example, the first service is a non-low latency downlink service, and the second service is a non-low latency uplink service.

[0166] For downlink non-low latency services (i.e., the example of the first service), they are grouped according to the Quality of Service (QoS) requirements. The downlink non-low latency services include 3 groups. The first group of downlink non-low latency services corresponds to the first preset value 1, the second group of downlink non-low latency services corresponds to the first preset value 2, and the third group of downlink non-low latency services corresponds to the first preset value 3. The values ​​of the first preset value 1, the first preset value 2, and the first preset value 3 may be different or partially different, which is not limited.

[0167] For uplink non-low latency services (i.e., examples of the second service), they are grouped according to the QoS requirements. Uplink non-low latency services include 3 groups. The first group of uplink non-low latency services corresponds to the second preset value 1, the second group of uplink non-low latency services corresponds to the second preset value 2, and the third group of uplink non-low latency services corresponds to the second preset value 3. The values ​​of the second preset value 1, the second preset value 2, and the second preset value 3 can be different or partially different, which is not limited.

[0168] The aforementioned fifth instruction information may indicate: a first preset value list (which contains a first preset value 1, a first preset value 2, and a first preset value 3), and / or a second preset value list (which contains a second preset value 1, a second preset value 2, and a second preset value 3).

[0169] The first preset value and / or the second preset value mentioned above can be preset values ​​(e.g., 0.5ms, 1ms, 2ms, etc.), that is, they can be defined by a standard, or determined by negotiation / agreement between the first device and the second device, or determined by negotiation / agreement among multiple parties, or they can be determined by the first device (or the second device) itself. This application does not make any specific limitations on this.

[0170] In one possible implementation, the first information may further include a sixth indication information; the sixth indication information indicates whether, after the preemptive session is established, a seventh indication information is allowed to be carried in the confirmation information of at least one second PPDU, and the seventh indication information indicates that there is data of low-latency service to be transmitted between the second device and the third device.

[0171] In the above, the sixth instruction information may also indicate whether it is permissible to set the TXS mode requested by the following sixth information (the sixth information is used to indicate the TXS mode requested by the second device) to the second mode.

[0172] In one possible implementation, the second information includes an eighth indication information; the eighth indication information indicates whether, after the preemptive session is established, a ninth indication information is allowed to be carried in the confirmation information of the at least one first PPDU, and the ninth indication information indicates that there is data of a low-latency service to be transmitted between the first device and the third device.

[0173] In the above, the eighth indication information may also indicate whether it is permissible to set the TXS mode requested by the fifth information (the fifth information is used to indicate the TXS mode requested by the first device) to the second mode.

[0174] In one possible implementation, the method of this application embodiment may further include the following steps a and / or b:

[0175] Step a: Based on S303 above, after receiving the at least one first PPDU sent by the second device, the first device sends a first confirmation message of the at least one first PPDU to the second device. The first confirmation message carries third information, which is used to indicate the duration required for the first device to send data for the low-latency service. Accordingly, the second device receives the first confirmation message of the at least one first PPDU sent by the first device.

[0176] In one possible implementation, the first confirmation information further includes a fifth piece of information, wherein the fifth piece of information indicates that when the TXS mode requested by the first device is the first mode, the first device has low-latency service data to be sent to the second device; and when the fifth piece of information indicates that the TXS mode requested by the first device is the second mode, the first device has low-latency service data to be sent to the second device and / or the third device.

[0177] In the above, the fifth piece of information can also be used to indicate the TXS mode requested by the first device.

[0178] In one possible implementation, following step a, the method of this embodiment may further include: the second device sending a second trigger frame to the first device, the second trigger frame including a first field indicating a first duration allocated by the second device for low-latency service data. Correspondingly, the first device receives the second trigger frame sent by the second device. Subsequently, the first device may send low-latency service data within the first duration based on the second trigger frame. The first duration may be equal to the duration required by the first device to send low-latency service data as indicated by the aforementioned third information. The first duration may also be less than the duration required by the first device to send low-latency service data as indicated by the aforementioned third information.

[0179] The second trigger frame may also include a second field; when the value of the second field is a first value, the second field is used to instruct the first device to send low-latency service data to the second device within a first duration after receiving the second trigger frame; when the value of the second field is a second value, the second field is used to instruct the first device to send low-latency service data to the second device and / or the third device within a first duration after receiving the second trigger frame.

[0180] For example, the second trigger frame can be a MU-RTS-TXS trigger frame, and the second field can be the TXS mode field carried in the MU-RTS-TXS trigger frame.

[0181] For example, if the fifth information in the first confirmation message sent by the first device to the second device indicates that the TXS mode requested by the first device is the first mode, then it means that when the second device sends a MU-RTS-TXS trigger frame (i.e., an example of the second trigger frame) to the first device, the value of the TXS mode field (i.e., an example of the second field) in that frame is set to the first value (e.g., 1). Accordingly, after receiving the first confirmation message sent by the first device, the second device can, according to the fifth information in the first confirmation message, set the TXS mode field (i.e., an example of the second trigger frame) in the MU-RTS-TXS trigger frame (i.e., an example of the second trigger frame) to the first device and set it to the first value (e.g., 1).

[0182] If the fifth information in the first confirmation message sent by the first device to the second device indicates that the TXS mode requested by the first device is the second mode, then it means that when the second device sends a MU-RTS-TXS trigger frame (i.e., an example of the second trigger frame) to the first device, the value of the TXS mode field (i.e., an example of the second field) in that frame should be set to the second value (e.g., 2). Accordingly, after receiving the first confirmation message sent by the first device, the second device can, according to the fifth information in the first confirmation message, set the TXS mode field (i.e., an example of the second field) in the MU-RTS-TXS trigger frame (i.e., an example of the second trigger frame) to the second value (e.g., 2) when sending the MU-RTS-TXS trigger frame to the first device.

[0183] In one possible implementation, the first confirmation information is a first multi-user block confirmation (MBA) frame, which includes first associated identification service identifier information, and the first associated identification service identifier information includes third information and / or fifth information.

[0184] Step b: Based on S304 above, after receiving the at least one second PPDU sent by the first device, the second device sends a second confirmation message for the at least one second PPDU to the first device. The second confirmation message carries fourth information, which indicates the duration required for the second device to send low-latency service data. Correspondingly, the first device receives the second confirmation message for the at least one second PPDU sent by the second device, which carries the fourth information, indicating the duration required for the second device to send low-latency service data.

[0185] In one possible implementation, the second confirmation information further includes a sixth piece of information, which indicates that when the TXS mode requested by the second device is the first mode, the second device has low-latency service data to be sent to the first device; the sixth piece of information indicates that when the TXS mode requested by the second device is the second mode, the second device has low-latency service data to be sent to the first device and / or the third device.

[0186] In the above, the sixth piece of information can also be used to indicate the TXS mode requested by the second device.

[0187] In one possible implementation, the second confirmation information is a second multi-user block confirmation (MBA) frame, which includes second associated identification service identifier information, and the second associated identification service identifier information includes fourth information and / or sixth information.

[0188] In steps a and / or b above, the value of the associated identifier in the first associated identifier business identifier information and / or the second associated identifier business identifier information can be a third preset value. For example, the first associated identifier business identifier information and / or the second associated identifier business identifier information is Per AID TID information, which includes an AID11 field. The value of the AID11 field is an integer value between 2008 and 2044, or 2046 or 2047.

[0189] In summary, embodiments of this application provide a communication method, comprising: a first device sending first information to a second device, the first information being used to request the establishment of a preemptive session; the first device receiving second information from the second device, the second information being used to indicate that the preemptive session has been successfully established; the first device receiving at least one first physical layer protocol data unit (PPDU) sent by the second device based on the preemptive session; the at least one first PPDU carrying data of a first service, the length of the first PPDU being less than a first preset value; and / or; the first device sending at least one second physical layer protocol data unit (PPDU) to the second device based on the preemptive session; the at least one second PPDU carrying data of a second service, the length of the second PPDU being less than a second preset value. In this method, the first device and the second device can transmit at least one first PPDU carrying data of a first service and / or transmit at least one second PPDU carrying data of a second service through the established preemptive session, and the length of each first PPDU is less than the maximum length of the first PPDU (i.e., the first preset value), and the length of each second PPDU is less than the maximum length of the second PPDU (i.e., the second preset value), thereby ensuring the transmission performance / communication performance (e.g., transmission rate, reliability, etc.) of the first service and / or the second service.

[0190] The scheme shown in Figure 3 above will be described in detail below through several specific implementation methods.

[0191] Implementation Method 1:

[0192] In Implementation Method 1, based on the scheme shown in Figure 3 above, the first device is an example of a non-access point (hereinafter referred to as STA1), and the second device is an example of an access point (hereinafter referred to as AP1). Furthermore, taking the first and second services as non-low-latency services in different directions, and the third and fourth services as low-latency services in different directions, as examples, the preemptive session establishment phases of S301-S302 in the scheme shown in Figure 3 are described in detail. Referring to Figure 4, the method of Implementation Method 1 may include the following steps:

[0193] S401: STA1 sends a preemptive session establishment request message to AP1 (an example of the first information in the scheme shown in Figure 3 above). Accordingly, AP1 receives the preemptive session establishment request message.

[0194] In one possible implementation, the preemptive session establishment request message includes one or more of the following indications:

[0195] (1) First instruction information:

[0196] The first indication information is used to indicate the service identification information corresponding to the downlink non-low latency service (an example of the first service in the scheme shown in Figure 3 above).

[0197] For example, the service identification information corresponding to the downlink non-low latency service is a list of TIDs for the downlink (DL) non-low latency service, which includes at least one TID; or the service identification information corresponding to the downlink non-low latency service is a bitmap of TIDs for the downlink (DL) non-low latency service, which includes at least one bit, and each bit can be used to represent / indicate a TID.

[0198] For example, if a TID bitmap includes 8 bits, these 8 bits can be used to represent TID 0 to 7 (i.e., 8 TIDs); or if a TID bitmap includes 16 bits, these 16 bits can be used to represent TID 0 to 15 (i.e., 16 TIDs).

[0199] After AP1 receives the session establishment request message, it can obtain the service identification information (such as TID list and TID bitmap) corresponding to the downlink non-low latency services through the first indication information in it, thereby determining which downlink non-low latency services are specifically available.

[0200] Furthermore, after STA1 and AP1 successfully establish a preemptive session, if AP1 sends a data frame corresponding to the TID of a downlink non-low latency service to STA1, AP1 needs to limit the length of each first PPDU (example of the first PPDU in the scheme shown in Figure 3 above) corresponding to the downlink non-low latency service data frame to a first preset value (that is, control the length of each first PPDU sent to be less than the first preset value).

[0201] (2) Second instruction information:

[0202] The second indication information is used to indicate the service identification information corresponding to the uplink non-low latency service (an example of the second service in the scheme shown in Figure 3 above).

[0203] For example, the service identification information corresponding to the uplink non-low latency service is a list of TIDs for the uplink (UL) non-low latency service, which includes at least one TID; or the service identification information corresponding to the uplink non-low latency service is a bitmap of the uplink (UL) non-low latency service, which includes at least one bit, and each bit can be used to represent / indicate a TID.

[0204] After AP1 receives the session establishment request message, it can obtain the service identification information (such as TID list or TID bitmap) corresponding to the uplink non-low latency services through the second indication information in the message, thereby determining which uplink non-low latency services are available.

[0205] Furthermore, after STA1 and AP1 successfully establish a preemptive session, if STA1 sends a data frame corresponding to the TID of the uplink non-low latency service to AP1, STA1 needs to limit the length of each second PPDU (an example of the second PPDU in the scheme shown in Figure 3 above) corresponding to the data frame of the uplink non-low latency service to within a second preset value (that is, control the length of each second PPDU sent to be less than the second preset value).

[0206] (3) Third instruction information:

[0207] The third indication information is used to indicate the service identification information corresponding to the downlink low-latency service (an example of the third service in the scheme shown in Figure 3 above).

[0208] For example, the service identification information corresponding to the downlink low latency service is a list of TIDs for the downlink (DL) low latency service, which includes at least one TID; or the service identification information corresponding to the downlink low latency service is a bitmap of TIDs for the downlink (DL) low latency service, which includes at least one bit, and each bit can be used to represent / indicate a TID.

[0209] After AP1 receives the session establishment request message, it can obtain the service identification information (such as TID list, TID bitmap) corresponding to the downlink low latency service through the third indication information in it, and thus indirectly determine the downlink non-low latency service.

[0210] For example, AP1 can treat a service corresponding to a TID that is not in the TID list of downlink DL low latency services as a downlink non-low latency service, or AP1 can treat a service corresponding to a TID that is not in at least one TID represented / indicated by the TID bitmap of downlink DL low latency services as a downlink non-low latency service.

[0211] Furthermore, after STA1 and AP1 successfully establish a preemptive session, if AP1 sends a data frame corresponding to the TID of a downlink non-low latency service (an example of the first service in the scheme shown in Figure 3 above) to STA1, AP1 needs to limit the length of each first PPDU (an example of the first PPDU in the scheme shown in Figure 3 above) corresponding to the downlink non-low latency service data frame to a first preset value (i.e., control the length of each first PPDU sent to be less than the first preset value).

[0212] (4) Fourth instruction information:

[0213] The fourth indication information is used to indicate the service identification information corresponding to the uplink low latency service (an example of the fourth service in the scheme shown in Figure 3 above).

[0214] For example, the service identification information corresponding to the uplink low latency service is a list of TIDs for the uplink (UL) low latency service, which includes at least one TID; or the service identification information corresponding to the uplink low latency service is a bitmap of TIDs for the uplink (UL) low latency service, which includes at least one bit, and each bit can be used to represent / indicate a TID.

[0215] After AP1 receives the session establishment request message, it can obtain the service identification information (such as TID list, TID bitmap) corresponding to the uplink low latency service through the fourth indication information, and thus indirectly determine the uplink non-low latency service.

[0216] For example, AP1 can treat a service corresponding to a TID that is not in the TID list of uplink UL low latency services as an uplink non-low latency service, or AP1 can treat a service corresponding to a TID that is not in at least one TID represented / indicated by the TID bitmap of uplink UL low latency services as an uplink non-low latency service.

[0217] Furthermore, after STA1 and AP1 successfully establish a preemptive session, if STA1 sends a data frame corresponding to the TID of an uplink non-low latency service (an example of the second service in the scheme shown in Figure 3 above) to AP1, STA1 needs to limit the length of each second PPDU (an example of the second PPDU in the scheme shown in Figure 3 above) corresponding to the data frame of the uplink non-low latency service to within a second preset value (that is, control the length of each second PPDU sent to be less than the second preset value).

[0218] (5) Fifth instruction information:

[0219] The fifth instruction information may be used to indicate one or more of the following:

[0220] First preset value; Second preset value; List of first preset values; List of second preset values.

[0221] In this embodiment of the application, there may be multiple groups of downlink non-low latency services. Each group of downlink non-low latency services may correspond to the maximum length / threshold of a PPDU (i.e., the first preset value mentioned above). The list of first preset values ​​may include multiple first preset values. The size (or value) of these multiple first preset values ​​may be partially or completely different, which is not limited.

[0222] Similarly, there can be multiple groups of uplink non-low latency services. Each group of uplink non-low latency services can correspond to a maximum length / threshold of PPDU (i.e., the second preset value mentioned above). The list of second preset values ​​can include multiple second preset values. The size (or value) of these multiple second preset values ​​may be partially or completely different, which is not limited.

[0223] For example, based on the above-mentioned indication information, the following are schematic diagrams of several possible structures of the preemptive session establishment request message in the embodiments of this application:

[0224] Structure 1: As shown in Figure 5A(a), the preemptive session establishment request message contains the TID bitmap of downlink non-low latency services, the TID bitmap of uplink non-low latency services, the first preset value (maximum length / threshold of PPDU for downlink non-low latency services), and the second preset value (maximum length / threshold of PPDU for uplink non-low latency services).

[0225] Structure 2: As shown in Figure 5A(b), the preemptive session establishment request message contains the TID bitmap of downlink low latency service, the TID bitmap of uplink low latency service, the first preset value (maximum length / threshold of PPDU for downlink non-low latency service), and the second preset value (maximum length / threshold of PPDU for uplink non-low latency service).

[0226] For the structure shown in Figure 5A(b), after AP1 receives the preemptive session establishment request message, it can know the TID bitmap of the downlink low latency service and the TID bitmap of the uplink low latency service. Then AP1 can regard the downlink service not included in the TID bitmap of the downlink low latency service as the downlink non-low latency service, and regard the uplink service not included in the TID bitmap of the uplink low latency service as the uplink non-low latency service.

[0227] Structure 3: As shown in Figure 5B(a), the preemptive session establishment request message contains direction information, a TID bitmap for non-low latency services, and preset value information. If the direction information indicates that the transmission direction is downlink, then the TID bitmap is the TID bitmap for downlink non-low latency services, and the preset value information is used to indicate a first preset value. If the direction information indicates that the transmission direction is uplink, then the TID bitmap is the TID bitmap for uplink non-low latency services, and the preset value information is used to indicate a second preset value.

[0228] Structure 4: As shown in Figure 5B(b), the preemptive session establishment request message includes direction information, a TID bitmap for low-latency services, and preset value information. If the direction information indicates a downlink transmission direction, then the TID bitmap is a downlink low-latency service TID bitmap, and the preset value information indicates a first preset value. If the direction information indicates an uplink transmission direction, then the TID bitmap is an uplink low-latency service TID bitmap, and the preset value information indicates a second preset value. If the direction information indicates both downlink and uplink transmission directions, then the TID bitmap includes both downlink and uplink low-latency service TID bitmaps, and the preset value information indicates both a first and a second preset value.

[0229] For the structure shown in Figure 5B(b), after AP1 receives the preemptive session establishment request message, it can know the TID bitmap of the downlink low latency service and / or the TID bitmap of the uplink low latency service. Then AP1 can regard downlink services not included in the TID bitmap of the downlink low latency service as downlink non-low latency services, and / or regard uplink services not included in the TID bitmap of the uplink low latency service as uplink non-low latency services.

[0230] Structure 5: As shown in Figure 5C, the preemptive session establishment request message includes k groups of non-low latency services. Each group corresponds to: the TID of the downlink non-low latency service, the TID of the uplink non-low latency service, a first preset value 1, and a second preset value. Referring to Figure 5C, the first group of non-low latency services includes: TID bitmap 1 of the DL non-low latency service, TID bitmap 1 of the UL non-low latency service, the first preset value 1, and the second preset value 1. Similarly, the kth group of non-low latency services includes: TID bitmap k of the DL non-low latency service, TID bitmap k of the UL non-low latency service, the first preset value k, and the second preset value k. Where k is an integer greater than 1.

[0231] The first preset value and / or the second preset value mentioned above can be preset values ​​(e.g., 0.5ms, 1ms, 2ms, etc.), that is, they can be defined by a standard, or determined by negotiation / agreement between the first device and the second device, or determined by negotiation / agreement among multiple parties, or they can be determined by the first device (or the second device) itself. This application does not make any specific limitations on this.

[0232] (6) Sixth instruction information:

[0233] The sixth indication information indicates whether, after the preemptive session is established, AP1 is allowed to carry the seventh indication information in the PPDU acknowledgment frame (an example of the acknowledgment information of at least one second PPDU in the scheme shown in Figure 3 above). The seventh indication information indicates that there is data of low-latency service to be transmitted between AP1 and other stations (i.e., an example of the third device in the scheme shown in Figure 3 above).

[0234] The sixth instruction can also indicate whether AP1 is allowed to set the requested TXS mode to the second mode.

[0235] In this embodiment of the application, AP1 may also carry indication information in the PPDU acknowledgment frame (an example of the acknowledgment information of at least one second PPDU in the scheme shown in FIG3 above) to indicate that there is low-latency service data to be transmitted between AP1 and STA1.

[0236] S402: AP1 sends a preemptive session establishment response message to STA1. Correspondingly, STA1 receives the preemptive session establishment response message.

[0237] In one possible implementation, the session establishment response message includes an eighth indication message, which indicates whether STA1 is allowed to carry a ninth indication message in the PPDU acknowledgment frame (an example of the acknowledgment message of at least one first PPDU in the scheme shown in Figure 3 above) after the preemptive session is established. The ninth indication message indicates that STA1 has data of low-latency service to be transmitted with other stations (i.e., an example of the third device in the scheme shown in Figure 3 above).

[0238] The eighth instruction message can also indicate whether STA1 is allowed to set the requested TXS mode to the second mode.

[0239] In this embodiment of the application, STA1 may also carry indication information (such as information 1 below) in the acknowledgment frame of PPDU (an example of the acknowledgment information of at least one first PPDU in the scheme shown in FIG3 above) to indicate that there is low-latency service data to be transmitted between STA1 and AP1.

[0240] In Implementation Method 1, the focus is on the preemptive session establishment phase between the AP and STA. This phase allows for the exchange of information necessary for subsequent data transmission, such as service identification information for non-low-latency services and / or the maximum length of the PPDU corresponding to a single non-low-latency service and / or enabling effective indication when a low-latency service is to be transmitted. Therefore, by utilizing the preemptive session establishment phase, this method enables the AP and STA to effectively exchange information regarding subsequent service transmission, thereby ensuring the transmission / communication quality of subsequent services.

[0241] Implementation Method Two:

[0242] In Implementation Method Two, after the preemptive session of Implementation Method One is successfully established, AP1 and STA1 further describe the service transmission based on this preemptive session. The following example illustrates this: AP1 needs STA1 to send downlink non-low-latency service data, while STA1 stores low-latency service data to be sent during this period. Referring to Figure 6A, the method of Implementation Method Two may include the following steps:

[0243] S601A: AP1 sends a downlink non-low latency service data frame (an example of the first service in the scheme shown in Figure 3 above) to STA1. Correspondingly, STA1 receives the downlink non-low latency service data frame sent by AP1.

[0244] In S601A, AP1 sends a data frame for downlink non-low latency service (an example of the first service in the scheme shown in Figure 3 above) to STA1, including the following:

[0245] Since different downlink non-low latency services may correspond to the same first preset value or different first preset values, if the length of the data frame of the downlink non-low latency service sent by AP1 is greater than the first preset value corresponding to the downlink non-low latency service, AP1 will split the data frame of the downlink non-low latency service to carry it in at least one first PPDU. The length of the at least one first PPDU may be the same or different, but the length of each first PPDU should be limited to the range of the corresponding first preset value (i.e., less than the corresponding first preset value).

[0246] S602A: STA1 sends acknowledgment frame 1 to AP1. The first acknowledgment frame is used to confirm that the data frame (or the first PPDU) of the downlink non-low latency data service has been received. Accordingly, AP1 receives acknowledgment frame 1 sent by STA1 (an example of the first acknowledgment information in the scheme shown in Figure 3 above).

[0247] In one possible implementation, the confirmation frame 1 (an example of the first confirmation information in the scheme shown in Figure 3 above) includes information 1 (an example of the third information in the scheme shown in Figure 3 above). Information 1 is used to indicate the duration required for STA1 to send low-latency service data. That is, through information 1, it can be indirectly / implicitly indicated that STA1 has low-latency service data to be sent.

[0248] In this embodiment, not only access points (such as AP1) can send MBA frames, but non-access points (such as STA1) can also send MBA frames. For example, acknowledgment frame 1 can be a multi-user block acknowledgment (MBA) frame.

[0249] The MBA frame of the embodiments of this application will be described in detail below.

[0250] Figure 7A shows a schematic diagram of the MBA frame structure. As shown in Figure 7A, the MBA frame includes a Block Acknowledgment (BA) information field. The BA information field may include one or more Per AID TID Info fields. The first 11 bits of each Per AID TID Info field are the AID11 field. Typically, when the value of the AID11 field is not equal to 2045, the field structure of the Per AID TID Info is shown in Figure 7B(a). This Per AID TID Info field includes AID TID information, a block ack starting sequence control field, and a block ack bitmap field. The block ack starting sequence control and block ack bitmap contain acknowledgment information for the preceding data frame. When the value of the AID11 field is equal to 2045, the field structure of the Per AID TID Info is shown in Figure 7B(b). The RA field in this Per AID TID Info is used to carry the MAC address of the station, that is, to indicate that a preceding data frame sent by the station corresponding to this MAC address has been received.

[0251] Typically, an AP can send MBAs to multiple sites. The following describes the relevant usage scenarios.

[0252] For example, in use case 1, AP1 triggers one or more associated sites to send data, and then AP1 sends an MBA frame to acknowledge the data frames from multiple sites. In this case, the AID11 field carries the AID of the associated site, which can uniquely identify an associated site.

[0253] In use case 2, AP1 triggers random access from an unassociated site, and then AP1 sends an MBA acknowledgment of the random access transmission. At this time, the value of the AID11 field is set to 2045, and the AID11 field is followed by RA, which carries the MAC address of the site, indicating that AP1 has received the preceding data frame sent by the site corresponding to that MAC address.

[0254] In this embodiment of the application, the MBA frame may carry other control information, such as the aforementioned information 1 (the duration required for low-latency service data) carried in the MBA frame.

[0255] For example, as shown in Figure 7C(a), the MBA frame contains a Per AID TID Info field, which includes an AID TID information field and a low latency (LL) traffic duration field (i.e., the aforementioned Information 1). The AID11 field in the AID TID information field takes a preset value (e.g., an integer value between 2008 and 2044, or 2046, or 2047). The AID11 field is used to indicate that the Per AID TID Info field carries the aforementioned Information 1 (Information 1 is used to indicate the duration required for the low latency traffic data to be transmitted by STA1).

[0256] In one possible implementation, the confirmation frame 1 (an example of the first confirmation information in the scheme shown in Figure 3) may further include information 2 (i.e., an example of the fifth information in the scheme shown in Figure 3). If STA1 has low-latency service data to be sent to AP1, then information 2 is used to indicate that the TXS mode requested by STA1 is mode 1 (an example of the first mode in the scheme shown in Figure 3). If STA1 has low-latency service data to be sent to AP1 and / or other sites (an example of the third device in the scheme shown in Figure 3), such as AP2 and STA2, then information 2 is used to indicate that the TXS mode requested by STA1 is mode 2 (an example of the second mode in the scheme shown in Figure 3).

[0257] For example, Figure 7C(b) shows another structural diagram of the Per AID TID Info in the MBA frame. As shown in Figure 7C(b), it includes the AID TID information field, the low latency service duration (LL traffic duration) field (i.e., information 1 above), and the requested TXS mode field (i.e., information 2 above).

[0258] S603A: AP1 sends trigger frame 1 to STA1. Trigger frame 1 is used to trigger STA1 to send low-latency service data. Correspondingly, STA1 receives trigger frame 1 sent by AP1.

[0259] In one possible implementation, trigger frame 1 (an example of the second trigger frame in the scheme shown in Figure 3 above) includes a first field, which indicates a first duration allocated by AP1 for the low-latency service. The first duration may be equal to the duration required for STA1 to transmit low-latency service data as indicated by information 1 in 602A above, or it may be less than the duration required for STA1 to transmit low-latency service data as indicated by information 1 in 602A above.

[0260] In one possible implementation, trigger frame 1 (an example of the second trigger frame in the scheme shown in Figure 3 above) also includes a second field:

[0261] When the value of the second field is the first value (e.g., 0), the second field is used to instruct STA1 to send low-latency service data to AP1 within a first duration after receiving trigger frame 1; when the value of the second field is the second value (e.g., 1), the second field is used to instruct STA1 to send low-latency service data to AP1 and / or other sites (example of the third device in the scheme shown in Figure 3 above) within a first duration after receiving trigger frame 1.

[0262] For example, trigger frame 1 is a MU-RTS-TXS trigger frame (an example of the second trigger frame in the scheme shown in Figure 3 above). The second field is the TXS mode field carried in the MU-RTS-TXS trigger frame. Figure 7D shows a schematic diagram of the structure of the MU-RTS-TXS trigger frame. As shown in Figure 7D, the MU-RTS-TXS trigger frame includes an allocation duration field (an example of the first field above) and a TXS mode field (an example of the second field above).

[0263] S604A: STA1 sends a low-latency service data frame to AP1. Correspondingly, AP1 receives the low-latency service data frame.

[0264] If the value of the second field in the trigger frame 1 received by STA1 is the first value (e.g., 0), then STA1 can send downlink low-latency service data frames to AP1 within the first time period allocated by AP1.

[0265] If the value of the second field in the trigger frame 1 received by STA1 is the second value (e.g., 1), then STA1 can send downlink low-latency service data frames to AP1 and / or other stations (e.g., AP2, STA2) within the first duration allocated by AP1.

[0266] S605A: AP1 sends acknowledgment frame 2 to STA1. Acknowledgment frame 2 is used to confirm that the data frame of the low-latency service has been received. Accordingly, AP1 receives the acknowledgment frame 2.

[0267] For example, Figure 6B shows a schematic diagram of the interaction between AP1 and STA2 when Embodiment 1 and Embodiment 2 are implemented in combination. As shown in Figure 6B, AP1 and STA1 complete the preemptive session establishment stage (see S401-S402 in Embodiment 1). After this, AP1 sends a first PPDU (downlink) with a length less than a first preset value to STA1 (see S601A above). After receiving the first PPDU, if STA1 has low-latency service data to be sent to AP1 and / or other stations, it can carry indication information in the acknowledgment frame 1 (see above). As described in S602A, AP1 is informed and acknowledgment frame 1 is sent to AP1. After receiving acknowledgment frame 1, AP1 sends trigger frame 1 to STA1 (as described in S603A above) to trigger STA1 to send (uplink) low-latency service data. After receiving trigger frame 1, STA1 sends (uplink) low-latency service data frames to AP1. In addition, STA1 may also send low-latency service data to other stations (see S604A above). After receiving the low-latency service data frames, AP1 sends acknowledgment frame 2 back to STA1 (see S605A above).

[0268] After the low-latency service data transmission of STA1 is completed, AP1 can continue to transmit non-low-latency service data with STA1, as described in S601A above (or S801A-S802A below), which will not be described in detail here.

[0269] In implementation method two, the session establishment process between STA1 and AP1 enables both parties to effectively and accurately obtain the service identification information and / or the maximum length of the corresponding PPDU (such as a first preset value and / or a second preset value) for non-low latency services. Thus, when AP1 needs to send downlink non-low latency service data to STA1, AP1 can limit the length of the first PPDU of the downlink non-low latency service within the corresponding threshold (i.e., the first preset value), thereby effectively ensuring the communication quality of the downlink non-low latency service. Furthermore, if STA1 has low latency service data to be sent to AP1 and / or other sites, it sends an acknowledgment frame to AP1. This acknowledgment frame can carry relevant information about the low latency service to effectively inform AP1. Based on this information, AP1 allocates a corresponding duration for the low latency service and informs STA1 via a trigger frame. This not only meets the transmission requirements of low latency services but also ensures the transmission requirements of non-low latency services.

[0270] Implementation Method 3:

[0271] In Implementation Method 3, after the preemptive session establishment success phase of Implementation Method 1, AP1 and STA1 further describe service transmission based on this preemptive session. The main difference between Implementation Method 2 and Implementation Method 3 is that after STA1 and AP1 complete the preemptive session establishment phase, STA1 sends uplink non-low-latency service data (an example of the second service in the scheme shown in Figure 3) to AP1. During this period, AP1 has low-latency service data to be sent. Referring to Figure 8A, the method of Implementation Method 3 may include the following steps:

[0272] S801A: AP1 sends trigger frame 2 to STA1 (an example of the first trigger frame in the scheme shown in Figure 3). Trigger frame 2 is used to trigger STA1 to send data frames for non-low latency services. Accordingly, STA1 receives trigger frame 2.

[0273] For example, trigger frame 2 is a basic trigger frame.

[0274] S802A: STA1 sends an uplink non-low latency service data frame to AP1. Correspondingly, AP1 receives the uplink non-low latency service data frame sent by STA1.

[0275] In S802A, STA1 sends an uplink non-delay service (an example of the second service in the scheme shown in Figure 3 above) data frame to AP1, including the following:

[0276] Since different uplink non-low latency services may correspond to the same second preset value or different second preset values, if the length of the data frame of the uplink non-latency service sent by STA1 is greater than the second preset value corresponding to the uplink non-latency service, STA1 will split the data frame of the uplink non-latency service to carry it in at least one second PPDU. The length of the at least one second PPDU may be the same or different, but the length of each second PPDU should be limited to the range of the corresponding second preset value (i.e., less than the corresponding second preset value).

[0277] S803A: AP1 sends acknowledgment frame 3 to STA1 (an example of the second acknowledgment information in the scheme shown in Figure 3 above). Acknowledgment frame 3 is used to confirm that the uplink non-low latency service data frame (or the second PPDU) has been received. Accordingly, STA1 receives acknowledgment frame 3 sent by AP1.

[0278] In one possible implementation, the confirmation frame 3 (an example of the second confirmation information in the scheme shown in Figure 3 above) carries information 3 (an example of the fourth information in the scheme shown in Figure 3 above). This information 3 is used to indicate the duration required for AP1 to send low-latency service data. That is, this information 3 can indirectly / implicitly indicate that AP1 has low-latency service data to be sent.

[0279] For example, the aforementioned confirmation frame 3 can be an MBA frame, and the MBA frame can carry other control information, such as the aforementioned information 3 (duration required for low latency service / duration of low latency service).

[0280] For example, the structure of an MBA frame can be referred to as shown in Figure 7A above. The MBA frame includes Per AID TID information, which includes the aforementioned information 3 (indicating the duration of low latency service). The Per AID TID information includes an AID TID information field, and the AID11 field in the AID TID information field takes a preset value (e.g., an integer value between 2008 and 2044, or 2046, or 2047). The structural diagram of the Per AID TID information can be referred to as shown in Figure 7C(a) above, and will not be repeated here.

[0281] In one possible implementation, the confirmation frame 3 (an example of the second confirmation information in the scheme shown in FIG3) may further include information 4 (an example of the sixth information in the scheme shown in FIG3 above); if AP1 has low-latency service data to be sent to STA1, then information 4 is used to indicate that the TXS mode requested by AP1 is mode 1 (an example of the first mode in the scheme shown in FIG3 above). If AP1 has low-latency service data to be sent to STA1 and / or other sites (an example of the third device in the scheme shown in FIG3 above); other sites may include other access sites (e.g., AP2) and / or other non-access sites (e.g., STA2), then information 4 is used to indicate that the TXS mode requested by AP1 is mode 2 (an example of the second mode in the scheme shown in FIG3 above).

[0282] For example, the structure of an MBA frame can be referred to in Figure 7A above. The MBA frame includes Per AID TID information, which includes information 3 (indicating the duration of low latency service) and information 4 (indicating the requested TXS mode). The structural diagram of the Per AID TID information can be referred to in Figure 7C(b) above, and will not be repeated here.

[0283] S804A: AP1 sends a downlink low-latency service data frame to STA1. Correspondingly, STA1 receives the downlink low-latency service data sent by AP.

[0284] If AP1's TXS mode is mode 1, then AP1 can send downlink low-latency service data frames to STA1 within the duration of the low-latency service data.

[0285] If AP1's TXS mode is mode 2, then AP1 can send downlink low-latency service data frames to STA1 within the duration of the low-latency service data, and can also send low-latency service data frames to other stations (such as STA2).

[0286] S805A: STA1 sends acknowledgment frame 4 to AP1. Acknowledgment frame 4 is used to confirm that the downlink low-latency service data frame has been received. Accordingly, AP1 receives the acknowledgment frame 4.

[0287] For example, Figure 8B shows the interaction diagram between AP1 and STA2 when Embodiment 1 and Embodiment 2 are implemented in combination. As shown in Figure 8B, AP1 and STA1 complete the preemptive session establishment stage (see S401-S402 in Embodiment 1 above); after this, AP1 sends trigger frame 2 to STA1 to trigger STA1 to send data frames for non-low latency services (see S801A above); after receiving trigger frame 2, STA1 sends a second PPDU (uplink) with a length less than a second preset value to AP1 (see S802A above), and AP1 receives the second PPDU. After the second PPDU, if AP1 has low-latency service data to be sent to STA1 and / or other sites, it can carry indication information in acknowledgment frame 3 (see S803A above) to inform STA1 and send acknowledgment frame 3 to STA1; then, AP1 sends (downlink) low-latency service data frames to STA1. In addition, AP1 may also have data to send low-latency service to other sites (see S804A above); after receiving the low-latency service data frames, STA1 sends acknowledgment frame 4 back to AP1 (see S805A above).

[0288] After the low-latency service data transmission of AP1 is completed, AP1 can continue to transmit non-low-latency service data with STA1, as described in S801A-S802A (or S601A). This will not be elaborated here.

[0289] In implementation method two, STA1 and AP1 can effectively and accurately obtain the service identification information and / or the maximum value of the corresponding PPDU length (such as a first preset value and / or a second preset value) for non-low latency services through the session establishment process. Thus, when STA1 sends uplink non-low latency service data to AP1, the length of the second PPDU for the uplink non-low latency service can be limited to the corresponding threshold (i.e., the second preset value), thereby effectively ensuring the communication quality of the uplink non-low latency service. Furthermore, if there is low latency service data to be sent between AP1 and STA1 and / or other stations, an acknowledgment frame can be sent to STA1 to effectively inform STA1 of the relevant information of the low latency service to be sent, thereby meeting the transmission requirements of the low latency service.

[0290] Regarding the above-described embodiments one to three, it should be noted that:

[0291] (1) The above-described embodiments one to three can be implemented individually or in combination, without any specific limitation. For example, the scheme shown in embodiment one (the preemptive session establishment phase) can be implemented in combination with some or all of the schemes shown in embodiment two and / or embodiment three.

[0292] (2) For each of the embodiments one to three, the improved steps of this application (e.g., adding indication information, fields, etc. to the message / frame structure) can be implemented in combination within the same embodiment or decoupled from each other, and there is no necessary binding relationship between them. For example, in embodiment one, the preemptive session establishment request message sent by STA1 to AP1 can be implemented according to the design described in S401, while the preemptive session establishment response message sent by AP1 to STA1 can be implemented without following the design described in S402. Embodiments two and three are similar, and will not be listed in detail here.

[0293] (3) The above focuses on describing the differences between implementation methods one to three. Apart from the differences, implementation methods one to three can be referred to each other.

[0294] (4) The step numbers of the flowcharts described in Embodiments 1 to 3 above are only examples of the execution flow and do not constitute a restriction on the order of execution of the steps. There are no time dependencies between the steps in the various implementations of this application, and there is no strict execution order between them. In addition, not all the steps shown in the flowcharts are mandatory steps. Some steps can be added or deleted based on the actual needs of each flowchart.

[0295] The above-described embodiments one to three primarily focus on the interaction between AP1 and STA1 (and may also include other stations). In practical applications, AP1 can also transmit with other devices (e.g., STA / AP), and STA1 can also transmit with other devices (e.g., STA / AP). Similarly, these can be implemented with reference to embodiments one to three, which will not be described in detail here. Furthermore, the embodiments of this application propose using a preemptive session establishment process to ensure the transmission quality of subsequent non-low-latency services. Similarly, other session establishment processes or other communication stages can also be used to implement this, which will not be described in detail here.

[0296] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspective of interaction between various devices. To implement the functions of the methods provided in the embodiments or implementations of this application, the first device or the second device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0297] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments or implementations of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0298] Similar to the above concept, as shown in FIG9, this application embodiment also provides a communication device 900 for implementing the functions of the first or second device in the above method. For example, the communication device 900 can be a software module or a chip system. In this application embodiment, the chip system can be composed of chips or can include chips and other discrete devices. The communication device 900 may include: a communication unit 901 and a processing unit 902.

[0299] In this embodiment, the communication unit 901, also referred to as the transceiver unit, may include a sending unit and / or a receiving unit, respectively used to perform the sending and receiving steps of the first or second device in the above method embodiments. The processing unit 902 may be used to read instructions and / or data from the storage module so that the communication device 900 implements the aforementioned method embodiments.

[0300] Optionally, the communication device 900 may further include a storage unit 903, which is equivalent to a storage module and can be used to store instructions and / or data.

[0301] The communication device provided in the embodiments of this application will be described in detail below with reference to Figures 9 and 10. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, the contents not described in detail can be implemented by referring to the manner shown in Figures 3-4, 6A and 8A above. For the sake of brevity, they will not be repeated here.

[0302] The communication unit 901 can also be called a transceiver, transceiver, or transceiver device. The processing unit can also be called a processor, processing board, processing module, or processing device. Optionally, the device in the communication unit 901 used to implement the receiving function can be considered a receiving unit, and the device in the communication unit 901 used to implement the transmitting function can be considered a transmitting unit; that is, the communication unit 901 includes both a receiving unit and a transmitting unit. The communication unit can sometimes also be called a transceiver, transceiver circuit, or transceiver unit. The receiving unit can sometimes be called a receiver, receiver, or receiving circuit. The transmitting unit can sometimes be called a transmitter, transmitter, or transmitting circuit.

[0303] When the communication device 900 executes the first device in the process shown in Figure 3 of the above embodiment:

[0304] The communication unit 901 is configured to send first information to the second device, the first information being used to request the establishment of a preemptive session; the communication unit 901 is also configured to receive second information from the second device, the second information being used to indicate that the preemptive session has been successfully established; the communication unit 901 is also configured to, based on the preemptive session, receive at least one first physical layer protocol data unit (PPDU) sent by the second device; the at least one first PPDU carries data of a first service, and the length of the first PPDU is less than a first preset value; and / or; based on the preemptive session, send at least one second physical layer protocol data unit (PPDU) to the second device; the at least one second PPDU carries data of a second service, and the length of the second PPDU is less than a second preset value.

[0305] The processing unit 902 can be used to process information and / or data, etc.

[0306] When the communication device 900 executes the second device in the process shown in Figure 3 of the above embodiment:

[0307] The communication unit 901 is configured to receive first information from the first device, the first information being used to request the establishment of a preemptive session; and to send second information to the first device, the second information being used to indicate that the preemptive session has been successfully established; the communication unit 901 is further configured to send at least one first physical layer protocol data unit (PPDU) to the first device based on the preemptive session; the at least one first PPDU carrying data of a first service, the length of the first PPDU being less than a first preset value; and / or; and to receive at least one second physical layer protocol data unit (PPDU) sent by the first device based on the preemptive session; the at least one second PPDU carrying data of a second service, the length of the second PPDU being less than a second preset value.

[0308] The processing unit 902 is used to process information and / or data, etc.

[0309] The above are just examples. Processing unit 902 and communication unit 901 can also perform other functions. For a more detailed description, please refer to the relevant descriptions in the method embodiments shown in Figures 3-4, 6A and 8A, which will not be repeated here.

[0310] Figure 10 shows a communication device 1000 provided in an embodiment of this application. The communication device shown in Figure 10 can be a hardware circuit implementation of the communication device shown in Figure 9. This communication device 1000 can be applied to the flowcharts shown above to perform the functions of the first or second device in the above method embodiments. For ease of explanation, Figure 10 only shows the main components of the communication device.

[0311] As shown in Figure 10, the communication device 1000 includes a communication interface 1001 and a processor 1002. The communication interface 1001 and the processor 1002 are coupled to each other. It is understood that the communication interface 1001 can be a transceiver or an input / output interface, or an interface circuit such as a transceiver circuit. Optionally, the communication device 1000 may further include a memory 1003 for storing instructions executed by the processor 1002, or storing input data required by the processor 1002 to execute instructions, or storing data generated after the processor 1002 executes instructions.

[0312] When the communication device 1000 is used to implement the methods shown in Figures 3-4, 6A, and 8A, the communication interface 1001 is used to implement the functions of the communication unit 901, and the processor 1002 is used to implement the functions of the processing unit 902.

[0313] This embodiment does not limit the specific connection medium between the communication interface 1001, processor 1002, and memory 1003. In Figure 10, the memory 1003, processor 1002, and communication interface 1001 are connected via a communication bus 1004, which is represented by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The communication bus 1004 can be divided into an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 10, but this does not indicate that there is only one bus or one type of bus.

[0314] When the aforementioned communication device is a chip, Figure 11 shows a simplified schematic diagram of the chip's device structure. The chip 1100 includes an interface circuit 1101 and one or more processors 1102. Optionally, the chip 1100 may also include a bus. Wherein:

[0315] Processor 1102 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the method for determining the service node information described above can be completed by the integrated logic circuitry in the hardware of processor 1102 or by instructions in software form. Processor 1102 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor.

[0316] The interface circuit 1101 can be used to send or receive data, instructions or information. The processor 1102 can use the data, instructions or other information received by the interface circuit 1101 to process the data, instructions or other information, and can send the processed information out through the interface circuit 1101.

[0317] Optionally, chip 1100 also includes memory 1103, which may include read-only memory and random access memory, and provides operation instructions and data to the processor. A portion of memory 1103 may also include non-volatile random access memory (NVRAM).

[0318] Optionally, the memory stores executable software modules or data structures, and the processor can execute corresponding operations by calling the operation instructions stored in the memory (which may be stored in the operating system).

[0319] Optionally, the chip can be used in the first or second device involved in the embodiments of this application. Optionally, the interface circuit 1101 can be used to output the execution result of the processor 1102. For the communication methods provided by one or more embodiments of this application, please refer to the foregoing embodiments, which will not be repeated here.

[0320] It should be noted that the functions of the interface circuit 1101 and the processor 1102 can be implemented through hardware design, software design, or a combination of hardware and software; no restrictions are imposed here.

[0321] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first or second device in the above method embodiments.

[0322] For example, when the computer program is executed by a computer, it enables the computer to implement the method performed by the first or second device in the above method embodiments.

[0323] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the method executed by the first or second device in the above method embodiments.

[0324] This application also provides a chip, including a processor, for calling computer programs or computer instructions stored in the memory, so that the processor executes the communication method of the implementation shown in Figures 3-4, 6A and 8A.

[0325] In one possible implementation, the input of the chip corresponds to the receiving operation in the implementation shown in Figures 3-4, 6A, and 8A, and the output of the chip corresponds to the transmitting operation in the implementation shown in Figures 3-4, 6A, and 8A.

[0326] Alternatively, the processor is coupled to the memory via an interface.

[0327] Optionally, the chip also includes a memory that stores computer programs or computer instructions.

[0328] The processor mentioned above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of a program for a communication method of the embodiments / implementations shown in Figures 3-4, 6A, and 8A. The memory mentioned above can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM).

[0329] It should be noted that, for the sake of convenience and brevity, the explanations and beneficial effects of the relevant content in any of the communication devices provided above can be referred to the corresponding service node information determination method embodiments provided above, and will not be repeated here.

[0330] In this application, the communication devices may further include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system layer may be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0331] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0332] Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments of this application can be implemented in hardware, firmware, or a combination thereof. When implemented in software, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a computer. For example, but not limited to, computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a computer. Furthermore, any connection can suitably be a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used in embodiments of this application, disks and discs include compact discs (CDs), laser discs, optical discs, digital video discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while discs optically copy data using lasers. The combinations above should also be included within the scope of protection for computer-readable media.

[0333] In summary, the above descriptions are merely embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the disclosure of this application should be included within the scope of protection of this application.

Claims

1. A communication method characterized by comprising: The method is applied to a first device or a chip of the first device, and includes: sending first information to a second device, the first information being used for requesting establishment of a preemption session; receiving second information from the second device, the second information being used for indicating that the preemption session is successfully established; based on the preemption session, receiving at least one first physical layer protocol data unit (PPDU) sent by the second device; the at least one first PPDU carries data of a first service, and a length of the first PPDU is less than a first preset value; and / or based on the preemption session, sending at least one second physical layer protocol data unit (PPDU) to the second device; the at least one second PPDU carries data of a second service, and a length of the second PPDU is less than a second preset value.

2. The method of claim 1, wherein, The first information includes one or more of the following: first indication information and second indication information; wherein the first indication information indicates service identification information corresponding to the first service, and the second indication information indicates service identification information corresponding to the second service.

3. The method of claim 1, wherein, The first information includes one or more of the following: third indication information and fourth indication information; wherein the third indication information indicates service identification information corresponding to a third service, the fourth indication information indicates service identification information corresponding to a fourth service, the first service is a service other than the third service, and the second service is a service other than the fourth service.

4. The method according to any one of claims 1 to 3, characterized in that, The first information further includes fifth indication information; the fifth indication information indicates one or more of the following: the first preset value and the second preset value.

5. The method according to any one of claims 1 to 4, characterized in that, The first information further includes sixth indication information. The sixth indication information indicates whether seventh indication information is allowed to be carried in acknowledgement information of the at least one second PPDU after the preemption session is established, the seventh indication information indicating that there is data of a low-latency service to be transmitted between the second device and a third device.

6. The method according to any one of claims 1 to 5, characterized in that, The second information includes eighth indication information; The eighth indication information indicates whether ninth indication information is allowed to be carried in acknowledgement information of the at least one first PPDU after the preemption session is established, the ninth indication information indicating that there is data of a low-latency service to be transmitted between the first device and a third device.

7. The method of claim 2 or 3, wherein, The service identification information is any of the following: a traffic identification (TID) list and a TID bitmap; wherein the TID list includes at least one TID, and the TID bitmap includes at least one bit, the at least one bit being used to represent the at least one TID one by one.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: after receiving the at least one first PPDU sent by the second device, sending first acknowledgement information of the at least one first PPDU to the second device, the first acknowledgement information carrying third information, the third information being used for indicating a time length required by the first device to send data of a low-latency service; and / or After sending the at least one second PPDU to the second device, receiving second acknowledgement information of the at least one second PPDU sent by the second device, the second acknowledgement information carrying fourth information, the fourth information being used to indicate a time length required by the second device to send low-latency service data.

9. The method of claim 8, wherein, The first acknowledgement information further comprises fifth information, wherein the fifth information indicates that, when the TXS mode requested by the first device is the first mode, the first device has low-latency service data to be sent to the second device; the fifth information indicates that, when the TXS mode requested by the first device is the second mode, the first device has low-latency service data to be sent to the second device and / or the third device; and / or The second acknowledgement information further comprises sixth information, the sixth information indicating that, when the TXS mode requested by the second device is the first mode, the second device has low-latency service data to be sent to the first device; the sixth information indicating that, when the TXS mode requested by the second device is the second mode, the second device has low-latency service data to be sent to the first device and / or the third device.

10. The method of claim 9, wherein, The first acknowledgement information is a first multi-user block acknowledgement (MBA) frame, and the first MBA frame comprises first association identifier (AID) service identifier information, wherein the first AID service identifier information comprises the third information and / or the fifth information; and / or The second acknowledgement information is a second multi-user block acknowledgement (MBA) frame, and the second MBA frame comprises second AID service identifier information, wherein the second AID service identifier information comprises the fourth information and / or the sixth information. The method further comprises:

11. The method according to any one of claims 1 to 10, characterized in that, receiving a first trigger frame sent by the second device, the first trigger frame being used to trigger the first device to send the second PPDU corresponding to the second service to the second device, the length of the second PPDU being less than the second preset value. The first device is a non-access point, and the second device is an access point.

12. The method according to any one of claims 1 to 11, characterized in that, The method is applied to a second device or a chip of the second device, and comprises:

13. A method of communication, comprising: receiving first information from a first device, the first information being used to request to establish a pre-emption session; sending second information to the first device, the second information being used to indicate that the pre-emption session is successfully established; sending at least one first physical layer protocol data unit (PPDU) to the first device based on the pre-emption session, the at least one first PPDU carrying data of a first service, and the length of the first PPDU being less than a first preset value; and / or receiving at least one second PPDU sent by the first device based on the pre-emption session, the at least one second PPDU carrying data of a second service, and the length of the second PPDU being less than a second preset value. The first information comprises one or more of the following:

14. The method of claim 13, wherein, first indication information and second indication information. ​ The first indication information indicates service identification information corresponding to the first service, and the second indication information indicates service identification information corresponding to the second service.

15. The method of claim 13, wherein, The first information includes one or more of the following: Third indication information and fourth indication information. The third indication information indicates service identification information corresponding to a third service, and the fourth indication information indicates service identification information corresponding to a fourth service. The first service is a service other than the third service, and the second service is a service other than the fourth service.

16. The method according to any one of claims 13 to 15, characterized in that, The first information further includes fifth indication information. The fifth indication information indicates one or more of the following: The first preset value and the second preset value.

17. The method according to any one of claims 14 to 16, characterized in that, The first information further includes sixth indication information. The sixth indication information indicates whether seventh indication information is allowed to be carried in acknowledgement information of the at least one second PPDU after the pre-emption session is established. The seventh indication information indicates that there is data of low-latency service to be transmitted between the second device and a third device.

18. The method according to any one of claims 13 to 17, characterized in that, The second information includes eighth indication information. The eighth indication information indicates whether ninth indication information is allowed to be carried in acknowledgement information of the at least one first PPDU after the pre-emption session is established. The ninth indication information indicates that there is data of low-latency service to be transmitted between the first device and a third device.

19. The method of claim 14 or 15, wherein, The service identification information is any of the following: A service identification TID list and a service identification TID bitmap. The TID list includes at least one TID, and the TID bitmap includes at least one bit. The at least one bit is used to represent the at least one TID one by one.

20. The method of any one of claims 13-19, wherein, The method further includes: After the at least one first PPDU is sent to the first device, receiving first acknowledgement information of the at least one first PPDU sent by the first device. The first acknowledgement information carries third information used to indicate a time length required by the first device to send data of low-latency service; and / or After the at least one second PPDU sent by the second device is received, sending second acknowledgement information of the at least one second PPDU to the first device. The second acknowledgement information carries fourth information used to indicate a time length required by the second device to send data of low-latency service.

21. The method of claim 20, wherein, The first acknowledgement information further includes fifth information. When the TXS mode requested by the first device is a first mode, the fifth information indicates that the first device has data of low-latency service to be sent to the second device. When the TXS mode requested by the first device is a second mode, the fifth information indicates that the first device has data of low-latency service to be sent to the second device and / or a third device; and / or The second confirmation information further comprises sixth information. When the TXS mode requested by the second device is the first mode, the sixth information indicates that the second device has data of low latency service to be sent to the first device. When the TXS mode requested by the second device is the second mode, the sixth information indicates that the second device has data of low latency service to be sent to the first device and / or the third device.

22. The method of claim 21, wherein, The first confirmation information is a first multi-user block acknowledgement (MBA) frame, and the first MBA frame comprises first association identifier (AID) service identifier information, wherein the first AID service identifier information comprises the third information and / or the fifth information. And / or The second confirmation information is a second multi-user block acknowledgement (MBA) frame, and the second MBA frame comprises second AID service identifier information, wherein the second AID service identifier information comprises the fourth information and / or the sixth information.

23. The method of any one of claims 13-22, wherein, The method further comprises: sending a first trigger frame to the first device, wherein the first trigger frame is used to trigger the first device to send the second PPDU corresponding to the second service to the second device, and the length of the second PPDU is less than the second preset value.

24. The method of any one of claims 13-23, wherein, The method further comprises: sending a second trigger frame to the first device, wherein the second trigger frame comprises a first field, and the first field is used to indicate a first time length allocated by the second device for low latency service data, and the first time length is equal to a time length required by the first device to send data of low latency service.

25. The method of any one of claims 13-24, wherein, The first device is a non-access point, and the second device is an access point.

26. A communications device, characterized by The apparatus comprises units or modules for performing the method of any one of claims 1-12, or units or modules for performing the method of any one of claims 13-25.

27. A communications device, characterized by The apparatus comprises a processor and a memory, wherein the memory is configured to store program instructions, and the processor is configured to execute the program instructions to cause the method of any one of claims 1-12 to be performed, or the processor is configured to execute the program instructions to cause the method of any one of claims 13-25 to be performed.

28. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer readable programs or instructions, which, when executed on a communication device, cause the method of any one of claims 1-12 to be performed, or cause the method of any one of claims 13-25 to be performed.

29. A computer program product, characterised in that, The computer program product comprises computer programs or instructions, which, when executed on a computer, cause the computer to perform the method of any one of claims 1-12, or cause the computer to perform the method of any one of claims 13-25.

30. A chip, characterized by The chip is configured to read and execute computer programs or instructions in the memory to implement the method of any one of claims 1-25.

Images