Communication method and device

Abstract

The invention provides a communication method and device, and relates to the technical field of communication. The method comprises the steps that a first transmission block is received, the first transmission block comprises a first check code and a second check code, the first check code is used for error detection of first information, and the second check code is used for error detection of second information; and determining that the first check code has a check error, or the second check code has a check error and the error rate of the second information is greater than or equal to a first threshold, and generating a negative acknowledgement (NACK). According to the scheme, whether the NACK is generated or not is judged according to different importance of the information in the transmission block, unnecessary retransmission of the transmission block is reduced, and the transmission efficiency of the system is improved.

Description

Technical Field

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

[0002] In communication systems, Cyclic Redundancy Check (CRC) is a commonly used error detection technique for data transmission. At the sending end, a checksum is calculated using a specific algorithm, and this checksum is appended to the data before being sent to the receiving end. The receiving end verifies the received data and checksum using the same algorithm to determine if the received data is correct and complete, thus protecting the reliability of data transmission. Current CRC implementations require completely correct transmission; that is, if the CRC check fails, the sending end needs to retransmit the data. This current implementation negatively impacts system transmission efficiency, for example, by increasing data packet transmission latency.

[0003] Therefore, how to improve system transmission efficiency while ensuring a certain level of transmission reliability is an urgent technical problem to be solved. Summary of the Invention

[0004] To address the aforementioned technical problems, this application provides a communication method and apparatus that can improve the transmission efficiency of the system.

[0005] Firstly, a communication method is provided. The execution entity of the method provided in the first aspect can be a first device. Unless otherwise specified, the first device in this application can refer to the first device itself (e.g., a network device or a terminal device), a module within the first device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or part of the functions of the first device. For ease of description, the following description uses a first device as an example.

[0006] The method includes: receiving a first transport block TB, the first TB including a first check code and a second check code, the first check code being used for error detection of first information, the second check code being used for error detection of second information, the first information and the second information being different; determining that the first check code is incorrect, or determining that the second check code is incorrect and the error rate of the second information is greater than or equal to a first threshold, and generating a negative response (NACK).

[0007] The above scheme performs error detection on the first and second information respectively. In the case of errors in the second information verification, the error rate of the second information is additionally considered to determine whether to generate a negative response. In this way, different thresholds can be set according to information of different importance, so as to ensure the accuracy of important fields while reducing unnecessary retransmission of unimportant fields, thereby reducing data transmission latency and increasing data transmission throughput, thus improving transmission efficiency.

[0008] Optionally, the first TB may also include first information and second information. For example, the first information and the second information may be different bit sequences in the first TB.

[0009] Optionally, determining that the first checksum is incorrect, or determining that the second checksum is incorrect and the error rate of the second information is greater than or equal to the first threshold, and generating a NACK, can also be expressed as one or more of the following: If the first checksum is correct and the second checksum is correct, generate a positive ACK; if the first checksum is correct, and the second checksum is incorrect and the error rate of the second information is less than the first threshold, generate an ACK; if the first checksum is correct, and the second checksum is incorrect and the error rate of the second information is greater than or equal to the first threshold, generate a NACK; if the first checksum is incorrect and the second checksum is correct, generate a NACK; if the first checksum is incorrect, and the second checksum is incorrect and the error rate of the second information is less than the first threshold, generate a NACK; if the first checksum is incorrect, and the second checksum is incorrect and the error rate of the second information is greater than or equal to the first threshold, generate a NACK.

[0010] In another formulation, the determination that the first checksum is faulty, or that the second checksum is faulty and the error rate of the second information is greater than or equal to the first threshold, and the generation of a NACK, can also be expressed as a single overall judgment condition: A NACK is generated based on a first condition. The first condition is either a first checksum error or a second checksum error and the error rate of the second information is greater than or equal to the first threshold. Here, the first checksum error is the first sub-condition, and the second checksum error and the error rate of the second information being greater than or equal to the first threshold is the second sub-condition. If at least one of the first and second sub-conditions is satisfied, the second device determines that a NACK is generated.

[0011] Optionally, before generating an ACK or NACK, the process further includes: determining a first parameter, which is used to determine a first threshold. The first threshold is the fault tolerance rate corresponding to the second information, and this fault tolerance rate can be obtained based on the importance of the second information.

[0012] In some implementations, before generating an ACK or NACK, the process further includes determining a first threshold, which is the fault tolerance rate corresponding to the second information. For example, the first threshold can be less than or equal to 1, such as 1%, 5%, or 10%.

[0013] Optionally, the first parameter can be predefined, configured, or preconfigured.

[0014] Optionally, the first parameter is used to indicate the importance or fault tolerance of the first information.

[0015] Optionally, the importance of the first piece of information may differ from that of the second piece of information, or the fault tolerance rates of the first and second pieces of information may differ. Fault tolerance can be understood as the tolerance for errors, i.e., at the receiving end, the threshold percentage of erroneous bits out of all bits, or the threshold percentage of erroneous bits out of all bits, or the upper limit of the tolerable percentage of erroneous bits out of all bits; importance can be understood as the degree of significance of the information. The fault tolerance rate or importance can be indicated by the upper layer or predefined.

[0016] Optionally, the first checksum is determined based on the first information, and the second checksum is determined based on the second information. In one possible implementation, the first information and the second information correspond to different checksum calculation methods.

[0017] The above scheme utilizes different checksum calculation methods to achieve varying error detection capabilities. For highly important information, checksums with higher bit overhead but stronger error detection capabilities can be used, while for less important information, checksums with lower bit overhead but weaker error detection capabilities can be used. This approach ensures the reliability of important information transmission, reduces the overhead of less important information, and improves transmission efficiency.

[0018] Optionally, the error rate of the second information is determined based on the verification result of the second check code and / or the quality of the channel through which the second information is transmitted.

[0019] Optionally, the first information includes some or all fields from the Service Data Adaptation Protocol (SDAP) header, Packet Data Convergence Protocol (PDCP) header, Radio Link Control (RLC) header, Media Access Control (MAC) header, Internet Protocol (IP) header, and / or Transmission Control Protocol (TCP) header; or, the first information is carried on the Signaling Radio Bearer (SRB), and the second information is carried on the Data Radio Bearer (DRB). Wherein, the first information is more important than the second information, or the fault tolerance of the first information is lower than that of the second information. For example, the first information may include header information from each layer. For example, the first information may include some or all of the headers from the SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, and User Datagram Protocol (UDP) header; or, the first information may include some fields from all of the headers from the SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, and UDP header; or, the first information may include some fields from the SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, or UDP header. In yet another example, the first information may include at least one of the Media Access Control (MAC) Control Element (CE), the RLC Control Protocol Data Unit (PDU), or the PDCP Control PDU. Exemplarily, the second information may include either a data portion or a payload portion. For example, the second information may include some or all of the MAC CE payload, the MAC Service Data Unit (SDU) payload, and the RLC SDU payload.

[0020] By including the headers of each protocol layer, or the data plane control information within the MAC CE and control PDU in the first information, and including the data portion or payload portion in the second information, the correctness of the transmission of important information can be guaranteed, and a certain fault tolerance rate can be set for data of relatively low importance, thereby improving transmission efficiency.

[0021] Optionally, the first information is carried on the first radio bearer (RB), and the second information is carried on the second RB; or, the logical channel (LCH) where the first information is located is the first LCH, and the LCH where the second information is located is the second LCH.

[0022] By carrying information of different importance or fault tolerance rates on different RBs or LCHs, different check codes can be used at the physical layer for the information on different RBs or LCHs, thus achieving different verification processing for information of different importance or fault tolerance rates.

[0023] Secondly, a communication method is provided. The method provided in this application can be executed by a second device. Unless otherwise specified, the second device in this application can refer to the second device itself (e.g., a network device or a terminal device), a module within the second device (e.g., a processor, a chip, or a chip system), or a logic module or software capable of implementing all or part of the functions of the second device. For ease of description, the following description uses a second device as an example.

[0024] The method includes: determining a first TB, the first TB including a first check code and a second check code, the first check code being used for error detection of first information, and the second check code being used for error detection of second information; wherein the importance of the first information is different from the importance of the second information, or the fault tolerance rate of the first information is different from the fault tolerance rate of the second information; and sending a first transport block.

[0025] Optionally, before determining the first TB, the method further includes: determining a first checksum based on the first information, and determining a second checksum based on the second information. In one possible implementation, the first information and the second information correspond to different checksum calculation methods.

[0026] By using check codes with higher bit overhead but stronger error detection capabilities for information of high importance, and using check codes with lower bit overhead but weaker error detection capabilities for information of low importance, the reliability of the transmission of important information can be guaranteed, the overhead of low-importance information can be reduced, and the transmission efficiency can be improved.

[0027] Optionally, before generating an ACK or NACK, the process further includes: determining a first parameter, which is used to determine a first threshold. The first threshold is the fault tolerance rate corresponding to the second information, and this fault tolerance rate can be obtained based on the importance of the second information.

[0028] In some implementations, before generating an ACK or NACK, the process further includes determining a first threshold, which is the fault tolerance rate corresponding to the second information. For example, the first threshold can be less than or equal to 1, such as 1%, 5%, or 10%.

[0029] Optionally, the first parameter can be predefined, configured, or preconfigured.

[0030] Optionally, the first parameter is used to indicate the importance or fault tolerance of the first information.

[0031] Optionally, the first information includes some or all fields from the Service Data Adaptation Protocol (SDAP) header, Packet Data Convergence Protocol (PDCP) header, Radio Link Control (RLC) header, Media Access Control (MAC) header, Internet Protocol (IP) header, and / or Transmission Control Protocol (TCP) header; or, the first information is carried on the Signaling Radio Bearer (SRB), and the second information is carried on the Data Radio Bearer (DRB). Wherein, the first information is more important than the second information, or the fault tolerance of the first information is lower than that of the second information. For example, the first information may include header information from each layer. For example, the first information may include some or all of the following headers: SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, and UDP header; or, the first information may include some fields from all of the following headers: SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, and UDP header; or, the first information may include some fields from any of the following headers: SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, or UDP header. In yet another example, the first information may include at least one of MAC CE, RLC control PDU, or PDCP control PDU. Exemplarily, the second information may include either a data portion or a payload portion. For example, the second information may include some or all of the following: MAC CE payload, MAC SDU payload, or RLC SDU payload.

[0032] Optionally, the first information is carried on the first radio bearer (RB), and the second information is carried on the second RB; or, the logical channel (LCH) where the first information is located is the first LCH, and the LCH where the second information is located is the second LCH.

[0033] Optionally, if a NACK is received, the first transport block is retransmitted.

[0034] Using the above method, if a transmission error occurs in a relatively important field, or if a transmission error occurs in a less important data segment with a high error rate, the first device can retransmit the first TB to the second device upon receiving a NACK, thereby ensuring the reliability of the first TB transmission.

[0035] Thirdly, a communication device is provided. The communication device includes a processor configured to perform the first aspect and any possible method thereof, or the processor configured to perform the second aspect and any possible method thereof.

[0036] In some implementations, the communication device described in the third aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the third aspect and other communication devices.

[0037] In one possible implementation, the communication device described in the third aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data involved in the method of the first aspect or any embodiment thereof, or computer programs and / or data involved in the method of the second aspect or any embodiment thereof.

[0038] Furthermore, the technical effects of the communication device described in the third aspect can be referenced to the technical effects of the first aspect or any embodiment thereof, or the technical effects of the second aspect or any embodiment thereof, which will not be repeated here.

[0039] Fourthly, a communication device is provided. The communication device includes: a processor coupled to a memory, the processor being configured to execute a computer program or instructions stored in the memory, such that the communication device performs the method of the first aspect or any embodiment thereof, or performs the method of the second aspect or any embodiment thereof.

[0040] In one possible implementation, the communication device may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device and other communication devices.

[0041] In one possible implementation, the communication device further includes the memory for storing the aforementioned computer program or instructions. Optionally, the memory and processor are integrated together.

[0042] Furthermore, the technical effects of the communication device described in the fourth aspect can be referred to the technical effects of the first aspect or any embodiment thereof, or the technical effects of the second aspect or any embodiment thereof, which will not be repeated here.

[0043] Fifthly, a chip is provided, including a processor for calling a computer program or computer instructions in memory to cause the processor to execute any of the implementations of the first aspect above, or to cause the processor to execute any of the implementations of the second aspect above.

[0044] In some implementations, the processor is coupled to the memory via an interface.

[0045] A sixth aspect provides a communication system. The communication system includes: a first means for performing the method described in the first aspect or any embodiment thereof, or a second means for performing the method described in the second aspect or any embodiment thereof.

[0046] A seventh aspect provides a computer-readable storage medium comprising: a computer program or instructions; wherein, when the computer program or instructions are executed, the method as described in the first aspect or any embodiment thereof is implemented, or the method as described in the second aspect or any embodiment thereof is implemented.

[0047] Eighthly, a computer program product is provided, comprising a computer program or instructions that, when executed, cause the method as described in the first aspect or any embodiment thereof to be implemented, or cause the method as described in the second aspect or any embodiment thereof to be implemented. Attached Figure Description

[0048] Figure 1 This is a schematic diagram of a communication system.

[0049] Figure 2 This is a schematic diagram of the basic process of physical layer data transmission.

[0050] Figure 3 This is a schematic diagram illustrating the specific transformation process of data flow from TB to CB to CW.

[0051] Figure 4 This is a schematic diagram of a TB structure.

[0052] Figure 5 This is a schematic diagram of a HARQ data transmission process.

[0053] Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application.

[0054] Figure 7 This is a schematic diagram of a TB structure according to an embodiment of this application.

[0055] Figure 8 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0056] Figure 9 This is a schematic block diagram of another communication device according to an embodiment of this application. Detailed Implementation

[0057] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0058] To facilitate understanding of the embodiments of this application, the following points will be explained before introducing this application.

[0059] 1. In this application, the term "system" may be used interchangeably with "network". This application will present various aspects, embodiments, or features in relation to a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches may also be used.

[0060] In this application, the words "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

[0061] In this application, for ease of description, numbering can start from 1 consecutively, start from 0 consecutively, or start from any parameter. It should be understood that the above settings are for ease of describing the technical solutions provided in the embodiments of this application, and are not intended to limit the scope of the embodiments of this application.

[0062] 2. In the embodiments of this application, "instruction" can include direct instruction and indirect instruction, as well as explicit instruction and implicit instruction. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a correlation between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement order of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, the common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0063] Furthermore, the specific instruction method can also be any existing instruction method, such as, but not limited to, the above-mentioned instruction methods and their various combinations. As can be seen from the above, for example, when multiple pieces of information of the same type need to be indicated, the instruction methods for different pieces of information may differ. In the specific implementation process, the required instruction method can be selected according to specific needs. This application embodiment does not limit the selected instruction method. Therefore, the instruction methods involved in this application embodiment should be understood to cover various methods that enable the party to be instructed to obtain the information to be indicated.

[0064] 3. "Predefined," "pre-defined," "pre-configured," or "pre-configured" can be understood as standard-defined, which can be implemented by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices). This application embodiment does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. One or more memories can be separate settings or integrated into the encoder or decoder, processor, or communication device. One or more memories can also be partially separate settings and partially integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application embodiment does not limit this. "Configuration" refers to network device configuration, which can be changed through system information block (SIB) or radio resource control (RRC) signaling. "Pre-configured" can be understood as information pre-recorded / written in the user equipment (UE) hardware and / or software, determined by the equipment manufacturer, and can be changed through software or hardware.

[0065] 4. The “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols applied to future communication systems. The embodiments of this application do not limit this.

[0066] 5. In the embodiments of this application, the descriptions such as "when," "under the circumstances," "if," and "if" all refer to the fact that the device (e.g., the terminal device) will make corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device (e.g., the terminal device) to have a judgment action when implementing it, nor do they mean that there are other limitations.

[0067] 6. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. The "and / or" in the embodiments of this application is merely a description of the relationship between the related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

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

[0069] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0070] The technical solutions of this application can be applied to various communication systems, including but not limited to: LTE systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, NR systems and other fifth-generation (5G) mobile communication systems, narrowband Internet of Things (NB-IoT) systems, enhanced machine-type communication (eMTC) systems, enhanced mobile broadband (eMBB) systems, ultra-reliable low latency communications (URLLC) systems, satellite communication systems, LTE-machine-to-machine (LTE-M) systems, or future communication networks, etc.

[0071] In the embodiments of this application, the term "communication" can also be described as "data transmission," "signal transmission," "information transmission," or simply "transmission." In the embodiments of this application, transmission can include sending or receiving. Exemplarily, transmission can be uplink transmission, such as a terminal device sending a signal to a network device; transmission can also be downlink transmission, such as a network device sending a signal to a terminal device; transmission can also be sidelink transmission, such as a terminal device sending a signal to another terminal device. Exemplarily, "transmission" can be air interface-level transmission, or it can refer to signal transmission at a chip input (I) / output (O) interface, rather than air interface-level transmission.

[0072] Figure 1 This is a schematic diagram of a communication system 100. (For example...) Figure 1 As shown, the communication system 100 includes a wireless access network 110 and a core network 120. Optionally, the communication system 100 may also include an Internet 130. The wireless access network 110 may include at least one network device (such as...). Figure 1 111a and 111b in the above), may also include at least one terminal device (such as Figure 1(112a-112j in the original text). Terminal devices connect to network devices wirelessly. Network devices connect to core network 120 wirelessly or via wired connection. Core network 120 may include one or more core network devices. These core network devices and network devices can be independent physical devices, or they can integrate the functions of core network devices and the logical functions of network devices onto the same physical device, or a single physical device can integrate some core network device functions and some network device functions. Terminal devices and network devices can be interconnected via wired or wireless means. Terminal devices can communicate wirelessly with each other, network devices with each other, and terminal devices with each other via air interface resources. For example, air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. It should be noted that... Figure 1 This is just an illustration; the communication system 100 may also include other network devices, such as wireless repeaters and wireless backhaul devices. Figure 1 It is not shown in the middle.

[0073] Network devices can be any device with wireless transceiver capabilities. For example, a network device can be a base station used to connect terminal devices to a radio access network (RAN). Network devices are sometimes also referred to as access network devices or access network nodes. It is understood that the names of devices with network device functions may differ in systems employing different wireless access technologies. For ease of description, the embodiments of this application collectively refer to devices providing wireless communication access functions to terminal devices as base stations. In the embodiments of this application, network devices include, but are not limited to: various forms of macro base stations (such as...). Figure 1 111a), micro base stations or indoor stations (such as Figure 1Network equipment can include 111b), pico base stations, small cells, balloon stations, relay stations, access points, etc., in LTE. It can also include evolved node B (eNB or eNodeB) in LTE, access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TPs), or transmission reception points (TRPs) in Wi-Fi systems. Furthermore, it can include next-generation NodeBs (gNBs) or transmission points (TRPs or TPs) in 5G systems, one or a group of antenna panels (including multiple antenna panels) of a 5G base station, network nodes constituting a gNB or transmission point, such as baseband units (BBUs) or distributed units (DUs), and network equipment, servers, or vehicle-mounted equipment in future communication networks. Network equipment can also be modules or units that perform some of the functions of a base station; for example, it can be a central unit (CU) or a DU.

[0074] For example, in a Universal Mobile Telecommunications System (UMTS) or LTE wireless communication system, the network device can be a macro base station (eNB); in a heterogeneous network (HetNet) scenario, the network device can be a micro base station (eNB); in a distributed base station scenario, the network device can include a base station unit (BBU) and a remote radio unit (RRU); in a cloud radio access network (CRAN) scenario, the network device can be a BBU pool and an RRU; and in future wireless communication systems, the network device can be a gNB.

[0075] In this embodiment, the means for implementing the function of the network device can be the network device itself, or it can be a means that enables the network device to implement the function, such as a chip system, which can be installed in the network device. The chip system can be composed of chips, or it can include chips and other discrete components.

[0076] In another possible scenario, multiple network devices collaborate to assist the terminal in achieving wireless access, with each network device performing a portion of the base station's functions. For example, network devices could be CUs, DUs, CUs (control plane, CP), CUs (user plane, UP), or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as RRUs, active antenna units (AAUs), or remote radio heads (RRHs).

[0077] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules. The embodiments of this application do not limit the specific technology or specific device form used in the network device.

[0078] Terminal equipment can be a device that provides voice and / or data connectivity to users; it can also be a device with wireless connectivity. Terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (such as on airplanes, balloons, and satellites). Terminal equipment can also be referred to as UE, access terminal, terminal, subscriber unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user equipment. In this application embodiment, terminal devices include, but are not limited to: cellular phones, mobile phones, wireless data cards, wireless modems, tablets, laptop computers, notebook computers, handheld computers, mobile internet devices (MIDs), computers with wireless transceiver capabilities, cordless phones, session initiation protocol (SIP) phones, smartphones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handsets with wireless communication capabilities, computing devices or other devices connected to wireless modems, in-vehicle devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), wearable devices (e.g., smartwatches, smart bracelets, pedometers, smart glasses, etc.), satellite terminals, terminal devices in the Internet of Things or the Internet of Vehicles, as well as any form of terminal in future networks, relay user equipment, or terminals in future evolved public land mobile networks (PLMNs), etc. Terminal devices can also be virtual reality (VR) devices, augmented reality (AR) devices, point-of-sale (POS) machines, customer-premises equipment (CPE), light user equipment (UE), reduced capability user equipment (REDCAP UE), and machine-type communication devices.

[0079] Terminal devices can be categorized into various types, including machine-type communication (MTC) terminals, terminal equipment in industrial control, terminal equipment in self-driving, terminal equipment in remote medical care, terminal equipment in smart grids, wireless terminals in transportation safety, terminal equipment in smart cities, terminal equipment in smart homes, tactile terminal devices, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters), intelligent robots, robotic arms, workshop equipment, wireless terminals in self-driving, and flying devices (e.g., intelligent robots, hot air balloons, drones, airplanes). Terminal devices can also be vehicle-mounted devices, such as complete vehicle units, vehicle-mounted modules, vehicle-mounted communication modules, vehicle-mounted chips, onboard units (OBUs), or telematics boxes (T-BOXs). Furthermore, terminal devices can be other devices with terminal functions; for example, they can act as terminals in device-to-device (D2D) communication. The terminal device can also be other embedded communication modules. This application does not limit this.

[0080] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip or chip system. This device can be installed in the terminal device. The chip system can consist of chips or include chips and other discrete components. In the technical solution of this application embodiment, the device for implementing the functions of the terminal device is referred to as the terminal device, which can also be called a terminal. The following description may use a UE (User Equipment) as an example to illustrate the technical solution provided in this application embodiment.

[0081] The roles of base stations and terminals can be relative, for example, Figure 1 The helicopter or drone 112i can be configured as a mobile base station. For terminals 112j that access the wireless access network 110 via 112i, terminal 112i is a base station; however, for base station 111a, 112i is a terminal, meaning that 111a and 112i communicate via a wireless air interface protocol. Of course, 111a and 112i can also communicate via a base station-to-base station interface protocol; in this case, relative to 111a, 112i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 1 111a and 111b in the diagram can be referred to as communication devices with base station functionality. Figure 1 The 112a-112j in the text can be referred to as communication devices with terminal functions.

[0082] Network devices and terminal devices can communicate via wireless links. The transmission link from a network device to a terminal device can be called a downlink (DL) or downlink channel, used to transmit downlink signals. The transmission link from a terminal device to a network device can be called an uplink (UL) or uplink channel, used to transmit uplink signals.

[0083] For example, considering the transmission from the Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (UTRAN) to the UE (Uu) interface, the two parties in the wireless communication may include network equipment and terminal equipment.

[0084] 1. Physical Layer Data Processing Flow

[0085] The basic process of physical layer data transmission is as follows: Figure 2 The physical layer receives data from the media access control (MAC) layer in the form of transport blocks (TBs). Upon receiving a TB, the physical layer first appends a Cyclic Redundancy Check (CRC) sequence, then performs code block segmentation, channel coding, and rate matching. The basic data unit processed in this process is the code block (CB). The output data unit after code block concatenation is the code word (CW). The CW is modulated and resource-mapped at the physical layer before being transmitted through the physical antenna.

[0086] The specific transformation process of data flow from TB to CB to CW is as follows: Figure 3As shown. The first step in physical layer processing is to append a CRC sequence to each TB. The size of the appended CRC sequence depends on the size of the TB; for TBs larger than 3824 bits, a 24-bit CRC sequence is used; otherwise, a 16-bit CRC sequence is used to reduce overhead. As the data transmission rate increases, the bit stream consisting of the TB data and the CRC sequence gradually increases, requiring the bit stream to be split to maintain reasonable complexity in channel coding. CB refers to the basic data unit after the TB with the added CRC sequence is divided into blocks. CRC sequence insertion and code block segmentation are performed on the TB, and CRC sequence insertion, channel coding, rate matching, and code block concatenation are performed on each CB. The output data unit after code block concatenation is CW. One CW corresponds to one bit stream processed by the TB, used for reliable transmission at the physical layer.

[0087] The typical structure of TB is as follows Figure 4 As shown in the diagram. When the size of a TB does not exceed the maximum data size that a single CB can transmit, it will not be split into multiple CBs, and no additional CRC sequence will be added. When the bitstream of a TB is large, it will be split into multiple CBs, and a CRC sequence will be added to the end of each CB to facilitate the verification of data correctness.

[0088] 2. TB

[0089] A TB, or Media Access Control Protocol Data Unit (MACPDU), refers to the basic data unit exchanged between the physical layer and the MAC layer. A MACPDU includes one or more MAC Sub-Protocol Data Units (MACsubPDUs). A MAC sub-PDU includes one of the following four types: a MAC subheader; a MAC subheader and a MAC Service Data Unit (SDU); a MAC subheader and a MAC Control Element (MACCE); or a MAC subheader and padding. Each MAC subheader can correspond to a MAC SDU, a MAC CE, or padding.

[0090] The MAC subheader includes one or more of the following fields: Logical Channel ID (LCID), Extended Logical Channel ID (eLCID), Length (L), Format (F), LCID Extension (LX), and Reserved (R). The LCID field indicates the logical channel corresponding to the MAC SDU, MAC CE, or padding information; the eLCID field indicates the extended logical channel corresponding to the MAC SDU or MAC CE; the L field indicates the length of the MAC SDU or MAC CE (e.g., in bytes); the F field indicates the length of the L field, for example, when the F field is 0, the L field length is 8 bits, and when the F field is 1, the L field length is 16 bits; the LX field indicates the use of extended LCID space; and the R field indicates reserved bits.

[0091] A MAC SDU can be data processed by higher layers, which may include the radio link control (RLC) layer, the packet data convergence protocol (PDCP) layer, and the service data adaptation protocol (SDAP) layer. Therefore, a MAC SDU may also include headers from various layers, such as the RLC header, PDCP header, and SDAP header.

[0092] The RLC header includes one or more of the following fields: sequence number (SN), segmentation info (SI), segment offset (SO), data / control (D / C), polling / flipping (P), R, and control PDU type (CPT). The SN field indicates the sequence number of the RLCSDU; the SI field indicates whether an RLC PDU contains a complete RLC SDU or the first, middle, or last segment of an RLCSDU; and the SO field indicates the position of the RLC SDU segment within the original RLC SDU.

[0093] The D / C field indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU; the P field indicates whether the sender requests a status report from the receiver; and the CPT field indicates the type of the RLC control PDU.

[0094] The PDCP header includes one or more of the following fields: PDCP SN, Message Authentication Code for Integrity (MAC-I), D / C, SDU type, and PDU type. The PDCP SN field indicates the sequence number of the PDCP SDU; the MAC-I field is used for integrity protection and verification; the D / C field indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU; the SDU type field indicates the type of PDCP SDU; and the PDU type indicates the type of control information within the PDCP control PDU.

[0095] The upper layer of the MAC layer can also include the Internet Protocol (IP) layer, Transmission Control Protocol (TCP) layer, or User Datagram Protocol (UDP) layer. Therefore, a MAC PDU can also include IP headers, TCP headers, and UDP headers. For example, the IP header may include one or more of the following fields: version, header length, type of service, total packet length, identifier, identifier, fragment offset, time to live, protocol, or header checksum; the TCP header may include one or more of the following fields: source port, destination port, sequence number, acknowledgment port number, header length, flags, window, checksum, urgent pointer, or options; the UDP header may include one or more of the following fields:

[0096] Source port, destination port, length, or checksum.

[0097] 3. Hybrid Automatic Repeat-Request (HARQ)

[0098] HARQ is a retransmission mechanism that combines forward error correction (FEC) and automatic repeat request (ARQ). FEC is an error control method where the signal is pre-encoded using a specific algorithm before being sent to the transmission channel, incorporating redundant codes characteristic of the signal itself. The receiver decodes the received signal according to the corresponding algorithm to identify and correct errors that occurred during transmission. ARQ refers to the receiver using verification information to determine the correctness of received data and feeding back the result to the sender. If a reception error occurs, the sender retransmits the data after receiving the feedback until the receiver receives it correctly.

[0099] For the data transmission process using HARQ, please refer to [link / reference]. Figure 5 The sending end can be, for example, a network device (such as a base station), and the receiving end can be a terminal device. For example... Figure 5 As shown, the base station sends data (e.g., TB) to the terminal device. The terminal device sends a HARQ response to the base station in response to this data. The HARQ response contains two types of feedback information: acknowledge (ACK) and non-acknowledge (NACK). If the base station receives an ACK, it indicates that the data transmission was successful. The base station can continue sending the next data if it receives an ACK. If the base station receives a NACK, it indicates that the data transmission failed. The base station can retransmit the data if it receives a NACK. Figure 5 The data was successfully transmitted on the second transmission, meaning the network device retransmitted the data once, or the number of retransmissions was 1.

[0100] 4. CRC

[0101] CRC is a commonly used error detection technique in data communication. It involves calculating a checksum using a specific algorithm at the sending end, appending the checksum to the end of the data frame, and sending it to the receiving end. The receiving end verifies the received data and checksum using the same algorithm to determine if the received data is correct and complete. The core idea of ​​CRC is to append an R-bit checksum to the K-bit data to be sent, then generate a new frame and send it to the receiving end. Upon receiving the new frame, the receiving end verifies the correctness of the received data based on the received data and checksum. Taking 5G as an example, both the sending and receiving ends need to select the same generator polynomial for modulo-2 division. The sending end calculates the checksum using modulo-2 division based on the K-bit data and the generator polynomial; the receiving end uses the generator polynomial to verify the new frame using modulo-2 division.

[0102] Current CRC checksum and retransmission methods can achieve near 100% error detection capability. However, in actual transmission, fields of different importance have varying impacts on service transmission. For example, for low-latency services (such as XR services) or services not sensitive to transmission errors (such as video or live streaming services), 100% error detection capability is not necessarily advantageous. In these types of services, if an unimportant field within a data unit (TB) is transmitted incorrectly, it will also cause a CRC checksum error, resulting in the retransmission of the entire TB. However, if this TB is submitted to the upper layer, it will not cause any significant performance degradation. Retransmission of the TB, on the contrary, will lead to a decrease in throughput. That is, in current CRC checksum and retransmission methods, all fields in a TB correspond to the same CRC checksum, so any field transmission error will lead to CRC checksum failure, thereby increasing transmission latency and affecting data transmission efficiency. To address this technical problem, in this embodiment, by calculating CRC checksums separately for fields of different importance, different processing can be achieved for fields of different importance. For example, important fields require retransmission by the sender to ensure complete accuracy of the transmitted content; while unimportant fields can be left unretransmitted if the error rate meets a threshold. This solution uses different CRC checksums and different error rate thresholds for fields of varying importance or fault tolerance to ensure the accuracy of important fields while reducing unnecessary retransmissions of unimportant fields, thereby increasing system throughput and reducing data packet transmission latency.

[0103] Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application. This communication method is applicable to the aforementioned communication system and mainly involves the interaction between a terminal device and a network device. This application embodiment includes a data transmission method, where the data sender is a first device and the data receiver is a second device. For uplink data transmission, the first device is the terminal device and the second device is the network device; for downlink data transmission, the first device is the network device and the second device is the terminal device. Unless otherwise specified, the device in this application can refer to the device itself, a module within the device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first device. For ease of description, the following description uses downlink transmission between the first and second devices as an example.

[0104] S601, the first device determines the first TB.

[0105] The first TB includes a first checksum and a second checksum. The first checksum is used for error detection of the first information, and the second checksum is used for error detection of the second information.

[0106] In this application, TB can be understood as a bit sequence used to carry information. The first device determining the first TB can be understood as the first device determining the bit sequence included in the first TB, or the order of the bit sequences. For example, the first check code and the second check code are CRC check codes. As another example, the first check code can be a parity check code, a vertical redundancy check code, or a Gray code, etc. The first check code and the second check code can be the same or different.

[0107] Optionally, the first TB may also include first information and second information. For example, the first information and the second information are different bit sequences in the first TB.

[0108] The first checksum is used for error detection of the first information. It can be understood as determining whether the receiving end has correctly received the first information, or whether the first information has been successfully transmitted. The second checksum is used for error detection of the second information. It can be understood as determining whether the receiving end has correctly received the second information, or whether the second information has been successfully transmitted.

[0109] Optionally, step S600 is included before S601: the first device determines a first check code based on the first information and determines a second check code based on the second information. That is, the first device calculates the corresponding check codes based on the first information and the second information respectively. Regarding the specific method for determining the check code, the first device can obtain the check code by performing modulo-2 division based on the transmitted data and the generator polynomial, or it can apply a lookup table method or other calculation methods. This application does not limit the specific method for determining the check code, nor does it limit whether the calculation methods of the first check code and the second check code are the same.

[0110] For example, the first TB includes first information, a first checksum, second information, and a second checksum. A first device determines a generator polynomial based on the length of the first checksum, determines the first checksum based on the generator polynomial and the first information, and includes the resulting checksum in the first TB. Similarly, the first device determines a generator polynomial based on the length of the second checksum, determines the second checksum based on the generator polynomial and the second information, and includes the resulting checksum in the first TB. Optionally, the first checksum and the second checksum may be included in the beginning or end of the first TB, with the first checksum preceding or following the second checksum. Alternatively, the first checksum may be appended before or after the first information, and the second checksum may be appended before or after the second information. Alternatively, the first information and the second information may be interleaved bit sequences in the first TB, for example, the information in the first TB may be in the order of first sub-information, second sub-information, third sub-information, and fourth sub-information. The first and third sub-information belong to the first information, and the second and fourth sub-information belong to the second information. In this scenario, after receiving the first TB, the second device first determines the first information and the second information. For example, the second device merges the first sub-information and the third sub-information into the first information, and merges the second sub-information and the fourth sub-information into the second information. Figure 7 As shown, the first checksum and the second checksum are included in the last segment of the first TB, and the first checksum precedes the second checksum. This is understandable. Figure 7 This is one example of a first TB structure, and the order or position of the first information, the first checksum, the second information, and the second checksum is not limited.

[0111] In one possible implementation, the first information and the second information correspond to different checksum calculation methods (e.g., generator polynomials). For example, the first device calculates a first checksum corresponding to the first information based on a first generator polynomial, and calculates a second checksum corresponding to the second information based on a second generator polynomial. Furthermore, different field types can correspond to different checksum calculation methods (e.g., generator polynomials). For example, when the information includes a PDCP header, the first device determines the checksum based on the first generator polynomial; when the information includes an RLC header, the first device determines the checksum based on the first generator polynomial. It is understood that different checksum calculation methods have different error detection capabilities. For information of high importance, a checksum with higher bit overhead but stronger error detection capability can be used; for information of low importance, a checksum with lower bit overhead but weaker error detection capability can be used. This approach can ensure the reliability of important information transmission, reduce the overhead of low-importance information, and improve transmission efficiency.

[0112] Optionally, the importance of the first piece of information may differ from that of the second piece of information, or the fault tolerance of the first piece of information may differ from that of the second piece of information.

[0113] In this application, fault tolerance can be understood as error tolerance, that is, at the receiving end, the threshold percentage of erroneous bits out of all bits, or the threshold percentage of erroneous bits out of all bits, or the upper limit of the percentage of erroneous bits that can be tolerated. For example, if a TB contains 1000 bits, and the number of erroneous bits that can be tolerated is 20 bits, then the fault tolerance of the TB is 2%. Fault tolerance can also be understood as bit error rate, bit error rate, or bit error rate, etc. Fault tolerance can also be called error rate threshold or error tolerance, etc. Importance can be understood as the degree of importance of information. For example, fault tolerance or importance can be indicated by the upper layer or predefined. For example, the fault tolerance or importance of data packets from the upper layer (e.g., the IP layer) can be determined by the upper layer and indicated to the lower layer (e.g., the MAC layer and / or the physical layer); the fault tolerance or importance of signaling or data packets (e.g., MAC CE or control PDUs of various layers) generated by the access layer can be determined by the access layer or predefined. For example, the fault tolerance of MAC CE and / or the control PDUs of each layer is predefined as 0. It can be understood that fault tolerance and importance are mutually derived, that is, the higher the importance, the lower the corresponding fault tolerance.

[0114] For example, the importance of the first information is higher than that of the second information, or the fault tolerance of the first information is lower than that of the second information. For example, the first information may include header information from various layers. For instance, the first information may include some or all of the headers from the SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, and UDP header; or, the first information may include some fields from all of the headers from the SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, and UDP header; or, the first information may include some fields from some of the headers from the SDAP header, PDCP header, RLC header, MAC layer header, IP header, TCP header, or UDP header. In yet another example, the first information may include at least one of MAC CE, RLC control PDU, or PDCP control PDU. For example, the second information may include either a data portion or a payload portion. For example, the second information may include some or all of the MACCE payload, MACSDU payload, and RLC SDU payload.

[0115] It's understandable that during communication, the headers of each protocol layer generally contain a fixed length of important information that needs to be transmitted correctly to ensure normal service operation. The MAC CE and control PDU contain control information from the data plane, which is also quite important, so their transmission accuracy must also be guaranteed. Other data components are of relatively lower importance and can tolerate a certain error rate. Therefore, ensuring the correct transmission of the first piece of information is sufficient, while a certain error tolerance can be set for the second piece of information to improve transmission efficiency.

[0116] Optionally, the first information and the second information can be carried on different radio bearers (RBs) or logical channels (LCHs). For example, the first information can be carried on a signaling radio bearer (SRB), and the second information can be carried on a data radio bearer (DRB). Another example is that the first information is carried on the first DRB, and the second information is carried on the second DRB; or, the LCH containing the first information is the first LCH, and the LCH containing the second information is the second LCH. Yet another example is that the first information is carried on an SRB, and the second information is carried on either the first RB or the first LCH.

[0117] It is understandable that different RBs or LCHs can transmit information of varying importance or fault tolerance. By carrying information of different importance or fault tolerance on different RBs or LCHs, different check codes can be used at the physical layer for the information on different RBs or LCHs, thus achieving different verification processing for information of different importance or fault tolerance.

[0118] It is understood that the method described prior to S601 also includes establishing an RRC connection.

[0119] After establishing an RRC connection between the terminal device and the network device, data transmission and / or signaling transmission for at least one service are performed. Data from different services, or data of different importance (or fault tolerance) for the same service, are delivered to the physical layer from the data generation point. The data generation point (e.g., the application layer) can indicate the importance (or fault tolerance) of the data to the lower layers, for example, by including an importance indication (or fault tolerance indication) in the data header. The physical layer determines first information and second information based on the importance or fault tolerance associated with the data, and further determines a first checksum and a second checksum. Signaling generated by different layers, or signaling used for different functions, can correspond to different importance (or fault tolerance), which can be predefined or indicated by the signaling generation layer. The physical layer determines first information and second information based on the importance (or fault tolerance) of different signaling, and further determines a first checksum and a second checksum. Signaling includes control plane signaling and data plane control information.

[0120] S602, the first device sends the first TB. Correspondingly, the second device receives the first TB.

[0121] S603, the second device performs error detection on the first and second information.

[0122] Specifically, the second device performs error detection on the first information based on the first checksum and on the second information based on the second checksum. It can be understood that the error detection of the first and second information by the second device can be a CRC check. For the specific method of CRC check, the second device can perform error detection using the same or corresponding method used by the first device to generate the checksum in step S600. Successful or correct verification of the first checksum can be understood as correctly decoding or receiving the first information, or successfully transmitting the first information; failure or error in the first checksum verification can be understood as incorrectly decoding or receiving the first information, or incorrect transmission of the first information. Similarly, successful or correct verification of the second checksum can be understood as correctly decoding or receiving the second information, or successfully transmitting the second information; failure or error in the second checksum verification can be understood as incorrectly decoding or receiving the second information, or incorrect transmission of the second information.

[0123] For example, after receiving the first TB, the receiving end can determine the first checksum using the same method based on the first information deciphered from the structure of the first TB in S601, and match the determined first checksum with the first checksum included in the first TB. If the first checksum determined by the receiving end based on the first information matches the first checksum included in the first TB, the first information is considered to have been successfully transmitted; otherwise, the first information is considered to have been transmitted incorrectly. Similarly, a second checksum is used to detect errors in the second information.

[0124] S604, the second device generates a positive or negative response.

[0125] The second device generating NACK or ACK can be understood as generating HARQ-ACK information, which includes NACK or ACK.

[0126] Specifically, the second device generates a response based on the error detection results of the first and second information and the error rate of the second information. In the method of this application embodiment, the second device performs error detection on the first and second information respectively, and additionally considers the error rate of the second information to determine whether to generate a negative response in the case of verification errors in the second information. This allows for setting different transmission reliability checks based on information of different importance, thereby improving transmission efficiency. The specific method is as follows:

[0127] If the first checksum is incorrect, or if the second checksum is incorrect and the error rate of the second information is greater than or equal to the first threshold, a NACK is generated. Here, "the second checksum is incorrect and the error rate of the second information is greater than or equal to the first threshold" can be replaced with "the error rate of the second information is greater than or equal to the first threshold." Alternatively, the above method can be understood as one or more of the following: If the first checksum is correct and the second checksum is correct, an ACK is generated; if the first checksum is correct, and the second checksum is incorrect and the error rate of the second information is less than the first threshold, an ACK is generated; if the first checksum is correct, and the second checksum is incorrect and the error rate of the second information is greater than or equal to the first threshold, a NACK is generated; if the first checksum is incorrect and the second checksum is correct, a NACK is generated; if the first checksum is incorrect, and the second checksum is incorrect and the error rate of the second information is less than the first threshold, a NACK is generated; if the first checksum is incorrect, and the second checksum is incorrect and the error rate of the second information is greater than or equal to the first threshold, a NACK is generated. Understandably, if the first checksum of the first information is incorrect, then regardless of whether the second checksum of the second information is correct or incorrect, a NACK is generated; if the first checksum of the first information is correct, then different responses are generated based on whether the second checksum of the second information is correct or incorrect, and the magnitude of the error rate.

[0128] The first threshold can be understood as the fault tolerance rate corresponding to the second information.

[0129] In another formulation, the overall judgment of the first checksum and the second checksum can be considered as a condition. Therefore, S604 can be specifically described as follows: The second device determines to generate a NACK based on a first condition. The first condition is either a first checksum error or a second checksum error and the error rate of the second information is greater than or equal to a first threshold. Here, the first checksum error is the first sub-condition, and the second checksum error and the error rate of the second information being greater than or equal to the first threshold is the second sub-condition. If at least one of the first and second sub-conditions is satisfied, the second device determines to generate a NACK. This can be understood as the second device generating a NACK when it determines that the first condition is satisfied, or generating an ACK when it determines that the first condition is not satisfied. That is, the second device generates a NACK when it determines that either the first or second sub-condition is satisfied, or it generates an ACK when it determines that neither the first nor the second sub-condition is satisfied.

[0130] Alternatively, the above method can be understood as follows: the second device determines to generate an ACK based on a second condition. The second condition is that the first checksum is verified correctly and the second checksum is verified incorrectly, and the error rate of the second information is less than a first threshold, or that the first checksum is verified correctly and the second checksum is verified correctly.

[0131] It's understandable that the error rate represents the accuracy of transmission, specifically the bit error rate (BER) or block error rate (BLER), or information determined based on BER or BLER. The error rate can be understood as the proportion of erroneous bits out of all bits in the information received by the receiver, or the proportion of erroneous portions of the information out of the total. For example, the error rate of the second information is the proportion of erroneous bits out of the total number of bits in the second information received by the receiver. It's understandable that the information received by the receiver may not be exactly the same as the information sent by the terminal. For example, during air interface transmission, information may be affected by noise interference, causing some bits to flip and resulting in transmission errors. Therefore, the error rate of the information determined by the receiver can be an estimated or extrapolated value; that is, the error rate of the information does not necessarily refer to the actual error rate.

[0132] For example, the error rate can be determined by the verification result of the check code. For instance, when the check code fails to verify the information and certain conditions are met, the error rate is determined. These specific conditions may be related to the current channel quality, the channel quality transmitting the information corresponding to the check code, or the channel quality measured before or after transmitting the information. Channel quality can be signal-to-noise ratio (SNR), signal-to-interference-plus-noise ratio (SINR), reference signal-received quality (RSRQ), or reference signal-received power (RSRP), etc. Specifically, for example, when the channel quality SNR is a specific value or within a specific range, the error rate is determined to be the first value. As another example, the error rate of the information can be obtained through artificial intelligence deduction. This application does not limit how the error rate is determined.

[0133] Optionally, the second device generates a NACK and then sends a NACK to the first device, or the second device generates an ACK and then sends an ACK to the first device.

[0134] In another possible implementation of S604, if the error rate of the second information is equal to the first threshold, the transmission reliability of the second information can be considered to meet the requirements, and an ACK is generated accordingly. The specific method is as follows:

[0135] If the first checksum is incorrect, or if the second checksum is incorrect and the error rate of the second information is greater than the first threshold, a NACK is generated. Alternatively, the above method can be understood as one or more of the following: If the first checksum is correct, and the second checksum is incorrect and the error rate of the second information is less than or equal to the first threshold, an ACK is generated; if the first checksum is correct and the second checksum is correct, an ACK is generated; if the first checksum is correct, and the second checksum is incorrect and the error rate of the second information is greater than the first threshold, a NACK is generated; if the first checksum is incorrect and the second checksum is correct, a NACK is generated; if the first checksum is incorrect, and the second checksum is incorrect and the error rate of the second information is less than or equal to the first threshold, a NACK is generated; if the first checksum is incorrect, and the second checksum is incorrect and the error rate of the second information is greater than the first threshold, a NACK is generated.

[0136] In another formulation, the overall judgment of the first and second check codes can be considered as a condition. Therefore, another possible implementation of S604 can be as follows: the second device determines to generate a NACK based on a third condition. The third condition is either a first check code error or a second check code error and the error rate of the second information is greater than a first threshold. Here, a first check code error is the first sub-condition, and a second check code error and the error rate of the second information being greater than the first threshold are the third sub-condition. If at least one of the first and third sub-conditions is satisfied, the second device determines to generate a NACK. This can be understood as the second device generating a NACK when it determines that the third condition is satisfied, or generating an ACK when it determines that the third condition is not satisfied. That is, the second device generates a NACK when it determines that either the first or third sub-condition is satisfied, or it generates an ACK when it determines that neither the first nor the third sub-condition is satisfied.

[0137] Alternatively, the above method can be understood as follows: the second device determines to generate an ACK based on a fourth condition. The fourth condition is that the first checksum is verified correctly and the second checksum is verified incorrectly, and the error rate of the second information is less than or equal to a first threshold, or that the first checksum is verified correctly and the second checksum is verified correctly.

[0138] In one possible implementation of S604, a fault tolerance rate assessment is also introduced for the first information. The second device, in determining whether to generate a positive or negative response, considers both the error rates of the first and second information, based on error detection. Specifically, the second device generates a response based on the error detection results and error rates of the first and second information, enabling simultaneous reliability verification of both pieces of information. This provides greater flexibility in transmission and improves transmission efficiency. The specific method is as follows:

[0139] If the first checksum fails and the error rate of the first information is greater than or equal to the second threshold, or if the second checksum fails and the error rate of the second information is greater than or equal to the third threshold, a NACK is generated. Here, "the first checksum fails and the error rate of the first information is greater than or equal to the second threshold" can be replaced with "the error rate of the first information is greater than or equal to the second threshold"; and "the second checksum fails and the error rate of the second information is greater than or equal to the third threshold" can be replaced with "the error rate of the second information is greater than or equal to the third threshold". Alternatively, the above method can also be understood as one or more of the following: If the first checksum is incorrect and the error rate of the first information is less than the second threshold, and the second checksum is incorrect and the error rate of the second information is less than the third threshold, generate an ACK; if the first checksum is correct, and the second checksum is incorrect and the error rate of the second information is less than the third threshold, generate an ACK; if the first checksum is incorrect and the error rate of the first information is less than the second threshold, and the second checksum is correct, generate an ACK; if the first checksum is correct and the second checksum is correct, generate an ACK; if the first checksum is incorrect and the error rate of the first information is greater than or equal to the second threshold, and the second checksum is correct, generate a NACK; if the first checksum is incorrect and the error rate of the first information is greater than or equal to the second threshold, and the second checksum is incorrect and the error rate of the second information is less than the third threshold, generate a NACK; if the first checksum is correct...

[0140] Furthermore, if the second checksum is incorrect and the error rate of the second information is greater than or equal to the third threshold, a NACK is generated; if the first checksum is incorrect and the error rate of the first information is less than the second threshold, and the second checksum is incorrect and the error rate of the second information is greater than or equal to the third threshold, a NACK is generated; if the first checksum is incorrect and the error rate of the first information is greater than or equal to the second threshold, and the second checksum is incorrect and the error rate of the second information is greater than or equal to the third threshold, a NACK is generated.

[0141] In another formulation, the overall judgment of the first check code and the second check code can also be considered as a condition, which will not be elaborated here.

[0142] Optionally, the method further includes S605 before S604, in which the second device determines the first threshold.

[0143] Wherein, the first threshold is the fault tolerance rate corresponding to the second information. The fault tolerance rate corresponding to the second information can be obtained based on the importance of the second information. It can be understood that the fault tolerance rate corresponding to the second information can be the fault tolerance rate corresponding to the RB where the second information is located or the LCH where the second information is located. For example, the second device generates a NACK or ACK response based on the error rate of the second information in the received first TB and the fault tolerance rate corresponding to the second information.

[0144] For example, the value of the first threshold can be less than or equal to 1, such as 1%, 5%, or 10%, and this application is not limited thereto. Optionally, the first threshold can be determined based on a first parameter. For example, the first parameter can be configured in the network to indicate the importance or fault tolerance of the second information. It is understood that the first threshold is related to the importance or fault tolerance of the second information.

[0145] For example, information of higher importance or lower fault tolerance corresponds to a lower fault tolerance threshold, or a lower first threshold, such as 1%; information of lower importance or higher fault tolerance corresponds to a higher fault tolerance threshold, or a higher first threshold, such as 10%. In particular, the first threshold corresponding to information of the highest importance or lowest fault tolerance is 0, that is, transmission errors are not allowed.

[0146] In possible implementations, the first threshold can be predefined, preconfigured, configured, or indicated by the first device. The first device can send the first parameter to the second device via the physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), or MACCE. This application embodiment does not limit the order of S605 with other steps; the first device can determine the first threshold before or after receiving the first TB. Different first thresholds can be set according to the transmission efficiency in the communication system and / or the data type in the first TB, thereby flexibly controlling the data fault tolerance rate during transmission.

[0147] It is understandable that the determination method for the second or third threshold can refer to the determination method for the first threshold.

[0148] Optionally, the method further includes S606, whereby if the first device receives a NACK, it retransmits the first TB. In cases of transmission errors in more important fields, or in cases of less important data transmission errors with a high error rate, the second device can indicate the transmission failure of the first TB by sending a NACK to the first device. Upon receiving a NACK, the first device can retransmit the first TB to the second device, thereby ensuring the reliability of the first TB transmission.

[0149] It is understood that the aforementioned first TB, including the first checksum and the second checksum, is merely an example, and the first TB may also include three or more checksums. Optionally, the first TB may also include three or more pieces of information. This application does not specifically limit the number of checksums and pieces of information included in the first TB.

[0150] Taking three checksums as an example, the first TB includes a first checksum, a second checksum, and a third checksum. The first checksum is used for error detection of the first information, the second checksum is used for error detection of the second information, and the third checksum is used for error detection of the third information. Optionally, the first TB may also include first information, second information, and third information. Optionally, the first device determines the first checksum based on the first information, determines the second checksum based on the second information, and determines the third checksum based on the third information.

[0151] Optionally, the importance of different pieces of information can differ, or the tolerance for error can differ. For example, the first piece of information may be more important than the second piece of information, and the second piece of information may be more important than the third piece of information; or, the tolerance for error of the first piece of information may be lower than the tolerance for error of the second piece of information, and the tolerance for error of the second piece of information may be lower than the tolerance for error of the third piece of information.

[0152] In this implementation, referring to the relevant description in S604, the second device generates an ACK based on the results of error detection of the first, second, and third information, and the error rates of the second and third information. It can be understood that the second device generates an ACK if and only if the first, second, and third information all meet the reliability requirements; otherwise, the second device generates a NACK. Specifically, the condition for the first information to meet the reliability requirements is that the first checksum is correctly verified; the condition for the second information to meet the reliability requirements is that the second checksum is correctly verified, or the error rate of the second information is less than a first threshold; the condition for the third information to meet the reliability requirements is that the third checksum is correctly verified, or the error rate of the third information is less than a fourth threshold.

[0153] In one possible implementation, the transmission reliability of the second and third information can be considered to meet the requirements when the error rate of the second information is equal to the first threshold and the error rate of the third information is equal to the fourth threshold, and an ACK is generated accordingly.

[0154] In another possible implementation, the second device, in determining whether to generate a positive or negative response, considers the error rates of the first, second, and third information in addition to error detection. It can be understood that in this case, the first information satisfies the reliability requirement if the first checksum is correctly verified, or if the error rate of the first information is less than the fifth threshold.

[0155] In one possible implementation, the fourth threshold is the fault tolerance rate corresponding to the third information, and the fifth threshold is the fault tolerance rate corresponding to the first information.

[0156] The above scheme, based on the varying importance or fault tolerance of information within a transport block, allows for different processing of fields of varying importance. Specifically, it generates NACK or ACK based on different conditions, reducing retransmissions for information with lower importance or higher fault tolerance. This transmission method minimizes unnecessary retransmissions of transport blocks and improves system transmission efficiency.

[0157] The following describes the apparatus embodiments corresponding to the method embodiments of this application. Only a brief description of the apparatus is provided below; for specific implementation steps and details, please refer to the preceding method embodiments.

[0158] To achieve the functions of the methods provided in this application, the communication device may include hardware structures and / or software modules, implementing the aforementioned functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0159] The following combination Figure 8 and Figure 9 This document describes in detail the communication apparatus used to perform the communication method provided in the embodiments of this application.

[0160] Figure 8 This is a schematic block diagram of a communication device 1000 according to an embodiment of this application. The communication device 1000 includes a processor 1010 and a communication interface 1020. Optionally, the processor 1010 and the communication interface 1020 can be interconnected via a bus. The communication device 1000 can be a first device or a second device.

[0161] Optionally, the communication device 1000 may further include a memory 1040. The memory 1040 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), cache, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD), registers, solid-state drive (SSD), or compact disc read-only memory (CD-ROM). The memory 1040 is used to store related instructions and / or data. The memory 1040 may be integrated with the processor 1010 or disposed separately.

[0162] Processor 1010 can be a general-purpose processor or a special-purpose processor. Processor 1010 may include one or more central processing units (CPUs), application processors, modem processors, graphics processors, image signal processors, digital signal processors (DSPs), video codec processors, controllers, or neural network processors. When processor 1010 is a CPU, the CPU can be a single-core CPU or a multi-core CPU. Processor 1010 can be a signal processor, a chip, or other integrated circuit capable of implementing the methods of this application, or a portion of the circuitry within the aforementioned processor, chip, or integrated circuit for processing functions. The processor in the embodiments of this application can be an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0163] The communication interface 1020 can be an input / output interface or an antenna. The input / output interface is used for inputting or outputting signals or data, or it can be an input / output circuit.

[0164] For example, the communication device 1000 is a first device, and the communication device 1000 is used to perform the following operations: determining a first transmission block, the first transmission block including a first check code and a second check code, the first check code being used for error detection of first information, and the second check code being used for error detection of second information; wherein the importance of the first information is different from the importance of the second information, or the fault tolerance rate of the first information is different from the fault tolerance rate of the second information; and sending the first transmission block.

[0165] For example, the communication device 1000 is a second device, and the communication device 1000 is configured to perform the following operations: receive a first transmission block, the first transmission block including a first check code and a second check code, the first check code being used for error detection of first information, the second check code being used for error detection of second information, the first information and the second information being different; determine that the first check code is incorrect, or determine that the second check code is incorrect and the error rate of the second information is greater than or equal to a first threshold, and generate a negative response (NACK).

[0166] The above description is for illustrative purposes only. The communication device 1000 is responsible for executing the methods or steps related to the first or second device in the foregoing method embodiments.

[0167] In one possible implementation, the communication interface 1020 can be a transceiver. The transceiver may include a transmitter and a receiver, with the transmitter performing a transmission operation and the receiver performing a reception operation. For example, the processor 1010 is used to control the transceiver to receive and / or transmit signals.

[0168] In one possible implementation, the communication interface 1020 can also be a communication circuit, pins, input / output interfaces, bus, etc.

[0169] Communication device 1000 may include a transmitter but not a receiver. Alternatively, communication device 1000 may include a receiver but not a transmitter. Specifically, it depends on whether the above-described scheme performed by communication device 1000 includes both transmitting and receiving actions.

[0170] The above description is merely exemplary. For details, please refer to the content shown in the above method embodiments. Figure 8 The implementation of each operation can also be found by referring to... Figure 6 The corresponding description of the method embodiments shown. For example, the communication device 1000 can be used to perform... Figure 6 The proposed solution is shown.

[0171] For example, the communication device 1000 is a first device, the processor 1010 is used to determine the first TB, and the communication interface 1020 is used to send the first TB.

[0172] For example, the communication device 1000 is a second device, the communication interface 1020 can be used to receive the first TB; the processor 1010 is used to perform error detection on the first information and the second information; the processor 1010 is used to generate ACK or NACK.

[0173] For details on other implementation methods, please refer to the foregoing. Figure 6 The detailed description of the embodiments shown will not be repeated here. It should be understood that the specific processes by which each component performs the corresponding processes described above have been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0174] Figure 9 This is a schematic block diagram of another communication device 1100 according to an embodiment of this application. The communication device 1100 can be the first device or the second device, or it can be a chip or module within the first or second device, used to implement... Figure 6 The methods involved in the embodiments shown are described in detail in the above-described method embodiments.

[0175] The communication device 1100 includes a transceiver unit 1110. The transceiver unit 1110 will be described exemplarily below.

[0176] The transceiver unit 1110 may include a sending unit and a receiving unit. The sending unit is used to perform the sending action of the communication device, and the receiving unit is used to perform the receiving action of the communication device. For ease of description, the sending unit and the receiving unit are combined into one transceiver unit in this embodiment. This will be explained uniformly here and will not be repeated later. The transceiver unit 1110 can implement the corresponding communication functions. The transceiver unit 1110 may also be referred to as a communication interface or a communication module.

[0177] The communication device 1100 may include a transmitting unit but not a receiving unit. Alternatively, the communication device 1100 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme performed by the communication device 1100 includes both transmitting and receiving actions.

[0178] For example, the transceiver unit 1110 is used to receive a first reference signal, etc.

[0179] Optionally, the communication device 1100 may further include a processing unit 1120, which is used to perform the processing, coordination and other steps involved in the communication device 1100.

[0180] Optionally, the communication device 1100 may further include a processing unit 1120, which is used to perform the processing, coordination and other steps involved in the communication device 1100.

[0181] The above description is for illustrative purposes only. The communication device 1100 will be responsible for executing the relevant methods or steps in the foregoing method embodiments.

[0182] Optionally, the communication device 1100 further includes a storage unit 1130 for storing programs or code for executing the aforementioned methods. Alternatively, the storage unit 1130 can be used to store instructions and / or data, and the processing unit 1120 can read the instructions and / or data from the storage unit 1130 to enable the communication device 1100 to implement the aforementioned method embodiments.

[0183] For details on the implementation method, please refer to the aforementioned document. Figure 6 The detailed description of the embodiments shown will not be repeated here. It should be understood that the specific processes by which each component performs the corresponding processes described above have been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0184] when Figure 8 When the communication device 1000 is a chip, the communication interface 1020 can be a transceiver, input / output circuit, or communication interface of the chip. The processor 1010 can be a processor integrated on the chip, a microprocessor, or an integrated circuit. In the above method embodiments, the transmitting operation of the first or second device can be understood as the output of the chip, and the receiving operation of the first or second device in the above method embodiments can be understood as the input of the chip.

[0185] when Figure 9 When the communication device 1100 is a chip, the transceiver unit 1110 can be a transceiver, input / output circuit, or communication interface of the chip. The processing unit 1120 can be a processor, microprocessor, or integrated circuit integrated on the chip. In the above method embodiments, the transmitting operation of the first device or the second device can be understood as the output of the chip, and the receiving operation of the first device or the second device in the above method embodiments can be understood as the input of the chip.

[0186] This application also provides a chip, including a processor, for calling and executing instructions stored in a memory, causing a communication device on which the chip is mounted to perform the methods described in the examples above.

[0187] This application also provides another chip, including: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is used to execute code in a memory. When the code is executed, the processor is used to perform the methods in the examples described above. Optionally, the chip further includes a memory for storing computer programs or code.

[0188] This application also provides a processor for coupling with a memory, for performing the methods and functions related to the communication device in any of the above embodiments, or for performing the methods and functions related to the first device or the second device in any of the above embodiments.

[0189] In another embodiment of this application, a computer program product comprising a computer program or instructions is provided, which, when run, enables the implementation of the methods described in the foregoing embodiments.

[0190] This application also provides a computer program that, when run, enables the implementation of the methods described in the foregoing embodiments.

[0191] In another embodiment of this application, a computer-readable storage medium is provided, which stores a computer program that, when run, implements the methods described in the foregoing embodiments.

[0192] This application also provides a communication system, which includes a first device and a second device. The first device and the second device are respectively used to perform the methods performed by the first device and the second device in the foregoing embodiments.

[0193] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

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

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

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

[0198] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contributing part of the technical solution of this application, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

Claims

1. A communication method, characterized in that, include: Receive a first transmission block, the first transmission block including a first check code and a second check code, the first check code is used for error detection of first information, the second check code is used for error detection of second information, the first information and the second information are different; If the first checksum is determined to be faulty, or if the second checksum is determined to be faulty and the error rate of the second information is greater than or equal to the first threshold, a negative response (NACK) is generated.

2. The method according to claim 1, characterized in that, A first parameter is determined, which is used to determine the first threshold.

3. The method according to claim 2, characterized in that, The first parameter is used to indicate the importance or fault tolerance of the first information.

4. The method according to any one of claims 1-3, characterized in that, The importance of the first information is different from that of the second information, or the fault tolerance of the first information is different from that of the second information.

5. The method according to any one of claims 1-4, characterized in that, The error rate of the second information is determined based on the verification result of the second check code and / or the quality of the channel through which the second information is transmitted.

6. The method according to any one of claims 1-5, characterized in that, The first information includes some or all fields from the Service Data Adaptation Protocol (SDAP) header, Packet Data Convergence Protocol (PDCP) header, Radio Link Control (RLC) header, Media Access Control (MAC) header, Internet Protocol (IP) header, and / or Transmission Control Protocol (TCP) header; or, The first information is carried on the signaling radio bearer (SRB), and the second information is carried on the data radio bearer (DRB).

7. The method according to any one of claims 1-5, characterized in that, The first information is carried on the first radio bearer (RB), and the second information is carried on the second RB; or, The logical channel (LCH) where the first information is located is the first LCH, and the LCH where the second information is located is the second LCH.

8. A communication method, characterized in that, include: A first transmission block is determined, the first transmission block including a first check code and a second check code, the first check code being used for error detection of first information, and the second check code being used for error detection of second information; wherein, the importance of the first information is different from that of the second information, or the fault tolerance rate of the first information is different from that of the second information; Send the first transport block.

9. The method according to claim 8, characterized in that, A first parameter is determined, which is used to indicate the importance or fault tolerance of the first information.

10. The method according to claim 8 or 9, characterized in that, The first information includes some or all fields from the SDAP header, PDCP header, RLC header, MAC layer header, IP header, and / or TCP header; or, The first information is carried on the SRB, and the second information is carried on the DRB.

11. The method according to claim 8 or 9, characterized in that, The first information is carried on the first RB, and the second information is carried on the second RB; or, The LCH containing the first information is the first LCH, and the LCH containing the second information is the second LCH.

12. The method according to any one of claims 8-11, characterized in that, The first verification code is determined based on the first information, and the second verification code is determined based on the second information.

13. The method according to any one of claims 8-12, characterized in that, If a NACK is received, retransmit the first transport block.

14. A communication device, characterized in that, Used to implement the method as described in any one of claims 1 to 7.

15. The communication device according to claim 14, characterized in that, The communication device includes network equipment or a chip.

16. A communication device, characterized in that, Used to implement the method as described in any one of claims 8 to 13.

17. The communication device according to claim 16, characterized in that, The communication device includes a terminal device or a chip.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, cause the method of any one of claims 1 to 7 to be implemented, or cause the method of any one of claims 8 to 13 to be implemented.

19. A computer program product, characterized in that, Includes computer instructions that, when executed, cause the method as described in any one of claims 1 to 7 to be implemented, or cause the method as described in any one of claims 8 to 13 to be implemented.

Images