Communication method, communication device, and communication system

Abstract

Embodiments of the present invention relate to a communication method, a communication device, and a communication system. The communication method is applied to a first device, and comprises: determining a first radio frame, the first radio frame comprising first identification information, and the first identification information identifying whether the first device supports a low-density parity-check code (LDPC) data encoding mode having a codeword length of 3844 bits; and sending the first radio frame. The first identification information is used for identifying whether the first device supports the LDPC data encoding mode having the codeword length of 3844 bits, so that a 2×LDPC transmission rule is used in data transmission, thereby improving data transmission efficiency and meeting service transmission requirements.

Description

Communication methods, communication equipment and communication systems Technical Field

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

[0002] Currently, research on Wi-Fi technology includes topics such as Ultra High Reliability (UHR), with the vision of improving the reliability of Wireless Local Area Networks (WLAN) connections, reducing latency, improving manageability, increasing throughput at different signal-to-noise ratio (SNR) levels, and reducing device-level power consumption.

[0003] In UHR, data encoding methods will be further enhanced to ensure the latency requirements of low-latency services.

[0004] Summary of the Invention

[0005] This disclosure provides a communication method, communication device, and communication system to further enhance data encoding methods.

[0006] In a first aspect, embodiments of this disclosure provide a communication method applied to a first device, the method comprising:

[0007] A first wireless frame is determined; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits;

[0008] Send the first wireless frame.

[0009] Secondly, embodiments of this disclosure also provide a communication method, the method comprising:

[0010] Receive a first wireless frame; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

[0011] Thirdly, this disclosure also provides a communication device, which is a first device, comprising:

[0012] The determination module is used to determine the first wireless frame; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits;

[0013] The transmitting module is used to transmit the first wireless frame.

[0014] Fourthly, embodiments of this disclosure also provide a communication device, which is a second device, the second device comprising:

[0015] A receiving module is used to receive a first wireless frame; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

[0016] Fifthly, embodiments of this disclosure also provide a communication device, which is a second device, comprising:

[0017] One or more processors;

[0018] The second device is used to execute the communication method described in the first aspect of the embodiments of this disclosure.

[0019] Sixthly, embodiments of this disclosure also provide a communication device, which is a second device, comprising:

[0020] One or more processors;

[0021] The second device is used to execute the communication method described in the second aspect of the embodiments of this disclosure.

[0022] In a seventh aspect, embodiments of this disclosure also provide a communication system, including a first device and a second device;

[0023] Wherein, the first device determines the first wireless frame; the first wireless frame includes first identification information, the first identification information indicating whether the first device supports LDPC data encoding with a codeword length of 3844 bits;

[0024] The first wireless frame is sent to the second device.

[0025] Eighthly, embodiments of this disclosure also provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in the first aspect of this disclosure, or to perform the communication method as described in the second aspect of this disclosure.

[0026] In this embodiment of the disclosure, the first device carries first identification information in the first wireless frame and sends the first wireless frame to the second device. The first identification information indicates whether the first device supports the use of LDPC data encoding with a codeword length of 3844 bits, so as to use the 2×LDPC transmission rule in data transmission, improve data transmission efficiency, and meet the service transmission requirements.

[0027] Additional aspects and advantages of embodiments of this disclosure will be set forth in part in the description which follows, and will become apparent from the description or may be learned by practice of this disclosure. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

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

[0030] Figure 2 is a schematic diagram of one example of a communication method provided in an embodiment of this disclosure;

[0031] Figure 3 is a second example schematic diagram of the communication method provided in the embodiments of this disclosure;

[0032] Figure 4 is a third example schematic diagram of the communication method provided in the embodiments of this disclosure;

[0033] Figure 5 is a flowchart illustrating one of the communication methods provided in this embodiment of the present disclosure;

[0034] Figure 6 is a second schematic flowchart of the communication method provided in this embodiment of the present disclosure;

[0035] Figure 7 is a schematic diagram of the structure of the first device proposed in an embodiment of this disclosure;

[0036] Figure 8 is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure;

[0037] Figure 9 is a schematic diagram of the structure of the terminal device proposed in an embodiment of this disclosure;

[0038] Figure 10 is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0039] This disclosure presents a communication method, communication device, and communication system.

[0040] In a first aspect, embodiments of this disclosure provide a communication method applied to a first device, the method comprising:

[0041] A first wireless frame is determined; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits;

[0042] The first wireless frame is sent. In the above embodiment, the first device carries first identification information in the first wireless frame and sends the first wireless frame to the second device. The first identification information identifies whether the first device supports the use of LDPC data encoding with a codeword length of 3844 bits, so as to use the 2×LDPC transmission rule in data transmission, improve data transmission efficiency, and meet the service transmission requirements.

[0043] Secondly, embodiments of this disclosure provide a communication method applied to a second device, the method comprising:

[0044] Receive a first wireless frame; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

[0045] Thirdly, embodiments of this disclosure also provide a communication device, which is a first device, including at least one of a determining module and a sending module; wherein the first device is used to execute an optional implementation of the first aspect.

[0046] Fourthly, embodiments of this disclosure also provide a communication device, which is a second device, including: a receiving module; wherein the second device is used to execute an optional implementation of the second aspect.

[0047] Fifthly, embodiments of this disclosure also provide a communication device, which is a first device, comprising:

[0048] One or more processors;

[0049] The first device is used to execute an optional implementation of the first aspect.

[0050] Sixthly, embodiments of this disclosure also provide a communication device, which is a second device, comprising:

[0051] One or more processors;

[0052] The second device is used to execute an optional implementation of the second aspect.

[0053] In a seventh aspect, embodiments of this disclosure also provide a communication system, including a first device and a second device; wherein the first device is configured to perform the optional implementation as described in the first aspect, and the second device is configured to perform the optional implementation as described in the second aspect.

[0054] Eighthly, embodiments of this disclosure also provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the optional implementations described in the first and second aspects.

[0055] Ninthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the optional implementations of the first and second aspects.

[0056] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the optional implementations of the first and second aspects.

[0057] Eleventhly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0058] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0059] This disclosure provides communication methods, communication devices, and communication systems. In some embodiments, the terms "communication method" and "signal transmission method," "wireless frame transmission method," etc., can be used interchangeably, as can the terms "information processing system" and "communication system."

[0060] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0061] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0062] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0063] In the embodiments disclosed herein, "multiple" refers to two or more.

[0064] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0065] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0066] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0067] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0068] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0069] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0070] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0071] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0072] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0073] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0074] In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel and downlink channel can be replaced with side channel, and uplink link and downlink link can be replaced with side link.

[0075] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0076] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0077] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0078] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0079] As shown in Figure 1, the communication system 100 includes a first device 101 and a second device 102; wherein the first device 101 and the second device 102 can be an access point (AP) device and a station (STA) device, respectively.

[0080] In some embodiments, the access point device can be an access point for mobile terminals to access a wired network. An AP acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet. Specifically, an AP can be a terminal device or network device with a Wi-Fi chip. Optionally, the AP can support various WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, 802.11bf, and 802.11bn, as well as the next-generation 802.11 protocol, but is not limited to these.

[0081] In some embodiments, the site equipment includes, for example, a wireless communication chip, a wireless sensor, or a wireless communication terminal that supports Wi-Fi communication. Optionally, the wireless communication terminal may be at least one of, but is not limited to, a mobile phone, a wearable device, an IoT device that supports Wi-Fi communication, a car with Wi-Fi communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home.

[0082] Specifically, the site device can be a terminal device or network device with a Wi-Fi chip. Optionally, the site device 102 can support multiple WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, 802.11bf, and 802.11bn, as well as the next-generation 802.11 protocol, but is not limited to these.

[0083] Optionally, in this embodiment of the disclosure, AP and STA can be devices that support multiple links. For example, they can be represented as Access Point Multi-Link Device (AP MLD) and Non-Access Point Multi-Link Device (Non-AP MLD), respectively. AP MLD can represent an access point that supports multiple link communication functions, and non-AP MLD can represent a site that supports multiple link communication functions.

[0084] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0085] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0086] The embodiments disclosed herein can be applied to Wireless Local Area Networks (WLANs), such as LANs using the 802.11 series of protocols. In a WLAN, a Basic Service Set (BSS) is a fundamental component. An BSS network consists of site devices with some association within a specific coverage area. One type of association is where sites communicate directly with each other in a self-organizing network; this is called an Independent Basic Service Set (IBSS). Another more common scenario is that in a BSS network, there is only one central site dedicated to managing the BSS, called an Access Point (AP) device, while other sites in the BSS network that are not APs are called terminals, also known as non-AP STAs. APs and non-AP STAs are collectively referred to as STAs. When describing STAs, it is not necessary to distinguish between APs and non-AP STAs. Within the same BSS network, due to distance, transmission power, etc., a STA cannot detect other STAs that are far away; they are each other's hidden nodes.

[0087] Figure 2 is one of the interactive schematic diagrams of a communication method according to an embodiment of the present disclosure. As shown in Figure 2, the method includes:

[0088] Step 201: The first device 101 determines the first wireless frame; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

[0089] Low-density parity check (LDPC) codes are linear block codes with a very sparse parity check matrix (H). The number of non-zero elements in the parity check matrix H is much smaller than the number of zero elements, or the row and column weights of the matrix are very small compared to the code length. Based on these characteristics, LDPC codes can be used to construct high-performance, low-complexity codes.

[0090] In related technologies of wireless communication systems, such as the 802.11n to 802.11bn communication protocols, LDPC is used to encode data. The maximum codeword length is 1944 bits, and the coding rate is, for example, 5 / 6, 3 / 4, 2 / 3, and 1 / 2. The codeword length can also be called the symbol length; for example, in binary code, the codeword length indicates the number of bits in the binary code. In this embodiment, to improve data transmission efficiency, the communication device may use a 2×(2× means twice) LDPC data encoding method, that is, the LDPC codeword length is 3888 bits, and the supported coding rate may be 5 / 6, 3 / 4, 2 / 3, and 1 / 2. Therefore, in this embodiment, the first device determines a first wireless frame, and carries first identification information in the first wireless frame. The first identification information indicates whether the first device supports the 3844-bit codeword length LDPC data encoding method.

[0091] It is understood that in this embodiment of the disclosure, "support" means at least one of "support sending" and "support receiving"; that is, whether the first device supports LDPC data encoding with a codeword length of 3844 bits includes at least one of "whether the first device supports receiving LDPC data encoding with a codeword length of 3844 bits (the maximum codeword length is 3844)" and "whether the first device supports sending LDPC data encoding with a codeword length of 3844 bits (the maximum codeword length is 3844)".

[0092] For example, the first identification information can occupy one bit. If the bit is set to "1", it means that the first device supports LDPC data encoding with a codeword length of 3844 bits; if the bit is set to "0", it means that the first device does not support LDPC data encoding with a codeword length of 3844 bits.

[0093] Alternatively, the first identification information may occupy two bits, one bit indicating whether the first device supports receiving LDPC data encoding with a codeword length of 3844 bits, and the other bit indicating whether the first device supports sending LDPC data encoding with a codeword length of 3844 bits.

[0094] In addition, the first identification information may occupy multiple bits to identify whether the first device supports LDPC data encoding with a codeword length of 3844 bits under different operating parameters; the operating parameters include at least one of bandwidth, spatial stream number, resource unit (RU) format, and modulation coding scheme.

[0095] In some embodiments, the first radio frame may be a radio frame sent during the initial association process, the first device includes a mobile access point (AP) or a multi-link site device (AP MLD), and the first radio frame includes a beacon frame, a probe response frame, an unsolicited probe response frame, an association response frame, and / or a reassociation response frame.

[0096] If the first device includes a site device (STA) or a non-AP MLD, then the first radio frame includes a probe request frame, an unsolicited probe request frame, an association request frame, and / or a reassociation request frame.

[0097] Step 202: The first device 101 sends the first wireless frame to the second device 102.

[0098] In this process, the first device 101 sends the first wireless frame to the second device 102, and identifies whether the first device supports 2×LDPC codeword length signaling (i.e. whether it supports LDPC data encoding using 3844 bit codeword length (the maximum bit codeword length is 3844)) through the first identification information, so as to use the 2×LDPC transmission rule in data transmission, improve data transmission efficiency, and meet the service transmission requirements.

[0099] In some embodiments, the first identification information includes: the first identification information may include at least one of the following three cases:

[0100] In scenario one, the first identification information includes a first identification bit, which indicates whether the first device supports LDPC data encoding with a codeword length of 3844 bits; wherein, "support" means at least one of "support sending" and "support receiving".

[0101] For example, the first identifier occupies one bit. If the bit is set to "1", it means that the first device supports LDPC data encoding with a codeword length of 3844 bits; if the bit is set to "0", it means that the first device does not support LDPC data encoding with a codeword length of 3844 bits.

[0102] In the second scenario, the first identification information includes a second identification bit and / or a third identification bit. The second identification bit indicates whether the first device supports receiving LDPC data encoding with a codeword length of 3844 bits; the third identification bit indicates whether the first device supports sending LDPC data encoding with a codeword length of 3844 bits.

[0103] For example, the first identification information can occupy two bits, while the second and third identification bits each occupy one bit. The second identification bit indicates whether the first device supports receiving LDPC data encoding with a 3844-bit codeword length. For example, if the first device is an AP, it indicates whether it supports receiving uplink (UL) physical layer protocol data units (PPDUs) encoded in LDPC data. The third identification bit indicates whether the first device supports transmitting LDPC data encoding with a 3844-bit codeword length. For example, if the first device is an AP, it indicates whether it supports transmitting downlink (DL) PPDUs encoded in LDPC data.

[0104] Scenario 3: The first identification information includes a fourth identification bit, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits under different operating parameters; the operating parameters include at least one of bandwidth, spatial stream number, resource unit (RU) format, and modulation and coding scheme.

[0105] Specifically, a fourth flag can be set for each different (or group of different) operating parameter to indicate whether the first device supports LDPC data encoding with a 3844-bit codeword length under that (or group of) operating parameter. For example, with bandwidths of 160MHz and 320MHz, the fourth flag indicates whether the first device supports LDPC data encoding with a 3844-bit codeword length (i.e., 2×LDPC). Alternatively, with bandwidths of 160MHz and 320MHz, if the number of spatial streams (NSS) is greater than or equal to 4, the fourth flag indicates whether the first device supports LDPC data encoding with a 3844-bit codeword length. Or, it can support 2×LDPC under dRU, such as 26-tone, 52-tone dRU, etc.

[0106] Figure 3 is a second interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3, the above method includes:

[0107] Step 301, the first device 101 determines the first wireless frame; wherein, the first wireless frame includes a first information element and a second information element; the first information element includes first identification information, the first identification information indicating whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

[0108] The second information element includes a fifth identifier bit, and the fifth identifier bit and the first identifier information can be set in two ways: Method 1 and Method 2.

[0109] In Method 1, the fifth identifier bit is set in the High Throughput (HT) information element, the Very High Throughput (VHT) information element, and / or the High Efficiency (HE) information element. When the first device supports LDPC data encoding with 1944, 1296, or 648 bit length codewords, the first identifier bit in the first information element indicates whether the first device supports LDPC data encoding with 1944, 1296, or 648 bit length codewords in the UHR information element.

[0110] The fifth identifier bit indicates that when the first device identifier supports LDPC data encoding methods with 1944, 1296, or 648 bit length codewords in the HT information element, VHT information element, and / or HE information element, it respectively indicates that it supports LDPC data encoding methods with 1944, 1296, or 648 bit length codewords under the corresponding transmission protocol.

[0111] For example, if the fifth identifier bit identifies the first device in the HT information element, then in the scenario where the identifier corresponds to the HT transmission protocol (e.g., 802.11n), it supports LDPC data encoding methods with codeword lengths of 1944, 1296, or 648 bits; correspondingly, VHT corresponds to the 802.11ac series transmission protocols, and HE corresponds to the 802.11ax series transmission protocols.

[0112] Taking the fifth flag bit set in the HT information element as an example, if the fifth flag bit indicates that the first device supports LDPC data encoding methods with codeword lengths of 1944, 1296, or 648 bits, then the first flag information indicates whether the first device supports LDPC data encoding methods with codeword lengths of 3844 bits in the UHR information element, i.e., 2×LDPC data encoding. For example, if the fifth flag bit is set to "1", then the first flag information is set to "0", indicating that the first device does not support LDPC data encoding methods with codeword lengths of 3844 bits. If the fifth flag bit is set to "1", then the first flag information is set to "1", indicating that the first device supports LDPC data encoding methods with codeword lengths of 3844 bits.

[0113] Method 2: The fifth identifier bit is set in the HT information element, VHT information element and / or HE information element, and when the identifier indicates that the first device does not support 1944, 1296 or 648 bit length codeword LDPC data encoding, the first identifier bit in the first information element is set as a reserved bit.

[0114] If the fifth identifier indicates that the first device does not support LDPC data encoding with a codeword length of 1944, 1296, or 648 bits, the first identifier information in the first information element is set to a reserved bit; that is, in HT, VHT, and / or HE transmission scenarios, if LDPC data encoding with a codeword length of 1944, 1296, or 648 bits is not supported, then in UHR transmission scenarios, it is also possible that LDPC data encoding with a codeword length of 3844 bits is not supported.

[0115] Step 302: The first device 101 sends the first wireless frame to the second device 102.

[0116] In some embodiments, the first device includes at least one of the following:

[0117] Mobile APs, STAs, and multi-link devices, only supporting STAs or non-AP MLDs with a 20MHz channel bandwidth.

[0118] Specifically, for a regular AP as the first device, since its capabilities need to be higher than those of a STA in practical applications, the first identification information does not need to be set. However, for a mobile AP as the first device, the first identification information needs to be set. For a STA as the first device that only supports 20MHz channel bandwidth (20MHz only STA), the first identification information also needs to be set. Furthermore, since devices may support multi-link communication in the 802.11bn protocol, if multi-link communication is supported (i.e., the first device includes or includes non-AP MLDs), then this first identification information is MLD-level information.

[0119] In some embodiments, the first information element includes a UHR capability information element;

[0120] The second information element includes HT capability information element, VHT capability information element and / or HE capability information element.

[0121] Figure 4 is a third interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 4, the above method includes:

[0122] Step 401, the AP determines and sends a first radio frame to the STA; the first radio frame also includes a trigger frame; the first radio frame includes a sixth flag bit, which indicates whether the subsequent part of the TB PPDU uses LDPC data encoding with a codeword length of 3844 bits;

[0123] The first identification information also indicates that the Trigger-Based Physical Protocol Data Unit (TB PPDU) sent by the STA to the AP must use LDPC data encoding with a codeword length of 3844 bits.

[0124] For example, if the trigger frame sent by the AP to the STA includes first identification information and the sixth identification bit indicates that the AP supports LDPC data encoding with a codeword length of 3844 bits, then the TB PPDU sent by the STA to the AP must use LDPC data encoding with a codeword length of 3844 bits.

[0125] Step 402: STA sends a TB PPDU to AP. The preamble of the TB PPDU may carry an identifier bit to identify whether the payload and data portions of the data frame use 2×LDPC encoding.

[0126] Accordingly, the preamble of the TB PPDU sent by the STA to the AP may carry an identifier bit to indicate whether the payload part and / or data part of the data frame are respectively encoded using 2×LDPC.

[0127] In some embodiments, the method further includes:

[0128] The first device sends a UL PPDU or DL ​​PPDU; wherein the preamble of the UL PPDU or DL ​​PPDU carries a seventh identifier bit, which indicates whether the payload part and / or data part of the UL PPDU or DL ​​PPDU uses LDPC data encoding with a codeword length of 3844 bits.

[0129] If the first device sends a data frame, for example, the STA sends a UL PPDU to the AP, or the AP sends a DL PPDU to the STA, then the preamble of the data frame carries an identifier bit to indicate whether the payload part and / or the data part of the data frame are respectively encoded using 2×LDPC.

[0130] The first device carries first identification information in the first wireless frame and sends the first wireless frame to the second device. The first identification information indicates whether the first device supports the use of LDPC data encoding with a codeword length of 3844 bits, so as to use the 2×LDPC transmission rule in data transmission, improve data transmission efficiency, and meet the service transmission requirements.

[0131] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "bit", "data", "program", and "chip" can be used interchangeably.

[0132] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0133] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0134] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0135] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0136] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0137] The communication method involved in the embodiments of this disclosure may include the foregoing steps and at least one of the embodiments. For example, step 201 may be implemented as an independent embodiment, step 202 may be implemented as an independent embodiment, step 301 may be implemented as an independent embodiment, step 302 may be implemented as an independent embodiment, step 401 may be implemented as an independent embodiment, and step 402 may be implemented as an independent embodiment; the combination of step 201 and step 202 may be implemented as an independent embodiment, the combination of step 301 and step 302 may be implemented as an independent embodiment, and the combination of step 401 and step 402 may be implemented as an independent embodiment, but is not limited thereto.

[0138] In some embodiments, other optional implementations may be described before or after the specification corresponding to Figures 2 to 4.

[0139] Figure 5 is a flowchart illustrating one of the communication methods according to an embodiment of the present disclosure.

[0140] As shown in Figure 5, the above method can be applied to the first device 101, and the method includes:

[0141] Step 501, determine the first wireless frame; the first wireless frame includes first identification information, the first identification information indicating whether the first device supports the low-density parity-check code (LDPC) data encoding method with a codeword length of 3844 bits;

[0142] Step 502: Send the first wireless frame.

[0143] Optionally, in this embodiment of the disclosure, the first identification information includes at least one of the following:

[0144] The first identifier bit indicates whether the first device supports LDPC data encoding with a codeword length of 3844 bits;

[0145] The second flag bit and / or the third flag bit, wherein the second flag bit indicates whether the first device supports receiving LDPC data encoding with a codeword length of 3844 bits; and the third flag bit indicates whether the first device supports sending LDPC data encoding with a codeword length of 3844 bits.

[0146] The fourth identifier bit indicates whether the first device supports LDPC data encoding with a codeword length of 3844 bits under different operating parameters; the operating parameters include at least one of bandwidth, spatial stream number, resource unit (RU) format, and modulation and coding scheme.

[0147] Optionally, in this embodiment of the present disclosure, the first wireless frame includes a first information element and a second information element;

[0148] The second information element includes a fifth identifier bit, which is set in the HT information element, VHT information element and / or HE information element. When the first device supports 1944, 1296 or 648 bit length codeword LDPC data encoding, the first identifier bit in the first information element indicates whether the first device supports 3844 bit length codeword LDPC data encoding in the UHR information element.

[0149] or

[0150] The fifth identifier bit is set in the HT information element, VHT information element and / or HE information element, and when the first device does not support LDPC data encoding of 1944, 1296 or 648 bit length codewords, the first identifier bit in the first information element is set as a reserved bit.

[0151] Optionally, in this embodiment of the disclosure, the first device includes at least one of the following:

[0152] Mobile APs, STAs, and multi-link devices only support STAs or non-AP MLDs with a channel bandwidth of 20MHz.

[0153] Optionally, in this embodiment of the disclosure, the method includes at least one of the following:

[0154] The first information element includes the ultra-high reliability (UHR) capability information element;

[0155] The second information element includes HT capability information element, VHT capability information element and / or HE capability information element;

[0156] The first device includes a mobile AP or AP MLD, and the first wireless frame includes a beacon frame, a probe response frame, an unsolicited probe response frame, an association response frame, and / or a reassociation response frame.

[0157] The first device includes a STA or a non-AP MLD, and the first radio frame includes a probe request frame, an unsolicited probe request frame, an association request frame, and / or a reassociation request frame.

[0158] Optionally, in this embodiment of the disclosure, the first wireless frame includes a trigger frame, and the first device includes an access point (AP).

[0159] The first identification information also indicates that the physical layer protocol data unit TB PPDU based on the trigger frame sent by the STA to the AP must use LDPC data encoding with a codeword length of 3844 bits.

[0160] Optionally, in this embodiment of the disclosure, the PHY preamble of the TB PPDU includes:

[0161] The sixth identifier bit indicates whether the subsequent part of the TB PPDU uses LDPC data encoding with a codeword length of 3844 bits.

[0162] Optionally, in this embodiment of the disclosure, the method further includes:

[0163] Send a UL PPDU or DL ​​PPDU; wherein the preamble of the UL PPDU or DL ​​PPDU carries a seventh identifier bit, the seventh identifier bit indicating whether the payload part and / or data part of the UL PPDU or DL ​​PPDU uses LDPC data encoding with a codeword length of 3844 bits.

[0164] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0165] The communication method involved in the embodiments of this disclosure may include the foregoing steps and at least one of the embodiments. For example, step 501 may be implemented as a separate embodiment, step 502 may be implemented as a separate embodiment, and the combination of step 501 and step 502 may be implemented as a separate embodiment, but is not limited thereto.

[0166] In some embodiments, other optional implementations described before or after the specification corresponding to Figure 5 may be referred to.

[0167] Figure 6 is a second schematic flowchart illustrating a communication method according to an embodiment of the present disclosure.

[0168] As shown in Figure 6, the above method can be applied to the second device 102, and the method includes:

[0169] Step 601: Receive a first wireless frame; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

[0170] Optionally, in this embodiment of the disclosure, the first wireless frame includes a trigger frame, and the first device includes an access point (AP).

[0171] The first identification information also indicates that the TB PPDU sent by the second device to the AP must use LDPC data encoding with a codeword length of 3844 bits.

[0172] Optionally, in this embodiment of the disclosure, the PHY preamble of the TB PPDU includes:

[0173] The sixth identifier bit indicates whether the subsequent part of the TB PPDU uses LDPC data encoding with a codeword length of 3844 bits.

[0174] Optionally, in this embodiment of the disclosure, the method further includes:

[0175] Send a UL PPDU or DL ​​PPDU; wherein the preamble of the UL PPDU or DL ​​PPDU carries a seventh identifier bit, the seventh identifier bit indicating whether the payload part and / or data part of the UL PPDU or DL ​​PPDU uses LDPC data encoding with a codeword length of 3844 bits.

[0176] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0177] The communication methods involved in the embodiments of this disclosure may include the foregoing steps and at least one of the embodiments. In some embodiments, reference can be made to the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, which will not be repeated here.

[0178] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0179] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD), such as a field-programmable gate array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0180] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0181] Figure 7 is a schematic diagram of the structure of a first device according to an embodiment of this disclosure. The first device is used to perform any of the above methods. In some embodiments, as shown in Figure 7, the first device 700 may include at least one of a determining module 701, a sending module 702, etc.

[0182] In some embodiments, the determining module 701 is used to determine whether the first wireless frame includes first identification information, the first identification information indicating whether the first device supports the low-density parity-check code (LDPC) data encoding method with a codeword length of 3844 bits; and the sending module 702 is used to send the first wireless frame.

[0183] Optionally, the determining module 701 is used to execute at least one of the communication steps (e.g., steps 201, 301, 401, 501, but not limited thereto) executed by the first device 101 in any of the above methods, which will not be described in detail here. The sending module 702 is used to execute at least one of the sending and receiving steps (e.g., steps 202, 302, 402, 502, but not limited thereto) executed by the first device 101 in any of the above methods, which will not be described in detail here.

[0184] In some embodiments, the determining module can be replaced by the processing module or the processor, and the sending module can be replaced by the transceiver module or the transceiver.

[0185] Figure 8 is a schematic diagram of the structure of the second device proposed in an embodiment of this disclosure. The second device is used to perform any of the above methods. In some embodiments, as shown in Figure 8, the second device 800 may include a receiving module 801.

[0186] In some embodiments, the receiving module 801 is used to receive a first wireless frame;

[0187] The first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

[0188] Optionally, the receiving module 801 is used to perform at least one of the sending and receiving steps (e.g., step 501) performed by the second device 102 in any of the above methods, which will not be described in detail here.

[0189] In some embodiments, the receiving module can be interchanged with the transceiver module or transceiver.

[0190] Figure 9 is a schematic diagram of the structure of the communication device 900 proposed in an embodiment of this disclosure. The communication device 900 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 900 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0191] As shown in Figure 9, the communication device 900 is used to execute any of the above methods. In some embodiments, the communication device 900 includes one or more processors 901. The processor 901 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 900 is used to execute any of the above methods. Optionally, one or more processors 901 are used to invoke instructions to cause the communication device 900 to execute any of the above methods.

[0192] In some embodiments, the communication device 900 further includes one or more transceivers 902. When the communication device 900 includes one or more transceivers 902, the transceiver 902 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps 202, 302, 402, 501, but not limited thereto), and the processor 901 performs at least one of other steps (e.g., steps 201, 301, 401, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0193] In some embodiments, the communication device 900 further includes one or more memories 903 for storing data and / or instructions. Optionally, one or more processors 901 are used to invoke instructions stored in the memory 903 to cause the communication device 900 to perform any of the above methods. Optionally, all or part of the memory 903 may also be located outside the communication device 900. In optional embodiments, the communication device 900 may include one or more interface circuits 904. Optionally, the interface circuit 904 is connected to the memory 902, and the interface circuit 904 can be used to receive data and / or instructions from the memory 902 or other devices, and can be used to send data and / or instructions to the memory 902 or other devices. For example, the interface circuit 904 can read data and / or instructions stored in the memory 902 and send the data and / or instructions to the processor 901.

[0194] The communication device 900 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 900 described in this disclosure is not limited thereto, and the structure of the communication device 900 may not be limited by FIG. 9. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0195] Figure 10 is a schematic diagram of the structure of the chip 1000 proposed in an embodiment of this disclosure. For cases where the communication device 900 can be a chip or a chip system, the schematic diagram of the chip 1000 shown in Figure 10 can be referenced, but is not limited thereto.

[0196] Chip 1000 includes one or more processors 1001. Chip 1000 is used to perform any of the above methods.

[0197] In some embodiments, chip 1000 further includes one or more interface circuits 1002. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 1000 further includes one or more memories 1003 for storing data and / or instructions. Optionally, all or part of the memories 1003 may be located outside chip 1000. Optionally, interface circuit 1002 is connected to memory 1003, and interface circuit 1002 can be used to receive data and / or instructions from memory 1003 or other devices, and interface circuit 1002 can be used to send data and / or instructions to memory 1003 or other devices. For example, interface circuit 1002 can read data and / or instructions stored in memory 1003 and send the data and / or instructions to processor 1001.

[0198] In some embodiments, the interface circuit 1002 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps 202, 302, 402, and 501, but not limited thereto). The interface circuit 1002 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 1002 performing data and / or instruction interaction between the processor 1001, the chip 1000, the memory 1003, or the transceiver device. In some embodiments, the processor 1001 performs at least one of other steps (e.g., steps 201, 301, and 401, but not limited thereto).

[0199] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0200] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0201] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0202] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method applied to a first device, characterized in that, The method includes: A first wireless frame is determined; the first wireless frame includes first identification information, which identifies whether the first device supports the 3844-bit codeword length low-density parity-check code (LDPC) data encoding method. Send the first wireless frame.

2. The communication method according to claim 1, characterized by, The first identification information includes at least one of the following: The first identifier bit indicates whether the first device supports LDPC data encoding with a codeword length of 3844 bits; The second flag bit and / or the third flag bit, wherein the second flag bit indicates whether the first device supports receiving LDPC data encoding with a codeword length of 3844 bits; and the third flag bit indicates whether the first device supports sending LDPC data encoding with a codeword length of 3844 bits. The fourth identifier bit indicates whether the first device supports LDPC data encoding with a codeword length of 3844 bits under different operating parameters; the operating parameters include at least one of bandwidth, spatial stream number, resource unit (RU) format, and modulation and coding scheme.

3. The communication method according to claim 1 or 2, characterized by, The first wireless frame includes a first information element and a second information element; The second information element includes a fifth identifier bit, which is set in the high throughput HT information element, the ultra-high throughput VHT information element, and / or the high efficiency HE information element. When the first device supports 1944, 1296, or 648 bit length codeword LDPC data encoding, the first identifier bit in the first information element indicates whether the first device supports 3844 bit length codeword LDPC data encoding in the UHR information element. or The fifth identifier bit is set in the HT information element, VHT information element and / or HE information element, and when the first device does not support LDPC data encoding of 1944, 1296 or 648 bit length codewords, the first identifier bit in the first information element is set as a reserved bit.

4. The communication method according to claim 3, wherein, The first device includes at least one of the following: Mobile access point (AP), site device (STA), multi-link device, and site device (STA) or multi-link site device (non-AP MLD) that only supports 20MHz channel bandwidth.

5. The communication method according to any one of claims 1 to 4, characterized by, The first wireless frame includes a trigger frame, and the first device includes an access point (AP). The first identification information also indicates that the physical layer protocol data unit TB PPDU based on the trigger frame sent by the STA to the AP must use LDPC data encoding with a codeword length of 3844 bits.

6. The communication method according to claim 5, wherein, The physical layer preamble (PHY preamble) of the TB PPDU includes: The sixth identifier bit indicates whether the subsequent part of the TB PPDU uses LDPC data encoding with a codeword length of 3844 bits.

7. The communication method according to any one of claims 1 to 6, characterized by, The method further includes: Send an uplink physical layer protocol data unit (UL PPDU) or a downlink physical layer protocol data unit (DL PPDU); wherein the preamble of the UL PPDU or DL ​​PPDU carries a seventh identifier bit, which indicates whether the payload part and / or data part of the UL PPDU or DL ​​PPDU uses LDPC data encoding with a codeword length of 3844 bits. 8.A communication method applied to a second device, the method comprising: The method includes: Receive a first wireless frame; the first wireless frame includes first identification information, which identifies whether the first device supports LDPC data encoding with a codeword length of 3844 bits.

9. The communication method according to claim 8, wherein, The first wireless frame includes a trigger frame, and the first device includes an access point (AP). The first identification information also indicates that the TB PPDU sent by the second device to the AP must use LDPC data encoding with a codeword length of 3844 bits.

10. The communication method according to claim 9, wherein, The PHY preamble of the TB PPDU includes: The sixth identifier bit indicates whether the subsequent part of the TB PPDU uses LDPC data encoding with a codeword length of 3844 bits.

11. The communication method according to any one of claims 8 to 10, characterized by, The method further includes: Send a UL PPDU or DL ​​PPDU; wherein the preamble of the UL PPDU or DL ​​PPDU carries a seventh identifier bit, the seventh identifier bit indicating whether the payload part and / or data part of the UL PPDU or DL ​​PPDU uses LDPC data encoding with a codeword length of 3844 bits.

12. A communication device, characterized by The communication device is used to perform the communication method according to any one of claims 1 to 7, or claims 8 to 11.

13. A communication system, characterized by Including the first device and the second device; Wherein, the first device determines the first wireless frame; the first wireless frame includes first identification information, the first identification information indicating whether the first device supports LDPC data encoding with a codeword length of 3844 bits; The first wireless frame is sent to the second device.

14. A storage medium, the storage medium storing instructions, wherein, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 7, or performs the communication method as described in any one of claims 8 to 11.

15. A program product comprising at least one of a program, instructions, characterized in that When at least one of the programs or instructions is executed by a communication device, it implements the communication method of any one of claims 1 to 7, or the communication method of any one of claims 8 to 11.

Images