CN114208077B - Retransmission mechanism for configuring authorized uplink transmissions - Google Patents

Retransmission mechanism for configuring authorized uplink transmissions Download PDF

Info

Publication number
CN114208077B
CN114208077B CN201980099028.6A CN201980099028A CN114208077B CN 114208077 B CN114208077 B CN 114208077B CN 201980099028 A CN201980099028 A CN 201980099028A CN 114208077 B CN114208077 B CN 114208077B
Authority
CN
China
Prior art keywords
transport block
time
retransmission
expiration time
grant
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201980099028.6A
Other languages
Chinese (zh)
Other versions
CN114208077A (en
Inventor
陶涛
吴春丽
T·伦蒂拉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks 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 filed Critical Nokia Shanghai Bell Co Ltd
Publication of CN114208077A publication Critical patent/CN114208077A/en
Application granted granted Critical
Publication of CN114208077B publication Critical patent/CN114208077B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • 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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • 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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • 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

Landscapes

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

Abstract

Embodiments of the present disclosure relate to apparatuses, methods, devices, and computer-readable storage media for configuring a retransmission mechanism for authorized uplink transmissions. The method comprises the following steps: transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block; in response to receiving feedback from the second device indicating unsuccessful reception of the transport block, adjusting an expiration time of a configured grant weight transmission timer without initiating autonomous retransmission of the transport block; determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and retransmitting the transport block while stopping configuring the weight grant timer in response to determining that the scheduling information is received. In this way, retransmissions in the hybrid automatic repeat request process may be performed in accordance with the uplink grant scheduled by the network device, and thus the retransmission efficiency of the configured grant uplink transmission in the unlicensed spectrum may be improved.

Description

Retransmission mechanism for configuring authorized uplink transmissions
Technical Field
Embodiments of the present disclosure relate generally to the field of telecommunications and, more particularly, relate to an apparatus, method, device, and computer readable storage medium for configuring a retransmission mechanism for authorized uplink transmissions.
Background
Uplink (UL) scheduling with Configuration Grants (CG) has been allowed in New Radios (NR). In an NR solution for UL transmission with CG, a network device may allocate UL resources for initial hybrid automatic repeat request (HARQ) transmission to a terminal device. Furthermore, two types of configuration authorization mechanisms are supported in the NR. For NR-U, it is not necessary to exclude the configuration of the grant mechanism for type 1 or type 2 of operation for NR in the unlicensed spectrum.
Currently, three retransmission modes for CGUL transmissions are supported in a new wireless unlicensed (NR-U). Alternatively, retransmissions may be scheduled via dynamic UL grants. Alternatively, autonomous retransmission on CG resources may be initiated when the terminal device receives NACK feedback via a Downlink Feedback Indication (DFI) of the corresponding HARQ process. In addition, autonomous retransmissions on CG resources may also be initiated when the "CG retransmission timer" expires.
Disclosure of Invention
In general, example embodiments of the present disclosure provide a solution for configuring a retransmission mechanism for authorized uplink transmissions.
In a first aspect, a first device is provided. The first device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the first device to at least: transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block; in response to receiving feedback from the second device indicating unsuccessful reception of the transport block, adjusting an expiration time of a configured grant weight transmission timer without initiating autonomous retransmission of the transport block; determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and retransmitting the transport block while stopping configuring the weight grant timer in response to determining that the scheduling information is received.
In a second aspect, a second apparatus is provided. The second device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to at least: receiving a transport block from a first device; and in response to failure to decode the transport block, sending feedback to the first device indicating unsuccessful reception of the transport block to trigger the first device to adjust an expiration time of the configuration grant weight transmission timer.
In a third aspect, a method is provided. The method comprises the following steps: transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block; in response to receiving feedback from the second device indicating unsuccessful reception of the transport block, adjusting an expiration time of a configured grant weight transmission timer without initiating autonomous retransmission of the transport block; determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and retransmitting the transport block while stopping configuring the weight grant timer in response to determining that the scheduling information is received.
In a fourth aspect, a method is provided. The method comprises the following steps: receiving a transport block from a first device; and in response to failure to decode the transport block, sending feedback to the first device indicating unsuccessful reception of the transport block to trigger the first device to adjust an expiration time of the configuration grant weight transmission timer.
In a fifth aspect, there is provided an apparatus comprising: means for transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block; means for adjusting an expiration time of a configured grant weight transmission timer without initiating autonomous retransmission of the transport block in response to receiving feedback from the second device indicating unsuccessful reception of the transport block; means for determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and means for retransmitting the transport block while stopping configuring the grant weight timer in response to determining that the scheduling information is received.
In a sixth aspect, there is provided an apparatus comprising: means for receiving a transport block from a first device; and means for sending feedback to the first device indicating unsuccessful reception of the transport block in response to failure to decode the transport block to trigger the first device to adjust the expiration time of the configured grant weight timer.
In a seventh aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform a method according to the third aspect.
In an eighth aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform a method according to the fourth aspect.
Other features and advantages of embodiments of the present disclosure will become apparent from the following description of the specific embodiments, when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the embodiments of the disclosure.
Drawings
Embodiments of the present disclosure are presented in an exemplary sense and their advantages are explained in more detail below with reference to the drawings, wherein:
FIG. 1 illustrates an example communication network in which example embodiments of the present disclosure may be implemented;
fig. 2 illustrates a conventional retransmission procedure for configuring an authorized uplink transmission;
fig. 3 shows a schematic diagram of a retransmission process for configuring an authorized uplink transmission according to an example embodiment of the present disclosure;
Fig. 4 illustrates a diagram of an example retransmission process for configuring an authorized uplink transmission, according to some example embodiments of the present disclosure;
fig. 5 illustrates a flowchart of an example method for configuring retransmission of an authorized uplink transmission, according to some example embodiments of the present disclosure;
fig. 6 illustrates a flowchart of an example method for configuring retransmission of an authorized uplink transmission, according to some example embodiments of the present disclosure;
FIG. 7 illustrates a simplified block diagram of a device suitable for implementing example embodiments of the present disclosure; and
fig. 8 illustrates a block diagram of an example computer-readable medium, according to some embodiments of the disclosure.
The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements.
Detailed Description
The subject matter described herein will now be discussed with reference to several example embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thereby practice the subject matter described herein, and are not meant to imply any limitation on the scope of the subject matter.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two functions or acts illustrated in succession may, in fact, be executed concurrently, or the acts may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-advanced (LTE-a), wideband Code Division Multiple Access (WCDMA), high Speed Packet Access (HSPA), and the like. Furthermore, the communication between the terminal device and the network device in the communication network may be performed according to any suitable generation communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and/or any other protocol currently known or to be developed in the future.
Embodiments of the present disclosure may be applied to various communication systems. In view of the rapid development of communications, there are of course future types of communication technologies and systems with which the present disclosure may be implemented. It should not be taken as limiting the scope of the invention to only the above-described systems. For purposes of illustration, embodiments of the present disclosure will be described with reference to a 5G communication system.
The term "network device" as used herein includes, but is not limited to, a Base Station (BS), gateway, registration management entity, and other suitable devices in a communication system. The term "base station" or "BS" means a node B (node B or NB), an evolved node B (eNodeB or eNB), an NRNB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, a low power node such as a femto, pico, etc.
The term "terminal device" as used herein includes, but is not limited to, "User Equipment (UE)" and other suitable terminal devices capable of communicating with a network device. For example, a "terminal device" may refer to a terminal, mobile Terminal (MT), subscriber Station (SS), portable subscriber station, mobile Station (MS), or Access Terminal (AT).
The term "circuitry" as used herein may refer to one or more or all of the following:
(A) Hardware-only circuit implementations (e.g., implementations in analog and/or digital circuits only)
(b) A combination of hardware circuitry and software, for example (as applicable):
(i) Combinations of analog and/or digital hardware circuits having
Software/firmware
(ii) A hardware processor (including a digital signal processor) having software, any portion of the software and memory that work together to cause a device such as a mobile phone or server to perform various functions), and
(c) Hardware circuitry and/or a processor (e.g., a microprocessor or a portion of a microprocessor) that requires software (e.g., firmware) to operate, but may not be present when software is not required to operate.
This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuit also encompasses an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or its) accompanying software and/or firmware. The term circuitry also encompasses a baseband integrated circuit, or processor integrated circuit, or a similar integrated circuit in a server, a cellular network device, or other computing or network devices for a mobile device, e.g., and if applicable to the particular claim element.
Fig. 1 illustrates an example communication network 100 in which embodiments of the present disclosure may be implemented. The network 100 includes a second device 110 (hereinafter may be referred to as network device 110) served by the network device 110 and first devices 120-1 and 120-2 (hereinafter collectively referred to as first devices 120 or individually referred to as terminal devices 120). The service area of network device 110 is referred to as cell 102. It should be understood that the number of network devices and terminal devices is for illustration purposes only and does not imply any limitation. Network 100 may include any suitable number of network devices and terminal devices suitable for implementing embodiments of the present disclosure. It should be understood that although not shown, one or more terminal devices may be in cell 102 and served by network device 110.
Communications in network 100 may conform to any suitable standard including, but not limited to, long Term Evolution (LTE), LTE evolution, LTE-advanced (LTE-a), wideband Code Division Multiple Access (WCDMA), code Division Multiple Access (CDMA), global system for mobile communications (GSM), and the like. Further, the communication may be performed according to any generation communication protocol currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols.
As described above, uplink (UL) scheduling with Configuration Grants (CG) has been allowed in NR. In the UL, the network device may dynamically allocate resources to the terminal device via a cell radio network temporary identity (C-RNTI) on a Physical Downlink Control Channel (PDCCH). The terminal device may always monitor the PDCCH in order to find possible grants for UL transmissions when its Downlink (DL) reception is enabled. Further, with CG, the network device may allocate UL resources for initial hybrid automatic repeat request (HARQ) transmissions to the terminal device.
Uplink (UL) scheduling with Configuration Grants (CG) has been allowed in New Radios (NR). In an NR solution for UL transmission with CG, a network device may allocate UL resources for initial hybrid automatic repeat request (HARQ) transmission to a terminal device. Furthermore, two types of configuration authorization mechanisms are supported in the NR. For NR-U, it is not necessary to exclude type 1 or type 2 configuration authorization mechanisms for operation of NRs in unlicensed spectrum.
As described above, uplink grants of two configurations are defined. For type 1, radio Resource Control (RRC) signaling provides configured uplink grants (including periodicity) directly. RRC signaling defines the periodicity of the configured uplink grant in type 2 while PDCCH is addressed to the configured scheduling-radio network temporary identity (CS-RNTI), or can signal activation of the configured uplink grant, or deactivation of the configured uplink grant; that is, the PDCCH addressed to the CS-RNTI uplink grant can be implicitly reused according to the RRC defined periodicity until deactivated.
When the configured uplink grant is active, if the terminal device cannot find its C-RNTI/CS-RNTI on the PDCCH, an uplink transmission according to the configured uplink grant may be made. Otherwise, if the terminal device finds its C-RNTI/CS-RNTI on the PDCCH, the PDCCH allocation covers the configured uplink grant.
A similar mechanism, referred to as "autonomous UL Access (AUL)", has been introduced in LTE for supporting autonomous UL transmissions on unlicensed spectrum. The terminal device may be configured with a set of subframes and HARQ processes for autonomous Physical Uplink Shared Channel (PUSCH) transmission via RRC signaling. AUL operation may be activated and released with Downlink Control Information (DCI) format 0A or 4A. If there is no data in the UL buffer, the terminal device may skip the AUL allocation. The AUL activation DCI is used to indicate resource allocation, modulation and Coding Scheme (MCS) and demodulation reference signal (DMRS) cyclic shift and orthogonal cover code to the terminal device.
Further, the terminal device may indicate to the network device the selected HARQ process ID, the new data indicator, the redundancy version, the ID of the terminal device, the PUSCH start and end point accompanying each UL transmission, and whether the Channel Occupation Time (COT) acquired by the terminal device can be shared with the network device. The network device may provide HARQ feedback for an AUL-enabled HARQ process, as well as Transmit Power Control (TPC) commands and Precoding Matrix Indicators (PMIs), to the terminal device via DL control signaling messages referred to as AUL-Downlink Feedback Indications (DFIs).
AUL also allows configuring a set of starting positions for terminal devices with very fine gratings within the first SC-FDMA symbol of a subframe: 16, 25, 34, 43, 52, or 61 microseconds after the subframe boundary, or at the beginning of symbol # 1. Since all terminal devices perform listen before talk operations before AUL transmission to determine if the channel is idle, the different starting points allow e.g. prioritizing the transmission for some terminal devices (by assigning earlier starting points) and reducing the number of collisions. The transmission in the first symbol is not PUSCH data, but rather a very long CP extending from the next symbol # 2. In effect, CP extensions are used to reserve channels for a given terminal device by blocking other terminal devices.
In NU-R, three retransmission modes are supported for configuration grant UL transmissions. As an option, retransmissions may be scheduled by dynamic UL grants. Alternatively, autonomous retransmission may be initiated on the configured grant resources when the terminal device receives NACK feedback for the corresponding HARQ process via the DFI. Further, autonomous retransmission may be initiated when a configured grant weight transmission timer (hereinafter may be referred to as CG retransmission timer) expires.
The CG retransmission timer behavior has been allowed. For the case of a Transport Block (TB) previously transmitted on a configuration grant, this timer is introduced for autonomous retransmission on the configuration grant (i.e. timer expiration = HARQ NACK). The CG retransmission timer is started when the TB is actually transmitted on the configuration grant, and stopped when the DFI or dynamic grant for the HARQ process is received.
It has been allowed that when the network device responds to CG PUSCH transmissions, the terminal device will rely on the scheduling of the network device rather than automatic retransmission. However, LTE behavior definition: the retransmission timer is stopped after the terminal device receives a NACK for a given HARQ process from the network device. Automatic retransmission may occur when a NACK is received while the timer is not running.
Thus, the behavior of the terminal device when it receives NACK feedback via DFI for the corresponding HARQ process is unclear. When the terminal device receives a NACK via the DFI, the terminal device may prepare for autonomous retransmission and attempt to access the channel. However, the network device may also attempt to access the channel to simultaneously send UL grants to the terminal device for scheduled retransmissions. Allowing both would lead to HARQ process contention/collision problems.
To avoid such ambiguous behavior, it has been proposed that UL grants for configuring retransmissions of authorized HARQ processes may be sent with the DFI (i.e. HARQ-NACK), or may be sent in a time slot prior to the DFI.
The DFI for HARQ feedback may use a bitmap with dedicated bits corresponding to each HARQ process to indicate feedback for multiple HARQ processes. Assuming the same approach is reused in the NR-U, the CG retransmission timer will stop when a NACK is received. When the CG retransmission timer is stopped, the network device may not schedule the HARQ process originally sent via the configured grant resources. Thus, it may happen that only a limited number of HARQ processes may be retransmitted via the scheduling mode, because the terminal device only expects up to two unicast UL grants in one slot.
Fig. 2 illustrates a conventional retransmission process for configuring an authorized uplink transmission. As shown in fig. 2, one terminal device performs CGUL transmission in time slots 201 to 204. Unfortunately, the network device cannot decode all of these transmissions (e.g., due to strong interference or collisions with another terminal device's transmissions). Assuming that the network device completes the LBT operation at slot 206 to obtain channel access, the network device will feed back a NACK to the terminal device for the corresponding HARQ process 211-214. Due to the limitation of the terminal device capability, the network device may only provide UL grants (in PDCCH 221) to the terminal device in slot 206 for retransmitting failed transport blocks with HARQ process ID 211. The other three transport blocks will depend only on autonomous retransmissions in the configuration grant resources. In practice, the network device can send UL grants in the following slots to schedule more retransmissions.
Thus, in order to improve the reliability and delay performance of pending HARQ processes for retransmissions, a new method may be discussed below that allows a network device to continue to transmit UL grants for retransmission configuration grant HARQ processes even after a NACK for the corresponding HARQ process is indicated to the terminal device.
The principles and implementations of the present disclosure will be described in detail below with reference to fig. 3, fig. 3 showing a schematic diagram of a retransmission process 300 for configuring an authorized uplink transmission according to an example embodiment of the present disclosure. For discussion purposes, the process 300 will be described with reference to FIG. 1. Process 300 may include network device 110 and terminal device 120 as shown in fig. 1.
Network device 110 may send 310 Downlink Control Information (DCI) to terminal device 120. The DCI may include configuration information to indicate a configured UL grant for transmission from terminal device 120 to network device 110. Further, the DCI may also include a value of a CG retransmission timer to indicate a time interval after which autonomous retransmissions may be initiated without receiving feedback from the network device.
The terminal device 120 may construct a TB to be transmitted and transmit 320 the TB on the resources indicated by the received configuration information for the configured UL grant transmission. Network device 110 may decode the TB to obtain the data sent from terminal device 120. If network device 110 determines that decoding the transport block fails, network device 110 may send 330 a DFI, i.e., HARQ-NACK, to terminal device 120 indicating that TB reception was unsuccessful.
If the terminal device 120 receives the DFI and knows that the reception of the TB is unsuccessful, the terminal device 120 adjusts 340 the expiration time of the CG retransmission timer without starting autonomous retransmission of the TB.
In some example embodiments, to adjust the expiration time, terminal device 120 may defer the expiration of the CG retransmission timer for a certain period of time. The CG retransmission timer may expire/stop when the terminal device 120 receives a HARQ-NACK. However, to wait for UL grants scheduled by network device 110 to be used for retransmissions in the HARQ process, terminal device 120 may defer the stopping of the CG retransmission timer for a certain period of time.
Alternatively, the terminal device 120 may adjust the expiration time of the configured grant weight transmission timer according to the time period. That is, the terminal device 120 can set the expiration time to a new specific period of time regardless of the time taken for the timer to expire. This procedure may be considered as a new timer running after receiving the HARQ-NACK.
As a further option, after the physical layer of the terminal device 120 receives the HARQ-NACK, the HARQ-NACK may be suspended for a certain period of time to defer transmission of the HARQ-NACK to the MAC layer. That is, even if HARQ-NACK arrives, the CG retransmission timer may not be stopped. The PHY layer may deliver only HARQ-NACK if the scheduling information is not received within a certain period of time.
The specific time period for adjusting the timer may be obtained from the network device 110 or determined by the terminal device 110 itself. Alternatively, the specific time may be predefined/configured in the specification.
In some example embodiments, the terminal device 120 may obtain a time period associated with the expiration time to be adjusted from the DCI. In some example embodiments, the terminal device 120 may obtain a time period associated with the expiration time to be adjusted from the DFI. In some example embodiments, when a connection is established between the terminal device and the network device, the terminal device 120 may obtain a time period associated with the expiration time to be adjusted via RRC signaling.
In some example embodiments, the terminal device 120 may determine a time period associated with the expiration time to be adjusted. The terminal device 120 may determine the number of HARQ processes to transmit based on the feedback. I.e. the number of HARQ-NACKs indicated in the DFI. Based on the number of HARQ processes to be transmitted, terminal device 120 may determine the number of occasions to be monitored for receiving UL grants from network device 110. A time period associated with the expiration time to be adjusted may be determined based on a time interval corresponding to the determined number of occasions.
Referring back to fig. 2, in the determined period of the adjusted CG retransmission timer, terminal device 120 may monitor the PDCCH to determine if scheduling information indicating UL grants sent from network device 110 is present before the adjusted configured grant weight transmission timer expires. If so, the terminal device 120 retransmits 350 the TB based on the scheduling information while stopping the CG retransmission timer.
In some example embodiments, if the terminal device 120 does not receive the scheduling information, the terminal device 120 may initiate autonomous retransmission of TBs for HARQ processes on the configured UL grant.
Fig. 4 illustrates a diagram of an example retransmission process for configuring an authorized uplink transmission, according to some example embodiments of the present disclosure. The concept for adjusting CG retransmission timers according to embodiments of the present disclosure is described in further detail below with reference to fig. 4.
As shown in fig. 4, CG transmissions from terminal device 120 exist in time slots 401 through 404. HARQ processes 411 to 414 are used in time slots 401 to 404, respectively. The terminal device 120 receives HARQ feedback via CG-DFI in time slot 406. Since network device 110 cannot decode HARQ processes 411 through 414, a "NACK" for the corresponding HARQ process (from 411 through 414) will be indicated in the CG-DFI.
As described above, when the terminal device 120 receives ACK/NACK feedback for a corresponding HARQ process via CG-DFI, the CG retransmission timer will not stop immediately. Terminal device 120 delays the stopping of the CG retransmission timer by an offset (e.g., a certain timer period 430).
Thus, for HARQ process 411, the CG retransmission timer associated with HARQ process 411 begins after time slot 401, with the CGUL transmission of HARQ process 411 being performed in time slot 401. After the UE decodes the PDCCH in slot 406, the CG retransmission timer associated with HARQ process 401 is stopped, as terminal device 120 receives NACK feedback and UL grant for HARQ process 411 in this PDCCH 421 occasion.
For HARQ process 412, a CG retransmission timer associated with HARQ process 412 is started after time slot 402, and the CGUL transmission of HARQ process 412 is performed in time slot 402. When terminal device 120 receives NACK feedback for HARQ process 412 via CG-DFI in slot 406, it adjusts the expiration of the timer in slot 406 and keeps monitoring the PDCCH from network device 110. After terminal device 120 decodes the PDCCH in slot 407, the CG retransmission timer associated with HARQ process 412 is stopped because terminal device 120 received the UL grant for HARQ process 412 in this PDCCH 422 occasion.
For HARQ processes 413-414, the process is similar to HARQ process 403. The CG retransmission timer associated with HARQ process 413 begins after time slot 403 and stops at time slot 408. CG retransmission timers associated with HARQ process 414 begin after time slot 404 and stop at time slot 409.
In some example embodiments, one of the signaling options may also be not to allow autonomous retransmission of the terminal device, i.e. to set a certain timer period 430 to be unlimited.
In some example embodiments, another state (e.g., setting the particular timer period 430 to 0) may disable network device scheduled retransmissions, i.e., the terminal device 120 may assume that all retransmissions will occur on CG resources.
In this way, CG retransmission flexibility may be increased, and retransmission efficiency of configuration-authorized uplink transmissions in unlicensed spectrum may be improved.
Further details of example embodiments according to the present disclosure will be described with reference to fig. 5-6.
Fig. 5 illustrates a flowchart of an example method 500 for configuring retransmission of an authorized uplink transmission, according to some example embodiments of the present disclosure. The method 500 may be implemented at the terminal device 120 as shown in fig. 1. For discussion purposes, the method 500 will be described with reference to FIG. 1.
At 510, the terminal device 120 transmits the transport block to the second device 110 while starting a configured grant weight timer for autonomous retransmission of the transport block.
At 520, terminal device 120 receives feedback from network device 110 indicating unsuccessful reception of a transport block.
If the terminal device 120 determines that feedback is received, the terminal device 120 adjusts the expiration time of the configured grant weight transmission timer without initiating autonomous retransmission of the transport block at 530.
At 540, the terminal device 120 determines whether scheduling information for retransmission of the transport block is received before the adjusted configured grant weight timer expires.
If the terminal device 120 determines that scheduling information is received, the terminal device 120 retransmits the transport block while stopping configuring the grant weight transmission timer at 550.
In some example embodiments, the terminal device 120 may determine a time period associated with the expiration time to be adjusted and defer configuration of the grant weight timer to the expiration time period.
In some example embodiments, the terminal device 120 may determine a time period associated with the expiration time to be adjusted and adjust the expiration time of the configuration weight transmission timer according to the time period.
In some example embodiments, the terminal device 120 receives control information from the second device and determines a time period associated with the expiration time to be adjusted from the control information.
In some example embodiments, if feedback is received at the physical layer, the terminal device 120 may suspend delivery of feedback to the MAC layer of the first device for a period of time associated with the expiration time to be adjusted to defer configuring the expiration time of the weight-imparting timer.
In some example embodiments, the terminal device 120 may determine a time period associated with the expiration time to be adjusted based on the feedback.
In some example embodiments, the terminal device 120 may receive radio resource control signaling from the second device and determine a time period associated with the expiration time to be adjusted according to the radio resource control signaling.
In some example embodiments, the terminal device 120 may determine the number of hybrid automatic repeat request processes to be retransmitted based on the feedback. The terminal device 120 may also determine the number of occasions to be monitored for receiving control information from the second device based on the number of hybrid automatic repeat request processes to be retransmitted; and determining a time period associated with the expiration time to be adjusted based on the time interval corresponding to the number of occasions.
In some example embodiments, the time period is preconfigured.
In some example embodiments, if the terminal device 120 determines that scheduling information for retransmission of a transport block is not received before the adjusted configuration grant weight transmission timer expires, the terminal device 120 may initiate automatic retransmission of the transport block for the hybrid automatic repeat request process.
Fig. 6 illustrates a flowchart of an example method 600 for configuring retransmission of an authorized uplink transmission, according to some example embodiments of the present disclosure. The method 600 may be implemented at a network device 110 as shown in fig. 1. For discussion purposes, the method 600 will be described with reference to FIG. 1.
At 610, network device 110 receives a transport block from a first device.
At 620, network device 110 determines whether there is a failure in decoding the transport block. If network device 110 determines that decoding the transport block failed, network device 110 sends feedback to the first device indicating unsuccessful reception of the transport block to trigger terminal device 120 to adjust the expiration time of the configure grant weight transmission timer at 630.
In some example implementations, the network device 110 may determine a time period associated with the expiration time based on a state of a channel between the first device and the second device; and transmitting an indication of the time period to the first device via control information for transmission of the transport block.
In some example implementations, the network device 110 may determine a time period associated with the expiration time based on a state of a channel between the first device and the second device; and sending an indication of the time period to the first device via feedback.
In some example embodiments, the network device 110 may send scheduling information for transport block retransmissions to the terminal device.
In some example embodiments, means capable of performing the method 500 (e.g., implemented at the terminal device 120) may include means for performing the various steps of the method 500. The apparatus may be implemented in any suitable form. For example, the apparatus may be implemented in a circuit or a software module.
In some example embodiments, the apparatus includes: means for transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block; means for adjusting an expiration time of a configured grant weight transmission timer without initiating autonomous retransmission of the transport block in response to receiving feedback from the second device indicating unsuccessful reception of the transport block; means for determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and means for retransmitting the transport block while stopping configuring the grant weight timer in response to determining that the scheduling information is received.
In some example embodiments, means capable of performing the method 600 (e.g., implemented at the network device 110) may comprise means for performing the steps of the method 600. The apparatus may be implemented in any suitable form. For example, the apparatus may be implemented in a circuit or a software module.
In some exemplary embodiments, the apparatus includes: means for receiving a transport block from a first device; and means for sending feedback to the first device indicating unsuccessful reception of the transport block in response to failure to decode the transport block to trigger the first device to adjust the expiration time of the configured grant weight timer.
Fig. 7 is a simplified block diagram of an apparatus 700 suitable for implementing embodiments of the present disclosure. Device 700 may be provided to implement communication devices such as terminal device 120 and network device 110 shown in fig. 1. As shown, device 700 includes one or more processors 710, one or more memories 740 coupled to processors 710, and one or more transmitters and/or receivers (TX/RX) 740 coupled to processors 710.
TX/RX 740 is used for two-way communication. TX/RX 740 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.
Processor 710 may be of any type suitable to the local technology network and may include, as non-limiting examples, one or more of the following: general purpose computers, special purpose computers, microprocessors, digital Signal Processors (DSPs), and processors based on a multi-core processor architecture. The apparatus 700 may have multiple processors, such as application specific integrated circuit chips that are temporally slaved to a clock that synchronizes the master processor.
Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact Discs (CDs), digital Video Discs (DVDs), and other magnetic and/or optical storage devices. Examples of volatile memory include, but are not limited to, random Access Memory (RAM) 722 and other volatile memory that does not last for the duration of the power outage.
The computer program 730 includes computer-executable instructions that are executed by an associated processor 710. Program 730 may be stored in ROM 1020. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 720.
Implementations of the present invention may be implemented by means of program 730 such that device 700 may perform any of the processes of the present invention as discussed with reference to fig. 3-6. Embodiments of the present disclosure may also be implemented in hardware or a combination of software and hardware.
In some implementations, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (such as in the memory 720) or in other storage devices accessible by the device 700. The device 700 may load the program 730 from a computer readable medium into the RAM 722 for execution. The computer readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig. 8 shows an example of a computer readable medium 800 in the form of a CD or DVD. The computer readable medium has stored thereon the program 730.
In general, various embodiments of the 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 aspects of the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods 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, that are executed in a device on a target real or virtual processor to perform the methods 500 and 600 as described above with reference to fig. 3-6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or separated as desired in various embodiments. Machine-executable instructions of program modules may be executed within local or distributed devices. In distributed devices, program modules may be located in both local and remote memory 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 code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine, partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device or processor to perform the various processes and operations described above. Examples of carrier waves include signals, computer readable media, and the like.
The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a 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.
Moreover, although operations are described in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these details should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features specific to particular implementations. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (36)

1. A first device for communication, comprising:
at least one processor; and
at least one memory including computer program code;
the at least one memory and the computer program code are configured to, with the at least one processor, cause the first device at least to:
transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block;
in response to receiving feedback from the second device indicating unsuccessful receipt of the transport block, adjusting an expiration time of the configured grant weight transmission timer without initiating the autonomous retransmission of the transport block;
determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and
in response to determining that the scheduling information is received, retransmitting the transport block while stopping configuring the grant weight timer.
2. The first device of claim 1, wherein the first device is caused to adjust the expiration time by:
determining a time period associated with the expiration time to be adjusted; and
deferring expiration of the configuration grant weight timer for the period of time.
3. The first device of claim 1, wherein the first device is caused to adjust the expiration time by:
determining a time period associated with an expiration time to be adjusted; and
and adjusting the expiration time of the configuration weight transmission timer according to the time period.
4. The first device of claim 1, wherein the first device is caused to adjust the expiration time by:
in response to receiving the feedback at a physical layer of the first device, suspending delivery of the feedback to a MAC layer of the first device for a period of time associated with an expiration time to be adjusted to defer the expiration time of the configuration grant weight transmission timer.
5. The first device of any of claims 2 to 4, wherein the first device is caused to determine the period of time by:
Receiving control information from the second device; and
the time period associated with the expiration time to be adjusted is determined from the control information.
6. The first device of any of claims 2 to 4, wherein the first device is caused to determine the period of time by:
the time period associated with the expiration time to be adjusted is determined from the feedback.
7. The first device of any of claims 2 to 4, wherein the first device is caused to determine the period of time by:
receiving radio resource control signaling from the second device; and
the time period associated with the expiration time to be adjusted is determined from the radio resource control signaling.
8. The first device of any of claims 2 to 4, wherein the first device is caused to determine the period of time by:
determining a number of hybrid automatic repeat request processes to be retransmitted based on the feedback;
determining a number of occasions to be monitored for receiving control information from the second device based on the number of hybrid automatic repeat request processes to be retransmitted; and
The time period associated with the expiration time to be adjusted is determined based on a time interval corresponding to the number of occasions.
9. The first device of any of claims 2-4, wherein the time period is preconfigured.
10. The first device of claim 1, wherein the first device is further caused to:
in response to determining that the scheduling information for the retransmission of the transport block is not received before the adjusted configuration grant weight transmission timer expires, initiating the automatic retransmission of the transport block for a hybrid automatic repeat request process.
11. The first device of claim 1, wherein the first device is a terminal device and the second device is a network device.
12. A second device for communication, comprising:
at least one processor; and
at least one memory including computer program code;
the at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to at least:
receiving a transport block from a first device; and
in response to a failure to decode the transport block, sending feedback to the first device indicating unsuccessful receipt of the transport block to trigger the first device to adjust an expiration time of a configured grant weight transmission timer, wherein a time period associated with the expiration time is determined based on a state of a channel between the first device and the second device.
13. A second device as claimed in claim 12, wherein the second device is further caused to:
an indication of the time period is sent to the first device via control information for transmission of the transport block.
14. A second device as claimed in claim 12, wherein the second device is further caused to:
an indication of the time period is sent to the first device via the feedback.
15. A second device as claimed in claim 12, wherein the second device is further caused to:
and sending scheduling information for retransmission of the transport block to the first device.
16. The second device according to any of claims 12 to 15, wherein the first device is a terminal device and the second device is a network device.
17. A method for communication at a first device, comprising:
transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block;
in response to receiving feedback from the second device indicating unsuccessful receipt of the transport block, adjusting an expiration time of the configured grant weight transmission timer without initiating the autonomous retransmission of the transport block;
Determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and
in response to determining that the scheduling information is received, retransmitting the transport block while stopping configuring the grant weight timer.
18. The method of claim 17, wherein adjusting the expiration time comprises:
determining a time period associated with the expiration time to be adjusted; and
deferring expiration of the configuration grant weight timer for the period of time.
19. The method of claim 17, wherein adjusting the expiration time comprises:
determining a time period associated with an expiration time to be adjusted; and
and adjusting the expiration time of the configuration weight transmission timer according to the time period.
20. The method of claim 17, wherein adjusting the expiration time comprises:
in response to receiving the feedback at a physical layer of the first device, suspending delivery of the feedback to a MAC layer of the first device for a period of time associated with an expiration time to be adjusted to defer the expiration time of the configuration grant weight transmission timer.
21. The method of any of claims 18 to 20, wherein determining the period of time comprises:
receiving control information from the second device; and
the time period associated with the expiration time to be adjusted is determined from the control information.
22. The method of any of claims 18 to 20, wherein determining the period of time comprises:
the time period associated with the expiration time to be adjusted is determined from the feedback.
23. The method of any of claims 18 to 20, wherein determining the period of time comprises:
receiving radio resource control signaling from the second device; and
the time period associated with the expiration time to be adjusted is determined from the radio resource control signaling.
24. The method of any of claims 18 to 20, wherein determining the period of time comprises:
determining a number of hybrid automatic repeat request processes to be retransmitted based on the feedback;
determining a number of occasions to be monitored for receiving control information from the second device based on the number of hybrid automatic repeat request processes to be retransmitted; and
the time period associated with the expiration time to be adjusted is determined based on a time interval corresponding to the number of occasions.
25. The method of any one of claims 18 to 20, wherein the time period is preconfigured.
26. The method of claim 17, further comprising:
in response to determining that the scheduling information for the retransmission of the transport block is not received before the adjusted configuration grant weight transmission timer expires, initiate the automatic retransmission of the transport block for a hybrid automatic repeat request process.
27. The method of claim 17, wherein the first device is a terminal device and the second device is a network device.
28. A method for communication at a second device, comprising:
receiving a transport block from a first device; and
in response to a failure to decode the transport block, sending feedback to the first device indicating unsuccessful receipt of the transport block to trigger the first device to adjust an expiration time of a configured grant weight transmission timer, wherein a time period associated with the expiration time is determined based on a state of a channel between the first device and the second device.
29. The method of claim 28, further comprising:
an indication of the time period is sent to the first device via control information for transmission of the transport block.
30. The method of claim 28, further comprising:
an indication of the time period is sent to the first device via the feedback.
31. The method of claim 28, further comprising:
and sending scheduling information for retransmission of the transport block to the first device.
32. The method of any of claims 28 to 31, wherein the first device is a terminal device and the second device is a network device.
33. An apparatus for communication, comprising:
means for transmitting a transport block to a second device while starting a configured grant weight timer for autonomous retransmission of the transport block;
means for adjusting an expiration time of the configured grant weight transmission timer without initiating the autonomous retransmission of the transport block in response to receiving feedback from the second device indicating unsuccessful reception of the transport block;
means for determining whether scheduling information for retransmission of the transport block is received before the adjusted configuration grant weight timer expires; and
in response to determining that the scheduling information is received, retransmitting the transport block while stopping configuring the grant weight timer.
34. An apparatus for communication, comprising:
means for receiving a transport block from a first device; and
means for sending feedback to the first device indicating unsuccessful reception of the transport block in response to failure to decode the transport block to trigger the first device to adjust an expiration time of a configuration grant weight transmission timer, wherein a time period associated with the expiration time is determined based on a state of a channel between the first device and a second device.
35. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of any one of claims 17 to 27.
36. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of any one of claims 28 to 32.
CN201980099028.6A 2019-08-06 2019-08-06 Retransmission mechanism for configuring authorized uplink transmissions Active CN114208077B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/099474 WO2021022485A1 (en) 2019-08-06 2019-08-06 Retransmission mechanism for configured grant uplink transmission

Publications (2)

Publication Number Publication Date
CN114208077A CN114208077A (en) 2022-03-18
CN114208077B true CN114208077B (en) 2024-04-05

Family

ID=74503287

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201980099028.6A Active CN114208077B (en) 2019-08-06 2019-08-06 Retransmission mechanism for configuring authorized uplink transmissions

Country Status (4)

Country Link
US (1) US12052109B2 (en)
EP (1) EP4011014A4 (en)
CN (1) CN114208077B (en)
WO (1) WO2021022485A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115314167A (en) * 2021-05-07 2022-11-08 华为技术有限公司 UE transmission parameter adjusting method and device
US20230040421A1 (en) * 2021-07-20 2023-02-09 FG Innovation Company Limited User equipment and method for performing configured grant based small data transmission

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105450368A (en) * 2014-09-24 2016-03-30 上海贝尔股份有限公司 Method and device of HARQ (Hybrid Automatic Repeat Request) on license-free carrier in LTE-LAA (Long Term Evolution-Licensed Assisted Access) system
WO2019030726A1 (en) * 2017-08-11 2019-02-14 Telefonaktiebolaget Lm Ericsson (Publ) Methods for autonomous uplink transmissions and retransmissions

Family Cites Families (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101607325B1 (en) 2008-02-27 2016-03-30 엘지전자 주식회사 Method of retransmitting data signal in wireless communication system
US8386870B2 (en) * 2008-07-03 2013-02-26 Wi-Lan, Inc. Fractional HARQ re-transmission
WO2010044721A1 (en) * 2008-10-17 2010-04-22 Telefonaktiebolaget L M Ericsson (Publ) Method for improving battery life and harq retransmissions in wireless communications systems
KR20110011517A (en) * 2009-07-28 2011-02-08 엘지전자 주식회사 Method for performing carrier management procedure in a multi-carrier supported wideband wireless communication system and appartus for the same
CA2886634C (en) * 2012-09-26 2020-03-24 Interdigital Patent Holdings, Inc. Methods for dynamic tdd uplink/downlink configuration
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
US20140269629A1 (en) * 2013-03-13 2014-09-18 Qualcomm Incorporated Retransmission timer in a high speed data network
US9071433B2 (en) * 2013-03-13 2015-06-30 Qualcomm Incorporated Method and apparatus for improving re-transmission of reconfiguration messages
WO2015023067A1 (en) * 2013-08-12 2015-02-19 삼성전자 주식회사 Method for processing radio link failure in multiple base station connectivity based radio communication system, and apparatus for same
US10355828B2 (en) * 2015-03-02 2019-07-16 Qualcomm Incorporated Fast radio link control error recovery with low latency transmissions
US10057016B2 (en) * 2015-04-09 2018-08-21 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for data transmission
PT3403450T (en) * 2016-01-11 2020-01-03 Ericsson Telefon Ab L M Method for controlling connected mode drx operations
US20170318620A1 (en) * 2016-04-28 2017-11-02 Mediatek Inc. Connected Mode Discontinuous Reception for Narrow Band Internet of Things
US10129827B2 (en) * 2016-05-17 2018-11-13 Samsung Electronics Co., Ltd. UE and method thereof for applying common discontinuous reception configuration
MX2019008369A (en) * 2017-03-23 2019-09-06 Lg Electronics Inc Method and user equipment for receiving downlink signals.
US11330624B2 (en) * 2017-03-24 2022-05-10 Samsung Electronics Co., Ltd. Method and apparatus for listen-before-talk (LBT) related operation in a wireless communication system using unlicensed band
US10721025B2 (en) * 2017-06-15 2020-07-21 Ofinno, Llc Grant-free failure reporting
US11233606B2 (en) * 2017-08-10 2022-01-25 Ofinno, Llc HARQ retransmission and control channel monitoring
US11831436B2 (en) * 2017-09-28 2023-11-28 Comcast Cable Communications, Llc HARQ feedback for grant-free transmission
US20200314658A1 (en) * 2017-10-27 2020-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for scheduling in laa
ES2945473T3 (en) * 2017-11-22 2023-07-03 Fg innovation co ltd Discontinuous receive operations between multiple pieces of bandwidth
US11711171B2 (en) * 2018-01-11 2023-07-25 Huawei Technologies Co., Ltd. System and method for reliable transmission over network resources
KR20210044778A (en) * 2018-08-07 2021-04-23 아이디에이씨 홀딩스, 인크. Method and apparatus for improving HARQ
US10848222B2 (en) * 2018-09-28 2020-11-24 Qualcomm Incorporated Synchronizing timing for updating beam configuration information
CN111148193B (en) * 2018-11-02 2021-09-07 华为技术有限公司 Information transmission method and communication device
US11330443B2 (en) * 2019-01-08 2022-05-10 Ofinno, Llc HARQ feedback for configured grant
US11291048B2 (en) * 2019-02-07 2022-03-29 Ofinno, Llc Listen before talk
US20220104306A1 (en) * 2019-02-13 2022-03-31 Apple Inc. Transmission, retransmission, and hybrid automatic repeat request process using preconfigured uplink resources in idle mode
BR112021016615A2 (en) * 2019-02-22 2021-11-03 Lenovo Singapore Pte Ltd Autonomous data relay drive
KR20200126835A (en) * 2019-04-30 2020-11-09 삼성전자주식회사 Method and apparatus for transmitting and receiving data in a wireless communication system
CN113767704A (en) * 2019-05-01 2021-12-07 苹果公司 Configuration authorization improvements for unlicensed New Radios (NRs)
US11432320B2 (en) * 2019-05-03 2022-08-30 Mediatek Singapore Pte. Ltd. Method and apparatus for autonomous retransmissions on configured grants in mobile communications
US11038628B2 (en) * 2019-05-04 2021-06-15 Qualcomm Incorporated Procedures for configured grants
WO2020228428A1 (en) * 2019-05-13 2020-11-19 Telefonaktiebolaget Lm Ericsson (Publ) Methods, terminal device and network node for uplink transmission
US11356894B2 (en) * 2019-05-14 2022-06-07 Qualcomm Incorporated Method and apparatus for configuring uplink hybrid automatic repeat request (HARQ) retransmission timer for narrowband communications
WO2021008174A1 (en) * 2019-07-12 2021-01-21 Telefonaktiebolaget Lm Ericsson (Publ) Methods, terminal device and network node for uplink transmission

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105450368A (en) * 2014-09-24 2016-03-30 上海贝尔股份有限公司 Method and device of HARQ (Hybrid Automatic Repeat Request) on license-free carrier in LTE-LAA (Long Term Evolution-Licensed Assisted Access) system
WO2019030726A1 (en) * 2017-08-11 2019-02-14 Telefonaktiebolaget Lm Ericsson (Publ) Methods for autonomous uplink transmissions and retransmissions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA 等.Configured grant operation for NR-U.3GPP TSG-RAN WG2 Meeting #106 R2-1906757.2019,全文. *

Also Published As

Publication number Publication date
EP4011014A1 (en) 2022-06-15
WO2021022485A1 (en) 2021-02-11
CN114208077A (en) 2022-03-18
US12052109B2 (en) 2024-07-30
US20220255672A1 (en) 2022-08-11
EP4011014A4 (en) 2023-04-19

Similar Documents

Publication Publication Date Title
CN111742511B (en) Configured authorization operations
KR102376053B1 (en) Discontinuous reception communication method and communication apparatus, communication device and communication system
CN112970301B (en) Acknowledgement for downlink early data transmission in paging messages
WO2021159352A1 (en) Determination of active time with discontinuous reception groups
TW201342966A (en) Update of timing advance without starting discontinuous reception activity timer
JP7327483B2 (en) Method, device and program for multi-TRP transmission
WO2021062713A1 (en) Resource selection for transmission of pending data unit
EP3876464A1 (en) Internet of vehicles data transmission method, transmission terminal and network side device
CN114208077B (en) Retransmission mechanism for configuring authorized uplink transmissions
US20230232371A1 (en) Improving spectrum efficiency in configured grant
EP3417566B1 (en) Terminal device, infrastructure equipment and methods
CN112868261B (en) L1 signaling for serving cells
CN114503771B (en) Termination of a monitoring window during random access
WO2020000429A1 (en) Uplink skipping during random access procedure
US20240334452A1 (en) Method, device and computer readable medium for communication
JP7347664B2 (en) Wireless communication methods, devices and systems
WO2023010580A1 (en) Methods and devices for communication
WO2022213238A1 (en) Reliable transmission on licensed and unlicensed bands
US20240356622A1 (en) Methods and devices for communication
CN117751648A (en) Reliable SPS configuration for MBS
CN118339913A (en) Contention resolution for non-terrestrial networks
CN116724514A (en) Enhancement of autonomous retransmission
CN118542066A (en) Mechanism for authorized transmission of configuration
CN118541959A (en) Enhanced blind retransmission scheme

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant