WO2016127704A1 - 一种数据重传方法及装置 - Google Patents

一种数据重传方法及装置 Download PDF

Info

Publication number
WO2016127704A1
WO2016127704A1 PCT/CN2015/098096 CN2015098096W WO2016127704A1 WO 2016127704 A1 WO2016127704 A1 WO 2016127704A1 CN 2015098096 W CN2015098096 W CN 2015098096W WO 2016127704 A1 WO2016127704 A1 WO 2016127704A1
Authority
WO
WIPO (PCT)
Prior art keywords
carrier
data
retransmission
initial
received
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.)
Ceased
Application number
PCT/CN2015/098096
Other languages
English (en)
French (fr)
Inventor
王锐
沈晓冬
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.)
China Mobile Communications Group Co Ltd
Original Assignee
China Mobile Communications 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 China Mobile Communications Corp filed Critical China Mobile Communications Corp
Priority to US15/550,249 priority Critical patent/US10341062B2/en
Priority to EP15881852.6A priority patent/EP3249841B1/en
Publication of WO2016127704A1 publication Critical patent/WO2016127704A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a data retransmission method and apparatus.
  • LAA License-assisted access
  • LAA License-assisted Access
  • HARQ hybrid automatic repeat reQuest
  • QoS quality of service
  • CA Carrier Aggregation
  • the unlicensed band is open to all operators and all wireless access systems, and cannot be coordinated between different operators or different systems, it cannot guarantee that data transmission on a carrier in an unlicensed band fails.
  • the carrier is then used for data retransmission immediately, resulting in a longer HARQ delay. If the carrier is still unavailable after waiting for a long time, it will eventually result in data being lost. Discard, thereby reducing network performance.
  • the embodiment of the present disclosure provides a data retransmission method and apparatus, which solves the problem that the data retransmission delay is long and the packet loss phenomenon occurs in the prior art, resulting in low network performance.
  • the embodiment of the present disclosure provides a data retransmission method, including:
  • the base station Receiving, by the base station, retransmission data transmitted to the user equipment UE on the second carrier; the retransmission data is data that failed to be transmitted on the first carrier;
  • the received retransmission data is merged with the initial transmission data corresponding to the retransmission data previously received on the first carrier.
  • the first carrier is located in an unlicensed band; and the second carrier is located in an unlicensed band or a licensed band.
  • the method before receiving the retransmitted data transmitted on the second carrier, the method further includes:
  • the DCI is used to instruct the UE to receive downlink data transmitted on the second carrier, and use the received downlink data as retransmission data, corresponding to the retransmitted data.
  • the initial data is merged.
  • the DCI includes:
  • the first information includes a carrier indication bit CIF indicating a first carrier, and a 1-bit indication bit for indicating that the carrier indicated by the CIF is a carrier that transmits the initial transmission data.
  • the method before receiving the retransmitted data transmitted on the second carrier, the method further includes:
  • the carrier that transmits the downlink data is the second carrier that is determined to perform data retransmission, and the process ID corresponding to the downlink data is the process ID corresponding to the previously determined retransmission data, it is determined.
  • the downlink data that needs to be received is the retransmission data.
  • the retransmission carrier selection principle includes: selecting, from the carriers participating in the carrier aggregation CA, a carrier with the smallest load and the best channel condition as the second carrier.
  • the process number selection principle includes:
  • the process ID corresponding to the retransmission data is selected as the value after the modulo
  • the process ID corresponding to the retransmission data is the value of the number of processes that can be carried by the second carrier; or the process ID corresponding to the retransmission data is selected as The default process number.
  • the number of processes that the second carrier can carry is 8; when the second carrier is a time division duplex TDD carrier, the second The number of processes that the carrier can carry is the number of processes that the second carrier can carry under the current uplink and downlink subframe ratio.
  • Another embodiment of the present disclosure provides a data retransmission method, including:
  • the second carrier that performs data retransmission is configured for the UE
  • the embodiment of the present disclosure provides a data retransmission device, including:
  • a receiving module configured to receive retransmission data that is transmitted by the base station to the user equipment UE on the second carrier; the retransmission data is data that has failed to be transmitted on the first carrier;
  • a merging module configured to combine the received retransmission data with the initial transmission data corresponding to the retransmission data previously received on the first carrier.
  • Another embodiment of the present disclosure provides a data retransmission apparatus, including:
  • a configuration module configured to configure, when the data transmission to the user equipment is failed on the first carrier, the second carrier that performs data retransmission for the UE, if it is determined that the first carrier cannot be used for data retransmission; as well as
  • a transmission module configured to transmit, on the second carrier configured by the configuration module, data that fails to be transmitted on the first carrier before retransmitting to the UE.
  • the second carrier that performs data retransmission may be configured for the UE, and is transmitted on the first carrier before being retransmitted to the UE on the second carrier.
  • the failed data after receiving the retransmission data, the UE combines the received retransmission data with the initial transmission data corresponding to the retransmission data previously received on the first carrier. It can be seen that the embodiment of the present disclosure can ensure timely retransmission after data transmission failure, reduce the delay of data retransmission, and reduce packet loss caused by long retransmission waiting time, and the UE can The received retransmission data is merged with the previous initial transmission data to ensure continuity of data transmission and improve network performance.
  • FIG. 1 is a flowchart of a data retransmission method according to Embodiment 1 of the present disclosure
  • FIG. 2(a) is a schematic diagram of an application scenario of Embodiment 2 of the present disclosure
  • FIG. 2(b) is a flowchart of a data retransmission method provided by Embodiment 2 of the present disclosure
  • FIG. 3(a) is a schematic diagram of an application scenario of Embodiment 3 of the present disclosure.
  • FIG. 3(b) is a flowchart of a data retransmission method according to Embodiment 3 of the present disclosure
  • Embodiment 4 is a flowchart of a data retransmission method provided by Embodiment 4 of the present disclosure
  • FIG. 5 is a flowchart of a data retransmission method according to Embodiment 5 of the present disclosure.
  • Embodiment 6 is a flowchart of a data retransmission method provided by Embodiment 6 of the present disclosure
  • FIG. 7 is a flowchart of a data retransmission method according to Embodiment 7 of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a data retransmission apparatus according to Embodiment 1 of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a data retransmission apparatus according to Embodiment 2 of the present disclosure.
  • the basic idea of the embodiment of the present disclosure is that when the data transmission to the user equipment (User Equipment, UE) fails on the first carrier, the second carrier that performs data retransmission may be configured for the UE, and the UE is configured on the second carrier. Before the retransmission, the failed data is transmitted on the first carrier, and after receiving the retransmitted data, the UE combines the received retransmission data with the initial transmission data corresponding to the retransmission data previously received on the first carrier. It can be seen that the embodiment of the present disclosure can ensure the data transmission fails. Timely retransmission reduces the delay of data retransmission and reduces the packet loss caused by long retransmission waiting time. Moreover, the UE can combine the received retransmission data with the previous initial transmission data to ensure that The continuity of data transmission improves network performance.
  • the user equipment User Equipment
  • the embodiment of the present disclosure further provides a scheme for the UE to combine the retransmitted data with the previously received initial transmission data after receiving the retransmission data, thereby ensuring continuity of data transmission.
  • a flowchart of a data retransmission method provided in Embodiment 1 of the present disclosure includes the following steps:
  • the UE may feed back the data transmission failure (NACK) information to the base station; the base station determines whether the first carrier can be used for data retransmission at this time, if not, Then configure other carriers for the UE.
  • NACK data transmission failure
  • the first carrier is located in an unlicensed band; and the second carrier is located in an unlicensed band or a licensed band.
  • the embodiments of the present disclosure are mainly directed to the case where the carrier data transmission fails on the unlicensed frequency band, and of course, the case where the carrier data transmission fails on the licensed frequency band is also applicable.
  • the second carrier configured to perform data retransmission for the UE includes:
  • the carrier of the unlicensed frequency band that can be used for data retransmission is found within the preset time length or the number of traversal times, the carrier of the unlicensed frequency band that is found is used as the second carrier, otherwise, the licensed frequency band is used.
  • the carrier is used as the second carrier.
  • the carrier of the unlicensed frequency band may be preferentially selected for data retransmission.
  • a timer the timing time is the preset time length
  • a counter the number of times of counting is the preset number of traversal times
  • the number of traversal here means that the state of the carriers of all the unlicensed frequency bands participating in the CA is looked up once as one traversal.
  • S102 The base station retransmits data that fails on the first carrier before retransmitting to the UE on the configured second carrier.
  • the UE receives retransmission data transmitted by the base station on the second carrier; the retransmission data is data that has failed to be transmitted on the first carrier.
  • the UE combines the received retransmission data with the initial transmission data corresponding to the retransmission data previously received on the first carrier.
  • the UE after receiving the data failure, the UE first stores the received initial transmission data, and after receiving the subsequent retransmission data, combines the retransmitted data with the initial transmission data.
  • the UE needs to know whether the received downlink data is retransmitted data. If the data is retransmitted, the initial transmission data corresponding to the retransmitted data is specifically transmitted by which carrier, and the process ID corresponding to the initial transmission data. What is it. Based on this information, the UE can combine the received retransmission data with the previous initial transmission data to ensure the continuity of the data.
  • the carrier, the corresponding process number, and the like, where the initial data is located may be indicated in Downlink Control Information (DCI) carried in the physical downlink control channel (PDCCH).
  • DCI Downlink Control Information
  • PDCCH physical downlink control channel
  • Information; the retransmission carrier selection principle and the process number selection principle may also be defined in advance so that the UE automatically matches the retransmission data and the initial transmission data.
  • the base station indicates, by the DCI, the carrier number corresponding to the transmission of the initial transmission data and/or the process number corresponding to the initial transmission data.
  • the method further includes: transmitting downlink control information DCI to the UE on the second carrier; the DCI is used to indicate that the UE receives downlink data on the second carrier, and The received downlink data is used as retransmission data, and the initial transmission data corresponding to the retransmission data is combined.
  • the DCI may include first information indicating a first carrier that transmits the initial transmission data; and/or second information indicating a process number corresponding to the initial transmission data.
  • the first information includes a carrier indication bit CIF indicating a first carrier, and a 1-bit indication bit for indicating that the carrier indicated by the CIF is a carrier that transmits the initial transmission data.
  • a 1-bit flag may be added to the DCI to indicate a carrier indication field in the DCI.
  • CIF CIF attribute information. For example, if the value of the indicator bit is 1, it may indicate that the carrier indicated by the CIF is a carrier that is to transmit downlink data (the meaning of the CIF does not change, and the cross-carrier scheduling is performed for the existing CA architecture); If the value is 0, it can indicate that the carrier indicated by the CIF is the carrier that transmits the initial data (the meaning of the CIF has changed, for the CA architecture under the LAA), where the initial data is the second and the second The retransmitted data transmitted on the carrier is connected to the previous data.
  • an indication bit indicating the process ID may be added to the DCI. If the carrier indicated by the CIF is a Frequency Division Duplex (FDD) carrier, three bits (3 bits) are added. The indication bit; if the carrier indicated by the CIF is a Time Division Duplexing (TDD) carrier, a four-bit (4 bits) indicator bit is added).
  • the original information of the DCI includes an indication bit indicating the process number, and another indicator bit is added here.
  • the original indicator bit and the newly added indicator bit can be used to indicate the process number corresponding to the initial transmission data and the retransmission data respectively.
  • the process ID is used to indicate the process ID corresponding to the retransmission data and the process ID corresponding to the initial data.
  • the UE may combine the received retransmission data with the saved initial data corresponding to the carrier and the process number.
  • the retransmission data may be defined in advance to be the same as the redundancy version (RV) of the initial transmission data.
  • the DCI may include both the first information and the second information.
  • the DCI may also include only the first information.
  • the process ID of the default initial data is the same as the process ID of the retransmitted data indicated in the CIF.
  • the base station needs to notify the UE to detect the DCI of the PDCCH transmission on the second carrier on the first carrier before transmitting the downlink control information DCI to the UE on the second carrier.
  • the UE needs to blindly detect the DCI of the PDCCH transmission on each carrier among all the carriers participating in the CA.
  • the method for informing the UE to detect the DCI of the PDCCH transmission on the second carrier on the first carrier may be: the base station instructing the UE to detect the DCI of the PDCCH transmission on the second carrier in the DCI of the PDCCH transmission on the first carrier.
  • Manner 2 The UE performs matching between the retransmission data and the initial transmission data according to the retransmission carrier selection principle and the process number selection principle.
  • the method further includes:
  • the process number corresponding to the second carrier and the retransmission data for performing data retransmission is determined.
  • the carrier that transmits the downlink data is the second carrier that is determined to perform data retransmission, and the process ID corresponding to the downlink data is the process ID corresponding to the previously determined retransmission data, it is determined.
  • the downlink data that needs to be received is the retransmission data.
  • the retransmission carrier selection principle may be multiple.
  • the first carrier except the first carrier in the carrier list sent by the base station may be selected as the second carrier.
  • a carrier with the smallest load and the best channel condition may be selected as the second carrier from the carriers participating in the carrier aggregation CA.
  • the process number selection principle may be various.
  • the principle may be: when the process number corresponding to the initial data is less than or equal to the number of processes that the second carrier can carry, the process ID corresponding to the retransmission data is the same as the process ID corresponding to the initial data.
  • the process number corresponding to the initial data is greater than the number of processes that can be carried by the second carrier, the process number corresponding to the retransmission data is a preset process number (the preset process number is 1 to the number of processes that the second carrier can carry) A value between values).
  • the principle may be: when the process number corresponding to the initial data is less than or equal to the number of processes that the second carrier can carry, the process ID corresponding to the retransmission data is the same as the process ID corresponding to the initial data.
  • the process number corresponding to the initial data is greater than the number of processes that can be carried by the second carrier, the process number corresponding to the retransmission data is selected by dividing the process number corresponding to the initial data by 2 n or the nth power, up or down. Rounded value. Where n is the minimum value of the process number corresponding to the retransmission data is less than or equal to the number of processes that the second carrier can carry.
  • the process number selection principle may include:
  • the process ID corresponding to the retransmission data is selected as the value after the modulo
  • the process ID corresponding to the retransmission data is the value of the number of processes that can be carried by the second carrier; or the process ID corresponding to the retransmission data is selected as The default process number.
  • the preset process number is a value between 1 and the value of the number of processes that the second carrier can carry.
  • the second carrier when the second carrier is a frequency division duplex FDD carrier, the number of processes that the second carrier can carry is 8; when the second carrier is a time division duplex TDD carrier, the second carrier can The number of processes carried is the number of processes that the second carrier can carry under the current uplink-downlink subframe ratio.
  • the process ID corresponding to the data is 5
  • the process ID corresponding to the retransmission data is 1.
  • the process ID corresponding to the initial data is 8
  • the process ID corresponding to the retransmission data is 4.
  • the process number corresponding to the initial data is 5
  • the process number corresponding to the retransmission data is 5
  • the process number corresponding to the retransmitted data is 2.
  • the process ID corresponding to the initial transmission data When the value is 8, the process ID corresponding to the retransmitted data is 8. When the process ID corresponding to the initial data is 14, the process ID corresponding to the retransmitted data is 4.
  • FIG. 2(a) is a schematic diagram of the application scenario, where D represents a downlink subframe, and U represents an uplink subframe.
  • S201 If the base station transmits data to the UE on the first carrier in the unlicensed frequency band, receiving a data transmission failure (NACK) message fed back by the UE, and determining that the first carrier is not used for data retransmission, determining that the Data retransmission is performed on the second carrier located in the licensed band.
  • NACK data transmission failure
  • the base station transmits the DCI to the UE on the PDCCH of the second carrier.
  • the UE After detecting the DCI on the PDCCH of the second carrier, the UE confirms that the CIF indicating the first carrier and the indication bit for indicating that the carrier indicated by the CIF is the carrier transmitting the initial data are carried.
  • the base station transmits the failed data on the first carrier before transmitting to the UE on the second carrier.
  • the UE After receiving the retransmission data transmitted on the second carrier, the UE extracts, according to the process ID corresponding to the retransmitted data, the first transmission data that is received on the first carrier before the stored corresponding process number.
  • S206 The UE combines the retransmitted data received on the second carrier with the extracted initial data.
  • Application scenario The first carrier that is located in the unlicensed frequency band (for example, corresponding to a certain secondary cell Scell) is retransmitted to the second carrier in the unlicensed frequency band (for example, corresponding to another secondary cell Scell).
  • Figure 3 (a) is a schematic diagram of the application scenario.
  • S301 If the base station transmits data to the UE on the first carrier in the unlicensed frequency band, the data transmission failure (NACK) message fed back by the UE is received, and when it is determined that the first carrier cannot be used for data retransmission, it is determined that the data needs to be re-transmitted. Data retransmission is performed on the second carrier located in the unlicensed band.
  • NACK data transmission failure
  • the base station transmits the DCI to the UE on the PDCCH of the second carrier.
  • the UE After detecting the DCI on the PDCCH of the second carrier, the UE confirms that the CIF indicating the first carrier and the indication bit for indicating that the carrier indicated by the CIF is the carrier transmitting the initial data are carried.
  • S304 The base station transmits the failed data on the first carrier before transmitting to the UE on the second carrier.
  • the UE After receiving the retransmission data transmitted on the second carrier, the UE corresponds to the retransmitted data.
  • the process number extracts the stored initial data received on the first carrier corresponding to the process number.
  • S306 The UE combines the retransmitted data received on the second carrier with the extracted initial data.
  • the first carrier that is located in the unlicensed frequency band is retransmitted.
  • the carrier that considers the unlicensed frequency band is retransmitted first. If the carrier of the unlicensed frequency band cannot be found within the constraint condition, the carrier of the authorized frequency band is searched.
  • the specific implementation process is shown in Figure 4, including the following steps:
  • the base station receives a data transmission failure (NACK) message fed back by the UE when transmitting data to the UE on the first carrier in the unlicensed frequency band, and determines that the first carrier cannot be used for data retransmission.
  • NACK data transmission failure
  • the base station transmits the DCI to the UE on the PDCCH of the second carrier.
  • the UE After detecting the DCI on the PDCCH of the second carrier, the UE confirms that the CIF indicating the first carrier and the indication bit for indicating that the carrier indicated by the CIF is the carrier transmitting the initial data are carried.
  • S405 The base station transmits the failed data on the first carrier before transmitting to the UE on the second carrier.
  • the UE After receiving the retransmission data transmitted on the second carrier, the UE extracts, according to the process ID corresponding to the retransmission data, the stored initial transmission data that is received on the first carrier corresponding to the process ID.
  • S407 The UE combines the retransmitted data received on the second carrier with the extracted initial data.
  • the application scenario is the same as that in the second embodiment.
  • the first carrier that is located in the unlicensed band (for example, corresponding to a certain secondary cell Scell) is retransmitted to the second carrier (for example, the corresponding primary cell Pcell).
  • the DCI carries not only the first information indicating the carrier transmitting the initial transmission data but also the second information indicating the process number of the initial transmission data.
  • S501 If the base station transmits data to the UE on the first carrier that is located in the unlicensed frequency band, receiving a data transmission failure (NACK) message fed back by the UE, and determining that the first carrier is not used for data retransmission. Data retransmission is performed on the second carrier located in the licensed band.
  • NACK data transmission failure
  • the base station transmits the DCI to the UE on the PDCCH of the second carrier.
  • the UE After detecting the DCI on the PDCCH of the second carrier, the UE confirms that the CIF indicating the first carrier is carried, the indication bit for indicating the carrier indicated by the CIF is the carrier for transmitting the initial transmission data, and the indication corresponding to the initial transmission data.
  • the process number and the indication bit of the process number corresponding to the retransmitted data After detecting the DCI on the PDCCH of the second carrier, the UE confirms that the CIF indicating the first carrier is carried, the indication bit for indicating the carrier indicated by the CIF is the carrier for transmitting the initial transmission data, and the indication corresponding to the initial transmission data.
  • the base station transmits the failed data on the first carrier before transmitting to the UE on the second carrier.
  • the UE After receiving the retransmission data of the process ID indicated in the corresponding DCI transmitted on the second carrier, the UE receives the stored on the first carrier according to the process ID corresponding to the initial data indicated in the DCI. The initial data.
  • S506 The UE combines the retransmitted data received on the second carrier with the extracted initial data.
  • the application scenario is the same as that in the third embodiment.
  • the first carrier (for example, corresponding to a certain secondary cell Scell) is transmitted in the unlicensed frequency band, and the second carrier located in the unlicensed frequency band is retransmitted (for example, corresponding to another secondary cell Scell).
  • the DCI carries not only the first information indicating the carrier transmitting the initial transmission data but also the second information indicating the process number of the initial transmission data.
  • S601 If the base station transmits data to the UE on the first carrier in the unlicensed frequency band, receiving a data transmission failure (NACK) message fed back by the UE, determining that the data is required to be retransmitted using the first carrier, Data retransmission is performed on the second carrier located in the unlicensed band.
  • NACK data transmission failure
  • the base station transmits the DCI to the UE on the PDCCH of the second carrier.
  • the UE After detecting the DCI on the PDCCH of the second carrier, the UE confirms that the CIF indicating the first carrier is carried, the indication bit for indicating the carrier indicated by the CIF is the carrier transmitting the initial transmission data, and the corresponding initial data is indicated.
  • the base station transmits the failed data on the first carrier before transmitting to the UE on the second carrier.
  • the UE After receiving the retransmission data of the process ID indicated by the corresponding DCI transmitted on the second carrier, the UE extracts the storage before the storage according to the process ID corresponding to the initial transmission data indicated in the DCI. The initial transmission data received on the first carrier.
  • S606 The UE combines the retransmitted data received on the second carrier with the extracted initial data.
  • the application scenario is the same as that in the fourth embodiment.
  • the first carrier that is in the unlicensed frequency band is first transmitted, and the carrier that considers the unlicensed frequency band is retransmitted first. If the carrier of the unlicensed frequency band cannot be found within the constraint condition, the carrier of the authorized frequency band is searched. .
  • the DCI carries not only the first information indicating the carrier transmitting the initial transmission data but also the second information indicating the process number of the initial transmission data.
  • the base station receives a data transmission failure (NACK) message fed back by the UE when transmitting data to the UE on the first carrier in the unlicensed frequency band, and determines that the first carrier cannot be used for data retransmission.
  • NACK data transmission failure
  • the base station transmits the DCI to the UE on the PDCCH of the second carrier.
  • the UE After detecting the DCI on the PDCCH of the second carrier, the UE confirms that the CIF indicating the first carrier, the indication bit for indicating that the carrier indicated by the CIF is the carrier for transmitting the initial transmission data, and the indication corresponding to the initial transmission data The process number and the indication bit of the process number corresponding to the retransmitted data.
  • the base station transmits the failed data on the first carrier before transmitting to the UE on the second carrier.
  • the UE After receiving the retransmission data of the process ID indicated in the corresponding DCI transmitted on the second carrier, the UE receives the stored on the first carrier according to the process ID corresponding to the initial transmission data indicated in the DCI. The initial data.
  • S707 The UE combines the retransmitted data received on the second carrier with the extracted initial data.
  • a data retransmission device corresponding to the data retransmission method is further provided in the embodiment of the present disclosure. Since the principle of the device solving the problem is similar to the data retransmission method in the embodiment of the present disclosure, the The implementation of the device can be referred to the implementation of the method, and the details are not repeated here.
  • FIG. 8 is a schematic structural diagram of a data retransmission apparatus according to Embodiment 1 of the present disclosure, including:
  • the receiving module 81 is configured to receive retransmission data that is transmitted by the base station to the user equipment UE on the second carrier, where the retransmission data is data that failed to be transmitted on the first carrier;
  • the merging module 82 is configured to combine the received retransmission data with the initial transmission data corresponding to the retransmission data previously received on the first carrier.
  • the first carrier is located in an unlicensed band; and the second carrier is located in an unlicensed band or a licensed band.
  • the receiving module 81 is further configured to: before receiving retransmission data transmitted on the second carrier, receive downlink control information DCI transmitted on the second carrier; the DCI is used to indicate that the UE receives The downlink data transmitted on the second carrier, and the received downlink data is used as retransmission data, and the initial transmission data corresponding to the retransmission data is combined.
  • the DCI includes:
  • the first information includes a carrier indication bit CIF indicating a first carrier, and a 1-bit indication bit for indicating that the carrier indicated by the CIF is a carrier that transmits the initial transmission data.
  • the receiving module 81 is further configured to: before receiving the retransmission data transmitted on the second carrier, after determining that the data is not received on the first carrier, according to the retransmission carrier selection principle and the process number selection principle, Determining a process number corresponding to the second carrier and the retransmission data for performing data retransmission; and determining, when the downlink data needs to be received, the carrier transmitting the downlink data is the previously determined second carrier for performing data retransmission, and the downlink data
  • the corresponding process ID is the process ID corresponding to the previously determined retransmission data, and the downlink data that needs to be received is determined to be the retransmission data.
  • the retransmission carrier selection principle includes: selecting, from the carriers participating in the carrier aggregation CA, a carrier with the smallest load and the best channel condition as the second carrier.
  • the process number selection principle includes:
  • the process ID corresponding to the retransmitted data is selected as the fetching Value after the model
  • the process ID corresponding to the retransmission data is the value of the number of processes that can be carried by the second carrier; or the process ID corresponding to the retransmission data is selected as The default process number.
  • the number of processes that the second carrier can carry is 8; when the second carrier is a time division duplex TDD carrier, the second The number of processes that the carrier can carry is the number of processes that the second carrier can carry under the current uplink and downlink subframe ratio.
  • FIG. 9 is a schematic structural diagram of a data retransmission apparatus according to Embodiment 2 of the present disclosure, including:
  • the configuration module 91 is configured to: if it is determined that the first carrier is not used for data retransmission when the data transmission to the user equipment UE fails on the first carrier, configure the second carrier for data retransmission for the UE ;as well as
  • the transmitting module 92 is configured to retransmit the data that failed to be transmitted on the first carrier before retransmitting to the UE on the second carrier configured by the configuration module 91.
  • the first carrier is located in an unlicensed band; and the second carrier is located in an unlicensed band or a licensed band.
  • the configuration module 91 is specifically configured to:
  • the carrier of the unlicensed frequency band that can be used for data retransmission is found within the preset time length or the number of traversal times, the carrier of the unlicensed frequency band that is found is used as the second carrier, otherwise, the licensed frequency band is used.
  • the carrier is used as the second carrier.
  • the transmitting module 92 is further configured to, on the second carrier that is configured, before the retransmission of the data before the UE fails to transmit on the first carrier, on the second carrier.
  • Downlink control information DCI is transmitted to the UE.
  • the DCI is used to indicate that the UE receives downlink data on the second carrier, and uses the received downlink data as retransmission data, and merges the initial transmission data corresponding to the retransmitted data.
  • the DCI includes:
  • the first information includes a carrier indication bit CIF indicating a first carrier, and a 1-bit indication bit for indicating that the carrier indicated by the CIF is a carrier that transmits the initial transmission data.
  • embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

根据本公开文本实施例提供的一种数据重传方法包括：接收基站在第二载波上传输给用户设备UE的重传数据；所述重传数据为之前在第一载波上传输失败的数据；将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。采用本公开文本实施例可以保证数据传输失败后的及时重传，减少了数据重传的时延，也减少了因重传等待时间较长而产生的丢包现象，并且，UE可以将接收的重传数据与之前的初传数据进行合并，保证了数据传输的连续性，提高了网络性能。

Description

一种数据重传方法及装置
相关申请的交叉参考
本申请主张在2015年2月10日在中国提交的中国专利申请号No.201510070005.6的优先权，其全部内容通过引用包含于此。
技术领域
本公开文本涉及通信技术领域，尤其涉及一种数据重传方法及装置。
背景技术
随着移动互联网中数据流量的激增，各大运营商都在探索在非授权频段上使用长期演进(Long Term Evolution，LTE)技术，由此发展出了一种名为辅助授权接入(License-assisted Access，LAA)的技术。
由于非授权频段对于所有的运营商都是开放的，不同运营商具有相同的权利在非授权频段上部署LTE。为了使异系统或异运营商公平竞争使用非授权频段，在辅助授权接入(License-assisted Access，LAA)技术中引入了先听后说(listen before talk，LBT)机制。即在每次进行数据传输前，先预留一段时间来对载波进行感知，当感知到载波可用时才开始进行数据传输，并且每次进行数据传输有最大时长的限制。可见，LAA中引入的LBT机制只是为了使异系统或异运营商不产生非授权频段使用的冲突，并不能在异系统或异运营商间真正协调使用非授权频段。
在LTE系统中，通常采用混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)机制来保证服务质量(Quality of Service，QoS)。LAA中主要考虑使用载波聚合(Carrier Aggregation，CA)架构，在现有的CA架构下，HARQ重传与初传位于相同的载波上。
由于非授权频段对所有的运营商及所有的无线接入系统都是开放的，且异运营商或异系统间无法进行协调，从而无法保证在一个非授权频段的载波上传输数据失败后，能够再立即使用该载波进行数据重传，从而导致HARQ时延较长。如果在等待较长时间后该载波仍不可用，将会最终导致数据被丢 弃，从而降低网络性能。
可见，在现有的HARQ机制下，数据重传时延较长，甚至会产生丢包现象，从而导致网络性能较低。
发明内容
(一)要解决的技术问题
本公开文本实施例提供一种数据重传方法及装置，用以解决现有技术中数据重传时延较长，甚至会产生丢包现象，从而导致网络性能较低的问题。
(二)技术方案
为了实现上述目的，本公开文本提供如下技术方案：
本公开文本实施例提供一种数据重传方法，包括：
接收基站在第二载波上传输给用户设备UE的重传数据；所述重传数据为之前在第一载波上传输失败的数据；以及
将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。
可选地，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
可选地，接收在第二载波上传输的重传数据之前，还包括：
接收在第二载波上传输的下行控制信息DCI；所述DCI用于指示所述UE接收在第二载波上传输的下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
可选地，所述DCI中包括：
指示传输所述初传数据的第一载波的第一信息；和/或
指示所述初传数据对应的进程号的第二信息。
可选地，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
可选地，接收在第二载波上传输的重传数据之前，还包括：
当确定在第一载波上接收数据失败后，根据重传载波选择原则和进程号选择原则，确定进行数据重传的第二载波和重传数据对应的进程号；
在需要接收下行数据时，若确定传输该下行数据的载波为之前确定的进行数据重传的第二载波，并且该下行数据对应的进程号为之前确定的重传数据对应的进程号，则确定需要接收的该下行数据为所述重传数据。
可选地，所述重传载波选择原则包括：从参与载波聚合CA的载波中，选择负载最小、信道条件最好的载波作为所述第二载波。
可选地，所述进程号选择原则包括：
确定所述初传数据对应的进程号对所述第二载波能够承载的进程数目取模后的值；
若所述取模后的值不为0，则选择所述重传数据对应的进程号为所述取模后的值；
若所述取模后的值为0，则选择所述重传数据对应的进程号为所述第二载波能够承载的进程数目的取值；或者，选择所述重传数据对应的进程号为预设的进程号。
可选地，当所述第二载波为频分双工FDD载波时，所述第二载波能够承载的进程数目为8；当所述第二载波为时分双工TDD载波时，所述第二载波能够承载的进程数目为所述第二载波在当前所处的上下行子帧配比下能够承载的进程数目。
本公开文本另一实施例提供一种数据重传方法，包括：
当在第一载波上向用户设备UE传输数据失败时，若确定无法继续使用所述第一载波进行数据重传，则为所述UE配置进行数据重传的第二载波；以及
在配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据。
本公开文本实施例提供一种数据重传装置，包括：
接收模块，用于接收基站在第二载波上传输给用户设备UE的重传数据；所述重传数据为之前在第一载波上传输失败的数据；以及
合并模块，用于将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。
本公开文本另一实施例提供一种数据重传装置，包括：
配置模块，用于当在第一载波上向用户设备UE传输数据失败时，若确定无法继续使用所述第一载波进行数据重传，则为所述UE配置进行数据重传的第二载波；以及
传输模块，用于在所述配置模块配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据。
(三)有益效果
本公开文本实施例至少具有如下有益效果：
在本公开文本实施例中，当在第一载波上向UE传输数据失败时，可以为UE配置进行数据重传的第二载波，在第二载波上向UE重传之前在第一载波上传输失败的数据，UE接收该重传数据后，将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。可见，采用本公开文本实施例可以保证数据传输失败后的及时重传，减少了数据重传的时延，也减少了因重传等待时间较长而产生的丢包现象，并且，UE可以将接收的重传数据与之前的初传数据进行合并，保证了数据传输的连续性，提高了网络性能。
附图说明
为了更清楚地说明本公开文本实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开文本的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本公开文本实施例一提供的数据重传方法流程图；
图2(a)为本公开文本实施例二的应用场景示意图；
图2(b)为本公开文本实施例二提供的数据重传方法流程图；
图3(a)为本公开文本实施例三的应用场景示意图；
图3(b)为本公开文本实施例三提供的数据重传方法流程图；
图4为本公开文本实施例四提供的数据重传方法流程图；
图5为本公开文本实施例五提供的数据重传方法流程图；
图6为本公开文本实施例六提供的数据重传方法流程图；
图7为本公开文本实施例七提供的数据重传方法流程图；
图8为本公开文本实施例一提供的数据重传装置结构示意图；以及
图9为本公开文本实施例二提供的数据重传装置结构示意图。
具体实施方式
下面结合附图和实施例，对本公开文本的具体实施方式做进一步描述。以下实施例仅用于说明本公开文本，但不用来限制本公开文本的范围。
为使本公开文本实施例的目的、技术方案和优点更加清楚，下面将结合本公开文本实施例的附图，对本公开文本实施例的技术方案进行清楚、完整地描述。显然，所描述的实施例是本公开文本的一部分实施例，而不是全部的实施例。基于所描述的本公开文本的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本公开文本保护的范围。
除非另作定义，此处使用的技术术语或者科学术语应当为本公开文本所属领域内具有一般技能的人士所理解的通常意义。本公开文本专利申请说明书以及权利要求书中使用的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。同样，“一个”或者“一”等类似词语也不表示数量限制，而是表示存在至少一个。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电性的连接，不管是直接的还是间接的。“上”、“下”、“左”、“右”等仅用于表示相对位置关系，当被描述对象的绝对位置改变后，则该相对位置关系也相应地改变。
以下结合附图对本公开文本实施例的原理和特征进行描述，所举实例只用于解释本公开文本实施例，并非用于限定本公开文本实施例的范围。
本公开文本实施例的基本思想是：当在第一载波上向用户设备(User Equipment，UE)传输数据失败时，可以为UE配置进行数据重传的第二载波，在第二载波上向UE重传之前在第一载波上传输失败的数据，UE接收该重传数据后，将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。可见，采用本公开文本实施例可以保证数据传输失败后的 及时重传，减少了数据重传的时延，也减少了因重传等待时间较长而产生的丢包现象，并且，UE可以将接收的重传数据与之前的初传数据进行合并，保证了数据传输的连续性，提高了网络性能。
本公开文本实施例进一步给出了UE在接收到重传数据后，将该重传数据与之前接收的初传数据进行合并，从而保证了数据传输的连续性的方案。
下面结合说明书附图对本公开文本实施例作进一步详细描述。
实施例一
如图1所示，为本公开文本实施例一提供的数据重传方法流程图，包括以下步骤：
S101：当基站在第一载波上向UE传输数据失败时，若确定无法继续使用所述第一载波进行数据重传，则为所述UE配置进行数据重传的第二载波。
在具体实施中，基站在第一载波上向UE传输数据失败后，UE会向基站反馈数据传输失败(NACK)信息；基站判断此时第一载波是否可以用于数据重传，如果不可以，则为UE配置其它载波。
可选地，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
这里，本公开文本实施例主要针对非授权频段上载波数据传输失败的情况，当然，对于授权频段上载波数据传输失败的情况也可适用。
可选地，为所述UE配置进行数据重传的第二载波，包括：
若在预设的时间长度或者遍历次数内，查找到能够用于进行数据重传的非授权频段的载波，则将查找到的非授权频段的载波作为所述第二载波，否则，将授权频段的载波作为所述第二载波。
在具体实施中，为了不影响授权频段的载波上的数据传输，可以优先选择非授权频段的载波进行数据重传。具体地，可以设置一个计时器(计时时间为所述预设的时间长度)或计数器(计数次数为所述预设的遍历次数)，当查找可用载波的时间达到计时器的计时时间或者当前的遍历次数达到计数器的计数次数时，放弃对非授权频段的载波的查找，采用授权频段的载波作为用于数据重传的载波。这里的遍历次数是指，将所有参与CA的非授权频段的载波的状态都查找一遍视为一次遍历。
S102：所述基站在配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据。
S103：所述UE接收基站在第二载波上传输的重传数据；所述重传数据为之前在第一载波上传输失败的数据。
S104：所述UE将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。
在具体实施中，UE在接收数据失败后，先将已接收的初传数据存储起来，在接收到后续的重传数据后，再将重传数据与初传数据进行合并。
在实际实施中，UE需要知道接收到的下行数据是否是重传数据，若是重传数据，该重传数据对应的初传数据具体是由哪个载波传输的、以及该初传数据对应的进程号是什么。基于这些信息，UE可以将接收的重传数据与之前的初传数据进行合并，保证数据的连续性。
在具体实施中，可以在物理下行控制信道(Physical Downlink Control Channel，PDCCH)承载的下行控制信息(Downlink Control Information，DCI)中指示上述初传数据所在的载波、对应的进程号(Process Number)等信息；也可以预先定义重传载波选择原则和进程号选择原则，以使UE自动匹配重传数据与初传数据。下面进行具体介绍。
方式一：基站通过DCI指示传输初传数据的载波和/或初传数据对应的进程号。
具体地，S101之后，S102之前，还包括：在所述第二载波上向所述UE传输下行控制信息DCI；所述DCI用于指示所述UE在所述第二载波上接收下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
这里，DCI中可以包括指示传输所述初传数据的第一载波的第一信息；和/或，指示所述初传数据对应的进程号的第二信息。
可选地，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
针对所述第一信息，在具体实施中，可以在DCI中增加一个1比特(bit)的指示位(flag)，用于指示DCI中的载波指示域(Carrier Instructions Field， CIF)的属性信息。比如，若该指示位的值为1，则可以表示CIF指示的载波为即将传输下行数据的载波(CIF的意义未发生变化，针对现有的CA架构下的跨载波调度)；若该指示位的值为0，则可以表示CIF所指示的载波为传输所述初传数据的载波(CIF的意义发生了变化，针对LAA下的CA架构)，这里的初传数据即为与在该第二载波上传输的重传数据相接续的之前的数据。
针对所述第二信息，在具体实施中，可以在DCI中增加指示进程号的指示位(若CIF指示的载波为频分双工(Frequency Division Duplex，FDD)载波，则增加三比特(3bits)的指示位；若CIF指示的载波为时分双工(Time Division Duplexing，TDD)载波，则增加四比特(4bits)的指示位)。DCI原有的信息中包含指示进程号的指示位，这里再增加另外的指示位，原有的指示位和新增加的指示位可以分别用于指示初传数据对应的进程号和重传数据对应的进程号，或者分别用于指示重传数据对应的进程号和初传数据对应的进程号。
获取初传数据对应的载波和进程号后，UE就可以将接收的重传数据与保存的对应所述载波和进程号的初传数据进行合并。这里，可以预先定义重传数据与初传数据的冗余版本(Redundancy Version，RV)相同。
在方式一中，DCI中可以既包括第一信息，又包括第二信息。当然，DCI也可以只包括第一信息，此时，默认初传数据的进程号与CIF中指示的重传数据的进程号相同。
这里，需要说明的是，在方式一中，基站在所述第二载波上向所述UE传输下行控制信息DCI之前，需要在第一载波上通知UE检测第二载波上的PDCCH传输的DCI；或者，UE需要在所有参与CA的载波中，盲检测各个载波上的PDCCH传输的DCI。其中，在第一载波上通知UE检测第二载波上的PDCCH传输的DCI的方式具体可以是：基站在第一载波上的PDCCH传输的DCI中指示UE检测第二载波上的PDCCH传输的DCI。
方式二、UE根据重传载波选择原则和进程号选择原则，进行重传数据与初传数据的匹配。
具体地，S103之前，还包括：
当确定在第一载波上接收数据失败后，根据重传载波选择原则和进程号选择原则，确定进行数据重传的第二载波和重传数据对应的进程号。
在需要接收下行数据时，若确定传输该下行数据的载波为之前确定的进行数据重传的第二载波，并且该下行数据对应的进程号为之前确定的重传数据对应的进程号，则确定需要接收的该下行数据为所述重传数据。
这里，所述重传载波选择原则可以有多种，比如，可以选择基站发送的载波列表中除第一载波外的第一个载波作为所第二载波。优选地，可以从参与载波聚合CA的载波中，选择负载最小、信道条件最好的载波作为所述第二载波。
这里，所述进程号选择原则可以有多种。比如，该原则可以是：当初传数据对应的进程号小于或等于第二载波能够承载的进程数目时，选择重传数据对应的进程号与初传数据对应的进程号相同。当初传数据对应的进程号大于第二载波能够承载的进程数目时，选择重传数据对应的进程号为预设的进程号(预设的进程号为1至第二载波能够承载的进程数目的取值之间的一个值)。再比如，该原则可以是：当初传数据对应的进程号小于或等于第二载波能够承载的进程数目时，选择重传数据对应的进程号与初传数据对应的进程号相同。当初传数据对应的进程号大于第二载波能够承载的进程数目时，选择重传数据对应的进程号为将初传数据对应的进程号除以2n或开n次方后，向上或向下取整的值。其中，n为使重传数据对应的进程号小于或等于第二载波能够承载的进程数目的最小值。
优选地，所述进程号选择原则可以包括：
确定所述初传数据对应的进程号对所述第二载波能够承载的进程数目取模后的值；
若所述取模后的值不为0，则选择所述重传数据对应的进程号为所述取模后的值；
若所述取模后的值为0，则选择所述重传数据对应的进程号为所述第二载波能够承载的进程数目的取值；或者，选择所述重传数据对应的进程号为预设的进程号。这里，预设的进程号为1至第二载波能够承载的进程数目的取值之间的一个值。
这里，当所述第二载波为频分双工FDD载波时，所述第二载波能够承载的进程数目为8；当所述第二载波为时分双工TDD载波时，所述第二载波能够承载的进程数目为所述第二载波在当前所处的上下行子帧配比下能够承载的进程数目。
如下表一所示，为载波在不同的TDD上下行子帧配比下能够承载的进程数目。
基于上述优选的进程号选择原则，当第一载波为FDD载波，第二载波为TDD载波时，若第二载波当前的上下行子帧配比为表中的0号配置(对应进程数目4)，则当初传数据对应的进程号为5时，重传数据对应的进程号为1；当初传数据对应的进程号为8时，重传数据对应的进程号为4。
当第一载波为TDD载波，第二载波为FDD载波(对应进程数目8)时，则当初传数据对应的进程号为5时，重传数据对应的进程号为5；当初传数据对应的进程号为10时，重传数据对应的进程号为2。
当第一载波为TDD载波，第二载波为TDD载波时，若第二载波当前的上下行子帧配比为表中的2号配置(对应进程数目10)，则当初传数据对应的进程号为8时，重传数据对应的进程号为8；当初传数据对应的进程号为14时，重传数据对应的进程号为4。
表一
Figure PCTCN2015098096-appb-000001
下面通过几个具体的实施例对本公开文本实施例的思想作进一步描述。
实施例二
应用场景：初传位于非授权频段的第一载波(比如对应某个辅小区Scell)，重传位于授权频段的第二载波(比如对应主小区Pcell)。图2(a)为该应用场景示意图，图中D代表下行子帧，U代表上行子帧。
具体实施过程如图2(b)所示，包括以下步骤：
S201：若基站在位于非授权频段的第一载波上向UE传输数据时，接收到UE反馈的数据传输失败(NACK)消息，在确定无法继续使用该第一载波进行数据重传时，确定需要在位于授权频段的第二载波上进行数据重传。
S202：基站在第二载波的PDCCH上向UE传输DCI。
S203：UE在第二载波的PDCCH上检测到DCI后，确认其中携带指示第一载波的CIF和用于说明CIF所指示的载波为传输初传数据的载波的指示位。
S204：基站在第二载波上向UE传输之前在第一载波上传输失败的数据。
S205：UE接收到在第二载波上传输的重传数据后，根据该重传数据对应的进程号，提取出存储的对应该进程号的之前在第一载波上接收的初传数据。
S206：UE将在第二载波上接收的重传数据与提取的所述初传数据进行合并。
实施例三
应用场景：初传位于非授权频段的第一载波(比如对应某个辅小区Scell)，重传位于非授权频段的第二载波(比如对应另外一个辅小区Scell)。图3(a)为该应用场景示意图。
具体实施过程如图3(b)所示，包括以下步骤：
S301：若基站在位于非授权频段的第一载波上向UE传输数据时，接收到UE反馈的数据传输失败(NACK)消息，在确定无法继续使用该第一载波进行数据重传时，确定需要在位于非授权频段的第二载波上进行数据重传。
S302：基站在第二载波的PDCCH上向UE传输DCI。
S303：UE在第二载波的PDCCH上检测到DCI后，确认其中携带指示第一载波的CIF和用于说明CIF所指示的载波为传输初传数据的载波的指示位。
S304：基站在第二载波上向UE传输之前在第一载波上传输失败的数据。
S305：UE接收到在第二载波上传输的重传数据后，根据该重传数据对应 的进程号，提取出存储的与该进程号对应的之前在第一载波上接收的初传数据。
S306：UE将在第二载波上接收的重传数据与提取的所述初传数据进行合并。
实施例四
应用场景：初传位于非授权频段的第一载波，重传先考虑非授权频段的载波，如果在约束条件内无法找到合适的非授权频段的载波，则查找授权频段的载波。具体实施过程如图4所示，包括以下步骤：
S401：基站在位于非授权频段的第一载波上向UE传输数据时，接收到UE反馈的数据传输失败(NACK)消息，并确定无法继续使用该第一载波进行数据重传。
S402：若在预设的时间长度或者遍历次数内，查找到能够用于进行数据重传的非授权频段的载波，则将查找到的非授权频段的载波作为进行数据重传的第二载波，否则，将授权频段的载波作为所述第二载波。
S403：基站在第二载波的PDCCH上向UE传输DCI。
S404：UE在第二载波的PDCCH上检测到DCI后，确认其中携带指示第一载波的CIF和用于说明CIF所指示的载波为传输初传数据的载波的指示位。
S405：基站在第二载波上向UE传输之前在第一载波上传输失败的数据。
S406：UE接收到在第二载波上传输的重传数据后，根据该重传数据对应的进程号，提取出存储的与该进程号对应的之前在第一载波上接收的初传数据。
S407：UE将在第二载波上接收的重传数据与提取的所述初传数据进行合并。
实施例五
应用场景与实施例二相同，初传位于非授权频段的第一载波(比如对应某个辅小区Scell)，重传位于授权频段的第二载波(比如对应主小区Pcell)。该实施例中，DCI中不仅携带指示传输初传数据的载波的第一信息，还携带指示初传数据的进程号的第二信息。
具体实施过程如图5所示，包括以下步骤：
S501：若基站在位于非授权频段的第一载波上向UE传输数据时，接收到UE反馈的数据传输失败(NACK)消息，在确定无法继续使用该第一载波进行数据重传时，确定需要在位于授权频段的第二载波上进行数据重传。
S502：基站在第二载波的PDCCH上向UE传输DCI。
S503：UE在第二载波的PDCCH上检测到DCI后，确认其中携带指示第一载波的CIF、用于说明CIF所指示的载波为传输初传数据的载波的指示位、以及指示初传数据对应的进程号和重传数据对应的进程号的指示位。
S504：基站在第二载波上向UE传输之前在第一载波上传输失败的数据。
S505：UE接收到在第二载波上传输的对应DCI中所指示的进程号的重传数据后，根据DCI中指示的初传数据对应的进程号，提取出存储的之前在第一载波上接收的初传数据。
S506：UE将在第二载波上接收的重传数据与提取的所述初传数据进行合并。
实施例六
应用场景与实施例三相同，初传位于非授权频段的第一载波(比如对应某个辅小区Scell)，重传位于非授权频段的第二载波(比如对应另外一个辅小区Scell)。该实施例中，DCI中不仅携带指示传输初传数据的载波的第一信息，还携带指示初传数据的进程号的第二信息。
具体实施过程如图6所示，包括以下步骤：
S601：若基站在位于非授权频段的第一载波上向UE传输数据时，接收到UE反馈的数据传输失败(NACK)消息，在确定无法继续使用该第一载波进行数据重传时，确定需要在位于非授权频段的第二载波上进行数据重传。
S602：基站在第二载波的PDCCH上向UE传输DCI。
S603：UE在第二载波的PDCCH上检测到DCI后，确认其中携带指示第一载波的CIF、用于说明CIF所指示的载波为传输初传数据的载波的指示位、以及指示初传数据对应的进程号和重传数据对应的进程号的指示位。
S604：基站在第二载波上向UE传输之前在第一载波上传输失败的数据。
S605：UE接收到在第二载波上传输的对应DCI中所指示的进程号的重传数据后，根据DCI中指示的初传数据对应的进程号，提取出存储的之前在 第一载波上接收的初传数据。
S606：UE将在第二载波上接收的重传数据与提取的所述初传数据进行合并。
实施例七
应用场景与实施例四相同，初传位于非授权频段的第一载波，重传先考虑非授权频段的载波，如果在约束条件内无法找到合适的非授权频段的载波，则查找授权频段的载波。该实施例中，DCI中不仅携带指示传输初传数据的载波的第一信息，还携带指示初传数据的进程号的第二信息。
具体实施过程如图7所示，包括以下步骤：
S701：基站在位于非授权频段的第一载波上向UE传输数据时，接收到UE反馈的数据传输失败(NACK)消息，并确定无法继续使用该第一载波进行数据重传。
S702：若在预设的时间长度或者遍历次数内，查找到能够用于进行数据重传的非授权频段的载波，则将查找到的非授权频段的载波作为进行数据重传的第二载波，否则，将授权频段的载波作为所述第二载波。
S703：基站在第二载波的PDCCH上向UE传输DCI。
S704：UE在第二载波的PDCCH上检测到DCI后，确认其中携带指示第一载波的CIF、用于说明CIF所指示的载波为传输初传数据的载波的指示位、以及指示初传数据对应的进程号和重传数据对应的进程号的指示位。
S705：基站在第二载波上向UE传输之前在第一载波上传输失败的数据。
S706：UE接收到在第二载波上传输的对应DCI中所指示的进程号的重传数据后，根据DCI中指示的初传数据对应的进程号，提取出存储的之前在第一载波上接收的初传数据。
S707：UE将在第二载波上接收的重传数据与提取的所述初传数据进行合并。
基于同一发明构思，本公开文本实施例中还提供了一种与数据重传方法对应的数据重传装置，由于该装置解决问题的原理与本公开文本实施例的数据重传方法相似，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
如图8所示，为本公开文本实施例一提供的数据重传装置结构示意图，包括：
接收模块81，用于接收基站在第二载波上传输给用户设备UE的重传数据；所述重传数据为之前在第一载波上传输失败的数据；以及
合并模块82，用于将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。
可选地，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
可选地，所述接收模块81还用于，接收在第二载波上传输的重传数据之前，接收在第二载波上传输的下行控制信息DCI；所述DCI用于指示所述UE接收在第二载波上传输的下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
可选地，所述DCI中包括：
指示传输所述初传数据的第一载波的第一信息；和/或
指示所述初传数据对应的进程号的第二信息。
可选地，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
可选地，所述接收模块81还用于，接收在第二载波上传输的重传数据之前，在确定在第一载波上接收数据失败后，根据重传载波选择原则和进程号选择原则，确定进行数据重传的第二载波和重传数据对应的进程号；在需要接收下行数据时，若确定传输该下行数据的载波为之前确定的进行数据重传的第二载波，并且该下行数据对应的进程号为之前确定的重传数据对应的进程号，则确定需要接收的该下行数据为所述重传数据。
可选地，所述重传载波选择原则包括：从参与载波聚合CA的载波中，选择负载最小、信道条件最好的载波作为所述第二载波。
可选地，所述进程号选择原则包括：
确定所述初传数据对应的进程号对所述第二载波能够承载的进程数目取模后的值；
若所述取模后的值不为0，则选择所述重传数据对应的进程号为所述取 模后的值；
若所述取模后的值为0，则选择所述重传数据对应的进程号为所述第二载波能够承载的进程数目的取值；或者，选择所述重传数据对应的进程号为预设的进程号。
可选地，当所述第二载波为频分双工FDD载波时，所述第二载波能够承载的进程数目为8；当所述第二载波为时分双工TDD载波时，所述第二载波能够承载的进程数目为所述第二载波在当前所处的上下行子帧配比下能够承载的进程数目。
如图9所示，为本公开文本实施例二提供的数据重传装置结构示意图，包括：
配置模块91，用于当在第一载波上向用户设备UE传输数据失败时，若确定无法继续使用所述第一载波进行数据重传，则为所述UE配置进行数据重传的第二载波；以及
传输模块92，用于在所述配置模块91配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据。
可选地，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
可选地，所述配置模块91具体用于：
若在预设的时间长度或者遍历次数内，查找到能够用于进行数据重传的非授权频段的载波，则将查找到的非授权频段的载波作为所述第二载波，否则，将授权频段的载波作为所述第二载波。
可选地，所述传输模块92还用于，在配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据之前，在所述第二载波上向所述UE传输下行控制信息DCI。所述DCI用于指示所述UE在所述第二载波上接收下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
可选地，所述DCI中包括：
指示传输所述初传数据的第一载波的第一信息；和/或
指示所述初传数据对应的进程号的第二信息。
可选地，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
本领域内的技术人员应明白，本公开文本的实施例可提供为方法、系统、或计算机程序产品。因此，本公开文本可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开文本可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本公开文本是参照根据本公开文本实施例的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本公开文本的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本公开文本范围的所有变更和修改。
显然，本领域的技术人员可以对本公开文本进行各种改动和变型而不脱离本公开文本的精神和范围。这样，倘若本公开文本的这些修改和变型属于本公开文本权利要求及其等同技术的范围之内，则本公开文本也意图包含这些改动和变型在内。

Claims (30)

  1. 一种数据重传方法，包括：
    接收基站在第二载波上传输给用户设备UE的重传数据；所述重传数据为之前在第一载波上传输失败的数据；以及
    将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。
  2. 如权利要求1所述的方法，其中，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
  3. 如权利要求1或2所述的方法，其中，接收在第二载波上传输的重传数据之前，还包括：
    接收在第二载波上传输的下行控制信息DCI；所述DCI用于指示所述UE接收在第二载波上传输的下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
  4. 如权利要求3所述的方法，其中，所述DCI中包括：
    指示传输所述初传数据的第一载波的第一信息；和/或
    指示所述初传数据对应的进程号的第二信息。
  5. 如权利要求4所述的方法，其中，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
  6. 如权利要求1或2所述的方法，其中，接收在第二载波上传输的重传数据之前，还包括：
    当确定在第一载波上接收数据失败后，根据重传载波选择原则和进程号选择原则，确定进行数据重传的第二载波和重传数据对应的进程号；以及
    在需要接收下行数据时，若确定传输该下行数据的载波为之前确定的进行数据重传的第二载波，并且该下行数据对应的进程号为之前确定的重传数据对应的进程号，则确定需要接收的该下行数据为所述重传数据。
  7. 如权利要求6所述的方法，其中，所述重传载波选择原则包括：从参与载波聚合CA的载波中，选择负载最小、信道条件最好的载波作为所述第 二载波。
  8. 如权利要求6所述的方法，其中，所述进程号选择原则包括：
    确定所述初传数据对应的进程号对所述第二载波能够承载的进程数目取模后的值；
    若所述取模后的值不为0，则选择所述重传数据对应的进程号为所述取模后的值；
    若所述取模后的值为0，则选择所述重传数据对应的进程号为所述第二载波能够承载的进程数目的取值；或者，选择所述重传数据对应的进程号为预设的进程号。
  9. 如权利要求8所述的方法，其中，当所述第二载波为频分双工FDD载波时，所述第二载波能够承载的进程数目为8；当所述第二载波为时分双工TDD载波时，所述第二载波能够承载的进程数目为所述第二载波在当前所处的上下行子帧配比下能够承载的进程数目。
  10. 一种数据重传方法，包括：
    当在第一载波上向用户设备UE传输数据失败时，若确定无法继续使用所述第一载波进行数据重传，则为所述UE配置进行数据重传的第二载波；以及
    在配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据。
  11. 如权利要求10所述的方法，其中，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
  12. 如权利要求11所述的方法，其中，为所述UE配置进行数据重传的第二载波，包括：
    若在预设的时间长度或者遍历次数内，查找到能够用于进行数据重传的非授权频段的载波，则将查找到的非授权频段的载波作为所述第二载波，否则，将授权频段的载波作为所述第二载波。
  13. 如权利要求10～12任一所述的方法，其中，在配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据之前，还包括：
    在所述第二载波上向所述UE传输下行控制信息DCI；所述DCI用于指 示所述UE在所述第二载波上接收下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
  14. 如权利要求13所述的方法，其中，所述DCI中包括：
    指示传输所述初传数据的第一载波的第一信息；和/或
    指示所述初传数据对应的进程号的第二信息。
  15. 如权利要求14所述的方法，其中，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
  16. 一种数据重传装置，包括：
    接收模块，用于接收基站在第二载波上传输给用户设备UE的重传数据；所述重传数据为之前在第一载波上传输失败的数据；以及
    合并模块，用于将接收的重传数据与之前在第一载波上接收的该重传数据对应的初传数据进行合并。
  17. 如权利要求16所述的装置，其中，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
  18. 如权利要求16或17所述的装置，其中，所述接收模块还用于，接收在第二载波上传输的重传数据之前，接收在第二载波上传输的下行控制信息DCI；所述DCI用于指示所述UE接收在第二载波上传输的下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
  19. 如权利要求18所述的装置，其中，所述DCI中包括：
    指示传输所述初传数据的第一载波的第一信息；和/或
    指示所述初传数据对应的进程号的第二信息。
  20. 如权利要求19所述的装置，其中，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
  21. 如权利要求16或17所述的装置，其中，所述接收模块还用于，接收在第二载波上传输的重传数据之前，当确定在第一载波上接收数据失败后，根据重传载波选择原则和进程号选择原则，确定进行数据重传的第二载波和重传数据对应的进程号；在需要接收下行数据时，若确定传输该下行数据的 载波为之前确定的进行数据重传的第二载波，并且该下行数据对应的进程号为之前确定的重传数据对应的进程号，则确定需要接收的该下行数据为所述重传数据。
  22. 如权利要求21所述的装置，其中，所述重传载波选择原则包括：从参与载波聚合CA的载波中，选择负载最小、信道条件最好的载波作为所述第二载波。
  23. 如权利要求21所述的装置，其中，所述进程号选择原则包括：
    确定所述初传数据对应的进程号对所述第二载波能够承载的进程数目取模后的值；
    若所述取模后的值不为0，则选择所述重传数据对应的进程号为所述取模后的值；
    若所述取模后的值为0，则选择所述重传数据对应的进程号为所述第二载波能够承载的进程数目的取值；或者，选择所述重传数据对应的进程号为预设的进程号。
  24. 如权利要求23所述的装置，其中，当所述第二载波为频分双工FDD载波时，所述第二载波能够承载的进程数目为8；当所述第二载波为时分双工TDD载波时，所述第二载波能够承载的进程数目为所述第二载波在当前所处的上下行子帧配比下能够承载的进程数目。
  25. 一种数据重传装置，包括：
    配置模块，用于当在第一载波上向用户设备UE传输数据失败时，若确定无法继续使用所述第一载波进行数据重传，则为所述UE配置进行数据重传的第二载波；以及
    传输模块，用于在所述配置模块配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据。
  26. 如权利要求25所述的装置，其中，所述第一载波位于非授权频段；所述第二载波位于非授权频段或授权频段。
  27. 如权利要求26所述的装置，其中，所述配置模块具体用于：
    若在预设的时间长度或者遍历次数内，查找到能够用于进行数据重传的非授权频段的载波，则将查找到的非授权频段的载波作为所述第二载波，否 则，将授权频段的载波作为所述第二载波。
  28. 如权利要求25～27任一所述的装置，其中，所述传输模块还用于，在配置的所述第二载波上，向所述UE重传之前在所述第一载波上传输失败的数据之前，在所述第二载波上向所述UE传输下行控制信息DCI；所述DCI用于指示所述UE在所述第二载波上接收下行数据，并将接收的下行数据作为重传数据，与该重传数据对应的初传数据进行合并。
  29. 如权利要求28所述的装置，其中，所述DCI中包括：
    指示传输所述初传数据的第一载波的第一信息；和/或
    指示所述初传数据对应的进程号的第二信息。
  30. 如权利要求29所述的装置，其中，所述第一信息包括指示第一载波的载波指示位CIF和用于说明该CIF所指示的载波为传输所述初传数据的载波的1比特指示位。
PCT/CN2015/098096 2015-02-10 2015-12-21 一种数据重传方法及装置 Ceased WO2016127704A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/550,249 US10341062B2 (en) 2015-02-10 2015-12-21 Data retransmission method and apparatus
EP15881852.6A EP3249841B1 (en) 2015-02-10 2015-12-21 Data retransmission method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510070005.6 2015-02-10
CN201510070005.6A CN105991246B (zh) 2015-02-10 2015-02-10 一种数据重传方法及装置

Publications (1)

Publication Number Publication Date
WO2016127704A1 true WO2016127704A1 (zh) 2016-08-18

Family

ID=56614208

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/098096 Ceased WO2016127704A1 (zh) 2015-02-10 2015-12-21 一种数据重传方法及装置

Country Status (4)

Country Link
US (1) US10341062B2 (zh)
EP (1) EP3249841B1 (zh)
CN (1) CN105991246B (zh)
WO (1) WO2016127704A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118826968A (zh) * 2024-09-18 2024-10-22 戎行技术有限公司 针对大批量数据的中途失败数据处理方法及装置

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10075970B2 (en) * 2015-03-15 2018-09-11 Qualcomm Incorporated Mission critical data support in self-contained time division duplex (TDD) subframe structure
US10342012B2 (en) 2015-03-15 2019-07-02 Qualcomm Incorporated Self-contained time division duplex (TDD) subframe structure
US9936519B2 (en) 2015-03-15 2018-04-03 Qualcomm Incorporated Self-contained time division duplex (TDD) subframe structure for wireless communications
US9992790B2 (en) 2015-07-20 2018-06-05 Qualcomm Incorporated Time division duplex (TDD) subframe structure supporting single and multiple interlace modes
CN108023719B (zh) 2016-11-04 2020-01-21 华为技术有限公司 混合自动重传请求harq码本的生成方法及相关设备
CN106533644B (zh) * 2016-11-28 2019-10-22 上海华为技术有限公司 一种进行CoMP传输的方法和基站
WO2018107458A1 (zh) * 2016-12-16 2018-06-21 富士通株式会社 用于免授权传输的装置、方法以及通信系统
CN109217974B (zh) * 2017-06-29 2021-07-09 华为技术有限公司 一种数据传输方法和相关设备
US11895659B2 (en) 2018-09-28 2024-02-06 Beijing Xiaomi Mobile Software Co., Ltd. Control instruction transmission method, base station, terminal and storage medium
US11164671B2 (en) 2019-01-22 2021-11-02 International Business Machines Corporation Continuous compliance auditing readiness and attestation in healthcare cloud solutions
US11495347B2 (en) 2019-01-22 2022-11-08 International Business Machines Corporation Blockchain framework for enforcing regulatory compliance in healthcare cloud solutions
WO2020155108A1 (zh) * 2019-02-01 2020-08-06 北京小米移动软件有限公司 混合自动重传的方法及装置
US20230073219A1 (en) * 2021-08-18 2023-03-09 Alireza Babaei Enhanced Cross-carrier Processes

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101964704A (zh) * 2009-07-23 2011-02-02 华为技术有限公司 混合自动重传请求通信方法、装置与通信系统
EP2391046A2 (en) * 2010-04-02 2011-11-30 Acer Incorporated Method of handling component carrier activation and deactivation and communication device thereof
CN102651679A (zh) * 2011-02-28 2012-08-29 华为技术有限公司 数据传输方法、演进基站以及用户设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100352243C (zh) * 2005-08-19 2007-11-28 中兴通讯股份有限公司 时分同步码分多址系统多载波高速下行分组接入实现方法
CN1976271A (zh) * 2005-11-28 2007-06-06 上海贝尔阿尔卡特股份有限公司 用于多载波系统基于加权合并的混合自动重传方法及系统
US8934405B2 (en) * 2008-05-06 2015-01-13 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for retransmission scheduling and control in multi-carrier wireless communication networks
WO2010032714A1 (ja) * 2008-09-17 2010-03-25 シャープ株式会社 移動通信システム、基地局装置、移動局装置および通信方法
CA2753725C (en) * 2009-03-13 2018-07-31 Research In Motion Limited Harq process number management for downlink carrier aggregation
KR101782640B1 (ko) 2009-07-16 2017-09-28 엘지전자 주식회사 다중 반송파 시스템에서 ｈａｒｑ 수행 장치 및 방법
KR20110090521A (ko) * 2010-02-04 2011-08-10 주식회사 팬택 무선통신 시스템에서 데이터 및 제어정보의 전송 방법 및 그 송신장치, 그 수신장치
CN102208966B (zh) * 2010-03-30 2014-04-09 中兴通讯股份有限公司 一种harq合并器和harq数据存储方法
CN103684713A (zh) * 2012-09-26 2014-03-26 中国移动通信集团公司 一种载波聚合场景下上行数据信道重传的方法和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101964704A (zh) * 2009-07-23 2011-02-02 华为技术有限公司 混合自动重传请求通信方法、装置与通信系统
EP2391046A2 (en) * 2010-04-02 2011-11-30 Acer Incorporated Method of handling component carrier activation and deactivation and communication device thereof
CN102651679A (zh) * 2011-02-28 2012-08-29 华为技术有限公司 数据传输方法、演进基站以及用户设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KYOCERA.: "HARQ retransmissions on LAA", 3GPP TSG-RAN WG2 #89 R2-150268, 31 January 2015 (2015-01-31), XP050952459 *
See also references of EP3249841A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118826968A (zh) * 2024-09-18 2024-10-22 戎行技术有限公司 针对大批量数据的中途失败数据处理方法及装置

Also Published As

Publication number Publication date
EP3249841A4 (en) 2018-01-17
CN105991246A (zh) 2016-10-05
EP3249841B1 (en) 2020-02-12
CN105991246B (zh) 2019-04-02
EP3249841A1 (en) 2017-11-29
US20180048431A1 (en) 2018-02-15
US10341062B2 (en) 2019-07-02

Similar Documents

Publication Publication Date Title
WO2016127704A1 (zh) 一种数据重传方法及装置
CN104756431B (zh) 无线通信中确认时序的选择
CN103782638B (zh) 多小区通信网络中的控制时序配置的方法、装置及存储介质
CN105393485B (zh) 无线通信系统中的方法和节点
WO2020057639A1 (zh) 混合自动重传请求确认码本的传输方法和设备
US9973324B2 (en) Transmission method and apparatus in TDD-FDD joint system
WO2017015836A1 (zh) 应答信息发送、接收方法，及接收设备和发送设备
CN105634693A (zh) 用于载波聚合系统的通信方法和装置
CN108282271A (zh) 用于tdd系统的调度定时设计
CN103580830A (zh) 一种发送harq-ack反馈信息的方法
CN105846977A (zh) 一种增强载波聚合系统的harq-ack传输方法和设备
KR20120093084A (ko) 응답 채널 자원들을 할당하는 방법 및 장치
CN105009496A (zh) 用于在通信系统中确定harq定时的方法和装置
WO2013131435A1 (zh) 一种harq反馈的实现方法及装置
CN106301702A (zh) 一种增强载波聚合系统的harq-ack传输方法和设备
CN106301725B (zh) 资源分配方法及装置
WO2012163170A1 (zh) 一种数据传输的方法及装置
TW201519680A (zh) 用於傳輸控制資訊的方法和設備
CN105814811A (zh) 基于载波聚合的无线通信系统中的通信方法
WO2017016351A1 (zh) 一种上行数据的传输方法及装置
WO2016158087A1 (ja) ユーザ装置及び基地局
KR20140030322A (ko) 피드백 정보를 송수신하는 방법, 시스템 및 장치
WO2020015667A1 (zh) 上行传输方法、装置、终端及网络侧设备
WO2016131235A1 (zh) 信息传输的方法、用户设备和基站
WO2018059073A1 (zh) 一种上行控制信息uci的传输方法和设备

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15550249

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015881852

Country of ref document: EP