Data verification method and device

Abstract

The invention discloses a data verification method and device, and the method comprises the steps: receiving at least one piece of data, and the at least one piece of data comprises first data; and determining a confidence coefficient corresponding to the first data according to the first data, wherein the confidence coefficient is used for indicating a receiving condition of the first data. For example, the method is applied to a first device. According to the embodiment of the invention, the first data is verified by determining the confidence coefficient of the first data. Therefore, the first data does not need to be retransmitted under the condition that the confidence meets the corresponding condition, so that the resource consumption caused by retransmission is reduced, and the time delay caused by retransmission is reduced.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to a data verification method and apparatus. Background Art

[0002] In the extended reality (XR) service of the new radio access technology (NR) in the 5th generation (5G) communication system, basic interaction between humans and the virtual world can be realized. For data with a 4K picture quality, the average access rate is approximately required to be about 120 megabits per second (Mbps), and the interaction delay is about 20 milliseconds (ms). However, for future services that may involve XR pro, holography, etc. and require immersive experiences, lower latency and higher transmission rates will be needed. And how to meet higher latency requirements and transmission requirements is a problem that needs to be solved currently. Summary of the Invention

[0003] Embodiments of this application provide a data verification method and apparatus, which verify the first data by determining the confidence level of the first data. So that when the confidence level meets the corresponding conditions, there is no need to retransmit the first data, thereby reducing the resource consumption caused by retransmission and reducing the latency caused by retransmission.

[0004] To achieve the above object, this application adopts the following technical solutions:

[0005] In a first aspect, a data verification method is provided, including: receiving at least one data, where the at least one data includes the first data; determining, according to the first data, a confidence level corresponding to the first data, where the confidence level is used to indicate the reception situation of the first data. For example, this method is applied to a first device.

[0006] Embodiments of this application verify the first data by determining the confidence level of the first data. So that when the confidence level meets the corresponding conditions, there is no need to retransmit the first data, thereby reducing the resource consumption caused by retransmission and reducing the latency caused by retransmission.

[0007] In a possible design, the confidence level is determined according to the log-likelihood ratios (LLR) corresponding to the first data.

[0008] Embodiments of this application apply LLR in the process of confirming the confidence level of data, so as not to indicate retransmission when the confidence level is high, thereby reducing the retransmission probability, reducing the resource consumption caused by retransmission, and at the same time reducing the latency caused by retransmission.

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

[0010] Embodiments of the present application provide various methods for determining the confidence level, and appropriate methods can be adopted in different scenarios to determine the confidence level, improving the universality.

[0011] In a possible design, the number of first bits is determined based on the LLR corresponding to the CB with CRC failure, including: the number of first bits is determined based on the LLR corresponding to the CB with CRC failure and the LLR reference value.

[0012] Embodiments 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 the bits with insufficient confidence level.

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

[0014] Embodiments of the present application can determine the LLR reference value according to the CB with successful CRC check, and can more accurately determine the bits with insufficient confidence level, improving the accuracy of the confidence level.

[0015] In a possible design, the method further includes at least one of the following steps: receiving the third information, where the third information is used to indicate the reference coefficient; determining the reference coefficient according to 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; sending the third information.

[0016] Embodiments of the present application provide various methods for determining the reference coefficient, and appropriate methods can be adopted in different scenarios to determine the reference coefficient, improving the universality.

[0017] In a possible design, the method further includes: sending the first information according to the confidence level and the first threshold, where the first information is used to indicate whether to retransmit at least one data.

[0018] The embodiments of the present application can determine whether to retransmit at least one piece of data according to the confidence level and the first threshold, so that data with a relatively high confidence level can be not retransmitted, reducing the resource consumption and latency caused by retransmission.

[0019] In a possible design, the method further includes: sending the confidence level; receiving first information, where the first information is used to indicate whether to retransmit at least one piece of data, and the first information is determined according to the confidence level and the first threshold.

[0020] The embodiments of the present application can also send the confidence level, and the peer end determines whether to retransmit the data according to the confidence level. This can reduce the hardware requirements and improve the universality.

[0021] In a possible design, sending the confidence level includes: determining the interval value where the confidence level is located according to the confidence level; sending the interval value.

[0022] The embodiments of the present application can also send the interval value of the confidence level to reduce the resource consumption caused by sending the confidence level.

[0023] In a possible design, that the first information is used to indicate whether to retransmit at least one piece of data includes: when the confidence level is less than the first threshold, the first information is used to indicate retransmitting the first data.

[0024] The embodiments of the present application determine to retransmit the first data when the confidence level is less than the first threshold. This enables some data that is received incorrectly but has a confidence level greater than or equal to the first threshold not to be retransmitted, reducing the resource consumption and latency caused by retransmission.

[0025] In a possible design, the method further includes: receiving fourth information, where the fourth information includes the first threshold; and / or determining the first threshold according to 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.

[0026] The embodiments of the present application provide multiple ways to determine the first threshold, and appropriate ways can be adopted to determine the reference coefficient in different scenarios, improving the universality.

[0027] In a possible design, the method further includes: sending the fourth information.

[0028] The embodiments of the present application can also send the first threshold when the first device determines the first threshold. So that the peer end can determine whether to retransmit the data according to the first threshold and the confidence level.

[0029] In a possible design, the method further includes: sending second information, where the second information is used to indicate the manner of indicating whether to retransmit the first data according to the confidence level; or receiving the second information.

[0030] In the embodiments of the present application, it can also be indicated by the second information whether the method of indicating whether to retransmit the first data according to the confidence level is adopted, so as to more flexibly configure the data verification methods of each device.

[0031] In a 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 a fault tolerance feature.

[0032] In the embodiments of the present application, the packet header can carry the fault tolerance feature, so that the receiving end can parse the fault tolerance feature and give feedback based on the fault tolerance feature. For data with the same fault tolerance feature, the retransmitted data can be appropriately reduced while ensuring that the data is correctly parsed, so as to reduce the resource consumption and latency caused by retransmission.

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

[0034] In the embodiments of the present application, the confidence level corresponding to the CB with correct CRC can be set to a specific value or omitted. This facilitates the subsequent determination and transmission of the confidence level of the first data.

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

[0036] The embodiments of the present application provide various data unit formats for the first data, which can be applicable to the verification of the first data based on the confidence level in different formats, improving the universality.

[0037] In a second aspect, a data verification method is provided, including: sending at least one data, where the at least one data includes the first data; receiving at least one of a confidence level and a first piece of information, where the confidence level is used to indicate the reception situation of the first data, and the first piece of information is used to indicate whether to retransmit the at least one data.

[0038] In the embodiments of the present application, the first data is verified by determining the confidence level of the first data. Such that when the confidence level meets the corresponding conditions, there is no need to retransmit the first data, so as to reduce the resource consumption and latency caused by retransmission.

[0039] In a possible design, the confidence level is determined according to the LLR corresponding to the first data.

[0040] In a possible design, the confidence level is determined based on the LLR corresponding to the first data, including at least one of the following methods: The confidence level is determined based on the LLR corresponding to the CB with CRC failure in the first data; The confidence level is determined based on the number of first bits in the first data, where the first bits are the bits in the CB with CRC failure in the first data, and the number of first bits is determined based on the LLR corresponding to the CB with CRC failure in the first data; The confidence level is determined based on the ratio of the number of first bits corresponding to the CB with CRC failure in the first data to the total code length of the first data.

[0041] In a possible design, the number of first bits is determined based on the LLR corresponding to the CB with CRC failure, including: The number of first bits is determined based on the LLR corresponding to the CB with CRC failure and the LLR reference value.

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

[0043] In a possible design, the method further includes at least one of the following steps: receiving third information, where the third information is used to indicate the reference coefficient; determining the reference coefficient according to 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; sending the third information.

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

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

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

[0047] In a possible design, receiving the confidence level includes: receiving the interval value where the confidence level is located, and the interval value is determined based on the confidence level.

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

[0049] In a possible design, the method further includes: receiving fourth information, where the fourth information includes a first threshold; and / or determining the first threshold according to 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.

[0050] In a possible design, the method further includes: sending the fourth information.

[0051] In a possible design, the method further includes: sending second information, where the second information is used to indicate the manner of indicating whether to retransmit the first data according to the confidence level; or receiving the second information.

[0052] In a 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 a fault tolerance feature.

[0053] In a possible design, the confidence level of the CB with correct CRC in the first data is a default value or is empty.

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

[0055] In a third aspect, a data verification device is provided, including: a communication module, configured to receive at least one data, where the at least one data includes the first data; a processing module, configured to determine the confidence level corresponding to the first data according to the first data, and the confidence level is used to indicate the reception situation of the first data. For example, this method is applied to the first device.

[0056] In the 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 the corresponding conditions, there is no need to retransmit the first data, so as to reduce the resource consumption caused by retransmission and reduce the delay caused by retransmission.

[0057] In a possible design, the confidence level is determined according to the LLR corresponding to the first data.

[0058] In a possible design, the confidence level is determined according to the LLR corresponding to the first data, including at least one of the following manners: the confidence level is determined according to the LLR of the CB with failed CRC in the first data; the confidence level is determined according to the number of first bits in the first data, where the first bit is the bit in the CB with failed CRC in the first data, and the number of the first bits is determined according to the LLR of the CB with failed CRC in the first data; the confidence level is determined according to the ratio of the number of first bits of the CB with failed CRC in the first data to the total code length of the first data.

[0059] In a possible design, the number of first bits is determined according to the LLR corresponding to the CB with CRC failure, including: the number of first bits is determined according to the LLR corresponding to the CB with CRC failure and the LLR reference value.

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

[0061] In a possible design, the communication module is further configured to receive third information, where the third information is used to indicate the reference coefficient; and / or, the processing module is further configured to determine the reference coefficient according to 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 further configured to send the third information.

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

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

[0064] In a possible design, the processing module is further configured to determine the interval value where the confidence level is located according to the confidence level; the communication module is further configured to send the interval value.

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

[0066] In a possible design, the communication module is further configured to receive fourth information, where the fourth information includes the first threshold; and / or, the processing module is further configured to determine the first threshold according to 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.

[0067] In a possible design, the communication module is further configured to send the fourth information.

[0068] In a possible design, the communication module is further configured to: send second information, where the second information is used to indicate the manner of indicating whether to retransmit the first data according to the confidence level; or, receive the second information.

[0069] In a 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 a fault tolerance feature.

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

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

[0072] In a fourth aspect, a data verification apparatus is provided, including: a communication module, configured to send at least one data, where the at least one data includes first data; the communication module is further configured to receive at least one of a confidence level and first information, where the confidence level is used to indicate the reception situation of the first data, and the first information is used to indicate whether to retransmit the at least one data.

[0073] In the 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 the corresponding conditions, there is no need to retransmit the first data, thereby reducing the resource consumption caused by retransmission and reducing the delay caused by retransmission.

[0074] In a possible design, the confidence level is determined according to the LLR corresponding to the first data.

[0075] In a possible design, the confidence level is determined according to the 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 CB with CRC failure in the first data; the confidence level is determined according to the number of first bits in the first data, where the first bit is a bit in the CB with CRC failure in the first data, and the number of first bits is determined according to the LLR corresponding to the CB with CRC failure in the first data; the confidence level is determined according to the ratio of the number of first bits corresponding to the CB with CRC failure in the first data to the total code length of the first data.

[0076] In a possible design, the number of first bits is determined according to the LLR corresponding to the CB with CRC failure, including: the number of first bits is determined according to the LLR corresponding to the CB with CRC failure and the LLR reference value.

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

[0078] In a possible design, the apparatus further includes a processing module. The communication module is further configured to receive third information, where the third information is used to indicate the reference coefficient; and / or, the processing module is configured to determine the reference coefficient according to 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 further configured to send the third information.

[0079] In a possible design, the communication module is further configured to receive first information, where the first information is determined according to a confidence level and a first threshold.

[0080] In a possible design, the communication module is further configured to receive a confidence level; the processing module is further configured to determine first information according to the confidence level and the first threshold; the communication module is further configured to send the first information.

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

[0082] In a possible design, the communication module is further configured to: receive an interval value where the confidence level is located, and the interval value is determined according to the confidence level.

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

[0084] In a possible design, the communication module is further configured to receive fourth information, where the fourth information includes the first threshold; and / or, the processing module is further configured to determine the first threshold according to 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.

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

[0086] In a possible design, the communication module is further configured to: send second information, where the second information is used to indicate a method of indicating whether to retransmit the first data according to the confidence level; or, receive the second information.

[0087] In a possible design, at least one piece of data corresponds to at least one packet header, and the at least one packet header is used to indicate that the at least one piece of data has a fault tolerance feature.

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

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

[0090] 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 is caused to execute the data verification method in any one of the above aspects.

[0091] In a sixth aspect, a chip system is provided. The chip system includes a processor and an input / output port. The processor is configured to implement the processing functions involved in the data verification method in any of the above aspects, and the input / output port is configured to implement the transceiver functions involved in the data verification method in any of the above aspects.

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

[0093] The chip system can be composed of chips or can include chips and other discrete devices.

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

[0095] In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions; when the computer instructions are run on a computer, the computer is caused to execute the data verification method in any design in any of the above aspects.

[0096] In a ninth aspect, a computer program product is provided. The computer program product includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer is caused to execute the data verification method in any design in any of the above aspects. Description of the Drawings

[0097] Figure 1 It is an architecture example diagram of the communication system provided by the embodiment of the present application;

[0098] Figure 2 It is a schematic diagram of hybrid automatic repeat request parallel transmission provided by the embodiment of the present application;

[0099] Figure 3 It is an example diagram of hybrid automatic repeat request feedback based on code block groups provided by the embodiment of the present application;

[0100] Figure 4 It is a schematic diagram of a communication scenario provided by the embodiment of the present application;

[0101] Figure 5 It is another schematic diagram of a communication scenario provided by the embodiment of the present application;

[0102] Figure 6 It is yet another schematic diagram of a communication scenario provided by the embodiment of the present application;

[0103] Figure 7Another schematic diagram of a communication scenario provided by an embodiment of the present application;

[0104] Figure 8 A schematic diagram of a data verification method provided by an embodiment of the present application;

[0105] Figure 9 Another schematic diagram of a data verification method provided by an embodiment of the present application;

[0106] Figure 10 A schematic diagram of screen restoration comparison provided by an embodiment of the present application;

[0107] Figure 11 A schematic diagram of adding a packet header to data provided by an embodiment of the present application;

[0108] Figure 12 A schematic diagram of the structure of a Media Access Control (MAC) protocol data unit provided by an embodiment of the present application;

[0109] Figure 13 Another schematic diagram of the structure of a Media Access Control (MAC) protocol data unit provided by an embodiment of the present application;

[0110] Figure 14 A schematic diagram of transport block division provided by an embodiment of the present application;

[0111] Figure 15 A schematic diagram of the packet header position provided by an embodiment of the present application;

[0112] Figure 16 Another schematic diagram of the packet header position provided by an embodiment of the present application;

[0113] Figure 17 A schematic diagram of data transfer from the Media Access Control (MAC) layer to the Physical layer provided by an embodiment of the present application;

[0114] Figure 18 Another schematic diagram of data transfer from the Media Access Control (MAC) layer to the Physical layer provided by an embodiment of the present application;

[0115] Figure 19 Another schematic diagram of data transfer from the Media Access Control (MAC) layer to the Physical layer provided by an embodiment of the present application;

[0116] Figure 20 Another schematic diagram of data transfer from the Media Access Control (MAC) layer to the Physical layer provided by an embodiment of the present application;

[0117] Figure 21 A schematic diagram of the interaction of a data verification method provided by an embodiment of the present application;

[0118] Figure 22 Another schematic diagram of the interaction of a data verification method provided by an embodiment of the present application;

[0119] Figure 23 Schematic diagram of another data verification method provided by an embodiment of the present application;

[0120] Figure 24 Interaction schematic diagram of another data verification method provided by an embodiment of the present application;

[0121] Figure 25 Interaction schematic diagram of yet another data verification method provided by an embodiment of the present application;

[0122] Figure 26 Flowchart of a data verification method provided by an embodiment of the present application;

[0123] Figure 27 Flowchart of another data verification method provided by an embodiment of the present application;

[0124] Figure 28 Schematic diagram of a data verification device provided by an embodiment of the present application;

[0125] Figure 29 Schematic diagram of another data verification device provided by an embodiment of the present application. Detailed implementation manners

[0126] The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation to the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art may know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0127] The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation to the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art may know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0128] Terms such as "first" and "second" in the specification and drawings of the embodiments of the present application are used to distinguish different objects, or to distinguish different processes for the same object. Words such as "first" and "second" can distinguish identical or similar items with basically the same function and role. For example, the first device and the second device are only for distinguishing different devices, and do not limit their sequence. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily limit to being different.

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

[0130] In the description of the embodiments of the present application, unless otherwise specified, " / " means that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B. The "and / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B may be singular or plural.

[0131] In the description of the embodiments of the present application, unless otherwise specified, "a plurality" means two or more than two. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c may represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c may be single or plural.

[0132] In addition, for the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and roles. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not necessarily limit to be different.

[0133] In the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific way for easy understanding.

[0134] It can be understood that the "embodiments" mentioned throughout the specification mean that specific features, structures or characteristics related to the embodiments are included in at least one embodiment of the embodiments of the present application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiments. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It can be understood that in the various embodiments of the embodiments of the present application, the magnitude of the sequence number of each process does not mean the sequence of execution order, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0135] It can be understood that in the embodiments of the present application, both "when..." and "if" refer to corresponding processing being performed under certain objective circumstances, rather than limiting time, and do not require a judgment action during implementation, nor do they imply other limitations.

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

[0137] In the embodiments of the present application, unless otherwise specified, the same or similar parts between various embodiments can be referred to each other. In the embodiments of the present application, in each embodiment and each implementation manner / implementation method / realization method in each embodiment, if there is no special specification and logical conflict, the terms and / or descriptions between different embodiments and between each implementation manner / implementation method / realization method in each embodiment are consistent and can be mutually referred to. The technical features in different embodiments and in each implementation manner / implementation method / realization method in each embodiment can be combined to form new embodiments, implementation manners, implementation methods, or realization methods according to their internal logical relationships. The implementation manners described in the following embodiments of the present application do not constitute a limitation on the protection scope of the embodiments of the present application.

[0138] Figure 1 It is an architecture example diagram of the communication system provided for the embodiments of the present application.

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

[0140] Among them, the terminal 110 and the network device 120 communicate wirelessly. The network device 120 may be a radio access network device. Terminals and terminals, as well as radio access network devices and radio access network devices, can be connected to each other by wired or wireless means. Figure 1 This is only a schematic diagram. The communication system may also include other network devices, such as wireless relay devices, wireless backhaul devices, core network devices, etc., which are not drawn in Figure 1 It. The connection relationships between devices are not limited to the above-listed manners.

[0141] The radio access network device can 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 NodeB in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it can also be a module or unit that completes some functions of the base station. For example, it can be a central unit (CU) or a distributed unit (DU). The radio access network device can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. In some other embodiments, the radio access network device can also be an access network device in an open RAN (O-RAN). In O-RAN, the CU can be called an open CU (O-CU), the DU can be called an open DU (O-DU), and the RU can be called an open RU (O-RU). The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the radio access network device. The radio access network device is sometimes also simply referred to as a network device. For ease of description, the base station is used as an example of the radio access network device in the following description.

[0142] The terminal can also be referred to as a terminal device, a user equipment (UE), a mobile station, a mobile terminal, etc. The terminal device can be widely applied to 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, remote medical treatment, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, etc. The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, etc. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the terminal device.

[0143] The base station and the terminal can be fixed in position or movable. The base station and the terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons, and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the base station and the terminal device.

[0144] Communication can be carried out between the base station and the terminal, between the base station and the base station, and between the terminal and the terminal through licensed spectrum, or through unlicensed spectrum, or through both licensed spectrum and unlicensed spectrum at the same time; communication can be carried out through spectrum below 6 gigahertz (GHz), or through spectrum above 6 GHz, or through both spectrum below 6 GHz and spectrum above 6 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0145] In the embodiments of the present application, the functions of the base station can also be performed by modules (such as chips) in the base station, or by a control subsystem including the functions of the base station. The control subsystem including the functions of the base station here can be a control center in the application scenarios of the above terminal devices such as smart grid, industrial control, intelligent transportation, and smart city. The functions of the repeater can also be performed by modules (such as chips or modems) in the repeater, or by a device including the functions of the repeater. The functions of the terminal can also be performed by modules (such as chips or modems) in the terminal, or by a device including the functions of the terminal.

[0146] In a wireless communication system, including communication devices, wireless communication can be carried out between the communication devices by using air interface resources. Among them, the communication devices can include network devices and terminal devices, and the network devices can also be called base station devices. The air interface resources can include at least one of time domain resources, frequency domain resources, code resources, and space resources.

[0147] For the XR service in the current 5G NR, the average access rate for 4K video quality is about 120 Mbps, and the delay is about 20 ms. A more typical 4K XR service requires a rate of 35 Mbps, 60 frames per second, and the air interface delay is usually within 10 ms. For immersive experience scenarios such as XRpro and holography, the requirements for cellular communication will be even higher. The average access rate will increase from 120 Mbps for 4K to about 2 gigabits per second (Gbps) for 16K. And the requirement for interactive delay is also further improved, shortened from about 20 ms currently to about 5 ms. Obviously, this poses further evolution requirements for 5G. It can be seen that the XR service has the characteristics and requirements of low delay and high rate.

[0148] Although in-depth research has been conducted on traditional Internet video communication technologies, including aspects such as congestion control and bitrate adaptation, there are still some challenges. In real-time video applications, the problems of packet jitter and loss have a significant adverse impact on the user experience. When there is packet jitter, packets arrive at the receiving end at irregular speeds, which leads to instability in video decoding and playback. When packets are lost, retransmission of the packets is required, which introduces additional latency, affects the timely decoding of multiple frames, and results in video stuttering and unsmooth playback. In the current communication system, feedback retransmission, as a relatively mature technology, achieves effective error control.

[0149] The hybrid automatic repeat request (HARQ) mechanism in the media access control (MAC) layer is a retransmission mechanism. This retransmission mechanism enables the sending end to perform fast retransmission based on the feedback result by immediately feeding back the result of successful or failed information transmission from the receiving end to the sending end.

[0150] Reference Figure 2 , the HARQ mechanism adopts the stop-and-wait protocol. Among them, the stop-and-wait protocol has the following two characteristics. One characteristic is that the receiving end will send feedback information to the sending end. Whether the information is correctly received by the receiving end or not, the receiving end needs to feedback the receiving situation to the sending end. Another characteristic is that the sending end must receive the feedback information from the receiving end before continuing to send information. Before the previous information is confirmed, the sending end will not send the next information.

[0151] The stop-and-wait protocol requires the sending end to stop and wait for the feedback from the receiving end every time it sends information, just as Figure 2For HARQ process 1, HARQ process 2, and HARQ process 3, after the sender sends the corresponding transport block (TB) for each HARQ process, it will wait for the 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 this HARQ process fails. 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 acknowledgement (ACK) to indicate that the data transmission on this HARQ process is successful. Regardless of which HARQ process it is, the sender will send new data after receiving the ACK or NACK feedback from the receiver. For example, if the sender receives a NACK for HARQ process 1, it can retransmit TB1, and if it receives an ACK for HARQ process 2 and HARQ process 3, it can transmit new TBs, such as TB4, TB5, etc. on the corresponding HARQ processes.

[0152] Assume that multiple HARQ processes are executed serially. If the stop-and-wait protocol is adopted, the throughput will be very low. Therefore, for example Figure 2 Fig. shows a schematic diagram of parallel transmission of multiple HARQ processes. Usually, parallel processing of multiple HARQ processes is adopted. In this way, when one HARQ process is waiting for acknowledgement, the sender can continue to send information through another HARQ process. Similarly, when the receiver is processing the information received by one process, it can also continue to receive information through another process. Parallel processing of multiple HARQ processes can form a HARQ entity. For each uplink or downlink carrier, it can be considered that there is a corresponding HARQ entity. In some scenarios, it is allowed that one HARQ entity supports up to 16 HARQ processes. Each HARQ process has an independent HARQ feedback.

[0153] In some examples, if the transmitting end sends the transport block (TB) in units of code blocks (CBs), the receiving end can feedback the CBs with code errors. In this way, the transmitting end can retransmit the CBs with decoding errors, which can reduce the retransmission overhead compared with retransmitting the entire TB. However, considering the feedback in units of CBs, since a TB contains multiple CBs, the feedback information will also increase significantly, resulting in a corresponding increase in the overhead of control signaling. In some examples, by introducing a compromise method in NR, i.e., retransmission based on code block groups (CBGs), multiple CBs are grouped into a CBG, and feedback is made based on each CBG. Of course, when retransmitting, only the faulty CBG can be retransmitted. Compared with retransmitting the entire TB, retransmission based on CBGs can reduce resource consumption. And compared with feedback for each CB, feedback based on CBGs can reduce signaling overhead.

[0154] In some examples, according to the number of initially transmitted CBs, the TB can be divided into 2, 4, 6, or 8 CBGs. The network device can indicate the CBG division method to the terminal through high-layer signaling parameters. Once the CBG division is completed, the mapping relationship between each CBG and the CBs is fixed and will not change even after multiple retransmissions, so as to ensure the accuracy of retransmission information.

[0155] Figure 3Fig. shows a schematic diagram of CBG-based HARQ feedback. It can be seen that the transmitting end can divide 1TB into 4 CBGs, namely CBG0, CBG1, CBG2, and CBG3. Among them, CBG0 and CBG3 are successfully received by the receiving end, while CBG1 and CBG2 are received by the receiving end unsuccessfully. Then the receiving end can perform feedback based on CBGs, that is, feedback ACK or NACK for each CBG respectively. The transmitting end can determine to retransmit CBG1 and CBG2 according to the feedback information from the receiving end. When the receiving end receives the retransmitted CBG1 and CBG2, it can delete the caches of the originally received incorrectly CBG1 and CBG2. The receiving end can also feedback ACK to inform the transmitting end that there is no need to retransmit and new data can be transmitted. For example, when the transmitting end performs retransmission, it can indicate whether the data is initial transmission data or retransmission data through a new data indicator (NDI). If the NDI indicates initial transmission data, the receiving end will consider all data as initial transmission data. If the NDI indicates retransmission data, the receiving end can determine which CBGs are retransmitted according to the codeblock 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 according to the code block group flushing out information (CBGFI). Refer to Figure 3 , when the transmitting end sends retransmission information, the CBGTI can be 0110, indicating that the second and third CBGs are the retransmitted CBGs. CBGFI being 0 can indicate that the cached CBG1 and CBG2 in between can be cleared.

[0156] In the above retransmission scheme, the receiving end can use the cyclic redundancy check (CRC) method to determine whether the data is received successfully. For example, after attaching a check code with an R-bit length to the data with a K-bit length sent, 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 is received correctly according to the data and the check code in the data frame.

[0157] However, the current CRC verification has an error rate of data reception errors that require feedback retransmission, which often cannot meet the needs of some ultra-reliable low-latency communications (URLLC) data services. If the HARQ feedback error rate is to be reduced, more feedback signaling needs to be added. This makes HARQ feedback very frequent and causes a lot of control signaling overhead. Frequent retransmissions will also lead to more data resource overhead and cause greater delays. Therefore, how to reduce the resource overhead and delay overhead caused by retransmission is a problem that needs to be solved at present.

[0158] Therefore, the embodiment of the present application provides a data verification method, which determines whether the first data needs to be retransmitted by determining the confidence of the first data, so that when the confidence meets the corresponding conditions, the first data does not need to be retransmitted, thereby reducing the resource consumption caused by the retransmission and reducing the delay caused by the retransmission.

[0159] Figure 4 , Figure 5 , Figure 6 and Figure 7 Various communication scenarios applicable to the embodiments of the present application are shown. The embodiments of the present application can be applicable to point-to-point single-connection communication in standalone (SA) scenarios such as between network devices and terminals. It is also applicable to multi-hop single-connection communication scenarios between network devices and terminals, such as 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 and the like. 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.

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

[0161] The solution provided by the embodiments of this application can be applied to wireless communication between communication devices. Among them, wireless communication can include: wireless communication between a network device and a terminal, wireless communication between network devices, and wireless communication between terminals. In the embodiments of this application, the term "wireless communication" can also be abbreviated as "communication", and the term "communication" can also be described as "data transmission", "information transmission", or "transmission".

[0162] The embodiments of this application can be used in possible communication links such as uplink (UL), downlink (DL), access link, backhaul link, sidelink (SL), etc., and the embodiments of this application do not make any limitations here. From the perspective of service scenarios, the embodiments of this application are applicable to multiple scenarios, such as hierarchical data coding in XR services, uplink high-capacity scenarios, etc., and the embodiments of this application do not make any limitations here.

[0163] Figure 8 It is a schematic diagram of a data verification method provided by the embodiments of this application.

[0164] As Figure 8 shown, this communication process can be applicable to but not limited to Figure 1 , Figures 4 to 7 the communication scenarios shown. In each embodiment of this application, the sending 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 can include the following steps:

[0165] S101, the sending end sends at least one piece of data to the receiving end.

[0166] In some embodiments, the sending end can send at least one piece of data to the receiving end. Among them, the at least one piece of data can include the first data. The first data can be any one of the at least one piece of data. In some embodiments, the receiving end can receive the at least one piece of data sent by the sending end. For example, the receiving end receives the first data sent by the sending end.

[0167] In some embodiments, the sending 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 sending end is a base station and the receiving end is a terminal, or the sending end is a terminal and the receiving end is a base station, or both the sending end and the receiving end are terminals. It can be considered that the sending end and the receiving end can be different devices in different communication scenarios, and the specific forms of the sending end and the receiving end can be determined according to the actual communication scenario, and the embodiments of this application do not make any limitations here.

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

[0169] In some embodiments, the first data may be divided in units of CBGs, that is, the first data is one CBG. Then, the first data may include multiple CBs.

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

[0171] S102. The receiving end determines the confidence level corresponding to the first data according to the first data.

[0172] In some embodiments, the receiving end may receive the first data according to S101 and determine the confidence level (confident) corresponding to the first data. Among them, the confidence level may be used to indicate whether to retransmit the corresponding first data.

[0173] For example, the receiving end may perform CRC check on the received first data. For the first data with CRC check error, the receiving end may determine the confidence level of such first data to indicate whether such first data with CRC check error 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 more inclined not to retransmit the first data. When the confidence level indicates that the first data is less reliable, the more inclined to retransmit the first data.

[0174] For another example, for the first data with correct CRC check, there may also be a corresponding confidence level, or the confidence level of such first data with correct CRC check may be omitted.

[0175] In the embodiments of the present application, descriptions such as CRC check passed, CRC correct, CRC check correct, CRC successful, CRC check successful, etc. can 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 wrong, CRC check error, CRC check error, CRC check not successful, etc. can be considered to have the same meaning, indicating that the data is received incorrectly after CRC check.

[0176] In some embodiments, the confidence level corresponding to the first data may be determined according to the log-likelihood ratios (LLR) corresponding to the first data. In some examples, the LLR may be determined for each bit in the data. For example, assume x k，q is the q-th bit of the transmission symbol S of the k-th transmitting antenna, then the LLR of the posterior probability for this x k，q can be represented by formula 1.

[0177]

[0178] Among them, P(x k，q =0|y) represents the probability that x in the transmitted symbol S is 0 when the received symbol is y k，q . Similarly, P(x k，q =1|y) represents the probability that x in the transmitted symbol S is 1 when the received symbol is y k，q . Therefore, LLR(x k，q ) can be considered to represent whether this x k，q bit is more likely to be 0 or more likely to be 1

[0179] In the related art, after the receiving end receives a wireless signal, channel equalization, detection, etc. can be performed, and the LLR value corresponding to each bit is output to the channel decoder. For example, the channel decoder can be a low density parity check (LDPC) decoder. The channel decoder can iteratively recover the transmitted bits according to the LLR corresponding to each bit. Then CRC check is performed to verify the accuracy of bit recovery. In this technology, LLR is only utilized in the bit recovery stage. For example, the LLR value is used to determine the tendency of the received bit to be 0 or 1

[0180] Considering that LLR has the characteristic of being able to reflect the probability that the received bit is 0 or 1, in the embodiments 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 this x k，q bit may be 0, and a negative LLR value indicates that this x k，q bit may be 1. And when the LLR value is positive, the larger the value, the higher the probability that this x k，q bit is 0. And when the LLR is negative, the smaller the value, the higher the probability that this x k，q bit is 1. Therefore, by taking the absolute value of the LLR value, the magnitude of the absolute value of this LLR value can reflect the reliability degree of this x k，q bit. For example, the larger the absolute value of LLR, the higher the reliability of this bit. Therefore, in the embodiments of the present application, applying LLR in the process of data confidence confirmation can enable some erroneously received data to determine the confidence based on LLR, so as not to indicate retransmission when the confidence is relatively high, thereby reducing the retransmission probability and the resource consumption caused by retransmission, and at the same time reducing the delay caused by retransmission

[0181] As follows, the embodiments of the present application introduce several ways to determine the confidence of the first data according to the LLR of the received first data

[0182] Method 1

[0183] In some embodiments, the confidence level can be determined based on the LLR corresponding to the CB with CRC failure in the first data.

[0184] For example, for the CB with CRC failure, the confidence level of this CB can be determined. Among them, the average value of the absolute values of the LLRs of each bit in this CB can be used as the confidence level of this CB. As shown in Formula 2,

[0185]

[0186] Among them, C represents the confidence level of the CB with CRC failure in the first data, which can be used to represent the reliability of this CB with CRC failure. K represents the code length of this CB, and it can also be considered as the total number of bits in this CB with CRC failure. The value of k ranges from 1 to K. ∑ k |LLR k | represents the sum of the absolute values of the LLRs of each bit in this CB with CRC failure.

[0187] It can be seen from Formula 1 that for the CB with CRC failure, if the confidence level of this CB is higher, it means the reliability of this CB is higher, and it can also be considered that the probability of transmission error of this CB is lower. Assuming that the CB with CRC failure contains 3 bits, the confidence level of this CB can be expressed as

[0188] Another example is that the sum of the absolute values of the LLRs of each bit in this CB can be used as the confidence level of this CB. As shown in Formula 3,

[0189] C = ∑ k |LLR k |

[0190] .....Formula 3

[0191] In this way, in the embodiments of the present application, LLR is applied in the process of confirming the confidence level of the first data, which can enable some received incorrect data to determine the confidence level of this data based on the LLR of this data. So that in the subsequent process, retransmission can not be indicated when the confidence level is relatively high, thereby reducing the retransmission probability, reducing the resource consumption caused by retransmission, and at the same time reducing the delay caused by retransmission.

[0192] Method 2:

[0193] In some embodiments, the confidence level can be determined according to the number of first bits. Herein, the first bits are the bits in the CBs where CRC fails in the first data, and the number of first bits is determined according to the LLR corresponding to the CBs where CRC fails in the first data. In various embodiments of the present application, it can also be considered that the confidence level is determined according to the first bits. For example, it is determined according to 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 number.

[0194] In some examples, the first bit number can refer to the bits with insufficient confidence levels in the CBs where CRC fails in the first data, or the bits with relatively low confidence levels. In other examples, the first bit number can refer to the bits with relatively high confidence levels in the CBs where CRC fails in the first data. The embodiments of the present application do not make any limitations in this regard.

[0195] The following description of the present application will take the first bit number being the bits with insufficient confidence levels as an example, but those skilled in the art should understand that the embodiments of the present application do not limit whether the first bit number is the bits with insufficient confidence levels or the bits with relatively high confidence levels.

[0196] For example, the number of bits with insufficient confidence levels in the CBs where CRC fails can be counted, that is, the first bit number. The confidence level of the first data is represented by this first bit number. For example, the more the first bit number, it means that more bits in the CBs where CRC fails may be incorrect bits, so it is more inclined to retransmit the CBs where CRC fails. On the contrary, the fewer the first bit number, it means that more bits in the CBs where CRC fails may be bits that pass the CRC check, so it is more inclined not to retransmit the CBs where CRC fails.

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

[0198] For example, for the CBs where CRC check fails, the first bit number can be obtained by determining the relationship between the absolute value of the LLR of each bit in the CB and the LLR reference value. Herein, the LLR reference value can be denoted as L ref .

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

[0200] Of course, in some examples, it is also possible to determine the number of the first bits according to some bits in the CB with a failed CRC verification and L ref for comparison. Among them, the selection of some bits can be determined according to the actual situation. For example, 1 bit is selected from every 2 bits for comparison with L ref for comparison. Or, any selected number of bits are compared with L ref for comparison, which is not limited in the embodiments of the present application.

[0201] In some embodiments, the LLR reference value can be determined according to the LLR corresponding to the CB with successful CRC in the first data and the reference coefficient.

[0202] For example, the LLR values corresponding to the CBs with correct CRC can be statistically determined to obtain L ref . For example, it can be obtained by taking the average of the LLR values of the CBs with correct CRC. As shown in Formula 4,

[0203]

[0204] where M R represents the total number of CBs passing the CRC check, and the value of m ranges from 1 to M R . LLR m，k represents the LLR value of the k-th bit in the m-th CB. "·" represents the multiplication operator. ε represents the reference coefficient, ε is a constant and takes a positive value. Among them, ε 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 checks. CB1 contains 3 bits, and CB2 contains 3 bits. Then L ref can be expressed as where |LLR 1，1 | is the absolute value of the LLR value of the first bit in CB1, and the meanings of |LLR 1，2 | and the like are similar, and are not elaborated in the embodiments of the present application.

[0205] In some examples, assume that ε is 1, then L ref can be considered to be the average of the absolute values of the LLRs in the CBs with correct CRC. Assume that ε is greater than 1, then Lref will be higher than the average of the absolute values of the LLRs in the CRC-correct CBs. Assuming ε is less than 1, then L ref will be lower than the average of the absolute values of the LLRs in the CRC-correct CBs.

[0206] It can be understood that the larger the value of ε, the more bits will likely have absolute values of LLR less than L ref . And when the number of the first bits of a CB is larger, it means that more bits of the CB are likely to have CRC check errors. Therefore, it can be considered that the larger the value of ε, the more inclined to retransmit data.

[0207] In some embodiments, the method further includes at least one of the following steps: receiving third information for indicating ε; determining a reference coefficient according to 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; sending the third information.

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

[0209] Again, for example, the first device can determine the reference coefficient according to 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 can be the radio interface traffic congestion condition, the noise interference condition during signal transmission, the obstacle blocking condition, etc. Also, the service type corresponding to the first data can be service requirements, such as lower latency, higher transmission rate, etc. Again, the service priority can indicate whether the service corresponding to the first data is important. For example, for unimportant services, a lower ε can be used to reduce the possibility of data retransmission. In this case, it can be considered that ε is determined by the first device.

[0210] Once again, for example, the first device can send the third information to the second device. In this case, it can be considered that ε is determined by the first device.

[0211] Of course, in the above multiple examples, it is not specified which of the first device and the second device is the transmitter and which is the receiver. That is to say, the first device can be either the transmitter or the receiver. Of course, if the first device is the transmitter, then the second device is the receiver. Conversely, if the first device is the receiver, then the second device can be the transmitter.

[0212] Analyze the determination of the value of ε from the perspectives of uplink communication and downlink communication. For the uplink communication process, for example, the value of ε can be determined by the terminal according to service requirements, and the terminal can inform the network device through the application layer. For another example, the network device can determine a value of ε according to the congestion status of the air interface traffic.

[0213] For the downlink communication process, the value of ε can also be determined by the terminal according to service requirements and informed to the network device through the application layer. Then, the network device informs the terminal through radio resource control (RRC) signaling, MAC control element (CE), and / or DCI. The purpose of doing this is that the ε determined by the terminal is application layer information and is unknown to the physical layer. It is necessary to make the physical layer of the terminal know the value of ε through this method. For another example, the network device can determine a value of ε according to the congestion status of the air interface traffic and inform 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 service requirements.

[0214] It can be understood that ε can be determined by any one or more of the above methods. For example, after a device determines ε, it sends ε to the peer device. Or, a device receives the ε sent by other devices, and this device determines a new ε according to the signal quality, service type, etc. between the devices, and jointly determines a suitable reference coefficient according to the received ε and the new ε. Optionally, this device can also synchronize the suitable reference coefficient reselected with other devices. The embodiments of the present application do not limit the method for determining ε.

[0215] Taking the first bit being the bit with insufficient confidence as an example above, in some other embodiments, the first bit can be the bit with high confidence. For example, the number of bits with high confidence in the CB with CRC failure can be counted. This number of bits can be called the first bit number. The confidence of the first data is represented by this first bit number. For example, the more the first bit number, it means that more bits in the CB with CRC failure may be correct bits, so in the subsequent process, it can be more inclined not to retransmit the CB with CRC failure. On the contrary, the fewer the first bit number, it can be more inclined to retransmit the CB with CRC failure.

[0216] Method 3:

[0217] In some embodiments, the confidence can be determined according to the proportion of the number of the first bits corresponding to the CB with CRC failure in the first data to the total code length of the first data.

[0218] In some examples, the proportion of the number of the first bits in the total code length of the first data can be determined as the confidence level. For example, the number of the first bits corresponding to the 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 proportion. This proportion can be used as the confidence level corresponding to the first data.

[0219] Optionally, the number of the first bits in this method is similar to the number of the first bits in Method 2, and can refer to the bits with insufficient confidence levels in the CBs with CRC failures in the first data, or the bits with relatively low confidence levels. The number of the first bits can also refer to the bits with relatively high confidence levels in the CBs with CRC failures in the first data. The embodiments of the present application do not make any limitations in this regard.

[0220] It can be understood that this proportion can represent the proportion of the bits with insufficient confidence levels in the first data in the whole data. The higher this proportion is, the more bits with insufficient confidence levels there are in the first data, and the more inclined the first data is to be retransmitted. The lower this proportion is, the fewer bits with insufficient confidence levels there are in the first data, and the more inclined the first data is not to be retransmitted.

[0221] For example, the total code length of the first data is 3 bits, and 2 bits of the CBs with CRC verification failures in the first data are bits with insufficient confidence levels. Then, it can be determined that the proportion of the bits with insufficient confidence levels is 2 / 3, and 2 / 3 can be used as the confidence level of the first data.

[0222] In some examples, assume that the sender sends CB1, CB2, and CB3, and among them, CB1 fails the CRC verification. Then, it can be determined whether to retransmit CB1 according to the confidence level of CB1.

[0223] In some other examples, assume that the sender sends CBG1, CBG2, and CBG3, and among them, CB1 in CBG2 fails the CRC verification. Then, the confidence level of CBG2 can be calculated according to the confidence level of CB1, and it can be determined whether to retransmit CBG2 according to the confidence level of CBG2.

[0224] In still some other examples, assume that the sender sends TB1, TB2, and TB3, and among them, CB1 in TB2 fails the CRC verification. Then, the confidence level of TB2 can be calculated according to the confidence level of CB1, and it can be determined whether to retransmit CBG2 according to the confidence level of TB2.

[0225] Among them, the confidence level of CB1 in the above examples can be determined by any one of the above Method 1, Method 2, and Method 3.

[0226] In the embodiments of the present application, by determining the confidence level of the first data, it is determined whether it is necessary to retransmit the first data. So that when the confidence level meets the corresponding conditions, there is no need to retransmit the first data, thereby reducing the resource consumption caused by retransmission and reducing the latency caused by retransmission.

[0227] Figure 9 It is a schematic diagram of another data verification method provided by the embodiments of the present application. As Figure 9 shown, this method can be applicable to Figure 1 , Figures 4 to 7 the communication scenarios shown. This method may include the following steps:

[0228] S201, the sending end sends at least one piece of data to the receiving end.

[0229] S202, the receiving end determines the confidence level corresponding to the first data according to the first data.

[0230] It can be understood that S201 is similar to S101, S202 is similar to S102, and the specific implementation processes of S201 and S202 can refer to Figure 8 the descriptions of the corresponding steps in the corresponding embodiments, and the embodiments of the present application will not be elaborated herein.

[0231] S203, the receiving end determines the first information according to the confidence level corresponding to the first data.

[0232] In some embodiments, the receiving end may obtain the first information according to the confidence level corresponding to the first data determined in S202. Among them, the first information can be used to indicate whether to retransmit at least one piece of data received in S201.

[0233] For example, the receiving end can determine the first information according to the confidence level corresponding to the first data and the first threshold. 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 regarded as a response message different from 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 the 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 the second response, it can indicate that the first data needs to be retransmitted.

[0234] For example, the first response can be a feature acknowledgement (FACK), which is used to indicate that the corresponding first data is successfully transmitted. The second response can be a feature negative acknowledgement (FNACK), which is used to indicate that the corresponding first data transmission fails.

[0235] In some examples, when the confidence level is determined according to the LLR corresponding to the CB with CRC failure in the first data, the first threshold can be denoted as C threshold . The receiving end can compare the confidence level of the first data with C threshold to determine the first piece of information. If the confidence level of the first data is greater than or equal to C threshold , it can be considered that the confidence level of the first data is relatively high and can be determined as FACK, indicating that retransmission is not required. If the confidence level of the first data is less than C threshold , it can be considered that the confidence level of the first data is relatively low and can be determined as FNACK, indicating that retransmission is required. Of course, for the case where the confidence level of the first data is equal to C threshold , it can also be considered that the first data is retransmitted. Specifically, according to the actual situation, when the confidence level of the first data is equal to C threshold , it can be considered that the first data is retransmitted or not retransmitted. The embodiments of the present application do not make any limitations here

[0236] In some examples, FACK and FNACK can be feedback based on CB, that is to say, the minimum feedback unit in the first piece of information is CB. The receiving end can determine whether the CB needs to be retransmitted according to the confidence level of the CB, that is, determine whether the CB corresponds to FACK or FNACK. Among them, the confidence level of the CB can be determined by the above formula 2 or formula 3

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

[0238] For example, assume that the sending end sends CB1 and CB2, and the receiving end receives CB1 and CB2 and performs CRC checks respectively. Assume that CB1 is a CB with successful CRC check and CB2 is a CB with failed CRC check. The receiving end can determine the confidence level of CB2 and determine the relationship between the confidence level of CB2 and C threshold . Assume that the confidence level of CB2 is less than C threshold , the receiving end can determine that CB2 corresponds to FNACK. For CB1, it can directly determine that the CB corresponds to FACK or directly omit it. The receiving end can send the first piece of information to the sending end, and the first piece of information includes FNACK corresponding to CB2. Optionally, the first piece of information also includes FACK corresponding to CB1

[0239] In some examples, FACK and FNACK can be feedback based on CBG. That is to say, the minimum feedback unit in the first information is CBG. Then, it is possible to determine whether the CBG needs to be retransmitted according to the confidence levels of one or more CBs in the CBG. For example, if a CBG includes 4 CBs, the confidence level of the CBG can be determined according to the confidence levels of the 4 CBs in the CBG. For example, the confidence level of the CBG is the average of the confidence levels of the 4 CBs. Another example is that the confidence level of the CBG can be determined according to the confidence levels of some of the 4 CBs. For example, it is determined according to the average of the confidence levels of a certain 2 CBs among the 4 CBs, or determined according to the average of the confidence levels of a certain 3 CBs among the 4 CBs, and so on.

[0240] It can be understood that the average value is only one way to determine the confidence level of the CBG. Other possible methods such as variance and standard deviation can also be used to calculate the confidence levels of some CBs in the CBG to obtain the confidence level of the CBG. The embodiments of the present application do not make any limitations here.

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

[0242] For example, assume that the sender sends CBG1 and CBG2, and the receiver receives CBG1 and CBG2 and performs CRC checks on the CBs in each CBG respectively. Assume that the CRC checks of the CBs in CBG1 are all successful, CB1 in CBG2 is a CB with successful CRC check, and CB2 is a CB with failed 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 the default value 0. The receiver determines the relationship between the confidence level of CBG2 and C threshold . Assume that the confidence level of CBG2 is less than C threshold , the receiver can determine that CBG2 corresponds to FNACK. For CBG1, it can be directly determined that the CBG corresponds to FACK or directly omitted. The receiver can send the first information to the sender, and the first information includes that CBG2 corresponds to FNACK. Optionally, the first information also includes that CBG1 corresponds to FACK.

[0243] In some examples, FACK and FNACK can be feedback based on TBs. That is to say, the minimum feedback unit in the first piece of information is a TB. Wherein, a TB can include multiple CBGs, and each CBG can include multiple CBs. Therefore, the receiving end can determine the confidence level of a CBG according to the confidence levels of one or more CBs in the CBG. And determine the confidence level of a TB through the confidence levels of one or more CBGs in the TB. The method for determining the confidence level of a CBG can refer to the foregoing embodiments for determining the confidence level of a CBG. The method for determining the confidence level of a TB is similar to the method for determining the confidence level of a CBG, and will not be elaborated herein in the embodiments of the present application.

[0244] For example, if the confidence level of a TB is greater than or equal to C threshold , it is determined that the TB corresponds to FACK; if the confidence level of the TB is less than C threshold , it is determined that the TB corresponds to FNACK.

[0245] It can be understood that assuming the sending end sends TB1 and TB2, the way for the receiving end to send the first piece of information indicating which TB needs to be retransmitted is similar to the implementation process when the first data is a CBG, and will not be elaborated herein in the embodiments of the present application.

[0246] In some examples, when the confidence level is determined according to the number of the first bits corresponding to the CBs with CRC failures in the first data, the first threshold can be denoted as N threshold . The receiving end can compare the confidence level of the first data with N threshold to determine the first piece of information. It can be understood that the way of comparing the confidence level of the first data with N threshold is similar to the way of comparing the confidence level of the first data with C threshold . Specifically, reference can be made to the description of the foregoing embodiments related to C threshold , and will not be elaborated herein in the embodiments of the present application.

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

[0248] For another example, the receiving end can perform feedback based on the CBG. In this case, it is possible to determine whether the CBG needs to be retransmitted according to the number of the first bits corresponding to the CBG. Among them, the number of the first bits of the CBG can be determined according to the number of the first bits of one or more CBs in the CBG. For yet another example, the receiving end can perform feedback based on the TB. In this case, it is possible to determine whether the TB needs to be retransmitted according to the number of the first bits corresponding to the TB. Among them, the number of the first bits of the TB can be determined according to the number of the first bits of one or more CBGs in the TB. And the number of the first bits of the CBG can be determined according to the number of the first bits of one or more CBs in the CBG.

[0249] It can be understood that for the determination method of the number of the first bits of the CBG, reference can be made to the determination process of the confidence level of the CBG when determining the LLR based on the CB. For the determination method of the number of the first bits of the TB, reference can be made to the determination process of the confidence level of the TB when determining the LLR based on the CB. The embodiments of the present application will not elaborate herein.

[0250] In some examples, when the confidence level can be determined according to the proportion of the number of the first bits in the total code length of the first data, the first threshold can be denoted as ρ. threshold The receiving end can compare the confidence level of the first data with ρ threshold to determine the first information. It can be understood that the comparison method between the confidence level of the first data and ρ threshold is similar to the comparison method between the confidence level of the first data and C threshold or the comparison method between the confidence level of the first data and N threshold . Specifically, reference can be made to the description of the related embodiments of C threshold and the description of the related embodiments of N threshold . The embodiments of the present application will not elaborate herein.

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

[0252] For another example, the receiving end can provide feedback based on the CBG. In this case, it can be determined whether the CBG needs to be retransmitted according to the ratio of the number of the first bits corresponding to the CBG to the total code length of the first data. For still another example, the receiving end can provide feedback based on the TB. In this case, it can be determined whether the TB needs to be retransmitted according to the ratio of the number of the first bits corresponding to the TB to the total code length of the first data. The number of the first bits of the CBG and the number of the first bits of the TB can refer to the descriptions in the corresponding examples above, and will not be elaborated in the embodiments of the present application.

[0253] Obviously, for a larger number of the first bits or a larger ratio of the number of the first bits to the total code length of the first data, it can be considered that the reliability of the corresponding CB, CBG or TB is lower.

[0254] In some embodiments, the first threshold can be dynamically adjusted according to current air interface transmission conditions, transmission quality requirements, etc. For example, in the case of good air interface transmission conditions and high transmission quality requirements, a higher first threshold can be selected. In this way, more data can be retransmitted while meeting the transmission conditions to ensure that the receiving end can process the corresponding services based on more accurate data.

[0255] In some examples, the first threshold can be received by the receiving end from other devices. For example, it can be sent by the sending end. For example, the receiving end receives the fourth information sent by the sending end, and the fourth information includes the first threshold. In this case, the first threshold can be determined by the sending end.

[0256] In some examples, the first threshold can be determined according to 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 can be the sending end and the receiving end. For example, the first device is the sending end and the second device is the receiving end. Or the first device is the receiving end and the second device is the sending end.

[0257] For example, the receiving end can determine the first threshold according to the signal quality between the receiving end and the sending end. For example, the first threshold can be determined according to the air interface traffic congestion condition, the noise interference condition during signal transmission, the obstacle blocking condition, etc. between the sending end and the receiving end.

[0258] For example, the receiving end can determine the first threshold according to the service type corresponding to the first data. For example, the service type can include requirements for lower latency, higher transmission rate, etc.

[0259] For example, the receiving end can determine the first threshold according to the service priority corresponding to the first data. The service priority can indicate whether the service corresponding to the first data is important. For example, for an unimportant service, a lower first threshold can be adopted to reduce the possibility of data retransmission.

[0260] It can be understood that the first threshold can be determined by any one or more of the above methods. For example, after a device determines the first threshold, it sends the first threshold to the peer device. Or, a device receives the first threshold sent by other devices, and the device determines a new first threshold according to the signal quality, service type, etc. between the devices, and jointly determines a suitable threshold based on the received first threshold and the new first threshold. Optionally, the device can also synchronize the selected suitable threshold with other devices. The embodiments of the present application do not limit the method for determining the first threshold.

[0261] S204, the receiving end sends the first information to the sending end.

[0262] In some embodiments, after the receiving end determines the first information in S203, it can send the first information to the sending end. So that the sending end can determine which of the at least one data sent in S201 needs to be retransmitted according to the first information.

[0263] For example, assume that the sending end sends CB1 and CB2, and CB1 fails the CRC check. Then the receiving end can determine whether to retransmit CB1 according to the confidence level of CB1. If the receiving end determines to retransmit CB1, the receiving end can send the first information to the sending end. The first information may include feedback information for indicating CB1 to indicate the sending end to retransmit CB1. The sending end can determine to retransmit CB1 based on the first information. Again, the receiving end can also determine the confidence level of CB2. If CB2 passes the CRC check, or although CB2 fails the CRC check but the confidence level of CB2 is high. Then the first information may also include feedback information for indicating CB2 to indicate the sending end not to retransmit CB1, or there is no feedback information indicating CB2 in the first information.

[0264] Similarly, CB in the above example can also be replaced by CBG or TB, and the embodiments of the present application do not limit this here.

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

[0266] In some embodiments, the receiving end can also determine whether to retransmit the first data corresponding to FNACK according to the actual situation. For example, if the air interface traffic between the sending end and the receiving end is very congested, the sending end can choose to retransmit some of the first data corresponding to FNACK, so as to reduce the resource consumption caused by retransmitted data.

[0267] In some embodiments, for some of the first data that does not need to be retransmitted, the feedback message of such first data can be omitted from the first information, or the feedback can be FACK. For example, assume that the first information is feedback in CB. Then, some CBs with correct CRC checks can be not retransmitted, that is, the feedback information of such CBs can be FACK. Then, the feedback information of such CBs can be directly omitted from the first information. Or, the feedback information of the CBs here can be a default value. Wherein, the default value can be considered as a preset default value. When the feedback information is this default value, it means that the corresponding first data does not need to be retransmitted.

[0268] In the embodiment of the present application, the receiving end can obtain the first information according to the confidence level of the first data, and send the first information to the sending end to instruct the first data whose confidence level does not meet the corresponding conditions to be retransmitted. Then, for the first data whose confidence level meets the corresponding conditions, there is no need to retransmit, which can reduce the resource consumption caused by retransmission and reduce the delay caused by retransmission.

[0269] Considering that when an XR scenario is involved, the data sent by the sending end may be suitable for recovery based on a feature stream. For example, in the case of video data, there is an artificial intelligence (AI)-based video encoding and decoding scheme. The data transmitted by such a scheme can use a feature stream with fault tolerance features for data recovery. For example, even if the received bits are incorrect, they can still be repaired by a configured generator. Ensure that a video with better quality is recovered at the receiving end. Part of the data with the same fault tolerance features can be considered to belong to the same feature stream. That is to say, the receiving end can recover the data in the feature stream based on a feature stream. Refer to Figure 10 As shown, compared with the scheme based only on CRC check, a picture with data errors cannot be displayed. For the AI-based video encoding and decoding scheme, although the received data is incorrect, the original picture can still be recovered.

[0270] In some examples, for the data of layer 2, reference can be made to Figure 11Add a packet header to the data in the following manner and pass it layer by layer until it is passed to the physical layer for transmission. For example, the data in the Internet Protocol (IP) layer, i.e., the IP packet. After this IP packet is passed to the Service Data Adaptation Protocol (SDAP) layer, it can be used as the SDAP Service Data Unit (SDU). In the SDAP layer, the corresponding packet header of this layer can be added to the SDAP SDU to obtain the Protocol Data Unit (PDU) of the SDAP layer. Then continue to pass the SDAP PDU to the next lower layer, that is, to the Packet Data Convergence Protocol (PDCP) layer. Similar to the SDAP layer, in the PDCP layer, the SDAP PDU is called the PDCP SDU. And the corresponding packet header of this layer can be added to the PDCP SDU to obtain the PDCP PDU and continue to pass it to the next lower layer. Similar to the SDAP layer and the PDCP layer, in the Radio Link Control (RLC) layer, the PDCP PDU is called the RLC SDU. And the corresponding packet header of this layer can be added to the RLC SDU to obtain the RLC PDU and continue to pass it to the next lower layer. For the MAC layer, similar to the SDAP layer, the PDCP layer, and the RLC layer, the RLC PDU can be called the MAC SDU. And the corresponding packet header of this layer can be added to the MAC SDU to obtain the MAC PDU.

[0271] Of course, in different layers, the data lengths of the PDUs in each layer can be different. For example, for the MAC layer, according to the pre-determined PDU size of this layer, the data corresponding to one or more PLC PDUs in the RLC layer can be combined to form a MAC PDU. The MAC PDU can be carried by the transport block (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 It is only an exemplary representation of adding a packet header during the transfer process of a kind of data between different layers. Different lengths of PDUs can be defined in different layers. Therefore, the PDU in each layer can be composed of one or more SDUs. And when the PDU in each layer is passed to the next lower layer, it becomes the SDU of the next lower layer.

[0272] Figure 12 and Figure 13 shows different MAC PDU structures. As Figure 12Shows a MAC PDU structure in an NR system. It can be seen that the MAC PDU can be composed of several MAC sub-PDUs. Each MAC sub-PDU can include a sub-header and a data part. Among them, the data part can be MAC CEs of different lengths or MAC SDUs. In some examples, the sub-header can be a reserved (R) field, a length (L) field, an F field, or a logical channel identification (LCID) field. The L field can represent the length of its corresponding MAC SDU or MAC CE. The F field is used to represent the size of the L field. The LCID field can represent the logical channel instance corresponding to the MAC SDU or MAC CE. And 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, and the header contains one or more sub-headers. Among them, each sub-header has a corresponding relationship with the MAC CE or MAC SDU in the data part. Optionally, the MAC PDU can be padded with padding bits at the end to ensure that the MAC PDU meets the corresponding length requirements.

[0273] It can be seen that Figure 12 the headers in can be respectively in front of their corresponding MAC CEs or MAC SDUs. And Figure 13 aggregates all the sub-header information together to form a MAC header, which is located at the very front of the data part. It can be understood that there may be some differences in the sub-headers in different communication systems.

[0274] In some examples, the TB of the MAC layer is transmitted to the physical layer, and the physical layer can add a CRC check code to the TB, for example Figure 14 as shown, that is, add TB-CRC. The physical layer can also divide the TB with CRC added into several CBs in a pre-set manner, and add a CRC check code to each CB, that is, CB-CRC. So that the receiving end can perform CRC check on each CB and obtain the correct CB.

[0275] However, currently the information related to the feature stream is unknown to the underlying layers such as the MAC layer and the physical layer. This makes it impossible for the physical layer to identify which data belongs to a feature stream, and also impossible to use the feature stream for data recovery, and thus impossible to optimize data retransmission.

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

[0277] In some embodiments, at least one piece of data sent by the sending end may correspond to at least one packet header. Among them, at least one packet header is used to indicate that the at least one piece of data sent has a fault-tolerant feature. It can be understood that this packet header can be the packet header added at any data layer in the above example.

[0278] For example, the fault-tolerant feature is used to represent the information of the above-mentioned feature stream. In other words, the fault-tolerant feature can be represented by the feature stream. Because, for the data corresponding to one feature stream, partial data errors are allowed to exist between them, and the data corresponding to the first feature stream can be recovered through a generator of related technologies. Therefore, it can be considered that there is a certain fault-tolerant ability between the data belonging to one feature stream.

[0279] In some examples, the relationship between the packet header and the data can be as Figure 15 shown, adding a packet header for each piece of data. Among them, each packet header includes a fault-tolerant feature, and this fault-tolerant feature can indicate the feature stream to which the data corresponding to this packet header belongs. Among them, Figure 15 each data part in can represent one piece of data in at least one piece of data. It can be seen that Figure 15 adds a packet header corresponding to each piece of data. For example, packet header 1 corresponds to data part 1, packet header 2 corresponds to data part 2, packet header 3 corresponds to data part 3, and so on. And for the fault-tolerant feature in each packet header, it can be considered as the fault-tolerant feature of the data part corresponding to this packet header. That is, fault-tolerant feature 1 corresponds to data part 1, fault-tolerant feature 2 corresponds to data part 2, fault-tolerant feature 3 corresponds to data part 3, etc.

[0280] For example, after the receiving end receives the data as Figure 15 shown, it can parse the fault-tolerant feature in the packet header and determine whether the data corresponding to this packet header has a fault-tolerant ability. For example, if the packet header indicates that the data corresponding to it corresponds to at least one feature stream, it can be considered that these data have a fault-tolerant ability. For example, when the receiving end receives the data as Figure 15For the data part 1 shown and the corresponding packet header 1, the receiving end can parse the error tolerance feature in the packet header 1, and this error tolerance feature can indicate the correspondence between the data part 1 and the feature stream.

[0281] For another example Figure 16 As shown, a packet header can be added for multiple data. That is Figure 16 the packet header 4 in corresponds to the data part 1, the data part 2, the data part 3, and so on. And Figure 16 the error tolerance feature 4 included in the packet header 4 in can be regarded as the error tolerance feature of the data parts such as the data part 1, the data part 2, and the data part 3.

[0282] In some examples, referring to Figure 11 the data transfer process shown, to ensure that the physical layer can identify which feature streams each data belongs to, when adding a packet header to each data layer, the error tolerance feature can be supplemented into the packet header. For the possible data segmentation in different data layers, the error tolerance feature in the packet header can be parsed and repackaged to ensure that this error tolerance feature will not be lost.

[0283] In some examples, the packet header can include a first field and a second field. Among them, the first field and the second field jointly indicate the error tolerance feature. For example, the first field can be a quantity (number, NUM) field, which is used to indicate the number of feature streams corresponding to the data corresponding to this packet header. The second field can be a position (position, POS) field, which is used to indicate the number of bits corresponding to each feature stream in the NUM field. In some examples, the number of bits of the last feature stream can be omitted. The reason is that the number of bits of a data is often unchanged during a communication process. Therefore, the number of bits of the last feature stream can be obtained through the number of bits of other feature streams and the inherent number of bits of the data.

[0284] Referring to Figure 15 , for example, the NUM field in the packet header 1 can indicate the number of feature streams corresponding to the data part 1, and the POS field in the packet header 1 can indicate the number of bits of the feature stream corresponding to the data part 1. Similarly, the packet header 2 and the packet header 3 are similar to the packet header 1, and the embodiments of the present application will not be elaborated here. Referring to Figure 16 , for example, the NUM field in the packet header 4 can indicate the number of feature streams corresponding to the data part 1, the data part 2, and the data part 3, and the POS field in the packet header 4 can indicate the number of bits of the feature streams involved in the NUM field in the packet header 4.

[0285] Referring to Figures 17 to 20, embodiments of the present application provide various schematic diagrams of data transfer from the MAC layer to the physical (PHY) layer. Among them, the data in the MAC layer can be regarded as MAC PDUs, and the data in the PHY layer can be regarded as CBs or CBGs obtained by dividing the TB, etc. For Figure 17 and Figure 18 , each piece of data in the MAC layer has an independent header, and each header includes an indication of the error tolerance characteristics of its corresponding data. For example Figure 17 and Figure 18 , in the MAC layer, the first header on the left can indicate that its corresponding MAC PDU corresponds to characteristic stream 1, the second header on the left can indicate that its corresponding MAC PDU corresponds to characteristic streams 1 and 2, and the third header on the left can indicate that its corresponding MAC PDU corresponds to characteristic streams 2 and 3, and so on. It can be seen that each pair of characteristic streams may correspond to one or more MAC PDUs. The header of each MAC PDU can then indicate which characteristic streams the MAC PDU corresponds to. For Figure 19 and Figure 20 , multiple pieces of data in the MAC layer have the same header, and this header includes an indication of the error tolerance characteristics of its corresponding multiple pieces of data. For example, the header of a unified MAC PDU can indicate which characteristic streams its corresponding multiple MAC PDUs correspond to. For Figure 17 and Figure 19 , each CB or CBG in the PHY layer can have an independent header, and each header includes an indication of the error tolerance characteristics of its corresponding CB or CBG, that is, an indication of which characteristic stream its corresponding CB or CBG corresponds to. For example Figure 17 and Figure 18 , in the PHY layer, the first header on the left can indicate which characteristic streams its corresponding CB or CBG corresponds to, the second header on the left can indicate which characteristic streams its corresponding CB or CBG corresponds to, and so on. For Figure 18 and Figure 20 , multiple CBs or CBGs in the PHY layer can have a unified header, and this header includes an indication of the error tolerance characteristics of its corresponding multiple CBs or CBGs, that is, an indication of which characteristic stream its corresponding multiple CBs or CBGs corresponds to. Of course, for the CBs or CBGs in the PHY layer, they can also be replaced by TBs, and the embodiments of the present application do not make any limitations.

[0286] It can be seen that for different data layers, the way of adding headers can be independent of each other, and the way of adding headers in each data layer does not affect the way of adding headers in other data layers.

[0287] In some more specific examples, the present application provides various data verification processes. For example, Figure 21 and Figure 22The process shown is different in that the first information sent by the receiving end is implemented with different feedback units. For example, Figure 21 as shown, the sending end sends at least one piece of data. For example, multi-process parallel sending can be adopted. For example, process 1 sends CB0, CB1 or CBG0, CBG1, and process 2 sends CB2, CB3 or CBG2, CBG3. When the sending end sends data, it can refer to the above Figures 15 to 20 described solution to add a packet header, and the packet header can include error tolerance features. The error tolerance features can indicate the feature streams corresponding to each CB or CBG. After receiving the data sent by the sending end, the receiving end can first perform CRC verification. And based on the correctness of the CRC verification, feedback ACK or NACK. For example, the CB or CBG with failed CRC verification can feedback NACK, and the CB or CBG with successful CRC verification can feedback ACK. This process can be implemented with reference to related technologies and will not be elaborated in this application. Although the sending end receives the ACK and / or NACK sent by the receiving end, it does not determine which data to retransmit based on this feedback. The receiving end can determine the confidence levels of the multiple pieces of data received. For example, for process 1, the receiving end can determine the confidence level of CB0, the confidence level of CB1, or the receiving end can determine the confidence level of CBG0, the confidence level of CB1. For process 2, the receiving end can determine the confidence level of CB2, the confidence level of CB3, or the receiving end can determine the confidence level of CBG2, the confidence level of CBG3. Assume that the receiving end determines that CB0, CB1, and CB2 belong to the same feature stream, such as feature stream 1, according to the packet header of the received data. The first information sent by the receiving end can correspond to this feature stream 1. Taking the first data as CB as an example, assume that the receiving end successfully performs CRC verification for CB1 and CB3, and fails for CB0 and CB2. The confidence level for CB1 can be 0, or it can be directly omitted. Because the sending end can know from the ACK feedback by the receiving end that this data has been successfully received by the receiving end and does not need to be retransmitted. The receiving end can adopt the above Figures 8 to 9For the described solution, the confidence levels of CB0 and CB1 are determined. For the specific implementation method, refer to the description of the corresponding embodiments above, and details are not repeated in the embodiments of this application. The receiving end can compare the confidence level of CB0 with the first threshold to determine whether to indicate retransmission of CB0. Similarly, the receiving end can compare the confidence level of CB2 with the first threshold to determine whether to indicate retransmission of CB2. Assume that the receiving end determines that CB0 needs to be retransmitted, then it can be determined that the first information corresponding to CB0 is FNACK. Assume that the receiving end determines that CB2 does not need to be retransmitted, then 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, this 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 can be FACK or omitted. The sending end can determine to retransmit CB0 in Feature Stream 1 according to the first information sent by the receiving end. Of course, CB in this example can be equivalently replaced by CBG.

[0288] Figure 22 Similar to Figure 21 except that the data sent by one process is one TB. In some examples, it can be set that each process sending in parallel sends data according to TB. Therefore, Figure 21 each process in Figure 22 can be considered to divide 1 TB into multiple CBs or CBGs for sending, while

[0289] Figure 23 is a schematic diagram of another data verification method provided by the embodiments of this application. As Figure 23 shown, this method can be applied to the Figure 1 , Figures 4 to 7 shown communication scenarios. This method can include the following steps:

[0290] S301, the sending end sends at least one piece of data to the receiving end.

[0291] S302, the receiving end determines the confidence level corresponding to the first data according to the first data.

[0292] It can be understood that S301 is similar to S101, S302 is similar to S102, and the specific implementation processes of S301 and S302 can refer to the description of the corresponding steps in Figure 8 , and details are not repeated in the embodiments of this application.

[0293] S303, the receiving end sends the confidence level to the sending end.

[0294] In some embodiments, the receiving end can directly feedback the confidence level corresponding to the first data determined in S302 to the sending end.

[0295] In some embodiments, considering the direct feedback confidence, for the case where the confidence data is large, it may occupy more bits, resulting in a large amount of resource consumption. Therefore, multiple interval values can be set for the confidence, and each interval value corresponds to a certain range of confidence values.

[0296] For example, Table 1 shows a possible correspondence between interval values and confidence.

[0297] Interval value 00 01 10 11 Confidence interval 0 (0，10] (10，20] (20，+∞)

[0298] Table 1

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

[0300] For the case where the confidence of the first data is determined according to the LLR of the CB with CRC failure, the interval value corresponding to the confidence can be determined in the manner of Table 1. For the case where the confidence of the first data is determined according to the number of the first bits of the CB with CRC failure, the interval value corresponding to the confidence can be determined in the manner of Table 2.

[0301] Interval value 00 01 10 11 Confidence interval [0，10) [10，20) [20，30) [30，+∞)

[0302] Table 2

[0303] For the case where the confidence of the first data is determined according to the ratio of the number of the first bits corresponding to the CB with CRC failure to the total code length of the first data, the interval value corresponding to the confidence can be determined in the manner of Table 3.

[0304] Interval value 00 01 10 11 Confidence interval [0，10％) [10％，20％) [20％，30％) [30％，+∞)

[0305] Table 3

[0306] It should be understood that the above Table 1, Table 2 and Table 3 only show 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 the actual situation.

[0307] In some embodiments, the receiving end can send the corresponding interval value to the sending end. The sending end can determine the confidence interval corresponding to the first data according to the interval value corresponding to the first data. The sending end can 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 of the first data to the sending end, the sending end can directly determine whether to retransmit the first data according to the confidence corresponding to the first data.

[0308] In some examples, the sender may determine whether to retransmit the first data according to the confidence level corresponding to the first data and the first threshold. The implementation process may refer to the description of the foregoing embodiment in which the receiver determines whether to retransmit the first data according to the confidence level corresponding to the first data and the first threshold, and the embodiments of the present application will not be described herein again. Among them, the determination method of the first threshold may also refer to the determination method of the first threshold in the foregoing embodiment, and the embodiments of the present application will not be described herein again.

[0309] In some examples, considering that whether to retransmit the first data is determined by the sender. Then, when the first threshold is determined by the receiver, the receiver may also send the first threshold to the sender. For example, the receiver sends the fourth information, and the sender receives the fourth information. Among them, the fourth information includes the first threshold.

[0310] S304. The sender sends the first information to the receiver.

[0311] In some embodiments, the sender may determine whether to retransmit the first data according to the confidence level of the first data received in S303. The sender may obtain the first information according to whether multiple first data are retransmitted. The first information may indicate whether to retransmit at least one data sent in S301. It can be understood that the purpose of the sender sending the first information is to let the receiver know which data the sender retransmits.

[0312] For the implementation process of S304, reference may be made to S204, the difference being that the device sending the first information is changed from the receiver to the sender. The embodiments of the present application will not be described herein again.

[0313] In some examples, if the confidence level of the first data is less than the first threshold, the first information may indicate retransmission of 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 non-retransmission of the first data.

[0314] In the embodiments of the present application, the receiver may send the confidence level to the sender so that the sender determines the first information according to the confidence level and the first threshold, and the first information may indicate retransmission of the first data whose confidence level does not meet the corresponding conditions. For the first data whose confidence level meets the corresponding conditions, there is no need to retransmit, which can reduce the resource consumption caused by retransmission and reduce the delay caused by retransmission.

[0315] In some more specific examples, the present application provides multiple data verification processes. For example, Figure 24 and Figure 25 The processes shown are different in that the receiver sends the confidence level in different feedback units. Figure 24 and Figure 21Similarly, the difference is that the confidence level corresponding to Feature Stream 1 is sent by the receiving end. The sending end can determine the first information corresponding to the feature stream according to the confidence level 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 will retransmit. And Figure 25 is Figure 24 similar, the difference being that the data sent by one process is one TB.

[0316] In a data verification method provided in an embodiment of the present application, it may further include: the sending end sends second information to the receiving end, or the receiving end sends second information to the sending end. The second information is used to indicate the method of indicating whether to retransmit the first data according to the confidence level.

[0317] In some embodiments, for the above Figures 8 to 25 described solution, it may further include that the sending end or the receiving end sends second information to indicate that the communication between the sending end and the receiving end adopts the method of indicating whether to retransmit the first data according to the confidence level. Among them, the method of indicating whether to retransmit the first data according to the confidence level may also be referred to as a fault-tolerant transmission service, a fault-tolerant service, etc. The present application does not limit the name.

[0318] It can be understood that if the second information indicates the method of indicating whether to retransmit the first data according to the confidence level, it means that the sending end no longer determines whether to retransmit the first data according to the ACK and / or NACK obtained by the receiving end based on CRC verification. The sending end will determine whether to retransmit the first data according to the FACK and / or FNACK fed back by the receiving end, or according to the confidence level or confidence interval fed back by the receiving end.

[0319] 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 send the second information to the network device. For another example, the second information can be carried by sidelink control information (SCI) to send the second information to other terminals.

[0320] In some examples, if the device sending the second information is a network device, the second information can be carried by DCI to send the second information to the terminal.

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

[0322] The embodiments of the present application can indicate whether the peer device has adopted the fault-tolerant transmission service through the second piece of information, so as to reduce the resource consumption caused by retransmission and the delay caused by retransmission when this service is enabled.

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

[0324] In some embodiments, the present application provides a relatively specific data verification process. Refer to Figure 26 As shown, in S401, the receiving end first determines whether to enable the fault-tolerant transmission service. For example, information indicating whether to enable the fault-tolerant transmission service is pre-configured in the receiving end, 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 CRC verification on the received data. For the case where all CRC verifications are correct, S404 can be directly executed, that is, the correctly received data is passed to the upper layer. If there is data with a failed CRC verification, the confidence level of each piece of data with a failed CRC verification can be determined according to the LLR in S403. The receiving end can determine whether to retransmit the corresponding data in S405 according to the confidence level determined in S403 and the first threshold, and obtain the first piece of information. The receiving end can send this first piece of information to the sending end to indicate which data needs to be retransmitted.

[0325] As Figure 27 shown, compared with Figure 26Similar to the solution shown, the difference is that whether to retransmit the data is determined by the sender. In S501, the receiver first determines whether to enable the fault-tolerant transmission service. In S502, the receiver performs CRC check on the received data. For the cases where the CRC checks are all correct, S504 can be directly executed to pass the correctly received data to the upper layer. For the data with failed CRC checks, in S503, the confidence level of each data with a failed CRC check can be determined according to the LLR. In S505, the receiver can send the confidence level of at least one first data to the sender. Herein, the first data is any one of at least one data received by the receiver. The sender can determine whether to retransmit the corresponding data according to the confidence level of at least one first data and the first threshold. The sender can perform the retransmission of the corresponding data. Or if the sender decides not to perform the retransmission, the receiver can pass the received data to the upper layer.

[0326] In some examples, the sender can send the first information indicating which data needs to be retransmitted. In other examples, if the sender does not send the first information and the receiver does not receive any retransmitted data, it can be considered that the sender determines not to retransmit. For example, the receiver does not receive the first information within the preset time and does not receive any retransmitted data. If the receiver determines that the sender has not performed data retransmission, S504 can be executed to pass the received data to the upper layer.

[0327] In some possible implementation manners, the receiver may send the confidence level to the sender, or may send the first information. Then the sender may receive at least one of the confidence level and the first information. For example, the sender receives the confidence level, or for another example, the sender receives the first information, or for yet another example, the sender receives the confidence level and the first information. It can be understood that when the sender receives the confidence level and the first information, the sender can determine which data needs to be retransmitted according to the confidence level, and combine the data indicated to be retransmitted in the first information to determine the finally required retransmitted data.

[0328] It should be noted that the above-mentioned multiple embodiments can be combined and the combined solution can be implemented. Optionally, some operations in the processes of the method embodiments are optionally combined, and / or the order of some operations is optionally changed. And, 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 executed. Those of ordinary skill in the art will think of various ways to reorder the operations herein. In addition, it should be pointed out that the process details involved in a certain embodiment herein are also applicable to other embodiments in a similar manner, or different embodiments can be combined and used.

[0329] It can be understood that, in order to implement the functions in the above embodiments, the base station and the terminal include corresponding hardware structures and / or software modules for performing each function. Those skilled in the art should easily realize that, in combination with the units and method steps of the examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application scenarios and design constraints of the technical solution.

[0330] Figure 28 and Figure 29 FIG. is a schematic structural diagram of a possible data verification device provided by an embodiment of this application. These data verification devices can be used to implement the functions of the terminal or the network device in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of this application, the data verification device can be a terminal, or a network device, or a module applied to the terminal or the network device. For example, a chip.

[0331] As Figure 28 shown, 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 sending end or the receiving end in the above Figure 8 , Figure 9 , Figures 21 to 27 shown method embodiments.

[0332] When the data verification device 2800 is used to implement the function of the receiving end in the Figure 8 shown method embodiment: The transceiver unit 2820 is used to receive at least one piece of data. The processing unit 2810 is used to determine the confidence level corresponding to the first data according to the first data. The processing unit 2810 is further used to execute all operations other than the transceiver operations performed by the data verification device in the Figure 8 shown embodiment, and / or other processes for supporting the technologies described herein.

[0333] When the data verification device 2800 is used to implement the function of the sending end in the Figure 8 shown method embodiment: The transceiver unit 2820 is used to send at least one piece of data. The processing unit 2810 is further used to execute all operations other than the transceiver operations performed by the data verification device in the Figure 8 shown embodiment, and / or other processes for supporting the technologies described herein.

[0334] For a more detailed description of the above processing unit 2810 and transceiver unit 2820, reference can be made to Figure 8 , Figure 9 , Figures 21 to 27The relevant descriptions in the method embodiments shown above. The above processing unit 2810 and transceiver unit 2820 can also perform other steps. For specific implementations, reference can be made to the method embodiments, which will not be elaborated here.

[0335] Optionally, the transceiver unit 2820 can be a transceiver, and the transceiver can include an antenna, a radio frequency circuit, etc.

[0336] The processing unit 2810 can be a processor (or, processing circuit), such as a baseband processor, and one or more CPUs can be included in the baseband processor.

[0337] As Figure 29 shown, the data verification device 2900 includes a processor 2910 and an interface circuit 2920. The processor 2910 and the interface circuit 2920 are coupled to each other. It can be understood that the interface circuit 2920 can be a transceiver or an input / output interface. Optionally, the data verification device 2900 can further include a memory 2930, which is used to store the instructions executed by the processor 910 or store the input data required for the processor 2910 to run the instructions or store the data generated after the processor 2910 runs the instructions.

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

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

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

[0341] Figure 28 orFigure 29 The communication device shown is merely an example, and in practical applications, the communication device may have more or fewer components than Figure 28 or Figure 29 those shown in

[0342] In the embodiments of this application, when entity A sends information to entity B, it can be that A directly sends to B, or A indirectly sends to B through other entities. Similarly, when entity B receives information from entity A, it can be that entity B directly receives the information sent by entity A, or entity B indirectly receives the information sent by entity A through other entities. Here, entity A and B can be RAN nodes or terminals, or modules inside RAN nodes or terminals. The sending and receiving of information can be information interaction between a RAN node and a terminal, for example, information interaction between a network device and a terminal; the sending and receiving of information can also be information interaction between two RAN nodes, for example, information interaction between a CU and a DU; the sending and receiving of information can further be information interaction between different modules within a device, for example, information interaction between a terminal chip and other modules of the terminal, or information interaction between a network device chip and other modules in the network device.

[0343] In the embodiments of this application, the network device sends a downlink signal or downlink information to the terminal device, and the downlink information is carried on a downlink channel; the terminal device sends an uplink signal or uplink information to the network device, and the uplink information is carried on an uplink channel. In order 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 that has established a wireless connection with the terminal device is called the serving cell of the terminal device.

[0344] It can be understood that in the embodiments of this application, PDSCH and PUSCH are only taken as examples of a downlink data channel and an uplink data channel. In different systems and different scenarios, the data channel and the control channel may have different names, and the embodiments of this application do not limit this.

[0345] It can be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), 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.

[0346] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions executable by a processor. The software instructions may be composed of corresponding software modules, and the software modules may be stored in a 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, removable 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 may also be a component of the processor. The processor and the storage medium may be located in an ASIC. Additionally, the ASIC may be located in a network device or a terminal. The processor and the storage medium may also exist as discrete components in the network device or the terminal.

[0347] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in the form of a computer program product in whole or in part. 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 executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a digital video disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile types of storage media.

[0348] In each of the embodiments of the embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be cross-referenced. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0349] It can be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and do not limit the scope of the embodiments of the present application. The magnitude of the sequence numbers of the above processes does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic.

Claims

1. A data verification method, characterized in that, it includes: receiving at least one data, where the at least one data includes first data; determining a confidence level corresponding to the first data according to the first data, where the confidence level is used to indicate the reception situation of the first data.

2. The method according to claim 1, characterized in that, the confidence level is determined according to the 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 the 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 with cyclic redundancy check CRC failure in the first data; the confidence level is determined according to the number of first bits in the first data, where the first bit is a bit in the CB with CRC failure in the first data, and the number of the first bits is determined according to the LLR corresponding to the CB with CRC failure in the first data; the confidence level is determined according to the ratio of the number of first bits corresponding to the CB with CRC failure 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 with CRC failure, including: the number of the first bits is determined according to the LLR corresponding to the CB with CRC failure and a LLR reference value.

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

6. The method according to any one of claims 1-4, characterized in that, the method further includes: sending the confidence level; receiving a first message, where the first message is used to indicate whether to retransmit the at least one data, and the first message 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 message is used to indicate whether to retransmit the at least one data, including: when the confidence level is less than a first threshold, the first message is used to indicate retransmitting the first data.

8. The method according to any one of claims 1-7, characterized in that, the method further includes: sending a second message, where the second message is used to indicate the method of indicating whether to retransmit the first data according to the confidence level; or, receiving the second message.

9. The method according to any one of claims 1-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 a fault tolerance feature.

10. A data verification method, characterized in that, it includes: sending at least one data, where the at least one data includes first data; Receive at least one of a reception confidence level and first information, where the confidence level is used to indicate the reception condition 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, wherein, the confidence level is determined according to the log-likelihood ratio (LLR) corresponding to the first data.

12. The method according to claim 11, wherein, the confidence level is determined according to the log-likelihood ratio (LLR) corresponding to the first data, including at least one of the following manners: the confidence level is determined according to the LLR corresponding to a code block (CB) with a cyclic redundancy check (CRC) failure in the first data; the confidence level is determined according to the number of first bits in the first data, where the first bits are the bits in the CB with a CRC failure in the first data, and the number of the first bits is determined according to the LLR corresponding to the CB with a CRC failure in the first data; the confidence level is determined according to the ratio of the number of first bits corresponding to the CB with a CRC failure in the first data to the total code length of the first data.

13. The method according to claim 12, wherein, the number of the first bits is determined according to the LLR corresponding to the CB with a CRC failure, including: the number of the first bits is determined according to the LLR corresponding to the CB with a CRC failure and a reference LLR value.

14. The method according to any one of claims 10-13, wherein, receiving at least one of the reception confidence level and first information includes: receiving the first information, where the first information is determined according to the confidence level and a first threshold.

15. The method according to any one of claims 10-13, wherein, receiving at least one of the reception confidence level and first information includes: receiving the confidence level; determining the first information according to the confidence level and a first threshold; transmitting the first information.

16. The method according to claim 14 or 15, wherein, the first information is used to indicate whether to retransmit the at least one data, including: when the confidence level is less than the first threshold, the first information is used to indicate retransmitting the first data.

17. The method according to any one of claims 10-16, wherein, the method further includes: transmitting second information, where the second information is used to indicate a manner of indicating whether to retransmit the first data according to the confidence level; or, receiving the second information.

18. The method according to any one of claims 10-17, wherein, 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 a fault tolerance feature.

19. A data verification device, wherein, including: a processing module and a communication module; the communication module is used to receive and / or transmit 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, wherein, including: A processing module and a communication module; The communication module is configured to receive and / or transmit signals, and the processing module is configured to enable the execution of the method according to any one of claims 10 to 18.

21. A data verification device, Characterized in that, Comprising: At least one processor and a communication interface, the communication interface is configured to receive and / or transmit signals, and the processor is configured to enable the execution of the method according to any one of claims 1 to 9.

22. A data verification device, Characterized in that, Comprising: At least one processor and a communication interface, the communication interface is configured to receive and / or transmit signals, and the processor is configured to enable the execution of the method according to any one of claims 10 to 18.

23. A communication system, Characterized in that, The system includes: a first device that executes the method according to any one of claims 1 to 9, and a second device that executes 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 run on a communication device, the communication device is caused to execute the method according to any one of claims 1-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 run on a communication device, the communication device is caused to execute the method according to any one of claims 10-18.

26. A computer program product, Characterized in that, The computer program product includes a computer program or instructions, and when the computer program or instructions run on a computer, the computer is caused to execute the method according to any one of claims 1-9.

27. A computer program product, Characterized in that, The computer program product includes a computer program or instructions, and when the computer program or instructions run on a computer, the computer is caused to execute the method according to any one of claims 10-18.

Images