Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device. The method comprises: a terminal device sending first data to a network device; in the case of a first data transmission failure, the terminal device determining whether to continue retransmitting the first data according to at least one of the QoS requirement of the QoS flow corresponding to the first data, the QoE information of the first data, and the type of the first data. In this way, the determination of whether to retransmit data can be realized, and the quality of experience of the terminal device and the QoS requirement of the QoS flow of the data can be guaranteed. Compared with directly retransmitting data, the determination of whether to retransmit data through the parameters of the data can avoid unnecessary retransmission and improve resource utilization.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more specifically, to a communication method and a communication device. Background Technology

[0002] During air interface transmission, bit errors or packet loss may occur. The robustness of air interface transmission can be improved through the hybrid automatic repeat request (HARQ) mechanism. Currently, in downlink transmission, network devices send transport blocks (TBs) to terminal devices, which can respond with either an ACK or a NACK. In uplink transmission, network devices do not send ACK / NACK responses to terminal devices; in case of reception failure, network devices typically schedule retransmission directly. Upon receiving a retransmission request from the network device, the terminal device directly retransmits the data, which may lead to unnecessary retransmissions. Summary of the Invention

[0003] This application provides a communication method and a communication device that can avoid unnecessary retransmissions and improve resource utilization.

[0004] Firstly, a communication method is provided. This method can be executed by a communication device. This communication device can be a terminal device, or a component for the terminal device (such as a chip or circuit, which can be a modem chip, also known as a baseband chip, or a system-on-chip (SoC) or system-in-package (SIP) chip containing a modem core, etc.), or a logic module or software capable of implementing some or all of the functions of the terminal device, etc. The following example uses a terminal device for illustration.

[0005] The method may include: sending first data; in the event that the first data transmission fails, determining whether to retransmit the first data based on the parameters of the first data, wherein the parameters of the first data include at least one of the following: the QoS requirements of the quality of service (QoS) stream corresponding to the first data, the quality of experience (QoE) information of the first data, and the type of the first data.

[0006] Based on the above technical solutions, when a terminal device sends data and determines that the data transmission has failed, it can determine whether to retransmit the data based on the data's parameters. For example, the terminal device can determine whether to retransmit the data based on the QoS requirements of the corresponding QoS stream. This not only enables retransmission judgment at the QoS stream level but also ensures the QoS requirements of the data's QoS stream. Furthermore, by differentiating data at the service flow level using QoS streams as the smallest granularity, when the first data includes data from multiple service flows (or multiple service channels), the terminal device can execute retransmission decisions for the data of each service flow based on the QoS requirements of the corresponding QoS stream. This fine-grained retransmission control mechanism based on QoS streams effectively avoids redundant transmission and significantly reduces the probability of unnecessary retransmissions. For another example, the terminal device can also determine whether to retransmit the data based on its QoE information. This not only enables judgment on whether to retransmit data but also ensures the user experience quality of the terminal device. In summary, compared to directly retransmitting data, determining whether retransmission is necessary based on the data's parameters effectively avoids redundant transmission, reduces the probability of unnecessary retransmissions, and improves resource utilization. In conjunction with the first aspect, in some implementations of the first aspect, the failure of the first data transmission includes: the first data fails after being transmitted N times via Hybrid Automatic Repeat Request (HARQ), where N is an integer greater than or equal to 1.

[0007] Based on the above technical solution, if data transmission still fails after HARQ, the terminal device can determine whether to perform secondary retransmission (or type II retransmission) based on the data parameters. This can achieve a balance between successful data transmission and resource utilization.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the parameters of the first data include the QoS requirements of the QoS stream corresponding to the first data. Determining whether to retransmit the first data based on the parameters of the first data includes: retransmitting the first data if the QoS requirements of the QoS stream corresponding to the first data are not met; or not retransmitting the first data if the QoS requirements of the QoS stream corresponding to the first data are met.

[0009] Based on the above technical solution, the terminal device can determine whether to retransmit the data based on whether the QoS requirements (or QoS constraints) of the corresponding QoS stream are met. If the QoS requirements of the data have been met, retransmission is unnecessary to improve resource utilization; if the QoS requirements of the data have not been met, retransmission can continue to improve the data transmission success rate and ensure the QoS of the data.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the QoS requirements of the QoS stream corresponding to the first data include the packet loss rate requirements of the QoS stream corresponding to the first data. If the QoS requirements of the QoS stream corresponding to the first data are not met, the first data is retransmitted, including: if the current packet loss rate of the QoS stream corresponding to the first data is higher than the packet loss rate requirements of the QoS stream corresponding to the first data, the first data is retransmitted.

[0011] Based on the above technical solution, the terminal device can determine whether to retransmit the data based on whether the current packet loss rate (i.e., the actual packet loss rate) of the QoS stream corresponding to the data meets the packet loss rate requirement. This judgment method is simple and easy to implement, and is applicable to many scenarios.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the current packet loss rate of the QoS stream corresponding to the first data is the packet loss rate of the QoS stream corresponding to the first data within the first window, wherein the length of the first window is: the length of transmitting T data, or a preset duration, where T is an integer greater than 1.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the parameters of the first data include the QoS requirements of the QoS stream corresponding to the first data and the type of the first data. Determining whether to retransmit the first data based on the parameters of the first data includes: if the type of the first data is a first service type, determining whether to retransmit the first data based on the QoS requirements of the QoS stream corresponding to the first data; or, if the type of the first data is a second service type, determining whether to retransmit the first data based on the QoS requirements of the QoS stream corresponding to the first data when the packet delay budget (PDB) in the QoS stream corresponding to the first data has not expired; or, if the PDB in the QoS stream corresponding to the first data expires, determining not to retransmit the first data.

[0014] Based on the above technical solution, and considering that some services are time-sensitive while others are not, different retransmission judgment methods can be selected based on different service types. For example, for time-sensitive services (such as the second service type), if the PDB has already timed out, retransmission is not very meaningful, so data for this type of service does not need to be retransmitted. For time-insensitive services (such as the first service type), even if the PDB has timed out, retransmission can still be determined based on whether the QoS requirements are met, in order to ensure the data transmission success rate as much as possible.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the parameters of the first data include the type of the first data. Determining whether to retransmit the first data based on the parameters of the first data includes: retransmitting the first data if the type of the first data is a first type; or determining not to retransmit the first data if the type of the first data is a second type.

[0016] Based on the above technical solution, it is possible to determine whether to retransmit data based on whether the data type requires retransmission or not. This places lower demands on the capabilities of the terminal device and can be applied to more scenarios.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first type and the second type satisfy at least one of the following: the importance of the data of the first type is higher than the importance of the data of the second type; the first type is associated with the first QoS stream, and the second type is associated with the second QoS stream; wherein, the transmission reliability requirement of the first QoS stream satisfies the first preset condition, and the transmission reliability requirement of the second QoS stream satisfies the second preset condition.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving indication information indicating that the first data transmission failed; or, if no indication that the first data transmission was successful is received within a preset time period, determining that the first data transmission failed.

[0019] Based on the above technical solution, the terminal device can determine the data transmission status based on feedback from the network device or whether it has received feedback from the network device, which is simple and easy to implement.

[0020] In conjunction with the first aspect, in certain implementations of the first aspect, sending the first data includes: sending the first data through a first HARQ process; the indication information indicating that the first data transmission failed includes: the indication information indicating whether at least one piece of data associated with M HARQ processes was successfully transmitted, wherein the M HARQ processes include the first HARQ process, and at least one piece of data associated with the first HARQ process includes the first data; or, the indication information is further used to schedule the second data associated with the first HARQ process.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, where the indication information is also used to schedule the second data associated with the first HARQ process, the method further includes: sending the second data through the first HARQ process based on the indication information.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the second data includes the first data or a portion of the first data; or, the second data is newly transmitted data.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, when the retransmission of the first data is determined based on the parameters of the first data, the method further includes: sending third data at the Media Access Control (MAC) layer, the third data being obtained based on the first data; or, sending third data at a higher layer 2, the third data being obtained based on the higher layer 2 data contained in the first data.

[0024] Secondly, a communication method is provided. This method can be executed by a communication device. This communication device can be a terminal device, or a component for the terminal device (such as a chip or circuit, which can be a modem chip, also known as a baseband chip, or a SoC or SIP chip containing a modem core, etc.), or a logic module or software capable of implementing some or all of the functions of the terminal device, etc. The following example uses a terminal device for illustration.

[0025] The method may include: sending first data; sending indication information, the indication information being used to determine whether to retransmit the first data; wherein the indication information indicates the maximum number of transmissions of the first data and / or time information, or, the indication information indicates whether to retransmit the first data; wherein, the maximum number of transmissions is the maximum number of retransmissions, or, the maximum number of transmissions is the maximum number of retransmissions + 1; and the time information indicates the expiration time of the first data.

[0026] Based on the above technical solution, the terminal device can directly indicate to the network device the maximum number of data transmissions and / or the data expiration time (or the data validity period), or the terminal device can directly indicate to the network device whether HARQ retransmission is required. In this way, the network device can schedule HARQ retransmissions based on the terminal device's instructions. This not only aligns data transmission and reception between the terminal device and the network device but also avoids unnecessary retransmissions, improving resource utilization. For example, for some data that has already expired or is about to expire, scheduling HARQ retransmissions is unnecessary; therefore, the terminal device can directly indicate to the network device that HARQ retransmission is not required.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: determining indication information based on the parameters of the first data, wherein the parameters of the first data include at least one of the following: the QoS requirements of the QoS stream corresponding to the first data, the Quality of Experience (QoE) information of the first data, and the type of the first data.

[0028] Thirdly, a communication method is provided. This method can be executed by a communication device. This communication device can be a network device, or a component for a network device (such as a chip or circuit, which can be a modem chip, also known as a baseband chip, or a SoC or SIP chip containing a modem core, etc.), or a logic module or software capable of implementing some or all of the functions of a network device, etc. The following example uses a network device for illustration.

[0029] The method may include: receiving first data; receiving indication information, the indication information being used to determine whether to retransmit the first data; wherein the indication information indicates the maximum number of transmissions of the first data and / or time information, or, the indication information indicates whether to retransmit the first data; wherein, the maximum number of transmissions is the maximum number of retransmissions, or, the maximum number of transmissions is the maximum number of retransmissions + 1; and the time information indicates the expiration time of the first data.

[0030] In conjunction with the second or third aspect, in some implementations, the first data and the indication information satisfy at least one of the following: the time domain resources of the first data and the time domain resources of the indication information are the same; the first data and the indication information are carried on the same channel; the first data and the indication information are carried on the same transport block.

[0031] Based on the above technical solutions, terminal devices can simultaneously send data and indication information for that data, or carry data and indication information for that data in the same channel or transport block, so that network devices can directly identify which data the indication information is for, with lower signaling overhead.

[0032] For possible approaches and beneficial effects of the third aspect, please refer to the relevant descriptions in the second aspect, which will not be repeated here.

[0033] Fourthly, a communication apparatus is provided for performing the methods of any one of the first to third aspects and any possible implementation thereof. Specifically, the apparatus may include units and / or modules for performing the methods of any one of the first to third aspects and any possible implementation thereof, such as processing units and / or communication units.

[0034] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0035] In another implementation, the device is a chip, chip system, circuit, or communication module for communication equipment (such as terminal equipment or network equipment). When the device is a chip, chip system, or circuit for communication equipment, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0036] Fifthly, a communication device is provided, the device comprising: at least one processor configured to cause the device to perform any of the first to third aspects and any possible implementation thereof.

[0037] Optionally, the at least one processor is configured to execute computer programs or instructions to perform the methods of any one of the first to third aspects and any possible implementation thereof.

[0038] Optionally, the device further includes a memory for storing the computer program or instructions.

[0039] Optionally, the at least one processor is coupled to a memory, which may be located outside the device.

[0040] Optionally, the device also includes a communication interface through which the processor reads instructions, such as instructions from memory. This can be understood as the communication interface being coupled to the processor and used to input computer programs or instructions to the processor, or to output information from the processor.

[0041] Unless otherwise specified, or if the transmission and acquisition / reception operations involved do not contradict their actual function or internal logic in the relevant description, they can be understood as output, input, or other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0042] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0043] In another implementation, the device is a chip, chip system, circuit, or communication module for communication equipment (such as terminal equipment or network equipment). Optionally, the chip is a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core.

[0044] In a sixth aspect, a computer-readable storage medium is provided, on which a computer program (e.g., program code) or instructions are stored, which, when executed on a communication device, cause the communication device to perform the methods of any one of the first to third aspects and any possible implementation thereof.

[0045] In a seventh aspect, a computer program product comprising instructions is provided, which, when run on a computer, causes the computer to perform any of the first to third aspects and any possible implementation thereof.

[0046] Eighthly, a communication system is provided, including a first communication device and a second communication device. The first communication device is used to execute the method provided in any implementation of the second aspect, and the second communication device is used to execute the method provided in any implementation of the third aspect. Attached Figure Description

[0047] Figure 1 This is a schematic diagram of a wireless communication system applicable to embodiments of this application.

[0048] Figure 2 This is a schematic diagram of data transmission using the stop-and-wait protocol.

[0049] Figure 3 This is a diagram illustrating data transmission via the HARQ process.

[0050] Figure 4 This is a schematic diagram of data transmission using the NDI flip mechanism.

[0051] Figure 5 This is a schematic diagram of a communication method 500 provided in an embodiment of this application.

[0052] Figure 6 This is a schematic diagram of data retransmission applicable to embodiments of this application.

[0053] Figure 7 This is a schematic diagram of a communication method 700 provided in an embodiment of this application.

[0054] Figure 8 This is a schematic diagram of data retransmission applicable to embodiments of this application.

[0055] Figure 9 This is a schematic block diagram of a communication device 900 provided in an embodiment of this application.

[0056] Figure 10 This is a schematic diagram of another communication device 1000 provided in an embodiment of this application.

[0057] Figure 11This is a schematic diagram of a chip system 1100 provided in an embodiment of this application. Detailed Implementation

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

[0059] Before introducing the scheme of this application, the following points should be noted.

[0060] (1) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing an instruction information as indicating A, it can be understood that the instruction information carries A, carries the identifier of A, carries B which is associated with A, carries the identifier of B which is associated with A, etc. In other words, if the receiving side of an instruction information can determine A based on the instruction information, it can be described as the instruction information indicating A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" can be replaced with "includes". In this case, a statement such as "send / receive instruction information, the instruction information indicates A" can be replaced with "send / receive A".

[0061] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate 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 of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0062] (2) In this application, the expression " / " is used to indicate that the objects before and after are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after are in a relationship of either "and" or "or"; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.

[0063] (3) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0064] (4) In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0065] (5) In this application, "predefined" can mean a standard protocol predefined, or it can mean a pre-agreed or pre-negotiated agreement between devices. Here, "protocol" can refer to a standard protocol in the field of communications, such as a fourth-generation (4G) protocol. th Generation 4G network, fifth generation (5G) network th This application does not limit the scope to network protocols such as 5G (generation, 5G), New Radio (NR), 5.5G, and related protocols applied in future communication networks.

[0066] (6) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a specific manner. In the embodiments of this application, “of,” “corresponding, relevant,” “corresponding,” and “associated” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless the distinction is emphasized.

[0067] (7) In this application, "first," "second," and "#1," "#2," and "#A" are merely for descriptive convenience and to distinguish objects, and are not intended to limit the scope of the embodiments of this application. For example, the QoS flow #A mentioned in the embodiments of this application is to distinguish different QoS flows; specifically, QoS flow #A represents the QoS flow corresponding to the first data. As another example, the first data in the embodiments of this application is a general term, and it can also be referred to as data.

[0068] (8) In this application, the configuration can be signaling configuration, such as radio resource control (RRC) messages, control information (such as downlink control information (DCI)), or medium access control (MAC) signaling (e.g., MAC control element (MAC CE / MAC-CE)). As an example, signaling configuration can be configured by signaling to the terminal device. For example, when a network device configures resources, it can be understood that the network device instructs the terminal device on the relevant information of the resource through signaling.

[0069] First, let me introduce the communication system to which this application applies.

[0070] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication networks. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication.

[0071] As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. Satellite base stations can also communicate with each other. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment.

[0072] As an example, V2X communication can include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0073] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication equipment, communication module, node, communication node, etc. This application uses a device as an example for description.

[0074] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3GPP standard. The device may be a wireless communication unit (RSU), or a device built into the aforementioned device (e.g., a communication module, modem, or chip in the aforementioned device), or other processing devices connected to the wireless modem.

[0075] It should be understood that in certain scenarios, a UE can also be used as a scheduling entity. For example, as a scheduling entity, a UE can provide sidelink signals between UEs in scenarios such as V2X, D2D, or P2P.

[0076] In this embodiment, the device for implementing the functions of a terminal device, i.e., 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 system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can also be configured with program instructions for performing corresponding communication functions.

[0077] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, multiple standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0078] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0079] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, or DU, or devices including CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes.

[0080] In some deployments, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, 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, AAUs, or RRHs.

[0081] 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, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (openCU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (open CU-CP, O-CU-CP), CU-UP can also be called an open CU-UP (open CU-UP, O-CU-UP), and RU can also be called an open RU (openRU, O-RU). 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.

[0082] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0083] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0084] Combination Figure 1 The communication system applicable to the embodiments of this application is briefly described below.

[0085] See Figure 1 As an example, Figure 1 This is a schematic diagram of a wireless communication system applicable to embodiments of this application. For example... Figure 1 As shown, the wireless communication system includes a wireless access network 100. The wireless access network 100 can be a future or later version of the wireless access network, or a traditional (e.g., 5G, 4G, 3G, or 2G) wireless access network. One or more terminal devices (120a-120j, collectively referred to as 120) can be interconnected or connected to one or more network devices (110a, 110b, collectively referred to as 110) within the wireless access network 100. Network elements in the wireless communication system are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces.

[0086] When network devices and terminal devices communicate, the network device can manage one or more cells, and a cell can include at least one terminal device. A cell can be understood as an area within the wireless signal coverage range of the network device.

[0087] Figure 1 This is just an illustration; the wireless communication system may also include other devices, such as core network equipment, wireless relay equipment, and / or wireless backhaul equipment. Figure 1 It is not shown in the middle.

[0088] To facilitate understanding of the embodiments of this application, the terms and concepts involved in this application are briefly explained. It is understood that the concepts and terms introduced below are for illustrative purposes only and do not limit the scope of protection of the embodiments of this application.

[0089] 1. Retransmission mechanism

[0090] Retransmission refers to retransmitting data after a transmission failure. Currently, there are three main retransmission mechanisms.

[0091] (1) Medium Access Control (MAC) Layer Retransmission: The Hybrid Automatic Repeat Request (HARQ) mechanism at the MAC layer is a commonly used retransmission mechanism. HARQ means that after receiving information, the receiving end immediately feeds back the result of successful or failed transmission to the sending end to achieve fast retransmission. To reduce feedback overhead, HARQ feedback does not include cyclic redundancy check (CRC), resulting in low reliability. Consequently, MAC layer retransmissions are sometimes considered lossy retransmissions.

[0092] (2) Radio Link Control (RLC) Layer Retransmission: The Automatic Repeat Request (ARQ) mechanism of the RLC layer can supplement the MAC layer retransmission. This ARQ mechanism means that the receiver uses CRC checksums to determine if the received data is correct and feeds back the result to the transmitter. If an error is received, the transmitter retransmits the data after receiving the feedback until the receiver receives it correctly. Compared to the HARQ mechanism, the RLC layer retransmission feedback status report has a lower transmission frequency, so the overhead required to achieve a lower feedback error rate is relatively small. Furthermore, RLC layer retransmission feedback is sent through the physical downlink shared channel (PDSCH), and the corresponding feedback is protected by CRC, thus achieving very high feedback reliability.

[0093] As an example, the RLC layer includes three data transmission modes.

[0094] 1) Transparent Mode (TM): In transparent mode, the RLC layer does not modify the data packet and passes it through to the adjacent layer. There are no RLC layer segmentation, header addition / removal, or retransmission operations in transparent mode. For example, information transmitted in transparent mode includes: system messages, paging messages, message (MSG)2, MSG3, MSG4, etc.

[0095] 2) Unacknowledged mode (UM): In unacknowledged mode, the RLC layer segments data packets but does not support retransmission. For example, information transmitted in unacknowledged mode includes: transmissions based on NR voice (VoNR) or other latency-sensitive services.

[0096] 3) Acknowledged Mode (AM): Acknowledged mode is a reliable transmission mode that supports operations such as segmentation, reassembly, and ARQ retransmission. This mode ensures that every data packet transmitted over the air interface is correctly received by the other end and strives to guarantee zero packet loss over the air interface. For example, information transmitted in acknowledged mode includes error-sensitive, latency-tolerant non-real-time application information, such as web browsing, file transfer protocol (FTP) downloads, and signaling transmissions.

[0097] RLC layer data retransmission typically uses an acknowledgment mode. In acknowledgment mode, when the receiver receives an erroneous protocol data unit (PDU), it notifies the sender to retransmit via a status report. The status report can be sent proactively by the receiver or requested by the sender. For example, if the sender's transmit buffer runs out of space due to unacknowledged PDUs, the sender can request the receiver to send a status report.

[0098] (3) Packet Data Convergence Protocol (PDCP) layer retransmission: mainly used in scenarios where terminal devices hand over cells across base stations. Since the relevant configurations and caches of lower-layer protocols (RLC layer and MAC layer) are cleared during the handover process, but not of the PDCP layer, the PDCP layer retransmission function can ensure as much as possible that data is not lost due to the terminal device handover.

[0099] It is understood that although the embodiments of this application mainly use the MAC layer and RLC layer as examples for illustration, the scope of protection of this application is not limited to these. Specifically, the RLC layer is a sub-layer of the data link layer (Layer 2, L2) in the protocol stack, usually located above the physical layer (PHY) and between the MAC layer and the PDCP layer. In this application, any protocol layer that can implement the same or similar functions as the RLC layer in a future communication system is applicable to the embodiments of this application. For example, the RLC layer can be replaced by a "first layer," as long as the "first layer" can perform some or all of the functions of the RLC layer, it falls within the scope of protection of this application.

[0100] It is understood that although the embodiments of this application mainly use the MAC layer and RLC layer as examples for illustration, the protection scope of the embodiments of this application is not limited to this. Taking the RLC layer as an example, specifically, the RLC layer is a sub-layer of the data link layer 2 (L2) in the protocol stack, usually located above the physical layer (PHY) and between the MAC layer and the PDCP layer. In the embodiments of this application, any protocol layer that can implement the same or similar functions as the RLC layer in a future communication system is applicable to the embodiments of this application. For example, the RLC layer can be replaced by "layer 1", as long as the "layer 1" can perform some or all of the functions of the RLC layer, it falls within the protection scope of the embodiments of this application.

[0101] 2. HARQ

[0102] As an example, the HARQ process can use a stop-and-wait protocol to send data. The stop-and-wait protocol means that after the sender sends a transport block (TB), it waits for an acknowledgment; the receiver can use one bit of information to acknowledge the transport block with either an ACK or a negative acknowledgment (NACK); the receiver sends the next TB only after receiving an ACK. Here, ACK indicates that the TB was successfully received and decoded; NACK indicates that the TB was not successfully received or decoded.

[0103] See Figure 2 As an example, Figure 2 This is a schematic diagram illustrating data transmission using a stop-and-wait protocol. For example... Figure 2 As shown, the sending end sends the first TB, the receiving end receives the first TB, and reports the reception status of the first TB back to the sending end; the sending end receives the reception status of the first TB, and if the reception status of the first TB indicates that the first TB was successfully received, the sending end sends the second TB, otherwise the sending end continues to send the first TB; and so on.

[0104] 3. HARQ process

[0105] Stop-and-wait protocols require the sender to pause and wait for feedback from the receiver after each message transmission, resulting in low throughput. Therefore, HARQ employs multiple stop-and-wait processes (i.e., HARQ processes) in parallel. Specifically, while one HARQ process is waiting for acknowledgment, the sender can use another HARQ process to continue sending messages; similarly, while the receiver is processing messages received by one HARQ process, it can use another HARQ process to continue receiving messages. Multiple HARQ processes processing in parallel form a HARQ entity, with one HARQ entity corresponding to each uplink or downlink carrier. As an example, a single HARQ entity supports a maximum of 16 HARQ processes, as defined in 3GPP TS 38.214.

[0106] See Figure 3 As an example, Figure 3 This is a diagram illustrating data transmission via the HARQ process. (Example) Figure 3 As shown, the sending end sends TB1 through HARQ process 0, and after sending TB1, it can send TB2 through HARQ process 1; and after sending TB2, it can send TB3 through HARQ process 2; and so on. Furthermore, after receiving a TB, the receiving end can report the reception status of the TB to the sending end, allowing the sending end to determine whether to retransmit the TB through the HARQ process containing that TB or send a new TB based on the reception status. Figure 3 As shown, taking TB1 as an example, the receiving end reports the reception status of TB1 to the sending end. If the receiving end reports NACK to the sending end, it means that TB1 was not successfully received. Based on the feedback from the receiving end, the sending end continues to retransmit TB1 through HARQ process 0. Assuming that the receiving end successfully receives the retransmitted TB1, the receiving end sends ACK to the sending end. Based on the feedback from the receiving end, the sending end determines that TB1 was successfully received, so the sending end sends a new TB (such as TB6) through HARQ process 0; and so on.

[0107] Considering the possibility of multiple HARQ processes operating in parallel, these processes can be numbered, such as each HARQ process corresponding to a HARQ process number. This way, when the receiving end receives a data unit (TB), it can determine which HARQ process the TB belongs to. The HARQ process number can also be called the HARQ process identifier (ID). A single HARQ process number can be used to uniquely identify a HARQ process.

[0108] As an example, network devices can use the DCI to indicate the HARQ process number to the terminal device, so that the terminal device can know which HARQ process the current uplink or downlink transmission belongs to. Assuming a HARQ entity supports a maximum of 16 HARQ processes, the network device can indicate the HARQ process number to the terminal device using 4 bits in the DCI. For a detailed explanation of the fields included in the DCI information and their meanings, please refer to section 7.3.1.2 of 3GPP TS 38.212; it will not be elaborated upon here.

[0109] 4. New Data Indicator (NDI)

[0110] Once the receiving end determines which HARQ process the received data transfer (TB) belongs to, it can use the NDI (Non-Distributed Data Indicator) to determine whether the TB is initial transmission or retransmission. This NDI can be carried in the DCI (Distributed Content Controller). Specifically, each HARQ process can store an NDI value, which can be either 0 or 1. The sending end uses whether the NDI value is toggled to indicate to the receiving end whether the current transmission is initial or retransmission. If the NDI value sent this time is opposite to the previously sent NDI value (i.e., NDI is toggled), it indicates that the data being sent is initial transmission; if the NDI value sent this time is the same as the previously sent NDI value (i.e., NDI is not toggled), it indicates that the data being sent is retransmission.

[0111] See Figure 4 As an example, Figure 4 This is a schematic diagram illustrating data transmission using the NDI flip-flop mechanism. (Example) Figure 4 As shown, assuming an initial NDI value of 0 in a certain HARQ process, when the sender transmits a new TB1 to the receiver in this HARQ process, the NDI value sent to the receiver is 0. If TB1 is successfully received, the receiver sends an ACK. After receiving the ACK, the sender sends a new TB (such as TB2) to the receiver in HARQ process 0, at which point it flips the NDI value to 1 and sends it to the receiver. The receiver, based on the NDI value of 1, determines that this transmission is the first transmission. If TB2 is not successfully received, the receiver sends a NACK. After receiving the NACK, the sender determines that TB2 needs to be retransmitted. When the sender retransmits TB2, the NDI value sent to the receiver remains unchanged at 1. The receiver, based on the NDI value of 1, determines that this transmission is a retransmission; and so on.

[0112] 5. Downlink HARQ transmission and uplink HARQ transmission

[0113] During downlink transmission, the network device sends data to the terminal device, and the terminal device can send HARQ feedback to the network device to indicate whether the data was successfully received. Specifically, if the terminal device successfully receives the data, it sends an ACK to the network device; if the terminal device fails to receive the data, it sends a NACK to the network device. The network device determines whether to retransmit the data based on the ACK or NACK.

[0114] In uplink transmission, the terminal device sends data to the network device, and in existing technologies, the network device does not provide ACK or NACK feedback to the terminal device. Specifically, after the network device schedules uplink transmission through DCI, the terminal device sends data to the network device based on DCI; if the network device successfully receives the data, it directly schedules the new data transmission; the terminal device sends the new data upon receiving a new transmission instruction, and retransmits the data upon receiving a retransmission instruction. In other words, in existing technologies, the terminal device does not explicitly know whether the network device has successfully received the data. One implementation involves the network device providing feedback to the terminal device regarding whether it has successfully received the data. If the network device fails to receive the data, whether the terminal device should retransmit the data is a question worth considering. In view of this, embodiments of this application propose that if data fails after one or more HARQ transmissions, the terminal device can determine whether to retransmit the data based on some data references. This not only improves the flexibility and success rate of data transmission but also reduces unnecessary retransmissions. Furthermore, the terminal device can also indicate to the network device whether to perform HARQ retransmission, so that the network device can schedule data based on the terminal device's indication.

[0115] The methods provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings. For ease of description, terminal devices and network devices are used as examples for illustrative purposes. The terminal device can be replaced by components of a terminal device (e.g., a chip, chip system, circuit, or communication module), and the network device can be replaced by components of a network device (e.g., a chip, chip system, circuit, or communication module). Furthermore, the steps described below as being performed by a single execution entity can also be divided into steps performed by multiple execution entities, which can be logically and / or physically separated.

[0116] See Figure 5 As an example, Figure 5 This is a schematic diagram of a communication method 500 provided in an embodiment of this application. Figure 5 The method 500 shown may include the following steps.

[0117] Method 500 includes steps S510 and S530. Optionally, method 500 also includes step S520. These steps are described in detail below.

[0118] In S510, the terminal device sends the first data, and correspondingly, the network device receives the first data.

[0119] Here, "data" can also be replaced with data packets or data blocks; there is no limitation on this. For consistency, the following descriptions will use "data." Furthermore, "first data" and "second data" mentioned later are general terms; for example, "first data" can also be simply referred to as "data."

[0120] Optionally, prior to S510, method 500 further includes: the terminal device receiving first control information, the first control information being used to schedule first data. Thus, the terminal device can send the first data based on the received first control information. In other words, the terminal device receives first control information used to configure a series of available authorization information for the terminal device, such that the terminal device can use the series of available authorization information to send the first data, or the terminal device can use one or more of the series of available authorization information to send the first data.

[0121] In the embodiments of this application, the terms first control information, second control information, and third control information are mentioned multiple times. Here, the first control information is used as an example for explanation. The first control information can be referred to as any of the following: control information, scheduling information, uplink scheduling, or configured grant information. For example, it can be a DCI (Distributed Control Information Framework), which can be used to configure available grant information for transmitting and receiving signals (such as data) for the terminal device. As an example, the first control information includes a resource indication (or resource configuration, or it can also be understood as an uplink grant (UL Grant)) for the first data, and the terminal device can then send the first data to the network device based on this resource indication. The second and third control information are similar to the first control information, except that the first, second, and third control information are used to configure different available grant information for the terminal device; or, in other words, the first, second, and third control information are used to schedule different data for the terminal device.

[0122] Optionally, method 500 also includes S520.

[0123] S520, the terminal device determines whether the first data has been successfully transmitted.

[0124] Specifically, data transmission status (or reception status) generally includes two types: successful data transmission and failed data transmission. Successful data transmission, or data transmission success, means that the terminal device sends data to the network device, and the data is successfully received by the network device. Failed data transmission, or data transmission failure, means that the terminal device sends data to the network device, but the data is not successfully received by the network device. Failed data transmission may be due to the terminal device failing to send data; it may also be due to the network device failing to receive data, such as incorrect demodulation, etc. This application embodiment does not limit the reasons for failed data transmission. In this application embodiment, successful data transmission can mean that the initial data transmission was successful, the data retransmission was successful, or the data was successfully transmitted after N HARQ transmissions; similarly, failed data transmission can mean that the initial data transmission failed, the data retransmission failed, or the data failed after N HARQ transmissions, and this is not limited. Here, N is an integer greater than or equal to 1. In the following embodiments, for consistency, successful transmission and failed transmission are used as examples for description. For HARQ newtransmissions and retransmissions, the receiving side (such as network devices) can perform merging and decoding to obtain soft merging gain. In order to obtain the soft merging effect, HARQ retransmissions do not change the content of the transport block. That is, the sending side (such as terminal devices) only retransmits the transport block transmitted at the HARQ point, and the content contained therein remains unchanged.

[0125] The terminal device determines whether the first data has been successfully transmitted in at least the following ways.

[0126] Implementation method 1: The network device sends information #A (an example of an indication message) to the terminal device, and the terminal device determines whether the first data was successfully transmitted based on information #A. Several scenarios are described below.

[0127] In the first possible scenario, information #A is control information, such as the second control information. Based on this, when scheduling new or retransmitted data, network devices can include an indication in the control information to indicate whether previous data transmission was successful. In other words, terminal devices can determine whether previous data transmission was successful by the indication included in the control information for the same HARQ process. Using control information for the same HARQ process to indicate whether previous data transmission was successful saves the overhead of carrying the additional HARQ process number. For example, the second control information implicitly indicates the success or failure of previous transmissions within the same HARQ process, thus saving the overhead of carrying the additional HARQ process number. Furthermore, the control information of the HARQ process containing the second control information includes a CRC checksum, which makes the reception of the second control information more reliable and minimizes false detection problems (e.g., NACK mistakenly detected as ACK).

[0128] As an example, message #A is used to schedule the second data. The first and second data belong to the same HARQ process (referred to as the first HARQ process for distinction), meaning the first and second data are sent by the terminal device through the same HARQ process. One possible implementation is that the second data is newly transmitted data. Taking Q data items associated with the first HARQ process as an example, the first data can be any one of the Q data items; the second data is the data item that follows the first data item among the Q data items, meaning the terminal device sends the first data item earlier than the second data item, where Q is an integer greater than 1. Another possible implementation is that the second data is retransmission of the first data. Based on this, message #A is used to schedule the retransmission of the first data. Further optionally, the terminal device also sends the second data through the first HARQ process. The second data includes the first data or a portion of the first data; or, the second data is newly transmitted data.

[0129] In this case, the information #A indicates whether the first data was successfully transmitted, and includes at least the following implementation methods.

[0130] In the first possible implementation, the terminal device determines whether the first data has been successfully transmitted based on the indication carried by information #A (referred to as indication information #1 for distinction).

[0131] For example, indication information #1 is implemented using at least 1 bit. Taking indication information #1 implemented using 1 bit as an example, that is, 1 bit is used to indicate whether the first data was transmitted successfully. For instance, if this bit is set to the first value (that is, the value of indication information #1 is the first value), it indicates that the first data transmission was successful; if this bit is set to the second value (that is, the value of indication information #1 is the first value), it indicates that the first data transmission failed. For example, the first value is 0 and the second value is 1; or the first value is 1 and the second value is 0.

[0132] For example, indication information #1 is implemented through a specific field. For instance, if the value of indication information #1 is ACK, it means that the first data transmission was successful; if the value of indication information #1 is NACK, it means that the first data transmission failed; or, if the value of indication information #1 is undetected (UDT), it means that the transmission of the first data was not detected.

[0133] Optionally, each data item is associated with an identifier, and different data items within the same HARQ process are associated with different identifiers over a period of time. This identifier can be used to identify (or characterize, or indicate) the data associated with it, or it can be used to identify different rounds within a HARQ process. For ease of description, the initial transmission and several retransmissions (if any) of a HARQ process are called a round of HARQ transmission. Figure 3Taking HARQ process 0 as an example, the sending end sends TB1 and TB6 through HARQ process 0. TB1 and TB6 can each be associated with an identifier. For example, the identifier can be a sequence number (SN) or an index. For instance, for the first HARQ process, the terminal device receives first control information, which is used to schedule the data associated with the sequence number (e.g., SN). The terminal device sends the data associated with SN based on the first control information. Subsequently, the terminal device receives second control information, which is used to schedule the data associated with the sequence number (e.g., SN+1). The terminal device sends the data associated with SN+1 based on the second control information. Subsequently, the terminal device receives third control information, which is used to schedule the data associated with the sequence number (e.g., SN+2). The terminal device sends the data associated with SN+2 based on the third control information.

[0134] As an example, a network device can carry an identifier for the first data association in information #A, so that the terminal device can determine, based on the identifier, whether the transmission success indication in information #A refers to the first data. For example, the network device can indicate whether the data associated with SN+1 was successfully received in the second control information (i.e., the DCI used to schedule the data associated with SN+1); as another example, the network device can indicate whether the data associated with SN+1 was successfully received in the third control information.

[0135] The above are illustrative examples, and the embodiments of this application are not limited thereto. For example, in the above examples, SN can be replaced with SN+i, SN+1 can be replaced with SN+i+1, SN+2 can be replaced with SN+i+2, where i is an integer. As another example, a HARQ process may include more or fewer data. Furthermore, considering that the identifier range may be limited, the identifier can be reused after reaching its maximum value, such as reusing it starting from the minimum value. For example, if the identifier range is 0-255, identifiers 0-255 are used in the first to the 256th packets respectively, and from the 257th packet onwards, identifier 0 is reassigned.

[0136] In the second possible implementation, the terminal device determines whether the first data has been successfully transmitted based on whether the information #A carries an indication (referred to as indication information #2 for distinction).

[0137] For example, if information #A includes first indication information #2 (such as first indication information #2 being NACK, or other content, which is not limited), it indicates that the first data transmission failed; if information #A does not include first indication information #2, it indicates (or by default) that the first data transmission succeeded. Alternatively, it can be understood that if first indication information #2 appears in information #A, it indicates that the first data transmission failed; if first indication information #2 does not appear in information #A, it indicates that the first data transmission succeeded.

[0138] For example, if information #A includes first indication information #2 (e.g., first indication information #2 is ACK, or it may be other content, which is not limited), it indicates that the first data transmission was successful; if information #A does not include first indication information #2, it indicates (or by default) that the first data transmission failed. This can also be understood as follows: if first indication information #2 appears in information #A, it indicates that the first data transmission was successful; if first indication information #2 does not appear in information #A, it indicates that the first data transmission failed.

[0139] The two implementation methods described above are illustrative examples, and the embodiments in this application are not limited thereto.

[0140] In the second possible scenario, information #A represents feedback. Based on this, network devices can directly use feedback information to indicate whether data transmission was successful.

[0141] As an example, message #A indicates whether at least one piece of data associated with M HARQ processes has been successfully transmitted. The M HARQ processes include a first HARQ process, and the at least one piece of data associated with the first HARQ process includes first data. M is an integer greater than or equal to 1. Based on this, when M equals 1, the network device can provide feedback to the terminal device regarding the transmission status of data associated with one HARQ process; when M is greater than 1, the network device can provide feedback to the terminal device regarding the transmission status of data associated with multiple HARQ processes. As an example, message #A can be carried in at least one of the following: DCI, Layer 2 signaling (e.g., MAC signaling, RLC signaling, PDCP signaling, etc.).

[0142] One possible implementation is that message #A indicates whether at least one piece of data associated with each of the M HARQ processes has been successfully transmitted.

[0143] Optionally, information #A may also include HARQ process IDs. For example, information #A may include the HARQ process ID of each of the M HARQ processes; or, information #A may include the HARQ process ID of the first HARQ process among the M HARQ processes, allowing the network device to deduce the HARQ process IDs of the M HARQ processes based on the HARQ process ID of the first HARQ process; or, information #A may include the HARQ process ID of the first HARQ process among the M HARQ processes and the number of HARQ processes (i.e., the value of M), allowing the network device to deduce the HARQ process IDs of the M HARQ processes based on the HARQ process ID of the first HARQ process and the number of HARQ processes.

[0144] Alternatively, message #A may not carry the HARQ process number. The terminal device determines which HARQ process corresponds to each data transmission status indicated by message #A based on predefined or pre-agreed rules. For example, if message #A indicates the transmission status of three data items, the terminal device, based on predefined or pre-agreed rules, defaults to the transmission status of HARQ process 1, HARQ process 2, and HARQ process 3, respectively. For instance, if M=8, the first feedback message corresponds to HARQ process P (i.e., HARQ process number P), the second feedback message corresponds to HARQ process P+1 (i.e., HARQ process number P+1), and so on, with the eighth feedback message corresponding to HARQ process P+7 (i.e., HARQ process number P+7). P can be predefined, such as a fixed value like 0 or 1, or it can be a value configured by the network device for the terminal device through configuration information; no limitation is made here.

[0145] Alternatively, the information #A may also carry an identifier associated with the data of the HARQ process being fed back, indicating that the feedback information is for the data associated with that identifier.

[0146] The above describes implementation method 1, in which the terminal device can determine the data reception status based on the information sent by the network device. The following describes implementation method 2, in which the terminal device can determine the data reception status based on whether it receives feedback from the network device.

[0147] In implementation method 2, if the terminal device does not receive feedback from the network device regarding the first data within a certain period after the first data is sent, the terminal device determines that the first data transmission was successful.

[0148] For example, if the terminal device does not receive feedback on the first data within a preset time period, the terminal device assumes that the first data transmission was successful. If the terminal device receives feedback on the first data within the preset time period, the terminal device determines that the first data transmission failed, or the terminal device can determine whether the first data was successfully transmitted based on the content of the feedback. The preset time period starts after the time the first data was sent, and the duration of the preset time period can be predefined or configured, without limitation.

[0149] In addition, the preset time period can be implemented using a timer. For example, after the terminal device sends the first data, it starts a timer. If the terminal device does not receive feedback on the first data during the timer's operation or before the timer expires, the terminal device assumes that the first data transmission was successful. If the terminal device receives feedback on the first data during the timer's operation or before the timer expires, the terminal device determines that the first data transmission failed, or the terminal device can determine whether the first data transmission was successful based on the content of the feedback.

[0150] The above is an illustrative example, and the embodiments of this application are not limited thereto. For example, if the terminal device does not receive feedback on the first data from the network device within a certain period of time after the first data is sent, the terminal device determines that the first data transmission has failed.

[0151] If the terminal device determines in S520 that the first data transmission has failed, method 500 also includes S530.

[0152] S530: The terminal device determines whether to retransmit the first data. That is, if the first data transmission fails, the terminal device determines whether to retransmit the first data.

[0153] Since the first data may contain data from multiple service channels, when retransmitting the first data, it may only retransmit data from a portion of the service channels. That is, the terminal device can determine whether the data from each service channel needs to be retransmitted separately.

[0154] "Retransmission" can also be called secondary retransmission or Type II retransmission. Specifically, if the first data fails after N HARQ transmissions, the terminal device determines whether to retransmit the first data, i.e., whether to continue transmitting the first data, where N is an integer greater than or equal to 1. Since HARQ retransmission cannot change the content of the transport block, the data contained in the first data cannot be changed during HARQ retransmission. Secondary retransmission or Type II retransmission does not have this restriction because it does not require soft combining during retransmission, and can retransmit a portion of the service channel data.

[0155] See Figure 6 As an example, Figure 6 This is a schematic diagram illustrating data retransmission according to an embodiment of this application. For example... Figure 6 If the data in the first HARQ process fails after one new transmission (i.e., HARQ new transmission) and two retransmissions (i.e., HARQ retransmission), the terminal device can determine whether to retransmit the first data. Furthermore, if the terminal device determines to retransmit the first data, this "retransmission" can be performed at various layers, such as at the MAC layer, or at a higher layer of Layer 2 (such as the RLC layer, PDCP layer, SDAP layer, etc.). The specific implementation of retransmission will be explained in detail later. Additionally, the terminal device's determination to retransmit the first data can be made at the MAC layer or at a higher layer of Layer 2. When performed at a higher layer of Layer 2, the terminal device can send information about the failure of the first data transmission to the higher layer of Layer 2 so that the higher layer of Layer 2 can determine whether to retransmit.

[0156] The terminal device can determine whether to retransmit the first data based on the parameters of the first data. The parameters of the first data, or attributes of the first data, represent attributes or parameters related to the data packets contained in the first data. For example, the parameters of the first data include at least one of the following: the QoS requirements of the QoS stream corresponding to the first data, the QoE information of the first data, and the type of the first data. As mentioned earlier, the first data may contain data from multiple service channels, and data from different service channels may correspond to different attributes or parameters. In this case, a separate judgment can be made for each service channel data. For ease of understanding and explanation, the following detailed description focuses on data from one service channel contained in the first data.

[0157] Option 1: The parameters of the first data include the QoS requirements of the QoS stream corresponding to the first data. In other words, the terminal device can determine whether to retransmit the first data based on the QoS requirements of the QoS stream corresponding to the first data.

[0158] One possible implementation is that the terminal device determines whether to retransmit the first data based on whether the QoS requirements of the QoS stream corresponding to the first data are met. For example, if the QoS requirements of the QoS stream corresponding to the first data are not met, the terminal device retransmits the first data; if the QoS requirements of the QoS stream corresponding to the first data are met, the terminal device does not retransmit the first data. Based on this, the terminal device can determine whether to retransmit the data based on whether the QoS requirements of the failed data transmission are met.

[0159] The QoS stream corresponding to the data can refer to the QoS stream used to transmit that data. For example, when the data is transmitted via a QoS stream, that QoS stream can be referred to as the QoS stream corresponding to the data.

[0160] QoS requirements for a QoS flow refer to the conditions that the QoS parameters (or QoS attributes) corresponding to the QoS flow must meet. QoS parameters can include, but are not limited to: rate, latency, packet loss rate, PDB, priority, reliability, etc. For example, the QoS requirement for a QoS flow might be that the rate in the QoS parameters of the QoS flow must meet 7 megabits per second (Mbps), that is, greater than or equal to 7 Mbps.

[0161] Whether the QoS requirements of a QoS stream are met: This refers to whether the QoS parameters corresponding to the QoS stream meet the QoS requirements, that is, whether the QoS parameters corresponding to the QoS stream meet the QoS requirements in actual communication. For example, QoS requirements include packet loss rate. If the QoS requirement corresponding to a QoS stream is a rate of 7 Mbps, but the rate achieved by the QoS parameters corresponding to the QoS stream in actual transmission is 5 Mbps, then the QoS requirement of the QoS stream can be considered not met. As another example, QoS requirements include packet loss rate. If the QoS requirement corresponding to a QoS stream is less than 10... -6 The packet loss rate is [not specified], but in actual transmission, the packet loss rate achieved by the QoS parameters corresponding to this QoS stream is 10%. -7 If so, then the QoS requirements of the QoS flow can be considered to be met. For another example, QoS requirements include PDB. If the QoS requirement for a QoS flow is 10ms PDB, but in actual transmission, if the buffer time of the first data packet does not exceed 10ms, then it needs to be retransmitted; if it exceeds 10ms, then it does not need to be retransmitted.

[0162] It is understandable that the specific value 10 mentioned above... -6 10 -3 10 -7 This is merely an example and does not limit the scope of protection of the embodiments of this application.

[0163] As mentioned earlier, the terminal device can determine whether to retransmit the first data based on whether the QoS requirements of the QoS stream corresponding to the first data have been met. For simplicity and ease of description, the QoS stream corresponding to the first data will be referred to as QoS stream #A below. An example using packet loss rate will be provided for illustration.

[0164] As an example, the QoS requirements of QoS flow #A include the packet loss rate requirement (or packet loss rate requirement) of QoS flow #A. If the current packet loss rate of QoS flow #A is higher than the packet loss rate requirement of QoS flow #A, the first data is retransmitted; if the current packet loss rate of QoS flow #A is lower than or equal to the packet loss rate requirement of QoS flow #A, the first data is not retransmitted; or, if the current transmission success rate of QoS flow #A is lower than the packet loss rate requirement of QoS flow #A, the first data is retransmitted; if the current packet loss rate of QoS flow #A is higher than or equal to the packet loss rate requirement of QoS flow #A, the first data is not retransmitted.

[0165] For example, suppose the transmission of data #1 of QoS stream #1 and data #2 of QoS stream #2 in the transport block fails, and QoS stream #1 requires a packet loss rate of no more than 10%. -6 QoS flow #2 requires a packet loss rate not to exceed 10%. -3 In other words, the packet loss rate requirement for data #1 is less than or equal to 10%. -6 The packet loss rate requirement for data #2 is less than or equal to 10%. -3 The terminal device can decide whether to retransmit data #1 and data #2 based on whether the current packet loss rates of QoS flow #1 and QoS flow #2 meet the packet loss rate requirements. Assume the terminal device determines that the current packet loss rate of QoS flow #1 is higher than 10%. -6 That is, the current transmission success rate of QoS flow #1 is less than 10%. -6 Therefore, the terminal device determines that the packet loss rate requirement of QoS flow #1 has not been met, and thus decides to continue sending data #1; assuming the terminal device calculates that the current packet loss rate of QoS flow #2 is less than 10%. -3 That is, the current transmission success rate of QoS flow #1 is higher than 10%. -3 Therefore, the terminal device determines that the packet loss rate requirement of QoS flow #2 has been met, and thus determines that there is no need to send data #2 again.

[0166] Here, the current packet loss rate of QoS flow #A represents the actual packet loss rate of QoS flow #A, that is, the packet loss rate of QoS flow #A during actual transmission. Optionally, the current packet loss rate of QoS flow #A is the packet loss rate of QoS flow #A within the first window. The first window, also known as the statistical window, represents the window in which the current packet loss rate is statistically analyzed. Based on this, the terminal device can use the first window to statistically analyze the packet loss rate of QoS flow #A.

[0167] One possible implementation is that the length of the first window is the length of the transmitted T data packets, where T is an integer greater than 1. Based on this, the terminal device can calculate the packet loss rate of QoS flow #A every T data packets. Specifically, the packet loss rate of QoS flow #A (i.e., the current packet loss rate of QoS flow #A) is the ratio of the total number of failed data packets to the total number of transmitted data packets. The specific value of T is not limited, such as T = 10000. The value of T can be determined by the terminal device itself, configured by the network device, or predefined; it is not limited in this respect.

[0168] Another possible implementation is that the length of the first window is a preset duration. Based on this, the terminal device can periodically calculate the packet loss rate of QoS flow #A. Specifically, the packet loss rate of QoS flow #A (i.e., the current packet loss rate of QoS flow #A) is the ratio of the total number of failed data transmissions to the total number of transmitted data within the preset duration. The preset duration can be determined by the terminal device itself, configured by the network device, or predefined; there is no limitation on this.

[0169] Furthermore, the first window can employ a sliding window mechanism. Taking Example 1 above as an example, the first window uses a sliding window mechanism, meaning the range of T data points can change. For instance, before sending T data points, the window contains 1 to T data points; when sending T+1 data points, the window changes to 1 to T+1 data points; when sending T+2 data points, the window changes to 2 to T+2 data points; and so on. In other words, the statistical window can always be calculated by counting backwards T data points from the last data point sent.

[0170] Scheme 1 primarily uses packet loss rate as an example for illustration, but the embodiments in this application are not limited to this. For example, packet loss rate can also be replaced with other QoS parameters, which will not be elaborated here.

[0171] Option 2: The parameters of the first data include the type of the first data. In other words, the terminal device can determine whether to retransmit the first data based on its type.

[0172] The type of the first data can be a business type or a type based on other parameters, such as transmission reliability, importance in the business flow, or whether it can be decoded independently.

[0173] Optionally, if the type of the first data is a first type, the terminal device retransmits the first data; if the type of the first data is a second type, the terminal device does not retransmit the first data.

[0174] The first and second types differ: the first type contains data that needs to be retransmitted, while the second type contains data that does not need to be retransmitted. Whether a piece of data or a type of service belongs to the first or second type can be determined by the terminal device itself, configured by the network device, or predefined; there is no limitation on this.

[0175] As examples, the first and second types include at least the following scenarios.

[0176] One possible scenario is that the first type of data is more important than the second type of data.

[0177] Specifically, within a service flow, the importance of different data may vary. For example, video streams are generally divided into I-frames and P-frames. I-frames can usually be decoded independently, while P-frames require decoding in conjunction with preceding I-frames. Therefore, losing a P-frame generally affects the decoding of the current frame, while losing an I-frame prevents the decoding of all subsequent P-frames that depend on it. Thus, the importance of I-frame data is higher than that of P-frame data. Therefore, if the first data is I-frame data (i.e., data of the first type), the terminal device will retransmit the first data; if the first data is P-frame data (i.e., data of the second type), the terminal device may choose not to retransmit the first data, or the terminal device may further determine whether to retransmit the first data based on the QoS requirements of the QoS flow in Scheme 1 above.

[0178] Another possible scenario is that the first type is associated with the first QoS stream, and the second type is associated with the second QoS stream. The transmission reliability requirements of the first QoS stream meet the first preset condition, and the transmission reliability requirements of the second QoS stream meet the second preset condition.

[0179] The first and second preset conditions are different. For example, the first preset condition is a high reliability requirement. The transmission reliability requirement of the first QoS stream must meet the first preset condition, meaning the transmission reliability requirement of the first QoS stream is a high reliability requirement, such as a packet loss rate requirement of less than 10%. -6 The first condition is that no more than one packet can be lost per million data packets; the second condition is for non-high reliability requirements (such as low reliability requirements, for example, a packet loss rate requirement of less than 10%). -3 The second QoS stream's transmission reliability requirement must meet the second preset condition (meaning no more than one packet can be lost out of every 1,000 data packets). This indicates that the second QoS stream's transmission reliability requirement is not a high reliability requirement (e.g., a low reliability requirement). Based on this, if the QoS stream #A's transmission reliability requirement is a high reliability requirement, the terminal device determines to retransmit the first data; if the QoS stream #A's transmission reliability requirement is not a high reliability requirement, the terminal device determines not to retransmit the first data.

[0180] As mentioned earlier, transmission reliability requirements, or simply reliability requirements, can be characterized by the QoS parameters (or QoS information, QoS requirements) of the data. For example, if the packet loss rate requirement is less than or equal to a first threshold, it indicates that the data transmission reliability requirement is high reliability; if the packet loss rate requirement is greater than or equal to a second threshold, it indicates that the data transmission reliability requirement is not high reliability. The first threshold is greater than the second threshold. The thresholds involved in the embodiments of this application (such as the first threshold, the second threshold, and the thresholds described below) can be predefined thresholds, configured by the network device for the terminal device, or preset within the terminal device, without restriction.

[0181] The above is an illustrative example, and the embodiments of this application are not limited thereto. As an example, reliability requirements can also be characterized by other parameters such as the service type of the data. For example, the transmission reliability requirement for Transmission Control Protocol (TCP) type services is a high reliability requirement, while the transmission reliability requirement for User Datagram Protocol (UDP) type services is a non-high reliability requirement.

[0182] Option 3: The parameters of the first data include the QoE information of the first data. In other words, the terminal device can determine whether to retransmit the first data based on the QoE information of the first data.

[0183] QoE can be used to measure the subjective satisfaction of terminal devices with network services, rather than just technical indicators (such as QoS). As an example, factors affecting QoE include, but are not limited to: application layer quality (such as video clarity, voice fluency, game latency, etc.), QoS parameters (such as latency, jitter, packet loss rate, throughput, etc.), terminal device performance (such as the processing power of the terminal device), and environmental factors (such as network congestion, signal strength, etc.).

[0184] Terminal devices can determine whether packet loss has occurred based on the impact of dropped data on the service's QoE experience. For example, if the impact of dropping a current packet on QoE is small, it is dropped, meaning the data is not retransmitted; if the impact of dropping a current packet on QoE is large, it is not dropped, meaning the data is retransmitted until successful. For instance, during gameplay, in dynamic scenes (such as fast-moving scenes), because higher transmission rates are required, packet loss has a significant impact on QoE, causing users to experience lag; while in static scenes, because lower transmission rates are required, the impact of dropping a current packet on QoE is small, and the user's perception is not noticeable.

[0185] The methods for assessing the impact on QoE are not limited in the embodiments of this application. For example, it can be calculated based on a QoE algorithm or inferred based on a model (such as an AI model).

[0186] The above schemes can also be used in combination. For example, the parameters of the first data include the type of the first data and the QoS requirements of the corresponding QoS flow (i.e., QoS flow #A). In this case, if the type of the first data is a first service type, it is determined whether to retransmit the first data based on the QoS requirements of QoS flow #A; or, if the type of the first data is a second service type, and the PDB in QoS flow #A has not timed out, it is determined whether to retransmit the first data based on the QoS requirements of QoS flow #A; or, if the PDB in QoS flow #A times out, it is determined not to retransmit the first data.

[0187] The first service type and the second service type are different. The first service type can be a time-insensitive service; therefore, regardless of whether the PDB times out, the terminal device can determine whether to retransmit the first data based on the QoS requirements of QoS flow #A. The second service type can be a time-sensitive service; therefore, if the PDB has not timed out, the terminal device can determine whether to retransmit the first data based on the QoS requirements of QoS flow #A; if the PDB times out, the terminal device can directly determine not to retransmit the first data.

[0188] The above describes the relevant schemes for the terminal device to determine whether to retransmit the first data when the first data transmission fails. The following describes the retransmission scheme for the first data when the terminal device determines to retransmit the first data.

[0189] Optionally, method 500 further includes: if the terminal device determines that it needs to retransmit the first data, the terminal device continues to send the first data. Two implementation methods are described below.

[0190] The first possible implementation is MAC layer retransmission.

[0191] As mentioned above, the naming of the layers is merely an example, and the embodiments of this application are not limited thereto. Any protocol layer that can implement the same or similar functions as the MAC layer in a future communication system is applicable to the embodiments of this application. The MAC layer is used as an example for illustration below.

[0192] Specifically, the terminal device sends third data at the MAC layer, which is derived from the first data. For example, the third data is obtained by processing the first data based on authorization information. This authorization information can be used to transmit lost packet data; in other words, it can be used to schedule lost packet data, or it can be a new transmission authorization. As an example, the network device sends this authorization information to the terminal device. Specifically, the terminal device receives a configured grant from the network device, which configures a series of available authorizations for the terminal device. The terminal device can use one of these available authorizations as its authorization. Based on this, the terminal device can retransmit previously failed data through the MAC layer, either by retransmitting the previously failed data using HARQ new transmission scheduling, without merging it with the previous HARQ transmission.

[0193] Optionally, the third data is segmented or re-segmented from the service data units (SDUs) of the first data (such as some or all SDUs), and / or, the third data is obtained by concatenating other SDUs from the SDUs of the first data (such as some or all SDUs). Based on this, data that fails to be transmitted can be (re)segmented and / or re-concatenated.

[0194] The concepts of first data and SDU can be found in the descriptions within the protocol. Taking TB as the first data, TB and SDU are two concepts in the data encapsulation and transmission process. Specifically, TB can be understood as a transmission unit for horizontal transmission between the MAC layer and the physical layer, while SDU can serve as a vertical transmission unit for the protocol layer (or protocol stack). For example, for downlink transmission, the MAC layer receives a TB as a MAC PDU; for uplink transmission, the MAC layer can concatenate SDUs from the upper layer to obtain a MAC PDU and send it as a TB to the physical layer for processing. It is understood that the names of SDU and TB are not limited in this application embodiment. For example, any data unit structure with the same or equivalent function as SDU / TB defined in any future communication protocol is also applicable to this application embodiment.

[0195] by Figure 6 For example, Figure 6As shown, assuming the first data fails after multiple HARQ transmissions, such as after new transmission (or initial transmission) and retransmission, the terminal device can determine whether to retransmit based on the parameters of the first data. As an example, the network device can include an indication in the new transmission schedule to indicate that the previous round of data (i.e., the first data) transmission failed; this can be referred to in the previous description and will not be repeated here. Assuming the first data transmission fails, and the first data includes SDU1, SDU2, SDU3, and SDU4, the terminal device determines that SDU1 and SDU2 need to be retransmitted based on their parameters. If the actual packet loss rate of the QoS streams corresponding to SDU1 and SDU2 is higher than the packet loss rate requirement, the terminal device determines that SDU1 and SDU2 need to be retransmitted. The terminal device determines that SDU3 and SDU4 do not need to be retransmitted based on their parameters. This is if the actual packet loss rate of the QoS flows corresponding to SDU3 and SDU4 is lower than the packet loss rate requirement, or if the PDB of SDU3 and SDU4 times out and SDU3 and SDU4 belong to the second service type. Therefore, the terminal device determines that SDU3 and SDU4 do not need to be retransmitted. Based on this, the terminal device can retransmit SDU1 and SDU2. Furthermore, if an SDU cannot be completely placed in a single MACPDU, the SDU can be segmented before placement.

[0196] Optionally, the third data includes a portion of the first data. For example, the first data can be re-segmented to obtain multiple SDUs, and then a portion of those SDUs can be sent; or, for another example, the first data can be re-segmented to obtain multiple SDUs, and then a portion of those SDUs can be reassembled and sent. Based on this, if data is not successfully received, the terminal device can continue to send a portion of the data to the network device, thus reducing transmission resources.

[0197] One possible implementation is that the third data includes the data obtained after removing data from the first data that does not require high reliability; in other words, the third data does not include data from the first data that does not require high reliability. Based on this, if data is not successfully received, the terminal device can remove the parts with low reliability requirements and then send the remaining parts to the network device; that is, the terminal device can send the parts with high reliability requirements to the network device.

[0198] The second possible implementation is layer 2 higher-level retransmission. In this case, the terminal device in S530 can also determine whether to retransmit the first data at layer 2 higher level. That is, the terminal device makes the retransmission judgment at layer 2 higher level. For the specific method of retransmission judgment, please refer to the relevant description in S530 above.

[0199] Specifically, the terminal device sends third data at layer 2 higher level, which is obtained based on the layer 2 higher level data contained in the first data.

[0200] As an example, Layer 2 higher layers include at least one of the following: RLC layer, PDCP layer, and SDAP layer. As mentioned earlier, the naming of layers, such as RLC layer, PDCP layer, and SDAP layer, is merely illustrative, and the embodiments of this application are not limited thereto. Taking the RLC layer as an example, as mentioned earlier, any protocol layer that can implement the same or similar functions as the RLC layer in a future communication system is applicable to the embodiments of this application. For ease of understanding, the RLC layer will be used as an example for illustration below.

[0201] For example, the MAC layer of the terminal device transmits information about which RLCPDUs are associated with the lost packets to the RLC layer. The terminal device then makes a determination at the RLC layer and retransmits the corresponding packets. Existing mechanisms can be referenced for RLC layer retransmission; no specific limitations are imposed.

[0202] The above mainly introduced the relevant schemes for the terminal device to determine whether to retransmit (i.e., secondary retransmission) the data when it fails after at least one HARQ transmission. The following section, in conjunction with Method 700, introduces the relevant scheme for the terminal device to indicate to the network device in advance whether to perform HARQ retransmission.

[0203] See Figure 7 As an example, Figure 7 This is a schematic diagram of a communication method 700 provided in an embodiment of this application. Figure 7 The method 700 shown may include the following steps.

[0204] In S710, the terminal device sends the first data, and correspondingly, the network device receives the first data.

[0205] The S710 is similar to the S510, so it will not be described in detail here.

[0206] S720, the terminal device sends an indication message, which is used to determine whether to retransmit the first data.

[0207] The indication information is used to determine whether to retransmit the first data. Specifically, the indication information is used to determine whether the first data should be retransmitted using HARQ.

[0208] Among them, the first data and indication information include at least the following implementation methods.

[0209] In one possible implementation, the time-domain resources of the first data are the same as those of the indication information. As an example, the indication information can be carried in Layer 2 signaling. Based on this, the terminal device can send the first data and the indication information simultaneously. This allows the network device to determine which data the indication information pertains to, and thus, whether to retransmit which data based on the indication information. As an example, the indication information and the first data can be transmitted using different data blocks.

[0210] A second possible implementation involves carrying the first data and indication information on the same channel. As an example, the indication information could be carried in uplink control information (UCI). Based on this, the first data and indication information can reuse the same channel; for instance, the indication information could be carried in the UCI, and the UCI and the first data could reuse the PUSCH.

[0211] A third possible implementation involves carrying the first data and indication information within the same data block (TB). As an example, the indication information could be carried within Layer 2 signaling. Based on this, the first data and indication information can be multiplexed and transmitted within a single TB, allowing the network device to determine which data the indication information pertains to, and thus, whether to retransmit that data. Alternatively, the indication information and the first data could be transmitted using different data blocks.

[0212] The above is an example illustration. The embodiments of this application are not limited to this. As long as the implementation method that enables the network device to determine the relationship between the indication information and the data, that is, the implementation method that enables the network device to determine which data the indication information is for, is applicable to the embodiments of this application.

[0213] Optionally, the instruction information may include at least the following implementation methods.

[0214] The first possible implementation is to indicate the maximum number of times the first data can be transmitted.

[0215] The indication information indicates the maximum number of times the first data can be transmitted, or it can indicate the maximum number of times the terminal device suggests (or recommends) the transmission.

[0216] The maximum number of transmissions of the first data can be either the maximum number of retransmissions of the first data plus 1, or simply the maximum number of retransmissions of the first data; there is no limitation on this. Assume the indication information specifies the maximum number of transmissions of the first data as S, where S is an integer greater than or equal to 1.

[0217] For the terminal device, there is no limitation on the method by which the terminal device determines S. Optionally, the terminal device determines S based on the parameters of the first data, wherein the parameters of the first data include at least one of the following: the QoS requirements of the QoS stream corresponding to the first data, the volume QoE information of the first data, and the type of the first data.

[0218] In one example, the terminal device calculates S based on the remaining time of the first data. For instance, assuming the remaining valid time of the first data is 20ms and the HARQ round-trip time (RTT) is 5ms, the terminal device determines that after the current transmission is completed, there are still 4 retransmission times. Therefore, the terminal device can determine the number of transmissions as 5 (i.e., 4 retransmissions + 1 initial transmission), or the terminal device can determine the number of transmissions as 4 (i.e., the number of subsequent retransmissions is 4).

[0219] In another example, the terminal device determines S based on QoS parameters (i.e., the QoS requirements of the QoS stream corresponding to the first data). For instance, if the packet loss rate of the QoS stream corresponding to the first data is very low, such as below the packet loss rate requirement, then the value of S can be smaller; if the packet loss rate of the QoS stream corresponding to the first data is very high, such as above the packet loss rate requirement, then the value of S can be larger.

[0220] The above is an illustrative example, and the embodiments of this application are not limited thereto. For example, the terminal device may also determine S according to the type of the first data. If the first data is data of higher importance, the value of S can be larger; if the first data is data of lower importance, the value of S can be smaller.

[0221] For network devices, the network device can schedule / receive the first data according to the instruction S from the terminal device. Taking S as the maximum number of retransmissions as an example, if the network device fails to receive the first data, it can schedule S' retransmissions of the first data, where S' is less than or equal to S. Specifically, after receiving this instruction, if the network device successfully receives the first data, it ends the transmission of the first data; if it fails to receive the first data, the network device can determine whether to continue scheduling retransmissions based on the instruction. For example, if the maximum number of transmissions indicated by the terminal device is 2, and the network device has already scheduled 1 new transmission and 1 retransmission but still has not received the data correctly, it can stop scheduling retransmissions and instead schedule new transmissions.

[0222] The second possible implementation is to indicate the time information of the first data.

[0223] The indication information indicates the time information of the first data, or it can indicate the time information suggested (or recommended) by the terminal device.

[0224] The time information, also known as timeliness information, indicates the expiration or validity period of the first data. This time information can be used by network devices to determine the expiration or validity period of the first data (such as a portion of the first data, e.g., the most urgent portion) or all of the data. The expiration or validity period refers to the point in time when the data arrives in the buffer and the waiting time exceeds the data's PDB (Program Data Block). For example, if the data arrives in the buffer at 2:00 and the PDB is 1 second (i.e., the time information indicated by the indication is 1 second), then if the data is not successfully sent by 2:01, it is invalid; it is valid until then. The expiration or validity period can be implemented using a timer. Specifically, after the data arrives in the buffer, a timer (or a discard timer) can be started and an initial value set. When the data is sent, the expiration or validity period is the remaining time of this timer. The initial value can be configured by the network device or determined by the terminal device itself, and this initial value can be less than or equal to the data's PDB.

[0225] For example, a terminal device can determine time information based on the PDB of the data.

[0226] For network devices, upon receiving this indication, if they successfully receive the first data, they terminate the transmission of the first data; if they fail to receive the first data, the network device can determine whether to continue scheduling retransmission based on the indication. For example, if the terminal device indicates a time of 10ms, the network device will determine whether to schedule a HARQ retransmission of the data within 10ms if there is no opportunity to schedule a HARQ retransmission of the data. Instead, it will schedule a new HARQ transmission.

[0227] The third possible implementation is to use an instruction message to indicate whether to retransmit the first data.

[0228] The instruction indicating whether to retransmit the first data can be replaced with: the instruction indicating whether the first data is expired, such as already expired or about to expire. Specifically, the instruction indicating to retransmit the first data can be replaced with: the instruction indicating the first data is not expired; the instruction indicating not to retransmit the first data can be replaced with: the instruction indicating the first data is expired. Based on this, the terminal device can directly indicate to the network device whether to retransmit the first data.

[0229] Specifically, after receiving control information, the terminal device sends data to the network device based on the control information. The terminal device can determine whether some or all of the data is about to expire or has already expired. If some or all of the data is about to expire or has already expired, the terminal device sends an indication message to the network device, indicating that HARQ retransmission scheduling is not required for the data. The control information, also known as uplink scheduling, such as DCI, can be used to schedule data, such as new transmission scheduling or retransmission scheduling.

[0230] For terminal devices, as an example, they can determine whether data is invalid based on the data's PDB (Program Data Block). For instance, after data arrives in the buffer, a timer (or discard timer) can be started. If the timer times out or the remaining time is less than or equal to a threshold, the terminal device determines that the data is invalid. The threshold can be configured by the network device, determined by the terminal device itself, or predefined; it is not limited to these parameters.

[0231] The above is an illustrative example, and the embodiments of this application are not limited thereto. For example, the terminal device can also determine whether the data is invalid based on the QoS parameters of the data. For example, if the packet loss rate of the QoS stream corresponding to the current data is very low, such as below the packet loss rate requirement, the terminal device can instruct the network device not to retransmit the first data, because even if it is not successfully received, the current packet loss rate still meets the packet loss rate requirement of the service.

[0232] For network devices, upon receiving this indication information, if they successfully receive the first data, they terminate the transmission of the first data; if they fail to receive the first data, the network device can determine whether to continue scheduling retransmission based on the indication information. For example, if the indication information indicates retransmission of the first data, the network device schedules a HARQ retransmission of the data; if the indication information indicates not to retransmit the first data, the network device will not schedule a HARQ retransmission of the data, but will instead schedule a HARQ new transmission.

[0233] The above introduced three implementation methods; below, we will combine them with... Figure 8 Please provide an explanation.

[0234] See Figure 8 , Figure 8 This is a schematic diagram illustrating data transmission applicable to embodiments of this application. For example... Figure 8As shown, after receiving control information (or uplink scheduling, such as DCI), the terminal device sends data to the network device. For example, the terminal device can send indication information (such as UCI) to the network device, which can indicate the maximum number of transmissions or time information. After receiving the data and indication information, if the network device successfully receives the data, it terminates the data transmission. If it fails to receive the data, the network device can determine whether to continue scheduling retransmission based on the indication information. Assuming the network device determines to continue scheduling retransmission based on the indication information, the terminal device continues to send the data based on the network device's retransmission schedule. Furthermore, the terminal device can also determine whether to perform the next HARO retransmission, such as whether to terminate HARQ retransmission. If the terminal device determines that HARQ retransmission is unnecessary, such as due to PDB timeout or data expiration, the terminal device can instruct the network device to terminate HARO retransmission. In addition, when retransmitting data, the terminal device can (re)segment and / or reconcatenate the failed data before retransmission. For details, please refer to the relevant description in method 500, which will not be elaborated here.

[0235] It is understood that methods 700 and 500 can be used individually or in combination. When used in combination, the terminal device can first indicate to the network device whether to perform HARQ retransmission based on the method described in method 700; then, the terminal device can determine whether to perform secondary retransmission based on the method in method 500.

[0236] The above, combined with Figures 5 to 8 The methods provided in the embodiments of this application are described in detail below. Figures 9 to 11 The apparatus provided in the embodiments of this application is described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0237] See Figure 9 As an example, Figure 9 This is a schematic diagram of a communication device 900 provided in an embodiment of this application. The communication device 900 includes a transceiver unit 910 and a processing unit 920. The transceiver unit 910 can be used to implement corresponding communication functions. The transceiver unit 910 can also be referred to as a communication interface or a communication unit. The processing unit 920 can be used to perform processing, such as determining whether data has been successfully received, or determining whether to retransmit data.

[0238] Optionally, the device 900 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 920 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiments.

[0239] In a first possible design, the device 900 can be the terminal device in the foregoing embodiments, which can implement the steps or processes executed by the terminal corresponding to those in the above method embodiments. Specifically, the transceiver unit 910 can be used to perform operations related to the transmission and reception of the terminal in the above method embodiments (such as sending and / or receiving data or messages), and the processing unit 920 can be used to perform processing-related operations of the terminal in the above method embodiments, or operations other than transmission and reception (such as operations other than sending and / or receiving data or messages).

[0240] One possible implementation is a transceiver unit 910 for sending first data; and a processing unit 920 for determining whether to retransmit the first data based on the parameters of the first data in the event of a failure in the transmission of the first data, wherein the parameters of the first data include at least one of the following: the QoS requirements of the QoS stream corresponding to the first data, the Quality of Experience (QoE) information of the first data, and the type of the first data.

[0241] Optionally, the failure of the first data transmission includes: the first data fails after being transmitted N times via Hybrid Automatic Repeat Request (HARQ), where N is an integer greater than or equal to 1.

[0242] Optionally, the parameters of the first data include the QoS requirements of the QoS stream corresponding to the first data. The processing unit 920 is used to determine whether to retransmit the first data based on the parameters of the first data, including: the processing unit 920 is used to determine to retransmit the first data if the QoS requirements of the QoS stream corresponding to the first data are not met; or, if the QoS requirements of the QoS stream corresponding to the first data are met, determine not to retransmit the first data.

[0243] Optionally, the QoS requirements of the QoS stream corresponding to the first data include the packet loss rate requirement of the QoS stream corresponding to the first data. The processing unit 920 is used to determine to retransmit the first data when the QoS requirements of the QoS stream corresponding to the first data are not met, including: the processing unit 920 is used to determine to retransmit the first data when the current packet loss rate of the QoS stream corresponding to the first data is higher than the packet loss rate requirement of the QoS stream corresponding to the first data.

[0244] Optionally, the current packet loss rate of the QoS stream corresponding to the first data is the packet loss rate of the QoS stream corresponding to the first data within the first window, wherein the length of the first window is: the length of transmitting T data, or a preset duration, where T is an integer greater than 1.

[0245] Optionally, the parameters of the first data include the QoS requirements of the QoS stream corresponding to the first data and the type of the first data. The processing unit 920 is used to determine whether to retransmit the first data based on the parameters of the first data, including: if the type of the first data is a first service type, the processing unit 920 is used to determine whether to retransmit the first data based on the QoS requirements of the QoS stream corresponding to the first data; or, if the type of the first data is a second service type, when the data packet delay budget (PDB) in the QoS stream corresponding to the first data has not expired, the processing unit 920 is used to determine whether to retransmit the first data based on the QoS requirements of the QoS stream corresponding to the first data; or, when the PDB in the QoS stream corresponding to the first data has expired, the processing unit 920 is used to determine not to retransmit the first data.

[0246] Optionally, the parameters of the first data include the type of the first data. The processing unit 920 is used to determine whether to retransmit the first data based on the parameters of the first data, including: the processing unit 920 is used to determine to retransmit the first data if the type of the first data is a first type; or, if the type of the first data is a second type, determine not to retransmit the first data.

[0247] Optionally, the first type and the second type satisfy at least one of the following: the importance of the data in the first type is higher than that of the data in the second type; the first type is associated with the first QoS stream, and the second type is associated with the second QoS stream; wherein the transmission reliability requirement of the first QoS stream satisfies the first preset condition, and the transmission reliability requirement of the second QoS stream satisfies the second preset condition.

[0248] Optionally, the transceiver unit 910 is used to receive indication information indicating that the first data transmission failed; or, if no indication of successful first data transmission is received within a preset time period, the processing unit 920 is used to determine that the first data transmission failed.

[0249] Optionally, the transceiver unit 910 is configured to send first data, including: the transceiver unit 910 is configured to send the first data through a first HARQ process; the indication information indicates that the first data transmission failed, including: the indication information indicates whether at least one data associated with M HARQ processes was successfully transmitted, the M HARQ processes including the first HARQ process, and at least one data associated with the first HARQ process including the first data; or, the indication information is further configured to schedule second data associated with the first HARQ process.

[0250] Optionally, if the indication information is also used to schedule the second data associated with the first HARQ process, the transceiver unit 910 is also used to send the second data through the first HARQ process based on the indication information.

[0251] Optionally, the second data includes the first data or a portion of the first data; or, the second data is newly transmitted data.

[0252] Optionally, if the retransmission of the first data is determined based on the parameters of the first data, the transceiver unit 910 is further configured to send third data at the Media Access Control (MAC) layer, the third data being obtained based on the first data; or, send third data at the Layer 2 higher layer, the third data being obtained based on the Layer 2 higher layer data contained in the first data.

[0253] Another possible implementation is that the transceiver unit 910 is used to send first data; the transceiver unit 910 is also used to send indication information, which is used to determine whether to retransmit the first data; wherein, the indication information indicates the maximum number of transmissions of the first data and / or time information, or, the indication information indicates whether to retransmit the first data; wherein, the maximum number of transmissions is the maximum number of retransmissions, or, the maximum number of transmissions is the maximum number of retransmissions + 1; the time information indicates the expiration time of the first data.

[0254] Optionally, the first data and the indication information satisfy at least one of the following: the time domain resources of the first data and the time domain resources of the indication information are the same; the first data and the indication information are carried on the same channel; the first data and the indication information are carried on the same transport block.

[0255] Optionally, the processing unit 920 is configured to determine indication information based on the parameters of the first data, wherein the parameters of the first data include at least one of the following: the QoS requirements of the QoS stream corresponding to the first data, the Quality of Experience (QoE) information of the first data, and the type of the first data.

[0256] In a second possible design, the device 900 can be a network device as described in the foregoing embodiments. This device 900 can implement the steps or processes performed by the network device corresponding to those described in the method embodiments above. Specifically, the transceiver unit 910 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the network device described in the method embodiments above, and the processing unit 920 can be used to perform processing-related operations of the network device described in the method embodiments above, or operations other than transceiver operations (such as operations other than sending and / or receiving data or messages).

[0257] In one possible implementation, the transceiver unit 910 is used to receive first data; the transceiver unit 910 is also used to receive indication information, the indication information being used to determine whether to retransmit the first data; wherein, the indication information indicates the maximum number of transmissions of the first data and / or time information, or, the indication information indicates whether to retransmit the first data; wherein, the maximum number of transmissions is the maximum number of retransmissions, or, the maximum number of transmissions is the maximum number of retransmissions + 1; the time information indicates the expiration time of the first data.

[0258] Optionally, the first data and the indication information satisfy at least one of the following: the time domain resources of the first data and the time domain resources of the indication information are the same; the first data and the indication information are carried on the same channel; the first data and the indication information are carried on the same transport block.

[0259] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0260] It should also be understood that the device 900 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 900 can specifically be the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the communication device in the above method embodiments; to avoid repetition, these will not be described again here.

[0261] The apparatus 900 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device (such as a terminal device or a network device) in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by a processor, respectively executing the transceiver operations and related processing operations in each method embodiment.

[0262] In addition, the transceiver unit 910 described above can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0263] It should be pointed out that, Figure 9 The device mentioned can be the communication equipment (such as a terminal device or a network device) in the foregoing embodiments, or it can be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0264] See Figure 10 As an example, Figure 10This is a schematic diagram of another communication device 1000 provided in an embodiment of this application. The device 1000 includes a processor 1010, which is coupled to a memory 1020. The memory 1020 is used to store computer programs or instructions and / or data. The processor 1010 is used to execute the computer programs or instructions stored in the memory 1020, or to read the data stored in the memory 1020, in order to execute the methods in the above method embodiments.

[0265] Optionally, there may be one or more processors 1010.

[0266] Optionally, the memory 1020 may be one or more.

[0267] Alternatively, the memory 1020 can be integrated with the processor 1010, or it can be set separately.

[0268] Optionally, such as Figure 10 As shown, the device 1000 also includes a transceiver 1030, which is used for receiving and / or transmitting signals. For example, the processor 1010 is used to control the transceiver 1030 to receive and / or transmit signals.

[0269] As an example, processor 1010 may have Figure 9 The processing unit 920 shown has the function of a storage unit, the memory 1020 can have the function of a storage unit, and the transceiver 1030 can have the function of a storage unit. Figure 9 The function of the transceiver unit 910 shown is illustrated.

[0270] As one option, the device 1000 is used to implement the operations performed by a communication device (such as a terminal device or a network device) in the various method embodiments described above.

[0271] For example, processor 1010 is used to execute computer programs or instructions stored in memory 1020 to implement the relevant operations of the communication device in the various method embodiments described above.

[0272] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0273] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0274] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0275] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0276] See Figure 11 As an example, Figure 11 This is a schematic diagram of a chip system 1100 provided in an embodiment of this application. The chip system 1100 (or may also be referred to as a processing system) includes logic circuitry 1110 and an input / output interface 1120.

[0277] The logic circuit 1110 can be a processing circuit in the chip system 1100. The logic circuit 1110 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1100 to implement the methods and functions of the embodiments of this application. The input / output interface 1120 can be an input / output circuit in the chip system 1100, outputting processed information from the chip system 1100, or inputting data or signaling information to be processed into the chip system 1100 for processing.

[0278] As one approach, the chip system 1100 is used to implement operations performed by communication devices (such as terminal devices or network devices) in the various method embodiments described above.

[0279] For example, logic circuit 1110 is used to implement processing-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments; input / output interface 1120 is used to implement sending and / or receiving-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments.

[0280] This application also provides a computer-readable storage medium storing a computer program or instructions for implementing the methods executed by a communication device (such as a terminal device or a network device) in the above-described method embodiments. For example, when the computer program or instructions are run on the communication device, they cause the communication device (such as a terminal device or a network device) to execute the above-described methods (such as method 500 or method 700).

[0281] This application also provides a computer program product comprising instructions that, when executed by a computer, implement the methods described above as performed by a communication device (such as a terminal device or a network device). For example, when the computer program or instructions are run on the communication device, the communication device (such as a terminal device or a network device) performs the methods described above (such as method 500 or method 700).

[0282] This application also provides a communication system, which includes the terminals and / or network devices described in the above embodiments. For example, the system includes... Figure 5 The terminal device and network device in the embodiment. For example, the system includes... Figure 7 The terminal device and network device in the embodiments.

[0283] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0284] In the several embodiments provided in this application, it should be understood that the disclosed apparatus 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 mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0285] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

[0286] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Send the first data; In the event of failure of the first data transmission, a determination is made as to whether to retransmit the first data based on the parameters of the first data, wherein the parameters of the first data include at least one of the following: the QoS requirements of the QoS stream corresponding to the first data, the Quality of Experience (QoE) information of the first data, and the type of the first data.

2. The method according to claim 1, characterized in that, The failure of the first data transmission includes: the first data failed after being transmitted N times via HARQ (Hybrid Automatic Repeat Request), where N is an integer greater than or equal to 1.

3. The method according to claim 1 or 2, characterized in that, The parameters of the first data include the QoS requirements of the QoS stream corresponding to the first data. The step of determining whether to retransmit the first data based on the parameters of the first data includes: If the QoS requirements of the QoS stream corresponding to the first data are not met, retransmit the first data; or, If the QoS requirements of the QoS stream corresponding to the first data are met, the first data will not be retransmitted.

4. The method according to claim 3, characterized in that, The QoS requirements of the QoS stream corresponding to the first data include the packet loss rate requirement of the QoS stream corresponding to the first data. If the QoS requirements of the QoS stream corresponding to the first data are not met, the first data is retransmitted, including: If the current packet loss rate of the QoS stream corresponding to the first data is higher than the packet loss rate requirement of the QoS stream corresponding to the first data, the first data shall be retransmitted.

5. The method according to claim 4, characterized in that, The current packet loss rate of the QoS stream corresponding to the first data is the packet loss rate of the QoS stream corresponding to the first data within the first window, wherein the length of the first window is: the length of transmitting T data, or a preset duration, where T is an integer greater than 1.

6. The method according to any one of claims 1 to 5, characterized in that, The parameters of the first data include the QoS requirements of the QoS stream corresponding to the first data and the type of the first data. The step of determining whether to retransmit the first data based on the parameters of the first data includes: If the type of the first data is a first service type, determine whether to retransmit the first data based on the QoS requirements of the QoS stream corresponding to the first data; or, When the type of the first data is the second service type, if the packet delay budget (PDB) in the QoS stream corresponding to the first data has not expired, it is determined whether to retransmit the first data according to the QoS requirements of the QoS stream corresponding to the first data; or, if the PDB in the QoS stream corresponding to the first data expires, it is determined not to retransmit the first data.

7. The method according to any one of claims 1 to 6, characterized in that, The parameters of the first data include the type of the first data, and determining whether to retransmit the first data based on the parameters of the first data includes: If the type of the first data is type one, retransmit the first data; or... If the type of the first data is the second type, it is determined that the first data will not be retransmitted.

8. The method according to claim 7, characterized in that, The first type and the second type satisfy at least one of the following: The first type of data is more important than the second type of data; The first type is associated with a first QoS flow, and the second type is associated with a second QoS flow; The transmission reliability requirement of the first QoS stream meets the first preset condition, and the transmission reliability requirement of the second QoS stream meets the second preset condition.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Receive an indication message indicating that the first data transmission failed; or... If no indication of successful data transmission is received within a preset time period, the first data transmission is determined to have failed.

10. The method according to claim 9, characterized in that, The sending of the first data includes: Send the first data through the first HARQ process; The indication information indicating that the first data transmission failed includes: the indication information indicating whether at least one piece of data associated with M HARQ processes was successfully transmitted, wherein the M HARQ processes include the first HARQ process, and the at least one piece of data associated with the first HARQ process includes the first data; or... The instruction information is also used to schedule the second data associated with the first HARQ process.

11. The method of claim 10, wherein if the indication information is further used to schedule second data associated with the first HARQ process, the method further includes: Based on the indicated information, the second data is sent through the first HARQ process.

12. The method according to claim 11, characterized in that, The second data includes the first data or a portion of the first data; or, The second data is newly transmitted data.

13. The method according to any one of claims 1 to 12, characterized in that, When retransmission of the first data is determined based on the parameters of the first data, the method further includes: The third data is sent at the Media Access Control (MAC) layer, the third data being derived from the first data; or... The third data is sent at the higher layer 2, and the third data is obtained based on the higher layer 2 data contained in the first data.

14. A communication method, characterized in that, include: Send the first data; Send an indication message, the indication message being used to determine whether to retransmit the first data; Wherein, the indication information indicates the maximum number of transmissions and / or time information of the first data, or the indication information indicates whether to retransmit the first data; Wherein, the maximum number of transmissions is the maximum number of retransmissions, or the maximum number of transmissions is the maximum number of retransmissions + 1; the time information indicates the expiration time of the first data.

15. The method according to claim 14, characterized in that, The first data and the indication information satisfy at least one of the following: The time-domain resources of the first data are the same as the time-domain resources of the indication information; The first data and the indication information are carried on the same channel; The first data and the indication information are carried in the same transport block.

16. The method according to claim 14 or 15, characterized in that, The method further includes: The indication information is determined based on the parameters of the first data, wherein the parameters of the first data include at least one of the following: the QoS requirements of the QoS stream corresponding to the first data, the Quality of Experience (QoE) information of the first data, and the type of the first data.

17. A communication method, characterized in that, include: Receive the first data; Receive indication information, the indication information being used to determine whether to retransmit the first data; Wherein, the indication information indicates the maximum number of transmissions and / or time information of the first data, or the indication information indicates whether to retransmit the first data; Wherein, the maximum number of transmissions is the maximum number of retransmissions, or the maximum number of transmissions is the maximum number of retransmissions + 1; the time information indicates the expiration time of the first data.

18. The method according to claim 17, characterized in that, The first data and the indication information satisfy at least one of the following: The time-domain resources of the first data are the same as the time-domain resources of the indication information; The first data and the indication information are carried on the same channel; The first data and the indication information are carried in the same transport block.

19. A communication device, characterized in that, It includes modules or units for performing the method of any one of claims 1 to 16; or, it includes modules or units for performing the method of claim 17 or 18.

20. A communication device, characterized in that, The device includes a processor configured to cause the communication device to perform the method of any one of claims 1 to 16, or configured to cause the communication device to perform the method of claim 17 or 18.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 16, or cause the communication device to perform the method as described in claim 17 or 18.

22. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as claimed in any one of claims 1 to 16, or cause the communication device to perform the method as claimed in claim 17 or 18.

Images