User Equipment, Base Station, and Their Methods

Abstract

According to the present invention, a method performed by a user equipment UE is provided, including: identifying a hybrid automatic repeat request HARQ process corresponding to the received uplink scheduling for the received uplink scheduling; determining whether the uplink scheduling is for a new transmission or for a retransmission; in the case where it is determined that the uplink scheduling is for a new transmission, for an uplink scheduling whose physical uplink shared channel PUSCH duration does not overlap with the PUSCH durations of other uplink schedulings, or an uplink scheduling whose PUSCH duration overlaps only with the PUSCH durations of other uplink schedulings with lower priorities, or a dynamic uplink scheduling whose PUSCH duration does not overlap with the PUSCH durations of other configured uplink schedulings with higher priorities, if the corresponding MAC PDU, i.e., the media access control protocol data unit, is obtained, then indicating that the identified HARQ process triggers a new transmission of the MAC PDU.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies, and more particularly, to user equipment, a base station, and methods thereof. Background Art

[0002] In March 2019, a work item supporting NR industrial Internet of Things was approved at the 83rd plenary session of the 3rd Generation Partnership Project (3GPP) RAN (see non-patent document: RP-190728: New WID: Support of NR Industrial Internet of Things (IoT)). In industrial application scenarios, user equipment (UE) needs to simultaneously process data flows from different applications or devices. Therefore, it is necessary to consider the priority processing and / or multiplexing when uplink / downlink data channels and control channels conflict within the UE, and the handling of resource conflicts between dynamic grants and configured grants, and between two or more configured grants. Accordingly, one of the purposes of this work item is to enhance the resolution of resource conflicts between dynamic grants and configured grants, and between two or more configured grants. If the media access control MAC (Medium Access Control) processes scheduling priorities, the 3GPP Working Group 2 (RAN2) needs to define a physical uplink shared channel (PUSCH) scheduling priority processing mechanism based on logical channel (LCH) priorities and logical channel priority (LCP) restrictions.

[0003] At the 3GPP RAN2 #105bis meeting held in April 2019, it was agreed that when multiple Configured Uplink Grants (CGs) or Downlink Semi-Persistent Scheduling (SPSs) are configured, an offset for calculating the Hybrid Automatic Repeat Request (HARQ) process number is configured for each CG or SPS. The purpose of this conclusion is to map different configured uplink schedulings (or downlink SPSs) to different HARQ processes, so that the HARQ processes associated with, mapped to, or used by the configured uplink schedulings (or downlink SPSs) are different or non-overlapping. At the 3GPP RAN2 #106 meeting held in May 2019, it was agreed that for the dynamic scheduling of low-priority PUSCH, the UE stores the corresponding low-priority MAC PDU in the HARQ buffer, so that the gNB can schedule re-transmission using the same HARQ process (For de-prioritized PUSCH on dynamic grant, the UE should store the de-prioritized MAC PDU in the HARQ buffer, to allow gNB to schedule re-transmission using the same HARQ process); for the configured uplink scheduling of low-priority PUSCH, a) the UE stores the corresponding low-priority MAC PDU in the HARQ buffer, so that the gNB can schedule re-transmission, b) it needs to be further discussed whether the UE can perform re-transmission on subsequent radio resources, such as using radio resources subsequently associated with the same HARQ process (For de-prioritized PUSCH on configured grants, a) the UE could store the de-prioritized MAC PDU in the HARQ buffer, to allow gNB to schedule re-transmission. b) FFS if the UE could transmit it using the subsequent radio resources e.g. associated with the same HARQ process); the above conclusions apply at least to the case where the MAC entity has generated a MAC PDU for the dynamic scheduling or configured uplink scheduling of low-low priority.

[0004] Based on the above - reached conclusion, when a lower - priority MAC PDU is stored in the HARQ buffer and there is an available uplink scheduling at this time (which can be dynamic scheduling or configured scheduling), and this uplink scheduling cannot be used to transmit the MAC PDU in the buffer. At this time, how the UE processes the available uplink scheduling is a problem that needs to be considered. Figure 1 An example description of this problem is given. At T1, there is a conflict between the dynamic scheduling DG1 and the configured scheduling CG of different HARQ processes. The dynamic scheduling has a higher priority, and the MAC PDU generated for the configured scheduling CG is stored in the buffer. At T2, a dynamic scheduling DG2 is received and DG2 has the same HARQ process as the configured scheduling CG. At this time, because the MAC PDU generated for CG is still stored in the buffer of the corresponding HARQ process, when the priority of DG2 is lower than that of CG, should a MAC PDU be generated for DG2 to overwrite the MAC PDU in the buffer? In addition, when the UE has multiple available uplink schedulings and there is a PUSCH duration overlap between these uplink schedulings, how to select an uplink scheduling to send data is a problem that needs to be considered. Summary of the Invention

[0005] To solve at least a part of the above - mentioned problems, the present invention provides a user equipment, a base station and their methods, which can solve the DG / CG PUSCH conflicts of different HARQ processes, CG / CG conflicts of different HARQ processes and the uplink scheduling / MAC PDU conflicts of the same HARQ process by setting an enabling priority indication flag.

[0006] To achieve the above object, according to the present invention, a method executed by a user equipment UE is proposed, including: identifying a hybrid automatic repeat request HARQ process corresponding to the received uplink scheduling; judging whether the uplink scheduling is for new transmission or for re - transmission; in the case where it is judged that the uplink scheduling is for new transmission, for an uplink scheduling whose physical uplink shared channel PUSCH duration does not overlap with the PUSCH durations of other uplink schedulings, or an uplink scheduling whose PUSCH duration overlaps only with the PUSCH durations of other lower - priority uplink schedulings, or a dynamic uplink scheduling whose PUSCH duration does not overlap with the PUSCH durations of other higher - priority configured uplink schedulings, if the corresponding MAC PDU, i.e., the media access control protocol data unit, is obtained, then indicating the identified HARQ process to trigger the new transmission of the MAC PDU.

[0007] Preferably, if the corresponding MAC PDU cannot be obtained, the HARQ buffer of the identified HARQ process is cleared or the configured scheduling timer of the identified HARQ process is stopped.

[0008] Preferably, in the case where it is determined that the uplink scheduling is for retransmission, if the uplink scheduling is indicated by a Physical Downlink Control Channel (PDCCH), and / or the Physical Uplink Shared Channel (PUSCH) duration of the uplink scheduling overlaps with the PUSCH duration of another uplink scheduling with a higher priority, then the uplink scheduling is ignored.

[0009] Preferably, in the case where it is determined that the uplink scheduling is for new transmission, if a first enable priority indication flag is configured and the value of the indication flag is a first predefined value, then for an uplink scheduling whose PUSCH duration does not overlap with the PUSCH duration of other uplink schedulings, or an uplink scheduling whose PUSCH duration only overlaps with the PUSCH duration of other uplink schedulings with a lower priority, or a dynamic uplink scheduling whose PUSCH duration does not overlap with the PUSCH duration of other configured uplink schedulings with a higher priority, if the corresponding Media Access Control Protocol Data Unit (MAC PDU) is obtained, then it is indicated that the identified Hybrid Automatic Repeat reQuest (HARQ) process triggers the new transmission of the MAC PDU.

[0010] Preferably, if the received uplink scheduling is a configured uplink scheduling and its priority is higher than the priority of the configured uplink scheduling on the same HARQ process or the priority of the MAC PDU that has not been transmitted or is waiting for initial transmission in the HARQ buffer of the same HARQ process, then the MAC PDU corresponding to the received configured uplink scheduling is obtained, and it is indicated that the identified HARQ process triggers the new transmission of the obtained MAC PDU.

[0011] Preferably, for an uplink scheduling whose PUSCH duration overlaps with the PUSCH duration of other uplink schedulings with a higher priority, if the uplink scheduling is for new transmission and the corresponding MAC PDU is obtained, then the obtained MAC PDU is handed over to the identified HARQ process, and it is indicated that the identified HARQ process does not trigger the new transmission of the MAC PDU; for an uplink scheduling whose PUSCH duration overlaps with the PUSCH duration of other uplink schedulings with a higher priority, if the uplink scheduling is for new transmission and the corresponding MAC PDU is not obtained, then the HARQ buffer of the identified HARQ process is cleared or the configured scheduling timer of the identified HARQ process is stopped.

[0012] Preferably, the priority of the dynamic uplink scheduling is indicated in the corresponding Downlink Control Information (DCI), and the priority of the configured uplink scheduling is configured by the base station through Radio Resource Control (RRC) signaling.

[0013] In addition, according to the present invention, a user equipment is provided, including: a processor; and a memory storing instructions; wherein, the instructions, when run by the processor, execute the above-mentioned method.

[0014] Furthermore, according to the present invention, a method performed by a base station is provided, including: indicating to a user equipment UE a priority for dynamic uplink scheduling and / or a priority for configured uplink scheduling, and according to the priority indicated by the base station, the UE executes the above-mentioned method.

[0015] In addition, according to the present invention, a base station is provided, including: a processor; and a memory storing instructions, wherein, the instructions, when run by the processor, execute the above-mentioned method.

[0016] According to the present invention as described above, it is possible to solve different HARQ process DG / CG PUSCH conflicts, different HARQ process CG / CG conflicts, and the same HARQ process uplink scheduling / MAC PDU conflicts by setting an enabling priority indication flag. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Through the following detailed description in conjunction with the drawings, the above and other features of the present disclosure will become more obvious, wherein:

[0018] Figure 1 A schematic diagram showing uplink scheduling conflicts is shown.

[0019] Figure 2 It is a flowchart showing the method performed by a user equipment according to Embodiment 1 of the present invention.

[0020] Figure 3 It is a flowchart showing the method performed by a user equipment according to Embodiment 2 of the present invention.

[0021] Figure 4 It is a flowchart showing the method performed by a user equipment according to Embodiment 3 of the present invention.

[0022] Figure 5 It is a flowchart showing the method performed by a user equipment according to Embodiment 4 of the present invention.

[0023] Figure 6 It is a schematic block diagram showing the user equipment involved in the present invention.

[0024] Figure 7 It is a schematic block diagram showing the base station involved in the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0025] The present disclosure will be described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below. In addition, for the sake of simplicity, the detailed description of well-known technologies that have no direct relation to the present disclosure is omitted to prevent confusion in the understanding of the present disclosure.

[0026] Some terms related to the present disclosure are described below. Unless otherwise specified, the terms are the same as those used in the current latest version of the 3GPP protocol, and are excerpted as follows.

[0027] RRC: Radio Resource Control, wireless resource control.

[0028] MAC: Medium Access Control, media access control.

[0029] PDCCH: Physical Downlink Control Channel, physical downlink control channel.

[0030] PUSCH: Physical Uplink Shared Channel, physical uplink shared channel.

[0031] SDU: Service Data Unit, service data unit.

[0032] PDU: Protocol Data Unit, protocol data unit.

[0033] CG: Configured uplink Grant, configured scheduling or configured uplink scheduling.

[0034] DG: Dynamic Grant, dynamic scheduling, which refers to the uplink scheduling dynamically received on the PDCCH. In other words, the uplink scheduling received on the PDCCH is for the C-RNTI or TC-RNTI (Temporary C-RNTI) of the MAC entity or the uplink scheduling received on the PDCCH is for the CS-RNTI of the MAC entity (this uplink scheduling is used for the retransmission of the MAC PDU transmitted on the configured uplink scheduling, and it is considered that the NDI value does not flip when the received NDI value is 1). The uplink scheduling received on the PDCCH for the C-RNTI or TC-RNTI (Temporary C-RNTI) or CS-RNTI of the MAC entity is the uplink scheduling indicated by the PDCCH scrambled by the C-RNTI or TC-RNTI or CS-RNTI of the MAC entity, and these two expressions can be used interchangeably.

[0035] HARQ information: The HARQ information for DL-SCH or UL-SCH transmission consists of a New Data Indicator (NDI), a Transport Block size (TBS), a Redundancy Version (RV), and a HARQ process ID.

[0036] CS-RNTI: Configured Scheduling RNTI, which is the configured scheduling RNTI.

[0037] ra-ResponseWindow: Random access response window. The UE receives a random access response within the random access response window.

[0038] In the present disclosure, on a serving cell, the situation where the PUSCH duration of dynamic scheduling DG on a certain HARQ process overlaps with the PUSCH duration of configured scheduling CG on another HARQ process is called different HARQ process DG / CG PUSCH conflict or different HARQ process DG / CG conflict. On a serving cell, the situation where the PUSCH duration of configured scheduling CG on a certain HARQ process overlaps with the PUSCH duration of configured scheduling CG on another HARQ process is called different HARQ process CG / CG PUSCH conflict or different HARQ process CG / CG conflict. The situation where the PUSCH duration of dynamic scheduling DG on a certain HARQ process overlaps with the PUSCH duration of configured scheduling CG on the same HARQ process is called the same HARQ process DG / CG conflict. The conflict that occurs between the uplink scheduling on a certain HARQ process and the MAC PDU that has not been sent (or has been sent but not yet confirmed as successfully sent) stored in the HARQ buffer of this HARQ process (this kind of conflict is mainly the conflict of using the HARQ buffer, because each HARQ process is associated with a HARQ buffer. If a MAC PDU is generated for this uplink scheduling, the existing MAC PDU stored in the HARQ buffer will be overwritten / damaged) is called the same HARQ process uplink scheduling / MAC PDU conflict. Different HARQ process DG / CG PUSCH conflicts include the situation where the PUSCH duration conflicts between one DG and CGs on multiple different HARQ processes. Similarly, different HARQ process CG / CG PUSCH conflicts also include the situation where the PUSCH durations conflict between multiple CGs. Unless otherwise specified, the DG / CG or CG / CG conflicts described in the embodiments of the present disclosure include the above various conflicts, and the conflicts refer to the DG and CG where the conflict occurs and the two or more CGs where the conflict occurs are all on the same serving cell. In the present disclosure, the occurrence of PUSCH overlap between different uplink schedulings means that different uplink schedulings overlap in the time domain.

[0039] When the configured scheduling timer corresponding to the HARQ process expires or a dynamic scheduling with an NDI flip is received after a MAC PDU is sent successfully, the UE or the MAC entity considers that this MAC PDU is sent successfully.

[0040] When the user equipment UE receives an uplink scheduling (DG or CG) (which can be received and executed by the uplink scheduling in the UE), and this uplink scheduling has a different HARQ process DG / CG PUSCH conflict with other uplink schedulings (CG or DG) (the base station configures CG for the UE), it judges the priorities of DG and CG and performs corresponding operations according to the judgment result (which can be received and executed by the uplink scheduling in the UE or the HARQ entity). The specific description is as follows:

[0041] In one embodiment, DG and / or CG are used for new transmissions (e.g., for DG, for new transmissions when NDI is flipped, and for CG, for new transmissions when the corresponding configuredGrantTimer is not running). When different HARQ process DG / CG PUSCH conflicts occur, if the priority of DG is higher, the UE does not generate a MAC PDU for CG and ignores CG. When the priority of DG is lower, if DG is used for new transmissions (i.e., the HARQ entity needs to obtain a MAC PDU), a MAC PDU is generated / obtained for DG (which can be executed by the HARQ entity) and stored in the buffer of the corresponding HARQ process (which can be executed by the corresponding HARQ process); if DG is used for retransmissions, the configuredGrantTimer is restarted (which can be executed by the HARQ entity).

[0042] Embodiments of the operations performed by a user equipment UE for uplink grant reception when DG / CG or CG / CG conflicts occur are described in detail below.

[0043] For the scenario where different HARQ process DG / CG PUSCH conflicts occur, the uplink scheduling received by the UE is the uplink scheduling of the C-RNTI for the MAC entity received on the PDCCH. If the first enabling priority indication flag is configured and / or the value of the flag is 1 or true or TRUE or setup or the first predefined value or the flag appears (or the value of the flag is 0 or false or False or Release or the flag does not appear), if the PUSCH duration of this uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings or only overlaps with the PUSCH durations of other uplink schedulings (such as CG) with a priority lower than or not higher than this uplink scheduling, then this uplink scheduling and / or the related HARQ information is indicated to the HARQ entity; optionally, if the previous uplink scheduling of the same HARQ process (that is, the HARQ process corresponding to the received uplink scheduling) delivered to the HARQ entity is a configured uplink scheduling or an uplink scheduling for the CS-RNTI of the MAC entity, then consider the NDI of the corresponding HARQ process to have been toggled regardless of the value of the NDI. Otherwise (that is, if the first enabling priority indication flag is not configured or the value of the flag is 0 or false or False or release or the flag does not appear (or the value of the flag is 1 or true or TRUE or setup or the flag appears)), this uplink scheduling and / or the related HARQ information is indicated to the HARQ entity; optionally, if the previous uplink scheduling of the same HARQ process (that is, the HARQ process corresponding to the received uplink scheduling) delivered to the HARQ entity is a configured uplink scheduling or an uplink scheduling for the CS-RNTI of the MAC entity, then consider the NDI of the corresponding HARQ process to have been toggled regardless of the value of the NDI. It should be noted that the judgment condition "whether the previous uplink scheduling of the same HARQ process delivered to the HARQ entity is a configured uplink scheduling or an uplink scheduling for the CS-RNTI of the MAC entity" can be independent of the judgment condition of whether the first enabling priority indication flag is configured, that is, for the received uplink scheduling, as long as the previous uplink scheduling of the same HARQ process delivered to the HARQ entity is a configured uplink scheduling or an uplink scheduling for the CS-RNTI of the MAC entity, then consider the NDI of the corresponding HARQ process to have been toggled.

[0044] In a scenario where there is a conflict between different HARQ processes DG / CG or CG / CG PUSCH, for each configured and activated scheduling configuration of each serving cell, if the first enabling priority indication identifier is not configured or the value of the identifier is 0 or false or False or Release or a second predefined value or the identifier does not appear (or the value of the identifier is 1 or true or TRUE or setup or the identifier appears) (this condition is optional), and if the PUSCH duration of this configured scheduling does not overlap with the PUSCH durations of other uplink schedulings, and if it also satisfies that the configured scheduling timer of the HARQ process corresponding to this configured scheduling is not running (this condition is optional) (in the case where all three conditions need to be executed or any two of them are required, their execution order includes but is not limited to the order listed above, and their order can be arbitrarily exchanged to form a new embodiment), then this configured scheduling and / or the related HARQ information is indicated to the HARQ entity; optionally, it is also considered that the NDI of the corresponding HARQ process is flipped. If the first enabling priority indication identifier is configured and / or the value of the identifier is 1 or true or TRUE or setup or a first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or Release or the identifier does not appear) (this condition is optional), and if the PUSCH duration of this configured scheduling only overlaps with the PUSCH durations of other uplink schedulings with a lower (or not higher) priority than this configured scheduling or the PUSCH duration of this configured scheduling does not overlap with the PUSCH durations of other uplink schedulings, and if it also satisfies that the configured scheduling timer of the corresponding HARQ process is not running (this condition is optional) (in the case where all three conditions need to be executed or any two of them are required, their execution order includes but is not limited to the order listed above, and their order can be arbitrarily exchanged to form a new embodiment), then this configured scheduling and / or the related HARQ information is indicated to the HARQ entity, optionally, it is also considered that the NDI of the corresponding HARQ process is flipped.

[0045] Optionally, if the configured scheduling timer of the corresponding HARQ process is running, it is also necessary to determine whether the priority of this configured scheduling is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the buffer of this HARQ process. If the priority of this configured scheduling is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the buffer of this HARQ process, then this configured scheduling and / or the related HARQ information is indicated to the HARQ entity, optionally, it is also considered that the NDI of the corresponding HARQ process is flipped. (Applied to the case of supporting CG / MAC PDU conflicts of the same HARQ process)

[0046] Optionally, if the configured scheduling timer of the corresponding HARQ process is running, it is also necessary to determine whether the second enable priority indication flag is configured and whether the priority of the configured scheduling is higher than the priority of the MAC PDU saved (or saved and not yet sent) in the HARQ process buffer. If the second enable priority indication flag is configured and / or the value of the flag is 1 or true or TRUE or setup or the first predefined value or the flag appears (or the value of the flag is 0 or false or False or release or the flag does not appear) and the priority of the configured scheduling is higher than the priority of the MAC PDU saved (or saved and not yet sent) in the HARQ process buffer, then the configured scheduling and / or related HARQ information is indicated to the HARQ entity. Optionally, it is also considered that the NDI of the corresponding HARQ process is flipped. (Applied to the case of supporting CG / MAC PDU conflicts of the same HARQ process)

[0047] It should be noted that the other uplink scheduling described in this disclosure includes the uplink scheduling received on the PDCCH and / or other configured scheduling and / or the uplink scheduling in the random access response. In the embodiments of this disclosure, that the PUSCH duration of a certain uplink scheduling only overlaps with the PUSCH durations of other uplink schedulings with priorities lower than or not higher than that of this uplink scheduling means that the PUSCH duration of this uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings with priorities not lower than or higher than that of this uplink scheduling.

[0048] In a scenario where there is a collision of the same HARQ process DG / MAC PDU, the uplink scheduling of the UE receives the uplink scheduling for the C-RNTI of the MAC entity received on the PDCCH. If the second enable priority indication flag is configured and the value of the flag is 1 or true or TRUE or setup or the first predefined value or the flag appears (or the value of the flag is 0 or false or False or release or the flag does not appear), if the configured scheduling timer of the HARQ process corresponding to the uplink scheduling is not running, then the uplink scheduling and / or related HARQ information is indicated to the HARQ entity; optionally, if the previous uplink scheduling of the same HARQ process (i.e., the HARQ process corresponding to the received uplink scheduling) delivered to the HARQ entity is a configured uplink scheduling or an uplink scheduling for the CS-RNTI of the MAC entity, then the NDI of the corresponding HARQ process is considered to be flipped regardless of the value of NDI. If the configured scheduling timer of the HARQ process corresponding to the uplink scheduling is running and if the previous uplink scheduling of the same HARQ process (i.e., the HARQ process corresponding to the received uplink scheduling) delivered to the HARQ entity is a configured uplink scheduling or an uplink scheduling for the CS-RNTI of the MAC entity and if the priority of the received uplink scheduling is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the buffer of the HARQ process, then the received uplink scheduling and / or related HARQ information is indicated to the HARQ entity, optionally, the NDI of the corresponding HARQ process is considered to be flipped.

[0049] It should be noted that in the present disclosure, the first enabling priority indication identifier is applied to DG / CG or CG / CG PUSCH conflicts on different HARQ processes, and the second enabling priority indication identifier is applied to DG / CG or uplink scheduling / MAC PDU conflicts on the same HARQ process. Configuring the enabling priority indication identifier (including the first enabling priority indication identifier and the second enabling priority indication identifier) and / or the value of the identifier being 1 or true or TRUE or setup or the first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or release or the second predefined value or the identifier does not appear) indicates that when there are DG / CG or CG / CG PUSCH conflicts on different HARQ processes or DG / CG or uplink scheduling / MAC PDU conflicts on the same HARQ process, the system or UE supports comparing the priorities of the conflicting uplink scheduling and / or MAC PDUs and performing the operations defined in the embodiments according to the comparison results. Not configuring the first enabling priority indication identifier or the value of the identifier being 0 or false or False or release or the second predefined value or the identifier does not appear (or the value of the identifier is 1 or true or TRUE or setup or the first predefined value or the identifier appears) means that the system or UE does not support the enabling priority indication identifier or when there is a DG / CG PUSCH conflict on different HARQ processes, it always considers the priority of DG to be higher, that is, it considers the NDI of the corresponding HARQ process to be flipped and delivers DG and its HARQ information to the HARQ entity. In addition, the value of the enabling priority indication identifier is not limited to the listed values and can also be other predefined values, such as enabling and / or disabling. If the system or UE does not support the enabling priority indication identifier, it only judges whether other conditions are met and ignores the judgment on whether the enabling priority indication identifier is configured. The first enabling priority indication identifier and the second enabling priority indication identifier can be combined into one indication identifier (denoted as the enabling priority indication identifier). Correspondingly, in the embodiments of the present disclosure, the first enabling priority indication identifier and the second enabling priority indication identifier are both replaced by the enabling priority indication identifier.

[0050] In the latest released version 15 (TS38.321-f50) of 3GPP TS38.321, when a DG / CG conflict occurs, the priority of DG is always considered higher than that of CG, DG always overrides CG, and data is transmitted using DG while ignoring CG. In other words, when a DG is received, it is always delivered to the HARQ entity, and the HARQ entity constructs a MAC PDU for the DG (for new transmission) or instructs the HARQ process to perform a retransmission; when a CG is received, the CG is delivered to the HARQ entity only if the PUSCH duration of the CG does not overlap with the PUSCH durations of other uplink schedules and the configured scheduling timer for the corresponding HARQ process is not running. In the present disclosure, by introducing an enable priority indication flag (including a first and / or second enable priority indication flag) to indicate that the UE processes different HARQ process DG / CG PUSCH duration conflicts and / or different HARQ process CG / CG PUSCH duration conflicts and / or the same HARQ process DG / CG conflict and / or the same HARQ process uplink scheduling / MAC PDU conflict (indicating that the UE performs a priority comparison when a conflict occurs), a higher-priority CG can override a lower-priority DG (or other CG) or transmit data using a higher-priority uplink schedule or deliver a higher-priority uplink schedule to the HARQ entity or generate / acquire a MAC PDU for a higher-priority uplink schedule or ignore a lower-priority DG. The enable priority indication flag (including a first and / or second enable priority indication flag) is pre-configured by the base station for the user equipment UE through RRC signaling / messages (for example, when configuring scheduling for the UE, the enable priority indication flag is configured, and the enable priority indication flag can be included in the cell BWP-UplinkDedicated of the UE-specific parameters used to configure the uplink bandwidth part BWP or included in the system information). The flag can be used to indicate whether to use a higher-priority CG and ignore a lower-priority DG when a DG / CG conflict occurs or whether to deliver a lower-priority DG to the HARQ entity or whether to generate / acquire a MAC PDU or whether to perform a retransmission or whether to process a lower-priority DG or whether to deliver a CG to the HARQ entity; or to indicate whether to use a higher-priority CG and ignore a lower-priority CG when a CG / CG conflict occurs or whether to deliver a lower-priority CG to the HARQ entity or whether to generate / acquire a MAC PDU.When the DG and CG conflicts occur in the same HARQ process, the uplink scheduling with a higher priority is delivered to the HARQ entity, and the HARQ entity generates a MAC PDU for it, which will cause the CG with a lower priority to be ignored or the MAC PDU generated for the uplink scheduling with a lower priority stored in the corresponding HARQ process (this MAC PDU may not have been sent yet, or has been sent but not yet acknowledged as correctly received (for example, the corresponding configured scheduling timer is running)) will be flushed or overwritten by the MAC PDU generated for the uplink scheduling with a higher priority. The first and / or second enabled priority indication identifier may be included in the ConfiguredGrantConfig cell, and the ConfiguredGrantConfig cell is used to configure uplink transmission without dynamic grant according to two possible schemes; the actual uplink scheduling may be configured by RRC (type 1) or provided by the PDCCH (address CS-RNTI) (type 2). When the value of the first and / or second enabled priority indication identifier is 1 or true or TRUE or setup or the identifier appears, the data is transmitted using the uplink scheduling with a higher priority or the uplink scheduling with a higher priority is delivered to the HARQ entity or a MAC PDU is constructed for the uplink scheduling with a higher priority; when the value of the enabled priority indication identifier is 0 or false or False or release or the identifier does not appear, it is always considered that the DG has the highest priority or the priority of the DG is higher than that of the CG or the priority of the uplink scheduling is higher than the priority of the MAC PDU stored in (or stored and not yet sent) the corresponding HARQ process buffer. Vice versa.

[0051] The following describes the process of handling conflicts through specific embodiments.

[0052] Embodiment 1

[0053] Figure 2 It is a flowchart showing the method executed by a user equipment according to Embodiment 1 of the present invention.

[0054] As Figure 2 shown, in Embodiment 1 of the present invention, the steps executed by the user equipment UE include: Step S201, Step S203, and Step S205.

[0055] In step S201, the uplink scheduling of the user equipment UE receives the uplink scheduling (dynamic uplink scheduling) of the C-RNTI for the MAC entity received on the PDCCH.

[0056] In step S203, for the received dynamic uplink scheduling, it is determined whether the first set condition described below is satisfied.

[0057] In step S205, when the uplink scheduling of the same HARQ process (that is, the HARQ process corresponding to the received uplink scheduling) handed to the HARQ entity in the previous one is a configured uplink scheduling or the uplink scheduling of the CS-RNTI for the MAC entity, if the first set condition is satisfied, it is considered that the NDI of the corresponding HARQ process is flipped regardless of the value of NDI. Optionally, the uplink dynamic scheduling is also handed to the HARQ entity. The first set condition may be any one of the following or any combination thereof:

[0058] 1) The user equipment is configured with a first enable priority indication identifier and / or the value of the identifier is 1 or true or TRUE or setup or a first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or release or the identifier does not appear); and if the PUSCH duration of the received uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings or does not overlap with the PUSCH durations of other uplink schedulings with higher priorities or only overlaps with the PUSCH durations of other uplink schedulings with priorities lower than or not higher than this uplink scheduling; and the priority of the received uplink scheduling is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the buffer of this HARQ process (this condition is optional); and the configured scheduling timer of this HARQ process is running (this condition is optional).

[0059] 2) The user equipment is configured with a first enable priority indication identifier and / or the value of the identifier is 1 or true or TRUE or setup or a first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or release or the identifier does not appear); and if the PUSCH duration of the received uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings or does not overlap with the PUSCH durations of other uplink schedulings with higher priorities or only overlaps with the PUSCH durations of other uplink schedulings with priorities lower than or not higher than this uplink scheduling; and the configured scheduling timer of this HARQ process is not running (this condition is optional).

[0060] 3) If the PUSCH duration of the received uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings or does not overlap with the PUSCH durations of other uplink schedulings with higher priorities or only overlaps with the PUSCH durations of other uplink schedulings with priorities lower than or not higher than that of this uplink scheduling; and the priority of the received uplink scheduling is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the HARQ process buffer (this condition is optional); and the configured scheduling timer of this HARQ process is running (this condition is optional).

[0061] 4) If the PUSCH duration of the received uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings or does not overlap with the PUSCH durations of other uplink schedulings with higher priorities or only overlaps with the PUSCH durations of other uplink schedulings with priorities lower than or not higher than that of this uplink scheduling; and the configured scheduling timer of this HARQ process is not running (this condition is optional).

[0062] 5) The user equipment is configured with a second enable priority indication identifier and / or the value of the identifier is 1 or true or TRUE or setup or a first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or release or the identifier does not appear), and the configured scheduling timer corresponding to this HARQ process is running (this condition is optional), and the priority of the received uplink scheduling is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the HARQ process buffer.

[0063] 5) The priority of the received uplink scheduling is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the buffer of the corresponding HARQ process; and the configured scheduling timer of this HARQ process is running (this condition is optional).

[0064] 6) The received uplink scheduling has a higher priority than the previous uplink scheduling (or the received uplink scheduling has a higher priority than the previous uplink scheduling that generated a MAC PDU but did not send it, or the received uplink scheduling has a higher priority than the previous uplink scheduling that generated a MAC PDU but was ignored); and the configured scheduling timer corresponding to this HARQ process is running (this condition is optional).

[0065] 7) The configured scheduling timer corresponding to the HARQ process of the received uplink scheduling is not running;

[0066] 8) If the first enabling priority indication flag is not configured or the value of the flag is 0 or false or False or release or a second predefined value or the flag does not appear (or the value of the flag is 1 or true or TRUE or setup or the flag appears), optionally, and if the PUSCH duration of the received uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings or does not overlap with the PUSCH durations of other uplink schedulings with higher priorities or only overlaps with the PUSCH durations of other uplink schedulings with priorities lower than or not higher than that of this uplink scheduling.

[0067] Among the above first set of conditions (1 - 8), all the conditions can be divided into two categories. One category is used to handle conflicts of DG / CG PUSCH durations on different HARQ processes, and this category of conditions includes any one or any combination of the following: whether the first enabling priority indication flag is configured, whether the PUSCH duration of the received uplink scheduling overlaps with the PUSCH durations of other uplink schedulings. The other category of conditions is used to handle DG / CG on the same HARQ process or uplink scheduling / MAC PDU conflicts, and this category of conditions includes any one or any combination of the following: whether the second enabling priority indication flag is configured, whether the corresponding configured scheduling timer is running, whether the priority of the received uplink scheduling is higher than the priority of the MAC PDU saved (or saved and not yet sent) in the buffer of this HARQ process, whether the received uplink scheduling has a higher priority than the previous uplink scheduling. These two categories of conditions are only required when the system or UE supports handling the corresponding types of conflicts. For example, if the system or UE does not support handling DG / CG on the same HARQ process or uplink scheduling / MAC PDU conflicts (in other words, it is always considered that the received uplink scheduling always has a higher priority, and the MAC PDU generated for this uplink scheduling will overwrite the MAC PDU saved in the current HARQ buffer), then the first set of conditions does not include the conditions for handling DG / CG on the same HARQ process or uplink scheduling / MAC PDU conflicts. In addition, the statement that the priority of the received uplink scheduling is higher than the priority of the MAC PDU saved (or saved and not yet sent) in the buffer of this HARQ process in the present disclosure can be replaced with the statement that the priority of the received uplink scheduling is not lower than the priority of the MAC PDU saved (or saved and not yet sent) in the buffer of this HARQ process. In addition, each of the above conditions (1 - 8) contains multiple judgment conditions (except for condition (7)), and in each item, the execution order of these judgment conditions includes but is not limited to the order listed above, and the order of these judgment conditions can also be exchanged to form a new embodiment.

[0068] Furthermore, if the uplink scheduling received by the user equipment UE is the uplink scheduling for the C-RNTI of the MAC entity received on the PDCCH and meets the first set condition, at least one of the following operations may also be performed:

[0069] 1) Deliver the received uplink grant and the associated HARQ information to the HARQ entity.

[0070] 2) Start or restart the configured GrantTimer for the correponding HARQ process, if configured.

[0071] Optionally, if the uplink scheduling received by the user equipment UE is the uplink scheduling for the C-RNTI of the MAC entity received on the PDCCH and does not meet the first set condition, at least one of the following operations is performed:

[0072] 1) If the previous uplink grant for the same HARQ process delivered to the HARQ entity is the uplink scheduling for the C-RNTI of the MAC entity, deliver the received uplink grant and the associated HARQ information to the HARQ entity;

[0073] 2) If the corresponding HARQ process is the HARQ process configured for configured scheduling and the configured GrantTimer is configured, start or restart the configured GrantTimer for the corresponding HARQ process;

[0074] 3) Ignore the received uplink grant.

[0075] In another embodiment, the uplink scheduling received by the user equipment UE on the PDCCH is the uplink scheduling for the C-RNTI of the MAC entity. If the previous uplink scheduling for the same HARQ process (i.e., the HARQ process corresponding to the received uplink scheduling) delivered to the HARQ entity is a configured uplink scheduling or an uplink scheduling for the CS-RNTI of the MAC entity, then consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI. If the foregoing first set condition is satisfied, then other operations that can be performed when the foregoing first set condition is satisfied may be executed.

[0076] In an embodiment of the present disclosure, the MAC PDU that is stored in the buffer of the HARQ process and has not been transmitted refers to that the buffer of the HARQ process is not empty and the stored MAC PDU has not been transmitted, or the buffer of the HARQ process contains a MAC PDU that has not been transmitted. When a conflict occurs between DGs corresponding to different HARQ processes or between CGs, the HARQ entity generates a MAC PDU for the uplink scheduling with a lower priority and stores it in the buffer. However, since the corresponding uplink scheduling has a lower priority and is ignored, the MAC PDU is not transmitted using the uplink scheduling. The MAC PDU refers to the MAC PDU that has not been transmitted and may also be referred to as the MAC PDU waiting for initial transmission.

[0077] Embodiment 2

[0078] Figure 3 is a flowchart showing a method performed by a user equipment according to Embodiment 2 of the present invention.

[0079] As Figure 3 shown, in Embodiment 2 of the present invention, the steps performed by the user equipment UE include: Step S301, Step S303, and Step S305.

[0080] In Embodiment 2, in Step S301, for each serving cell, receive the configured uplink scheduling for the MAC entity (the MAC entity may perform the following operations).

[0081] In Step S303, for the received configured uplink scheduling, determine whether the second set condition is satisfied.

[0082] In Step S305, if the second set condition is satisfied, then perform one or more of the following operations (for example, deliver the configured uplink scheduling to the HARQ entity):

[0083] 1) Set the HARQ process ID to the HARQ process ID corresponding to the configured uplink scheduling PUSCH duration;

[0084] 2) If the configured scheduling timer for the corresponding HARQ process is not running; or, the buffer for the corresponding HARQ process is empty or the configured scheduling timer for the corresponding HARQ process is running but the buffer for the HARQ process is empty (this condition is optional), then it is considered that the NDI of the corresponding HARQ process is flipped, and / or the configured uplink scheduling and its related HARQ information are delivered to the HARQ entity (optional). Optionally, if the configured scheduling timer for the corresponding HARQ process is running and there is an unsent MAC PDU in the HARQ buffer (for example, the MAC PDU is generated for a previous configured uplink scheduling with a lower priority), then it is considered that the NDI of the corresponding HARQ process is not flipped.

[0085] 3) Deliver the configured uplink scheduling and its related HARQ information to the HARQ entity (if this operation is performed in 2), it is not performed here again).

[0086] 4) Start the configured scheduling timer for the corresponding HARQ process (this operation is only performed if a configured scheduling timer is configured).

[0087] Optionally, if the second set condition is not met, ignore the configured uplink scheduling or do not deliver the configured uplink scheduling to the HARQ entity.

[0088] Specifically, the second set condition may be any one or any combination of the following:

[0089] 1) The UE is configured with a first enable priority indication flag and the value of the flag is 1 or true or TRUE or setup or a first predefined value or the flag appears (or the value of the flag is 0 or false or False or release or the flag does not appear); and the configured scheduling timer for the corresponding HARQ process is not running (optional).

[0090] 2) The UE is configured with a first enabled priority indication identifier, and the value of the identifier is 1 or true or TRUE or setup or a first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or release or the identifier does not appear); and (or) the configured PUSCH duration of the uplink scheduling overlaps with the PUSCH durations of other uplink schedulings in the same serving cell, but the configured uplink scheduling has a higher priority, or the configured uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings in the same serving cell, or the configured PUSCH duration of the uplink scheduling only overlaps with the PUSCH durations of other uplink schedulings with a priority lower than (or not higher than) the configured uplink scheduling; and the configured scheduling timing of the corresponding HARQ process is running, but the configured scheduling has a higher priority (compared with the priority of the MAC PDU in the buffer) (optional), or the configured scheduling timer of the HARQ process corresponding to the configured uplink scheduling is not running.

[0091] 3) The UE is not configured with a first enabled priority indication identifier, or the value of the identifier is 0 or false or False or release or a second predefined value or the identifier does not appear (or the value of the identifier is 1 or true or TRUE or setup or the identifier appears), and / or the configured PUSCH duration of the uplink scheduling does not overlap with the PUSCH duration of the uplink scheduling received on the PDCCH in the same serving cell or the PUSCH durations of other configured uplink schedulings in the same serving cell or the PUSCH duration of the uplink scheduling in the random access response; and the configured scheduling timer of the corresponding HARQ process is not running. Optionally, the configured scheduling timer of the corresponding HARQ process is running if it is configured with a second enabled priority indication identifier, or the value of the identifier is 0 or false or False or release or a second predefined value or the identifier does not appear (or the value of the identifier is 1 or true or TRUE or setup or the identifier appears) and the configured scheduling has a higher priority (compared with the priority of the MAC PDU in the buffer).

[0092] 4) The configured PUSCH duration of the uplink scheduling overlaps with the PUSCH duration of the uplink scheduling received on the PDCCH in the same serving cell or overlaps with the PUSCH durations of other configured uplink schedulings in the same serving cell, but the configured uplink scheduling has a higher priority; or the configured PUSCH duration of the uplink scheduling does not overlap with the PUSCH duration of the uplink scheduling in the random access response but overlaps with the PUSCH duration of the uplink scheduling received on the PDCCH in the same serving cell or the PUSCH durations of other configured uplink schedulings in the same serving cell, and the configured uplink scheduling has a higher priority.

[0093] 5) The UE is configured with a second enabling priority indication identifier, and the value of the identifier is 1 or true or TRUE or setup or a first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or release or the identifier does not appear); and the configured scheduling timing of the corresponding HARQ process is running (optional) but the configured scheduling priority is higher (compared with the priority of the MAC PDU in the buffer) or the configured scheduling timer for the configured uplink scheduling corresponding to the HARQ process is not running.

[0094] Optionally, in the above second setting condition (1 - 5), if the received or available PUSCH duration of the configured uplink scheduling overlaps with the PUSCH duration of the uplink scheduling in the random access response, then ignore the configured uplink scheduling or do not deliver the configured uplink scheduling to the HARQ entity (that is, always consider the uplink scheduling in the random access response to have the highest priority, which can also be applied to other embodiments of the present disclosure).

[0095] In the above second setting condition (1 - 5), all the conditions can be divided into two categories. One category is used to handle DG / CG or CG / CG PUSCH duration conflicts on different HARQ processes, and such conditions include any one or any combination of the following: whether the first enabling priority indication identifier is configured, whether the received PUSCH duration of the configured uplink scheduling overlaps with the PUSCH duration of other uplink schedulings (such as another configured uplink scheduling or DG or the uplink scheduling in the random access response). The other category of conditions is used to handle configured uplink scheduling / MAC PDU conflicts on the same HARQ process, and such conditions include any one or any combination of the following: whether the second enabling priority indication identifier is configured, whether the corresponding configured scheduling timer is running but the configured scheduling priority is higher (compared with the priority of the MAC PDU in the buffer). These two categories of conditions are only required when the system or the UE supports handling the corresponding type of conflicts. For example, if the system or the UE does not support handling configured uplink scheduling / MAC PDU conflicts on the same HARQ process (in other words, if the corresponding configured scheduling timer is running, then do not deliver the configured uplink scheduling to the HARQ entity), then the first setting condition does not include the conditions for handling configured uplink scheduling / MAC PDU conflicts on the same HARQ process. In addition, if the system or the UE does not support the enabling priority indication identifier (including the first enabling priority indication identifier and the second enabling priority indication identifier), then the judgment on whether the enabling priority indication identifier is configured in the above second setting condition (1 - 5) can be deleted. In addition, for the items in the above conditions (1 - 5) that contain multiple judgment conditions, the execution order of these judgment conditions includes but is not limited to the order listed above, and the order of these judgment conditions can be exchanged to form a new embodiment.

[0096] In the embodiments of the present disclosure, the uplink scheduling for the C-RNTI or CS-RNTI or TC-RNTI of the MAC entity, or the uplink scheduling received on the PDCCH for the C-RNTI or CS-RNTI or TC-RNTI of the MAC entity, refers to the uplink scheduling indicated by the PDCCH scrambled by the C-RNTI or CS-RNTI or TC-RNTI.

[0097] In the embodiments of the present disclosure, the priority of dynamic scheduling may be indicated in the corresponding downlink control information DCI. The priority of configured scheduling may be configured by the base station through RRC signaling / message or indicated in the downlink control information DCI used to activate the configured scheduling. It may also be the highest priority of the logical channel corresponding to the data that this uplink scheduling can send or can be multiplexed or will be multiplexed or has been multiplexed (executed by the multiplexing and assembly process according to the logical channel priority LCP process), or the priority of the logical channel corresponding to the data included in the MAC PDU to be generated for this uplink scheduling. The priority of the MAC PDU refers to the priority of the logical channel corresponding to the data with the highest priority included in the MAC PDU or the priority of the uplink scheduling corresponding to the MAC PDU (the MAC PDU is the MAC PDU generated for the uplink scheduling). Comparing the priorities of an uplink scheduling and a MAC PDU means comparing the priority of the uplink scheduling with the priority of the uplink scheduling corresponding to the MAC PDU, or comparing the priority of the MAC PDU generated for the uplink scheduling with the priority of the MAC PDU. If the priority of the uplink scheduling is determined by its corresponding MAC PDU or by the priority of the logical channel with the highest corresponding priority, then the comparison of priorities between uplink schedulings is the comparison of the priorities of their corresponding MAC PDUs or the priorities of the logical channels with the highest corresponding priorities. Correspondingly, when the uplink scheduling receiver or HARQ entity processes the corresponding uplink scheduling, it first obtains the priority of the uplink scheduling from the "process for determining the priority of uplink scheduling" before comparing the priority with other uplink schedulings. For example, it obtains the priority from the multiplexing and assembly process, and then compares the obtained priority with the priorities of other uplink schedulings. When the "process for determining the priority of uplink scheduling" (such as the multiplexing and assembly process) receives an indication to obtain the priority of the uplink scheduling, it determines the priority of the logical channel with the highest priority corresponding to the data that this uplink scheduling can send or can be multiplexed or will be multiplexed according to the limiting conditions of the logical channel priority LCP (or the mapping restrictions configured by RRC for each logical channel), or uses the priority of the logical channel with the highest priority among the logical channels selected or preselected for this uplink scheduling as the priority of this uplink scheduling (if there is data that can be sent in the logical channels selected by the "process for determining the priority of uplink scheduling", and if there is no data that can be sent in all logical channels according to the LCP rules, the priority for the corresponding uplink scheduling may be a predefined value, such as 0. Different predefined values may also be set for the cases where only MAC CE can be sent and where there is no data and MAC CE can be sent), and indicates it to the uplink scheduling receiver or HARQ entity.In addition, if the uplink scheduling reception obtains / receives the priority of a certain uplink scheduling, when the uplink scheduling reception delivers the uplink scheduling to the HARQ entity, the priority of the uplink scheduling can also be delivered to the HARQ entity. For the HARQ entity, if it receives the priority of a certain uplink scheduling from the uplink scheduling reception, then it does not need to obtain the priority of the uplink scheduling from the "process of determining the uplink scheduling priority", but if it does not receive the priority of a certain uplink scheduling, then it can obtain the priority of the uplink scheduling from the "process of determining the uplink scheduling priority". Optionally, when the HARQ entity delivers the uplink scheduling to the HARQ process, it also indicates the priority of the uplink scheduling to the HARQ process.

[0098] The following specifically describes an operation embodiment executed by the HARQ entity of the user equipment UE when a DG / CG or CG / CG conflict occurs.

[0099] The following describes a processing method of the HARQ entity for the received uplink scheduling.

[0100] For an uplink scheduling whose PUSCH duration does not overlap with the PUSCH durations of other uplink schedulings, or for an uplink scheduling whose PUSCH duration only overlaps with the PUSCH durations of other uplink schedulings with lower priorities, or the PUSCH duration of this uplink scheduling overlaps with the PUSCH durations of other uplink schedulings with lower priorities, or for a dynamic scheduling whose PUSCH duration does not overlap with the PUSCH durations of other configured uplink schedulings with higher priorities, identify the HARQ process of this uplink scheduling, and for the identified HARQ process, perform the following operations:

[0101] If this uplink scheduling is for new transmission (i.e., meets the new transmission conditions, such as the conditions for obtaining the MAC PDU given in steps 002 / 003 of the following embodiments), then obtain the MAC PDU.

[0102] If the MAC PDU is obtained, then deliver the MAC PDU, this uplink scheduling, and the HARQ information of the transport block of the identified HARQ process to the identified HARQ process, indicate the identified HARQ process to trigger new transmission, and if the condition for starting the configured scheduling timer of the identified HARQ process is met, then start or restart the configured scheduling timer of the identified HARQ process.

[0103] If the MAC PDU is not obtained, then clear the HARQ buffer of the identified HARQ process, and optionally, stop the configured scheduling timer of the identified HARQ process (if it is running).

[0104] Optionally, for an uplink scheduling whose PUSCH duration overlaps with the PUSCH durations of other higher-priority uplink schedulings, if this uplink scheduling is for new transmission (i.e., meets the new transmission conditions, such as the conditions for obtaining the MAC PDU given in the following embodiments), then obtain the MAC PDU. If the MAC PDU is obtained, then deliver the MAC PDU to the identified HARQ process, deliver the HARQ information of the transmission block of this uplink scheduling and / or the identified HARQ process to the identified HARQ process (this operation is optional), indicate that the identified HARQ process does not trigger new transmission (or do not indicate that the identified HARQ process triggers new transmission or indicate that the identified HARQ process stores the MAC PDU) (this operation is also optional), and if the conditions for starting the configured scheduling timer of the identified HARQ process are met, then start or restart the configured scheduling timer of the identified HARQ process. If the MAC PDU is not obtained, then clear the HARQ buffer of the identified HARQ process, and optionally, stop the configured scheduling timer of the identified HARQ process (if it is running).

[0105] Optionally, for an uplink scheduling whose PUSCH duration overlaps with the PUSCH durations of other higher-priority uplink schedulings, if this uplink scheduling is for new transmission (i.e., meets the new transmission conditions, such as the conditions for obtaining the MAC PDU given in the following embodiments), then clear the HARQ buffer of the identified HARQ process, and optionally, stop the configured scheduling timer of the identified HARQ process (if it is running).

[0106] Optionally, for an uplink scheduling for retransmission (i.e., does not meet the new transmission conditions), if the PUSCH duration of this uplink scheduling overlaps with the PUSCH durations of other higher-priority uplink schedulings, then ignore this uplink scheduling, and optionally, indicate that the identified HARQ process does not trigger retransmission (or do not indicate that the identified HARQ process triggers retransmission), and optionally, if the conditions for starting the configured scheduling timer of the identified HARQ process are met, then start or restart the configured scheduling timer of the identified HARQ process.

[0107] The following is another processing method for the uplink scheduling received by the HARQ entity.

[0108] For each uplink scheduling, identify the HARQ process of this uplink scheduling. For the identified HARQ process, if this uplink scheduling is for new transmission (i.e., meets the new transmission conditions, such as the conditions for obtaining the MAC PDU given in steps 002 / 003 of the following embodiments), then obtain the MAC PDU. If the MAC PDU is obtained, then deliver the MAC PDU to the identified HARQ process. Optionally, also deliver the HARQ information of the transmission block of this uplink scheduling and / or the identified HARQ process to the identified HARQ process. Optionally, if the PUSCH duration of this uplink scheduling overlaps with the PUSCH durations of other uplink schedulings with higher priorities, then indicate that the identified HARQ process does not trigger new transmission or do not indicate that the identified HARQ process triggers new transmission or indicate that the identified HARQ process stores the MAC PDU. If the condition for starting the configured scheduling timer of the identified HARQ process is met, then start or restart the configured scheduling timer of the identified HARQ process; if the PUSCH duration of this uplink scheduling only overlaps with the PUSCH durations of other uplink schedulings with priorities lower than (or not higher than) this uplink scheduling, then indicate that the identified HARQ process triggers new transmission. Optionally, also deliver the HARQ information of the transmission block of this uplink scheduling and / or the identified HARQ process to the identified HARQ process (if this operation has been performed before judging the priority of this uplink scheduling and other uplink schedulings, then this operation is not performed here). If the MAC PDU is not obtained, then clear the HARQ buffer of the identified HARQ process. Optionally, stop the configured scheduling timer of the identified HARQ process (if it is running). If this uplink scheduling is for retransmission and meets one of the following conditions, then ignore this uplink scheduling and stop the configured scheduling timer of the identified HARQ process (if it is running): (1) if this uplink scheduling is indicated by a PDCCH scrambled with a CS-RNTI and the HARQ buffer of the identified HARQ process is empty; (2) if this uplink scheduling is part of a group of uplink schedulings and no MAC PDU has been obtained for this group of uplink schedulings; (3) if this uplink scheduling is part of a group of uplink schedulings and the PUSCH duration of this uplink scheduling overlaps with the PUSCH duration of another uplink scheduling indicated by a PDCCH duration or a random access response on this serving cell; (4) if the PUSCH duration of this uplink scheduling overlaps with the PUSCH durations of other uplink schedulings with priorities not lower than (or higher than) this uplink scheduling.

[0109] The conditions for configuring and scheduling the timer for the HARQ process that initiates recognition are as follows: If the uplink scheduling corresponds to a CS-RNTI, or the uplink scheduling is configured uplink scheduling, or the uplink scheduling corresponds to a C-RNTI and the recognized HARQ process is configured with configured uplink scheduling, then if the configured scheduling timer is configured, the configured scheduling timer is started or restarted when transmission is performed.

[0110] It should be noted that the enable priority indication identifier (including the first or second enable priority indication identifier) defined in the operation embodiment of the uplink scheduling reception execution can also be applied to the operation embodiment executed by the HARQ entity. At this time, in the operation embodiment executed by the HARQ entity, only when the enable priority indication identifier is configured and / or the value of the identifier is 1 or true or TRUE or setup or the first predefined value or the identifier appears (or the value of the identifier is 0 or false or False or release or the identifier does not appear), it is determined whether the PUSCH duration of the received uplink scheduling overlaps with the PUSCH duration of other uplink schedulings, and the operations defined in the embodiment are executed according to the judgment result. If the enable priority indication identifier is not configured or the value of the identifier is 0 or false or False or the second predefined value or the identifier does not appear (or the value of the identifier is 1 or true or TRUE or the identifier appears), it is executed in the manner of not performing the operation of determining whether the PUSCH duration of the received uplink scheduling overlaps with the PUSCH duration of another uplink scheduling in the embodiment (that is, the default condition is satisfied). In the operation embodiment executed by the HARQ entity, the judgment of the enable priority indication identifier and the priority comparison between uplink schedulings is the same as the first set of conditions (1-8) and the second set of conditions (1-5) defined in the operation embodiment of the uplink scheduling reception execution.

[0111] The above two processing methods are described in more detail below through specific embodiments.

[0112] Embodiment III

[0113] Figure 4 It is a flowchart showing a method executed by a user equipment according to Embodiment III of the present invention.

[0114] As Figure 4 shown, in Embodiment III of the present invention, the steps executed by the user equipment UE include: steps 001 to 009.

[0115] In this embodiment, for each uplink grant (or for an uplink grant whose PUSCH duration does not overlap with the PUSCH durations of other uplink grants, or for an uplink grant whose PUSCH duration only overlaps with the PUSCH durations of other uplink grants with lower priorities, or for a dynamic grant whose PUSCH duration does not overlap with the PUSCH durations of other uplink grants with higher priorities), the HARQ entity performs the following operations:

[0116] In step 001, identify the HARQ process associated with this uplink grant, and for each identified HARQ process, perform step 002.

[0117] In step 002, if the received uplink grant is not indicated by a PDCCH addressed to the corresponding TC-RNTI, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or if the received uplink grant is indicated by a PDCCH scrambled with the C-RNTI and the HARQ buffer of the identified HARQ process is empty; or if the uplink grant is received in a Random Access Response; or if the uplink grant received within the ra-ResponseWindow is indicated by a PDCCH scrambled with the C-RNTI and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery;Or if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission, and if no MAC PDU has been obtained for this bundle, then step 003 is executed (meeting at least one of the conditions), otherwise (none of the conditions are met), step 008 is executed (the uplink grant is for retransmission).;

[0118] In step 003, if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response, or if there is a MAC PDU in the Msg3 buffer and the uplink grant received in ra-ResponseWindow was indicated by a PDCCH scrambled with a C-RNTI and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery, then step 004 is executed (meeting at least one of the conditions), otherwise (none of the conditions are met), step 005 is executed.

[0119] In step 004, obtain the MAC PDU from the Msg3 buffer. If the size of the uplink grant does not match with the size of the obtained MAC PDU, and if the Random Access procedure was successfully completed upon receiving the uplink grant, indicate to the Multiplexing and assembly entity to include MAC subPDU(s) carrying MAC SDU from the obtained MAC PDU in the subsequent uplink transmission, and obtain the MAC PDU from the Multiplexing and assembly entity for transmission. Execute step 006.

[0120] In step 005, obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any. Execute step 006.

[0121] In step 006, if a MAC PDU to transmit has been obtained, then perform the following operations (and end after performing the following operations):

[0122] (1) Deliver the MAC PDU and / or the uplink grant and / or the HARQ information of the TB to the identified HARQ process.

[0123] (2) Preferably, the identified HARQ process is instructed to trigger a new transmission. Alternatively, if the PUSCH duration of the uplink grant does not overlap with the PUSCH durations of other uplink grants or if the PUSCH duration of the uplink grant only overlaps with the PUSCH durations of other uplink grants with lower priority (If the uplink grant does not overlapwith other uplink grant or if the uplink grant overlaps with other uplinkgrant with lower priority) or if the uplink grant is indicated by a PDCCH scrambled with a C-RNTI and the priority of the configured uplink grant that overlaps with its PUSCH duration is not higher than that of this uplink grant (these judgment conditions in this operation are optional. For example, when the HARQ entity executes step 001 and subsequent steps for each uplink grant, it judges whether these conditions are met and performs subsequent operations when any of the conditions is met), then the identified HARQ process is instructed to trigger a new transmission (instruct the identified HARQ process to trigger a new transmission) and / or the uplink grant and / or the HARQ information of this transport block is delivered to the identified HARQ process (deliver the uplinkgrant and / or the HARQ information of the TB to the identified HARQ process); otherwise (optional), the uplink grant and / or the HARQ information of this transport block is delivered to the identified HARQ process and / or the identified HARQ process is instructed not to trigger a new transmission (or not to instruct the identified HARQ to trigger a new transmission or to instruct the identified HARQ process to store the MAC PDU) and / or the uplink grant is ignored; optionally, if the uplink grant is indicated by a PDCCH scrambled with a C-RNTI and the PUSCH duration of the uplink grant overlaps with the PUSCH durations of other uplink grants with higher priority (this judgment condition is optional. For example, when the HARQ entity executes step 001 and subsequent steps for each uplink grant, it judges whether this condition is met and performs subsequent operations when the condition is met), then the uplink grant and / or the HARQ information of this transport block is delivered to the identified HARQ process and / or the identified HARQ process is instructed not to trigger a new transmission (or not to instruct the identified HARQ to trigger a new transmission or to instruct the identified HARQ process to store the MAC PDU) and / or the uplink grant is ignored.

[0124] (3) If the received uplink grant is addressed to CS-RNTI, or the received uplink grant is a configured uplink grant, or the received uplink grant is addressed to C-RNTI and the identified HARQ process is configured for a configured uplink grant, then if the configured grant timer is configured, start or restart the configuredGrantTimer for the corresponding HARQ process when the transmission is performed;

[0125] Otherwise (no MAC PDU for transmission is obtained), step 007 is performed.

[0126] In step 007, clear the HARQ buffer of the identified HARQ process. Optionally, if the configured grant timer is running, stop the configured grant timer. End.

[0127] In step 008, if the third set condition is met, ignore the uplink grant; if the third set condition is not met, step 009 is performed. The third set condition may be at least one of the following:

[0128] (1) If the uplink grant received on PDCCH was addressed to CS-RNTI and the HARQ buffer of the identified HARQ process is empty;

[0129] (2) If the uplink grant is part of a bundle and if no MAC PDU has been obtained for this bundle

[0130] (3) If the uplink grant is part of a bundle of the configured uplink grant, and the PUSCH of the uplink grant overlaps with a PUSCH of another uplink grant received on the PDCCH or in a Random Access Response for this Serving Cell

[0131] (4) The uplink grant is indicated by a PDCCH and / or the PUSCH duration of the uplink grant overlaps with the PUSCH duration of another uplink grant with a higher priority.

[0132] Optionally, step 008 further includes: if the uplink grant is ignored, if the uplink grant is indicated by a PDCCH scrambled with a CS-RNTI and / or if the configured scheduling timer corresponding to the identified HARQ process is running, then stop the configured scheduling timer.

[0133] Optionally, in step 008, after ignoring the uplink grant, if the configured scheduling timer corresponding to the identified HARQ process is running (only executed when a configured uplink grant and / or a configured scheduling timer is configured for the HARQ process), then stop the configured scheduling timer.

[0134] Optionally, step 008 further includes: if the uplink grant is indicated by a PDCCH scrambled with a CS-RNTI (the uplink grant received on PDCCH was addressed to CS-RNTI) and the HARQ buffer of the identified HARQ process is empty, if the configured scheduling timer corresponding to the identified HARQ process is running (only executed when a configured uplink grant and / or a configured scheduling timer is configured for the HARQ process), then stop the configured scheduling timer.

[0135] Optionally, step 008 further includes: if the uplink scheduling is indicated by PDCCH and / or the PUSCH duration of the uplink scheduling overlaps with the PUSCH duration of another uplink scheduling with a higher priority, if the configured scheduling timer corresponding to the identified HARQ process is running (only executed when the configured uplink scheduling and / or the configured scheduling timer are configured for the HARQ process), then stop the configured scheduling timer.

[0136] In step 009, submit the HARQ information (redundancy version) corresponding to the uplink scheduling and the transport block to the identified HARQ process; indicate the identified process to trigger a retransmission; if the received uplink scheduling corresponds to CS-RNTI or the received uplink scheduling is a configured uplink scheduling or the received uplink scheduling corresponds to C-RNTI and the identified HARQ process is configured with a configured uplink scheduling, then if the configured scheduling timer is configured, start or restart the configuredGrantTimer when performing the transmission.

[0137] Embodiment 4

[0138] Figure 5 is a flowchart showing a method executed by a user equipment according to Embodiment 4 of the present invention.

[0139] As Figure 5 shown, in Embodiment 4 of the present invention, the steps executed by the user equipment UE include: steps 101 to 113.

[0140] In this embodiment, for each uplink scheduling (or for an uplink scheduling whose PUSCH duration does not overlap with the PUSCH duration of other uplink schedulings, or for an uplink scheduling whose PUSCH duration only overlaps with the PUSCH duration of other uplink schedulings with a lower priority, or for a dynamic scheduling whose PUSCH duration does not overlap with the PUSCH duration of other uplink schedulings with a higher priority), the HARQ entity performs the following operations:

[0141] In step 101, identify the HARQ process corresponding to the uplink scheduling, and perform step 102 for each identified HARQ process.

[0142] In step 102, if the received uplink scheduling is not indicated by the PDCCH corresponding to the TC-RNTI, and the NDI provided in the corresponding HARQ information is flipped compared to the NDI value of the previous transmission of the transport block of this HARQ process; or if the received uplink scheduling is indicated by the PDCCH scrambled by the C-RNTI and the HARQ buffer of the identified HARQ process is empty; or if the uplink scheduling is received from the random access response; or if the uplink scheduling received within the ra-ResponseWindow is indicated by the PDCCH scrambled by the C-RNTI and this PDCCH has successfully completed the random access process caused by beam error recovery; or if the uplink scheduling is part of a set of configured uplink schedulings and may be used for the initial transmission and no MAC PDU has been obtained for this set of configured uplink schedulings, then step 103 is executed (if at least one of the conditions is met), otherwise (none of the conditions are met), step 108 is executed.

[0143] In step 103, if there is a MAC PDU in the Msg3 buffer and the uplink scheduling is received from the random access response, or if there is a MAC PDU in the Msg3 buffer and the uplink scheduling received within the ra-ResponseWindow is indicated by the PDCCH scrambled by the C-RNTI and this PDCCH has successfully completed the random access process caused by beam error recovery, then step 104 is executed (if at least one of the conditions is met), otherwise (none of the conditions are met), step 105 is executed.

[0144] In step 104, obtain the MAC PDU from the Msg3 buffer. If the size of the uplink scheduling does not match the size of the obtained MAC PDU and the random access process is successfully completed when this uplink scheduling is received, instruct the multiplexing and assembly entity to include, in the subsequent uplink transmission, the MAC subPDUs carrying the MAC SDUs from the obtained MAC PDU, and obtain the MAC PDU from the multiplexing and assembly entity for transmission. Step 106 is executed.

[0145] In step 105, obtain the MAC PDU from the multiplexing and assembly entity for transmission (if available). Step 106 is executed.

[0146] In step 106, if a MAC PDU to transmit has been obtained, then perform the following operations (and end after performing the following operations):

[0147] (1) Deliver the MAC PDU and / or the uplink scheduling and / or the HARQ information of this transport block to the identified HARQ process.

[0148] (2) Preferably, the indicated identified HARQ process triggers a new transmission. Alternatively, if the PUSCH duration of this uplink scheduling does not overlap with the PUSCH durations of other uplink schedulings, or the PUSCH duration of this uplink scheduling only overlaps with the PUSCH durations of other uplink schedulings with lower priorities, or this uplink scheduling is indicated by a PDCCH scrambled with a C-RNTI and the priority of the configured uplink scheduling that overlaps with its PUSCH duration is not higher than this uplink scheduling (the above judgment conditions in this operation are optional. For example, when the HARQ entity executes step 101 and its subsequent steps for each uplink scheduling, it judges whether these conditions are met and executes subsequent operations when any of these conditions is met), then the indicated identified HARQ process triggers a new transmission and / or delivers the HARQ information of this uplink scheduling and / or this transport block to the identified HARQ process; otherwise (optional), delivers the HARQ information of this uplink scheduling and / or this transport block to the identified HARQ process and / or indicates that the identified HARQ process does not trigger a new transmission (or does not indicate that the identified HARQ triggers a new transmission or indicates that the identified HARQ process stores the MAC PDU) and / or ignores this uplink scheduling; optionally, if this uplink scheduling is indicated by a PDCCH scrambled with a C-RNTI and the PUSCH duration of this uplink scheduling overlaps with the PUSCH durations of other uplink schedulings with higher priorities (this judgment condition is optional. For example, when the HARQ entity executes step 101 and its subsequent steps for each uplink scheduling, it judges whether this condition is met and executes subsequent operations when the condition is met), then delivers the HARQ information of this uplink scheduling and / or this transport block to the identified HARQ process and / or indicates that the identified HARQ process does not trigger a new transmission (or does not indicate that the identified HARQ triggers a new transmission or indicates that the identified HARQ process stores the MAC PDU) and / or ignores this uplink scheduling.

[0149] (3) If the received uplink scheduling corresponds to a CS-RNTI, or the received uplink scheduling is a configured uplink scheduling, or the received uplink scheduling corresponds to a C-RNTI and the identified HARQ process is configured with a configured uplink scheduling, then if a configured scheduling timer is configured, start or restart the configured scheduling timer configuredGrantTimer when performing the transmission;

[0150] Otherwise (no MAC PDU for transmission is obtained), then execute step 107.

[0151] In step 107, clear the HARQ buffer of the identified HARQ process. Optionally, if the configured scheduling timer is running, stop the configured scheduling timer. End.

[0152] In step 108, if the received uplink scheduling is indicated by a PDCCH scrambled with a C-RNTI and another uplink scheduling for the same HARQ process (the HARQ process identified for the received uplink scheduling) delivered to this HARQ entity is indicated by a PDCCH scrambled with a CS-RNTI or is configured uplink scheduling, or if the received uplink scheduling is configured uplink scheduling and another uplink scheduling for the same HARQ process delivered to this HARQ entity is indicated by a PDCCH scrambled with a CS-RNTI or a C-RNTI, or there is a MAC PDU in the HARQ buffer of the identified HARQ process that has not been sent or is waiting for initial transmission, then step 109 is executed; otherwise, step 112 is executed.

[0153] In step 109, if the priority of this received configured scheduling is higher (higher than the priority of the CG or the MAC PDU that has not been sent or is waiting for initial transmission on the same HARQ process, or not lower than the priority of the CG or the MAC PDU that has not been sent or is waiting for initial transmission on the same HARQ process), then step 110 is executed; otherwise, step 111 is executed.

[0154] In step 110, obtain the MAC PDU for transmission from the multiplexing and assembly entity; deliver the MAC PDU, the uplink scheduling, and the HARQ information of this transport block to the identified HARQ process; instruct the identified HARQ process to trigger a new transmission; start or restart the configured scheduling timer corresponding to the identified HARQ process when transmission is performed (only executed if a configured scheduling timer is configured for this configured uplink scheduling). End.

[0155] In step 111, if the received uplink scheduling is indicated by a PDCCH scrambled with a C-RNTI, then ignore this uplink scheduling. If the received uplink scheduling is configured uplink scheduling and the previous uplink scheduling for the same HARQ process (the HARQ process identified for the received uplink scheduling) delivered to this HARQ entity is indicated by a PDCCH scrambled with a CS-RNTI or is configured uplink scheduling, then deliver the uplink scheduling to be performed and the HARQ information (redundancy version) of this TB to the identified HARQ process; instruct the identified HARQ process to trigger a retransmission and start the configured scheduling timer of this HARQ process (if configured). If none of the above conditions are met, then ignore this uplink scheduling. End.

[0156] In step 112 (the same as step 008 in the previous Embodiment 3), if the fourth set condition is satisfied, then ignore this uplink scheduling; if the third set condition is not satisfied, then step 113 is executed. The fourth set condition may be at least one of the following:

[0157] (1) If the uplink grant received on PDCCH was addressed to CS-RNTI and the HARQ buffer of the identified HARQ process is empty;

[0158] (2) If the uplink grant is part of a bundle and if no MAC PDU has been obtained for this bundle

[0159] (3) If the uplink grant is part of a bundle of the configured uplink grant, and the PUSCH of the uplink grant overlaps with a PUSCH of another uplink grant received on the PDCCH or in a Random Access Response for this Serving Cell

[0160] (4) The uplink grant is indicated by a PDCCH and / or the PUSCH duration of the uplink grant overlaps with the PUSCH duration of another uplink grant with a higher priority.

[0161] Optionally, in step 112, if the uplink grant is ignored, if the uplink grant is indicated by a PDCCH scrambled with CS-RNTI and / or if the configured scheduling timer corresponding to the identified HARQ process is running, stop the configured scheduling timer.

[0162] Optionally, in step 112, if the uplink grant received on PDCCH was addressed to CS-RNTI and the HARQ buffer of the identified HARQ process is empty, and if the configured grant timer corresponding to the identified HARQ process is running (only executed when the configured uplink grant and / or the configured grant timer are configured for the HARQ process), then stop the configured grant timer.

[0163] Optionally, in step 112, if the uplink grant is indicated by PDCCH and / or the PUSCH duration of the uplink grant overlaps with the PUSCH duration of another uplink grant with a higher priority, and if the configured grant timer corresponding to the identified HARQ process is running (only executed when the configured uplink grant and / or the configured grant timer are configured for the HARQ process), then stop the configured grant timer.

[0164] In step 113 (the same as step 009 in the third embodiment of the previous example), deliver the HARQ information (redundancy version) corresponding to the uplink grant and the transport block to the identified HARQ process; instruct the identified process to trigger a retransmission; if the received uplink grant corresponds to CS-RNTI or the received uplink grant is a configured uplink grant or the received uplink grant corresponds to C-RNTI and the identified HARQ process is configured with a configured uplink grant, then if the configured grant timer is configured, start or restart the configured grant timer configuredGrantTimer when the transmission is performed.

[0165] It should be noted that in the embodiments of the present disclosure, each HARQ process supports one transport block TB or two transport blocks (two transport blocks are supported in spatial multiplexing MIMO).

[0166] It should be noted that if the HARQ entity generates / obtains a MAC PDU for a lower-priority uplink scheduling (the PUSCH duration of the uplink scheduling overlaps with the PUSCH duration of a higher-priority uplink scheduling) and stores it in the buffer, or if the lower-priority uplink scheduling has data to send, it indicates that the multiplexing and assembly process includes a cached data indication MAC CE in the MAC PDU generated for the higher-priority uplink scheduling or triggers a low-priority data indication. Optionally, if the cached data indication is triggered and not cancelled, when the MAC entity is allocated uplink resources for new transmission, it indicates that the multiplexing and assembly process generates a cached data indication MAC CE and cancels the triggered cached data indication. Among them, that the lower-priority uplink scheduling has data to send can be determined by the priority obtained by the HARQ entity from the "process of determining uplink scheduling priority", so that the lower-priority uplink scheduling having data to send can also be described as the priority of the low-priority uplink scheduling not being a predefined value for no data and / or no data and MAC CE to send, for example, the priority of the low-priority uplink scheduling is greater than 0. The cached data indication MAC CE can indicate whether there is cached data in the lower-priority uplink scheduling where PUSCH duration overlap occurs or whether there is cached data in the buffer of the HARQ process identified by the low-priority uplink scheduling. For example, represented by a bitmap, each bit in the bitmap corresponds to a lower-priority uplink scheduling where PUSCH duration overlap occurs. When there is cached data in the buffer of the HARQ process corresponding to the uplink scheduling, the corresponding bit is set to 1 (or 0), otherwise it is set to 0 (or 1). Preferably, if the cached data indication MAC CE is included in the MAC PDU generated for dynamic scheduling, the configured schedulings with PUSCH duration overlap are correspondingly mapped to the bits from left to right (or from right to left) in the bitmap in ascending (or descending) order of the configured scheduling identifier. For example, the 0th bit of the bitmap corresponds to the configured scheduling with the smallest configured scheduling identifier where PUSCH duration overlap occurs, and so on. If the cached data indication MAC CE is included in the MAC PDU generated for configured scheduling, the 0th bit of the bitmap corresponds to dynamic, the 1st bit corresponds to the configured scheduling with the smallest configured scheduling identifier where PUSCH duration overlap occurs, and so on. The configured scheduling identifier is configured by the base station for each configured scheduling through RRC signaling / message, for example, included in the ConfiguredGrantConfig cell and configured when configuring the corresponding configured scheduling. Optionally, the priority of the cached data indication MAC CE is less than the priority of the PHR MAC CE (including Single Entry PHR MAC CE and Multiple Entry PHR MAC CE) and greater than the priority of the data from the logical channel (except for the data from UL-CCCH)

[0167] The following specifically describes an operation embodiment of the execution of the HARQ process of the user equipment UE when a DG / CG or CG / CG conflict occurs.

[0168] In one embodiment, if the HARQ entity requests to store a MAC PDU corresponding to a transport block (TB), or if the HARQ entity requests not to trigger a new transmission or retransmission, or if the HARQ process does not receive an indication from the HARQ entity to trigger a new transmission or retransmission, the HARQ process performs at least one of the following operations:

[0169] 1) Store the uplink grant received from the HARQ entity for storing the MAC PDU;

[0170] 2) Do not generate a transmission or retransmission.

[0171] It should be noted that in the present disclosure, unless otherwise specified, the scheduling refers to uplink scheduling. Dynamic scheduling refers to the uplink grant for a serving cell received on the PDCCH for the MAC entity's C-RNTI or CS-RNTI (in other words, the uplink grant received on the PDCCH). If the dynamic scheduling is for the CS-RNTI of the MAC entity, then NDI is 1; configured scheduling is the configured uplink grant.

[0172] The following describes an embodiment of the processing method of the multiplexing and assembly (which may also be the logical channel prioritization process LCP) process when multiple uplink grants are received.

[0173] In one embodiment, if the multiplexing and assembly process receives an uplink scheduling whose PUSCH duration overlaps with that of other uplink schedulings and whose priority is higher, and the multiplexing and assembly process has generated a MAC PDU for the uplink scheduling with the lower priority, the MAC control elements CE (including buffer status report BSR and power headroom report PHR) that have been included in the MAC PDU generated for the uplink scheduling with the lower priority are included in the MAC PDU generated for the uplink scheduling with the higher priority (if BSR is included therein, BSR needs to be recalculated and generated). If the MAC PDU generated for the uplink scheduling with the lower priority only contains MAC CE, all the MAC CE (the MAC CE includes BSR, PHR, configured scheduling acknowledgment MAC CE) are included in the MAC PDU generated for the uplink scheduling with the higher priority, and the MAC PDU generated for the uplink scheduling with the lower priority is cancelled (i.e., the HARQ buffer of the HARQ process corresponding to the uplink scheduling with the lower priority is cleared). Optionally, the configured scheduling timer of the HARQ process corresponding to the uplink scheduling with the lower priority is also stopped (if it is running).

[0174] In one embodiment, if multiple uplink schedulings of a serving cell are received, the MAC PDU is first generated for the uplink scheduling with the higher priority and the MAC CE (including BSR, PHR, configured scheduling acknowledgment MAC CE, if any) is included in this MAC PDU. If the priorities of the multiple received uplink schedulings are the same, if dynamic scheduling is included therein, the MAC PDU is generated for the dynamic scheduling and the MAC CE to be sent is included therein.

[0175] [Variant Example]

[0176] Next, use Figure 6 to illustrate a user equipment that can execute the method performed by the user equipment described in detail above according to the present invention as a variant example.

[0177] Figure 6 is a block diagram showing the user equipment UE related to the present invention.

[0178] As shown in Figure 6As shown, the user equipment UE60 includes a processor 601 and a memory 602. The processor 601 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 602 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories, etc. Program instructions are stored on the memory 602. When executed by the processor 601, the instructions can perform the above-described method executed by the user equipment as detailed in the present invention.

[0179] Next, Figure 7 is used to illustrate a base station that can execute the method executed by the base station as detailed above in the present invention as a variant example.

[0180] Figure 7 is a block diagram showing the base station related to the present invention.

[0181] As Figure 7 shown, the base station 70 includes a processor 701 and a memory 702. The processor 701 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 702 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories, etc. Program instructions are stored on the memory 702. When executed by the processor 701, the instructions can perform the above-described method executed by the base station as detailed in the present invention.

[0182] In addition, the present invention proposes a method executed by a base station. According to the method executed by the base station of the present invention, the base station indicates to the user equipment UE the priority for dynamic uplink scheduling and / or the priority for configured uplink scheduling. According to the priority indicated by the base station, the UE performs the operations described in the above embodiments.

[0183] The computer-executable instructions or programs running on the device according to the present invention can be programs that enable a computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU). The program or the information processed by the program can be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.

[0184] The computer-executable instructions or programs for implementing the functions of the embodiments of the present invention can be recorded on a computer-readable storage medium. The corresponding functions can be implemented by causing a computer system to read the programs recorded on the recording medium and execute these programs. The so-called "computer system" here can be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices). The "computer-readable storage medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for short-term dynamically storing programs, or any other recording medium readable by a computer.

[0185] The various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., single-chip or multi-chip integrated circuits). The circuits designed to execute the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor can be a microprocessor or any existing processor, controller, microcontroller, or state machine. The above circuits can be digital circuits or analog circuits. In the case where new integrated circuit technologies that replace existing integrated circuits emerge due to the progress of semiconductor technology, one or more embodiments of the present invention can also be implemented using these new integrated circuit technologies.

[0186] In addition, the present invention is not limited to the above embodiments. Although various examples of the embodiments have been described, the present invention is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV devices, kitchen appliances, cleaning devices, air conditioners, office equipment, vending machines, and other household appliances, etc.

[0187] As described above, the embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and the present invention also includes any design modifications that do not deviate from the gist of the present invention. In addition, various modifications can be made to the present invention within the scope of the claims, and the embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Moreover, the components having the same effects described in the above embodiments can be mutually replaced.

Claims

1. A user equipment UE, comprising: a receiving circuit configured to receive a first uplink scheduling on a physical downlink control channel PDCCH for a C-RNTI of a media access control MAC entity; and a controller circuit configured to consider that a new data indication NDI has been flipped for a corresponding HARQ process regardless of the value of the NDI if a previous uplink scheduling for the same HARQ process associated with the first uplink scheduling that is passed to a hybrid automatic repeat request HARQ entity is an uplink scheduling received for a CS-RNTI of the MAC entity or a configured uplink scheduling, wherein the controller circuit is configured to determine that there is no overlapping physical uplink shared channel PUSCH duration for a configured uplink scheduling for which the UE is configured with a first indication and whose priority is higher than the priority of the first uplink scheduling, wherein if the UE is not configured with the first indication or if the UE is configured with the first indication and there is no overlapping PUSCH duration for a configured uplink scheduling whose priority is higher than the priority of the first uplink scheduling, the controller circuit is configured to obtain a MAC protocol data unit PDU from a multiplexing and assembly entity by the HARQ entity for transmission corresponding to the HARQ process, wherein the first indication is used to indicate that the UE is configured with a priority ranking based on logical channel priorities between overlapping uplink schedulings.

2. A method performed by a user equipment UE, comprising: receiving a first uplink scheduling on a physical downlink control channel PDCCH for a C-RNTI of a media access control MAC entity; considering that a new data indication NDI has been flipped for a corresponding HARQ process regardless of the value of the NDI if a previous uplink scheduling for the same HARQ process associated with the first uplink scheduling that is passed to a hybrid automatic repeat request HARQ entity is an uplink scheduling received for a CS-RNTI of the MAC entity or a configured uplink scheduling; determining that there is no overlapping physical uplink shared channel PUSCH duration for a configured uplink scheduling for which the UE is configured with a first indication and whose priority is higher than the priority of the first uplink scheduling; and if the UE is not configured with the first indication or if the UE is configured with the first indication and there is no overlapping PUSCH duration for a configured uplink scheduling whose priority is higher than the priority of the first uplink scheduling, obtaining a MAC protocol data unit PDU from a multiplexing and assembly entity by the HARQ entity for transmission corresponding to the HARQ process, wherein the first indication is used to indicate that the UE is configured with a priority ranking based on logical channel priorities between overlapping uplink schedulings.

Images