Communication methods and communication devices

Abstract

The present invention provides a communication method and communication device that optimize channel access parameters. [Solution] The first station sends a request frame to the access point. The request frame is used to request preferential access to the channel. The request frame carries a first parameter set. The first parameter set includes Multi-User Extended Distributed Channel Access (MU EDCA) parameters that the first station intends to use to perform channel contention. The first station, which is an Emergency Alert Communications Service (EPCS) station, also receives a response frame to the request frame and performs channel access by using the MU EDCA mechanism.

Description

Technical Field

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

Background Art

[0002] Emergency preparedness communications service (EPCS) is a service with extremely high requirements for communication delay, for example, a communication service in critical scenarios such as fires and earthquakes. For EPCS, the wireless local area network standard 802.11be defines a priority access mechanism, whereby an EPCS station can access the channel as soon as possible to ensure the priority transmission of emergency services. An EPCS station is a station that needs to execute EPCS. Therefore, it is necessary to study a solution that enables an EPCS station to access the channel as soon as possible in various scenarios.

Summary of the Invention

[0003] Embodiments of this application disclose a communication method and a communication device.

[0004] According to a first aspect, embodiments of this application provide a communication method. The method includes transmitting a request frame to an access point, where the request frame is used to request to obtain channel priority access rights, the request frame carries a first parameter set, and the first parameter set includes multi-user (MU) extended distributed channel access (EDCA) parameters intended to be used by a first station to perform channel contention, and receiving a response frame to the request frame. In the first aspect and possible implementation manners of the first aspect, the executor is the first station.

[0005] In this embodiment of the application, the first parameter set includes MU EDCA parameters intended for use by the first station to perform channel contention. A request frame carrying the first parameter set is sent. In this way, channel contention is performed by using parameters having a higher channel access priority.

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

[0007] In this implementation, channel contention is performed using parameters from a first parameter set after a data frame triggered based on the access point's trigger frame has been transmitted. Compared to a typical station, the first station has a higher channel access priority.

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

[0009] In this implementation, channel contention is performed within a first duration by using parameters in a first parameter set. This follows the MU EDCA mechanism. In this way, 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 embodiment may be replaced as follows: The first station transmits a request frame to the access point. The request frame carries a second parameter set. The second parameter set includes MU EDCA parameters intended for use by the second station to perform channel conflict. 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 for the request frame. The response frame carries a fourth parameter set. The fourth parameter set includes MU EDCA parameters that the access point permits the second station to use to perform channel conflict. The fourth parameter set may be the same as or different from the second parameter set.

[0011] In this embodiment of the application, the second parameter set includes MU EDCA parameters intended for use by the second station to perform channel contention. A request frame carrying the second parameter set is sent. In this way, channel contention is performed by using parameters having a higher channel access priority.

[0012] According to a second aspect, an embodiment of the present application provides a communication method, the method comprising the steps of: sending a request frame to an access point, the request frame being used to request preferential access to a channel; and receiving a response frame to the request frame, the response frame carrying a third parameter set, the third parameter set comprising MU EDCA parameters to be used by a first station to perform channel conflict. In other words, the third parameter set comprises MU EDCA parameters that the access point permits the first station to use to perform channel conflict. In the second aspect and possible implementations thereof, the implement is the first station.

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

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

[0015] In this implementation, channel contention is performed using parameters in a third parameter set after a data frame triggered based on the access point's trigger frame has been transmitted. Compared to a typical station, the first station has a higher channel access priority.

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

[0017] In this implementation, channel contention is performed within a third duration by using parameters in a third parameter set. This follows the MU EDCA mechanism. In this way, 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, embodiments of the present application provide another communication method, the method comprising the steps of: sending a request frame to an access point, the request frame being used to request channel priority access; receiving a response frame to the request frame; and determining a MU EDCA parameter set to be used by the first station based on the response frame and a set of EDCA parameters carried in the beacon frame. In the third aspect and possible implementations of the third aspect, the implement is the first station.

[0019] In this embodiment of the 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 having a 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 access point's trigger frame has been 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 access point's trigger frame has been 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] In this implementation method, the following problems can be solved. An MU EDCA parameter set with a higher channel access priority cannot be accurately and quickly determined based only on the EDCA parameter set carried in the beacon frame.

[0024] In a possible implementation method, 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 method, an MU EDCA parameter set with a higher channel access priority can be accurately and quickly determined.

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

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

[0028] In this implementation method, the request frame is an emergency warning communication service EPCS priority accessable request frame, and the response frame is an EPCS priority accessable response frame. Since both the request frame and the response frame are existing frames, no additional signaling needs to be transmitted for the reception and transmission of the request frame and the response frame.

[0029] According to the fourth aspect, an embodiment of this application provides another communication method. The method includes receiving a request frame from a first station, where the request frame is used to request obtaining channel priority access rights, the request frame carries a first parameter set, and the first parameter set includes MU EDCA parameters intended to be used by the first station to perform channel contention, and transmitting a response frame to the first station for the request frame. In the fourth aspect and possible implementation manners of the fourth aspect, the executor is an access point.

[0030] In this embodiment of this application, the first parameter set includes MU EDCA parameters intended to be used by the first station to perform channel contention. The request frame carrying the first parameter set may be received to obtain the MU EDCA parameters intended to be used by the first station to perform channel contention.

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

[0032] In this implementation manner, the first parameter set is included in the link information field within the multi-link element MLE in the request frame to independently indicate a set of MU EDCA parameters intended to be used by the first station to perform channel contention. The first parameter set is included in the MU EDCA parameter set field in the request frame, thereby enabling the access point to quickly obtain the first parameter set from the MU EDCA parameter set field in the request frame.

[0033] In possible implementations of the first or fourth embodiment, the request frame further carries a second parameter set, which 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.

[0034] In this implementation, the request frame further carries a second set of parameters. The second station may notify the access point of the second set of parameters it intends to use without sending a request frame, thereby reducing signaling overhead.

[0035] In possible implementations of the first or fourth embodiment, the second set of parameters is included in the link information field within the MLE in the request frame.

[0036] In this implementation, the second parameter set independently specifies the MU EDCA parameters that are included in the link information field within the MLE in the request frame and are intended to be used by the second station to perform channel contention.

[0037] In possible implementations of the first or fourth embodiment, the response frame carries a third parameter set, which 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.

[0038] In this implementation, the response frame carries a third set of parameters, which allows the first station to perform channel contention by using the parameters in the third set of parameters to ensure channel access priority.

[0039] In possible implementations of the first or fourth embodiment, 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 the perspective of the first station. Access points and other stations are not considered. The third parameter set is determined by the access point from an overall perspective. Multiple stations are 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 possible implementations of the first or fourth embodiment, 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. The first station has a higher channel access priority when it performs channel contention using parameters from the third parameter set compared to when it performs channel contention using parameters from the first parameter set.

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

[0044] In this implementation, the response frame carries a third set of parameters, which allows the first station to perform channel contention by using the parameters in the third set of parameters to ensure channel access priority.

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

[0046] In this implementation, the third parameter set is included in the link information field within the MLE in the response frame, independently indicating the MU EDCA parameters to be used by the first station to perform channel contention. The third parameter set is included in the MU EDCA parameter set field in the response frame, thereby enabling the first station to quickly retrieve the third parameter set from the MU EDCA parameter set field in the response frame.

[0047] In possible implementations of the first or fourth embodiment, 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. 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 set of parameters. The access point does not need to send the response frame separately to the second station, reducing signaling overhead.

[0049] In possible implementations of the first or fourth embodiment, 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 the perspective of the second station. Access points and other stations are not considered. The fourth parameter set is determined by the access point from an overall perspective. Multiple stations are 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 possible implementations of the first or fourth embodiment, 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. The second station has a higher channel access priority when it performs channel contention using parameters from the fourth parameter set compared to when it performs channel contention using parameters from the second parameter set.

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

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

[0055] In possible implementations of the first or fourth embodiment, the fourth parameter set is included in the link information field within the MLE in the response frame.

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

[0057] In possible implementations of the first or fourth embodiment, the request frame is an EPCS priority access request frame for emergency alert communication services, and the response frame is an EPCS priority access response frame.

[0058] In this implementation, the request frame is an EPCS priority access request frame for the emergency alert communication service, and the response frame is an EPCS priority access response frame. Since both the request frame and the response frame are existing frames, no further signaling is required for the reception and transmission of the request and response frames.

[0059] In possible implementations of the first or fourth embodiment, 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 is not an EPCS station.

[0060] The communication method in the fourth embodiment may be replaced as follows: The access point receives a request frame from the first station. The request frame carries a second parameter set. The second parameter set includes MU EDCA parameters intended for use by the second station to perform channel conflict. 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 for the request frame. The response frame carries a fourth parameter set. The fourth parameter set includes MU EDCA parameters that the access point permits the second station to use to perform channel conflict. The fourth parameter set may be the same as or different from the second parameter set.

[0061] In this embodiment of the application, a fourth set of parameters 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 having a higher channel access priority.

[0062] According to a fifth aspect, embodiments of the present application provide another communication method, the method comprising: receiving a request frame from a first station, the request frame being used to request channel priority access; and transmitting a response frame to the first station, the response frame carrying a third parameter set, the third parameter set comprising MU EDCA parameters to be used by the first station to perform channel conflict. In other words, the third parameter set comprises MU EDCA parameters that the access point permits the first station to use to perform channel conflict. In the fifth aspect and possible implementations of the fifth aspect, the implementer is an access point.

[0063] In this embodiment of the application, the third parameter set includes MU EDCA parameters to be used by the first station to perform channel competition. A response frame carrying the third parameter set is transmitted to the first station so that the first station can perform channel competition by using the third parameter set to obtain a higher channel access priority.

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

[0065] In this implementation, the third parameter set is included in the link information field within the MLE in the response frame, independently indicating the MU EDCA parameters to be used by the first station to perform channel contention. The third parameter set is included in the MU EDCA parameter set field in the response frame, thereby enabling the first station to quickly retrieve the third parameter set from the MU EDCA parameter set field in the response frame.

[0066] In possible implementations of the second or fifth embodiment, 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. 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 set of parameters. The access point does not need to send the response frame separately to the second station, reducing signaling overhead.

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

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

[0070] In possible implementations of the second or fifth embodiment, the request frame is an EPCS priority access request frame for emergency alert communication services, and the response frame is an EPCS priority access response frame.

[0071] In this implementation, the request frame is an EPCS priority access request frame for the emergency alert communication service, and the response frame is an EPCS priority access response frame. Since both the request frame and the response frame are existing frames, no further signaling is required for the reception and transmission of the request and response frames.

[0072] In possible implementations of the second or fifth embodiment, the channel access priority of the third parameter set is higher than the channel access priority of the MU EDCA parameter set used by a typical station. 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 a method in the first, second, third, or any possible implementation thereof. The communication device includes a corresponding unit configured to perform a method in the first, second, third, 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, second, or third embodiment, such as a non-AP MLD, STA, or a chip within a non-AP MLD, such as a Wi-Fi chip.

[0075] According to the seventh aspect, an embodiment of the present application provides a communication device configured to perform a method in the fourth aspect, the fifth aspect, or any possible implementation thereof. The communication device includes a corresponding unit configured to perform a method in 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 includes an access point in the fourth or fifth embodiment, for example, an AP MLD, an AP, or a chip in the AP MLD such as a Wi-Fi chip.

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

[0078] In the process of performing the above method, the process of transmitting information and the process of receiving information in the above method may be understood as the process of outputting information by the processor and the process of receiving input information by the processor. When outputting information, the processor outputs the information to the transceiver so that the transceiver can transmit the information. After the information is output by the processor, further 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 it to the processor. Furthermore, after the transceiver receives the information, further processing may need to be performed on the information before it is input to the processor.

[0079] Based on the above principles, for example, sending a request frame as described above may be understood as the processor outputting the request frame. In another example, receiving a response frame may be understood as the processor receiving the input response frame.

[0080] Operations such as transmission, sending, and receiving associated with a processor may more generally be understood as operations such as output, receiving, and input of a processor, unless otherwise specified, or if the operation does not contradict the actual function or internal logic of the operation in the relevant description.

[0081] In the implementation process, the processor may be a dedicated processor for performing 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 non-transitory memory, such as read-only memory (ROM). The memory and processor may be integrated on the same chip, or they may be located on different chips. The type of memory, and the arrangement of the memory and processor, are not limited to this embodiment of this application.

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

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

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

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

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

[0087] According to the ninth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to execute a program stored in memory. When the program is executed, the communication device becomes capable of performing a method in the fourth aspect, the fifth aspect, or any possible implementation thereof.

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

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

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

[0091] In possible implementations, the communication device further includes a transceiver. The transceiver is configured to receive and / or transmit signals. For example, the transceiver may be configured to receive request frames. In other examples, the transceiver may be further configured to transmit response frames, etc.

[0092] In this embodiment of the application, the communication device may be an access point in the fourth or fifth embodiment. For example, the access 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 to output data. The processing circuit is configured to perform a corresponding method in a first aspect or a possible implementation of either the first aspect, or the processing circuit is configured to perform a corresponding method in a second aspect or a possible implementation of either the second aspect, or the processing circuit is configured to perform a corresponding method in a third aspect or a possible implementation of either the third aspect.

[0094] According to the 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 to output data. The processing circuit is configured to perform a corresponding method in the fourth aspect or any possible implementation of the fourth aspect, or the processing circuit is configured to perform a corresponding method in the fifth aspect or any possible implementation of the fifth aspect.

[0095] According to a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program. When the computer program is executed on a computer, a method in the first aspect, the second aspect, the third aspect, or any possible implementation thereof is performed.

[0096] According to the thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program. When the computer program is executed on a computer, a method in the fourth aspect, the fifth aspect, or any possible implementation thereof is performed.

[0097] According to the fourteenth aspect, an embodiment of this application provides a computer program product, the computer program product comprising a computer program or computer code, when the computer program product is executed on a computer, the method in the first aspect, the second aspect, the third aspect, or any possible implementation thereof is performed.

[0098] According to the fifteenth aspect, an embodiment of this application provides a computer program product, the computer program product comprising a computer program or computer code, when the computer program product is executed on a computer, the method in the fourth aspect, the fifth aspect, or any possible implementation thereof is performed.

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

[0100] According to the 17th aspect, embodiments of this application provide a multilink communication system. The multilink communication system includes an STA and an AP MLD. Optionally, the STA is configured to perform a method in the first aspect or any possible implementation of the first aspect, and the AP MLD is configured to perform a method in the fourth aspect or any possible implementation of the fourth aspect. Optionally, a non-AP MLD is configured to perform a method in the second aspect or any possible implementation of the second aspect, and the AP MLD is configured to perform a method in the fifth aspect or any possible implementation of the fifth aspect. The AP MLD can be replaced with an AP. [Brief explanation of the drawing]

[0101] To more clearly illustrate the embodiments or technical solutions in the background art of this application, the accompanying drawings illustrating the embodiments or background art of this application are briefly described below. [Figure 1A] This is a schematic diagram of a multilink communication scenario according to an embodiment of this application. [Figure 1B] This is a schematic diagram of a multilink communication scenario according to an embodiment of this application. [Figure 1C] This is a schematic diagram of a multilink communication scenario according to an embodiment of this application. [Figure 2] This shows an example of the basic access process of the CSMA / CA mechanism. [Figure 3] This example shows the backoff process for multiple STAs under DCF. [Figure 4] Here is an example of the exponential increase in CW. [Figure 5] Examples of EDCA parameter sets for different AC services according to embodiments of this application are shown. [Figure 6] An example of an MLE frame body is shown. [Figure 7] This is a schematic diagram illustrating the operating principle of the MU EDCA mechanism according to the embodiment of this application. [Figure 8]This is a flowchart of the communication method according to an embodiment of this application. [Figure 9A] This is an example of the format of a priority access multi-link element field according to an embodiment of this application. [Figure 9B] This is an example of the format of a priority access multi-link element field according to an embodiment of this application. [Figure 9C] This is an example of the format of a priority access multi-link element field according to an embodiment of this application. [Figure 10] This is a flowchart of another communication method according to an embodiment of this application. [Figure 11] This is a flowchart of another communication method according to an embodiment of this application. [Figure 12] This is a flowchart of another communication method according to an embodiment of this application. [Figure 13] This is a flowchart of another communication method according to an embodiment of this application. [Figure 14] This is a flowchart of another communication method according to an embodiment of this application. [Figure 15] This is a schematic diagram of the structure of a communication device according to an embodiment of the present invention. [Figure 16] This is a schematic diagram of the structure of a communication device according to an embodiment of the present invention. [Figure 17] This is a schematic diagram of the structure of a communication device according to an embodiment of the present invention. [Modes for carrying out the invention]

[0102] In the specification, claims, or accompanying drawings of this application, terms such as “first,” “second,” etc., are intended solely to distinguish between different objects and not to indicate a specific order. Furthermore, the terms “include,” “comprise,” and any variation thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device comprising a set of steps or units may, at their discretion, further include other steps or units not listed, or other inherent steps or units of the process, method, product, or device, not limited to those listed.

[0103] The “embodiments” as used in this specification mean that certain features, structures, or characteristics described with reference to this specification may be included in at least one embodiment of this application. The terms used in various parts of this specification do not necessarily mean the same embodiment and are not exclusive, independent, or optional embodiments from other embodiments. It will be 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 to describe specific embodiments and not to limit this application. The terms “one,” “a,” “the,” “the foregoing,” “this,” and “the one” as used in this specification and the claims attached to this application are also intended to include the plural unless explicitly specified otherwise in the context. The terms “and / or” as used in this application should further be understood to indicate and include any and all possible combinations of one or more listed items. For example, “A and / or B” may mean one of the following three cases: that only A exists, that only B exists, and that both A and B exist, where A and B may be singular or plural. In this application, the term “at least one” means one or more, and “plural” means two or more. The expression “at least one of the following items” or similar expressions indicates any combination of these items, including any combination of singular 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. Here, a, b, and c may each be singular or plural.

[0105] The following will first describe the terminology and technical features of the embodiments of this application.

[0106] Multilink communication

[0107] With the advancement of wireless technology, an increasing number of wireless devices support multilink communication. For example, some wireless devices can communicate simultaneously on the 2.4GHz, 5GHz, and 6GHz frequency bands, or on different channels within the same frequency band. This improves the communication rate between wireless devices. Devices that support multilink communication are usually called multilink devices (MLDs).

[0108] A multilink device includes one or more interoperability stations (STAs). An interoperability station is a logical station and may operate on one link, one frequency band, one channel, etc. An interoperability 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 interoperability station is an AP may be called a multilink AP, a multilink AP device, or an AP multi-link device (AP MLD). A multilink device in which the interoperability station is a non-AP STA may be called a multilink STA, a multilink STA device, or an STA multi-link device, or a multilink device in which the interoperability station is a non-AP STA may be called a multilink non-AP, a multilink non-AP device, or a non-AP multi-link device (non-AP MLD), etc. In the following explanation, a multilink device whose connecting station is an AP is called an AP MLD, and a multilink device whose connecting station is a non-AP STA is called a non-AP MLD. An AP MLD has one or more connecting APs. An STA MLD has one or more connecting STAs.

[0109] A station device may communicate with an access point device after multilink establishment (or 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, the multilink access point device includes n APs, e.g., AP1 to APn, and the 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 within the device. The multilink element may also be called a multilink information element. Similarly, an association response frame sent back to the station by the access point may also carry an MLE for carrying information about the multilink access point device and other access points within the device.

[0111] A multilink device (which may be a non-AP MLD or AP MLD) is a communication device having wireless communication capabilities. The communication device may be an entire device, or a chip or processing system installed in the entire device. A device on which a chip or processing system is 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 transmit and receive 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 enables a user to communicate with an AP and then with a WLAN. For example, a non-AP multilink device may be an Internet-connected user device 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 Things. Alternatively, the non-AP multilink device may be a chip and processing system within the terminal described above. The AP multilink device may be a device that provides services to the non-AP multilink device and may support the 802.11 series protocol. For example, the AP multilink device may be a communication entity such as a communication server, router, switch, or bridge, or it may include various forms of macro base stations, micro base stations, relay stations, etc. Clearly, the AP multilink device may, as an alternative, be a chip and processing system within various forms of devices. The 802.11 protocol may be a protocol that supports 802.11be or is compatible with 802.11be.

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

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

[0114] Figure 1C is a schematic diagram of another multilink communication scenario according to an embodiment of this application. As shown in Figure 1C, it includes at least one AP and at least one STA. Figure 1C shows three STAs, for example, STA1, STA2, and STA3. Figure 1C shows two APs, for example, AP1 and AP2. For example, STA1 and STA3 may communicate with AP1 through different links, and the two links may be represented by the two arrows shown in Figure 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 any of the above), 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 a 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 an STA intends to transmit data, the STA must perform a clear channel assessment (CCA) on the wireless medium. If the medium state (i.e., the state of the wireless medium) is idle for a period of time (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 period of time (e.g., DIFS). After the random backoff process is complete, the STA may transmit data. The random backoff time during which the STA must perform a backoff is the time obtained by multiplying the random backoff value by each slot (e.g., 9 μs). The random backoff value is randomly selected from an evenly distributed window [0, CW]. The contention window (CW) has multiple values. The contention window takes its minimum value, i.e., CWmin, on the initial attempt. However, CW gradually increases until it reaches its maximum value, i.e., CWmax, when a retransmission needs to be performed each time a transmission fails (e.g., a conflict occurs). However, when the STA successfully transmits data, CW is reset to CWmin. The size of each window can be the difference between a power of 2 and 1, and is approximately twice the size of 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 or not through energy detection (ED) and preamble detection (PD). Virtual carrier sensing is located in the MAC and determines whether the channel is idle or not based on the duration field in the received radio frame. After receiving the 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 that the station transmitting the radio frame must occupy the channel. After the STA sets the NAV, a countdown begins. When the countdown reaches 0, this indicates that the channel is idle. A channel is considered idle only when both the physical and virtual carrier sensing mechanisms believe that the channel is 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, the station initiates a random backoff process after the idle state has been maintained for a certain period. This period may be one of the following: DIFS, point coordination function (PCF) inter-frame space (PCF inter-frame space, PIFS), or short inter-frame space (SIFS). The station determines a random backoff time for the backoff. The backoff window in Figure 2 corresponds to the random backoff time. Figure 3 shows an example of the backoff process for multiple STAs under DCF.As shown in Figure 3, initially, STA A sends a data frame, and STA B, STA C, and STA D all delay sending their data frames. After STA A has sent a complete data frame (the channel is idle), STA B, STA C, and STA D begin the random backoff process. STA C completes the random backoff process first and then sends a data frame. After STA C has sent a complete data frame (the channel is idle), STA B, STA D, and STA E begin the random backoff process. STA D completes the random backoff process first and then sends a data frame. The rest may be estimated by analogy.

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

[0120] Enhanced Distributed Channel Access (EDCA) Competitive Transmission

[0121] EDCA is an extension of the DCF mechanism. EDCA allows services in 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 represents the arbitration interframe spacing number, TXOP represents the transmission opportunity, TXOP limit represents the transmission opportunity limit, and AC_BK, AC_BE, AC_VI, and AC_VO represent different ACs.

[0122] For a specific AC service, the service backoff process is essentially the same as the DCF backoff process, the difference being that AIFS replaces DIFS in DCF. Specifically, when the channel returns to idle again, the STA must wait for AIFS before executing 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 service's EDCA parameter set 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 must wait for aSIFSTime + 3 * aSlotTime before executing the backoff process. Here, aSIFSTime represents the slot length, which is typically 9 μs, and SIFSTime represents the SIFS length, which is typically 16 μs. Furthermore, the initial value of the service backoff counter should be randomly generated from [0,31]. The AP transmits the EDCA parameter set within 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 MLE frame body. As shown in Figure 6, the MLE includes element ID, length, element ID extension, multi-link control field, common info field, and 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 multi-link control field carries the type of multilink element and instructional information indicating which fields appear and do not appear in common info. For example, the link info field contains zero, one or more per-STA profile sub-elements. As shown in Figure 6, the link info field contains per-STA profile 1 to per-STA profile x, where x is an integer greater than 0. A per-STA profile sub-element may include a subelement ID, length, station control field, station info field, and 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 to 802.11ac and previous standards, stations that comply with the 802.11ax standard have two uplink transmission methods: EDCA-based competition 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 clearly unfair to legacy stations. To maintain relative fairness, the MU EDCA mechanism was introduced into the 802.11ax standard, thereby ensuring that legacy stations are not at a significant disadvantage when performing channel competition. Furthermore, since trigger-based uplink transmission has higher transmission efficiency than competition-based access transmission, it is expected that APs 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., after receiving a trigger frame), the priority of conventional EDCA access should be lowered. Specifically, the station performs channel access by using another set of EDCA parameters, namely the MU EDCA parameter set. The station may perform channel access by using two groups (or two sets) of EDCA parameter sets: one group being the conventional EDCA parameter set and the other being the MU EDCA parameter set. Compared to performing channel access using the conventional EDCA parameter set, performing channel access by the station using the MU EDCA parameter set accommodates longer contention latency and a larger backoff window. Therefore, performing channel access using the MU EDCA parameter set has a lower priority compared to performing channel access using the conventional EDCA parameter set.

[0128] The AP adds two groups of EDCA parameter sets to the beacon frame or the associated response frame of the beacon frame. One group is the conventional EDCA parameter set, and the other group is the MU EDCA parameter set. As described above, the parameters in the MU EDCA parameter set are more conservative, i.e., larger AIFSN, larger CWmin, and 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, the station may perform EDCA contention by using the conventional EDCA parameter set. When the station receives a trigger frame transmitted by the AP and performs uplink data transmission, the station must perform channel contention by 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 has successfully completed uplink data transmission once, the station may revert to the conventional EDCA contention method, i.e., perform channel contention by 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 operating 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 transmitted 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 a 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 and has successfully completed uplink data transmission once.

[0129] EPCS priority access mechanism

[0130] Regarding EPCS, 802.11be defines a priority access mechanism that allows EPCS stations to access channels as quickly as possible to ensure priority transmission of emergency services.

[0131] A station may request an EPCS priority access opportunity by sending an EPCS priority access enable request frame to an access point. The access point may send 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 parameters 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 set carried in the EPCS priority access enable request frame and the EPCS priority access enable response frame has a higher priority than the EDCA parameter set carried in the beacon frame, thereby giving the EPCS station (or EPCS STA) a higher priority than a general station in EDCA contention. 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 may send an EPCS priority access enable request frame, but a general station may not.

[0132] A non-AP MLD may also use the EPCS priority access mechanism. Specifically, one STA in the non-AP MLD submits 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 in this application as an EPCS non-AP MLD.

[0133] As described above, according to the MU EDCA channel access mechanism, after receiving a trigger frame transmitted by an AP and successfully transmitting a data frame, an EPCS station uses the MU EDCA parameter set as the parameter for channel access. However, all stations within the entire cell use the same MU EDCA parameter set. Therefore, after receiving a trigger frame transmitted by an AP and successfully transmitting a data frame, an EPCS station loses channel access priority compared to a typical station. This is clearly illogical. Therefore, it is necessary to study how to ensure that EPCS stations and EPCS non-AP MLDs have higher channel access priority than typical stations in all scenarios.

[0134] The communication solution provided in this application is primarily applicable to multilink communication scenarios. Figures 1A, 1B, and 1C are schematic diagrams of multilink communication scenarios according to embodiments of this application, respectively.

[0135] Referring to the attached drawings, the following describes a communication solution provided in this application that ensures EPCS stations and EPCS non-AP MLDs have a higher channel access priority than typical stations in all scenarios.

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

[0137] 801: The first station sends a request frame to the 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 channel priority access. Alternatively, the request frame is used to request 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 channel conflict 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 any other frame. The specific name of the request frame is not limited in this application.

[0140] The request frame carries a first parameter set, which includes MU EDCA parameters intended for use by the first station to perform channel contention. For example, the first parameter set includes MU EDCA parameters intended for use by the first station to perform channel contention after it has successfully transmitted a data frame triggered based on an 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 a typical station. How the request frame carries the first parameter set is described below with reference to the frame body of the request frame.

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

[0142] It should be noted in this application that there are two or more MU EDCA parameter sets. One MU EDCA parameter set is used by a general station after it has successfully transmitted 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 has successfully transmitted 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 a received trigger frame, the first station performs channel access by using parameters in the first parameter set, where the first parameter set 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 possible implementations, the request frame further carries a second parameter set. The second parameter set includes MU EDCA parameters intended for use by a second station to perform channel conflict. The second station and the first station belong to the same multilink station device. In possible implementations, the second parameter set is included in the link information field within the MLE in 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 further 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 conflict. For example, the request frame further carries MU EDCA parameters intended for use by station 1 to perform channel conflict and MU EDCA parameters intended for use by station 2 to perform channel conflict, and stations 1, 2, and the first station all belong to the same multilink station device.

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

[0145] In a possible implementation, the response frame carries a third parameter set. This third parameter set contains the MU EDCA parameters to be used by the first station to perform channel contention. The third parameter set 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 that the first station will perform channel conflict by using parameters in the first parameter set, the access point may send a response frame to the first station carrying a third parameter set. The third parameter set contains the MU EDCA parameters to be used by the first station to perform channel conflict. The third parameter set is different from the first parameter set. In this implementation, the response frame carries the third parameter set, thereby allowing the first station to perform channel conflict by using parameters in the third parameter set to secure channel access priority. How the response frame carries the third parameter set is described below with reference to the frame body of the response frame. It should be understood that if the access point agrees that the first station will perform channel conflict by using parameters in the first parameter set, the response frame sent by the access point to the first station may carry the third parameter set. In possible implementations, the third parameter set may include the first parameter set, be equal to the first parameter set, or the first parameter set may be a subset of the third parameter set. If the access point agrees that the first station will perform a channel conflict by using the 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 is sent to the first station that does not carry any parameter set for the first station. This indicates that the first station is, by default, allowed to perform a subsequent channel conflict by using the first parameter set carried in the first station's request frame.In this implementation, if the response frame does not carry a third set of parameters, this indicates that the access point has agreed to reduce the amount of data in the response frame by having the first station perform channel contention by using parameters from the first set of parameters.

[0147] In possible implementations, 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 conflict. 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 conflict. The fourth parameter set is either the same as or different from the second parameter set. If the access point agrees that the second station will perform channel conflict by using the parameters in the second parameter set, it should be understood that the response frame sent by the access point to the first station may carry the fourth parameter set. In possible implementations, the fourth parameter set includes the second parameter set, is equal to the second parameter set, or the second parameter set is a subset of the fourth parameter set. If the access point agrees that the second station will perform a channel conflict by using the 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 for the first station. In other words, a response frame is sent to the second station that does not carry any parameter sets for the second station. This indicates that the second station is allowed by default to perform a subsequent channel conflict by using the second parameter set carried in the first station's request frame. How the response frame carries the fourth parameter set is described below with reference to the frame body of the response frame.

[0148] In some possible implementations, the request frame sent by the first station does not have to carry the MU EDCA parameters that the first station intends to use to perform channel conflict. In other words, the first station may carry only the set of MU EDCA parameters that one or more stations belonging to the same multilink station device as the first station intend to use to perform channel conflict. The response frame sent by the access point on behalf of the first station may carry only the set of MU EDCA parameters that one or more stations belonging to the same multilink station device as the first station are permitted to use to perform channel conflict.

[0149] The steps of the method in Figure 8 may be replaced as follows: The first station sends a request frame to the access point. The request frame carries a second parameter set. The second parameter set includes MU EDCA parameters intended for use by the second station to perform channel conflict. 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 permits the second station to use to perform channel conflict. 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 that the second station will perform channel conflict by using the 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 possible implementations, the fourth parameter set either includes the second parameter set, is equal to the second parameter set, or the second parameter set is a subset of the fourth parameter set. If the access point agrees that the second station will perform a channel conflict by using the 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 is sent that does not carry any parameter set. This indicates that the second station is permitted by default to perform a subsequent channel conflict by using the second parameter set carried in the first station's request frame. How the request frame carries the second parameter set is described below with reference to the frame body of the request frame.

[0150] In this embodiment of the application, the request frame carries a first parameter set, which includes MU EDCA parameters intended for use by a first station to perform channel competition, by using parameters having higher channel priority.

[0151] The frame body of the request frame will be described below with reference to the attached drawings or tables, and with reference to the frame body of the request frame, how the request frame carries the first parameter set and how the request frame carries the second parameter set will be further explained.

[0152] Request frame body 1:

[0153] Table 1 shows an example of the fields included in frame body 1 of a request frame. Referring to Table 1, the first parameter set is contained 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 illustrative purposes and is not limited to this embodiment of the present invention.

[0155] The category field indicates the type of action frame. The value of the category field may also be a protected EHT action, indicating that the action frame belongs to the "protected EHT action" category.

[0156] The protected EHT action field indicates a subcategory of the action frame. In a possible implementation, the value of the protected EHT action field is EPCS priority access enable request, indicating 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, indicating that the action frame is an NSEP priority access enable request frame.

[0157] The dialog token field is used to pair the request frame with the response frame.

[0158] The EDCA parameter set field indicates the EDCA parameter set intended for use by the first station.

[0159] The MU EDCA parameter set field indicates the MU EDCA parameter set that the first STA is intended to use, i.e., the first parameter set.

[0160] The priority access multi-link element field is used to carry EDCA parameter sets and MU EDCA parameter sets intended for use by one or more stations belonging to the same multi-link station device as the first station. For example, the priority access multi-link element field is used to carry EDCA parameter sets and MU EDCA parameter sets intended for use by a second station, and the second station and the first station belong to the same multi-link 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 sets and MU EDCA parameter sets intended for use by the second station. This is not limited to this application. The priority access multi-link element field may also be replaced by a link ID bitmap field plus a list of parameter set fields. The parameter set fields include EDCA parameter sets and / or MU EDCA parameter sets. The link ID bitmap field is a bitmap of link identifiers. Each bit in the bitmap indicates whether the subsequent parameter set field list contains the 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 subsequent parameter set field list contains the parameter set for the link with link ID (i-1). The value of i is in the range of 1 to 16, and the value of the link ID is in the range of 0 to 15.

[0161] The priority access multi-link element field is optional, not mandatory. When the first station is an independent station, it can be understood that the request frame transmitted by the first station does not need to carry the EDCA parameter set and 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 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 it may not carry the EDCA parameter set and 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 MLE format in Figure 6 is the different information contained 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 in the priority access multi-link element field may include the EDCA parameter set and MU EDCA parameter set. As shown in Figure 9A, the STA control field contains the link identifier (link ID).

[0162] In possible implementations, the priority access multi-link element field contains 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 contains 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 Figure 9A, the priority access multi-link element field contains 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, ..., and per-STA profile x corresponds to station x. per-STA profile 1 contains an EDCA parameter set and an MU EDCA parameter set intended for use by station 1. per-STA profile 2 contains 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 intended for use by station x, where x is an integer greater than 1. Stations 1, 2, ..., and x all belong to the same multilink station device as the first station. For example, the STA profile field in each per-STA profile within the priority access multi-link element field includes the EDCA parameter set and MU EDCA parameter set intended for use by the station corresponding to that 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 profile field in per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set intended for use by station 1. The STA profile field in per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set intended for use by station 2. In this example, stations 1 and 2 belong to the same multilink station device. In a possible implementation, the STA control field in per-STA profile includes the 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 contains the link ID corresponding to station 2. The link ID corresponding to a station is the ID of the link that the station uses to access the access point. The link identifier in the STA control field indicates a link or a station. The access point may determine the station corresponding to the per-STA profile based on the link ID contained in the STA control field in the per-STA profile.The EDCA parameter set and MU EDCA parameter set in the STA profile field within the per-STA profile are the EDCA parameter set and MU EDCA parameter set intended for use by the station.

[0163] Request frame body 2:

[0164] Table 2 shows an example of fields included in the frame body 2 of the request frame. Referring to Table 2, the first parameter set is contained 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 contained 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 contained in the MLE in the request frame. The order in Table 2 is merely an example for illustrative purposes. This is not limited to this embodiment of the invention. The meaning of the fields in Table 2 is described when Table 1 was explained. Therefore, further details will not be explained again here. [Table 2]

[0165] In possible implementations, the first parameter set is contained in the link info field within the priority access multi-link element field. Figure 9B shows an example of another format of the priority access multi-link element field according to embodiments of this application. For the meaning of the fields in Figure 9B, see the field descriptions in Figure 6. Figure 9B shows the priority access multi-link element field in a request frame, where 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 multi-link station device as the first station.

[0166] In possible implementations, the priority access multi-link element field includes a per-STA profile corresponding to a first station, and the per-STA profile includes an EDCA parameter set and an MU EDCA parameter set intended for use by the first station. For example, the STA profile field within the per-STA profile in 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 possible implementations, the STA control field within the per-STA profile includes a link ID corresponding to a first station, and the first station corresponds to the per-STA profile. As shown in Figure 9B, the link information field includes a per-STA profile, and the per-STA profile corresponds to a first station. The per-STA profile includes an 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 contained in the STA control field within the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field within the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the station is intended to use.

[0167] In possible implementations, the priority access multi-link element field includes multiple per-STA profiles. One of the multiple per-STA profiles corresponds to a 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. Figure 9C shows an example of another format of the priority access multi-link element field according to embodiments of this application. As shown in Figure 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, ..., and 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 includes the EDCA parameter set and MU EDCA parameter set intended for use by station 2. By analogy, per-STA profile m includes 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 within 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. 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 multi-link station device. In a possible implementation, the STA control field in per-STA profile contains the 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 the first station. per-STA profile 2 corresponds to station 2. The STA control field in per-STA profile 1 contains the link ID corresponding to the first station. 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 that the station uses to access the access point.The link identifier in the STA control field included in the per-STA profile indicates a station or link. The STA profile in the per-STA profile includes the EDCA parameter set and MU EDCA parameter set intended for use by 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 intended for use by the station.

[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 contains 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 contains the EDCA parameter set and 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 MU EDCA parameter set intended for use by the first station.

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

[0170] Response frame body 1:

[0171] Table 3 shows an example of the fields included in frame body 1 of the response frame. Referring to Table 3, the third parameter set is contained 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 illustrative purposes and is not limited to 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 EPCS was successfully established or not.

[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, i.e., the third parameter set, that the access point permits the first station to use. It should be understood that if the access point permits the first station to use the EDCA parameter set or MU EDCA parameter set in the request frame, the EDCA parameter set or 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 EDCA parameter sets and MU EDCA parameter sets that the access point permits one or more stations belonging to the same multi-link station device as the first station to use. For example, the priority access multi-link element field is used to carry EDCA parameter sets and MU EDCA parameter sets (i.e., a fourth parameter set) that the access point permits a second station to use, and the second and first stations belong to the same multi-link 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 sets and MU EDCA parameter sets that the access point permits a second station to use. This is not limited to this application. The priority access multi-link element field is optional, not required. If the access point permits the second station to use the EDCA parameter set or MU EDCA parameter set in the request frame, it should be understood that the EDCA parameter set or MU EDCA parameter set permitted for use by the second station 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 possible implementations, the priority access multi-link element field contains 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 contains an EDCA parameter set and an MU EDCA parameter set that the access point permits the station corresponding to the per-STA profile to use. Any two per-STA profiles correspond to different stations. As shown in Figure 9A, the priority access multi-link element field contains 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, ..., and per-STA profile x corresponds to station x. per-STA profile 1 contains an EDCA parameter set and an MU EDCA parameter set that the access point permits station 1 to use. per-STA profile 2 contains an EDCA parameter set and an MU EDCA parameter set that the access point permits 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. Stations 1, 2, ..., and x all belong to the same multilink station device as the first station.For example, the STA profile field in each per-STA profile within the priority access multi-link element field contains the EDCA parameter set and MU EDCA parameter set that the access point permits 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 permits 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 permits station 2 to use. In this example, stations 1 and 2 belong to the same multilink station device. In a possible implementation, the STA control field in per-STA profile contains the 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 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 identifier in the STA control field included in the per-STA profile indicates a station. The STA profile in the per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the access point permits 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 permits the station to use.

[0179] Response frame body 2:

[0180] Table 4 shows an example of fields included in the frame body 2 of the 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 frame. The order in Table 4 is merely an example for illustrative purposes. This is not limited to this embodiment of the invention. The meaning of the fields in Table 4 is described when Table 3 was explained. Therefore, further details will not be explained again here. [Table 4]

[0181] In possible implementations, the third parameter set is contained in the link info field within 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, MU EDCA parameter set represents the third parameter set, which is contained in the STA profile field, which is contained in the per-STA profile, which is contained in the link info field.

[0182] In possible implementations, the priority access multi-link element field includes a per-STA profile corresponding to a first station, and the per-STA profile includes an EDCA parameter set and an MU EDCA parameter set (i.e., a third parameter set) that the access point permits the first station to use. For example, the STA profile field within the per-STA profile in the priority access multi-link element field includes an EDCA parameter set and an MU EDCA parameter set that the access point permits the first station to use, corresponding to the per-STA profile. In possible implementations, the STA control field within the per-STA profile includes a link ID corresponding to a first station, and the first station corresponds to the per-STA profile. As shown in Figure 9B, the link information field includes a per-STA profile, and the per-STA profile corresponds to a first station. The per-STA profile includes an 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. 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 permits the first station to use, based on the STA control field and STA profile field in the priority access multi-link element field.

[0183] In possible implementations, the priority access multi-link element field contains multiple per-STA profiles. One of the per-STA profiles corresponds to the first station. Another of the per-STA profiles corresponds to a station belonging to the same multi-link station device as the first station. Each per-STA profile contains 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 Figure 9C may be considered as the priority access multi-link element field in the response frame. As shown in Figure 9C, the priority access multi-link element field contains 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, ..., and 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 permits the first station to use. per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set that the access point permits the second station to use. By analogy, per-STA profile m includes the EDCA parameter set and MU EDCA parameter set that the access point permits the second station to use, 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 within the priority access multi-link element field contains the EDCA parameter set and MU EDCA parameter set that the access point permits 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 permits 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 permits the station 2 to use. In this example, station 2 and the first station belong to the same multilink station device. In possible implementations, the STA control field within a per-STA profile contains a link ID corresponding to one station, and each station corresponds to a 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. per-STA profile 2 corresponds to station 2. The STA control field within per-STA profile 1 contains a link ID corresponding to the first station.The STA control field in per-STA profile 2 contains the link ID corresponding to station 2. The first station may determine the station corresponding to the per-STA profile based on the link ID contained 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 to perform channel contention by one or more stations belonging to the same multilink station device as the first station, 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 contains 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 contains the EDCA parameter set and MU EDCA parameter set that the access point permits 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 MU EDCA parameter set that the access point permits the first station to use.

[0185] Figure 10 is a flowchart of another communication method according to an embodiment of this application. The steps of the method 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: The first station sends a request frame to the access point.

[0187] Before sending the request frame to the access point, the first station may generate the request frame. See step 801 for step 1001. The request frame carries the 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 a typical station.

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

[0189] Table 5 shows examples of fields in a response frame sent by an access point to the first station. For the meaning of the fields in Table 5, refer to the meaning of the fields in Table 3. [Table 5]

[0190] 1003: After sending 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.

[0191] A possible implementation of step 1003 is as follows: After transmitting a data frame triggered based on the access point's trigger frame, the first station performs channel contention within 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 also be obtained based on the 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, parameters in the first parameter set indicate the first duration, and the first station determines the first duration based on parameters in the first parameter set that indicate the first duration.

[0192] In this embodiment of the application, after transmitting a data frame triggered based on an access point trigger frame, the first station performs channel contention by using parameters in a first parameter set. Compared to a typical station, the first station may have a higher channel access priority.

[0193] Figure 11 is a flowchart of another communication method according to an embodiment of this application. The steps of the method 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: The first station sends a request frame to the access point.

[0195] For step 1001, refer to step 801. The request frame carries the first set of parameters.

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

[0197] The response frame carries a third parameter set, which includes the 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.

[0198] 1103: After sending a data frame triggered based on the access point's trigger frame, 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 access point's trigger frame, the first station performs channel contention within 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, parameters in the third parameter set indicate the third duration, and the first station determines the third duration based on parameters in the third parameter set that indicate the third duration.

[0200] The first parameter set is determined by the first station from the perspective of the first station. Access points and other stations are not considered. The third parameter set is determined by the access point from an overall perspective. Multiple stations are comprehensively considered. In this embodiment of the application, after transmitting a data frame triggered based on an access point's trigger frame, 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 its 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 possible implementations of the method in Figure 8. As shown in Figure 12, the method includes the following steps:

[0202] 1201: The first station sends a request frame to the 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 sending 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, which includes MU EDCA parameters intended for use by the second station to perform channel contention. In this implementation, the second station may actively send the first parameter information, including the second parameter set, to the first station.

[0205] In a possible implementation, before sending a request frame to the access point, the first station performs the following actions: sending a parameter set query message to the second station and receiving second parameter information sent by the second station in response to the parameter set query message, the second parameter information containing a second parameter set. The parameter set query message is used to obtain the MU EDCA parameter set that the second station intends to use to perform channel conflict. In this implementation, the first station obtains the MU EDCA parameter set that the second station intends to use to perform channel conflict using an active query method.

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

[0207] In possible implementations, the response frame carries a third and a fourth parameter set. The third parameter set includes MU EDCA parameters that the access point permits the first station to use to perform channel contention. The fourth parameter set includes MU EDCA parameters that the access point permits 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. With respect to the parameter sets that each station intends to use and which are carried in the request frame, if the access point agrees that a station (any station) intends to 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. If the access point does not agree that a station intends to use the parameter set that the station intends to use, the response frame carries the parameter set that the access point permits the station to use. For example, the access point agrees that the first station will cause channel conflict by using parameters from the first parameter set, and the response frame may or may not carry the first parameter set. In another example, the access point does not agree that the first station will cause channel conflict by using parameters from the first parameter set, and the response frame carries a third parameter set that the access point permits the first station to use, and the third parameter set is different from the first parameter set. In yet another example, the access point does not agree that the second station will cause channel conflict by using parameters from the second parameter set, and the response frame carries a fourth parameter set that the access point permits the second station to use, and the fourth parameter set is 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. The fourth parameter set is the MU EDCA parameter set that the access point allows the second station to use.

[0210] 1204: After sending a data frame triggered based on the access point's trigger frame, 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. If the access point agrees that the first station will perform a channel conflict by using the parameters in the first parameter set, the response frame may or may not carry the third parameter set, and it should be understood that the third parameter set is the same as the first parameter set. If the access point does not agree that the first station will perform a channel conflict by using the parameters in the first parameter set, the response frame will carry the third parameter set, and it should be understood that 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 of step 1204 is as follows: After sending a data frame triggered based on the access point's trigger frame, the first station performs channel contention within a third duration by using parameters in a third parameter set. The third duration is obtained based on parameters in the third parameter set.

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

[0214] The fourth parameter set may or may not be the same as the second parameter set. If the access point agrees that the second station will perform a channel conflict by using parameters from the second parameter set, the response frame may or may not carry the fourth parameter set, and it should be understood that the fourth parameter set is the same as the second parameter set. If the access point does not agree that the second station will perform a channel conflict by using parameters from the second parameter set, the response frame will carry the fourth parameter set, and it should be understood that the fourth parameter set is different from the second parameter set.

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

[0216] In a possible implementation, the response frame carries a third parameter set but not a fourth parameter set, the third parameter set containing MU EDCA parameters that the access point permits the first station to use to perform channel conflict, the fourth parameter set containing MU EDCA parameters that the access point permits the second station to use to perform channel conflict, 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 decides that the access point permits the second station to perform channel conflict by using the second parameters. Step 1205 may be replaced as follows: After sending a data frame triggered based on the access point's trigger frame, the second station performs channel conflict by using the parameters in the second parameter set. The response frame carrying the third parameter set but not the fourth parameter set may also mean that the response frame carries the third parameter set and the second parameter set, or 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, the fourth parameter set containing MU EDCA parameters that the access point allows the second station to use to perform channel contention, and the third parameter set containing MU EDCA parameters that the access point allows the first station to use to perform channel contention, the fourth parameter set being different from the second parameter set. Step 1204 may be replaced as follows: After sending a data frame triggered based on the access point's trigger frame, the first station performs channel contention by using the parameters in the first parameter set. The response frame carrying a fourth parameter set but not a third parameter set may also mean that the response frame carries a fourth parameter set and a first parameter set, or that the response frame carries a fourth parameter set but not a first parameter set.

[0218] In possible implementations, the response frame does not carry the fourth and third parameter sets, the fourth parameter set includes MU EDCA parameters that the access point permits the second station to use to perform channel conflict, the third parameter set includes MU EDCA parameters that the access point permits the first station to use to perform channel conflict, 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 from the first station, or the second station decides that the access point permits the second station to perform channel conflict by using the second parameters. Step 1204 may be replaced as follows: After sending a data frame triggered based on the access point's trigger frame, the first station performs channel conflict by using the parameters in the first parameter set. 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 not carrying the fourth and third parameter sets may also carry the first and second parameter sets, or it may carry no parameter sets at all.

[0219] In this embodiment of the application, the request frame carries a first parameter set and a second parameter set. Compared to the embodiment in Figure 11, in the embodiment in Figure 12, the request frame transmitted 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 transmitting a request frame. Thus, 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 steps of the method in Figure 13 and the steps of the methods in Figures 8, 10, 11, and 12 is that the request frame transmitted by the first station does not include the MU EDCA parameters intended for use by the first station. As shown in Figure 13, the method includes the following steps:

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

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

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

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

[0225] The response frame carries a third parameter set. This third parameter set contains the MU EDCA parameters that should 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 transmits a radio frame carrying a third set of parameters directly to the first station. In other words, steps 1301 and 1302 may be replaced as follows: The access point transmits a radio frame carrying a third set of parameters to the first station, and the radio frame may also be an EPCS priority access request frame. The radio frame may further carry a fourth set of parameters, the fourth set of parameters including 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 sending a data frame triggered based on the access point's trigger frame, 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 contains 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 Figure 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 sending 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 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 permits the first station to use. In this way, the amount of data carried in the request frame can be reduced.

[0231] In the procedure of the method shown in Figures 8, 10, 11, 12, and 13, the first station sends a request frame to obtain the MU EDCA parameter set to be used for channel conflict. Referring to the attached drawings, the solution by which the first station determines the MU EDCA parameter set to be used based on the EDCA parameter set carried in the beacon frame is described below.

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

[0233] 1401: The first station sends a request frame to the access point.

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

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

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

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

[0238] 1403: The first station determines the MU EDCA parameter set to be used by the first station based on the EDCA parameter set carried in the response frame and 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 the data frame triggered based on the access point's trigger frame has been successfully transmitted. In this implementation, after successfully transmitting the data frame triggered based on the access point's trigger frame, the first station performs channel contention using the determined MU EDCA parameter set, thereby allowing the first station to have a 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 the data frame triggered based on the access point's trigger frame has been successfully transmitted. The second duration is obtained based on the parameters in the MU EDCA parameter set.

[0240] In possible implementations, 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 and the MU EDCA parameter set in the beacon frame. 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 also be done as follows: The first station determines the MU EDCA parameter set to be used by the first station based on the EDCA parameter set and the MU EDCA timer in the MU EDCA parameter set in the beacon frame. 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 the duration for which channel contention will occur by using the EDCA parameter set as the MU EDCA parameter set, based on the MU EDCA timer in the MU EDCA parameter set. The first station using the EDCA parameter set in the beacon frame as the MU EDCA parameter set to be used by the first station may also include setting the values ​​of the ACI / AIFSN field and ECWmin / ECWmax field corresponding to each AC in the EDCA parameter set to the ACI / AIFSN field and ECWmin / ECWmax field corresponding to each AC in the MU EDCA parameter set.Determining the duration for which channel contention is performed by using an EDCA parameter set as a MU EDCA parameter set, based on the MU EDCA timer in the MU EDCA parameter set, may also be done by setting the value of the MU EDCA timer field corresponding to each AC in the MU EDCA parameter set to be used by the first station 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 by using the parameters in the EDCA parameter set in the beacon frame. The length of the period is carried 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 by using the parameters in the EDCA parameter set of the second station's link. The length of the period is carried in the MU EDCA parameter set of the second station's link.

[0241] Compared to the embodiments described in the steps of the method in Figures 8, 10, 11, 12, and 13, the embodiment described in the steps of the method in Figure 14 does not require either the request frame or the response frame to carry the MU EDCA parameter set, thereby reducing the amount of data transmitted. 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 the parameter with higher channel access priority.

[0242] The communication device provided in the embodiments of this application will be described below.

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

[0244] Figure 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 correspond to the functions or steps implemented by the communication device (e.g., the first station and access point) in the embodiment of the method described above. 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 (code or program) 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 instructions (code or program) and / or data from the storage unit to implement the corresponding method. The above units may be arranged independently, or they may be partially or fully integrated. For example, the transceiver module 1520 may include a transmit module and a receive module. The transmit module may be a transmitter, and the receive module may be a receiver. The entity corresponding to the transceiver module 1520 may be a transceiver.

[0245] In several possible implementations, the communication device 1500 can correspondingly implement the actions and functions of the first station in the embodiment of the method. For example, the communication device 1500 may be the first station, or it may be 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 the 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 technology described herein. The processing module 1510 is configured to perform all operations other than the transmission and reception operations, which are performed by the first station in the embodiments shown in Figures 10, 11, 12, 13, and 14, for example, 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 several possible implementations, the communication device 1500 can implement corresponding actions and functions of the access point in the embodiment of the method. 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 receive or transmit 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 technology described in this specification. The processing module 1510 is configured to perform all operations other than the transmission and reception operations performed by the access point in the embodiment shown in Figure 11, for example, step 1102 in the embodiment shown in Figure 11.

[0247] The above describes the first station and access point in the embodiments of this application. The following describes possible product forms of the first station and access point. It should be understood that any form of product having the functionality of the first station in Figure 15, and any form of product having the functionality of the access point in Figure 15, falls within the scope of protection of the embodiments of this application. The following description is merely an example, and it should be further understood that the product forms of the access point and first station in the embodiments of this application are not limited to these.

[0248] In possible implementations, in the communication device shown in Figure 15, the processing module 1510 may be one or more processors, 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 are integrated into a single component, for example, a transceiver. In this embodiment of the application, the processor and the transceiver may be coupled, etc. The connection method between the processor and the transceiver is not limited in this embodiment of the application.

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

[0250] As shown in Figure 16, the communication device 160 includes one or more processors 1620 and a transceiver 1610. The transceiver 1610 may implement the functions of a transceiver module 1520. The processor 1620 may implement the functions of a processing module 1510.

[0251] In each implementation of the communication device shown in Figure 16, the transceiver may include a receiver and a transmitter. The receiver is configured to perform a receiving function (or operation). The transmitter is configured to perform a transmitting function (or operation). The transceiver is configured to communicate with other devices / devices through 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 memories 1630 are coupled to the processor 1620. The coupling in this embodiment of the application may be an indirect coupling or communication connection between devices, units or modules of electrical, mechanical or other forms, used for information exchange between devices, units or modules. The processor 1620 may operate in cooperation with the memories 1630. The processor 1620 may execute program instructions stored in the memories 1630.

[0253] The specific connection medium between the transceiver 1610, the processor 1620, and the memory 1630 is not limited to 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 via a bus 1640 in Figure 16. In Figure 16, the bus is represented by the use of a thick line. The connection methods between other components are merely illustrative examples and do 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 Figure 16. However, this does not indicate that only one bus or only one type of bus exists.

[0254] In this embodiment of the 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 execute the methods, steps and logic block diagrams disclosed in 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 embodiments of this application may be performed directly by the hardware processor, or by a combination of hardware modules and software modules within the processor.

[0255] In this embodiment of this 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 ROM (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 can be read and / or written to by a computer (e.g., a communication device as shown in this application). However, it is not limited to such storage medium. Memory in this embodiment of this application may, alternatively, be a circuit or any other device that can implement a storage function and is configured to store program instructions and / or data.

[0256] The processor 1620 is primarily configured to process communication protocols and data, control the entire communication device, execute software programs, and process data from the software programs. The memory 1630 is primarily configured to store software programs and data. The transceiver 1610 may include a control circuit and an antenna. The control circuit is primarily configured to perform conversions between baseband signals and radio frequency signals and to process 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 the user and output data to the user.

[0257] After the communication device is powered on, the processor 1620 may read the software program in memory 1630, interpret and execute the instructions of the software program, and process the 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 transmits the radio frequency signal in the form of electromagnetic waves through the 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 into a baseband signal, and outputs the baseband signal to the processor 1620. The processor 1620 converts the baseband signal into data and processes the data.

[0258] In other implementations, the radio frequency circuit and antenna may be located independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna may be located remotely, independently of the communication equipment.

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

[0260] In other possible implementations, in the communication device shown in Figure 15, the processing module 1510 may be one or more logic circuits, and the transceiver module 1520 may be an input / output interface, also called a communication interface, interface circuit, interface, etc. Alternatively, the transceiver module 1520 may be a transmit unit and a receive unit. The transmit unit may be an output interface, and the receive unit may be an input interface. Alternatively, the transmit unit and the receive unit may be integrated into a single unit, for example, an input / output interface. As shown in Figure 17, the communication device shown in Figure 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, processing circuit, integrated circuit, system on chip (SoC) chip, etc., and the interface 1702 may be a communication interface, input / output interface, pin, etc. For example, Figure 17 shows an example where the above communication device is a chip. The chip includes a logic circuit 1701 and an interface 1702.

[0261] In this embodiment of the application, the logic circuits and interfaces may be further coupled to one another. The specific connection methods of the logic circuits and interfaces are not limited to this embodiment of the application.

[0262] For example, when the communication device is configured to perform the above-mentioned method, function, or step 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 a communication device is configured to perform a method, function, or step performed by an access point, interface 1702 is configured to receive a request frame, logic circuit 1701 is configured to generate a response frame based on the request frame, and interface 1702 is configured to output a response frame.

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

[0265] Embodiments of this application further provide a wireless communication system, which includes a first station and an access point. The first station and access point may be configured to perform the method in any one of the above embodiments (shown in Figures 8 and 10-14).

[0266] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer becomes capable of performing operations and / or processes performed by the first station in the manner provided in this application.

[0267] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer becomes capable of performing operations and / or processes performed by an access point in the manner provided in this application.

[0268] This application further provides a computer program product, which includes computer code or a computer program. When the computer code or computer program is executed on a computer, the operations and / or processes performed by the first station in the manner provided in this application are performed.

[0269] This application further provides a computer program product, which includes computer code or a computer program. When the computer code or computer program is executed on a computer, the operations and / or processes performed by the access point in the manner provided in this application are executed.

[0270] In some embodiments provided in this application, it should be understood that the disclosed systems, apparatus and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division. In actual implementations, 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 performed. Furthermore, the illustrated or discussed mutual coupling, direct coupling or communication connection may be an indirect coupling or communication connection through some interface, apparatus or unit, or it may be an electrical connection, a mechanical connection or other form of connection.

[0271] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, may be in one location, or may be distributed across multiple network elements. Some or all of the units may be selected in accordance with the actual requirements in order to achieve the technical effects of the solution 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 physically exist independently, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware, or may be implemented in the form of a software functional unit.

[0273] When the integrated unit is implemented 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 such understanding, the technical solution of this application is essentially, or the part that contributes 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 execute 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 that can store program codes, 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 manner of this application and is not intended to limit the protection scope of this application. Any modification or substitution that can be easily conceived by those skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, The steps include sending a request frame to an access point, the request frame being used to request preferential channel access rights, the request frame carrying a first set of parameters, the first set of parameters including multi-user (MU) extended distributed channel access (EDCA) parameters intended for use by a first station to perform channel contention, The steps include receiving a response frame for the aforementioned request frame, and A method that includes this.

2. The method according to claim 1, wherein the first parameter set is included in the link information field within the multilink element (MLE) in the request frame, or the first parameter set is included in the MU EDCA parameter set field in the request frame.

3. The method according to claim 1 or 2, wherein 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, and the second station and the first station belong to the same multilink station device.

4. The method according to claim 3, wherein the second set of parameters is included in the link information field in the MLE within the request frame.

5. The method according to any one of claims 1 to 4, wherein the response frame carries a third parameter set, the third parameter set comprising MU EDCA parameters to be used by the first station to perform channel competition, and the third parameter set is different from the first parameter set.

6. The method according to claim 5, wherein 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.

7. The response frame further carries a fourth set of parameters. The method according to claim 6, wherein the fourth parameter set includes MU EDCA parameters to be used by the second station to perform channel conflict, the second station and the first station belong to the same multilink station device, and the fourth parameter set is different from the second parameter set, the second parameter set includes the MU EDCA parameters intended to be used by the second station to perform channel conflict.

8. The method according to claim 7, wherein the fourth set of parameters is included in the link information field in the MLE within the response frame.

9. The method according to any one of claims 1 to 8, further comprising the step of performing channel contention by using the parameters in the first parameter set after a data frame triggered based on the trigger frame of the access point has been transmitted.

10. The step of performing channel competition by using the parameters in the first parameter set is: The method according to claim 9, comprising the step of performing channel competition within a first duration by using the parameters in the first parameter set, wherein the first duration is obtained based on the parameters in the first parameter set.

11. The method according to any one of claims 1 to 10, wherein the request frame is an Emergency Warning Communication Service (EPCS) priority access request frame, and the response frame is an EPCS priority access response frame.

12. A method of communication, The steps include sending a request frame to an access point, the request frame being used to request priority access to the channel, and The steps include: receiving a response frame for the request frame; and determining the 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. A method that includes this.

13. The method according to claim 12, wherein the MU EDCA parameter set to be used by the first station is used to perform channel contention after a data frame triggered based on the access point's trigger frame has been successfully transmitted.

14. The step of determining the MU EDCA parameter set to be used by the first station is: The method according to claim 12 or 13, further comprising 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.

15. 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 is: The method according to claim 14, comprising 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.

16. The method according to claim 13, wherein 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 has been successfully transmitted, the second duration being determined based on the parameters in the MU EDCA parameter set.

17. The method according to any one of claims 12 to 16, wherein the request frame is an EPCS priority access request frame and the response frame is an EPCS priority access response frame.

18. A method of communication, Steps include receiving a request frame from a first station, the request frame being used to request channel priority access rights, the request frame carrying a first parameter set, the first parameter set including MU EDCA parameters intended for use by the first station to perform channel contention, The steps include: transmitting a response frame to the request frame to the first station; A method that includes this.

19. The method according to claim 18, wherein the first parameter set is included in the link information field within the multilink element (MLE) in the request frame, or the first parameter set is included in the MU EDCA parameter set field in the request frame.

20. The method according to claim 18 or 19, wherein the request frame further carries a second parameter set, the second parameter set comprising MU EDCA parameters intended for use by the second station to perform channel contention, and the second station and the first station belong to the same multilink station device.

21. The method according to claim 20, wherein the second set of parameters is included in the link information field in the MLE within the request frame.

22. The method according to any one of claims 18 to 21, wherein the response frame carries a third parameter set, the third parameter set comprising MU EDCA parameters to be used by the first station to perform channel competition, and the third parameter set is different from the first parameter set.

23. The method according to claim 22, wherein 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.

24. The method according to claim 23, wherein the response frame further carries a fourth parameter set, the fourth parameter set comprising MU EDCA parameters to be used by the second station to perform channel competition, and the second station and the first station belong to the same multilink station device.

25. The method according to claim 24, wherein the fourth set of parameters is included in the link information field in the MLE within the response frame.

26. The method according to any one of claims 18 to 25, wherein the request frame is an EPCS priority access request frame and the response frame is an EPCS priority access response frame.

27. A communication device, A processing module configured to generate a request frame, the request frame being used to request channel priority access rights, the request frame carrying a first parameter set, the first parameter set including multi-user (MU) extended distributed channel access (EDCA) parameters intended for use by a first station to perform channel contention, and A transceiver module configured to transmit the aforementioned request frame to an access point Includes, The transceiver module is further configured to receive a response frame to the request frame, in a device.

28. A communication device, A transceiver module configured to send a request frame to an access point, the request frame being used to request priority access to the channel, and a transceiver module further configured to receive a response frame to the request frame, A processing module configured to determine the 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. A device that includes this.

29. A communication device, A transceiver module configured to receive a request frame from a first station, the request frame being used to request priority access to a channel, the request frame carrying a first parameter set, the first parameter set including MU EDCA parameters intended for use by the first station to perform channel contention, and the transceiver module A processing module configured to generate a response frame for the aforementioned request frame and Includes, The transceiver module is further configured to transmit the response frame to the request frame to the first station.

30. A computer-readable storage medium, A computer-readable storage medium that stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is able to perform the method according to any one of claims 1 to 26.

31. A communication device including a processor and memory, The memory is configured to store computer programs or instructions. The device wherein the processor is configured to execute the computer program or instructions in the memory to perform the method according to any one of claims 1 to 26.

32. The steps include generating a wireless frame that carries a third parameter set, the third parameter set including multi-user (MU) extended distributed channel access (EDCA) parameters to be used by a first station to perform channel contention, The steps include transmitting the wireless frame to the first station and A method that includes this.

33. The method according to claim 32, wherein the wireless frame is an Emergency Warning Communication Service (EPCS) priority access request frame.

34. The method according to claim 32 or 33, wherein the third set of parameters is included in the Preferred Access Multilink Element (MLE) field.

35. The method according to claim 32 or 33, wherein the third parameter set is included in the link information field within the preferred access MLE field.

36. The method according to any one of claims 32 to 35, wherein the wireless frame is used to request the acquisition of channel priority access rights.

37. A method of communication, The steps include receiving a radio frame from an access point that carries a third parameter set, the third parameter set including multi-user (MU) extended distributed channel access (EDCA) parameters to be used by a first station to perform channel competition, The steps include: after a data frame triggered based on the trigger frame of the access point has been transmitted, channel contention is performed by using the parameters in the third parameter set; A method that includes this.

38. The method according to claim 37, wherein the wireless frame is an Emergency Warning Communication Service (EPCS) priority access request frame.

39. The method according to claim 37 or 38, wherein the third set of parameters is included in the Preferred Access Multilink Element (MLE) field.

40. The method according to claim 37 or 38, wherein the third parameter set is included in the link information field within the preferred access MLE field.

41. The method according to any one of claims 37 to 40, wherein the wireless frame is used to request the acquisition of channel priority access rights.

42. A method of communication, The steps include receiving a request frame from the first station, The steps include sending a response frame to the first station for the request frame, wherein the response frame carries a third parameter set, the third parameter set including multi-user (MU) extended distributed channel access (EDCA) parameters to be used by the first station to perform channel contention, and A method that includes this.

43. The method according to claim 42, wherein the response frame further carries a fourth parameter set, the fourth parameter set comprising MU EDCA parameters to be used by a second station to perform channel competition, and the second station and the first station belong to the same multilink station device.

44. The method according to claim 42 or 43, wherein the third set of parameters is included in the Preferred Access Multilink Element (MLE) field.

45. The method according to claim 42 or 43, wherein the third parameter set is included in the link information field within the preferred access MLE field.

46. A method of communication The steps include sending the request frame to the access point, The steps include receiving a response frame transmitted by the access point in response to the request frame, wherein the response frame carries a third parameter set, the third parameter set including multi-user (MU) extended distributed channel access (EDCA) parameters to be used by the first station to perform channel contention, and A method that includes this.

47. The method according to claim 46, wherein the response frame further carries a fourth parameter set, the fourth parameter set comprising MU EDCA parameters to be used by a second station to perform channel competition, and the second station and the first station belong to the same multilink station device.

48. The method according to claim 46 or 47, further comprising the step of performing channel contention by using the parameters in the third parameter set after a data frame triggered based on the trigger frame of the access point has been transmitted.

49. The method according to any one of claims 46 to 48, wherein the third parameter set is included in the preferred access multilink element (MLE) field.

50. The method according to any one of claims 46 to 48, wherein the third parameter set is included in the link information field within the preferred access MLE field.

51. A processing module configured to generate a wireless frame carrying a third parameter set, wherein the third parameter set includes multi-user (MU) extended distributed channel access (EDCA) parameters to be used by a first station to perform channel contention. A transceiver module configured to transmit the aforementioned wireless frame to the first station and A device that includes this.

52. The apparatus according to claim 51, wherein the wireless frame is an Emergency Warning Communication Service (EPCS) priority access request frame.

53. The apparatus according to claim 51 or 52, wherein the third parameter set is included in the preferred access multilink element (MLE) field.

54. The apparatus according to claim 51 or 52, wherein the third parameter set is included in the link information field within the preferred access MLE field.

55. The apparatus according to any one of claims 51 to 54, wherein the wireless frame is used to request the acquisition of channel priority access rights.

56. A communication device, A transceiver module configured to receive radio frames carrying a third parameter set from an access point, wherein the third parameter set includes multi-user (MU) extended distributed channel access (EDCA) parameters to be used by a first station to perform channel contention. A processing module configured to perform channel contention by using the parameters in the third parameter set after a data frame triggered based on the access point's trigger frame has been transmitted. A device that includes this.

57. The apparatus according to claim 56, wherein the wireless frame is an Emergency Warning Communication Service (EPCS) priority access request frame.

58. The apparatus according to claim 56 or 57, wherein the third parameter set is included in the preferred access multilink element (MLE) field.

59. The apparatus according to claim 56 or 57, wherein the third parameter set is included in the link information field within the preferred access MLE field.

60. The apparatus according to any one of claims 56 to 59, wherein the wireless frame is used to request the acquisition of channel priority access rights.

61. A communication device, A transceiver module configured to receive request frames from a first station, A processing module configured to generate a response frame for the aforementioned request frame and Includes, 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) extended distributed channel access (EDCA) parameters to be used by the first station to perform channel contention.

62. The apparatus according to claim 61, wherein the response frame further carries a fourth parameter set, the fourth parameter set comprising MU EDCA parameters to be used by a second station to perform channel competition, and the second station and the first station belong to the same multilink station device.

63. The apparatus according to claim 61 or 62, wherein the third parameter set is included in the preferred access multilink element (MLE) field.

64. The apparatus according to claim 61 or 62, wherein the third parameter set is included in the link information field within the preferred access MLE field.

65. 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 to receive a response frame transmitted by the access point in response to the request frame, wherein the response frame carries a third parameter set, the third parameter set including multi-user (MU) extended distributed channel access (EDCA) parameters to be used by a first station to perform channel contention. A device that includes this.

66. The apparatus according to claim 65, wherein the response frame further carries a fourth parameter set, the fourth parameter set comprising MU EDCA parameters to be used by a second station to perform channel competition, and the second station and the first station belong to the same multilink station device.

67. The apparatus according to claim 65 or 66, 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 the trigger frame of the access point has been transmitted.

68. The apparatus according to any one of claims 66 to 67, wherein the third parameter set is included in the preferred access multilink element (MLE) field.

69. The apparatus according to any one of claims 65 to 67, wherein the third parameter set is included in the link information field within the preferred access MLE field.

70. A computer-readable storage medium, A computer-readable storage medium that stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is able to perform the method according to any one of claims 32 to 50.

71. A communication device including a processor and memory, The memory is configured to store computer programs or instructions. The device wherein the processor is configured to execute the computer program or instructions in the memory to perform the method according to any one of claims 32 to 50.

72. A computer program product, The computer program product includes a computer program, the computer program includes program instructions, and when the program instructions are executed, the computer becomes capable of performing the method according to any one of claims 32 to 50.

73. It is a communication system, The communication system comprises a communication device according to any one of claims 51 to 55 and a communication device according to any one of claims 56 to 60, or the communication system comprises a communication device according to any one of claims 61 to 64 and a communication device according to any one of claims 65 to 69.

Images