A communication method and a communication apparatus

Abstract

The embodiment of the present application discloses a communication method for optimizing channel access parameters, which comprises: a first station sending a request frame to an access point; the request frame is used for requesting to obtain channel priority access right; the request frame carries a first parameter set; the first parameter set comprises MU EDCA parameters to be used by the first station for channel competition; and a response frame for the request frame is received. The first station is an EPCS station, and the first station uses a MU EDCA mechanism for channel access. In the embodiment of the present application, the first parameter set comprises the MU EDCA parameters to be used by the first station for channel competition, and the request frame carrying the first parameter set is sent, so that channel competition is performed by using parameters with higher channel access priority.

Description

[0001] This application is a divisional application. The original application has the application number 202210200091.8 and the original application date is March 1, 2022. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and a communication device. Background Technology

[0003] Emergency preparedness communications service (EPCS) refers to services with extremely high latency requirements, such as communication services during crisis scenarios like fires and earthquakes. For EPCS, the 802.11be wireless LAN standard defines a priority access mechanism to ensure that EPCS sites can access the channel as quickly as possible, guaranteeing priority transmission of emergency services. EPCS sites are those that require EPCS. Therefore, it is necessary to research solutions that enable EPCS sites to access the channel as quickly as possible in various scenarios. Summary of the Invention

[0004] This application discloses a communication method and a communication device.

[0005] In a first aspect, embodiments of this application provide a communication method, the method comprising: sending a request frame to an access point; 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 multi-user MU enhanced distributed channel access (EDCA) parameters to be used by a first site in channel contention; and receiving a response frame in response to the request frame. In the first aspect and its possible implementations, the executing entity is the first site.

[0006] In this embodiment of the application, the first parameter set includes the MU EDCA parameters that the first station intends to use for channel contention. By sending a request frame carrying the first parameter set, channel contention can be carried out using parameters with higher channel access priority.

[0007] In one possible implementation, the method further includes: after sending a data frame triggered by a trigger frame based on the access point, using parameters from the first parameter set to perform channel contention.

[0008] In this implementation, after sending a data frame triggered by the access point trigger frame, channel contention is performed using parameters from the first parameter set; it has a higher channel access priority compared to ordinary sites.

[0009] In one possible implementation, the channel contention using parameters from the first parameter set includes: performing channel contention using parameters from the first parameter set for a first duration; the first duration is obtained from the parameters in the first parameter set.

[0010] In this implementation, the parameters in the first parameter set are used for channel contention during the first time period, which conforms to the MU EDCA mechanism and can maintain relative fairness between the first site and the traditional site (sites that do not meet the 802.11ax standard).

[0011] The communication method in the first aspect can be replaced by: a first station sending a request frame to an access point, the request frame carrying a second parameter set, the second parameter set including MU EDCA parameters that the second station intends to use for channel contention, the second station and the first station belonging to the same multi-link site device; the first station receiving a response frame from the access point in response to the request frame, the response frame carrying a fourth parameter set, the fourth parameter set including MU EDCA parameters that the access point allows the second station to use for channel contention, the fourth parameter set being the same as or different from the second parameter set.

[0012] In this embodiment of the application, the second parameter set includes the MU EDCA parameters that the second station intends to use for channel contention. By sending a request frame carrying the second parameter set, channel contention can be carried out using parameters with higher channel access priority.

[0013] Secondly, embodiments of this application provide a communication method, the method comprising: sending a request frame to an access point, the request frame being used to request priority access to a channel; and receiving a response frame in response to the request frame, the response frame carrying a third parameter set, the third parameter set including MU EDCA parameters used by a first site for channel contention. Alternatively, the third parameter set includes MU EDCA parameters used by the access point to allow the first site to engage in channel contention. In this second aspect and its possible implementations, the executing entity is the first site.

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

[0015] In one possible implementation, the method further includes: after sending a data frame triggered by a trigger frame based on the access point, using parameters from the third parameter set to compete for channel space.

[0016] In this implementation, after sending a data frame triggered by the access point trigger frame, channel contention is conducted using parameters from the third parameter set; this gives it a higher channel access priority compared to ordinary sites.

[0017] In one possible implementation, the channel contention using parameters from the third parameter set includes: performing channel contention using parameters from the third parameter set for a third duration; the third duration is obtained from the parameters in the third parameter set.

[0018] In this implementation, channel contention is carried out using parameters from the third parameter set during the third time period, which conforms to the MU EDCA mechanism and can maintain relative fairness between the first site and traditional sites (sites that do not meet the 802.11ax standard).

[0019] Thirdly, embodiments of this application provide another communication method, the method comprising: sending a request frame to an access point; the request frame being used to request priority access to the channel; receiving a response frame in response to the request frame; and determining, based on the response frame and the EDCA parameter set carried in the beacon frame, the MU EDCA parameter set adopted by the first station. In the third aspect and its possible implementations, the executing entity is the first station.

[0020] In this embodiment of the application, based on the response frame and the EDCA parameter set carried in the beacon frame, the MU EDCA parameter set adopted by the first site is determined; thus, a MU EDCA parameter set with higher channel access priority can be obtained.

[0021] In one possible implementation, the MU EDCA parameter set used by the first station is used to compete for channel contention after successfully transmitting a data frame triggered by the access point's trigger frame.

[0022] In this implementation, the MU EDCA parameter set used by the first station is used to compete for channel access after successfully sending a data frame triggered by the access point trigger frame, so as to ensure that the first station has a higher channel access priority.

[0023] In one possible implementation, determining the MU EDCA parameter set used by the first station further includes: determining the MU EDCA parameter set used by the first station based on the MU EDCA parameter set in the beacon frame.

[0024] This implementation method can solve the problem that the EDCA parameter set of MU with higher channel access priority cannot be accurately and quickly determined based solely on the EDCA parameter set carried in the beacon frame.

[0025] In one possible implementation, determining the MU EDCA parameter set used by the first station based on the MU EDCA parameter set in the beacon frame includes: determining the MU EDCA parameter set used by the first station based on the MU EDCA timer in the MU EDCA parameter set.

[0026] In this implementation, the problem of accurately and quickly determining the MU EDCA parameter set with higher channel access priority can be solved.

[0027] In one possible implementation, the MU EDCA parameter set used by the first station is used to conduct channel contention for a second duration after successfully transmitting a data frame triggered by the access point's trigger frame; the second duration is obtained from parameters in the MU EDCA parameter set.

[0028] In one possible implementation, the request frame is an EPCS priority access enable request frame, and the response frame is an EPCS priority access enable response frame.

[0029] In this implementation, the request frame is an Emergency Communication Service (EPCS) priority access enable request frame, and the response frame is an EPCS priority access enable response frame. Since both the request and response frames are existing frames, sending and receiving them does not require additional signaling.

[0030] Fourthly, embodiments of this application provide another communication method, the method comprising: receiving 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 that the first station intends to use in channel contention; and sending a response frame to the first station in response to the request frame. In this fourth aspect and its possible implementations, the executing entity is an access point.

[0031] In this embodiment of the application, the first parameter set includes the MU EDCA parameters that the first station intends to use in channel contention. The MU EDCA parameters that the first station intends to use in channel contention can be obtained by receiving a request frame carrying the first parameter set.

[0032] In one possible implementation of the first or fourth aspect, the first parameter set is included in the link information field of the multi-link element (MLE) in the request frame, or the first parameter set is included in the MU EDCA parameter set field in the request frame.

[0033] In this implementation, the first parameter set is included in the link information field of the Multi-Link Element (MLE) in the request frame, so as to independently indicate the MU EDCA parameter set to be used by the first site in channel contention. The first parameter set is included in the MU EDCA parameter set field in the request frame so that the access point can quickly obtain the first parameter set from the MU EDCA parameter set field in the request frame.

[0034] In one possible implementation of the first or fourth aspect, the request frame also carries a second parameter set, which includes the MU EDCA parameters that the second site intends to use for channel contention, and the second site and the first site belong to the same multi-link site device.

[0035] In this implementation, the request frame also carries a second parameter set. The second station does not need to send a request frame itself to inform the access point of the second parameter set that the second station intends to use, which can reduce signaling overhead.

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

[0037] In this implementation, the second parameter set is included in the link information field of the MLE in the request frame, so as to independently indicate the MU EDCA parameters to be used by the second site for channel contention.

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

[0039] In this implementation, the response frame carries a third parameter set so that the first station can use the parameters in the third parameter set to compete for the channel, thus ensuring the priority of channel access.

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

[0041] In this implementation, the third parameter set is a subset of the first parameter set. The first parameter set is determined by the first site from its own perspective, without considering the access point and other sites. The third parameter set is determined by the access point from a holistic perspective, comprehensively considering multiple sites. The first site uses the parameters from the third parameter set for channel contention, which ensures the priority of channel access while minimizing the impact on other sites.

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

[0043] 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 using the parameters in the third parameter set to compete for the channel compared to using the parameters in the first parameter set.

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

[0045] In this implementation, the response frame carries a third parameter set so that the first station can use the parameters in the third parameter set to compete for the channel, thus ensuring the priority of channel access.

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

[0047] In this implementation, the third parameter set is included in the link information field of the MLE in the response frame, so as to independently indicate the MU EDCA parameters to be used by the first station in channel contention. The third parameter set is included in the MU EDCA parameter set field in the response frame so that the first station can quickly obtain the third parameter set from the MU EDCA parameter set field in the response frame.

[0048] In one possible implementation of the first or fourth aspect, the response frame further carries a fourth parameter set, which includes MU EDCA parameters to be used by the second site for channel contention, wherein the second site and the first site belong to the same multi-link site device.

[0049] In this implementation, the response frame also carries a fourth parameter set, so the access point does not need to send a separate response frame to the second station; this can reduce signaling overhead.

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

[0051] In this implementation, the fourth parameter set is a subset of the second parameter set. The second parameter set is determined by the second site from its own perspective, without considering the access point or other sites. The fourth parameter set is determined by the access point from a holistic perspective, comprehensively considering multiple sites. The second site uses the parameters from the fourth parameter set for channel contention, which ensures the priority of channel access while minimizing the impact on other sites.

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

[0053] 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 using the parameters in the fourth parameter set to compete for the channel compared to using the parameters in the second parameter set.

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

[0055] In this implementation, the response frame carries a fourth parameter set so that the second station can use the parameters in the fourth parameter set to compete for the channel, thus ensuring the priority of channel access.

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

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

[0058] In one possible implementation of the first or fourth aspect, the request frame is an Emergency Communication Service (EPCS) priority access enable request frame, and the response frame is an EPCS priority access enable response frame.

[0059] In this implementation, the request frame is an Emergency Communication Service (EPCS) priority access enable request frame, and the response frame is an EPCS priority access enable response frame. Since both the request and response frames are existing frames, sending and receiving them does not require additional signaling.

[0060] In one possible implementation of the first or fourth aspect, the channel access priority of the first parameter set is higher than the channel access priority of the MU EDCA parameter set used by ordinary sites, and the first site is an EPCS site. Ordinary sites are non-EPCS sites. In other words, ordinary sites are not EPCS sites.

[0061] The communication method in the fourth aspect can be replaced by: the access point receiving a request frame from a first site, the request frame carrying a second parameter set, the second parameter set including MU EDCA parameters that the second site intends to use for channel contention, the second site and the first site belonging to the same multi-link site device; the access point sending a response frame to the first site in response to the request frame, the response frame carrying a fourth parameter set, the fourth parameter set including MU EDCA parameters that the access point allows the second site to use for channel contention, the fourth parameter set being the same as or different from the second parameter set.

[0062] In this embodiment of the application, the fourth parameter set includes the MUEDCA parameter used by the access point to allow the second station to compete for the channel, so that the second station can compete for the channel by using parameters with higher channel access priority.

[0063] Fifthly, embodiments of this application provide another communication method, the method comprising: receiving a request frame from a first site, the request frame being used to request priority access to a channel; and sending a response frame to the first site in response to the request frame, the response frame carrying a third parameter set, the third parameter set including MU EDCA parameters used by the first site for channel contention. Alternatively, the third parameter set includes MU EDCA parameters used by the access point to allow the first site to engage in channel contention. In this fifth aspect and its possible implementations, the executing entity is the access point.

[0064] In this embodiment, the third parameter set includes the MU EDCA parameters used by the first station in channel contention. By sending a response frame carrying the third parameter set to the first station, the first station can use the third parameter set to obtain a higher channel access priority in channel contention.

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

[0066] In this implementation, the third parameter set is included in the link information field of the MLE in the response frame, so as to independently indicate the MU EDCA parameters to be used by the first station in channel contention. The third parameter set is included in the MU EDCA parameter set field in the response frame so that the first station can quickly obtain the third parameter set from the MU EDCA parameter set field in the response frame.

[0067] In one possible implementation of the second or fifth aspect, the response frame also carries a fourth parameter set, which includes MU EDCA parameters to be used by the second site for channel contention, wherein the second site and the first site belong to the same multi-link site device.

[0068] In this implementation, the response frame also carries a fourth parameter set, so the access point does not need to send a separate response frame to the second station; this can reduce signaling overhead.

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

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

[0071] In one possible implementation of the second or fifth aspect, the request frame is an Emergency Communication Service (EPCS) priority access enable request frame, and the response frame is an EPCS priority access enable response frame.

[0072] In this implementation, the request frame is an Emergency Communication Service (EPCS) priority access enable request frame, and the response frame is an EPCS priority access enable response frame. Since both the request and response frames are existing frames, sending and receiving them does not require additional signaling.

[0073] In one possible implementation of the second or fifth aspect, the channel access priority of the third parameter set is higher than the channel access priority of the MU EDCA parameter set used by ordinary sites, and the first site is an EPCS site.

[0074] Sixthly, embodiments of this application provide a communication device for performing the methods of the first aspect, the second aspect, the third aspect, or any possible implementation thereof. The communication device includes corresponding units for performing the methods of the first aspect, the second aspect, the third aspect, or any possible implementation thereof.

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

[0076] In a seventh aspect, embodiments of this application provide a communication apparatus for performing the methods of the fourth aspect, the fifth aspect, or any possible implementation thereof. The communication apparatus includes corresponding units for performing the methods of the fourth aspect, the fifth aspect, or any possible implementation thereof.

[0077] For example, the communication device may include a transceiver unit and a processing unit. The communication device may include an access point as described in the fourth or fifth aspect above, such as an AP MLD, or an AP, or a chip within the AP MLD, such as a WiFi chip.

[0078] Eighthly, embodiments of this application provide a communication device including a processor for executing the methods shown in the first, second, and third aspects or any possible implementation thereof.

[0079] In executing the above method, the processes of sending and receiving information can be understood as the process by which the processor outputs the aforementioned information, and the process by which the processor receives the input information. When outputting the aforementioned information, the processor sends it to the transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after receiving the information, the transceiver may require further processing before inputting it to the processor.

[0080] Based on the above principles, for example, the request frame mentioned in the aforementioned method can be understood as the processor outputting the request frame. Similarly, the response frame can be understood as the processor receiving the input response frame.

[0081] Unless otherwise specified, or unless their actual function or internal logic in the relevant description is contradicted, the operations of a processor, such as transmitting, sending, and receiving, can be more generally understood as processor output and receiving, input, and other operations.

[0082] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0083] In one possible implementation, the memory is located outside the aforementioned communication device.

[0084] In one possible implementation, the memory is located within the aforementioned communication device.

[0085] In this embodiment of the application, the processor and memory can also be integrated into a single device, that is, the processor and memory can be integrated together.

[0086] In one possible implementation, the communication device further includes a transceiver for receiving and / or transmitting signals. For example, the transceiver may be used to transmit request frames. Alternatively, it may also be used to receive response frames, etc.

[0087] In this embodiment of the application, the communication device can be the first station in the first, second, or third aspects described above. For example, the first station can be a non-AP MLD or STA, etc.

[0088] Ninthly, embodiments of this application provide a communication device including a processor for executing a program stored in a memory, wherein when the program is executed, the communication device performs the methods shown in the fourth aspect, the fifth aspect, or any possible implementation thereof above.

[0089] In one possible implementation, the memory is located outside the aforementioned communication device.

[0090] In one possible implementation, the memory is located within the aforementioned communication device.

[0091] In the embodiments of this application, the processor and memory can also be integrated into a single device, that is, the processor and memory can be integrated together.

[0092] In one possible implementation, the communication device further includes a transceiver for receiving and / or transmitting signals. For example, the transceiver may be used to receive request frames. Alternatively, it may be used to transmit response frames, etc.

[0093] In this embodiment of the application, the communication device can be an access point as described in the fourth or fifth aspect above. For example, the receiving point can be an AP MLD or AP, etc.

[0094] In a tenth aspect, embodiments of this application provide a communication device, which includes a processing circuit and an interface circuit. The interface circuit is used to acquire data or output data. The processing circuit is used to execute a corresponding method as shown in the first aspect or any possible implementation of the first aspect above, or the processing circuit is used to execute a corresponding method as shown in the second aspect or any possible implementation of the second aspect above, or the processing circuit is used to execute a corresponding method as shown in the third aspect or any possible implementation of the third aspect above.

[0095] Eleventhly, embodiments of this application provide a communication device, which includes a processing circuit and an interface circuit. The interface circuit is used to acquire data or output data. The processing circuit is used to execute the corresponding method as shown in the fourth aspect or any possible implementation of the fourth aspect above, or the processing circuit is used to execute the corresponding method as shown in the fifth aspect or any possible implementation of the fifth aspect above.

[0096] In a twelfth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods shown in the first, second, third, or any possible implementation thereof to be executed.

[0097] In a thirteenth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods shown in the fourth aspect, fifth aspect, or any possible implementation thereof to be executed.

[0098] In a fourteenth aspect, embodiments of this application provide a computer program product comprising a computer program or computer code that, when run on a computer, causes the methods shown in the first aspect, second aspect, third aspect, or any possible implementation thereof to be executed.

[0099] In a fifteenth aspect, embodiments of this application provide a computer program product comprising a computer program or computer code that, when run on a computer, causes the methods shown in the fourth aspect, the fifth aspect, or any possible implementation thereof to be executed.

[0100] In a sixteenth aspect, embodiments of this application provide a multi-link communication system, which includes a non-AP MLD and an AP MLD. Optionally, the non-AP MLD is used to perform the method shown in the first aspect or any possible implementation of the first aspect, and the AP MLD is used to perform the method shown in the fourth aspect or any possible implementation of the fourth aspect. Optionally, the non-AP MLD is used to perform the method shown in the second aspect or any possible implementation of the second aspect, and the AP MLD is used to perform the method shown in the fifth aspect or any possible implementation of the fifth aspect.

[0101] In a seventeenth aspect, embodiments of this application provide a multi-link communication system, which includes a STA and an AP MLD. Optionally, the STA is used to perform the method shown in the first aspect or any possible implementation thereof, and the AP MLD is used to perform the method shown in the fourth aspect or any possible implementation thereof. Optionally, the STA is used to perform the method shown in the second aspect or any possible implementation thereof, and the AP MLD is used to perform the method shown in the fifth aspect or any possible implementation thereof. The AP MLD can be replaced by an AP. Attached Figure Description

[0102] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0103] Figure 1A , Figure 1B as well as Figure 1C A schematic diagram illustrating a multi-link communication scenario provided in an embodiment of this application;

[0104] Figure 2 An example of a basic access procedure for the CSMA / CA mechanism is shown;

[0105] Figure 3 An example of a rollback process between multiple STAs under DCF is shown;

[0106] Figure 4 An example of exponentially growing CW is shown;

[0107] Figure 5 An example of an EDCA parameter set for services of different ACs provided in this application embodiment;

[0108] Figure 6 An example of a frame body for an MLE is shown;

[0109] Figure 7A schematic diagram illustrating the working principle of a MU EDCA mechanism provided in an embodiment of this application;

[0110] Figure 8 A flowchart of a communication method provided in an embodiment of this application;

[0111] Figure 9A , Figure 9B as well as Figure 9C An example of the format of the priority access multi-linkelement field provided in embodiments of this application;

[0112] Figure 10 A flowchart illustrating another communication method provided in this application embodiment;

[0113] Figure 11 A flowchart illustrating another communication method provided in this application embodiment;

[0114] Figure 12 A flowchart illustrating another communication method provided in this application embodiment;

[0115] Figure 13 A flowchart illustrating another communication method provided in this application embodiment;

[0116] Figure 14 A flowchart illustrating another communication method provided in this application embodiment;

[0117] Figures 15 to 17 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Detailed Implementation

[0118] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used only to distinguish different objects and not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0119] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0120] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to and includes any or all possible combinations of one or more of the listed items. For example, “A and / or B” can mean: only A exists, only B exists, and both A and B exist, where A and B can be singular or plural. The term “at least one” as used in this application means one or more, and “more” means two or more. “At least one of the following” or similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. a, b, and c can be a single or multiple.

[0121] The following section first introduces the terminology and technical features involved in the embodiments of this application.

[0122] multi-link communication

[0123] With the development of wireless technology, more and more wireless devices support multi-link communication. For example, some wireless devices can communicate simultaneously on the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, or simultaneously on different channels within the same frequency band, thus improving the communication speed between wireless devices. Such devices that support multi-link communication are usually called multi-link devices (MLDs).

[0124] A multi-link device includes one or more affiliated stations (STAs). The affiliated station is a logical station and can operate on a single link, frequency band, or channel. The affiliated station can be an access point (AP) or a non-access point station (non-AP STA). A multi-link device can be an access point device or a station device. For ease of description, this application may refer to a multi-link device whose affiliated station is an AP as a multi-link AP, a multi-link AP device, or an AP multi-link device (APMLD). A multi-link device whose affiliated station is a non-AP STA is referred to as a multi-link STA, a multi-link STA device, or a STA multi-link device (STA multi-link device), or a multi-link non-AP, a multi-link non-AP device, or a non-AP multi-link device (non-APMLD), etc. In the following text, multi-link devices belonging to AP sites are referred to as AP MLDs, and multi-link devices belonging to non-AP STA sites are referred to as non-AP MLDs. An AP MLD may belong to one or more APs; a STA MLD may belong to one or more STAs.

[0125] Site equipment can establish multiple links (or associate multiple links) with access point equipment before communicating. Figure 1A This is a schematic diagram illustrating a multi-link communication scenario provided in an embodiment of this application. Figure 1A As shown, a multi-link access point device includes n APs, such as AP1 to APn, and a multi-link site device includes n STAs, such as STA1 to STAn. One AP in the multi-link access point device is associated with one STA in the multi-link site device. For example, AP1 and STA1 are associated through link 1.

[0126] During the multi-link establishment (or multi-link association) process, one site in a multi-link site device can send an association request frame to one access point in a multi-link access point device. This association request frame carries a multi-link element (MLE) to convey information about the multi-link site device and other sites within the device. The multi-link element can also be called a multi-link information unit. Similarly, the association response frame sent by the access point to the site can also carry an MLE to convey information about the multi-link access point device and other access points within the device.

[0127] A multi-link device (which can be either a non-AP MLD or an AP MLD) is a communication device with wireless communication capabilities. This communication device can be a complete device or a chip or processing system installed within a complete device. Devices with these chips or processing systems can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the non-AP multi-link device in the embodiments of this application has wireless transceiver capabilities, supports the 802.11 series protocols, and can communicate with AP multi-link devices or other non-AP multi-link devices. For example, a non-AP multi-link device is any user communication device that allows users to communicate with an AP and thus with a WLAN. For example, a non-AP multi-link device can be a network-connected user device such as a tablet, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone, or an IoT node in the Internet of Things (IoT), or an in-vehicle communication device in the Internet of Vehicles (IoV). The non-AP multi-link device can also be the chip and processing system within these terminals. An AP multi-link device is a device that can provide services to non-AP multi-link devices and supports the 802.11 series of protocols. For example, an AP multi-link device can be a communication server, router, switch, bridge, or other communication entity; alternatively, it can include various forms of macro base stations, micro base stations, repeaters, etc. Furthermore, the AP multi-link device can also include the chips and processing systems within these various types of devices. The 802.11 protocol used can be one that supports or is compatible with 802.11be.

[0128] Understandably, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to even more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-checkout machines, self-ordering machines, etc.). The specific form of the multi-link device in this application embodiment is not limited; it is merely an illustrative example.

[0129] Figure 1BThis is a schematic diagram of another multi-link communication scenario provided in an embodiment of this application. For example... Figure 1B As shown, it includes at least one AP and at least one STA. Figure 1B The diagram shows three STAs, such as STA1, STA2, and STA3. For example, STA1 can communicate with the AP via two links, which can be as follows: Figure 1B The two arrows are shown. For example, STA2 or STA3 can communicate with the AP via a link. That is to say, Figure 1B The system shown includes both multi-link communication and single-link communication.

[0130] Figure 1C This is a schematic diagram of another multi-link communication scenario provided in an embodiment of this application. For example... Figure 1C As shown, it includes at least one AP and at least one STA. Figure 1C The diagram shows three STAs, such as STA1, STA2, and STA3. Figure 1C The diagram shows two access points, such as AP1 and AP2. For example, STA1 and STA3 can communicate with AP1 via different links, such as... Figure 1C The two arrows indicate that communication is possible between two STAs. For example, STA2 and STA3 can communicate via a link between them. Communication is also possible between different APs. For example, AP1 and AP2 can communicate via a link between them.

[0131] The method provided in this application can be applied to, but is not limited to, single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X can represent anything), and device-to-device (D2D). For example, the V2X can include: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communication, etc.

[0132] Distributed coordination function (DCF)

[0133] To ensure that access points (APs) and STAs can access the wireless medium without collisions, the 802.11 wireless LAN standard uses a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism. This CSMA / CA mechanism is also known as DCF. The basic idea of ​​CSMA / CA is as follows: When a STA intends to transmit data, it needs to perform a clear channel access (CCA) assessment of the wireless medium. If the medium state (i.e., the state of the wireless medium) is idle for a period of time (e.g., the DCF inter-frame space (DIFS)), the STA can begin a random backoff process. If the medium state is busy, the STA must wait for the medium state to become idle and maintain this state for a period of time (e.g., DIFS) before initiating the random backoff process. After the random backoff process is complete, the STA can transmit data. The random backoff time required by the STA is a random backoff value multiplied by the time of each time slot (e.g., 9µs). The random backoff value is randomly selected from a uniformly distributed window [0, CW]. The contention window (CW) has multiple values. It is initialized to its minimum value (CWmin) during the initial attempt. Each time a transmission fails (e.g., a collision occurs), a retransmission is required, and CW increases progressively until it reaches its maximum value (CWmax). When the STA successfully transmits data, CW is reset to CWmin. The size of each window can be a power of 2 minus 1, and is approximately twice the size of the previous window.

[0134] CSMA / CA is based on carrier sensing (CS). DCF uses both physical carrier sensing (PCS) and virtual carrier sensing (VCS) to determine the media status. PCS, located in the physical layer (PHY), uses energy detection (ED) and preamble detection (PD) to determine if the media is busy. VCS, located in the MAC layer, uses the duration field in the received radio frame to determine if the channel is idle. After receiving a radio frame, the STA sets the network allocation vector (NAV) based on the duration field. The NAV value indicates the length of time the station sending the radio frame needs to occupy the channel. The STA then starts a countdown; when the countdown reaches 0, the channel is considered idle. The channel is considered idle only if both PCS and VCS mechanisms deem it idle; otherwise, the channel is considered busy. Figure 2 An example of a basic access procedure using the CSMA / CA mechanism is shown. For example... Figure 2 As shown, after the channel changes from busy to idle, the station maintains this state for a period of time before initiating a random backoff process. This period can be any of the following: DIFS, PCF inter-frame space (PIFS), or short inter-frame space (SIFS); the station determines the random backoff time that needs to be backed up. Figure 2 The rollback window in the text corresponds to a random rollback time. Figure 3 An example of a rollback process between multiple STAs under DCF is shown. Figure 3 As shown, initially, STA A sends a data frame, while STA B, STA C, and STA D all delay sending their data frames. After STAA finishes sending its data frame (channel idle), STA B, STA C, and STA D begin a random backoff process. STA C completes the random backoff process first and then sends its data frame. After STAA finishes sending its data frame (channel idle), STA B, STA D, and STAA begin a random backoff process. STAA completes the random backoff process first and then sends its data frame, and so on.

[0135] The random backoff time required for STA is a random backoff value multiplied by the time of each time slot. This random backoff value is randomly selected from a uniformly distributed window [0, CW]. The contention window (CW) has multiple values. It is initialized to its minimum value (CWmin) during the initial attempt. Each time a transmission fails (e.g., a collision occurs), a retransmission is required, and CW increases progressively until it reaches its maximum value (CWmax). When data is successfully transmitted, CW is reset to CWmin. The size of each window is a factor of 2 minus 1, and approximately twice the size of the previous window; for simplicity, this is referred to as window doubling. Figure 4 An example of exponentially growing CW is shown. For example... Figure 4 As shown, the CW is 7 on the first attempt, 15 on the first retransmission, 31 on the second retransmission, 63 on the third retransmission, and so on.

[0136] Enhanced Distributed Channel Access (EDCA) Contention Transmission

[0137] EDCA is an enhancement of the DCF mechanism. It allows services of different access categories (ACs) to have different sets of EDCA parameters, including CWmin, CWmax, and arbitration interframe space (AIFS). Figure 5 This application provides an example of an EDCA parameter set for a service of a different AC. Figure 5 In this context, AIFSN represents the arbitration inter-frame spacing number, TXOP represents the transmit opportunity, TXOP limit represents the transmit opportunity limit, and AC_BK, AC_BE, AC_VI, and AC_VO represent different ACs.

[0138] For a specific AC service, the backoff process is basically the same as DCF, except that AIFS replaces DIFS in DCF. That is, when the channel returns to idle, the STA must wait for AIFS before initiating the backoff process. AIFS is calculated as AIFS[AC] = aSIFSTime + AIFSN[AC] * aSlotTime. For example, for a service with access level AC_BE, its EDCA parameter set is {CWmin = 31, CWmax = 1023, AIFSN = 3}. Therefore, during the EDCA backoff process, AIFS is aSIFSTime + 3 * aSlotTime. This means that when the channel returns to idle, the STA must wait for aSIFSTime + 3 * aSlotTime before initiating the backoff process. aSIFSTime represents the length of the time slot, typically 9µs. SIFSTime represents the length of SIFS, typically 16µs. Additionally, the initial value of the backoff counter should be randomly generated between [0, 31]. The AP sends the EDCA parameter set in the beacon frame. All STAs use the EDCA parameters sent by the AP in the Beacon frame to compete for the EDCA channel.

[0139] Multi-link element (MLE)

[0140] Multilink elements are used to carry information about multilink devices and the sites (including access points) within those devices. Figure 6 An example of a frame body for an MLE is shown. Figure 6 As shown, the MLE includes an element ID, length, element ID extension, multi-link control field, common info field, and link info field. The common info field carries information shared by multiple stations in the multi-link device, as well as information about the multi-link device itself. The link info field carries information about the stations on each link in the multi-link device. The multi-link control field carries the type of the multi-link element and indicates which fields in the common info appear and which do not. For example, the link info field includes zero or one per-STA profile sub-elements. Figure 6In the diagram, the `linkinfo` field includes `per-STA profile 1` to `per-STA profile x`, where `x` is an integer greater than 0. `per-STAprofile` sub-elements can include sub-element ID, length, `STAcontrol` field, `STA info` field, and `STA profile` field. STA profile fields include `field` fields, `element` fields, and non-inheritance elements. For example... Figure 6 As shown, the STA profile fields include field 1 to field m, element 1 to element n, and non-ihheritance element.

[0141] Multi-user (MU) EDCA

[0142] Compared to 802.11ac and earlier standards, sites compliant with the 802.11ax standard have two uplink transmission modes: contention-based transmission using EDCA and trigger-frame-based uplink transmission. The simultaneous existence of these two modes means that sites compliant with the 802.11ax standard have more channel access opportunities than traditional sites (i.e., sites not compliant with the 802.11ax standard), which is clearly unfair to traditional sites. To maintain relative fairness, the 802.11ax standard introduces the MUEDCA mechanism, ensuring that traditional sites are not significantly disadvantaged in channel contention. Furthermore, since trigger-based uplink transmission is more efficient than contention-based access, it is desirable for the AP to send more trigger frames to schedule uplink transmissions, and MUEDCA can achieve the same goal.

[0143] The basic idea of ​​the MU EDCA mechanism is that when a site is triggered by an AP (e.g., receiving a trigger frame) to send data, the priority of traditional EDCA access needs to be reduced. Specifically, the site uses a different set of EDCA parameters, namely the MU EDCA parameter set, for channel access. A site can use two sets (or two sets of EDCA parameter sets) for channel access: one is the traditional EDCA parameter set, and the other is the MU EDCA parameter set. Compared to using the traditional EDCA parameter set, the contention waiting time is longer and the backoff window is larger when using the MU EDCA parameter set for channel access, thus resulting in a lower priority for channel access.

[0144] The AP carries two sets of EDCA parameter sets in the Beacon frame or the associated response frame of the Beacon frame: one is the traditional EDCA parameter set, and the other is the MU EDCA parameter set. As mentioned above, the parameters in the MU EDCA parameter set are more conservative, i.e., larger AIFSN, CWmin, and CWmax. It should be noted that AIFSN, CWmin, and CWmax in the MU EDCA parameter set do not all need to be larger. When the station is not triggered, it can use the traditional EDCA parameter set for EDCA contention; once the station receives the trigger frame sent by the AP and performs uplink data transmission, the station needs to use the MU EDCA parameter set for channel contention for a period of time (e.g., AIFS). The length of this period of time can be carried in the MU EDCA parameter set. If the station does not receive the trigger frame and successfully completes an uplink data transmission within the aforementioned period of time, the station can revert to the traditional EDCA contention method, i.e., use the traditional EDCA parameter set for channel contention. In this application, channel contention and channel access are interchangeable. Figure 7 This is a schematic diagram illustrating the working principle of a MU EDCA mechanism provided in an embodiment of this application. For example... Figure 7 As shown, the STA initially uses the traditional EDCA parameter set for channel contention. After receiving the trigger frame from the AP and sending a data frame, the STA uses the MU EDCA parameter set for channel contention. After the MU EDCA timer expires, the STA uses the traditional EDCA parameter set for channel contention. The MU EDCA timer expiration indicates that the STA has not received a trigger frame and has not successfully completed an uplink data transmission within a certain period of time.

[0145] EPCS priority access mechanism

[0146] For EPCS, 802.11be defines a priority access mechanism, which aims to enable EPCS sites to access the channel as quickly as possible and ensure priority transmission of urgent services.

[0147] A site can send an EPCS priority access enable request frame to the access point to request EPCS priority access. The access point can respond by sending an EPCS priority access enable response frame. Both the EPCS priority access enable request and response frames can carry EDCA parameter sets as parameters for EDCA channel access. If the EPCS priority access mechanism is successfully established, the site will use the parameters in the EDCA parameter set to compete for EDCA channel access. Generally, the EDCA parameter set carried in the EPCS priority access enable request and response frames has a higher priority than the EDCA parameter set carried in the Beacon frame, thus giving EPCS sites (or EPCS STAs) a higher priority in EDCA competition than ordinary sites. An EPCS site can be a site that provides EPCS. An ordinary site can be a site that cannot provide EPCS. EPCS sites can send EPCS priority access enable request frames, while ordinary sites cannot.

[0148] Non-AP MLDs can also use the EPCS priority access mechanism, meaning that if one STA in a non-AP MLD sends a request, multiple STAs in the non-AP MLD can obtain priority access rights. For ease of description, this application may refer to a non-AP MLD that can use the EPCS priority access mechanism as an EPCS non-AP MLD.

[0149] As mentioned earlier, according to the MU EDCA channel access mechanism, after an EPCS site receives a trigger frame from the AP and successfully transmits a data frame, it will use the MU EDCA parameter set as the channel access parameters. However, all sites in the entire cell use the same MU EDCA parameter set. This would cause the EPCS site to lose its channel access priority compared to ordinary sites after receiving the trigger frame from the AP and successfully transmitting the data frame, which is clearly unreasonable. Therefore, it is necessary to study how to ensure that EPCS sites and EPCS non-AP MLDs have a higher channel access priority than ordinary sites in all scenarios.

[0150] The communication solution provided in this application is mainly applied to multi-link communication scenarios. Figure 1A , Figure 1B as well as Figure 1C This is a schematic diagram of a multi-link communication scenario provided in an embodiment of this application.

[0151] The following, with reference to the accompanying drawings, describes the communication scheme provided in this application that ensures EPCS sites and EPCS non-AP MLDs have a higher channel access priority than ordinary sites in all scenarios.

[0152] Figure 8 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 8 As shown, the method includes:

[0153] 801. The first station sends a request frame to the access point.

[0154] The first site can be a single-link STA or a site within a non-AP MLD. Alternatively, the first site can be an EPCS site or a site within an EPCS non-AP MLD. The access point can be a single-link AP or an AP within an AP MLD.

[0155] The aforementioned request frame is used to request priority access to the channel. Alternatively, the aforementioned request frame is used to request higher priority channel access parameters. Alternatively, the aforementioned request frame is used to request priority access to the channel. Alternatively, the aforementioned request frame is used to request higher priority channel contention parameters. The aforementioned request frame can be an EPCS priority access enable request frame, a national security and emergency preparedness (NSEP) priority access enable request frame, or other frames; the specific name of the request frame is not limited in this application.

[0156] The aforementioned request frame carries a first parameter set, which includes the MUEDCA parameters that the first site intends to use for channel contention. For example, the first parameter set includes the MUEDCA parameters that the first site intends to use for channel contention after successfully sending a data frame triggered by the access point's trigger frame. The MUEDCA parameters may include AIFSN, CWmin, CWmax, TXOP Limit, etc., corresponding to each access level. The channel access priority of the first parameter set may be higher than the channel access priority of the MUEDCA parameter set used by ordinary sites. The following section will describe how the request frame carries the first parameter set in conjunction with the frame body of the request frame.

[0157] In one possible implementation, the request frame carries first indication information indicating the first parameter set. This first indication information may be an identifier of the first parameter set or a binary sequence indicating the first parameter set, such as 10. The first station and the access point may pre-agree to indicate the first parameter set using the first indication information, thus reducing the amount of data carried by the request frame.

[0158] It should be noted that this application involves two or more MU EDCA parameter sets. One is the MU EDCA parameter set used by a normal station after successfully transmitting a data frame triggered by a received trigger frame; the other MU EDCA parameter sets are used by an EPCS station (e.g., the first station) after successfully transmitting a data frame triggered by a received trigger frame. For example, after successfully transmitting a data frame triggered by a received trigger frame, a normal station uses parameters from the first MU EDCA parameter set for channel access; the first station uses parameters from the first parameter set for channel access after successfully transmitting a data frame triggered by a received trigger frame; this first parameter set is a second MU EDCA parameter set different from the first MU EDCA parameter set. In one possible implementation, different EPCS stations may use different MU EDCA parameter sets for channel access after successfully transmitting a data frame triggered by a received trigger frame.

[0159] In one possible implementation, the request frame also carries a second parameter set, which includes the MU EDCA parameters that the second site intends to use for channel contention, and the second site and the first site belong to the same multi-link site device. In another possible implementation, the second parameter set is included in the link information field of the MLE in the request frame. The following description of how the request frame carries the second parameter set will be based on the frame body of the request frame. It should be understood that the request frame may also carry the MU EDCA parameters that one or more sites belonging to the same multi-link site device as the first site intend to use for channel contention. For example, the request frame may also carry the MU EDCA parameters that site 1 intends to use for channel contention and the MU EDCA parameters that site 2 intends to use for channel contention, where both site 1 and site 2 belong to the same multi-link site device as the first site.

[0160] 802. The first station receives the response frame in response to the request frame.

[0161] In one possible implementation, the response frame carries a third parameter set, which includes MU EDCA parameters to be used by the first site in channel contention. This third parameter set may be the same as or different from the first parameter set.

[0162] It should be understood that if the access point does not agree with the first site using parameters from the first parameter set for channel contention, the access point may send a response frame carrying a third parameter set to the first site. This third parameter set includes the MU EDCA parameters that the first site will use for channel contention, and this third parameter set is different from the first parameter set. In this implementation, carrying the third parameter set in the response frame ensures the priority of channel access by allowing the first site to use parameters from the third parameter set for channel contention. The following section will describe how the response frame carries the third parameter set in conjunction with the frame body. It should be understood that if the access point agrees with the first site using parameters from the first parameter set for channel contention, the response frame sent by the access point to the first site may carry the third parameter set; in one possible implementation, the third parameter set includes or is equal to the first parameter set, or the first parameter set is a subset of the third parameter set. If the access point agrees that the first site can use the parameters in the first parameter set for channel contention, then the access point can also send a response frame to the first site without carrying a third parameter set specific to the first site. That is, the response frame sent to the first site does not carry any parameter set specific to the first site, indicating that the first site is allowed to use the first parameter set carried in its request frame for subsequent channel contention by default. In this implementation, the absence of a third parameter set in the response frame indicates that the access point agrees to the first site using the parameters in the first parameter set for channel contention, which reduces the amount of data in the response frame.

[0163] In one possible implementation, the request frame also carries a second parameter set, which includes the MU EDCA parameters that the second site intends to use for channel contention. The second site and the first site belong to the same multi-link site device. Correspondingly, the response frame also carries a fourth parameter set, which includes the MU EDCA parameters that the second site intends to use for channel contention. This fourth parameter set may be the same as or different from the second parameter set. It should be understood that if the access point agrees to the second site using parameters from the second parameter set for channel contention, the response frame sent by the access point to the first site may carry the fourth parameter set. In one possible implementation, the fourth parameter set includes or 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 to the second site using parameters from the second parameter set for channel contention, the access point may also send a response frame to the first site without carrying the fourth parameter set specific to the first site. That is, the response frame sent to the second site does not carry any parameter set specific to the second site, indicating that the second site is allowed by default to use the second parameter set carried in its request frame for subsequent channel contention. The fourth parameter set will then be described in conjunction with the frame body of the response frame.

[0164] In some possible implementations, the request frame sent by the first site may not carry the MU EDCA parameters that the first site intends to use for channel contention. Alternatively, the first site may only carry the MU EDCA parameter set that one or more sites belonging to the same multi-link site device as the first site intend to use for channel contention. The response frame sent by the access point to the first site may only carry the MU EDCA parameter set that allows one or more sites belonging to the same multi-link site device as the first site to use for channel contention.

[0165] Figure 8 The method flow can be replaced as follows: A first site sends a request frame to an access point, the request frame carrying a second parameter set, which includes the MU EDCA parameters that the second site intends to use for channel contention. The second site and the first site belong to the same multi-link site device. The access point sends a response frame to the first site, the response frame carrying a fourth parameter set, which includes the MU EDCA parameters that the access point allows the second site to use for channel contention. The fourth parameter set may be the same as or different from the second parameter set. The response frame may only carry the fourth parameter set. It should be understood that if the access point agrees to the second site using parameters from the second parameter set for channel contention, the response frame sent by the access point to the first site may carry the fourth parameter set. In one possible implementation, the fourth parameter set includes or 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 site can use the parameters in the second parameter set for channel contention, then the access point can also send a response frame to the first site without carrying the fourth parameter set. That is, by sending a response frame without carrying any parameter set, the access point indicates that it implicitly allows the second site to use the second parameter set carried in its request frame for subsequent channel contention. The following section will describe how the request frame carries the second parameter set in conjunction with the frame body of the request frame.

[0166] In this embodiment of the application, the request frame carries a first parameter set, which includes the MU EDCA parameters that the first station intends to use for channel contention, so as to use parameters with higher channel priority for channel contention.

[0167] The frame body of the request frame is described below with reference to the accompanying drawings or tables. Furthermore, the frame body of the request frame is used to describe how the request frame carries the first parameter set and how it carries the second parameter set.

[0168] Frame body 1 of the request frame:

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

[0170] Table 1

[0171] 1 category 2 protected EHT action 3 dialog token 4 EDCA parameter set 5 MU EDCA parameter set 6 priority access multi-link element

[0172] The sorting in Table 1 is merely illustrative and is not intended to limit the scope of this invention.

[0173] The category field indicates the type of action frame. Its value can be "protected EHT action", which indicates that the action frame belongs to the "protected EHT action" category.

[0174] The `protected EHT action` field indicates the subtype of the action frame. In one 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.

[0175] The dialog token field is used for pairing request and response frames.

[0176] The EDCA parameter set field indicates the EDCA parameter set to be used at the first site.

[0177] The MU EDCA parameter set field is used to indicate the MU EDCA parameter set that the first STA intends to use, i.e., the first parameter set.

[0178] The "priority access multi-link element" field carries the EDCA parameter set and MU EDCA parameter set to be used by one or more sites belonging to the same multi-link site device as the first site. For example, the "priority access multi-link element" field carries the EDCA parameter set and MU EDCA parameter set to be used by a second site belonging to the same multi-link site device as the first site. The "priority access multi-link element" field can be replaced by "basic multi-link element" or other fields, as long as this field carries the EDCA parameter set and MU EDCA parameter set to be used by the second site; this application does not impose any limitations on this. The "priority access multi-link element" field can also be replaced by a link ID bitmap field plus a list of parameter set fields. The parameter set fields include EDCA parameter set and / or MU EDCA parameter set. The link ID bitmap field is a bitmap of link identifiers, where each bit indicates whether the parameter set of the corresponding link is included in the list of the subsequent parameter set fields. For example, the link ID bitmap field is 16 bits long, with each bit corresponding to one link, for a total of 16 links. The i-th bit in the link ID bitmap field is 1, indicating that the parameter set list in the subsequent parameter set field includes the parameter set of the link with link ID (i-1). The value of 1 ranges from 1 to 16, and the value of link ID ranges from 0 to 15.

[0179] The priority access multi-link element field is optional, not mandatory. This means that when the first site is an independent site, the request frame sent by that first site does not need to carry the EDCA parameter set and MU EDCA parameter set to be used by other sites. When the first site is a site in a non-AP MLD, the request frame sent by that first site may carry the EDCA parameter set and MU EDCA parameter set to be used by one or more sites belonging to the same multi-link site device as that first site, or it may not carry the EDCA parameter set and MU EDCA parameter set to be used by other sites. Figure 9A This is an example of the format of a priority access multi-link element field provided for embodiments of this application. Figure 9AThe format of the priority access multi-link element field shown is the same as... Figure 6 Compared to the MLE format, one difference is that the STA profile field includes different information. Figure 9A For the meaning of each field, please refer to [link / reference]. Figure 6 The meaning of each field in the priority access multi-link element field. The STAprofile field in the priority access multi-link element field can include the EDCA parameter set and the MU EDCA parameter set. For example... Figure 9A As shown, the STA control field contains the link identifier (link ID).

[0180] In one possible implementation, the priority access multi-link element field includes one or more per-STA profiles. Each per-STA profile corresponds to a site belonging to the same multi-link site device as the first site. Each per-STA profile includes the EDCA parameter set and MU EDCA parameter set to be used by the site corresponding to that per-STA profile. Any two per-STA profiles correspond to different sites. For example... Figure 9AAs shown, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., per-STA profile x. Per-STA profile 1 corresponds to site 1, per-STA profile 2 corresponds to site 2, ..., per-STA profile x corresponds to site x. Per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set to be used by site 1, per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set to be used by site 2, and so on. Per-STA profile x includes the EDCA parameter set and MU EDCA parameter set to be used by site x. x is an integer greater than 1. Site 1, site 2, ..., site x all belong to the same multi-link site device as the first site. For example, the STAprofile field in each per-STA profile within the priority access multi-link element field includes the EDCA parameter set and MU EDCA parameter set to be used by the site 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 site 1, and per-STA profile 2 corresponds to site 2. The STA profile field in per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set to be used by site 1; the STA profile field in per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set to be used by site 2. In this example, site 1 and site 2 belong to the same multi-link site device. In one possible implementation, the STAcontrol field in the per-STA profile contains a link ID corresponding to a site, which corresponds to this 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 site 1, and per-STA profile 2 corresponds to site 2. The STAcontrol field in per-STA profile 1 includes the link ID corresponding to site 1, and the STAcontrol field in per-STA profile 2 includes the link ID corresponding to site 2. The link ID corresponding to a site is the ID of the link to the access point that the site accesses. The link identifier in the STA control field indicates a link or site. The access point can determine the site corresponding to the per-STA profile based on the link ID contained in the STA control field of the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field of the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the site intends to use.

[0181] Frame body 2 of the request frame:

[0182] Table 2 shows examples of fields included in the frame body 2 of the request frame. Referring to Table 2, the aforementioned 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 aforementioned 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. That is, the first parameter set is contained in the MLE in the request frame. The order in Table 2 is merely illustrative and is not limited in the embodiments of the present invention. Since the meaning of each field in Table 2 has been described in the introduction of Table 1, it will not be repeated here.

[0183] Table 2

[0184] 1 category 2 protected EHT action 3 dialog token 4 priority access multi-link element

[0185] In one possible implementation, the first parameter set is contained in the link info field of the priority access multi-linkelement field. Figure 9B An example of another format for the priorityaccess multi-link element field provided for embodiments of this application. Figure 9B For the meaning of each field, please refer to [link / reference]. Figure 6 Descriptions of each field in the document. Figure 9B The priority access multi-link element field in the request frame is shown, and MU EDCAparameter set represents the first parameter set. Figure 9B and Figure 9A compared to, Figure 9B One of the per-STA profiles corresponds to the first site. Figure 9A The x per-STA profiles in the diagram correspond to the x sites that belong to the same multi-link site device as the first site.

[0186] In one possible implementation, the priority access multi-link element field includes the per-STA profile corresponding to the first site, which includes the EDCA parameter set and MU EDCA parameter set to be used by the first site. For example, the STA profile field in the per-STA profile of the priority access multi-link element field includes the EDCA parameter set and MU EDCA parameter set to be used by the first site corresponding to that per-STA profile. In another possible implementation, the STA control field in the per-STA profile contains the link ID corresponding to the first site, which corresponds to that per-STA profile. Figure 9BAs shown, the link information field includes a per-STA profile, which corresponds to the first site. The per-STA profile includes an STA control field and an STA profile field. The STA control field includes a link ID, and the STA profile field includes an EDCA parameter set and a MU EDCA parameter set. The link identifier in the STA control field indicates the first site. The access point can determine the site corresponding to the per-STA profile based on the link ID contained in the STA control field. The EDCA parameter set and MU EDCA parameter set in the STA profile field of the per-STA profile are the EDCA parameter set and MU EDCA parameter set to be used by the site.

[0187] In one possible implementation, the priority access multi-link element field includes multiple per-STA profiles, one of which corresponds to a first site, and each of the other per-STA profiles corresponds to a site belonging to the same multi-link site device as the first site. Each per-STA profile includes the EDCA parameter set and MU EDCA parameter set to be used by the site corresponding to the per-STA profile, and any two per-STA profiles correspond to different sites. Figure 9C An example of another format for the priority access multi-link element field provided for embodiments of this application. For example... Figure 9CAs shown, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., per-STA profile m. Per-STA profile 1 corresponds to the first site, per-STA profile 2 corresponds to site 2, ..., per-STA profile m corresponds to site m. Per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set to be used by the first site, per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set to be used by site 2, and so on. Per-STA profile m includes the EDCA parameter set and MU EDCA parameterset to be used by site m. m is an integer greater than 1. Site 2, site 3, ..., site m all belong to the same multi-link site device as the first site. For example, the STA profile field in each per-STA profile in the priority access multi-link element field includes the EDCA parameter set and MU EDCA parameter set to be used by the site corresponding to that per-STA profile. For example, the priority access multi-link element field includes per-STAprofile 1 and per-STAprofile 2. Per-STA profile 1 corresponds to the first site, and per-STAprofile 2 corresponds to site 2. The STA profile field in per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set to be used by the first site; the STA profile field in per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set to be used by site 2. In this example, site 2 and the first site belong to the same multi-link site device. In one possible implementation, the STA control field in per-STAprofile contains a link ID corresponding to a site, and this site corresponds to this per-STAprofile.For example, the priority access multi-link element field includes per-STA profile1 and per-STA profile2. Per-STA profile1 corresponds to the first site, and per-STA profile2 corresponds to the second site. The STA control field in per-STA profile1 includes the link ID corresponding to the first site, and the STA control field in per-STA profile2 includes the link ID corresponding to the second site. The link ID corresponding to a site is the ID of the link that the site connects to the access point. The link identifier in the STA control field of the per-STA profile indicates a site or link. The STA profile in the per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the site intends to use. The access point can determine the site corresponding to the per-STA profile based on the link ID contained in the STA control field of the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field of the per-STA profile are the EDCA parameter set and MU EDCA parameter set that the site intends to use.

[0188] In one possible implementation, the request frame sent by the first station carries only the MU EDCA parameter set to be used by one or more stations belonging to the same multi-link site device as the first station for channel contention. These MU EDCA parameter sets may be included in the link information (linkinfo) field of the priority access multi-link element field. In this implementation, the priority access multi-link element field includes multiple per-STA profiles, each corresponding to a station belonging to the same multi-link site device as the first station. Each per-STA profile includes the EDCA parameter set and MU EDCA parameter set to be used by the station corresponding to that per-STA profile. Any two per-STA profiles correspond to different stations. In this implementation, the link information (link info) field of the priority access multi-link element field does not carry the EDCA parameter set and MU EDCA parameter set to be used by the first station.

[0189] The following describes the frame body of the response frame with reference to the accompanying figures or tables, and then describes how the response frame carries the third parameter set and how it carries the fourth parameter set.

[0190] Frame body 1 of the response frame:

[0191] Table 3 shows examples of fields included in the frame body 1 of the response frame. Referring to Table 3, the aforementioned third parameter set is contained in the MU EDCA parameter set field of the response frame. In other words, the MU EDCA parameterset field in Table 3 carries the third parameter set.

[0192] Table 3

[0193] 1 category 2 protected EHT action 3 dialog token 4 status code 5 EDCA parameter set 6 MU EDCA parameter set 7 priority access multi-link element

[0194] The sorting in Table 3 is merely illustrative and is not intended to limit the scope of this invention.

[0195] The meanings of the first three fields in Table 3 are the same as those of the first three fields in Table 1. The difference is that the value of the protectedEHT action field is EPCS priority access enable response.

[0196] The status code field is used to indicate whether the EPCS was successfully established.

[0197] The EDCA parameter set is used to indicate the set of EDCA parameters that the access point allows the first site to use.

[0198] The MU EDCA parameter set is used to indicate the MU EDCA parameter set that the access point allows the first site to use, i.e., the third parameter set. It should be understood that if the access point allows the first site to use the EDCA parameter set or the MU EDCA parameter set in the request frame, it does not need to carry the EDCA parameter set or MU EDCA parameter set in the response frame.

[0199] The priority access multi-link element field carries the EDCA parameter set and MU EDCA parameter set that the access point allows one or more sites belonging to the same multi-link site device as the first site to use. For example, the priority access multi-link element field carries the EDCA parameter set and MU EDCA parameter set (i.e., the fourth parameter set) that the access point allows a second site belonging to the same multi-link site device to use. The priority access multi-link element field can be replaced by the basic multi-link element or other fields, as long as this field carries the EDCA parameter set and MU EDCA parameter set that the access point allows the second site to use; this application does not impose any limitations on this. The priority access multi-link element field is optional, not mandatory. It should be understood that if the access point allows the second site to use the EDCA parameter set or MU EDCA parameter set in the request frame, it is not necessary to carry the EDCA parameter set or MU EDCA parameter set allowed for the second site in the response frame. Figure 9A An example of the format of the priority access multi-link element field in the response frame is shown. Figure 9A As shown, the STA profile field in the priority access multi-link element field of the response frame may include the EDCA parameter set and the MU EDCA parameter set.

[0200] In one possible implementation, the priority access multi-link element field includes one or more per-STA profiles. Each per-STA profile corresponds to a site belonging to the same multi-link site device as the first site. Each per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the access point allows the site corresponding to that per-STA profile to use. Any two per-STA profiles correspond to different sites. For example... Figure 9AAs shown, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., per-STA profile x. Per-STA profile 1 corresponds to site 1, per-STA profile 2 corresponds to site 2, ..., per-STA profile x corresponds to site x. Per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set allowed by the access point for site 1; per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set allowed by the access point for site 2, and so on. Per-STA profile x includes the EDCA parameter set and MU EDCA parameter set allowed by the access point for site x. x is an integer greater than 1. Site 1, site 2, ..., site x all belong to the same multi-link site device as the first site. 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 allowed by the access point for the site 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 site 1, and per-STA profile 2 corresponds to site 2. The STA profile field in per-STA profile 1 includes the EDCA parameter set and MUEDCA parameter set that the access point allows site 1 to use; the STA profile field in per-STA profile 2 includes the EDCA parameter set and MUEDCA parameter set that the access point allows site 2 to use. In this example, site 1 and site 2 belong to the same multi-link site device. In one possible implementation, the STA control field in the per-STA profile contains a link ID corresponding to a site that corresponds to this per-STA profile.For example, the priorityaccess multi-link element field includes per-STA profile 1 and per-STA profile 2. Per-STA profile 1 corresponds to site 1, and per-STA profile 2 corresponds to site 2. The STA control field in per-STA profile 1 includes the link ID corresponding to site 1, and the STA control field in per-STA profile 2 includes the link ID corresponding to site 2. The link identifier in the STA control field of the per-STA profile indicates a site. The STA profile in this per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the access point allows the site to use. The first site can determine the site corresponding to this per-STA profile based on the link ID contained in the STA control field of the per-STA profile. The EDCA parameter set and MU EDCA parameter set in the STA profile field of this per-STA profile are the EDCA parameter set and MU EDCA parameter set that the access point allows the site to use.

[0201] Frame body 2 of the response frame:

[0202] Table 4 shows examples of fields included in frame body 2 of the response frame. Referring to Table 4, the aforementioned third parameter set is contained 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. That is, the third parameter set is contained in the MLE in the response frame. The order in Table 4 is merely illustrative and is not limited in the embodiments of this invention. Since the meaning of each field in Table 4 has been described in the introduction of Table 3, it will not be repeated here.

[0203] Table 4

[0204]

[0205]

[0206] In one possible implementation, the third parameter set is contained in the link info field of the priority access multi-linkelement field. (Reuse) Figure 9B , Figure 9B The priorityaccess multi-link element field in the response frame is shown. Figure 9B In this context, 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.

[0207] In one possible implementation, the priority access multi-link element field includes the per-STA profile corresponding to the first site. This per-STA profile includes the EDCA parameter set and MU EDCA parameter set (i.e., the third parameter set) that the access point allows the first site to use. For example, the STA profile field within the per-STA profile of the priority access multi-link element field includes the EDCA parameter set and MU EDCA parameter set that the access point allows the first site corresponding to this per-STA profile to use. In another possible implementation, the STA control field within the per-STA profile contains the link ID corresponding to the first site, which is associated with this per-STA profile. Figure 9BAs shown, the link information field includes a per-STA profile, which corresponds to the first site. This per-STA profile includes an STA control field and an STA profile field. The STA control field includes the link ID, and the STA profile field includes the EDCA parameter set and the MU EDCA parameter set. It should be understood that the first site can obtain the EDCA parameter set and MU EDCA parameter set to be used by the first site based on the STA control field and the STA profile field in the priority access multi-link element field; that is, the EDCA parameter set and MU EDCA parameter set that the access point allows the first site to use.

[0208] In one possible implementation, the priority access multi-link element field includes multiple per-STA profiles, one of which corresponds to a first site, and each of the other per-STA profiles corresponds to a site belonging to the same multi-link site device as the first site. Each per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the access point allows the site corresponding to the per-STA profile to use. Any two per-STA profiles correspond to different sites. Figure 9C The "priority access multi-link element" field in the response frame can be considered equivalent to the "priority access multi-link element" field in the response frame. For example... Figure 9CAs shown, the priority access multi-link element field includes per-STA profile 1, per-STA profile 2, ..., per-STA profile m. per-STA profile 1 corresponds to the first site, per-STA profile 2 corresponds to site 2, ..., per-STA profile m corresponds to site m. per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set allowed by the access point for the first site; per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set allowed by the access point for site 2, and so on. Per-STA profile m includes the EDCA parameter set and MU EDCA parameter set allowed by the access point for site m. m is an integer greater than 1. Site 2, site 3, ..., site m all belong to the same multi-link site device as the first site. 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 allowed by the access point for the site 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 the first site, and per-STA profile 2 corresponds to site 2. The STA profile field in per-STA profile 1 includes the EDCA parameter set and MU EDCA parameter set that the access point allows the first site to use. The STA profile field in per-STA profile 2 includes the EDCA parameter set and MU EDCA parameter set that the access point allows site 2 to use. In this example, site 2 and the first site belong to the same multi-link site device. In one possible implementation, the STA control field in the per-STA profile contains a link ID corresponding to a site, which corresponds to this per-STA profile.For example, the "priority access multi-link element" field includes per-STA profile1 and per-STA profile2. Per-STA profile1 corresponds to the first site, and per-STA profile2 corresponds to the second site. The STA control field in per-STA profile1 includes the link ID corresponding to the first site, and the STA control field in per-STA profile2 includes the link ID corresponding to the second site. The first site can determine the site corresponding to this per-STA profile based on the link ID contained in the STA control field of the per-STA profile. The EDCA parameter set and MU EDCA parameterset in the STA profile field of this per-STA profile are the EDCA parameter set and MU EDCA parameter set that the access point allows the site to use.

[0209] In one possible implementation, the response frame sent by the access point carries only the MU EDCA parameter set to be used by one or more sites belonging to the same multi-link site device as the first site for channel contention. These MU EDCA parameter sets may be included in the link info field of the priority access multi-link element field. In this implementation, the priority access multi-link element field includes multiple per-STA profiles. Each per-STA profile corresponds to a site belonging to the same multi-link site device as the first site. Each per-STA profile includes the EDCA parameter set and MU EDCA parameter set that the access point allows the site corresponding to that per-STA profile to use. Any two per-STA profiles correspond to different sites. In this implementation, the link info field of the priority access multi-link element field does not carry the EDCA parameter set and MU EDCA parameter set that the access point allows the first site to use.

[0210] Figure 10 Another communication flowchart is provided for an embodiment of this application. Figure 10 The method flow is as follows Figure 8 One possible implementation of the method in [the document / framework]. For example... Figure 10 As shown, the method includes:

[0211] 1001. The first station sends a request frame to the access point.

[0212] Before sending a request frame to the access point, the first site may generate a request frame. Step 1001 can be found in step 801. The request frame carries a first parameter set. The channel access priority of the first parameter set is higher than the channel access priority of the MU EDCA parameter set used by ordinary sites.

[0213] 1002. The access point sends a response frame to the first site in response to the request frame.

[0214] Table 5 shows examples of fields in the response frame sent by the access point to the first site. The meanings of the fields in Table 5 can be found in Table 3.

[0215] Table 5

[0216] 1 category 2 protected EHT action 3 dialog token 4 status code 5 EDCA parameter set

[0217] 1003. After sending a data frame triggered by the access point trigger frame, the first station uses the parameters in the first parameter set to compete for the channel.

[0218] One possible implementation of step 1003 is as follows: After sending a data frame triggered by the access point's trigger frame, the first station uses the parameters in the aforementioned first parameter set to compete for channel space within a first duration; the first duration is obtained from the parameters in the aforementioned first parameter set. The first parameters may include AIFSN, CWmin, CWmax, TXOP Limit, etc., corresponding to each access level. The first duration may be obtained from the MU EDCA timer field in the first parameter set. Or, 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. Another example is that the parameters in the first parameter set indicate the first duration, and the first station determines the first duration based on the parameters in the first parameter set that indicate the first duration.

[0219] In this embodiment, after sending a data frame triggered by the access point trigger frame, the first station uses parameters from the first parameter set to compete for the channel; compared to ordinary stations, it can have a higher channel access priority.

[0220] Figure 11 Another communication flowchart is provided for an embodiment of this application. Figure 11 The method flow is as follows Figure 8One possible implementation of the method in [the document / framework]. For example... Figure 11 As shown, the method includes:

[0221] 1101. The first station sends a request frame to the access point.

[0222] Step 1001 can be referred to step 801. The request frame carries the first parameter set.

[0223] 1102. If the access point disagrees with the first site using the parameters in the first parameter set for channel contention, it sends a response frame carrying the third parameter set to the access point.

[0224] The response frame carries a third parameter set, which includes the MU EDCA parameters to be used by the first site in channel contention. This third parameter set is different from the first parameter set.

[0225] 1103. After the first station sends a data frame triggered by the access point trigger frame, it uses the parameters in the third parameter set to compete for the channel.

[0226] One possible implementation of step 1003 is as follows: After sending a data frame triggered by the access point's trigger frame, the first station uses parameters from a third parameter set to compete for channel space within a third duration; this third duration is obtained from the 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. Another example is that the parameters in the third parameter set indicate the third duration, and the first station determines the third duration based on the parameters in the third parameter set that indicate the third duration.

[0227] The first parameter set is determined by the first station from its own perspective, without considering the access point and other stations. The third parameter set is determined by the access point from a holistic perspective, comprehensively considering multiple stations. In this embodiment, after sending a data frame triggered by the access point's trigger frame, the first station uses the parameters from the third parameter set for channel contention. This allows the first station to have a higher channel access priority while reducing the impact on other stations.

[0228] Figure 12 Another communication flowchart is provided for an embodiment of this application. Figure 12 The method flow is as follows Figure 8 One possible implementation of the method in [the document / framework]. For example... Figure 12 As shown, the method includes:

[0229] 1201. The first station sends a request frame to the access point.

[0230] The request frame carries a first parameter set and a second parameter set. The second parameter set includes the MU EDCA parameters that the second site intends to use for channel contention, and this second site and the aforementioned first site belong to the same multi-link site device. The second parameter set may also include the EDCA parameters that the second site intends to use for channel contention.

[0231] In one possible implementation, before sending a request frame to the access point, the first station may receive first parameter information from the second station. This first parameter information includes a second parameter set, which includes the MU EDCA parameters that the second station intends to use for channel contention. In this implementation, the second station may proactively send the first parameter information containing the second parameter set to the first station.

[0232] In one possible implementation, before sending a request frame to the access point, the first station performs the following operations: sends a parameter set query message to the second station; and receives second parameter information, including a second parameter set, sent by the second station in response to the parameter set query message. The parameter set query message is used to obtain the MU EDCA parameter set that the second station intends to use for channel contention. In this implementation, the first station obtains the MU EDCA parameter set that the second station intends to use for channel contention through an active query.

[0233] 1202. The access point sends a response frame to the first site in response to the request frame.

[0234] In one possible implementation, the response frame carries a third parameter set and a fourth parameter set. The third parameter set includes MU EDCA parameters that the access point allows the first site to use for channel contention, and the fourth parameter set includes MU EDCA parameters that the access point allows the second site to use for channel contention. The third parameter set differs from the first parameter set, and the fourth parameter set also differs from the second parameter set. For each parameter set that the request frame carries, if the access point agrees with a site (any site) using its proposed parameter set, the response frame may or may not carry that proposed parameter set; if the access point disagrees with the site using its proposed parameter set, the response frame carries the parameter set that the access point allows the site to use. For example, if the access point agrees with the first site using parameters from the first parameter set for channel contention, the response frame may or may not carry that first parameter set. As another example, if the access point disagrees with the first site using parameters from the first parameter set for channel contention, the response frame carries a third parameter set that the access point allows the first site to use, which differs from the first parameter set. For example, if the access point disagrees with the second site using parameters from the second parameter set for channel contention, the response frame carries a fourth parameter set that the access point allows the second site to use, which is different from the second parameter set.

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

[0236] Step 1203 can be replaced with: The second site can obtain the fourth parameter set from the first site. The fourth parameter set is the MU EDCA parameter set that the access point allows the second site to use.

[0237] 1204. After the first station sends a data frame triggered by the access point trigger frame, it uses the parameters in the third parameter set to compete for the channel.

[0238] The third parameter set may be the same as or different from the first parameter set. It should be understood that if the access point agrees with the first site using parameters from the first parameter set for channel contention, the response frame may or may not carry the third parameter set, which is the same as the first parameter set. It should be understood that if the access point does not agree with the first site using parameters from the first parameter set for channel contention, the response frame carries the third parameter set, which is different from the first parameter set. The order of steps 1203 and 1204 is not limited. Step 1204 is optional, not necessary.

[0239] One possible implementation of step 1204 is as follows: After the first station sends a data frame triggered by the access point trigger frame, it uses parameters from the third parameter set to compete for the channel during the third time period; the third time period is obtained from the parameters in the third parameter set.

[0240] 1205. After the second station sends a data frame triggered by the access point trigger frame, it uses the parameters in the fourth parameter set to compete for the channel.

[0241] The fourth parameter set may be the same as or different from the second parameter set. It should be understood that if the access point agrees with the second site using parameters from the second parameter set for channel contention, the response frame may or may not carry the fourth parameter set, which is the same as the second parameter set. It should be understood that if the access point does not agree with the second site using parameters from the second parameter set for channel contention, the response frame carries the fourth parameter set, which is different from the second parameter set.

[0242] One possible implementation of step 1204 is as follows: After the second station sends a data frame triggered by the access point trigger frame, it uses parameters from the fourth parameter set to compete for the channel during the fourth duration; the fourth duration is obtained from the parameters in the fourth parameter set.

[0243] In one possible implementation, the response frame carries a third parameter set but not a fourth parameter set. The third parameter set includes MU EDCA parameters that the access point allows the first station to use for channel contention, and the fourth parameter set includes MU EDCA parameters that the access point allows the second station to use for channel contention. This third parameter set is different from the first parameter set. Step 1203 can be replaced by: the second station receiving the second parameter set from the first station, or the second station confirming that the access point allows it to use the second parameters for channel contention. Step 1205 can be replaced by: the second station using the parameters in the second parameter set for channel contention after sending a data frame triggered by the access point's trigger frame. The response frame carrying a third parameter set but not a fourth parameter set can be either a response frame carrying both a third and a second parameter set, or a response frame carrying a third parameter set but not a second parameter set.

[0244] In one possible implementation, the response frame carries a fourth parameter set but not a third parameter set. The fourth parameter set includes MU EDCA parameters used by the access point to allow the second station to compete for channel contention, and the third parameter set includes MU EDCA parameters used by the access point to allow the first station to compete for channel contention. This fourth parameter set is different from the second parameter set. Step 1204 can be replaced by: after sending a data frame triggered by the access point's trigger frame, the first station uses parameters from the first parameter set to compete for channel contention. The response frame carrying a fourth parameter set but not a third parameter set can be either a response frame carrying both the fourth and first parameter sets, or a response frame carrying the fourth parameter set but not the first parameter set.

[0245] In one possible implementation, the response frame does not carry a fourth parameter set and a third parameter set. The fourth parameter set includes MU EDCA parameters that the access point allows the second station to use for channel contention, and the third parameter set includes MU EDCA parameters that the access point allows the first station to use for channel contention. The fourth parameter set is different from the second parameter set, and the third parameter set is different from the first parameter set. Step 1203 can be replaced by: the second station receiving the second parameter set from the first station, or the second station confirming that the access point allows the second station to use the second parameters for channel contention. Step 1204 can be replaced by: the first station using the parameters in the first parameter set for channel contention after sending a data frame triggered by the access point's trigger frame. Step 1205 can be replaced by: the second station using the parameters in the second parameter set for channel contention after sending a data frame triggered by the access point's trigger frame. The response frame not carrying the fourth and third parameter sets can mean that the response frame carries the first and second parameter sets, or that the response frame does not carry any parameter sets.

[0246] In this embodiment of the application, the request frame carries a first parameter set and a second parameter set. Figure 12 The embodiments and Figure 11 Compared to the previous embodiment, the request frame sent by the first station also carries a second set of parameters, so the second station can obtain the MU EDCA parameters that the access point allows the second station to use without sending a request frame; this can reduce signaling interactions.

[0247] Figure 13 Another communication flowchart is provided for an embodiment of this application. Figure 13 The methods and processes in Figure 8 , Figure 10 , Figure 11 as well as Figure 12 One difference in the method flow is that the request frame sent by the first site does not contain the MU EDCA parameters that the first site intends to use. For example... Figure 13 As shown, the method includes:

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

[0249] Table 6 shows examples of the fields in the request frame sent by the first site to the access point. The meaning of each field in Table 6 can be found in Table 1.

[0250] Table 6

[0251]

[0252]

[0253] The sorting (order) in Table 6 is merely illustrative and is not intended to limit the scope of this invention.

[0254] 1302. The access point sends a response frame to the first site in response to the request frame.

[0255] The response frame carries a third parameter set, which includes the MUEDCA parameters that the first site will use during channel contention. See also... Figure 9B MU EDCA parameter set represents the third parameter set.

[0256] Step 1301 is optional, not mandatory. In one possible implementation, the access point directly sends a radio frame carrying a third parameter set to the first site. That is, steps 1301 and 1302 can be replaced by the access point sending a radio frame carrying a third parameter set to the first site, which may be an EPCS priority access enable request frame. This radio frame may also carry a fourth parameter set, which includes the MU EDCA parameters to be used by the second site in channel contention, and the second site and the first site belong to the same multi-link site device.

[0257] 1303. After the first station sends a data frame triggered by the access point trigger frame, it uses the parameters in the third parameter set to compete for the channel.

[0258] Step 1303 can be found in step 1203.

[0259] In one possible implementation, the response frame also carries a fourth parameter set, which includes the MU EDCA parameters to be used by the second site in channel contention, the second site and the first site belonging to the same multi-link site device. See also Figure 9C The second station corresponds to per-STA profile 2, where the MU EDCA parameter set represents the fourth parameter set. In this implementation, after sending a data frame triggered by the access point's trigger frame, the second station uses the parameters in the fourth parameter set to compete for channel access.

[0260] In this embodiment, the request frame does not carry the MU EDCA parameter set, while the response frame carries the MU EDCA parameters that the access point allows the first site to use; this can reduce the amount of data carried by the request frame.

[0261] Figure 8 , Figure 10 , Figure 11 , Figure 12 as well as Figure 13 In the process, the first station obtains the MU EDCA parameter set to be used for channel contention by sending a request frame. The following section, with reference to the accompanying diagram, describes the scheme 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.

[0262] Figure 14 A flowchart illustrating another communication method provided in an embodiment of this application. Figure 14 As shown, the method includes:

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

[0264] The request frame is used to request priority access to the channel. Step 1401 can be found in step 1301. Table 6 shows examples of the fields in the request frame sent by the first station to the access point.

[0265] 1402. The access point sends a response frame to the first site in response to the request frame.

[0266] Table 5 shows examples of the fields in the response frame sent by the access point to the first site.

[0267] In one possible implementation, the request frame is an EPCS priority access enable request frame, and the response frame is an EPCS priority access enable response frame.

[0268] 1403. Based on the response frame and the EDCA parameter set carried in the beacon frame, the first station determines the MU EDCA parameter set to be used by the first station.

[0269] In one possible implementation, the MU EDCA parameter set used by the first station is used for channel contention after successfully transmitting a data frame triggered by the access point's trigger frame. In this implementation, the first station, after successfully transmitting the data frame triggered by the access point's trigger frame, uses a defined MU EDCA parameter set for channel contention, thus achieving a higher channel access priority. In another possible implementation, the MU EDCA parameter set used by the first station is used for channel contention during a second duration after successfully transmitting the data frame triggered by the access point's trigger frame; this second duration is obtained from parameters in the MU EDCA parameter set.

[0270] In one possible implementation, determining the MU EDCA parameter set adopted by the first station further includes: determining the MU EDCA parameter set adopted by the first station based on the MU EDCA parameter set in the beacon frame. That is, the first station determines the MU EDCA parameter set adopted 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 adopted by the first station based on the MU EDCA parameter set in the beacon frame and the MU EDCA timer in the MU EDCA parameter set can be: the first station determines the MU EDCA parameter set adopted by the first station based on the EDCA parameter set in the beacon frame and the MU EDCA timer in the MU EDCA parameter set. For example, the first station uses the EDCA parameter set in the beacon frame as its MU EDCA parameter set to be adopted, and the first station determines the duration of channel contention 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 from the beacon frame as its MU EDCA parameter set may involve setting the values ​​of the ACI / AIFSN and ECWmin / ECWmax fields corresponding to each AC in the EDCAParameter Set to the corresponding ACI / AIFSN and ECWmin / ECWmax fields in the MU EDCAParameter Set. Determining the duration of channel contention using the EDCA parameter set based on the MU EDCA timer in the MU EDCA parameter set may involve setting the value of the MU EDCA Timer field corresponding to each AC in the MU EDCAParameter Set used by the first station to the corresponding MU EDCA Timer field. For example, after the first station receives a trigger frame and successfully transmits a data frame, it uses the parameters from the EDCA parameter set in the beacon frame for a period of time to compete for EDCA channel contention; the length of this period is carried in the MU EDCA parameter set in the beacon frame. For example, after the second station receives the trigger frame and successfully sends the data frame, it will use the parameters in the EDCA parameter set on the link where the second station is located to compete for the EDCA channel for a period of time. The length of this period of time is carried in the MU EDCA parameter set on the link where the second station is located.

[0271] Figure 14 The embodiments described in the method flow are as follows Figure 8 , Figure 10 , Figure 11 , Figure 12 as well as Figure 13 Compared to the embodiments described in the method flow description, neither the request frame nor the response frame needs to carry the MU EDCA parameter set, which can reduce the amount of data sent. Furthermore, by determining the MU EDCA parameter set used by the first station based on the EDCA parameter set carried in the beacon frame, parameters with higher channel access priority can be obtained.

[0272] The following describes the communication device provided in the embodiments of this application.

[0273] This application divides the communication device into functional modules according to the above-described method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and represents only one logical functional division; other division methods may be used in actual implementation. The following will combine... Figures 15 to 17 The communication device of the present application embodiment is described in detail.

[0274] Figure 15 This is a schematic diagram of a communication device 1500 provided in an embodiment of this application. The communication device 1500 can correspondingly implement the functions or steps implemented by the communication device (e.g., a first station and an access point) in the various method embodiments described above. The communication device may include a processing module 1510 and a transceiver module 1520. Optionally, it may also include a storage unit, which can be used to store instructions (code or program) and / or data. The processing module 1510 and the transceiver module 1520 can be coupled to the storage unit. For example, the processing module 1510 can read the instructions (code or program) and / or data from the storage unit to implement the corresponding method. The various units described above can be set independently, or partially or completely integrated. For example, the transceiver module 1520 may include a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The entity corresponding to the transceiver module 1520 can be a transceiver.

[0275] In some possible implementations, the communication device 1500 can correspondingly implement the behavior and functions of the first station in the above method embodiments. For example, the communication device 1500 can be the first station, or it can be a component (e.g., a chip or circuit) applied in the first station. The transceiver module 1520 can, for example, be used to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 13 as well as Figure 14 In the embodiments, all receive or send operations performed by the first station, for example Figure 8Steps 801 and 802 in the illustrated embodiment, Figure 10 Steps 1001 and 1002 in the illustrated embodiment, Figure 11 Steps 1101 and 1102 in the illustrated embodiment, Figure 12 Steps 1201, 1202, and 1203 in the illustrated embodiment are as follows: Figure 13 Steps 1301 and 1302 in the illustrated embodiment, Figure 14 Steps 1401 and 1402 in the illustrated embodiments, and / or other processes used to support the techniques described herein. Processing module 1510 is used to execute... Figure 10 , Figure 11 , Figure 12 , Figure 13 as well as Figure 14 In the embodiment, all operations performed by the first station other than sending and receiving operations, such as Figure 10 Step 1003 in the illustrated embodiment, Figure 11 Step 1103 in the illustrated embodiment, Figure 12 Step 1204 in the illustrated embodiment, Figure 13 Step 1303 in the illustrated embodiment, Figure 14 Step 1403 in the illustrated embodiment.

[0276] In some possible implementations, the communication device 1500 can correspondingly implement the behavior and functions of the access point in the above method embodiments. For example, the communication device 1500 can be an access point or a component (e.g., a chip or circuit) applied in the access point. The transceiver module 1520 can, for example, be used to perform... Figure 8 , Figure 10 , Figure 11 , Figure 12 , Figure 13 as well as Figure 14 In the embodiments, all receive or send operations performed by the access point, for example Figure 8 Steps 801 and 802 in the illustrated embodiment, Figure 10 Steps 1001 and 1002 in the illustrated embodiment, Figure 11 Steps 1101 and 1102 in the illustrated embodiment, Figure 12 Steps 1201 and 1202 in the illustrated embodiment, Figure 13 Steps 1301 and 1302 in the illustrated embodiment, Figure 14 Steps 1401 and 1402 in the illustrated embodiments, and / or other processes used to support the techniques described herein. Processing module 1510 is used to execute... Figure 11 In this embodiment, all operations performed by the access point except for sending and receiving operations are considered. Figure 11 Step 1102 of the embodiment shown.

[0277] The first site and access point of this application embodiment have been described above. The following describes the possible product forms of the first site and access point. It should be understood that any product possessing the above-described features... Figure 15 Any product in any form that possesses the functions of the first site, or anything that has the above-mentioned features. Figure 15 Any form of product that provides the functionality of the access point falls within the protection scope of this application's embodiments. It should also be understood that the following description is merely illustrative and does not limit the product form of the first site and access point in this application's embodiments to this specific form.

[0278] In one possible implementation, Figure 15 In the communication device shown, the processing module 1510 can be one or more processors, and the transceiver module 1520 can be a transceiver, or the transceiver module 1520 can also be a transmitting unit and a receiving unit. The transmitting unit can be a transmitter, and the receiving unit can be a receiver. The transmitting unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver can be coupled, etc. The connection method between the processor and the transceiver is not limited in the embodiments of this application.

[0279] Figure 16 A schematic diagram of another communication device 160 provided in an embodiment of this application. Figure 16 The communication device mentioned above can be either the first station or the access point.

[0280] like Figure 16 As shown, the communication device 160 includes one or more processors 1620 and transceivers 1610. The transceiver 1610 can implement the functions of the transceiver module 1520, and the processor 1620 can implement the functions of the processing module 1510.

[0281] exist Figure 16 In various implementations of the communication apparatus shown, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0282] Optionally, the communication device 160 may further include one or more memories 1630 for storing program instructions and / or data. The memories 1630 are coupled to the processor 1620. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1620 may operate in conjunction with the memories 1630. The processor 1620 may execute program instructions stored in the memories 1630.

[0283] This application embodiment does not limit the specific connection medium between the transceiver 1610, processor 1620, and memory 1630. This application embodiment... Figure 16 The memory 1630, processor 1620, and transceiver 1610 are connected via a bus 1640. Figure 16 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 16 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0284] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0285] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code in the form of instructions or data structures, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0286] The processor 1620 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. The memory 1630 is primarily used for storing software programs and data. The transceiver 1610 may include control circuitry and an antenna. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

[0287] When the communication device is powered on, the processor 1620 can read the software program in the 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 outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF 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.

[0288] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0289] It is understood that the communication device shown in the embodiments of this application may also have more than Figure 16This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver shown above are merely examples; the specific steps performed by the processor and transceiver can be found in the methods described above.

[0290] In another possible implementation, Figure 15 In the communication device shown, the processing module 1510 can be one or more logic circuits, and the transceiver module 1520 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 1520 can also be a transmitting unit and a receiving unit; the transmitting unit can be an output interface, and the receiving unit can be an input interface, integrated into one unit, such as an input / output interface. Figure 17 As shown, Figure 17 The communication device shown includes logic circuit 1701 and interface 1702. That is, the processing module 1510 can be implemented using logic circuit 1701, and the transceiver module 1520 can be implemented using interface 1702. The logic circuit 1701 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 1702 can be a communication interface, input / output interface, pins, etc. For example, Figure 17 Taking the aforementioned communication device as an example, the chip includes a logic circuit 1701 and an interface 1702.

[0291] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment.

[0292] For example, when the communication device is used to perform the method, function or step performed by the first station described above, logic circuit 1701 is used to generate a request frame; interface 1702 is used to output the request frame.

[0293] For example, when the communication device is used to perform the method, function or step performed by the access point described above, interface 1702 is used to input a request frame; logic circuit 1701 is used to generate a response frame according to the request frame; and interface 1702 is used to output the response frame.

[0294] It is understood that the communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form or in software form, etc., and the embodiments of this application do not limit it in this way.

[0295] This application also provides a wireless communication system, which includes a first station and an access point. The first station and the access point can be used to perform any of the foregoing embodiments (such as...). Figure 8 , Figures 10 to 14 The method in ).

[0296] In addition, this application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by the first site in the method provided in this application.

[0297] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by the access point in the method provided in this application.

[0298] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by a first site in the method provided in this application to be executed.

[0299] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by an access point in the method provided in this application to be executed.

[0300] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0301] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0302] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0303] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0304] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive a request frame from a first site, which is an Emergency Communication Service (EPCS) site or a site in an EPCS Non-Access Point Multilink Device (non-AP MLD). A response frame is sent to the first station in response to the request frame. The response frame carries a third parameter set, which includes the Multi-User MU Enhanced Distributed Channel Access (EDCA) parameters that the first station needs to use for channel contention.

2. The method according to claim 1, characterized in that, The response frame also carries a fourth parameter set, which includes the MU EDCA parameters to be used by the second site in channel contention. The second site and the first site belong to the same multi-link site device.

3. The method according to claim 1 or 2, characterized in that, The third parameter set is included in the MLE field of the Priority Access Multi-Link Element.

4. The method according to claim 1 or 2, characterized in that, The third parameter set is included in the link information field of the priority access MLE field.

5. A communication method, characterized in that, include: Send a request frame to the access point; The system receives a response frame sent by the access point in response to the request frame. The response frame carries a third parameter set, which includes the Multi-User MU Enhanced Distributed Channel Access (EDCA) parameters to be used by the first site in channel contention. The first site is either an Emergency Communication Service (EPCS) site or a site in the EPCS Non-Access Point Multi-Link Device (non-AP MLD).

6. The method according to claim 5, characterized in that, The response frame also carries a fourth parameter set, which includes the MU EDCA parameters to be used by the second site in channel contention. The second site and the first site belong to the same multi-link site device.

7. The method according to claim 5 or 6, characterized in that, The method further includes: After sending a data frame triggered by the access point's trigger frame, channel contention is performed using parameters from the third parameter set.

8. The method according to claim 5 or 6, characterized in that, The third parameter set is included in the MLE field of the Priority Access Multi-Link Element.

9. The method according to claim 5 or 6, characterized in that, The third parameter set is included in the link information field of the priority access MLE field.

10. A communication device, characterized in that, include: The transceiver module is used to receive request frames from a first site, which is an Emergency Communication Service (EPCS) site or a site in the EPCS Non-Access Point Multilink Device (non-AP MLD). A processing module is used to generate a response frame for the request frame; The transceiver module is further configured to send a response frame to the first station in response to the request frame. The response frame carries a third parameter set, which includes the Multi-User MU Enhanced Distributed Channel Access (EDCA) parameters to be used by the first station for channel contention.

11. The apparatus according to claim 10, characterized in that, The response frame also carries a fourth parameter set, which includes the MU EDCA parameters to be used by the second site in channel contention. The second site and the first site belong to the same multi-link site device.

12. The apparatus according to claim 10 or 11, characterized in that, The third parameter set is included in the MLE field of the Priority Access Multi-Link Element.

13. The apparatus according to claim 10 or 11, characterized in that, The third parameter set is included in the link information field of the priority access MLE field.

14. A communication device, characterized in that, include: The processing module generates a request frame; The transceiver module is used to send the request frame to the access point; The system receives a response frame sent by the access point in response to the request frame. The response frame carries a third parameter set, which includes the Multi-User MU Enhanced Distributed Channel Access (EDCA) parameters to be used by the first site in channel contention. The first site is either an Emergency Communication Service (EPCS) site or a site in the EPCS Non-Access Point Multi-Link Device (non-AP MLD).

15. The apparatus according to claim 14, characterized in that, The response frame also carries a fourth parameter set, which includes the MU EDCA parameters to be used by the second site in channel contention. The second site and the first site belong to the same multi-link site device.

16. The apparatus according to claim 14 or 15, characterized in that, The processing module is further configured to perform channel contention using parameters from the third parameter set after sending a data frame triggered by the trigger frame of the access point.

17. The apparatus according to claim 14 or 15, characterized in that, The third parameter set is included in the MLE field of the Priority Access Multi-Link Element.

18. The apparatus according to claim 14 or 15, characterized in that, The third parameter set is included in the link information field of the priority access MLE field.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 9.

20. A communication device, characterized in that, Including processor and memory, The memory is used to store computer programs or instructions; The processor is configured to execute a computer program or instructions in memory such that the method described in any one of claims 1-9 is performed.

21. A chip, characterized in that, include: A communication interface is used for signal transmission and reception of the chip. as well as A processor for executing computer program instructions, causing a communication device including the chip to perform the method as described in any one of claims 1 to 9.

Images