Downlink scheduling method, device and terminal

Abstract

The present application discloses a downlink scheduling method, apparatus, and terminal, belonging to the field of wireless communication technology. The downlink scheduling method of an embodiment of the present application includes: receiving a first downlink allocation transmitted via a first PDCCH; determining, based on the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted, the target HARQ process being the HARQ process corresponding to the first downlink allocation; and determining, based on whether the NDI corresponding to the target HARQ process is inverted or not inverted, whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission.

Description

Technical Field

[0001] The present application belongs to the field of wireless communication technology, and specifically relates to a downlink scheduling method, device and terminal. Background Art

[0002] In the New Radio (NR) system, broadcast and multicast services are primarily transmitted via the group-common physical downlink shared channel (PDSCH). The group-common PDSCH can be scheduled using the group-common physical downlink control channel (PDCCH). To ensure service reliability, the group-common PDSCH supports hybrid automatic repeat request (HARQ) feedback. For example, when a user equipment (UE) sends back a negative acknowledgement (NACK), the network-side device (e.g., base station) can schedule retransmissions using either the group-common PDSCH scheduled by the group-common PDCCH or the unicast PDSCH scheduled by the unicast PDCCH.

[0003] However, when the network side device can schedule the group-common PDSCH through the group-common PDCCH, and schedule the unicast PDSCH through the unicast PDCCH, for the case of retransmission of the unicast PDSCH scheduled by the unicast PDCCH, or for the case of retransmission of the group-common PDSCH scheduled by the group-common PDCCH, since the unicast service scheduling of different UEs may be different, that is, the NDI (New Data Indicator) has undergone different inversions, and the group-common PDCCH is group-common, when it schedules the group-common PDSCH, its NDI can only be indicated as a specific value, it may cause the network side device to be unable to use the HARQ process (process) to schedule the group-common PDSCH, or unable to indicate the NDI corresponding to the HARQ process. Summary of the Invention

[0004] The embodiments of the present application provide a downlink scheduling method, apparatus, and terminal, which can solve the problem that the network-side device cannot use the common PDSCH of the HARQ process scheduling group or cannot indicate the NDI corresponding to the HARQ process.

[0005] In a first aspect, a downlink scheduling method is provided, which is executed by a terminal device, and the method includes: receiving a first downlink assignment (DL assignment) transmitted via a first PDCCH; determining whether an NDI corresponding to a target HARQ process is inverted or not inverted according to a radio network temporary identifier (RNTI) corresponding to the first downlink assignment, and the target HARQ process is the HARQ process corresponding to the first downlink assignment; and determining whether a transport block (TB) scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not.

[0006] In the second aspect, a downlink scheduling device is provided, which includes: a receiving module for receiving a first downlink allocation transmitted via a first PDCCH; a first determination module for determining, based on the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted, and the target HARQ process is the HARQ process corresponding to the first downlink allocation; a second determination module for determining, based on whether the NDI corresponding to the target HARQ process is inverted or not inverted, whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission.

[0007] 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.

[0008] 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.

[0009] In a fifth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the steps of the method described in the first aspect.

[0010] In a sixth aspect, a computer program product is provided, which includes 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 seventh aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the steps of the method described in the first aspect.

[0012] In an embodiment of the present application, the terminal device determines whether the NDI corresponding to the target HARQ process is inverted or not by detecting the RNTI corresponding to the first downlink allocation, and then determines whether the TB associated with the target HARQ process is a new transmission or a retransmission based on whether the NDI is inverted or not. This can solve the problem that the network side device cannot use the common PDSCH of the HARQ process scheduling group, or cannot indicate the NDI corresponding to the HARQ process, while also improving the effectiveness of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 It is a structural diagram of a wireless communication system provided by an exemplary embodiment of the present application.

[0014] Figure 2 It is a flowchart of a downlink scheduling method provided by an exemplary embodiment of the present application.

[0015] Figure 3 It is a flowchart of a downlink scheduling method provided by another exemplary embodiment of the present application.

[0016] Figure 4 It is a flowchart of a downlink scheduling method provided by another exemplary embodiment of the present application.

[0017] Figure 5 It is a block diagram of a downlink scheduling device provided by an exemplary embodiment of the present application.

[0018] Figure 6 It is a schematic block diagram of a terminal provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0019] The following will be combined with the accompanying drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the embodiments described are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present 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. The following description describes the NR system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0022] Figure 1The following is a result diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or a user terminal. 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 (PDA), a handheld computer, a netbook, an 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: smart watches, 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 side device 12 can be a base station or a core network, where the base station can be called 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] The technical solutions provided by the embodiments of the present application are described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0024] like Figure 2 FIG2 is a flow chart of a downlink scheduling method 200 provided in an exemplary embodiment of the present application. The method 200 may be executed by, but not limited to, a terminal device. For example, the method 200 may be executed by software and / or hardware installed in the terminal device. In this embodiment, the method 200 may include the following steps.

[0025] S210: Receive a first downlink assignment transmitted via a first PDCCH.

[0026] The terminal device may perform the first PDCCH detection and reception in a PDCCH detection opportunity, wherein the PDCCH detection opportunity may be determined by, but not limited to, high-level signaling configuration, protocol agreement, etc., and is not limited here.

[0027] In addition, in this embodiment, the terminal device may support both reception of multicast services and reception of unicast services, or support both reception of group-common PDSCH and reception of unicast PDSCH, which is not limited here.

[0028] S220: Determine, based on the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not.

[0029] The target HARQ process is the HARQ process corresponding to the first downlink allocation.

[0030] In this embodiment, each HARQ process saves an NDI value, and the NDI value can use 1 bit to indicate whether the scheduled TB is a new transmission or a retransmission. If the NDI value of the same HARQ process changes compared to the previous one, that is, the NDI is reversed (NDI toggled), it means that the currently transmitted TB is the initial transmission of a new TB; otherwise (NDI not toggled) it means that the current transmission is a retransmission (i.e., a retransmission) of the same TB. In this case, this embodiment determines whether the TB associated with the target HARQ process is a new transmission or a retransmission by determining whether the NDI value corresponding to the target HARQ process is reversed or not.

[0031] S230 : Determine whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not.

[0032] Among them, considering that when the PDSCH is scheduled by the first PDCCH, one PDSCH may carry 1 or 2 TBs, for example, when the physical layer is not configured with downlink spatial multiplexing, one PDSCH may carry one TB (i.e., one HARQ process corresponds to one TB), and when the physical layer is configured with downlink spatial multiplexing, one PDSCH may carry one or two TBs (i.e., one HARQ process corresponds to one TB or two TBs). Then, for the scenario where two TBs are carried on the group common PDSCH, the two TBs may correspond to the same HARQ process (or different HARQ processes), or one of the two TBs may be a new transmission and the other a retransmission. Based on this, the present application may determine whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not, thereby improving the reliability of the determination result.

[0033] In this embodiment, the terminal device determines whether the NDI corresponding to the target HARQ is inverted or not by detecting the RNTI corresponding to the first downlink allocation, and then determines whether the TB associated with the target HARQ process is a new transmission or a retransmission based on whether the NDI is inverted or not. This can solve the problem that the network side device cannot use the HARQ process scheduling group common PDSCH, or cannot indicate the NDI corresponding to the HARQ process, while also improving the effectiveness of the communication system.

[0034] like Figure 3 FIG. 3 is a flow chart of a downlink scheduling method 300 provided in an exemplary embodiment of the present application. The method 300 may be executed by, but not limited to, a terminal device. For example, the method 300 may be executed by software and / or hardware installed in the terminal device. In this embodiment, the method 300 may include the following steps.

[0035] S310: Receive a first downlink assignment transmitted via a first PDCCH.

[0036] Among them, in addition to referring to the relevant description in method embodiment 200, the implementation process of S310, as a possible implementation method, when the first PDCCH is a unicast PDCCH and the unicast PDSCH or group common PDSCH is scheduled by the first PDCCH, the first PDCCH can be scrambled by a specific RNTI; wherein, the specific RNTI is different from the specified RNTI, and the specified RNTI is the RNTI used when scheduling the unicast PDSCH.

[0037] For example, the designated RNTI may include any one of the cell RNTI (CellRNTI, C-RNTI) used by the terminal device to identify its own service, the temporary cell RNTI (Temporary C-RNTI, TC-RNTI), the configured scheduling RNTI (ConfiguredScheduling RNTI, CS-RNTI), and the group-common RNTI (group-common RNTI, g-RNTI). Among them, the g-RNTI in this application refers to the RNTI of the scrambled group common PDSCH, which refers to the same RNTI for a group of terminals receiving the PDSCH, as distinguished from the specific RNTI of the UE, and may also be called other RNTIs, such as MBS-RNT, SC-g-RNTI, etc., which are not specifically limited here.

[0038] It is worth noting that the group-common PDSCH in this application mainly refers to the PDSCH that transmits multicast / groupcast / broadcast services, which refers to the PDSCH transmitted to multiple receiving points through the same physical downlink transmission resources. It can also be called multicast PDSCH or groupcast PDSCH. This application does not impose any restrictions.

[0039] As another possible implementation method, when the first PDCCH is a unicast PDCCH and a unicast PDSCH or a group-common PDSCH is scheduled by the first PDCCH, the downlink control information (DCI) carried by the first PDCCH includes a specific bit field, and the specific bit field is used to indicate whether the PDSCH scheduled by the unicast PDCCH is a retransmission of a unicast PDSCH or a group-common PDSCH.

[0040] S320: Determine, based on the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not.

[0041] The target HARQ process is the HARQ process corresponding to the first downlink allocation.

[0042] It can be understood that, in addition to referring to the relevant description in method embodiment 200, in this embodiment, as a possible implementation method, if the group-common PDSCH is retransmitted only through the group-common PDSCH scheduled by the group-common PDCCH, then when the terminal device supports both the reception of multicast services and the reception of unicast services, the group-common PDSCH can only be retransmitted through the group-common PDSCH scheduled by the group-common PDCCH, and the unicast PDSCH can only be retransmitted through the unicast PDSCH scheduled by the unicast PDCCH. Based on this, in a PDCCH detection opportunity, the process of the terminal device "determining whether the NDI corresponding to the target HARQ process is inverted or not inverted according to the RNTI corresponding to the first downlink allocation" can be implemented by at least one of the following (1)-(9).

[0043] (1) When the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a C-RNTI, a TC-RNTI, or a CS-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0044] (2) When the RNTI corresponding to the first downlink assignment is a g-RNTI and the second downlink assignment is a configured unicast downlink assignment (also called a unicast configured downlink assignment), determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink assignment is a previous downlink assignment of the same HARQ process indicating the same HARQ entity as the first downlink assignment.

[0045] (3) When the RNTI corresponding to the first downlink assignment is a g-RNTI and the RNTI corresponding to the second downlink assignment is a group-common CS-RNTI (it is worth noting that this indicates the RNTI used by the group-common PDSCH of Semi-Persistent Scheduling (SPS), and the specific name may not be limited), or the second downlink assignment is a configured group-common downlink assignment (also called a group-common configured downlink assignment), it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink assignment is a previous downlink assignment of the same HARQ process indicating the same HARQ entity as the first downlink assignment.

[0046] (4) When the RNTI corresponding to the first downlink allocation and the RNTI corresponding to the second downlink allocation are both g-RNTI, determine whether the NDI corresponding to the target HARQ process is inverted based on the values ​​of the NDI indicated by the first downlink allocation and the second downlink allocation respectively; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0047] (5) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a g-RNTI or a group common CS-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0048] (6) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the second downlink allocation is a configured group common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0049] (7) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a CS-RNTI, or the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0050] (8) When the RNTI corresponding to the first downlink allocation is c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is c-RNTI or TC-RNTI, determine whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDI indicated by the first downlink allocation and the second downlink allocation respectively; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0051] (9) When the RNTI corresponding to the first downlink allocation is a g-RNTI and the first downlink allocation is the first downlink allocation (that is, before the first downlink allocation, there is no downlink allocation for the same HARQ process and the same HARQ entity as indicated by the first downlink allocation), it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is the previous downlink allocation for the same HARQ process and the same HARQ entity as indicated by the first downlink allocation.

[0052] It can be understood that the terminal device uses which one or more of the above (1)-(9) to determine whether the NDI corresponding to the target HARQ process is inverted or not inverted, which can be configured by high-level signaling (including direct configuration or indirect configuration, such as by configuring the retransmission method of the group common PDSCH) or protocol agreement, and is not limited here.

[0053] S330: Determine whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not.

[0054] It can be understood that in addition to referring to the relevant description in method embodiment 200 or 300, the implementation process of S430 may include, in this embodiment, as a possible implementation method, the implementation process of S330 may include: when the NDI is reversed, determining that the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission; when the NDI is not reversed, determining that the TB scheduled by the first PDCCH and associated with the target HARQ process is a retransmission.

[0055] In this embodiment, the RNTI corresponding to the first downlink allocation is compared with the second downlink allocation or the RNTI corresponding to the second downlink allocation to determine whether the NDI corresponding to the target HARQ process is inverted or not, which can further solve the problem that the network side device cannot indicate the NDI corresponding to the HARQ process and improve the wireless communication performance.

[0056] like Figure 4 FIG. 4 is a flow chart of a downlink scheduling method 400 provided in an exemplary embodiment of the present application. The method 400 may be executed by, but not limited to, a terminal device. For example, the method 400 may be executed by software and / or hardware installed in the terminal device. In this embodiment, the method 400 may include the following steps.

[0057] S410: Receive a first downlink assignment transmitted via a first PDCCH.

[0058] The implementation process of S410 may refer to the relevant description in the aforementioned method 200 or 300, and will not be repeated here to avoid repetition.

[0059] S420: Determine whether the NDI corresponding to the target HARQ process is inverted or not inverted according to at least one group-common PDSCH retransmission mode and the RNTI corresponding to the first downlink allocation.

[0060] The target HARQ process is the HARQ process corresponding to the first downlink allocation.

[0061] It can be understood that in addition to referring to the relevant description in method embodiment 200 or 300 for the implementation process of S420, in this embodiment, as a possible implementation method, the retransmission method of the group common PDSCH can include at least one of the following methods 1 to 6.

[0062] Mode 1: Group-common PDSCH scheduled by group-common PDCCH.

[0063] Among them, when the terminal device is configured with mode 1, the group-common PDSCH can only be retransmitted and scheduled through the group-common PDSCH scheduled by the group-common PDSCH.

[0064] Mode 2: Unicast PDSCH scheduled by unicast PDCCH.

[0065] Among them, when the terminal device is configured with mode 2, the group common PDSCH can only be retransmitted and scheduled through the unicast PDSCH scheduled by the unicast PDSCH.

[0066] Mode 3: Group-common PDSCH scheduled by unicast PDCCH.

[0067] Among them, when the terminal device is configured with mode 3, the group-common PDSCH can only be retransmitted and scheduled through the group-common PDSCH scheduled by the unicast PDSCH.

[0068] Mode 4: a group-common PDSCH scheduled by a group-common PDCCH, or a unicast PDSCH scheduled by a unicast PDCCH.

[0069] Among them, when the terminal device is configured with mode 4, the group-common PDSCH can be retransmitted and scheduled through the group-common PDSCH scheduled by the group-common PDSCH, and can also be retransmitted and scheduled through the unicast PDSCH scheduled by the unicast PDSCH.

[0070] Mode 5: Unicast PDSCH scheduled by unicast PDCCH, or group-common PDSCH scheduled by unicast PDCCH.

[0071] Among them, when the terminal device is configured with mode 5, the group-common PDSCH can be retransmitted and scheduled through the group-common PDSCH scheduled by the unicast PDSCH, and can also be retransmitted and scheduled through the unicast PDSCH scheduled by the unicast PDCCH.

[0072] Mode 6: a unicast PDSCH scheduled by a unicast PDCCH, or a group-common PDSCH scheduled by a unicast PDCCH, or a group-common PDSCH scheduled by a group-common PDSCH.

[0073] Among them, when the terminal device is configured with method 6, the group-common PDSCH can be retransmitted through the group-common PDSCH scheduled by unicast PDSCH, the unicast PDSCH scheduled by unicast PDCCH, or the group-common PDSCH scheduled by group-common PDSCH.

[0074] In an optional implementation, the aforementioned at least one group-common PDSCH retransmission mode may be, but is not limited to, configured for the terminal device by a network-side device (such as a base station) through high-layer signaling. It is understood that the group-common PDSCH retransmission mode may include at least one of the aforementioned modes 1 to 6.

[0075] Furthermore, based on the several group-common PDSCH retransmission methods given above, the process of "the terminal device determining whether the NDI corresponding to the target HARQ process is inverted or not inverted based on at least one group-common physical downlink shared channel PDSCH retransmission method and the RNTI corresponding to the first downlink allocation" is explained below with combination of different examples.

[0076] Example 1

[0077] If the terminal device is configured with the aforementioned mode 1, that is, the group-common PDSCH is retransmitted only through the group-common PDSCH scheduled by the group-common PDCCH, then when the terminal device supports both multicast service reception and unicast service reception, the group-common PDSCH can only be retransmitted through the group-common PDSCH scheduled by the group-common PDCCH, and the unicast PDSCH can only be retransmitted through the unicast PDSCH scheduled by the unicast PDCCH. In this case, in a PDCCH detection opportunity, if the terminal device receives the first downlink allocation, then it can be determined based on at least one of the following (1)-(8) whether the NDI corresponding to the HARQ process is inverted or not.

[0078] (1) If the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a C-RNTI, a TC-RNTI, or a CS-RNTI, then regardless of the value of the NDI, it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0079] (2) When the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured unicast downlink allocation, regardless of the value of the NDI, it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0080] (3) When the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a group-common CS-RNTI or the second downlink allocation is a configured group-common downlink allocation, regardless of the value of the NDI, it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0081] (4) When the RNTI corresponding to the first downlink allocation and the RNTI corresponding to the second downlink allocation are both g-RNTI, determine whether the NDI corresponding to the target HARQ process is inverted based on the values ​​of the NDI indicated by the first downlink allocation and the second downlink allocation respectively; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0082] (5) When the RNTI corresponding to the first downlink allocation is c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is g-RNTI or group common CS-RNTI, regardless of the value of NDI, it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0083] (6) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the second downlink allocation is a configured group common downlink allocation, regardless of the value of the NDI, it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0084] (7) When the RNTI corresponding to the first downlink allocation is c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is CS-RNTI, or the second downlink allocation is a configured unicast downlink allocation, regardless of the value of NDI, it is determined that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0085] (8) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a c-RNTI or a TC-RNTI, determining whether the NDI corresponding to the target HARQ process is inverted based on the values ​​of the NDIs indicated by the first downlink allocation and the second downlink allocation, respectively. The second downlink allocation is a previous downlink allocation for the same HARQ process and the same HARQ entity as the first downlink allocation.

[0086] It can be understood that in (1)-(8) in the aforementioned example 1, the RNTI corresponding to the first downlink allocation received by the terminal device is g-RNTI. Then, it is only necessary to compare the NDI of the second downlink allocation corresponding to the group common scheduling (i.e., g-RNTI) of the previous same HARQ process (i.e., the target HARQ process) with the first downlink allocation. If the RNTI corresponding to the second downlink allocation of the previous same HARQ process is C-RNTI, TC-RNTI, or CS-RNTI, or the second downlink allocation is a configured unicast downlink allocation or a configured group common downlink allocation, then regardless of the value of NDI, the NDI corresponding to the HARQ process is considered to be reversed.

[0087] Alternatively, when the RNTI corresponding to the first downlink allocation received by the terminal device is c-RNTI or TC-RNTI, it is only necessary to compare the first downlink allocation with the NDI of the second downlink allocation corresponding to the unicast scheduling of the same HARQ process. If the RNTI corresponding to the second downlink allocation of the same HARQ process is g-RNTI or group common CS-RNTI, or the second downlink allocation is a configured group common downlink allocation, then regardless of the value of NDI, the NDI is considered to be reversed.

[0088] Example 2

[0089] If the terminal device is configured with the aforementioned mode 2, that is, the group-common PDSCH is retransmitted only through the unicast PDSCH scheduled by the unicast PDCCH, then when the terminal device supports both multicast service reception and unicast service reception, the group-common PDSCH can only be retransmitted through the group-common PDSCH scheduled by the group-common PDCCH, and the unicast PDSCH can only be retransmitted through the unicast PDSCH scheduled by the unicast PDCCH. In this case, in a PDCCH detection opportunity, if the terminal device receives the first downlink allocation, then it can be determined based on at least one of the following (1)-(4) whether the NDI corresponding to the HARQ process is inverted or not.

[0090] (1) When the RNTI corresponding to the first downlink allocation is a g-RNTI and the first downlink allocation is the first downlink allocation, regardless of the value of the NDI, it is determined that the NDI corresponding to the target HARQ process is inverted.

[0091] (2) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is scrambled by the first RNTI, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDIs indicated by the first downlink allocation and the second downlink allocation, respectively, wherein the first RNTI is any one of a g-RNTI, a C-RNTI, and a TC-RNTI. The second downlink allocation is a previous downlink allocation for the same HARQ process and the same HARQ entity as the first downlink allocation.

[0092] (3) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI and the RNTI corresponding to the second downlink allocation is a CS-RNTI, regardless of the value of the NDI, determining that the NDI corresponding to the target HARQ process is inverted, wherein the second downlink allocation is a previous downlink allocation indicating the same HARQ entity and the same HARQ process as the first downlink allocation.

[0093] (4) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI and the second downlink allocation is a configured downlink allocation, regardless of the value of the NDI, determining that the NDI corresponding to the target HARQ process is inverted, wherein the second downlink allocation is a previous downlink allocation indicating the same HARQ entity and the same HARQ process as the first downlink allocation.

[0094] It can be understood that in (1)-(4) given in Example 2, when the terminal device receives the first downlink allocation corresponding to the g-RNTI, regardless of the value of the NDI, the NDI is considered to be inverted. Similarly, when the terminal receives the first downlink allocation corresponding to the c-RNTI or TC-RNTI, if there is a second downlink allocation for the same HARQ process, regardless of whether the RNTI of the second downlink allocation is C-RNTI or g-RNTI, it is determined whether the NDI is inverted based on the NDI values ​​of the two downlink allocations.

[0095] In addition, it should be noted that when the terminal device is configured as the aforementioned mode 3 or mode 5, the process of determining whether the NDI corresponding to the target HARQ process is reversed or not can refer to the aforementioned example 2. To avoid repetition, it will not be repeated here.

[0096] Example 3

[0097] If the terminal device is configured with the aforementioned mode 4, that is, the group-common PDSCH can be retransmitted via both the group-common PDSCH scheduled by the group-common PDCCH and the unicast PDSCH scheduled by the unicast PDCCH, then when the UE supports both multicast service reception and unicast service reception. In a PDCCH detection opportunity, the terminal device receives the first downlink allocation, then, it can be determined based on at least one of the following (1)-(10) whether the NDI corresponding to the target HARQ process is inverted or not.

[0098] (1) When the RNTI corresponding to the first downlink allocation is g-RNTI scrambled and the RNTI corresponding to the second downlink allocation is C-RNTI or CS-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0099] (2) When the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0100] (3) When the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a group common CS-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0101] (4) when the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured multicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted;

[0102] (5) When the RNTI corresponding to the first downlink assignment is a g-RNTI and the RNTI corresponding to the second downlink assignment is a g-RNTI, determining whether the NDI corresponding to the target HARQ is inverted based on the values ​​of the NDIs indicated by the first downlink assignment and the second downlink assignment, respectively. The second downlink assignment is a previous downlink assignment indicating the same HARQ entity and the same HARQ process as the first downlink assignment.

[0103] (6) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a second RNTI, determining whether the NDI is reversed according to the NDI values ​​respectively indicated by the first downlink allocation and the second downlink allocation, wherein the second RNTI is any one of a g-RNTI, a C-RNTI, and a TC-RNTI; and wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0104] (7) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a group common CS-RNTI, determining whether the NDI is reversed according to the NDI values ​​respectively indicated by the first downlink allocation and the second downlink allocation, wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0105] (8) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a CS-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0106] (9) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI and the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted, wherein the second downlink allocation is a previous downlink allocation for the same HARQ process and the same HARQ entity as the first downlink allocation.

[0107] (10) When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI and the second downlink allocation is a configured multicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted. The second downlink allocation is a previous downlink allocation for the same HARQ process and the same HARQ entity as the first downlink allocation.

[0108] It can be understood that in (1)-(10) in the aforementioned Example 3, when the terminal device receives the first downlink allocation corresponding to the g-RNTI, it only needs to compare it with the NDI of the second downlink allocation corresponding to the g-RNTI of the same HARQ process. If the second downlink allocation of the same HARQ process corresponds to C-RNTI or TC-RNTI or CS-RNTI, or the second downlink allocation is a configured unicast downlink allocation, the value of NDI is ignored, that is, the NDI is considered to be reversed.

[0109] When the terminal device receives the first downlink allocation corresponding to c-RNTI or TC-RNTI, regardless of whether the second downlink allocation of the same HARQ process corresponds to g-RNTI or C-RNTI, it determines whether the NDI is reversed based on the values ​​of the NDI indicated by the two downlink allocations.

[0110] In addition, it should be noted that when the terminal device is configured as the aforementioned method 6, the process of determining whether the NDI corresponding to the target HARQ process is inverted or not can refer to the aforementioned example 3. To avoid repetition, it will not be repeated here.

[0111] S430: Determine whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not.

[0112] Among them, the implementation process of S430 can refer to the relevant description in the aforementioned method embodiment 200 or 300, and will not be repeated here to avoid repetition.

[0113] In this embodiment, the terminal device determines whether the NDI corresponding to the target HARQ process is inverted or not inverted in combination with the retransmission mode of the group-common PDSCH and the RNTI corresponding to the first downlink allocation, and then determines whether the TB associated with the target HARQ process is a new transmission or a retransmission based on whether the NDI is inverted or not. This can solve the problem that the network side device cannot use the HARQ process to schedule the group-common PDSCH, or cannot indicate the NDI corresponding to the HARQ process, while also improving the effectiveness of the communication system.

[0114] It should be noted that the downlink scheduling methods 200-400 provided in the embodiments of the present application may be performed by a downlink scheduling device, or a control module in the downlink scheduling device for performing the downlink scheduling methods 200-400. The subsequent sections of the embodiments of the present application use the downlink scheduling device performing the downlink scheduling method as an example to illustrate the downlink scheduling device provided in the embodiments of the present application.

[0115] like Figure 5 As shown, a block diagram of a downlink scheduling device 500 provided in an exemplary embodiment of the present application is provided, and the downlink scheduling device 500 includes: a receiving module 510, used to receive a first downlink allocation transmitted via a first PDCCH; a first determination module 520, used to determine whether the NDI corresponding to the target HARQ process is inverted or not inverted according to the RNTI corresponding to the first downlink allocation, and the target HARQ process is the HARQ process corresponding to the first downlink allocation; a second determination module 530, used to determine whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not inverted.

[0116] As a possible implementation manner, the first determining module 520 is configured to do at least one of the following: when the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a C-RNTI, a TC-RNTI, or a CS-RNTI, determine that the NDI corresponding to the target HARQ process is inverted;

[0117] In a case where the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; in a case where the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a group-common CS-RNTI or the second downlink allocation is a configured group-common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; in a case where the RNTI corresponding to the first downlink allocation and the RNTI corresponding to the second downlink allocation are both g-RNTI, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDI respectively indicated by the first downlink allocation and the second downlink allocation; in a case where the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI and the RNTI corresponding to the second downlink allocation is a g-RNTI or a group-common CS-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; in a case where the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI, and when the second downlink allocation is a configured group common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; when the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is a CS-RNTI, or the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; when the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is a c-RNTI or TC-RNTI, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDIs respectively indicated by the first downlink allocation and the second downlink allocation; when the RNTI corresponding to the first downlink allocation is a g-RNTI, and the first downlink allocation is the first downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is a previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0118] As another possible implementation, the first determination module 520 is configured to determine whether the NDI corresponding to the target HARQ process is inverted or not according to a retransmission mode of at least one group common physical downlink shared channel PDSCH and the RNTI corresponding to the first downlink allocation.

[0119] As another possible implementation method, the retransmission method of the group-common PDSCH includes at least one of the following: Method 1: group-common PDSCH scheduled by group-common PDCCH; Method 2: unicast PDSCH scheduled by unicast PDCCH; Method 3: group-common PDSCH scheduled by unicast PDCCH.

[0120] As another possible implementation manner, the retransmission mode of the at least one group-common PDSCH is configured for the terminal device by a network-side device through high-layer signaling.

[0121] As another possible implementation, the second determination module is used to determine that the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission when the NDI is inverted; and, when the NDI is not inverted, determine that the TB scheduled by the first PDCCH and associated with the target HARQ process is a retransmission.

[0122] As another possible implementation method, when the first PDCCH is a unicast PDCCH and the unicast PDSCH or group common PDSCH is scheduled by the first PDCCH, the first PDCCH is encrypted by a specific RNTI; wherein the specific RNTI is different from the specified RNTI, and the specified RNTI is the RNTI used when scheduling the unicast PDSCH.

[0123] As another possible implementation manner, the designated RNTI includes any one of C-RNTI, TC-RNTI, CS-RNTI, and g-RNTI.

[0124] As another possible implementation method, when the first PDCCH is a unicast PDCCH and a unicast PDSCH or a group-common PDSCH is scheduled by the first PDCCH, the downlink control information DCI carried by the first PDCCH includes a specific bit field, and the specific bit field is used to indicate whether the PDSCH scheduled by the unicast PDCCH is a retransmission of a unicast PDSCH or a groupcast PDSCH.

[0125] In this embodiment, the RNTI corresponding to the detected first downlink allocation is used to determine whether the corresponding NDI of the target HARQ is inverted or not, and then whether the TB associated with the target HARQ process is newly transmitted or retransmitted is determined based on whether the NDI is inverted or not. This can solve the problem that the network side device cannot use the HARQ process scheduling group common PDSCH, or cannot indicate the NDI corresponding to the HARQ process, while also improving the effectiveness of the communication system.

[0126] The downlink scheduling device in the embodiments of the present application can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. The device or electronic device can be a mobile terminal or a non-mobile terminal. For example, mobile terminals can include, but are not limited to, the types of terminals 11 listed above, and non-mobile terminals can include servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc., and the embodiments of the present application do not specifically limit this.

[0127] The downlink scheduling device provided in the embodiment of the present application can achieve Figures 2 to 4 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0128] Furthermore, an embodiment of the present application also provides a terminal, comprising a processor and a communication interface, wherein the processor and the communication interface are coupled, and the processor executes a program or instruction to implement method embodiments 200-400. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this terminal embodiment and can achieve the same technical effects.

[0129] Specifically, Figure 6 This is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application. The terminal 600 includes, but is not limited to, at least some of the components including a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, and a processor 610.

[0130] Those skilled in the art will understand that the terminal 600 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 610 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 6 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.

[0131] It should be understood that in an embodiment of the present application, the input unit 604 may include a graphics processing unit (GPU) 1041 and a microphone 6042, and the graphics processor 6041 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 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 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.

[0132] In this embodiment of the present application, the radio frequency unit 601 receives downlink data from the network-side device and transmits it to the processor 610 for processing. Furthermore, the radio frequency unit 601 transmits uplink data to the network-side device. Typically, the radio frequency unit 601 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.

[0133] The memory 609 can be used to store software programs or instructions and various data. The memory 609 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 609 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.

[0134] Processor 610 may include one or more processing units. Optionally, processor 610 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 610.

[0135] Among them, the processor 610 is used to receive a first downlink allocation transmitted through a first PDCCH; determine whether the NDI corresponding to the target HARQ process is inverted or not inverted according to the RNTI corresponding to the first downlink allocation, and the target HARQ process is the HARQ process corresponding to the first downlink allocation; determine whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not.

[0136] The processor 610 determines, based on the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted, including at least one of the following: when the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a C-RNTI or a TC-RNTI or a CS-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; when the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; when the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When I is a g-RNTI and the RNTI corresponding to the second downlink allocation is a group common CS-RNTI or the second downlink allocation is a configured group common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; when the RNTI corresponding to the first downlink allocation and the RNTI corresponding to the second downlink allocation are both g-RNTI, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDI respectively indicated by the first downlink allocation and the second downlink allocation; when the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is a g-RNTI In the case where the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI and the second downlink allocation is a configured group common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; in the case where the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI and the RNTI corresponding to the second downlink allocation is a CS-RNTI or the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; in the case where the RNTI corresponding to the first downlink allocation is a c-RNTI or TC-RNTI and the RNTI corresponding to the second downlink allocation is a CS-RNTI or the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When the RNTI corresponding to the first downlink allocation is c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is c-RNTI or TC-RNTI, determine whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDI respectively indicated by the first downlink allocation and the second downlink allocation; when the RNTI corresponding to the first downlink allocation is g-RNTI, and the first downlink allocation is the first downlink allocation, determine that the NDI corresponding to the target HARQ process is inverted; wherein the second downlink allocation is the previous downlink allocation of the same HARQ process indicating the same HARQ entity as the first downlink allocation.

[0137] As a possible implementation method, the processor 610 determines whether the NDI corresponding to the target HARQ process is inverted or not inverted based on the RNTI corresponding to the first downlink allocation, including: determining whether the NDI corresponding to the target HARQ process is inverted or not inverted based on the retransmission method of at least one group common physical downlink shared channel PDSCH and the RNTI corresponding to the first downlink allocation.

[0138] As a possible implementation method, the retransmission method of the group-common PDSCH includes at least one of the following: Method 1: group-common PDSCH scheduled by group-common PDCCH; Method 2: unicast PDSCH scheduled by unicast PDCCH; Method 3: group-common PDSCH scheduled by unicast PDCCH;.

[0139] As a possible implementation manner, the retransmission mode of the at least one group-common PDSCH is configured for the terminal device by a network-side device through high-layer signaling.

[0140] As a possible implementation method, the processor 610 determines whether the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission according to whether the NDI corresponding to the target HARQ process is inverted or not, including: when the NDI is inverted, determining that the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission; when the NDI is not inverted, determining that the TB scheduled by the first PDCCH and associated with the target HARQ process is a retransmission.

[0141] As a possible implementation method, when the first PDCCH is a unicast PDCCH and the unicast PDSCH or group common PDSCH is scheduled by the first PDCCH, the first PDCCH is encrypted by a specific RNTI; wherein the specific RNTI is different from the specified RNTI, and the specified RNTI is the RNTI used when scheduling the unicast PDSCH.

[0142] As a possible implementation manner, the designated RNTI includes any one of C-RNTI, TC-RNTI, CS-RNTI, and g-RNTI.

[0143] As a possible implementation method, when the first PDCCH is a unicast PDCCH and a unicast PDSCH or a group-common PDSCH is scheduled by the first PDCCH, the downlink control information DCI carried by the first PDCCH includes a specific bit field, and the specific bit field is used to indicate whether the PDSCH scheduled by the unicast PDCCH is a retransmission of a unicast PDSCH or a groupcast PDSCH.

[0144] The terminal device determines whether the NDI corresponding to the target HARQ is inverted or not by detecting the RNTI corresponding to the first downlink allocation, and then determines whether the TB associated with the target HARQ process is a new transmission or a retransmission based on whether the NDI is inverted or not. This can solve the problem that the network side device cannot use the HARQ process scheduling group common PDSCH, or cannot indicate the NDI corresponding to the HARQ process, while also improving the effectiveness of the communication system.

[0145] 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 the processor, the various processes of the above-mentioned downlink scheduling method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0146] The processor is the processor in the terminal 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.

[0147] 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 downlink scheduling method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0148] 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.

[0149] An embodiment of the present application also provides a computer program product, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the various processes of the above-mentioned downlink scheduling method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0150] 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.

[0151] 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 computer 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 network device, etc.) to execute the methods described in each embodiment of the present application.

[0152] 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 downlink scheduling method, characterized in that: Executed by a terminal device, the method includes: receiving a first downlink allocation transmitted via a first physical downlink control channel (PDCCH); determining, based on the Radio Network Temporary Identifier (RNTI) corresponding to the first downlink assignment, whether an NDI corresponding to a target hybrid automatic repeat request (HARQ) process is inverted or not inverted, the target HARQ process being the HARQ process corresponding to the first downlink assignment; Determining, according to whether the NDI corresponding to the target HARQ process is inverted or not inverted, whether the transport block TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission; The determining, according to the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted includes at least one of the following: determining that the NDI corresponding to the target HARQ process is inverted if the RNTI corresponding to the first downlink allocation is a group g-RNTI and the RNTI corresponding to the second downlink allocation is a cell C-RNTI or a configured granted CS-RNTI or a group common CS-RNTI or the second downlink allocation is a configured unicast downlink allocation or a group common downlink allocation; When the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a TC-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; When both the RNTI corresponding to the first downlink allocation and the RNTI corresponding to the second downlink allocation are g-RNTIs, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDIs indicated by the first downlink allocation and the second downlink allocation respectively; determining that the NDI corresponding to the target HARQ process is inverted if the RNTI corresponding to the first downlink allocation is a c-RNTI and the RNTI corresponding to the second downlink allocation is a g-RNTI or a group-common CS-RNTI or a CS-RNTI or the second downlink allocation is a configured group-common downlink allocation or a unicast downlink allocation; determining that the NDI corresponding to the target HARQ process is inverted, if the RNTI corresponding to the first downlink allocation is a TC-RNTI and the RNTI corresponding to the second downlink allocation is a g-RNTI or a group-common CS-RNTI or a CS-RNTI or the second downlink allocation is a configured group-common downlink allocation or a unicast downlink allocation; When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a c-RNTI or a TC-RNTI, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDIs indicated by the first downlink allocation and the second downlink allocation, respectively; When the RNTI corresponding to the first downlink allocation is a g-RNTI and the first downlink allocation is a first downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; The second downlink allocation is a previous downlink allocation indicating the same HARQ entity and the same HARQ process as the first downlink allocation.

2. The method according to claim 1, wherein Determining, according to the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted further includes at least one of the following: When the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a group-common CS-RNTI or the second downlink allocation is a configured group-common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the second downlink allocation is a configured group common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When the RNTI corresponding to the first downlink allocation is c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is CS-RNTI, or the second downlink allocation is a configured unicast downlink allocation, it is determined that the NDI corresponding to the target HARQ process is inverted.

3. The method according to claim 1 or 2, wherein: Determining, according to the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted, further comprising: It is determined whether the NDI corresponding to the target HARQ process is inverted or not inverted according to a retransmission mode of at least one group-common physical downlink shared channel (PDSCH) and an RNTI corresponding to the first downlink allocation.

4. The method according to claim 3, wherein The retransmission mode of the group common PDSCH includes at least one of the following: Mode 1: Group-common PDSCH scheduled by group-common PDCCH; Mode 2: Unicast PDSCH scheduled by unicast PDCCH; Mode 3: Group-common PDSCH scheduled by unicast PDCCH.

5. The method according to claim 3, wherein The retransmission mode of the at least one group-common PDSCH is configured for the terminal device by a network-side device through high-layer signaling.

6. The method according to claim 1, wherein Determining, according to whether the NDI corresponding to the target HARQ process is inverted or not inverted, whether a TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission, includes: In a case where the NDI is inverted, determining that the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission; In a case where the NDI is not inverted, it is determined that the TB scheduled by the first PDCCH and associated with the target HARQ process is a retransmission.

7. The method according to claim 1, wherein In a case where the first PDCCH is a unicast PDCCH and a unicast PDSCH or a group-common PDSCH is scheduled by the first PDCCH, the first PDCCH is scrambled by a specific RNTI; The specific RNTI is different from the designated RNTI, and the designated RNTI is the RNTI used when scheduling the unicast PDSCH.

8. The method according to claim 7, wherein The designated RNTI includes any one of C-RNTI, TC-RNTI, CS-RNTI, and g-RNTI.

9. The method according to claim 1, wherein When the first PDCCH is a unicast PDCCH and a unicast PDSCH or a group-common PDSCH is scheduled by the first PDCCH, the downlink control information DCI carried by the first PDCCH includes a specific bit field, and the specific bit field is used to indicate whether the PDSCH scheduled by the unicast PDCCH is a retransmission of a unicast PDSCH or a groupcast PDSCH.

10. A downlink scheduling device, characterized in that: The device comprises: A receiving module, configured to receive a first downlink allocation transmitted via a first physical downlink control channel PDCCH; a first determining module, configured to determine, based on the radio network temporary identifier RNTI corresponding to the first downlink allocation, whether an NDI corresponding to a target hybrid automatic repeat request HARQ process is inverted or not inverted, the target HARQ process being the HARQ process corresponding to the first downlink allocation; A second determining module is configured to determine, according to whether the NDI corresponding to the target HARQ process is inverted or not inverted, whether the transport block TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission or a retransmission; The determining, according to the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted includes at least one of the following: determining that the NDI corresponding to the target HARQ process is inverted if the RNTI corresponding to the first downlink allocation is a group g-RNTI and the RNTI corresponding to the second downlink allocation is a cell C-RNTI or a configured granted CS-RNTI or a group common CS-RNTI or the second downlink allocation is a configured unicast downlink allocation or a group common downlink allocation; When the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a TC-RNTI, determining that the NDI corresponding to the target HARQ process is inverted; When both the RNTI corresponding to the first downlink allocation and the RNTI corresponding to the second downlink allocation are g-RNTIs, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDIs indicated by the first downlink allocation and the second downlink allocation respectively; determining that the NDI corresponding to the target HARQ process is inverted if the RNTI corresponding to the first downlink allocation is a c-RNTI and the RNTI corresponding to the second downlink allocation is a g-RNTI or a group-common CS-RNTI or a CS-RNTI or the second downlink allocation is a configured group-common downlink allocation or a unicast downlink allocation; determining that the NDI corresponding to the target HARQ process is inverted, if the RNTI corresponding to the first downlink allocation is a TC-RNTI and the RNTI corresponding to the second downlink allocation is a g-RNTI or a group-common CS-RNTI or a CS-RNTI or the second downlink allocation is a configured group-common downlink allocation or a unicast downlink allocation; When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the RNTI corresponding to the second downlink allocation is a c-RNTI or a TC-RNTI, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDIs indicated by the first downlink allocation and the second downlink allocation, respectively; When the RNTI corresponding to the first downlink allocation is a g-RNTI and the first downlink allocation is a first downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; The second downlink allocation is a previous downlink allocation indicating the same HARQ entity and the same HARQ process as the first downlink allocation.

11. The device according to claim 10, characterized in that The determining, based on the RNTI corresponding to the first downlink allocation, whether the NDI corresponding to the target HARQ process is inverted or not inverted further includes at least one of the following: When the RNTI corresponding to the first downlink allocation is a g-RNTI and the second downlink allocation is a configured unicast downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When the RNTI corresponding to the first downlink allocation is a g-RNTI and the RNTI corresponding to the second downlink allocation is a group-common CS-RNTI or the second downlink allocation is a configured group-common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When both the RNTI corresponding to the first downlink allocation and the RNTI corresponding to the second downlink allocation are g-RNTIs, determining whether the NDI corresponding to the target HARQ process is inverted according to the values ​​of the NDIs indicated by the first downlink allocation and the second downlink allocation respectively; When the RNTI corresponding to the first downlink allocation is a c-RNTI or a TC-RNTI, and the second downlink allocation is a configured group common downlink allocation, determining that the NDI corresponding to the target HARQ process is inverted; When the RNTI corresponding to the first downlink allocation is c-RNTI or TC-RNTI, and the RNTI corresponding to the second downlink allocation is CS-RNTI, or the second downlink allocation is a configured unicast downlink allocation, it is determined that the NDI corresponding to the target HARQ process is inverted.

12. The device according to claim 10 or 11, characterized in that The first determining module is configured to determine whether the NDI corresponding to the target HARQ process is inverted or not inverted according to a retransmission mode of at least one group common physical downlink shared channel PDSCH and an RNTI corresponding to the first downlink allocation.

13. The device according to claim 12, wherein The retransmission mode of the group common PDSCH includes at least one of the following: Mode 1: Group-common PDSCH scheduled by group-common PDCCH; Mode 2: Unicast PDSCH scheduled by unicast PDCCH; Mode 3: Group-common PDSCH scheduled by unicast PDCCH.

14. The device according to claim 12, wherein The retransmission mode of the at least one group-common PDSCH is configured for the terminal device by the network side device through high-layer signaling.

15. The device according to claim 10, wherein The second determining module is configured to determine, when the NDI is inverted, that the TB scheduled by the first PDCCH and associated with the target HARQ process is a new transmission; as well as, In a case where the NDI is not inverted, it is determined that the TB scheduled by the first PDCCH and associated with the target HARQ process is a retransmission.

16. The device according to claim 10, wherein In a case where the first PDCCH is a unicast PDCCH and a unicast PDSCH or a group-common PDSCH is scheduled by the first PDCCH, the first PDCCH is scrambled by a specific RNTI; The specific RNTI is different from the designated RNTI, and the designated RNTI is the RNTI used when scheduling the unicast PDSCH.

17. The device according to claim 16, wherein The designated RNTI includes any one of C-RNTI, TC-RNTI, CS-RNTI, and g-RNTI.

18. The device according to claim 10, wherein When the first PDCCH is a unicast PDCCH and a unicast PDSCH or a group-common PDSCH is scheduled by the first PDCCH, the downlink control information DCI carried by the first PDCCH includes a specific bit field, and the specific bit field is used to indicate whether the PDSCH scheduled by the unicast PDCCH is a retransmission of a unicast PDSCH or a groupcast PDSCH.

19. A terminal, characterized in that: It includes 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 downlink scheduling method according to any one of claims 1 to 9.

20. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the downlink scheduling method according to any one of claims 1 to 9 are implemented.

Images