WO2021168834A1 - 数据传输方法、装置及设备 - Google Patents

数据传输方法、装置及设备 Download PDF

Info

Publication number
WO2021168834A1
WO2021168834A1 PCT/CN2020/077279 CN2020077279W WO2021168834A1 WO 2021168834 A1 WO2021168834 A1 WO 2021168834A1 CN 2020077279 W CN2020077279 W CN 2020077279W WO 2021168834 A1 WO2021168834 A1 WO 2021168834A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
harq process
type
terminal device
length
Prior art date
Application number
PCT/CN2020/077279
Other languages
English (en)
French (fr)
Inventor
吴作敏
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080079577.XA priority Critical patent/CN114731690A/zh
Priority to PCT/CN2020/077279 priority patent/WO2021168834A1/zh
Publication of WO2021168834A1 publication Critical patent/WO2021168834A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling

Definitions

  • the present invention relates to the field of communication technology, in particular to a data transmission method, device and equipment.
  • Non-terrestrial communication network refers to a communication network between terminal equipment and satellites (also called network equipment).
  • retransmission can be performed through a hybrid automatic repeat request (HARQ) mechanism.
  • HARQ hybrid automatic repeat request
  • the terminal device After the terminal device receives the downlink data corresponding to a HARQ process sent by the network device, the terminal device decodes the downlink data and sends HARQ feedback to the network device according to the decoding result. After the network device receives the HARQ feedback sent by the terminal device, the network device sends the retransmitted data or new data to the terminal device through the HARQ process.
  • the transmission delay between the terminal device and the network device is relatively large, and the number of interactions for data transmission through the HARQ mechanism is relatively large, the efficiency of data transmission through the HARQ mechanism is low.
  • the embodiments of the present application provide a data transmission method, device, and equipment, which improve data transmission efficiency.
  • the embodiments of the present application provide a data transmission method, including:
  • the terminal device receives the downlink control information DCI sent by the network device;
  • the terminal device determines whether to feed back the HARQ process of the hybrid automatic repeat request indicated by the DCI.
  • an embodiment of the present application provides a data transmission method, including:
  • the network device determines the downlink control information DCI of the terminal device
  • the network device sends the DCI to the terminal device, where the DCI is used by the terminal device to determine whether to feed back the HARQ process indicated by the DCI.
  • an embodiment of the present application provides a data transmission device, including a receiving module and a processing module, where:
  • the receiving module is configured to receive downlink control information DCI sent by a network device;
  • the processing module is configured to determine, according to the DCI, whether to feed back the HARQ process of the hybrid automatic repeat request indicated by the DCI.
  • an embodiment of the present application provides a data transmission device, including: a processing module and a sending module, where:
  • the processing module is used to determine the downlink control information DCI of the terminal device
  • the sending module is configured to send the DCI to the terminal device, where the DCI is used by the terminal device to determine whether to feed back the HARQ process indicated by the DCI.
  • an embodiment of the present application provides a terminal device, which is characterized by including: a transceiver, a processor, and a memory;
  • the memory stores computer execution instructions
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the data transmission method according to any one of the first aspect.
  • an embodiment of the present application provides a network device, which is characterized by including: a transceiver, a processor, and a memory;
  • the memory stores computer execution instructions
  • the processor executes the computer-executable instructions stored in the memory, so that the processor executes the data transmission method according to any one of the second aspect.
  • an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the first The data transmission method described in any one of the aspects.
  • an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer-executable instruction, and when the computer-executable instruction is executed by a processor, it is used to implement the first The data transmission method of any one of the two aspects.
  • FIG. 1 is a schematic diagram of HARQ process and RTT provided by an embodiment of this application;
  • 2A is a schematic diagram of the architecture of a communication system provided by an embodiment of this application.
  • 2B is a schematic structural diagram of another communication system provided by an embodiment of this application.
  • FIG. 3 is a schematic diagram of processing a HARQ process of the first type provided by an embodiment of the application
  • FIG. 5 is a schematic flowchart of another data transmission method provided by an embodiment of this application.
  • FIG. 6 is a schematic flowchart of another data transmission method provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of yet another data transmission method provided by an embodiment of the application.
  • FIG. 8 is a schematic flowchart of another data transmission method provided by an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of a data transmission device provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of another data transmission device provided by an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of yet another data transmission device provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • evolution system of NR system LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum, NR-U) system, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, Universal Mobile Telecommunication System (UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, WiFi), next-generation communication (5th-Generation, 5G) system, or other communication systems, etc.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC machine type communication
  • V2V vehicle to vehicle
  • the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) deployment.
  • CA Carrier Aggregation
  • DC dual connectivity
  • SA standalone
  • the embodiment of the application does not limit the applied frequency spectrum.
  • the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum (also referred to as unlicensed spectrum or shared spectrum).
  • the embodiments of this application describe various embodiments in combination with network equipment and terminal equipment.
  • the terminal equipment usually has a wireless transceiver function, which can also be called User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile Station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE User Equipment
  • the terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, and personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, and next-generation communication systems, such as terminal devices in the NR network or Terminal equipment in the public land mobile network (PLMN) network that will evolve in the future.
  • STAION, ST station
  • WLAN Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • land including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • First class can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (AR) ) Terminal equipment, wireless terminals in industrial control, vehicle-mounted terminal equipment, wireless terminals in self-driving (self-driving), wireless terminal equipment in remote medical, and smart grid (smart grid) Wireless terminal equipment, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, wearable terminal equipment, etc.
  • a virtual reality virtual reality
  • AR augmented reality
  • the terminal equipment involved in the embodiments of the present application may also be referred to as a terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station , Remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE agent or UE device, etc.
  • the terminal device can also be fixed or mobile.
  • the terminal device may be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • the network device may be a device used to communicate with mobile devices.
  • the network equipment can be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, or a base station in LTE Evolutional Node B (eNB or eNodeB), or relay station or access point, or in-vehicle equipment, wearable equipment, and network equipment (gNB) in the NR network or network equipment in the future evolved PLMN network, etc.
  • Access Point Access Point
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • eNB LTE Evolutional Node B
  • gNB network equipment
  • the network device may have mobile characteristics, for example, the network device may be a mobile device.
  • the network equipment can be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, or a high elliptical orbit (High Elliptical Orbit, HEO). ) Satellite etc.
  • the network device may also be a base station installed in a location such as land or water.
  • the network equipment provides services for the cell, and the terminal equipment communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell.
  • the cell may be a network
  • the cell corresponding to the device such as a base station).
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: Metro cell, Micro cell, Pico Pico cells, femto cells, etc., these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • Downlink control information For terminal devices with downlink services, the network device can schedule the physical downlink shared channel (PDSCH) transmission for the terminal device through the downlink authorized DCI.
  • the downlink authorized DCI includes physical uplink control channel (PUCCH) resource indication information.
  • the terminal device After the terminal device receives the PDSCH, the terminal device can determine the decoding result (ACK or NACK information) of the PDSCH, and pass the The PUCCH resource feeds back the decoding result to the network device.
  • the DCI format for PDSCH scheduling includes DCI format 1_0, DCI format 1_1, and DCI format 1_2. In the following, the information fields and bit sizes included in the DCI of each DCI format are introduced in conjunction with Table 1, Table 2 and Table 3 respectively.
  • the downlink allocation index, the TPC command of the predetermined PUCCH, the PUCCH resource indication, and the PDSCH to HARQ feedback timing indication information field are used to feed back the HARQ-ACK information corresponding to the PDSCH transmission.
  • the downlink allocation index, the TPC command of the predetermined PUCCH, the PUCCH resource indicator, and the PDSCH-to-HARQ_feedback timing indication information field are used to feed back the HARQ-ACK information corresponding to the PDSCH transmission.
  • the size of most information fields included in DCI can be configured by network equipment through high-level parameters (for example, radio resource control (RRC) signaling) of.
  • RRC radio resource control
  • the number of bits corresponding to the information field in the DCI format is 0, it means that the information field may not be included in the DCI format.
  • the above DCI may include the channel access indication (ChannelAccess-CPext) information field; if the communication between the network device and the terminal device occurs on the licensed spectrum, the above DCI does not include the channel access indication (ChannelAccess-CPext) information area.
  • the network device can schedule physical uplink shared channel (PUSCH) transmission for the terminal device through the uplink authorization DCI.
  • the uplink authorized DCI may include indication information for determining the PUSCH resource, and the terminal device may transmit the PUSCH on the determined PUSCH resource according to the uplink authorized DCI.
  • the DCI format for scheduling PUSCH transmission includes DCI format 0_0, DCI format 0_1, or DCI format 0_2.
  • Hybrid automatic repeat request (HARQ) mechanism The HARQ mechanism is a medium access control (MAC) layer retransmission mechanism. The HARQ mechanism can retransmit data that has been lost or transmitted incorrectly. .
  • the HARQ process includes an uplink HARQ process and a downlink HARQ process, and the uplink HARQ process and the downlink HARQ process are independent of each other.
  • a stop-and-wait protocol (stop-and-wait protocol) is usually used for HARQ retransmission.
  • the sender sends a transport block (TB) through a HARQ process, it stops and waits for the confirmation message sent by the receiver (the confirmation message is used to indicate whether the receiver receives the transmission correctly Block TB).
  • the sender cannot send other TBs to the terminal device through the HARQ process.
  • the receiving end After the receiving end receives a TB corresponding to the HARQ process, the receiving end decodes the TB. If the decoding is successful, the receiving end sends an acknowledgement message (ACK) to the sending end.
  • ACK acknowledgement message
  • the receiving end sends an acknowledgement message (ACK) to the sending end.
  • the sender sends a negative acknowledgement (NACK).
  • NACK negative acknowledgement
  • the sending end receives the ACK information corresponding to the HARQ process
  • the sending end can send other TBs to the receiving end through the HARQ process.
  • the sender receives the NACK corresponding to the HARQ process, or the sender does not receive any response for a long time, the sender can retransmit the TB through the HARQ process.
  • the sending end is a network device
  • the receiving end may be a terminal device.
  • the sending end is a terminal device
  • the receiving end can be a network device or another terminal device.
  • the network device can indicate the maximum number of HARQ processes in uplink and downlink to the terminal device by means of, for example, radio resource control (Radio Resource Control, RRC) signaling semi-static configuration. If the network device does not provide corresponding configuration parameters, the number of downlink HARQ processes may be a default value of 8, for example.
  • the maximum number of HARQ processes supported by each carrier in the uplink can be 16. Among them, each HARQ process corresponds to a HARQ process number (HARQ process number, HPN), and the HARQ process number is also called HARQ ID (Identity, identification).
  • Figure 1 illustrates how the number of HARQ processes and the round-trip transmission time RTT affect the throughput of data transmission.
  • the maximum number of HARQ processes configured by the terminal device is 16.
  • the 16 HARQ processes include HARQ0 to HARQ15, and the 16 HARQ processes can be continuously scheduled within 16ms. Among them, for a HARQ process such as HARQ0, after it is scheduled, the HARQ process HARQ0 is in a stopped state during the data round-trip process and cannot be used to transmit other data. Therefore, the maximum number of HARQ processes in the terminal device shown in Figure 1 is In the scenario of 16, there may be the following situations:
  • the terminal device can always have parallel HARQ processes (one or more of HARQ1 to HARQ15) for data transmission;
  • HARQ0 can be used to transmit data again. Therefore, data can be continuously transmitted on the HARQ entity composed of HARQ0 to HARQ15 without affecting the maximum throughput of the terminal device.
  • the RTT is equal to 16ms and the maximum number of HARQ processes configured for the terminal device is 16, it can be seen that there are always HARQ processes that can transmit service data; however, if the maximum number of HARQ processes configured for the terminal device is less than 16, then When there is service data to be transmitted, it is possible that all HARQ processes are in a state of waiting for feedback from the network equipment, and then no HARQ process is available at this time, which affects the throughput of terminal equipment data transmission.
  • the RTT in the NTN system can reach 600ms.
  • the RTT in the NTN system can reach 600ms.
  • all HARQ processes of the terminal device are in a state of not receiving feedback from the network device, and the terminal device has business data to be transmitted when , There will be no HARQ process available for a long time, which will seriously affect the throughput of terminal equipment data transmission.
  • the number of HARQ processes configured by the terminal device does not match the system RTT, and ultimately the system performance is degraded.
  • an embodiment of the present application proposes a data transmission method.
  • the architecture of the communication system in this application will be described with reference to FIGS. 2A-2B.
  • FIG. 2A is a schematic diagram of the architecture of a communication system provided by an embodiment of this application.
  • a terminal device 201 and a satellite 202 which includes a terminal device 201 and a satellite 202, and wireless communication can be performed between the terminal device 201 and the satellite 202.
  • the network formed between the terminal device 201 and the satellite 202 may also be referred to as NTN.
  • the satellite 202 has the function of a base station, and the terminal device 201 and the satellite 202 can directly communicate with each other. Under the system architecture, the satellite 202 can be referred to as a network device.
  • FIG. 2B is a schematic diagram of the architecture of another communication system provided by an embodiment of this application.
  • FIG. 2B which includes a terminal device 301, a satellite 302, and a base station 303.
  • the terminal device 301 and the satellite 302 can communicate wirelessly, and the satellite 302 and the base station 303 can communicate.
  • the network formed between the terminal device 301, the satellite 302, and the base station 303 may also be referred to as NTN.
  • the satellite 302 does not have the function of a base station, and the communication between the terminal device 101 and the base station 303 needs to be relayed by the satellite 302.
  • the base station 103 can be referred to as a network device.
  • FIGS. 2A-2B are only examples of the systems applicable to this application.
  • the methods shown in the embodiments of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc.
  • the embodiments of this application do not specifically limit this.
  • the embodiments of the present application may include at least part of the following content.
  • the network device in order to improve the data transmission efficiency between the terminal device and the network device, for the downlink HARQ process of the terminal device, can configure or instruct the downlink to the terminal device
  • the HARQ feedback function status corresponding to the HARQ process For example, the HARQ feedback function state corresponding to the downlink HARQ process is configured as the disabled state.
  • the terminal device determines that the HARQ feedback function status corresponding to the downlink HARQ process is in the disabled state, the terminal device is scheduled by the downlink authorization to receive data on the downlink HARQ process, and does not perform the HARQ process according to the downlink authorization. Perform HARQ-ACK information feedback.
  • the network device does not need to wait for the HARQ-ACK information feedback corresponding to the HARQ process, and can continue to schedule other data to the terminal device through the HARQ process, so that the network device does not need to wait, and the data transmission efficiency between the terminal device and the network device is improved.
  • the network device may configure or indicate the HARQ feedback function status corresponding to the uplink HARQ process to the terminal device.
  • the HARQ feedback function state corresponding to the uplink HARQ process is configured as the disabled state.
  • the terminal device determines that the HARQ feedback function status corresponding to the uplink HARQ process is in the disabled state, the terminal device is scheduled to be uplink authorized to send the TB on the uplink HARQ process without waiting for the network device’s feedback for the TB.
  • the uplink HARQ process can be used to transmit another TB again according to the instructions of the network device, which improves the efficiency of data transmission between the terminal device and the network device.
  • the state of the HARQ feedback function corresponding to the downlink HARQ process or the uplink HARQ process of the terminal device may be in the disabled state.
  • the network device may configure the HARQ feedback function state corresponding to part or all of the HARQ process of the terminal device to an enabled state or a non-enabled state.
  • the non-enable state is also called the disabled state.
  • the terminal device needs to send the HARQ-ACK corresponding to the TB to the network device after receiving the transport block TB through the HARQ process Information; or, the terminal device needs to receive feedback from the network device on the TB before it can use the HARQ process again; or, the terminal device needs to perform corresponding HARQ-ACK information feedback according to the DCI that schedules the TB; or, the terminal device passes the schedule according to the schedule
  • the HARQ process transmits the DCI of the first physical channel to send the HARQ-ACK information corresponding to the first physical channel transmitted in the HARQ process to the network device.
  • the terminal device does not need to send the HARQ-ACK corresponding to the TB to the network device after receiving the TB through the HARQ process Information; or, the terminal device can reuse the HARQ process without receiving feedback from the network device on the TB; or, the terminal device does not need to perform corresponding HARQ-ACK information feedback according to the DCI that schedules the TB; or, the terminal device
  • the DCI of the first physical channel is transmitted through the HARQ process without scheduling, and the HARQ-ACK information corresponding to the first physical channel transmitted in the HARQ process is sent to the network device.
  • the HARQ-ACK information includes ACK information or NACK information corresponding to the decoding result of the TB.
  • the terminal device if the HARQ feedback function status corresponding to a HARQ process is enabled, then after the terminal device sends the transport block TB through the HARQ process, it needs to receive feedback from the network device on the TB before it can be used again
  • the HARQ process for example, the HARQ process is used to send a new TB or the TB is sent again; or, the terminal device waits for the network device's feedback of the first physical channel transmitted in the HARQ process.
  • the HARQ feedback function status corresponding to a HARQ process is in the disabled state, it means that after the terminal device sends the TB through the HARQ process, it does not need to receive feedback from the network device on the TB.
  • Use the HARQ process again for example, use the HARQ process to send a new TB or send the TB again); or, the terminal device does not wait for the network device's feedback on the first physical channel transmitted in the HARQ process.
  • the time interval between two uses of the same HARQ process is greater than or equal to the first time length, and/or the time interval between two uses of the same HARQ process may be less than the second time length.
  • the first time length is determined according to the decoding time of the receiving device, and the second time length is determined according to RTT. Wherein, the first time length is less than the second time length.
  • the feedback includes the terminal device sending HARQ-ACK information to the network device.
  • the feedback includes the network device sending HARQ-ACK information to the terminal device, or the network device sending the uplink authorized DCI to the terminal device.
  • the type of HARQ process may include the first type or the second type.
  • the first type of HARQ process may include the HARQ process whose HARQ feedback function state is in the disabled state
  • the second type of HARQ process may include the HARQ process whose HARQ feedback function state is in the enabled state.
  • the first type of HARQ process may also be referred to as a feedback-disabled HARQ process, or an uplink HARQ feedback-disabled HARQ process.
  • the terminal device does not feedback the HARQ process of the first type (it can also be understood that the terminal device does not respond to a scheduling of the HARQ process of the first type). That is, after the network device sends the TB to the terminal device through the HARQ process, the terminal device does not need to send the HARQ process to the network device the corresponding feedback message (ACK or NACK) for this transmission, and the network device can send the TB through the HARQ process, for example,
  • the HARQ process transmits a new TB.
  • the feedback message may include HARQ-ACK information
  • HARQ-ACK may be ACK or NACK.
  • FIG. 3 is a schematic diagram of processing a first type of HARQ process provided by an embodiment of the application.
  • the terminal device includes multiple HARQ processes, and HARQ process 7 of the multiple HARQ processes is the first type of HARQ process.
  • the network device sends the downlink data corresponding to the PDSCH 0 to the terminal device through the HARQ process 7, and the NDI is 0. Since the HARQ process 7 is the first type of HARQ process, after the terminal device receives the downlink data corresponding to the HARQ process 7, the terminal device does not need to send the feedback message of the HARQ process 7 to the network device, and the network device does not need to wait for the terminal device to send the feedback message.
  • the feedback message of the HARQ process 7 can send other data to the terminal device through the HARQ process 7.
  • the network device may send downlink data corresponding to PSDCH 1 to the terminal device through the HARQ process 7 and reverse the NDI to 1, where the reversal of the NDI indicates that the downlink data transmitted through the HARQ process 7 is a new downlink data packet.
  • the network device can continue to send the new downlink data packet corresponding to the PDSCH 2 to the terminal device, and reverse the NDI to 0.
  • the second type of HARQ process may also be referred to as a feedback-enabled (enable) HARQ process, or an uplink HARQ feedback-enabled HARQ process.
  • the terminal device feedbacks the HARQ process of the second type (it can also be understood that the terminal device responds to the HARQ process of the second type). That is, after the network device sends the TB to the terminal device through the HARQ process, the terminal device needs to send the HARQ feedback (ACK or NACK) corresponding to the HARQ process to the network device. After the network device receives the HARQ-ACK, the network device can pass the HARQ The process sends other TBs.
  • the first type of HARQ process may also be referred to as a feedback-disabled HARQ process, or a downlink HARQ feedback-disabled HARQ process.
  • a feedback-disabled HARQ process or a downlink HARQ feedback-disabled HARQ process.
  • the second type of HARQ process may also be referred to as a feedback-enabled (ensble) HARQ process, or a downlink HARQ feedback-enabled HARQ process.
  • a feedback-enabled (ensble) HARQ process or a downlink HARQ feedback-enabled HARQ process.
  • the network device may configure part of the HARQ process in the terminal device as the first type or the disabled state, and the network device may also indicate the type of the HARQ process in the terminal device through the DCI.
  • the efficiency of data transmission between the terminal device and the network device can be improved.
  • FIG. 4 is a schematic flowchart of a data transmission method provided by an embodiment of this application. See Figure 4, which includes:
  • the network device determines the DCI.
  • the network device determines the DCI, and schedules the terminal device to perform downlink reception through the DCI, for example, schedules the terminal device to perform PDSCH reception, where the DCI includes indication information of the HARQ process number corresponding to the downlink transmission.
  • the network device determines the DCI, and schedules the terminal device to perform uplink transmission through the DCI, for example, schedules the terminal device to perform PUSCH transmission, where the DCI includes indication information of the HARQ process number corresponding to the uplink transmission.
  • the network device may determine the DCI corresponding to the type of HARQ process according to the type of the HARQ process to be scheduled by the DCI (the HARQ process indicated by the HARQ process number included in the DCI). For example, the network device determines that the HARQ process to be scheduled by the DCI is a non-enabled HARQ process, so the network device can determine the DCI according to the determined type of the HARQ process.
  • the type of the HARQ process can be configured by the network device.
  • the type of the HARQ process can be the first type or the second type.
  • the network device may pre-configure the type of the HARQ process in the terminal device, or may not pre-configure the type of the HARQ process in the terminal device. If the network device pre-configures the HARQ process type, the network device can determine the HARQ process type according to the pre-configuration. After the network device pre-configures the type of the HARQ process in the terminal device, the network device can also send the configuration to the terminal device. For example, the network device can use RRC signaling, medium access control (medium access control, MAC) control unit (control element, CE) or DCI sends the configuration to the terminal device. Of course, the network device may not send the configuration to the terminal device. If the network device does not pre-configure the type of the HARQ process, the network device can determine the type of the HARQ process corresponding to the DCI when sending the DCI to the terminal device.
  • RRC signaling medium access control (medium access control, MAC) control unit (control element, CE) or DCI sends the configuration to the terminal
  • the network device or the terminal device may determine the first information of the DCI for scheduling the HARQ process of this type according to the type of the configured HARQ process.
  • the first information includes at least one of the following information: the length of the DCI; or, the radio network temporary identifier (RNTI) corresponding to the DCI; or, the search space corresponding to the DCI; or, the aggregation level corresponding to the DCI .
  • RNTI radio network temporary identifier
  • the process of determining the first information by the network device may be different, which is described in the embodiment shown in FIG. 5 to FIG. 8 and will not be repeated here.
  • the network device may configure the HARQ process of the first type to repeatedly transmit N times.
  • the network device may configure the second type of HARQ process as non-repetitive transmission, or the number of repeated transmissions is M.
  • M and N are integers greater than one. M and N can be different.
  • the network device may determine that the configuration parameter of the HARQ process of the first type is the first configuration parameter, and the network device may determine that the configuration parameter of the HARQ process of the second type is the second configuration parameter. Wherein, at least one of the first configuration parameter and the second configuration parameter is different.
  • S402 The network device sends DCI to the terminal device.
  • the terminal device determines the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the DCI.
  • the terminal device determines whether to feed back the HARQ process scheduled by the DCI according to the DCI.
  • the terminal device may determine whether to feed back the HARQ process scheduled by the DCI in the following manner: the terminal device determines the type of the HARQ process according to the DCI, and according to the type of the HARQ process, determines whether to determine the HARQ process scheduled by the DCI according to the DCI Give feedback.
  • the terminal device may determine whether to feed back the HARQ process scheduled by the DCI in the following manner: the terminal device may determine whether to feed back the HARQ process indicated by the DCI according to the first information of the DCI.
  • the first information includes at least one of the following information: the length of the DCI; or, the RNTI corresponding to the DCI; or, the search space corresponding to the DCI; or, the aggregation level corresponding to the DCI.
  • the terminal device may determine the type of the HARQ process according to the first information of the DCI, and determine whether to feed back the HARQ process according to the type of the HARQ process.
  • the type of the HARQ process is the first type or the second type. If the type of the HARQ process is the first type, the terminal device determines not to feed back the HARQ process; or, if the type of the HARQ process is the second type, the terminal device determines to feed back the HARQ process.
  • the terminal device determines the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the DCI.
  • the terminal device may determine the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the first information of the DCI.
  • the first information includes at least one of the following information: the length of the DCI; or, the RNTI corresponding to the DCI; or, the search space corresponding to the DCI; or, the aggregation level corresponding to the DCI.
  • the terminal device may determine the type of the HARQ process according to the first information of the DCI, and determine the HARQ feedback function state corresponding to the HARQ process according to the type of the HARQ process.
  • the HARQ feedback function status corresponding to the HARQ process determined by the terminal device according to the first information is also different, or, when the first information is different, the terminal device determines the HARQ process according to the first information.
  • the different types are described in the embodiments shown in Figs. 5-8, which will not be repeated here.
  • the terminal device may determine the type of the HARQ process indicated by the DCI according to the DCI, and the type of the HARQ process is the first type or the second type. After the terminal device determines the HARQ process type, it can perform other processing according to the HARQ process type.
  • the embodiment of the application does not specifically limit the processing items that the terminal device performs according to the HARQ process.
  • the terminal device determines not to feedback the HARQ process indicated by the DCI according to the DCI, the terminal device does not need to feedback the HARQ process, and the network device does not need to wait for the feedback of the terminal device to pass the HARQ process.
  • the HARQ process transmits other data, which improves the efficiency of data transmission. Further, the terminal device can determine whether it needs to feedback the HARQ process through the DCI, and the network device does not need to send additional signaling to the terminal device, which saves signaling overhead.
  • the terminal device determines whether to feed back the HARQ process according to different first information in conjunction with the embodiments shown in FIG. 5 to FIG. 8.
  • FIG. 5 is a schematic flowchart of another data transmission method provided by an embodiment of the application.
  • the first information is the length of the DCI.
  • the method may include:
  • the network device determines the length of the DCI, and determines the DCI according to the length of the DCI.
  • the network device may determine the length of the DCI according to the type of the HARQ process corresponding to the DCI, and generate the DCI according to the length of the DCI.
  • the network device determines that the length of the corresponding DCI is the first DCI length; or, if the type of the HARQ process is the second type, the network device determines that the length of the corresponding DCI is the second DCI length.
  • the length of the first DCI and the length of the second DCI are not equal.
  • the first DCI length is less than the second DCI length.
  • the DCI does not include at least one of the following information fields: the TPC command of the physical uplink control channel PUCCH, the downlink assignment index (DAI), and the PUCCH resource indicator , PDSCH to HARQ feedback timing indicator, single HARQ-ACK feedback request, PDSCH group indicator, new feedback indicator NFI, trigger feedback group indicator.
  • the DCI includes at least one of the following information fields: PUCCH TPC command, downlink allocation indicator DAI, PUCCH resource indicator, PDSCH to HARQ feedback timing indicator, single HARQ-ACK feedback request, PDSCH group indication, new feedback indication NFI, trigger feedback group indication.
  • the corresponding DCI lengths are different, for example, the first DCI length or the second DCI length.
  • the information field included in the DCI of the first DCI length is at least partially different from the information field included in the DCI of the second DCI length.
  • the DCI format is DCI format 1_0
  • the number of bits in each DCI field (can also be referred to as an information field) in the DCI corresponding to the first DCI length and the second DCI length is as shown in Table 4:
  • the length of the following four DCI fields (can also be referred to as information fields) in the DCI is 0: downlink allocation index, TPC of the predetermined PUCCH Command, PUCCH resource indicator, PDSCH to HARQ feedback timing indicator.
  • the DCI does not include the following four information fields: downlink allocation index, TPC command of the predetermined PUCCH, PUCCH resource indicator, PDSCH to HARQ feedback timing instruct.
  • the DCI format is DCI format 1_1
  • the number of bits in each DCI field (can also be referred to as information field) in the DCI corresponding to the first DCI length and the second DCI length is as shown in Table 5:
  • the length of the DCI is the first DCI length
  • the length of the following eight DCI fields (can also be referred to as information fields) in the DCI is 0: downlink allocation index, TPC of the predetermined PUCCH Command, PUCCH resource indicator, PDSCH to HARQ feedback timing indicator, single HARQ-ACK request, PDSCH group index, new feedback indicator, number of PDSCH groups requested.
  • the DCI does not include the following eight information fields: downlink allocation index, TPC command of the predetermined PUCCH, PUCCH resource indicator, PDSCH to HARQ feedback timing Indication, single HARQ-ACK request, PDSCH group index, new feedback indication, number of PDSCH groups requested.
  • the DCI format is DCI format 1_2
  • the number of bits in each DCI field (also referred to as information field) in the DCI corresponding to the first DCI length and the second DCI length is as shown in Table 6:
  • the length of the DCI is the first DCI length
  • the length of the following four DCI fields (also called information fields) in the DCI is 0: downlink allocation index, TPC of the predetermined PUCCH Command, PUCCH resource indicator, PDSCH-to-HARQ_feedback timing indicator.
  • the DCI does not include the following four information fields: downlink allocation index, predetermined PUCCH TPC command, PUCCH resource indicator, PDSCH-to-HARQ _Feedback timing indication.
  • S502 The network device sends DCI to the terminal device.
  • the terminal device determines the HARQ feedback function state corresponding to the HARQ process scheduled by the DCI according to the length of the DCI.
  • the terminal device may first determine the length of the DCI, and then determine whether to feed back the HARQ process indicated by the DCI according to the length of the DCI.
  • the length of the DCI can be the first DCI length or the second DCI length. If the DCI length is the first DCI length, the terminal device determines not to feedback the HARQ process; or, if the DCI length is the second DCI length, the terminal device Determine to feedback the HARQ process.
  • the terminal device can perform DCI detection (also called PDCCH detection) through different DCI lengths, and determine the DCI length used when DCI is detected as the length of the DCI. For example, if the terminal device detects the DCI according to the first DCI length, it can determine that the length of the DCI is the first DCI length; or, if the terminal device detects the DCI according to the second DCI length, it can determine that the DCI length is the first DCI length. Two DCI length. In the process of PDCCH detection performed by the terminal device, when the length of the DCI is the first DCI length, there are fewer information bits included in the DCI, and the reliability of PDCCH detection can be increased when the same PDCCH transmission resource is used.
  • DCI detection also called PDCCH detection
  • the above detection may be blind detection.
  • the detection is a blind detection as an example for description.
  • the blind detection involved in the following may also be referred to as DCI blind detection or PDCCH blind detection.
  • the terminal device may cause the terminal device to perform blind detection more often.
  • the terminal device may determine the DCI length used for blind detection according to the configuration of the HARQ process of the network device.
  • the DCI length used by the terminal device for blind PDCCH detection includes the first DCI length.
  • the terminal device may not use the second DCI length to perform blind detection, so that the number of blind detection performed by the terminal device is less.
  • the DCI length used by the terminal device for blind PDCCH detection includes the second DCI length.
  • the terminal device may not use the first DCI length to perform blind detection, so that the number of blind detection performed by the terminal device is less.
  • the DCI length used by the terminal device for PDCCH detection includes the first DCI length and the second DCI length.
  • the terminal device may also receive other types of DCI.
  • the terminal device may use other DCI lengths to perform other types. Blind detection of DCI.
  • the DCI length used by the terminal device for blind detection may also be other DCI lengths (DCI lengths other than the first DCI length and the second DCI length).
  • different aggregation levels may be configured for different DCI lengths.
  • the first DCI length is configured to correspond to the first aggregation level
  • the second DCI length is configured to correspond to the second aggregation level
  • the first aggregation level is less than or equal to the second aggregation level. Since the first DCI length is less than the second DCI length, while ensuring the reliability of the same PDCCH transmission, the resources required to transmit the DCI corresponding to the first DCI length are less than the resources required to transmit the DCI corresponding to the second DCI length. Reduce the number of blind PDCCH detections of terminal equipment.
  • the terminal device can further determine whether the type of HARQ process corresponding to DCI is consistent with the type of HARQ process corresponding to the DCI length, if they are consistent , And then determine whether to feed back the HARQ process. If they are inconsistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.
  • the terminal device may determine that the type of the HARQ process indicated by the DCI is the first type according to the first DCI length. The terminal device may further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device may determine not to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • the terminal device can determine that the type of the HARQ process indicated by the DCI is the second type according to the second DCI length.
  • the terminal device may further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • other methods may be: the terminal device determines the HARQ process type through the HARQ process type pre-configured by the network device; or the terminal device may determine the HARQ process through any method in the embodiments of FIG. 6-8.
  • the type of process may be: the terminal device determines the HARQ process type through the HARQ process type pre-configured by the network device; or the terminal device may determine the HARQ process through any method in the embodiments of FIG. 6-8. The type of process.
  • the terminal device can determine whether to feed back the HARQ process indicated by the DCI according to the length of the DCI. If the terminal device determines not to feedback the HARQ process indicated by the DCI, the terminal device does not need to feed back the HARQ process, and the network device does not need to wait for the terminal device's feedback to transmit other data through the HARQ process, which improves the data transmission efficiency. Further, the HARQ process type can be implicitly indicated through the length of the DCI, without adding additional signaling to the DCI, which saves signaling overhead.
  • FIG. 6 is a schematic flowchart of another data transmission method provided by an embodiment of the application.
  • the first information is the RNTI corresponding to the DCI.
  • the method may include:
  • the network device determines the RNTI corresponding to the DCI, and scrambles the DCI according to the RNTI.
  • the network device may determine the RNTI corresponding to the DCI according to the type of the HARQ process indicated by the DCI.
  • the network device determines that the RNTI corresponding to the DCI is the first RNTI; or, if the type of the HARQ process is the second type, the network device determines that the RNTI corresponding to the DCI is the second RNTI.
  • the network device may configure the first RNTI and/or the second RNTI for the terminal device, where the first RNTI is used to scramble the DCI (downlink authorized DCI) corresponding to the HARQ process of the first type, and the second RNTI is used to scramble the second The downlink authorized DCI corresponding to the type of HARQ process.
  • the first RNTI is used to scramble the DCI (downlink authorized DCI) corresponding to the HARQ process of the first type
  • the second RNTI is used to scramble the second The downlink authorized DCI corresponding to the type of HARQ process.
  • the network device may configure the first RNTI for the terminal device.
  • the RNTI configured by the network device for the terminal device includes the first RNTI.
  • the network device may configure the second RNTI for the terminal device.
  • the RNTI configured by the network device for the terminal device includes the second RNTI.
  • the network equipment can configure the first RNTI and the second RNTI for the terminal equipment, in other words, the network equipment is a terminal equipment
  • the configured RNTI includes the first RNTI and the second RNTI.
  • the network device After the network device determines that the DCI and the RNTI corresponding to the DCI are obtained, the network device can scramble the DCI through the RNTI corresponding to the DCI.
  • the length of the DCI generated by the network device may be the first length. If the type of the HARQ process is the second type, the length of the DCI generated by the network device may be the second length. For this process, refer to S501, which will not be repeated here.
  • the network device sends the DCI to the terminal device.
  • the terminal device determines the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the RNTI corresponding to the DCI.
  • the terminal device may first determine the RNTI corresponding to the DCI, and then determine whether to feed back the HARQ process indicated by the DCI according to the RNTI corresponding to the DCI.
  • the RNTI corresponding to the DCI is the first RNTI or the second RNTI. If the RNTI corresponding to the DCI is the first RNTI, the terminal device determines not to feed back the HARQ process, or if the RNTI corresponding to the DCI is the second RNTI, the terminal device determines to The HARQ process provides feedback.
  • the terminal device may perform DCI detection (also called PDCCH detection) through different RNTIs, and determine the RNTI used when the DCI is detected as the RNTI corresponding to the DCI. For example, if the terminal device detects the DCI based on the first RNTI, it can determine that the RNTI corresponding to the DCI is the first RNTI; or, if the terminal device detects the DCI based on the second RNTI, it can determine that the RNTI corresponding to the DCI is the second RNTI. RNTI.
  • the RNTI corresponding to the DCI can be used to determine whether to feed back the HARQ process without adding indication information in the DCI, which not only saves signaling overhead, but also makes PDCCH detection more reliable.
  • the above detection may be blind detection.
  • the detection is a blind detection as an example for description.
  • the terminal device may cause the terminal device to perform blind detection more often.
  • the terminal equipment may determine the RNTI used for the blind detection according to the configuration of the HARQ process of the network equipment.
  • the RNTI used by the terminal equipment for PDCCH detection includes the first RNTI.
  • the terminal device may not use the second RNTI to perform blind detection, so that the number of times the terminal device performs blind detection is less.
  • the RNTI used by the terminal equipment for PDCCH detection includes the second RNTI.
  • the terminal device may not use the first RNTI to perform blind detection, so that the number of blind detection performed by the terminal device is less.
  • the RNTI used by the terminal device for PDCCH detection includes the first RNTI and the second RNTI.
  • the terminal device can further determine whether the type of the HARQ process corresponding to the DCI is consistent with the type of the HARQ process corresponding to the RNTI. Determine whether to give feedback to the HARQ process. If they are not consistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.
  • the terminal device may determine that the type of the HARQ process indicated by the DCI is the first type according to the first RNTI. The terminal device may further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device may determine not to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • the terminal device may determine, according to the second RNTI, that the type of the HARQ process indicated by the DCI is the second type. The terminal device may further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • the terminal device determines the type of HARQ process through the type of HARQ process pre-configured by the network device; or, the terminal device may use any of the embodiments in FIG. 5 and FIG. 7-8.
  • the method determines the type of HARQ process.
  • the terminal device can determine whether to feed back the HARQ process indicated by the DCI according to the RNTI corresponding to the DCI. If the terminal device determines not to feedback the HARQ process indicated by the DCI, the terminal device does not need to feed back the HARQ process, and the network device does not need to wait for the terminal device's feedback to transmit other data through the HARQ process, which improves the data transmission efficiency. Further, the type of HARQ process can be implicitly indicated through the RNTI corresponding to the DCI, and there is no need to add additional signaling in the DCI, which saves signaling overhead.
  • FIG. 7 is a schematic flowchart of yet another data transmission method provided by an embodiment of the application.
  • the first information is the search space corresponding to the DCI.
  • the method may include:
  • the network device determines the DCI and the search space corresponding to the DCI.
  • the network device may determine the search space corresponding to the DCI according to the type of the HARQ process indicated by the DCI.
  • the network device determines that the search space corresponding to the DCI is the first search space; or, if the type of the HARQ process is the second type, the network device determines that the search space corresponding to the DCI is the second search space.
  • the network device may configure the first search space and/or the second search space for the terminal device, where the first search space is used to transmit the DCI (downlink authorized DCI) corresponding to the first type of HARQ process, and the second search space is used for transmission DCI corresponding to the second type of HARQ process.
  • the network device can also configure other search spaces for the terminal device.
  • the network device may configure the first search space for the terminal device.
  • the search space configured by the network device for the terminal device includes the first search space.
  • the network device may configure the second search space for the terminal device.
  • the search space configured by the network device for the terminal device includes the second search space.
  • the network device can configure the first search space and the second search space for the terminal device.
  • the network device is The search space configured by the terminal device includes a first search space and a second search space.
  • the length of the DCI generated by the network device may be the first length. If the type of the HARQ process is the second type, the length of the DCI generated by the network device may be the second length. For this process, refer to S501, which will not be repeated here. And/or, if the type of the HARQ process is the first type, the network device determines that the RNTI corresponding to the DCI may be the first RNTI. If the type of the HARQ process is the second type, the network device determines that the RNTI corresponding to the DCI may be the second RNTI. For this process, refer to S601, which will not be repeated here.
  • the network device sends the DCI to the terminal device through the search space corresponding to the DCI.
  • the network device transmits the DCI through the first search space. If the search space corresponding to the DCI is the second search space, the network device transmits the DCI through the second search space.
  • the terminal device determines the HARQ feedback function state corresponding to the HARQ process scheduled by the DCI according to the search space corresponding to the DCI.
  • the terminal device may first determine the search space corresponding to the DCI, and then determine whether to feed back the HARQ process indicated by the DCI according to the search space corresponding to the DCI.
  • the search space corresponding to the DCI is the first search space or the second search space. If the search space corresponding to the DCI is the first search space, the terminal device determines not to feedback the HARQ process, or if the search space corresponding to the DCI is the second search Space, the terminal device determines to feed back the HARQ process.
  • the terminal device can perform DCI detection (also called PDCCH detection) through different search spaces, and determine the search space used when DCI is detected as the search space corresponding to the DCI. For example, if the terminal device detects the DCI according to the first search space, it can determine that the search space corresponding to the DCI is the first search space; or, if the terminal device detects the DCI according to the second search space, it can determine the DCI corresponding to the DCI.
  • the search space is the second search space.
  • the search space corresponding to the DCI can be used to determine whether to feed back the HARQ process without adding indication information in the DCI, which not only saves signaling overhead, but also makes PDCCH detection more reliable.
  • the above detection may be blind detection.
  • the detection is a blind detection as an example for description.
  • the terminal device may cause the terminal device to perform blind detection more often.
  • the terminal device may determine the search space used for the blind detection according to the configuration of the HARQ process of the network device.
  • the search space used by the terminal device for PDCCH detection includes the first search space.
  • the terminal device may not use the second search space to perform blind detection, so that the number of blind detection performed by the terminal device is less.
  • the search space used by the terminal device for PDCCH detection includes the second search space.
  • the terminal device may not use the first search space to perform blind detection, so that the number of blind detection performed by the terminal device is less.
  • the search space used by the terminal device for PDCCH detection includes the first search space and the second search space.
  • the terminal device can further determine whether the type of the HARQ process corresponding to the DCI is consistent with the type of the HARQ process corresponding to the search space, if they are consistent , And then determine whether to feedback the HARQ process. If they are not consistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.
  • the terminal device can determine that the type of the HARQ process indicated by the DCI is the first type according to the first search space. The terminal device may further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device may determine not to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • the terminal device can determine that the type of the HARQ process indicated by the DCI is the second type according to the second search space.
  • the terminal device may further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • other methods may be: the terminal device determines the type of HARQ process through the type of HARQ process pre-configured by the network device; or, the terminal device may determine the type of HARQ process through any of the embodiments in FIG. 5, FIG. 6 or FIG. The method determines the type of HARQ process.
  • the terminal device can determine whether to feed back the HARQ process indicated by the DCI according to the search space corresponding to the DCI. If the terminal device determines not to feedback the HARQ process indicated by the DCI, the terminal device does not need to feed back the HARQ process, and the network device does not need to wait for the terminal device's feedback to transmit other data through the HARQ process, which improves the data transmission efficiency. Further, the HARQ process type can be implicitly indicated through the search space corresponding to the DCI, without adding additional signaling in the DCI, which saves signaling overhead.
  • FIG. 8 is a schematic flowchart of another data transmission method provided by an embodiment of the application.
  • the first information is the aggregation level corresponding to the DCI.
  • the method may include:
  • the network device determines the DCI and the aggregation level corresponding to the DCI.
  • the network device may determine the aggregation level corresponding to the DCI according to the type of HARQ process indicated by the DCI.
  • the network device determines that the aggregation level corresponding to the DCI is the first aggregation level; or, if the type of the HARQ process is the second type, the network device determines that the aggregation level corresponding to the DCI is the second aggregation grade.
  • the network device may configure the first aggregation level and/or the second aggregation level for the terminal device.
  • the network device can also configure other aggregation levels for the terminal device.
  • the network device can configure the first aggregation level for the terminal device.
  • the aggregation level configured by the network device for the terminal device includes the first aggregation level.
  • the network device may configure the second aggregation level for the terminal device.
  • the aggregation level configured by the network device for the terminal device includes the second aggregation level.
  • the network device can configure the first aggregation level and the second aggregation level for the terminal device.
  • the network device is The aggregation level configured by the terminal device includes a first aggregation level and a second aggregation level.
  • the length of the DCI generated by the network device may be the first length. If the type of the HARQ process is the second type, the length of the DCI generated by the network device may be the second length. For this process, refer to S501, which will not be repeated here. And/or, if the type of the HARQ process is the first type, the network device determines that the RNTI corresponding to the DCI may be the first RNTI. If the type of the HARQ process is the second type, the network device determines that the RNTI corresponding to the DCI may be the second RNTI. For this process, refer to S601, which will not be repeated here.
  • the network device determines that the search space corresponding to the DCI may be the first search space. If the type of the HARQ process is the second type, the network device determines that the search space corresponding to the DCI may be the second search space. This process can be referred to S701, which will not be repeated here
  • the network device sends DCI to the terminal device according to the aggregation level.
  • the terminal device determines the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the aggregation level corresponding to the DCI.
  • the terminal device may first determine the aggregation level corresponding to the DCI, and then determine whether to feed back the HARQ process indicated by the DCI according to the aggregation level corresponding to the DCI.
  • the aggregation level corresponding to the DCI is the first aggregation level or the second aggregation level. If the aggregation level corresponding to the DCI is the first aggregation level, the terminal device determines not to feedback the HARQ process, or if the aggregation level corresponding to the DCI is the second aggregation level Level, the terminal device determines to feed back the HARQ process.
  • the terminal device may perform DCI detection (also called PDCCH detection) through different aggregation levels, and determine the aggregation level used when DCI is detected as the aggregation level corresponding to the DCI. For example, if the terminal device detects the DCI according to the first aggregation level, it can determine that the DCI corresponding to the DCI is the first aggregation level; or if the terminal device detects the DCI according to the second aggregation level, it can determine the DCI corresponding to the DCI.
  • the aggregation level is the second aggregation level. In the above process, the aggregation level corresponding to the DCI can be used to determine whether to feed back the HARQ process without adding indication information in the DCI, which not only saves signaling overhead, but also makes PDCCH detection more reliable.
  • the above detection may be blind detection.
  • the detection is a blind detection as an example for description.
  • the terminal device may cause the terminal device to perform blind detection more often.
  • the terminal device may determine the aggregation level used for the blind detection according to the configuration of the HARQ process of the network device.
  • the aggregation level used by the terminal device for PDCCH detection includes the first aggregation level.
  • the terminal device may not use the second aggregation level to perform blind detection, so that the number of blind detection performed by the terminal device is less.
  • the aggregation level used by the terminal device for PDCCH detection includes the second aggregation level.
  • the terminal device may not use the first aggregation level to perform blind detection, so that the number of blind detection performed by the terminal device is less.
  • the aggregation levels used by the terminal device for PDCCH detection include the first aggregation level and the second aggregation level.
  • the terminal device can further determine whether the type of the HARQ process corresponding to the DCI is consistent with the type of the HARQ process corresponding to the aggregation level, if they are consistent , And then determine whether to feedback the HARQ process. If they are not consistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.
  • the terminal device may determine that the type of the HARQ process indicated by the DCI is the first type according to the first aggregation level. The terminal device may further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device may determine not to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • the terminal device may determine that the type of the HARQ process indicated by the DCI is the second type according to the second aggregation level. The terminal device may further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to feed back the HARQ process. In this way, false alarms of blind DCI detection can be reduced. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device may ignore the scheduling of the DCI, or the terminal device may not receive the PDSCH scheduled by the DCI.
  • other methods may be: the terminal device determines the type of HARQ process through the type of HARQ process pre-configured by the network device; or, the terminal device may determine the HARQ process through any method in the embodiments of FIGS. 5-7.
  • the type of process may be: the terminal device determines the type of HARQ process through the type of HARQ process pre-configured by the network device; or, the terminal device may determine the HARQ process through any method in the embodiments of FIGS. 5-7. The type of process.
  • the terminal device can determine whether to feed back the HARQ process indicated by the DCI according to the aggregation level corresponding to the DCI. If the terminal device determines not to feedback the HARQ process indicated by the DCI, the terminal device does not need to feed back the HARQ process, and the network device does not need to wait for the terminal device's feedback to transmit other data through the HARQ process, which improves the data transmission efficiency. Further, the HARQ process type can be implicitly indicated through the aggregation level corresponding to the DCI, without adding additional signaling in the DCI, which saves signaling overhead.
  • the terminal device after the terminal device receives the DCI sent by the network device, if the DCI indicates to feed back the HARQ process indicated by the DCI, the DCI includes a single HARQ-ACK feedback request.
  • the terminal device sends feedback information corresponding to the HARQ process in the terminal device to the network device, that is, the HARQ feedback codebook may include the first type and the second type HARQ-ACK feedback information corresponding to the HARQ process.
  • the terminal device when the single HARQ-ACK feedback request is not triggered, the terminal device does not send the HARQ-ACK feedback information corresponding to the first type of HARQ process to the network device, that is, the uplink HARQ feedback codebook does not include the first type HARQ-ACK feedback information corresponding to the HARQ process.
  • the terminal device it is also possible to configure more parallel HARQ processes for the terminal device, thereby improving the communication efficiency between the terminal device and the network device. For example, for the NTN system, if 16 HARQ processes are usually configured for the terminal device at present, the number of HARQ processes configured for the terminal device may be greater than 16 in this application.
  • the terminal device receives the DCI sent by the network device, and the DCI is used to indicate the release of semi-persistent scheduling (SPS), and the terminal device determines whether to feed back the DCI according to the DCI .
  • SPS semi-persistent scheduling
  • the network device may schedule the terminal device to perform uplink transmission.
  • the network device may schedule the terminal device to perform uplink transmission through the HARQ process.
  • the terminal device may determine whether to transmit uplink data to the network device through the first HARQ process according to the type of the first HARQ process.
  • the terminal device may first determine whether the terminal device transmits uplink data through the first HARQ process within a preset period of time before the current moment. If the terminal device does not transmit the uplink data through the first HARQ process within the preset time period before the current moment, the terminal device sends the uplink data to the network device through the first HARQ process. If the terminal device transmits uplink data through the first HARQ process within the preset time period before the current moment, the terminal device determines whether to transmit the uplink data to the network device through the first HARQ process according to the type of the first HARQ process.
  • the terminal device transmits uplink data to the network device through the first HARQ process; if the type of the first HARQ process is the second type, the terminal device can ignore the network device That is, the terminal device does not send uplink data to the network device through the first HARQ process.
  • the network equipment when the network equipment schedules the terminal equipment to transmit uplink data through the first type of HARQ process, the network equipment can continuously schedule the terminal equipment to transmit uplink data through the first type of HARQ process, and the terminal equipment through the first type of HARQ process After the HARQ process transmits uplink data, the terminal device does not need to wait for a preset time, and the terminal device can perform uplink data transmission through the first type of HARQ process, which improves the efficiency of data transmission between the terminal device and the network device.
  • FIG. 9 is a schematic structural diagram of a data transmission device provided by an embodiment of the application.
  • the data transmission device 10 can be provided in a terminal device.
  • the data transmission device 10 may include a receiving module 11 and a processing module 12, where:
  • the receiving module 11 is configured to receive downlink control information DCI sent by a network device;
  • the processing module 12 is configured to determine, according to the DCI, whether to feed back the HARQ process of the hybrid automatic repeat request indicated by the DCI.
  • the data transmission device provided in the embodiments of the present application can execute the technical solutions shown in the foregoing method embodiments, and the implementation principles and beneficial effects are similar, and details are not described herein again.
  • processing module 12 is specifically configured to:
  • the DCI According to the first information of the DCI, it is determined whether to feed back the HARQ process indicated by the DCI.
  • the first information includes at least one of the following information:
  • the wireless network device temporary identifier RNTI corresponding to the DCI
  • the aggregation level corresponding to the DCI is the aggregation level corresponding to the DCI.
  • processing module 12 is specifically configured to:
  • the type of the HARQ process is determined, the type of the HARQ process is the first type or the second type, the HARQ process of the first type is an HARQ process for which terminal equipment does not feedback, and the second The type of HARQ process is the HARQ process that the terminal device feedbacks;
  • the type of the HARQ process it is determined whether to feed back the HARQ process indicated by the DCI.
  • processing module 12 is specifically configured to:
  • the type of the HARQ process is the first type, feedback the HARQ process indicated by the DCI;
  • the HARQ process indicated by the DCI is not fed back.
  • the first information is the length of the DCI; the processing module is specifically configured to:
  • the length of the DCI is the first DCI length, it is determined not to feed back the HARQ process; or,
  • the length of the DCI is the second DCI length, it is determined to feed back the HARQ process.
  • the first DCI length is less than the second DCI length.
  • the DCI length is the first DCI length
  • the length of the DCI is the second DCI length.
  • the first DCI length corresponds to a first aggregation level
  • the second DCI length corresponds to a second aggregation level.
  • the first aggregation level is less than or equal to the second aggregation level.
  • the length of the DCI is the first DCI length; the DCI does not include at least one of the following information fields:
  • the TPC command of the physical uplink control channel PUCCH is the TPC command of the physical uplink control channel PUCCH
  • the length of the DCI is the second DCI length; the DCI includes at least one of the following information fields:
  • the HARQ process in the terminal device is configured as the first type, and the DCI length used by the terminal device for PDCCH detection includes the first DCI length.
  • the HARQ process in the terminal device is configured as the second type, and the DCI length used by the terminal device for PDCCH detection includes the second DCI length.
  • some HARQ processes in the terminal device are configured as the first type, and some HARQ processes are configured as the second type, and the DCI length used by the terminal device for PDCCH detection includes the The first DCI length and the second DCI length.
  • the first information is the RNTI corresponding to the DCI; the processing module 12 is specifically configured to:
  • the RNTI corresponding to the DCI is the first RNTI, determine not to feed back the HARQ process; or,
  • the RNTI corresponding to the DCI is the second RNTI, it is determined to feed back the HARQ process.
  • the RNTI corresponding to the DCI is the first RNTI
  • the RNTI corresponding to the DCI is the second RNTI.
  • the HARQ process in the terminal device is configured as a first type, and the RNTI used by the terminal device for PDCCH detection includes the first RNTI.
  • the HARQ process in the terminal device is configured as the second type, and the RNTI used by the terminal device for PDCCH detection includes the second RNTI.
  • part of the HARQ processes in the terminal equipment are configured as the first type, and part of the HARQ processes are configured as the second type, and the RNTI used by the terminal equipment for PDCCH detection includes the first type.
  • the first information is a search space corresponding to the DCI; the processing module is specifically configured to:
  • search space corresponding to the DCI is the first search space, it is determined not to feed back the HARQ process; or,
  • search space corresponding to the DCI is the second search space, it is determined to feed back the HARQ process.
  • the search space corresponding to the DCI is the first search space
  • the search space corresponding to the DCI is the second search space.
  • the HARQ process in the terminal device is configured as the first type, and the search space where the terminal device performs PDCCH detection includes the first search space.
  • the HARQ process in the terminal device is configured as the second type, and the search space where the terminal device performs PDCCH detection includes the second search space.
  • some HARQ processes in the terminal device are configured as the first type, and some HARQ processes are configured as the second type, and the search space for PDCCH detection by the terminal device includes the first type.
  • the first information is the aggregation level corresponding to the DCI; the processing module 12 is specifically configured to:
  • the aggregation level corresponding to the DCI is the first aggregation level, it is determined not to feed back the HARQ process; or,
  • the aggregation level corresponding to the DCI is the second aggregation level, it is determined to feed back the HARQ process.
  • the aggregation level corresponding to the DCI is the first aggregation level
  • the aggregation level corresponding to the DCI is the second aggregation level.
  • the HARQ process in the terminal device is configured as the first type, and the aggregation level of the PDCCH detection performed by the terminal device includes the first aggregation level.
  • the HARQ process in the terminal device is configured as the second type, and the aggregation level of the PDCCH detection performed by the terminal device includes the second aggregation level.
  • some HARQ processes in the terminal device are configured as the first type, and some HARQ processes are configured as the second type, and the aggregation level of the PDCCH detection performed by the terminal device includes the first type.
  • the receiving module 11 is further configured to:
  • the second information includes at least one of the following information:
  • processing module 12 is specifically configured to:
  • the following step is performed: determining whether to indicate to the DCI according to the DCI
  • the hybrid automatic retransmission requests the HARQ process for feedback.
  • processing module 12 is further configured to:
  • the DCI is discarded or the PDSCH corresponding to the DCI is not received.
  • the DCI indicates to feed back the HARQ process indicated by the DCI, and the DCI includes a single HARQ-ACK feedback request.
  • FIG. 10 is a schematic structural diagram of another data transmission device provided by an embodiment of this application. On the basis of the embodiment shown in FIG. 9. Referring to FIG. 10, the data transmission device 10 further includes a sending module 13, wherein:
  • the sending module 13 is configured to send feedback information corresponding to the HARQ process in the terminal device to the network device when the single HARQ-ACK feedback request is triggered.
  • the data transmission device provided in the embodiments of the present application can execute the technical solutions shown in the foregoing method embodiments, and the implementation principles and beneficial effects are similar, and details are not described herein again.
  • FIG. 11 is a schematic structural diagram of another data transmission device provided by an embodiment of the application.
  • the data transmission device 20 can be installed in a network device.
  • the data transmission device 20 may include: a processing module 21 and a sending module 22, where:
  • the processing module 21 is configured to determine the downlink control information DCI of the terminal device
  • the sending module 22 is configured to send the DCI to the terminal device, where the DCI is used by the terminal device to determine whether to feed back the HARQ process indicated by the DCI.
  • the data transmission device provided in the embodiments of the present application can execute the technical solutions shown in the foregoing method embodiments, and the implementation principles and beneficial effects are similar, and details are not described herein again.
  • processing module 21 is specifically configured to:
  • the type of the HARQ process is the first type or the second type
  • the HARQ process of the first type is the HARQ process that the terminal device does not feedback
  • the HARQ process of the second type is the HARQ that the terminal device feedbacks. process.
  • processing module 21 is specifically configured to:
  • the first information of the DCI is determined according to the type of the HARQ process.
  • the first information includes at least one of the following information:
  • the wireless network device temporary identifier RNTI corresponding to the DCI
  • the aggregation level corresponding to the DCI is the aggregation level corresponding to the DCI.
  • the first information is the length of the DCI; the processing module 21 is specifically configured to:
  • the type of the HARQ process is the first type, determine that the length of the DCI is the first DCI length; or,
  • the type of the HARQ process is the second type, it is determined that the length of the DCI is the first DCI length.
  • the first DCI length is less than the second DCI length.
  • the length of the DCI is the first DCI length; the DCI does not include at least one of the following information fields:
  • the TPC command of the physical uplink control channel PUCCH is the TPC command of the physical uplink control channel PUCCH
  • the length of the DCI is the second DCI length; the DCI includes at least one of the following information fields:
  • the first information is the RNTI corresponding to the DCI; the processing module 21 is specifically configured to:
  • the type of the HARQ process is the first type, and it is determined that the RNTI corresponding to the DCI is the first RNTI; or,
  • the type of the HARQ process is the second type, and it is determined that the RNTI corresponding to the DCI is the second RNTI.
  • the first information is a search space corresponding to the DCI; the processing module 21 is specifically configured to:
  • the type of the HARQ process is the first type, and it is determined that the search space corresponding to the DCI is the first search space; or,
  • the type of the HARQ process is the second type, and it is determined that the search space corresponding to the DCI is the second search space.
  • the first information is the aggregation level corresponding to the DCI; the processing module 21 is specifically configured to:
  • the type of the HARQ process is the first type, and the network device determines that the aggregation level corresponding to the DCI is the first aggregation level; or,
  • the type of the HARQ process is the second type, and the network device determines that the aggregation level corresponding to the DCI is the second aggregation level.
  • the data transmission device provided in the embodiments of the present application can execute the technical solutions shown in the foregoing method embodiments, and the implementation principles and beneficial effects are similar, and details are not described herein again.
  • FIG. 12 is a schematic structural diagram of a terminal device provided by an embodiment of the application.
  • the terminal device 30 may include: a transceiver 31, a memory 32, and a processor 33.
  • the transceiver 31 may include: a transmitter and/or a receiver.
  • the transmitter can also be referred to as a transmitter, a transmitter, a transmitting port, or a transmitting interface
  • the receiver can also be referred to as a receiver, a receiver, a receiving port, or a receiving interface, and other similar descriptions.
  • the transceiver 31, the memory 32, and the processor 33 are connected to each other through a bus 34.
  • the memory 32 is used to store program instructions
  • the processor 33 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 30 to execute any of the above-mentioned data transmission methods.
  • the receiver of the transceiver 31 can be used to perform the receiving function of the terminal device in the above-mentioned data transmission method.
  • the transmitter of the transceiver 31 can be used to perform the sending function of the terminal device in the above-mentioned data transmission method.
  • the terminal device provided in the embodiment of the present application can execute the technical solution shown in the foregoing method embodiment, and its implementation principles and beneficial effects are similar, and details are not described herein again.
  • FIG. 13 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • the network device 40 may include: a transceiver 41, a memory 42, and a processor 43.
  • the transceiver 41 may include: a transmitter and/or a receiver.
  • the transmitter can also be referred to as a transmitter, a transmitter, a transmitting port, or a transmitting interface
  • the receiver can also be referred to as a receiver, a receiver, a receiving port, or a receiving interface, and other similar descriptions.
  • the transceiver 41, the memory 42, and the processor 43 are connected to each other through a bus 44.
  • the memory 42 is used to store program instructions
  • the processor 43 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 30 to execute any of the above-mentioned data transmission methods.
  • the transmitter of the transceiver 41 can be used to perform the sending function of the network device in the above-mentioned data transmission method.
  • the network device provided in the embodiments of the present application can execute the technical solutions shown in the foregoing method embodiments, and the implementation principles and beneficial effects are similar, and details are not described herein again.
  • An embodiment of the present application provides a computer-readable storage medium that stores a computer-executable instruction, and when the computer-executable instruction is executed by a processor, it is used to implement the above-mentioned data transmission method.
  • the implementation principle and beneficial effects are similar, and will not be repeated here.
  • the embodiments of the present application may also provide a computer program product, which can be executed by a processor, and when the computer program product is executed, it can implement the data transmission method executed by any of the above-mentioned terminal devices.
  • a computer program product which can be executed by a processor, and when the computer program product is executed, it can implement the data transmission method executed by any of the above-mentioned terminal devices.
  • the implementation principle and beneficial effects are similar, and will not be repeated here.
  • An embodiment of the present application provides a system on a chip or a system chip, the system on a chip or a system chip may be applied to a terminal device, and the system on a chip or a system chip includes: at least one communication interface, at least one processor, and at least one The memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the base station can execute the above-mentioned data transmission method.
  • the embodiment of the present application provides a system on a chip or a system chip.
  • the system on a chip or a system chip may be applied to a network device.
  • the system on a chip or the system chip includes: at least one communication interface, at least one processor, and at least one
  • the memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the base station can execute the above-mentioned data transmission method.
  • All or part of the steps in the foregoing method embodiments may be implemented by a program instructing relevant hardware.
  • the aforementioned program can be stored in a readable memory.
  • the program executes the steps that include the foregoing method embodiments; and the foregoing memory (storage medium) includes: read-only memory (English: read-only memory, abbreviation: ROM), RAM, flash memory, hard disk, Solid state hard disk, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.
  • These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing equipment can be used to generate It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • the term “including” and its variations may refer to non-limiting inclusion; the term “or” and its variations may refer to “and/or”.
  • the terms “first”, “second”, etc. in this application are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence.
  • “plurality” means two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects before and after are in an "or” relationship.

Landscapes

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

Abstract

本申请实施例提供一种数据传输方法、装置及设备,该方法包括:终端设备接收网络设备发送的下行控制信息DCI;所述终端设备根据所述DCI,确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。提高了网络设备和终端设备之间的数据传输效率。

Description

数据传输方法、装置及设备 技术领域
本发明涉及通信技术领域,尤其涉及一种数据传输方法、装置及设备。
背景技术
非地面通信网络(non-terrestrial network,NTN)是指终端设备和卫星(还可以称为网络设备)之间的通信网络。
在NTN系统中,可以通过混合自动重传请求(hybrid automatic repeat request,HARQ)机制进行重传。在HARQ机制中,在终端设备接收到网络设备发送的一个HARQ进程对应的下行数据之后,终端设备对下行数据进行译码,并根据译码结果向网络设备发送HARQ反馈。在网络设备接收到终端设备发送的HARQ反馈之后,网络设备才通过该HARQ进程向终端设备发送重传的数据或者新的数据。然而,由于终端设备和网络设备之间的传输时延较大,且通过HARQ机制进行数据传输的交互次数较多,导致通过HARQ机制进行数据传输的效率较低。
发明内容
本申请实施例提供一种数据传输方法、装置及设备,提高了数据传输效率。
第一方面,本申请实施例提供种数据传输方法,包括:
终端设备接收网络设备发送的下行控制信息DCI;
所述终端设备根据所述DCI,确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
第二方面,本申请实施例提供一种数据传输方法,包括:
网络设备确定终端设备的下行控制信息DCI;
所述网络设备向所述终端设备发送所述DCI,所述DCI用于所述终端设备确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
第三方面,本申请实施例提供一种数据传输装置,包括接收模块和处理模块,其中,
所述接收模块用于,接收网络设备发送的下行控制信息DCI;
所述处理模块用于,根据所述DCI,确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
第四方面,本申请实施例提供一种数据传输装置,包括:处理模块和发送模块,其中,
所述处理模块用于,确定终端设备的下行控制信息DCI;
所述发送模块用于,向所述终端设备发送所述DCI,所述DCI用于所述终端设备确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
第五方面,本申请实施例提供一种终端设备,其特征在于,包括:收发器、处理器、存储器;
所述存储器存储计算机执行指令;
所述处理器执行所述存储器存储的计算机执行指令,使得所述处理器执行如第一方面任一项所述的数据传输方法。
第六方面,本申请实施例提供一种网络设备,其特征在于,包括:收发器、处理器、存储器;
所述存储器存储计算机执行指令;
所述处理器执行所述存储器存储的计算机执行指令,使得所述处理器执行如第二方面任一项所述的数据传输方法。
第七方面,本申请实施例提供一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有计算机执行指令,当所述计算机执行指令被处理器执行时用于实现第一方面任一项所述的数据传输方法。
第八方面,本申请实施例提供一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有计算机执行指令,当所述计算机执行指令被处理器执行时用于实现第二方面任一项所述的数据传输方法。
附图说明
图1为本申请实施例提供的HARQ进程与RTT的示意图;
图2A为本申请实施例提供的一种通信系统的架构示意图;
图2B为本申请实施例提供的另一种通信系统的架构示意图;
图3为本申请实施例提供的对第一类型的HARQ进程进行处理的示意图;
图4为本申请实施例提供的一种数据传输方法的流程示意图;
图5为本申请实施例提供的另一种数据传输方法的流程示意图;
图6为本申请实施例提供的又一种数据传输方法的流程示意图;
图7为本申请实施例提供的再一种数据传输方法的流程示意图;
图8为本申请实施例提供的另一种数据传输方法的流程示意图;
图9为本申请实施例提供的一种数据传输装置的结构示意图;
图10为本申请实施例提供的另一种数据传输装置的结构示意图;
图11为本申请实施例提供的又一种数据传输装置的结构示意图;
图12为本申请实施例提供的终端设备的结构示意图;
图13为本申请实施例提供的网络设备的结构示意图。
具体实施方式
为了便于理解,首先,对本申请所涉及的概念进行说明。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(Global System of Mobile communication,GSM)系统、码分多址(Code Division Multiple Access,CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)系统、通用分组无线业务 (General Packet Radio Service,GPRS)、长期演进(Long Term Evolution,LTE)系统、先进的长期演进(Advanced long term evolution,LTE-A)系统、新无线(New Radio,NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum,LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum,NR-U)系统、非地面通信网络(Non-Terrestrial Networks,NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、无线局域网(Wireless Local Area Networks,WLAN)、无线保真(Wireless Fidelity,WiFi)、下一代通信(5th-Generation,5G)系统或其他通信系统等。
通常来说,传统的通信系统支持的连接数有限,也易于实现,然而,随着通信技术的发展,移动通信系统将不仅支持传统的通信,还将支持例如,设备到设备(Device to Device,D2D)通信,机器到机器(Machine to Machine,M2M)通信,机器类型通信(Machine Type Communication,MTC),以及车辆间(Vehicle to Vehicle,V2V)通信,或车联网V2X通信等,本申请实施例也可以应用于这些通信系统。
可选地,本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation,CA)场景,也可以应用于双连接(Dual Connectivity,DC)场景,还可以应用于独立(Standalone,SA)布网场景。
本申请实施例对应用的频谱并不限定。例如,本申请实施例可以应用于授权频谱,也可以应用于非授权频谱(也称为免授权频谱或共享频谱)。
本申请实施例结合网络设备和终端设备描述了各个实施例,其中:终端设备通常具有无线收发功能,也可以称为用户设备(User Equipment,UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。终端设备可以是WLAN中的站点(STAION,ST),可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统,例如,NR网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)网络中的终端设备等。
在本申请实施例中,终端设备可以部署在陆地上,包括室内或室外、手持、穿戴或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中,终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality,简称VR)终端设备、增强现实(augmented reality,简称AR)终端设备、工业控制(industrial control)中的无线终端、车载终端设备、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备、可穿戴终端设备等。本申请实施例所涉及的终端设备还可以称为终端、用户设备(user equipment,UE)、接入终端设备、车载终端、工业控制终端、UE单元、UE站、移动站、移动台、远方站、远程终端设备、移动设备、UE终端设备、无线通信设备、UE代理或UE装置等。终端设备也可以是固定的或者移动的。
作为示例而非限定,在本申请实施例中,该终端设备可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能首饰等。
网络设备可以是用于与移动设备通信的设备。网络设备可以是WLAN中的接入点(Access Point,AP),GSM或CDMA中的基站(Base Transceiver Station,BTS),也可以是WCDMA中的基站(NodeB,NB),还可以是LTE中的演进型基站(Evolutional Node B,eNB或eNodeB),或者中继站或接入点,或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备等。
在本申请实施例中,网络设备可以具有移动特性,例如,网络设备可以为移动的设备。可选地,网络设备可以为卫星、气球站。例如,卫星可以为低地球轨道(low earth orbit,LEO)卫星、中地球轨道(medium earth orbit,MEO)卫星、地球同步轨道(geostationary earth orbit,GEO)卫星、高椭圆轨道(High Elliptical Orbit,HEO)卫星等。可选地,网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中,网络设备为小区(Cell)提供服务,终端设备通过该小区使用的传输资源(例如,频域资源,或者说,频谱资源)与网络设备进行通信,该小区可以是网络设备(例如基站)对应的小区,小区可以属于宏基站,也可以属于小小区(Small cell)对应的基站,这里的小小区可以包括:城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等,这些小小区具有覆盖范围小、发射功率低的特点,适用于提供高速率的数据传输服务。
应理解,本文中术语“系统”和“网络”在本文中常可互换使用。本文中术语“和/或”用来描述关联对象的关联关系,例如表示前后关联对象可存在三种关系,举例说明,A和/或B,可以表示:单独存在A、同时存在A和B、单独存在B这三种情况。本文中字符“/”一般表示前后关联对象是“或”的关系。
为了更好地描述本申请实施例的原理和具体实施方式,以下对本申请实施例的相关技术内容进行描述。
下行控制信息(downlink control information,DCI):对于有下行业务的终端设备,网络设备可以通过下行授权DCI为终端设备调度物理下行共享信道(physical downlink shared channel,PDSCH)的传输。下行授权DCI中包括物理上行控制信道(physical uplink control channel,PUCCH)资源的指示信息,终端设备在收到PDSCH后,终端设备可以确定该PDSCH的译码结果(ACK或NACK信息),并通过该PUCCH资源将译码结果反馈给网络设备。在NR系统中,PDSCH调度的DCI格式包括DCI格式1_0,DCI格式1_1,DCI格式1_2。下面,分别结合表1、表2和表3介绍每种DCI格式的DCI中包括的信息域以及比特大小。
表1
Figure PCTCN2020077279-appb-000001
在表1中,下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH到HARQ反馈定时指示信息域用于反馈PDSCH传输对应的HARQ-ACK信息。
表2
Figure PCTCN2020077279-appb-000002
Figure PCTCN2020077279-appb-000003
在表2中,下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH到HARQ反馈定时指示、单次HARQ-ACK请求、PDSCH群索引、新反馈指示、请求的PDSCH组数信息域用于反馈PDSCH传输对应的HARQ-ACK信息。
表3
Figure PCTCN2020077279-appb-000004
Figure PCTCN2020077279-appb-000005
在表3中,下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH-to-HARQ_反馈定时指示信息域用于反馈PDSCH传输对应的HARQ-ACK信息。
在上述表2-表3中,对于DCI格式1_1和DCI格式1_2,DCI中包括的多数信息域的大小可以是网络设备通过高层参数(例如无线资源控制(radio resource control,RRC)信令)配置的。例如,DCI格式中的信息域对应的比特数为0时,表示该DCI格式中可以不包括该信息域。
在上述表1-表3中,若网络设备和终端设备之间的通信传输是发生在共享频谱上(例如,非授权频谱上),或者终端设备通过非授权频谱上的资源发送PUCCH时,上述DCI中可以包括信道接入指示(ChannelAccess-CPext)信息域;若网络设备和终端设备之间的通信传输是发生在授权频谱上时,上述DCI中不包括信道接入指示(ChannelAccess-CPext)信息域。
对于有上行业务的终端设备,网络设备可以通过上行授权DCI为终端设备调度物理上行共享信道(physical uplink shared channel,PUSCH)的传输。上行授权DCI中可以包括确定PUSCH资源的指示信息,终端设备可以根据上行授权DCI在该确定的PUSCH资源上传输PUSCH。在NR系统中,调度PUSCH传输的DCI格式包括DCI格式0_0,DCI格式0_1,或DCI格式0_2。
混合自动重传请求(hybrid automatic repeat request,HARQ)机制:HARQ机制为媒体接入控制(medium access control,MAC)层的重传机制,通过HARQ机制可以对传输丢失或者传输出错的数据进行重传。HARQ进程包括上行HARQ进程和下行HARQ进程,上行HARQ进程和下行HARQ进程相互独立。
在相关技术中(例如NR系统中),通常采用停等协议(stop-and-wait protocol)进行HARQ重传。在采用等停协议进行HARQ重传时,发送端通过一个HARQ进程发送传输块(transport block,TB)以后,就停下来等待接收端发送的确认信息(确认信息用于指示接收端是否正确接收传输块TB),在该等待的过程中,发送端无法通过该HARQ进程向终端设备发送其它TB。在接收端接收到一个HARQ进程对应的TB以后,接收端对TB进行译码,若译码成功,则接收端向发送端发送肯定应答确认信息(ACK),若译码失败,则接收端向发送端发送否定应答确认信息(NACK)。若发送端接收到HARQ进程对应的ACK信息,则发送端可以通过该HARQ进程向接收端发送其它TB。若发送端接收到HARQ进程对应的NACK,或者发送端长时间内未接收到任何响应,则发送端可以通过该HARQ进程重传TB。在上述过程中,当发送端为网络设备时,接收端可以为终端设备。当发送端为终端设备时,接收端可 以为网络设备或另一终端设备。
在相关技术中,网络设备可以通过例如无线资源控制(Radio Resource Control,RRC)信令半静态配置等方式向终端设备指示上下行最大的HARQ进程数。如果网络设备未提供相应的配置参数,则下行的HARQ进程数可以为缺省值例如为8。上行每个载波支持的最大HARQ进程数可以为16。其中,每个HARQ进程对应一个HARQ进程号(HARQ process number,HPN),HARQ进程号也称为HARQ ID(Identity,标识)。
图1以下行传输为例,对HARQ进程数和往返传输时间RTT如何影响数据传输的吞吐量进行说明。如图1所示,终端设备被配置的最大HARQ进程数为16,16个HARQ进程包括HARQ0至HARQ15,16个HARQ进程可在16ms内被连续调度。其中,对于一个HARQ进程例如HARQ0,其被调度后,在数据往返过程中该HARQ进程HARQ0处于停等状态,不能用于传输其他数据,因此,在图1所示的终端设备最大HARQ进程数为16的场景中,可能存在以下几种情况:
如果RTT小于16ms,在HARQ0被调度后的RTT范围内,在有业务数据要传输时,该终端设备总是可以有并行的HARQ进程(HARQ1至HARQ15中的一个或多个)来进行数据传输;在HARQ0被调度后的时间超过RTT时,HARQ0可再次用于传输数据。因此,数据可以在由HARQ0至HARQ15构成的HARQ实体上连续传输,不影响该终端设备的最大吞吐量。另外,如果RTT等于16ms,且终端设备被配置的最大HARQ进程数为16,同理可知,总是有HARQ进程可传输业务数据;但是,如果终端设备被配置的最大HARQ进程数小于16,则在有业务数据要传输时,有可能所有HARQ进程都处于等待网络设备反馈的状态,则此时没有HARQ进程可用,影响终端设备数据传输的吞吐量。
如果RTT远大于16ms,例如NTN系统中的RTT可达600ms,实际中可能的情况是:终端设备的所有HARQ进程都处于未收到网络设备反馈的状态,则终端设备在有业务数据待传输时,将在很长时间内没有HARQ进程可用,严重影响终端设备数据传输的吞吐量。
也就是说,在NTN系统的应用场景或类似的其他场景中,由于RTT大幅增大,导致终端设备配置的HARQ进程数与系统RTT不匹配,最终导致系统性能下降。
为了解决上述技术问题,本申请实施例提出一种数据传输方法,为了便于理解本申请所示的数据传输方法,首先,结合图2A-图2B,对本申请中的通信系统的架构进行说明。
图2A为本申请实施例提供的一种通信系统的架构示意图。请参见图2A,包括终端设备201和卫星202,终端设备201和卫星202之间可以进行无线通信。终端设备201和卫星202之间所形成的网络还可以称为NTN。在图1所示的通信系统的架构中,卫星202具有基站的功能,终端设备201和卫星202之间可以直接通信。在系统架构下,可以将卫星202称为网络设备。
图2B为本申请实施例提供的另一种通信系统的架构示意图。请参见图2B,包括终端设备301、卫星302和基站303,终端设备301和卫星302之间可以进行无线通信,卫星302与基站303之间可以通信。终端设备301、卫星302和基站303之间所形成的网络还可以称为NTN。在图2所示的通信系统的架构中,卫星302不具有基站的功能,终端设备101和基站303之间的通信需要通过卫星302的中转。在该种系统架构下,可以将基站103称为网络设备。
需要说明的是,图2A-图2B只是以示例的形式示意本申请所适用的系统,当然,本申请实施例所示的方法还可以适用于其它系统,例如,5G通信系统、LTE通信系统等,本申请实施例对此不作具体限定。本申请实施例可以包括下述内容中的至少部分内容。
在本申请中,在RTT较大的场景(例如NTN)下,为了提高终端设备和网络设备之间的数据传输效率,针对终端设备的下行HARQ进程,网络设备可以向终端设备配置或指示该下行HARQ进程对应的HARQ反馈功能状态。例如,将下行HARQ进程对应的HARQ反馈功能状态配置为非使能态。相应的,若终端设备确定该下行HARQ进程对应的HARQ反馈功能状态为非使能态,则终端设备被下行授权调度在该下行HARQ进程上接收到数据后,不根据该下行授权对该HARQ进程进行HARQ-ACK信息反馈。网络设备也无须等待该HARQ进程对应的HARQ-ACK信息反馈,即可通过该HARQ进程继续向终端设备调度其他数据,使得网络设备无需等待,提高了终端设备和网络设备之间的数据传输效率。
或者,针对终端设备的上行HARQ进程,网络设备可以向终端设备配置或指示该上行HARQ进程对应的HARQ反馈功能状态。例如,将上行HARQ进程对应的HARQ反馈功能状态配置为非使能态。相应的,若终端设备确定该上行HARQ进程对应的HARQ反馈功能状态为非使能态,则终端设备被上行授权调度在该上行HARQ进程上发送TB后,无需等待网络设备的反馈针对该TB的反馈,即可根据网络设备的指示再次使用该上行HARQ进程传输另一TB,提高了终端设备和网络设备之间的数据传输效率。
在本申请中,终端设备的下行HARQ进程或上行HARQ进程对应的HARQ反馈功能状态可以为非使能态。例如,网络设备可以将终端设备的部分或全部HARQ进程对应的HARQ反馈功能状态配置为使能态或者非使能态。其中,非使能态也称为去使能态(disabled)。
可选地,对于下行HARQ进程,若一个HARQ进程对应的HARQ反馈功能状态为使能态,那么终端设备通过该HARQ进程接收到传输块TB后,需要向网络设备发送该TB对应的HARQ-ACK信息;或,终端设备需要收到网络设备对该TB的反馈才能再次使用该HARQ进程;或,终端设备需要根据调度该TB的DCI进行对应的HARQ-ACK信息反馈;或,终端设备根据调度通过该HARQ进程传输第一物理信道的DCI向网络设备发送该HARQ进程中传输的第一物理信道对应的HARQ-ACK信息。
可选地,对于下行HARQ进程,若一个HARQ进程对应的HARQ反馈功能状态为非使能态,那么终端设备通过该HARQ进程接收到TB后,不需要向网络设备发送该TB对应的HARQ-ACK信息;或,终端设备不需要收到网络设备对该TB的反馈就可以再次使用该HARQ进程;或,终 端设备不需要根据调度该TB的DCI进行对应的HARQ-ACK信息反馈;或,终端设备不根据调度通过该HARQ进程传输第一物理信道的DCI,向网络设备发送该HARQ进程中传输的第一物理信道对应的HARQ-ACK信息。
可选地,在本申请中,HARQ-ACK信息包括TB的译码结果对应的ACK信息或NACK信息。
可选地,对于上行HARQ进程,若一个HARQ进程对应的HARQ反馈功能状态为使能态,那么终端设备通过该HARQ进程发送传输块TB后,需要收到网络设备对该TB的反馈才能再次使用该HARQ进程(例如使用该HARQ进程发送新的TB或再次发送该TB);或,终端设备等待网络设备对该HARQ进程中传输的第一物理信道的反馈。
可选地,对于上行HARQ进程,若一个HARQ进程对应的HARQ反馈功能状态为非使能态,则说明终端设备通过该HARQ进程发送TB后,不需要收到网络设备对该TB的反馈就可以再次使用该HARQ进程(例如使用该HARQ进程发送新的TB或再次发送该TB);或,终端设备不等待网络设备对该HARQ进程中传输的第一物理信道的反馈。
可选地,同一个HARQ进程两次被使用之间的时间间隔大于或等于第一时间长度,和/或,同一个HARQ进程两次被使用之间的时间间隔可以小于第二时间长度。其中,第一时间长度是根据接收设备的译码时间确定的,第二时间长度是根据RTT确定的。其中,第一时间长度小于第二时间长度。
可选地,对于下行传输,反馈包括终端设备向网络设备发送HARQ-ACK信息。
可选地,对于上行传输,反馈包括网络设备向终端设备发送HARQ-ACK信息,或网络设备向终端设备发送上行授权DCI。
可选地,HARQ进程的类型可以包括第一类型或者第二类型。其中,第一类型的HARQ进程可以包括HARQ反馈功能状态为非使能态的HARQ进程,第二类型的HARQ进程可以包括HARQ反馈功能状态为使能态的HARQ进程。
可选地,针对下行过程:
第一类型的HARQ进程还可以称为反馈去使能(disabled)的HARQ进程,或者上行HARQ反馈去使能的HARQ进程。终端设备不对第一类型的HARQ进程进行反馈(还可以理解为终端设备不响应第一类型的HARQ进程的一次调度)。即,网络设备通过HARQ进程向终端设备发送TB之后,终端设备无需向网络设备发送该HARQ进程该次传输对应的反馈消息(ACK或者NACK),网络设备即可通过该HARQ进程发送TB,例如通过该HARQ进程传输新的TB。其中,反馈消息可以包括HARQ-ACK信息,HARQ-ACK可以为ACK或者NACK。
下面,结合图3,对第一类型的HARQ进程进行说明。
图3为本申请实施例提供的对第一类型的HARQ进程进行处理的示意图。请参见图3,假设终端设备中包括多个HARQ进程,该多个HARQ进程中的HARQ进程7为第一类型的HARQ进程。网络设备通过HARQ进程7向终端设备发送PDSCH 0对应的下行数据,且NDI为0。由于HARQ进程7为第一类型的HARQ进程,因此,终端设备接收到HARQ进程7对应的下行数据之后,终端设备无需向网络设备发送HARQ进程7的反馈消息,网络设备也无需等待终端设备发送的HARQ进程7的反馈消息,即可通过HARQ进程7向终端设备发送其它数据。例如,网络设备可以通过HARQ进程7向终端设备发送PSDCH 1对应的下行数据,且将NDI翻转为1,其中,对NDI进行翻转说明通过该HARQ进程7传输的下行数据为新的下行数据包。在网络设备向终端设备发送PDSCH 1对应的下行数据之后,网络设备可以继续向终端设备发送PDSCH 2对应的新的下行数据包,且将NDI翻转为0。
第二类型的HARQ进程还可以称为反馈使能(enable)的HARQ进程,或者上行HARQ反馈使能的HARQ进程。终端设备对第二类型的HARQ进程进行反馈(还可以理解为终端设备响应第二类型的HARQ进程)。即,网络设备通过HARQ进程向终端设备发送TB之后,终端设备需要向网络设备发送该HARQ进程对应的HARQ反馈(ACK或者NACK),网络设备接收到HARQ-ACK之后,网络设备才可以通过该HARQ进程发送其它TB。
可选地,针对上行过程:
第一类型的HARQ进程还可以可以称为反馈去使能(disabled)的HARQ进程,或者下行HARQ反馈去使能的HARQ进程。在终端设备通过第一类型的HARQ进程向网络设备发送上行数据之后的预设时长之内例如在RTT时长之内,若网络设备再次调度终端设备通过该HARQ进程进行上行数据传输时,则终端设备可以通过该HARQ进程进行上行数据传输。
第二类型的HARQ进程还可以称为反馈使能(ensble)的HARQ进程,或者下行HARQ反馈使能的HARQ进程。在终端设备通过第一类型的HARQ进程向网络设备发送上行数据之后的预设时长之内,若网络设备再次调度终端设备通过该HARQ进程进行上行数据传输时,则终端设备可以忽略对该HARQ进程的调度。或者说,终端设备在该预设时长内不期待网络设备对该HARQ进程进行再次调度。
在本申请中,网络设备可以将终端设备中的部分HARQ进程配置为第一类型或非使能态,网络设备还可以通过DCI指示终端设备中HARQ进程的类型。如前所述,在终端设备中的至少部分HARQ进程为第一类型时,可以提高了终端设备和网络设备之间的数据传输效率。
下面,通过具体实施例对本申请所示的技术方案进行详细说明。需要说明的是,下面几个实施例可以独立存在,也可以相互结合,对于相同或相似的内容,在不同的实施例中不再重复说明。
图4为本申请实施例提供的一种数据传输方法的流程示意图。请参见图4,包括:
S401、网络设备确定DCI。
可选地,网络设备确定DCI,并通过DCI调度终端设备进行下行接收例如调度终端设备进行PDSCH接收,其中,该DCI中包括该下行传输对应的HARQ进程号的指示信息。
可选地,网络设备确定DCI,并通过DCI调度终端设备进行上行发送例如调度终端设备进行PUSCH发送,其中,该DCI中包括该上行传输对应的HARQ进程号的指示信息。
可选的,网络设备在确定DCI的时候,可以根据该DCI要调度的HARQ进程(DCI中包括的HARQ进程号指示的HARQ进程)的类型,确定该类型的HARQ进程对应的DCI。例如,网络设备确定DCI要调度的HARQ进程为非使能态的HARQ进程,因此网络设备根据该确定的HARQ进程的类型,可以确定DCI。该HARQ进程的类型可以为网络设备配置的。HARQ进程的类型可以为第一类型或者第二类型。
网络设备可以预先配置终端设备中的HARQ进程的类型,也可以不预先配置终端设备中的HARQ进程的类型。若网络设备预先配置HARQ进程的类型,则网络设备可以根据预先配置确定HARQ进程的类型。网络设备预先配置终端设备中的HARQ进程的类型之后,网络设备还可以向终端设备发送该配置,例如,网络设备可以通过RRC信令、媒介接入控制(medium access control,MAC)控制单元(control element,CE)或者DCI向终端设备发送该配置。当然,网络设备也可以不向终端设备发送该配置。若网络设备不预先配置HARQ进程的类型,则网络设备可以在向终端设备发送DCI时才确定该DCI对应的HARQ进程的类型。
可选地,网络设备或终端设备可以根据配置的HARQ进程的类型确定调度该类型的HARQ进程的DCI的第一信息。第一信息包括如下信息中的至少一种:DCI的长度;或,DCI对应的无线网络设备临时标识(radio network temporary identifier,RNTI);或,DCI对应的搜索空间;或,DCI对应的聚合等级。
需要说明的是,当第一信息不同时,网络设备确定第一信息的过程可以不同,在图5-图8所示的实施例中进行说明,此处不再进行赘述。
可选的,网络设备可以将第一类型的HARQ进程配置为重复传输N次。网络设备可以将第二类型的HARQ进程配置为不重复传输,或者重复传输次数为M。M和N为大于1的整数。M和N可以不同。
可选的,网络设备可以确定第一类型的HARQ进程的配置参数为第一配置参数,网络设备可以确定第二类型的HARQ进程的配置参数为第二配置参数。其中,第一配置参数和第二配置参数中至少存在一个参数不同。
S402、网络设备向终端设备发送DCI。
S403、终端设备根据DCI,确定该DCI调度的HARQ进程对应的HARQ反馈功能状态。
可选地,对于下行传输,终端设备根据DCI,确定是否对该DCI调度的HARQ进程进行反馈。
可选地,终端设备可以通过如下方式确定是否对DCI调度的HARQ进程进行反馈:终端设备根据DCI确定HARQ进程的类型,并根据HARQ进程的类型,确定是否根据该DCI对该DCI调度的HARQ进程进行反馈。
可选地,终端设备可以通过如下方式确定是否对DCI调度的HARQ进程进行反馈:终端设备可以根据DCI的第一信息,确定是否对DCI指示的HARQ进程进行反馈。可选的,第一信息包括如下信息中的至少一种:DCI的长度;或,DCI对应的RNTI;或,DCI对应的搜索空间;或,DCI对应的聚合等级。可选的,终端设备可以根据DCI的第一信息确定HARQ进程的类型,并根据HARQ进程的类型确定是否对HARQ进程进行反馈。
在上述实现方式中,HARQ进程的类型为第一类型或第二类型。若HARQ进程的类型为第一类型,则终端设备确定不对HARQ进程进行反馈;或者,若HARQ进程的类型为第二类型,则终端设备确定对HARQ进程进行反馈。
可选地,对于上行传输,终端设备根据该DCI确定该DCI调度的HARQ进程对应的HARQ反馈功能状态。可选地,终端设备可以根据DCI的第一信息,确定该DCI调度的HARQ进程对应的HARQ反馈功能状态。可选的,第一信息包括如下信息中的至少一种:DCI的长度;或,DCI对应的RNTI;或,DCI对应的搜索空间;或,DCI对应的聚合等级。可选的,终端设备可以根据DCI的第一信息确定HARQ进程的类型,并根据HARQ进程的类型确定HARQ进程对应的HARQ反馈功能状态。
需要说明的是,当第一信息不同时,终端设备根据第一信息确定的HARQ进程对应的HARQ反馈功能状态也不同,或者,当第一信息不同时,终端设备根据第一信息确定HARQ进程的类型的方式不同,在图5-图8所示的实施例中进行说明,此处不再进行赘述。
在一种可能的实施例中,终端设备可以根据DCI确定DCI指示的HARQ进程的类型,HARQ进程的类型为第一类型或者第二类型。终端设备确定得到HARQ进程的类型之后,可以根据HARQ进程的类型进行其它处理,本申请实施例对终端设备根据和HARQ进程进行的处理事项不做具体限定。
本申请实施例提供的数据传输方法,在终端设备根据DCI确定不对DCI指示的HARQ进程进行反馈时,则终端设备无需对该HARQ进程进行反馈,网络设备也无需等待终端设备的反馈即可通过该HARQ进程传输其它数据,提高了数据传输效率。进一步的,终端设备通过DCI即可确定得到是否需要对HARQ进程进行反馈,网络设备无需向终端设备发送额外的信令,节省了信令开销。
在上述任意一个实施例的基础上,下面,结合图5-图8所示的实施例,对终端设备根据不同的第一信息确定是否对HARQ进程进行反馈的过程进行说明。
图5为本申请实施例提供的另一种数据传输方法的流程示意图。在图5所示的实施例中,第一信息为DCI的长度。请参见图5,该方法可以包括:
S501、网络设备确定DCI的长度,并根据DCI的长度确定DCI。
网络设备可以根据DCI对应的HARQ进程的类型,确定DCI的长度,并根据DCI的长度生成DCI。
例如,若HARQ进程的类型为第一类型,网络设备确定对应DCI的长度为第一DCI长度;或者,若HARQ进程的类型为第二类型,网络设备确定对应DCI的长度为第二DCI长度。第一DCI长度和第二DCI长度不相等。可选地,第一DCI长度小于第二DCI长度。
可选地,当DCI的长度为第一DCI长度时,DCI不包括如下信息域中的至少一种:物理上行控制信道PUCCH的TPC命令、下行分配指示(downlink assignment index,DAI)、PUCCH资源指示、PDSCH 到HARQ反馈的定时指示、单次HARQ-ACK反馈请求、PDSCH分组指示、新反馈指示NFI、触发反馈组指示。
可选地,当DCI的长度为第二DCI长度时,DCI包括如下信息域中的至少一种:PUCCH的TPC命令、下行分配指示DAI、PUCCH资源指示、PDSCH到HARQ反馈的定时指示、单次HARQ-ACK反馈请求、PDSCH分组指示、新反馈指示NFI、触发反馈组指示。
当DCI调度不同类型的HARQ进程时,对应的DCI的长度不同,例如为第一DCI长度或第二DCI长度。其中,第一DCI长度的DCI中包括的信息域与第二DCI长度的DCI中包括的信息域至少部分不同。下面,以下行调度为例,结合表4-表6进行说明。
例如,当DCI格式为DCI格式1_0时,第一DCI长度和第二DCI长度对应的DCI中各DCI域(还可以称为信息域)的比特数如表4所示:
表4
Figure PCTCN2020077279-appb-000006
请参见表4,若网络设备确定DCI的长度为第一DCI长度,则该DCI中如下四个DCI域(还可以称为信息域)的长度为0:下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH到HARQ反馈定时指示。换句话说,若网络设备确定DCI的长度为第一DCI长度,则该DCI中不包括如下四个信息域:下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH到HARQ反馈定时指示。
例如,当DCI格式为DCI格式1_1时,第一DCI长度和第二DCI长度对应的DCI中各DCI域(还可以称为信息域)的比特数如表5所示:
表5
Figure PCTCN2020077279-appb-000007
Figure PCTCN2020077279-appb-000008
请参见表5,若网络设备确定DCI的长度为第一DCI长度,则该DCI中如下八个DCI域(还可以称为信息域)的长度为0:下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH到HARQ反馈定时指示、单次HARQ-ACK请求、PDSCH群索引、新反馈指示、请求的PDSCH组数。换句话说,若网络设备确定DCI的长度为第一DCI长度,则该DCI中不包括如下八个信息域:下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH到HARQ反馈定时指示、单次HARQ-ACK请求、PDSCH群索引、新反馈指示、请求的PDSCH组数。
例如,当DCI格式为DCI格式1_2时,第一DCI长度和第二DCI长度对应的DCI中各DCI域(还 可以称为信息域)的比特数如表6所示:
表6
Figure PCTCN2020077279-appb-000009
请参见表6,若网络设备确定DCI的长度为第一DCI长度,则该DCI中如下四个DCI域(还可以称为信息域)的长度为0:下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH-to-HARQ_反馈定时指示。换句话说,若网络设备确定DCI的长度为第一DCI长度,则该DCI中不包括如下四个信息域:下行链路分配索引、预定PUCCH的TPC命令、PUCCH资源指示、PDSCH-to-HARQ_反馈定时指示。
S502、网络设备向终端设备发送DCI。
S503、终端设备根据DCI的长度,确定该DCI调度的HARQ进程对应的HARQ反馈功能状态。
可选的,终端设备可以先确定DCI的长度,再根据DCI的长度确定是否对DCI指示的HARQ进程进行反馈。DCI的长度可以为第一DCI长度或第二DCI长度,若DCI的长度为第一DCI长度,则终端设备确定不对HARQ进程进行反馈;或,若DCI的长度为第二DCI长度,则终端设备确定对HARQ进程进行反馈。
终端设备可以通过不同的DCI长度进行DCI检测(还可以称为PDCCH检测),将检测到DCI时所使用的DCI长度确定为该DCI的长度。例如,若终端设备根据第一DCI长度检测到该DCI,则可以确定DCI的长度为第一DCI长度;或者,若终端设备根据第二DCI长度检测到该DCI,则可以确定 DCI的长度为第二DCI长度。在终端设备进行PDCCH检测的过程,当DCI的长度为第一DCI长度时,DCI中包括的信息比特较少,使用相同的PDCCH传输资源时可以增加PDCCH检测的可靠性。
可选的,上述检测可以为盲检测。为了便于描述,在下文中,以该检测为盲检测为例进行说明。下文所涉及的盲检测还可以称为DCI盲检测或者PDCCH盲检测。
在实际应用过程中,若终端设备使用第一DCI长度和第二DCI长度进行盲检测,则可能会使得终端设备进行盲检测的次数较多。为了减少终端设备进行盲检测的次数,终端设备可以根据网络设备对其HARQ进程的配置,确定盲检测所使用的DCI长度。
例如,若终端设备中的HARQ进程均被配置为第一类型,终端设备进行PDCCH盲检测所使用的DCI长度包括第一DCI长度。在该种情况下,终端设备可以不使用第二DCI长度进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的HARQ进程均被配置为第二类型,终端设备进行PDCCH盲检测所使用的DCI长度包括第二DCI长度。在该种情况下,终端设备可以不使用第一DCI长度进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,终端设备进行PDCCH检测所使用的DCI长度包括第一DCI长度和第二DCI长度。
在实际应用过程中,终端设备除了接收用于调度数据传输的DCI之外,终端设备可能还接收其它类型的DCI,在终端设备接收其它类型的DCI时,终端设备可以通过其它DCI长度进行其它类型的DCI的盲检测。换句话说,终端设备进行盲检测所使用的DCI长度还可以为其它DCI长度(除第一DCI长度和第二DCI长度之外的DCI长度)。
在终端设备使用第一DCI长度和第二DCI长度进行PDCCH盲检测时,为了减少终端设备进行盲检测的次数,可以为不同的DCI长度配置不同的聚合等级。例如,配置第一DCI长度对应第一聚合等级,配置第二DCI长度对应第二聚合等级,第一聚合等级小于或等于第二聚合等级。由于第一DCI长度小于第二DCI长度,在保证相同PDCCH传输的可靠性的情况下,传输第一DCI长度对应的DCI需要的资源少于传输第二DCI长度对应的DCI所需的资源,从而减少终端设备的PDCCH盲检测次数。
为了减少DCI盲检测的虚警,在终端设备通过一种DCI长度检测到DCI之后,终端设备还可以进一步确定DCI对应的HARQ进程的类型与该DCI长度对应的HARQ进程的类型是否一致,若一致,再确定是否对HARQ进程进行反馈,若不一致,则终端设备丢弃DCI或者不接收DCI对应的PDSCH。
例如,若终端设备根据第一DCI长度检测到DCI,终端设备根据该第一DCI长度可以确定该DCI指示的HARQ进程的类型为第一类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第一类型。若终端设备根据其它方式确认该HARQ进程的类型也为第一类型,则终端设备可以确定不对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第二类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
例如,若终端设备根据第二DCI长度检测到DCI,终端设备根据该第二DCI长度可以确定该DCI指示的HARQ进程的类型为第二类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第二类型。若终端设备根据其它方式确认该HARQ进程的类型也为第二类型,则终端设备可以确定对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第一类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
在上述两个示例中,其它方式可以为:终端设备通过网络设备预先配置的HARQ进程的类型,确定HARQ进程的类型;或者,终端设备可以通过图6-图8实施例中的任意方式确定HARQ进程的类型。
在图5所示的实施例中,在终端设备根据DCI的长度即可确定是否对DCI指示的HARQ进程进行反馈。若终端设备确定不对DCI指示的HARQ进程进行反馈时,则终端设备无需对该HARQ进程进行反馈,网络设备也无需等待终端设备的反馈即可通过该HARQ进程传输其它数据,提高了数据传输效率。进一步的,通过DCI的长度即可隐式的指示出HARQ进程的类型,无需在DCI中增加额外的信令,节省了信令开销。
图6为本申请实施例提供的又一种数据传输方法的流程示意图。在图6所示的实施例中,第一信息为DCI对应的RNTI。请参见图6,该方法可以包括:
S601、网络设备确定DCI对应的RNTI,并根据RNTI对DCI进行扰码。
网络设备可以根据DCI指示的HARQ进程的类型,确定DCI对应的RNTI。
例如,若HARQ进程的类型为第一类型,网络设备确定DCI对应的RNTI为第一RNTI;或者,若HARQ进程的类型为第二类型,网络设备确定DCI对应的RNTI为第二RNTI。
网络设备可以为终端设备配置第一RNTI和/或第二RNTI,其中,第一RNTI用于扰码第一类型的HARQ进程对应的DCI(下行授权DCI),第二RNTI用于扰码第二类型的HARQ进程对应的下行授权DCI。
例如,若终端设备中的HARQ进程均被配置为第一类型,则网络设备可以为终端设备配置第一RNTI,换句话说,网络设备为终端设备配置的RNTI包括第一RNTI。若终端设备中的HARQ进程均被配置为第二类型,则网络设备可以为终端设备配置第二RNTI,换句话说,网络设备为终端设备配置的RNTI包括第二RNTI。若终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,则网络设备可以为终端设备配置第一RNTI和第二RNTI,换句话说,网络设备为终端设备配置的RNTI包括第一RNTI和第二RNTI。
在网络设备确定得到DCI和DCI对应的RNTI之后,网络设备可以通过DCI对应的RNTI对该DCI进行扰码。
需要说明的是,若HARQ进程的类型为第一类型,则网络设备生成的DCI的长度可以为第一长度。 若HARQ进程的类型为第二类型,则网络设备生成的DCI的长度可以为第二长度。该过程可以参见S501,此处不再进行赘述。
S602、网络设备向终端设备发送DCI。
S603、终端设备根据DCI对应的RNTI,确定该DCI调度的HARQ进程对应的HARQ反馈功能状态。
可选的,终端设备可以先确定DCI对应的RNTI,再根据DCI对应的RNTI确定是否对DCI指示的HARQ进程进行反馈。DCI对应的RNTI为第一RNTI或者第二RNTI,若DCI对应的RNTI为第一RNTI,则终端设备确定不对HARQ进程进行反馈,或,若DCI对应的RNTI为第二RNTI,则终端设备确定对HARQ进程进行反馈。
终端设备可以通过不同的RNTI进行DCI检测(还可以称为PDCCH检测),将检测到DCI时所使用的RNTI确定为该DCI对应的RNTI。例如,若终端设备根据第一RNTI检测到该DCI,则可以确定DCI对应的RNTI为第一RNTI;或者,若终端设备根据第二RNTI检测到该DCI,则可以确定DCI对应的RNTI为第二RNTI。在上述过程中,通过DCI对应的RNTI即可确定是否对HARQ进程进行反馈,无需在DCI中增加指示信息,不但节省信令开销,还可以使得PDCCH检测的可靠性较高。
可选的,上述检测可以为盲检测。为了便于描述,在下文中,以该检测为盲检测为例进行说明。
在实际应用过程中,若终端设备使用第一RNTI和第二RNTI进行盲检测,则可能会使得终端设备进行盲检测的次数较多。为了减少终端设备进行盲检测的次数,终端设备可以根据网络设备对其HARQ进程的配置,确定盲检测所使用的RNTI。
例如,若终端设备中的HARQ进程均被配置为第一类型,终端设备进行PDCCH检测所使用的RNTI包括第一RNTI。在该种情况下,终端设备可以不使用第二RNTI进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的HARQ进程均被配置为第二类型,终端设备进行PDCCH检测所使用的RNTI包括第二RNTI。在该种情况下,终端设备可以不使用第一RNTI进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,终端设备进行PDCCH检测所使用的RNTI包括第一RNTI和第二RNTI。
为了减少DCI盲检测的虚警,在终端设备通过一种RNTI检测到DCI之后,终端设备还可以进一步确定DCI对应的HARQ进程的类型与该RNTI对应的HARQ进程的类型是否一致,若一致,再确定是否对HARQ进程进行反馈。若不一致,则终端设备丢弃DCI或者不接收DCI对应的PDSCH。
例如,若终端设备通过第一RNTI检测到DCI,终端设备根据该第一RNTI可以确定该DCI指示的HARQ进程的类型为第一类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第一类型。若终端设备根据其它方式确认该HARQ进程的类型也为第一类型,则终端设备可以确定不对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第二类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
例如,若终端设备通过第二RNTI检测到DCI,终端设备根据该第二RNTI可以确定该DCI指示的HARQ进程的类型为第二类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第二类型。若终端设备根据其它方式确认该HARQ进程的类型也为第二类型,则终端设备可以确定对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第一类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
在上述两个示例中,其它方式可以为:终端设备通过网络设备预先配置的HARQ进程的类型,确定HARQ进程的类型;或者,终端设备可以通过图5、图7-图8实施例中的任意方式确定HARQ进程的类型。
在图6所示的实施例中,在终端设备根据DCI对应的RNTI即可确定是否对DCI指示的HARQ进程进行反馈。若终端设备确定不对DCI指示的HARQ进程进行反馈时,则终端设备无需对该HARQ进程进行反馈,网络设备也无需等待终端设备的反馈即可通过该HARQ进程传输其它数据,提高了数据传输效率。进一步的,通过DCI对应的RNTI即可隐式的指示出HARQ进程的类型,无需在DCI中增加额外的信令,节省了信令开销。
图7为本申请实施例提供的再一种数据传输方法的流程示意图。在图7所示的实施例中,第一信息为DCI对应的搜索空间。请参见图7,该方法可以包括:
S701、网络设备确定DCI和DCI对应的搜索空间。
网络设备可以根据DCI指示的HARQ进程的类型,确定DCI对应的搜索空间。
例如,若HARQ进程的类型为第一类型,网络设备确定DCI对应的搜索空间为第一搜索空间;或者,若HARQ进程的类型为第二类型,网络设备确定DCI对应的搜索空间为第二搜索空间。
网络设备可以为终端设备配置第一搜索空间和/或第二搜索空间,其中,第一搜索空间用于传输第一类型的HARQ进程对应的DCI(下行授权DCI),第二搜索空间用于传输第二类型的HARQ进程对应的DCI。当然,网络设备还可以为终端设备配置其它搜索空间。
例如,若终端设备中的HARQ进程均被配置为第一类型,则网络设备可以为终端设备配置第一搜索空间,换句话说,网络设备为终端设备配置的搜索空间包括第一搜索空间。若终端设备中的HARQ进程均被配置为第二类型,则网络设备可以为终端设备配置第二搜索空间,换句话说,网络设备为终端设备配置的搜索空间包括第二搜索空间。若终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,则网络设备可以为终端设备配置第一搜索空间和第二搜索空间,换句话说,网络设备为终端设备配置的搜索空间包括第一搜索空间和第二搜索空间。
需要说明的是,若HARQ进程的类型为第一类型,则网络设备生成的DCI的长度可以为第一长度。若HARQ进程的类型为第二类型,则网络设备生成的DCI的长度可以为第二长度。该过程可以参见S501,此处不再进行赘述。和/或,若HARQ进程的类型为第一类型,则网络设备确定DCI对应的RNTI可以为第一RNTI。若HARQ进程的类型为第二类型,则网络设备确定DCI对应的RNTI可以为第二RNTI。该过程可以参见S601,此处不再进行赘述。
S702、网络设备通过DCI对应的搜索空间向终端设备发送DCI。
例如,若DCI对应的搜索空间为第一搜索空间,则网络设备通过第一搜索空间传输该DCI。若DCI对应的搜索空间为第二搜索空间,则网络设备通过第二搜索空间传输该DCI。
S703、终端设备根据DCI对应的搜索空间,确定该DCI调度的HARQ进程对应的HARQ反馈功能状态。
可选的,终端设备可以先确定DCI对应的搜索空间,再根据DCI对应的搜索空间确定是否对DCI指示的HARQ进程进行反馈。DCI对应的搜索空间为第一搜索空间或者第二搜索空间,若DCI对应的搜索空间为第一搜索空间,则终端设备确定不对HARQ进程进行反馈,或,若DCI对应的搜索空间为第二搜索空间,则终端设备确定对HARQ进程进行反馈。
终端设备可以通过不同的搜索空间进行DCI检测(还可以称为PDCCH检测),将检测到DCI时所使用的搜索空间确定为该DCI对应的搜索空间。例如,若终端设备根据第一搜索空间检测到该DCI,则可以确定DCI对应的搜索空间为第一搜索空间;或者,若终端设备根据第二搜索空间检测到该DCI,则可以确定DCI对应的搜索空间为第二搜索空间。在上述过程中,通过DCI对应的搜索空间即可确定是否对HARQ进程进行反馈,无需在DCI中增加指示信息,不但节省信令开销,还可以使得PDCCH检测的可靠性较高。
可选的,上述检测可以为盲检测。为了便于描述,在下文中,以该检测为盲检测为例进行说明。
在实际应用过程中,若终端设备使用第一搜索空间和第二搜索空间进行盲检测,则可能会使得终端设备进行盲检测的次数较多。为了减少终端设备进行盲检测的次数,终端设备可以根据网络设备对其HARQ进程的配置,确定盲检测所使用的搜索空间。
例如,若终端设备中的HARQ进程均被配置为第一类型,终端设备进行PDCCH检测所使用的搜索空间包括第一搜索空间。在该种情况下,终端设备可以不使用第二搜索空间进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的HARQ进程均被配置为第二类型,终端设备进行PDCCH检测所使用的搜索空间包括第二搜索空间。在该种情况下,终端设备可以不使用第一搜索空间进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,终端设备进行PDCCH检测所使用的搜索空间包括第一搜索空间和第二搜索空间。
为了减少DCI盲检测的虚警,在终端设备通过一种搜索空间检测到DCI之后,终端设备还可以进一步确定DCI对应的HARQ进程的类型与该搜索空间对应的HARQ进程的类型是否一致,若一致,再确定是否对HARQ进程进行反馈。若不一致,则终端设备丢弃DCI或者不接收DCI对应的PDSCH。
例如,若终端设备通过第一搜索空间检测到DCI,终端设备根据该第一搜索空间可以确定该DCI指示的HARQ进程的类型为第一类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第一类型。若终端设备根据其它方式确认该HARQ进程的类型也为第一类型,则终端设备可以确定不对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第二类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
例如,若终端设备通过第二搜索空间检测到DCI,终端设备根据该第二搜索空间可以确定该DCI指示的HARQ进程的类型为第二类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第二类型。若终端设备根据其它方式确认该HARQ进程的类型也为第二类型,则终端设备可以确定对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第一类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
在上述两个示例中,其它方式可以为:终端设备通过网络设备预先配置的HARQ进程的类型,确定HARQ进程的类型;或者,终端设备可以通过图5、图6或图8实施例中的任意方式确定HARQ进程的类型。
在图7所示的实施例中,在终端设备根据DCI对应的搜索空间即可确定是否对DCI指示的HARQ进程进行反馈。若终端设备确定不对DCI指示的HARQ进程进行反馈时,则终端设备无需对该HARQ进程进行反馈,网络设备也无需等待终端设备的反馈即可通过该HARQ进程传输其它数据,提高了数据传输效率。进一步的,通过DCI对应的搜索空间即可隐式的指示出HARQ进程的类型,无需在DCI中增加额外的信令,节省了信令开销。
图8为本申请实施例提供的另一种数据传输方法的流程示意图。在图8所示的实施例中,第一信息为DCI对应的聚合等级。请参见图8,该方法可以包括:
S801、网络设备确定DCI和DCI对应的聚合等级。
网络设备可以根据DCI指示的HARQ进程的类型,确定DCI对应的聚合等级。
例如,若HARQ进程的类型为第一类型,网络设备确定DCI对应的聚合等级为第一聚合等级;或者,若HARQ进程的类型为第二类型,网络设备确定DCI对应的聚合等级为第二聚合等级。
网络设备可以为终端设备配置第一聚合等级和/或第二聚合等级。当然,网络设备还可以为终端设备配置其它聚合等级。
例如,若终端设备中的HARQ进程均被配置为第一类型,则网络设备可以为终端设备配置第一聚 合等级,换句话说,网络设备为终端设备配置的聚合等级包括第一聚合等级。若终端设备中的HARQ进程均被配置为第二类型,则网络设备可以为终端设备配置第二聚合等级,换句话说,网络设备为终端设备配置的聚合等级包括第二聚合等级。若终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,则网络设备可以为终端设备配置第一聚合等级和第二聚合等级,换句话说,网络设备为终端设备配置的聚合等级包括第一聚合等级和第二聚合等级。
需要说明的是,若HARQ进程的类型为第一类型,则网络设备生成的DCI的长度可以为第一长度。若HARQ进程的类型为第二类型,则网络设备生成的DCI的长度可以为第二长度。该过程可以参见S501,此处不再进行赘述。和/或,若HARQ进程的类型为第一类型,则网络设备确定DCI对应的RNTI可以为第一RNTI。若HARQ进程的类型为第二类型,则网络设备确定DCI对应的RNTI可以为第二RNTI。该过程可以参见S601,此处不再进行赘述。和/或,若HARQ进程的类型为第一类型,则网络设备确定DCI对应的搜索空间可以为第一搜索空间。若HARQ进程的类型为第二类型,则网络设备确定DCI对应的搜索空间可以为第二搜索空间。该过程可以参见S701,此处不再进行赘述
S802、网络设备根据聚合等级向终端设备发送DCI。
S803、终端设备根据DCI对应的聚合等级,确定该DCI调度的HARQ进程对应的HARQ反馈功能状态。
可选的,终端设备可以先确定DCI对应的聚合等级,再根据DCI对应的聚合等级确定是否对DCI指示的HARQ进程进行反馈。DCI对应的聚合等级为第一聚合等级或者第二聚合等级,若DCI对应的聚合等级为第一聚合等级,则终端设备确定不对HARQ进程进行反馈,或,若DCI对应的聚合等级为第二聚合等级,则终端设备确定对HARQ进程进行反馈。
终端设备可以通过不同的聚合等级进行DCI检测(还可以称为PDCCH检测),将检测到DCI时所使用的聚合等级确定为该DCI对应的聚合等级。例如,若终端设备根据第一聚合等级检测到该DCI,则可以确定DCI对应的聚合等级为第一聚合等级;或者,若终端设备根据第二聚合等级检测到该DCI,则可以确定DCI对应的聚合等级为第二聚合等级。在上述过程中,通过DCI对应的聚合等级即可确定是否对HARQ进程进行反馈,无需在DCI中增加指示信息,不但节省信令开销,还可以使得PDCCH检测的可靠性较高。
可选的,上述检测可以为盲检测。为了便于描述,在下文中,以该检测为盲检测为例进行说明。
在实际应用过程中,若终端设备使用第一聚合等级和第二聚合等级进行盲检测,则可能会使得终端设备进行盲检测的次数较多。为了减少终端设备进行盲检测的次数,终端设备可以根据网络设备对其HARQ进程的配置,确定盲检测所使用的聚合等级。
例如,若终端设备中的HARQ进程均被配置为第一类型,终端设备进行PDCCH检测所使用的聚合等级包括第一聚合等级。在该种情况下,终端设备可以不使用第二聚合等级进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的HARQ进程均被配置为第二类型,终端设备进行PDCCH检测所使用的聚合等级包括第二聚合等级。在该种情况下,终端设备可以不使用第一聚合等级进行盲检测,使得终端设备进行盲检测的次数较少。
例如,若终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,终端设备进行PDCCH检测所使用的聚合等级包括第一聚合等级和第二聚合等级。
为了减少DCI盲检测的虚警,在终端设备通过一种聚合等级检测到DCI之后,终端设备还可以进一步确定DCI对应的HARQ进程的类型与该聚合等级对应的HARQ进程的类型是否一致,若一致,再确定是否对HARQ进程进行反馈。若不一致,则终端设备丢弃DCI或者不接收DCI对应的PDSCH。
例如,若终端设备通过第一聚合等级检测到DCI,终端设备根据该第一聚合等级可以确定该DCI指示的HARQ进程的类型为第一类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第一类型。若终端设备根据其它方式确认该HARQ进程的类型也为第一类型,则终端设备可以确定不对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第二类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
例如,若终端设备通过第二聚合等级检测到DCI,终端设备根据该第二聚合等级可以确定该DCI指示的HARQ进程的类型为第二类型。终端设备可以再根据其它方式进一步确认该HARQ进程的类型是否为第二类型。若终端设备根据其它方式确认该HARQ进程的类型也为第二类型,则终端设备可以确定对该HARQ进程进行反馈,这样,可以减少DCI盲检测的虚警。若终端设备根据其它方式确定该HARQ进程的类型为第一类型,则终端设备可以忽略该DCI的调度,或者终端设备可以不接收该DCI调度的PDSCH。
在上述两个示例中,其它方式可以为:终端设备通过网络设备预先配置的HARQ进程的类型,确定HARQ进程的类型;或者,终端设备可以通过图5-图7实施例中的任意方式确定HARQ进程的类型。
在图8所示的实施例中,在终端设备根据DCI对应的聚合等级即可确定是否对DCI指示的HARQ进程进行反馈。若终端设备确定不对DCI指示的HARQ进程进行反馈时,则终端设备无需对该HARQ进程进行反馈,网络设备也无需等待终端设备的反馈即可通过该HARQ进程传输其它数据,提高了数据传输效率。进一步的,通过DCI对应的聚合等级即可隐式的指示出HARQ进程的类型,无需在DCI中增加额外的信令,节省了信令开销。
在上述任意一个实施例的基础上,在终端设备接收到网络设备发送的DCI之后,若DCI指示对DCI指示的HARQ进程进行反馈,则该DCI中包括单次HARQ-ACK反馈请求。可选的,在该单次HARQ-ACK反馈请求被触发时,终端设备向网络设备发送终端设备中的HARQ进程对应的反馈信息,即,HARQ反馈码本中可以包括第一类型和第二类型的HARQ进程对应的HARQ-ACK反馈信息。或者,在该单次HARQ-ACK反馈请求未被触发时,终端设备不向网络设备发送第一类型的HARQ进程 对应的HARQ-ACK反馈信息,即,上行HARQ反馈码本中不包括第一类型的HARQ进程对应的HARQ-ACK反馈信息。
在上述任意一个实施例的基础上,还可以为终端设备配置更多的并行HARQ进程,进而提高终端设备和网络设备之间的通信效率。例如,对于NTN系统,若目前通常为终端设备配置16个HARQ进程,则在本申请中,为终端设备配置的HARQ进程的数量可以大于16。
在上述任意一个实施例的基础上,终端设备接收网络设备发送的DCI,该DCI用于指示释放半持续调度(semi-persistent scheduling,SPS),则终端设备根据该DCI确定是否对该DCI进行反馈。需要说明的是,终端设备确定是否对该DCI进行反馈的方式,与上述实施例中涉及的确定是否对DCI指示的HARQ进行反馈的方式相同,此处不再进行赘述。
可选地,在上行过程中,网络设备可以调度终端设备进行上行传输,例如,网络设备可以调度终端设备通过HARQ进程进行上行传输。在网络设备调度终端设备通过第一HARQ进程进行上行传输时,终端设备可以根据第一HARQ进程的类型确定是否通过第一HARQ进程向网络设备传输上行数据。
可选的,在网络设备调度终端设备通过第一HARQ进程进行上行传输时,终端设备可以先判断在当前时刻之前的预设时长之内,终端设备是否通过第一HARQ进程传输上行数据。若终端设备在当前时刻之前的预设时长之内未通过第一HARQ进程传输上行数据,则终端设备通过第一HARQ进程向网络设备发送上行数据。若终端设备在当前时刻之前的预设时长之内通过第一HARQ进程传输上行数据,则终端设备根据第一HARQ进程的类型确定是否通过第一HARQ进程向网络设备传输上行数据。可选的,若第一HARQ进程的类型为第一类型,则终端设备通过第一HARQ进程向网络设备传输上行数据;若第一HARQ进程的类型为第二类型,则终端设备可以忽略网络设备的调度,即,终端设备不通过第一HARQ进程向网络设备发送上行数据。
在上述过程中,当网络设备调度终端设备通过第一类型的HARQ进程传输上行数据时,网络设备可以连续的调度终端设备通过第一类型的HARQ进程传输上行数据,在终端设备通过第一类型的HARQ进程传输上行数据之后,终端设备无需等待预设时长,终端设备即可通过第一类型的HARQ进程再进行上行数据传输,提高了终端设备和网络设备之间的数据传输效率。
图9为本申请实施例提供的一种数据传输装置的结构示意图。该数据传输装置10可以设置在终端设备中。请参见图9,该数据传输装置10可以包括接收模块11和处理模块12,其中,
所述接收模块11用于,接收网络设备发送的下行控制信息DCI;
所述处理模块12用于,根据所述DCI,确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
本申请实施例提供的数据传输装置可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
在一种可能的实施方式中,所述处理模块12具体用于:
根据所述DCI的第一信息,确定是否对所述DCI指示的HARQ进程进行反馈。
在一种可能的实施方式中,所述第一信息包括如下信息中的至少一种:
所述DCI的长度;
所述DCI对应的无线网络设备临时标识RNTI;
所述DCI对应的搜索空间;
所述DCI对应的聚合等级。
在一种可能的实施方式中,所述处理模块12具体用于:
根据所述DCI,确定所述HARQ进程的类型,所述HARQ进程的类型为第一类型或者第二类型,所述第一类型的HARQ进程为终端设备不进行反馈的HARQ进程,所述第二类型的HARQ进程为终端设备进行反馈的HARQ进程;
根据所述HARQ进程的类型,确定是否对所述DCI指示的HARQ进程进行反馈。
在一种可能的实施方式中,所述处理模块12具体用于:
若所述HARQ进程的类型为所述第一类型,则对所述DCI指示的HARQ进程进行反馈;
若所述HARQ进程的类型为所述第二类型,则不对所述DCI指示的HARQ进程进行反馈。
在一种可能的实施方式中,所述第一信息为所述DCI的长度;所述处理模块具体用于:
若所述DCI的长度为第一DCI长度,则确定不对所述HARQ进程进行反馈;或,
若所述DCI的长度为第二DCI长度,则确定对所述HARQ进程进行反馈。
在一种可能的实施方式中,所述第一DCI长度小于所述第二DCI长度。
在一种可能的实施方式中,若根据所述第一DCI长度检测到所述DCI,则所述DCI的长度为所述第一DCI长度;或,
若根据所述第二DCI长度检测到所述DCI,则所述DCI的长度为所述第二DCI长度。
在一种可能的实施方式中,所述第一DCI长度对应第一聚合等级;
所述第二DCI长度对应第二聚合等级。
在一种可能的实施方式中,所述第一聚合等级小于或等于所述第二聚合等级。
在一种可能的实施方式中,所述DCI的长度为第一DCI长度;所述DCI不包括如下信息域中的至少一种:
物理上行控制信道PUCCH的TPC命令;
下行分配指示DAI;
PUCCH资源指示;
物理下行共享信道PDSCH到HARQ反馈的定时指示;
单次HARQ-ACK反馈请求;
PDSCH分组指示;
新反馈指示NFI;
触发反馈组指示。
在一种可能的实施方式中,所述DCI的长度为第二DCI长度;所述DCI包括如下信息域中的至少一种:
PUCCH的TPC命令;
DAI;
PUCCH资源指示;
PDSCH到HARQ反馈的定时指示;
单次HARQ-ACK反馈请求;
PDSCH分组指示;
NFI;
触发反馈组指示。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测所使用的DCI长度包括所述第一DCI长度。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测所使用的DCI长度包括所述第二DCI长度。
在一种可能的实施方式中,所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测所使用的DCI长度包括所述第一DCI长度和所述第二DCI长度。
在一种可能的实施方式中,所述第一信息为所述DCI对应的RNTI;所述处理模块12具体用于:
若所述DCI对应的RNTI为第一RNTI,则确定不对所述HARQ进程进行反馈;或,
若所述DCI对应的RNTI为第二RNTI,则确定对所述HARQ进程进行反馈。
在一种可能的实施方式中,若根据所述第一RNTI检测到所述DCI,则所述DCI对应的RNTI为所述第一RNTI;或,
若根据所述第二RNTI检测到所述DCI,则所述DCI对应的RNTI为所述第二RNTI。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测所使用的RNTI包括所述第一RNTI。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测所使用的RNTI包括所述第二RNTI。
在一种可能的实施方式中,所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测所使用的RNTI包括所述第一RNTI和所述第二RNTI。
在一种可能的实施方式中,所述第一信息为所述DCI对应的搜索空间;所述处理模块具体用于:
若所述DCI对应的搜索空间为第一搜索空间,则确定不对所述HARQ进程进行反馈;或,
若所述DCI对应的搜索空间为第二搜索空间,则确定对所述HARQ进程进行反馈。
在一种可能的实施方式中,若在所述第一搜索空间中检测到所述DCI,则所述DCI对应的搜索空间为所述第一搜索空间;或,
若在所述第二搜索空间中检测到所述DCI,则所述DCI对应的搜索空间为所述第二搜索空间。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测的搜索空间包括所述第一搜索空间。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的搜索空间包括所述第二搜索空间。
在一种可能的实施方式中,所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的搜索空间包括所述第一搜索空间和所述第二搜索空间。
在一种可能的实施方式中,所述第一信息为所述DCI对应的聚合等级;所述处理模块12具体用于:
若所述DCI对应的聚合等级为第一聚合等级,则确定不对所述HARQ进程进行反馈;或,
若所述DCI对应的聚合等级为第二聚合等级,则确定对所述HARQ进程进行反馈。
在一种可能的实施方式中,若根据所述第一聚合等级检测到所述DCI,则所述DCI对应的聚合等级为所述第一聚合等级;或,
若根据所述第二聚合等级检测到所述DCI,则所述DCI对应的聚合等级为所述第二聚合等级。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测的聚合等级包括所述第一聚合等级。
在一种可能的实施方式中,所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的聚合等级包括所述第二聚合等级。
在一种可能的实施方式中,所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的聚合等级包括所述第一聚合等级和所述第二聚合等级。
在一种可能的实施方式中,所述接收模块11还用于:
接收所述网络设备发送的第二信息,所述第二信息用于配置所述终端设备中的至少一个HARQ进程的类型。
在一种可能的实施方式中,所述第二信息包括如下信息中的至少一种:
无线资源控制RRC信令;
DCI;
媒质接入控制MAC控制单元CE。
在一种可能的实施方式中,所述处理模块12具体用于:
在所述处理模块根据所述DCI确定得到的所述HARQ进程的类型与所述第二信息指示的所述HARQ进程的类型相同时,执行如下步骤:根据所述DCI确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
在一种可能的实施方式中,所述处理模块12还用于:
在所述处理模块根据所述DCI确定得到的所述HARQ进程的类型与所述第二信息指示的所述HARQ进程的类型不相同时,丢弃所述DCI或者不接收所述DCI对应的PDSCH。
在一种可能的实施方式中,所述DCI指示对所述DCI指示的HARQ进程进行反馈,所述DCI中包括单次HARQ-ACK反馈请求。
图10为本申请实施例提供的另一种数据传输装置的结构示意图。在图9所示实施例的基础上。请参见图10,所述数据传输装置10还包括发送模块13,其中,
所述发送模块13用于,在所述单次HARQ-ACK反馈请求被触发时,向所述网络设备发送所述终端设备中的HARQ进程对应的反馈信息。
本申请实施例提供的数据传输装置可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
图11为本申请实施例提供的又一种数据传输装置的结构示意图。在数据传输装置20可以设置在网络设备中。请参见图11,该数据传输装置20可以包括:处理模块21和发送模块22,其中,
所述处理模块21用于,确定终端设备的下行控制信息DCI;
所述发送模块22用于,向所述终端设备发送所述DCI,所述DCI用于所述终端设备确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
本申请实施例提供的数据传输装置可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
在一种可能的实施方式中,所述处理模块21具体用于:
根据所述HARQ进程的类型确定所述DCI;
其中,所述HARQ进程的类型为第一类型或者第二类型,所述第一类型的HARQ进程为终端设备不进行反馈的HARQ进程,所述第二类型的HARQ进程为终端设备进行反馈的HARQ进程。
在一种可能的实施方式中,所述处理模块21具体用于:
根据所述HARQ进程的类型确定所述DCI的第一信息。
在一种可能的实施方式中,所述第一信息包括如下信息中的至少一种:
所述DCI的长度;
所述DCI对应的无线网络设备临时标识RNTI;
所述DCI对应的搜索空间;
所述DCI对应的聚合等级。
在一种可能的实施方式中,所述第一信息为所述DCI的长度;所述处理模块21具体用于:
若所述HARQ进程的类型为所述第一类型,确定所述DCI的长度为第一DCI长度;或,
若所述HARQ进程的类型为所述第二类型,确定所述DCI的长度为第一DCI长度。
在一种可能的实施方式中,所述第一DCI长度小于所述第二DCI长度。
在一种可能的实施方式中,所述DCI的长度为第一DCI长度;所述DCI不包括如下信息域中的至少一种:
物理上行控制信道PUCCH的TPC命令;
下行分配指示DAI;
物理上行控制信道PUCCH资源指示;
物理下行共享信道PDSCH到HARQ反馈的定时指示;
单次HARQ-ACK反馈请求;
PDSCH分组指示;
新反馈指示NFI;
触发反馈组指示。
在一种可能的实施方式中,所述DCI的长度为第二DCI长度;所述DCI包括如下信息域中的至少一种:
PUCCH的TPC命令;
DAI;
PUCCH资源指示;
PDSCH到HARQ反馈的定时指示;
单次HARQ-ACK反馈请求;
PDSCH分组指示;
NFI;
触发反馈组指示。
在一种可能的实施方式中,所述第一信息为所述DCI对应的RNTI;所述处理模块21具体用于:
所述HARQ进程的类型为所述第一类型,确定所述DCI对应的RNTI为第一RNTI;或,
所述HARQ进程的类型为所述第二类型,确定所述DCI对应的RNTI为第二RNTI。
在一种可能的实施方式中,所述第一信息为所述DCI对应的搜索空间;所述处理模块21具体用于:
所述HARQ进程的类型为所述第一类型,确定所述DCI对应的搜索空间为第一搜索空间;或,
所述HARQ进程的类型为所述第二类型,确定所述DCI对应的搜索空间为第二搜索空间。
在一种可能的实施方式中,所述第一信息为所述DCI对应的聚合等级;所述处理模块21具体用于:
所述HARQ进程的类型为所述第一类型,所述网络设备确定所述DCI对应的聚合等级为第一聚合等级;或,
所述HARQ进程的类型为所述第二类型,所述网络设备确定所述DCI对应的聚合等级为第二聚合等级。
本申请实施例提供的数据传输装置可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
图12为本申请实施例提供的终端设备的结构示意图。请参见图12,终端设备30可以包括:收发器31、存储器32、处理器33。收发器31可包括:发射器和/或接收器。该发射器还可称为发送器、发射机、发送端口或发送接口等类似描述,接收器还可称为接收器、接收机、接收端口或接收接口等类似描述。示例性地,收发器31、存储器32、处理器33,各部分之间通过总线34相互连接。
存储器32用于存储程序指令;
处理器33用于执行该存储器所存储的程序指令,用以使得终端设备30执行上述任一所示的数据传输方法。
其中,收发器31的接收器,可用于执行上述数据传输方法中终端设备的接收功能。收发器31的发送器,可用于执行上述数据传输方法中终端设备的发送功能。
本申请实施例提供的终端设备可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
图13为本申请实施例提供的网络设备的结构示意图。请参见图13,网络设备40可以包括:收发器41、存储器42、处理器43。收发器41可包括:发射器和/或接收器。该发射器还可称为发送器、发射机、发送端口或发送接口等类似描述,接收器还可称为接收器、接收机、接收端口或接收接口等类似描述。示例性地,收发器41、存储器42、处理器43,各部分之间通过总线44相互连接。
存储器42用于存储程序指令;
处理器43用于执行该存储器所存储的程序指令,用以使得终端设备30执行上述任一所示的数据传输方法。
其中,收发器41的发送器,可用于执行上述数据传输方法中网络设备的发送功能。
本申请实施例提供的网络设备可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
本申请实施例提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机执行指令,当所述计算机执行指令被处理器执行时用于实现上述数据传输方法。其实现原理以及有益效果类似,此处不再进行赘述。
本申请实施例还可提供一种计算机程序产品,该计算机程序产品可以由处理器执行,在计算机程序产品被执行时,可实现上述任一所示的终端设备执行的数据传输方法。其实现原理以及有益效果类似,此处不再进行赘述。
本申请实施例提供一种芯片上系统或系统芯片,所述芯片上系统或系统芯片可应用于终端设备,所述芯片上系统或系统芯片包括:至少一个通信接口,至少一个处理器,至少一个存储器,所述通信接口、存储器和处理器通过总线互联,所述处理器通过执行所述存储器中存储的指令,使得所述基站可执行上述数据传输方法。
本申请实施例提供一种芯片上系统或系统芯片,所述芯片上系统或系统芯片可应用于网络设备,所述芯片上系统或系统芯片包括:至少一个通信接口,至少一个处理器,至少一个存储器,所述通信接口、存储器和处理器通过总线互联,所述处理器通过执行所述存储器中存储的指令,使得所述基站可执行上述数据传输方法。
实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一可读取存储器中。该程序在执行时,执行包括上述各方法实施例的步骤;而前述的存储器(存储介质)包括:只读存储器(英文:read-only memory,缩写:ROM)、RAM、快闪存储器、硬盘、固态硬盘、磁带(英文:magnetic tape)、软盘(英文:floppy disk)、光盘(英文:optical disc)及其任意组合。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理单元以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理单元执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
在本申请中,术语“包括”及其变形可以指非限制性的包括;术语“或”及其变形可以指“和/或”。 本本申请中术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。本申请中,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。

Claims (78)

  1. 一种数据传输方法,其特征在于,包括:
    终端设备接收网络设备发送的下行控制信息DCI;
    所述终端设备根据所述DCI,确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
  2. 根据权利要求1所述的方法,其特征在于,所述终端设备根据所述DCI,确定是否对所述DCI指示的HARQ进程进行反馈,包括:
    所述终端设备根据所述DCI的第一信息,确定是否对所述DCI指示的HARQ进程进行反馈。
  3. 根据权利要求2所述的方法,其特征在于,所述第一信息包括如下信息中的至少一种:
    所述DCI的长度;
    所述DCI对应的无线网络设备临时标识RNTI;
    所述DCI对应的搜索空间;
    所述DCI对应的聚合等级。
  4. 根据权利要求2或3所述的方法,其特征在于,所述终端设备根据所述DCI,确定是否对所述DCI指示的HARQ进程进行反馈,包括:
    所述终端设备根据所述DCI,确定所述HARQ进程的类型,所述HARQ进程的类型为第一类型或者第二类型,所述第一类型的HARQ进程为终端设备不进行反馈的HARQ进程,所述第二类型的HARQ进程为终端设备进行反馈的HARQ进程;
    所述终端设备根据所述HARQ进程的类型,确定是否对所述DCI指示的HARQ进程进行反馈。
  5. 根据权利要求4所述的方法,其特征在于,所述终端设备根据所述HARQ进程的类型,确定是否对所述DCI指示的HARQ进程进行反馈,包括:
    若所述HARQ进程的类型为所述第一类型,则所述终端设备不对所述DCI指示的HARQ进程进行反馈;
    若所述HARQ进程的类型为所述第二类型,则所述终端设备对所述DCI指示的HARQ进程进行反馈。
  6. 根据权利要求4或5所述的方法,其特征在于,所述第一信息为所述DCI的长度;所述终端设备根据所述DCI的第一信息,确定是否对所述DCI指示的HARQ进程进行反馈,包括:
    若所述DCI的长度为第一DCI长度,则所述终端设备确定不对所述HARQ进程进行反馈;或,
    若所述DCI的长度为第二DCI长度,则所述终端设备确定对所述HARQ进程进行反馈。
  7. 根据权利要求6所述的方法,其特征在于,所述第一DCI长度小于所述第二DCI长度。
  8. 根据权利要求6或7所述的方法,其特征在于,
    若根据所述第一DCI长度检测到所述DCI,则所述DCI的长度为所述第一DCI长度;或,
    若根据所述第二DCI长度检测到所述DCI,则所述DCI的长度为所述第二DCI长度。
  9. 根据权利要求6-8任一项所述的方法,其特征在于,
    所述第一DCI长度对应第一聚合等级;
    所述第二DCI长度对应第二聚合等级。
  10. 根据权利要求9所述的方法,其特征在于,所述第一聚合等级小于或等于所述第二聚合等级。
  11. 根据权利要求6-10任一项所述的方法,其特征在于,所述DCI的长度为第一DCI长度;所述DCI不包括如下信息域中的一种或多种:
    物理上行控制信道PUCCH的发射功率控制TPC命令;
    下行分配指示DAI;
    PUCCH资源指示;
    物理下行共享信道PDSCH到HARQ反馈的定时指示;
    单次HARQ-ACK反馈请求;
    PDSCH分组指示;
    新反馈指示NFI;
    触发反馈组指示。
  12. 根据权利要求6-10任一项所述的方法,其特征在于,所述DCI的长度为第二DCI长度;所述DCI包括如下信息域中的一种或多种:
    PUCCH的TPC命令;
    DAI;
    PUCCH资源指示;
    PDSCH到HARQ反馈的定时指示;
    单次HARQ-ACK反馈请求;
    PDSCH分组指示;
    NFI;
    触发反馈组指示。
  13. 根据权利要求4-12任一项所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测所使用的DCI长度包括所述第一DCI长度。
  14. 根据权利要求4-12任一项所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测所使用的DCI长度包括所述第二DCI长度。
  15. 根据权利要求4-12任一项所述的方法,其特征在于,
    所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述 终端设备进行PDCCH检测所使用的DCI长度包括所述第一DCI长度和所述第二DCI长度。
  16. 根据权利要求4-15任一项所述的方法,其特征在于,所述第一信息为所述DCI对应的RNTI;所述终端设备根据所述DCI的第一信息,确定是否对所述DCI指示的HARQ进程进行反馈,包括:
    若根据第一RNTI检测到所述DCI,则所述终端设备确定不对所述HARQ进程进行反馈;或,
    若根据第二RNTI检测到所述DCI,则所述终端设备确定对所述HARQ进程进行反馈。
  17. 根据权利要求16所述的方法,其特征在于,
    若根据所述第一RNTI检测到所述DCI,则所述DCI对应的RNTI为所述第一RNTI;或,
    若根据所述第二RNTI检测到所述DCI,则所述DCI对应的RNTI为所述第二RNTI。
  18. 根据权利要求16或17所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测所使用的RNTI包括所述第一RNTI。
  19. 根据权利要求16或17所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测所使用的RNTI包括所述第二RNTI。
  20. 根据权利要求16或17所述的方法,其特征在于,
    所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测所使用的RNTI包括所述第一RNTI和所述第二RNTI。
  21. 根据权利要求4-20任一项所述的方法,其特征在于,所述第一信息为所述DCI对应的搜索空间;所述终端设备根据所述DCI的第一信息,确定是否对所述DCI指示的HARQ进程进行反馈,包括:
    若所述DCI对应的搜索空间为第一搜索空间,则所述终端设备确定不对所述HARQ进程进行反馈;或,
    若所述DCI对应的搜索空间为第二搜索空间,则所述终端设备确定对所述HARQ进程进行反馈。
  22. 根据权利要求21所述的方法,其特征在于,
    若在所述第一搜索空间中检测到所述DCI,则所述DCI对应的搜索空间为所述第一搜索空间;或,
    若在所述第二搜索空间中检测到所述DCI,则所述DCI对应的搜索空间为所述第二搜索空间。
  23. 根据权利要求21或22所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测的搜索空间包括所述第一搜索空间。
  24. 根据权利要求21或22所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的搜索空间包括所述第二搜索空间。
  25. 根据权利要求21或22所述的方法,其特征在于,
    所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的搜索空间包括所述第一搜索空间和所述第二搜索空间。
  26. 根据权利要求4-25任一项所述的方法,其特征在于,所述第一信息为所述DCI对应的聚合等级;所述终端设备根据所述DCI的第一信息,确定是否对所述DCI指示的HARQ进程进行反馈,包括:
    若所述DCI对应的聚合等级为第一聚合等级,则所述终端设备确定不对所述HARQ进程进行反馈;或,
    若所述DCI对应的聚合等级为第二聚合等级,则所述终端设备确定对所述HARQ进程进行反馈。
  27. 根据权利要求26所述的方法,其特征在于,
    若根据所述第一聚合等级检测到所述DCI,则所述DCI对应的聚合等级为所述第一聚合等级;或,
    若根据所述第二聚合等级检测到所述DCI,则所述DCI对应的聚合等级为所述第二聚合等级。
  28. 根据权利要求26或27所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第一类型,所述终端设备进行PDCCH检测的聚合等级包括所述第一聚合等级。
  29. 根据权利要求26或27所述的方法,其特征在于,
    所述终端设备中的HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的聚合等级包括所述第二聚合等级。
  30. 根据权利要求26或27所述的方法,其特征在于,
    所述终端设备中的部分HARQ进程被配置为第一类型,部分HARQ进程被配置为第二类型,所述终端设备进行PDCCH检测的聚合等级包括所述第一聚合等级和所述第二聚合等级。
  31. 根据权利要求1-30任一项所述的方法,其特征在于,所述方法还包括:
    所述终端设备接收所述网络设备发送的第二信息,所述第二信息用于配置所述终端设备中的至少一个HARQ进程的类型。
  32. 根据权利要求31所述的方法,其特征在于,所述第二信息包括如下信息中的至少一种:
    无线资源控制RRC信令;
    DCI;
    媒质接入控制MAC控制单元CE。
  33. 根据权利要求31或32所述的方法,其特征在于,所述终端设备根据所述DCI,确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈,包括:
    在所述终端设备根据所述DCI确定得到的所述HARQ进程的类型与所述第二信息指示的所述HARQ进程的类型相同时,所述终端设备执行如下步骤:
    根据所述DCI确定是否对所述DCI指示的HARQ进程进行反馈。
  34. 根据权利要求31或32所述的方法,其特征在于,所述方法还包括:
    在所述终端设备根据所述DCI确定得到的所述HARQ进程的类型与所述第二信息指示的所述HARQ进程的类型不相同时,所述终端设备丢弃所述DCI或者不接收所述DCI对应的PDSCH。
  35. 根据权利要求1-34任一项所述的方法,其特征在于,所述DCI指示对所述DCI指示的HARQ进程进行反馈,所述DCI中包括单次HARQ-ACK反馈请求。
  36. 根据权利要求35所述的方法,其特征在于,所述方法还包括:
    在所述单次HARQ-ACK反馈请求被触发时,所述终端设备向所述网络设备发送所述终端设备中的HARQ进程对应的反馈信息。
  37. 一种数据传输方法,其特征在于,包括:
    网络设备确定终端设备的下行控制信息DCI;
    所述网络设备向所述终端设备发送所述DCI,所述DCI用于所述终端设备确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
  38. 根据权利要求36所述的方法,其特征在于,网络设备确定终端设备的DCI,包括:
    所述网络设备根据所述HARQ进程的类型确定所述DCI;
    其中,所述HARQ进程的类型为第一类型或者第二类型,所述第一类型的HARQ进程为终端设备不进行反馈的HARQ进程,所述第二类型的HARQ进程为终端设备进行反馈的HARQ进程。
  39. 根据权利要求38所述的方法,其特征在于,所述网络设备根据所述HARQ进程的类型确定所述DCI,包括:
    所述网络设备根据所述HARQ进程的类型确定所述DCI的第一信息。
  40. 根据权利要求39所述的方法,其特征在于,所述第一信息包括如下信息中的至少一种:
    所述DCI的长度;
    所述DCI对应的无线网络设备临时标识RNTI;
    所述DCI对应的搜索空间;
    所述DCI对应的聚合等级。
  41. 根据权利要求39或40所述的方法,其特征在于,所述第一信息为所述DCI的长度;所述网络设备根据所述HARQ进程的类型确定所述DCI的第一信息,包括:
    若所述HARQ进程的类型为所述第一类型,所述网络设备确定所述DCI的长度为第一DCI长度;或,
    若所述HARQ进程的类型为所述第二类型,所述网络设备确定所述DCI的长度为第二DCI长度。
  42. 根据权利要求41所述的方法,其特征在于,所述第一DCI长度小于所述第二DCI长度。
  43. 根据权利要求41或42所述的方法,其特征在于,所述DCI的长度为第一DCI长度;所述DCI不包括如下信息域中的至少一种:
    物理上行控制信道PUCCH的TPC命令;
    下行分配指示DAI;
    物理上行控制信道PUCCH资源指示;
    物理下行共享信道PDSCH到HARQ反馈的定时指示;
    单次HARQ-ACK反馈请求;
    PDSCH分组指示;
    新反馈指示NFI;
    触发反馈组指示。
  44. 根据权利要求41或42所述的方法,其特征在于,所述DCI的长度为第二DCI长度;所述DCI包括如下信息域中的至少一种:
    PUCCH的TPC命令;
    DAI;
    PUCCH资源指示;
    PDSCH到HARQ反馈的定时指示;
    单次HARQ-ACK反馈请求;
    PDSCH分组指示;
    NFI;
    触发反馈组指示。
  45. 据权利要求39-44任一项所述的方法,其特征在于,所述第一信息为所述DCI对应的RNTI;所述网络设备根据所述HARQ进程的类型确定所述DCI的第一信息,包括:
    所述HARQ进程的类型为所述第一类型,所述网络设备确定所述DCI对应的RNTI为第一RNTI;或,
    所述HARQ进程的类型为所述第二类型,所述网络设备确定所述DCI对应的RNTI为第二RNTI。
  46. 据权利要求39-45任一项所述的方法,其特征在于,所述第一信息为所述DCI对应的搜索空间;所述网络设备根据所述HARQ进程的类型确定所述DCI的第一信息,包括:
    所述HARQ进程的类型为所述第一类型,所述网络设备确定所述DCI对应的搜索空间为第一搜索空间;或,
    所述HARQ进程的类型为所述第二类型,所述网络设备确定所述DCI对应的搜索空间为第二搜索空间。
  47. 根据权利要求38-45任一项所述的方法,其特征在于,所述第一信息为所述DCI对应的聚合等级;所述网络设备根据所述HARQ进程的类型确定所述DCI的第一信息,包括:
    所述HARQ进程的类型为所述第一类型,所述网络设备确定所述DCI对应的聚合等级为第一聚合等级;或,
    所述HARQ进程的类型为所述第二类型,所述网络设备确定所述DCI对应的聚合等级为第二聚合等级。
  48. 一种数据传输装置,其特征在于,包括接收模块和处理模块,其中,
    所述接收模块用于,接收网络设备发送的下行控制信息DCI;
    所述处理模块用于,根据所述DCI,确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
  49. 根据权利要求48所述的装置,其特征在于,所述处理模块具体用于:
    根据所述DCI的第一信息,确定是否对所述DCI指示的HARQ进程进行反馈。
  50. 根据权利要求49所述的装置,其特征在于,所述第一信息包括如下信息中的至少一种:
    所述DCI的长度;
    所述DCI对应的无线网络设备临时标识RNTI;
    所述DCI对应的搜索空间;
    所述DCI对应的聚合等级。
  51. 根据权利要求49或50所述的装置,其特征在于,所述处理模块具体用于:
    根据所述DCI,确定所述HARQ进程的类型,所述HARQ进程的类型为第一类型或者第二类型,所述第一类型的HARQ进程为终端设备不进行反馈的HARQ进程,所述第二类型的HARQ进程为终端设备进行反馈的HARQ进程;
    根据所述HARQ进程的类型,确定是否对所述DCI指示的HARQ进程进行反馈。
  52. 根据权利要求51所述的装置,其特征在于,所述处理模块具体用于:
    若所述HARQ进程的类型为所述第一类型,则对所述DCI指示的HARQ进程进行反馈;
    若所述HARQ进程的类型为所述第二类型,则不对所述DCI指示的HARQ进程进行反馈。
  53. 根据权利要求51或52所述的装置,其特征在于,所述第一信息为所述DCI的长度;所述处理模块具体用于:
    若所述DCI的长度为第一DCI长度,则确定不对所述HARQ进程进行反馈;或,
    若所述DCI的长度为第二DCI长度,则确定对所述HARQ进程进行反馈。
  54. 根据权利要求53所述的装置,其特征在于,所述第一DCI长度小于所述第二DCI长度。
  55. 根据权利要求53或54所述的装置,其特征在于,
    若根据所述第一DCI长度检测到所述DCI,则所述DCI的长度为所述第一DCI长度;或,
    若根据所述第二DCI长度检测到所述DCI,则所述DCI的长度为所述第二DCI长度。
  56. 根据权利要求49-55任一项所述的装置,其特征在于,所述第一信息为所述DCI对应的RNTI;所述处理模块具体用于:
    若所述DCI对应的RNTI为第一RNTI,则确定不对所述HARQ进程进行反馈;或,
    若所述DCI对应的RNTI为第二RNTI,则确定对所述HARQ进程进行反馈。
  57. 根据权利要求56所述的装置,其特征在于,
    若根据所述第一RNTI检测到所述DCI,则所述DCI对应的RNTI为所述第一RNTI;或,
    若根据所述第二RNTI检测到所述DCI,则所述DCI对应的RNTI为所述第二RNTI。
  58. 根据权利要求49-57任一项所述的装置,其特征在于,所述第一信息为所述DCI对应的搜索空间;所述处理模块具体用于:
    若所述DCI对应的搜索空间为第一搜索空间,则确定不对所述HARQ进程进行反馈;或,
    若所述DCI对应的搜索空间为第二搜索空间,则确定对所述HARQ进程进行反馈。
  59. 根据权利要求58所述的装置,其特征在于,
    若在所述第一搜索空间中检测到所述DCI,则所述DCI对应的搜索空间为所述第一搜索空间;或,
    若在所述第二搜索空间中检测到所述DCI,则所述DCI对应的搜索空间为所述第二搜索空间。
  60. 根据权利要求49-59任一项所述的装置,其特征在于,所述第一信息为所述DCI对应的聚合等级;所述处理模块具体用于:
    若所述DCI对应的聚合等级为第一聚合等级,则确定不对所述HARQ进程进行反馈;或,
    若所述DCI对应的聚合等级为第二聚合等级,则确定对所述HARQ进程进行反馈。
  61. 根据权利要求60所述的装置,其特征在于,
    若根据所述第一聚合等级检测到所述DCI,则所述DCI对应的聚合等级为所述第一聚合等级;或,
    若根据所述第二聚合等级检测到所述DCI,则所述DCI对应的聚合等级为所述第二聚合等级。
  62. 根据权利要求48-61任一项所述的装置,其特征在于,所述接收模块还用于:
    接收所述网络设备发送的第二信息,所述第二信息用于配置终端设备中的至少一个HARQ进程的类型。
  63. 根据权利要求62所述的装置,其特征在于,所述第二信息包括如下信息中的至少一种:
    无线资源控制RRC信令;
    DCI;
    媒质接入控制MAC控制单元CE。
  64. 根据权利要求62或63所述的装置,其特征在于,所述处理模块具体用于:
    在所述处理模块根据所述DCI确定得到的所述HARQ进程的类型与所述第二信息指示的所述HARQ进程的类型相同时,执行如下步骤:根据所述DCI确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
  65. 根据权利要求62或63所述的装置,其特征在于,所述处理模块还用于:
    在所述处理模块根据所述DCI确定得到的所述HARQ进程的类型与所述第二信息指示的所述HARQ进程的类型不相同时,丢弃所述DCI或者不接收所述DCI对应的PDSCH。
  66. 根据权利要求48-65任一项所述的装置,其特征在于,所述DCI指示对所述DCI指示的HARQ进程进行反馈,所述DCI中包括单次HARQ-ACK反馈请求。
  67. 一种数据传输装置,其特征在于,包括:处理模块和发送模块,其中,
    所述处理模块用于,确定终端设备的下行控制信息DCI;
    所述发送模块用于,向所述终端设备发送所述DCI,所述DCI用于所述终端设备确定是否对所述DCI指示的混合自动重传请求HARQ进程进行反馈。
  68. 根据权利要求67所述的装置,其特征在于,所述处理模块具体用于:
    根据所述HARQ进程的类型确定所述DCI;
    其中,所述HARQ进程的类型为第一类型或者第二类型,所述第一类型的HARQ进程为终端设备不进行反馈的HARQ进程,所述第二类型的HARQ进程为终端设备进行反馈的HARQ进程。
  69. 根据权利要求68所述的装置,其特征在于,所述处理模块具体用于:
    根据所述HARQ进程的类型确定所述DCI的第一信息。
  70. 根据权利要求69所述的装置,其特征在于,所述第一信息包括如下信息中的至少一种:
    所述DCI的长度;
    所述DCI对应的无线网络设备临时标识RNTI;
    所述DCI对应的搜索空间;
    所述DCI对应的聚合等级。
  71. 根据权利要求69或70所述的装置,其特征在于,所述第一信息为所述DCI的长度;所述处理模块具体用于:
    若所述HARQ进程的类型为所述第一类型,确定所述DCI的长度为第一DCI长度;或,
    若所述HARQ进程的类型为所述第二类型,确定所述DCI的长度为第二DCI长度。
  72. 根据权利要求71所述的装置,其特征在于,所述第一DCI长度小于所述第二DCI长度。
  73. 据权利要求69-72任一项所述的装置,其特征在于,所述第一信息为所述DCI对应的RNTI;所述处理模块具体用于:
    所述HARQ进程的类型为所述第一类型,确定所述DCI对应的RNTI为第一RNTI;或,
    所述HARQ进程的类型为所述第二类型,确定所述DCI对应的RNTI为第二RNTI。
  74. 据权利要求69-73任一项所述的装置,其特征在于,所述第一信息为所述DCI对应的搜索空间;所述处理模块具体用于:
    所述HARQ进程的类型为所述第一类型,确定所述DCI对应的搜索空间为第一搜索空间;或,
    所述HARQ进程的类型为所述第二类型,确定所述DCI对应的搜索空间为第二搜索空间。
  75. 据权利要求69-74任一项所述的装置,其特征在于,所述第一信息为所述DCI对应的聚合等级;所述处理模块具体用于:
    所述HARQ进程的类型为所述第一类型,确定所述DCI对应的聚合等级为第一聚合等级;或,
    所述HARQ进程的类型为所述第二类型,确定所述DCI对应的聚合等级为第二聚合等级。
  76. 一种终端设备,其特征在于,包括:收发器、处理器、存储器;
    所述存储器存储计算机执行指令;
    所述处理器执行所述存储器存储的计算机执行指令,使得所述处理器执行如权利要求1至36任一项所述的数据传输方法。
  77. 一种网络设备,其特征在于,包括:收发器、处理器、存储器;
    所述存储器存储计算机执行指令;
    所述处理器执行所述存储器存储的计算机执行指令,使得所述处理器执行如权利要求37至47任一项所述的数据传输方法。
  78. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有计算机执行指令,当所述计算机执行指令被处理器执行时用于实现权利要求1至36任一项所述的数据传输方法,或者权利要求37至47任一项所述的数据传输方法。
PCT/CN2020/077279 2020-02-28 2020-02-28 数据传输方法、装置及设备 WO2021168834A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080079577.XA CN114731690A (zh) 2020-02-28 2020-02-28 数据传输方法、装置及设备
PCT/CN2020/077279 WO2021168834A1 (zh) 2020-02-28 2020-02-28 数据传输方法、装置及设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/077279 WO2021168834A1 (zh) 2020-02-28 2020-02-28 数据传输方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2021168834A1 true WO2021168834A1 (zh) 2021-09-02

Family

ID=77490636

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/077279 WO2021168834A1 (zh) 2020-02-28 2020-02-28 数据传输方法、装置及设备

Country Status (2)

Country Link
CN (1) CN114731690A (zh)
WO (1) WO2021168834A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115004596A (zh) * 2022-04-25 2022-09-02 北京小米移动软件有限公司 混合自动重传请求harq反馈的处理方法及其装置
CN115004597A (zh) * 2022-04-25 2022-09-02 北京小米移动软件有限公司 混合自动重传请求harq反馈的处理方法及其装置
WO2023045794A1 (zh) * 2021-09-24 2023-03-30 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
WO2024077457A1 (en) * 2022-10-10 2024-04-18 Nokia Shanghai Bell Co., Ltd. Subframe based hybrid automatic repeat request feedback

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055319A1 (zh) * 2022-09-16 2024-03-21 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107733582A (zh) * 2016-08-10 2018-02-23 华为技术有限公司 发送指示信息和harq‑ack的方法及设备
CN108353313A (zh) * 2015-11-05 2018-07-31 株式会社Ntt都科摩 用户终端、无线基站以及无线通信方法
US20200044790A1 (en) * 2018-08-01 2020-02-06 Charter Communications Operating, Llc Disabling hybrid automatic repeat request (harq) acknowledgments for packets for which acknowledgements are supported at network or higher layer
WO2020038340A1 (zh) * 2018-08-20 2020-02-27 华为技术有限公司 一种harq反馈方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108353313A (zh) * 2015-11-05 2018-07-31 株式会社Ntt都科摩 用户终端、无线基站以及无线通信方法
CN107733582A (zh) * 2016-08-10 2018-02-23 华为技术有限公司 发送指示信息和harq‑ack的方法及设备
US20200044790A1 (en) * 2018-08-01 2020-02-06 Charter Communications Operating, Llc Disabling hybrid automatic repeat request (harq) acknowledgments for packets for which acknowledgements are supported at network or higher layer
WO2020038340A1 (zh) * 2018-08-20 2020-02-27 华为技术有限公司 一种harq反馈方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "Summary for more delay-tolerant re-transmission mechanisms in NR-NTN", 3GPP DRAFT; R1-1907656-MEDIATEK-SUMMARY DELAY-TOLERANT TRANSMISSION MECHANISMS IN NR-NTN-V01, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, Nevada, USA; 20190513 - 20190517, 16 May 2019 (2019-05-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051739945 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023045794A1 (zh) * 2021-09-24 2023-03-30 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN115004596A (zh) * 2022-04-25 2022-09-02 北京小米移动软件有限公司 混合自动重传请求harq反馈的处理方法及其装置
CN115004597A (zh) * 2022-04-25 2022-09-02 北京小米移动软件有限公司 混合自动重传请求harq反馈的处理方法及其装置
WO2023206033A1 (zh) * 2022-04-25 2023-11-02 北京小米移动软件有限公司 混合自动重传请求harq反馈的处理方法及其装置
WO2023206034A1 (zh) * 2022-04-25 2023-11-02 北京小米移动软件有限公司 混合自动重传请求harq反馈的处理方法及其装置
WO2024077457A1 (en) * 2022-10-10 2024-04-18 Nokia Shanghai Bell Co., Ltd. Subframe based hybrid automatic repeat request feedback

Also Published As

Publication number Publication date
CN114731690A (zh) 2022-07-08

Similar Documents

Publication Publication Date Title
WO2021168834A1 (zh) 数据传输方法、装置及设备
WO2021168833A1 (zh) 数据传输方法、装置及设备
WO2022027195A1 (zh) Harq反馈的处理方法及装置、存储介质
WO2015141728A1 (ja) 通信制御方法及びユーザ端末
WO2021237721A1 (zh) Harq-ack码本的反馈方法和终端设备
WO2022150937A1 (zh) 用于接收数据的方法与装置和用于发送数据的方法与装置
WO2021168835A1 (zh) Harq进程的状态确定方法、装置及设备
WO2021237702A1 (zh) Harq-ack码本的反馈方法和终端设备
US20230231665A1 (en) Method for feeding back hybrid automatic repeat request acknowledgement (harq-ack) and terminal device
WO2020248258A1 (zh) 无线通信方法、收端设备和发端设备
WO2022021007A1 (zh) 无线通信方法、终端设备和网络设备
WO2022061661A1 (zh) 无线通信的方法、终端设备和网络设备
WO2021217378A1 (zh) 无线通信方法、终端设备和网络设备
CN116114197B (zh) 无线通信的方法、终端设备和网络设备
CN115580380A (zh) 无线通信的方法及装置
WO2021226851A1 (zh) Harq-ack码本的反馈方法、终端设备和网络设备
WO2021163968A1 (zh) 用于确定混合自动重传请求信息的方法、终端设备和网络设备
WO2021007778A1 (en) Method and apparatus for resource allocation in v2x communication
CN115804202B (zh) 无线通信方法、终端设备和网络设备
WO2022205436A1 (zh) 无线通信的方法及终端设备
WO2023279399A1 (zh) 侧行传输资源的确定方法、发送方法、装置、设备及介质
WO2022077481A1 (zh) 一种信道传输方法及其装置
WO2023004584A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023108351A1 (zh) 无线通信的方法及终端设备
WO2024055319A1 (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: 20922274

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

Country of ref document: EP

Kind code of ref document: A1