CN109039529B - Data transmission method and data transmission device - Google Patents

Data transmission method and data transmission device Download PDF

Info

Publication number
CN109039529B
CN109039529B CN201710431047.7A CN201710431047A CN109039529B CN 109039529 B CN109039529 B CN 109039529B CN 201710431047 A CN201710431047 A CN 201710431047A CN 109039529 B CN109039529 B CN 109039529B
Authority
CN
China
Prior art keywords
end device
receiving end
data segment
segment corresponding
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.)
Active
Application number
CN201710431047.7A
Other languages
Chinese (zh)
Other versions
CN109039529A (en
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.)
Suzhou Yudeshui Electric Technology Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201710431047.7A priority Critical patent/CN109039529B/en
Priority to PCT/CN2018/089030 priority patent/WO2018223877A1/en
Publication of CN109039529A publication Critical patent/CN109039529A/en
Application granted granted Critical
Publication of CN109039529B publication Critical patent/CN109039529B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045Arrangements at the receiver end
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056Systems characterized by the type of code used
    • H04L1/0067Rate matching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/04Error control

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

The application provides a data transmission method and a data transmission device, wherein the data transmission method comprises the following steps: receiving end equipment receives a coded data block corresponding to a first Redundancy Version (RV) of a data block sent by sending end equipment; the receiving end equipment decodes according to the coded data segment corresponding to the first RV; when the decoding fails, the receiving end equipment sends a request message to the sending end equipment, wherein the request message is used for requesting the coded data segment corresponding to the second RV; and the receiving end device receives the coded data segment corresponding to the second RV, which is sent by the sending end device according to the request message. The data transmission method and the data transmission device are beneficial to improving the success rate of decoding.

Description

Data transmission method and data transmission device
Technical Field
The present application relates to the field of communications, and more particularly, to a data transmission method and a data transmission apparatus in the field of communications.
Background
In a Long Term Evolution (LTE) communication system, a sending end device sends a data block to a receiving end device by using a hybrid automatic repeat request (HARQ) mechanism, and specifically, the sending end device encodes the data block by using a Turbo code to obtain a coded data block, divides the coded data block to obtain a plurality of coded data segments, where the plurality of coded data segments correspond to different Redundancy Versions (RVs) of the data block, the sending end device sequentially sends the coded data segment corresponding to each RV in the plurality of RVs according to a preset RV sending order, and if the receiving end device receives the coded data segment corresponding to an mth RV sent by the sending end device or the receiving end device receives the coded data segment corresponding to the mth RV, but decoding fails according to the coded data segment corresponding to the mth RV, the sending end device sends the coded data segment corresponding to the (m + 1) th RV, and the receiving end device decodes according to the (m + 1) th RV, wherein m is an integer greater than 0.
However, in a communication system in which a data channel is encoded by using a Low Density Parity Check (LDPC) code, the success rate of decoding by a receiving device may be higher only if the encoded data segments received by the receiving device are as continuous as possible. Therefore, if the HARQ mechanism in the LTE communication system is used to transmit the data block, the success rate of decoding is low.
Disclosure of Invention
The application provides a data transmission method and a data transmission device, which are beneficial to improving the success rate of decoding.
In a first aspect, the present application provides a data transmission method, including:
receiving end equipment receives a coded data block corresponding to a first Redundancy Version (RV) of a data block sent by sending end equipment;
the receiving end equipment decodes according to the coded data segment corresponding to the first RV;
when the decoding fails, the receiving end equipment sends a request message to the sending end equipment, wherein the request message is used for requesting the coded data segment corresponding to the second RV;
and the receiving end device receives the coded data segment corresponding to the second RV, which is sent by the sending end device according to the request message.
According to the data transmission method provided by the embodiment of the application, when the receiving end device fails to decode the encoded data segment corresponding to the received first RV, the receiving end device actively sends the request message to the sending end device to request the encoded data segment corresponding to the second RV, and after receiving the encoded data segment corresponding to the second RV sent by the sending end device according to the request message, the receiving end device can decode according to the received encoded data segments corresponding to all RVs, so that the decoding success rate and the decoding flexibility of the receiving end device are improved.
Optionally, the request message may carry indication information of the second RV.
It should be understood that the data transmission method can be used in the uplink data transmission scenario as well as the downlink data transmission scenario. In the context of uplink data transmission, the sending end device may be a terminal device, and the receiving end device may be a network device; in a scenario of downlink data transmission, the sending end device may be a network device, and the receiving end device may be a terminal device, which is not limited in this application embodiment.
Optionally, the sending end device sends, to the receiving end device, the encoded data segment corresponding to the first RV of the data block, which may be: the sending end device sends the indication information of the first RV and the first encoded data segment to the receiving end device, where the indication information of the first RV is used to indicate that the first encoded data segment is the encoded data segment corresponding to the first RV.
As an optional embodiment, in a scenario of downlink data transmission, the network device may send the indication information of the first RV to the terminal device through a downlink control channel, and send the coded bit segment corresponding to the first RV to the terminal device through a downlink data channel, which is not limited in this application.
Optionally, the sending end device sends the encoded data segment corresponding to the first RV to the receiving end device, which may be to transmit the data block to the receiving end device for the first time, or may be to retransmit the data block to the receiving end device for the sending end device, and this is not limited in this embodiment of the application.
It should be understood that, before receiving, by a receiving end device, a coded data block corresponding to a first RV of a data block sent by a sending end device, the sending end device may perform coding and rate matching on the data block to obtain the coded data block, and write the coded data block into a cyclic cache, where the coded data block written into the cyclic cache is divided into coded data segments corresponding to a plurality of RVs, and the sending end device selects a coded data segment corresponding to a certain RV each time for transmission.
Optionally, the indication information of different RVs of the data block may be indication information that can uniquely indicate the RV, such as a serial number of the RV in a preset RV sequence, a value of the RV, a number of the RV, and an identifier of the RV, which is not limited in this embodiment of the present application.
It should also be understood that the sending end device and the receiving end device may pre-agree on a sending sequence (also referred to as an RV sequence) of the RVs and a sequence number (also referred to as a number, a value, etc.) of each RV in the RVs, for example, the sending end device may agree on a protocol, or the sending end device indicates the receiving end device through a notification message before transmitting the data block, which is not limited in this application.
For example, a coded data block 1 in the circular buffer is divided into coded data segments corresponding to 4 RVs, values of the 4 RVs are RV0, RV1, RV2, and RV3, and a predetermined RV sequence of the transmitting end device and the receiving end device is as follows: RV0-RV2-RV3-RV1, when the transmitting end device transmits the data block, the encoded data segment corresponding to RV0, the encoded data segment corresponding to RV2, the encoded data segment corresponding to RV3, and the encoded data segment corresponding to RV1 are sequentially transmitted according to the RV sequence.
Optionally, the number of the RVs in this application embodiment may be, for example, 4, 8, 16, 32 or other values, which is not limited in this application embodiment.
Optionally, the sending end device and the receiving end device may pre-agree on a starting position of the encoded data segment corresponding to each RV of the data block in the circular buffer, for example, the starting position may be agreed by a protocol, or the sending end device indicates the receiving end device through a notification message before transmitting the data block, which is not limited in this embodiment of the present application.
Optionally, the coded data segment corresponding to each RV of the plurality of RVs may include some or all bits of the data block.
Optionally, in the multiple RVs, the coded data segments corresponding to different RVs may not overlap, or the coded data segments corresponding to different RVs may partially overlap, or the coded data segment corresponding to a previous RV and the coded data segment corresponding to a next RV in any two consecutive RVs are consecutive, which is not limited in this embodiment of the present application.
Optionally, assume that the number of RVs of the data block is 2nThe receiving end device may indicate the 2 by n bits, or may indicate the 2 in a differential coding mannernAny one of the RVs, or the 2 can be indicated by other meansnAny one of the RVs is not limited in this application.
In a possible implementation manner, before the receiving end device sends the request message to the sending end device, the data transmission method further includes: the receiving end device determines the second RV according to the received RV of the encoded data segment and the preconfigured RV sequence.
In another possible implementation manner, the determining, by the receiving end device, the second RV according to the RV of the received encoded data segment and a preconfigured RV sequence includes: the receiving end equipment determines that at least one RV which is not received exists before the first RV is received according to the RV of the received coded data segment and the RV sequence; the receiving end device determines the most forward RV in the RV sequence in the at least one RV as the second RV.
As an alternative embodiment, the receiving end device may determine all the non-received at least one RV in the RV sequence before the first RV, and use the most previous RV in the RV sequence in the at least one RV as the second RV.
As another alternative, the receiving end device may use the first non-received RV before the first RV in the RV sequence as the second RV.
In the data transmission method provided in the embodiment of the present application, the receiving end device uses the first RV, which is not received before the first RV in the RV sequence, as the second RV, and requests the transmitting end device for the encoded data segment corresponding to the second RV, so that the encoded data segment corresponding to the second RV and the encoded data segment corresponding to the RV before the first RV can be continuous as much as possible, thereby improving the decoding success rate of the receiving end device and the reliability of data transmission.
In another possible implementation manner, the determining, by the receiving end device, the second RV according to the RV of the received encoded data segment and the preconfigured RV sequence includes: the receiving end equipment determines that no RV which is not received exists before the first RV is received according to the RV of the received coded data segment and the RV sequence; the receiving end device determines the next RV of the first RV in the RV sequence as the second RV.
In the data transmission method provided in the embodiment of the present application, after receiving end equipment has received all RVs before the first RV in the RV sequence, a subsequent RV of the second RV is used as a second RV, and a coding data segment corresponding to the second RV is requested from sending end equipment, so that the coding data segment corresponding to the second RV and the coding data segment corresponding to the first RV are continuous as much as possible, thereby improving the decoding success rate of the receiving end equipment and the reliability of data transmission.
In a second aspect, the present application provides a data transmission method, including:
the sending end equipment sends a coded data segment corresponding to a first redundancy version RV of a data block to the receiving end equipment;
when the receiving end equipment fails to decode according to the coded data segment corresponding to the first RV, the sending end equipment receives a request message sent by the receiving end equipment, wherein the request message is used for requesting the coded data segment corresponding to a second RV;
and the sending end equipment sends the coded data segment corresponding to the second RV to the receiving end equipment according to the request message.
In the data transmission method provided by the embodiment of the application, after the sending end device sends the encoded data segment corresponding to the first RV to the receiving end device, when receiving the request message sent by the receiving end device for requesting the encoded data segment corresponding to the second RV, the sending end device sends the encoded data segment corresponding to the second RV to the receiving end device according to the request message, which is beneficial to improving the decoding success rate and the decoding flexibility of the receiving end device.
Optionally, the request message may carry indication information of the second RV.
In one possible implementation, the second RV is determined according to the RV of the encoded data segment that has been received by the receiving end device and a preconfigured RV sequence.
In another possible implementation, the second RV is the first RV in the RV sequence that is not received by the receiving end device before the first RV.
In the data transmission method provided in the embodiment of the present application, the sending end device sends, to the receiving end device, a coded data segment corresponding to a second RV according to the request message sent by the receiving end device, where the second RV takes a first RV, which is not received before the first RV in the RV sequence, as a second RV, so that the coded data segment corresponding to the second RV and the coded data segment corresponding to the RV before the first RV, which are received by the receiving end device, are continuous as much as possible, thereby improving the decoding success rate of the receiving end device and the reliability of data transmission.
In another possible implementation manner, the second RV is a next RV of the first RV in the RV sequence, where the receiving end device has received all RVs before the first RV in the RV sequence.
In the data transmission method provided in the embodiment of the present application, the sending end device sends, to the receiving end device, the encoded data segment corresponding to the second RV according to the request message sent by the receiving end device, where the second RV is a next RV of the first RV in the RV sequence, and the receiving end device has received all RVs before the first RV in the RV sequence, so that the encoded data segment corresponding to the second RV and the encoded data segment corresponding to the first RV, which are received by the receiving end device, are continuous as much as possible, thereby improving the decoding success rate of the receiving end device and the reliability of data transmission.
In a third aspect, the present application provides a data transmission method, including:
the sending end equipment sends a coded data segment corresponding to a first redundancy version RV of a data block to the receiving end equipment;
the sending end equipment receives a feedback message sent by the receiving end equipment, wherein the feedback message is used for feeding back the coded data segment corresponding to the first RV, which is not received;
and the sending end equipment retransmits the coded data segment corresponding to the first RV to the receiving end equipment.
According to the data transmission method provided by the embodiment of the application, when the receiving end device does not receive the coded data segment corresponding to the first RV sent by the sending end device, the sending end device retransmits the coded data segment corresponding to the first RV to the receiving end device, so that the coded data segment received by the receiving end device is as continuous as possible, and the decoding success rate of the receiving end and the reliability of data transmission are improved.
It should be understood that the data transmission method can be used in the uplink data transmission scenario as well as the downlink data transmission scenario. In the context of uplink data transmission, the sending end device may be a terminal device, and the receiving end device may be a network device; in a scenario of downlink data transmission, the sending end device may be a network device, and the receiving end device may be a terminal device, which is not limited in this application embodiment.
In a fourth aspect, the present application provides a data transmission method, including:
when receiving end equipment does not receive the coded data segment corresponding to the first redundancy version RV of the data block sent by sending end equipment, the receiving end equipment sends a feedback message to the sending end equipment, wherein the feedback message is used for feeding back the coded data segment corresponding to the first RV which is not received;
and the receiving end equipment receives the coded data segment corresponding to the first RV retransmitted by the sending end equipment according to the feedback message.
According to the data transmission method provided by the embodiment of the application, when the receiving end device does not receive the coded data segment corresponding to the first RV sent by the sending end device, the receiving end device sends the feedback message to the sending end device and receives the coded data segment corresponding to the first RV retransmitted by the sending end device according to the feedback message, so that the coded data segment received by the receiving end device is continuous as much as possible, and the decoding success rate of the receiving end and the reliability of data transmission are improved.
In a fifth aspect, the present application provides a data transmission apparatus, configured to execute the data transmission method in the first aspect or any possible implementation manner of the first aspect.
In a sixth aspect, the present application provides a data transmission apparatus, configured to execute the data transmission method in the second aspect or any possible implementation manner of the second aspect.
In a seventh aspect, the present application provides a data transmission apparatus, configured to execute the data transmission method in the third aspect or any possible implementation manner of the third aspect.
In an eighth aspect, the present application provides a data transmission apparatus, configured to execute the data transmission method in the fourth aspect or any possible implementation manner of the fourth aspect.
In a ninth aspect, the present application provides a data transmission apparatus, comprising: memory, processor, transceiver and computer program stored on the memory and executable on the processor, characterized in that the processor executes the computer program to perform the data transmission method of the first aspect or any possible implementation manner of the first aspect.
Optionally, the processor and the memory included in the apparatus may also be implemented by a chip.
In a tenth aspect, the present application provides a data transmission apparatus, comprising: memory, processor, transceiver and computer program stored on the memory and executable on the processor, characterized in that the processor executes the computer program to perform the data transmission method of the second aspect or any possible implementation manner of the second aspect.
Optionally, the processor and the memory included in the apparatus may also be implemented by a chip.
In an eleventh aspect, the present application provides a data transmission apparatus comprising: memory, processor, transceiver and computer program stored on the memory and executable on the processor, characterized in that the processor executes the computer program to perform the data transmission method of the third aspect or any possible implementation manner of the third aspect.
Optionally, the processor and the memory included in the apparatus may also be implemented by a chip.
In a twelfth aspect, the present application provides a data transmission apparatus, including: memory, processor, transceiver and computer program stored on the memory and executable on the processor, characterized in that the processor executes the computer program to perform the data transmission method of the fourth aspect or any possible implementation manner of the fourth aspect.
Optionally, the processor and the memory included in the apparatus may also be implemented by a chip.
In a thirteenth aspect, the present application provides a computer-readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation manner of the first aspect.
In a fourteenth aspect, the present application provides a computer readable medium for storing a computer program comprising instructions for performing the method of the second aspect or any possible implementation of the second aspect.
In a fifteenth aspect, the present application provides a computer readable medium for storing a computer program comprising instructions for carrying out the method of the third aspect or any possible implementation form of the third aspect.
In a sixteenth aspect, the present application provides a computer readable medium for storing a computer program comprising instructions for performing the method of the fourth aspect or any possible implementation manner of the fourth aspect.
In a seventeenth aspect, the present application provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the method of the first aspect or any possible implementation manner of the first aspect.
Eighteenth, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the second aspect described above or any possible implementation of the second aspect.
In a nineteenth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the third aspect or any possible implementation of the third aspect.
Twentieth aspect provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the fourth aspect or any possible implementation of the fourth aspect.
Drawings
Fig. 1 is a schematic architecture diagram of a communication system provided by an embodiment of the present application;
fig. 2 is a schematic flow chart of a data transmission method provided by an embodiment of the present application;
fig. 3 is a schematic flow chart of another data transmission method provided by an embodiment of the present application;
fig. 4 is a schematic flow chart of still another data transmission method provided in the embodiments of the present application;
fig. 5 is a schematic flow chart of another data transmission method provided by an embodiment of the present application;
fig. 6 is a schematic block diagram of a data transmission apparatus provided in an embodiment of the present application;
fig. 7 is a schematic block diagram of another data transmission apparatus provided in an embodiment of the present application;
FIG. 8 is a schematic block diagram of yet another data transmission apparatus provided by an embodiment of the present application;
fig. 9 is a schematic block diagram of another data transmission apparatus provided in an embodiment of the present application;
fig. 10 is a schematic block diagram of another data transmission apparatus provided in an embodiment of the present application;
fig. 11 is a schematic block diagram of another data transmission apparatus provided in an embodiment of the present application;
fig. 12 is a schematic block diagram of another data transmission apparatus provided in an embodiment of the present application;
fig. 13 is a schematic block diagram of another data transmission apparatus provided in the embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
Fig. 1 shows a schematic architecture diagram of a communication system 100 provided by an embodiment of the present application. As shown in fig. 1, the communication system 100 may include at least one sending device (sending device 110 is shown in fig. 1) and at least one receiving device (receiving device 120 is shown in fig. 1), and data transmission is possible between the at least one sending device and the at least one receiving device.
Optionally, the communication system 100 provided in the embodiment of the present application may be used in a scenario of uplink data transmission, and may also be used in a scenario of downlink data transmission.
In the context of uplink data transmission, the sending-end device 110 may be a terminal device, and the receiving-end device 120 may be a network device; in a scenario of downlink data transmission, the sending end device may be a network device, and the receiving end device may be a terminal device, which is not limited in this application embodiment.
Alternatively, the network device may provide communication coverage for a particular geographic area and may communicate with UEs located within that coverage area. The network device may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a base station (nodeB, NB) in a WCDMA system, an evolved node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN). The network device may also be a core network, a relay station, an access point, a vehicle-mounted device, a wearable device, a network-side device in a future 5G network, or a network device in a Public Land Mobile Network (PLMN) for future evolution, and the like.
Alternatively, the terminal device may be mobile or stationary. The terminal equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device, etc. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved PLMN, etc.
Fig. 1 exemplarily shows one network device and one terminal device, and optionally, the communication system 100 may further include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application. Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited thereto in the embodiments of the present application.
Fig. 2 shows a schematic flow chart of a data transmission method 200 provided in an embodiment of the present application. The data transmission method 200 may be applied to the communication system 100 as shown in fig. 1.
S210, the sending end equipment sends the coded data segment corresponding to the first RV of the data block to the receiving end equipment; accordingly, the receiving end device receives the encoded data segment corresponding to the first RV sent by the sending end device.
It should be understood that the data transmission method 200 can be used in the uplink data transmission scenario as well as the downlink data transmission scenario. In the context of uplink data transmission, the sending end device may be a terminal device, and the receiving end device may be a network device; in a scenario of downlink data transmission, the sending end device may be a network device, and the receiving end device may be a terminal device, which is not limited in this application embodiment.
Optionally, in S210, the sending end device sends, to the receiving end device, the encoded data segment corresponding to the first RV of the data block, which may be: the sending end device sends the indication information of the first RV and the first encoded data segment to the receiving end device, where the indication information of the first RV is used to indicate that the first encoded data segment is the encoded data segment corresponding to the first RV.
As an optional embodiment, in a scenario of downlink data transmission, the network device may send the indication information of the first RV to the terminal device through a downlink control channel, and send the first coded bit segment to the terminal device through a downlink data channel, which is not limited in this embodiment of the present application.
Optionally, the sending end device sends the encoded data segment corresponding to the first RV to the receiving end device, which may be to transmit the data block to the receiving end device for the first time, or may be to retransmit the data block to the receiving end device for the sending end device, and this is not limited in this embodiment of the application.
It should be understood that, before S210, the sending end device may perform encoding and rate matching on the data block to obtain an encoded data block, and write the encoded data block into a circular buffer, where the encoded data block written into the circular buffer is divided into a plurality of encoded data segments corresponding to RVs, and the sending end device selects an encoded data segment corresponding to a certain RV each time to transmit.
Optionally, the indication information of different RVs of the data block may be, for example, a serial number of the RV in a preset RV sequence, a value of the RV, a number of the RV, an identifier of the RV, and the like, which are capable of uniquely indicating the RV, and this is not limited in this embodiment of the present application.
It should also be understood that the sending end device and the receiving end device may pre-agree on a sending sequence (also referred to as an RV sequence) of the RVs and a sequence number (also referred to as a number, a value, etc.) of each RV in the RVs, for example, the sending end device may agree on a protocol, or the sending end device indicates the receiving end device through a notification message before transmitting the data block, which is not limited in this application.
For example, a coded data block 1 in the circular buffer is divided into coded data segments corresponding to 4 RVs, values of the 4 RVs are RV0, RV1, RV2, and RV3, and a predetermined RV sequence of the transmitting end device and the receiving end device is as follows: RV0-RV2-RV3-RV1, when the transmitting end device transmits the data block, the encoded data segment corresponding to RV0, the encoded data segment corresponding to RV2, the encoded data segment corresponding to RV3, and the encoded data segment corresponding to RV1 are sequentially transmitted according to the RV sequence.
Optionally, the number of the RVs in this application embodiment may be, for example, 4, 8, 16, 32 or other values, which is not limited in this application embodiment.
Optionally, the sending end device and the receiving end device may pre-agree on a starting position of the encoded data segment corresponding to each RV of the data block in the circular buffer, for example, the starting position may be agreed by a protocol, or the sending end device indicates the receiving end device through a notification message before transmitting the data block, which is not limited in this embodiment of the present application.
Optionally, the coded data segment corresponding to each RV of the plurality of RVs may include some or all bits of the data block.
Optionally, in the multiple RVs, the coded data segments corresponding to different RVs may not overlap, or the coded data segments corresponding to different RVs may partially overlap, or the coded data segment corresponding to a previous RV and the coded data segment corresponding to a next RV in any two consecutive RVs are consecutive, which is not limited in this embodiment of the present application.
Optionally, assume that the number of RVs of the data block is 2nThe receiving end device may indicate the 2 by n bits, or may indicate the 2 in a differential coding mannernAny one of the RVs, or the 2 can be indicated by other meansnAny one of the RVs, n is an integer greater than 0, which is not limited in the embodiments of the present application.
S220, the receiving end device decodes according to the encoded data segment corresponding to the first RV.
S230, when the decoding fails, the receiving end device sends a request message to the sending end device, where the request message is used to request a coded data segment corresponding to a second RV; accordingly, the sending end device receives the request message sent by the receiving end device.
Optionally, the request message may carry indication information of the second RV.
Optionally, before S230, the receiving end device may determine the second RV according to the RV of the received encoded data segment and a preconfigured RV sequence.
In the data transmission method provided by the embodiment of the present application, when a receiving end device fails to decode a coded data segment corresponding to a received first RV, a request message is actively sent to a sending end device to request a coded data segment corresponding to a second RV, and the receiving end device is in the transmitting end device
After receiving the coded data segment corresponding to the second RV sent by the sending end device according to the request message, the decoding can be performed according to the coded data segments corresponding to all the received RVs, which is beneficial to improving the decoding success rate and the decoding flexibility of the receiving end device.
In addition, the receiving end equipment carries out incremental redundancy or combined decoding according to the coded data segment corresponding to the second RV and the coded data segment corresponding to the other RVs which are already received, so that the decoding success rate can be improved, and the reliability of data transmission is improved.
As an alternative embodiment, the receiving end device may determine, according to the RV of the received encoded data segment and the RV sequence, that there is at least one RV that has not been received before receiving the first RV; the receiving end device determines the most forward RV in the RV sequence in the at least one RV as the second RV.
For example, assuming that the RV sequence of the data block is RV0-RV2-RV3-RV1, the receiving end device receives the encoded data segment corresponding to RV3 sent by the sending end device, decodes the encoded data segment according to RV3, and when the receiving end device fails to decode the encoded data segment corresponding to RV3, the receiving end device has received RV0 and RV3, that is, there is an unreceived RV2, and then the receiving end device sends a request message to the sending end device, where the request message is used to request the encoded data segment corresponding to RV 2. That is, the receiving end device has received RV0, RV2, and RV3 after receiving RV 2.
For another example, assuming that the RV sequence of the data block is RV1-RV2-RV3-RV4-RV5-RV6-RV7, a receiving end device receives a coded data segment corresponding to RV5 sent by a sending end device, decodes the coded data segment according to RV5, and when the receiving end device fails to decode the coded data segment according to the received RV5, the receiving end device has received RV1, RV4 and RV5, that is, there are RV2 and RV3 which are not received, and RV2 is located before RV3 in the RV sequence, the receiving end device sends a request message to the sending end device, where the request message is used to request the coded data segment corresponding to RV 2. That is, the receiving-end device has received RV1, RV2, RV4, and RV5 after receiving RV 2.
It should be understood that, in the LTE communication system, when the receiving end device fails to decode the encoded data segment corresponding to the mth RV, the sending end device sends the encoded data segment corresponding to the m +1 th RV, and the receiving end device decodes the encoded data segment according to the m +1 th RV, that is, the receiving end device lacks the encoded data segment corresponding to the mth RV during decoding, where m is an integer greater than 0.
In the data transmission method provided in the embodiment of the present application, in a communication system in which a data channel adopts LDPC coding, a receiving end device uses a first RV that is not received before a first RV in a RV sequence as a second RV, and requests a transmitting end device for an encoded data segment corresponding to the second RV, so that the encoded data segment corresponding to the second RV and the encoded data segment corresponding to the RV before the first RV can be continuous as much as possible, thereby improving a decoding success rate of the receiving end device and reliability of data transmission.
As another alternative, the receiving end device may determine, according to the RV of the received encoded data segment and the RV sequence, that there is no RV that is not received before receiving the first RV; the receiving end device determines the next RV of the first RV in the RV sequence as the second RV.
For example, assuming that the RV sequence of the data block is RV0-RV2-RV3-RV1, the receiving end device receives the encoded data segment corresponding to RV3 sent by the sending end device, decodes the encoded data segment according to RV3, and when the receiving end device fails to decode the encoded data segment corresponding to RV3, the receiving end device has received all RVs before RV3, that is, has received RV0, RV2 and RV3, and then the receiving end device sends a request message to the sending end device, where the request message is used to request the next RV of RV3, that is, the encoded data segment corresponding to RV 1. That is, the receiving end device has received RV0, RV2, RV3, and RV1 after receiving RV 1.
In the data transmission method provided in the embodiment of the present application, after receiving end equipment has received all RVs before the first RV in the RV sequence, a subsequent RV of the second RV is used as a second RV, and a coding data segment corresponding to the second RV is requested from sending end equipment, so that the coding data segment corresponding to the second RV and the coding data segment corresponding to the first RV are continuous as much as possible, thereby improving the decoding success rate of the receiving end equipment and the reliability of data transmission.
S240, the sending end device sends the encoded data segment corresponding to the second RV to the receiving end device according to the request message; accordingly, the receiving end device receives the encoded data segment corresponding to the second RV sent by the sending end device.
Optionally, after S240, if the receiving end device receives the encoded data segment corresponding to the second RV sent by the sending end device according to the request message, the receiving end device decodes according to the encoded data segment corresponding to the second RV.
Optionally, the decoding, by the receiving end device, according to the encoded data segment corresponding to the second RV may be: the receiving end device performs incremental redundancy or merging decoding on the encoded data segment corresponding to the second RV and the received encoded data segment corresponding to the other RVs, which is not limited in this embodiment of the application.
Optionally, the received coded data segment corresponding to the other RVs may be a coded data segment corresponding to each RV in at least one RV, where the at least one RV may be a part of or all of the received RVs, which is not limited in this embodiment of the present application.
Optionally, if the receiving end device successfully decodes the encoded data segment corresponding to the second RV, the sending end device sends a second feedback message, where the second feedback message is used to feed back that the data block is successfully received; correspondingly, the sending end device receives the second feedback message sent by the receiving end device, and sends other data blocks to the receiving end device according to the second feedback message.
Fig. 3 shows a schematic flow chart of a data transmission method 300 provided in the embodiment of the present application, and the data transmission method 300 can be applied to the communication system 100 shown in fig. 1.
S310, the sending end device sends the encoded data segment corresponding to the first RV of the data block to the receiving end device.
It should be understood that the data transmission method 300 can be used in the uplink data transmission scenario as well as the downlink data transmission scenario. In the context of uplink data transmission, the sending end device may be a terminal device, and the receiving end device may be a network device; in a scenario of downlink data transmission, the sending end device may be a network device, and the receiving end device may be a terminal device, which is not limited in this application embodiment.
It should also be understood that S310 in fig. 3 is similar to S210 in fig. 2, and therefore S310 may be implemented with reference to the S210 implementation, and is not described herein again to avoid redundancy.
S320, when the receiving end device does not receive the encoded data segment corresponding to the first RV sent by the sending end device, the receiving end device sends a feedback message to the sending end device, where the feedback message is used to feed back the encoded data segment corresponding to the first RV that is not received; accordingly, the sending end device receives the feedback message sent by the receiving end device.
S330, the sending end device resends the encoded data segment corresponding to the first RV to the receiving end device; correspondingly, the receiving end device receives the encoded data segment corresponding to the first RV, which is retransmitted by the sending end device according to the feedback message.
For example, assuming that the RV sequence of the data block is RV0-RV2-RV3-RV1, the receiving end device has received the encoded data segment corresponding to RV0 and the encoded data segment corresponding to RV2, if the receiving end device does not receive the encoded data segment corresponding to RV3 sent by the sending end device, the receiving end device sends a feedback message to the sending end device, where the feedback message is used to feed back that the encoded data segment corresponding to RV3 is not received, and the sending end device retransmits the encoded data segment corresponding to RV3 to the receiving end device according to the feedback message. That is, after receiving RV3 sent by the sending end device according to the feedback message, the receiving end device receives the encoded data segment corresponding to RV0, the encoded data segment corresponding to RV2, and the encoded data segment corresponding to RV 3.
Optionally, in a scenario of downlink data transmission, the sending end device sends, to the receiving end device, the encoded data segment corresponding to the first RV, where the encoded data segment may be: the sending end device sends the indication information of the first RV through a downlink control channel and sends a first coded data segment through a downlink data channel, wherein the indication information of the first RV is used for indicating that the first coded data segment is a coded data segment corresponding to the first RV.
Optionally, in a scenario of downlink data transmission, the receiving end does not receive the encoded data segment corresponding to the first RV sent by the sending end device, and the receiving end may: the receiving end does not receive the indication information of the first RV in the downlink control channel, which is not limited in this embodiment of the present application.
Optionally, after S330, if the receiving end device receives the encoded data segment corresponding to the first RV sent by the sending end device according to the request message, the receiving end device decodes according to the encoded data segment corresponding to the first RV.
Optionally, the decoding, by the receiving end device, according to the encoded data segment corresponding to the first RV may be: the receiving end device performs incremental redundancy or merging decoding on the encoded data segment corresponding to the first RV and the received encoded data segment corresponding to the other RVs, which is not limited in this embodiment of the present application.
Optionally, the received coded data segment corresponding to the other RVs may be a coded data segment corresponding to each RV in at least one RV, where the at least one RV may be a part of or all of the received RVs, which is not limited in this embodiment of the present application.
Optionally, if the receiving end device succeeds in decoding according to the encoded data segment corresponding to the first RV, the sending end device sends a feedback message, where the feedback message is used to feed back that the data block is successfully received; correspondingly, the sending end device receives the feedback message sent by the receiving end device, and sends other data blocks to the receiving end device according to the feedback message.
It should be understood that, in the LTE communication system, when the receiving end device does not receive the encoded data segment corresponding to the mth RV sent by the sending end device, the sending end device sends the encoded data segment corresponding to the m +1 th RV, and the receiving end device decodes according to the m +1 th RV, that is, the receiving end device lacks the encoded data segment corresponding to the mth RV when decoding, where m is an integer greater than 0.
In the data transmission method provided in the embodiment of the present application, in a communication system in which an LDPC coding is used in a data channel, when a sending end device receives a coded data segment corresponding to a first RV, which is not received by a receiving end device in feedback, the sending end device retransmits the coded data segment corresponding to the first RV, so that the coded data segment received by the receiving end device is as continuous as possible, thereby improving a decoding success rate of the receiving end device and reliability of transmission data.
Fig. 4 shows a schematic flow chart of a data transmission method 400 provided in this embodiment, where the data transmission method 400 may be applied to the communication system 100 shown in fig. 1, but this is not limited in this embodiment.
It is assumed that a sending end device obtains a coded data block after coding and rate matching a data block to be sent, and stores the coded data block into a cyclic buffer, wherein the coded data block stored into the cyclic buffer is divided into 4 coded data segments corresponding to RVs, 4 RVs are RV1, RV2, RV3 and RV4, and RV sequences preconfigured by the sending end device and a receiving end device are RV1-RV2-RV3-RV 4.
S401, the sending end equipment sends the coded data segment corresponding to RV1 of the data block to the receiving end equipment; accordingly, the receiving end device receives the encoded data segment corresponding to the RV1 sent by the network device.
That is, the receiving end device receives the encoded data segment corresponding to RV 1.
S402, the receiving end device decodes according to the encoded data segment corresponding to RV 1.
S403, when the receiving end device fails to decode the encoded data segment corresponding to RV1, the receiving end device sends a first request message carrying indication information of RV2 to the sending end device according to the received encoded data segment corresponding to RV1 and the RV sequence, where the first request message is used to request the sending end device to send the encoded data segment corresponding to RV 2; accordingly, the sending end device receives the first request message sent by the receiving end device.
S404, the sending end device sends the encoded data segment corresponding to RV2 to the receiving end device according to the first request message.
It should be understood that S401 in fig. 4 is similar to S210 in fig. 2, S402 in fig. 4 is similar to S220 in fig. 2, S403 in fig. 4 is similar to S230 in fig. 2, and S404 in fig. 4 is similar to S240 in fig. 2, and therefore, S401 to S404 may refer to the implementation of S210 to S240, and are not repeated here to avoid repetition.
S405, when the receiving end device does not receive the encoded data segment corresponding to RV2, the receiving end device feeds back Discontinuous Transmission (DTX) to the sending end device, where the DTX is used to feed back that the receiving end device does not receive the encoded data segment corresponding to RV 2; accordingly, the transmitting end device receives the DTX transmitted by the receiving end device.
S406, the sending end device sends the encoded data segment corresponding to the next RV of RV2, that is, RV3, to the receiving end device; accordingly, the receiving end device receives the encoded data segment corresponding to RV3 sent by the sending end device.
That is, the receiving end device receives the encoded data segment corresponding to RV 3.
S407, the receiving end device decodes according to the encoded data segment corresponding to RV 3.
S408, when the receiving end device fails to decode the encoded data segment corresponding to RV3, the receiving end device determines that the encoded data segment corresponding to RV2 has not been received before RV3 according to the received encoded data segment corresponding to RV1, the encoded data segment corresponding to RV3, and the RV sequence, and sends a second request message carrying indication information of RV2 to the sending end device, where the second request message is used to request the sending end device to retransmit the encoded data segment corresponding to RV 2; accordingly, the sending end device receives the second request message sent by the receiving end device.
S409, the sending end device retransmits the encoded data segment corresponding to RV2 to the receiving end device according to the second request message; accordingly, the receiving end device receives the encoded data segment corresponding to RV2 sent by the sending end device.
That is, the receiving end device has received the coded data segment corresponding to RV1, the coded data segment corresponding to RV2, and the coded data segment corresponding to RV 3.
It should be understood that S406 in fig. 4 is similar to S210 in fig. 2, S407 in fig. 4 is similar to S220 in fig. 2, S408 in fig. 4 is similar to S230 in fig. 2, and S409 in fig. 4 is similar to S240 in fig. 2, and therefore, S406 to S409 may be implemented by referring to the embodiments of S210 to S240, and are not repeated here to avoid repetition.
S410, the receiving end device successfully decodes the encoded data segment according to the RV 2.
Optionally, the decoding success of the receiving end device according to the encoded data segment corresponding to the RV2 may be: and the receiving end equipment successfully decodes according to the coded data segment corresponding to the RV2 and the coded data segments corresponding to the received other RVs. Wherein, the other RVs received can be RV1 and/or RV 2.
S411, the receiving end device feeds back an Acknowledgement Character (ACK) to the sending end device, where the ACK is used to feed back that the data block is successfully received; accordingly, the sending end device receives the ACK sent by the receiving end device.
Optionally, after S411, the sending end device may send other data blocks to the receiving end device according to the ACK.
Fig. 5 shows a schematic flow chart of another data transmission method 500 provided by the embodiment of the present application, and the data transmission method 500 can be applied to the communication system 100 shown in fig. 1.
Suppose that a sending end device performs coding and rate matching on a data block to be sent to obtain a coded data block, and writes the coded data block into a cyclic buffer, where the coded data block written into the cyclic buffer is divided into 4 coded data segments corresponding to RVs, 4 RVs are RV1, RV2, RV3 and RV4, respectively, and RV sequences preconfigured by the sending end device and a receiving end device are RV1-RV2-RV3-RV 4.
It should be understood that, in the embodiment of the present application, only 4 RVs are taken as an example for description, after the data block stores the encoded data block in the circular buffer, the encoded data block may also be divided into other encoded data segments corresponding to other numbers of RVs, which is not limited in this embodiment of the present application.
It should be further understood that, in the embodiment of the present application, only the RV sequence is described as RV1-RV2-RV3-RV4, and multiple RVs of the data block may also be transmitted according to other RV sequences, which is not limited in this embodiment of the present application.
Optionally, the coded data segment corresponding to each of the 4 RVs may include some or all of the bits of the data block.
Optionally, in the 4 RVs, the coded data segments corresponding to different RVs may not overlap, or the coded data segments corresponding to different RVs may partially overlap, or the coded data segment corresponding to a previous RV in any two consecutive RVs is consecutive to the coded data segment corresponding to a next RV, which is not limited in this embodiment of the present application.
S501, sending the coded data segment corresponding to RV1 of the data block to receiving end equipment by the sending end equipment; accordingly, the receiving end device receives the encoded data segment corresponding to the RV1 sent by the network device.
S502, the receiving end device decodes according to the encoded data segment corresponding to RV 1.
S503, when the receiving end device fails to decode the encoded data segment corresponding to the RV1, the receiving end device feeds back a first Negative Acknowledgement (NACK) to the sending end device, where the first NACK is used to feed back the decoding failure; accordingly, the transmitting end device receives the NACK transmitted by the receiving end device.
S504, the transmitting end device sends, according to the first NACK, a coded data segment corresponding to a next RV of the RV1, that is, RV2, to the receiving end device.
S505, when the receiving end device does not receive the encoded data segment corresponding to RV2, the receiving end device feeds back DTX to the sending end device; accordingly, the transmitting end device receives the DTX transmitted by the transmitting end device.
S506, the sending end device retransmits the encoded data segment corresponding to RV2 to the receiving end device; accordingly, the receiving end device receives the encoded data segment corresponding to RV2 sent by the sending end device.
It should be understood that S504 in fig. 5 is similar to S310 in fig. 3, S505 in fig. 5 is similar to S320 in fig. 3, and S506 in fig. 5 is similar to S330 in fig. 3, and therefore, S504 to S506 may be implemented with reference to the implementation of S310 to S330, and are not repeated herein to avoid repetition.
S507, the receiving end device decodes according to the encoded data segment corresponding to the RV 2.
S508, when the receiving end device fails to decode the encoded data segment corresponding to the RV2, the receiving end device feeds back a second NACK to the sending end device, where the second NACK is used to feed back the decoding failure; accordingly, the number of the first and second electrodes,
and the sending end equipment receives the second NACK sent by the receiving end equipment.
S509, the sending end device sends, according to the second NACK, a coded data segment corresponding to a next RV of the RV2, that is, RV3, to the receiving end device; accordingly, the receiving end device receives the encoded data segment corresponding to RV 3.
S510, the receiving end device successfully decodes the encoded data segment according to the RV 3.
S511, the receiving end device feeds back ACK to the sending end device, where the ACK is used to feed back that the data block is successfully received; accordingly, the sending end device receives the ACK sent by the receiving end device.
Optionally, after S511, the sending end device may send other data blocks to the receiving end device according to the ACK.
The data transmission method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to 5, and the data transmission device provided by the embodiment of the present application is described below with reference to fig. 6 to 13.
Fig. 6 shows a schematic block diagram of a data transmission apparatus 600 provided in an embodiment of the present application. The data transmission device 600 includes:
a receiving unit 610, configured to receive an encoded data block corresponding to a first redundancy version RV of a data block sent by a sending end device;
a decoding unit 620, configured to decode according to the encoded data segment corresponding to the first RV received by the receiving unit 610;
a sending unit 630, configured to send a request message to the sending end device when the decoding fails, where the request message is used to request a coded data segment corresponding to the second RV;
the receiving unit 610 is further configured to receive the encoded data segment corresponding to the second RV, where the encoded data segment is sent by the sending end device according to the request message sent by the sending unit 630.
Optionally, the data transmission apparatus further includes: and the processing unit is used for determining the second RV according to the RV of the received coded data segment and a pre-configured RV sequence before sending the request message to the sending terminal equipment.
Optionally, the processing unit is specifically configured to: determining, from the RV of the received encoded data segment and the RV sequence, that there is at least one RV that was not received before the first RV was received; and determining the most previous RV in the RV sequence in the at least one RV as the second RV.
Optionally, the processing unit is specifically configured to: determining, from the RV of the received encoded data segment and the RV sequence, that there is no RV that was not received before the first RV was received; and determining the next RV of the first RV in the RV sequence as the second RV.
In an optional example, as can be understood by those skilled in the art, the data transmission apparatus 600 may be specifically a receiving end device in the foregoing method embodiment, and the data processing apparatus 600 may be configured to execute each procedure and/or step corresponding to the receiving end device in the foregoing method embodiment, which is not described herein again to avoid repetition.
It should be understood that the data transmission device 600 herein may be embodied in the form of a functional unit. The term "unit" herein may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality.
Fig. 7 provides a schematic block diagram of a data transmission apparatus 700 provided in an embodiment of the present application. The data transmission device 700 includes:
a sending unit 710, configured to send, to a receiving end device, an encoded data segment corresponding to a first redundancy version RV of a data block;
a receiving unit 720, configured to receive a request message sent by the receiving end device, where the request message is used to request a coded data segment corresponding to a second RV when the receiving end device fails to decode the coded data segment corresponding to the first RV;
the sending unit 710 is further configured to send the encoded data segment corresponding to the second RV to the receiving end device according to the request message received by the receiving unit 720.
Optionally, the second RV is determined according to the RV of the encoded data segment that has been received by the receiving end device and a preconfigured RV sequence.
Optionally, the second RV is a first RV, which is not received by the receiving end device before the first RV in the RV sequence.
Optionally, the second RV is a next RV of the first RV in the RV sequence, where the receiving end device has received all RVs before the first RV in the RV sequence.
In an optional example, it may be understood by those skilled in the art that the data transmission apparatus 700 may be specifically a sending end device in the foregoing method embodiment, and the data transmission apparatus 700 may be configured to execute each procedure and/or step corresponding to the sending end device in the foregoing method embodiment, and details are not described here again to avoid repetition.
It should be understood that the data transmission device 700 herein may be embodied in the form of a functional unit. The term "unit" herein may refer to an ASIC, an electronic circuit, a processor (e.g., a shared, dedicated, or group processor) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality.
Fig. 8 provides a schematic block diagram of a data transmission apparatus 800 provided in an embodiment of the present application. The data transmission apparatus 800 includes:
a sending unit 810, configured to send, to a receiving end device, an encoded data segment corresponding to a first redundancy version RV of a data block;
a receiving unit 820, configured to receive a feedback message sent by the receiving end device, where the feedback message is used to feed back an encoded data segment corresponding to the first RV, where the encoded data segment is not received;
the transmitting unit 810 is further configured to retransmit the encoded data segment corresponding to the first RV to the receiving end device.
In an optional example, as can be understood by those skilled in the art, the data transmission apparatus 800 may be specifically a sending end device in the foregoing method embodiment, and the data transmission apparatus 800 may be configured to execute each procedure and/or step corresponding to the sending end device in the foregoing method embodiment, and for avoiding repetition, details are not described here again.
It should be understood that the data transmission device 800 herein may be embodied in the form of a functional unit. The term "unit" herein may refer to an ASIC, an electronic circuit, a processor (e.g., a shared, dedicated, or group processor) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality.
Fig. 9 provides a schematic block diagram of a data transmission apparatus 900 provided in an embodiment of the present application. The data transmission apparatus 900 includes:
a sending unit 910, configured to send a feedback message to a sending end device when a coded data segment corresponding to a first redundancy version, RV, of a data block sent by the sending end device is not received, where the feedback message is used to feed back the coded data segment corresponding to the first RV which is not received;
a receiving unit 920, configured to receive the encoded data segment corresponding to the first RV, which is retransmitted by the sending end device according to the feedback message sent by the sending unit 910.
In an optional example, as can be understood by those skilled in the art, the data transmission apparatus 900 may be specifically a receiving end device in the foregoing method embodiment, and the data transmission apparatus 900 may be configured to execute each procedure and/or step corresponding to the receiving end device in the foregoing method embodiment, and for avoiding repetition, details are not described here again.
It should be appreciated that the data transmission apparatus 900 herein may be embodied in the form of a functional unit. The term "unit" herein may refer to an ASIC, an electronic circuit, a processor (e.g., a shared, dedicated, or group processor) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality.
Fig. 10 provides a schematic block diagram of a data transmission apparatus 1000 provided in an embodiment of the present application. The data transmission device 1000 includes a processor 1010, a transceiver 1020, and a memory 1030. Wherein the processor 1010, the transceiver 1020 and the memory 1030 are in communication with each other via an internal connection path, the memory 1030 is configured to store instructions, and the processor 1010 is configured to execute the instructions stored in the memory 1030 to control the transceiver 1020 to transmit and/or receive signals.
Optionally, the processor and the memory included in the data transmission device may also be implemented by a chip.
The processor 1010 is specifically configured to: controlling the transceiver 1020 to receive the encoded data block corresponding to the first redundancy version RV of the data block sent by the sending end device; decoding according to the coded data segment corresponding to the first RV; when the decoding fails, controlling the transceiver 1020 to send a request message to the sending-end device, where the request message is used to request a coded data segment corresponding to a second RV; controlling the transceiver 1020 to receive the encoded data segment corresponding to the second RV, which is sent by the sending-end device according to the request message.
It should be understood that the data transmission apparatus 1000 may be embodied as the receiving end device in the foregoing embodiments, and may be configured to perform each step and/or flow corresponding to the receiving end device in the foregoing method. Optionally, the memory 1020 may include both read-only memory and random access memory, and provides instructions and data to the processor. The portion of memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1010 may be configured to execute instructions stored in the memory, and when the processor 1010 executes the instructions stored in the memory, the processor 1010 is configured to execute the steps and/or processes corresponding to the receiving end device in the above embodiments.
It should be understood that, in the embodiment of the present application, the processor of the data transmission apparatus may be a Central Processing Unit (CPU), and the processor may also be other general processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Fig. 11 shows a schematic block diagram of a data transmission apparatus 1100 provided in an embodiment of the present application. The data transmission device 1100 includes a processor 1110, a transceiver 1120, and a memory 1130. The processor 1110, the transceiver 1120 and the memory 1130 are in communication with each other through an internal connection path, the memory 1130 is used for storing instructions, and the processor 1110 is used for executing the instructions stored in the memory 1130 to control the transceiver 1120 to transmit and/or receive signals.
Optionally, the processor and the memory included in the data transmission device may also be implemented by a chip.
Processor 1110 is specifically configured to: controlling the transceiver 1120 to transmit the encoded data segment corresponding to the first redundancy version RV of the data block to the receiving end device; controlling the transceiver 1120 to receive a request message sent by the receiving end device, where the request message is used to request a coded data segment corresponding to a second RV when the receiving end device fails to decode according to the coded data segment corresponding to the first RV; controlling the transceiver 1120 to transmit the encoded data segment corresponding to the second RV to the receiving end device according to the request message received by the receiving unit.
It should be understood that the data transmission apparatus 1100 may be embodied as the sending end device in the foregoing embodiment, and may be configured to execute each step and/or flow corresponding to the sending end device in the foregoing method. Alternatively, the memory 1130 may include both read-only memory and random access memory, and provides instructions and data to the processor. The portion of memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1110 may be configured to execute instructions stored in the memory, and when the processor 1110 executes the instructions stored in the memory, the processor 1110 is configured to execute various steps and/or procedures corresponding to the sending end device in the above-described embodiments.
It should be understood that in embodiments of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Fig. 12 provides a schematic block diagram of a data transmission apparatus 1200 provided in an embodiment of the present application. The data transmission apparatus 1200 includes a processor 1210, a transceiver 1220, and a memory 1230. The processor 1210, the transceiver 1220 and the memory 1230 are in communication with each other through an internal connection path, the memory 1230 is used for storing instructions, and the processor 1210 is used for executing the instructions stored in the memory 1230 to control the transceiver 1220 to transmit and/or receive signals.
Optionally, the processor and the memory included in the data transmission device may also be implemented by a chip.
The processor 1210 is specifically configured to: controlling the transceiver 1220 to send the encoded data segment corresponding to the first redundancy version RV of the data block to the receiving end device; controlling the transceiver 1220 to receive a feedback message sent by the receiving end device, where the feedback message is used to feed back an encoded data segment corresponding to the first RV, where the encoded data segment is not received; the transceiver 1220 is controlled to retransmit the encoded data segment corresponding to the first RV to the receiving device.
It should be understood that the data transmission apparatus 1200 may be embodied as the sending end device in the foregoing embodiment, and may be configured to execute each step and/or flow corresponding to the sending end device in the foregoing method. Alternatively, the memory 1220 may include a read-only memory and a random access memory, and provide instructions and data to the processor. The portion of memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1210 may be configured to execute instructions stored in the memory, and when the processor 1210 executes the instructions stored in the memory, the processor 1210 is configured to perform various steps and/or procedures corresponding to the sending end device in the above embodiments.
It should be understood that in the embodiments of the present application, the processor of the data transmission device may be a Central Processing Unit (CPU), and the processor may also be other general processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Fig. 13 shows a schematic block diagram of a data transmission apparatus 1300 provided in an embodiment of the present application. The data transmission apparatus 1300 includes a processor 1310, a transceiver 1320, and a memory 1330. Wherein the processor 1310, the transceiver 1320, and the memory 1330 are in communication with each other through the interconnection, the memory 1330 is configured to store instructions, and the processor 1310 is configured to execute the instructions stored in the memory 1330 to control the transceiver 1320 to transmit and/or receive signals.
Optionally, the processor and the memory included in the data transmission device may also be implemented by a chip.
The processor 1310 is specifically configured to: when the coded data segment corresponding to the first redundancy version RV of the data block sent by the sending end device is not received, controlling the transceiver 1320 to send a feedback message to the sending end device, where the feedback message is used to feed back the coded data segment corresponding to the first RV which is not received; controlling the transceiver 1320 to receive the encoded data segment corresponding to the first RV, which is retransmitted by the sending-end device according to the feedback message.
It should be understood that the data transmission apparatus 1300 may be embodied as the receiving end device in the foregoing embodiments, and may be configured to perform each step and/or flow corresponding to the receiving end device in the foregoing method. Alternatively, the memory 1330 may include a read-only memory and a random access memory, and provide instructions and data to the processor. The portion of memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1310 may be configured to execute instructions stored in the memory, and when the processor 1310 executes the instructions stored in the memory, the processor 1310 is configured to execute the steps and/or processes corresponding to the receiving end device in the above embodiments.
It should be understood that in embodiments of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (12)

1. A method of data transmission, comprising:
receiving end equipment receives a coded data block corresponding to a first Redundancy Version (RV) of a data block sent by sending end equipment;
the receiving end equipment decodes according to the coded data segment corresponding to the first RV;
when the decoding fails, the receiving end equipment determines that at least one RV which is not received exists before the first RV is received according to the RV of the received coded data segment and a pre-configured RV sequence;
the receiving end equipment determines the most front RV in the RV sequence in the at least one RV as a second RV;
the receiving end equipment sends a request message to the sending end equipment, wherein the request message is used for requesting a coded data segment corresponding to a second RV;
and the receiving end equipment receives the coded data segment corresponding to the second RV sent by the sending end equipment according to the request message.
2. The data transmission method according to claim 1, wherein the receiving end device determines, according to the RV of the received encoded data segment and a preconfigured RV sequence, that there is at least one RV that has not been received before receiving the first RV;
the determining, by the receiving end device, a first RV in the RV sequence of the at least one RV as a second RV includes:
the receiving end equipment determines that no RV which is not received exists before the first RV is received according to the RV of the received coded data segment and the RV sequence;
and the receiving terminal equipment determines the next RV of the first RV in the RV sequence as the second RV.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
the sending end equipment receives a feedback message sent by the receiving end equipment, wherein the feedback message is used for feeding back the coded data segment corresponding to the first RV, which is not received;
and the sending end equipment retransmits the coded data segment corresponding to the first RV to the receiving end equipment.
4. A method of data transmission, comprising:
the sending end equipment sends a coded data segment corresponding to a first redundancy version RV of a data block to the receiving end equipment;
when the receiving end device fails to decode the encoded data segment corresponding to the first RV, the sending end device receives a request message sent by the receiving end device, where the request message is used to request an encoded data segment corresponding to a second RV, and the second RV is a most previous RV that is not received by the receiving end device before the first RV in a preconfigured RV sequence;
and the sending end equipment sends the coded data segment corresponding to the second RV to the receiving end equipment according to the request message.
5. The data transmission method according to claim 4, wherein the second RV is a next RV of the first RV in the RV sequence, wherein the receiving end device has received all RVs before the first RV in the RV sequence.
6. The method according to claim 4 or 5, characterized in that the method further comprises:
when receiving end equipment does not receive a coded data segment corresponding to a first Redundancy Version (RV) of a data block sent by sending end equipment, sending feedback information to the sending end equipment by the receiving end equipment, wherein the feedback information is used for feeding back the coded data segment corresponding to the first RV which is not received;
and the receiving end equipment receives the coded data segment corresponding to the first RV retransmitted by the sending end equipment according to the feedback message.
7. A data transmission apparatus, comprising:
a receiving unit, configured to receive an encoded data block corresponding to a first redundancy version RV of a data block sent by a sending end device;
a decoding unit, configured to decode according to the encoded data segment corresponding to the first RV received by the receiving unit;
a processing unit, configured to determine, when the decoding fails, that there is at least one RV that has not been received before receiving the first RV according to the RV of the received encoded data segment and a preconfigured RV sequence;
the processing unit is further configured to determine a most preceding one of the at least one RV in the RV sequence as the second RV;
a sending unit, configured to send a request message to the sending end device, where the request message is used to request an encoded data segment corresponding to a second RV;
the receiving unit is further configured to receive the encoded data segment corresponding to the second RV, where the encoded data segment is sent by the sending end device according to the request message sent by the sending unit.
8. The data transmission apparatus of claim 7,
the processing unit is further configured to determine, according to the RV of the received encoded data segment and the RV sequence, that there is no RV that is not received before the first RV is received; and
and determining the next RV of the first RV in the RV sequence as the second RV.
9. The data transmission apparatus according to claim 7 or 8,
the receiving unit is further configured to receive a feedback message sent by the receiving end device, where the feedback message is used to feed back an encoded data segment corresponding to the first RV, where the encoded data segment is not received;
the sending unit is further configured to resend the encoded data segment corresponding to the first RV to the receiving end device.
10. A data transmission apparatus, comprising:
a sending unit, configured to send, to a receiving end device, a coded data segment corresponding to a first redundancy version RV of a data block;
a receiving unit, configured to receive, when the receiving end device fails to decode the encoded data segment corresponding to the first RV, a request message sent by the receiving end device, where the request message is used to request an encoded data segment corresponding to a second RV, and the second RV is a oldest RV, which is not received by the receiving end device before the first RV in the RV sequence;
the sending unit is further configured to send, to the receiving end device, the encoded data segment corresponding to the second RV according to the request message received by the receiving unit.
11. The data transmission apparatus of claim 10, wherein the second RV is a next RV of the first RV in the RV sequence, and wherein all RVs prior to the first RV in the RV sequence have been received by the receiving end device.
12. A data transmission apparatus according to claim 10 or 11, comprising:
the sending unit is further configured to send a feedback message to the sending end device when the coded data segment corresponding to the first redundancy version RV of the data block sent by the sending end device is not received, where the feedback message is used to feed back the coded data segment corresponding to the first RV which is not received;
the receiving unit is further configured to receive the encoded data segment corresponding to the first RV, which is retransmitted by the sending-end device according to the feedback message.
CN201710431047.7A 2017-06-09 2017-06-09 Data transmission method and data transmission device Active CN109039529B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710431047.7A CN109039529B (en) 2017-06-09 2017-06-09 Data transmission method and data transmission device
PCT/CN2018/089030 WO2018223877A1 (en) 2017-06-09 2018-05-30 Data transmission method and data transmission device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710431047.7A CN109039529B (en) 2017-06-09 2017-06-09 Data transmission method and data transmission device

Publications (2)

Publication Number Publication Date
CN109039529A CN109039529A (en) 2018-12-18
CN109039529B true CN109039529B (en) 2021-01-29

Family

ID=64565751

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710431047.7A Active CN109039529B (en) 2017-06-09 2017-06-09 Data transmission method and data transmission device

Country Status (2)

Country Link
CN (1) CN109039529B (en)
WO (1) WO2018223877A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020132794A1 (en) * 2018-12-24 2020-07-02 Nokia Shanghai Bell Co., Ltd. Method, device and computer readable medium for diversity transmissions
CN111769899B (en) * 2019-03-30 2021-10-01 华为技术有限公司 Method and device for determining transmission resources
CN111600683B (en) * 2019-06-06 2022-02-01 维沃移动通信有限公司 Processing method and device
US11863331B2 (en) * 2019-10-03 2024-01-02 Qualcomm Incorporated Determining priorities for a plurality of transport blocks for transmission

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101843025A (en) * 2007-10-29 2010-09-22 Lg电子株式会社 Method of data transmission using HARQ
CN103312473A (en) * 2012-03-06 2013-09-18 中兴通讯股份有限公司 Method and device for reducing HARQ (Hybrid Automatic Repeat Request) combination failures
CN104838612A (en) * 2012-12-13 2015-08-12 Zte维创通讯公司 Method and apparatus for a modified harq procedure after a receiver outage event
WO2016060598A1 (en) * 2014-10-13 2016-04-21 Telefonaktiebolaget L M Ericsson (Publ) Harq feedback reporting based on mirrored information copied from resource-assignment message

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102045146A (en) * 2009-10-15 2011-05-04 上海华为技术有限公司 Hybrid automatic repeat request merging method, device and system
CN101754274B (en) * 2009-12-29 2012-07-04 华为技术有限公司 Data retransmission method and equipment
CN102255710B (en) * 2011-04-15 2014-01-29 电信科学技术研究院 Method and device for storing encoding block

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101843025A (en) * 2007-10-29 2010-09-22 Lg电子株式会社 Method of data transmission using HARQ
CN103312473A (en) * 2012-03-06 2013-09-18 中兴通讯股份有限公司 Method and device for reducing HARQ (Hybrid Automatic Repeat Request) combination failures
CN104838612A (en) * 2012-12-13 2015-08-12 Zte维创通讯公司 Method and apparatus for a modified harq procedure after a receiver outage event
WO2016060598A1 (en) * 2014-10-13 2016-04-21 Telefonaktiebolaget L M Ericsson (Publ) Harq feedback reporting based on mirrored information copied from resource-assignment message

Also Published As

Publication number Publication date
CN109039529A (en) 2018-12-18
WO2018223877A1 (en) 2018-12-13

Similar Documents

Publication Publication Date Title
US10897774B2 (en) Information processing method and apparatus
US10574401B2 (en) Polar code retransmission method and apparatus
CN109039529B (en) Data transmission method and data transmission device
CN107925990B (en) Method for transmitting feedback information, terminal equipment and base station
CN110392993B (en) Method for transmitting feedback information, terminal equipment, network equipment and storage medium
KR20190028375A (en) Data transfer method and apparatus
KR102323496B1 (en) Communication method, network device and terminal
WO2018152714A1 (en) Method and device for information transmission
CN108809481B (en) Data processing method and data processing device
CN109155706B (en) Data transmission method, data transmission device and communication system
US20210105745A1 (en) Data transmission method, network device and terminal device
US10165595B2 (en) Device and method of handling uplink transmission
CN110121850B (en) Data transmission method, transmitting terminal equipment and receiving terminal equipment
CN111757505B (en) Communication method, terminal device and network device
CN109150380B (en) Data transmission method, network equipment and terminal equipment
CN108631918B (en) Data transmission method and device
CN114205874A (en) Communication method and device
CN111684747B (en) Method and terminal equipment for transmitting information
WO2019191885A1 (en) Method and device for transmitting configuration information, and method and device for receiving configuration information
EP4270839A1 (en) Control information sending method, receiving method, apparatus, and storage medium

Legal Events

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

Effective date of registration: 20211129

Address after: 215010 room 704, building 5, No. 556, Changjiang Road, high tech Zone, Suzhou, Jiangsu

Patentee after: SUZHOU YUDESHUI ELECTRICAL TECHNOLOGY Co.,Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right