WO2015062477A1 - 一种数据传输方法及设备 - Google Patents

一种数据传输方法及设备 Download PDF

Info

Publication number
WO2015062477A1
WO2015062477A1 PCT/CN2014/089691 CN2014089691W WO2015062477A1 WO 2015062477 A1 WO2015062477 A1 WO 2015062477A1 CN 2014089691 W CN2014089691 W CN 2014089691W WO 2015062477 A1 WO2015062477 A1 WO 2015062477A1
Authority
WO
WIPO (PCT)
Prior art keywords
downlink
configuration
division duplex
duplex uplink
subframe
Prior art date
Application number
PCT/CN2014/089691
Other languages
English (en)
French (fr)
Inventor
赵锐
高秋彬
陈文洪
彭莹
Original Assignee
电信科学技术研究院
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 电信科学技术研究院 filed Critical 电信科学技术研究院
Publication of WO2015062477A1 publication Critical patent/WO2015062477A1/zh

Links

Images

Classifications

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

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a data transmission method and device.
  • D2D Device-to-device
  • a terminal-through technology refers to a method in which neighboring terminals can transmit data through a direct link in a short range without going through a central node (ie, a base station). Forward.
  • both user equipment 1 (UE1) and user equipment 2 (UE2) are out of coverage; in the scenario of FIG. 1b, UE1 is in the network coverage (In Coverage), UE2 is in In the scenario of Figure 1c, UE1 and UE2 are within the network coverage of the same cell; in the scenario of Figure 1d, UE1 and UE2 are within the network coverage of different cells.
  • UE1 and UE2 are within the network coverage of different cells.
  • a typical application scenario includes group/broadcast communication between D2D users.
  • D2D communication including D2D discovery and D2D communication
  • TDD Time Division Duplexing
  • a terminal with D2D communication capability may have both D2D communication and cellular communication, and a resource multiplexing method of D2D communication and cellular communication is TDM multiplexing.
  • a D2D link of a User Equipment if a D2D link of a User Equipment (UE) is located, it is a Physical Downlink Shared Channel (PDSCH) feedback that requires a cellular link.
  • the subframe in which the Acknowledgement/Negative Acknowledgment (ACK/NACK) information is located may cause a collision between the physical uplink control channel (PUCCH) of the D2D link and the cellular link.
  • PUCCH physical uplink control channel
  • subframe 8 in one radio frame is configured as a D2D subframe, then if a D2D terminal schedules a PDSCH that transmits a cellular link in subframe 4, then The corresponding ACK/NACK needs to be fed back in the subframe 8, which causes the PUCCH of the cellular link to collide with the transmission of the D2D link.
  • the purpose of the present application is to provide a data transmission method and apparatus to solve the problem of ACK/NACK feedback conflict between a D2D link and a cellular link PDSCH.
  • a data transmission method on the user equipment side includes:
  • the user equipment receives the cellular downlink data in the downlink subframe indicated by the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is determined according to the TDD uplink and downlink configuration and the D2D subframe configuration of the cellular;
  • the user equipment performs the hybrid downlink repeat data in the uplink subframe of the TDD uplink and downlink reference configuration according to the Hybrid Automatic Repeat Request (HARQ) feedback timing of the cellular downlink data configured according to the TDD uplink and downlink reference configuration.
  • HARQ Hybrid Automatic Repeat Request
  • ACK/NACK feedback the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for ACK/NACK feedback of the cellular downlink data.
  • the user equipment uses the TDD uplink and downlink reference configuration to perform cellular downlink data reception and ACK/NACK feedback, and the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the cellular downlink data.
  • the ACK/NACK feedback thus avoiding the problem of the D2D link conflicting with the ACK/NACK feedback of the cellular link's PDSCH.
  • the foregoing TDD uplink and downlink reference configuration may be that the network side device broadcasts a message through the system.
  • the device may be delivered by the network side device through the dedicated signaling of the user equipment, or may be determined by the user equipment in the same manner as the network side device.
  • the manner of determining the foregoing TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is defined based on the TDD uplink and downlink reference configuration.
  • the HARQ feedback timing of the downlink data of the cellular, in the TDD uplink and downlink configuration, the subframe with the same D2D subframe number is a pseudo downlink subframe, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink configuration of the cellular
  • the downlink subframes with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent by the system broadcast message, or may be sent by the network side device through the dedicated signaling of the user equipment.
  • a data transmission method on a network device side includes:
  • the network side device sends the cellular downlink data in the downlink subframe indicated by the TDD uplink and downlink reference configuration, where the TDD uplink and downlink reference configuration is determined according to the TDD uplink and downlink configuration and the D2D subframe configuration of the cellular;
  • the network side device according to the cellular downlink data configured based on the foregoing TDD uplink and downlink reference configuration
  • the uplink subframe of the TDD uplink and downlink reference configuration receives the ACK/NACK feedback of the cellular downlink data, and the subframe with the same D2D subframe number is not used for the cellular downlink data in the TDD uplink and downlink reference configuration.
  • ACK/NACK feedback is not used for the cellular downlink data in the TDD uplink and downlink reference configuration.
  • the network side device uses the TDD uplink and downlink reference configuration to perform the downlink data transmission and the ACK/NACK feedback, and the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used.
  • the ACK/NACK feedback of the cellular downlink data avoids the problem of the D2D link conflicting with the ACK/NACK feedback of the PDCH of the cellular link.
  • the TDD uplink and downlink reference configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and sent to the user equipment by using the dedicated signaling of the user equipment. It is also possible that the network side device is determined in the same manner as the user equipment.
  • the manner of determining the TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is defined based on the TDD uplink and downlink reference configuration.
  • the HARQ feedback timing of the downlink data of the cellular, in the TDD uplink and downlink configuration, the subframe with the same D2D subframe number is a pseudo downlink subframe, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink configuration of the cellular
  • the downlink subframes with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and used by the user equipment. Signaling is sent to the user equipment.
  • the embodiment of the present application further provides a user equipment, including:
  • a cellular data receiving module configured to receive cellular downlink data in a downlink subframe of the TDD uplink and downlink reference configuration indication, where the TDD uplink and downlink reference configuration is determined according to a TDD uplink and downlink configuration of the cellular and a device to device D2D subframe configuration;
  • a feedback information sending module configured to perform ACK/NACK feedback of the cellular downlink data in an uplink subframe indicated by the TDD uplink and downlink reference configuration according to a HARQ feedback timing of the cellular downlink data configured according to the TDD uplink and downlink reference configuration,
  • the subframes in the TDD uplink and downlink reference configuration that are the same as the D2D subframe number are not used for ACK/NACK feedback of the cellular downlink data.
  • the user equipment provided by the embodiment of the present application uses the TDD uplink and downlink reference configuration to perform cellular downlink data reception and ACK/NACK feedback, because the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the ACK of the cellular downlink data. /NACK feedback, thus avoiding the problem of D2D links and ACK/NACK feedback conflicts of the PDCH of the cellular link.
  • the TDD uplink and downlink reference configuration may be delivered by the network side device through the system broadcast message, and may be sent by the network side device through the dedicated signaling of the user equipment, or may be the user equipment according to the network side.
  • the device is determined in the same way.
  • the manner of determining the foregoing TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are pseudo downlink subframes, and the In the TDD uplink and downlink reference configuration, the downlink subframes in the TDD uplink and downlink configuration of the cellular are the same, but the downlink subframes in the opposite transmission direction are pseudo downlink subframes; or, if the changed TDD uplink and downlink configuration and the standard specified TDD are up and down
  • the row configuration is different, and the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the HARQ feedback timing of the cellular downlink data based on the TDD uplink and downlink reference configuration is defined, and the defined TDD is up and down.
  • the subframe with the same D2D subframe number is a pseudo downlink subframe
  • the downlink subframe in the TDD uplink and downlink reference configuration is the same as the subframe number in the TDD uplink and downlink configuration of the cell, but the downlink subframe is opposite in the transmission direction. Pseudo downlink subframe.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent by the system broadcast message, or may be delivered by the network side device through the dedicated signaling of the user equipment.
  • the embodiment of the present application further provides another user equipment, including: a transceiver, a processor, and a memory;
  • the processor is configured to read a program in the memory, and perform the following process: receiving, by the transceiver, downlink downlink data in a downlink subframe indicated by a time division duplex uplink and downlink reference configuration, where the time division duplex uplink and downlink The reference configuration is determined according to a time division duplex uplink and downlink configuration and a D2D subframe configuration of the cell; and a HARQ feedback timing according to the cellular downlink data configured based on the time division duplex uplink and downlink reference configuration, by the transceiver at the time division
  • the uplink subframe of the duplex uplink and downlink reference configuration indicates that the downlink downlink data is ACK/NACK, and the subframe with the same D2D subframe number in the time division duplex uplink and downlink reference configuration is not used for the cellular downlink data.
  • ACK/NACK feedback indicates that the downlink downlink data is ACK/NACK, and the subframe with the same D2D subframe number in the time division duplex
  • the user equipment provided by the embodiment of the present application uses the TDD uplink and downlink reference configuration to perform cellular downlink data reception and ACK/NACK feedback, because the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the cellular downlink data.
  • ACK/NACK feedback thus avoiding the problem of D2D link and ACK/NACK feedback collision of the PDCH of the cellular link.
  • the embodiment of the present application further provides a network side device, and a package include:
  • a cellular data sending module configured to send cellular downlink data in a downlink subframe of the TDD uplink and downlink reference configuration indication, where the TDD uplink and downlink reference configuration is determined according to a TDD uplink and downlink configuration and a D2D subframe configuration of the cellular;
  • the feedback information receiving module is configured to receive the ACK/NACK feedback of the cellular downlink data in the uplink subframe indicated by the TDD uplink and downlink reference configuration according to the HARQ feedback timing of the cellular downlink data configured according to the TDD uplink and downlink reference configuration.
  • the network side device uses the TDD uplink and downlink reference configuration to perform the downlink data transmission and the ACK/NACK feedback, and the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the cellular downlink.
  • the ACK/NACK feedback of the data thus avoids the problem of the D2D link conflicting with the ACK/NACK feedback of the PDCH of the cellular link.
  • the TDD uplink and downlink reference configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and sent to the user equipment by using the dedicated signaling of the user equipment. It is also possible that the network side device is determined in the same manner as the user equipment.
  • the manner of determining the TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the definition is based on the TDD.
  • the subframes refer to the configured HARQ feedback timing of the downlink data of the cellular, and the subframes with the same D2D subframe number in the TDD uplink and downlink configuration are pseudo downlink subframes, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink of the cellular
  • the downlink subframes in the configuration with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be a dedicated message determined by the network side device and passed by the user equipment. Order to send to the user device.
  • the embodiment of the present application further provides a network side device, including: a transceiver, a processor, and a memory;
  • the processor is configured to read a program in the memory, and perform the following process: sending, by the transceiver, cellular downlink data in a downlink subframe indicated by a time division duplex uplink and downlink reference configuration, where the time division duplex uplink and downlink reference configuration And determining, according to the time division duplex uplink and downlink configuration and the D2D subframe configuration of the cell, and according to the HARQ feedback timing of the cellular downlink data based on the time division duplex uplink and downlink reference configuration, by using the transceiver in the time division duplex
  • the uplink subframe indicated by the uplink and downlink reference configuration receives ACK/NACK feedback of the cellular downlink data.
  • the network side device uses the TDD uplink and downlink reference configuration to perform the downlink data transmission and the ACK/NACK feedback, because the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the cellular.
  • the ACK/NACK feedback of the downlink data avoids the problem that the D2D link conflicts with the ACK/NACK feedback of the PDSCH of the cellular link.
  • 1a to 1d are schematic diagrams of a D2D scene
  • FIG. 2 is a schematic diagram of transmission collision of a PUCCH and a D2D link of a cell in the same subframe
  • FIG. 3 is a flowchart of a method for data transmission on a user equipment side according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a method for data transmission on a network device side according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of determining a TDD uplink and downlink reference configuration according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of another TDD uplink and downlink reference configuration according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a user equipment for data transmission according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a network side device for data transmission according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a user equipment according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a network side device according to an embodiment of the present disclosure.
  • Manner 1 By scheduling, for example, the transmission of the Physical Downlink Shared Channel (PDSCH) of the D2D UE in the subframe n-k is not scheduled.
  • the problem is that the transmission of the cell is limited.
  • the uplink and downlink subframes share one radio frame, and one uplink subframe needs to carry multiple downlink subframes in some TDD uplink and downlink configurations.
  • the ACK/NACK feedback of the PDSCH by avoiding scheduling the PDSCH transmission of the downlink subframe corresponding to the uplink subframe, has a large impact on the PDSCH transmission of the D2D UE of the TDD system.
  • Mode 3 If a collision occurs, the transmission of the D2D link is discarded, which affects the transmission of the D2D link.
  • the embodiment of the present application provides a data transmission method and device.
  • the user equipment and the network side device use the TDD uplink and downlink reference configuration to perform cellular downlink data transmission and ACK/NACK feedback.
  • the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the ACK/NACK of the cellular downlink data. Feedback, thus avoiding the problem of D2D links colliding with the ACK/NACK feedback of the cellular link's PDSCH.
  • the solution provided by the embodiment of the present application improves resource utilization compared to the above-mentioned method for avoiding conflict.
  • the following will be taken from the user equipment side and the network respectively with reference to the accompanying drawings. The method and device provided by the embodiments of the present application are described in detail on the network device side.
  • FIG. 3 is a schematic diagram of a data transmission method on a user equipment side according to an embodiment of the present disclosure, which specifically includes the following operations:
  • step 300 the user equipment receives the downlink downlink data in the downlink subframe of the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is determined according to the TDD uplink and downlink configuration and the D2D subframe configuration of the cellular.
  • the user equipment refers to a D2D UE in the network coverage.
  • the downlink data of the cell refers to downlink data of the cellular link, for example, data transmitted through the PDSCH.
  • the TDD uplink and downlink configuration of the cellular refers to the TDD uplink and downlink configuration used by the cellular network accessed by the user equipment.
  • step 310 the user equipment performs ACK/NACK feedback of the downlink downlink data in the uplink subframe of the TDD uplink and downlink reference configuration according to the HARQ feedback timing of the downlink data of the TDD uplink and downlink reference configuration, where the TDD uplink and downlink The subframe in the reference configuration that is the same as the D2D subframe number is not used for ACK/NACK feedback of the cellular downlink data.
  • the TDD uplink and downlink reference configuration is determined according to the TDD uplink and downlink configuration and the D2D subframe configuration of the cellular.
  • the subframes that are the same as the D2D subframe number, and the downlink subframes that are the same as the subframe ID of the TDD uplink and downlink configuration of the cell but have the opposite transmission direction are pseudo downlink subframes.
  • the TDD uplink and downlink reference configuration may be delivered by the network side device through the system broadcast message, and may be sent by the network side device through the dedicated signaling of the user equipment, or may be the user equipment according to the network side.
  • the device is determined in the same way.
  • the TDD uplink and downlink reference configuration may be transmitted through a Radio Resource Control (RRC) message, or the TDD may be used.
  • RRC Radio Resource Control
  • the uplink and downlink reference configuration is transmitted through a Media Access Control Control Element (MAC CE) information.
  • MAC CE Media Access Control Control Element
  • the TDD uplink and downlink reference configuration is adopted. RRC message transmission.
  • the manner of determining the foregoing TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the TDD uplink and downlink reference configuration is the same as the D2D subframe number.
  • the subframe is a pseudo downlink subframe, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the HARQ feedback timing of the cellular downlink data based on the TDD uplink and downlink reference configuration is defined, and the defined TDD uplink and downlink configuration is used.
  • the subframes with the same D2D subframe number are pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes with opposite transmission directions are pseudo-downlinks. frame.
  • the pseudo downlink subframe indicates that the subframe is actually used for D2D link operation, and is not used for cellular downlink transmission (including downlink data, reference signal detection and other downlink signals).
  • the network side device determines according to the foregoing manner.
  • the user equipment is sent by the system broadcast message or the dedicated signaling of the user equipment.
  • the HARQ feedback timing of the cellular downlink data based on the TDD uplink and downlink reference configuration in the foregoing step 310 is standard.
  • the HARQ feedback timing corresponding to each TDD uplink and downlink configuration specified by the standard can be seen in Table 1.
  • Table 1 Values of k in the uplink and downlink configuration of TDD
  • the uplink subframe n needs to feed back the ACK/NACK information corresponding to the PDSCH transmitted in the n-k subframe.
  • k is a set, as shown in Table 1.
  • the D2D subframe configuration may be determined by the network side device and sent by the system broadcast message, or may be the dedicated signaling of the network side device through the user equipment. Issued.
  • the D2D subframe configuration is sent by the network side device through the dedicated signaling of the user equipment. Specifically, the D2D subframe configuration may be transmitted through the RRC message, or the D2D subframe configuration may be transmitted through the MAC CE information. If the user equipment is in the RRC connected state, preferably, the D2D subframe configuration is transmitted through the RRC message.
  • the D2D subframe configuration includes at least the following information: a period of the D2D subframe (for example, 5 ms, 10 ms, 20 ms, etc.), a number of the D2D subframe, or a subframe offset.
  • the D2D subframe configuration may be indicated in a manner of a pattern.
  • FIG. 4 is a schematic diagram of a data transmission method on a network device side according to an embodiment of the present disclosure, which specifically includes the following operations:
  • Step 400 The network side device sends the cellular downlink data in the downlink subframe indicated by the TDD uplink and downlink reference configuration, where the TDD uplink and downlink reference configuration is based on the TDD uplink and downlink configuration of the cellular and the D2D sub-interface.
  • the frame configuration is determined.
  • the network side device receives the ACK/NACK feedback of the cellular downlink data in the uplink subframe indicated by the TDD uplink and downlink reference configuration according to the HARQ feedback timing of the cellular downlink data configured according to the TDD uplink and downlink reference configuration, where the TDD is up and down.
  • the subframe with the same D2D subframe number in the row reference configuration is not used for ACK/NACK feedback of cellular downlink data.
  • the TDD uplink and downlink reference configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and sent to the user equipment by using the dedicated signaling of the user equipment. It may also be determined by the network side device in the same manner as the user equipment.
  • the manner of determining the TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is defined based on the TDD uplink and downlink reference configuration.
  • the HARQ feedback timing of the downlink data of the cellular, in the TDD uplink and downlink configuration, the subframe with the same D2D subframe number is a pseudo downlink subframe, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink configuration of the cellular
  • the downlink subframes with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the configuration may be determined by the network side device and sent to the user equipment through the system broadcast message, or may be determined by the network side device and sent to the user equipment through the dedicated signaling of the user equipment.
  • the TDD uplink and downlink configuration of the cell is 1, the D2D subframe is configured with a 10 ms period, and the subframe 3 and the subframe 8 are D2D subframes.
  • the subframe 3 and the subframe 8 in the TDD uplink and downlink configuration 1 of the cell are regarded as pseudo downlink subframes (pseudo DL subframes).
  • the changed TDD uplink and downlink configuration is TDD uplink and downlink configuration 2, and then the TDD uplink and downlink configuration 2 is determined to be the TDD uplink and downlink reference configuration.
  • the ACK/NACK information needs to be fed back in the subframe 8, and a potential PUCCH and D2D link collision occurs.
  • the network side device sends the PDSCH in the subframe 4 according to the TDD uplink and downlink reference configuration (that is, the TDD uplink and downlink configuration 2); the user equipment is configured on the subframe 4 according to the TDD uplink and downlink reference configuration.
  • the TDD uplink and downlink reference configuration that is, the TDD uplink and downlink configuration 2
  • the user equipment is configured on the subframe 4 according to the TDD uplink and downlink reference configuration.
  • the network side device corresponding to the TDD uplink and downlink reference configuration
  • the HARQ feedback timing, the subframe 2 of the next radio frame indicated by the TDD uplink and downlink reference configuration receives the AKC/NACK feedback, thus avoiding the collision of the potential PUCCH and the D2D link.
  • the TDD uplink and downlink configuration of the cell is 1, the D2D subframe is configured with a 10 ms period, and the subframe 8 is a D2D subframe.
  • the subframe 8 in the TDD uplink and downlink configuration 1 of the cell is used as the pseudo downlink subframe.
  • the changed TDD uplink and downlink configuration is different from the TDD uplink and downlink configuration 0 to 6.
  • the TDD uplink and downlink configuration 2 can be used as the TDD uplink and downlink reference configuration.
  • the transmission direction of the subframe 3 and the TDD uplink and downlink configuration is opposite, and also serves as a pseudo downlink subframe.
  • the ACK/NACK information needs to be fed back in the subframe 8, and a potential PUCCH and D2D link collision occurs.
  • the network side device is configured according to the TDD uplink and downlink reference.
  • the PDSCH is transmitted on the subframe 4, and the PDSCH is received on the subframe 4 in accordance with the TDD uplink and downlink reference configuration, and is used by the device according to the HARQ feedback timing corresponding to the TDD uplink and downlink reference configuration.
  • ACK/NACK feedback is performed on the subframe 2 of the next radio frame indicated by the TDD uplink and downlink reference configuration; the network side device according to the HARQ feedback timing corresponding to the TDD uplink and downlink reference configuration, and the next radio frame indicated by the TDD uplink and downlink reference configuration Subframe 2 receives the AKC/NACK feedback, thus avoiding potential PUCCH and D2D link collisions.
  • the embodiment of the present application further provides a user equipment, as shown in FIG. 7, including:
  • the cellular data receiving module 701 is configured to receive the cellular downlink data in the downlink subframe of the TDD uplink and downlink reference configuration indication, where the TDD uplink and downlink reference configuration is determined according to the TDD uplink and downlink configuration of the cellular and the device to device D2D subframe configuration.
  • the feedback information sending module 702 is configured to perform ACK/NACK feedback of the cellular downlink data in an uplink subframe indicated by the TDD uplink and downlink reference configuration according to a HARQ feedback timing of the downlink downlink data configured according to the TDD uplink and downlink reference configuration.
  • the subframe in the TDD uplink and downlink reference configuration that is the same as the D2D subframe number is not used for ACK/NACK feedback of the cellular downlink data.
  • the user equipment provided by the embodiment of the present application uses the TDD uplink and downlink reference configuration to perform cellular downlink data reception and ACK/NACK feedback, because the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the ACK of the cellular downlink data. /NACK feedback, thus avoiding the problem of D2D links and ACK/NACK feedback conflicts of the PDCH of the cellular link.
  • the TDD uplink and downlink reference configuration may be delivered by the network side device through the system broadcast message, and may be sent by the network side device through the dedicated signaling of the user equipment, and the user equipment may be in accordance with the network side device. The same way is determined.
  • the manner of determining the foregoing TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is defined based on the TDD uplink and downlink reference configuration.
  • the HARQ feedback timing of the downlink data of the cellular, in the TDD uplink and downlink configuration, the subframe with the same D2D subframe number is a pseudo downlink subframe, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink configuration of the cellular
  • the downlink subframes with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent by the system broadcast message, or may be performed by the network side device through the dedicated signaling of the user equipment. Made.
  • the embodiment of the present application further provides a network side device, as shown in FIG.
  • the cellular data sending module 801 is configured to send the cellular downlink data in the downlink subframe of the TDD uplink and downlink reference configuration indication, where the TDD uplink and downlink reference configuration is determined according to the TDD uplink and downlink configuration and the D2D subframe configuration of the cellular;
  • the feedback information receiving module 802 is configured to receive ACK/NACK feedback of the cellular downlink data in an uplink subframe indicated by the TDD uplink and downlink reference configuration according to a HARQ feedback timing of the downlink downlink data configured according to the TDD uplink and downlink reference configuration. .
  • the network side device uses the TDD uplink and downlink reference configuration to perform the downlink data transmission and the ACK/NACK feedback, and the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the cellular downlink.
  • ACK/NACK feedback of the data thus avoiding A problem in which the D2D link conflicts with the ACK/NACK feedback of the PDSCH of the cellular link.
  • the TDD uplink and downlink reference configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and sent to the user equipment by using the dedicated signaling of the user equipment. It is also possible that the network side device is determined in the same manner as the user equipment.
  • the manner of determining the TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is defined based on the TDD uplink and downlink reference configuration.
  • the HARQ feedback timing of the downlink data of the cellular, in the TDD uplink and downlink configuration, the subframe with the same D2D subframe number is a pseudo downlink subframe, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink configuration of the cellular
  • the downlink subframes with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and passed by the user equipment.
  • the dedicated signaling is sent to the user equipment.
  • the network device may be an evolved node (eNB), a node (NB), a relay, or the like.
  • eNB evolved node
  • NB node
  • relay or the like.
  • the embodiment of the present application further provides another user equipment, as shown in FIG. 9, including: a transceiver 901, a processor 902, a memory 903, and a bus interface 904, a user interface 905;
  • the transceiver 901 is configured to receive and send data under the control of the processor 902.
  • the processor 902 is configured to read a program in the memory, and perform the following process: receiving, by the transceiver, the downlink downlink data in the downlink subframe indicated by the time division duplex uplink and downlink reference configuration, and the time division duplex uplink and downlink reference configuration is based on the time of the cellular Determined by the duplex uplink and downlink configuration and the D2D subframe configuration; and according to the HARQ feedback timing of the cellular downlink data based on the time division duplex uplink and downlink reference configuration, performing, by the transceiver, the uplink subframe in the time division duplex uplink and downlink reference configuration indication
  • the ACK/NACK feedback of the downlink data, the subframe with the same D2D subframe number in the time division duplex uplink and downlink reference configuration is not used for ACK/NACK feedback of the cellular downlink data;
  • the memory 903 is configured to store one or more executable programs, which are used to configure the processor.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 902 and various circuits of memory represented by memory 903.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • Bus interface 904 provides an interface.
  • Transceiver 901 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 905 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 902 is responsible for managing the bus architecture and general processing, and the memory 903 can store data used by the processor 902 in performing operations.
  • the user equipment provided by the embodiment of the present application uses the TDD uplink and downlink reference configuration to perform cellular downlink data reception and ACK/NACK feedback, because the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the cellular downlink data.
  • ACK/NACK feedback thus avoiding the problem of D2D link and ACK/NACK feedback collision of the PDCH of the cellular link.
  • the foregoing TDD uplink and downlink reference configuration may be that the network side device broadcasts a message through the system.
  • the device that is delivered may be delivered by the network side device through the dedicated signaling of the user equipment, and may also be determined by the user equipment in the same manner as the network side device.
  • the manner of determining the foregoing TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is defined based on the TDD uplink and downlink reference configuration.
  • the HARQ feedback timing of the downlink data of the cellular, in the TDD uplink and downlink configuration, the subframe with the same D2D subframe number is a pseudo downlink subframe, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink configuration of the cellular
  • the downlink subframes with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent by the system broadcast message, or may be performed by the network side device through the dedicated signaling of the user equipment. Made.
  • the embodiment of the present application further provides another network side device, as shown in FIG. 10, including: a transceiver 1001, a processor 1002, a memory 1003, and a bus interface 1004.
  • the transceiver 1001 is configured to receive and send data under the control of the processor 1002.
  • the processor 1001 is configured to read a program in the memory 1003 and execute the following process: sending and receiving The device transmits the downlink downlink data in the downlink subframe of the time division duplex uplink and downlink reference configuration indication, and the time division duplex uplink and downlink reference configuration is determined according to the time division duplex uplink and downlink configuration and the D2D subframe configuration of the cellular, and according to the time division duplex
  • the HARQ feedback timing of the downlink downlink data of the uplink and downlink reference configuration, the ACK/NACK feedback of the cellular downlink data is received by the transceiver in the uplink subframe indicated by the time division duplex uplink and downlink reference configuration.
  • the memory 1003 is configured to store one or more executable programs, which are used to configure the processor.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 1002 and various circuits of memory represented by memory 1003.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • Bus interface 1004 provides an interface.
  • the transceiver 1001 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 1002 is responsible for managing the bus architecture and general processing, and the memory 1003 can store data used by the processor 1002 in performing operations.
  • the network side device uses the TDD uplink and downlink reference configuration to perform the downlink data transmission and the ACK/NACK feedback, and the subframe with the same D2D subframe number in the TDD uplink and downlink reference configuration is not used for the cellular downlink.
  • the ACK/NACK feedback of the data thus avoids the problem of the D2D link conflicting with the ACK/NACK feedback of the PDCH of the cellular link.
  • the TDD uplink and downlink reference configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and sent to the user equipment by using the dedicated signaling of the user equipment. It is also possible that the network side device is determined in the same manner as the user equipment.
  • the manner of determining the TDD uplink and downlink reference configuration includes but is not limited to:
  • a subframe that is the same as the D2D subframe number in the TDD uplink and downlink configuration of the above-mentioned cell is used as a pseudo downlink subframe;
  • the changed TDD uplink and downlink configuration is the standard TDD uplink and downlink configuration i, i belongs to 0 to 6, then determine that the TDD uplink and downlink configuration i is the TDD uplink and downlink reference configuration;
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration
  • one of the standard TDD uplink and downlink configurations is selected as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration and the D2D subframe.
  • the subframes with the same number are the pseudo-downlink subframes, and the downlink subframes in the TDD uplink and downlink reference configuration are the same as the subframes in the TDD uplink and downlink configuration of the cell, but the downlink subframes in the opposite direction are the downlink subframes; or
  • the changed TDD uplink and downlink configuration is different from the standard TDD uplink and downlink configuration.
  • the TDD uplink and downlink configuration different from the standard TDD uplink and downlink configuration is defined as the TDD uplink and downlink reference configuration, and the TDD uplink and downlink reference configuration is defined based on the TDD uplink and downlink reference configuration.
  • the HARQ feedback timing of the downlink data of the cellular, in the TDD uplink and downlink configuration, the subframe with the same D2D subframe number is a pseudo downlink subframe, and the TDD uplink and downlink reference configuration and the TDD uplink and downlink configuration of the cellular
  • the downlink subframes with the same subframe number but opposite transmission directions are pseudo downlink subframes.
  • the pseudo downlink subframe is not used for cellular downlink transmission.
  • the D2D subframe configuration may be determined by the network side device and sent to the user equipment by using a system broadcast message, or may be determined by the network side device and passed through the user equipment.
  • the exclusive signaling is sent to the user equipment.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种数据传输方法及设备。该方法包括：在时分双工上下行参考配置指示的下行子帧传输蜂窝下行数据，时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的；根据基于时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，在时分双工上下行参考配置指示的上行子帧进行蜂窝下行数据的ACK/NACK反馈，时分双工上下行参考配置中、与D2D子帧编号相同的子帧不用于蜂窝下行数据的ACK/NACK反馈。本申请实施例，避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。

Description

一种数据传输方法及设备
本申请要求在2013年10月31日提交中国专利局、申请号为201310533385.3、发明名称为“一种数据传输方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据传输方法及设备。
背景技术
设备到设备(Device-to-Device，D2D)，即终端直通技术，是指邻近的终端可以在近距离范围内通过直连链路进行数据传输的方式，不需要通过中心节点(即基站)进行转发。
在D2D的研究中，主要考虑的场景有四种，各个场景可以组合出现，如图1a～1d所示。
其中，图1a的场景下，用户设备1(UE1)和用户设备2(UE2)均在网络覆盖外(Out of Coverage)；图1b的场景下，UE1在网络覆盖内(In Coverage)，UE2在网络覆盖外；图1c的场景下，UE1和UE2在同一小区的网络覆盖内；图1d的场景下，UE1和UE2在不同小区的网络覆盖内。
在D2D的通信中，除了用户之间的一对一的通信方式之外，典型的应用场景还包括D2D用户之间进行群组/广播通信。
在有网络覆盖情况下，目前第三代合作伙伴计划(The 3rd Generation Partnership Project，3GPP)标准已经确定D2D通信(包含D2D discovery和D2D communication)工作在蜂窝的上行资源上，例如：在时分双工(Time Division Duplexing，TDD)情况下，工作在上行子帧上。在有网络覆盖情况下，一个具有D2D通信能力的终端，有可能同时存在D2D通信和蜂窝通信，D2D通信和蜂窝通信的一种资源复用方式是TDM复用。
在TDM复用中，如果一个终端(User Equipment，UE)的D2D链接(D2D link)所在的子帧是其需要对蜂窝链接(cellular link)的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)反馈正确确认/错误确认(Acknowledgement/Negative Acknowledgment，ACK/NACK)信息所在的子帧，这样会引起D2D link和cellular link的物理上行控制信道(Physical Uplink Control Channel，PUCCH)的冲突。以TDD上下行配置1为例，如图2所示，一个无线帧中的子帧8被配置为D2D子帧，那么为一个D2D终端如果调度了在子帧4中发送cellular link的PDSCH，那么其对应的在子帧8中需要反馈ACK/NACK，会造成cellular link的PUCCH与D2D link的传输发生冲突。
发明内容
本申请的目的是提供一种数据传输方法及设备，以解决D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
本申请的目的是通过以下技术方案实现的：
一种用户设备侧的数据传输方法，包括：
用户设备在TDD上下行参考配置指示的下行子帧接收蜂窝下行数据，该TDD上下行参考配置是根据蜂窝的TDD上下行配置和D2D子帧配置确定的；
该用户设备根据基于上述TDD上下行参考配置的蜂窝下行数据的混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)反馈时序，在该TDD上下行参考配置指示的上行子帧进行上述蜂窝下行数据的ACK/NACK反馈，该TDD上下行参考配置中、与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的方法，用户设备使用TDD上下行参考配置进行蜂窝下行数据的接收及ACK/NACK反馈，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是网络侧设备通过***广播消息 下发的，可以是网络侧设备通过该用户设备的专属信令下发的，还可以是该用户设备按照与网络侧设备相同的方式确定的。
较佳地，确定上述TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一方法实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息下发的，也可以是网络侧设备通过用户设备的专属信令下发的。
一种网络设备侧的数据传输方法，包括：
网络侧设备在TDD上下行参考配置指示的下行子帧发送蜂窝下行数据，该TDD上下行参考配置是根据蜂窝的TDD上下行配置和D2D子帧配置确定的；
该网络侧设备根据基于上述TDD上下行参考配置的蜂窝下行数据的 HARQ反馈时序，在该TDD上下行参考配置指示的上行子帧接收上述蜂窝下行数据的ACK/NACK反馈，该TDD上下行参考配置中、与D2D子帧编号相同的子帧不用于蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的方法，网络侧设备使用TDD上下行参考配置进行蜂窝下行数据的发送及ACK/NACK反馈的接收，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是由网络侧设备确定并通过***广播消息发送给用户设备的，也可以是由网络侧设备确定并通过用户设备的专属信令发送给该用户设备的，还可以是网络侧设备按照与用户设备相同的方式确定的。
较佳地，确定TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一网络侧设备的方法实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息发送给用户设备的，也可以是网络侧设备确定并通过用户设备的专属信令发送给用户设备的。
基于与方法同样的发明构思，本申请实施例还提供一种用户设备，包括：
蜂窝数据接收模块，用于在TDD上下行参考配置指示的下行子帧接收蜂窝下行数据，所述TDD上下行参考配置是根据蜂窝的TDD上下行配置和设备到设备D2D子帧配置确定的；
反馈信息发送模块，用于根据基于所述TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，在所述TDD上下行参考配置指示的上行子帧进行所述蜂窝下行数据的ACK/NACK反馈，所述TDD上下行参考配置中、与D2D子帧编号相同的子帧不用于所述蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的用户设备使用TDD上下行参考配置进行蜂窝下行数据的接收及ACK/NACK反馈，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是网络侧设备通过***广播消息下发的，可以是网络侧设备通过该用户设备的专属信令下发的，还可以是该用户设备按照与网络侧设备相同的方式确定的。
较佳地，确定上述TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该 TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一用户设备的实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息下发的，也可以是网络侧设备通过用户设备的专属信令下发的。
基于与方法同样的发明构思，本申请实施例还提供另一种用户设备，包括：收发机、处理器、存储器；
所述处理器，用于读取所述存储器中的程序，执行下列过程：通过所述收发机在时分双工上下行参考配置指示的下行子帧接收蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的；以及根据基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，通过所述收发机在所述时分双工上下行参考配置指示的上行子帧进行所述蜂窝下行数据的ACK/NACK反馈，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧不用于所述蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的用户设备，使用TDD上下行参考配置进行蜂窝下行数据的接收及ACK/NACK反馈，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
基于与方法同样的发明构思，本申请实施例还提供一种网络侧设备，包 括：
蜂窝数据发送模块，用于在TDD上下行参考配置指示的下行子帧发送蜂窝下行数据，所述TDD上下行参考配置是根据蜂窝的TDD上下行配置和D2D子帧配置确定的；
反馈信息接收模块，用于根据基于所述TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，在所述TDD上下行参考配置指示的上行子帧接收所述蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的网络侧设备使用TDD上下行参考配置进行蜂窝下行数据的发送及ACK/NACK反馈的接收，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是由网络侧设备确定并通过***广播消息发送给用户设备的，也可以是由网络侧设备确定并通过用户设备的专属信令发送给该用户设备的，还可以是网络侧设备按照与用户设备相同的方式确定的。
较佳地，确定TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下 行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一网络的设备的实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息发送给用户设备的，也可以是网络侧设备确定并通过用户设备的专属信令发送给用户设备的。
基于与方法同样的发明构思，本申请实施例还提供一种网络侧设备，包括：收发机、处理器、存储器；
所述处理器，用于读取存储器中的程序，执行下列过程：通过所述收发机在时分双工上下行参考配置指示的下行子帧发送蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的，以及根据基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，通过所述收发机在所述时分双工上下行参考配置指示的上行子帧接收所述蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的网络侧设备，使用TDD上下行参考配置进行蜂窝下行数据的发送及ACK/NACK反馈的接收，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
附图说明
图1a～图1d为D2D场景示意图；
图2为蜂窝的PUCCH与D2D链接在同一子帧的传输冲突示意图；
图3为本申请实施例提供的一种用户设备侧数据传输的方法流程图；
图4为本申请实施例提供的一种网络设备侧数据传输的方法流程图；
图5为本申请实施例提供的一种确定TDD上下行参考配置的示意图；
图6为本申请实施例提供的另一种确定TDD上下行参考配置的示意图；
图7为本申请实施例提供的一种数据传输的用户设备的结构示意图；
图8为本申请实施例提供的一种数据传输的网络侧设备的结构示意图；
图9为本申请实施例提供的一种用户设备的结构示意图；
图10为本申请实施例提供的一种网络侧设备的结构示意图。
具体实施方式
如何解决D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题，现有机制没有相关的考虑。直观上来说避免冲突的方式有如下几种：
方式一、通过调度避免，例如不调度D2D UE在子帧n-k的物理下行共享信道(PDSCH)的传输。这样导致的问题是蜂窝的传输会受到限制，尤其在TDD***中，由于上下行子帧分享一个无线帧，并且一个上行子帧在某些TDD上下行配置中需要承载多个下行子帧中的PDSCH的ACK/NACK反馈，那么通过避免调度与该上行子帧对应的下行子帧的PDSCH的传输，会对TDD***的D2D UE的蜂窝的PDSCH的传输造成较大的影响。
方式二、如果发生冲突，则丢弃cellular link的PUCCH反馈，同样会对蜂窝的传输造成影响。
方式三、如果发生冲突，则丢弃D2D link的传输，这样会对D2D link的传输造成影响。
采用上述方式的组合，例如调度避免与丢弃D2D link的传输两种方式的结合，也存在同样的问题。
本申请实施例提供一种数据传输方法及设备。用户设备和网络侧设备使用TDD上下行参考配置进行蜂窝下行数据的传输及ACK/NACK反馈，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。另外，较之上述提到的避免冲突的方法，本申请实施例提供的解决方案提高了资源利用率。下面将结合附图，分别从用户设备侧和网 络设备侧对本申请实施例提供的方法及设备进行详细说明。
图3所示为本申请实施例提供的一种用户设备侧的数据传输方法，具体包括如下操作：
步骤300，用户设备在TDD上下行参考配置指示的下行子帧接收蜂窝下行数据，该TDD上下行参考配置是根据蜂窝的TDD上下行配置和D2D子帧配置确定的。
本申请实施例中，用户设备是指网络覆盖内的D2D UE。
本申请实施例中，蜂窝下行数据是指cellular link的下行数据，例如通过PDSCH传输的数据。
本申请实施例中，蜂窝的TDD上下行配置是指用户设备接入的蜂窝网络所使用的TDD上下行配置。
步骤310，该用户设备根据基于上述TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，在该TDD上下行参考配置指示的上行子帧进行上述蜂窝下行数据的ACK/NACK反馈，该TDD上下行参考配置中、与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈。
本申请实施例中，如上所述，TDD上下行参考配置是根据蜂窝的TDD上下行配置和D2D子帧配置确定的。TDD上下行参考配置中、与D2D子帧编号相同的子帧，以及与蜂窝的TDD上下行配置的子帧编号相同但传输方向相反的下行子帧，为伪下行子帧。
较佳地，上述TDD上下行参考配置可以是网络侧设备通过***广播消息下发的，可以是网络侧设备通过该用户设备的专属信令下发的，还可以是该用户设备按照与网络侧设备相同的方式确定的。
其中，如果TDD上下行参考配置是网络侧设备通过用户设备的专属信令下发的，具体可以将TDD上下行参考配置通过无线资源控制协议(Radio Resource Control，RRC)消息传输，也可以将TDD上下行参考配置通过媒体接入控制信道单元(Media Access Control Control Element，MAC CE)信息传输。对处于RRC连接态的用户设备，优选的，将TDD上下行参考配置通过 RRC消息传输。
较佳地，确定上述TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，可以有如下两种处理方式：
其一、从标准规定的TDD上下行配置中选择一个与变化后的TDD上下行配置最为接近的TDD上下行配置作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
其二、定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧表示该子帧实际上用于D2D link的操作，不用于蜂窝下行传输(包括下行数据、参考信号检测等下行信号)。
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，为避免用户设备与网络侧设备确定的TDD上下行子帧配置不同，较佳地，由网络侧设备按照上述方式确定并通过***广播消息或用户设备的专属信令发送给用户设备。
本申请实施例中，如果确定的TDD上下行参考配置是标准规定的TDD上下行配置中的一种，则上述步骤310中基于TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序就是标准规定的TDD上下行配置对应的HARQ反 馈时序。标准规定的各个TDD上下行配置对应的HARQ反馈时序可以参见表1。
表1：TDD上下行配置中k的取值
Figure PCTCN2014089691-appb-000001
其中，上行子帧n需要反馈的是n-k子帧中传输的PDSCH对应的ACK/NACK信息。在TDD***中，k是一个集合，即表1所示。
基于上述任一用户设备进行数据传输的方法实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息下发的，也可以是网络侧设备通过用户设备的专属信令下发的。
如果D2D子帧配置是网络侧设备通过用户设备的专属信令下发的。具体的，可以通过RRC消息传输D2D子帧配置，也可以通过MAC CE信息传输D2D子帧配置。如果用户设备处于RRC连接态，优选的，通过RRC消息传输D2D子帧配置。
本申请实施例中，D2D子帧配置中至少包括如下信息：D2D子帧的周期(例如5ms、10ms、20ms等等)、D2D子帧的编号或者子帧偏移量。具体可以通过图样的方式指示D2D子帧配置。
如图4所示为本申请实施例提供的一种网络设备侧的数据传输方法，具体包括如下操作：
步骤400，网络侧设备在TDD上下行参考配置指示的下行子帧发送蜂窝下行数据，该TDD上下行参考配置是根据蜂窝的TDD上下行配置和D2D子 帧配置确定的。
步骤410，该网络侧设备根据基于上述TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，在该TDD上下行参考配置指示的上行子帧接收上述蜂窝下行数据的ACK/NACK反馈，该TDD上下行参考配置中、与D2D子帧编号相同的子帧不用于蜂窝下行数据的ACK/NACK反馈。
较佳地，上述TDD上下行参考配置可以是由网络侧设备确定并通过***广播消息发送给用户设备的，也可以是由网络侧设备确定并通过用户设备的专属信令发送给该用户设备的，还可以是由网络侧设备按照与用户设备相同的方式确定的。
较佳地，确定TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一网络设备进行数据传输的方法实施例，较佳地，D2D子帧 配置可以是由网络侧设备确定并通过***广播消息发送给用户设备的，也可以是由网络侧设备确定并通过用户设备的专属信令发送给用户设备的。
本申请网络设备实施例中，与用户设备侧相同或类似的技术特征的具体描述可以参照用户设备侧方法实施例的描述，这里不再赘述。
如图5所示，以蜂窝的TDD上下行配置为1，D2D子帧配置10ms周期、子帧3和子帧8为D2D子帧为例。根据蜂窝的TDD上下行配置1和D2D子帧的配置，将蜂窝的TDD上下行配置1中的子帧3和子帧8作为伪下行子帧(伪DL子帧)。变化后的TDD上下行配置为TDD上下行配置2，则确定TDD上下行配置2为TDD上下行参考配置。对于子帧4上传输的PDSCH来说，按照原来的TDD上下行配置1对应的HARQ反馈时序，需要在子帧8反馈ACK/NACK信息，会发生潜在的PUCCH和D2D link的冲突。
采用本申请实施例提供的技术方案，网络侧设备按照TDD上下行参考配置(即TDD上下行配置2)，在子帧4上发送PDSCH；用户设备按照TDD上下行参考配置，在子帧4上接收PDSCH；用于设备按照TDD上下行参考配置对应的HARQ反馈时序，在TDD上下行参考配置指示的下一个无线帧的子帧2进行ACK/NACK反馈；网络侧设备按照TDD上下行参考配置对应的HARQ反馈时序，在TDD上下行参考配置指示的下一个无线帧的子帧2接收AKC/NACK反馈，这样就避免了潜在的PUCCH和D2D link的冲突。
如图6所示，以蜂窝的TDD上下行配置为1，D2D子帧配置10ms周期、子帧8为D2D子帧为例。根据蜂窝的TDD上下行配置和D2D子帧的配置，将蜂窝的TDD上下行配置1中的子帧8作为伪下行子帧。变化后的TDD上下行配置与TDD上下行配置0～6均不同。可以将TDD上下行配置2作为TDD上下行参考配置，在该TDD上下行参考配置中，子帧3与TDD上下行配置的传输方向相反，也作为伪下行子帧。对于子帧4上传输的PDSCH来说，按照原来的TDD上下行配置1对应的HARQ反馈时序，需要在子帧8反馈ACK/NACK信息，会发生潜在的PUCCH和D2D link的冲突。
采用本申请实施例提供的技术方案，网络侧设备按照TDD上下行参考配 置(即TDD上下行配置2)，在子帧4上发送PDSCH；用户设备按照TDD上下行参考配置，在子帧4上接收PDSCH；用于设备按照TDD上下行参考配置对应的HARQ反馈时序，在TDD上下行参考配置指示的下一个无线帧的子帧2进行ACK/NACK反馈；网络侧设备按照TDD上下行参考配置对应的HARQ反馈时序，在TDD上下行参考配置指示的下一个无线帧的子帧2接收AKC/NACK反馈，这样就避免了潜在的PUCCH和D2D link的冲突。
基于与方法同样的发明构思，本申请实施例还提供一种用户设备，如图7所示，包括：
蜂窝数据接收模块701，用于在TDD上下行参考配置指示的下行子帧接收蜂窝下行数据，所述TDD上下行参考配置是根据蜂窝的TDD上下行配置和设备到设备D2D子帧配置确定的；
反馈信息发送模块702，用于根据基于所述TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，在所述TDD上下行参考配置指示的上行子帧进行所述蜂窝下行数据的ACK/NACK反馈，所述TDD上下行参考配置中、与D2D子帧编号相同的子帧不用于所述蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的用户设备使用TDD上下行参考配置进行蜂窝下行数据的接收及ACK/NACK反馈，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是网络侧设备通过***广播消息下发的，可以是网络侧设备通过该用户设备的专属信令下发的，还可以该用户设备按照与网络侧设备相同的方式确定的。
较佳地，确定上述TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一用户设备进行数据传输的实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息下发的，也可以是网络侧设备通过用户设备的专属信令下发的。
基于与方法同样的发明构思，本申请实施例还提供一种网络侧设备，如图8所示，包括：
蜂窝数据发送模块801，用于在TDD上下行参考配置指示的下行子帧发送蜂窝下行数据，所述TDD上下行参考配置是根据蜂窝的TDD上下行配置和D2D子帧配置确定的；
反馈信息接收模块802，用于根据基于所述TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，在所述TDD上下行参考配置指示的上行子帧接收所述蜂窝下行数据的ACK/NACK反馈。
本申请实施例提供的网络侧设备使用TDD上下行参考配置进行蜂窝下行数据的发送及ACK/NACK反馈的接收，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了 D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是由网络侧设备确定并通过***广播消息发送给用户设备的，也可以是由网络侧设备确定并通过用户设备的专属信令发送给该用户设备的，还可以是网络侧设备按照与用户设备相同的方式确定的。
较佳地，确定TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一网络设备进行数据传输的实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息发送给用户设备的，也可以是网络侧设备确定并通过用户设备的专属信令发送给用户设备的。
本申请实施例中，网络设备可以是演进型节点(eNB)，节点(NB)，中继等等。
基于与方法同样的发明构思，本申请实施例还提供另一种用户设备，如图9所示，包括：收发机901、处理器902、存储器903，还包括总线接口904，用户接口905；
收发机901，用于在处理器902的控制下接收和发送数据；
处理器902，用于读取存储器中的程序，执行下列过程：通过收发机在时分双工上下行参考配置指示的下行子帧接收蜂窝下行数据，时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的；以及根据基于时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，通过收发机在时分双工上下行参考配置指示的上行子帧进行蜂窝下行数据的ACK/NACK反馈，时分双工上下行参考配置中、与D2D子帧编号相同的子帧不用于蜂窝下行数据的ACK/NACK反馈；
存储器903，用于存储一个或多个可执行程序，被用于配置处理器。
其中，在图9中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器902代表的一个或多个处理器和存储器903代表的存储器的各种电路链接在一起。总线架构还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口904提供接口。收发机901可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口905还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。处理器902负责管理总线架构和通常的处理，存储器903可以存储处理器902在执行操作时所使用的数据。
本申请实施例提供的用户设备，使用TDD上下行参考配置进行蜂窝下行数据的接收及ACK/NACK反馈，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是网络侧设备通过***广播消息 下发的，可以是网络侧设备通过该用户设备的专属信令下发的，还可以该用户设备按照与网络侧设备相同的方式确定的。
较佳地，确定上述TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一用户设备进行数据传输的实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息下发的，也可以是网络侧设备通过用户设备的专属信令下发的。
基于与方法同样的发明构思，本申请实施例还提供另一种网络侧设备，如图10所示，包括：收发机1001、处理器1002、存储器1003，还包括总线接口1004。
收发机1001，用于在处理器1002的控制下接收和发送数据；
处理器1001，用于读取存储器1003中的程序，执行下列过程：通过收发 机在时分双工上下行参考配置指示的下行子帧发送蜂窝下行数据，时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的，以及根据基于时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，通过收发机在时分双工上下行参考配置指示的上行子帧接收蜂窝下行数据的ACK/NACK反馈。
存储器1003，用于存储一个或多个可执行程序，被用于配置处理器。
其中，在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1002代表的一个或多个处理器和存储器1003代表的存储器的各种电路链接在一起。总线架构还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1004提供接口。收发机1001可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器1002负责管理总线架构和通常的处理，存储器1003可以存储处理器1002在执行操作时所使用的数据。
本申请实施例提供的网络侧设备使用TDD上下行参考配置进行蜂窝下行数据的发送及ACK/NACK反馈的接收，由于TDD上下行参考配置中与D2D子帧编号相同的子帧不用于该蜂窝下行数据的ACK/NACK反馈，因此避免了D2D链接与蜂窝链接的PDSCH的ACK/NACK反馈冲突的问题。
较佳地，上述TDD上下行参考配置可以是由网络侧设备确定并通过***广播消息发送给用户设备的，也可以是由网络侧设备确定并通过用户设备的专属信令发送给该用户设备的，还可以是网络侧设备按照与用户设备相同的方式确定的。
较佳地，确定TDD上下行参考配置的方式包括但不仅限于是：
将上述蜂窝的TDD上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧；
如果变化后的TDD上下行配置为标准规定的TDD上下行配置i，i属于0～6，则确定TDD上下行配置i为TDD上下行参考配置；
如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则从标准规定的TDD上下行配置中选择一个作为TDD上下行参考配置，该TDD上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的TDD上下行配置与标准规定的TDD上下行配置均不同，则定义与标准规定的TDD上下行配置不同的TDD上下行配置作为TDD上下行参考配置，并定义基于该TDD上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的TDD上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且该TDD上下行参考配置中、与蜂窝的TDD上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
本申请实施例中，伪下行子帧不用于蜂窝下行传输。
基于上述任一网络侧设备进行数据传输的实施例，较佳地，D2D子帧配置可以是网络侧设备确定并通过***广播消息发送给用户设备的，也可以是网络侧设备确定并通过用户设备的专属信令发送给用户设备的。
本领域内的技术人员应明白，本申请的实施例可提供为方法、***、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (24)

  1. 一种数据传输方法，其特征在于，包括：
    用户设备在时分双工上下行参考配置指示的下行子帧接收蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和设备到设备D2D子帧配置确定的；
    所述用户设备根据基于所述时分双工上下行参考配置的蜂窝下行数据的混合自动重传请求HARQ反馈时序，在所述时分双工上下行参考配置指示的上行子帧进行所述蜂窝下行数据的正确确认/错误确认ACK/NACK反馈，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧不用于所述蜂窝下行数据的ACK/NACK反馈。
  2. 根据权利要求1所述的方法，其特征在于，所述时分双工上下行参考配置是网络侧设备通过***广播消息下发的；或者，
    所述时分双工上下行参考配置是网络侧设备通过所述用户设备的专属信令下发的；或者，
    所述时分双工上下行参考配置是所述用户设备按照与网络侧设备相同的方式确定的。
  3. 根据权利要求1所述的方法，其特征在于，确定所述时分双工上下行参考配置的方式包括：
    将所述蜂窝的时分双工上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧，伪下行子帧不用于蜂窝下行传输；
    如果变化后的时分双工上下行配置为标准规定的时分双工上下行配置i，i属于0～6，则确定时分双工上下行配置i为所述时分双工上下行参考配置；
    如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则从标准规定的时分双工上下行配置中选择一个作为所述时分双工上下行参考配置，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双 工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则定义与标准规定的时分双工上下行配置不同的时分双工上下行配置作为所述时分双工上下行参考配置，并定义基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的时分双工上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
  4. 根据权利要求1～3任一项所述的方法，其特征在于，所述D2D子帧配置是网络侧设备通过***广播消息下发的；或者，
    所述D2D子帧配置是网络侧设备通过所述用户设备的专属信令下发的。
  5. 一种数据传输方法，其特征在于，包括：
    网络侧设备在时分双工上下行参考配置指示的下行子帧发送蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的；
    所述网络侧设备根据基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，在所述时分双工上下行参考配置指示的上行子帧接收所述蜂窝下行数据的ACK/NACK反馈，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧不用于所述蜂窝下行数据的ACK/NACK反馈。
  6. 根据权利要求5所述的方法，其特征在于，所述时分双工上下行参考配置是由所述网络侧设备确定并通过***广播消息发送给用户设备的；或者，
    所述时分双工上下行参考配置是由所述网络侧设备确定并通过用户设备的专属信令发送给所述用户设备的；或者，
    所述时分双工上下行参考配置是所述网络侧设备按照与用户设备相同的方式确定的。
  7. 根据权利要求5所述的方法，其特征在于，确定所述时分双工上下行参考配置的方式包括：
    将所述蜂窝的时分双工上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧，伪下行子帧不用于蜂窝下行传输；
    如果变化后的时分双工上下行配置为标准规定的时分双工上下行配置i，i属于0～6，则确定时分双工上下行配置i为所述时分双工上下行参考配置；
    如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则从标准规定的时分双工上下行配置中选择一个作为所述时分双工上下行参考配置，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则定义与标准规定的时分双工上下行配置不同的时分双工上下行配置作为所述时分双工上下行参考配置，并定义基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的时分双工上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
  8. 根据权利要求5～7任一项所述的方法，其特征在于，所述D2D子帧配置是由网络侧设备确定并通过***广播消息发送给所述用户设备的；或者，
    所述D2D子帧配置是由网络侧设备确定并通过所述用户设备的专属信令发送给所述用户设备的。
  9. 一种用户设备，其特征在于，包括：
    蜂窝数据接收模块，用于在时分双工上下行参考配置指示的下行子帧接收蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的；
    反馈信息发送模块，用于根据基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，在所述时分双工上下行参考配置指示的上行子帧进行所述蜂窝下行数据的ACK/NACK反馈，所述时分双工上下行参考配置 中、与D2D子帧编号相同的子帧不用于所述蜂窝下行数据的ACK/NACK反馈。
  10. 根据权利要求9所述的用户设备，其特征在于，所述时分双工上下行参考配置是网络侧设备通过***广播消息下发的；或者，
    所述时分双工上下行参考配置是网络侧设备通过所述用户设备的专属信令下发的；或者，
    所述时分双工上下行参考配置是所述用户设备按照与网络侧设备相同的方式确定的。
  11. 根据权利要求9所述的用户设备，其特征在于，确定所述时分双工上下行参考配置的方式包括：
    将所述蜂窝的时分双工上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧，伪下行子帧不用于蜂窝下行传输；
    如果变化后的时分双工上下行配置为标准规定的时分双工上下行配置i，i属于0～6，则确定时分双工上下行配置i为所述时分双工上下行参考配置；
    如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则从标准规定的时分双工上下行配置中选择一个作为所述时分双工上下行参考配置，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则定义与标准规定的时分双工上下行配置不同的时分双工上下行配置作为所述时分双工上下行参考配置，并定义基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的时分双工上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
  12. 根据权利要求9～11任一项所述的用户设备，其特征在于，所述D2D 子帧配置是网络侧设备通过***广播消息下发的；或者，
    所述D2D子帧配置是网络侧设备通过所述用户设备的专属信令下发的。
  13. 一种网络侧设备，其特征在于，包括：
    蜂窝数据发送模块，用于在时分双工上下行参考配置指示的下行子帧发送蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的；
    反馈信息接收模块，用于根据基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，在所述时分双工上下行参考配置指示的上行子帧接收所述蜂窝下行数据的ACK/NACK反馈。
  14. 根据权利要求13所述的网络侧设备，其特征在于，所述时分双工上下行参考配置是由所述网络侧设备确定并通过***广播消息发送给用户设备的；或者，
    所述时分双工上下行参考配置是由所述网络侧设备确定并通过用户设备的专属信令发送给所述用户设备的；或者，
    所述时分双工上下行参考配置是所述网络侧设备按照与用户设备相同的方式确定的。
  15. 根据权利要求13所述的网络侧设备，其特征在于，确定所述时分双工上下行参考配置的方式包括：
    将所述蜂窝的时分双工上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧，伪下行子帧不用于蜂窝下行传输；
    如果变化后的时分双工上下行配置为标准规定的时分双工上下行配置i，i属于0～6，则确定时分双工上下行配置i为所述时分双工上下行参考配置；
    如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则从标准规定的时分双工上下行配置中选择一个作为所述时分双工上下行参考配置，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧； 或者，如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则定义与标准规定的时分双工上下行配置不同的时分双工上下行配置作为所述时分双工上下行参考配置，并定义基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的时分双工上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
  16. 根据权利要求13～15任一项所述的网络侧设备，其特征在于，所述D2D子帧配置是由网络侧设备确定并通过***广播消息发送给所述用户设备的；或者，
    所述D2D子帧配置是由网络侧设备确定并通过所述用户设备的专属信令发送给所述用户设备的。
  17. 一种用户设备，其特征在于，包括：收发机、处理器、存储器；
    所述处理器，用于读取所述存储器中的程序，执行下列过程：通过所述收发机在时分双工上下行参考配置指示的下行子帧接收蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的；以及根据基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，通过所述收发机在所述时分双工上下行参考配置指示的上行子帧进行所述蜂窝下行数据的ACK/NACK反馈，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧不用于所述蜂窝下行数据的ACK/NACK反馈。
  18. 根据权利要求17所述的用户设备，其特征在于，所述时分双工上下行参考配置是网络侧设备通过***广播消息下发的；或者，
    所述时分双工上下行参考配置是网络侧设备通过所述用户设备的专属信令下发的；或者，
    所述时分双工上下行参考配置是所述用户设备按照与网络侧设备相同的方式确定的。
  19. 根据权利要求17所述的用户设备，其特征在于，确定所述时分双工上下行参考配置的方式包括：
    将所述蜂窝的时分双工上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧，伪下行子帧不用于蜂窝下行传输；
    如果变化后的时分双工上下行配置为标准规定的时分双工上下行配置i，i属于0～6，则确定时分双工上下行配置i为所述时分双工上下行参考配置；
    如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则从标准规定的时分双工上下行配置中选择一个作为所述时分双工上下行参考配置，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则定义与标准规定的时分双工上下行配置不同的时分双工上下行配置作为所述时分双工上下行参考配置，并定义基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的时分双工上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
  20. 根据权利要求17-19任一项所述的用户设备，其特征在于，所述D2D子帧配置是网络侧设备通过***广播消息下发的；或者，
    所述D2D子帧配置是网络侧设备通过所述用户设备的专属信令下发的。
  21. 一种网络侧设备，其特征在于，包括：收发机、处理器、存储器；
    所述处理器，用于读取存储器中的程序，执行下列过程：通过所述收发机在时分双工上下行参考配置指示的下行子帧发送蜂窝下行数据，所述时分双工上下行参考配置是根据蜂窝的时分双工上下行配置和D2D子帧配置确定的，以及根据基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，通过所述收发机在所述时分双工上下行参考配置指示的上行子帧接 收所述蜂窝下行数据的ACK/NACK反馈。
  22. 根据权利要求21所述的网络侧设备，其特征在于，所述时分双工上下行参考配置是由所述网络侧设备确定并通过***广播消息发送给用户设备的；或者，
    所述时分双工上下行参考配置是由所述网络侧设备确定并通过用户设备的专属信令发送给所述用户设备的；或者，
    所述时分双工上下行参考配置是所述网络侧设备按照与用户设备相同的方式确定的。
  23. 根据权利要求21所述的网络侧设备，其特征在于，确定所述时分双工上下行参考配置的方式包括：
    将所述蜂窝的时分双工上下行配置中、与D2D子帧编号相同的子帧作为伪下行子帧，伪下行子帧不用于蜂窝下行传输；
    如果变化后的时分双工上下行配置为标准规定的时分双工上下行配置i，i属于0～6，则确定时分双工上下行配置i为所述时分双工上下行参考配置；
    如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则从标准规定的时分双工上下行配置中选择一个作为所述时分双工上下行参考配置，所述时分双工上下行参考配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧；或者，如果变化后的时分双工上下行配置与标准规定的时分双工上下行配置均不同，则定义与标准规定的时分双工上下行配置不同的时分双工上下行配置作为所述时分双工上下行参考配置，并定义基于所述时分双工上下行参考配置的蜂窝下行数据的HARQ反馈时序，定义的时分双工上下行配置中、与D2D子帧编号相同的子帧为伪下行子帧，且所述时分双工上下行参考配置中、与所述蜂窝的时分双工上下行配置中的子帧编号相同但传输方向相反的下行子帧为伪下行子帧。
  24. 根据权利要求21-23任一项所述的网络侧设备，其特征在于，所述 D2D子帧配置是由网络侧设备确定并通过***广播消息发送给所述用户设备的；或者，
    所述D2D子帧配置是由网络侧设备确定并通过所述用户设备的专属信令发送给所述用户设备的。
PCT/CN2014/089691 2013-10-31 2014-10-28 一种数据传输方法及设备 WO2015062477A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310533385.3A CN104601300B (zh) 2013-10-31 2013-10-31 一种数据传输方法及设备
CN201310533385.3 2013-10-31

Publications (1)

Publication Number Publication Date
WO2015062477A1 true WO2015062477A1 (zh) 2015-05-07

Family

ID=53003346

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/089691 WO2015062477A1 (zh) 2013-10-31 2014-10-28 一种数据传输方法及设备

Country Status (2)

Country Link
CN (1) CN104601300B (zh)
WO (1) WO2015062477A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110086582A (zh) * 2018-01-26 2019-08-02 中兴通讯股份有限公司 一种信道测量方法和***、第一通信节点及第二通信节点

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102514908B1 (ko) * 2015-12-22 2023-03-28 삼성전자 주식회사 무선 통신 시스템의 d2d 신호 전송 지원을 위한 기지국 동작 방법 및 장치
CN108463962B (zh) * 2016-01-13 2022-05-31 联想创新有限公司（香港) 双向子帧通信
WO2021068159A1 (en) * 2019-10-10 2021-04-15 Qualcomm Incorporated Systems and methods for handling sidelink feedback signaling

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729225A (zh) * 2008-10-16 2010-06-09 中兴通讯股份有限公司 一种传输同步混合自动重传请求反馈数据的方法
CN101771522A (zh) * 2009-01-05 2010-07-07 大唐移动通信设备有限公司 一种发送重复确认或否认反馈的方法、***及用户设备
CN101807983A (zh) * 2009-02-13 2010-08-18 中兴通讯股份有限公司 克服上行混合自动重传请求与突发业务冲突的方法和***
CN102271032A (zh) * 2011-08-09 2011-12-07 电信科学技术研究院 一种实现上行反馈的方法、***及装置
CN103368706A (zh) * 2012-03-26 2013-10-23 中兴通讯股份有限公司 混合自动重传请求传输方法、装置及***

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2604081A4 (en) * 2010-08-12 2016-10-19 Nokia Technologies Oy CONFIGURING AN UPLINK AND DOWNLINK DIVISION DIAGRAM FOR DEVICE (D2D) COMMUNICATION IN A CELLULAR NETWORK
CN103368713B (zh) * 2012-03-26 2017-03-15 中兴通讯股份有限公司 设备到设备的通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729225A (zh) * 2008-10-16 2010-06-09 中兴通讯股份有限公司 一种传输同步混合自动重传请求反馈数据的方法
CN101771522A (zh) * 2009-01-05 2010-07-07 大唐移动通信设备有限公司 一种发送重复确认或否认反馈的方法、***及用户设备
CN101807983A (zh) * 2009-02-13 2010-08-18 中兴通讯股份有限公司 克服上行混合自动重传请求与突发业务冲突的方法和***
CN102271032A (zh) * 2011-08-09 2011-12-07 电信科学技术研究院 一种实现上行反馈的方法、***及装置
CN103368706A (zh) * 2012-03-26 2013-10-23 中兴通讯股份有限公司 混合自动重传请求传输方法、装置及***

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110086582A (zh) * 2018-01-26 2019-08-02 中兴通讯股份有限公司 一种信道测量方法和***、第一通信节点及第二通信节点

Also Published As

Publication number Publication date
CN104601300B (zh) 2018-03-16
CN104601300A (zh) 2015-05-06

Similar Documents

Publication Publication Date Title
JP6951025B2 (ja) ビーム構成方法および装置
RU2631671C2 (ru) Временная шкала harq для tdd-fdd агрегирования несущих
US11622361B2 (en) Mission critical data support in self-contained time division duplex (TDD) subframe structure
EP2932638B1 (en) A network node, a wireless device and methods therein for enabling and performing harq transmissions in a d2d communication between wireless devices in a wireless telecommunications network
CN107682099B (zh) 无线通信中确认时序的选择
JP6061942B2 (ja) 無線通信における肯定応答タイミングの選択
US10904919B2 (en) Information feedback method, base station, terminal and storage medium
TWI577230B (zh) 處理裝置對裝置運作的方法
EP2993818B1 (en) Method, system and device for determining transmission link type
JP2016174371A (ja) プログラム、コンピュータ可読媒体および拡張ノードｂ
WO2014067140A1 (zh) 一种信息传输方法、用户设备及基站
WO2014121687A1 (zh) 一种通信处理方法及装置
US9843420B2 (en) Cross carrier scheduling method and apparatus
WO2017197949A1 (zh) 一种数据传输的控制方法及相关设备
WO2018010497A1 (zh) 一种混合自动重传请求进程处理方法、设备及通信***
US20190207718A1 (en) Information transmission method and device
JP2017077013A (ja) 無線通信における肯定応答タイミングの選択
US10575363B2 (en) Signaling reduction for out-of-sync users
JP2022520255A (ja) フィードバック情報送信方法及び装置
US9042280B2 (en) Methods and apparatus for half duplex scheduling
WO2022029721A1 (en) TIMING ENHANCEMENTS RELATED TO PUCCH REPETITION TOWARDS MULTIPLE TRPs
KR20190056429A (ko) 업 링크 제어 정보(uci)의 전송 방법 및 장치
WO2015062477A1 (zh) 一种数据传输方法及设备
WO2022029711A1 (en) COLLISION AVOIDANCE AND/OR HANDLING OF INVALID SYMBOLS WHEN UTILIZING UPLINK CHANNEL REPETITION TOWARDS MULTIPLE TRPs
CN109565369B (zh) 混合自动重传请求应答捆绑

Legal Events

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

Ref document number: 14857863

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14857863

Country of ref document: EP

Kind code of ref document: A1