Data receiving method, device, terminal and readable storage medium

Abstract

The present application discloses a data receiving method, device, terminal and readable storage medium. The method comprises: when the first data is decoded successfully, the terminal stops receiving target data; wherein the target data is the first data retransmitted by the network device; the first data is transmitted through a first hybrid automatic repeat request HARQ process, and the uplink feedback of the first HARQ process is disabled. The embodiment of the present application reduces the power consumption of the terminal.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and in particular relates to a data receiving method, device, terminal and readable storage medium. Background Art

[0002] With the development of communication technology, in the communication mechanism, when a terminal receives a downlink schedule, it must receive the downlink data corresponding to the downlink schedule and provide uplink feedback to improve transmission reliability. However, in non-terrestrial networks (NTN) scenarios, network equipment may configure the terminal to disable uplink feedback for downlink data and use methods such as blind scheduling to transmit downlink data. In this case, the network equipment may schedule the terminal to receive the same data at multiple resource locations. This requires the terminal to receive the same data multiple times, resulting in a large power loss for the terminal. Summary of the Invention

[0003] The embodiments of the present application provide a data receiving method, device, terminal and readable storage medium, which can solve the problem that a network device schedules a terminal to receive the same data at multiple resource locations, resulting in large power consumption of the terminal.

[0004] In a first aspect, a data receiving method is provided, comprising:

[0005] When the first data is successfully decoded, the terminal stops receiving the target data;

[0006] The target data is the first data retransmitted by the network device; the first data is transmitted through a first hybrid automatic repeat request HARQ process, and uplink feedback of the first HARQ process is disabled.

[0007] In a second aspect, a data receiving device is provided, comprising:

[0008] A transmission module, configured for the terminal to stop receiving target data if the first data is successfully decoded;

[0009] The target data is the first data retransmitted by the network device; the first data is transmitted through a first hybrid automatic repeat request HARQ process, and uplink feedback of the first HARQ process is disabled.

[0010] In a third aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0011] In a fourth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0012] In a fifth aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method described in the first aspect.

[0013] In this embodiment of the present application, a terminal stops receiving target data when first data is successfully decoded. The target data is the first data retransmitted by a network device. The first data is transmitted via a first HARQ process, and uplink feedback for the first HARQ process is disabled. This prevents the terminal from continuing to receive the first data on subsequent retransmission resources, which would cause unnecessary power consumption. Therefore, this embodiment of the present application reduces power consumption in the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a structural diagram of a network system to which the embodiments of the present application can be applied;

[0015] Figure 2 This is a flow chart of a data receiving method provided in an embodiment of the present application;

[0016] Figure 3 is a structural diagram of a data receiving device provided in an embodiment of the present application;

[0017] Figure 4 This is a structural diagram of a communication device provided in an embodiment of the present application;

[0018] Figure 5 This is a structural diagram of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0019] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0020] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects; for example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0021] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, although these technologies can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0022] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network device 12. Among them, the terminal 11 can also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal-side devices. Wearable devices include: bracelets, headphones, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network device 12 can be a base station or a core network, where the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0023] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

[0024] In the New Radio (NR) communication mechanism, dynamic scheduling and semi-static scheduling are supported for scheduling terminals to receive downlink data. Among them, for dynamic scheduling, before scheduling the terminal to receive data each time, the network device will allocate downlink resources through downlink scheduling signaling to allow the terminal to receive data. For semi-static scheduling, the network device configures the period of periodic downlink resources through Radio Resource Control (RRC) signaling, and indicates the starting position of the periodic downlink resources through downlink scheduling signaling. The terminal starts from the resource starting position indicated by the network device and periodically uses subsequent resource positions to receive downlink data. For example, the resource repetition period configured by the network device is 2 symbols, and the starting position of the resource indicated by the downlink control information (DCI) is the first subframe with a system frame number (SFN) of 0. Then, the terminal receives data at the corresponding resource position every two symbols starting from the starting resource.

[0025] The network device sends scheduling signaling on the physical downlink control channel (PDCCH), and the terminal receives data on the physical downlink shared channel (PDSCH). The time-frequency resources required to receive data on the PDSCH are indicated by DCI. In the existing mechanism, after the terminal receives the scheduling signaling, it must attempt to receive data on the PDSCH under normal circumstances (for example, the terminal does not have a working bandwidth (Bandwidth Part, BWP) switch). After receiving the data, it will attempt to decode the received data. If the decoding is successful, a positive acknowledgment (ACK) is fed back to indicate that the network device has successfully received the data, and the subsequent network device will not continue to schedule the terminal to receive the same data. If the decoding is unsuccessful, a negative acknowledgment (NACK) is fed back to indicate that the network device has not successfully received the data, and the subsequent network device can reschedule the terminal to receive the same data.

[0026] However, in NTN scenarios, network equipment may configure terminals to disable uplink feedback for downlink data and instead transmit downlink data using methods such as blind scheduling. In other words, the network equipment can schedule terminals to receive the same data at multiple resource locations, independent of uplink feedback from the terminals. Continuing to receive the same data after the terminal has already successfully decoded it results in unnecessary power consumption. This is why the solution proposed in this application was developed.

[0027] The data receiving method, device, terminal, and readable storage medium provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through specific embodiments and their application scenarios.

[0028] See Figure 2 , Figure 2 This is a flow chart of a data receiving method provided by an embodiment of the present application, which is executed by a terminal, such as Figure 2 As shown, the following steps are included:

[0029] Step 201: If the first data is successfully decoded, the terminal stops receiving the target data.

[0030] The target data is the first data retransmitted by the network device; the first data is transmitted through a first hybrid automatic repeat request acknowledgement (HARQ) process, and uplink feedback of the first HARQ process is disabled. It can be understood that the disabling of uplink feedback of the first HARQ process means that the terminal does not need to provide feedback on the data sent by the network device through the first HARQ process, that is, feedback to the network device whether it is successfully received (ACK) or not successfully received (NACK).

[0031] In an embodiment of the present application, a network device may perform downlink allocation for a terminal. The downlink allocation may be understood as transmission resources for first data, and may specifically include resources for newly transmitting the first data and retransmission resources for retransmitting the first data. The resources for newly transmitting the first data may be understood as resources for the first transmission of the first data, and the first data may be understood as downlink data. The terminal may attempt to receive the first data through a first HARQ process based on the transmission resources allocated by the network device.

[0032] Optionally, when allocating downlink allocation to the terminal, the network device can configure the terminal to disable feedback of the above-mentioned first HARQ process. At this time, regardless of whether the terminal receives the above-mentioned first data, it will not feedback a hybrid automatic repeat request acknowledgement (HARQ-ACK) to the network device.

[0033] It should be understood that in an embodiment of the present application, each time the terminal receives the first data through the first HARQ process, it can determine whether the currently received first data is decoded successfully. If the decoding is successful, it stops receiving the first data retransmitted by the network device, thereby avoiding the terminal receiving the first data on the subsequent retransmission resources of the first data, causing unnecessary power consumption and waste of electricity.

[0034] In this embodiment of the present application, a terminal stops receiving target data when first data is successfully decoded. The target data is the first data retransmitted by a network device. The first data is transmitted via a first HARQ process, and uplink feedback for the first HARQ process is disabled. This prevents the terminal from continuing to receive the first data on subsequent retransmission resources, which would cause unnecessary power consumption. Therefore, this embodiment of the present application reduces power consumption in the terminal.

[0035] Optionally, in some embodiments, the terminal stopping receiving target data includes:

[0036] The physical layer of the terminal stops receiving the target data.

[0037] In other words, in the embodiment of the present application, stopping receiving the target data is performed by the physical layer. It should be understood that the physical layer can automatically stop receiving the target data (for example, through internal interaction of the terminal, the physical layer learns that the first data has been successfully decoded, and then stops receiving the first data retransmitted by the network device). The physical layer can also stop receiving the target data based on instructions from other layers. For example, in some embodiments, the media access control (MAC) layer can instruct the physical layer to stop receiving the target data. At this time, the above-mentioned terminal stops receiving the target data including:

[0038] The media access control MAC layer of the terminal sends first indication information to the physical layer;

[0039] The physical layer of the terminal stops receiving the target data according to the first indication information.

[0040] In the embodiment of the present application, the MAC layer includes a MAC entity, a HARQ entity, and a HARQ process. Specifically, one or more of the MAC entity, the HARQ entity, and the HARQ process may send indication information to the physical layer to instruct the physical layer to stop receiving the target data. In other words, in some embodiments, the first indication information sent by the MAC layer of the terminal to the physical layer includes at least one of the following:

[0041] The MAC entity sends first sub-indication information to the physical layer;

[0042] The HARQ entity of the terminal sends second sub-indication information to the physical layer;

[0043] The HARQ process of the terminal sends third sub-indication information to the physical layer.

[0044] In the embodiments of the present application, the first, second, and third sub-indication information have the same function, namely, to instruct the physical layer to stop receiving the target data. However, the content of the first, second, and third sub-indication information may be the same or different, and is not further limited herein.

[0045] The MAC entity sends the first sub-indication information to the physical layer to instruct the physical layer to stop receiving the first data, including the following situations:

[0046] In some embodiments, for dynamic scheduling, assuming that the MAC entity receives a first downlink allocation sent by a network device, and determines through interaction within the MAC layer that the first downlink allocation is a retransmission resource for the first data, and the first data has been successfully decoded, the MAC entity instructs the physical layer to stop receiving the first data corresponding to the first downlink allocation.

[0047] In some embodiments, the network device configures downlink aggregation transmission for the terminal, such as the PDSCH aggregation (PDSCH-Aggregation) function, which can be simply understood as configuring the downlink aggregation transmission factor PDSCH-AggregationFactor=4 for RRC, indicating that the network device will have three retransmissions after the new transmission. The network device indicates the downlink resources required for the four data transmissions through a scheduling signaling (such as DCI). The MAC entity determines through interaction within the MAC layer that the first data has been successfully decoded and expired, and then instructs the physical layer to stop receiving the subsequent retransmitted first data. For example, assuming PDSCH-AggregationFactor=4, when the MAC layer determines that the newly transmitted data has been successfully decoded, it instructs the physical layer to stop receiving the subsequent three retransmitted data.

[0048] In some embodiments, the network device configures semi-static resources and the semi-static resources are configured with downlink aggregate transmission. This can be simply understood as if the RRC configures the downlink aggregate transmission factor PDSCH-AggregationFactor = 4. The semi-static resources configured in each cycle can be used for new transmission and three retransmissions. The MAC entity determines through interaction within the MAC layer that the first data has been successfully decoded and expired, and the MAC entity instructs the physical layer to stop receiving the first data that is subsequently retransmitted by the network. For example, assuming PDSCH-AggregationFactor = 4, if the MAC layer determines that the newly transmitted data has been successfully decoded, it instructs the physical layer to stop receiving the subsequent three retransmissions of data.

[0049] The HARQ entity sending the second sub-indication information to the physical layer to instruct the physical layer to stop receiving the first data includes the following situations:

[0050] In some embodiments, when the HARQ entity receives HARQ information corresponding to the first downlink allocation and determines based on the interaction within the MAC layer that the first downlink allocation is a retransmission resource for the first data and the first data has been successfully decoded, the HARQ entity instructs the physical layer to stop receiving the first data retransmitted by the network device.

[0051] In some embodiments, a network device configures downlink aggregate transmission for a terminal, and if a HARQ entity determines that first data has been successfully decoded, instructs the physical layer to stop receiving subsequent retransmitted first data. For example, if the HARQ entity determines that newly transmitted first data transmitted via aggregate transmission has been successfully decoded, it instructs the physical layer to stop receiving retransmitted first data transmitted via aggregate transmission.

[0052] In some embodiments, a network device configures semi-static resources and configures downlink aggregate transmission for the semi-static resources. If the HARQ entity determines that the first data has been successfully decoded, the network device instructs the physical layer to stop receiving subsequent retransmitted data. For example, if the HARQ entity determines that the newly transmitted first data transmitted via the aggregate transmission mode has been successfully decoded, the network device instructs the physical layer to stop receiving the retransmitted first data transmitted via the aggregate transmission mode.

[0053] Sending the third sub-indication information to the physical layer for the HARQ process to instruct the physical layer to stop receiving the first data includes the following situations:

[0054] The HARQ process determines, based on the HARQ information associated with the received first downlink allocation, that the first downlink allocation is a retransmission resource for the first data, and that the first data has been successfully decoded, and the HARQ process instructs the physical layer to stop receiving the first data retransmitted by the network device.

[0055] Optionally, in some embodiments, after the step of the MAC entity sending the first sub-indication information to the physical layer, the method further includes:

[0056] In a case where the MAC entity determines that the first downlink allocation is a retransmission resource for the first data, the MAC entity stops sending target information to the HARQ entity associated with the first downlink allocation;

[0057] The target information includes second indication information and HARQ information associated with the first downlink allocation, and the second indication information is used to indicate the existence of the first downlink allocation.

[0058] It should be understood that the MAC entity stops sending target information to the HARQ entity associated with the first downlink allocation, which can be understood as the MAC entity not sending target information to the HARQ entity associated with the first downlink allocation, that is, the MAC entity does not send the target information.

[0059] The embodiment of the present application is applied to a dynamic scheduling scenario. During the dynamic scheduling process, the network device dynamically schedules the terminal to perform downlink reception. Since the physical layer will stop receiving the first data after the MAC entity indicates the first sub-indication information to the physical layer, the MAC entity does not indicate the existence of the first downlink allocation to the HARQ entity, and does not send the HARQ information associated with the first downlink allocation to the HARQ entity. This can prevent the HARQ entity and the HARQ process from executing invalid processing procedures, thereby improving the system performance of the terminal.

[0060] Optionally, in some embodiments, after the step of the HARQ entity sending the second sub-indication information to the physical layer, the method further includes:

[0061] In a case where the HARQ entity determines that the first downlink allocation associated with the received HARQ information is a retransmission resource for the first data, the HARQ entity stops directing the HARQ information associated with the first downlink allocation to the HARQ process corresponding to the HARQ information.

[0062] It should be understood that the HARQ entity stops directing the HARQ information associated with the first downlink allocation to the HARQ process corresponding to the HARQ information, which can be understood as: the HARQ entity does not direct the HARQ information associated with the first downlink allocation to the HARQ process corresponding to the HARQ information (such as The HARQ entity does not direct HARQ information to the corresponding HARQ processes).

[0063] The embodiments of the present application are applied to a dynamic scheduling scenario. During the dynamic scheduling process, a network device dynamically schedules a terminal to perform downlink reception. Since the physical layer stops receiving the first data after the MAC entity receives the HARQ information corresponding to the first downlink assignment, the HARQ entity does not direct the HARQ information associated with the first downlink assignment to the HARQ process corresponding to the HARQ information. This can prevent the HARQ process from executing an invalid processing flow, thereby improving the system performance of the terminal.

[0064] It should be understood that the content included in the above-mentioned first indication information can be set according to actual needs. Optionally, in some implementations, the above-mentioned first indication information includes at least one of the following: downlink allocation information and HARQ process information.

[0065] The downlink allocation information can be understood as follows: assuming the MAC layer confirms that the first downlink allocation is a retransmission resource for the first data and the first data has been successfully decoded, the physical layer is instructed to stop receiving the downlink data corresponding to the first downlink allocation.

[0066] The HARQ process information can be understood as: assuming that the first data is transmitted through the first HARQ process, if the MAC confirms that the first downlink allocation is a retransmission resource for the first data and the first data has been successfully decoded, then the physical layer is instructed to stop receiving the data corresponding to the first HARQ process.

[0067] It should be understood that the above-mentioned first indication information is used to indicate any one of the following items: the physical layer stops receiving the first data retransmitted by the network device for the next time, and the physical layer stops receiving all retransmitted first data by the network device after the first data is successfully decoded.

[0068] In an embodiment of the present application, the first indication information of the MAC layer can instruct the physical layer to stop receiving the first data retransmitted by the network device only once, or can instruct the physical layer to stop receiving the first data retransmitted by the network device multiple times.

[0069] Exemplarily, the network device configures downlink aggregate transmission for the terminal, for example, by configuring the downlink aggregate transmission factor (e.g., PDSCH-AggregationFactor) to 4 through RRC. If the MAC layer successfully decodes the first data newly transmitted by the network device, it instructs the physical layer to stop receiving the first data subsequently retransmitted by the network device. For example, the MAC layer may send the first indication information three times, respectively instructing the physical layer to stop receiving the first data retransmitted by the network device for the first, second, and third time. Alternatively, the first indication information may be sent once to instruct the physical layer to stop receiving the first data retransmitted by the network device for the first, second, and third time.

[0070] Optionally, in some embodiments, the terminal's behavior of stopping receiving target data includes at least one of the following:

[0071] The terminal discards the retransmission resources allocated by the network device;

[0072] The terminal ignores the retransmission resources allocated by the network device;

[0073] The terminal stops receiving data at a resource location corresponding to the retransmission resource allocated by the network device;

[0074] The retransmission resource is a resource used by the network device to retransmit the first data.

[0075] In the embodiment of the present application, the retransmission resource refers to a resource used to retransmit the first data after the first data is successfully decoded. It should be understood that stopping receiving data can be understood as not attempting to receive data.

[0076] The terminal discards the retransmission resources allocated by the network device. For example, the network device allocates resources to newly transmit the first data at time t1, and allocates resources to retransmit the first data at time t2. If the first data received through the resources allocated at time t1 has been successfully decoded, the UE discards the resources allocated at time t2 to retransmit the first data.

[0077] The terminal ignores the retransmission resources. For example, the network device allocates resources to newly transmit the first data at time t1 and allocates resources to retransmit the first data at time t2. If the first data received through the resources allocated at time t1 has been successfully decoded, the UE ignores the resources allocated at time t2 to retransmit the first data.

[0078] The terminal stops receiving data at the resource position corresponding to the retransmission resource. For example, the network device allocates resources to newly transmit the first data at time t1, and allocates resources to retransmit the first data at time t2. If the first data received through the resources allocated at time t1 has been successfully decoded, the UE stops receiving or does not attempt to receive the first data at the resource position allocated at time t2 for retransmitting the first data.

[0079] Optionally, in some embodiments, before the terminal stops receiving target data, the method further includes:

[0080] The terminal determines the retransmission resource according to a target parameter; wherein the target parameter includes at least one of HARQ information associated with the first downlink allocation and retransmission information configured by a network device.

[0081] In the embodiment of the present application, whether the downlink allocation is a retransmission resource for the first data may be determined based on at least one of the HARQ information and the retransmission information.

[0082] Optionally, in some embodiments, when HARQ information is used to determine the retransmission resource, the HARQ information includes a New Data Indicator (NDI) parameter value, and the terminal determines the retransmission resource according to the HARQ information associated with the first downlink assignment, including:

[0083] When the NDI parameter value associated with the first downlink allocation does not change compared with the last scheduling, the terminal determines that the first downlink allocation is the retransmission resource.

[0084] It should be noted that the NDI field can be an extended parameter field (e.g., two bits). Since uplink feedback is disabled, when some DCI is lost, the terminal may incorrectly determine whether the DCI carries retransmission resources or new transmission resources. The extended NDI can further ensure that the terminal correctly determines whether the downlink resource is a retransmission resource or a new transmission resource.

[0085] In an embodiment of the present application, it is assumed that the first data is transmitted through the first HARQ process, the terminal receives the first downlink allocation (i.e., downlink scheduling), and determines that the NDI parameter associated with the first downlink allocation has not changed compared with the last scheduling of the first HARQ process, and therefore determines that the first downlink allocation is a retransmission resource for the first data.

[0086] Optionally, in some embodiments, when retransmission information is used to determine the retransmission resource, the retransmission information includes the number of retransmissions of the first data.

[0087] In example one, the network device configures downlink aggregate transmission for the terminal, for example, by configuring PDSCH-AggregationFactor = 4 through RRC, and the network device provides four resource locations through downlink scheduling signaling. The terminal can then determine that these four resource locations correspond to new transmission resources, first retransmission resources, second retransmission resources, and third retransmission resources, respectively.

[0088] Example 2: The network device configures semi-static resources and the semi-static resources are configured with downlink aggregate transmission. For example, through RRC configuration PDSCH-AggregationFactor = 4, the network device configures four semi-static resources for the terminal in each cycle. The terminal can determine that these four resource positions correspond to new transmission resources, first retransmission resources, second retransmission resources and third retransmission resources respectively.

[0089] It should be noted that the data receiving method provided in the embodiments of the present application can be executed by a data receiving device, or a control module in the data receiving device for executing the data receiving method. In the embodiments of the present application, the data receiving device provided in the embodiments of the present application is described by taking the data receiving device executing the data receiving method as an example.

[0090] See Figure 3 , Figure 3 This is a structural diagram of a data receiving device provided in an embodiment of the present application. Figure 3 As shown, the data receiving device 300 includes:

[0091] The transmission module 301 is configured to stop receiving target data when the first data is successfully decoded.

[0092] The target data is the first data retransmitted by the network device; the first data is transmitted through a first HARQ process, and uplink feedback of the first HARQ process is disabled.

[0093] Optionally, the transmission module 301 is specifically configured to: cause the physical layer of the terminal to stop receiving the target data.

[0094] Optionally, the transmission module 301 includes:

[0095] A first transmission unit, configured for a media access control (MAC) layer of the terminal to send first indication information to a physical layer;

[0096] The second transmission unit is configured to enable a physical layer of the terminal to stop receiving the target data according to the first indication information.

[0097] Optionally, the first transmission unit is specifically configured to perform at least one of the following:

[0098] The MAC entity sends first sub-indication information to the physical layer;

[0099] The HARQ entity of the terminal sends second sub-indication information to the physical layer;

[0100] The HARQ process of the terminal sends third sub-indication information to the physical layer.

[0101] Optionally, the first transmission unit is further configured to: when the MAC entity determines that the first downlink allocation is a retransmission resource for the first data, the MAC entity stops sending target information to the HARQ entity associated with the first downlink allocation;

[0102] The target information includes second indication information and HARQ information associated with the first downlink allocation, and the second indication information is used to indicate the existence of the first downlink allocation.

[0103] Optionally, the first transmission unit is also used to: when the HARQ entity determines that the first downlink allocation associated with the received HARQ information is a retransmission resource for the first data, the HARQ entity stops directing the HARQ information associated with the first downlink allocation to the HARQ process corresponding to the HARQ information.

[0104] Optionally, the first indication information is used to indicate any one of the following: the physical layer stops receiving the first data retransmitted by the network device for the next time, and the physical layer stops receiving all retransmitted first data by the network device after the first data is successfully decoded.

[0105] Optionally, the first indication information includes at least one of the following: downlink allocation information and HARQ process information.

[0106] Optionally, the terminal's behavior of stopping receiving target data includes at least one of the following:

[0107] discarding retransmission resources allocated by the network device;

[0108] Ignore the retransmission resources allocated by the network device;

[0109] Stop receiving data at the corresponding resource location allocated by the network device;

[0110] The retransmission resource is a resource used by the network device to retransmit the first data.

[0111] Optionally, the data receiving device 300 further includes:

[0112] The first determination module is used for the terminal to determine the retransmission resource according to a target parameter; wherein the target parameter includes at least one of the HARQ information associated with the first downlink allocation and the retransmission information configured by the network device.

[0113] Optionally, the HARQ information includes a new data indication NDI parameter value, and the first determination module is specifically used to: when the NDI parameter value associated with the first downlink allocation has not changed compared with the previous scheduling, the terminal determines that the first downlink allocation is the retransmission resource.

[0114] Optionally, the retransmission information includes the number of retransmissions of the first data.

[0115] Optionally, the data receiving device 300 further includes:

[0116] The second determination module is used by the terminal to determine whether the first data received through the first HARQ process is successfully decoded.

[0117] The network device provided in the embodiment of the present application can achieve Figure 2 To avoid repetition, each process in the method embodiment will not be described here.

[0118] The data receiving device in the embodiments of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. For example, the mobile terminal can include but is not limited to the types of terminal 11 listed above, and the non-mobile terminal can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), an ATM, or an kiosks, etc., which are not specifically limited in the embodiments of the present application.

[0119] The data receiving device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0120] The data receiving device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0121] Optional, such as Figure 4 As shown, an embodiment of the present application also provides a communication device 400, including a processor 401, a memory 402, and a program or instruction stored in the memory 402 and executable on the processor 401. When the program or instruction is executed by the processor 401, each process of the above-mentioned data receiving method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0122] Figure 5 A schematic diagram of the hardware structure of a terminal for implementing various embodiments of the present application.

[0123] The terminal 500 includes but is not limited to components such as a radio frequency unit 501 , a network module 502 , an audio output unit 503 , an input unit 504 , a sensor 505 , a display unit 506 , a user input unit 507 , an interface unit 508 , a memory 509 , and a processor 510 .

[0124] Those skilled in the art will understand that the terminal 500 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 510 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 5 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0125] It should be understood that in an embodiment of the present application, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042, and the graphics processor 5041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 507 includes a touch panel 5071 and other input devices 5072. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include two parts: a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0126] In the embodiment of the present application, the radio frequency unit 501 receives downlink data from the network device and transmits it to the processor 510 for processing. Furthermore, the radio frequency unit 501 transmits uplink data to the network device. Typically, the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0127] The memory 509 can be used to store software programs or instructions and various data. The memory 109 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, at least one application program or instruction required for a function (such as a sound playback function, an image playback function, etc.). In addition, the memory 509 may include a high-speed random access memory and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0128] Processor 510 may include one or more processing units. Optionally, processor 510 may integrate an application processor and a modem processor. The application processor primarily processes the operating system, user interface, and application programs or instructions, while the modem processor primarily processes wireless communications, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 510.

[0129] The radio frequency unit 501 is configured to stop receiving target data when the terminal successfully decodes the first data;

[0130] The target data is the first data retransmitted by the network device; the first data is transmitted through a first HARQ process, and uplink feedback of the first HARQ process is disabled.

[0131] It should be understood that in this embodiment, the processor 510 and the radio frequency unit 501 can implement Figure 2 To avoid repetition, the various processes implemented by the terminal in the method embodiment are not described here.

[0132] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data receiving method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0133] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0134] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data receiving method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0135] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0136] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0137] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or base station, etc.) to execute the methods described in each embodiment of the present application.

[0138] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A data receiving method, characterized in that: include: When the first data is decoded successfully, the terminal stops receiving the target data; The target data is the first data retransmitted by the network device; the first data is transmitted through a first hybrid automatic repeat request HARQ process, and uplink feedback of the first HARQ process is disabled; The terminal stopping receiving target data includes: The media access control MAC layer of the terminal sends first indication information to the physical layer; The physical layer of the terminal stops receiving the target data according to the first indication information; The first indication information is used to indicate any one of the following: the physical layer stops receiving the first data retransmitted by the network device for the next time, and the physical layer stops receiving all the first data retransmitted by the network device after the first data is successfully decoded.

2. The method according to claim 1, characterized in that The terminal stopping receiving target data includes: The physical layer of the terminal stops receiving the target data.

3. The method according to claim 1, characterized in that The MAC layer of the terminal sends the first indication information to the physical layer, including at least one of the following: The MAC entity sends first sub-indication information to the physical layer; The HARQ entity of the terminal sends second sub-indication information to the physical layer; The HARQ process of the terminal sends third sub-indication information to the physical layer.

4. The method according to claim 3, characterized in that: After the step of the MAC entity sending the first sub-indication information to the physical layer, the method further includes: In a case where the MAC entity determines that the first downlink allocation is a retransmission resource for the first data, the MAC entity stops sending target information to the HARQ entity associated with the first downlink allocation; The target information includes second indication information and HARQ information associated with the first downlink allocation, and the second indication information is used to indicate the existence of the first downlink allocation.

5. The method according to claim 3, characterized in that: After the step of the HARQ entity sending the second sub-indication information to the physical layer, the method further includes: In a case where the HARQ entity determines that the first downlink allocation associated with the received HARQ information is a retransmission resource for the first data, the HARQ entity stops directing the HARQ information associated with the first downlink allocation to the HARQ process corresponding to the HARQ information.

6. The method according to claim 1, characterized in that The first indication information includes at least one of the following: downlink allocation information and HARQ process information.

7. The method according to claim 1, characterized in that The behavior of the terminal stopping receiving target data includes at least one of the following: The terminal discards the retransmission resources allocated by the network device; The terminal ignores the retransmission resources allocated by the network device; The terminal stops receiving data at a resource location corresponding to the retransmission resource allocated by the network device; The retransmission resource is a resource used by the network device to retransmit the first data.

8. The method according to claim 7, characterized in that Before the terminal stops receiving the target data, the method further includes: The terminal determines the retransmission resource according to a target parameter; wherein the target parameter includes at least one of HARQ information associated with the first downlink allocation and retransmission information configured by a network device.

9. The method according to claim 8, characterized in that The HARQ information includes a new data indication NDI parameter value, and the terminal determines the retransmission resource according to the HARQ information associated with the first downlink allocation, including: When the NDI parameter value associated with the first downlink allocation does not change compared with the last scheduling, the terminal determines that the first downlink allocation is the retransmission resource.

10. The method according to claim 8, characterized in that The retransmission information includes the number of retransmissions of the first data.

11. A data receiving device, characterized in that: include: A transmission module, used for the terminal to stop receiving target data when the first data is decoded successfully; The target data is the first data retransmitted by the network device; the first data is transmitted through a first hybrid automatic repeat request HARQ process, and uplink feedback of the first HARQ process is disabled; Wherein, the transmission module includes: A first transmission unit, used for a media access control MAC layer of the terminal to send first indication information to a physical layer; a second transmission unit, configured for causing a physical layer of the terminal to stop receiving the target data according to the first indication information; The first indication information is used to indicate any one of the following: the physical layer stops receiving the first data retransmitted by the network device for the next time, and the physical layer stops receiving all the first data retransmitted by the network device after the first data is successfully decoded.

12. The device according to claim 11, characterized in that The transmission module is specifically used to: the physical layer of the terminal stops receiving the target data.

13. The device according to claim 11, characterized in that The first transmission unit is specifically configured to perform at least one of the following: The MAC entity sends first sub-indication information to the physical layer; The HARQ entity of the terminal sends second sub-indication information to the physical layer; The HARQ process of the terminal sends third sub-indication information to the physical layer.

14. The device according to claim 13, characterized in that The first transmission unit is further configured to: when the MAC entity determines that the first downlink allocation is a retransmission resource of the first data, the MAC entity stops sending target information to the HARQ entity associated with the first downlink allocation; The target information includes second indication information and HARQ information associated with the first downlink allocation, and the second indication information is used to indicate the existence of the first downlink allocation.

15. The device according to claim 13, characterized in that The first transmission unit is further used for: when the HARQ entity determines that the first downlink allocation associated with the received HARQ information is a retransmission resource for the first data, the HARQ entity stops directing the HARQ information associated with the first downlink allocation to the HARQ process corresponding to the HARQ information.

16. The device according to claim 11, characterized in that The first indication information includes at least one of the following: downlink allocation information and HARQ process information.

17. The device according to claim 11, characterized in that The behavior of the terminal stopping receiving target data includes at least one of the following: discarding retransmission resources allocated by the network device; Ignore the retransmission resources allocated by the network device; Stop receiving data at a resource location corresponding to the retransmission resource allocated by the network device; The retransmission resource is a resource used by the network device to retransmit the first data.

18. The device according to claim 17, characterized in that The data receiving device also includes: The first determination module is used for the terminal to determine the retransmission resource according to the target parameter; wherein the target parameter includes at least one of the HARQ information associated with the first downlink allocation and the retransmission information configured by the network device.

19. The device according to claim 18, characterized in that The HARQ information includes a new data indication NDI parameter value, and the first determination module is specifically used for: when the NDI parameter value associated with the first downlink allocation has not changed relative to the previous scheduling, the terminal determines that the first downlink allocation is the retransmission resource.

20. The device according to claim 18, characterized in that The retransmission information includes the number of retransmissions of the first data.

21. A terminal, characterized in that: include: A memory, a processor, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps in the data receiving method according to any one of claims 1 to 10 are implemented.

22. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or instruction is executed by a processor, the steps of the data receiving method according to any one of claims 1 to 10 are implemented.

Images