Communication methods and devices

By selecting a suitable reliability sequence based on multiple factors, the problem of determining the reliability sequence of Polar codes in 5G systems has been solved, improving system compatibility and transmission performance, reducing signaling overhead, and optimizing encoding and decoding latency.

CN123074633APending Publication Date: 2026-11-10HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510592202.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-08
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In 5G mobile communication systems, existing Polar codes require longer reliability sequences as communication technology develops. However, existing technologies struggle to reasonably determine the reliability sequence, leading to limitations in system compatibility and transmission performance.

Method used

By selecting a suitable reliability sequence based on factors such as the length information related to the encoding, the parameter type carried in the control information, transmission condition information, terminal capabilities, and physical channel type, a flexible and accurate reliability sequence selection method is provided, which is compatible with existing standards and improves transmission performance.

Benefits of technology

It enables flexible reliability sequence selection under different transmission conditions and terminal capabilities, improves system compatibility and transmission reliability, reduces signaling overhead and optimizes encoding and decoding latency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074633A_ABST
    Figure CN123074633A_ABST
Patent Text Reader

Abstract

A communication method and apparatus are disclosed, capable of reasonably determining a reliability sequence. In this scheme, the communication device can select a first reliability sequence from a set of reliability sequences based on at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capabilities, the type of control information, the type of physical channel, or indication information used to indicate the first reliability sequence. Then, channel coding or channel decoding is performed based on the first reliability sequence. This enables the communication device to select a suitable reliability sequence based on the aforementioned information, thereby improving the rationality and accuracy of the reliability sequence selection, which helps ensure subsequent transmission and thus guarantees communication performance.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0002] Polar codes are a widely used channel coding method in 5G mobile communication systems. Polar codes are linear block codes, and the encoding process can be represented as follows: in, It is a binary vector with a length of N (i.e., code length), G N It is an N×N matrix.

[0003] in, A portion of the bits is used to carry information and is called information bits; the other portion of the bits is set to fixed values ​​predetermined by the transmitting and receiving ends and is called fixed bits or frozen bits. Typically, information bits are... The position of an information bit can be determined using a reliability sequence. For example, if the number of information bits is K, then the K index positions with the highest reliability in the reliability sequence are the positions of the information bits within the sequence. The position in the middle.

[0004] Currently, the reliability sequence used to construct Polar codes is defined in the standard as having a length of 1024. However, with the development of communication technology, longer reliability sequences may be required. Therefore, determining the reliability sequence becomes a pressing issue. Summary of the Invention

[0005] This application provides a communication method and apparatus that can reasonably determine a reliability sequence.

[0006] In a first aspect, a communication method is provided. This method can be executed by a communication device, by a module applied to the communication device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the communication device. For example, the communication device can be a terminal or a wireless access network node. The method includes: selecting a first reliability sequence from a set of reliability sequences based on first information, and performing channel coding or channel decoding based on the first reliability sequence. The set of reliability sequences includes at least two reliability sequences. The first information includes at least one of the following: encoding-related length information, the type of parameters carried in control information, transmission condition information, mother code segmentation information, terminal capabilities, indication information, the type of control information, or the type of physical channel, wherein the indication information indicates the first reliability sequence.

[0007] Based on this scheme, when selecting a reliability sequence, the communication device can consider at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capabilities, control information type, physical channel type, or indication information used to indicate the first reliability sequence. This allows it to select a suitable reliability sequence based on the aforementioned information. For example, it can select a reliability sequence that matches the encoding-related length information, or a reliability sequence that meets the error correction performance requirements corresponding to the parameter carried in the control information, or a reliability sequence that adapts to the channel quality based on the transmission condition information, or a reliability sequence that adapts to the terminal's capabilities based on the terminal's capabilities. This improves the rationality and accuracy of reliability sequence selection, helps ensure subsequent transmission, and thus guarantees communication performance.

[0008] In one possible design, there are at least two reliability sequences of different lengths in the set of reliability sequences.

[0009] Based on this possible design, when there are at least two reliability sequences of different lengths in the reliability sequence set, the communication device can flexibly select different reliability sequences according to different needs, thereby improving the flexibility and rationality of reliability sequence selection.

[0010] In one possible design, the set of reliability sequences includes a second reliability sequence. A subsequence of the second reliability sequence is either a third reliability sequence or a subsequence of the second reliability sequence is a subsequence of the third reliability sequence, and the length of the third reliability sequence is 1024.

[0011] Based on this possible design, existing standards define a reliability sequence of length 1024. In the case where a subsequence of the second reliability sequence is the third reliability sequence, or a subsequence of the second reliability sequence is a subsequence of the third reliability sequence, the reliability sequence set provided in this application can be compatible with the reliability sequences in existing standards, thereby improving system compatibility.

[0012] In one possible design, the encoding-related length information includes at least one of the following: mother code length, net payload bits, sequence length after rate matching, or cyclic redundancy check (CRC) length.

[0013] Based on this possible design, the communication device selects a reliability sequence according to the mother code length, the number of payload bits, the sequence length after rate matching, or the CRC length. Therefore, the selected reliability sequence better adapts to the aforementioned parameters, improving the accuracy of reliability sequence selection. Furthermore, the encoding-related length information is a parameter understood and agreed upon by both the channel encoder and decoder. Therefore, there is no need for explicit signaling between the channel encoder and decoder to indicate the reliability sequence, thereby reducing signaling overhead.

[0014] In one possible design, if the number of payload bits is less than a first payload bit threshold, the length of the first reliability sequence is a first length; or, if the number of payload bits is greater than or equal to the first payload bit threshold and less than a second payload bit threshold, the length of the first reliability sequence is a second length; or, if the number of payload bits is greater than or equal to the second payload bit threshold and less than a third payload bit threshold, the length of the first reliability sequence is a third length; or, if the number of payload bits is greater than or equal to the third payload bit threshold and less than a fourth payload bit threshold, the length of the first reliability sequence is a fourth length.

[0015] Based on this possible design, when the number of payload bits is less than the first payload bit threshold, a shorter reliability sequence (i.e., the first length) is selected for channel coding or decoding. The corresponding mother code length is also shorter. While satisfying error correction performance, a smaller code length can be maintained, reducing resource overhead. Subsequently, as the number of payload bits increases, the length of the reliability sequence and the mother code length can be appropriately and reasonably increased to maintain the code rate / error correction performance unchanged or to allow it to fluctuate within a certain range, thereby maintaining transmission performance.

[0016] In one possible design, the first payload bit threshold, the second payload bit threshold, the third payload bit threshold, or the fourth payload bit threshold is determined based on the difference between 1024 and the CRC length.

[0017] Based on this possible design, the reliability sequence can be selected by combining the CRC length, which can better adapt to the encoding / decoding of the net payload bits of the concatenated CRC code, or better adapt to the encoding / decoding of Polar code based on CRC-Aided Polar code, thereby improving the performance of channel coding / decoding.

[0018] In one possible design, the second payload bit threshold is 2 times the first payload bit threshold. n1 The third payload bit threshold is twice the first payload bit threshold. n2 The fourth payload bit threshold is twice the first payload bit threshold. n3The multiples of n2, n2 is greater than n1, n3 is greater than n2, and n1, n2, and n3 are positive integers greater than or equal to 1.

[0019] In one possible design, if the length of the sequence after rate matching is less than a first rate matching length threshold, the length of the first reliability sequence is a first length; or, if the length of the sequence after rate matching is greater than or equal to the first rate matching length threshold and less than a second rate matching length threshold, the length of the first reliability sequence is a second length; or, if the length of the sequence after rate matching is greater than or equal to the second rate matching length threshold and less than a third rate matching length threshold, the length of the first reliability sequence is a third length; or, if the length of the sequence after rate matching is greater than or equal to the third rate matching length threshold and less than a fourth rate matching length threshold, the length of the first reliability sequence is a fourth length.

[0020] Based on this possible design, selecting the reliability sequence according to the sequence length after rate matching can better adapt to the number of encoded bits that time-frequency resources can carry. For example, it can avoid selecting a long reliability sequence, which would result in a number of encoded bits that is much greater than the number of encoded bits that time-frequency resources can carry, thus causing more bits to be discarded when performing puncturing operations during rate matching; or, it can avoid selecting a short reliability sequence, which would result in a number of encoded bits that is much less than the number of encoded bits that time-frequency resources can carry, thus wasting time-frequency resources.

[0021] In one possible design, the type of control information includes primary control information or secondary control information; or, the type of control information is broadcast control information.

[0022] In one possible design, when the control information is of the first-level control type, the length of the first reliability sequence is a first length; when the control information is of the second-level control type, the length of the first reliability sequence is a second length. Wherein, the control information is uplink control information, downlink control information, or sidelink control information, and the second length is greater than or equal to the first length.

[0023] Based on this possible design, choosing a shorter reliability sequence for the primary control information, or in other words, choosing a reliability sequence from the existing standard, is beneficial for system compatibility and can adapt to low-capability terminals. Choosing a longer reliability sequence for the secondary control information allows for the transmission of longer control information and adapts to higher-order modulation.

[0024] In one possible design, where the control information is uplink control information and the uplink control information is first-level uplink control information, the length of the first reliability sequence is greater than or equal to 1024.

[0025] Based on this possible design, for Level 1 uplink control information, when using a longer reliability sequence, the length of the Level 1 uplink control information can be increased, supporting the encoding of longer Level 1 uplink control information.

[0026] In one possible design, where the type of control information is broadcast control information, the length of the first reliability sequence is greater than or equal to 1024.

[0027] Based on this possible design, since the length of the reliability sequence in the existing standard is 1024, choosing a reliability sequence of length 1024 for the broadcast control information can adapt to existing terminals, such as existing low-capability terminals (e.g., terminals with poor channel coding / decoding capabilities), thus improving system compatibility. Choosing a reliability sequence longer than 1024 for the broadcast control information can support channel coding for larger broadcast control information. Furthermore, due to the longer reliability sequence, reliability requirements can be met even when the number of bits in the broadcast control information is large.

[0028] In one possible design, the type of control information includes control information carried on a control channel or control information carried on a data channel. If the control information is carried on a data channel, the length of the first reliability sequence is a first length; or, if the control information is carried on a control channel, the length of the first reliability sequence is a second length, where the second length is greater than or equal to the first length.

[0029] Based on this possible design, the control information carried in the data channel may be control information that needs to be transmitted in a timely manner. For example, uplink control information (UCI) that requires timely feedback may need to be transmitted along with the data (i.e., carried in the physical uplink shared channel (PUSCH)). Therefore, for control information carried in the data channel, choosing a shorter reliability sequence, compared to choosing a longer reliability sequence, can reduce the channel coding or decoding delay, thereby meeting the transmission delay requirements of the control information. For control information carried in the control channel, choosing a longer reliability sequence, compared to choosing a shorter reliability sequence, can improve error correction performance and reliability.

[0030] In one possible design, the control information is carried on a data channel, and when there is no data transmission on the data channel, the length of the first reliability sequence is greater than or equal to 1024.

[0031] Based on this possible design, since there is no data transmission on the data channel, a larger amount of control information (such as a larger UCI payload) can be transmitted on the data channel. In this case, using a longer reliability sequence can achieve better error correction performance and improve reliability for this control information compared to choosing a shorter reliability sequence.

[0032] In one possible design, the parameters carried in the control information include either a first type of parameter or a second type of parameter, and the lengths of the first type of parameter and the second type of parameter are different. Specifically, if the parameters carried in the control information are of the first type, the length of the first reliability sequence is a first length; or, if the parameters carried in the control information are of the second type, the length of the first reliability sequence is a second length, and the second length is greater than or equal to the first length.

[0033] Based on this possible design, a reliability sequence can be selected according to the length of the parameters carried in the control information. For example, when the parameters carried in the control information are short, a shorter reliability sequence is selected to minimize the encoding length while satisfying error correction performance, thereby reducing encoding and decoding latency. When the parameters carried in the control information are long, a longer reliability sequence is selected to satisfy the error correction performance of the control information and improve reliability. In other words, it can meet the error correction performance requirements of parameters of different lengths carried in the control information.

[0034] In one possible design, the transmission condition information includes at least one of the following: channel quality, modulation and coding scheme (MCS) index, code rate, modulation order, spectral efficiency, number of retransmissions in hybrid automatic repeat request (HARQ), or link direction.

[0035] Based on this possible design, a reliability sequence that is more adapted to the transmission condition information can be selected. Furthermore, in the event of changes in the transmission condition information, both communicating parties can adjust the reliability sequence in a timely manner, achieving adaptive adjustment of the reliability sequence.

[0036] In one possible design, if the channel quality is greater than a first channel quality threshold, the length of the first reliability sequence is a first length; or, if the channel quality is less than or equal to the first channel quality threshold and greater than or equal to a second channel quality threshold, the length of the first reliability sequence is a second length; or, if the channel quality is less than the second channel quality threshold, the length of the first reliability sequence is a third length.

[0037] Based on this possible design, a reliability sequence can be rationally selected according to channel quality. For example, if the channel quality is greater than the first channel quality threshold, the channel quality can be considered relatively good, and a shorter reliability sequence can meet the error correction requirements. Therefore, compared to using a longer reliability sequence, the encoding and decoding length can be reduced, thereby reducing encoding and decoding latency. If the channel quality is greater than or equal to the second channel quality threshold but less than or equal to the first channel quality threshold, the channel quality can be considered moderate, and a slightly longer reliability sequence can be used to meet the error correction requirements. If the channel quality is less than the second threshold, the channel quality can be considered poor, and in this case, a longer reliability sequence can meet the error correction requirements and ensure transmission reliability.

[0038] In one possible design, if the MCS index belongs to a first index range, the length of the first reliability sequence is a first length; or, if the MCS index belongs to a second index range, the length of the first reliability sequence is a second length; or, if the MCS index belongs to a third index range, the length of the first reliability sequence is a third length. Wherein, the smallest MCS index in the second index range is greater than the largest MCS index in the first index range, and the smallest MCS index in the third index range is greater than the largest MCS index in the second index range.

[0039] Based on this possible design, when the MCS index falls within the first index range, the corresponding modulation order is low (e.g., modulation order 2), the modulation scheme is QPSK, and the corresponding spectral efficiency requirement is low, thus the reliability requirement is low. Therefore, a shorter reliability sequence can be used to reduce encoding and decoding latency while meeting reliability requirements. When the MCS index falls within the second index range, the corresponding modulation order is medium (e.g., modulation order 4), the modulation scheme is 16QAM, and the corresponding spectral efficiency requirement is relatively higher, thus the reliability requirement is also relatively higher. Therefore, a relatively longer reliability sequence can be used to meet the reliability requirements. When the MCS index falls within the third index range, the corresponding modulation order is high (e.g., modulation order 6), the modulation scheme is 64QAM, and the corresponding spectral efficiency requirement is high, thus the reliability requirement is high. In this case, using a longer reliability sequence can meet the reliability requirements and ensure transmission reliability.

[0040] In one possible design, if the number of HARQ retransmissions is greater than a first retransmission threshold and less than or equal to a second retransmission threshold, the length of the first reliability sequence is a first length; or, if the number of HARQ retransmissions is greater than a second retransmission threshold and less than or equal to a third retransmission threshold, the length of the first reliability sequence is a second length, which is greater than the first length.

[0041] Based on this possible design, if the number of HARQ retransmissions falls between the first and second retransmission thresholds, the channel quality can be considered relatively good. Therefore, a shorter reliability sequence can be used to reduce encoding / decoding latency while maintaining error correction performance. Conversely, if the number of HARQ retransmissions falls between the second and third retransmission thresholds, the channel quality can be considered relatively poor. In this case, a longer reliability sequence can meet reliability requirements and ensure transmission reliability.

[0042] In one possible design, if the link direction is uplink, the length of the first reliability sequence is the second length; or, if the link direction is downlink, the length of the first reliability sequence is the first length, and the second length is greater than or equal to the first length.

[0043] Based on this possible design, for the downlink direction, a shorter reliability sequence is adopted, such as the existing standard reliability sequence of length 1024, or a slightly longer one (e.g., a reliability sequence of length 2048). This can accommodate the weaker processing capabilities of the terminal, and the shorter reliability sequence can reduce the complexity of encoding and decoding, increase the encoding and decoding rate, and reduce encoding and decoding latency. For the uplink direction, a longer reliability sequence is adopted, such as a reliability sequence of length 2048, 4096, or 8192. This can utilize the stronger processing capabilities of the RAN nodes to obtain long code gain, improve error correction capabilities, and achieve more complete polarization.

[0044] In one possible design, the second length is twice the length of the first length. m1 Double, or the third length is twice the length of the first. m2 Double, or the fourth length is twice the length of the first. m3 The multiples of 1, m2 is greater than m1, m3 is greater than m2, and m1, m2, and m3 are positive integers greater than or equal to 1.

[0045] In one possible design, the mother code segmentation information includes the segment index of the mother code, which corresponds to at least one of the following: the number of segments of the mother code, or the length of the reliability sequence corresponding to each segment.

[0046] Based on this possible design, a suitable reliability sequence can be selected according to the segmentation of the mother code, thus better adapting to scenarios based on long segments of the mother code.

[0047] In one possible design, where the communication device is a terminal, and the first information includes indication information, the method further includes: sending first capability information to a wireless access network node, wherein the first capability information indicates at least one of the following: the maximum number of supported reliability sequences, the maximum supported code length, or the length of the supported reliability sequences in a first scenario.

[0048] Based on this possible design, the terminal indicates its capabilities to the RAN node, enabling the RAN node to reasonably select a reliability sequence based on the terminal's capabilities. This avoids selecting a reliability sequence that the terminal does not support or exceeds its capabilities, improving the accuracy of reliability sequence selection and preventing transmission failures caused by unreasonable reliability sequence selection.

[0049] In one possible design, the method further includes sending second capability information to the radio access network node, the second capability information indicating support for the selection or configuration of a reliability sequence.

[0050] In one possible design, the method further includes receiving indication information from a radio access network node, the indication information including an index of a first reliability sequence.

[0051] Based on this possible design, the terminal can select a reliability sequence based on the indication information of the RAN node, which can reduce the complexity of the terminal in selecting a reliability sequence, thereby reducing the power consumption of the terminal and the capability requirements of the terminal.

[0052] In one possible design, where the communication device is a wireless access network node and the first information includes indication information, the method further includes: receiving first capability information from a terminal, the first capability information indicating at least one of the following: the maximum number of supported reliability sequences, the maximum supported code length, or the length of the supported reliability sequences in a first scenario.

[0053] In one possible design, the method further includes receiving second capability information from the terminal, the second capability information indicating the selection or configuration of a reliability sequence.

[0054] In one possible design, the method further includes sending indication information to the terminal, the indication information including an index of the first reliability sequence.

[0055] In one possible design, the physical channel can be either a control channel or a data channel. If the physical channel is a control channel, the length of the first reliability sequence is a first length; or, if the physical channel is a data channel, the length of the first reliability sequence is a second length, which is greater than or equal to the first length.

[0056] Secondly, a communication device is provided for implementing various methods. The communication device includes modules, units, or means corresponding to the implementation of the methods, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0057] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

[0058] In some possible designs, the transceiver module can consist of transceiver circuits, transceivers, transceivers, or communication interfaces.

[0059] Thirdly, a communication device is provided, comprising: a processor and a memory; the memory being used to store computer instructions that, when executed by the processor, cause the communication device to perform the method described in either aspect.

[0060] Fourthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute computer programs or instructions to cause the communication device to perform the method described in any one of these aspects.

[0061] Fifthly, a communication device is provided, comprising: at least one processor; said processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the method described in any of the aspects. The memory may be coupled to the processor, or may be independent of the processor.

[0062] In a sixth aspect, a communication device (e.g., the communication device may be a chip or a chip system) is provided, the communication device including a processor for implementing the functions involved in any of the first aspects.

[0063] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0064] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0065] It is understood that the communication devices provided in the second to sixth aspects may be the communication devices in the first aspect, or modules or units (e.g., chips, chip systems, or circuits) in the communication devices that perform the methods / operations / steps / actions described in the first aspect, or modules or units that can be matched with the communication devices, or logic nodes, logic modules, or software that can realize all or part of the functions of the communication devices.

[0066] In a seventh aspect, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any of the first aspects.

[0067] In an eighth aspect, a computer program product containing instructions is provided that, when run on a communication device, enables the communication device to perform the method described in any of the first aspects.

[0068] A ninth aspect provides a communication system comprising a communication device. The communication device is used to perform the method described in the first aspect and any possible design thereof.

[0069] The technical effects of any of the design methods in aspects two through nine can be found in the technical effects of different design methods in aspect one, and will not be repeated here. Attached Figure Description

[0070] Figure 1 A schematic diagram of a fence provided for this application;

[0071] Figure 2 A schematic diagram of the structure of a communication system provided in this application;

[0072] Figure 3 A schematic diagram of an ORAN system architecture provided in this application;

[0073] Figures 4-5 A schematic diagram of the protocol layer architecture of a CU-DU provided in this application;

[0074] Figure 6 A flowchart illustrating a communication method provided in this application;

[0075] Figure 7 A schematic diagram illustrating the interaction process between a terminal and a RAN node regarding capability information, provided in this application;

[0076] Figure 8 A flowchart illustrating another communication method provided in this application;

[0077] Figures 9-11 This is a schematic diagram of the structure of a communication device provided in this application. Detailed Implementation

[0078] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0079] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0080] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0081] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0082] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0083] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0084] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0085] Polar codes are a coding scheme based on channel polarization, and are a channel coding method that can be rigorously proven to "achieve" channel capacity. At different code lengths, especially for finite code lengths, Polar codes outperform Turbo codes and low-density parity-check (LDPC) codes. Furthermore, Polar codes have lower computational complexity in encoding and decoding. These advantages have led to the widespread application of Polar codes in communication systems.

[0086] Polar codes are linear block codes, and their encoding process can be represented as follows: in, It is a binary vector with a length of N (i.e., code length), G N It is an N×N generating matrix. For example, in, n = log2(N), It is the Kronecker product of n matrices N2.

[0087] in, A portion of the bits is used to carry information and is called information bits (also known as information digits). The other portion of the bits consists of fixed values ​​agreed upon beforehand by the transmitting and receiving ends; therefore, this other portion of bits can be called fixed bits (also known as frozen bits, fixed bits, or frozen digits). The set of indices for the information bits can be denoted as... The set of fixed-bit indices can be denoted as supplement

[0088] Polar codes can be encoded using, for example... Figure 1 The fence diagram shown is used for encoding. (like The fixed bits and information bits are placed on the leftmost bit position (i.e., the input bit position) of the fence diagram, and an n-order butterfly operation is performed sequentially from left to right to obtain the rightmost output bit of the fence diagram. (like See also Figure 1 u8,u 11 ,u 12 ,u 13 ,u14 ,u 15 ,u 16 All of these are information bits, therefore the bit positions they occupy are all information bits: u1, u2, u3, u4, u5, u6, u7, u9, u 10 All of them are fixed bits, so the bit position they occupy is a fixed bit.

[0089] The key problem in constructing Polar codes is determining the index set of information bits. In the early stages of theoretical research, the set The polarization channel error probability corresponding to bit i is usually determined as follows: First, the polarization channel error probability is obtained using methods such as density evolution or Gaussian analysis. Select the smallest K The sets are composed of the indices corresponding to the values. However, this method requires calculating different methods for different channel conditions. In other words, this is a channel-dependent method of determination. Because channels are highly variable in real-world scenarios, this method is difficult to apply in practice.

[0090] Further research shows that the index set of information bits can be determined using a sequence (also known as a reliability sequence or Polar sequence). Specifically, this sequence uses polarization channel numbers to represent the order in which information bits are selected, in the construction of the set. At that time, K sub-channel numbers can be read from back to front as a set. The elements in the set. K is the number of information bits. This method is easier to implement and is also used in 5G mobile communication systems to determine the set.

[0091] For example, the 5G standard predefines a reliability sequence of length 1024. Each element in this reliability sequence... and its corresponding reliability As shown in Table 1. Here, i can be understood as the index of an element in the reliability sequence, and its value ranges from [0, N]. max -1]. N max This can be understood as the maximum code length, or the maximum length of the reliability sequence.

[0092] Table 1

[0093]

[0094]

[0095]

[0096]

[0097] Table 1 (continued)

[0098]

[0099]

[0100]

[0101]

[0102] In Table 1, According to its corresponding reliability Arranged in ascending order, for example, When the value is 0, the reliability is the lowest, and correspondingly... The reliability is highest when the value is 1023, and correspondingly... When the value is 1022, the reliability is the second highest, and correspondingly... When the value is 1021, the corresponding reliability ranks third from high to low. When the value is 1019, the corresponding reliability ranks fourth from high to low. And so on, without going into further detail.

[0103] For example, the order of reliability can also be understood as the order in which information bits are selected; the higher the reliability, the higher the corresponding reliability. The higher the priority, the more likely it is to be selected as an information bit. For example, taking a code length of 1024 and an information bit count K of 128 as an example, then this information bit is located in When taking 896 to 1023, the corresponding The location; or rather, it can be read from Table 1 from the end to the beginning of 128. As a set

[0104] With the development of communication systems, the application scope of Polar codes is expected to expand further, potentially requiring the introduction of longer reliability sequences. At this point, determining the reliability sequence becomes a pressing issue. For example, as a possible implementation, multiple reliability sequences of various lengths may exist, and the communication device needs to determine the appropriate reliability sequence from among them.

[0105] Based on this, this application provides a communication method in which a communication device selects a reliability sequence from a set of reliability sequences based on at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capability information, the type of control information, and the type of physical channel. The method provided in this application will be described in detail in subsequent embodiments and will not be repeated here.

[0106] The technical solutions of this application embodiment can be used in various communication systems, including 3GPP communication systems such as 4th generation (4G) systems (e.g., Long Term Evolution (LTE) systems), 5G systems (e.g., New Radio (NR) systems), LTE and 5G hybrid networking systems, non-terrestrial networks (NTN), device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, machine-type communication (MTC) systems, Internet of Things (IoT) systems, or other future communication systems. The communication system can also be a non-3GPP communication system; there is no limitation on this.

[0107] The communication systems described above are merely illustrative examples, and are not limited to those described herein. The communication systems provided in this application do not impose any limitations on the solutions described herein. This will be explained uniformly here and will not be repeated below.

[0108] Figure 2 A possible, non-limiting system schematic diagram is shown. For example... Figure 2 As shown, the communication system 20 includes a radio access network (RAN) 200 and a core network (CN) 300. The RAN 200 includes at least one RAN node (e.g., Figure 2 210a and 210b (collectively referred to as 210) and at least one terminal (such as Figure 2 RAN 200, denoted as 220a-220j, is collectively referred to as 220. RAN 200 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 2(Not shown in the image). Terminal 220 is connected to RAN node 210 wirelessly. RAN node 210 is connected to core network 300 wirelessly or via wired connection. The core network equipment in core network 300 and RAN node 210 in RAN 200 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0109] RAN 200 can be a 3GPP-related cellular system, such as a 4G, 5G mobile communication system, or a future-oriented evolution system. RAN 200 can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 200 can also be a communication system that integrates two or more of the above systems.

[0110] As one possible implementation, the communication system 20 provided in this application may further include artificial intelligence (AI) network elements to implement some or all AI-related operations. AI network elements can also be referred to as AI nodes, AI devices, AI entities, AI modules, AI models, or AI units, etc. The AI ​​network elements may be built into the network elements of the communication system. For example, an AI network element may be an AI module built into: access network equipment, core network equipment, cloud server, or operation, administration, and maintenance (OAM) to implement AI-related functions. The OAM may act as the network management system for core network equipment and / or access network equipment. Alternatively, the AI ​​network element may also be a network element independently set up in the communication system. Optionally, the terminal or its built-in chip may also include an AI entity to implement AI-related functions.

[0111] Terminals include handheld devices and vehicle-mounted devices with wireless connectivity. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as D2D, V2X communication, MTC, IoT, virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, intelligent transportation, and smart cities. For example, terminals can be: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, smart glasses, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, point of sale (POS) machines, customer-premises equipment (CPE), light user equipment (UE), reduced capability user equipment (REDCAP UE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as smart robots, hot air balloons, drones, airplanes), etc. Terminal devices can also be vehicle-mounted devices (such as vehicle-mounted devices, vehicle-mounted modules, vehicle-mounted chips, on-board units (OBUs), or telematics boxes (T-BOXs)). Terminal devices can also be other devices with terminal functions; for example, a terminal device can also be a device that performs terminal functions in D2D communication.

[0112] The embodiments of this application do not limit the device form of the terminal. The device for implementing the functions of the terminal can be a terminal device; it can also be a device that supports the terminal device in implementing the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device.

[0113] In this embodiment, the chip system may consist of chips or include chips and other discrete devices. All or part of the functions of the terminal device in this application may also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform).

[0114] RAN node 210, sometimes also called access network node, RAN entity, or access node, constitutes part of the communication system and helps terminals achieve wireless access. Multiple RAN nodes 210 in communication system 20 can be of the same type or different types. In some scenarios, the roles of RAN node 210 and terminal 220 are relative, for example... Figure 2 Network element 220i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminal 220j accessing RAN 200 via network element 220i, network element 220i is a base station; however, for network element 210a, network element 220i is a terminal. RAN node 210 and terminal 220 are sometimes referred to as communication devices, for example... Figure 2 Network elements 210a and 210b can be understood as communication devices with base station functions, while network elements 220a-220j can be understood as communication devices with terminal functions.

[0115] In one possible scenario, the RAN node can be an access network device, such as a base station, an evolved NodeB (eNodeB), an access point (AP), a TRP, a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. Access network devices can also be macro base stations (e.g.,...). Figure 2 210a), micro base stations or indoor stations (such as Figure 2 The access network device can be a relay node or donor node (as described in section 210b), or a wireless controller in a CRAN scenario. Optionally, the access network device can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the access network device functions.

[0116] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node implementing a portion of the access network equipment's functions. For example, a RAN node can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0117] In different systems, CU, DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, and RU may also be called O-RU. For ease of description, this application uses CU, DU, and RU as examples. Any of the units in CU, DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0118] For example, such as Figure 3 The diagram shown illustrates a possible, non-limiting O-RAN system. In this system, the CU, DU, and RU cooperate to assist the terminal in achieving radio access. The CU, DU, and RU can be included in the access network equipment, and the CU and DU can be included in the BBU of the access network equipment.

[0119] See Figure 3 Access network devices communicate with core network devices via backhaul links and with terminals via air interfaces. Specifically, the BBU (Browser Unit) of an access network device communicates with the core network device via the backhaul link, and the RU (Remote Root Unit) of the access network device communicates with at least one terminal device via the air interface. The BBU communicates with at least one RU via a fronthaul link, and the CU (Core Unit) communicates with at least one DU (Device Root Unit) via a midhaul link. The BBU and RU can be co-located or not.

[0120] As one possible implementation, the CU and DU respectively implement some of the protocol layer functions of the access network device. For example, some protocol layer functions are implemented in the CU, and the remaining or all protocol layer functions are implemented in the DU. The CU can control one or more DUs.

[0121] For example, such as Figure 4 As shown, the CU can deploy the radio resource control (RRC) layer, the service data adaptation protocol (SDAP) layer, and the packet data convergence protocol (PDCP) layer. In other words, the CU can be understood as a logical node carrying the RRC, SDAP, and PDCP layers of the access network equipment. Therefore, the CU has the processing capabilities of the RRC, PDCP, and SDAP layers. Of course, the CU can also implement or carry other control functions. Similarly, the DU can deploy the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer. In other words, the DU can be understood as a logical node carrying the RLC, MAC, and PHY layers. Therefore, the DU has the processing capabilities of the RLC, MAC, and PHY layers. Of course, the DU can also implement or carry other functions.

[0122] Optionally, the CU connects to network nodes such as the core network through interfaces, which may be interfaces such as the N2 interface. Furthermore, the CU can also implement some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the RLC layer and lower layers) through interfaces, which may be interfaces such as the F1 interface. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). For example, F1 supports control plane functions through F1-C and user plane functions through F1-U.

[0123] In one example, the CU may include a CU control plane (CU-CP) and a CU user plane (CU-UP). For example... Figure 5As shown, CU-CP can be understood as a logical node carrying the RRC layer and the PDCP control plane (PDCP control plane part of PDCP, PDCP-C), used to implement the control plane functions of the CU. CU-CP can communicate with DU through F1-C. CU-UP can be understood as a logical node carrying the SDAP layer and the PDCP user plane (PDCP user plane part of PDCP, PDCP-U), used to implement the user plane functions of the CU. CU-UP can communicate with DU through F1-U.

[0124] The functional division of CU and DU described above is merely an example and does not constitute a limitation on CU and DU. Furthermore, the functions of CU and DU can be configured as needed. For example, CU or DU can be configured as a node with more protocol layer functions, or as a node with partial protocol layer processing functions. For instance, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. As another example, the functions of CU or DU can be divided according to service type or other system requirements, such as by latency, placing functions that need to meet low latency requirements in the DU and functions that do not need to meet such latency requirements in the CU.

[0125] For example, in some examples, the CU may not carry the PDCP layer, i.e., it may only carry the RRC layer. CU-CP may not carry PDCP-C, CU-UP may not carry PDCP-U, or CU-UP may not exist. In other examples, the DU may not carry the RLC layer. Furthermore, it is also possible to have only the DU without a CU.

[0126] As one possible implementation, the DU and RU can cooperate to implement the functions of the PHY layer. For example, the DU can deploy the RLC layer, MAC layer, and higher physical layer (Higher PHY). The RU can deploy the lower physical layer (Lower PHY) and radio frequency (RF) processing functions. The DU can control at least one RU, and the DU and RU can communicate via a fronthaul interface. The DU and RU can be co-located or not.

[0127] The higher physical layer is closer to the MAC layer, and its functions may include at least one of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, modulation / demodulation, etc. The lower physical layer is closer to the mid-RF side, and its functions may include at least one of the following: fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), digital beamforming, and filtering, etc.

[0128] The functional division of DU and RU described above is merely an example and does not constitute a limitation on DU and RU. The functions of DU and RU can be configured in various ways depending on the design. For example, DU can be configured to implement baseband functions, and RU can be configured to implement radio frequency functions, etc.

[0129] As one possible implementation, the O-RAN system may also include a non-realtime ran intelligent controller (Non-RT RIC or NRT RIC) and / or a near-real time ran intelligent controller (Near-RT RIC or nRT RIC).

[0130] Non-RT RIC is used to implement non-real-time intelligent management of the RAN, enabling AI / machine learning (ML) including model training and updates, and guiding applications / functions within the Near-RT RIC based on policies. Near-RT RIC is used to implement near real-time intelligent management of the RAN, achieving near real-time control and optimization of O-RAN modules and resources through data collection and related operations on the E2 interface. The E2 interface can be understood as an open interface between two nodes (or endpoints).

[0131] It should be noted that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0132] The following is combined Figure 2The system shown uses the interaction between a terminal and a RAN node as an example to describe the communication method provided in the embodiments of this application. It should be noted that in the following embodiments of this application, the message names, parameter names, or information names between various devices are just examples, and other names may be used in other embodiments. The method provided in this application does not specifically limit these names.

[0133] It is understood that in the embodiments of this application, each device may perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the operations in the embodiments of this application.

[0134] It is understood that, unless otherwise specified, the same or similar parts between the various embodiments in this application may be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced mutually. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0135] It is understood that this application uses a terminal and a RAN node as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the terminal in this application can also be executed by a module applied to the terminal (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the terminal's functions; similarly, the method executed by the RAN node can also be executed by a module applied to the RAN node (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the RAN node's functions.

[0136] First, this application provides a communication method, such as Figure 6 As shown, the communication method may include the following steps:

[0137] S601, The communication device selects a first reliability sequence from the set of reliability sequences based on the first information.

[0138] The first information includes at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capabilities, indication information, the type of control information, or the type of physical channel. This indication information indicates the first reliability sequence.

[0139] As one possible implementation, the communication device can act as a channel coder (or data sender), or it can act as a channel decoder (or data receiver).

[0140] For example, the communication device can be a terminal or a RAN node. When the communication device is a terminal, the other device communicating with the communication device can be a RAN node or another terminal; when the communication device is a RAN node, the other device communicating with the communication device can be a terminal.

[0141] In other words, in the embodiments of this application, the channel coder can be a terminal, and correspondingly, the channel decoder can be a RAN node or another terminal; or, the channel coder can be a RAN node, and correspondingly, the channel decoder can be a terminal.

[0142] The reliability sequence set includes at least two reliability sequences. For example, the reliability sequence set may also have other names, such as a reliability sequence group, etc., without limitation.

[0143] It should be noted that the reliability sequence set is a concept introduced for ease of description. In practical applications, the concept of a reliability sequence set may not exist. In this case, step S601 can also be understood as: the communication device selects a first reliability sequence from at least two reliability sequences based on the first information, and the "reliability sequence set" in subsequent embodiments of this application can be replaced with "at least two reliability sequences".

[0144] As one possible implementation, the set of reliability sequences contains at least two reliability sequences of different lengths. For example, the length of any reliability sequence in the set of reliability sequences can be 2. n n is a positive integer greater than 1, such as n equal to 8, 9, 10, 11, 12, 13, or 14, etc.

[0145] For example, the set of reliability sequences includes at least one of the following: a reliability sequence of length 2048, a reliability sequence of length 4096, or a reliability sequence of length 8192. For instance, it may include four reliability sequences of lengths 1024, 2048, 4096, and 8192, or it may include two reliability sequences of lengths 1024 and 8192.

[0146] It should be noted that, since the length of the final reliability sequence used in the channel coding process is determined by the length of the mother code (which can be simply referred to as the code length), and this final reliability sequence may be a subsequence of a certain reliability sequence in the reliability sequence set, therefore, in the embodiments of this application, unless otherwise specified, the length of the reliability sequence can be understood as the maximum length of the reliability sequence. The subsequence of the sequence may or may not include the sequence itself.

[0147] It is understood that in this application, the mother code can be understood as the bits (or codewords or codeword bits) before rate matching after channel coding (such as Polar coding). Correspondingly, the mother code length can be understood as the length (or size or number) of the bits (or codewords or codeword bits) before rate matching after channel coding (such as Polar coding). The mother code length is a power of 2. This is a unified explanation here, and will not be repeated in subsequent embodiments.

[0148] As one possible implementation, the set of reliability sequences includes a second reliability sequence. A subsequence of the second reliability sequence is a third reliability sequence, or a subsequence of the second reliability sequence is a subsequence of the third reliability sequence. For example, the length of the third reliability sequence is 1024. For instance, the third reliability sequence is the reliability sequence shown in Table 1 above.

[0149] For example, if a subsequence of the second reliability sequence is the third reliability sequence, and this subsequence is the second reliability itself, then the second reliability can be understood as the third reliability sequence. Alternatively, if the subsequence of the second reliability sequence does not include the second reliability sequence itself, in addition to the above implementation, the second reliability sequence can also be a reliability sequence of length 1024, such as the reliability sequences shown in Table 1 above. In this case, it can be considered that the set of reliability sequences includes a reliability sequence of length 1024, which can be as shown in Table 1, thus being compatible with reliability sequences in existing standards and improving system compatibility.

[0150] As one possible implementation, the set of reliability sequences includes at least two non-nested reliability sequences. Non-nested reliability sequences can be understood as one reliability sequence not being a subsequence of the other. For example, if the set of reliability sequences includes four sequences of lengths 1024, 2048, 4096, and 8192, and these four sequences cannot be nested, then the reliability sequence of length 1024 is not a subsequence of the other three, the reliability sequence of length 2048 is not a subsequence of either the reliability sequence of length 4096 or 8192, and the reliability sequence of length 4096 is not a reliability sequence of length 8192.

[0151] Furthermore, specific subsequences of different reliability sequences can be the same. These specific subsequences refer to particularly short subsequences, such as subsequences with a length less than or equal to 32 or less than or equal to 16. That is, in reliability sequences of lengths 1024, 2048, 4096, and 8192, the subsequences with a length less than or equal to 32 or 16 are identical. This is because when the length of the reliability sequence is particularly short, the order of the reliability sequences is fixed.

[0152] As one possible implementation, the reliability sequence can be represented in tabular form. The format of this table can be the same as or similar to Table 1, meaning the table can display the elements of the reliability sequence. and its corresponding reliability The correspondence is as follows. Accordingly, the above-mentioned set of reliability sequences can be represented as multiple reliability sequence tables, among which there are reliability sequence tables of the same or different lengths. Of course, reliability sequences can be represented in other forms, such as in the form of key-value pairs, where a key-value pair can be an element in the reliability sequence and its corresponding reliability. The form in which the reliability sequences are represented in this application is not specifically limited.

[0153] For example, when the reliability sequence is represented in tabular form, the reliability sequence can also be called a reliability sequence table or a reliability table, etc. In this case, the maximum length of the reliability sequence can also be understood as: the maximum length of the reliability sequence table, the maximum length supported by the reliability table, the maximum length of the reliability table, or the maximum length supported by the reliability table.

[0154] The implementation of the first information and the selection of the first reliability sequence by the communication device based on the first information will be described in subsequent embodiments and will not be repeated here.

[0155] S602, The communication device performs channel coding or channel decoding according to the first reliability sequence.

[0156] In this scenario, when the communication device acts as the channel coder, it performs channel coding based on a first reliability sequence; when the communication device acts as the channel decoder, it performs channel decoding based on the first reliability sequence. Furthermore, channel decoding can also be understood as channel decoding, and the two are interchangeable.

[0157] In one possible implementation, the communication device performs channel coding or channel decoding based on a first reliability sequence. This can be understood as the communication device performing channel coding or channel decoding based on a subsequence of the first reliability sequence. The subsequence of the first reliability sequence may or may not include the first reliability sequence itself. The following explanation uses the example where the subsequence of the first reliability sequence does not include the first reliability sequence itself.

[0158] As one possible implementation, the length of the first reliability sequence is greater than or equal to the length of the mother code. When the length of the first reliability sequence is equal to the length of the mother code, the communication device performs channel coding or channel decoding based on the first reliability sequence itself; when the length of the first reliability sequence is greater than the length of the mother code, after selecting the first reliability sequence, the communication device can select a sub-sequence with a length equal to the length of the mother code from the first reliability sequence, and perform channel coding or channel decoding based on the sub-sequence.

[0159] For example, when a communication device acts as a channel coder, it can determine the bit sequence to be encoded based on a first reliability sequence or a subsequence of the first reliability sequence. And according to Channel coding is performed, where, G is the encoded bit sequence. N This is the encoding matrix.

[0160] Based on this scheme, when selecting a reliability sequence, the communication device can consider at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capabilities, control information type, physical channel type, or indication information used to indicate the first reliability sequence. This allows it to select a suitable reliability sequence based on the aforementioned information. For example, it can select a reliability sequence that matches the encoding-related length information, or a reliability sequence that meets the error correction performance requirements corresponding to the parameter carried in the control information, or a reliability sequence that adapts to the channel quality based on the transmission condition information, or a reliability sequence that adapts to the terminal's capabilities based on the terminal's capabilities. This improves the rationality and accuracy of reliability sequence selection, helps ensure subsequent transmission, and thus guarantees communication performance.

[0161] The specific process of the communication method provided in this application has been described above. The implementation of the first information and the communication device selecting a first reliability sequence from a set of reliability sequences based on the first information will be described below.

[0162] In a first possible implementation, the first information includes encoding-related length information. This encoding-related length information includes at least one of the following: mother code length N. m The payload bit count is A, the sequence length after rate matching is E, or the cyclic redundancy check (CRC) length. For example, the CRC length can also be understood as the length of the CRC code, or the number of CRC check bits.

[0163] The following discussion addresses the implementation of a communication device selecting the first reliability sequence from a set of reliability sequences based on various parameters in the encoding-related length information.

[0164] Case 1: The communication device is based on the mother code length N. m Select the first reliability sequence.

[0165] Among them, the first reliability sequence is the one in the reliability sequence set whose length is greater than or equal to the mother code length N. m A reliability sequence. For example, if the set of reliability sequences contains a sequence of length equal to the mother code length N... m If the reliability sequence is N, then choose the sequence with a length equal to N. m The reliability sequence is used as the first reliability sequence. At this time, the communication device performs channel coding or channel decoding based on this first reliability sequence itself; if the reliability sequence set does not contain a sequence with a length equal to the mother code length N... m If the reliability sequence is greater than N, then choose one with a length greater than N. m The reliability sequence is taken as the first reliability sequence. At this time, the communication device uses a subsequence (of length N) of the first reliability sequence. m Perform channel coding or channel decoding.

[0166] As one possible implementation, the mother code length N m It can be determined based on the length E after rate matching. For example, the mother code length N... m The length E after matching the speed can satisfy the following relationship:

[0167]

[0168] in, This indicates rounding x up. Furthermore, rounding up can be replaced with rounding down or other rounding methods; there are no restrictions.

[0169] For example, taking a sequence length of E = 1728 after rate matching as an example, If the set of reliability sequences includes four reliability sequences with lengths of {1024 2048 4096 8192}, then the reliability sequence with a length of 2048 is selected as the first reliability sequence.

[0170] Alternatively, taking a length of E = 1728 after rate matching as an example, If the set of reliability sequences includes two reliability sequences with lengths of {1024 8192}, then the reliability sequence with a length of 8192 is selected as the first reliability sequence, and then a subsequence with a length of 2048 is selected from the first reliability sequence for channel coding or channel decoding.

[0171] Understandably, when the reliability sequence table includes four reliability sequences of lengths {1024, 2048, 4096, 8192}, it can flexibly adapt to Polar code encoding of various lengths (such as 1024, 2048, 4096, 8192). When the reliability sequence set includes two reliability sequences of lengths {1024, 8192}, subsequences of various lengths (such as 2048, 4096) can be selected from the reliability sequence of length 8192 for channel coding or decoding. By adding a reliability sequence of length 8192, the standard representation can be simplified or the storage overhead of the communication device can be reduced, while adapting to Polar code encoding of various lengths (such as 1024, 2048, 4096, 8192).

[0172] Scenario 2: The communication device selects the first reliability sequence based on the number of payload bits A.

[0173] The number of payload bits A can be positively correlated with the length of the first reliability sequence. For example, if the number of payload bits is less than the first payload bit threshold, the length of the first reliability sequence is the first length; or...

[0174] If the number of payload bits is greater than or equal to the first payload bit threshold and less than the second payload bit threshold, the length of the first reliability sequence is the second length; or,

[0175] If the number of payload bits is greater than or equal to the second payload bit threshold and less than the third payload bit threshold, the length of the first reliability sequence is the third length; or,

[0176] If the number of payload bits is greater than or equal to the third payload bit threshold and less than the fourth payload bit threshold, the length of the first reliability sequence is the fourth length.

[0177] The first, second, third, and fourth net payload bit count thresholds are all different. The order of these four thresholds can be: first net payload bit count threshold < second net payload bit count threshold < third net payload bit count threshold < fourth net payload bit count threshold.

[0178] As one possible implementation, the second payload bit count threshold is 2 times the first payload bit count threshold. n1 ±a times, or the third net payload bit threshold is 2 times the first net payload bit threshold. n2 ±b times, or the fourth payload bit threshold is 2 times the first payload bit threshold. n3 ±c times. Where n2 is greater than n1, n3 is greater than n2, and n1, n2, and n3 are positive integers greater than or equal to 1. a, b, and c are natural numbers, such as a, b, c = 0, 1, 2, ...

[0179] It should be noted that when a,b,c=0, it can also be assumed that a,b,c do not exist, and a,b,c in the above threshold relationship can be deleted.

[0180] Correspondingly, when a, b, c = 0, the third net payload bit threshold can also be considered as 2 times the second net payload bit threshold. n2-n1 The fourth net payload bit threshold is twice the second net payload bit threshold. n3-n1 Double; or, the fourth net payload bit threshold is twice the third net payload bit threshold. n3-n2 times.

[0181] For example, the first net payload bit count threshold can be 360. n1, n2, and n3 can be 1, 2, and 3, respectively. That is, when a,b,c = 0, or when a,b,c does not exist, the second net payload bit count threshold can be 720, the third net payload bit count threshold can be 1440, and the fourth net payload bit count threshold can be 2880.

[0182] For example, the standard may predefine a first payload bit count threshold, or the channel coder and channel decoder may negotiate the first payload bit count threshold, or the RAN node may configure the first payload bit count threshold to the terminal. The second, third, and fourth payload bit count thresholds can be determined based on their relationship with the first payload bit count threshold as described above.

[0183] Alternatively, the standard may predefine a first payload bit threshold, a second payload bit threshold, a third payload bit threshold, and a fourth payload bit threshold; or the channel coder and the channel decoder may negotiate the above four payload bit thresholds; or the RAN node may configure the above four payload bit thresholds to the terminal without restriction.

[0184] The first, second, third, and fourth lengths are all different. The order of the four lengths can be: first length ≤ second length ≤ third length ≤ fourth length.

[0185] As one possible implementation, the second length is 2 times the first length. m1 ±a1 times, or the third length is 2 times the first length. m2 ±b1 times, or the fourth length is 2 times the first length. m3 ±c1 times. Where m2 is greater than m1, m3 is greater than m2, and m1, m2, and m3 are positive integers greater than or equal to 1. a1, b1, and c1 are natural numbers, such as a1, b1, c1 = 0, 1, 2, ...

[0186] Correspondingly, when a1, b1, c1 = 0, the third length can also be considered to be twice the second length. m2-m1 The fourth length is twice the length of the second length. m3-m1 Double. Or, the fourth length is twice the length of the third. m3-m2 times.

[0187] For example, the first length can be 1024. m1, m2, and m3 can be 1, 2, and 3, respectively. That is, when a1, b1, c1 = 0, the second length can be 2048, the third length can be 4069, and the fourth length can be 8192.

[0188] For example, the standard may predefine a first length, or the channel coder and channel decoder may negotiate the first length, or the RAN node may configure the first length to the terminal. The second, third, and fourth lengths can be determined based on their relationship with the first length as described above.

[0189] Alternatively, the standard can predefine a first length, a second length, a third length, and a fourth length, or the channel coder and the channel decoder can negotiate the above four lengths, or the RAN node can configure the above four lengths to the terminal without restriction.

[0190] For example, based on the above description of the four payload bit thresholds and four lengths, the payload bit count A and the length of the reliability sequence can satisfy one or more of the correspondences shown in Table 2.

[0191] Table 2

[0192]

[0193] In Table 2, the length of the reliability sequence can also be understood as the maximum length of the reliability sequence, or the maximum length N supported by the reliability sequence table or the reliability table. maxFurthermore, if the reliability sequence set includes reliability sequences of the four lengths shown in Table 2 above, then in the standard, these four lengths of reliability sequences can be identified by a reliability sequence index, a reliability sequence number, a reliability sequence table index, or a reliability table number. Taking the identification of reliability sequences in the reliability sequence set by reliability table number as an example, Table 2 above may also include the reliability sequence table number.

[0194] As one possible implementation, the scheme for selecting the first reliability sequence based on the number of payload bits A, as described above, can be considered as a scheme for selecting the first reliability sequence under the assumption that the code rate remains unchanged or fluctuates within a certain range, or that the error correction performance remains unchanged or fluctuates within a certain range.

[0195] For example, when the payload bit count A1 is less than 360, the length of the first reliability sequence is 1024. Assuming the mother code length is N1, then N1 ≤ 1024, and the code rate is A1 / N1. When the payload bit count is 360 ≤ A2 < 720, if channel coding is performed with a mother code length N2 ≤ 1024, the code rate increases, and the error correction performance decreases. To ensure that the code rate / error correction performance remains basically consistent, it is necessary to increase the mother code length and select a reliability sequence with a length of 2048 as the first reliability sequence; or, if the reliability sequence set does not include a reliability sequence with a length of 2048, select a reliability sequence with a length greater than 2048 as the first reliability sequence, and then select a subsequence with a length of 2048 for channel coding or channel decoding.

[0196] Based on the above scheme, when the number of payload bits is less than the first payload bit threshold, a shorter reliability sequence (i.e., the first length) is selected for channel coding or decoding. The corresponding mother code length is also shorter. While satisfying error correction performance, a smaller code length can be maintained, reducing resource overhead. Subsequently, as the number of payload bits increases, the length of the reliability sequence and the mother code length can be appropriately and reasonably increased to maintain the code rate / error correction performance unchanged or to allow it to fluctuate within a certain range, thereby maintaining transmission performance.

[0197] Scenario 3: The communication device selects the first reliability sequence based on the number of payload bits A and the CRC length.

[0198] The number of payload bits A can be positively correlated with the length of the first reliability sequence. For example, if the number of payload bits is less than the first payload bit threshold, the length of the first reliability sequence is the first length; or...

[0199] If the number of payload bits is greater than or equal to the first payload bit threshold and less than the second payload bit threshold, the length of the first reliability sequence is the second length; or,

[0200] If the number of payload bits is greater than or equal to the second payload bit threshold and less than the third payload bit threshold, the length of the first reliability sequence is the third length; or,

[0201] If the number of payload bits is greater than or equal to the third payload bit threshold and less than the fourth payload bit threshold, the length of the first reliability sequence is the fourth length.

[0202] The first, second, third, and fourth payload bit count thresholds are determined based on the CRC length. For example, the first, second, third, and fourth payload bit count thresholds can be determined based on the difference between 1024 and the CRC length.

[0203] The first, second, third, and fourth net payload bit count thresholds are all different. The relationship between the four net payload bit count thresholds can be found in the relevant description in Case 2 above, and will not be repeated here.

[0204] For example, the first payload bit threshold is equal to the difference between 1024 and the CRC length, expressed as (1024-N). CRC ), N CRC This is the CRC length. The second payload bit threshold is 2 × (1024 - N). CRC The third net payload bit threshold is 4×(1024-N). CRC The fourth net payload bit threshold is 8 × (1024 - N). CRC ).

[0205] The first, second, third, and fourth lengths are all different. Exemplary values ​​for the four lengths, the relationships between them, and the methods for determining them can be found in the relevant description in Case Two above, and will not be repeated here.

[0206] For example, based on the above description of the four payload bit thresholds and four lengths, the payload bit count A, CRC length, and reliability sequence length can satisfy one or more of the correspondences shown in Table 3.

[0207] Table 3

[0208]

[0209] In the case of a code length of 1024 and the presence of a CRC code, the maximum length of the information bits is 1024-N. CRCSince the code rate needs to be less than 1, therefore, when the length of the reliability sequence is 1024, if the net payload bits A equals (1024-N)... CRC If the code rate is 1, it is equivalent to no channel coding. Therefore, the number of payload bits A needs to be less than (1024-N). CRC ).

[0210] For other implementations of Table 3, please refer to the relevant explanations of Table 2 in Case 2 above, which will not be repeated here.

[0211] As one possible implementation, the scheme described above, which selects the first reliability sequence based on the number of payload bits A and the CRC length, can be considered as a scheme for selecting the first reliability sequence under the assumptions that the code rate remains constant or fluctuates within a certain range, or that the error correction performance remains constant or fluctuates within a certain range. Refer to the relevant explanation in Case Two above; it will not be repeated here.

[0212] Based on the above scheme, when the number of payload bits is less than the first payload bit threshold, a shorter reliability sequence (i.e., the first length) is selected for channel coding or decoding. The corresponding mother code length is also shorter. While satisfying error correction performance, a smaller code length can be maintained, reducing resource overhead. Subsequently, as the number of payload bits increases, the length of the reliability sequence and the mother code length can be appropriately and reasonably increased to maintain the code rate / error correction performance unchanged or to allow it to fluctuate within a certain range, thereby maintaining transmission performance.

[0213] In addition, the selection of reliability sequences is combined with CRC length, which can better adapt to the encoding / decoding of the net payload bits of concatenated CRC codes, or better adapt to the encoding / decoding of CRC-aided Polar codes, thereby improving the performance of channel coding / decoding.

[0214] Case 4: The communication device selects the first reliability sequence based on the sequence length E after rate matching.

[0215] Wherein, the sequence length E after rate matching is positively correlated with the length of the first reliability sequence. For example, if the sequence length after rate matching is less than the first rate matching length threshold, the length of the first reliability sequence is the first length; or,

[0216] If the length of the sequence after rate matching is greater than or equal to the first rate matching length threshold and less than the second rate matching length threshold, then the length of the first reliability sequence is the second length; or...

[0217] If the length of the sequence after rate matching is greater than or equal to the second rate matching length threshold and less than the third rate matching length threshold, then the length of the first reliability sequence is the third length; or...

[0218] If the length of the sequence after rate matching is greater than or equal to the third rate matching length threshold and less than the fourth rate matching length threshold, the length of the first reliability sequence is the fourth length.

[0219] For example, the aforementioned "rate matching length threshold" can also be understood as "the length threshold of the sequence after rate matching," and the two can be interchanged without restriction.

[0220] Among them, the first rate matching length threshold, the second rate matching length threshold, the third rate matching length threshold, and the fourth rate matching length threshold are all different. The order of the four thresholds can be: first rate matching length threshold < second rate matching length threshold < third rate matching length threshold < fourth rate matching length threshold.

[0221] As one possible implementation, the second rate matching length threshold is 2 times the first rate matching length threshold. n1 ±a times, or the third rate matching length threshold is 2 times the first rate matching length threshold. n2 ±b times, or the fourth rate matching length threshold is 2 times the first rate matching length threshold. n3 ±c times. Where n2 is greater than n1, n3 is greater than n2, and n1, n2, and n3 are positive integers greater than or equal to 1. a, b, and c are natural numbers, such as a, b, c = 0, 1, 2, ... Refer to the relevant explanations of the four thresholds in Case Two above.

[0222] For example, the first rate matching length threshold can be 1088. n1, n2, and n3 can be 1, 2, and 3, respectively. That is, when a, b, c = 0, the second rate matching length threshold can be 2176, the third rate matching length threshold can be 4352, and the fourth rate matching length threshold can be 8704.

[0223] For example, the standard may predefine a first rate match length threshold, or the channel coder and channel decoder may negotiate the first rate match length threshold, or the RAN node may configure the first rate match length threshold to the terminal. The second, third, and fourth rate match length thresholds can be determined based on their relationship with the first rate match length threshold as described above.

[0224] Alternatively, the standard may predefine a first rate matching length threshold, a second rate matching length threshold, a third rate matching length threshold, and a fourth rate matching length threshold; or the channel coder and the channel decoder may negotiate the above four rate matching length thresholds; or the RAN node may configure the above four rate matching length thresholds to the terminal without restriction.

[0225] The first, second, third, and fourth lengths are all different. Exemplary values ​​for the four lengths, the relationships between them, and the methods for determining them can be found in the relevant description in Case Two above, and will not be repeated here.

[0226] For example, based on the above description of the four rate matching length thresholds and the four lengths, the sequence length E after rate matching and the length of the reliability sequence can satisfy one or more of the correspondences shown in Table 4.

[0227] Table 4

[0228]

[0229] The implementation of Table 4 can refer to the relevant explanation of Table 2 in Case 2 above. For example, the net charge bit count A in Table 2 can be replaced with the sequence length E after rate matching for understanding. This will not be elaborated further here.

[0230] Based on this possible implementation, selecting the reliability sequence according to the sequence length after rate matching can better adapt to the number of encoded bits that time-frequency resources can carry. For example, it can avoid selecting a long reliability sequence, which would result in a number of encoded bits that is much greater than the number of encoded bits that time-frequency resources can carry, thus causing more bits to be discarded when performing puncturing operations during rate matching; or, it can avoid selecting a short reliability sequence, which would result in a number of encoded bits that is much less than the number of encoded bits that time-frequency resources can carry, thus causing a waste of time-frequency resources.

[0231] It is understood that the above four scenarios can be executed independently, or at least two of the above four scenarios can be combined. For example, the length of the first reliability sequence selected in scenarios two through four must be greater than or equal to the length of the mother code; or, the first reliability sequence can be selected based on the number of payload bits A and the length E after rate matching. For example, if the number of payload bits A is greater than the first payload bit threshold and the length E after rate matching is greater than the first rate matching length threshold, the length of the first reliability sequence is the first length; or, the first reliability sequence can be selected based on the number of payload bits A, the CRC length, and the length E after rate matching. Of course, there can be other combinations of the above four scenarios, and this application does not specifically limit them.

[0232] In the first possible implementation described above, the communication device selects a reliability sequence based on the mother code length, the number of payload bits, the sequence length after rate matching, or the CRC length. Therefore, the selected reliability sequence better adapts to these parameters, improving the accuracy of reliability sequence selection. Furthermore, the encoding-related length information is a parameter understood and agreed upon by both the channel encoder and decoder. Therefore, explicit signaling between the channel encoder and decoder is unnecessary to indicate the reliability sequence, thereby reducing signaling overhead.

[0233] In a second possible implementation, the first information includes the type of control information. The type of control information includes primary control information or secondary control information; or, the type of control information is broadcast control information.

[0234] The following sections will first explain the primary control information, secondary control information, and broadcast control information.

[0235] One possible implementation is that the control information can be uplink control information, downlink control information, or sidelink control information. Accordingly, uplink control information can be divided into first-level uplink control information or second-level uplink control information. Downlink control information can be divided into first-level downlink control information or second-level downlink control information. Sidelink control information can be divided into first-level sidelink control information or second-level sidelink control information.

[0236] For example, uplink control information can be understood as control information sent by the terminal to the RAN node. This uplink control information may include UCI (uplink control information), AI-related parameters (such as training data for the AI ​​model), perception-related parameters (such as perception accuracy), and MAC control elements (CE). The AI-related parameters and / or perception-related parameters may be part of the uplink control information parallel to UCI, or they may be included within UCI; there are no restrictions on this.

[0237] For example, downlink control information can be understood as control information sent by the RAN node to the terminal. This downlink control information can include DCI (downlink control information), AI-related parameters (such as model parameters of the AI ​​model), perception-related parameters (such as perception measurement configuration), MAC CE, etc. Among these, AI-related parameters and / or perception-related parameters can be downlink control information parallel to DCI, or they can be carried within DCI; there are no restrictions.

[0238] For example, sidelink control information can be understood as control information sent from one terminal to another. This sidelink control information may include SCI (sidelink control information), AI-related parameters, perception-related parameters, MAC CE, etc. Among these, AI-related parameters and / or perception-related parameters may be sidelink control information parallel to SCI, or they may be carried within SCI; there are no restrictions.

[0239] As one possible implementation, Level 1 uplink control information includes hybrid automatic repeat request (HARQ) feedback and / or scheduling request (SR). Level 2 uplink control information includes channel state information (CSI).

[0240] For example, HARQ feedback information can be HARQ acknowledgement (HARQ-ACK) or HARQ negative acknowledgment (HARQ-NACK). SR is used to request uplink resources from the network.

[0241] For example, CSI may include CSI part 1 and / or CSI part 2. CSI part 1 may include rank indicator (RI), channel quality indicator (CQI), etc., and CSI part 2 may include precoding matrix indicator (PMI), layer indicator (LI), etc.

[0242] For example, the number of bits in CSI part 1 is fixed and is used to determine the number of bits in CSI part 2. Furthermore, CSI part 1 can also be referred to as Type-I CSI, and CSI part 2 can also be referred to as Type-II CSI.

[0243] For example, Level 1 uplink control information can be carried on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). Level 2 uplink control information can also be carried on a PUCCH or a PUSCH. In this case, it can be assumed that when the physical channel is a PUCCH or PUSCH carrying Level 1 uplink control information, the length of the first reliability sequence is a first length; when the physical channel is a PUCCH or PUSCH carrying Level 2 uplink control information, the length of the first reliability sequence is a second length.

[0244] As one possible implementation, the first-level downlink control information may include relevant control signaling with high latency sensitivity, such as time-frequency resource information including HARQ feedback. The second-level downlink control information may include relevant control signaling with low latency sensitivity or no latency sensitivity. Optionally, the first-level downlink control information may include scheduling information from the second-level downlink control information, such as time-frequency resource information from the second-level downlink control information.

[0245] For example, the first-level downlink control information can be carried on the physical downlink control channel (PDCCH), and the second-level downlink control information can be carried on the physical downlink shared channel (PDSCH). In this case, it can also be considered that when the physical channel is PDCCH, the length of the first reliability sequence is the first length; when the physical channel is PDSCH, the length of the first reliability sequence is the second length.

[0246] As one possible implementation, the implementation of Level 1 Link Control Information (LCI) can be found in Section 8.3.1 of 3GPP TS 38.212 V18.4.0, which describes the Level 1 LCI. Similarly, the implementation of Level 2 LCI can be found in Section 8.4.1 of 3GPP TS 38.212 V18.4.0, which describes the Level 2 LCI. Further details will not be provided here. It should be noted that the standard versions cited in this application are merely examples; other versions with the same standard number may also be referenced, and this application does not limit the scope of the application.

[0247] For example, the first-level crosslink control information can be carried on the physical sidelink control channel (PSCCH), and the second-level crosslink control information can be carried on the physical sidelink shared channel (PSSCH). In this case, it can also be considered that when the physical channel is PSCCH, the length of the first reliability sequence is the first length; when the physical channel is PSSCH, the length of the first reliability sequence is the second length.

[0248] For example, Level 1 control information can also be called first-stage control information, and Level 2 control information can also be called second-stage control information. The two descriptions can be used interchangeably.

[0249] For example, the aforementioned uplink control information, downlink control information, or sidelink control information can be understood as control information sent in a unicast manner.

[0250] As one possible implementation, broadcast control information can be understood as control information carried on a broadcast channel, or control information carried in a broadcast channel, such as information carried in a physical broadcast channel (PBCH). Alternatively, broadcast control information can be understood as control information sent by RAN nodes via broadcast, or cell-level control information sent by RAN nodes.

[0251] The following discussion addresses the implementation of a communication device selecting the first reliability sequence from a set of reliability sequences based on the type of control information.

[0252] Case 1: The communication device selects the first reliability sequence based on whether the control information is primary or secondary control information.

[0253] When the type of control information is level one control information, the length of the first reliability sequence is the first length; when the type of control information is level two control information, the length of the first reliability sequence is the second length.

[0254] In other words, in Case 1, when the control information is a first-level uplink control information, a first-level downlink control information, or a first-level side link control information, the length of the first reliability sequence is the first length; when the control information is a second-level uplink control information, a second-level downlink control information, or a second-level side link control information, the length of the first reliability sequence is the second length.

[0255] The second length is greater than or equal to the first length. For example, if the second length is greater than the first length, the second length can be twice the length of the first length. n The length is a multiple of n, where n is a positive integer greater than or equal to 1. For example, the first length is 1024, the second length is 2048, or 4096, or 8192.

[0256] Based on this scheme, selecting a shorter reliability sequence for the first-level control information, or choosing a reliability sequence from the existing standard, is beneficial for system compatibility and can adapt to low-capability terminals. Selecting a longer reliability sequence for the second-level control information allows for the transmission of longer control information and adapts to higher-order modulation.

[0257] Case 2: When the control information is uplink control information and the uplink control information is level 1 uplink control information, the length of the first reliability sequence is greater than or equal to 1024.

[0258] Preferably, in case 2, the length of the first reliability sequence is greater than 1024. That is, compared to case 1, a longer reliability sequence is selected for the first-level uplink control information.

[0259] As one possible implementation, in case 2, the secondary uplink control information may not exist. For example, for the primary uplink control information, if a longer reliability sequence is used, the length of the primary uplink control information can be increased. In this case, the primary uplink control information may also include CSI, that is, it supports encoding longer primary uplink control information. Therefore, the secondary uplink control information may not exist.

[0260] Case 3: When the type of control information is broadcast control information, the length of the first reliability sequence is either the first length or the second length.

[0261] The second length is greater than the first length. For example, the second length can be twice the length of the first length. n The length is a multiple of n, where n is a positive integer greater than or equal to 1. For example, the first length is 1024, the second length is 2048, or 4096, or 8192.

[0262] In other words, when the type of control information is broadcast control information, the length of the first reliability sequence can be greater than or equal to 1024.

[0263] Based on the scheme in scenario 3, since the length of the reliability sequence in the existing standard is 1024, choosing a reliability sequence of length 1024 for the broadcast control information can adapt to existing terminals, such as existing low-capability terminals (e.g., terminals with poor channel coding / decoding capabilities), thus improving system compatibility. Choosing a reliability sequence longer than 1024 for the broadcast control information can support channel coding for larger broadcast control information. Furthermore, due to the longer reliability sequence, reliability requirements can be met even when the number of bits in the broadcast control information is large.

[0264] For example, based on the descriptions of Situations 1, 2, and 3 above, the length of the reliability sequence corresponding to the uplink control information, downlink control information, sidelink control information, or broadcast control information can be as shown in at least one of Table 5, or at least one of Table 6, or at least one of Table 7.

[0265] Table 5

[0266] Control Information Select a reliability sequence of length N1. Select a reliability sequence of length N². Level 1 uplink control information √ Level 2 uplink control information √ Level 1 Downlink Control Information √ Level 2 Downlink Control Information √ Broadcast control information √ Level 1 side link control information √ Secondary side link control information √

[0267] Where N1 represents the first length and N2 represents the second length. √ indicates that a reliability sequence of the corresponding length is selected. For example, a reliability sequence of length N1 is selected for the first-level uplink control information, and a reliability sequence of length N2 is selected for the second-level uplink control information.

[0268] Table 6

[0269] Control Information Select a reliability sequence of length N1. Select a reliability sequence of length N². Level 1 uplink control information √ Level 2 uplink control information (not present) NA NA Level 1 Downlink Control Information √ Level 2 Downlink Control Information √ Broadcast control information √ Level 1 side link control information √ Secondary side link control information √

[0270] Table 7

[0271] Control Information Select a reliability sequence of length N1. Select a reliability sequence of length N². Level 1 uplink control information √ Level 2 uplink control information (not present) NA NA Level 1 Downlink Control Information √ Level 2 Downlink Control Information √ Broadcast control information √ Level 1 side link control information √ Secondary side link control information √

[0272] NA can represent no selection. Table 6 shows the reliability sequence of broadcast control information selection with a length of N1, and Table 7 shows the reliability sequence of broadcast control information selection with a length of N2.

[0273] In a third possible implementation, the first information includes the type of control information. The type of control information includes control information carried on a control channel or control information carried on a data channel.

[0274] As one possible implementation, the control information includes uplink control information. The control channel carrying the uplink control information can be a physical uplink control channel (PUCCH), and the data channel carrying the uplink control information can be a physical uplink shared channel (PUSCH). For a description of the uplink control information, please refer to the relevant description in the second possible implementation described above, which will not be repeated here.

[0275] As a first possible implementation, when the control information is control information carried on a data channel (or in other words, control information carried on a data channel), the length of the first reliability sequence is a first length; or, when the control information is control information carried on a control channel (or in other words, control information carried on a control channel), the length of the first reliability sequence is a second length.

[0276] For example, for UCI on PUSCH, the length of the first reliability sequence is a first length; for UCI on PUCCH, the length of the first reliability sequence is a second length.

[0277] Wherein, the second length is greater than or equal to the first length. For example, if the second length is greater than the first length, the second length can be twice the length of the first length. n The multiple, where n is a positive integer greater than or equal to 1. For example, the first length is 1024, and the second length is 2048, or 4096, or 8192; or the first length is 2048, and the second length is 2048, or 4096, or 8192.

[0278] As a second possible implementation, the control information is carried on a data channel, and when there is no data transmission on the data channel, the length of the first reliability sequence is greater than or equal to 1024.

[0279] For example, taking UCI as an example, when the DCI scheduling PUSCH indicates that UCI is transmitted on PUSCH and there is no uplink data transmission on PUSCH (such as when the uplink shared channel (UL-SCH) indicator field in the DCI is set to 0), or when UCI transmission on PUSCH occurs without UL-SCH, the length of the first reliability sequence can be greater than or equal to 1024.

[0280] As one possible implementation, when control information is carried on a control channel, the second length can vary depending on the format of the control channel. For example, if the PUCCH carrying uplink control information uses PUCCH Format 2 or PUCCH Format 4, the second length can be 2048; or if the PUCCH carrying uplink control information uses PUCCH Format 3, the second length can be 4096.

[0281] As one possible implementation, in the third possible implementation described above, the control information can also be downlink control information or sidelink control information. For a description of the downlink control information or sidelink control information, please refer to the relevant description in the second possible implementation described above; for the implementation of the communication device selecting the first reliability sequence when the control information is downlink control information or sidelink control information, please refer to the relevant description in the third possible implementation regarding the selection of the first reliability sequence when the control information is uplink control information. Further details will not be elaborated here.

[0282] Based on the above implementation methods, the control information carried in the data channel may be control information that needs to be transmitted in a timely manner. For example, UCI that requires timely feedback may need to be transmitted along with the path (i.e., carried in the PUSCH). Therefore, for control information carried in the data channel, choosing a shorter reliability sequence can reduce the channel coding or decoding delay compared to choosing a longer reliability sequence, thereby meeting the transmission delay requirements of the control information. For control information carried in the control channel, choosing a longer reliability sequence can improve error correction performance and reliability compared to choosing a shorter reliability sequence.

[0283] Alternatively, if the control information is carried on the data channel and there is no data transmission on the data channel, a larger amount of control information (such as a larger UCI payload) can be transmitted on the data channel. In this case, a longer reliability sequence can be used. For this control information, compared with choosing a shorter reliability sequence, better error correction performance can be obtained and reliability can be improved.

[0284] In a fourth possible implementation, the first information includes the type of parameters carried in the control information. The type of parameters carried in the control information includes either a first type of parameter or a second type of parameter, wherein the lengths of the first type of parameter and the second type of parameter are different. For example, the length of the first type of parameter is shorter than the length of the second type of parameter. The length of a parameter can also be understood as the size of the parameter, or the number of bits in the parameter.

[0285] As one possible implementation, the control information includes uplink control information, downlink control information, or sidelink control information. Please refer to the relevant description in the second possible implementation above, which will not be repeated here.

[0286] As one possible implementation, when the control information includes uplink control information, the first type of parameter does not include channel state information (CSI), or does not include two-part CSI. For example, the first type of parameter may include at least one of the following: hybrid automatic repeat request (HARQ) feedback information, scheduling request (SR), or CSI not of two parts.

[0287] When the control information includes uplink control information, the second type of parameter includes two parts of CSI. For example, the second type of parameter includes two parts of CSI, or includes two parts of CSI and HARQ feedback information, or includes two parts of CSI and SR, or includes two parts of CSI, HARQ feedback information and SR.

[0288] For example, a two-part CSI can be understood as CSI part 1 and CSI part 2; a non-two-part CSI can be understood as either CSI part 1 or CSI part 2. That is, the first type of parameter does not include CSI, or does not simultaneously include CSI part 1 and CSI part 2, such as including CSI part 1 but not CSI part 2, or including CSI part 2 but not CSI part 1. The second type of parameter includes CSI part 1 and CSI part 2. The implementation of CSI part 1, CSI part 2, HARQ feedback information, and SR can be referred to the relevant descriptions in the second possible implementation described above, and will not be repeated here.

[0289] As one possible implementation, if the parameters carried in the control information are of the first type, the length of the first reliability sequence is a first length; or if the parameters carried in the control information are of the second type, the length of the first reliability sequence is a second length.

[0290] For example, for uplink control information that does not include CSI or does not include two parts of CSI, the length of the first reliability sequence is a first length; for uplink control information that includes two parts of CSI, the length of the first reliability sequence is a second length.

[0291] Wherein, the second length is greater than or equal to the first length. For example, if the second length is greater than the first length, the second length can be twice the length of the first length. n The multiple, where n is a positive integer greater than or equal to 1. For example, the first length is 1024, and the second length is 2048, or 4096, or 8192; or the first length is 2048, and the second length is 2048, or 4096, or 8192.

[0292] Based on the above implementation method, a reliability sequence can be selected according to the length of the parameters carried in the control information. For example, when the parameters carried in the control information are short, a shorter reliability sequence is selected to minimize the encoding length while satisfying error correction performance, thereby reducing encoding and decoding latency; when the parameters carried in the control information are long, a longer reliability sequence is selected to satisfy the error correction performance of the control information and improve reliability. In other words, it can meet the error correction performance requirements of parameters of different lengths carried in the control information.

[0293] In a fifth possible implementation, the first information includes transmission condition information. This transmission condition information includes at least one of the following: channel quality, modulation and coding scheme (MCS) index, code rate, modulation order, spectral efficiency, HARQ retransmission count, or link direction.

[0294] The following discussion addresses the various parameters in the transmission condition information and the implementation of the communication device selecting the first reliability sequence from the set of reliability sequences based on these parameters, with each case being considered separately.

[0295] Case A: Transmission condition information includes channel quality.

[0296] As one possible implementation, channel quality can be represented by at least one of the following: reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), signal-to-noise ratio (SNR), signal-to-interference plus noise ratio (SINR), etc. Furthermore, channel quality can also be alternatively described as signal quality.

[0297] For example, channel quality can be obtained by the terminal measuring a reference signal. The reference signal can be, for example, a synchronization signal and PBCH block (SSB), a channel state information-reference signal (CSI-RS), etc., and is not limited to any particular type. Furthermore, the terminal can indicate this channel quality to the RAN node or another terminal so that the RAN node or another terminal can select a reliability sequence based on the channel quality.

[0298] In the case where the communication device selects the first reliability sequence based on the channel quality, the channel quality can be negatively correlated with the length of the first reliability sequence. For example, as the channel quality decreases, the length of the first reliability sequence increases, or as the channel quality improves, the length of the first reliability sequence decreases.

[0299] As one possible implementation, if the channel quality is greater than a first channel quality threshold, the length of the first reliability sequence is a first length; or,

[0300] If the channel quality is less than or equal to the first channel quality threshold and greater than or equal to the second channel quality threshold, the length of the first reliability sequence is the second length; or,

[0301] When the channel quality is less than or equal to the second channel quality threshold, the length of the first reliability sequence is the third length.

[0302] The first channel quality threshold is greater than the second channel quality threshold. Furthermore, the first and second channel quality thresholds can differ depending on the parameters used to represent channel quality.

[0303] For example, when channel quality is represented by RSRP, the first channel quality threshold is -85 dBm and the second channel quality threshold is -95 dBm. When channel quality is represented by RSRQ, the first channel quality threshold is -10 dB and the second channel quality threshold is -15 dB. When channel quality is represented by RSSI, the first channel quality threshold is 25 and the second channel quality threshold is 15.

[0304] In other words, when channel quality is represented by RSRP, it can be divided into three ranges: RSRP > -85dBm, RSRP ∈ [-95dBm, -85dBm], and RSRP < -95dBm. When channel quality is represented by RSRQ, it can be divided into three ranges: RSRP > -10dB, RSRQ ∈ [-15dBm, -10dBm], and RSRQ < -15dB. When channel quality is represented by RSSI, it can be divided into three ranges: RSSI > 25, RSSI ∈ [15, 25], and RSSI < 15.

[0305] As one possible implementation, the first channel quality threshold, the second channel quality threshold, or the third channel quality threshold can be predefined by the protocol, negotiated by the channel coder and the channel decoder, or configured by the RAN node to the terminal, without restriction.

[0306] The first, second, and third lengths are all different. The order of the three lengths can be: first length ≤ second length ≤ third length.

[0307] As one possible implementation, the second length is 2 times the first length. m1 ±a1 times, or the third length is 2 times the first length. m2 ±b1 times. Where m2 is greater than m1, and m1 and m2 are positive integers greater than or equal to 1. a1 and b1 are natural numbers, such as a1, b1 = 0, 1, 2, ... For example, the first length is 1024, the second length is 2048, and the third length is 4096. Refer to the descriptions of the four lengths in the first possible implementation above; they will not be repeated here.

[0308] For example, based on the above description of the two channel quality thresholds and three lengths, the length of the channel quality and reliability sequence can satisfy one or more of the correspondences shown in Table 8.

[0309] Table 8

[0310]

[0311] The descriptions of the length of the reliability sequence and the table number of the reliability sequence in Table 8 can be found in the relevant descriptions in Table 2 above, and will not be repeated here.

[0312] In the above case A, description is given by taking the channel quality ranges divided by the first channel quality threshold (denoted as Z1) and the second channel quality threshold (denoted as Z2) as >Z1, [Z1, Z2], and <Z2 as an example. In addition, the interval endpoints of the ranges may have other forms. For example, the channel quality ranges divided by Z1 and Z2 may be ≥Z1, (Z1, Z2], and <Z2, or >Z1, [Z1, Z2), and ≤Z2, or ≥Z1, (Z1, Z2), and ≤Z2, and the like. For the length of the first reliability sequence in each range, reference may be made to the related description when the channel quality ranges are >Z1, [Z1, Z2], and <Z2, which is not repeated herein.

[0313] As a possible implementation, the channel encoding side and the channel decoding side may adaptively adjust or switch the length of the reliability sequence according to the channel quality. For example, within a first time period, if the channel quality is greater than the first channel quality threshold, the channel encoding side and the channel decoding side select a reliability sequence of a first length. Subsequently, if the channel quality changes, for example, the channel quality falls between the first channel quality threshold and the second channel quality threshold, the channel encoding side and the channel decoding side may adjust the reliability sequence to a reliability sequence of a second length.

[0314] Based on the above solution, the reliability sequence can be reasonably selected according to the channel quality. For example, when the channel quality is greater than the first channel quality threshold, it can be considered that the channel quality is good, and a reliability sequence with a shorter length can meet the error correction requirement. Therefore, compared with using a longer reliability sequence, the coding and decoding length can be reduced, thereby reducing the coding and decoding delay. When the channel quality is greater than or equal to the second channel quality threshold but less than or equal to the first channel quality threshold, it can be considered that the channel quality is at a medium level, and a slightly longer reliability sequence can be used to meet the error correction requirement. When the channel quality is less than the second threshold, it can be considered that the channel quality is poor. In this case, using a longer reliability sequence can meet the error correction requirement and ensure transmission reliability.

[0315] Case B: The transmission condition information includes an MCS index.

[0316] As a possible implementation, the MCS index is used to indicate a modulation and coding scheme. For example, one MCS index may correspond to at least one of a code rate (also referred to as a target code rate) and a modulation order Q m ), or spectral efficiency.

[0317] For example, the modulation order can be 2, 4, 6, 8, etc. The modulation order can correspond to the modulation method. For instance, when the modulation order is 2, the modulation method can be quadrature phase shift keying (QPSK). When the modulation order is 4, the modulation method can be quadrature amplitude modulation (QAM). When the modulation order is 6, the modulation method can be 64QAM. When the modulation order is 8, the modulation method can be 256QAM.

[0318] For example, the standard can predefine various MCS index tables. An MCS index table can include at least one correspondence between MCS index, modulation order, code rate, and spectral efficiency. For instance, when the MCS index is 0, it corresponds to a modulation order of 2, a code rate of (×1024)120, and a spectral efficiency of 0.2344. When the MCS index is 1, it corresponds to a modulation order of 2, a code rate of (×1024)193, and a spectral efficiency of 0.3770, etc.

[0319] In the case where the communication device selects the first reliability sequence based on the MCS index, the MCS index can be positively correlated with the length of the first reliability sequence. For example, as the MCS index increases, the length of the first reliability sequence increases, or as the MCS index decreases, the length of the first reliability sequence decreases.

[0320] As one possible implementation, if the MCS index falls within the first index range, the length of the first reliability sequence is the first length; or,

[0321] If the MCS index falls within the range of the second index, the length of the first reliability sequence is the second length; or...

[0322] When the MCS index falls within the third index range, the length of the first reliability sequence is the third length.

[0323] Among them, the smallest MCS index in the second index range is greater than the largest MCS index in the first index range, and the smallest MCS index in the third index range is greater than the largest MCS index in the second index range.

[0324] For example, the MCS indexes are consecutive across the three index ranges. For instance, the difference between the smallest MCS index in the second index range and the largest MCS index in the first index range is 1, and the difference between the smallest MCS index in the third index range and the largest MCS index in the second index range is also 1.

[0325] For example, the number of MCS indexes included in different index ranges can be the same or different across the three index ranges. Furthermore, for an MCS index to belong to an index range, it can be understood that the MCS index can be either the smallest or the largest MCS index within that index range. That is, the index range can be closed.

[0326] For example, the minimum value in the first index range can be understood as the first index threshold, and the maximum value in the first index range can be understood as the second index threshold. Therefore, the MCS index belonging to the first index range can also be understood as: the MCS index is greater than or equal to the first index threshold and less than or equal to the second index threshold. Other index ranges can be implemented similarly, and will not be elaborated further.

[0327] For example, in Table 5.1.3.1-1 of the MCS index table for PDSCH defined in the 3GPP TS 38.214V18.4.0 standard, the first index range can be [0,9], the second index range can be [10,16], and the third index range can be [17,28]. In Table 5.1.3.1-2 of the MCS index table for PDSCH defined in the 3GPP TS 38.214V18.4.0 standard, the first index range can be [0,10], the second index range can be [11,19], and the third index range can be [20,27]. In Table 5.1.3.1-3 of the MCS index table for PDSCH defined in the 3GPP TS 38.214V18.4.0 standard, the first index range can be [0,14], the second index range can be [15,20], and the third index range can be [21,28].

[0328] As one possible implementation, the first index range, the second index range, or the third index range can be predefined by the protocol, negotiated by the channel coder and the channel decoder, or configured by the RAN node to the terminal, without restriction.

[0329] The first, second, and third lengths are all different. The order of the three lengths can be: first length ≤ second length ≤ third length.

[0330] As one possible implementation, the second length is 2 times the first length. m1 ±a1 times, or the third length is 2 times the first length. m2±b1 times. Where m2 is greater than m1, and m1 and m2 are positive integers greater than or equal to 1. a1, b1 are natural numbers, such as a, b = 0, 1, 2, ... For example, the first length is 1024, the second length is 2048, and the third length is 4096. Refer to the description of the four lengths in the first possible implementation above; further details are omitted here.

[0331] As an example, based on the above description of the three index ranges and three lengths, the length of the MCS index and the reliability sequence can satisfy one or more of the correspondences in Table 9, Table 10, or Table 11.

[0332] Table 9 (Table 5.1.3.1-1 for the MCS index applied to PDSCH)

[0333]

[0334] Based on the correspondence shown in Table 9, in I MCS In the case of ∈[0,9], the corresponding modulation order is lower (e.g., modulation order 2), the modulation method is QPSK, and the corresponding spectral efficiency requirement is lower, thus the reliability requirement is lower. Therefore, a shorter reliability sequence can be used to reduce the encoding and decoding delay while meeting the reliability requirements. In I MCS In the case of ∈[10,16], the corresponding modulation order is at a medium level (e.g., modulation order 4), and the modulation method is 16QAM. The corresponding spectral efficiency requirement is relatively higher, and thus the reliability requirement is also relatively higher. Therefore, a relatively long reliability sequence can be used to meet the reliability requirements. In I MCS In the case of ∈[17,28], the corresponding modulation order is higher (e.g., modulation order is 6), the modulation method is 64QAM, the corresponding spectral efficiency requirement is higher, and thus the reliability requirement is higher. At this time, a longer reliability sequence can be used to meet the reliability requirements and ensure transmission reliability.

[0335] Table 10 (Table 5.1.3.1-2 of the MCS index applied to PDSCH)

[0336]

[0337] Based on the correspondence shown in Table 10, in I MCS In the case of ∈[0,10], the corresponding modulation order is lower (e.g., modulation order 2 or 4), the modulation method is QPSK or 16QAM, and the corresponding spectral efficiency requirement is lower, thus the reliability requirement is lower. Therefore, a shorter reliability sequence can be used to reduce the encoding and decoding delay while meeting the reliability requirements. In I MCSIn the case of ∈[11,19], the corresponding modulation order is at a medium level (e.g., modulation order 6), the modulation method is 64QAM, and the corresponding spectral efficiency requirement is relatively higher, thus the reliability requirement is also relatively higher. Therefore, a relatively long reliability sequence can be used to meet the reliability requirements. In I MCS In the case of ∈[20,27], the corresponding modulation order is higher (e.g., modulation order is 8), the modulation method is 256QAM, the corresponding spectral efficiency requirement is higher, and thus the reliability requirement is higher. At this time, a longer reliability sequence can be used to meet the reliability requirements and ensure transmission reliability.

[0338] Table 11 (Table 5.1.3.1-3 of the MCS index applied to PDSCH)

[0339]

[0340] The technical effects resulting from the correspondence shown in Table 11 can be found in the explanations of the corresponding technical effects in Table 9 above. Further details will not be provided here.

[0341] Furthermore, the explanations of the length of the reliability sequence and the table number of the reliability sequence in Tables 9, 10, and 11 can be found in the relevant descriptions in Table 2 above, and will not be repeated here.

[0342] As another example, based on the above description, reliability sequence information can also be added to the MCS index table. For example, a certain correspondence in the MCS index table is used to indicate the correspondence between the MCS index and at least one of the following: reliability sequence length or reliability sequence table number. Optionally, this correspondence is also used to indicate the correspondence between the MCS index and at least one of code rate, modulation order, and spectral efficiency.

[0343] As one possible implementation, since the MCS index can correspond to at least one of the following: code rate, modulation order, or spectral efficiency, the scheme for selecting a reliability sequence based on at least one of the following can be referenced to the scheme for selecting a reliability sequence based on the MCS index described above. For example, the index range can be understood by replacing it with the code rate, modulation order, or spectral efficiency corresponding to the MCS within the index range, which will not be elaborated further here.

[0344] Case C: Transmission condition information includes the number of HARQ retransmissions.

[0345] As one possible implementation, the number of HARQ retransmissions can also be understood as the number of HARQ-NACKs, or the number of soft NACK responses. For example, Soft NACK differs from the forced retransmission mechanism of traditional NACK by allowing the receiver to choose partial retransmission or delayed response based on specific conditions (such as data priority and network status).

[0346] As one possible implementation, if the number of HARQ retransmissions is greater than the first retransmission threshold and less than or equal to the second retransmission threshold, the length of the first reliability sequence is the first length; or, if the number of HARQ retransmissions is greater than the second retransmission threshold and less than or equal to the third retransmission threshold, the length of the first reliability sequence is the second length.

[0347] Specifically, the second retransmission threshold is greater than the first retransmission threshold, and the third retransmission threshold is greater than the first retransmission threshold. For example, the first retransmission threshold can be 2, the second retransmission threshold can be 4, and the third retransmission threshold can be 8. Of course, the above three retransmission thresholds can also have other values, which are not restricted.

[0348] As one possible implementation, the first retransmission threshold, the second retransmission threshold, or the third retransmission threshold can be predefined by the protocol, negotiated by the channel coder and the channel decoder, or configured by the RAN node to the terminal, without restriction.

[0349] The second length is greater than the first length. For example, the second length is twice the length of the first length. m1 ±a1 times. m1 is a positive integer greater than or equal to 1. a1 is a natural number, such as a1 = 0, 1, 2, ... For example, the first length is 2048, and the second length is 4096.

[0350] As one possible implementation, if the initial transmission or the number of HARQ retransmissions is less than or equal to the first retransmission threshold, the length of the first reliability sequence can be less than the first length, for example, the length of the first reliability sequence is 1024.

[0351] In case C above, the range of retransmission counts divided by the first retransmission threshold (H1), the second retransmission threshold (H2), and the third retransmission threshold (H3) is (H1, H2] and (H2, H3], respectively, as an example. Furthermore, the endpoints of this range can be in other ways. For example, the range of retransmission counts divided by H1, H2, and H3 can be [H1, H2), [H2, H3), or [H1, H2], (H2, H3], etc. The length of the first reliability sequence under each range can refer to the relevant explanations when the retransmission count range is (H1, H2] and (H2, H3], and will not be repeated here.

[0352] Based on the above scheme, when the number of HARQ retransmissions falls between the first and second retransmission thresholds, the channel quality can be considered relatively good. Therefore, a shorter reliability sequence can be used to reduce encoding / decoding latency while maintaining error correction performance. When the number of HARQ retransmissions falls between the second and third retransmission thresholds, the channel quality can be considered relatively poor. In this case, a longer reliability sequence can be used to meet reliability requirements and ensure transmission reliability.

[0353] Case D: Transmission condition information includes link direction.

[0354] The link direction includes the uplink direction (which can also be replaced by uplink, uplink channel, or uplink transmission) or the downlink direction (which can also be replaced by downlink, downlink channel, or downlink transmission). The uplink direction is the transmission direction from the terminal to the RAN node, and the downlink direction is the transmission direction from the RAN node to the terminal.

[0355] For example, in the uplink direction, the terminal's power is limited, and the RAN node can deploy high-performance algorithms. Both the terminal and the RAN node need to support short packet transmission (such as control signaling) and long packet transmission (such as data). In the downlink direction, the RAN node has sufficient power, but the terminal's decoding complexity is limited and it is sensitive to decoding latency.

[0356] As one possible implementation, if the link direction is uplink, the length of the first reliability sequence is the second length; or, if the link direction is downlink, the length of the first reliability sequence is the first length.

[0357] Where the second length is greater than or equal to the first length. If the second length is greater than the first length, the second length is twice the first length. m1 ±a1 times. m1 is a positive integer greater than or equal to 1. a1 is a natural number, such as a1 = 0, 1, 2, ... For example, the first length is 1024 or 2048, and the second length is 2048 or 4096 or 8192.

[0358] Based on the above scheme, for the downlink direction, using a shorter reliability sequence, such as the existing standard's 1024-bit reliability sequence, or a slightly longer one (e.g., 2048-bit), can accommodate the weaker processing capabilities of the terminal. Furthermore, the shorter reliability sequence reduces encoding and decoding complexity, increases encoding / decoding speed, and reduces encoding / decoding latency. For the uplink direction, using a longer reliability sequence, such as 2048, 4096, or 8192-bit, can leverage the stronger processing capabilities of the RAN nodes, achieving long code gain, improving error correction capabilities, and obtaining more complete polarization.

[0359] In a sixth possible implementation, the first information includes mother code segmentation information. The mother code segmentation information includes segment indices of the mother code. The segment indices of the mother code correspond to at least one of the following: the number of segments in the mother code, or the length of the reliability sequence corresponding to each segment.

[0360] As one possible implementation, a segment of the mother code can be understood as a segment of the mother code length; that is, the length of the mother code can be segmented. For example, if the length of the mother code is N, the length N can be divided into multiple segment lengths, such as N1 and N2, where the sum of N1 and N2 equals N. The lengths of different segments of the mother code can be the same or different; for example, N1 and N2 mentioned above can be the same or different.

[0361] As one possible implementation, the number of segments in the mother code is the same as the number of segments in the information bits; that is, the segment index of the mother code can be considered to correspond to the number of segments in the information bits. For example, the information bits (including payload bits and CRC code (optional)) can be segmented, and each segment of the information bits can be channel-coded to obtain a segment of the mother code.

[0362] For example, channel coding can be performed on different segments of information bits using reliability sequences of the same or different lengths to obtain the corresponding segments of the mother code.

[0363] As one possible implementation, the number of segments in the mother code corresponding to different segment indices can be different or the same. When different segment indices correspond to the same number of segments, the segmentation method of the mother code differs. For example, the segmentation method of the mother code can include the length division of each segment. The segmentation method of the mother code can also correspond to the segment index of the mother code; that is, the segment index of the mother code can also correspond to the segmentation method of the mother code, or to the length of each segment of the mother code. Furthermore, different segment indices correspond to different reliability sequences.

[0364] As one possible implementation, the correspondence between the segment index of the mother code and the number of segments in the mother code includes at least one of the correspondences shown in Table 12. Here, I represents the segment index of the mother code, and N... u Indicates the number of segments in the mother code.

[0365] Table 12

[0366] I 1 2 3 4 5 6 7 8 9 10 11 12 13 14 <![CDATA[N u ]]> 1 2 2 3 3 4 3 4 4 5 4 5 5 6

[0367] As shown in Table 12, when the segment index of the mother code is 1, the number of segments in the mother code is 1, and it can be considered that the mother code has not been segmented. When the segment index of the mother code is 2 or 3, the number of segments in the mother code is 2. In this case, although the number of segments corresponding to the two segment indices is the same, the length of the segments can be different. For example, the lengths of the two segments corresponding to segment index 2 are length #11 and length #12, respectively, and the lengths of the two segments corresponding to segment index 3 are length #21 and length #22, respectively. The number of segments corresponding to other segment indices in Table 12 can be understood in a similar way and will not be elaborated further.

[0368] As one possible implementation, the correspondence between the segment index of the mother code and the first reliability sequence may include at least one of the following correspondences:

[0369] When the segment index of the mother code is 1, the first reliability sequence is a reliability sequence of the first length; or,

[0370] When the segment index of the mother code is 2, the first reliability sequence is two reliability sequences of the first length; or,

[0371] When the segment index of the mother code is 3, the first reliability sequence includes a reliability sequence of a first length and a reliability sequence of a second length; or,

[0372] When the segment index of the mother code is 4, the first reliability sequence includes two reliability sequences of the first length and one reliability sequence of the second length; or,

[0373] When the segment index of the mother code is 5, the first reliability sequence includes a reliability sequence of the first length and two reliability sequences of the second length; or,

[0374] When the segment index of the mother code is 6, the first reliability sequence includes two reliability sequences of the first length and two reliability sequences of the second length; or,

[0375] When the segment index of the mother code is 7, the first reliability sequence includes a reliability sequence of a first length, a reliability sequence of a second length, and a reliability sequence of a third length; or,

[0376] When the segment index of the mother code is 8, the first reliability sequence includes two reliability sequences of the first length, one reliability sequence of the second length, and one reliability sequence of the third length; or,

[0377] When the segment index of the mother code is 9, the first reliability sequence includes a reliability sequence of a first length, two reliability sequences of a second length, and a reliability sequence of a third length; or,

[0378] When the segment index of the mother code is 10, the first reliability sequence includes two reliability sequences of the first length, two reliability sequences of the second length, and one reliability sequence of the third length; or,

[0379] When the segment index of the mother code is 11, the first reliability sequence includes a reliability sequence of a first length, a reliability sequence of a second length, and two reliability sequences of a third length; or,

[0380] When the segment index of the mother code is 12, the first reliability sequence includes two reliability sequences of the first length, one reliability sequence of the second length, and two reliability sequences of the third length; or,

[0381] When the segment index of the mother code is 13, the first reliability sequence includes a reliability sequence of a first length, two reliability sequences of a second length, and two reliability sequences of a third length; or,

[0382] When the segment index of the mother code is 14, the first reliability sequence includes two reliability sequences of the first length, two reliability sequences of the second length, and two reliability sequences of the third length.

[0383] For example, based on the above correspondence, when the first reliability sequence is a reliability sequence of a first length, this first-length reliability sequence can be used for channel coding of the information bits. When the first reliability sequence consists of two first-length reliability sequences, one first-length reliability sequence can be used for channel coding of a segment of the information bits, and the other first-length reliability sequence can be used for channel coding of another segment of the information bits. If the first reliability sequence includes a first-length reliability sequence and a second-length reliability sequence, the first-length reliability sequence can be used for channel coding of a segment of the information bits, and the second-length reliability sequence can be used for channel coding of another segment of the information bits. Other implementations of the first reliability sequence in the above correspondence can be understood similarly and will not be elaborated further.

[0384] The first, second, and third lengths are all different. The order of the three lengths can be: first length ≤ second length ≤ third length.

[0385] As one possible implementation, the second length is 2 times the first length. m1 ±a1 times, or the third length is 2 times the first length. m2 ±b1 times. Where m2 is greater than m1, and m1 and m2 are positive integers greater than or equal to 1. a1 and b1 are natural numbers, such as a1, b1 = 0, 1, 2, ... For example, the first length is 1024, the second length is 2048, and the third length is 4096. Refer to the descriptions of the four lengths in the first possible implementation above; they will not be repeated here.

[0386] As one possible implementation, the two reliability sequences of the first length in the first reliability sequence described above can be the same reliability sequence. Alternatively, the two reliability sequences of the second length in the first reliability sequence can be the same reliability sequence. Alternatively, the two reliability sequences of the third length in the first reliability sequence can be the same reliability sequence.

[0387] For example, based on the above description, the segment index of the mother code and the first reliability sequence can satisfy one or more of the correspondences shown in Table 13.

[0388] Table 13

[0389] I 1 2 3 4 5 6 7 8 9 10 11 12 13 14 <![CDATA[N3]]> 0 0 0 0 0 0 1 1 1 1 2 2 2 2 <![CDATA[N2]]> 0 0 1 1 2 2 1 1 2 2 1 1 2 2 <![CDATA[N1]]> 1 2 1 2 1 2 1 2 1 2 1 2 1 2

[0390] Where N3 represents the number of reliability sequences of the third length, N2 represents the number of reliability sequences of the second length, and N1 represents the number of reliability sequences of the first length.

[0391] Based on the above scheme, a suitable reliability sequence can be selected according to the segmentation of the mother code, so as to better adapt to the scenario based on the long segmentation of the mother code.

[0392] In a seventh possible implementation, the first information includes the terminal's capabilities and / or indication information. This indication information indicates a first reliability sequence.

[0393] The terminal's capabilities may include at least one of the following: whether the terminal supports the selection or configuration of reliability sequences, the maximum number of supported reliability sequences, the maximum supported code length, or the length of the reliability sequences supported in the first scenario.

[0394] As one possible implementation, whether the terminal supports the selection or configuration of reliability sequences can also be understood as whether the terminal supports the selection or configuration of Polar codes.

[0395] For example, if the terminal supports the selection or configuration of reliability sequences, the RAN node can configure reliability sequences for the terminal, and the terminal can perform channel coding or channel decoding based on the reliability sequences configured by the RAN node. If the terminal does not support the selection or configuration of reliability sequences, the terminal can select a reliability sequence for channel coding or channel decoding on its own.

[0396] As one possible implementation, the maximum number of reliability sequences supported by the terminal can be understood as: the maximum number of reliability sequences the terminal can support, or the maximum number of reliability sequences the terminal can store.

[0397] For example, the maximum number of reliability sequences supported by the terminal can be 1, 2, 3, or 4. A number of 2 means the terminal supports a maximum of two reliability sequences, or stores a maximum of two reliability sequences. A number of 3 means the terminal supports a maximum of three reliability sequences, or stores a maximum of three reliability sequences.

[0398] As one possible implementation, the maximum code length supported by the terminal can be understood as the maximum code length after channel coding supported by the terminal. For example, this maximum code length can be 512, 1024, 2048, 4096, or 8192, etc., without limitation.

[0399] As one possible implementation, the first scenario could be enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), or massive machine-type communication (mMTC), or other service scenarios, without limitation.

[0400] For example, the first scenario can be the current business scenario of the terminal. In the case of eMBB in the first scenario, the reliability sequence length supported by the terminal can be 1024 or 2048, or it can be other lengths without limitation.

[0401] As one possible implementation, the terminal can report its capabilities to the RAN node. The RAN node can then select a first reliability sequence based on the terminal's capabilities and send the aforementioned indication information to the terminal to indicate its selected first reliability sequence. The terminal, upon receiving the indication information, selects the first reliability sequence accordingly. Alternatively, the terminal can select a first reliability sequence based on its capabilities and send the aforementioned indication information to the RAN node to indicate its selected first reliability sequence. The RAN node, upon receiving the indication information, selects the first reliability sequence accordingly. Alternatively, the RAN node can send indication information to the terminal indicating the first reliability sequence, and both the terminal and the RAN node select the first reliability sequence based on this indication information.

[0402] The following example illustrates the interaction process between a terminal and a RAN node, whereby the terminal reports its capabilities to the RAN node, the RAN node selects a first reliability sequence based on the terminal's capabilities, and sends an indication message to the terminal. For example,... Figure 7 As shown, the interaction process includes the following steps S701-S702.

[0403] S701, the terminal sends the first capability information to the RAN node. Correspondingly, the RAN node receives the first capability information from the terminal.

[0404] The first capability information indicates at least one of the following: the maximum number of supported reliable sequences, the maximum supported code length, or the length of reliable sequences supported in the first scenario. The capabilities indicated by the first capability information can be found in the foregoing descriptions and will not be repeated here.

[0405] For example, the maximum number of supported reliable sequences can be carried in the `maxSequenceTables` element. The maximum supported code length can be carried in the `maxCodeLength` element. Furthermore, the `maxSequenceTables` and `maxCodeLength` elements can be carried in the `PolarCodeCapability` element.

[0406] For example, the supported reliability sequence length in the first scenario can be carried in the maximum code length information element (maxCodeLength) in the capability configuration information element of the first scenario. In the case that the first scenario is eMBB, the capability configuration information element of the first scenario can be, for example, embbPolarConfig.

[0407] Optionally, the first capability information may also be used to indicate at least one of the following: the switching latency level of the reliability sequence, the supported application scenarios, measurement capabilities, the maximum bit rate supported in the eMBB scenario, the list decoding depth, etc.

[0408] The handover latency level of the reliability sequence indicates the latency of the handover reliability sequence; for example, the longer the reliability sequence, the greater the corresponding handover latency. Supported application scenarios indicate the application scenarios supported by the terminal, such as eMBB, URLLC, and mMTC. Measurement capabilities indicate the terminal's measurement capabilities, which can refer to the terminal's ability to perform and report various measurement tasks, including but not limited to signal strength, signal quality, and time difference. These measurement tasks can be used for network optimization, handover, and location purposes. The list decoding depth represents the number of candidate paths maintained simultaneously during the decoding process.

[0409] For example, the switching latency level of the reliability sequence can be carried in the switchingLatency information element, the supported application scenarios can be carried in the supportedScenarios information element, and the measurement capability can be carried in the measurementCapability information element. Furthermore, the switchingLatency information element, the supportedScenarios information element, and the measurementCapability information element can be included in the PolarCodeCapability information element.

[0410] For example, the maximum supported bitrate in the eMBB scenario can be carried in the `maxCodeRate` element, and the list decoding depth can be carried in the `listDecodingDepth` element. Furthermore, the `maxCodeRate` and `listDecodingDepth` elements can be included in the `embbPolarConfig` element.

[0411] For example, based on the above examples and descriptions, a possible information cell structure for first capability information can be as follows:

[0412] PolarCodeCapability::=SEQUENCE{

[0413] maxSequenceTables INTEGER(1..4), -- Maximum number of reliable sequences supported

[0414] switchingLatency ENUMERATED{

[0415] ms0,ms1,ms2,ms5

[0416] },--Reliability sequence switching delay level

[0417] supportedScenarios ENUMERATED {--Supported application scenarios}

[0418] embb(0),

[0419] urllc(1),

[0420] mmtc(2)

[0421] }(SIZE(1..3)),

[0422] maxCodeLength INTEGER{--Maximum supported code length}

[0423] 512,1024,2048,4096

[0424] },

[0425] Measurement Capability

[0426] }

[0427] Capabilities in eMBB scenarios:

[0428] embbPolarConfig::=SEQUENCE{

[0429] `maxCodeLength INTEGER{1024,2048}`, -- The length of the reliability sequence supported in the eMBB scenario.

[0430] maxCodeRate ENUMERATED{0_8,0_9,0_95},

[0431] listDecodingDepthINTEGER(1..8)

[0432] }

[0433] As one possible implementation, the initial capability information can be carried in the UE Capability Information. The terminal can send this UE capability information to the RAN node after entering the connected state.

[0434] S702, the RAN node sends indication information to the terminal. Correspondingly, the terminal receives the indication information from the RAN node.

[0435] The indication information refers to a first reliability sequence. For example, the indication information may include an index of the first reliability sequence or an indication of the length of the first reliability sequence. The index of the first reliability sequence may be the index of the first reliability sequence within a set of reliability sequences.

[0436] As one possible implementation, the RAN node receives the first capability information, selects the first reliability sequence index based on the first capability information, and sends the indication information to the terminal.

[0437] For example, the first reliability sequence selected by the RAN node may satisfy at least one of the following: the length of the first reliability sequence is greater than or equal to the maximum code length supported by the terminal, or the length of the first reliability sequence is the length of a reliability sequence supported by the terminal in the first scenario, etc.

[0438] As one possible implementation, the indication information can be carried in an RRC message (such as an RRC Reconfiguration message) or in a DCI, without restriction.

[0439] For example, if the indication information is carried in an RRC message, the indication information may include an index of the first reliability sequence.

[0440] Optionally, this indication information may also include the maximum code length. For example, an example of RRC signaling is as follows:

[0441] PolarCodeConfig::=SEQUENCE{

[0442] maxCodeLength ENUMERATED{n1024,n2048,n4096,n8192},--Maximum code length

[0443] sequenceTableIndex INTEGER(0..7) -- Index of the first reliable sequence

[0444] }

[0445] For example, if this indication information is carried in the DCI, the length of the first reliability sequence can be indicated by the first field in the DCI. The value of the first field can also be understood as the index of the reliability sequence. This first field can be a newly added field (such as adding a SeqTableIdx field) or an existing field can be reused, without restriction.

[0446] For example, different values ​​of the first field can indicate different reliability sequence lengths. Taking a first field of two bits as an example, the correspondence between the values ​​of the first field and the length of the reliability sequence can be shown in Table 14.

[0447] Table 14

[0448]

[0449] Based on the example shown in Table 14, when the value of the first field is 01, the index of the first reliability sequence can be considered to be 01, and correspondingly, the length of the first reliability sequence is the first length. Furthermore, the code length in Table 14 can be understood as the corresponding encoding length or mother code length when a certain reliability sequence length is selected. For example, when the reliability sequence length is 1024, the code length is 512–1024; when the reliability sequence length is 4096, the code length is 1024–4096.

[0450] As one possible implementation, after step S702, the terminal can determine the first reliability sequence based on the indication information, and perform channel coding or channel decoding based on the first reliability sequence.

[0451] As one possible implementation, the first capability information in step S701 can be reported proactively by the terminal, or it can be reported by the terminal based on a request from the RAN node. For example, in the case where the terminal reports the first capability information based on a request from the RAN node, such as... Figure 7 As shown, before step S701, the process also includes the following steps S700a-S700b.

[0452] S700a: The terminal sends second capability information to the RAN node. Correspondingly, the RAN node receives the second capability information from the terminal.

[0453] As one possible implementation, the second capability information indicates support for the selection or configuration of reliability sequences. Please refer to the above explanation regarding whether the terminal supports the selection or configuration of reliability sequences; further details will not be repeated here.

[0454] As another possible implementation, the second capability information indicates whether the selection or configuration of a reliability sequence is supported. If the second capability information indicates support for the selection or configuration of a reliability sequence, step S700b is performed; if the second capability information indicates that the selection or configuration of a reliability sequence is not supported, the first reliability sequence can be selected in other ways, such as by selecting at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, the type of control information, or the type of physical channel.

[0455] As one possible implementation, the second capability information can be understood as a top-level capability flag. For example, it can be carried in the Polar Code Selection Support (polarCodeSelectionSupport) element. Furthermore, the polarCodeSelectionSupport element can be carried in the UE-CapabilityRAT-ContainerList. That is, a possible element structure could be as follows:

[0456] UE-CapabilityRAT-ContainerList::=SEQUENCE{ ...

[0458] polarCodeSelectionSupport ENUMERATED{supported}OPTIONAL -- Top-level capability flag

[0459] }

[0460] As one possible implementation, the second capability information can be carried in the RRC Setup Complete message. Of course, the second capability information can also be carried in other messages, without restriction.

[0461] The S700b RAN node sends capability request information to the terminal. Correspondingly, the terminal receives the capability request information from the RAN node.

[0462] The capability information request information is used to request the terminal to report the first capability information, or in other words, to request the terminal to report detailed capability information about the reliability sequence / Polar code.

[0463] As one possible implementation, the capability request information can be carried in the UE Capability Enquiry message. Of course, the capability request information can also be carried in other messages, without restriction.

[0464] As one possible implementation, in steps S700a-S702 above, the information exchanged between the terminal and the RAN node (such as first capability information, indication information, second capability information, and capability request information) can be channel coded or channel decoded using a fixed code length or reliability sequence.

[0465] Based on the above scheme, a reliability sequence can be rationally selected based on the terminal's capabilities. This avoids selecting a reliability sequence that the terminal does not support or exceeds its capabilities, improving the accuracy of reliability sequence selection and preventing transmission failures caused by unreasonable reliability sequence selection. Alternatively, the terminal can select a reliability sequence based on indication information from the RAN node, which reduces the complexity of reliability sequence selection, thereby reducing the terminal's power consumption and capability requirements.

[0466] In an eighth possible implementation, the first information includes the type of physical channel. The type of physical channel may include a control channel (which can also be understood as a physical control channel) or a data channel (which can also be understood as a physical data channel).

[0467] As one possible implementation, when the physical channel is a control channel, the length of the first reliability sequence is a first length; or, when the physical channel is a data channel, the length of the first reliability sequence is a second length.

[0468] Where the second length is greater than or equal to the first length. If the second length is greater than the first length, the second length is twice the first length. m1 ±a1 times. m1 is a positive integer greater than or equal to 1. a1 is a natural number, such as a1 = 0, 1, 2, ... For example, the first length is 1024 or 2048, and the second length is 2048, 4096, or 8192. Refer to the relevant descriptions of the first and second lengths in the first possible implementation above, which will not be repeated here.

[0469] In one possible implementation, the reliability sequence of the first length in this application can be understood as a base table, which reduces the complexity and latency of encoding and decoding. The reliability sequence of the second length can be understood as an extended table, which improves coding gain and coverage. The reliability sequence of the third length can be understood as an ultra-table, which can be applied to NTN networks (such as satellite communications) and ultra-long-distance transmission scenarios.

[0470] It should be noted that the above eight possible implementation schemes can be executed independently or in combination. For example, the reliability sequence can be selected by combining the length information related to the encoding and the type of parameters carried in the control information, or the reliability sequence can be selected by combining the type of parameters carried in the control information and the transmission condition information. This application does not specifically limit the combination of the above schemes.

[0471] The above describes the implementation of the first information and the selection of the first reliability sequence by the communication device based on the first information. Furthermore, this application also provides a communication method, in which the application process of the above scheme is illustrated by taking the first communication device as the channel encoder and the second communication device as the channel decoder as an example. Figure 8 As shown, the communication method includes the following steps:

[0472] S801, The first communication device selects a first reliability sequence from the reliability sequence set according to the first information.

[0473] The first communication device can be a terminal or a RAN node. The implementation of the first information and the selection of the first reliability sequence from the reliability sequence set based on the first information can be found in the aforementioned descriptions and will not be repeated here.

[0474] S802, the second communication device selects a first reliability sequence from the reliability sequence set based on the first information.

[0475] Wherein, if the first communication device is a terminal, the second communication device can be a RAN node or another terminal; if the first communication device is a RAN node, the second communication device can be a terminal.

[0476] As one possible implementation, the first information used by the first communication device is the same as or corresponds to the first information used by the second communication device. For example, both the first and second communication devices select a first reliability sequence from a set of reliability sequences based on encoding-related length information; or, if the first communication device is a RAN node and the second communication device is a terminal, the first communication device selects the first reliability sequence based on the terminal's capabilities and sends indication information to the second communication device to indicate the first reliability sequence, and the second communication device selects the first reliability sequence based on the indication information.

[0477] It should be noted that, apart from the first information including the above-mentioned instruction information, there is no strict order between the above steps S801 and S802. Step S801 can be executed first, followed by step S802, or step S802 can be executed first, followed by step S801, or steps S801 and S802 can be executed simultaneously.

[0478] For example, when the first information includes indication information, in the first communication device and the second communication device, the party sending the indication information may first determine a first reliability sequence; the party receiving the indication information may determine the first reliability sequence based on the indication information.

[0479] S803. The first communication device performs channel coding on the information bit sequence of length K according to the first reliability sequence to obtain the coded bit sequence of length N.

[0480] As one possible implementation, the first communication device can acquire an information bit sequence of length K, map the information bit sequence of length K to a bit sequence to be encoded of length N based on a fourth reliability sequence of length N, and perform polar encoding on the bit sequence to be encoded to obtain an encoded bit sequence of length N. Here, the fourth reliability sequence is a subsequence of the first reliability sequence (the subsequence of the first reliability sequence includes the first reliability sequence itself). K and N are positive integers.

[0481] The information bit sequence can include the information bits themselves, and K can be the number of information bits included in the information bit sequence. Alternatively, the information bit sequence can include information bits and CRC bits, that is, the information bit sequence can be a CRC-encoded information bit sequence, and K can be the sum of the number of information bits and the number of CRC bits included in the information bit sequence. Or, the information bit sequence can include information bits, CRC bits, and check bits, and K can be the sum of the number of information bits, the number of CRC bits, and the number of check bits included in the information bit sequence.

[0482] Based on the above description of the information bit sequence and the fourth reliability sequence, the transmitting device can map the information bit sequence of length K to the bit sequence to be encoded of length N.

[0483] In the first possible design, the transmitting device can determine the reliability of each position in the bit sequence to be encoded based on the fourth reliability sequence, and map the information bit sequence of length K to the K positions with high reliability in the bit sequence to be encoded.

[0484] For example, with K being 4 and the fourth reliability sequence being 0, 1, 2, 4, 3, 5, 6, 7, the transmitting device can map the information bit sequence to the four positions with the highest reliability in the bit sequence to be encoded (i.e., [3, 5, 6, 7]).

[0485] In the second possible design, the transmitting device can determine the reliability of each position in the bit sequence to be encoded based on the fourth reliability sequence, and map the information bit sequence of length K to the K positions in the bit sequence to be encoded with high reliability, excluding the rate matching position.

[0486] In the third possible design, the transmitting device can determine the reliability of each position in the bit sequence to be encoded based on the first reliability sequence, and map the information bit sequence of length K to the K positions in the bit sequence to be encoded with high reliability, excluding the pre-frozen bit positions. The pre-frozen bit positions may include rate-matching bit positions and additionally frozen bit positions.

[0487] S804. The first communication device outputs an encoded bit sequence of length N. Correspondingly, the second communication device acquires the symbol sequence.

[0488] As one possible implementation, the first communication device outputs an coded bit sequence of length N, which may include: the first communication device outputting a first symbol sequence determined based on the coded bit sequence of length N. The symbol sequence may also be referred to as a modulation symbol sequence.

[0489] For example, the first communication device can modulate a coded bit sequence of length N to obtain a first symbol sequence. Alternatively, the first communication device can perform rate matching on the coded bit sequence of length N to obtain a rate-matched bit sequence, and then modulate the rate-matched bit sequence to obtain the first symbol sequence. Alternatively, the first communication device can interleave the coded bit sequence of length N to obtain an interleaved symbol sequence; further, the first communication device can also modulate the interleaved symbol sequence to obtain the first symbol sequence. Alternatively, the first communication device can perform rate matching on the coded bit sequence of length N to obtain a rate-matched bit sequence, interleave the rate-matched bit sequence to obtain an interleaved symbol sequence, and then modulate the interleaved symbol sequence to obtain the first symbol sequence.

[0490] Accordingly, the second communication device can receive the first symbol sequence output by the first communication device. For example, the first symbol sequence typically sent by the first communication device to the second communication device may be affected by interference during transmission through the channel, causing the second communication device to receive a first symbol sequence affected by noise and other interference, i.e., a second symbol sequence. In other words, the second symbol sequence is the first symbol sequence affected by noise and other interference.

[0491] Therefore, the second communication device can receive the first symbol sequence output from the first communication device. In fact, the second communication device receives the first symbol sequence affected by interference (i.e., the second symbol sequence). The second symbol sequence corresponds to an encoded bit sequence of length N. At this time, the symbol sequence obtained by the second communication device in step S804 is the second symbol sequence.

[0492] S805, the second communication device performs channel decoding on the symbol sequence according to the first reliability sequence to obtain the decoding sequence.

[0493] As one possible implementation, if polar coding is used in step S803, the second communication device can use a successive cancellation decoding (SC) algorithm to perform channel decoding on the symbol sequence according to the first reliability sequence.

[0494] For example, the second communication device can determine the information bits and frozen bits based on the first reliability sequence, thereby progressively calculating the log likelihood ratio (LLR) of the information bits. For an information bit, if LLR > 0, the bit is determined to be 0; if LLR < 0, the bit is determined to be 1. For a frozen bit, the bit is set to 0 regardless of the LLR value.

[0495] As one possible implementation, corresponding to the first communication device performing polarization coding, rate matching, and modulation on the information bit sequence, the second communication device can demodulate, de-rate-match, and polarize decode the information to be decoded to obtain the decoding result (i.e., the decoding sequence).

[0496] Based on this scheme, when selecting a reliability sequence, the first and second communication devices can take into account at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capabilities, the type of control information, the type of physical channel, or indication information used to indicate the first reliability sequence, thereby enabling them to select a suitable reliability sequence based on the above information.

[0497] In one possible implementation, for the above method embodiments, in a CU-DU architecture or ORAN system, the function of RAN node and terminal interaction can be implemented by DU or O-DU. The information sent by the RAN node to the terminal can be generated by DU or O-DU, or it can be generated by CU or O-CU and sent to DU or O-DU. The processing function of the RAN node can be implemented by CU or O-CU, or by DU or O-DU, or by a combination of CU and DU (or O-CU and O-DU), without limitation.

[0498] The communication method provided in this application has been described above. In addition, this application also provides a communication device for implementing the functions described in the above method embodiments.

[0499] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0500] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0501] Figure 9 A schematic diagram of a communication device 90 is shown. The communication device 90 includes a processing module 901 and a transceiver module 902. This communication device 90 can be used to implement the functions described above. The communication device can be a terminal or a RAN node.

[0502] In some embodiments, the communication device 90 may further include a storage module ( Figure 9 (Not shown in the image) is used to store program instructions and data.

[0503] In some embodiments, the transceiver module 902, also referred to as a transceiver unit, is used to implement sending and / or receiving functions. The transceiver module 902 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0504] In some embodiments, the transceiver module 902 may include a receiving module and a sending module, respectively configured to perform the receiving and sending steps performed by the communication device in the above method embodiments, and / or other processes to support the technology described herein; the processing module 901 may be configured to perform the processing steps performed by the communication device in the above method embodiments, and / or other processes to support the technology described herein.

[0505] The processing module 901 is configured to select a first reliability sequence from a set of reliability sequences based on first information. The set of reliability sequences includes at least two reliability sequences. The first information includes at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capability, indication information, the type of control information, or the type of physical channel. The indication information indicates the first reliability sequence. The processing module 901 is also configured to perform channel coding or channel decoding based on the first reliability sequence.

[0506] As one possible implementation, the communication device is used to achieve the functions of the aforementioned terminal:

[0507] The transceiver module 902 is used to send first capability information to the radio access network node, the first capability information indicating at least one of the following: the maximum number of supported reliability sequences, the maximum supported code length, or the length of the supported reliability sequences in a first scenario.

[0508] Optionally, the transceiver module 902 is also configured to send second capability information to the radio access network node, the second capability information indicating support for the selection or configuration of a reliability sequence.

[0509] Optionally, the transceiver module 902 is also configured to receive indication information from the radio access network node, the indication information including an index of a first reliability sequence.

[0510] As one possible implementation, this communication device is used to perform the functions of the aforementioned RAN node:

[0511] The transceiver module 902 is used to receive first capability information from the terminal, the first capability information indicating at least one of the following: the maximum number of supported reliability sequences, the maximum supported code length, or the length of the supported reliability sequences in the first scenario.

[0512] Optionally, the transceiver module 902 is also configured to receive second capability information from the terminal, which indicates support for the selection or configuration of a reliability sequence.

[0513] Optionally, the transceiver module 902 is also configured to send indication information to the terminal, the indication information including an index of the first reliability sequence.

[0514] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0515] In this application, the communication device 90 can be presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0516] In some embodiments, when Figure 9 When the communication device 90 is a chip or chip system, the function / implementation process of the transceiver module 902 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 901 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0517] Since the communication device 90 provided in this embodiment can execute the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

[0518] As one possible product form, the communication device described in the embodiments of this application can be implemented using one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0519] As another possible product form, the communication device described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, see [link to documentation]. Figure 10 , Figure 10 This is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of this application. The communication device 1000 includes a processor 1001 and a transceiver 1002. The communication device 1000 can be a terminal or a RAN node, or a chip or chip system therein. Figure 10 Only the main components of the communication device 1000 are shown. In addition to the processor 1001 and transceiver 1002, the communication device may further include a memory 1003 and input / output devices (not shown).

[0520] Optionally, the processor 1001 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs, thereby implementing the methods provided in the above-described method embodiments. The memory 1003 is mainly used to store software programs and data. The transceiver 1002 may include a radio frequency (RF) circuit and an antenna. The RF circuit is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0521] Optionally, the processor 1001, transceiver 1002, and memory 1003 can be connected via a communication bus.

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

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

[0524] In some embodiments, those skilled in the art will recognize that the above-described communication device 90 can be implemented in hardware. Figure 10 The communication device 1000 shown is in the form of this device.

[0525] As an example, Figure 9 The function / implementation process of the processing module 901 can be achieved through... Figure 10 The processor 1001 in the communication device 1000 shown calls computer execution instructions stored in the memory 1003 to implement the function. Figure 9 The function / implementation process of the transceiver module 902 in the middle can be obtained through Figure 10 This is achieved through the transceiver 1002 in the communication device 1000 shown.

[0526] As another possible product form, the communication device in this application can adopt... Figure 11 The shown composition structure, or including Figure 11 The components shown. Figure 11 This application provides a schematic diagram of the composition of a communication device 1100, which can be a terminal or a chip or system-on-a-chip in a terminal; or, it can be a RAN node or a module, chip or system-on-a-chip in a RAN node.

[0527] like Figure 11 As shown, the communication device 1100 includes at least one processor 1101 and at least one communication interface. Figure 11 (This is merely an example illustration, using a communication interface 1104 and a processor 1101 as examples.) Optionally, the communication device 1100 may also include a communication bus 1102 and a memory 1103.

[0528] Processor 1101 can be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 1101 can also be other devices with processing functions, such as circuits, devices, or software modules, without limitation.

[0529] The communication bus 1102 is used to connect different components in the communication device 1100, enabling communication between them. The communication bus 1102 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 11 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0530] Communication interface 1104 is used for communicating with other devices or communication networks. For example, communication interface 1104 can be a module, circuit, transceiver, or any device capable of communication. Optionally, the communication interface 1104 can also be an input / output interface located within processor 1101, used to implement signal input and signal output for the processor.

[0531] The memory 1103 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.

[0532] For example, the memory 1103 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and / or instructions; it may also be a random access memory (RAM) or other type of dynamic storage device capable of storing information and / or instructions; it may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0533] It should be noted that the memory 1103 may exist independently of the processor 1101 or may be integrated with the processor 1101. The memory 1103 may be located within or outside the communication device 1100, without limitation. The processor 1101 may be used to execute the instructions stored in the memory 1103 to implement the methods provided in the following embodiments of this application.

[0534] As an optional implementation, the communication device 1100 may further include an output device 1105 and an input device 1106. The output device 1105 communicates with the processor 1101 and can display information in various ways. For example, the output device 1105 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1106 communicates with the processor 1101 and can receive user input in various ways. For example, the input device 1106 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0535] In some embodiments, the hardware implementation will be apparent to those skilled in the art as described above. Figure 9 The communication device 90 shown can be adopted Figure 11 The communication device 1100 shown is in the form of this device.

[0536] As an example, Figure 9 The function / implementation process of the processing module 901 can be achieved through... Figure 11 The processor 1101 in the communication device 1100 shown calls computer execution instructions stored in memory 1103 to implement the function. Figure 9 The function / implementation process of the transceiver module 902 in the middle can be obtained through Figure 11 This is achieved through the communication interface 1104 in the communication device 1100 shown.

[0537] It should be noted that, Figure 11 The structure shown does not constitute a specific limitation on the communication device. For example, in other embodiments of this application, the communication device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0538] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0539] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0540] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0541] As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.

[0542] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0543] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0544] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0545] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0546] It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

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

[0548] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0549] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0550] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0551] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method is applied to a communication device, and the method includes: A first reliability sequence is selected from a set of reliability sequences based on first information. The set of reliability sequences includes at least two reliability sequences. The first information includes at least one of the following: encoding-related length information, the type of parameters carried in the control information, transmission condition information, mother code segmentation information, terminal capability, indication information, the type of control information, or the type of physical channel. The indication information indicates the first reliability sequence. Channel coding or channel decoding is performed based on the first reliability sequence.

2. The method according to claim 1, characterized in that, The set of reliability sequences contains at least two reliability sequences of different lengths.

3. The method according to claim 2, characterized in that, The set of reliability sequences includes a second reliability sequence; Wherein, a subsequence of the second reliability sequence is a third reliability sequence, or a subsequence of the second reliability sequence is a subsequence of the third reliability sequence, and the length of the third reliability sequence is 1024.

4. The method according to any one of claims 1-3, characterized in that, The encoding-related length information includes at least one of the following: mother code length, net payload bits, sequence length after rate matching, or cyclic redundancy check (CRC) length.

5. The method according to claim 4, characterized in that, If the number of net payload bits is less than a first net payload bit threshold, the length of the first reliability sequence is the first length; or... If the number of payload bits is greater than or equal to a first payload bit threshold and less than a second payload bit threshold, then the length of the first reliability sequence is the second length; or... If the number of net payload bits is greater than or equal to the second net payload bit threshold and less than the third net payload bit threshold, then the length of the first reliability sequence is the third length; or... If the number of net payload bits is greater than or equal to the third net payload bit threshold and less than the fourth net payload bit threshold, the length of the first reliability sequence is the fourth length.

6. The method according to claim 5, characterized in that, The first payload bit threshold, the second payload bit threshold, the third payload bit threshold, or the fourth payload bit threshold are determined based on the difference between 1024 and the CRC length.

7. The method according to claim 5 or 6, characterized in that, The second payload bit count threshold is 2 times the first payload bit count threshold. n1 The third net payload bit threshold is twice the first net payload bit threshold. n2 The fourth net payload bit threshold is twice the first net payload bit threshold. n3 The multiples of n2, n2 is greater than n1, n3 is greater than n2, and n1, n2, and n3 are positive integers greater than or equal to 1.

8. The method according to claim 4, characterized in that, If the length of the sequence after rate matching is less than the first rate matching length threshold, the length of the first reliability sequence is the first length; or, If the length of the sequence after rate matching is greater than or equal to the first rate matching length threshold and less than the second rate matching length threshold, then the length of the first reliability sequence is the second length; or... If the length of the sequence after rate matching is greater than or equal to the second rate matching length threshold and less than the third rate matching length threshold, then the length of the first reliability sequence is the third length; or... If the length of the sequence after rate matching is greater than or equal to the third rate matching length threshold and less than the fourth rate matching length threshold, then the length of the first reliability sequence is the fourth length.

9. The method according to any one of claims 1-8, characterized in that, The control information can be classified as either primary control information or secondary control information; or... The type of control information is broadcast control information.

10. The method according to claim 9, characterized in that, When the type of the control information is the first-level control information, the length of the first reliability sequence is the first length; When the type of control information is the secondary control, the length of the first reliability sequence is the second length; The control information is uplink control information, downlink control information, or sidelink control information, and the second length is greater than or equal to the first length.

11. The method according to claim 9, characterized in that, When the control information is uplink control information, and the uplink control information is first-level uplink control information, the length of the first reliability sequence is greater than or equal to 1024.

12. The method according to claim 9, characterized in that, When the type of control information is broadcast control information, the length of the first reliability sequence is greater than or equal to 1024.

13. The method according to any one of claims 1-8, characterized in that, The control information includes control information carried on a control channel or control information carried on a data channel; When the control information is control information carried on the data channel, the length of the first reliability sequence is a first length. or, When the control information is control information carried on the control channel, the length of the first reliability sequence is the second length, and the second length is greater than or equal to the first length.

14. The method according to any one of claims 1-13, characterized in that, The types of parameters carried in the control information include a first type of parameter or a second type of parameter, and the first type of parameter and the second type of parameter have different lengths; Wherein, if the parameters carried in the control information are of the first type, the length of the first reliability sequence is the first length; or, When the parameters carried in the control information are the second type of parameters, the length of the first reliability sequence is the second length, which is greater than or equal to the first length.

15. The method according to any one of claims 1-14, characterized in that, The transmission condition information includes at least one of the following: channel quality, modulation and coding scheme (MCS) index, code rate, modulation order, spectral efficiency, number of Hybrid Automatic Repeat Request (HARQ) retransmissions, or link direction.

16. The method according to claim 15, characterized in that, If the channel quality is greater than a first channel quality threshold, the length of the first reliability sequence is the first length; or... If the channel quality is less than or equal to a first channel quality threshold and greater than or equal to a second channel quality threshold, the length of the first reliability sequence is the second length; or, When the channel quality is less than the second channel quality threshold, the length of the first reliability sequence is the third length.

17. The method according to claim 15, characterized in that, If the MCS index belongs to the first index range, the length of the first reliability sequence is the first length; or... If the MCS index falls within the range of the second index, the length of the first reliability sequence is the second length; or... If the MCS index belongs to the third index range, the length of the first reliability sequence is the third length. Wherein, the smallest MCS index in the second index range is greater than the largest MCS index in the first index range, and the smallest MCS index in the third index range is greater than the largest MCS index in the second index range.

18. The method according to claim 15, characterized in that, If the number of HARQ retransmissions is greater than the first retransmission threshold and less than or equal to the second retransmission threshold, the length of the first reliability sequence is the first length. or, If the number of HARQ retransmissions is greater than the second retransmission threshold and less than or equal to the third retransmission threshold, the length of the first reliability sequence is the second length, which is greater than the first length.

19. The method according to claim 15, characterized in that, When the link direction is uplink, the length of the first reliability sequence is the second length; or... When the link direction is downlink, the length of the first reliability sequence is the first length, and the second length is greater than or equal to the first length.

20. The method according to any one of claims 5, 8, 10, 13-14, or 16-19, characterized in that, The second length is 2 times the first length. m1 The third length is twice the length of the first length. m2 Double, or the fourth length is twice the length of the first length. m3 The multiples of 1, m2 is greater than m1, m3 is greater than m2, and m1, m2, and m3 are positive integers greater than or equal to 1.

21. The method according to any one of claims 1-20, characterized in that, The mother code segmentation information includes the segmentation index of the mother code, and the segmentation index of the mother code corresponds to at least one of the following: the number of segments of the mother code, or the length of the reliability sequence corresponding to each segment.

22. The method according to any one of claims 1-21, characterized in that, When the communication device is a terminal, and the first information includes the indication information, the method further includes: Send first capability information to the radio access network node, the first capability information indicating at least one of the following: the maximum number of supported reliability sequences, the maximum supported code length, or the length of the supported reliability sequences in the first scenario.

23. The method according to claim 22, characterized in that, The method further includes sending second capability information to the radio access network node, the second capability information indicating support for the selection or configuration of a reliability sequence.

24. The method according to claim 22 or 23, characterized in that, The method further includes: The indication information received from the radio access network node includes an index of the first reliability sequence.

25. The method according to any one of claims 1-21, characterized in that, The communication device is a wireless access network node; when the first information includes the indication information, the method further includes: Receive first capability information from the terminal, the first capability information indicating at least one of the following: the maximum number of supported reliability sequences, the maximum supported code length, or the length of the supported reliability sequences in the first scenario.

26. The method according to claim 25, characterized in that, The method further includes: Receive second capability information from the terminal, the second capability information indicating support for the selection or configuration of reliability sequences.

27. The method according to claim 25 or 26, characterized in that, The method further includes: The indication information is sent to the terminal, and the indication information includes the index of the first reliability sequence.

28. The method according to any one of claims 1-27, characterized in that, The physical channel types include control channels or data channels; When the physical channel is the control channel, the length of the first reliability sequence is a first length; or... When the physical channel is the data channel, the length of the first reliability sequence is the second length, and the second length is greater than or equal to the first length.

29. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-28.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-28 to be performed.

31. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, the method described in any one of claims 1-28 is performed.