Communication method and communication device

Abstract

The invention relates to the technical field of wireless communication, in particular to a communication method and a communication device. The method comprises the following steps: a first site and a second site determine a first LDPC code length according to a transmission mode, or the second site determines the first LDPC code length according to operation information. A first station sends a PPDU, correspondingly, a second station receives the PPDU, and the PPDU adopts a first LDPC code length. According to the application, an IEEE (Institute of Electrical and Electronic Engineers) protocol can be supported, such as an IEEE 802.11 be protocol, an IEEE 802.11 bn protocol, an IEEE integrated millimeter wave protocol, an IEEE 802.15 protocol or an IEEE 802.11 bf / sensing protocol; the technical scheme provided by the embodiment of the invention can also be applied to a satellite flash system and supports a satellite flash standard protocol.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and communication device. Background Technology

[0002] Wireless local area networks (WLANs) have evolved from 802.11a / b / g to 802.11n, 802.11ac, 802.11ax, 802.11be, and 802.11bn. The 802.11a / b / g protocols are collectively referred to as non-high throughput (non-HT), the 802.11n protocol as high throughput (HT), the 802.11ac protocol as very high throughput (VHT), the 802.11ax protocol as high efficient (HE), the 802.11be protocol as extremely high throughput (EHT), and the 802.11bn protocol as ultra-high reliability (UHR). Low-density parity check (LDPC) coding was introduced starting with 802.11n. LDPC codes have the following advantages: they can achieve good error performance without deep interleaving; they have better frame error rate performance; error level is greatly reduced; decoding is not grid-based; they support parallel decoding and have low decoding latency.

[0003] LDPC codes are a type of linear block code with a sparse parity-check matrix, characterized by flexible structure and low decoding complexity. LDPC codes can be used as error-correcting codes in communication systems, thereby improving the reliability and power utilization of channel transmission.

[0004] LDPC codes come in various codeword lengths, so choosing the appropriate LDPC codeword length for a site is a problem that urgently needs to be solved. Summary of the Invention

[0005] This application provides a communication method and a communication device that improves the flexibility of a site in determining the code length of a low-density parity check (LDPC).

[0006] In a first aspect, embodiments of this application provide a communication method applied to a first site, which includes a wireless local area network (WLAN) device (including Wi-Fi devices or devices involved in the StarFlash Alliance, etc.), or a chip, functional module, processing system, or communication component that can be disposed in the WLAN device. The method includes:

[0007] The first low-density parity check (LDPC) code length is determined according to the transmission method, which includes unicast transmission or multicast transmission; a physical protocol data unit (PPDU) is sent, which adopts the first LDPC code length.

[0008] If a PPDU includes a data field, the data field uses the first LDPC code length.

[0009] In this embodiment of the application, the first station determines the first LDPC code length according to different transmission methods, so that the first station can flexibly determine the LDPC code length corresponding to the transmission method, making the first LDPC code length more compatible with the transmission method.

[0010] In one possible implementation, the method further includes: sending first capability information, the first capability information being used to indicate whether a first site supports a second LDPC code length, the second LDPC code length being greater than 1944; and receiving second capability information, the second capability information being used to indicate whether a second site supports a second LDPC code length.

[0011] The second LDPC code length can include one or more of the following: 3888 (i.e., 1944*2), 5832 (i.e., 1944*3), and 7776 (i.e., 1944*4). For example, the second LDPC code length includes 2×LDPC. Further examples include 2×LDPC and 3×LDPC, etc., which will not be listed here. 3888 can also be called 2×1944 code length, 5832 can also be called 3×1944 code length, and 7776 can also be called 4×1944 code length, or simply referred to as 2× code length, 3× code length, and 4× code length, or simply 2×LDPC, 3×LDPC, and 4×LDPC, respectively. The code lengths listed here are only examples; as the standard progresses, later sites may support even longer code lengths. For example, the second LDPC code length can also include 2×1296 or 3×1296, etc., which will not be listed here.

[0012] Optionally, the first capability information is included in the management frame. Optionally, the second capability information is included in the management frame. The embodiments of this application do not limit the order in which the first station sends the first capability information and the second station sends the second capability information.

[0013] When the first site is an access point (AP), the management frame may include, but is not limited to, at least one of a beacon frame, probe response frame, association response frame, or reassociation response frame. When the second site is a non-access point station (non-AP STA), the management frame may include, but is not limited to, at least one of a probe request frame, association request frame, or reassociation request frame.

[0014] Typically, both the transmitting and receiving ends must support three code lengths: 648, 1296, and 1944. The transmitting and receiving ends determine the LDPC code length to use based on a first code length parameter table. However, the above scheme does not consider introducing longer LDPC code lengths, and whether a site supports a longer LDPC code length is optional. Therefore, in this embodiment, the sites interact to determine whether a second LDPC code length is supported, allowing both the transmitting and receiving ends to clearly know whether the other end supports the second LDPC code length.

[0015] In one possible implementation, determining the first LDPC code length according to the transmission mode includes: when the transmission mode is multicast transmission, determining the first LDPC code length according to a first code length parameter table, wherein the first code length parameter table does not include LDPC code lengths greater than 1944, or in other words, the first code length parameter table includes LDPC code lengths no greater than 1944.

[0016] The first code length parameter table may include one or more of 648, 1296, or 1944, for example, the first code length parameter table may include 648, 1296, and 1944. The first LDPC code length determined by the first code length parameter table is 648, 1296, or 1944.

[0017] Typically, both the transmitting and receiving ends must support LDPC code lengths of 648, 1296, and 1944. The transmitting and receiving ends determine the LDPC code length to use based on a first code length parameter table. However, the above scheme does not consider introducing longer LDPC code lengths, and whether a site supports a longer LDPC code length is optional. This is especially true in multicast (multicast or broadcast) transmission, where there are multiple receiving ends (i.e., multiple second sites). Multicast transmission differs from unicast transmission. In unicast transmission, the transmitting and receiving ends have a unified understanding of their capabilities, but in multicast transmission, it is unclear whether multiple receiving ends can use longer LDPC code lengths, or whether the transmitting end uses a longer LDPC code length. Therefore, in multicast transmission, regardless of whether the first site supports a second LDPC code length, the first site determines the first LDPC code length based on the first code length parameter table. Similarly, the second sites also determine the first LDPC code length based on the first code length parameter table, thus ensuring that the transmitting and receiving ends maintain consistency in the LDPC code length used, thereby guaranteeing that the receiving end can correctly decode the PPDU sent by the transmitting end.

[0018] In one possible implementation, determining the first LDPC code length according to the transmission mode includes: when the transmission mode is multicast transmission, determining the first LDPC code length according to a first code length parameter table, wherein the first code length parameter table does not include LDPC code lengths greater than 3888, or in other words, the LDPC code lengths included in the first code length parameter table are not greater than 3888.

[0019] In this implementation, both the transmitting and receiving ends must support four code lengths: 648, 1296, 1944, and 3888. In this case, when the transmission method is multicast, the first station determines the first LDPC code length based on a code length parameter table that includes one or more code lengths of 3888, 1944, 1296, or 648.

[0020] In one possible implementation, where the transmission method is multicast transmission, the method further includes: sending operation information, which indicates whether the LDPC code length used by the first station is a second LDPC code length, or the operation information indicates whether the first station uses a second code length parameter table, which includes a second LDPC code length.

[0021] The LDPC code length used by the first site refers to the LDPC code length used by the first site when performing one or more transmissions in multicast or broadcast, or the code length parameter table used.

[0022] Optionally, operational information is included in the signaling (SIG) field of the management frame or PPDU. This signaling field includes general signaling fields. Alternatively, the signaling field includes signaling fields corresponding to the standard to which the PPDU belongs, such as the UHR-SIG field for an Ultra High Reliability (UHR) PPDU.

[0023] When the operation information indicates that the first site uses the second LDPC code length, the first LDPC code length and the second LDPC code length are the same. When the operation information indicates that the first site uses the second code length parameter table, the first LDPC code length may be the same as or different from the second LDPC code length.

[0024] In this embodiment of the application, when the transmission method is multicast transmission, the first station sends operation information so that the second station can clearly know the LDPC code length it uses. Thus, the first and second stations maintain consistency in the LDPC code length they use, and consequently, the second station can correctly decode the PPDU sent by the first station (i.e., the PPDU encoded using the first LDPC code length).

[0025] In one possible implementation, where the transmission method is multicast, sending a PPDU includes sending a PPDU containing operational information, such as the SIG field in the PPDU.

[0026] In one possible implementation, sending operation information includes: sending operation information based on the LDPC code length supported by the first site and the second capability information.

[0027] In one possible implementation, sending operation information includes: sending operation information based on first capability information and second capability information.

[0028] In this embodiment of the application, the first station sends operation information by combining the first capability information and the second capability information, which can make the LDPC code length used by the sender and receiver more compatible with their respective capabilities, enabling the sender and receiver to use a longer LDPC code length.

[0029] In one possible implementation, the operation information is used to indicate whether the LDPC code length used by the first multicast in at least two multicasts corresponding to the first site is the second LDPC code length, or the operation information is used to indicate whether the second multicast in at least two multicasts corresponding to the first site uses the second code length parameter table.

[0030] In this embodiment of the application, by combining the above information with different multicast indications, it is possible to ensure that an appropriate LDPC code length is used in the multicast as much as possible, so that the LDPC code length determined in each multicast is more accurate.

[0031] In one possible implementation, the operation information includes a predefined identifier (ID); the predefined ID is used to indicate that the first station uses a second LDPC code length; or, the predefined ID is used to indicate that the first station uses a second code length parameter table.

[0032] In this embodiment of the application, the above information is indicated by a predefined ID, which not only enables both the sender and receiver to clearly understand the LDPC code length, but also saves signaling overhead.

[0033] In one possible implementation, when the transmission mode is unicast, the first modulation and coding scheme (MCS) field occupies bits Bx1 to By1, where x1 and y1 are both positive integers and y1 is greater than x1; when the transmission mode is multicast, Bx1 to By1 carry operation information and the second MCS field.

[0034] Bx1 to By1 represent the position of the first MCS within a field. For example, the first MCS field is contained within the SIG field of the PPDU, and the bits occupied by the first MCS field are bits x1 to y1 of the SIG field. For multicast transmission, bits x1 to y1 of the SIG field carry operation information and the second MCS field.

[0035] In unicast and multicast transmissions, the number of bits occupied by the MCS field differs, and the content indicated by the index in the MCS field can also differ. For example, in multicast transmission, the number of bits occupied by the second MCS field is less than that of the first MCS field. The bits saved in the second MCS field can be used to carry operational information. Thus, the purpose of indicating the LDPC code length is achieved without increasing signaling overhead.

[0036] In one possible implementation, when the transmission mode is unicast, the first number of spatial streams (NSS) field occupies bits Bx2 to By2, where x2 and y2 are both positive integers and y2 is greater than x2; when the transmission mode is multicast, Bx2 to By2 carry operation information and the second NSS field.

[0037] In one possible implementation, the operation information is carried in the MCS field; the index in the MCS field is a first value, which indicates that the LDPC code length used by the first station is a second LDPC code length, or the first station uses a second code length parameter table; the index in the MCS field is a second value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses a first code length parameter table.

[0038] Optionally, the index in the MCS field can indicate different content in unicast and multicast transmissions.

[0039] In this embodiment of the application, for multicast transmission, since the transmission rate is low, the index of the MCS can be reused to indicate the above information, indicating the LDPC code length while minimizing signaling overhead.

[0040] In one possible implementation, the operation information is carried in the NSS field; the index in the NSS field is a third value, which indicates that the LDPC code length used by the first station is the second LDPC code length, or the first station uses the second code length parameter table; the index in the NSS field is a fourth value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses the first code length parameter table.

[0041] Optionally, the content indicated by the index in the NSS field can differ between unicast and multicast transmissions.

[0042] In one possible implementation, determining the first LDPC code length based on the transmission method includes: if the transmission method is unicast transmission and the first and second stations support the second LDPC code length, determining the first LDPC code length based on a second code length parameter table; or, if the transmission method is unicast transmission and the first or second station does not support the second LDPC code length, determining the first LDPC code length based on a first code length parameter table.

[0043] In this embodiment, the LDPC code length or the code length parameter table used to determine the LDPC code length may differ depending on the transmission method. For unicast transmission, the sending and receiving parties can determine whether to use a code length parameter table that includes a longer code length to select the LDPC code length by combining the other end's and their own support for a second LDPC code length. This not only ensures that the sending and receiving parties use a more suitable LDPC code length, but also ensures that the LDPC code length determined by the sending and receiving parties is consistent.

[0044] Secondly, embodiments of this application provide a communication method applied to a first site, which includes a WLAN device (including a Wi-Fi device or devices involved in the StarFlash Alliance, etc.), or a chip, functional module, processing system, or communication component that can be disposed in the WLAN device. The method includes:

[0045] The first station determines the operation information, which indicates whether the LDPC code length used by the first station is the second LDPC code length, or whether the operation information indicates whether the first station uses the second code length parameter table, which includes the second LDPC code length, and the second LDPC code length is greater than 1944; the first station sends the operation information.

[0046] In one possible implementation, the first station uses multicast transmission.

[0047] In one possible implementation, the operation information includes a predefined ID; the predefined ID is used to indicate that the first station uses a second LDPC code length; or, the predefined ID is used to indicate that the first station uses a second code length parameter table.

[0048] In one possible implementation, when the transmission method is unicast, the first MCS field occupies bits Bx1 to By1, where x1 and y1 are both positive integers and y1 is greater than x1; when the transmission method is multicast, Bx1 to By1 carry operation information and the second MCS field.

[0049] In one possible implementation, when the transmission method is unicast, the first NSS field occupies bits Bx2 to By2, where x2 and y2 are both positive integers and y2 is greater than x2; when the transmission method is multicast, Bx2 to By2 carry operation information and the second NSS field.

[0050] In one possible implementation, the operation information is carried in the MCS field; the index in the MCS field is a first value, which indicates that the LDPC code length used by the first station is a second LDPC code length, or the first station uses a second code length parameter table; the index in the MCS field is a second value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses a first code length parameter table.

[0051] In one possible implementation, the operation information is carried in the NSS field; the index in the NSS field is a third value, which indicates that the LDPC code length used by the first station is the second LDPC code length, or the first station uses the second code length parameter table; the index in the NSS field is a fourth value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses the first code length parameter table.

[0052] In one possible implementation, the operational information is contained in the signaling field of the management frame or PPDU.

[0053] In one possible implementation, the method further includes: sending first capability information, the first capability information being used to indicate whether a first site supports a second LDPC code length, the second LDPC code length being greater than 1944; and receiving second capability information, the second capability information being used to indicate whether a second site supports a second LDPC code length.

[0054] In one possible implementation, determining the operation information includes: determining the operation information based on the first capability information and the second capability information.

[0055] For an explanation of the second aspect, please refer to the first aspect; it will not be repeated here.

[0056] Thirdly, embodiments of this application provide a communication method applied to a second site, which includes a WLAN device (including Wi-Fi devices or devices involved in the StarFlash Alliance, etc.), or a chip, functional module, processing system, or communication component that can be disposed in the WLAN device. The method includes:

[0057] The first LDPC code length is determined according to the transmission method, which includes unicast transmission or multicast transmission; PPDU is received, wherein the PPDU adopts the first LDPC code length.

[0058] In one possible implementation, the method further includes: receiving first capability information, the first capability information being used to indicate whether a first site supports a second LDPC code length, the second LDPC code length being greater than 1944; and sending second capability information, the second capability information being used to indicate whether a second site supports a second LDPC code length.

[0059] In one possible implementation, determining the first LDPC code length according to the transmission mode includes: when the transmission mode is multicast transmission, determining the first LDPC code length according to a first code length parameter table, wherein the first code length parameter table does not include LDPC code lengths greater than 1944, or in other words, the first code length parameter table includes LDPC code lengths no greater than 1944.

[0060] In one possible implementation, where the transmission method is multicast transmission, the method further includes: receiving operation information, which indicates whether the LDPC code length used by the first station is a second LDPC code length, or the operation information indicates whether the first station uses a second code length parameter table, which includes a second LDPC code length.

[0061] In one possible implementation, where the transmission method is multicast transmission, receiving a PPDU includes receiving a PPDU that includes operation information.

[0062] In one possible implementation, determining the first LDPC code length based on the transmission mode includes: in the case of multicast transmission, determining the first LDPC code length based on operation information.

[0063] In one possible implementation, the operation information is used to indicate whether the LDPC code length used by the first multicast in at least two multicasts corresponding to the first site is the second LDPC code length, or the operation information is used to indicate whether the second multicast in at least two multicasts corresponding to the first site uses the second code length parameter table.

[0064] In one possible implementation, the operation information includes a predefined ID; the predefined ID is used to indicate that the first station uses a second LDPC code length; or, the predefined ID is used to indicate that the first station uses a second code length parameter table.

[0065] In one possible implementation, when the transmission method is unicast, the first MCS field occupies bits Bx1 to By1, where x1 and y1 are both positive integers and y1 is greater than x1; when the transmission method is multicast, Bx1 to By1 carry operation information and the second MCS field.

[0066] In one possible implementation, when the transmission method is unicast, the first NSS field occupies bits Bx2 to By2, where x2 and y2 are both positive integers and y2 is greater than x2; when the transmission method is multicast, Bx2 to By2 carry operation information and the second NSS field.

[0067] In one possible implementation, the operation information is carried in the MCS field; the index in the MCS field is a first value, which indicates that the LDPC code length used by the first station is a second LDPC code length, or the first station uses a second code length parameter table; the index in the MCS field is a second value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses a first code length parameter table.

[0068] In one possible implementation, the operation information is carried in the NSS field; the index in the NSS field is a third value, which indicates that the LDPC code length used by the first station is the second LDPC code length, or the first station uses the second code length parameter table; the index in the NSS field is a fourth value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses the first code length parameter table.

[0069] In one possible implementation, determining the first LDPC code length based on the transmission method includes: if the transmission method is unicast transmission and the first and second stations support the second LDPC code length, determining the first LDPC code length based on a second code length parameter table; or, if the transmission method is unicast transmission and the first or second station does not support the second LDPC code length, determining the first LDPC code length based on a first code length parameter table.

[0070] Fourthly, embodiments of this application provide a communication method applied to a second site, which includes a WLAN device (including a Wi-Fi device or devices involved in the StarFlash Alliance, etc.), or a chip, functional module, processing system, or communication component that can be disposed in the WLAN device. The method includes:

[0071] Receive operation information, which indicates whether the LDPC code length used by the first station is the second LDPC code length, or the operation information indicates whether the first station uses a second code length parameter table, the second code length parameter table including a second LDPC code length, the second LDPC code length being greater than 1944; determine the first LDPC code length according to the operation information.

[0072] In one possible implementation, the second station uses multicast transmission.

[0073] In one possible implementation, the operation information includes a predefined ID; the predefined ID is used to indicate that the first station uses a second LDPC code length; or, the predefined ID is used to indicate that the first station uses a second code length parameter table.

[0074] In one possible implementation, when the transmission method is unicast, the first MCS field occupies bits Bx1 to By1, where x1 and y1 are both positive integers and y1 is greater than x1; when the transmission method is multicast, Bx1 to By1 carry operation information and the second MCS field.

[0075] In one possible implementation, when the transmission method is unicast, the first NSS field occupies bits Bx2 to By2, where x2 and y2 are both positive integers and y2 is greater than x2; when the transmission method is multicast, Bx2 to By2 carry operation information and the second NSS field.

[0076] In one possible implementation, the operation information is carried in the MCS field; the index in the MCS field is a first value, which indicates that the LDPC code length used by the first station is a second LDPC code length, or the first station uses a second code length parameter table; the index in the MCS field is a second value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses a first code length parameter table.

[0077] In one possible implementation, the operation information is carried in the NSS field; the index in the NSS field is a third value, which indicates that the LDPC code length used by the first station is the second LDPC code length, or the first station uses the second code length parameter table; the index in the NSS field is a fourth value, which indicates that the LDPC code length used by the first station is less than or equal to 1944, or the first station uses the first code length parameter table.

[0078] Fifthly, embodiments of this application provide a communication device for executing the methods in any one of the first to fourth 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 fourth aspects or any possible implementations thereof.

[0079] Sixthly, embodiments of this application provide a communication device, which includes a processor and a transceiver. The processor is used to execute the processing steps in the method described in any one of the first to fourth aspects or any possible implementation thereof, and the transceiver is used to execute the sending and receiving steps in the method described in any one of the first to fourth aspects or any possible implementation thereof.

[0080] In a seventh aspect, embodiments of this application provide a communication device including a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to input and / or output information, and the logic circuit is used to perform processing steps in the method described in any one of the first to fourth aspects or any possible implementation thereof.

[0081] Eighthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods described in any of the first to fourth aspects or any possible implementation thereof to be executed.

[0082] Ninthly, embodiments of this application provide a computer program product that, when run on a computer, causes the methods described in any of the first to fourth aspects or any possible implementation thereof to be executed.

[0083] In a tenth aspect, embodiments of this application provide a communication system comprising a first station and a second station. The first station is configured to perform the method described in the first aspect, the second aspect, or any possible implementation thereof, and the second station is configured to perform the method described in the third aspect, the fourth aspect, or any possible implementation thereof. Attached Figure Description

[0084] Figure 1 This application provides a schematic diagram of the structure of a communication system according to an embodiment of the present application.

[0085] Figure 2A A flowchart illustrating a communication method provided in an embodiment of this application;

[0086] Figure 2B A flowchart illustrating another communication method provided in an embodiment of this application;

[0087] Figure 2C A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0088] Figure 3 This is a schematic diagram of the structure of a capability information element provided in an embodiment of this application;

[0089] Figure 4 This is a schematic diagram of the structure of an operation parameter element provided in an embodiment of this application;

[0090] Figure 5 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0091] Figure 6A A schematic diagram of the structure of a signaling field provided in an embodiment of this application;

[0092] Figure 6B This is a schematic diagram of another signaling field structure provided in an embodiment of this application;

[0093] Figure 7 This is a schematic diagram illustrating the structure of another signaling field provided in an embodiment of this application;

[0094] Figure 8 This is a schematic diagram illustrating the structure of another signaling field provided in an embodiment of this application;

[0095] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0096] Figure 10 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0097] Figure 11 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0098] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are only used to distinguish different objects and not to limit the order, sequence, priority, or importance of multiple objects. In the embodiments of this application, "multiple" refers to two or more. 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 device 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 devices. Additionally, the character " / ," unless otherwise specified, generally indicates that the preceding and following objects are in an "or" relationship.

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

[0100] 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 or 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, or 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".

[0101] In this application, transmission includes sending and / or receiving.

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

[0103] The technical solutions provided in this application can be applied to wireless local area network (WLAN) systems, supporting Institute of Electrical and Electronics Engineers (IEEE) protocols (or standards), such as IEEE 802.11be / Wi-Fi 7 / EHT protocol, IEEE 802.11bn / Ultra High Reliability (UHR) / Wi-Fi 8 protocol, IEEE Integrated Millimeter Wave (IMMW) protocol, IEEE 802.15 / Ultra Wideband (UWB) protocol, or IEEE 802.11bf / Sensing protocol; the technical solutions provided in this application can also be applied to SparkLink (SL) systems, supporting the SparkLink (or NearLink) protocol. The technical solutions provided in 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 emerging in future communication development. For example, V2X can include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communication.

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

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

[0106] In one possible implementation, 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 non-access point station (non-AP STA).

[0107] An Access Point (AP) is a device with wireless communication capabilities that supports communication, sensing, or power transmission using WLAN protocols. It has the function of communicating or sensing with other devices in a WLAN network (such as non-access point stations (non-APSTAs) or other access points), and can also communicate, sense, or transmit power with devices in other networks. 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 802.11 series protocols or subsequent protocols. 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. It is mainly deployed in homes, inside buildings, and within campuses, with a typical coverage radius of tens to hundreds of meters. Of course, it can also be deployed outdoors. Another example is an AP, which can be a communication server, router, switch, bridge, or other communication entity; APs can include various forms of macro base stations, micro base stations, repeaters, etc.

[0108] A non-AP STA is a device with wireless communication capabilities that supports communication, sensing, or power transmission using the WLAN protocol. 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 non-AP STA is any user communication device that allows a user to communicate with an AP (Access Point) or sense or transmit power, thereby communicating with the WLAN. This wireless communication device can be a complete device, or it can be 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 of this application under the control of the chips, processing systems, or functional modules. For example, a non-AP 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, a non-AP 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.

[0109] The communication system provided in this application includes access points and sites. For example, this application can be applied to scenarios of communication or sensing between an AP and a non-AP STA, between APs, or between non-AP STAs in a WLAN, and this application does not limit this. Optionally, an AP can communicate or sense a single non-AP STA, or an AP can communicate or sense multiple non-AP STAs simultaneously. Specifically, communication or sensing between an AP and multiple non-AP STAs can be further 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. The communication between the AP and non-AP STAs, between APs, and between non-AP STAs can support WLAN communication protocols, which can include protocols of the IEEE 802.11 series, such as the 802.11bn protocol, and of course, protocols after 802.11bn are also applicable.

[0110] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. The communication system may include one or more access points (APs) and one or more non-AP STAs. Figure 1 The diagram illustrates two access points, such as AP1 and AP2, and three non-APSTAs, such as non-APSTA1, non-APSTA2, and non-APSTA3. As an example, the method provided in this application can be applied to data communication, sensing, or power transmission between an AP and one or more non-APSTAs, such as... Figure 1 The communication or sensing between AP1 and non-APSTA1 shown, for example... Figure 1 The example illustrates communication or sensing between AP1 and non-APSTA2. As another example, the method provided in this application embodiment can be applied to communication between APs, such as... Figure 1 The example illustrates communication or sensing between AP1 and AP2. As another example, the method provided in this application embodiment can be applied to communication or sensing between non-AP STAs, such as... Figure 1 The communication or sensing between non-APSTA2 and non-APSTA3 shown.

[0111] Figure 1 The example of a non-AP STA (phone) and an AP (router) is provided and is not intended to limit the types of APs and non-AP STAs in this application. Furthermore, Figure 1The number of APs and non-AP STAs shown are merely examples. In a specific implementation, the number of APs or non-AP STAs may be more or less, and this application embodiment does not limit this.

[0112] The following describes the terms used in the embodiments of this application.

[0113] 1. Low-density parity check (LDPC) code

[0114] LDPC codes are a class of linear block codes with sparse parity-check matrices, characterized by flexible structure and low decoding complexity. LDPC codes can be used as error correction codes in the aforementioned communication systems, thereby improving the reliability and power utilization of channel transmission. LDPC codes offer advantages such as achieving good error performance without deep interleaving, better frame error rate performance, significantly reduced error levels, non-grid-based decoding, support for parallel decoding, and low decoding latency.

[0115] LDPC codes include various codeword lengths, such as 648 bits, 1296 bits, and 1944 bits.

[0116] In this embodiment of the application, LDPC codes can also support code lengths longer than 1944 bits. For example, the code length of an LDPC code can be twice 1944 (i.e., 3888 bits), and is also simply referred to as 2×1944 code length, or 2× code length, or 2×LDPC code length, or 2x LDPC code length, or 2×LDPC, etc. As another example, the code length of an LDPC code can be three times 1944 (i.e., 5832 bits), and is also simply referred to as 3×1944 code length, or 3× code length, or 3×LDPC code length, or 3x LDPC code length, or 3×LDPC, etc. As yet another example, the code length of an LDPC code can be four times 1944 (i.e., 7776 bits), and is also simply referred to as 4×1944 code length, or 4× code length, or 4×LDPC code length, or 4x LDPC code length, or 4×LDPC, etc. Specific values ​​for even longer code lengths are not listed here. This application does not limit the representation of longer code lengths in its embodiments.

[0117] 2. First code length parameter table

[0118] The site can determine the LDPC code length to be used based on the first code length parameter table, which includes the correspondence between the number of codeword bits in this data transmission and the LDPC code length.

[0119] As an example, the first code length parameter table does not include LDPC code lengths greater than 1944, or in other words, the first code length parameter table includes LDPC code lengths no greater than 1944. For example, the first code length parameter table includes at least one of the following LDPC code lengths: 648, 1296, or 1944. That is to say, the site supports the above three code lengths by default, or the site must support the above three code lengths.

[0120] For example, the total number of codeword bits in this data transmission is determined by the number of OFDM symbols required for this data transmission and the number of codeword bits carried by each OFDM symbol.

[0121] For example, the total number of codeword bits in this data transmission can satisfy:

[0122] N avbits =N CBPS ·N SYM

[0123] Where, N CBPS N represents the number of codeword bits carried by each OFDM symbol. SYM Indicates the number of OFDM nodes required for data transmission. N SYM It can be determined by the length of the data packet, the space-time coding mode of the data packet, and the number of data bits carried by each OFDM symbol.

[0124] For example, N SYM It can satisfy:

[0125]

[0126] Where length represents the length of the data packet, in bytes. STBC This indicates the space-time encoding mode of the data packet (this value is 1 if space-time encoding is not used, otherwise it is 2). N DBPS This indicates the number of data bits carried by each OFDM symbol. This indicates rounding up to the nearest integer.

[0127] For example, the first code length parameter table can be as shown in Table 1.

[0128] Table 1

[0129]

[0130] In Table 1, R represents the bit rate, and N... pld This indicates the length of the data bits after adding the 16-bit cyclic redundancy code (CRC) to the current data transmission. This N... pld It can satisfy:

[0131] Npld =length × 8 + 16

[0132] As shown in Table 1, when 648 <N avbits When N ≤ 1296, if avbits ≥N pld +1464·(1-R), the site uses an LDPC code length of 1966, and the number of LDPC codewords is 1. Otherwise, the site uses an LDPC code length of 1296, that is, if N avbits <N pld +1464·(1-R), the site uses an LDPC code length of 1296, and the number of LDPC codewords is 1. Regarding N... avbits The selection of LDPC code length under other value ranges can be shown in Table 1, and will not be described in detail here.

[0133] As another example, the first code length parameter table includes LDPC code lengths no greater than 3888. For instance, this first code length parameter table may include one or more of the following LDPC code lengths: 648, 1296, 1944, or 3888. That is, the site supports these four code lengths by default, or in other words, the site must support these four code lengths. The specific method for a site to determine the LDPC code length based on the code length parameter table is described in Table 1, and will not be detailed here. For the first code length parameter table including 3888, they will not be listed individually here.

[0134] 3. Second code length parameter table

[0135] The second code length parameter table includes LDPC code lengths greater than 1944. Such LDPC code lengths greater than 1944 may include, but are not limited to, at least one of the following: 3888, 5832, or 7776. For example, the second code length parameter table also includes at least one of the following LDPC code lengths: 648, 1296, or 1944. The embodiments of this application do not limit the code lengths involved in the second code length parameter table.

[0136] Regarding the second code length parameter table, the embodiments of this application provide the following examples:

[0137] Example 1:

[0138] The second code length parameter table is shown in Table 2. In Table 2, R represents the code rate, which can be 1 / 2, 3 / 4, 2 / 3, or 5 / 6. Alternatively, the code rate value can be predefined by the standard protocol. It is understood that each row in Table 2 can be independent.

[0139] Table 2

[0140]

[0141]

[0142] In Table 2, to ensure that the calculation results in the judgment conditions are integers, both x1 and x2 must be divisible by 12. Simultaneously, to achieve a balance between code length and the number of punctured bits, the proportion of parity bits dropped by punctures to all parity bits must be approximately 0.25. Therefore, the values ​​of x1 and x2 can be: x1 = 2916 = 12 × 243, x2 = 5832 = 12 × 486. Furthermore, to facilitate further reducing the proportion of punctured bits, x1 and x2 can also take the following values: x1 = 2916 + 12t, x2 = 5832 + 12w, where t, w = 0, 1, 2, etc. If a slight increase in the proportion of punctured bits is required, the values ​​of t, w can be t, w = -1, -2, etc. It can be understood that the values ​​of t and w can be the same or different.

[0143] As shown in Table 2, when 3888 <N avbits When N ≤ 5832, if avbits ≥N pld +x2×(1-R), the site selects an LDPC code with a code length of 3888, at which point the number of LDPC codewords is 2. If N avbits <N pld +x2×(1-R), the site selects an LDPC code with a code length of 1944, at which point the number of LDPC codewords is 3. This is understandable regarding N. avbits The selection of LDPC code length under other value ranges can be shown in Table 2, which will not be described in detail here.

[0144] Example 2:

[0145] The second code length parameter table can be shown in Table 3.

[0146] Table 3

[0147]

[0148] In Table 3, R represents the bitrate, which can be 1 / 2, 3 / 4, 2 / 3, or 5 / 6. Alternatively, the bitrate value can be predefined by the standard protocol. It is understood that each row in Table 3 can be independent.

[0149] In Table 3, to ensure the calculation result in the judgment condition is an integer, x1 needs to be divisible by 12. Simultaneously, to achieve a balance between code length and the number of punctured bits, the proportion of punctured parity bits to all parity bits must be approximately 0.25. Therefore, the value of x1 can be: x1 = 2916 = 12 × 243. Furthermore, to further reduce the proportion of punctured bits, x1 can also be taken as follows: x1 = 2916 + 12t, where t = 0, 1, 2, etc. If a slight increase in the proportion of punctured bits is required, the value of t can be t = -1, -2, etc.

[0150] As shown in Table 3, when 1944 <N avbits At this time, the site selects an LDPC code with a code length of 3888, and the number of LDPC codewords is [number missing]. Understandable, regarding N avbits The selection of LDPC code length under other value ranges can be shown in Table 3, which will not be described in detail here.

[0151] Example 3:

[0152] The second code length parameter table can be shown in Table 4.

[0153] Table 4

[0154]

[0155] In Table 4, R represents the bitrate, which can be 1 / 2, 3 / 4, 2 / 3, or 5 / 6. Alternatively, the bitrate value can be predefined by the standard protocol. It is understood that each row in Table 4 can be independent.

[0156] Example 4:

[0157] The second code length parameter table is shown in Table 5, where R represents the code rate, which can be 1 / 2, 3 / 4, 2 / 3, 5 / 6, 7 / 8, or 8 / 9. It is understood that each row in Table 5 can be independent.

[0158] Table 5

[0159]

[0160] In Table 5, to ensure that the calculation results in the judgment conditions are integers, x1, x2, x3, and x4 must all be divisible by the least common multiple of the denominators of all code rates. Simultaneously, to achieve a balance between code length and the number of punctured bits, the values ​​of x3 and x4 should be as close as possible to the standard values ​​for WLAN, i.e., x3 ≈ 912, x4 ≈ 1464. For x1 and x2, as described in Example 1, the proportion of punctured parity bits to all parity bits must be approximately 0.25.

[0161] As an example, the bitrate R can range from 7 / 8. If R ranges from 1 / 2, 3 / 4, 2 / 3, 5 / 6, or at least 7 / 8, then x1, x2, x3, and x4 must all be divisible by the least common multiple of the denominators of all bitrates within the range of R. This least common multiple is 24. Therefore, in this case, x3 = 912 = 38 × 24, and x4 = 1464 = 61 × 24. And x1 = 2928 = 122 × 24, and x2 = 5832 = 243 × 24. Furthermore, to further reduce the proportion of punctured bits, x1, x2, x3, and x4 can also take the following values: x1 = 2928 + 24t1, x2 = 5832 + 24t2, where t1, t2 = 0, 1, 2, etc. If the proportion of punched bits needs to be slightly increased, the values ​​of t1 and t2 can be t1, t2 = -1, -2, etc. It's understandable that the values ​​of t1 and t2 can be the same or different.

[0162] As another example, the bitrate R can range from 8 / 9. If R ranges from 1 / 2, 3 / 4, 2 / 3, 5 / 6, or at least 8 / 9, then x1, x2, x3, and x4 must all be divisible by the least common multiple of the denominators of all bitrates within the range of R. This least common multiple is 36. Therefore, in this case, x3 = 936 = 26 × 36, and x4 = 1476 = 41 × 36. Meanwhile, x1 = 2916 = 81 × 36, and x2 = 5832 = 162 × 36. Furthermore, to further reduce the proportion of punctured bits, x1, x2, x3, and x4 can also take the following values: x1 = 2916 + 36t1, x2 = 5832 + 36t2, x3 = 936 + 36t3, and x4 = 1476 + 36t4, where t1, t2, t3, and t4 = 0, 1, 2, etc. If the proportion of punched bits needs to be increased, then the values ​​of t1, t2, t3, t4 can be t1, t2, t3, t4 = -1, -2, etc. It can be understood that the values ​​of t1, t2, t3, t4 can be the same or different.

[0163] As another example, the bitrate R can range from 7 / 8 to 8 / 9. If R ranges from 1 / 2, 3 / 4, 2 / 3, 5 / 6, 7 / 8, to 8 / 9, then x1, x2, x3, and x4 must all be divisible by the least common multiple of the denominators of all bitrates within the range of R. This least common multiple is 72. Therefore, in this case, x3 = 936 = 13 × 72, x4 = 1512 = 21 × 72. And x1 = 2952 = 41 × 72, x2 = 5832 = 81 × 72. Meanwhile, to further reduce the proportion of punctured bits, x1, x2, x3, and x4 can also take the following values: x1 = 2952 + 72t1, x2 = 5832 + 72t2, x3 = 936 + 72t3, x4 = 1512 + 72t4, where t1, t2, t3, and t4 are positive integers, such as t1, t2, t3, and t4 = 0, 1, 2, etc. If it is necessary to increase the proportion of punctured bits, t1, t2, t3, and t4 can be negative integers, such as t1, t2, t3, and t4 = -1, -2, etc. It can be understood that the values ​​of t1, t2, t3, and t4 can be the same or different.

[0164] Example 5:

[0165] The second code length parameter table is shown in Table 6, where R represents the code rate, which can be 1 / 2, 3 / 4, 2 / 3, 5 / 6, 7 / 8, or 8 / 9. It is understood that each row in Table 6 can be independent.

[0166] Table 6

[0167]

[0168] In Table 6, to ensure that the calculation results in the judgment conditions are integers, x1, x3, and x4 must all be divisible by the least common multiple of the denominators of all code rates. Simultaneously, to achieve a balance between code length and the number of punctured bits, the values ​​of x3 and x4 should be as close as possible to the standard values ​​for WLAN, i.e., x3≈912, x4≈1464. For x1, as described in Example 1 or Example 2, the proportion of punctured parity bits to all parity bits must be approximately 0.25.

[0169] As an example, the bitrate R can range from 7 / 8. If R ranges from 1 / 2, 3 / 4, 2 / 3, 5 / 6, or at least 7 / 8, then x1, x3, and x4 must all be divisible by the least common multiple of the denominators of all bitrates within the range of R. This least common multiple is 24. Therefore, in this case, x3 = 912 = 38 × 24, x4 = 1464 = 61 × 24, and x1 = 2928 = 122 × 24. Furthermore, to further reduce the proportion of punctured bits, x1, x3, and x4 can also take the following values: x1 = 2928 + 24t1, where t1 is a natural number, such as t1 = 0, 1, 2, etc. If it is necessary to increase the proportion of punctured bits, t1 can be a negative integer, such as t1 = -1, -2, etc.

[0170] As another example, the bitrate R can range from 8 / 9. If R ranges from 1 / 2, 3 / 4, 2 / 3, 5 / 6, or at least 8 / 9, then x1, x3, and x4 must all be divisible by the least common multiple of the denominators of all bitrates within the range of R. This least common multiple is 36. Therefore, in this case, x3 = 936 = 26 × 36, x4 = 1476 = 41 × 36, and x1 = 2916 = 81 × 36. Furthermore, to further reduce the proportion of punched bits, x1, x3, and x4 can also take the following values: x1 = 2916 + 36t1, x3 = 936 + 36t3, x4 = 1476 + 36t4, where t1, t3, and t4 are natural numbers, such as t1, t3, and t4 = 0, 1, 2, etc. If the proportion of punched bits needs to be increased, t1, t3, and t4 can be negative integers, such as t1, t3, and t4 = -1, -2, etc. It can be understood that the values ​​of t1, t3, and t4 can be the same or different.

[0171] As another example, the bitrate R can range from 7 / 8 to 8 / 9. If R ranges from 1 / 2, 3 / 4, 2 / 3, 5 / 6, or 8 / 9, then x1, x3, and x4 must all be divisible by the least common multiple of the denominators of all bitrates within the range of R. This least common multiple is 72. Therefore, in this case, x3 = 936 = 13 × 72, x4 = 1512 = 21 × 72, and x1 = 2952 = 41 × 72. Furthermore, to further reduce the proportion of punctured bits, x1, x3, and x4 can also take the following values: x1 = 2952 + 72t1, x3 = 936 + 72t3, x4 = 1512 + 72t4, where t1, t3, and t4 are natural numbers, such as t1, t3, t4 = 0, 1, 2, etc. If the proportion of punched bits needs to be increased, t1, t3, and t4 can be negative integers, such as t1, t3, and t4 = -1, -2, etc. It can be understood that the values ​​of t1, t3, and t4 can be the same or different.

[0172] Example 6:

[0173] The second code length parameter table is shown in Table 7, where R represents the code rate, which can be 1 / 2, 3 / 4, 2 / 3, 5 / 6, 7 / 8, or 8 / 9. It is understood that each row in Table 7 can be independent.

[0174] Table 7

[0175]

[0176] In Table 7, the values ​​of x1, x3, and x4 can be found in the relevant descriptions in Example 5, and will not be repeated here.

[0177] Example 7:

[0178] The second code length parameter table includes an LDPC code length of 1944 × 2 = 3888 bits and an LDPC code length of 3888 × 2 = 7776 bits. The second code length parameter table can be shown in Table 8. It is understood that each row in Table 8 can be independent.

[0179] Table 8

[0180]

[0181] In Table 8, to ensure that the calculation results in the judgment conditions are integers, both x1 and x2 must be divisible by 12. Simultaneously, to achieve a balance between code length and the number of punctured bits, the proportion of parity bits dropped by punctures to all parity bits must be approximately 0.25. Therefore, the values ​​of x1, x2, and x5 can be: x1 = 2916 = 12 × 243, x2 = 5832 = 12 × 486, x5 = 12 × 972. Furthermore, to further reduce the proportion of punctured bits, x1 and x2 can also take the following values: x1 = 2916 + 12t1, x2 = 5832 + 12t2, x5 = 11664 + 12t3, where t1, t2, and t3 are natural numbers, such as t1, t2, t3 = 0, 1, 2, etc. If the proportion of punched bits needs to be increased, t1, t2, and t3 can be negative integers, such as t1, t2, and t3 = -1, -2, etc. It can be understood that the values ​​of t1, t2, and t3 can be the same or different.

[0182] As shown in Table 8, when 7776 <N avbits When N ≤ 11664, if avbits ≥N pld +x5×(1-R), the site selects an LDPC code with a code length of 7776, at which point the number of LDPC codewords is 2. If N avbits <N pld +x5×(1-R), the site selects an LDPC code with a length of 3888, at which point the number of LDPC codewords is 3.

[0183] The first and second code length parameter tables shown above are merely examples, and the specific relationships within these parameter tables are not limited in the embodiments of this application. In this application, the code length parameter tables may also have other names (such as a code length selection table). For example, the first code length parameter table may also be called the first code length selection table, and the second code length parameter table may also be called the second code length selection table.

[0184] When selecting the code length for WLAN LDPC codes, both the performance of longer codes and the number of punctured bits need to be considered. Generally, longer LDPC codes offer better error control performance; therefore, longer codes should be chosen whenever possible. However, for different code lengths, WLAN LDPC encoding requires puncturing, meaning that a few parity bits at the end are not transmitted. Punching increases the actual code rate, resulting in some performance loss. Therefore, the specific code length selection for WLAN LDPC encoding needs to strike a balance between favoring longer codes and the actual number of punctured bits. As can be seen from the code length parameter tables shown above, the code length selection for WLAN LDPC codes does not monotonically increase with the information bit length, but rather may gradually regress to shorter code lengths. At the shortest length, WLAN LDPC codes directly choose an intermediate code length (e.g., 1296 bits) instead of the shortest code length (e.g., 648 bits), because the information bits must at least fill a single OFDM symbol. The encoding process also involves repetitive operations, which will not be elaborated here.

[0185] As protocols evolve, LDPC codes can be extended beyond 1944 bits, such as 2×LDPC, 3×LDPC, or 4×LDPC. Longer code lengths allow more bits to participate in encoding, can randomize noise, and the parity check matrix of longer codes has more check equations. More check equations provide more check relationships, offering stronger error correction capabilities. Therefore, embodiments of this application provide a communication method and apparatus. Optionally, the sending and receiving parties can interact regarding whether to support longer LDPC code lengths. Optionally, the first station can select a longer LDPC code length and notify the second station whether to adopt a longer LDPC code length. Optionally, the first and second stations can determine a suitable LDPC code length based on a code length parameter table.

[0186] In this application embodiment, a longer LDPC code length may include one or more of the following: 2×LDPC, 3×LDPC or 4×LDPC.

[0187] Please see Figure 2A , Figure 2AThis is a flowchart illustrating a communication method provided in an embodiment of this application. In this method, the sender and receiver can exchange their respective supported LDPC code lengths. This communication method can be applied to a first site and a second site. The first site can be an AP or a non-AP STA as described above, and the second site can be an AP or a non-AP STA as described above. Further details regarding the first and second sites can be found in [reference needed]. Figure 1 And so on, which will not be elaborated here. Figure 2A As shown, the method includes, but is limited to, the following steps.

[0188] 201. The first station sends the first capability information, and the second station receives the first capability information accordingly.

[0189] The first capability information indicates whether the first site supports a second LDPC code length greater than 1944. That is, the first capability information indicates whether the first site supports LDPC code lengths greater than 1944. Alternatively, the first capability information indicates whether the first site supports longer LDPC code lengths. The first capability information can be referred to as longer code length capability information. Optionally, both the second and first capability information shown below can be referred to as longer code length capability information.

[0190] The second LDPC code length includes one or more of the following: 2×LDPC, 3×LDPC, or 4×LDPC. Alternatively, the second LDPC code length can also be longer than 4×LDPC. These will not be listed individually here.

[0191] Regarding this first capability information, the embodiments of this application provide the following examples:

[0192] Example 1:

[0193] The second LDPC code length is one or more of 2×LDPC, 3×LDPC, or 4×LDPC, and the first capability information indicates whether the first site supports one or more of 2×LDPC, 3×LDPC, or 4×LDPC.

[0194] As an example, the second LDPC code length is one of 2×LDPC, 3×LDPC, or 4×LDPC, and the first capability information indicates whether the first site supports one of 2×LDPC, 3×LDPC, or 4×LDPC. For example, the first capability information uses one bit to indicate whether the first site supports 2×LDPC. A bit of 1 indicates that the first site supports 2×LDPC, and a bit of 0 indicates that the first site does not support 2×LDPC. Alternatively, a bit of 0 indicates that the first site supports 2×LDPC, and a bit of 1 indicates that the first site does not support 2×LDPC. As another example, the first capability information uses one bit to indicate whether the first site supports 3×LDPC. A bit of 1 indicates that the first site supports 3×LDPC, and a bit of 0 indicates that the first site does not support 3×LDPC. Alternatively, a bit of 0 indicates that the first site supports 3×LDPC, and a bit of 1 indicates that the first site does not support 3×LDPC. As yet another example, the first capability information uses one bit to indicate whether the first site supports 4×LDPC. A bit value of 1 indicates that the first site supports 4×LDPC, and a bit value of 0 indicates that the first site does not support 4×LDPC. Alternatively, a bit value of 0 indicates that the first site supports 4×LDPC, and a bit value of 1 indicates that the first site does not support 4×LDPC.

[0195] For the above example, optionally, when the first station supports 3×LDPC code length, the first station supports 2×LDPC code length, or the first station does not support 2×LDPC code length. Similarly, when the first station supports 4×LDPC code length, the first station supports 2×LDPC code length or 3×LDPC code length, or the first station does not support both 2×LDPC code length and 3×LDPC code length.

[0196] As another example, the first capability information indicates that the first site supports multiple LDPC code lengths greater than 1944 (such as 4×LDPC, 3×LDPC, and 2×LDPC). For example, the first capability information occupies 1 bit, and the relationship between the value of this 1 bit and its meaning is as follows: 0 indicates that the first site does not support LDPC code lengths longer than 1944, that is, the first site does not support 4×LDPC, 3×LDPC, and 2×LDPC; 1 indicates that the first site supports 4×LDPC, 3×LDPC, and 2×LDPC. It is understood that the relationship between the value of the above 1 bit and its meaning is only an example and should not be construed as a limitation of this application.

[0197] Example 2: The first capability information indicates different LDPC code lengths greater than 1944 separately. For example, the first capability information indicates whether the first site supports 2×LDPC, 3×LDPC, and 4×LDPC respectively. For instance, the first capability information uses 3 bits to indicate whether the first site supports 2×LDPC, 3×LDPC, and 4×LDPC respectively. The first bit of these 3 bits indicates whether the first site supports 2×LDPC, the second bit indicates whether it supports 3×LDPC, and the third bit indicates whether it supports 4×LDPC.

[0198] Example 3: The first capability information indicates that the first site supports LDPC code lengths shorter than the second LDPC code length by instructing the first site to support the second LDPC code length. For example, if the first capability information indicates that the first site does not support the second LDPC code length, it means that the first site does not support LDPC code lengths longer than 1944, i.e., the first site does not support 4×LDPC, 3×LDPC, and 2×LDPC. As another example, if the second LDPC code length is 2×LDPC, the first capability information indicates that the first site supports 2×LDPC code lengths and LDPC code lengths shorter than 2×LDPC, but does not support 4×LDPC and 3×LDPC. Similarly, if the second LDPC code length is 3×LDPC, the first capability information indicates that the first site supports 3×LDPC and 2×LDPC, but does not support 4×LDPC. And again, if the second LDPC code length is 4×LDPC, the first capability information indicates that the first site supports 4×LDPC, 3×LDPC, and 2×LDPC.

[0199] In other words, in this example, if the first station supports a longer LDPC code length, then the first station also supports a relatively shorter LDPC code length. For example, the first capability information occupies 2 bits, and the relationship between the values ​​of these 2 bits and their meanings is as follows: 0 indicates that LDPC code lengths greater than 1944 are not supported; 1 indicates that the first station supports 2×LDPC, but not 3×LDPC or 4×LDPC; 2 indicates that the first station supports 2×LDPC and 3×LDPC, but not 4×LDPC; 3 indicates that the first station supports 2×LDPC, 3×LDPC, and 4×LDPC. It should be understood that the relationship between the values ​​of the above 2 bits and their meanings is merely an example and should not be construed as a limitation of this application.

[0200] For example, the aforementioned first capability information can be included in a UHR capability information element. This UHR capability information element can be as follows: Figure 3As shown, the capability information element includes at least one of the following fields: element ID (occupying 1 byte), length (occupying 1 byte), element ID extension (occupying 1 byte), UHR MAC capabilities information, and UHR PHY capabilities information. The number of bytes occupied by the UHR MAC capabilities information field and the UHR PHY capabilities information field is not fixed (or is pending or variable). Optionally, the aforementioned first capability information can be carried in the UHR PHY capabilities information field.

[0201] Figure 3 Examples 1 to 3 of the aforementioned first capability information are also exemplarily shown. For example... Figure 3 As shown, for Example 1, the first capability information is carried in a 1-bit field supporting longer code lengths; the explanation of this field can be found in Example 1 above. For Example 2, the first capability information can be carried in a 1-bit field supporting 2×LDPC code lengths, a 1-bit field supporting 2×LDPC code lengths, and a 1-bit field supporting 4×LDPC code lengths. The explanation of these three fields can be found in Example 2 above. For Example 3, the first capability information is carried in a 2-bit field supporting longer code lengths; the explanation of this field can be found in Example 3 above. Further details will not be provided here.

[0202] Optionally, the first capability information can be carried in the UHR capability information element of the management frame. For example, if the first site is an AP, the management frame can be one or more of a beacon frame, probe response frame, association response frame, reassociation response frame, etc. As another example, if the first site is a STA, the management frame can be one or more of a probe request frame, association request frame, reassociation request frame, etc.

[0203] In this embodiment, the content indicated by the first capability information applies to the transmitting capability and / or receiving capability of the first site. For example, the content indicated by the first capability information may simultaneously support both the transmitting and receiving capabilities of the first site. Or, the first capability information may include first capability information 1 and / or first capability information 2, where first capability information 1 indicates whether the transmitting capability of the first site supports a second LDPC code length, and first capability information 2 indicates whether the receiving capability of the first site supports a second LDPC code length. The second LDPC code length supported by the transmitting capability and the second LDPC code length supported by the receiving capability may be the same or different. For the separate indications of transmitting and receiving capabilities, refer to Examples 1 to 4 above, which will not be detailed here.

[0204] 202, the second station sends the second capability information, and correspondingly, the first station receives the second capability information.

[0205] The second capability information is used to indicate whether the second site supports the second LDPC code length. For an explanation of the second LDPC code length, please refer to the description in step 201; it will not be elaborated here. The specific implementation of the second capability information indicating whether the second site supports the second LDPC code length can be found in the above description of the specific implementation of the first capability information indicating whether the first site supports the second LDPC code length; it will not be repeated here.

[0206] For example, the second capability information can be included in the UHR capability information element. This second capability information can be carried in the UHR capability information element of a management frame. For instance, if the second site is an AP, the management frame can be one or more of a beacon frame, probe response frame, association response frame, reassociation response frame, etc. Or, if the second site is a STA, the management frame can be one or more of a probe request frame, association request frame, reassociation request frame, etc.

[0207] In this embodiment, the content indicated by the second capability information applies to the transmitting capability and / or receiving capability of the second station. For example, the content indicated by the second capability information may simultaneously support both the transmitting and receiving capabilities of the second station. Or, the second capability information may include second capability information 1 and / or second capability information 2, where second capability information 1 indicates whether the transmitting capability of the second station supports a second LDPC code length, and second capability information 2 indicates whether the receiving capability of the second station supports a second LDPC code length. The second LDPC code length supported by the transmitting capability and the second LDPC code length supported by the receiving capability may be the same or different.

[0208] It is understood that this application does not restrict the order of steps 201 and 202 described above.

[0209] In this embodiment of the application, the stations can interact to determine whether the other end supports the second LDPC code length, so that both the sender and receiver can clearly know whether the other end supports the second LDPC code length, thereby ensuring that both the sender and receiver can use a unified LDPC code length as much as possible.

[0210] Figure 2B This is a flowchart illustrating another communication method provided in an embodiment of this application. In this method, the sending and receiving parties can determine the LDPC code length to be used based on the transmission method, ensuring that both parties use a unified LDPC code length.

[0211] Figure 2B The method shown is the same as Figure 2A The method shown can be a standalone embodiment, or Figure 2B Can be with Figure 2A Combination, such as Figure 2C . Figure 2C As shown, the first and second stations interact with each other using their respective supported second LDPC code lengths (reference). Figure 2A In the case of transmitting PPDU, the first station and the second station determine the first LDPC code length according to the transmission mode; or the first station determines the first LDPC code length according to the transmission mode and the second LDPC code length supported by the second station; or the second station determines the first LDPC code length according to the transmission mode and the second LDPC code length supported by the first station; or the second station determines the first LDPC code length according to the transmission mode and operation information. Figure 2C For specific methods, please refer to Figure 2B Related examples in the document.

[0212] like Figure 2B As shown, the method includes, but is not limited to, the following steps.

[0213] 211. The first station determines the first LDPC code length based on the transmission method.

[0214] The first LDPC code length is the LDPC code length used by the PPDU transmitted by the first site. The transmission method includes unicast transmission or multicast transmission. Multicast transmission includes at least one of multicast transmission or broadcast transmission.

[0215] For example, when the transmission method is unicast transmission, the first station can determine the first LDPC code length based on the second capability information. For instance, the first station can determine the first LDPC code length based on the LDPC code lengths it supports and the second capability information. Alternatively, the first station can determine the first LDPC code length based on both the first capability information and the second capability information. Specific explanations of the first and second capability information can be found in the relevant descriptions above.

[0216] In one possible implementation, if the transmission method is unicast and both the first and second stations support the second LDPC code length, the first station determines the first LDPC code length according to a second code length parameter table, which includes the second LDPC code length. Alternatively, if the transmission method is unicast and both the first and second stations support the second LDPC code length, the first LDPC code length is the second LDPC code length. When determining the first LDPC code length according to the second code length parameter table, the first LDPC code length and the second LDPC code length may be the same or different. That is, even if the first station uses a code length parameter table that includes a longer LDPC code length, the first station may not necessarily use a longer LDPC code length; the first LDPC code length determined by the first station depends on the total number of codeword bits and the length of the data bits in this data transmission.

[0217] Unicast transmission is a one-to-one transmission, meaning there is a single receiving end (i.e., the second station). For unicast transmission, after the first and second stations associate or pair, they can determine each other's capabilities, specifically whether the other station supports a second LDPC code length. If both the first and second stations support the second LDPC code length, the first station can determine the first LDPC code length based on the second code length parameter table, enabling both stations to use a longer LDPC code length. It is understood that the second code length parameter table can be any of the items in Tables 2 to 8, and will not be elaborated upon here.

[0218] In another possible implementation, the transmission method is unicast transmission, and if the first station or the second station does not support the second LDPC code length, the first station determines the first LDPC code length according to the first code length parameter table.

[0219] When either the first site or the second site does not support the second LDPC code length, the first site determines the first LDPC code length according to the first code length parameter table, thereby avoiding the use of an LDPC code length that is not supported by the first site or the second site.

[0220] For example, the first site supports longer LDPC code lengths of A, B, and C; the second site supports longer LDPC code lengths of A, C, and D, where the lengths of A, B, C, and D are all greater than 1944.

[0221] When the second LDPC code length is A, both the first and second stations support the second LDPC code length. The first and second stations determine the first LDPC code length according to a code length parameter table that includes A.

[0222] When the second LDPC code length is C, both the first and second stations support the second LDPC code length. The first and second stations determine the first LDPC code length according to a code length parameter table that includes C.

[0223] When the second LDPC code length is A and C, the first and second stations support the second LDPC code length. The first and second stations determine the first LDPC code length according to a code length parameter table including A and / or C.

[0224] When the second LDPC code length is B, the first station supports the second LDPC code length; the second station does not support the second LDPC code length. The first station and the second station determine the first LDPC code length according to the first code length parameter table, or in other words, according to the code length parameter table excluding B.

[0225] When the second LDPC code length is D, the first station does not support the second LDPC code length; the second station supports the second LDPC code length. The first station and the second station determine the first LDPC code length according to the first code length parameter table, or in other words, according to the code length parameter table excluding D.

[0226] For example, the first station supports longer LDPC code lengths of A, B, and C; the second station supports longer LDPC code lengths of A, C, and D. The first and second stations can choose code length A or C for communication, and the second code length selection table contains code lengths A and / or C.

[0227] For example, the first station supports longer LDPC code lengths of A and C; the second station supports a longer LDPC code length of D. The first and second stations can only select the first code length parameter table to determine the first LDPC code length. This first LDPC code length is the code length used by the first station when encoding the PPDU, which is also the code length used by the second station when decoding the PPDU.

[0228] Taking the example where the first site supports LDPC code lengths of 2×LDPC and the second site supports LDPC code lengths of 2×LDPC:

[0229] When the second LDPC code length is 2×LDPC, both the first and second sites support 2×LDPC. The first LDPC code length can be 2×LDPC, or the first LDPC code length is determined according to a code length parameter table that includes 2×LDPC.

[0230] If the second LDPC code length is 3×LDPC, then neither the first nor the second site supports 3×LDPC. The first LDPC code length may include 2×LDPC, or a code length shorter than 2×LDPC. That is, the first LDPC code length may be determined according to a first code length parameter table, or according to a code length parameter table that includes 2×LDPC.

[0231] Taking the second site as an example, where the LDPC code length supported is 4×LDPC and the first site supports 3×LDPC code length:

[0232] As an example, as shown in the above implementation, the first LDPC code length is determined according to the first code length parameter table.

[0233] As another example, when the first site supports 3×LDPC, it supports a code length shorter than 3×LDPC, and when the second site supports 4×LDPC, it supports a code length shorter than 4×LDPC. The first LDPC code length includes at least one of 3×LDPC, 2×LDPC, and a code length shorter than 2×LDPC.

[0234] As another example, taking the case where the first site supports 3×LDPC but does not support 2×LDPC, and the case where the second site supports 4×LDPC but does not support 3×LDPC and 2×LDPC, the first LDPC code length can be determined according to the first code length parameter table.

[0235] In multicast transmission (broadcast and / or multicast transmission), there are multiple receivers (such as multiple second sites). Even if only one receiver does not support a longer LDPC code length, the transmitter cannot use a longer LDPC code length. However, these multiple receivers are unaware of each other's capabilities; that is, they are unaware of the LDPC code lengths they support (e.g., whether they support longer LDPC code lengths is unknown). Therefore, in multicast transmission, the implementation method for the first site to determine the first LDPC code length can include:

[0236] Implementation method 1:

[0237] As an example, in the case of multicast transmission, the first station determines the first LDPC code length according to the first code length parameter table. The first code length parameter table does not include LDPC code lengths greater than 1944, or in other words, it includes LDPC code lengths not greater than 1944.

[0238] Both the transmitting and receiving ends are prohibited from using longer LDPC code lengths, or the first LDPC code length must be determined by default using a code length parameter table that does not include longer LDPC code lengths. If the first and second sites must support 648, 1296, or 1944, longer LDPC code lengths include, but are not limited to, 2×LDPC, 3×LDPC, or 4×LDPC.

[0239] For example, the first code length parameter table includes LDPC code lengths less than or equal to 1944. The first site and the second site support LDPC code lengths less than or equal to 1944 by default, or both the first site and the second site support the code lengths in the first code length parameter table.

[0240] As another example, in the case of multicast transmission, when the LDPC code length supported by the first site and the second site includes 2×LDPC, the first site determines the first LDPC code length according to the first code length parameter table including 2×LDPC.

[0241] For example, the first code length parameter table includes one or more of 2×LDPC, 1944, 1296, or 648. The first and second sites support 648, 1296, 1944, and 2×LDPC by default. Longer LDPC code lengths are code lengths longer than 2×LDPC, such as 3×LDPC or 4×LDPC.

[0242] In this implementation, the first station can determine the first LDPC code length based on the default LDPC code lengths supported by the first and second stations and the code length parameter table.

[0243] By implementing Method 1, during multicast transmission, longer LDPC code lengths are prohibited, or the use of a code length parameter table that includes longer LDPC code lengths to determine the first LDPC code length is prohibited. This not only ensures that both the sender and receiver use the same LDPC code length, but also makes the implementation simple and has low complexity.

[0244] Optionally, when the sending and receiving capabilities of a station may be inconsistent, the first station may determine the first LDPC code length based on the second capability information and the LDPC code length supported by the first station, and the second station may determine the first LDPC code length based on the first capability information and the LDPC code length supported by the second station.

[0245] Implementation Method Two:

[0246] When the transmission method is multicast transmission (such as broadcast transmission and / or multicast transmission), the first station determines the first LDPC code length based on whether each of the multiple second stations supports the second LDPC code length. That is, the first station can determine the first LDPC code length based on the second capability information of the multiple second stations. The method by which the first station obtains whether the second stations support the second LDPC code length can be found above. Figure 2A This will not be elaborated upon here.

[0247] In other words, the first station determines the first LDPC code length based on whether multiple second stations support the second LDPC code length. If all second stations support the second LDPC code length, then the first LDPC code length is the same as the second LDPC code length, or the first LDPC code length is determined according to the second code length parameter table. Alternatively, if at least one of the multiple second stations does not support the second LDPC code length, then the first station can determine the first LDPC code length according to the first code length parameter table.

[0248] As an example, the first site can determine the first LDPC code length based on its own capabilities (i.e., the LDPC code lengths it supports) and the capability information of multiple second sites. As another example, the first site can determine the first LDPC code length based on first capability information and the capability information of multiple second sites.

[0249] As an example, the aforementioned multiple second sites are all the second sites associated with the first site. If all the second sites associated with the first site support the second LDPC code length, the first site determines the LDPC code length to use based on the second code length parameter table when performing broadcast and / or multicast transmissions. If any of the second sites associated with the first site does not support the second LDPC code length, the first site determines the LDPC code length to use according to the first code length parameter table when performing broadcast transmissions.

[0250] As another example, the aforementioned multiple second sites are associated second sites of a multicast group corresponding to the first site.

[0251] As another example, the aforementioned multiple second sites are associated second sites of multiple multicast groups corresponding to the first site. In this example, the first LDPC code lengths corresponding to the multiple multicast groups may be the same or different.

[0252] If all second sites in a multicast group support the second LDPC code length, the first site determines the LDPC code length to use based on the second code length parameter table when performing multicast transmission for the second sites in that multicast group. If there is a second site in a multicast group that does not support the second LDPC code length, the first site determines the LDPC code length to use based on the first code length parameter table when performing multicast transmission for the second sites in that multicast group.

[0253] The second implementation described above illustrates how the first station determines the first LDPC code length based on the second capability information of multiple second stations. In a more practical implementation, when the transmission mode is multicast, the first station can freely choose the first LDPC code length. That is, the first station can determine the first LDPC code length without combining the second capability information of each second station, and instead choose not to use a longer LDPC code length. This simplifies the implementation.

[0254] In one possible implementation, when the transmission method is multicast transmission, the first station can also send operation information, and the second station receives the operation information accordingly. This operation information is used to indicate whether the LDPC code length used by the first station is a second LDPC code length, or it is used to indicate whether the first station uses a second code length parameter table, which includes the second LDPC code length.

[0255] The second station can determine the first LDPC code length based on this operation information. That is, by sending this operation information, the first station enables the second station to clearly know the LDPC code length used by the first station, thereby ensuring that the first station and the second station maintain the consistency of the LDPC code length they use.

[0256] Optionally, the first station may send operation information based on at least one of the first capability information and the second capability information. For example, the first station may determine the LDPC code length to be used by the first station based on the first capability information and the second capability information, and use the operation information to indicate whether the LDPC code length used by the first station is a second LDPC code length or to indicate whether the first station uses a second code length parameter table.

[0257] Optionally, the first site can correspond to at least two multicasts. The operation information indicates whether the first multicast in the at least two multicasts uses a second LDPC codelength, or the operation information is used to indicate whether the second multicast in the at least two multicasts uses a second codelength parameter table. That is, when the first site corresponds to multiple multicasts, the operation information can indicate whether each of the multiple multicasts uses a second LDPC codelength or a second codelength parameter table. In this way, by combining the above information with different multicast indications, it is possible to enable the use of longer LDPC codelengths within multicasts as much as possible, making the determined LDPC codelengths within each multicast more appropriate.

[0258] Regarding the specific implementation of the operation information indication in the case of multicast transmission, the embodiments of this application provide the following examples:

[0259] Example 1: The operation information indicates whether the multicast transmission uses a second LDPC code length or a second code length parameter table, including both broadcast and multicast transmissions. For example, this operation information can indicate whether the multicast transmission uses a second LDPC code length or a second code length parameter table using only one bit. A value of 0 indicates that the multicast transmission uses the second LDPC code length or a second code length parameter table, while a value of 1 indicates that the multicast transmission does not use the second LDPC code length or a second code length parameter table. Alternatively, a value of 1 indicates that the multicast transmission uses the second LDPC code length or a second code length parameter table, while a value of 0 indicates that the multicast transmission does not use the second LDPC code length or a second code length parameter table.

[0260] In Example 1, the operation information does not specifically distinguish between multicast and broadcast transmissions.

[0261] Example 2: Operation information indicates whether broadcast transmission uses the second LDPC code length or whether the second code length parameter table is used, and indicates whether multicast transmission uses the second LDPC code length or whether the second code length parameter table is used.

[0262] Operation information can indicate whether broadcast and multicast transmissions use a second LDPC code length or not. For example, operation information includes two bits, one bit indicating whether broadcast transmissions use a second LDPC code length or a second code length parameter table, and the other bit indicating whether multicast transmissions use a second LDPC code length or a second code length parameter table.

[0263] In Example 2, the operation information indicates whether it is for multicast transmission or broadcast transmission.

[0264] Example 3: The operation information indicates whether the broadcast transmission uses the second LDPC code length or the second code length parameter table, and indicates whether the first multicast group uses the second LDPC code length or the second code length parameter table, and indicates whether the second multicast group uses the second LDPC code length or the second code length parameter table.

[0265] In this example, the first station may correspond to at least two multicast groups (including a first multicast group and a second multicast group), and the operation information may indicate whether the multicast transmissions corresponding to the at least two multicast groups use the second LDPC code length or the second code length parameter table. The first station indicates whether the corresponding multicast transmissions will use the second LDPC code length for different multicast groups. For example, if the first station corresponds to M multicast groups, the operation information may indicate whether multicast group 1 to multicast group M use the second LDPC code length.

[0266] In Example 3, the operation information indicates whether it is for a broadcast transmission, the first multicast group, or the second multicast group.

[0267] Optionally, the operational information may also include the identifier of the broadcast and / or the identifier of the multicast group. The identifier of the broadcast includes, but is not limited to, at least one of the following: the medium access control (MAC) address, STA ID, or association identifier (AID) of the broadcast. The identifier of the multicast group may include, but is not limited to, at least one of the following: the MAC address, STA ID, or AID of the multicast group.

[0268] For example, in Example 2 above, the operational information may include the identifier of the broadcast and / or the identifier of the multicast group. The identifier of the multicast group may not specifically distinguish between different multicast groups. That is, the identifier of the multicast group can be used to distinguish broadcast transmissions, without the need to maintain different multicast groups. For example, in Example 3 above, the operational information may include the identifier of the broadcast, the identifier of the first multicast group, the identifier of the second multicast group, etc.

[0269] To distinguish between different multicast groups, the AP can assign different STA IDs or AIDs to different multicast groups. For example, the first multicast group might be assigned STA ID = 20, and the second multicast group might be assigned STA ID = 21. Operation information can instruct the multicast group with STA ID = 20 to use a second LDPC code length, or instruct the multicast group with STA ID = 20 to use a second code length parameter table. Operation information can also instruct the multicast group with STA ID = 21 not to use a second LDPC code length, or instruct the multicast group with STA ID = 21 not to use a second code length parameter table. Therefore, after receiving the PPDU, the second station reads the corresponding STA ID or AID, determines the corresponding multicast group, and determines the first LDPC code length based on whether the corresponding multicast group uses a second LDPC code length (or whether it uses a second code length parameter table) as indicated by the operation information.

[0270] Optionally, the operational information is included in the operational information element of the management frame or in the signaling (SIG) field of the physical protocol data unit (PPDU). This signaling field includes general signaling fields. Alternatively, the signaling field includes a signaling field corresponding to the standard to which the PPDU belongs; for example, if the PPDU is an ultra-high reliability (UHR) PPDU, the signaling field is the UHR-SIG field. Optionally, the above operational information can be included in the PPDU shown in step 213 below. The management frame can include one or more of the following: beacon frame, probe response frame, association response frame, and reassociation response frame.

[0271] For example, the operation information element can be as follows: Figure 4 As shown, the operation information element may include at least one of the following: element ID (occupying 1 byte), length (occupying 1 byte), element ID extension (occupying 1 byte), and UHR operation parameters. The number of bytes occupied by the UHR operation parameters field is undetermined (or variable). The above operation information is contained in the UHR operation parameters field.

[0272] Figure 4Examples one through three above are also exemplarily illustrated. For example one, the UHR operation parameter fields include a multicast longer code length indication field, which indicates whether the multicast transmission uses a second LDPC code length or a second code length parameter table. A description of this field can be found in example one above. For example two, the UHR operation parameter fields include a broadcast longer code length adoption indication field and a multicast longer code length adoption indication field. The broadcast longer code length adoption indication field indicates whether the broadcast transmission uses a second LDPC code length or a second code length parameter table, and the multicast longer code length adoption indication field indicates whether the multicast transmission uses a second LDPC code length or a second code length parameter table. A description of these two fields can be found in example two above. For Example 3, the UHR operation parameter fields include a broadcast longer code length adoption indication field, a multicast group 1 longer code length adoption indication field, ..., a multicast group M longer code length adoption indication field. The broadcast longer code length adoption indication field indicates whether the broadcast transmission uses the second LDPC code length or whether it uses the second code length parameter table. The multicast group 1 longer code length adoption indication field indicates whether multicast group 1 uses the second LDPC code length or whether it uses the second code length parameter table, ..., the multicast group M longer code length adoption indication field indicates whether multicast group M uses the second LDPC code length or whether it uses the second code length parameter table. For example, the multicast group 1 longer code length adoption indication field includes a multicast identifier field and a longer code length adoption indication field. The multicast identifier field indicates the multicast identifier of multicast group 1 (such as the MAC address of multicast group 1), and the longer code length adoption indication field indicates whether multicast group 1 uses the second LDPC code length or whether it uses the second code length parameter table. The explanation of each of the above fields can be found in Example 3 above. They will not be detailed here.

[0273] 212. The second station determines the first LDPC code length based on the transmission method.

[0274] 213. The first station sends a PPDU, and the corresponding second station receives the PPDU, which uses the first LDPC code length.

[0275] The first station performs LDPC encoding on the PPDU based on the first LDPC code length. The second station decodes the PPDU based on the first LDPC code length. If the PPDU includes a data field, that data field uses the first LDPC code length.

[0276] In this embodiment, the second station may first determine the first LDPC code length based on the transmission method, and then receive the PPDU; alternatively, the second station may first receive the PPDU, and then determine the first LPDC code length based on the transmission method. This embodiment does not limit this aspect.

[0277] The aforementioned PPDU may include signaling fields. As an example, the transmission method of the PPDU is indicated by its signaling fields. For instance, the transmission method is indicated by the STA ID in the signaling field. For example, if the STA ID value is in the range of 1 to 2006, the transmission method is unicast. As another example, if the STA ID is a BSSID index of the basic service set identifier (BSSID), the transmission method is multicast. In this example, after receiving the PPDU, the second station can determine the transmission method based on the signaling fields of the PPDU.

[0278] As another example, the second station can know the PPDU transmission method in advance. For instance, the second station can determine the PPDU transmission method based on the default transmission method. Alternatively, the second station can determine the PPDU transmission method based on capability interaction or negotiation with the first station. Or, the second station can determine the transmission method of the current PPDU based on the transmission method of previously received PPDUs.

[0279] In one possible implementation, where the transmission method is unicast, the second station can determine the first LDPC code length based on the first capability information. For example, the second station can determine the first LDPC code length by combining its supported LDPC code lengths with the first capability information. Alternatively, the first station can determine the first LDPC code length based on both the first and second capability information.

[0280] As an example, if the transmission method is unicast transmission and both the first and second stations support the second LDPC code length, the second station determines the first LDPC code length according to the second code length parameter table, which includes the second LDPC code length.

[0281] As another example, if the transmission method is unicast transmission and the first or second station does not support the second LDPC code length, the first station determines the first LDPC code length according to the first code length parameter table.

[0282] For a detailed explanation of this implementation method, please refer to the relevant description in step 211 above, which will not be elaborated here.

[0283] In another possible implementation, where the transmission method is multicast, the second station determines the first LDPC code length based on the first code length parameter table. For a detailed explanation of this implementation, please refer to Implementation Method 1 above; it will not be elaborated upon here.

[0284] In another possible implementation, where the transmission method is multicast transmission, the second station determines the first LDPC code length based on the operation information.

[0285] As an example, the operation information indicates whether the multicast transmission uses a second LDPC code length or a second code length parameter table. For instance, if the operation information indicates that the multicast transmission does not use a second LDPC code length or a second code length parameter table, the second station determines the first LDPC code length according to the first code length parameter table. Alternatively, if the operation information indicates that the multicast transmission uses a second LDPC code length, the first LDPC code length and the second LDPC code length are the same. Or, if the operation information indicates that the second code length parameter table is used, the second station determines the first LDPC code length according to the second code length parameter table.

[0286] As another example, the operation information indicates whether broadcast transmission uses a second LDPC code length or a second code length parameter table, and also indicates whether multicast transmission uses a second LDPC code length or a second code length parameter table. The second station can determine whether the PPDU transmission mode is broadcast or multicast. If the PPDU transmission mode is broadcast, and the operation information indicates that broadcast transmission does not use a second LDPC code length or indicates that a second code length parameter table is not used, then the second station determines the first LDPC code length according to the first code length parameter table; if the operation information indicates that broadcast transmission uses a second LDPC code length, then the first LDPC code length is the same as the second LDPC code length; if the operation information indicates that broadcast transmission uses a second code length parameter table, then the second station determines the first LDPC code length according to the second code length parameter table. When the PPDU transmission mode is multicast transmission, if the operation information indicates that the multicast transmission does not use the second LDPC code length or indicates that the second code length parameter table is not used, the second station determines the first LDPC code length according to the first code length parameter table; if the operation information indicates that the multicast transmission uses the second LDPC code length, the first LDPC code length is the same as the second LDPC code length; if the operation information indicates that the multicast transmission uses the second code length parameter table, the second station determines the first LDPC code length according to the second code length parameter table.

[0287] As yet another example, the operation information indicates whether the broadcast transmission uses the second LDPC code length or the second code length parameter table, and indicates whether the first multicast group uses the second LDPC code length or the second code length parameter table, and indicates whether the second multicast group uses the second LDPC code length or the second code length parameter table.

[0288] When the PPDU transmission mode is broadcast transmission, if the operation information indicates that the broadcast transmission does not use the second LDPC code length or indicates that the second code length parameter table is not used, the second station determines the first LDPC code length according to the first code length parameter table; if the operation information indicates that the broadcast transmission uses the second LDPC code length, the first LDPC code length is the same as the second LDPC code length; if the operation information indicates that the broadcast transmission uses the second code length parameter table, the second station determines the first LDPC code length according to the second code length parameter table.

[0289] When the PPDU transmission mode is multicast transmission and the second station belongs to the first multicast group, if the operation information indicates that the first multicast group does not use the second LDPC code length or does not use the second code length parameter table, the second station determines the first LDPC code length according to the first code length parameter table; if the operation information indicates that the first multicast group uses the second LDPC code length, then the first LDPC code length is the same as the second LDPC code length; if the operation information indicates that the first multicast group uses the second code length parameter table, then the second station determines the first LDPC code length according to the second code length parameter table.

[0290] Optionally, the operation information may be included in the aforementioned PPDU, or it may be included in the signaling field of the management frame or PPDU1. PPDU1 may be a PPDU received by the second station before receiving the aforementioned PPDU (i.e., the PPDU in step 213). Further explanation regarding the operation information is given in step 211 and will not be elaborated here.

[0291] In this embodiment of the application, the first station determines the first LDPC code length according to different transmission methods, so that the first station can flexibly determine the LDPC code length corresponding to the transmission method, making the first LDPC code length more compatible with the transmission method.

[0292] Please see Figure 5 , Figure 5 A flowchart illustrating another communication method provided in this application embodiment. For example... Figure 5 As shown, the method includes, but is not limited to, the following steps.

[0293] 501, the first station sends the operation information, and the corresponding second station receives the operation information.

[0294] The operation information is used to indicate whether the LDPC code length used by the first site is the second LDPC code length, or the operation information is used to indicate whether the first site uses the second code length parameter table, which includes the second LDPC code length.

[0295] For example, if the second LDPC code length is greater than 1944, the operation information is used to indicate whether the LDPC code length used by the PPDU transmitted by the first site is the second LDPC code length, or the operation information is used to indicate whether the PPDU transmitted by the first site uses the second code length parameter table. It is understood that a detailed explanation of the second code length parameter table can be found in any of Tables 2 to 8 above, and will not be repeated here.

[0296] For example, the operation information may be included in the signaling field of a management frame or PPDU. For instance, the operation information may be included in the signaling field of a UHR PPDU.

[0297] As an example, the signaling field can be as follows: Figure 6A As shown, the signaling field may include at least one of the following: STA ID (11 bits, B0-B10), MCS field (4 bits, B11-B14), reserve field (1 bit, B15), NSS field (3 bits, B16-B18), EQM / UEQM flag field (1 bit, B19, value 0), beamforming (1 bit, B20), and coding (1 bit, B21). The EQM / UEQM flag indicates whether equal modulation was used in this transmission; it is set to 0 if equal modulation was used, and 1 otherwise. The beamforming flag indicates whether beamforming was used in this transmission; it is set to 1 if beamforming was used, and 0 otherwise. The coding flag indicates whether binary convolutional code (BCC) or LDPC encoding was used in this transmission.

[0298] As another example, the signaling field can be as follows: Figure 6B As shown, the signaling field may include at least one of the following: STA ID (11 bits, B0-B10), MCS field (4 bits, B11-B14), reserved (1 bit, B15), second NSS field (2 bits, B16-B17), operation information field (1 bit, B18), EQM / UEQM flag field (1 bit, B19, value 0), beamformed (1 bit, B20), and coding (1 bit, B21). A description of the second NSS field can be found below and will not be detailed here. Figure 6BThe signaling fields shown can be signaling fields in a PPDU for multicast transmission.

[0299] In the case of multicast transmission, the meaning of each field in this signaling field can be seen in Table 9.

[0300] Table 9

[0301]

[0302] about Figure 6B Other instructions are available for reference. Figure 6A This will not be elaborated upon here.

[0303] As another example, the signaling field can be as follows: Figure 7 As shown, the signaling field may include at least one of the following: STA ID (11 bits), MCS field (4 bits), reserve field (1 bit), NSS field (2 bits), EQM / UEQM flag field (1 bit), and UEQM pattern variations (per NSS) (2 bits).

[0304] When the EQM / UEQM flag indicates that the modulation scheme is UEQM, different spatial streams can correspond to different modulation QAM combinations. Optionally, the MCS field can indicate the MCS of one stream as the base MCS. Further, changes in the UEQM mode indicate the changes in the MCS of other spatial streams relative to the base MCS. That is, for a given spatial stream, changes in the UEQM mode can indicate the modulation QAM of other spatial streams. The reserved bits in this signaling field can be used to extend the MCS field defined in 802.11bn from 4 bits to 5 bits.

[0305] As yet another example, signaling fields can be as follows: Figure 8 As shown, the signaling field includes at least one of the following: STAID (occupying 11 bits), MCS field (occupying 4 bits), reserve field (occupying 1 bit), NSS and UEQM pattern variations (occupying 3 bits), EQM / UEQM flag field (occupying 1 bit), NSS and UEQM pattern variations extension or reserve (occupying 2 bits).

[0306] In this example, a single field can indicate both NSS and UEQM pattern variations. For Figure 8 Other instructions can be found here. Figure 7 This will not be elaborated upon here.

[0307] Understandable, such as Figure 6A or Figure 6B or Figure 7 or Figure 8 The positions and number of bits occupied by the various subfields included in the signaling fields shown are merely examples and should not be construed as limitations on the embodiments of this application. The signaling fields in the embodiments of this application may also be defined by standards or protocols (such as WiFi 7 or WiFi 8, or possibly Wi-Fi 9 or WiFi 10, or integrated millimeter wave standards (802.11bq), etc.). In this application, PPDU and signaling fields may also have other names, and this application does not limit the names of PPDU and signaling fields.

[0308] In one possible implementation, the first station can determine the operation information before sending it. For example, the first station might determine the operation information based on the transmission method. Alternatively, the first station might determine the operation information based on second capability information. Or, the first station might determine the operation information based on its supported LDPC code length and second capability information, or it might determine the operation information based on both first and second capability information.

[0309] Optionally, in the case of multicast transmission, the operation information may indicate whether the multicast, broadcast, or multicast transmission uses a second LDPC code length or a second code length parameter table. For example, a first site may correspond to at least two multicasts, and the operation information may indicate whether the first multicast in the at least two multicasts uses a second LDPC code length, or the operation information may indicate whether the second multicast in the at least two multicasts uses a second code length parameter table. Regarding the case of multicast transmission, the specific implementation of the content indicated by the operation information can refer to one or more of the examples one to three of the operation information shown above. Optionally, implementation methods two to five below can be combined with examples one to three above. The specific methods of combination will not be detailed here.

[0310] The specific details regarding the content of the operation information are as follows:

[0311] Implementation method 1:

[0312] Operational information may include a predefined ID, which indicates that the first station uses a second LDPC code length, or that the predefined ID indicates that the first station uses a second code length parameter table. Using a predefined ID to indicate the above information not only allows both the sender and receiver to clearly define the LDPC code length, but also saves signaling overhead.

[0313] For example, the predefined ID can be a predefined STA ID or a predefined AID. The value of the predefined STAID can be a value greater than or equal to 2008 and less than or equal to 2047.

[0314] As an example, a predefined STA ID of z1 indicates that the first site uses 2×LDPC. A predefined STA ID of z2 indicates that the first site uses 3×LDPC. A predefined STA ID of z3 indicates that the first site uses 4×LDPC. z1, z2, and z3 are any three different values ​​within the range of 2009 to 2047. For example, z1 could be 2009, z2 could be 2010, and z3 could be 2011.

[0315] As another example, when the predefined STA ID is z1, it indicates that the first station uses the second code length parameter table. The specific LDPC code length used by the first station can be further determined based on the second code length parameter table. The value range of z1 is 2008 to 2047, such as z1 being 2009.

[0316] As another example, when the predefined STA ID is z1, it indicates that the first station uses one of 2×LDPC, 3×LDPC, or 4×LDPC. The value of z1 ranges from 2008 to 2047, such as 2009.

[0317] Optionally, the predefined ID can be one value or two values. For example, predefined IDs of 0 and 2008 indicate that users associated with the first site do not use the second LDPC code length, or do not use the second code length parameter table. Similarly, predefined IDs of 2047 and 2009 indicate that users not associated with the first site use the second LDPC code length, or use the second code length parameter table.

[0318] Implementation Method Two:

[0319] In unicast transmission, the first MCS field occupies bits Bx1 to By1, where x1 and y1 are both positive integers, and y1 is greater than x1. In multicast transmission, Bx1 to By1 carry operation information and the second MCS field. For example, Bx1 to By1 represent the x1th to y1th bits of the first field. In multicast transmission, the operation information and the second MCS field are contained within the x1th to y1th bits of the first field. In unicast transmission, the first MCS field is contained within the x1th to y1th bits of the first field. This first field may be a signaling field, etc.

[0320] In this implementation, the number of bits occupied by the MCS field differs between unicast and multicast transmissions, and the content indicated by the index in the MCS field can also differ. For example, in multicast transmission, the number of bits occupied by the second MCS field is less than that of the first MCS field, and the bits saved by the second MCS field can be used to carry operational information. Thus, the purpose of indicating the LDPC code length is achieved without increasing signaling overhead.

[0321] For example, Bx1 represents the x1th bit of the signaling field, and By1 represents the y1th bit of the signaling field. (See figure...) Figure 6A or Figure 7 or Figure 8 For example, x1 is 11 and y1 is 14. In unicast transmission, the MCS used by the first station is indicated by the first MCS field (i.e., B x1 to By y1 in the signaling field), and the LDPC code length used by the first station is determined by the capability information of the first and second stations. In multicast transmission, B x1 to By y1 in the signaling field are used to indicate the MCS used by the first station and whether the first station uses the second LDPC code length (or to indicate whether the first station uses the second code length parameter table).

[0322] For example, Bx1 to By1 each include 4 bits, meaning the first MCS field can include 4 bits. For unicast transmission, these 4 bits can be used to indicate the MCS used by the first site. These 4 bits are used to indicate the index of the MCS used by the first site. In the case of unicast transmission, the correspondence between the index in the MCS field and the modulation scheme and code rate corresponding to the MCS can be shown in Table 10.

[0323] Table 10

[0324]

[0325]

[0326] It is understood that Table 10 uses a first MCS field containing 4 bits as an example. In the embodiments of this application, the first MCS field may include 5 bits (such as B11 to B15), or more bits. The correspondence between the MCS index, modulation scheme, and code rate shown in Table 10 is only an example and should not be construed as a limitation of this application. The correspondence between the number of bits in the first MCS field, the index in the first MCS field, the modulation scheme, and the code rate in the embodiments of this application may be predefined by standards or protocols.

[0327] As shown in Table 10, the data rate increases from MCS0 to MCS13. MCS14 and MCS15 are two special low-data-rate transmission modes. For multicast transmission, there are multiple receivers, and the channel conditions of multiple receivers need to be considered. Therefore, a lower-data-rate, more reliable transmission mode is usually required. Thus, in multicast transmission scenarios, a very high MCS is not necessary; fewer bits can be used to indicate the MCS used by the first site.

[0328] For example, the second MCS field may include 3 bits (e.g., B11-B13) (i.e., the second MCS field is obtained by compressing the first MCS field), and the operation information includes 1 bit (e.g., B14). That is, for multicast transmission, 3 bits indicate the MCS used by the first station, and 1 bit indicates whether the first station uses the second LDPC code length or whether the first station uses the second code length parameter table. In the case of multicast transmission, the correspondence between the index in this second MCS field and the modulation scheme and code rate can be shown as MCS0-MCS7 in Table 11.

[0329] Table 11

[0330]

[0331] For example, the operation information may be located before the second MCS field, or the operation information may be located after the second MCS field. This application does not restrict the order of the operation information and the second MCS field.

[0332] Implementation method three:

[0333] In unicast transmission, the first NSS field occupies bits Bx2 to By2, where x2 and y2 are both positive integers, and y2 is greater than x2. In multicast transmission, Bx2 to By2 carry operation information and the second NSS field. For example, Bx2 to By2 represent bits x1 to y1 of the second field. In multicast transmission, the operation information and the second NSS field are contained in bits x2 to y2 of the second field. In unicast transmission, the first NSS field is contained in bits x2 to y2 of the second field. The first and second fields can be the same field. For example, the second field can be a signaling field, etc.

[0334] In this transmission method, the number of bits occupied by the NSS field differs between unicast and multicast transmissions, and the content indicated by the index in the NSS field can also differ. For example, in multicast transmission, the number of bits occupied by the second NSS field is less than that of the first NSS field, and the bits saved by the second NSS field can be used to carry operational information. Thus, the purpose of indicating the LDPC code length is achieved without increasing signaling overhead.

[0335] For example, Bx2 represents the x2-th bit of the signaling field of the PPDU, and By2 represents the y2-th bit of the signaling field of the PPDU. For example, x2 is 16, y2 is 18, and the first NSS field can be as follows: Figure 6A The NSS field shown. For example, if x2 is 16 and y2 is 17, the first NSS field could be... Figure 7 The NSS field shown. For example, if x2 is 16 and y2 is 18, the first NSS field could be... Figure 8 The NSS and UEQM pattern change fields are shown. In unicast transmission, the NSS used by the first station is indicated by the first NSS field (i.e., B x2 to By2 in the signaling field), and the LDPC code length used by the first station is determined by the capability information of the first and second stations. In multicast transmission, B x2 to By2 in the signaling field are used to indicate the NSS used by the first station and whether the first station uses the second LDPC code length (or to indicate whether the first station uses the second code length parameter table).

[0336] For example, Bx2 to By2 include 3 bits, that is, the first NSS field may include 3 bits. For unicast transmission, the 3 bits can be used to indicate the NSS used by the first site. These 3 bits are used to indicate the NSS used by the first site. For example, these 3 bits indicate that 0 to 7 represent spatial stream 1 to spatial stream 8, respectively. In the case of unicast transmission, the correspondence between the index in the NSS field and the number of spatial streams (NSS) can be shown in Table 12.

[0337] Table 12

[0338] index Spatial Stream Number (NSS) 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8

[0339] It is understood that Table 12 uses the example of the first NSS field containing 3 bits. In the embodiments of this application, the first NSS field may include 4 bits or more bits. The correspondence between the index and NSS shown in Table 12 is only an example and should not be construed as a limitation of this application. The number of bits in the first NSS field and the correspondence between the index in the NSS field and the NSS in the embodiments of this application may be predefined by standards or protocols.

[0340] For multicast transmissions (such as multicast and / or broadcast transmissions), a high spatial stream is typically not used. Therefore, in multicast transmission scenarios, fewer bits can be used to indicate the NSS used by the first site. For example, some bits in the first NSS can be used to indicate the NSS used by the first site, while other bits are used to indicate whether the first site uses a second LDPC code length or a second code length parameter table.

[0341] For example, the second NSS field may include 2 bits (e.g., B16-B17), and the operation information includes 1 bit (e.g., B18). Figure 6B (As shown). That is, for multicast transmission, 2 bits are used to indicate the NSS used by the first station, and 1 bit is used to indicate whether the first station uses the second LDPC code length or whether the first station uses the second code length parameter table.

[0342] The correspondence between the index in the second NSS field and the NSS can be shown as NSS indices 0-3 in Table 12, and will not be elaborated further here. Alternatively, the second NSS field can also include fewer bits, such as 1 bit. The correspondence between the index in this second NSS field and the NSS can be shown as indices 0-1 in Table 12, and will not be elaborated further here.

[0343] For example, the operation information may be placed before the second NSS field, or the operation information may be placed after the second NSS field. This application does not restrict the order of the operation information and the second NSS field.

[0344] Implementation Method 4:

[0345] Operational information is carried in the MCS field. The index in the MCS field is the first value, indicating that the first site uses either the second LDPC code length or the second code length parameter table. The index in the MCS field is the second value, indicating that the first site uses either an LDPC code length less than or equal to 1944 or the first code length parameter table.

[0346] Optionally, the index in the MCS field can indicate different content in unicast and multicast transmissions.

[0347] As an example, the MCS field includes 4 bits (e.g., Figure 6A or Figure 7 or Figure 8 (See B11 to B14). For unicast transmission, the correspondence between the index in the MCS field and the modulation scheme and code rate is shown in Table 10, which will not be elaborated here. For multicast transmission, since a very high MCS (such as MCS10 to MCS13) is not required, the content indicated by the index in the MCS field can be redefined, so that the MCS field can indicate the MCS used by the first station and whether the first station uses the second LDPC code length or whether the first station uses the second code length parameter table.

[0348] For example, for multicast transmissions, the index of the MCS field and the content it indicates can be as shown in Table 13. Taking Table 13 as an example, the first value mentioned above can be a value between 10 and 13. The second value mentioned above can be a value between 0 and 9, 14, or 15.

[0349] Table 13

[0350]

[0351] As another example, besides redefining some existing unicast transmission indices, the reserved indices in a longer MCS field can be used to indicate whether a second LDPC code length or a second code length parameter table is used. For instance, if the MCS field includes 5 bits (such as B11–B15 in the signaling field), the MCS field indicates the MCS used by the first station and whether the first station uses a second LDPC code length or a second code length parameter table. For example, the index of the MCS field and its indicated content can be shown in Table 14. This example is applicable not only to broadcast and / or multicast transmissions but also to unicast transmissions.

[0352] Table 14

[0353]

[0354]

[0355] In this embodiment of the application, for multicast transmission, since the transmission rate is low, the index of the MCS can be reused to indicate the above information, indicating the LDPC code length while minimizing signaling overhead.

[0356] Implementation Method 5:

[0357] Operational information is carried in the NSS field. The index in the NSS field is the third value, indicating that the first site uses the second LDPC code length, or the first site uses the second code length parameter table. The index in the NSS field is the fourth value, indicating that the first site uses an LDPC code length less than or equal to 1944, or the first site uses the first code length parameter table.

[0358] In this implementation, since multicast transmission does not use a high spatial stream, the index in the NSS field can correspond to a lower spatial stream and indicate whether the first station uses the second LDPC code length or whether the first station uses the second code length parameter table. Therefore, the index of NSS can be reused to indicate the above information, indicating the LDPC code length while minimizing signaling overhead.

[0359] Optionally, the content indicated by the index in the NSS field can differ between unicast and multicast transmissions. For example, in the case of unicast transmission, the first and second stations can determine the LDPC code length to be used based on the first and second capability information without needing to indicate it through operation information. Furthermore, unicast transmission supports higher spatial streams; therefore, the index in the NSS field is used to indicate the NSS, without needing to indicate whether the first station uses a second LDPC code length or a second code length parameter table. The correspondence between the index in the NSS field and the NSS can be shown in Table 12. When the NSS field includes 3 bits, it can indicate eight different spatial streams.

[0360] As an example, the index in the NSS field and the content it indicates can be shown in Table 15. Taking Table 15 as an example, the third value mentioned above can be a value between 4 and 7, and the fourth value can be a value between 0 and 3. The first to fourth values ​​mentioned above are only examples. In specific implementations, the first and third values ​​may be the same or different; or the second and fourth values ​​may be the same or different. This application does not limit the specific values.

[0361] Table 15

[0362]

[0363] As shown in Table 15, in the case of multicast transmission, this NSS field can indicate four types of NSS.

[0364] As another example, the NSS field can have at least fewer spatial flows; for example, the NSS field can indicate only one or two spatial flows. Simultaneously, the NSS field can also indicate the LDPC code length used by the first site. For example, the index in this NSS field and the content it indicates can be shown in Table 16.

[0365] Table 16

[0366] index Spatial Stream Number (NSS) LDPC code length 0 1 Determined by the first code length parameter table 1 2 Determined by the first code length parameter table 2 1 2×LDPC 3 2 2×LDPC 4 1 3×LDPC 5 2 3×LDPC 6 1 4×LDPC 7 2 4×LDPC

[0367] Regarding implementation methods three and five, in the case of unicast transmission, the NSS field occupies three bits; in the case of multicast transmission, the NSS and operation information fields together occupy three bits. These three bits can all indicate 0 to 7. However, in this embodiment, the second station needs to determine the transmission method before parsing these three bits, as different transmission methods correspond to different interpretations. For example, in implementation methods three and five, for broadcast or multicast transmission, the NSS field occupies two bits, and the operation information occupies one bit. The second station can distinguish between unicast and multicast transmission based on the STA ID (for example only). If it is unicast transmission, these three bits indicate the NSS; if it is multicast transmission, two of these three bits indicate the NSS, and one of these three bits indicates whether a longer LDPC code length is used, or whether a code length parameter table including a longer LDPC code length is used. Optionally, the longer LDPC code length indicated by this one bit can include, but is not limited to, at least one of the following: 2×LPDC, 3×LDPC, or 4×LDPC.

[0368] 502, The second station determines the first LDPC code length based on the operation information. The first LDPC code length is the LDPC code length used by the first station.

[0369] As an example, the operation information indicates that the first site uses the second LDPC code length, which is the same as the first LDPC code length.

[0370] As another example, the operation information instructs the first station to use a second code length parameter table, which can be based on the total number of codeword bits N in this data transmission. avbits The first LDPC code length is determined by the second code length parameter table. At this time, the first LDPC code length may be the same as or different from the second LDPC code length.

[0371] As another example, the operation information instructs the first station not to use the second code length parameter table, and the second station can determine the first LDPC code length based on the first code length parameter table.

[0372] 503, the first station sends a PPDU, and the second station receives the PPDU accordingly.

[0373] The PPDU uses a first LDPC code length, and the second station can decode the PPDU based on the first LDPC code length.

[0374] In this embodiment, the first station sends operation information, enabling the second station to clearly know the LDPC code length it uses. Thus, the first and second stations maintain consistency in the LDPC code lengths they employ.

[0375] The embodiments shown above can be individual embodiments, or the embodiments can be combined with each other.

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

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

[0378] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application, such as... Figure 9 As shown, the communication device includes a processing module 901 and a transceiver module 902. The transceiver module 902 can implement corresponding communication functions, and the processing module 901 is used to implement corresponding processing functions. The transceiver module 902 can also be referred to as an interface, communication interface, or communication module, etc.

[0379] 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 communication device can be the first station itself or a chip or functional module configurable in the first station. The transceiver module 902 is used to perform the transceiver-related operations of the first station in the above method embodiments, and the processing module 901 is used to perform the processing-related operations of the first station in the above method embodiments.

[0380] For example, the processing module 901 is used to determine the first LDPC code length according to the transmission method; the transceiver module 902 is used to send or output PPDU.

[0381] Optionally, the transceiver module 902 is also used to send or output first capability information and receive or input second capability information.

[0382] Optionally, the transceiver module 902 is also used to send or output operation information.

[0383] It is understood that the specific implementation of the transmission method, the first LDPC code length, PPDU, the first capability information, the second capability information, and the operation information can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0384] Reuse Figure 9 In 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 communication device can be the second station itself or a chip or functional module configurable in the second station. The transceiver module 902 is used to perform the transceiver-related operations of the second station in the above method embodiments, and the processing module 901 is used to perform the processing-related operations of the second station in the above method embodiments.

[0385] For example, the processing module 901 is used to determine the first LDPC code length according to the transmission method; the transceiver module 902 is used to receive or input PPDU.

[0386] Optionally, the transceiver module 902 is also used to receive or input first capability information and send or output second capability information.

[0387] Optionally, the transceiver module 902 is also used to receive or input operation information.

[0388] It is understood that the specific implementation of the transmission method, the first LDPC code length, PPDU, the first capability information, the second capability information, and the operation information can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0389] Reuse Figure 9 In some other 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 communication device can be the first station itself or a chip or functional module configurable in the first station. The transceiver module 902 is used to perform the transceiver-related operations of the first station in the above method embodiments, and the processing module 901 is used to perform the processing-related operations of the first station in the above method embodiments.

[0390] For example, the processing module 901 is used to determine the operation information; the transceiver module 902 is used to send or output the operation information.

[0391] Optionally, the transceiver module 902 is also used to send or output first capability information and receive or output second capability information.

[0392] It is understood that specific descriptions of operational information, first capability information, and second capability information can be found in the relevant descriptions in the above method embodiments, and will not be elaborated here.

[0393] Reuse Figure 9In 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 communication device can be the second station itself or a chip or functional module configurable in the second station. The transceiver module 902 is used to perform the transceiver-related operations of the second station in the above method embodiments, and the processing module 901 is used to perform the processing-related operations of the second station in the above method embodiments.

[0394] For example, the transceiver module 902 is used to receive or input operation information; the processing module 901 is used to determine the first LDPC code length based on the operation information.

[0395] Optionally, the transceiver module 902 is also used to receive or input first capability information and send or output second capability information.

[0396] It is understood that specific descriptions of operational information, first capability information, and second capability information can be found in the relevant descriptions in the above method embodiments, and will not be elaborated here.

[0397] For example, the transceiver module 902 may include a radio frequency module, an antenna module, etc. For example, the transceiver module 902 may include a pin module, etc.

[0398] 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 901 can read the instructions and / or data from the storage module to enable the communication device to implement the aforementioned method embodiments. For example, the storage module can store the radio frequency signal transmission strategy, etc., as shown above.

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

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

[0401] The communication device according to the embodiments of this application has been described above. The following describes the possible product forms of the communication device. Any device possessing the above-described... Figure 7 Any form of the communication device described herein 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 in the embodiments of this application to this.

[0402] In one possible implementation, Figure 9In the communication device shown, the processing module 901 can be one or more processors, and the transceiver module 902 can be a transceiver, or the transceiver module 902 can also be a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can 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 can be coupled, etc., and the connection method between 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 can 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 can be the process of the processor receiving the above information input. 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 above information, the above information may need to undergo other processing before being input into the processor.

[0403] like Figure 10 As shown, the communication device 100 includes one or more processors 1020 and transceivers 1010.

[0404] In some embodiments of this application, the communication device can be used to perform the steps, methods, or functions performed by the first station described above, such as the processor 1020 being used to perform... Figure 9 The transceiver 1010 can be used to perform the functions or steps implemented by the processing module 901 shown. Figure 9 The transceiver module 902 shown illustrates the functions or steps implemented by this module. For detailed information on the processor 1020 and transceiver 1010, please refer to [link / reference needed]. Figure 9 Alternatively, the method embodiments shown above will not be described in detail here.

[0405] In other embodiments of this application, the communication device is used to perform the steps, methods, or functions performed by the second station described above, such as the processor 1020 being used to perform... Figure 9 The transceiver 1010 can be used to perform the functions or steps implemented by the processing module 901 shown. Figure 7 The transceiver module 902 shown illustrates the functions or steps implemented by this module. For detailed information on the processor 1020 and transceiver 1010, please refer to [link / reference needed]. Figure 9 Alternatively, the method embodiments shown above will not be described in detail here.

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

[0407] Optionally, the communication device 100 may further include one or more memories 1030 for storing program instructions and / or data. The memories 1030 are coupled to the processor 1020. 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 1020 may operate in conjunction with the memories 1030. The processor 1020 may execute program instructions stored in the memories 1030. Optionally, at least one of the aforementioned memories may be included in the processor.

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

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

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

[0411] The processor 1020 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1030 is mainly used to store software programs and data. The transceiver 1010 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0412] When the communication device is powered on, the processor 1020 can read the software program in the memory 1030, 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 1020 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit then performs RF processing on 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 1020. The processor 1020 converts the baseband signal into data and processes the data.

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

[0414] The communication device shown in the embodiments of this application may also have a higher... Figure 10This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver shown above are merely examples; the specific steps performed by the processor and transceiver can be found in the methods described above.

[0415] In another possible implementation Figure 9 In the communication device shown, the processing module 901 can be one or more logic circuits, and the transceiver module 902 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 902 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, integrated into one module, such as an input / output interface. Figure 11 As shown, Figure 11 The communication device shown includes logic circuit 1101 and interface 1102. That is, the processing module 901 can be implemented using logic circuit 1101, and the transceiver module 902 can be implemented using interface 1102. The logic circuit 1101 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 1102 can be a communication interface, input / output interface, pins, etc. For example, Figure 11 Taking the aforementioned communication device as an example, the chip includes a logic circuit 1101 and an interface 1102.

[0416] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 1101 can be used to perform... Figure 9 The processing module 901 shown implements the functions or steps, and the interface 1102 can be used to execute such functions or steps. Figure 9 The transceiver module 902 shown illustrates the functions or steps implemented by this module. For detailed information on logic circuit 1101 and interface 1102, please refer to [link / reference needed]. Figure 9 Alternatively, the method embodiments shown above will not be described in detail here.

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

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

[0419] This application also provides a computer program for implementing the operations and / or processes performed by a first site or a second site in the method provided in this application.

[0420] 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 a first or second site in the method provided in this application.

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

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

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

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

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

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

Claims

1. A communication method characterized by comprising: The method is applied to a first station, and the method comprises: determining a first low-density parity-check (LDPC) code length according to a transmission mode, the transmission mode comprising unicast transmission or groupcast transmission; sending a physical layer protocol data unit (PPDU) using the first LDPC code length.

2. The method of claim 1, wherein, The method further comprises: sending first capability information indicating whether the first station supports a second LDPC code length, the second LDPC code length being greater than 1944; receiving second capability information indicating whether a second station supports the second LDPC code length.

3. The method according to claim 1 or 2, characterized in that, The determination of the first LDPC code length according to the transmission mode comprises: in the case where the transmission mode is groupcast transmission, determining the first LDPC code length according to a first code length parameter table, the first code length parameter table comprising an LDPC code length not greater than 1944.

4. The method according to any one of claims 1 to 3, characterized in that, In the case where the transmission mode is groupcast transmission, the method further comprises: sending operation information indicating whether the first station uses the second LDPC code length or whether the first station uses a second code length parameter table, the second code length parameter table comprising a second LDPC code length.

5. The method of claim 4, wherein, The sending of the operation information comprises: sending the operation information according to the first capability information and the second capability information.

6. The method according to claim 4 or 5, characterized in that, The operation information indicates whether the first station uses the second LDPC code length in a first groupcast of at least two groupcasts corresponding to the first station or whether the first station uses the second code length parameter table in a second groupcast of the at least two groupcasts.

7. The method according to claim 4 or 5, characterized in that, The operation information comprises a predefined identifier (ID). The predefined ID indicates that the first station uses the second LDPC code length; or The predefined ID indicates that the first station uses the second code length parameter table.

8. The method of claim 4 or 5, wherein in the case where the transmission mode is groupcast transmission, the operation information and a second modulation and coding strategy (MCS) field are carried in Bx1-By1; and in the case where the transmission mode is unicast transmission, Bx1-By1 carries a first MCS field. wherein x1 and y1 are positive integers, and y1 is greater than x1.

9. The method of claim 4 or 5, wherein in the case where the transmission mode is groupcast transmission, the operation information and a number of spatial streams (NSS) field are carried in Bx2-By2; and in the case where the transmission mode is unicast transmission, Bx2-By2 carries a first NSS field. wherein x2 and y2 are positive integers, and y2 is greater than x2.

10. The method of claim 4 or 5, wherein, The operation information is carried in an MCS field. An index in the MCS field is a first value, the first value indicating that the first station uses the second LDPC code length or that the first station uses the second code length parameter table. an index in the MCS field is a second value, the second value indicating that the first station adopts an LDPC code length less than or equal to 1944 or adopts a first code length parameter table.

11. The method of claim 4 or 5, wherein, the operation information is carried in an NSS field; an index in the NSS field is a third value, the third value indicating that the first station adopts the second LDPC code length or adopts the second code length parameter table; an index in the NSS field is a fourth value, the fourth value indicating that the first station adopts an LDPC code length less than or equal to 1944 or adopts a first code length parameter table.

12. The method according to any one of claims 4-10, characterized in that, the operation information is included in a signaling field in a management frame or a physical layer protocol data unit (PPDU).

13. The method of claim 1 or 2, wherein, the first LDPC code length is determined according to a transmission mode, including: in a case where the transmission mode is unicast transmission and the first station and the second station support the second LDPC code length, the first LDPC code length is determined according to the second code length parameter table; or in a case where the transmission mode is unicast transmission and the first station or the second station does not support the second LDPC code length, the first LDPC code length is determined according to the first code length parameter table.

14. A communication method, comprising: the method is applied to a first station, and the method includes: a first station determines operation information, the operation information being used to indicate whether an LDPC code length adopted by the first station is a second LDPC code length or the operation information being used to indicate whether the first station adopts a second code length parameter table, the second code length parameter table including the second LDPC code length, the second LDPC code length being greater than 1944; the first station transmits the operation information.

15. The method of claim 14, wherein, the transmission mode of the first station is groupcast transmission.

16. The method according to claim 14 or 15, characterized in that the operation information includes a predefined identification (ID); the predefined ID is used to indicate that the LDPC code length adopted by the first station is the second LDPC code length; or the predefined ID is used to indicate that the first station adopts the second code length parameter table.

17. The method of claim 14 or 15, wherein: in a case where the transmission mode is groupcast transmission, the operation information and a second modulation and coding strategy (MCS) field are carried in Bx1-By1; in a case where the transmission mode is unicast transmission, Bx1-By1 carries a first MCS field; wherein x1 and y1 are both positive integers, and y1 is greater than x1.

18. The method of claim 14 or 15, wherein: in a case where the transmission mode is groupcast transmission, the operation information and a second number of spatial streams (NSS) field are carried in Bx2-By2; in a case where the transmission mode is unicast transmission, Bx2-By2 carries a first NSS field; wherein x2 and y2 are both positive integers, and y2 is greater than x2.

19. The method of claim 14 or 15, wherein, the operation information is carried in an MCS field; the index in the MCS field is a first value, the first value indicating that the first station adopts an LDPC code length being the second LDPC code length, or the first station adopts the second code length parameter table; the index in the MCS field is a second value, the second value indicating that the first station adopts an LDPC code length being less than or equal to 1944, or the first station adopts a first code length parameter table.

20. The method of claim 14 or 15, wherein, the operation information is carried in a NSS field; the index in the NSS field is a third value, the third value indicating that the first station adopts an LDPC code length being the second LDPC code length, or the first station adopts the second code length parameter table; the index in the NSS field is a fourth value, the fourth value indicating that the first station adopts an LDPC code length being less than or equal to 1944, or the first station adopts a first code length parameter table.

21. The method according to any one of claims 14-20, characterized by, the operation information is included in a signaling field in a management frame or a physical layer protocol data unit (PPDU).

22. The method according to any one of claims 14-21, characterized by, The method further comprises: sending first capability information, the first capability information being used to indicate whether the first station supports a second LDPC code length, the second LDPC code length being greater than 1944; receiving second capability information, the second capability information being used to indicate whether a second station supports the second LDPC code length.

23. The method of claim 22, wherein, The determining operation information comprises: determining the operation information according to the first capability information and the second capability information.

24. A communications device, characterized by A module for performing the method of any one of claims 1-23.

25. A computer-readable storage medium, characterized in that, A computer readable storage medium for storing a computer program, the computer program being executed by a computer to perform the method of any one of claims 1-23.

26. A computer program product, characterised in that, A computer program product being executed by a computer to perform the method of any one of claims 1-23.

Images