Communication method and communication apparatus

Abstract

The present application relates to the technical field of wireless communications, and in particular to a communication method and a communication apparatus. The method comprises: a first station and a second station determine a first LDPC codeword length on the basis of a transmission mode, or a second station determines a first LDPC codeword length on the basis of operation information. The first station transmits a PPDU, and correspondingly, the second station receives the PPDU, wherein the PPDU uses the first LDPC codeword length. The present application can support IEEE protocols, such as the IEEE 802.11be protocol, the IEEE 802.11bn protocol, IEEE integrated millimeter-wave protocols, the IEEE 802.15 protocol, or the IEEE 802.11bf / sensing protocol. The technical solutions provided in embodiments of the present application can also be applied to a SparkLink system and support the SparkLink standard protocol.

Description

Communication method and communication apparatus

[0001] This application claims priority to the Chinese patent application No. 202411245742.0, filed on September 5, 2024, with the State Intellectual Property Office of China, and the Chinese patent application No. 202411245742.0 has the invention name of “Communication method and communication apparatus”, the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a communication method and a communication apparatus. BACKGROUND

[0003] Wireless local area network (WLAN) starts from 802.11a / b / g, goes through 802.11n, 802.11ac, 802.11ax, 802.11be and 802.11bn. Among them, 802.11a / b / g protocols are collectively referred to as non high throughput (non-HT), 802.11n protocol is referred to as high throughput (HT), 802.11ac protocol is referred to as very high throughput (VHT), 802.11ax protocol is referred to as high efficient (HE), 802.11be protocol is referred to as extremely high throughput (EHT), and 802.11bn protocol is referred to as ultra high reliability (UHR). Low density parity check (LDPC) coding is introduced from 802.11n. LDPC code has the following advantages: good error performance can be obtained without deep interleaving; better frame error rate performance; greatly reduced error floor; decoding is not based on grid; supports parallel decoding, small decoding delay, etc.

[0004] LDPC code is a kind of linear block code with sparse check matrix, which has the characteristics of flexible structure and low decoding complexity. LDPC code can be used as error correction code in communication system, thereby improving the reliability and power utilization rate of channel transmission.

[0005] LDPC code contains a variety of different code lengths (codeword length), so how to select a suitable LDPC code length for a station is a problem to be solved. SUMMARY

[0006] The embodiment of the present application provides a communication method and a communication device, and the flexibility of determining a low density parity check (LDPC) code length by a station is improved.

[0007] In a first aspect, the embodiment of the present application provides a communication method, which is applied to a first station, the first station comprising a wireless local area network (WLAN) device (including a Wi-Fi device or a device involved in a star alliance), or a chip, a functional module, a processing system or a communication component which can be arranged in the WLAN device. The method comprises the following steps:

[0008] determining a first low density parity check (LDPC) code length according to a transmission mode, the transmission mode comprising unicast transmission or groupcast transmission; and transmitting a physical protocol data unit (PPDU), the PPDU adopting the first LDPC code length.

[0009] If the PPDU comprises a data field, the data field adopts the first LDPC code length.

[0010] In the embodiment of the present application, the first station determines the first LDPC code length according to different transmission modes, so that the first station can flexibly determine the LDPC code length corresponding to the transmission mode, and the first LDPC code length is more matched with the transmission mode.

[0011] In a possible implementation manner, the method further comprises the following steps: transmitting first capability information, the first capability information being used for indicating whether the first station 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 for indicating whether a second station supports the second LDPC code length.

[0012] The second LDPC code length can include one or more of 3888 (i.e., 1944*2), 5832 (i.e., 1944*3), and 7776 (i.e., 1944*4). For example, the second LDPC code length includes 2xLDPC. For another example, the second LDPC code length includes 2xLDPC and 3xLDPC, and the like, which are not listed one by one here. The 3888 can also be referred to as a 2x1944 code length, the 5832 can also be referred to as a 3x1944 code length, and the 7776 can also be referred to as a 4x1944 code length, and can also be referred to as a 2x code length, a 3x code length, and a 4x code length, respectively, and can also be referred to as a 2xLDPC, a 3xLDPC, and a 4xLDPC, respectively. The code lengths listed here are only examples, and later stations can also support longer code lengths as the standard evolves. For example, the second LDPC code length can also include 2x1296, or 3x1296, and the like, which are not listed one by one here.

[0013] Optionally, the first capability information is contained in a management frame. Optionally, the second capability information is contained in a management frame. The present application does not limit the order in which the first station sends the first capability information and the second station sends the second capability information.

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

[0015] Generally speaking, both the transmitting end and the receiving end must support the three code lengths of 648, 1296, and 1944, and the LDPC code length used by both the transmitting end and the receiving end is determined according to the first code length parameter table. However, in the above scheme, the introduction of a longer LDPC code length is not considered, and whether a station supports a longer LDPC code length is optional. Therefore, in the embodiments of the present application, whether a second LDPC code length is supported between stations through interaction can enable the transmitting end and the receiving end to clearly know whether the opposite end supports the second LDPC code length.

[0016] In a possible implementation, the first LDPC code length is determined according to the transmission mode, including: in a case where the transmission mode is groupcast transmission, the first LDPC code length is determined according to a first code length parameter table, and the first code length parameter table does not include an LDPC code length greater than 1944, or in other words, the LDPC code lengths contained in the first code length parameter table are not greater than 1944.

[0017] The first code length parameter table can include one or more of 648, 1296, or 1944, such as the first code length parameter table including 648, 1296, and 1944. The first LDPC code length determined by the first code length parameter table is 648 or 1296 or 1944.

[0018] Generally, the transceiver end and the receiving end must support the three code lengths of 648, 1296, and 1944, and the transceiver end determines the LDPC code length to be used according to the first code length parameter table. However, in the above scheme, a longer LDPC code length is not introduced, and whether the station supports the longer LDPC code length is optional. Especially in the case of multicast (multicast or broadcast) transmission, there are multiple receiving ends (i.e., multiple second stations). The multicast transmission is different from the unicast transmission, in which the transceiver end and the receiving end have a unified awareness of the capability support, while in the multicast transmission, it is not clear whether the multiple receiving ends can use a longer LDPC code length, and whether the longer LDPC code length is used by the transmitting end when transmitting. Therefore, in the case of multicast transmission, whether the first station supports the second LDPC code length, the first station determines the first LDPC code length according to the first code length parameter table, and similarly, the second station also determines the first LDPC code length according to the first code length parameter table, so that the transceiver end and the receiving end can keep unified on the LDPC code length used, and then ensure that the receiving end can correctly decode the PPDU sent by the transmitting end.

[0019] In a possible implementation, the first LDPC code length is determined according to the transmission mode, including: in the case of multicast transmission, the first LDPC code length is determined according to the first code length parameter table, the first code length parameter table does not include an LDPC code length greater than 3888, or in other words, the LDPC code length included in the first code length parameter table is not greater than 3888.

[0020] In this implementation, the transceiver end and the receiving end must support the four code lengths of 648, 1296, 1944, and 3888. In this case, when the transmission mode is multicast transmission, the first station determines the first LDPC code length according to the code length parameter table including one or more of 3888, 1944, 1296, or 648.

[0021] In a possible implementation, in the case of multicast transmission, the method further includes: sending operation information, the operation information being used to indicate whether the LDPC code length used by the first station is the second LDPC code length, or the operation information being used to indicate whether the first station uses the second code length parameter table including the second LDPC code length.

[0022] The LDPC code length used by the first station refers to the LDPC code length used by the first station when performing one or more of multicast or broadcast transmission, or the code length parameter table used.

[0023] Optionally, the operation information is contained in a signal (SIG) field in a management frame or a PPDU. The SIG field includes a general SIG field. Alternatively, the SIG field includes a SIG field corresponding to a standard to which the PPDU belongs, such as a UHR-SIG field when the PPDU is an ultrahigh reliability (UHR) PPDU.

[0024] In a case where the operation information is used to indicate that the first station adopts a first LDPC code length that is the same as a second LDPC code length, the first LDPC code length is the same as the second LDPC code length. In a case where the operation information is used to indicate that the first station adopts a second code length parameter table, the first LDPC code length can be the same as or different from the second LDPC code length.

[0025] In the embodiments of the present application, in a case where the transmission mode is groupcast transmission, the first station can enable the second station to clearly know the LDPC code length adopted by the second station by sending the operation information. Thus, the first station and the second station keep the LDPC code lengths adopted by them consistent, and then the second station can correctly decode the PPDU (i.e., the PPDU encoded by using the first LDPC code length) sent by the first station.

[0026] In a possible implementation, in a case where the transmission mode is groupcast transmission, the sending of the PPDU includes: sending the PPDU including the operation information. For example, the operation information is contained in a SIG field in the PPDU.

[0027] In a possible implementation, the sending of the operation information includes: sending the operation information according to the LDPC code length supported by the first station and the second capability information.

[0028] In a possible implementation, the sending of the operation information includes: sending the operation information according to the first capability information and the second capability information.

[0029] In the embodiments of the present application, the first station sends the operation information in combination with the first capability information and the second capability information, which can make the LDPC code lengths adopted by the two stations more matched with the respective capabilities, and enable the two stations to adopt a longer LDPC code length.

[0030] In a possible implementation, the operation information is used to indicate whether the LDPC code length adopted by the first station in a first groupcast of at least two groupcasts corresponding to the first station is the second LDPC code length, or the operation information is used to indicate whether a second code length parameter table is adopted by the first station in a second groupcast of the at least two groupcasts.

[0031] In the embodiments of the present application, the information is indicated by different multicast indications, so as to ensure the LDPC code length in each multicast as far as possible, and make the determined LDPC code length in each multicast more accurate.

[0032] In a possible implementation, the operation information includes a predefined identifier (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.

[0033] In the embodiments of the present application, the information is indicated by the predefined ID, so as to make the transceiving parties clear the LDPC code length, and save the signaling overhead.

[0034] In a possible implementation, in the case of unicast transmission, the first modulation and coding scheme (MCS) field occupies Bx1-B y1 bits, x1 and y1 are positive integers, and y1 is greater than x1; in the case of multicast transmission, Bx1-B y1 carries the operation information and the second MCS field.

[0035] Bx1-B y1 represents the position of the first MCS in a field. For example, the first MCS field is included in the SIG field in the PPDU, and the first MCS field occupies the x1th bit to the y1th bit in the SIG field. For multicast transmission, the x1th bit to the y1th bit in the SIG field carries the operation information and the second MCS field.

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

[0037] In a possible implementation, in the case of unicast transmission, the first number of spatial stream (NSS) field occupies Bx2-B y2 bits, x2 and y2 are positive integers, and y2 is greater than x2; in the case of multicast transmission, Bx2-B y2 carries the operation information and the second NSS field.

[0038] In a possible implementation, the operation information is carried in the MCS field; an index in the MCS field is a first 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; and an 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 the first code length parameter table.

[0039] Optionally, the index in the MCS field can indicate different contents in the unicast transmission and the multicast transmission.

[0040] In the embodiments of the present application, for the multicast transmission, the index of the MCS can be reused to indicate the above information, so as to indicate the LDPC code length while reducing the signaling overhead as much as possible.

[0041] In a possible implementation, the operation information is carried in the NSS field; an 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; and an 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.

[0042] Optionally, the index in the NSS field can indicate different contents in the unicast transmission and the multicast transmission.

[0043] In a possible implementation, the first LDPC code length is determined according to the transmission mode, including: in a case where the transmission mode is the 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 the 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.

[0044] In the embodiments of the present application, the LDPC code length determined according to different transmission modes or the code length parameter table used to determine the LDPC code length can be different. For the unicast transmission, the transceiver station can determine whether to use the code length parameter table including the longer code length to select the LDPC code length according to whether the opposite station and itself support the second LDPC code length, so as to not only ensure that the transceiver station uses the more suitable LDPC code length, but also ensure that the LDPC code lengths determined by the transceiver station are unified.

[0045] In a second aspect, the embodiments of the present application provide a communication method, which is applied to a first station, the first station comprising a WLAN device (including a Wi-Fi device or a device involved in the Star Alliance, etc.), or a chip, a functional module, a processing system or a communication component which can be arranged in the WLAN device. The method comprises the following steps:

[0046] The first station determines operation information, the operation information being used to indicate whether the LDPC code length adopted by the first station is the second LDPC code length, or the operation information being used to indicate whether the first station adopts the second code length parameter table, the second code length parameter table comprising the second LDPC code length, and the second LDPC code length being greater than 1944; and the first station transmits the operation information.

[0047] In a possible implementation, the transmission mode of the first station is groupcast transmission.

[0048] In a possible implementation, the operation information comprises a predefined 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.

[0049] In a possible implementation, in the case of unicast transmission, the first MCS field occupies bits Bx1-B y1, x1 and y1 are both positive integers, and y1 is greater than x1; and in the case of groupcast transmission, Bx1-B y1 carries the operation information and the second MCS field.

[0050] In a possible implementation, in the case of unicast transmission, the first NSS field occupies bits Bx2-B y2, x2 and y2 are both positive integers, and y2 is greater than x2; and in the case of groupcast transmission, Bx2-B y2 carries the operation information and the second NSS field.

[0051] In a possible implementation, the operation information is carried in the MCS field; an index in the MCS field is a first value, the first value indicating that the LDPC code length adopted by the first station is the second LDPC code length, or the first station adopts the second code length parameter table; and the index in the MCS field is a second value, the second value indicating that the LDPC code length adopted by the first station is less than or equal to 1944, or the first station adopts the first code length parameter table.

[0052] In a possible implementation, the operation information is carried in an NSS field; an index in the NSS field is a third value, which indicates that the first station adopts an LDPC code length as a second LDPC code length, or the first station adopts a second code length parameter table; and an index in the NSS field is a fourth value, which indicates that the first station adopts an LDPC code length less than or equal to 1944, or the first station adopts a first code length parameter table.

[0053] In a possible implementation, the operation information is contained in a signaling field in a management frame or a PPDU.

[0054] In a possible implementation, the method further includes: 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; and receiving second capability information, the second capability information being used to indicate whether the second station supports the second LDPC code length.

[0055] In a possible implementation, determining the operation information includes: determining the operation information according to the first capability information and the second capability information.

[0056] The description of the second aspect can refer to the first aspect, and will not be repeated here.

[0057] In a third aspect, an embodiment of the present application provides a communication method, which is applied to a second station, the second station including a WLAN device (including a Wi-Fi device or a device involved in the Star Alliance, etc.), or a chip, a functional module, a processing system or a communication component, etc. that can be arranged in the WLAN device. The method includes:

[0058] determining the first LDPC code length according to a transmission mode, the transmission mode including unicast transmission or groupcast transmission; and receiving a PPDU, the PPDU adopting the first LDPC code length.

[0059] In a possible implementation, the method further includes: receiving 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; and sending second capability information, the second capability information being used to indicate whether the second station supports the second LDPC code length.

[0060] In a possible implementation, determining the first LDPC code length according to the transmission mode includes: in a 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 not including an LDPC code length greater than 1944, or in other words, the first code length parameter table containing an LDPC code length not greater than 1944.

[0061] In a possible implementation, when the transmission mode is the groupcast transmission, the method further includes: receiving operation information, the operation information being used to indicate whether the first LDPC code length adopted by the first station is the second LDPC code length, or the operation information being used to indicate whether the first station adopts the second code length parameter table including the second LDPC code length.

[0062] In a possible implementation, when the transmission mode is the groupcast transmission, receiving the PPDU includes: receiving the PPDU including the operation information.

[0063] In a possible implementation, the first LDPC code length is determined according to the transmission mode, including: when the transmission mode is the groupcast transmission, the first LDPC code length is determined according to the operation information.

[0064] In a possible implementation, the operation information is used to indicate whether the LDPC code length adopted by the first station in a first groupcast of the at least two groupcasts corresponding to the first station is the second LDPC code length, or the operation information is used to indicate whether a second groupcast of the at least two groupcasts corresponding to the first station adopts the second code length parameter table.

[0065] In a possible implementation, the operation information includes a predefined 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.

[0066] In a possible implementation, when the transmission mode is the unicast transmission, the first MCS field occupies bits Bx1-B y1, x1 and y1 are positive integers, and y1 is greater than x1; when the transmission mode is the groupcast transmission, Bx1-B y1 carries the operation information and the second MCS field.

[0067] In a possible implementation, when the transmission mode is the unicast transmission, the first NSS field occupies bits Bx2-B y2, x2 and y2 are positive integers, and y2 is greater than x2; when the transmission mode is the groupcast transmission, Bx2-B y2 carries the operation information and the second NSS field.

[0068] In a possible implementation, the operation information is carried in the MCS field; an index in the MCS field is a first value, the first value indicating that the LDPC code length adopted by the first station is 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 LDPC code length adopted by the first station is less than or equal to 1944, or the first station adopts the first code length parameter table.

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

[0070] In a possible implementation, the first LDPC code length is determined according to the 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.

[0071] In a fourth aspect, an embodiment of the present application provides a communication method, which is applied to a second station, the second station including a WLAN device (including a Wi-Fi device or a device involved in the Star Alliance, etc.), or a chip, a functional module, a processing system or a communication component, etc. that can be arranged in the WLAN device. The method includes:

[0072] receiving operation information, the operation information being used to indicate whether the LDPC code length adopted by the first station is the second LDPC code length, or the operation information being used to indicate whether the first station adopts the second code length parameter table, the second code length parameter table including the second LDPC code length, and the second LDPC code length being greater than 1944; and determining the first LDPC code length according to the operation information.

[0073] In a possible implementation, the transmission mode of the second station is groupcast transmission.

[0074] In a possible implementation, the operation information includes a predefined 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.

[0075] In a possible implementation, in a case where the transmission mode is unicast transmission, the first MCS field occupies bits Bx1-B y1, x1 and y1 are both positive integers, and y1 is greater than x1; and in a case where the transmission mode is groupcast transmission, the Bx1-B y1 carries the operation information and the second MCS field.

[0076] In a possible implementation, in the case of unicast transmission, the first NSS field occupies Bx2~By2 bits, x2 and y2 are positive integers, and y2 is greater than x2; in the case of groupcast transmission, Bx2~By2 carries the operation information and the second NSS field.

[0077] In a possible implementation, the operation information is carried in the MCS field; an 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; an 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.

[0078] In a possible implementation, the operation information is carried in the NSS field; an index in the NSS field is a third 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; an 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 a first code length parameter table.

[0079] In a fifth aspect, an embodiment of the present application provides a communication apparatus, which is configured to execute the method in any one of the first aspect to the fourth aspect or any possible implementation.

[0080] In a sixth aspect, an embodiment of the present application provides a communication apparatus, which includes a processor and a transceiver, the processor is configured to execute the processing steps in the method in any one of the first aspect to the fourth aspect or any possible implementation, and the transceiver is configured to execute the transceiving steps in the method in any one of the first aspect to the fourth aspect or any possible implementation.

[0081] In a seventh aspect, an embodiment of the present application provides a communication apparatus, which includes a logic circuit and an interface, the logic circuit and the interface are coupled; the interface is configured to input and / or output information, and the logic circuit is configured to execute the processing steps in the method in any one of the first aspect to the fourth aspect or any possible implementation.

[0082] In an eighth aspect, an embodiment of the present application provides a computer readable storage medium, which is configured to store a computer program, when the computer program is executed on a computer, the method in any one of the first aspect to the fourth aspect or any possible implementation is executed.

[0083] In a ninth aspect, an embodiment of the present application provides a computer program product, which, when executed on a computer, causes the method of any one of the first aspect to the fourth aspect or any possible implementation manner thereof to be performed.

[0084] In a tenth aspect, an embodiment of the present application provides a communication system, which comprises a first station configured to perform the method of the first aspect or the second aspect or any possible implementation manner thereof, and a second station configured to perform the method of the third aspect or the fourth aspect or any possible implementation manner thereof. BRIEF DESCRIPTION OF DRAWINGS

[0085] FIG. 1 is a structural schematic diagram of a communication system according to an embodiment of the present application;

[0086] FIG. 2A is a flow schematic diagram of a communication method according to an embodiment of the present application;

[0087] FIG. 2B is a flow schematic diagram of another communication method according to an embodiment of the present application;

[0088] FIG. 2C is a flow schematic diagram of still another communication method according to an embodiment of the present application;

[0089] FIG. 3 is a structural schematic diagram of a capability information element according to an embodiment of the present application;

[0090] FIG. 4 is a structural schematic diagram of an operation parameter element according to an embodiment of the present application;

[0091] FIG. 5 is a flow schematic diagram of still another communication method according to an embodiment of the present application;

[0092] FIG. 6A is a structural schematic diagram of a signaling field according to an embodiment of the present application;

[0093] FIG. 6B is a structural schematic diagram of another signaling field according to an embodiment of the present application;

[0094] FIG. 7 is a structural schematic diagram of still another signaling field according to an embodiment of the present application;

[0095] FIG. 8 is a structural schematic diagram of still another signaling field according to an embodiment of the present application;

[0096] FIG. 9 is a structural schematic diagram of a communication apparatus according to an embodiment of the present application;

[0097] FIG. 10 is a structural schematic diagram of another communication apparatus according to an embodiment of the present application;

[0098] FIG. 11 is a structural schematic diagram of still another communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0099] The terms "first" and "second" and the like in the specification and claims of this application are used for distinguishing between similar elements and not necessarily for describing a sequential or chronological order. The terms "a" and "an" and "the" and similar reference used in this application do not denote a limitation on the number of entities to which the modifier is applied but are to be construed as referring to at least one. The phrase "at least one of" followed by a list of two or more items, such as "at least one of A and B", is intended to cover the instances where any one of the items in the list of A and B is present alone, as well as instances where A and B are present together or in combination with one or more of the items not listed. The phrase "one or more of" followed by a list of two or more items, such as "one or more of A and B", is intended to cover the instances where one or more of the items in the list of A and B is present alone, as well as instances where A and B are present together or in combination with one or more of the items not listed. The phrase "at least one of" followed by a list of two or more items, such as "at least one of A and B", is intended to cover the instances where any one of the items in the list of A and B is present alone, as well as instances where A and B are present together or in combination with one or more of the items not listed. The phrase "one or more of" followed by a list of two or more items, such as "one or more of A and B", is intended to cover the instances where one or more of the items in the list of A and B is present alone, as well as instances where A and B are present together or in combination with one or more of the items not listed. The character " / " is generally used to represent an "or" relationship between the associated objects in front and behind.

[0100] Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase "in an embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily mutually exclusive of one another. Those skilled in the art will appreciate that embodiments described herein can be combined with other embodiments.

[0101] In this application, "at least one", "multiple", "plurality", or "two or more" means two or more. "And / or" used in the context of a list of two or more items, such as "A and / or B", means that any of the items can be present alone, used in combinations with each other or in combination with one or more of the items not listed. "Or" means one is present alone, the other is present alone, or both are present, unless the context clearly indicates otherwise. The character " / " generally represents an "or" relationship between the associated objects in front and behind. "At least one of" or similar expressions means any combination of these items. For example, at least one 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".

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

[0103] In the present application, "sending" and "receiving" represent the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, which can include direct transmission through the air interface, or indirect transmission through the air interface by other units or modules. "Receiving information from YY" can be understood as the source of the information being YY, which can include direct reception from YY through the air interface, or indirect reception from YY through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be between devices, such as between network devices and terminal devices, or within devices, such as between components, modules, chips, software modules or hardware modules within a device through a bus, wire or interface.

[0104] The technical solutions provided by the embodiments of the present application can be applied to a wireless local area network (WLAN) system, support 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 mmWave (IMMW) IMMW protocol, IEEE 802.15 / ultra wideband (UWB) protocol, or IEEE 802.11bf / sensing protocol; the technical solutions provided by the embodiments of the present application can also be applied to a spark link (SL) system, support a spark link (or nearlink) protocol. The technical solutions provided by the embodiments of the present application can also be applied to a communication system, for example, can be an internet of things (IoT) system, a vehicle-to-everything (V2X, X can represent any thing) system, a device-to-device (D2D) system, a narrow band internet of things (NB-IoT) system, a long term evolution (LTE) system, a 5th-generation (5G) communication system, and a new communication system that appears in future communication development, and the like. For example, the V2X can include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P) or vehicle-to-network (V2N) communication, and the like.

[0105] The WLAN system can provide high-rate and low-latency transmission. As the WLAN application scenarios evolve, the WLAN system 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, sports venues, exhibition halls, concert halls, hotel rooms, dormitories, hospital rooms, classrooms, supermarkets, squares, streets, manufacturing workshops, and warehouses. Of course, the devices (such as access points or stations) that support WLAN communication or sensing can be sensor nodes in smart cities (such as smart water meters, smart electricity meters, and smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, televisions, sound systems, refrigerators, washing machines, and the like), nodes in the Internet of Things, entertainment terminals (such as augmented reality (AR) and virtual reality (VR) wearable devices), smart devices in smart offices (such as printers, projectors, amplifiers, sound systems, and the like), Internet of Vehicles devices in the Internet of Vehicles, infrastructure in daily life scenarios (such as vending machines, self-service navigation stations in supermarkets, self-service checkout devices, and self-service ordering machines), and devices in large sports and music venues.

[0106] Although the embodiments of the present application mainly take WLAN as an example, especially the network applied to the IEEE 802.11 series standard. The various aspects involved in the embodiments of the present application can be extended to other networks using 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 network (WAN) or other now known or later developed networks.

[0107] In a possible implementation, the method provided by the embodiments of the present application 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).

[0108] The AP is a device with wireless communication function, which supports communication or sensing or energy transmission using WLAN protocol, has the function of communication or sensing with other devices (such as non-AP STA or other access points) in the WLAN network or energy transmission, and of course, can also have the function of communication or sensing or energy transmission with devices in other networks. Alternatively, the access point is equivalent to a bridge connecting wired and wireless networks, and its main function is to connect various wireless network clients together and then access the wireless network to the Ethernet. In the WLAN system, the access point can be referred to as an access point station (AP STA). The device with wireless communication function can be a whole machine device, or a chip, processing system or functional module installed in the whole machine device, and the device installed with the chip or processing system or functional module can realize the method and function of the embodiments of the application under the control of the chip or processing system or functional module. The AP in the embodiments of the application is a device providing services for non-AP STA, which can support 802.11 series protocol or subsequent protocol, etc. For example, the access point can be an access point for terminals (such as mobile phones) to enter wired (or wireless) networks, and is mainly deployed in homes, buildings and parks, with a typical coverage radius of tens of meters to hundreds of meters, and of course, can also be deployed outdoors. For another example, the AP can be a communication server, a router, a switch, a network bridge and the like; the AP can include various forms of macro base stations, micro base stations, relay stations and the like.

[0109] The non-AP STA is a device with wireless communication function, which supports communication or sensing or energy transmission using WLAN protocol, has the ability of communication or sensing or energy transmission with other non-AP STAs or access points in the WLAN network. In the WLAN system, the non-AP STA is any user communication device that allows users to communicate or sense or transmit energy with the AP and then communicate with the WLAN. The device with wireless communication function can be a whole machine device, or a chip, processing system or functional module installed in the whole machine device, and the device installed with the chip or processing system or functional module can realize the method and function of the embodiments of the application under the control of the chip or processing system or functional module. For example, the 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. For another example, the non-AP STA can be a mobile phone supporting Wi-Fi communication function, a tablet computer supporting Wi-Fi communication function, a set-top box supporting Wi-Fi communication function, a smart television supporting Wi-Fi communication function, a smart wearable device supporting Wi-Fi communication function, a vehicle-mounted communication device supporting Wi-Fi communication function and a computer supporting Wi-Fi communication function, etc.

[0110] The communication system provided by the embodiments of the present application includes an access point and a station. For example, the embodiments of the present application can be applied to the communication or sensing between an AP and a non-AP STA, between an AP and an AP, or between a non-AP STA and a non-AP STA in a WLAN, and the embodiments of the present application are not limited in this regard. Optionally, the AP can communicate or sense with a single non-AP STA, or the AP can simultaneously communicate or sense with multiple non-AP STAs. Specifically, the communication or sensing between the AP and the multiple non-AP STAs can include downlink transmission in which the AP simultaneously sends signals to the multiple non-AP STAs, and uplink transmission in which the multiple non-AP STAs send signals to the AP. The communication between the AP and the non-AP STA, between the AP and the AP, or between the non-AP STA and the non-AP STA can support a WLAN communication protocol, which can include a protocol in the IEEE 802.11 series, such as an 802.11bn protocol, and of course, the embodiments of the present application are also applicable to protocols after the 802.11bn protocol.

[0111] FIG. 1 is a schematic diagram of an architecture of a communication system provided by the embodiments of the present application. The communication system can include one or more APs and one or more non-AP STAs. As shown in FIG. 1, two access points, such as AP1 and AP2, and three non-AP STAs, such as non-AP STA1, non-AP STA2, and non-AP STA3, are shown. As an example, the method provided by the embodiments of the present application can be applied to data communication or sensing or energy transmission between an AP and one or more non-AP STAs, such as the communication or sensing between AP1 and non-AP STA1 shown in FIG. 1, or the communication or sensing between AP1 and non-AP STA2 shown in FIG. 1. As another example, the method provided by the embodiments of the present application can be applied to communication between an AP and an AP, such as the communication or sensing between AP1 and AP2 shown in FIG. 1. As yet another example, the method provided by the embodiments of the present application can be applied to communication or sensing between a non-AP STA and a non-AP STA, such as the communication or sensing between non-AP STA2 and non-AP STA3 shown in FIG. 1.

[0112] In FIG. 1, a non-AP STA is taken as a mobile phone and an AP is taken as a router as an example, which does not limit the types of the AP and the non-AP STA in the embodiments of the present application. Meanwhile, the number of APs and the number of non-AP STAs shown in FIG. 1 are only examples, and the number of APs or non-AP STAs can be more or less in a specific implementation, which is not limited in the embodiments of the present application.

[0113] The following introduces the terms related to the embodiments of the present application.

[0114] 1. A low density parity check (LDPC) code

[0115] An LDPC code is a type of linear block code with a sparse parity check matrix, and has the characteristics of flexible structure and low decoding complexity. The LDPC code can be used as an error correction code for the communication system described above, thereby improving the reliability of channel transmission and power utilization. The LDPC code has the advantages of good error performance without deep interleaving, better frame error rate performance, greatly reduced error floor, decoding not based on a trellis, support for parallel decoding, small decoding delay, and the like.

[0116] The LDPC code includes a plurality of different code lengths, such as 648 bits, 1296 bits, and 1944 bits.

[0117] In an embodiment of the present application, the LDPC code can also support a code length longer than 1944 bits. For example, the code length of the LDPC code can be twice 1944 bits (i.e., 3888 bits), which is also referred to as a 2x1944 code length, or a 2x code length, or a 2x LDPC code length, or a 2x LDPC code length, or a 2x LDPC, and the like. For another example, the code length of the LDPC code can be three times 1944 bits (i.e., 5832 bits), which is also referred to as a 3x1944 code length, or a 3x code length, or a 3x LDPC code length, or a 3x LDPC code length, or a 3x LDPC, and the like. For yet another example, the code length of the LDPC code can be four times 1944 bits (i.e., 7776 bits), which is also referred to as a 4x1944 code length, or a 4x code length, or a 4x LDPC code length, or a 4x LDPC code length, or a 4x LDPC, and the like. Specific values of longer code lengths are not listed here. The representation of longer code lengths is not limited in the embodiments of the present application.

[0118] 2. A first code length parameter table

[0119] The station can determine the LDPC code length to be used based on the first code length parameter table, which includes a correspondence between the number of code words and the LDPC code length for the current data transmission.

[0120] As an example, the first code length parameter table does not include an LDPC code length greater than 1944, or in other words, the first code length parameter table includes an LDPC code length not 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, the station supports the above three code lengths by default, or in other words, the station must support the above three code lengths.

[0121] Exemplarily, the total number of code word bits of the current data transmission is determined by the number of OFDM symbols required by the current data transmission and the number of code word bits carried by each OFDM symbol.

[0122] For example, the total number of code word bits of the current data transmission can satisfy: avbits N CBPS ·N SYM

[0123] wherein N CBPS represents the number of code word bits carried by each OFDM symbol. N SYM represents the number of OFDM symbols required by the data transmission. N SYM may 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 may satisfy:

[0125] wherein length represents the length of the data packet, in bytes (Byte). m STBC represents the space-time coding mode of the data packet (the value is 1 when space-time coding is not used, otherwise 2). N DBPS represents the number of data bits carried by each OFDM symbol. represents rounding up.

[0126] Exemplarily, the first code length parameter table can be as shown in Table 1.

[0127] Table 1

[0128] In Table 1, R represents the code rate, N pld represents the data bit length after the current data transmission plus 16-bit cyclic redundancy code (CRC), and the N pld may satisfy: N pld = length × 8 + 16

[0129] As shown in Table 1, when 648 < N avbits ≤ 1296, if N avbits ≥ N pld + 1464 · (1-R), the LDPC code length used by the station is 1966, and the number of LDPC code words is 1. Otherwise, the LDPC code length used by the station is 1296, that is, if N avbits < N pld + 1464 · (1-R), the LDPC code length used by the station is 1296, and the number of LDPC code words is 1. As for Navbits The selection of the LDPC code length in other value ranges can be as shown in Table 1, which is not repeated here.

[0130] As another example, the first code length parameter table includes an LDPC code length no greater than 3888. As the first code length parameter table includes one or more of the following LDPC code lengths: 648, 1296, 1944, or 3888. That is, the station supports the above four code lengths by default, or the station must support the above four code lengths. The specific manner in which the station determines the LDPC code length according to the code length parameter table is described with reference to Table 1, which is not repeated here. For the first code length parameter table including 3888, it is not repeated here.

[0131] 3、Second code length parameter table

[0132] The second code length parameter table includes an LDPC code length greater than 1944. As the LDPC code length greater than 1944 can include but is 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, 1944. The code length involved in the second code length parameter table is not limited by the embodiments of the present application.

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

[0134] Example 1:

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

[0136] Table 2

[0137] In Table 2, in order to ensure that the calculation result in the judgment condition is an integer, x1 and x2 must be divisible by 12. At the same time, in order to achieve balance before the code length and the number of puncturing bits, when the proportion of the punctured parity bits to all parity bits is about 0.25, the values of x1 and x2 can be: x1 = 2916 = 12 * 243, x2 = 5832 = 12 * 486. At the same time, in order to facilitate further reduction of the proportion of puncturing bits, x1 and x2 can also take the following values: x1 = 2916 + 12t, x2 = 5832 + 12w, where t, w = 0, 1, 2, etc. If the proportion of puncturing bits needs to be slightly increased, the values of t and 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.

[0138] As shown in Table 2, when 3888 < N avbits≤5832, if N avbits ≥N pld +x2×(1-R), the LDPC code length is selected as 3888, and the number of LDPC codewords is 2. If N avbits <N pld +x2×(1-R), the LDPC code length is selected as 1944, and the number of LDPC codewords is 3. It can be understood that the selection of the LDPC code length under other value ranges of N avbits may be shown in Table 2, which will not be described one by one here.

[0139] Example Two:

[0140] The second code length parameter table may be shown in Table 3.

[0141] Table 3

[0142] In Table 3, R represents the code rate, which can be 1 / 2 or 3 / 4 or 2 / 3 or 5 / 6, or the value of the code rate can be predefined by a standard protocol. It can be understood that each row in Table 3 can be independent.

[0143] In Table 3, in order to ensure that the calculation result in the judgment condition is an integer, x1 must be divisible by 12. At the same time, in order to achieve balance before the code length and the number of puncturing bits, when the proportion of punctured parity bits to all parity bits is about 0.25, the value of x1 can be: x1 = 2916 = 12 x 243. At the same time, in order to facilitate further reduction of the proportion of puncturing bits, x1 can also take the following values: x1 = 2916 + 12t, where t = 0, 1, 2, etc. If the proportion of puncturing bits needs to be slightly increased, the value of t can be t = -1, -2, etc.

[0144] As shown in Table 3, when 1944 < N avbits , the LDPC code length is selected as 3888, and the number of LDPC codewords is It can be understood that the selection of the LDPC code length under other value ranges of N avbits may be shown in Table 3, which will not be described one by one here.

[0145] Example Three:

[0146] The second code length parameter table may be shown in Table 4.

[0147] Table 4

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

[0149] Example Four:

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

[0151] Table 5

[0152] In Table 5, in order to ensure that the calculation result in the judgment condition is an integer, x1, x2, x3, and x4 all need to be divisible by the least common multiple of all code rate denominators. At the same time, in order to achieve balance before the code length and the number of puncturing bits, the values of x3 and x4 should be as close as possible to the values of the standard of WLAN, that is, x3≈912, x4≈1464. For x1 and x2, as described in Example One, the proportion of punctured check bits to all check bits should be about 0.25.

[0153] As an example, the value range of code rate R includes 7 / 8, such as R value range includes at least one of 1 / 2, 3 / 4, 2 / 3, 5 / 6 or 7 / 8, x1, x2, x3, x4 all need to be divisible by the least common multiple of all code rate denominators in the value range of R, and the least common multiple is 24. Therefore, at this time x3=912=38×24, x4=1464=61×24. And x1=2928=122×24, x2=5832=243×24. At the same time, in order to further reduce the proportion of puncturing bits, x1, x2, x3, x4 can also take the following values: x1=2928+24t1, x2=5832+24t2, where t1, t2=0, 1, 2, etc. If the proportion of puncturing bits needs to be slightly increased, the values of t1, t2 can be t1, t2=-1, -2, etc. It can be understood that the values of t1 and t2 can be the same or different.

[0154] As another example, the value range of the code rate R includes 8 / 9, such as the value range of the code rate R includes at least one of 1 / 2, 3 / 4, 2 / 3, 5 / 6 or 8 / 9, and x1, x2, x3, x4 all need to be divided by the least common multiple of all the denominators of the code rate in the value range of R, and the least common multiple is 36. Therefore, at this time, x3 = 936 = 26*36, x4 = 1476 = 41*36. And x1 = 2916 = 81*36, x2 = 5832 = 162*36. At the same time, in order to further reduce the proportion of puncturing bits, x1, x2, x3, x4 can also take the following values: x1 = 2916 + 36t1, x2 = 5832 + 36t2, x3 = 936 + 36t3, x4 = 1476 + 36t4, wherein t1, t2, t3, t4 = 0, 1, 2, etc. If it is necessary to increase the proportion of puncturing bits, 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.

[0155] As another example, the value range of the code rate R includes 7 / 8 and 8 / 9, such as the value range of the code rate R includes at least one of 1 / 2, 3 / 4, 2 / 3, 5 / 6, 7 / 8 and 8 / 9, and x1, x2, x3, x4 all need to be divided by the least common multiple of all the denominators of the code rate in the value range of R, and the least common multiple is 72. Therefore, at this time, x3 = 936 = 13*72, x4 = 1512 = 21*72. And x1 = 2952 = 41*72, x2 = 5832 = 81*72. At the same time, in order to further reduce the proportion of puncturing bits, x1, x2, x3, x4 can also take the following values: x1 = 2952 + 72t1, x2 = 5832 + 72t2, x3 = 936 + 72t3, x4 = 1512 + 72t4, wherein t1, t2, t3, t4 are positive integers, such as t1, t2, t3, t4 = 0, 1, 2, etc. If it is necessary to increase the proportion of puncturing bits, t1, t2, t3, t4 can be negative integers, such as 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.

[0156] Example five:

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

[0158] Table 6

[0159] In Table 6, in order to ensure that the calculation result in the judgment condition is an integer, x1, x3, x4 all need to be divisible by the least common multiple of all the denominators of the code rate. At the same time, in order to achieve balance before the code length and the number of puncturing bits, the values of x3 and x4 should be as close as possible to the values of the standard of WLAN, that is, x3≈912, x4≈1464. For x1, as described in Example One or Example Two, the ratio of the number of punctured check bits to the total number of check bits should be about 0.25.

[0160] As an example, the value range of the code rate R includes 7 / 8, such as R includes at least one of 1 / 2, 3 / 4, 2 / 3, 5 / 6 or 7 / 8, x1, x3, x4 all need to be divisible by the least common multiple of all the denominators of the code rate in the value range of R, and the least common multiple is 24. Therefore, at this time x3=912=38×24, x4=1464=61×24. x1=2928=122×24. At the same time, in order to further reduce the ratio of puncturing bits, x1, x3, 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 ratio of puncturing bits, t1 can be a negative integer, such as t1 can take values t1=-1, -2, etc.

[0161] As another example, the value range of the code rate R includes 8 / 9, such as R includes at least one of 1 / 2, 3 / 4, 2 / 3, 5 / 6 or 8 / 9, x1, x3, x4 all need to be divisible by the least common multiple of all the denominators of the code rate in the value range of R, and the least common multiple is 36. Therefore, at this time x3=936=26×36, x4=1476=41×36. x1=2916=81×36. At the same time, in order to further reduce the ratio of puncturing bits, x1, x3, x4 can also take the following values: x1=2916+36t1, x3=936+36t3, x4=1476+36t4, where t1, t3, t4 are natural numbers, such as t1, t3, t4=0, 1, 2, etc. If it is necessary to increase the ratio of puncturing bits, t1, t3, t4 can be negative integers, such as t1, t3, t4 can take values t1, t3, t4=-1, -2, etc. It can be understood that the values of t1, t3, t4 can be the same or different.

[0162] As another example, the value range of the code rate R includes 7 / 8 and 8 / 9, such as the value range of the code rate R includes at least one of 1 / 2, 3 / 4, 2 / 3, 5 / 6 or 8 / 9, and the least common multiple of all denominators of the code rates in the value range of the code rate R needs to be evenly divided by x1, x3, x4, and the least common multiple is 72. Therefore, at this time x3 = 936 = 13 * 72, x4 = 1512 = 21 * 72. And x1 = 2952 = 41 * 72. At the same time, in order to facilitate further reducing the proportion of puncturing bits, x1, x3, x4 can also take the following values: x1 = 2952 + 72t1, x3 = 936 + 72t3, x4 = 1512 + 72t4, where t1, t3, t4 are natural numbers, such as t1, t3, t4 = 0, 1, 2, etc. If it is necessary to increase the proportion of puncturing bits, t1, t3, t4 can be negative integers, such as t1, t3, t4 = -1, -2, etc. It can be understood that the values of t1, t3, t4 can be the same or different.

[0163] Example six:

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

[0165] Table 7

[0166] In Table 7, the values of x1, x3, x4 can refer to the related description in Example five, which will not be repeated here.

[0167] Example seven:

[0168] The second code length parameter table includes a 1944 * 2 = 3888 bit LDPC code length and a 3888 * 2 = 7776 bit LDPC code length. The second code length parameter table can be as shown in Table 8. It can be understood that each row in Table 8 can be independent.

[0169] Table 8

[0170] In Table 8, in order to ensure that the calculation result in the judgment condition is an integer, x1 and x1 both need to be divisible by 12. At the same time, in order to achieve balance before the code length and the number of puncturing bits, when the proportion of punctured check bits in all check bits is about 0.25, the values of x1, x2 and x5 can be: x1 = 2916 = 12 * 243, x2 = 5832 = 12 * 486, x5 = 12 * 972. At the same time, in order to facilitate further reduction of the proportion of puncturing bits, x1 and x2 can also take the following values: x1 = 2916 + 12t1, x2 = 5832 + 12t2, x5 = 11664 + 12t3, where t1, t2, t3 are natural numbers, such as t1, t2, t3 = 0, 1, 2, etc. If the proportion of puncturing bits needs to be increased, t1, t2, t3 can be negative integers, such as t1, t2, t3 = -1, -2, etc. It can be understood that the values of t1, t2, t3 can be the same or different.

[0171] As shown in Table 8, when 7776 < N avbits ≤ 11664, if N avbits ≥ N pld + x5 * (1-R), the station selects the LDPC code with a code length of 7776, and the number of LDPC codewords is 2 at this time. If N avbits < N pld + x5 * (1-R), the station selects the LDPC code with a code length of 3888, and the number of LDPC codewords is 3 at this time.

[0172] The first code length parameter table and the second code length parameter table shown above are only examples, and the specific relationship in the parameter table is not limited by the embodiments of the application. In the application, the code length parameter table can also have other names (such as code length selection table), for example, the first code length parameter table can also be called the first code length selection table, and the second code length parameter table can also be called the second code length selection table.

[0173] The WLAN LDPC code needs to comprehensively consider the performance of long code and the number of punctured bits when selecting the code length. Generally, the longer the LDPC code length is, the better the error control performance is, and thus the long code should be selected as much as possible in the selection of the code length. Meanwhile, for different code lengths, the WLAN LDPC code needs to be punctured after encoding, that is, the last several check bits are not transmitted. The puncturing causes the actual code rate to increase, thereby causing a certain performance loss. Therefore, when the WLAN LDPC code is encoded, the selection of the specific code length needs to balance between the tendency of long code and the actual number of punctured bits. As can be seen from the code length parameter tables shown in the foregoing, the selection of the code length of the WLAN LDPC code is not monotonously increased with the increase of the information bit length, but can be constantly reduced to a shorter code length with the increase of the information bit length. In the shortest length, the WLAN LDPC code directly selects the middle code length (such as 1296 bits) rather than the shortest code length (such as 648 bits), because the information bit needs to fill at least a single OFDM symbol. The encoding process also involves a repetition operation, which is not described here.

[0174] With the progress of the protocol, the LDPC code can introduce a code length longer than 1944 bits, such as 2xLDPC, 3xLDPC or 4xLDPC, etc. The longer code length can have more bits participating in encoding, which can randomize the noise, and the check matrix of the long code has more check equations, and more check equations provide more check relations, which can provide stronger error correction capability. Therefore, the embodiments of the present application provide a communication method and device. Optionally, the transceiving parties can interact whether to support a longer LDPC code length. Optionally, the first station can select a longer LDPC code length and notify the second station whether to adopt the longer LDPC code length. Optionally, the first station and the second station can determine a suitable LDPC code length according to the code length parameter table.

[0175] In the embodiments of the present application, the longer LDPC code length can include one or more of the following: 2xLDPC, 3xLDPC or 4xLDPC.

[0176] Please refer to FIG. 2A, which is a flowchart of a communication method provided by the embodiments of the present application. In the method, the transceiving parties can interact the LDPC code lengths supported by each other. The communication method can be applied to a first station and a second station, the first station can be the AP or non-AP STA described in the foregoing, and the second station can be the AP or non-AP STA described in the foregoing. For other descriptions of the first station and the second station, please refer to FIG. 1, etc., which will not be described here in detail. As shown in FIG. 2A, the method includes but is not limited to the following steps.

[0177] 201. The first station sends first capability information, and correspondingly, the second station receives the first capability information.

[0178] The first capability information is used to indicate whether the first station supports a second LDPC code length, which is greater than 1944. That is, the first capability information is used to indicate whether the first station supports an LDPC code length greater than 1944. Alternatively, the first capability information is used to indicate whether the first station supports a longer LDPC code length. The first capability information can be referred to as a longer code length capability information. Alternatively, the second capability information shown below and the first capability information can both be referred to as a longer code length capability information.

[0179] The second LDPC code length includes one or more of 2xLDPC, 3xLDPC or 4xLDPC. Alternatively, the second LDPC code length can also be a code length longer than 4xLDPC. Here, it is not listed one by one.

[0180] Regarding the first capability information, the embodiments of the present application provide the following examples:

[0181] Example 1:

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

[0183] As an example, the second LDPC code length is one of 2xLDPC, 3xLDPC or 4xLDPC, and the first capability information indicates whether the first station supports one of 2xLDPC, 3xLDPC or 4xLDPC. For example, the first capability information indicates whether the first station supports 2xLDPC by 1 bit. The bit is 1, which means that the first station supports 2xLDPC, and the bit is 0, which means that the first station does not support 2xLDPC. Alternatively, the bit is 0, which means that the first station supports 2xLDPC, and the bit is 1, which means that the first station does not support 2xLDPC. As another example, the first capability information indicates whether the first station supports 3xLDPC by 1 bit. The bit is 1, which means that the first station supports 3xLDPC, and the bit is 0, which means that the first station does not support 3xLDPC. Alternatively, the bit is 0, which means that the first station supports 3xLDPC, and the bit is 1, which means that the first station does not support 3xLDPC. As another example, the first capability information indicates whether the first station supports 4xLDPC by 1 bit. The bit is 1, which means that the first station supports 4xLDPC, and the bit is 0, which means that the first station does not support 4xLDPC. Alternatively, the bit is 0, which means that the first station supports 4xLDPC, and the bit is 1, which means that the first station does not support 4xLDPC.

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

[0185] As another example, the first capability information indicates that the first station supports a plurality of LDPC code lengths greater than 1944 (e.g., 4x LDPC, 3x LDPC, and 2x LDPC). For example, the first capability information occupies 1 bit, and the relationship between the value of the 1 bit and the meaning is as follows: 0 indicates that the first station does not support the LDPC code length longer than 1944, i.e., the first station does not support 4x LDPC, 3x LDPC, and 2x LDPC; 1 indicates that the first station supports 4x LDPC, 3x LDPC, and 2x LDPC. It can be understood that the relationship between the value of the 1 bit and the meaning is only an example, and should not be understood as a limitation on the present application.

[0186] Example 2: The first capability information respectively indicates a plurality of LDPC code lengths greater than 1944, e.g., the first capability information respectively indicates whether the first station supports 2x LDPC, 3x LDPC, and 4x LDPC. For example, the first capability information respectively indicates whether the first station supports 2x LDPC, 3x LDPC, and 4x LDPC by 3 bits. The first bit in the 3 bits is used to indicate whether the first station supports 2x LDPC, the second bit in the 3 bits is used to indicate whether the first station supports 3x LDPC, and the third bit in the 3 bits is used to indicate whether the first station supports 4x LDPC.

[0187] Example 3: The first capability information indicates that the first station supports the LDPC code length shorter than the second LDPC code length by indicating that the first station supports the second LDPC code length. For example, the first capability information indicates that the first station does not support the second LDPC code length, which indicates that the first station does not support the LDPC code length longer than 1944, i.e., the first station does not support 4x LDPC, 3x LDPC, and 2x LDPC. As another example, the second LDPC code length is 2x LDPC, the first capability information indicates that the first station supports the 2x LDPC code length and supports the LDPC code length smaller than 2x LDPC, and the first station does not support 4x LDPC and 3x LDPC. As another example, the second LDPC code length is 3x LDPC, the first capability information indicates that the first station supports 3x LDPC and 2x LDPC, and the first station does not support 4x LDPC. As another example, the second LDPC code length is 4x LDPC, the first capability information indicates that the first station supports 4x LDPC, 3x LDPC, and 2x LDPC.

[0188] That is, in this example, if the first station supports a longer LDPC code length, it also supports a relatively shorter LDPC code length. For example, the first capability information occupies 2 bits, and the relationship between the values and meanings of the 2 bits is as follows: 0 indicates that the first station does not support an LDPC code length greater than 1944; 1 indicates that the first station supports 2x LDPC, but does not support 3x LDPC and 4x LDPC; 2 indicates that the first station supports 2x LDPC and 3x LDPC, but does not support 4x LDPC; and 3 indicates that the first station supports 2x LDPC, 3x LDPC, and 4x LDPC. It can be understood that the relationship between the values and meanings of the 2 bits is only an example, and should not be construed as a limitation on the present application.

[0189] For example, the first capability information can be included in a UHR capability information element. The UHR capability information element can be as shown in FIG. 3, and the capability information element includes at least one field: element ID (occupying 1 byte), length (occupying 1 byte), element ID extension (occupying 1 byte), UHR MAC capability information, and UHR PHY capability information. The UHR MAC capability information field and the UHR PHY capability information field occupy a variable number of bytes (or are pending or variable). Alternatively, the first capability information can be carried in the UHR PHY capability information field.

[0190] Examples 1 to 3 of the first capability information are also shown in FIG. 3. As shown in FIG. 3, for example 1, the first capability information is carried in a 1-bit support longer code length field, and the description of the support longer code length field can refer to example 1 above. For example 2, the first capability information can be carried in a 1-bit support 2x LDPC code length field, a 1-bit support 3x LDPC code length field, and a 1-bit support 4x LDPC code length field. The description of the three fields can refer to example 2 above. For example 3, the first capability information is carried in a 2-bit support longer code length field, and the description of the field can refer to example 3 above. Details are not repeated here.

[0191] Optionally, the first capability information can be carried in a UHR capability information element in a management frame. For example, the first station is an AP, and the management frame can be one or more of a beacon frame, a probe response frame, an association response frame, a re-association response frame, etc. For another example, the first station is a STA, and the management frame can be one or more of a probe request frame, an association request frame, a re-association request frame, etc.

[0192] In the embodiments of the present application, the content indicated by the first capability information is applicable to the transmission capability of the first station and / or the reception capability of the first station. For example, the content indicated by the first capability information supports both the transmission capability and the reception capability of the first station. For another example, the first capability information includes a first capability information 1 and / or a first capability information 2, the first capability information 1 is used to indicate whether the transmission capability of the first station supports the second LDPC code length, and the first capability information 2 is used to indicate whether the reception capability of the first station supports the second LDPC code length. The second LDPC code length supported by the transmission capability can be the same as or different from the second LDPC code length supported by the reception capability. The respective indication of the transmission capability and the reception capability is described above in the examples 1-4, and thus will not be described here in detail.

[0193] 202. The second station transmits second capability information, and correspondingly, the first station receives the second capability information.

[0194] The second capability information is used to indicate whether the second station supports the second LDPC code length. The description of the second LDPC code length is described above in the step 201, and thus will not be described here in detail. The specific implementation of the second capability information indicating whether the second station supports the second LDPC code length can refer to the specific implementation of the first capability information indicating whether the first station supports the second LDPC code length, which will not be described here in detail.

[0195] For example, the second station is an AP, and the management frame can be one or more of a beacon frame, a probe response frame, an association response frame, a re-association response frame, etc. For another example, the second station is a STA, and the management frame can be one or more of a probe request frame, an association request frame, a re-association request frame, etc.

[0196] In the embodiments of the present application, the content indicated by the second capability information is applicable to the transmission capability of the second station and / or the reception capability of the second station. The content indicated by the second capability information supports both the transmission capability and the reception capability of the second station. For another example, the second capability information includes the second capability information 1 and / or the second capability information 2, the second capability information 1 is used to indicate whether the transmission capability of the second station supports the second LDPC code length, and the second capability information 2 is used to indicate whether the reception capability of the second station supports the second LDPC code length. The second LDPC code length supported by the transmission capability can be the same as or different from the second LDPC code length supported by the reception capability.

[0197] It can be understood that the present application does not limit the order of the above-mentioned steps 201 and 202.

[0198] In the embodiments of the present application, whether the second LDPC code length is supported by the interaction between the stations can enable the transceiving parties to clearly know whether the opposite end supports the second LDPC code length, thereby ensuring that the transceiving parties can use the unified LDPC code length as much as possible.

[0199] FIG. 2B is a flow diagram of another communication method provided by the embodiments of the present application. In the method, the transceiving parties can determine the LDPC code length to be used according to the transmission mode, to ensure that the transceiving parties use the unified LDPC code length.

[0200] The method shown in FIG. 2B and the method shown in FIG. 2A can be separate embodiments, or FIG. 2B can be combined with FIG. 2A, such as FIG. 2C. In FIG. 2C, the first station and the second station interact to support the second LDPC code length (refer to FIG. 2A), and in the case of transmitting a 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 the operation information. For the specific mode of FIG. 2C, the related examples in FIG. 2B can also be referred to.

[0201] As shown in FIG. 2B, the method includes but is not limited to the following steps.

[0202] 211, the first station determines the first LDPC code length according to the transmission mode.

[0203] The first LDPC code length is the LDPC code length used by the PPDU transmitted by the first station. The transmission mode includes unicast transmission or groupcast transmission. The groupcast transmission includes at least one of multicast transmission or broadcast transmission.

[0204] Exemplarily, in the case that the transmission mode is unicast transmission, the first station can determine the first LDPC code length according to the second capability information. For example, the first station can determine the first LDPC code length according to the LDPC code length supported by the first station itself and the second capability information. For another example, the first station can determine the first LDPC code length according to the first capability information and the second capability information. The specific description of the first capability information and the second capability information can refer to the related description above.

[0205] In a possible implementation, in the case that the transmission mode is unicast transmission and the first station and the second station both support the second LDPC code length, the first station determines the first LDPC code length according to the second code length parameter table, and the second code length parameter table includes the second LDPC code length. Alternatively, in the case that the transmission mode is unicast transmission and the first station and the second station both support the second LDPC code length, the first LDPC code length is the second LDPC code length. In the case that the first station determines the first LDPC code length according to the second code length parameter table, the first LDPC code length can be the same as the second LDPC code length, or can be different from the second LDPC code length. That is, even if the first station adopts a code length parameter table including a longer LDPC code length, the first station does not necessarily adopt the longer LDPC code length, and the first LDPC code length determined by the first station depends on the total number of code bits of the current data transmission and the data bit length of the current data transmission.

[0206] Unicast transmission is one-to-one transmission, that is, there is one receiving end (that is, the second station). For unicast transmission, after the first station and the second station are associated or paired, the capability information of each other can be known, that is, whether the opposite end supports the second LDPC code length is known. If the first station and the second station both support the second LDPC code length, the first station can determine the first LDPC code length according to the second code length parameter table, so that the first station and the second station can adopt a longer LDPC code length. It can be understood that the second code length parameter table can be any one of Tables 2 to 8, which will not be described here.

[0207] In another possible implementation, in the case that the transmission mode is unicast transmission and 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.

[0208] When any one of the first station and 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, so as to avoid adopting an LDPC code length that is not supported by the first station or the second station.

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

[0210] When the second LDPC code length is A, the first station and the second station support the second LDPC code length. The first station and the second station determine the first LDPC code length according to the code length parameter table including A.

[0211] When the second LDPC code length is C, the first station and the second station support the second LDPC code length. The first station and the second station determine the first LDPC code length according to the code length parameter table including C.

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

[0213] When the second LDPC code length is B, the first station supports the second LDPC code length; and 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 according to the code length parameter table not including B.

[0214] When the second LDPC code length is D, the first station does not support the second LDPC code length; and 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 according to the code length parameter table not including D.

[0215] For example, the first station supports longer LDPC code lengths A, B, and C; and the second station supports longer LDPC code lengths A, C, and D. The first station and the second station can select code length A or C for communication, and the second code length selection table includes code length A and / or C.

[0216] For example, the first station supports longer LDPC code lengths A, B, and C; and the second station supports longer LDPC code lengths A, C, and D. The first station and the second station can select code length A or C for communication, and the second code length selection table includes code length A and / or C.

[0217] For example, the first station supports longer LDPC code lengths A, B, and C; and the second station supports longer LDPC code lengths A, C, and D. The first station and the second station can select code length A or C for communication, and the second code length selection table includes code length A and / or C.

[0218] When the second LDPC code length is 2×LDPC, the first station and the second station both support 2×LDPC. The first LDPC code length can be 2×LDPC, or the first LDPC code length is determined according to the code length parameter table including 2×LDPC.

[0219] When the second LDPC code length is 3×LDPC, the first station and the second station do not support 3×LDPC. The first LDPC code length can include 2×LDPC, or a code length shorter than 2×LDPC. That is, the first LDPC code length can be determined according to the first code length parameter table, or be determined according to the code length parameter table including 2×LDPC.

[0220] Taking the case that the LDPC code length supported by the second station is 4×LDPC, and the LDPC code length supported by the first station is 3×LDPC as an example:

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

[0222] As another example, taking the case that the first station supports 3×LDPC, and supports a code length shorter than 3×LDPC, and the case that the second station supports 4×LDPC, and 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.

[0223] As yet another example, taking the case that the first station supports 3×LDPC, and does not support 2×LDPC, and the case that the second station supports 4×LDPC, and does not support 3×LDPC and 2×LDPC, the first LDPC code length can be determined according to the first code length parameter table.

[0224] In the case of multicast transmission (broadcast and / or multicast transmission), there are multiple receiving ends (such as multiple second stations), and for the multiple receiving ends, even if there is only one receiving end that does not support a longer LDPC code length, the sending end cannot use a longer LDPC code length. However, the multiple receiving ends are not clear about the capability information of each other, that is, the multiple receiving ends are not clear about the LDPC code lengths supported by each other (such as whether a longer LDPC code length is supported is not clear). Therefore, in the case of multicast transmission, the implementation manner in which the first station determines the first LDPC code length can include:

[0225] Implementation manner one:

[0226] 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, and the first code length parameter table does not include an LDPC code length greater than 1944, or in other words, includes an LDPC code length not greater than 1944.

[0227] The first station and the second station must support 648, 1296, 1944, and the longer LDPC code length includes but is not limited to 2xLDPC, 3xLDPC or 4xLDPC.

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

[0229] As another example, when the first station and the second station support LDPC code length including 2xLDPC in the case of groupcast transmission, the first station determines the first LDPC code length according to the first code length parameter table including 2xLDPC.

[0230] For example, the first code length parameter table includes one or more of 2xLDPC, 1944, 1296 or 648. The first station and the second station support 648, 1296, 1944 and 2xLDPC by default. The longer LDPC code length is a code length longer than 2xLDPC, such as 3xLDPC or 4xLDPC.

[0231] In this implementation, the first station can determine the first LDPC code length according to the LDPC code length supported by the first station and the second station by default and the code length parameter table.

[0232] Through the first implementation, in the case of groupcast transmission, the longer LDPC code length is prohibited, or the first LDPC code length is determined according to the code length parameter table including the longer LDPC code length, so that not only the consistent LDPC code length can be ensured for the transmitting and receiving parties, but also the implementation is simple and the complexity is low.

[0233] Optionally, when the transmitting capability and the receiving capability of the station can be inconsistent, the first station can determine the first LDPC code length according to the second capability information and the LDPC code length supported by the first station, and the second station can determine the first LDPC code length according to the first capability information and the LDPC code length supported by the second station.

[0234] Implementation two:

[0235] In case that the transmission mode is a groupcast transmission (e.g., a broadcast transmission and / or a multicast transmission), the first station determines the first LDPC code length according to whether each of the second stations supports the second LDPC code length. That is, the first station can determine the first LDPC code length according to the second capability information of the second stations. The manner in which the first station obtains whether the second stations support the second LDPC code length can refer to the above description of FIG. 2A, and will not be repeated here.

[0236] That is, the first station determines the first LDPC code length according to whether each of the second stations supports the second LDPC code length. For example, if each of the second stations supports the second LDPC code length, 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. For another example, if at least one of the second stations does not support the second LDPC code length, the first station can determine the first LDPC code length according to the first code length parameter table.

[0237] As an example, the first station can determine the first LDPC code length based on its own capability (i.e., the LDPC code length that it supports) and the capability information of the second stations. As another example, the first station can determine the first LDPC code length based on the first capability information and the capability information of the second stations.

[0238] As an example, the second stations mentioned above are all the associated second stations of the first station. If all the associated second stations of the first station support the second LDPC code length, the first station determines the LDPC code length to be used in the broadcast and / or multicast transmission based on the second code length parameter table. If any of the associated second stations of the first station does not support the second LDPC code length, the first station determines the LDPC code length to be used in the broadcast transmission according to the first code length parameter table.

[0239] As another example, the second stations mentioned above are the associated second stations of a multicast group corresponding to the first station.

[0240] As yet another example, the second stations mentioned above are the associated second stations of multiple multicast groups corresponding to the first station. In this example, the first LDPC code lengths corresponding to the multiple multicast groups can be the same or different.

[0241] If the second stations in a multicast group all support the second LDPC code length, the first station determines the LDPC code length to be used in the multicast transmission to the second stations in the multicast group based on the second code length parameter table. If there is a second station in the multicast group that does not support the second LDPC code length, the first station determines the LDPC code length to be used in the multicast transmission to the second stations in the multicast group according to the first code length parameter table.

[0242] The second implementation manner is exemplified by taking the first station determining the first LDPC code length according to the second capability information of the second stations as an example. In a specific implementation, in the case of the transmission manner being groupcast transmission, the first station can be free to select, that is, the first station can determine the first LDPC code length without combining the second capability information of each second station, but determine not to use a longer LDPC code length. Thus, the implementation can be simplified.

[0243] In a possible implementation, in the case of the transmission manner being groupcast transmission, the first station can further send operation information, and the second station can receive the operation information. The operation information is used to indicate whether the LDPC code length used by the first station is the second LDPC code length, or the operation information is used to indicate whether the first station uses the second code length parameter table, and the second code length parameter table includes the second LDPC code length.

[0244] The second station can determine the first LDPC code length based on the operation information. That is, the first station can enable the second station to clearly know the LDPC code length used by the first station by sending the operation information, so as to ensure that the first station and the second station keep the unity of the LDPC code length used by each station.

[0245] Optionally, the first station can send the operation information based on at least one of the first capability information and the second capability information. For example, the first station determines the LDPC code length used by the first station based on the first capability information and the second capability information, and indicates whether the LDPC code length used by the first station is the second LDPC code length or indicates whether the first station uses the second code length parameter table through the operation information.

[0246] Optionally, the first station can correspond to at least two groupcasts, and the operation information indicates whether the LDPC code length used by a first groupcast in the at least two groupcasts is the second LDPC code length, or the operation information is used to indicate whether a second groupcast in the at least two groupcasts uses the second code length parameter table. That is, when the first station corresponds to multiple groupcasts, the operation information can indicate whether the multiple groupcasts use the second LDPC code length or use the second code length parameter table respectively. In this way, the above information is indicated in combination with different groupcasts, which can enable the use of a longer LDPC code length in the groupcast as much as possible, so that the LDPC code length determined in each groupcast is more appropriate.

[0247] Regarding the specific implementation of the content indicated by the operation information in the case of groupcast transmission, the embodiments of the present application provide the following several examples:

[0248] Example 1: The operation information indicates whether the second LDPC code length or the second code length parameter table is adopted for a multicast transmission, which includes a broadcast transmission and a multicast transmission. For example, the operation information can indicate whether the second LDPC code length or the second code length parameter table is adopted for the multicast transmission by 1 bit. The value of the 1 bit is 0, which indicates that the second LDPC code length or the second code length parameter table is adopted for the multicast transmission. The value of the 1 bit is 1, which indicates that the second LDPC code length or the second code length parameter table is not adopted for the multicast transmission. Alternatively, the value of the 1 bit is 1, which indicates that the second LDPC code length or the second code length parameter table is adopted for the multicast transmission. The value of the 1 bit is 0, which indicates that the second LDPC code length or the second code length parameter table is not adopted for the multicast transmission.

[0249] In Example 1, the content indicated by the operation information is not specifically distinguished for the multicast transmission or the broadcast transmission.

[0250] Example 2: The operation information indicates whether the second LDPC code length or the second code length parameter table is adopted for a broadcast transmission, and indicates whether the second LDPC code length or the second code length parameter table is adopted for a multicast transmission.

[0251] The operation information can indicate whether the second LDPC code length or the second code length is adopted for the broadcast transmission and the multicast transmission, respectively. For example, the operation information includes 2 bits, in which 1 bit is used to indicate whether the second LDPC code length or the second code length parameter table is adopted for the broadcast transmission, and the other bit is used to indicate whether the second LDPC code length or the second code length parameter table is adopted for the multicast transmission.

[0252] In Example 2, the content indicated by the operation information is specifically distinguished for the multicast transmission or the broadcast transmission.

[0253] Example 3: The operation information indicates whether the second LDPC code length or the second code length parameter table is adopted for a broadcast transmission, and indicates whether the second LDPC code length or the second code length parameter table is adopted for a first multicast group, and indicates whether the second LDPC code length or the second code length parameter table is adopted for a second multicast group.

[0254] In this example, the first station can correspond to at least two multicast groups (including the first multicast group and the second multicast group), and the operation information can indicate whether the second LDPC code length or the second code length parameter table is adopted for the multicast transmission corresponding to the at least two multicast groups, respectively. The first station indicates whether the second LDPC code length is adopted for the corresponding multicast transmission for different multicast groups, respectively. For example, the first station corresponds to M multicast groups, and the operation information can indicate whether the second LDPC code length is adopted for the multicast group 1 to the multicast group M, respectively.

[0255] In example three, the operation information indicates whether the content is for a broadcast transmission, or for the first multicast group, or for the second multicast group.

[0256] Optionally, the operation information further comprises an identification of the broadcast, and / or an identification of the multicast group. The identification of the broadcast can comprise, but is not limited to, at least one of a medium access control (MAC) address or a STA ID or an association identifier (AID) of the broadcast. The identification of the multicast group can comprise, but is not limited to, at least one of a MAC address or a STA ID or an AID of the multicast group.

[0257] As for example two above, the operation information can comprise an identification of the broadcast and / or an identification of the multicast group. The identification of the multicast group can not specifically distinguish different multicast groups. That is, the identification of the multicast group can be used to distinguish the broadcast transmission, without maintaining different multicast groups. As for example three above, the operation information can comprise an identification of the broadcast, an identification of the first multicast group, an identification of the second multicast group, etc.

[0258] To distinguish different multicast groups, the AP can assign different STA IDs or AIDs to different multicast groups. For example, the first multicast group transmission is assigned a STA ID = 20, and the second multicast group transmission is assigned a STA ID = 21. The operation information can indicate that the second LDPC code length is used for the multicast group with STA ID = 20, or indicate that the second code length parameter table is used for the multicast group with STA ID = 20. The operation information indicates that the second LDPC code length is not used for the multicast group with STA ID = 21, or indicates that the second code length parameter table is not used for the multicast group with STA ID = 21. Thus, 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 according to whether the corresponding multicast group indicated by the operation information uses the second LDPC code length (or whether the corresponding multicast group indicated by the operation information uses the second code length parameter table).

[0259] Optionally, the operation information is contained in an operation information element in a management frame or a signal (SIG) field in a physical protocol data unit (PPDU). The signal field includes a general signal field. Alternatively, the signal field includes a signal field corresponding to a standard to which the PPDU belongs, such as a UHR-SIG field when the PPDU is an ultrahigh reliability (UHR) PPDU. Optionally, the operation information described above can be contained in a PPDU shown in step 213 below. The management frame can include one or more of a beacon frame, a probe response frame, an association response frame, and a re-association response frame.

[0260] Exemplarily, the operation information element can be as shown in FIG. 4. The operation information element can include at least one of an element ID (occupying 1 byte), a length (occupying 1 byte), an element ID extension (occupying 1 byte), and UHR operation parameters. The number of bytes occupied by the UHR operation parameter field is pending (or variable). The operation information described above is contained in the UHR operation parameter field.

[0261] Fig. 4 also exemplarily shows the above-mentioned example one to example three. For example one, the UHR operation parameter field includes a multicast longer code length adoption indication field, which is used to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted for multicast transmission. The description of this field can refer to the above-mentioned example one. For example two, the UHR operation parameter field includes 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 is used to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted for broadcast transmission. The multicast longer code length adoption indication field is used to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted for multicast transmission. The description of these two fields can refer to the above-mentioned example two. For example three, the UHR operation parameter field includes a broadcast longer code length adoption indication field, a multicast group 1 longer code length adoption indication field,..., and a multicast group M longer code length adoption indication field. The broadcast longer code length adoption indication field is used to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted for broadcast transmission. The multicast group 1 longer code length adoption indication field is used to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted for multicast group 1. The multicast group M longer code length adoption indication field is used to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted for multicast group M. Exemplarily, the multicast group 1 longer code length adoption indication field includes a multicast identification field and a longer code length adoption indication field. The multicast identification field is used to indicate the multicast identification of the multicast group 1 (such as the MAC address of the multicast group 1). The longer code length adoption indication field is used to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted for the multicast group 1. The description of the above-mentioned fields can refer to the above-mentioned example three. Here, no longer detailed description is given.

[0262] 212. The second station determines the first LDPC code length according to the transmission mode.

[0263] 213. The first station transmits the PPDU, and correspondingly, the second station receives the PPDU. The PPDU adopts the first LDPC code length.

[0264] The first station performs LDPC encoding on the PPDU based on the first LDPC code length. The second station performs decoding on the PPDU based on the first LDPC code length. For example, the PPDU includes a data field, which adopts the first LDPC code length.

[0265] In the embodiments of the present application, the second station can first determine the first LDPC code length according to the transmission mode, and then receive the PPDU. Alternatively, the second station can first receive the PPDU, and then determine the first LDPC code length according to the transmission mode. The embodiments of the present application do not limit this.

[0266] The PPDU can comprise a signaling field. As an example, the transmission mode of the PPDU is indicated by the signaling field in the PPDU. For example, the transmission mode of the PPDU is indicated by a STA ID in the signaling field. For example, in a case where the value of the STA ID is in a range of 1-2006, the transmission mode is unicast transmission. For another example, in a case where the STA ID is a basic service set identifier (BSSID) index of a multi-BSSID, the transmission mode is groupcast transmission. In this example, after receiving the PPDU, the second station can determine the transmission mode of the PPDU based on the signaling field of the PPDU.

[0267] As another example, the second station can know the transmission mode of the PPDU in advance. For example, the second station can determine the transmission mode of the PPDU based on a default transmission mode. For another example, the second station can determine the transmission mode of the PPDU based on a capability interaction or negotiation with the first station. For another example, the second station can determine the transmission mode of the PPDU based on the transmission mode of a previously received PPDU.

[0268] In a possible implementation, in a case where the transmission mode is unicast transmission, the second station can determine the first LDPC code length according to the first capability information. For example, the second station determines the first LDPC code length in combination with the LDPC code lengths supported by the second station and the first capability information. For another example, the first station can determine the first LDPC code length based on the first capability information and the second capability information.

[0269] As an example, in a case where the transmission mode is unicast transmission and the first station and the second station both support the second LDPC code length, the second station determines the first LDPC code length according to the second code length parameter table, and the second code length parameter table comprises the second LDPC code length.

[0270] As another example, 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 station determines the first LDPC code length according to the first code length parameter table.

[0271] For a specific description of this implementation, reference can be made to the related description in step 211 above, and no longer be described in detail here.

[0272] In another possible implementation, in a case where the transmission mode is groupcast transmission, the second station determines the first LDPC code length according to the first code length parameter table. For a specific description of this implementation, reference can be made to the implementation one above, and no longer be described in detail here.

[0273] In yet another possible implementation, in a case where the transmission mode is groupcast transmission, the second station determines the first LDPC code length according to the operation information.

[0274] As one example, the operation information indicates whether the multicast transmission employs the second LDPC code length or whether the second code length parameter table is employed. For example, in a case where the operation information indicates that the multicast transmission does not employ the second LDPC code length or the second code length parameter table, the second station determines the first LDPC code length according to the first code length parameter table. As another example, in a case where the operation information indicates that the multicast transmission employs the second LDPC code length, the first LDPC code length and the second LDPC code length are the same. As yet another example, in a case where the operation information indicates that the second code length parameter table is employed, the second station determines the first LDPC code length according to the second code length parameter table.

[0275] As another example, the operation information indicates whether the broadcast transmission employs the second LDPC code length or whether the second code length parameter table is employed, and indicates whether the multicast transmission employs the second LDPC code length or whether the second code length parameter table is employed. The second station can determine whether the transmission mode of the PPDU is the broadcast transmission or the multicast transmission. In a case where the transmission mode of the PPDU is the broadcast transmission, if the operation information indicates that the broadcast transmission does not employ the second LDPC code length or indicates that the second code length parameter table is not employed, 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 employs the second LDPC code length, the first LDPC code length and the second LDPC code length are the same; if the operation information indicates that the broadcast transmission employs the second code length parameter table, the second station determines the first LDPC code length according to the second code length parameter table. In a case where the transmission mode of the PPDU is the multicast transmission, if the operation information indicates that the multicast transmission does not employ the second LDPC code length or indicates that the second code length parameter table is not employed, 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 employs the second LDPC code length, the first LDPC code length and the second LDPC code length are the same; if the operation information indicates that the multicast transmission employs the second code length parameter table, the second station determines the first LDPC code length according to the second code length parameter table.

[0276] As yet another example, the operation information indicates whether the broadcast transmission employs the second LDPC code length or whether the second code length parameter table is employed, and indicates whether a first multicast group employs the second LDPC code length or whether the second code length parameter table is employed, and indicates whether a second multicast group employs the second LDPC code length or whether the second code length parameter table is employed.

[0277] In the case that the transmission mode of the PPDU is broadcast transmission, if the operation information indicates that the second LDPC code length is not used or the second code length parameter table is not used for the broadcast transmission, the second station determines the first LDPC code length according to the first code length parameter table; if the operation information indicates that the second LDPC code length is used for the broadcast transmission, the first LDPC code length is the same as the second LDPC code length; if the operation information indicates that the second code length parameter table is used for the broadcast transmission, the second station determines the first LDPC code length according to the second code length parameter table.

[0278] In the case that the transmission mode of the PPDU is multicast transmission and the second station belongs to the first multicast group, if the operation information indicates that the second LDPC code length is not used or the second code length parameter table is not used for the first multicast group, the second station determines the first LDPC code length according to the first code length parameter table; if the operation information indicates that the second LDPC code length is used for the first multicast group, the first LDPC code length is the same as the second LDPC code length; if the operation information indicates that the second code length parameter table is used for the first multicast group, the second station determines the first LDPC code length according to the second code length parameter table.

[0279] Optionally, the operation information can be included in the PPDU, or the operation information can be included in a management frame or a signaling field of the PPDU1. The PPDU1 can be a PPDU received by the second station before the PPDU (i.e., the PPDU in step 213) is received. For more information about the operation information, refer to step 211, which will not be described in detail here.

[0280] In the embodiments of the present application, the first station determines the first LDPC code length according to different transmission modes, so that the first station can flexibly determine the LDPC code length corresponding to the transmission mode, so that the first LDPC code length is more matched with the transmission mode.

[0281] Please refer to FIG. 5, which is a flowchart of another communication method provided by the embodiments of the present application. As shown in FIG. 5, the method includes but is not limited to the following steps.

[0282] 501, the first station sends operation information, and correspondingly, the second station receives the operation information.

[0283] The operation information is used to indicate whether the LDPC code length used by the first station is the second LDPC code length, or the operation information is used to indicate whether the second code length parameter table is used by the first station, and the second code length parameter table includes the second LDPC code length.

[0284] Exemplarily, the second LDPC code length is greater than 1944, and the operation information is used to indicate whether the LDPC code length adopted by the PPDU transmitted by the first station is the second LDPC code length, or the operation information is used to indicate whether the PPDU transmitted by the first station adopts the second code length parameter table. It can be understood that the specific description about the second code length parameter table can refer to any one of the above Tables 2-8, which will not be described here again.

[0285] Exemplarily, the operation information can be contained in a signaling field in a management frame or a PPDU. For example, the operation information is contained in a signaling field of a UHR PPDU.

[0286] As an example, the signaling field can be as shown in FIG. 6A, and the signaling field can include at least one of the following: STA ID (occupying 11 bits, B0-B10 respectively), MCS field (occupying 4 bits, B11-B14 respectively), reserved (occupying 1 bit, B15), NSS field (occupying 3 bits, B16-B18 respectively), EQM / UEQM flag field (occupying 1 bit, B19, taking value 0), beamformed (occupying 1 bit, B20), coding (occupying 1 bit, B21). The EQM / UEQM flag is used to indicate whether equal modulation is adopted in this transmission, and if equal modulation is adopted, 0 is set, otherwise 1 is set. The beamformed is used to indicate whether beamforming is adopted in this transmission, and if beamforming is adopted, 1 is set, otherwise 0 is set. The coding is used to indicate whether binary convolution code (BCC) coding or LDPC coding is adopted in this transmission.

[0287] As another example, the signaling field can be as shown in FIG. 6B, and the signaling field can include at least one of the following: STA ID (occupying 11 bits, B0-B10 respectively), MCS field (occupying 4 bits, B11-B14 respectively), reserved (occupying 1 bit, B15), second NSS field (occupying 2 bits, B16-B17 respectively), operation information field (occupying 1 bit, B18), EQM / UEQM flag field (occupying 1 bit, B19, taking value 0), beamformed (occupying 1 bit, B20), coding (occupying 1 bit, B21). The description about the second NSS field can be referred to below, which will not be described in detail here. The signaling field shown in FIG. 6B can be a signaling field in a PPDU under groupcast transmission.

[0288] In the case of multicast transmission, the meaning of each field in the signaling field can be as shown in Table 9.

[0289] Table 9

[0290] Further description regarding FIG. 6B can refer to FIG. 6A, which will not be repeated here.

[0291] As another example, the signaling field can be as shown in FIG. 7, which can include at least one of: STA ID (occupying 11 bits), MCS field (occupying 4 bits), reserved (occupying 1 bit), NSS field (occupying 2 bits), EQM / unequal modulation (UEQM) flag field (occupying 1 bit), UEQM pattern variations (per NSS) (occupying 2 bits).

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

[0293] As yet another example, the signaling field can be as shown in FIG. 8, which includes at least one of: STA ID (occupying 11 bits), MCS field (occupying 4 bits), reserved (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 reserved (occupying 2 bits).

[0294] In this example, the NSS and UEQM pattern variations can be indicated by one field. Further description regarding FIG. 8 can refer to FIG. 7, which will not be repeated here.

[0295] It can be understood that the positions of the various subfields included in the signaling field as shown in FIG. 6A or FIG. 6B or FIG. 7 or FIG. 8 and the number of bits occupied are only examples, and should not be understood as a limitation on the embodiments of the present application. The signaling field in the embodiments of the present application can also be defined by a standard or protocol (such as WiFi7 or WiFi8 or later possible Wi-Fi 9 or WiFi 10 or integrated millimeter wave standard (802.11bq) and the like). In the present application, the PPDU and the signaling field can also have other names, and the present application does not limit the names of the PPDU and the signaling field.

[0296] In a possible implementation, the first station can determine the operation information before sending the operation information. For example, the first station determines the operation information according to the transmission mode. For another example, the first station determines the operation information according to the second capability information. For another example, the first station determines the operation information according to the LDPC code length supported by the first station and the second capability information, or the first station determines the operation information according to the first capability information and the second capability information.

[0297] Optionally, in the case of groupcast transmission, the operation information can indicate whether the groupcast transmission or the broadcast transmission or the multicast transmission adopts the second LDPC code length or whether the second code length parameter table is adopted. For example, the first station can correspond to at least two groupcasts, and the operation information indicates whether the LDPC code length adopted by a first groupcast of the at least two groupcasts is the second LDPC code length, or the operation information is used to indicate whether a second groupcast of the at least two groupcasts adopts the second code length parameter table. For the specific implementation of the content indicated by the operation information in the case of groupcast transmission, reference can be made to one or more of the examples one to three of the operation information shown above. Optionally, the following implementation modes two to five can be combined with the above examples one to three. For the specific manner of combination, no longer be described in detail here.

[0298] The specific manner of the content of the operation information is as follows:

[0299] Implementation mode one:

[0300] The operation information can include a predefined ID, which 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 second code length parameter table is adopted by the first station. By using the predefined ID to indicate the above information, not only can the LDPC code length be clearly indicated by the transmitting and receiving parties, but also the signaling overhead can be saved.

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

[0302] As an example, the predefined STA ID is z1, which indicates that the first station adopts 2xLDPC. When the predefined STA ID is z2, which indicates that the first station adopts 3xLDPC. When the predefined STA ID is z3, which indicates that the first station adopts 4xLDPC. The z1, x2, z3 are any three different values in the range of 2009-2047. For example, z1 can be 2009, z2 can be 2010, and z3 can be 2011.

[0303] As another example, the predefined STA ID is z1, which indicates that the first station adopts the second code length parameter table, and the LDPC code length adopted by the first station can be further determined according to the second code length parameter table. The z1 can be in the range of 2008-2047, for example, z1 can be 2009.

[0304] As another example, the predefined STA ID is z1, which indicates that the first station adopts one of 2xLDPC, 3xLDPC, and 4xLDPC. The z1 can be in the range of 2008-2047, for example, z1 can be 2009.

[0305] Optionally, the predefined ID can be one value or two values. For example, the predefined ID is 0 and 2008, which indicates that the user associated with the first station does not adopt the second LDPC code length or the second code length parameter table. For example, the predefined ID is 2047 and 2009, which indicates that the user not associated with the first station adopts the second LDPC code length or the second code length parameter table.

[0306] Implementation mode two:

[0307] In the case of unicast transmission, the first MCS field occupies Bx1-B y1, x1 and y1 are positive integers, and y1 is greater than x1. In the case of groupcast transmission, Bx1-B y1 carries operation information and a second MCS field. For example, Bx1-By1 indicates the x1th bit to the y1th bit in the first field. For example, in the case of groupcast transmission, the operation information and the second MCS field are contained in the x1th bit to the y1th bit in the first field. In the case of unicast transmission, the first MCS field is contained in the x1th bit to the y1th bit in the first field. For example, the first field is a signaling field.

[0308] In the unicast transmission and the groupcast transmission, the MCS field occupies different number of bits, and the content indicated by the index in the MCS field can be different. For example, in the groupcast transmission, the second MCS field occupies less bits than the first MCS field, and the bits saved by the second MCS field can be used to carry the operation information. Thus, the purpose of indicating the LDPC code length is achieved without increasing the signaling overhead.

[0309] Exemplarily, Bx1 represents the x1th bit of the signaling field, and By1 represents the y1th bit of the signaling field. For example, in FIG. 6A or FIG. 7 or FIG. 8, x1 is 11, and y1 is 14. In the unicast transmission, the MCS adopted by the first station is indicated by the first MCS field (i.e., Bx1 to By1 in the signaling field), and the LDPC code length adopted by the first station is determined by the capability information of the first station and the second station. In the groupcast transmission, Bx1 to By1 in the signaling field are used to indicate the MCS adopted by the first station and indicate whether the second LDPC code length is adopted by the first station (or indicate whether the second code length parameter table is adopted by the first station).

[0310] Exemplarily, Bx1 to By1 include 4 bits, i.e., the first MCS field can include 4 bits, and for the unicast transmission, the MCS adopted by the first station can be indicated by the 4 bits. The 4 bits are used to indicate the index of the MCS adopted by the first station, and the correspondence between the index in the MCS field and the modulation mode and the code rate corresponding to the MCS in the case of the unicast transmission can be as shown in Table 10.

[0311] Table 10

[0312] It can be understood that Table 10 takes the first MCS field including 4 bits as an example, and the first MCS field in the embodiments of the present application can include 5 bits (such as B11 to B15) or more bits. The correspondence between the MCS index and the modulation mode and the code rate shown in Table 10 is only an example and should not be understood as a limitation on the present application. The number of bits of the first MCS field, the correspondence between the index in the first MCS field and the modulation mode and the code rate in the embodiments of the present application can be predefined by a standard or a protocol.

[0313] As can be seen from Table 10, from MCS0 to MCS13, the rate is higher and higher. MCS14 and MCS15 are two special low-rate transmission modes. For the groupcast transmission, there are multiple receiving ends, and the channel states of the multiple receiving ends need to be considered, so a lower rate and a more reliable transmission mode is usually needed. Therefore, in the scenario of the groupcast transmission, a very high MCS does not need to be used, and fewer bits can be used to indicate the MCS adopted by the first station.

[0314] Exemplarily, the second MCS field can include 3 bits (such as B11-B13) (i.e. the second MCS field is obtained by compressing the first MCS field), and the operation information includes 1 bit (such as B14). That is, for the multicast transmission, the MCS adopted by the first station is indicated by 3 bits, and whether the first station adopts the second LDPC code length or whether the first station adopts the second code length parameter table is indicated by 1 bit. The correspondence between the index in the second MCS field and the modulation mode and the code rate in the case of multicast transmission can be as shown in MCS0-MCS7 in Table 11.

[0315] Table 11

[0316] Exemplarily, the operation information can be located before the second MCS field, or the operation information can also be located after the second MCS field, and the application does not limit the order of the operation information and the second MCS field.

[0317] Implementation mode three:

[0318] In the case of unicast transmission, the first NSS field occupies Bx2-B y2, x2 and y2 are both positive integers, and y2 is greater than x2; in the case of multicast transmission, Bx2-B y2 carries operation information and the second NSS field. Exemplarily, Bx2-By2 represents the x1th bit to the y1th bit in the second field. For example, in the case of multicast transmission, the operation information and the second NSS field are contained in the x2th bit to the y2th bit in the second field. In the case of unicast transmission, the first NSS field is contained in the x2th bit to the y2th bit in the second field. For example, the first field and the second field can be the same field. For example, the second field is a signaling field.

[0319] In this transmission mode, the number of bits occupied by the NSS field is different in unicast transmission and multicast transmission, and the content indicated by the index in the NSS field can be different. For example, in the case of multicast transmission, the number of bits occupied by the second NSS field is less than the number of bits occupied by the first NSS field, and the number of bits saved by the second NSS field can be used to carry operation information. Thus, the purpose of indicating the LDPC code length is achieved without increasing the signaling overhead.

[0320] Exemplarily, Bx2 represents the x2th bit of the signaling field of the PPDU, and By2 represents the y2th bit of the signaling field of the PPDU. For example, x2 is 16, y2 is 18, and the first NSS field can be the NSS field shown in FIG. 6A. For another example, x2 is 16, y2 is 17, and the first NSS field can be the NSS field shown in FIG. 7. For another example, x2 is 16, y2 is 18, and the first NSS field can be the NSS and UEQM pattern change field shown in FIG. 8. In unicast transmission, the NSS adopted by the first station is indicated by the first NSS field (i.e., Bx2-By2 in the signaling field), and the LDPC code length adopted by the first station is determined according to the capability information of the first station and the second station. In groupcast transmission, Bx2-By2 in the signaling field is used to indicate the NSS adopted by the first station and to indicate whether the second LDPC code length is adopted by the first station (or to indicate whether the second code length parameter table is adopted by the first station).

[0321] Exemplarily, Bx2-By2 include 3 bits, i.e., the first NSS field can include 3 bits, and in unicast transmission, the NSS adopted by the first station can be indicated by the 3 bits. The 3 bits are used to indicate the NSS adopted by the first station, and for example, the 3 bits indicate that 0-7 respectively represent spatial stream 1 to spatial stream 8. In unicast transmission, the correspondence between the index in the NSS field and the number of spatial streams NSS can be as shown in Table 12.

[0322] Table 12

[0323] It can be understood that Table 12 takes the first NSS field including 3 bits as an example, and the first NSS field in the embodiments of the present application can include 4 bits or more bits. The correspondence between the index and the NSS shown in Table 12 is only an example, and should not be understood as a limitation on the present application. The number of bits of the first NSS field and the correspondence between the index in the NSS field and the NSS in the embodiments of the present application can be predefined by a standard or a protocol.

[0324] For groupcast transmission (such as multicast transmission and / or broadcast transmission), a very high number of spatial streams is generally not adopted, and therefore, in the scenario of groupcast transmission, fewer bits can be used to indicate the NSS adopted by the first station, such as using part of the bits in the first NSS to indicate the NSS adopted by the first station, and using another part of the bits to indicate whether the second LDPC code length is adopted by the first station or whether the second code length parameter table is adopted by the first station.

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

[0326] The correspondence between the index in the second NSS field and the NSS can be as shown in Table 12 for the indexes 0-3 of the NSS, which will not be repeated here. Alternatively, the second NSS field can include a smaller number of bits, such as 1 bit, and the correspondence between the index in the second NSS field and the NSS can be as shown in Table 12 for the indexes 0-1, which will not be repeated here.

[0327] For example, the operation information can be located before the second NSS field, or the operation information can be located after the second NSS field, and the present application does not limit the order of the operation information and the second NSS field.

[0328] Implementation manner four:

[0329] The operation information is carried in the MCS field. The index in the MCS field is a first value, and the first value indicates that the LDPC code length adopted by the first station is the second LDPC code length or that the second code length parameter table is adopted by the first station. The index in the MCS field is a second value, and the second value indicates that the LDPC code length adopted by the first station is less than or equal to 1944 or that the first code length parameter table is adopted by the first station.

[0330] Optionally, the content indicated by the index in the MCS field can be different between the unicast transmission and the multicast transmission.

[0331] As an example, the MCS field includes 4 bits (e.g., B11-B14 as shown in FIG. 6A or FIG. 7 or FIG. 8). For the unicast transmission, the correspondence between the index in the MCS field and the modulation mode and the code rate can be as shown in Table 10, which will not be repeated here. For the multicast transmission, since a very high MCS (e.g., MCS 10-MCS 13) is not needed to be adopted, the content indicated by the index in the MCS field can be redefined, so that the MCS field can indicate the MCS adopted by the first station and indicate whether the second LDPC code length is adopted by the first station or indicate whether the second code length parameter table is adopted by the first station.

[0332] For example, for the multicast transmission, the index of the MCS field and the content indicated thereby can be as shown in Table 13. Taking Table 13 as an example, the first value described above can be a value in 10-13. The second value described above can be a value in 0-9, 14, or 15.

[0333] Table 13

[0334] As another example, in addition to redefining some of the original indexes of the unicast transmission, the indexes reserved in the longer MCS field can also be utilized to indicate whether the second LDPC code length is adopted or whether the second code length parameter table is adopted. For example, if the MCS field includes 5 bits (e.g., B11-B15 in the signaling field), the MCS field indicates the MCS adopted by the first station and indicates whether the second LDPC code length is adopted by the first station or indicates whether the second code length parameter table is adopted by the first station. For example, the indexes of the MCS field and the content indicated thereby can be as shown in Table 14. This example is applicable not only to the broadcast and / or multicast transmission, but also to the unicast transmission.

[0335] Table 14

[0336] In the embodiments of the present application, for the multicast transmission, since the transmission rate is low, the indexes of the MCS can be reused to indicate the above information, and the LDPC code length is indicated on the basis of reducing the signaling overhead as much as possible.

[0337] Implementation Mode Five:

[0338] The operation information is carried in the NSS field. The index in the NSS field is the third value, and the third value indicates that the LDPC code length adopted by the first station is the second LDPC code length or that the second code length parameter table is adopted by the first station. The index in the NSS field is the fourth value, and the fourth value indicates that the LDPC code length adopted by the first station is less than or equal to 1944 or that the first code length parameter table is adopted by the first station.

[0339] In this implementation mode, since the multicast transmission does not use a very high spatial stream, the index in the NSS field can correspond to a lower spatial stream and indicate whether the second LDPC code length is adopted by the first station or whether the second code length parameter table is adopted by the first station, and thus the index of the NSS can be reused to indicate the above information, and the LDPC code length is indicated on the basis of reducing the signaling overhead as much as possible.

[0340] Optionally, the index in the NSS field can indicate different content in the unicast transmission and the multicast transmission. For example, in the case of the unicast transmission, the first station and the second station can determine the LDPC code length to be adopted according to the first capability information and the second capability information without the indication by the operation information, and the unicast transmission supports a higher spatial stream, and thus the index in the NSS field is used to indicate the NSS without indicating whether the second LDPC code length is adopted by the first station or whether the second code length parameter table is adopted by the first station. The correspondence between the index in the NSS field and the NSS can be as shown in Table 12, and when the NSS field includes 3 bits, the NSS field can indicate 8 kinds of spatial stream numbers.

[0341] As an example, the index in the NSS field and its indicated content can be shown in Table 15. Taking Table 15 as an example, the third value can be a value in 4-7, and the fourth value can be a value in 0-3. The first value to the fourth value are only examples, and in a specific implementation, the first value can be the same as or different from the third value, or the second value can be the same as or different from the fourth value. For specific values, embodiments of the present application are not limited.

[0342] Table 15

[0343] As can be seen from Table 15, in the case of multicast transmission, the NSS field can indicate four kinds of NSS.

[0344] As another example, the NSS field can indicate at least fewer spatial streams, for example, the NSS field can only need to indicate one spatial stream or two spatial streams. At the same time, the NSS field can also indicate the LDPC code length adopted by the first station. For example, the index in the NSS field and its indicated content can be shown in Table 16.

[0345] Table 16

[0346] For the above-mentioned implementation mode three and implementation mode five, in the case of unicast transmission, the NSS field occupies three bits; in the case of multicast transmission, the NSS and operation information field occupy three bits. The three bits can indicate 0-7. However, in embodiments of the present application, the second station needs to determine the transmission mode before parsing the three bits, and different transmission modes correspond to different interpretations. For example, in the implementation mode three and the implementation mode five, in the case of broadcast transmission or multicast transmission, the NSS field occupies two bits, and the operation information occupies one bit. The second station can distinguish whether it is unicast transmission or multicast transmission according to the STA ID (only an example), if it is unicast transmission, the three bits indicate the NSS; if it is multicast transmission, two bits of the three bits indicate the NSS, and one bit of the three bits indicates whether to adopt a longer LDPC code length or to adopt a code length parameter table including a longer LDPC code length. Alternatively, the longer LDPC code length indicated by the one bit can include but is not limited to at least one of the following: 2xLDPC, 3xLDPC or 4xLDPC.

[0347] 502, the second station determines the first LDPC code length according to the operation information. The first LDPC code length is the LDPC code length adopted by the first station.

[0348] As an example, the operation information indicates that the LDPC code length adopted by the first station is the second LDPC code length, and the first LDPC code length and the second LDPC code length are the same.

[0349] As another example, the operation information indicates that the first station adopts the second code length parameter table, and the first LDPC code length can be determined by the first station according to the total number of code word bits N avbits of the current data transmission and the second code length parameter table, and the first LDPC code length can be the same as or different from the second LDPC code length.

[0350] As yet another example, the operation information indicates that the first station does not adopt the second code length parameter table, and the second station can determine the first LDPC code length according to the first code length parameter table.

[0351] 503, the first station transmits the PPDU, and correspondingly, the second station receives the PPDU.

[0352] The PPDU adopts the first LDPC code length, and the second station can decode the PPDU based on the first LDPC code length.

[0353] In the embodiments of the present application, the first station can enable the second station to clearly know the LDPC code length adopted by the second station by transmitting the operation information. Thus, the first station and the second station keep the unification of the LDPC code length adopted by each station.

[0354] The various embodiments shown above can be separate embodiments, or the various embodiments can be combined with each other.

[0355] The communication apparatus provided by the embodiments of the present application will be described below.

[0356] The communication apparatus is divided into functional modules according to the method embodiments of the present application, for example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be realized in the form of hardware or in the form of a software functional module. It should be noted that the division of the modules in the present application is illustrative, and is only a logical function division. Actual implementation can have another division manner. The communication apparatus of the embodiments of the present application will be described in detail below with reference to FIGS. 9 to 11.

[0357] FIG. 9 is a structural schematic diagram of a communication apparatus provided by an embodiment of the present application. As shown in FIG. 9, the communication apparatus includes a processing module 901 and a transceiver module 902. The transceiver module 902 can realize corresponding communication functions, and the processing module 901 is used to realize corresponding processing functions. For example, the transceiver module 902 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0358] In some embodiments of the present application, the communication apparatus can be configured to perform the actions performed by the first station in the above method embodiments. The communication apparatus can be the first station itself or a chip or functional module configured in the first station. The transceiver module 902 is configured to perform the transceiving related operations of the first station in the above method embodiments. The processing module 901 is configured to perform the processing related operations of the first station in the above method embodiments.

[0359] For example, the processing module 901 is configured to determine the first LDPC code length according to the transmission mode. The transceiver module 902 is configured to send or output the PPDU.

[0360] Optionally, the transceiver module 902 is further configured to send or output the first capability information and receive or input the second capability information.

[0361] Optionally, the transceiver module 902 is further configured to send or output the operation information.

[0362] It can be understood that the specific implementation of the transmission mode, the first LDPC code length, the PPDU, the first capability information, the second capability information, and the operation information can refer to the related description in the above method embodiments, and will not be described in detail here.

[0363] In other embodiments of the present application, the communication apparatus can be configured to perform the actions performed by the second station in the above method embodiments. The communication apparatus can be the second station itself or a chip or functional module configured in the second station. The transceiver module 902 is configured to perform the transceiving related operations of the second station in the above method embodiments. The processing module 901 is configured to perform the processing related operations of the second station in the above method embodiments.

[0364] For example, the processing module 901 is configured to determine the first LDPC code length according to the transmission mode. The transceiver module 902 is configured to receive or input the PPDU.

[0365] Optionally, the transceiver module 902 is further configured to receive or input the first capability information and send or output the second capability information.

[0366] Optionally, the transceiver module 902 is further configured to receive or input the operation information.

[0367] It can be understood that the specific implementation of the transmission mode, the first LDPC code length, the PPDU, the first capability information, the second capability information, and the operation information can refer to the related description in the above method embodiments, and will not be described in detail here.

[0368] Referring to FIG. 9, in some embodiments of the present application, the communication apparatus can be configured to perform the actions of the first station in the above method embodiments. The communication apparatus can be the first station itself or a chip or functional module configured in the first station. The transceiver module 902 can be configured to perform the transceiving related operations of the first station in the above method embodiments. The processing module 901 can be configured to perform the processing related operations of the first station in the above method embodiments.

[0369] For example, the processing module 901 can be configured to determine the operation information. The transceiver module 902 can be configured to send or output the operation information.

[0370] Optionally, the transceiver module 902 can be further configured to send or output the first capability information and receive or output the second capability information.

[0371] It can be understood that the specific descriptions of the operation information, the first capability information and the second capability information can refer to the related descriptions in the above method embodiments, which will not be repeated here.

[0372] Referring to FIG. 9, in some embodiments of the present application, the communication apparatus can be configured to perform the actions of the second station in the above method embodiments. The communication apparatus can be the second station itself or a chip or functional module configured in the second station. The transceiver module 902 can be configured to perform the transceiving related operations of the second station in the above method embodiments. The processing module 901 can be configured to perform the processing related operations of the second station in the above method embodiments.

[0373] For example, the transceiver module 902 can be configured to receive or input the operation information. The processing module 901 can be configured to determine the first LDPC code length based on the operation information.

[0374] Optionally, the transceiver module 902 can be further configured to receive or input the first capability information and send or output the second capability information.

[0375] It can be understood that the specific descriptions of the operation information, the first capability information and the second capability information can refer to the related descriptions in the above method embodiments, which will not be repeated here.

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

[0377] Optionally, in the above embodiments, the communication apparatus can further include a storage module. The storage module can be configured to store instructions and / or data. The processing module 901 can read the instructions and / or data in the storage module, so that the communication apparatus implements the above method embodiments. For example, the storage module can store the transmission strategy of the radio frequency signal as shown above.

[0378] In the above embodiments, the specific description of each term or name or step can refer to the description in the method embodiments above, and will not be repeated here.

[0379] The specific description of the transceiver module and the processing module in the above embodiments is only an example. For the specific functions or steps of the transceiver module and the processing module, refer to the method embodiments above, and will not be repeated here.

[0380] The communication device of the embodiments of the present application is introduced above, and possible product forms of the communication device are introduced below. Any form of product with the functions of the communication device described in FIG. 7 falls within the protection scope of the embodiments of the present application. The following introduction is only an example, and does not limit the product form of the communication device of the embodiments of the present application.

[0381] In a possible implementation, in the communication device shown in FIG. 9, 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 sending module and a receiving module, the sending module can be a transmitter, and the receiving module can be a receiver, and the sending module and the receiving module are integrated in one device, for example, a transceiver. In the embodiments of the present application, the processor and the transceiver can be coupled, and the connection mode of the processor and the transceiver is not limited in the embodiments of the present application. In the process of executing the above method, the process of sending information in the above method can be the process of outputting the above information by the processor. When outputting the above information, the processor outputs the above information to the transceiver for transmission by the transceiver. After the above information is output by the processor, it can also need to be processed further, and then reach the transceiver. Similarly, the process of receiving information in the above method can be the process of receiving the input above information by the processor. When the processor receives the input information, the transceiver receives the above information and inputs it to the processor. Further, after the transceiver receives the above information, the above information can need to be processed further, and then input to the processor.

[0382] As shown in FIG. 10, the communication device 100 includes one or more processors 1020 and a transceiver 1010.

[0383] In some embodiments of the present application, the communication device can be used to execute the steps or methods or functions executed by the first station, for example, the processor 1020 can be used to execute the functions or steps implemented by the processing module 901 shown in FIG. 9, and the transceiver 1010 can be used to execute the functions or steps implemented by the transceiver module 902 shown in FIG. 9. The specific description of the processor 1020 and the transceiver 1010 can refer to the method embodiments shown in FIG. 9 or the above, and will not be repeated here.

[0384] In some embodiments of the application, the communication device is configured to perform the steps or methods or functions performed by the second station as described above, e.g., the processor 1020 can be configured to perform the functions or steps implemented by the processing module 901 as shown in FIG. 9, and the transceiver 1010 can be configured to perform the functions or steps implemented by the transceiving module 902 as shown in FIG. 7. For details of the processor 1020 and the transceiver 1010, reference can be made to the method embodiments shown in FIG. 9 or above, and thus no further elaboration is provided here.

[0385] In the various implementations of the communication device shown in FIG. 10, the transceiver can include a receiver configured to perform the functions (or operations) of receiving and a transmitter configured to perform the functions (or operations) of transmitting. The transceiver is configured to communicate with other devices / apparatuses over a transmission medium.

[0386] Optionally, the communication device 100 can further include one or more memories 1030 configured to store program instructions and / or data. The memory 1030 is coupled to the processor 1020. The coupling between the components, units or modules in the embodiments of the application can be indirect coupling or communication connection therebetween, which can be electrical, mechanical or other form, for information interaction between the components, units or modules. The processor 1020 can operate in cooperation with the memory 1030. The processor 1020 can execute the program instructions stored in the memory 1030. Optionally, at least one of the one or more memories can be included in the processor.

[0387] The specific connection medium between the transceiver 1010, the processor 1020 and the memory 1030 in the embodiments of the application is not limited. In FIG. 10, the memory 1030, the processor 1020 and the transceiver 1010 are connected through a bus 1040, which is represented by a thick line in FIG. 10, and the connection mode between other components is only schematically illustrated and is not limited. The bus can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, only one thick line is used in FIG. 10, but it does not mean that there is only one bus or only one type of bus.

[0388] In the embodiments of the application, the processor can be a general processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., which can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the application. The general processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in conjunction with the embodiments of the application can be directly embodied as execution completed by a hardware processor, or executed by a combination of hardware and software modules in the processor, etc.

[0389] The memory in the embodiments of the present application can include, but is not limited to, a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), a random access memory (RAM), an erasable programmable ROM (EPROM), a read-only memory (ROM), a compact disc read-only memory (CD-ROM), and the like. The memory is any storage medium that can be used to carry or store program codes in the form of instructions or data structures and can be read and / or written by a computer (such as the communication device shown in the present application and the like). The memory in the embodiments of the present application can also be a circuit or any other device capable of realizing a storage function, used for storing program instructions and / or data.

[0390] The processor 1020 is mainly used for processing communication protocols and communication data, controlling the whole communication device, executing software programs, and processing data of the software programs. The memory 1030 is mainly used for storing software programs and data. The transceiver 1010 can include a control circuit and an antenna, and the control circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. The input and output devices, such as touch screens, display screens, keyboards, and the like, are mainly used for receiving user input data and outputting data to users.

[0391] 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 circuit. The radio frequency circuit converts the baseband signal into a radio frequency signal, and transmits the radio frequency signal through the antenna in the form of electromagnetic waves. When data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1020. The processor 1020 converts the baseband signal into data and processes the data.

[0392] In another implementation, the radio frequency circuit and the antenna can be arranged independently of the processor performing baseband processing, for example, in a distributed scenario, the radio frequency circuit and the antenna can be arranged remotely from the communication device.

[0393] The communication apparatus shown in the embodiments of the present application can also have more components than those shown in FIG. 10, and the embodiments of the present application do not limit this. The method performed by the processor and the transceiver shown above is only an example, and the steps specifically performed by the processor and the transceiver can refer to the method described above.

[0394] In another possible implementation, in the communication apparatus shown in FIG. 9, the processing module 901 can be one or more logic circuits, and the transceiving module 902 can be an input / output interface, also referred to as a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiving module 902 can also be a sending module and a receiving module, the sending module can be an output interface, and the receiving module can be an input interface, and the sending module and the receiving module are integrated in one module, for example, an input / output interface. As shown in FIG. 11, the communication apparatus shown in FIG. 11 includes a logic circuit 1101 and an interface 1102. That is, the processing module 901 described above can be implemented by the logic circuit 1101, and the transceiving module 902 can be implemented by the interface 1102. The logic circuit 1101 can be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, etc., and the interface 1102 can be a communication interface, an input / output interface, a pin, etc. For example, FIG. 11 is a chip obtained by taking the above communication apparatus as an example, and the chip includes the logic circuit 1101 and the interface 1102.

[0395] In the embodiments of the present application, the logic circuit and the interface can also be coupled to each other. The embodiments of the present application do not limit the specific connection mode of the logic circuit and the interface. For example, the logic circuit 1101 can be used to perform the functions or steps implemented by the processing module 901 shown in FIG. 9, and the interface 1102 can be used to perform the functions or steps implemented by the transceiving module 902 shown in FIG. 9. For specific descriptions of the logic circuit 1101 and the interface 1102, refer to the method embodiments shown in FIG. 9 or the above, which will not be described in detail here.

[0396] The communication apparatus shown in the embodiments of the present application can implement the method provided by the embodiments of the present application in the form of hardware, or implement the method provided by the embodiments of the present application in the form of software, etc., and the embodiments of the present application do not limit this.

[0397] In addition, the embodiments of the present application also provide a communication system, which includes a first station and a second station, and the first station and the second station can be used to perform the method in any of the preceding embodiments.

[0398] The present application also provides a computer program for implementing the operations and / or processes performed by the first station or the second station in the method provided by the present application.

[0399] The application further provides a computer readable storage medium, wherein computer code is stored in the computer readable storage medium, and when the computer code is run on a computer, the computer code causes the computer to perform operations and / or processes performed by the first station or the second station in the method provided by the application.

[0400] The application further provides a computer program product, which comprises computer code or a computer program, and when the computer code or the computer program is run on a computer, operations and / or processes performed by the first station or the second station in the method provided by the application are performed.

[0401] In several embodiments provided in the application, it should be understood that the disclosed system, communication device and method can be implemented in other manners. For example, the embodiments of the communication device described above are merely schematic; for example, the division of the modules is merely a logical function division; an actual implementation can be another division manner; for example, a plurality of modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed coupling or direct coupling or communication connection between the modules can be indirect coupling or communication connection through some interfaces, communication devices or modules, and can also be electrical, mechanical or other forms of connection.

[0402] The modules illustrated as separated components can or can not be physically separated, and the components illustrated as modules can or can not be physical modules, i.e., can be located in one place, or can be distributed on a plurality of network modules. Part or all of the modules can be selected according to actual needs to achieve the technical effects of the scheme provided in the embodiments of the application.

[0403] In addition, each functional module in each embodiment of the application can be integrated into a processing module, or each module can exist physically independently, or two or more modules can be integrated into one module. The integrated module can be realized in the form of hardware or in the form of a software functional module.

[0404] The integrated module, if implemented in the form of a software function module and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or say the part that contributes to the prior art, or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a readable storage medium, including a plurality of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in various embodiments of the present application. The aforementioned readable storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0405] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection 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