Communication method and communication device

Abstract

An embodiment of this application discloses a communication method for optimizing channel access parameters. The method includes: A first station sends a request frame to an access point. The request frame is used to request to obtain channel priority access. The request frame carries a first parameter set. The first parameter set includes MU EDCA parameters that the first station intends to use to perform channel contention. The first station receives a response frame to the request frame. The first station is an EPCS station. The first station performs channel access by using a MU EDCA mechanism. In an embodiment of this application, the first parameter set includes MU EDCA parameters that the first station intends to use to perform channel contention. A request frame carrying the first parameter set is transmitted. In this way, channel contention is performed by using parameters with a higher channel access priority.

Description

[Technical Field]

[0001] [ Technical Field] This application relates to the field of communications, and in particular to communication methods and devices. [Background technology]

[0002] Emergency preparedness communications service (EPCS) is a service with extremely high requirements for communication delay, such as in crisis scenarios such as fires and earthquakes. For EPCS, the wireless local area network standard 802.11be defines a priority access mechanism, which allows EPCS stations to access the channel as quickly as possible to ensure priority transmission of emergency services. EPCS stations are stations that need to perform EPCS. Therefore, solutions that enable EPCS stations to access the channel as quickly as possible in various scenarios need to be researched. Summary of the Invention

[0003] SUMMARY OF THE INVENTION The embodiments of this application disclose a communication method and a communication device.

[0004] According to a first aspect, an embodiment of the present application provides a communication method, the method including: transmitting a request frame to an access point, the request frame being used to request obtaining channel priority access, the request frame carrying a first parameter set, the first parameter set including multi-user MU enhanced distributed channel access (EDCA) parameters intended for use by the first station to perform channel contention; and receiving a response frame to the request frame. In the first aspect and a possible implementation thereof, the executing entity is the first station.

[0005] In this embodiment of the present application, the first parameter set includes MU EDCA parameters that the first station intends to use to perform channel contention. A request frame carrying the first parameter set is transmitted. In this manner, channel contention is performed by using parameters with a higher channel access priority.

[0006] In a possible implementation, the method further includes a step of performing channel contention by using parameters in the first parameter set after a data frame triggered based on a trigger frame of the access point.

[0007] In this implementation, after a data frame triggered by a trigger frame of an access point is transmitted, channel contention is performed by using parameters in a first parameter set, and the first station has a higher channel access priority than a general station.

[0008] In a possible implementation, performing channel contention by using parameters in the first parameter set includes performing channel contention for a first duration by using parameters in the first parameter set, where the first duration is obtained based on the parameters in the first parameter set.

[0009] In this implementation, channel contention is performed for a first duration by using parameters in a first parameter set, following the MU EDCA mechanism, and thus relative fairness can be maintained for the first station and legacy stations (stations that do not meet the 802.11ax standard).

[0010] The communication method in the first aspect may be replaced as follows: A first station transmits a request frame to an access point. The request frame carries a second parameter set. The second parameter set includes MU EDCA parameters that the second station intends to use to perform channel contention. The second station and the first station belong to the same multilink station device. The first station receives a response frame from the access point to the request frame. The response frame carries a fourth parameter set. The fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention. The fourth parameter set may be the same as or different from the second parameter set.

[0011] In this embodiment of the present application, the second parameter set includes MU EDCA parameters that the second station intends to use to perform channel contention. A request frame carrying the second parameter set is transmitted. In this manner, channel contention is performed by using parameters with a higher channel access priority.

[0012] According to a second aspect, an embodiment of the present application provides a communication method, the method including: transmitting a request frame to an access point, the request frame being used to request obtaining channel priority access; and receiving a response frame to the request frame, the response frame carrying a third parameter set, the third parameter set including MU EDCA parameters to be used by the first station to perform channel contention. In other words, the third parameter set includes MU EDCA parameters that the access point allows the first station to use to perform channel contention. In the second aspect and a possible implementation thereof, the executing entity is the first station.

[0013] In this embodiment of the application, the response frame carries a third parameter set, and the first station can obtain the MU EDCA parameters to be used by the first station to perform channel contention through receiving the response frame.

[0014] In a possible implementation, the method further includes a step of performing channel contention by using parameters in a third parameter set after a data frame triggered based on a trigger frame of the access point.

[0015] In this implementation, after the triggered data frame is transmitted based on the trigger frame of the access point, the channel contention is performed by using the parameters in the third parameter set, and the first station has a higher channel access priority than the general station.

[0016] In a possible implementation, performing channel contention by using parameters in a third parameter set includes performing channel contention for a third duration by using parameters in the third parameter set, where the third duration is obtained based on the parameters in the third parameter set.

[0017] In this implementation, channel contention is performed for a third duration by using parameters in a third parameter set, which follows the MU EDCA mechanism, and thus relative fairness can be maintained for the first station and legacy stations (stations that do not meet the 802.11ax standard).

[0018] According to a third aspect, an embodiment of the present application provides another communication method, the method including: transmitting a request frame to an access point, the request frame being used to request obtaining channel priority access; receiving a response frame to the request frame; and determining an MU EDCA parameter set to be used by a first station based on the EDCA parameter set carried in the response frame and the beacon frame. In the third aspect and a possible implementation thereof, the executing entity is the first station.

[0019] In this embodiment of this application, the MU EDCA parameter set to be used by the first station is determined based on the EDCA parameter set carried in the response frame and the beacon frame to obtain the MU EDCA parameter set with higher channel access priority.

[0020] In a possible implementation, the MU EDCA parameter set to be used by the first station is used to perform channel contention after the data frame triggered based on the trigger frame of the access point is successfully transmitted.

[0021] In this implementation, the MU EDCA parameter set to be used by the first station is used to perform channel contention after the data frame triggered based on the trigger frame of the access point is successfully transmitted, ensuring that the first station has a higher channel access priority.

[0022] In a possible implementation, the step of determining the MU EDCA parameter set to be used by the first station further includes the step of determining the MU EDCA parameter set to be used by the first station based on the MU EDCA parameter set in the beacon frame.

[0023] This implementation can solve the following problems: The MU EDCA parameter set with higher channel access priority cannot be determined accurately and quickly based only on the EDCA parameter set carried in the beacon frame.

[0024] In a possible implementation, the step of determining the MU EDCA parameter set to be used by the first station based on the MU EDCA parameter set in the beacon frame includes the step of determining the MU EDCA parameter set to be used by the first station based on the MU EDCA timer in the MU EDCA parameter set.

[0025] In this implementation, the MU EDCA parameter set with higher channel access priority can be determined accurately and quickly.

[0026] In a possible implementation, the MU EDCA parameter set to be used by the first station is used to perform channel contention within a second duration after the data frame triggered based on the trigger frame of the access point is successfully transmitted, and the second duration is obtained based on parameters in the MU EDCA parameter set.

[0027] In a possible implementation, the request frame is an EPCS priority access allowed request frame and the response frame is an EPCS priority access allowed response frame.

[0028] In this implementation, the request frame is an Emergency Presence Communication Service (EPCS) priority access request frame, and the response frame is an EPCS priority access response frame. Because both the request frame and the response frame are existing frames, no additional signaling needs to be sent for receiving and transmitting the request frame and the response frame.

[0029] According to a fourth aspect, an embodiment of the present application provides another communication method, the method including: receiving a request frame from a first station, the request frame being used to request obtaining channel priority access, the request frame carrying a first parameter set, the first parameter set including MU EDCA parameters that the first station intends to use to perform channel contention; and transmitting a response frame to the request frame to the first station. In the fourth aspect and a possible implementation manner of the fourth aspect, the executing entity is an access point.

[0030] In this embodiment of the present application, the first parameter set includes MU EDCA parameters that the first station intends to use to perform channel contention, and a request frame carrying the first parameter set may be received to obtain the MU EDCA parameters that the first station intends to use to perform channel contention.

[0031] In a possible implementation of the first or fourth aspect, the first parameter set is included in a link information field in a multilink element MLE in the request frame, or the first parameter set is included in an MU EDCA parameter set field in the request frame.

[0032] In this implementation, the first parameter set is included in the link information field in the multilink element (MLE) in the request frame to independently indicate the MU EDCA parameter set that the first station intends to use to perform channel contention, and the first parameter set is included in the MU EDCA parameter set field in the request frame, allowing the access point to quickly obtain the first parameter set from the MU EDCA parameter set field in the request frame.

[0033] In a possible implementation of the first or fourth aspect, the request frame further carries a second parameter set, which includes MU EDCA parameters that the second station intends to use to perform channel contention, and the second station and the first station belong to the same multilink station device.

[0034] In this implementation, the request frame further carries the second parameter set, and the second station may inform the access point of the second parameter set that the second station intends to use without sending a request frame, thereby reducing signaling overhead.

[0035] In a possible implementation of the first or fourth aspect, the second parameter set is included in a link information field in an MLE in a request frame.

[0036] In this implementation, the second parameter set is included in the link information field in the MLE in the request frame to independently indicate the MU EDCA parameters that the second station intends to use to perform channel contention.

[0037] In a possible implementation of the first or fourth aspect, the response frame carries a third parameter set, which includes MU EDCA parameters to be used by the first station to perform channel contention, and which is different from the first parameter set.

[0038] In this implementation, the response frame carries a third parameter set, so that the first station performs channel contention by using parameters in the third parameter set to ensure channel access priority.

[0039] In a possible implementation of the first or fourth aspect, the third parameter set is a subset of the first parameter set.

[0040] In this implementation, the third parameter set is a subset of the first parameter set. The first parameter set is determined by the first station from its perspective, without taking into account the access point and other stations. The third parameter set is determined by the access point from a holistic perspective, with multiple stations being comprehensively considered. The first station performs channel contention by using parameters in the third parameter set to ensure channel access priority and reduce the impact on other stations.

[0041] In a possible implementation of the first or fourth aspect, the first parameter set is a subset of the third parameter set.

[0042] In this implementation, the first parameter set is a subset of the third parameter set, and compared with when the first station performs channel contention by using parameters in the first parameter set, the first station has a higher channel access priority when performing channel contention by using parameters in the third parameter set.

[0043] In a possible implementation of the first or fourth aspect, the response frame carries a third parameter set, which includes MU EDCA parameters to be used by the first station to perform channel contention, and which is the same as the first parameter set.

[0044] In this implementation, the response frame carries a third parameter set, so that the first station performs channel contention by using parameters in the third parameter set to ensure channel access priority.

[0045] In a possible implementation of the first or fourth aspect, the third parameter set is included in the link information field in the MLE in the response frame, or the third parameter set is included in the MU EDCA parameter set field in the response frame.

[0046] In this implementation, the third parameter set is included in the link information field in the MLE in the response frame to independently indicate the MU EDCA parameters to be used by the first station to perform channel contention, and the third parameter set is included in the MU EDCA parameter set field in the response frame, allowing the first station to quickly acquire the third parameter set from the MU EDCA parameter set field in the response frame.

[0047] In a possible implementation of the first or fourth aspect, the response frame further carries a fourth parameter set, which includes MU EDCA parameters to be used by the second station to perform channel contention, and the second station and the first station belong to the same multilink station device.

[0048] In this implementation, the response frame further carries a fourth parameter set, and the access point does not need to send the response frame to the second station separately, reducing signaling overhead.

[0049] In a possible implementation of the first or fourth aspect, the fourth parameter set is a subset of the second parameter set.

[0050] In this implementation, the fourth parameter set is a subset of the second parameter set. The second parameter set is determined by the second station from its perspective, without taking into account the access point and other stations. The fourth parameter set is determined by the access point from a holistic perspective, with multiple stations being comprehensively considered. The second station performs channel contention by using parameters in the fourth parameter set to ensure channel access priority and reduce the impact on other stations.

[0051] In a possible implementation of the first or fourth aspect, the second parameter set is a subset of the fourth parameter set.

[0052] In this implementation, the second parameter set is a subset of the fourth parameter set, and the second station has a higher channel access priority when performing channel contention using parameters in the fourth parameter set than when performing channel contention using parameters in the second parameter set.

[0053] In a possible implementation of the first or fourth aspect, the response frame carries a fourth parameter set, which includes MU EDCA parameters to be used by the second station to perform channel contention, and which is the same as the second parameter set.

[0054] In this implementation, the response frame carries a fourth parameter set, which causes the second station to perform channel contention by using parameters in the fourth parameter set to ensure channel access priority.

[0055] In a possible implementation of the first or fourth aspect, the fourth parameter set is included in the link information field in the MLE in the response frame.

[0056] In this implementation, a fourth parameter set is included in the link information field in the MLE in the response frame to independently indicate the MU EDCA parameters to be used by the second station to perform channel contention.

[0057] In a possible implementation of the first or fourth aspect, the request frame is an emergency alert communication service (EPCS) priority access available request frame, and the response frame is an EPCS priority access available response frame.

[0058] In this implementation, the request frame is an Emergency Presence Communication Service (EPCS) priority access request frame, and the response frame is an EPCS priority access response frame. Because both the request frame and the response frame are existing frames, no additional signaling needs to be sent for receiving and transmitting the request frame and the response frame.

[0059] In a possible implementation of the first or fourth aspect, the channel access priority of the first parameter set is higher than the channel access priority of the MU EDCA parameter set to be used by the general station. The first station is an EPCS station. The general station is a non-EPCS station. In other words, the general station does not belong to the EPCS station.

[0060] The communication method in the fourth aspect may be replaced as follows: The access point receives a request frame from a first station. The request frame carries a second parameter set. The second parameter set includes MU EDCA parameters that the second station intends to use to perform channel contention. The second station and the first station belong to the same multilink station device. The access point transmits a response frame to the request frame to the first station. The response frame carries a fourth parameter set. The fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention. The fourth parameter set may be the same as or different from the second parameter set.

[0061] In this embodiment of the application, the fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention, thereby causing the second station to perform channel contention by using parameters with a higher channel access priority.

[0062] According to a fifth aspect, an embodiment of the present application provides another communication method. The method includes: receiving a request frame from a first station, the request frame being used to request obtaining channel priority access; and transmitting a response frame to the request frame to the first station, the response frame carrying a third parameter set, the third parameter set including MU EDCA parameters to be used by the first station to perform channel contention. In other words, the third parameter set includes MU EDCA parameters that the access point allows the first station to use to perform channel contention. In the fifth aspect and a possible implementation of the fifth aspect, the executing entity is an access point.

[0063] In this embodiment of the present application, the third parameter set includes MU EDCA parameters to be used by the first station to perform channel contention, and a response frame carrying the third parameter set is sent to the first station, thereby causing the first station to perform channel contention by using the third parameter set to obtain a higher channel access priority.

[0064] In a possible implementation of the second or fifth aspect, the third parameter set is included in the link information field in the MLE in the response frame, or the third parameter set is included in the MU EDCA parameter set field in the response frame.

[0065] In this implementation, the third parameter set is included in the link information field in the MLE in the response frame to independently indicate the MU EDCA parameters to be used by the first station to perform channel contention, and the third parameter set is included in the MU EDCA parameter set field in the response frame, allowing the first station to quickly acquire the third parameter set from the MU EDCA parameter set field in the response frame.

[0066] In a possible implementation of the second or fifth aspect, the response frame further carries a fourth parameter set, which includes MU EDCA parameters to be used by the second station to perform channel contention, and the second station and the first station belong to the same multilink station device.

[0067] In this implementation, the response frame further carries a fourth parameter set, and the access point does not need to send the response frame to the second station separately, reducing signaling overhead.

[0068] In a possible implementation of the second or fifth aspect, the fourth parameter set is included in the link information field in the MLE in the response frame.

[0069] In this implementation, a fourth parameter set is included in the link information field in the MLE in the response frame to independently indicate the MU EDCA parameters to be used by the second station to perform channel contention.

[0070] In a possible implementation of the second or fifth aspect, the request frame is an emergency alert communication service (EPCS) priority access available request frame, and the response frame is an EPCS priority access available response frame.

[0071] In this implementation, the request frame is an Emergency Presence Communication Service (EPCS) priority access request frame, and the response frame is an EPCS priority access response frame. Because both the request frame and the response frame are existing frames, no additional signaling needs to be sent for receiving and transmitting the request frame and the response frame.

[0072] In a possible implementation of the second or fifth aspect, the channel access priority of the third parameter set is higher than the channel access priority of the MU EDCA parameter set used by the general station, and the first station is an EPCS station.

[0073] According to a sixth aspect, an embodiment of the present application provides a communication device configured to perform the method of the first aspect, the second aspect, the third aspect or any possible implementation thereof, the communication device comprising a corresponding unit configured to perform the method of the first aspect, the second aspect, the third aspect or any possible implementation thereof.

[0074] For example, the communication device may include a transceiver unit and a processing unit. The communication device may include a first station in the first aspect, the second aspect, or the third aspect, such as a non-AP MLD, a STA, or a chip in a non-AP MLD such as a Wi-Fi chip.

[0075] According to a seventh aspect, an embodiment of the present application provides a communication device configured to perform the method of the fourth aspect, the fifth aspect or any possible implementation thereof, the communication device comprising a corresponding unit configured to perform the method of the fourth aspect, the fifth aspect or any possible implementation thereof.

[0076] For example, the communication device may include a transceiver unit and a processing unit. The communication device may include an access point according to the fourth or fifth aspect, for example, an AP MLD, an AP, or a chip in an AP MLD such as a Wi-Fi chip.

[0077] According to an eighth aspect, an embodiment of the present application provides a communications device, the communications device including a processor configured to perform the method of the first aspect, the second aspect, the third aspect, or any possible implementation thereof.

[0078] In the process of executing the above method, the process of transmitting information and the process of receiving information in the above method may be understood as a process of outputting information by a processor and a process of receiving input information by a processor. When outputting information, the processor outputs the information to the transceiver, thereby causing the transceiver to transmit the information. After the information is output by the processor, other processing may need to be performed on the information before it arrives at the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs the information to the processor. Furthermore, after the transceiver receives information, other processing may need to be performed on the information before it is input to the processor.

[0079] Based on the above principle, for example, sending a request frame mentioned in the above method may be understood as outputting the request frame by the processor, and in another example, receiving a response frame may be understood as receiving an input response frame by the processor.

[0080] Operations such as transmit, send, and receive related to a processor may also be more generally understood as operations such as output, receive, and input of a processor unless otherwise specified, or where the operations do not contradict the actual functionality or internal logic of the operations in the relevant description.

[0081] In the implementation process, the processor may be a dedicated processor for executing these methods, or a processor that executes computer instructions in memory to perform these methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM). The memory and the processor may be integrated on the same chip, or may be located on different chips. The type of memory and the manner in which the memory and the processor are located are not limited in this embodiment of this application.

[0082] In a possible implementation, the memory is located external to the communication device.

[0083] In a possible implementation, the memory is located within the communication device.

[0084] In this embodiment of the application, the processor and the memory may alternatively be integrated into one component, in other words, the processor and the memory may alternatively be integrated together.

[0085] In a possible implementation, the communication device further includes a transceiver configured to receive and / or transmit signals. For example, the transceiver may be configured to transmit a request frame. In another example, the transceiver may further be configured to receive a response frame, etc.

[0086] In this embodiment of the present application, the communication device may be a first station in the first aspect, the second aspect, or the third aspect. For example, the first station may be a non-AP MLD or a STA.

[0087] According to a ninth aspect, an embodiment of the present application provides a communications device, the communications device including a processor configured to execute a program stored in a memory, the program, when executed, enabling the communications device to perform the method of the fourth aspect, the fifth aspect, or any possible implementation thereof.

[0088] In a possible implementation, the memory is located external to the communication device.

[0089] In a possible implementation, the memory is located within the communication device.

[0090] In this embodiment of the application, the processor and the memory may alternatively be integrated into one component, in other words, the processor and the memory may alternatively be integrated together.

[0091] In a possible implementation, the communication device further includes a transceiver configured to receive and / or transmit signals. For example, the transceiver may be configured to receive a request frame. In another example, the transceiver may further be configured to transmit a response frame, etc.

[0092] In this embodiment of the present application, the communication device may be an access point in the fourth aspect or the fifth aspect. For example, accessThe point may be an AP MLD or an AP.

[0093] According to a tenth aspect, an embodiment of the present application provides a communication device. The communication device includes a processing circuit and an interface circuit. The interface circuit is configured to acquire data or output data. The processing circuit is configured to perform a corresponding method in the first aspect or any possible implementation manner of the first aspect, or the processing circuit is configured to perform a corresponding method in the second aspect or any possible implementation manner of the second aspect, or the processing circuit is configured to perform a corresponding method in the third aspect or any possible implementation manner of the third aspect.

[0094] According to an eleventh aspect, an embodiment of the present application provides a communication device. The communication device includes a processing circuit and an interface circuit. The interface circuit is configured to acquire data or output data. The processing circuit is configured to perform a corresponding method in any possible implementation manner of the fourth aspect or the fourth aspect, or the processing circuit is configured to perform a corresponding method in any possible implementation manner of the fifth aspect or the fifth aspect.

[0095] According to a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, which, when run on a computer, performs the method of the first aspect, the second aspect, the third aspect, or any possible implementation thereof.

[0096] According to a thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, which, when run on a computer, performs the method of the fourth aspect, the fifth aspect, or any possible implementation thereof.

[0097] According to a fourteenth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program or computer code, which, when run on a computer, performs the method of the first aspect, the second aspect, the third aspect or any possible implementation thereof.

[0098] According to a fifteenth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program or computer code, which, when run on a computer, performs the method of the fourth aspect, the fifth aspect, or any possible implementation thereof.

[0099] According to a sixteenth aspect, an embodiment of the present application provides a multi-link communication system. The multi-link communication system includes a non-AP MLD and an AP MLD. Optionally, the non-AP MLD is configured to perform the method of the first aspect or any possible implementation manner of the first aspect, and the AP MLD is configured to perform the method of the fourth aspect or any possible implementation manner of the fourth aspect. Optionally, the non-AP MLD is configured to perform the method of the second aspect or any possible implementation manner of the second aspect, and the AP MLD is configured to perform the method of the fifth aspect or any possible implementation manner of the fifth aspect.

[0100] According to a seventeenth aspect, an embodiment of the present application provides a multi-link communication system. The multi-link communication system includes a STA and an AP MLD. Optionally, the STA is configured to perform the method of the first aspect or any possible implementation manner of the first aspect, and the AP MLD is configured to perform the method of the fourth aspect or any possible implementation manner of the fourth aspect. Optionally, the non-AP MLD is configured to perform the method of the second aspect or any possible implementation manner of the second aspect, and the AP MLD is configured to perform the method of the fifth aspect or any possible implementation manner of the fifth aspect. The AP MLD can be replaced with an AP. [Brief explanation of the drawings]

[0101] In order to describe the technical solutions in the embodiments or background art of this application more clearly, the following briefly describes the accompanying drawings for describing the embodiments or background art of this application. [Figure 1A] 1 is a schematic diagram of a multi-link communication scenario according to an embodiment of the present application; [Figure 1B] 1 is a schematic diagram of a multi-link communication scenario according to an embodiment of the present application; [Figure 1C] 1 is a schematic diagram of a multi-link communication scenario according to an embodiment of the present application; [Figure 2] An example of the basic access process of the CSMA / CA mechanism is shown below. [Figure 3] 1 shows an example of a backoff process for multiple STAs under DCF. [Figure 4] An example of exponential growth of CW is shown. [Figure 5] 1 illustrates examples of EDCA parameter sets for services of different ACs according to an embodiment of this application. [Figure 6] An example of an MLE frame body is shown below. [Figure 7] 1 is a schematic diagram of the working principle of the MU EDCA mechanism according to an embodiment of this application; [Figure 8]1 is a flowchart of a communication method according to an embodiment of the present application. [Figure 9A] 1 is an example of a format of a priority access multi-link element field according to an embodiment of the present application. [Figure 9B] 1 is an example of a format of a priority access multi-link element field according to an embodiment of the present application. [Figure 9C] 1 is an example of a format of a priority access multi-link element field according to an embodiment of the present application. [Figure 10] 4 is a flowchart of another communication method according to an embodiment of the present application. [Figure 11] 4 is a flowchart of another communication method according to an embodiment of the present application. [Figure 12] 4 is a flowchart of another communication method according to an embodiment of the present application. [Figure 13] 4 is a flowchart of another communication method according to an embodiment of the present application. [Figure 14] 4 is a flowchart of another communication method according to an embodiment of the present application. [Figure 15] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present invention; [Figure 16] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present invention; [Figure 17] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0102] In the specification, claims, or accompanying drawings of this application, the terms "first," "second," etc. are intended only to distinguish between different objects and do not indicate a particular order. Furthermore, the terms "include," "comprise," and any variations thereof are intended to cover a 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 recited steps or units, but may optionally further include other unrecited steps or units, or may optionally further include other inherent steps or units of the process, method, product, or device.

[0103] The term "embodiment" referred to in this specification means that a particular feature, structure, or characteristic described with reference to this embodiment may be included in at least one embodiment of this application. Phrases appearing in various places in this specification do not necessarily refer to the same embodiment, nor are they an independent or optional embodiment exclusive of other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described in this specification may be combined with other embodiments.

[0104] The terms used in the following embodiments of this application are intended merely to describe particular embodiments and are not intended to limit this application. As used in this specification and the appended claims of this application, the terms "one," "a," "the," "the foregoing," "this," and "the one" are also intended to include the plural, unless the context clearly dictates otherwise. It should be further understood that the term "and / or" used in this application denotes and includes any or all possible combinations of one or more listed items. For example, "A and / or B" may represent the following three cases: only A is present, only B is present, and both A and B are present, and A and B may be singular or plural. In this application, the term "at least one" means one or more, and "plurality" means two or more. The phrase "at least one of the following items" or similar expressions denotes any combination of these items, including any combination of singular items or plural items. For example, at least one of a, b, and c may represent a, b, or c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may each be singular or plural.

[0105] First, the terms and technical features in the embodiments of this application will be described below.

[0106] Multi-link Communication

[0107] With the development of wireless technology, more and more wireless devices support multi-link communication. For example, some wireless devices may simultaneously communicate on the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, or may simultaneously communicate on different channels of the same frequency band. In this way, the communication rate between wireless devices can be improved. A device that supports multi-link communication is usually called a multi-link device (MLD).

[0108] A multilink device includes one or more cooperating stations (STAs). A cooperating station is a logical station and may operate on one link, one frequency band, one channel, etc. A cooperating station may be an access point (AP) or a non-access point station (non-AP STA). A multilink device may be an access point device or a station device. For ease of explanation, in this application, a multilink device in which the cooperating station is an AP may be referred to as a multilink AP, a multilink AP device, or an AP multilink device (AP multilink device, AP MLD). A multilink device in which the cooperating station is a non-AP STA may be referred to as a multilink STA, a multilink STA device, or an STA multilink device (STA multilink device), or a multilink device in which the cooperating station is a non-AP STA may be referred to as a multilink non-AP, a multilink non-AP device, a non-AP multilink device (non-AP MLD), etc. In the following description, a multilink device whose associated station is an AP is called an AP MLD, and a multilink device whose associated station is a non-AP STA is called a non-AP MLD. An AP MLD has one or more associated APs. A STA MLD has one or more associated STAs.

[0109] A station device may communicate with an access point device after multilink establishment (also called multilink association). Figure 1A is a schematic diagram of a multilink communication scenario according to an embodiment of this application. As shown in Figure 1A, a multilink access point device includes n APs, e.g., AP1 to APn, and a multilink station device includes n STAs, e.g., STA1 to APn. One AP in the multilink access point device is associated with one STA in the multilink station device. For example, AP1 is associated with STA1 through link 1.

[0110] In the multilink establishment (or multilink association) process, a station in a multilink station device may send an association request frame to an access point in a multilink access point device. The association request frame carries a multilink element (MLE) for carrying information about the multilink station device and other stations in the device. The multilink element may also be referred to as a multilink information element. Similarly, an association response frame sent back by the access point to the station may also carry an MLE for carrying information about the multilink access point device and other access points in the device.

[0111] A multilink device (which may be a non-AP MLD or AP MLD) is a communication device with wireless communication capabilities. The communication device may be an entire device, or a chip or processing system installed in the entire device. A device with a chip or processing system installed may implement the methods and functions of the embodiments of this application under the control of the chip or processing system. For example, a non-AP multilink device in the embodiments of this application may have wireless transmission and reception capabilities, support 802.11 series protocols, and communicate with an AP multilink device or another non-AP multilink device. For example, a non-AP multilink device is any user communication device that allows a user to communicate with an AP and then communicate with a WLAN. For example, a non-AP multilink device may be a user device that can connect to the Internet, such as a tablet computer, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone, or an Internet of Things node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles. Alternatively, the non-AP multilink device may be a chip and processing system within the above-mentioned terminal. The AP multilink device may be a device that provides services to the non-AP multilink device and may support the 802.11 series of protocols. For example, the AP multilink device may be a communication entity such as a communication server, router, switch, or bridge, or may include various types of macro base stations, micro base stations, relay stations, etc. Obviously, the AP multilink device may alternatively be a chip and processing system within various types of devices. The 802.11 protocol may support 802.11be or be a protocol compatible with 802.11be.

[0112] It can be understood that the Multilink device may support high-rate and low-latency transmission. With the continuous development of application scenarios of wireless local area networks, the Multilink device may be further applied to more scenarios, such as sensor nodes (such as smart meters, smart electricity meters, or smart air detection nodes) in smart cities, smart devices (such as smart cameras, projectors, displays, televisions, sounders, refrigerators, or washing machines) in smart homes, nodes in the Internet of Things, entertainment terminals (such as AR, VR, or other wearable devices), smart devices (such as printers or projectors) in smart offices, Internet of Vehicles devices in the Internet of Vehicles, and some infrastructures in daily life scenarios (such as vending machines, self-service navigation stations in supermarkets, self-service cash register devices, and self-service ordering machines). The specific form of the Multilink device is not limited in this embodiment of this application. This is merely an example for the purpose of explanation here.

[0113] FIG. 1B is a schematic diagram of another multi-link communication scenario according to an embodiment of the present application. As shown in FIG. 1B, at least one AP and at least one STA are included. FIG. 1B shows three STAs, such as STA1, STA2, and STA3. For example, STA1 may communicate with the AP through two links, which may be represented by two arrows shown in FIG. 1B. In another example, STA2 or STA3 may communicate with the AP through one link. In other words, the system shown in FIG. 1B includes both multi-link communication and single-link communication.

[0114] FIG. 1C is a schematic diagram of another multi-link communication scenario according to an embodiment of the present application. As shown in FIG. 1C, at least one AP and at least one STA are included. FIG. 1C shows three STAs, e.g., STA1, STA2, and STA3. FIG. 1C shows two APs, e.g., AP1 and AP2. For example, STA1 and STA3 may communicate with AP1 through different links, and the two links may be represented by two arrows shown in FIG. 1C. Two STAs can communicate. For example, STA2 and STA3 may communicate through a link between them. Different APs can communicate. For example, AP1 and AP2 may communicate through a link between them.

[0115] The methods provided in this application may be applied to, but are not limited to, single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X may represent anything), and device-to-device (D2D). For example, V2X may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communications.

[0116] Distributed Coordination Function (DCF)

[0117] To ensure that APs and STAs can access the wireless medium without collisions, the wireless local area network standard 802.11 uses the carrier sense multiple access with collision avoidance (CSMA / CA) mechanism. The CSMA / CA mechanism is called DCF. The basic idea of ​​the CSMA / CA mechanism is as follows: When a STA intends to transmit data, it performs a clear channel assessment on the wireless medium. assessment , CCA) is required. If the medium state (i.e., the state of the wireless medium) is idle for a certain period (e.g., DCF inter-frame space (DIFS)), the STA may initiate a random backoff process. If the medium state is busy, the STA must wait for the medium state to change to idle and initiate the random backoff process after the idle state has been maintained for a certain period (e.g., DIFS). After the random backoff process is completed, the STA may transmit data. The random backoff time during which the STA must perform backoff is obtained by multiplying the random backoff value by each slot (e.g., 9 μs). The random backoff value is randomly selected from a uniformly distributed window [0, CW]. The contention window (CW) has multiple values. The contention window takes its minimum value, i.e., CWmin, in the initial attempt. However, the CW gradually increases until it reaches a maximum value of CW, i.e., CWmax, when a retransmission needs to be performed each time a transmission fails (e.g., a contention occurs). However, when the STA successfully transmits data, the CW is reset to CWmin. The size of each window can be the difference between a power of two and one, and is approximately twice the size at the previous level.

[0118] CSMA / CA is based on carrier sensing (CS). DCF determines the medium state through both physical and virtual carrier sensing. The physical carrier sensing function is located in the physical layer (PHY) and determines whether the medium is busy through energy detection (ED) and preamble detection (PD). The virtual carrier sensing function is located in the MAC and determines whether the channel is idle based on the duration field in the received radio frame. After receiving a radio frame, the STA sets the value of the network allocation vector (NAV) based on the duration field. The NAV value indicates the length of time the station transmitting the radio frame needs to occupy the channel. After the STA sets the NAV, a countdown begins. When the countdown reaches 0, this indicates that the channel is idle. The channel is considered idle only when both the physical and virtual carrier sensing mechanisms consider the channel to be idle. Otherwise, the channel is considered busy. Figure 2 shows an example of the basic access process of the CSMA / CA mechanism. As shown in Figure 2, after a channel changes from a busy state to an idle state, a station starts a random backoff process after the idle state is maintained for a certain period. The period may be any one of DIFS, point coordination function (PCF) inter-frame space (PIFS), or short inter-frame space (SIFS). The station determines the random backoff time for backoff. The backoff window in Figure 2 corresponds to the random backoff time. Figure 3 shows an example of a backoff process for multiple STAs under DCF.As shown in FIG. 3, STA A transmits a data frame first, and STA B, STA C, and STA D all delay transmitting their data frames. After STA A transmits a complete data frame (the channel becomes idle), STA B, STA C, and STA D begin a random backoff process. STA C completes the random backoff process first, and then STA C transmits a data frame. After STA C transmits a complete data frame (the channel becomes idle), STA B, STA D, and STA E begin a random backoff process. STA D completes the random backoff process first, and then STA D transmits a data frame. The rest can be deduced by analogy.

[0119] The random backoff time that a STA needs to perform backoff is obtained by multiplying the random backoff value by each slot. The random backoff value is randomly selected from a uniformly distributed window [0, CW]. The contention window (CW) has multiple values. The contention window takes on a minimum value, i.e., CWmin, at the initial attempt. However, the CW gradually increases until it reaches the maximum value, i.e., CWmax, when a retransmission must be performed each time a transmission fails (e.g., a contention occurs). However, when data is successfully transmitted, the CW is reset to CWmin. The size of each window can be the difference between a power of two and one, which is approximately twice the size of the previous level. For ease of explanation, this is called window doubling. Figure 4 shows an example of exponential increase of the CW. As shown in FIG. 4, CW is 7 in the station's first attempt, CW is 15 in the first retransmission, CW is 31 in the second retransmission, CW is 63 in the third retransmission, and so on.

[0120] Enhanced distributed channel access (EDCA) contention transmission

[0121] EDCA is an extension of the DCF mechanism. EDCA allows services of different access categories (ACs) to have different EDCA parameter sets, including CWmin, CWmax, arbitration interframe space (AIFS), etc. Figure 5 shows an example of EDCA parameter sets for services of different ACs according to an embodiment of this application. In Figure 5, AIFSN stands for arbitration interframe spacing number, and TXOP stands for transmission opportunity ( transmission TXOP limit represents the transmission opportunity limit, and AC_BK, AC_BE, AC_VI, and AC_VO represent different ACs.

[0122] For a service of a specific AC, the backoff process of the service is basically the same as that of DCF, except that AIFS replaces DIFS in DCF. Specifically, when the channel returns to idle again, the STA needs to wait for an AIFS before performing the backoff process. The method for calculating AIFS is as follows: AIFS[AC]=aSIFSTime+AIFSN[AC]*aSlotTime. For example, for a service whose access category is AC_BE, the EDCA parameter set for the service is {CWmin=31, CWmax=1023, AIFSN=3}. Therefore, in the EDCA backoff process, AIFS is aSIFSTime+3*aSlotTime. Specifically, when the channel returns to idle again, the STA needs to wait for aSIFSTime+3*aSlotTime before performing the backoff process. Here, aSIFSTime indicates the slot length, which is typically 9 μs, and SIFSTime indicates the SIFS length, which is typically 16 μs. Furthermore, the initial value of the service's backoff counter should be randomly generated from [0,31]. The AP transmits the EDCA parameter set in the beacon frame. All STAs perform EDCA channel contention by using the EDCA parameters transmitted by the AP in the beacon frame.

[0123] multi-link element (MLE)

[0124] The multilink element is used to carry multilink device information and information about stations (including access points) within the multilink device. Figure 6 shows an example of the frame body of an MLE. As shown in Figure 6, the MLE includes an element ID, a length, an element ID extension, a multilink control field, a common info field, and a link info field. The common info field carries common information for multiple stations within the multilink device and information about the multilink device. The link info field carries information about stations on each link of the multilink device. The multilink control field carries the type of the multilink element and indication information indicating which fields appear and which do not appear in the common info. For example, the link info field may include zero, one, or more per-STA profile subelements. As shown in Figure 6, the link info field includes per-STA profile 1 through per-STA profile x, where x is an integer greater than 0. The per-STA profile subelement may include a subelement ID, a length, a STA control field, a station information field, and a station profile field. The STA profile field includes a field, an element field, and a non-inheritance element. As shown in Figure 6, the STA profile field includes field 1 to field m, element 1 to element n, and a non-inheritance element.

[0125] Multi-user (MU) EDCA

[0126] Compared with 802.11ac and previous standards, stations that comply with the 802.11ax standard have two uplink transmission methods: EDCA-based contention transmission and trigger frame-based uplink transmission. When the two transmission methods coexist, stations that comply with the 802.11ax standard have more channel access opportunities than legacy stations (i.e., stations that do not comply with the 802.11ax standard). This is obviously unfair to legacy stations. To maintain relative fairness, the MU EDCA mechanism is introduced into the 802.11ax standard to prevent legacy stations from being obviously inferior when performing channel contention. Furthermore, because trigger-based uplink transmission has higher transmission efficiency than contention-based access transmission, it is expected that the AP can send more trigger frames to schedule uplink transmissions. This can also be achieved through MU EDCA.

[0127] The basic idea of ​​the MU EDCA mechanism is that after a station is triggered by an AP to transmit data (e.g., receives a trigger frame), the priority of conventional EDCA access needs to be lowered. Specifically, the station performs channel access by using another EDCA parameter set, i.e., the MU EDCA parameter set. The station may perform channel access by using two groups (or two sets) of EDCA parameter sets. One group is the conventional EDCA parameter set, and the other group is the MU EDCA parameter set. Compared with performing channel access by using the conventional EDCA parameter set, performing channel access by a station by using the MU EDCA parameter set corresponds to a longer contention waiting time and a larger backoff window. Therefore, performing channel access by using the MU EDCA parameter set has a lower priority than performing channel access by using the conventional EDCA parameter set.

[0128] The AP adds two groups of EDCA parameter sets to a beacon frame or its associated response frame. One group is the conventional EDCA parameter set, and the other group is the MU EDCA parameter set. As mentioned above, the parameters in the MU EDCA parameter set are more conservative, i.e., a larger AIFSN, a larger CWmin, and a larger CWmax. It should be noted that the AIFSN, CWmin, and CWmax in the MU EDCA parameter set do not all need to be larger. When a station is not triggered, it may perform EDCA contention using the conventional EDCA parameter set. When a station receives a trigger frame sent by the AP and performs uplink data transmission, it must perform channel contention using the MU EDCA parameter set within a certain period (e.g., AIFS). The length of this period may be carried in the MU EDCA parameter set. If the station does not receive a trigger frame within the above period and successfully completes one uplink data transmission, it may revert to the conventional EDCA contention scheme, i.e., perform channel contention using the conventional EDCA parameter set. In this application, channel contention and channel access may be interchangeable. Figure 7 is a schematic diagram of the operation principle of the MU EDCA mechanism according to an embodiment of this application. As shown in Figure 7, the STA first performs channel contention using a conventional EDCA parameter set. After receiving a trigger frame sent by the AP and transmitting a data frame, the STA performs channel contention using the MU EDCA parameter set. After the MU EDCA timer expires, the STA performs channel contention using the conventional EDCA parameter set. When the MU EDCA timer expires, this indicates that the STA has not received a trigger frame within a certain period of time and has successfully completed uplink data transmission once.

[0129] EPCS priority access mechanism

[0130] For EPCS, 802.11be defines a priority access mechanism, which allows EPCS stations to access the channel as quickly as possible to ensure priority transmission of emergency services.

[0131] A station may request an EPCS priority access opportunity by transmitting an EPCS priority access enable request frame to an access point. The access point may transmit an EPCS priority access enable response frame in response. The EPCS priority access enable request frame and the EPCS priority access enable response frame may carry an EDCA parameter set to be used as a parameter for EDCA channel access. If the EPCS priority access mechanism is successfully established, the station performs EDCA channel contention by using the parameters in the EDCA parameter set. Generally, the EDCA parameter sets carried in the EPCS priority access enable request frame and the EPCS priority access enable response frame have a higher priority than the EDCA parameter sets carried in the beacon frame, thereby allowing an EPCS station (also called an EPCS STA) to obtain a higher priority in EDCA contention than a general station. An EPCS station may be a station that can provide EPCS. A general station may be a station that cannot provide EPCS. An EPCS station can transmit an EPCS priority access enable request frame, but a general station cannot transmit an EPCS priority access enable request frame.

[0132] A non-AP MLD may also use the EPCS priority access mechanism. Specifically, one STA in the non-AP MLD sends a request, thereby allowing multiple STAs in the non-AP MLD to obtain priority access. For ease of explanation, a non-AP MLD that can use the EPCS priority access mechanism may be referred to as an EPCS non-AP MLD in this application.

[0133] As described above, according to the MU EDCA channel access mechanism, after receiving a trigger frame sent by an AP and successfully transmitting a data frame, an EPCS station uses the MU EDCA parameter set as the channel access parameter. However, all stations in the entire cell use the same MU EDCA parameter set. Therefore, after receiving a trigger frame sent by an AP and successfully transmitting a data frame, an EPCS station loses channel access priority compared to a general station. This is clearly unreasonable. Therefore, research is needed to ensure that EPCS stations and EPCS non-AP MLD have higher channel access priority than general stations in all scenarios.

[0134] The communication solution provided in this application is mainly applied to a multi-link communication scenario. Figures 1A, 1B and 1C are respectively schematic diagrams of a multi-link communication scenario according to an embodiment of this application.

[0135] With reference to the accompanying drawings, the following describes a communication solution provided in this application and capable of ensuring that EPCS stations and EPCS non-AP MLDs have higher channel access priority than general stations in all scenarios.

[0136] 8 is a flowchart of a communication method according to an embodiment of this application. As shown in FIG. 8, the method includes the following steps:

[0137] 801: A first station sends a request frame to an access point.

[0138] The first station may be a single-link STA or a station in a non-AP MLD. In other words, the first station may be an EPCS station or a station in an EPCS non-AP MLD. The access point may be a single-link AP or an AP in an AP MLD.

[0139] The request frame is used to request obtaining channel priority access. Alternatively, the request frame is used to request obtaining channel access parameters with a higher priority. Alternatively, the request frame is used to request channel priority access. Alternatively, the request frame is used to request obtaining channel contention parameters with a higher priority. The request frame may be an EPCS priority access enable request frame, or a national security & emergency preparedness (NSEP) priority access enable request frame, or other frame. The specific name of the request frame is not limited in this application.

[0140] The request frame carries a first parameter set. The first parameter set includes MU EDCA parameters intended for the first station to use to perform channel contention. For example, the first parameter set includes MU EDCA parameters intended for the first station to use to perform channel contention after the first station successfully transmits a data frame triggered based on the access point's trigger frame. The MU EDCA parameters may include AIFSN, CWmin, CWmax, TXOP limit, etc. corresponding to each access category. The channel access priority of the first parameter set may be higher than the channel access priority of the MU EDCA parameter set used by general stations. How the request frame carries the first parameter set will be described below with reference to the frame body of the request frame.

[0141] In a possible implementation, the request frame carries first indication information indicating the first parameter set. The first indication information may be an identifier of the first parameter set or a binary sequence indicating the first parameter set, for example, 10. The first station and the access point may pre-agree to use the first indication information to indicate the first parameter set, thereby enabling the amount of data carried in the request frame to be reduced.

[0142] It should be noted that in this application, there may be two or more MU EDCA parameter sets. One MU EDCA parameter set is used by the general station after it successfully transmits a triggered data frame based on a received trigger frame, and another MU EDCA parameter set is used by an EPCS station (e.g., a first station) after it successfully transmits a triggered data frame based on a received trigger frame. For example, after successfully transmitting a triggered data frame based on a received trigger frame, the general station performs channel access by using parameters in the first MU EDCA parameter set, and after successfully transmitting a triggered data frame based on the received trigger frame, the first station performs channel access by using parameters in the first parameter set, which is a second MU EDCA parameter set different from the first MU EDCA parameter set. In a possible implementation, after successfully transmitting a triggered data frame based on a received trigger frame, different EPCS stations may perform channel access by using different MU EDCA parameter sets.

[0143] In a possible implementation, the request frame further carries a second parameter set. The second parameter set includes MU EDCA parameters intended for use by the second station to perform channel contention. The second station and the first station belong to the same multilink station device. In a possible implementation, the second parameter set is included in a link information field in the MLE of the request frame. How the request frame carries the second parameter set is described below with reference to the frame body of the request frame. It should be understood that the request frame may also carry MU EDCA parameters intended for use by one or more stations belonging to the same multilink station device as the first station to perform channel contention. For example, the request frame may further carry MU EDCA parameters intended for use by station 1 to perform channel contention and MU EDCA parameters intended for use by station 2 to perform channel contention, where station 1, station 2, and the first station all belong to the same multilink station device.

[0144] 802: The first station receives a response frame to the request frame.

[0145] In a possible implementation, the response frame carries a third parameter set, which includes MU EDCA parameters to be used by the first station to perform channel contention, and which may be the same as or different from the first parameter set.

[0146] It should be understood that if the access point does not agree to the first station performing channel contention by using parameters in the first parameter set, the access point may transmit a response frame carrying a third parameter set to the first station. The third parameter set includes MU EDCA parameters to be used by the first station to perform channel contention. The third parameter set is different from the first parameter set. In this implementation, the response frame carries the third parameter set, thereby causing the first station to perform channel contention by using parameters in the third parameter set to ensure channel access priority. How the response frame carries the third parameter set will be described below with reference to the frame body of the response frame. It should be understood that if the access point agrees to the first station performing channel contention by using parameters in the first parameter set, the response frame transmitted by the access point to the first station may carry the third parameter set. In a possible implementation, the third parameter set includes the first parameter set, is equal to the first parameter set, or is a subset of the third parameter set. If the access point agrees that the first station will perform channel contention by using parameters in the first parameter set, the access point may also send a response frame to the first station that does not carry the third parameter set for the first station. In other words, a response frame that does not carry any parameter set for the first station is sent to the first station. This indicates that the first station is by default permitted to perform subsequent channel contention by using the first parameter set carried in the first station's request frame.In this implementation, if the response frame does not carry the third parameter set, this indicates that the access point agrees to the first station performing channel contention by using parameters in the first parameter set, thereby reducing the amount of data in the response frame.

[0147] In a possible implementation, the request frame further carries a second parameter set. The second parameter set includes MU EDCA parameters that the second station intends to use to perform channel contention. The second station and the first station belong to the same multilink station device. Correspondingly, the response frame further carries a fourth parameter set. The fourth parameter set includes MU EDCA parameters to be used by the second station to perform channel contention. The fourth parameter set may be the same as or different from the second parameter set. It should be understood that if the access point agrees to allow the second station to perform channel contention by using parameters in the second parameter set, the response frame transmitted by the access point to the first station may carry the fourth parameter set. In a possible implementation, the fourth parameter set includes the second parameter set, is equal to the second parameter set, or is a subset of the fourth parameter set. If the access point agrees to allow the second station to perform channel contention by using parameters in the second parameter set, the access point may also transmit a response frame to the first station that does not carry a fourth parameter set for the first station. In other words, a response frame that does not carry any parameter set for the second station is transmitted to the second station. This indicates that the second station is by default permitted to perform subsequent channel contention by using the second parameter set carried in the first station's request frame. How the response frame carries the fourth parameter set will be described below with reference to the frame body of the response frame.

[0148] In some possible implementations, the request frame transmitted by the first station may not carry MU EDCA parameters that the first station intends to use to perform channel contention. In other words, the first station may carry only MU EDCA parameter sets that one or more stations belonging to the same multi-link station device as the first station intend to use to perform channel contention. The response frame transmitted by the access point on behalf of the first station may carry only MU EDCA parameter sets that one or more stations belonging to the same multi-link station device as the first station are permitted to use to perform channel contention.

[0149] The steps of the method in FIG. 8 may be replaced as follows: A first station sends a request frame to an access point. The request frame carries a second parameter set. The second parameter set includes MU EDCA parameters that the second station intends to use to perform channel contention. The second station and the first station belong to the same multilink station device. The access point sends a response frame to the first station. The response frame carries a fourth parameter set. The fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention. The fourth parameter set may be the same as or different from the second parameter set. The response frame may carry only the fourth parameter set. It should be understood that if the access point agrees to allow the second station to perform channel contention by using parameters in the second parameter set, the response frame sent by the access point to the first station may carry the fourth parameter set. In a possible implementation, the fourth parameter set includes the second parameter set, is equal to the second parameter set, or is a subset of the fourth parameter set. If the access point agrees that the second station will perform channel contention by using parameters in the second parameter set, the access point may also send a response frame to the first station that does not carry the fourth parameter set. In other words, a response frame that does not carry any parameter set is sent. This indicates that the second station is by default permitted to perform subsequent channel contention by using the second parameter set carried in the first station's request frame. How the request frame carries the second parameter set will be described below with reference to the frame body of the request frame.

[0150] In this embodiment of the present application, the request frame carries a first parameter set, which includes MU EDCA parameters that the first station intends to use to perform channel contention, and performs channel contention by using parameters with a higher channel priority.

[0151] The following describes the frame body of the request frame with reference to the accompanying drawings or tables, and further describes how the request frame carries the first parameter set and how the request frame carries the second parameter set with reference to the frame body of the request frame.

[0152] Frame Body 1 of the Request Frame:

[0153] Table 1 shows an example of fields included in frame body 1 of a request frame. Referring to Table 1, the first parameter set is included in the MU EDCA parameter set field in the request frame. In other words, the MU EDCA parameter set field in Table 1 carries the first parameter set. [Table 1]

[0154] The order in Table 1 is merely an example for illustration purposes and is not limiting in this embodiment of the present invention.

[0155] The category field indicates the type of the action frame. The value of the category field may be "protected EHT action" to indicate that the action frame is in the "protected EHT action" category.

[0156] The protected EHT action field indicates the subcategory of the action frame. In one possible implementation, the value of the protected EHT action field is EPCS priority access enable request to indicate that the action frame is an EPCS priority access enable request frame. In another possible implementation, the value of the protected EHT action field is NSEP priority access enable request to indicate that the action frame is an NSEP priority access enable request frame.

[0157] The dialog token field is used to pair request and response frames.

[0158] The EDCA parameter set field indicates the EDCA parameter set that the first station intends to use.

[0159] The MU EDCA parameter set field indicates the MU EDCA parameter set that the first STA intends to use, ie, the first parameter set.

[0160] The priority access multi-link element field is used to convey EDCA parameter sets and MU EDCA parameter sets intended for use by one or more stations belonging to the same multilink station device as a first station. For example, the priority access multi-link element field is used to convey EDCA parameter sets and MU EDCA parameter sets intended for use by a second station, where the second station and the first station belong to the same multilink station device. The priority access multi-link element field may be replaced by a basic multi-link element or other field, provided that the field conveys the EDCA parameter sets and MU EDCA parameter sets intended for use by the second station. This is not a limitation of this application. The priority access multi-link element field may also be replaced by a link ID bitmap field plus a parameter set field list. The parameter set field contains an EDCA parameter set and / or an MU EDCA parameter set. The link ID bitmap field is a bitmap of link identifiers. Each bit in the bitmap indicates whether the following parameter set field list contains a parameter set for the corresponding link. For example, the link ID bitmap field may be 16 bits long, with each bit corresponding to one link, and the link ID bitmap field may correspond to a total of 16 links. If the value of the i-th bit in the link ID bitmap field is 1, this indicates that the following parameter set field list contains a parameter set for the link whose link ID is (i-1). The value of i ranges from 1 to 16, and the value of link ID ranges from 0 to 15.

[0161] The priority access multi-link element field is not required but optional. It can be understood that when the first station is an independent station, the request frame transmitted by the first station does not need to carry the EDCA parameter set and the MU EDCA parameter set intended for use by other stations. When the first station is a station in a non-AP MLD, the request frame transmitted by the first station may carry the EDCA parameter set and the MU EDCA parameter set intended for use by one or more stations belonging to the same multi-link station device as the first station, or may not carry the EDCA parameter set and the MU EDCA parameter set intended for use by other stations. Figure 9A is an example of the format of the priority access multi-link element field according to an embodiment of this application. The difference between the format of the priority access multi-link element field shown in Figure 9A and the format of the MLE in Figure 6 is the different information included in the STA profile field. For the meaning of the fields in Figure 9A, refer to the meaning of the fields in Figure 6. The STA profile field within the priority access multi-link element field may include an EDCA parameter set and an MU EDCA parameter set. As shown in FIG. 9A, the STA control field includes a link identifier (link ID).

[0162] In a possible implementation, the priority access multi-link element field includes one or more per-STA profiles. Each per-STA profile corresponds to one station belonging to the same multilink station device as the first station. Each per-STA profile includes an EDCA parameter set and an MU EDCA parameter set intended for use by the station corresponding to the per-STA profile. Any two per-STA profiles correspond to different stations. As shown in FIG. 9A, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., and per-STA profile x. Per-STA profile 1 corresponds to station 1, per-STA profile 2 corresponds to station 2, ..., per-STA profile x corresponds to station x. Per-STA profile 1 includes an EDCA parameter set and an MU EDCA parameter set intended for use by station 1. Per-STA profile 2 includes an EDCA parameter set and an MU EDCA parameter set intended for use by station 2. By analogy, per-STA profile x includes the EDCA parameter set and MU EDCA parameter set that station x intends to use, where x is an integer greater than 1. Station 1, station 2, ..., and station x all belong to the same multilink station device as the first station. For example, the STA profile field in each per-STA profile in the priority access multi-link element field includes the EDCA parameter set and MU EDCA parameter set that the station corresponding to the per-STA profile intends to use.For example, the priority access multi-link element field includes per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to station 1. Per-STA profile 2 corresponds to station 2. The STA profile field in per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set that station 1 intends to use. The STA profile field in per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set that station 2 intends to use. In this example, stations 1 and 2 belong to the same multi-link station device. In a possible implementation, the STA control field in the per-STA profile includes a link ID corresponding to one station, and the station corresponds to the per-STA profile. For example, the priority access multi-link element field includes per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to station 1. Per-STA profile 2 corresponds to station 2. The STA control field in per-STA profile 1 includes the link ID corresponding to station 1. The STA control field in per-STA profile 2 includes a link ID corresponding to station 2. The link ID corresponding to a station is the ID of the link the station uses to access the access point. The link identifier in the STA control field indicates the link or the station. The access point may determine the station corresponding to the per-STA profile based on the link ID included in the STA control field in the per-STA profile.The EDCA parameter set and MU EDCA parameter set in the STA profile field in the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the station intends to use.

[0163] Frame body 2 of the request frame:

[0164] Table 2 shows an example of fields included in frame body 2 of a request frame. Referring to Table 2, the first parameter set is included in the priority access multi-link element field. In other words, the priority access multi-link element field in Table 2 carries the first parameter set. The first parameter set is included in the priority access multi-link element field. The priority access multi-link element field in Table 2 represents the MLE in the request frame. In other words, the first parameter set is included in the MLE in the request frame. The order in Table 2 is merely an example for explanation purposes and is not limited in this embodiment of the present invention. The meanings of the fields in Table 2 have been described when Table 1 was described. Therefore, the details will not be described again here. [Table 2]

[0165] In a possible implementation, the first parameter set is included in a link info field in the priority access multi-link element field. Figure 9B is an example of another format of the priority access multi-link element field according to an embodiment of this application. For the meanings of the fields in Figure 9B, please refer to the field description in Figure 6. Figure 9B shows the priority access multi-link element field in a request frame, and the MU EDCA parameter set represents the first parameter set. When Figure 9B is compared with Figure 9A, one per-STA profile in Figure 9B corresponds to the first station, and x per-STA profiles in Figure 9A correspond to x stations belonging to the same multilink station device as the first station.

[0166] In a possible implementation, the priority access multi-link element field includes a per-STA profile corresponding to the first station, which includes an EDCA parameter set and an MU EDCA parameter set intended for use by the first station. For example, the STA profile field in the per-STA profile within the priority access multi-link element field includes an EDCA parameter set and an MU EDCA parameter set intended for use by the first station corresponding to the per-STA profile. In a possible implementation, the STA control field in the per-STA profile includes a link ID corresponding to the first station, which corresponds to the per-STA profile. As shown in FIG. 9B, the link information field includes the per-STA profile, which corresponds to the first station. The per-STA profile includes a STA control field and an STA profile field. The STA control field includes a link ID. The STA profile field includes an EDCA parameter set and an MU EDCA parameter set. The link identifier in the STA control field indicates the first station. The link identifier in the STA control field indicates the first station. The access point may determine the station corresponding to the per-STA profile based on the link ID included in the STA control field in the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field in the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the station intends to use.

[0167] In a possible implementation, the priority access multi-link element field includes multiple per-STA profiles. One of the multiple per-STA profiles corresponds to the first station. Another of the multiple per-STA profiles corresponds to a station belonging to the same multi-link station device as the first station. Each per-STA profile includes an EDCA parameter set and an MU EDCA parameter set intended for use by the station corresponding to the per-STA profile. Any two per-STA profiles correspond to different stations. FIG. 9C is an example of another format of the priority access multi-link element field according to an embodiment of this application. As shown in FIG. 9C, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., and per-STA profile m. Per-STA profile 1 corresponds to the first station, per-STA profile 2 corresponds to station 2, ..., per-STA profile m corresponds to station m. Per-STA profile 1 includes an EDCA parameter set and an MU EDCA parameter set intended for use by the first station. Per-STA profile 2 contains the EDCA parameter set and MU EDCA parameter set intended for use by station 2. By analogy, per-STA profile m contains the EDCA parameter set and MU EDCA parameter set intended for use by station m, where m is an integer greater than 1. Stations 2, 3, ..., and m all belong to the same multilink station device as the first station.For example, the STA profile field in each per-STA profile in the priority access multi-link element field contains the EDCA parameter set and MU EDCA parameter set intended for use by the station corresponding to the per-STA profile. For example, the priority access multi-link element field contains per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to the first station, and per-STA profile 2 corresponds to station 2. The STA profile field in per-STA profile 1 contains the EDCA parameter set and MU EDCA parameter set intended for use by the first station. The STA profile field in per-STA profile 2 contains the EDCA parameter set and MU EDCA parameter set intended for use by station 2. In this example, station 2 and the first station belong to the same multilink station device. In a possible implementation, the STA control field in the per-STA profile contains a link ID corresponding to one station, and the station corresponds to the per-STA profile. For example, the priority access multi-link element field contains per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to station 1. Per-STA profile 2 corresponds to station 2. The STA control field in per-STA profile 1 contains the link ID corresponding to station 1. The STA control field in per-STA profile 2 contains the link ID corresponding to station 2. The link ID corresponding to a station is the ID of the link the station uses to access the access point.The link identifier in the STA control field included in the per-STA profile indicates the station or link. The STA profile in the per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the station intends to use. The access point may determine the station corresponding to the per-STA profile based on the link ID included in the STA control field in the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field in the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the station intends to use.

[0168] In a possible implementation, the request frame transmitted by the first station carries only the MU EDCA parameter set intended for use by one or more stations belonging to the same multilink station device as the first station to perform channel contention, and the MU EDCA parameter set may be included in the link info field within the priority access multi-link element field. In this possible implementation, the priority access multi-link element field includes multiple per-STA profiles, each corresponding to a station belonging to the same multilink station device as the first station. Each per-STA profile includes an EDCA parameter set and an MU EDCA parameter set intended for use by the station corresponding to the per-STA profile. Any two per-STA profiles correspond to different stations. In this implementation, the link info field within the priority access multi-link element field does not carry the EDCA parameter set and the MU EDCA parameter set intended for use by the first station.

[0169] Below, the frame body of the response frame will be described with reference to the accompanying drawings or tables, and how the response frame carries the third parameter set and how the response frame carries the fourth parameter set will be further described with reference to the frame body of the response frame.

[0170] Frame body 1 of the response frame:

[0171] Table 3 shows an example of fields included in frame body 1 of the response frame. Referring to Table 3, the third parameter set is included in the MU EDCA parameter set field in the response frame. In other words, the MU EDCA parameter set field in Table 3 carries the third parameter set. [Table 3]

[0172] The order in Table 3 is merely an example for illustration purposes and is not limiting in this embodiment of the present invention.

[0173] The meaning of the first three fields in Table 3 is the same as the meaning of the first three fields in Table 1. The difference is that the value of the protected EHT action field is EPCS priority access enable response.

[0174] The status code field indicates whether the EPCS was successfully established.

[0175] The EDCA parameter set field indicates the EDCA parameter set that the access point allows the first station to use.

[0176] The MU EDCA parameter set indicates the MU EDCA parameter set that the access point allows the first station to use, i.e., the third parameter set. It should be understood that when the access point allows the first station to use the EDCA parameter set or the MU EDCA parameter set in the request frame, the EDCA parameter set or the MU EDCA parameter set does not need to be carried in the response frame.

[0177] The priority access multi-link element field is used to carry the EDCA parameter set and MU EDCA parameter set that the access point allows to be used by one or more stations that belong to the same multilink station device as the first station. For example, the priority access multi-link element field is used to carry the EDCA parameter set and MU EDCA parameter set (i.e., the fourth parameter set) that the access point allows to be used by a second station, and the second station and the first station belong to the same multilink station device. The priority access multi-link element field may be replaced by a basic multi-link element or other field, provided that the field carries the EDCA parameter set and MU EDCA parameter set that the access point allows to be used by the second station. This is not a limitation in this application. The priority access multi-link element field is not required but is optional. It should be understood that if the access point allows the second station to use the EDCA parameter set or the MU EDCA parameter set in the request frame, the EDCA parameter set or the MU EDCA parameter set that the second station is allowed to use does not need to be carried in the response frame. Figure 9A shows an example of the format of the priority access multi-link element field in the response frame. As shown in Figure 9A, the STA profile field in the priority access multi-link element field in the response frame may include the EDCA parameter set and the MU EDCA parameter set.

[0178] In a possible implementation, the priority access multi-link element field includes one or more per-STA profiles. Each per-STA profile corresponds to one station belonging to the same multi-link station device as the first station. Each per-STA profile includes an EDCA parameter set and an MU EDCA parameter set that the access point allows the station corresponding to the per-STA profile to use. Any two per-STA profiles correspond to different stations. As shown in FIG. 9A, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., and per-STA profile x. Per-STA profile 1 corresponds to station 1, per-STA profile 2 corresponds to station 2, ..., per-STA profile x corresponds to station x. Per-STA profile 1 includes an EDCA parameter set and an MU EDCA parameter set that the access point allows station 1 to use. Per-STA profile 2 includes an EDCA parameter set and an MU EDCA parameter set that the access point allows station 2 to use. By analogy, per-STA profile x includes the EDCA parameter set and MU EDCA parameter set that the access point allows station x to use, where x is an integer greater than 1. Station 1, station 2, ..., and station x all belong to the same multilink station device as the first station.For example, the STA profile field in each per-STA profile in the priority access multi-link element field contains the EDCA parameter set and MU EDCA parameter set that the access point allows the station corresponding to the per-STA profile to use. For example, the priority access multi-link element field contains per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to station 1. Per-STA profile 2 corresponds to station 2. The STA profile field in per-STA profile 1 contains the EDCA parameter set and MU EDCA parameter set that the access point allows station 1 to use. The STA profile field in per-STA profile 2 contains the EDCA parameter set and MU EDCA parameter set that the access point allows station 2 to use. In this example, stations 1 and 2 belong to the same multi-link station device. In a possible implementation, the STA control field in the per-STA profile contains a link ID corresponding to one station, and the station corresponds to the per-STA profile. For example, the priority access multi-link element field includes per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to station 1. Per-STA profile 2 corresponds to station 2. The STA control field in per-STA profile 1 includes the link ID corresponding to station 1. The STA control field in per-STA profile 2 includes the link ID corresponding to station 2.The link identifier in the STA control field included in the per-STA profile indicates the station. The STA profile in the per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the access point allows the station to use. The first station may determine the station corresponding to the per-STA profile based on the link ID included in the STA control field in the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field in the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the access point allows the station to use.

[0179] Frame body 2 of the response frame:

[0180] Table 4 shows an example of fields included in frame body 2 of a response frame. Referring to Table 4, the third parameter set is included in the priority access multi-link element field. In other words, the priority access multi-link element field in Table 4 carries the third parameter set. The priority access multi-link element field in Table 4 represents the MLE in the response frame. In other words, the third parameter set is included in the MLE in the response request frame. The order in Table 4 is merely an example for explanation purposes and is not limiting in this embodiment of the present invention. The meanings of the fields in Table 4 have been described when Table 3 was described. Therefore, the details will not be described again here. [Table 4]

[0181] In a possible implementation, the third parameter set is included in the link info field in the priority access multi-link element field. Figure 9B is still used. Figure 9B shows the priority access multi-link element field in the response frame. In Figure 9B, the MU EDCA parameter set represents the third parameter set, and the third parameter set is included in the STA profile field, which is included in the per-STA profile, which is included in the link info field.

[0182] In a possible implementation, the priority access multi-link element field includes a per-STA profile corresponding to the first station, which includes an EDCA parameter set and an MU EDCA parameter set (i.e., a third parameter set) that the access point allows the first station to use. For example, the STA profile field in the per-STA profile within the priority access multi-link element field includes an EDCA parameter set and an MU EDCA parameter set that the access point allows the first station corresponding to the per-STA profile to use. In a possible implementation, the STA control field in the per-STA profile includes a link ID corresponding to the first station, which corresponds to the per-STA profile. As shown in FIG. 9B , the link information field includes the per-STA profile, which corresponds to the first station. The per-STA profile includes a STA control field and a STA profile field. The STA control field includes a link ID. The STA profile field includes an EDCA parameter set and an MU EDCA parameter set. It should be understood that the first station may obtain the EDCA parameter set and MU EDCA parameter set to be used by the first station, i.e., the EDCA parameter set and MU EDCA parameter set that the access point allows the first station to use, based on the STA control field and the STA profile field in the priority access multi-link element field.

[0183] In a possible implementation, the priority access multi-link element field includes multiple per-STA profiles. One of the multiple per-STA profiles corresponds to the first station. Another of the multiple per-STA profiles corresponds to a station belonging to the same multilink station device as the first station. Each per-STA profile includes an EDCA parameter set and an MU EDCA parameter set that the access point allows the station corresponding to the per-STA profile to use. Any two per-STA profiles correspond to different stations. The priority access multi-link element field in FIG. 9C may be considered the priority access multi-link element field in the response frame. As shown in FIG. 9C, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., and per-STA profile m. Per-STA profile 1 corresponds to the first station, per-STA profile 2 corresponds to station 2, ..., per-STA profile m corresponds to station m. Per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set that the access point allows station 1 to use. Per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set that the access point allows station 2 to use. By analogy, per-STA profile m includes the EDCA parameter set and MU EDCA parameter set that the access point allows station m to use, where m is an integer greater than 1.Station 2, station 3, ..., and station m all belong to the same multilink station device as the first station. For example, the STA profile field in each per-STA profile in the priority access multi-link element field contains the EDCA parameter set and MU EDCA parameter set that the access point allows the station corresponding to the per-STA profile to use. For example, the priority access multi-link element field contains per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to the first station. Per-STA profile 2 corresponds to station 2. The STA profile field in per-STA profile 1 contains the EDCA parameter set and MU EDCA parameter set that the access point allows the first station to use. The STA profile field in per-STA profile 2 contains the EDCA parameter set and MU EDCA parameter set that the access point allows station 2 to use. In this example, station 2 and the first station belong to the same multilink station device. In a possible implementation, the STA control field in the per-STA profile includes a link ID corresponding to one station, and the station corresponds to the per-STA profile. For example, the priority access multi-link element field includes per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to the first station. Per-STA profile 2 corresponds to station 2. The STA control field in per-STA profile 1 includes the link ID corresponding to the first station.The STA control field in per-STA profile 2 includes a link ID corresponding to station 2. The first station may determine the station corresponding to the per-STA profile based on the link ID included in the STA control field in the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field in the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the access point allows the station to use.

[0184] In a possible implementation, the response frame transmitted by the access point carries only the MU EDCA parameter set to be used by one or more stations belonging to the same multilink station device as the first station to perform channel contention, and the MU EDCA parameter set may be included in the link information (link info) field within the priority access multi-link element field. In this possible implementation, the priority access multi-link element field includes multiple per-STA profiles. Each of the multiple per-STA profiles corresponds to one station belonging to the same multilink station device as the first station. Each per-STA profile includes an EDCA parameter set and an MU EDCA parameter set that the access point allows the station corresponding to the per-STA profile to use. Any two per-STA profiles correspond to different stations. In this implementation, the link info field within the priority access multi-link element field does not carry the EDCA parameter set and the MU EDCA parameter set that the access point allows the first station to use.

[0185] Figure 10 is a flowchart of another communication method according to an embodiment of this application. The method steps in Figure 10 are possible implementations of the method in Figure 8. As shown in Figure 10, the method includes the following steps:

[0186] 1001: A first station sends a request frame to an access point.

[0187] Before transmitting the request frame to the access point, the first station may generate the request frame. For step 1001, refer to step 801. The request frame carries a first parameter set. The channel access priority of the first parameter set is higher than the channel access priority of the MU EDCA parameter set used by general stations.

[0188] 1002: The access point sends a response frame to the request frame to the first station.

[0189] Table 5 is an example of the fields in the response frame sent by the access point to the first station. For the meanings of the fields in Table 5, refer to the meanings of the fields in Table 3. [Table 5]

[0190] 1003: After transmitting a data frame triggered based on the trigger frame of the access point, the first station performs channel contention by using parameters in the first parameter set.

[0191] A possible implementation of step 1003 is as follows: After transmitting a data frame triggered based on the trigger frame of the access point, the first station performs channel contention for a first duration by using parameters in a first parameter set. The first duration is obtained based on parameters in the first parameter set. The first parameters may include AIFSN, CWmin, CWmax, TXOP limit, etc. corresponding to each access category. The first duration may be obtained based on an MU EDCA timer field in the first parameter set. In other words, the MU EDCA timer field indicates the first duration. For example, the first duration is carried in the first parameter set, and the first station determines the first duration based on the first parameter set. In another example, a parameter in the first parameter set indicates the first duration, and the first station determines the first duration based on the parameter in the first parameter set indicating the first duration.

[0192] In this embodiment of the present application, after transmitting a data frame triggered by a trigger frame of an access point, the first station performs channel contention by using parameters in a first parameter set, and compared with a general station, the first station can have a higher channel access priority.

[0193] Figure 11 is a flowchart of another communication method according to an embodiment of this application. The method steps in Figure 11 are possible implementations of the method in Figure 8. As shown in Figure 11, the method includes the following steps:

[0194] 1101: A first station sends a request frame to an access point.

[0195] For step 1001, refer to step 801. The request frame carries a first parameter set.

[0196] 1102: When the access point does not agree to the first station performing channel contention by using parameters in the first parameter set, the access point sends a response frame carrying a third parameter set to the access point.

[0197] The response frame carries a third parameter set, which includes MU EDCA parameters to be used by the first station to perform channel contention, and which is different from the first parameter set.

[0198] 1103: After transmitting a data frame triggered based on the trigger frame of the access point, the first station performs channel contention by using parameters in the third parameter set.

[0199] A possible implementation of step 1003 is as follows: After transmitting a data frame triggered based on the trigger frame of the access point, the first station performs channel contention for a third duration by using parameters in a third parameter set. The third duration is obtained based on parameters in the third parameter set. For example, the third duration is carried in the third parameter set, and the first station determines the third duration based on the third parameter set. In another example, a parameter in the third parameter set indicates the third duration, and the first station determines the third duration based on the parameter in the third parameter set indicating the third duration.

[0200] The first parameter set is determined by the first station from its perspective, without taking into account the access point and other stations. The third parameter set is determined by the access point from a global perspective, with multiple stations being comprehensively considered. In this embodiment of the present application, after transmitting a data frame triggered based on the trigger frame of the access point, the first station performs channel contention by using parameters in the third parameter set. In this way, the first station can have a higher channel access priority and reduce the impact on other stations.

[0201] Figure 12 is a flowchart of another communication method according to an embodiment of this application. The steps of the method in Figure 12 are a possible implementation of the method in Figure 8. As shown in Figure 12, the method includes the following steps:

[0202] 1201: A first station sends a request frame to an access point.

[0203] The request frame carries a first parameter set and a second parameter set. The second parameter set includes MU EDCA parameters intended for use by the second station to perform channel contention. The second station and the first station belong to the same multilink station device. The second parameter set may further include EDCA parameters intended for use by the second station to perform channel contention.

[0204] In a possible implementation, before transmitting a request frame to the access point, the first station may receive first parameter information from the second station. The first parameter information includes a second parameter set. The second parameter set includes MU EDCA parameters that the second station intends to use to perform channel contention. In this implementation, the second station may actively transmit the first parameter information including the second parameter set to the first station.

[0205] In a possible implementation, before transmitting the request frame to the access point, the first station performs the following operations: transmitting a parameter set query message to the second station; and receiving second parameter information transmitted by the second station in response to the parameter set query message, where the second parameter information includes a second parameter set. The parameter set query message is used to acquire an MU EDCA parameter set that the second station intends to use to perform channel contention. In this implementation, the first station acquires the MU EDCA parameter set that the second station intends to use to perform channel contention through an active query method.

[0206] 1202: The access point sends a response frame to the request frame to the first station.

[0207] In a possible implementation, the response frame carries a third parameter set and a fourth parameter set. The third parameter set includes MU EDCA parameters that the access point allows the first station to use to perform channel contention. The fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention. The third parameter set is different from the first parameter set. The fourth parameter set is different from the second parameter set. For the parameter sets that each station intends to use and that are carried in the request frame, when the access point agrees that the station (any station) will use the parameter set that the station intends to use, the response frame may or may not carry the parameter set that the station intends to use. When the access point does not agree that the station will use the parameter set that the station intends to use, the response frame carries the parameter set that the access point agrees that the station will use. For example, the access point may agree that the first station will perform channel contention by using parameters in a first parameter set, and the response frame may or may not carry the first parameter set. In another example, the access point may not agree that the first station will perform channel contention by using parameters in the first parameter set, and the response frame may carry a third parameter set that the access point will allow the first station to use, the third parameter set being different from the first parameter set. In another example, the access point may not agree that the second station will perform channel contention by using parameters in a second parameter set, and the response frame may carry a fourth parameter set that the access point will allow the second station to use, the fourth parameter set being different from the second parameter set.

[0208] 1203: The second station receives the fourth parameter set from the first station.

[0209] Step 1203 may be replaced as follows: The second station may obtain a fourth parameter set from the first station, where the fourth parameter set is an MU EDCA parameter set that the access point allows the second station to use.

[0210] 1204: After transmitting the data frame triggered based on the trigger frame of the access point, the first station performs channel contention by using parameters in the third parameter set.

[0211] The third parameter set may be the same as or different from the first parameter set. It should be understood that if the access point agrees to the first station performing channel contention by using parameters in the first parameter set, the response frame may or may not carry the third parameter set, and the third parameter set is the same as the first parameter set. It should be understood that if the access point does not agree to the first station performing channel contention by using parameters in the first parameter set, the response frame carries the third parameter set, and the third parameter set is different from the first parameter set. The order of steps 1203 and 1204 is not limited. Step 1204 is optional and not required.

[0212] A possible implementation manner of step 1204 is as follows: after transmitting a data frame triggered by the access point's trigger frame, the first station performs channel contention within a third duration by using parameters in a third parameter set, where the third duration is obtained based on the parameters in the third parameter set.

[0213] 1205: After transmitting the data frame triggered based on the trigger frame of the access point, the second station performs channel contention by using the parameters in the fourth parameter set.

[0214] The fourth parameter set may be the same as or different from the second parameter set. It should be understood that if the access point agrees to the second station performing channel contention by using parameters in the second parameter set, the response frame may or may not carry the fourth parameter set, and the fourth parameter set is the same as the second parameter set. It should be understood that if the access point does not agree to the second station performing channel contention by using parameters in the second parameter set, the response frame carries the fourth parameter set, and the fourth parameter set is different from the second parameter set.

[0215] A possible implementation manner of step 1204 is as follows: After transmitting a data frame triggered by the access point's trigger frame, the second station performs channel contention for a fourth duration by using parameters in a fourth parameter set, where the fourth duration is obtained based on the parameters in the fourth parameter set.

[0216] In a possible implementation, the response frame carries a third parameter set but not a fourth parameter set, where the third parameter set includes MU EDCA parameters that the access point allows the first station to use to perform channel contention, and the fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention, and the third parameter set is different from the first parameter set. Step 1203 may be replaced as follows: The second station receives the second parameter set of the first station, or the second station determines that the access point allows the second station to perform channel contention by using the second parameters. Step 1205 may be replaced as follows: After transmitting a data frame triggered based on the access point's trigger frame, the second station performs channel contention by using parameters in the second parameter set. The response frame carrying the third parameter set but not the fourth parameter set may mean that the response frame carries the third parameter set and the second parameter set, or may mean that the response frame carries the third parameter set but not the second parameter set.

[0217] In a possible implementation, the response frame carries a fourth parameter set but not a third parameter set, where the fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention, and the third parameter set includes MU EDCA parameters that the access point allows the first station to use to perform channel contention, and the fourth parameter set is different from the second parameter set. Step 1204 may be replaced as follows: After transmitting a data frame triggered based on the access point's trigger frame, the first station performs channel contention by using parameters in the first parameter set. The response frame carrying the fourth parameter set but not the third parameter set may also mean that the response frame carries the fourth parameter set and the first parameter set, or may mean that the response frame carries the fourth parameter set but not the first parameter set.

[0218] In a possible implementation, the response frame does not carry the fourth parameter set and the third parameter set, the fourth parameter set includes MU EDCA parameters that the access point allows the second station to use to perform channel contention, the third parameter set includes MU EDCA parameters that the access point allows the first station to use to perform channel contention, the fourth parameter set is different from the second parameter set, and the third parameter set is different from the first parameter set. Step 1203 may be replaced as follows: The second station receives the second parameter set of the first station, or the second station determines that the access point allows the second station to perform channel contention by using the second parameters. Step 1204 may be replaced as follows: After transmitting a data frame triggered based on the access point's trigger frame, the first station performs channel contention by using parameters in the first parameter set. Step 1205 may be replaced as follows: After transmitting the data frame triggered based on the trigger frame of the access point, the second station performs channel contention by using parameters in the second parameter set. The response frame not carrying the fourth parameter set and the third parameter set may be the response frame carrying the first parameter set and the second parameter set, or may be the response frame not carrying any parameter set.

[0219] In this embodiment of the present application, the request frame carries a first parameter set and a second parameter set. Compared with the embodiment in Fig. 11, in the embodiment in Fig. 12, the request frame sent by the first station further carries a second parameter set, and the second station can obtain the MU EDCA parameters that the access point allows the second station to use without sending a request frame. Therefore, signaling exchange can be reduced.

[0220] Figure 13 is a flowchart of another communication method according to an embodiment of this application. The difference between the method steps in Figure 13 and those in Figures 8, 10, 11 and 12 is that the request frame sent by the first station does not include the MU EDCA parameters that the first station intends to use. As shown in Figure 13, the method includes the following steps:

[0221] 1301: A first station sends a request frame to an access point, where the request frame does not carry an MU EDCA parameter set.

[0222] Table 6 is an example of the fields in a request frame sent by a first station to an access point. For the meanings of the fields in Table 6, refer to the meanings of the fields in Table 1. [Table 6]

[0223] The order in Table 6 is merely an example for illustration purposes and is not limiting in this embodiment of the present invention.

[0224] 1302: The access point sends a response frame to the request frame to the first station.

[0225] The response frame carries a third parameter set, which includes MU EDCA parameters to be used by the first station to perform channel contention. Referring to Figure 9B, the MU EDCA parameter set represents the third parameter set.

[0226] Step 1301 is optional and not required. In a possible implementation, the access point directly transmits a radio frame carrying the third parameter set to the first station. In other words, steps 1301 and 1302 may be replaced as follows: The access point transmits a radio frame carrying the third parameter set to the first station, and the radio frame may be an EPCS priority access request frame. The radio frame may further carry a fourth parameter set. The fourth parameter set includes MU EDCA parameters to be used by the second station to perform channel contention. The second station and the first station belong to the same multilink station device.

[0227] 1303: After transmitting the data frame triggered based on the trigger frame of the access point, the first station performs channel contention by using parameters in the third parameter set.

[0228] For step 1303, refer to step 1203.

[0229] In a possible implementation, the response frame further carries a fourth parameter set. The fourth parameter set includes MU EDCA parameters to be used by the second station to perform channel contention. The second station and the first station belong to the same multilink station device. Referring to FIG. 9C, the second station corresponds to per-STA profile 2, and the MU EDCA parameter set in per-STA profile 2 represents the fourth parameter set. In this implementation, after transmitting a data frame triggered based on the access point's trigger frame, the second station performs channel contention by using the parameters in the fourth parameter set.

[0230] In this embodiment of the present application, the request frame does not carry the MU EDCA parameter set, and the response frame carries the MU EDCA parameters that the access point allows the first station to use, thus reducing the amount of data carried in the request frame.

[0231] In the method steps in Figures 8, 10, 11, 12, and 13, a first station transmits a request frame to obtain an MU EDCA parameter set to be used for channel contention. With reference to the accompanying drawings, the following describes a solution in which the first station determines an MU EDCA parameter set to be used based on an EDCA parameter set carried in a beacon frame.

[0232] 14 is a flowchart of another communication method according to an embodiment of the present application. As shown in FIG. 14, the method includes the following steps:

[0233] 1401: A first station sends a request frame to an access point.

[0234] The request frame is used to request to obtain channel priority access. For step 1401, refer to step 1301. Table 6 is an example of fields in a request frame sent by a first station to an access point.

[0235] 1402: The access point sends a response frame to the request frame to the first station.

[0236] Table 5 is an example of the fields in a response frame sent by the access point to the first station.

[0237] In a possible implementation, the request frame is an EPCS priority access allowed request frame and the response frame is an EPCS priority access allowed response frame.

[0238] 1403: The first station determines an MU EDCA parameter set to be used by the first station based on the response frame and the EDCA parameter set carried in the beacon frame.

[0239] In a possible implementation, the MU EDCA parameter set to be used by the first station is used to perform channel contention after successfully transmitting a data frame triggered by the access point's trigger frame. In this implementation, after successfully transmitting a data frame triggered by the access point's trigger frame, the first station performs channel contention by using the determined MU EDCA parameter set, thereby enabling the first station to have higher channel access priority. In a possible implementation, the MU EDCA parameter set to be used by the first station is used to perform channel contention within a second duration after successfully transmitting a data frame triggered by the access point's trigger frame. The second duration is obtained based on parameters in the MU EDCA parameter set.

[0240] In a possible implementation, determining the MU EDCA parameter set to be used by the first station further includes determining the MU EDCA parameter set to be used by the first station based on the MU EDCA parameter set in the beacon frame. In other words, the first station determines the MU EDCA parameter set to be used by the first station based on the EDCA parameter set in the beacon frame and the MU EDCA parameter set. Determining the MU EDCA parameter set to be used by the first station based on the MU EDCA parameter set in the beacon frame may be as follows: The first station determines the MU EDCA parameter set to be used by the first station based on the EDCA parameter set in the beacon frame and an MU EDCA timer in the MU EDCA parameter set. For example, the first station uses the EDCA parameter set in the beacon frame as the MU EDCA parameter set to be used by the first station, and the first station determines, based on an MU EDCA timer in the MU EDCA parameter set, the duration for which channel contention is performed by using the EDCA parameter set as the MU EDCA parameter set. Using the EDCA parameter set in the beacon frame as the MU EDCA parameter set to be used by the first station may include setting the values ​​of the ACI / AIFSN fields and ECWmin / ECWmax fields corresponding to each AC in the EDCA parameter set to the ACI / AIFSN fields and ECWmin / ECWmax fields corresponding to each AC in the MU EDCA parameter set.Determining the duration for which channel contention will be performed by using the EDCA parameter set as the MU EDCA parameter set based on the MU EDCA timer in the MU EDCA parameter set may involve setting the value of the MU EDCA timer field corresponding to each AC in the MU EDCA parameter set in the beacon frame to the MU EDCA timer field corresponding to each AC in the MU EDCA parameter set to be used by the first station. For example, after receiving a trigger frame and successfully transmitting a data frame, the first station performs EDCA channel contention within a certain period of time by using parameters in the EDCA parameter set in the beacon frame. The length of the period is conveyed in the MU EDCA parameter set in the beacon frame. In another example, after receiving a trigger frame and successfully transmitting a data frame, the second station performs EDCA channel contention within a certain period of time by using parameters in the EDCA parameter set of the second station's link. The length of the period is conveyed in the MU EDCA parameter set of the second station's link.

[0241] Compared with the embodiments described in the method steps in Figures 8, 10, 11, 12, and 13, in the embodiment described in the method steps in Figure 14, neither the request frame nor the response frame needs to carry the MU EDCA parameter set, thereby allowing the amount of data to be transmitted to be reduced. Furthermore, the MU EDCA parameter set to be used by the first station is determined based on the EDCA parameter set carried in the beacon frame to obtain parameters with higher channel access priority.

[0242] The following describes a communication device provided in an embodiment of this application.

[0243] In this application, the communication device is divided into functional modules based on the above-described method embodiment. For example, functional modules corresponding to functions may be obtained through division, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division into modules is an example and is merely a logical functional division in this application. In actual implementation, other division methods may exist. Below, the communication device in the embodiment of this application will be described in detail with reference to Figures 15 and 17.

[0244] FIG. 15 is a schematic diagram of the structure of a communication device 1500 according to an embodiment of this application. The communication device 1500 may correspondingly implement functions or steps implemented by the communication devices (e.g., the first station and the access point) in the above-mentioned method embodiments. The communication device may include a processing module 1510 and a transceiver module 1520. Optionally, the communication device may further include a storage unit. The storage unit may be configured to store instructions (codes or programs) and / or data. The processing module 1510 and the transceiver module 1520 may be coupled to the storage unit. For example, the processing module 1510 may read the instructions (codes or programs) and / or data in the storage unit to implement the corresponding method. The above units may be independently located or may be partially or fully integrated. For example, the transceiver module 1520 may include a transmitting module and a receiving module. The transmitting module may be a transmitter, and the receiving module may be a receiver. The entity corresponding to the transceiver module 1520 may be a transceiver.

[0245] In some possible implementations, the communication device 1500 can correspondingly implement the actions and functions of the first station in the method embodiments. For example, the communication device 1500 may be the first station or a component (e.g., a chip or circuit) used in the first station. For example, the transceiver module 1520 may be configured to perform all receiving or transmitting operations performed by the first station in the embodiments shown in Figures 8, 10, 11, 12, 13, and 14, such as steps 801 and 802 in the embodiment shown in Figure 8, steps 1001 and 1002 in the embodiment shown in Figure 10, steps 1101 and 1102 in the embodiment shown in Figure 11, steps 1201, 1202, and 1203 in the embodiment shown in Figure 12, steps 1301 and 1302 in the embodiment shown in Figure 13, steps 1401 and 1402 in the embodiment shown in Figure 14, and / or other processes used to support the techniques described herein. The processing module 1510 is configured to perform all operations other than the transmitting and receiving operations performed by the first station in the embodiments shown in Figures 10, 11, 12, 13 and 14, such as step 1003 in the embodiment shown in Figure 10, step 1103 in the embodiment shown in Figure 11, step 1204 in the embodiment shown in Figure 12, step 1303 in the embodiment shown in Figure 13 and step 1403 in the embodiment shown in Figure 14.

[0246] In some possible implementations, the communication device 1500 can correspondingly implement the actions and functions of an access point in the method embodiments. For example, the communication device 1500 may be an access point or a component (e.g., a chip or circuit) used in an access point. For example, the transceiver module 1520 may be configured to perform all reception or transmission operations performed by the access point in the embodiments shown in Figures 8, 10, 11, 12, 13, and 14, such as steps 801 and 802 in the embodiment shown in Figure 8, steps 1001 and 1002 in the embodiment shown in Figure 10, steps 1101 and 1102 in the embodiment shown in Figure 11, steps 1201 and 1202 in the embodiment shown in Figure 12, steps 1301 and 1302 in the embodiment shown in Figure 13, steps 1401 and 1402 in the embodiment shown in Figure 14, and / or other processes used to support the techniques described herein. The processing module 1510 is configured to perform all operations other than the transmitting and receiving operations performed by the access point in the embodiment shown in FIG. 11, for example, step 1102 in the embodiment shown in FIG.

[0247] The first station and the access point in the embodiments of this application have been described above. Possible product forms of the first station and the access point will be described below. It should be understood that any type of product having the function of the first station in FIG. 15 and any type of product having the function of the access point in FIG. 15 fall within the scope of protection of the embodiments of this application. It should be further understood that the following description is merely an example, and the product forms of the access point and the first station in the embodiments of this application are not limited thereto.

[0248] In a possible implementation manner, in the communication device shown in FIG. 15 , the processing module 1510 may be one or more processors, and the transceiver module 1520 may be a transceiver, or the transceiver module 1520 may be a transmitting unit and a receiving unit. The transmitting unit may be a transmitter, and the receiving unit may be a receiver. The transmitting unit and the receiving unit may be integrated into one component, for example, a transceiver. In this embodiment of the present application, the processor and the transceiver may be combined, etc. The connection manner between the processor and the transceiver is not limited in this embodiment of the present application.

[0249] 16 is a schematic diagram of the structure of another communication device 160 according to an embodiment of the present application. The communication device in FIG. 16 may be the above-mentioned first station, or may be the above-mentioned access point.

[0250] 16, the communications device 160 includes one or more processors 1620 and a transceiver 1610. The transceiver 1610 may implement the functionality of the transceiver module 1520. The processor 1620 may implement the functionality of the processing module 1510.

[0251] In each implementation of the communication apparatus shown in Figure 16, the transceiver may include a receiver and a transmitter. The receiver is configured to perform receiving functions (or operations). The transmitter is configured to perform transmitting functions (or operations). The transceiver is configured to communicate with other devices / apparatuses over a transmission medium.

[0252] Optionally, the communication device 160 may further include one or more memories 1630 configured to store program instructions and / or data. The memory 1630 is coupled to the processor 1620. The coupling in this embodiment of the application may be an electrical, mechanical, or other type of indirect coupling or communication connection between devices, units, or modules, used for information exchange between the devices, units, or modules. The processor 1620 may operate in cooperation with the memory 1630. The processor 1620 may execute program instructions stored in the memory 1630.

[0253] The specific connection medium between the transceiver 1610, the processor 1620, and the memory 1630 is not limited in this embodiment of the application. In this embodiment of the application, the memory 1630, the processor 1620, and the transceiver 1610 are connected to each other through a bus 1640 in FIG. 16. In FIG. 16, the bus is represented by using a thick line. The connection scheme between the other components is merely an example for explanation and does not impose limitations. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used to represent the bus in FIG. 16. However, this does not indicate that only one bus or only one type of bus exists.

[0254] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., which may implement or perform the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor, any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of this application may be performed directly by a hardware processor, or may be performed by a combination of hardware modules and software modules in a processor.

[0255] In this embodiment of the application, memory may include, but is not limited to, non-volatile memory, such as a hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), compact disc read-only memory (CD-ROM), etc. Memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures and that can be read and / or written by a computer (e.g., a communication device shown in this application). However, it is not limited thereto. Memory in this embodiment of the application may alternatively be a circuit or any other device capable of performing a storage function and configured to store program instructions and / or data.

[0256] The processor 1620 is primarily configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data of the software programs. The memory 1630 is primarily configured to store software programs and data. The transceiver 1610 may include control circuitry and an antenna. The control circuitry is primarily configured to convert between baseband signals and radio frequency signals and process the radio frequency signals. The antenna is primarily configured to receive and transmit radio frequency signals in the form of electromagnetic waves. An input / output device, such as a touchscreen, display, or keyboard, is primarily configured to receive data entered by a user and output data to a user.

[0257] After the communication device is powered on, the processor 1620 may read the software program in the memory 1630, interpret and execute the instructions of the software program, and process data of the software program. When data needs to be transmitted wirelessly, the processor 1620 performs baseband processing on the data to be transmitted and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal in the form of electromagnetic waves through an antenna. When data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal to a baseband signal, and outputs the baseband signal to the processor 1620. The processor 1620 converts the baseband signal to data and processes the data.

[0258] In other implementations, the radio frequency circuitry and antenna may be located independently of the processor performing the baseband processing, for example, in a distributed scenario, the radio frequency circuitry and antenna may be located independently and remotely from the communication device.

[0259] It can be understood that the communication device shown in this embodiment of the present application may further include more components than those in FIG. 16 , etc. This is not limited to this embodiment of the present application. The methods performed by the processor and the transceiver are merely examples. For specific steps performed by the processor and the transceiver, please refer to the above methods.

[0260] In another possible implementation, in the communication device shown in FIG. 15 , the processing module 1510 may be one or more logic circuits, and the transceiver module 1520 may be an input / output interface, also referred to as a communication interface, interface circuit, interface, etc. Alternatively, the transceiver module 1520 may be a transmitting unit and a receiving unit. The transmitting unit may be an output interface, and the receiving unit may be an input interface. Alternatively, the transmitting unit and the receiving unit may be integrated into one unit, for example, an input / output interface. As shown in FIG. 17 , the communication device shown in FIG. 17 includes a logic circuit 1701 and an interface 1702. In other words, the processing module 1510 may be implemented using the logic circuit 1701, and the transceiver module 1520 may be implemented using the interface 1702. The logic circuit 1701 may be a chip, a processing circuit, an integrated circuit, a system on chip (SoC) chip, etc., and the interface 1702 may be a communication interface, an input / output interface, a pin, etc. For example, an example in which the above communication device is a chip is used in Figure 17. The chip includes a logic circuit 1701 and an interface 1702.

[0261] In this embodiment of the present application, the logic circuit and the interface may further be coupled to each other, and the specific connection manner of the logic circuit and the interface is not limited in this embodiment of the present application.

[0262] For example, when the communication device is configured to perform the above-described methods, functions, or steps performed by the first station, the logic circuit 1701 is configured to generate a request frame and the interface 1702 is configured to output the request frame.

[0263] For example, when the communication device is configured to perform a method, function, or step performed by an access point, the interface 1702 is configured to input a request frame, the logic circuit 1701 is configured to generate a response frame based on the request frame, and the interface 1702 is configured to output the response frame.

[0264] It can be understood that the communication device shown in this embodiment of this application may implement the methods provided in the embodiment of this application in the form of hardware or software, which is not limited to this embodiment of this application.

[0265] An embodiment of the present application further provides a wireless communication system. The wireless communication system includes a first station and an access point. The first station and the access point may be configured to perform the method in any one of the above embodiments (shown in FIGS. 8 and 10 to 14).

[0266] This application further provides a computer-readable storage medium that stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by the first station in the methods provided in this application.

[0267] This application further provides a computer-readable storage medium that stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by the access point in the methods provided in this application.

[0268] This application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the operations and / or processes performed by the first station in the methods provided in this application.

[0269] This application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the operations and / or processes performed by the access point in the methods provided in this application.

[0270] In some embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of function. In actual implementation, other division methods may be used. For example, multiple units or components may be combined or integrated into other systems, or some features may be ignored or not implemented. Furthermore, the illustrated or discussed mutual couplings, direct couplings, or communication connections may be indirect couplings or communication connections through some interfaces, devices, or units, or may be electrical, mechanical, or other types of connections.

[0271] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, and may be located in one location or distributed across multiple network elements. Some or all of the units may be selected according to actual requirements to achieve the technical effects of the solutions provided in the embodiments of this application.

[0272] Furthermore, the functional units in the embodiments of this application may be integrated into one processing unit, or each unit may exist physically independently, or two or more units may be integrated into one unit. The integrated unit may be realized in the form of hardware or in the form of a software functional unit.

[0273] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application may essentially, or the portion contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product. The computer software product is stored in a readable storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method described in the embodiments of this application. The above-mentioned readable storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0274] The above description is merely a specific implementation of this application and is not intended to limit the scope of protection of this application. Any modifications or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in this application shall fall within the scope of protection of this application. Therefore, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. 1. A communication method comprising: receiving a request frame from a first station, the first station associating with EPCS non-AP MLD; transmitting a response frame to the request frame to the first station, the response frame carrying a third parameter set, the third parameter set including multi-user (MU) enhanced distributed channel access (EDCA) parameters to be used by the first station to perform channel contention; Including, The method, wherein the response frame further carries a fourth parameter set, the fourth parameter set including MU EDCA parameters to be used by a second station to perform channel contention, and the second station and the first station belong to the same multilink station device.

2. The method of claim 1 , wherein the third parameter set is included in a priority access multilink element (MLE) field.

3. The method of claim 1 , wherein the third parameter set is included in a link information field within a priority access MLE field.

4. 1. A communication method comprising: transmitting a request frame to an access point; receiving a response frame transmitted by the access point in response to the request frame, the response frame carrying a third parameter set, the third parameter set including multi-user (MU) enhanced distributed channel access (EDCA) parameters to be used by the first station to perform channel contention, the first station working with EPCS non-AP MLD; Including, The method, wherein the response frame further carries a fourth parameter set, the fourth parameter set including MU EDCA parameters to be used by a second station to perform channel contention, and the second station and the first station belong to the same multilink station device.

5. 5. The method of claim 4, further comprising: performing channel contention by using the parameters in the third parameter set after a data frame triggered based on a trigger frame of the access point is transmitted.

6. The method of claim 4 , wherein the third parameter set is included in a priority access multilink element (MLE) field.

7. The method of claim 4 , wherein the third parameter set is included in a link information field within a priority access MLE field.

8. A communication device, a transceiver module configured to receive a request frame from a first station, the first station associating with an EPCS non-AP MLD; a processing module configured to generate a response frame to the request frame; Including, the transceiver module is further configured to transmit the response frame to the request frame to the first station, the response frame carrying a third parameter set, the third parameter set including multi-user (MU) enhanced distributed channel access (EDCA) parameters to be used by the first station to perform channel contention; The response frame further carries a fourth parameter set, the fourth parameter set including MU EDCA parameters to be used by a second station to perform channel contention, and the second station and the first station belong to the same multilink station device.

9. The apparatus of claim 8 , wherein the third parameter set is included in a priority access multilink element (MLE) field.

10. The apparatus of claim 8 , wherein the third parameter set is included in a link information field within a priority access MLE field.

11. A communication device, a processing module configured to generate a request frame; a transceiver module configured to transmit the request frame to an access point and receive a response frame transmitted by the access point in response to the request frame, the response frame carrying a third parameter set, the third parameter set including multi-user (MU) enhanced distributed channel access (EDCA) parameters to be used by the communication device to perform channel contention, the communication device cooperating with EPCS non-AP MLD; Including, The response frame further carries a fourth parameter set, the fourth parameter set including MU EDCA parameters to be used by the second station to perform channel contention, and the second station and the first station belong to the same multilink station device.

12. 12. The apparatus of claim 11, wherein the processing module is further configured to perform channel contention by using the parameters in the third parameter set after a data frame triggered based on a trigger frame of the access point is transmitted.

13. The apparatus of claim 11 , wherein the third parameter set is included in a priority access multilink element (MLE) field.

14. The apparatus of claim 11 , wherein the third parameter set is included in a link information field within a priority access MLE field.

15. 1. A computer-readable storage medium, comprising:

8. The computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a processor, enable the processor to perform the method of any one of claims 1 to 7.

Images