Data verification method and apparatus

Abstract

A data verification method and apparatus. The data verification method comprises: receiving at least one piece of data, the at least one piece of data comprising first data; and on the basis of the first data, determining a confidence level corresponding to the first data, wherein the confidence level is used for indicating a receiving condition of the first data. For example, the method is applied to a first device. In embodiments of the present application, the first data is verified by determining the confidence level of the first data, so that when the confidence level meets a corresponding condition, the first data does not need to be retransmitted, thereby reducing resource consumption caused by retransmission and reducing the delay caused by retransmission.

Description

Data verification method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 30, 2023, with application number "202311637532.1" and application name "Data Verification Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a data verification method and device. Background Art

[0003] The extended reality (XR) services in the new radio access technology (NR) of the fifth-generation (5G) communication system enable basic interaction between people and the virtual world. For 4K quality data, the average access rate is required to be around 120 megabits per second (Mbps), and the interaction latency is around 20 milliseconds (ms). However, for future services that require an immersive experience, such as XR pro and holographic experiences, lower latency and higher transmission rates will be required. How to meet these higher latency and transmission requirements is a problem that needs to be solved.

[0004] Summary of the Invention

[0005] The present invention provides a data verification method and apparatus for verifying first data by determining its confidence level. This method eliminates the need to retransmit the first data if the confidence level satisfies a corresponding condition, thereby reducing resource consumption and latency associated with retransmissions.

[0006] To achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, a data verification method is provided, comprising: receiving at least one data, the at least one data including first data; and determining, based on the first data, a confidence level corresponding to the first data, the confidence level indicating a reception status of the first data. For example, the method is applied to a first device.

[0008] The embodiment of the present application verifies the first data by determining the confidence level of the first data, so that when the confidence level meets the corresponding conditions, the first data does not need to be retransmitted, thereby reducing resource consumption caused by retransmission and reducing the delay caused by retransmission.

[0009] In one possible design, the confidence level is determined based on log-likelihood ratios (LLR) corresponding to the first data.

[0010] The embodiment of the present application applies LLR in the process of confirming the confidence of data so that retransmission is not indicated when the confidence is high, thereby reducing the probability of retransmission, reducing the resource consumption caused by retransmission, and reducing the delay caused by retransmission.

[0011] In one possible design, the confidence is determined based on the LLR corresponding to the first data, including at least one of the following methods: the confidence is determined based on the LLR corresponding to the code block (CB) in the first data that fails a cyclic redundancy check (CRC); the confidence is determined based on the number of first bits in the first data, where the first bit is a bit in the CB in the first data that fails CRC, and the number of first bits is determined based on the LLR corresponding to the CB in the first data that fails CRC; the confidence is determined based on the ratio of the number of first bits corresponding to the CB in the first data that fails CRC to the total code length of the first data.

[0012] The embodiments of the present application provide multiple ways to determine confidence, and appropriate ways can be used to determine confidence in different scenarios to improve universality.

[0013] In one possible design, the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails, including: the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails and an LLR reference value.

[0014] The embodiment of the present application can determine the number of first bits based on the LLR of each bit and the LLR reference value, and can quickly determine bits with insufficient confidence.

[0015] In one possible design, the LLR reference value is determined based on the LLR corresponding to the CB with successful CRC in the first data and a reference coefficient.

[0016] The embodiment of the present application can determine the LLR reference value based on the CB that has successfully completed the CRC check, and can more accurately determine the bits with insufficient confidence, thereby improving the accuracy of the confidence.

[0017] In one possible design, the method also includes at least one of the following steps: receiving third information, where the third information is used to indicate a reference coefficient; determining the reference coefficient based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data; and sending the third information.

[0018] The embodiments of the present application provide multiple ways to determine the reference coefficient, and appropriate ways can be used to determine the reference coefficient in different scenarios to improve universality.

[0019] In one possible design, the method further includes sending first information based on the confidence level and a first threshold, the first information being used to indicate whether to retransmit at least one data.

[0020] The embodiment of the present application can determine whether to retransmit at least one data based on the confidence level and the first threshold value, so that data with higher confidence levels does not need to be retransmitted, thereby reducing resource consumption caused by retransmission and reducing the delay caused by retransmission.

[0021] In one possible design, the method also includes: sending a confidence level; receiving first information, the first information being used to indicate whether to retransmit at least one data, the first information being determined based on the confidence level and a first threshold.

[0022] The embodiment of the present application can also send a confidence level, and the other end determines whether to retransmit the data based on the confidence level, which can reduce hardware requirements and improve universality.

[0023] In one possible design, sending the confidence level includes: determining an interval value of the confidence level based on the confidence level; and sending the interval value.

[0024] The embodiment of the present application may also send interval values ​​of confidence levels to reduce resource consumption caused by sending confidence levels.

[0025] In one possible design, the first information is used to indicate whether to retransmit at least one data, including: a confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

[0026] In the embodiment of the present application, when the confidence level is less than a first threshold, the first data is determined to be retransmitted. This allows some data to be received erroneously but with a confidence level greater than or equal to the first threshold without needing to be retransmitted, thereby reducing resource consumption and latency associated with retransmission.

[0027] In one possible design, the method also includes: receiving fourth information, the fourth information including the first threshold; and / or determining the first threshold based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data.

[0028] The embodiments of the present application provide multiple methods for determining the first threshold value, and a suitable method can be used to determine the reference coefficient in different scenarios to improve universality.

[0029] In one possible design, the method also includes: sending fourth information.

[0030] In the embodiment of the present application, the first device may also send the first threshold value when the first device determines the first threshold value, so that the peer end may determine whether to retransmit the data based on the first threshold value and the confidence level.

[0031] In one possible design, the method further includes: sending second information, where the second information is used to indicate whether to retransmit the first data based on the confidence level; or, receiving the second information.

[0032] The embodiment of the present application can also use the second information to indicate whether the method of retransmitting the first data based on the confidence indication is adopted, which can more flexibly configure the method of each device to perform data verification.

[0033] In one possible design, at least one data corresponds to at least one packet header, and the at least one packet header is used to indicate that the at least one data has fault-tolerant characteristics.

[0034] In the embodiments of the present application, the packet header carries the error-tolerance feature, allowing the receiving end to parse the error-tolerance feature and provide feedback based on the error-tolerance feature. For data with the same error-tolerance feature, the amount of retransmitted data can be appropriately reduced while ensuring that the data is correctly parsed, thereby reducing the resource consumption and latency caused by retransmissions.

[0035] In one possible design, the confidence level corresponding to the CB with a correct CRC in the first data is a default value or is empty.

[0036] In the embodiment of the present application, the confidence level corresponding to the CB with a correct CRC can be set to a specific value or omitted, so as to facilitate the subsequent determination and transmission of the confidence level of the first data.

[0037] In one possible design, the first data includes at least one of the following data units: CB; code block group (CBG); transport block (TB).

[0038] The embodiment of the present application provides a variety of data unit formats for first data, which can be applied to verify first data in different formats based on confidence, thereby improving universality.

[0039] In a second aspect, a data verification method is provided, comprising: sending at least one data, the at least one data including first data; receiving at least one of a confidence level and a first information, wherein the confidence level is used to indicate the reception status of the first data, and the first information is used to indicate whether to retransmit the at least one data.

[0040] The embodiment of the present application verifies the first data by determining the confidence level of the first data, so that when the confidence level meets the corresponding conditions, the first data does not need to be retransmitted, thereby reducing resource consumption caused by retransmission and reducing the delay caused by retransmission.

[0041] In one possible design, the confidence level is determined based on the LLR corresponding to the first data.

[0042] In one possible design, the confidence is determined based on the LLR corresponding to the first data, including at least one of the following methods: the confidence is determined based on the LLR corresponding to the CB where CRC fails in the first data; the confidence is determined based on the number of first bits in the first data, wherein the first bit is the bit in the CB where CRC fails in the first data, and the number of first bits is determined based on the LLR corresponding to the CB where CRC fails in the first data; the confidence is determined based on the ratio of the number of first bits corresponding to the CB where CRC fails in the first data to the total code length of the first data.

[0043] In one possible design, the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails, including: the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails and an LLR reference value.

[0044] In one possible design, the LLR reference value is determined based on the LLR corresponding to the CB with successful CRC in the first data and a reference coefficient.

[0045] In one possible design, the method also includes at least one of the following steps: receiving third information, where the third information is used to indicate a reference coefficient; determining the reference coefficient based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data; and sending the third information.

[0046] In one possible design, receiving at least one of the confidence level and the first information includes receiving the first information, wherein the first information is determined based on the confidence level and a first threshold.

[0047] In one possible design, receiving at least one of the confidence level and the first information includes: receiving the confidence level; determining the first information based on the confidence level and a first threshold; and sending the first information.

[0048] In one possible design, the first information is used to indicate whether to retransmit at least one data, including: a confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

[0049] In one possible design, receiving a confidence level includes receiving an interval value of the confidence level, where the interval value is determined based on the confidence level.

[0050] In one possible design, the first information is used to indicate whether to retransmit at least one data, including: a confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

[0051] In one possible design, the method also includes: receiving fourth information, the fourth information including the first threshold; and / or determining the first threshold based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data.

[0052] In one possible design, the method also includes: sending fourth information.

[0053] In one possible design, the method further includes: sending second information, where the second information is used to indicate whether to retransmit the first data based on the confidence level; or, receiving the second information.

[0054] In one possible design, at least one data corresponds to at least one packet header, and the at least one packet header is used to indicate that the at least one data has fault-tolerant characteristics.

[0055] In one possible design, the confidence level corresponding to the CB with a correct CRC in the first data is a default value or is empty.

[0056] In one possible design, the first data includes at least one of the following data units: CB; CBG; TB.

[0057] In a third aspect, a data verification apparatus is provided, comprising: a communication module configured to receive at least one data item, wherein the at least one data item includes first data; and a processing module configured to determine, based on the first data item, a confidence level corresponding to the first data item, wherein the confidence level indicates a reception status of the first data item. For example, the method is applied to a first device.

[0058] The embodiment of the present application verifies the first data by determining the confidence level of the first data, so that when the confidence level meets the corresponding conditions, the first data does not need to be retransmitted, thereby reducing resource consumption caused by retransmission and reducing the delay caused by retransmission.

[0059] In one possible design, the confidence level is determined based on the LLR corresponding to the first data.

[0060] In one possible design, the confidence is determined based on the LLR corresponding to the first data, including at least one of the following methods: the confidence is determined based on the LLR corresponding to the CB where CRC fails in the first data; the confidence is determined based on the number of first bits in the first data, wherein the first bit is the bit in the CB where CRC fails in the first data, and the number of first bits is determined based on the LLR corresponding to the CB where CRC fails in the first data; the confidence is determined based on the ratio of the number of first bits corresponding to the CB where CRC fails in the first data to the total code length of the first data.

[0061] In one possible design, the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails, including: the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails and an LLR reference value.

[0062] In one possible design, the LLR reference value is determined based on the LLR corresponding to the CB with successful CRC in the first data and a reference coefficient.

[0063] In one possible design, the communication module is also used to receive third information, where the third information is used to indicate a reference coefficient; and / or the processing module is also used to determine the reference coefficient based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data; and / or the communication module is also used to send third information.

[0064] In one possible design, the communication module is further used to send first information based on the confidence level and a first threshold, where the first information is used to indicate whether to retransmit at least one data.

[0065] In one possible design, the communication module is further used to: send a confidence level; receive first information, the first information being used to indicate whether to retransmit at least one data, the first information being determined based on the confidence level and a first threshold.

[0066] In a possible design, the processing module is further used to determine an interval value of the confidence level according to the confidence level; and the communication module is further used to send the interval value.

[0067] In one possible design, the first information is used to indicate whether to retransmit at least one data, including: a confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

[0068] In one possible design, the communication module is also used to receive fourth information, which includes a first threshold; and / or the processing module is also used to determine the first threshold based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data.

[0069] In one possible design, the communication module is further used to send fourth information.

[0070] In one possible design, the communication module is further used to: send second information, where the second information is used to indicate whether to retransmit the first data based on the confidence level; or receive second information.

[0071] In one possible design, at least one data corresponds to at least one packet header, and the at least one packet header is used to indicate that the at least one data has fault-tolerant characteristics.

[0072] In one possible design, the confidence level corresponding to the CB with a correct CRC in the first data is a default value or is empty.

[0073] In one possible design, the first data includes at least one of the following data units: CB; CBG; TB.

[0074] In a fourth aspect, a data verification device is provided, including: a communication module for sending at least one data, the at least one data including first data; the communication module is also used to receive at least one of a confidence level and a first information, wherein the confidence level is used to indicate the reception status of the first data, and the first information is used to indicate whether to retransmit at least one data.

[0075] The embodiment of the present application verifies the first data by determining the confidence level of the first data, so that when the confidence level meets the corresponding conditions, the first data does not need to be retransmitted, thereby reducing resource consumption caused by retransmission and reducing the delay caused by retransmission.

[0076] In one possible design, the confidence level is determined based on the LLR corresponding to the first data.

[0077] In one possible design, the confidence is determined based on the LLR corresponding to the first data, including at least one of the following methods: the confidence is determined based on the LLR corresponding to the CB where CRC fails in the first data; the confidence is determined based on the number of first bits in the first data, wherein the first bit is the bit in the CB where CRC fails in the first data, and the number of first bits is determined based on the LLR corresponding to the CB where CRC fails in the first data; the confidence is determined based on the ratio of the number of first bits corresponding to the CB where CRC fails in the first data to the total code length of the first data.

[0078] In one possible design, the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails, including: the number of first bits is determined based on the LLR corresponding to the CB where the CRC fails and an LLR reference value.

[0079] In one possible design, the LLR reference value is determined based on the LLR corresponding to the CB with successful CRC in the first data and a reference coefficient.

[0080] In one possible design, the apparatus further includes a processing module. The communication module is further configured to receive third information indicating a reference coefficient; and / or the processing module is configured to determine the reference coefficient based on at least one of a signal quality between the first device and the second device, a service type corresponding to the first data, and a service priority corresponding to the first data; and / or the communication module is further configured to send the third information.

[0081] In a possible design, the communication module is further used to receive first information, where the first information is determined based on a confidence level and a first threshold.

[0082] In one possible design, the communication module is further used to receive the confidence level; the processing module is further used to determine the first information based on the confidence level and the first threshold; and the communication module is further used to send the first information.

[0083] In one possible design, the first information is used to indicate whether to retransmit at least one data, including: a confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

[0084] In a possible design, the communication module is further used to: receive an interval value of the confidence level, where the interval value is determined based on the confidence level.

[0085] In one possible design, the first information is used to indicate whether to retransmit at least one data, including: a confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

[0086] In one possible design, the communication module is also used to receive fourth information, which includes a first threshold; and / or the processing module is also used to determine the first threshold based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data.

[0087] In a possible design, the communication module is further used to: send fourth information.

[0088] In one possible design, the communication module is further used to: send second information, where the second information is used to indicate whether to retransmit the first data based on the confidence level; or receive second information.

[0089] In one possible design, at least one data corresponds to at least one packet header, and the at least one packet header is used to indicate that the at least one data has fault-tolerant characteristics.

[0090] In one possible design, the confidence level corresponding to the CB with a correct CRC in the first data is a default value or is empty.

[0091] In one possible design, the first data includes at least one of the following data units: CB; CBG; TB.

[0092] In a fifth aspect, a data verification device is provided. The data verification device includes: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the data verification device executes the data verification method of any of the above aspects.

[0093] In the sixth aspect, a chip system is provided, which includes a processor and an input / output port, the processor is used to implement the processing functions involved in the data verification method of any aspect of the above aspects, and the input / output port is used to implement the receiving and sending functions involved in the data verification method of any aspect of the above aspects.

[0094] In one possible design, the chip system also includes a memory, which is used to store program instructions and data for implementing the functions involved in the data verification method of any of the above aspects.

[0095] The chip system may be composed of chips, or may include chips and other discrete devices.

[0096] In a seventh aspect, a communication system is provided, which includes a relay device that executes any method of any of the above aspects, and a network device that executes any method of any of the above aspects.

[0097] In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions, which, when executed on a computer, cause the computer to execute the data verification method according to any of the above aspects.

[0098] In a ninth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer executes the data verification method designed in any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0099] FIG1 is an exemplary diagram of the architecture of a communication system provided in an embodiment of the present application;

[0100] FIG2 is a schematic diagram of a hybrid automatic repeat request parallel transmission provided by an embodiment of the present application;

[0101] FIG3 is an example diagram of a hybrid automatic repeat request feedback based on code block groups provided in an embodiment of the present application;

[0102] FIG4 is a schematic diagram of a communication scenario provided in an embodiment of the present application;

[0103] FIG5 is a schematic diagram of another communication scenario provided in an embodiment of the present application;

[0104] FIG6 is a schematic diagram of another communication scenario provided in an embodiment of the present application;

[0105] FIG7 is a schematic diagram of another communication scenario provided in an embodiment of the present application;

[0106] FIG8 is a schematic diagram of a data verification method provided in an embodiment of the present application;

[0107] FIG9 is a schematic diagram of another data verification method provided in an embodiment of the present application;

[0108] FIG10 is a schematic diagram of image restoration comparison provided by an embodiment of the present application;

[0109] FIG11 is a schematic diagram of a data addition header provided in an embodiment of the present application;

[0110] FIG12 is a schematic diagram of the structure of a media access control protocol data unit provided in an embodiment of the present application;

[0111] FIG13 is a schematic diagram of another media access control protocol data unit structure provided in an embodiment of the present application;

[0112] FIG14 is a schematic diagram of a transmission block division according to an embodiment of the present application;

[0113] FIG15 is a schematic diagram of a packet header position provided in an embodiment of the present application;

[0114] FIG16 is a schematic diagram of another packet header position provided in an embodiment of the present application;

[0115] FIG17 is a schematic diagram of data transmission from a media access control layer to a physical layer according to an embodiment of the present application;

[0116] FIG18 is a schematic diagram of another embodiment of the present application providing data transmission from the media access control layer to the physical layer;

[0117] FIG19 is a schematic diagram of another embodiment of the present application, wherein the media access control layer provides data transmission to the physical layer;

[0118] FIG20 is a schematic diagram of data transmission from a media access control layer to a physical layer according to another embodiment of the present application;

[0119] FIG21 is an interactive diagram of a data verification method provided in an embodiment of the present application;

[0120] FIG22 is an interactive diagram of another data verification method provided in an embodiment of the present application;

[0121] FIG23 is a schematic diagram of another data verification method provided in an embodiment of the present application;

[0122] FIG24 is a schematic diagram of another data verification method interaction provided by an embodiment of the present application;

[0123] FIG25 is an interactive diagram of another data verification method provided in an embodiment of the present application;

[0124] FIG26 is a flow chart of a data verification method provided in an embodiment of the present application;

[0125] FIG27 is a flow chart of another data verification method provided in an embodiment of the present application;

[0126] FIG28 is a schematic diagram of a data verification device provided in an embodiment of the present application;

[0127] Figure 29 is a schematic diagram of another data verification device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0128] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0129] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0130] The terms "first" and "second" in the description and drawings of the embodiments of the present application are used to distinguish different objects, or to distinguish different treatments of the same object. Words such as "first" and "second" can distinguish between identical or similar items with substantially the same functions and effects. For example, the first device and the second device are merely used to distinguish different devices and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences.

[0131] "At least one" means one or more, and "a plurality" means two or more.

[0132] In the description of the embodiments of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the embodiments of the present application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0133] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural 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 plural.

[0134] In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.

[0135] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0136] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the embodiment of the present application, the size of the sequence number of each process does not mean 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 embodiment of the present application.

[0137] It can be understood that in the embodiments of the present application, "when" and "if" both mean that corresponding processing will be performed under certain objective circumstances, and do not limit the time, nor do they require any judgment action when implementing, nor do they mean that there are other limitations.

[0138] It is understood that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. In certain scenarios, they may also be combined with other features as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.

[0139] In the embodiments of the present application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In the various embodiments of the present application, and the various implementation methods / implementation methods / implementation methods in the various embodiments, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The implementation methods of the embodiments of the present application described below do not constitute a limitation on the scope of protection of the embodiments of the present application.

[0140] FIG1 is an example diagram of the architecture of a communication system provided in an embodiment of the present application.

[0141] As shown in FIG. 1 , the communication system involved in the embodiment of the present application may include at least one terminal 110 and a network device 120 .

[0142] Terminal 110 and network device 120 communicate wirelessly. Network device 120 may be a wireless access network device. Terminals and wireless access network devices may be connected to each other via wired or wireless means. Figure 1 is merely a schematic diagram. The communication system may also include other network devices, such as wireless relay devices, wireless backhaul devices, and core network devices, which are not shown in Figure 1. The connection relationships between devices are not limited to the methods listed above.

[0143] The radio access network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it may also be a module or unit that performs some of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU). The radio access network device may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. In other embodiments, the radio access network device may also be an access network device in an open RAN (O-RAN). In O-RAN, the CU may be referred to as an open CU (O-CU), the DU may be referred to as an open DU (O-DU), and the RU may be referred to as an open RU (O-RU). The embodiments of the present application do not limit the specific technologies and device forms used by the wireless access network equipment. The wireless access network equipment is sometimes referred to as the network equipment. For ease of description, the following description uses a base station as an example of the wireless access network equipment.

[0144] A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal devices.

[0145] Base stations and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminal devices.

[0146] Communication between base stations and terminals, between base stations, and between terminals can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0147] In an embodiment of the present application, the function of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem including a base station function. The control subsystem including the base station function here may be a control center in the application scenarios of the above-mentioned terminal devices such as smart grid, industrial control, intelligent transportation, smart city, etc. The function of the repeater may also be performed by a module (such as a chip or a modem) in the repeater, or by a device including a relay function. The function of the terminal may also be performed by a module (such as a chip or a modem) in the terminal, or by a device including a terminal function.

[0148] A wireless communication system includes communication devices that can communicate wirelessly using air interface resources. These devices can include network devices and terminal devices. Network devices can also be referred to as base stations. Air interface resources can include at least one of time domain resources, frequency domain resources, code resources, and space resources.

[0149] For the current XR services in 5G NR, the average access rate for 4K image quality is about 120Mbps, and the latency is about 20ms. The more typical 4K XR service requires a rate of 35Mbps, 60 frames per second, and the air interface latency is usually within 10ms. For immersive experience scenarios such as XR pro and holograms, the requirements for cellular communications will be higher, and the average access rate will increase from 120Mbps for 4K to 2 gigabits per second (Gbps) for about 16K. In addition, the interactive latency requirement will be further improved, from the current 20ms to about 5ms. Obviously, this puts forward further evolution requirements for 5G. It can be seen that XR services have the characteristics and requirements of low latency and high speed.

[0150] While traditional Internet video communication technologies have undergone extensive research, including areas like congestion control and bitrate adaptation, they still face challenges. In real-time video applications, packet jitter and loss significantly negatively impact the user experience. When packets jitter, they arrive at the receiver at irregular speeds, leading to instability in video decoding and playback. When packets are lost, they need to be retransmitted, introducing additional latency and hindering the timely decoding of multiple frames, resulting in video freezes and choppy playback. In current communication systems, feedback retransmission, a mature technology, effectively implements error control.

[0151] The hybrid automatic repeat request (HARQ) mechanism of the media access control (MAC) layer is a retransmission mechanism that enables the sender to quickly retransmit based on the feedback result by immediately feeding back the result of information transmission success or failure at the receiving end.

[0152] Referring to Figure 2, the HARQ mechanism uses a stop-and-wait protocol, which has two key features. First, the receiver sends feedback to the transmitter. Regardless of whether the message is received correctly, the receiver must provide feedback to the transmitter. Second, the transmitter must receive feedback before continuing to send messages. It will not send the next message until the previous one has been acknowledged.

[0153] The stop-and-wait protocol requires the transmitter to stop and wait for feedback from the receiver each time it sends information. Just like HARQ process 1, HARQ process 2, and HARQ process 3 in Figure 2, for each HARQ process, after sending the corresponding transport block (TB), the transmitter will wait for feedback information from the receiver for the corresponding TB. If the receiver does not successfully receive TB1 sent on HARQ process 1, the receiver can feedback a negative acknowledgement (NACK) to indicate that the data transmission on the HARQ process has failed. Similarly, for HARQ process 2 and HARQ process 3, if the receiver successfully receives the TB transmitted on the corresponding HARQ process, it can feedback an acknowledgment (ACK) to indicate that the data transmission on the HARQ process has been successful. Regardless of the HARQ process, the transmitter will send new data only after receiving the ACK or NACK feedback from the receiver. If the transmitting end receives NACK for HARQ process 1, TB1 can be retransmitted. If ACK is received for HARQ process 2 and HARQ process 3, new TBs such as TB4 and TB5 can be transmitted on the corresponding HARQ processes.

[0154] Assuming that multiple HARQ processes are executed serially, the use of a stop-and-wait protocol will result in very low throughput. Therefore, for example, Figure 2 shows a schematic diagram of parallel transmission of multiple HARQ processes. Multiple HARQ processes are often processed in parallel, so that when one HARQ process is waiting for confirmation, the transmitter can continue to send information through another HARQ process. Similarly, when the receiver is processing information received by one process, it can also continue to receive information through another process. Multiple HARQ processes processed in parallel can form a HARQ entity, and each uplink or downlink carrier can be considered to correspond to a HARQ entity. In some scenarios, a HARQ entity is allowed to support a maximum of 16 HARQ processes. Each HARQ process has independent HARQ feedback.

[0155] In some examples, if the transmitter transmits TBs in code block (CB) units, the receiver can provide feedback on CBs with coding errors. This allows the transmitter to retransmit the CBs with decoding errors. This reduces retransmission overhead compared to retransmitting the entire TB. However, when providing feedback in CB units, since a TB contains multiple CBs, the amount of feedback information increases significantly, leading to a corresponding increase in control signaling overhead. In some examples, a compromise approach has been introduced in NR: code block group (CBG)-based retransmission, where multiple CBs are grouped into a single CBG and feedback is provided on a per-CBG basis. Of course, it is also possible to retransmit only the CBGs with errors. Compared to retransmitting the entire TB, CBG-based retransmission reduces resource consumption. Furthermore, compared to providing feedback on each CB, CBG-based feedback reduces signaling overhead.

[0156] In some cases, a TB can be divided into 2, 4, 6, or 8 CBGs, depending on the number of CBs initially transmitted. Network equipment can indicate the CBG division method to the terminal through higher-layer signaling parameters. Once the CBG division is completed, the mapping between each CBG and CB is fixed and remains unchanged even after multiple retransmissions, thus ensuring the accuracy of the retransmitted information.

[0157] Figure 3 shows a schematic diagram of HARQ feedback based on CBGs. As can be seen, the transmitter can divide 1TB into four CBGs: CBG0, CBG1, CBG2, and CBG3. CBG0 and CBG3 are successfully received by the receiver, while CBG1 and CBG2 fail to be received by the receiver. The receiver can then provide feedback based on the CBGs, providing an ACK or NACK for each CBG. Based on the receiver's feedback, the transmitter can determine whether to retransmit CBG1 or CBG2. Upon receiving the retransmitted CBG1 or CBG2, the receiver can delete the cache of the erroneously received CBG1 or CBG2. The receiver can also provide an ACK to inform the transmitter that retransmission is not necessary and that new data can be transmitted. For example, when retransmitting, the transmitter can use a new data indicator (NDI) to indicate whether the data is initially transmitted or retransmitted. If the NDI indicates initially transmitted data, the receiver will consider all data to be initially transmitted data. If the NDI indicates retransmitted data, the receiving end can determine which CBGs are retransmitted based on the code block group transmission information (CBGTI) in the downlink control information (DCI). It can also determine whether the cached content of the same CBG received previously is still available based on the code block group flushing out information (CBGFI). Referring to Figure 3, when the sending end sends retransmission information, the CBGTI can be 0110, indicating that the second and third CBGs are the retransmitted CBGs. A CBGFI of 0 indicates that the cached CBG1 and CBG2 can be cleared.

[0158] In the retransmission scheme described above, the receiving end can use a cyclic redundancy check (CRC) to determine whether the data has been successfully received. For example, a checksum of R bits is appended to the K-bit data sent, and then a new data frame is generated and sent to the receiving end. After receiving the data frame, the receiving end can verify whether the data has been received correctly based on the data in the frame and the checksum.

[0159] However, current CRC verification often suffers from data reception errors requiring feedback and retransmission, often failing to meet the requirements of some ultra-reliable low-latency communications (URLLC) data services. Reducing the HARQ feedback error rate requires increasing feedback signaling. This results in frequent HARQ feedback and significant control signaling overhead. Frequent retransmissions also lead to increased data resource overhead and increased latency. Therefore, reducing the resource and latency overhead associated with retransmissions is a pressing issue.

[0160] Therefore, an embodiment of the present application provides a data verification method that determines whether to retransmit the first data by determining the confidence level of the first data. If the confidence level meets the corresponding conditions, the first data does not need to be retransmitted, thereby reducing resource consumption and latency caused by retransmission.

[0161] Figures 4, 5, 6 and 7 show a variety of communication scenarios applicable to the embodiments of the present application. The embodiments of the present application can be applicable to point-to-point single-connection communication in a standalone (SA) scenario between a network device and a terminal. It is also applicable to multi-hop single-connection communication scenarios between network devices and terminals, such as those implemented by multiple relay devices (relay) 130. It can also be applicable to dual connectivity (DC) communication scenarios between multiple network devices and terminals. Among them, one network device in the DC scenario can be a macro base station, and the other network device can be a micro base station. It can also be applicable to multi-hop multi-connection communication scenarios, etc. It can be understood that only a limited number of communication scenarios are shown in the embodiments of the present application. The embodiments of the present application can also be applicable to any other possible communication scenarios, and the applicable network scenario architecture is not limited here. The embodiments of the present application can be applicable to any long term evolution (LTE), NR and other protocol frameworks.

[0162] The relay device 130 may be any possible relay device such as an integrated access and backhaul (IAB) node, a router, or the like.

[0163] The solutions provided in the embodiments of this application can be applied to wireless communications between communication devices. Wireless communications can include wireless communications between network devices and terminals, wireless communications between network devices, and wireless communications between terminals. In the embodiments of this application, the term "wireless communications" can also be simply referred to as "communication," which can also be described as "data transmission," "information transmission," or "transmission."

[0164] The embodiments of the present application can be used for possible communication links such as uplink (UL), downlink (DL), access link, backhaul link, and sidelink (SL), and the embodiments of the present application are not limited here. From the perspective of business scenarios, the embodiments of the present application are applicable to various scenarios, such as layered data coding in XR services and uplink high-capacity scenarios, and the embodiments of the present application are not limited here.

[0165] FIG8 is a schematic diagram of a data verification method provided in an embodiment of the present application.

[0166] As shown in FIG8 , the communication process can be applied to, but not limited to, the communication scenarios shown in FIG1 and FIG4 to FIG7 . In each embodiment of the present application, the transmitting end can also be referred to as the first device, and the receiving end can also be referred to as the second device. The method may include the following steps:

[0167] S101: A transmitting end sends at least one data to a receiving end.

[0168] In some embodiments, a transmitting end may send at least one data item to a receiving end. The at least one data item may include first data item. The first data item may be any one of the at least one data item. In some embodiments, a receiving end may receive at least one data item sent by the transmitting end. For example, the receiving end receives the first data item sent by the transmitting end.

[0169] In some embodiments, the transmitting end can be any of the devices mentioned above, such as a terminal, a network device, etc. The receiving end can also be any of the devices mentioned above, such as a terminal, a network device, etc. For example, the transmitting end is a base station and the receiving end is a terminal, or the transmitting end is a terminal and the receiving end is a base station, or both the transmitting end and the receiving end are terminals. It can be considered that the transmitting end and the receiving end can be different devices in different communication scenarios. The specific forms of the transmitting end and the receiving end can be determined based on the actual communication scenario, and the embodiments of the present application do not limit this.

[0170] In some embodiments, the first data may be divided in units of CB, that is, the first data is one CB.

[0171] In some embodiments, the first data may be divided into CBG units, that is, the first data is one CBG. Then, the first data may include multiple CBs.

[0172] In some embodiments, the first data may be divided into TB units, that is, the first data is one TB. Then the first data may include multiple CBGs, and each CBG may include multiple CBs.

[0173] S102: The receiving end determines the confidence level corresponding to the first data based on the first data.

[0174] In some embodiments, the receiving end may determine the confidence level corresponding to the first data received in S101, wherein the confidence level may be used to indicate whether to retransmit the corresponding first data.

[0175] For example, the receiving end may perform a CRC check on the received first data. For first data with CRC check errors, the receiving end may determine the confidence level of such first data to indicate whether such first data with CRC check errors needs to be retransmitted. It can be considered that the confidence level corresponding to the first data represents the reliability of the received first data. When the confidence level indicates that the received first data is more reliable, the receiving end is more inclined not to retransmit the first data. When the confidence level indicates that the first data is less reliable, the receiving end is more inclined to retransmit the first data.

[0176] For another example, there may also be a corresponding confidence level for first data that is correct through CRC verification, or the confidence level for such first data that is correct through CRC verification may be omitted.

[0177] In the various embodiments of the present application, descriptions such as CRC check passed, CRC correct, CRC check correct, CRC success, and CRC check success may be considered to have the same meaning, indicating that the data is received correctly after CRC check. Descriptions such as CRC check failed, CRC error, CRC error, CRC check error, CRC check error, and CRC check unsuccessful may be considered to have the same meaning, indicating that the data is received incorrectly after CRC check.

[0178] In some embodiments, the confidence level corresponding to the first data may be determined based on the log-likelihood ratios (LLRs) corresponding to the first data. In some examples, the LLRs may be determined for bits in the data. For example, assuming x k,q is the qth bit of the transmitted symbol S of the kth transmitting antenna, then for this x k,q The LLR of the posterior probability can be expressed by formula 1,

[0179] Among them, P(x k,q =0|y) means that when the received symbol is y, the x in the transmitted symbol S k,q The probability of being 0. Similarly, P(x k,q =1|y) means that when the received symbol is y, the x in the transmitted symbol S k,q The probability of being 1. Therefore, LLR(x k,q ) can be considered to represent the x k,q Whether a bit is more likely to be 0 or 1.

[0180] In related technologies, after receiving a wireless signal, the receiver can perform channel equalization and detection, outputting the LLR value corresponding to each bit to a channel decoder. For example, the channel decoder can be a low-density parity check (LDPC) decoder. The channel decoder can iteratively recover the transmitted bit based on the LLR corresponding to each bit. A CRC check is then performed to verify the accuracy of the bit recovery. In this technology, LLRs are only utilized during the bit recovery phase. For example, LLR values ​​are used to determine the likelihood that a received bit is 0 or 1.

[0181] Considering that LLR has the characteristic of reflecting the probability of the received bit being 0 or 1, in the embodiment of the present application, the absolute value of LLR can be taken. It can be understood from Formula 1 that a positive LLR value indicates that the x k,q The bit may be 0, and the LLR is negative, indicating that x k,q The bit may be 1. When the LLR value is positive, the larger the value is, the k,q The higher the probability that the bit is 0, the smaller the value is when the LLR is negative. k,q The higher the probability that the bit is 1, the higher the probability that the bit is 1. Therefore, by taking the absolute value of the LLR value, the absolute value of the LLR value can reflect the x k,q The reliability of a bit. A larger absolute value of the LLR indicates a higher reliability of the bit. Therefore, the present embodiment utilizes the LLR in the data confidence confirmation process. This allows the confidence level of partially received erroneous data to be determined based on the LLR. This allows retransmission to be omitted when the confidence level is high, thereby reducing the probability of retransmission, resource consumption caused by retransmission, and latency caused by retransmission.

[0182] The embodiments of the present application are as follows:

[0183] Method 1:

[0184] In some embodiments, the confidence level may be determined based on the LLR corresponding to the CB where the CRC fails in the first data.

[0185] For example, the confidence level of a CB that fails CRC can be determined. The average of the absolute values ​​of the LLRs of the bits in the CB can be used as the confidence level of the CB.

[0186] Where C represents the confidence level of the CB that failed CRC in the first data, which can be used to indicate the reliability of the CB that failed CRC. K represents the code length of the CB, which can also be considered as the total number of bits in the CB that failed CRC. The value of k ranges from 1 to K. k |LLR k | represents the sum of the absolute values ​​of the LLRs of the bits in the CB where the CRC fails.

[0187] From formula 1, we can see that for a CB that fails CRC, the higher the confidence of the CB, the higher the reliability of the CB. It can also be considered that the probability of transmission error of the CB is lower. Assuming that the CB that fails CRC contains 3 bits, the confidence of the CB can be expressed as

[0188] For another example, the sum of the absolute values ​​of the LLRs of the bits in the CB can be used as the confidence of the CB, as shown in Formula 3, C = ∑ k |LLR k |...Formula 3

[0189] In this way, the embodiment of the present application utilizes LLRs in the process of confirming the confidence of first data, allowing the confidence of partially erroneously received data to be determined based on the LLRs of the data. This allows for the subsequent process to avoid instructing retransmission when the confidence level is high, thereby reducing the probability of retransmission, reducing resource consumption caused by retransmission, and reducing the delay caused by retransmission.

[0190] Method 2:

[0191] In some embodiments, the confidence level can be determined based on the number of first bits. The first bit is a bit in the CB for which the CRC fails in the first data, and the number of first bits is determined based on the LLR corresponding to the CB for which the CRC fails in the first data. In various embodiments of the present application, the confidence level can also be considered to be determined based on the first bit. For example, the confidence level can be determined based on the number of first bits. In the embodiments of the present application, the number of first bits can also be referred to as the first bit quantity.

[0192] In some examples, the first bit quantity may refer to bits with insufficient confidence in the CB where the CRC fails in the first data, or bits with low confidence. In other examples, the first bit quantity may refer to bits with high confidence in the CB where the CRC fails in the first data. This is not limited in the embodiments of the present application.

[0193] This application will be described below using the example of the first bit quantity being bits with insufficient confidence, but those skilled in the art should understand that the embodiments of this application do not limit the first bit quantity to being bits with insufficient confidence or bits with high confidence.

[0194] For example, the number of bits with insufficient confidence in the CB that failed CRC, i.e., the number of first bits, can be counted. The confidence of the first data is represented by the number of first bits. For example, a larger number of first bits means that more bits in the CB that failed CRC are likely to be erroneous bits, and therefore the CB that failed CRC may be more likely to be retransmitted. Conversely, a smaller number of first bits means that more bits in the CB that failed CRC are likely to be bits that passed CRC verification, and therefore the CB that failed CRC may not be retransmitted.

[0195] In some embodiments, the number of first bits corresponding to the first data may be determined according to the LLR corresponding to the CB where the CRC fails and the LLR reference value.

[0196] For example, for a CB that fails CRC check, the first bit number can be obtained by determining the relationship between the LLR absolute value of each bit in the CB and the LLR reference value. The LLR reference value can be recorded as L ref .

[0197] For example, the absolute value of the LLR of a bit in the CB where the CRC fails in the first data is less than L ref , it can be considered that the confidence of the bit is insufficient. And add one when counting the number of the first bit. For example, the absolute value of the LLR of a bit is greater than or equal to L ref , it can be considered that the confidence of this bit is high and this bit is more likely to be the correct bit. In this case, the number of the first bit remains unchanged, that is, this bit is not counted in the number of the first bit. By comparing each bit of the CB with L ref By comparing, the number of bits with insufficient confidence in the CB can be obtained, that is, the first number of bits. The first number of bits can be used as the value of the confidence.

[0198] Of course, in some examples, it is also possible to verify the CRC failure of the CB based on the bits and L ref Compare and determine the first bit quantity. Among them, the selection of some bits can be determined according to the actual situation, for example, one bit is selected from every two bits and L ref Or, arbitrarily select a number of bits and compare them with L ref For comparison, the embodiments of the present application are not limited.

[0199] In some embodiments, the LLR reference value may be determined based on the LLR corresponding to the CB with successful CRC in the first data and a reference coefficient.

[0200] For example, the LLR value corresponding to the CB with correct CRC can be counted to determine L ref For example, the LLR value of the correct CB of CRC can be averaged. Refer to formula 4,

[0201] Among them, M R Indicates the total number of CBs that pass the CRC check. The value of m ranges from 1 to M. R .LLR m,k It represents the LLR value of the kth bit in the mth CB. “·” represents the multiplication operator. ε represents the reference coefficient, which is a constant and has a positive value. ε can also be called the LLR reference coefficient. Assume that the first data includes CB1, CB2 and CB3, where CB1 and CB2 are CBs with correct CRC check, CB1 contains 3 bits, and CB2 contains 3 bits, then L ref It can be expressed as Among them, |LLR 1,1 | is the absolute value of the LLR value of the first bit in CB1, |LLR 1,2 | and so on have similar meanings and will not be repeated in the embodiments of this application.

[0202] In some examples, assuming ε is 1, then L ref It can be considered as the average value of the absolute value of LLR in the correct CB of CRC. Assuming ε is greater than 1, then L ref will be higher than the average absolute value of LLR in the correct CB of CRC. Assuming ε is less than 1, then L ref It will be lower than the average absolute value of LLR in the CRC correct CB.

[0203] It can be understood that the larger the value of ε is, the more bits may have LLR absolute values ​​smaller than L ref The more first bits a CB has, the more likely it is that the CB has CRC errors. Therefore, it can be assumed that a larger value of ε indicates a greater tendency to retransmit data.

[0204] In some embodiments, the method further includes at least one of the following steps: receiving third information, the third information being used to indicate ε; determining a reference coefficient based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data; and sending the third information.

[0205] For example, the first device may receive third information sent by the second device, where the third information may be used to indicate a reference coefficient, that is, the third information may indicate ε. In this case, it may be considered that ε is determined by the second device.

[0206] For another example, the first device may determine the reference coefficient based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data. For example, the signal quality between the first device and the second device may be air interface traffic congestion, noise interference during signal transmission, obstacle obstruction, and the like. For another example, the service type corresponding to the first data may be a service requirement, such as the need for lower latency, higher transmission rate, and the like. For another example, the service priority may be expressed as whether the service corresponding to the first data is important. For example, a lower ε may be used for unimportant services to reduce the possibility of data retransmission. In this case, it can be considered that ε is determined by the first device.

[0207] For another example, the first device may send the third information to the second device. In this case, it can be considered that ε is determined by the first device.

[0208] Of course, the above examples do not specify which of the first and second devices is the transmitter and which is the receiver. In other words, the first device can be either a transmitter or a receiver. Of course, if the first device is a transmitter, the second device is a receiver. Conversely, if the first device is a receiver, the second device can be a transmitter.

[0209] The determination of the ε value is analyzed from the perspectives of uplink and downlink communications. For uplink communication, for example, the value of ε can be determined by the terminal based on service requirements, and the terminal can inform the network device through the application layer. Another example is that the network device can determine the ε value based on the air interface traffic congestion status.

[0210] During downlink communication, the value of ε can also be determined by the terminal according to business requirements and notified to the network device through the application layer. The network device then notifies the terminal through radio resource control (RRC) signaling, MAC control element (CE) and / or DCI. The purpose of doing this is because the ε determined by the terminal is application layer information, which is unknown to the physical layer. This method is needed to make the physical layer of the terminal know the value of ε. For another example, the network device can determine an ε value based on the air interface traffic congestion status. And notify the terminal through RRC signaling, MAC CE and / or DCI. For the network device, it can directly receive the ε determined by the terminal according to business requirements.

[0211] It is understood that ε can be determined by any one or more of the above methods, such as a device determining ε and sending it to a peer device. Alternatively, a device receives ε sent by another device and determines a new ε based on the signal quality and service type between the devices. The device then determines a suitable reference coefficient based on the received ε and the new ε. Optionally, the device can also reselect a suitable reference coefficient synchronously with other devices. The embodiments of the present application do not limit the method for determining ε.

[0212] In the above, the example of the first bit being a bit with insufficient confidence is taken. In other embodiments, the first bit may be a bit with high confidence. For example, the number of bits with high confidence in the CB where CRC fails may be counted. This number of bits may be referred to as the first bit number. The confidence of the first data is represented by the first bit number. For example, the more the first bit number is, the more bits in the CB where CRC fails may be correct bits, so the subsequent process may be more inclined not to retransmit the CB where CRC fails. Conversely, the fewer the first bit number is, the more inclined it may be to retransmit the CB where CRC fails.

[0213] Method 3:

[0214] In some embodiments, the confidence level may be determined based on the ratio of the number of first bits corresponding to CBs where CRC fails in the first data to the total code length of the first data.

[0215] In some examples, the ratio of the number of first bits to the total code length of the first data can be determined as the confidence level. For example, the number of first bits corresponding to CBs with CRC errors in the first data is accumulated and then divided by the total code length of the first data to obtain the corresponding ratio. This ratio can be used as the confidence level corresponding to the first data.

[0216] Optionally, the first bit quantity in this method is similar to the first bit quantity in Method 2, and may refer to bits with insufficient confidence in the CB where the CRC fails in the first data, or bits with low confidence. The first bit quantity may also refer to bits with high confidence in the CB where the CRC fails in the first data. This embodiment of the present application is not limited here.

[0217] It can be understood that this ratio can represent the proportion of bits with insufficient confidence in the first data to the entire data. A higher ratio can indicate that more bits in the first data have insufficient confidence, and the first data is more likely to be retransmitted. A lower ratio can indicate that fewer bits in the first data have insufficient confidence, and the first data is more likely not to be retransmitted.

[0218] For example, if the total code length of the first data is 3 bits, and 2 bits of the CB that failed the CRC check in the first data are bits with insufficient confidence, it can be determined that the proportion of bits with insufficient confidence is 2 / 3, and 2 / 3 can be used as the confidence of the first data.

[0219] In some examples, assuming that the transmitting end sends CB1, CB2, and CB3, where CB1 fails the CRC check, it can be determined whether to retransmit CB1 based on the confidence level of CB1.

[0220] In other examples, assuming that the sending end sends CBG1, CBG2 and CBG3, where CB1 in CBG2 fails the CRC check, the confidence level of CBG2 can be calculated based on the confidence level of CB1, and whether to retransmit CBG2 can be determined based on the confidence level of CBG2.

[0221] In some other examples, assuming that the transmitting end includes TB1, TB2, and TB3, and CB1 in TB2 fails the CRC check, the confidence of TB2 can be calculated based on the confidence of CB1, and whether to retransmit CBG2 can be determined based on the confidence of TB2.

[0222] The confidence level of CB1 in the above examples may be determined using any one of the above methods 1, 2, and 3.

[0223] The embodiment of the present application determines whether the first data needs to be retransmitted by determining the confidence level of the first data. If the confidence level meets the corresponding conditions, the first data does not need to be retransmitted, thereby reducing resource consumption and delay caused by retransmission.

[0224] FIG9 is a schematic diagram of another data verification method provided by an embodiment of the present application. As shown in FIG9, the method can be applied to the communication scenarios shown in FIG1, FIG4 to FIG7. The method may include the following steps:

[0225] S201: A transmitting end sends at least one data to a receiving end.

[0226] S202: The receiving end determines the confidence level corresponding to the first data based on the first data.

[0227] It can be understood that S201 is similar to S101, and S202 is similar to S102. The specific implementation process of S201 and S202 can refer to the description of the corresponding embodiment of the corresponding steps in Figure 8, and the embodiments of this application will not be repeated here.

[0228] S203: The receiving end determines the first information according to the confidence level corresponding to the first data.

[0229] In some embodiments, the receiving end may obtain the first information based on the confidence level corresponding to the first data determined in S202. The first information may be used to indicate whether to retransmit the at least one data received in S201.

[0230] For example, the receiving end can determine the first information based on the confidence level and the first threshold corresponding to the first data. For example, the first information can be a response message different from the traditional ACK and NACK. For example, the first information may include a first response and / or a second response. The first response and the second response can be considered as a response message different from the ACK and NACK in the related art. Among them, each response message corresponds to a first data. If the response message corresponding to a certain first data is a first response, it can indicate that the first data does not need to be retransmitted. If the response message corresponding to a certain first data is a second response, it can indicate that the first data needs to be retransmitted.

[0231] For example, the first response may be a feature acknowledgement (FACK), indicating that the corresponding first data transmission is successful, and the second response may be a feature negative acknowledgement (FNACK), indicating that the corresponding first data transmission fails.

[0232] In some examples, when the confidence level is determined based on the LLR corresponding to the CB where the CRC fails in the first data, the first threshold may be denoted as C threshold The receiving end can determine the confidence level of the first data and the C threshold Compare and determine the first information. If the confidence of the first data is greater than or equal to C threshold , then the confidence of the first data is considered to be high and can be determined as FACK, indicating that no retransmission is required. threshold , then the confidence of the first data is considered to be low and can be determined as FNACK, indicating that retransmission is required. Of course, for the confidence of the first data equal to C threshold Specifically, the confidence level of the first data can be dynamically adjusted to be equal to C according to the actual situation. threshold When the first data is retransmitted, it is considered that the first data is retransmitted, or not retransmitted. The embodiment of the present application is not limited here.

[0233] In some examples, FACK and FNACK can be fed back based on the CB. That is, the minimum feedback unit in the first information is the CB. The receiving end can determine whether the CB needs to be retransmitted based on the confidence level of the CB, that is, determine whether the CB corresponds to FACK or FNACK. The confidence level of the CB can be determined using Formula 2 or Formula 3 above.

[0234] The first information may include response messages corresponding to multiple CBs. For example, the confidence level of a CB is greater than or equal to C threshold , determine that the CB corresponds to FACK; the confidence of CB is less than C threshold , determine that the CB corresponds to FNACK.

[0235] For example, suppose the sender sends CB1 and CB2, and the receiver receives CB1 and CB2 and performs CRC check on them respectively. Assume that CB1 is the CB that succeeds the CRC check and CB2 is the CB that fails the CRC check. The receiver can determine the confidence level of CB2 and determine the confidence level of CB2 and CB2. threshold Assume that the confidence of CB2 is less than C threshold The receiving end may determine that CB2 corresponds to FNACK. For CB1, it may directly determine that the CB corresponds to FACK or directly omit it. The receiving end may send first information to the transmitting end, where the first information includes FNACK corresponding to CB2. Optionally, the first information also includes FACK corresponding to CB1.

[0236] In some examples, FACK and FNACK can be fed back based on CBGs, that is, the minimum feedback unit in the first information is a CBG. Then, based on the confidence of one or more CBs in the CBG, it can be determined whether the CBG needs to be retransmitted. For example, if a CBG includes four CBs, the confidence of the CBG can be determined based on the confidence of the four CBs in the CBG. For example, the confidence of the CBG can be the average of the confidences of the four CBs. For another example, the confidence of the CBG can be determined based on the confidence of some of the four CBs. For example, it can be determined based on the average of the confidences of two of the four CBs, or based on the average of the confidences of three of the four CBs, and so on.

[0237] It is clear that the average value is only one way to determine the confidence level of the CBG. The confidence level of some CBs in the CBG can also be calculated using any other possible method such as variance or standard deviation to obtain the confidence level of the CBG, which is not limited in this embodiment of the present application.

[0238] For example, the confidence level of CBG is greater than or equal to C threshold , determine that the CBG corresponds to FACK; the confidence of CBG is less than C threshold , determine that the CBG corresponds to FNACK.

[0239] For example, suppose the transmitter sends CBG1 and CBG2, and the receiver receives CBG1 and CBG2 and performs CRC check on the CBs in each CBG respectively. Assuming that the CRC check on each CB in CBG1 is successful, CB1 in CBG2 is the CB that succeeds the CRC check, and CB2 is the CB that fails the CRC check. The receiver can determine the confidence level of CB2 in CBG2. And determine the confidence level of CBG2 based on the confidence level of CB2. In some examples, the confidence level of CBG2 can also be determined based on the confidence level of CB1 and the confidence level of CB2, where the confidence level of CB1 can be a default value of 0. The receiver determines the confidence level of CBG2 based on the confidence level of CB1 and CB2. threshold Assume that the confidence of CBG2 is less than C threshold The receiving end may determine that CBG2 corresponds to FNACK. For CBG1, it may directly determine that the CBG corresponds to FACK or directly omit it. The receiving end may send first information to the transmitting end, where the first information includes FNACK corresponding to CBG2. Optionally, the first information also includes FACK corresponding to CBG1.

[0240] In some examples, FACK and FNACK can be fed back based on TB, that is, the minimum feedback unit in the first information is TB. Among them, a TB can include multiple CBGs, and each CBG can include multiple CBs. Therefore, the receiving end can determine the confidence of the CBG based on the confidence of one or more CBs in the CBG. And the confidence of the TB is determined by the confidence of one or more CBGs in the TB. For the method of determining the confidence of the CBG, reference can be made to the above-mentioned embodiment of determining the confidence of the CBG. The method of determining the confidence of the TB is similar to the method of determining the confidence of the CBG, and the embodiments of the present application will not be repeated here.

[0241] For example, the confidence level of TB is greater than or equal to C threshold , determine that the TB corresponds to FACK; the confidence of TB is less than C threshold , determine that the TB corresponds to FNACK.

[0242] It can be understood that, assuming that the sending end sends TB1 and TB2, the way in which the receiving end sends the first information to indicate which TB needs to be retransmitted is similar to the implementation process when the first data is CBG, and the embodiments of the present application will not be repeated here.

[0243] In some examples, when the confidence level is determined based on the number of first bits corresponding to CBs that fail CRC in the first data, the first threshold may be N threshold The receiving end can determine the confidence level of the first data and N threshold Compare and determine the first information. It can be understood that the confidence of the first data is related to N thresholdThe way of comparison is to compare the confidence level of the first data with C threshold The comparison method is similar, please refer to the above and C threshold The description of the related embodiments will not be repeated here.

[0244] For example, the receiving end can provide feedback based on CB. In this case, it can determine whether the CB needs to be retransmitted based on the number of first bits corresponding to the CB. For example, the number of first bits corresponding to the CB is greater than or equal to N threshold , determine that the CB corresponds to FACK; the number of the first bits corresponding to the CB is less than N threshold , determine that the CB corresponds to FNACK.

[0245] For another example, the receiving end may provide feedback based on a CBG. In this case, the receiving end may determine whether the CBG needs to be retransmitted based on the first bit number corresponding to the CBG. The first bit number of the CBG may be determined based on the first bit number of one or more CBs in the CBG. For another example, the receiving end may provide feedback based on a TB. In this case, the receiving end may determine whether the TB needs to be retransmitted based on the first bit number corresponding to the TB. The first bit number of the TB may be determined based on the first bit number of one or more CBGs in the TB. The first bit number of the CBG may be determined based on the first bit number of one or more CBs in the CBG.

[0246] It can be understood that the method for determining the first bit number of CBG can refer to the above-mentioned process of determining the confidence of CBG when determining the LLR based on CB, and the method for determining the first bit number of TB can refer to the process of determining the confidence of TB based on the LLR based on CB. The embodiments of this application will not be repeated here.

[0247] In some examples, when the confidence level is determined based on the ratio of the first bit quantity to the total code length of the first data, the first threshold value can be recorded as ρ threshold The receiving end can calculate the confidence level of the first data and ρ threshold Compare and determine the first information. It can be understood that the confidence of the first data is related to ρ threshold The way of comparison is to compare the confidence level of the first data with C threshold Compare or with N threshold The comparison method is similar, please refer to the above and C threshold Description of related embodiments, and threshold The description of the related embodiments will not be repeated here.

[0248] For example, the receiving end can provide feedback based on the CB. In this case, it can determine whether the CB needs to be retransmitted based on the ratio of the number of first bits corresponding to the CB to the total code length of the first data. For example, the ratio of the number of first bits corresponding to the CB to the total code length of the first data is greater than or equal to ρ threshold , determine that the CB corresponds to FACK; the ratio of the number of first bits corresponding to the CB to the total code length of the first data is less than ρ threshold , determine that the CB corresponds to FNACK.

[0249] For another example, the receiving end may provide feedback based on CBG. In this case, it may determine whether the CBG needs to be retransmitted based on the ratio of the first bit number corresponding to the CBG to the total code length of the first data. For another example, the receiving end may provide feedback based on TB. In this case, it may determine whether the TB needs to be retransmitted based on the ratio of the first bit number corresponding to the TB to the total code length of the first data. The first bit number of the CBG and the first bit number of the TB can refer to the description in the corresponding examples above, and will not be repeated in the embodiments of this application.

[0250] Obviously, the larger the number of first bits or the larger the proportion of the first bits to the total code length of the first data, the lower the reliability of the corresponding CB, CBG or TB.

[0251] In some embodiments, the first threshold can be dynamically adjusted based on current air interface transmission conditions, transmission quality requirements, and the like. For example, when air interface transmission conditions are good and transmission quality requirements are high, a higher first threshold can be selected. This allows for more data to be retransmitted when transmission conditions are met, ensuring that the receiving end can process the corresponding service based on more accurate data.

[0252] In some examples, the first threshold may be sent by a receiving end to another device. For example, it may be sent by a transmitting end. For example, the receiving end may receive fourth information sent by a transmitting end, and the fourth information includes the first threshold. In this case, the first threshold may be determined by the transmitting end.

[0253] In some examples, the first threshold may be determined based on at least one of the signal quality between the first device and the second device, the service type corresponding to the first data, and the service priority corresponding to the first data. For example, the first device and the second device may be a transmitter and a receiver. For example, the first device may be a transmitter and the second device may be a receiver. Alternatively, the first device may be a receiver and the second device may be a transmitter.

[0254] For example, the receiving end may determine the first threshold based on the signal quality between the receiving end and the transmitting end, such as the air interface traffic congestion between the transmitting end and the receiving end, the noise interference during signal transmission, the obstacle blocking condition, etc.

[0255] For example, the receiving end may determine the first threshold value according to the service type corresponding to the first data. For example, the service type may include a requirement for lower latency, higher transmission rate, etc.

[0256] For example, the receiving end may determine the first threshold based on the service priority corresponding to the first data. The service priority may indicate whether the service corresponding to the first data is important. For example, a lower first threshold may be used for unimportant services to reduce the possibility of data retransmission.

[0257] It is understood that the first threshold can be determined by any one or more of the above methods, such as a device determining the first threshold and then sending the first threshold to a peer device. Alternatively, a device receives the first threshold sent by another device, and determines a new first threshold based on the signal quality, service type, etc. between the devices, and jointly determines an appropriate threshold based on the received first threshold and the new first threshold. Optionally, the device can also reselect an appropriate threshold in synchronization with other devices. The embodiments of the present application do not limit the method for determining the first threshold.

[0258] S204: The receiving end sends first information to the sending end.

[0259] In some embodiments, after determining the first information in S203, the receiving end may send the first information to the sending end, so that the sending end can determine which data of the at least one data sent in S201 to retransmit based on the first information.

[0260] For example, assuming that the transmitting end receives CB1 and CB2, where CB1 fails the CRC check, the receiving end can determine whether to retransmit CB1 based on the confidence level of CB1. If the receiving end determines to retransmit CB1, the receiving end can send first information to the transmitting end. The first information may include feedback information indicating CB1 to instruct the transmitting end to retransmit CB1. The transmitting end may determine to retransmit CB1 based on the first information. For another example, the receiving end may also determine the confidence level of CB2. If CB2 succeeds in the CRC check, or although CB2 fails the CRC check but the confidence level of CB2 is high. The first information may also include feedback information indicating CB2 to instruct the transmitting end not to retransmit CB1, or there is no feedback information indicating CB2 in the first information.

[0261] Similarly, the CB in the above example can also be replaced by CBG or TB, which is not limited in this embodiment of the present application.

[0262] For example, when the first information includes response messages for different CBs, such as FACK, FNACK, etc., the transmitting end may determine that the first data corresponding to the FACK does not need to be retransmitted, and the first data corresponding to the FNACK needs to be retransmitted.

[0263] In some embodiments, the receiving end may also determine whether to retransmit the first data corresponding to the FNACK based on actual conditions. For example, if the air interface traffic between the sending end and the receiving end is very congested, the sending end may choose to retransmit part of the first data corresponding to the FNACK, thereby reducing resource consumption caused by retransmitting data.

[0264] In some embodiments, if some first data does not need to be retransmitted, the feedback message for such first data may be omitted from the first information, or the feedback may be a FACK. For example, assuming that the first information is fed back as a CB, then some CBs with correct CRC checks may not be retransmitted, that is, the feedback information for such CBs may be a FACK. In this case, the feedback information for such CBs may be directly omitted from the first information. Alternatively, the feedback information for the CB may be a default value. The default value may be considered a pre-set default value. When the feedback information is the default value, it means that the corresponding first data does not need to be retransmitted.

[0265] In this embodiment of the present application, a receiving end can obtain first information based on the confidence level of the first data and send the first information to the transmitting end, instructing the first data whose confidence level does not meet the corresponding conditions to be retransmitted. Therefore, the first data whose confidence level meets the corresponding conditions does not need to be retransmitted, thereby reducing resource consumption and latency caused by retransmission.

[0266] Considering that the data sent by the transmitter when XR scenarios are involved may be suitable for recovery based on feature streams. For example, when the data is video data, there is a video codec solution based on artificial intelligence (AI). The data transmitted by this type of solution can be recovered using a feature stream with fault-tolerant characteristics. For example, even if there is an error in the received bit, it can still be repaired by the configured generator. It is guaranteed that a good quality video is restored at the receiving end. Partial data with the same fault-tolerant characteristics can be considered to belong to the same feature stream. In other words, the receiving end can recover the data in the feature stream based on a feature stream. Referring to Figure 10, compared with the solution based only on CRC check, the picture with data error will not be displayed. In the AI-based video codec solution, although the received data is incorrect, the original picture can still be restored.

[0267] In some examples, for the data of layer 2, a header can be added to the data in the manner of Figure 11, and the data can be passed layer by layer until it is passed to the physical layer for transmission. For example, the data in the Internet Protocol (IP) layer is an IP packet. After the IP packet is passed to the Service Data Adaptation Protocol (SDAP) layer, it can be used as an SDAP service data unit (SDU). In the SDAP layer, the header corresponding to the layer can be added to the SDAP SDU to obtain the protocol data unit (PDU) of the SDAP layer. The SDAP PDU is then passed to the next layer, that is, to the Packet Data Convergence Protocol (PDCP) layer. Similar to the SDAP layer, the SDAP PDU in the PDCP layer is called a PDCP SDU. And the header corresponding to the layer can be added to the PDCP SDU to obtain the PDCP PDU, and then passed to the next layer. Similar to the SDAP and PDCP layers, the PDCP PDU in the radio link control (RLC) layer is called the RLC SDU. The corresponding header for that layer is added to the RLC SDU to obtain the RLC PDU, which is then passed to the next layer. Similar to the SDAP, PDCP, and RLC layers, the RLC PDU in the MAC layer is called the MAC SDU. The corresponding header for that layer is added to the MAC SDU to obtain the MAC PDU.

[0268] Of course, for different layers, the data length of the PDU of each layer can be different. For example, the MAC layer can form a MAC PDU with the data corresponding to one or more PLC PDUs of the RLC layer according to the PDU size predetermined by the layer. The MAC PDU can be carried by the TB, and the TB can be transmitted to the physical layer. In some examples, the size of the MAC PDU can be the same as the size of the TB, that is, one MAC PDU is equal to 1 TB. Figure 11 is only an exemplary representation of adding a header during the transmission of data between different layers. PDUs of different lengths can be defined in different layers. Therefore, the PDU of each layer in each layer can be composed of one or more SDUs. In addition, when the PDU in each layer is passed to the next layer, it becomes the SDU of the next layer.

[0269] Figures 12 and 13 illustrate different MAC PDU structures. Figure 12 shows a MAC PDU structure in an NR system. It can be seen that a MAC PDU can be composed of several MAC sub-PDUs. Each MAC sub-PDU can include a sub-header and a data portion. The data portion can be a MAC CE of varying lengths or a MAC SDU. In some examples, the sub-header can be a reserved bit (R) field, a length (L) field, an F field, or a logical channel identification (LCID) field. The L field can indicate the length of the corresponding MAC SDU or MAC CE. The F field is used to indicate the size of the L field. The LCID field can indicate the logical channel instance corresponding to the MAC SDU or MAC CE. Figure 13 shows a MAC PDU structure in an LTE system. It can be seen that the MAC PDU has a MAC header at the front, which contains one or more sub-headers. Each sub-header corresponds to a MAC CE or MAC SDU in the data portion. Optionally, the MAC PDU can be padded with padding bits to ensure that the MAC PDU meets the corresponding length requirements.

[0270] As can be seen in Figure 12, the headers can precede their respective MAC CEs or MAC SDUs. In Figure 13, however, all sub-header information is aggregated to form a single MAC header, which is placed at the beginning of the data portion. It is understandable that sub-headers may differ slightly across different communication systems.

[0271] In some examples, the MAC layer transmits the TB to the physical layer, where it can add a CRC checksum to the TB, as shown in Figure 14 (TB-CRC). The physical layer can also divide the TB with the CRC checksum into several CBs according to a predefined method and add a CRC checksum to each CB (CB-CRC). This allows the receiver to perform a CRC check on each CB and obtain the correct CB.

[0272] However, currently, information related to feature flows is unknown to the MAC layer, physical layer, and other lower layers. This makes it impossible for the physical layer to identify which data belongs to a feature flow, nor to use the feature flow for data recovery, and therefore impossible to optimize data retransmission.

[0273] In some embodiments, the transmitting end may carry the information of the feature stream in the at least one data sent by adding a packet header when sending at least one data. So that the receiving end can know which first data belongs to which feature stream. The information of the feature stream can also be called a fault-tolerant feature. By adding a fault-tolerant feature to at least one data sent, the subsequent receiving end can send the corresponding first information for a feature stream. A feature stream may correspond to one or more CBs, or a feature stream may correspond to one or more CBGs, or a feature stream may correspond to one or more TBs. The receiving end can determine whether to retransmit part of the first data in the feature stream for different feature streams.

[0274] In some embodiments, at least one data item sent by the transmitting end may correspond to at least one packet header. The at least one packet header is used to indicate that the at least one data item sent has a fault-tolerant feature. It is understood that the packet header may be a packet header added to any data layer in the above example.

[0275] For example, the fault-tolerance feature is used to represent the information in the aforementioned feature stream. In other words, the fault-tolerance feature can be represented by the feature stream. This is because some data errors can be tolerated within the data corresponding to a feature stream, and the data corresponding to the first feature stream can be recovered using the generator of related technologies. Therefore, it can be considered that the data within a feature stream has a certain degree of fault tolerance.

[0276] In some examples, the relationship between the packet header and the data can be as shown in Figure 15, where a packet header is added for each data. Each packet header includes a fault-tolerant feature, and the fault-tolerant feature can indicate the feature stream to which the data corresponding to the packet header belongs. Each data portion in Figure 15 can represent one data in at least one data. It can be seen that in Figure 15, a packet header corresponding to the data is added for each data. For example, packet header 1 corresponds to data portion 1, packet header 2 corresponds to data portion 2, packet header 3 corresponds to data portion 3, and so on. The fault-tolerant feature in each packet header can be considered as the fault-tolerant feature of the data portion corresponding to the packet header. That is, fault-tolerant feature 1 corresponds to data portion 1, fault-tolerant feature 2 corresponds to data portion 2, fault-tolerant feature 3 corresponds to data portion 3, and so on.

[0277] For example, after receiving the data shown in Figure 15, the receiving end can parse the error-tolerance feature in the packet header and determine whether the data corresponding to the packet header is error-tolerant. For example, if the packet header indicates that the corresponding data corresponds to at least one characteristic stream, then the data can be considered error-tolerant. For example, if the receiving end receives data portion 1 and corresponding packet header 1 as shown in Figure 15, the receiving end can parse the error-tolerance feature in packet header 1, which can indicate the corresponding relationship between data portion 1 and the characteristic stream.

[0278] As shown in FIG16 , a packet header can be added for multiple data. That is, packet header 4 in FIG16 corresponds to data portion 1, data portion 2, data portion 3, and so on. Fault-tolerance feature 4 included in packet header 4 in FIG16 can be considered as the fault-tolerance feature for data portion 1, data portion 2, data portion 3, and so on.

[0279] In some examples, referring to the data transmission process shown in Figure 11, to ensure that the physical layer can identify which feature stream each data belongs to, the error-tolerance feature can be added to the packet header when adding the packet header at each data layer. To address possible data segmentation in different data layers, the error-tolerance feature in the packet header can be parsed and repackaged to ensure that the error-tolerance feature is not lost.

[0280] In some examples, the packet header may include a first field and a second field. The first field and the second field together indicate the fault-tolerance feature. For example, the first field may be a number (NUM) field, used to indicate the number of feature streams corresponding to the data corresponding to the packet header. The second field may be a position (POS) field, used to indicate the number of bits corresponding to each feature stream in the NUM field. In some examples, the number of bits for the last feature stream may be omitted. This is because the number of bits of a piece of data is often constant during a communication process. Therefore, the number of bits for the last feature stream may be obtained by using the number of bits of other feature streams and the inherent number of bits of the data.

[0281] With reference to FIG15 , for example, the NUM field in header 1 can indicate the number of feature streams corresponding to data portion 1, and the POS field in header 1 can indicate the number of bits of the feature stream corresponding to data portion 1. Similarly, headers 2 and 3 are similar to header 1 and will not be described in detail in this embodiment of the present application. With reference to FIG16 , for example, the NUM field in header 4 can indicate the number of feature streams corresponding to data portion 1, data portion 2, and data portion 3, and the POS field in header 4 can indicate the number of bits of the feature stream to which the NUM field in header 4 relates.

[0282] With reference to Figures 17 to 20, embodiments of the present application provide schematic diagrams of various MAC layer to physical (PHY) layer data transfers. MAC layer data can be considered as MAC PDUs, and PHY layer data can be considered as CBs or CBGs, etc., which divide TBs. In Figures 17 and 18, each MAC layer data has an independent header, and each header includes fault tolerance characteristics indicating the corresponding data. For example, the first header on the left of the MAC layer in Figures 17 and 18 can indicate that its corresponding MAC PDU corresponds to feature stream 1, the second header on the left can indicate that its corresponding MAC PDU corresponds to feature stream 1 and feature stream 2, the third header on the left can indicate that its corresponding MAC PDU corresponds to feature stream 2 and feature stream 3, and so on. It can be seen that each feature stream pair may correspond to one or more MAC PDUs. The header of each MAC PDU can indicate which feature streams the MAC PDU corresponds to. In Figures 19 and 20, multiple MAC layer data have the same header, which includes fault tolerance characteristics indicating the corresponding multiple data. For example, the packet header of a unified MAC PDU can indicate which feature flows the corresponding multiple MAC PDUs correspond to. For Figures 17 and 19, each CB or CBG in the PHY layer can have an independent packet header, and each packet header includes an indication of the fault-tolerance characteristics of its corresponding CB or CBG, that is, an indication of which feature flow the corresponding CB or CBG corresponds to. For example, the first packet header on the left in the PHY layer in Figures 17 and 18 can indicate which feature flows the corresponding CB or CBG corresponds to, the second packet header on the left can indicate which feature flows the corresponding CB or CBG corresponds to, and so on. For Figures 18 and 20, multiple CBs or CBGs in the PHY layer can have a unified packet header, and the packet header includes an indication of the fault-tolerance characteristics of the corresponding multiple CBs or CBGs, that is, an indication of which feature flow the corresponding multiple CBs or CBGs correspond to. On the same day, the CB or CBG of the PHY layer can also be replaced by a TB, which is not limited in the embodiments of the present application.

[0283] It can be seen that the methods of adding packet headers in different data layers can be independent of each other, and the method of adding packet headers in each data layer does not affect the methods of adding packet headers in other data layers.

[0284] In some specific examples, this application provides multiple data verification processes. For example, the processes shown in Figures 21 and 22 differ in that the receiving end sends the first information using different feedback units. As shown in Figure 21, the transmitting end sends at least one data item, for example, using multiple processes in parallel. For example, process 1 sends CB0, CB1, or CBG0, CBG1, and process 2 sends CB2, CB3, or CBG2, CBG3. When sending data, the transmitting end can refer to the schemes described in Figures 15 to 20 above and add a packet header. This header can include fault tolerance features. This fault tolerance feature can indicate the feature stream corresponding to each CB or CBG. After receiving the data sent by the transmitting end, the receiving end can first perform a CRC check and, based on the correctness of the CRC check, provide an ACK or NACK. For example, a CB or CBG that fails the CRC check can provide a NACK, while a CB or CBG that succeeds the CRC check can provide an ACK. This process can be implemented with reference to related technologies and will not be described in detail in this application. Although the transmitting end receives an ACK and / or NACK sent by the receiving end, it does not use this feedback to determine which data to retransmit. The receiving end can determine the confidence levels of multiple received data. For example, for process 1, the receiving end can determine the confidence levels of CB0 and CB1, or the receiving end can determine the confidence levels of CBG0 and CBG1. For process 2, the receiving end can determine the confidence levels of CB2 and CB3, or the receiving end can determine the confidence levels of CBG2 and CBG3. Assume that the receiving end determines that CB0, CB1, and CB2 belong to the same feature stream, such as feature stream 1, based on the packet header of the received data. The first information sent by the receiving end can be that corresponding to feature stream 1. Taking the first data as CB as an example, assuming that the receiving end successfully performs CRC check on CB1 and CB3, and fails CRC check on CB0 and CB2. The confidence level of CB1 can be 0 or omitted directly. Because the sending end can know that the data has been successfully received by the receiving end based on the ACK feedback from the receiving end, there is no need for retransmission. The receiving end can adopt the scheme described in Figures 8 to 9 above to determine the confidence of CB0 and the confidence of CB1. The specific implementation method refers to the description of the corresponding embodiment above, and the embodiments of the present application will not be repeated here. The receiving end can compare the confidence of CB0 with the first threshold to determine whether to indicate CB0 to be retransmitted; similarly, the receiving end can compare the confidence of CB2 with the first threshold to determine whether to indicate CB2 to be retransmitted. Assuming that the receiving end determines that CB0 needs to be retransmitted, it can be determined that the first information corresponding to CB0 is FNACK. Assuming that the receiving end determines that CB2 does not need to be retransmitted, it can be determined that the first information corresponding to CB0 is FACK. The receiving end can send the first information corresponding to feature stream 1, that is, the first information includes the first information corresponding to CB0 and the first information corresponding to CB2.Optionally, since the confidence level corresponding to CB1 is 0 or omitted, the first information corresponding to CB1 may be FACK or omitted. The transmitting end may determine CB0 in the retransmission feature stream 1 based on the first information sent by the receiving end. Of course, CB in this example may be equivalently replaced with CBG.

[0285] Figure 22 is similar to Figure 21, except that each process sends a single TB of data. In some cases, each concurrent process can be configured to send data in TBs. Therefore, in Figure 21, each process can be considered to be dividing a single TB into multiple CBs or CBGs for transmission, while in Figure 22, each process directly sends a single TB.

[0286] FIG23 is a schematic diagram of another data verification method provided by an embodiment of the present application. As shown in FIG23, the method can be applied to the communication scenarios shown in FIG1, FIG4 to FIG7. The method may include the following steps:

[0287] S301: A transmitting end sends at least one data to a receiving end.

[0288] S302: The receiving end determines the confidence level corresponding to the first data based on the first data.

[0289] It can be understood that S301 is similar to S101, and S302 is similar to S102. The specific implementation process of S301 and S302 can refer to the description of the corresponding embodiment of the corresponding steps in Figure 8, and the embodiments of this application will not be repeated here.

[0290] S303: The receiving end sends the confidence level to the sending end.

[0291] In some embodiments, the receiving end may directly feed back the confidence level corresponding to the first data determined in S302 to the sending end.

[0292] In some embodiments, direct confidence feedback may consume more bits when the confidence data is large, resulting in significant resource consumption. Therefore, multiple interval values ​​can be set for the confidence level, with each interval value corresponding to a certain range of confidence values. For example, Table 1 shows a possible correspondence between interval values ​​and confidence levels.

[0293] Table 1

[0294] It can be seen that when the confidence level is within the corresponding confidence level interval, the receiving end can reduce resource consumption by feeding back the interval value corresponding to the confidence level.

[0295] If the confidence level of the first data is determined based on the LLR of the CB that failed the CRC, the interval value corresponding to the confidence level can be determined using the method in Table 1. If the confidence level of the first data is determined based on the number of first bits of the CB that failed the CRC, the interval value corresponding to the confidence level can be determined using the method in Table 2.

[0296] Table 2

[0297] In the case where the confidence level of the first data is determined based on the ratio of the number of first bits corresponding to the CBs where CRC fails to the total code length of the first data, the interval value corresponding to the confidence level can be determined using the method in Table 3.

[0298] Table 3

[0299] It is clear that Tables 1, 2, and 3 above only illustrate the case where the interval value is 2 bits. In other examples, the interval value can also be represented by any number of bits, such as 1 bit, 3 bits, etc. The embodiments of the present application do not limit the number of bits corresponding to the interval value and can be adaptively adjusted according to actual conditions.

[0300] In some embodiments, the receiving end may send a corresponding interval value to the transmitting end. The transmitting end may determine the confidence interval corresponding to the first data based on the interval value corresponding to the first data. The transmitting end may determine whether to retransmit the first data based on the confidence interval corresponding to the first data. In other embodiments, if the receiving end directly sends the confidence level of the first data to the transmitting end, the transmitting end may directly determine whether to retransmit the first data based on the confidence level corresponding to the first data.

[0301] In some examples, the transmitting end may determine whether to retransmit the first data based on the confidence level corresponding to the first data and a first threshold. This implementation process can be described with reference to the aforementioned embodiment in which the receiving end determines whether to retransmit the first data based on the confidence level corresponding to the first data and a first threshold, and the present embodiment will not be further described here. The method for determining the first threshold can also be described with reference to the method for determining the first threshold in the aforementioned embodiment, and the present embodiment will not be further described here.

[0302] In some examples, considering that the decision on whether to retransmit the first data is made by the transmitting end, if the first threshold is determined by the receiving end, the receiving end may also send the first threshold to the transmitting end. For example, the receiving end sends fourth information, and the transmitting end receives the fourth information. The fourth information includes the first threshold.

[0303] S304: The sending end sends first information to the receiving end.

[0304] In some embodiments, the transmitting end may determine whether to retransmit the first data based on the confidence level of the first data received in S303. The transmitting end may obtain first information based on whether multiple first data are retransmitted. The first information may indicate whether to retransmit at least one data item sent in S301. It is understood that the purpose of the transmitting end sending the first information is to inform the receiving end which data item the transmitting end retransmits.

[0305] The implementation process of S304 can refer to S204, except that the device sending the first information is changed from a receiving end to a sending end.

[0306] In some examples, if the confidence level of the first data is less than a first threshold, the first information may indicate to retransmit the first data. If the confidence level of the first data is greater than or equal to the first threshold, the first information may indicate not to retransmit the first data.

[0307] In this embodiment of the present application, a receiving end may send a confidence level to a transmitting end, so that the transmitting end can determine first information based on the confidence level and a first threshold. This first information may indicate that first data whose confidence level does not meet a corresponding condition should be retransmitted. First data whose confidence level meets the corresponding condition does not need to be retransmitted, thereby reducing resource consumption and latency associated with retransmissions.

[0308] In some more specific examples, the present application provides a variety of data verification processes. For example, the difference between the processes shown in Figures 24 and 25 is that the confidence sent by the receiving end is implemented in different feedback units. Figure 24 is similar to Figure 21, except that the receiving end sends the confidence corresponding to feature stream 1. The sending end can determine the first information corresponding to the feature stream based on the confidence of feature stream 1. The sending end can also send the first information corresponding to feature stream 1 to the receiving end to inform the receiving end which data in feature stream 1 the sending end wants to retransmit. Figure 25 is similar to Figure 24, except that the data sent by a process is one TB.

[0309] In a data verification method provided in an embodiment of the present application, the method may further include: the transmitting end sending second information to the receiving end, or the receiving end sending second information to the transmitting end, wherein the second information is used to indicate whether to retransmit the first data based on the confidence level.

[0310] In some embodiments, the schemes described in Figures 8 to 25 above may further include the transmitting end or the receiving end sending second information to indicate whether to retransmit the first data based on the confidence level in the communication between the transmitting end and the receiving end. The method of indicating whether to retransmit the first data based on the confidence level may also be referred to as a fault-tolerant transmission service, a fault-tolerant service, etc., and this application does not limit this term.

[0311] It will be understood that if the second information indicates that whether to retransmit the first data is indicated based on the confidence level, this means that the transmitting end no longer determines whether to retransmit the first data based on the ACK and / or NACK obtained by the receiving end based on the CRC check. The transmitting end will determine whether to retransmit the first data based on the FACK and / or FNACK fed back by the receiving end, or based on the confidence level or confidence interval fed back by the receiving end.

[0312] In some examples, if the device sending the second information is a terminal, the second information can be carried by uplink control information (UCI) to achieve the second information being sent to the network device. For another example, the second information can be carried by sidelink control information (SCI) to achieve the second information being sent to other terminals.

[0313] In some examples, if the device that sends the second information is a network device, the second information can be carried by DCI to achieve sending the second information to the terminal.

[0314] In some examples, the second information can be represented by 1 bit. If the bit is 0, it indicates that the method of indicating whether to retransmit the first data based on the confidence level is not adopted; if the bit is 1, it indicates that the method of indicating whether to retransmit the first data based on the confidence level is adopted. Alternatively, if the bit is 0, it indicates that the method of indicating whether to retransmit the first data based on the confidence level is adopted; if the bit is 1, it indicates that the method of indicating whether to retransmit the first data based on the confidence level is not adopted. The embodiment of the present application does not limit the correspondence between the bit value and whether the fault-tolerant transmission service is adopted. Of course, the second information can also be represented by more bits, and the embodiment of the present application does not limit this.

[0315] In the embodiment of the present application, the second information can be used to indicate whether the opposite device has adopted the fault-tolerant transmission service, so as to reduce the resource consumption caused by retransmission and the delay caused by retransmission when the service is enabled.

[0316] In some embodiments, for the solutions mentioned in the above embodiments of this application, when data retransmission is determined, regardless of how the first threshold changes, data with a lower confidence level is preferentially selected as the object of retransmission. Of course, a confidence level of 0 is a special case, and the first data corresponding to this confidence level is considered to be correctly received and is not considered for retransmission.

[0317] In some embodiments, the present application provides a more specific data verification process, as shown in Figure 26. In S401, the receiving end first determines whether to enable the fault-tolerant transmission service. For example, the receiving end is pre-configured with information indicating whether to enable the fault-tolerant transmission service, or the receiving end receives indication information sent by other devices to indicate whether to enable the fault-tolerant transmission service. In S402, the receiving end performs a CRC check on the received data. If the CRC check is correct, S404 can be directly executed, that is, the correct data is passed to the upper layer. If there is data that fails the CRC check, the confidence level of each data that fails the CRC check can be determined based on the LLR in S403. The receiving end can determine whether to retransmit the corresponding data in S405 based on the confidence level determined in S403 and the first threshold, and obtain the first information. The receiving end can send the first information to the sending end to indicate which data needs to be retransmitted.

[0318] As shown in Figure 27, the scheme is similar to that shown in Figure 26, except that whether the data is retransmitted is determined by the sending end. In S501, the receiving end first determines whether to enable the fault-tolerant transmission service. In S502, the receiving end performs a CRC check on the received data. If the CRC check is correct, S504 can be directly executed to pass the correctly received data to the upper layer. For data that fails the CRC check, the confidence level of each data that fails the CRC check can be determined based on the LLR in S503. In S505, the receiving end can send the confidence level of at least one first data to the sending end. The first data is any one of the at least one data received by the receiving end. The sending end can determine whether to retransmit the corresponding data based on the confidence level of the at least one first data and the first threshold. The sending end can retransmit the corresponding data. Or if the sending end decides not to retransmit, the receiving end can pass the received data to the upper layer.

[0319] In some examples, the transmitting end may send first information indicating which data needs to be retransmitted. In other examples, if the transmitting end does not send the first information and the receiving end does not receive any retransmitted data, it can be considered that the transmitting end has determined not to retransmit. For example, if the receiving end does not receive the first information or any retransmitted data within a preset time, the receiving end may determine that the transmitting end has not retransmitted data and may then execute S504 to transfer the received data to the upper layer.

[0320] In some possible implementations, the receiving end may send either a confidence level or first information to the transmitting end. The transmitting end may then receive at least one of the confidence level and the first information. For example, the transmitting end may receive the confidence level, the first information, or both. It will be appreciated that when the transmitting end receives both the confidence level and the first information, the transmitting end may determine which data requires retransmission based on the confidence level and, in combination with the data indicated as requiring retransmission in the first information, ultimately determine the data requiring retransmission.

[0321] It should be noted that the above-mentioned multiple embodiments can be combined and the combined solutions can be implemented. Optionally, some operations in the process of each method embodiment are optionally combined, and / or the order of some operations is optionally changed. In addition, the execution order between the steps of each process is only exemplary and does not constitute a limitation on the execution order between the steps. There can also be other execution orders between the steps. It is not intended to indicate that the execution order is the only order in which these operations can be performed. Ordinary technicians in this field will think of many ways to reorder the operations of this article. In addition, it should be pointed out that the process details involved in a certain embodiment of this article are also applicable to other embodiments in a similar manner, or different embodiments can be used in combination.

[0322] It is understood that in order to implement the functions in the above embodiments, the base station and the terminal include hardware structures and / or software modules that perform the corresponding functions. Those skilled in the art should readily appreciate that, in combination with the units and method steps of the various examples described in the embodiments disclosed in the present application, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

[0323] Figures 28 and 29 are schematic diagrams of possible data verification devices provided in embodiments of the present application. These data verification devices can be used to implement the functions of the terminal or network device in the above-mentioned method embodiments, thereby also achieving the beneficial effects of the above-mentioned method embodiments. In the embodiments of the present application, the data verification device can be a terminal or a network device, or a module applied to a terminal or network device. For example, a chip.

[0324] As shown in Figure 28, the data verification device 2800 includes a processing unit 2810 and a transceiver unit 2820. The data verification device 2800 is used to implement the functions of the transmitter or receiver in the method embodiments shown in Figures 8, 9, and 21 to 27.

[0325] When data verification device 2800 is used to implement the functions of the receiving end in the method embodiment shown in FIG8 , transceiver unit 2820 is used to receive at least one data item. Processing unit 2810 is used to determine the confidence level corresponding to the first data item based on the first data item. Processing unit 2810 is also used to perform all operations performed by the data verification device in the embodiment shown in FIG8 , except for the transceiver operations, and / or to support other processes of the technology described herein.

[0326] When data verification device 2800 is used to implement the functions of the transmitting end in the method embodiment shown in FIG8 , transceiver unit 2820 is used to transmit at least one data item. Processing unit 2810 is further used to perform all operations performed by the data verification device in the embodiment shown in FIG8 , except for the transceiver operations, and / or to support other processes of the technology described herein.

[0327] For a more detailed description of the processing unit 2810 and the transceiver unit 2820, please refer to the relevant descriptions of the method embodiments shown in Figures 8, 9, and 21 to 27. The processing unit 2810 and the transceiver unit 2820 may also perform other steps, and the specific implementation can refer to the method embodiments, which will not be repeated here.

[0328] Optionally, the transceiver unit 2820 may be a transceiver, which may include an antenna and a radio frequency circuit, etc.

[0329] The processing unit 2810 may be a processor (or a processing circuit), such as a baseband processor, which may include one or more CPUs.

[0330] As shown in Figure 29, data verification device 2900 includes a processor 2910 and an interface circuit 2920. Processor 2910 and interface circuit 2920 are coupled to each other. It is understood that interface circuit 2920 can be a transceiver or an input / output interface. Optionally, data verification device 2900 may further include a memory 2930 for storing instructions executed by processor 2910, or storing input data required by processor 2910 to execute instructions, or storing data generated after processor 2910 executes instructions.

[0331] When the data verification device 2900 is used to implement the methods shown in Figures 8, 9, 21 to 27, etc., the processor 2910 is used to implement the functions of the above-mentioned processing unit 2810, and the interface circuit 2920 is used to implement the functions of the above-mentioned transceiver unit 2820.

[0332] When the data verification device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above-mentioned method embodiment. When the terminal chip receives information from the network device, it can be understood that the information is first received by other modules in the terminal (such as a radio frequency module or antenna) and then sent to the terminal chip by these modules. When the terminal chip sends information to the network device, it can be understood that the information is first sent to other modules in the terminal (such as a radio frequency module or antenna) and then sent to the network device by these modules.

[0333] When the data verification device is a chip used in a network device, the network device chip implements the functions of the network device in the above method embodiment. When the network device chip receives information from the terminal, it can be understood that the information is first received by other modules in the network device (such as a radio frequency module or antenna) and then sent to the network device chip by these modules. When the network device chip sends information to the terminal, it can be understood that the information is sent to other modules in the network device (such as a radio frequency module or antenna) and then sent to the terminal by these modules.

[0334] The communication device shown in FIG. 28 or FIG. 29 is merely an example, and in actual applications the communication device may have more or fewer components than those shown in FIG. 28 or FIG. 29 , may combine two or more components, or may have a different component configuration.

[0335] In the embodiments of the present application, when entity A sends information to entity B, A may send the information directly to B or indirectly to B through another entity. Similarly, when entity B receives information from entity A, entity B may directly receive the information sent by entity A or indirectly receive the information sent by entity A through another entity. Entities A and B herein may be RAN nodes or terminals, or modules within a RAN node or terminal. The sending and receiving of information may be information exchange between a RAN node and a terminal, for example, information exchange between a network device and a terminal; the sending and receiving of information may also be information exchange between two RAN nodes, for example, information exchange between a CU and a DU; the sending and receiving of information may also be information exchange between different modules within a device, for example, information exchange between a terminal chip and other modules of the terminal, or information exchange between a network device chip and other modules within the network device.

[0336] In the embodiments of the present application, a network device sends downlink signals or downlink information to a terminal device, and the downlink information is carried on a downlink channel. The terminal device sends uplink signals or uplink information to the network device, and the uplink information is carried on an uplink channel. To communicate with the network device, the terminal device needs to establish a wireless connection with a cell controlled by the network device. The cell with which the terminal device has established a wireless connection is called the serving cell of the terminal device.

[0337] It can be understood that in the embodiment of the present application, PDSCH and PUSCH are only used as examples of downlink data channels and uplink data channels. In different systems and different scenarios, data channels and control channels may have different names, and the embodiment of the present application does not limit this.

[0338] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0339] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal. The processor and storage medium can also exist in a network device or a terminal as discrete components.

[0340] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0341] In each embodiment of the present application, unless otherwise specified or provided by logic, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0342] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A data verification method, characterized in that: include: receiving at least one data, wherein the at least one data comprises first data; A confidence level corresponding to the first data is determined according to the first data, where the confidence level is used to indicate a reception status of the first data.

2. The method according to claim 1, characterized in that The confidence level is determined according to a log likelihood ratio (LLR) corresponding to the first data.

3. The method according to claim 2, characterized in that The confidence level is determined according to a log likelihood ratio (LLR) corresponding to the first data, including at least one of the following methods: The confidence level is determined according to the LLR corresponding to the code block CB in which the cyclic redundancy check CRC fails in the first data; The confidence is determined according to the number of first bits in the first data, wherein the first bits are bits in the CB where CRC fails in the first data, and the number of the first bits is determined according to the LLR corresponding to the CB where CRC fails in the first data; The confidence level is determined based on the ratio of the number of first bits corresponding to CBs where CRC fails in the first data to the total code length of the first data.

4. The method according to claim 3, characterized in that The number of the first bits is determined according to the LLR corresponding to the CB where the CRC fails, including: The number of the first bits is determined according to the LLR corresponding to the CB where the CRC fails and the LLR reference value.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: First information is sent according to the confidence level and a first threshold, where the first information is used to indicate whether to retransmit the at least one data.

6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: sending the confidence level; First information is received, where the first information is used to indicate whether to retransmit the at least one data, and the first information is determined according to the confidence level and a first threshold.

7. The method according to claim 5 or 6, characterized in that: The first information is used to indicate whether to retransmit the at least one data, including: The confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: sending second information, where the second information is used to indicate whether to retransmit the first data according to the confidence level; or, The second information is received.

9. The method according to any one of claims 1 to 8, characterized in that: The at least one data corresponds to at least one packet header, and the at least one packet header is used to indicate that the at least one data has an error-tolerant feature.

10. A data verification method, characterized in that: include: Sending at least one data, wherein the at least one data includes first data; At least one of receiving confidence and first information, wherein the confidence is used to indicate a reception status of the first data, and the first information is used to indicate whether to retransmit the at least one data.

11. The method according to claim 10, characterized in that The confidence level is determined according to a log likelihood ratio (LLR) corresponding to the first data.

12. The method according to claim 11, characterized in that The confidence level is determined according to a log likelihood ratio (LLR) corresponding to the first data, including at least one of the following methods: The confidence is determined according to the LLR corresponding to the code block CB in which the cyclic redundancy check CRC fails in the first data; The confidence is determined according to the number of first bits in the first data, wherein the first bits are bits in the CB where CRC fails in the first data, and the number of the first bits is determined according to the LLR corresponding to the CB where CRC fails in the first data; The confidence level is calculated based on the ratio of the number of first bits corresponding to CBs that fail CRC in the first data to the first bits of the first data. The ratio of the total code length is determined.

13. The method according to claim 12, characterized in that The number of the first bits is determined according to the LLR corresponding to the CB where the CRC fails, including: The number of the first bits is determined according to the LLR corresponding to the CB where the CRC fails and the LLR reference value.

14. The method according to any one of claims 10 to 13, characterized in that: The receiving at least one of the confidence level and the first information comprises: The first information is received, wherein the first information is determined based on the confidence level and a first threshold.

15. The method according to any one of claims 10 to 13, characterized in that: The receiving at least one of the confidence level and the first information comprises: receiving the confidence level; determining the first information according to the confidence level and a first threshold; The first information is sent.

16. The method according to claim 14 or 15, characterized in that The first information is used to indicate whether to retransmit the at least one data, including: The confidence level is less than a first threshold, and the first information is used to indicate retransmission of the first data.

17. The method according to any one of claims 10 to 16, characterized in that: The method further comprises: sending second information, where the second information is used to indicate whether to retransmit the first data according to the confidence level; or, The second information is received.

18. The method according to any one of claims 10 to 17, characterized in that: The at least one data corresponds to at least one packet header, and the at least one packet header is used to indicate that the at least one data has an error-tolerant feature.

19. A data verification device, characterized in that: include: Processing module and communication module; The communication module is used to receive and / or send signals, and the processing module is configured to enable the method according to any one of claims 1 to 9 to be executed.

20. A data verification device, characterized in that: include: Processing module and communication module; The communication module is used to receive and / or send signals, and the processing module is configured to enable the method according to any one of claims 10 to 18 to be executed.

21. A data verification device, characterized in that: include: At least one processor and a communication interface, the communication interface being used to receive and / or send signals, the processor being configured to enable the method according to any one of claims 1 to 9 to be executed.

22. A data verification device, characterized in that: include: At least one processor and a communication interface, the communication interface being used to receive and / or send signals, the processor being configured to enable the method of any one of claims 10 to 18 to be executed.

23. A communication system, characterized in that: The system comprises: a first device for executing the method according to any one of claims 1 to 9 , and a second device for executing the method according to any one of claims 10 to 18 .

24. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions or programs, and when the instructions or programs are executed on the communication device, the communication device executes the method according to any one of claims 1 to 9.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions or programs, and when the instructions or programs are executed on the communication device, the communication device executes the method according to any one of claims 10 to 18.

26. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and when the computer program or instructions are run on a computer, the computer is caused to perform the method according to any one of claims 1 to 9.

27. A computer program product, characterized in that The computer program product comprises a computer program or instructions, which, when executed on a computer, causes the computer to perform the method according to any one of claims 10 to 18.

Images