WO2016109980A1 - Procédé et appareil pour réaliser une transmission de données - Google Patents

Procédé et appareil pour réaliser une transmission de données Download PDF

Info

Publication number
WO2016109980A1
WO2016109980A1 PCT/CN2015/070452 CN2015070452W WO2016109980A1 WO 2016109980 A1 WO2016109980 A1 WO 2016109980A1 CN 2015070452 W CN2015070452 W CN 2015070452W WO 2016109980 A1 WO2016109980 A1 WO 2016109980A1
Authority
WO
WIPO (PCT)
Prior art keywords
retransmission
identifier
component carrier
carrier
channel
Prior art date
Application number
PCT/CN2015/070452
Other languages
English (en)
Inventor
Hongmei Liu
Lei Jiang
Zhennian SUN
Chuangxin JIANG
Gang Wang
Original Assignee
Nec Corporation
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 Nec Corporation filed Critical Nec Corporation
Priority to PCT/CN2015/070452 priority Critical patent/WO2016109980A1/fr
Publication of WO2016109980A1 publication Critical patent/WO2016109980A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling

Definitions

  • Embodiments of the present invention generally relate to communication techniques. More particularly, embodiments of the present invention relate to a method and apparatus for performing data transmission in a cross carrier Hybrid Automatic Repeat Request (HARQ) procedure.
  • HARQ Hybrid Automatic Repeat Request
  • ARQ Automatic repeat request
  • ACK acknowledgment
  • NACK negative acknowledgment
  • Hybrid automatic repeat request is a combination of high-rate forward error-correcting coding and ARQ error-control.
  • HARQ with Chase combining and IR combining is an effective way to decrease the latency and provide time diversity gain for data transmission.
  • unlicensed carrier has been introduced to provide additional spectrum resource.
  • the carrier availability is uncertain due to regulations and there is restriction on the maximum available time.
  • cross carrier HARQ may be employed.
  • Cross carrier HARQ different fiom the legacy HARQ procedure in which first transmission and retransmission are carried on the same component carrier (CC) , refers to a HARQ process in which the component carriers carrying the first transmission and the retransmission are different.
  • the component carrier carrying the first transmission may be an unlicensed carrier
  • the component carrier carrying the retransmission may be a licensed carrier.
  • the present invention proposes a solution for data transmission in a cross carrier HARQ procedure. Specifically, the present invention provides a method and apparatus for indicating the component carrier carrying first transmission that corresponds to retransmission.
  • embodiments of the invention provide a method for performing data transmission in a cross carrier HARQ procedure.
  • the method may comprise: receiving retransmission of a data block from a transmitter, wherein the retransmission is performed by the transmitter in response to receiving a negative acknowledge message, and wherein the negative acknowledge message indicates first transmission of the data block on a first component carrier is failed; obtaining, from the retransmission of the data block, an identifier indicating the first component carrier; and determining the first component carrier based on the identifier.
  • embodiments of the invention provide a method for performing data transmission in a cross carrier HARQ procedure.
  • the method may comprise: in response to receiving a negative acknowledge message from a receiver, setting an identifier indicating a first component carrier that carries first transmission of a data block, wherein the negative acknowledge message indicates the first transmission of the data block on the first component carrier is failed; and transmitting the identifier in retransmission of the data block.
  • embodiments of the invention provide an apparatus for performing data transmission in a cross carrier HARQ procedure.
  • the apparatus may comprise: a receiving unit configured to receive retransmission of a data block from a transmitter, wherein the retransmission is performed by the transmitter in response to receiving a negative acknowledge message, and wherein the negative acknowledge message indicates first transmission of the data block on a first component carrier is failed; an obtaining unit configured to obtain, from the retransmission of the data block, an identifier indicating the first component carrier; and a determining unit configured to determine the first component carrier based on the identifier.
  • embodiments of the invention provide an apparatus for performing data transmission in a cross carrier HARQ procedure.
  • the apparatus may comprise: a setting unit configured to, in response to receiving a negative acknowledge message from a receiver, set an identifier indicating a first component carrier that carries first transmission of a data block, wherein the negative acknowledge message indicates the first transmission of the data block on the first component carrier is failed; and a transmitting unit configured to transmit the identifier in retransmission of the data block.
  • the proposed solution is directed to a cross carrier HARQ procedure, in which the component carrier carrying first transmission of a data block can be indicated by retransmission of the data block.
  • FIG. 1 illustrates a flow chart of a method 100 for performing data transmission in a cross carrier HARQ procedure at a receiver according to embodiments of the invention
  • FIG. 2 illustrates a flow chart of a method 200 for performing data transmission in a cross carrier HARQ procedure at a receiver according to embodiments of the invention
  • FIG. 3 illustrates a flow chart of a method 300 for performing data transmission in a cross carrier HARQ procedure at a receiver according to further embodiments of the invention
  • FIG. 4 illustrates a flow chart of a method 400 for performing data transmission in a cross carrier HARQ procedure at a receiver according to still further embodiments of the invention
  • FIG. 5 illustrates a flow chart of a method 500 for performing data transmission in a cross carrier HARQ procedure at a transmitter according to further embodiments of the invention
  • FIG. 6 illustrates a schematic diagram of a cross carrier HARQ procedure 600 according to embodiments of the invention
  • FIG. 7 illustrates a schematic diagram of a cross carrier HARQ procedure 700 according to further embodiments of the invention.
  • FIG. 8 illustrates a schematic diagram of a cross carrier HARQ procedure 800 according to still further embodiments of the invention.
  • FIG. 9 illustrates a block diagram of an apparatus 900 for performing data transmission in a cross carrier HARQ procedure according to embodiments of the invention.
  • FIG. 10 illustrates a block diagram of an apparatus 1000 for performing data transmission in a cross carrier HARQ procedure according to embodiments of the invention.
  • Embodiments of the present invention are directed to a solution for performing data transmission in a cross carrier HARQ procedure.
  • the solution may be carried out between a receiver and a transmitter.
  • the transmitter performs retransmission of the data block.
  • the receiver may obtain an identifier based on the retransmission, wherein the identifier indicates a component carrier carrying the first transmission. Based on the identifier, the receiver may determine the component carrier carrying the first transmission.
  • the cross carrier HARQ procedure may be used in downlink cellular transmission.
  • the receiver may comprise user equipment (UE) , such as a terminal, a Mobile Terminal (MT) , a Subscriber Station (SS) , a Portable Subscriber Station (PSS) , Mobile Station (MS) , or an Access Terminal (AT) .
  • the transmitter may comprise a base station (BS) , such as a node B (NodeB or NB) , or an evolved NodeB (eNodeB or eNB) .
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • the cross carrier HARQ procedure may be used in D2D transmission.
  • the receiver may be a Device-to-Device (D2D) receiver and the transmitter may be a D2D transmitter.
  • D2D Device-to-Device
  • Embodiments of the present invention may be applied in various communication systems, including but not limited to a Long Term Evolution (LTE) system or a Long Term Evolution Advanced (LTE-A) system.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Advanced
  • FIG. 1 illustrates a flow chart of a method 100 for performing data transmission in a cross carrier HARQ procedure at a receiver according to embodiments of the invention.
  • the method 100 may be performed at a receiver, such as a UE, a D2D receiver, and other suitable device.
  • a receiver may send a negative acknowledge message, for example NACK, to a transmitter to request retransmission.
  • a negative acknowledge message for example NACK
  • the transmitter may retransmit the data block to the receiver.
  • the retransmission of the data block may comprise a data portion and a control portion.
  • the data portion comprises the retransmitted data block, which may be carried on a data channel of the retransmission, for example, PDSCH.
  • the control portion comprises control information of the retransmission, which may be carried on a control channel of the retransmission, for example, PDCCH.
  • the first transmission of the data block may likewise comprise a data portion and a control portion.
  • the data channel and the control channel may be carried on the same component carrier, which may be called as “self-scheduling. ”
  • the data channel and the control channel may be carried on different component carriers, which may be called as “cross carrier scheduling. ”
  • step S110 retransmission of a data block is received from a transmitter.
  • the retransrnission is performed by the transmitter in response to receiving a negative acknowledge message, which indicates first transmission of the data block on a first component carrier is failed.
  • the component carrier carrying the first transmission is different from that carrying the retransmission.
  • the receiver to identify the component carrier of the first transmission of the data block, so as to combine the first transmission and the retransmission to obtain the data block correctly.
  • an identifier indicating the first component carrier is obtained from the retransmission of the data block.
  • the identifier may be obtained in several ways.
  • the identifier may be obtained from a new field predefined in control information transmitted on the control channel of the retransmission.
  • the identifier may be obtained from an existing field reused for indicating the first component carrier.
  • a carrier indication field (CIF) may be reused.
  • the control information of both the first transmission and the retransmission may comprise the CIF.
  • the CIF is a field defined in control channel for indicating the component carrier of the data channel.
  • the receiver may obtain the CIF from the control channel of the retransmission to determine the component carrier of the data channel of the retransmission.
  • the identifier may be indicated by the value of the new field or the reused field.
  • control information may be obtained from a control channel of the retransmission first. Then whether there is a field predefined for the identifier in the control information may be determined.
  • the field predefined for the identifier may be a new field with one or more bits, such as 3 bits.
  • the identifier may be obtained from the predefined field. Details of the embodiment will be described with reference to FIG. 2.
  • whether a relationship between a data channel and a control channel of the retransmission is preconfigured may be determined first.
  • the data channel and the control channel are carried on the same component carrier, it may be determined that the relationship between the data channel and the control channel is preconfigured. If the relationship is preconfigured, it may be determined that the CIF of control information carried by the control channel is reused to indicate the component carrier of the first transmission, instead of indicating the data portion of the retransmission. Then, the identifier may be obtained from the carrier indication field of the control information. Details of the embodiment will be described with reference to FIG. 3.
  • control information may be obtained from a control channel of the retransmission first. Then, whether the component carrier indicated by a carrier indication field of the control information belongs to a set of preconfigured component carriers may be determined. If yes, the identifier may be obtained from the carrier indication field. Details of the embodiment will be described with reference to FIG. 4.
  • the first component carrier is determined based on the identifier.
  • the identifier may be obtained from a dedicated field, such as a new field predefined for the identifier in the control information.
  • the identifier may be obtained from a reused field, such as the CIF.
  • the identifier may comprise 3 bits. The 3 bits may indicate 8 component carriers (such as CC0-CC7) , for example, “000” may indicate CC0, “001” may indicate CC1, and so on.
  • the identifier obtained at step S120 is “000” , it may be determined that the first component carrier is CC0.
  • the identifier obtained at step S120 is “001”
  • the identifier may comprise more than or less than 3 bits.
  • FIG. 2 illustrates a flow chart of a method 200 for performing data transmission in a cross carrier HARQ procedure at a receiver according to embodiments of the invention.
  • the method 200 may be considered as a specific implementation of the method 100 described above with reference to Fig. 1.
  • the identifier may be obtained from a new field of control information of the retransmission, and the new field is predefined for the identifier.
  • Method 200 begins at step S210, in which retransmission of a data block is received from a transmitter.
  • the retransmission of the data block may comprise a data portion and a control portion.
  • the data portion comprises the retransmitted data block, which may be carried on a data channel of the retransmission, for example, PDSCH.
  • the control portion comprises control information of the retransmission, which may be carried on a control channel of the retransmission, for example, PDCCH.
  • the control information is obtained from a control channel of the retransmission.
  • whether there is a field predefined for the identifier in the control information is determined.
  • the identifier is obtained from the predefined field.
  • the field predefined for the identifier may be called as first transmission carrier (FTC) , which may be appended to legacy control information.
  • FTC first transmission carrier
  • the first component carrier is determined based on the identifier. This step is similar to the step S110 of method 100, and details are not described for purpose of brief.
  • FIG. 6 illustrates a schematic diagram of a cross carrier HARQ procedure 600 according to embodiments of the invention.
  • the first transmission is self-scheduling, in which both the control channel, PDCCH 611, and the data channel, PDSCH 612, are carried on a component carrier CC2.
  • the retransmission is cross carrier scheduling, in which the control channel, PDCCH 621, is carried on a component carrier CC0, and the data channel, PDSCH 622, is carried on a component carrier CC1.
  • the value of the CIF carried by the PDCCH 621 is 1, for example “001” , which indicates the component carrier of the PDSCH 622 is CC1.
  • a new field 601 that may be called as first transmission carrier (FTC) is predefined in the PDCCH 611. Since the first transmission is carried on a component carrier CC2, the value of the FTC may be set as 2,for example “010” . As such, when the receiver obtains the identifier from the FTC, it may determine that the component carrier of the first transmission is CC2.
  • FTC first transmission carrier
  • the first transmission may be cross carrier scheduling and the identifier may indicate the component carrier carrying the data channel of the first transmission.
  • the retransmission is not limited to the cross carrier scheduling; alternatively, it may be self-scheduling.
  • FIG. 3 illustrates a flow chart of a method 300 for performing data transmission in a cross carrier HARQ procedure at a receiver according to further embodiments of the invention.
  • the method 300 may be considered as a specific implementation of the method 100 described above with reference to Fig. 1.
  • the relationship between the data channel and the control channel of the retransmission may be preconfigured. For instance, the data channel and the control channel of the retransmission may be on the same component carrier.
  • retransmission of a data block is received from a transmitter.
  • the retransmission of the data block may comprise a data portion and a control portion.
  • the data portion comprises the retransmitted data block, which may be carried on a data channel of the retransmission, for example, PDSCH.
  • the control portion comprises control information of the retransmission, which may be carried on a control channel of the retransmission, for example, PDCCH.
  • step S320 whether a relationship between a data channel and a control channel of the retransmission is preconfigured is determined. There may be several ways to determine whether the relationship is preconfigured. In some embodiments, whether the data channel and the control channel are carried on a same component carrier may be determined; and in response to determining that the data channel and the control channel are carried on the same component carrier, it may be determined that the relationship between the data channel and the control channel is preconfigured. In other words, when the retransmission is self-scheduling, the relationship between the data channel and the control channel may be determined as being preconfigured.
  • the identifier is obtained from a carrier indication field of control information in the control channel.
  • the first component carrier is determined based on the identifier. This step is similar to the step S110 of method 100, and details are not described for purpose of brief.
  • FIG. 7 illustrates a schematic diagram of a cross carrier HARQ procedure 700 according to further embodiments of the invention.
  • the first transmission is self-scheduling, in which both the control channel, PDCCH 711, and the data channel, PDSCH 712, are carried on a component carrier CC2.
  • the retransmission is self-scheduling, in which both the control channel, PDCCH 721, and the data channel, PDSCH 722, are carried on a component carrier CC2.
  • the self-scheduling of the retransmission may be preconfigured, for example, via high layer signaling or specification. As such, there is no need to use the CIF to indicate the PDSCH 722. In this case, the CIF may be used to indicate the component carrier of the first transmission. As shown, the value of the CIF carried by the PDCCH 721 is 2, which indicates the component carrier of the first transmission is CC2.
  • the first transmission may be cross carrier scheduling and the identifier may indicate the component carrier carrying the data channel of the first transmission.
  • FIG. 4 illustrates a flow chart of a method 400 for performing data transmission in a cross carrier HARQ procedure at a receiver according to still further embodiments of the invention.
  • the method 400 may be considered as a specific implementation of the method 100 described above with reference to Fig. 1.
  • the carrier indication field is reused for indicating the first component carrier, that is, the component carrier of the first transmission.
  • retransmission of a data block is received from a transmitter.
  • the retransmission of the data block may comprise a data portion and a control portion.
  • the data portion comprises the retransmitted data block, which may be carried on a data channel of the retransmission, for example, PDSCH.
  • the control portion comprises control information of the retransmission, which may be carried on a control channel of the retransmission, for example, PDCCH.
  • control information is obtained from a control channel of the retransmission.
  • whether the component carrier indicated by a carrier indication field of the control information belongs to a set of preconfigured component carriers is determined.
  • the set of preconfigured component carriers may be determined in advance. In some embodiments, if 5 component carriers (denoted as CC0, CC1, ..., CC4) are configured in a communication system, the set of preconfigured component carriers may comprise one or more component carriers which are available to the communication system and different from CC0 to CC4. For example, unlicensed component carriers CC5 to CC7 may be available to the communication system. Thus, the set ofpreconfigured component carriers may comprise one or more of CC5 to CC7.
  • the carrier indication field is reused to indicate the component carrier of the first transmission, instead of indicating the data portion of the retransmission.
  • the identifier is obtained from the carrier indication field.
  • the first component carrier is determined based on the identifier. This step is similar to the step S110 of method 100, and details are not described for purpose of brief.
  • the relationship between a data channel of the first transmission and a data channel of the retransmission may be preconfigured.
  • the data channel of the retransmission may be preconfigured on a component carrier (for example, denoted as “CC1” )
  • the data channel of the first transmission may be preconfigured on another component carrier (for example, denoted as “CC5” )
  • the preconfiguration may be implemented via high layer signaling or specification.
  • FIG. 8 illustrates a schematic diagram of a cross carrier HARQ procedure 800 according to still further embodiments of the invention.
  • the first transmission is self-scheduling, in which both the control channel, PDCCH 811, and the data channel, PDSCH 812, are carried on a component carrier CC5.
  • the retransmission is cross carrier scheduling, in which the control channel, PDCCH 821 is carried on a component carrier CC0, and the data channel, PDSCH 822, is carried on a component carrier CC1.
  • a set of preconfigured component carriers comprises CC5-CC7
  • the receiver may obtain the identifier that indicates the CC5 is the component carrier of the first transmission.
  • the first transmission may be cross carrier scheduling and the identifier may indicate the component carrier carrying the data channel of the first transmission.
  • the retransmission is not limited to the cross carrier scheduling; alternatively, it may be self-scheduling.
  • FIG. 5 illustrates a flow chart of a method 500 for performing data transmission in a cross carrier HARQ procedure at a transmitter according to further embodiments of the invention.
  • the method 500 may be performed at a transmitter, such as a BS, a D2D transmitter, and other suitable device.
  • the method begins at step S510, in which an identifier indicating a first component carrier that carries first transmission of a data block is set in response to receiving a negative acknowledge message from a receiver.
  • the negative acknowledge message indicates the first transmission of the data block on the first component carrier is failed.
  • the identifier may be set in several ways.
  • the identifier may be set in a new field in control information to be transmitted on the control channel.
  • the identifier may be set in an existing field that is reused for indicating the first component carrier.
  • the CIF may be reused.
  • the identifier may comprise 3 bits. The 3 bits may indicate 8 component carriers (such as CC0-CC7) , for example, “000” may indicate CC0, “001” may indicate CC1, and so on. In this way, if the first component carrier is CC0, the identifier may be set as “000” . Likewise, if the first component carrier is CC1, the identifier may be set as “001” .
  • control information to be transmitted on a control channel of retransmission may comprise a field predefined for the identifier.
  • the predefined field may be for example implemented as a new field of the channel information.
  • the identifier may be set in the predefined field.
  • the relationship between a data channel and a control channel of the retransmission may be preconfigured.
  • the carrier indication field carried by the control channel may be reused to indicate the component carrier of the first transmission, instead of indicating the data portion of the retransmission.
  • the identifier may be set in the CIF of control information that is to be transmitted in a control channel of the retransmission.
  • the data channel and the control channel are configured as being carried on the same component carrier, it may be determined that the relationship between a data channel and a control channel of the retransmission is preconfigured, and thus the identifier may be set in the CIF.
  • the identifier indicating the first component carrier may be set in a carrier indication field of control information to be transmitted in a control channel of the retransmission.
  • the relationship between a data channel of the first transmission and a data channel of the retransmission may be preconfigured.
  • the preconfiguration may be implemented via high layer signaling or specification.
  • the identifier is transmitted in retransmission of the data block.
  • the retransmission of the data block may comprise a data portion and a control portion.
  • the data portion may be carried on a data channel of the retransmission, for example, PDSCH.
  • the control portion comprising control information of the retransmission may be carried on a control channel of the retransmission of the data block, for example, PDCCH.
  • the identifier that is set in the control information may be transmitted on the control channel of the retransmission.
  • FIGs. 9 and 10 relate to block diagrams of apparatus for performing data transmission in a cross carrier HARQ procedure according to embodiments of the invention, respectively.
  • FIG. 9 illustrates a block diagram of an apparatus 900.
  • the apparatus 900 may be implemented at a receiver, for example, a cellular UE, a D2D receiver or any other applicable device.
  • the apparatus 900 comprises: a receiving unit 910 configured to receive retransmission of a data block from a transmitter, wherein the retransmission is performed by the transmitter in response to receiving a negative acknowledge message, and wherein the negative acknowledge message indicates first transmission of the data block on a first component carrier is failed; an obtaining unit 920 configured to obtain, from the retransmission of the data block, an identifier indicating the first component carrier; and a determining unit 930 configured to determine the first component carrier based on the identifier.
  • the obtaining unit 920 may comprise: an information obtaining unit configured to obtain control information from a control channel of the retransmission; a field determining unit configured to determine whether there is a field predefined for the identifier in the control information; and an identifier obtaining unit configured to, in response to that there is a field predefined for the identifier, obtain the identifier from the predefined field.
  • the obtaining unit 920 may comprise: a relationship determining unit configured to determine whether a relationship between a data channel and a control channel of the retransmission is preconfigured; and an identifier obtaining unit configured to, in response to determining that the relationship is preconfigured, obtain the identifier from a carrier indication field of control information in the control channel.
  • the relationship determining unit may be further configured to determine whether the data channel and the control channel are carried on a same component carrier; and in response to determining that the data channel and the control channel are carried on the same component carrier, determine that the relationship between the data channel and the control channel is preconfigured.
  • the obtaining unit 920 may comprise: an information obtaining unit configured to obtain control information from a control channel of the retransmission; a carrier determining unit configured to determine whether the component carrier indicated by a carrier indication field of the control information belongs to a set of preconfigured component carriers; and an identifier obtaining unit configured to, in response to determining that the component carrier indicated by a carrier indication field of the control information belongs to a set of preconfigured component carriers, obtain the identifier from the carrier indication field.
  • the relationship between a data channel of the first transmission and a data channel of the retransmission may be preconfigured.
  • FIG. 10 illustrates a block diagram of an apparatus 1000 for performing data transmission in a cross carrier HARQ procedure according to embodiments of the invention.
  • the apparatus 1000 may be implemented at a transmitter, for example, a BS, a D2D transmitter or any other applicable device.
  • the apparatus 1000 comprises: a setting unit 1010 configured to, in response to receiving a negative acknowledge message from a receiver, set an identifier indicating a first component carrier that carries first transmission of a data block, wherein the negative acknowledge message indicates the first transmission of the data block on the first component carrier is failed; and a transrnitting unit 1020 configured to transmit the identifier in retransmission of the data block.
  • the setting unit 1010 may comprise: a first setting unit configured to set the identifier in a field predefined for the identifier in control information, wherein the control information is to be transmitted on a control channel of the retransmission.
  • the setting unit 1010 may comprise: a second setting unit configured to, in response to the relationship between a data channel of the retransmission and the control channel of the retransmission being preconfigured, set the identifier in a carrier indication field of control information to be transmitted in a control channel of the retransmission.
  • the second setting unit may be further configured to, in response to the data channel and the control channel being carried on the same component carrier, set the identifier in the carrier indication field.
  • the setting unit 1010 may comprise: a third setting unit configured to, in response to that the first component carrier belongs to a set of preconfigured component carriers, set the identifier indicating the first component carrier in a carrier indication field of control information to be transmitted in a control channel of the retransmission.
  • the relationship between a data channel of the retransmission and a data channel of first transmission may be preconfigured.
  • apparatuses 900 and 1000 may be respectively implemented by any suitable technique either known at present or developed in the future. Further, a single device shown in FIG. 9 or FIG. 10 may be alternatively implemented in multiple devices separately, and multiple separated devices may be implemented in a single device. The scope of the present invention is not limited in these regards.
  • the apparatus 900 may be configured to implement functionalities as described with reference to FIGs. 1-4, and the apparatus 1000 may be configured to implement functionalities as described with reference to FIG. 5. Therefore, the features discussed with respect to any of methods 100-400 may apply to the corresponding components of the apparatus 900, and the features discussed with respect to the method 500 may apply to the corresponding components of the apparatus 1000. It is further noted that the components of the apparatus 900 or the apparatus 1000 may be embodied in hardware, software, firmware, and/or any combination thereof. For example, the components of the apparatus 900 or the apparatus 1000 may be respectively implemented by a circuit, a processor or any other appropriate device. Those skilled in the art will appreciate that the aforesaid examples are only for illustration not limitation.
  • the apparatus 900 or the apparatus 1000 may comprise at least one processor.
  • the at least one processor suitable for use with embodiments of the present disclosure may include, by way of example, both general and special purpose processors already known or developed in the future.
  • the apparatus 900 or the apparatus 1000 may further comprise at least one memory.
  • the at least one memory may include, for example, semiconductor memory devices, e.g., RAM, ROM, EPROM, EEPROM, and flash memory devices.
  • the at least one memory may be used to store program of computer executable instructions.
  • the program can be written in any high-level and/or low-level compliable or interpretable programming languages.
  • the computer executable instructions may be configured, with the at least one processor, to cause the apparatus 900 to at least perform according to any of methods 100 to 400 as discussed above, or to cause the apparatus 1000 to at least perform according to method 500 as discussed above.
  • the present disclosure may be embodied in an apparatus, a method, or a computer program product.
  • the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • FIGs. 1-5 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function (s) .
  • At least some aspects of the exemplary embodiments of the disclosures may be practiced in various components such as integrated circuit chips and modules, and that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, FPGA or ASIC that is configurable to operate in accordance with the exemplary embodiments of the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Conformément à des modes de réalisation, l'invention concerne un procédé et un appareil pour réaliser une transmission de données dans une procédure de demande de répétition automatique hybride (HARQ) inter-porteuses. Le procédé peut consister à recevoir une retransmission d'un bloc de données à partir d'un émetteur, la retransmission étant réalisée par l'émetteur en réponse à la réception d'un message d'accusé de réception négatif, et le message d'accusé de réception négatif indiquant qu'une première transmission du bloc de données sur une première porteuse composante a échoué; à obtenir, à partir de la retransmission du bloc de données, un identifiant indiquant la première porteuse composante; et à déterminer la première porteuse composante sur la base de l'identifiant.
PCT/CN2015/070452 2015-01-09 2015-01-09 Procédé et appareil pour réaliser une transmission de données WO2016109980A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/070452 WO2016109980A1 (fr) 2015-01-09 2015-01-09 Procédé et appareil pour réaliser une transmission de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/070452 WO2016109980A1 (fr) 2015-01-09 2015-01-09 Procédé et appareil pour réaliser une transmission de données

Publications (1)

Publication Number Publication Date
WO2016109980A1 true WO2016109980A1 (fr) 2016-07-14

Family

ID=56355437

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/070452 WO2016109980A1 (fr) 2015-01-09 2015-01-09 Procédé et appareil pour réaliser une transmission de données

Country Status (1)

Country Link
WO (1) WO2016109980A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022002145A1 (fr) * 2020-06-30 2022-01-06 Mediatek Singapore Pte. Ltd. Procédés et appareil pour des transmissions de harq entre porteuses

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102098152A (zh) * 2010-12-30 2011-06-15 电子科技大学 载波聚合下harq的跨载波重传方法
US20110205978A1 (en) * 2010-02-20 2011-08-25 Motorola, Inc. Multi-Carrier Control Signaling in Wireless Communication System
CN102783053A (zh) * 2009-12-24 2012-11-14 三星电子株式会社 用于在支持交叉载波调度的时分双工通信系统中定义物理信道的收发定时的方法和装置
CN103718484A (zh) * 2011-05-31 2014-04-09 三星电子株式会社 在支持载波聚合的tdd通信系统中定义物理信道传送/接收定时和资源分配的设备及其方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102783053A (zh) * 2009-12-24 2012-11-14 三星电子株式会社 用于在支持交叉载波调度的时分双工通信系统中定义物理信道的收发定时的方法和装置
US20110205978A1 (en) * 2010-02-20 2011-08-25 Motorola, Inc. Multi-Carrier Control Signaling in Wireless Communication System
CN102098152A (zh) * 2010-12-30 2011-06-15 电子科技大学 载波聚合下harq的跨载波重传方法
CN103718484A (zh) * 2011-05-31 2014-04-09 三星电子株式会社 在支持载波聚合的tdd通信系统中定义物理信道传送/接收定时和资源分配的设备及其方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022002145A1 (fr) * 2020-06-30 2022-01-06 Mediatek Singapore Pte. Ltd. Procédés et appareil pour des transmissions de harq entre porteuses

Similar Documents

Publication Publication Date Title
US11838130B2 (en) Method for partial retransmission
CN107005509B (zh) 用于未授权共享介质中的数据传输的方法、装置和系统
WO2020063641A1 (fr) Mécanismes pour différer un retour d'accusé de réception de requête automatique de répétition hybride (harq-ack)
US20180152274A1 (en) Acknowledgement information sending and receiving methods, receiving device, and sending device
TWI577151B (zh) 處理非執照細胞中的服務的通訊裝置
EP3429112B1 (fr) Procédés, appareils et équipement utilisateur pour transmission de demandes de répétition automatique hybride
EP3097653B1 (fr) Structure de données pour trames harq et procédé d'émission et de réception avec harq dans des systèmes utilisant une détection en aveugle
US9331759B2 (en) HARQ timing design for a TDD system
KR20180030173A (ko) 상향링크 제어정보의 전송 방법 및 장치
KR20190028375A (ko) 데이터 전송 방법 및 장치
US10721028B2 (en) Wireless communication method and wireless communication device
WO2017215749A1 (fr) Réattribution de ressources de canal de commande pour retransmission de données dans des réseaux sans fil basée sur le mode de communication
US9948433B2 (en) User equipment and base station
CN107113117B (zh) 一种信息反馈的方法、设备和系统
US10750537B2 (en) Data transmission method and apparatus
US20190207718A1 (en) Information transmission method and device
US10999016B2 (en) Control information sending method, control information receiving method, network device, and terminal device
WO2020083251A1 (fr) Procédé et appareil de transmission de données
CN109314590B (zh) 上行传输的方法和装置
EP2651160B1 (fr) Procédé, station de base et système pour gérer des ressources
WO2016109980A1 (fr) Procédé et appareil pour réaliser une transmission de données
WO2016161550A1 (fr) Procédé et appareil pour communiquer dans un système de communication
WO2020164128A1 (fr) Commande de rétroaction de retransmission
WO2018157353A1 (fr) Système de communication
WO2016109978A1 (fr) Procédé et appareil de transmission de données

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

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

Country of ref document: EP

Kind code of ref document: A1