WO2020259495A1 - 用户设备、基站及其方法 - Google Patents

用户设备、基站及其方法 Download PDF

Info

Publication number
WO2020259495A1
WO2020259495A1 PCT/CN2020/097724 CN2020097724W WO2020259495A1 WO 2020259495 A1 WO2020259495 A1 WO 2020259495A1 CN 2020097724 W CN2020097724 W CN 2020097724W WO 2020259495 A1 WO2020259495 A1 WO 2020259495A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink scheduling
scheduling
uplink
priority
harq process
Prior art date
Application number
PCT/CN2020/097724
Other languages
English (en)
French (fr)
Inventor
肖芳英
刘仁茂
山田升平
Original Assignee
夏普株式会社
肖芳英
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 肖芳英 filed Critical 夏普株式会社
Priority to US17/622,138 priority Critical patent/US12016049B2/en
Publication of WO2020259495A1 publication Critical patent/WO2020259495A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1806—Go-back-N protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path

Definitions

  • the present disclosure relates to the field of wireless communication technology, and more specifically, the present disclosure relates to user equipment, base stations and methods thereof.
  • Non-Patent Document: RP-190728: New WID: Support of NR Industrial Internet of Things (IoT) the user equipment (UE) needs to process traffic flows from different applications or devices at the same time. Therefore, it is necessary to consider when the uplink/downlink data channel and the control channel conflict in the user equipment (intra-UE) Priority processing and/or multiplexing, and processing of resource conflicts between dynamic scheduling (grant) and configuration scheduling, and between two or more configuration scheduling.
  • one of the goals of this work item is to enhance the resolution of resource conflicts between dynamic scheduling and configuration scheduling and between two or more configuration scheduling.
  • media access control MAC Medium Access Control
  • 3GPP Working Group 2 RAN2
  • PUSCH Physical Uplink Shared CHannel scheduling priority processing mechanism based on logical channel (LCH) priority and logical channel priority (LCP) restrictions.
  • LCH logical channel
  • LCP logical channel priority
  • the UE For low-priority PUSCH dynamic scheduling, the UE stores its corresponding low-priority MAC PDU in the HARQ buffer, so that gNB can use the same HARQ process Schedule retransmission (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 configuration of the low priority PUSCH process Uplink scheduling, a) The UE stores its corresponding low-priority MAC PDU in the HARQ buffer area so that the gNB can schedule retransmission, b) Whether the UE can retransmit on subsequent radio resources requires further discussion, for example Use the wireless resources that are subsequently associated with the same HARQ process (For de-prioritized PUSCH on configured grants, a) the UE could store the de-prioritized MAC
  • the present invention provides a user equipment, a base station and a method thereof, which can resolve DG/CG PUSCH conflicts between different HARQ processes and CG/CG conflicts between different HARQ processes by setting an enable priority indicator. It conflicts with uplink scheduling/MAC PDU of the same HARQ process.
  • a method executed by a user equipment UE includes: receiving dynamic uplink scheduling for a medium access control MAC entity; and judging whether the received dynamic uplink scheduling satisfies the first Setting conditions; if the first setting conditions are met, the uplink dynamic scheduling is submitted to the hybrid automatic repeat request HARQ entity.
  • the first setting condition includes any one or any combination of the following conditions: whether the first enabling priority indicator is configured; and whether the received dynamic uplink scheduling physical uplink shared channel PUSCH duration It overlaps with other uplink scheduled PUSCH durations.
  • the first enable priority indicator indicates that when a physical uplink shared channel PUSCH conflict of uplink scheduling occurs on different HARQ processes, the comparison of priorities between the conflicted uplink scheduling is supported.
  • the first setting condition includes any one or any combination of the following conditions: whether the second enable priority indicator is configured; whether the corresponding configured uplink scheduling timer is running; the received dynamic uplink Whether the priority of the scheduling is higher than the priority of the MAC PDU stored in the buffer area of the same HARQ process, that is, the priority of the MAC protocol data unit; and whether the priority of the received dynamic uplink scheduling is higher than the priority of the previous uplink scheduling.
  • the second enable priority indicator indicates that when a conflict between uplink scheduling and MAC PDU, that is, a MAC protocol data unit, occurs on the same HARQ process, the priority between the conflicting uplink scheduling and MAC PDU is supported Comparison.
  • a method executed by a user equipment UE includes: for each serving cell, receiving configured uplink scheduling for a medium access control MAC entity; determining whether the received configured uplink scheduling is The second setting condition is satisfied; if the second setting condition is satisfied, the configured uplink scheduling is submitted to the hybrid automatic repeat request HARQ entity.
  • the second setting condition includes any one or any combination of the following conditions: whether the first enabling priority indicator is configured; and whether the received physical uplink shared channel PUSCH duration configured for uplink scheduling is It overlaps with other uplink scheduled PUSCH durations.
  • the second setting condition includes any one or any combination of the following conditions: whether a second enable priority indicator is configured; whether the corresponding configured uplink scheduling timer is running; and the configured uplink scheduling Whether the priority of is higher than the priority of the MAC PDU stored in the corresponding HARQ buffer area, that is, the MAC protocol data unit.
  • the priority of the dynamic uplink scheduling is indicated in the corresponding downlink control information DCI, and the priority of configuring the uplink scheduling is configured by the base station through radio resource control RRC signaling.
  • a user equipment including: a processor; and a memory storing instructions; wherein the instructions execute the above-mentioned method when run by the processor.
  • a method executed by a base station including: sending a first enabling priority indicator and/or a second enabling priority indicator to user equipment UE, and when the first enabling priority indicator is received When enabling the priority indicator and/or the second enabling priority indicator, the UE executes the foregoing method.
  • a base station which includes: a processor; and a memory storing instructions, wherein the instructions execute the above-mentioned method when run by the processor.
  • the DG/CG PUSCH conflicts of different HARQ processes, the CG/CG conflicts of different HARQ processes, and the uplink scheduling/MAC PDU conflicts of the same HARQ process can be resolved by setting the enable priority indicator.
  • Figure 1 shows a schematic diagram of uplink scheduling conflicts.
  • Fig. 2 is a flowchart showing a method executed by a user equipment according to the first embodiment of the present invention.
  • Fig. 3 is a flowchart showing a method executed by a user equipment according to the second embodiment of the present invention.
  • Fig. 4 is a flowchart showing a method executed by a user equipment according to the third embodiment of the present invention.
  • Fig. 5 is a flowchart showing a method executed by a user equipment according to the fourth embodiment of the present invention.
  • Fig. 6 is a block diagram schematically showing a user equipment involved in the present invention.
  • Fig. 7 is a block diagram schematically showing a base station involved in the present invention.
  • RRC Radio Resource Control, radio resource control.
  • MAC Medium Access Control, media access control.
  • PDCCH Physical Downlink Control Channel, physical downlink control channel.
  • PUSCH Physical Uplink Shared Channel, physical uplink shared channel.
  • SDU Service Data Unit, service data unit.
  • PDU Protocol Data Unit, protocol data unit.
  • CG Configured uplink Grant, configure scheduling or configure uplink scheduling.
  • DG Dynamic Grant
  • dynamic scheduling refers to the uplink scheduling dynamically received on the PDCCH.
  • the uplink scheduling of the C-RNTI or TC-RNTI (Temporary C-RNTI) or CS-RNTI of the MAC entity received on the PDCCH is scrambled by the C-RNTI or TC-RNTI or CS-RNTI of the MAC entity
  • these two expressions can be used interchangeably.
  • HARQ information HARQ information, HARQ information transmitted on DL-SCH or UL-SCH is indicated by new data (New Data Indicator, NDI), Transport Block size (TBS), Redundancy Version (RV), and HARQ process ID (HARQ process ID) composition.
  • new data New Data Indicator, NDI
  • Transport Block size TBS
  • Redundancy Version RV
  • HARQ process ID HARQ process ID composition.
  • CS-RNTI Configured Scheduling RNTI, configure scheduling RNTI.
  • ra-ResponseWindow Random access response window.
  • the UE receives random access responses in the random access response window.
  • the PUSCH duration (duration) of the dynamically scheduled DG on a certain HARQ process overlaps with the PUSCH duration of the scheduled CG configured on another HARQ process, which is called a different HARQ process DG.
  • /CG PUSCH conflict or DG/CG conflict of different HARQ processes In a serving cell, the PUSCH duration configured to schedule a CG on a certain HARQ process overlaps with the PUSCH duration configured to schedule a CG on another HARQ process, which is called a CG/CG PUSCH conflict between different HARQ processes or a different HARQ process CG/ CG conflict.
  • the overlap of the PUSCH duration of the dynamically scheduled DG on a certain HARQ process with the PUSCH duration of the configured scheduled CG on the HARQ process is called the same HARQ process DG/CG conflict.
  • the conflict between the uplink scheduling on a certain HARQ process and the MAC PDU stored in the HARQ buffer area of the HARQ process that has not been sent (or has been sent but has not been confirmed to be sent successfully) (this conflict is mainly a conflict using the HARQ buffer area) , Because each HARQ process is associated with a HARQ buffer area, if a MAC PDU is generated for the uplink scheduling, then the existing MAC PDU stored in the HARQ buffer area will be overwritten/destroyed) It is called the same HARQ process uplink scheduling/MAC PDU conflict .
  • DG/CG PUSCH conflicts between different HARQ processes include a PUSCH duration conflict between one DG and multiple CGs on different HARQ processes.
  • CG/CG PUSCH conflicts in different HARQ processes also include PUSCH duration conflicts among multiple CGs.
  • the DG/CG or CG/CG conflicts described in the embodiments of the present disclosure include the above types of conflicts, and the conflicts refer to the conflicting DG and CG and the conflicting two or more CGs.
  • PUSCH overlap in different uplink schedules means that different uplink schedules overlap in the time domain.
  • the UE or the MAC entity When the configured scheduling timer of the corresponding HARQ process expires or the dynamic scheduling of NDI flipping is received after the transmission of a MAC PDU is completed, the UE or the MAC entity considers that the MAC PDU is successfully transmitted.
  • the user equipment UE receives the uplink scheduling (DG or CG) (which can be executed by the uplink scheduling reception in the UE), and the uplink scheduling and other uplink scheduling (CG or DG) have different HARQ processes DG/CG PUSCH conflict (the base station configures the UE for the UE) CG), the priority of DG and CG is judged and the corresponding operation is executed according to the judgment result (which can be executed by the uplink scheduling reception in the UE or the HARQ entity).
  • DG or CG uplink scheduling
  • CG or DG uplink scheduling and other uplink scheduling
  • DG and/or CG are used for new transmission (for example, for DG, it is used for new transmission when NDI is overturned, and for CG, when the corresponding configuredGrantTimer is not running, it is used for new transmission),
  • a DG/CG PUSCH conflict between different HARQ processes occurs, if the priority of the DG is higher, the UE does not generate a MAC PDU for the CG and ignores the CG.
  • the MAC PDU is generated/obtained for the DG (which can be executed by the HARQ entity) and stored in the buffer of the corresponding HARQ process (which can be The corresponding HARQ process is executed); if the DG is used for retransmission, the configured scheduling timer configuredGrantTimer (which can be executed by the HARQ entity) is restarted.
  • the following specifically describes an embodiment of the operation performed by the uplink scheduling reception (UL Grant reception) of the user equipment UE when a DG/CG or CG/CG conflict occurs.
  • the uplink scheduling of the UE receives the uplink scheduling of the C-RNTI received as the MAC entity on the PDCCH. If the first enabling priority indicator is configured and/or the 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), if the The uplink scheduled PUSCH duration does not overlap with the duration of other uplink scheduled PUSCHs or only overlaps with the duration of the PUSCH of other uplink scheduling (such as CG) whose priority is lower or not higher than the uplink scheduling, then the uplink The scheduling and/or 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 to configure uplink scheduling
  • the first enable 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 identifier appears)
  • the judgment condition "whether the previous uplink scheduling of the same HARQ process submitted to the HARQ entity is configured uplink scheduling or is the uplink scheduling of the CS-RNTI of the MAC entity" can be independent of whether the judgment condition is configured with the first Enable the priority indicator, that is, for the received uplink scheduling, as long as the uplink scheduling of the same HARQ process submitted to the HARQ entity is configured uplink scheduling or the uplink scheduling of the CS-RNTI of the MAC entity, it is considered NDI rollover corresponding to HARQ process.
  • the first 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 identifier does not appear) (this condition is optional), and if the PUSCH duration of the configuration scheduling is only related to other uplink scheduling scheduling with a priority lower (or not higher than) the configuration scheduling The duration of the PUSCH overlaps or the duration of the PUSCH scheduled by this configuration does not overlap with the duration of other uplink scheduled PUSCHs.
  • this condition is optional (here In the case that 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 the configuration scheduling and/ Or the related HARQ information is indicated to the HARQ entity. Optionally, it is also considered that the NDI corresponding to the HARQ process is reversed.
  • the configuration scheduling timer of the corresponding HARQ process it is also necessary to determine whether the priority of the configuration scheduling is higher than the priority of the MAC PDU saved (or saved and not yet sent) in the HARQ process buffer If the priority of the configuration scheduling is higher than the priority of the MAC PDU stored (or saved and not yet sent) in the HARQ process buffer, then the configuration scheduling and/or related HARQ information will be indicated to HARQ
  • the entity optionally, also considers the NDI rollover corresponding to the HARQ process. (Applicable to support the same HARQ process CG/MAC PDU conflict)
  • the configuration scheduling timer of the corresponding HARQ process is running, it is also necessary to determine whether the second enable priority indicator is configured and whether the priority of the configuration scheduling is higher than that stored in the HARQ process buffer.
  • the priority of MAC PDU (or saved and not yet sent) is higher.
  • 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
  • the 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 priority of the configuration scheduling is higher than that stored in the HARQ process buffer (or saved and not yet
  • the transmitted MAC PDU has a higher priority
  • the configuration scheduling and/or related HARQ information is indicated to the HARQ entity.
  • the NDI corresponding to the HARQ process is reversed. (Applicable to support the same HARQ process CG/MAC PDU conflict)
  • the other uplink scheduling described in the present disclosure includes uplink scheduling received on the PDCCH and/or other configuration scheduling and/or uplink scheduling in a random access response.
  • the PUSCH duration of a certain uplink scheduling only overlaps with the duration of other uplink scheduling PUSCHs whose priority is lower or not higher than that of the uplink scheduling, which means that the PUSCH duration of the uplink scheduling does not correspond to the priority.
  • the uplink scheduling of the UE receives the uplink scheduling of the C-RNTI that is the MAC entity on the PDCCH. If the second enable priority indicator is configured and the identifier is The value of 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), if the uplink If the configuration scheduling timer of the corresponding HARQ process is not running, the uplink scheduling and/or related HARQ information is indicated to the HARQ entity; optionally, if the same HARQ process (that is, the received one) is delivered to the HARQ entity before When the uplink scheduling of the HARQ process corresponding to the uplink scheduling is configured to configure the uplink scheduling or the uplink scheduling of the CS-RNTI of the MAC entity, it is considered that the NDI of the corresponding HARQ process is reversed regardless of
  • the configured scheduling timer of the HARQ process corresponding to the uplink scheduling is running and if the uplink scheduling of the same HARQ process (the HARQ process corresponding to the received uplink scheduling) that was previously submitted to the HARQ entity is configured for uplink scheduling or is MAC
  • the entity s CS-RNTI uplink scheduling and if the received uplink scheduling priority is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the HARQ process buffer, then the received
  • the uplink scheduling and/or related HARQ information is indicated to the HARQ entity, and optionally, it is considered that the NDI corresponding to the HARQ process is reversed.
  • the first enabling priority indicator is applied to DG/CG or CG/CG PUSCH conflicts on different HARQ processes
  • the second enabling priority indicator is applied to the same HARQ process DG/CG or Uplink scheduling/MAC PDU conflict.
  • the enable priority indicator is configured (including the first enable priority indicator and the second enable priority indicator) and/or the value of the identifier is 1 or true or TRUE or setup or the first predefined
  • the value of or the occurrence of the identifier means that a different HARQ process DG/CG or CG/CG occurs
  • the system or UE supports comparing the conflicting uplink scheduling and/or MAC PDU priority, and executes the operations defined in the embodiment according to the comparison result.
  • the first enable priority indication flag is not configured or the value of the flag is 0 or false or False or release or the 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 first predefined value or the identifier appears) means that the system or LIE does not support the enable priority indicator or when different HARQ processes DG/CG PUSCH conflicts, the priority of DG is always considered Higher, that is, the NDI corresponding to the HARQ process is considered to be reversed and the DG and its HARQ information are delivered to the HARQ entity.
  • the value of the enable priority indicator is not limited to the listed values, and may also be other predetermined values, such as enable and/or disable.
  • the system or UE does not support the enabling priority indicator, it only judges whether other conditions are met and ignores the judgment on whether the enabling priority indicator is configured.
  • the first enable priority indicator and the second enable priority indicator can be combined into one indicator (denoted as the enable priority indicator). Accordingly, the first enable priority indicator in the embodiment of the present disclosure Both the identifier and the second enable priority indicator are replaced with the enable priority indicator.
  • DG is always considered to have a higher priority than CG.
  • DG always covers CG, and DG is used to transmit data and ignore CG. .
  • the DG when a DG is received, the DG is always delivered to the HARQ entity, and the HARQ entity constructs a MAC PDU for the DG (for new transmissions) or instructs the HARQ process to retransmit;
  • the CG when the CG is received, if the PUSCH duration of the CG is not Only when the PUSCH duration overlaps with other uplink scheduled PUSCH and the configured scheduling timer of the corresponding HARQ process is not running, the CG is delivered to the HARQ entity.
  • the enabling priority indicator (including the first and/or second enabling priority indicator) is introduced to instruct the UE to handle different HARQ process DG/CG PUSCH duration conflicts and/or different HARQ process CG /CG PUSCH duration conflict and/or same HARQ process DG/CG conflict and/or same HARQ process uplink scheduling/MAC PDU conflict (indicating UE to compare priority when conflict occurs), so that CG with higher priority can be covered
  • a DG with a lower priority (or other CG) may use a higher priority uplink scheduling to transmit data or submit a higher priority uplink scheduling to the HARQ entity or generate/obtain MAC PDUs for the higher priority uplink scheduling or Ignore the lower priority DGs.
  • the enabling priority indicator (including the first and/or second enabling priority indicator) is configured by the base station in advance for the user equipment UE through RRC signaling/message (for example, when configuring the scheduling for the UE).
  • the enabling priority indication identifier may be included in the information element BWP-UplinkDedicated used to configure the UE-specific parameters of the uplink bandwidth segment BWP or included in the system information).
  • the identifier can be used to indicate whether to use a CG with a higher priority and ignore a DG with a lower priority when a DG/CG conflict occurs, or whether to submit to the HARQ entity or whether to generate/generate a DG with a lower priority when a DG with a lower priority is received.
  • the higher priority uplink scheduling is submitted to the HARQ entity, and the HARQ entity generates MAC PDU for it, which will cause the CG with lower priority to be ignored or saved in the corresponding HARQ process
  • the MAC PDU generated for lower priority uplink scheduling (this MAC PDU may have not been sent, or has been sent but has not been confirmed to be received correctly (for example, the corresponding configured scheduling timer is running)) will be flushed or Covers MAC PDUs generated for higher priority uplink scheduling.
  • the first and/or second enable priority indicator may be included in the ConfiguredGrantConfig information element, and the ConfiguredGrantConfig information element is used to configure uplink transmission according to two possible mechanisms when there is no dynamic scheduling (the IE ConfiguredGrantConfig is used to configure uplink transmission without dynamic grant according to two possible schemes; the actual uplink scheduling can be configured through RRC (type 1) or provided by PDCCH (address is CS-RNTI) (type 2).
  • the uplink scheduling transmission data with higher priority is used or the priority is higher
  • the uplink scheduling is submitted to the HARQ entity or the MAC PDU is constructed for the uplink scheduling with higher priority; when the value of the enable priority indication flag is 0 or false or False or release or the flag does not appear, always It is considered that the priority of DG is the highest or the priority of DG is higher than that of CG or the priority of uplink scheduling is higher than the priority of MAC PDU stored (or stored and not yet sent) in the corresponding HARQ process buffer. vice versa.
  • Fig. 2 is a flowchart showing a method executed by a user equipment according to the first embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S201, step S203, and step S205.
  • step S201 the uplink scheduling of the user equipment UE receives the uplink scheduling (dynamic uplink scheduling) of the C-RNTI received as the MAC entity on the PDCCH.
  • step S203 for the received dynamic uplink scheduling, it is determined whether the first setting condition described below is satisfied.
  • step S205 when the current uplink scheduling of the same HARQ process (that is, the HARQ process corresponding to the received uplink scheduling) delivered to the HARQ entity is configured for uplink scheduling or is the uplink scheduling of the CS-RNTI of the MAC entity, if the first Once the conditions are set, it is considered that the NDI corresponding to the HARQ process is flipped regardless of the value of the NDI, and optionally, the uplink dynamic scheduling is also submitted to the HARQ entity.
  • the first setting condition may be any one or any combination of the following:
  • the user equipment is configured with the first enable priority indicator 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 identifier appears The value is 0 or false or False or release or the flag does not appear); and if the received uplink scheduled PUSCH duration does not overlap with other uplink scheduled PUSCH durations or does not overlap with other higher priority uplink schedules
  • the PUSCH duration overlaps or only overlaps with other uplink scheduled PUSCHs whose priority is lower or not higher than that of the uplink scheduling; and the priority of the received uplink scheduling is higher than that stored in the HARQ process buffer (or saved
  • the MAC PDU that has not been sent has a higher priority (this condition is optional); and the configuration scheduling timer of the HARQ process is running (this condition is optional).
  • the user equipment is configured with the first enable priority indicator 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 identifier is The value is 0 or false or False or release or the flag does not appear); and if the received uplink scheduled PUSCH duration does not overlap with other uplink scheduled PUSCH durations or does not overlap with other higher priority uplink schedules The duration of the PUSCH overlaps or only overlaps with the duration of other uplink scheduled PUSCHs whose priority is lower or not higher than the uplink scheduling; and the configuration scheduling timer of the HARQ process is not running (this condition is optional).
  • 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 the first predefined value or the identifier appears (or the identifier appears The value is 0 or false or False or release or the flag does not appear), and the configured scheduling timer corresponding to the HARQ process is running (this condition is optional), and the received uplink scheduling priority is higher than the HARQ
  • the MAC PDU stored in the process buffer (or stored and not yet sent) has a higher priority.
  • 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 the corresponding HARQ process; and the configuration scheduling timer of the HARQ process is running (this condition Is optional).
  • the received uplink schedule has a higher priority than the previous uplink schedule (or the received uplink schedule has a higher priority than the previous uplink schedule that generated MAC PDU but did not send, or the received uplink schedule has a higher priority than the previous one.
  • a MAC PDU that has been generated but is ignored has a higher priority for uplink tuning); and the configuration scheduling timer corresponding to the HARQ process is running (this condition is optional).
  • the configured scheduling timer corresponding to the HARQ process corresponding to the received uplink scheduling is not running
  • the first enable priority indication flag is not configured or the value of the flag is 0 or false or False or release or the 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 identifier appears), optionally, and if the received uplink scheduled PUSCH duration does not overlap with other uplink scheduled PUSCH durations or does not overlap with other higher priority uplink schedules
  • the PUSCH duration overlaps or only overlaps with other uplink scheduled PUSCH durations whose priority is lower or not higher than the uplink scheduling.
  • first setting condition (1-8) all the conditions can be divided into two types.
  • One type is used to deal with DG/CG PUSCH duration conflicts on different HARQ processes.
  • Such conditions include any of the following or Any combination thereof: whether the first enable priority indicator is configured, and whether the received uplink scheduled PUSCH duration overlaps with other uplink scheduled PUSCH durations.
  • Another type of condition is used to deal with the same HARQ process DG/CG or uplink scheduling/MAC PDU conflict.
  • This type of condition includes any one or any combination of the following: whether the second enable priority indicator is configured and the corresponding configuration Whether the scheduling timer is running, whether the priority of the received uplink scheduling is higher than the priority of the MAC PDU stored (or saved and not yet sent) in the HARQ process buffer, and whether the received uplink scheduling is higher than the previous one
  • the uplink scheduling priority is higher.
  • the MAC PDU generated for this uplink scheduling will cover the MAC PDU stored in the current HARQ buffer), then the first set condition does not include the DG/CG or uplink scheduling used to process the same HARQ process /MAC PDU conflict conditions.
  • the priority of the received uplink scheduling in the present disclosure is higher than the priority of the MAC PDU stored (or stored and not yet sent) in the HARQ process buffer, which can be replaced by the priority of the received uplink scheduling
  • the level is not lower than the priority of the MAC PDU stored in the HARQ process buffer (or stored and not yet sent).
  • each of the above conditions (1-8) contains multiple judgment conditions (except condition (7)).
  • the execution order of these judgment conditions in each item includes but is not limited to the order listed above. The order of these judgment conditions can be exchanged to form a new embodiment.
  • the uplink scheduling of the user equipment UE receives the uplink scheduling of the C-RNTI that is the MAC entity on the PDCCH, and meets the first set condition, at least one of the following operations may be performed:
  • the corresponding HARQ process is configured with a configured scheduling timer, start or restart the configured scheduling timer (start or restart the configured Grant Timer for the correponding HARQ process, if configured) of the corresponding HARQ process.
  • the uplink scheduling of the user equipment UE receives the uplink scheduling of the C-RNTI that is the MAC entity on the PDCCH and does not meet the first set condition, at least one of the following operations is performed:
  • the uplink scheduling of the user equipment UE receives the uplink scheduling of the C-RNTI that is the MAC entity on the PDCCH. If the same HARQ process previously delivered to the HARQ entity (that is, the received uplink scheduling corresponds to The uplink scheduling of the HARQ process is configured to configure the uplink scheduling or the uplink scheduling of the CS-RNTI of the MAC entity, and the NDI corresponding to the HARQ process is considered to be reversed regardless of the value of the NDI (consider the NDI to have toggled for the corresponding HARQ process Regardless of the value of the NDI). If the foregoing first set condition is satisfied, other operations that can be performed when the foregoing first set condition is satisfied may be performed.
  • the MAC PDU stored in the HARQ process buffer and not yet sent refers to that the HARQ process buffer is not empty and the MAC PDU stored therein has not been sent or the HARQ process buffer contains the MAC PDU that has not been sent .
  • the HARQ entity When there is a conflict between DG and CG or between CG and CG corresponding to different HARQ processes, the HARQ entity generates MAC PDU for the uplink scheduling with lower priority and stores it in the buffer area, but because the corresponding uplink scheduling priority is lower The MAC PDU is ignored without using the uplink scheduling.
  • the MAC PDU refers to the MAC PDU that has not been sent, and may also be referred to as the MAC PDU waiting for initial transmission.
  • Fig. 3 is a flowchart showing a method executed by a user equipment according to the second embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S301, step S303, and step S305.
  • step S301 for each serving cell, receive the configured uplink scheduling for the MAC entity (the MAC entity can perform the following operations),
  • step S303 for the received configuration uplink scheduling, it is determined whether the second setting condition is satisfied.
  • step S305 if the second setting condition is met, perform one or more of the following operations (for example, submit the configured uplink scheduling to the HARQ entity):
  • the configuration scheduling timer corresponding to the HARQ process is running and there is an unsent MAC PDU in the HARQ buffer area (for example, the MAC PDU is generated for the previous configuration with lower priority uplink scheduling), it is considered The NDI corresponding to the HARQ process is not flipped.
  • the configured uplink scheduling is ignored or the configured uplink scheduling is not submitted to the HARQ entity.
  • the second set condition may be any one or any combination:
  • the UE is configured with the first enable priority indicator and 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 flag does not appear); and the configuration scheduling timer corresponding to the HARQ process is not running (optional).
  • the UE is configured with the first enable priority indicator and 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); and (or) the PUSCH duration configured for uplink scheduling overlaps with other uplink scheduling PUSCH durations of the same serving cell, but the configured uplink scheduling priority is higher or the Configure the uplink scheduling not to overlap with the PUSCH duration of other uplink scheduling in the same serving cell or configure the PUSCH duration of the uplink scheduling only to overlap with the PUSCH duration of other uplink scheduling with a priority lower (or not higher) than that of the configured uplink scheduling ; And the configuration scheduling timing of the corresponding HARQ process is running but the configuration scheduling priority is higher (compared with the priority of the MAC PDU in the buffer) (optional) or the configuration scheduling of the HARQ process corresponding to the configuration uplink scheduling The timer is not running.
  • the UE is not configured with the first enable priority indicator 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 (or the value of the identifier Is 1 or true or TRUE or setup or the identifier appears), and/or configure the uplink scheduling PUSCH duration and the uplink scheduling PUSCH duration of the same serving cell received on the PDCCH or other configured uplinks on the same serving cell
  • the scheduled PUSCH duration or the uplink scheduled PUSCH duration in the random access response do not overlap; and the configured scheduling timer corresponding to the HARQ process is not running.
  • the configuration scheduling timer corresponding to the HARQ process is running, if a second enable priority indicator is configured or the value of the flag 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 configuration scheduling priority is higher (compared with the priority of the MAC PDU in the buffer).
  • the PUSCH duration of the configured uplink scheduling overlaps with the PUSCH duration of the uplink scheduling of the same serving cell received on the PDCCH or overlaps with the PUSCH duration of other configured uplink scheduling on the same serving cell, but the configuration of the uplink scheduling has priority Higher level; or the PUSCH duration of the configured uplink scheduling does not overlap with the PUSCH duration of the uplink scheduling in the random access response, but is the same as the uplink scheduling of the same serving cell received on the PDCCH or other configured uplink scheduling of the same serving cell
  • the PUSCH duration overlaps, but this configuration has a higher priority for uplink scheduling.
  • the UE is configured with a second enabling priority indicator and 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 identification does not appear); and the configuration scheduling timing of the corresponding HARQ process is running (optional) but the configuration scheduling priority is higher (compare with the priority of the MAC PDU in the buffer Compare) or the configuration scheduling timer of the HARQ process corresponding to the configured uplink scheduling is not running.
  • the configuration is ignored Uplink scheduling or not submitting the configured uplink scheduling to the HARQ entity (that is, it is always considered that the uplink scheduling priority in the random access response is the highest, which can also be applied to other embodiments of the present disclosure).
  • all conditions can be divided into two types.
  • One type is used to deal with DG/CG or CG/CG PUSCH duration conflicts on different HARQ processes.
  • Such conditions include the following Any one or any combination thereof: whether the first enable priority indicator is configured, whether the received PUSCH duration configured for uplink scheduling is consistent with other uplink scheduling (such as another configured uplink scheduling or DG or random access response (Uplink scheduling) PUSCH duration overlap.
  • Another type of condition is used to handle the same HARQ process configuration uplink scheduling/MAC PDU conflict.
  • This type of condition includes any one or any combination of the following: whether the second enable priority indicator is configured, the corresponding configuration scheduling timer It is running but the scheduling priority of this configuration is higher (compared with the priority of the MAC PDU in the buffer).
  • These two types of conditions are only required when the system or UE supports handling of the corresponding type of conflict, for example, if the system or UE does not support handling the same HARQ process configuration uplink scheduling/MAC PDU conflict (in other words, if the corresponding configuration scheduling timer is running , The configured uplink scheduling is not submitted to the HARQ entity), and the first setting condition does not include the condition for handling the configuration uplink scheduling/MAC PDU conflict of the same HARQ process.
  • the second setting condition (1-5) above is about whether All judgments configured with the enable priority indicator can be deleted.
  • 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.
  • the uplink scheduling of the C-RNTI or CS-RNTI or TC-RNTI of the MAC entity or the uplink scheduling of the C-RNTI or CS-RNTI or TC-RNTI of the MAC entity received on the PDCCH is Refers to the uplink scheduling indicated by the PDCCH scrambled by C-RNTI or CS-RNTI or TC-RNTI.
  • the priority of dynamic scheduling can be indicated in its corresponding downlink control information DCI, and the priority of configuration scheduling can be configured by the base station through RRC signaling/message or in the downlink control information DCI used to activate the configuration scheduling. Indication, it can also be the highest priority ( That is, the priority of the logical channel with the highest priority corresponding to the contained data) or the priority of the logical channel with the highest priority corresponding to the data contained 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 with the highest priority corresponding to the data contained in the MAC PDU or the priority of the uplink scheduling corresponding to the MAC PDU (the MAC PDU is a MAC PDU generated for the uplink scheduling).
  • the priority of a certain uplink scheduling and MAC PDU comparison means that the priority of the uplink scheduling is compared with the priority of the uplink scheduling corresponding to the MAC PDU or the priority of the MAC PDU generated for the uplink scheduling and the priority of the MAC PDU Compare.
  • the priority comparison between the uplink scheduling is the priority of their corresponding MAC PDU or their corresponding priority Comparison of the priority of the logical channel with the highest level.
  • the uplink scheduling receiving 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 scheduling, for example, to multiplexing and The assembly process obtains the priority, and then compares the obtained priority with the priority of other uplink scheduling.
  • Determination of uplink scheduling priority process (such as multiplexing and assembly process) when receiving an instruction to obtain uplink scheduling priority, according to the logical channel priority LCP limitation (or the mapping restriction configured by RRC for each logical channel) Determine the priority of the logical channel with the highest priority corresponding to the data that the uplink scheduling can send or reuse or to be multiplexed, or the priority of the logical channel with the highest priority among the logical channels selected or preselected for the uplink scheduling
  • the priority of the uplink scheduling (the process of determining the priority of the uplink scheduling" there is data to be sent in the logical channel selected. If there is no data to send in all the logical channels according to the LCP rules, the priority of the corresponding uplink scheduling is A predefined value, for example, 0.
  • the uplink scheduling receiving has acquired/received the priority of a certain uplink scheduling, when the uplink scheduling receiving submits the uplink scheduling to the HARQ entity, the priority of the uplink scheduling may also be submitted to the HARQ entity.
  • the priority of a certain uplink scheduling is received from the uplink scheduling, there is no need to obtain the priority of the uplink scheduling from the "process for determining the priority of uplink scheduling", but if an uplink scheduling is not received
  • the priority of the uplink scheduling can be obtained from the "procedure for determining the priority of uplink scheduling”.
  • the priority of the uplink scheduling is also indicated to the HARQ process.
  • the following specifically describes an operation embodiment performed by the HARQ entity of the user equipment UE when a DG/CG or CG/CG conflict occurs.
  • the following describes a processing method of the HARQ entity for the received uplink scheduling.
  • the PUSCH duration of other uplink scheduling For uplink scheduling where the PUSCH duration does not overlap with the PUSCH duration of other uplink scheduling, or for uplink scheduling where the PUSCH duration only overlaps with the PUSCH duration of other uplink scheduling with lower priority, or the PUSCH duration of the uplink scheduling Dynamic scheduling that overlaps with the PUSCH duration of other uplink scheduling with lower priority, or the PUSCH duration does not overlap with the PUSCH duration of other uplink scheduling with higher priority, identifies the HARQ process of the uplink scheduling, and is The HARQ process, perform the following operations:
  • the uplink scheduling is used for new transmission (that is, the new transmission condition is satisfied, for example, the condition for obtaining MAC PDU is given in step 002/003 of the following embodiment), then MAC PDU is obtained.
  • the MAC PDU is obtained, the MAC PDU, the uplink schedule, and the HARQ information of the transport block of the identified HARQ process are delivered to the identified HARQ process, indicating that the identified HARQ process triggers a new transmission. If the requirements for starting the identified HARQ process are met Configure the condition of the scheduling timer, then start or restart the configured scheduling timer of the identified HARQ process.
  • the HARQ buffer area of the identified HARQ process is cleared, and optionally, the configured scheduling timer of the identified HARQ process (if running) is stopped.
  • MAC PDU For uplink scheduling where the PUSCH duration overlaps with the PUSCH duration of other higher priority uplink scheduling, if the uplink scheduling is used for new transmission (that is, the new transmission conditions are met, for example, the acquisition given in the following embodiment MAC PDU condition), then MAC PDU is obtained.
  • the MAC PDU is delivered to the identified HARQ process, and the uplink scheduling and/or HARQ information of the transport block of the identified HARQ process is delivered to the identified HARQ process (this operation is optional), Indicate that the recognized HARQ process does not trigger new transmission (or does not indicate that the recognized HARQ process triggers new transmission or indicates that the recognized HARQ process stores MAC PDU) (this operation is also optional), if the configuration scheduling timing for starting the recognized HARQ process is met Condition of the device, start or restart the configured scheduling timer of the identified HARQ process. If the MAC PDU is not obtained, the HARQ buffer area of the identified HARQ process is cleared, and optionally, the configured scheduling timer of the identified HARQ process (if running) is stopped.
  • the uplink scheduling is used for new transmission (that is, the new transmission conditions are met, for example, the acquisition given in the following embodiment MAC PDU condition)
  • the HARQ buffer area of the identified HARQ process is cleared, and optionally, the configured scheduling timer of the identified HARQ process (if running) is stopped.
  • the uplink scheduling used for retransmission (that is, the condition for new transmission is not met)
  • the uplink scheduling is ignored
  • indicate that the identified HARQ process does not trigger retransmission (or do not indicate that the identified HARQ process triggers retransmission)
  • the conditions for starting the configured scheduling timer of the identified HARQ process are met, start or restart The configured scheduling timer of the identified HARQ process.
  • the following is another way of processing the received uplink scheduling by the HARQ entity.
  • For each uplink scheduling identify the HARQ process of this uplink scheduling. For the identified HARQ process, if the uplink scheduling is used for new transmission (that is, the new transmission conditions are met, for example, the MAC PDU is obtained in step 002/003 of the following embodiment) Condition), then get MAC PDU.
  • the MAC PDU is delivered to the identified HARQ process, optionally, the uplink scheduling and/or HARQ information of the transport block of the identified HARQ process is also delivered to the identified HARQ process, optional If the PUSCH duration of the uplink scheduling overlaps with the PUSCH duration of other higher priority uplink scheduling, then the identified HARQ process does not trigger the new transmission or the identified HARQ process does not trigger the new transmission or the identified HARQ process Store MAC PDU, and if the conditions for starting the configured scheduling timer of the identified HARQ process are met, start or restart the configured scheduling timer of the identified HARQ process; if the uplink scheduling PUSCH duration is only lower than (or not) the priority Higher than) that the PUSCH duration of other uplink scheduling of the uplink scheduling overlaps, indicating that the identified HARQ process triggers a new transmission.
  • the HARQ information of the transmission block of the uplink scheduling and/or the identified HARQ process is also submitted to The identified HARQ process (if the operation has been performed before judging the priority of the uplink scheduling and the priority of other uplink scheduling, it is not performed here). If the MAC PDU is not obtained, the HARQ buffer area of the identified HARQ process is cleared, and optionally, the configured scheduling timer of the identified HARQ process (if running) is stopped.
  • the uplink scheduling is used for retransmission and one of the following conditions is met, the uplink scheduling is ignored, and the configured scheduling timer of the identified HARQ process (if running) is stopped: (1) If the uplink scheduling is added by CS-RNTI The HARQ buffer area of the HARQ process indicated by the scrambled PDCCH and identified is empty; (2) If the uplink scheduling is part of a group of uplink scheduling and no MAC PDU is obtained for this group of uplink scheduling; (3) If the uplink scheduling is A part of a group of uplink scheduling and the PUSCH duration of the uplink scheduling overlaps with the duration of another uplink scheduling PUSCH indicated by the PDCCH duration or random access response on this serving cell; (4) If the uplink scheduling PUSCH The duration overlaps with the PUSCH duration of other uplink schedules whose priority is not lower than (or higher than) the uplink schedule.
  • the condition for starting the configured scheduling timer of the identified HARQ process is: if the uplink scheduling corresponds to CS-RNTI, or the uplink scheduling is configured for uplink scheduling, or the uplink scheduling corresponds to C-RNTI and the identified HARQ process is configured When configuring uplink scheduling, if the configuration scheduling timer is configured, the configuration scheduling timer is started or restarted when the transmission is performed.
  • the enabling priority indicator (including the first or second enabling priority indicator) defined in the operation embodiment for uplink scheduling reception execution may also be applied to the operation embodiment performed by the HARQ entity.
  • 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 When 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 judged whether the received uplink scheduled PUSCH duration overlaps with other uplink scheduled PUSCH durations, and according to The judgment result executes the operation defined in the embodiment.
  • the enable priority indicator is not configured or the value of the flag is 0 or false or False or the second predefined value or the flag does not appear (or the value of the flag is 1 or true or TRUE or the value When the identifier appears), it is executed according to the embodiment in which the operation of judging whether the received uplink scheduled PUSCH duration overlaps with another uplink scheduled PUSCH duration is not performed (that is, the default condition is satisfied).
  • the second setting conditions (1-5) are the same.
  • Fig. 4 is a flowchart showing a method executed by a user equipment according to the third embodiment of the present invention.
  • the steps performed by the user equipment UE include: steps 001-009.
  • the HARQ entity performs the following operations:
  • step 001 identify the HARQ process corresponding to the uplink scheduling, and perform step 002 for each identified HARQ process (identify the HARQ process associated with this grant, and for each identified HARQ process).
  • step 002 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 inverted compared with the NDI value of the previous transmission of the transport block of the HARQ process (if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been received to the value in the previous process of this ARQ transmission of this TB Scheduling is indicated by the PDCCH scrambled by the C-RNTI and the HARQ buffer of the identified HARQ process is empty (if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty); or If the uplink scheduling is received from the random access response (if the uplink grant was received in a Random Access Response); or if the uplink scheduling received in the ra-ResponseWindow is indicated by the PDCCH scrambled by the C-RN
  • step 003 if there is a MAC PDU in the message 3 (Msg3) buffer area and the uplink scheduling is received from the random access response (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 message 3 (Msg3) buffer area and the uplink scheduling received in ra-ResponseWindow is indicated by the PDCCH scrambled by C-RNTI and this PDCCH successfully completes the random access process caused by beam error recovery (ifthere is a MAC PDU in the Msg3 buffer and the uplink grant was received on PDCCH for the C-RNTI in ra-ResponseWindow and this PDCCH successfully completed the Random Access procedure is already covered, then the procedure is already covered for At least one condition in ), otherwise (none of the conditions are satisfied), go to step 005.
  • the MAC PDU is obtained from the Msg3 buffer area. 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 the uplink scheduling is received (if the uplink grant size does not match with size of the obtained MAC PDU, and if the Random Access procedure) was successfully completed up receiving the uplink grant), indicating that the multiplexing and assembling entity includes the MAC subPDU (indicate to the Multiplexing and assembly entity to include MAC subPDU(s) from the obtained MAC PDU in subsequent uplink transmissions carrying MAC SDU from the obtained MAC PDU in the subsequent uplink transmission), obtain MAC PDU from the multiplexing and assembling entity for transmission. Go to step 006.
  • step 005 the MAC PDU is obtained from the multiplexing and assembly entity for transmission (if any) (obtain the MAC PDU to transmit from the multiplexing and assembly entity, ifany). Go to step 006.
  • step 006 if a MAC PDU for transmission (if a MAC PDU to transmit has been obtained) is obtained, perform the following operations (and end after performing the following operations):
  • the identified HARQ process is instructed to trigger a new transmission.
  • the uplink scheduled PUSCH duration does not overlap with other uplink scheduled PUSCH durations or the uplink scheduled PUSCH duration only overlaps with other lower priority uplink scheduled PUSCH durations (If the uplink grant Does not overlap with other uplink grant or if the uplink grant overlaps with other uplink grant with lower priority) or the uplink scheduling is indicated by the PDCCH scrambled by the C-RNTI and the priority of the uplink scheduling configuration that overlaps with the PUSCH duration is not high
  • the uplink scheduling the above judgment conditions in this operation are optional, for example, when the HARQ entity executes step 001 and subsequent steps for each uplink scheduling, it judges whether these conditions are met and when any of the conditions is met Perform subsequent operations), instruct the identified HARQ process to trigger a new transmission (instruct the identified HARQ process to trigger a new transmission) and/or submit the uplink scheduling and/or HARQ information of this transport block to the identified
  • the HARQ process is configured to configure uplink scheduling (if the uplink grant is addressed to C-RNTI, and the identified HARQ process is configured for a configured uplink grant), if the configured scheduling timer is configured, it will start or restart when transmission is performed Configure scheduling timer configuredGrantTimer(start or restart theconfiguredGrantTimer, if configured, for the corresponding HARQ process when the transmission is performed);
  • step 007 is executed.
  • step 007 the HARQ buffer area of the identified HARQ process is cleared.
  • the configuration scheduling timer is running, stop the configuration scheduling timer. End.
  • step 008 if the third setting condition is met, the uplink scheduling is ignored; if the third setting condition is not met, step 009 is executed.
  • the third setting condition may be at least one of the following:
  • the uplink scheduling is indicated by the PDCCH scrambled by CS-RNTI (the uplink grant received on PDCCH was addressed to CS-RNTI) and the HARQ buffer area of the identified HARQ process is empty;
  • the uplink scheduling is part of a group of uplink scheduling and the PUSCH of the uplink scheduling overlaps with another PUSCH of the uplink scheduling indicated by the PDCCH or random access response on this serving cell (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
  • the uplink scheduling is indicated by the PDCCH and/or the PUSCH duration of the uplink scheduling overlaps with the PUSCH duration of another uplink scheduling with higher priority.
  • step 008 also includes: if the uplink scheduling is ignored, if the uplink scheduling is indicated by the PDCCH scrambled by the CS-RNTI and/or if the configured scheduling timer corresponding to the identified HARQ process is running, stopping This configuration schedules the timer.
  • step 008 after ignoring the uplink scheduling, 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 is configured on the HARQ process ), the configuration scheduling timer is stopped.
  • step 008 further includes: if the uplink scheduling is indicated by the PDCCH scrambled by the CS-RNTI (the uplink grant received on PDCCH was addressed to CS-RNTI) and the HARQ buffer area of the identified HARQ process is empty, 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 is configured on the HARQ process), the configured scheduling timer is stopped.
  • step 008 further includes: if the uplink scheduling is indicated by the 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 identified HARQ process corresponds
  • the configured scheduling timer of is running (only executed when the configured uplink scheduling and/or configured scheduling timer is configured on the HARQ process), then the configured scheduling timer is stopped.
  • the uplink scheduling and the HARQ information (redundancy version) corresponding to the transport block are delivered to the identified HARQ process; the identified process triggers a retransmission; if the received uplink scheduling corresponds to CS-RNTI or received
  • the uplink scheduling is configured to configure the uplink scheduling or the received uplink scheduling corresponds to the C-RNTI and the identified HARQ process is configured with the configured uplink scheduling, if the configured scheduling timer is configured, the configuration scheduling timing is started or restarted when the transmission is performed ConfiguredGrantTimer.
  • Fig. 5 is a flowchart showing a method executed by a user equipment according to the fourth embodiment of the present invention.
  • the steps performed by the user equipment UE include: steps 101-113.
  • the HARQ entity performs the following operations:
  • step 101 the HARQ process corresponding to the uplink scheduling is identified, and step 102 is executed for each identified HARQ process.
  • 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 inverted compared with the NDI value of the previous transmission of the transport block of the HARQ process; or If the received uplink scheduling is indicated by the PDCCH scrambled by C-RNTI and the HARQ buffer of the identified HARQ process is empty; or if the uplink scheduling is received from a random access response; or if it is received in ra-ResponseWindow Uplink scheduling is indicated by the PDCCH scrambled by C-RNTI and this PDCCH successfully completes the random access process caused by beam error recovery; or if the uplink scheduling is part of a set of configured uplink scheduling and may be used for initial transmission and also If the uplink scheduling is not configured for this group to obtain the MAC PDU, step 103 is performed (at least one of the conditions is satisfied), otherwise (the conditions are not met), step 108 is performed.
  • step 103 if there is a MAC PDU in the message 3 (Msg3) buffer and the uplink scheduling is received from the random access response, or if there is a MAC PDU in the message 3 (Msg3) buffer and the uplink scheduling received in ra-ResponseWindow is If the PDCCH scrambled by C-RNTI indicates and this PDCCH successfully completes the random access process caused by beam error recovery, then perform step 104 (satisfy at least one of the conditions), otherwise (the conditions are not met) ), go to step 105.
  • the MAC PDU is obtained from the Msg3 buffer area. If the size of the uplink schedule does not match the size of the obtained MAC PDU and the random access process is successfully completed when the uplink schedule is received, the multiplexing and assembling entity is instructed to include the MAC PDU carried from the obtained MAC PDU in the subsequent uplink transmission. The MAC subPDU is obtained from the multiplexing and assembly entity for transmission. Go to step 106.
  • step 105 the MAC PDU is obtained from the multiplexing and assembly entity for transmission (if any). Go to step 106.
  • step 106 if a MAC PDU for transmission (if a MAC PDU to transmit has been obtained) is obtained, perform the following operations (and end after performing the following operations):
  • the identified HARQ process is instructed to trigger a new transmission.
  • the PUSCH duration of the uplink scheduling does not overlap with the PUSCH durations of other uplink scheduling or the PUSCH duration of the uplink scheduling only overlaps with the PUSCH durations of other uplink scheduling with lower priority or the uplink scheduling is
  • the priority of the configured uplink scheduling that is indicated by the PDCCH scrambled by the C-RNTI and overlaps with its PUSCH duration is not higher than the uplink scheduling (the above judgment conditions in this operation are optional, for example, the HARQ entity performs each uplink scheduling When scheduling step 101 and its subsequent steps, it is determined whether these conditions are met and subsequent operations are performed when any of these conditions are met), then the identified HARQ process is instructed to trigger a new transmission and/or the uplink scheduling and/or this transmission
  • the HARQ information of the block is delivered to the identified HARQ process; otherwise (optional), the uplink scheduling and/or the HARQ information of this transport block is delivered to the identified
  • the received uplink scheduling corresponds to CS-RNTI, or the received uplink scheduling is configured for uplink scheduling, or the received uplink scheduling corresponds to C-RNTI and the identified HARQ process is configured with configured uplink scheduling, then if configured To configure the scheduling timer, start or restart the configuredGrantTimer when the transmission is performed;
  • step 107 the HARQ buffer area of the identified HARQ process is cleared.
  • the configuration scheduling timer is running, stop the configuration scheduling timer. End.
  • step 108 if the received uplink schedule is indicated by the PDCCH scrambled by the C-RNTI and submitted to the same HARQ process (the HARQ process identified for the received uplink schedule) of this HARQ entity, another uplink schedule is performed by CS- RNTI scrambled PDCCH indication or configured uplink scheduling, or if the received uplink scheduling is configured with uplink scheduling and another uplink scheduling submitted to the same HARQ process of this HARQ entity is scrambled by CS-RNTI or C-RNTI If the PDCCH indicates or there is a MAC PDU in the HARQ buffer area of the identified HARQ process that has not yet been sent or is waiting for initial transmission, step 109 is executed; otherwise, step 112 is executed.
  • step 109 if the priority of the received configuration scheduling is higher (higher than the priority of the CG on the same HARQ process or the MAC PDU that has not been sent or waiting for the initial transmission, or is not higher than the CG or not yet on the same HARQ process The MAC PDU sent or waiting for the first transmission has a low priority), go to step 110; otherwise, go to step 111.
  • step 110 obtain a MAC PDU for transmission from the multiplexing and assembling entity; submit the MAC PDU, the uplink scheduling and the HARQ information of the transmission block to the identified HARQ process; indicate that the identified HARQ process triggers a new transmission; when executed
  • the configured scheduling timer corresponding to the identified HARQ process is started or restarted during transmission (only executed if the configured scheduling timer is configured for the configured uplink scheduling). End.
  • step 111 if the received uplink scheduling is indicated by the C-RNTI scrambled PDCCH, then the uplink scheduling is ignored. If the received uplink schedule is the configured uplink schedule and the previous uplink schedule of the same HARQ process (the HARQ process identified for the received uplink schedule) of this HARQ entity is indicated by the PDCCH scrambled by the CS-RNTI or Configure uplink scheduling, then submit the to-be-uplink scheduling and HARQ information (redundancy version) of this TB to the identified HARQ process; instruct the identified HARQ process to trigger retransmission, and start the configured scheduling timer of this HARQ process (if configured) . If the above conditions are not met, the uplink scheduling is ignored. End.
  • step 112 (same as step 008 in the third embodiment above), if the fourth setting condition is met, the uplink scheduling is ignored; if the third setting condition is not met, step 113 is executed.
  • the fourth setting condition may be at least one of the following:
  • the uplink scheduling is indicated by the PDCCH scrambled by CS-RNTI (the uplink grant received on PDCCH was addressed to CS-RNTI) and the HARQ buffer area of the identified HARQ process is empty;
  • the uplink scheduling is part of a group of uplink scheduling and the PUSCH of the uplink scheduling overlaps with another PUSCH of the uplink scheduling indicated by the PDCCH or random access response on this serving cell (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
  • the uplink scheduling is indicated by the PDCCH and/or the PUSCH duration of the uplink scheduling overlaps with the PUSCH duration of another uplink scheduling with higher priority.
  • step 112 if the uplink scheduling is ignored, if the uplink scheduling is indicated by the PDCCH scrambled by the CS-RNTI and/or if the configured scheduling timer corresponding to the identified HARQ process is running, stop the configuration Schedule timer.
  • step 112 if the uplink scheduling is indicated by the PDCCH scrambled by the CS-RNTI (the uplink grant received on PDCCH was addressed to CS-RNTI) and the HARQ buffer area of the identified HARQ process is empty, if it is identified
  • the configured scheduling timer corresponding to the HARQ process is running (only executed when the configured uplink scheduling and/or configured scheduling timer is configured on the HARQ process), then the configured scheduling timer is stopped.
  • step 112 if the uplink scheduling is indicated by the PDCCH and/or the PUSCH duration of the uplink scheduling overlaps with the PUSCH duration of another uplink scheduling with higher priority, if the identified HARQ process corresponds to the configuration
  • the scheduling timer is running (only executed when the uplink scheduling and/or scheduling timer is configured on the HARQ process), then the configured scheduling timer is stopped.
  • step 113 the uplink scheduling and the HARQ information (redundancy version) corresponding to the transport block are submitted to the identified HARQ process; instruct the identified process to trigger a retransmission; if The received uplink scheduling corresponds to CS-RNTI or the received uplink scheduling is configured for uplink scheduling or the received uplink scheduling corresponds to C-RNTI and the identified HARQ process is configured with configured uplink scheduling, then if the configured scheduling timer is configured, When the transmission is performed, the configured scheduling timer configuredGrantTimer is started or restarted.
  • each HARQ process supports one transmission block TB or two transmission blocks (in space division multiplexing MIMO, two transmission blocks are supported).
  • the HARQ entity generates/obtains a MAC PDU for a lower priority uplink scheduling (the PUSCH duration of the uplink scheduling overlaps the PUSCH duration of the higher priority uplink scheduling) and stores it in the buffer area If there is data to be sent in the lower priority uplink scheduling, it indicates that the multiplexing and assembly process will include a buffered data to indicate MAC CE or trigger low priority data when generating MAC PDUs for the higher priority uplink scheduling Instructions.
  • the buffered data indication is triggered and not cancelled, when the MAC entity is allocated uplink resources for new transmission, instruct the multiplexing and assembly process to generate a buffered data indication MAC CE, and cancel the triggered buffered data indication .
  • the lower priority uplink scheduling data to be sent can be determined by the HARQ entity through the priority obtained from the "process for determining the uplink scheduling priority", so the lower priority uplink scheduling data to be sent can also be described
  • the priority for low-priority uplink scheduling is not a value predefined for no data and/or no data and MAC CE transmission.
  • the priority of low-priority uplink scheduling is greater than 0.
  • the buffered data indicates that the MAC CE may indicate whether there is buffered data in the low-priority uplink scheduling where the PUSCH duration overlap occurs or whether there is buffered data in the buffer area of the HARQ process identified by the low-priority uplink scheduling.
  • each bit in the bitmap corresponds to a low-priority uplink scheduling where PUSCH duration overlap occurs.
  • the corresponding bit is set to 1 (or 0), otherwise set to 0 (or 1).
  • the configuration scheduling where the PUSCH duration overlaps will occur in the order of configuration scheduling identifiers from small to large (or from large to small).
  • the bits from left to right (or right to left) in the bitmap corresponds to the bits from left to right (or right to left) in the bitmap.
  • the 0th bit of the bitmap corresponds to the configuration scheduling with the smallest configuration scheduling identifier where the PUSCH duration overlaps, and so on. If the buffered data indicates that the MAC CE is included in the MAC PDU generated for configuration scheduling, the 0th bit of the bitmap corresponds to dynamic, the 1st bit corresponds to the configuration scheduling with the smallest configuration scheduling identifier where PUSCH duration overlap occurs, and so on.
  • the configuration scheduling identifier is configured by the base station for each configuration scheduling through RRC signaling/message, for example, included in the ConfiguredGrantConfig information element, and configured when configuring the corresponding configuration scheduling.
  • the buffered data indicates that the priority of MAC CE is lower than that of PHR MAC CE (including Single Entry PHR MAC CE and Multiple Entry PHR MAC CE) is greater than the priority of data from logical channels (except for data from UL-CCCH)
  • the following specifically describes an operational embodiment of the execution of the HARQ process of the user equipment UE when a DG/CG or CG/CG conflict occurs.
  • the HARQ entity 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 a trigger from the HARQ entity to trigger a new transmission or retransmission , The HARQ process performs at least one of the following operations:
  • scheduling refers to uplink scheduling.
  • Dynamic scheduling refers to uplink scheduling in which the C-RNTI or CS-RNTI of the MAC entity is received on the PDCCH for a certain serving cell (an uplink grant for a serving cell is received on the PDCCH for the MAC entity's C-RNTI or CS-RNTI (in other words, the uplink scheduling received on the PDCCH), if the dynamic scheduling is for the CS-RNTI of the MAC entity, then NDI is 1; configuring scheduling means configuring uplink scheduling (configured uplink grant).
  • the following describes an embodiment of the processing mode when multiple uplink scheduling is received in the process of multiplexing and assembling (also can be a logical channel priority process LCP).
  • the multiplexing and assembly process receives an uplink schedule whose PUSCH duration overlaps with other uplink scheduled PUSCH durations, and the priority of the uplink scheduling is higher, the multiplexing and assembly process has been If the lower priority uplink scheduling generates MAC PDU, the MAC control element CE (including the buffer status report BSR and the power headroom report PHR) that has been included in the MAC PDU generated for the lower priority uplink scheduling is included In the MAC PDU generated for the higher priority uplink scheduling (if it contains a BSR, the BSR must be recalculated and generated), if the MAC PDU generated by the lower priority uplink scheduling only contains MAC CE, then Include all MAC CEs in the MAC PDU generated for higher priority uplink scheduling (the MAC CE includes BSR, PHR, and configure scheduling confirmation MAC CE), and cancel the generated MAC PDU for the lower priority uplink scheduling MAC PDU (that is, clear the HARQ buffer area of the HARQ process corresponding to the low-pri
  • MAC PDU is generated for the uplink scheduling with higher priority and MAC CE (including BSR, PHR, configuration scheduling confirmation MAC CE, if it exists) includes In this MAC PDU. If the received multiple uplink schedules have the same priority, if dynamic scheduling is included, a MAC PDU is generated for dynamic scheduling and includes the MAC CE that needs to be sent.
  • FIG. 6 is used to describe a user equipment that can execute the method executed by the user equipment described in detail above in the present invention as a modified example.
  • Fig. 6 is a block diagram showing a user equipment UE related to the present invention.
  • 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, and the like.
  • the memory 602 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memories.
  • the memory 602 stores program instructions. When the instruction is executed by the processor 601, it can execute the above method executed by the user equipment described in detail in the present invention.
  • FIG. 7 is used to describe a base station that can execute the method executed by the base station described in detail above in the present invention as a modified example.
  • Fig. 7 is a block diagram showing a base station according to the present invention.
  • 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, and the like.
  • the memory 702 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memories.
  • the memory 702 stores program instructions. When the instruction is executed by the processor 701, it can execute the above method executed by the base station described in detail in the present invention.
  • the present invention proposes a method executed by the base station.
  • the base station sends the first enabling priority indicator and/or the second enabling priority indicator to the user equipment UE.
  • the UE performs the operations described in the above embodiments.
  • the computer-executable instructions or program running on the device according to the present invention may be a program that enables the 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 volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • Computer-executable instructions or programs for implementing the functions of the various embodiments of the present invention may be recorded on a computer-readable storage medium. Corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute these programs.
  • the so-called “computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium storing a program dynamically for a short period of time, or any other recording medium readable by a computer.
  • circuits for example, single-chip or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification can include general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (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 may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuit can be a digital circuit or an analog circuit. In the case of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present invention can also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the above-mentioned embodiment. Although various examples of the embodiment have been described, the present invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioning, office equipment, vending machines, and other household appliances.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

根据本发明，提出了一种由用户设备UE执行的方法，包括：接收针对媒体访问控制MAC实体的动态上行调度；针对接收到的所述动态上行调度，判断是否满足第一设定条件；如果满足所述第一设定条件，则将该上行动态调度递交给混合自动重传请求HARQ实体。

Description

用户设备、基站及其方法 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及用户设备、基站及其方法。
背景技术
2019年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#83次全会上批准了一个支持NR工业物联网的工作项目(参见非专利文献：RP-190728：New WID：Support of NR Industrial Internet of Things(IoT))。在工业应用场景中，用户设备(UE)需要同时处理来自不同应用或设备的数据流(traffic flows)，因此需要考虑用户设备内(intra-UE)发生上行/下行数据信道与控制信道发生冲突时优先级处理和/或复用，以及动态调度(grant)和配置调度之间以及两个或多个配置调度之间发生资源冲突的处理。据此，该工作项目的目的之一是在解决动态调度和配置调度之间以及两个或多个配置调度之间发生资源冲突方面进行增强，如果在媒体访问控制MAC(Medium Access Control)处理调度优先级，3GPP第二工作组(RAN2)需定义基于逻辑信道(LCH)优先级和逻辑信道优先级(LCP)限制的物理上行共享信道PUSCH(Physical Uplink Shared CHannel)调度优先级处理机制。
在2019年4月召开的3GPP RAN2#105bis次会议上达成：当配置多个配置上行调度CG(Configured Uplink Grant)或下行半静态调度SPS(Semi-Persistent Scheduling)时，为每个CG或SPS配置一个用于计算混合自动重传请求HARQ(Hybrid Automatic Repeat reQuest)进程号的偏移。该结论的目的在于将不同的配置上行调度(或下行SPS)映射到不同的HARQ进程，使得配置上行调度(或下行SPS)所关联或映射或使用的HARQ进程不同或没有重叠。在2019年5月召开的3GPP RAN2 #106次会议上达成：对于低优先级PUSCH的动态调度，UE将其对应的低优先级的MAC  PDU存储在HARQ缓存区中，使得gNB可以利用同一HARQ进程调度重传(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)；对于低优先级PUSCH的配置上行调度，a)UE将其对应的低优先级的MAC PDU存储在HARQ缓存区中，使得gNB可以调度重传，b)UE是否可以在随后的无线资源上进行重传是需要进一步讨论，例如采用随后关联到同一HARQ进程的无线资源(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 proces)；上述结论至少适用于MAC实体已经为低低优先级的动态调度或配置上行调度产生了MAC PDU的情况。
基于上述达成的结论，当较低优先级MAC PDU存储在HARQ缓存区中，此时有上行调度可用(可以是动态调度或配置调度)，并且此上行调度不能用来传输缓存区中的MAC PDU。此时，UE如何处理所述可用的上行调度是需要考虑的问题。图1给出了此问题的示例描述，在T1，不同HARQ进程的动态调度DG1和配置调度CG发生冲突，动态调度的优先级更高，为配置调度CG生成的MAC PDU存储在缓存区中。在T2，接收到动态调度DG2且DG2与配置调度CG具有相同的HARQ进程，此时，因为为CG产生的MAC PDU还存储在对应HARQ进程的缓存区中，当DG2的优先级比CG低时，是否为DG2产生MAC PDU来覆盖缓存区中的MAC PDU？此外，当UE具有多个可用的上行调度且这些上行调度之间存在PUSCH持续时间重叠时如何选择一个上行调度来发送数据是需要考虑的问题。
发明内容
为了解决上述问题中的至少一部分，本发明提供了一种用户设备、基站及其方法，能够通过设置使能优先级指示标识来解决不同HARQ进程DG/CG PUSCH冲突、不同HARQ进程CG/CG冲突和相同HARQ进程上行调度/MAC PDU冲突。
为了实现上述目的，根据本发明，提出了一种由用户设备UE执行的方法，包括：接收针对媒体访问控制MAC实体的动态上行调度；针对接收到的所述动态上行调度，判断是否满足第一设定条件；如果满足所述第一设定条件，则将该上行动态调度递交给混合自动重传请求HARQ实体。
优选地，所述第一设定条件包括以下条件中的任一个或其任意组合：是否配置了第一使能优先级指示标识；以及接收到的动态上行调度的物理上行共享信道PUSCH持续时间是否与其他上行调度的PUSCH持续时间重叠。
优选地，所述第一使能优先级指示标识表示在不同HARQ进程上发生了上行调度的物理上行共享信道PUSCH冲突时，支持发生了冲突的上行调度之间的优先级的比较。
优选地，所述第一设定条件包括以下条件中的任一个或其任意组合：是否配置了第二使能优先级指示标识；对应的配置上行调度定时器是否正在运行；接收到的动态上行调度的优先级是否比同一HARQ进程的缓存区中保存的MAC PDU即MAC协议数据单元的优先级更高；以及接收到的动态上行调度的优先级是否比前一个上行调度的优先级更高。
优选地，所述第二使能优先级指示标识表示在相同HARQ进程上发生了上行调度和MAC PDU即MAC协议数据单元的冲突时，支持发生了冲突的上行调度和MAC PDU之间的优先级的比较。
另外，根据本发明，提出了一种由用户设备UE执行的方法，包括：针对每个服务小区，接收针对媒体访问控制MAC实体的配置上行调度；针对接收到的所述配置上行调度，判断是否满足第二设定条件；如果满足所述第二设定条件，则将该配置上行调度递交给混合自动重传请求HARQ实体。
优选地，所述第二设定条件包括以下条件中的任一个或其任意组合：是否配置了第一使能优先级指示标识；以及接收到的配置上行调度的物理上行共享信道PUSCH持续时间是否与其他上行调度的PUSCH持续时间重叠。
优选地，所述第二设定条件包括以下条件中的任一个或其任意组合：是否配置了第二使能优先级指示标识；对应的配置上行调度定时器是否正 在运行；以及该配置上行调度的优先级是否比对应HARQ缓存区保存的MAC PDU即MAC协议数据单元的优先级更高。
优选地，所述动态上行调度的优先级在对应的下行控制信息DCI中指示，所述配置上行调度的优先级由基站通过无线资源控制RRC信令配置。
此外，根据本发明，提出了一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行上述的方法。
另外，根据本发明，提出了一种由基站执行的方法，包括：向用户设备UE发送第一使能优先级指示标识和/或第二使能优先级指示标识，当接收到所述第一使能优先级指示标识和/或所述第二使能优先级指示标识时，所述UE执行上述的方法。
此外，根据本发明，提出了一种基站，包括：处理器；以及存储器，存储有指令，其中，所述指令在由所述处理器运行时执行上述的方法。
根据如上所述的本发明，能够通过设置使能优先级指示标识来解决不同HARQ进程DG/CG PUSCH冲突、不同HARQ进程CG/CG冲突和相同HARQ进程上行调度/MAC PDU冲突。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1示出了上行调度冲突的示意图。
图2是示出了根据本发明的实施例一的由用户设备执行的方法的流程图。
图3是示出了根据本发明的实施例二的由用户设备执行的方法的流程图。
图4是示出了根据本发明的实施例三的由用户设备执行的方法的流程图。
图5是示出了根据本发明的实施例四的由用户设备执行的方法的流程图。
图6是示意性示出本发明所涉及的用户设备的框图。
图7是示意性示出本发明所涉及的基站的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，所述术语与3GPP协议当前最新版本中采用的术语相同，现摘录如下。
RRC：Radio Resource Control，无线资源控制。
MAC：Medium Access Control，媒体访问控制。
PDCCH：Physical Downlink Control Channel，物理下行控制信道。
PUSCH：Physical Uplink Shared Channel，物理上行共享信道。
SDU：Service Data Unit，服务数据单元。
PDU：Protocol Data Unit，协议数据单元。
CG：Configured uplink Grant，配置调度或配置上行调度。
DG：Dynamic Grant，动态调度，是指在PDCCH上动态接收到的上行调度。换言之，PDCCH上接收到的为MAC实体的C-RNTI或TC-RNTI(Temporary C-RNTI)的上行调度或者PDCCH上接收到的为MAC实体的CS-RNTI的上行调度(这个上行调度用于配置上行调度上传输的MAC PDU的重传，其中接收到的NDI值为1认为NDI不翻转)。所述PDCCH上接收到的为MAC实体的C-RNTI或TC-RNTI(Temporary C-RNTI)或CS-RNTI的上行调度是由MAC实体的C-RNTI或TC-RNTI或CS-RNTI加扰的PDCCH指示的上行调度，这两种表述可互换使用。
HARQ信息：HARQ information，DL-SCH或UL-SCH传输的HARQ信息由新数据指示(New Data Indicator，NDI)、传输块大小(Transport Block size，TBS)、冗余版本(Redundancy Version，RV)以及HARQ进程号(HARQ process ID)组成。
CS-RNTI：Configured Scheduling RNTI，配置调度RNTI。
ra-ResponseWindow：随机接入响应窗，UE在随机接入响应窗内接收随机接入响应。
本公开中，在一个服务小区上，某个HARQ进程上的动态调度DG的PUSCH持续时间(duration)与另一个HARQ进程上的配置调度CG的PUSCH持续时间重叠(overlap)称为不同HARQ进程DG/CG PUSCH冲突或不同HARQ进程DG/CG冲突。在一个服务小区上，某个HARQ进程上的配置调度CG的PUSCH持续时间与另一个HARQ进程上的配置调度CG的PUSCH持续时间重叠称为不同HARQ进程CG/CG PUSCH冲突或不同HARQ进程CG/CG冲突。某个HARQ进程上的动态调度DG的PUSCH持续时间与该HARQ进程上的配置调度CG的PUSCH持续时间重叠称为相同HARQ进程DG/CG冲突。某个HARQ进程上的上行调度与该HARQ进程的HARQ缓存区存储的尚未发送(或已发送但尚未确认发送成功)的MAC PDU间所发生的冲突(这种冲突主要是使用HARQ缓存区的冲突，因为每个HARQ进程关联一个HARQ缓存区，如果为该上行调度生成MAC PDU，那么存储在HARQ缓存区中的已有MAC PDU将被覆盖/破坏)称为相同HARQ进程上行调度/MAC PDU冲突。不同HARQ进程DG/CG PUSCH冲突包括一个DG与多个不同HARQ进程上的CG间PUSCH持续时间冲突的情况。同样的，不同HARQ进程CG/CG PUSCH冲突也包含多个CG间PUSCH持续时间冲突的情况。如未特别说明，本公开实施例所述DG/CG或CG/CG冲突包括以上各类冲突，且所述冲突是指发生冲突的DG和CG以及发生冲突的两个或多个CG均在同一个服务小区上。在本公开中，不同的上行调度发生PUSCH重叠是指不同的上行调度在时域上重叠。
当对应HARQ进程的配置调度定时器到期或在一个MAC PDU发送完成后接收到NDI翻转的动态调度时，UE或MAC实体认为这个MAC PDU发送成功。
用户设备UE接收到上行调度(DG或CG)(可由UE中的上行调度接收执行)，且该上行调度与其他上行调度(CG或DG)发生不同HARQ进程DG/CG PUSCH冲突(基站为UE配置了CG)，则判断DG与CG的优先级并根据判断结果执行相应的操作(可由UE中的上行调度接收执行或HARQ实体执行)。具体描述如下：
在一个实施例中，DG和/或CG用于新传(例如，对于DG，当NDI翻转时用于新传，对于CG，当对应的配置调度定时器configuredGrantTimer 未运行时用于新传)，当发生不同HARQ进程DG/CG PUSCH冲突时，如果DG的优先级较高，则UE不为CG生成MAC PDU，忽略CG。当DG的优先级较低时，如果DG用于新传(即HARQ实体需要获取MAC PDU)，为DG生成/获取MAC PDU(可由HARQ实体执行)并存储在对应HARQ进程的缓存区中(可由对应的HARQ进程执行)；如果DG用于重传，重启配置调度定时器configuredGrantTimer(可由HARQ实体执行)。
下面具体描述在发生DG/CG或CG/CG冲突时用户设备UE的上行调度接收(UL Grant reception)执行的操作的实施例。
对于发生不同HARQ进程DG/CG PUSCH冲突的场景，UE的上行调度接收在PDCCH上接收到为MAC实体的C-RNTI的上行调度，如果配置了第一使能优先级指示标识且/或所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或Release或所述标识不出现)，如果该上行调度的PUSCH持续时间不与其他上行调度的PUSCH的持续时间重叠或者仅与优先级低于或不高于该上行调度的其他上行调度(例如CG)的PUSCH的持续时间重叠，则将该上行调度和/或相关的HARQ信息指示给HARQ实体；可选的，如果前一个递交给HARQ实体的同一HARQ进程(就是接收到的上行调度对应的HARQ进程)的上行调度是配置上行调度或者是为MAC实体的CS-RNTI的上行调度时，则认为对应HARQ进程的NDI翻转而不管NDI的值(consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI)。否则(即如果没有配置第一使能优先级指示标识或所述标识的取值为0或假或False或release或所述标识不出现(或者所述标识的取值为1或真或TRUE或setup或所述标识出现))，将该上行调度和/或相关的HARQ信息指示给HARQ实体；可选的，如果前一个递交给该HARQ实体的同一HARQ进程(就是接收到的上行调度对应的HARQ进程)的上行调度是配置上行调度或者是为MAC实体的CS-RNTI的上行调度时，则认为对应HARQ进程的NDI翻转而不管NDI的值。需要说明的是，判断条件“前一个递交给该HARQ实体的同一HARQ进程的上行调度是否是配置上行调度或者是为MAC实体的CS-RNTI的上行调度”可以独立于判断条件是否配置了第一使能优先级指示标志，即，对于接收 到的上行调度，只要满足前一个递交给HARQ实体的同一HARQ进程的上行调度是配置上行调度或者是为MAC实体的CS-RNTI的上行调度，则认为对应HARQ进程的NDI翻转。
在发生不同HARQ进程DG/CG或CG/CG PUSCH冲突的场景中，对于每个服务小区的每个配置调度(被配置且被激活)，如果没有配置第一使能优先级指示标识或者所述标识的取值为0或假或False或Release或第二预定义的值或所述标识不出现(或者所述标识的取值为1或真或TRUE或setup或所述标识出现)(这个条件是可选的)，且如果该配置调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠，如果还满足该配置调度对应的HARQ进程的配置调度定时器未运行(这个条件是可选的)(在这三个条件都需要执行或需要其中任意两个的情况下，它们的执行顺序包括但不限于上述列出的顺序，可以任意交换它们的顺序形成新的实施例)，则将该配置调度和/或相关的HARQ信息指示给HARQ实体；可选的，还认为对应HARQ进程的NDI翻转。如果配置了第一使能优先级指示标识且/或所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或Release或所述标识不出现)(这个条件是可选的)，且如果该配置调度的PUSCH持续时间仅与优先级低于(或不高于)该配置调度的其他上行调度的PUSCH持续时间重叠或者该配置调度的PUSCH持续时间不与其他上行调度的PUSCH的持续时间重叠，如果还满足对应的HARQ进程的配置调度定时器未运行(这个条件是可选的)(在这三个条件都需要执行或需要其中任意两个的情况下，它们的执行顺序包括但不限于上述列出的顺序，可以任意交换它们的顺序形成新的实施例)，则将该配置调度和/或相关的HARQ信息指示给HARQ实体，可选的，还认为对应HARQ进程的NDI翻转。
可选的，如果对应的HARQ进程的配置调度定时器正在运行，则还需要判断该配置调度的优先级是否比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高，如果该配置调度的优先级比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高，则将该配置调度和/或相关的HARQ信息指示给HARQ实体，可选的，还认为对应HARQ进程的NDI翻转。(应用于支持相同HARQ进程CG/MAC PDU冲突的情况)
可选的，如果对应的HARQ进程的配置调度定时器正在运行，则还需要判断是否配置了第二使能优先级指示标识和判断该配置调度的优先级是否比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高，如果配置了第二使能优先级指示标识且/或所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)且该配置调度的优先级比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高，则将该配置调度和/或相关的HARQ信息指示给HARQ实体，可选的，还认为对应HARQ进程的NDI翻转。(应用于支持相同HARQ进程CG/MAC PDU冲突的情况)
需要说明的是，本公开所述其他上行调度包括在PDCCH上接收到的上行调度和/或其他配置调度和/或随机接入响应中的上行调度。在本公开实施例中，某上行调度的PUSCH持续时间仅与优先级低于或不高于该上行调度的其他上行调度的PUSCH的持续时间重叠是指该上行调度的PUSCH持续时间不与优先级不低于或高于该上行调度的其他上行调度的PUSCH的持续时间重叠。
在发生相同HARQ进程DG/MAC PDU冲突的场景中，UE的上行调度接收在PDCCH上接收到为MAC实体的C-RNTI的上行调度，如果配置了第二使能优先级指示标识且所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)，如果该上行调度对应的HARQ进程的配置调度定时器未运行，则将该上行调度和/或相关的HARQ信息指示给HARQ实体；可选的，如果前一个递交给HARQ实体的同一HARQ进程(就是接收到的上行调度对应的HARQ进程)的上行调度是配置上行调度或者是为MAC实体的CS-RNTI的上行调度时，则认为对应HARQ进程的NDI翻转而不管NDI的值。如果该上行调度对应的HARQ进程的配置调度定时器正在运行且如果前一个递交给HARQ实体的同一HARQ进程(就是接收到的上行调度对应的HARQ进程)的上行调度是配置上行调度或者是为MAC实体的CS-RNTI的上行调度且如果该接收到的上行调度的优先级比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高，则将该接收到的上行调度和/或相关的HARQ信息指示给HARQ实体， 可选的，认为对应HARQ进程的NDI翻转。
需要说明的是，本公开中，第一使能优先级指示标识应用于不同HARQ进程上DG/CG或CG/CG PUSCH冲突，第二使能优先级指示标识应用于相同HARQ进程DG/CG或上行调度/MAC PDU冲突。配置了使能优先级指示标识(包括第一使能优先级指示标识和第二使能优先级指示标识)且/或所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或第二预定义的值或所述标识不出现)表示在发生不同HARQ进程DG/CG或CG/CG PUSCH冲突或者相同HARQ进程DG/CG或上行调度/MAC PDU冲突时，系统或UE支持比较发生冲突的上行调度和/或MAC PDU的优先级，并根据比较结果执行实施例中定义的操作。没有配置第一使能优先级指示标识或所述标识的取值为0或假或False或release或第二预定义的值或所述标识不出现(或者所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现)是指系统或LIE不支持使能优先级指示标识或者当发生不同HARQ进程DG/CG PUSCH冲突时，总是认为DG的优先级更高，即认为对应HARQ进程的NDI翻转并将DG及其HARQ信息递交给HARQ实体。此外，使能优先级指示标识的取值不限于所列举的取值，也可以是其他预先规定的取值，例如使能和/或去使能。如果系统或UE不支持使能优先级指示标识，则只判断其他条件是否满足而忽略关于是否配置了使能优先级指示标识的判断。第一使能优先级指示标识和第二使能优先级指示标识可以合并为一个指示标识(记为，使能优先级指示标识)，相应的，本公开实施例中第一使能优先级指示标识和第二使能优先级指示标识都替换为使能优先级指示标识。
在3GPP TS38.321最新发布的版本15(TS38.321-f50)中，当发生DG/CG冲突时总是认为DG的优先级高于CG，DG总是覆盖CG，利用DG传输数据而忽略CG。换言之，在接收到DG时，总是将DG递交给HARQ实体，HARQ实体为DG构建MAC PDU(对于新传)或指示HARQ进程进行重传；在接收到CG时，如果CG的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠且对应HARQ进程的配置调度定时器未运行，才将该CG递交给HARQ实体。在本公开中，通过引入使能优先级指示标识(包 括第一和/或第二使能优先级指示标识)来指示UE处理不同HARQ进程DG/CG PUSCH持续时间冲突和/或不同HARQ进程CG/CG PUSCH持续时间冲突和/或相同HARQ进程DG/CG冲突和/或相同HARQ进程上行调度/MAC PDU冲突(指示在发生冲突时UE进行优先级比较)，使得优先级较高的CG可以覆盖优先级较低的DG(或其他CG)或采用优先级较高的上行调度传输数据或将优先级较高的上行调度递交给HARQ实体或为优先级较高的上行调度生成/获取MAC PDU或忽略优先级较低的DG。所述使能优先级指示标识(包括第一和/或第二使能优先级指示标识)是基站预先通过RRC信令/消息为用户设备UE配置的(例如，在为UE配置配置调度时配置使能优先级指示标识，使能优先级指示标识可以包含在用于配置上行带宽片段BWP的UE特定参数的信元BWP-UplinkDedicated中或者包含在系统信息中)。所述标识可用于指示当发生DG/CG冲突时，是否采用优先级较高的CG而忽略优先级较低的DG或者当接收到优先级较低的DG时是否递交给HARQ实体或是否生成/获取MAC PDU或是否执行重传或者是否处理优先级较低的DG或者是否将CG递交给HARQ实体；或者用于指示当发生CG/CG冲突时，是否采用优先级较高的CG而忽略优先级较低的CG或者当接收到优先级较低的CG时是否递交给HARQ实体或是否生成/获取MAC PDU。在DG和CG冲突发生在同一HARQ进程时，将较高优先级的上行调度递交给HARQ实体，HARQ实体为其产生MAC PDU，这将导致优先级较低的CG被忽略或者对应HARQ进程中保存的为较低优先级上行调度生成的MAC PDU(这个MAC PDU可以是尚未发送，或者已发送但尚未被确认正确接收(例如对应的配置调度定时器正在运行))将被清空(flush)或被为较高优先级上行调度生成的MAC PDU覆盖。所述第一和/或第二使能优先级指示标识可以包含在ConfiguredGrantConfig信元中，所述ConfiguredGrantConfig信元用于配置没有动态调度时根据两种可能机制的上行传输(the IE ConfiguredGrantConfig is used to configure uplink transmission without dynamic grant according to two possible schemes)；实际的上行调度可以是通过RRC配置(type 1)或由PDCCH提供(地址为CS-RNTI)(type 2)。当所述第一和/或第二使能优先级指示标识的取值为1或真或TRUE或setup或所述标识出现时，采用优先级较高的上行调度传输数据或将优先级较高的上行调度递交给HARQ实体或为优先级较高的上行 调度构建MAC PDU；当所述使能优先级指示标识的取值为0或假或False或release或所述标识不出现时，总是认为DG的优先级最高或DG的优先级比CG高或上行调度的优先级比对应HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级高。反之亦然。
下面通过具体的实施例描述冲突的处理过程。
实施例一
图2是示出了根据本发明的实施例一的由用户设备执行的方法的流程图。
如图2所示，在本发明的实施例一中，用户设备UE执行的步骤包括：步骤S201、步骤S203和步骤S205。
在步骤S201，用户设备UE的上行调度接收在PDCCH上接收到为MAC实体的C-RNTI的上行调度(动态上行调度)。
在步骤S203，针对接收到的动态上行调度，判断是否满足以下所述的第一设定条件。
在步骤S205，当前一个递交给HARQ实体的同一HARQ进程(就是接收到的上行调度对应的HARQ进程)的上行调度是配置上行调度或者是为MAC实体的CS-RNTI的上行调度时，如果满足第一设定条件，则认为对应HARQ进程的NDI翻转而不管NDI的值，可选地，还将该上行动态调度递交给HARQ实体。所述第一设定条件可以是以下任意一项或其任意组合：
1)用户设备被配置了第一使能优先级指示标识且/或所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)；并且如果接收到的上行调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠或不与其他优先级较高的上行调度的PUSCH持续时间重叠或者仅与优先级低于或不高于该上行调度的其他上行调度的PUSCH持续时间重叠；并且接收到的上行调度的优先级比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高(这个条件是可选的)；并且该HARQ进程的配置调度定时器正在运行(这个条件是可选的)。
2)用户设备被配置了第一使能优先级指示标识且/或所述标识的取值为 1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)；并且如果接收到的上行调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠或不与其他优先级较高的上行调度的PUSCH持续时间重叠或者仅与优先级低于或不高于该上行调度的其他上行调度的PUSCH持续时间重叠；并且该HARQ进程的配置调度定时器未运行(这个条件是可选)。
3)如果接收到的上行调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠或不与其他优先级较高的上行调度的PUSCH持续时间重叠或者仅与优先级低于或不高于该上行调度的其他上行调度的PUSCH持续时间重叠；并且接收到的上行调度的优先级比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高(这个条件是可选的)；并且该HARQ进程的配置调度定时器正在运行(这个条件是可选)。
4)如果接收到的上行调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠或不与其他优先级较高的上行调度的PUSCH持续时间重叠或者仅与优先级低于或不高于该上行调度的其他上行调度的PUSCH持续时间重叠；并且该HARQ进程的配置调度定时器未运行(这个条件是可选)。
5)用户设备被配置了第二使能优先级指示标识且/或所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)，并且该HARQ进程对应的配置调度定时器正在运行(这个条件是可选)，并且接收到的上行调度的优先级比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高。
5)接收到的上行调度的优先级比对应的HARQ进程的缓存区中保存的(或保存且尚未发送)MAC PDU的优先级更高；并且该HARQ进程的配置调度定时器正在运行(这个条件是可选)。
6)接收到的上行调度比前一个上行调度优先级更高(或接收到的上行调度比前一个生成了MAC PDU但未发送的上行调度的优先级更高，或接收到的上行调度比前一个生成了MAC PDU但被忽略的上行调到的优先级更高)；并且该HARQ进程对应的配置调度定时器正在运行(这个条件是可选)。
7)该接收到的上行调度对应的HARQ进程对应的配置调度定时器未运行；
8)如果没有配置第一使能优先级指示标识或所述标识的取值为0或假或False或release或第二预定义的值或所述标识不出现(或者所述标识的取值为1或真或TRUE或setup或所述标识出现)，可选地，并且如果接收到的上行调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠或不与其他优先级较高的上行调度的PUSCH持续时间重叠或者仅与优先级低于或不高于该上行调度的其他上行调度的PUSCH持续时间重叠。
在上述第一设定条件(1-8)中，所有的条件可以分为两类，一类用于处理不同HARQ进程上DG/CG PUSCH持续时间冲突，这类条件包括以下中的任一个或其任意组合：是否配置了第一使能优先级指示标识、接收到的上行调度的PUSCH持续时间是否与其他上行调度的PUSCH持续时间重叠。另一类条件用于处理相同HARQ进程DG/CG或上行调度/MAC PDU冲突，这类条件包括以下中的任一个或其任意组合：是否配置了第二使能优先级指示标识、对应的配置调度定时器是否正在运行、接收到的上行调度的优先级是否比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高、接收到的上行调度是否比前一个上行调度优先级更高。这两类条件分别只有在系统或UE支持处理对应类型的冲突时才需要，比如，如果系统或UE不支持处理相同HARQ进程DG/CG或上行调度/MAC PDU冲突(换言之，总认为接收到的上行调度总是优先级更高，为该上行调度生成的MAC PDU将覆盖当前HARQ缓存区保存的MAC PDU)，则第一设定条件中不包括用于处理相同HARQ进程DG/CG或上行调度/MAC PDU冲突的条件。此外，本公开所述接收到的上行调度的优先级比该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级更高可以替换为所述接收到的上行调度的优先级不低于该HARQ进程缓存区中保存的(或保存且尚未发送的)MAC PDU的优先级。此外，上述条件(1-8)中的每一项都含有多个判定条件(条件(7)除外)，在每一项中这些判定条件的执行顺序包括但不限于上述列出的顺序，也可以交换这些判断条件的顺序形成新的实施例。
更进一步的，用户设备UE的上行调度接收在PDCCH上接收到为MAC实体的C-RNTI的上行调度，并且满足第一设定条件，则还可以执行以下操 作至少一项：
1)将所述接收到的上行调度和相关的HARQ信息递交给HARQ实体(deliver the uplink grant and the associated HARQ information to the HARQ entity)。
2)如果对应的HARQ进程配置了配置调度定时器，启动或重启对应的HARQ进程的配置调度定时器(start or restart the configuredGrantTimer for the correponding HARQ process，if configured)。
可选的，用户设备UE的上行调度接收在PDCCH上接收到为MAC实体的C-RNTI的上行调度并且不满足第一设定条件，则执行以下操作至少一项：
1)如果前一个递交给HARQ实体的同一HARQ进程的上行调度是为MAC实体的C-RNTI的上行调度，将所述接收到的上行调度和相关的HARQ信息递交给HARQ实体(deliver the uplink grant and the associated HARQ information to the HARQ entity)；
2)如果对应的HARQ进程是为配置调度配置的HARQ进行并且配置了配置调度定时器，则启动或重启对应HARQ进程的配置调度定时器；
3)忽略接收到的上行调度。
在另一个实施例中，用户设备UE的上行调度接收在PDCCH上接收到为MAC实体的C-RNTI的上行调度，如果前一个递交给HARQ实体的同一HARQ进程(就是接收到的上行调度对应的HARQ进程)的上行调度是配置上行调度或者是为MAC实体的CS-RNTI的上行调度，则认为对应HARQ进程的NDI翻转而不管NDI的值(consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI)。如果满足前述第一设定条件，则可以执行前述满足第一设定条件时可以执行的其他操作。
在本公开实施例中，HARQ进程的缓存区中保存且尚未发送的MAC PDU是指HARQ进程缓存区不为空且其中存储的MAC PDU尚未发送或HARQ进程的缓存区中包含尚未发送的MAC PDU。当对应不同HARQ进程的DG与CG之间或CG与CG间发生了冲突，HARQ实体为优先级较低 的上行调度生成了MAC PDU并存储在缓存区中，但由于对应的上行调度优先级较低被忽略而没有利用该上行调度发送所述MAC PDU，所述MAC PDU就是指尚未发送的MAC PDU，也可称为等待初传的MAC PDU。
实施例二
图3是示出了根据本发明的实施例二的由用户设备执行的方法的流程图。
如图3所示，在本发明的实施例二中，用户设备UE执行的步骤包括：步骤S301、步骤S303和步骤S305。
在实施例二中，在步骤S301，对于每个服务小区，接收针对MAC实体的配置上行调度(MAC实体可以执行以下操作)，
在步骤S303，针对接收到的配置上行调度，判断是否满足第二设定条件。
在步骤S305，如果满足第二设定条件，则执行以下操作中的一项或多项(例如，将该配置上行调度递交给HARQ实体)：
1)设置HARQ进程号(HARQ process ID)为这个配置上行调度PUSCH持续时间对应的HARQ进程号；
2)如果对应HARQ进程的配置调度定时器未运行；或者，对应HARQ进程的缓存区为空或对应HARQ进程的配置调度定时器正在运行但HARQ进程的缓存区为空(这个条件是可选的)，则认为对应HARQ进程的NDI翻转，和/或将配置上行调度及其相关的HARQ信息递交给HARQ实体(可选的)。可选的，如果对应HARQ进程的配置调度定时器正在运行，且HARQ缓存区存在尚未发送的MAC PDU(例如，该MAC PDU是为前一个优先级较低的配置上行调度生成的)，则认为对应HARQ进程的NDI没有翻转。
3)将配置上行调度及其相关的HARQ信息递交给HARQ实体(如果2)中执行了此操作，则此处不再执行)。
4)启动对应HARQ进程的配置调度定时器(如果配置了配置调度定时器才执行此操作)。
可选的，如果不满足第二设定条件，忽略该配置上行调度或不将该配置上行调度递交给HARQ实体。
具体的，所述第二设定条件可为以任意一项或其任意组合：
1)UE被配置了第一使能优先级指示标识且所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)；并且对应HARQ进程的配置调度定时器未运行(可选的)。
2)UE被配置了第一使能优先级指示标识且所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)；并且(或者)配置上行调度的PUSCH持续时间与同一服务小区的其他上行调度的PUSCH持续时间重叠但该配置上行调度优先级较高或者该配置上行调度不与同一服务小区的其他上行调度的PUSCH持续时间重叠或者配置上行调度的PUSCH持续时间仅与优先级低于(或不高于)该配置上行调度的其他上行调度的PUSCH持续时间重叠；并且对应的HARQ进程的配置调度定时正在运行但该配置调度优先级更高(与缓存区中的MAC PDU的优先级进行比较)(可选)或该配置上行调度对应的HARQ进程的配置调度定时器未运行。
3)UE没有被配置第一使能优先级指示标识或所述标识的取值为0或假或False或release或第二预定义的值或所述标识不出现(或者所述标识的取值为1或真或TRUE或setup或所述标识出现)，并且/或者配置上行调度的PUSCH持续时间与PDCCH上接收到的同一服务小区的上行调度的PUSCH持续时间或同一服务小区上的其他配置上行调度的PUSCH持续时间或随机接入响应中的上行调度的PUSCH持续时间不重叠；并且对应HARQ进程的配置调度定时器未运行。可选的，对应HARQ进程的配置调度定时器正在运行，如果被配置了第二使能优先级指示标识或所述标识的取值为0或假或False或release或第二预定义的值或所述标识不出现(或者所述标识的取值为1或真或TRUE或setup或所述标识出现)且该配置调度优先级更高(与缓存区中的MAC PDU的优先级进行比较)。
4)配置上行调度的PUSCH持续时间与PDCCH上接收到的同一服务小区的上行调度的PUSCH持续时间重叠或与同一服务小区上的其他配置上行调度的PUSCH持续时间重叠，但该配置上行调度的优先级更高；或者配置上行调度的PUSCH持续时间不与随机接入响应中的上行调度的PUSCH持续时间重叠但与PDCCH上接收到的同一服务小区的上行调度或同一服务小区的其他配置上行调度的PUSCH持续时间重叠但该配置上行 调度的优先级更高。
5)UE被配置了第二使能优先级指示标识且所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)；并且对应的HARQ进程的配置调度定时正在运行(可选)但该配置调度优先级更高(与缓存区中的MAC PDU的优先级进行比较)或该配置上行调度对应的HARQ进程的配置调度定时器未运行。
可选的，在上述第二设定条件(1-5)中，如果接收到或可用的配置上行调度的PUSCH持续时间与随机接入响应中的上行调度的PUSCH持续时间重叠，则忽略该配置上行调度或不将该配置上行调度递交给HARQ实体(即总认为随机接入响应中的上行调度优先级最高，这也可应用于本公开其他实施例)。
在上述第二设定条件(1-5)中，所有的条件可以分为两类，一类用于处理不同HARQ进程上DG/CG或CG/CG PUSCH持续时间冲突，这类条件包括以下中的任一个或其任意组合：是否配置了第一使能优先级指示标识、接收到的配置上行调度的PUSCH持续时间是否与其他上行调度(例如另一配置上行调度或DG或随机接入响应的上行调度)的PUSCH持续时间重叠。另一类条件用于处理相同HARQ进程配置上行调度/MAC PDU冲突，这类条件包括以下中的任一个或其任意组合：是否配置了第二使能优先级指示标识、对应的配置调度定时器正在运行但该配置调度优先级更高(与缓存区中的MAC PDU的优先级进行比较)。这两类条件只有在系统或UE支持处理对应类型的冲突时才需要，比如，如果系统或UE不支持处理相同HARQ进程配置上行调度/MAC PDU冲突(换言之，如果对应的配置调度定时器正在运行，则不将该配置上行调度递交给HARQ实体)，则第一设定条件中不包括用于处理相同HARQ进程配置上行调度/MAC PDU冲突的条件。此外，如果系统或UE不支持使能优先级指示标识(包括第一使能优先级指示标识和第二使能优先级指示标识)，则上述第二设定条件(1-5)中关于是否配置了使能优先级指示标识的判断都可以删除。此外，上述条件(1-5)中的对于包含多个判定条件的项，这些判定条件的执行顺序包括但不限于上述列出的顺序，可以交换这些判断条件的顺序形成新的实施例。
本公开实施例中所述为MAC实体的C-RNTI或CS-RNTI或TC-RNTI的上行调度或者在PDCCH上接收到为MAC实体的C-RNTI或CS-RNTI或TC-RNTI的上行调度是指由C-RNTI或CS-RNTI或TC-RNTI加扰的PDCCH指示的上行调度。
本公开实施例中，动态调度的优先级可以在其对应的下行控制信息DCI中指示，配置调度的优先级可由基站通过RRC信令/消息配置或者在用于激活该配置调度的下行控制信息DCI中指示，也可以是这个上行调度可发送或可复用或将要复用或已复用(由复用和组装过程根据逻辑信道优先级LCP过程执行)的数据对应的逻辑信道的最高优先级(即所包含的数据对应的优先级最高的那个逻辑信道的优先级)或将要为这个上行调度生成的MAC PDU中包含的数据对应的优先级最高的逻辑信道的优先级。MAC PDU的优先级是指MAC PDU包含的数据对应的优先级最高的逻辑信道的优先级或该MAC PDU对应的上行调度的优先级(该MAC PDU是为该上行调度生成的MAC PDU)。某个上行调度与MAC PDU比较优先级是表示该上行调度的优先级与MAC PDU对应的上行调度的优先级进行比较或者是为该上行调度生成的MAC PDU的优先级与该MAC PDU的优先级进行比较。如果上行调度的优先级由其对应的MAC PDU决定或由对应优先级最高的逻辑信道的优先级决定，那么上行调度之间的优先级比较就是它们对应的MAC PDU的优先级或它们对应的优先级最高的逻辑信道的优先级的比较。相应的，上行调度接收或HARQ实体在处理相应的上行调度时，在与其他上行调度进行优先级比较前先向“决定上行调度优先级过程”获取该上行调度的优先级，例如向复用与组装过程获取优先级，然后将获取的优先级与其他上行调度的优先级进行比较。“决定上行调度优先级过程”(例如复用与组装过程)在接收到获取上行调度优先级的指示时，根据逻辑信道优先级LCP的限定条件(或RRC为每个逻辑信道配置的映射限制)确定该上行调度可发送或可复用或将要复用的数据对应的优先级最高的逻辑信道的优先级，或者将为该上行调度选择或预选的逻辑信道中优先级最高的逻辑信道的优先级作为该上行调度的优先级(“决定上行调度优先级过程”所选择的逻辑信道中有可发送数据，如果根据LCP规则所有逻辑信道都没有数据可发送，则可为对应上行调度的优先级为一个预定义的值，例如为0。也可以为只有MAC CE可发送和没有数据和MAC CE可发送分别 预定义不同的值)，并指示给上行调度接收或HARQ实体。此外，如果上行调度接收获取了/接收到了某个上行调度的优先级，在上行调度接收将该上行调度递交给HARQ实体时，可以将该上行调度的优先级也递交给HARQ实体。对于HARQ实体来说，如果从上行调度接收收到了某个上行调度的优先级，那么不需要向“决定上行调度优先级过程”获取该上行调度的优先级，但如果没有收到某个上行调度的优先级，那么可以向“决定上行调度优先级过程”获取该上行调度的优先级。可选的，HARQ实体在将上行调度递交给HARQ进程时，将该上行调度的优先级也指示给HARQ进程。
下面具体描述在发生DG/CG或CG/CG冲突时用户设备UE的HARQ实体执行的操作实施例。
以下描述HARQ实体对接收到的上行调度的一种处理方式。
对于PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠的上行调度，或者对于PUSCH持续时间仅与优先级较低的其他上行调度的PUSCH持续时间重叠的上行调度，或者该上行调度的PUSCH持续时间与其他优先级较低的上行调度的PUSCH持续时间重叠，或者PUSCH持续时间不与其他优先级较高的配置上行调度的PUSCH持续时间重叠的动态调度，识别该上行调度的HARQ进程，并且对于识别的HARQ进程，执行以下操作：
如果该上行调度用于新传(即满足新传条件，例如下面实施例步骤002/003中给出的获取MAC PDU的条件)，则获取MAC PDU。
如果获取到了MAC PDU，则将该MAC PDU、该上行调度以及识别的HARQ进程的传输块的HARQ信息递交给识别的HARQ进程，指示识别的HARQ进程触发新传，如果满足启动识别的HARQ进程的配置调度定时器的条件，则启动或重启识别的HARQ进程的配置调度定时器。
如果没有获取到MAC PDU，则清空识别的HARQ进程的HARQ缓存区，可选的，停止识别的HARQ进程的配置调度定时器(如果正在运行)。
可选的，对于PUSCH持续时间与其他优先级较高的上行调度的PUSCH持续时间重叠的上行调度，如果该上行调度用于新传(即满足新传条件，例如下面实施例中给出的获取MAC PDU的条件)，则获取MAC PDU。如果获取到了MAC PDU，则将该MAC PDU递交给识别的HARQ进程，将 该上行调度和/或识别的HARQ进程的传输块的HARQ信息递交给识别的HARQ进程(这个操作是可选的)，指示识别的HARQ进程不触发新传(或不指示识别的HARQ进程触发新传或指示识别的HARQ进程存储MAC PDU)(这个操作也是可选的)，如果满足启动识别的HARQ进程的配置调度定时器的条件，则启动或重启识别的HARQ进程的配置调度定时器。如果没有获取到MAC PDU，则清空识别的HARQ进程的HARQ缓存区，可选的，停止识别的HARQ进程的配置调度定时器(如果正在运行)。
可选的，对于PUSCH持续时间与其他优先级较高的上行调度的PUSCH持续时间重叠的上行调度，如果该上行调度用于新传(即满足新传条件，例如下面实施例中给出的获取MAC PDU的条件)，则清空识别的HARQ进程的HARQ缓存区，可选的，停止识别的HARQ进程的配置调度定时器(如果正在运行)。
可选的，对于用于重传的上行调度(即不满足新传的条件)，如果该上行调度的PUSCH持续时间与其他优先级较高的上行调度的PUSCH持续时间重叠，则忽略该上行调度，可选的，指示识别的HARQ进程不触发重传(或不指示识别的HARQ进程触发重传)，可选的，如果满足启动识别的HARQ进程的配置调度定时器的条件，则启动或重启识别的HARQ进程的配置调度定时器。
以下是HARQ实体对接收到的上行调度的另一种处理方式。
对于每个上行调度，识别这个上行调度的HARQ进程，对于识别的HARQ进程，如果该上行调度用于新传(即满足新传条件，例如下面实施例步骤002/003中给出的获取MAC PDU的条件)，则获取MAC PDU。如果获取到了MAC PDU，则将该MAC PDU递交给识别的HARQ进程，可选的，还将该上行调度和/或识别的HARQ进程的传输块的HARQ信息递交给识别的HARQ进程，可选的，如果该上行调度的PUSCH持续时间与其他优先级较高的上行调度的PUSCH持续时间重叠，则指示识别的HARQ进程不触发新传或不指示识别的HARQ进程触发新传或指示识别的HARQ进程存储MAC PDU，如果满足启动识别的HARQ进程的配置调度定时器的条件，则启动或重启识别的HARQ进程的配置调度定时器；如果该上行调度的PUSCH持续时间仅与优先级低于(或不高于)该上行调度的其他上行调度的PUSCH持续时间重叠，则指示识别的HARQ进程触发新传，可 选的，还将该上行调度和/或识别的HARQ进程的传输块的HARQ信息递交给识别的HARQ进程(如果在判断上行调度的优先级与其他上行调度的优先级之前已经执行该操作，则此处不执行)。如果没有获取到MAC PDU，则清空识别的HARQ进程的HARQ缓存区，可选的，停止识别的HARQ进程的配置调度定时器(如果正在运行)。如果该上行调度用于重传，且满足以下条件之一，则忽略这个上行调度，停止识别的HARQ进程的配置调度定时器(如果正在运行)：(1)如果该上行调度由CS-RNTI加扰的PDCCH指示且识别的HARQ进程的HARQ缓存区为空；(2)如果该上行调度是一组上行调度的一部分且没有为这组上行调度获取到MAC PDU；(3)如果该上行调度是一组上行调度的一部分且该上行调度的PUSCH持续时间与这个服务小区上的另一个由PDCCH持续时间或随机接入响应指示的上行调度的PUSCH持续时间重叠；(4)如果该上行调度的PUSCH持续时间与优先级不低于(或高于)该上行调度的其他上行调度的PUSCH持续时间重叠。
所述启动识别的HARQ进程的配置调度定时器的条件为：如果该上行调度对应CS-RNTI，或者该上行调度是配置上行调度，或者该上行调度对应C-RNTI且识别的HARQ进程被配置了配置上行调度，则如果配置了配置调度定时器，当执行传输时启动或重启配置调度定时器。
需要说明的是，在上行调度接收执行的操作实施例中定义的使能优先级指示标识(包括第一或第二使能优先级指示标识)也可以应用于HARQ实体执行的操作实施例。此时，在HARQ实体执行的操作实施例中，只有在配置了使能优先级指示标识且/或所述标识的取值为1或真或TRUE或setup或第一预定义的值或所述标识出现(或者所述标识的取值为0或假或False或release或所述标识不出现)时才判断接收到的上行调度的PUSCH持续时间与其他上行调度的PUSCH持续时间是否重叠，并根据判断结果执行实施例中所定义的操作。如果没有配置使能优先级指示标识或标识的取值为0或假或False或第二预定义的值或所述标识不出现(或者所述标识的取值为1或真或TRUE或所述标识出现)时，按照实施例中不执行判断接收到的上行调度的PUSCH持续时间与另一个上行调度的PUSCH持续时间是否重叠操作的方式执行(即默认条件满足)。在HARQ实体执行的操作实施例中，对使能优先级指示标识和上行调度间优先级比较的判断与在上行调度接收执行的操作实施例中定义的第一设定条件(1-8)和第二设定条件 (1-5)相同。
下面通过具体的实施例对上述两种处理方式更详细的描述。
实施例三
图4是示出了根据本发明的实施例三的由用户设备执行的方法的流程图。
如图4所示，在本发明的实施例三中，用户设备UE执行的步骤包括：步骤001～009。
在本实施例中，对于每个上行调度(或者对于PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠的上行调度，或者对于PUSCH持续时间仅与其他优先级较低的上行调度的PUSCH持续时间重叠的上行调度，或者PUSCH持续时间不与优先级较高的其他上行调度的PUSCH持续时间重叠的动态调度)，HARQ实体执行以下操作：
在步骤001，识别与该上行调度对应的HARQ进程，并对每个识别的HARQ进程(identify the HARQ process associated with this grant，and for each identified HARQ process)执行步骤002。
在步骤002，如果接收到的上行调度不是由对应TC-RNTI的PDCCH指示，且相应的HARQ信息中提供的NDI与该HARQ进程的传输块的前一次传输的NDI值相比发生了翻转(if the received grant was not addressed to a Temporary C-RNTI on PDCCH，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)；或者如果接收到的上行调度是由C-RNTI加扰的PDCCH指示且该识别的HARQ进程的HARQ缓存区为空(if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty)；或者如果上行调度接收自随机接入响应(if the uplink grant was received in a Random Access Response)；或者如果在ra-ResponseWindow内接收到的上行调度是由C-RNTI加扰的PDCCH指示且这个PDCCH成功完成了由波束错误恢复引起的随机接入过程(if the uplink grant was received on PDCCH for the C-RNTI in ra-ResponseWindow and this PDCCH successfully completed the Random  Access procedure initiated for beam failure recovery)；或者如果上行调度是一组配置上行调度的一部分且可能被用于初始传输且还没有为这组配置上行调度获取MAC PDU(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)，则执行步骤003(满足所述条件中的至少一个条件)，否则(所述条件均不满足)，执行步骤008(上行调度用于重传)。
在步骤003，如果消息3(Msg3)缓存区中有MAC PDU且上行调度接收自随机接入响应(if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response)，或者如果消息3(Msg3)缓存区中有MAC PDU且在ra-ResponseWindow接收到的上行调度是由C-RNTI加扰的PDCCH指示且这个PDCCH成功完成了由波束错误恢复引起的随机接入过程(ifthere is a MAC PDU in the Msg3 buffer and the uplink grant was received on PDCCH for the C-RNTI in ra-ResponseWindow and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery)，则执行步骤004(满足所述条件中的至少一个条件)，否则(所述条件均不满足)，执行步骤005。
在步骤004，从Msg3缓存区获取MAC PDU。如果上行调度的大小与获取的MAC PDU大小不匹配并且在接收到该上行调度时随机接入过程成功完成(if the uplink grant size does not match with size of the obtained MAC PDU，and if the Random Access procedure was successfully completed upon receiving the uplink grant)，指示复用和组装实体在后续上行链路传输中包括从获得的MAC PDU携带MAC SDU的MAC subPDU(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)，从复用和组装实体获取MAC PDU用于传输。执行步骤006。
在步骤005，从复用和组装实体获取MAC PDU用于传输(如果存在)(obtain the MAC PDU to transmit from the Multiplexing and assembly entity，ifany)。执行步骤006。
在步骤006，如果获取到了用于传输的MAC PDU(if a MAC PDU to transmit has been obtained)，则执行以下操作(并在执行完以下操作后结束)：
(1)将该MAC PDU和/或该上行调度和/或这个传输块的HARQ信息 递交给识别的HARQ进程(deliver the MAC PDU and/or the uplink grant and/or the HARQ information of the TB to the identified HARQ process)。
(2)优选的，指示识别的HARQ进程触发新传。备选的，如果该上行调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠或者该上行调度的PUSCH持续时间仅与其他优先级较低的上行调度的PUSCH持续时间重叠(If the uplink grant does not overlap with other uplink grant or if the uplink grant overlaps with other uplink grant with lower priority)或者该上行调度是由C-RNTI加扰的PDCCH指示且与其PUSCH持续时间重叠的配置上行调度的优先级不高于该上行调度(这个操作中的以上这些判断条件是可选的，例如在HARQ实体对每个上行调度执行步骤001及其后续步骤时，才判断是否满足这些条件并在满足其中任一条件时执行后续操作)，则指示识别的HARQ进程触发新传(instruct the identified HARQ process to trigger a new transmission)和/或将该上行调度和/或这个传输块的HARQ信息递交给识别的HARQ进程(deliver the uplink grant and/or the HARQ information of the TB to the identified HARQ process)；否则(可选)，将该上行调度和/或这个传输块的HARQ信息递交给识别的HARQ进程和/或指示识别的HARQ进程不触发新传(或不指示识别的HARQ触发新传或指示识别的HARQ进程存储MAC PDU)和/或忽略该上行调度；可选的，如果该上行调度是由C-RNTI加扰的PDCCH指示且该上行调度的PUSCH持续时间与其他优先级较高的上行调度的PUSCH持续时间重叠(这判断条件是可选的，例如在HARQ实体对每个上行调度执行步骤001及其后续步骤时，才判断是否满足这个条件并在满足条件时执行后续操作)，则将该上行调度和/或这个传输块的HARQ信息递交给识别的HARQ进程和/或指示识别的HARQ进程不触发新传(或不指示识别的HARQ触发新传或指示识别的HARQ进程存储MAC PDU)和/或忽略该上行调度。
(3)如果接收到的上行调度对应CS-RNTI(if the uplink grant is addressed to CS-RNTI)，或者接收到的上行调度是配置上行调度，或者接收到的上行调度对应C-RNTI且识别的HARQ进程被配置了配置上行调度(if the uplink grant is addressed to C-RNTI，and the identified HARQ process is configured for a configured uplink grant)，则如果配置了配置调度定时器，当执行传输时启动或重启配置调度定时器configuredGrantTimer(start or restart  theconfiguredGrantTimer，if configured，for the corresponding HARQ process when the transmission is performed)；
否则(没有获取到用于传输的MAC PDU)，则执行步骤007。
在步骤007，清空识别的HARQ进程的HARQ缓存区。可选的，如果配置调度定时器正在运行，则停止配置调度定时器。结束。
在步骤008，如果满足第三设定条件，则忽略该上行调度；如果不满足第三设定条件，则执行步骤009。所述第三设定条件可以是以下至少一个：
(1)如果该上行调度由CS-RNTI加扰的PDCCH指示(the uplink grant received on PDCCH was addressed to CS-RNTI)且识别的HARQ进程的HARQ缓存区为空；
(2)如果该上行调度是一组上行调度的一部分且没有为这组上行调度获取到MAC PDU(if the uplink grant is part of a bundle and if no MAC PDU has been obtained for this bundle)
(3)如果该上行调度是一组上行调度的一部分且该上行调度的PUSCH与这个服务小区上的另一个由PDCCH或随机接入响应指示的上行调度的PUSCH重叠(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)
(4)该上行调度由PDCCH指示且/或该上行调度的PUSCH持续时间与另一个优先级较高的上行调度的PUSCH持续时间重叠。
可选的，在步骤008中还包括：如果该上行调度被忽略，如果该上行调度由CS-RNTI加扰的PDCCH指示和/或如果识别的HARQ进程对应的配置调度定时器正在运行，则停止该配置调度定时器。
可选的，在步骤008中，在忽略上行调度后，如果识别的HARQ进程对应的配置调度定时器正在运行(只有当该HARQ进程上配置了配置上行调度和/或配置调度定时器时才执行)，则停止该配置调度定时器。
可选的，在步骤008中还包括：如果该上行调度由CS-RNTI加扰的PDCCH指示(the uplink grant received on PDCCH was addressed to CS-RNTI)且识别的HARQ进程的HARQ缓存区为空，如果识别的HARQ进程对应的配置调度定时器正在运行(只有当该HARQ进程上配置了配置上行调度 和/或配置调度定时器时才执行)，则停止该配置调度定时器。
可选的，在步骤008中还包括：如果该上行调度由PDCCH指示且/或该上行调度的PUSCH持续时间与另一个优先级较高的上行调度的PUSCH持续时间重叠，如果识别的HARQ进程对应的配置调度定时器正在运行(只有当该HARQ进程上配置了配置上行调度和/或配置调度定时器时才执行)，则停止该配置调度定时器。
在步骤009，将该上行调度和该传输块对应的HARQ信息(冗余版本)递交给识别的HARQ进程；指示识别的进程触发一个重传；如果接收到的上行调度对应CS-RNTI或接收到的上行调度是配置上行调度或接收到的上行调度对应C-RNTI且识别的HARQ进程被配置了配置上行调度，则如果配置了配置调度定时器，当执行传输时启动或重启所述配置调度定时器configuredGrantTimer。
实施例四
图5是示出了根据本发明的实施例四的由用户设备执行的方法的流程图。
如图5所示，在本发明的实施例四中，用户设备UE执行的步骤包括：步骤101～113。
在本实施例中，对于每个上行调度(或者对于PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠的上行调度，或者对于PUSCH持续时间仅与其他优先级较低的上行调度的PUSCH持续时间重叠的上行调度，或者PUSCH持续时间不与优先级较高的其他上行调度的PUSCH持续时间重叠的动态调度)，HARQ实体执行以下操作：
在步骤101，识别与该上行调度对应的HARQ进程，并对每个识别的HARQ进程执行步骤102。
在步骤102，如果接收到的上行调度不是由对应TC-RNTI的PDCCH指示，且相应的HARQ信息中提供的NDI与该HARQ进程的传输块的前一次传输的NDI值相比发生了翻转；或者如果接收到的上行调度是由C-RNTI加扰的PDCCH指示且该识别的HARQ进程的HARQ缓存区为空； 或者如果上行调度接收自随机接入响应；或者如果在ra-ResponseWindow内接收到的上行调度是由C-RNTI加扰的PDCCH指示且这个PDCCH成功完成了由波束错误恢复引起的随机接入过程；或者如果上行调度是一组配置上行调度的一部分且可能被用于初始传输且还没有为这组配置上行调度获取MAC PDU，则执行步骤103(满足所述条件中的至少一个条件)，否则(所述条件均不满足)，执行步骤108。
在步骤103，如果消息3(Msg3)缓存区中有MAC PDU且上行调度接收自随机接入响应，或者如果消息3(Msg3)缓存区中有MAC PDU且在ra-ResponseWindow接收到的上行调度是由C-RNTI加扰的PDCCH指示且这个PDCCH成功完成了由波束错误恢复引起的随机接入过程，则执行步骤104(满足所述条件中的至少一个条件)，否则(所述条件均不满足)，执行步骤105。
在步骤104，从Msg3缓存区获取MAC PDU。如果上行调度的大小与获取的MAC PDU大小不匹配并且在接收到该上行调度时随机接入过程成功完成，指示复用和组装实体在后续上行链路传输中包括从获得的MAC PDU携带MAC SDU的MAC subPDU，从复用和组装实体获取MAC PDU用于传输。执行步骤106。
在步骤105，从复用和组装实体获取MAC PDU用于传输(如果存在)。执行步骤106。
在步骤106，如果获取到了用于传输的MAC PDU(if a MAC PDU to transmit has been obtained)，则执行以下操作(并在执行完以下操作后结束)：
(1)将该MAC PDU和/或该上行调度和/或这个传输块的HARQ信息递交给识别的HARQ进程。
(2)优选的，指示识别的HARQ进程触发新传。备选的，如果该上行调度的PUSCH持续时间不与其他上行调度的PUSCH持续时间重叠或者该上行调度的PUSCH持续时间仅与其他优先级较低的上行调度的PUSCH持续时间重叠或者该上行调度是由C-RNTI加扰的PDCCH指示且与其PUSCH持续时间重叠的配置上行调度的优先级不高于该上行调度(这个操作中的以上这些判断条件是可选的，例如在HARQ实体对每个上行调度执行步骤101及其后续步骤时，才判断是否满足这些条件并在满足其中任一条件时执行后续操作)，则指示识别的HARQ进程触发新传和/或将该上行 调度和/或这个传输块的HARQ信息递交给识别的HARQ进程；否则(可选)，将该上行调度和/或这个传输块的HARQ信息递交给识别的HARQ进程和/或指示识别的HARQ进程不触发新传(或不指示识别的HARQ触发新传或指示识别的HARQ进程存储MAC PDU)和/或忽略该上行调度；可选的，如果该上行调度是由C-RNTI加扰的PDCCH指示且该上行调度的PUSCH持续时间与其他优先级较高的上行调度的PUSCH持续时间重叠(这判断条件是可选的，例如在HARQ实体对每个上行调度执行步骤101及其后续步骤时，才判断是否满足这个条件并在满足条件时执行后续操作)，则将该上行调度和/或这个传输块的HARQ信息递交给识别的HARQ进程和/或指示识别的HARQ进程不触发新传(或不指示识别的HARQ触发新传或指示识别的HARQ进程存储MAC PDU)和/或忽略该上行调度。
(3)如果接收到的上行调度对应CS-RNTI，或者接收到的上行调度是配置上行调度，或者接收到的上行调度对应C-RNTI且识别的HARQ进程被配置了配置上行调度，则如果配置了配置调度定时器，当执行传输时启动或重启配置调度定时器configuredGrantTimer；
否则(没有获取到用于传输的MAC PDU)，则执行步骤107。
在步骤107，清空识别的HARQ进程的HARQ缓存区。可选的，如果配置调度定时器正在运行，则停止配置调度定时器。结束。
在步骤108，如果接收到的上行调度由C-RNTI加扰的PDCCH指示且递交给这个HARQ实体的同一HARQ进程(为接收到的上行调度识别的HARQ进程)的另一个上行调度是由CS-RNTI加扰的PDCCH指示或是配置上行调度，或者如果接收到的上行调度是配置上行调度且递交给这个HARQ实体的同一HARQ进程的另一个上行调度是由CS-RNTI或C-RNTI加扰的PDCCH指示，或者识别的HARQ进程的HARQ缓存区中存在尚未发送或等待初传的MAC PDU，则执行步骤109，否则，执行步骤112。
在步骤109，如果这个接收到的配置调度的优先级更高(比同一HARQ进程上的CG或尚未发送或等待初传的MAC PDU的优先级更高，或者不比同一HARQ进程上的CG或尚未发送或等待初传的MAC PDU的优先级低)，则执行步骤110；否则，执行步骤111。
在步骤110，从复用和组装实体获取用于传输MAC PDU；将该MAC PDU及该上行调度及这个传输块的HARQ信息递交给识别的HARQ进程； 指示识别的HARQ进程触发新传；当执行传输时启动或重启识别的HARQ进程对应的配置调度定时器(只有为该配置上行调度配置了配置调度定时器才执行)。结束。
在步骤111，如果接收到的上行调度由C-RNTI加扰的PDCCH指示，则忽略该上行调度。如果接收到的上行调度是配置的上行调度且递交给这个HARQ实体的同一HARQ进程(为接收到的上行调度识别的HARQ进程)的前一个上行调度是由CS-RNTI加扰的PDCCH指示或是配置上行调度，则将待上行调度和这个TB的HARQ信息(冗余版本)递交给识别的HARQ进程；指示识别的HARQ进程触发重传，启动这个HARQ进程的配置调度定时器(如果配置了)。如果以上条件都不满足，则忽略该上行调度。结束。
在步骤112(与上一个实施例三中步骤008相同)，如果满足第四设定条件，则忽略该上行调度；如果不满足第三设定条件，则执行步骤113。所述第四设定条件可以是以下至少一个：
(1)如果该上行调度由CS-RNTI加扰的PDCCH指示(the uplink grant received on PDCCH was addressed to CS-RNTI)且识别的HARQ进程的HARQ缓存区为空；
(2)如果该上行调度是一组上行调度的一部分且没有为这组上行调度获取到MAC PDU(if the uplink grant is part of a bundle and if no MAC PDU has been obtained for this bundle)
(3)如果该上行调度是一组上行调度的一部分且该上行调度的PUSCH与这个服务小区上的另一个由PDCCH或随机接入响应指示的上行调度的PUSCH重叠(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)
(4)该上行调度由PDCCH指示且/或该上行调度的PUSCH持续时间与另一个优先级较高的上行调度的PUSCH持续时间重叠。
可选的，在步骤112中，如果该上行调度被忽略，如果该上行调度由CS-RNTI加扰的PDCCH指示和/或如果识别的HARQ进程对应的配置调度定时器正在运行，则停止该配置调度定时器。
可选的，在步骤112中，如果该上行调度由CS-RNTI加扰的PDCCH指示(the uplink grant received on PDCCH was addressed to CS-RNTI)且识别的HARQ进程的HARQ缓存区为空，如果识别的HARQ进程对应的配置调度定时器正在运行(只有当该HARQ进程上配置了配置上行调度和/或配置调度定时器时才执行)，则停止该配置调度定时器。
可选的，在步骤112中，如果该上行调度由PDCCH指示且/或该上行调度的PUSCH持续时间与另一个优先级较高的上行调度的PUSCH持续时间重叠，如果识别的HARQ进程对应的配置调度定时器正在运行(只有当该HARQ进程上配置了配置上行调度和/或配置调度定时器时才执行)，则停止该配置调度定时器。
在步骤113(与上一个实施例三中步骤009相同)，将该上行调度和该传输块对应的HARQ信息(冗余版本)递交给识别的HARQ进程；指示识别的进程触发一个重传；如果接收到的上行调度对应CS-RNTI或接收到的上行调度是配置上行调度或接收到的上行调度对应C-RNTI且识别的HARQ进程被配置了配置上行调度，则如果配置了配置调度定时器，当执行传输时启动或重启所述配置调度定时器configuredGrantTimer。
需要说明的是，在本公开实施例中，每个HARQ进程支持一个传输块TB或两个传输块(在空分复用MIMO中支持两个传输块)。
需要说明的是，如果HARQ实体为较低优先级的上行调度(所述上行调度的PUSCH持续时间与优先级较高的上行调度的PUSCH持续时间重叠)生成/获取了MAC PDU并存储在缓存区中或者如果较低优先级的上行调度有数据要发送，则指示复用与组装过程在为优先级较高的上行调度生成MAC PDU时在其中包含一个缓存数据指示MAC CE或者触发低优先级数据指示。可选的，如果缓存数据指示被触发且未被取消，当MAC实体被分配了用于新传的上行资源时，指示复用和组装过程生成一个缓存数据指示MAC CE，取消触发的缓存数据指示。其中，所述较低优先级的上行调度有数据要发送可以是HARQ实体通过向“决定上行调度优先级过程”获取的优先级确定，因此较低优先级的上行调度有数据要发送也可以描述为低优先级的上行调度的优先级不是为没有数据和/或没有数据和MAC CE发送而 预定义的值，例如低优先级的上行调度的优先级大于0。所述缓存数据指示MAC CE中可以指示发生PUSCH持续时间重叠的低优先级上行调度是否有缓存数据或者指示低优先级的上行调度识别的HARQ进程的缓存区是否有缓存数据。例如，用位图表示，位图中的每位对应一个发生PUSCH持续时间重叠的低优先级上行调度，当所述上行调度对应的HARQ进程的缓存区有缓存数据，则对应的位被置为1(或0)，否则置为0(或1)。优选的，如果缓存数据指示MAC CE被包含在为动态调度生成的MAC PDU中，则将发生PUSCH持续时间重叠的配置调度按照配置调度标识由小到大(或从大到小)的顺序以此对应位图中从左到右(或从右到左)的位。例如，位图第0位对应发生PUSCH持续时间重叠的具有最小配置调度标识的配置调度，依次类推。如果缓存数据指示MAC CE被包含在为配置调度生成的MAC PDU中，则位图的第0位对应动态，第1位对应发生PUSCH持续时间重叠的具有最小配置调度标识的配置调度，依次类推。所述配置调度标识是基站通过RRC信令/消息为每个配置调度配置的，例如，包含在ConfiguredGrantConfig信元中，在配置相应的配置调度时配置。可选的，缓存数据指示MAC CE的优先级小于PHR MAC CE(包括Single Entry PHR MAC CE和Multiple Entry PHR MAC CE)大于来自逻辑信道的数据的优先级(来自UL-CCCH的数据除外)
下面具体描述在发生DG/CG或CG/CG冲突时用户设备UE的HARQ进程的执行的操作实施例。
在一个实施例中，如果HARQ实体请求存储一个传输块(TB)对应的MAC PDU或如果HARQ实体请求不触发新传或重传或如果HARQ进程没有接收到来自HARQ实体的触发新传或重传的指示，则HARQ进程执行以下操作至少一项：
1)存储接收来自HARQ实体对应于存储的MAC PDU的上行调度(store the uplink grant received from the HARQ entity for storing MAC PDU)；
2)不产生传输或重传(do not generate a transmission or retransmission)。
需要说明的是，在本公开中如未特别说明调度都是指上行调度，动态调度是指对某个服务小区来说在PDCCH上接收到MAC实体的C-RNTI或 CS-RNTI的上行调度(an uplink grant for a serving cell is received on the PDCCH for the MAC entity’s C-RNTI or CS-RNTI)(换言之，在PDCCH上接收到的上行调度)，如果动态调度是针对MAC实体的CS-RNTI，那么NDI为1；配置调度就是配置上行调度(configured uplink grant)。
下面描述复用与组装(也可以是逻辑信道优先级过程LCP)过程在接受到多个上行调度时的处理方式实施例。
在一个实施例中，如果复用和组装过程接收到一个PUSCH持续时间与其他上行调度的PUSCH持续时间重叠的上行调度，且该上行调度的优先级更高，复用与组装过程已经为所述较低优先级的上行调度生成了MAC PDU，则将已经包含在为所述较低优先级的上行调度生成了MAC PDU的MAC控制元素CE(包括缓存状态报告BSR和功率余量报告PHR)包含在为该优先级较高的上行调度生成的MAC PDU中(如果其中包含BSR，则要重新计算并生成BSR)，如果所述较低优先级的上行调度生成的MAC PDU只包含MAC CE，则将所有MAC CE包含在为较高优先级的上行调度生成的MAC PDU中(所述MAC CE包括BSR、PHR、配置调度确认MAC CE)，并取消为所述较低优先级的上行调度生成的MAC PDU(即清空低优先级上行调度对应的HARQ进程的HARQ缓存区)，可选的，还停止所述较低优先级的上行调度对应的HARQ进程的配置调度定时器(如果正在运行)。
在一个实施例中，如果接收到一个服务小区的多个上行调度，先为具有较高优先级的上行调度生成MAC PDU且MAC CE(包括BSR、PHR、配置调度确认MAC CE，如果存在)包含在这个MAC PDU中。如果接收到的多个上行调度的优先级相同，如果其中包含动态调度，则为动态调度生成MAC PDU并在其中包含需要发送的MAC CE。
[变形例]
下面，利用图6来说明作为一种变形例的可执行本发明上面所详细描述的用户设备执行的方法的用户设备。
图6是表示本发明所涉及的用户设备UE的框图。
如图6所示，该用户设备UE60包括处理器601和存储器602。处理器601例如可以包括微处理器、微控制器、嵌入式处理器等。存储器602例如 可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器602上存储有程序指令。该指令在由处理器601运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
下面，利用图7来说明作为一种变形例的可执行本发明上面所详细描述的基站执行的方法的基站。
图7是表示本发明所涉及的基站的框图。
如图7所示，该基站70包括处理器701和存储器702。处理器701例如可以包括微处理器、微控制器、嵌入式处理器等。存储器702例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器702上存储有程序指令。该指令在由处理器701运行时，可以执行本发明详细描述的由基站执行的上述方法。
另外，本发明提出了一种由基站执行的方法。根据本发明的由基站执行的方法，基站向用户设备UE发送第一使能优先级指示标识和/或第二使能优先级指示标识。当接收到所述第一使能优先级指示标识和/或所述第二使能优先级指示标识时，所述UE执行以上实施例中所述的操作。
运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他 记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (6)

  1. 一种由用户设备UE执行的方法，包括：
    从基站接收无线资源控制RRC消息，所述RRC消息中包含第一使能优先级指示标识，所述第一使能优先级指示标识用于指示所述UE在不同HARQ进程上发生了上行许可的物理上行共享信道PUSCH冲突时，对发生了冲突的上行许可基于逻辑信道优先级进行优先级比较；
    针对每个服务小区上激活的配置上行许可，判断是否满足第一设定条件；
    如果满足所述第一设定条件，则将混合自动重传请求HARQ进程标识设置为该配置上行许可的物理上行共享信道PUSCH持续时间所关联的HARQ进程标识。
  2. 根据权利要求1所述的方法，其中，
    所述第一设定条件包括以下条件中的任一个或其任意组合：
    配置了第一使能优先级指示标识；以及
    配置上行调度的物理上行共享信道PUSCH持续时间不与所述服务小区上接收自随机接入响应中的上行调度的PUSCH持续时间冲突。
  3. 根据权利要求1所述的方法，还包括，
    如果HARQ进程标识对应的HARQ进程的配置上行许可定时器未运行，则认为新数据指示NDI发生翻转并将该配置上行许可递交给HARQ实体。
  4. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令，
    其中，所述指令在由所述处理器运行时执行根据权利要求1至3中的任一项所述的方法。
  5. 一种由基站执行的方法，包括：
    向用户设备UE发送无线资源控制RRC消息，所述RRC消息中包含第一使能优先级指示标识，所述第一使能优先级指示标识用于指示所述UE在不同HARQ进程上发生了上行许可的物理上行共享信道PUSCH冲突时，对发生了冲突的上行许可基于逻辑信道优先级进行优先级比较，
    当接收到所述第一使能优先级指示标识时，所述UE执行权利要求1所述的方法。
  6. 一种基站，包括：
    处理器；以及
    存储器，存储有指令，
    其中，所述指令在由所述处理器运行时执行根据权利要求5所述的方法。
PCT/CN2020/097724 2019-06-25 2020-06-23 用户设备、基站及其方法 WO2020259495A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/622,138 US12016049B2 (en) 2019-06-25 2020-06-23 User equipment, base station, and method thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910558282.XA CN112135356A (zh) 2019-06-25 2019-06-25 用户设备、基站及其方法
CN201910558282.X 2019-06-25

Publications (1)

Publication Number Publication Date
WO2020259495A1 true WO2020259495A1 (zh) 2020-12-30

Family

ID=73849518

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/097724 WO2020259495A1 (zh) 2019-06-25 2020-06-23 用户设备、基站及其方法

Country Status (3)

Country Link
US (1) US12016049B2 (zh)
CN (1) CN112135356A (zh)
WO (1) WO2020259495A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023011326A1 (zh) * 2021-08-03 2023-02-09 大唐移动通信设备有限公司 Mac pdu的传输处理方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113632562A (zh) * 2019-07-25 2021-11-09 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
CN111901882A (zh) * 2020-01-17 2020-11-06 中兴通讯股份有限公司 信道冲突处理方法、装置、设备和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018075828A1 (en) * 2016-10-19 2018-04-26 Convida Wireless, Llc Apparatus
US20180368133A1 (en) * 2017-06-15 2018-12-20 Samsung Electronics Co., Ltd. Method and apparatus for an uplink transmission based on a characteristic of physical resources
CN109891987A (zh) * 2016-11-04 2019-06-14 瑞典爱立信有限公司 用于无线通信系统中的传输调度的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018075828A1 (en) * 2016-10-19 2018-04-26 Convida Wireless, Llc Apparatus
CN109891987A (zh) * 2016-11-04 2019-06-14 瑞典爱立信有限公司 用于无线通信系统中的传输调度的方法和装置
US20180368133A1 (en) * 2017-06-15 2018-12-20 Samsung Electronics Co., Ltd. Method and apparatus for an uplink transmission based on a characteristic of physical resources

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
FUJITSU: "Prioritization and UE autonomous switching", 3GPP TSG-RAN WG2 MEETING #106 R2-1906254, 17 May 2019 (2019-05-17), XP051729724, DOI: 20200909145753Y *
SAMSUNG: "Prioritization between Data Resources", 3GPP TSG-RAN WG2 MEETING #106 R2-1906792, 17 May 2019 (2019-05-17), XP051730248, DOI: 20200909145537Y *
SHARP: "Discussion on Intra-UE prioritization and multiplexing", 3GPP TSG RAN WG1 MEETING #97 R1-1907225, 17 May 2019 (2019-05-17), XP051728668, DOI: 20200909150414A *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023011326A1 (zh) * 2021-08-03 2023-02-09 大唐移动通信设备有限公司 Mac pdu的传输处理方法及装置

Also Published As

Publication number Publication date
CN112135356A (zh) 2020-12-25
US20220264595A1 (en) 2022-08-18
US12016049B2 (en) 2024-06-18

Similar Documents

Publication Publication Date Title
WO2020259495A1 (zh) 用户设备、基站及其方法
WO2020259496A1 (zh) 用户设备、基站及其方法
US12035324B2 (en) Data sending method, data sending apparatus, and terminal device utilizing a configured grant resource
WO2021022907A1 (zh) 数据传输方法、装置及存储介质
JP2021168485A (ja) 混合許可無し及び許可有りアップリンク送信のためのシステム及び方法
CN112567661A (zh) 用于以不同可靠性传递数据的方法、系统和设备
JP6940121B2 (ja) データ伝送方法、機器およびシステム
US11445553B2 (en) Method executed by user equipment, user equipment and base station
WO2021063307A1 (zh) 由用户设备执行的方法以及用户设备
WO2017166929A1 (zh) 基站、用户设备和相关方法
WO2016065620A1 (zh) 混合自动重传反馈的获取方法、装置以及通信系统
EP3422766A1 (en) Data transmission method and device
WO2016119102A1 (zh) 缓存状态报告的处理方法、装置以及通信系统
US20160337867A1 (en) Mobile station, base station, uplink signal transmission method, and uplink signal reception method
TWI777392B (zh) 考量組配授權計時器之彈性資料傳輸方法及設備以及關聯之電腦可讀媒體
WO2019120311A1 (zh) 无线通信方法和设备
WO2020063767A1 (zh) 上行免动态授权传输的配置方法及通信装置
WO2016106729A1 (zh) 缓存状态报告的生成方法、装置以及通信系统
EP3668226A1 (en) Base station, user equipment, and related method
US20220360414A1 (en) Communication processing method and communication device
WO2021063305A1 (zh) 由用户设备执行的方法以及用户设备
WO2019062641A1 (zh) 无线通信方法和设备
WO2021139673A1 (zh) 由用户设备执行的方法以及用户设备
WO2018112922A1 (zh) 一种数据传输的方法及设备
WO2018121643A1 (zh) 一种数据传输方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20830751

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20830751

Country of ref document: EP

Kind code of ref document: A1