EP3834552B1 - Kanalkollisionshandhabung mit urllc und ack-feedback-ein/aus für harq-ack von urllc-pdsch-übertragungen - Google Patents

Kanalkollisionshandhabung mit urllc und ack-feedback-ein/aus für harq-ack von urllc-pdsch-übertragungen

Info

Publication number
EP3834552B1
EP3834552B1 EP19847607.9A EP19847607A EP3834552B1 EP 3834552 B1 EP3834552 B1 EP 3834552B1 EP 19847607 A EP19847607 A EP 19847607A EP 3834552 B1 EP3834552 B1 EP 3834552B1
Authority
EP
European Patent Office
Prior art keywords
pucch
ack
urllc
harq
feedback
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
EP19847607.9A
Other languages
English (en)
French (fr)
Other versions
EP3834552A1 (de
EP3834552A4 (de
Inventor
Zhanping Yin
Tatsushi Aiba
Kazunari Yokomakura
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.)
Sharp Corp
Original Assignee
Sharp Corp
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 Sharp Corp filed Critical Sharp Corp
Publication of EP3834552A1 publication Critical patent/EP3834552A1/de
Publication of EP3834552A4 publication Critical patent/EP3834552A4/de
Application granted granted Critical
Publication of EP3834552B1 publication Critical patent/EP3834552B1/de
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/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/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/1861—Physical mapping 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/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
    • H04L1/203—Details of error rate determination, e.g. BER, FER or WER
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • 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/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria

Definitions

  • the present disclosure relates generally to communication systems. More specifically, the present disclosure relates to a user equipment, a base station device, a method performed by a user equipment and a method performed by a base station device.
  • wireless communication devices may communicate with one or more devices using a communication structure.
  • the communication structure used may only offer limited flexibility and/or efficiency.
  • systems and methods that improve communication flexibility and/or efficiency may be beneficial.
  • Document VIVO "Discussion on eMBB and URLLC UCI multiplexing", 3GPP DRAFT; R1-1806064 discusses the case where the HARQ-ACK for URLLC DL may be overlapped in time with eMBB PUSCH. In this case, it is proposed that the HARQ-ACK for URLLC DL needs to be prioritized, i.e.UE follows the later received DL grant to proceed the URLLC HARQ-ACK transmission and cancels eMBB PUSCH transmission.
  • a user equipment includes a higher layer processor configured to configure physical uplink control channel (PUCCH) resources for HARQ-ACK feedback of ultra-reliable low-latency communication (URLLC) physical downlink shared channel (PDSCH) transmissions.
  • the higher layer processor is also configured to determine if there is a collision between a PUCCH for HARQ-ACK feedback of URLLC PDSCH transmissions and other uplink (UL) channels.
  • the higher layer processor is further configured to determine if simultaneous UL transmissions is supported for URLLC transmissions and other UL channels.
  • the UE also includes transmitting circuitry configured to transmit HARQ-ACK feedback for URLLC PDSCH transmission and other UL channels.
  • the UE may transmit the PUCCH for HARQ-ACK feedback of URLLC PDSCH transmission and may drop the overlapping symbols on other UL channels.
  • the UE may transmit the PUCCH for HARQ-ACK feedback of URLLC PDSCH transmissions, and one of the other UL channels with highest priority.
  • the UE includes a higher layer processor configured to configure PUCCH resources for HARQ-ACK feedback of URLLC PDSCH transmission.
  • the higher layer processor is also configured to determine if ACK feedback is on or off for HARQ-ACK feedback of the URLLC PDSCH transmission.
  • the UE also includes transmitting circuitry configured to transmit HARQ-ACK feedback for URLLC DL data based on the configured PUCCH resource and HARQ-ACK status.
  • the ACK feedback for a URLLC PDSCH transmission may be turned off. If the ACK feedback is turned off, and if the HARQ-ACK is corresponding to NACK, the UE may report a NACK using the configured PUCCH resource. If the ACK feedback is turned off, and if the HARQ-ACK is corresponding to ACK, the UE may not transmit a PUCCH corresponding to the PDSCH.
  • the ACK feedback for a URLLC PDSCH transmission may be turned on or off by higher layer signaling (e.g., RRC signaling).
  • the ACK feedback for a URLLC PDSCH transmission may be turned on or off by indication of the fields in the scheduling DCI formats.
  • the ACK feedback for a URLLC PDSCH transmission may be turned on or off by the MCS setting or the scrambling RNTI of the scheduling DCI.
  • the 3rd Generation Partnership Project also referred to as "3GPP," is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems.
  • the 3GPP may define specifications for next generation mobile networks, systems and devices.
  • 3GPP Long Term Evolution is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements.
  • UMTS has been modified to provide support and specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • a wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.).
  • a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc.
  • Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc.
  • PDAs personal digital assistants
  • a wireless communication device is typically referred to as a UE.
  • UE and “wireless communication device” may be used interchangeably herein to mean the more general term “wireless communication device.”
  • a UE may also be more generally referred to as a terminal device.
  • a base station In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB) or some other similar terminology.
  • base station As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station,” “Node B,” “eNB,” “gNB” and/or “HeNB” may be used interchangeably herein to mean the more general term “base station.”
  • the term “base station” may be used to denote an access point.
  • An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices.
  • the term “communication device” may be used to denote both a wireless communication device and/or a base station.
  • An eNB may also be more generally referred to as a base station device.
  • a "cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between an eNB and a UE. It should also be noted that in E-UTRA and E-UTRAN overall description, as used herein, a “cell” may be defined as "combination of downlink and optionally uplink resources.” The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.
  • Configured cells are those cells of which the UE is aware and is allowed by an eNB to transmit or receive information.
  • Configured cell(s) may be serving cell(s). The UE may receive system information and perform the required measurements on all configured cells.
  • Configured cell(s)” for a radio connection may include a primary cell and/or no, one, or more secondary cell(s).
  • Activated cells are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH).
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • 5G Fifth generation (5G) cellular communications
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communication
  • MMTC massive machine type communication
  • a new radio (NR) base station may be referred to as a gNB.
  • a gNB may also be more generally referred to as a base station device.
  • eMBB may be targeted for high data rate
  • URLLC is for ultra-reliability and low latency.
  • the PUCCH for UCI feedback may be enhanced to the same reliability level as the data for URLLC. Due to the ultra-low latency requirements, the PUCCH format 0 (i.e., short PUCCH with up to 2 bits of UCI) is more suitable for URLLC data HARQ-ACK feedback.
  • bit error rate (BER) requirements are applied for ACK to NACK error, and NACK to ACK error.
  • Some differentiation methods may be introduced to provide better protection of NACK feedback than ACK feedback.
  • the PUCCH carrying HARQ-ACK for a URLLC PDSCH may have higher priority than other channels.
  • a PUCCH carrying HARQ-ACK for a URLLC PDSCH transmission may puncture any other UL channels if collision occurs. If the ACK is always reported, excessive dropping of other UL channels may happen since the URLLC data has very low error probability of 10 -5 . Therefore, methods to avoid unnecessary UL channel dropping while providing the desirable reliability may be beneficial.
  • FIG. 1 is a block diagram illustrating one implementation of one or more base stations (gNBs) 160 and one or more user equipments (UEs) 102 in which channel collision handling with ultra-reliable low-latency communication (URLLC), and acknowledgment (ACK) feedback ON/OFF for HARQ-ACK of URLLC physical downlink shared channel (PDSCH) transmissions may be implemented.
  • the one or more UEs 102 communicate with one or more gNBs 160 using one or more antennas 122a-n.
  • a UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using the one or more antennas 122a-n.
  • the gNB 160 communicates with the UE 102 using one or more antennas 180a-n.
  • UL data may include URLLC data.
  • the URLLC data may be UL-SCH data.
  • URLLC-PUSCH i.e., a different Physical Uplink Shared Channel from PUSCH
  • PUSCH may mean any of (1) only PUSCH (e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not regular PUSCH).
  • uplink channels 121 may be used for transmitting Hybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel State Information (CSI), and/or Scheduling Request (SR).
  • HARQ-ACK may include information indicating a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for DL data (i.e., Transport Block(s), Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH (Downlink-Shared Channel)).
  • ACK positive acknowledgment
  • NACK negative acknowledgment
  • DL data i.e., Transport Block(s), Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH (Downlink-Shared Channel)
  • the CSI may include information indicating a channel quality of downlink.
  • the SR may be used for requesting UL-SCH (Uplink-Shared Channel) resources for new transmission and/or retransmission. Namely, the SR may be used for requesting UL resources for transmitting UL data.
  • UL-SCH Uplink-Shared Channel
  • the one or more gNBs 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119, for instance.
  • downlink channels 119 include a PDCCH, a PDSCH, etc. Other kinds of channels may be used.
  • the PDCCH may be used for transmitting Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104 and a UE operations module 124.
  • one or more reception and/or transmission paths may be implemented in the UE 102.
  • only a single transceiver 118, decoder 108, demodulator 114, encoder 150 and modulator 154 are illustrated in the UE 102, though multiple parallel elements (e.g., transceivers 118, decoders 108, demodulators 114, encoders 150 and modulators 154) may be implemented.
  • the transceiver 118 may include one or more receivers 120 and one or more transmitters 158.
  • the one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert signals to produce one or more received signals 116.
  • the one or more received signals 116 may be provided to a demodulator 114.
  • the one or more transmitters 158 may transmit signals to the gNB 160 using one or more antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.
  • the demodulator 114 may demodulate the one or more received signals 116 to produce one or more demodulated signals 112.
  • the one or more demodulated signals 112 may be provided to the decoder 108.
  • the UE 102 may use the decoder 108 to decode signals.
  • the decoder 108 may produce decoded signals 110, which may include a UE-decoded signal 106 (also referred to as a first UE-decoded signal 106).
  • the first UE-decoded signal 106 may comprise received payload data, which may be stored in a data buffer 104.
  • Another signal included in the decoded signals 110 (also referred to as a second UE-decoded signal 110) may comprise overhead data and/or control data.
  • the second UE-decoded signal 110 may provide data that may be used by the UE operations module 124 to perform one or more operations.
  • the UE operations module 124 may enable the UE 102 to communicate with the one or more gNBs 160.
  • the UE operations module 124 may include a UE scheduling module 126.
  • the UE scheduling module 126 may perform collision handling with URLLC, and ACK feedback ON/OFF for HARQ-ACK of URLLC PDSCH transmissions.
  • the HARQ-ACK feedback of a URLLC downlink (DL) data may have the same reliability requirements as the URLLC data transmission itself.
  • the current NR PUCCH design is targeted for an acknowledgment (ACK) miss-detection probability of 1% and negative-acknowledgment (NACK) to ACK error probability of 0.1%. Therefore, some enhancements may be specified to increase the PUCCH reliability for HARQ-ACK feedback of URLLC traffic.
  • PUCCH format 0 is a short PUCCH with 1 or 2 symbols, and is designed for feedback of up to 2 UCI bits.
  • several methods can be considered (e.g., configuring more than one physical resource block (PRB); time domain repetition; transmit diversity; different transmit power settings). These methods can be configured independently or jointly.
  • a new PUCCH format may be defined to capture these enhancements.
  • the URLLC traffic may share the HARQ-ACK processes with eMBB.
  • the number of HARQ-ACK processes for URLLC can be limited (e.g., only 1 or 2 HARQ-ACK processes for URLLC traffic).
  • the PUCCH format for URLLC DL transmission may also provide ultra-reliability and low latency after a URLLC DL transmission. Only short PUCCH may be used for URLLC HARQ-ACK feedback. The position of short PUCCH can be determined dynamically based on URLLC DL data transmission (e.g., immediately after a URLLC DL transmission with a gap satisfying the processing time requirements).
  • URLLC ACK and NACK feedback differentiation is described herein.
  • the BER requirement of HARQ-ACK feedback on PUCCH for a URLLC PDSCH transmission should be the same as or better than the URLLC data channel (e.g., at least 10 -5 or 10 -6 ).
  • the NACK to ACK error probability should be much lower than the ACK to NACK error probability. If an ACK is detected as a NACK, the PDSCH will be re-transmitted and cause unnecessary waste of resource. On the other hand, if a NACK is detected as an ACK, the gNB 160 may assume it is correctly received, and the packet data will be dropped. This may cause much more overhead of re-transmission.
  • the UE 102 may use a whole of the PUCCH resource configured by the parameters. Also, if the HARQ-ACK is corresponding to ACK, the UE 102 may use a part of the PUCCH resource configured by the parameters.
  • NACK should be transmitted with two antenna ports using two PUCCH resources, ACK may be reported with a single antenna port on a single PUCCH resource.
  • the different parameters may be configured independently or jointly for the PUCCH resources of ACK and NACK feedback.
  • the gNB 160 may transmit, by using a higher layer signal(s) (e.g., an RRC message), the parameter(s) used for configuring the PUCCH resource(s) of ACK and NACK.
  • the gNB 160 may transmit, by using DCI included in the DCI format(s) used for scheduling of the PDSCH transmission, the parameter(s) used for indicating the PUCCH resource(s) of ACK and NACK.
  • the PDCCH scheduling the PDSCH transmission (e.g., a control channel element(s) of the PDCCH) may be used for indicating the PUCCH resource(s) of ACK and NACK.
  • the gNB 160 may configure the parameter(s) only for the short PUCCH format(s) (e.g., the PUCCH format 0 and/or the PUCCH format 1).
  • the UE 102 may use the PUCCH resource (i.e., one PUCCH resource(s)) based on the parameter(s) to transmit HARQ-ACK (either ACK or NACK). And, the UE 102 may determine, based on whether the HARQ-ACK is corresponding to ACK or NACK, the amount of resources (e.g., the number of resource elements (RE(s)) in frequency and/or time domain) used for HARQ-ACK feedback. For example, for ACK feedback, the UE 102 may use less amounts of resources than that of resources used for NACK feedback.
  • the PUCCH resource i.e., one PUCCH resource(s)
  • the UE 102 may use less amounts of resources than that of resources used for NACK feedback.
  • how to determine the amount of resources may be determined, in advance, by the specification, etc., (e.g., by using an equation).
  • the gNB 160 may configure, by using the higher layer signal(s), a parameter(s) (e.g., an offset value(s)) used for configuring the amount of resources (e.g., the amount of resource for ACK feedback).
  • the UE 102 may determine, based on the parameter(s) (e.g., the offset value(s)), the amount of resources used for HARQ-ACK feedback (e.g., the amount of resources for ACK feedback) on the PUCCH resource.
  • the PUCCH resource for a NACK feedback may be configured with parameters that provide better BER performance than that of the PUCCH resource for an ACK feedback.
  • the PUCCH resources for ACK and NACK feedback may have different starting PRB indexes and a different number of PRBs.
  • the number of PRBs (e.g., supported number of PRBs) configured for NACK feedback may be higher than that of ACK feedback.
  • the PUCCH resources for ACK and NACK feedback may have a different number of symbols (e.g., supported number of symbols) or number of time domain repetitions (e.g., supported number of time domain repetitions). For example, 1 symbol PUCCH for ACK feedback and 2-symbol PUCCH for NACK feedback.
  • the PUCCH for NACK feedback may be configured with TxD, and the PUCCH for ACK may not be configured with TxD. Namely, only for NACK feedback, two antenna ports transmission may be supported. For example, if the UE 102 is configured with two antenna ports transmission for PUCCH format 0, for HARQ-ACK transmission using PUCCH format 0, the UE 102 may use two antenna ports (with two PUCCH resources) only for NACK feedback, and use single antenna port (with single PUCCH resource) for ACK feedback.
  • the transmit power for a NACK feedback may be configured with a higher value than that of a PUCCH for ACK feedback.
  • the difference between the transmit power or the delta value may be pre-defined or RRC configured to a UE 102.
  • the different parameters may be configured independently or jointly for PUCCH resources of ACK and NACK feedback.
  • the gNB 160 may configure the different parameters for PUCCH resources.
  • the different parameter(s) may include, at least, the parameter(s) described in the method 1.
  • NACK may be reported only on a configured NACK resource (e.g., the PUCCH resource only used for NACK feedback) and ACK may be reported only on a configured ACK resource (e.g., the PUCCH resource only used for ACK feedback).
  • a resource is defined by a sequence and a cyclic shift in each configured RB.
  • one PUCCH resource is configured for a single bit of ACK or NACK feedback (e.g., similar with the method 1)
  • two cyclic shifts with distance of 6 are reserved, and the resource is configured based on the lowest BER requirements between ACK and NACK.
  • each PUCCH resource only reserves one cyclic shift of the sequence. Thus, the PUCCH resource overhead is not increased.
  • the ACK feedback may be turned off, as described in detail below.
  • the UE 102 may be configured with only PUCCH resources for NACK feedback.
  • URLLC PUCCH transmission and collision handling with other UL channels is also described herein.
  • URLLC traffic requires ultra-reliability and low latency.
  • An URLLC UL data transmission may collide with a PUCCH or a PUSCH transmission of the same UE 102 (e.g., on the same symbol).
  • An example of a collision of URLLC PUCCH for HARQ-ACK with other UL channels is illustrated in Figure 4 .
  • the URLLC traffic should have higher priority than any other UL transmissions.
  • the HARQ-ACK feedback of a DL URLLC PDSCH transmission should have higher priority than an UL URLLC data.
  • the PUCCH feedback for a URLLC PDSCH transmission should have the highest priority among all channels or UL transmissions.
  • HARQ-ACK multiplexing on a normal PUSCH transmission may also be difficult.
  • the RE mapping for URLLC HARQ-ACK should be different from normal HARQ-ACK.
  • a much higher beta offset value may be used.
  • the UE 102 may not have enough processing time to handle the PUSCH data puncturing or rate matching.
  • the HARQ-ACK of a URLLC may come at any symbol, if the HARQ-ACK is multiplexed after a DMRS symbol, the timing requirement may be violated for URLLC traffic.
  • the PUCCH carrying HARQ-ACK for URLLC PDSCH may always be transmitted, and the other UL channels may be de-prioritized or dropped.
  • a first SCS may be configured for a first PDCCH and/or a first PDSCH.
  • the first PDCCH may be used for scheduling of the PDSCH.
  • a second SCS may be configured for a second PDCCH and/or a second PDSCH.
  • the second PDCCH may be used for scheduling of the second PDSCH.
  • the first SCS and the second SCS may be configured for the same BWP (e.g., the same DL BWP) and/or the same timing (e.g., the same slot(s) and/or symbol(s)).
  • the UE 102 may perform on the PUCCH, HARQ-ACK transmission corresponding to the first PDSCH (e.g., even if the PUCCH symbol(s) for the first PDSCH and the PUCCH symbols(s) for the second PDSCH are overlapped). In this case, the UE 102 may drop HARQ-ACK transmission for the second PDSCH (e.g., drop the whole symbol of the PUCCH for HARQ-ACK transmission for the second PDSCH).
  • simultaneous UL channel transmission may be supported in Release-16 and later. If supported, the PUCCH for URLLC traffic may be transmitted simultaneously with another PUCCH or PUSCH channel.
  • UL transmit power should be allocated to the PUCCH for URLLC traffic first.
  • the remaining power can be allocated to the remaining REs of the other UL channel in the same UL symbol.
  • power scaling should be performed on the remaining REs of the other UL channel in the same UL symbol to satisfy the Pcmax limit on the given BWP or serving cell.
  • a PUCCH for HARQ-ACK of URLLC PDSCH can be transmitted simultaneously with other UL channels; a URLLC PUSCH (e.g., a sub-slot PUSCH with new MCS table of 10 -5 target BLER) can be simultaneously transmitted with other UL channels; and/or a PUCCH for HARQ-ACK of URLLC PDSCH may be simultaneously transmitted with a URLLC PUSCH transmission by either grant-based or grant-free scheduling.
  • a URLLC PUSCH e.g., a sub-slot PUSCH with new MCS table of 10 -5 target BLER
  • Simultaneous UL channel transmission may be extended to all traffic types (e.g., both PUCCH and PUSCH are for eMBB transmissions).
  • the simultaneous UL channel transmission support may be defined as a separate UE feature, and may be configured to a UE 102 from a gNB 160 by RRC signaling.
  • simultaneous UL transmission may be limited to 2 UL channels.
  • An order of priority may be defined for UL channels from the highest priority to lowest priority (e.g., PUCCH for HARQ-ACK of URLLC PDSCH transmission > PUCCH for SR of URLLC > PUSCH for URLLC > PUCCH for URLLC CSI reporting > PUCCH for HARQ-ACK feedback of eMBB PDSCH > PUCCH for SR of eMBB > PUCCH for CSI feedback of eMBB PDSCH > PUSCH for eMBB).
  • URLLC PUCCH ON/OFF for ACK feedback is also described herein. Due to ultra-reliability of URLLC data transmission, the probability than a NACK is reported is very low at 10 -5 . In another words, 99.999% of HARQ-ACK feedback for URLLC PDSCH will be ACK. If the PUCCH for HARQ-ACK feedback is always reported for a URLLC PDSCH transmission, 99.999% of time ACK is reported.
  • the other UL channel is dropped if method 1 (e.g., URLLC PUCCH punctures any other UL channel) above is applied; or the performance is degraded if method 2 (e.g., simultaneous transmission of PUCCH for URLLC and other channel) above is applied.
  • method 1 e.g., URLLC PUCCH punctures any other UL channel
  • method 2 e.g., simultaneous transmission of PUCCH for URLLC and other channel
  • the ACK feedback can be turned on or off. If the ACK feedback is turned off, only NACK is reported on the PUCCH (e.g., the PUCCH for URLLC DL data). This significantly reduces the number of PUCCH transmissions because the NACK probability is only 10 -5 . Therefore, the other UL channel transmissions are not impacted in most cases.
  • the PDCCH miss-detection probability is 1%
  • the block error rate (BLER) target for a PDSCH decoding is 10%
  • the HARQ-ACK feedback error probability is 1% to 0.1%.
  • a normal HARQ-ACK procedure for a single PDSCH transmission, if a UE 102 does not detect a scheduling DCI correctly for the given PDSCH transmission, no HARQ-ACK is reported and no PUCCH is transmitted.
  • the gNB 160 treats the missing of a corresponding PUCCH feedback as a DTX, and the gNB 160 then retransmits the PDSCH.
  • the gNB 160 cannot differentiate a DTX from an ACK. In case of a DTX occurs, the gNB 160 may think the PDSCH is correctly received because no NACK is reported. However, if the PDCCH miss-detection probability is lower than the data error probability, the PDCCH miss-detection error is acceptable because it already satisfies the data performance criteria. For example, if the expected URLLC data error probability is 10 -5 , and the PDCCH error probability is 10 -5 or 10 -6 , the DTX error is acceptable even if the ACK feedback is turned off.
  • the error probability for a PDSCH already considers necessary PDSCH re-transmissions, and the initial PDSCH transmission probability may be much higher than the expected URLLC data error probability.
  • the initial PDSCH transmission error probability may be 10 -3
  • the PDSCH error probability may be reduced to 10 -5 or 10 -6 .
  • the ACK feedback (e.g., for URLLC PDSCH transmission) may be turned off to avoid excessive dropping of other UL channels.
  • the ACK feedback on/off can be regarded as a special handling of ACK and NACK differentiation. In this extreme case, the ACK does not need to be reported, and only NACK is reported. If the ACK feedback is turned off, the UE 102 can be configured with PUCCH resource for only NACK reporting (e.g., for sequence base format 0 feedback) and only one cyclic shift of a sequence needs to be reserved for the HARQ-ACK feedback. No PUCCH reporting will be treated as an ACK, and the detection of the PUCCH transmission is a NACK. Basically, the NACK feedback is confirmed with ON/OFF keying of PUCCH transmission. The combination of on/off keying and NACK detection on PUCCH will provide higher reliability for the HARQ-ACK feedback.
  • the on/off of ACK feedback may be configured by higher layer signaling. If the ACK feedback (e.g., for URLLC DL transmission) is turned off, the PUCCH resources for HARQ-ACK feedback are configured for only NACK feedback. Namely, the gNB 160 may transmit, by using the higher layer signal(s), a parameter(s) used for indicating whether ACK feedback is performed or not (i.e., ACK feedback is turned on or off). For example, the gNB 160 may configure, per PUCCH format, the parameter(s) used for indicating whether ACK feedback is performed or not.
  • the gNB 160 may configure, per BWP (e.g., UL BWP), the parameter(s) used for indicating whether ACK feedback is performed or not. Also, the gNB 160 may configure, per serving cell, the parameter(s) used for indicating whether ACK feedback is performed or not. Also, the gNB 160 may configure, per PUCCH sell group (e.g., a primary PUCCH group and a secondary PUCCH group), the parameter(s) used for indicating whether ACK feedback is performed or not. And, the UE 102 may determine, based on the parameter(s), whether ACK feedback is performed or not.
  • BWP e.g., UL BWP
  • PUCCH sell group e.g., a primary PUCCH group and a secondary PUCCH group
  • the UE 102 may perform HARQ-ACK (i.e., either ACK or NACK) feedback.
  • HARQ-ACK i.e., either ACK or NACK
  • the gNB 160 may configure first PUCCH resources used for HARQ-ACK (i.e., either ACK or NACK) feedback.
  • the UE 102 may perform HARQ-ACK (i.e., either ACK or NACK) feedback.
  • HARQ-ACK i.e., either ACK or NACK
  • the gNB 160 may configure first PUCCH resources used for HARQ-ACK (i.e., either ACK or NACK) feedback.
  • the UE 102 may perform HARQ-ACK (i.e., either ACK or NACK) feedback.
  • HARQ-ACK i.e., either ACK or NACK
  • the gNB 160 may configure first PUCCH resources used for HARQ-ACK (i.e., either ACK or NACK) feedback.
  • the MCS information field in DCI is 5-bit. If the DCI CRC is scrambled with the new RNTI, the new MCS table is used with a target BLER of 10 -5 , the ACK feedback may be turned off; otherwise, the legacy MCS tables are used with a target BLER of 10%, and the ACK feedback is ON.
  • RRC indicates if the new 64QAM table is configured. The indication for the new MCS table for DL SPS is separate from the one for grant-based DL scheduling. Therefore, if the new MCS table is configured for a DL SPS transmission, the ACK feedback may be turned off; otherwise, the ACK feedback is on.
  • the UE 102 may perform HARQ-ACK (i.e., either ACK or NACK) feedback.
  • the gNB 160 may configure first PUCCH resources used for HARQ-ACK (i.e., either ACK or NACK) feedback.
  • the UE 102 may perform only NACK feedback.
  • the gNB 160 may configure second PUCCH resources used only for NACK feedback.
  • the eMBB PDSCH transmission and the URLLC PDSCH transmission may be identified by information included in the DCI format (e.g., the DCI format used for scheduling of the PDSCH).
  • the eMBB PDSCH transmission and the URLLC PDSCH transmission may be identified by a value(s) set to the PDSCH-to-HARQ-timing indicator field (or 1-bit information).
  • the eMBB PDSCH transmission and the URLLC PDSCH transmission may be identified by the DCI formats (e.g., the long DCI, the compact DCI).
  • the UE 102 may identify eMBB PDSCH transmission based on a detection of the long DCI format (i.e., the first DCI format). For example, based on the detection of the long DCI format, the UE 102 may perform HARQ-ACK (either ACK or NACK) feedback for eMBB PDSCH transmission.
  • the UE 102 may identify URLLC PDSCH transmission based on a detection of the compact DCI format (i.e., the second DCI format). For example, based on the detection of the compact DCI format, the UE 102 may perform only NACK feedback for a URLLC PDSCH transmission.
  • the eMBB PDSCH transmission and the URLLC PDSCH transmission may be identified by the MCS table.
  • the UE 102 may identify eMBB PDSCH transmission based on the MCS table corresponding to the PDSCH transmission. For example, in a case that the PDSCH transmission is corresponding to the old MCS table (i.e., the fist MCS table), the UE 102 may perform HARQ-ACK (either ACK or NACK) feedback for eMBB PDSCH transmission.
  • the UE 102 may identify URLLC PDSCH transmission based on the MCS table corresponding to the PDSCH transmission. For example, in a case that the PDSCH transmission is corresponding to the new MCS table (i.e., the second MCS table), the UE 102 may perform only NACK feedback for URLLC PDSCH transmission.
  • the eMBB PDSCH transmission and the URLLC PDSCH transmission may be identified by RNTI used for scrambling of CRC to be attached to the DCI format.
  • the UE 102 may identify eMBB PDSCH transmission based on a detection of the DCI format with CRC scrambled by the old RNTI (e.g., the C-RNTI).
  • the UE 102 may perform HARQ-ACK (either ACK or NACK) feedback for eMBB PDSCH transmission.
  • the UE 102 may identify URLLC PDSCH transmission based on a detection of the DCI format with CRC scrambled by the new RNTI (e.g., the first RNTI). For example, in a case that the PDSCH transmission is indicated by the DCI format with CRC scrambled by the new RNTI (e.g., the fist RNTI), the UE 102 may perform only NACK feedback for URLLC PDSCH transmission.
  • the new RNTI e.g., the fist RNTI
  • the UE operations module 124 may provide information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the receiver(s) 120 when to receive retransmissions.
  • the UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of a modulation pattern anticipated for transmissions from the gNB 160.
  • the UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the gNB 160.
  • the UE operations module 124 may provide information 142 to the encoder 150.
  • the information 142 may include data to be encoded and/or instructions for encoding.
  • the UE operations module 124 may instruct the encoder 150 to encode transmission data 146 and/or other information 142.
  • the other information 142 may include PDSCH HARQ-ACK information.
  • the encoder 150 may encode transmission data 146 and/or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and/or other information 142 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc.
  • the encoder 150 may provide encoded data 152 to the modulator 154.
  • the UE operations module 124 may provide information 144 to the modulator 154.
  • the UE operations module 124 may inform the modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB 160.
  • the modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.
  • the UE operations module 124 may provide information 140 to the one or more transmitters 158.
  • This information 140 may include instructions for the one or more transmitters 158.
  • the UE operations module 124 may instruct the one or more transmitters 158 when to transmit a signal to the gNB 160.
  • the one or more transmitters 158 may transmit during a UL subframe.
  • the one or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more gNBs 160.
  • the transceiver 176 may include one or more receivers 178 and one or more transmitters 117.
  • the one or more receivers 178 may receive signals from the UE 102 using one or more antennas 180a-n.
  • the receiver 178 may receive and downconvert signals to produce one or more received signals 174.
  • the one or more received signals 174 may be provided to a demodulator 172.
  • the one or more transmitters 117 may transmit signals to the UE 102 using one or more antennas 180a-n.
  • the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.
  • the demodulator 172 may demodulate the one or more received signals 174 to produce one or more demodulated signals 170.
  • the one or more demodulated signals 170 may be provided to the decoder 166.
  • the gNB 160 may use the decoder 166 to decode signals.
  • the decoder 166 may produce one or more decoded signals 164, 168.
  • a first eNB-decoded signal 164 may comprise received payload data, which may be stored in a data buffer 162.
  • a second eNB-decoded signal 168 may comprise overhead data and/or control data.
  • the second eNB-decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module 182 to perform one or more operations.
  • the gNB operations module 182 may enable the gNB 160 to communicate with the one or more UEs 102.
  • the gNB operations module 182 may include a gNB scheduling module 194.
  • the gNB scheduling module 194 may perform operations for channel collision handling with URLLC, and ACK feedback ON/OFF for HARQ-ACK of URLLC PDSCH transmissions as described herein.
  • the gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of a modulation pattern anticipated for transmissions from the UE(s) 102.
  • the gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of an anticipated encoding for transmissions from the UE(s) 102.
  • the gNB operations module 182 may provide information 101 to the encoder 109.
  • the information 101 may include data to be encoded and/or instructions for encoding.
  • the gNB operations module 182 may instruct the encoder 109 to encode information 101, including transmission data 105.
  • the encoder 109 may encode transmission data 105 and/or other information included in the information 101 provided by the gNB operations module 182. For example, encoding the data 105 and/or other information included in the information 101 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc.
  • the encoder 109 may provide encoded data 111 to the modulator 113.
  • the transmission data 105 may include network data to be relayed to the UE 102.
  • the gNB operations module 182 may provide information 103 to the modulator 113.
  • This information 103 may include instructions for the modulator 113.
  • the gNB operations module 182 may inform the modulator 113 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 102.
  • the modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.
  • a DL subframe may be transmitted from the gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160 and the one or more UEs 102 may transmit data in a standard special subframe.
  • one or more of the elements or parts thereof included in the eNB(s) 160 and UE(s) 102 may be implemented in hardware.
  • one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc.
  • one or more of the functions or methods described herein may be implemented in and/or performed using hardware.
  • one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.
  • ASIC application-specific integrated circuit
  • LSI large-scale integrated circuit
  • Figure 20 is a block diagram illustrating one implementation of a UE 2002 in which channel collision handling with URLLC, and ACK feedback ON/OFF for HARQ-ACK of URLLC PDSCH transmissions may be implemented.
  • the UE 2002 includes transmit means 2058, receive means 2020 and control means 2024.
  • the transmit means 2058, receive means 2020 and control means 2024 may be configured to perform one or more of the functions described in connection with Figure 1 above.
  • Figure 18 above illustrates one example of a concrete apparatus structure of Figure 20 .
  • Other various structures may be implemented to realize one or more of the functions of Figure 1 .
  • a DSP may be realized by software.
  • Figure 21 is a block diagram illustrating one implementation of a gNB 2160 in which channel collision handling with URLLC, and ACK feedback ON/OFF for HARQ-ACK of URLLC PDSCH transmissions may be implemented.
  • the gNB 2160 includes transmit means 2123, receive means 2178 and control means 2182.
  • the transmit means 2123, receive means 2178 and control means 2182 may be configured to perform one or more of the functions described in connection with Figure 1 above.
  • Figure 19 above illustrates one example of a concrete apparatus structure of Figure 21 .
  • Other various structures may be implemented to realize one or more of the functions of Figure 1 .
  • a DSP may be realized by software.
  • computer-readable medium refers to any available medium that can be accessed by a computer or a processor.
  • computer-readable medium may denote a computer- and/or processor-readable medium that is non-transitory and tangible.
  • Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method.
  • the method steps and/or actions may be interchanged with one another and/or combined into a single step.
  • the order and/or use of specific steps and/or actions may be modified.

Landscapes

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

Claims (4)

  1. Eine Benutzerausrüstung (User Equipment - UE) (1802), die für den Betrieb gemäß den Standards des 3rd Generation Partnership Project (3GPP) konfiguriert ist, wobei die UE (1802) Folgendes umfasst:
    einen Prozessor (1803), der konfiguriert ist, um Folgendes zu bewerkstelligen:
    Konfigurieren eines physikalischen Uplink-Steuerkanals (Physical Uplink Control CHannel - PUCCH) mit höherer Priorität für ein HARQ-ACK-Feedback, wobei das HARQ-ACK-Feedback eine Rückmeldung für eine Downlink-Übertragung eines ultra-zuverlässigen, latenzarmen (DL URLLC) physikalischen gemeinsam genutzten Downlink-Kanals (Physical Downlink Shared CHannel - PDSCH) ist, wobei das HARQ-ACK-Feedback auf dem PUCCH eine höhere Priorität aufweist als jegliche andere Uplink- (UL) Übertragungen, die UL-URLLC-Daten beinhalten; und
    Bestimmen, ob eine Kollision vorliegt zwischen a) dem PUCCH mit höherer Priorität für das HARQ-ACK-Feedback und b) einem physikalischen gemeinsam genutzten Uplink-Kanal (Physical Uplink Shared CHannel - PUSCH) mit niedrigerer Priorität, der früher als der PUCCH mit höherer Priorität beginnt; und
    einen Sender (1858), der konfiguriert ist, um das HARQ-ACK-Feedback auf dem PUCCH mit höherer Priorität zu übertragen, den PUSCH mit niedrigerer Priorität in nicht überlappenden Symbolen zu übertragen und den PUSCH mit niedrigerer Priorität in überlappenden Symbolen zu verwerfen, falls die Kollision auftritt.
  2. Eine Basisstationsvorrichtung (1960), die für den Betrieb gemäß den Standards des 3rd Generation Partnership Project (3GPP) konfiguriert ist, wobei die Basisstationsvorrichtung (1960) Folgendes umfasst:
    einen Sender (1917), der konfiguriert ist, um eine Downlink-Übertragung eines ultra-zuverlässigen, latenzarmen (DL URLLC) physikalischen gemeinsam genutzten Downlink-Kanals (Physical Downlink Shared CHannel - PDSCH) durchzuführen; und
    einen Empfänger (1978), der konfiguriert ist, um einen physikalischen Uplink-Steuerkanal (Physical Uplink Control CHannel - PUCCH) mit höherer Priorität für ein HARQ-ACK-Feedback zu empfangen, wobei das HARQ-ACK-Feedback eine Rückmeldung für die DL-URLLC-PDSCH-Übertragung ist, wobei das HARQ-ACK-Feedback auf dem PUCCH eine höhere Priorität aufweist als jegliche andere Uplink- (UL) Übertragungen, die UL-URLLC-Daten beinhalten; wobei
    im Falle einer Kollision zwischen a) dem PUCCH mit höherer Priorität für das HARQ-ACK-Feedback und b) einem physikalischen gemeinsam genutzten Uplink-Kanal (Physical Uplink Shared CHannel - PUSCH) mit niedrigerer Priorität, der früher als der PUCCH mit höherer Priorität beginnt, der Empfänger (1978) dazu konfiguriert ist, während der PUCCH mit höherer Priorität empfangen wird, den PUSCH mit niedrigerer Priorität in nicht überlappenden Symbolen zu empfangen, ohne den PUSCH mit niedrigerer Priorität in überlappenden Symbolen zu empfangen.
  3. Ein Verfahren, das von einer Benutzerausrüstung (User Equipment - UE) (102, 1702, 1802) durchgeführt wird, zum Betrieb gemäß den Standards des 3rd Generation Partnership Project (3GPP), wobei das Verfahren Folgendes umfasst:
    Konfigurieren eines physikalischen Uplink-Steuerkanals (Physical Uplink Control CHannel - PUCCH) mit höherer Priorität für ein HARQ-ACK-Feedback, wobei das HARQ-ACK-Feedback eine Rückmeldung für eine Downlink-Übertragung eines ultra-zuverlässigen, latenzarmen (DL URLLC) physikalischen gemeinsam genutzten Downlink-Kanals (Physical Downlink Shared Channel - PDSCH) ist, wobei das HARQ-ACK-Feedback auf dem PUCCH eine höhere Priorität aufweist als jegliche andere Uplink- (UL) Übertragungen, die UL-URLLC-Daten beinhalten; und
    Bestimmen, ob eine Kollision vorliegt zwischen a) dem PUCCH mit höherer Priorität für das HARQ-ACK-Feedback und b) einem physikalischen gemeinsam genutzten Uplink-Kanal (Physical Uplink Shared CHannel - PUSCH) mit niedrigerer Priorität, der früher als der PUCCH mit höherer Priorität beginnt; wobei
    im Falle des Auftretens einer Kollision das Verfahren ferner Folgendes umfasst:
    Senden der HARQ-ACK-Rückmeldung auf dem PUCCH mit höherer Priorität;
    Senden des PUSCH mit niedrigerer Priorität in nicht überlappenden Symbolen; und
    Verwerfen des PUSCH mit niedrigerer Priorität in überlappenden Symbolen.
  4. Ein Verfahren, das von einer Basisstationsvorrichtung (160, 1660, 1960) durchgeführt wird, zum Betrieb gemäß den Standards des 3rd Generation Partnership Project (3GPP), wobei das Verfahren Folgendes umfasst:
    Durchführen einer Downlink-Übertragung eines ultra-zuverlässigen, latenzarmen (DL URLLC) physikalischen gemeinsam genutzten Downlink-Kanals (Physical Downlink Shared CHannel - PDSCH); und
    Empfangen eines physikalischen Uplink-Steuerkanals (Physical Uplink Control CHannel - PUCCH) mit höherer Priorität für ein HARQ-ACK-Feedback, wobei das HARQ-ACK-Feedback eine Rückmeldung für die DL-URLLC-PDSCH-Übertragung ist, wobei das HARQ-ACK-Feedback auf dem PUCCH eine höhere Priorität aufweist als jegliche andere Uplink- (UL) Übertragungen, die UL-URLLC-Daten beinhalten; wobei
    im Falle einer Kollision zwischen a) dem PUCCH mit höherer Priorität für das HARQ-ACK-Feedback und b) einem physikalischen gemeinsam genutzten Uplink-Kanal (Physical Uplink Shared CHannel - PUSCH) mit niedrigerer Priorität, der früher als der PUCCH mit höherer Priorität beginnt, das Verfahren ferner Folgendes umfasst:
    während der PUCCH mit höherer Priorität empfangen wird, Empfangen des PUSCH mit niedrigerer Priorität in nicht überlappenden Symbolen, ohne den PUSCH mit niedrigerer Priorität in überlappenden Symbolen zu empfangen.
EP19847607.9A 2018-08-09 2019-08-07 Kanalkollisionshandhabung mit urllc und ack-feedback-ein/aus für harq-ack von urllc-pdsch-übertragungen Active EP3834552B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862716836P 2018-08-09 2018-08-09
PCT/JP2019/031097 WO2020032096A1 (en) 2018-08-09 2019-08-07 CHANNEL COLLISION HANDLING with URLLC, and ACK FEEDBACK ON/OFF for HARQ-ACK of URLLC PDSCH TRANSMISSIONS

Publications (3)

Publication Number Publication Date
EP3834552A1 EP3834552A1 (de) 2021-06-16
EP3834552A4 EP3834552A4 (de) 2022-03-02
EP3834552B1 true EP3834552B1 (de) 2025-10-01

Family

ID=69415532

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19847607.9A Active EP3834552B1 (de) 2018-08-09 2019-08-07 Kanalkollisionshandhabung mit urllc und ack-feedback-ein/aus für harq-ack von urllc-pdsch-übertragungen

Country Status (6)

Country Link
US (1) US11943061B2 (de)
EP (1) EP3834552B1 (de)
CN (1) CN112567849B (de)
BR (1) BR112021001565A8 (de)
PH (1) PH12021550253A1 (de)
WO (1) WO2020032096A1 (de)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021088062A1 (zh) * 2019-11-08 2021-05-14 华为技术有限公司 一种通信方法及装置
CN111901882B (zh) * 2020-01-17 2025-05-30 中兴通讯股份有限公司 信道冲突处理方法、装置、设备和存储介质
US20230046231A1 (en) * 2020-01-21 2023-02-16 Qualcomm Incorporated Different reliability levels for acknowledgement/negative acknowledgement (ack/nack) transmissions
CN111432350B (zh) * 2020-02-27 2022-04-29 咪咕文化科技有限公司 通信业务复用方法、电子设备与存储介质
KR20210109254A (ko) * 2020-02-27 2021-09-06 삼성전자주식회사 통신 시스템에서 단말의 소프트버퍼 관리 방법 및 장치
CN115245024B (zh) * 2020-04-10 2025-11-25 捷开通讯(深圳)有限公司 处理多个高优先级上行传输的方法以及用户设备
CN115462145A (zh) * 2020-04-22 2022-12-09 日本电气株式会社 用于通信的方法、终端设备、网络设备和计算机可读介质
US11844103B2 (en) * 2020-06-24 2023-12-12 Qualcomm Incorporated Management of single-shot HARQ-ACK codebooks along with HARQ-ACK codebooks with set priority levels
US12219563B2 (en) * 2020-07-27 2025-02-04 Samsung Electronics Co., Ltd. Systems, methods, and apparatus for multiplexing control information on a physical channel
CN114070481B (zh) * 2020-07-31 2023-08-11 中国信息通信研究院 一种物理信道的传输方法和设备
CN114070526B (zh) * 2020-08-07 2023-04-25 维沃移动通信有限公司 信息确定方法、信息指示方法、终端及网络侧设备
US11778655B2 (en) * 2020-11-16 2023-10-03 Qualcomm Incorporated Techniques for configuring multiple frequency domain opportunities for sidelink feedback
US11716753B2 (en) * 2021-01-26 2023-08-01 Qualcomm Incorporated Feedback methods for subband full duplex systems
CN113347730B (zh) * 2021-06-21 2022-08-19 展讯通信（上海）有限公司 静态调度方法及装置、可读存储介质、终端
US20230163897A1 (en) * 2021-11-24 2023-05-25 Qualcomm Incorporated Type 3 hybrid automatic repeat request codebook feedback triggering
US12532315B2 (en) * 2022-02-11 2026-01-20 Qualcomm Incorporated Managing overlap between uplink control channel repetitions and uplink data transmissions

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011041623A1 (en) * 2009-10-01 2011-04-07 Interdigital Patent Holdings, Inc. Uplink control data transmission
US9137804B2 (en) * 2011-06-21 2015-09-15 Mediatek Inc. Systems and methods for different TDD configurations in carrier aggregation
WO2014046374A1 (ko) * 2012-09-19 2014-03-27 엘지전자 주식회사 상향링크 제어정보 전송 방법 및 장치
CN110622451B (zh) * 2017-05-03 2022-09-09 苹果公司 针对基于微时隙和基于时隙的传输处理冲突
WO2019024918A1 (en) * 2017-08-04 2019-02-07 Mediatek Inc. ULTRA-LOW LATENCY (URLLC) AND UPLINK TRANSMISSION (UL) COMMUNICATION COLLISION MANAGEMENT WITH IMPROVED MOBILE BAND (EMBB)
TWI697244B (zh) * 2018-08-07 2020-06-21 財團法人資訊工業策進會 用於行動通訊系統之使用者裝置及基地台

Also Published As

Publication number Publication date
BR112021001565A2 (pt) 2021-04-20
EP3834552A1 (de) 2021-06-16
CN112567849B (zh) 2024-10-15
EP3834552A4 (de) 2022-03-02
PH12021550253A1 (en) 2021-11-03
BR112021001565A8 (pt) 2022-06-28
US20210314104A1 (en) 2021-10-07
CN112567849A (zh) 2021-03-26
US11943061B2 (en) 2024-03-26
WO2020032096A1 (en) 2020-02-13

Similar Documents

Publication Publication Date Title
EP3834552B1 (de) Kanalkollisionshandhabung mit urllc und ack-feedback-ein/aus für harq-ack von urllc-pdsch-übertragungen
US12003330B2 (en) System and method of HARQ-ACK timing and PUCCH resource determination for ultra-low latency PDSCH transmission
US11706766B2 (en) PUCCH collision handling for multi-slot long PUCCH in 5G NR
WO2020031918A1 (en) ACK and NACK DIFFERENTIATION ON PUCCH for HARQ-ACK FEEDBACK of URLLC PDSCH TRANSMISSIONS
WO2020026708A1 (en) User equipments, base stations and methods for uplink multiplexing
US11997042B2 (en) Simultaneous HARQ-ACK and SR transmission on NR PUCCH
WO2020067515A1 (en) User equipment and base stations that achieve ultra reliable and low latency communications
EP3619861B1 (de) Hybrid automatic repeat request für ultrazuverlässige und niedriglatente uplink-kommunikationen
US12256393B2 (en) Multiplexing HARQ-ACK of different service types on a single PUSCH
US11647513B2 (en) User equipment, a base station apparatus, a communication method of a user equipment and a communication method of a base station apparatus
US12003334B2 (en) URLLC physical uplink control channel (PUCCH) configuration with sub-slot structure
US20200008189A1 (en) Ultra-Reliability Design for Physical Uplink Control Channel (PUCCH) in 5th Generation (5G) New Radio (NR)
WO2020145357A1 (en) Subslot-based harq-ack timing and pucch resource determination for ultra-low latency pdsch transmission
EP3909357B1 (de) Verstärkungen eines physikalischen uplink-steuerkanals mit niedriger latenzzeit (pucch) und ressourcenkonfiguration
WO2020022482A1 (en) Low latency physical uplink control channel (pucch) configuration and resource allocation

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210305

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: FG INNOVATION COMPANY LIMITED

Owner name: SHARP KABUSHIKI KAISHA

A4 Supplementary search report drawn up and despatched

Effective date: 20220128

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/04 20090101ALI20220124BHEP

Ipc: H04W 72/04 20090101AFI20220124BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20230215

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20240918

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTC Intention to grant announced (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SHARP KABUSHIKI KAISHA

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20250310

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Ref country code: CH

Ref legal event code: F10

Free format text: ST27 STATUS EVENT CODE: U-0-0-F10-F00 (AS PROVIDED BY THE NATIONAL OFFICE)

Effective date: 20251001

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602019076458

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20251001

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1843934

Country of ref document: AT

Kind code of ref document: T

Effective date: 20251001

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20251001

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20251001

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20260101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20251001

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20251001

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20251001

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20260101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20260201