WO2020098685A1 - Procédé de réception de données et appareil de communication - Google Patents

Procédé de réception de données et appareil de communication Download PDF

Info

Publication number
WO2020098685A1
WO2020098685A1 PCT/CN2019/117935 CN2019117935W WO2020098685A1 WO 2020098685 A1 WO2020098685 A1 WO 2020098685A1 CN 2019117935 W CN2019117935 W CN 2019117935W WO 2020098685 A1 WO2020098685 A1 WO 2020098685A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcch
harq process
pdsch
network device
configuration
Prior art date
Application number
PCT/CN2019/117935
Other languages
English (en)
Chinese (zh)
Inventor
王潇涵
杭海存
葛士斌
纪刘榴
毕晓艳
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020098685A1 publication Critical patent/WO2020098685A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal

Definitions

  • the present application relates to the field of wireless communication, and more specifically, to a method and a communication device for receiving data.
  • Coordinated multiple point (Coordination multiple point, CoMP) transmission is a method for solving inter-cell interference problems and improving the throughput of cell edge users.
  • a network device such as a transmission and reception point (TRP) can schedule a physical downlink shared channel (PDSCH) for the terminal device through downlink control information (DCI).
  • the network device can indicate to the terminal device which HARQ corresponds to the transport block (TB) carried by the hybrid automatic repeat request (HARQ) process number (HARQ) process number (HPN) in the DCI to the terminal device process.
  • HARQ hybrid automatic repeat request
  • HPN hybrid automatic repeat request
  • a multi-site scheduling based on multiple DCIs (hereinafter may be referred to as multiple DCI-based Multi-site scheduling) is proposed.
  • multiple sites send DCI to schedule the respective PDSCH to the same terminal device, because the HARQ process between the sites cannot be coordinated, the terminal device may not be able to accurately determine the correspondence of each PDSCH based on the HARQ process number when receiving the PDSCH from multiple sites HARQ process. Therefore, the data transmission performance is affected.
  • the present application provides a data receiving method and a communication device, with a view to improving data transmission performance.
  • a method of receiving data is provided.
  • the method may be executed by the terminal device, or may be executed by a chip configured in the terminal device. This application does not limit this.
  • the method includes: receiving a PDSCH, the PDSCH is scheduled by a PDCCH, and the DCI carried by the PDCCH includes an indication of a HARQ process number; according to the HARQ process number and one or more of the following, the HARQ process corresponding to the PDSCH is determined: the PDCCH Configuration parameters, the network device group that sends the PDSCH, the port of the demodulation reference signal (DMRS) indicated in DCI, and the bandwidth part (BWP); the data carried by the PDSCH is processed according to the determined HARQ process.
  • DMRS demodulation reference signal
  • the terminal device may determine the first PDSCH according to one or more of the HARQ process number, the configuration parameters of the PDCCH, the network device group that sends the first PDSCH, the DMRS port indicated in the first DCI, and the BWP
  • the corresponding HARQ process can accurately determine the corresponding HARQ process when multiple PDSCHs are received.
  • the terminal device may not know whether it is currently in a single-site service or a multi-site service scenario.
  • the value range of HARQ process numbers of transport blocks carried by multiple PDSCHs may be the same. It may happen that the same HARQ process number corresponds to multiple HARQ processes. If the terminal device determines the HARQ process only according to the HARQ process number, it may cause an error in data processing. For example, combining and decoding two transport blocks that are not the same HARQ process results in decoding failure and triggers another retransmission. In fact, two transmission blocks of the same HARQ process can be decoded successfully, only because the terminal device misuses one transmission block and causes unnecessary retransmissions, thus affecting the data transmission performance.
  • the terminal device determines the PDSCH by combining one or more of the HARQ process number and the configuration parameter of the PDCCH, the port group to which the DMRS port belongs, the BWP, and the network device group that sends the first PDSCH
  • the corresponding HARQ process can accurately determine the HARQ process corresponding to the PDSCH, thereby avoiding errors that may occur in the data processing process of the terminal device, which is beneficial to improve data transmission performance.
  • the configuration parameters of the PDCCH include: the PDCCH configuration of the PDCCH, the BWP downlink dedicated parameter to which the PDCCH configuration belongs, the BWP downlink parameter to which the PDCCH configuration belongs, and the The serving cell configuration, the PDCCH control resource set, the control resource set group to which the PDCCH control resource set belongs, the search space set group to which the PDCCH search space set or the PDCCH search space set belongs to.
  • the protocol may be pre-defined according to one of the configuration parameters listed above to be used in combination with the HARQ process number to determine the HARQ process corresponding to the PDSCH.
  • the protocol defines one of the configuration parameters listed above to determine the HARQ process, it can be considered that this configuration parameter has a corresponding relationship with the network device group.
  • the terminal device may consider two or more PDCCHs received based on the same configuration parameter as PDCCHs from the same network device group.
  • the DCI includes an indication of the network device group that sends the PDCCH.
  • the network device group that transmits the PDCCH can be indicated by adding an indication field of the network device group to the DCI. It should be understood that the indication of the network device group through DCI is only one possible implementation manner, and should not constitute any limitation to this application.
  • the terminal device can further distinguish between different scenarios and use different methods to determine the HARQ process corresponding to the PDSCH.
  • the HARQ process corresponding to the PDSCH is determined according to the HARQ process number and one or more of the following: configuration parameters of the PDCCH, network device group that sends the PDSCH, and DCI
  • the indicated port and BWP of the DMRS include: when multiple configuration parameters of the PDCCH are received, the HARQ process corresponding to the PDSCH is determined according to at least the HARQ process number and the configuration parameters of the PDCCH.
  • the terminal device can determine whether it is currently in single-site service or multi-site service according to the number of received PDCCH configuration parameters, and can determine the HARQ process corresponding to the PDSCH based on the above scheme in the scenario of multi-site service; In the site service scenario, the HARQ process corresponding to the PDSSCH is directly determined according to the HARQ process number.
  • the HARQ process corresponding to the PDSCH is determined according to the HARQ process number and one or more of the following: configuration parameters of the PDCCH, network device group that sends the PDSCH, and DCI
  • the indicated DMRS port and BWP include: when receiving the indication of multiple DMRS port groups, the HARQ process corresponding to the PDSCH is determined according to at least the HARQ process number and the port group to which the DMRS port indicated in the DCI belongs.
  • the terminal device can determine whether it is currently in single-site service or multi-site service according to the number of received DMRS port groups, and can determine the HARQ process corresponding to the PDSCH based on the above scheme in the scenario of multi-site service; In the service scenario, the HARQ process corresponding to the PDSSCH is directly determined according to the HARQ process number.
  • the specific way in which the terminal device determines whether to be in the single-site service or the multi-site service is not limited to the above enumeration.
  • the terminal device may also determine whether it is currently in the single-site service or the multi-site service based on other methods.
  • the HARQ process corresponding to the PDSCH is determined according to the HARQ process number and one or more of the following: the configuration parameters of the PDCCH, the network device group that sends the PDSCH, the DMRS port and BWP indicated in the DCI.
  • the DCI includes an indication of multiple transport blocks, and the PDSCH carries one or more transport blocks, and each transport block corresponds to a HARQ process; and the HARQ-based The process number and one or more of the following determine the HARQ process corresponding to the PDSCH: PDCCH configuration parameters, the network device group that sends the PDSCH, the port and BWP of the DMRS indicated in the DCI, including: according to the HARQ process number, the indication of the transport block, and One or more of the following, the HARQ process corresponding to each transport block in the PDSCH is determined: the configuration parameters of the PDCCH, the network device group that sends the PDSCH, the port of the DMRS and the BWP indicated in the DCI.
  • the HARQ process corresponding to the PDSCH may be one or more, corresponding to one or more transport blocks, respectively.
  • the terminal device may further determine the HARQ process corresponding to each transport block in the PDSCH in conjunction with the indication of the transport block in the DCI.
  • a communication device including various modules or units for performing the method in any possible implementation manner of the first aspect.
  • a communication device including a processor.
  • the processor is coupled to the memory, and can be used to execute instructions in the memory to implement the method in any possible implementation manner of the first aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication device is a terminal device.
  • the communication interface may be a transceiver or an input / output interface.
  • the communication device is a chip configured in the terminal device.
  • the communication interface may be an input / output interface.
  • the transceiver may be a transceiver circuit.
  • the input / output interface may be an input / output circuit.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the first aspect and the method in any possible implementation manner of the first aspect.
  • the processor may be a chip
  • the input circuit may be an input pin
  • the output circuit may be an output pin
  • the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to a receiver
  • the signal output by the output circuit may be, for example but not limited to, output to and transmitted by the transmitter
  • the circuit may be the same circuit, which is used as an input circuit and an output circuit at different times, respectively.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter to perform the first aspect and the method in any possible implementation manner of the first aspect.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor are provided separately.
  • the memory may be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which may be integrated with the processor on the same chip, or may be separately set in different On the chip, the embodiments of the present application do not limit the type of memory and the manner of setting the memory and the processor.
  • a non-transitory memory such as a read-only memory (read only memory, ROM)
  • ROM read only memory
  • sending instruction information may be a process of outputting instruction information from the processor
  • receiving capability information may be a process of receiving input capability information by the processor.
  • the data output by the processor may be output to the transmitter, and the input data received by the processor may come from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the processing device in the fifth aspect may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc .; when implemented by software
  • the processor may be a general-purpose processor, implemented by reading software codes stored in a memory, the memory may be integrated in the processor, or may be located outside the processor and exist independently.
  • a computer program product includes: a computer program (also referred to as code or instructions) that, when the computer program is executed, causes the computer to perform the first aspect and the above On the one hand, any possible implementation method.
  • a computer-readable medium that stores a computer program (also may be referred to as code or instructions) that when executed on a computer, causes the computer to perform the first aspect and the first
  • a computer program also may be referred to as code or instructions
  • FIG. 1 is a schematic diagram of a communication system suitable for a method of sending and receiving data according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for sending and receiving data according to an embodiment of the present application
  • 3 and 4 are schematic diagrams of different HARQ process sets corresponding to different PDCCH configurations provided by embodiments of the present application;
  • FIG. 5 shows the indication bits of transport block # 1 and transport block # 2 in DCI
  • 6 to 10 are schematic diagrams of different HARQ processes corresponding to different PDCCH configurations and different transport blocks provided by embodiments of the present application;
  • FIG. 11 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • GSM global mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • general packet radio service general packet radio service, GPRS
  • LTE long term evolution
  • LTE frequency division duplex FDD
  • TDD time division duplex
  • UMTS universal mobile communication system
  • WiMAX worldwide interoperability for microwave access
  • 5G fifth generation
  • 5G fifth generation
  • NR new radio
  • the network device in the communication system may be any device with a wireless transceiver function or a chip that can be installed in the device.
  • the device includes but is not limited to: evolved Node B (evolved Node B, eNB), wireless Network Controller (Radio Network Controller, RNC), Node B (Node B, NB), Base Station Controller (Base Station, Controller, BSC), Base Transceiver Station (Base Transceiver Station, BTS), Home Base Station (eg, Home evolved NodeB , Or Home Node B, HNB, Base Band Unit (BBU), Wireless Fidelity (WIFI) access point (Access Point, AP), wireless relay node, wireless backhaul node, Transmission point (transmission point, TP) or sending and receiving point (TRP), etc.
  • 5G such as NR, gNB in the system, or, transmission point (TRP or TP), one or a group of base stations in 5G system (Including multiple antenna panels)
  • An antenna panel or, may be a
  • gNB may include a centralized unit (CU) and DU.
  • the gNB may also include a radio unit (RU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB, for example, CU implements radio resource control (RRC), packet data convergence layer protocol (packet, data, protocol, PDCP) layer functions
  • DU implements wireless chain Road control (radio link control, RLC), media access control (media access control, MAC) and physical (physical, PHY) layer functions.
  • RRC radio resource control
  • RLC radio link control
  • media access control media access control
  • MAC media access control
  • PHY physical
  • the network device may be a CU node, or a DU node, or a device including a CU node and a DU node.
  • the CU can be divided into network devices in the access network RAN, and can also be divided into network devices in the core network CN, which is not limited herein.
  • terminal equipment in the communication system may also be called user equipment (user equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user Terminal, terminal, wireless communication device, user agent or user device.
  • UE user equipment
  • access terminal subscriber unit
  • subscriber unit user station
  • mobile station mobile station
  • remote station remote terminal
  • mobile device user Terminal
  • terminal wireless communication device
  • wireless communication device user agent or user device.
  • the terminal device in the embodiments of the present application may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Wireless terminals in equipment, industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical (remote medical), wireless terminals in smart grid (smart grid), transportation safety ( Wireless terminals in transportation, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the embodiments of the present application do not limit the application scenarios.
  • HARQ uses the stop-and-wait protocol to send data. Take the following transmission as an example. After sending a transmission block, the network device stops and waits for confirmation. The terminal device can confirm the acknowledgement (acknowledgement, ACK) or negative (negative acknowledgement, NACK) of the transport block through the HARQ information. However, after each transmission, the terminal equipment stops to wait for confirmation, which will result in a very low throughput. Therefore, the terminal device can use multiple parallel HARQ processes. When one HARQ process is waiting for confirmation information, the terminal device can use another HARQ process to continue sending data.
  • acknowledgement acknowledgement
  • NACK negative acknowledgement
  • the HARQ process number is also called HARQ process identifier (ID).
  • ID HARQ process identifier
  • a HARQ process number can be used to indicate a HARQ process.
  • a HARQ process can process a transport block in a unit of time. Therefore, one HARQ process can correspond to one transport block. The correspondence between the transport block and the HARQ process can be reflected by the correspondence between the transport block and the HARQ process number.
  • the terminal device can decode the received transport block. For the transmission block of the initial transmission, the terminal device may decode successfully or fail. Although the transport block that failed to be decoded cannot be decoded correctly, it may contain useful information.
  • the terminal device can store it in a buffer.
  • the cache may be a cache pool.
  • the cache may be a HARQ cache in the prior art.
  • the buffer may be located at the physical layer, so that the physical layer performs soft combining and decoding on the received data.
  • the terminal device When receiving the retransmitted transport block, the terminal device can obtain the transport block of the same HARQ process from the HARQ buffer and merge it with the retransmitted transport block, so that a transport block that is more reliable than individual decoding can be obtained.
  • the terminal device can decode the combined transmission block, so that the success rate of decoding can be improved, and thus the transmission performance can be improved.
  • the transmission block corresponding to the HARQ process indicated by the HARQ process number may be a transmission block for initial transmission or a transmission block for retransmission. This application does not limit this.
  • successfully decoded transport block can also be stored in the HARQ buffer. This application does not limit this.
  • Transmission block it can be a data block from a high layer.
  • a transmission block may include, for example, a data block of a media access control (MAC) protocol data unit (protocol, data, unit, PDU).
  • the data block may be transmitted in a time unit, or may be retransmitted by HARQ. unit.
  • the time unit may be a transmission time interval (transmission time interval, TTI).
  • a network device can send up to two transport blocks per time unit.
  • each network device can send one transport block per time unit.
  • each network device may also send two transmission blocks or more transmission blocks per time unit. This application does not limit this.
  • Control resource set (CORESET) and control resource set (CORESET) group The control resource set may be a resource set used for transmitting downlink control information (downlink control information, DCI), and may also be called a control resource Region, or physical downlink control channel resource set.
  • DCI downlink control information
  • Each control resource set may be a set of resource element groups (resource element group, REG).
  • REG is the basic unit of downlink control signaling for physical resource allocation, and is used to define the mapping of downlink control signaling to resource elements (RE).
  • RE resource elements
  • one REG is composed of 4 REs with continuous non-reference signals (reference signals, RS) in the frequency domain.
  • REG is only a unit for resource allocation and should not constitute any limitation to this application. This application does not exclude the definition of new resource allocation units in future agreements to achieve the same or similar functions.
  • a control resource set can be understood as a set of resources that may be used for sending a PDCCH; for a terminal device, the resources corresponding to the search space of the PDCCH of each terminal device belong to the control resource set.
  • the network device may determine the resource used for sending the PDCCH from the control resource set, and the terminal device may determine the search space of the PDCCH according to the control resource set.
  • the control resource set may include time-frequency resources.
  • the frequency domain may be a section of bandwidth, or one or more subbands, etc .; the time domain may be one or more symbols; and the control resource set may be time-frequency domain. It is a continuous or discontinuous resource unit, for example, a continuous resource block (resource block (RB) or a discontinuous RB).
  • RB resource block
  • RB discontinuous RB
  • RB is an example of a resource unit
  • the size of RB may be a resource defined in the NR protocol or a resource defined in a future protocol, or it may be replaced with another name.
  • the control resource set may also be one or more time slots, radio frames, subframes, mini slots (mini slots or sub slots), or transmission time intervals (transmission time interval, TTI) in the time domain.
  • TTI transmission time interval
  • the control resource set may be configured by a control resource set information element (ControlResourceSet information) element in a high-level parameter, for example.
  • the high-level parameters may include, for example, an identifier (ID) of the control resource set, a frequency domain resource, and the number of symbols included in the duration (duration). This application does not limit the specific parameters used to configure the control resource set.
  • a control resource set group may include one or more control resource sets.
  • the control resource set included in the control resource set group may be configured by high-level parameters, for example.
  • it can be configured through the PDCCH configuration information element (PDCCH-Config information, PDCCH-Config), or through the ControlResourceSet information element, which is not limited in this application.
  • PDCCH-Config information PDCCH-Config information, PDCCH-Config
  • ControlResourceSet information element which is not limited in this application.
  • search space set search space set
  • search space set group The search space set may be a set of search spaces described from the perspective of the physical layer. For higher layers, the search space set can also be called a search space. In the embodiment of the present application, in order to distinguish it from the search space described below, it is referred to as a search space set in the present application.
  • the network device can configure the search space set through high-level parameters, for example, through a search space information element (SearchSpace information element).
  • the high-level parameters may include, for example, the identifier of the search space set, the identifier of the control resource set, the period and offset of the monitoring slot, the monitoring symbol in the slot, and aggregation level (AL). This application does not limit the specific parameters for configuring the search space.
  • a search space set group may include one or more search space sets.
  • the search space set included in the search space set group can be configured by high-level parameters, for example, can be configured by PDCCH-Config information element, or can be configured by SearchSpace information element, which is not limited in this application.
  • the SearchSpace information element mentioned here is a high-level parameter.
  • the high-level parameter can be considered to be used to configure a set of search spaces.
  • the search space can be understood as a set of search spaces in the physical layer. For brevity, the description of the same or similar cases is omitted below.
  • Search space (SS) the search range for blind detection of the terminal device, or the set of candidate downlink control channels that the terminal device needs to monitor.
  • the physical resources of the search space can be determined jointly by the set of control resources and the set of search spaces.
  • the control resource set may indicate the frequency domain position and duration of the search space
  • the search space set may indicate the starting position of the search space in the time domain, such as the starting time slot.
  • the terminal device may jointly determine the time-frequency resource of the blind detection PDCCH based on the control resource set and the search space set configured in the PDCCH configuration.
  • PDCCH configuration The network device can configure PDCCH parameters based on each bandwidth part (BWP) in each cell, for example, control resource set, control resource set group (CORESET) group, Search space set, search space set group (SS group) and other parameters that can be used for blind detection of PDCCH.
  • the PDCCH configuration may be configured through PDCCH-ConfigIE in the higher layer parameters, for example.
  • the PDCCH-Config IE may include, for example, a control resource set addition status list (controlResourceSetToAddModList) and a control resource set release list (controlResourceSetToReleaseList). Each list may include the identification of one or more control resource sets.
  • the PDCCH-Config IE may also include a search space addition status list (searchSpacesToAddModList) and a search space release list (searchSpacesToReleaseList), for example. Each list may include one or more search space identifiers.
  • each PDCCH configuration may also indicate one or more control resource set groups and / or one or more search space groups.
  • the control resource set increase status list in the PDCCH-Config IE may include one or more control resource set groups and the identifiers of the control resource sets contained in each control resource set group.
  • the search space increase list in the PDCCH-Config IE may include one or more search space groups and the search space identifiers included in each search space group.
  • One or more search spaces can be determined by PDCCH configuration.
  • the PDCCH configuration of the PDCCH can be understood as the PDCCH configuration on which the PDCCH is received, or in other words, the terminal device blindly detects the PDCCH in the search space determined by the PDCCH configuration;
  • the PDCCH configuration of the PDCCH can be understood as the PDCCH configuration on which the PDCCH is transmitted, or in other words, the network device transmits the PDCCH on a part of resources in the search space determined by the PDCCH configuration.
  • Serving cell configuration It can be used to configure serving cell for terminal equipment.
  • the network device can configure the serving cell for the terminal device through high-level parameters, such as a serving cell configuration control element (ServingCellConfig information).
  • ServingCellConfig information a serving cell configuration control element
  • one serving cell configuration may include one or more sets of bandwidth part (BWP) downlink parameters, uplink configuration (uplink) configuration, and CSI measurement configuration (CSI-MeasConfig).
  • BWP bandwidth part
  • uplink configuration uplink
  • CSI-MeasConfig CSI measurement configuration
  • Each group of BWP downlink parameters may be configured for one BWP.
  • the BWP ID may be indicated in the BWP downlink parameters.
  • Each group of BWP upstream parameters may also be configured for one BWP.
  • the BWP ID may be indicated in the BWP downstream parameters.
  • Each group of BWP downlink parameters may include BWP downlink dedicated (DL dedicated) parameters and BWP downlink common (DL common) parameters, where the BWP downlink dedicated parameters may specifically include PDCCH configuration and PDSCH configuration.
  • Each group of BWP uplink parameters may include BWP uplink dedicated parameters (uplink dedicated, UL dedicated) and BWP uplink common parameters (UP common), where the BWP uplink dedicated parameters may specifically include PUCCH configuration and PUSCH configuration.
  • the CSI measurement configuration may include one or more CSI reporting configurations.
  • the common parameters can be understood as cell-level (cell-specific) parameters
  • the dedicated parameters can be understood as UE-level parameters.
  • the BWP upstream dedicated parameters can be embodied in the NR protocol as BWP-UplinkDedicated
  • the BWP downstream dedicated parameters can be embodied in the NR protocol as BWP-DownlinkDedicated.
  • Cell or serving cell. It is described by senior management from the perspective of resource management or mobility management or service unit.
  • the coverage of each network device can be divided into one or more serving cells, and the serving cell can be regarded as consisting of a certain frequency domain resource.
  • the cell may be replaced with a serving cell or a component carrier (CC, or component carrier, component carrier, carrier, etc.).
  • CC component carrier
  • component carrier component carrier
  • CC component carrier
  • the network device of cell # 1 and the network device of cell # 2 may be the same network device, and the network device may be, for example, a base station, such as gNB or TRP.
  • a base station such as gNB or TRP.
  • the network device of cell # 1 and the network device of cell # 2 may also be different antenna panels of the same base station.
  • cell # 1 and cell # 2 can be managed by the same base station, have the same baseband processing unit and intermediate frequency processing unit, but have different radio frequency processing units. This application does not specifically limit this.
  • Antenna port (antenna port): referred to as port.
  • One antenna port can be configured for each virtual antenna, each virtual antenna can be a weighted combination of multiple physical antennas, and each antenna port can correspond to one reference signal port.
  • DCI may include an indication field of an antenna port, which may be used to indicate a port of DMRS.
  • the indication field may be an index value, and the correspondence between the index value and the DMRS port may be defined in advance, such as a protocol definition.
  • Each index value may correspond to one DMRS port or a combination of multiple DMRS ports.
  • the terminal device can determine the port of the DMRS.
  • the ports of the DMRS can be distinguished by, for example, port numbers.
  • serial numbers can be started from 0.
  • the value range of the HARQ process number may be 0 to N-1.
  • the specific implementation is not limited to this.
  • it may be consecutively numbered from 1.
  • the value range of the N process numbers can be 1 to N. Since the initial value of the number is different, the HARQ process number corresponding to the same HARQ process is also different.
  • the first, second, and various numerical numbers in the embodiments shown below are only for the convenience of description, and are not intended to limit the scope of the embodiments of the present application. For example, distinguish between different PDCCHs, different PDSCHs, and so on.
  • pre-acquisition may include signaling indication or pre-defined by the network device, for example, protocol definition.
  • pre-defined can be achieved by pre-storing corresponding codes, tables or other methods that can be used to indicate relevant information in the device (for example, including terminal devices and network devices), and this application does not do for its specific implementation limited.
  • "save” referred to in the embodiments of the present application may refer to being saved in one or more memories.
  • the one or more memories may be provided separately or integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partly set separately and partly integrated in a decoder, processor, or communication device.
  • the type of memory may be any form of storage medium, which is not limited in this application.
  • the “protocol” referred to in the embodiments of the present application may refer to standard protocols in the communication field, and may include, for example, the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which are not limited in this application.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • And / or describes the relationship of the related objects, indicating that there can be three relationships, for example, A and / or B, which can mean: A exists alone, A and B exist at the same time, B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related object is a "or” relationship.
  • At least one of the following” or a similar expression refers to any combination of these items, including any combination of a single item or a plurality of items.
  • At least one of a, b, and c can represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a , B and c.
  • a, b, and c may be single or multiple, respectively.
  • FIG. 1 shows a schematic diagram of a communication system 100 suitable for a method of receiving data according to an embodiment of the present application.
  • the communication system 100 may include at least one terminal device, such as the terminal device 101 shown in the figure; the communication system 100 may also include at least one network device, as shown in the network device # 1 102 or Network equipment # 2 103.
  • the communication system 100 may include multiple network devices, such as network device # 1 102 and network device # 2 103 shown in the figure.
  • the network device # 1 102 and the network device # 2 103 may be network devices in the same cell or network devices in different cells, which is not limited in this application.
  • the figure is only an example, and shows an example in which network device # 1102 and network device # 2 103 are located in the same cell.
  • the network device # 1 102 and the network device # 2 103 can communicate with each other through a backhaul link, which can be a wired backhaul link (eg, optical fiber, copper cable), or It is a wireless backhaul link (such as microwave).
  • the network device # 1 102 and the network device # 2 103 can cooperate with each other to provide services for the terminal device 101. Therefore, the terminal device 101 can communicate with the network device # 1 and the network device # 2 and 103 through a wireless link, respectively.
  • one or more of the network device # 1 102 and the network device # 2 103 may also use a carrier aggregation technology to schedule the PDSCH for the terminal device 101 on one or more CCs.
  • network device # 1 102 can schedule PDSCH for terminal device 101 on CC # 1 and CC # 2
  • network device # 2 103 can schedule PDSCH for terminal device 101 on CC # 1 and CC # 3.
  • the CCs scheduled by network device # 1 102 and network device # 2 103 may be the same or different, which is not limited in this application.
  • the communication delay between mutually coordinated network devices can be divided into ideal backhaul and non-ideal backhaul. Between the two sites under ideal backhaul, the communication delay can be in the microsecond level, which can be neglected compared to the millisecond level scheduling in NR; between the two sites under non-ideal backhaul, the communication delay can be in the millisecond level. Compared with the millisecond level scheduling in NR, it cannot be ignored.
  • a multi-site scheduling scheme based on multiple DCIs allows multiple network devices to schedule their respective PDSCHs for terminal devices through their respective DCIs for data transmission.
  • the PDSCHs can completely overlap or partially overlap in time and / or frequency domain resources. Or not overlap.
  • the terminal device independently demodulates its scheduled PDSCH according to the DCI sent by each network device; optionally, the terminal device separately feeds back HARQ information corresponding to the PDSCH sent by different network devices to the corresponding network device.
  • the terminal device can receive a plurality of cell radio network temporary identifiers (cell radio network identifier (C-RNTI) and / or modulation coding scheme (MCS) -C-RNTI scrambled PDCCHs, which can respectively Schedule PDSCHs that completely overlap, partially overlap, or not overlap in the time and / or frequency domain.
  • C-RNTI cell radio network identifier
  • MCS modulation coding scheme
  • the terminal device independently demodulates its corresponding PDSCH according to each PDCCH.
  • the terminal device separately feeds back HARQ information corresponding to its scheduled PDSCH according to the PDCCH attributes.
  • this multi-site scheduling scheme based on multiple DCIs can also be called a multi-DCI scheduling scheme.
  • each DCI may be completely independent, and each contains all information that can be used to schedule the PDSCH.
  • Each DCI can have the same format as the DCI sent by the network device in the single-site scenario in the prior art.
  • Multiple DCIs may also be related, for example, primary DCI and secondary DCI. Regardless of the relationship between multiple DCIs, each DCI contains an indication of the HARQ process number of the scheduled PDSCH.
  • the network device # 1 102 of FIG. 1 may send PDCCH # 1 to the terminal device 101, and the PDCCH # 1 may carry DCI # 1, which may be used to schedule PDSCH # 1 for the terminal device 101, the DCI # 1 may include an indication of the HARQ process number corresponding to the transport block carried in PDSCH # 1.
  • Network device # 2 103 in FIG. 1 may also send PDCCH # 2 to terminal device 101, which may carry DCI # 2, which may be used to schedule PDSCH # 2 and DCI # 2 for terminal device 101 It may include an indication of the HARQ process number corresponding to the transport block carried in PDSCH # 2.
  • the HARQ processes used may not be coordinated, so the value range of the HARQ process numbers used by the two network devices may be the same. This may cause the problem that the same HARQ process number corresponds to two HARQ processes. Since the terminal device cannot distinguish between different transmission blocks, data transmission performance may be affected.
  • the present application provides a method for receiving data, which can improve data transmission performance.
  • the method for receiving data provided by the embodiments of the present application may be applied to a wireless communication system, such as the communication system 100 shown in FIG. 1.
  • the communication devices in the wireless communication system may have a wireless communication connection relationship.
  • the terminal device 101 shown in FIG. 1 may have a wireless communication connection relationship with the network device # 1 102 and the network device # 2 103, respectively.
  • the network device # 1 102 and the network device # 2 103 may be an ideal backhaul link or a non-ideal backhaul link, which is not limited in this application.
  • network device # 1 102 and network device # 2 103 are ideal backhaul links
  • network device # 1102 and network device # 2 103 can be considered to belong to the same network device group, or network device # 1 102 and Network device # 2103 belongs to different network device groups.
  • the network device # 1 102 and the network device # 2 103 are non-ideal backhaul links, it can be considered that the network device # 1 102 and the network device # 2 103 belong to different network device groups.
  • the network devices in the same network device group can be scheduled through one DCI, for example, or a scheduling entity can be used for scheduling, or the PDCCH can be sent based on the same PDCCH configuration. It can be understood that whether an ideal backhaul link between network devices is transparent to network devices. Therefore, this should not constitute any limitation on the scenarios to which the method provided by this application is applicable.
  • the first network device group shown below may include, for example, network device # 1 102 in FIG. 1, and the second network device group may correspond to network device # 2 103 in FIG. 2, for example.
  • the following uses the interaction between the first network device group and the second network device group and the terminal device as an example to describe in detail the method for receiving data provided by the embodiment of the present application.
  • first network device group and the second network device group may be the same network device group, or may be different network device groups.
  • the first network device group may include one or more network devices, and the second network device group may also include one or more network devices.
  • the first network device group includes only one network device (for example, may be denoted as the first network device) and the second network device group includes only one network device (for example, may be denoted as the second network device)
  • the first network device group and The second network device group is the same network device group, which can be replaced by the first network device and the second network device are the same network device
  • the first network device group and the second network device group are different network device groups, which can be replaced by ,
  • the first network device and the second network device are different network devices.
  • scheduling may be performed through the PDCCH in advance.
  • the network devices in the network device group may negotiate through the backhaul link in advance, and then send the PDCCH through a certain network device (for example, the first network device) to schedule the PDSCH for the terminal device. Therefore, the network device group can transmit the PDCCH through one network device.
  • the terminal device may receive the PDSCH according to the PDCCH.
  • the network devices in the network device group are transparent to the terminal device.
  • the terminal device only receives the PDSCH from the network device group without knowing whether the PDSCH comes from one network device or multiple network devices. In other words, the terminal device does not know whether the received PDSCH is sent by a network device or a network device group.
  • the PDSCH received by a terminal device from a network device or a network device group may be one PDSCH scheduled based on one PDCCH.
  • sending the PDSCH to the terminal device by the network device group may refer to that multiple network devices in the network device group work together to send the PDSCH to the terminal device.
  • multiple network devices may send PDSCH to the terminal device through a transmission mode of diversity transmission or space division multiplexing.
  • FIG. 2 shows a schematic flowchart of a method 200 for sending and receiving data provided by an embodiment of the present application from the perspective of device interaction. As shown, the method 200 may include steps 210 to 240. The steps of the method 200 are described in detail below.
  • step 210 the terminal device receives the first PDSCH, and the first PDSCH carries at least one transport block.
  • the PDSCH received by the terminal device in step 210 is recorded as the first PDSCH.
  • the first PDSCH may be a PDSCH sent by the first network device group. That is, in step 210, the first network device group transmits the first PDSCH.
  • the first PDSCH may be scheduled by the first network device group through PDCCH.
  • the first PDSCH may be scheduled by the first network device in the first network device group through the PDCCH.
  • the PDCCH used to schedule the first PDSCH is referred to as the first PDCCH.
  • DCI may be transmitted on the first PDCCH.
  • the method 200 further includes: step 220, the terminal device receives a first PDCCH, and the first PDCCH is used to schedule the first PDSCH.
  • the first network device in the first network device group sends the first PDCCH.
  • the DCI transmitted on the first PDCCH is recorded as the first DCI.
  • the first DCI may include information such as the time-frequency resource, antenna port, HARQ process number of the first PDSCH scheduled by the first DCI.
  • the PDCCH may be used to transmit DCI.
  • scheduling of PDSCH by PDCCH and scheduling of PDSCH by DCI may be considered equivalent.
  • DCI can be replaced with PDCCH.
  • One or more transport blocks may be carried in the first PDSCH.
  • a network device can transmit up to two transport blocks per TTI. That is, a maximum of two transport blocks can be carried in the first PDSCH.
  • the maximum number of transport blocks that can be carried in the PDSCH can be indicated by higher layer signaling, such as RRC messages, for example.
  • the DCI scheduling PDSCH may contain configuration information of only one transport block.
  • the configuration information of the transport block may include, for example: MCS, new data indicator (NDI) and redundancy version (redundancy version, RV).
  • the DCI scheduling PDSCH may contain configuration information of two transport blocks, and a certain transport block may be disabled in a predefined manner. For example, when the MCS in the configuration information of a transport block is 26 and the RV is 1, it can implicitly indicate that the transport block is disabled; otherwise, the transport block is an enabled transport block.
  • the disabled transmission block may be understood as a transmission block that does not carry data, and the enabled transmission block may be understood as a transmission block that carries data.
  • the number of transport blocks carried by the PDSCH can be considered to be 1; when a transport block in the PDSCH is not disabled, the number of transport blocks carried by the PDSCH can be considered Is 2.
  • the method further includes: the terminal device receives a second PDCCH, and the second PDCCH is used to schedule the PDSCH.
  • the second PDCCH may be sent by the second network device in the second network device group.
  • the method further includes: the terminal device receives the second PDSCH.
  • the second PDSCH may be scheduled by the second network device group.
  • the first network device may be a network device in the first network device group
  • the second network device may be a network device in the second network device group.
  • the first network device group and the second network device group may be the same network device group, or may be different network device groups.
  • the present application does not limit the sequence in which the terminal device receives the first PDCCH and the second PDCCH.
  • the first PDCCH and the second PDCCH may be received at the same time, and the first PDCCH may be before or after the second PDCCH. received.
  • This application also does not limit the sequence in which the terminal device receives the first PDSCH and the second PDSCH.
  • the first PDSCH and the second PDSCH may be received at the same time, and the first PDSCH may also be received before or after the second PDSCH. .
  • the terminal device When the terminal device receives multiple PDCCHs or multiple PDSCHs, the HARQ process number indicated by the DCI in multiple PDCCHs may be repeated. Therefore, the HARQ process corresponding to the same HARQ process number may not be unique.
  • the terminal device needs to determine the HARQ process corresponding to the scheduled PDSCH according to the DCI in each PDCCH. In the following, without loss of generality, the specific process in which the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI is described in detail.
  • the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and one or more of the following: the configuration parameters of the first PDCCH, the network device group that sends the first PDSCH, and the indication in the first DCI DMRS port and BWP.
  • one or more transport blocks may be carried in the first PDSCH, and each transport block may correspond to one HARQ process. Therefore, the HARQ process number indicated in the first DCI may be used to indicate the HARQ process corresponding to one or more transport blocks. That is to say, the HARQ process corresponding to the first PDSCH may be one HARQ process or multiple HARQ processes.
  • the terminal device may determine that the first PDSCH carries at most one transport block according to the RRC message received in advance.
  • the HARQ process corresponding to the first PDSCH that is, the HARQ process corresponding to the transport block carried in the first PDSCH.
  • the terminal device may determine the HARQ process in combination with the HARQ process number indicated in the first DCI and one or more of the following: configuration parameters of the first PDCCH, the network device group transmitting the first PDSCH, and the first DCI The port and BWP of the DMRS indicated in.
  • the HARQ process set may correspond to one or more of the following: PDCCH configuration parameters, DMRS port group, BWP, network equipment (or network equipment group).
  • the terminal device may use one of the port group to which the port of the DMRS indicated in the first DCI belongs and the BWP according to the configuration parameter of the PDCCH on which the first PDCCH is received, the network device (or group of network devices) transmitting the first PDSCH
  • the item or items determine the HARQ process set, and may further determine the HARQ process from the HARQ process set according to the HARQ process number indicated in the first DCI.
  • the terminal device may directly determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and one or more of the following: the configuration parameters of the PDCCH, the port group to which the DMRS port belongs, the BWP, and the network device group that sends the first PDSCH; or , The terminal device may also first determine the corresponding one or more HARQ processes according to the HARQ process number, and then determine the HARQ process corresponding to the first PDSCH from the one or more HARQ processes according to one or more of the following: PDCCH configuration parameters, The port group to which the DMRS port belongs, the BWP, and the network device group that sends the first PDSCH.
  • the present application does not limit the specific process of the HARQ process corresponding to the first PDSCH determined by the terminal device and the execution order, as long as the HARQ process corresponding to the first PDSCH is determined according to the HARQ process number and one or more of the following: PDCCH
  • PDCCH Physical Downlink Control Channel
  • step 230 specifically includes: the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the configuration parameters of the first PDCCH.
  • the configuration parameter of the first PDCCH may be a parameter for configuring time-frequency resources of the first PDCCH and the like.
  • the configuration parameters of the first PDCCH may include one or more of the following: the PDCCH configuration of the first PDCCH, the BWP downlink dedicated parameter to which the first PDCCH configuration belongs, the BWP downlink parameter to which the first PDCCH configuration belongs, the first The serving cell configuration to which the PDCCH configuration belongs, the control resource set of the first PDCCH, the control resource set group to which the control resource set of the first PDCCH belongs, the search space set of the first PDCCH, and the search space set to which the search space set of the first PDCCH belongs group.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to one of the HARQ process number and the configuration parameter of the first PDCCH listed above.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH.
  • the PDCCH configuration can be used to determine one or more search spaces.
  • the PDCCH configuration of the first PDCCH can be understood as the PDCCH configuration on which the first PDCCH is received, or in other words, the terminal device can blindly detect the first PDCCH in the search space determined by the PDCCH configuration
  • the PDCCH configuration of the first PDCCH can be understood as the PDCCH configuration on which the first PDCCH is sent, or in other words, the network device can send on some resources in the search space determined by the PDCCH configuration The first PDCCH.
  • the HARQ process set may correspond to the PDCCH configuration.
  • One or more HARQ processes corresponding to one PDCCH configuration may be referred to as a HARQ process set corresponding to the PDCCH configuration.
  • HARQ process set # 1 may correspond to PDCCH configuration # 1
  • HARQ process set # 2 may correspond to PDCCH configuration # 2.
  • the terminal device may save the transport block carried in the received PDSCH in the corresponding HARQ buffer according to the PDCCH configuration on which the PDCCH scheduling the PDSCH is based.
  • the terminal device may divide the HARQ buffer into one or more regions, and each region corresponds to a PDCCH configuration.
  • the storage space occupied by HARQ caches in different regions may be different, and the storage space occupied by different HARQ caches does not overlap.
  • different HARQ process sets occupy different areas in the HARQ cache. It should be understood that HARQ processes included in different HARQ process sets are scheduled based on different PDCCHs, respectively.
  • FIG. 3 shows an example in which different PDCCH configurations correspond to different HARQ buffer areas.
  • PDCCH configuration # 1 may correspond to region # 1 in the HARQ buffer
  • PDCCH configuration # 2 may correspond to region # 2 in the HARQ buffer. It can be understood that the HARQ process in the area # 1 in the HARQ cache may belong to the HARQ process set # 1, and the HARQ process in the area # 2 in the HARQ cache may belong to the HARQ process set # 2.
  • FIG. 3 is only an example, and shows that PDCCH configuration # 1 and PDCCH configuration # 2 respectively correspond to different HARQ buffer regions, but this should not constitute any limitation to this application.
  • the PDCCH configuration is not limited to two, and the PDCCH configuration is not limited to be distinguished by different number numbers, which is not limited in this application.
  • the terminal device may determine the corresponding HARQ buffer area according to the PDCCH configuration on which the first PDCCH is received, and then may determine the HARQ process corresponding to the first PDSCH in the HARQ buffer area according to the HARQ process number indicated in the first DCI .
  • the terminal device may renumber HARQ processes corresponding to different HARQ process sets according to preset rules.
  • the number of HARQ processes in different HARQ process sets is referred to as the local number of the HARQ process.
  • the terminal device may determine the local number of the HARQ process according to the HARQ process number and the PDCCH configuration indicated in the DCI. That is to say, the local numbers of HARQ processes included in different HARQ process sets are different, and there is no duplication.
  • FIG. 4 shows an example of local numbers corresponding to different HARQ processes with different PDCCH configurations.
  • the HARQ process numbers indicated in the two DCIs received by the terminal device are both 0 to N-1, but the two DCIs are received based on PDCCH configuration # 1 and PDCCH configuration # 2, respectively.
  • the HARQ process number indicated in the DCI received based on PDCCH configuration # 1 may correspond to local numbers 0 to N-1
  • the HARQ process number indicated in the DCI received based on PDCCH configuration # 2 may correspond to local numbers N to 2N-1.
  • HARQ processes with local numbers of 0 to N-1 may belong to HARQ process set # 1
  • HARQ processes with local numbers of N to 2N-1 may belong to HARQ process set # 2.
  • the corresponding local number may also be n; based on the PDCCH configuration # 2
  • the corresponding local number may be n + N.
  • the terminal device may determine the local number of the HARQ process corresponding to the first PDSCH according to the PDCCH configuration based on the first PDCCH and the HARQ process number indicated in the first DCI, and then may determine the HARQ process corresponding to the first PDSCH.
  • the terminal device can still determine the local number of the HARQ process according to a preset rule.
  • each network device group may correspond to a PDCCH configuration. That is, the protocol may be pre-defined, and two or more PDCCH configurations are configured in the same serving cell configuration, and each PDCCH configuration may correspond to a network device group.
  • the network devices in the network device group may send the PDCCH based on the corresponding PDCCH configuration.
  • the correspondence between the network device group and the PDCCH configuration may be determined in advance through negotiation between each network device group.
  • the correspondence between the network device group and the PDCCH configuration can be negotiated and configured between the network device groups through the backhaul link. This application does not limit the correspondence between the network device group and the PDCCH configuration and the configuration manner of the correspondence.
  • one network device group may also be configured with two or more PDCCHs, and different network device groups correspond to different PDCCH configurations.
  • the present application does not limit the number of PDCCH configurations corresponding to one network device group.
  • the method for determining the HARQ process set according to the PDCCH configuration has been described above with reference to the drawings, but this should not constitute any limitation to this application. Based on the same concept, those skilled in the art may also adopt other possible ways to determine the HARQ process set according to the PDCCH configuration. This application does not limit the specific manner of determining the HARQ process set corresponding to the first PDSCH according to the PDCCH configuration. In addition, the HARQ process set is only defined for ease of understanding and should not constitute any limitation to this application. Those skilled in the art can also determine the HARQ process set, and directly determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration.
  • the above PDCCH configuration may also be replaced with BWP downlink dedicated parameters, BWP downlink parameters, serving cell configuration, and control resource set, respectively. , Control resource set group, search space set, search space set group, DMRS port group, BWP or network equipment group.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP downlink dedicated parameter to which the PDCCH configuration of the first PDCCH belongs.
  • the network device can configure the serving cell for the terminal device through high-level parameters, such as RRC messages.
  • a serving cell configuration may include one BWP downlink parameter.
  • the BWP downlink parameter may include multiple BWP downlink dedicated parameters, and each BWP downlink dedicated parameter may include a PDCCH configuration.
  • the HARQ process set may correspond to BWP downlink dedicated parameters.
  • one BWP downlink dedicated parameter may include one or more parameters, or may also be referred to as a group of parameters, and is not necessarily limited to one parameter.
  • Each BWP downstream dedicated parameter can be independent of each other. In other words, each BWP downlink dedicated parameter can be used independently of other BWP downlink dedicated parameters.
  • HARQ process set # 1 may correspond to BWP downlink dedicated parameter # 1
  • HARQ process set # 2 may correspond to BWP downlink dedicated parameter # 2.
  • the terminal device may determine the HARQ process set corresponding to the BWP downlink dedicated parameter according to the PDCCH configuration to which the first PDCCH is based, and then determine the HARQ corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI process.
  • the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP downlink dedicated parameter to which the PDCCH configuration of the first PDCCH corresponds to the terminal device determining the first PDSCH corresponding to the HARQ process number and the PDCCH configuration of the first PDCCH
  • the specific process of the HARQ process is similar, and for the sake of brevity, it will not be repeated here.
  • each network device group may correspond to a BWP downlink dedicated parameter.
  • the protocol can be pre-defined, and two or more BWP downlink dedicated parameters are configured in the same serving cell configuration, and each BWP downlink dedicated parameter can correspond to a network device group.
  • the network devices in the network device group may send the PDCCH based on the PDCCH configuration under the corresponding BWP downlink dedicated parameters.
  • the correspondence between the network device group and the BWP downlink dedicated parameter may be determined in advance through negotiation between each network device group. This application does not limit the correspondence between the network device group and the BWP downlink dedicated parameter and the configuration method of the correspondence.
  • one network device group may also correspond to two or more BWP downlink dedicated parameters. Different network device groups correspond to different BWP downlink dedicated parameters. This application is dedicated to BWP downlink dedicated to one network device group. The number of parameters is not limited.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP downlink parameter to which the PDCCH configuration of the first PDCCH belongs.
  • the network device can configure the serving cell for the terminal device through high-level parameters.
  • a serving cell configuration may include one or more BWP downlink parameters, each BWP downlink parameter may include a BWP downlink dedicated parameter, and each BWP downlink dedicated parameter may include a PDCCH configuration.
  • the HARQ process set may correspond to BWP downlink parameters.
  • one BWP downlink parameter may include one or more parameters, or may also be referred to as a group of parameters, and is not necessarily limited to one parameter.
  • the BWP downstream parameters can be independent of each other. In other words, each BWP downlink parameter can be used independently of other BWP downlink parameters.
  • HARQ process set # 1 may correspond to BWP downlink parameter # 1
  • HARQ process set # 2 may correspond to BWP downlink parameter # 2.
  • the terminal device may determine the HARQ process set corresponding to the BWP downlink parameter according to the BWP downlink parameter to which the PDCCH configuration based on the first PDCCH belongs, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI. Because the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP downlink parameter to which the PDCCH configuration of the first PDCCH belongs, the terminal device determines the first PDSCH corresponding to the HARQ process number and the PDCCH configuration of the first PDCCH The specific process of the HARQ process is similar. For the sake of brevity, it will not be repeated here.
  • each network device group may correspond to a BWP downlink parameter.
  • the protocol may be pre-defined, and two or more BWP downlink parameters are configured in the same serving cell configuration, and each BWP downlink parameter may correspond to a network device group.
  • the network devices in the network device group may send the PDCCH based on the PDCCH configuration under the corresponding BWP downlink parameter.
  • the correspondence between the network device group and the BWP downlink parameter may be determined in advance through negotiation between each network device group. This application does not limit the correspondence between the network device group and the BWP downlink dedicated parameter and the configuration method of the correspondence.
  • a network device group may also correspond to two or more BWP downlink parameters, and different network device groups correspond to different BWP downlink parameters.
  • the number of BWP downlink parameters corresponding to a network device group in this application Not limited.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the serving cell configuration to which the PDCCH configuration of the first PDCCH belongs.
  • the network device can configure the serving cell for the terminal device through high-level parameters.
  • the protocol may be defined in advance, and each terminal device may be configured with multiple serving cells.
  • the first network device group and the second network device group may be located in different serving cells.
  • Each serving cell configuration may include a BWP downlink parameter, each BWP downlink parameter may include a BWP downlink dedicated parameter, and each BWP downlink dedicated parameter may include a PDCCH configuration.
  • the HARQ process set may correspond to the serving cell configuration.
  • HARQ process set # 1 may correspond to serving cell configuration # 1
  • HARQ process set # 2 may correspond to serving cell configuration # 2.
  • the terminal device may determine the HARQ process set corresponding to the serving cell configuration according to the serving cell configuration to which the PDCCH configuration on which the first PDCCH belongs belongs, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI. Because the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the serving cell configuration to which the PDCCH configuration of the first PDCCH belongs, and the terminal device determines the first PDSCH corresponding to the HARQ process number and the PDCCH configuration of the first PDCCH The specific process of the HARQ process is similar. For the sake of brevity, it will not be repeated here.
  • each network device group may correspond to a serving cell configuration. That is to say, the network device groups in different serving cells can send the PDCCH based on different serving cell configurations.
  • the corresponding relationship between the network device group and the serving cell configuration may be pre-negotiated between each network device group. This application does not limit the correspondence between the configuration of the network device group and the serving cell and the configuration method of the correspondence.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the control resource set of the first PDCCH.
  • the control resource set can be used to determine the search space of the PDCCH.
  • the control resource set of the first PDCCH may be understood as the control resource set on which the first PDCCH is received, or in other words, the terminal device may blindly detect the first resource in the search space determined by the control resource set A PDCCH;
  • the control resource set of the first PDCCH can be understood as the control resource set on which the first PDCCH is sent, or in other words, the network device can be in the search space determined by the control resource set Send the first PDCCH on part of the resources.
  • Network devices that transmit PDCCH based on the same control resource set may be considered to be the same network device or belong to the same network device group.
  • the HARQ process set may correspond to the control resource set.
  • HARQ process set # 1 may correspond to control resource set # 1
  • HARQ process set # 2 may correspond to control resource set # 2.
  • the terminal device may determine the HARQ process set according to the control resource set on which the first PDCCH is received, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI. Because the terminal device determines the specific process of the HARQ process corresponding to the first PDSCH according to the HARQ process number and the control resource set of the first PDCCH and the terminal device determines the specific process of the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH The process is similar and will not be repeated here for brevity.
  • multiple network device groups may send PDCCHs based on the same PDCCH configuration and different sets of control resources.
  • Each network device group can correspond to a set of control resources.
  • the network device group that sends the PDCCH based on the same PDCCH configuration belongs to the same cell.
  • the network device groups that transmit the PDCCH based on the same PDCCH configuration belong to different cells.
  • the corresponding relationship between the network device group and the control resource set may be determined in advance through negotiation between each network device group. This application does not limit the correspondence between the network device group and the control resource set and the configuration method of the correspondence.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the control resource set group to which the control resource set of the first PDCCH belongs.
  • each HARQ process set may correspond to one or more control resource sets.
  • One or more control resource sets corresponding to the same HARQ process set may be called a control resource set group.
  • HARQ process set # 1 may correspond to control resource set group # 1
  • HARQ process set # 2 may correspond to control resource set group # 2.
  • the terminal device may determine the HARQ process set according to the control resource set group to which the control resource set on which the first PDCCH is received belongs, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI. Since the terminal device determines the specific HARQ process corresponding to the first PDSCH according to the HARQ process number and the control resource set group to which the control resource set of the first PDCCH belongs, the terminal device determines the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH The specific process of the corresponding HARQ process is similar. For the sake of brevity, it will not be repeated here.
  • multiple network device groups may send PDCCHs based on the same PDCCH configuration and different control resource set groups.
  • Each network device group can correspond to a control resource set group.
  • the network device group that sends the PDCCH based on the same PDCCH configuration belongs to the same cell.
  • the network device groups that transmit the PDCCH based on the same PDCCH configuration belong to different cells.
  • the correspondence between the network device group and the control resource set group may be determined in advance through negotiation between the network device groups. This application does not limit the correspondence between the network device group and the control resource set group and the configuration method of the correspondence.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the search space set of the first PDCCH.
  • the search space set may be a collection of search spaces.
  • a search space set may include one or more search spaces.
  • the search space set of the first PDCCH can be understood as the search space set on which the first PDCCH is received, or in other words, the terminal device can blindly detect the first search space in the search space included in the search space set PDCCH;
  • the search space set of the first PDCCH can be understood as the search space set on which the first PDCCH is transmitted, or in other words, the network device can be on a search space included in the search space set Send the first PDCCH.
  • Network devices that transmit PDCCH based on the same search space set may be considered to be the same network device or belong to the same network device group.
  • the HARQ process set may correspond to the search space set.
  • HARQ process set # 1 may correspond to search space set # 1
  • HARQ process set # 2 may correspond to search space set # 2.
  • the terminal device may determine the HARQ process according to the search space set on which the first PDCCH is received, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI. Because the terminal device determines the specific process of the HARQ process corresponding to the first PDSCH according to the HARQ process number and the search space set of the first PDCCH and the terminal device determines the specific process of the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH The process is similar and will not be repeated here for brevity.
  • multiple network device groups may send PDCCHs based on the same PDCCH configuration and different search space sets.
  • Each network device group can correspond to a search space set.
  • the network device group that sends the PDCCH based on the same PDCCH configuration belongs to the same cell.
  • the network device groups that transmit the PDCCH based on the same PDCCH configuration belong to different cells.
  • the correspondence between the network device group and the search space set may be determined in advance through negotiation between each network device group. This application does not limit the correspondence between the network device group and the search space set and the configuration method of the correspondence.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the search space set group to which the search space set of the first PDCCH belongs.
  • each HARQ process set may correspond to one or more search space sets.
  • One or more search space sets corresponding to the same HARQ process set may be called a search space set group.
  • HARQ process set # 1 may correspond to search space set group # 1
  • HARQ process set # 2 may correspond to search space set group # 2.
  • the terminal device may determine the HARQ process set according to the search space set group to which the search space set on which the first PDCCH is received belongs, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI. Because the terminal device determines the specific HARQ process corresponding to the first PDSCH according to the HARQ process number and the search space set group to which the search space set of the first PDCCH belongs, and the terminal device determines the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH The specific process of the corresponding HARQ process is similar. For the sake of brevity, it will not be repeated here.
  • multiple network devices or groups of network devices may send PDCCHs based on the same PDCCH configuration and different search space set groups.
  • Each network device or network device group can correspond to a search space set group.
  • the network devices that transmit the PDCCH based on the same PDCCH configuration belong to the same cell.
  • the network devices that transmit the PDCCH based on the same PDCCH configuration belong to different cells.
  • the correspondence between the network device group and the search space set group may be determined in advance through negotiation between the network device groups. This application does not limit the correspondence between the network device group and the search space set group and the configuration method of the correspondence.
  • the correspondence relationship between the HARQ process set and the PDCCH configuration parameters listed above is only an example, and should not constitute any limitation to this application.
  • This application refers to the number of network equipment groups, the number of network equipment in the network equipment group, the number of HARQ process sets, the number of serving cell configurations, the number of BWP downlink parameters in the same serving cell configuration, and the BWP downlink dedicated parameters in the same BWP downlink parameters.
  • the number of, the number of PDCCH configurations in the same BWP downlink dedicated parameter, the number of control resource sets or control resource set groups in the same PDCCH configuration, and the number of search space sets or search space set groups in the same PDCCH configuration are not limited.
  • step 230 specifically includes: the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the port of the DMRS indicated in the first DCI.
  • each network device group is not limited to using one port group.
  • a network device group may also be connected to two or more port groups. The ports in the port groups corresponding to different network device groups are not duplicated. The present application does not limit the number of port groups corresponding to a network device group.
  • each port group may be pre-defined, as defined by the protocol, or may be indicated by the network device, such as indicated by the network device through high-level signaling, such as an RRC message.
  • the first network device may indicate the scheduled DMRS port of the first PDSCH in the first DCI.
  • the terminal device may determine the DMRS port used to demodulate the first PDSCH according to the received first DCI, so as to demodulate the received first PDSCH.
  • the HARQ process set may correspond to the port group.
  • HARQ process set # 1 may correspond to port group # 1
  • HARQ process set # 2 may correspond to port group # 2.
  • the terminal device may determine the port group to which it belongs according to the port used to demodulate the DMRS of the first PDSCH indicated in the first DCI, and then determine the HARQ process set. The terminal device may further determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI.
  • the correspondence between the network device group and the DMRS port group may be determined in advance through negotiation between each network device group. This application does not limit the correspondence between the network device group and the DMRS port group and the configuration method of the correspondence.
  • DMRS and DMRS ports may be corresponding.
  • Each DMRS may correspond to a DMRS port.
  • the meaning expressed by the DMRS port and the DMRS port is the same.
  • step 230 specifically includes: the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP indicated in the first DCI.
  • the network device can configure the serving cell for the terminal device through high-level parameters.
  • a serving cell configuration may include one or more BWP downlink parameters.
  • Each BWP downlink parameter can correspond to a BWP.
  • the network device may indicate the ID of the BWP through DCI, for example, through the BWP indication (bandwidth part indicator) field in DCI.
  • the BWP indicated by the DCI can be understood as an activated BWP.
  • the BWP indicated by the DCI can be used for data transmission by the terminal device, for example, receiving PDSCH.
  • the HARQ process set may correspond to BWP.
  • the correspondence between the HARQ process set and the BWP is similar to the correspondence between the HARQ process set and the BWP downlink parameters described above.
  • HARQ process set # 1 may correspond to BWP # 1
  • HARQ process set # 2 may correspond to BWP # 2.
  • the terminal device may determine the HARQ process set corresponding to the BWP according to the ID of the BWP indicated in the first DCI in the first PDCCH, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI. Because the terminal device determines the specific process of the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP indicated by the first DCI and the terminal device determines the specific process of the HARQ process corresponding to the first PDSCH according to the HARQ process number and the PDCCH configuration of the first PDCCH Similarly, for the sake of brevity, I will not repeat them here.
  • each network device group may correspond to a BWP.
  • each network device group can activate a BWP.
  • the correspondence between the network device group and the BWP can be expressed as, for example, the correspondence between the network device group and the BWP downlink parameter.
  • the protocol may be pre-defined, and multiple or more BWP downlink parameters are configured in the same serving cell configuration, and each BWP downlink parameter may correspond to a network device group.
  • the network device in the network device group may indicate (or activate) the corresponding BWP through DCI based on the corresponding BWP downlink parameter.
  • the correspondence between the network device group and the BWP may be determined in advance through negotiation between the network device groups. This application does not limit the correspondence between the network device group and the BWP and the configuration method of the correspondence.
  • one network device group may also correspond to two or more BWPs.
  • the BWPs corresponding to different network device groups do not overlap.
  • the application does not limit the number of BWPs corresponding to one network device group.
  • step 230 specifically includes: the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the network device group that sends the first PDSCH.
  • the terminal device when the terminal device receives the first PDSCH, it does not know whether the first PDSCH comes from a network device or a network device group.
  • the indication of the network device group may be, for example, the identification of the network device or the identification of the network device group; when the network device group includes multiple network devices, the network device group The indication of may be, for example, the identification of the network device group.
  • This application does not limit the specific way of indicating the network device group. For example, it can be indicated by an identifier, or by other information that can be used to distinguish different groups of network devices.
  • the HARQ process set may correspond to the network device group.
  • HARQ process set # 1 may correspond to network device group # 1
  • HARQ process set # 2 may correspond to network device group # 2.
  • the terminal device may determine the corresponding HARQ process set according to the network device sending the first PDSCH, and then determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI.
  • the network device group that sends the first PDSCH may be indicated by the first DCI.
  • a field indicating a network device group is added to the first DCI to indicate the network device group scheduling the first PDSCH.
  • the terminal device may determine the network device group that sends the first PDSCH according to the network device group indicated by the first DCI, and then determine the corresponding HARQ process set.
  • the terminal device may further determine the HARQ process corresponding to the first PDSCH according to the HARQ process number indicated in the first DCI.
  • the network device group transmitting the first PDSCH may also be indicated in other ways. This application does not limit the specific manner of instructing the network device group that sends the first PDSCH.
  • the terminal device may also combine the HARQ process with the DCI type or receive beam group, etc. to determine the HARQ process corresponding to the first PDSCH.
  • step 230 specifically includes: the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the type of the first DCI.
  • DCI types can be divided into primary DCI and secondary DCI.
  • the PDCCH used to transmit the primary DCI may be referred to as the primary PDCCH.
  • the PDCCH used to transmit the secondary DCI may be referred to as a secondary PDCCH.
  • the information contained in the secondary DCI may be a subset of the information contained in the primary DCI.
  • the secondary DCI may only include an indication field included in part of the primary DCI, that is, the primary DCI may contain more indication information than the secondary DCI.
  • the primary DCI and the secondary DCI may contain different information.
  • the primary DCI may be a DCI containing a certain item or items of specific parameters.
  • the specific parameter may include, for example, at least one of the following: carrier indicator (carrier indicator), partial bandwidth indicator (bandwidth indicator), rate matching indicator (rate matching indicator), and zero power channel state information reference signal trigger (zero power channelstate information reference trigger, ZP CSI-RS trigger); correspondingly, the secondary DCI may be a DCI that does not contain any of the above specific parameters.
  • the secondary DCI may be a DCI including one or more of the following: resource allocation (resource allocation), MCS, RV, NDI, HARQ process number, and so on.
  • the protocol can predefine the specific content contained in the primary DCI and the secondary DCI.
  • the PDCCH may be considered as the main PDCCH.
  • the primary and secondary DCI may correspond to one HARQ process set respectively.
  • the primary DCI corresponds to HARQ process set # 1
  • the secondary DCI corresponds to HARQ process set # 2.
  • the terminal device may determine whether the first DCI is the primary DCI or the secondary DCI according to the information contained in the received first DCI, and then determine the corresponding HARQ process set. Thereafter, the terminal device may further determine the HARQ process corresponding to the first PDSCH from the HARQ process set according to the HARQ process number.
  • step 230 specifically includes: the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the receive beam group of the first PDSCH.
  • the reception beams of the terminal devices may be grouped, and the PDCCH and PDSCH from the same network device or the same network device group may be received through the reception beams in the same reception beam group. Therefore, one receive beam group can correspond to one HARQ process set.
  • the receiving beam group # 1 may correspond to the HARQ process set # 1
  • the receiving beam group # 2 may correspond to the HARQ process set # 2.
  • the network device may carry a transmission configuration indication (TCI) in the first DCI, and indicate the selected TCI state (TCI state) through the TCI.
  • TCI state may contain an identifier for determining a reference signal resource used to receive the receive beam of the first PDSCH. In other words, the identification of the reference signal resource has a corresponding relationship with the reception beam. Therefore, in one implementation, grouping the received beams can also be achieved by grouping reference signal resources.
  • the network device may indicate multiple reference signal resource groups through signaling, and each reference signal resource group includes one or more reference signal resources.
  • the terminal device may determine the reception beam according to the identifier of the reference signal resource indicated in the TCI state, and receive the PDSCH from the network device through the reception beam corresponding to the reference signal resource.
  • the receive beams in the same receive beam group can be configured on the same antenna panel. Therefore, in another implementation manner, an indication field may be added to the existing TCI state to distinguish different receive beam groups.
  • an indication field related to an antenna panel may be added in the TCI state, for example, "panel 1" indicates antenna panel 1, and "panel 2" indicates antenna panel 2.
  • the network device may indicate the available TCI status through TCI, and then indicate which antenna panel the terminal device uses to receive the PDSCH.
  • the terminal device may determine the receive beam group to which the receive beam receiving the first PDSCH belongs according to the TCI in the first DCI, and then determine the HARQ process set corresponding to the receive beam group. Thereafter, the terminal device may determine the HARQ process corresponding to the first PDSCH from the HARQ process set according to the HARQ process number.
  • the indication field related to the antenna panel is not limited to the above example, and the indication field related to the antenna panel is not limited in this application. It should also be understood that distinguishing different receive beam groups by referring to signal resources and antenna panels is only two possible implementations provided by this application, and should not constitute any limitation to this application. This application does not exclude the possibility of distinguishing different receive beam groups in other ways.
  • step 230 specifically includes: the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the receive beam group of the first PDCCH.
  • the network device may activate a TCI state through a media access control (MAC) control element (CE).
  • the TCI state may include a reference signal resource identifier used to determine the receive beam used to receive the PDCCH.
  • the terminal device may determine the reception beam for receiving the PDCCH according to the TCI state activated in the MAC CE.
  • the reference signal resource identifier has a relationship with the receiving beam and also has a corresponding relationship with the transmitting beam
  • the corresponding receiving beam and transmitting beam can also be determined.
  • the reference signal resource indicated by the reference signal resource identifier indicated in the TCI belongs to the same reference signal resource group, it can be considered that the corresponding transmit beam also belongs to the same transmit beam group.
  • the receive beams corresponding to the reference signal resource identifiers indicated in the TCI belong to the same receive beam group, it can be considered that the transmit beams corresponding to the reference signal resource identifiers indicated in the TCI also belong to the same transmit beam group.
  • the above “the terminal device determines the HARQ process corresponding to the first PDSCH according to the HARQ process number and the receiving beam group of the first PDSCH” can be replaced by “the terminal device determines the first according to the HARQ process number and the transmitting beam group of the first PDSCH.
  • the PDCCH configuration parameters, DMRS port, BWP, network device group that sends the first PDSCH, DCI type, the receive beam (or transmit beam) of the first PDSCH, and the receive beam (or One or more of the transmit beams can also be used in combination with the HARQ process number to determine the HARQ process corresponding to the first PDSCH.
  • the terminal device may determine the HARQ process corresponding to the first PDSCH according to the HARQ process number, the configuration parameter of the PDCCH, and the port group to which the DMRS port belongs.
  • the terminal device may also determine the HARQ process corresponding to the first PDSCH according to the HARQ process number, the PDCCH configuration, and the receive beam group to which the receive beam of the first PDSCH belongs. For brevity, I will not list them here.
  • the terminal device combines the PDCCH configuration parameters, DMRS port, BWP, network device group that sends the first PDSCH, the type of the first DCI, the receive beam (or transmit beam) of the first PDSCH, and the receive beam (or transmit beam) of the first PDCCH
  • One or more of) can also be used in combination with the HARQ process number to determine the specific method of the HARQ process corresponding to the first PDSCH is similar to the specific method described above, and for the sake of brevity, no more details are provided here.
  • the protocol may predefine which item is used to determine the HARQ process corresponding to the first PDSCH.
  • the protocol may be defined in advance, and the HARQ process corresponding to the first PDSCH is determined according to the HARQ process number and the PDCCH configuration.
  • the correspondence between the PDCCH configuration and the network device group may be predefined between the network device groups.
  • the first network device may send the first PDCCH based on the corresponding PDCCH configuration, and the terminal device may determine the HARQ process corresponding to the first PDSCH according to the PDCCH configuration on which the first PDCCH is blindly detected, in combination with the HARQ process number.
  • the network device and the terminal device may process based on a method similar to that described above to determine the HARQ process corresponding to the first PDSCH. Since the specific processing procedures are similar, this article will not describe them in detail for the sake of brevity.
  • the terminal device when receiving multiple PDCCHs for scheduling multiple PDSCHs, can combine one of the configuration parameters of the PDCCH, the port of the DMRS, and the network device group that sends the PDSCH according to the HARQ process number or Multiple items to determine the HARQ process corresponding to each PDSCH.
  • the terminal device may carry two or more transport blocks.
  • the terminal device may, for example, determine the corresponding number of each transport block according to the method in the prior art. HARQ process.
  • the first PDSCH may carry one transport block or multiple transport blocks.
  • the specific process of the terminal device determining the HARQ process corresponding to the first PDSCH is described in detail by taking an example of carrying a transport block in the first PDSCH as an example.
  • the terminal device may also determine the HARQ process corresponding to the first PDSCH based on the same method. For example, the terminal device may determine that the first PDSCH carries at most two transport blocks according to the RRC message received first. In this case, the number of HARQ processes corresponding to the first PDSCH may be one or multiple.
  • the terminal device may further determine that each transport block in the first PDSCH corresponds to its corresponding in the HARQ process set. HARQ process.
  • the terminal device may, for example, determine the HARQ process corresponding to each transport block according to the method in the prior art.
  • step 230 specifically includes: determining the HARQ process corresponding to each transport block in the PDSCH according to the HARQ process number, the indication of the transport block, and one or more of the following: the configuration parameters of the PDCCH, the network device group sending the PDSCH, The port and BWP of the DMRS indicated in the first DCI.
  • the first PDCCH may include an indication of the transport block.
  • the indication of the transport block may be, for example, the identifier of the transport block, or other information that can be used to distinguish different transport blocks.
  • different transport blocks can be distinguished by the order in which the indication fields of the configuration information appear in DCI.
  • the configuration information of transport block # 1 may precede the configuration information of transport block # 2.
  • the indication bit of the configuration information of transport block # 1 precedes the indication bit of the configuration information of transport block # 2.
  • FIG. 5 show two examples of the indication bits of transport block # 1 and transport block # 2 in DCI.
  • the indicator bit of the transport block # 1 and the indicator bit of the transport block # 2 may be continuous, and the indicator bit of the transport block # 1 may precede the indicator bit of the transport block # 2.
  • the illustrations in the drawings are only examples, and should not constitute any limitation to this application.
  • the indicator bit of transport block # 1 and the indicator bit of transport block # 2 may not be continuous, but the indicator bit of transport block # 1 is still before the indicator bit of transport block # 2. This application does not limit the specific positions of the indication bits of transport block # 1 and the indication bits of transport block # 2 in DCI.
  • distinguishing different transport blocks by indicating the order of bits in DCI is only one possible implementation manner, and should not constitute any limitation to this application.
  • different transmission blocks can also be distinguished by different indexes or numbers, and the specific indication method of the transmission blocks is not limited in this application.
  • the terminal device may further determine the HARQ process corresponding to each transport block according to the HARQ process number and the indication of the transport block.
  • the terminal device may parse the indication field of the transport block in the first DCI to determine the number of transport blocks carried in the first PDSCH.
  • the terminal device may determine the HARQ process corresponding to the transport block based on the method described above; when the number of transport blocks carried in the first PDSCH is multiple, The terminal device may further determine the HARQ process corresponding to each transport block according to the HARQ process number and the indication of the transport block.
  • the process set corresponding to the first PDSCH may be further divided into two subsets based on different indications of the transport block. For example, subset # 1 corresponds to transport block # 1, and subset # 2 corresponds to transport block # 2. Thereafter, the terminal device may determine the HARQ process corresponding to the HARQ process number from the subset corresponding to the transport block.
  • the HARQ process is also a HARQ process corresponding to the transport block carried in the first PDSCH.
  • 6 to 10 are schematic diagrams of different HARQ processes corresponding to different PDCCH configurations and different transport blocks provided by embodiments of the present application.
  • FIG. 6 may correspond to FIG. 3, which is a further refinement of FIG. 3.
  • the HARQ buffer may be divided into different regions based on different PDCCH configurations.
  • Region # 1 corresponds to PDCCH configuration # 1
  • region # 2 corresponds to PDCCH configuration # 2.
  • the area may be further divided into corresponding to different transport blocks.
  • area # 1-1 and area # 2-1 may correspond to transport block # 1
  • area # 1-2 and area # 2-2 may correspond to transport block # 2.
  • the HARQ process saved in the area # 1-1 can correspond to the PDCCH configuration # 1, the transport block # 1, that is, the subset # 1 in the HARQ process set # 1; the HARQ process saved in the area # 1-2 can be PDCCH configuration # 1 corresponds to transport block # 2, that is, subset # 2 in HARQ process set # 1; HARQ processes stored in area # 2-1 can correspond to PDCCH configuration # 2, transport block # 1, that is, HARQ process Subset # 1 in set # 2; HARQ processes stored in area # 2-2 can correspond to PDCCH configuration # 2 and transport block # 2, that is, subset # 2 in HARQ process set # 2.
  • region # 1 and region # 2 may be continuous or discontinuous, which is not limited in this application.
  • Area # 1-1 and area # 1-2 may be continuous or discontinuous, and area # 2-1 and area # 2-2 may also be discontinuous, as shown in FIG. 7. This application does not limit the arrangement position and order of different areas.
  • FIG. 8 may correspond to FIG. 4. Specifically, first, HARQ processes may be renumbered based on different PDCCH configurations. HARQ processes with local numbers 0 to 2N-1 correspond to PDCCH configuration # 1, and HARQ processes with local numbers 2N to 4N-1 correspond to PDCCH configuration # 2. Thereafter, the local number may be further grouped based on different transport blocks to correspond to different transport blocks.
  • a HARQ process with a local number of 0 to N-1 may correspond to PDCCH configuration # 1, transport block # 1, that is, a subset # 1 in HARQ process set # 1; a HARQ process with a local number of N to 2N-1 Can correspond to PDCCH configuration # 1, transport block # 2, that is, subset # 2 in HARQ process set # 1; HARQ processes with local numbers 2N to 3N-1 can correspond to PDCCH # 2, transport block # 1, that is , Subset # 1 in HARQ process set # 2; HARQ processes with local numbers 3N to 4N-1 can correspond to PDCCH # 2 and transport block # 2, that is, subset # 2 in HARQ process set # 2.
  • FIG. 9 is another example corresponding to FIG. 4.
  • the local number of the HARQ process in each subset defined in FIG. 9 and FIG. 8 is the same, but the physical address of the HARQ cache occupied may be different.
  • the local number of the HARQ process set corresponding to the same PDCCH configuration may be continuous or discontinuous.
  • the local number of the HARQ process of the subset # 1 in the HARQ process set # 1 can be 0 to N-1; the local number of the HARQ process of the subset # 2 in the HARQ process set # 1 can be 2N to 3N-1; the local number of HARQ processes in subset # 1 in HARQ process set # 2 can be N to 2N-1; the local number of HARQ processes in subset # 2 in HARQ process set # 2 can be 3N to 4N-1.
  • This application does not limit this.
  • the methods listed above for determining different subsets of the HARQ process set according to the PDCCH configuration and the indication of the transport block are only examples. Based on the same idea, those skilled in the art may also adopt other possible ways to determine the corresponding subset of the HARQ process set according to the PDCCH configuration and the transport block.
  • the present application does not limit the specific manner of determining the subset of the HARQ process set according to the PDCCH configuration and the transport block.
  • the HARQ process set and subset are defined only for ease of understanding, and should not constitute any limitation to this application.
  • Those skilled in the art can also determine the HARQ process set and the subset, and directly determine the HARQ process corresponding to the transport block according to the HARQ process number, transport block, and PDCCH configuration.
  • the above PDCCH configuration may also be replaced with BWP downlink dedicated parameters, BWP downlink parameters, serving cell configuration, control resource set, control resource set group, search space set, search space set group, DMRS port group, or network device group.
  • the above technical solution does not limit the number of network device groups. In other words, whether in a single-site scenario or a multi-site scenario, the above technical solutions can be used to determine the HARQ process of the PDSCH.
  • the terminal device may also determine whether it is currently in a single-site service or multi-site service scenario according to a preset rule.
  • a single site can be a network device or a network device group; a multi-site can be multiple network devices or multiple network device groups. This application does not limit this.
  • the terminal device determines whether it is currently in single-site service or multi-site service according to the number of received PDCCH configuration parameters.
  • the configuration parameters of the PDCCH may include at least one of the following: the serving cell configuration, the BWP downlink parameter under the serving cell configuration, the BWP downlink dedicated parameter under the BWP downlink parameter, the PDCCH configuration under the BWP downlink dedicated parameter, and the The control resource set and the search space set under the PDCCH configuration, or the combined search space set group under the PDCCH configuration.
  • the terminal device receiving multiple PDCCH configuration parameters may refer to receiving multiple serving cell configurations, or receiving multiple BWP downlink parameters, or receiving multiple BWP downlink dedicated parameters, or receiving multiple PDCCH configurations, Either multiple control resource sets are received, or multiple control resource set groups are received, or multiple search space sets are received, or multiple search space set groups are received. In other words, when one of the configuration parameters of the PDCCH listed above received by the terminal device is multiple, it can be determined that the terminal device is currently in a scenario of multi-site service.
  • each configuration parameter may include one or Multiple parameters.
  • a BWP downlink parameter may include a set of parameters
  • a BWP downlink dedicated parameter may also include a set of parameters. This application does not limit the specific content and number of parameters included in each configuration parameter.
  • step 230 may further include: when receiving the configuration parameters of multiple PDCCHs, the terminal device determines the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the configuration parameters of the PDCCH.
  • the terminal device can determine the HARQ process corresponding to the first PDSCH according to the HARQ process number and the configuration parameters of the PDCCH in the case of multi-site service, using the technical solution as described above.
  • the configuration parameter of the PDCCH according to which the terminal device determines the HARQ process corresponding to the first PDSCH may be one of the above-mentioned parameters received by the terminal device. For example, if the terminal device receives multiple PDCCH configurations, the terminal device may determine the HARQ process corresponding to the first PDSCH according to at least the HARQ process number and the PDCCH configuration.
  • configuration parameters of the PDCCH listed above are only examples, and should not constitute any limitation to this application.
  • the configuration parameters of the PDCCH may also include other parameters than those listed above, or may also include parameters that have the same or similar functions as one or more items listed above, which is not limited in this application.
  • step 230 may further include: in the case of the multi-site service, the terminal device determines the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the configuration parameters of the PDCCH.
  • the terminal device determines whether it is currently in single-site service or multi-site service according to the number of received DMRS port groups.
  • the terminal device may determine that it is currently in a multi-site service scenario.
  • Multiple network device groups may respectively send PDSCH based on DMRS ports in different port groups.
  • step 230 may further include: in the case of receiving multiple DMRS port groups, the terminal device determines the HARQ process corresponding to the first PDSCH according to at least the HARQ process number and the port group to which the DMRS port belongs.
  • the terminal device can use the technical solution as described above in the case of multi-site service to determine the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the port group to which the DMRS port belongs.
  • step 230 may further include: in the case of the multi-site service, the terminal device determines the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the configuration parameters of the PDCCH.
  • the terminal device determines the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the indication of the network device group.
  • the terminal device may determine whether it is currently in a multi-site service scenario based on the methods listed above or other possible ways.
  • the technical solution as described above may be adopted to determine the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the indication of the network device group.
  • the terminal device determines at least the HARQ process corresponding to the first PDSCH according to the HARQ process number and the BWP indication.
  • the terminal device may determine whether it is currently in a multi-site service scenario based on the methods listed above or other possible ways.
  • the technical solution as described above may be used to determine the HARQ process corresponding to the first PDSCH at least according to the HARQ process number and the BWP indication.
  • step 240 the terminal device processes the data carried in the first PDSCH according to the HARQ process.
  • the transport block carried by the terminal device in the received PDSCH before the first PDSCH may be stored in the HARQ buffer.
  • the transmission block stored in the HARQ buffer may be, for example, a transmission block that fails decoding, or a transmission block that succeeds in decoding, which is not limited in this application.
  • the terminal device may further according to the HARQ process number in the first DCI, as well as the PDCCH configuration parameters listed above, the port group to which the DMRS port belongs, and sending One or more items in the network device group of the first PDSCH determine the HARQ process corresponding to the first PDSCH.
  • the terminal device may obtain the transmission block of the same HARQ process from the HARQ cache according to the determined HARQ process.
  • the terminal device may perform soft combining and decoding on multiple transmission blocks of the same HARQ process (for example, it may include a transmission block for initial transmission and a transmission block for retransmission).
  • the specific process by which the terminal device processes the data carried in the first PDSCH according to the determined HARQ process may be the same as the prior art. It should also be understood that the specific method for the terminal device to determine whether the transport block carried by the first PDSCH is the initial transmission block or the retransmission transport block can refer to the prior art. For example, it can be determined whether the transmission block is the initial transmission or not according to whether the NDI field is inverted. Retransmission. A detailed description of this specific method is omitted in this article.
  • the terminal device according to the HARQ process number, as well as the configuration parameters of the PDCCH, the port group to which the DMRS port belongs, the BWP indicated by the first DCI, the network device sending the first PDSCH, the type of the first DCI, One or more of the receive beam (or transmit beam) of the PDSCH and the receive beam (or transmit beam) of the first PDCCH, etc., to determine the HARQ process corresponding to the first PDSCH, which can be accurate when multiple PDSCHs are received To determine the corresponding HARQ process.
  • the terminal device can correctly handle the HARQ process in different scenarios, so that the communication system can flexibly adopt different transmission schemes to serve the terminal device, which is beneficial to improve system performance.
  • the communication device 1000 may include a communication unit 1100 and a processing unit 1200.
  • the communication device 1000 may correspond to the terminal device in the foregoing method embodiment, for example, it may be a terminal device, or a chip configured in the terminal device.
  • the communication device 1000 may correspond to the terminal device in the method 200 according to an embodiment of the present application, and the communication device 1000 may include a unit for performing the method performed by the terminal device in the method 200 in FIG. 2.
  • each unit in the communication device 1000 and the other operations and / or functions described above are respectively to implement the corresponding flow of the method 200 in FIG. 2.
  • the communication unit 1100 can be used to perform steps 210 and 220 in the method 200
  • the processing unit 1200 can be used to perform steps 230 and 240 in the method 200.
  • the communication unit 1100 in the communication device 1000 may correspond to the transceiver 2020 in the terminal device 2000 shown in FIG. 12, and the processing unit 1200 in the communication device 1000 may This corresponds to the processor 2010 in the terminal device 2000 shown in FIG. 12.
  • the communication unit 1100 in the communication device 1000 may be an input / output interface.
  • the communication apparatus 1000 may correspond to the network device in the foregoing method embodiment, for example, may be the first network device in the foregoing method embodiment, or be configured in the first network device Can also be the second network device in the above method embodiment, or a chip configured in the second network device.
  • the communication apparatus 1000 may correspond to the first network device in the method 200 according to an embodiment of the present application, and the communication apparatus 1000 may include a unit for performing the method performed by the first network device in the method 200 of FIG. 2 .
  • each unit in the communication device 1000 and the other operations and / or functions described above are respectively to implement the corresponding flow of the method 200 in FIG. 2.
  • the communication unit 1100 can be used to perform steps 210 and 220 in the method 200, and the processing unit 1200 can be used to generate the first DCI.
  • the second network device may perform the same actions as the first network device, and for the sake of brevity, no further details are provided here.
  • the communication unit in the communication device 1000 may correspond to the transceiver 3200 in the network device 3000 shown in FIG. 13, and the processing unit 1200 in the communication device 1000 may This corresponds to the processor 3100 in the network device 3000 shown in FIG. 13.
  • the communication unit 1100 in the communication device 1000 may be an input / output interface.
  • FIG. 12 is a schematic structural diagram of a terminal device 2000 provided by an embodiment of the present application.
  • the terminal device 2000 can be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the above method embodiments.
  • the terminal device 2000 includes a processor 2010 and a transceiver 2020.
  • the terminal device 2000 further includes a memory 2030.
  • the processor 2010, the transceiver 2002 and the memory 2030 can communicate with each other through an internal connection channel to transfer control and / or data signals.
  • the memory 2030 is used to store a computer program, and the processor 2010 is used from the memory 2030 Call and run the computer program to control the transceiver 2020 to send and receive signals.
  • the terminal device 2000 may further include an antenna 2040 for sending uplink data or uplink control signaling output by the transceiver 2020 through a wireless signal.
  • the processor 2010 and the memory 2030 may be combined into a processing device.
  • the processor 2010 is used to execute the program code stored in the memory 2030 to implement the above functions.
  • the memory 2030 may also be integrated in the processor 2010 or independent of the processor 2010.
  • the processor 2010 may correspond to the processing unit in FIG. 11.
  • the above-mentioned transceiver 2020 may correspond to the communication unit in FIG. 11, and may also be referred to as a transceiver unit.
  • the transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.
  • the terminal device 2000 shown in FIG. 12 can implement various processes involving the terminal device in the method embodiment shown in FIG. 2.
  • the operations and / or functions of each module in the terminal device 2000 are respectively for implementing the corresponding processes in the above method embodiments.
  • the above-mentioned processor 2010 may be used to perform the actions described in the foregoing method embodiments that are internally implemented by the terminal device, and the transceiver 2020 may be used to perform the operations described in the foregoing method embodiments by the terminal device to or from the network device. action.
  • the transceiver 2020 may be used to perform the operations described in the foregoing method embodiments by the terminal device to or from the network device. action.
  • the above terminal device 2000 may further include a power supply 2050, which is used to supply power to various devices or circuits in the terminal device.
  • a power supply 2050 which is used to supply power to various devices or circuits in the terminal device.
  • the terminal device 2000 may further include one or more of an input unit 2060, a display unit 2070, an audio circuit 2080, a camera 2090, a sensor 2100, etc. It may also include a speaker 2082, a microphone 2084, and so on.
  • FIG. 13 is a schematic structural diagram of a network device provided by an embodiment of the present application, for example, may be a schematic structural diagram of a base station.
  • the base station 3000 can be applied to the system shown in FIG. 1 to perform the functions of the network device in the above method embodiments.
  • the base station 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBU) (also called digital units) , Digital, unit, DU) 3200.
  • the RRU 3100 may be called a transceiver unit, corresponding to the communication unit 1200 in FIG. 11.
  • the transceiver unit 3100 may also be called a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 3101 and a radio frequency unit 3102.
  • the transceiving unit 3100 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter, transmitting circuit).
  • the RRU 3100 part is mainly used for the transmission and reception of radio frequency signals and the conversion of radio frequency signals and baseband signals, for example, for sending instruction information to terminal devices.
  • the BBU 3200 part is mainly used for baseband processing and control of the base station.
  • the RRU 3100 and the BBU 3200 may be physically arranged together, or may be physically separated, that is, distributed base stations.
  • the BBU 3200 is the control center of the base station, and may also be referred to as a processing unit. It may correspond to the processing unit 1100 in FIG.
  • the BBU 3200 (processing unit) may be used to control the base station to perform the operation flow of the network device (such as the first network device) in the foregoing method embodiment, for example, generate a first DCI, and so on.
  • the BBU 3200 may be composed of one or more boards, and multiple boards may jointly support a wireless access network (such as an LTE network) of a single access standard, or may support different access standards respectively. Wireless access network (such as LTE network, 5G network or other networks).
  • the BBU 3200 also includes a memory 3201 and a processor 3202.
  • the memory 3201 is used to store necessary instructions and data.
  • the processor 3202 is used to control the base station to perform necessary actions, for example, to control the base station to perform the operation flow on the network device in the foregoing method embodiment.
  • the memory 3201 and the processor 3202 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It is also possible that multiple boards share the same memory and processor. In addition, each board can also be provided with necessary circuits.
  • the base station 3000 shown in FIG. 13 can implement various processes involving network devices (such as the first network device or the second network device) in the method embodiment of FIG. 2.
  • the operations and / or functions of each module in the base station 3000 are respectively for implementing the corresponding processes in the above method embodiments.
  • the above-mentioned BBU 3200 can be used to perform the actions described in the foregoing method embodiments that are internally implemented by the network device, and the RRU 3100 can be used to perform the actions described in the previous method embodiments that the network device sends to or receives from the terminal device.
  • the RRU 3100 can be used to perform the actions described in the previous method embodiments that the network device sends to or receives from the terminal device.
  • An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is used to perform the communication method in the foregoing method embodiment.
  • the above processing device may be one or more chips.
  • the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system chip (SoC), or It is a central processor (CPU), it can also be a network processor (NP), it can also be a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller) , MCU), can also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system chip
  • CPU central processor
  • NP network processor
  • DSP digital signal processor
  • microcontroller micro controller
  • MCU microcontroller
  • PLD programmable logic device
  • each step of the above method may be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. In order to avoid repetition, they will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components .
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electronically Erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (random access memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • synchronous RAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • double data SDRAM double data SDRAM
  • DDR SDRAM enhanced synchronous dynamic random access memory
  • ESDRAM synchronous connection dynamic random access memory
  • direct RAMbus RAM direct RAMbus RAM
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on the computer, the computer is caused to execute the embodiment shown in FIG. 2 In any of the embodiments.
  • the present application also provides a computer-readable medium that stores program code, and when the program code runs on a computer, the computer is caused to execute the embodiment shown in FIG. 2 In any of the embodiments.
  • the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disc, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disc, SSD
  • the network device in each of the above device embodiments corresponds exactly to the network device or terminal device in the terminal device and method embodiments, and the corresponding steps are performed by the corresponding modules or units, for example, the communication unit (transceiver) performs the receiving or The steps of sending, other than sending and receiving, can be executed by the processing unit (processor).
  • the function of the specific unit can refer to the corresponding method embodiment. There may be one or more processors.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer.
  • the application running on the computing device and the computing device can be components.
  • One or more components can reside in a process and / or thread of execution, and a component can be localized on one computer and / or distributed between 2 or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • the component may, for example, be based on a signal having one or more data packets (eg, data from two components that interact with another component between the local system, the distributed system, and / or the network, such as the Internet that interacts with other systems through signals) Communicate through local and / or remote processes.
  • data packets eg, data from two components that interact with another component between the local system, the distributed system, and / or the network, such as the Internet that interacts with other systems through signals
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a division of logical functions.
  • there may be other divisions for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • each functional unit can be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented using software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmit to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the usable medium may be a magnetic medium (eg, floppy disk, hard disk, magnetic tape), optical medium (eg, DVD), or semiconductor medium (eg, solid state disk (SSD)), or the like.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

La présente invention concerne un procédé de réception de données et un appareil de communication. Le procédé consiste : à recevoir par le biais d'un dispositif terminal un PDSCH, une indication d'un numéro de processus HARQ étant comprise dans un PDCCH afin de planifier le PDSCH ; à déterminer le numéro de processus HARQ correspondant au PDSCH selon le numéro de processus HARQ et un ou plusieurs des éléments suivants : un paramètre de configuration du PDCCH, un port DMRS, une BWP, et un groupe de dispositifs de réseau permettant d'envoyer le PDSCH ; et à traiter des données transportées par le PDSCH selon un processus HARQ déterminé. Comme un dispositif de réseau n'est pas visible par le dispositif terminal, lorsque le dispositif terminal reçoit la pluralité de PDSCH, si le processus HARQ est déterminé uniquement selon le numéro de processus HARQ, le numéro de processus HARQ peut correspondre à de multiples processus HARQ, et le traitement des données peut échouer. Au moyen du procédé décrit dans la présente invention, le processus HARQ correspondant au PDSCH peut être déterminé de manière précise, ce qui facilite l'amélioration des performances de transmission de données.
PCT/CN2019/117935 2018-11-16 2019-11-13 Procédé de réception de données et appareil de communication WO2020098685A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811369613.7A CN111200871B (zh) 2018-11-16 2018-11-16 接收数据的方法和通信装置
CN201811369613.7 2018-11-16

Publications (1)

Publication Number Publication Date
WO2020098685A1 true WO2020098685A1 (fr) 2020-05-22

Family

ID=70731772

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/117935 WO2020098685A1 (fr) 2018-11-16 2019-11-13 Procédé de réception de données et appareil de communication

Country Status (2)

Country Link
CN (1) CN111200871B (fr)
WO (1) WO2020098685A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112019463A (zh) * 2020-09-04 2020-12-01 中兴通讯股份有限公司 信道状态发送、接收、信令信息传输方法、节点和介质
CN113767695A (zh) * 2021-08-05 2021-12-07 北京小米移动软件有限公司 通信方法、装置和存储介质
CN115087099A (zh) * 2022-08-19 2022-09-20 翱捷科技股份有限公司 一种寻呼信道的增强接收装置和方法
EP4152663A4 (fr) * 2020-06-09 2023-11-01 Huawei Technologies Co., Ltd. Procédé et appareil de communication

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112021017989A2 (pt) * 2019-03-11 2021-11-16 Beijing Xiaomi Mobile Software Co Ltd Método, aparelho e dispositivo para indicar a transmissão, e, mídia de armazenamento legível por computador não transitória
CN115943594A (zh) * 2020-09-22 2023-04-07 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
US20230413282A1 (en) * 2020-09-30 2023-12-21 Beijing Xiaomi Mobile Software Co., Ltd. Method for transmitting information, apparatus, terminal, device and medium
CN114339615B (zh) * 2020-09-30 2023-10-20 大唐移动通信设备有限公司 Bwp的配置方法、装置、网络侧设备及终端
CN115189807B (zh) * 2021-04-02 2024-06-11 维沃移动通信有限公司 Harq进程号的确定、指示方法、装置、终端及网络侧设备
WO2024000568A1 (fr) * 2022-07-01 2024-01-04 Lenovo (Beijing) Limited Procédé et appareil d'indication de nombre de processus harq

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150156753A1 (en) * 2010-03-26 2015-06-04 Samsung Electronics Co., Ltd. Method and apparatus for transmitting downlink control information for resource allocation in a wireless communication system
CN107733597A (zh) * 2016-08-11 2018-02-23 株式会社Ntt都科摩 确定混合自动重复请求进程号的方法以及基站和用户设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018101821A (ja) * 2015-04-24 2018-06-28 シャープ株式会社 端末装置、基地局装置、集積回路、および、通信方法
CN107027180B (zh) * 2016-02-02 2019-08-30 中兴通讯股份有限公司 非授权载波上行数据的发送方法及终端
CN108270527A (zh) * 2017-01-04 2018-07-10 电信科学技术研究院 一种混合自动重传请求harq传输方法及相关设备
CN108631958A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 一种确定混合自动重传请求harq进程的方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150156753A1 (en) * 2010-03-26 2015-06-04 Samsung Electronics Co., Ltd. Method and apparatus for transmitting downlink control information for resource allocation in a wireless communication system
CN107733597A (zh) * 2016-08-11 2018-02-23 株式会社Ntt都科摩 确定混合自动重复请求进程号的方法以及基站和用户设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Summary of DL/UL Scheduling and HARQ Management", 3GPP TSG-RAN WG1 MEETING AH 1801 R1-1803388, 2 March 2018 (2018-03-02), XP051398549 *
SAMSUNG: "HARQ Management and Feedback", 3GPP TSG RAN WGI MEETING NR#3 R1-1716005, 21 September 2017 (2017-09-21), XP051339464 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4152663A4 (fr) * 2020-06-09 2023-11-01 Huawei Technologies Co., Ltd. Procédé et appareil de communication
CN112019463A (zh) * 2020-09-04 2020-12-01 中兴通讯股份有限公司 信道状态发送、接收、信令信息传输方法、节点和介质
CN113767695A (zh) * 2021-08-05 2021-12-07 北京小米移动软件有限公司 通信方法、装置和存储介质
CN115087099A (zh) * 2022-08-19 2022-09-20 翱捷科技股份有限公司 一种寻呼信道的增强接收装置和方法
CN115087099B (zh) * 2022-08-19 2022-11-15 翱捷科技股份有限公司 一种寻呼信道的增强接收装置和方法

Also Published As

Publication number Publication date
CN111200871B (zh) 2022-02-18
CN111200871A (zh) 2020-05-26

Similar Documents

Publication Publication Date Title
US12003340B2 (en) Method for sending hybrid automatic repeat request acknowledgment information, method for receiving hybrid automatic repeat request acknowledgment information, and communications apparatus
WO2020098685A1 (fr) Procédé de réception de données et appareil de communication
JP7032576B2 (ja) フィードバック情報送信方法および通信デバイス
US11956794B2 (en) Data sending and receiving method and communication apparatus
US11968675B2 (en) Uplink control information sending and receiving method and communications apparatus
US10193681B2 (en) Method, apparatus and computer program for wireless communications
TWI530144B (zh) 處理通訊運作的方法及其通訊裝置
US9838161B2 (en) Bundling HARQ feedback in a time division duplexing communication system
US11431462B2 (en) Indication method, network device, and user equipment
CN113490278B (zh) 下行信号传输的方法和设备
US20140105224A1 (en) Retransmissions in a Communication System Using Almost Blank Subframes
WO2021032015A1 (fr) Procédé de transmission d'informations de rétroaction et appareil de communication
EP4075894A1 (fr) Procédé et appareil de transmission d'informations de commande de liaison montante
WO2021017765A1 (fr) Procédé de communication et dispositif de communication
WO2020098662A1 (fr) Procédé et appareil de communication permettant d'envoyer et de recevoir un canal physique de commande de liaison descendante
WO2023208211A1 (fr) Procédé et appareil de communication
WO2020143813A1 (fr) Procédé et appareil de transmission d'informations
WO2022206893A1 (fr) Procédé de communication et appareil de communication
WO2020156002A1 (fr) Procédé de communication et dispositif de communication
WO2023125762A1 (fr) Procédé et appareil de communication

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

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

Country of ref document: EP

Kind code of ref document: A1