WO2023272456A1 - Transmission d'autorisation configurée - Google Patents

Transmission d'autorisation configurée Download PDF

Info

Publication number
WO2023272456A1
WO2023272456A1 PCT/CN2021/102877 CN2021102877W WO2023272456A1 WO 2023272456 A1 WO2023272456 A1 WO 2023272456A1 CN 2021102877 W CN2021102877 W CN 2021102877W WO 2023272456 A1 WO2023272456 A1 WO 2023272456A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
terminal device
predetermined condition
harq
configured grant
Prior art date
Application number
PCT/CN2021/102877
Other languages
English (en)
Inventor
Ping-Heng Kuo
Chunli Wu
Original Assignee
Nokia Shanghai Bell Co., Ltd.
Nokia Solutions And Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co., Ltd., Nokia Solutions And Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co., Ltd.
Priority to CN202180099912.7A priority Critical patent/CN117581494A/zh
Priority to PCT/CN2021/102877 priority patent/WO2023272456A1/fr
Publication of WO2023272456A1 publication Critical patent/WO2023272456A1/fr

Links

Images

Classifications

    • 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

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to devices, methods, apparatus and computer readable storage media for configured grant (CG) transmission.
  • CG configured grant
  • enhanced mobile broadband eMBB
  • massive machine type communication mMTC
  • ultra-reliable and low latency communication URLLC
  • 5G NR has introduced CG transmissions to provide low latency transmission opportunities.
  • a communication device may be configured to use the CG resources to transmit transport blocks (TBs) without a dynamic UL grant.
  • TBs transport blocks
  • periodic transmission occasions are available for communication devices (such, as, UE) for use in uplink transmissions.
  • the communication device may use multiple HARQ processes for initial transmissions or retransmissions of different TBs.
  • the terminal device may determine a HARQ process for transmission on the CG.
  • example embodiments of the present disclosure provide a solution for CG transmission. Embodiments that do not fall under the scope of the claims, if any, are to be interpreted as examples useful for understanding various embodiments of the disclosure.
  • a terminal device comprising: at least one processor; and at least one memory including computer program codes.
  • the at least one memory and the computer program codes are configured to, with the at least one processor, cause the terminal device to: upon determining a Hybrid Automatic Repeat Request (HARQ) process for a configured grant, determine whether a configured grant timer associated with the HARQ process is running or activated; in accordance with a determination that the configured grant timer is running or activated, determine whether a predetermined condition related to content of a protocol data unit (PDU) stored in a buffer for the HARQ process is met; and in accordance with a determination that the predetermined condition is met, deliver the configured grant and at least one associated HARQ information to a HARQ entity of the terminal device.
  • HARQ Hybrid Automatic Repeat Request
  • a terminal device comprising: at least one processor; and at least one memory including computer program codes.
  • the at least one memory and the computer program codes are configured to, with the at least one processor, cause the terminal device to: deprioritize a first configured grant associated with a Hybrid Automatic Repeat Request (HARQ) process for a first packet data unit (PDU) ; determine whether a predetermined condition related to content of the first PDU is met; and in accordance with a determination that the predetermined condition is met, refrain from conducting an autonomous transmission of the first PDU to a network device.
  • HARQ Hybrid Automatic Repeat Request
  • a method comprising: upon determining a Hybrid Automatic Repeat Request (HARQ) process for a configured grant, determining whether a configured grant timer associated with the HARQ process is running or activated; in accordance with a determination that the configured grant timer is running or activated, determining whether a predetermined condition related to content of a protocol data unit (PDU) stored in a buffer for the HARQ process is met; and in accordance with a determination that the predetermined condition is met, delivering the configured grant and at least one associated HARQ information to a HARQ entity of the terminal device.
  • HARQ Hybrid Automatic Repeat Request
  • a method comprises: deprioritizing a first configured grant associated with a Hybrid Automatic Repeat Request (HARQ) process for a first protocol data unit (PDU) ; determining whether a predetermined condition related to content of the first PDU is met; and in accordance with a determination that the predetermined condition is met, refraining from conducting an autonomous transmission of the first PDU to a network device.
  • HARQ Hybrid Automatic Repeat Request
  • a first apparatus comprises: means for upon determining a Hybrid Automatic Repeat Request (HARQ) process for a configured grant, determining whether a configured grant timer associated with the HARQ process is running or activated; means for in accordance with a determination that the configured grant timer is running or activated, determining whether a predetermined condition related to content of a protocol data unit (PDU) stored in a buffer for the HARQ process is met; and means for in accordance with a determination that the predetermined condition is met, delivering the configured grant and at least one associated HARQ information to a HARQ entity of the terminal device.
  • HARQ Hybrid Automatic Repeat Request
  • a second apparatus comprises: means for means for deprioritizing a first configured grant associated with a Hybrid Automatic Repeat Request (HARQ) process for a first protocol data unit (PDU) ; means for means for determining whether a predetermined condition related to content of the first PDU is met; and means for in accordance with a determination that the predetermined condition is met, refraining from conducting an autonomous transmission of the first PDU to a network device.
  • HARQ Hybrid Automatic Repeat Request
  • a non-transitory computer readable medium comprises program instructions for causing an apparatus to perform the method according to the third aspect.
  • non-transitory computer readable medium comprises program instructions for causing an apparatus to perform the method according to the fourth aspect
  • FIG. 1 illustrates an example communication network in which example embodiments of the present disclosure can be implemented
  • FIG. 2 shows a schematic diagram of UCI multiplexing according to some example embodiments of the present disclosure
  • FIG. 3 illustrates a flowchart of an example method for CG transmission implemented at a terminal device according to example embodiments of the present disclosure
  • FIG. 4 illustrates a flowchart of an example method for CG transmission implemented at a terminal device according to example embodiments of the present disclosure
  • FIG. 5 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
  • FIG. 6 illustrates a block diagram of an example computer readable medium in accordance with example embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • suitable generation communication protocols including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and
  • radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node.
  • An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
  • IAB-MT Mobile Terminal
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/
  • the terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) .
  • MT Mobile Termination
  • IAB node e.g., a relay node
  • the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
  • resource may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.
  • a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
  • CG also called “CG resource, ” may refer to resource (s) configured to device (s) for transmission without a dynamic UL grant.
  • CG resource and “CG” are used interchangeably herein.
  • a communication device e.g., a terminal device
  • the communication device is able to reduce signaling overhead and latency relative to a grant-based UL transmission. In some cases, for example, if the communication device does not have any user data to transmit the communication device configured with the CG may skip the UL transmission.
  • the terminal device may determine the HARQ process identity (ID) for each transmission based on time parameters, such as system frame number (SFN) , subframe or symbol numbers, and so on. Hence, the HARQ process IDs for different CG occasions may be different.
  • SFN system frame number
  • subframe or symbol numbers and so on.
  • a PUSCH using a certain HARQ process ID (e.g. PUSCH of a dynamic grant)
  • the terminal device performs a new transmission on the CG occasions for the same HARQ process
  • the MAC PDU previously stored in a buffer for the HARQ process would be flushed away and overwritten by the new data, which may result in data loss.
  • a configured grant timer associated with the HARQ process has been introduced.
  • a corresponding CG timer associated with the HARQ process starts, and all the CG occasions using the same HARQ process cannot be used by the terminal device for transmitting new data while the CG timer is running or activated.
  • the grant of this CG occasion will not be delivered to the HARQ entity of the terminal device for further processing.
  • the purpose of the CG timer is to ensure proper re-transmissions (if needed) of the MAC PDU by protecting it in the HARQ buffer over an interval of time.
  • the communication device cannot skip the UL transmission on the CG, even if there is no user data or control data to be transmitted, such as, MAC control element (CE) , Common Control Channel (CCCH) service data unit (SDU) , Dedicated Control Channel (DCCH) SDU, and MAC SDU of any logical channel.
  • CE MAC control element
  • CCCH Common Control Channel
  • SDU Dedicated Control Channel
  • DCCH Dedicated Control Channel
  • the communication device may still generate a MAC PDU without user data, which may be multiplexed with or include UCI for transmission on this CG.
  • the term “empty MAC PDU” may refer to such a MAC PDU that is generated for multiplexing with or including the control information (e.g., UCI) and includes no user data or only padding Buffer State Report (BSR) .
  • a legacy communication network there may be a situation where new transmissions on the CG for a HARQ process is blocked due to the empty PDU stored in the corresponding HARQ buffer, and the empty PDU actually has no user data or useful MAC CE at all.
  • an empty MAC PDU is generated for a CG and stored in the buffer for the HARQ process, which starts the CG timer. While the CG timer is running or activated, new transmissions that use the same HARQ process are blocked.
  • the CG mainly aims at facilitating transmissions of delay-sensitive traffics, such as URLLC. Thus, such a situation is undesirable and should be avoided.
  • a MAC PDU could be generated for a CG but then deprioritized by a further traffic with a higher priority.
  • the MAC PDU may have been constructed but not completely transmitted to the network device (e.g., gNB) .
  • the autonomous transmission has been introduced. This is particularly applicable for CG, as the gNB may not be aware whether any MAC PDU has been generated for the CG, if the MAC PDU is not completely transmitted, and hence the gNB may not issue a retransmission grant for the MAC PDU. In this case, the MAC PDU is stuck in the HARQ buffer.
  • the HARQ entity of the terminal device for handling this CG may check if there is a MAC PDU stored in the HARQ buffer already but not completely transmitted. If so, the terminal device may then determine if the CG could be used for autonomous transmission of the MAC PDU, rather than generating a new MAC PDU. Hence, from the network device’s point of view, the autonomous transmission of the MAC PDU is regarded an initial transmission. Otherwise, the HARQ entity may instruct the multiplexing and assembly entity to generate a new MAC PDU for the CG, rather than considering that the MAC PDU is obtained already.
  • the MAC PDU stored in the HARQ buffer for the deprioritized grant is generated solely for purposes of UCI multiplexing.
  • the deprioritized grant could have been skipped by the terminal device, but it was not skipped due to overlapping with PUCCH.
  • the stored MAC PDU is actually empty and does not include any data or any useful MAC CE (e.g. only padding BSR is included) .
  • autonomous transmission of such a MAC PDU may be meaningless and unnecessary. What is more, this is a waste of radio resource that could have been used by other data traffic in the buffer and cause unnecessary delay for new arrival data, which is especially problematic for URLLC or time sensitive communication (TSC) application where the latency requirement for packet delivery is quite stringent.
  • TSC time sensitive communication
  • the terminal device may check the PDU stored for the HARQ process, and determine whether to deliver the CG and at least one associated HARQ information to the HARQ entity for new transmission based on the content of the PDU. According to at least the determination, if the PDU is empty and includes no user data or only padding BSR, the terminal device may avoid unnecessarily delaying data transmission due to the empty PDU on the CG. Additionally or alternatively, the terminal device may determine whether to recover the autonomous transmission on a CG based on the content of the PDU generated for a grant previous that is deprioritized previously. According to at least the determination, if the PDU is empty, the terminal device may avoid the autonomous transmission of the PDU. In this way, the autonomous transmission mechanism is also improved.
  • FIG. 1 shows an example communication environment 100 in which example embodiments of the present disclosure can be implemented.
  • the communication environment 100 may comprise a plurality of communication devices, including a terminal device 110 (hereinafter may also be referred to as a UE 110 or a first device 110) and a network device 120 (hereinafter may also be referred to as a gNB 120 or a second device 120) .
  • a terminal device 110 hereinafter may also be referred to as a UE 110 or a first device 110
  • a network device 120 hereinafter may also be referred to as a gNB 120 or a second device 120
  • the network device 120 manages a cell 102.
  • the terminal device 110 and the network device 120 can communicate with each other in the coverage of the cell 102.
  • a link from the network device 120 to the terminal device 110 is referred to as a downlink (DL)
  • a link from the terminal device 110 to the network device 120 is referred to as an uplink (UL) .
  • the network device 120 is a transmitting (TX) device (or a transmitter) and the terminal device 110 is a receiving (RX) device (or a receiver) .
  • TX transmitting
  • RX receiving
  • the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver) .
  • the environment 100 may include any suitable number of devices adapted for implementing embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 102, and one or more additional cells may be deployed in the environment 100.
  • the network device 120 may configure the terminal device 110 with the CG.
  • the terminal device 110 may transmit user data and/or control information to the network device 120 by using the CG resources without transmitting a Scheduling Request (SR) or the BSR to obtain the UL grant.
  • the control information may comprise UCI.
  • the control information may include HARQ feedback information such as HARQ-acknowledgment (HARQ-ACK) , channel state information (CSI) , SR, and configured grant uplink control information (CG-UCI) .
  • HARQ-ACK HARQ-acknowledgment
  • CSI channel state information
  • SR configured grant uplink control information
  • FIG. 2 shows a schematic diagram of UCI multiplexing according to some example embodiments of the present disclosure.
  • the CG-PUSCH 201 is partially overlapped with the PUCCH 202 in time, and the terminal device 110 may multiplex UCI from PUCCH 202 on the CG-PUSCH 201.
  • the terminal device 110 may generate and deliver a TB in spite of absence of user data or control data to be transmitted, such as, MAC CE, CCCH SDU, DCCH) SDU, and MAC SDU of any logical channel.
  • the MAC layer of the terminal device 110 may generate a MAC PDU for the CG-PUSCH 201 and delivers the MAC PDU to its PHY layer.
  • a MAC PDU may be equivalent to a TB.
  • the PHY layer of the device 110 may multiplex or include control information from PUCCH 202 to the MAC PDU.
  • the UCI and the MAC PDU are separately encoded. In such a case, the TB is generated for control information multiplexing only due to the overlap between CG-PUSCH 201 and PUCCH 202.
  • the empty MAC PDU without any user data may block the transmission of new data, which causes a waste of radio resources and aggravate the latency for packet delivery.
  • the transmission or retransmission of such MAC PDUs is carefully determined by the terminal device 110.
  • the terminal device 110 may check the content of the MAC PDU, and adjust its subsequent processing based on the content, which will be discussed in details below.
  • the terminal device 110 may determine the HARQ process identity (ID) for each transmission based on time parameters, such as SFN, subframe or symbol numbers, and so on.
  • ID HARQ process identity
  • the HARQ process IDs for different CG occasions may be different.
  • a PUSCH that uses a certain HARQ process ID e.g. PUSCH of a dynamic grant
  • a corresponding CG timer associated with the HARQ process starts. All the CG occasions that use the same HARQ process are not used by the terminal device 110 for transmitting new data while the CG timer is running or activated. From the perspective of the terminal device 110, the grant of this CG occasion will not be delivered to its HARQ entity in MAC layer for further processing.
  • the device 110 may determine the absence of user data in the TB by determining the reason why this TB was generated and buffered for the HARQ process. In some example embodiments, the device 110 may determine whether the TB is generated only to be multiplexed with or include control information and thus comprises no user data. For example, the device 110 may check if the TB includes no MAC CE except for padding buffer state report (BSR) . In some examples, the device 110 may determine that the TB is generated only to be multiplexed with or include control information such as hybrid automatic repeat request process-acknowledgment (HARQ-ACK) , channel state information (CSI) , scheduling request (SR) , and/or Configured Grant Uplink Control Information (CG-UCI) .
  • HARQ-ACK hybrid automatic repeat request process-acknowledgment
  • CSI channel state information
  • SR scheduling request
  • CG-UCI Configured Grant Uplink Control Information
  • FIG. 3 illustrates a flowchart of an example method for CG transmission implemented at a terminal device according to example embodiments of the present disclosure.
  • the method 300 will be described with reference to FIGs. 1-2.
  • the method 300 may involve the terminal device 110 and the network device 120 as illustrated in FIG. 1.
  • the network device 120 may configure a CG to the terminal device 110. Prior to using this CG for data transmission, the terminal device 110 may determine a corresponding HARQ process ID for each transmission on the CG. At 310, the terminal device 110 determines a HARQ process for the CG.
  • the terminal device 110 determines whether the CG timer associated with the HARQ process is running or activated. If the CG timer is not running, the CG and at least one associated HARQ information are delivered to the HARQ entity of the terminal device 110 for new data transmission. If the CG timer is running or activated, it means the PUSCH using this HARQ process ID is transmitted, and in this case, there are TBs stored in a buffer for the HARQ process, for example, the PDU.
  • the terminal device 110 may check the content of the MAC PDU to determine whether to block other data transmissions due to the MAC PDU.
  • the terminal device 110 determines whether a predetermined condition related to the content of the PDU stored in the buffer for the HARQ process is met.
  • the predetermined condition may be used by the terminal device 110 for determining whether the content of the PDU is empty.
  • the determination of whether the predetermined condition is met may be performed at the MAC layer of the terminal device 110.
  • the predetermined condition may be the PDU comprising only padding BSR.
  • the terminal device 110 may determine that the PDU is empty by the fact of the PDU is generated and buffered for multiplexing of at least one UCI on a PUSCH. In this example, the device 110 may check if the PDU includes no MAC CE except for the padding BSR.
  • the predetermined condition may be the PDU comprising no user data.
  • the device 110 may check whether the PDU includes one or more segments storing user data. If no user data is found in the PDU, for example, if the PDU includes no MAC CE, no CCCH SDU, no DCCH, and/or SDU of any logical channel (LCH) , the device 110 may determine that the PDU comprises no user data.
  • LCH logical channel
  • the terminal device 110 delivers the CG and at least one associated HARQ information to the HARQ entity of the terminal device 110.
  • the CG may be used by the terminal device 110 for new data transmission.
  • the terminal device 110 refrains from delivery of the CG and at least one associated HARQ information to the HARQ entity and the CG is skipped. In this case, all the CG occasions using the same HARQ process cannot be used by the terminal device 110 for new data transmission until expiration of the CG timer.
  • the terminal device 110 may receive an indication from the network device 120 for determining whether the predetermined condition is met upon the transmission of the PDU being deprioritized. In some other example embodiments, the terminal device 110 may receive an indication from the network device 120 for cancelling such a determination step. As such, the enhanced transmission mechanism may be enabled and disabled based on the indication from the network device 120.
  • an improved solution for CG transmission instead of directly skipping a CG for a HARQ process whose associated CG timer is running or activated, the terminal device is capable of checking the content of MAC PDUs stored for the HARQ process, and determining whether to deliver the CG and at least one associated HARQ information to the HARQ entity for new transmission based on the content. As such, it is possible to avoid unnecessarily delaying data transmission due to empty MAC PDUs.
  • FIG. 4 illustrates a flowchart of an example method for CG transmission implemented at a terminal device according to example embodiments of the present disclosure.
  • the method 400 will be described with reference to FIGs. 1-2.
  • the method 400 may involve the terminal device 110 and the network device 120 as illustrated in FIG. 1.
  • the network device 120 may configure a CG with autonomous transmission to the terminal device 110.
  • the terminal device 110 may use the CG for transmitting a MAC PDU to the network device 120.
  • data traffic with a higher priority than the priority of the MAC PDU is to be transmitted to the network device 120.
  • the MAC PDU is not completely transmitted and deprioritized due to the data traffic.
  • the terminal device 110 e.g., the HARQ entity
  • the terminal device 110 may check if there is a MAC PDU stored in a buffer for the HARQ process but not completely transmitted. If so, the terminal device 110 may then determine if the CG could be used for autonomous transmission of the MAC PDU, rather than generating a new MAC PDU.
  • the terminal device 110 deprioritizes the first CG associated with a HARQ process for a first protocol data unit (PDU) .
  • the first CG is configured with the autonomous transmission.
  • the de-prioritization of the first CG for the first PDU may be due to data traffic with a higher priority than that of the first PDU.
  • the first PDU is not completely transmitted before being deprioritized.
  • the terminal device 110 may store the first PDU in the buffer for a corresponding HARQ process.
  • this configured uplink grant is considered as a de-prioritized UL grant. If this deprioritized UL grant is configured with autonomousTx, the configuredGrantTimer for the corresponding HARQ process of this de-prioritized UL grant shall be stopped if it is running or activated.
  • the terminal device 110 may check the content of the first PDU to determine how to deal with the first PDU, and/or how to arrange the possible transmission of the first PDU with other data transmissions.
  • the terminal device 110 determines whether a predetermined condition related to content of the first PDU is met.
  • the predetermined condition may be used by the terminal device 110 for determining whether the content of the first PDU is empty. In some embodiments, the determination of whether the predetermined condition is met may be performed at a HARQ entity of the terminal device 110.
  • the predetermined condition may be the first PDU comprising only padding BSR.
  • the terminal device 110 may determine that the first PDU is empty by the fact of the first PDU is generated and buffered for multiplexing of at least one UCI on a PUSCH.
  • the device 110 may check if the first PDU includes no MAC CE except for the padding BSR.
  • the predetermined condition may be the first PDU comprising no user data.
  • the device 110 may check whether the first PDU includes one or more segments storing user data. If no user data is found in the first PDU, for example, if the first PDU includes no MAC CE, no CCCH SDU, no DCCH, and/or SDU of any logical channel (LCH) , the device 110 may determine the first PDU comprises no user data.
  • LCH logical channel
  • the predetermined condition may be a comparison between at least one priority level of at least logical channel mapped to the first PDU and at least one priority level of at least logical channel with a buffered data. For example, if the priority of data buffered in at least one logical channel is higher than the priority of data that has been included in the first PDU, the terminal device 110 may consider the predetermined condition is met.
  • the terminal device 110 refrains from conducting the autonomous transmission of the first PDU to the network device 120.
  • the second CG may be subsequent to the first CG.
  • the second CG may be used by the terminal device 110 for new data transmission.
  • the terminal device 110 may obtain a different TB, for example, a second PDU to be transmitted with the CG.
  • the HARQ entity of the terminal device 110 may instruct the multiplexing and assembly entity to construct a new MAC PDU as the second PDU.
  • the first PDU may be flushed and replaced by the second PDU in the buffer of the HARQ process.
  • the terminal device 110 may then transmit the second PDU on the second CG.
  • the first CG and the second CG may be associated with the HARQ process.
  • the terminal device 110 may flush the first PDU stored in the buffer for the HARQ process.
  • the first PDU may be flushed directly upon the de-prioritization of the first CG.
  • the terminal device 110 may stop the CG timer associated with the HARQ process.
  • the terminal device 110 may perform the autonomous transmission of the first PDU to the network device 120 by using the second CG. In this case, the terminal device 110 does not obtain the second PDU for transmission on the second CG.
  • the terminal device 110 may receive an indication from the network device 120 for whether the determination of the predetermined condition is to be performed. In some other example embodiments, the terminal device 110 may receive an indication from the network device 120 for disabling such a determination step. With the indication from the network device 120, the terminal device 110 may decide whether to determine the predetermined condition in response to the de-prioritization of the first CG. As such, the enhanced transmission mechanism may be enabled and disabled based on the indication from the network device 120.
  • the terminal device is capable of checking the content of MAC PDUs stored in the HARQ buffer, and determining whether to recover the transmission of the MAC PDU.
  • the terminal device may flush it from the buffer, or alternatively, refrain from performing an autonomous transmission of the MAC PDU. As such, it is possible to avoid unnecessarily delaying data transmission due to empty MAC PDUs, and the latency of data transmission can be reduced.
  • a first apparatus capable of performing any of the method 300 may comprise means for performing the respective steps of the method 300.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the first apparatus comprises: means for upon determining a Hybrid Automatic Repeat Request (HARQ) process for a configured grant, determining whether a configured grant timer associated with the HARQ process is running or activated; means for in accordance with a determination that the configured grant timer is running or activated, determine whether a predetermined condition related to content of a packet data unit (PDU) stored in a buffer for the HARQ process is met; and means for in accordance with a determination that the predetermined condition is met, deliver the configured grant and at least one associated HARQ information to a HARQ entity of the first apparatus.
  • HARQ Hybrid Automatic Repeat Request
  • the predetermined condition comprises at least one of the following: the PDU comprising only a padding buffer status report (BSR) , and the PDU comprising no service data unit (SDU) .
  • BSR padding buffer status report
  • SDU no service data unit
  • the PDU meeting the predetermined condition is generated for multiplexing of at least one uplink control information (UCI) on a Physical Uplink Shared Channel (PUSCH) .
  • UCI uplink control information
  • PUSCH Physical Uplink Shared Channel
  • the determination of whether the predetermined condition is met is performed at a medium access control (MAC) layer of the first apparatus.
  • MAC medium access control
  • the first apparatus further comprises: means for receiving, from a network device, an indication indicative of whether the determination of the predetermined condition is to be performed.
  • the first apparatus comprises a terminal device, and the network device serves the terminal device.
  • a second apparatus capable of performing any of the method 400 may comprise means for performing the respective steps of the method 400.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the second apparatus comprises: means for deprioritizing a first configured grant associated with a Hybrid Automatic Repeat Request (HARQ) process for a first packet data unit (PDU) ; determining whether a predetermined condition related to content of the first PDU is met; and in accordance with a determination that the predetermined condition is met, refraining from conducting an autonomous transmission of the first PDU to a network device.
  • HARQ Hybrid Automatic Repeat Request
  • the predetermined condition comprises at least one of the following: the first PDU comprising only a padding buffer status report (BSR) , the first PDU comprising no service data unit (SDU) and a comparison between at least one priority level of at least logical channel mapped to the first PDU and at least one priority level of at least logical channel with a buffered data.
  • BSR padding buffer status report
  • SDU no service data unit
  • the determination of whether the predetermined condition is met is performed at a HARQ entity of the second apparatus.
  • the means for refraining from conducting the autonomous transmission of the first PDU further comprises: means for obtaining a second PDU to be transmitted with a second configured grant, the second PDU being different from the first PDU.
  • the first configured grant and the second configured grant are associated with the HARQ process.
  • the means for refraining from conducting the autonomous transmission of the first PDU further comprises: means for flushing the first PDU stored in a buffer for the HARQ process; and means for stopping a configured grant timer associated with the HARQ process.
  • the second apparatus further comprises: means for flushing the first PDU stored in a buffer for the HARQ process upon the de-prioritization of the first configured grant.
  • the second apparatus further comprises: means for receiving, from a network device, an indication indicative of whether the determination of the predetermined condition is to be performed.
  • the second apparatus comprises a terminal device, and a network device serves the terminal device.
  • FIG. 5 is a simplified block diagram of a device 500 that is suitable for implementing embodiments of the present disclosure.
  • the device 500 may be provided to implement the communication device, for example the terminal device 110 or the network device 120 as shown in FIG. 1.
  • the device 500 includes one or more processors 510, one or more memories 520 coupled to the processor 510, and one or more transmitters and receivers (TX/RX) 540 coupled to the processor 510.
  • TX/RX transmitters and receivers
  • the TX/RX 540 is for bidirectional communications.
  • the TX/RX 540 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 510 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 500 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 520 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 524, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 522 and other volatile memories that will not last in the power-down duration.
  • a computer program 530 includes computer executable instructions that are executed by the associated processor 510.
  • the program 530 may be stored in the ROM 520.
  • the processor 510 may perform any suitable actions and processing by loading the program 530 into the RAM 520.
  • the embodiments of the present disclosure may be implemented by means of the program 530 so that the device 500 may perform any process of the disclosure as discussed with reference to FIGs. 1-4.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 530 may be tangibly contained in a computer readable medium which may be included in the device 500 (such as in the memory 520) or other storage devices that are accessible by the device 500.
  • the device 500 may load the program 530 from the computer readable medium to the RAM 522 for execution.
  • the computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • FIG. 6 illustrates an example of the computer readable medium 600 in form of CD or DVD.
  • the computer readable medium has the program 530 stored thereon.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, device, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the methods 300 and 400 as described above with reference to FIGs. 3-4.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing device, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, device or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs, des appareils et un support lisible par ordinateur pour la transmission d'unité de données. Le procédé consiste, lors de la détermination d'un processus HARQ pour une CG, à déterminer si un temporisateur de CG associé au processus HARQ est exécuté ou activé; quand il est déterminé que le temporisateur de CG est exécuté ou activé, à déterminer si une condition prédéterminée relative au contenu d'une PDU stockée dans un tampon pour le processus HARQ est satisfaite; et quand il est déterminé que la condition prédéterminée est satisfaite, à distribuer la CG et au moins une information HARQ associée à une entité HARQ du dispositif terminal. Grâce à cette solution, le dispositif terminal est capable de vérifier la PDU MAC stockée pour le processus HARQ lorsque le temporisateur de CG est exécuté ou activé, et de déterminer s'il faut utiliser la CG pour une nouvelle transmission.
PCT/CN2021/102877 2021-06-28 2021-06-28 Transmission d'autorisation configurée WO2023272456A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180099912.7A CN117581494A (zh) 2021-06-28 2021-06-28 配置授权传输
PCT/CN2021/102877 WO2023272456A1 (fr) 2021-06-28 2021-06-28 Transmission d'autorisation configurée

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/102877 WO2023272456A1 (fr) 2021-06-28 2021-06-28 Transmission d'autorisation configurée

Publications (1)

Publication Number Publication Date
WO2023272456A1 true WO2023272456A1 (fr) 2023-01-05

Family

ID=84692131

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/102877 WO2023272456A1 (fr) 2021-06-28 2021-06-28 Transmission d'autorisation configurée

Country Status (2)

Country Link
CN (1) CN117581494A (fr)
WO (1) WO2023272456A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865508A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 一种通信方法及通信装置
WO2021022532A1 (fr) * 2019-08-07 2021-02-11 Nokia Shanghai Bell Co., Ltd. Partage de processus harq par de multiples ressources à octroi configurées
CN112583535A (zh) * 2019-09-30 2021-03-30 夏普株式会社 由用户设备执行的方法以及用户设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865508A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 一种通信方法及通信装置
WO2021022532A1 (fr) * 2019-08-07 2021-02-11 Nokia Shanghai Bell Co., Ltd. Partage de processus harq par de multiples ressources à octroi configurées
CN112583535A (zh) * 2019-09-30 2021-03-30 夏普株式会社 由用户设备执行的方法以及用户设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT: "Report of [035][IIOT] Deprioritized transmissions (CATT)", 3GPP DRAFT; R2-2002286, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Elbonia; 20200224 - 20200228, 11 March 2020 (2020-03-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051864815 *

Also Published As

Publication number Publication date
CN117581494A (zh) 2024-02-20

Similar Documents

Publication Publication Date Title
US20220286235A1 (en) Dynamic Retransmission Configuration
US9974059B2 (en) Method and apparatus for control information transmission
US20220294576A1 (en) Resource selection for transmission of pending data unit
WO2020191625A1 (fr) Mécanisme d'activation de harq basé sur un service
US20240236745A1 (en) Priority setting for quality of experience
US20240195535A1 (en) Harq process selection
US11849497B2 (en) Methods, devices, and medium for handling of non-SDT data
WO2023272456A1 (fr) Transmission d'autorisation configurée
WO2021022422A1 (fr) Transmission d'ack/nack de couche supérieure
WO2023035140A1 (fr) Demande de cot proactive
WO2024168740A1 (fr) Indication de rétroaction de demande de répétition automatique hybride dynamique
WO2024216508A1 (fr) Mécanisme pour effectuer une retransmission pour autorisation configurée
WO2023035148A1 (fr) Demande de cot proactive
WO2024212064A1 (fr) Rapport de csi pour activation de cellule
WO2022133758A1 (fr) Amélioration de la retransmission autonome
WO2024031477A1 (fr) Différenciation de radiomessagerie
WO2022213238A1 (fr) Transmission fiable sur des bandes sous licence et sans licence
WO2024031369A1 (fr) Activation et désactivation de retour harq dans un réseau non terrestre
WO2024168896A1 (fr) Gestion de support de transmission de petites données à terminaison mobile
WO2022267064A1 (fr) Réduction de latence dans un accès à un canal semi-statique
WO2022222062A1 (fr) Mécanisme d'assistance de liaison latérale
US20240015594A1 (en) Uplink Data Duplication Avoidance
WO2024212177A1 (fr) Mécanisme de transmission d'uci
US20240349266A1 (en) Methods, devices, and computer readable medium for communication
WO2023077511A1 (fr) Résolution de contention pour réseau non terrestre

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180099912.7

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21947420

Country of ref document: EP

Kind code of ref document: A1