Communication method and apparatus based on link adaptation

Abstract

The present application relates to the technical field of communications, and particularly relates to a communication method and apparatus based on link adaptation. For example, the present application can be applied to the IEEE 802.11ax standard, the 802.11be standard, the 802.11bn standard, and other standards of the IEEE 802.11 series, such as the 802.15 standard, the 802.11bf standard, the IMMW standard or the SparkLink standard. In the method, an MFB response or an unsolicited MFB may comprise a control information field, which may comprise information used for indicating whether a modulation type is an UEQM or an EQM, or comprise information used for indicating whether an RU type is a DRU or an RRU. Alternatively, a control information field in an MFB request may also comprise the above information. The addition of the above information to the control information field makes it possible to better adapt to link adaptation under a new standard.

Description

Link-adaptive communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202410940413.1, filed on July 12, 2024, entitled "Communication Method and Apparatus Based on Link Adaptation", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus based on link adaptation (LA). Background Technology

[0003] In wireless communication, channel conditions typically change over time. Wireless channels are affected by factors such as path loss, shadowing, fading, noise, and interference. For the transmitting end of a wireless communication system, different modulation and coding schemes (MCS) can be selected based on the varying channel conditions to achieve a trade-off between a certain probability of successful transmission and a high transmission rate, thereby improving the overall system throughput.

[0004] To select a suitable Modulation-Coding Scheme (MCS), the transmitter needs a certain understanding of the channel conditions, such as the signal-to-noise ratio (SNR) or signal-to-interference-plus-noise ratio (SINR). Therefore, the transmitter can obtain some channel parameters, such as SNR, through a probe-feedback process. After channel probing, the receiver can suggest the MCS, number of spatial streams (NSTS), or number of spatial streams (NSS) to the transmitter. This process of adjusting the transmitter's MCS through modulation and coding scheme feedback (MFB) from the receiver is a typical example of link adaptive technology.

[0005] As standards have evolved, channel parameter requirements have changed. Therefore, how to achieve link adaptation under the new standards urgently needs to be addressed. Summary of the Invention

[0006] This application provides a link-adaptive communication method and apparatus, which improves the content of link-adaptive information, thereby realizing link adaptation under the new standard.

[0007] In a first aspect, embodiments of this application provide a link-adaptive communication method. This method can be applied to a first site, which may include a wireless local area network (WLAN) device (including Wi-Fi devices, etc.), or a chip, functional module, processing system, or communication component disposed within the WLAN device. The method includes:

[0008] The first station generates a first radio frame, which includes a first control information field. The first control information field includes first information, which is used to indicate whether the modulation type recommended by the first station is unequal modulation (UEQM) or equal modulation (EQM). The first control information field is used to carry link adaptation information. The first station then transmits the first radio frame.

[0009] The first control information field includes first information. Considering the function of this first control information field (which carries link adaptive information), it can also be understood that the link adaptive information includes the first information. The explanation of the first information and the link adaptive information also applies to the other information shown below, and will not be elaborated further.

[0010] In this embodiment, the first station indicates its recommended modulation type, thereby allowing the second station to use a wider variety of modulation types, which can better match channel conditions. Simultaneously, by adding first information to the first control information field, it can better adapt to next-generation standards, such as Ultra High Reliability (UHR) (or 8021.bn standard), achieving link adaptation under the new standard.

[0011] In conjunction with the first aspect, in one possible implementation, the method further includes:

[0012] The first station receives the second radio frame, which is a request frame in a request-based MFB.

[0013] Secondly, embodiments of this application provide a link-adaptive communication method. This method can be applied to a second site, which may include a WLAN device (including a Wi-Fi device, etc.), or a chip, functional module, processing system, or communication component disposed within the WLAN device. The method includes:

[0014] The second station receives the first radio frame, which includes a first control information field. The first control information field includes first information, which is used to indicate whether the modulation type recommended by the first station is UEQM or EQM. The first control information field is used to carry link adaptation information. The second station parses the first radio frame.

[0015] In conjunction with the second aspect, in one possible implementation, the method further includes:

[0016] The second station sends a second radio frame, which is a request frame in a request-based MFB.

[0017] In conjunction with the first or second aspect, in one possible implementation, the first control information field further includes first NSS information;

[0018] When the modulation type indicated by the first information is EQM, the first NSS information is used to indicate the number of spatial streams (NSS) recommended by the first site; or, when the modulation type indicated by the first information is UEQM, the first NSS information is used to indicate the NSS recommended by the first site, and the MCS corresponding to each SS in the spatial streams (SS) recommended by the first site.

[0019] For example, the MCS corresponding to each SS in the SS recommended by the first site includes the difference between the MCS corresponding to the first SS and the MCS corresponding to the base SS. The first SS is the SS other than the base SS in the SS recommended by the first site. The difference between MCSs may include the difference between quadrature amplitude modulation (QAM).

[0020] In this embodiment, the first information and the first NSS information can be implemented using different fields; that is, the first information and the first NSS information can be carried in different fields. The first NSS information can be implemented using one field or two fields.

[0021] In conjunction with the first or second aspect, in one possible implementation, the first information is further used to indicate the NSS recommended by the first site; or, the first information is further used to indicate the NSS recommended by the first site, and the difference between the MCS corresponding to the first SS and the MCS corresponding to the base SS, wherein the first SS is an SS other than the base SS among the SSs recommended by the first site.

[0022] In this embodiment of the application, the content indicated by the first information can be implemented by one field, two fields, or three fields, etc.

[0023] In conjunction with the first or second aspect, in one possible implementation, the first control information field further includes MCS information, which is used to indicate the MCS corresponding to the first SS, or the MCS information is used to indicate the MCS corresponding to the base SS.

[0024] In this embodiment of the application, the MCS information may include an index of the MCS, and the index may correspond to an MCS.

[0025] In conjunction with the first or second aspect, in one possible implementation, the first information is further used to indicate the SNR corresponding to each SS recommended by the first site; or, the first information is further used to indicate the difference between the SNR corresponding to the first SS and the SNR corresponding to the second SS, wherein the first SS and the second SS are SSs recommended by the first site.

[0026] In conjunction with the first or second aspect, in one possible implementation, the first information is further used to indicate the difference between the SNR of the first frequency domain resource and the SNR of the second frequency domain resource, wherein the first and second frequency domain resources are frequency domain resources corresponding to the physical (PHY) layer protocol data unit (PPDU) used for measurement.

[0027] In conjunction with the first or second aspect, in one possible implementation, the first information is also used to indicate whether the PPDU used for measurement employs beamforming (BF).

[0028] In conjunction with the first or second aspect, in one possible implementation, the first control information field further includes first resource unit (RU) type information, which is used to indicate whether the RU type recommended by the first site is a distributed resource unit (DRU) or a regular resource unit (RRU).

[0029] In conjunction with the first or second aspect, in one possible implementation, the first control information field further includes first RU size information, which is used to indicate the recommended RU size for the first site.

[0030] The RU type or RU size mentioned above can be the RU size or RU type corresponding to the PPDU used for measurement.

[0031] In conjunction with the first or second aspect, in one possible implementation, the first control information field is included in the first control field of the first radio frame, and the first control field further includes a control identifier (ID) field, which is used to indicate that the first control information field is used for Ultra-Reliable HR.

[0032] In this embodiment of the application, the control ID field can be used to indicate that the first control information field is used for UHR, or next-generation standards, etc.

[0033] In conjunction with the first or second aspect, in one possible implementation, the first control information field is included in the first control field of the first radio frame, and the first control field further includes a control ID field with a value of 2.

[0034] In the first control information field: the value of B0 is 0, the value of B24 is 1, and the values ​​of B0 and B24 are used to indicate that the first control information field is used for UHR; or, in the first control information field: the value of B0 is 1, the value of B22 is 1, the value of B25 is 1, and the values ​​of B0, B22, and B25 are used to indicate that the first control information field is used for UHR.

[0035] B0 can be the first bit in the first control information field, B24 can be the 25th bit in the first control information field, and so on. Of course, the first bit in the first control information field can also be represented by B1. The embodiments of this application do not limit the representation of the starting bit in a certain field.

[0036] In this embodiment of the application, the aforementioned bits can be used to indicate that the first control information field is used for UHR, or next-generation standards, etc.

[0037] In conjunction with the first or second aspect, in one possible implementation, the first control information field occupies 26 bits.

[0038] In conjunction with the first or second aspect, in one possible implementation, the first control information field further includes an LA variant field, which is used to indicate that the first control information field is used for UHR.

[0039] For example, the first control field, which includes a first control information field, can be included in a control response frame (CRF), an acknowledgment frame, or other frames. Carrying link adaptation information through a CRF or acknowledgment frame can accelerate the feedback speed of link adaptation, making it more timely.

[0040] In conjunction with the first or second aspect, in one possible implementation, the first control information field is included in the high throughput control (HTC) field of the first radio frame, the HTC field including a special control ID field, wherein if the value of the special control ID field is a special value, the first control information field is included in an extension portion of the HTC field.

[0041] In conjunction with the first or second aspect, in one possible implementation, the number of bits occupied by the first control information field is greater than or equal to 26.

[0042] In this embodiment, by carrying the first control field in the extended portion of the HTC field, the length of the first control information field is no longer limited to 26 bits, thus allowing for better design of various information. Of course, the length of the first control information field can also be 26 bits, thereby ensuring consistent field parsing and simplifying implementation complexity.

[0043] In conjunction with the first or second aspect, in one possible implementation, the second radio frame includes a second control information field, which includes at least one of the following:

[0044] The second control information field is used for UHR; the RU type of the requested MFB is DRU or RRU; the modulation type of the requested MFB is UEQM or EQM; the UEQM type of the requested MFB is SD UEQM or FD UEQM; the MCS corresponding to different spatial streams is requested, or the difference between the MCS corresponding to different spatial streams is requested; the SNR corresponding to each spatial stream in different spatial streams is requested, or the difference between the SNR corresponding to different spatial streams is requested; the SNR corresponding to different frequency domain resources is requested, or the difference between the SNR corresponding to different frequency domain resources is requested.

[0045] In this embodiment of the application, the first station can perform measurements based on the channel parameters in the second wireless frame, enabling the first station to perform targeted channel measurements and improve the communication efficiency between the sender and receiver.

[0046] Thirdly, embodiments of this application provide a link-adaptive communication method. This method can be applied to a second site, which may include a WLAN device (including a Wi-Fi device, etc.), or a chip, functional module, processing system, or communication component disposed within the WLAN device. The method includes:

[0047] The second station generates a second radio frame, which includes a second control information field. The second control information field includes second information, which is used to indicate whether the modulation type requested by the second station is UEQM or EQM. The second control information field is used to request link adaptation information. The second station then transmits the second radio frame.

[0048] The modulation type requested by the second station can also be referred to as the modulation type requested by the second station from the first station, or the modulation type requested by the second station from the first station in the MFB. For example, if the modulation type is UEQM, then the MFB sent by the first station is the MFB used for UEQM transmission, or the MFB returned during UEQM transmission. Similarly, if the modulation type is EQM, then the MFB sent by the first station is the MFB used for EQM transmission, or the MFB returned during EQM transmission.

[0049] In this embodiment, by sending a second radio frame to the first station, the second station can effectively obtain the channel parameters it needs to measure, thereby enabling the first station to send an MFB (Multi-Functional Broadcast) to the first station in conjunction with the second radio frame, thus improving communication efficiency. Simultaneously, by adding second information to the second control information field, it can better adapt to next-generation standards, such as UHR (or the 8021.bn standard).

[0050] Fourthly, embodiments of this application provide a link-adaptive communication method. This method can be applied to a first site, which may include a wireless local area network (WLAN) device (including Wi-Fi devices, etc.), or a chip, functional module, processing system, or communication component that may be configured within the WLAN device. The method includes:

[0051] The first station receives a second radio frame, which includes a second control information field. The second control information field includes second information, which is used to indicate whether the modulation type requested by the second station is UEQM or EQM. The second control information field is used to request link adaptation information. The first station parses the second radio frame.

[0052] The first station can effectively determine the type of information carried in its MFB response by parsing the second radio frame. For example, for a non-requesting MFB, the link adaptation information can be estimated based on the most recently received PPDU, and the non-requesting MFB response can indicate the corresponding parameters of that PPDU. Similarly, for a requesting MFB, the link adaptation information can be measured based on the PPDU carrying the MFB request. The aforementioned second radio frame can also be called an MFB request. The first radio frame shown above can also be called an MFB response. The beneficial effects of the fourth aspect can be referred to in the third aspect, and will not be elaborated here.

[0053] In conjunction with the third or fourth aspect, in one possible implementation, the second information is also used to indicate that the type of UEQM requested by the second site is spatial stream domain (SD) UEQM (or spatial domain UEQM) or frequency domain (FD) UEQM.

[0054] If the UEQM type is SD UEQM, the MFB sent by the first station is either the MFB measured during SD UEQM transmission or the MFB fed back during SD UEQM transmission. For example, the first station can perform measurements based on the PPDU carrying the MFB request, and determine the MCS of each spatial stream for the UEQM transmission recommended by the first station by estimating the SNR of each spatial stream. Similarly, if the UEQM type is FD UEQM, the MFB sent by the first station is either the MFB measured during FD UEQM transmission or the MFB fed back during FD UEQM transmission. For example, a description of the MFB sent by the first station can be referenced to the first radio frame shown in the first or second aspect above.

[0055] In this embodiment of the application, the indication function of the second information can be implemented by one field, two fields, or even three fields.

[0056] In conjunction with the third or fourth aspect, in one possible implementation, the second information is also used to request whether the PPDU used for measurement employs beamforming (BF).

[0057] In this embodiment, the second information can be used to indicate the modulation type and whether the PPDU used for measurement employs BF. The function of this second information can be implemented using one field (e.g., two bits), or two fields (each field occupying one bit), etc. This description also applies to other functions to be implemented by the second information.

[0058] In conjunction with the third or fourth aspect, in one possible implementation, the second control information field further includes second NSS information, which is used to indicate the NSS requested by the second site.

[0059] In this embodiment, the second station indicates second NSS information to the first station, enabling the first station to perform measurements using the NSS indicated by the second NSS information. In other words, the MFB (Mean Factor Buffer) can be obtained based on the NSS indicated by the second NSS information. Thus, the sending and receiving parties can agree on the NSS, improving communication efficiency.

[0060] In conjunction with the third or fourth aspect, in one possible implementation, the second control information field further includes second RU size information, which is used to indicate the RU size requested by the second site.

[0061] In conjunction with the third or fourth aspect, in one possible implementation, the second control information field further includes second RU type information, which indicates that the RU type requested by the second site is a Discrete Resource Unit (DRU) or a Conventional Resource Unit (RRU).

[0062] If the RU type is DRU, the MFB sent by the first station is either the MFB measured during DRU transmission or the MFB fed back during DRU transmission. Similarly, if the RU type is RRU, the MFB sent by the first station is either the MFB measured during RRU transmission or the MFB fed back during RRU transmission.

[0063] In conjunction with the third or fourth aspect, in one possible implementation, the second information is also used to indicate at least one of the following:

[0064] Instructions to retrieve the MCS corresponding to each spatial flow in different spatial flows, or the differences between the MCS corresponding to different spatial flows;

[0065] Instructions to retrieve the SNR corresponding to each spatial flow in different spatial flows, or the differences between the SNRs corresponding to different spatial flows;

[0066] This instruction requests the SNR corresponding to each frequency domain resource in different frequency domains, or the difference between the SNRs corresponding to different frequency domain resources.

[0067] For example, in the case of modulation type UEQM, the second information can also be used to indicate the above content. Thus, the first station can send the MFB in conjunction with the above content.

[0068] In conjunction with the third or fourth aspect, in one possible implementation, the second control information field is included in the second control field of the second radio frame, and the second control field also includes a control ID field, which is used to indicate that the second control information field is used for Ultra-Reliable HR (UHR).

[0069] In conjunction with the third or fourth aspect, in one possible implementation, the second control information field is included in the second control field of the second radio frame, and the second control field also includes a control ID field with a value of 2.

[0070] In the second control information field: the value of B0 is 0, and the value of B24 is 1. The values ​​of B0 and B24 are used to indicate that the second control information field is used for UHR; or, in the second control information field: the value of B0 is 1, the value of B22 is 1, and the value of B25 is 1. The values ​​of B0, B22, and B25 are used to indicate that the second control information field is used for UHR.

[0071] In conjunction with the third or fourth aspect, in one possible implementation, the second control information field also includes an LA variant field, which is used to indicate that the second control information field is used for UHR.

[0072] In conjunction with the third or fourth aspect, in one possible implementation, the first control information field is included in the high throughput control (HTC) field in the first radio frame, the HTC field including a special control ID field, and if the value of the special control ID field is a special value, the first control information field is included in an extension portion of the HTC field.

[0073] For explanations regarding the control ID field or the second control field, please refer to the first or second aspect; they will not be elaborated upon here.

[0074] Fifthly, embodiments of this application provide a link-adaptive communication method. This method can be applied to a first site, which may include a WLAN device (including a Wi-Fi device, etc.), or a chip, functional module, processing system, or communication component disposed within the WLAN device. The method includes:

[0075] The first station generates a first radio frame, which includes a first control information field. The first control information field includes RU type information, which indicates whether the recommended RU type is DRU or RRU. The first control information field is used to carry link adaptation information. The first station then transmits the first radio frame.

[0076] In this embodiment of the application, by adding RU type information to the first control information field, the first control information field can be adapted to UHR or next-generation standards, thereby achieving link adaptation under the new standard.

[0077] Sixthly, embodiments of this application provide a link-adaptive communication method. This method can be applied to a second site, which may include a WLAN device (including a Wi-Fi device, etc.), or a chip, functional module, processing system, or communication component disposed within the WLAN device. The method includes:

[0078] The second station receives a first radio frame, which includes a first control information field. The first control information field includes resource unit (RU) type information, which indicates that the first station recommends either a discrete resource unit (DRU) or a conventional resource unit (RRU). The first control information field is used to carry link adaptation information. The second station parses the first radio frame.

[0079] In conjunction with the fifth or sixth aspect, in one possible implementation, the first control information field is included in a first control field in the first radio frame, the first control field further including a control ID field, the control ID field being used to indicate that the first control information field is used for UHR.

[0080] In conjunction with the fifth or sixth aspect, in one possible implementation, the first control information field is included in the first control field of the first radio frame, and the first control field further includes a control ID field with a value of 2.

[0081] In the first control information field: the value of B0 is 0, the value of B24 is 1, and the values ​​of B0 and B24 are used to indicate that the first control information field is used for UHR; or, in the first control information field: the value of B0 is 1, the value of B22 is 1, the value of B25 is 1, and the values ​​of B0, B22, and B25 are used to indicate that the first control information field is used for UHR.

[0082] In conjunction with the fifth or sixth aspect, in one possible implementation, the first control information field occupies 26 bits.

[0083] In conjunction with the fifth or sixth aspect, in one possible implementation, the first control information field further includes an LA variant field, which is used to indicate that the first control information field is used for UHR.

[0084] In conjunction with the fifth or sixth aspect, in one possible implementation, the first control information field is included in the high throughput control (HTC) field in the first radio frame, the HTC field including a special control ID field, wherein if the value of the special control ID field is a special value, the first control information field is included in an extension portion of the HTC field.

[0085] In conjunction with the fifth or sixth aspect, in one possible implementation, the number of bits occupied by the first control information field is greater than or equal to 26.

[0086] In a seventh aspect, embodiments of this application provide a communication device for executing the methods in any one of the first to sixth aspects or any possible implementations thereof. The first communication device includes a module having the capability to execute the methods in any one of the first to sixth aspects or any possible implementations thereof.

[0087] Eighthly, embodiments of this application provide a communication device including a processor for executing the methods shown in any one of the first to sixth aspects or any possible implementations thereof. The processor executes a program stored in a memory, and when the program is executed, the methods shown in any one of the first to sixth aspects or any possible implementations thereof are executed.

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

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

[0090] In this embodiment, the processor and memory can also be integrated into a single device, that is, the processor and memory can be integrated together. For example, the communication device can be a chip.

[0091] In one possible implementation, the communication device further includes a transceiver for receiving or sending information.

[0092] Ninthly, embodiments of this application provide a communication device, the communication device including a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used for inputting and / or outputting information, and the logic circuit is used for performing the method described in any one of the first to sixth aspects or any possible implementation thereof.

[0093] In a tenth 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 any of the first to sixth aspects or any possible implementation thereof to be executed.

[0094] In one aspect, embodiments of this application provide a computer program product that, when run on a computer, causes the methods shown in any of the first to sixth aspects or any possible implementations above to be executed.

[0095] In a twelfth aspect, embodiments of this application provide a communication system including a first station and a second station. The first station is used to perform the method shown in the first aspect or any possible implementation thereof, and the second station is used to perform the method shown in the second aspect or any possible implementation thereof.

[0096] In a thirteenth aspect, embodiments of this application provide a communication system including a first station and a second station. The first station is used to perform the method shown in the fourth aspect or any possible implementation thereof, and the second station is used to perform the method shown in the third aspect or any possible implementation thereof.

[0097] In a fourteenth aspect, embodiments of this application provide a communication system including a first station and a second station. The first station is used to perform the method shown in the fifth aspect or any possible implementation thereof, and the second station is used to perform the method shown in the sixth aspect or any possible implementation thereof. Attached Figure Description

[0098] Figure 1 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0099] Figure 2a is a schematic diagram of a medium access control (MAC) frame format provided in an embodiment of this application;

[0100] Figure 2b is a schematic diagram of the format of the aggregated control (A-control) field provided in an embodiment of this application;

[0101] Figure 3a is a flowchart illustrating the request-based MFB provided in an embodiment of this application;

[0102] Figure 3b is a flowchart illustrating the non-requested MFB provided in an embodiment of this application;

[0103] Figure 4 is a schematic diagram of a format of the control field provided in an embodiment of this application;

[0104] Figure 5 is a schematic diagram of another format of the control field provided in an embodiment of this application;

[0105] Figure 6a is a flowchart illustrating a link-adaptive communication method provided in an embodiment of this application;

[0106] Figure 6b is another flowchart illustrating the link-adaptive communication method provided in an embodiment of this application;

[0107] Figure 7 is a schematic diagram of the format of the control field provided in an embodiment of this application;

[0108] Figure 8a is a schematic diagram of a format of a control field provided in an embodiment of this application;

[0109] Figure 8b is a schematic diagram of the format of the control field in the second wireless frame provided in an embodiment of this application;

[0110] Figure 8c is a schematic diagram of the format of the control field in the first wireless frame provided in an embodiment of this application;

[0111] Figure 9 is a schematic diagram of another format of the control field provided in an embodiment of this application;

[0112] Figure 10 is a schematic diagram of another format of the control field provided in an embodiment of this application;

[0113] Figure 11a is a schematic diagram of another format of the control field provided in an embodiment of this application;

[0114] Figure 11b is a schematic diagram of another format of the control field provided in an embodiment of this application;

[0115] Figures 12a and 12b are schematic diagrams of the format of the confirmation frame provided in the embodiments of this application;

[0116] Figure 12c is a schematic diagram of the format of a block acknowledgment request (BAR) frame provided in an embodiment of this application;

[0117] Figure 13a is a schematic diagram of a format of the HTC field provided in an embodiment of this application;

[0118] Figure 13b is a schematic diagram of another format of the HTC field provided in an embodiment of this application;

[0119] Figure 14 is a schematic diagram of a communication device provided in an embodiment of this application;

[0120] Figure 15 is a schematic diagram of another structure of the communication device provided in an embodiment of this application;

[0121] Figure 16 is a schematic diagram of another structure of the communication device provided in the embodiments of this application. Detailed Implementation

[0122] To facilitate understanding of the technical solution of this application, the application will be further described below with reference to the accompanying drawings.

[0123] 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.

[0124] 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.

[0125] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. "Or" indicates that there can be two relationships, such as only A exists and only B exists; when A and B are not mutually exclusive, it can also mean that there are three relationships, such as only A exists, only B exists, and both A and B exist simultaneously. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0126] In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0127] In this application, the information indicated by the instruction information is called the instruction information. The information used to indicate a certain piece of information, as shown below, can all be called instruction information. In specific implementations, there are many ways to indicate the instruction information, such as, but not limited to, directly indicating the instruction information itself or its index. It can also indirectly indicate the instruction information by indicating other information, where there is a correlation between the other information and the instruction information. It can also indicate only a part of the instruction information, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the instruction information can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0128] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which can include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which can include direct reception from YY via the air interface or indirect reception from YY via the air interface from other units or modules. "Send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via buses, traces, or interfaces.

[0129] This application provides a link-adaptive communication method and apparatus, which can be adapted to the UHR standard or next-generation standard, and effectively realizes link adaptation under the new standard.

[0130] The following describes the communication system involved in the embodiments of this application.

[0131] The technical solutions provided in this application can be applied to WLAN systems, such as Wi-Fi. For example, the technical solutions provided in this application can be applied to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series standards (or protocols), such as the 802.11be standard, the 802.11bn standard (or Wi-Fi 8, also known as ultra-high reliability (UHR) or ultra-high reliability and throughput (UHRT)), or next-generation standards of the 802.11bn standard, or standards supporting ambient power (AMP), etc., and will not be listed exhaustively. The technical solutions provided in this application can also be applied to wireless personal area networks (WPANs) based on millimeter wave (MMW) technologies, such as integrated millimeter wave (IMMW) and ultra-wideband (UWB) technologies. The technical solutions provided in the embodiments of this application can be applied to the IEEE 802.15 series standards, such as the 802.15.4a, 802.15.4z, or 802.15.4ab standards, or future UWB WPAN standards, etc., and will not be listed one by one. The technical solutions provided in the embodiments of this application can also be applied to the Spark Link or NearLink standards. The technical solutions provided in the embodiments of this application can also be applied to the following communication systems, such as Internet of Things (IoT) systems, vehicle-to-everything (V2X, where X can represent anything), device-to-device (D2D), narrowband Internet of Things (NB-IoT) systems, long term evolution (LTE) systems, 5th generation (5G) communication systems, and new communication systems that will emerge in the future development of communication, etc.For example, V2X can include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communication.

[0132] WLAN systems can provide high-speed, low-latency transmission. As WLAN application scenarios continue to evolve, WLAN systems will be applied to more scenarios or industries, such as the Internet of Things industry, the Internet of Vehicles industry, the banking industry, enterprise offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, shopping malls, squares, streets, production workshops and warehouses, etc. Of course, devices that support WLAN communication or sensing (such as access points or sites) can be sensor nodes in smart cities (such as smart water meters, smart electricity meters, and smart air monitoring nodes), smart devices in smart homes (such as smart cameras, projectors, displays, televisions, speakers, refrigerators, and washing machines), nodes in the Internet of Things (IoT), entertainment terminals (such as wearable devices for augmented reality (AR) and virtual reality (VR), smart devices in smart offices (such as printers, projectors, loudspeakers, and speakers), vehicle-to-everything (V2X) devices, infrastructure in daily life scenarios (such as vending machines, self-service navigation kiosks in supermarkets, self-service checkout machines, and self-service ordering machines), and equipment in large sports and music venues.

[0133] Although the embodiments of this application primarily use WLAN as an example, especially networks applied to the IEEE 802.11 series of standards, the various aspects involved in the embodiments of this application can be extended to other networks employing various standards or protocols. For example, Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard), and wide area networks (WANs) or other networks now known or to be developed in the future.

[0134] The method provided in this application embodiment can be implemented by a communication device in a communication system. For example, the communication device can be an access point (AP) or a station (STA). For example, access points and stations can be devices used in vehicle networks, IoT nodes and sensors in IoT, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities, etc. The following is a detailed description:

[0135] An Access Point (AP) is a device with wireless communication capabilities that supports communication, sensing, or power transmission using WLAN standards. It has the function of communicating or sensing with other devices in a WLAN network (such as non-access point stations (non-AP STAs) or other access points), and can also have the function of communicating, sensing, or transmitting power with other devices. Alternatively, an access point acts as a bridge connecting wired and wireless networks, primarily connecting various wireless network clients together and then connecting the wireless network to an Ethernet network. In a WLAN system, an access point can be called an Access Point Station (AP STA). This wireless communication device can be a complete device or a chip, processing system, or functional module installed within a complete device. Devices with these chips, processing systems, or functional modules can implement the methods and functions of the embodiments in this application under the control of the chips, processing systems, or functional modules. The AP in the embodiments of this application is a device that provides services to non-AP STAs and can support the 802.11 series standards or subsequent standards. For example, an access point can be an access point for a terminal (such as a mobile phone) to enter a wired (or wireless) network, mainly deployed in homes, buildings, and parks, with a typical coverage radius of tens to hundreds of meters. Of course, it can also be deployed outdoors. Another example is that an AP can be a communication entity such as a communication server, router, switch, or bridge; an AP can include various forms of macro base stations, micro base stations, and repeater stations. Yet another example is that an AP can be used to transmit power to an AMP STA. Of course, an AP can also be a chip, processing system, or module in the various types of devices mentioned above, thereby implementing the methods and functions of the embodiments of this application.

[0136] A Station-Style (STA) is a device with wireless communication capabilities that supports communication, sensing, or power transmission using WLAN standards. It has the ability to communicate, sense, or transmit power with other non-AP STAs or access points in a WLAN network. In a WLAN system, a station can be called a non-access point station (non-AP STA). For example, an STA is any user communication device that allows a user to communicate with an AP (Access Point) or sense or transmit power, and thus communicate with the WLAN. This wireless communication device can be a complete device, or it can be a chip, processing system, or functional module installed in a complete device. Devices with these chips, processing systems, or functional modules can implement the methods and functions of the embodiments of this application under the control of the chips, processing systems, or functional modules. For example, an STA can be a wireless communication chip, a wireless sensor, or a wireless communication terminal, and can also be referred to as a user. Furthermore, an STA can be a mobile phone supporting Wi-Fi communication, a tablet computer supporting Wi-Fi communication, a set-top box supporting Wi-Fi communication, a smart TV supporting Wi-Fi communication, a smart wearable device supporting Wi-Fi communication, an in-vehicle communication device supporting Wi-Fi communication, and a computer supporting Wi-Fi communication. Of course, STA can also be a chip, processing system, or module in the various types of devices described above, thereby implementing the methods and functions of the embodiments of this application.

[0137] Figure 1 is a schematic diagram of the communication system architecture provided in an embodiment of this application. As shown in Figure 1, the embodiments of this application can be applied to scenarios such as communication, sensing, or power transmission between APs and non-AP STAs, between APs, or between non-AP STAs in a WLAN, and the embodiments of this application do not limit this. For example, an AP can communicate, sense, or transmit power with a single non-AP STA, or an AP can communicate, sense, or transmit power with multiple non-AP STAs simultaneously. For example, communication, sensing, or power transmission between an AP and multiple non-AP STAs can be divided into downlink transmission where the AP simultaneously sends signals to multiple non-AP STAs, and uplink transmission where multiple non-AP STAs send signals to the AP.

[0138] As one possible implementation, AP1 can be an AP belonging to the AP MLD, or AP2 can be an AP belonging to the AP MLD. Non-AP STA1, non-AP STA2, or non-AP STA3 can be a non-AP STA belonging to the non-AP MLD. Communication standards can be supported between APs and non-AP STAs, between APs, and between non-AP STAs. These standards can include IEEE 802.11 series standards, such as 802.11bn, and also standards after 802.11bn.

[0139] Figure 1 uses a mobile phone as a non-AP STA and a router as an example, and does not imply a limitation on the types of APs and non-AP STAs in the embodiments of this application. Furthermore, the number of APs and non-AP STAs shown in Figure 1 is merely an example; in a specific implementation, the number of APs or non-AP STAs may be more or less, and this embodiment of the application does not limit this.

[0140] The following describes the nouns or terms used in the embodiments of this application.

[0141] 1. The relationship between bandwidth, NSTS (or NSS), and MCS

[0142] WLAN standards, starting with 802.11a / g, have evolved through 802.11n, 802.11ac, 802.11ax, 802.11be, and its next-generation standard, 802.11bn. The 802.11n standard is also known as high throughput (HT), the 802.11ac standard as very high throughput (VHT), the 802.11ax standard as high efficient (HE), the 802.11be standard as extremely high throughput (EHT), and the 802.11bn standard as UHR. Standards prior to HT, such as 802.11a / b / g, are collectively referred to as non-high throughput (Non-HT). 802.11b uses orthogonal frequency division multiplexing (OFDM) mode, therefore Table 1 does not show the bandwidth, NSTS, and MCS involved in the 802.11b standard.

[0143] Table 1 exemplarily illustrates the relationship between allowed transmission bandwidth, space-time stream count, and MCS. As standards evolve, other bandwidths, NSSs, or MCSs may emerge, and this application embodiment does not limit these. That is, the relationship between bandwidth, NSS, and MCS shown in Table 1 may change as standards evolve. Given that space-time coding is no longer considered starting with the 802.11be standard, space stream count can be considered starting with the 802.11be standard.

[0144] Table 1

[0145] 2. Medium Access Control (MAC) Frame

[0146] In WLAN, access points (APs) and non-AP stations (STAs) can transmit control signaling, management signaling, or data via MAC protocol data units (MPDUs). For example, an MPDU can be carried within the data field of a PPDU. This MPDU can also be called a MAC frame. For ease of description, the following explanation will use MAC frames as an example.

[0147] Figure 2a is a schematic diagram of a MAC frame format provided in an embodiment of this application. As shown in Figure 2a, a MAC frame may include a frame header, a frame body, and a frame check sequence (FCS). The frame header includes at least one of the following: frame control, duration / ID, address (A1), A2, A3, A4, sequence control, quality of service (QoS) control, or HT control (HTC). The frame body can be used to carry data or management or control information passed down from the upper layer. The frame check sequence can be used to verify whether the MAC frame is transmitted correctly. Figure 2a also exemplarily shows the length of each field. The embodiments of this application do not limit the length or order of each field.

[0148] The HTC field can be used to carry some control information. An efficient variant of the HTC field, the aggregated control (A-control) field, can include one or more control fields. A control field can include a control ID field and a control information field. The control field can be used to carry some control information corresponding to the control ID. The aforementioned efficient variants may include, but are not limited to, high-throughput variants, very high-throughput variants, or efficient variants.

[0149] Figure 2b is a schematic diagram of the format of the A-control field provided in an embodiment of this application. As shown in Figure 2b, an A-control field includes N control fields, where N is a positive integer. Optionally, the A-control field may also include a padding field. Each control field may include a control ID field and a control information field, where the control ID field can be used to indicate the type of control information. In other words, the type of information carried in the control information field can be determined by the control ID field (as shown in Figure 2b). Figure 2b also exemplarily shows the length of each field. The number of bits occupied by the control information field is variable.

[0150] The names, lengths, or positions of the frames, elements, or fields shown in the embodiments of this application are merely examples and are not intended to limit the embodiments of this application. The following examples all use fields as examples and do not specifically distinguish between fields, subfields, elements, or subelements, but this should not be considered a limitation on the embodiments of this application. The length of each field can be in bits, bytes, or double bytes; this application does not limit this. In the embodiments of this application, the fields shown by the dashed lines in the accompanying drawings are optional fields, and fields with a length of 0 can also be optional fields.

[0151] The following describes the methods involved in the embodiments of this application.

[0152] The MFBs involved in the embodiments of this application include non-requesting MFBs and requesting MFBs.

[0153] Figure 3a is a schematic flowchart of a request-based MFB provided in an embodiment of this application. As shown in Figure 3a, the MFB requester sends an MFB request, which can be used to request MFB feedback. The MFB responder receives the MFB request and measures relevant MFB parameters based on the PPDU carrying the MFB request. The MFB responder can then send an MFB response to the MFB requester, which can be used to respond to the MFB request. This MFB response can be a response obtained by measuring the relevant MFB parameters of the PPDU. The MFB response can carry link adaptation information (or link adaptation parameters, or MFB parameters), such as the measurement results of the aforementioned MFB parameters. After receiving the MFB response, the MFB requester can send a PPDU using the parameters recommended in the MFB response (such as recommended MCS parameters).

[0154] The specific product types of the MFB requester and MFB responder are not limited in this application. For example, both the MFB requester and MFB responder can be non-AP STAs. Alternatively, the MFB requester can be a non-AP STA, and the MFB responder can be an AP, etc., and these will not be listed here.

[0155] Figure 3b is a schematic flowchart of a non-requested MFB provided in an embodiment of this application. As shown in Figure 3b, the MFB responder can send a non-requested MFB. The MFB responder can estimate relevant MFB parameters based on the most recently received PPDU. The non-requested MFB can indicate the corresponding parameters of the aforementioned PPDU, such as, but not limited to, indications of PPDU type, encoding type, and transmitter beamforming. The aforementioned corresponding parameters can be the estimation results of the aforementioned MFB parameters.

[0156] For non-requested MFBs, there are two main approaches:

[0157] (1) As shown in Mode 1 of Figure 3b, after receiving the non-requested MFB, the receiver of the MFB can send a trigger frame to the responder of the MFB, and schedule the responder to perform uplink transmission through the trigger frame. For example, the receiver of the MFB can send the trigger frame using the parameters recommended by the non-requested MFB. After receiving the trigger frame, the responder of the MFB can send a trigger-based PPDU (TB PPDU). For example, in Mode 1, the receiver of the MFB can be an AP, and the responder of the MFB can be a non-AP STA.

[0158] (2) As shown in Method 2 of Figure 3b, after receiving the non-requested MFB, the receiver of the MFB can send a multi-user PPDU (MU PPDU) or a single-user PPDU (SU PPDU) using the parameters recommended by the non-requested MFB. The specific product types of the MFB responder and the MFB receiver are not limited in this embodiment.

[0159] The explanations regarding request-based MFBs and non-request-based MFBs provided here also apply to the following text, and will not be repeated here.

[0160] As one possible implementation, this application provides a link-adaptive communication method. The process involved in this method can be referred to Figures 3a and 3b, and the format of the control fields involved in this method can be referred to Figure 4.

[0161] Figure 4 is a schematic diagram of a control field format provided in an embodiment of this application. As shown in Figure 4, the control field may include at least one of the following: control ID, unsolicited MCS feedback (MBF), MCS request (MRQ), spatial stream number (NSS), high-efficiency MCS (HE-MCS), dual carrier modulation (DCM), resource unit allocation (RU allocation), bandwidth (BW), MCS feedback sequence identifier (MSI) or partial PPDU parameters (MSI / partial PPDU parameters), transmit beamforming (TxBF) or uplink high-efficiency trigger-based PPDU MCS feedback (UL HE TB PPDU MFB). Figure 4 also exemplarily shows the length of each field. The control ID field occupies 4 bits, and the control information field occupies 26 bits.

[0162] For example, the value of the control ID field is 2. The control information field carried in the same control field as the control ID field can be used for 802.11ax or HE link adaptation. The above control field can also be called a High-Efficiency Link Adaptation (HLA) control field. The specific names of each field are not limited in the embodiments of this application.

[0163] Table 2 illustrates the meaning and definition of each field, and the description of each field shown in Figure 4 can be found in Table 2.

[0164] Taking Table 2 as an example, in Figure 3a, the non-request MFB field in the MFB request can be 0 and the MRQ field can be 1. In Figure 3a, the non-request MFB field in the MFB response can be 0 and the MRQ field can be 0. In Figure 3b, the non-request MFB field can be 1. When the process shown in Figure 3b includes a trigger frame, the non-request MFB field can be 1 and the UL HE TB PPDU MFB field can be 0. When the process shown in Figure 3b includes a trigger frame, the non-request MFB field can be 1 and the UL HE TB PPDU MFB field can be 1.

[0165] Table 2

[0166] As another possible implementation, this application provides another link-adaptive communication method. The process involved in this method can be referred to Figures 3a and 3b, and the format of the control fields involved in this method can be referred to Figure 5.

[0167] Figure 5 is a schematic diagram of another format of the control field provided in an embodiment of this application. As shown in Figure 5, the control field may include at least one of the following: control ID, non-requested MFB, MRQ / UL EHT TB PPDU MFB, spatial stream number, EHT-MCS, resource unit allocation (RU allocation), primary / secondary (PS) 160, BW, MCS feedback sequence identifier (MRQ sequence identifier, MSI) or partial PPDU parameters (MSI / partial PPDU parameters), TxBF or HE / EHT indicator (or HLA / ELA indicator). Figure 5 also exemplarily shows the length of each field. The control ID field occupies 4 bits, and the control information field occupies 26 bits.

[0168] For example, the value of the control ID field is 2. The control information field carried in the same control field as the control ID field can be used for 802.11be or EHT link adaptation. The above control field can also be called an Extremely High Throughput Link Adaptation (EHT linkadaptation, ELA) control field. The specific names of each field are not limited in the embodiments of this application.

[0169] In the control information fields shown in Figure 5, B25 can serve as an indication of HLA or ELA. Compared to Figure 4, the BW field has been expanded from 2 bits to 3 bits, further supporting a bandwidth of 320MHz. The RU allocation field and PS160 field can be used to indicate RUs or multiple resource units (MRUs). The EHT-MCS field can implicitly indicate DCMs, thus saving one bit of the original DCM field. Simultaneously, the MRQ field and the UL EHT TB PPDU MFB field are combined into one. Furthermore, since the EHT PPDU includes two formats, when the non-requested MFB field is 1, the PPDU format field occupies 1 bit, leaving an additional reserved bit compared to Figure 4.

[0170] Table 3 illustrates the meaning and definition of some fields. For explanations of other fields not shown in Table 3, please refer to Table 2. They will not be repeated here.

[0171] Table 3

[0172] The methods described above do not consider the new features added by the new standard, such as the support for UEQM (as shown in Table 1) and DRU in the UHR standard. Therefore, this application provides another link-adaptive communication method. This method designs link adaptation for the new features added in the new standard. This method can better adapt to the new standard to support link adaptation for some or all of the features such as UEQM and DRU. The following is a detailed description.

[0173] Figure 6a is a flowchart illustrating a link-adaptive communication method provided in an embodiment of this application. The method shown in Figure 6a can be for a request-based MFB. The descriptions of the first and second stations in Figure 6a can be found in Figure 1 or Figure 3a above, and will not be detailed here. For example, the first station can also be called the MFB responder, and the second station can also be called the MFB requester. As shown in Figure 6a, the method includes:

[0174] In one possible implementation, the method shown in FIG6a may include step 601.

[0175] 601. The second station generates the second wireless frame.

[0176] For an explanation of the second wireless frame, please refer to step 602.

[0177] 602. The second station sends a second radio frame, and correspondingly, the first station receives the second radio frame. The second radio frame may include a second control information field, which is used for UHR link adaptation (ULA) and can be used to request link adaptation information.

[0178] In this embodiment, ULA is merely an example. The control information field can also be used in LAs of other subsequent standards, and this embodiment is not limiting. The aforementioned link adaptation information can also be called link adaptation parameters or MFB parameters.

[0179] For example, the non-requested MFB field in the second control information field can be 0, and the MRQ field can be 1. The MRQ field can be used to indicate whether the second radio frame is an MFB request. The MRQ field can also be called the MRQ / UL UHR TB PPDU MFB field, meaning this field can combine the following functions: indicating an MFB request or MFB response, or indicating whether it is an MFB of a UL TB PPDU. For a requested MFB, the MRQ / UL UHR TB PPDU MFB field can be used to indicate that the second radio frame is an MFB request.

[0180] The second control information field may be included within the second control field, which may also be referred to as the ULA field, etc. The name of the second control field may vary with changes in standards, and this application embodiment does not limit it. For example, the second radio frame may also be referred to as an MFB request, and this application embodiment does not limit the specific name of the second radio frame.

[0181] The second control field can be used to indicate at least one of the following:

[0182] (1A) The second control information field is used for ULA, or the second control information field is used for UHR, or the second control field is ULA;

[0183] (2A) The modulation type requested is UEQM or EQM;

[0184] (3A) The requested UEQM type is SD UEQM or FD UEQM;

[0185] (4A) Obtain the SNR corresponding to each flow in different spatial flows (or simply flows);

[0186] (5A) Obtain the MCS corresponding to each flow in different spatial flows;

[0187] (6A) Obtain the SNR corresponding to each frequency domain resource in different frequency domain resources;

[0188] (7A) Indicates that the type of RU requested is DRU or RRU.

[0189] For example, in (3A), if the UEQM type is SD UEQM, the MFB sent by the first station is either the MFB measured during SD UEQM transmission or the MFB fed back during SD UEQM transmission. For instance, the first station can perform measurements based on the PPDU carrying the MFB request, and determine the MCS of each spatial flow during the recommended UEQM transmission by estimating the SNR of each spatial flow. Similarly, if the UEQM type is FD UEQM, the MFB sent by the first station is either the MFB measured during FD UEQM transmission or the MFB fed back during FD UEQM transmission. For example, in (4A), the second station requests the MFB fed back by the first station, which includes the SNR corresponding to each flow in different spatial flows. For example, in (7A), if the RU type is DRU, the MFB sent by the first station is either the MFB measured during DRU transmission or the MFB fed back during DRU transmission. For example, if the RU type is RRU, then the MFB sent by the first station is either the MFB measured during RRU transmission or the MFB fed back during RRU transmission.

[0190] The above (4A) can include the SNR difference between different spatial streams, or the difference in SNR corresponding to different spatial streams. The above (5A) can include the MCS difference between different spatial streams, or the difference in MCS corresponding to different spatial streams. The above (6A) can include the SNR difference between different frequency domain resources, or the difference in SNR corresponding to different frequency domain resources.

[0191] The above (1A) to (7A) represent the types of information requested by the second station, that is, the types of information in the first radio frame that the second station requests from the first station. Each item in (1A) to (7A) can be represented by a single piece of information, such as the second RU type information or the second RU size information as shown below; or, at least two of the above items can be represented by a single piece of information, such as the second information as shown below, etc., which will not be listed here. For an explanation of the contents of the second control field, please refer to the following text, which will not be detailed here.

[0192] 603. The first station parses the second wireless frame and generates the first wireless frame.

[0193] By parsing the second radio frame, the first station can identify the second control field as a ULA field and determine the type of information in the MFB response requested by the second station from the first station. Therefore, the first station can measure the MFB parameters based on the PPDU carrying the second radio frame, and generate a first radio frame based on the measurement results. For example, by measuring the PPDU, the first station can determine the MCS or SNR corresponding to different spatial flows, and thus carry this information in the first radio frame. A description of the first radio frame can be found in step 604, and will not be detailed here.

[0194] 604. The first station sends a first radio frame, and correspondingly, the second station receives the first radio frame. The first radio frame may include a first control information field, which is used for ULA and may be used to carry link adaptation information.

[0195] For example, the non-requested MFB field in the first control information field can be 0, and the MRQ field can also be 0. Further explanation of the MRQ field can be found in step 602, and will not be detailed here. For a requested MFB, the MRQ / UL UHR TB PPDU MFB field can be used to indicate that the first radio frame is an MFB response.

[0196] The first control information field may be contained within the first control field. For an explanation of the first control information field, the first control field, or the first radio frame, please refer to the above descriptions of the second control information field, the second control field, or the second radio frame; these will not be elaborated upon here. The first radio frame may also be referred to as an MFB response or a non-request MFB, etc.

[0197] The first control field can be used to indicate at least one of the following:

[0198] (1B) The first control information field is used for ULA, or the first control information field is used for UHR, or the first control field is ULA;

[0199] (2B) The modulation type is UEQM or EQM;

[0200] (3B) The UEQM type is SD UEQM or FD UEQM;

[0201] (4B) SNR corresponding to each flow in different spatial flows;

[0202] (5B) MCS corresponding to each flow in different spatial flows;

[0203] (6B) SNR corresponding to each frequency domain resource in different frequency domain resources;

[0204] (7B) The RU type is either DRU or RRU.

[0205] The above (4B) may include the SNR difference between different spatial streams, or the difference between the SNRs corresponding to different spatial streams, or the difference between the SNR of the first SS and the SNR of the second SS. The above (5B) may include the MCS difference between different spatial streams, or the difference between the MCSs corresponding to different spatial streams, or the difference between the MCS of the first SS and the MCS of the second SS. The first SS and the second SS are both SSs recommended by the first site. Optionally, the second SS can be the basic SS. For example, the first site can provide feedback on the SNR difference or MCS difference between other SSs and the basic SS. Other SSs are SSs other than the basic SS among the SSs recommended by the first site. The above (6B) may include the SNR difference between different frequency domain resources, or the difference between the SNRs corresponding to different frequency domain resources, or the difference between the SNR of the first frequency domain resource and the SNR of the second frequency domain resource. Other explanations regarding (1B) to (7B) can be found in (1A) to (7A) above, and will not be detailed here.

[0206] The above (1B) to (7B) represent the information content in the first radio frame fed back by the first station. Each item in (1B) to (7B) can be represented by a single piece of information, such as the first RU type information or the first RU size information as shown below; or, at least two of the above items can be represented by a single piece of information, such as the first information as shown below, etc., which will not be listed here. For an explanation of the first control field, please refer to the following text, which will not be detailed here.

[0207] 605. The second station parses the first wireless frame.

[0208] The second station can obtain the link adaptation information recommended by the first station by parsing the first radio frame, and thus select appropriate parameters to send PPDU.

[0209] For further explanation of the request-based MFB shown in Figure 6a, please refer to Figure 3a, which will not be elaborated here.

[0210] Figure 6b is another flowchart illustrating the link-adaptive communication method provided in this application embodiment. The method shown in Figure 6b can be for non-requestive MFB. The descriptions of the first and second stations in Figure 6b can be found in Figure 1 or Figure 3b above, and will not be detailed here. As shown in Figure 6b, the method includes:

[0211] In one possible implementation, the method shown in FIG6b may include step 611.

[0212] 611. The first station generates the first wireless frame.

[0213] For non-requested MFBs, the first station can estimate the relevant MFB parameters based on its most recently received PPDU and generate the first radio frame based on the estimation results.

[0214] 612. The first station sends a first radio frame, and correspondingly, the second station receives the first radio frame. The first radio frame may include a first control information field, which is used for ULA and may be used to carry link adaptation information.

[0215] For example, the non-requested MFB field in the first control information field can be 1. For a non-requested MFB, the MRQ / UL UHR TB PPDU MFB field can be used to indicate whether the first radio frame is a feedback for a UHR MU PPDU or a UHR TB PPDU. If this field is 1, it indicates that the link adaptation information recommended by the first site is for the UHR TB PPDU sent by the first site. Conversely, if this field is 0, it indicates that the link adaptation information recommended by the first site is for the UHR MU PPDU sent by the second site to the first site.

[0216] Further details regarding the first radio frame can be found in step 604 or below, and will not be elaborated here.

[0217] 613. The second station parses the first wireless frame.

[0218] The second station can obtain the link adaptation information recommended by the first station by parsing the first radio frame. For example, if the MRQ / UL UHR TB PPDU MFB field is 1, the second station can schedule the first station based on the recommended link adaptation information, allowing the first station to send UHR TB PPDUs. Conversely, if the MRQ / UL UHR TB PPDU MFB field is 0, the second station can send MU PPDUs to the first station based on the recommended link adaptation information.

[0219] For further explanation of the non-requested MFB shown in Figure 6b, please refer to Figure 3b, which will not be elaborated here.

[0220] In this embodiment of the application, by designing control fields such as a first control field and a second control field, the control fields can be compatible with link adaptation under the new standard and better adapt to the new standard.

[0221] The following describes the control fields involved in the embodiments of this application.

[0222] As one possible implementation, the first control information field may include at least one of the following: first information, first NSS information, first RU size information, or first RU type information.

[0223] The first information may be used to indicate at least one of the following: the modulation type recommended by the first site is UEQM or EQM; the NSS recommended by the first site; the MCS corresponding to each stream in different spatial streams; the SNR corresponding to each stream in different spatial streams; the SNR corresponding to each frequency domain resource in different frequency domain resources; or, whether the PPDU used for measurement adopts BF.

[0224] The first NSS information can be used to indicate the NSS recommended by the first site, such as if the first NSS information is carried in the NSS / UEQM difference mode field (or NSS and UEQM difference mode field). The first RU size information can be used to indicate the RU size recommended by the first site, such as if the first RU size information is carried in the RU size field. The first RU type information can be used to indicate the RU type recommended by the first site, which may include DRU or RRU, such as if the first RU type information is carried in the DRU / RRU recommendation field.

[0225] The aforementioned information can be contained in one field or in at least two fields. This application does not limit the number of fields contained in a single piece of information. Examples are given below:

[0226] As an example 1, the aforementioned first information can be carried in the UEQM / EQM field, which can be used to indicate the modulation type recommended by the first site.

[0227] As another example 2, the aforementioned first information can be carried in the UEQM / EQM field and the TxBF field. The UEQM / EQM field is used to indicate the modulation type recommended by the first site, and the TxBF field indicates whether the PPDU used for measurement adopts beamforming. If the PPDU used for measurement adopts beamforming, it means that the transmission type of the PPDU is beamforming PPDU; if the PPDU used for measurement does not adopt beamforming, it means that the transmission type of the PPDU is non-beamforming PPDU.

[0228] For example, the UEQM / EQM field and the TxBF field can be used to jointly indicate at least one of the following: the modulation type recommended by the first site is EQM, and the transmission type of the PPDU is non-beamforming PPDU; the modulation type recommended by the first site is EQM, and the transmission type of the PPDU is beamforming PPDU; or the modulation type recommended by the first site is UEQM, and the transmission type of the PPDU is beamforming PPDU.

[0229] For example, the UEQM / EQM field and the TxBF field are used to jointly indicate at least one of the following: the modulation type recommended by the first site is EQM, and the transmission type of the PPDU is non-beamforming PPDU; the modulation type recommended by the first site is EQM, and the transmission type of the PPDU is beamforming PPDU; the modulation type recommended by the first site is UEQM, and the first control information field includes the RU allocation field; or the modulation type recommended by the first site is UEQM, and the first control information field includes the SNR field (or the SNR difference field).

[0230] For example, the UEQM / EQM field and the TxBF field are used to jointly indicate at least one of the following: the modulation type recommended by the first site is EQM, and the transmission type of the PPDU is non-beamforming PPDU; the modulation type recommended by the first site is EQM, and the transmission type of the PPDU is beamforming PPDU; the modulation type recommended by the first site is UEQM, and the type of UEQM is SD UEQM; or the modulation type recommended by the first site is UEQM, and the type of UEQM is FD UEQM.

[0231] For example, the UEQM / EQM field can occupy 1 bit, and the TxBF field can occupy 1 bit. Of course, the UEQM / EQM field and the TxBF field can also be carried in a single field, which occupies 2 bits.

[0232] As another example 3, the first information can be carried in the UEQM / EQM field and the NSS / UEQM difference mode field. The UEQM / EQM field can be used to indicate the modulation type recommended for the first site. The NSS / UEQM difference mode field can be used to indicate the NSS; optionally, the NSS / UEQM difference mode field can also be used to indicate the MCS corresponding to each stream in different spatial streams. Of course, the first information can also be carried in the UEQM / EQM field, the TxBF field, and the NSS / UEQM difference mode field (or the NSS and UEQM difference mode fields).

[0233] As another example 4, the first information can be carried in the UEQM / EQM field and the SNR field (or SNR difference field). The UEQM / EQM field can be used to indicate the modulation type recommended by the first site, and the SNR field can be used to indicate the SNR corresponding to each stream in different spatial streams, or the SNR corresponding to different frequency domain resources. Of course, the first information can also be carried in the UEQM / EQM field, the TxBF field, and the SNR field (or SNR difference field).

[0234] For further explanation of the above fields, please refer to the following text, as shown in Figure 8a or Tables 4 to 12, etc.

[0235] As another possible implementation, the second control information field may include at least one of the following: second information, second NSS information, second RU size information, or second RU type information.

[0236] The second information may be used to indicate at least one of the following: the modulation type requested by the second site is UEQM / EQM; the UEQM type requested by the second site is SD UEQM or FD UEQM; or, whether the PPDU used for measurement adopts BF.

[0237] The second NSS information can be used to indicate the NSS requested by the second site, such as if the second NSS information is carried in the NSS / UEQM difference mode field (or NSS and UEQM difference mode field). The second RU size information can be used to indicate the RU size requested by the second site, such as if the second RU size information is carried in the RU size field. The second RU type information can be used to indicate the RU type requested by the second site, which may include DRU or RRU, such as if the second RU type information is carried in the DRU / RRU suggestion field.

[0238] For an explanation of the fields carried by the second information, please refer to Examples 1 and 2 above, which will not be elaborated here.

[0239] For further explanation of the first control information field, the second control information field, etc., please refer to the following text.

[0240] Since the first control information field or the first control field is a field in an MFB response or a non-request MFB, and the second control information field or the second control field is a field in an MFB request, the format for the first control field and the second control field, or the format for the first control information field and the second control information field, is as follows:

[0241] The formats of the first control field and the second control field can be similar. For example, if these two fields have the same length, the control information fields they contain must also have the same format; that is, the first control information field and the second control information field can have the same format. However, the functions of the same field within the first and second control information fields can differ. For instance, for an MFB request, field A in the second control information field can be used to request information B, while field A in the first control information field can be used to indicate information B. In other words, field A in the second control information field can indicate the type of information requested by the second site, while field A in the first control information field can indicate the content of the information requested by field A. Therefore, the following explanation will use control fields, control information fields, and control ID fields as examples, without further distinguishing between the first and second control fields, the first and second control information fields, or the first and second control ID fields.

[0242] Of course, the formats of the first control field and the second control field can also be different. Alternatively, the formats of the first control information field and the second control information field can also be different.

[0243] Figure 7 is a schematic diagram of the format of the control field provided in an embodiment of this application. As shown in Figure 7, the control field may include a control ID field and a control information field. Figure 7 also exemplarily shows the length of the control ID field and the length of the control information field. The control ID field can be used to identify that the control field carrying the control ID field is a ULA field, or to identify that the control field is used for UHR, or to identify that the control field is used for UHR LA. For the second radio frame, the control information field can be used to indicate the type of information requested by the second station, or the type of link adaptation information requested by the second station. For the first radio frame, the control information field can be used to indicate the link adaptation information (or link adaptation parameters) fed back by the first station.

[0244] The embodiments of this application are applicable not only to the UHR standard, but also to standards after the UHR standard. Therefore, the names of the fields below are only examples. As the standard progresses, the names of the fields may change. The embodiments of this application do not limit the names of the fields.

[0245] The following examples illustrate control fields. Four implementation methods for control fields are shown below. If any implementation method or example is not described in detail below, please refer to other implementation methods or examples, or refer to the above text.

[0246] Implementation Method 1

[0247] The control ID field can have an integer value between 10 and 14. When the control ID field has a value between 10 and 14, it indicates that the control field carrying the control ID can be a ULA field. Of course, as standards evolve, the control ID field can also have other values ​​used to identify a ULA; for example, it can occupy more bits, and with the increase in the number of bits, the control ID field may have more possible values.

[0248] For example, taking Figure 5 as an example, if the control ID field is 2 and B25 in the control information field is 0, then the control field can be an HLA field. If the control ID field is 2 and B25 in the control information field is 1, then the control field can be an ELA field. B25 represents the 26th bit in the control information field, and the 1st bit in the control information field can be represented as B0.

[0249] For example, if the control ID field is an integer value between 10 and 14, then the control field can be a ULA field. Both the sender and receiver can identify the control field based on this control ID field.

[0250] Figure 8a is a schematic diagram of a control field format provided in an embodiment of this application. As shown in Figure 8a, the control field may include a control ID field and a control information field. The control information field may include at least one of the following: non-requested MFB, MRQ / UL UHR TB PPDU MFB, NSS / UEQM variation patterns, UHR-MCS, RU allocation, PS160, BW, UEQM / EQM, MSI / partial PPDU parameters, TxBF, or DRU / RRU suggestion. The aforementioned NSS / UEQM variation pattern field may also be referred to as NSS and UEQM variation pattern or NSS / UEQM QAM variation pattern field, etc. The names of each field are not limited in this embodiment of the application.

[0251] For an explanation of Figure 8a, please refer to Tables 4 to 12, etc. Table 4 exemplarily illustrates the meaning and definition of each field in the control information field shown in Figure 8a. Figure 8a also exemplarily illustrates the length and order of each field, but the embodiments of this application are not limited thereto.

[0252] Figure 8b is a schematic diagram of the format of the control field in the second radio frame provided in an embodiment of this application. As shown in Figure 8b, for the control information field in the second radio frame, the non-request MFB field can be 0 (indicating a requested MFB), and the MRQ / UL UHR TB PPDU MFB field can be 1 (indicating an MFB request).

[0253] Figure 8c is a schematic diagram of the format of the control field in the first radio frame provided in an embodiment of this application. As shown in Figure 8c, for the control information field in the first radio frame, the non-requested MFB field can be 1 (indicating a non-requested MFB), and the MRQ / UL UHR TB PPDU MFB field can be 0 or 1; or, the non-requested MFB field can be 0 (indicating a requested MFB), and the MRQ / UL UHR TB PPDU MFB field can be 0 (indicating an MFB response). The relationship between the values ​​of the fields and their corresponding meanings shown in Figures 8b and 8c is merely an example and is not intended to limit the embodiments of this application.

[0254] Figures 8b and 8c illustrate examples where the first and second control fields share the same control field. In specific implementations, the formats of the first and second control fields can also differ; for example, different fields can define functions separately, which will not be detailed here. Further explanations of Figures 8b and 8c can be found in Figure 8a or Tables 4 to 12, etc., and will not be elaborated here. The relationship between the values ​​and corresponding meanings of the combined indications of the UEQM / EQM and TxBF fields in Figures 8a to 8c is merely an example, and the content jointly indicated by these two fields is also an example, not intended to limit the embodiments of this application. Other content jointly indicated by the above two fields can be found in Table 4. The correspondence between the values ​​and meanings of each field in Table 4 is merely an example and not intended to limit the embodiments of this application.

[0255] In Table 4, STA can be the MFB responder, i.e., the first site.

[0256] Table 4

[0257] The following examples illustrate the UEQM / EQM field, the NSS / UEQM difference pattern field, and the UHR-MCS field.

[0258] When the UEQM / EQM field indicates EQM: the NSS / UEQM difference mode field can be used to indicate the NSS, which can be 1 to 8. The UHR-MCS field can be used to indicate the MCS of each flow, and the MCS of each flow is the same. The MCS indicated by the UHR-MCS field (or the index of the MCS) can be the MCS of the SS with the lowest SNR, or the MCS of the SS with the highest SNR.

[0259] As an example, the index of the MCS indicated by the UHR-MCS field can be the same as that in the 802.11be standard. As shown in Table 5, the MCS index can include 16 entries, with indices 0 to 13 corresponding to modulation schemes from BPSK to 4096-QAM, respectively. Index 14 is reserved for triggered transmissions. Table 5 also shows the code rate as an example.

[0260] Table 5

[0261] As another example, the UHR-MCS field can also indicate more indices, meaning the supported MCS indices can be greater than 16, such as expanding from 16 entries to 32 entries. For instance, the combination of modulation scheme and code rate indicated by the UHR-MCS field can include, but is not limited to, at least one of the following: QPSK, 2 / 3 code rate; 16-QAM, 2 / 3 code rate; 256-QAM, 2 / 3 code rate; 16-QAM, 5 / 6 code rate.

[0262] The above-described combinations of modulation methods and bit rates are merely examples and are not intended to limit the embodiments of this application.

[0263] When the UEQM / EQM field indicates UEQM: the NSS / UEQM difference pattern field can be used to indicate the NSS and the MCS corresponding to each spatial flow in different spatial flows. The MCS corresponding to each flow can include the MCS differences corresponding to each spatial flow, and these MCS differences can include QAM differences, such as the QAM difference between the MCS of the first SS and the MCS of the second SS. Optionally, the second SS can be the base SS. For example, the NSS / UEQM difference pattern field can be used to indicate the QAM difference between the MCS of other SSs and the MCS of the base SS. For example, if NSS = 4, then these 4 spatial flows can be the 4 SSs with the highest SNR.

[0264] As an example, the NSS / UEQM difference mode field can occupy 3 bits. Table 6 illustrates the relationship between the index and meaning represented by the NSS / UEQM difference mode field. Table 6 illustrates 8 UEQM difference modes. When NSS is 2, 2 UEQM difference modes are supported; when NSS is 3, 3 UEQM difference modes are supported; when NSS is 4, 3 UEQM difference modes are supported, for a total of 8 UEQM difference modes, with indices corresponding to 0 to 7 respectively. The 8 UEQM difference modes correspond exactly to 3 bits.

[0265] Assuming the first spatial stream is the one with the highest SNR, the QAM of the first spatial stream can be the QAM corresponding to the base MCS. The UHR-MCS field indicates the QAM corresponding to the base MCS, and the bitrate of each spatial stream can also be indicated through the UHR-MCS field.

[0266] In Table 6, QAM-1 indicates that it differs from the QAM of the first spatial flow by one level. For example, if the first spatial flow is 4096-QAM, then the QAM-1 of the second spatial flow corresponds to 1024-QAM; if the first spatial flow is 1024-QAM, then the QAM-1 of the second spatial flow corresponds to 256-QAM; if the first spatial flow is 256-QAM, then the QAM-1 of the second spatial flow corresponds to 64-QAM; if the first spatial flow is 64-QAM, then the QAM-1 of the second spatial flow corresponds to 16-QAM; if the first spatial flow is 16-QAM, then the QAM-1 of the second spatial flow corresponds to QPSK; if the first spatial flow is QPSK, then the QAM-1 of the second spatial flow corresponds to BPSK.

[0267] In Table 6, QAM-2 indicates that it differs from the QAM of the first spatial flow by two levels. For example, if the first spatial flow is 4096-QAM, then the QAM-2 of the second spatial flow corresponds to 256-QAM; if the first spatial flow is 1024-QAM, then the QAM-2 of the second spatial flow corresponds to 64-QAM; if the first spatial flow is 256-QAM, then the QAM-2 of the second spatial flow corresponds to 16-QAM; if the first spatial flow is 64-QAM, then the QAM-2 of the second spatial flow corresponds to QPSK; and if the first spatial flow is 16-QAM, then the QAM-2 of the second spatial flow corresponds to BPSK. The meaning of QAM-3 can be found in the explanations of QAM-1 or QAM-2, and will not be listed here.

[0268] The MCS differences between the various spatial streams shown in Table 6 are merely examples and are not intended to limit the embodiments of this application. The embodiments of this application are shown with a starting index of 0; in specific implementations, the starting index can also be 1, in which case other indices can be incremented by 1 sequentially. The explanation of the indices also applies to the other tables shown in the embodiments of this application.

[0269] Table 6

[0270] As another example, the NSS / UEQM difference mode field can occupy 4 bits. Table 7 exemplarily illustrates the relationship between the index and meaning represented by the NSS / UEQM difference mode field. Table 7 introduces more UEQM difference modes, such as supporting more spatial streams for QAM-3. Table 7 exemplarily shows 13 UEQM difference modes. When NSS is 2, 2 UEQM difference modes are supported; when NSS is 3, 5 UEQM difference modes are supported; when NSS is 4, 6 UEQM difference modes are supported, for a total of 13 UEQM difference modes, with indices corresponding to 0 to 12 respectively. The 13 UEQM difference modes can correspond to 4 bits.

[0271] The various UEQM difference modes shown in Table 7 can be obtained by simulating various combinations under specific channel conditions. Other explanations in Table 7 can be found in Table 6, and will not be repeated here.

[0272] Table 7

[0273] In this embodiment, when the NSS / UEQM difference mode occupies 4 bits, the length of other fields shown in Figure 8a can be appropriately compressed. For example, the length of the MSI / partial PPDU parameter fields can be reduced, and the control information field can exclude the TxBF field, etc. Fields whose lengths are compressed will not be listed here individually.

[0274] In this embodiment, the UEQM / EQM field and the NSS / UEQM difference mode field can also be used to jointly indicate: the NSS under EQM, and the MCS corresponding to each stream in different spatial streams under UEQM. These two fields can be represented by a unified M bits, and can jointly indicate M1 entries under EQM and M2 entries under UEQM. M, M1, and M2 are all positive integers. For example, M = 4, M1 = M2 = 8. The UEQM / EQM field can occupy 1 bit, and the NSS / UEQM difference mode field can occupy 3 bits, for a total of 4 bits. When the index indicated by these two fields is 0 to 7, the most significant bit (MSB) of these 4 bits is 0, and MSB = 0 indicates 1SS-8SS under EQM; when the index indicated by these two fields is 8 to 15, the MSB of these 4 bits is 1, and MSB = 1 indicates various combinations of UEQM difference modes for different spatial stream numbers under UEQM.

[0275] Table 8 provides an example of the indices 0–15 jointly indicated by the UEQM / EQM field and the NSS / UEQM difference pattern field, along with the meaning of each index. Further explanation of Table 8 can be found in the table above, and will not be elaborated upon here.

[0276] Table 8

[0277] For UEQM, Tables 6-8 above illustrate examples where the NSS / UEQM difference mode field simultaneously indicates both the NSS and the MCS of different spatial streams, i.e., simultaneously indicating both NSS and UEQM difference modes. As another possible implementation, two fields can be used to indicate the NSS and UEQM difference modes respectively. For example, field A can be used to indicate the NSS, and field B can be used to indicate the UEQM difference mode. Field A can occupy 3 bits, and field B can occupy 2 or 3 bits, etc. For EQM, field B can be reserved or as shown in Tables 9-12. Field A can be called the NSS field, and field B can be called the UEQM / EQM difference mode field (or simply the UEQM difference mode field). This implementation is logically simple.

[0278] In another possible implementation, where two fields indicate the NSS and UEQM difference modes respectively, the EQM and UEQM difference modes under the same NSS can be indicated by a single field, which can be called the EQM / UEQM difference mode field. The NSS field can occupy 3 bits, and the NSS can be 1 to 8. For example, for EQM, the NSS can be 1 to 8; for UEQM, the NSS can be 1 to 4. Alternatively, the NSS can be limited to 1 to 4, in which case the NSS field can occupy 2 bits. The UEQM / EQM difference mode field can occupy 2 or 3 bits, etc. Tables 9 to 12 show examples of a 2-bit UEQM / EQM difference mode field. For explanations of NSS greater than 5, please refer to Table 12, which will not be repeated below.

[0279] Table 9 provides an example of the relationship between the indexes and meanings indicated by the UEQM / EQM difference pattern fields when NSS=2.

[0280] Table 9

[0281] Table 10 provides an example of the relationship between the indexes and meanings indicated by the UEQM / EQM difference pattern fields when NSS=3.

[0282] Table 10

[0283] Table 11 provides an example of the relationship between the indexes and meanings indicated by the UEQM / EQM difference pattern fields when NSS=4.

[0284] Table 11

[0285] Table 12 provides an example of the relationship between the indexes and meanings indicated by the UEQM / EQM difference pattern fields when NSS=5.

[0286] Table 12

[0287] For SD UEQM, the control information field may include an NSS / UEQM difference mode field, which can indicate the MCS of each stream in different spatial streams (as shown above). In addition, the control information field may also include an SNR field (or SNR difference field), which can be used to indicate the SNR of each spatial stream in different spatial streams, or the SNR difference between spatial streams.

[0288] Figure 9 is a schematic diagram of another format of the control field provided in an embodiment of this application. As shown in Figure 9, the control field may include a control ID field and a control information field. The control information field may include at least one of the following: non-requested MFB, MRQ / UL UHR TB PPDU MFB, NSS / UEQM variation patterns (or NSS and UEQM variation patterns), UHR-MCS, SNR (or SNR gap), BW, UEQM / EQM, MSI / partial PPDU parameters, TxBF, or DRU / RRU suggestion. The names of each field are not limited in this embodiment.

[0289] Figure 9 illustrates an example where SD UEQM supports a maximum of four SSs. Therefore, the 9 bits occupied by the SNR field can indicate the SNR difference between the following SSs: SS1 and SS2 (SS2-SS1 in Figure 9), SS2 and SS3 (SS3-SS2 in Figure 9), and SS3 and SS4 (SS4-SS3 in Figure 9). The SNR difference between each pair of SSs can occupy 3 bits. Figure 9 uses SNR difference as an example; in specific implementations, the SNR field can also indicate the SNR of each spatial stream in different spatial streams (not shown in Figure 9). Further explanations of Figure 9 can be found in Figures 8a-8b or Tables 4-12.

[0290] Simulations show that the SNR difference between two SSs is typically between 2dB and 16dB. Therefore, Table 13A exemplarily illustrates the SNR difference between two SSs. Table 13A also shows the relationship between the index and meaning indicated by each 3 bits in the SNR field. This relationship is merely an example and is not intended to limit the embodiments of this application.

[0291] Table 13A

[0292] Figure 9 illustrates an example where the control information field includes the SNR field. In a specific implementation, the control information field can also include a field indicating an offset, which can be the offset between the currently used transmission power and the maximum transmission power. The unit of this offset can be dB, etc., and this embodiment does not impose any limitations. Indicating the aforementioned offset can assist in subsequent AP scheduling.

[0293] As shown above, this embodiment of the application, through the joint indication of the UEQM / EQM field and the TxBF field, can distinguish whether the control information field includes the UEQM / EQM field + RU allocation field + PS160 field, or whether it includes the UEQM / EQM field + SNR / SNR difference field. The joint indication method shown in this embodiment of the application can be applied to the first control field or the second control field. When the control information field does not include the RU allocation field and the PS160 field, the first site can default to full bandwidth feedback and not perform RU indication; or it can default to testing the MFB in the allocated RU (or measure in the default allocated RU to obtain the MFB parameter), without additional indication.

[0294] Figure 10 is a schematic diagram of another format of the control field provided in an embodiment of this application. As shown in Figure 10, the control field may include a control ID field and a control information field. The control information field may include at least one of the following: non-requested MFB, MRQ / UL UHR TB PPDU MFB, NSS / UEQM variation patterns (or NSS and UEQM variation patterns), UHR-MCS, SNR (or SNR difference), BW, UEQM / EQM, MSI / partial PPDU parameters, TxBF or DRU / RRU suggestion.

[0295] For FD UEQM, the SNR field can be used to indicate the SNR of each frequency domain resource in different frequency domain resources. The SNR of each frequency domain resource can include the SNR difference between the various frequency domain resources. For example, the SNR field can include at least one of the following: RU size field or lower half to upper half SNR difference field. The lower half to upper half SNR difference field can be used to indicate the SNR difference between the SNR of the first frequency domain resource and the SNR of the second frequency domain resource. The frequency domain resource can be the frequency domain resource corresponding to the PPDU used for measurement. The RU size field can indicate the RU size with less overhead. The names of the various fields shown in FIG10 are not limited in this embodiment. Other descriptions of FIG10 can be found in FIG8a to FIG8b or Tables 4 to Tables 12, etc.

[0296] As an example, the RU size field indicates that only large RUs are supported. FD UEQM can be used to adapt to the signal-to-interference-plus-noise ratio difference between sub-channels of 20MHz (which can correspond to a 242-tone RU). Large RU sizes can include, but are not limited to, at least one of the following: 242-tone RU, 484-tone RU, 484+242-tone MRU, 996-tone RU, 996+484-tone MRU, 996+484+242-tone MRU, 2*996-tone RU, 2*996+484-tone MRU, 3*996-tone RU, 3*996+484-tone MRU, 4*996-tone RU. This RU size can occupy 4 bits.

[0297] As another example, the RU size field indicates that the RU size can support small RUs. Since there is a large frequency selectivity among small RUs, the small RU size can include, but is not limited to, at least one of the following: 26-tone RU, 52-tone RU, 52+26-tone MRU, 106-tone RU, 106+26-tone MRU, etc.

[0298] The SNR difference between different frequency domain resources can be an integer or a negative number. Therefore, more bits (such as 4 bits) may be needed to indicate it. Table 13B exemplarily shows the SNR difference between two frequency domain resources. Each SNR difference can be indicated using 4 bits. The SNR field can indicate one SNR difference or two SNR differences, etc., and this application embodiment is not limited thereto.

[0299] Table 13B

[0300] If the control information fields do not include the RU allocation field and the PS160 field, the first site can default to full bandwidth feedback without RU indication; or it can default to testing the MFB in the assigned RU without additional indication.

[0301] Regarding implementation method one, this application embodiment provides a way to adapt to link adaptation under the new standard by appropriately adjusting the length or indication method of the field when the number of bits is limited, so that UHR link adaptation can support new features such as UEQM and DRU.

[0302] In Implementation Method 1, the Control ID field can be any integer value between 10 and 14. In Implementation Method 2, as shown below, the Control ID field can still be equal to 2, thus saving Control IDs. When the value of the Control ID field is 2, the control information field carried in the same control field as that Control ID can be used for HLA, ELA, or ULA. To facilitate differentiation of ULA, other fields can be used to distinguish ULA. These other fields can be fields reserved in ULA control but have actual functions in HLA or ELA control. Implementation Method 2 will illustrate these other fields with examples.

[0303] Implementation Method Two

[0304] For HLA or ELA controls, when the non-requested MFB field is 0, the TxBF field is reserved, with a default value of 0. Therefore, as an example, B0=0 and B24=1 in the control information field can indicate that this control information field is used for UHR. Alternatively, B0=0 and B24=1 in the control information field means that the control field carrying this control information field can be used for ULA control.

[0305] Figure 11a is a schematic diagram of another format of the control field provided in an embodiment of this application. As shown in Figure 11a, the non-requested MFB field (i.e., B0 of the control information field) is 0, and the TxBF field (i.e., B24 of the control information field) is 1, then the control field can be used for UHR. Of course, B0 in the control information field can also be called B4 in the control field. That is to say, the position of each bit shown in the embodiment of this application can change with different fields. For other bit positions, the embodiment of this application will not list them one by one. The UHR non-requested MFB field (also called non-requested MFB) in Figure 11a can be used to indicate whether the MFB is a requested MFB or a non-requested MFB.

[0306] For ELA control, when the non-requested MFB field is 1, B0 in the MSI / partial PPDU parameter field (i.e., B22 in the control information field) is reserved. Therefore, as another example, B0=1, B22=1, and B25=1 in the control information field can indicate that this control information field is used for UHR. Alternatively, B0=1, B22=1, and B25=1 in the control information field means that the control field carrying this control information field can be used for ULA control.

[0307] Figure 11b is a schematic diagram of another format of the control field provided in an embodiment of this application. As shown in Figure 11b, the non-request MFB field (i.e., B0 of the control information field) is 1, the MSI / partial PPDU parameter field (i.e., B22 of the control information field) is 1, and the HE / EHT indication field (i.e., B25 of the control information field) is 1. Therefore, the control field can be used for UHR. Of course, the HE / EHT indication field can also have other names; this embodiment of the application does not limit the specific name of this field.

[0308] The explanations of the other fields in Figures 11a and 11b can be found above, and will not be detailed here.

[0309] The methods for distinguishing ULA controls shown in Figures 11a and 11b are merely examples. In actual implementations, when the non-request MFB field is 1 and the MRQ (or MRQ / UL EHT TB PPDU MFB) field is 1, many reserved fields will still exist in the HLA or ELA controls. These reserved fields can all be used to escape indication ULA controls. When using two or more bits to escape indication ULA controls, since the indication ULA controls occupy more bits, the length of other fields can be compressed. For example, the supported RU types or numbers can be reduced to compress the RU allocation field or PS160 field. Another example is that encoding types can be predefined to compress the encoding type field, etc., which will not be listed here.

[0310] Regarding implementation method two, the embodiments of this application utilize reserved fields or combinations that exist in certain situations in HLA or ELA to indicate ULA, thus saving control ID.

[0311] The implementation methods 1 and 2 described above are both illustrated using a 26-bit control information field as an example, thus allowing the use of the same number of bits as HLA or ELA, ensuring consistent parsing and simplifying implementation complexity. The implementation methods 3 and 4 described below are both illustrated using a control information field that occupies 26 bits or more as an example, allowing various pieces of information to be carried using appropriate field lengths.

[0312] Implementation Method 3

[0313] The control information field can be an LA variant field, which indicates that the control information field is used for UHR. Of course, the LA variant field can also be used to indicate a future LA variant. The length of the LA variant field is not limited in this embodiment.

[0314] Optionally, the control information fields under the HLA or ELA shown above may also include an LA variant field. This LA variant field can be used to indicate the protocol version corresponding to the control information field.

[0315] For example, the first radio frame can be a control response frame (CRF) or an acknowledgment frame, or various variations thereof. Using a CRF or acknowledgment frame to carry the control field can speed up link adaptation.

[0316] Figures 12a and 12b are schematic diagrams of the format of the acknowledgment frame provided in the embodiments of this application. As shown in Figures 12a and 12b, the acknowledgment frame may include at least one of the following: frame control, duration, receive address (RA), transmitter address (TA), block acknowledgment control (BA control), block acknowledgment information (BA information), control feedback, padding, or FCS. Control field 1 in the control feedback field can be used for UHR. The control information field in control field 1 may include a variant of the LA field. Figure 12a shows an example where the control information field includes the RU allocation field, and Figure 12b shows an example where the control information field includes the SNR field (or SNR difference field). Figures 12a and 12b also exemplarily show the content jointly indicated by the UEQM / EQM field and the TxBF field. For explanations of other fields in Figures 12a and 12b, please refer to the above text, which will not be detailed here.

[0317] Figures 12a and 12b illustrate examples where the control information field is longer than 26 bits. By using CRF or acknowledgment frames to carry ULA, the control information field can be freed from the 26-bit limitation. This allows for the design of control fields that can provide more detailed link adaptation information. For example, the MRQ, UL, UHR, TB, and PPDU fields can be separated, or the order of some fields can be adjusted, such as merging the UEQM / EQM and TxBF fields into a single field. These examples are not listed here.

[0318] In practical implementations, the length of the control information field shown in Figures 12a and 12b can also be equal to 26 bits. If the control information field includes the LA variant field, other fields in the control information field as shown in Implementation Method 1 or Implementation Method 2 above can be compressed. By using the same number of bits, the parsing of the control information field can be kept consistent, simplifying the implementation complexity.

[0319] The second radio frame can be a control request frame, such as a block acknowledgment request (BAR) frame or a multi-user block acknowledgment request (MU BAR) frame.

[0320] Figure 12c is a schematic diagram of the format of a BAR frame provided in an embodiment of this application. As shown in Figure 12c, the BAR frame may include at least one of the following: frame control, duration, receive address (RA), transmitter address (TA), block acknowledgment request control (BAR control), BAR information, control request, padding, or FCS. Control field 1 in the control request field can be used for UHR. Further explanation of control field 1 can be found in Figures 12a or 12b, and will not be detailed here.

[0321] Regarding implementation method three, the embodiments of this application can carry ULA through CRF or through acknowledgment frames, thereby accelerating the feedback rate of link adaptation and making link adaptation more timely.

[0322] Implementation Method 4

[0323] In this implementation, the HTC field can be extended to carry more link adaptation information, so that the control information field is not limited to 26 bits.

[0324] For example, if the HTC field includes a special control ID field with a special value, then the HTC field can include an HTC extension field. This special control ID can be 15, or any integer value between 10 and 14. The special control ID can indicate whether the HTC or A-control field will be extended subsequently.

[0325] Optionally, the HTC field may also include information indicating the total length of the extended or subsequent portions. Optionally, the HTC field may also include one or more redefined control fields. The specific format of the control fields is not limited in this embodiment. Optionally, the control ID field may occupy 4 bits. Alternatively, the control ID field may be extended to 5 bits to define more control types.

[0326] As an example, the HTC field may also include an A-control field. The A-control field and the HTC extended portion field may include one or more control fields, each of which may include a control ID field and a control information field.

[0327] Figure 13a is a schematic diagram of a format of the HTC field provided in an embodiment of this application. As shown in Figure 13a, the HTC field may include at least one of the following: a VHT field, an HE field, an A-control field, or an HTC extension field. The A-control field may occupy 30 bits, and the HTC extension field may occupy X bits. When the value of the special control ID field is a special value, X may be an integer greater than 0. For example, X = 8 bits, or 16 bits, etc., which will not be listed one by one. Optionally, the total length of the A-control field and the HTC extension field may be 30 + X. The HTC extension length field may be used to indicate X or 30 + X. The HTC extension length field may occupy Y bits. Y may be an integer greater than or equal to 0 and less than X.

[0328] As another example, HTC extended fields may include the A-control field.

[0329] Figure 13b is a schematic diagram of another format of the HTC field provided in an embodiment of this application. As shown in Figure 13b, the HTC field may include at least one of the following: a VHT field, an HE field, or an HTC extension field. The HTC extension field may include at least one of the following: a special control ID, an HTC extension length, or an A-control (or UHR A-control). The A-control field may include one or more control fields.

[0330] Figures 13a and 13b illustrate examples where the control ID field occupies 5 bits, but are not intended to limit the embodiments of this application. The description of control field 1 shown in Figures 13a and 13b can be found above, such as in implementation method one, implementation method two, or implementation method three, and will not be detailed here.

[0331] Regarding implementation method four, by extending HTC, the control information field can be freed from the 26-bit limitation, thus allowing the designed control field to indicate link adaptive information in more detail. For example, the MRQ and UL UHR TB PPDU fields can be separated, or the order of some fields can be adjusted, such as merging the UEQM / EQM field and the TxBF field into one field, etc., which will not be listed here.

[0332] For any instances or implementations not described in detail in the methods described above, please refer to other examples or implementations.

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

[0334] This application divides the communication device into functional modules according to the above 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 only represents one logical functional division; other division methods may be used in actual implementation. The communication device of the embodiments of this application will be described in detail below with reference to Figures 14 to 16.

[0335] Figure 14 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 14, the communication device includes a processing module 1401 and a transceiver module 1402. The transceiver module 1402 can implement corresponding communication functions, and the processing module 1401 is used to implement corresponding processing functions. For example, the transceiver module 1402 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0336] In some embodiments of this application, the communication device can be used to perform the actions performed by the first station in the above method embodiments. In this case, the first station can be the device itself or a chip or functional module configurable in the device. The transceiver module 1402 is used to perform the transceiver-related operations of the first station in the above method embodiments, and the processing module 1401 is used to perform the processing-related operations of the first station in the above method embodiments.

[0337] Processing module 1401 can be used to generate a first radio frame; transceiver module 1402 can be used to send or output the first radio frame. For example, transceiver module 1402 can be used to send the first radio frame to a second station via an antenna module. Alternatively, transceiver module 1402 can output the first radio frame generated by the processing module via an input / output module. The description of sending or output here also applies to the following text, and will not be detailed further.

[0338] The transceiver module 1402 can also be used to receive or input a second radio frame. For example, the transceiver module 1402 can receive a second radio frame from a second station via an antenna module. Alternatively, after receiving a second radio frame in antenna mode, the transceiver module 1402 can input the second radio frame into processing mode via an input / output module, allowing the processing module to parse the second radio frame. The description of receiving or input here also applies to the following text, and will not be detailed further.

[0339] Reusing Figure 14, in some other embodiments of this application, the communication device can be used to perform the actions performed by the second station in the above method embodiments. In this case, the second station can be the device itself or a chip or functional module configurable in the device. The transceiver module 1402 is used to perform the transceiver-related operations of the second station in the above method embodiments, and the processing module 1401 is used to perform the processing-related operations of the second station in the above method embodiments.

[0340] The transceiver module 1402 is used to receive or input a first wireless frame. The processing module 1401 can be used to parse the first wireless frame.

[0341] The transceiver module 1402 can also be used to send or output a second wireless frame. The processing module 1401 can also be used to generate the aforementioned second wireless frame.

[0342] For example, transceiver module 1402 may include a radio frequency module, an antenna module, etc. For instance, the transmitting or receiving steps described above can be implemented by the radio frequency module and the antenna module. For example, transceiver module 1402 may include an input / output module, etc. For instance, the output or input steps described above can be implemented by the input / output module.

[0343] Optionally, in the above embodiments, the communication device may further include a storage module, which can be used to store instructions and / or data. The processing module 1401 can read the instructions and / or data in the storage module so that the communication device can implement the aforementioned method embodiments.

[0344] For details regarding the specific explanations of each term, noun, or step in the above embodiments, please refer to the descriptions in the above method embodiments; they will not be detailed here.

[0345] The specific descriptions of the transceiver module and processing module shown in the above embodiments are merely examples. For the specific functions or execution steps of the transceiver module and processing module, please refer to the above method embodiments, which will not be described in detail here.

[0346] It is understandable that the module division in the above-mentioned device is merely a logical functional division. Each function can correspond to a functional module, or two or more functions can be integrated into one functional module. In actual implementation, all or some modules can be integrated into one physical entity, or they can be distributed across different physical entities. Furthermore, the above-mentioned functional modules can be implemented in hardware, software, or a combination of both.

[0347] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0348] The communication device according to the embodiments of this application has been described above. The following describes possible product forms of the communication device. Any product possessing the functions of the communication device described in FIG. 14 above falls within the protection scope of the embodiments of this application. The following description is merely illustrative and does not limit the product form of the communication device according to the embodiments of this application to this extent.

[0349] In one possible implementation, in the communication device shown in FIG14, the processing module 1401 may be one or more processors, and the transceiver module 1402 may be a transceiver, or the transceiver module 1402 may also be a transmitting module and a receiving module. The transmitting module may be a transmitter, and the receiving module may be a receiver. The transmitting module and the receiving module are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver may be coupled, etc., and the connection method of the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method may be the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method may be the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the aforementioned information, the information may need to undergo further processing before being input into the processor.

[0350] Figure 15 is a schematic diagram of another structure of the communication device provided in an embodiment of this application. As shown in Figure 15, the communication device 150 includes one or more processors 1520 and transceivers 1510.

[0351] In some embodiments of this application, the communication device can be used to execute the steps, methods, or functions performed by the first station. For example, the processor 1520 can be used to execute the functions or steps implemented by the processing module 1401 shown in FIG. 14, and the transceiver 1510 can be used to execute the functions or steps implemented by the transceiver module 1402 shown in FIG. 14. Detailed descriptions of the processor 1520 and transceiver 1510 can be found in FIG. 14 or the method embodiments shown above, and will not be elaborated further here.

[0352] In other embodiments of this application, the communication device is used to execute the steps, methods, or functions performed by the second station. For example, the processor 1520 can be used to execute the functions or steps implemented by the processing module 1401 shown in FIG. 14, and the transceiver 1510 can be used to execute the functions or steps implemented by the transceiver module 1402 shown in FIG. 14. Detailed descriptions of the processor 1520 and transceiver 1510 can be found in FIG. 14 or the method embodiments shown above, and will not be elaborated further here.

[0353] In various implementations of the communication device shown in Figure 15, 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.

[0354] Optionally, the communication device 150 may further include one or more memories 1530 for storing program instructions and / or data. The memory 1530 is coupled to the processor 1520. The coupling in this embodiment is an indirect coupling or communication connection between communication devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between the communication devices, units, or modules. The processor 1520 may operate in conjunction with the memory 1530. The processor 1520 may execute program instructions stored in the memory 1530. Optionally, at least one of the above-mentioned memories may be included in the processor.

[0355] This embodiment does not limit the specific connection medium between the transceiver 1510, processor 1520, and memory 1530. In Figure 15, the memory 1530, processor 1520, and transceiver 1510 are connected via a bus 1540, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 15, but this does not imply that there is only one bus or one type of bus.

[0356] 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.

[0357] 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 having instruction or data structure forms, 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.

[0358] The processor 1520 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. The memory 1530 is primarily used for storing software programs and data. The transceiver 1510 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.

[0359] When the communication device is powered on, the processor 1520 can read the software program in the memory 1530, 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 1520 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 1520. The processor 1520 converts the baseband signal into data and processes the data.

[0360] 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.

[0361] The communication device shown in this application embodiment may have more components than those in Figure 15, and this application embodiment does not limit this. The methods executed by the processor and transceiver shown above are only examples, and the specific steps executed by the processor and transceiver can be referred to the methods described above. The dashed lines in Figure 15 indicate optional parts.

[0362] In another possible implementation, in the communication device shown in Figure 14, the processing module 1401 can be one or more logic circuits, and the transceiver module 1402 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 1402 can also be a transmitting module and a receiving module. The transmitting module can be an output interface, and the receiving module can be an input interface. The transmitting module and the receiving module are integrated into one module, such as an input / output interface.

[0363] Figure 16 is a schematic diagram of another structure of the communication device provided in an embodiment of this application. As shown in Figure 16, the communication device includes a logic circuit 1601 and an interface 1602. That is, the processing module 1401 can be implemented using the logic circuit 1601, and the transceiver module 1402 can be implemented using the interface 1602. The logic circuit 1601 can be a chip, a processing circuit, an integrated circuit, or a system-on-chip (SoC) chip, etc., and the interface 1602 can be a communication interface, an input / output interface, pins, etc. For example, Figure 16 illustrates the communication device as a chip, which includes the logic circuit 1601 and the interface 1602.

[0364] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 1601 can be used to execute the functions or steps implemented by the processing module 1401 shown in FIG. 14, and the interface 1602 can be used to execute the functions or steps implemented by the transceiver module 1402 shown in FIG. 14. For a detailed description of the logic circuit 1601 and the interface 1602, please refer to FIG. 14 or the method embodiment shown above, which will not be detailed here.

[0365] 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 it can implement the method provided in the embodiments of this application in software form, etc., and the embodiments of this application do not limit it in this way.

[0366] Furthermore, embodiments of this application also provide a communication system, which includes a first station and a second station, the first station and the second station being used to perform the methods in any of the foregoing embodiments.

[0367] This application also provides a computer program for implementing the operations and / or processes performed by various sites in the methods provided in this application.

[0368] 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 various communication devices in the methods provided in this application.

[0369] 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 various entities in the method provided in this application to be executed.

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

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

[0372] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0373] If the integrated module is implemented as a software functional module 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.

Claims

1. A link-adaptive communication method, characterized in that, The method includes: The first station generates a first radio frame, which includes a first control information field. The first control information field includes first information, which is used to indicate that the modulation type recommended by the first station is unbalanced modulation (UEQM) or balanced modulation (EQM). The first control information field is used to carry link adaptive information. The first station sends the first wireless frame.

2. A link-adaptive communication method, characterized in that, The method includes: The second station receives a first radio frame, which includes a first control information field. The first control information field includes first information, which is used to indicate that the modulation type recommended by the first station is unbalanced modulation (UEQM) or equalized modulation (EQM). The first control information field is used to carry link adaptive information. The second station parses the first wireless frame.

3. The method according to claim 1 or 2, characterized in that, The first control information field also includes the first spatial stream number (NSS) information; When the modulation type indicated by the first information is EQM, the first NSS information is used to indicate the NSS recommended by the first site; or... When the modulation type indicated by the first information is the UEQM, the first NSS information is used to indicate the NSS recommended by the first site, and the difference between the coding and modulation strategy MCS corresponding to the first spatial stream SS and the MCS corresponding to the basic SS. The first SS is the SS recommended by the first site other than the basic SS.

4. The method according to claim 1 or 2, characterized in that, The first information is also used to indicate the NSS recommended by the first site; or, The first information is also used to indicate the NSS recommended by the first site, and the difference between the MCS corresponding to the first SS and the MCS corresponding to the base SS, wherein the first SS is the SS recommended by the first site other than the base SS.

5. The method according to any one of claims 1-4, characterized in that, The first control information field also includes MCS information, which is used to indicate the MCS corresponding to the first SS, or the MCS information is used to indicate the MCS corresponding to the base SS.

6. The method according to any one of claims 1-5, characterized in that, The first information is also used to indicate the signal-to-noise ratio (SNR) corresponding to each SS recommended by the first site; or, The first information is also used to indicate the difference between the SNR corresponding to the first SS and the SNR corresponding to the second SS, wherein the first SS and the second SS are SSs recommended by the first site.

7. The method according to any one of claims 1-5, characterized in that, The first information is also used to indicate the difference between the SNR of the first frequency domain resource and the SNR of the second frequency domain resource, wherein the first frequency domain resource and the second frequency domain resource are frequency domain resources corresponding to the physical layer protocol data unit (PPDU) used for measurement.

8. The method according to any one of claims 1-7, characterized in that, The first information is also used to indicate whether the PPDU used for measurement employs beamforming (BF).

9. The method according to any one of claims 1-8, characterized in that, The first control information field also includes first resource unit (RU) type information, which indicates that the recommended RU type for the first site is either a discrete resource unit (DRU) or a conventional resource unit (RRU).

10. The method according to any one of claims 1-9, characterized in that, The first control information field is included in the first control field in the first radio frame. The first control field also includes a control identifier ID field, which is used to indicate that the first control information field is used for ultra-high reliability UHR.

11. The method according to any one of claims 1-9, characterized in that, The first control information field is included in the first control field in the first radio frame. The first control field also includes a control ID field, and the value of the control ID field is 2. In the first control information field: the value of B0 is 0, and the value of B24 is 1. The values ​​of B0 and B24 are used to indicate that the first control information field is used for UHR; or, In the first control information field: the value of B0 is 1, the value of B22 is 1, and the value of B25 is 1. The values ​​of B0, B22, and B25 are used to indicate that the first control information field is used for UHR.

12. The method according to claim 10 or 11, characterized in that, The first control information field occupies 26 bits.

13. The method according to any one of claims 1-9, characterized in that, The first control information field also includes a link adaptive LA variant field, which indicates that the first control information field is used for UHR.

14. The method according to any one of claims 1-9, characterized in that, The first control information field is included in the High Throughput Control (HTC) field in the first radio frame. The HTC field includes a Special Control ID field. When the value of the Special Control ID field is a special value, the first control information field is included in the extended portion of the HTC field.

15. The method according to claim 13 or 14, characterized in that, The first control information field occupies 26 or more bits.

16. The method according to claim 1, characterized in that, The method further includes: The first station receives a second radio frame, which is a request frame in the request-type MCS feedback MFB.

17. The method according to claim 2, characterized in that, The method further includes: The second station sends a second radio frame, which is a request frame in a request-type MFB.

18. The method according to claim 16 or 17, characterized in that, The second radio frame includes a second control information field, which includes at least one of the following: Indicates that the second control information field is used for UHR; The requested RU type is either DRU or RRU; The modulation type requested is either the UEQM or the EQM; The requested UEQM type is either SD UEQM or FD UEQM; Instructions to retrieve the MCS corresponding to each spatial flow in different spatial flows, or the differences between the MCS corresponding to different spatial flows; Instructions to retrieve the SNR corresponding to each spatial flow in different spatial flows, or the differences between the SNRs corresponding to different spatial flows; This instruction requests the SNR corresponding to each frequency domain resource in different frequency domains, or the difference between the SNRs corresponding to different frequency domain resources.

19. A link-adaptive communication method, characterized in that, The method includes: The second station generates a second radio frame, which includes a second control information field. The second control information field includes second information, which is used to indicate that the modulation type requested by the second station is unbalanced modulation (UEQM) or balanced modulation (EQM). The second control information field is used to request link adaptation information. The second station sends the second radio frame.

20. A link-adaptive communication method, characterized in that, The method includes: The first station receives a second radio frame, the second radio frame includes a second control information field, the second control information field includes second information, the second information is used to indicate that the modulation type requested by the second station is unbalanced modulation UEQM or balanced modulation EQM, and the second control information field is used to request link adaptation information. The first station parses the second wireless frame.

21. The method according to claim 19 or 20, characterized in that, The second information is also used to indicate that the type of UEQM requested by the second site is spatial domain SD UEQM or frequency domain FD UEQM.

22. The method according to any one of claims 19-21, characterized in that, The second information is also used to request whether the Physical Layer Protocol Data Unit (PPDU) used for measurement employs beamforming (BF).

23. The method according to any one of claims 19-22, characterized in that, The second control information field also includes second spatial stream number (NSS) information, which is used to indicate the NSS requested by the second site.

24. The method according to any one of claims 19-23, characterized in that, The second control information field also includes second resource unit (RU) type information, which indicates whether the RU type requested by the second site is a discrete resource unit (DRU) or a conventional resource unit (RRU).

25. The method according to any one of claims 19-24, characterized in that, The second information is also used to indicate at least one of the following: Instructions to retrieve the coding and modulation schemes (MCS) corresponding to each spatial stream in different spatial streams, or the differences between the MCS corresponding to different spatial streams; The instruction requests the signal-to-noise ratio (SNR) of each spatial stream in different spatial streams, or the difference in SNR between different spatial streams. This instruction requests the SNR corresponding to each frequency domain resource in different frequency domains, or the difference between the SNRs corresponding to different frequency domain resources.

26. The method according to any one of claims 19-25, characterized in that, The second control information field is included in the second control field in the second radio frame. The second control field also includes a control identifier ID field, which is used to indicate that the second control information field is used for ultra-high reliability UHR.

27. The method according to any one of claims 19-25, characterized in that, The second control information field is included in the second control field in the second radio frame. The second control field also includes a control ID field, the value of which is 2. In the second control information field: the value of B0 is 0, and the value of B24 is 1. The values ​​of B0 and B24 are used to indicate that the second control information field is used for UHR; or, In the second control information field: the value of B0 is 1, the value of B22 is 1, and the value of B25 is 1. The values ​​of B0, B22, and B25 are used to indicate that the second control information field is used for UHR.

28. The method according to any one of claims 19-25, characterized in that, The second control information field also includes a link adaptive LA variant field, which indicates that the second control information field is used for UHR.

29. The method according to any one of claims 19-25, characterized in that, The second control information field is included in the High Throughput Control (HTC) field in the first radio frame. The HTC field includes a Special Control ID field. When the value of the Special Control ID field is a special value, the second control information field is included in the extended portion of the HTC field.

30. A communication device, characterized in that, Includes a processor for performing the method as described in any one of claims 1-29.

31. A communication device, characterized in that, Includes logic circuits and interfaces, wherein the logic circuits and interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used for performing the method as described in any one of claims 1-29.

32. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed, performs the method as described in any one of claims 1-29.

33. A computer program product, characterized in that, When the computer program product is executed, the method described in any one of claims 1-29 is performed.

Images