WO2021063305A1 - 由用户设备执行的方法以及用户设备 - Google Patents

由用户设备执行的方法以及用户设备 Download PDF

Info

Publication number
WO2021063305A1
WO2021063305A1 PCT/CN2020/118361 CN2020118361W WO2021063305A1 WO 2021063305 A1 WO2021063305 A1 WO 2021063305A1 CN 2020118361 W CN2020118361 W CN 2020118361W WO 2021063305 A1 WO2021063305 A1 WO 2021063305A1
Authority
WO
WIPO (PCT)
Prior art keywords
priority
mac pdu
low
harq process
mac
Prior art date
Application number
PCT/CN2020/118361
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 夏普株式会社
Publication of WO2021063305A1 publication Critical patent/WO2021063305A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • 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
    • 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/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

Definitions

  • the present disclosure relates to the field of wireless communication technology, and more specifically, the present disclosure relates to methods executed by user equipment and user equipment.
  • UE user equipment
  • 3GPP Working Group 2 (RAN2) needs to define a physical uplink shared channel PUSCH (Physical Uplink Shared CHannel) scheduling priority processing mechanism based on logical channel (LCH) priority and logical channel priority (LCP) restrictions.
  • PUSCH Physical Uplink Shared CHannel
  • the present disclosure solves the problems involved in retransmitting the low-priority MAC PDU stored in the HARQ process buffer area.
  • the purpose of the present invention is to provide a method executed by a user equipment and a user equipment that can reliably execute processing related to the low-priority MAC PDU stored in the HARQ process buffer area.
  • a method executed by a user equipment including: identifying a hybrid automatic repeat request HARQ process associated with an uplink grant; judging according to a low-priority media access control protocol data unit MAC PDU indication Whether the low priority MAC PDU waiting to be transmitted is stored in the HARQ buffer area of the HARQ process.
  • the timer corresponding to the HARQ process is running, the HARQ buffer area of the HARQ process has a low-priority MAC PDU waiting for transmission, and there is a low-priority MAC PDU indication waiting for transmission.
  • the multiplexing and assembling entity carries a low-priority MAC PDU indicating MAC control element CE in the generated MAC PDU, and uses the MAC CE to indicate that there is a low-priority MAC PDU waiting to be transmitted in the HARQ buffer area of the HARQ process, or
  • the low priority MAC PDU indication carried in the generated MAC PDU by the user and assembling entity indicates that there is a low priority MAC PDU waiting to be transmitted in the HARQ buffer area of the HARQ process in the MAC CE.
  • the physical uplink control channel PUCCH resource and the priority of the uplink shared channel UL-SCH, the physical uplink shared channel PUSCH, and the uplink grant with a priority lower than the priority of the SR may be transmitted in the scheduling request SR waiting to be sent.
  • a low-priority MAC PDU indication is triggered.
  • the MAC entity triggers a low-priority MAC PDU indication after instructing the physical layer to send the SR.
  • the given condition may include at least one of the following conditions: the MAC entity has valid PUCCH resources configured for the SR; the MAC entity has valid PUCCH resources configured for the SR SR transmission timing; the timer corresponding to the SR transmission is not running at the SR transmission timing; the PUCCH resource of the SR transmission does not overlap with the measurement interval; the PUCCH resource of the SR transmission does not have a priority higher than the SR Level of UL-SCH overlap.
  • the priority of the SR is the priority of the logical channel that triggers the SR.
  • the multiplexing and assembling entity is instructed to generate a low priority MAC PDU indication MAC CE and/or cancel the triggered low priority MAC PDU indication.
  • the low priority MAC PDU indication MAC CE includes the HARQ process number used to indicate the HARQ process number of the HARQ process identified by the low priority configuration uplink grant recognition that the physical uplink shared channel PUSCH duration overlaps Information, or including HARQ process number information used to indicate that a low-priority MAC PDU waiting to be transmitted is stored in the HARQ buffer area.
  • a user equipment including: a processor; and a memory storing instructions; wherein the instructions execute the above method when run by the processor.
  • the processing related to the low-priority MAC PDU stored in the HARQ process buffer area can be reliably executed.
  • Fig. 1 shows a flowchart of a method executed by a user equipment according to an embodiment of the present invention.
  • Fig. 2 shows a flowchart of a method executed by a user equipment according to the first embodiment of the present invention.
  • Fig. 3 shows a flowchart of a method executed by a user equipment according to the third embodiment of the present invention.
  • Figure 4 shows a schematic diagram of a low-priority MAC PDU indicating a MAC CE.
  • Fig. 5 shows a block diagram of a user equipment according to an embodiment of 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.
  • PUCCH Physical Uplink Control Channel, physical uplink control channel.
  • PUSCH Physical Uplink Shared Channel, physical uplink shared channel.
  • UL-SCH Uplink Shared Channel, uplink shared channel
  • SDU Service Data Unit, service data unit.
  • PDU Protocol Data Unit, protocol data unit.
  • SR Scheduling Request, scheduling request.
  • CG Configured uplink Grant, configuration permission.
  • configuredGrantTimer This is a timer.
  • the initial value of the timer is configured by the base station for each CG of the UE through RRC signaling, and its value is several times the corresponding CG period.
  • the information element configuredGrantTimer defined in TS38.331.
  • the start and stop operations of this timer are described in TS38.321. In the embodiment of the present disclosure, other start or stop conditions for this timer are added.
  • RNTI Radio Network Temporary Identifier, wireless network temporary identifier.
  • CS-RNTI Configured Scheduling RNTI, configure scheduling RNTI.
  • DG Dynamic Grant
  • dynamic grant refers to the uplink grant dynamically received on the PDCCH.
  • the uplink grant of the CS-RNTI that is the MAC entity can be used to configure the retransmission of the MAC PDU transmitted on the uplink grant.
  • the received New Data Indicator (NDI) value is 1 and the NDI is not reversed. .
  • the uplink grant received on the PDCCH is the C-RNTI or TC-RNTI or CS-RNTI of the MAC entity and is an uplink grant indicated by the PDCCH 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 by DL-SCH or UL-SCH consists of NDI, Transport Block size (TBS), Redundancy Version (RV) and HARQ process ID (HARQ process ID) .
  • TBS Transport Block size
  • RV Redundancy Version
  • HARQ process ID HARQ process ID
  • the HARQ information may also contain other information.
  • the UE For the dynamic grant of low-priority PUSCH, the UE stores its corresponding low-priority MAC PDU in the HARQ buffer area, so that gNB can use the same HARQ process Scheduling 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 low-priority PUSCH configuration Uplink grant, a) The UE stores its corresponding low-priority MAC PDU in the HARQ buffer so that the gNB can schedule retransmission, b) Whether the UE can retransmit on subsequent radio resources requires further discussion, for example Use subsequent radio resources associated with the same HARQ process (For de-prioritized PUSCH on configured grants, a) the UE could store the de-prioritized MAC P
  • CG conflicts with CG the same priority scheme as CG conflicts with DG is adopted (that is, based on the same priority determination method); new transmission (that is, a new MAC PDU is generated for uplink permission)
  • the same priority scheme is adopted for resource conflicts between new transmissions and new transmissions and resource conflicts between new transmissions and retransmissions (that is, retransmissions of MAC PDUs); the recovery mechanism for low-priority MAC PDUs when there is a conflict between PUSCHs ( That is, when a conflict occurs, how to retransmit the low-priority MAC PDU stored in the HARQ process buffer) is also applied to the PUSCH conflict with the scheduling request SR; when the DG and CG conflict, if the priority of the two scheduling is the same ( That is, the priority or highest priority of the MAC PDU generated by the two uplink licenses is the same), then the MAC PDU generated for the DG is considered to have a higher priority (
  • SR ie SR PUCCH or SR PUCCH
  • the conflict or overlap of the duration or the PUCCH in which the SR occurs or the PUCCH in which the SR is sent is conflicting or overlapping (in other words, UL-SCH or PUSCH and SR cannot be sent at the same time or at the same time).
  • DG/CG PUSCH conflict On a serving cell, the overlap between the PUSCH duration of the dynamically permitted DG on a certain HARQ process and the PUSCH duration of the configured permitted CG on another HARQ process is called a DG/CG PUSCH conflict.
  • the overlap of the PUSCH duration of the allowed CG configured on a certain HARQ process and the PUSCH duration of the allowed CG configured on another HARQ process is called a CG/CG PUSCH conflict.
  • DG/CG PUSCH conflicts include the conflict of PUSCH duration between one DG and multiple CGs on different HARQ processes.
  • a CG/CG PUSCH conflict also includes a PUSCH duration conflict between 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 or SRs. In the same service area.
  • the conflicts refer to the conflicting DG and CG and the conflicting two or more CGs or SRs. In the same service area.
  • PUSCH overlaps (or conflicts) or PUSCH and SR overlap (or conflict) in different uplink grants it may be that different uplink grants overlap (or conflict) in the time domain, in other words, they cannot all be sent or they cannot be sent at the same time.
  • a MAC PDU is generated for a CG that has a DG/CG or CG/CG conflict or a conflict between an uplink license and an SR, and the MAC PDU is stored in the corresponding HARQ process (that is, the HARQ process corresponding to the CG or the HARQ process identified by the CG)
  • the MAC PDU is stored in the corresponding HARQ process (that is, the HARQ process corresponding to the CG or the HARQ process identified by the CG)
  • the non-transmission may be not indicated to the physical layer, or indicated to the physical layer but not due to a conflict with a MAC PDU or SR with a higher priority. Transmission or transmission was interrupted or not transmitted on the corresponding uplink license.
  • the MAC PDU generated by the CG is referred to as a low priority MAC PDU waiting for transmission (deprioritized MAC PDU).
  • the low-priority MAC PDU waiting to be transmitted stored in the HARQ buffer area of a HARQ process is considered to be a low-priority MAC PDU waiting to be transmitted only when it is not sent on any uplink permission or when the transmission is completed. Transmission on other HARQ processes of the same CG.
  • the configuredGrantTimer (or its associated configuredGrantTimer) of the HARQ process is running.
  • the MAC PDU is the low priority MAC PDU waiting to be transmitted.
  • the HARQ buffer area can be cleared or the low-priority MAC PDUs waiting to be transmitted can be cleared.
  • the MAC entity or HARQ entity determines whether a low-priority MAC PDU waiting to be transmitted is stored in other HARQ processes of a CG, it can only be judged whether the HARQ buffer area of the HARQ process in which configuredGrantTimer is running stores low-priority MAC waiting to be transmitted. PDU.
  • the low-priority MAC PDU waiting to be transmitted in the embodiment of the present disclosure may also be referred to as an effective low-priority MAC PDU waiting to be transmitted.
  • a low-priority MAC PDU indication flag waiting to be transmitted can be set, and its initial value can be set to FALSE or false or 0 or other predefined values.
  • the low priority MAC PDU indication flag waiting to be transmitted is set to TRUE or true or 1 or other predefined values.
  • an uplink grant is available (for example, an uplink grant is received on the PDCCH of the MAC entity's C-RNTI or temporary C-RNTI)
  • this uplink grant has a higher priority
  • Low PUSCH duration conflict and the priority of the uplink grant is higher.
  • MAC PDU has been generated for the uplink grant with lower priority, it will be set to the HARQ process identified by the uplink grant with low priority (or corresponding)
  • the low-priority MAC PDU waiting for transmission indicates that the identifier is TRUE or true or 1 or other predefined values.
  • the indication flag of the low-priority MAC PDU waiting to be transmitted is set to FALSE or false or 0 or other predefined values. If a low-priority MAC PDU indicator waiting to be transmitted is set for each HARQ process of each CG, then it can be judged whether there is a low-priority MAC PDU waiting to be transmitted by judging the low priority of each HARQ process waiting to be transmitted. Level MAC PDU indicates whether the value of the identifier is TRUE or true or 1 or other predefined values.
  • Fig. 1 shows a flowchart of a method executed by a user equipment according to an embodiment of the present invention.
  • the method executed by the user equipment UE of the present invention includes: step S1 and step S2.
  • step S1 the HARQ process associated with the uplink grant is identified.
  • step S2 according to the low-priority MAC PDU indication, it is judged whether the low-priority MAC PDU waiting to be transmitted is stored in the HARQ buffer area of the HARQ process.
  • the following describes an embodiment of sending the low-priority MAC PDU waiting to be transmitted.
  • Fig. 2 shows a flowchart of 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: steps 101-105.
  • the subsequent configuration of the same CG is used to allow the transmission of the low-priority MAC PDU waiting to be transmitted.
  • the HARQ entity performs the following operations:
  • step 101 the HARQ process associated with the uplink grant is identified, and for each identified HARQ process, step 102 is executed.
  • step 102 if the received permission is not for the temporary C-RNTI (Temporary C-RNTI) on the PDCCH, and the NDI provided by the related HARQ information is compared with the value of the TB of this HARQ process during the previous transmission.
  • Temporal C-RNTI Temporal C-RNTI
  • the uplink grant is received from the PDCCH for CS-RNTI and the HARQ buffer of the identified HARQ process is empty (if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the HARQ information has been already toggled to the value in the previous transmission of this TB of this HARQ process; or if the uplink grant was received on PDCCH for the CS-RNTI and the processed steps of the HARQ identified 103
  • step 103 if the uplink grant is the configured uplink grant and there is at least one low-priority MAC PDU waiting to be transmitted in the HARQ buffer of the other HARQ process associated with the corresponding CG, then step 104 is performed; otherwise, step 105 is performed.
  • the low-priority MAC PDU waiting to be transmitted is obtained from the HARQ buffer area of the other HARQ process associated with the corresponding CG. If there are low-priority MAC PDUs waiting to be transmitted in the HARQ buffer of multiple HARQ processes, the low-priority MAC PDU waiting to be transmitted with the highest priority is obtained; if there are multiple low-priority MAC PDUs waiting to be transmitted priority If they are the same and the highest, one of them can be obtained arbitrarily or the low-priority MAC PDU waiting to be transmitted stored in the HARQ buffer with the smallest or largest HARQ process number.
  • a MAC PDU is obtained from the multiplexing and assembling entity for transmission (if any). the end.
  • step 103 can be replaced with the following steps to form another embodiment:
  • step 103 if the uplink grant is configured to configure the uplink grant and there is at least one low-priority MAC PDU waiting to be transmitted in the HARQ buffer area of other HARQ processes associated with the corresponding CG, and the low-priority MAC PDU waiting to be transmitted is If the priority is greater than (or greater than or equal to) the priority of the MAC PDU that can be obtained from the multiplexing and assembling entity, step 104 is executed; otherwise, step 105 is executed.
  • the priority of the low-priority MAC PDU waiting to be transmitted is the highest priority among the priorities of the multiple low-priority MAC PDUs waiting to be transmitted level.
  • the priority of the MAC PDU that can be obtained from the multiplexing and assembling entity can also be referred to as the priority of the uplink permission, which means that if the MAC PDU transmission is obtained from the multiplexing and assembling entity for the uplink permission, the obtained MAC PDU
  • the priority of the uplink grant or the priority determined by the MAC entity or an entity in the MAC entity that can be used to determine the priority of the MAC PDU, such as the process of determining the priority of the uplink grant).
  • step 103 before comparing the priority of the configured uplink license (that is, the priority of the MAC PDU that can be obtained from the multiplexing and assembling entity) and the priority of the low-priority MAC PDU waiting to be transmitted, it further includes the step 103a. Obtain the priority of configuring the uplink grant from the process of determining the priority of the uplink grant.
  • the base station schedules an uplink grant to transmit a low-priority MAC PDU waiting to be transmitted, but if the UE receives the uplink grant, But the HARQ buffer area of the HARQ process corresponding to the uplink grant is empty and/or the corresponding configuredGrantTimer (that is, the configuredGrantTimer of the corresponding HARQ process) is not running, then the uplink grant is used for new transmission (or transmission of new MAC PDU).
  • the corresponding HARQ process refers to the HARQ process corresponding to the received uplink grant or the HARQ process identified for the received uplink grant.
  • the condition in this embodiment if the HARQ buffer of the corresponding HARQ process is empty, is replaced with the condition if the corresponding configuredGrantTimer (that is, the configuredGrantTimer of the corresponding HARQ process) is not running, correspondingly, the corresponding HARQ process If the HARQ buffer area is not empty, it can be replaced with the configuredGrantTimer of the corresponding HARQ process that is running, so that a new embodiment can be formed.
  • the HARQ entity when the HARQ entity delivers the low-priority MAC PDU waiting for transmission to the corresponding HARQ process, it can start the configuredGrantTimer timer of the HARQ process.
  • Fig. 3 shows a flowchart of a method executed by a user equipment according to the third embodiment of the present invention.
  • the method executed by the user equipment UE includes: steps 201-203.
  • the PUCCH resource transmitted by the SR is related to the UL-SCH with a lower priority or the UL-SCH with a priority lower than (or lower than or equal to) the priority of the SR Overlap (optionally, it is also satisfied that a MAC PDU has been generated for the low-priority UL-SCH), triggering a low-priority MAC PDU indication, or after instructing the physical layer to signal the SR, triggering a low-priority MAC PDU instructions.
  • the priority of the SR is the priority of the logical channel that triggers the SR.
  • UL-SCH can also be replaced with PUSCH or uplink grant or MAC PDU.
  • the multiplexing and assembly entity can determine whether the configuredGrantTimer corresponding to a HARQ process (that is, the configuredGrantTimer of the corresponding HARQ process or the associated configuredGrantTimer) is running or whether there is waiting in the HARQ buffer of the HARQ process
  • the transmitted low-priority MAC PDU determines whether to carry a low-priority MAC PDU in the MAC PDU.
  • the MAC control element CE is used to indicate that the HARQ buffer of the HARQ process contains a low-priority MAC PDU waiting to be transmitted or decides whether to Low-priority MAC PDU indication MAC CE indicates that the HARQ buffer area of the HARQ process contains low-priority MAC PDUs waiting to be transmitted.
  • timer configuredGrantTimer that is, the configuredGrantTimer of the corresponding HARQ process or the associated configuredGrantTimer
  • a low-priority MAC is carried in the generated MAC PDU
  • the PDU indication MAC control element CE is used to indicate that the HARQ buffer area of the HARQ process contains a low priority MAC PDU waiting to be transmitted or the low priority MAC PDU carried in the generated MAC PDU.
  • the MAC CE indicates the HARQ of the HARQ process.
  • the buffer area contains low-priority MAC PDUs waiting to be transmitted.
  • the multiplexing and assembling entity can carry a low-priority MAC PDU indication in the generated MAC PDU.
  • the MAC control element CE is used to indicate a certain HARQ process (for example, a conflict occurs).
  • the HARQ buffer area of the HARQ process contains the low priority MAC PDU waiting to be transmitted or the low priority MAC PDU indication carried in the generated MAC PDU.
  • the HARQ buffer area indicating the HARQ process in the MAC CE contains the low priority waiting for transmission. Level MAC PDU.
  • the multiplexing and assembling entity is in the generated MAC PDU. Carry low priority MAC PDU to indicate the MAC control element CE.
  • the MAC entity When at least one SR is waiting to be sent (at least one SR is pending), for each SR waiting to be sent, the MAC entity performs the following operations:
  • step 201 if the MAC entity has a valid PUCCH resource configured for the SR waiting to be sent, it performs step 202 for the SR configuration corresponding to the SR waiting to be sent;
  • step 202 when the MAC entity has an SR transmission opportunity on the valid PUCCH resource configured for the SR (when the MAC entity has an SR transmission occurrence on the valid PUCCH resource for SR configured), and the SR-Prohibittimer has no SR transmission timing Running (if sr-ProhibitTimer is not running at the time of the SR transmission occasion), and the PUCCH resource transmitted by SR does not overlap with the measurement interval (if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap),
  • the PUCCH resource transmitted by the SR does not overlap with the UL-SCH with a higher priority or does not overlap with the UL-SCH with a priority higher than (or higher than or equal to) the priority of the SR, then step 203 is executed.
  • the priority of the UL-SCH refers to the priority of the MAC PDU corresponding to the UL-SCH.
  • UL-SCH can also be replaced with PUSCH or uplink grant or MAC PDU.
  • step 203 if SR_COUNTER is less than sr-TransMax, the value of SR_COUNTER increases by 1, and instructs the physical layer to send this SR (instruct the physical layer to signal the SR on one valid PUCCH resource for SR) on a valid PUCCH resource of the SR, Start the timer sr-ProhibitTimer. If the PUCCH resource transmitted by the SR overlaps with the UL-SCH with a lower priority or with the UL-SCH with a priority lower than (or lower than or equal to) the priority of the SR (optional, it is also satisfied that it is already a low priority The first UL-SCH generates MAC PDU), which triggers the low-priority MAC PDU indication.
  • the effective PUCCH resource refers to the PUCCH resource of the BWP activated at the time of SR transmission (PUCCH resources on a BWP which is active at the time of SR transmission occasion are considered valid).
  • Each SR configuration defines a timer sr-ProhibitTimer.
  • the value of the timer is configured by the gNB to the UE through RRC.
  • the sr-ProhibitTimer is the timer of the SR transmitted on the PUCCH.
  • Each SR configuration defines the maximum number of times a corresponding SR can be transmitted, sr-TransMax, and its value is configured by RRC.
  • Each SR configuration defines an SR_COUNTER to count the sent SRs.
  • the MAC entity sets the SR_COUNTER value of this SR configuration to 0.
  • the C-RNTI or CS-RNTI or TC-RNTI uplink grant of the MAC entity described in the embodiment of the present disclosure or the uplink grant of the C-RNTI or CS-RNTI or TC-RNTI of the MAC entity received on the PDCCH is Refers to the uplink grant indicated by the PDCCH scrambled by C-RNTI or CS-RNTI or TC-RNTI.
  • the priority of the dynamic permission can be indicated in its corresponding downlink control information DCI, and the priority of configuring the uplink permission can be configured by the base station through RRC signaling/message or in the downlink control information used to activate the configuration permission. Directed in DCI.
  • the MAC entity defines a process to determine the priority of the uplink grant to determine the priority of the uplink grant.
  • the priority of the uplink grant is whether it can be sent or reused or will be multiplexed or has been multiplexed (by multiplexing).
  • the highest priority of the logical channel corresponding to the data that the assembly process is executed according to the logical channel priority LCP process (that is, the priority of the logical channel with the highest priority corresponding to the contained data) or the MAC that can be generated for this uplink permission The priority of the PDU.
  • the priority of the MAC PDU may be the priority of the logical channel with the highest priority corresponding to the data contained in the MAC PDU. Conversely, if the priority of the uplink grant is indicated in the DCI or configured through RRC signaling (the base station configures the UE's uplink grant through RRC signaling), then the priority of the MAC PDU of the uplink grant is that of the corresponding uplink grant priority. For example, a MAC PDU contains data from logical channels LCH1, LCH2, and LCH3, where the priority of LCH3 is 2 and the highest, then the priority of the MAC PDU is 2.
  • the process of determining the uplink permission priority when receiving an instruction to obtain the uplink permission priority, determines the priority according to the logical channel priority LCP limitation (or the mapping restriction configured by RRC for each logical channel).
  • the priority of the logical channel with the highest priority corresponding to the data to be multiplexed, or the priority of the logical channel with the highest priority among the logical channels selected or preselected for the uplink permission is used as the priority of the uplink permission.
  • the priority of the uplink grant (the logical channel selected in the "process of determining the priority of the uplink grant" has data to be sent.
  • the priority of the corresponding uplink grant can be a preset The defined value is, for example, 0. It can also be that only MAC CE can send and no data and MAC CE can send different predefined values), and indicate to the uplink grant reception or HARQ entity. In addition, if the uplink grant reception has acquired/received the priority of a certain uplink grant, when the uplink grant reception submits the uplink grant to the HARQ entity, the priority of the uplink grant may also be submitted to the HARQ entity.
  • the HARQ entity For the HARQ entity, if the priority of a certain uplink license is received from the uplink grant, it may not obtain the priority of the uplink grant from the "process for determining the priority of uplink grant", but if it does not receive a certain uplink grant The priority of the uplink permission can be obtained from the "procedure for determining the priority of the uplink permission".
  • the priority of the uplink grant is also indicated to the HARQ process.
  • the uplink permission described in the embodiment of the present disclosure may be DG or CG.
  • the following describes related operations performed by the MAC entity on the low-priority MAC PDU indication.
  • the indication If the low-priority MAC PDU indication is triggered and not cancelled, and the MAC entity has uplink resources allocated for new transmission (in other words, the MAC entity can obtain the MAC PDU from the multiplexing and assembling entity), then the indication The multiplexing and assembling entity generates a low-priority MAC PDU indication MAC CE, and/or cancels the triggered low-priority MAC PDU indication.
  • the low-priority MAC PDU indication MAC CE may include information used to indicate the HARQ process number of the HARQ process identified by the low-priority configuration uplink grant identification for the occurrence of PUSCH duration overlap or include information used to indicate that the HARQ buffer is stored in the waiting area.
  • the information can be represented by a bitmap.
  • the length of the bitmap can be a fixed size (for example, one or two or more bytes) or a variable size. Each bit in the bitmap corresponds to one configured for the UE or the CG of the UE. A HARQ process number.
  • each bit of the bitmap from right to left (or from left to right) can be corresponded in sequence.
  • the Di field indicates whether low-priority MAC PDUs waiting to be transmitted are stored in the HARQ buffer of HARQ process i. i is the first in ascending order of the HARQ process number configured for the UE (or the CG of the UE).
  • the Di field is set to 1 to indicate that the HARQ buffer of HARQ process i stores low priority MAC PDUs waiting for transmission; the Di field is set to 0 to indicate that the HARQ buffer of HARQ process i does not store low priority MAC PDUs waiting for transmission Priority MAC PDU. You can also set the Di field to 1 to indicate that the HARQ buffer of HARQ process i does not store low-priority MAC PDUs waiting for transmission; setting the Di field to 0 indicates that the HARQ buffer of HARQ process i stores low-priority waiting for transmission.
  • MAC PDU indicates that the HARQ buffer of HARQ process i stores low-priority waiting for transmission.
  • the low-priority MAC PDU indication MAC CE may also include the HARQ process number of the low-priority MAC PDU waiting to be transmitted stored in the HARQ buffer area. This can be applied to at most one low-priority waiting to be transmitted at a time. The condition that the MAC PDU is stored in the buffer area.
  • bitmap in Figure 4 corresponds to the HARQ process number (or CG's HARQ process number) from small to large according to the bitmap bits from right to left, or the bitmap from left to right
  • the bits correspond to the HARQ process number (or the HARQ process number of the CG) from small to large one-to-one.
  • a low-priority MAC PDU waiting to be transmitted is sent (for example, it is delivered by the HARQ entity to the identified HARQ process and/or instructs the identified HARQ process to trigger a new transmission or retransmission), cancel the corresponding low-priority MAC PDU instructions.
  • the multiplexing and assembling entity includes the low-priority MAC PDU corresponding to the low-priority MAC PDU waiting to be transmitted in a MAC PDU indicating MAC CE or in low priority MAC PDU indication MAC CE indicates this low priority MAC PDU waiting to be transmitted or its corresponding HARQ process (or HARQ process number).
  • the method executed by the UE in the present disclosure may also be executed in the gNB.
  • Fig. 5 shows a block diagram of a user equipment UE50 according to an embodiment of the present invention.
  • the UE 50 includes a processor 510 and a memory 520.
  • the processor 510 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 520 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories.
  • the memory 520 stores program instructions. When the instruction is run by the processor 510, it can execute the foregoing method in the user equipment described in detail in the present invention.
  • 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 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 may 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 conditioners, 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

本发明提供一种由用户设备执行的方法以及用户设备。所述方法包括：识别上行许可所关联的混合自动重传请求HARQ进程；根据低优先级媒体访问控制协议数据单元MAC PDU指示，判断HARQ进程的HARQ缓存区中是否存储了等待传输的低优先级MAC PDU。由此，能够可靠地执行与存储在HARQ进程缓存区中的低优先级的MAC PDU有关的处理。

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)DG和配置许可CG之间以及两个或多个配置许可之间发生资源冲突的处理(即数据信道与数据信道冲突或上行共享信道UL-SCH之间的冲突)。据此，该工作项目的目的之一是在解决动态许可和配置许可之间以及两个或多个配置许可之间发生资源冲突方面进行增强，如果在媒体访问控制MAC(Medium Access Control)处理调度优先级，3GPP第二工作组(RAN2)需定义基于逻辑信道(LCH)优先级和逻辑信道优先级(LCP)限制的物理上行共享信道PUSCH(Physical Uplink Shared CHannel)调度优先级处理机制。
本公开解决重传保存在HARQ进程缓存区中的低优先级的MAC PDU所涉及的问题。
发明内容
本发明的目的在于，提供一种由用户设备执行的方法以及用户设备，能够可靠地执行与存储在HARQ进程缓存区中的低优先级的MAC PDU有关的处理。
根据本发明的第一方面，提供了一种由用户设备执行的方法，包括：识别上行许可所关联的混合自动重传请求HARQ进程；根据低优先级媒体访问控制协议数据单元MAC PDU指示，判断HARQ进程的HARQ缓存区中是否存储了等待传输的低优先级MAC PDU。
在上述方法中，可以是，在HARQ进程对应的定时器正在运行、HARQ进程的HARQ缓存区存在等待传输的低优先级MAC PDU、存在等待的低优先级MAC PDU指示中的任意一种情况下，复用和组装实体在生成的MAC PDU中携带低优先级MAC PDU指示MAC控制元素CE，利用该MAC CE指示所述HARQ进程的HARQ缓存区中存在等待传输的低优先级MAC PDU，或者复用和组装实体在生成的MAC PDU中携带的低优先级MAC PDU指示MAC CE中指示所述HARQ进程的HARQ缓存区中存在等待传输的低优先级MAC PDU。
在上述方法中，可以是，在等待发送的调度请求SR传输的物理上行控制信道PUCCH资源与优先级为所述SR的优先级以下的上行共享信道UL-SCH、物理上行共享信道PUSCH、上行许可中的任一者重叠且为重叠的UL-SCH、PUSCH、或上行许可生成了MAC PDU的情况下，触发低优先级MAC PDU指示。
在上述方法中，可以是，在所述重叠的情况下，当满足给定条件时，MAC实体在指示物理层发送所述SR后，触发低优先级MAC PDU指示。
在上述方法中，可以是，所述给定条件包括下述条件中的至少一项：MAC实体有为所述SR配置的有效PUCCH资源；MAC实体在为所述SR配置的有效PUCCH资源上具有SR传输时机；所述SR传输对应的定时器在SR传输时机未运行；所述SR传输的PUCCH资源不与测量间隔重叠；所述SR传输的PUCCH资源不与优先级高于所述SR的优先级的UL-SCH重叠。
在上述方法中，可以是，所述SR的优先级是触发该SR的逻辑信道的优先级。
在上述方法中，可以是，在低优先级MAC PDU指示被触发且没有被取消的情况下，当MAC实体能够从复用和组装实体获取MAC PDU时，指示复用和组装实体产生低优先级MAC PDU指示MAC CE和/或取消触发的低优先级MAC PDU指示。
在上述方法中，可以是，在所述低优先级MAC PDU指示MAC CE中，包含用于指示发生物理上行共享信道PUSCH持续时间重叠的低优先级配置上行许可识别的HARQ进程的HARQ进程号的信息，或者包含用于指示HARQ缓存区中存储了等待传输的低优先级MAC PDU的HARQ进程号信息。
在上述方法中，可以是，在等待传输的低优先级MAC PDU被发送的情况下，取消对应的低优先级MAC PDU指示。
根据本发明的第二方面，提供了一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行上述方法。
发明效果
根据本发明的由用户设备执行的方法以及用户设备，能够可靠地执行与存储在HARQ进程缓存区中的低优先级的MAC PDU有关的处理。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1示出了根据本发明实施例的由用户设备执行的方法的流程图。
图2示出了根据本发明实施例一的由用户设备执行的方法的流程图。
图3示出了根据本发明实施例三的由用户设备执行的方法的流程图。
图4示出了低优先级MAC PDU指示MAC CE的示意图。
图5示出了根据本发明实施例的用户设备的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，所述术语与3GPP协议当前最新版本中采用的术语相同，现摘录如下。
RRC：Radio Resource Control，无线资源控制。
MAC：Medium Access Control，媒体访问控制。
PDCCH：Physical Downlink Control Channel，物理下行控制信道。
PUCCH：Physical Uplink Control Channel，物理上行控制信道。
PUSCH：Physical Uplink Shared Channel，物理上行共享信道。
UL-SCH：Uplink Shared Channel，上行共享信道
SDU：Service Data Unit，服务数据单元。
PDU：Protocol Data Unit，协议数据单元。
SR：Scheduling Request，调度请求。
CG：Configured uplink Grant，配置许可。
UL Grant：上行许可。
configuredGrantTimer：这是一个定时器，定时器的初始值由基站通过RRC信令为UE的每个CG配置，其值是对应CG周期的若干倍。关于这个定时器的配置可以参见TS38.331中定义的信息元素configuredGrantTimer，这个定时器的启动和停止操作在TS38.321中描述。在本公开实施例中，增加了对这个定时器的其他启动或停止条件。
RNTI：Radio Network Temporary Identifier，无线网络临时标识。
CS-RNTI：Configured Scheduling RNTI，配置调度RNTI。
DG：Dynamic Grant，动态许可，是指在PDCCH上动态接收到的上行许可。换言之，PDCCH上接收到的为MAC实体的C-RNTI或TC-RNTI(Temporary C-RNTI)的上行许可或者PDCCH上接收到的为MAC实体的CS-RNTI的上行许可。为MAC实体的CS-RNTI的上行许可可以用于配置上行许可上传输的MAC PDU的重传，在这种情况下接收到的新数据指示(New Data Indicator，NDI)值为1认为NDI不翻转。所述PDCCH上接收到的为MAC实体的C-RNTI或TC-RNTI或CS-RNTI的上行许可是由MAC实体的C-RNTI或TC-RNTI或CS-RNTI加扰的PDCCH指示的上行许可，这两种表述可互换使用。
HARQ信息：HARQ information，DL-SCH或UL-SCH传输的HARQ信息由NDI、传输块大小(Transport Block size，TBS)、冗余版本(Redundancy Version，RV)以及HARQ进程号(HARQ process ID)组成。HARQ信息中还可能包含其他信息。
在2019年4月召开的3GPP RAN2#105bis次会议上达成：当配置多个配置许可CG或下行半静态调度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的情况。在RAN2#107次会议上达成：对于CG与CG冲突采用与CG与DG冲突相同的优先级方案(即都基于相同的确定优先级的方法)；新传(即为上行许可产生新的MAC PDU)与新传之间的资源冲突和新传与重传(即MAC PDU的重传)之间的资源冲突采用相同的优先级方案；PUSCH间发生冲突时对低优先级MAC PDU的恢复机制(即在发生冲突时，如何重传HARQ进程缓存区中保存的低优先级MAC PDU)也应用于PUSCH与调度请求SR冲突；当DG和CG发生冲突时，如果这两个调度的优先级相同(即为这两个上行许可的产生的MAC PDU的优先级或最高优先级相同)，那么认为为DG产生的MAC PDU的优先级更高(即MAC层指示物理层发送为DG产生的MAC PDU)；当两个上行许可发生冲突时，如果还没有为这两个上行许可产生MAC PDU，则仅为其中一个上行许可产生MAC PDU；如果用于传输SR的PUCCH与UL-SCH发生重叠， 则通过比较触发SR的逻辑信道的优先级与UL-SCH的优先级来确定是否发送SR，如果触发SR的逻辑信道优先级更高，则发送SR；如果SR在为UL-SCH产生MAC PDU之前且用于传输SR的PUCCH和MAC PDU的UL-SCH发生冲突(即两者不能同时传输)且UL-SCH的优先级较低，则不为UL-SCH产生MAC PDU。
本公开中，在一个服务小区上，某个HARQ进程上的上行许可(即动态许可DG或配置上行许可或UL-SCH)的PUSCH持续时间(duration)与SR(即SR的PUCCH或SR的PUCCH持续时间或发生SR的PUCCH或发送SR的PUCCH持续时间)发生冲突或重叠称为上行许可与SR冲突(换言之，UL-SCH或PUSCH与SR不能都发送或不能同时发送)。在一个服务小区上，某个HARQ进程上的动态许可DG的PUSCH持续时间与另一个HARQ进程上的配置许可CG的PUSCH持续时间重叠(overlap)称为DG/CG PUSCH冲突。在一个服务小区上，某个HARQ进程上的配置许可CG的PUSCH持续时间与另一个HARQ进程上的配置许可CG的PUSCH持续时间重叠称为CG/CG PUSCH冲突。DG/CG PUSCH冲突包括一个DG与多个不同HARQ进程上的CG间PUSCH持续时间冲突的情况。同样的，CG/CG PUSCH冲突也包含多个CG间PUSCH持续时间冲突的情况。如未特别说明，本公开实施例所述DG/CG或CG/CG冲突包括以上各类冲突，且所述冲突是指发生冲突的DG和CG以及发生冲突的两个或多个CG或SR均在同一个服务小区上。在本公开中，不同的上行许可发生PUSCH重叠(或冲突)或PUSCH与SR重叠(或冲突)可以是不同的上行许可在时域上重叠，换言之它们不能都发送或不能同时发送。
如果为发生了DG/CG或CG/CG冲突或上行许可与SR冲突的CG产生了MAC PDU且所述MAC PDU被存储在对应HARQ进程(即CG对应的HARQ进程或为CG识别的HARQ进程)的HARQ缓存区中没有传输(例如因其优先级较低)，所述没有传输可以是没有指示给物理层，或已经指示给物理层但因与优先级更高的MAC PDU或SR冲突而没有传输或传输被中断或没有在对应的上行许可上传输。在本公开实施例中，将为所述CG产生的MAC PDU称为等待传输的低优先级MAC PDU(deprioritized MAC PDU)。本公开中存储在一个HARQ进程的HARQ缓存区中等待传输的低优先级 MAC PDU只有在没有在任何上行许可上发送或发送完成时，才认为是等待传输的低优先级MAC PDU，才可以在同一CG的其他HARQ进程上传输。当用于发送等待传输的低优先级MAC PDU的PUSCH持续时间不与其他PUSCH持续时间或SR重叠或者虽然重叠但等待传输的低优先级MAC PD的优先级更高(prioritized)时，认为所述等待传输的低优先级MAC PDU已经在上行许可上发送或发送完成，则它不再是等待传输的低优先级MAC PDU。此外，还可以对等待传输的低优先级MAC PDU进一步的限制，如果存储等待传输的低优先级MAC PDU的HARQ缓存区对应的HARQ进程的configuredGrantTimer(或其所关联的configuredGrantTimer)正在运行，则所述MAC PDU才是等待传输的低优先级MAC PDU。此外，对于HARQ缓存区中存储了等待传输的低优先级MAC PDU的HARQ进程，如果configuredGrantTimer期满，则可以清空HARQ缓存区或删除等待传输的低优先级MAC PDU。在MAC实体或HARQ实体确定一个CG的其他HARQ进程中是否存储了等待传输的低优先级MAC PDU时，可以仅判断configuredGrantTimer正在运行的HARQ进程的HARQ缓存区是否存储了等待传输的低优先级MAC PDU。本公开实施例中所述等待传输的低优先级MAC PDU也可以称为有效的等待传输的低优先级MAC PDU。
优选的，可以为每个CG的每个HARQ进程设置一个等待传输的低优先级MAC PDU指示标识，其初始值可以设置为FALSE或假或0或其他预定义的值。当一个CG的某个HARQ进程的HARQ缓存区中保存了等待传输的低优先级MAC PDU，则置等待传输的低优先级MAC PDU指示标识为TRUE或真或1或其他预定义的值。例如，当有可用的上行许可(例如在MAC实体的C-RNTI或临时C-RNTI的PDCCH上接收到一个上行许可)时，如果该上行许可与另一个上行许可(这个上行许可的优先级较低)的PUSCH持续时间冲突且该上行许可的优先级更高，如果已经为优先级较低的上行许可生成了MAC PDU，则置为低优先级的上行许可识别的(或对应的)HARQ进程的等待传输的低优先级MAC PDU指示标识为TRUE或真或1或其他预定义的值。当某个等待传输的低优先级MAC PDU被发送后，置等待传输的低优先级MAC PDU指示标识为FALSE或假或0或其他预定义的值。如果为每个CG的每个HARQ进程设置一个等待传输的低优先级MAC PDU指示标识，则判断是否存在等待传输的低优先级MAC PDU就可 以通过判断CG的各个HARQ进程的等待传输的低优先级MAC PDU指示标识取值是否为TRUE或真或1或其他预定义的值实现。
图1示出了根据本发明实施例的由用户设备执行的方法的流程图。
如图1所示，本发明的用户设备UE执行的方法包括：步骤S1和步骤S2。在步骤S1中，识别上行许可所关联的HARQ进程。
在步骤S2中，根据低优先级MAC PDU指示，判断HARQ进程的HARQ缓存区中是否存储了等待传输的低优先级MAC PDU。
根据上述方法，能够可靠地执行与存储在HARQ进程缓存区中的低优先级的MAC PDU有关的处理。
以下描述发送所述等待传输的低优先级MAC PDU的实施例。
实施例一
图2示出了根据本发明实施例一的由用户设备执行的方法的流程图。
如图2所示，在本发明的实施例一中，用户设备UE执行的步骤包括：步骤101～105。
在实施例一中，利用同一CG随后的配置上行许可传输所述等待传输的低优先级MAC PDU。具体的，对于每个上行许可，HARQ实体执行以下操作：
在步骤101，识别所述上行许可关联的HARQ进程，且对于每个识别的HARQ进程，执行步骤102。
在步骤102，如果接收到的许可不是针对PDCCH上的临时C-RNTI(Temporary C-RNTI)，并且由相关的HARQ信息提供的NDI与这个HARQ进程的TB在先前传输时的值相比发生了翻转，或者如果上行许可接收自针对CS-RNTI的PDCCH且所识别的HARQ进程的HARQ缓存区为空(ifthe 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；or if the uplink grant was received on PDCCH for the CS-RNTI and the HARQ buffer of the identified process is empty)，执行步骤103。
在步骤103，如果上行许可是配置上行许可并且其对应的CG所关联的 其他HARQ进程的HARQ缓存区中至少有一个等待传输的低优先级MAC PDU，则执行步骤104，否则，执行步骤105。
在步骤104，从对应的CG所关联的其他HARQ进程的HARQ缓存区中获取等待传输的低优先级MAC PDU。如果有多个HARQ进程的HARQ缓存区中存在等待传输的低优先级MAC PDU，则获取优先级最高的等待传输的低优先级MAC PDU；如果有多个等待传输的低优先级MAC PDU优先级相同且最高，则可以从中任意获取一个或从中获取HARQ进程号最小或最大的HARQ缓存区中存储的等待传输的低优先级MAC PDU。可选的，停止所获取的等待传输的低优先级MAC PDU所对应的(或所来自的)HARQ进程的定时器configuredGrantTimer。可选的，清空所获取的等待传输的低优先级MAC PDU所对应的(或所来自的)HARQ进程的HARQ缓存区。结束。
在步骤105，从复用和组装实体获取MAC PDU用于传输(如果存在)。结束。
需要说明的是，步骤103可以替换为以下步骤，从而形成另一个实施例：
在步骤103，如果上行许可是配置上行许可并且对应的CG所关联的其他HARQ进程的HARQ缓存区中至少有一个等待传输的低优先级MAC PDU，且所述等待传输的低优先级MAC PDU的优先级大于(或大于或等于)可以从复用和组装实体获取的MAC PDU的优先级，则执行步骤104，否则，执行步骤105。需要说明的是，如果有多个等待传输的低优先级MAC PDU，则等待传输的低优先级MAC PDU的优先级是所述多个等待传输的低优先级MAC PDU的优先级中的最高优先级。在本公开实施例中，可以规定数值越小优先级越高，数值越大优先级越低，也可以规定数值越大优先级越高，数值越小优先级越低。
所述可以从复用和组装实体获取的MAC PDU的优先级也可称为上行许可的优先级，是指如果从复用和组装实体为该上行许可获取MAC PDU传输，所述获取的MAC PDU的优先级或者所述上行许可被MAC实体(或MAC实体中的可用于确定MAC PDU的优先级的实体，例如决定上行许可优先级过程)确定的优先级。可选的，步骤103中，在比较配置上行许可的优先级(即可以从复用和组装实体获取的MAC PDU的优先级)和等待 传输的低优先级MAC PDU的优先级之前，还包含步骤103a，从决定上行许可优先级过程获取配置上行许可的优先级。
实施例二
在实施例二中，当发生DG/CG或CG/CG冲突或上行许可与SR冲突时，基站调度上行许可用于传输等待传输的低优先级MAC PDU，但是如果UE接收到所述上行许可，但所述上行许可对应的HARQ进程的HARQ缓存区为空和/或对应的定时器configuredGrantTimer(即对应的HARQ进程的configuredGrantTimer)没有运行，则将所述上行许可用于新传(或传输新的MAC PDU)。
具体的，如果已经在MAC实体的CS-RNTI的PDCCH上接收到一个服务小区的针对该PDCCH时机(occation)的上行许可(if an uplink grant for this PDCCH occation has been received for the Serving Cell on the PDCCH for the MAC entities’s CS-RNTI)，如果接收到的HARQ信息中包含的NDI值为1且如果对应的HARQ进程的HARQ缓存区为空，则认为对应HARQ进程的NDI发生了翻转(toggled)，否则(即如果接收到的HARQ信息中包含的NDI值为1且如果对应的HARQ进程的HARQ缓存区不为空)，则认为对应HARQ进程的NDI没有翻转(toggled)。需要说明的是，所述对应的HARQ进程是指所述接收到的上行许可对应的HARQ进程或为所述接收到的上行许可识别的HARQ进程。此外，如果将本实施例中的条件如果对应的HARQ进程的HARQ缓存区为空替换为条件如果对应的定时器configuredGrantTimer(即对应的HARQ进程的configuredGrantTimer)没有运行，相应的，对应的HARQ进程的HARQ缓存区不为空可以替换为对应的HARQ进程的定时器configuredGrantTimer正在运行，这样可以形成一个新的实施例。还可以将本实施例中的条件如果对应的HARQ进程的HARQ缓存区为空替换为条件如果对应的HARQ进程的HARQ缓存区为空且对应的定时器configuredGrantTimer(即对应的HARQ进程的configuredGrantTimer或关联的configuredGrantTimer)没有运行，这样可以形成另一个新的实施例。
在本公开中，当HARQ实体将等待传输的低优先级MAC PDU交付(deliver)给相应的HARQ进程时，可以启动该HARQ进程的定时器 configuredGrantTimer。
实施例三
图3示出了根据本发明实施例三的由用户设备执行的方法的流程图。
如图3所示，在本发明的实施例三中，用户设备UE执行的方法包括：步骤201～203。
在实施例三中，在本实施例中，当SR传输的PUCCH资源与优先级更低的UL-SCH或与优先级低于(或低于或等于)所述SR的优先级的UL-SCH重叠(可选的，还满足已经为低优先级的UL-SCH生成了MAC PDU)，触发低优先级MAC PDU指示，或者在指示物理层发送(signal)所述SR后，触发低优先级MAC PDU指示。优选的，SR的优先级是触发该SR的逻辑信道的优先级。本实施例中，UL-SCH也可以替换为PUSCH或上行许可或MAC PDU。
复用和组装实体(Multiplexing and Assembly Entity)可以通过判断某个HARQ进程对应的定时器configuredGrantTimer(即对应的HARQ进程的configuredGrantTimer或关联的configuredGrantTimer)是否正在运行或该HARQ进程的HARQ缓存区是否存在等待传输的低优先级MAC PDU来决定是否在MAC PDU中携带一个低优先级MAC PDU指示MAC控制元素CE用来指示该HARQ进程的HARQ缓存区中包含等待传输的低优先级MAC PDU或决定是否在低优先级MAC PDU指示MAC CE中指示该HARQ进程的HARQ缓存区中包含等待传输的低优先级MAC PDU。如果定时器configuredGrantTimer(即对应的HARQ进程的configuredGrantTimer或关联的configuredGrantTimer)正在运行或该HARQ进程的HARQ缓存区存在等待传输的低优先级MAC PDU，则在生成的MAC PDU中携带一个低优先级MAC PDU指示MAC控制元素CE用来指示该HARQ进程的HARQ缓存区中包含等待传输的低优先级MAC PDU或在生成的MAC PDU中携带的低优先级MAC PDU指示MAC CE中指示该HARQ进程的HARQ缓存区中包含等待传输的低优先级MAC PDU。
如果存在正在等待(pending)的低优先级MAC PDU指示，复用和组装实体可以在生成的MAC PDU中携带一个低优先级MAC PDU指示MAC控制元素CE用来指示某个HARQ进程(例如发生冲突的HARQ进程)的 HARQ缓存区中包含等待传输的低优先级MAC PDU或在生成的MAC PDU携带的低优先级MAC PDU指示MAC CE中指示该HARQ进程的HARQ缓存区中包含等待传输的低优先级MAC PDU。
需要说明的是，在本公开中，只有存在需要指示的等待传输的低优先级MAC PDU或存在正在等待(pending)的低优先级MAC PDU指示，复用和组装实体才在生成的MAC PDU中携带低优先级MAC PDU指示MAC控制元素CE。
下面具体描述本实施例。
当至少有一个SR等待发送(at least one SR is pending)时，对每个等待发送的SR，MAC实体执行以下操作：
在步骤201，如果MAC实体有为这个等待发送的SR配置的有效PUCCH资源，则对这个等待发送的SR对应的SR配置，执行步骤202；
在步骤202，对于当MAC实体在为SR配置的有效PUCCH资源上具有SR传输时机(when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured)，并且sr-Prohibittimer在SR传输时机未运行(if sr-ProhibitTimer is not running at the time of the SR transmission occasion)，并且SR传输的PUCCH资源不与测量间隔重叠(if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap)，并且SR传输的PUCCH资源不与优先级更高的UL-SCH重叠或不与优先级高于(或高于或等于)SR的优先级的UL-SCH重叠，则执行步骤203。其中，UL-SCH的优先级是指UL-SCH对应的MAC PDU的优先级。本实施例中，UL-SCH也可以替换为PUSCH或上行许可或MAC PDU。
在步骤203，如果SR_COUNTER小于sr-TransMax，SR_COUNTER的值增加1，并指示物理层在SR的一个有效PUCCH资源上发送这个SR(instruct the physical layer to signal the SR on one valid PUCCH resource for SR)，启动定时器sr-ProhibitTimer。如果SR传输的PUCCH资源与优先级更低的UL-SCH或与优先级低于(或低于或等于)所述SR的优先级的UL-SCH重叠(可选的，还满足已经为低优先级的UL-SCH生成了MAC PDU)，触发低优先级MAC PDU指示。
有效PUCCH资源是指在SR传输时机时激活的BWP的PUCCH资源 (PUCCH resources on a BWP which is active at the time of SR transmission occasion are considered valid)。
每个SR配置定义一个定时器sr-ProhibitTimer，定时器的值由gNB通过RRC配置给UE，sr-ProhibitTimer是在PUCCH上传输的SR的定时器。
每个SR配置定义一个对应的SR可传输的最大次数sr-TransMax，其值通过RRC配置。
每个SR配置定义一个SR_COUNTER用于对已发送的SR进行计数。当一个SR被触发并且对于同一SR配置没有其他等待的SR，MAC实体将这个SR配置的SR_COUNTER的值为0。
本公开实施例中所述为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中指示。
在另一个实施例中，MAC实体中定义一个决定上行许可优先级过程来确定上行许可的优先级，上行许可的优先级是可发送或可复用或将要复用或已复用(由复用和组装过程根据逻辑信道优先级LCP过程执行)的数据对应的逻辑信道的最高优先级(即所包含的数据对应的优先级最高的那个逻辑信道的优先级)或可为这个上行许可产生的MAC PDU的优先级。
MAC PDU的优先级可以是MAC PDU包含的数据对应的优先级最高的逻辑信道的优先级。反之，如果上行许可的优先级是在DCI中指示或通过RRC信令配置(由基站通过RRC信令为UE的上行许可配置)，则该上行许可的MAC PDU的优先级是对应的上行许可的优先级。例如，MAC PDU中包含来自逻辑信道LCH1、LCH2、LCH3的数据，其中LCH3的优先级为2且最高，则该MAC PDU的优先级为2。
决定上行许可优先级过程(例如复用与组装过程)在接收到获取上行许可优先级的指示时，根据逻辑信道优先级LCP的限定条件(或RRC为每个逻辑信道配置的映射限制)确定该上行许可可发送或可复用或将要复用 的数据对应的优先级最高的逻辑信道的优先级，或者将为该上行许可选择或预选的逻辑信道中优先级最高的逻辑信道的优先级作为该上行许可的优先级(“决定上行许可优先级过程”所选择的逻辑信道中有可发送数据，如果根据LCP规则所有逻辑信道都没有数据可发送，则可为对应上行许可的优先级为一个预定义的值，例如为0。也可以为只有MAC CE可发送和没有数据和MAC CE可发送分别预定义不同的值)，并指示给上行许可接收或HARQ实体。此外，如果上行许可接收获取了/接收到了某个上行许可的优先级，在上行许可接收将该上行许可递交给HARQ实体时，可以将该上行许可的优先级也递交给HARQ实体。对于HARQ实体来说，如果从上行许可接收收到了某个上行许可的优先级，那么可以不向“决定上行许可优先级过程”获取该上行许可的优先级，但如果没有收到某个上行许可的优先级，那么可以向“决定上行许可优先级过程”获取该上行许可的优先级。可选的，HARQ实体在将上行许可递交给HARQ进程时，将该上行许可的优先级也指示给HARQ进程。
如未特别说明，本公开实施例所述上行许可可以是DG或CG。
以下描述所述MAC实体对低优先级MAC PDU指示执行的相关操作。
如果低优先级MAC PDU指示被触发且没有被取消，并且MAC实体有被分配用于新传(new Transmission)的上行资源(换言之，MAC实体可以从复用和组装实体获取MAC PDU)，则指示复用和组装实体产生低优先级MAC PDU指示MAC CE，和/或取消触发的低优先级MAC PDU指示。
所述低优先级MAC PDU指示MAC CE中可以包含用于指示发生PUSCH持续时间重叠的低优先级配置上行许可识别的HARQ进程的HARQ进程号的信息或包含用于指示HARQ缓存区中存储了等待传输的低优先级MAC PDU的HARQ进程号信息。所述信息可以用位图表示，位图的长度可以是固定大小(例如一个或两个或多个字节)或者大小可变，位图中的每位对应一个为UE或UE的CG配置的一个HARQ进程号。可以按照CG配置的HARQ进程号由低到高依次对应位图从右到左(或从左到右)的各个比特。如图4所示，Di域指示HARQ进程i的HARQ缓存区中是否存储了等待传输的低优先级MAC PDU，i是按照为UE(或UE的CG)配置的HARQ进程号的升序排列的第i个HARQ进程；Di域置为1表示HARQ进 程i的HARQ缓存区中存储了等待传输的低优先级MAC PDU；Di域置为0表示HARQ进程i的HARQ缓存区中没有存储等待传输的低优先级MAC PDU。也可以将Di域置为1表示HARQ进程i的HARQ缓存区中没有存储等待传输的低优先级MAC PDU；Di域置为0表示HARQ进程i的HARQ缓存区中存储了等待传输的低优先级MAC PDU。备选的，所述低优先级MAC PDU指示MAC CE也可以包含HARQ缓存区中存储了等待传输的低优先级MAC PDU的HARQ进程号，这可以应用于每次最多只有一个等待传输的低优先级MAC PDU存储在缓存区中的情况。
需要说明的是，图4中位图是按照从右向左将位图比特与HARQ进程号(或CG的HARQ进程号)从小到大一一对应，也可以按照从左到右将将位图比特与HARQ进程号(或CG的HARQ进程号)从小到大一一对应。
当某个等待传输的低优先级MAC PDU被发送(例如，被HARQ实体交付给识别出的HARQ进程和/或指示识别出的HARQ进程触发新传或重传)，取消对应的低优先级MAC PDU指示。
只有某个等待传输的低优先级MAC PDU没有传输过时，复用和组装实体才在一个MAC PDU中包含这个等待传输的低优先级MAC PDU对应的低优先级MAC PDU指示MAC CE或在低优先级MAC PDU指示MAC CE中指示这个等待传输的低优先级MAC PDU或其对应的HARQ进程(或HARQ进程号)。
需要说明的是，本公开中UE执行的方法也可以在gNB中执行。
图5示出了根据本发明实施例的用户设备UE50的框图。如图5所示，UE50包括处理器510和存储器520。处理器510例如可以包括微处理器、微控制器、嵌入式处理器等。存储器520例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器520上存储有程序指令。该指令在由处理器510运行时，可以执行本发明详细描述的用户设备中的上述方法。
运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取 存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备执行的方法，包括：
    识别上行许可所关联的混合自动重传请求HARQ进程；
    根据低优先级媒体访问控制协议数据单元MAC PDU指示，判断HARQ进程的HARQ缓存区中是否存储了等待传输的低优先级MAC PDU。
  2. 根据权利要求1所述的方法，其中，
    在HARQ进程对应的定时器正在运行、HARQ进程的HARQ缓存区存在等待传输的低优先级MAC PDU、存在等待的低优先级MAC PDU指示中的任意一种情况下，
    复用和组装实体在生成的MAC PDU中携带低优先级MAC PDU指示MAC控制元素CE，利用该MAC CE指示所述HARQ进程的HARQ缓存区中存在等待传输的低优先级MAC PDU，或者
    复用和组装实体在生成的MAC PDU中携带的低优先级MAC PDU指示MAC CE中指示所述HARQ进程的HARQ缓存区中存在等待传输的低优先级MAC PDU。
  3. 根据权利要求1所述的方法，其中，
    在等待发送的调度请求SR传输的物理上行控制信道PUCCH资源与优先级为所述SR的优先级以下的上行共享信道UL-SCH、物理上行共享信道PUSCH、上行许可中的任一者重叠且为重叠的UL-SCH、PUSCH、或上行许可生成了MAC PDU的情况下，触发低优先级MAC PDU指示。
  4. 根据权利要求3所述的方法，其中，
    在所述重叠的情况下，当满足给定条件时，MAC实体在指示物理层发送所述SR后，触发低优先级MAC PDU指示。
  5. 根据权利要求4所述的方法，其中，
    所述给定条件包括下述条件中的至少一项：
    MAC实体有为所述SR配置的有效PUCCH资源；
    MAC实体在为所述SR配置的有效PUCCH资源上具有SR传输时机；
    所述SR传输对应的定时器在SR传输时机未运行；
    所述SR传输的PUCCH资源不与测量间隔重叠；
    所述SR传输的PUCCH资源不与优先级高于所述SR的优先级的UL-SCH重叠。
  6. 根据权利要求3所述的方法，其中，
    所述SR的优先级是触发该SR的逻辑信道的优先级。
  7. 根据权利要求1所述的方法，其中，
    在低优先级MAC PDU指示被触发且没有被取消的情况下，当MAC实体能够从复用和组装实体获取MAC PDU时，指示复用和组装实体产生低优先级MAC PDU指示MAC CE和/或取消触发的低优先级MAC PDU指示。
  8. 根据权利要求7所述的方法，其中，
    在所述低优先级MAC PDU指示MAC CE中，包含用于指示发生物理上行共享信道PUSCH持续时间重叠的低优先级配置上行许可识别的HARQ进程的HARQ进程号的信息，或者包含用于指示HARQ缓存区中存储了等待传输的低优先级MAC PDU的HARQ进程号信息。
  9. 根据权利要求1所述的方法，其中，
    在等待传输的低优先级MAC PDU被发送的情况下，取消对应的低优先级MAC PDU指示。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
PCT/CN2020/118361 2019-09-30 2020-09-28 由用户设备执行的方法以及用户设备 WO2021063305A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910939588.XA CN112584530A (zh) 2019-09-30 2019-09-30 由用户设备执行的方法以及用户设备
CN201910939588.X 2019-09-30

Publications (1)

Publication Number Publication Date
WO2021063305A1 true WO2021063305A1 (zh) 2021-04-08

Family

ID=75116141

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/118361 WO2021063305A1 (zh) 2019-09-30 2020-09-28 由用户设备执行的方法以及用户设备

Country Status (2)

Country Link
CN (1) CN112584530A (zh)
WO (1) WO2021063305A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220361191A1 (en) * 2019-10-02 2022-11-10 Sony Group Corporation Communications device, infrastructure equipment and methods

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115696598A (zh) * 2021-07-28 2023-02-03 中国移动通信有限公司研究院 Ndi确定方法、装置、终端及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019098663A1 (en) * 2017-11-14 2019-05-23 Lg Electronics Inc. Method and apparatus for deprioritizing duplicated packet transmission in wireless communication system
WO2019156528A1 (en) * 2018-02-12 2019-08-15 Lg Electronics Inc. Method and apparatus for deprioritizing packet transmission based on reliability level or congestion level in wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019098663A1 (en) * 2017-11-14 2019-05-23 Lg Electronics Inc. Method and apparatus for deprioritizing duplicated packet transmission in wireless communication system
WO2019156528A1 (en) * 2018-02-12 2019-08-15 Lg Electronics Inc. Method and apparatus for deprioritizing packet transmission based on reliability level or congestion level in wireless communication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Handling of de-prioritized MAC PDUs", 3GPP DRAFT; R2-1909375 HANDLING OF DE-PRIORITIZED MAC PDUS, vol. RAN WG2, 15 August 2019 (2019-08-15), Prague, Czech, pages 1 - 5, XP051767175 *
HUAWEI, HISILICON: "Handling of de-prioritized MAC PDU due to intra-UE prioritization", 3GPP DRAFT; R2-1910363, vol. RAN WG2, 16 August 2019 (2019-08-16), Prage, CZ, pages 1 - 3, XP051768142 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220361191A1 (en) * 2019-10-02 2022-11-10 Sony Group Corporation Communications device, infrastructure equipment and methods

Also Published As

Publication number Publication date
CN112584530A (zh) 2021-03-30

Similar Documents

Publication Publication Date Title
WO2021063307A1 (zh) 由用户设备执行的方法以及用户设备
TWI716803B (zh) 一種進行混合自動重送請求回饋的方法和終端
CN112913309B (zh) 抢占上行链路资源的分配
WO2020094107A1 (zh) 发送数据的方法、发送数据的装置、以及终端设备
WO2021022907A1 (zh) 数据传输方法、装置及存储介质
RU2754679C2 (ru) Система, устройство и способ передачи данных
US11039302B2 (en) Base station, user equipment, and associated method
CN112567661A (zh) 用于以不同可靠性传递数据的方法、系统和设备
CN116095872B (zh) 无线通信设备
WO2017024912A1 (zh) 一种随机接入方法、设备和系统
JP2013179643A (ja) 無線アクセス網での半永久的割り当てとダイナミック割り当てとの衝突を回避する方法
WO2021063305A1 (zh) 由用户设备执行的方法以及用户设备
TWI777392B (zh) 考量組配授權計時器之彈性資料傳輸方法及設備以及關聯之電腦可讀媒體
WO2019062641A1 (zh) 无线通信方法和设备
US20220264595A1 (en) User equipment, base station, and method thereof
US20220353899A1 (en) User equipment, base station, and method thereof
WO2018121643A1 (zh) 一种数据传输方法、装置及系统
WO2018201929A1 (zh) 用于处理调度请求的方法和设备
EP3668226A1 (en) Base station, user equipment, and related method
WO2021204080A1 (zh) 用户设备、基站及其方法
WO2021139673A1 (zh) 由用户设备执行的方法以及用户设备
WO2019062760A1 (zh) 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质
US20220217787A1 (en) Random access method and user equipment
WO2016112512A1 (zh) Mac控制元素的上行配置方法、装置以及通信系统
WO2019015513A1 (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: 20871789

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: 20871789

Country of ref document: EP

Kind code of ref document: A1