WO2018024946A1 - Réémissions en aveugle sur ressources partagées - Google Patents

Réémissions en aveugle sur ressources partagées Download PDF

Info

Publication number
WO2018024946A1
WO2018024946A1 PCT/FI2017/050562 FI2017050562W WO2018024946A1 WO 2018024946 A1 WO2018024946 A1 WO 2018024946A1 FI 2017050562 W FI2017050562 W FI 2017050562W WO 2018024946 A1 WO2018024946 A1 WO 2018024946A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
initial transmission
blind
decoded
blind retransmission
Prior art date
Application number
PCT/FI2017/050562
Other languages
English (en)
Inventor
Renato ABREU
Gilberto BERARDINELLI
Preben Mogensen
Klaus Pedersen
Original Assignee
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 Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2018024946A1 publication Critical patent/WO2018024946A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/189Transmission or retransmission of more than one copy of a message
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1896ARQ related signaling

Definitions

  • MTC machine type communications
  • Pre-scheduling resources conservatively for robust transmissions can reduce the signaling overhead and delays caused by the request/grant procedure, while achieving reliability and latency requirements associated with URLLC.
  • a procedure can easily drain the capacity of the network.
  • the pre-scheduling allocation for unpredictable data traffic could result in waste of radio resources when there is no data available for transmission.
  • a UE/device operating in semi-persistent scheduling mode may occupy the assigned resource from a radio perspective, no matter whether the resource is used for data transmission or not.
  • Contention based access schemes in which the resources are not UE-specific but allocated to a group of UEs, combined with semi-persistent allocation, can give opportunity for the UEs to transmit sporadic data over the shared resources with reduced request/grant signaling (and reduced associated overhead).
  • collisions may happen if more than one UE uses the shared resource at the same instant, which can result in failures for decoding the transmitted block of data.
  • BLER block error rate
  • MTC may exploit the usage of blind retransmissions in a proactive way, in order to increase the success probability of transmitting a message with low delay penalty. Instead of transmitting and waiting for the feedback to retransmit, the node may just aggressively retransmit for a predetermined number of attempts or until a positive acknowledgement is received.
  • this method can also lead to poor resource utilization, since further retransmissions might not be needed if the message was already detected on the initial transmissions.
  • Figure 1 illustrates a method according to certain embodiments.
  • Figure 2 illustrates resource allocation according to certain embodiments.
  • Figure 3 illustrates an example of downlink transmission according to certain embodiments.
  • Figure 4 illustrates using semi-persistent uplink allocation for different UEs, according to certain embodiments.
  • Figure 5 illustrates an access node method according to certain embodiments.
  • Figure 6 illustrates a trend plot of resolved packet using various approaches.
  • Figure 7 illustrates a receiver method according to certain embodiments.
  • Figure 8 illustrates a method according to certain embodiments.
  • FIG. 9 illustrates a system according to certain embodiments.
  • Certain embodiments relate to a 5G new radio (NR) architecture, with focus on ultra-reliable and low latency communication (URLLC) use cases.
  • NR new radio
  • URLLC ultra-reliable and low latency communication
  • certain embodiments may help a system meet stringent latency and reliability requirements, such as 1-10 "5 within 1ms, and average user plane latency of 0.5ms.
  • certain embodiments may meet these requirements in an efficient way, without draining network capacity.
  • certain embodiments may provide a procedure to perform blind retransmissions on shared radio resources together with the application of successive interference cancelation to detect remaining non-decoded data with a low delay penalty.
  • Retransmissions may be beneficial to improve reliability, but conventionally the problem is either node, for example a user equipment (UE), performs blind retransmission on dedicated resources, which drains channel capacity, or a delay penalty is incurred due to the round trip time for the ACK/NACK before performing a retransmission.
  • node for example a user equipment (UE)
  • UE user equipment
  • Certain embodiments provide an approach that permits the nodes to perform blind retransmissions with low delay penalty and improved resource utilization. More specifically, certain embodiments provide a scheme to perform efficient transmission for URLLC. Initial transmissions can be scheduled on safer resources, while automatic blind retransmissions can be configured on shared resources. The automatic blind retransmissions can be decoded by eventually relying on a successive interference cancelation receiver.
  • Figure 1 illustrates a method according to certain embodiments.
  • a base station such as a next generation Node B (gNB) can configure semi-persistent or dynamically granted resources for a UE's initial UL transmission, for each of a plurality of UEs.
  • the initial transmission may have a low block error rate (BLER) target, for example 10 "2 , even though this BLER target may be higher than a final error probability, for example 10 "5 .
  • BLER block error rate
  • the BS can also configure the UEs to perform blind retransmissions on shared retransmission channels.
  • the retransmission channels can be shared by multiple UEs with similar traffic characteristics.
  • the configuration can define a certain number K of blind retransmissions.
  • the configuration can be defined such that retransmissions occur until the message is acknowledged. There can a maximum number of blind retransmissions even in this case.
  • the UE can perform the initial transmission in a dedicated channel and, at 140, can perform blind retransmissions on a shared channel. These transmissions and retransmissions can be according to the configuration from 110 and 120. Retransmissions can possibly perform frequency hopping among different shared retransmission channels to harvest diversity gain.
  • the BS can try to decode the initial transmissions from the UEs in their dedicated resources.
  • the BS can store the decoded signals.
  • the BS can attempt decoding the shared channel by subtracting the already decoded signals from the combined received signal.
  • the BS can also store signals decoded from the retransmissions.
  • SIC successive interference cancellation
  • certain embodiments can provide a method for scheduling and combining initial transmission on protected resources with automatic blind retransmissions on a set of shared resources. Moreover, certain embodiments can provide a procedure for fast decoded retransmissions carried on shared resources using known information from previously decoded transmissions.
  • the BS can configure the UE to perform the UE's initial transmissions on safer or dedicated time- frequency resources.
  • the BS can perform dynamic allocation for the initial transmission.
  • the BS can use a robust radio resource control (RRC) message to configure the resources to occur periodically, as in semi-persistent scheduling.
  • RRC radio resource control
  • the BS can also configure the UE to perform automatic blind retransmissions on certain shared channels. From the UE's perspective, it may be transparent whether the UE is transmitting on a shared resource or not.
  • the BS can also assign reference signals to the UEs to be able to detect each UE's transmissions and estimate the channel.
  • the number of shared channels and number of consecutive retransmissions can be flexibly set.
  • the BS can define and assign them according the load of the network and quality of service (QoS) requirements.
  • the BS can configure the UE to retransmit until the UE receives feedback to stop, which may be a more controlled solution with the price of more signaling.
  • Another possibility is to configure the UE to retransmit a fixed amount of repetitions, reducing the dependency of feedback signaling.
  • the UE can also be configured to drop the packet retransmission if a certain time deadline is reached.
  • the BS could possibly assign more than one parallel shared retransmission channel for the UE, that is, a shared resource pool for retransmissions.
  • the UE could, for instance, select randomly how many and/or which of the shared resources to use for retransmission.
  • Retransmissions can perform frequency hopping to improve diversity or for other reasons, such as load balancing or fairness.
  • An identifier (ID) or a preamble can be used to identify each retransmission.
  • the BS and the UE can agree on a seed for a pseudo-random sequence that can determine which resources from the pool will be used.
  • the modulation and coding scheme (MCS) for the initial transmission can be set to achieve a relatively low BLER target, such as 10 "2 , even though it is not necessarily as low as the final error probability, such as 10 "5 .
  • the retransmissions can possibly use the same MCS, and can rely on soft combining gain to improve the chances of correct detection.
  • the UE may be able to regularly use the UE's pre-scheduled resources whenever the UE has data available for transmission, reducing control overhead, latency and error probability on control signaling.
  • the UE can transmit the UE's available data on the initial protected resources and can then perform blind retransmission on the shared resources.
  • the retransmissions can be simple repetitions of the same packet or can be different redundant versions of the same packet.
  • Figure 2 illustrates resource allocation according to certain embodiments.
  • Figure 2 shows one example related to scheduling and transmission procedures.
  • Figure 2 is a simple illustration of one possible realization.
  • the time- frequency position of the resources might not necessarily be aligned as shown.
  • seven UEs can perform their initial transmission in dedicated resources.
  • such transmissions can be assumed to happen simultaneously over different frequency resources.
  • all the UEs can be allocated a set of shared resources.
  • the receiver was not able to decode UE2 and UE3 on the initial transmission (BLER > 10%), for the second transmission (first retransmission) the signals from UE5 and UE6 decoded on initial transmission can be cancelled from the signal of UE3.
  • the signal of UE3 can be successfully decoded.
  • the same can happen with UE2 on the next retransmission.
  • the non-decoded transmissions may happen on different shared retransmission resources, sorted by the UEs.
  • the number of shared channels can decrease with the time to reduce resource utilization.
  • the UEs may have similar traffic characteristics, such as all being MTC devices. Thus, it may be possible to have the joint transmission on the same resources.
  • Figure 3 illustrates an example of downlink transmission according to certain embodiments.
  • the BS can transmit different packets to the same UE. This can be done using shared blind retransmission on downlink.
  • the combined transmission could be performed as GF(2) addition or a signal superposition. Assuming that there is a high probability that datal or data2 is decoded on the initial transmission, the UE could cancel the decoded one from dataC and decode the other one.
  • Figure 4 illustrates using semi-persistent uplink allocation for different UEs, according to certain embodiments. More particularly, Figure 4 shows another example using semi-persistent uplink allocation for different UEs and two parallel shared retransmission channels.
  • TTI transmission time interval
  • SPS semi-persistent scheduling
  • side (a) shows resource scheduling from a base station perspective
  • side (b) shows resource scheduling from a UE4 perspective.
  • UE4 for example, if the device has data to transmit, it transmits in its periodic resource and, in this example, performs two blind retransmissions on a randomly selected shared retransmission channel. If the UE4 message is not decoded from the initial transmission, the BS may be able to remove the interference from other detected UEs on the shared resource and finally decode UE4. The BS can balance the amount of scheduled resources and the number of UEs sharing the retransmission channels in order to achieve a required decoding performance.
  • Figure 5 illustrates an access node method according to certain embodiments.
  • Figure 5 illustrates a procedure on the BS side that may be applied for each admitted UE for UL transmissions.
  • the BS can perform an iterative decoding process until each transmission is resolved, or the BS can initially configure the UE to drop the packet if a certain latency deadline cannot be reached anymore.
  • the BS can connect a new URLLC UE. Then, at 2, the BS can configure the UE to use pre-defined/periodic dedicated resources for initial transmission. The BS can also, at 3, configure the UE to use a pre-defined shared resource pool for up to T blind retransmissions. Although 2 and 3 are shown in this order, the order could be reversed or the two could be done at essentially the same time, using the same message. Likewise, at 4 the BS can configure the UE to either stop transmitting after K retransmissions or stop if an acknowledgment (ACK) is received.
  • ACK acknowledgment
  • the BS can receive a next UE transmission on a dedicated resource and can try to decode the transmission.
  • a determination can be made as to whether the transmission is decoded. If so, at 13 an acknowledgment of the decoded transmission can be provided. Otherwise, at 7, a determination can be made as to whether the UE can do another retransmission. If not, then the BS can simply wait for the next received transmission at 5. Otherwise, at 8, the BS can receive the next transmission on a shared resource.
  • the BS can identify the UE(s) transmitting on the shared resource.
  • the BS can also, at 10, reconstruct and subtract signals of decoded UEs from the shared resources.
  • the BS can combine the signal of the UE with the UE's previous transmissions and attempt to decode. If the transmission is not decoded, the method can retum to step 7. Otherwise, the if the transmission is decoded, an acknowledgment of the decoded transmission can be provided at 13.
  • the received signal on the shared resource can be the combination of the transmissions from all the UEs retransmitting on that channel, considering also the channel effect over each transmission.
  • n k denotes the noise power
  • the receiver may be able to estimate the UEs channels h t (by using configured reference symbols for instance) and may be able to reconstruct the signal from the previously decoded ones. After that, the receiver can cancel interference over the non-decoded signals. That can be part of the SIC decoding process. Ideally, each successfully decoded replica may permit removal of its interference on the other replicas, at each retransmission.
  • Figure 6 illustrates a trend plot of resolved packet using various approaches.
  • Figure 6 illustrates a trend plot for the overall number of resolved transmissions over time when comparing a proposed solution according to certain embodiments and a non-scheduled access approach.
  • Figure 7 illustrates a receiver method according to certain embodiments.
  • a method can include, at 1 , receiving an initial transmission on a safer resource, such as a dedicated channel.
  • the receiver can estimate and store decoded transmissions.
  • the receiver can determine whether the entire transmission is decoded. If so, then at 6 the method can end. Otherwise, at 4, the receiver can receive a shared resource with joint blind retransmissions.
  • the receiver can then, at 5, cancel interference caused by the decoded signals against the un-decoded signals.
  • the receiver can estimate and store any further decoded transmissions. This process can continue to cycle through multiple repetitions of retransmission.
  • Figure 8 illustrates a method according to certain embodiments.
  • the method can include, at 810, providing a dedicated channel for a user equipment for initial uplink transmission of a message by the user equipment.
  • the method can also include, at 820, providing a shared channel for the user equipment for blind retransmissions of the message.
  • the method can further include, at 830, attempting to decode the initial uplink transmission received on the dedicated channel.
  • the method can further include, at 840, attempting to decode the blind retransmissions on the shared channel.
  • the attempting to decode the blind retransmissions can include, at 845, subtracting already decoded signals from a combined received signal.
  • the providing the dedicated channel, at 810 can include configuring a user equipment with semi-persistent or dynamically granted resources.
  • the providing the shared channel, at 820 can include providing a set of shared retransmission channels.
  • the providing the shared channel, at 820 can include configuring the user equipment to perform an identified number of blind retransmissions.
  • the providing the shared channel, at 820 can include grouping the user equipment with a plurality of other user equipment based on at least one traffic characteristic. For example, various MTC devices can be grouped together because they are MTC devices.
  • the providing the shared channel, at 820 can include configuring the user equipment to perform blind retransmissions until the message is acknowledged.
  • a maximum number of retransmissions or a maximum duration can be configured in case the acknowledgment takes too long or never comes.
  • the above-described features of Figure 8 can be performed by an access node, such as a base station or gNB.
  • the following features can be performed by another device, such as a user equipment.
  • the method can include, at 850, receiving a configuration of a dedicated channel for a user equipment for initial uplink transmission of a message by the user equipment. This can be the same configuration provided at 810.
  • the method can also include, at 860, receiving a configuration of a shared channel for the user equipment for blind retransmissions of the message. This can be the same configuration provided at 820.
  • the method can further include, at 870, performing an initial uplink transmission of the message using the dedicated channel. This can be the same transmission on which a decoding attempt is made at 830.
  • the method can also include, at 880, performing blind retransmission of the message using the shared channel.
  • the blind retransmission at 880 can include performing frequency hopping among different shared retransmission channels.
  • the receiving the configuration of the dedicated channel, at 850 can include receiving a configuration of semi-persistent or dynamically granted resources.
  • the receiving the configuration of the shared channel, at 860 can include receiving a configuration of a set of shared retransmission channels.
  • the receiving the configuration of the shared channel, at 860 can include receiving a configuration to perform an identified number of blind retransmissions.
  • the receiving the configuration of the shared channel, at 870 can include receiving a configuration to perform blind retransmissions until the message is acknowledged. As mentioned above, this can explicitly or implicitly configure a maximum number of retransmissions or a maximum retransmission duration.
  • the initial transmissions are carried on safer resources.
  • most of the packets may tend to be decoded in a short time.
  • the remaining non-decoded packets can be left to be resolved during the blind retransmissions.
  • the risk of collision after the first transmission attempt increases the overall delay for decoding the packets in loaded scenarios.
  • certain embodiments may have various benefits and/or advantages. For example, certain embodiments may provide reduced BLER and a low delay penalty with aggressive retransmissions. Additionally, certain embodiments may provide reduced susceptibility to signaling issues to perform the retransmissions. Furthermore, certain embodiments may provide improved resource utilization scheduling the retransmissions in shared resources and doing SIC.
  • the receiver node may need to keep track of the signals that were already decoded to be able to perform the interference cancelation during the successive retransmissions. Additionally, the transmitting node may need to keep retransmitting until it receives an ACK or until a max number of transmissions is reached. In scenarios where the data traffic load is not high, there may be less benefit as contrasted with contention based solutions. Thus, certain embodiments may be particularly useful in cases that require ultra-reliable and low latency communication, for example in 5G.
  • Figure 9 illustrates a system according to certain embodiments of the invention. It should be understood that each block of the flowchart of Figures 1, 5, and 8 may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.
  • a system may include several devices, such as, for example, network element 910 and user equipment (UE) or user device 920.
  • the system may include more than one UE 920 and more than one network element 910, although only one of each is shown for the purposes of illustration.
  • a network element can be an access point, a base station, an eNode B (eNB), or any other network element, such as a PCell base station or a PSCell base station.
  • eNB eNode B
  • Each of these devices may include at least one processor or control unit or module, respectively indicated as 914 and 924.
  • At least one memory may be provided in each device, and indicated as 915 and 925, respectively.
  • the memory may include computer program instructions or computer code contained therein, for example for carrying out the embodiments described above.
  • transceiver 916 and 926 may be provided, and each device may also include an antenna, respectively illustrated as 917 and 927. Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to each of the devices. Other configurations of these devices, for example, may be provided.
  • network element 910 and UE 920 may be additionally configured for wired communication, in addition to wireless communication, and in such a case antennas 917 and 927 may illustrate any form of communication hardware, without being limited to merely an antenna.
  • Transceivers 916 and 926 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
  • the transmitter and/or receiver (as far as radio parts are concerned) may also be implemented as a remote radio head which is not located in the device itself, but in a mast, for example.
  • the operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case.
  • One possible use is to make a network element to deliver local content.
  • One or more functionalities may also be implemented as a virtual application that is provided as software that can run on a server.
  • a user device or user equipment 920 may be a mobile station (MS) such as a mobile phone or smart phone or multimedia device, a computer, such as a tablet, provided with wireless communication capabilities, personal data or digital assistant (PDA) provided with wireless communication capabilities, vehicle, portable media player, digital camera, pocket video camera, navigation unit provided with wireless communication capabilities or any combinations thereof.
  • MS mobile station
  • PDA personal data or digital assistant
  • the user device or user equipment 920 may be a sensor or smart meter, or other device that may usually be configured for a single location.
  • an apparatus such as a node or user device, may include means for carrying out embodiments described above in relation to Figures 1, 5, and 8.
  • Processors 914 and 924 may be embodied by any computational or data processing device, such as a central processing unit (CPU), digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable device or a combination thereof.
  • the processors may be implemented as a single controller, or a plurality of controllers or processors. Additionally, the processors may be implemented as a pool of processors in a local configuration, in a cloud configuration, or in a combination thereof.
  • the term circuitry may refer to one or more electric or electronic circuits.
  • the term processor may refer to circuitry, such as logic circuitry, that responds to and processes instructions that drive a computer.
  • the implementation may include modules or units of at least one chip set (e.g., procedures, functions, and so on).
  • Memories 915 and 925 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
  • a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used.
  • the memories may be combined on a single integrated circuit as the processor, or may be separate therefrom.
  • the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • the memory or data storage entity is typically internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider.
  • the memory may be fixed or removable.
  • the memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as network element 910 and/or UE 920, to perform any of the processes described above (see, for example, Figures 1, 5, and 8). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein.
  • Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective- C, C, C++, C#, Java, etc., or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments of the invention may be performed entirely in hardware.
  • a programming language which may be a high-level programming language, such as objective- C, C, C++, C#, Java, etc.
  • a low-level programming language such as a machine language, or assembler.
  • certain embodiments of the invention may be performed entirely in hardware.
  • Figure 9 illustrates a system including a network element 910 and a UE 920
  • embodiments of the invention may be applicable to other configurations, and configurations involving additional elements, as illustrated and discussed herein.
  • multiple user equipment devices and multiple network elements may be present, or other nodes providing similar functionality, such as nodes that combine the functionality of a user equipment and an access point, such as a relay node.
  • an access point such as a relay node.
  • eNB Evolved Node B base station node in LTE
  • a method can include providing a dedicated channel for a user equipment for initial uplink transmission of a message by the user equipment.
  • the method can also include providing a shared channel for the user equipment for blind retransmissions of the message.
  • the method can further include attempting to decode the initial uplink transmission received on the dedicated channel.
  • the method can further include attempting to decode the blind retransmissions on the shared channel.
  • the attempting to decode the blind retransmissions can include subtracting already decoded signals from a combined received signal.
  • the providing the dedicated channel can include configuring a user equipment with semi-persistent or dynamically granted resources.
  • the providing the shared channel can include providing a set of shared retransmission channels.
  • the providing the shared channel can include configuring the user equipment to perform an identified number of blind retransmissions.
  • the providing the shared channel can include grouping the user equipment with a plurality of other user equipment based on at least one traffic characteristic.
  • a method can include receiving a configuration of a dedicated channel for a user equipment for initial uplink transmission of a message by the user equipment.
  • the method can also include receiving a configuration of a shared channel for the user equipment for blind retransmissions of the message.
  • the method can further include performing an initial uplink transmission of the message using the dedicated channel.
  • the method can further include performing blind retransmission of the message using the shared channel.
  • the blind retransmission can include performing frequency hopping among different shared retransmission channels.
  • the receiving the configuration of the dedicated channel can include receiving a configuration of semi-persistent or dynamically granted resources.
  • the receiving the configuration of the shared channel can include receiving a configuration of a set of shared retransmission channels.
  • the receiving the configuration of the shared channel can include receiving a configuration to perform an identified number of blind retransmissions. In a variant, the receiving the configuration of the shared channel can include receiving a configuration to perform blind retransmissions until the message is acknowledged.
  • an apparatus can include means for performing the method according to the first and second embodiments respectively, in any of their variants.
  • an apparatus can include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform the method according to the first and second embodiments respectively, in any of their variants.
  • a computer program product may encode instructions for performing a process including the method according to the first and second embodiments respectively, in any of their variants.
  • a non-transitory computer readable medium may encode instructions that, when executed in hardware, perform a process including the method according to the first and second embodiments respectively, in any of their variants.
  • a system may include at least one apparatus according to the third or fifth embodiments in communication with at least one apparatus according to the fourth or sixth embodiments, respectively in any of their variants.

Landscapes

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

Abstract

Divers systèmes de communication sont susceptibles de tirer profit d'un traitement approprié des émissions. Par exemple, certains systèmes sans fil pourraient tirer profit du traitement approprié de réémissions en aveugle sur des ressources partagées. Un procédé peut comprendre l'étape consistant à mettre en place un canal dédié pour un équipement d'utilisateur en vue d'une émission initiale en liaison montante d'un message par l'équipement d'utilisateur. Le procédé peut également comprendre l'étape consistant à mettre en place un canal partagé pour l'équipement d'utilisateur en vue de réémissions en aveugle du message.
PCT/FI2017/050562 2016-08-05 2017-08-02 Réémissions en aveugle sur ressources partagées WO2018024946A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662371406P 2016-08-05 2016-08-05
US62/371,406 2016-08-05
US201762453776P 2017-02-02 2017-02-02
US62/453,776 2017-02-02

Publications (1)

Publication Number Publication Date
WO2018024946A1 true WO2018024946A1 (fr) 2018-02-08

Family

ID=61074229

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2017/050562 WO2018024946A1 (fr) 2016-08-05 2017-08-02 Réémissions en aveugle sur ressources partagées

Country Status (1)

Country Link
WO (1) WO2018024946A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316395A1 (en) * 2017-05-01 2018-11-01 Qualcomm Incorporated Techniques and apparatuses for priority-based resource configuration
CN109450602A (zh) * 2018-10-18 2019-03-08 无锡北邮感知技术产业研究院有限公司 一种数据传输方法、装置及电子设备
WO2020085885A1 (fr) * 2018-10-26 2020-04-30 엘지전자 주식회사 Procédé et appareil permettant d'effectuer une retransmission dans une communication v2x en nr
WO2020165862A1 (fr) * 2019-02-14 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de retransmission pour des ressources de liaison montante préconfigurées
WO2022027460A1 (fr) * 2020-08-06 2022-02-10 Oppo广东移动通信有限公司 Procédé de communication sans fil, dispositif de terminal et dispositif de réseau
WO2022041084A1 (fr) * 2020-08-27 2022-03-03 北京小米移动软件有限公司 Procédé et appareil de retransmission aveugle, procédé d'indication de retransmission aveugle et appareil

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009010434A2 (fr) * 2007-07-19 2009-01-22 Telefonaktiebolaget L M Ericsson (Publ) Procédé et dispositif de commande des ressources de transmission pour des processus de demande de répétition automatique
US7904034B2 (en) * 2006-12-18 2011-03-08 Samsung Electronics Co., Ltd. Method and system for providing an interference cancellation in a wireless communication system
US7996744B2 (en) * 2007-04-30 2011-08-09 Nokia Corporation Method and apparatus for providing a data retransmission scheme
WO2015072905A1 (fr) * 2013-11-12 2015-05-21 Telefonaktiebolaget L M Ericsson (Publ) Dispositifs et procédés de gestion de (re)transmissions aveugles dans un réseau
WO2016165653A1 (fr) * 2015-04-17 2016-10-20 Mediatek Singapore Pte. Ltd. Procédés et appareil destinés à améliorer une harq avec des répétitions de canaux

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7904034B2 (en) * 2006-12-18 2011-03-08 Samsung Electronics Co., Ltd. Method and system for providing an interference cancellation in a wireless communication system
US7996744B2 (en) * 2007-04-30 2011-08-09 Nokia Corporation Method and apparatus for providing a data retransmission scheme
WO2009010434A2 (fr) * 2007-07-19 2009-01-22 Telefonaktiebolaget L M Ericsson (Publ) Procédé et dispositif de commande des ressources de transmission pour des processus de demande de répétition automatique
WO2015072905A1 (fr) * 2013-11-12 2015-05-21 Telefonaktiebolaget L M Ericsson (Publ) Dispositifs et procédés de gestion de (re)transmissions aveugles dans un réseau
WO2016165653A1 (fr) * 2015-04-17 2016-10-20 Mediatek Singapore Pte. Ltd. Procédés et appareil destinés à améliorer une harq avec des répétitions de canaux

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316395A1 (en) * 2017-05-01 2018-11-01 Qualcomm Incorporated Techniques and apparatuses for priority-based resource configuration
US10484054B2 (en) * 2017-05-01 2019-11-19 Qualcomm Incorporated Techniques and apparatuses for priority-based resource configuration
CN109450602A (zh) * 2018-10-18 2019-03-08 无锡北邮感知技术产业研究院有限公司 一种数据传输方法、装置及电子设备
WO2020085885A1 (fr) * 2018-10-26 2020-04-30 엘지전자 주식회사 Procédé et appareil permettant d'effectuer une retransmission dans une communication v2x en nr
US11469861B2 (en) 2018-10-26 2022-10-11 Lg Electronics Inc. Method and apparatus for performing retransmission in NR V2X
WO2020165862A1 (fr) * 2019-02-14 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de retransmission pour des ressources de liaison montante préconfigurées
WO2022027460A1 (fr) * 2020-08-06 2022-02-10 Oppo广东移动通信有限公司 Procédé de communication sans fil, dispositif de terminal et dispositif de réseau
WO2022041084A1 (fr) * 2020-08-27 2022-03-03 北京小米移动软件有限公司 Procédé et appareil de retransmission aveugle, procédé d'indication de retransmission aveugle et appareil

Similar Documents

Publication Publication Date Title
US11387946B2 (en) Reliable ultra-low latency communications
US10091117B2 (en) Code block segmentation and rate matching for multiple transport block transmissions
WO2018024946A1 (fr) Réémissions en aveugle sur ressources partagées
EP2286537B1 (fr) Augmentation de la fiabilité du protocole de demande automatique de répétition hybride (harq)
JP7221866B2 (ja) 伝送方法及び装置
CN110603881B (zh) Stti与tti传输之间的冲突处理
CN107624227B (zh) 用于在通信中处理束大小的配置的设备和方法
US20200083991A1 (en) Feedback for Data Block Transmission
CN110832944B (zh) 对ul免授权传输—配置及资源捆绑,或与之相关的改进
TWI702815B (zh) 高效混合自動重傳請求運作方法及其使用者設備
JP2022078280A (ja) 通信システム
WO2018201369A1 (fr) Procédé de commande de transmission d'informations, dispositif terminal et dispositif réseau
CN111183603A (zh) Harq编号确定方法、网络设备、终端和计算机存储介质
CN113169828B (zh) 蜂窝无线通信网络中的上行链路混合自动重传请求
US20200015199A1 (en) Uplink grant-free transmission enhancement for latency and reliability
US10931427B2 (en) Network node, client device and methods thereof
CN117751539A (zh) 方法、通信装置和基础设施设备
CN109983818B (zh) 用于发送/接收调度命令的方法和设备
WO2019071463A1 (fr) Demande de répétition automatique hybride sans octroi
WO2023079917A1 (fr) Considérations de ligne de temps et améliorations d'abandon de canal pour une résolution de collision entre de multiples pucch à priorité élevée avec harq-ack et un pusch à faible priorité
US20230261789A1 (en) Method and apparatus for uplink transmission on configured grant resources
WO2023079916A1 (fr) Procédés de résolution de collision entre de multiples pucch à priorité élevée avec harq-ack et un pusch à faible priorité
EP3961946A1 (fr) Procédé de traitement d'informations de rétroaction et dispositif associé
WO2021007796A1 (fr) Signalisation intégrée d'accusés de réception harq
CN115707122A (zh) 一种重传反馈信息的方法及装置

Legal Events

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

Ref document number: 17836466

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17836466

Country of ref document: EP

Kind code of ref document: A1